Troubleshooting Webgility Desktop Startup and SQL Authentication Errors in Hosted Environments
This article helps Webgility Desktop users troubleshoot persistent errors encountered when relaunching the app in a hosted environment. It covers issues related to SQL authentication failures and unsuccessful application startups, and provides steps to resolve these problems beyond standard reinstallations and database resets.
Issue Overview
Receiving persistent errors when relaunching the Webgility Desktop app within a hosted environment. Errors included failures related to SQL authentication and unsuccessful application startups, even after standard reinstallations and database resets.
Common Root Causes
- Misconfigured SQL credentials
- Corrupt or incomplete install of the Webgility Desktop app
- Hosting environment instability affecting app access
Step-by-Step Troubleshooting Procedure
1. Confirm Error Details
- Review error messages for SQL authentication failures, app crashes, or timeouts.
- Identify the exact stage at which the app fails (startup, database connection, etc.).
2. Validate SQL Credentials
- Confirm the SQL authentication credentials.
3. Reinstall or Repair Webgility Desktop
- Do a clean uninstall of Webgility Desktop after taking a database backup.
- Delete any leftover configuration data or cache.
- Download and install the latest version of the app from the portal.
4. Assess Hosted Environment Status
- Engage the hosting provider to verify the server/environment health.
- Request an environment reset or reboot if abnormal behavior is detected.
- Confirm that necessary ports and permissions are correctly set for SQL access.
5. Test Application Startup
- Launch Webgility Desktop and attempt SQL authentication again.
- Validate that no errors are encountered at startup or during database connection.