Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move

Status
Not open for further replies.
M

M Yasir Memon

Hello Everyone, Good Day

We are transitioning Exchange 2007 SP2 to Exchange 2010 SP1, almost 3000 mailboxes, client access has successfully been transitioned to new CAS Array, HUB Transport Servers have also been introduced within the same AD Site, eveything works perfectyly including redirection of client access and mail flow. Now its the time to move mailboxes to exchange 2010 mailbox servers (DAG) but unfortunately when we move mailboxes we are getting following error with plenty move requests:

Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.

I understand there is some email corruption in the mailboxes, so i scheduled the downtime and ran ISINTEG tool with -fix and -test alltest switches, it took many hours to complete and also fixed many issues, with one database it showed almost 4000 Fixes !!!

Once ISINTEG completed, we mounted the Database and restarted the migration of mailbox but unfortunately still getting the same error " This mailbox exceeded the maximum number of corrupted items that were specified for this move request."

Is there anyway through which we can identify the actual corrpution and number of total messages which are corrupt within the mailbox? and how can we fix them permanently so that we can move mailboxes to Exchange 2010 with no data loss.

Soonest response is needed, will highly be appreciated.

Thanks and Regards

MYM
 
B

Brian Day MCITP

Did you run ISINTEG again to see if it had 0 errors/fixes? Sometimes it takes a few runs with ISINTEG before it fixes everything and still it is normal to have some bad items in mailboxes. How many bad items did you set the move to ignore?

If you use EMS and New-MoveRequest you can configure the BadItemLimit with a little more granularity and then accept data loss if you specify >50.

From TechNet for 2010 SP1: http://technet.microsoft.com/en-us/library/dd351123.aspx

The BadItemLimit parameter specifies the number of bad items to skip if the request encounters corruption in the mailbox. Use 0 to not skip bad items. The valid input range for this parameter is from 0 through 2147483647. The default value is 0. We recommend that you keep the default value 0 and only change the BadItemLimit parameter value if the request fails.

Note:

If you set the BadItemLimit parameter to more than 50, the command fails, and you receive a warning stating: " Please confirm your intention to accept a large amount of data loss by specifying AcceptLargeDataLoss." If you receive this warning, you need to run the command again, this time using the AcceptLargeDataLoss parameter. No further warnings appear, and any corrupted items aren't available after the move to the destination mailbox is complete.

Microsoft Premier Field Engineer, Exchange
MCSA 2000/2003, CCNA
MCITP: Enterprise Messaging Administrator 2010
Former Microsoft MVP, Exchange Server
My posts are provided "AS IS" with no guarantees, no warranties, and they confer no rights.
 
M

M Yasir Memon

Dear Brian, Thank You for the response,

Second time ISINTEG is being run now, I'll restart the migration of mailbox once it shows me the 0 fixes and let you know. however our clients requirement is to migrate mailboxes without any data loss, so is there any other effective way through which we can fix this corruption? and can we identify the actual number of corruptions per mailbox?

Kindly note that BadItemLimit has been specified as 0 item which is company requirement.

Regards

MYM
 
M

M Yasir Memon

Dear Brian, Thank You for the response,

I ran ISINTEG twise on the same Database and second time it showed 0 Errors/Fixes on all tests result, means there is no more corruption in database, however when i restarted the migration of mailbox i get same error " This mailbox exceeded the maximum number of corrupted items that were specified for this move request."

Kindly note that BadItemLimit has been specified 0 item as our client's requirement is to migrate user mailboxes without any data loss. Is there any other effective way through which we can fix this corruption? (although i havent seen anyother way so far) and can we identify the corruption / actual number of corruptions per mailbox? and one more thing what MS is considering corruption actually while there are no user complains about it.

If i select BadItemLimit 50, will it delete actual email / contacts / meeting items or what? please could you explain it.

Looking forward for the usual support and co-operation.

Regards

MYM
 
M

M Yasir Memon

Dear Brian, Thank You for the response,

I ran ISINTEG twise on the same Database and second time it showed 0 Errors/Fixes on all tests result, means there is no more corruption in database, however when i restarted the migration of mailbox i get same error " This mailbox exceeded the maximum number of corrupted items that were specified for this move request."

Kindly note that BadItemLimit has been specified 0 item as our client's requirement is to migrate user mailboxes without any data loss. Is there any other effective way through which we can fix this corruption? (although i havent seen anyother way so far) and can we identify the corruption / actual number of corruptions per mailbox? and one more thing what MS is considering corruption actually while there are no user complains about it.

If i select BadItemLimit 50, will it delete actual email / contacts / meeting items or what? please could you explain it.

One more thing i think should be adviseable to specify that our client is using Symantec Enterprise Vault for E-Mail Archiving, is there any possibility that move request is considering archived emails as corrupt?? if yes then what would be the way forward?

Looking forward for the usual support and co-operation.

Regards

MYM
 
B

Brian Day MCITP

Keep in mind ISINTEG is fixing corruption within the database, bad pages, messed up tables, etc., and this doesn't guarantee the actual data inside the DB will be 100% healthy. The user may have had a corrupt message for months/years and never new it because they didn' try to open it or its attachment.

If you set BadItemLimit to 50 then it will allow up to 50 messages to be bad before failing the move. If it only finds for example 35 bad items then the mailbox moves successfully and those 35 items are lost. If they were corrupt then the user probably couldn't work with them anyways.

Exchange has no clue about EV. If they're stubbing messages then all Exchange sees are tons of little tiny messages with a different message class within the mailbox and tries to move them like any other email.

A baditemlimit of 0 isn't extremely reasonable in my opinion. If they want to go that route then move as many mailboxes as you can with it set to 0, and then export the rest of the mailboxes with Outlook to PST, compare the item counts in store versus the PST, and see if there is a difference or not.

Microsoft Premier Field Engineer, Exchange
MCSA 2000/2003, CCNA
MCITP: Enterprise Messaging Administrator 2010
Former Microsoft MVP, Exchange Server
My posts are provided "AS IS" with no guarantees, no warranties, and they confer no rights.
 
Y

Yvel Guelce

I'm having the same issue with moving mailboxes to Exchange 2010. We're running coexistence between 2003 > 2007 > 2010, at the end we will only have Exchange 2010 in production. I was able to successfully move the user mailbox to Exchange 2007, but I can't get it to move to Exchange 2010, failing with the error message: " This mailbox exceeded the maximum number of corrupted items that were specified for this move request." I have tried Yasir suggestion: BadItemLimit 50 with no success.

Did you have any luck?

Thank you,
 
M

M Yasir Memon

Dear Yvel,

Sometimes it happens when some mailboxes contain more than 50 corrupt items while users doesnt even know about it, you can find out the number of corrupt items by getting the properties of failed move request (Number Of Corrupt Items) and also you can read detailed log on the log tab.

I would suggest you to specify -BadItemLimit 100 with -AcceptLargeDataLoss:$true and it should move because in the real world environment it will rarely reach 100 corrupt itema per mailbox.

If in case, some mailboxes reaches 100 bad items limit too, then you have two solutions, one to increase the limit to 150 or 200 and second to export the mailbox into PST File and fix it or use MFCMAPI tool to identify the corruption and delete it permanently. in cany case i would suggest you to increase the Bad Item Limit.

For me, i specified the same and encountered maximum 8 Corrput items in only one mailbox, and lowest was 1 corrupt item.

Dear Brian Day,

Thank You very much for the prompt response, but unfortunately my question is still unanswered that what and how microsoft is identifying an item as BAD while there is no user complain, and secondly how can we fix those corruptions as logically deleting those bad items should not be the ultimate solution (even though i havent seen any solution to fix them so far) and even still we cannot identify those bad items before migration.

Any update on this analysis would highly be appreciated.

Regards

M.Yasir Memon
 
J

JKhanMse

Hi,

How to change the default limit from 100 to any other higher number?
 
J

JeffL57

Hello all,

I am transitoning from exchange 2003 to exchange 2010 SP1 RU 1, the 2010 HUB, CAS and MBX servers are all in coexistance with the 2003 mailbox servers,. At present we are using the HUB and CAS arrays to handle the email. With reguards to transitioning mailboxes from 2003 to 2010 we have found that the 2010 move filters if allowed to accept baditem limits of 51 or more does cause issues with the larger mailboxes in that they have non functional Serach folders; non functional reminders; nonfunctional custom views; nonfunctional To-DO List and follow-up Flags. All are problems that have arisen using any Outlook client 2003;2007 or 2010 to access the newly migrated mailboxes. Note all of the troubled mailboxes were large mailboxes in size and did have a high rate of corrupted items. It seems this issue is directly related to the transition and affects the mailbox folder structure and not so much the data withing the mailbox.

Note: I have used every tool in existance to fix defrag and reached the 0 errors ratings and still had coruption errors and problems.
Jeffrey S. Lefever
 
Status
Not open for further replies.
Thread starter Similar threads Forum Replies Date
S Error message received saying mailbox has exceeded size limit on Office Professional Academic 2010. Using Outlook 1
P Error message received saying mailbox has exceeded size limit on Windows Vista Using Outlook 2
J Outlook - 2013 - Error msg when copying folders from Online Archives to another user's mailbox Using Outlook 0
A "Unable to display the folder" error when accessing Group mailbox Using Outlook 0
J Import/Export Mailbox issue Error: -2147467259 Exchange Server Administration 1
J Exchange 2010 SP1 fails at Mailbox Error Unable to load exrpc32.dll Exchange Server Administration 4
D Outlook 2003 is getting an error when trying to open an exchange 2010 mailbox Exchange Server Administration 5
Y error when installing mailbox role Exchange Server Administration 4
R Error attempting to create a mailbox for a new user Exchange Server Administration 4
A Sync error in exchange 2010 mailbox Exchange Server Administration 4
A Mailbox Error - Outlook 2010 - Temporaraly Removed Error Exchange Server Administration 2
S add mailbox database error Exchange Server Administration 5
K Error moving mailbox back to Exchange 2003 from Exchange 2010. Exchange Server Administration 5
K Exchage 2010 mailbox role install error Exchange Server Administration 18
S error message for recieving 08004210E -ERR[IN USE] mailbox Using Outlook 2
A Exchange 2010 sp1. When i dismount a mailbox database occur error in event viewer Exchange Server Administration 5
C Restore Mailbox Error in exchange 2010 Exchange Server Administration 6
J Exchange 2010 SP1 upgrade error when installing mailbox role Exchange Server Administration 5
A Error 0x86000108 after mailbox move from Exchange 2010 til Exchange 2003 SP2 Exchange Server Administration 3
J Exchange 2010 transport server error to exchange 2003 System Attendant mailbox Exchange Server Administration 2
S False error for exceeding mailbox storage limit. Exchange Server Administration 6
L LDAP server unavailable error while creating mailbox on EXchange 2010 Exchange Server Administration 6
D Error when installing Exchange 2010 SP1 at Mailbox role Exchange Server Administration 10
A Error with starting Exchange services (Address book and Mailbox replications) Exchange Server Administration 4
M Installing Exchange Mailbox role Error Exchange Server Administration 4
F Error mounting mailbox store 0x6d9 Exchange Server Administration 4
R Re: Move Mailbox Error Exchange Server Administration 2
A Exchange 2010 Mailbox role install error: You can't leave the EmailAddresses parameter value empty. Property Name: EmailAddresses Exchange Server Administration 5
D Error Message when creating Mailbox Database Exchange Server Administration 2
M Error Outlook Web Access is not currently available for the user mailbox that you are trying to acce Using Outlook 14
U Error after mailbox move... EVENT 10001 - MSExchangeIS Mailbox Store Exchange Server Administration 2
A ExFolders error: Cannot open mailbox Exchange Server Administration 1
J Re: Unable to access Mailbox after Remote move (Cannot open mailbox, Get-CalendarProcessing error) Exchange Server Administration 8
M Exchange 2010 Mailbox move error - Property Expression 'Jim Smith' Isn't vaild - FQE=A169C2C1 Exchange Server Administration 3
K Exchange 2003 - 2010 Mailbox Migration Error Exchange Server Administration 25
O Unable to update Mailbox SD in the DS. Mailbox Guid .... Error Code 0x8004010f (Archive Mailboxes) Exchange Server Administration 21
H Outlook 2019 Certificate error Using Outlook 0
V Date and/or time error in Outlook Form Outlook VBA and Custom Forms 0
A Run-time error '430' on certain emails when trying to set "Outlook.mailitem" as "ActiveExplorer.Selection.Item" Outlook VBA and Custom Forms 2
E Complite error on SaveAsFile method Outlook VBA and Custom Forms 3
I Error saving screenshots in a custom form in outlook 2016, outlook 365 - ok in outlook 2013, outlook 2010 Outlook VBA and Custom Forms 5
D Outlook VBA error extracting property data from GetRules collection Outlook VBA and Custom Forms 10
A Unable to save recurring Meeting to Documents folder due to error Using Outlook 2
M Compile error: User-defined type not defined Outlook VBA and Custom Forms 0
R Error when trying to forward current email item Outlook VBA and Custom Forms 7
M ERROR: None of your email accounts could send to this recipient Using Outlook 2
J OLADD.FAE Error When Exporting Contacts Using Outlook 6
C Send/receive error 80040119 Using Outlook 2
W error with the permission for the file Outlook VBA and Custom Forms 0
L Outlook 2019 MAC sync error after working for 4 hours Using Outlook 1
Similar threads


















































Top