Newly created move request remains in queued status forever in Exchange Server 2013 or Exchange Server 2016

  • Article
  • Applies to:
    Exchange Server 2013 Enterprise, Exchange Server 2013 Standard Edition, Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition

Original KB number:   3016284

Summary

When this issue occurs, you can run the Get-MoveRequestStatistics cmdlet to check that the mailbox is in the queued status. Because of resource constraints, the move request isn't picked up and queued. Follow the steps in the Workaround section to determine which resource may be causing this issue.

Workaround

For servers that have Exchange Server 2013 Cumulative Update 5 or a later-version update installed, run the following command to determine which resource may be causing this issue:

Get-MoveRequestStatistics -Identity <mailbox name> | fl Message

For servers that have an update that is earlier than Exchange Server 2013 Cumulative Update 5, run the following command to determine which resource may be causing this issue:

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

After you run these commands in your environment, the CiAgeOfLastNotification component is in a critical state. This state indicates that the content index isn't in a good status. In this case, follow these steps to reseed the content index for the database:

  1. Run the following commands to stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services:

    Stop-Service MSExchangeFastSearch
Stop-Service HostControllerService

  2. After the services are stopped, delete the Exchange content index catalog for the database.

  3. Run the following commands to restart the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services:

    Start-Service MSExchangeFastSearch
Start-Service HostControllerService

  4. After you restart these services, Exchange Search will rebuild the content index catalog. Finally, you can run the Get-MailboxDatabaseCopyStatus cmdlet to confirm the content index state.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to.

References

reseed the search catalog