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 2:17 PM
 
IJ Singh

Joined: 3/3/2008
Posts: 18

Hi,

I moved an existing DNN installation to 2 different Windows XP ( Service Pack 3 ) machines. One of them is working fine but the second one is constantly giving me the following error. I have compared the 2 machines and found that nothing is different on them. But still only one of the moved installations works whereas the second one keeps on saying

 

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

 

I have checked all SQL Server 2005 settings and also cross checked the web.config a few times.

Can someone tell me what I could be missing

 

Thanks and Regarsd

 
 
New Post
10/3/2009 3:01 PM
 
Robert J Collins


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

In the SQL Server folder under All Programs in the Start menu you will see a Configuration Tools folder and within it a SQL Server Connection Manager.

Open it and then go to: SQL Native Client Configuration > Client Protocols.  In the right pain you will then see the various protocols such as Named Pipe, TCP/IP, etc.  Make sure Named Pipes is Enabled.  If not Enabled, Enable it and then restart the SQL Services.

This is where I would start in trouble shooting.  If this does not fix the issue, please post back.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

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

Joined: 3/3/2008
Posts: 18

Hi Robert,

Thanks for responding. Named Pipes is enabled on my SQL server instance.

Regards

IJ

 
 
New Post
10/3/2009 3:16 PM
 
Robert J Collins


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

Hmm.. If the DNN Site and DB are on the same box this is the preferred communication protocol, however you could also try disabling it to see if you can force it to use TCP/IP and see if that gets you connected...

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
New Post
10/3/2009 3:46 PM
 
IJ Singh

Joined: 3/3/2008
Posts: 18

Did not work.

I saw that the order of the Protocols was

Shared Memory

TCP/IP

Named Pipes.

 

I modiifed the order to put Named Pipes ahead of TCP/IP too but that also did not work

 
 
 Page 1 of 3
123Next 
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