I/O operation initiated byt the Registry failed unrecoverably

[kgraw21]

I get this error from a Windows 2003 Guest,

Evenet ID 333

"An I/O operation initiated byt 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"

Has anyone seen this before?

[Ancan]

Yes, we get it in our ESX 3.02 environment. It seems to randomly affect guests after migration between hosts, and is very disturbing. A reboot or two of the guest O/S usually resolves it, but that's not what we want to do on our systems.

I have a feeling that the issue started after moving from 3.01 to 3.02.

[xMichal]

Hi, I have same problem. I get it in ESX 3.5, when I was migrate from vmware server 1.04 thought vmware converter 3.0.2. When I rebooting, It seems to be good, but not for a long time. It's occurs again during 24h.

Have anyone idea to resolve it ?

[kastlr]

Hi,

did you check the following MS articles?

http://support.microsoft.com/kb/951031/en-us

http://support.microsoft.com/kb/927653/en-us

http://support.microsoft.com/kb/950310/en-us

[Brasshat]

I recently started seeing this error too after I used VMware Converter 3.0.3 to convert two physical Windows 2003 to VM's on Virtual Server 1.0.6.

When I reboot the VM, it's OK for a few hours then Event ID 333, Source Application Popup is non stop like every 10 seconds. I checked my page file size and ran CHKDSK but I'm still seeing this event logged consistently. The services that the two servers host seem to be fine though as I am not seeing any performance issues.

I checked the links earlier in this post but I'm not running any Symantec Products on these boxes, the host CPU is a Xeon 64-bit, and I don't have RIS installed.

Anyone get anywhere with resolving this?

[Brasshat]

I think we finally fixed this one. I had two Win 2003 VM's showing this behavior post P2V conversion. One was running SP1 and the other SP2.

For the SP2 box, I removed the current page file, rebooted, created a new page file, rebooted, and then monitored. It's been a few days now and the error has not come back.

For the SP1 box, I did the same thing as above, but the error came back a few hours post-reboot. So then I updated it to SP2 and ran the same steps as above again. This time it has been error free now for a few days.

Hope this helps someone!