Calling a VB.NET com+ component from a vb 6.0 com+ component

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Kent - 01 Jul 2004 02:28 GMT

Need help!!!

This works on my development machine (of course).
I have 2 com+ components installed on a win2k server. 1 is a vb 6.0 dll and 1 is a vb.net dll. Here is the scenerio: I installed both on the server by exporting .MSI packages from my development machine and running the package on the server. A VB 6.0 client app makes a call to the VB 6.0 com+ component which makes a call to the vb.net com+ component. When the vb 6.0 com+ component tries to create the vb.net component it generates the error "Activex component can't create the object". I can call the vb.net component installed on the server from my machine from a vb.net client, so I know it is installed correctly for vb.net at least. Any ideas how to figure out what's going on?

Thanks in advance,
Kent

Reply to this Message

Klaus H. Probst - 01 Jul 2004 21:54 GMT

Are you sure you didn't export one of the MSIs as a proxy?

In general you shouldn't use MSIs to move applications from one machine to
another. It's much better to write a simple script that works with the COM+
admin to create the applications, set their attributes and secure them as
needed.

Signature

Klaus H. Probst, MVP
http://www.vbbox.com/

> Need help!!!
>
> This works on my development machine (of course).
> I have 2 com+ components installed on a win2k server. 1 is a vb 6.0 dll and 1 is a vb.net dll. Here is the scenerio: I installed both on the

server by exporting .MSI packages from my development machine and running
the package on the server. A VB 6.0 client app makes a call to the VB 6.0
com+ component which makes a call to the vb.net com+ component. When the vb
6.0 com+ component tries to create the vb.net component it generates the
error "Activex component can't create the object". I can call the vb.net
component installed on the server from my machine from a vb.net client, so I
know it is installed correctly for vb.net at least. Any ideas how to figure
out what's going on?

> Thanks in advance,
> Kent

Reply to this Message

Calling a VB.NET com+ component from a vb 6.0 com+ component

Free Magazines