DCOM Proxy Is Decoupled with Server Stub When It Looks for Binding Handle

This article was previously published under Q324102
This article has been archived. It is offered "as is" and will no longer be updated.
In some Distributed Component Object Model (DCOM) client and server application scenarios, the client proxy may lose connection with the server stub. When this occurs, DCOM garbage collection runs down the orphaned server stub in approximately eight minutes. You cannot reboot the server computer to get the client proxy to work.
When the client tries to create the remote procedure call (RPC) binding handle for the server stub, the binding object is marked as initialized without checking the binding status. Therefore, if a binding operation fails, the client proxy does not contact the server again because the binding object has a NULL binding string, and DCOM garbage collection recycles the server stub.

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 Microsoft COM+ Hotfix Rollup 20.2.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
324034 INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 20.2
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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.
kbWin2000preSP3COMRollup202Fix disconnect disconnected kbIISCOM

Identyfikator artykułu: 324102 — ostatni przegląd: 02/28/2014 04:32:51 — zmiana: 2.3

Microsoft COM+ 1.0

  • kbnosurvey kbarchive kbwin2ksp4fix kbbug kbdcom kbfix kbwin2000presp3fix kbwin2000sp3fix KB324102
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)