title: Is This MSDTC configuration Issue?
body: <p>It seems I am running into the Microsoft Distributed Transaction Coordinator (MSDTC) related issue.</p>
  
  <p><strong>SCENARIO</strong></p>
  
  <p>I am using TransactionScope and with in the single scope it hits two different databases on different servers (for instance, <strong>DB_A</strong> running Windows Server 2003 and <strong>DB_B</strong> running Windows Server 2008). One database is accessed using Entity Framework 4.0 and another using normal ADO.NET APIs.</p>
  
  <p>When I run the application from my development machine (running WinXP) it commits and rollbacks both the connections accurately. But when I run the application, deployed on another server (for instance <strong>WAS_A</strong> running Windows Server 2003) it commits correctly but in case of exception is doesn't roll back the database activities on both the servers.</p>
  
  <p>I thought it would be the MSDTC configuration issue on the <strong>WAS_A</strong>. So I went to the MSDTC -> Security Configuration and checked all the available options (as I did previously on other machines). But still I am facing the same issue.</p>
  
  <p>Looking for your expert advices. :)</p>