Pages

Monday, July 17, 2017

Mailbox Exceeded Maximum Number of Corrupted Items in Exchange 2007, 2010 & 2013


Mailbox Exceeded the Maximum Number of Corrupted Items Specified for This Move

If any user wants to migrate some presently existing email setup from 1 particular version to the other, then it is rather an intricate task requiring proper planning, expert execution, and timely testing for accomplishing it in a successful manner. Though available automated tools make this process simple, but there still are no. of things needing manual attention. Slight errors like: Has your Mailbox Exceeded the Maximum Number of Corrupted Items Specified for This Move in Exchange 2007, 2010 & 2013 can causes corruption of mailboxes. Also, some other complex errors can arise, hampering the process.

Exchange Move Error : Mailbox Exceeded Maximum Number of Corrupted Items

One such puzzling error that many users face while Exchange migration process is mid way shows the message:

“This-mailbox-exceeded-the-maximum-number-of-corrupted-items-that-were-specified-for-this-move-request”. 

When such error appears, it disrupts the migration till there is a handy solution. Migration stops temporarily, in turn, impacting users’ mailboxes present on server. So, at such time, solving such issue becomes top priority.

Causes of the Error: Mailbox Exceeded the Maximum Number of Corrupted Items in Exchange

  • As the error message is itself stating that if no. of corrupted mailboxes that are being migrated tends to exceed the set limit, then this error erupts. So, MS Exchange server basically allows only a limited no. of corrupted mailboxes for being a part of this migration. If this no. exceeds the limit, then the process gets paused in mid-way. 
  • If server is itself corrupted, then it must be isolated. Such an error appears under such cases as well. Corrupted mailboxes have corrupted mails as well as corrupted email attachments. Such mailboxes aren’t allowed to be migrated. So, if any issue is faced while isolating such mailboxes, server corrupts itself, leading to this error.

Some Manual Solution to Fix the Issue

Following are some of the manual methods that can help to solve error : Has your Mailbox Exceeded the Maximum Number of Corrupted Items Specified for This Move in Exchange 2007, 2010 & 2013

 1. Increasing Corrupt Mailboxes’ Limit Using Power Shell Commands 

  • Launch Power Shell
  •  Launch with administrator rights 
  • Type command Get-MoveRequest 
  • Press Enter 
  • All of the mailboxes, which had failed the migration, get listed
  •  Execute command “Set- Move Request” having value 100 
  • AcceptLargeDataLoss switch is needed if user is setting limit of “BadItems” somewhere close to value 50
 2. Identifying Mailbox’s Corrupted Items and Removing Those from Isolation

  • Fetch GUID of those mailboxes that are corrupted 
  • This can be done by executing command “Get-mailbox-statistics-identity”
  •  Now, press F1
  •  Search for the registry entry - HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Private-\Quarantinemailboxes\  
  • Change key that mentions GUID
  •  Restart IIS using command “iisreset”
  •  This would remove mailbox’s corrupted items from isolation to help solve the issue Has your Mailbox Exceeded the Maximum Number of Corrupted Items Specified for This Move in Exchange 2007, 2010 & 2013

 3. Repair Corrupt EDB Files Using ESEUTIL Administrators can use the built-in Exchange’s ESEUTIL, which is a command-line utility, for get back corrupted Exchange EDB files. This utility helps in hard and soft recovery of data from offline MS Exchange servers. For c corrupt Exchange databases, this ESEUTIL command has to be used with “/p” switch, which has to be followed by “Eseutil/d” command for defragmenting repaired databases. And finally, IsInteg command helps in checking integrity of databases.

Limitations of Manual Ways

For using Power Shell, one has to have some expertise in executing these commands. As any follies can make the damage even worse or can also cause permanent loss of data. The second method described above is definitely not a preferable workaround as it may turn off the feature of isolation, which might allow corrupted mailboxes to become a part of the process of migration. For using ESEUTIL, one must be having admin rights and technical know-how about using this utility.

A Recommended Solution

After being acquainted with the above mentioned three free fixes for resolving MS Exchange server problems & errors: Mailbox Exceeded the Maximum Number of Corrupted Items , users can leverage these as and when they require; but, the flipside of these manual ways is that they require technical know-how and expertise as a pre-requisite. So, for those who are under-confident about performing such technical commands and for those looking for non-lengthy, easy, speedy, safe and hassle-free solutions to recover exchange mailbox from edb by SysTools can be your final choice and the best bet!

The Bottom Line

The blog discussed about a particular MS Exchange error message: Has your Mailbox Exceeded the Maximum Number of Corrupted Items Specified for This Move in Exchange 2007, 2010 & 2013 arising at the of migration from 1 particular Exchange version to some other; then the causes behind such an error and some manual fixes for its solution, finally highlighting a powerful third-party software as the ultimate solution in this case. Though the manual fixes are surely free of cost and might work in some cases, but, they have their fair share of risks involved.

0 comments:

Post a Comment

Post a reply