Live Chat
Home » Blog » Error » Exchange Server Error Guide: Failed to Mount Database Exchange 2016/2010
Error, Exchange Server

Exchange Server Error Guide: Failed to Mount Database Exchange 2016/2010

Published By Mohit Jha
Tej Pratap Shukla
Approved By Tej Pratap Shukla
Published On April 2nd, 2024
Reading Time 4 Minutes Reading

The Microsoft Exchange Server failed to mount database Exchange 2016/2010 is a frequently arising problem. It is for several reasons which include logs and database files out of space, power failure, server crashes, and so on. 

It can be fixed using different methods. Some of them are PowerShell, Exchange Admin Center, and automated methods. However, sometimes after fixing, it continuously generates the unable to mount database (hr=0x80004005, ec=1108) error. So, in this post, we will see the root cause and solution of the Exchange Server Error “failed to Mount Database”.  So, let’s get started with the problem itself.

Table of Content 

Problem “Unable to Mount Database (hr=0x80004005, ec=1108)”

Failed to mount the Exchange database ‘Mailbox Database’ Mailbox Database < Some Number> Failed

Error: Couldn’t mount the database that you specified, The database action failed, and Operation failed with the message: MapiExceptionCallFailed: Unable to mount the database.

Specified database: Mailbox Database;

Error code: An Active Manager operation failed.

How to Resolve “Failed to Mount Database Exchange 2016”?

There are two main possible causes of unable to mount database in Exchange 2016” :

  • Due to a Corrupt Database or,
  • Corrupt logs

To confirm the issue behind the error. We need to perform some troubleshooting methodologies mentioned below:

Step 1. Check the Database State: Dirty Shutdown Problem

The dirty Shutdown problem in the Exchange Server is the root problem for most of the issues. So, what is Dirty Shutdown? For Exchange Server to work fine it must be shut down properly.

Simply type the command: eseutil /mh “database name” in the command prompt. This will give you the status of whether or not your database suffers from dirty shutdown.

Step 2. Change Database State: From Dirty Shutdown to Clean Shutdown?

You can use the ESEUtil /r command to perform a soft recovery of your database. If this works then you can easily mount the database and complete the Exchange database recovery.

eseutil r cmdlet

In case of soft recovery (using ESEUtil /r) doesn’t work then you need to perform hard recovery. To perform Exchange database hard repair / recovery use ESEUtil /p command.


eseutil p cmdlet

Step 3. Repair Database Logs Files

First of all, check the Exchange Logs using the command ESEUtil /ml (with E00 as the starting sequence for the logs).

eseutil /ml “<Mailbox Path>\E00”

After running the above command you will be presented with full details of errors (if present) and database state (clean or dirty shutdown).

It is not true that by using these commands you can fix the unable to mount database (hr=0x80004005, ec=1108) error permanently. You need to spend more time to complete the process depending on the size of the database. You will also face downtime during the process. So, is there any efficient solution to get out of this issue? Yes, let’s move to a better alternative.

EseUtil Fails to Repair the Database: What to do Next?

In case the above method fails to resolve the issue “failed to mount Database” then you can try EDB Converter which repair corrupt Exchange mailbox and EDB file when ESEUtil fails to repair the database efficiently. You do not need to worry about the process, because operating this tool is very simple, even a non-tech user can also use it.

Download Now Purchase Now


When the database is dismounted, you have to suffer from a lot of issues which include downtime. So, to avoid these issues, you need to mount it. That’s why through this write-up, we have elaborated on the different approaches for successfully resolving the “failed to mount database Exchange 2016” error. You can verify the state of the database whether it is dirty or clean shutdown. If found dirty, you can perform soft or hard recovery. However, these processes are quite complex and affect the database integrity. So, the automated tool is the best alternative for an efficient process.

Frequently Asked Questions

Q1. Why an active manager operation failed with a transient error persist?

Ans – Active Manager handling the mailboxes. This error persists during the migration of mailboxes to another database.

Q2. What is the command to perform hard recovery?

Ans –  ESEUtil /p is the command for hard recovery.


By Mohit Jha

Mohit is a Microsoft-certified expert who has assisted thousands of clients with Outlook & Microsoft Office 365 issues. He enjoys writing on email clients as well as data migration. He is always excited about giving troubled readers the most up-to-date knowledge, explanation, and refinements.