Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Windows Server 2012 R2 Clustering Issues Expand / Collapse
Author
Message
Posted Monday, April 7, 2014 8:20 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 10, 2014 6:52 AM
Points: 154, Visits: 954
Hi,

I am setting up a test Windows Server 2012 R2 VM with SQL Server 2008 R2 cluster. Setting up Windows Server 2008 R2 clusters always succeeds, but for some odd reason, I cannot figure out why my roles in the 2012 Cluster are failing. Here are some of the errors I get when attempting to put the roles online (this example is of the DTC role):

1) Clustered role '2012DTC12' 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.

2) The Cluster service failed to bring clustered role '2012DTC12' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

3) Cluster resource '2012DTC12' of type 'Network Name' in clustered role '2012DTC12' 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.

4) Cluster network name resource '2012DTC12' failed to create its associated computer object in domain 'XXX.local' during: Resource online.

The text for the associated error code is: A constraint violation occurred.


Please work with your domain administrator to ensure that:
- The cluster identity '2012CLUSTER$' has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity '2012CLUSTER$'.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity '2012CLUSTER$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.

If someone can please help, I'd greatly appreciate it!

Thank you!


My Blog!
Post #1559099
Posted Tuesday, April 8, 2014 5:30 AM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 11:32 AM
Points: 6,463, Visits: 13,914
dajonx (4/7/2014)
Please work with your domain administrator to ensure that:
- The cluster identity '2012CLUSTER$' has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity '2012CLUSTER$'.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity '2012CLUSTER$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.

If someone can please help, I'd greatly appreciate it!

Thank you!

The root issue above is covered here


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1559437
Posted Tuesday, April 8, 2014 8:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 10, 2014 6:52 AM
Points: 154, Visits: 954
Thank you, Perry!

Do you think I should change the cluster service from Local System Account to an Active Directory account (for example: Cluster Admin)? When I did make the change, I got an error:

Windows could not start the Cluster Service service on Local Computer.

Error 1297: A privilege that the service requires to function properly does not exist in the service account configuration. You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration.


My Blog!
Post #1559509
Posted Tuesday, April 8, 2014 9:20 AM This worked for the OP Answer marked as solution


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 11:32 AM
Points: 6,463, Visits: 13,914
No, the cluster service should be left as is. The issue is because the Cluster Name object does not have permission to create Virtual Computer Objects. Either pre stage them as defined in the link or grant the CNO permission to create them. the link has all the detail you need

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1559538
Posted Tuesday, April 8, 2014 9:22 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 10, 2014 6:52 AM
Points: 154, Visits: 954
Ok, sounds good! Thank you very much, Perry!

My Blog!
Post #1559539
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse