Microsoft KB Archive/817230

= BUG: XLANG May Leak ADO Connections When a Transaction Fails =

Article ID: 817230

Article Last Modified on 9/29/2003

-

APPLIES TO

 Microsoft BizTalk Server 2002 Standard Edition, when used with:  Microsoft Windows 2000 Service Pack 3

 Microsoft Windows 2000 Service Pack 2

 Microsoft Windows 2000 Service Pack 1

 Microsoft Windows 2000 Standard Edition</li></ul> </li></ul>

-

<div class="symptoms_section">

SYMPTOMS
A resource starvation issue may occur when you running multiple XLANG schedule instances that fail with a 0x8004e007 error. This problem may cause the database connection to be orphaned.

XLANG uses Microsoft ActiveX Data Objects (ADO) for database connectivity. When this problem occurs, the database connection leaks may cause multiple errors, including access violations. However, the error that occurs varies depending on the application that is involved.

<div class="cause_section">

This problem occurs under the following conditions:
 * The XLANG schedule instances that are running contain transaction semantics.
 * An ongoing transaction is aborted. This behavior causes an error.
 * The error causes COM Services to orphan the open connection to the XLANG database, although XLANG closed the connection to the database correctly.

The lack of system resources may cause an access violation in a custom component. This problem may also cause an access violation in XLANG itself. Although this problem was found in XLANG, this problem may occur in any application that uses ADO for database connectivity and that is using transactions.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Additional query words: 0x8004e007

Keywords: kbpending kbbug KB817230

-

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

© Microsoft Corporation. All rights reserved.