Recently, it was observed that when using Servicedesk, clicking on the lightning bolt to edit a user caused the error below to appear:
System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
The full text of the error
Error,Friday, October 25, 2013 7:20:24 PM,[global] Application 'LogicBase.Ensemble' error
[global] Client Host Information:
[global] IP: xxx.xxx.xxx.xxx
[global] HostName: xxx.xxx.xxx.xxx
[global] Browser: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.2; MS-RTC LM 8; .NET4.0E)
[global] -- error.ToString() --
[global] System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
[global] at LogicBase.Ensemble.Controls.TabControl.OnPreRender(EventArgs e)
[global] at System.Web.UI.Control.PreRenderRecursiveInternal()
[global] at System.Web.UI.Control.PreRenderRecursiveInternal()
[global] at System.Web.UI.Control.PreRenderRecursiveInternal()
[global] at System.Web.UI.Control.PreRenderRecursiveInternal()
[global] at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[global] --- End of inner exception stack trace ---
[global] at System.Web.UI.Page.HandleError(Exception e)
[global] at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[global] at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[global] at System.Web.UI.Page.ProcessRequest()
[global] at System.Web.UI.Page.ProcessRequest(HttpContext context)
[global] at ASP.docman_documentaddsimple2_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\processmanager\8e242adb\738a87da\App_Web_yig40o_w.12.cs:line 0
[global] at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
[global] at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
It was determined that this error was affecting the ability of some of the Infragistics libraries to open correctly. Specfically:
- Infragistics35.WebUI.Misc.v8.3.dll
- Infragistics35.WebUI.UltraWebNavigator.v8.3.dll
- Infragistics35.WebUI.WebDateChooser.v8.3.dll
The server somehow was expecting that these libraries were an earlier version than what was actually on the server. A particularly vexing problem, it was determined that a recent installation of the MS Service Center Operation Manager (SCOM) 2012 agent was causing the problem. Removing the agent resolved the issue.
Servicedesk and Workflow are not currently compatible with the MS SCOM 2012 Agent.