Event logs stop responding after 3601 events

[Systems Admin]

I have two w2k domain controllers running AD, DNS and
DHCP. Both servers have taken a hit in that when the
systems log gets to 3601 events, none of the events will
open, and the only way to recover is to save the event log
out, and delete the events from the log file. Thinking
that the problem was that the events were not auto
deleting, I left one server with delete after 7 days, and
I set the primary server to delete as needed. It still
occurs. Searching the knowledge base yeilded no solutions.

Any help is greately appreciated

cschaefer_at_hafeleamericas_dot_com

 

[Dave Patrick]

The temporary fix;
You might try changing the file properties to "Overwrite as needed"

Then; Control Panel|Administrative Tools|Services|Event Log Service|General,
set the "Startup Type:" to "Disabled" restart the pc, then delete (or move)
the corrupt *.evt file(s) from %windir%\system32\config then set the Event
Log Service "Startup Type:" back to "Automatic", restart for effect.

The more permanent fix;
http://support.microsoft.com/default.aspx?scid=kb;en-us;829246&Product=win2000

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
|I have two w2k domain controllers running AD, DNS and
| DHCP. Both servers have taken a hit in that when the
| systems log gets to 3601 events, none of the events will
| open, and the only way to recover is to save the event log
| out, and delete the events from the log file. Thinking
| that the problem was that the events were not auto
| deleting, I left one server with delete after 7 days, and
| I set the primary server to delete as needed. It still
| occurs. Searching the knowledge base yeilded no solutions.
|
| Any help is greately appreciated
|
| cschaefer_at_hafeleamericas_dot_com

 

[Systems Admin]

Dave,

Thanks for the quick response. As I said, the servers are
already set to overwright as needed, but I will ready
through th rest of your message and also through the
linked MS doc, and after determining which is lest likly
to bring my systems down, implement the fix.

Thanks for taking the point!

CS