Link to home
Start Free TrialLog in
Avatar of TechNine
TechNineFlag for Italy

asked on

And Again - Error ID 333 - An I/O operation initiated by the Registry failed unrecoverably.

Hi All

After months of diags, registry checks, hotfixes and hours spent to try to fix this problem, I'm here to submit it to you all

Problem is know on this forum, but never was really fixed if not use a night reboot (that is not a solution, just a workaround)...

This is the Complete error:

Event Type:      Error
Event Source:      Application Popup
Event Category:      None
Event ID:      333
Date:            18/04/2012
Time:            3.13.00
User:            N/A
Computer:      xxxxxxxxx
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   ........

As you can see in the attached image, it happens so many times on System Event log and ANY CHANGES to SAM become impossible, no user can change password or add/delete new users, groups and so on

As I told before, I spent weeks over google to try to fix and my last try before write here was reinstall Windows 2003 from scratch and move all over here, in a week the problem returns itself

Some Tech details on server:
It's a Windows 2003 Standard edition 32 bit
avast! Server Business Protection
IIS6 with a huge number of websites
Backup Exec 2010 Remote Agent Utility

Hardware is based on a brend new
Dell R610
Dual Xeon Quadra Core
4 GB RAM ECC
Perc 6i with 6 x 146 HDD in RAID5

I hope somebody can help us to fix :(

Thanks
Mauro
ErrorID333.png
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Guessing you tried this Fixit?
http://support.microsoft.com/kb/970054
Avatar of TechNine

ASKER

Hi Ve3ofa

Yep, it was allready tryed this way on the "old" server, no changes...

Thanks
Mauro
ASKER CERTIFIED SOLUTION
Avatar of Davis McCarn
Davis McCarn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Davis,

thanks for advices, I'm going to debug IIS, I'll reply when something happens...

Mauro
My experience is that 333 errors are due to exhausted paged or nonpaged pools; do you also get 2019 errors before the 333 errors flood the event logs?
Thanks for reply MidnightOne

we have not error ID 2019 before ID333 errors flood, but to be complete, each flood starts with a IIS crash, I think Davis is pretty close to the correct matter

All here have the same opinion, too much memory is used by IIS App Pools and after some days, this is fragmenting the memory free for other applications and services, when IIS Crash, it restarts automatically and LSASS receive many calls for authentication and use much memory... fragmented memory, maybe this is not the right thing for the correct use of it and "something goes wrong" and flood of error starts because SAM become readonly.

Strange is there is NO error on LSASS or other errors except ID333 and a "normal IIS" restart message:

 Event Type:      Information
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7035
Date:            16/04/2012
Time:            9.30.44
User:            NT AUTHORITY\SYSTEM
Computer:      xxxxxxxx
Description:
The World Wide Web Publishing Service service was successfully sent a stop control.

Thanks
Mauro
The Technet article I posted gives instructions for numerous ways to recycle the App Pool in IIS; at a given time, when memory usage reaches a set value, or after a set number of transactions.
Here is another thread on memory fragmentation: https://www.experts-exchange.com/questions/23975807/How-to-fix-IIS-Worker-Process'-Virtual-Bytes-from-constantly-increasing.html
Hi all

so, unfortually we haven't get the right path to the solution to the "memory fragmentation" (if it is), we still have the problem... after some days, problem returns.

Using memory limit to 1,1 GB to each IIS app pool, the annoying problem become less frequent, but never solved

Did you guys have some other advice/solution?

Thanks
Mauro
You only have 4GB of ram.  If you have more than 3 IIS pools, you need to lower that number.  500MB each, maybe?  Or every day at 3AM?
I cannot install more than 4 GB of RAM because the OS is 32 bit

Every night, is scheduled a IISreset at 2AM also for stats calculation and other internal tasks.

I think 4 GB is enought for 2 Pools of 1 GB also because this IIS Server is monotask, only IIS no database engines or other apps is using memory

With less than 1 GB, App Pools recycle itself every 10 mins... is not a good idea...
Application pools are supposed to recycle on a regular basis. Why is recycling the application pool every ten minutes a bad idea?
Normally, AppPools never recycles is not for an IISReset happens (for example for a IIS Crash or something similar), when app pool recycle, all the user session will be reset, all shopping carts will be blanked and so on...

Anyway, I dont think recycling frequently is the correct way to fix... I think somewhere else is located the solution, I'm trying to find with you guys... that's all...

I noticed on other forums talking about the same problem, they found a workaround (for example, reboot server every night) but this is not a solution and is not really correct for a systemistic point of view...

I hope all you guys agree with me...

Any other ideas?
Thanks for help
From what I read, flawed Java or PHP routines are what aggravate the issue (which is a bug); but, fixing that coding may be the solution.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok All

Sorry for delay in reply to the solution, I definitively use the "split Application pool" solution, exactly i moved half of websites to a new application pool (one for DotNet 1.1 and one for DotNet2.0 respectively), from 2 App Pools to 4 App Pools.

This looks the best solution (maybe) because flood of errors ID 333 do not happens so frequently (now happens 1 only time after my last post)

So, thanks all for suggestions
Mauro