How to Handle Exchange Server Errors Correctly

Sandeep Saxena | Updated On - 22 Dec 2020 |

If you are using Exchange Server to manage your email communication, then you must be aware of the importance of its database file which has the .edb extension. It is a strategic warehouse which saves the data sent/received by the Exchange Server. Any Exchange database corruption and failure may affect the functionality of the whole email communication channel within the organization.

There are multiple types of errors which you should recognize and know. We will discuss about their possible reasons and how to tackle them –

  1. Exchange Server Error Code 528.
  2. Sudden Shutdown Error.
  3. JET_errInvalidDatabaseId -1010 and many more.
  4. Corrupted/Damaged header information.
  5. Exchange Server Error Code 550.
  6. Unable to initialize the MS Exchange Information Store service.
  7. Improper Server shutdowns.
  8. “JET_errRecordNotFound, the key was not found” “Jet_errRecordDeleted”.
  9. Deleted mailboxes.

Now we will go through some common JET errors and how you can resolve them –

501 JET_errLogFileCorrupt

Reason – The Log has become unresponsive or unreachable due to corrupt I/O at writing. It leaves the Exchange database in a corrupt state.

Resolution – Use the backup to restore the database or try to reinstall the Domain Controller.

528 JET_errMissingLogFile

Reason – The computer may have shut down unexpectedly due to a power outage.

Resolution – Use the backup to restore the database or try to reinstall the Domain Controller.

567 JET_errDbTimeMismatch

Reason – The disk has lost an I/O subsystem due to unscheduled shutdown.

Resolution – Check battery backup for disk cache.

1018 JET_errReadVerifyFailure / Checksum error on a database page

Reason – The database is corrupt due to a hardware failure.

Resolution – Update the firmware or defrag the disk.

1605 JET_errKeyDuplicate / Illegal duplicate key

Reason – Index corruption.

Resolution – Remove and reinstall the Active Directory on the Domain Controller.

These are a smaller set of JET errors which are quite frequent in the Exchange database. But you can handle these corruptions and to retrieve the data in different ways-

  1. Backup your data

    It is the first and foremost thing which you should do before making any attempt to repair corrupt Exchange database. Because during the recovery process, a single wrong step will make the data inaccessible.

  2. Run ESEUTIL tool

    ESEUTIL is an inbuilt command line tool which can repair smaller corruption in EDB, STM, and LOG files. There are multiple switches which you can run with this command and use for various purposes. Here is how you can use the switches –

    ESEUTIL /p

    This command will repair the database. It checks the database pages which are either corrupt or damaged.

    ESEUTIL /g

    This command checks the logical integrity of the database. It checks whether the database was properly shut down or not. But it does not perform a more in-depth check.

    ESEUTIL /r

    It checks the discrepancies in the log files. It recreates or forwards the transaction log files.

    ESEUTIL /d

    It defragments the database after you complete the repairing. It removes any whitespace which will ultimately reduce the total size of Exchange database.

  3. Professional Exchange Recovery tools

    If any of the manual methods does not work, then it is the time to go for a professional tool. Kernel for Exchange Server Recovery is the most suited tool for Exchange Recovery. It securely recovers mailboxes from the Exchange database. Using the tool, you can recover Exchange mailboxes to PST files, live Exchange Server, or Office 365.