TransactionScope implicitly or explicitly committed or aborted

[Rick_Kierner]

I am attempting to use the TransactionScope class to manage my transactions.
I am running into an issue. My web server [WEB1] is in an NT work group. My
SQL Server [SQL1] is in a domain. When my code attempts to execute the
Complete method of the TransactionScope object, I get the following error:

"The transaction has already been implicitly or explicitly committed or
aborted"

I have tried altering the registry entry to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1 on both
SQL1 and WEB1. I restarted both machines to make sure that changes took
effect.

When I run the code from a web server that is on the same domain as SQL1,
the code executes successfully. It is NOT and option to add WEB1 to a
domain.

Any suggestions?

[SP]

try turning off TurnOffRpcSecurity as per this article

http://support.microsoft.com/kb/Q827805

-sp

"Rick_Kierner" wrote:

I am attempting to use the TransactionScope class to manage my transactions.
I am running into an issue. My web server [WEB1] is in an NT work group. My
SQL Server [SQL1] is in a domain. When my code attempts to execute the
Complete method of the TransactionScope object, I get the following error:

"The transaction has already been implicitly or explicitly committed or
aborted"

I have tried altering the registry entry to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1 on both
SQL1 and WEB1. I restarted both machines to make sure that changes took
effect.

When I run the code from a web server that is on the same domain as SQL1,
the code executes successfully. It is NOT and option to add WEB1 to a
domain.

Any suggestions?

[Rick_Kierner]

As I stated in my post, that has been tried. It has come to my attention
that when working with SQL 2000, the transactionscope object automatically
promotes the transaction to a distributed transaction EVERY time. Is this
behavior by design? I thought it was only supposed to promote if it had to
be distributed.

"SP" wrote:

try turning off TurnOffRpcSecurity as per this article

http://support.microsoft.com/kb/Q827805

-sp

"Rick_Kierner" wrote:

I am attempting to use the TransactionScope class to manage my transactions.
I am running into an issue. My web server [WEB1] is in an NT work group. My
SQL Server [SQL1] is in a domain. When my code attempts to execute the
Complete method of the TransactionScope object, I get the following error:

"The transaction has already been implicitly or explicitly committed or
aborted"

I have tried altering the registry entry to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1 on both
SQL1 and WEB1. I restarted both machines to make sure that changes took
effect.

When I run the code from a web server that is on the same domain as SQL1,
the code executes successfully. It is NOT and option to add WEB1 to a
domain.

Any suggestions?

[SP]

oops, sorry about that,

we have run into the same problem, and I can't believe that there's no
solution for this. Have you tried the DTCtester.exe from ms what did that
report?

SP

"Rick_Kierner" wrote:

As I stated in my post, that has been tried. It has come to my attention
that when working with SQL 2000, the transactionscope object automatically
promotes the transaction to a distributed transaction EVERY time. Is this
behavior by design? I thought it was only supposed to promote if it had to
be distributed.

"SP" wrote:

try turning off TurnOffRpcSecurity as per this article

http://support.microsoft.com/kb/Q827805

-sp

"Rick_Kierner" wrote:

I am attempting to use the TransactionScope class to manage my transactions.
I am running into an issue. My web server [WEB1] is in an NT work group. My
SQL Server [SQL1] is in a domain. When my code attempts to execute the
Complete method of the TransactionScope object, I get the following error:

"The transaction has already been implicitly or explicitly committed or
aborted"

I have tried altering the registry entry to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1 on both
SQL1 and WEB1. I restarted both machines to make sure that changes took
effect.

When I run the code from a web server that is on the same domain as SQL1,
the code executes successfully. It is NOT and option to add WEB1 to a
domain.

Any suggestions?

[Rick_Kierner]

DTC actually won't work. I'm ok with that. The network admins have stated
that they will not open the ports necessary and won't add the DB servers to
the same domain as the web server. I figure that's a battle not worth
fighting.

My concern is that I don't really want to use DTC. It adds another layer of
complexity and performance inhibition. I would like for the TransactionScope
object to work as I had understood it to work (automatic promotion to DTC
only when necessary). Does anyone know if there are any plans for this to
take place?

--
Rick_Kierner
"SP" wrote:

oops, sorry about that,

we have run into the same problem, and I can't believe that there's no
solution for this. Have you tried the DTCtester.exe from ms what did that
report?

SP

"Rick_Kierner" wrote:

As I stated in my post, that has been tried. It has come to my attention
that when working with SQL 2000, the transactionscope object automatically
promotes the transaction to a distributed transaction EVERY time. Is this
behavior by design? I thought it was only supposed to promote if it had to
be distributed.

"SP" wrote:

try turning off TurnOffRpcSecurity as per this article

http://support.microsoft.com/kb/Q827805

-sp

"Rick_Kierner" wrote:

> I am attempting to use the TransactionScope class to manage my transactions.
> I am running into an issue. My web server [WEB1] is in an NT work group. My
> SQL Server [SQL1] is in a domain. When my code attempts to execute the
> Complete method of the TransactionScope object, I get the following error:
>
> "The transaction has already been implicitly or explicitly committed or
> aborted"
>
> I have tried altering the registry entry to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1 on both
> SQL1 and WEB1. I restarted both machines to make sure that changes took
> effect.
>
> When I run the code from a web server that is on the same domain as SQL1,
> the code executes successfully. It is NOT and option to add WEB1 to a
> domain.
>
> Any suggestions?

[Vince Bolduc]

[...]My concern is that I don't really want to use DTC. It adds another layer of complexity and performance inhibition. I would like for the TransactionScope object to work as I had understood it to work (automatic promotion to DTC only when necessary). Does anyone know if there are any plans for this to take place?

I ran into the exact same problem and have the same concern. As far as our company is concerned, using System.Transactions.TransactionScope is a NO GO.

My first intuitive comprehension of this feature, based on marketing texts and articles I've read made it look like one of the nicest addition to ADO.NET 2.0 (even if in fact it is independent from ADO).

After the reality check of a concrete implementation, I am very disapointed by the limits of this feature so far.

Any plans for a fix in the future? To bad our new architecture can't be based on this paradigm.