Quick Answer: To resolve the error, use the eseutil tool to replay the uncommitted transaction log files to the database and then try to mount the EDB file.

An Exchange Server database may fail to mount due to logical or physical corruption, a dirty shutdown state, storage issues, etc. You will get the following error message when you are unable to mount database in Exchange Server.

Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2- ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259)

Moving forward, we will discuss in detail why you are getting the above error, along with methods to fix Exchange database mount error.

Why is the Exchange Database Unable to Mount?

There can be multiple reasons why you cannot mount the database in Exchange Server. The top reasons are:

  • Deletion of uncommitted transaction logs.
  • Corrupt Database.
  • Dirty Shutdown State due to an abrupt system shutdown.
  • Database is almost full (more than 90%).

How to Fix ‘Exchange Database Fails to Mount' Issue Using Eseutil?

You can resolve the error and mount the Exchange database again successfully using the eseutil tool.

Method 1: Replaying Log Files

If the database is in a dirty shutdown state, you will not be able to mount the database on the Exchange Server. Using eseutil, we will first confirm the state of the database, and if it is in a dirty shutdown state, we will resolve Exchange unable to mount database error using the log files.

  • Run eseutil /mh command to verify database current state un eseutil /mh command
  • If the output displays the database in a dirty shutdown state, as shown below, we will use the /r (soft recovery) switch to fix the issue. Database is missing a transaction log

    Run this command to replay logs:

    eseutil /r <log-prefix> /l <log files path location> /d <database path location>

  • When the repair process is complete, again run the eseutil /mh command. Doing so will let you verify whether the database is in a clean shutdown state or not. Verify that the database
  • Now, you can mount the database in Exchange without error using the command -

Mount-MailboxDatabase -Identity <database-name> However, if the database state is still dirty shutdown, you need to perform hard recovery.

Method 2: Fix Exchange Unable to Mount Database Issue with Hard Repair

In cases when replaying the log files did not resolve Exchange 2010 error unable to mount database issue, you should perform a hard repair on the Exchange database using the Eseutil tool. The hard repair will scan the database for damaged pages and, if any are found, will remove them.

Hard repair will delete all the corrupt/damaged pages from the database, and this deletion is permanent. Therefore, use this command only when there are no other ways left to repair EDB files. Command to run the hard repair:

eseutil /p <EDB file path>

After this, you must defragment the database with this command:

eseutil /d <EDB file path>

And finally, run the isinteg command. Then, check if the “Exchange database fails to mount” issue is resolved.

What If Eseutil Cannot Repair the Exchange Database?

Sometimes, the eseutil tool may fail to resolve Exchange 2010 error unable to mount database. This could happen if the EDB file is severely corrupted.

In such a case, do not forcefully try to fix Exchange database mount error. This may waste time. Also, if you use hard repair multiple times, the EDB file may not be useful to you anymore. I recommend that, here, you must focus on data recovery. To safely recover all the user mailboxes from the damaged EDB file, use the following methods:

Method 1: Recover Data Using a Backup File

If you have a backup of the database, you can use it to recover the user’s data without the original EDB file. Recovering data from a backup file is especially useful when the EDB file is offline and fails to mount. In this case, you can create a Recovery Database (RDB) and use it to get back the user's data. Administrators often use this method to restore or recover mailboxes without affecting the original EDB file.

Steps to perform data recovery are:

  1. Open the Exchange Management Shell (EMS) and create a recovery database.
  2. Use Windows Server Backup to restore the database from the backup file.
  3. Bring the restored database to ‘Clean’ state from ‘Dirty Shutdown’ state.
  4. Mount the new database and move the data from RDB to the production mailboxes.

In case of missing data, use the transaction logs to restore the lost data using the eseutil tool. However, if you do not have the log files, the missing data may be lost forever. If you do not want to lose data, you must use a professional Exchange Server recovery tool to access the damaged EDB file.

Method 2: Recover the Database Using a Recovery Software

A professional Exchange database recovery tool allows you to recover the complete data from your dismounted or corrupted EDB file. Kernel for Exchange Server is a reliable software that supports severely damaged EDB files. The tool does not need the transaction logs and allows you to access the user's mailboxes, public folders, and other EDB file data without any issues. With this tool, you can:

  • Recover and export mailboxes from the EDB file to PST.
  • Export public folder data to your local system.
  • Migrate EDB to live Exchange or Office 365.
  • Restore mailboxes with original folder structure and metadata intact.

How to Prevent the Exchange Unable to Mount Database Error?

If you cannot mount the database, you will face issues with email communication, user logging, and more. To avoid these, make sure to:

  • Monitor space: Experts in Exchange recommend never letting your EDB file reach its storage limits to avoid mounting issues. Therefore, many admins prefer to export old mailboxes from the EDB using the native method or with an EDB to PST converter for bulk export.
  • Gracefully shut down server: Abrupt server shutdowns can introduce consistency issues in the database file and lead to issues like Dirty Shutdown in Exchange 2010. Make sure to always shutdown the system gracefully.
  • Do not delete log files: Some users delete old transaction log files to free up space on the database, and sometimes while doing this, they accidentally delete uncommitted log files, leading to the unable to mount database error.

Conclusion

The methods explained in this article provide practical solutions to resolve Exchange 2010 error unable to mount database. However, if the above discussed methods fail to mount the database, then your EDB file is heavily corrupted. In such a situation, you must try to recover the data either using the backup or with an Exchange recovery tool.

Frequently Asked Questions

Q. How do I fix an Exchange database that won't mount?

A.Use the eseutil tool to resolve Exchange unable to mount database error by replaying the uncommitted log files.

Q. Can I mount a corrupted Exchange database?

A. No. Exchange Server does not allow mounting a corrupt database.

Q. Is it safe to perform hard recovery on the Exchange database?

A. No. Hard recovery should be your last option, as it permanently removes corrupted data, causing data loss.

Q. Why is Exchange showing unable to mount database error?

A. Such an error usually happens due to a dirty shutdown state, missing transaction logs, or existing storage issues.

Q. How to recover data from a database that fails to mount in Exchange?

A. To recover data from a dismounted database file, you can either use a backup file or a professional EDB file recovery tool.

Sarthak Poswal
Sarthak PoswalTechnical Writer

This article is written by Sarthak Poswal, a technical content writer at Kernel Data Recovery. This content has been reviewed in accordance with our editorial guidelines.

Table of Contents
Related topic
↑