Some errors create obstacles in accessing the Exchange database. And the most common among them are Exchange Server Jet Errors. Here, we will discuss two main Exchange Jet error codes 1601 and 1605. We will discuss how these errors occur and how they can be resolved.

Jet Engine Error code 1601

This error is faced by Exchange Administrator when they try to access the Exchange database.

“Operation is terminated with error-1601 (JET_errRecordNotFound The Key was not found).”
Causes of Jet Error code 1601

The reason behind this error is Exchange database inconsistency. Also, Jet Engine Error Code 1601 usually occurs due to the reasons:

1. Exchange database files (EDB files) are highly corrupt.
2. EDB and STM files of the Exchange database have different structures.
3. You have a damaged Exchange database, and you are using incompatible Eseutil application for repairing the corrupted database.

Jet Engine Error Code 1605

This is a very common Jet Engine Error in Exchange database. This error may occur when an Administrator uses Eseutil application for repairing the database (using Eseutil /P).
“Operation is terminated with error-1605.”
Causes of Jet Engine Error Code 1605
This error may encounter if any user is using Eseutil application for Exchange recovery and during the process, Eseutil recreates an irregular B-tree structure. In such cases, the user may face error 1605.
Resolution for Jet Engine Error-1601 & 1605

To resolve errors mentioned above then there are three different ways:

1. Update MS Exchange server with the latest service pack
2. Recover data from the most recent backup.
3. Use a third-party EDB repair tool. You can use Exchange Recovery Manager as this tool has many amazing features.

Features of Exchange Recovery Manager Tool

The tool is integrated with many amazing features:

• Quickly repairs damaged EDB files and restores data to PST files.
• Exports Live Exchange mailboxes to Office 365 & vice versa.
• Migrates mailboxes, public folder, and archive mailboxes.
• Efficiently recovers permanently deleted mailboxes.
• Extract attachments from specific emails or the entire folder.
• Does not require MS Outlook while exporting EDB to PST.