We are running Exchange 2010 Enterprise SP1. I have to restore many mailboxes from backups for a litigation case. On several of the mailbox restores, I am getting status failed when I run the Get-MailboxRestoreRequest command. I get nothing in the event logs other than an event that says the cmdlet was successfully sent. When I check the mailbox that the data was restored to, I see mail, but have zero confidence that everything is there. How am I supposed to troubleshoot why a restore failed when exchange returns absolutely no information as to the cause of the failure? There has got to be a better way to monitor the progress of resotres than the Get-MailboxRestoreRequest command. It is extremely limited in the info it gives you and it's redundant for multiple restores making it almost useless to figure out which restore belonged to which mailbox. In fact, only 1 line lists the actual target mailbox in the list. I hope that I am missing something, because I am becoming less of a powershell fan every passing day.

There are a handful of options with the Get-MailboxRestoreRequest as you can see here http://technet.microsoft.com/en-us/library/ff829907.aspx is the command itself failing or is it saying a restore failed? BTW if you want to be able to extract data from an offline EDB check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp since it can open any offline EDB so that you can Browse, Search, or Export the entire contents or just the search results to PST, MSG and XML format or recover data directly to the original or alternate mailbox/server Troy Werelius www.Lucid8.com

After getting more info out of the command, here is the beginning text of the error: RunspaceId : 80e5b672-b4ba-4fee-ac27-6d8570faad3e Name : MailboxRestore Status : Failed StatusDetail : FailedMAPI SyncStage : CopyingMessages Flags : IntraOrg, Pull, Suspend RequestStyle : IntraOrg Direction : Pull Protect : False Suspend : True SourceExchangeGuid : 7f140f78-3c12-4e1d-855f-052dbe477741 SourceRootFolder : SourceVersion : Version 14.1 (Build 289.0) SourceDatabase : RDB1 MailboxRestoreFlags : Disabled, Recovery TargetAlias : recovery TargetIsArchive : False TargetExchangeGuid : e2b4555b-8069-4487-b376-9db09a5661f9 TargetRootFolder : TargetVersion : Version 14.1 (Build 289.0) TargetDatabase : DS09 TargetMailboxIdentity : mydomain.com/Users/recovery IncludeFolders : {} ExcludeFolders : {} ExcludeDumpster : False ConflictResolutionOption : KeepSourceItem AssociatedMessagesCopyOption : DoNotCopy BatchName : BadItemLimit : 0 BadItemsEncountered : 0 QueuedTimestamp : 5/24/2011 11:14:01 AM StartTimestamp : 5/24/2011 11:20:44 AM LastUpdateTimestamp : 5/24/2011 11:22:37 AM CompletionTimestamp : SuspendedTimestamp : OverallDuration : 23:34:50 TotalSuspendedDuration : TotalFailedDuration : 23:26:13 TotalQueuedDuration : 00:06:42 TotalInProgressDuration : 00:01:53 TotalStalledDueToHADuration : TotalTransientFailureDuration : MRSServerName : EstimatedTransferSize : 233.9 MB (245,271,540 bytes) EstimatedTransferItemCount : 3809 BytesTransferred : 121.9 MB (127,808,243 bytes) BytesTransferredPerMinute : ItemsTransferred : 2409 PercentComplete : 50 PositionInQueue : FailureCode : -2147024809 FailureType : MapiExceptionInvalidParameter FailureSide : Target Message : Error: MapiExceptionInvalidParameter: Unable to modify table. (hr=0x80070057, ec=-21470 24809) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=192] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=324][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropModifyRules [65] Lid: 17082 ROP Error: 0x80070057 Lid: 27745 Lid: 21921 StoreEc: 0x80070057 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropModifyRules [65] 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: 0x67F60040 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F60040 Lid: 48851 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F60040 Lid: 51077 dwParam: 0x80000000 Lid: 65267 Lid: 40691 Lid: 5559 StoreEc: 0x80070057 Lid: 65015 Lid: 65439 Lid: 4302 StoreEc: 0x80070057 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80070057 Lid: 29150 Lid: 20446 StoreEc: 0x80070057 FailureTimestamp : 5/24/2011 11:22:37 AM I saw an article that said it could be related to rules or the junk e-mail folder. Has anyone else run into this?

I have seen that happen and you can try to fix the problem by opening the problem mailbox with the MfcMapi utility and looking for suspect rules, i.e. rules with a blank name, funky characters etc. Open the problem mailbox via Outlook with the /CleanRules switch to see if that cleans issue. Add another rule to the problem mailbox which will force an update in the rules set in the mailbox. Troy Werelius www.Lucid8.com

I cannot open the mailbox. The database was restored to a recovery database and I am restoring from there. Is there a way to open mailboxes in a recovery database?

Right, sorry i was talking about checking the target mailbox? Are you placing the items into the original users mailboxes, a temp mailbox or?? Nothing from Microsoft, you would need to use a 3rd party product like DigiScope to do that from an OFFLINE database http://www.lucid8.com/product/digiscope.asp Troy Werelius www.Lucid8.com

Basically, what I am doing is restoring A user's mailbox to a dummy mailbox that I then export to PST. The dummy mailbox is empty when I start the restore.

have you been reusing the same dummy mailbox? if so then perhaps something remains in that MB from previous recoveries and deleting and then re-creating could resolve? If it is a fresh dummy mailbox then I am stumped and only other thing I could suggest is running eseutil /P against that offline EDB (and make sure its not your only copy in case it goes boom) and perhaps that will do the trick. Barring that I would open a case with MS to see if they have some additional special magic or use a 3rd party utilit Troy Werelius www.Lucid8.com

I am using a fresh dummy mailbox for each restore. I also ran a repair against the recovery database. It found corruption in 3 mailboxes, none of which I am trying to restore. I do have an open case with Microsoft at the moment and we'll see how that goes I guess. I will post updates as I have them.

Thanks for the update and let me know what MS has to say.Troy Werelius www.Lucid8.com

How is thing going on? If there is any progress or question, please feel free to post it here. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Any update with this? We are experiencing the same issue. Posting the outcome, if any, would benefit others. Thank you!

Typically when you can't open the mailbox it's because some msexch* attributes are mismatching or looking for an old value that is not there. On the dummy mailbox try editing the legacydn to that of the original mailbox. The convention should be the same except for the alias.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com