Exchange 2007 Problem - URGENT!

Posted on 2009-12-26
Last Modified: 2012-06-27
Looks like the Exchange 2007 booted unexpectedly.  Database in Dirty Shutdown status.
ESEUTIL /ML E00   shows E00.LOG corrupted.
Have LCR setup, but it is INITIALIZING status and I cannot restore from the LCR copy (storage group must be in healty status)
Tried ESEUTIL /r E00 and it fails with one or more logs missing or corrupt.

NEED HELP!  Please advise.    Ex2007 with all corrections and SP's applied.  Running on Win 2008
Question by:rstuemke
    LVL 74

    Accepted Solution

    Do you have a backup of the logs?

    If not you are going to need to run ESEUTIL /P to do a hard recovery on the database.

    Before you do anything make sure you have a copy of the store files (I like to take the view of not making things any worse)
    LVL 21

    Assisted Solution


    If a database is in a "Dirty Shutdown" state, all existing transaction logs from the checkpoint forward must be present before you can mount the database again. If these logs are unavailable, you must repair the database with Eseutil /p to make the database consistent and ready to start.

    Caution :
    If you have to repair a database, some data may be lost. Data loss is frequently minimal; however, it may be catastrophic. After running Eseutil /p on a database, you should complete repair of the database with two further operations.

    Check these links:,289625,sid43_gci1148988,00.html

    Faraz H. Khan
    LVL 74

    Expert Comment

    by:Glen Knight
    Please see here for a ESEUTIL /P reference :

    also once you have performed a hard recover make sure you run an ISINTEG on the database before you remount it.

    Once both utilities have been run then re-mount the database.
    LVL 74

    Expert Comment

    by:Glen Knight
    If it's urgent then just go straight for the EDEUTIL /P databasename.edb
    as per my first post then run ISINTEG and follow the instructions.  The store must be dismounted for the correct options to appear on ISINTEG.

    Author Comment


    Ran a check on the logs and only E00.log was corrupted.  Ran a ESEUTIL /R E00 /I /A to ignore corrupted logs as long as database integrity would not be compromised.  Worked and database recovered fine.  Thank you

    Author Closing Comment

    Awarding Points because I know solution provided would have worked and willingness to answer my question.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Why spend so long doing email signature updates?

    Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

    In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
    To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now