Exchange 2013 Mailbox Move FailedOther

I am attempting to move 600 Mailboxes from my Exchange 2010 SP3 environment over to my Exchange 2013 environment all in all everything is going smooth Exchange is functioning properly. 

I have successfully moved half of my users in which I found a problem with 2 accounts. The move status shows "FailedOther" at 95% complete. I have been searching the google for 2 days now and I have not found a solution to this problem. The user account still shows that is on our old Exchange 2010 server. I have attempted to force restart the move but that fails and it says at FailedOther. 

Has anyone seen this problem before? My Environment is as follows

1 Server Mailbox server EMS - Mail box roles -  Specs 8 Procs, 14 GB of RAM running on a VM Server 2012 DC

1 Server Cas server - Client access server -  4 Procs, 12 GB Ram running on a VM Server 2012 DC

Exchange 2013 CU1 and all accumulative updates since CU1 release. 

I read some where this was because I didn't have enough resources for the move which I then bumped up the server to the current specs and rebooted the VM. I restarted the move with 

Get-MoveRequest | where{$_.Status -eq "FailedOther"} | Resume-MoveRequest

Do I need to remove this move request and start from the beginning or should this command work? 

June 5th, 2013 6:54pm

I actually figured out this problem on my own. 

I did this to resolve problem. 

Remove-MoveRequest -Identity username

New-MoveRequest -Identity "username" -TargetDatabase "MAILDatabase" -BatchName "Username" -BadItemLimit "200" 

My research shows that our EMS server lost connection to our 2010 Exchange server during the finalization of the move which caused the move to fail. As the last 5% of the move is the clean up process of removing the mailbox and all items off of the old mail server. 

I hope this information is useful to someone else. 

  • Marked as answer by peter16912 Wednesday, June 05, 2013 9:27 PM
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2013 9:27pm

Thank you very much for posting your resolution! We're 5 hours into a server migration and this just came up on the CEO's mailbox. I hadn't even gotten to start panicking when your solution came up. Thanks!!
June 28th, 2013 1:48am

hank you very much for posting your resolution! 
Free Windows Admin Tool Kit Click here and download it now
January 3rd, 2014 3:21pm

I actually figured out this problem on my own. 

I did this to resolve problem. 

Remove-MoveRequest -Identity username

New-MoveRequest -Identity "username" -TargetDatabase "MAILDatabase" -BatchName "Username" -BadItemLimit "200" 

My research shows that our EMS server lost connection to our 2010 Exchange server during the finalization of the move which caused the move to fail. As the last 5% of the move is the clean up process of removing the mailbox and all items off of the old mail server. 

I hope this information is useful to someone else. 


Incredible, that worked a treat. Many thanks for taking the time out to post this solution as about 10 of my 50mailboxes got to 95% and failed with this message and now they're working :)
July 2nd, 2014 11:05am

Or you could just do this if it was a huge mailbox and you didn't want to start all again:

Get-MoveRequest | ?{$_.DisplayName -eq "joebloggs"} | Set-MoveRequest -BadItemLimit 200 -AcceptLargeDataLoss
Get-MoveRequest | ?{$_.DisplayName -eq "joebloggs"} | Resume-MoveRequest

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2014 8:27am

Thanks, This solved a similar problem I was having with a mailbox.
May 5th, 2015 9:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics