How to Fix the Error “MapiExceptionCallFailed: Unable To Mount Database. (hr=0x80004005, ec=-515)”?

Alphy Thomas | Modified: 2021-02-25T10:43:48+00:00 | Error, Exchange Server|

Summary: When user try to mount the Exchange database which is corrupted or its log file are missing then they receive this error occurs MapiExceptionCallFailed: Unable To Mount Database. (hr=0x80004005, ec=-515). This write-up will guide users and provide solution to solve the mailbox database mounting issue and mount it successfully.

It requires users to have database & log files if they try to mount the offline or dismounted Exchange database file. You cannot mount the EDB if the log files are missing and it can go into an inconsistent state. Also, if users have a corrupted mailbox database & log file, then the mounting of the database fails and they receive the following error:

“Failed to mount database ‘Mailbox Database’.
Mailbox Database
Failed
Error:
Couldn’t mount the database that you specified. Specified database: Mailbox Database; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database (hr=0x80004005, ec=-515)
. [Database: Mailbox Database, Server: SERVER.rapidspillrespo.local].
An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)
. [Database: Mailbox Database, Server: SERVER.rapidspillrespo.local]
An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)
. [Server: SERVER.rapidspillrespo.local]
MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)”

In this scenario, users need to check and repair EDB file to mount it back.

Use Steps to Solve the Error: MapiExceptionCallFailed: Unable To Mount Database. (hr=0x80004005, ec=-515)

Here we have provided the steps that help users to fix the error and mount the Exchange database successfully.

Step 1: Check the State Of Database

First, you have to make sure that the database is in Exchange dirty shutdown state or in a clean shutdown. This issue or error occurs when users try to mount DB which is either is not in a clean shutdown state or corrupted. You can use the command given below:

mh command

Output

dirty shutdown

As you can see the current state of the database in the output. If it is a dirty shutdown, it means that the DB wasn’t shut down properly. Then, you have to repair the Exchange database file before mounting it and avoid this error: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515).

Step 2: Repair the Exchange Mailbox Database

When the state of the database is in dirty shutdown then use the following command given below to bring the database into clean shutdown.

eseutil-p-cmdlet

After executing the cmdlet a window will appear, click OK and proceed to repair the DB.

message

eseutil p message

After this, again run the eseutil /mh command to check the state of the database.

When it displays the state: clean shutdown then try to mount the database. If the DB is mounted then the issue or error is fixed but if it does not mount even the database is in clean state, visit this guide – Exchange Database clean shutdown won’t mount.

Check the logs of the database if the state is still dirty.

Step 3: Check Database Log Files

When the database is in dirty shutdown or its not mounting, then check the database log file. Then run the command given below:

eseutil ml “log file path\log prefix

eseutil log file

After executing the command it will display the log file list and the status of the given log files are OK.

Step 4: Recover the Exchange Database

If these log files are clean and the status if OK, then you can run eseutil r command to perform Exchange database soft recovery by using the cmdlet given below:

soft-recovery-process

When the log files are OK then back up it to another location, then delete it from the actual location. Then mount the database.

If this solution doesn’t solve the error MapiExceptionCallFailed: Unable To Mount Database. (hr=0x80004005, ec=-515) and fails to recover or mount the DB. In that case, you can use the Exchange Server Recovery Software provided by SysTools which easily recover the EDB file from corruption with no data loss in a hassle-freeway.

Step 5: Recover Exchange Database Via Exchange Server Recovery Tool

Exchange Server Recovery Software is an advanced tool which supports both offline/dismounted EDB file. It provides scan mode option i.e. Quick and Advance scan which removes corruption from EDB file and repair Exchange mailbox as well as .edb file automatically without using any command.

Download purchase

This utility support various mailboxes such as: users, archive, shared, legacy, disconnected and data items like – mails, notes, tasks, calendars, contacts, journals.

Users can use this tool to extract mailbox from EDB file Exchange 2016 / 2013 / 2010 / 2007 / 2003 and export recovered EDB mailboxes to Live Exchange Server, O365, and multiple file formats: PST, EML, HTML, MSG, MBOX, PDF.

Any Exchange and novice users can use the software, as it provides graphical user interface which reduces the workload and saves their time & effort too. The recovery manager for Exchange database software supports all version of Exchange Server, Microsoft Outlook, and Windows OS.

Bringing It All Together

There are various reasons (like – dirty shutdown, missing log file, etc…) due to which Exchange database corruption may occur which results in dismounting of DB (database). When it is dismounted or offline, it directly impacts the businesses and email-flow. Thus you may face the error MapiExceptionCallFailed: Unable To Mount Database. (hr=0x80004005, ec=-515). Now user have detailed information fix this error and to avoid the complexity of the manual solution, you can use the advanced software described in the above section which easily resolves database corruption Exchange 2010 / 2013 / 2016 and repair the Exchange database without any loss of data in a simplified manner.

Comments are closed.

Exclusive Offers & Deals, Grab it Now!

Systool Offer
Live Chat