M
michdoh
HI All
We are running mcms 2002 on framework 1.1 SQL 2000 on windows 2000
servers.
It's a load balanced pair of servers using windows NLB writing the
session to an SQL shared DB.
We are getting the following exeption (A lot)
System.Web.UI.Page.HandleError(Exception e) at
System.Web.UI.Page.ProcessRequestMain() at
System.Web.UI.Page.ProcessRequest() at
System.Web.UI.Page.ProcessRequest(HttpContext context) at
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Exception of type System.Web.HttpUnhandledException was thrown.
It's on a basic CMS channel summary page containing the usual
navigation controls (As with all of the other templates, which are OK)
but with a summary control. It's based on the woodgrove sample control.
Please note that I have not been able to replicate this error on our
test or live environment
I Posted this on the CMS work group but stefan suggested this was an
ASP problem so any thoughts are greatly appreciated
Mikey
We are running mcms 2002 on framework 1.1 SQL 2000 on windows 2000
servers.
It's a load balanced pair of servers using windows NLB writing the
session to an SQL shared DB.
We are getting the following exeption (A lot)
System.Web.UI.Page.HandleError(Exception e) at
System.Web.UI.Page.ProcessRequestMain() at
System.Web.UI.Page.ProcessRequest() at
System.Web.UI.Page.ProcessRequest(HttpContext context) at
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Exception of type System.Web.HttpUnhandledException was thrown.
It's on a basic CMS channel summary page containing the usual
navigation controls (As with all of the other templates, which are OK)
but with a summary control. It's based on the woodgrove sample control.
Please note that I have not been able to replicate this error on our
test or live environment
I Posted this on the CMS work group but stefan suggested this was an
ASP problem so any thoughts are greatly appreciated
Mikey