PRB: The Compiled Schedule Stops Responding When Receiving Data from COM Interface with the "No Instantiation" Option (312563)
The information in this article applies to:
- Microsoft BizTalk Server 2000
This article was previously published under Q312563 SYMPTOMS
If you bind an XLANG port to a Microsoft Visual Basic COM component and you select the No instantiation option, the resulting compiled schedule may stop responding or hang when you run it, particularly if the schedule is dehydrated.
CAUSE
This behavior occurs because of threading limitations that are inherent to Dynamic Link Libraries (DLLs) that are written in Visual Basic.
RESOLUTION
To work around this problem:
- Re-create your COM component as a free-threaded DLL that is written in C++.
- Bind your XLANG port to the C++ version of the COM component.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 9/30/2003 |
|---|
| Keywords: | kbnofix kbprb KB312563 |
|---|
|