locked
ActiveSync fails after having to restore Exchange 2010 and running repair RRS feed

  • Question

  • Due to a failed array controller, I restored our mail server to a new host.  (We use VMWare ESXi 5.5).  After I brought the new <g class="gr_ gr_279 gr-alert gr_spell ContextualSpelling ins-del multiReplace" data-gr-id="279" id="279">vm</g> machine online, the database did not <g class="gr_ gr_322 gr-alert gr_spell ContextualSpelling" data-gr-id="322" id="322">mount</g> as expected.  I ended up have to run the <g class="gr_ gr_362 gr-alert gr_spell ContextualSpelling ins-del multiReplace" data-gr-id="362" id="362">eseutil</g> recovery.  All the exchange log files came back with no errors and the soft recovery worked.  I mounted the database and email flowed.  However, I have 2 mailboxes that will not <g class="gr_ gr_666 gr-alert gr_spell ContextualSpelling" data-gr-id="666" id="666">synch</g> to the device.  It fails with this error message:

    An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 

    URL=/Microsoft-Server-ActiveSync/default.eas?User=jrogers&DeviceId=ApplC39MJGM2FF9R&DeviceType=iPhone&Cmd=Sync
    --- Exception start ---
    Exception type: Microsoft.Exchange.Data.Storage.SyncStateExistedException
    Exception message: The sync state named 5 already exists.
    Exception level: 0
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.SyncState.CreateSyncStateFolderInFolder(SyncStateInfo syncStateInfo, Folder syncStateParentFolder, PropertyDefinition[] properties, Object[] values)
       at Microsoft.Exchange.Data.Storage.SyncState.CreateSyncStateStoreObject(SyncStateStorage syncStateStorage, SyncStateInfo syncStateInfo, Folder syncStateParentFolder, PropertyDefinition[] properties, Object[] values)
       at Microsoft.Exchange.Data.Storage.FolderSyncState.CreateSyncState(SyncStateStorage syncStateStorage, Folder syncStateParentFolder, ISyncProviderFactory syncProviderFactory, String syncFolderId)
       at Microsoft.Exchange.Data.Storage.SyncStateStorage.CreateFolderSyncState(ISyncProviderFactory syncProviderFactory, String syncFolderId)
       at Microsoft.Exchange.AirSync.SyncCollection.OpenSyncState(Boolean autoLoadFilterAndSyncKey, SyncStateStorage syncStateStorage)
       at Microsoft.Exchange.AirSync.SyncCommand.SyncTheCollection(SyncCollection collection, Boolean createSubscription, Boolean tryNullSync)
       at Microsoft.Exchange.AirSync.SyncCommand.OnExecute()
       at Microsoft.Exchange.AirSync.SyncCommand.ExecuteCommand()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    Inner exception follows below:
    Exception type: Microsoft.Exchange.Data.Storage.ObjectExistedException
    Exception message: Could not create folder 5.
    Exception level: 1
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.FolderCreatePropertyBag.CreateMapiFolder()
       at Microsoft.Exchange.Data.Storage.FolderCreatePropertyBag.SaveFolderPropertyBag(Boolean needVersionCheck)
       at Microsoft.Exchange.Data.Storage.CoreFolder.Save(SaveMode saveMode)
       at Microsoft.Exchange.Data.Storage.Folder.Save(SaveMode saveMode)
       at Microsoft.Exchange.Data.Storage.SyncState.CreateSyncStateFolderInFolder(SyncStateInfo syncStateInfo, Folder syncStateParentFolder, PropertyDefinition[] properties, Object[] values)
    Inner exception follows below:
    Exception type: Microsoft.Mapi.MapiExceptionCollision
    Exception message: MapiExceptionCollision: Unable to create folder. (hr=0x80040604, ec=-2147219964)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=60]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=244][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropCreateFolder [28]
        Lid: 17082   ROP Error: 0x80040604
        Lid: 25953  
        Lid: 21921   StoreEc: 0x80040604
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropCreateFolder [28]
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x3FE5000B
        Lid: 15348   StoreEc: 0xFFFFFA84
        Lid: 63733  
        Lid: 5079    StoreEc: 0x80040604
        Lid: 6255    StoreEc: 0x80040604
        Lid: 6511    StoreEc: 0x80040604
        Lid: 8047    StoreEc: 0x80040604
        Lid: 7310    StoreEc: 0x80040604
        Lid: 1750    ---- Remote Context End ----
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22417  
        Lid: 30609   StoreEc: 0x80040604
        Lid: 29073  
        Lid: 20369   StoreEc: 0x80040604
    Exception level: 2
    Exception stack trace:    at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiFolder.CreateFolder(String folderName, String folderComment, Boolean openIfExists, Boolean createSearchFolder, Byte[] folderId)
       at Microsoft.Mapi.MapiFolder.CreateFolder(String folderName, String folderComment, Boolean openIfExists)
       at Microsoft.Exchange.Data.Storage.FolderCreatePropertyBag.CreateMapiFolder()
    --- Exception end ---.

    We use Exchange Server 2010 SP3.  I have already checked to ensure that both accounts inherit permissions.  I also tried to just repair the mailboxes and Exchange <g class="gr_ gr_1212 gr-alert gr_gramm Grammar multiReplace" data-gr-id="1212" id="1212">comes</g> back with the mailbox is repaired.  Any other ideas?  I also tried to move the mailbox to a new .edb file, but the move request fails.  So I know there's some corruption to their mailboxes, just not sure how to fix it.

    Tuesday, May 19, 2015 2:02 PM

All replies

  • It's hard to say without knowing how you did the restore.  And even then, it might still be hard to say.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, March 2, 2017 6:12 PM
  • Please have a look here. This article has helped me to solve very similar problem
    Wednesday, April 5, 2017 2:12 PM