How to Fix COM Class Factory Errors When Connecting Webgility Desktop to QuickBooks Desktop
This article helps Webgility Desktop users resolve the “COM Class Factory” error that can occur when integrating Webgility Desktop with QuickBooks Desktop. This error typically indicates a communication issue between the two applications, often caused by missing or misregistered COM components or permission-related problems particularly in multi-user or server environments. The guide provides step-by-step instructions to fix the error, whether on a primary workstation or an add-on system.
Overview
You may see an error message similar to:
Error: Retrieving the COM class factory for component with CLSID…
This prevents Webgility Desktop from connecting to or posting data into QuickBooks Desktop.
Common Causes
-
Missing or incorrectly registered QuickBooks COM components
-
Webgility dependency not installed properly
-
Running QuickBooks or Webgility Desktop without admin permissions
-
Network or user permission issues on secondary/add-on systems
Step-by-Step Resolution
Step 1: Close Webgility Desktop and Scheduler on All Systems
To avoid conflicts:
-
Exit Webgility Desktop and Webgility Scheduler on all systems where they’re running
-
You can refer to the guide: How to Start or Stop the Scheduler if needed
Step 2: Run the Webgility Desktop Merge Module
a. Navigate to Installation Directory:
Go to:C:\Webgility\UnifyEnterprise
b. Locate and Run the File:
-
Find WebgilityMergeModule.exe
-
Right-click and choose Run as administrator
This will re-register the required COM components necessary for QuickBooks Desktop integration.
If you're on an add-on system (not the main server), restart the computer after this step.
Step 3: Re-Test Integration with Correct Permissions
a. Launch Both Applications as Administrator:
-
Right-click and Run as administrator on both QuickBooks Desktop and Webgility Desktop
b. Test the Integration:
-
In Webgility, go to QuickBooks Desktop Integration Settings
-
Attempt the action that previously triggered the error.
If the error no longer appears, your integration is now restored.