Web Client Session Timeout

the web client timeouts after 20 min of non activity.  I adjusted the  300WEBAPI  - WEB.config  under key name “SessionPoolTimeOut” to 120.  Restarted the application pool and all sites and i still timeout after 20 min.  Has anyone successfully found how to control this timeout setting so they can be logged in with no activity for 2 or 3 hours.  

Parents Reply Children
  • 0 in reply to Tim - Accsys Consulting

    changing the settings noted in this thread does control the length of time out however what I am finding now is that if they lock their workstation and unlock it - no matter how long the time out setting is at it requires them to login again.  Does anyone have a solution for that?

  • 0 in reply to ValerieH

    Assuming this isn't the AppPool recycling (yet another setting different to the ones above), the problem is likely the network card or machine sleeping while its locked.  All I can think of is ensure your users are on Maximum performance power profiles with the computer, display, wifi, network, hard drive  and literally anything else set not to sleep.  Especially on modern PC's with aggresive power saving - even at the motherboard level, the temptation of an important component going to sleep while locked breaking your Sage session will be huge - I think this is going to be a tough battle but if you solve it let us know!  Maybe your users can change to a screensaver with lock on wake instead of just locking their PC with the screen going blank?