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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Named Pipes Provider, error: 40 - Could not open a connection to SQL ServerNamed Pipes Provider, error: 40 - Could not open a connection to SQL Server
Previous
 
Next
New Post
10/3/2009 5:03 PM
 
Robert J Collins


www.netlogiccorporation.com
Joined: 9/26/2003
Posts: 1021

Do you have more than one instance and more than one version of SQL on the system? 

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
10/3/2009 5:06 PM
 
IJ Singh

Joined: 3/3/2008
Posts: 18

Yes Robert I do.

A SQL200o instance which is the default instance and a SQL 2005 instance which is a named instance, and is being for DNN
 
New Post
10/3/2009 5:09 PM
 
Robert J Collins


www.netlogiccorporation.com
Joined: 9/26/2003
Posts: 1021

In my last post (directly above this) I forgot to ask what version(s) of SQL are you running?

Also, is the SQL Instance Name the same on both PCs?  I.e. is the site was pointing to .\SqlExpress and on one PC that is the case (.\SqlExpress) but the other is .\Sql2k8Express, then you would need to update the Connection String in the Web.Config.

Here is an article I found that has several troubleshooting steps to work through this issue.  Take a look and see of this helps:
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx

Let me know if none of this helps (be sure to add answers to my questions above).

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
10/3/2009 5:18 PM
 
IJ Singh

Joined: 3/3/2008
Posts: 18

Hi Robert

I do see in the Config Manager under the Protocols for SQL2005 section that Named Pipes is disabled. But this is true for the machine on which the moved DNN is working fine. So I would guss this is not the cuse for not being able to connect.

As I mentioned in my last psot. I am using SQL2000 as a default instance and SQL2005 as anamed instance n both the machines. The instance names for SQL2005 differ only in the machine names, and I have modified the web.config to reflect this.

I did go through the article but it did not help me at all.

Thanks for the effort

 
 
New Post
10/3/2009 5:20 PM
 
Robert J Collins


www.netlogiccorporation.com
Joined: 9/26/2003
Posts: 1021

I had a similar issue this week with a system that was originally running SQL 2k and then we installed SQL 2k8.  We could access both using SQL Management Studio but not from a DNN Instance.  With us we were connecting via TCP/IP (disabled Named Pipes since the SQL and Web were different machines).  What we ended up doing was opening the SQL Config Manager (the one I noted earlier) and we disabled Named Pipes and then Enabled TCP/IP and in its properties we selected a different port number (since SQL 2k and 2k8 were both fighting for 1433).  We selected 5010 and manually set it in the TCP/IP settings in the config manager (in TCP/IP of the correct instance which in our case was 2k8).  Then we did a restart and all worked well.  If it isn't a different instance name as mentioned above and the article noted does not do it, try the same and see if that works.   Make sure you make the TCP/IP change and Named Pipes disable for the right SQL Instance (your 2k5 instance that you are trying to us).  You will see a couple since you have more than one instance.  When you open the properties you will see an IP Address tab and that is where you can change the port number...

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Named Pipes Provider, error: 40 - Could not open a connection to SQL ServerNamed Pipes Provider, error: 40 - Could not open a connection to SQL Server


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