Email Repair

How to Fix Exchange Jet Errors 1018 & 1216

Author: Ravi Singh | Updated on March 12, 2021 | Email Repair | Exchange Database Issues | 5 min read

Microsoft Exchange, the most widely used emailing platform, is prone to many errors. Often, these errors are caused by minor issues and can be easily resolved through simple fixes. However, some errors such as Exchange Jet errors 1018 and 1216, which we’re focusing on in this article, are caused due to severe Jet Engine issues and need more attention and efforts to completely resolve them. These errors, which if not resolved soon, are capable enough to corrupt the entire Exchange database file (EDB).

Moreover, to fix such issues for good, it is necessary to fully understand them and to eradicate the core causes behind them. Thus, let us begin by exploring about the errors 1018 and 1216, the reasons that trigger them and the solutions to fix them. To grasp the concepts better, first take a brief look on how pages are organized in an EDB file.

EDB File Structure

Logically, an EDB file is a set of 4 KB (or 8 KB, 12 KB, 16 KB 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, 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, it means the page is 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. Usually, this error happens during online backup creation.

Common Reasons behind Exchange Error 1018

  • Checksum recalculated during an operation on the database doesn't match with 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. You can try to fix the error by using the manual methods given below:

1. Restoring from Online Backup

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

2. Repair Database with ESEUTIL Command

Use the command ESEUTIL /p to discard the damaged pages. Before starting, take a backup of the database and then execute the command, as follows:

ESEUTIL /p

database integrity check

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

ESEUTIL /d

Integrity check completed

 

Finally, correct the logical numbering of the pages through the ISInteg command, as follows:

ISINTEG –s servername –fix –test alltests

Alternate Solution

TIP: To overcome the shortcomings of manual methods such as the requirement of technical knowledge, failure to have a recent complete backup etc., use third-party EDB Repair Tool such as Stellar Repair for Exchange.


Exchange Error 1216

Exchange 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.

Reasons behind the Error 1216

The main cause behind error 1216 is the sudden stopping of a running storage group. Thereafter, if the administrator runs recovery method, the storage group will also start running again but with missing files. This poses two issues:

  1. It might become nearly impossible to include the lost information in the storage group again.
  2. 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?

Here is the stepwise manual method to fix Exchange error 1216:

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

ESEUTIL /mh | find /i "consistent"

check inconsistencies

For Microsoft Exchange Server 2003 and beyond, modify the command as:

ESEUTIL /mh | find /i "Shutdown"

dirty shutdown

After the command is finished, 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. The only option left is to perform the following 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 ISINTEG -fix command. The syntax for these commands is shown in the previous error’s section.

Note: Though the above-mentioned manual method is easy, it doesn’t  Recover Exchange Database when Log files are missing & some severe corruption cases. So, you can use a third-party Exchange repair tool such as 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 a reliable Exchange mailbox recovery software such as Stellar Repair for Exchange. This competent utility recovers emails, attachments, contacts, calendars, tasks, etc. from corrupt EDB files. It has 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 Exchange Recovery tool is bound to act as your data rescuer, if these or any other difficult errors threaten to put a halt to your work.

81% of people found this article helpful