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

Troubleshooting SSL SQL Error When Launching Webgility Desktop

This article guides Webgility Desktop users through troubleshooting the “SSL SQL error” that prevents the application from starting and accessing the respective integrated SQL database and services. It provides a step-by-step workflow to resolve this critical startup issue.

Overview

This article outlines the step-by-step troubleshooting workflow for resolving the 'SSL SQL error' encountered when launching Webgility Desktop. The issue typically blocks application startup and access to the integrated database and services.

Error Symptom

  • User attempts to launch Webgility Desktop.
  • Application fails with an 'SSL SQL error' message.

Prerequisites

  • Administrative access to the host machine and Webgility service.
  • Valid backup of the existing application database (if accessible).

Troubleshooting Steps

1. Verify Application Version

  • Confirm the Webgility Desktop version is current.
  • If outdated, perform a software update to apply the latest patches and compatibility fixes.

3. Restart Webgility Services

  • Open Windows Services.
  • Locate and restart the following services (if present):
    • SQL Server Unify 
    • SQL Server Browser
  • Ensure both services are running without errors.

4. Adjust API Configuration

  • Navigate to the Webgility installation directory and locate the API.config file under the XML folder.
  • Open API.config in a text editor with administrative privileges.
  • Identify the <Provider> node or key related to SQL connectivity.
  • Try changing the Provider to SQLOLEDB or MSOLEDBSQL 
  • Save changes and close the file.

5. Relaunch Application

  • Re-attempt to start Webgility Desktop.
  • Verify that the SSL SQL error no longer appears.

6. Validate Integration and Backup

  • On successful launch, perform the following checks:
    • Database Backup: Initiate a database backup from application settings; ensure backup completes without errors.
    • Integration Check: Validate connections to accounting backend (e.g., QuickBooks) and Shopify to ensure no further authentication or data-sync errors occur.

Additional Considerations

  • Ensure the SQL Server instance supports the encryption level configured in API.config.
  • If using a custom SQL certificate, verify trust relationships and certificate validity.

Reference links : Webgility Desktop Update