Resolving Login Errors in Webgility Desktop Due to System Version Mismatch
This article helps Webgility Desktop users resolve login errors caused by version mismatches between systems connected to SQL Server. The issue typically occurs when the main system is updated but an Add-on system is still running an older version. The guide explains how to ensure all systems are on the same version.
Overview
A login error can occur in Webgility Desktop when different systems connected to SQL Server are running different versions of the software. This often happens when the main computer has been updated, but an Add-on system is still using an older version. To resolve this, all systems must be using the same Webgility Desktop version.
Identifying Version Mismatch Issues
Login issues may appear if the main and Add-on systems are running different versions of Webgility Desktop.
Common symptoms include:
-
Authentication errors
-
Failure to connect to SQL Server
Resolution Steps
1. Confirm the Error
Try to log in again and note the error message. If it suggests a version mismatch, continue with the following steps.
2. Check Webgility Desktop Versions on All Systems
On both the main computer and the Add-on system:
-
Open Webgility Desktop
-
Go to Help > About
-
Note the version numbers shown
3. Update Versions to Match
If the version numbers are different:
-
Download the latest version of Webgility Desktop from Portal.webgility.com.
-
On all Add-on systems, run the installer to update Webgility Desktop to match the main system’s version.
4. Verify SQL Server Connection
On the Add-on system:
-
Open Webgility Desktop and try logging in again.
-
The connection to SQL Server should now work without error.
-
If the error continues, restart both the main and Add-on systems, then try again.
Additional Notes
-
Always keep both the main and Add-on systems updated to the same version of Webgility Desktop.
-
Keeping your software versions aligned will help prevent login and connection issues in the future.
Reference Links : click here