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 ...Hosting Company says itHosting Company says it's a bug in DNN
Previous
 
Next
New Post
9/27/2006 7:45 PM
 

I have similar problem installing Dotnetnuke. Where does it say in installation guide about having two database connection strings? And if I do define it twice, IIS just spits an error that 'SiteSqlServer' has already been added. The way I have done is define it once in <appSettings> section in web.config file - which is the section ASP.NET reads when starting Dotnetnuke.

I am still getting this error:

Error Installing DotNetNuke
Current Assembly Version: 04.03.05
ERROR: Could not connect to database specified in connectionString for SqlDataProvider

Part of my web.config file is below. And by the way, this web.config below returns correct parameters under IIS --> ASP.NET configuration settings.

Thanks for your help.

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

 
New Post
9/27/2006 9:22 PM
 
I found one issue but the orginial error has not changed

<appSettings>
    <!--<add name="
    <!--<add key="
    <!--<add key="
    <!--<add key="
    <!--<add key="
    <!--<add key="
  </appSettings>

With that fixed the error I still get is below

Server Error in '/dotnetnuke_ver4-3-5' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +125
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +5768
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.26; ASP.NET Version:2.0.50727.26


 
New Post
9/28/2006 12:41 AM
 

Did you comment out the SQLExpress connection string about 3 or 4 lines above this one?


Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
9/28/2006 12:46 AM
 
Is your host company using SQLExpress or SQL Server?  If they are using SQL Server as I expect, you need to comment out the two SQLExpress connection strings and remove the <!--  --> from around the SQL Server Connection String.  Configure it and see if that fixes the issue.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
9/28/2006 2:20 AM
 
caduceus wrote

I have similar problem installing Dotnetnuke. Where does it say in installation guide about having two database connection strings?       

DotNetNuke Installation Guide.pdf Page 35,36

Configuring web.config for Installation

......

There are three major differences between the 3.x web.config and the 4.x web.config:

36

DotNetNuke Installation Guide

Copyright © 2003-2005 Perpetual Motion Interactive Systems, Inc. All Rights Reserved.

1. In addition to the connection String setting under <appSettings> required in

3.x, 4.x also requires the same connection String to be set under the

<connectionStrings> section

 


Regards KM
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Hosting Company says itHosting Company says it's a bug in DNN


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