I'm getting a reference error in License Base. I don't know how I can fix that problem.
Here's what I did:
- d/l the es.zip (the second one) that Ben posted, with all the ES files in it
- Stopped the site with ES
- Deleted all the files in my ES folder, except my License file in the bin folder, my datasources and web config files.
- Copied all the files from ES.zip into my folder, except the datasource and web config files
- Started the site
- Restarted IIS
I have no other ES or SF files on this machine.
Here is the stack trace, found at the bottom of the error page returned when attempting to hit the Status.aspx page:
[FileLoadException]: Could not load file or assembly 'MicroFour License Base, Version=1.6.0.0, Culture=neutral, PublicKeyToken=7bb29517c3189d04' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at MicroFour.StrataFrame.Enterprise.Server.Status.Status_PreInit(Object sender, EventArgs e)
at System.Web.UI.Page.OnPreInit(EventArgs e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
[HttpUnhandledException]: Exception of type 'System.Web.HttpUnhandledException' was thrown.
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.status_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I'm at a loss of what I could have done wrong to get this error. ES was working on this machine prior to upgrading to the version that fixed the null argument problem.