Skip to Content

Named Pipes Provider, error 40

This error arises usually for the first time a user attempts to connect the SQL Server 2005 using Visual Web Developer 2005.

"Named Pipes Provider, error 40 - Could not open a connection to SQL Server"

It is definitely not a good sign. However, the solution is very simple! Just that Microsoft had made it in a way such that the system becomes too rigid.

(let's go and find the solution...)

Apparently, when asked for the server name by the panel; instead of just specifying the server name, you should also include the instance name. For example,

COMPUTER123\SQLEXPRESS

where "COMPUTER123" is the server name and "SQLEXPRESS" refers to the instance name - which is the default used by SQL Server 2005.

If that did not solve the issue, you can try the 2 steps below:

  1. Enable "Named Pipes & TCP" from the SQL Server Configuration Manager (presumably you have installed it together with SQL Server 2005.
  2. Enable "Local and Remote" connections from the SQL Server Configuration Manager.

Finally, restart the SQL Server (service). That should solve it, nonetheless.

Trackback URL for this post:

http://www.neohide.com/trackback/212

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options