Problem:
If on clicking the “Login” button, you receive this message after about 90 seconds:
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)
Solution:
Check for the following:
1) Go to services and see if SQL service is running. May say Automatic but not started.
2) Check if the SQL server instance is specified correctly in the CABINET Registration
3) Check if Allow Remote Connections has been specified using SQL Configuration tool
Note: RESTART the SQL Server Service for the settings to take effect and close SQL Management Studio before you do this.
Note: VIA is to be disabled. If VIA is required to be enabled you can specify the IP address that is to be used by enabling the IP address of interest.
To enable the IP address, double click on TCP/IP, go to IP Addresses Tab. Select your IP Address and enable it.
Finally RESTART the SQL Server Service for the settings to take effect and close SQL Management Studio before you do this.
4) If the Instance has been set to server name instead of IP address in the registration window, change to IP address, re register and try again.
5) Check to see if the server or client has windows firewall turned on. If firewall is ON, set exceptions to SQL server program and the SQL ports 1433 and 1434. (Check both “Windows Firewall” as well as “Windows Firewall With Advanced Security”)
6) Check to see if a 3rd party firewall is being employed. E.g.: Trend Micro, Bit Defender etc. If so turn it off to see if that fixes the issue. If it does fix the issue turn on the program and then set exception to the CABINET SAFE executables & ports (8993, 8994, 11000) and SQL program & ports(1433, 1434).
Comments
Please sign in to leave a comment.