ISessionIDManager.InitializeRequest has not been called

[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

 

[Bob Barrows]

Hello,

We appear to get getting an HttpException with the above message upon
the There was no way for you to know it (except maybe by browsing

through
some of the previous questions before posting yours - always a
recommended practice), but this is a classic (COM-based) asp newsgroup.
ASP.Net is a different technology from classic ASP. While you may be
lucky enough to find a dotnet-savvy person here who can answer your
question, you can eliminate the luck factor by posting your question to
a newsgroup where the dotnet-savvy people hang out. I suggest

microsoft.public.dotnet.framework.aspnet.

There are also forums at www.asp.net where you can find a lot of people
to help you.