This is likely due to the fact that the session timeout has reached the limit that ends with the session.
In this case, you have three possible solutions:
First
You can try editing the web.config located in the root application to extend the session timeout. Try something like this:
<sessionState mode="StateServer" timeout="500"> </sessionState>
According to MSDN, you can set the timeout to 525,601 minutes (1 year).
Second
If it does not work and you have access, you can try editing the timeout in IIS:
Open IIS, click Application Pools, select the application pool for your application.
Right click on it, select "Properties".
On the "Performance" tab, set the wait timeout as the desired minutes for "shutting down work processes after downtime for ..... minutes".
IMPORTANT: in addition to this, you must set the timeout in web.config as described above.
Third
You can create an ajax function that will execute in the background without waiting for the session to end:
function keepSessionAlive(mod) { mod.open("GET", "blank.html", true); mod.onreadystatechange = function() { if (mod.readyState == 4) { document.getElementById("#blankDiv").innerHTML = mod.responseText; } }; mod.send(null) } setInterval('keepSessionAlive()', 100000);
What is it. Hope this helps.
Christian
source share