Fix SQL Server Error 53: Could not open a connection on SQL Server
Today, I will explain how to fix SQL Server error 53 (The network path was not found). The details about SQL error 53 are given as “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 on SQL Server) (Microsoft SQL Server, Error : 53)”
You can also get below error similar to error 53 under below details.
An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Microsoft SQL Server Error 53 looks very much like the Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server at first look. Like SQL Server error 40, here also SQL Server client cannot connect to the SQL Server Instance. This error could occur because either the client cannot resolve the name of the server or the name of the server is incorrect.
You might get this issue due to other reasons as well although main reason is the wrong server name or port name. I have given all those possible reasons behind the Microsoft SQL Server error 53 in below points.
- Wrong SQL Server Instance name while establishing database connection.
- Entering wrong port no can be one of the reason for SQL Server error 53.
- SQL Server Instance is not accessible due to firewall or any reason.
- Telnet port 1433 or port no on which SQL Server is running. These ports might be blocked.
- TCP/IP or Named Pipes protocol is disabled in SQL Server Configuration Manager.
- Remote Connection is disabled for this SQL Server Instance.
- SQL Server Browser service is stopped.
We need to check and validate multiple factors to rectify Microsoft SQL Server error 53. Check all factors given in below step by step points to fix all possibilities for this error.
- Sometimes, we enter wrong server details by mistake. Make sure to enter correct SQL Server instance name while making database connection otherwise you will face sql error 53.
- Try to connect using ip address and port number instead of putting server name in connection string.
- Make sure SQL Server services are running fine and its accessible.
- Check firewall details. Firewall should open between your client machine and database server. Port 1433 and 1434 should be enabled. Telnet both ports to make sure ports are open.
- Make sure to enable TCP/IP and Named Pipes. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and click on Protocols for MSSQLSERVER. MSSQLSERVER is SQL Server Instance name. Now you will see all protocols in to right side pane. Right click on given protocols and select Enable button to enable both protocols.
- Check TCP/IP name resolution, you can use the ping command in the Windows operating system. You can also right-click on TCP/IP and select Properties in SQL Server Configuration Manager. Verify that, under IP2, the IP Address is set to the computer’s IP address on the local subnet. Scroll down to IPAll. Make sure that TCP Dynamic Ports is blank. Make sure that TCP Port is set to 1433 or your identified port no.
- Remote connection must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.
- SQL browser service should not be stopped if your security policy allows it. If you have disabled this service to apply hardening then make sure to pass port no along with SQL Server instance name/IP while making database connection.
- Fix Error 28 – Server doesn’t support requested protocol
- Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server
- Error 4064: Cannot open user default database. Login failed.
- Fix Login Drop issue Error 15138 and Error 3729
Latest posts by Manvendra Deo Singh (see all)
- Understanding Hybrid Buffer Pool in SQL Server - December 30, 2018
- Fix:VIEW SERVER STATE permission was denied on object ‘server’, database ‘master’ - August 30, 2018
- SQL Server Error 5184: Cannot use file ‘I:\Path\Techyaz.mdf’ for clustered server - August 29, 2018