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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
The error message "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" typically occurs when there is an issue establishing a connection to a SQL Server database.
This error can occur due to various reasons, including:
Incorrect instance name: The instance name specified in the connection string or configuration settings may be incorrect. The instance name is the name of the SQL Server instance to which you are trying to connect. Make sure that the instance name is spelled correctly and matches the actual name of the SQL Server instance.
SQL Server configuration: The SQL Server may not be configured to allow remote connections. By default, SQL Server may be configured to only allow local connections. You need to configure SQL Server to allow remote connections if you are trying to connect to it from a different machine or over the network.
Network issues: There may be network-related issues such as firewall settings, network connectivity, or DNS resolution problems that are preventing the connection to the SQL Server. Ensure that the network is properly configured and that there are no network-related issues.
SQL Server not running: The SQL Server service may not be running or may have stopped unexpectedly. Make sure that the SQL Server service is running and is accessible.
Incorrect connection string: The connection string used to establish the connection to SQL Server may be incorrect or incomplete. Double-check the connection string and ensure that it contains the correct information, such as the server name, instance name, authentication method, and other required parameters.
Permissions and security: There may be permissions or security-related issues that are preventing the connection to SQL Server. Ensure that the user account used to establish the connection has the necessary permissions and privileges to connect to the SQL Server instance.
To resolve this error, you can try the following steps:
Verify the instance name: Double-check the instance name specified in the connection string or configuration settings and ensure that it matches the actual name of the SQL Server instance.
Check SQL Server configuration: Verify that SQL Server is configured to allow remote connections. You can do this by checking the SQL Server configuration settings and enabling the necessary options to allow remote connections.
Check network settings: Ensure that the network settings, such as firewall settings, network connectivity, and DNS resolution, are properly configured and not blocking the connection to SQL Server.
Start SQL Server service: Check if the SQL Server service is running and start it if it has stopped unexpectedly.
Verify connection string: Double-check the connection string used to establish the connection and ensure that it contains the correct information, such as the server name, instance name, authentication method, and other required parameters.
Check permissions and security: Ensure that the user account used to establish the connection has the necessary permissions and privileges to connect to the SQL Server instance.
Troubleshooting
1). Check whether the “SQL services” are running or not and whether they are on “Network Service” or not. Type "service" in the Windows search to open services. If services are not on the network, then move them there. To move SQL services to Network Service, please refer to this link: Move services to the network."
2). Type services in the Windows search bar and click “Open”
3). On the services window, look for SQL Server [instance name for Webgility], Right-click on ‘SQL Server [instance name for Webgility]’, and click Properties.
4). Click on “Log On” and then click “Browse.”
5). Type "network" and click on the “Check Names” button.
6). Click “Network Service” or “Network” and then click on “OK”
7). Remove the password from both fields and click on Apply> OK.
8). Right-click the SQL Server, and click Restart & now it will show services on “Network Mode”
9). You need to perform the same steps on “SQL Browser” as well.
10). Check “TCP/IP and the named pipes” to see whether they are enabled or not. Open “SQL Configuration Manager” and then go to “SQL Server Network Configuration> Protocols for Unify/Webgility” to enable the TCP/UDP pipes.
11). Check whether the “TCP/UDP” ports are added to the “firewall” or not. Follow this path “Control Panel\System and Security\Windows Defender Firewall,” and then click on “Advanced Settings” to check or add the ports in the firewall. Please refer to the below link to add ports to the firewall:
Perform the following steps on the machine where admin Webgility is installed when the add-on user is getting an error while connecting to the SQL database: Add ports to the firewall.
For adding the exceptions for “TCP” and “UDP” ports, perform the following steps:
Go to Start> Control Panel> Windows Firewall and follow the below steps:
Click on Advanced Settings:
Click on Inbound Rules in the leftmost upper corner:
Adding TCP Port:
Click on New Rule in the rightmost upper corner:
This window will open. Now click on Port as shown, and then click on Next:
Click on the TCP option and Specific local ports, add port “1433,” and click Next:
Select the first option. “Allow the connection” and click Next:
Select all three options. “Domain,” “Private,” and "Public,” and click Next:
Name the port TCP port and click on Finish:
Adding UDP Port:
Click on New Rules in the rightmost upper corner:
Select the “Port” option and click on Next:
Click on the UDP option and Specific Local Ports, add port 1434, and click Next:
Select the first option, “Allow the connection,” and click on Next:
Select all three options, “Domain,” "Private," and "Public,” and click on Next:
Add the name “UDP Port”:
Now add the Outbound Rules:
Adding TCP Port:
Click on New Rule in the rightmost upper corner:
This window will open. Now click on Port as shown, and then click on Next:
Click on the TCP option and Specific local ports, add port “1433,” and click Next:
Select the first option. “Allow the connection” and click Next:
Select all three options. "Domain," "Private,” and "Public,” and click Next:
Name the port TCP Port and click on Finish:
Adding UDP Port:
Click on "New Rules" in the rightmost upper corner:
Select the "Port" option and click on Next:
Click on the UDP option and Specific local ports, add port “1434,” and click Next:
Select the first option, “Allow the connection,” and click on Next:
Select all three options, “Domain,” “Private,” and Public,” and click on Next:
Add the name "UDP Port":
Go to the Start> Search option. Write ’services.msc’ and select Enter
Restart the following services:
>> SQL Server (Unify/Webgility)
>> SQL Server Browser
and try to connect through the add-on machine, Webgility will get connected to the admin database.
Note: If Webgility won’t get connected to the admin database, then follow the steps further for the above operations.
Click on Inbound Rules in the leftmost upper corner of the screen:
Click on "New Rule":
Select the option for Program and click Next:
Select Option “This program path:” and browse the path for Unify.exe as shown here:
Select Unify.exe and click Next.
Select the option “Allow the connection”:
Check all three boxes “Domain,” “Public,” and “Private” and click on Next:
Name the exception added as “Unify.exe” and click on Finish:
Add the same file to the exception list for the outbound rules as follows:
Click on the Outbound Rules:
Click New Rules:
Select “Program” option and click on Next:
Select the option "This program path: and browse the Unify.exe file to it as shown:
And select the Unify.exe file and click "open."
Once the Unify.exe file is browsed, click on Next:
Select the option “Allow the connection” and Next:
Check all three options available, i.e., “Domain,” “Private,” and “Public” and click on Next:
Name the rule Unify.exe and click on Finish:
Launch the Webgility and connect Webgility with the existing database by selecting the correct “database name” and then clicking on “Connect with SQL Authentication” to connect.
Username: “sa” and the Password: Webgility2011.
If you still get the error message, then please restart the server and log in to Webgility again. Webgility must get connected to the existing database, and if it doesn’t work after performing the above troubleshooting steps, then please contact Webgility Support for help.