The local availability replica of availability group '%1!s!' did not become primary. A concurrent operation may have changed the state of the availability group in Windows Server Failover Cluster. Verify that the availability group state in Windows Server Failover Cluster is correct, then retry the operation.
The listener with DNS name '%1!s!' for the availability group '%2!s!' is already listening on the TCP port %3!s!. Please ...
The LoadFromSQLServer method has encountered OLE DB error code 1!8.8X! (%2!s!). The SQL statement that was issued has failed. ...
The local availability replica of availability group '%1!s!' cannot accept signal '%2!s!' in its current replica role, '%3!s!', ...
The local availability replica of availability group '%1!s!' cannot become the primary replica. The last-known primary availability ...
The local availability replica of availability group '%1!s!' did not become primary. A concurrent operation may have changed ...
The local availability replica of availability group '%1!s!' is in a failed state. The replica failed to read or update the ...
The local computer is an owner of a cluster group that contains the SQL Server service, Analysis Services service or a generic ...
The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server ...
The local computer is the only node left in the failover cluster that has not been upgraded, or it is a single-node failover ...