msdtc

I'm occasionaly getting this exception on our production server: System.ArgumentNullException: Value cannot be null. at System.Threading.Monitor.Enter(Object obj) at System.Data.ProviderBase.DbConnectionPool.TransactedConnectionPool.TransactionEnded(Transaction transaction, DbConnectionInternal transactedObject) at System.Data.SqlClient.SqlDelegatedTransaction.SinglePhaseCommit(SinglePhaseEnlistment enlistment) at System.Transactions.TransactionStateDelegatedCommitting.EnterState(InternalTransaction tx) at System.Transactions.CommittableTransaction.Commit() at System.Transactions

I'm sure I'm not the first to say it, but there's a severe lack of documentation on the finer points of Service Bus 1.0 for Windows Server out there... I'm hoping some of the MS insiders can help clear a few things up... Do services utilizing queues/topics run in an implicit, ambient transaction? For instance consider the following code snippet: [ServiceBehavior] public class MySbService : IDoWork { [OperationBehavior] void DoSomeWork(WorkRequest request) { DoDatabaseWork(); DoMoreDatabaseWork(); } } In the above sample, without creating an explicit TransactionScope , would DoDatabaseWork() be

Our packages are randomly failing with the following error message: SSIS Error Code DTS_E_OLEDBERROR . An OLE DB error has occurred. Error code: 0x8004D00A. COM error object information is available. Source: "[Some Package Name]" error code: 0x8004D00A Description: "The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction." This doesn't happen all the time, and re-running the package often succeeds, so I don't think it's a DTC or network config problem. This happens whether or not we're running the

We are using transaction scope features of ASP.NET to manage distributed transaction for that we need to enable distributed transaction via following link: The partner transaction manager has disabled its support for remote/network transactions Its works well with SQL Server 2005 and Windows Server 2003 but when it comes to Windows Server 2008 server and SQL Server 2005 we are getting following error, still we followed the same steps provided in above link: Windows Server 2008 + SQL Server 2005 + Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC

We are using MSDTC for SQL transactions. I am having issue with setting up firewall for MSDTC to work. The application and SQL are running on separate machine. Currently MSDTC is working if i turn off firewall on application server. I think there should be someway to add exception to the firewall setting for some ports. So that firewall can still be ON and DTC will not have any issues. I am not sure of the ports to add in firewall setting (I did try adding port 135 with no success) Have your Firewall allow port 135 and the dcom port range. By default, the dcom port range is 1024-65535. Thats a

I have hosted my Webapp on server 1 and my database on server 2 But i m getting following error "Communication with the underlying transaction manager has failed." I googled and found a post which mentioned that it is the issue of DTC(Distributed Transaction) I enabled DTC on server2(DB server) and made an exception of it in Firewall. But still same error. Here is the full stack trace Message: System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. ---> System.Runtime.InteropServices.COMException: The MSDTC transaction

Our team have got a problem that manifests as: The underlying provider failed on EnlistTransaction; Cannot access a disposed object.Object name: 'Transaction'. which seemed to appear as soon as we began using TransactionScope to handle our applications' transactions. The top part of the stacktrace is captured as: at System.Data.EntityClient.EntityConnection.EnlistTransaction(Transaction transaction) at System.Data.Objects.ObjectContext.EnsureConnection() at System.Data.Objects.ObjectContext.ExecuteStoreCommand(String commandText, Object[] parameters) at Reconciliation.Models.BillLines

are there any alternative to transactionScope which does not need to enable DTC?? In the transaction I need to make two operations: Create one user (using membership - sql membership provider) Do one insert operation. TransactionScope uses the LTM - Lightweight Transaction Manager in .Net. Only if you open more than one connection in the same transaction or go between databases, should TransactionScope promote the transaction to the 2PC-based TX-manager, DTC. For MS SQL Server 2008 and above, the DTC will become involved only if you are opening connections to different DBs. OR if you are