Failed to start task to process a down notification for the local Windows Server Failover Clustering (WSFC) node (SQL OS error: %1!s!). Possible causes are no worker threads are available or there is insufficient memory. Check the state of the local WSFC node. If this problem persists, you might need to restart the instance of SQL Server.
Failed to set the resource dependency expression '%1!s!' for the WSFC resource '%2!s!'. The error code is %3!s!. The WSFC ...
Failed to set the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%1!s!' (Error code %2!s!). ...
Failed to simulate heap for Table '%s' specified in input configuration. Simulating heaps for tables requires SQL Server ...
Failed to start client information manager for replay. Invalid sequencing mode or other configuration settings have been ...
Failed to start task to process a down notification for the local Windows Server Failover Clustering (WSFC) node (SQL OS ...
Failed to start the task of the Windows Server Failover Clustering (WSFC) event notification worker (SQL OS error: %1!s!). ...
Failed to start the Windows Server Failover Clustering (WSFC) change listener (SQLOS error code %1!s!). SQL Server may not ...
Failed to stop the task of WSFC event notification worker (SQL OS error: %1!s!). If the problem persists, you might need ...
Failed to suspend data movement in database '{2}', which resides on the availability replica '{0}' in the availability group ...