Microsoft KB Archive/319989

= High CPU Usage by RPCSS When You Start the Computer and Run a Service That Uses DCOM =

Article ID: 319989

Article Last Modified on 2/19/2007

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 3

-



This article was previously published under Q319989



SYMPTOMS
When you start your computer, Remote Procedure Call Server Service (RPCSS) may use a lot of CPU resources. This may occur if your computer runs a DCOM program that uses Remote Procedure Call (RPC) when the computer starts. This problem may occur intermittently, and might not occur every time that you start your computer.



CAUSE
When Windows sets up a connection, it tries to verify that the connection is secure. If the connection is not secure, Windows tries to set the connection to be secure and then retries the connection. Windows may loop through the retry attempts forever.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information
To resolve this problem, obtain and install the fix that is described in the following Microsoft Knowledge Base article:

324039 INFO: Availability of Windows 2000 Post-Service Pack 3 COM+ Hotfix Rollup Package 21



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Keywords: kbbug kbfix kbwin2000presp4fix kbwin2ksp4fix KB319989

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.