The remote procedure call failed and did not execute

[lenin]

Hi,
I am having a problem invoking a method call from a VB client making a call to COM+.

I have a couple of VB classes which I put into COM+. I then exported the COM+ application as an application proxy. Next I copied the msi and cab file to the client machine, with the VB client. I ran the msi file which went ok.

When I run the client thpugh I get

"The remote procedure call failed and did not execute"

both machines ( client and server are Win2k sp2 ).

I am able to ping both machines. I can see shares on each machine etc. This lead me think the issue was not network related.

Any help with this is greatly appreciated. The web seems a bit light with this issue.

Lenin

[jim mcnamara]

What you want to look for is called "NDR" - DCOM and RPC use the NDR engine and make calls to registered servers on remote boxes. That's why you got an RPC error.

I don't ever try to code this stuff in VB, but you can look up the RPC api's and try to make a very simple dummy app that calls your stub and try to debug what is happening.

Search for "RPC" then for "NDR" on MSDN

[bobbynad]

Will U guys convey me the process to initiate RPC. It could be greatful if U send me sample program in regard to RPC .

[biswajitdas]

your problem seems to be on authentication problem

it is true com required some authentication to run in every compuetr.


you can say minum to power user.

when you login in different machine just check the user aunthetication.


if your come is good running just check the authentication of that computer.
this will solve your problem

Biswajit das]