Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL Server error log and the Windows error log for additional error messages. If a low memory condition exists, investigate and correct its cause.
Could not set value for registry key '{2}' of type '{3}'. Examine if subkey '{1}' exists in registry hive '{0}' exists and ...
Could not start distributed query using integrated login because the user is logged in using SQL Server authentication. Provide ...
Could not start Service Broker for database id: %1!s!. A problem is preventing SQL Server from starting Service Broker. Check ...
Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages. ...
Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory ...
Could not start the network library because of an internal error in the network library. To determine the cause, review the ...
could not start the Replication Conflict Viewer for server '%2' using the command line '%1'. Be sure that the command line ...
could not start the Snapshot Agent to generate a new snapshot. You must start the Snapshot Agent manually before the subscription(s) ...
Could not submit Change Role completion tasks for %1!s!' (URI: '%2!s!', partition ID '%3!s!') . Encountered error (error ...