More importantly along this line would be precise information on all settings in IIS and DNN that control the "session timeout" and IIs timeout processes.
We are experiencing strange behavior and can't tie it down to IIS Application Pools (worker process recycle def: 20min), IIS ASP.NET State Configuration in Machine,config or web.config (def : 20 min) or IIS Home Directory, Application, Configuration, Options ... Session Timeout (can this be unchecked in any case for DNN?) (Def : 20 min).
Scenario : We have a module that presents a data entry form to the user ... the information on the form requires the user to type in very detailed and acurate information which can take some time ( up to an hours with typical interuptions and distractions ... right?).
Of course, when the user submits the form, the data never goes anywhere, since the user is logged out, and DNN logs them back in sending them back to the Edit Form page, WITH NO INFORMATION ... IE the orriginal blank form. Needless to say they are somewhat annoyed!
So ... somewhere along the way the user session has timed out ... we have been doing extensive testing, and cant figure out which setting, or DNN override is causing the problem.
Is there something in DNN that sets a "timeout" during the "Edit" mode of a module? I'm guessing not.
I believe the ASP.NET State Configuration is what I should be concerned with, and we can set the settings to 1 minute, but our sessions stay alive longer than this setting ... typically approx 5 minutes .. then they do indeed timeout. However setting these settings to 120 minutes seems to still yield a 20 minute window. What gives?
What is actually controlling the session timeout settings? How do I keep users connected to this DNN/IIS site for 2 hours?
Thanks!
Chuck