DCOM doesn't work

[strahd850]

I am attempting to run a dll on a remote machine. The DLL is registered on the remote machine and I have exported the registry information and imported it on the client side so the necessary reg information will be present. However, when I try to instantiate the object on the Remote machine I keep getting the infamous 'Run-time error '429' ActiveX component can't create object'
But, if I run the DLL in the VB IDE and try to create it from the client machine then everything works fine! This is driving me crazy...what is my problem?

[BBB]

Lets run through some things first ...

1. Create and ActiveX EXE on Machine A and build it (Select the option to produce the remote files, i.e. tlb file, etc.).
2. Create a test harness on machine A that uses the ActiveX EXE and build the test harness.
3. Run the test harness on machine A and check that the ActiveX works correctly on machine A.
4. Copy the ActiveX EXE onto machine B and double click on the ActiveX EXE (This registers it).
5. Register the tlb file on machine A using CliReg32 (See /? of clireg for help).
6. Install/Invoke DCOM on Machine B (Leave the default settings as they are for the time being).
7. Run the test harness on machine A ... check results.

Now depending on many factors, i.e. platform, permissions, user, what your ActiveX EXE does ... this may or may not have worked first time ... if it doesn't then supply more info and I will try to point you in the right direction.

P.S. Avoid using msgbox's and forms in the ActiveX EXE when trying to create your first Distributed app.

Later

Billy

[strahd850]

You da man, Billy! One question though...when you register the ActiveXExe on the remote machine, you have to supply the ip address of the machine that has the server. Is there any way around this? In other words, I want to be able to run these exes on random server machines. Does this make sence?

[BBB]

You mention " ...when you register the ActiveXEXE on the remote machine ..." note, to register the ActiveXEXE on the remote machine (Machine B) you only need to double click it. The registering of the 'TBL' file on the client machine (Machine A) is the more complex registering and help for this can be obtained by running clireg32.exe /?. The application will require details about the location of the remote server, i.e. the location of Machine B ... I believe your TBL can only point to one location.

Hope this is understandable.

Billy