About Me

My photo
I am an MCSE in Data Management and Analytics, specializing in MS SQL Server, and an MCP in Azure. With over 19+ years of experience in the IT industry, I bring expertise in data management, Azure Cloud, Data Center Migration, Infrastructure Architecture planning, as well as Virtualization and automation. I have a deep passion for driving innovation through infrastructure automation, particularly using Terraform for efficient provisioning. If you're looking for guidance on automating your infrastructure or have questions about Azure, SQL Server, or cloud migration, feel free to reach out. I often write to capture my own experiences and insights for future reference, but I hope that sharing these experiences through my blog will help others on their journey as well. Thank you for reading!

Disk resource 'Cluster Disk X' cannot be used as a failover cluster disk.disk resource 'Cluster Disk X' is already in use by resource 'New Distributed Transaction Coordinator'

The specified disk resource 'Cluster Disk 10' cannot be used as a failover cluster disk.  Reason: The disk resource 'Cluster Disk 10' is already in use by resource 'New Distributed Transaction Coordinator (1)'. To use a disk in a new SQL Server failover cluster instance, the disk must not have any dependencies that reference it.
----------------------------------------------------------------------------------
The SQL Server failover cluster instance name 'XXXXXXSQLXXXX' already exists as a clustered resource.  Specify a different failover cluster instance name.
--------------------------------------------------------------------------------------------------------------------------

Error: - when you un-install SQL Server  MSDTC or any SQL server resource, sometimes do not clean neatly, even after remove node wizard executes successfully, and at a time of SQL Server Installation, will notice below error.. 

The specified disk resource 'Cluster Disk 1' cannot be used as a failover cluster disk.  Reason: The disk resource 'Cluster Disk X' is already in use by resource 'New Distributed Transaction Coordinator (1)'. To use a disk in a new SQL Server failover cluster instance, the disk must not have any dependencies that reference it.

Error in details.txt

(01) 2015-08-21 12:11:47 Slp: Inner exceptions are being indented
(01) 2015-08-21 12:11:47 Slp: 
(01) 2015-08-21 12:11:47 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
(01) 2015-08-21 12:11:47 Slp:     Message: 
(01) 2015-08-21 12:11:47 Slp:         The specified disk resource 'Cluster Disk 1' cannot be used as a failover cluster disk.  Reason: The disk resource 'Cluster Disk 10' is already in use by resource 'New Distributed Transaction Coordinator (1)'. To use a disk in a new SQL Server failover cluster instance, the disk must not have any dependencies that reference it.
(01) 2015-08-21 12:11:47 Slp:     HResult : 0x84b40002
(01) 2015-08-21 12:11:47 Slp:         FacilityCode : 1204 (4b4)
(01) 2015-08-21 12:11:47 Slp:         ErrorCode : 2 (0002)
(01) 2015-08-21 12:11:47 Slp:     Data: 
(01) 2015-08-21 12:11:47 Slp:       SQL.Setup.FailureCategory = InputSettingValidationFailure
(01) 2015-08-21 12:11:47 Slp:       DisableWatson = true
(01) 2015-08-21 12:11:47 Slp:     Stack: 

And

(01) 2015-08-21 13:03:31 Slp: Inner exceptions are being indented
(01) 2015-08-21 13:03:31 Slp: 
(01) 2015-08-21 13:03:31 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
(01) 2015-08-21 13:03:31 Slp:     Message: 
(01) 2015-08-21 13:03:31 Slp:         The SQL Server failover cluster instance name 'XXXXXXSQLXXXX' already exists as a clustered resource.  Specify a different failover cluster instance name.
(01) 2015-08-21 13:03:31 Slp:     HResult : 0x84b40002
(01) 2015-08-21 13:03:31 Slp:         FacilityCode : 1204 (4b4)
(01) 2015-08-21 13:03:31 Slp:         ErrorCode : 2 (0002)
(01) 2015-08-21 13:03:31 Slp:     Data: 
(01) 2015-08-21 13:03:31 Slp:       SQL.Setup.FailureCategory = InputSettingValidationFailure
(01) 2015-08-21 13:03:31 Slp:       DisableWatson = true
(01) 2015-08-21 13:03:31 Slp:     Stack: 
(01) 2015-08-21 13:03:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
(01) 2015-08-21 13:03:31 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
(01) 2015-08-21 13:03:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2015-08-21 13:03:31 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
(01) 2015-08-21 13:03:31 Slp: Collecting Cluster Logs:



Issue:-

While Installing SQl Server in Failover Cluster Environment, gets below error:-

The specified disk resource 'Cluster Disk X' cannot be used as a failover cluster disk.  Reason: The disk resource 'Cluster Disk X' is already in use by resource 'New Distributed Transaction Coordinator (1)'. To use a disk in a new SQL Server failover cluster instance, the disk must not have any dependencies that reference it.


Problem:-

Installation of SQL Server will gets fail. you will not find  any resource  with name "'New Distributed Transaction Coordinator (1)"  using  graphical mode of cluadmin.msc

so what you will do? How we will resolve this Error?

if you will search this in registry, with string "New Distributed Transaction Coordinator (1)", chances are  you will find this in "HKEY_LOCAL_MACHINE\Cluster\Resources"



Do not delete this key from here.

Resolution:-

 go to command prompt

run 
C:\> Cluster resource

  

You will get a resource with name "New Distributed Transaction Coorinator (1) as a resource

then
Run this command..

C:\>Cluster resource "New Distributed Transaction Coordinator (1)" /delete

After execution of this command, This offline resource will get deleted.

Now you can install SQL Server, SQL Server in cluster will get install successfully.


Thanks for reading..