none
eseutil /r is termined with error -501 (JET_errLogFileCorrupt)

    Question

  • After a power outage, our SBS 2011 could no longer could mount the Exchange 2010 IS. In our application log we had ESE 412, ESE 454 & MSExchangeIS 9519 errors.

    • Running a "eseutil /mh" on the DB gave the following result:
      State: Dirty Shutdown
      Log Required: 38765-38766 (0x976d-0x976e)
      Log Committed: 0-38767 (0x0-0x976f)
      Log Recovering: 38765 (0x976d)
    • We ran a "eseutil /r" on the DB and this ended with the following result:
      Operation terminated with error -501 (JET_errLogFileCorrupt...)
    • Re-running "eseutil /mh" gives us the same result above

    The transaction log dir is full of logs. The newest log is "E000000976E".

    Help! What should we next do?


    Thursday, November 15, 2012 11:27 AM

Answers

  • You can run Eseutil /P for this corrupted database, make a copy this corrupted database to some safe place before preforming the recovery .

    The command causes  corrupted pages to delete and creates unused space. Thus, you need to run  Eseutil /D command to defragment the database.

    After running the hard repair through Eseutil /P command, the database  may not be stable as data loss is likely. Thus, it is recommended to either move the mailboxes to a new database.


    Om

    (MCITP,Enterprise Messaging Administrator)

    **My posts are provided “AS IS” without warranty of any kind**



    Thursday, November 15, 2012 12:23 PM

All replies

  • After a power outage, our SBS 2011 could no longer could mount the Exchange 2010 IS. In our application log we had ESE 412, ESE 454 & MSExchangeIS 9519 errors.

    • Running a "eseutil /mh" on the DB gave the following result:
      State: Dirty Shutdown
      Log Required: 38765-38766 (0x976d-0x976e)
      Log Committed: 0-38767 (0x0-0x976f)
      Log Recovering: 38765 (0x976d)
    • We ran a "eseutil /r" on the DB and this ended with the following result:
      Operation terminated with error -501 (JET_errLogFileCorrupt...)
    • Re-running "eseutil /mh" gives us the same result above

    The transaction log dir is full of logs. The newest log is "E000000976E".

    Help! What should we next do?






    • Edited by Oliver Buckie Thursday, November 15, 2012 11:50 AM
    • Merged by Fiona_Liao Friday, November 16, 2012 1:10 AM duplicated
    Thursday, November 15, 2012 11:29 AM
  • Duplicate Post
    Thursday, November 15, 2012 11:53 AM
    Owner
  • Sorry, my browser froze when I posted the 1st question (http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/4e4a67e5-e5fb-4681-8eba-33f4171f6216) and I did not know that it had got submitted.
    Thursday, November 15, 2012 11:58 AM
  • Running "eseutil /ml E000000976E.log" results in an Error: Cannot read log file header. Error -501.

    However, when running on logfile E000000976E.log, the integrity check is passed. Looks as if my last transaction log file is corrupt.

    I thought that "eseutil /p" is a hard recovery and can lead to data loss, that's why I didn't run it.

    Thursday, November 15, 2012 12:01 PM
  • You can run Eseutil /P for this corrupted database, make a copy this corrupted database to some safe place before preforming the recovery .

    The command causes  corrupted pages to delete and creates unused space. Thus, you need to run  Eseutil /D command to defragment the database.

    After running the hard repair through Eseutil /P command, the database  may not be stable as data loss is likely. Thus, it is recommended to either move the mailboxes to a new database.


    Om

    (MCITP,Enterprise Messaging Administrator)

    **My posts are provided “AS IS” without warranty of any kind**



    Thursday, November 15, 2012 12:23 PM
  • Hi Oliver,

    /P must be use as last action if you don't have any way. make sure you have free spave in log drive and then run below cmdlet. Adjust log base file according to you if you are running from other directry. 

    eseutil.exe /r e00 <log base file name> /l "Log Directry path" /d "EDB File location"

    If this not work then use it with /a. /a option will help you to mount DB if few logs missed too.


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

    Thursday, November 15, 2012 12:25 PM
  • I agree that eseutil /p should be the last resort. I have tried "eseutil /r e00 /l /d" - with and without /a - but I keep getting error "-501 (JET_errLogFileCorrupt)" when running the command. Any ideas?
    Thursday, November 15, 2012 12:40 PM
  • I believe some 3rd party tool is the only option to recover in order to avoid a hard recovery of the database.

    Om

    (MCITP,Enterprise Messaging Administrator)

    **My posts are provided “AS IS” without warranty of any kind**

    Thursday, November 15, 2012 1:43 PM
  • Have a look this

    http://www.nucleustechnologies.com/datarecoveryblog/0xfffffe0b-jet_errlogfilecorrupt/


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

    Thursday, November 15, 2012 4:04 PM
  • The same question, will merge to http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/4e4a67e5-e5fb-4681-8eba-33f4171f6216

    Thanks.


    Fiona Liao

    TechNet Community Support

    Friday, November 16, 2012 1:09 AM
  • Hi Oliver,

    Still you have issue ?


    Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

    Friday, November 16, 2012 6:58 AM