Failed to bring availability group '%1!s!' online. The operation timed out. Verify that the local Windows Server Failover Clustering (WSFC) node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
Failed to acquire exclusive access to the extended recovery fork stack (error %1!s!). If the problem persists, you might ...
Failed to add a node to the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code %1!s!). ...
Failed to add a resource dependency, making resource '%1!s!' depend on resource '%2!s!', in the WSFC cluster. The error code ...
Failed to allocate and schedule an AlwaysOn Availability Groups task for database '%1!s!'. Manual intervention may be required ...
Failed to bring availability group '%1!s!' online. The operation timed out. Verify that the local Windows Server Failover ...
Failed to bring Availability Group '%1!s!' online. The Windows Server Failover Clustering (WSFC) service may not be running, ...
Failed to bring the Windows Server Failover Clustering (WSFC) group online (Error code %1!s!). The WSFC service may not be ...
Failed to change the encryption algorithm to '%1!s!'. An error occurred while encrypting the environment variables with the ...
Failed to change the encryption algorithm to '%1!s!'. An error occurred while encrypting the parameter values using the '%2!s!' ...