Re: [Firebird-net-provider] TransactionScope "Unable to enlist in transaction, a local transaction already exists"

[MartinT <mar...@ya...>]

>From what I can gather Firebird doesn;t support a 2 phase commit so this kind
of scenario with a TransactionScope over 2 separate connections won't work
with FirebirdDotNetProvider because it is promoted to a DTC.

woudl be great if somebody more knowledgeable could verify this for me,
thanks


MartinT wrote:
> 
> Hi, sorry for double posting but I am under bit of pressure. Is the
> TransactionScope not fully supported by Firebird, or am I doign something
> wrong in my method calls to generate this problem, thanks
> 
> 
> MartinT wrote:
>> 
>> im trying to utilise the transactionscope in .net with the latest driver
>> v2.5.1. when i use a TransactionScope object and execute operations
>> within the same FbConnection, it works OK. however when i execute
>> operations on separate FbConnections (with the same connection strings)
>> then i am receiving the following exception:
>> 
>> System.ArgumentException was unhandled
>>   Message="Unable to enlist in transaction, a local transaction already
>> exists"
>>   Source="FirebirdSql.Data.FirebirdClient"
>>   StackTrace:
>>        at
>> FirebirdSql.Data.FirebirdClient.FbConnectionInternal.EnlistTransaction(Transaction
>> transaction)
>>        at FirebirdSql.Data.FirebirdClient.FbConnection.Open()
>>        at ... bla bla bla ...
>> 
>> help much appreciated as the usage of TransactionScope will save us heaps
>> of work rewriting data access layer code. thanks.
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/TransactionScope-%22Unable-to-enlist-in-transaction%2C-a-local-transaction-already-exists%22-tp25530564p25534520.html
Sent from the firebird-net-provider mailing list archive at Nabble.com.