Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Deadlock Issues Occur When You Update a Channel When a Server Is Under Stress


View products that this article applies to.

This article was previously published under Q275847

↑ Back to the top


Symptoms

When you edit a channel, you may experience deadlock issues with BizTalk Server while the server is under stress. The following errors may be logged to the event log:
An error occurred in BizTalk Server.

Details:
------------------------------
The database call failed and returned the following error string: "Transaction (Process ID 118) was deadlocked on {lock} resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". If possible, we will attempt to retry this call.

The following stored procedure call failed: "{call bts_oledb_outputconfigs_load(?, ?, ?, ?, ?, ?)}".


An error occurred in BizTalk Server.

Details:
------------------------------
The following stored procedure call failed: "{call bts_oledb_outputconfigs_load(?, ?, ?, ?, ?, ?)}".

Unspecified error

The database call failed and returned the following error string: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". If possible, we will attempt to retry this call.

The following stored procedure call failed: "{ call dta_log_outbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}".


An error occurred in BizTalk Server.

Details:
------------------------------
The following stored procedure call failed: "{ call dta_log_outbound_details( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}".

Unspecified error

Changes could not be committed to the database.


An error occurred in BizTalk Server.

Details:
------------------------------
The database call failed and returned the following error string: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". If possible, we will attempt to retry this call.

The following stored procedure call failed: "{ call cs_create_SuspendedQ_from_ScheduledQ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}".


An error occurred in BizTalk Server.

Details:
------------------------------
The root transaction wanted to commit, but transaction aborted

↑ Back to the top


Resolution

Disable the Receive function that is associated with channel being edited. When the modifications are complete, re-enable this Receive function.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in BizTalk Server 2000.

↑ Back to the top


Keywords: KB275847, kbpending, kbbug

↑ Back to the top

Article Info
Article ID : 275847
Revision : 4
Created on : 11/5/2003
Published on : 11/5/2003
Exists online : False
Views : 302