|
Home > Archive > BizTalk Server Applications Integration > July 2004 > Event log filling with RFSQL Deadlocked Errors, can anyone pleas h
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Event log filling with RFSQL Deadlocked Errors, can anyone pleas h
|
|
|
| I am running Biztalk 2002, using Microsoft BizTalk Adapter for SQL Server. I currently have 17 jobs running and will need to add even more. I keep getting the following error:
Event Type: Error
Event Source: RFSQL
Event Category: None
Event ID: 10
Date: 07/12/2004
Time: 8:54:56 AM
User: N/A
Computer: BIZTALK
Description:
A worker thread reported a failure: Transaction (Process ID 207) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
The error code is shown in the data area below.
The operation was: ISQLWorker->Execute
The worker thread was working on:
Job Name: USA_StockTransfers_IVT
SQL Script: Exec & #91;sp_SmoCreateStockTransfer_USA_IVT_Tr
ansactions]
| |
| Adrian Hamza[MSFT] 2004-07-12, 5:51 pm |
| Probably the SQL statements that you are using with the SQL Adapter are
blocking each-other and hence the deadlock. In order to further investigate
this issue with the SQL statements I recommend you to start SQL Profiler
(from Microsoft SQL Server) and capture tracing information while you repro
the scenario. You should make sure that you capture only events that are
happening in the database of interest (use a filter for this), and also
make sure you capture the "Lock" events. This should allow you to see the
SQL statements that are in a deadlock. Search in the SQL Server Books
Online documentation for more information on how to prevent deadlocks.
--------------------[vbcol=seagreen]
pleas h[vbcol=seagreen]
h[vbcol=seagreen]
Server. I currently have 17 jobs running and will need to add even more.
I keep getting the following error:[vbcol=seagreen]
deadlocked on lock resources with another process and has been chosen as
the deadlock victim. Rerun the transaction.[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
| Jan Eliasen 2004-07-16, 8:03 am |
| Hi
I can see you are executing a stored procedure and not just executing
a query. Take a look at your stored procedure, since this must be the
one deadlocking. Perhaps you can reaarange some statements to make the
stored procedure serializable with itself?
Jan Eliasen
On Mon, 12 Jul 2004 05:55:02 -0700, "Miles"
<Miles@discussions.microsoft.com> wrote:
>I am running Biztalk 2002, using Microsoft BizTalk Adapter for SQL Server. I currently have 17 jobs running and will need to add even more. I keep getting the following error:
>
>
>Event Type: Error
>Event Source: RFSQL
>Event Category: None
>Event ID: 10
>Date: 07/12/2004
>Time: 8:54:56 AM
>User: N/A
>Computer: BIZTALK
>Description:
>A worker thread reported a failure: Transaction (Process ID 207) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
>The error code is shown in the data area below.
>The operation was: ISQLWorker->Execute
>The worker thread was working on:
> Job Name: USA_StockTransfers_IVT
> SQL Script: Exec & #91;sp_SmoCreateStockTransfer_USA_IVT_Tr
ansactions]
>
--
Jan Eliasen, representing himself and not the company he works for.
|
|
|
|
|