<!-- /* Font Definitions */ @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1; mso-font-alt:; mso-font-charset:134; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 680460288 22 0 262145 0;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1; mso-font-charset:134; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 680460288 22 0 262145 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:SimSun; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:SimSun; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> Error occurred in the step: Moving messages. This mailbox exceeded the maximum number of corrupted items specified for this move mailbox operation., error code: -1056749110 I was prompt with above error message while migrating my exchange 2003 user to exchange 2007. Which is around 30% of my migration hit that problem. I'm understand that "skip the corrupted items" option may help to complete the migration of certain mailbox. But I don't wish to have user complaint that some of their mails were missing. Do anybody know what tool can check the mailbox healthy status or fix the corrupted message before the migration took place? Or methods to ensure mailbox migration is smooth?

Hi, I think you can use ISINTEG or ESEUTIL for these purposes so kindly check the article below which will guide you through out. http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html I hope this will help you. Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, Phone: +923008210320

Hi, There is no way to fix the corrupted messages. Although you could try to repair database, but repairing database is not fit for such a situation and not recommended at all. Repairing Exchange databases with ESEUTIL - when and how http://msexchangeteam.com/archive/2004/06/18/159413.aspx I suggest you use the backup to restore the problematic mailboxes into pst file and then import to Exchange 2007 server. Thanks, Elvis

Hi, There is no way to fix the corrupted messages. Although you could try to repair database, but repairing database is not fit for such a situation and not recommended at all. Repairing Exchange databases with ESEUTIL - when and how http://msexchangeteam.com/archive/2004/06/18/159413.aspx I suggest you use the backup to restore the problematic mailboxes into pst file and then import to Exchange 2007 server. Thanks, Elvis