How to Resolve ‘COM Class Factory’ Errors During QuickBooks Integration in Webgility
This article helps Webgility Desktop users in addressing the ‘COM Class Factory’ error that may occur when integrating Webgility Desktop with QuickBooks Desktop. The error usually indicates unstable communication between the applications or missing/misregistered COM components. It includes step-by-step instructions applicable to both main systems and add-on computers in a server setup.
You may encounter a ‘COM Class Factory’ error when attempting to integrate Webgility with QuickBooks Desktop. This error typically indicates unstable communication between both applications or missing/incorrectly registered COM components necessary for integration.
This article provides clear, step-by-step instructions to resolve this issue, whether you’re working on the main system or an add-on computer in a server setup.
The error message usually appears as:
Error: Retrieving the COM class factory for component with CLSID...
Reason:
An unstable or failed connection between Webgility and QuickBooks, often due to:
-
Missing or improperly registered QuickBooks COM components
-
Webgility dependency issues
-
Incorrect application permissions
-
Network or user account issues on add-on computers
Step-by-Step Resolution
Step 1: Close Webgility and Scheduler on All Systems
-
Exit the Webgility Desktop application and Webgility Scheduler on all computers where it is running.
-
You may refer to the article: How to Start or Stop the Scheduler for help.
Step 2: Locate and Run the Webgility Merge Module
-
Navigate to the installation folder:
C:\Webgility\UnifyEnterprise
-
Locate:
WebgilityMergeModule.exe
-
Run the installer:
-
Right-click and choose Run as administrator
-
This step registers required COM components for QuickBooks integration
-
-
Important: If on an add-on computer, restart the computer after installation.
Step 3: Confirm Permissions and Account Settings and Test the Integration
-
Launch QuickBooks and Webgility (Run as administrator)
-
Go to the QuickBooks Integration section in Webgility
-
Try the action that previously caused the error (e.g., verifying QuickBooks connection)
If the error is resolved, your integration is now operational.
📘 Note: You can refer to the article How to Test QuickBooks Connection in Webgility Desktop for further diagnosis.
Summary
Running the Webgility Merge Module with administrative permissions typically resolves the ‘COM Class Factory’ error. Make sure all systems have proper application permissions, and always restart the system after installing components.