Skip to content
  • There are no suggestions because the search field is empty.

Connecting an Additional Computer to Your Webgility Database

This article helps Webgility Desktop users in addressing the root causes and resolution steps for database connection issues between an add-on computer and the primary Webgility Desktop database machine. These issues typically occur due to network configuration problems, SQL instance access restrictions, or mismatched system settings.

Having trouble connecting an add-on computer to your Webgility SQL database? This guide outlines the key causes and walks you through troubleshooting steps to resolve the connection issue between your primary and secondary systems.

Causes of Connection Issues

Here are some common reasons you may not be able to connect your add-on system to the SQL database:

  • Incorrect database credentials – Wrong username or password.

  • Network issues – The computers aren’t on the same network or can't communicate.

  • Firewall restrictions – The Windows Firewall is blocking SQL or Webgility services.

  • Database server issues – The SQL Server isn't configured to accept remote connections.

  • Database is offline – The SQL Server service may be stopped.

Step-by-Step Instructions

1. Run Webgility Firewall Utility

  • Go to C:\Webgility\UnifyEnterprise.

  • Right-click on WgFirewall and choose Run as Administrator.

  • If prompted with options, select the first option to allow access.

  • Perform this step on both the primary and add-on computers.

2. Allow Webgility Through Windows Firewall

  • On the primary computer, open the Start Menu and search for Allow an app through Windows Firewall.

  • Locate all eCC entries.

  • Ensure all checkboxes (Private, Public, and Domain) are selected.

3. Launch Webgility on Add-On Computer

  • Open the Webgility application.

  • When prompted, choose Connect to an existing SQL Server.

  • Use the Locate SQL Server dropdown or select Browse to discover the database over the network.

4. Identify the Correct SQL Server

  • The server name will appear as: ComputerName\DatabaseName.

    • Example: DESKTOP123\WEBGILITY or SERVER01\UNIFY

  • This information must match the primary machine hosting the SQL database.

5. Authenticate with SQL Credentials

  • Choose Use SQL Server Authentication.

  • Enter the following credentials:

    • Username: sa

    • Password: Webgility2011 (Note: capital W)

  • Click Connect to establish the link.

Notes

  • Ensure both systems are on the same local network.

  • If SQL is installed with a custom instance name, make sure to use the correct server format: ComputerName\InstanceName.

  • Make sure SQL Server is configured to allow TCP/IP connections and SQL Browser service is running.