locked
DTC Ping cannot run RRS feed

  • Question

  • I have two 64 bit Windows 2003 Servers. One is Web App, installed only IIS and .NET Framework 2.0, 3.0 & 3.5. Another is DB Server, installed SQL Server 2005, .NET Frameworkf 2.0, 3.0 and 3.5 also.

    I can save normal records from Web App. However, I got "Communication with Underlying transaction manager was failed." messages. I know that MS DTC was not configured properly since I have also solved the same thing on previous experiences.

    I wanted to hand-shake by using DTC Ping program. I can run well on Web App. However, cannot run on DB Server and program was crashed. A log file was generated on DB Server saying that "ACCESS_VIOLATION". I don't know what setting I am missing.

    Any workaround on 
    1) Why DTC Ping cannot be run on my DB Server with this "ACCESS_VIOLATION" message ?
    2) What setting i am missing ? (Actually, i have configured the MS DTC according to Microsoft KB articles).


    Any help would be much appreciated !!!!!!

    wunna
    Friday, March 6, 2009 2:12 PM

Answers

All replies

  • You should be able to use DtcPing tool. Can you post more information about the exception. 
    Also you can find more information below.

    http://msdn.microsoft.com/en-us/library/aa561924.aspx

    Friday, March 6, 2009 5:38 PM
    Moderator
  • Srini,

    This is the Log file content I've faced.

    =======================================================================================

    Platform:Windows 2003
     Windows 2003 environment is detected:
     Reading MSDTC settings from local registry:
    Open DTC root key failure: error(2)
    IP Configure Information
     Host Name . . . . . . . . . : XXXXXX
     DNS Servers . . . . . . . . : 10.150.1.50
                                             10.150.1.51
     Node Type . . . . . . . . . :
     NetBIOS Scope ID. . . . . . :
     IP Routing Enabled. . . . . : no
     WINS Proxy Enabled. . . . . : no
     NetBIOS Resolution Uses DNS : no

    Ethernet adapter {23734AF1-201D-406E-A8FD-A5B9CACEB22E}:

     Description . . . . . . . . :  xxxxxxxxxxx
     Physical Address. . . . . . : 00-23-7D-ED-92-18
     DHCP Enabled. . . . . . . . : no
     IP Address. . . . . . . . . : 10.102.10.32
     Subnet Mask . . . . . . . . : 255.255.0.0
     Default Gateway . . . . . . : 10.102.0.1
     DHCP Server . . . . . . . . :
     Primary WINS Server . . . . : 0.0.0.0
     Secondary WINS Server . . . : 0.0.0.0
     Lease Obtained. . . . . . . : Thu Jan 01 00:00:00 1970
     Lease Expires . . . . . . . : Thu Jan 01 00:00:00 1970

    Ethernet adapter {B3109815-510F-41D1-820F-649614D62024}:

     Description . . . . . . . . : xxxxxxx
     Physical Address. . . . . . : 00-23-7D-ED-92-36
     DHCP Enabled. . . . . . . . : yes
     IP Address. . . . . . . . . : 0.0.0.0
     Subnet Mask . . . . . . . . : 0.0.0.0
     Default Gateway . . . . . . :
     DHCP Server . . . . . . . . : 255.255.255.255
     Primary WINS Server . . . . : 0.0.0.0
     Secondary WINS Server . . . : 0.0.0.0
     Lease Obtained. . . . . . . : Tue Feb 24 07:49:31 2009
    //=====================================================
    Exception code: C0000005 ACCESS_VIOLATION

     Fault address:  0041E0E4

     Section(offset): 01:0001D0E4
    Registers:

    EAX:00000000 EBX:7EFDF000
    ECX:02031DE0 EDX:02031DE0
    ESI:002CFDA4 EDI:002CFDF8
    CS:EIP:0023:0041E0E4
    SS:ESP:002B:002CFD80  EBP:002CFD98
    DS:002B  ES:002B  FS:0053  GS:002B
    Flags:00010202
    fail to Enum loaded images
    +++++++++++loaded module information++++++++++++++
    Name                            Base    Size   

    +++++++++++execution path+++++++++++++++++++++++++
    +++++++++++++++END of Exception Report++++++++++++




    ==============================================================================


    wunna
    Saturday, March 7, 2009 3:41 AM
  • If you still have the issue, before we dig further can you check if the both the machines are configured so that MS DTC communication flows between the firewall?  Follow the steps in the below KB.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306843

    Refere to the troubleshooting step 3.
    Saturday, March 21, 2009 12:45 AM
    Moderator
  • I believe that the link contain information about the firewall problem that DTCPing is supposed to test. However I am having the same problem which is I can't even start DTCPing to test with it, due to "Open DTC root key failure: error(2)" problem.

    It seems like there is a particular registery key that needs to be present but for some reason it is not.

    Can anyone advise on this?
    Monday, July 27, 2009 2:00 PM
  • Can you provide details on source and desitnation configuration.
    Monday, July 27, 2009 5:32 PM
    Moderator
  • Hi, Ethan

    I am also having the same problem when using DTCPing, which I cannot start DTCPing to test and getting exception "Exception code: C0000005 ACCESS_VIOLATION". I turn-off FIREWALL so it will be not a cause. I think you figured it out. Please help me.

    Any help would be appreciated.



    Lokesh
     

    Monday, November 9, 2009 4:42 PM
  • Hi, David

    I am also having the same problem when using DTCPing, which I cannot start DTCPing to test and getting exception "Exception code: C0000005 ACCESS_VIOLATION". I turn-off FIREWALL so it will be not a cause. I think you figured it out. Please help me.

    Any help would be appreciated.



    Lokesh
    Monday, November 9, 2009 4:43 PM
  • Hi all,

    Just for anyone out there who is interested I had the similar problem above. I have just been configuring Windows 2003 64 bit MS DTC and trying to run DTCPing. The application failed to start and the output log contained the following errors.

    Open DTC root key failure: error(2)
    Exception code: C0000005 ACCESS_VIOLATION .. etc

    I have scratched my head like everyone else and was sure the registry had been configured correctly. In the end I noticed that the IP Address in the log was 0.0.0.0 which indicated to me there was some problem obtaining the network endpoint because when I ran IPConfig from the command line it listed the correct ip address. I then realised that there were 4 network ports, 3 of them inactive so I presumed that DTCPing was selecting one of them which did not have a valid connection. Disabled the inactive three and DTCPing started straight away and worked.

    The log still contains the registry error but I believe this is something to do with win 64 bit, didn't seem to stop the app working though.

    Hope this helps,

    Richard

    Friday, January 15, 2010 1:14 PM
  • Open DTC root key failure: error(2) indicates issues with the registry.  I removed DTC from cluster admin and re-added it, this seemed to fix this error.

    some more info here.

    http://radicalmeandering.blogspot.com/2007/05/distributed-transactions-between-xp-sp2.html
    Sunday, March 14, 2010 10:40 PM
  • You should be able to use DtcPing tool. Can you post more information about the exception. 
    Also you can find more information below.

    http://msdn.microsoft.com/en-us/library/aa561924.aspx


    Now I have a more clear idea about it, It is good for reference.
    Friday, August 27, 2010 1:06 AM