Error: 17813, Severity: 20, The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
Error: 17825, Severity: 18, Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. Review the error log: the entry listed after this error contains the error code from the network library.
Error: 17826, Severity: 18, Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17827, Severity: 20, There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls

Error: 17828, Severity: 20, The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
Error: 17829, Severity: 20, A network error occurred while establishing a connection; the connection has been closed.%.*ls
Error: 17830, Severity: 20, Network error code 0x%x occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms, network writes %d ms, network
Error: 17832, Severity: 20, The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls

Error: 17835, Severity: 20, Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library.%.*ls
Error: 17836, Severity: 20, Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.%.*ls
Error: 17881, Severity: 16, ‘%ls’ is an unsupported Open Data Services API.
Error: 17883, Severity: 10, Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yielding on Scheduler %ld. Thread creation time: %I64d. Approx Thread CPU Used: kernel %I64d ms, user %I64d ms. Process Utilization %d%%. System Idle %d%%. Interval: %I64d ms.
Error: 17884, Severity: 10, New queries assigned to process on Node %d have not been picked up by a worker thread in the last %d seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the “max worker threads” configurati
Error: 17885, Severity: 16, An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
Error: 17886, Severity: 20, The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the sessio
Error: 17887, Severity: 10, IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
Error: 17888, Severity: 10, All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
Error: 17889, Severity: 16, A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls
Error: 17890, Severity: 10, A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.
Error: 17891, Severity: 10, Resource Monitor (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Memory freed: %I64d KB. Last wait: %ls. Last clerk: type %ls, name %ls. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.

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.