Article ID: 297689 - Last Review: May 8, 2002 - Revision: 1.0

FIX: RPCSS Does Not Release TCP Connections

This article was previously published under Q297689
Expand all | Collapse all

SYMPTOMS

Under heavy load, RPCSS does not release Transmission Control Protocol (TCP) connections between the COM+ application proxy on the client computer and the COM+ application. Even hours after both the client and server processes shut down, the TCP connections are not released.

NOTE: This problem only occurs if the application passes interface pointers between the client and the application server. If the interface pointers are not passed, this problem does not occur.

The following error description may also be logged in the Event log:
DCOM was unable to communicate with the computer <COMPUTERNAME> using any of the configured protocols
When you use Performance Monitor or Netstat to monitor TCP connections, you see that the TCP connections are not released.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910  (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

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 Windows 2000 Service Pack 2.

APPLIES TO
  • Microsoft COM+ 1.0
Keywords: 
kbbug kbfaq kbfix kbwin2000presp2fix KB297689
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations