| Event Id | 333 |
| Source | Application Popup |
| Description | An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the systems image of the Registry. |
| Event Information | This information from some newsgroups may help you: Software issues: Some anti-virus and backup software may cause this event. Disable suspect software. Or use msconfig to remove the software form the startup. Also you may try to boot the safe mode to see if you still receive the same Event ID. We have seen some cases regarding disk quota. If the user reaches the quota, it may generate event ID 333. Software may damage some system file such as TCPIP.SYS. If you receive this error after installing new software, you may try to remove it. Uninstalling/reinstalling or upgrade the SP . Hardware issues:
------------------------------------------------------------------------------------------------------------------ This information from some newsgroups may help you: ------------------------------------------------------------------------------ CAUSE: This issue may occur if Veritas Backup Exec version 8.6, revision 3808 or 3878, is configured to perform backups on the server by using the Mailbox option. Backup Exec does not properly close the connections that it opens to the Microsoft Exchange server. This eventually consumes all of the available client access licenses. This issue does not occur with the Information Store backup option in Backup Exec. RESOLUTION: Although the license errors will stop appearing, Backup Exec still creates the connections without properly closing them. To work around this behavior, use any of the following methods: 1. Stop and restart the Backup Exec Job engine to release the used licenses. 2. Use the Information Store backup option in Backup Exec instead of the Mailbox option. Based on this analysis, a few items must be addressed when developing the backup and recovery procedures for your SQL Server environment. It is necessary to think about what you are trying to recover from, how much downtime users can endure and the acceptable amount of data loss in the event of a failure. Several options are available that can be leveraged when constructing the BACKUP and RESTORE commands. These additional options can be found on SQL Server 2000 Books Online. Along with the BACKUP settings, ensure a comprehensive Disaster Recovery (DR) plan has been developed, tested and implemented. Executing backups and working through a restore process is a good start for a SQL Server Disaster Recovery plan. Documentation is a key component to a SQL Server DR plan and should begin with the choices you have selected for your recovery model. |
| Reference Links | Many events with ID 333 are added to the System log on a Windows Server 2003-based computer Troubleshooting Server Setup Installing security update MS05-019 or Windows Server 2003 Service Pack 1 may cause network connectivity between clients and servers to fail More Information Question: Disk Corruption |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.