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

Webgility has stopped working, The type initializer for 'wd.ecc.Data.Factory.ConnectionFactory' threw an exception

This article helps Webgility Desktop users resolve the ‘The type initializer for 'wd.ecc.Data.Factory.ConnectionFactory' threw an exception’ error in Webgility Desktop. It explains how a missing or corrupted apiConfig.xml file can cause this issue and provides step-by-step instructions to verify and restore the file, allowing Webgility Desktop to launch again and continue with processing orders.

Overview

This error message typically occurs when the API config file is missing from the Webgility Desktop installation directory. This article will guide you through the steps to identify and resolve this issue.

 

 

Steps to Resolve the Issue

Verify the Presence of the API Config File

  • Navigate to the following directory on your computer:
    C:\Webgility\UnifyEnterprise\XML

  • Check if the file named apiConfig.xml exists in this folder.
    ​


If Webgility Is Running on Another Computer

  • If Webgility is functioning correctly on an add-on computer in your network, you can copy the apiConfig.xml file from that machine.

  • Paste the file into the directory mentioned above on the computer where the error occurred.

Download the Missing API Config File

  • If the file is missing and you cannot retrieve it from another computer, then reinstall the Webgility Desktop for restoring the default version of the Apiconfig file. Kindly refer to the article: Installation Guide for Webgility Desktop
  • Once done then try to login again and it should now ask you to connect to an existing database instance. So select your Webgility Desktop database instance and then use the SQL Authentication Mode with the username "sa" and password "Webgility2011" , both the credentials are case sensitive. And you should be able to login back into your Webgility Desktop. Refer: SQL Connection Disconnected 

Customization Nodes (If Applicable)

  • If you were using any paid customizations, the necessary nodes may need to be updated after replacing the API config file.

 

By following these steps, you should be able to resolve the error and get Webgility back to working condition.