How to solve SQL Connection Issues for Add-On Computers in Webgility Desktop
This article helps Webgility Desktop users in addressing issues encountered when setting up an add-on computer with Webgility Desktop, specifically problems connecting to the existing SQL database on the primary machine. It covers common causes such as incorrect credentials, network configuration, and firewall restrictions.
When setting up an add-on computer with Webgility Desktop, you might encounter issues connecting to the existing SQL database hosted on your primary machine. This can happen for several reasons, including incorrect credentials, network configuration, or firewall restrictions.
Below are common causes and step-by-step troubleshooting instructions to help you resolve the issue.
Common Causes
-
Incorrect SQL Server credentials
-
Network connectivity issues
-
Firewall blocking access
-
SQL Server not running or unavailable
-
Misconfigured database settings
Step-by-Step Troubleshooting
1. Run Webgility Firewall Utility as Administrator
On both the primary and add-on computers:
-
Navigate to:
C:\Webgility\UnifyEnterprise
-
Right-click on WgFirewall.exe
-
Select Run as Administrator
2. Configure Windows Firewall Settings on Primary Computer
On the computer hosting the SQL database:
-
Open the Start menu and search for Allow an app through Windows Firewall.
-
Find and enable all eCC Ports/Browser/SqlServer by checking the boxes for Private, Public, and Domain (if applicable).
3. Attempt to Connect from Add-On Computer
Now move to the add-on computer:
-
Launch Webgility Desktop.
-
When prompted to install or connect to a database, choose:
"Connect to an existing SQL Server" -
In the Locate SQL Server drop-down, select the server that appears in the format:
ComputerName\DatabaseName
-
Example:
MainPC\UNIFY
orMainPC\WEBGILITY
-
💡 If your SQL Server isn't listed, click Browse to manually locate available servers on the network.
4. Enter SQL Server Credentials
In the authentication window:
-
Select Use SQL Server Authentication
-
Enter the following credentials:
-
Username:
sa
-
Password:
Webgility2011
(note: W is capitalized)
-
-
Click Connect
Still Can't Connect?
If you're still unable to connect after completing these steps:
-
Double-check your network connectivity between computers.
-
Confirm that SQL Server is running on the primary machine.
-
Ensure that no antivirus or third-party firewall software is blocking the connection.