The default connection string for SQL Express 2005 looks like this:
|<add name="Sitefinity" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Sitefinity.mdf" providerName="System.Data.SqlClient"/>
I have come to loathe User Instance because it means that only one process at a time can access the database (namely ASP.NET).
In the Sitefinity 3.2 days I had a SQL connection string that worked:
|add name="Sitefinity" connectionString="server=.\SQLExpress;uid=the_database_owner;pwd=the_password;database=TheSitefinityDatabase;" providerName="System.Data.SqlClient" />
Now, in 3.6, when I try same connection string, I get:
Server Error in '/Take6' Application.
This type of page is not served.
type of page you have requested is not served because it has been
explicitly forbidden. The extension '.aspx' may be incorrect. Please
review the URL below and make sure that it is spelled correctly.
Requested URL: /Take6/Sitefinity/Admin/Modules.aspx
Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053
The connection string works in Visual Studio's Server Explorer. I can even create new tables.
Any pointers for getting SQL authentication working? I'm even open to Windows Authentication. I just want to get away from User Instance.