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

How to Fix the "Unable to Find Database" Error When Installing Webgility Desktop

This article helps Webgility Desktop users resolve the "Unable to find database" error encountered when installing Webgility Desktop on a new computer. The issue typically occurs due to a missing, outdated, or misconfigured APIConfig.xml file. The article provides steps to analyze and update the APIConfig file to fix the error.

Overview

When installing Webgility on a new computer, users may encounter an 'Unable to find database' error. This issue typically occurs when the APIConfig.xml file is missing, outdated, or incorrectly configured. This article outlines the steps Webgility Desktop users should follow to resolve this error by analyzing and updating the APIConfig file.

Root Cause

Webgility relies on the APIConfig.xml file to establish a connection with the company database. If this file is missing or contains incorrect values, the application cannot locate the target database resulting in a connection failure.

Step-by-Step Resolution

1. Gather Information

  • Check if any previous configuration files (e.g., from the old computer) are available.

2. Locate the APIConfig.xml File

  • Browse to the Webgility program directory on the old computer (usually C:\Webgility\UnifyEnterprises\XML or a similar path).
  • Identify and copy the APIConfig.xml file.

3. Transfer the Config File

  • Send the APIConfig.xml file to the new computer via secure method (e.g., company-approved email, USB stick).
  • Place the file in the corresponding Webgility program directory on the new computer.
    • Example path: C:\Webgility\UnifyEnterprises\XML.

4. Validate File Settings

  • Open APIConfig.xml in a text editor (such as Notepad).
  • Cross-check key database connection values:
    • Database server address
    • Database name
    • Authentication credentials
  • Update values if the server or connection has changed during migration.

5. Relaunch Webgility

  • Close and relaunch Webgility.
  • Confirm that the error no longer appears, and verify database connectivity (e.g., access to company data within the application).

6. Final Confirmation

  • Perform typical operations (e.g., importing/exporting data) to validate Webgility Desktop is fully functional.