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

How to Complete Post-Restore Setup for Webgility Desktop After Database Migration

This article helps Webgility Desktop users complete essential post-restore steps after migrating a Webgility Desktop database backup to a new server. It ensures the system remains accessible, fully functional, and properly connected to sales channels and QuickBooks Desktop following the migration.

Steps to Follow After Restoring Database on New Server

1. Verify Database Restoration

  • Confirm that the correct backup file was restored (check file name, timestamp, and version).

2. Review and Configure Firewall Settings

  • Ensure that firewall exceptions are enabled for the SQL Server port (default: 1433).

  • Test SQL connectivity from client machines using the command:
    telnet [new-server-ip] 1433

  • Confirm SQL Server is listening on the appropriate network interfaces.

  • Document any added or modified firewall rules for future reference.

3. Switch SQL Server Service Accounts (If Applicable)

  • Verify that SQL Server is running under the correct service account:

    • Local System, Network Service, or a defined domain account.

  • If you switch service accounts (e.g., from Local System to Network Service):

    • Ensure proper folder-level permissions are assigned for DB files and backups.

    • Reapply login credentials or mappings that may have been lost during migration.

4. Update Application and Connection Strings

  • Update the connection settings in Webgility Desktop to point to the new SQL Server hostname or IP address.

  • Test the Webgility application to ensure it connects successfully.

  • Perform basic functions like downloading data from your sales channel and posting to QuickBooks.

  • Check for any login failures or timeout issues in the SQL Server logs.


5. Troubleshooting Tips

If you face connectivity issues:

  • Ensure TCP/IP is enabled in SQL Server Configuration Manager.

  • Double-check Windows Firewall or any network ACLs.

  • Recreate or remap missing SQL Server logins, if needed.

  • Review SQL Server logs and Webgility logs for detailed error information.

Summary

After restoring the database to a new server for Webgility Desktop, it’s critical to perform the above checks to ensure successful migration and continued system performance. These proactive steps help minimize downtime and avoid potential issues with sales channel syncing or QuickBooks connectivity.