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

How to Fix the “SQL Server is Unavailable” Error in Webgility Desktop

This article helps Webgility Desktop users troubleshoot and resolve the "SQL server is unavailable" error, which occurs when the application cannot connect to its underlying SQL Server database. It provides step-by-step instructions to restore the database connection and resume normal operations, preventing downtime caused by this issue.

If you're seeing an "SQL server is unavailable" error when trying to connect Webgility Desktop, it means the application cannot communicate with its database. This can prevent Webgility Desktop from functioning. This article provides step-by-step guidance to help you restore the connection and get back to uninterrupted operations.

  • What it means: Webgility Desktop is unable to connect to its underlying SQL Server database.
  • Impact: You won't be able to use Webgility Desktop until this issue is resolved.

Troubleshooting Steps

Follow these steps in order to diagnose and resolve the connection problem:

1. Restart Your Computer and SQL Services

Sometimes, a simple restart can resolve temporary connection glitches.

  • Restart the host computer where your SQL Server is installed. This is often the computer where Webgility Desktop's main database resides.
  • Once the computer has restarted, open Services.msc (you can search for "Services" in your Windows search bar) and restart the following services:
    • SQL Server (Your_Database_Name) (The name in parentheses will correspond to your Webgility Desktop database instance, often MSSQLSERVER or UNIFYENTERPRISE).
    • SQL Server Browser

2. Verify Network Connectivity

Ensure that your Webgility Desktop computer can reach the SQL Server.

  • Ping the SQL server:
    • Open Command Prompt (search for cmd in Windows).
    • Type ping [SQL server’s IP address or hostname] (e.g., ping 192.168.1.100 or ping MyServerPC).
    • Press Enter. You should see replies, indicating a successful connection. If you see "Request timed out," there's a network issue.
  • Check SQL Server Configuration Manager:
    • Search for "SQL Server Configuration Manager" in your Windows search bar and open it.
    • Navigate to SQL Server Network Configuration > Protocols for Your_SQL_Instance_Name (e.g., Protocols for MSSQLSERVER).
    • Confirm that TCP/IP is Enabled.
    • Under TCP/IP Properties, go to the IP Addresses tab and ensure SQL Server is listening on the correct port (the default is 1433).
    • Firewall Check: Make sure your Windows Firewall (or any third-party firewall) is not blocking SQL traffic. You may need to create an inbound rule to allow traffic on port 1433.

3. Enable Named Pipes and TCP/IP Protocols

These protocols are essential for SQL Server communication.

  • Open SQL Server Configuration Manager.
  • Go to: SQL Server Network Configuration > Protocols for Your_SQL_Instance_Name (e.g., Protocols for MSSQLSERVER).
  • Ensure both:
    • TCP/IP
    • Named Pipes
    • are Enabled.
  • Restart the SQL Server service after making these changes (as done in Step 1).

4. Install SQL Server 2022 Express (If Needed)

If the issue persists and you suspect a corrupted or missing SQL instance, you might need to install SQL Server 2022 Express Edition.

  • Download SQL Server 2022 Express Edition from the Microsoft website.
  • Run the installer. During the installation, you can typically use the default settings.
  • Confirm that the installation is successful.

5. Restore Database Backup

If you had to reinstall SQL Server, or if the database itself is corrupted, you will need to restore your Webgility Desktop database from a backup.

  • Open SQL Server Management Studio (SSMS). (If you don't have SSMS, you might need to install it separately from Microsoft's website).
  • Connect to your SQL Server instance (the one you just installed or repaired).
  • Restore your Webgility Desktop database:
    • Right-click on Databases in the left panel.
    • Select Restore Database...
    • Choose Device and navigate to select your latest Webgility Desktop .bak file from your backup directory.
    • Follow the prompts to complete the restoration.
  • Verify that the database restores successfully and that you can access it from Webgility Desktop.

Post-Resolution Confirmation

After attempting the troubleshooting steps:

  • Validate that Webgility Desktop is now connected to the SQL Server.
  • Test database access and application functionality (e.g., download orders, view products) to ensure everything is working correctly.
  • Confirm that no further error messages appear during operation.