Distributed transaction problem

[Zameer Mohammed]

I am using COM+ components, every client request kicks of
a chain call of these components. One of the components
executes a SQL query, and this fails every time for a
particular client request. I am getting the following
exception on execution of the query.

Distributed transaction completed. Either enlist this
session in a new transaction or the NULL transaction.
System.Exception

_stackTraceString " at
System.Data.OleDb.OleDbDataReader.ProcessResults(Int32 hr)
at System.Data.OleDb.OleDbDataReader.NextResult()
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal
(CommandBehavior behavior, String method)
at System.Data.OleDb.OleDbCommand.ExecuteReader
(CommandBehavior behavior)
at
System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.Execu
teReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillFromCommand
(Object data, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet
dataSet, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet
dataSet)

Database : SQL Server 2000 SP3
..Net server : Windows 2003 Server on Dual processor m/c
Data provider : OleDb
MDAC : 2.7

 

[Angel Saenz-Badillos[MS]]

Could you post some more information?

When you open a connection without specifying Enlist=false it will
automatically look up the stack for an available distributed transaction,
when one is present the connection will auto enlist into this distributed
transaction.

Angel

 

[IbrahimMalluf]

Zameer;

you may be getting timeout errors or lock conflicts, or some other failure
causing the transaction to close. Make sure you are not locking any rows!

Ibrahim