[QODBC Desktop] Resolving Error 80040154 - "Create QuickBooks COM Instance" / Begin Session Failed

Problem Description:

QODBC users may encounter Error 80040154 when trying to connect to QuickBooks data via QODBC. The error message states: "Create QuickBooks COM Instance Error on Machine <hostname>, Errorcode = 80040154, Class not registered." This indicates that the Windows COM registration for QuickBooks is missing or invalid on the machine running QODBC.

Affected products: QODBC Desktop (all versions), QRemote Server/Client, QuickBooks Desktop (Enterprise, Pro, Premier)
Expected outcome: QuickBooks COM registration is restored and QODBC can successfully connect to the open company file.

Symptoms:

• "QuickBooks Open Connection Failed. Create QuickBooks COM Instance Error on Machine <hostname> Errorcode = 80040154, Class not registered"
• QODBC Test Tool fails to connect with a "Class not registered" or "Class not found" error.
• Errors only start appearing after installing/upgrading QuickBooks, another version of Office, or running a system cleanup tool that may have undone COM registrations.
• QuickBooks opens fine normally - the issue is specifically QODBC's ability to communicate with it via COM.

Cause:

1. QuickBooks COM registration was undone. Installing a previous version of QuickBooks, reinstalling Office, or running certain system cleanup tools can unregister the QuickBooks COM components that QODBC depends on to communicate with the QuickBooks application.
2. QRemote is launching in admin mode. If QRemote runs with elevated (Administrator) privileges while the calling application runs as a standard user, the two cannot communicate via COM - resulting in Error 80040154 or related connection failures.
3. QuickBooks is not installed on the same machine as QODBC. The QuickBooks COM object must be present on the machine where QODBC is installed. Remote-only access requires QRemote architecture (not direct DSN connections).

Environment:

Solution:

1. Ensure QRemote is NOT running in admin mode. This is a common cause. Right-click the QRemote tray icon → "Exit." Then launch QuickBooks normally (not as Administrator), followed by launching QODBC from a standard user session. Verify in Task Manager that QRemote.exe is running without elevated privileges.
2. Verify QuickBooks is installed and updated on the same machine. QODBC requires QuickBooks to be installed locally. The machine must have the matching or newer version of QuickBooks (e.g., QODBC for QuickBooks 2024 requires QB Desktop 2024+). Update QuickBooks to the latest release via Help → Update QuickBooks.
3. Restart the machine. After confirming QuickBooks is installed and updated, restart to allow COM registrations to take effect.
4. Re-register QuickBooks COM components (if the error persists). Open an elevated Command Prompt and run:

   regsvr32.exe "C:\Program Files (x86)\Common Files\Intuit\QuickBooks\QuickBooks.exe"

   If this does not work, reinstall the latest version of QuickBooks - it will re-register all COM components automatically.
5. Test the connection. Open the QODBC Support Wizard (http://qodbc.com/links/2981) or the QODBC Test Tool and try to connect. The connection should now succeed without Error 80040154.

Additional Notes:

• QODBC 64-Bit requires QuickBooks 2022 or above. For QuickBooks 2021 and older, you must use the QRemote 64-Bit driver or DSN instead of the native 64-Bit QODBC driver.
• QuickBooks must be open before querying. QODBC connects to whatever company file is currently open in QuickBooks. If QuickBooks is not running, the COM object will not be available.
• Avoid running QRemote and applications as different privilege levels. Both QRemote and any consuming application (Excel, Access, custom scripts) must run under the same user context - either both as Administrator or both as standard users. Mixing privilege levels causes COM communication to fail.

Related Articles:

QODBC QRemote Multi-Company File Setup

Keywords: