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 ...SQLExpress2005 Install on 4.03.05SQLExpress2005 Install on 4.03.05
Previous
 
Next
New Post
10/21/2006 12:55 PM
 

I am only using one connection string.  I have tried different varations to see what was working.  As far as the key.  I have not changed any of the keys.  The instructions do not say to do that.

Any other clues?


Neadom Tucker New to the wide world of .NET... I could care less about PHP
 
New Post
10/21/2006 1:13 PM
 

Ok guys the issue is a commented out section on the default connections string.  Here is what it orginally looks like.

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=;"/>
    -->

 

Note that by default the SQL EXPRESS connection string is Good to go but the SQL2000/2005 is Commented out.

See the bolded sections.  If you want to use the SQL 2000/2005 then this is what your connections string needs to look like.

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=;"/>

 

Once I did this then it installed in a snap!

I think they need to update the manuals!!!!

Thanks Neadom!!!
   


Neadom Tucker New to the wide world of .NET... I could care less about PHP
 
New Post
10/21/2006 2:31 PM
 

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/23/2006 9:48 AM
 

Sorry, but that didn't help.  I've set up a laptop running xp pro EXACTLY the same as a box running Windows Server 2003.  I've set up an instance of SQL server on both machines and given each the same SQL server db name, same user id, password, permissions, etc.  Laptop running XP pro works - server does not install.  I get the same errors indicated on this post.

I've seen several posts on this site indicating this same problem on Windows Server 2003.  Is there a conflict with that OS v. XP?

Michael

 
New Post
10/23/2006 10:32 AM
 

Post your connection string.

Thanks
Neadom


Neadom Tucker New to the wide world of .NET... I could care less about PHP
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQLExpress2005 Install on 4.03.05SQLExpress2005 Install on 4.03.05


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