Getting Event ID 333 error messages 60 70 times a minute

[Guest john.stevenson@castlecement.com]

Hi,

 

I have W2K3 SP2 Standard server running SQL 2000 standard. I was

trying to specify a non SA account to run SQL Server Agent jobs but

when I entered the username and password of the account I got the

following error.

 

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.

 

The Event ID is 333

 

On closer examination of the system log I noticed that i was getting

this error 60-70 times a minute and had been doing so for several

weeks.

 

Can anyone throw any light on this problem?

 

Thanks in advance

[Guest Matt]

Re: Getting Event ID 333 error messages 60 70 times a minute

 

Hi John,

 

Not sure I can help with that particular event id. Sounds like it could be

a serious problem with the registry. :(

 

However, I use a script that emails me when an event happens (in the event

log). It really helps to spot these problems before they become serious.

See :

http://eventidwiki.com/blog/2008/03/20/getting-email-alerts-from-the-event-log/.

 

Hope this helps

 

--

 

Matt

 

============================

Add your solutions to Event Log Errors @ http://www.eventidwiki.com

 

 

 

<john.stevenson@castlecement.com> wrote in message

news:a997de12-6419-458a-a1d4-8aea6857ac21@m44g2000hsc.googlegroups.com...

> Hi,

>

> I have W2K3 SP2 Standard server running SQL 2000 standard. I was

> trying to specify a non SA account to run SQL Server Agent jobs but

> when I entered the username and password of the account I got the

> following error.

>

> 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.

>

> The Event ID is 333

>

> On closer examination of the system log I noticed that i was getting

> this error 60-70 times a minute and had been doing so for several

> weeks.

>

> Can anyone throw any light on this problem?

>

> Thanks in advance

>

>