You may occasionally run across a crisis while using Microsoft Exchange Server, wherein the Exchange mailbox stores belonging to a particular Storage Group fail to mount. Generally, this behavior is seen after an abnormal termination of the Information Store service, putting your database into a 'Dirty Shutdown' state.

An Exchange database in 'Dirty Shutdown' state may indicate damages in your Exchange database files, i.e. '.EDB' and '.STM'. In an event of Exchange dirty shutdown, you may get the below error after running 'Eseutil /k' command against your database:

'File: priv1.STM
ERROR: database was not shutdown cleanly (dirty shutdown)
Operation terminated with error -550 (JET_errDatabaseDirtyShutdown, Database was not shutdown cleanly. Recovery must first be run to properly complete database'

In order to work around this problem, you need to stop your Information Store service and back up everything (edb, stm, and log files) to a different disk. You must ensure that you have sufficient amount of free disk space. Now, follow the steps given below to get your database back to the clean shutdown state:

  • Initially, run the following command to verify your database consistency:
    eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"
  • If you find the database state to be 'Dirty Shutdown', perform a soft repair using the below command: eseutil /r "c:\program files\exchsrvr\mdbdata\priv1.edb"

This command replays the transaction log files to make sure that all the database operations are successfully completed.

  • Perform a hard repair of your database using 'Eseutil /p' as follows: eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb"
  • Defrag your database stores by using the 'Eseutil /d' command-line utility.
  • Check the database integrity by running the 'Isinteg' utility from the BIN folder as follows: 'isinteg -s servername -fix -test alltests'
    Isnteg.exe tool was last using in Exchange 2010. If you are using Exchange 2013 or 2016 then use New-MailboxRepairRequest command:
    New-MailboxRepairRequest –Database - CorruptionType

If you fail to recover from Exchange database 'Dirty Shutdown' state using above steps, use Stellar Repair for Exchange application. This software repairs your damaged Exchange database to recover data from corrupt or inaccessible mailbox stores. It quickly scans the entire database and extracts all recoverable items from different user mailboxes, such as emails, appointments, contacts, calendar entries, notes, tasks, and journal records.

Exchange Database Repair Tool has a simple three-step procedure to repair your corrupt MS Exchange databases. Initially, the software enables you to select an Exchange database from a known location or search for Exchange (.EDB) files in any specific volume in your system. Next, the software scans your database comprehensively to display all recoverable Exchange objects in the main interface. Finally, it saves all the recovered Exchange data to a new database file at user's specified location in the system.

Stellar's Exchange recovery solution facilitates an accurate and precise repair of corrupt EDB file components for MS Exchange 2019, 2016, 2013, 2010, 2007, 2003, 2000, and 5.5 versions.

Buy Now
Why Choose Stellar?
Easy to Use


Future Ready


24X5 Supports


Money Back


Most Awarded


Reliable & Secure