Summary: The error ‘Unable to Mount Database. (hr=0x80004005, ec=1032)’ is a database mounting error that appears in the Exchange Management Shell when the Mount-Database cmdlet fails to mount the database on the Exchange server. This may happen due to missing or deleted log files, permissions, corrupt database files, and storage-related issues. In this guide, we discussed a few workarounds to help you fix this error and restore the Exchange database mailboxes to resume connectivity and email flow.
An Exchange database that contains user mailboxes may get dismounted or go offline due to various reasons. When database is offline, users can’t connect to their mailboxes on the Exchange server. This disrupts the email flow and leads to a loss in productivity. Usually, the database is dismounted due to missing log files, damage to the database file, or hardware issues leading to system crash, unexpected shutdown, etc.
However, you can mount an offline or dismounted database by using the Mount-Database cmdlet in Exchange Management Shell.
If the database does not mount, you can add parameters, such as -AcceptDataLoss to Mount-Database cmdlet. The parameter specifies that you accept data loss to mount the database. In this case, damaged or corrupt mail items and mailboxes are skipped. Obviously, using this parameter can lead to data loss as it removes items and changes that are not yet committed to database from log files.
But if you want to restore mailboxes from the database, including the damaged ones, and avoid Unable to Mount Database. (hr=0x80004005, ec=1032) error, use an Exchange recovery software, such as Stellar Repair for Exchange.
The software repairs the damaged Exchange database file, recovers deleted mailboxes, and restores all the mailboxes to live Exchange account. You can export these mailboxes to a new or existing healthy database on your Exchange server and resume mailbox connectivity.
There are manual ways and workarounds also to fix the error but they require additional permissions, time, and efforts. Also, there’s no guarantee that these workarounds will work. Plus, some may lead to data loss. So before proceeding any further, back up the database.
Workarounds to Fix Unable to Mount Database. (hr=0x80004005, ec=1032)
Following are some workarounds to fix the error ec=1032 in MS Exchange.
1. Check Permissions
Before mounting the database, you must assign permission to the user account that you are using to mount the database in Exchange. To mount the database, the user must be assigned with Database Management role.
The database management role allows administrators and users to create, manage, mount, or dismount the databases on Exchange servers. To find the permissions required to run any cmdlet or parameter, refer to this Microsoft guide.
2. Check Database Status
It’s also important to check the current status of the database before mounting. If a database is in Dirty Shutdownstate, it can’t be mounted. To mount a database in Exchange, the database should be in a Clean Shutdown state. You can check the status of the offline database by using the following command in Command Prompt,
ESEUtil /MH <Database_Name>
If the database is in Dirty Shutdown state, you must change the status to Clean Shutdown by using the following command,
After executing the above command, check the status of the database again by using the following command,
ESEUtil /MH <Database_Location>
If it shows the database in Clean Shutdown state, you may go ahead and try mounting the database. If the database status is still Dirty or it does not mount, you may need to recover the database by using advanced EseUtil commands.
3. Recover Database
You may attempt to recover the database by using EseUtil commands for Soft Recovery, if it does not mount and still displays the status as Dirty Shutdown. Further, you may perform Hard Recovery on the Exchange database to recover it when soft recovery fails. However, Hard Recovery is risky and may cause damage to the database and lead to data loss. Thus, proceed at your own risk.
The command to perform Soft Recovery on the database,
After this command, check the status of the database.
ESEUtil /MH <Database_Location>
If the status is still Dirty Shutdown, use the following command to perform Hard Recovery,
Eseutil /p <path to database file>
Again check the status of the database after Hard Recovery,
ESEUtil /MH <Database_Location>
The state of database should now change to Clean Shutdown. However, if the database is severely damaged or corrupt, these commands and workarounds will not work. In such a case, the only solution is to use Exchange recovery software to repair the damaged Exchange database.
As mentioned earlier, you can download and use Stellar Repair for Exchange to repair the database and save the mailboxes in PST format. Once saved, you can create a new database on live Exchange and then import these PSTs.
Alternatively, you can also import the repaired mailboxes from the damaged database file to a new database on the live Exchange server. That too, in a few clicks and without any additional permissions or roles. However, you need administrator account credentials to import mailboxes from a corrupt database to a new database on live Exchange by using Stellar Repair for Exchange.
Once the import is done, you may go ahead and delete the damaged database from the server.
The Exchange database mount error ‘unable to mount database (hr=0x80004005, ec=-1032)’ can be resolved by performing a few operations on the database files by using EseUtil utility. The utility helps to resolve the problem that causes the ‘hr=0x80004005, ec=-1032’ error in Exchange. After the fix, you can reattempt to mount the database. However, if the database is severely damaged or corrupt, you need to create a new database file on the server, repair the corrupt database file by using Exchange recovery software and then import the repaired mailboxes to live Exchange. One such Exchange recovery software that you can use is Stellar Repair for Exchange. It also recovers deleted mailboxes and helps you recover lost mail items from a corrupt or healthy Exchange database (EDB) file.
Ravi Singh is a Senior Writer at Stellar®. He is an expert Tech Explainer, IoT enthusiast, and a passionate nerd with over 5 years’ experience in technical writing. He writes about Data Recovery, File Repair, Email Migration, Linux, Windows, Mac, and DIY Tech. Ravi spends most of his weekends working with IoT devices and playing games on the Xbox. He is also a solo traveler who loves hiking and exploring new trails. Read More