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

Troubleshooting 'SQL Server is Unavailable' Error in Webgility Desktop

This article helps Webgility Desktop users troubleshoot and resolve the "SQL server is unavailable" error in Webgility Desktop. It provides step-by-step guidance to restore the connection between Webgility Desktop and the SQL Server database, ensuring database connectivity and uninterrupted operations.

Error Summary

  • Error Message: SQL server is unavailable

  • Context: Attempting to connect Webgility Desktop to the SQL Server

  • Impact: Application downtime until the issue is resolved

Troubleshooting Steps

1. Restart Host Computer and SQL Services

  • Restart the host computer where SQL Server is installed.

  • Open Services.msc and restart the following services:

    • SQL Server (Database Name)

    • SQL Server Browser

2. Verify Network Connectivity

  • Ensure the SQL Server is reachable:

    • Ping the SQL server’s IP address or hostname from the affected machine.

  • Check SQL Server Configuration Manager:

    • Confirm TCP/IP is enabled.

    • Verify SQL is listening on the correct port (default: 1433).

  • Ensure firewalls are not blocking SQL traffic (allow port 1433).

3. Enable Named Pipes and TCP/IP Protocols

  • Open SQL Server Configuration Manager.

  • Go to: SQL Server Network Configuration > Protocols for MSSQLSERVER.

  • Enable both:

    • TCP/IP

    • Named Pipes

  • Restart SQL Server service after making changes.

4. Install SQL Server 2022 Express (if needed)

  • If the issue is due to a corrupted or missing SQL instance:

    • Download SQL Server 2022 Express Edition from Microsoft.

    • Run the installer using default settings.

    • Confirm successful installation.

5. Restore Database Backup

  • Open SQL Server Management Studio (SSMS).

  • Connect to the newly installed or repaired SQL instance.

  • Restore the Webgility database:

    • Right-click Databases > Restore Database...

    • Select the latest .bak file from your backup directory.

  • Verify that the database restores successfully and is accessible from Webgility Desktop.

Post-Resolution Confirmation

  • Validate that Webgility Desktop is now connected to the SQL Server.

  • Test database access and application functionality.

  • Ensure no further error messages appear during operation.

Best Practices & Recommendations

  • Maintain regular Webgility database backups.

  • Document SQL instance names, ports, and configuration settings.

  • Monitor SQL Server services and network availability regularly to prevent future disruptions.