Exchange database dirty shutdown means the .edb file stopped before Exchange detached it from its transaction logs.
Check State and Log Required with eseutil /mh. Replay the logs with eseutil /r when all of them are present. Missing logs leave a backup restore, an offline export or a hard repair.
Your mail stays inside the database file and its logs when Exchange refuses to mount a database in dirty shutdown. Mount attempts fail until you apply the logs that database needs.
Order matters during Exchange database dirty shutdown recovery, because one fix deletes data it cannot repair. Steps below go from least to most costly.
What Does Dirty Shutdown Mean in Exchange?
Dirty shutdown state means a database stopped before Exchange detached it from its logs, so the logs contain changes the .edb lacks.
Exchange logs a change first and applies it to the database file afterwards. Understanding Transaction Logging explains this for Exchange 2007, where log files are exactly 1 MB.
Reference for Common Eseutil Errors separates the two states for Exchange 2007. Databases shut down correctly detach from their logs, while ones stopped unexpectedly stay attached and need the required logs applied.
Three causes appear in Microsoft documentation.
- Unexpected stop of the server or database
- Full log drive that dismounts databases
- Antivirus scans that lock or quarantine database and log files
Full log disks appear in The log disk is full for Exchange 2007. Scan locks appear in Anti-Virus Software in the Operating System on Exchange Servers for Exchange 2013.
How do You Check a Database for Dirty Shutdown?
Dismount the database, then view its header with eseutil /mh. Microsoft says the file header carries state and diagnostic information, per Eseutil /M File Dump Mode.
Find your file paths first. Get-MailboxDatabase lists your databases.
Get-MailboxDatabase -Identity DB01 | Format-Table Name,EdbFilePath,LogFolderPath
eseutil /mh "E:\Mail\DB01\DB01.edb"
Two lines in the output matter. Sample values are shown here.
State: Dirty Shutdown
Log Required: 4011-4014 (0xfab-0xfae)
State shows the dirty shutdown state or Clean Shutdown. Log Required gives the first and last log you need as a decimal range. Eseutil.exe Examples says to convert that range to hexadecimal to match log file names, so 4011 to 4014 points to files numbered FAB to FAE.
Log Required 0-0 means a normal disconnect with no logs needed. Header dumps with eseutil /mh only report and leave your .edb unchanged, per Eseutil /M File Dump Mode.
On Exchange 2007, Understanding Transaction Logging says all existing logs from the checkpoint forward must be present before you mount. Switches beyond /mh and /r appear in Eseutil Commands Reference.
“Before anyone types eseutil, find the log folder. In most jobs we see, the logs that fix the problem are still on the server.”
How do You Fix Dirty Shutdown With Soft Recovery?
Exchange database dirty shutdown ends after eseutil /r applies the logged transactions that finished and rolls back the ones that did not, per Eseutil /R Recovery Mode for Exchange 2007.
Log check and replay commands look like this. E00 is a sample log prefix. Your log file names show your own prefix.
eseutil /ml "E:\Mail\Logs\DB01\E00"
eseutil /r E00 /d "E:\Mail\DB01" /l "E:\Mail\Logs\DB01"
Recovery that stops on a missing log leads to the next section. Exchange Jet Error -1811 covers a log file that cannot be found at mount time.
What if Exchange Log Files are Missing?
Missing logs in Exchange database dirty shutdown stop soft recovery, so you choose between a backup restore, a hard repair and an offline export.
For Exchange 2007, Reference for Common Eseutil Errors names two ways forward for a dirty database with unavailable logs, backup restoration or repair. Offline export from a copy adds a third.
| Option | Effect on original file | Fits when |
|---|---|---|
| Restore from backup | Database comes from backup | Recent backup exists |
| Offline export from a copy | Source file unmodified | No backup, mail matters most |
| eseutil /p hard repair | Repair changes the file and stops log replay from older backups at the repair point | Server must return and mail is already saved |
How to Run Eseutil /P (Repair) warns for Exchange 2007 that a repair can finish and still leave a database too damaged to mount. Microsoft adds that you can still restore older backups after a repair, but log replay stops at the repair point.
Never point a hard repair at your only copy. Before You Run Eseutil /p explains what it deletes.
Can You Export Mail From a Dirty Database Without Repair?
Yes. Offline converters open a duplicate and export mail from it, even when logs are gone.
Dirty Exchange 2000 to 2019 databases open offline in Exchange EDB Converter from Univik on Windows 10 and 11. Univik Software replays logs from your selected log folder inside a working copy, which mirrors eseutil /r.
Repair inside the app follows when no logs exist. Raw data scanning skips broken sections and processes files that Exchange itself refuses to open.
Univik Software copies a dirty database before it opens the file, so free space in the working folder must equal the database size plus 256 MB. Your original .edb stays unmodified.

SBS 2011 Exchange Database Recovery follows a dirty database with no logs through its export. PST export for those mailboxes continues in How to Convert EDB to PST.
- Exchange database dirty shutdown means the .edb stayed attached to logs it still needs.
- eseutil /mh output lists State plus a Log Required range.
- eseutil /r applies those logs and returns the database to Clean Shutdown.
- Missing logs leave a backup restore, a hard repair or an offline export.
- Place a copy of your .edb and its logs on a second disk before you fix Exchange database dirty shutdown.
Give Univik Software a copy of your dirty database plus the matching logs to preview mailboxes before you repair. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.
Free Download See all featuresQuestions About Dirty Shutdown Databases
How to clear dirty shutdown in an Exchange database?
Replay the logs that Log Required lists with eseutil /r. Microsoft says restored databases need Eseutil /R to reach Clean Shutdown, per Restore data using a recovery database in Exchange Server. Mount the database after eseutil /mh shows State as Clean Shutdown.
Can I mount a dirty shutdown database without logs?
No. Exchange 2007 keeps a dirty database offline without its required logs until you restore a backup or repair the file. Reference for Common Eseutil Errors documents both options.
What does Log Required 0-0 mean?
Log Required 0-0 means the database disconnected normally and needs no logs, per Eseutil.exe Examples. Other ranges name logs you must keep.
Is dirty shutdown the same as corruption?
No. Dirty shutdown databases stay attached to logs that Exchange must apply. Page damage is a separate fault. How to Run Eseutil /P (Repair) says repair mode corrects damage at page and table levels.
Does dirty shutdown happen in Exchange 2019 too?
Yes. Exchange 2019 leaves your restored recovery database in dirty shutdown. Exchange 2016 and SE do the same. Restore data using a recovery database in Exchange Server says that database needs Eseutil /R.
Should I delete old log files to free space?
No, not while a database sits in dirty shutdown. Exchange 2007 documentation says all logs from the checkpoint forward must be present before a mount, per Understanding Transaction Logging.
How can I prevent dirty shutdown?
Keep free space on your log drive and exclude .edb, .log and .chk files from antivirus scans. Microsoft covers a full log disk in The log disk is full (Exchange 2007) and scan locks in Anti-Virus Software in the Operating System on Exchange Servers (Exchange 2013).
Do you need to mount a dirty shutdown database before you open it?
No. Univik Software works on a dirty shutdown .edb while it sits offline on your Windows PC, with no need for Exchange Server or Outlook.
