3

Last week our Application Log appeared to be corrupt. Event Viewer said the log was 20MB, and had 18,446,744,073,709,550,735 (0.000000000008674 bits each) records (which can not possibly be true), and mmc would crash whenever we tried to view the log.

We cleared the Application log, and it appears to be logging data because when we go to the Windows Logs section in mmc, it says the Application Log has 1,985 events (in 3MB), but when we actually click on the log to open it, it says there are zero events.

I have made sure that all filtering is off. Any ideas?

Edit: Problem appears not to be an isolated incident. See Application Event Log keeps getting corrupted.

Community
  • 1
yakatz
  • 1,213
  • 4
  • 12
  • 35

2 Answers2

3

Based on Shane Madden's answer but with no restart required... (This is an e-commerce production server, so we can't restart easily.)

  1. In Event Viewer, right click the Application Log.
  2. Change the name of the log. I added _2 at the end.
yakatz
  • 1,213
  • 4
  • 12
  • 35
  • Nice! Make sure to accept this answer for people who find this question in the future with the same issue; I believe it'll let you do so once the question is 8 hours old. – Shane Madden Jan 09 '12 at 22:31
  • Two days until I can accept it... – yakatz Jan 09 '12 at 22:38
  • Ahh - 200 rep might be the threshold for the faster accept, then. Though I can't find the documentation on that at the moment.. – Shane Madden Jan 09 '12 at 22:41
2

2^64 is near the number that you're seeing. Coincidence? I think not!

Sounds like the log's definitely corrupt; your best bet may be to just nuke it (see here) and start clean.

Shane Madden
  • 114,520
  • 13
  • 181
  • 251