Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. If a virus scanner scans the Adams Web directories, then that can cause the IIS process to restart thus loosing sessions. https://docs.microsoft.com/en-us/troubleshoot/aspnet/session-data-lost-inproc-mode

  2. In IIS, the Adams Web pool is set to recycle automatically on a schedule. To see the schedule, IIS > Application Pools > AdamsWebPool > Recycling…

  3. The session expired due to inactivity but the browser did not redirect to the login page so the user is unaware the session expired. For example, perhaps the computer went to sleep so when the session expired, the redirect could not happen.

  4. The user used Chrome’s forward or back buttons to navigate between pages and did not perform any action that involved the server such as click a button within 30 seconds.

  5. For Adams Web Azure implementations, if both Windows and Forms authentication are enabled then the authentication cookie may not get extended when it should. To resolve, disable Windows authentication and recycle the Adams Web pool.

  6. Editing some settings in the web.config can cause the pool to be recycledrecycle which will end sessions.

Page Properties
hiddentrue

Related issues