Hi, We are in the middle of moving mailboxes to Exchange 2010 SP1. During the mailbox move, some of the move are not successful because the corrupted items are above the -badItemlimit value. I tried to open the "mailbox" in Outlook 2007 and open the corrupted items. It opens OK. Any idea why this happening? Below is the content of the log file from the failed mailbox ============================================================================ 12/11/2010 11:38:45 PM [MAILBOXSVR] 'DOMAIN.COM/ADMIN' created move request. 13/11/2010 3:16:30 AM [CAS_HT_SVR] The Microsoft Exchange Mailbox Replication service 'CAS_HT_SVR.DOMAIN.COM' (14.1.218.11 caps:07) is examining the request. 13/11/2010 3:16:30 AM [CAS_HT_SVR] Connected to target mailbox 'Primary (c9a9a044-da79-443b-8f05-c67634208269)', database 'Tier 1', Mailbox server 'MAILBOXSVR.DOMAIN.COM' Version 14.1 (Build 218.0). 13/11/2010 3:16:30 AM [CAS_HT_SVR] Connected to source mailbox 'Primary (c9a9a044-da79-443b-8f05-c67634208269)', database 'SRC_SVR\First Storage Group\Mailbox Store', Mailbox server 'SRC_SVR.DOMAIN.COM' Version 6.0 (Build 7638.0). 13/11/2010 3:16:42 AM [CAS_HT_SVR] Request processing started. 13/11/2010 3:16:42 AM [CAS_HT_SVR] Mailbox signature will not be preserved for mailbox 'Primary (c9a9a044-da79-443b-8f05-c67634208269)'. Outlook clients will need to restart to access the moved mailbox. 13/11/2010 3:16:42 AM [CAS_HT_SVR] Source Mailbox information before the move: Regular Items: 493, 53.68 MB (56,288,442 bytes) Regular Deleted Items: 1, 405 B (405 bytes) FAI Items: 67, 0 B (0 bytes) FAI Deleted Items: 0, 0 B (0 bytes) 13/11/2010 3:16:42 AM [CAS_HT_SVR] Initializing folder hierarchy in mailbox 'Primary (c9a9a044-da79-443b-8f05-c67634208269)': 29 folders total. 13/11/2010 3:16:46 AM [CAS_HT_SVR] Folder hierarchy initialized for mailbox 'Primary (c9a9a044-da79-443b-8f05-c67634208269)': 29 folders total. 13/11/2010 3:16:46 AM [CAS_HT_SVR] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15. 13/11/2010 3:16:47 AM [CAS_HT_SVR] Stage: LoadingMessages. Percent complete: 20. 13/11/2010 3:16:50 AM [CAS_HT_SVR] Stage: CopyingMessages. Percent complete: 25. 13/11/2010 3:16:50 AM [CAS_HT_SVR] Copy progress: 0/548 messages, 0 B (0 bytes)/53.68 MB (56,286,834 bytes). 13/11/2010 3:16:50 AM [CAS_HT_SVR] Messages have been enumerated successfully. 548 items loaded. Total size: 53.68 MB (56,286,834 bytes). 13/11/2010 3:18:33 AM [CAS_HT_SVR] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox. <baditem errorType="MapiExceptionInvalidParameter" errorCode="0x80070057" flags="0x00000000" id="00000000CA7F643099AE854A9DD2E3B4FC34F82A0700FDF36D57FCC3B64ABACC9CF5498C8AD500000370F0070000D5C9D3DABB29B041AF9023E22FBA2B0B0000013704500000"> <folder id="00000000CA7F643099AE854A9DD2E3B4FC34F82A0100FDF36D57FCC3B64ABACC9CF5498C8AD500000370F0070000">Deleted Items</folder> <sender>Ian </sender> <recipient>Stephanie </recipient> <subject>Karinyup PS</subject> <messageClass>IPM.Note</messageClass> <size>158998</size> <dateSent>08/09/2010 01:52:28</dateSent> <dateReceived>08/09/2010 01:52:32</dateReceived> <errorMessage>MapiExceptionInvalidParameter: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80070057, ec=-2147024809) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=29737] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=685][latency=15] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropFXDstCopyConfig [83] Lid: 27962 ROP: ropTellVersion [134] Lid: 27962 ROP: ropFXDstPutBufferEx [157] Lid: 17082 ROP Error: 0x80070057 Lid: 31329 Lid: 21921 StoreEc: 0x80070057 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 32762 dwParam: 0x3D84B0 Lid: 32762 dwParam: 0x3F0102 Lid: 32762 dwParam: 0x4084B1 Lid: 32762 dwParam: 0x410102 Lid: 32762 dwParam: 0x4284B1 Lid: 32762 dwParam: 0x430102 Lid: 32762 dwParam: 0x4484B1 Lid: 32762 dwParam: 0x470102 Lid: 32762 dwParam: 0x510102 Lid: 32762 dwParam: 0x520102 Lid: 32762 dwParam: 0x57000B Lid: 32762 dwParam: 0x58000B Lid: 32762 dwParam: 0x59000B Lid: 32762 dwParam: 0x620003 Lid: 32762 dwParam: 0x63000B Lid: 32762 dwParam: 0x6484E4 Lid: 32762 dwParam: 0x6584E4 Lid: 32762 dwParam: 0x7084B0 Lid: 32762 dwParam: 0x710102 Lid: 32762 dwParam: 0x7584E4 Lid: 43207 StoreEc: 0x80070057 Lid: 8011 StoreEc: 0x80070057 Lid: 22282 Lid: 3625 StoreEc: 0x80070057 Lid: 25066 Lid: 31002 StoreEc: 0x80070057 Lid: 18154 Lid: 4073 StoreEc: 0x80070057 Lid: 28570 StoreEc: 0x80070057 Lid: 29738 Lid: 3401 StoreEc: 0x80070057 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80070057 Lid: 22630 </errorMessage> <errorContext>-------- Operation: IMapiFxProxy.ProcessRequest OpCode: TransferBuffer DataLength: 31680 -------- Operation: IMapiFxProxy.ProcessRequest OperationSide: Target Primary (c9a9a044-da79-443b-8f05-c67634208269) OpCode: TransferBuffer DataLength: 31680</errorContext> </baditem> =======================================================================

Hi, Looks like when the mailbox was in the process of moving it found a corrupted iteam. When move mailbox try to skip few number of corrupted mails and check are you ale to move the mailbox. You can only specify 50 corrupted mails to be skiped when moving mails using EMC. If the corrupted mails are more than 50 then you have to use EMS to move the mailbox with Baditemlimit. When using EMS you can provide more than 50 mails to be skip or even unlimited. Please refer to the below link for Mailbox move using EMS: http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/moving-mailboxes-exchange-2010-part2.html Thanks. Nagaraj N

Hi Nagaraj, I actually using EMS to move the mailbox (New-MoveRequest –Identity "user" -TargetDatabase 'Tier 1' -BadItemLimit '5'). What confuse me is I load the mailbox to Outlook 2007 and open the corrupted items including all the attachments without any problem.

If you want to keep the deleted item, then try and move it to a PST file so that the item can be deleted. Although given the item appears to be in the Deleted Items folder I wonder if the user wants to keep it at all. It is not unusual for Outlook to be able to open what Exchange calls a "corrupt" item, this may well be because the corruption is something that Outlook doesn't see. Not a lot you can do about it, other than extract the item. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi Sembe, Export the mailboxes to PST files is an option even it may take awhile considering the size of mailboxes (0.5GB - 5GB) and PST size limit. And the corrupted items exist in various folders (inbox, sent items, etc) At the moment , the best option is to export the mailbox to PST, increase the -baditemlimit then move the mailbox to Exchange 2010, read the log file and see what i ems are corrupted and try to recover this from the PST. Is there a utility that can quickly scan mailboxes for "corrupted items" without actually move it Exchange 2010 then report these items?

I am not aware of anything that will go through the process without actually moving the items. Exchange 2010 SP1 does introduce a mailbox level scan for corrupt items, but the content has to be on Exchange 2010 to do that. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Try do defrag database on 2003 Exchange Server, to see if it pop up anything. If you have any additional database on Exchange 2003 server, than try to move effective mailbox to different database from task on Exchange 2003 Server not 2010 server. Then try to move mailbox. When you open corrupted item in Outlook, are you opening it from Outlook cache mode or online ?

Hi Malistane, Offline defrag is not an option due to freespace limit . I did try to move the effective mailbox to diffrerent Exchange 2003 server. the move is completed successfull, however when I try to move this mailbox to Exchange 2010 , the move failed again with the same corrupted item . I can open the mailbox and the corrupted items from Outlook 2007/2010 without any issue and I test both online and cache mode from different PCs.

The only other think that come to my mind is that there must be something that scan massages, before they are written to store, it is highly unlikely, but ?

Hi, How large is the mailbox you are trying to move? I had a similar error previously because the max mailbox size on the exchange 2010 was less that what it was on exchange 2003 and the mailbox i moved was larger than allowed. The error I got was corrupted items, but after change the max mailbox size limit the mailbox was moved without any errors. /MartinExchange is a passion not just a collaboration software.

I realize this is an old thread, but we encountered a similar problem with mailbox move corruption and solved it mostly by using Outlook switches. During our first test mailbox moves from 2003 to 2010, if a mailbox reported corrupted items, we set the local move request to "Skip the corrupted messages" (typically with 5 for the "maximum number of messages to skip"). When we did that, the mailbox would often move, but then we encountered a problem with the To-Do bar and list. The To-Do list would display in cached mode, but it would not show up with cached mode disabled. We found that others had this same problem when forcing mailbox moves that encountered corrupted items (see especially http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/89902f00-4b84-4f10-b909-121a81241c85/ ). Most often for us, the corrupted items were default mailbox folders, especially search folders. (We could tell that the problem was with a default mailbox folder if the move failed at 10%; if it failed at a higher percentage, the problem was with individual corrupted items.) To clean corrupted items before moving mailboxes, we set up a new account with full access to the mailboxes reporting corruption, and then we ran Outlook switches on those accounts, one at a time. In about 80% of the corrupted mailboxes, /cleanfinders fixed the problem, and the mailbox moved without reporting any more corruption. For the remaining 20%, /cleanreminders and/or /resettodobar fixed almost all of them. However, on a few remaining mailboxes, we logged into them with MfcMAPI and deleted the “Reminders” or “Tracked Mail Processing” folders (*not* using a hard deletion). The mailbox moves were then able to complete without reporting corruption, and those users did not lose their To-Do bars. Users with individual messages or calendar items that were corrupted did not report To-Do bar problems when we skipped their corrupted mailbox items. (By the way, to fix missing To-Do bars, we either had people use cached mode in Outlook, or we opened their mailboxes in MfcMAPI and then performed a "hard (permanent/unrecoverable) deletion" of their "To-Do Search" folder in the mailbox's Root Container.)