Not able to add listener IP and Port to the secondary instance on the server

%3CLINGO-SUB%20id%3D%22lingo-sub-1506597%22%20slang%3D%22en-US%22%3ENot%20able%20to%20add%20listener%20IP%20and%20Port%20to%20the%20secondary%20instance%20on%20the%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1506597%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20am%20trying%20to%20add%20listener%20IP%20and%20port%20to%20the%20secondary%20instance%20on%20the%20server%2C%20I%20am%20getting%20the%20following%20error.%20Where%20I%20am%20able%20to%20add%20successfully%20on%20primary%20instance.%20(Both%20my%20primary%20instance%20and%20secondary%20instance%20on%20the%20same%20server)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%20Screenshot%20attached.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECreate%20failed%20for%20Availability%20Group%20Listener%20'SQLCDB01Temp'.%20(Microsoft.SqlServer.Smo)%3C%2FSPAN%3E%3CSPAN%3EThe%20WSFC%20cluster%20could%20not%20bring%20the%20Network%20Name%20resource%20with%20DNS%20name%20'SQLCDB01Temp'%20online.%20The%20DNS%20name%20may%20have%20been%20taken%20or%20have%20a%20conflict%20with%20existing%20name%20services%2C%20or%20the%20WSFC%20cluster%20service%20may%20not%20be%20running%20or%20may%20be%20inaccessible.%20Use%20a%20different%20DNS%20name%20to%20resolve%20name%20conflicts%2C%20or%20check%20the%20WSFC%20cluster%20log%20for%20more%20information.%20The%20attempt%20to%20create%20the%20network%20name%20and%20IP%20address%20for%20the%20listener%20failed.%20The%20WSFC%20service%20may%20not%20be%20running%20or%20may%20be%20inaccessible%20in%20its%20current%20state%2C%20or%20the%20values%20provided%20for%20the%20network%20name%20and%20IP%20address%20may%20be%20incorrect.%20Check%20the%20state%20of%20the%20WSFC%20duster%20and%20validate%20the%20network%20name%20and%20IP%20address%20with%20the%20network%20administrator.%20(Microsoft%20SQL%20Server%2C%20Error%3A%2019471)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1514919%22%20slang%3D%22en-US%22%3ERe%3A%20Not%20able%20to%20add%20listener%20IP%20and%20Port%20to%20the%20secondary%20instance%20on%20the%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1514919%22%20slang%3D%22en-US%22%3EHi%20Bhanu%20%2C%3CBR%20%2F%3EIt%20could%20be%20because%20of%20the%20permissions%20for%20cluster%20name%20object%20(CNO)%20in%20the%20active%20directory%20to%20create%20and%20read%20the%20listener%20object.%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20refer%20to%20the%20below%20article%20%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server-support%2Fcreate-listener-fails-with-message-the-wsfc-cluster-could-not%2Fba-p%2F318235%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsql-server-support%2Fcreate-listener-fails-with-message-the-wsfc-cluster-could-not%2Fba-p%2F318235%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

When I am trying to add listener IP and port to the secondary instance on the server, I am getting the following error. Where I am able to add successfully on primary instance. (Both my primary instance and secondary instance on the same server)

 

Error Screenshot attached.

 

Create failed for Availability Group Listener 'SQLCDB01Temp'. (Microsoft.SqlServer.Smo)The WSFC cluster could not bring the Network Name resource with DNS name 'SQLCDB01Temp' 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 duster and validate the network name and IP address with the network administrator. (Microsoft SQL Server, Error: 19471)

 

 

1 Reply
Highlighted
Hi Bhanu ,
It could be because of the permissions for cluster name object (CNO) in the active directory to create and read the listener object.

Please refer to the below article :
https://techcommunity.microsoft.com/t5/sql-server-support/create-listener-fails-with-message-the-wsf...