The event log generally stops logging new events when the log reaches a size of from approximately 200 megabytes (MB) to 600 MB.
Service pack informationTo resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
02-May-2002 14:28 5.00.2195.5722 45,328 Eventlog.dll
To use the new automated backup behavior after you apply this hotfix, you must add registry keys such as the following keys:
Data value: Value not present or 0 (zero) equals "disabled." (This is the default.) Any non-zero value equals "enabled."
If you are using the "Shut down system immediately if unable to log security audits" (CrashOnAuditFail) policy and if you do not clear the security log after you set the Security registry value to 1, the computer still stops responding when an audit failure occurs.
Description of the AutoBackupLogFiles registry entryUsing this entry causes the Event Log service to automatically clear a full event log and to back up the log file. On computers with the "CrashOnAuditFail" policy turned on, the computer continues to log events (instead of hanging because of an audit failure) if the current log file can be backed up automatically. By default, event logs are stored in the %SystemRoot%\System32\Config folder. If you turn on this registry value, a full log file is automatically backed up in the %SystemRoot%\System32\Config folder, the log file is cleared, and event logging resumes.
If you turn on this registry value, you must make sure to move or delete the backup log files from the System volume. If you do not, the volume may become full. Microsoft recommends that you implement a manual or automated procedure to move or delete the backup log files to prevent the backup log files from consuming all of the space on the System volume. If you turn on this registry value, take immediate action if you receive a "Disk full" message.
When a log file is successfully backed up, event 524 is logged with a source of "eventlog" in the Security event log file. The event is similar to:
For more information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 312571 - Last Review: Jun 19, 2014 - Revision: 1