Introduction to Mailbox Export Request Stuck Queued – Error

Moving mailboxes from Exchange environment can be an easy task if the Administrator knows the right method such as using PowerShell commands. But sometimes while using command new mailbox Export Requests, the process gets stuck or queued in Exchange 2016, 2013, 2010 and status viewed in Management Shell.

“Actually, I faced an issue while exporting data from Exchange Environment. I have 2 CAS servers, one is named mailbox_db1 and other titled as mailbox_db 2. I used New-MailboxExportRequest in order to move PST files from mailbox_db 1 server. It takes around 2 hours to export. After that, when I was trying to move exchange mailboxes. Then, I observed that my newly created Exchange 2010 mailbox export request is stuck in a queue with 0 % progress results. Do I have no idea why this situation occurs and how to fix this? If any of my technical friends know the resolving methods, then please provide the solution.”

Situation In Exchange 2010/13/16 where mailbox request stuck in Queued status needs a reliable and quick solution to resume process. In this article, readers will understand how to fix mailbox export request is stuck in queued status problem easily. Besides this, an alternate and simple way be also discussed in the below section.

Fix Exchange Mailbox Export Request Stuck in ‘Queued’ Status

At very first, users need to check whether the request is in Progress or Queued. For this, take the help of command: Test-ReplicationHealth

This command is used to check the progress status of Exchange Mailboxes Server in a Database Availability Group (DAG). This command can be either used from the local system or from the remote location for the Mailbox Server. In a case, when the status of Job shown as ‘Queued’ then follows below workarounds.

Approach 1: Truncate Replication Process

Once you realized that Exchange Mailbox Export Request Stuck in queued, then go through the below instructions to resolve it.

1. Run the below command to suspend the replication task first:

Suspend-MailboxDatabaseCopy – Identify “DB1\servername’\

2. After that, execution of the following cmdlet to remove an existing data file:

Update-MailboxDatabaseCopy -Identity "DB1\Servername" –DeleteExistingFiles

3. Wait until the process gets over. The waiting time depends upon the size of mailbox and internet speed. Once the execution of the above command is over, then restart replication of the database. Besides this, we have an option to perform manual replication using the following cmdlet:

Update-MailboxDatabaseCopy -Identity "DB1\servername" -DeleteExistingFiles –ManualResume

Approach 2: Use DataMoveReplicationConstraint to Fix Issue

Another solution to fix resume new mailbox export request queued issue in Exchange 2010/13/16 environment. You need to set DataMoveReplicationConstraint value None. To do this, follow the below instructions:

1. First, check that whether the value of constraint is Second Copy or SecondDatacentre. The command looks like this:

Set-MailboxDatabase -Identity database name -DataMoveReplicationConstraint second copy

Set-MailboxDatabase-Identity databasename-DataMoveReplicationConstraint SecondDatacente

2. If the above-mentioned command is available, then replace the command with following cmdlet: None

Set-MailboxDatabase -Identity databasename -DataMoveReplicationConstraint None

Alternative Solution – Automated Solution to Export Mailboxes

With Exchange Export Tool, no need to worry about mailbox export request stuck queued and PowerShell Commands of Exchange, view live progress report of exported items such as emails, contacts, calendars and other details. The software is developed in such a way that supports Exchange 2016/2013/2010 and below version perfectly. To know, how utility works, visit below steps:

1. Launch the software and provides appropriate information in the respective box. You need to type admin credentials, Live Exchange Server, AD IP, and Server IP. If you want to add sub-domain users, then check the box corresponding to Include Sub-Domain Users.

2. Next, click on the Login button. As soon as you select the option, all the mailboxes list in Sever will be displayed on the screen. You can clearly see the sub-domain users mailbox as well. Here you can select the mailboxes that you want to export. Then, click Next.

3. Here, you can select the Data folder, Split option, Maintain folder hierarchy option. Navigate to the destination location using Browse option. Finally, click on the Export option to begin the process.

4. You can clearly see a process of status report on the screen. If you want to save the report then click on Save Report.

There are some situations in which users have offline EDB file with them. At that time, they cannot export it with the help of the methods discussed above. Try SysTools EDB to PST Converter tool and export EDB to PST format in no time without any hassle.

Final Words

Most enterprises rely on the Microsoft Exchange environment. But no application is error-free and the same things happen to Exchange also. When users are importing PST files from the huge Mailboxes using PowerShell method, a problem is generated. And if one can realize Exchange 2010 Mailbox Export request stuck queued status, then use the above mentioned handy solutions. However, if you are unable to use the cmdlet to resolve the issue, then click on Exchange Export tool. It can easily move multiple mailboxes to Outlook PST at a single time without an error.