locked
Another "Communication with the underlying transaction manager has failed."

    Question

  • I have this major problem a few weeks now, tried everything but I can't seem to get it working.
    This is the deal; at our company we have two domains, let's call them DOMA and DOMB. We have a trust between those domains.

    I have a transactionscope which contains calls to create multiple connections to a database server.

    The code will be run on a windows 2008 R2 computer in DOMA and will perform the transaction to a windows 2003 server (with sql) on DOMB.

    Firewalls are open (full udp/tcp everything)

    DTCPing shows no errors.
    Added hosts/domains to LMHOSTS file.

    But still I get this message:

    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)

    I'm stuck here. I feel I've tried everything I can find on the internet.

    MSDTC log (sql server) says:

    pid=872        ;tid=6364       ;time=02/17/2010-08:38:42.814   ;seq=914        ;eventid=TRANSACTION_BEGUN                        ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"transaction has begun, description :'user_transaction'"
    pid=872        ;tid=6364       ;time=02/17/2010-08:38:42.814   ;seq=915        ;eventid=RM_ENLISTED_IN_TRANSACTION               ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"resource manager #1001 enlisted as transaction enlistment #1. RM guid = '572d4191-1acd-4790-aa73-c9eaa2080561'"
    pid=872        ;tid=6364       ;time=02/17/2010-08:39:01.251   ;seq=916        ;eventid=RECEIVED_ABORT_REQUEST_FROM_BEGINNER     ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"received request to abort the transaction from beginner"
    pid=872        ;tid=6364       ;time=02/17/2010-08:39:01.251   ;seq=917        ;eventid=TRANSACTION_ABORTING                     ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"transaction is aborting"
    pid=872        ;tid=6364       ;time=02/17/2010-08:39:01.251   ;seq=918        ;eventid=RM_ISSUED_ABORT                          ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"abort request issued to resource manager #1001 for transaction enlistment #1"
    pid=872        ;tid=6364       ;time=02/17/2010-08:39:01.251   ;seq=919        ;eventid=RM_ACKNOWLEDGED_ABORT                    ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null)                                            '" ;"received acknowledgement of abort request from the resource manager #1001 for transaction enlistment #1"
    pid=872        ;tid=6364       ;time=02/17/2010-08:39:01.251   ;seq=920        ;eventid=TRANSACTION_ABORTED                      ;tx_guid=5891fe50-b8b0-43b6-a171-784716c530b3     ;"TM Identifier='(null) 

    I get that the transaction gets aborted. But I don't get WHY.

    Using nbtstat, both machines can find eachother trough hostname (without domain suffix, won't work with domain suffix, can that be the problem?)

    Any help is appreciated.


    Thursday, February 18, 2010 3:49 PM

Answers

  • Solved! I tried sniffing the network traffic. I found that we had another server (a Distributed Transaction Coordinator server), which was causing the problems. Opening the firewall to that server solved my problem!
    • Marked as answer by Cypher87 Friday, February 19, 2010 12:52 PM
    Friday, February 19, 2010 12:52 PM