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

Article translations Article translations
Article ID: 281177 - View products that this article applies to.
This article was previously published under Q281177
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

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 name>
Module ID: <module GUID>
Instance ID: <instance GUID>
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 name>
Module ID: <module GUID>
Instance ID: <instance GUID>

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: "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: <name of XLANG message.field>

Rule name: Access_Denied
Script expression: '<name of XLANG message.field> <>0 AND <name of XLANG message.field> = ""AccessDenied""'
Module name: <module name>
Module ID: <module GUID>
Instance ID: <instance GUID>

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

Properties

Article ID: 281177 - Last Review: October 21, 2013 - Revision: 3.1
APPLIES TO
  • Microsoft BizTalk Server 2000 Standard Edition
Keywords: 
kbnosurvey kbarchive kbpending kbprb KB281177

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com