Archive for the ‘Session’ Category
Session state can only be used when enableSessionState is set to true
Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.
This error usually occurs when you have declared an object variable public to the page and it access a Session variable, example:
Partial Class _Default
Inherits System.Web.UI.Page
Private m As New DBAccess(Session(”dbname”))
Protected Sub form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles form1.Load
End Sub
End Class
How to check if the ASP.Net Session has expired
-
protected void OnInit(EventArgs e)
-
{
-
base.OnInit(e);
-
//It appears from testing that the Request and Response both share the
-
// same cookie collection. If I set a cookie myself in the Reponse, it is
-
// also immediately visible to the Request collection. This just means that
-
// since the ASP.Net_SessionID is set in the Session HTTPModule (which
-
// has already run), thatwe can't use our own code to see if the cookie was
-
// actually sent by the agent with the request using the collection. Check if
-
// the given page supports session or not (this tested as reliable indicator
-
// if EnableSessionState is true), should not care about a page that does
-
// not need session
-
if (Context.Session !=null)
-
{
-
//Tested and the IsNewSession is more advanced then simply checking if
-
// a cookie is present, it does take into account a session timeout, because
-
// I tested a timeout and it did show as a new session
-
if (Session.IsNewSession)
-
{
-
// If it says it is a new session, but an existing cookie exists, then it must
-
// have timed out (can't use the cookie collection because even on first
-
// request it already contains the cookie (request and response
-
// seem to share the collection)
-
string</span> szCookieHeader <span>=</span> Request.Headers["Cookie"];
-
if((null!= szCookieHeader) (szCookieHeader.IndexOf("ASP.NET_SessionId")<= 0))
-
{
-
Response.Redirect("sessionTimeout.htm");
-
}
-
}
-
}
-
}
Source