Unable to Mount Database Exchange 2007, 2010, 2013 Clean Shutdown Error
This article explains the methods to fix Unable to Mount Database Exchange 2013, 2010, 2007 error in simple steps.
The Exchange environment users might face a situation when they get an error Exchange database clean shutdown won’t mount error. This can happen after a routine patch cycle or a normal reboot. If you are launching the EAC (Exchange Admin Center) and shown with an “Updating” status.
If you run the Exchange Management Shell, it displays the database as dismounted. Due to this situation, users are unable to access the mailbox database. Thus, users have to execute some steps to resolve the issue.
Steps to Resolve Exchange Database Clean Shutdown Won’t Mount Issue
You can try running the following command to check the status of DAG
Get-Mailboxdatabasecopystatus
Then you try to mount the DB manually and you face a very long error message and the command hangs when it is executed.
Now, the next step is to check the shutdown status of the DB. Now, from the same EMS i.e. Exchange Management Shell, you should execute a command to check the status of the database.
Note: Make sure that you are running the command from an elevated EMS.
- eseutil /mh
This command shows that the Exchange Databases are in a clean shutdown state, still the DB won’t mount.
The Exchange Database copies index state shows “Failed” and it logs an event ID of 1009. The sample of the error is shown below:
If the following error occurs, then don’t run the following command unless the Exchange DB is not completely corrupted or in dirty shutdown state:
- eseutil /p
The reason for this is that it might result into some data loss while resolving Exchange database clean shutdown won’t mount issue.
Instant Solution: You can use the Exchange Server Recovery Software to recover and repair Exchange Mailbox 2003, 2007, 2010, 2013, 2016, 2019 from corruption in a simplified way without any data loss.
You may also notice the error encountered in event viewer in the application log associated with the databases and its corresponding copies:
<db namea>, <db nameb>
<db namea> – There were some database redundancy check failures for this database which might be lowering its redundancy and increasing the risk data loss.
Redundancy Count: 1.Expected Redundancy Count: 2. Detailed error(s).
Database <db namea> does not have enough of copies configured to meet the validation criteria.
<db nameb> – There were redundancy check failures for DB <db nameb> that might be lowering the redundancy and putting the DB at the risk of data loss. Redundancy Count:1. Expected Redundancy Count: 2.Detailed error(s).
Database <db nameb> does not have enough of copies configured to meet the validation criteria.
The next step will be to start looking for the DAG itself. This can be performed by opening the Failover Cluster Manager over the Server.
We will not make any changes but will only check if the Cluster is in healthy state. Once you open it, you will see the event logs of the cluster and there will be a red X if there are any issues in it.
While proceeding with the steps to fix Unable to Mount Exchange Database clean shutdown issue, expand the DAG name in the failover cluster manager and see the members in it.
It will help you to see if they are in a healthy state. In this scenario, more than 1 member of Database Availability Group was showing offline due to which the database is not mounting.
The next task is to reboot the servers which are displaying as offline. While starting up, keep an eye on the health of the server while reboot process takes place. Once it comes online, wait for a while to settle down and then reboot the next server.
Once all the reboots are completed, the members should be in online state. Now, if you go back to the EMS and check the DAG status, it should show the databases in mounted state.
Now, the final step is to get the database copies index state back to healthy state. The copy can be updated from the EAC or by running the following command in EMS:
- Update-Mailboxdatabasecopy – “<DB Name>” -Catalogonly
If the above command fails, then the following command will be required to update the copies by deleting the existing ones.
Note: This process may consume a lot of time depending upon the size of your Exchange database.
- Update-MailiboxDatabaseCopy “<DB Name>” –DeleteExistingFiles
Note: User can use the EDB to PST Converter Software to multiple and selective export mailbox from offline Exchange database data to Outlook data file, HTML, EML, MBOX, PDF, MSG file formats in a hassle freeway.
Related: Unable to Open EDB File? Resolve
Conclusion
In this article, we have explained the methods to fix Exchange 2013, 2010, 2007 database clean shutdown won’t mount issue. You can try all the commands mentioned in the above segment and resolve the problem. If the problem still persists, then you can try the advanced solution i.e. Exchange Server recovery software and access all your mailbox data in MS Outlook.