-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To the best of my knowledge (and COM is my friend, so I think this is
accurate....), you can't possibly have a .exe component run inproc.
Under Windoze, ALL EXEs run as their own process and ALL DLLs run in
somebody else's process. As far as I know, there are NO exceptions
to that.
This probably sounds pretty, lame but... Try renaming the thing to a
.DLL, then re-run regsvr32 on it.
It sounds like you have an inproc COM trapped in an EXE. I wonder if
someone else renamed it originally. Check out the OriginalFilename
property of the EXE. It might even say it's supposed to be a DLL.
As for why it's working in ASP & not CF.... Microsoft does their
homework, Allaire (usually) doesn't.... I'd imagine that ASP is
seeing the COM for what it really is & handling it appropriately,
whereas CF doesn't know how to do that.
I'd also change your CFOBJECT call to:
<CFOBJECT CLASS="fmswebx.fmswebx" ACTION="create" NAME="repx">
(Since CF should get the context from the registry, and there IS no
server for an inproc component).
I know renaming it's a long shot, but....
Good luck!
Zac Bedell
> Hi There,
>
> I'm currently having trouble interfacing with a COM object on
> CF4.0.1/NT4
> SP6/IIS4. This is a third party component - written to work
> with an existing
> product written in ASP (bah!). I am trying to integrate this
> component with
> a new CF app.
>
> My code:
> -----
> <CFOBJECT CLASS="fmswebx.fmswebx" ACTION="create" SERVER="monster"
> NAME="repx" CONTEXT="INPROC">
> -----
>
> Error message:
> -----
> COM error 0x80040154. Class not registered
> -----
>
> ASP code that works:
> ----
> Set repx = CreateObject("fmswebx.fmswebx")
> ----
>
> The context used is INPROC - even though it is an .exe it is
> does not run as
> a background process. And the component does not support the
> 'connect' interface - so even if the component is running (created
> via
> .asp) as an NT
> process, you can't access it through CF.
>
> What I can do - create an instance with .asp and call methods etc.
>
> What I can't do - I can't even create it with CF.
>
> This is a .exe COM automation object which supports the
> IDispatch interface.
>
> It's depoyed with it's own registry program and works fine
> with ASP. I have
> registered the object with the account the CF service uses (as well
> as reverting back to using the system account for the CF
> service) and have also
> registered the component with NT's task scheduler - as
> advised in Allaire's
> support forums.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
Comment: Please use PGP!!!
iQA/AwUBOW3RfgraVoMWBwRBEQKzmQCfWMMgZpkKrU1+SsGZl3q+U6dWBiwAn2f0
ktQaX8l06QXzjgEGKHiRxWoH
=cvus
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
