How to Get Rid of Dirty Shutdown Problem in Exchange Server

Introduction

In this how to we will talk about dirty shutdown problem in Exchange Server and how you can overcome it. There can be many reasons for Dirty Shutdown but the two major reasons are: Corrupt Database and Corrupt Logs. In order to resolve the issue we need to perform soft and hard recovery.

Steps
(5 total)

1

Verify Exchange Database State: Dirty or Clean shutdown

First you need to verify the Exchange Database State: whether it is clean shutdown or dirty shutdown. To check this you need to type the following command: eseutil /mh "path of Database"

2

Perform Soft Database Recovery

Run ESEUtil /r command to perform soft database recovery. See the screenshot for full command syntax for soft recovery.

3

Perform Hard Recovery

In case Soft Recovery fails to eliminate the problem of dirty shutdown problem you can try hard recovery also. The syntax for hard recovery is:Eseutil /cc “Path of the restore.env containing folder"

4

Run ESEUtil /mh to check state

run 'eseutil \mh' command to check the consistency of database. It should be Clean Shutdown.

5

Perform the Offline Defragmentation using Eseutil

Now if the state is clean shutdown you can perform offline defragmentation using eseutil /d command.
syntax for offline defragmentation is: ‘eseutil /d Database_Name’

Conclusion

Most of the time the above inbuilt utility in Exchange Server works and you can resolve the problem of dirty shutdown problem.

A vendor claims Ciscos hardware routers would out perform Sophos firewalls as gateway devices. Each vendor claims their stuff is superior. What do you think, is the hardware advantage enough to overcome the extra hop/processing cost?