DCOM May Not Release All Cached Information from RPCSS

ID: Q242916

The information in this article applies to:

Microsoft Windows NT Server versions 4.0 SP3, 4.0 SP4, 4.0 SP5

SYMPTOMS

When Component Object Model (COM) communicates with remote computers through Distributed Component Object Model (DCOM), it does not release all cached information from RPC Endpoint Mapper (RPCSS).

If a client (COM) program on one computer connects to to several remote servers (COM), this behavior results into a large handle count for RPCSS.

CAUSE

This behavior is caused by a problem in the RPC run-time component.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English-language version of this fix should have the following file attributes or later:


   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   09/29/99  05:53p               330,000 Rpcrt4.dll    Intel
   09/29/99  05:52p               579,344 Rpcrt4.dll    Alpha

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

Additional query words:

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0 SP3,4.0 SP4,4.0 SP5
Platform : winnt
Issue type : kbbug