Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The connection name The connection name 'SiteSqlServer' was not found in the applications configuration
Previous
 
Next
New Post
4/19/2006 5:48 PM
 
I believe your problem is with the .Net2.0 Membership and Roles providor.  .Net20 allows you to use SQLServer2k+ to manage centrally, your registration/login/roles information.  This requires you to set up a seperate SQLDB for the providor, hence the fact that your error is referencing connectionStringName="SiteSqlServer". You need to find out where "SiteSqlServer" is pointing to. My guess is that you never set up the roles DB.  Take a look at the .Net Quickstarts, they tell you how to set it up.

-e
 
New Post
4/25/2006 4:14 PM
 

I had this same problem.  I can tell you what I did, but I'm not sure if it is correct.  When I was setting up the web.config file the welcome.html file told me to change the connection string in connectionStrings to this:

<add name="DotNetNuke" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />

and to change the connection string in appSettings to this:

<add key="DotNetNuke" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />

In both places I changed either the name or the key from SiteSqlServer to DotNetNuke, so when I received this error I changed SiteSqlServer to DotNetNuke in all of the other places in web.config.  Once I did that it worked.  I'm not sure if this is correct or not, but it worked.

Please let me know if I did something wrong.

Thanks

 
New Post
4/30/2006 6:16 AM
 

The problem you are experiencing is probably this:

When you remove the connection string for the Express 2005 provider then you are left with this:

    <!-- Connection String for SQL Server 2000/2005
    <add name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
   -->

This code is commented out with the <!--   --> brackets. This would result in an error like the one you are describing.

If you change it to this:

    <!-- Connection String for SQL Server 2000/2005   -->
    <add name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />

and fill in your details about the server, db, user and password it should work fine.

 
New Post
5/6/2006 5:15 PM
 
Me too same problem!
 
New Post
5/7/2006 8:26 AM
 

Guys - DNN 4.x Application Strings settings assumes you're using SQL 2005 Express. If you're using SQL 2000 or 2005 you'll need to edit the application string and connections strings to include this line.

To use a SQL Server 2000 or 2005 database replace the whole connection string by something similar to

Server=(local);Database=DatabaseName;uid=LoginName;pwd=LoginPassword;

Here's the copy and paste from the Welcome.html page in the documents folder in DNN install.

The examples shown above are for the default SQL Server 2005 Express database file "Database.mdf".  If you used the defaults when creating you SQL Server Express 2005 database, you will not need to make any modifications to the connection strings. If you used a different filename for the database file, you need to change the AttachDBFilename=|DataDirectory|Database.mdf; section.

To use a SQL Server 2000 or 2005 database replace the whole connection string by something similar to

Server=(local);Database=DatabaseName;uid=LoginName;pwd=LoginPassword;

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The connection name The connection name 'SiteSqlServer' was not found in the applications configuration


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out