Theme Graphic
Theme Graphic

Exchange Server Recovery | PST Recovery

Stellar’s Email Recovery Solutions encompasses a wide range of software for almost any data loss situation ranging from accidental deletion...

Subscribe

Author

I am a Data recovery expert and providing solution for MS Exchange server, Lotus Notes, MS Entourage Database and MS Outlook. I would like to keep update the readers of this blog about Exchange Server Recovery, Lotus Notes Recovery and Exchange BKF recovery techniques.

Archive

Open 2010

Tags

Posted on Monday, March 29, 2010 at 1:49 AM

Resolving 'Logs could not be interpreted' Error in Exchange Server


Exchange Server transaction logs are stored on Exchange computer hard drive and are crucial for the working of database (*.edb) file. When you start any Exchange Server, ESE (Extensible Storage Engine) checks the database for consistency. This information is revealed by a specific flag in the database header that shows database status as dirty or clean. The dirty database status indicates that there are some uncommitted transactions that need to be replayed. Exchange tries to replay them at the time of mount, but may fail if cannot read them. The reason can be corruption of log files. Such situations can force you to use an EDB Repair Software.

To comprehend these potential problems, consider you use Exchange Server 2007. You experience an unexpected crash (Dirty database shutdown). The next time when you try to mount the database, it gives the below error message:

-1852 0xFFFFF8C4 JET_errLogCorrupted

Logs could not be interpreted 4294965444


The related event ID is 9513. You can observe the same error when restoring the database from backup.

Cause

Event 9513 in Exchange Server 2007 and the above error suggest that the Information Store Service, which is using ESE, cannot read the transaction log files because they are corrupt. As a result, when you try to mount the database after dirty database shutdown or attempt to restore from backup, ESE fails to replay the log files and also to bring the database to a consistent state.

Solution

Following are few concrete solutions that you can apply to solve the depicted issue:

1. Check the application event log for more ESE events. This can help you to find the specific reasons and solutions to the existing problem.

2. Try to duplicate the behavior- mounting the database or restoring from backup.

3. Try to restore the database while excluding the corrupted log files and its sequence. But this operation will cause data loss

4. Run eseutil /p command. Keep in mind that this is a hard repair command and is likely to delete the corrupted and unreadable pages

5. Use a third-party EDB Repair utility. An EDB Repair Software can analyze the corrupted database and extract the lost data using powerful, yet safe, scanning algorithms.

EDB Repair Tool is an efficient EDB Repair product that scans corrupted Exchange database and extracts the mailboxes in readable PST files. The software supports Exchange Server 2007, 2003, 2000, and 5.5. With an interactive, user-friendly design, the software is easy to operate. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.
Bookmark: Submit To Digg Submit To reddit Submit To del.icio.us Bookmark With StumbleUpon Bookmark With FaceBook Bookmark With Google Bookmarks   Share: Share By Email By Email

0 comments on "Resolving 'Logs could not be interpreted' Error in Exchange Server"
No comments posted yet.

Leave A Comment
Subject:


Comment:
   Bold Italic Underline          Code Link Image Horizontal Rule


Because you do not have or are not logged in to your Programmer's Heaven account, please enter your name.

Name:


To help prevent comment SPAM, please enter the magic code '214' in the box:




Posting Rules
Please follow these rules when posting comments on blog posts.
  • Do not post anything that is racist, hate speech or of a sexual or adult nature.
  • Do not post or link to anything that infringes copyrighted laws.
  • Posting about security or legal topics is fine so long as you are not glorifying or encouraging people to perform illegal activities.
  • Both the author of this blog and the Programmer's Heaven administrators may delete any inappropriate comments without notice at their own discretion.
 

Recent Jobs

Official Programmer's Heaven Blogs
Web Hosting | Browser and Social Games | Gadgets

Popular resources on Programmersheaven.com
Assembly | Basic | C | C# | C++ | Delphi | Flash | Java | JavaScript | Pascal | Perl | PHP | Python | Ruby | Visual Basic
© Copyright 2011 Programmersheaven.com - All rights reserved.
Reproduction in whole or in part, in any form or medium without express written permission is prohibited.
Violators of this policy may be subject to legal action. Please read our Terms Of Use and Privacy Statement for more information.
Operated by CommunityHeaven, a BootstrapLabs company.