Home/ Questions/Q 3460186
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T10:11:57+00:00

Our intranet has a custom membership system (not asp membership) which puts values in

  • 0

Our intranet has a custom membership system (not asp membership) which puts values in the session information to identify users. As the intranet is constantly evolving, I often have to publish changes to the live server several times every day. Each time I do, the users who are logged in’s sessions end and they have to log in again. This causes various issues which I won’t bore anybody with here.

My question – is there anyway to prevent this, or do I just have to live with it? Have spent the last 3 hours Goggling and can find no solution.

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The solution is to use a different Session Mode; You are using “InProc”, which means the session is stored in the same application space as your application. You can use “StateServer” or “SQLServer”, however these will likely require application changes (and additional setup; StateServer will require a separate service to be running on the IIS Server and SQLServer will require a database to store information in). Everything that you store in the Session will need to be serializable.

    Here is the information on MSDN regarding Session Mode.

    • 0