Easily fix various kinds of Exchange Server Jet Engine Errors
While working on Exchange Server, users face various kinds of Jet Engine errors which leave them in a state of confusion as they are not well aware about these errors or more often what is Jet Engine? Here we are going to tell you about what basically is Jet Engine, what causes errors in it and how to resolve such errors. To start with, MS Exchange Server uses ESE (Extensible Storage Engine) technology to function and to provide its services. This storage technology is also referred as JET Blue. This technology enhances the performance of Exchange Server as it stores and fetches data using sequential and indexed approach.
Now whenever any kind of corruption or damage is encountered in Exchange Server at file, database or application level, then it results in various kinds of Jet Engine errors which hampers your working with Exchange Server and restricts you from accessing files. Various kinds of Exchange Server Jet Engine errors and why they occur are briefly explained here:
» Exchange Error "1018 JET_err Read VerifyFailure": As the EDB file consists of 4 KB or multiple of 4 KB pages and these pages are organised in B-tree structure to enable quick results once a query is generated. Due to this B-tree structure, the first two pages of EDB file are occupied by Headers. Now when Exchange Server finds the checksum value (total number of pages) and it comes out to be different from the final recalculated checksum value obtained by the page read process then this Jet Engine error occurs. Other reasons could be:
- Checksum value calculated by Server is incorrect.
- Correct checksum is obtained but by mistake it is entered into an incorrect location.
- Corrupt data written on hard disk or any other incorrect location.
- There may be an error prevailing in NTFS file system.
» Exchange Error "1019 JET_err Page NotInitialized": In case you tried to access a particular page and it was found to be blank or unintialized in the Exchange database, then this kind of error is reported. The unavailability of such requested page is due to the corruption in file system which has ultimately damaged your Exchange database.
» Exchange Error "1022 JET_err DiskIO": This error generally occurs when Exchange Server tries to access the page number that exceeds the total number of pages. At the end due to these inefficient transaction activities, the Exchange Information store gets corrupted or damaged.
» Exchange Error "1216 JET_err AttachedDatbaseMismatch": During the assessment of header information in log files and assessment, if it is reported that some important files are removed or substituted then this error is generated. It happens when any running storage group is stopped suddenly which in turn resulted in inconsistencies amongst files of database.
There are also other reasons which could result in generating these kinds of different Jet Engine errors. Some of them are listed below:
- Corruption prevailing in Exchange database’s critical objects which in turn crashes the software.
- Power failure, hard disk crash etc hardware related problems damage the EDB file which was accessed at the particular instant.
- Unreliable third-party resource which was integrated with Server could result in false data restoration.
The repair and recovery process in order to get the access of corrupted file are very few and most of them are covered here. So from the described methods, user can choose any one depending on the level of corruption or all in case nothing works out.
Using ESEUTIL switches for repairing database
ESEUTIL is the repair and recovery process provided by Microsoft which searches out for your corrupted or invalid pages and delete them from your database. For this you just need to launch the command prompt window and then follow these instructions:
- ESEUTIL/P switch is to be used to resolve file-system level damage prevailing in the Server database by deleting the corrupted files. It is recommended to take backup before using this command.
- Use ESEUTIL/D command to make sure that after defragmentation or removal of corrupted files empty space which was left behind is removed properly.
- Finally correct the logical sequence of pages by using ISINTEG utility which removes the logical corruption in the database.
Restore from latest backup
Taking regular backup is always advised whenever you are doing any kind of work and hence if you are doing so, you can follow this restoring method. Here the database can be restored back in the original form by Exchange Server which performs recovery operation through transaction log files.
However in case you don’t have back up and the described method does not work then there is no other option left other then depending on a third-party Exchange recovery tool, which is professional in recovering the Exchange Server database and in repairing it if is corrupted.