Microsoft KB Archive/319975

= FIX: RosettaNet Receives &quot;No Object for Moniker&quot; Error Message from XLANG for Valid Monikers Under Stress =

Article ID: 319975

Article Last Modified on 7/30/2002

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition
 * Microsoft BizTalk Accelerator for RosettaNet 1.0 Enterprise Edition

-



This article was previously published under Q319975



SYMPTOMS
Under high stress, a Microsoft Visual Basic component that makes a call to the GetObject method 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.

Keywords: KB319975

-

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

© Microsoft Corporation. All rights reserved.