Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...I have three SQLServer connection stringsI have three SQLServer connection strings
Previous
 
Next
New Post
10/5/2010 3:58 PM
 
kcsurfer


Joined: 2/21/2007
Posts: 56
Recently, I was trying to install/add a 3rd party module and was having issues. While troubleshooting. the module builders looked at my web.config and said I have three SQL Server connections strings. I am not sure how this is the case and I don't have much SQL experience either. Can someone help me with this?
 
New Post
10/5/2010 5:39 PM
 
Chris Hammond


Chris Hammond's Avatar

Chris Hammond's Avatar

Chris Hammond's Avatar

www.christoc.com
Joined: 1/14/2003
Posts: 7319
Well, typical DNN installs with have two connection strings, but it's possible that you have 4 total, with 2 of them actually being commented out in the web.config file. Do you have a copy of your web.config handy? If so post the connection string info here, BE SURE TO REPLACE ANY SENSATIVE INFO SUCH AS USERNAMES AND PASSWORDS WITH DUMMY TEXT
Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/5/2010 5:55 PM
 
kcsurfer


Joined: 2/21/2007
Posts: 56
Chris Hammond wrote:
Well, typical DNN installs with have two connection strings, but it's possible that you have 4 total, with 2 of them actually being commented out in the web.config file. Do you have a copy of your web.config handy? If so post the connection string info here, BE SURE TO REPLACE ANY SENSATIVE INFO SUCH AS USERNAMES AND PASSWORDS WITH DUMMY TEXT

 Hi Chris, 

Thanks for your response. Here you are the connection strings from different lines from the web.config.

<connectionStrings>
    <!-- Connection String for SQL Server 2005/2008 Express -->
    <add name="SiteSqlServer" connectionString="Server=REMOVED" providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2005/2008
    <add name="SiteSqlServer" connectionString="Server=REMOVED" providerName="System.Data.SqlClient" /> 
    -->
  </connectionStrings>
<appSettings>
    <!-- Connection String for SQL Server 2005/2008 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Server=(local);Database=REMOVED;" />
    <!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=REMOVED"/>
    -->


<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="SiteSqlServer" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="0" requiresUniqueEmail="false" passwordFormat="Encrypted" applicationName="DotNetNuke" description="Stores and retrieves membership data from the local Microsoft SQL Server database" />

<add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo" />
 
New Post
10/5/2010 6:02 PM
 
Chris Hammond


Chris Hammond's Avatar

Chris Hammond's Avatar

Chris Hammond's Avatar

www.christoc.com
Joined: 1/14/2003
Posts: 7319
The things in bold below are actually commented out, they are inbetween <!-- AND --> meaning they are just comments and could be removed. You basically have two connection strings, the ones that DNN requires, I have them in italics below

<connectionStrings>
    <!-- Connection String for SQL Server 2005/2008 Express -->
    <add name="SiteSqlServer" connectionString="Server=REMOVED" providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2005/2008
    <add name="SiteSqlServer" connectionString="Server=REMOVED" providerName="System.Data.SqlClient" /> 
    -->
  </connectionStrings>
<appSettings>
    <!-- Connection String for SQL Server 2005/2008 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Server=(local);Database=REMOVED;" />
    <!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=REMOVED"/>
    -->
Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/8/2010 2:39 AM
 
kcsurfer


Joined: 2/21/2007
Posts: 56
Hi Chris, 
The module developer suggests I remove one connection string. They say that the module (the one I am trying to use) uses whatever DNN uses; however, DNN may be trying another connection. Can you advise on which connection string I should remove (or comment out ) to test this?
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...I have three SQLServer connection stringsI have three SQLServer connection strings


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