Error: 17892, Severity: 20, Logon failed for login ‘%.*ls’ due to trigger execution.%.*ls
Error: 17894, Severity: 10, Dispatcher (0x%lx) from dispatcher pool ‘%.*ls’ Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
Error: 17895, Severity: 10, sp_server_diagnostics running on Worker 0x%p appears to be non-yielding on Node %ld.
Error: 18002, Severity: 20, Exception happened when running extended stored procedure ‘%.*ls’ in the library ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.

Error: 18052, Severity: 16, Error: %d, Severity: %d, State: %d.
Error: 18053, Severity: 16, Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 18054, Severity: 16, Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.
Error: 18055, Severity: 20, Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support.

Error: 18056, Severity: 20, The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this e
Error: 18057, Severity: 20, Error: Failed to set up execution context.
Error: 18058, Severity: 17, Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and resource file in localized directory matches the file under English directory. Also check memory usage.
Error: 18059, Severity: 16, The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See “Impersonation Overview”
Error: 18060, Severity: 16, Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the message.
Error: 18061, Severity: 20, The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error me
Error: 18100, Severity: 10, Process ID %d was killed by hostname %.*ls, host process ID %d.
Error: 18113, Severity: 10, SQL Server shutdown after verifying system indexes.
Error: 18124, Severity: 10, The default collation was successfully changed.
Error: 18125, Severity: 10, Engine didn’t find configuration for error detection, default configuration was applied.
Error: 18126, Severity: 10, Engine failed to load configuration for error detection, default configuration was applied.
Error: 18127, Severity: 10, Engine takes DB offline in cloud DB mode due to %d, %d.

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.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.