DENALI CTP3 - incorrect error message when setting up Listener with no DNS access - by Rei

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 686548 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 9/1/2011 7:43:53 AM
Access Restriction Public


Trying to setup an AlwaysOn Listener after AG has been created is raising an error. The error message is incorrect.

Msg 19471, Level 16, State 0, Line 1
The WSFC cluster could not bring the Network Name resource with DNS name 'DELL_AG1_Listener' 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.
Msg 19476, Level 16, State 4, Line 1
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.

Sign in to post a comment.
Posted by Rei on 9/15/2011 at 10:26 PM
the issue is resolved, the name was changed by the DNS team, so I had to ask AD team to add as Computer Object and provide FullControl. That resolved the issue.

the ask here is to have a correct error message on what the issue is. Basically the install had no permissions to create the object in AD. Why cant you display this error message?
and the solution is to have it precreate the AD computer object and give Full Control.

This is a VERY common issue in large organizations where the DBA role is segregated from AD admin and DNS admin.
My 2 cents: I think there is a LOT of complexity added in Denali release by having to create CNO and so on where before it was all within the SQL realm. No AD, DNS was needed for DBM. I bet you if the message stays as is, CSS will get lots of calls and it will take hours to resolve. Cluster setup is complex.

thanks again.
Posted by David [MSFT] on 9/15/2011 at 8:09 PM

Are you still receiving the error message and can you send us the cluster error logs? The simplest command to create the log is to run 'cluster log /g'. A cluster log file will be generated and stored in the %windir%\Cluster\Reports directory on each node of the cluster.

We would like to research this and need some more information in order to resolve this issue.

Thank you,

David Pless
Posted by David [MSFT] on 9/7/2011 at 5:31 PM

Did you ever see a cluster error code message in the logs?

The other question I have is, have you been able to create listeners and / or client access points for your HADRON environment before receiving this error?

Thank you,

David Pless
Posted by Microsoft on 9/2/2011 at 12:40 PM
Thanks Ranjith, in the error message do you see a cluster error code?
we had a DCR bug to embed cluster errors into sql error message to make the error more clear to customers.
Finally due to lack of resource and implementation complexity , we declined the DCR and that's why you see the error message now is more general should you hit a cluster issue.

A good way to check it is to go to cluster manager and see cluster errors in detail or use : cluster.exe to dump the cluster log.
We also put the permission issue in AlwaysOn prerequisites in BoL to help all customers to avoid this issue in the front.

Sorry for the inconvenience.
Posted by David [MSFT] on 9/1/2011 at 2:16 PM

Thank you for contacting Microsoft. My name is David Pless. I am the Support Professional who will be working with you on this Service Request.

I will be looking into your issue and will be getting back to you shortly.

You may reach me using the contact information listed below. If you have any questions or concerns, please let me know.

Best Regards,

David Pless
Senior Premier Field Engineer - SQL Server
US East Premier Field Engineering
Microsoft Services


Microsoft respects your privacy. Please read our online Privacy Statement (
If you would prefer to no longer be contacted about participation in new Microsoft Connect programs, surveys, and events, please go to Your Profile ( to unsubscribe.
If you are a current participant in a Microsoft Connect beta program, you will continue to receive emails related to that program unless you end your participation by visiting Your Dashboard ( page and choosing 'quit' for that program. To set your contact preferences for other Microsoft communications, see the communications preferences section of the Microsoft Privacy Statement.
Alternatively, if you would prefer to no longer be contacted by Microsoft Connect, send an e-mail to with UNSUBSCRIBE in the subject line and we will unregister you from Microsoft Connect, ending your participation in all programs and connections.
Posted by Ranjith Reddy N on 9/1/2011 at 1:08 PM

This can be resolved by registering the Listner name (DELL_AG1_Listener) in the Active Directory computers and users (As we need to provide a DNS Name) before using it in the Listener creation wizard.