transaction has already been implicitly or explicitly committed er

microsoft.public.dotnet.framework.adonet

14 Feb 2006 3:26 PM

Ben Lam

We are using MSDTC to handle our transactions and some clients seem to be
getting these errors more and more when we went to framework 2.0. Any ideas
what could be causing this?

Before in framework 1.1 we would ask our clients to re-register their
computer into the domain and/or rename their computer and this worked but it
seems like in framework 2.0 it doesn't do the trick. Also, the wrong dns
setup causes this too but after trying to fix both things it still doesn't
work. I believe this error means either the server has finished the
transaction and can't find the client to return the result or the active
directory account/computer account is corrupted. Any ideas?

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

Type: TransactionException
StackTrace:
Server stack trace:
   at
System.Transactions.Oletx.OletxTransactionManager.ProxyException(COMException
comException)
   at System.Transactions.TransactionInterop.GetExportCookie(Transaction
transaction, Byte[] whereabouts)
   at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction
tx)
   at System.Data.SqlClient.SqlInternalConnection.Enlist(Transaction tx)
   at System.Data.SqlClient.SqlInternalConnectionTds.Activate(Transaction
transaction)
   at
System.Data.ProviderBase.DbConnectionInternal.ActivateConnection(Transaction
transaction)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
   at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
   at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()