Distributed transaction completed errors

[Guest]

I am encountering SQLClient errors in a COM+ object (spawned from Biztalk) that extracts data from an xml document and updates a SQL table (version 2000 8.00.760 SP3)
Under a fairly low load of documents, there seems to be no problems, but with several messages to process, these errors start to stack up. I also see "SqlConnection does not support parallel transactions.
I am only using one SQL connection, one stored procedure - and one SQLTransaction that may be called a couple of times throughout the process
Any advice will be greatly appreciated
Troy

 

[David Schleifer [MSFT]]

When you say you have one connection, do you mean one for the entire process
(e.g.a static instance shared among all of the instances of the COM+
object)? My guess is that this error has something to do with that.

If that is the case, I'd recommend to instead try obtaining the connection
as late as possible, and closing the connection as soon as possible, rather
than trying to share the connection. Connection pooling will take place
under the covers so performance won't suffer, and it will also ensure that
your connection ends up being enlisted in the right distributed transaction.

- Dave

I am encountering SQLClient errors in a COM+ object (spawned from Biztalk)

that extracts data from an xml document and updates a SQL table (version
2000 8.00.760 SP3).

Under a fairly low load of documents, there seems to be no problems, but

with several messages to process, these errors start to stack up. I also see
"SqlConnection does not support parallel transactions."

I am only using one SQL connection, one stored procedure - and one

SQLTransaction that may be called a couple of times throughout the process.