We have been having some problems with our client application timing out on us.
We have a .NET C# Smart Client that connects to a remote server.
The remote server serves up Remoting Objects over HTTPS to the Smart Client using an IIS .NET 2.0 Web Application.
Our remoted objects have a lifetime leaseTime of 0 or “forever”.
But for some reason our user’s kept getting timed out after 20 minutes.
Finally we figure out that our ASP.NET web application has a default timeout of 20.
Here is the parameter for the web.config that controls the ASP.NET timeout:
The number for the timeout must be an integer, and it is in minutes. What we found in our project was that unless the web.config had a parameter setting the time to keep an ASP.NET session alive it would terminate it after 20 minutes and the app would throw exceptions.
The parameter goes anywhere within the <system.web> portion of the configuration section of web.config. Hopefully that will help anyone else having this type of problem.