DTCPING


Melissa     21st March 2012

DTCPing is a very useful tool for initial troubleshooting of DTC. If there is some type of failure it can give some errors through which we can analyze as to what can be the cause of the failure in transactions.

 

Steps to run the tool DTCPing:

  1. Launch DTCPing on both the servers involved in DTC communication. You will get the console as below:

 

                           

 

 

 2.  From one of the Servers, in the Remote Server Name type the host name of the client. You can get the hostname by opening a command prompt and typing the command “hostname” without the commas. Press the Ping button.

3. Then from the other machine, in the Remote Server Name give the hostname of the first server and press the ping button. This is the correct way of running the DTCPing tool.

4.  This shows the reverse bind too between the machines. Also, you can analyze the text files present in the folder of DTCPing which will contain the results of the Ping.

 

A typical output will look as below:

++++++++++++++++++++++++++++++++++++++++++++++

     DTCping 1.9 Report for T-MEAMAN 

++++++++++++++++++++++++++++++++++++++++++++++

Firewall Port Settings:

                Port:6000-6100

RPC server is ready

11-08, 12:45:10.408–>RPC server:T-MEAMAN received following information:

                Network Name: t-meaman

                Source  Port: 6009

                Partner LOG: MELISSAA340.log

                Partner CID: 5333B891-F376-45E0-B0E4-597E60300730

11-08, 12:45:47.678–>RPC server:T-MEAMAN received following information:

                Network Name: t-meaman

                Source  Port: 6009

                Partner LOG: MELISSAA3308.log

                Partner CID: 5333B891-F376-45E0-B0E4-597E60300730

++++++++++++Validating Remote Computer Name++++++++++++

11-08, 12:46:28.670–>Start DTC connection test

Name Resolution:

                melissaa–>10.171.70.188–>MELISSAA

11-08, 12:46:28.780–>Start RPC test (T-MEAMAN–>melissaa)

RPC test is successful

                Partner’s CID:5333B891-F376-45E0-B0E4-597E60300730

++++++++++++RPC test completed+++++++++++++++

++++++++++++Start DTC Binding Test +++++++++++++

Trying Bind to melissaa

11-08, 12:46:29.218–>T-MEAMAN Initiating DTC Binding Test….

                Test Guid:72283D9B-963A-41F0-A4C9-1EAF4010093B

Received reverse bind call from melissaa

                Network Name: t-meaman

                Source  Port: 6009

                Hosting Machine:T-MEAMAN

Binding success: T-MEAMAN–>melissaa

++++++++++++DTC Binding Test END+++++++++++++

++++++++++++Start Reverse Bind Test+++++++++++++

Received Bind call from melissaa

                Network Name: t-meaman

                Source  Port: 6009

                Hosting Machine:T-MEAMAN

11-08, 12:46:31.298–>Trying to Reverse Bind to melissaa…

                Test Guid:5333B891-F376-45E0-B0E4-597E60300730

Name Resolution:

                melissaa–>10.171.70.188–>MELISSAA

Reverse Binding success: T-MEAMAN–>melissaa

++++++++++++Reverse Bind Test ENDED++++++++++

 

 

You can refer the blog below to analyze the errors that we get with DTCPing and resolve the same.

 

http://blogs.msdn.com/b/distributedservices/archive/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool.aspx

 

For a cluster environment, we need to give the DTC network resource name instead of the hostname when we do a ping from the non-clustered server to the clustered one. You can get the network resource name as right clicking on the DTC name in the SQL Studio Management Wizard –> go to Properties à Go to the Dependencies tab and use the name specified there.  You can also use the cluster name if there is no DTC network name.

Reviewed by:

Earl Beaman

Microsoft

 

Comments (0)

Skip to main content