Tagged: Work

MS Exchange Dirty Shutdown: Explained and Troubleshooting

I’ve been using Microsoft Exchange 2003 and playing with it for almost 4 years and during these 4 years, I have encounter many kind of issues involving this product. And the father of all this “issues” is exchange database “Dirty Shutdown”. This is by far the worst and most common issues that I’ve heard or experience.

So what is exchange “Dirty Shutdown”?

As the name suggest, “Dirty Shutdown” is when the MS Exchange shutdown dirtily, whatever that means. All jokes aside, it’s actually really bad even disastrous. A “Dirty Shutdown” happens whenever the Information Stores have not been closed in a properly manner. This might be due to power outage or power surges or any other action that might caused the server to be inproperly shutdown.

Most people 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.

From TechNet

A Dirty Shutdown state does not indicate the database is corrupted or damaged. A Dirty Shutdown state indicates only that the database files were not detached from the log stream correctly. Therefore, before you can start the database again, you must first recover the database files.

The next time that the database is mounted, this recovery is run automatically. If automatic recovery fails, you can use the Microsoft Exchange Server Disaster Recovery Analyzer Tool to analyze the reasons for failure. After analysis, the Exchange Server Disaster Recovery Analyzer will provide recommendations for manually recovering the database files.

So how to check for Dirty Shutdown?

Login to you Exchange Server that you want to run the check and follow these steps.

  1. Click Start, and then click Run.
  2. In the Open box, type CMD, and then click OK.
  3. Switch to the C:\Program Files\ExchSrvr\Bin folder, type one of the following commands (as appropriate to your situation), and then press ENTER:
  4. type in eseutil /mh <My_Database_Name.edb>
    eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"

    Find State: when you have “Dirty Shutdown”  it will say “State:Dirty Shutdown”.

Continue reading

All in the days work….

“Whoaaa!! down boy, down!” so I said to the vicious stomach of mine. It’s an hour before lunch and my haven’t-had-breakfast-starving-like-crazy-stomach growling to the max, begging to be fed with a sacrificial lamb, so to speak.

While dilly daling around the department cubicle one-after another looking for some grubs, I hear a voice, not too far away from the place where I’m standing. It’s the voice of an unfamiliar one, puzzled when he couldn’t access his email. I turn, and I saw a man staring at me straight into the eyes, hoping for some answers. The man goes by the name “Flash”. The groggy voice I heard earlier was actually due to the flu he’s having. Then he told me that some other users are experiencing it too. I hope for the best that nothing big happen. I cannot tahan alreay, sooo lapar ( ̄へ ̄) (excuse my english please ( ^_^)   )

As I went to the server room, and trying to access the email server, a coleague of mine told me that department was bombarded with calls asking why they can’t access the email. Hmmm….this looks like a major problem. After done some investigation, we found out that the system having a “bad” day and decide to take a bit of extreme measure and reboot the server. The uneasiness in my heart starts to build up bit by bit, as my effort to bring up the service bear fruitless. ( ̄へ ̄). Sorry beloved stomach, looks like you have to bear it a little bit more….. (to be continued)