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 ...Could not connect to databaseCould not connect to database
Previous
 
Next
New Post
4/6/2007 12:32 PM
 

I am installing DNN 4.3.7 on Server 2003 SP1 with SQL 2000 SP4 and getting this error when installing:

Could not connect to database specified in connectionString for SqlDataProvider.

So I have a couple of quesitons.  It says to first rename the release.config to web.config.  There already is a web.config so Im not sure what to do here...

 Also does DNN have a preference when it comes to SQL authentication, Windows vs. Mixed Mode?

I am using the login I setup for the DotNetNuke SQL database in the config file vs. using sa or Administrator - just want to make sure that is correct. 

Also does DNN prefer the instance of SQL to be registered in Enterprise Manager as (Local) or should it be re-registered with the ServerName?

TIA

 
 
New Post
4/6/2007 1:18 PM
 
  • in the install package, web.config shall be same as release.config
  • SQL server authentication method is dependng on your network security concept and has no impact on DNN performance or front end security
  • Here is an article about hardening DNN security that includes a recommendation to use a different account and how to st it up.
  • Server registration has no issue on the DNN access as long as web server and db server are installed on same machine

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/6/2007 1:37 PM
 

Just to expand on what Leupold says on the fourth point, the registration of the SQL server name in Enterprise Manager has nothing to do with a client, any client, (in this case DNN) connecting to the database.  You don't even need to have Ent Mgr there, that is only for Admins.

Carlos

 

 
New Post
4/6/2007 2:51 PM
 

 

After reading through some of the posts it looks like even though I had my data connection strings right, they were commented out.  I guess DNN expects SQL 2005 Express as its default DB.  Here is a snippet from my web.config - Ive bolded where I had to move the commenting to allow it to read my SQL 2000 DB.

<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=dnnuser;pwd=dnnuser;" 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=dnnuser;pwd=dnnuser;" />
    <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-->
    <add key="InstallationDate" value="4/6/2007" />
  </appSettings>

 
New Post
4/6/2007 10:19 PM
 

I am encountered same ploblem. I find a way out of this ploblem mentioned below.

server:windows server 2003

database : sql server 2000 standard edition

Don't create database with enterprise mangager.

If you make database with enterprise mangager,please delete it.

Then  use command porompt.

command line

logid:osql -U sa -P [your password] -S servername]
create database [your database name]
...

Without this ,I use 'full'  connction string like...

workstation id=[hostname];packet size=4096;user id=sa;data source=localhost;persist security info=True;initial catalog=[your database name];password=[your password]

and server mode make mix mode.

But last two is not neccesary,I think.

Please try again.

I am Japanese,so I am not good at English.

I am happy if you look ut my site.


http://www.synapsoid.jp/dotnetnuke/

http://www.synapsoid.jp/ghg/

But  these are Japanese site.....

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Could not connect to databaseCould not connect to database


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