FIX: Remote COM Calls Fail Because RPCSS Is Not Started

MORE INFORMATION

Rpcss.exe is not needed for local communication between COM objects, thus COM delays loading it until it is truly necessary. COM is able to launch Rpcss.exe correctly if:

• The server is launched locally by COM.
• The server is started manually but the first class registration is from a multi-threaded apartment (MTA, aka "free-threaded") server.
• The server is launched manually, but the class object is registered in a suspended state (calling CoRegisterClassObject() with REGCLS_SUSPENDED flag).

However, Rpcss.exe is not launched reliably when a manually-started single- threaded apartment (STA) server is the first caller of CoRegisterClassObject.

Note that in server scenarios, COM only launches RPCSS if EnableRemoteConnection is set to Y.

There are other reasons a client application may not be able to communicate with a remote object:

• DCOM is not enabled on either the client or server computer.
• On Windows 95 server computers, remote connections have not been enabled.
• On Windows 95 server computers, the server application has not been manually launched.
• The client does not have appropriate permissions to communicate with the server.

You can determine whether an observed failure is caused by failure to launch Rpcss.exe by either checking whether the RPCSS process is running or manually starting Rpcss.exe before launching the server process.