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

Summary: When the offline/dismounted Exchange mailbox database fails to mount then users face this error unable to mount database. (hr=0x80004005, ec=-543). It occurs because of database corruption, sudden shutdown, server crash, database inconsistency, etc… This write-up will help users to solve the error.

When the database fails to mount then users cannot connect their dismounted or offline Exchange database mailboxes in the Microsoft Exchange Server. It also disrupts the mail flow which loss of productivity.

This error “MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543)” appears when they try to mount the offline / dismounted mailbox database using the mount-database command.

The problem occurs due to missing log files. Also, there are various reasons that cause the error with the error code =-543.

1. Corrupted or Missing log files
2. The database is in Exchange dirty shutdown state
3. Exchange Database or Streaming Media File corruption
4. DB is in use or locked by another program like – antivirus

Generally, this error is the result of corrupted Exchange database file, missing log files or dirty shutdown.

Steps to Troubleshoot the Error: Unable to Mount Database. (hr=0x80004005, ec=-543)

Users can follow the given steps which helps them to fix the error and mount the mailbox database on the MS Exchange Server. Also, we have discussed the solution to repair EDB file & mailboxes from corruption and restore the healthy as well as recovered Exchange mailboxes to the Live Exchange Server, Office 365 and multiple file formats.

Step 1: Check & End Other Programs

Make sure that when your are trying to mount the database, first check that the EDB & STM file not used by other program i.e. antivirus software. While scanning, when the Exchange database is in use or lock by antivirus software while scannig, the error may appear while mounting “Unable to Mount Database. (hr=0x80004005, ec=-543)” the database in Exchange PowerShell.

What you can do is to avoid the error is that users can add the exception in the antivirus application in the EDB and log file or you can stop the antivirus program. Also, you can check and stop the program that are using the database that users are trying to mount.

Step 2: Restore the Exchange Mailbox Database from Backup

When the Exchange database is fails to mount, then it displays the error hr=0x80004005, ec=-543. Users can easily restore the mailbox database from the recent backup but if the backup is old and doesn’t contains the existing recent Exchange data. Then, follow the step given below to fix the error & mount Exchange database file.

Step 3: Migrate/Move Log File to Another Location

Migrating the recent log files, that might be corrupted or users can automatically recreates the log files. It helps them to solve the issue & mount the mailbox database without any error.

1. Go to the database log file folder location where it is stored
2. Create the New Folder
3. Then, migrate or move the log file from recent folder to the new one
4. Now, restart the server. It auto recreates new log files & restores the missing log files

Step 4: Ensure the Database State Before Mounting

Make sure that the state of the mailbox database before mounting it. Use the command given below to check the database state weather it is clean shutdown or in Exchange dirty shutdown state.

Output

If the output is in dirty shutdown state, then you can use the cmdlet given below to bring back to it in clean state.

Then users have to again run the eseutil /mh command to check database state.

If users shows the clean shutdown in the output then move forward and mount the database by using the cmdlet in the Exchange Management Shell. In case, if the database state doesn’t change then the users have to perform soft recovery and hard recovery in Exchange 2010 / 2013 / 2016 by using the eseutil /p & eseutil /r command.

However, if the mailbox database is severely corrupted or damaged then in that case users can go for the Exchange Server Recovery Software provided by SysTools that easily repair EDB file and mailboxes from corruption automatically without using the command.

After recovery, users can extract mailbox from EDB file Exchange 2016/2013 and export recovered EDB mailboxes to Live Exchange Server, Office 365 and PST, MBOX, MSG, PDF, EML, HTML file formats in a simplified manner.

Bringing It All Together

The quickest and safest way to solve the issue i.e. unable to mount database. (hr=0x80004005, ec=-543) is to restore the Exchange mailbox database from backup. In case, when the backup is not available then you can use the manual solution to fix the error code =-543. But the manual method leads to loss of data and to avoid all this complexity then you can go for the advanced recovery manager for Exchange database software given in the above section which easily resolves database corruption Exchange 2010, 2013, 2016 and repair Exchange mailbox as well as database file with no data loss & export to the Exchange Server, O365 and different file formats in a hassle freeway.