News We Recently Launched AD Migrator and AD Reporter.

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

  author
Written By Kumar Raj
Anuraag Singh
Approved By Anuraag Singh
Published On September 16th, 2024
Reading Time 4 Minutes Reading

Summary: Users face this error “unable to mount database. (hr=0x80004005, ec=1032)” , when they use the mount database command in the Exchange PowerShell. It occurs because of deleted or missing log files, corrupted database, permissions, & storage-related problems. This write-up will guide users by providing the solution to fix the error and restore Exchange mailboxes.

Exchange database file plays vital role in IT organization and other industry verticals. It contains various EDB user mailboxes and it may get dismounted or offline due to various reasons such as: unhealthy or damaged mailbox database file, missing log file, hardware problem which result in system crash, sudden power failure, etc… Users are able to access the Exchange database when it is in offline / dismounted state and impaired the email flow.

You can use the mount-database command in Exchange Management Shell to mount the dismounted or offline mailbox database.

Mount-Database -Identity “enter the database name”

If the database is unable to mount, in that case you can add the parameter like -AcceptDataLoss in the above cmdlet. It skips the damaged or corrupt mailbox items & Exchange database mailboxes as well as accepts the data loss to mount the EDB.

However, if users want to restore the healthy or corrupted mailboxes from the Exchange database and avoid this error “unable to mount database. (hr=0x80004005, ec=1032)”, thwn use the advanced Exchange Server Recovery Software provided by SysTools. This utility provides Quick & Advance scan that recovers and repair corrupted mailbox databases automatically without any loss of data.

Download purchase

Users can use these scan mode option that easily recovers & repair EDB file and mailboxes in a hassle freeway. The advance scanning mode also recovers permanently deleted Exchange database mailboxes and data items from offline/dismounted .edb file.

You can extract mailbox from EDB file Exchange 2016/2013 and export directly to the Live Exchange Server 2016/2013/2010/2007/2003 mailboxes, O365 and multiple file formats (PST, EML, HTML, MBOX, PDF, MSG) in a simplified manner.

While using the manual solution to solve the error, users may require additional permission, time & effort. So, it is important to back up the data before starting the process.

How to Troubleshoot the Unable to Mount Database. (hr=0x80004005, ec=1032) Error?

Follow the steps given below to solve the error ec=1032:

Step 1: Check Permission

Users have to assign the right permission before mounting the database. To mount the DB, users have to assign with Database Management Role. It allows admin to create, manage, mount or dismount the database on Exchange Servers. To assign these permission to run the command or parameter, visit Microsoft Exchange cmdlet permission.

Step 2: Check Exchange Database Status

It is mandatory to check the state of mailbox database because if it is in dirty shutdown state, users cannot mount it back. If you want to mount the Exchange database then it should be in a clean shutdown state. You can use the command given below to check the state of offline/dismounted EDB.

mh command

Output

dirty shutdown

If the state is in dirty shutdown that you have to perform Exchange database soft recovery by running the eseutil /r command  given below:

soft recovery process

After that, again check the state of the database by using the cmdlet given below:

clean shutdown

When the database goes into a clean shutdown state, then proceed forward and mount the DB but the state is still in a dirty shutdown then you have to use the eseutil command given below.

Step 3: Recover Exchange Database

Now users can use the eseutil /p command to perform the hard recovery but using this recovery may leads to data loss. So, it is important to back up the database before using this cmdlet.

eseutil-p-cmdlet

Output:

eseutil p message

Then, again check the database state after performing hard repair.

Now the database change into a clean shutdown state. But if the database is severely corrupted then you can use the advanced software i.e. Exchange Server Recovery Software to repair Exchange mailbox and mailbox database from corruption.

Download purchase

As mentioned above, you can download the professional recovery manager for Exchange database utility and export EDB mailboxes to Live Exchange Server, Office 365, and various file formats. After conversion, the software automatically creates the export report which contains the success and fail counts in CSV file formats.

Bringing It All Together

Now you have complete information how to fix this error “unable to mount database. (hr=0x80004005, ec=1032)” by using the ESEUTIL tool. This utility help users to mount the database and resolve the problem. If the Exchange mailbox database is severely damaged or corrupted, you can use the advanced software to resolve Exchange database corruption without any loss of data in a simplified manner. Also, you can recover hard deleted mailboxes and items from offline/dismounted EDB file and export to the Exchange Server, O365 and different file formats.

  author

By Kumar Raj

A versatile writer with the vast knowledge of technology helps to reduce the gap between a user and technology. Provides easy and reliable ways to resolve multiple technical issues, which users encounter in their day-to-day life.