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 ...SQL Server ErrorSQL Server Error
Previous
 
Next
New Post
7/21/2007 8:07 AM
 

Hi,

We upgraded to 4.5.3 a few weeks ago.  For the most part, all seemed to be working fine (the few sites we upgraded were very simple sites).  But today I noticed that when adding certain new modules (i.e. it happens for the repository module, but not for the text/html module) to a site, I am getting an error that shows up inside the page:

A critical error has occurred.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

After doing some research, my hunch is that this has to do with our web.config file - specifically, the connection strings.  When I looked at it, I realized that we seem to have a connection to BOTH SQL Server 2005 and SQL Express.  When I try to comment out the SQL Express connection string and bring in the SQL Server string, ALL sites completely crash.  Below is the relevant section of our web.config file:

 

<

<!--

<add

name="SiteSqlServer"

connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"

providerName="System.Data.SqlClient" />

connectionStrings> Connection String for SQL Server 2005 Express

-->

<!--

<

</

<

<!--

<

<!--

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=USERID;pwd=PASSWORD;"/>

 

<

Connection String for SQL Server 2000/2005 -->add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=USERID;pwd=PASSWORD;" 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="InstallTemplate" value="DotNetNuke.install.config" />

Any thoughts?

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Server ErrorSQL Server Error


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