May 22, 2012 at 8:38 am
Hi - I recently uninstalled a SQL cluster, however I am left with an issue with MSDTC. I am trying to re-create the cluster but the IP we assigned for MSDTC is saying that its in use. I can see there is a service and also in COM there is a clustered MSDTC.
How can I completely remove MSDTC from the cluster? I have tried MSDTC -uninstall but this just uninstalled the local copy of MSDTC and not the clustered one.
All thoughts welcome
Thanks
May 22, 2012 at 9:43 am
Can't you just delete it in Cluster Manager?
May 23, 2012 at 1:09 am
After uninstalling SQL its not longer in cluster manager, it was part of the same group.
May 23, 2012 at 8:01 am
Which version of Windows?
If you setup a clustered file server, does it show back up?
May 24, 2012 at 5:41 am
Hi - Its windows 2008 R2. I have not tired setting up any other type of cluster, however if I got to component services it is a clustered MSDTC in there.
I have removed the entry from DNS and flushed, also done msdtc -uninstall and -install, however I can not get rid of the clustered DTC from component services.
I am able to create a new clustered MSDTC with a different name, but I don't like this being untidy nor do I understand how to remove it.
Perhaps what I should have done was to delete the cluster resource in Cluster Failover Manager before uninstalling SQL
May 24, 2012 at 6:55 am
Well... you could always right click on the cluster and destroy it and then start over.
I don't have a lab cluster to play with, so I'm just exploring our production cluster looking for something to help 😉
May 24, 2012 at 7:22 am
Hey thanks for looking, just to be clear though there is not clustered resource in Failover Cluster Manager, its just present in Component Services. You can't even look at the properties of it, its although its no longer there but there is some residue, perhaps some regkeys or something left over.
Perhaps destroying the entire windows cluster may resolve it, but I think at present we are just going to create a new MSDTC clustered resource.
May 25, 2012 at 3:57 am
When you destroy a clustered service, very often the IP address is not deleted from the DNS server and the cluster name record is not deleted from Active Directory.
You should check both of these and delete the orphan records, otherwise you may not be able to re-install your cluster.
You should be able to delete any detritus left on the cluster servers for the MSDTC cluster by using Administrative Tools -> Component Services, then drilling down to see the Distributed Transaction Coordinator item. You may need to do this on all machines that were in the cluster.
If I was in your position, I would get Windows re-installed and start from a known clean state. What you are doing is OK as a learning experience in a sandbox, but not a professional approach for a Production machine.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 25, 2012 at 4:02 am
Hi thanks for the reply, I had already done everything you suggested apart from one aspect. You mentioned drilling down through component services to remove from there, however there is no option to delete through this route.
Thanks
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply