There are many
reasons why one would export a mailbox from the Exchange server like exporting
a certain year or exporting a copy of a mailbox or someone who left the company
to have a backup. For this process there is no option on the Microsoft Exchange
Management Console and you will need to use PowerShell command
New-MailboxExportRequest with the – Identity parameter for the mailbox name and
the –FilePath for the UNC path where you want to export the mailbox to. After
you run the command while having all the necessary permissions in the Exchange
setup and on the share to store your PST, the mailbox should start exporting.
Though you can use the PowerShell command Get-MailboxExportRequest to see the mailbox export request status and whether the mailbox is in queue, processing, or completed. There are certain times that when you export a mailbox from your Exchange Server that you will see the status set as queued and nothing is happens. When a mailbox request gets stuck, you need to manually remove the request by using PowerShell command and try again. However, you can avoid such as situation and quickly export mailboxes from Exchange database to PST format by using an EDB to PST Converter software, such as Stellar Converter for EDB.
Methods to Solve Mailbox Export Request stuck in queued
1. The first thing to check is that the server underneath and the Exchange itself are fully patched and updated. Apart from solving a lot of issues, it improves the performance, fixes a lot of things and on top of this, upscale the security features of the application. If after you update the latest patches and service packs you still have the issue, one might try to remove the ExportRequest which is queued. This can be done by the command below, but note not all the mailboxes which status is stuck in queued as the command will delete any export request with the status marked as queued. This can be done by opening the Microsoft Exchange Management Shell and typing the following command.
After this you would start over the export of the mailbox using the New-MailboxExportRequest and see if the issue manifests itself again. If the issue persists, one would need to look deeper into the issue. If you have a Database Availability Group (DAG) you might look into the health of the replication since if the replication is not healthy you will have instances with the export requests being stuck on queued. This applies to Exchange 2019, 2016, 2013 and 2010.
2. Another thing one would look into is the Exchange Application log which can be viewed by running the below PowerShell command under the Microsoft Exchange Server Shell.
This will give you more insight on what could be the cause of the issue. Another drastic option is to delete the export requests, restart the server and try again. A painful solution to the problem is to have an Outlook with the attached mailbox and export from there, but it will take long and you would need the user to login on Outlook for you and might create some data privacy issue. Also, for a disconnected mailbox you would need to create a new AD user and connect the mailbox to the user which might take a little longer and frustrating.
Thou if all fails you might need to consider looking at a more reliable resource to export your mailboxes with ease and with just a click of a button.
It is possible by using a third-party application like Stellar Converter for EDB to have an easy tool which anyone can use with ease and practical in its way. The application runs very smooth and can be installed on either the server or on a Windows machine. With Stellar Converter for EDB you will be able to access the EDB file and browse through all the mailboxes and with a click of a button export the mailboxes you need to PST, EML, HTML and other formats. You can have a number of search filters you can use to customize you export. With this EDB to PST Converter Software you can also export Public Folders to PST and export from offline EDB and online EDB files without restarting of affecting your Exchange Server in any way or the need to dismount the store.
With the application you can also export directly the mailboxes from the EDB files to Office 365 without exporting and then importing as the application does all that on its own. There is no size limitation when exporting from any version of EDB database file being from Microsoft Exchange 2019 to 5.5 version and when exporting mailboxes, you can export one to many at the same time. You can also export to a live Exchange server for example if you restored an old EDB file and wish to export a mailbox directly to another mailbox in your system. Why would you bother in using PowerShell and other applications when you can have this multi-use tool to simplify your work?
Eric Simson is an Email Platform Consultant and is associated with Stellar Data Recovery from last 6 years. He writes about the latest technology tips and provides custom solutions related to MS Outlook, MS Exchange Server, Office 365, and many other Email Clients & Servers.