Hi, Scott.
A few more things to check :
1. Is this a typo ? : cookiesless="fa lse"
That should be : cookieless="fal se"
2. Could you check to see if you can connect to another database in your
SQL Server using either "localhost" , "(local)", or "Instance_n ame" ?
3. Check your connection string. You are not using case-sensitive strings.
<configuratio n>
<system.web>
<sessionState mode="SQLServer "
sqlConnectionSt ring="Integrate d Security=SSPI;d ata source=SampleSq lServer;" />
</system.web>
</configuration>
If you specify a trusted connection to your SQL Server in the configuration file using the
sessionState element's sqlConnectionSt ring attribute, the SessionStateMod ule will connect
to SQL Server using SQL Server integrated security. The connection will be made using
the ASP.NET process identity or the user credentials supplied for the identity configuration
element, if they exist.
4. Did you run the Aspnet_regsql.e xe Tool ?
Follow the instructions at :
http://windowssdk.msdn.microsoft.com...8b9b591bb4.asp
if you haven't installed the SQL Server database with the Aspnet_regsql.e xe tool.
Let us know what you did, and how it came out, OK ?
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
=============== =============== =====
<lu****@gmail.c om> wrote in message news:11******** ************@t3 1g2000cwb.googl egroups.com...
Juan,
Thank you for your reply!
I originally had the session state set at inProc and it was still
giving me the same error.
I tried your suggestion and changed the localhost to the SQL
Instance name to no avail. I still get the same message.
Thank you,
Scott Vercuski