Sorry, it's a "Communication with the underlying transaction manager has failed.". The wording was padded within a caught exception thrown by my framework
It's a System.Transactions.TransactionManagerCommunicationException with an inner exception of: "Error HRESULT E_FAIL has been returned from a call to a COM component." On Jul 2, 10:40 am, Scott Belchak <[EMAIL PROTECTED]> wrote: > I am trying to use the RollBack2 attribute to test a method that opens > two database connections. > > The first one works and I am able to retrieve information from the > database, the second one borks. I get an "Unable to connect to > dbCommunication with the underlying transaction manager has failed." > error. > > This only happens when I am testing against a remote server; it works > fine locally. I have followed all the instructions outlined in > several posts on the internet to enable the MSDTC on both the server > and my dev machine, and it still won't work. > > I have a feeling this problem is arising because I am creating two > transactions. I don't know how I can work around this problem. > > Any suggestions? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
