Microsoft KB Archive/325601

= PRB: Running Schedules with Long-Running Transactions Do Not Finish After Failover =

Article ID: 325601

Article Last Modified on 9/29/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-



This article was previously published under Q325601



SYMPTOMS
When the BizTalk Server and the XLANG Scheduler Engine are clustered, running XLANG schedules on the first node may not finish on the second node after cluster failover. This occurs on schedules that have the whole business process (except for the Begin shape and the End shape) enclosed in a long-running transaction.



RESOLUTION
As a workaround, if your business process permits, you can use a DTC-style transaction to replace the long-running transaction and set the timeout value to 0 (no timeout).



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

Keywords: kbfix kbprb KB325601

-

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

© Microsoft Corporation. All rights reserved.