Mailbox Move-Request FailedOther 95 %

Question

_{Monday, August 1, 2016 2:15 PM}

Hello,

during our migration from Exchange 2010 to Exchange 2016 I am moving step by step some mailboxes over form 2016 to 2016.

Now, while I am trying to move a specific mailbox I already got two times FailedOther with 95%. I found this post https://social.technet.microsoft.com/Forums/exchange/en-US/a51b223a-4a0d-468b-822b-9ae21aebbd71/exchange-2013-mailbox-move-failedother?forum=exchangesvrgeneral and tried "New-MoveRequest -Identity "username" -TargetDatabase "MAILDatabase" -BatchName "Username" -BadItemLimit "200"" - but still the same problem.

I cannot tell in detail what the exact problem is, is there any option to figure out why exacttely the move fails? Is maybe BadItemLmit 200 to less, or is there some other issue?

thanks,

Dieter

All replies (11)

_{Wednesday, August 3, 2016 3:04 PM ✅Answered}

Looks like I got the solution. If I fire "get-moverequest -movestatus Failed|get-moverequeststatistics|select DisplayName,SyncStage,Failure*,Message,PercentComplete,largeitemsencountered,baditemsencountered|ft -autosize", eventuall just Message as a filter since the error message can be pretty long and will be truncated than, I got "Error: An error occurred while updating a user object after the move operation. --> Either the primary or the archive mailbox exceeds the allowed quota. Primary Mailbox [Size: '5.495 GB (5,900,254,398 bytes)', Quota: '5 GB (5,368,709,120 bytes)']..."

This lead me to the database quota limit settings on new server, which was set to 4.9 GB. I have increased the quota and have resumed the Move-Request.
Now my move suceeded.

There is a great article related to how to figure out more about FailedOther reasons, see https://blogs.technet.microsoft.com/mikehall/2013/08/06/managing-failed-mailbox-move-requests/

_{Monday, August 1, 2016 6:04 PM}

Are you using the 'AcceptLargeDataLoss' switch as well?

Regards,

Fazal

_{Monday, August 1, 2016 6:37 PM}

No, never heard before about that switch. What would that mean? I dont want to loose too many mailbox items. At least I'd like to figure out which are corrupted and if possible delete or fix themprior to move the mailbox.

kind regards,

Dieter Tontsch

mobileX AG

_{Monday, August 1, 2016 7:09 PM}

Its a parameter used for higher BadItemLimit(s), Same as specifying  BadItemLimit, which means that the corrupted items would not be written to the destination DB.

Regards,

Fazal

_{Monday, August 1, 2016 7:35 PM}

Hi, thanks.

Is that supposed to be used together with BadItemLimit or  'AcceptLargeDataLoss' only? Is that kind of a switch which allows to move all moveable items as good as possible, all what is corrupted, damaged, will be kind of thrown away?

cheers,

Dieter

_{Monday, August 1, 2016 7:52 PM}

This is supposed to be used with BadItemLimit, As long as items are readable from the source, they would be moved, else discarded.

Regards,

Fazal

_{Tuesday, August 2, 2016 4:40 AM}

Hi Dieter,

Welcome to our forum.

Please clear all the existed move-request items before you run this move request.

We could run the following command before run move request:

New-MailboxRepaireRequest -Mailbox <username> -CorruptionType SearchFolder,AggregateCounts,ProvisionedFolder,FolderView 

In addition, please run the following command for specific database which hosts this specific mailbox:

Clean-MailboxDatabase <DatabaseName>

Best Regard,

Jim Xu

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Jim Xu
TechNet Community Support

_{Tuesday, August 2, 2016 4:55 AM}

As a workaround try move with -LargeItemLimit 50

Also try the command with -AcceptLargeDataLoss
https://technet.microsoft.com/en-us/library/dd351123(v=exchg.150).aspx

Also have a look at this blog post i.e. Exchange 2013 Mailbox Move “FailedOther”: http://jermsmit.com/exchange-2013-mailbox-move-failedother/

Hope this helps!

Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

_{Wednesday, August 3, 2016 10:09 AM}

Hi Dieter,

Is there any update for this thread?

If the above suggestions are helpful to you, please mark it as answer so that someone who has similar issue could find this thread as soon as possible.

Best Regard,

Jim Xu

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Jim Xu
TechNet Community Support

_{Wednesday, August 3, 2016 10:34 AM}

Yes, I just got the following:

after *"-BadItemLimit "200" -AcceptLargeDataLos"*s did not work either, I sticked to "-BadItemLimit "500" -AcceptLargeDataLoss -SuspendWhenReadyToComplete". Please note, I also increased BadItemLimit from 200 to 500.

This lead me to the fact that Move stopped aith AutoSuspend at 95%. But after I deleted suspend and resumed the move req. it again ended up at FailedOther with 95% Status.

No idea what else I can try.

kind regards,

Dieter Tontsch

mobileX AG

_{Monday, December 4, 2017 9:18 AM}

Thanks for sharing this , it definitely helped me as well,