This past weekend our website running with IIS 6.0 stopped handling calls to web services. The log file was filled with the following error until the server was rebooted approximately 8 hours later:
2011-05-08 01:53:12,109 ERROR - Execution permission cannot be acquired.
2011-05-08 01:53:12,135 ERROR - at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission).
This error above appears another 316,871 times in the web log file.
The timing was interesting in that the first error above occurred immediately after the 29 hour applciation pool recycle was scheduled as I see this entry:
A worker process with process id of '758628' serving application pool 'gpsigolf.com' has requested a recycle because the worker process reached its allowed processing time limit.
in the event log (using the event viewer) just before the problem and associated log file filled with the Execution permission error start. This entry is also exactly 29 hours after the previous such entry in the event log.
The server has been running since without issue through several application pool recycles and had been running for five days prior to this problem happening. It is a new server we had migrated to so it had only been up a total of five days prior to running into this problem.
The question is why/how would an application pool recycle cause this problem? Are there certain settings we should avoid like Overlapped Recycling for instance?