ActiveX component can't create object

[Steven King]

Here's one for you (or anybody!).

A component is installed on two different machines exactly the same (the
registry entries on both machines are the same) but when a "New" or "CreateObject"
call is called from an app on one machine the dreaded error "ActiveX component
can't create object" occurs and on the other machine this call works fine!
In a group of about 15 clients with this software, only 1 is having this
problem.

We've exported each's registry to a text file then parsed out the lines relevant
then compared the two - they are exactly the same!

Using Word's VB editor, the component shows up in the references list AND
Intellisense can see its methods (it's typelib is registered OK). Unless
we get an answer we'll have to rebuild the client's machine (format).


PLEASE HELP!!!!

[Dan Appleman]

It's probably DLL-****.

A missing dependency, or incorrect version of a DLL that your component needs.

I don't know if you've heard of our VersionStamper product (www.desaware.com), but
it's very helpful at resolving
these types of problems.
It can build a list of all the dependencies for your component on the system where it
works. Then you run a scan on the other system and it will show you a list of
components that are missing or obsolete.

Of course, the real magic starts when you are distributing your application, and you
build the technology into your application or component so that it becomes
self-verifying, or even self-updating.

Dan


Steven King wrote:

> Here's one for you (or anybody!).
>
> A component is installed on two different machines exactly the same (the
> registry entries on both machines are the same) but when a "New" or "CreateObject"
> call is called from an app on one machine the dreaded error "ActiveX component
> can't create object" occurs and on the other machine this call works fine!
> In a group of about 15 clients with this software, only 1 is having this
> problem.
>
> We've exported each's registry to a text file then parsed out the lines relevant
> then compared the two - they are exactly the same!
>
> Using Word's VB editor, the component shows up in the references list AND
> Intellisense can see its methods (it's typelib is registered OK). Unless
> we get an answer we'll have to rebuild the client's machine (format).
>
> PLEASE HELP!!!!

[Tsun Mok]

Steve,

This is a one of the typical DLL **** problems.
In addition to checking the Windows Registry,
Check the DLLs in diretories ado, ole db,
msadc under the \Program Files\Common Files
System directory

Match the files to those in the good machine
might solve the problem in some case.



"Steven King" <steve.king@mail.state.ky.us> wrote:
>
>Here's one for you (or anybody!).
>
>A component is installed on two different machines exactly the same (the
>registry entries on both machines are the same) but when a "New" or "CreateObject"
>call is called from an app on one machine the dreaded error "ActiveX component
>can't create object" occurs and on the other machine this call works fine!
> In a group of about 15 clients with this software, only 1 is having this
>problem.
>
>We've exported each's registry to a text file then parsed out the lines
relevant
>then compared the two - they are exactly the same!
>
>Using Word's VB editor, the component shows up in the references list AND
>Intellisense can see its methods (it's typelib is registered OK). Unless
>we get an answer we'll have to rebuild the client's machine (format).
>
>
>PLEASE HELP!!!!
>