Well that sounds good and is worth cleaning up but I dont think that causes the problems we were having -

We were able to track our problem down to the caching - now I dont know how the caching works but doing it in memeory is a recipie for disaster.

I observed on our live site (Windows server 2003, not sure of all the specs but its a robust machine and has almost nothing else running on it) after splitting DNN out to it own application pool that the number of people visiting the site cause the memory to spike with each new user - and that memory never appeared to be released even when the scheduled cache clear ran

We set all modules to have a cache of 0 and went into the host settings and set it to minimum cache - now our server seems to be very stable and our memory usage for the app pool never goes over 170 megs even with a few hundred users on

I would suggest keeping cache only on Text html modules and then only on ones that may not change - other modules I do not think cache is handled well

We just got this error on a 4.7 site. It went away by itself after a few mins. I checked for orphaned files and there were none. Any other ideas on what can cause this?