skip to Main Content

Move Exchange mailbox FailedOther stops at 95%

We have mailboxes migration going in Exchange Server. When migrating mailboxes in Exchange Server, we always hope to see the 100% completed messages. Sometimes we get FailedOther stops at 95% message in our Exchange migration. The move request did not complete, unfortunately. What should we do in this case?

Status detail FailedOther 95%

Run Exchange Management Shell as administrator. We like to check the move status of the mailboxes that are moving. We are going to make use of the Get-MoveRequest cmdlet. Let’s take the user John Doe with e-mail john.doe@alitajran.com as an example.

[PS] C:\>Get-MoveRequest | Get-MoveRequestStatistics

DisplayName StatusDetail    TotalMailboxSize                TotalArchiveSize PercentComplete
----------- ------------    ----------------                ---------------- ---------------
Neal Donna  CopyingMessages 56.97 GB (61,167,145,401 bytes)                  75             
Fox Marvin  CopyingMessages 93,93 GB (100,857,634,368 bytes)                 75
Doe John    FailedOther     23,17 GB (24,881,934,963 bytes)                  95

Have a look at the third line.

StatusDetail: FailedOther
PercentComplete: 95%

Options to fix FailedOther stops at 95%

We have two options to get the move request completed and not getting the FailedOther stops at 95% message.

  1. Remove the move request and start again with a BadItemLimit and AcceptLargeDataLoss flag.
  2. Change the parameter and resume the move request with a BadItemLimit and AcceptLargeDataLoss flag.

I prefer option 2 as the mailbox has already been moved. Removing and starting the move will only take bandwidth and time.

Option 1: Remove the move request and start the move request

Run the commands to remove the move request and start the move request.

[PS] C:\>Remove-MoveRequest -Identity "Doe, John"

Confirm
Are you sure you want to perform this action?
Removing completed move request "Doe, John".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): A
[PS] C:\>New-MoveRequest -Identity "Doe, John" -TargetDatabase "DB14-2016" -BadItemLimit "200" -AcceptLargeDataLoss
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to
the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox.

DisplayName StatusDetail        TotalMailboxSize             TotalArchiveSize PercentComplete
----------- ------------        ----------------             ---------------- ---------------
Doe John    WaitingForJobPickup 142.6 MB (149,559,487 bytes)                  0

It will start the move request from the beginning, this time you will not get FailedOther stops at 95% status.

Option 2: Resume existing mailbox move request

Run the commands to resume existing mailbox move request.

[PS] C:\>Get-MoveRequest -Identity "Doe, John" | Set-MoveRequest -BadItemLimit 200 -AcceptLargeDataLoss
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to
the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox.

[PS] C:\>Get-MoveRequest -Identity "Doe, John" | Resume-MoveRequest

Now it will resume the move request. Note that you can get an error when you run the second command. It will show the output: You can’t modify request ‘John Doe’ because it has already completed. This means that the mailbox already got moved after you did run the first command.

Verify the move request

Verify if the move request is proceeding or already is finished.

[PS] C:\>Get-MoveRequest | Get-MoveRequestStatistics

DisplayName StatusDetail    TotalMailboxSize                TotalArchiveSize PercentComplete
----------- ------------    ----------------                ---------------- ---------------
Neal Donna  CopyingMessages 56.97 GB (61,167,145,401 bytes)                  92             
Fox Marvin  CopyingMessages 93,93 GB (100,857,634,368 bytes)                 90
Doe John    Completed       23,17 GB (24,881,934,963 bytes)                  100

Have a look at the third line.

StatusDetail: Completed
PercentComplete: 100%

Final thoughts

You learned why you are getting the FailedOther stops at 95% in Exchange Server. There are a couple of ways to get past the FailedOther 95% status in an Exchange migration. With the commands shown in the article, you can proceed further.

Did you enjoy this article? You may also like Check Exchange health mailboxes. Don’t forget to follow us and share this article.

ALI TAJRAN

ALI TAJRAN

ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Read more »

This Post Has 0 Comments

Leave a Reply

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