Help! ASP.NET C# Project Unable to access Session Variable in Thread or Timed Event.

Question

0.00/5 (No votes)

See more:

I have a webpage in ASP.NET C# that creates a session variable using

Session["State"]="State1";

I try to access this session variable in another page called WaitPage and it works.

When i try to access this Session variable in a thread in WaitPage or try to access the session variable in a timed event, I get the error.

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.

I have already enabled "EnableSessionState=true" in both webpages.
I have the required add name="Session" type="System.Web.SessionState.SessionStateModule" in httpModules section in web.config.

Why am I getting this error? Can you help me fix this?

Thanks
Jobin Thomas

Posted 26-Feb-11 4:06am

jobin007007

Updated 26-Feb-11 8:01am

thatraja

v5

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_Ashish · Answer 1 · 2011-02-26T07:10:00

You cannot directly access the Session variable in a Thread.

Session is associated with HttpContext.Current object. When a Http request is under process a HttpContext.Current is instantiated and thus the HttpContext.Current.Session is instantiated. These objects gets out of scope when a http request is proceesed and page is rendered.

In Threads that are started on a page event runs async and there the HttpContext.Current.Session is null. so you cant access the Session object.

One way :
A ashx or aspx page would be created to do the session manipulation and let the Thread calls that aspx/ashx page through a WebRequest.

Albin Abel · Answer 2 · 2011-02-26T05:29:00

Solution 2

You may need to enable session store.

Refer this

http://support.microsoft.com/kb/317604[^]

Posted 26-Feb-11 5:29am

Albin Abel

Comments

[no name] 26-Feb-11 11:40am

I think the link you posted refers to SQL usage. I do not use SQL in my code at all.

Sandeep Mewara · Answer 3 · 2011-02-26T04:55:00

Solution 1

Error in itself is quite self-explanatory.

Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive...
This simply means,
You need to include a <pages... > attribute in web.config:

XML

<pages enableSessionState = "true" />

OR
Just Enable SessionState in the <%@ Page ...%> directive in your ASPX page, like:

XML

<%@ Page enableSessionState = "true" %>

Posted 26-Feb-11 4:55am

Sandeep Mewara

Comments

[no name] 26-Feb-11 11:38am

I have already enabled "EnableSessionState=true" in both webpages.
I have the required add name="Session" type="System.Web.SessionState.SessionStateModule" in httpModules section in web.config.

Updated the question.

Sandeep Mewara 26-Feb-11 11:40am

Do a IISreset and try. :)

For now, leaving those options, without looking at the environment configured, it would be difficult to tell the reason now. :doh: