New-MoveRequest stuck in queue

Question

_{Tuesday, September 24, 2019 9:16 AM}

Hello,

We are trying to move users mailbox & archive from a Exchange Server 2016 to another.

The two servers are up to date with CU13 from June 2019.

- Get-MoveRequest return : Status = Queued

- Get-MoveRequestStatistics return : StatusDetail = StallDueToTarget_ContentIndexing

- Get-MailboxDatabaseCopyStatus return : ContentIndexState = Healthy (for all database)

We find several topics about repairing the database index (stop MS Exchange Search services, delete ".single" folder, etc) or creating AD Group 'ContentSubmitters" but nothing is working.

Any suggestions are welcome !

Kind regards.

All replies (3)

_{Wednesday, September 25, 2019 7:10 AM ✅Answered}

Hi Kyle Xu,

We had tried few days ago to disable the indexing with the same cmd but no result.

Great news, the move process is now working after correct the error "MSEXchange ADAccess Event ID 4127" on the target server.

Regards.

_{Wednesday, September 25, 2019 2:47 AM}

Hi,

Does this phenomenon occur on all mailboxes or just one mailbox?

Does it occurs on new created mailbox?

>> - Get-MoveRequestStatistics return : StatusDetail = StallDueToTarget_ContentIndexing

From the above information, we can know this issue is related with database index. So, if this phenomenon occurs on all mailboxes, I would suggest you use command below to disable source and target database's index temporarily. Then try to migrate this mailboxes again:

Set-MailboxDatabase "Source/Target database" -IndexEnabled:$False

Regards,

Kyle Xu

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, September 25, 2019 9:46 AM}

Glad to see that your problem has been solved now. Thanks for your sharing.