The Windows Server Failover Clustering (WSFC) resource control API returned error code %1!s!. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
The Windows Server Failover Clustering (WSFC) change handle is invalid because a WSFC notification port has not been created ...
The Windows Server Failover Clustering (WSFC) cluster control API returned error code %1!s!. The WSFC service may not be ...
The Windows Server Failover Clustering (WSFC) group control API returned error code %1!s!. The WSFC service may not be running ...
The Windows Server Failover Clustering (WSFC) node control API returned error code %1!s!. The WSFC service may not be running ...
The Windows Server Failover Clustering (WSFC) resource control API returned error code %1!s!. The WSFC service may not be ...
The Windows service was not configured to use a built-in windows account. Previously designated settings are still be used. ...
The Winsock proxy cannot be configured using SQL Server tools. For information about how to configure the Winsock proxy, ...
The witness for the mirroring session received error response %1!s! (state %2!s!) from server instance %3!s! for database ...
The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE ...