I have a ASP.Net web application in witch i want to put a timeOut (for user that dosen't do anything for too much time). My test use a 3 secondes timeOut. In the web.config :
<sessionState mode="StateServer" stateNetworkTimeout="3"></sessionState>
I get the following error as soon as i run my app:
Cannot request session state in session state server.
I can't find anything relevante for this case...
i tried to put InProc in Mode="" but it dosen't timeout anything.
Looking at this, you're trying to use a State Server and set the idle time between the web server and the state server. To properly configure the web server to use a state server, you must also configure the state server. Go to your state server and run:
systemroot\Microsoft.NET\Framework\versionNumber\aspnet_state.exe
This will install the asp.net state service. Then in the sessionState element in your web config you will need to set the stateConnectionString attibute as well.
<configuration>
<system.web>
<sessionState mode="StateServer"
stateConnectionString="tcpip=SampleStateServer:42424"
cookieless="false"
timeout="20"
stateNetworkTimeout="3"/>
</system.web>
</configuration>
You now have two "timeouts" here. The "timeout" attribute is how long the user can keep a connection to the webserver. The stateNetworkTimeout is how long the webserver to stateserver connection can be idle. The default is 10 seconds.
Hope this helps.
ref: https://msdn.microsoft.com/en-us/library/ms178586(v=vs.100).aspx
/ip
<sessionState mode="InProc" timeout="1" cookieless="false" ></sessionState>
I mistaken secondes for minutes, the Timeout value is about minutes. So i waited 1 minute for my test...
Thanks to #Devian and #Agolo.
Related
In my application i am facing session timeout issue . What happens is that suddenly users kicked out . I surf alot for solution and did many things . Like increasing session timeout , idle timeout ,implemented keepalive . But issue still exists
Is it possible that its due to internet connectivity . Because i saw multiple time in console that net::Error connection-reset , Network-changed etc etc.
If yes then what could be the possible solution for this .
Thanks,
Session timeout is controlled by the following key in web.config...
<system.web>
<sessionState mode="InProc" timeout="30" />
</system.web>
I have Webform ASP.NET 4.5 application.
In the login page Session variable is set as :(simplified related code)
Session["UserName"] = txtUserName.Text; (txtUserName.Text cannot be empty)
and then
Response.Redirect("Survey.aspx");
In survey page I have
if (Session == null || Session["UserName"] == null)
{
string errorText = "Session was timed out due to inactivity, to continue, please close All of your Browser windows and log in again";
In web.config file I have:
<system.web>
<sessionState mode="InProc" timeout="1200" />
<compilation debug="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
<customErrors mode="Off"> </customErrors>
</system.web>
Also on IIS itself I have
timeout :02:00:00
Still users report Session time out intermittently, after 15-20 minutes.
What this cause this?
=============================
Update: After setting it up to stateserver I get:
Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the same. If the server is on a remote machine, please ensure that it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection. If the server is on the local machine, and if the before mentioned registry value does not exist or is set to 0, then the state server connection string must use either 'localhost' or '127.0.0.1' as the server name.
As noted in comments, your application pool is probably configured to recycle periodically, which will cause InProc sessions to be lost.
You also asked in comments:
What do you recommend change the app pool or <sessionState mode="StateServer "> ?
In general, I would do neither! Instead, I would design the application so that it is resilient to Session data being lost.
In your example, you're storing a username in Session. Instead, I would use Forms Authentication, in which case the username will be available to you from HttpContext.Current.User.Identity.Name: no need to store it in Session.
In general, I would only store stuff in Session that can easily be regenerated, e.g. by reading from a database. To retrieve stuff from Session, check for null and regenerate if necessary, something like:
var mySessionValue = (MyType) Session["MyKey"];
if (mySessionValue == null)
{
mySessionValue = ... regenerate value, e.g. by reading from database
Session["MyKey"] = mySessionValue;
}
...
You may be losing the session state because the app pool is being recycled. There are all sorts of reasons why the app pool might get recycled including time-outs, exceptions etc.
If you change your session state from InProc to StateServer then your session information should survive the app pool being recycled.
There are some downsides to using StateServer - the primary one is that objects added to the session have to be serializable. This is not normally a big issue.
To make StateServer work you need to make sure the ASP.NET State Server is installed and the service is running.
I am facing session expiring issue in my ASP.NET Web Forms application. The session is timing out randomly. After 5 to 10 minutes(not exact time but happening randomly) there is no any explicit session. Timeout declaration elsewhere in the code. Given below are settings I have defined in Web.Config file. Any help is much appreciated
<httpRuntime maxRequestLength="350000" enableVersionHeader="false"
maxQueryStringLength="3584" executionTimeout="180000"/>
<sessionState mode="InProc" timeout="30"></sessionState>
I have an intranet page which needs to not time out (indefinitely) and I'm using JS to keep it alive that way.
But I am having one issue that happens when the user loses the connection (happens frequently due to to going in and out of wifi range) the session times out then.
How can I keep the session up/refresh it if that happens?
How about increase the session time out on web.config ?
<configuration>
<system.web>
<sessionState timeout="120"></sessionState>
</system.web>
</configuration>
http://msdn.microsoft.com/en-us/library/system.web.sessionstate.httpsessionstate.timeout.aspx
Other possible way is to make your database, connected with the user cookie, and use your "custom session" data that are totally connected with your users.
Try using in web config if you are using Form Authentication
<system.web>
<authentication mode="Forms">
<forms timeout="120"/>
</authentication>
<sessionState timeout="120" />
</system.web>
first Sets the session timeout on the server is for all session
Rather than a single Session
out wifi range is the entire network are broken
so not keep alive
You have to use cookie
use cookie keep alive
I am using ASP.NET 4.0 for a site I am making. It has a login that leads to some backend sites. That all works fine...
BUT...
There seems to be a logout thing in the Session cookie. Whenever I login and leave it for a few minutes it logs me out when I load the page.
Does anybody know what I can do to change this... or remove it??
you need to set your session timeout on your web.config:
<configuration>
<system.web>
<sessionState timeout="10"></sessionState>
</system.web>
</configuration>
Default value for session timeout is 20 minutes. You can change it in your webconfig as per your need.