Blog Home » general » Resolve Error “This Mailbox Exceeded The Maximum Number Of Corrupted Items That Were Specified”
  Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Resolve Error “This Mailbox Exceeded The Maximum Number Of Corrupted Items That Were Specified”

Angelbrown Leka | March 3rd, 2015 | general

Instantiate a situation when you are migrating mailboxes from Exchange Server 2010 to another version, say Exchange Server 2013. At times, when a couple of mailboxes are migrated there are chances that some of them will display Failed status. When we go deeper into the details of the transaction, the following error message is encountered:

The above mentioned error disrupts the migration process and puts a halt to other mailboxes from getting migrated. As clear from the error message, Exchange server allows migration of a predefined number of mailboxes and exceeding this limit may lead to occurrence of this error.

exchange-recovery-new

Root Causes Behind The Error

  • As already discussed above, the error mainly arises due to exceed in the limit of corrupted mailbox during the migration process between Exchange Server 2010 and other versions of Exchange. This error is also observed during the migration between Exchange server and Office 365 with hybrid deployment facility.
  • The other reason which contributes in the occurrence of this error is Exchange Server being poisoned and has been quarantined. When the mailbox is tagged as poisoned it refers to the fact that either the attachments or the mail itself has got corrupted. When he poisoned mailbox is quarantined, it is placed in a separate queue and the healthy mailboxes are permitted to migrate. If the mailbox has been quarantined, then also you can experience the above error.

How To Overcome This Error?

There are a number of possible methods which can be taken into consideration so as to resolve error-This mailbox exceeded the maximum number of corrupted items that were specified”.

  • Using Power Shell Commands

You can resolve this error by increasing the limit of corrupted mailbox by making changes with Power shell commands.

  1. Run Power Shell as administrator.
  2. Enter the following command Get-MoveRequest.

The above statement will get all the mailboxes that have failed to migrate.

  • Set the maximum number of corrupted mailboxes limit to 100 in Set- Move Request.

It is to be noted that you will need AcceptLargeDataLoss switch if you are setting the limit of BadItems anywhere close to 50.

Drawback: This solution may corrupt mailboxes if the changes with the Power Shell commands are not done in a correct manner.

  • Remove Mailbox From Quarantine

The error can also be removed by removing the mailbox from quarantine state. This can be done by following steps:

Run the following command to get GUID of the mailbox.

    Get-mailbox-statistics-identity and press F1 key.

  1. Browse for the following registry and change the key that is mentioning GUID.

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Private-<db-guid>\Quarantinemailboxes\ <the mailbox guid>

  • After removing the guide restart IIS with following command

Iisreset

  1. Once the commands are entered the mailbox is not quarantined.

Drawback: This method should be considered as a last resort as it will disable the quarantine feature that prevents migration of corrupted and virus containing mailboxes. These mailboxes render performance issues in entire Exchange server.

  • Eseutil Utility

The command line utility of Exchange server, Eseutil can be employed in order to repair the EDB files. This may remove the above discussed error.

The following two tabs change content below.
My Twitter profileMy Facebook profileMy Google+ profileMy LinkedIn profileMy YouTube channel

Angelbrown Leka

Angelbrown Leka is a software developer by profession. She loves to write technical blogs over distinct topics pertaining to the issues of Exchange server and Outlook environment. She has earned certification in MCTS and her areas of specialization are MS Exchange server and Outlook platforms.