Have you ever encountered an error while creating a listener in SQL Server? If so, you’re not alone. This is a common issue that many database administrators face when setting up a failover cluster instance or an AlwaysOn availability group.
One of the most common errors that you might come across is the “WSFC cluster could not bring the Network Name resource with DNS name ‘DNS name’ online” error. This error message indicates that there may be a conflict with the DNS name or the WSFC cluster service may not be running or accessible.
So, what could be causing this error? One possible reason is that the Domain Administrator has not granted the necessary permissions for the Cluster Name Object (CNO). The CNO requires “Read All Properties” and “Create computer Objects” permissions in order to create the network name or client access point resource in the cluster.
To resolve this issue, you can follow these steps:
- Connect to the domain controller with a user account that has permissions to create computer objects in the domain.
- Open the Active Directory Users and Computers Snap-in (dsa.msc).
- In the menu, go to View -> Advanced Features to enable advanced features.
- Right-click on the OU/Container where you want the Virtual Computer Object (VCO) to be created and select “New” -> “Computer”.
- Provide a name for the object, which will be your SQL Server Network Name in a failover cluster instance or Listener Name in an AlwaysOn availability group.
- Right-click on the VCO that you just created and select “Properties”.
- Click on the Security tab and then click “Add”.
- Enter the CNO (Cluster Name Object) and click “OK”. Make sure to select the “Computers” option in the “Object Types” window.
- Give the CNO “Full Control” over the VCO.
By following these steps, you should be able to resolve the “Access is denied” error and successfully create the listener.
It’s important to note that there may be other errors that you could encounter while creating a listener. If you have experienced any other errors, please share them in the comments below.
Thank you for reading and stay tuned for more SQL Server tips and tricks!