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

Restoring Webgility Desktop SQL Database Connection After Failed Upgrades or Misconfigurations

This article helps Webgility Desktop users identify and resolve database connection errors encountered when launching Webgility Desktop. Common causes include SQL service interruptions, failed upgrades, or misconfigured settings. The article provides guidance to troubleshoot these issues and restore a successful connection to the Webgility Desktop SQL database.

Overview

Webgility Desktop relies on a stable connection to its underlying SQL Server database. If this connection is broken or misconfigured, the application may fail to launch or initialize data properly. Common causes include:

  • Interrupted SQL Server or network services

  • Incomplete or failed database upgrades

  • Improper SQL Server instance or authentication configuration

This step-by-step guide walks you through verifying SQL services, reconnecting to the correct SQL Server instance, and using proper authentication to restore access.

Step-by-Step Resolution

1. Verify SQL Services Are Running

a. Open Windows Services

  • Press the Windows key and type Services

  • Open the Services application from the results

b. Restart SQL Services

  • Locate the SQL Server instance used by Webgility (e.g., SQL Server (UNIFY) or your custom instance)

  • Right-click on it and choose Restart

  • Also restart the SQL Server Browser service

Tip: The default instance used by Webgility is often named UNIFY or WEBGILITY

2. Reconnect from Within Webgility Desktop

a. Launch Webgility Desktop

  • After restarting services, open the Webgility Desktop application

b. Choose Existing SQL Server

  • When prompted, select Connect to an existing SQL Server

  • From the Locate SQL Server dropdown, choose your instance
    Format: ComputerName\InstanceName (e.g., DESKTOP123\UNIFY)

c. Use SQL Authentication

  • Select Use SQL Server Authentication

  • Enter the following credentials:

    • Username: sa

    • Password: Webgility2011 (case-sensitive)

  • Click Connect

3. If SQL Server Is Hosted on Another Machine

  • Click Browse more in the SQL Server dropdown

  • Wait a few moments for all available SQL Server instances to load

  • Select the correct one from the list

Note: Make sure both machines (your client and the server) are on the same network and the firewall allows SQL connections.