Microsoft KB Archive/281177

= Event IDs 12322, 12332, and 12308 Occur When You Use XLANG Scheduler =

Article ID: 281177

Article Last Modified on 11/6/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q281177



SYMPTOMS
When you use an XLANG Scheduler that uses custom COM+ components and transactions, the Event Viewer may log one or more of the following events:

Event ID: 12322

Event Source: XLANG Scheduler

Event Description: The state of the schedule instance could not be saved to the database. Detailed information is provided in the following message.

Module name:

Module ID: 

Instance ID: 

Database error(s):

Error Code = 0x8004e007 : You made a method call on a COM+ component that has a transaction that has already committed or aborted.

XLANG Scheduler Engine Internals Information:

File: d:\bts\private\sked\src\runtime\persistence\persist.cpp

Line: 263

Event ID: 12332

Event Source: XLANG Scheduler Error

Event Description: An error was encountered while attempting to persist an XLANG schedule instance. Detailed information is provided in the following message.

Error source: Field

name: __Correlation__

HRESULT: 0x8004e007

Module name:

Module ID: 

Instance ID: 

Error Code = 0x8004e007 : You made a method call on a COM+ component that has a transaction that has already committed or aborted.

XLANG Scheduler Engine Internals Information:

File: d:\bts\private\sked\src\runtime\execctxt\fieldinstance.cpp

Line: 225

Event ID: 12308

Event Source: XLANG Scheduler

Event Description: &quot;A scripted decision rule in an XLANG schedule instance could not be executed. The error returned by the script engine is shown in the following message. The script's source code and information about the schedule instance in which the error occurred is also provided.

Script error: Object doesn't support this property or method: 

Rule name: Access_Denied

Script expression: ' <>0 AND  = &quot;&quot;AccessDenied&quot;&quot;'

Module name:

Module ID: 

Instance ID: 



CAUSE
The transaction context times out before the call to the COM+ object can complete.



RESOLUTION
To resolve this problem, increase the transaction property timeout value and the connection timeout values. For additional informationabout how to increase the timeout values, click the article number below to view the article in the Microsoft Knowledge Base:

281167 INFO: Timeout Values for Database Connections and Command Objects Used by BizTalk Server 2000

Keywords: kbprb kbpending KB281177

-

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

© Microsoft Corporation. All rights reserved.