Many times while working on MS Exchange Server, users face various error issues that create a hurdle in the working flow. Out of which one such error is Exchange error 1018 that mainly arises when the database is corrupted on page-level. MS Exchange Server has an in-built facility that makes easy in determining as well as fixing any damages that takes place in Exchange database at level of file-system.
If an EDB data file is corrupted at page level then, it is usually hit by Exchange Jet Error 1018 JET_errReadVerifyFailure. This error mainly occurs at the time of online backup creation.
Causes Behind Occurrence of Exchange Error 1018
There are some reasons due to which user’s face the Exchange (2007, 2010, 2013) error 1018 as mentioned:
• The value of checksum fails to match with the value of calculated checksum at the time of writing the database to disk.
• Either the data is written at the incorrect location or there is some issue with NTFS file system.
Technique to Fix Exchange Jet Error 1018 JET_errReadVerifyFailure
Once it is cleared that how the Exchange (2013, 2010, 2007) error 1018 is occurred. Now, let u know the way to fix it by using the Eseutil tool. It is an open-source command-line utility, which is programmed by Microsoft to recover the EDB data. Follow the systematic steps to resolve the page-level EDB file corruption.
Step 1: Using ESEUTIL
Using the Eseutil/p switch is one of the best method to solve the damage of the file-system level. If the data damage prevails in page of EDB file then, it results in data loss. Moreover, if you are facing damage in internal page then, DB drops its structure information. It results in the reconstruction of table.
Once the procedure is started, all the corrupted EDB files are removed and healthy data files are left behind. However, it is not possible to directly mount the server to database until you defrag and correct it.
Follow the syntax to follow the repair Exchange database file by using Eseutil/p cmdlet:
Step 2: Defragmentation of Database
Once the corrupted pages are removed from the database then, some white space is left behind. This can only be eliminated by defragging the DB by using the syntax:
C:\program files\exchsevr\bin>Eseutil/d “c:\program files\exchsrvr\mdbdata\priv1.edb”.
Step 3: Correct B-Tree Structure
An index of database is not maintained properly at the time of repairing and defragmentation procedure. Therefore, it can be easily corrected by making the usage of Isinteg utility. It makes easy to correct the physical and logical numbering of database, which in turn makes it mountable on the server.
Final Words
The discussed procedure is quiet lengthy as well as it is essential to be professional for using Eseutil. In a way to recover EDB data files and remove Exchange Jet Error 1018 JET_errReadVerifyFailure in Exchange 2013, 2010, 2007. It is advised to utilize Exchange Recovery software. It is an easy approach to recover data from private as well as public folder from corrupted or offline EDB files.