When I tried to run the DTCPing.exe, it's unable to run at all. Below is the error generated from the error log.

Is there any configuration that is required in order to run DTCPing in SQL Server?

++++++++++++hosts      ++++++++++++

Cluster Environment detected
07-08, 13:55:46.302-->DTC resource not found
07-08, 13:55:46.303-->Error(0x57) at clutil.cpp @516
07-08, 13:55:46.303-->-->ClusterResourceOpenEnum
07-08, 13:55:46.303-->-->87(The parameter is incorrect.)
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION

 Fault address:  65B7A004

Section(offset): 01:00039004
Registers:

EAX:0018FD6C EBX:7FFDE000
ECX:CCCCCCCC EDX:0018FD70
ESI:0018FD38 EDI:CCCCCCCC
CS:EIP:0023:65B7A004
SS:ESP:002B:0018FD1C  EBP:0018FD2C
DS:002B  ES:002B  FS:0053  GS:002B
Flags:00010286
fail to Enum loaded images
+++++++++++loaded module information++++++++++++++
Name                            Base    Size    

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

Hi,

On a clustered machine you should always put the name of the NETWORK RESOURCE on which the MSDTC resource is dependent on in the Remote Server Name field. To find out the right NETWORK NAME to use in DTCPing, open up the Cluster Administrator and go to the group in which the MSDTC Resource is present. That group should have one network name resource on which the DTC Resource is dependent on. To find out the network name, just go to the properties of the network name resource and go to the Parameters tab. The name that you see there is what is network name for this MSDTC resource. Lets understand this with an example :- lets say that you have a 2 node cluster with two nodes with the NETBIOS names as DBSERVER01 and DBSERVER02 and you are trying to run distributed transactions from a third server APPSERVER. Then to run DTCPing in the right way, you should start the DTCPING.EXE on the APPSERVER and the active node of the cluster. (By active node, I mean the node on which the DTC resource is online). Then from the Cluster Administrator go to the properties of the NETWORK NAME resource in which the Distributed Transaction Coordinator resource is present and go to the PARAMETERS tab. Note this network name. Once you have determined the right network name, launch DTCPING on the active node of the cluster and the APPSERVER and inside the DTCPing window on the APPSERVER, put in the network name of the clustered MSDTC Resource inside the (Remote Server Name) field and then click PING.

Check out this page for further DTCPing troubleshooting
http://blogs.msdn.com/b/distributedservices/archive/2008/11/12/troubleshooting-msdtc-issues-with-the-dtcping-tool.aspx

As a matter of fact, DTCPing can't even be started. The error is from the error log file.

Go through the steps in this article:
https://support.microsoft.com/en-us/kb/306843

The first thing came to my mind on seeing the error is "Is the MSDTC configured as a Clustered Resource at all?". When you cluster servers nowadays, the MSDTC configuration is automatically changed to the first clustered MSDTC instance (yes, you can create one MSDTC per Resource/Application Group). If you do not create a clustered MSDTC then the value of the transaction coordinator for the MSDTC service is left "BLANK" which is why the error.

Refer http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx - Yes I know it is for 2008 but the methodology is the same.

If you're going to create multiple instances of MSDTC then you also need to bookmark https://technet.microsoft.com/en-us/library/cc742483%28v=ws.10%29.aspx because without the proper mappings the whole purpose of having multiple MSDTC resources is lost.

Regards.

• Edited by ShankycheilMicrosoft community contributor 22 hours 20 minutes ago edit
• Proposed as answer by Rachit Sikroria 16 hours 32 minutes ago

The first thing came to my mind on seeing the error is "Is the MSDTC configured as a Clustered Resource at all?". When you cluster servers nowadays, the MSDTC configuration is automatically changed to the first clustered MSDTC instance (yes, you can create one MSDTC per Resource/Application Group). If you do not create a clustered MSDTC then the value of the transaction coordinator for the MSDTC service is left "BLANK" which is why the error.

Refer http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx - Yes I know it is for 2008 but the methodology is the same.

If you're going to create multiple instances of MSDTC then you also need to bookmark https://technet.microsoft.com/en-us/library/cc742483%28v=ws.10%29.aspx because without the proper mappings the whole purpose of having multiple MSDTC resources is lost.

Regards.

• Edited by ShankycheilMicrosoft community contributor Wednesday, July 08, 2015 8:44 AM edit
• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:32 PM

The first thing came to my mind on seeing the error is "Is the MSDTC configured as a Clustered Resource at all?". When you cluster servers nowadays, the MSDTC configuration is automatically changed to the first clustered MSDTC instance (yes, you can create one MSDTC per Resource/Application Group). If you do not create a clustered MSDTC then the value of the transaction coordinator for the MSDTC service is left "BLANK" which is why the error.

Refer http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx - Yes I know it is for 2008 but the methodology is the same.

If you're going to create multiple instances of MSDTC then you also need to bookmark https://technet.microsoft.com/en-us/library/cc742483%28v=ws.10%29.aspx because without the proper mappings the whole purpose of having multiple MSDTC resources is lost.

Regards.

• Edited by ShankycheilMicrosoft community contributor Wednesday, July 08, 2015 8:44 AM edit
• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:32 PM

The first thing came to my mind on seeing the error is "Is the MSDTC configured as a Clustered Resource at all?". When you cluster servers nowadays, the MSDTC configuration is automatically changed to the first clustered MSDTC instance (yes, you can create one MSDTC per Resource/Application Group). If you do not create a clustered MSDTC then the value of the transaction coordinator for the MSDTC service is left "BLANK" which is why the error.

Refer http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx - Yes I know it is for 2008 but the methodology is the same.

If you're going to create multiple instances of MSDTC then you also need to bookmark https://technet.microsoft.com/en-us/library/cc742483%28v=ws.10%29.aspx because without the proper mappings the whole purpose of having multiple MSDTC resources is lost.

Regards.

• Edited by ShankycheilMicrosoft community contributor Wednesday, July 08, 2015 8:44 AM edit
• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:32 PM

Thanks for all the reply. We found out that the clustering was not done properly. After fixing it, we're able to perform a DTCPing. Appreciate all the helps here.

Thanks for all the reply. We found out that the clustering was not done properly. After fixing it, we're able to perform a DTCPing. Appreciate all the helps here.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 48 minutes ago

Thanks for all the reply. We found out that the clustering was not done properly. After fixing it, we're able to perform a DTCPing. Appreciate all the helps here.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 6:17 AM

Thanks for all the reply. We found out that the clustering was not done properly. After fixing it, we're able to perform a DTCPing. Appreciate all the helps here.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 6:17 AM

Thanks for all the reply. We found out that the clustering was not done properly. After fixing it, we're able to perform a DTCPing. Appreciate all the helps here.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 6:17 AM