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

How to Fix .NET Framework and Database Connection Issues for Webgility Desktop

This article helps Webgility Desktop users encountering login errors in Webgility Desktop caused by issues with the .NET Framework and SQL database connectivity. These errors often result from outdated Windows components or incompatible software versions. The guide provides troubleshooting steps and resolutions to help users update their system and restore successful login.

Overview

This article details the troubleshooting process and resolution steps for errors encountered when logging into Webgility, specifically those relating to .NET Framework and database connectivity. These errors commonly occur due to outdated Windows components and software versions.

Symptoms

  • Errors displayed upon logging into Webgility
  • Error messages referencing .NET Framework or database connection issues

 

Root Cause

These errors typically result from one or more of the following:

  • Outdated or missing Windows updates
  • Incompatible or outdated .NET Framework
  • Using an older version of the Webgility application

Resolution Steps

1. Check and Install Windows Updates

  • Open Settings > Update & Security > Windows Update.
  • Click Check for updates.
  • Install all pending critical and recommended updates.
  • Restart the system if prompted.

2. Verify or Update .NET Framework

  • Open Control Panel > Programs > Programs and Features.
  • Click Turn Windows features on or off.
  • Ensure the latest supported versions of .NET Framework are enabled (minimum: 4.7 or higher recommended).
  • If outdated, download the latest .NET Framework installer from the Microsoft website and run the installation.
  • Reboot the system as required.

 

3. Update Webgility Application

  • Launch Webgility and log in with administrative credentials.
  • Go to Help > Check for Updates.
  • Follow on-screen prompts to download and install the latest version (e.g., from v9.6 to v9.9.2).
  • If an in-app update fails, download the latest installer from the vendor portal and perform a manual upgrade.