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

Fixing Webgility Desktop Database Connection Failures Caused by Service, Firewall, or Network Settings

This article helps Webgility Desktop users in troubleshooting and restoring database connection issues in Webgility Desktop. These problems are commonly caused by incorrect service settings, firewall restrictions, or network permission conflicts. The guide provides step-by-step instructions to identify the root cause and re-establish a successful connection to the Webgility Desktop database.

If you're unable to connect to the Webgility database in Webgility Desktop, you're not alone—this is a common issue often caused by service settings, firewalls, or network permissions. Here is your step-by-step guide to troubleshoot and restore your database connection.

Causes of Connection Issues

  • SQL Server not running or misconfigured

  • Incorrect SQL authentication

  • TCP/IP protocol or named pipes disabled

  • Firewall blocking database communication

  • Missing instance name or services

  • Antivirus interference

  • Hosting restrictions (for cloud-hosted QuickBooks environments)

Steps to Resolve Database Connection Issues

1. Verify SQL Database Location

  • Make sure you're on the Primary Workstation where the Webgility SQL database is hosted.

  • Open the Services app (type services.msc in Start menu).

  • Look for SQL Server (Database Name):

    • If not listed, SQL is hosted on another machine.

    • If listed but not running, right-click and Restart the service.

2. Confirm SQL Server & Browser Services

  • Open the Services application.

  • Locate and right-click on:

    • SQL Server (Database Name)

    • SQL Server Browser

  • Select Properties > Log On tab.

    • Click Browse, select Network Service.

    • Remove any existing password fields.

    • Click Apply, then OK.

  • Restart both services.

3. Enable TCP/IP and Named Pipes

  • Open SQL Server Configuration Manager.

  • Under SQL Server Network Configuration, enable:

    • TCP/IP

    • Named Pipes

  • Restart the SQL services after enabling.

4. Restart SQL Services

  • After making changes, return to Services and restart:

    • SQL Server (Database Name)

    • SQL Server Browser

5. Configure Firewall Rules

  • Go to C:\Webgility\UnifyEnterprise.

  • Right-click on wgFirewall.exe and select Run as Administrator.

  • This automatically sets up firewall permissions for Webgility.

6. Whitelist Webgility in Antivirus

  • Open your antivirus software.

  • Add C:\Webgility to the Exemption/Exclusion List.

  • Restart Webgility Desktop afterward.

7. Select the Correct SQL Instance

  • In the Webgility Database Configuration screen:

    • Choose Locate SQL Server.

    • If your instance doesn’t appear, click Browse for more.

    • Select the correct instance, typically:
      ComputerName\UNIFY

8. Use SQL Authentication (For Add-On Machines)

  • On add-on computers, select SQL Server Authentication.

    • Username: sa

    • Password: Webgility2011 (note the capital W)

9. If Using QuickBooks Hosting Providers

  • If your QuickBooks file is hosted by Rightworks, Summit Hosting, etc.:

    • Contact their customer support to verify SQL connection settings.

    • Hosted environments may have specific restrictions or configuration requirements.