My doubt is on a classic asp application. The session time we have set up on the IIS is not being considered and it kicks out the customers very frequently from the application which creates a huge problem. We dont have have the session time out set up anywhere in the code and I believe IIS set up should work through the webconfig file. Not sure where else this could have been set up.
We had this working fine till few days back before we did a huge DB change. Previously we had 10 database and we planned to merge it all to one. So we created a new instance with merged database and moved to this instance. We have not changed anything on the code except for the connection strings but we are not getting a solution on this time out issue.
We have changed the session time out to 40 minutes in the application pool in IIS and restarted the IIS for the changes to get affected. But it does not work. Please provide us your valuable solution. Most part of our application is in classic asp where few are asp.net applications which we have created as separate application and integrated with the asp application.
ASPASP.NET.NET Programming
Last Comment
gracesoft
8/22/2022 - Mon
Om Prakash
Please try the following for setting session timeout in IIS :
I forgot to mention, that your session time out could be reset because the app pool crashes or resets. If the work load is too heavy, it resets and you loose your session.
Thank you respected experts for your inputs. We have tried all the solutions mentioned except for the Scott fell's comment on script time out and app pool crashing possibility. Can you please let me know what is solution to address application pool getting crashed? we created few more frameworks to share the applications equally? Is this is the right solution?
https://technet.microsoft.com/en-us/library/cc725820(v=ws.10).aspx
For classic asp, put global asa file into root folder and set session time out there