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

How to Fix “Access Denied” and SQL Server Connection Errors When Installing Webgility Desktop on Additional Computers

This article helps Webgility Desktop users resolve “Access Denied” or SQL Server connection errors encountered when installing Webgility Desktop on an additional computer. It provides guidance on fixing network permissions, correcting SQL Server instance names, and adjusting authentication settings to ensure a successful connection to the existing Webgility Desktop setup.

Common Symptoms

  • Webgility Desktop cannot connect to the database during installation.
  • You receive “Access Denied” or “Login Failed” errors.
  • SQL instance name is not found or not responding.
  • The secondary PC can't detect the Webgility API or SQL Server.
     

Step-by-Step Troubleshooting and Resolution

Confirm Network Connectivity
  • Make sure the new PC is on the same network as the primary machine or SQL Server.
  • Try a ping test to the server’s hostname or IP to confirm reachability.
  • Check that firewall settings are not blocking SQL Server traffic (typically TCP port 1433 or dynamic port ranges for named instances).

Check User Permissions
  • Ensure your Windows user account on the new PC has access to shared folders and mapped drives used by Webgility Desktop.
  • Confirm that the SQL Server login (Windows or SQL Authentication) is enabled for the connecting user/computer.

Validate Webgility API Access
  • On the old  PC, try accessing the Webgility API if your setup uses it:
    • Navigate to the Webgility folder under XML
    • Check apiconfig file and ensure it's reachable.

4. Verify SQL Server Authentication Settings

Mixed Mode Authentication

  • Open SQL Server Management Studio (SSMS) on the main server.
  • Make sure SQL Server Authentication (Mixed Mode) is enabled:
    • Right-click on the server → Properties → Security → Select SQL Server and Windows Authentication mode.
  • Create or confirm that a SQL login exists for Webgility and has the correct roles/permissions.

SQL Server Instance Name

  • If you're using a named instance (like SERVERNAME\SQLEXPRESS), confirm it’s correct. If the new PC can’t discover the instance, use the server’s IP address in this format:

CopyEdit
192.168.1.100\INSTANCE_NAME

  • Replace any unreliable DNS-based names with the IP format in the Webgility connection screen during setup.
  • Test SQL Connection with SSMS
  • Open SQL Server Management Studio on the new PC.
  • Try connecting to the database using the same credentials and instance name or IP you used in Webgility.
  • If you receive login errors, check:
    • User mapping in SQL
    • Case sensitivity in credentials
    • SQL Server services running

Resolution Confirmation

  • After replacing the SQL instance name with the server's IP address, retry the Webgility connection.
  • If successful, proceed with completing the installation.
  • Webgility Desktop should now be fully functional on the second PC.