In this blog we will discuss the main reason of Jet Engine Error 1018 (Jet_Errreadverifyfailure) and possible solution for the same in Exchange Server.
The major reason of the error is corruption in the database that may occur due to many reasons like Improper Shutdown, Improper Handling, Virus Attack, etc. This corruption in the database sometimes corrupts the main components of the Exchange Server database, like Page Header, Database Catalogs, Indexes, Leaf Pages.
Instant Solution: To remove the severe and minor corruption from offline / dismounted Exchange database file, you can use the advanced Exchange Server Recovery Software which easily remove corruption from EDB file without using any PowerShell cmdlet. After recovery, user can export multiple mailboxes to PST Exchange 2016/2013/2010 and various file formats to keep the database safe & secure. Also, this utility allows you to export mailboxes directly to the Live Exchange Server 2016 / 2013 / 2010 / 2007 / 2003 mailboxes and Office 365. It support all versions of Windows OS, Microsoft Outlook and Exchange Server.
Due to security measures it is highly recommended to detect the errors as soon as possible otherwise it may lead you in a serious trouble. One of such error is Jet Engine Error 1018 (Jet_Errreadverifyfailure) that shows that the Exchange Server Database has experienced damage at file System Level.
These types of errors are detected by application log in the Windows NT/2000. The description of the error is shown in the figure below:
You may encounter these types of error while performing the online backup or while doing any maintenance operation on it.
The reason is that on the every page that is presents in the database of the Exchange Server, The database engine performs the check operation. Each page contains the header that contains information about that page. Size of each such page is 4KB. Whenever this engine reads any particular page, first of all make sure that page should be same as that one returned during extraction of information from the page header of that particular page. After that it authenticates the CRC. If Database engine finds it invalid, it will return Engine Error 1018
To repair the database from such corruption you can use Eseutil Command or can restore the databse from backup if you have. Lets us discuss both of recovery operation in details.
One can use Eseutil Utility provided by Microsoft to perform the recovery operation. Eseutil with parameter P is used to perform the hard recovery of the Database.
I will suggest you to only use this tool if the database has minor corruptions. If the database has major corruption and you try to recover data using Eseutil, It may delete the highly corrupted pages and hence you may lose some important data. As there is danger of losing data, that’s why the utility is not preferred by many of the users. Still if you want to go through with this solution,
Here you can check, how to recover database using Eseutil Command. If Eseutil doesn’t work for you, Then you should go for third-party tool to recover the Corrupted database.
If you have a healthy backup of the database, you don’t need to go anywhere. You can easily restore your entire database from backup.
You can visit this post for how to restore mailboxes using recovery database or windows server backup (WSB). In case if the backup file that you are using to recover the database is corrupted, You first need to repair the backup file using third-party utility i.e. Exchange server Recovery Software which provides Quick and Advance scan mode option that easily recovers severely damaged/corrupted offline or dismounted Exchange database file without any data loss in a simplified manner with no data loss.
Database corruption is the general issue faced by many system administrators. The blog will help you to recover from Jet Engine Error 1018 (Jet_Errreadverifyfailure) by using the ESEUTIL utility. After that also if your mailbox database is not recovered from corruption then you can use the advanced software mentioned in this write-up which easily recover the corrupted offline/dismounted EDB file without any loss of data in a hassle-freeway. In case if you are having any issues regarding the recovery operation, Please comment, We will try our best to sort out your query.