An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context failed. This attempt failed because switching the cluster context back to the local cluster at this time might cause data loss because one or more secondary databases on synchronous-commit replicas are not in the SYNCHRONIZED state. Wait until all synchronous-commit secondary databases are synchronized, and then retry the ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command.
An attempt to add or join a system database, '%1!s!', to an availability group failed. Specify only user databases for this ...
An attempt to attach an auto-named database for file %1!s! failed. A database with the same name exists, or specified file ...
An attempt to create a distributed transaction export token failed with this error: %1!s!. Contact your Microsoft Distributed ...
An attempt to fail over or create an availability group failed. This operation is not supported when Always On Availability ...
An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context ...
An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to a ...
An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to the ...
An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be ...
An attempt was made to change the RoleID of the '%{strPermID/}' permission from '%{strRoleID/}' to '%{strNewRoleID/}'. The ...