How to Fix Amazon Order Download Failures in Webgility Desktop Due to SQL Server Version
This article helps Webgility Desktop users resolve issues with Amazon orders failing to download in Webgility Desktop, which may be caused by an outdated SQL Server version. It guides users through checking their current SQL version, upgrading to SQL Server 2022 if necessary, and reconnecting the Webgility database to restore proper order download functionality.
Step 1: Check Your SQL Server Version
-
Open SQL Server Management Studio on the Webgility server.
-
Connect to your Webgility database instance.
-
Note the SQL Server version. If it’s earlier than SQL Server 2019, an upgrade is recommended.
💾 Step 2: Back Up the Webgility Database
Before making changes, create a full backup:
-
In SQL Server Management Studio:
-
Right-click your Webgility database
-
Go to Tasks > Back Up…
-
Choose a backup destination and start the process
-
-
Save the backup file securely—you’ll need this if restoring on a new SQL version.
⬆️ Step 3: Install SQL Server 2022
-
Download the SQL Server 2022 installer from Microsoft’s official site.
-
Run the installer:
-
Choose Upgrade existing instance (if allowed), or
-
Install a new instance if preferred for stability
-
-
Follow the prompts and complete the installation.
Tip: If installing a new instance, document the new server name and authentication mode (SQL or Windows).
📦 Step 4: Restore Your Webgility Database to the New SQL Instance
If you used a new instance:
-
In SQL Server Management Studio:
-
Right-click Databases > Restore Database…
-
Choose Device, then select your saved backup file
-
Adjust file paths if needed and start the restore
-
-
Confirm the restored database appears in the list
🧪 Step 5: Verify the Fix
-
Open Webgility Desktop.
-
Manually trigger an Amazon order download from:
-
Orders > Get New orders
-
-
If everything is set up correctly, orders should download without SQL or Scheduler errors.