Hi Gladi,

if you are running DNN live, you'll need to ask your hosting provider the correct connection string to connect to their SQL server. If you are running DNN locally for testing purposes, your connection string should look like the following. This is the connection string I use locally on my developing environment:

<connectionStrings>
  <!-- Connection String for SQL Server 2005 Express -->
  <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient"/>
...
 </connectionStrings>
 <appSettings>
  <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
  <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
...
 </appSettings>

Needless to say, you need SQL Server 2005 Express installed and running before accessing your localhost. Let me know if you need further help.

Best regards,
Dario Rossa

I am getting this error after installing on DNN 5.0.1.  Everything worked fine on 4.9.2.

Using Plesk, I added a new connection string as follows:

Name
---------
SiteSqlServe 

Connection Parameters
---------------------------------
Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient"

Now, when I browse to my DNN site, I get an application error; but I can't view the error details because the current custom error settings prevent the details of the application error from being viewed remotely.

Can anyone help me figure out what the correct connection string (or strings) should be for my installation?

Thanks,
Brian Bird