asp.net - Intermittent PolicyException: Execution permission cannot be acquired -

Text after "

We intermittently see the following exceptions shortly after an application pool recycle in ASP.NET applications: < / P>

  System.Configuration.ConfigurationErrorsException: The file or assembly could not load Microsoft.Web.Mvc, version = 1.0.0.0, culture = neutral, publicKeyToken = null 'or one of your dependencies. Failed to allow execution. (Exception with HRESULT: 0x80131418) --- & gt; System.IO.FileLoadException: Failed to allow file or assembly to execute 'Microsoft.Web.Mvc, version = 1.0.0.0, culture = neutral, public keypoint = faucet' or one of its dependencies could not be loaded. (Exception from HRESULT: 0x80131418) Name File: 'Microsoft.Web.Mvc, Version = 1.0.0.0, Culture = Neutral, PublicKeyToken = Nulled' --- & gt; System.Security.Policy.PolicyException: Permission can not be obtained for execution. On System.Security.SecurityManager.ResolvePolicy (proof proof, permission asset reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet & False, Boolean Check Exclusion Promotion) (Proof proof, permission Asset reqdPset, PermissionSet on System.Security.SecurityManager.ResolvePolicy OptPset, PermissionSet denyPset, PermissionSet & amp; on System Disclaimed, Int 32 and Security Special Flags, Boolean Check Execution Promotion). Reflections.exabilities._update (assembly name filename, string codebase, proof assembly security, assembly placeholder, stack crawl mark and stack marker, boolean throwoverflow knotfound, boolean for introspection). AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark & ​​amp; stackMark, Boolean forIntrospection) System.Reflection.Assembly.InternalLoad (string assemblyString, evidence assemblySecurity, on StackCrawlMark & ​​amp; stackMark on System.Reflection.Assembly.Load, Boolean forIntrospection) (S System.Web.Configuration.CompilationSection.LoadAssemblyHelper on Tring assemblyString) (string AssemblyName, Boolean starDirective)  

specific DLL fails to load varies for this event from the event, but always refers to a main assembly .

We are running on ASP.NET 3.5 on Windows Server 2008. It seems that this does not happen in batches affecting some sites on the same app pool. We have a large number of sites running the same code.

Once a site fails to load the DLL, it throws a yellow screen off death until the next app pool recycle. We have not been able to reproduce this behavior and sites work fine for days or weeks before the failure (and recycle multiple app pools).

Has anyone else seen such behavior?

Update:

We tried to reproduce a script written failure to hit the set of a few hundred sites and times Couple of minutes and even a few others were unable to complete the loading of the server's CPU straight for a few days.

We Aspi.ankti.al.al.al with copies to try to play the (locking of DLLs, the file is changed to allow). Does and succeeds in reproducing similar behaviors but not the only exception.

Does anyone have any idea how to adjust the security policy? is to throw the System.Security policy Ethics: Permission can not be obtained for execution. While loading a specific DLL? In

load

"process IIS application pool settings under the model" user right profile.

to