Microsoft Knowledge Base Email Alertz

(817230) - 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...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 817230 - Last Review: September 29, 2003 - Revision: 2.3

BUG: XLANG May Leak ADO Connections When a Transaction Fails

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.
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.

STATUS

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

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
    • the operating system: Microsoft Windows 2000
Keywords: 
kbpending kbbug KB817230
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate