How to Fix Exchange Error 1018 (Page Level Corruption in Exchange Database)

What is Exchange Error 1018 JET errReadVerifyFailure?

An Exchange Server database can become corrupt at different levels, for different reasons, with varying results. For example, if an EDB file page is corrupt or the database index is compromised, Exchange Server database corruption can be categorized as physical (page level) or logical (ESE database level and Information Store level).

Error 1018 JET errReadVerifyFailure is caused by page-level corruption in an Exchange Database (EDB) file. Mostly, this error occurs during online backup creation. If left unresolved, the 1018 jet_errreadverifyfailure error can corrupt or damage the EDB at the page level, resulting in users' inability to access and read messages stored in the Exchange database.

The reasons for Exchange Error 1018 - Page Level Corruption

Error 1018 in Exchange can occur due to the following factors.

• The checksum value calculated when the Exchange database is written to disk does not match the checksum value for any specific page in the file header.
• A NTFS file system error.
• Data was written to the wrong location on the hard disk.
• Exchange Server generated an incorrect checksum value for the page.
• The correct checksum was written to the wrong location.

Solution for Exchange Error 1018: JET_errReadVerifyFailure

There are both manual and automatic methods to fix Exchange Error 1018. You can choose the solution as per your requirement.

Manual Ways to Fix Exchange Error 1018

1. Utilize online backup services.

If you have created them previously, you can use a reliable media, such as NTBackup or Windows Server Backup, to restore the database and log files from an online backup.

Using the ESEUTIL Command

You can utilize the built-in Microsoft utility, ESEUTIL, to fix Exchange Database error 1018. Before proceeding, it's highly recommended to back up your Exchange database to prevent any potential data loss due to incorrect operations.

The /p command: If the checksum fails, you can use the /p command to repair the damaged database file. If the corruption is severe, it will recreate the table by dropping internal pages.

The /d command: If free space was created by deleting damaged pages, you can run the /d command to defragment the database and remove this space.

Methods to Automatically Fix Exchange Error 1018 and Repair Exchange Server Database

As stated above, Exchange error 1018 (Page Level Corruption in Exchange Database) if not resolved, might corrupt the EDB and make the database unreadable. Hopefully, you can resolve the issue with the manual methods mentioned above.

However, if you still cannot access the EDB file or read messages from mailboxes, you can use the Exchange Recovery tool to recover data from the EDB file. With this utility, you can easily repair damaged mailboxes in Exchange 2016/2013/2010 to restore deleted mailboxes, attachments, contacts, calendars, tasks, and more. Additionally, after the recovery, you can export the recovered mailboxes to a Live Exchange server or MSG format.

Now, proceed with the following steps to automatically repair and recover Exchange Server database:

Step 1: Select the EDB file.

Search and select the lost Exchange Database file. After selecting the EDB file, click on “Analyze”.

Step 2: Analyze the file.

The software will analyze and locate lost Exchange data.

Step 3: Retrieve the desired information.

Select the emails and other data you need, and preview the contents of your mailboxes.

Then, you can export the data to a specific location by clicking “Export MSG” or recover the data to the server by clicking “Recover”.