Software⏱️ 3 min read📅 2026-06-11

How to Fix: How to fix an EDB database error -1022 on an Exchange 2007 (Enterprise Edition) server

Exchange 2007 database error -1022 fix and recovery guidance.

Quick Answer: Run the command "eseutil /mh" with elevated privileges, then use the Exchange Server Management Console to repair the database.

An error -1022 on an Exchange 2007 (Enterprise Edition) server can be frustrating when trying to run the eseutil /mh command, resulting in the dismounting of a database and loss of approximately 41Gb of data. This issue affects users who rely on the Exchange server for their email communications.

The situation becomes more challenging when no working backup of the database is available, leaving administrators with limited options to recover the lost mailboxes.

💡 Why You Are Getting This Error

  • The primary cause of error -1022 occurs due to a corrupted EDB file. This can be caused by various factors such as power failures, hardware issues, or software conflicts during the exchange installation process.
  • An alternative reason for this issue could be due to incorrect configuration or mismanagement of the Exchange database. In some cases, the database may become fragmented or locked, leading to the -1022 error.

🔧 Proven Troubleshooting Steps

Recovering from a Corrupted EDB File

  1. Step 1: Step 1: Stop the Exchange Information Store service and ensure that all mailboxes are disconnected. This can be achieved by running the command 'Get-Mailbox -ResultSize Unlimited | Stop-ExchangeMailbox' to disconnect all mailboxes.
  2. Step 2: Step 2: Use Eseutil to recover the database. Run the following command: 'Eseutil /m /r ' where is the name of the corrupted database and is the point in time when the database was last backed up (if available).
  3. Step 3: Step 3: Once the recovery process is complete, restart the Exchange Information Store service and test mailbox connectivity to ensure that all mailboxes are accessible.

Using Exchange Server Backup Software to Recover from a Corrupted Database

  1. Step 1: Step 1: Install and configure an Exchange server backup software such as Veeam or Acronis. This will allow you to recover the database from a previous backup point.
  2. Step 2: Step 2: Use the backup software to restore the EDB file from the last available backup point. The exact steps may vary depending on the software being used, so refer to the software's documentation for specific instructions.

🎯 Final Words

Recovering an Exchange database with error -1022 requires prompt action and careful planning. By following these steps, administrators can successfully recover their mailboxes and minimize downtime. It is essential to maintain regular backups of the database to avoid such issues in the future.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions