microsoft.public.dotnet.framework.aspnet.caching

Greg

5/21/2009 5:48:00 PM

I have the exact same problem though it's affecting my IIS6 website. Haven't
found a solution yet.

"Dave DiFilippo" wrote:

> Hello,
>
> I've posted this in several discussion groups, but this may be the most
> appropriate one, since I beleive this issue has something to do with InProc
> session state within an ASP .NET 2.0 application.
>
> We appear to get getting an HttpException (below) with the message in the
> subject title 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
>
>
>