FIX: RosettaNet Receives "No Object for Moniker" Error Message from XLANG for Valid Monikers Under Stress (319975)


The information in this article applies to:

  • Microsoft BizTalk Server 2002
  • Microsoft BizTalk Server Accelerator for RosettaNet 1.0
This article was previously published under Q319975

SYMPTOMS

Under high stress, a Microsoft Visual Basic component that makes a call to the GetObject method (some valid moniker) may intermittently receive the following error message from the Visual Basic runtime, although the moniker is valid:
No Object
You may receive the following error because the GetObject call to the System Manager that is running in a separate process is unsuccessful intermittently:
RPC_E_DISCONNECTED: 0x80010108L

RESOLUTION

To work around this problem, add retry logic to the GetObject method call.

STATUS

Microsoft has confirmed that this is a problem in Biztalk Server 20002. This problem was corrected in Windows 2000 Post-SP2 COM+ Hotfix 20.
Modification Type:MajorLast Reviewed:7/30/2002
Keywords:KB319975
©2002 Microsoft Corporation. All rights reserved.