Skip navigation

Bad Transaction Logs

My Microsoft Exchange Server crashed and wouldn't let me mount the Private and Public databases. To solve the problem, I tried using the Isinteg and Eseutil utilities but didn't have any luck. Next, I unsuccessfully attempted to perform a backup to free up the transaction logs. After numerous other attempts at a solution, I figured out that edb.chk was pointing to a corrupt transaction log. I renamed edb.chk as edb.old, deleted all the transaction logs, and restarted the Exchange Server services. I was then able to manually mount the Private and Public databases.

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish