How to Fix Exchange 2010 Database Dismounted After Reboot Issue? Complete Solution

Exchange administrators or users usually face my error while using the Microsoft Exchange Server. Among those errors, one such issue is – Exchange 2010 database dismounted after reboot. When they try to mount the Exchange database by rebooting or restarting the Exchange server, users receive an internal processing error.

If the EDB goes into the dismounted state after repairing as well as rebooting the Exchange Server 2010, they can use the solution provided here to fix the Exchange database dismounted after reboot.

Now you know how this issue occurs and if users have to use the Eseutil tool to fix this issue and after that, the problem remains the same, then, in that case, you can use the solution provided in this write-up. But before heading towards the solution let’s know the reason due to which this issue generates.

Cause of Exchange 2010 Database Dismounted After Reboot

1. Power failure
2. Exchange Server crash
3. Hardware problem
4. Log file issue
5. Exchange dirty shutdown state
6. Registry key deleted accidentally

Solutions to Fix the Issue: Exchange 2010 Database Dismounted After Reboot

Follow the solutions given below to resolve the issue i.e. Exchange database dismounted after reboot.

Solution 1: Rename Log File

When the user reboots the Exchange Server, the Exchange database dismounted announces that the IS is incapable to locate the file such as: private and public Exchange database file which means that the prime reason for this issue is missing log file.

To resolve this issue, users have to restore Exchange 2010 database from backup and after that restart the IS. Copy this file “EOO.log file” to the backup folder, if it is newly generated. After if the issue remains the same then use the solution given below.

Now rename the EOO*.log file to the EOO.log and recover the Exchange data from the EDB dismounted file. Then open the log file again, this helps Exchange mailboxes to move headed to the consistent state. Execute the repair cmdlet if the DB isn’t moving towards a consistent state.

1. Search the “EDB*.Log file” in the MDBDATA directory then see the unbroken sequential string in all file names which is figured in hexadecimal.

For Example: EDBOOO0a.log to EDBOOO2g.log and EDB.log. Ensure that there isn’t space in the numbering scheme. When entire files are present & accounted for, then it is also possible that the EDB.CHK exist. After that, move this file to another directory & restart the IS.

2. The recovery procedure will be different if the log file is not available. For Example: Suppose this file “EDBOOO2g.log” is not present then remove all file lower than 2g. Also, keep in mind that you have to erase the EDB.CHK file & open the log file again.

3. Finally, restart the Microsoft Exchange Server and see weather the Exchange dismounted database is mounted or not after restarting it.

Solution 2: Mount Database Again After Reboot Via PowerShell Cmdlet

By using the ESEUTIL utility, we can check the Exchange database state i.e. Clean or Dirty Shutdown. Use the command given below to check the database state and repair it.

1. Command to check Exchange database state:

If the database is not clean then use the command given below to bring it back into a clean shutdown state.

2. Run eseutil /r command to repair the database and fix the log file.

After running this cmdlet, again check the Exchange database state, if it is still in dirty shutdown then use the command given below.

3. Use the eseutil /p cmdlet to resolve the Exchange 2010 database dismounted after the reboot issue.

4. Finally use the Isinteg tool to check & remove the other remaining errors.

5. When the Exchange database have no more issue or error remains then users can mount Exchange database.

Note: If the problem still remains after using both methods, then check whether the database is corrupted or not. If it is severely damaged then users can use the SysTools Exchange Server EDB Recovery Tool which easily removes the corruption from offline/dismounted EDB file without any data loss in a simplified manner and users can import EDB into Exchange 2016/2013/2010 & below version mailboxes in a hassle freeway.

Use Alternative Solution to Recover & Repair Dismointed Exchange Database File

Exchange Server EDB Recovery Tool support both offline or dismounted private as well as public .edb file. The recovery manager for Exchange database utility provides Quick and Advance scan which resolves database corruption Exchange 2010, 2013, 2016 and repair EDB file & mailboxes automatically without using any command. To remove minimal corruption select quick scan and for highly corrupted Exchange database file choose advance scan.

As it provides graphical user interface which makes the users work easier and save their time & effort to repair Exchange mailbox and database file easily. Any technical and non-technical users can use this utility. After recovery, you can extract mailbox from EDB file Exchange 2016/2013 and export it directly to the Live Exchange Server mailboxes, Office 365 and different file formats.

After conversion, the software automatically creates the export report which contains the success and fail count of exported Exchange mailbox data. It supports all versions of Exchange Server, Microsoft Outlook, and Windows OS.

Bringing It All Together

Now users know how to fix Exchange 2010 database dismounted after reboot. There are various reason due to which this issue occur. In order to solve this, you have to check all the methods to mount the Exchange database. Although, it is not easy to fix this issue, this write-up describes the possible manual solution to solve this problem and you can use the automated wizard described in the above section to recover and repair the unhealthy / damaged / corrupted Exchange database file without any hindrance.