How to resolve Jet Engine Errors in MS Exchange Server?

Updated On - October 25, 2024 by Armaan | Reading Time: 8 minutes

You might have come across Exchange Server JET Engie errors in Microsoft Exchange Server and struggling on how to resolve those error messages. This article discusses the various Exchange Server JET Engine Errors. The below list enlists few Exchange Server JET Engine Errors:

1. Error 344 – JET_errDbTimeCorrupted (Time Mismatch Error)
2. Error 501 – JET_errLogFileCorrupt
3. Error 510 – JET_errLogWriteFail
4. Error 528 – JET_errMissingLogFile
5. Error 543 – JET_errRequiredLogFilesMissing
6. Error 550 – JET_errDatabaseDirtyShutdown
7. Error 551 – JET_errConsistentTimeMismatch
8. Error 567 – JET_errDbTimeTooNew
9. Error 1018 – JET_errReadVerifyFailure
10. Error 1019 – JET_errPageNotInitialized
11. Error 1021 – JET_errDiskReadVerificationFailure
12. Error 1022 – JET_err DiskIO
13. Error 1032: (JET_errFileAccessDenied, cannot access file, the file is locked or in use)
14. Error 1206 – JET_errDatabaseCorrupted
15. Error 1216 – JET_errAttachedDatabaseMismatch
16. Error 1601 – JET_errRecordNotFound
17. Error 1605 – JET_errKeyDuplicate
18. Exchange Server JET Engine Error 1811
19. Error 0xfffffdfd – JET_errInvalidLogSequence
20. Error JET_errFileAccessDenied (Anti-Virus)

Discuss all the above Exchange Server JET Engine errors in detail, the reason for their occurrence and the manual method to resolve them.

Exchange Server JET Engine Error 344 – JET_errDbTimeCorrupted (Time Mismatch Error)

Error message that appears states –

“JET_errDbTimeCorrupted -344 The Dbtime on the current page is greater than the global database dbtime. This error is returned by the directory manager.”

This error might appear when there is a time mismatch in the DB compared to the directory.

Resolution

To resolve this issue, perform the steps as below:

1. Run eseutil /d command
2. After defragmentation completion, move all the existing mailboxes to a new Exchange Database.

Exchange Server JET Engine Error 501 – JET_errLogFileCorrupt

The Exchange Server JET Engine Error 501 occurs when hardware corrupted the I/O at writing, or the hardware lost flush causing the log to become unusable. The error results in corruption of database.

To resolve this error message, restore the database from a known good backup, or reinstall the domain controller (DC).

Exchange Server JET Engine Error 510 – JET_ErrLogWriteFail

This error causes failure to write log files. This error might appear due to following reasons:

• A controller, hard drive, or other hardware stopped responding to disk commands.
• Software like Antivirus created locks on Active Directory log files.

Resolution

• In case of a hardware issue, restart Server will restore access. If the issue still persists, upgrade firmware, replace the controller, or replace the disk.
• In case of software issue, stop the services that create locks on the files in the file system.

Exchange Server JET Engine Error 528 – JET_errMissingLogFile

The Exchange Server JET Engine 528 appears due to unexpected shutdown caused due to a power outage or an unexpected shutdown. Other reasons may include changes to log files by administrator, corrupted backup/restore software.

To resolve this error message, restore the database from a known good backup, or reinstall the domain controller (DC).

Exchange Server JET Engine Error 543 – JET_errRequiredLogFilesMissing

The Exchange Server JET Engine 543 occurs when Administrator modifies logs or lost I/O flush on shutdown.

Exchange Server JET Engine Error 550 – JET_errDatabaseDirtyShutdown

Exchange Server JET Engine 550 occurs when Administrator modifies logs or lost I/O flush on shutdown.

Exchange Server JET Engine Error 551 – JET_errConsistentTimeMismatch

Exchange JET Engine 551 occurs when Administrator modifies logs or lost I/O flush on shutdown.

Exchange Server JET Engine Error 567 – JET_errDbTimeTooNew

This occurs due to disk subsystem lost an I/O, most probably on a hang or unscheduled shutdown.

To resolve this error message, verify battery backup for disk cache.

Related Blog: How to Repair Corrupt EDB file

Exchange Server JET Engine Error 1018 – JET_errReadVerifyFailure

This is the most common mounting error in the Exchange Server. This error corrupts the Exchange Database .EDB files and displays “JET_errReadVerifyFailure”.

This error occurs in case incorrect checksum or page number is encountered during the read page process. Microsoft Exchange Server finds the checksum value of stored page as different with the final recalculated checksum value at the page read process. The discrepancies in the physical location of a page leads to mismatch in the page number that further results in Exchange file system corruption.

Cause

Exchange JET Error 1018 occurs due to page-level corruption in the Exchange Database .EDB files which are beyond the scope of repair with inbuilt Exchange Server utility. This error message appears during creation of the online backup i.e. cloud backup.

Resolution

To resolve this issue, try any of the below solution:

• Online Backup Restoration: Restore log files and database files from the online backup by employing reliable backup media like NTBackup or Windows Server Backup.
• Restoration using ESEUTIL Command:
  1. Take a backup of the database.
  2. Execute restoration process by Eseutil/p command.
  3. Ensure process correctness by defragmenting the database.

Exchange Server JET Engine Error 1019 – JET_errPageNotInitialized

The Exchange JET Engine Error 1019 – JET_errPageNotInitialized occurs when the requested page is either empty or uninitialized in the Exchange Database. The reason for unavailability of requested page might be due to corruption in the file system that further damages the Exchange Server database.

Exchange Server JET Engine Error 1021 – JET_errDiskReadVerificationFailure

The Exchange Server JET Engine Error 1021 might appear due to bad blocks on the hard disk.

To resolve this error message, remove and reinstall Active Directory on the Domain Controller.

Exchange Server JET Engine Error 1022 – JET_err DiskIO

Error 1022 JET_err DiskIO occurs in case the disk Input/Output process restricts Exchange Server to access the targeted page in the Exchange database. This error results in truncated or damaged file when Exchange Server access page number that exceeds total number of pages. The Exchange JET Engine error 1022 corrupts the Exchange Information Store due to inefficient transaction log replay activities.

Exchange Server JET Engine Error 1032: (JET_errFile AccessDenied, cannot access the file, the file is locked or in use)

The above error message might appear if:

• An application is holding onto the file
• In case of no anti-virus exclusions in place, anti-virus might either remove log files or lock .edb file to scan it.

Resolution

To resolve this issue, perform any of the below solutions:

• Disable the antivirus software
• Exclude the Exchange folder
• Run the eseutil /p command to perform Exchange mailbox database recovery

Exchange Server JET Engine Error 1206 – JET_errDatabaseCorrupted

The Exchange Server JET Engine Error 1206 is same as missing or corrupt log file. The error message indicates occurrence of a lost flush.

Exchange Server JET Engine Error 1216 – JET_errAttachedDatabaseMismatch

JET_errAttachedDatabaseMismatch appears in case few important files are deleted, removed, or substituted. This error is reported by the header information assessment in log files and databases.

Cause
The Exchange JET Error 1216 occurs due to abrupt stopping of a running storage group. In case the administrator executes the recovery method, the running file may not include the recovery of deleted files and when the storage group initiates, the header information is examined by the system and the Exchange JET Error 1216 will appear again.

Resolution

Perform the below steps to resolve the Exchange JET Error 1216:

1. Execute the command: – ESEUTIL /mh | find /i “consistent”
2. Execute the command: ESEUTIL /mh | find /I “Shutdown”
3. Transfer the files to the safe location before undergoing the restoration.
4. Restore the remaining files by mounting them.
5. Restore the database from the backup.
6. Repair the database.

Exchange Server JET Engine Error 1601 – JET_errRecordNotFound

Exchange JET Engine Error 1601 occurs in case the STM and EDB files have different structure or severe corruption in the Exchange Database EDB file.

The error message reads as: “JET_errRecordNotFound, the key was not found”.

To resolve this error, perform the below options:

• Get the latest service pack of MS Exchange Server
• If you have an updated database backup, perform a complete backup restore.
• Use third-party Exchange Database EDB repair software to repair the corrupted database.

Exchange Server JET Engine Error 1605 – JET_errKeyDuplicate

The Exchange Server Jet Engine Error 1605 may occur due to index corruption.

To resolve this error message, remove and reinstall Active Directory on the Domain Controller (DC). Run NTDUSITL semantic database analysis. If the error message still appears, perform an offline defragmentation.

Exchange Server JET Engine Error 1811

Error 1811 occurs in case administrator modifies logs or lost I/O flush on shutdown.

Exchange Server JET Engine Error 0xfffffdfd – JET_errInvalidLogSequence

Error 0xfffffdfd occurs due to missing log files or log file mismatch.

To resolve this error message run the commands Eseutil /r and Eseutil /p through the inbuilt utility Eseutil.

Exchange Server JET Engine Error JET_errFileAccessDenied (Anti-Virus)

Anti-Virus can delete log files or can lock files, also you may encounter JET_errFileAccessDenied error message when the Exchange database tries to mount.

Resolution

In case of any anti-virus installed in Exchange, make sure that all the exclusions are set. With correct exclusions in place, it ensures that Exchange runs properly.

Few Other Exchange Server JET Engine Error Messages

• Microsoft JET Database Engine cannot open the file ‘(unknown)’ It is already opened exclusively by another user, or you need permission to view its data.
• The JET VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) failed to initialize when called. Try reinstalling the applications that returned the error.
• JET_errRecordNotFound, the key was not found
• Exchange Server JET Engine Error 100 – JET_errRfsFailure
• Unable to initialize DAO/JET DB Engine
• The Microsoft JET Database Engine stopped the process because you and another user are attempting to change the same data at the same time.

Common Reasons for Exchange Server JET Engine Errors

• Hardware malfunctioning like hard drive crash
• Power Failure that leads to damaging the EDB mailboxes
• Various registry issues and software crashes that results in corrupting critical objects of Exchange database
• Mismatch in JET or DAO files
• Missing or deleted Exchange log files
• Mismatch between Exchange log file generation number and signature
• Incorrect data restoration in the Exchange database

EseUtil Commands for Exchange Database Repair

In Exchange Server, Microsoft provides a native command-line tool Extensible Storage Engine Utilities (EseUtil) that helps check the status of a database and perform various Exchange database maintenance and repair tasks.

ESEUTIL Commands with Description and Usage

1. ESEUTIL /C : To perform the hard recovery of the Exchange database, displays restore log files of the database.
2. ESEUTIL /D :  To facilitate the offline defragmentation of the Exchange database for removing the empty space. Helps reduce the overall size of Exchange database on the disk, optimizes database file for performance. Keeps a check on the database health.
3. ESEUTIL /G : To perform the integrity inspection of the Exchange database. Verifies page-level and ESE-level database integrity checks to detect specific inconsistencies with the database.
4. ESEUTIL /K : To initiate the analysis of checksum values in database file, transaction log file and checkpoint file.
5. ESEUTIL /M : Displays the header information of the Exchange database files, log files and checkpoint files. Displays database space allocation and page header information with metadata.
6. ESEUTIL /MH : Displays database state i.e. Dirty Shutdown (Inconsistent) or Clean Shutdown (Consistent)
7. ESEUTIL /P : To recover the corrupted or damaged Exchange database. Removes pages that can’t be repaired. After executing this command, it is mandatory to perform offline defragmentation of the database.
8. ESEUTIL /R : To perform useful recovery operations on the Exchange Server database. Helps restoring the database. Replays transaction log files to bring the database from Dirty Shutdown or inconsistent state to Clean Shutdown or consistent state.
9. ESEUTIL /Y : To execute the copy operation on large mailboxes of the Exchange database

Use Professional tool to fix Jet Engine Errors in Exchange Server

Use a third-party solution – Regain Exchange Recovery tool to restore the Exchange database mailboxes on the Exchange Server. The tool restores mailboxes on Live Exchange Server and resumes mailbox connectivity lost due to dismounted Exchange mailbox database.

Free Download100% Secure Buy NowPrice: $99

Few Eminent Features of Exchange Server Backup Software

• Backup of complete Exchange Server data without any data loss.
• Saves backed up Exchange mailbox in PST, EML, EMLX, MBOX, MSG file format.
• Supports multiple backups from Exchange database including Primary and Archive.
• Backup all mailbox folders e.g. emails, contacts, calendars, tasks, notes, journal, etc.
• Retains original formatting of data during complete backup of Exchange mailboxes.
• Allows user to exclude the Empty and Deleted Items folders.
• Allows user to select the mailboxes and public folders to take backup.
• Backup Exchange Server data to Office365 account.
• Facilitates incremental backup feature to backup only additional data in case already backup done.
• Facilitates selective backups of Exchange Server mailbox folders.

Conclusion

This article discusses various Exchange Server JET Engine errors, reason for their occurrence and the manual solution for how to resolve that error message. Also, the article suggests using a third-party solution to restore Exchange database mailboxes on Exchange Server.