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

How to Fix SQL Authentication Failures When Connecting Webgility Desktop on an Add-On Machine

This article helps Webgility Desktop users resolve SQL authentication failures when connecting Webgility Desktop on an add-on machine. It provides step-by-step instructions to verify authentication settings, configure necessary permissions, and securely connect using SQL credentials. This guide is specifically intended for environments requiring SQL Server authentication for multi-machine access to the Webgility Desktop database.

Causes of SQL Authentication Issues

  • SQL Server is not configured to allow SQL authentication

  • Required login for the add-on machine does not exist

  • Incorrect username or password used

  • Firewall or antivirus interference

  • TCP/IP or Named Pipes not enabled in SQL Server

  • Incorrect SQL instance selected

Step-by-Step Instructions

1. Enable SQL Server Authentication

This can be found in SQL Server Management Studio (SSMS) on the primary server:

  • Log in with Windows Authentication

  • Right-click on the server name > Properties

  • Go to Security

  • Select SQL Server and Windows Authentication mode

  • Click OK, then restart SQL Server from the Services app (services.msc)

2. Create SQL Login for Add-On Machine

  • In SSMS, expand Security > Logins

  • Right-click Logins > New Login

  • Choose SQL Server authentication

  • Enter a username and secure password

  • Uncheck Enforce password policy (optional)

  • Under User Mapping, select your Webgility database and assign roles:

    • db_datareader

    • db_datawriter

  • Click OK to save

3. Enable TCP/IP and Named Pipes

  • Open SQL Server Configuration Manager

  • Navigate to SQL Server Network Configuration > Protocols for UNIFY

  • Enable both TCP/IP and Named Pipes

  • Restart SQL Server again in the Services app

4. Allow SQL Communication Through Firewall

  • Navigate to C:\Webgility\UnifyEnterprise

  • Right-click wgFirewall.exe > Run as Administrator to auto-configure firewall rules

5. Add Webgility to Antivirus Exclusion List

  • Open your antivirus software

  • Add the folder C:\Webgility to the Exclusion List

  • Restart Webgility afterward

6. Connect Using SQL Authentication on Add-On Machine

  • Open Webgility Desktop

  • On the Database Configuration screen:

    • Select SQL Server Authentication

    • Enter the username and password created earlier

    • If the instance is not listed, click Browse and select the correct one (e.g., ComputerName\UNIFY)

  • Click Test Connection and then Connect

Notes

  • The default SQL login for Webgility is:

    • Username: sa

    • Password: Webgility2011 (W is capital)

  • If your QuickBooks is hosted with a provider (Rightworks, Summit Hosting, etc.), their support may need to configure SQL access

  • SQL Authentication is required for connecting add-on machines—Windows Authentication may not work across networks