Resolve Exchange Jet Error 1018 & 1216 – Simple Solution
Microsoft Exchange Server is a widely used emailing platform which is utilized as on-premises software and software as service form. Despite its advanced features Exchange server is also popular for its Jet Error like Exchange Jet error 1018 and 1216. These Jet Errors cause various problems causing trouble at the deeper end. And if these issues are not treated correctly, then they can cause entire Exchange database file corruption.
Hence, to fix such errors and to eradicate the main reasons, you first need to understand them completely. Thus, let’s start with “Jet checksum error 1018” and “jet error Attached Database mismatch 1216” by grasping the concept of EDB files and Page organization.
Exchange EDB files Storage Architecture
EDB files in Exchange server database are organized in a B-tree structure where each page is pointing to the next and previous page. This architecture results in fast search outputs and easy traversal.
An alone EDB file consists of approx 200 pages with initial ones (two) are occupied by email header and the consecutive one is the first logical page.
Page checksum is another important aspect of Exchange Error 1018. This term comes in picture when you write the database over a disk. The checksum value is calculates using a mathematical formula and is included in the header page. Reason for calculating checksum is to crosscheck whether the page is corrupted or not.
This two concept will help you to understand and then troubleshoot Exchange error 1018 and Exchange jet error 1216. Now, lets take a look at both individually.
Exchange Jet Checksum Error 1018
A user can face this error with “Exchange error 1018 “JET_errReadVerifyFailure” message. This is causes due to page level corruption in EDB files. And this file system database corruption is caused due to following reasons:
- The recalculated checksum (created during an operation) does not match with the previous checksum value.
- Any error faced with the NTFS file system can also cause jet error 1018
- When checksum is calculated accurately but is written at an incorrect location
- Lastly, if the checksum calculated in the first instance is itself inaccurate then also Exchange “JET_errReadVerifyFailure” occurs.
Free Fix of Jet_errReadVerifyFailure checksum error 1018
- Restore files from online backup
Log files in Exchange server can be restored by using the online backup. Exchange server makes sure that the backup files are save from any type of damage if jet error 1018 occurs. This can be successfully achieved by using Windows Server Backup – a reliable media.
- Recover Database using inbuilt utilities.
Use Eseutil /p command which will repair the corrupted database and discard the faulty pages. And followed by /d command to defragment the database to remove the white spaces created after recovery. Before executing the following commands please make sure that you have a database backup.
This is not all, after successfully running the commands, you need to use another inbuilt utility ISINTEG. This utility will fix the damage at the application level.
ISINTEG – s servername –fix –test alltestsAlternate Solution
Exchange Error 1216
It is also encountered as Jet Error 1216 “JET_errAttachedDatabaseMismatch” and occurs due to changes made in header information of log files. Moreover, the database indicates that some of the important files have been removed. And the core reason behind this that the storage group must have been stopped suddenly.
Reason of the Error
The origin of Jet Error 1216 is the sudden shutdown or terminated storage group. The recovery of the database is considered to be the best solution. But if the log files are missing then 2 difficulties are faced:
- One is when it is next to impossible to restore the lost information back in the storage group.
- Another one is when header information is examined by storage group and again Exchange error 1216 is encounter in case of inconsistency.
Manual Solution For Jet Error 1216
Step-wise solution to resolve Exchange Error 1216 “JET_errAttachedDatabaseMismatch”.
Step 1: Locate the files facing inconsistency by using following commands
ESEUTIL /mh | find /i “consistent”
If you are using Exchange Server 2003 or above version then the following command is used
ESEUTIL /mh | find /i “Shutdown”
Now you need to check whether all log files are available in order to recover database files successfully. Otherwise, you need to proceed further.
Step 2: Move all missing files i.e last consistent log files to a safe location and then restore the remaining files.
Step 3: Restore the database with the help of backup.
Step 4: Finally restore and repair the database.
A Quick and Efficient Solution
Free solutions used to Fix Exchange Error 1018 & 1216 involves some precaution as their improper implementation will cause further damage to the Exchange database. Hence, it is more suggested to use a standalone application which is specifically designed for such situations. Many Softwares are available in the market which are intended to repair Exchange EDB files without compromising the data. Some of them provide a trial or demo versions to try and test the software with limited features.
Exchange Jet error 1216 and 1018 can be resolved by using manual methods but these solutions too have some limitations. To properly implement the repair commands, one need to have some technical expertise otherwise it will make the situation worse. In such situations, experts recommend using professional tools which provides more accurate results.