Experience Stellar's software with confidence! 100% safe to download.
Free Download For Windows

File Conversion

[Fixed]: Newly Created Move Request Remains in Queued Status

Summary:Sometimes, when moving a mailbox from one database to another, the mailbox move request gets stuck or remains in the queue forever. In this article, we will see how to resolve the move request remains in the queued status issue. We’ll also mention an EDB converter software that can directly export mailboxes from Exchange database file to another live Exchange Server database without any issue.

Free Download For Windows
Free Download For Windows
Table of Content arrow

    You may need to move or export mailboxes from the Exchange Server due to several reasons. When you transfer several mailboxes from one mailbox database to another in the same Exchange Server environment, the move request is initiated with the following command.

    New-MoveRequest -Identity "email address of mailbox" -TargetDatabase /destination database="" /destination

    New-MoveRequest -Identity

    After running the above command, the mailboxes will start exporting. To see the status of the move request (if it is in queue, processing, or completed), you can use theGet-MoveRequestcommand. When you run theGet-MoveRequestcommand, you will see the status of the move request asQueued.

    Get-MoveRequest

    After an hour, you re-run the command to get the move request status. You notice that the status of that specific move request is still in queue and nothing is moving. If you are running batches, it will be a bit difficult to pinpoint the exact mailbox which is causing the issue. You can use theGet-MoveRequestStatisticsPowerShell command to get more information and narrow down the investigation.

    Get-MoveRequestStatistics

    Let’s see how to fix the move request remains in queued status issue.

    Solutions to Fix the Move Request Remains in Queued Status issue

    Here are some solutions you can try to troubleshoot this issue.

    1. Move Another Mailbox

    你可以试着移动另一个邮箱。它可能没说完en that there is an issue with that particular mailbox and not the server or database. You can move a test mailbox or a system mailbox to confirm that it is not a universal issue. You can also try to move to another database as there could be an issue with the destination database.

    1. Remove the Move Request

    You can try to remove the current move request by using theRemove-MailboxExportRequestcommand in the Exchange Management Shell (EMS).

    Get-MailboxExportRequest -Status Queued | Remove-MailboxExportRequest

    这个命令将删除请求system. You can re-run the new mailbox move request to confirm if this was a one time case or there are issues underneath which are causing this issue.

    1. Check Event Viewer

    You need to check the Event Viewer on the server to ensure that if there are any specific issues with the Exchange Server, permissions, operating system, or hardware which are causing the move request remains in queued status. You need to also confirm that the source and destination have ample space to accommodate the new mailboxes.

    1. Restart Exchange Mailbox Replication Service

    There could be an issue with the Exchange Mailbox Replication service. You can restart the Microsoft Exchange Mailbox Replication service. This can be done via the following PowerShell command, using the Restart Service parameter.

    Get-Service MSExchangeMailboxReplication | Restart-Service

    Get-Service MSExchangeMailboxReplication

    Alternatively, you can go to theServicesManagement Console, find theMicrosoft Exchange Mailbox Replication Service, right-click on the service, and click onRestart.

    Microsoft Exchange Mailbox Replication Service

    1. Check Indexing

    Now, re-run theGet-MoveRequestcommand to see the status. If it is still queued, you can look at the indexing as there could be an issue with the indexing.

    Get-ExchangeDiagnosticInfo -Server /server name="" -Process MSExchangeMailboxReplication -Component MailboxReplicationService -Argument "queues= database name,pickupresults" /server

    Get-ExchangeDiagnosticInfo

    As you can see, theCiAgeOfLastNotificationcomponent is in the critical state. You need to restart the following Search components. For this, first stop the services (as given below).

    Stop-Service MSExchangeFastSearch
    Stop-Service HostControllerService

    After the services are stopped, delete the Exchange content index catalog for the specified database. Then, go to the location where the database is stored. You will find a folder with the name - CatalogData. Delete the folder. After the folder is deleted, start the services.

    Start-Service MSExchangeFastSearch
    开始营运HostControllerService

    Alternate Solution

    An alternate solution is to export the mailboxes using a third-party application, such asStellar Converter for EDB. With this application, you can easily open multiple Exchange Server databases of any size and from any Exchange Server version. You can granularly export to PST file and other formats. You can not only export mailboxes but also export user archives, disabled mailboxes, shared mailboxes, and even public folders with ease. You can also export directly to a live Exchange Server database or Office 365 tenant.

    In a nutshell, this application reduces the impact to the business at the minimum. It drastically reduces the conversion time, resources, and the administrative effort.

    progress
    76% of people found this article helpful

    WHY STELLAR®IS GLOBAL LEADER

    Why Choose Stellar?
    • 0M+

      Customers

    • 0+

      Years of Excellence

    • 0+

      R&D Engineers

    • 0+

      Countries

    • 0+

      PARTNERS

    • 0+

      Awards Received

    • TUV SUD ISO 27001
    • TUV SUD ISO 9001
    • NIST
    • HIPAA Verified