AO Listener creation failed - Error 19471

Question

AO Listener creation failed - Error 19471

SQL Galaxy

One Orange Chip

Points: 29472
More actions
December 1, 2015 at 12:39 am

#322938

Hi.
Now I am facing issues for creating AO listener in this setup. CNO pre-staged in AD cluster name object created successfully and up & running.
Error Messages:
The WSFC cluster could not bring the Network Name resource with DNS name 'ClusterHMSCLr' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. (Microsoft SQL Server, Error: 19471)
CNO - Cluster Name Object by used for domain account SQLAlways.admin having full control in AD.
Cluster name object created successfully up and running already.
Pre-staged listener object created in AD- domain account SQLAlways.admin having full control in AD and even though Computer Name Object creation permission assigned. but not hope still that same Error 19471 occurred while creating AO listener. Please help me what else need to be checked.
Event log errors 1: while creating AO listener group
Cluster network name resource 'HMS-HADR_CLUSTERHMSL' failed to create its associated computer object in domain 'in.abc.com' during: Resource online.
The text for the associated error code is: Access is denied.
Please work with your domain administrator to ensure that:
- The cluster identity 'CLUSTERHMSC$' has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity CLUSTERHMSC$'.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity 'CLUSTERHMSC$' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.
Event log errors 2:
Cluster resource 'HMS-HADR_CLUSTERHMSL' of type 'Network Name' in clustered role 'HMS-HADR' 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.
Thanks

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Justin Manning SA Hall of Fame Points: 3190 More actions · Answer 1

Try this link:

http://blogs.msdn.com/b/psssql/archive/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance.aspx

I had similar issues when setting up an AO environment. Permissions had to be explicitly granted to cluster name

Perry Whittle SSC Guru Points: 234013 More actions · Answer 2

Justin Manning SA (12/1/2015)
Permissions had to be explicitly granted to cluster name

This is correct

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

"Ya can't make an omelette without breaking just a few eggs" 😉

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 3

Thanks for your valuable reply..

In AD team shows to me, that Pre-staged Listener name object and domain account having FULL Control defined in AD level even same problem coming.

Pl. guide me. how to assign Permissions had to be explicitly granted to cluster name? in AD level. so that I will explain to my AD team.

Thanks

Justin Manning SA Hall of Fame Points: 3190 More actions · Answer 4

If you work through the link I posted earlier, you will see a step that needs to be performed:

Step 6 of Option #1:

6. Make sure "Read all properties" and "Create Computer objects" are checked. Click OK until you're back to the AD Users and Computer window:

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 5

Resolved issues.. listener created successfully after giving proper permission in AD side.

this Listener object must be added in cluster computer object security permissions with full rights

Thanks