Forum Discussion
StefanoC66
Jan 09, 2025Iron Contributor
Move request falsely stuck
We are migrating mailboxes cross forest between two Exchange organizations and are having an issue with 3 of them.
We were migrating these 3 mailboxes when the target Exchange server had the log disk filling-up, and move request seemed to be stuck.
We extended the disk and the move actually completed, we check the get-moverequest for "non completed" and none was reported.
We move the mailbox database, on the target DAG, between the two hosts and then, not sure if it's related, the get-moverequest reported three entries in "waitingforjobpickup" even if the migrationa has successfully completed, the mailbox is active on the destination and users are connecting without issue.
How can we clear the status correctly or we just can delete the move request ?
thanks
SC
- 9rt8s-Copper Contributor
Found some answers to this in a few places....
Suspend-MoveRequest -Identity "<identity of move request>" Resume-MoveRequest -Identity "<identity of move request>"
if fails then try....
Remove-MoveRequest -Identity "<identity of move request>" New-MoveRequest -Identity "<identity name>" -TargetDatabase "<target database>" -BadItemLimit "20" -AcceptLargeDataLoss
or if all else fails start looking at AD / DNS etc; the following will query for more diagnostics to attempt to locate which component is causing the issue...
New move request remains in queued status - Exchange
Or restart the replication service
Get-Service *repl* | Restart-Service