Published On - November 18, 2022 by Nasir Khan |Reading Time: 4 minutes
In the business world, Microsoft Exchange Server is a tried-and-true system. The administrator should be familiar with Power Shell Commands, but the product’s built-in security and user-friendly interface make migrating mailboxes from an Exchange setup simple. While the user is in the midst of the export process to create a backup of the Exchange Database, the mailbox may become queued up or otherwise unavailable. This blog post will show you how to Fix “Mailbox Export Request stuck in queued” error.
There are a variety of reasons why one might want to export a mailbox from the Exchange server, such as making a backup of a mailbox or exporting all messages from a specific year. To accomplish this, you will need to use the PowerShell command New-MailboxExportRequest with the – Identity parameter for the mailbox name and the -FilePath parameter for the UNC path you want to export the mailbox. Neither of these options is available in the Microsoft Exchange Management Console. If you have the correct permissions in the Exchange configuration and on the share where you wish to save your PST, exporting the mailbox should begin after you run the command.
Get-MailboxExportRequest is a PowerShell command that displays if an export request has been submitted, is currently being processed, or has been finished. Nothing will likely happen when you try to export a mailbox from your Exchange Server, and the status shows up as queued.
Methods to Solve Mailbox Export Request stuck in queued
First, ensure that both the underlying server and Exchange have the latest security patches installed. In addition to resolving a wide variety of problems, it enhances the app’s performance and eliminates numerous bugs while strengthening its security. If the problem persists after applying all available patches and service packs, consider cancelling the pending ExportRequest. In this case, you can use the following command, but keep in mind that it will delete any export request with a pending status, not only those whose mailboxes are now in that state. Launch the Microsoft Exchange Management Shell and input the following command.
Get-MailboxExportRequest –Status Queued | Remove-MailboxExportRequest
If the problem persists, you can try exporting the mailbox again using New-MailboxExportRequest. And again If the difficulty persists, further investigation will be required. If you have a Database Availability Group (DAG) and export requests are getting delayed in the queue, you should investigate the replication’s health. Any version of Exchange from 2019 back to 2013 is supported.
One further place to explore is the Exchange Application log, which can be accessed through the Microsoft Exchange Server Shell using the PowerShell command.
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics –IncludeReport |FL
This will help you narrow down the potential causes of the problem. The last resort would be to remove the export requests, restart the server, and try again. Having the user log into Outlook so you can access their mailbox and export from there is a tedious workaround that could compromise their privacy. Moreover, if a user’s mailbox has been disconnected, it will be necessary to create a new AD user and link the mailbox to the user, a process that can be time-consuming and annoying. If it doesn’t work, consider looking into a more dependable method for exporting your mailboxes quickly and easily with a single mouse click.
Method 3:Truncate Replication Cycle
Following the discovery of an Exchange Mailbox Export Request Stuck in queue, follow the steps below to get it processed.
First, pause the replication process by executing the command below:
Suspend-MailboxDatabaseCopy – Identify “DB1\servername’\
The following cmdlet can then be used to delete an existing data file:
Update-MailboxDatabaseCopy -Identity “DB1Servername” -DeleteExistingFiles
The third step is to be patient and wait till the procedure is complete. The wait time will be different for everyone, based on their mailbox size and connection speed. After the preceding command completes its execution, database replication can be resumed. In addition, we can use the following cmdlet to replicate data manually by running:
Update-MailboxDatabaseCopy -Identity “DB1\servername” -DeleteExistingFiles–ManualResume
Method 4: Using a DataMoveReplicationConstraint
Another approach to resuming a pending export request from a new mailbox in an Exchange 2010/13/16 setting. DataMoveReplicationConstraint must be set to “None.” So as to accomplish this, please refer to the steps below:
- As a first step, verify that “Second Copy” or “SecondDatacentre” is the value of the constraint. The format of the command is as follows:
Set-MailboxDatabase -Identity database name -DataMoveReplicationConstraintsecond copySet-MailboxDatabase-Identity databasename-DataMoveReplicationConstraintSecondDatacente
- Alternatively, if the aforementioned command is not accessible, you can use the following cmdlet: None
Set-MailboxDatabase -Identity databasename -DataMoveReplicationConstraint None
Method5: Use the most recent release
If the aforementioned steps do not fix the issue, likely, you are still using an out-of-date version of the exchange server. You should then rerun the application after updating it for optimal speed.
Method 6: Validating the DAG Environment
There are 16 exchange servers in the DAG, each with its own rules on handling failover and switchover. Separate progress checks by the administrator are required. The user must check the DAG replication policy if the Exchange Server is part of a DAG environment. The administrator can rapidly fix the “Mailbox Export Request Stuck in Queue” problem using this technique.
Words for attention: these manual approaches are not suggested for anyone without technical training. Because it just takes one false move to wipe out everything you’ve worked on.
Professional Tool to Fix Mailbox Stuck in Queued error
In addition to these hand-operated strategies, an automated instrument exists to deal with this matter. Regain EDB to PST Converter utility has been recommended by several Exchange administrators and MVPs. If you use this tool, you may easily and quickly convert EDB files to PST without any complicated procedures. The tool has an easy-to-follow procedure. Also, there’s even a trial version you can use to evaluate its features and compatibility.
The Regain EDB to PST Converter automates exporting mailboxes from EDB files to Office 365, so you don’t have to worry about doing so manually. There is no restriction on the number of mailboxes to export. Also, you can export from any version of the EDB file, from Microsoft Exchange 2019 to version 5.5. If you’ve restored an old EDB file and would like to export a mailbox to another mailbox in your system, you can do so by exporting to a live Exchange server. When you have this handy utility at your disposal, you won’t need to waste time with PowerShell or any other single-purpose programme.
We discussed both the automatic and the manual ways to resolve the Mailbox Export Request stuck in queued problem. Regain EDB to PST Converter is the best option if you need a fast fix. This programme can export mailboxes from EDB files to the more widely used PST format for use as a backup.