[Fixed]: Too Many Transient Failure Retries – Object Not Found Error in Exchange Server

Summary: You may encounter various issues and errors when migrating from on-premises Exchange Server to Office 365. One such error is Too Many Transient Failure Retries - Object Not Found that occurs when migrating mailboxes from local Exchange to Office 365 using Cutover Migration method. In this post, we will see how to resolve this transient error in Exchange Server. We will also mention an EDB converter tool that can help migrate data from Exchange database (EDB) file directly to Office 365 without any errors or issues.

When migrating mailboxes from Exchange Server to Office 365 using the Cutover Migration method, you may face a situation where a migration batch stops during the processing stage and you get a transient failure error. The complete error message may look like:

Transient error CommunicationErrorTransientException has occurred. The system will retry (1/60)). Too many Transient Failure Retries Permanent Exception has occurred.

It seems the error occurs due to some mailbox objects not being found or corrupted items in the mailbox.

Below we will see how to fix the Too Many Transient Failure Retries – Object Not Found error.

Solutions to Fix Too Many Transient Failure Retries Error in Exchange Server

Here are some possible solutions to fix the transient error when migrating mailboxes using Cutover Migration from on-premises Exchange to Office 365.

1 – Increase the Bad Items Limit

You can increase the bad items limit to possibly 100, 200, or 500 and then try the migration again. To increase the bad items limit, you need to change the move request using the Set-MoveRequest command (see the below example).

Set-MoveRequest -Identity "<mailbox>" -BadItemLimit 100

If the issue still persists, then follow the next solution.

2 – Check for Corruption in the Mailbox

The migration may stop if there is corruption in a mailbox. So, check for corruption in the mailbox by using the New-MailboxRepairRequest command as given below.

New-MailboxRepairRequest -Mailbox <mailbox name> -CorruptionType SearchFolder,AggregateCounts,ProvisionedFolder,FolderView

This command will find and fix issues with the mailbox, if any.

To track the repair process, you can check the Event Log for the following entries:

• 10047: The MailboxRequestRepair process has started.
• 10048: The MailboxRequestRepair process is completed.
• 10049: The Mailbox or Database Repair Request Failed.
• 10050: A Mailbox is skipped from Repair task.
• 10059: Repair Request at Database Level has Started.
• 10062: Corruption is detected.

3 – Move Mailbox to Another Database

If the problem persists, you can try to move the mailbox to another database and then try the migration again. This helps to determine if the problem is related to that particular mailbox or the database hosting the mailbox.

4 – Create a New Target Mailbox and Change the Source

If the problem is still not resolved, then there is another way to resolve it. You need to first get some information about the mailbox, like the Exchange GUID and database. For this, use the below command:

Get-Mailbox "<mailbox name>" | ft displayname, Exchangeguid, database

Then, take a backup of the problematic mailbox by exporting it to PST using the New-MailboxExportRequest command.

New-MailboxExportRequest -Mailbox "<mailbox>" -Filepath "<unc path to pst>"

Next, create a new (empty) target mailbox and change the source to the new database. This will create a new mailbox for the user and disconnect from the current mailbox. It will preserve all the Active Directory attributes but will create a new empty mailbox for the same user.

Set-Mailbox "<mailbox name>" -Database <database name>

Wait for 15 to 30 minutes until the Active Directory is fully replicated across all the domain controllers and restore the source mailbox from the previous database to the new mailbox in the new mailbox database.

Now, run the below command to restore the source mailbox to the new target mailbox (created above) from disconnected mailbox.

Get-mailboxRestoreRequest -SourceStoreMailbox <guid number> -sourceDatabase <source database> -Priority high -TargetMailbox "<mailbox name>"

You can use the below commands to check the restore status.

Get-mailboxRestoreRequestStatistics Users/<user>\MailboxRestore

Get-MailboxRestoreRequest Users/<user>\MailboxRestore

After this process, the user will not be able to use the mailbox. So, after the restore is completed, delete the local Outlook profile and recreate it. This will fix the problem from the client side.

Now try to migrate the mailbox. It should be migrated with no issues.

An Easy and Effective Way to Migrate Mailboxes

To avoid errors, like the ‘Too Many Transient Failure Retries – Object Not Found’ and any other issues during migration, you can take the help of a specialized EDB to PST converter tool, like Stellar Converter for EDB. It is a powerful tool that can streamline your migration process.

With Stellar Converter for EDB, you can directly export data from the on-premises Exchange database (EDB) file to Office 365. This eliminates the need for intermediary steps, saving time and effort during the migration process. You can also export the EDB file data to PST and various other formats. The tool offers features, such as automatic mailbox matching and parallel exports that facilitate speedy migration of mailboxes.

Conclusion

The error ‘Too Many Transient Failure Retries – Object Not Found’ in Exchange Server can occur due to various reasons. Above, we have mentioned some possible solutions to fix this transient error. If the manual solutions fail to resolve the issue, you can use a specialized tool, like Stellar Converter for EDB for migrating data from your local Exchange Server to Office 365 without any issue.

Related Post