How to fix exchange JET Error 1018 & the JET Error 1216

In this article, we are going to discuss the causes of Exchange Server JET Error 1018 & the JET Error 1216, and the methods to fix them. MS Exchange Server is introduced by Microsoft for the act of Exchanging Emails. It is available exclusively for Windows Operating System. Microsoft Exchange Server is based upon JET engine or the ESE (Extensible Storage Engine). The Server is susceptible to various failures and Errors like any other server.

After discussing the JET Error 1018 & JET Error 1216 we can say that these errors usually occur in the exchange server database. However, the user can fix them with inbuilt utility. But still, some tools are recommended for a faster access.

Error 1018 jet_errreadverifyfailure

The Exchange JET Error 1018 arises when there is a page-level corruption in Exchange server database. If the user’s EDB file is corrupt at the page level then the 1018 jet_errreadverifyfailure checksum error occurs.

Reasons that might cause the JET Error 1018:

To manually resolve the 1018 jet_errreadverifyfailure checksum error follow these steps:

1. Mismatch in the value of checksum calculated at the time of writing transactions to the database & the checksum value stored in the header of the page.
2. Hard drive problems or the data might be written to an incorrect location on local drive
3. If the checksum value generated for a page is incorrect then, The MS Exchange server itself might behave abnormally and generate this Error

Resolve JET 1018 Error Manually:

1. Complete Database Restoration can be performed to restore the database to the previous stage where it was Error free. It can be achieved by using Windows Server Backup or the NTBackup.
2. ESEUTIL is an inbuilt switch to deal with the exchange server corruption problems. The “ESEUTIL/p” switch is the best way to fix the damage in Exchange Server data:

Once the broken files are removed from the Exchange database the defragmentation can be done to remove the white spaces left behind. The syntax for the defragmentation is “ESEUTIL/d”:

Eseutil 1216 jet_errattacheddatabasemismatch

The Exchange JET Error 1216 arises when some crucial data is missing from the header of the log file. If the soft recovery is run then it might be hard to incorporate wit the missing files and the eseutil 1216 jet_errattacheddatabasemismatch might show.

Reasons that Might cause JET Error 1216:

1. Abrupt disruption in running of a storage group
2. Mismatch in the header data of the log file

Fixing JET Error 1216 Manually:

The Exchange error “eseutil 1216 jet_errattacheddatabasemismatch” can be fixed with the inbuilt utility by following these steps:

1. The user can restore the Exchange Server Database with the help of eseutil.exe followed by the isinteg.exe. The method first fixes the damaged files and then performs integration & optimization.
2. Restoring the inconsistent files from an existing backup and then applying the ESEUTIL/p & ESEUTIL/d switch as discussed above.

Alternate Solution to Resolve the JET Error 1018 & the JET Error 1216

The above-mentioned methods do not work in some cases to fix the 1018 jet_errreadverifyfailure checksum error and the eseutil 1216 jet_errattacheddatabasemismatch. The ESEUTIL switch is complicated to use for a novice user. For Such users, EDB to PST Software is recommended.