[FIXED] How To Resolve Exchange Dirty Shutdown Error?

How to Handle Dirty Shut Down Error and Repair EDB Files to Get a Clean State?

While mounting the database, you might come across the Exchange dirty shutdown error. These dirty shutdown errors make the  Exchange administrators unable to mount the Exchange database on the server.

As we know Exchange Server is needed in order to maintain continuous and smooth email communication inside and outside of the organization irrespective of the business you possess. Hence, we cannot compromise with the Exchange Server dirty shutdown error.

Exchange Server works with the MS Outlook email client to maintain the entire email system running. The Exchange Server provides the ease to its users to access the mailbox info using the Outlook/Outlook Web Access.

MS Exchange Server totally relies upon EDB files to store the user’s mailbox information. And, like other database files, EDB files are also vulnerable to corruption. And, Exchange Server dirty shutdown error is one of the corruptions that may take place in the server.

Due to this error, you may lose all the data and that’s why it is crucial to repair the Exchange dirty shutdown state. So, here I have listed down the two easy ways to resolve this issue.

But before heading towards the fixes, let’s get to know more about the dirty shutdown error in EDB. It will help you to understand why this error occurs on the server so that you can avoid this situation in the future.

What is Dirty Shutdown Error/State in the Exchange Server?

The dirty shutdown is a state of the Exchange Server, in which log files are not committed to the database and this may lead to the data loss. Now you must be thinking what is the log file.

Well, EDB is designed on the JET engines, where log files play a major role as it is responsible for recording all the input/output operations performed in the Exchange Database files.

But, when the log files don’t commit to the database and left behind in the cache memory, then the JET engine shows it as dirty. In this case, the database gets into an inconsistent state. And when the system gets shut down unexpectedly, it throws dirty shutdown error.

Common Exchange Server Dirty Shutdown Errors

When you access such EDB files in the inconsistent state, you may come across the below-mentioned dirty shutdown errors:

‘Database was not shutdown cleanly (dirty shutdown)’

‘Exchange is unable to mount the database that you specified database:0f770558-4961-4a57-9008-2549f8f19116;Error Code:MapiExceptionCallfailed:Unable to mount database. (hr=0×80004005, ec=-528)’

Operation terminated with error -550 JET_errDatabaseDirtyShutdown, Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown

‘Exchange is unable to mount the database that you specified’

Causes of Exchange Server Dirty Shutdown State

These are some common reasons for the dirty shutdown error in Exchange Server:

  • When the EDB files not detached properly from the log files
  • Transaction log files are corrupted
  • The server is unable to read the log files
  • If the transaction log files are missing from the server

So, now you all are well aware of the causes of dirty shutdown error. Now, its time to look for the solutions to fix the Exchange dirty shutdown error.

How to Fix Exchange Database Dirty Shutdown Error? 

Tips to Follow Before Handling the EDB Dirty Shutdown Error:

  • Before starting the recovery process for EDB files, Log files, and STM files always take a backup of the database.
  • You must avoid Exchange database sharing and check whether you have enough free disk space on the system or not.

Method 1: Use Eseutil to Repair EDB from Dirty Shutdown

There are two ways to recover from the Exchange dirty shutdown error using Eseutil:

  • Soft Recovery
  • Hard Recovery

First, try to perform the soft recovery, if that doesn’t work then go with the hard recovery option.

  • In the first step, we need to check the state of the EDB whether it is in the dirty shutdown state or not. For this, we are going to run the below-given command:

eseutil /mh “path of priv.edb”

eseutil/mh “C:\program files\exchsrvr\mdbdata\priv1.edb”

Exchange database shutdown error

  • Check the dirty shutdown state of the public folder using the command mentioned below:

eseutil/mh “C:\ program files\exchsrvr\mdbdata\pub1.edb”

  • After executing the above-given commands, if you found your EDB file in the dirty shutdown state, then execute this command to repair the Exchange server from the dirty shutdown state:

eseutil/r “C:\program files\exchsrvr\mdbdata\priv1.edb”

fix exchange dirty shutdown error

  • Now, again check the state and consistency of the Exchange Database using the commands given in the first step. If it still in the dirty shutdown state, then try the hard recovery option. For this use the eseutil/p command. But make sure to backup all the data because using this way you may lose your data.

eseutil/p “C:\ program files\ exchsrvr\ mdbdata\ priv1.edb”

  • Once the hard repair is done, defrag the Exchange Server Database using the following command:

eseutil/d “C:\ program files\ exchsrvr\ mdbdata\ priv1.edb”

defrag edb file

Method 2: Overcome Exchange Server Dirty Shutdown Error Using Isinteg

There is another built-in tool that you can use in repairing Exchange Database shutdown error which is Isinteg. Execute the command given below to troubleshoot dirty shutdown error:

“isinteg –s servername –fix –test alltests”

isinteg command

Recommended Solution to Fix Exchange Dirty Shutdown Error

If none of the above-mentioned solutions worked for you and you are still getting the Exchange dirty shutdown error, then here I will suggest you try the EDB Repair Tool. This is an automatic way to fix this error and you don’t need any manual work while fixing the error using this tool.

This tool will not only fix the error mentioned in this blog but is also able to fix a wide range of Exchange Database errors. And, the best part of this tool is its interface is easy to understand and one can use it with ease.

So, if you want to go ahead with this solution, then download this tool on your device and left the rest of the work on it.

Steps To Fix Corrupted Exchange Database Server

Step 1: Click on ‘open EDB File‘ and choose the EDB file or to search the files you may click on ‘Find EDB File’.

step 1

Step 2: Select the MS Exchange Server type and click ‘Start’ button.

step 2

Step 3: Select the scanning types, ‘Quick Scan‘ or ‘Extensive Scan‘ and click ‘OK’.

step 3

Step 4: Recoverable file and folders are presented in the left panel; you may see the preview of the item by clicking.

step 4

Step 5: Now select the mailbox folders to recover and then click on the ‘Save mailboxes‘ icon. Fill the destination drive or folder in a dialog box and click ‘OK’.

step 5

Step 6: And the selected Data will be recovered.

step 6

Final Verdict

In this article, I have tried my best to explain to you about the dirty shutdown error in the EDB files and how can you easily resolve this using the inbuilt command tools eseutil and isinteg.

I hope the fixes I have listed down in this article will help you to fix the Exchange dirty shutdown error. If you liked this article and found the solutions helpful then share it with the ones who are having the same issue.

For any other queries and assistance, you can contact and follow us on Facebook and Twitter.