Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

I can't synchronize my Exchange account on Mail app.

I'm trying to synchronize my Exchange Email and Calendar accounts, but when I try to do so nothing happens, I just can't get any new emails or calendar invites.


On the Console app I can see this error whenever I open the Email app:


7/24/17 7:33:21.864 PM Mail[446]: Received an unexpected error: Error Domain=SOAPWebServicesErrorDomain Code=-997 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -997.)", response: (null)

7/24/17 7:33:22.468 PM Mail[446]: -[SOAPParser:0x60800045e3c0 parser:didStartElement:namespaceURI:qualifiedName:attributes:] Type not found in EWSMeetingCancellationMessageType for DoNotForwardMeeting (t:DoNotForwardMeeting)


Do you know how this could be fixed?


I have tried deleting this accounts cache, deleting the Calendars app cache, and nothing works.

MacBook Pro with Retina display, OS X Yosemite (10.10.5)

Posted on Jul 24, 2017 5:57 PM

Reply
Question marked as Top-ranking reply

Posted on Aug 7, 2017 6:38 PM

I ran into this issue on one client aswell but only for their calendar - not their e-mail.


There seems to be a current service interruption with Office365 (registered with ID EX111121 in the status dashboard) causing connectivity issues. I've copy-pasted the text int heir status message here:


User Impact: Users may be unable to connect to the Exchange Online service via the Outlook client and mobile devices.
More info: While we work to remediate impact, Outlook on the web can be used as an alternative method to connect to the service. Our interim mitigation improved availability for Outlook client requests, but mobile devices may continue to experience impact until the code issue is resolved. Impact to other Exchange Online protocols appears to be very infrequent.
Current status: We're reverting the code update that caused this issue, and we expect to completely restore service in the next 18 hours.
Scope of impact: The listed number of your affected users reflects how many users could potentially experience this issue; however, impact occurs only if a user connection is routed through the affected infrastructure. This issue is likely affecting a very limited percentage of users and requests.
Start time: Wednesday, July 26, 2017, at 2:15 PM UTC
Estimated time to resolve: We expect this issue to be completely resolved for all affected users within the next 18 hours as the fix is safely implemented through our change management process.
Preliminary root cause: A recent change introduced a code issue to the infrastructure responsible for client access connectivity and routing. The code issue caused the systems to perform below acceptable thresholds and resulted in connectivity issues.
Next update by: Thursday, July 27, 2017, at 7:00 PM UTC

40 replies
Sort By: 
Question marked as Top-ranking reply

Aug 7, 2017 6:38 PM in response to Ang3lusG

I ran into this issue on one client aswell but only for their calendar - not their e-mail.


There seems to be a current service interruption with Office365 (registered with ID EX111121 in the status dashboard) causing connectivity issues. I've copy-pasted the text int heir status message here:


User Impact: Users may be unable to connect to the Exchange Online service via the Outlook client and mobile devices.
More info: While we work to remediate impact, Outlook on the web can be used as an alternative method to connect to the service. Our interim mitigation improved availability for Outlook client requests, but mobile devices may continue to experience impact until the code issue is resolved. Impact to other Exchange Online protocols appears to be very infrequent.
Current status: We're reverting the code update that caused this issue, and we expect to completely restore service in the next 18 hours.
Scope of impact: The listed number of your affected users reflects how many users could potentially experience this issue; however, impact occurs only if a user connection is routed through the affected infrastructure. This issue is likely affecting a very limited percentage of users and requests.
Start time: Wednesday, July 26, 2017, at 2:15 PM UTC
Estimated time to resolve: We expect this issue to be completely resolved for all affected users within the next 18 hours as the fix is safely implemented through our change management process.
Preliminary root cause: A recent change introduced a code issue to the infrastructure responsible for client access connectivity and routing. The code issue caused the systems to perform below acceptable thresholds and resulted in connectivity issues.
Next update by: Thursday, July 27, 2017, at 7:00 PM UTC

Reply

Aug 4, 2017 12:16 AM in response to Ang3lusG

Morning all - I'm the Exchange Administrator for a large university... 😉


Microsoft are now aware and are working on this. under EX112430 - "Mail sync issue"


Details Below - as I get more I'll post here.


Status:

Service degradation

User impact:

Users are unable to sync emails using Apple Mail on their Mac computers.

Latest message:

Title: Mail sync issue User Impact: Users are unable to sync emails using Apple Mail on their Mac computers. More info: While we're focused on remediation, users may be able to access their mail with the Outlook for Mac client or Outlook on the web as an alternative method. Current status: We're working to develop a fix for this issue. After deploying a potential solution, we determined that a more comprehensive fix is needed to address the underlying issue causing impact. We're continuing our work to test and develop the fix, which will then be deployed across the affected environment.

Scope of impact: Impact is specific to users attempting to sync emails using the default mail client on Mac machines.

Start time: Monday, July 31, 2017, at 2:55 PM UTC

Preliminary root cause: A recent update contained a code issue that prevents users from syncing emails using Apple Mail on Mac computers.

Next update by: Friday, August 4, 2017, at 8:00 PM UTC

Reply

Jul 24, 2017 8:31 PM in response to Ang3lusG

You need to enable 2 Factor Authentication on your Apple ID and create an app specific password to use. If your account won’t allow 2 Factor Authentication, try 2 step verification. The change was only supposed to affect 3rd party e-mail programs, but others have posted the same problem when using older OS versions of Mail and Calendar.


Apple ID -Two-factor authentication


Apple ID - Using app-specific passwords


Apple ID - Two Step Verification App Specific Passwords


Apple ID - Two Step Verifications FAQ

Reply

Jul 26, 2017 9:36 AM in response to Ang3lusG

We've started getting EXACTLY the same repeated instances in the system log across many users in the company…

Type not found in EWSMeetingRequestMessageType for DoNotForwardMeeting

Type not found in EWSMeetingCancellationMessageType for DoNotForwardMeeting


(This is in Mail both in Mavericks and El Capitan)


I don't know that it's to do with AppleID 2-factor authentication, but I do worry it's something to do with Exchange/Outlook365 2FA being made active somewhere, and our Apple Mail.app users are unable to do much about it. The inbox just won't synch new incoming mails, and the systems logs are just filling up very quickly


The first cases were on the morning of the 24th. Are you also on Office365?


we've been asking users to workaround this with the web https://outlook.office.com/owa/ client until we can suss what the heck is going on.

Reply

Jul 27, 2017 5:40 AM in response to Ang3lusG

I found an event from an invite sent from an Outlook user, deleted it, and since then Calendar on the mac would synch OK and not throw those EWS SOAP errors in the log


however mail carries on the same :-(


A new oddity is that it is JUST the inbox. If I use outlook web to move a new e-mail to a sub-folder I already have, then the mail appears in Apple mail without any further action!

Reply

Jul 28, 2017 6:52 PM in response to Ang3lusG

Started having the same problem on the same day - around noon EDT of Jul 25. Logs are full of identical error messages and Mail.app is blocked if there is a calendar invite (any invite) in my inbox. The only way to unblock it is to accept the invite from the Web (or mobile phone) and then delete the invite email from the Trash folder.


And I can no longer create events in the Calendar. I tried to do it and Calendar fails with another error. I ended up with like 50+ instances of the identical event.


Our IT did not install any patches/updates around these days so it seems that something got changed on O365 side.

Reply

Jul 31, 2017 1:57 PM in response to Ang3lusG

I'm having the same issues as described in this thread. Has anyone opened a ticket with Apple or Microsoft and gotten any further info? I'm assuming it's a Microsoft issue since it started out of the blue without me updating my Macs. FYI I see the same issues (initially mail dead, then deleted the bad invite and now just calendar won't work) on both of the 2 Macs I have, but not on my iPhone.

Reply

Jul 31, 2017 3:32 PM in response to techyjoel

We are having this at our org where Exchange will stop pulling mail and any Shared Cals just error out. Only happens on 10.10 and 10.11. We opened a ticket with our support company who opened a ticket with MS for us. MS told us it's apples fault somehow and that Sierra works fine so use that. They could not tell us what Apple might have done to cause this but passed the buck anyway.

Reply

Aug 2, 2017 5:07 AM in response to Ang3lusG

The Apple Mail error with Office365 Exchange appears to be related to the Security Update 2017-003 patch. Only after the update did I have the problems.


This website reports the same error -


Possible Apple Mail issues after Security Update 2017-003 - Jamf Nation


I spoke with Apple about it last night. They reported only seeing one other incident. They created a new ticket and said they would get back to me.


This is a big problem waiting to happen. It's only a matter of time before more users push the Security Update. It appears the problem is Apple's fault.

Reply

Aug 2, 2017 5:45 AM in response to user0987

On one of our most visible users (CEO) with the issue - he is on 10.11.6 and with "softwareupdate -l" it still lists:


* Security Update 2017-003 (10.11.6), 519906K [recommended] [restart]


Plus I've got it on 10.11.5 - you need to run the .6 update before that security update I think, plus it's not listed in my "System Information" under Software/Installations. And I've users on Mavericks with the issue - in fact they were the first to report it

Reply

Aug 2, 2017 7:31 AM in response to Ang3lusG

This problem was driving me nuts, especially because of the broken Calendar. I have just upgraded to Sierra and it seems that the things got better - at least the Calendar does not show errors anymore and Mail does not get stuck on the incoming invites.


However, there are still quite a few messages dumped to the log every time Mail syncs:


default 10:28:22.655503 -0400 Mail [outlook.office365.com](0x608000a316e0) Receiving: <EWSGetItemResponseType> {

ResponseMessages = [

[0] = <EWSItemInfoResponseMessageType> {

ResponseClass: 3;

MessageText = The specified object was not found in the store., The process failed to get the correct properties.;

ResponseCode = 190;

Items = [

]

}



[1] = <EWSItemInfoResponseMessageType> {

ResponseClass: 3;

MessageText = The specified object was not found in the store., The process failed to get the correct properties.;

ResponseCode = 190;

Items = [

]

}



]

}

Reply

Aug 2, 2017 9:48 AM in response to user0987

I think it's just a timing coincidence that Apple issued that security update at about the same time that Microsoft changed something on their Office365 Exchange servers. Another reason why people are noticing this at different times it that it seems to be triggered by receiving and attempting to download an email with a meeting notification embedded, and everything works fine until that point.


I first encountered this problem on July 31st on a Mac running Snowleopard (10.6.8). It certainly hasn't seen any recent security or other updates from Apple in a few years, yet it encountered the same Exchange email problems in Apple Mail as other newer systems at about the same time.


It really looks like it's a problem cause by Microsoft, and reverting from that change seems to be the only way to fix it for all systems that are impacted. I don't see any hope that Apple will release an update to Snowleopard to address a newly discovered Mail.app issue.


I had also submitted a note to MacInTouch in the hope of getting more visibility to this problem.


MacInTouch Note

Reply

Aug 3, 2017 7:11 AM in response to Ang3lusG

FYI : I'm seeing the same error codes in my logs. I THOUGHT the problem with my mail was related to that but I had a couple old SMTP connections that were bad (found in Connection Doctor in the Mail app) when I removed them, my mail came through. Calendar is still not syncing though.

Reply

I can't synchronize my Exchange account on Mail app.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.