I am in the middle of an export to pst using the new-mailboxexportrequest cmdlet Here's the command I used to kick it off. $export = get-mailbox; $Export|%{$_|New-MailboxExportRequest -FilePath "\\share.domain.com\pst\$($_.alias).pst"} All seemed to be going well, and I've exported 168 of 298 mailboxes, but now it seems hung, if I do a Get-MailboxExportRequest | Get-MailboxExportRequestStatistics to check the progress they're all either 100% and complete or 0% and queued. Has anyone else seen this? Can I kick this thing into gear? I need to get the rest of these MBxS exported ASAP! Any help is gratefully appreciated, Brian

Hi Brian, Do you have the same level of permissions over the problem mailbox as you do with the others that have already been extracted? Perhaps an obvious question but have you verified that there is enough disk space in the target area? Is the problem mailbox currently being accessed in any way by the end user? Is there any entries in the application/security/system logs that relate to the problem mailbox or process of extraction in general? Kind Regards GBF

Good questions all, I've got the appropriate level of permissions, file system is not full. To do: I'll check the eventviewer Follow Up Question: Would a user accessing their mailbox affect the ability of this cmdlet to export the pst? Thanks! Brian

Brian check out this thread and the resolution re MRS to see if it resolves you issue http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/efe49fc0-1cc3-456a-82e3-77250f6630cc BTW are you on SP1, SP1 RU2?? Troy Werelius www.Lucid8.com

Hi Brian, Would a user accessing their mailbox affect the ability of this cmdlet to export the pst? Potentially, especially so if the user was working in the mailbox at the time the extraction started. Is somebody logged into it? You can try the below powershell command to find out... Get-MailboxStatistics -Database “Database Name” | Format-Table DisplayName, LastLoggedOnUserAccount, LastLogonTime, LastLogoffTime Can you extract the problem mailbox on its own and extract it to a local location on the mailbox server? Kind Regards G,

So I just kicked off an individual export after checking the logoff LastLogonTime : 3/3/2011 5:45:55 AM LastLogoffTime : 3/3/2011 5:45:56 AM So he's not logged in right now, but it's just queued up. Name Status SourceAlias PercentComplete ---- ------ ----------- --------------- MailboxExport Queued amitchell 0 Any other ideas? BTW, thanks for the help --Brian

Did you check my post above?Troy Werelius www.Lucid8.com

Hey Troy, Just got your second ping, I'll check the URL you supplied. Here's the exchange version from the EMC Exchange Server 2010 Microsoft Corporation Version: 14.01.0270.001

So I've moved all of the pst files to a folder within that same share (I don't have another place to put them now). I've also created a new folder for the particular user whom I'm trying to export to PST right now, it doesn't appear to have changed the situation. This mail server set up does have a "replication partner" (still not familliar with the exch2010 yet) I'm not sure what the deal is, but in reading the other posts and the links from within the post you recommended I'm not sure that I can reboot the mailserver. Are there any services I might just be able to restart to kick this thing into gear? We're trying to just get these users exported so they can access their old email. We will not be importing these mailboxes back into another system. Thanks again Brian

Hi Brian, Out of interest can you use the EMC GUI to export the problem mailbox by right clicking the mailbox in question? This would require that you stop the previous attempts to migrate the mailbox obviously. If not then at this point if I would suggest that the problem mailbox is bypassed and that all other mailboxes are exported (to take any potential heat out of the situation). Are you aware of how to export all remaining mailboxes except the problem mailbox? In doing this we will also be able to verify that the target location is ok. Kind Regards

To be honest I wasn't aware that the EMC gui had that capability, I will certainly give it a try. However, it's not one problem mailbox, it's more like 130! So, just out of curiosity, how do you export through the GUI? It appears that there is a new move request local/remote, but neither of those accomplish my goal, which is just EXPORT to a PST file. I'm not migrating these mailboxes. We're exporting them and then retiring the server. Thanks Brian

Hi Brian, At this point I would suggest that the problem mailbox is bypassed and that all other mailboxes are exported (to take any potential heat out of the situation). Are you aware of how to export all remaining mailboxes except the problem mailbox? In doing this we will also be able to verify that the target location is ok. Kind Regards G,

In a last ditch attempt to remedy this issue I have rebooted the mail server and it still won't export the damn mailbox! Anyone? Bueller, Bueller...

Have you tried running a mailbox repair request? http://technet.microsoft.com/en-us/library/ff625226.aspxTroy Werelius www.Lucid8.com

Brian, The cause was that the mailboxes that failed to export (0% queued) belonged to databases in the DAG which had "suspended and failed" status for replication copies. By removing or fixing the replication status back to HEALTHY, the exports could then proceed. -jim

Thanks again Jim! I see you found my thread ;-)