BUG: Security Information is not Synchronized

ID: Q165309

The information in this article applies to:

Microsoft OLE Libraries 4.0 included with: - Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

If client "A" initializes COM, then client "B" starts and makes a remote COM call, an attempt by Client "A" to make a secure remote COM call fails with error RPC_E_NO_GOOD_SECURITY_PACKAGES.

CAUSE

The problem occurs because security information is not being synchronized properly if, when it is time to launch Rpcss.exe in a client, COM finds that it has already been launched.

RESOLUTION

You can work around this problem by pre-launching Rpcss.exe before launching the client process. A convenient place to do this is in the registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Run (launches when the shell loads) or \RunServices (launches immediately upon machine boot, that is, before login). Add a named value (any name) and a value of "RPCSS.EXE".

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Note that there are other reasons a client application may not be able to communicate with a remote object.

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q165300
   TITLE     : BUG: Remote COM Calls Fail Because RPCSS is not Started

You can determine whether an observed failure is caused by failure to synchronize security information by manually starting RPCSS before launching the client process that failed.

Keywords          : LeTwoDCom kbbuglist
Version           : 4.0
Issue type        : kbbug

Last Reviewed: March 21, 1997