How to Fix Webgility Desktop Launch Issues Caused by SQL Instance Errors

Overview

Before proceeding, make sure you have:

• Access to the affected machine

• Administrator privileges

• Access to both Webgility Desktop and its backend configuration files

Step-by-Step Troubleshooting

1. Verify SQL Server Configuration

• Open SQL Server Configuration Manager on the customer’s computer

• Under SQL Server Services, identify the SQL instance used by Webgility—this is usually named:

  • WEBGILITY

  • Or a custom instance name configured during installation

• Confirm that the SQL Server service status is Running

  • If it's stopped, right-click and select Start

2. Check Connection Credentials

• Locate the SQL credentials:

  • Look in the apiconfig file 

  • Or confirm the credentials provided by the customer

• Open SQL Server Management Studio (SSMS)

  • Try connecting to the SQL instance using the retrieved credentials

  • If the connection fails, reset the SQL user password and attempt the connection again

3. Connect Webgility Desktop to the SQL Instance

• Launch Webgility Desktop

• When prompted for SQL Server connection:

  • Enter the verified SQL instance name

  • Use the correct username and password

• If connection still fails:

  • Review the error message

4. Restore Previous Webgility Settings

Once connected:

• Check whether the company data, settings, and sales channels are intact

• If data is missing:

  • Go to C:\Webgility\Data\Backup

  • Use Webgility's Restore feature to reload company settings from a recent backup

5. Test the Application and Confirm Fix

• Ask the customer to perform common functions, such as:

  • Syncing orders

  • Updating inventory

• Ensure no further SQL or connection errors appear

• Document your resolution steps in the case log, including:

  • SQL instance name used

  • Changes to credentials or configuration