I have an Exchange 2013 SP1 on 2012 R2 and I get this warning migrating a users mailbox from 2010

Cmdlet cancelled. Cmdlet New-MoveRequest, parameters {TargetDatabase=XXXX, WhatIf=True, Identity=xxxxx BadItemLimit=3, BatchName=MigrationService:XXXX, CompletedRequestAgeLimit=7.00:00:00}.

I removed user info.

Looking here I see some similar postings but nothing in the way of an answer. It completes fine, no issues, but these warnings indicate something is off.

Any answer for this?

These are bad items (corrupt messages etc), I usually use -baditemlimit 50 when migrating between exchange versions.

It's likely the  client wouldn't be able to access these 3 items it's discarded anyway.

• Proposed as answer by Gareth Fletcher 10 hours 9 minutes ago
• Unproposed as answer by bateslabel 1 hour 1 minutes ago

Additionally I would look at Move Request Statistics Report to get more info on why it is getting failed....

Get-MoveRequest -Identity "YourMoveRequestIdentity" | Get-MoveRequestStatistics -IncludeReport | FL

There were no bad items. Those are the parameters of the request, I set it to 3. That is copied from the event viewer. The statistics report was clean as far as I can see. No bad items, nothing stalled, nothing failed. No errors at all. Total idle duration was 4 seconds, can't see how that would cause an alarm. Weird, completed 100% with no issues.

• Edited by bateslabel 8 hours 31 minutes ago

These are bad items (corrupt messages etc), I usually use -baditemlimit 50 when migrating between exchange versions.

It's likely the  client wouldn't be able to access these 3 items it's discarded anyway.

• Proposed as answer by Gareth Fletcher Wednesday, July 02, 2014 12:46 AM
• Unproposed as answer by bateslabel Wednesday, July 02, 2014 9:54 AM

There were no bad items. Those are the parameters of the request, I set it to 3. That is copied from the event viewer. The statistics report was clean as far as I can see. No bad items, nothing stalled, nothing failed. No errors at all. Total idle duration was 4 seconds, can't see how that would cause an alarm. Weird, completed 100% with no issues.

• Edited by bateslabel Wednesday, July 02, 2014 2:23 AM

Apart from above suggestions, Please also check all the given prerequisites in this library if you meet exactly with them before moving from exchange 2010 to 2013 :http://technet.microsoft.com/en-us/library/ee332309%28v=exchg.150%29.aspx

Few more references you can have a look at below that might be helpful to get rid from such issues soon :http://technet.microsoft.com/en-us/library/jj898583%28v=exchg.150%29.aspx

http://www.petenetlive.com/KB/Article/0000788.htm

Hi,

Based on my research, the warning may be caused by the disk storage performance on one of your Exchange servers. And here are some similar threads you can refer to:

http://social.technet.microsoft.com/Forums/en-US/00a48c77-3ddf-4d3b-b870-425a8a6e288e/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin

http://social.technet.microsoft.com/Forums/en-US/d93249da-22d9-496a-a5c0-529077ea33be/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin

Thanks,