Exchange Mailbox Moves: ‘FailedOther’ Stops at 95%

KB ID 0001376

Problem

If you don’t see this happen at least once in a migration I would be surprised!

Exchange-Mailbox-Move-FailedOther-95-Percent

  • StatusDetail: FailedOther
  • PercentComplete: 95%

 

Solution

 You can remove the move request and start it again, with both a BadItemLimit and AcceptLargeDataLoss flag, (these might seem scary, but I’ve migrated many thousands of mailboxes, and never seen a problem.)

But the mailbox is massive and it had been moving for hours! OK, we can change the parameters, and resume the move as well!

Option 1 (Remove and Restart the Move)

Remove-MoveRequest -Identity user-name

New-MoveRequest -Identity “user-name” -TargetDatabase “target-mailbox-database” -BatchName “user-name” -BadItemLimit “200” -AcceptLargeDataLoss

Option 2 (Resume Existing Mailbox Move)

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Set-MoveRequest -BadItemLimit 200 -AcceptLargeDataLoss

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Resume-MoveRequest

PowerShell - Resume Move Request

The move should now restart/resume.

Exchange-Mailbox-Move-Statistics-Percent

Related Articles, References, Credits, or External Links

NA

Author: PeteLong

Share This Post On

2 Comments

  1. How can i move a disconnected mailbox from Exchange 2010 to Exchange 2013 without connecting that mailbox again ? We are retaining disconnected mailboxes for 365 days, so there s a lot of mailboxes that we don t want to loose. Thanks.

    Post a Reply
    • Try

      Get-Mailbox | ?{$_.ExchangeUserAccountControl -eq ‘AccountDisabled’ -and $_.database -ne “The-2013-Database-Name” } | new-moverequest -targetdatabase “The-2013-Database-Name”

      Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *