How to fix Exchange Database Dirty Shutdown Error?
Updated On - October 19, 2022
While trying to mount a database, Exchange administrators may sometimes face Dirty shutdown error. This dirty shutdown error will not let them mount the database as it is in an inconsistent state. It is the sudden termination of Exchange Server (due to reasons like power loss) that causes dirty shutdown error.
What is Dirty Shutdown in Exchange Server?
When you make changes in Exchange database, Exchange records this information in transaction log files before committing to the database. But when the log files are not replayed into the database, the modifications you have done are not reflected in Exchange database. In such a case your database is in an inconsistent state. This happens when the log files are corrupt, missing, or damaged. So, when your database is inconsistent, and you are trying to mount this, you will face a dirty shutdown error.
Reasons for Dirty Shutdown
There are many reasons for the dirty shutdown error:
- EDB files are not detached from log files properly.
- Log files are missing from the server.
- Log files are damaged.
- The server is unable to read the log files
The Resolution to Dirty Shutdown
To fix this dirty shutdown error, first you need to check the status of the database to see whether the database is in dirty shutdown or clean shutdown. Use the below command on the Exchange Management Shell (run as administrator) to check the database status:
If the Exchange database is in dirty shutdown state, then you have to fix it. Use the following steps to fix the dirty shutdown error.
1. Create a backup of your entire Exchange database files.
2. . Run eseutil command to check the consistency of the tool. Execute Use below command on the Exchange Management Shell:
3. Now perform soft recovery on the database with this command:
eseutil /r enn /l < path to log files > /d < path to database file > /i
4. Now, recheck the consistency of the database. If it is still in an inconsistent state, then perform hard recovery. Run this command:
5. Now it’s time to perform defragmentation on the database
6. Finally, check the integrity of the database with the below command
Recover Exchange data without log files
Well, if you are still not getting the desired result, then you should recover mailboxes from the EDB file or the available Exchange backup files.
Recoveryfix for Exchange Server Recovery helps you in recovering mailboxes from dismounted EDB files. Yes, you can repair your Exchange database using this tool without log files and then you can export them to Exchange Server or Office 365 directly. In this software, you just need to add your offline EDB file as the source, and the software will automatically repair it. Then it offers you the options to export mailboxes to Exchange server, Office 365 or Outlook PST files.
How to recover inaccessible Exchange Data from offline EDB files?
When you cannot mount EDB files due to dirty shutdown errors, you can try recovering data from offline EDB files by EDB to PST conversion. The entire recovery process is quite easy. You need to follow the steps:
- Launch the installed RecoveryFix for Exchange server tool and select Offline EDB file as the source.
- Add EDB file from your system hard drive and then move ahead.
- Now the EDB file is successfully added as the source. The tool also offers a preview of the mailbox data.
- Now right-click on the source files and select Export mailboxes to PST.
- Select the mailboxes, mailbox folders, apply filters on data (like Date Range and Item Type) and select the required options (to split it into multiple PST & to create Unicode PST). Then click Export.
Now your Exchange mailboxes are successfully exported to PST files.
Conclusion
In this blog, we have dealt with the Exchange database dirty shutdown error by running a set of cmdlets in the Exchange Management Shell. Considering the risk of manual process failure, we have explained the use of a reliable third-party tool to recover the Exchange data efficiently and securely.
Read Related Blog
I hope your post useful for everyone. When I read your blog I get the huge benefits by this blog.
Manual procedure is quite complex, I executed the Recoveryfix for Exchange Server Recovery tool. It’s very simple and efficient. Even though, I don’t possess any technical background, I was able to handle it pretty well. Thanks for highlighting this amazing product and for sharing this information as well!
Is there any other manual method apart from the above mentioned to recover Exchange data?
Hello Everett,
No, there are no other methods. In fact, the given method is not 100% reliable in recovering Exchange database. That’s why we recommend you use Recoveryfix for Exchange Server Recovery to repair and recover all your EDB files.
The way you presented the information is incredible, I mean step-wise instructions are easy to follow and demands less risk. Highly appreciated!
I do not know whether the transaction files are altered or not but the database is not mounting on the Exchange server and showing the error?
Hello Mason,
If you are not sure about the status of the transaction logs, then you can scan the database for the corruption using a profession software. it will retrieve the data and help you to save them properly.
While using the manual solution, i used the transaction logs for recovery. Does your tool also requires such log files?
Hi Samira,
The tool does not require the log but, but only the corrupt EDB file. it will retrieve all the content without needing the log files.
I am reading your blog post and found it quite interesting. The blog you shared is very uniquely & informative. Thanks for sharing this useful blog.
After restarting the Exchange Server after I found out that some of the log files are behaving abnormally. So, I deleted them. But, now the ESEUTIL tool is not getting the desired results. What should I do?