Microsoft Exchange Server, the most widely used emailing platform, is prone to many errors. These errors are often caused by minor issues that are easily resolved through simple fixes and built-in utilities. But some errors, such as Exchange Jet error 1018 or 1216, are caused due to severe Jet issues and need more attention and effort to completely resolve them. These errors indicate database damage. If not resolved soon, they can corrupt the entire Exchange database file (EDB).
In this article, you will learn the reasons behind the Jet error 1018 or 1216 and the solutions to fix these Jet errors without losing any data.
Reasons behind Exchange Jet Error 1018
The Exchange Server error 1018 JET_errReadVerifyFailure, also referred to as Checksum error on a database page, generally occurs as a result of page-level corruption in the EDB file. While file system-level database damage can be fixed by using the Exchange Server’s inbuilt utility, such help is absent for page-level corruption.
This error is usually occurred during online backup creation. The error may also occur due to the following reasons:
- Checksum recalculated during an operation on the database doesn't match with previously stored value.
- Error with your disk’s NTFS file system.
- Possibility of corrupt data being written to the hard disk or being written to an improper location.
- Incorrect checksum calculation by the Exchange Server at the first instance can also lead to this error.
- Creation of the correct checksum but writing it at an incorrect location may also cause this error.
- Lack of power by UPS, after power failure, prevents the onboard RAID controller to commit the changes to the disk. This is experienced on virtualized domain controllers running on the same virtual host on computers using an onboard RAID controller.
Solutions to Fix Exchange Jet Error 1018
Following are some solutions that you may follow to troubleshoot and fix the Exchange Jet error 1018.
1. Configure UPS to Shut Down
One of the workarounds to prevent and fix jet error -1018 in virtualized domain controllers is to configure the Uninterrupted Power Supply (UPS) software to power off virtualized guests when the power is lost. You may also use dedicated (not on-board) RAID controllers with their UPS or battery backups to prevent the -1018 JET error.
2. Restore Database from Backup
You can try restoring the database and log files from an online or offline backup. Exchange Server automatically ensures that the backup file is not corrupt by terminating the process, if the error 1018 occurs. You can perform this by using any third-party Exchange-aware backup utility or Windows Server Backup (WSB).
3. Repair Database with EseUtil
EseUtil is a built-in command line tool that can help fix issues with the Exchange database. You can perform Hard Recovery on the Exchange database by using the command ESEUTIL /p. This will discard the damaged pages from the database. This can lead to data loss as all damaged pages will be removed from the database. Thus, before running the command on your database, take a backup.
Once you have the backup copy of the database, execute the following command:
eseutil /p databasepath /databasepath
Click OK to accept the data loss and perform the hard recovery on the database.
After the process is complete, make sure everything is fine by defragmenting the database to remove the spaces created because of removal of damaged pages. This can be done through the ESEUTIL /d command:
ESEUTIL /d
Finally, correct the logical numbering of the pages through the ISInteg command, as follows:
ISINTEG –s servername –fix –test alltests
Alternate Solution
TIP: To overcome the shortcomings of manual methods such as the requirement of technical knowledge, failure to have a recent complete backup etc., use third-party EDB Repair Tool such as Stellar Repair for Exchange.
Exchange Error 1216
Exchange Error 1216 JET_errAttachedDatabaseMismatch occurs when header information assessment in log files and databases shows that some important files have been removed or substituted. This happens if a running storage group stops suddenly. Such a sudden stop leads to inconsistencies in almost all files of the database.
Reasons behind the Error 1216
The main cause behind error 1216 is the sudden stopping of a running storage group. Thereafter, if the administrator runs recovery method, the storage group will also start running again but with missing files. This poses two issues:
- It might become nearly impossible to include the lost information in the storage group again.
- When the storage group starts, the header information is examined by the system and if inconsistencies are found, error 1216 will be thrown again.
How to Fix Exchange Error 1216?
Here is the stepwise manual method to fix Exchange error 1216:
Step 1: Identify the files which have inconsistencies. This can be done by executing the ESEUTIL /mh command:
ESEUTIL /mh | find /i "consistent"
For Microsoft Exchange Server 2003 and earlier, modify the command as:
ESEUTIL /mh | find /i "Shutdown"
After the command is finished, check a sample of the output. It is important to note that all process logs must be available to recover the database successfully. If any log is missing, performing database recovery won’t be possible. The only option left is to perform the following steps:
Step 2: Transfer all files that are missing (last Consistent logs) to a safe location and then restore the remaining files by mounting them.
Step 3: Restore the database from backup.
Step 4: Repair the database.
To perform this, you need to run the Hard Recovery using the ESEUTIL /p command, followed by the defragmentation ESEUTIL /d command and ISINTEG -fix command.
Although Hard Recovery can help fix the Jet error 1216 and recover the database by removing the faulty or corrupt pages from the database, it can lead to significant data loss. All the data, such as mailboxes or mail items stored in the damaged or irrecoverable database pages, will be purged permanently.
Conclusion
To avoid data loss and overcome the shortcomings of manual methods, you can use an advanced Exchange recovery software, such as Stellar Repair for Exchange. This competent utility recovers all mailboxes and mail items, such as emails, attachments, contacts, calendars, tasks, etc. from corrupt EDB files with complete integrity. It has a range of other features and facilities such as exporting recovered mailboxes to a live Exchange Server or Office 365, saving recovered EDB in multiple formats, including PST, MSG, EML, HTML, RTF, and PDF, searching mails from scanned EDB, and more. Stellar Exchange Recovery tool acts as your data rescuer if 1018, 1216, or any other difficult errors threaten to put a halt to your work.
5 min read
