ISessionIDManager.InitializeRequest has not been called

D

Dave DiFilippo

Hello,

We appear to get getting an HttpException with the above message upon the
initial call to our ASP .NET 2.0 application, running locally on our
development machines, using InProc session handling. I've searched the
Internet, and have not found anything usefull on this error, although
apparently others have received this error as well. Is there any additional
information regarding this error? Again, it only happens once, upon the
first request against the application, and never again.

[HttpException (0x80004005): ISessionIDManager.InitializeRequest has not
been called for this request yet. In each request, please first call
ISessionIDManager.InitializeRequest before calling other methods.]
System.Web.SessionState.SessionIDManager.GetSessionID(HttpContext
context) +149
System.Web.SessionState.SessionStateModule.DelayedGetSessionId() +43
System.Web.SessionState.SessionStateModule.OnReleaseState(Object source,
EventArgs eventArgs) +328

System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +64


Thanks,

Dave
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,007
Latest member
obedient dusk

Latest Threads

Top