Here we have come up with an Exchange error which is generally known as Exchange Error 1018. Read this blog to know how to tackle this error.
Know about Exchange Error 1018
The Exchange error 1018 is due to corruption in the Exchange database (EDB) file. It is a page level (physical) corruption, and leads to the inaccessibility of EDB data. Usually this error occurs when a user takes an online backup of the Exchange database. The error reads like this.
Exchange jet error 1018: Operation terminated >
Error 1018 jet_errreadverifyfailure checksum error >
Exchange Error 1018 – Scenario and Causes
Exchange Server EDB file is built up of pages of 4KB size, organized in a B-tree structure linked sequentially. The starting two pages make the header while the third one is considered as the first logical page. Conventionally, when an EDB file is written to the disk, checksum value of these pages are calculated and stored the header page. When any operation like Exchange database backup or other operation is performed, this checksum value is calculated and tallied with the actual one on the header. If there is any difference or mismatch between the values due to any reason, the process gets failed and the page is considered corrupted.
The reasons for this checksum values’ mismatch could be NTFS file system error, incorrect hard drive location for writing EDB file, etc.
For this EDB page level corruption, we can try on some manual solutions provided by the Exchange Server like in-built utility ESEUTIL commands to repair the existing EDB file or secured online backups programs to retrieve the Exchange data from a backup file.
Here, are the solutions to resolve the Exchange error 1018.
- Run ESEUTIL commands
- Restore Exchange data from backup
- Repair Exchange database with Recoveryfix for Exchange Server Recovery
Exchange administrators can use ESEUTIL for Exchange Server repair. ESEUTIL is a command line utility available within \EXCHSRVR\BIN directory. For example, the default location of this application in the Exchange Server 2013 is – C:\Program Files\Microsoft\Exchange Server\V15\Bin. It is advised to take a backup of the existing Exchange database to avoid any data loss during the operation of this utility.
Now, first dismount the Exchange database and launch the ESEUTIL tool.
Run this command to repair the EDB file, i.e. to fix corruption within the file, remove the damaged pages and also create the new table structure.
ESEUTIL /p >
It is possible that due to deletion of the damaged pages, some white space is created within the EDB database. So, run the defragmentation command to defrag the database.
ESEUTIL /d >
By running the above ESEUTIL commands, the database index and thus logical & physical numbering of the EDB pages may get distorted which we can correct a using the ISINTEG command utility.
Find the ISENTEG utility at the same location C:\Program Files\Microsoft\Exchange Server\V15\Bin and launch it. Then execute this command.
ISINTEG –s servername –fix –test all tests >
After running this command, mount the Exchange Server database and then check if the error is resolved while taking the online backup.
If you have a recent Exchange backup file with you and do not want to run the in-built application commands, then you can restore of Exchange database using that backup easily. It would allow you to access your database again. The best utility to perform Exchange database backup/restore is Windows Server Backup utility.
If none of the above solutions work in your favor, then the ultimate way to fix the EDB corruption is using a trustworthy third-party tool. The advanced Recoveryfix for Exchange Server tool repairs corrupted EDB files using its powerful algorithms. The tool fixes all the Exchange corruptions and errors including this page-level error. We list out the main functions of this EDB recovery tool for the users.
- Repairs highly corrupted EDB files
- Restores selective data from offline EDB files
- Recovers mailboxes, public folders, archived mailboxes, etc.
- Preview of EDB data before saving to destination
- Saves recovered EDB data to Live Exchange, PST file, Office 3656, and more destinations
- Restores Exchange database files from backups
- Offers automated and quick database recovery
- Full support to all Exchange Server versions
- Time and effort-saving solution for fixing EDB issues
- Trial version is absolutely free of cost
We have discussed some effective solutions, both manual and automated, to resolve Exchange error 1018. You can try any of the methods and move forward to the other if not succeeded with the first one. We welcome your comments and queries on this topic.
Read Related Blog
- Fix the ‘mailbox export request stuck in queued’ issue in Exchange
- Fix the Low Disk Space Issue in Exchange Server Database
- How to Create PST from Exchange Server?