If you are migrating mailboxes to Exchange 2010, then it is a possibility that you may have to face the following error –
This error will stop the migration process, and you may no longer be able to transfer the mailboxes. The cause behind the error is that the user mailbox may have more corrupt items than Exchange can handle. The Exchange can be configured to skip the migration when the number of corrupt items in a user mailbox exceeds the specified number.
If you have encountered a similar message, then you can follow the solutions mentioned below:
- Increase the limit of corrupted items allowed
Let’s suppose that the mailbox move request has a bad item limit set to 10. So, if the number of corrupt items is more than 10, then the move request will stop and give the error mentioned above. There is a simple set of commands, which you can run as an Administrator in the Exchange Management shell to increase the bad item limit. To do so, run the following command –Get-MoveRequest -Identity “Peter Helmsley”
This command will bring out the details of the move request created for the mailbox named Peter Helmsley.Set-MoveRequest -Identity “Peter Helmsley” -BadItemLimit 10
This command will increase the bad item limit to 10.Resume-MoveRequest -Identity “Peter Helmsley”
The move resume will resume the migration.
You can also choose to run a new move request with the help of command –New-MoveRequest -identity “Peter Helmsley” -TargetDatabase DB30209
After completing these changes, it is quite probable that you will not need to face the same error again. If the error persists, then you can go for another method.
- Use ESEUTIL command to repair the corrupt database
There is an inbuilt ESEUTIL utility which is used to fix minor corruption in the Exchange database. You can find it at –
This ESEUTIL tool has multiple switches which you can use as per the need. Some of the switches to tackle the error mentioned above are here –
- ESEUTIL /G – To check database integrity
- ESEUTIL /P – To repair corrupt database
- ESEUTIL /C – To run a hard recovery of the database
NOTE: Before running the ESEUTIL tool, you should backup your database.
First, dismount the database with the following command –Dismount-Database -Identity “
Now, run the following ESEUTIL Commandeseutil /g “Test Database 12345.edb”
This command will check the integrity of the database file and inform you about its health.
You can also run a command to recover the database.eseutil /p “Test Database 12345.edb”
If you are not able to remove the error or perform the migration, then it is wise to use a professional tool which will both repair the database and migrate mailboxes to the desired destination. These tools are embedded with advanced algorithm and scanning techniques, and hence they are highly proficient in repairing Exchange files facing any corruption issues – one reliable and effective tool for you is Kernel Migrator for Exchange, and the second one is Kernel for Exchange Recovery.
Tools to help you with the bad items in Exchange mailboxes
Kernel Migrator for Exchange reduces all the complexities of migration and provides you the best interface to migrate between any Exchange server versions. It is the best platform for Exchange-to-Exchange Migration. It has a separate option to increase the limit to skip the bad items for Exchange migration. You can easily use this option and save yourself from facing such error.