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

How to Troubleshoot SQL Database Issues with Webgility Desktop

This article helps Webgility Desktop users troubleshoot issues where the application cannot locate the SQL database, particularly after restoring a previous instance. It outlines steps to verify database paths, service status, and connection settings to restore functionality.

This guide provides troubleshooting steps for situations where Webgility cannot locate the SQL database, especially after attempting to restore a previous instance.

Steps for Troubleshooting

1. Confirm SQL Instance and Service Status

  • Ensure SQL Server Express 2022 is properly installed and running on the correct server.

  • Open SQL Server Configuration Manager to check instance status.

  • Open SQL Server Management Studio (SSMS) and confirm that the Webgility database instance (WEBGILITY) is listed and accessible.

  • In Services (services.msc), verify the following are Running:

    • SQL Server (WEBGILITY)

    • SQL Server Browser

2. Verify Network Connectivity

  • Ensure the machine running Webgility can reach the server hosting SQL.

  • Check firewalls, VPNs, or network configurations that might block communication.

3. Restore the Database via SQL Server Management Studio

  • Confirm the .BAK backup file is:

    • Present on the system

    • Valid and not corrupt

  • Open SSMS and try restoring the database manually:

    • Right-click Databases > Restore Database

    • Choose the backup file and follow the prompts to restore

4. Reauthorize Webgility Store Connections

  • Open Webgility Desktop

  • Go to Connections > Sales channel> manage sales channels> edit connection

  • Follow the reauthorization steps for the store or channel