Why Exchange 2010 Database Dismounted After Reboot? And The Solution

Solving Exchange server problems is not an easy task, especially when an Exchange server is stuck with an issue like Exchange database dismounts after a simple reboot. The most practical way to resolve such an issue is to first understand the affects and reasons for database stuck dismounting state, and then resolve the error by using the Exchange inbuilt utilities such as ESEUtil. Let’s understand why Exchange 2010 Database Dismounted.

free download

Why Exchange 2010 Database Dismounted?

There could be many reasons but let us see the usual culprits:

  • A sudden power outage or hardware failure can lead to an abrupt reset of the server. This means that the system is not able to smoothly shut down the mailbox database and reconcile the log files.
  • An application which is not application-aware or Exchange server-friendly can lead to locked or deleted files, or lack of diskspace.
  • A malfunction during an update or upgrade can lead to a database not being able to mount.
  • A malware, virus, or ransomware attack.

How Dismounted Exchange Database Affects?

When you try to mount the Exchange server mailbox database and receive an internal processing error, then it means the Exchange database is corrupted or a log file is missing.

Troubleshooting the Issue

Let’s take a situation that the Exchange server suffers an unexpected problem and Exchange database is showing as dismounted, due to power outage, system crash or hardware issues.

On analysing the issue by using the ESEUtil /mh command, it is found that the database state is showing as Dirty Shutdown.

What are the First Things to Check when Exchange 2010 Database dismounted?

  • Check if antivirus or backup application is not trying to access the files as it may lock any files related to the Exchange mailbox database.
  • Disk on which database is installed has enough free space to install the Exchange 2010 database, once it is dismounted.
  • Check if the rights to the folder, in which DB is located, are same as at the time of installation.
  • Check server for any Application Event logs or errors and check for problems.

Resolution Steps

After verifying the above-mentioned things and checking that the system is in place, proceed with the below-mentioned resolution steps:

Restart Exchange after Backup

Take the backup of log files and restart the server. In case the Exchange does not start, then this backup helps you to upload the database. Follow the given steps:

  1. Stop all Exchange services
  2. Take a backup of all E*.files as available in the log directory
  3. Delete all E*.log files from the log directory
  4. Verify that log folder consists of E00.chk, res1.log and res2.log only. Move all other files to a folder
  5. After removing the log files, restart Exchange
  6. Try to mount the database

In this case, if the Exchange database fails to mount, then the backup file is available. However, if the log files are corrupt, then the problem will not be resolved.

Repair Exchange Database with Inbuilt Exchange Utility 

With ESEUtil, it is always best to start with a soft recovery by using the /R parameter. If this fails, use the /P parameter to perform a hard recovery. The hard recovery should only be used as a last option as it purges the data which it deems corrupted. Depending on the damage, it could lead to some serious data loss.

Ideal Solution in Such Cases

A corrupt database needs to be repaired or extracted from scratch in the least possible timeframe and with minimal administrative and resource effort. Unfortunately, this is not possible by using the native tools. For easy and painless recovery, it is suggested to look at Stellar Repair for Exchange.

What does easy and painless mean? Well to recover a dismounted Exchange database by using Stellar Repair for Exchange, you don’t need a complex setup as the application can be installed on both a server operating system or Windows 10 without the need of Exchange Server. Then, follow the below simple steps:

  1. Run the software and Open or Find the EDB file.
  2. Start Scan of corrupt copy. You can add multiple EDB files for scanning.
  3. Preview is displayed for Exchange database verification.
  4. Save scanned EDB to PST or other format. You can also export directly to a Live Exchange Server or Office365.

Why Should you use Stellar Repair for Exchange Software?

Once an Exchange mailbox database gets dismounted after reboot, it is a complex situation as the Outlook becomes unavailable for users. It may lead to business loss, if the Exchange database remains unavailable for a long time. To avoid such cases, install a reliable exchange server recovery software such as Stellar Repair for Exchange which will reduce the recovery time. Here are some advantages of using the software:

  • There is no data loss during recovery as all the Exchange database files or EDB files are recovered.
  • Database is available in original form, and a preview is available for verification
  • The software recovers the database files, irrespective of the cause of error – Exchange server crash, dirty shutdown, database fails to mount, or ESEUtil failure.
  • Deleted and corrupt mailboxes are recovered.
  • Supports Unicode Exchange Database file repair, thus supporting Exchange server recovery in multiple languages.
  • It exports directly to Live Exchange Server or Office 365 tenant.
  • Scanned DAT file can be saved for future recovery.
  • The software supports all Exchange server versions (2019, 2016, 2013, 2010, 2007, 2003, 2000 & 5.5)
style=”text-align: center;”>


It is not easy to deal with Exchange server issues such as Exchange 2010 database is dismounted after reboot. Though cmdlets may help in resolving the error, but it takes some time, if you manage, to resume the services. Also, it is not 100% guaranteed that it will resolve the issue. As time is a big constraint, the most suitable solution is to deploy Stellar Repair for Exchange Software. The software installs in a minute, ensures quick database recovery and acts as a secure recovery solution in times of crises as compared to manual processes.

  1. Barbara J. Rodriguez January 30, 2019
  2. Roberta A. Cardenas January 21, 2019
    • Eric Simson January 21, 2019
  3. Suzanne M. Nilles January 11, 2019
    • Eric Simson January 11, 2019
  4. Eden Laura September 12, 2018
    • Eric Simson September 13, 2018
  5. Shelia Reeves June 18, 2018
    • Eric Simson June 19, 2018
  6. Tara Martin April 24, 2018
    • Eric Simson April 25, 2018

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.