Loading this assembly would produce a different grant set from other instances
Last Week after a successful MS Patch and Service reboot of the SharePoint WFE and App server we were left with a service failure.
Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error
and where it originated in the code.
Exception Details:System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)] System.Linq.Enumerable.Count(IEnumerable`1 source) +0 Microsoft.SharePoint.IdentityModel.SPChunkedCookieHandler.ReadCore(String name, HttpContext context) +366 Microsoft.IdentityModel.Web.SessionAuthenticationModule.TryReadSessionTokenFromCookie(SessionSecurityToken& sessionToken) +93 Microsoft.IdentityModel.Web.SessionAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs eventArgs) +61 Microsoft.SharePoint.IdentityModel.SPSessionAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs eventArgs) +231 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +176 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +169 |
The Short Term fix was to update the web.config for all Web App on all Servers within the SP Farm
From:
<trust level="Full" originUrl="" legacyCasModel="true" />
To:
<trust level="Full" originUrl="" legacyCasModel="false" />
While this worked and returned the web apps to a normal service, it would have left our SP web apps (Intranet, Extranet, MySite + Central Admin) in anunsupported state. As informed by Microsoft.
Microsoft suggests removing the Web.config update and returning the web.config values back to a supported state.And the Updating the Registry, with the following values:
Create a new registryDWORD value called LoaderOptimization and give it the value1 within the key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework”
Perform IISRESET and check Web Apps behavior.
Steve Lamin