Exchange under Mountain Lion

Apple, please fix this. We know you're on it but please be fast. I'm really losing money here since I was so stupid to upgrade both of my macs. I'm not able to work in a normal way - this circumstances will effect my capability to buy a new iPhone in october or not

I dont understand the details but load-balanced Exchange servers seem to go a long way towards explaining the very mixed success people having been having with the various "solutions" in this thread. In particular the mail dropping out after 15 minutes or restarting Mail.

Let's hope this helps Apple swiftly solve this show-stopping problem.

Can only add my +1. Upgraded to Mountain Lion from Snow Leopard, in which Mail used to have no problem connecting with my business and personal email accounts and the Exchange server of a key client. Since upgrade, no parlez with the Exchange account. Other accounts are OK. Other than Exchange issue, ML upgrade went OK.

I use Macs because they're supposed to work out of the box, but this is wasting all our time and money totally unnecessarily, and makes my business look out of step with my Exchange-using clients. Amazed that ML was released without this being spotted.

While I understand everyone's frustration, you should never blindly upgrade your entire OS if you have mission critical work on a stable system - especially on multiple machines. Any OS upgrade is bound to have issues as they are extremely complex things with many parts.

Yes, Macs are supposed to work 'out of the box' but that does not mean that there will absolutely no issues for everyone in any situation - that viewpoint is simply unrealistic.

In addition, not all third-party software is guaranteed to work with an OS upgrade so if you have something you rely on, you should wait and check the discussion boards to see if there are any issues before making the plunge.

Granted, this is a Mac OS X issue (which they are working on) but no one forced anyone to upgrade. Any piece of software as complex as an OS will inherently have some bugs so it's always wise to be patient, check to see if there are any major issues or wait until the first bug patch before installing.

All that said, editing the 'hosts' file is a solid workaround and as far as I know I haven't seen anyone on here who has said they have specifically tried that and it did not work but correct me if I am wrong.

The other thing that people need to realize is that this is not happening with all Exchange servers. After we rebuilt our domain, the problem went away for me so this is not purely Apple's issue - it is an Apple Mail talking to Exchange servers that are configured with split domains problem.

Steven Carter wrote:

I use Macs because they're supposed to work out of the box, but this is wasting all our time and money totally unnecessarily, and makes my business look out of step with my Exchange-using clients. Amazed that ML was released without this being spotted.

I use Macs with Exchange 2010 and 2007, uograded to ML and everything is the same, working.

So - I just tried something that seems to help. Still a bug in ML, but perhaps this might stick a bit longer?

First I deleted my exchange account in accounts. Then I went into the "library" folder. Home>Library>Mail and deleted EVERYTHING that was related to my exchange account. After that I re-added my exchange account and everything populated as it should. I turned mail off and back on - still there. I re-booted - still there.

I'm traveling tomorrow so my MBP will be off for a couple hours so we'll see if it sticks. For now everything is working as it should.

Hope that helps. And hope it sticks.

Hi all,

I am having the same issue and the clearly is something wrong with Mountain Lion's Mail.app. I can setup my account fine, however my mail never downloads. Stranger still is that I can see my mail boxes just not any of the messages. I have to open up console to see the actual errors.

BAD FORM APPLE!!! Errors should always be shown to the user. Operations initiated by the user should never just silently fail.

For those who are interest and in the vain hope the Apple are monitoring the thread, below are the to errors from my console logs:

1/08/12 2:32:03.760 PM Mail[379]: *** Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1485/Message/EWS/EWSConnection.m:555

Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)" UserInfo=0x7ffbfa2d80a0 {EWSErrorPosition=433, EWSErrorMessage=The required attribute 'Id' is missing., EWSErrorLine=1, NSUnderlyingError=0x7ffc0253fa40 "The operation couldn’t be completed. (SOAPWebServicesErrorDomain error -1000.)"}, response: (null)

(

0 CoreMessage 0x00007fff932c6ab7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141

1 CoreMessage 0x00007fff932c6928 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215

2 Message 0x00007fff8cc0871e -[EWSConnection sendMessage:forRequest:] + 762

3 Message 0x00007fff8cc11743 -[EWSGateway sendMessage:forRequest:] + 69

4 Message 0x00007fff8cc280ca -[EWSRequestOperation executeOperation] + 110

5 CoreMessage 0x00007fff932e2106 -[MonitoredOperation main] + 219

6 Foundation 0x00007fff94026bb6 -[__NSOperationInternal start] + 684

7 Foundation 0x00007fff9402e3d1 __block_global_6 + 129

8 libdispatch.dylib 0x00007fff8bc0ef3d _dispatch_call_block_and_release + 15

9 libdispatch.dylib 0x00007fff8bc0b0fa _dispatch_client_callout + 8

10 libdispatch.dylib 0x00007fff8bc0c23e _dispatch_worker_thread2 + 304

11 libsystem_c.dylib 0x00007fff93bd6ceb _pthread_wqthread + 404

12 libsystem_c.dylib 0x00007fff93bc11b1 start_wqthread + 13

)

1/08/12 2:32:44.165 PM Mail[379]: *** Assertion failure in -[EWSGateway fetchCopyOfSyncIssuesEntryID], /SourceCache/Message/Message-1485/Message/EWS/EWSGateway.m:1853

Didn't get a proper response for a GetFolder request on Inbox

(

0 CoreMessage 0x00007fff932c6ab7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141

1 CoreMessage 0x00007fff932c6928 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215

2 Message 0x00007fff8cc1c088 -[EWSGateway fetchCopyOfSyncIssuesEntryID] + 425

3 Message 0x00007fff8cc0139b -[EWSAccount _synchronizeMailboxListWithUserInput:] + 585

4 Message 0x00007fff8cc0095f -[EWSAccount synchronizeAllMailboxes] + 76

5 Message 0x00007fff8cc0081d -[EWSAccount fetchSynchronouslyIsAuto:] + 496

6 CoreFoundation 0x00007fff8de8fcac __invoking___ + 140

7 CoreFoundation 0x00007fff8de8fb47 -[NSInvocation invoke] + 263

8 CoreMessage 0x00007fff932e1d5d -[MonitoredInvocation invoke] + 225

9 CoreMessage 0x00007fff932fa2b2 -[ThrowingInvocationOperation main] + 33

10 CoreMessage 0x00007fff932a6602 -[_MFInvocationOperation main] + 431

11 Foundation 0x00007fff94026bb6 -[__NSOperationInternal start] + 684

12 Foundation 0x00007fff9402e3d1 __block_global_6 + 129

13 libdispatch.dylib 0x00007fff8bc0ef3d _dispatch_call_block_and_release + 15

14 libdispatch.dylib 0x00007fff8bc0b0fa _dispatch_client_callout + 8

15 libdispatch.dylib 0x00007fff8bc0c23e _dispatch_worker_thread2 + 304

16 libsystem_c.dylib 0x00007fff93bd6ceb _pthread_wqthread + 404

17 libsystem_c.dylib 0x00007fff93bc11b1 start_wqthread + 13

)

Same problem here!!

mails diseppear in inbox or other folders, after rebuild (takes long time) they reappear 😟 then some folders are gone

horrible

after deleting everything with appzapper except the mail.app reconfig everything works fine again.

Bud this can't be done everyday :@

Hopefully there comes a quick fix

i also had this problem in Lion

no problem on iPad, iPhone, iPod and W7 Laptop

Ja. es ist eine Schande für Apple, ein solches Betriebssystem auf den Markt zu bringen.

Wie kann man nur so von seinen Idealen abweichen? Steve Jobs - nicht mehr da!

Ob man da bei Apple bleiben mag, bei solcher Unprofessionalität?

Beruflich kann ich den Mac nun nicht mehr einsetzen seit Mountain Lion - sehr ärgerlich.😠

Vielleicht sollte man seitens Apple mehr Energie in die Produkte, als in die Patentstreitigkeiten stecken? - Wäre vielleicht ein Ansatz.

Und vielleicht kommt doch möglichst schnell ein Update, um den Exchange-Fehler zu beseitigen? 😠

OK, why removing the .me account made my Exchange account work I don't know. But when I rebooted, all failed again 😟

Hallo,

der in diesem Thread beschriebene Workaround von Ondray Wells jr. vom 26.07.2012 19:31 Uhr funktioniert bei mir.

Mail kann offensichtlich den Servernamen nicht in eine IP Adresse auflösen. Der Eintrag der (zutreffenden) IP Adresse in den Einstellungen wird aber bei jedem Neustart von Mail automatisch überschrieben, so dass div. Lösungen, die hier beschrieben wurden nur solange funktionierten, bis Mail geschlossen wird.

Der Eintrag der IP und der zughörigen Serveradresse in der hosts-Datei löste bei mir das Problem dauerhaft, da Mail diese Datei beim Start abfragt.

Es ist zu hoffen, dass beim nächsten Update der bisherige Zustand wieder hergestellt wird, bei der die IP des ExchangeServers direkt eingetragen werden kann, ohne ständig überschrieben zu werden, oder eine funktionierende Namensauflösung implementiert wird.

While I take your point about being circumspect about upgrading - I usually am - the fact that Apple offers this as a paid-for OS release and sends me several emails inviting me to upgrade, along with blurb quoting 'the most stable OSX release ever' or some such, encouraged me to make this uncharacteristically rash buying decision. I look forward to future releases suggesting 'OSX Mangy Alley Cat - available now, but we suggest you wait a bit until other people have found out what's wrong with it...'

I don't expect everything to be right and as I pointed out, most other stuff worked perfectly satisfactorily. But Apple's historical perfectionist approach, and the numbers of people apparently wrestling with this issue, suggests to me that someone missed something. Look forward to a proper fix.

Heh. well, having finally found a friendly Exchange-speaking, Terminal-daring soul to pilot me through the 'hosts' workaround I seem to have fixed it. Interestingly he said as he cheered from the sidelines that 'this is exactly the same issue we sometimes have with Windows.' So I'm happy to take some of my previous comments re Apple back. But I still think it's a pain and could have been picked up before.

Incidentally, in the workaround, we found we had to put the IP address first followed by the server name to make it work, whereas the original recipe from Ondray Wells Jr had it the other way round. Someone else may have already said this.

This has wrecked my whole team's productivity for 2 days! I need an step by step explanation of how to fix this. We have reverted to our personal Gmail accounts to simply stay productive.

Please help me fix the bug that will not change the internal server address for my exchange account so that my email will work again!

-ARW