Like most web based services, sessions are used to track various server side parameters such as user logins, shopping carts and other transient variables.

ASP.NET has three different modes:

  • In Process Mode. This is the default. Sessions are stored in memory alongside your application. These sessions remain active until your web application is restarted.
  • State Server Mode. This requires an additional service to be running, which isn’t enabled by default. A centralised service means your sessions persist beyond any application restarts and also allows for clustered web servers to access a centralised pool so that the sessions are visible from all pooled web servers.
  • SQL Server Mode. This uses your SQL Server to store the session states in, which again persists beyond application restarts as well as allowing pooled web servers to centrally access.

The configuration of the sessions is handled by your web.config file, located in the httpdocs folder which you can edit with the Plesk File Manager.


For shared hosting with Conetix, only In Process and SQL Server Mode are allowed.

Further reading: https://docs.microsoft.com/en-us/previous-versions/aspnet/ms178586(v=vs.100)

Setting In Process

If you’re moving your ASP.NET hosting to a shared hosting plan with Conetix, you may need to adjust your session settings. Unless there’s explicit reasons not to, we recommend using the default In Process Mode. To set this:

  1. Login to Plesk or via the Conetix Control Panel.
  2. Go to the File Manager:
    asp.net session state modes
  3. Then select the web.config file:
    asp.net session state modes
    This will open the code editor.
  4. Find the sessionState variable and set:
    <sessionState mode="InProc"></sessionState>

    Note: If you don’t see the variable set, then by default it will be set to In Process Mode.

Was this article helpful?

Related Articles