Note that there are some explanatory texts on larger screens.

plurals
  1. POhow to switch to SQL server state for sessions.... I get an error
    text
    copied!<p>Because of some In Proc problems I try to switch to SQL State session.</p> <p>I checked my CMS database and I see the tables like aspnet_XXX already exists. To be sure I also created the DEFAULT database "aspnetdb" and compared the tables aspnet_xxx and checked whether they already exists in my CMS_DB_DEV or not... and all of them are already exists.</p> <p>Then I went to web.config and I configured via IIS the sessionstate connectionstring and it looks like below: </p> <pre><code> &lt;system.web&gt; &lt;sessionState allowCustomSqlDatabase="true" cookieless="UseCookies" mode="SQLServer" sqlConnectionString="Server=localhost;Database=cms_db_dev;User ID=sa;Password=xxxx" timeout="20" /&gt; </code></pre> <p>now when I run my application I get the error:</p> <blockquote> <p>Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL server. Please install ASP.NET Session State SQL Server version 2.0 or above.</p> </blockquote> <p>I use W7 pro, IIS 7.5 is installed</p> <p>I checked these 2 links which mention the problem but no hope:</p> <p><a href="http://support.microsoft.com/kb/317604" rel="nofollow">http://support.microsoft.com/kb/317604</a></p> <p><a href="http://www.brianstevenson.com/blog/aspstate-concurrently-running-for-net-1011-and-net-20#comment-984" rel="nofollow">http://www.brianstevenson.com/blog/aspstate-concurrently-running-for-net-1011-and-net-20#comment-984</a></p> <p>AFter I get this working on my localhost, I'll do the same in Production machine. It seems the tables already exists, so I just need to configure web.config....</p> <p>I MAY NOT DELETE THE EXISTING tables (like aspnet_xxx), because it's used by Dotnetnuke CMS system... But I can test on my localhost... </p> <p>so what am I missing ? </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload