CFObject in CF 2018 for calling a COM object

September 10, 2019
Newbie 1 posts
Followers: 0 people
5

CFObject in CF 2018 for calling a COM object

Newbie 1 posts
Followers: 0 people
September 10, 2019

When calling the activePDF toolkit dll using this:

<CFOBJECT ACTION=”Create” TYPE=”COM” CLASS=APToolkit.Object NAME=”TK”> I get this error:

An exception occurred when instantiating a COM object.
The cause of this exception was that: AutomationException: 0x80040154 – Class not registered.

I did register the .dll  Also this is on Windows server 2016

This doesn’t happen in CF11 but does in CF 2018.  Any help would be greatly appreciated.

Comments (5)
2019-09-12 21:38:34
2019-09-12 21:38:34

After getting support from activePDF, we found that CF, when trying to load a COM object is looking at a path that doesn’t exist: D:\ColdFusion2018\cfusion\wwwroot\WEB-INF\exception\coldfusion\runtime\com and also this key: HKCR\WOW6432Node\CLSID\{F74F7C81-E3B7-4974-95C6-E487390CCE48} which is not one of their CLSIDs.   How can I get help from Adobe on this?

Like
2019-09-10 23:15:58
2019-09-10 23:15:58

Is the “cf11 where this problem doesn’t happen” running on this same box? If not, then if you don’t find an explanation/solution for CF2018, you may want to install CF11 just to see if the problem DOES now happen in CF11 on this box. In that case, the problem is either in how you registered the DLL or some other aspect of configuration of the box, and not (it would seem) CF.

Like
(1)
>
Charlie Arehart
's comment
2019-09-11 04:03:59
2019-09-11 04:03:59
>
Charlie Arehart
's comment

I just downloaded and installed the newest edition of activePDF Toolkit on 2 servers which are identical, new, and running windows 2016.  One with CF18 and the other with CF11.  I didn’t bother registering any dlls – that should be the installer’s job.  I tried the same code on both and the CF18 server failed and gave the same error message as in my 1st post and the CF11 server worked perfectly.    In my first post I was referring to another very old server (win 2008 r2) that runs CF11 and never had an issue with Toolkit.  Now I’m at a loss.  I hate the thought of sticking with CF11 on a brand new server that I’m hoping lasts another 5 years.  Any suggestions?

Like
2019-09-10 23:01:12
2019-09-10 23:01:12

The program has a 32-bit and a 64-bit version and both are registered.  I’m not sure how the code knows which one to call.  CF should be 64 bit, just downloaded it on to a brand new server

Like
2019-09-10 22:40:24
2019-09-10 22:40:24

Is the DLL a 32-bit DLL? Are you using a 32-bit version of CF running in a 32-bit application pool? I think they both have to be the same “bit-ness”.

Dave Watts, Eidolon LLC

Like
Add your comment