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.
This indicates there is an issue with connecting to the SQL Server database. This error can arise from several causes:
Common Causes of Error 26:
Incorrect Instance Name:
The instance name provided in the connection string might be incorrect. Verify that the instance name matches the actual SQL Server instance.SQL Server Configuration:
SQL Server may not be configured to allow remote connections, particularly if it's set to only accept local connections. Ensure that the server is configured to allow remote access if needed.Network Issues:
Network-related issues such as firewall settings, connectivity problems, or DNS resolution failures may be blocking the connection. Check network settings to ensure smooth communication.SQL Server Not Running:
The SQL Server service might be stopped or not running. Confirm that the SQL Server service is active.Incorrect Connection String:
The connection string might be incomplete or contain errors. Ensure all parameters, such as the server name, instance name, and authentication method, are correct.Permissions and Security:
Ensure that the account trying to connect has the necessary permissions to access the SQL Server instance.Antivirus Software:
Some antivirus software may block the connection to SQL Server. Temporarily disable or configure your antivirus settings to allow the connection.
Steps to Resolve Error 26:
1). Verify Instance Name:
Check that the instance name in your connection string is correct and matches the actual SQL Server instance.
To verify, first find the correct computer name which has the SQL installed.
Then on that computer open Sevices window and find SQL servers
If you see ‘SQL server Unify’ or ‘SQL server Webgility’ in the list, then that is the name fo the instance.
2). Review Network Settings:
Check for any network or firewall issues that might be blocking access to SQL Server, such as misconfigured firewall settings or network connectivity problems.
Try temporarily disabling the Firewall.
3). Start SQL Server Service:
Ensure that the SQL Server service is running. If it has stopped, Restart it.
4). Verify Connection String:
If you get the configuration form then review the connection string and make sure it contains the correct server name (server computer name) with the instance name
5). Check Antivirus Settings:
Temporarily disable or adjust your antivirus software to ensure it’s not blocking the SQL Server connection.
Mandatory Steps
1. Check SQL Services Status
Verify if the SQL services are running and if they are set to “Network Service.”
Open the Windows Services application and check if SQL services are running.
If necessary, move them to “Network Service” by following these steps: [Move SQL services to Network Service].
2. Activate SQL Protocols
Access the SQL Server Manager by navigating to C:\Windows\SysWOW64, searching for ‘SQLServerManager’, and selecting the relevant version.
Expand SQL Server Network Configuration and select Protocols for [DatabaseName].
Enable all protocols (Shared Memory, Named Pipes, and TCP/IP) by right-clicking and activating each.
3. Configure Firewall Settings
If your firewall is enabled, run the Webgility firewall configuration tool:
Navigate to C:\Webgility\UnifyEnterprise.
Right-click WgFirewall and run it as an administrator.
If prompted with an error, select the first option.
Next, on the primary SQL server computer:
Open Allow an app through Windows firewall from the Start menu. Ensure that all checkboxes (Public, Private, and Domain) are selected for Webgility (ECC)apps.
Connecting Webgility to SQL Server
Open Webgility.
Select the correct database and choose "Connect with SQL Authentication."
Username: sa
Password: Webgility2011
Additionally
Check Permissions:
Confirm that the user account has the appropriate permissions to connect to the SQL Server.
Restart the SQL server computer:
After performing the above steps, try restarting the server computer.
If the error persists, restart the server and try reconnecting. If further issues occur, contact Webgility Support for assistance.
Still facing the issue?