tracker issue : CF-4198557

select a category, or use search below
(searches all categories and all time range)

AutomationException: 0x80040154 - Class not registered.

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): Sébastien Delmotte / Sébastien Delmotte ()

Created: 04/25/2017

Components: COM/DCOM

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: 2016.0.03.301771 /

Priority/Frequency: Normal / All users will encounter

Locale/System: French / Win 2012 Server x64

Vote Count: 0

Problem Description: When CreateObject("COM","DebenuPDFLibrary64AX1312.PDFLibrary");
The DLL is good registred 64 bits and CF is 64 bits

Steps to Reproduce: Install Coldfusion, DLL for COM/OLE automation, register the DLL and test in a cfm with createobject.

Actual Result:An exception occurred when instantiating a COM object.The cause of this exception was that: AutomationException: 0x80040154 - Class not registered. The specific sequence of files included or processed is: E:\Central\gpaye\edit\prtmpper.cfm, line: 34

Expected Result: The oject create...

Any Workarounds:



S├ębastien, Is the DLL registered with the local machine (the host on which CF is running)? Can you confirm is the DLL was successfully registered with the OS. You can use the "DCOMCNFG" utility to verify if the DLL is registered. Can you share the code extract from the CFM page where you are trying to instantiate the COM component? Can you also try using the setDLLHost supplied with CF (at <cf_root>\cfusion\jintegra\bin) to register the DLL. Ref.
Comment by Piyush K.
898 | May 05, 2017 01:41:31 PM GMT
S├ębastien, Any updates on this. Did you try out what I suggested. If you are still facing that issue, can you pls., share the information I requested earlier.
Comment by Piyush K.
899 | August 07, 2017 08:00:44 AM GMT
closing this as the reporter has not reverted with further details. we can take this up if more information is available. from the error msg shared in the original report, looks like its resulting from incomplete step-up steps performed when registering the COM component.
Comment by Piyush K.
900 | August 10, 2017 01:31:00 PM GMT