Shawn Weisfeld

I find when I talk to myself nobody listens. - Shawn Weisfeld
posts - 352, comments - 144, trackbacks - 34

My Links

News

The views expressed in this blog are mine and mine alone, not that of my employer, Microsoft, or anyone else’s. No warrantee is given for the quality of any material on this site.

Archives

Post Categories

Could not open a connection to SQL Server

Problem:

.NET application throws the following error.

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)

clip_image002

Solution:

Check SQL Server to ensure that TCP/IP is enabled. Open the List of available “Protocols for SQL Server”. You can find this in the “Computer Management” Console under “Services and Application”, “SQL Server Configuration Manager”, “SQL Server 200X Network Configuration.” After you enable TCP/IP you will need to restart the SQL Server relational engine. You can do that using the “SQL Server 200X Services” option.

clip_image004

Print | posted on Wednesday, July 08, 2009 11:44 AM | Filed Under [ SQL ]

Feedback

Gravatar

# re: Could not open a connection to SQL Server

still generates th same error when connecting to the database
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)
help please.
7/26/2011 8:33 AM | william

Post Comment

Title  
Name  
Email
Url
Comment   
Please add 8 and 4 and type the answer here:

Powered by: