|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| ||||||||||||||||||||||||||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
June 9th, 2009, 12:59 PM
|
|||
|
|||
|
Named Pipes Provider: Error 40
Greetings, all.
I've got a new problem that just came up. Everything had been running fine. I'm getting a message on my SQL 2005 server 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 the SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) I've verified that it is accepting remote connections. I'm not aware of anything else being changed! Any assistance would be great. Thanks. Steve
|
|
#2
June 10th, 2009, 10:56 PM
|
||||
|
||||
|
Firewall change perhaps? Check the event logs on both the server and the client machines, you just might find more clues. Is it possible someone might have accidentally changed the server name in a connection string somewhere? Has there been a restore from backup lately?
__________________
My worst nightmare was a pointless infinite loop. Work in progress; don't poke the curmudgeon! http://www.odonahue.com/
|
|
#3
June 11th, 2009, 10:18 AM
|
|||
|
|||
|
Quote:
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
|
|
| Viewing: Dev Shed Forums > Databases > MS SQL Development > Named Pipes Provider: Error 40 |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
