How to Resolve Unable to Mount Database Error

unable to mount database error

Often errors are encountered in Exchange 2016, 2013, 2010 and 2007 server. This can prevent users from accessing their mailbox from Outlook application from their machines. It prevents employees to communicate both internally and externally in an organization. One such error is the unable to mount database error. It occurs when trying to mount a mailbox or public folder onto the server machine. This kind of issue must be avoided at all cost. This post mentions all the ways to resolve exchange database unable to mount issue. Read the entire article and follow the steps precisely to avoid data loss.

Common Errors in Exchange Server 2007, 2010, 2013, 2016

  • Failed to mount database 'Mailbox Database'.
  • Event ID 9519 Event ID 9518.
  • Unable to mount database. (hr=0x80004005,ec=1108).
  • The computer hangs and stops responding.
  • An error message is displayed saying ‘Applying computer settings’ on each login.

Reasons For Outlook 2016 Receiving Error 0x80004005

  • The Exchange server has not been assigned proper security logs.
  • There is some corruption of Exchange server 2016, 2013, 2010, 2007.
  • Some issue in log files that is generating the error.

Manual Approach to Fix Unable to Mount Database Error

Method#1 Use eseutil /p

This is an inbuilt repair tool provided by Microsoft to repair any kind of corruption in the Exchange database. It can be used in the following manner:

  • In Exchange 2013 and 2016, go to C:\Program Files\Microsoft\Exchange Server\V15\Bin.
  • Then, double click on the eseutil.exe file.
  • Next, type in ESEUTIL /P database_filename.edb

The database file name can be found in a path below:

  • C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database10.edb
  • After the command has been executed, try to mount the mailbox again.
  • Verify that the Outlook 2010 error 0x80004005 has been removed from user machine.

Method#2 Use eseutil /ml

  • First, go to C:\Program Files\Microsoft\Exchange Server\V15\Bin in Exchange 2013 and 2016.
  • Then, double click on the eseutil.exe file.
  • Next, type in ESEUTIL /ml.
  • This will check the condition of all the log files on the server machine
  • Then, perform a soft recovery by using the following command:
  • Eseutil /r /l /d
  • here, log filename is: C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00
  • The database filename is same as in the previous method
  • Again, try to mount the mailbox database to Exchange server
  • Verify that the ‘unable to mount database. (hr=0x80004005, ec=550)’ error has been removed.

Method#3 Repair using Exchange Server CD

  • Go to Exchange Server 2010 Help>>Contents Tab
  • Then, expand Deployment>>New Installation>>Preparing to Deploy Exchange 2010
  • Following the instructions in the How to Prepare Active Directory and Domains article
  • It is a guide run the Setup /PrepareAD command from the Exchange server CD
  • It can help remove Outlook 2010 error 0x80004005.

Limitations of Manual Method

Data Integrity is Effected: Following the eseutil command may corrupt the existing structure of the log files. So one should proceed with caution before running this command.

Technical Task: It is not easy following all the steps to remove ‘unable to mount database error. (hr=0x80004005, ec=550)’ error. It requires a basic understanding of log files and Exchange groups that not everyone can grasp.

Automated Solution to Resolve Unable to Mount Database Error

After implementing the manual solutions, one should be able to mount mailbox to Outlook application on their machine. Often the error still persists and one is unable to communicate successfully. In such a case one can opt for Exchange Recovery tool. It is an easy-to-use tool that every administrator must have for common errors in Exchange server. It can quickly repair the Exchange Database(EDB) files and log files to recover useful data. It is better than any manual solution as it retains data integrity of mailbox data.

Conclusion

It is very easy to perform the manual approach only some technical expertise is needed. Microsoft has provided an inbuilt tool to repair common errors in Exchange server. This post describes all the steps needed to resolve unable to mount database error manually. An automated solution has also been suggested that can help any organization that frequently runs into Exchange errors.