Cannot use SAVE TRANSACTION within a distributed transaction

[MarathonMan]

I am running some Data-Centric and User-Centric components in a COM+ application.

The Data-Centric components have Requires Transaction on them - they have the setcomplete and setabort in them

The user centric components do not. They do not call set complete and set abort - they just instantiate the data-centric components
and of course the data-centric components take care of the transactions - or so I thought !

I get this error .....

" [Microsoft][ODBC SQL Server Driver][SQL SERVER]Cannot use SAVE TRANSACTION within a distributed transaction "

I have a SAVE point in a transaction in a stored procedure and I suspect this is conflicting with COM+ transactions - is it possible in any way to have SAVE points in stored procedures being called by transactional COM+ Data Centric components???


Many many thanks !!!!

[jamesf]

I have run into the same problem and think that you may be on the right track in thinking that the sprocs transaction is conflicting with COM+. Just for giggles, I set the transaction level for the object in COM+ to supported instead of required, and this seemed to help on some of the objects...but this is not really a permanent solution in my case. What is odd is that if I run the app in vb without reference to COM+, it works great. If I run the app as compiled dlls registered on a local machine, it works great, which does seem to point to a COM+ conflict. Have you tried removing the transaction altogether from the sproc as I have not tried this yet? I will be interested to hear if you solved the problem.