Resolve Exchange 2010 Error “Unable to Mount Database”?

Last Page Updated on 21 March 2022 by Manoj Kumar

Are you running Exchange Server 2010, 2013 or 2016 and you are seeing an error message such as "Unable to mount database" It is important to understand the way transaction logs function. The Transaction log acts as the core of Exchange Server. It is essential to ensure the smooth operation for the servers. Each transaction on the server gets recorded in log files that are subsequently committed into the database. The transaction logs remain in the database and memory of the system until the transaction is stored in the database.

In case of a failure, in this scenario there is a chance that you will lose the information from memory you reboot because it wasn't completely saved to Exchange database files. This is where the transaction logs play a role. They're the reliable recovery mechanism to return the data back to safekeeping in the Exchange database.

Importance of Log files:-

Checkpoint files and transaction logs Checkpoint files and transaction logs in Exchange Server 2010 help prevent data loss. The transaction log tracks every change made to the database in memory while checkpoint files store details of the modifications that were logged to the databases stored on disk.

Exchange Server 2010 provides a single set of transaction logs for every database. Prior to the records being transferred to the database file they are recorded in transactions logs.

The restore procedure lets you restore the disc to the database even if the disc is damaged, however the transaction logs remain intact. Exchange Store Exchange Store reads the transaction logs and replays transaction logs that had been completed. In the future, you will be able to play the remaining log files of the transaction on disc. The transaction could be unsuccessful if the system cannot distinguish to complete two of the transactions recorded in the log. In these cases restoration of the log may fail.

If you are unable to mount the Database on Exchange Server, you might receive this error message:

Exchange is unable to mount the database you specified."

Specified Database - d1cdba46-6f79-46f2- ba14-3ae2fa8aad43; Error code:

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259)”

Causes of Exchange Server Databse Errors

  • Logs of transactions were erased and were to be committed to the database
  • Dirty shutdown
  • Corrupt database

Microsoft provides an Eseutil tool to determine and verify that a database has been properly shut down. If it's in a state of good health the tool will fix the problems and bring the database back to its original state. If the data isn't in a constant state it is possible to get the information back from backup using the following steps.

How to Resolve Exchange Database Errors?

The removal of log files is one of the major reasons why it might not be in a position to mount. To fix this issue, it is necessary to verify the compatibility of the application.

Soft Repair Steps to verify and repair Inconsistent Database

It is possible to perform soft repair by using this Eseutil tool. It could be of immense assistance when you need to mounting the database again after an abrupt stop. These are steps you should follow:

  • Run mh/eseutil command
  • If it displays a dirty shutdown status on the report, the database may be missing the transaction log.
  • To restore the database to an identical state, it is crucial to recreate log files from the database. In this manner, you could run the command ESEUTIL - eseutil /r /l /d
  • Provide location where logs are stored, such as - G:\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\DAGDB1
  • After completing the repair process, perform this action again. Run the command eseutil/mh. By doing so, you can easily verify database in clean shutdown state.
  • You can now mount database back to Exchange with this command – Mount-MailboxDatabase -Identity '-DAGDB1.edb'

If you still cannot mount the database, verify the transaction log consistency.

Hard Repair to Verify and Repair Database Logs

Eseutil tool really comes handy for hard repair to test database for any of the damaged pages. This tool will delete those pages, if any. Run the following command for hard repair – Eseutil /p '\DAGDB1.edb

If you're still having trouble mounting the database, in this case, I recommend you utilize the third party EDB to PST Converter software designed for Exchange Server Recovery, a useful tool that can recover the data from any damage quickly, even if the Eseutil tool fails to produce the expected result. In this method, EDB to PST Converter is a cutting-edge software to recover damaged or corrupted Exchange database files, without the need for Exchange log files or services. This tool allows you to retrieve EDB documents in exchange for a Live Office 365 mailbox and Exchange Server.

Secure100% Safe & SECURE
SupportLifetime Support (24X7)
Moneyback GuaranteeMoney Back Guarantee
Trust ImageTrusted by Millions Worldwide