Error Mailbox Export Request Stuck Queued [Fixed]

Moving mailboxes from the Exchange can be a simple task if the Administrator is aware of using PowerShell commands. Besides, sometimes while using the command new mailbox export request, the process gets held in Exchange 2016, 2013, 2010. As status seen in Management Shell. Situation In Exchange mailbox export request stuck queued status requires a secure and quick solution to continue the process. In this article, readers will learn how to fix mailbox export request stuck in progress which are in queued status.

4 Methods to  Fix Exchange Mailbox Export Request Stuck Queued Status

There are multiple solutions to fix this error. Besides, it’s not mandatory that every solution will work in your case. So, you’ll have to try every solution to get out of this issue.

1. By Updating the Exchange Version

Sometimes, this problem might arise due to an old version of Exchange Server. So, you’ll have to keep your Exchange Server updated to enhance its appearance and reduce such issues automatically. Also, you get better preservation, management, and versatility with the updated versions of Exchange. Updating Exchange Server might fix the “mailbox export request stuck queued” issue. Though, if it doesn’t, then you can apply the below-mention methods.

2. Verify whether the Exchange Server is in DAG Environment

The mailbox export request is used to review the progress of the Exchange mailboxes server in the DAG context. So, you’ll have to verify if the Exchange Server is in the DAG context or not. If it is in DAG, then you’ll have to confirm the DAG replication is in a stable state. Moreover, there are no concerns associated with DAG. Using this method can also fix the queued issue in Exchange 2010, 2013, 2016.

Also Read – Migrate Windows Live Mail to Outlook 2016 and 2013

3.  Use Data Move Replication Constraint to Fix Issue

Another solution to fix the new mailbox export request queued error in Exchange 2010/13/16 circumstances. You require to set the Data move replication constraint value None. 

To do this, follow the below instructions:

1. Firstly, check whether the value of constraint is Second Copy. The command seems like this:

Set-MailboxDatabase -Identity database name -DataMoveReplicationConstraint 

second copy

2. Secondly, If the above-mentioned command is there, then succeed the command with the next cmdlet: None

Set-MailboxDatabase -Identity database name -Data move replication constraint None

Applying this method, you can also fix the mailbox export request stuck queued issue in Exchange 2010, 2013, 2016.

4. Prune Replication Process

One of the efficient and prosperous methods to get out of this error is to suspend the replication task first.

Apply the below command to suspend the replication task.

Suspend-MailboxDatabaseCopy – Identify “DB1\servername’\

Now, extract the existing data file with the below command.

Update-MailboxDatabaseCopy – Identity “DB1\Servername” – DeleteExistingFiles

Wait for the command to execute. After the cmdlet is executed, restart replication of the database. You can also conduct manual replication with the below-mentioned cmdlet.

Update-MailboxDatabaseCopy -Identity “DB1\servername” – DeleteExistingFiles – ManualResume

After completing these steps, you will not face the stuck in queued error. However, if the matter still exists, then you’ll use the below methods.

Limitations of Manual Methods

Well, implementing the above manual methods might resolve some issues. Besides, there are some more limitations in it, such as:

• These methods are not perfect for all Exchange versions.
• You can not migrate maximum mailboxes with these methods.
• Performing also can end in the loss of mailboxes data, or it can disturb the hierarchy of mailboxes.

So, to deal with these limitations, there is an alternate solution (Professional approach) that doesn’t involve using the new mailbox export request for exporting Exchange mailboxes. 

Professional Approach

The above manual has its limitations and also there is a risk of file data corruption. To avoid these types of corruption, you can opt for the professional approach. The professional method consists of software i.e, EDB to PST Converter. Moreover, it can easily remove the inconsistency from the EDB file by converting them to PST file format. Besides, it is designed with a user-friendly GUI which makes it easy to handle even for novice users.

Conclusion

Migrating mailboxes from Exchange is essential to keep the data safe. However, many users face the new mailbox export request stuck queued error with the manual approach. So, here we have mentioned some useful solutions to get out of this issue. Also, we have suggested a third-party tool that enables users to migrate Exchange mailboxes indirectly.

Also Read: Error Fixed: Outlook Mailbox Size Not Reducing After Archive

Related Post