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 ...ERROR: Could not connect to database specified in connectionString for SqlDataProviderERROR: Could not connect to database specified in connectionString for SqlDataProvider
Previous
 
Next
New Post
10/4/2006 3:58 AM
 

Hi !

 

I always receive:

 

Error Installing DotNetNuke

Current Assembly Version: 04.03.05

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

 

I give up. Have to look for another freeware portal application. I have spent 3-4 days with this problem but it seems that noone can help me with this or have had the same problem. I have a new installation of XP Pro + VS2005 Pro + SQL Server 2005 Express.

I am using all default settings in the dnn packages.

I have tried the installation package and source package but always receive the same result.

 

Rgds/Gunnar Snellman

 
New Post
10/4/2006 4:02 AM
 
Have you configured Both SQL Connection strings in the Web.Config?  Also verify the ones you are configuring are not the ones that are commented out? There are two Portal connection strings and two Module connections string.  You need to have one of each configured.  I normally use SQL so I have to comment out the SQL Express and then configure the SQL 2k/2k5 connections.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
10/4/2006 4:59 AM
 

Hi Robert !

Yes I have.

 

----

  <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" />
    <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      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;"/>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableWebFarmSupport" value="false" />
    <add key="EnableCachePersistence" value="false"/>
    <add key="HostHeader" value="" /><!-- Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx" -->
    <add key="RemoveAngleBrackets" value="false" /><!--optionally strip angle brackets on public login and registration screens-->
    <add key="PersistentCookieTimeout" value="0" /><!--use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure-->
  </appSettings>

----

I have not manually created a database

Rgds/Gunnar

 
New Post
10/4/2006 7:07 AM
 

Rober you information isnt very informative.  If I new what you were talking about I most porbably would be having a problem.  Perhaps you could resond with a little more detail in how to actually get the it working..

thanks

 

Jim

 
New Post
10/4/2006 2:05 PM
 

Gunnar,

Yes, you do need to manually create the database.

When I configure my connections (since I am using SQL Server 2k/2k5) it looks like this*:

<code>

  <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" />
    Connection String for SQL Server 2000/2005   -->
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=SomeUserName;pwd=ThatUsersPassword;"
      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;"/>
    Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules-->
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=SomeUserName;pwd=ThatUsersPassword;"/>

</code>

Note how I change the comments to comment out SQL Express and then I configure the SQL Connection info.  If you are using SQL Express then you would not do this.


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...ERROR: Could not connect to database specified in connectionString for SqlDataProviderERROR: Could not connect to database specified in connectionString for SqlDataProvider


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