Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

Possible Resolution of the Exchange Jet Error 1601 & 1605

Mark Jonathan Smith | April 6th, 2015 | general

MS Exchange is one of the most trusted Email Server because of its fabulous functionalities offered to the different organizations. Exchange Database (EDB) is the file format in which it stores all its data. Minor Corruption in this database makes it completely inaccessible. In case of the corruption, Most Exchange Professionals advised to use Eseutil.exe utility which is provided by Microsoft. ESEUTIL is one of the suitable method can be used in case of minor corruption in the Database. But in case of major corruptions I will not recommend you to use ESEUTIL as it deletes the pages that are highly corrupted from the database and results in the information loss. In that case I would like to recommend you to go with a professional third party utility.

exchange-recovery-new

Consider a Scenario when you are repairing the Exchange Database due to the inconsistency in it. For this you have used Eseutil/p command to repair the Exchange Database the command terminates with the Error message given below:

Operation terminated with error -1605 or 1601

These are Jet engine error that generally occurs due to the Corruption in Exchange database. These errors make the Exchange Mailboxes inaccessible.

Below I have mentioned the main Causes and Possible resolution of the Jet Errors

Main Reasons of Exchange Server Jet Engine Error 1601

The Jet Engine Error 1601 generally occurs when you go to try to repair the Exchange Server by using the Eseutil utility.

This happens when you try to repair the Exchange Database using the incompatible Eseutil utility. For example, you try to repair the Exchange Database of Microsoft Exchange 2007 with the Eseutil utility of Exchange 2003 another possible reason for the same is a higher level of Corruption in the Exchange Database.

Main Reasons of Exchange Server Jet Engine Error 1605

This error occurs after the recovery operation performed by using the Eseutil utility, i.e the Eseutil has rebuilt the B-tree structure of Exchange Database in an improper manner.

Resolution of Jet Error 1601 & 1605

In case of Error messages above mentioned you need to repair the Exchange database as now they are inaccessible by the Exchange Server. You can’t repair it by using the inbuilt Eseutil utility as the error indicates that the EDB files are badly Corrupted. If you have the updated backup copy of Exchange Database then no need to worry, you can easily get back your data from an updated copy of backup, but what to do if you don’t have the updated backup copy of Exchange Server. Don’t worry, you can go with the professional tool that can help you in repairing Exchange Server database file & allow you to extract or export server data into PST & multiple other formats

Conclusion:

In this blog I have discussed the main causes and possible resolution of the Jet Engine error: 1601 & 1605. In case, if you are facing any issue regarding this error, feel free to comment

The following two tabs change content below.

Mark Jonathan Smith

Mark Jonathan Smith is a Tech. Blogger & he wrote posts on various topics related to Exchange Server & MS Outlook issues, conversion & migration. Mark is a MCITP certified & he continues focus on Active Directory, Exchange Server & Outlook.