HttpError "Session state has created a session id..."

[PL]

I've seen a few of these in the eventlog, what in the world would cause something like this,
why can't it save the session id cookie ??

Exception type: HttpException
Exception message: Session state has created a session id, but cannot save it because the response was already flushed by the
application.

System.Web.Sess ionState.Sessio nIDManager.Save SessionID(HttpC ontext context, String id, Boolean& redirected, Boolean& cookieAdded)
at System.Web.Sess ionState.Sessio nStateModule.Cr eateSessionId()
at System.Web.Sess ionState.Sessio nStateModule.De layedGetSession Id()
at System.Web.Sess ionState.Sessio nStateModule.On ReleaseState(Ob ject source, EventArgs eventArgs)
at System.Web.Sess ionState.Sessio nStateModule.On EndRequest(Obje ct source, EventArgs eventArgs)
at System.Web.Http Application.Syn cEventExecution Step.System.Web .HttpApplicatio n.IExecutionSte p.Execute()
at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean& completedSynchr onously)

PL.

[Patrice]

Never had this one. My guess would be defining a session variable after
having flushed the response buffer. Try perhaps a sequence such
Response.Write, Response.Flush, Session("Test") ="A".

Let' us know...

--
Patrice

"PL" <pb****@yahoo.s e> a écrit dans le message de
news:ut******** *****@TK2MSFTNG P15.phx.gbl...

I've seen a few of these in the eventlog, what in the world would cause something like this, why can't it save the session id cookie ??

Exception type: HttpException
Exception message: Session state has created a session id, but cannot save it because the response was already flushed by the application.

System.Web.Sess ionState.Sessio nIDManager.Save SessionID(HttpC ontext context, String id, Boolean& redirected, Boolean& cookieAdded) at System.Web.Sess ionState.Sessio nStateModule.Cr eateSessionId()
at System.Web.Sess ionState.Sessio nStateModule.De layedGetSession Id()
at System.Web.Sess ionState.Sessio nStateModule.On ReleaseState(Ob ject source, EventArgs eventArgs) at System.Web.Sess ionState.Sessio nStateModule.On EndRequest(Obje ct source, EventArgs eventArgs) at System.Web.Http Application.Syn cEventExecution Step.System.Web .HttpApplicatio n
..IExecutionSte p.Execute() at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean& completedSynchr onously)
PL.

[PL]

But this happens on a page where I don't use any session variables at all,
it seems it happen on the very first request and only intermittently.

Seems like a bug to me, if someone from MS could give any insight that would be nice.

PL.

"Patrice" <no****@nowhere .com> skrev i meddelandet news:eW******** *****@TK2MSFTNG P15.phx.gbl...

Never had this one. My guess would be defining a session variable after
having flushed the response buffer. Try perhaps a sequence such
Response.Write, Response.Flush, Session("Test") ="A".

Let' us know...

--
Patrice

"PL" <pb****@yahoo.s e> a écrit dans le message de
news:ut******** *****@TK2MSFTNG P15.phx.gbl...

I've seen a few of these in the eventlog, what in the world would cause

something like this,

why can't it save the session id cookie ??

Exception type: HttpException
Exception message: Session state has created a session id, but cannot save

it because the response was already flushed by the

application.

System.Web.Sess ionState.Sessio nIDManager.Save SessionID(HttpC ontext

context, String id, Boolean& redirected, Boolean& cookieAdded)

at System.Web.Sess ionState.Sessio nStateModule.Cr eateSessionId()
at System.Web.Sess ionState.Sessio nStateModule.De layedGetSession Id()
at System.Web.Sess ionState.Sessio nStateModule.On ReleaseState(Ob ject

source, EventArgs eventArgs)

at System.Web.Sess ionState.Sessio nStateModule.On EndRequest(Obje ct source,

EventArgs eventArgs)

at

System.Web.Http Application.Syn cEventExecution Step.System.Web .HttpApplicatio n
.IExecutionStep .Execute()

at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&

completedSynchr onously)

PL.