SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


2017 Standard Edition Listener limit


2017 Standard Edition Listener limit

Author
Message
Rekonn
Rekonn
SSC Veteran
SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)

Group: General Forum Members
Points: 294 Visits: 269

Is there a limit to the number of listeners that can be created using SQL Server Standard?

I'm working with a DBA who has set up a 2017 Standard server, with CU3. We have 12 databases, and he was able to set up 12 basic availability groups. He was able to set up 10 listeners, but on the 11th, is getting the error below:

Create failed for Availability Group Listener 'test12300'. (Microsoft.SqlServer.Smo)


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


The WSFC cluster could not bring the Network Name resource with DNS name 'test12300' 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. If this is a WSFC availability group, 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. Otherwise, contact your primary support provider. (Microsoft SQL Server, Error: 19471)


Rekonn
Rekonn
SSC Veteran
SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)SSC Veteran (294 reputation)

Group: General Forum Members
Points: 294 Visits: 269

Think I found the answer, found the links below that describe the need to increase the ms-DS-MachineAccountQuota attribute from its default of 10. I think the original error message from the AG Wizard is a red herring.

Creating listeners with SQL Server AlwaysOn suddenly stopped working! - SOLVED
https://stackoverflow.com/questions/33717629/creating-listeners-with-sql-server-alwayson-suddenly-stopped-working-solved

Resolving an Error When Creating an Availability Group Listener
http://www.sqlservercentral.com/articles/always+on/145147/

Looking at Failover Cluster Manager on wal1qa-dw1a supports the scenario described on those links too: "The text for the associated error code is: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."


Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)SSC Guru (214K reputation)

Group: General Forum Members
Points: 214546 Visits: 18591
Rekonn - Friday, January 19, 2018 9:50 PM

Think I found the answer, found the links below that describe the need to increase the ms-DS-MachineAccountQuota attribute from its default of 10. I think the original error message from the AG Wizard is a red herring.

Creating listeners with SQL Server AlwaysOn suddenly stopped working! - SOLVED
https://stackoverflow.com/questions/33717629/creating-listeners-with-sql-server-alwayson-suddenly-stopped-working-solved

Resolving an Error When Creating an Availability Group Listener
http://www.sqlservercentral.com/articles/always+on/145147/

Looking at Failover Cluster Manager on wal1qa-dw1a supports the scenario described on those links too: "The text for the associated error code is: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."



10 is the limit for creating an AD computer object.
You should ideally have your AD admins pre stage the Listener computer account

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

"Ya can't make an omelette without breaking just a few eggs" ;-)
Evgeny Garaev
Evgeny Garaev
SSCertifiable
SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)SSCertifiable (5.3K reputation)

Group: General Forum Members
Points: 5341 Visits: 1564
SQL Server 2017 on Linux does not have a listener.
SQL Surfer '66
SQL Surfer '66
SSCarpal Tunnel
SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)

Group: General Forum Members
Points: 4650 Visits: 471
Rekonn - Friday, January 19, 2018 9:50 PM

Think I found the answer, found the links below that describe the need to increase the ms-DS-MachineAccountQuota attribute from its default of 10. I think the original error message from the AG Wizard is a red herring.

Creating listeners with SQL Server AlwaysOn suddenly stopped working! - SOLVED
https://stackoverflow.com/questions/33717629/creating-listeners-with-sql-server-alwayson-suddenly-stopped-working-solved

Resolving an Error When Creating an Availability Group Listener
http://www.sqlservercentral.com/articles/always+on/145147/

Looking at Failover Cluster Manager on wal1qa-dw1a supports the scenario described on those links too: "The text for the associated error code is: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."



Excellent. Thanks. This is really helpful.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search