M
Mark Meyers
I have no clue what is happening and hope someone can explain this.
I have my Web site set up to use SQL Server session state. This works fine.
When a session starts, a row is created in ASPStateTempSessions.
When the user logs off the application, I am trying to call the stored
procedure TempRemoveStateItem to clean up after myself (not sure if this is
the right way to do it or not).
What I noticed is that the SQL table's SessionID column contains 32
characters whereas the .NET Session.SessionID value only contains 24
characters (which match the first 24 characters of the 32 characters stored
in the SQL table). Because the values do not match, the stored procedure
always fails.
Why would the SessionID value differ between .NET and SQL?
I have my Web site set up to use SQL Server session state. This works fine.
When a session starts, a row is created in ASPStateTempSessions.
When the user logs off the application, I am trying to call the stored
procedure TempRemoveStateItem to clean up after myself (not sure if this is
the right way to do it or not).
What I noticed is that the SQL table's SessionID column contains 32
characters whereas the .NET Session.SessionID value only contains 24
characters (which match the first 24 characters of the 32 characters stored
in the SQL table). Because the values do not match, the stored procedure
always fails.
Why would the SessionID value differ between .NET and SQL?