Problems with DTC on Clustered SQL database. | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Problems with DTC on Clustered SQL database.

Has anyone successfully managed to create DTC transactions on a clustered SQL database?
We are experiencing problems trying to get the DTCs to work. (We also know they work successfully when on a non-clustered SQL DB).
Thanks in advance.

Hi Hugh, I’ve not tried to use DTC on a cluster, but may be able to help anyway…? Have you set up DTC to be cluster-aware?
Start comclust.exe from the command prompt.
When it is done, go to the Cluster Administrator and verify that MSDTC has been added to the Cluster Group as one of the shared resources.
Repeat the same procedure for each server node
>>>> Are you getting any specific errors? What OS, SQL, etc. are you running? Cheers
Twan PS also this link may help troubleshoot DTC;EN-US;Q306843
Hugh Kindly post thread in relevant forum, follow Twan’s suggestion for workaround.
(email’d WM to move the post) I’m sure you can modify the thread and move it to Cluster Forum. Thanks.
Satya SKJ

MSDTC has to be running on both the SQL Server and the client machine/server (web/app server, workstation etc.) to be able to work. 2.
If the MSDTC service is running on both machines but still doesn’t work then it’s most likely due to a name resolution issue or a firewall. MSDTC needs to be able to do name lookups (in both directions) on the servers involved to be able to function. To check this try and ping the SQL server by name from the web/app server and vice versa ping the web/app server by name from the SQL server. Be sure to ping the virtual SQL Server name. Use the DTCping.exe utility that Twan refered to:;EN-US;Q306843 You will notice (when using DTCping) that even if the client connects to the MSDTC service trough the virtual SQL Server name it will sometimes still resolve the physical node name of the node that currently owns the MSDTC service in the cluster. So make sure that name reolution works for the physical node names as well and not only the virtual names. 3.
If DNS or WINS are miss-configured or traffic is blocked in routers or something then add name and IP address entries in "lmhosts" and "hosts" files on the involved SQL server and web/app server or fix the DNS or WINS. 4.
If there is a firewall between the servers look at this article on what ports to open: INFO: Configuring Microsoft Distributed Transaction Coordinator (DTC) to Work Through a Firewall (Q250367);EN-US;q250367 /Argyle
Hugh kindly act as advised to move the thread. _________
Satya SKJ

How do I move the thread?
Edit your first post above by clicking Edit Reply button (with a pen/letter icon) and change the Forum name from list box. Thanks _________
Satya SKJ

I just did an sp_helpserver on both the old server and new server. The old server has both the SQL server AND the Web server listed. The SQL server has an ID of 0 and the web server has an id of 2. The new server only lists the SQL Server. It DOES NOT list the Web server when I execute the sp_helpserver. How can I add the web server so it will show up when I execute sp_helpserver on the new server? Could this be my problem???
Thamest: Kindly post thread in relevant forum. Luis Martin …Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
Bertrand Russell
SP_HELPSERVER reports information about a particular remote or replication server, or about all servers of both types. And it relates to only SQL Server not for non-SQL servers. Satya SKJ
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.