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

Troubleshooting Common Causes of Database Connection Failures in Webgility Desktop

This article helps Webgility Desktop users identify and fix common causes such as network misconfigurations, firewall restrictions, incorrect credentials, and incompatible SQL drivers to restore proper database connectivity and integration.

Step-by-Step Troubleshooting

Step 1: Verify Network Connectivity

Check if the add-on machine can reach the SQL host:

      • Open Command Prompt and run:

        php-template
        CopyEdit
        ping <SQL host IP or hostname>
        telnet <SQL host IP or hostname> <port>

      • Replace <SQL host> and <port> with your database’s details (default SQL port is 1433)

If the Ping Fails, Confirm network cables or Wi-Fi connections are active and Check for VPN or firewall rules blocking traffic.

Step 2: Configure Firewall and Security Rules

  • On the add-on machine, allow outbound connections to the SQL port (e.g., 1433).

  • On the SQL Server, ensure inbound connections are allowed for the same port.

To allow SQL traffic in Windows Firewall:

  1. Open Windows Defender Firewall with Advanced Security

  2. Go to Inbound Rules > New Rule

  3. Choose Port > TCP > 1433

  4. Select Allow the connection

  5. Apply to all network profiles (Domain, Private, Public)

  6. Name the rule (e.g., SQL Port 1433)

Step 4: Confirm Authentication and Permissions

  • Ensure the database user account has permission to connect and perform the required actions.

  • If using Windows Integrated Authentication, verify:

    • The add-on machine is joined to the same domain

    • Group policy allows remote SQL access

  • If using SQL Authentication, confirm the login exists and is not locked or expired.

Step 5: Restart SQL services:
  • Type services in the Windows search bar and click ‘Open’ Look for the SQL Server [Instance name for Webgility], Right-click on ‘SQL Server and click Restart.
  • Similarly, right-click on the services for ‘SQL Server Browser’ and restart the services as mentioned above.
  • Once done re-try connecting the add-on user of Webgility with the main server.