Availability group '%1!s!' failed to process the %2!s!-%3!s! command. The availability group configuration has been updated. ...

Availability group '%1!s!' failed to process the %2!s!-%3!s! command.  The availability group configuration has been updated.  However, the operation encountered SQL Server error %4!s! while applying the new configuration to the local availability replica, and has been terminated.  Refer to the SQL Server error log for details .  Verify that the local Windows Server Failover Clustering node is online.  Use an ALTER AVAILABILITY GROUP command to undo the changes to the availability group configuration.

Availability group '%1!s!' cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is ... Availability group '%1!s!' failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%2!s!) ... Availability group '%1!s!' failed to process %2!s!-%3!s! command. The local availability replica is not in a state that could ... Availability group '%1!s!' failed to process %2!s!-%3!s! command. The operation encountered SQL Server error %4!s! before ... Availability group '%1!s!' failed to process the %2!s!-%3!s! command. The availability group configuration has been updated. ... Availability group '%1!s!' failed to process the WSFC lease-renewal command. The local availability replica lease is no longer ... Availability group name to ID map entry for availability group '%1!s!' cannot be found in the Windows Server Failover Clustering ... Availability replica '%1!s!' cannot be added to availability group '%2!s!'. The availability group already contains an availability ... Availability replica '%1!s!' cannot be removed from availability group '%2!s!', because this replica is on the local instance ...