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

How to Resolve SQL Server 2022 Express Restore and Error 26 Connection Issues

This article helps Webgility Desktop users troubleshoot and resolve SQL Server error 26 and database restoration issues when using Webgility Desktop. It provides step-by-step guidance for situations involving SQL Server 2022 Express installation, restoring Webgility Desktop database backups, and fixing connectivity problems that hinder application functionality.

Causes of Issue

  • SQL Server instance is not running or incorrectly installed

  • TCP/IP and Named Pipes protocols are disabled

  • Windows Firewall blocking SQL traffic

  • Misconfiguration of database instance or connection parameters

  • Backup file paths or permissions incorrect during restore

Steps to Resolve

1. Confirm SQL Server Services

  • Open SQL Server Configuration Manager.

  • Make sure SQL Server (SQLEXPRESS) and SQL Server Browser services are set to Running.

2. Enable Network Protocols

  • In SQL Server Network Configuration, enable both TCP/IP and Named Pipes.

  • After making these changes, restart the SQL Server (SQLEXPRESS) service.

3. Configure Windows Firewall

  • Open Windows Defender Firewall with Advanced Security.

  • Add new Inbound Rules & Outbound Rules to allow the following:

    • TCP Port 1433 (default SQL Server communication port)

    • UDP Port 1434 (used by SQL Server Browser)

4. Test SQL Server Connectivity Using SSMS

  • Launch SQL Server Management Studio (SSMS).

  • Attempt to connect using localhost\SQLEXPRESS or the full machine name with the instance.

  • If you still receive Error 26, verify that the machine is accessible on the network and the server name is correct.

5. Restore Webgility Database Backup

  • In SSMS, right-click Databases > Restore Database...

  • Choose Device and select the .bak backup file.

  • Ensure the Restore As file paths are valid and not in use.

  • Click OK to begin the restore.

  • Confirm completion in the Messages tab.

6. Reconnect Webgility Desktop to the Restored Database

  • Open Webgility Desktop.

  • Navigate to Connections > Database Connection.

  • Confirm the Server/Instance name and Authentication method are correctly configured.

  • Test the connection to ensure successful linking.

Post-Restoration Verification

  • Verify the database is accessible via SSMS and Webgility Desktop.

  • Run basic queries or test order syncing to validate functionality.

  • Check that your sales channel connections (Shopify, Amazon, etc.) operate normally post-restoration.

Note

For optimal performance and future protection:

  • Schedule regular database backups.

  • Monitor SQL Server logs for any recurring connectivity or performance issues.

  • Ensure network and firewall settings remain consistent across software updates.