Summary: When trying to mount Exchange database, users may encounter the “Unable to Mount Database” (hr=0x80004005, ec=-543) error. Common fixes like restarting the server or restoring from backup might not work in such a case. Getting to the root of the issue becomes essential.
Microsoft Exchange server keeps a record of all transactions that are made through it including saving, deleting, modifying, or updating data. This record is saved in log files and the server refers to these files periodically to stay on track with its activities. At the end of each working day when the sever is shut down, modified or newly created log files are committed to the database so that when the server is started up the next time, it can refer the latest version of those files and resume activities from where they were left off.
As is evident from the above description, discrepancies within transaction log files can throw Exchange’s working off track. The most common problem that arises is the database being marked to be in dirty shutdown state. This happens when modified or newly created log files aren’t committed to the database before it is shut down. The reason behind this occurrence is abrupt shutdown of the server resulting from a power surge or technical fault. While the “dirty shutdown” issue can be resolved fairly easily, the scenario where the “database fails to mount” is a bit trickier. As you may have guessed, the cause behind an un-mounting database is also related to log files and resolving the problem involves restoring them in some way. Read on to find out all there is to know about this error and its solutions.
Exchange Database Unable to Mount (hr=0x80004005, ec=-543)
Continuing from the explanation of “Dirty Shutdown” state, if one or more of the log files that weren’t committed to the database at shutting down time are removed / deleted / misplaced, the Exchange database fails to mount (hr=0x80004005, ec=-543). To resolve this problem you need to remove all the log files so that no record of the existence of unsaved log files is left. Thereafter, you need to restore the database from backup or apply an EDB Repair technique to bring it to consistent state.
Solutions to the error
Try one of the following solutions to resolve the (hr=0x80004005, ec=-543) error:
- Move transaction log files to a different folder
- Stop the Information Store and all databases in the storage group
- Verify the integrity of database by running esesutil /mh command, followed by database name. Examine the ‘State’ value under its header information
- If the database is in Clean Shutdown (Consistent) state, you can safely remove all transaction log files (except the current transaction log file) and save them to a different folder.
- If the database is in Dirty Shutdown (Inconsistent) state, restore from the last online backup. In case backup is invalid, perform soft recovery with the following command:
eseutil /r “prefix”<E00> /l <log file location> /d <database location>
- Create Recovery Database and restore data to it
- Use the Exchange Management Shell to create a recovery database with the following command:
New-MailboxDatabase -Recovery -Name RDB -Server “servername” -EdbFilePath “path” -LogFolderPath “path”
Note: The recovery database should not be mounted before the restore.
- Select the Database to be restored from the “Backup Exec Restore” job properties
- Select “Microsoft Exchange Redirection” -> “Redirect Exchange Sets”
- Select ‘Microsoft Exchange” -> “Default options”
- Run the restore
- Once the restore is successfully completed, data from a recovery database can be merged to an existing mailbox or exported to a folder
- Hard repair the database
If the above mentioned techniques don’t work, you will need to perform a hard repair on the database by using the eseutil /p command. However, you should be aware that using this option causes some amount of data loss as the database pages that cannot be repaired as straightaway discarded.
What to do if no conventional solutions work?
If you’re unable to get rid of the “database unable to mount” (hr=0x80004005, ec=-543) error even after applying all the solutions mentioned above, the real issue could be severe corruption of Exchange Database (EDB) files and log files. The safest and most efficient way to fix Exchange database corruption is to repair EDB files with the help of trustworthy third-party software Stellar Repair for Exchange.
Stellar Repair for Exchange is the most hassle-free method to deal with Exchange errors like hr=0x80004005, ec=-543. The tool is equipped with highly progressive scanning algorithms which help it combat any level of corruption in EDB, STM, and log files to bring an inaccessible database to up-and-running state. Additionally, the software supports extracting vital mailbox components stored within EDB files like emails, attachments, contacts, calendar entries, etc. and saving them in Outlook compatible PST format. The product includes a ton of impressive features along with an interactive GUI which make it one of the most preferred solutions to Exchange errors.
Third-party applications like Stellar Repair for Exchange have proven to be the most reliable way to deal with cryptic Exchange problems. Thus, if you’re not an expert at performing technical procedures or have tried everything but not received the desired results, avoid wasting your time and resources and employ this method that will work for sure. You can download the software from here: