COM object with CLSID {...} is either not valid or registered

1 Feb 2006 10:24 AM

Tom

Hi Friends

I have a VB6 dll for ftp file to a remote server (third-party, free dll).
Now I migrate the application to VB.net and so I Add the vb6 dll in Reference
-> Switch to COM tab, a corresponding Interop is created. Then I run the
application in my machine and it works fine. But when I move to QA
environment, the above exception is thrown. I then try to register the
interop using regasm in QA machine but the same exception is thrown. Would
that mean the QA machine miss any dll that present in my machine, say, some
dll required by the third-party dll?

Many thanks in advance!!

Best Regards
Tom

1 Feb 2006 2:39 PM

Cowboy (Gregory A. Beamer) - MVP

You are missing a dependency somewhere.

My suggestion: Use something like Process explorer (sysinternals.com) on
both the dev and the QA machine and note the loaded libraries. That will give
you a big clue of what needs to be deployed.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

Show quote

"Tom" wrote:

> Hi Friends
>
> I have a VB6 dll for ftp file to a remote server (third-party, free dll).
> Now I migrate the application to VB.net and so I Add the vb6 dll in Reference
> -> Switch to COM tab, a corresponding Interop is created. Then I run the
> application in my machine and it works fine. But when I move to QA
> environment, the above exception is thrown. I then try to register the
> interop using regasm in QA machine but the same exception is thrown. Would
> that mean the QA machine miss any dll that present in my machine, say, some
> dll required by the third-party dll?
>
> Many thanks in advance!!
>
> Best Regards
> Tom

COM object with CLSID {...} is either not valid or registered - He