Event ID 333

  • Thread starter Thread starter Venkat
  • Start date Start date
V

Venkat

Guest
Hi,

We are using Windows 2003 server SP2 Enterprise edition. Our server hangs
often and is generating Event ID 333.

Event ID 333 says "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 system's image of the Registry."

After going through the events, i also found Event ID 2020 which says "The
server was unable to allocate from the system paged pool because the pool was
empty."

So i just wanted to know what was causing these errors. Once if we restart
the server, it works fine for some time and again this events starts
generating and the server hangs.

Are these 2 events interlinked ? How to resolve this issue.

Any help would be greatly appreciated.

Thanks in advance.

Venkat
 
RE: Event ID 333


"Venkat" wrote:

> Hi,
>
> We are using Windows 2003 server SP2 Enterprise edition. Our server hangs
> often and is generating Event ID 333.
>
> Event ID 333 says "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 system's image of the Registry."
>
> After going through the events, i also found Event ID 2020 which says "The
> server was unable to allocate from the system paged pool because the pool was
> empty."
>
> So i just wanted to know what was causing these errors. Once if we restart
> the server, it works fine for some time and again this events starts
> generating and the server hangs.
>
> Are these 2 events interlinked ? How to resolve this issue.
>
> Any help would be greatly appreciated.
>
> Thanks in advance.
>
> Venkat
>
>
Sounds to me like you have some kind of memory leak.

Use task manager to find out which process or processes show steady increase
in memory or virtual memory as the hours pass since last reboot.
--
Regards,
Newell White
 
RE: Event ID 333

I have a question here...does this server or machine act as a print server or
Terminal Server? I have had this issue on Terminal Servers and I'm suspecting
that it is related to the Print Spooler. When this happens to me, I will stop
and start the Print Spooler and I will still get the message, but the login
time is cut dramatically. Thus far, the only solution for it is a reboot.
Look on your machine and see if you have any 3rd party Port Monitors. I have
noticed in the Event Viewer that when the issuse starts, a Port Monitor
message preceeds the problem. I would suggest looking into this.

"Venkat" wrote:

> Hi,
>
> We are using Windows 2003 server SP2 Enterprise edition. Our server hangs
> often and is generating Event ID 333.
>
> Event ID 333 says "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 system's image of the Registry."
>
> After going through the events, i also found Event ID 2020 which says "The
> server was unable to allocate from the system paged pool because the pool was
> empty."
>
> So i just wanted to know what was causing these errors. Once if we restart
> the server, it works fine for some time and again this events starts
> generating and the server hangs.
>
> Are these 2 events interlinked ? How to resolve this issue.
>
> Any help would be greatly appreciated.
>
> Thanks in advance.
>
> Venkat
>
>
 
Back
Top