Ag listener fail to offline in 2 node always on without AD

Kelvin Yu 0 Reputation points
2025-12-13T12:33:30.07+00:00

Let me describe my env first:

  1. Two nodes always on without domain (with witness share file)
  2. Both node is sql server 2022 and windows server 2022
  3. Both nodes are in the same subnet
  4. Set DNS server for these two nodes
  5. Didn’t register A record in DNS
  6. Didn’t set failover cluster ip and AG listener ip in servers’ host file
  7. AG listener using Static IP

When I try manual failover always on, it sometimes fails, and the always on status becomes 'resolving'. After 10 minutes, all things resume health automatically

The failure pattern is: After some time (quite random, normally more than one week) from last success

Ausqlsrvlis04 is ag listener name

Error from cluster log:

00000e40.00002960::2025/12/09-01:47:52.973 INFO [RCM] TransitionToState(sqlcluster04_AUSQLSRVLIS04) Online-->WaitingToGoOffline.

00000e40.00001fb4::2025/12/09-01:56:14.310 INFO [RCM] TransitionToState(sqlcluster04_AUSQLSRVLIS04) [Terminating to Failed]-->Failed.

Another event log:

A component on the server did not respond in a timely fashion. This caused the cluster resource 'sqlcluster04_AUSQLSRVLIS04' (resource type 'Network Name', DLL 'clusres.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.

SQL Server Database Engine
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2025-12-13T12:33:45.45+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    In your scenario with a two-node Always On Availability Group (AG) setup without Active Directory, there are several factors to consider regarding the failure of the AG listener to go offline and the subsequent timeout issues you are experiencing.

    1. DNS Configuration: Since you mentioned that you did not register the A record in DNS, it is crucial to ensure that the DNS settings are correctly configured. The AG listener relies on DNS for name resolution, and without proper DNS registration, clients may struggle to connect, leading to timeouts.
    2. Static IP Configuration: Using a static IP for the AG listener is valid, but ensure that this IP is correctly configured in both the SQL Server and Windows Failover Cluster settings. If there are any discrepancies, it could lead to the listener failing to transition states properly.
    3. Cluster Resource Timeout: The error logs indicate that a component did not respond in a timely manner, causing the cluster resource to exceed its timeout threshold. You may want to check the health of the underlying infrastructure, including network connectivity and any services that the cluster resource depends on. This includes ensuring that there are no network issues or high latency between the nodes.
    4. Failover Cluster Configuration: Since you are using a witness share, ensure that it is accessible and functioning correctly. Any issues with the witness can also impact the failover process.
    5. Manual Failover Behavior: The random nature of the failover failures suggests that there might be intermittent issues with resource availability or network stability. Monitoring the cluster logs during failover attempts can provide more insights into what might be causing the delays.
    6. Cluster Resource Management: Consider adjusting the timeout settings for the cluster resource if you find that the defaults are too aggressive for your environment. This can help prevent premature failover attempts during brief periods of unresponsiveness.

    By addressing these areas, you may improve the stability and responsiveness of your Always On AG listener during failover operations.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.