An I/O operation initiated by the Registry failed unrecoverably

[tdubb123]

Hi I have a problem with a vm recently.

i have a win2003 SP2 mssql 2000 vm that in recent weeks have a rife quantity of event id 333 in the sys logs

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

A little history, this vm was running on a cluster DRS Enabled. The ESX host is 3.0.2 61618 build and on Virtual center version 2.5.0 Build 84767. It was running fine for a long time.

then we moved the cluster to another Virtual center (version 2.5.0 Build 64192).

Then after a day or so, we were getting these errors on this one vm. And only this one. Event ID 333.

After applying a bunch of hotfixes and patches. the error temporary went away. but return after a few hours.

So I tried to shutdown the vm to move it to another host on the cluster. The reason I did not do vmotion is because the CPU of the ESX server the vm was on is not compatible with the other hosts. Same manufacturer but different steppign or something. So I shutdown the vm and migrated it to another ESX host on the same cluster. But this ESX host is on version 3.0.1* *build 34176.

so I booted the vm up and after a few hours or in some cases a few minutes, the system completely hung up and saw available physical memory going to zero without seeing any process in task manager using up this memory.

After a while I decided to move the vm to another cluster. Both ESX hosts are running 3.5 build 120512.

This time the vm ran fine without any memory resource depletion. All errors 333 disappeared.

What do you think the problem is? Is this a bug on earlier versions of ESX or VC?

[wila]

Hi,

Did this happen right after patch tuesday?

Sounds suspiciously much like

Check the system eventlog and verify at what time your automatic patches started, on my VM it started 35 seconds after the update was scheduled....

--

Wil

[stoutat]

Did you ever find a fix for this? I rolled out 3 new terminal servers and one of the three is showing the event 333 in the event viewer. The odd thing is, it's working fine. Please assist if you can!

[rizo73]

Hi -

Maybe worth checking SQL Enterprise Manager memory settings

Rgds

[AlbertWT]

You're not alone here mate, my Windows Server 2003 VM also got hangs today and i was able to resolve it with hard reset:

Event Type: Error

Event Source: Application Popup

Event Category: None

Event ID: 333

Date: 25/05/2010

Time: 3:33:47 PM

User: N/A

Computer: RST01

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 system's image of the Registry.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 00 00 00 00 01 00 6c 00 ......l.

0008: 00 00 00 00 4d 01 00 c0 ....M..À

0010: 00 00 00 00 4d 01 00 c0 ....M..À

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

any clue how to fix this error ?

Kind Regards,

AWT