Sql-server – MVC 3 : The MSDTC transaction manager was unable to pull the transaction from the source


I am using MVC 3 with Entities, now I have used the below line of codes from my controller

        using (var scope = new TransactionScope())
            _myRepository.DeleteFM2(id, name);

and inside my DeleteFM2 method which happens to be my method defined in the Entity class is as follows :

    public void DeleteFM2(int id, string name)
        var data= _repositoryMD.Fetch().Where(mColl => mColl.Col1 == id);

        if (data!= null)
                //insert here is giving some error MSDTC error !
                // here I prepare a message using the '**data**'
                _repositoryHistory.Insert(name, message, "FM2", "Delete", dateTime);


and I have a seperate class where I have defined the Insert method as

   public bool Insert(string realName, string logMessage, string tableName, string changeType, DateTime dateTime)
        var history = new History
            ModifiedBy = realName,
            ChangeType = changeType,
            DateModified = dateTime,
            LogMessage = logMessage,
            TableName = tableName


        return true;

After inserting this line of code in the above method DeleteFM2

      _repositoryHistory.Insert(name, message, "FM2", "Delete", dateTime);

I am getting this error, without this line my code works just fine, I have used this line in all of my other methods too even where I there I had used Transaction Scope, but I still dont seem to understand the problem here. Please help. Thanks

The underlying provider failed on Open.

Communication with the underlying transaction manager has failed. —>
System.Runtime.InteropServices.COMException: The MSDTC transaction
manager was unable to pull the transaction from the source transaction
manager due to communication problems. Possible causes are: a firewall
is present and it doesn't have an exception for the MSDTC process, the
two machines cannot find each other by their NetBIOS names, or the
support for network transactions is not enabled for one of the two
transaction managers. (Exception from HRESULT: 0x8004D02B) at
propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier,
Guid& transactionIdentifier, OletxTransactionIsolationLevel&
isolationLevel, ITransactionShim& transactionShim) at
propagationToken) — End of inner exception stack trace — at
propagationToken) at
tx) at
tx) at
System.Transactions.EnlistableStates.Promote(InternalTransaction tx)
at System.Transactions.Transaction.Promote() at
transaction) at
transaction, Byte[] whereabouts) at
transaction, Byte[] whereAbouts) at
tx) at System.Data.SqlClient.SqlInternalConnection.Enlist(Transaction
tx) at
transaction) at
transaction) at
owningObject) at
owningConnection) at
outerConnection, DbConnectionFactory connectionFactory) at
System.Data.SqlClient.SqlConnection.Open() at
openCondition, DbConnection storeConnectionToOpen, DbConnection
originalConnection, String exceptionCode, String attemptedOperation,
Boolean& closeStoreConnectionOnFailure)

My FireWall settings

My FireWall settings

Best Solution

I also encountered this error even though the config, firewalls and netbios/dns were set up correctly. The two servers in my setup were clones of one another, so MSDTC on each server had the same CID value, which makes them not able to interoperate.

Here are some other things to think about when troubleshooting MSDTC http://msdn.microsoft.com/en-us/library/aa561924.aspx My situation is described under Ensure that MSDTC is assigned a unique CID value

The MSDTC feature of the Windows operating system requires unique CID values to ensure that MSDTC functionality between computers works correctly. Disk duplicate images of Windows installations must have unique CID values or MSDTC functionality may be impaired. This can occur when using virtual hard disks to deploy an operating system to a virtual machine.

To determine if MSDTC CID values for computers that are running the Windows operating system are unique, check the values for the entries under the HKEY_CLASSES_ROOT\CID registry key on both computers. If these values are not unique for each computer then follow the steps in the section Consider reinstalling the Distributed Transaction Coordinator service if other troubleshooting steps are not successful to reinstall MSDTC on one of the computers, which will then generate unique MSDTC CID values for that computer and accommodate proper MSDTC operations.

To reset the CIDs on a Windows 2012 Server use the following Powershell script:

#View: CIDs (These must be different on all systems)
ls Microsoft.PowerShell.Core\Registry::HKEY_CLASSES_ROOT\CID | select Name

#reinstall MSDTC to regenerate CIDs. 
msdtc -uninstall
sleep 5
msdtc -install
sleep 5
Set-Service msdtc -startuptype "auto"
#then reboot for changes to take effect