I'm on my 2nd 2012 SQL multi-node cluster and I'm running into the same issue in bringing the resources online. In the first instance the issue was with a new sql instance for an app. Posted here:
I ended up having SQL installed and somehow the issue resolved itself.
In this new sql cluster I have the quorum online yet when trying to bring a new DTC resources online I get the following errors:
Event ID: 1069
Cluster resource 'SQLDTC' of type 'Network Name' in clustered role 'SQLDTC' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID: 1205
The Cluster service failed to bring clustered service or application 'SQLDTC' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Event ID: 1254
Clustered role 'SQLDTC' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to
bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring
it online again after the restart delay period.
I've tried moving the resource to the other node and bringing it online but it doesn't help. What I'd like to do is confirm the steps I'm taking to create the new resource from within the failover cluster manager console as I may be missing something. Normally I'd create the computer object within Active Directory and disable it but this wasn't working.
Here are the steps taken to create a new MS DTC resource:
1. Log into the SQL cluster and launch the Failover Cluster Manager console.
2. Expand the root tree, right-click “Roles” and click “Configure Role..”.
3. Click “Next” at the “High Availability Wizard” window.
4. Select “Distributed Transaction Coordinator (DTC)” and click “Next” to continue.
5. The “Client Access Point” window opens. Perform the following:
a. Enter a new name for the DTC: SQLDTC
b. Enter the newly assigned IP address: 10.150.50.134
c. Click “Next” to continue
6. The “Select Storage” window opens. Select the drive to be assigned to the MS DTC and click “Next” to continue.
7. Confirm the selections and click “Next” to continue.
8. The MS DTC has been successfully created. Click “Finish” to close the wizard.
9. The new MS DTC service appears with a status of “Offline”. This is by design if the computer object hasn’t been created within Active Directory.
10. Open the Active Directory Users & Computers console and navigate to the container to house the MS DTC computer object:
11. Right-click the container, select New, Computer, enter SQLDTC as the name for the new object, and click “OK”.
12. Right-click the new computer object and select Properties.
13. Click the “Security” tab, add the MS Virtual Cluster computer object, SQLCLUSTER1 , and assign it Full Control permissions.
14. Click “OK” to apply the changes.
15. Right-click the DTC computer object and select “Disable Account”.
16. Open a DOS command prompt type “gpupdate /force” and press enter.
17. Open the DNS management console and check to see if a new DNS record was created for the computer object. If not you’ll need to create it.
18. Right-click the new DNS entry, select Properties, add the MS Virtual Cluster computer object, SQLCLUSTER1 , and assign it Full Control permissions. Click "OK" to close the window.
19. Allow time for replication before making sure you can ping the new computer object via name and IP address.
Any response to the steps necessary to create this new object is greatly appreciated.