locked
Cannot recreate listener (The maximum number of NetBIOS names may have been exceeded) RRS feed

  • Question

  • Hi,

     

    We have one alwayson group which has only one replica(primary) and one dummy database, then we create a listener, it works fine until we found there is a IP conflict yesterday, a virtual machine was assigned same IP address, now the replica is in resolving status, and database is in recovery pending(not synchronizing).

     

    I removed the alwayson availability group and tried to recreate it again.

     

    1:

     

    DROP AVAILABILITY GROUP [AGDB1A2];

     

    GO

     

    2:

    Use master

    Restore database [AGDB1A2] with recovery

     

    CREATE AVAILABILITY GROUP [AGDB1A2]

    WITH (AUTOMATED_BACKUP_PREFERENCE = SECONDARY)

    FOR DATABASE [AGDB1A2]

    REPLICA ON N'SYDCO-SSQL-1A\INSTANCE2' WITH (ENDPOINT_URL = N'TCP://test.alz.com:23', FAILOVER_MODE = MANUAL, AVAILABILITY_MODE = ASYNCHRONOUS_COMMIT, BACKUP_PRIORITY = 50, SECONDARY_ROLE(ALLOW_CONNECTIONS = NO));

     

    GO

     

    Until this step it is all good, then run the following t-sql statement to create listener is failed:

     

    USE [master]

     

    GO

    ALTER AVAILABILITY GROUP [AGDB1A2]

    ADD LISTENER N'AGDB1A2' (

    WITH IP

    ((N'10.61.198.20', N'10.255.248.0')

    )

    , PORT=1433);

    GO

     

     

     

    Those are the logs:

     

     

     

    1044:

     

    Encountered a failure when attempting to create a new NetBIOS interface while bringing resource 'AGDB1A2_10.61.198.20 online (error code '1450'). The maximum number of NetBIOS names may have been exceeded.

     

    1069:

     

    Cluster resource 'AGDB1A2_10.61.198.20 of type 'IP Address' in clustered role 'AGDB1A2' failed.

     

    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

     

    1205:

     

    The Cluster service failed to bring clustered role 'AGDB1A2' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

     

     

     

    1254:

     

    Clustered role 'AGDB1A2' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

    Does anyone know how to resolve it?

    Thanks,

    Albert


    • Edited by AlbertZOZ Tuesday, December 15, 2015 3:52 AM
    Monday, December 14, 2015 11:30 PM

Answers

All replies

  • Hi Albert,

    You need to remove the computerobjects from the Active directory. Looks like the clean up process is not completed.

    You can prestage the Listener with the allocated ip address and configured as well. 

    Re run the Cluster validation report again and make sure you did not have any errors.

    Good luck

    Kumar

    Tuesday, December 15, 2015 12:38 AM
  • Aside from the Active Directory virtual computer object for the Availability Group listener name, you need to remove the corresponding DNS entry. Alternatively, you can just use an entirely different listener name

    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master/Solutions Master
    Blog | Twitter | LinkedIn
    Learn SQL Server High Availability and Disaster Recovery


    Tuesday, December 15, 2015 3:26 AM
  • Thanks for your reply, Kumar.<o:p></o:p>

     

    We tried delete the AGDB1A2, and recreate AG(sucessfull), then create listener(failed)<o:p></o:p>

     

    prestage is not required, as we usually let the gui to automatically create the listener.<o:p></o:p>

     

    cluster validation does not have any errors.<o:p></o:p>

    Tuesday, December 15, 2015 3:52 AM
  • Thanks Edwin for your reply.

    I did try remove the dns and recreate AG(sucessfull), then create listener(failed)

    USE [master]
    GO
    ALTER AVAILABILITY GROUP [AGDB1A2]
    ADD LISTENER N'AGDB1A2' (
    WITH IP
    ((N'10.61.198.20', N'10.255.248.0')
    )
    , PORT=1433);
    GO

    Msg 41009, Level 16, State 7, Line 16
    The Windows Server Failover Clustering (WSFC) resource control API returned error code 5894.  The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  For information about this error code, see "System Error Codes" in the Windows Development documentation.
    Msg 19476, Level 16, State 3, Line 16
    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.
    Msg 19476, Level 16, State 1, Line 16
    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.

    Tuesday, December 15, 2015 3:54 AM
  • Hi AlbertZOZ,

    As mentioned in this article, error code 5894 means that a matching cluster network for the specified IP address could not be found.

    Please specify a subnet mask and a cluster network, make sure that you type the correct subnet addresses when creating AlwaysOn group listener.

    There are a similar thread and a blog for your reference.
    Error creating SQL2012 AvailabilityGroupListner
    Setup an Availability Group with Multiple Subnets in VMware Workstation

    Thanks,
    Lydia Zhang


    Lydia Zhang
    TechNet Community Support




    Tuesday, December 15, 2015 7:57 AM