Problem with Application Event Log

  • Thread starter Thread starter Hornet
  • Start date Start date
H

Hornet

It appears that the application event log on one of our Windows 2000 Service
Pack 4 systems is corrupted. I can fire up the event log viewer and view
the system and security event logs without any problems.

When I attempt to view the application event log, everything is blank. When
I go back to view the system and security logs, they go blank as well.

I found the KB article, 829246 - Event Logs Are Corrupted. I've applied the
hotfix to my system. The application of the hotfix did not fix my problem.

I went ahead and cleared out the Application Log so everything is working
fine. I believe I will have the problem again when log fills up.

Any suggestions if the problem (even with the application of the hotfix)
crops up again after the log fills up?

Thanks.
 
--------------------
From: "Hornet" <[email protected]>
Subject: Problem with Application Event Log
Date: Mon, 2 Feb 2004 14:19:06 -0500
Newsgroups: microsoft.public.win2000.general

It appears that the application event log on one of our Windows 2000 Service
Pack 4 systems is corrupted. I can fire up the event log viewer and view
the system and security event logs without any problems.

When I attempt to view the application event log, everything is blank. When
I go back to view the system and security logs, they go blank as well.

I found the KB article, 829246 - Event Logs Are Corrupted. I've applied the
hotfix to my system. The application of the hotfix did not fix my problem.

I went ahead and cleared out the Application Log so everything is working
fine. I believe I will have the problem again when log fills up.

Any suggestions if the problem (even with the application of the hotfix)
crops up again after the log fills up?

Thanks.
Click to expand...
--

The hotfix will only prevent the log file from becoming corrupted the next time it becomes full. It will not repair a log file that is
already corrupted. You did the correct step in clearing the log file after the hotfix was applied. Now that the hotfix is applied
the issue should not happen again.

Bill Peele
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
 
Back
Top