Article ID: 281162
Article Last Modified on 10/17/2003
APPLIES TO
- Microsoft BizTalk Server 2000 Standard Edition
This article was previously published under Q281162
SYMPTOMS
When a COM component is registered, and the Visual Basic source code of the component is being executed for debugging purposes, if you use the BizTalk Orchestration Designer to bind the component to a port, it may not appear in the list of components for COM binding. If the COM component is not being executed in debug mode in Visual Basic, everything works as expected.
CAUSE
When Visual Basic is running a component in debug mode, Visual Basic temporarily removes the component entries from the HKEY_LOCAL_MACHINE registry key and creates a new registry entry in HKEY_CLASSES_ROOT. Visual Basic uses this information to temporarily cache the type library for the component. This registry key is removed as soon as the component is taken out of debug mode in Visual Basic.
When the COM Component Binding Wizard is executed, it builds a tree view, which lists all of the available components. Because the component entry is temporarily removed from the HKEY_LOCAL_MACHINE registry key, the wizard is unable to display the component in the list of available components.
WORKAROUND
Do not run the component in debug mode in Visual Basic.
STATUS
This behavior is by design.
MORE INFORMATION
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
283726 PRB: Error -2147319765 When You Use BizTalk Orchestration Designer to Bind a COM Component
Keywords: kbbug kbpending KB281162
