Exchange Server’s dirty shutdown issue
Exchange Server’s dirty shutdown is most prevalent leading to various corruption issues in Exchange Server .EDB and .STM database files. Dirty shutdown is termed as ‘abnormal termination of Exchange database .EDB file’.
Priv1.edb file is the main reason behind dirty shutdown. Any irregularity in this file creates fuss in exchange email and 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.
Running another inbuilt utility eseutil/k makes no use, problem still remains. Running eseutil /k on priv1.edb tells us that database is in dirty shutdown state giving below message,
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).
In such circumstances, you are supposed to take help of Kernel for Exchange Server recovery software to recover mails and other mailbox items. Using this software, all dirty shutdown issue gets resolved and you are able to mount mails on Exchange Server once again.
For free download exchange edb recovery software.