Storing session state in SQL Server eliminates session log outs due to memory issues and web server restarts.   This is because the session token is stored in a SQL database and not in memory.   As long as the user maintains the same browser, state will be maintained.


Note that this does not resolve the issue of multiple browser windows.   In this situation, it is not recommended that users maintain multiple session of LobbyCentral on the same computer.


  1. Log into the LobbyCentral server.
  2. Go to c:\windows\Microsoft.NET\Frameworks\v4.0.30319
  3. Create the ASPState database by executing this command: 

       

    aspnet_regsql -ssadd -sstype p -S <dbServerName> -U <username> -P <password> 
     

       

  4. Connect to the database server using SQL Management Studio.
  5. Verify that the ASPState database was created.
  6. Expand Security and right-click on Logins and select New Login.
  7. Set the login name to sessionStateUser and select SQL Server Authentication.
  8. Enter a strong password.
  9. Uncheck" Enforce Password Expiration" and "User must change password".
  10. Click User Mappings.
  11. Check the Map box for the ASPState database.
  12. Check "db_owner" under roles.
  13. Click OK to save the account.

Update the LobbyCentral Configuration File


Make a backup of c:\program files\fuhr software\lobbycentral\web\Web.config and then open web.config in Notepad.


Locate the <sessionState> tag and change it to the following:


<sessionState mode="SQLServer" sqlConnectionString="Data Source=<dbServerName>;User ID=sessionStateUser;Password=<password>" timeout="720"/>

 

 Where:

  •                dbServerName- IP or name of the database server
  •                password- user's password


Save and close the file.