Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: RosettaNet Receives "No Object for Moniker" Error Message from XLANG for Valid Monikers Under Stress

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

View products that this article applies to.

This article was previously published under Q319975

↑ Back to the top

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

↑ Back to the top

Resolution

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

↑ Back to the top

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.

↑ Back to the top

Keywords: KB319975

↑ Back to the top

Article Info
Article ID : 319975
Revision : 3
Created on : 7/30/2002
Published on : 7/30/2002
Exists online : False
Views : 338