Exchange appointment invite bounce back

You may want to look at how this user fixed the problem
https://www.experts-exchange.com/questions/26434118/Exchange-2010-mail-enabled-public-folders-550-5-2-0-STOREDRV-Deliver-error.html

Created a new mailbox database and tried to move the mailbox, left the option to 'skip mailbox' if corruption is found.  It made it 15% before failing.  I have the users mailbox up in Outlook 2010 and i'm exporting to a pst to play it safe.  What is the suggested method to proceed with now that the users mailbox is proven to have corruption?

Move the mailbox but specify a number of errors that are acceptable.  I usually use 49 (don't ask why) and that means it can drop 49 items without failing.  If that isn't enough raise the number and try it again.

Sounds like you have found corruption, so moving the mailbox will ensure it is left behind.

I really appreciate the quick response, I'll post the results for the sake of closure on this item.

You are welcome.  If that doesn't resolve the issue, please let us know.

Alan

Additional items, I tried to do a move and specified a number but unfortunately it still failed at 15% again.




1/29/2013 5:42:03 PM [Exchange01] The Microsoft Exchange Mailbox Replication service 'server.domain.local' (14.2.328.9 caps:07) is examining the request.
1/29/2013 5:42:03 PM [Exchange01] Connected to target mailbox 'Primary (94f9bacc-6afe-45e4-9062-d3971511c018)', database 'ExchangeMailDB', Mailbox server 'server.domain.local' Version 14.2 (Build 247.0).
1/29/2013 5:42:03 PM [Exchange01] Connected to source mailbox 'Primary (94f9bacc-6afe-45e4-9062-d3971511c018)', database 'Mailbox Database 1552018407', Mailbox server 'server.domain.local' Version 14.2 (Build 328.0).
1/29/2013 5:42:04 PM [Exchange01] Request processing started.
1/29/2013 5:42:04 PM [Exchange01] Source mailbox information before the move:
Regular Items: 27940, 7.703 GB (8,271,444,862 bytes)
Regular Deleted Items: 5866, 281.2 MB (294,819,114 bytes)
FAI Items: 64, 0 B (0 bytes)
FAI Deleted Items: 0, 4.473 KB (4,580 bytes)
1/29/2013 5:42:05 PM [Exchange01] Initializing folder hierarchy in mailbox 'Primary (94f9bacc-6afe-45e4-9062-d3971511c018)': 173 folders total.
1/29/2013 5:42:15 PM [Exchange01] Folder hierarchy initialized for mailbox 'Primary (94f9bacc-6afe-45e4-9062-d3971511c018)': 173 folders total.
1/29/2013 5:42:15 PM [Exchange01] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
1/29/2013 5:42:19 PM [Exchange01] Fatal error MapiExceptionJetDatabaseCorruption has occurred.
Error details: MapiExceptionJetDatabaseCorruption: Unable to synchronize manifest. (hr=0x80004005, ec=-1206)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=239]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=455][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropIncrCfg [112]
    Lid: 27962   ROP: ropUpldStStrmBegin [117]
    Lid: 27962   ROP: ropUpldStStrmEnd [119]
    Lid: 27962   ROP: ropUpldStStrmBegin [117]
    Lid: 27962   ROP: ropUpldStStrmEnd [119]
    Lid: 27962   ROP: ropUpldStStrmBegin [117]
    Lid: 27962   ROP: ropUpldStStrmEnd [119]
    Lid: 27962   ROP: ropUpldStStrmBegin [117]
    Lid: 27962   ROP: ropUpldStStrmEnd [119]
    Lid: 27962   ROP: ropFXSrcGetBufferEx [156]
    Lid: 17082   ROP Error: 0xFFFFFB4A
    Lid: 23137  
    Lid: 21921   StoreEc: 0xFFFFFB4A
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropFXSrcGetBufferEx [156]
    Lid: 23921   StoreEc: 0x3EC    
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67F60040
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x67EE0102
    Lid: 21970   StoreEc: 0xFFFFFB4A PropTag: 0x681C0003
    Lid: 49857   StoreEc: 0xFFFFFB4A
    Lid: 54569   StoreEc: 0xFFFFFB4A
    Lid: 52459   StoreEc: 0xFFFFFB4A
    Lid: 28292  
    Lid: 10213   StoreEc: 0xFFFFFB4A
    Lid: 28256  
    Lid: 9189    StoreEc: 0xFFFFFB4A
    Lid: 22500  
    Lid: 25058   StoreEc: 0xFFFFFB4A
    Lid: 22844  
    Lid: 3742    StoreEc: 0xFFFFFB4A
    Lid: 23296  
    Lid: 2526    StoreEc: 0xFFFFFB4A
    Lid: 20912  
    Lid: 24504   StoreEc: 0xFFFFFB4A
    Lid: 24148   StoreEc: 0xFFFFFB4A
    Lid: 23796  
    Lid: 2478    StoreEc: 0xFFFFFB4A
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849  
    Lid: 21817   ROP Failure: 0xFFFFFB4A
    Lid: 32758  
    Lid: 16586   StoreEc: 0xFFFFFB4A
    Lid: 22518  
    Lid: 28874   StoreEc: 0xFFFFFB4A
    Lid: 29516  
    Lid: 31820   StoreEc: 0xFFFFFB4A
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiManifest.Synchronize()
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceFolder.DoManifestSync(Boolean catchup, SyncContentsManifestState syncState, FolderChangesManifest changes)
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceFolder.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.EnumerateChanges(Boolean catchup)
   at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceFolder.EnumerateChanges>b__6()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.SourceFolderWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceFolder.EnumerateChanges(Boolean catchup)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CatchupFolder(FolderRec folderRec, ISourceFolder srcFolder)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.<>c__DisplayClass6.<>c__DisplayClass8.<CatchupFolderContents>b__5()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.<>c__DisplayClass6.<CatchupFolderContents>b__4(FolderRecWrapper destFolderRec, EnumFolderContext ctx)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CatchupFolderContents()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CatchupFolders(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: ISourceFolder.EnumerateChanges
OperationSide: Source
Primary (94f9bacc-6afe-45e4-9062-d3971511c018)
Catchup: True
--------
Folder: '/Shortcuts', entryId [len=46, data=00000000601E7108EE4FE642A5A609E2F720662D0100A8E4C60379E2D44389741D825C5E092E0000028CE9240000], parentId [len=46, data=00000000601E7108EE4FE642A5A609E2F720662D0100A8E4C60379E2D44389741D825C5E092E0000028CE9180000]
1/29/2013 5:42:19 PM [Exchange01] Relinquishing job.

Okay - time to dismount the store and repair, defragment and integrity check it.

eseutil  /p (to repair)

eseutil /d (to defragment)

isinteg -s servername -fix -test alltests (to integrity check - run at least twice).

Alan

Thoughts about moving any other mailboxes first?

You can try others, but not sure it will help in any way.

You were right, no mailboxes could be moved, I have a scheduled downtime on the server in an hour to start the recovery process.  I'll let you know how it goes.  Should I prepare for any data loss after running all 3 commands?

Question, as it seems the defrag is going to take another 15 hours to complete.  Is it requried that I run the isinteg immediately afterward or can I let the email system come back up and run for the rest of the business day to catch up and then bring it back down after business hours to run it?
Thanks again in advance for your help.  Also is there a way to add additional points for your continued help with this?

I would run them all together, one after the other so that you know you have make a good, clean, working database at the end, then let the users back on otherwise you may have to do it all over again, which wouldn't be much fun!

Repair
Defrag
Integrity check x 2 minimum

No additional points can be given beyond the max of 500 - but that's fine - I don't help people for the points :)  If you are desperate to - you would need to hit the Request Attention button and ask a Moderator to re-open the question and increase the points, then you can re-close and I would get more points, but that isn't necessary from my side of the equation.

Good to know, the defrag is done, consolidating the snapshot taken before moving forward with the isinteg, while researching I found information on New-MailboxRepairRequest which I wasn't aware existed.  Is that new cmdlet preferred to isinteg for my situation?

Follow up, I was unable to get ISINTEG to work.  I ended up using the New-MailboxRepairRequest -Database "Database Name" -CorrutptionType earchFolder,AggregateCounts,ProvisionedFolder,FolderView from the Exchange Shell
I had to mount the database to perform this command as recommended.  From viewing the Application log file on the server I am now monitoring as it goes through and cleans up corruption of all 4 types from each mailbox.  Absolutely amazing.  Will post results.