When you create a listener in SQL Server, Windows cluster creates a client access point resource. If SQL Server cannot create a listener, it may be unable to report the cause because Windows cluster is creating the resource. In this situation, you can collect the Windows cluster log and Windows System event log in order to diagnose the cause.
If you cannot create a listener, it is usually because of at least one of the following reasons:
- You do not have sufficient Windows cluster permissions to create and change an Active Directory cluster name account.
- You cannot register the IP address in DNS because of certain problems that involve a duplicate or invalid IP address.
- You violate the Windows policies.
SQL Server may not report the cause when you cannot create an availability group listener
However, you may also receive an error message that does not explain why you cannot create the group listener. For example, when you try to create an availability group listener, you receive an error message that resembles the following, which does not specify the actual cause of the error:
The WSFC cluster could not bring the Network Name resource with DNS name '<DNS name>' 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.
Article ID: 2829783 - Last Review: Apr 11, 2013 - Revision: 1