SQL Server Errors or Failures from Error: 17174 to Error: 17196
Error: 17174, Severity: 10, Unable to initialize SQL Server native HTTP support due to insufficient resources. HTTP access to SQL Server will not be available. Error 0x%lx. This error typically indicates insufficient memory. Reduce non-essential memory load or increase system memory
Error: 17175, Severity: 10, The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
Error: 17176, Severity: 10, This instance of SQL Server last reported using a process ID of %s at %s (local) %s (UTC). This is an informational message only; no user action is required.
Error: 17177, Severity: 10, This instance of SQL Server has been using a process ID of %s since %s (local) %s (UTC). This is an informational message only; no user action is required.
Error: 17181, Severity: 16, SNIInitializeListener() failed with error 0x%lx.
Error: 17182, Severity: 16, TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
Error: 17183, Severity: 10, Attempting to cycle error log. This is an informational message only; no user action is required.
Error: 17184, Severity: 10, The error log has been reinitialized. See the previous log for older entries.
Error: 17185, Severity: 16, Unable to update password policy.
Error: 17186, Severity: 16, Failed to enqueue %s task. There may be insufficient memory.
Error: 17187, Severity: 16, SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. %.*ls
Error: 17188, Severity: 16, SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
Error: 17189, Severity: 16, SQL Server failed with error code 0x%x to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.%.*ls
Error: 17190, Severity: 16, Initializing the FallBack certificate failed with error code: %d, state: %d, error number: %d.
Error: 17191, Severity: 16, Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this s
Error: 17192, Severity: 10, Dedicated admin connection support was not started because of error 0x%lx, status code: 0x%lx. This error typically indicates a socket-based error, such as a port already in use.
Error: 17193, Severity: 10, SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
Error: 17194, Severity: 16, The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online
Error: 17195, Severity: 16, The server was unable to complete its initialization sequence because the available network libraries do not support the required level of encryption. The server process has stopped. Before restarting the server, verify that SSL certificates have been ins
Error: 17196, Severity: 10, Preparing for eventual growth to %d GB with Hot Add Memory.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.