How do I fix the error 'Named Pipes Provider,

Question

I can't seem to connect to my database from a site. I get this error:

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

I tried using the local IP address to connect as well as a public one. I've tried:

1. Yes, the site can communicate with the server
2. Named pipes/TCP is enabled.
3. Remote connections are allowed.
4. Windows Firewall is off
5. Created an exception for port 1433 in Windows Firewall.
6. Enabled everything in SQL Server Configuration Manager.

What else can I do here?

Answer 1

I had the same problem and solved the problem by disabling my firewall(ESET).

The first step to solve this problem should be to try pinging your own computer from another computer. If you have firewall on, you may not be able to ping yourself. I tried pinging my own pc, then ping was failed(didnt get response from the server)

Answer 2

You will find most likely your DB name is not correct, you will see the server name in VS like "DESKTOP-0I14BKI" but if you open up SSMS you will see DESKTOP-0I14BKI\SQLBLAHBLAH , simply add "\SQLBLAHBLAH" (instance name) to your "server name" in VS connection properties.

You will see:

To Fix:

Answer 3

A thread on MSDN Social, Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server, has a pretty decent list of possible issues that are related to your error. You may want to see if any of them could be what you're experiencing.

• Incorrect connection string, such as using SqlExpress
• Named Pipes(NP) was not enabled on the SQL instance
• Remote connection was not enabled
• Server not started, or point to not a real server in your connection string
• Other reasons such as incorrect security context
• try basic connectivity tests between the two machines you are working on

Answer 4

I was trying to add a new connection in VS2015. None of the suggestions here worked. Suspecting some sort of a bug in the wizard, especially since SSMS was able to connect just fine, I decided to try and trick it. It worked!

1. Instead of adding the connection, use "Create new SQL Server Database". Enter your server name and a random name for the new DB, e.g. "test".

2. Assuming this succeeds, open Server Explorer in VS, locate the connection in Data Connections, right-click it and select Modify Connection.

3. Change "test" (from step 1) to the name of the existing database you want to connect to. Click "Test Connection". This time it should work!

4. Delete the temporary database you created in step 1.

Answer 5

I had just installed SQL SERVER 2012 developer. When I was creating my first SSIS package, I received this pipes error when I was trying to create a data connection task in SQL Server 2012 Data Tools in the Connection Manager box. I resolved with the help of the post above.

If choose a named instance and you call your named instance SSQDatabase1 and your pc's name is PCX1. You must enter PCX1\SSQDatabase1 not just SSQDatabase1 or you will receive the named pipes error.

Answer 6

I have one more solution, I think. I recently had changed my computer name so, after I couldn't connect still after trying all above methods. I changed the Server name.. Server name => (browse for more) => under database engine, a new server was found same as computers new name. This worked, and life is good again.