Summary: Have you ever encountered a dirty shutdown issue? If yes, then ho through the article where we guide users and provide solution on how to repair Exchange 2010 database dirty shutdown. So, let’s get started!
Microsoft EDB file plays an important role in Exchange Server. As it stores numerous mailboxes and data items like – mails, notes, tasks, calendars, contacts, journals, etc… In addition to this, it is also the main repository of server and prone to corruption. Working at a large scale the server stores data in the batch and all this Exchange data are saved in the .edb file. That’s why it is important to keep it safe and secure from various threats or errors.
There are times due to certain errors like – dirty shutdown state, and much more. Users are unable to mount the database and not able to access the Exchange data. Sometimes, because of some situation the EDB goes into dirty state such as: power outage, hardware problem, storage space issue in Exchange, installation of third-part application, etc…
Generally, the Exchange database goes into dirty shutdown when transaction log file s isn’t committed to the EDB. As we all know that log file has its own importance in Exchange Server. It keep the record of everything that occurred in the Exchange database and when the log file are not disconnected from the database then it directly goes into dirty state.
If the users or organization lose their Exchange data due to this issue then they have to face the consequences such as:
- Bear the heavy financial loss
- The users or client start losing trust in them
- Their company growth will start decreasing
- Have to face the legal charges and penalties
- Sometime, in rare situation they may run out of business
These are some of the major repercussion that they have to go through and to avoid all this trouble it is necessary to repair the dismounted or offline Exchange mailbox database from dirty shutdown.
Errors Occurred When Exchange Database Goes Into Dirty Shutdown State
- Error MapiExceptionNetworkError(hr=0x80040115, ec=-2147221227)
- Unable to Database (hr=0x80004005, ec=-528)
- EDB wasn’t shutdown cleanly (Dirty Shutdown)
Solution for How to Repair Exchange 2010 Database Dirty Shutdown
Users can use the built-in utility provided by Microsoft i.e. Eseutil to resolve the Exchange database dirty shutdown issue. Users can use the Eseutil and ISINTEG command in order to repair, perform defragmentation, & check the integrity of lost as well as damaged Exchange data. Then, users can use the Isinteg after the Eseutil when it fix & test the condition.
You can use this utility when the Microsoft Exchange Server mailbox database gets corrupted or damaged. Users can restore it from backup either by repair it by using the Eseutil cmdlets. It works with the .edb file (Exchange Database), .stm file (Streaming Media), ESE (Extensible Storage Engine), and log file. Before using the utility users have to fulfill some requirement which is given below:
Pre-requisites:
- Login as Microsoft Exchange administrator
- Take the backup of the existing Exchange database file
- Then, use the MS Exchange Server to dismount the complete database
- After that, move the unwanted files and folder. Also, it requires large storage space. (It should be double the size of Exchange database file)
- To test the hard drive for bad sectors use the CHKDSH (Check Disk) tool
Repair Exchange 2010 Database Dirty Shutdown Via Eseutil Tool
1. Now we know that the EDB is in a dirty state and to resolve all this issue user have to perform the soft repair by using the cmdlet described in the below section:
Syntax:
eseutil /r “insert_ExchangeDatabase_file_path\DatabaseName.edb”
2. After executing the cmdlet again check the state of the database by using eseutil /mh command. If the database state is in a clean shutdown state then mount the Exchange database and if stills it is in the dirty state then use the cmdlet given below to repair Exchange databases dirty shutdown state.
Syntax:
eseutil /p “insert_ExchangeDatabase_file_path\DatabaseName.edb”
When you run this command a warning dialogue box will appear then click on the OK button to proceed forward.
3. Use the following cmdlet to defrag the DB and rebuild indexes. Also, it removes the empty page in the Exchange database & rebuilds its indices.
Syntax:
eseutil /d “insert_ExchangeDatabase_file_path\DatabaseName.edb”
4. After that, use the following cmdlet to fix the logical corruption & repair the EDB at the application level.
Isinteg – (Server) -test alltests
5. Then select the recover Exchange database from the MS Exchange Server directory
6. After that, run the Eseutil.exe cmdlet to check that no more threats are shown in the Microsoft Exchange Server
7. Then, use the eseutil /g command to check the reliability of the repaired Exchange database
Example:
eseutil /g "C:\MailboxDatabase2E2E.edb"
8. Use the MS Exchange Server administrator utilities to remount the repaired Exchange database file
Limitations Of Manual Solution
- Time-consuming solution & need ample amount of storage space (Which should be double the size of mailbox database)
- Need in-depth knowledge, technical skills, and hands-on experience
- There is a risk of data loss and you cannot predict that how much data is lost
Note: Many users are new to the Exchange Server environment and if your offline/dismounted Exchange database file gets highly corrupted then it is necessary to recover and repair it. So, to avoid the technicality & complexity of the manual method users can use the Exchange Server Recovery Software which supports this Exchange EDB file (Public & Private) and use by various IT professionals, Exchange, and novice users to recover and repair the minimally and major corrupted EDB file in a simplified way without any hassle. As it provides an interactive graphical user interface which makes the users work a lot easier and save their time as wll as effort too.
This advance utility provides Quick and Advance scanning mode which recovers and repairs the minor and major corrupted offline/dismounted Exchange database file in a hassle freeway without using any command. To recover the .edb file from minimal corruption select the Quick scan and to recover the highly corrupted Exchange database then click on advance scanning mode.
After recovery, users can export the healthy as well as recovered mailboxes directly to the Live Exchange Server 2016 / 2013 / 2010 / 2007 / 2003, Office 365, and various file formats. The software generates the export report in CSV file format which stores the success and fail count of exported Exchange database mailbox data. It supports all versions of Windows OS, Microsoft Outlook & Exchange Server (2003 – 2016).
Working Steps to Repair Corrupted Offline/Dismounted Exchange Database File
1. Download the software and launch the automated tool in your local machine
2. Then, select the add file button to load the corrupt offline Exchange EDB file
3. After that, select the advance scan radio button from scan mode option >> Click on the add button
4. Preview the recovered offline Exchange database, mailboxes, and data items >> Click on the export button
5. Select the required dismounted / offline Exchange EDB mailboxes and export them to the desired export option
Bringing It All Together
In this write-up, we have provided complete information on how to repair Exchange 2010 database dirty shutdown issue by using the solution provided here. Also, we have mentioned the advance solution in the above section that helps users to repair the minor and highly corrupted offline/dismounted EDB file in a simplified way without any hassle. Rest, depending on the users preferences they can select the solution and do their work.
