So at this point I had but one reasonable option left, and it had been staring me in the face since I first saw the 10030 Event ID. Unfortunately, we were getting the same errors regarding the inability to reply to messages. In my case I deleted each of these devices & had the user delete their profiles & re-create them. Underneath the object you’ll find a container called CN=ExchangeActiveSyncDevices & underneath that you’ll find the various devices associated with that user.Įven if you use ’s ActiveSync test you’ll see an entry for that “device” listed here. I then drilled down to the user object in question. I opened ADSIEDIT (Start>Run>adsiedit.msc) & navigated to the Domain Partition (Default Naming Context). At this point I was pretty lost in terms of the logging available to me so I used an old trick, manually deleting the Device from underneath the User object in AD using ADSIEDIT (obligatory warning about using ADSIEDIT with care)
#Office 365 inbox not syncing with outlook 2013 download#
We were able to download mail items but whenever we tried replying to a message we were met with an error message. We definitely found corruption so I had the user try the sync again and it worked!…….partly…. Online integrity check for request ec853fb3-1999-4911-9782-5170a31a37cb completed successfully. Mailbox:4F1B824D-5C81-477E-B40B-418C888109F3 (John Smith)Ĭorruption Is Fixed FID Property Resolution Tasks=SearchFolder, View, AggregateCount, ProvisionedFidĬorruptions detected during online integrity check for request ec853fb3-1999-4911-9782-5170a31a37cb Mailbox level online integrity check for request ec853fb3-1999-4911-9782-5170a31a37cb started: To view the logs on Mailbox Repair Requests you need to head back to the Application Log in Event Viewer ( Reference )
The command lets you know the request was created but not much more than that. New-MailboxRepairRequest -Mailbox John.Smith -CorruptionType FolderView,ProvisionedFolder,AggregateCounts,SearchFolder
So in this case I ran the following command: So I immediately went to the handy replacement for ISINTEG, “New-MailboxRepairRequest”. The mismatched item was ignored.Īttempts may be made to rebuild the view, but if this message continues to persist for this mailbox, moving the mailbox to a different database may resolve the issue.įunction: EcPopulateInitialMsgViewTable(Search)Ī folder view which previously experienced consistency issues has been deleted and will be rebuilt the next time it is needed.Īfter seeing these events I came to the conclusion that there was logical corruption in this user’s Mailbox preventing ActiveSync from pulling the mail items down. Looking through Event Viewer in the Application logs led me to the following events from “MSExchangeIS Mailbox Store”:Ī mismatch was detected between a view of a folder and the actual contents of the folder. The customer said it was working fine until about a week previously. The odd thing was that the folder structure would come down but no mail items would be synched. One of our smaller customers running Exchange 2010 SP3 UR2 was having an issue with one particular mailbox being unable to download mail items via ActiveSync on any device.
0 kommentar(er)
