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 ...CanCan't connect to database on install
Previous
 
Next
New Post
8/31/2006 1:06 PM
 

I have installed SQL Express with an instance name of CTHOG and set the login mode for mixed.  I then set a userid of sa with a password of cthog.  I can then use osql to connect to the database (using the cthog password)
c:\
>osql -U sa -S (local)\CTHOG
Password:
1>

I am assuming that since the 1> prompt appears, the connection was established and SQL Express is working.  I am not sure of other SQL Express setting are required...

I then tried to edit the web.config and set the Server=, uid= and pwd= values used above:

  <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)\CTHOG;Database=DotNetNuke;uid=sa;pwd=cthog;"
      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)\CTHOG;Database=DotNetNuke;uid=sa;pwd=cthog;"/>
    -->

However, when I attempt to connect the first time, I get an error that it could not connect to the database and the 2nd attempt results in an Assembly version not matching a database version.

Any help would be greatly appreciated.  I did only change those fields (Server=, uid= and pwd=) in web.config.  Maybe I should not have used mixed authentication in SQL Express?  Or was I supposed to set some other settings in SQL Express?  Any help would be appreciated!

 
New Post
8/31/2006 8:59 PM
 

As usual, worked for quite a while with no progress, so I posted the question and 10 minutes later figured it out...

Sorry to bother...

 
New Post
8/31/2006 10:05 PM
 

You have your "Connection String for SQL Server 2000/2005" connections still commented out.

Here is what you should replace it with (changes are in Red) ..

  <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)\CTHOG;Database=DotNetNuke;uid=USER;pwd=PASS;"
      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)\CTHOG;Database=DotNetNuke;uid=USER;pwd=PASS;"/>

Also, mixed authentication is correct, however, you should not use sa acct. Create a login, then a database user, then give the user dbo permissions after adding the user to your DotNetNuke database.

This is all explained in the installation guide, which you can get here.

One last thing .... never paste your uid or pwd here (I changed it to USER & PASS, so you will have to fix it if you paste the above text) .... you never know who might decide to "knock" on your sql back door



Gary
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...CanCan't connect to database on install


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