(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Question

(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

Tara Kizer SSCommitted Points: 1789 More actions · Answer 1

Oh and then you need to restart the SQL Server service for it to take effect.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
Ramblings of a DBA (My SQL Server Blog)[/url]
Subscribe to my blog

SAFEKOM SSC-Addicted Points: 431 More actions · Answer 2

I give 1500 under IP All only but IPv4 still hav 1433 port on it do i need to change it too and what i hav to enter in Server Name in client computer?

I will also open 1500 port on firewall and let u know the update status.

Thanks alot.

Tara Kizer SSCommitted Points: 1789 More actions · Answer 3

You can change it under the other one if you want. I only ever touch the IPAll section. If you have multiple ones and they use a different port, SQL will be listening on them as can be seen in the SQL Server Error Log.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
Ramblings of a DBA (My SQL Server Blog)[/url]
Subscribe to my blog

SAFEKOM SSC-Addicted Points: 431 More actions · Answer 4

Problem is sorted out, In my case Sql ports were blocked in Local Security policies(win2008 server).

Click on below link to find out how to open ports for sql in LSP:

http://faq.1and1.com/dedicated_servers/windows_server/server_safety/5.html

/*Matt*/ Valued Member Points: 61 More actions · Answer 5

Thought I'd post a comment/possible solution...at least for me it was. Initially had a query running with a left outer join to a table in a db on a linked sever. I needed to move the database, referred to in that query via the linked server connection, to a different server. After moving the database, and repointing the pertinent portion of the query, I got this same "named pipes" error. The solution for me was to edit the linked server connection for the new server hosting the database - the username specified in the linked server connection did not have rights to the database on the new server. I'm going to try running a "synchronize logins" script on the original username used to make the linked server connection. That may have taken care of it, rather than changing the login name to one with rights.

nunezreinaldo Grasshopper Points: 11 More actions · Answer 6

In my case what it worked for me was the Hosts file in the folder C:\Windows\System32\drivers\etc

I was trying to connect into a SQL server with a name that has an entry in the HOSTS file; however, the IP in the HOSTS file was unreachable - Nonexisting - throwing the same exact error as posted here.

First, I connected using my SQL client using the IP address and it was no problem.
Next, I delete the entry for the SQL server name in the HOST file in the folder C:\Windows\System32\drivers\etc, saved it and again tried to connect into that SQL server using the name that I just deleted from the host file and it went thru without issues.

I hope it helps someone along the way