Exchange Dirty Shutdown – How serious issue it is?

Avatar    Lambert Butler     Updated On - 24 Jan 2019

Sometimes while working on MS Exchange Server, dirty shutdown issue leaves us perplexed. Dirty shutdown situation really becomes hell whenever we encounter it. Our large database is at the verge of corruption after all. Exchange Error 550 really takes our breath away.

But what exactly we define as dirty shutdown is abnormal termination of Exchange database .EDB file.  We usually think of dirty shutdown as the indication of damaged database. But that’s not the case at all. It’s just that Exchange database has not been shut normally and therefore it becomes our area of concern as it leads to corruptions in Exchange database .EDB and .STM files.

Mostly priv1.edb file is the main reason behind dirty shutdown. Any irregularity in the file causes exchange email to pretty much shut down and then it just stops us from mounting any mailbox store any further. If you attempt running Exchange inbuilt utility named eseutil /r for repairing Exchange database file, using eseutil /r <log file name> command, you will see that it won’t work at all because of exchange dirty shutdown.

It comes to notice that EDB database is corrupt while running another inbuilt utility eseutil/k. Running eseutil /k on priv1.edb tells us that database is in dirty shutdown state.

Here’s what you get from the results:

File: priv1.STM
ERROR: database was not shutdown cleanly (dirty shutdown).

Above result conveys that 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).

Now you can consider soft recovery using eseutil /r priv1.edb utility. Run the eseutil /r priv1.edb to see if you can do a soft recovery. But if it fails then you get the following series of error log:

Initiating RECOVERY mode…
Logfile base name: priv1.edb
Log files: <current directory>
System files: <current directory>
Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para meter).

In spite of all recovery efforts you still not find the solution. Don’t panic, one solution is there and that is to fix this dirty shutdown issue using Kernel for Exchange recovery software.

The exchange repair software efficiently repairs the priv1.edb database and recovers user mailboxes. The recovered mailboxes are saved to working EDB database and can be then mounted to MS Exchange Server. The exchange recovery is made possible with Kernel for Exchange Server which supports handling and providing results to MS Exchange Server 5.0, 5.5, 2000, 2003, and 2007 databases (EDB and STM files).

Download and evaluate the demo version of Kernel for Exchange Server – Exchange recovery tool, which will let you experience the working features and functions of the software before purchasing the Full version.