How to Fix Exchange Jet Errors 1018 & 1216

Updated on July 3, 2019

Despite being the most widely used emailing platform, Microsoft Exchange is troubled by many errors. Often, these errors lie at the surface and are easy to resolve through simple fixes. However in some cases, like the ones we’re focusing on in this article, the errors lie at a deeper level and need more attention and efforts to completely resolve. These errors include Exchange Jet Engine issues which if not resolved soon are capable enough to corrupt the entire Exchange database file (EDB).

Moreover, to fix such issues for good, understanding them fully and eradicating the core causes behind them is necessary. Thus, let us begin by exploring what errors 1018 and 1216 mean, what are the reasons that trigger them and how to fix them. To grasp concepts better, let’s start with a brief description of how pages are organized in an EDB file.

EDB File Structure

Logically, an EDB file is a set of 4KB (or 8KB, 12KB, 16KB and so on) pages that are consecutively numbered. The entire database is organized in a B-Tree structure with one page pointing to the next adjacent page or the previous page. Such an organization facilitates faster page traversal and thus quicker search results. Out of approximately 200 pages in a single EDB file, the first two pages are occupied by the database header. So actually, the third physical page of the database is its first logical page.

In addition to the page number, page checksum value is also important. When the database is written to the disk, the page Checksum is calculated through a mathematical formula. The resulting value is written to the header page. While creating backups or performing other operations, the checksum is calculated again and matched with the previously stored value. If there is a mismatch, the page is considered to be corrupt.

Exchange Error 1018

Exchange error 1018 “JET_errReadVerifyFailure” generally occurs as a result of page-level corruption in the EDB file. While file-system level database damage can be fixed by Exchange server’s inbuilt utility, such help is absent for page-level corruption. Most commonly, this error happens during online backup creation.

Common Reasons Behind Exchange Error 1018 include:

  • Checksum recalculated during an operation on the database doesn't match previously stored value.
  • Error with the NTFS file system
  • Possibility of corrupt data being written to the hard disk or being written to an improper location.
  • Incorrect checksum calculation by Exchange server at the first instance can also lead to this error.
  • Creation of the correct checksum but writing it at an incorrect location may also cause this error.

How to fix Exchange error 1018

There are quite a few ways to fix Exchange error 1018. They've broadly been divided into 2 categories:

Manual method

1. Restoring from online backup

Restore database and Log files from an online backup (Exchange auto-ensures that the backup file is not corrupt by terminating the process if error 1018 occurs). This solution can be achieved by using any reliable media such as NTBackup or Windows Server backup.

2. Repair database with the ESEUTIL command

Use the command ESEUtil /p to discard the damaged pages. Before starting, take a backup of the database as it is. Then execute the command as follows:


After the process completes, make sure everything is fine by defragmenting the database to remove the spaces created because of removal of the damaged pages. This can be done through the Eseutil /d command as follows:


Finally correct the logical numbering of the pages through the ISInteg command as follows:ISINTEG –s servername –fix –test alltestsAlternate Solution

To overcome the shortcomings of manual methods such as requirement of technical knowledge, failure to have a recent complete backup etc., use third-party EDB repair tool Stellar Repair for Exchange. Read the section at last for more information about this product.

Exchange Error 1216

Error 1216 "JET_errAttachedDatabaseMismatch" occurs when header information assessment in log files and databases shows that some important files have been removed or substituted. This happens if a running storage group stops suddenly. Such a sudden stop leads to inconsistencies in almost all files of the database.

Reason Behind the Error

The main cause behind error 1216 is the sudden stopping of a running storage group. Thereafter, if on seeing this error, the administrator runs recovery method, the storage group will also start running again but with missing files. This will pose 2 issues – firstly, it might become nearly impossible to include the lost information in the storage group again; secondly, when the storage group starts the header information is examined by the system and if inconsistencies are found, error 1216 will be thrown again.

How to fix Exchange Error 1216

Again, the repair process here can broadly be divided into manual and automatic methods.

Manual Method

Here is the step-wise manual method to fix Exchange error 1216:

Step 1: Identify which files have inconsistencies. This can be done by executing the following command:

ESEUTIL /mh | find /i "consistent"

This command modifies a bit with Microsoft Exchange Server versions 2003 and beyond:

ESEUTIL /mh | find /i "Shutdown"

After the above command finishes its execution, check a sample of the output. It is important to note that all process logs must be available to recover the database successfully. If any log is missing, performing database recovery won’t be possible and the only option left would be to following these steps:

Step 2: Transfer all files that are missing (last Consistent logs) to a safe location and then restore the remaining files by mounting them.

Step 3: Restore the database from backup

Step 4: Repair the database.

To perform this, you need to run the ESEUTIL /p command, ESEUTIL /d command, and after that run the ISINTEG -fix command. The syntax for these commands is shown in the previous error’s section.

Alternate method

The above mentioned manual method though easy, doesn’t work in some cases. Thus, we recommend using third-party Exchange repair tool Stellar Repair for Exchange.

To sum it up

Exchange Jet engine errors 1018 and 1216 can be resolved in one shot with a single, worthwhile investment in reliable mailbox recovery software Stellar Repair for Exchange. This competent utility recovers emails, attachments, contacts, calendars, tasks, etc. from corrupt EDB files and enables a range of other features and facilities such as exporting recovered mailboxes to Live Exchange server or Office 365, saving recovered EDB in multiple formats including MSG, EML, HTML, RTF and PDF, searching mails from scanned EDB and more. Stellar Mailbox Recovery is bound to act as your data rescuer if these or any other difficult errors threaten to put a halt to your work.


Related Articles


How to Recover Exchange Database when Log files are missing

Updated on July 3, 2019 | Read Article


How to Repair Exchange 2010 database with Eseutil Switches

Updated on July 3, 2019 | Read Article


How to Resolve Exchange "Dirty Shutdown" Error

Updated on July 3, 2019 | Read Article


How to Restore Exchange 2016 Mailboxes Easily

Updated on July 3, 2019 | Read Article