Snow Leopard native Mail app / EWS error
I know this is a bit of a reach, but Apple support has been worthless. I have a couple of Mac clients that are connecting to Exchange 2007 via the new Snow Leopard Mail app that uses EWS for connectivity. However, the app is not downloading the entire contents of the many of the users' mail folders. Here's the particular error in question...
Exchange Sync: Unable to sync item id:AAMkADliZjRiYWIwLTMzNmMtNDRhYi1iYWViLTE0NzliZDA5NTJlNQBGAAAAAACHxo0gPx2hS5kbhgKymkgeBwDR6CpKTNL+Rq+Pv0XsImIKAAALtwAnAADR6CpKTNL+Rq+Pv0XsImIKAAALt0i/AAA= (item with incomplete headers)
This is repeated hundreds of times in the system log - with the message id varying in each error. Apple Support has pointed the finger at Exchange - saying that something is misconfigured. However, EVERY other client (Entourage 2008 WebDAV, Entourage 2008 EWS, iPhone, OWA, Outlook 2007) can sync the messages properly.
My uneducated guess is that the SOAP envelope is somehow not getting encoded/passed properly and that Apple is at fault, not Exchange. Anyone have any insight on what else I could look at for troubleshooting purposes?
- Mark
所有回覆
- Not sure if I can be help you. But we'll give it a try. I'm an Exchange 2007 administrator and use all those clients you have, except Entourage WebDAV, which I've had quite some problems with. All the others have worked fine so far. That is: It's disappointing that Snow Leopard Mail doesn't support public folders.
Now to your problem: I need a bit more information. Do all users have those problems with SL Mail? Or only some users? Do all users have Entourage 2008?
These entries show up in /private/var/log/system.log?
Have you enabled logging for the mail.app (there's a script in the Scripts folder)?
Best regards,
Jon-Alfred Smith
MCTS: Messaging, MCSE: S+M - Snow Leopard’s Exchange client won’t be the Mac equivalent of Outlook in terms of functionality. It might not even be an Entourage.
Read below about the same..
http://www.macwindows.com/column_snowleopard_exchange.html
Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3| - I am the local Exchange admin as well - a single Exchange 2007 server (SP2) with about 50 users. Only 2 are Mac clients - both are executives of the company (of course). I haven't deployed Snow Leopard on their laptops yet - am just testing it on my Macbook that I use for supporting them. So, my environment is this -> Macbook Pro, Snow Leopard, 8 GB RAM, Office 2008, Entourage Web Services Edition.
I initially had a mailbox about 200MB - with about 5000 items scattered across a few folders. Entourage 2008 synced all the messages. Mail would only sync about 3500. Apple initially told me that I had to break my folders up so that any one folder only contained 500 items (or less). Quite a pain - but I did it. Same problem. I've since done some long overdue mailbox cleanup and have gotten my mailbox to about 90MB (1300 items). Again - Entourage syncs everything. Mail only syncs 1000 - missing about 300. I've reviewed some of the messages that aren't syncing - there's nothing special about them that I can see.
The error(s) I initially referenced in my first message do occur in system.log (viewed via the Console app). It appears I get a single error per message that doesn't sync. Finally, at the end, there's an assertion that's trapped. Here are the details...
*** Assertion failure in -[EWSGateway _handleSyncedMessagesWithoutHeaders:inFolderIdString:store:newSyncState:], /SourceCache/Message/Message-1076.1/MessageStores.subproj/EWSGateway.m:760
Exchange Sync: Reattempting to sync folder:2007 — Work with folderId:AAMkADliZjRiYWIwLTMzNmMtNDRhYi1iYWViLTE0NzliZDA5NTJlNQAuAAAAAACHxo0gPx2hS5kbhgKymkgeAQDR6CpKTNL+Rq+Pv0XsImIKAAALtwAnAAA=
(
0 Message 0x00007fff82c72828 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff82c7278d -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff82bc7ea2 -[EWSGateway _handleSyncedMessagesWithoutHeaders:inFolderIdString:store:newSyncState:] + 1578
3 Message 0x00007fff82bc97f2 -[EWSGateway _syncFolderItemsFromTargetFolderIdType:syncState:forStore:includesLastItem:] + 818
4 Message 0x00007fff82bc9015 -[EWSGateway syncFolderItemsFromFolderIdString:syncState:forStore:] + 494
5 Message 0x00007fff82bd9209 -[EWSStore _fetchChangesFromServer] + 335
6 Message 0x00007fff82bd7373 -[EWSStore openSynchronouslyUpdatingMetadata:] + 114
7 CoreFoundation 0x00007fff8788a35c __invoking___ + 140
8 CoreFoundation 0x00007fff8788a22d -[NSInvocation invoke] + 141
9 Message 0x00007fff82acea35 -[MonitoredInvocation invoke] + 214
10 Message 0x00007fff82ab5f50 -[ThrowingInvocationOperation main] + 31
11 Message 0x00007fff82ab5890 -[_MFInvocationOperation main] + 275
12 Foundation 0x00007fff873e211a -[__NSOperationInternal start] + 673
13 Foundation 0x00007fff873e1dd8 ____startOperations_block_invoke_2 + 99
14 libSystem.B.dylib 0x00007fff80071cf6 _dispatch_call_block_and_release + 15
15 libSystem.B.dylib 0x00007fff800501e9 _dispatch_worker_thread2 + 231
16 libSystem.B.dylib 0x00007fff8004fb28 _pthread_wqthread + 353
17 libSystem.B.dylib 0x00007fff8004f9c5 start_wqthread + 13
)
I understand that iPhones, Outlook, etc connect using different methods than Mail. Heck, from what I gather, even though Entourage WSE and Mail both use EWS, they vary in their implmentations, since Entourage supports public folders and Mail doesn't. Just irritates me that Apple is telling me that something is misconfigured on Exchange, when the lone problem I'm having is with Mail and none of my other clients.
Regarding enabling logging for mail.app, please elaborate with details if possible. My Mac experience is limited at best. (I know just enough to be incredibly dangerous...)
EDIT: Never mind. Found the logging script. Will post results (if anything worthwhile is logged).
EDIT2: Turned on logging. Nothing additional worthwhile was written to the log (only entries pertained to check my gmail account).
- Mark Now I have had time to do bit more testing. Configured my mail account at work on my MacBook Pro (4 GB sic transit ...) with Snow Leopard (SL) Mail: about 350 MB and some 2200 messages with few folders. No error what so ever in the /private/var/log/system.log. This is with update: 10.6.1 (I guess that's your version too).
One surprising finding. The mail account was configured with Autodiscover. At work this is done with an SRV record. Entourage 2008 EWS needed to be configured manually and uses obviously only https://domain.com/Autodiscover/Autodiscover.xml and https://autodiscover.domain.com/Autodiscover/Autodiscover.xml (that is, of the several Exchange organizations I have access to, none uses the HTTP redirect way).
Personally I believe you have become an involuntary beta tester and discovered some show-stopping bugs in SL Mail with unintelligible error messages that should be handed back to the developers. I don't know if it has anything to do with the SOAP envelope.I would have steered clear of a version 1.0 implementation of Exchange access for business use, especially with that kind of support from Apple you mention, and opted for Office 2008/SP2 with Entourage 2008 WSE instead (the latter being version 13.0.0, released on August 13, 2009 :-), for several reasons:
* Office 2008 has been around for more than 1 1/2 year and works most of the time (was terrible buggy initially)
* Entourage 2008 WSE was in limited public beta for almost 8 months before it was released (I was a beta tester and found the January release to be almost stable). MacBU stated that they worked closely togeather with the Exchange team
* Entourage 2008 WSE supports more features: public folders, Out of Office, Notes and Tasks in addition to at least some support for SharePoint (Microsoft Document Connection) with drag-and-drop (which I actually use quite a lot with my SBS 2008 box for sharing documents between my Mac and Windows 7 machine.
* Office 2007 file level compatibility with Word, Excel and PowerPoint, while iWork '09 (Pages, Numbers and Keynote) only sort of.
* Excellent support and a general openness about bugs. That is the support I know of, is mostly due to the MVPs Diane Ross and William Smith with Entourage. But you can log a case with MS in the worst case.
* Upgrade path to Outlook for Mac, which is announced for next summer.
And yes, upgrade to Mac OS X 10.6.1 Snow Leopard. No-brainer. It's mostly about highly optimized code, in addition to improved QuickTime, Spaces, Exposé and Docks. The reviews have been overwhelming, see for instance Edward Mendelson of PC Magazine:
http://www.pcmag.com/article2/0,2817,2352065,00.asp
For ressources:http://blog.entourage.mvps.org/
Jon-Alfred Smith
MCTS: Messaging, MCSE: S+M- FWIW I had a similar problem and at least discovered a work around:
One major difference is that my initial setup and install went fine and I was happily using SL Mail with Exchange 2007 until one day it stopped updating my sent items folder. All the other folders continued to work and to make things truly mysterious I discovered that mail that I sent from SL Mail was actually going out and a copy was on the server. I could confrm using a windows box and Outlook or even OWA on the Mac. It just wouldn't download the "newer" items to the SL Mail client
The Log error looked very similar to above:
Nov 11 09:49:59 Chuck-2 Mail[2501]: Exchange Sync: Unable to sync item id:AAMkAGFhODRkMWZjLTVhYmEtNDg4Yy05ZjMzLTllZWRmMGFjYzY5NABGAAAAAAC8LeP0aqWRRaiSbUh8D+UQBwAIWCEM6ocdRphnnFKi6rHWAAAyDjYAAAAIWCEM6ocdRphnnFKi6rHWACZKX+zFAAA= (item with incomplete headers)
It wasn't size per se because I know I have lots of folders that exceed 500 items and they were working.
Since I sort of knew when it stopped working I went for a brute force troubleshooting method. I simply started blowing away mail items on the server until I found the one that was choking the app. Nothing extraordinary about it and remember that Outlook and OWA never stopped working so I had to conclude that SL Mail is very sensitive or intolerant of something in the headers that the MS clients can tolerate.
Hope someone can make use of the extra diagnostic info. I stopped working on it when I got functional again. - Having the same problem. A million of these will pop up during a refresh cycle:
12/1/09 11:53:52 AM Mail[120] Exchange Sync: Unable to sync item id:AAMkADliODk3MjBiLWU3NjktNGU3Mi04ZTRjLTExOTFjOTQ1MjMzNgBGAAAAAADzGqUlFq2AQ4WOsyeUnwwdBwCftf/wotzzQb4vmP7EcQzmAAABE3FgAAAAXctrvNlsSJNl/3sHkIkNAAAA06HAAAA= (item with incomplete headers)
and then it'll end with this:
12/1/09 11:54:14 AM Mail[120] *** Assertion failure in -[EWSGateway _handleSyncedMessagesWithoutHeaders:inFolderIdString:store:newSyncState:], /SourceCache/Message/Message-1076.1/MessageStores.subproj/EWSGateway.m:760
Exchange Sync: Reattempting to sync folder:Trash — myname@example.com with folderId:AAMkADliODk3MjBiLWU3NjktNGU3Mi04ZTRjLTExOTFjOTQ1MjMzNgAuAAAAAADzGqUlFq2AQ4WOsyeUnwwdAQCftf/wotzzQb4vmP7EcQzmAAABE3FgAAA=
(
0 Message 0x00007fff84b67828 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff84b6778d -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff84abcea2 -[EWSGateway _handleSyncedMessagesWithoutHeaders:inFolderIdString:store:newSyncState:] + 1578
3 Message 0x00007fff84abe7f2 -[EWSGateway _syncFolderItemsFromTargetFolderIdType:syncState:forStore:includesLastItem:] + 818
4 Message 0x00007fff84abe015 -[EWSGateway syncFolderItemsFromFolderIdString:syncState:forStore:] + 494
5 Message 0x00007fff84ace209 -[EWSStore _fetchChangesFromServer] + 335
6 Message 0x00007fff84aa72d2 __-[EWSAccount _synchronizeMailboxesSynchronously]_block_invoke_1 + 389
7 libSystem.B.dylib 0x00007fff8137e0a8 _dispatch_apply2 + 44
8 libSystem.B.dylib 0x00007fff813111e9 _dispatch_worker_thread2 + 231
9 libSystem.B.dylib 0x00007fff81310b28 _pthread_wqthread + 353
10 libSystem.B.dylib 0x00007fff813109c5 start_wqthread + 13
)
One interesting note is that it says "folder Trash" -- I wonder if this has something to do with checking the "store deleted messages on server" box in account preferences?
My box is mostly syncing and has a lot of items, so can't track down a problem if there is one. My main complaint is that it seems to clog itself and will pretend that it's synced when in fact there's a message waiting for it.
