dlchase89 on Mon, 10 Dec 2012 21:48:45
I have seen the error below before and was always able to fix it by adding Network Service to the login of the SQL 2008 database. Now, however, I am getting a good connection on 1 database but failing trying to query the 2nd database (same sever) from our intranet asp.net app. Where else can I look? I have checked SQL configuration and all but VIA are enabled.
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)
RohitGarg on Tue, 11 Dec 2012 09:53:58
Error mention is the common error of connectivity. There are many reasons of SQL server connectivity issue.
If issue is with login on database then you will get different login error.
Try the below small checklist that helps to find out the real cause of connectivity issue.
1. Check SQL services are running
2. Check SQL Browser service is running
3. Check remote connections are enabled
4. Network connectivity between database & application servers by TRACERT command
5. Check TCP/IP protocol enabled at SQL server
6. Check talent connectivity – telnet <IP address> <port no on SQL server running>
7. Check UDP port 1434 is open or not on SQL Server
8. Check firewall is running or not Check
9. If firewall running, SQL Server & UDP port must be added in exception in firewall
This posting is provided with no warranties and confers no rights.
Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.