I have just moved over from a Windows 2003 hosting environment to Windows 2008.

All my sites (300 +) are in asp.net 2.0 and since moving to the new environment (2 x win 2008 servers), I am randomly getting the following error message appear:

Attempted to read or write protected memory. This is often an indication that other memory has been corrupted 

The only way to rectify the error is to recycle the application pool / kill the worker process so it starts again/

It is happening on the two servers and appears to happen to sites when they experience heavy load. I have tried both having the sites in a shared application pool and dedicated application pool. I have also changed session state from in process to using a state server.

Has anyone else experienced this issue running asp.net 2.0 sites that have been working fine for years in II6 6.0 and then experiencing this issue in iis 7?

Any help at all will be appreciated.. I am at my wits end and have hundreds of clients on my back asking why their sites keep going down.

Have you checked the physical RAM itslef?  Reseat it?  Replace it?

Jeff 

Hello,

I'm having same issue on w2k8 R2 server which is virtual so there is no way that it could be caused by phisical RAM.

I guess it's because server is x64 but application is 32bit.

But I have no idea how to fix it =\

rebelok:

I'm having same issue...

Maybe, maybe not.  Have you tried the forums at www.iis.net, same login as here?  Have you checked with your hosting company?

Jeff