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

How to Fix Database Connection Issues in Webgility Desktop

This article helps Webgility Desktop users diagnose and resolve SQL connection errors in Webgility Desktop that prevent the application from connecting to its database. It provides clear steps to troubleshoot and fix these issues, helping restore smooth operation.

Causes of Issues:

  • SQL Server service is not running: The service that hosts your database might be stopped.

  • Disabled network protocols: TCP/IP or Named Pipes are not enabled, preventing connectivity.

  • Firewall blocks: Your firewall may be blocking the SQL server ports.

  • Certificate authorization errors: The connection between Webgility and QuickBooks may be blocked by a rejected certificate.

  • Corrupted or missing database files: Database components may be damaged or incomplete.

Step-by-Step Instructions:

1. Verify SQL Services Are Running

  • Press Windows + R, type services.msc, and press Enter.

  • Locate "SQL Server (Unify)" or your instance name.

  • If the status is not "Running", right-click and choose "Start".

  • Do the same for "SQL Server Browser".

 2. Enable SQL Server Network Protocols

  • Open SQL Server Configuration Manager.

  • Under SQL Server Network Configuration, click "Protocols for ".

  • Enable both TCP/IP and Named Pipes (right-click > Enable).

  • Restart the SQL Server services.

3. Adjust Firewall Settings

  • Open "Windows Defender Firewall with Advanced Security".

  • Create new inbound rules for:

    • TCP Port 1433 (for SQL Server)

    • UDP Port 1434 (for SQL Browser)

  • Allow these ports for both Private and Public networks.

4. Regenerate QuickBooks Certificate (If Prompted)

  • In QuickBooks: Edit > Preferences > Integrated Applications > Company Preferences

  • Remove the Webgility certificate.

  • In Webgility: Go to Integrations > Accounting/POS/ERP > Edit Connection

  • Click "Test QuickBooks Connection" and accept the new certificate prompt.

5. Test Database Connection in Webgility

  • Launch Webgility Desktop.

  • Go to System > Database > Test Connection.

  • If "Connected" appears, you're all set.

6. Restore or Repair the Database (if needed)

  • Go to System > Database > Restore

  • Select the latest UnifyDB.bak file.

  • Follow the prompts to restore.

Note: Always create a backup before making any changes. You can find your SQL instance name by opening: C:\Webgility\UnifyEnterprise\XML\apiconfig using Notepad. Look for the value under <SourceName>.