Asp.Net Session expires immediately

Question

My Asp.net Session Expires immediately even though i did the settings in web.config file,

<system.web>
        <sessionState timeout="2880" mode="InProc" cookieless="UseCookies"></sessionState>
        <customErrors mode="RemoteOnly"/>
        <trace enabled="false" localOnly="false"/>
        <compilation debug="false" strict="false" explicit="true" targetFramework="4.0"/>
        <httpCookies httpOnlyCookies="true"/>
        <pages validateRequest="false" enableEventValidation="false" viewStateEncryptionMode ="Never" enableViewStateMac="false" />
    </system.web>

i did above settings in web.config even then it expires after approx 3 minutes... can anyone help me??

How did you set the settings in the web.config?Can you show us some code what you did? — coder, Nov 16 '11 at 10:35
i have pasted the code which i used above in tags.. do reply if you have the answer.. — Puneesh, Nov 16 '11 at 10:38
http://blogs.iis.net/webtopics/archive/2009/07/21/in-proc-session-state-management.aspx — huMpty duMpty, Nov 16 '11 at 10:54
Look at [this link](http://stackoverflow.com/a/11375003/779408). I had this problem and its solution solved it. — Bob, Jul 08 '12 at 05:54

score 0 · Answer 1 · answered Nov 16 '11 at 10:47

Remove the cookieless attribute if your application is AJAX-Enabled. Use default value of cookieless attribute.

From MSDN doc:

The cookieless attribute can be one of the following possible values. The default is the UseCookies value.

Note: When you configure an AJAX-enabled ASP.NET Web site, use only the default value of UseCookies for the cookieless attribute. Settings that use cookies encoded in the URL are not supported by the ASP.NET AJAX client script libraries.

yes i have used cookieless="UseCookies" in tag.. so what is the issue here? — Puneesh, Nov 16 '11 at 10:53

score 0 · Answer 2 · answered Nov 16 '11 at 10:47

0

I believe session does not expire immediately, but simply die. Since you are using InProc session state it could die whilst

Any change to the web.config file cause AppDomain unload and session as well
Application Pool restart. InProc session satte pretty risky thing, I would suggest at least allocating separate Applciation Pool for each web-site
Any code changes in code behind files cause AppDomain unload (and session as well) in order to load new assemblies in a new AppDomain

The best solution - use SqlServer Mode session state.

answered Nov 16 '11 at 10:47

sll

61,540
22
104
156

i cannot use sqlserverto store session state i don't have access to admin rights of online sql server, i need to do it by other means.. – Puneesh Nov 16 '11 at 10:54
@Puneesh - is it hosting company? You can ask to setup this feature for you. At elast ask whether your site has own app pool – sll Nov 16 '11 at 10:59
SQL Server isn't necessarily the "best" solution. It's the most robust solution. I would go for State Server mode at the minimum though, and that doesn't need a SQL Server to host it. – starskythehutch Nov 16 '11 at 11:21

Asp.Net Session expires immediately

2 Answers2