I just had an issue, after a CAU automatic patch, the AG always On group disappeared on secondary node, it was missing.
A quick fix — Restart the cluster service.
You can try to add the group back by T-SQL, you can try to add a dummy database and you can suspend one DB and resume. It just a test, this might work.
Error log:
A connection timeout has occurred on a previously established connection to availability replica ‘Primary Server’ with id [F58F54A2-F919-4BCF-9DB7-CBD2B10981BF]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
Always On Availability Groups connection with primary database ternated for secondary database ” on the availability replica ‘Primary Server’ with Replica ID: {f58f54a2-f919-4bcf-9db7-cbd2b10981bf}. This is an informational message only. No user action is required.
DbMgrPartnerComtPolicy::SetSyncAndRecoveryPoint: 116C857F-ED35-4CDD-A7E1-626CEDA77F78:4
Always On Availability Groups connection with secondary database ternated for primary database ” on the availability replica ‘Primary Server’ with Replica ID: {116c857f-ed35-4cdd-a7e1-626ceda77f78}. This is an informational message only. No user action is required.
A connection for availability group ‘Group’ from availability replica ‘Seconday Server’ with id [27C29DC0-087F-4E32-AE20-2DA69BD1F6A9] to ‘Primary Server’ with id [F58F54A2-F919-4BCF-9DB7-CBD2B10981BF] has been successfully established. This is an informational message only. No user action is required.
Always On Availability Groups connection with primary database established for secondary database ” on the availability replica ‘Primary Server’ with Replica ID: {f58f54a2-f919-4bcf-9db7-cbd2b10981bf}. This is an informational message only. No user action is required.
Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 41034.
Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user action is required.
Error: 41144, Severity: 16, State: 8.
The local availability replica of availability group ‘Group Name’ is in a failed state. The replica failed to read or update the persisted configuration data (SQL Server error: 41029). To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
Cannot process the operation. The local replica of availability Group ‘Group Name’ is in a failed state. A previous operation to read or update persisted configuration data for the availability group has failed. To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
The availability group database “” is changing roles from “SECONDARY” to “RESOLVING” because the rroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
Error: 41143, Severity: 16, State: 2.
cluadmin.msc log
Cluster node ‘Seconday Server’ was removed from the active failover cluster membership. The Cluster service on this node may have stopped.
This could also be due to the node having lost communication with other active nodes in the failover cluster.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node.
Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
No matching network interface found for resource ‘Cluster IP Address IPs’ IP address ‘IPs’ (return code was ‘5035’). If your cluster nodes span different subnets, this may be normal.
Cluster resource ‘IP Address IPs’ of type ‘IP Address’ in clustered role ‘Cluster Group’ 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 Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Cluster resource ‘Group Name_IPs’ of type ‘IP Address’ in clustered role ‘Group Name’ 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.
