SQL Server Named Pipes Provider Error 40

by dcurtis 7/20/2008 7:10:00 AM

So, I had the following scenario at a customer:

  • They were moving a SQL Server 2000 database from one server to another
  • All of the references to connection strings in the application were updated to point to the new database
  • The data was moved from the old database to the new database and the old database was shut down

Everything seemed great; however, there was one ASP.NET 2.0 application that kept throwing the following error:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

 We scratched our heads for awhile on this.  We couldn't figure out why it was throwing a 2005 error when the database we were connecting to was 2000.  Further, we were absolutely positive that we had updated all of the connection strings...until I remembered that this application used a membership provider for authentication that was defined in the machine.config configuration file.  We updated the machine.config, and everything started to run without error.

Currently rated 3.0 by 5 people

  • Currently 3/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags: , , ,

Powered by BlogEngine.NET 1.3.0.0
Theme by Mads Kristensen

About the author

Derek Curtis Derek Curtis
President, Plaid Pony Technology Solutions LLC

E-mail me Send mail

Calendar

<<  November 2017  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

View posts in large calendar

Pages

    Recent comments

    Authors

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

    © Copyright 2017

    Sign in