The server side of our product has two processes.

Program A is started as an NT service. After initializing
and registering its class objects, it WinExec()s program B.

Program B then connects back to program A by calling
CoCreateInstanceEx() with a server address of "127.0.0.1".

This works fine everywhere except one customer site. The
server is running NT4 sp5 and the local sysadmin describes
it as "mainly just a file/print server".

When program B starts, the CoCreateInstanceEx call fails with
"The RPC server is unavailable" and event ID 10009 is logged
to the event log: "DCOM was unable to communicate with the
computer 127.0.0.1 using any of the configured protocols".

I've asked them to send me the complete registry tree below
HKLM\Software\Microsoft\RPC and everything there looks OK.
The DCOMProtocols value has ncadg_ip_udp at the top as normal
for NT and ncadg_ip_udp has associated entries under
ClientProtocols and ServerProtocols.

I'm stuck. Web searches only throw up cases of remote
machines being unable to connect. And the only references
in the MS KB refer to COM+ and Windows 2000, which don't
apply here.

Any ideas?

Thanks in advance,
Kenn

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]