5

I am getting this error:
Retrieving the COM class factory for component with CLSID {6C9E80E3-B780-4361-A693-5E5C6BDC83A9} failed due to the following error: 80040154.

Dim smgrGlobal As QBSessionManager
smgrGlobal = New QBSessionManagerClass()

The 2nd line is the one that errors.
I get this error only with QB2013 and QBFC12. This does not happen with any previous versions.
I as far as I can find, this error is due to an application not being compiled for x86 (if "Any CPU" was used instead.) However I have set my application to compile for x86 NOT "Any CPU" and I am still receiving this error.

Keith Palmer Jr.
  • 27,666
  • 16
  • 68
  • 105
Casey Barsness
  • 51
  • 1
  • 2
  • http://stackoverflow.com/a/2123678/62576 has an explanation you might want to follow up on (check to see if the COM class is actually registered). The other reason for this is building a 64-bit app that tries to use a 32-bit ActiveX (or 32-bit trying to load a 64-bit ActiveX). – Ken White Feb 22 '13 at 23:43

3 Answers3

6

COM error 0x80040154 literally means "class not registered". The "class" being referred to is the COM class for the component that you're trying to instantiate. Here are the reasons you might get this error:

  1. As you noted, if you build your app with "x64" or "Any CPU" instead of "x86" you will see this problem. That's because 32 bit processes use a different registry hive than 64 bit processes, and the registry is where information about COM class registration is kept.
  2. You have not properly installed QBFC on the current local machine. Whatever the version of QBFC you used to develop your application, you must install that same version of QBFC on every computer on which your application runs. If you don't, you may get lucky because someone else installed the correct version, but eventually you will see this problem. Let me emphasize: QBFC is not installed with QuickBooks by default.
  3. (less likely but possible) Somehow the COM registration information for QBFC has become corrupted. This problem can be solved by re-installing the correct version of QBFC.
Paul Keister
  • 12,851
  • 5
  • 46
  • 75
1

If changing to X86 doesn't work try this: I'm using Version 13, may work for other versions too Install QBFC13_0Installer.exe Make sure you install the SDK first On my system it's under: C:\Program Files(x86)\Intuit\IDN\QBSDK13.0\tools\installers

I have two identical Surface Pro 3s with Windows 10. Using an identical copy of the code on one system compiled and ran just fine. On the other I'd get the dreaded class error. After much searching and not finding a solution I started just taking stabs in the dark and this particular stab fixed the problem.

Phil
  • 13
  • 4
0

I have a similar problem with QB POS 2013.

I am getting this error when run application with admin credentials - when I am run application under current user all is ok. The reason of this error can be an issue in QBFC installer (or merge module) - both installers are write COM component class id in registry branch of current user (HKCU) instead on local machine branch (HKLM). So, when you run your app not under current user (admin or other user) application can not find COM component ID.

Also, regular QB XML (Interop.QBPOSXMLRPLIB) installed correctly and successfully run under all users.

Please see similar discussion here - How can A COM component be registered halfway?.

Community
  • 1
  • 1
Dmytro Kutetskyi
  • 701
  • 6
  • 11