Jeff,

I solved the problem!  There was a gem in the first article you
supplied.  The answer was so easy I'm kicking myself in the face.

I just had to add the C:\windows\system32\msdtc.exe to the list of
exceptions to my windows firewall.

Now I just have to figure out how to configure MSDTC on Windows Server
2008. They moved everything around :P

On Jul 2, 6:04 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote:
> Hmm.
>
> You might need to change the configuration of the dev databases to enable
> cross-database or distributed transactions.  This is often turned off by
> default.  There can also be access control issues for remote clients.
>
> If it works locally but not remotely, I would expect that the problem is
> almost certainly some difference in configuration between your local
> environment and the remote one.  Unfortunately those differences can be
> exceedingly hard to find!
>
> MbUnit isn't really doing anything special here for the rollback.
>
> Some links that might 
> help:http://www.lucidocean.com/Blogs/Jonathan/UseTransactions_56723343848c...
> d0a1b35dd7869.aspxhttp://gps678.com/20/2b2ad946a0660730.htmlhttp://www.bokebb.com/dev/english/2056/posts/2056141537.shtml
>
> Jeff.
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On
>
> Behalf Of Scott Belchak
> Sent: Wednesday, July 02, 2008 1:12 PM
> To: MbUnit.User
> Subject: MbUnit Re: Problems with RollBack2 and multiple database calls
>
> Jeff,
>
> Thanks for the prompt reply!
>
> It works when I take one of the other database calls out.
>
> I am successfully using the RollBack2 attribute on about 50 other tests, but
> they are all testing methods that make single db connections.
>
> It errors when it tries to open up another connection, even after the first
> has been closed.
>
> This is driving me insane!  It works locally like a champ, but I have
> 26 tests that fail when I run them against the dev server.
>
> On Jul 2, 3:01 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote:
> > What happens when you disable one or the other connections?
>
> > Just to see, try commenting out or disabling the code that uses the
> > first connection.  Does it fail?  Undo those changes then try
> > commenting out or disabling the second connection.
>
> > Jeff.
>
> > -----Original Message-----
> > From: [email protected] [mailto:[EMAIL PROTECTED]
> > On
>
> > Behalf Of Scott Belchak
> > Sent: Wednesday, July 02, 2008 8:49 AM
> > To: MbUnit.User
> > Subject: MbUnit Re: Problems with RollBack2 and multiple database
> > calls
>
> > 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to