SQL Server Error Messages 17001 to 18000

In this post, we’ll list out the SQL Server Error Messages from the error codes 17001 to 18000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 17001 to 18000

ErrorCodeSeverityErrorMessage
1700116Failure to send an event notification instance of type ‘%s’ on conversation handle ‘%s’. Error Code = ‘%s’.
1700216Failed to post QUEUE_ACTIVATION event. Error code: ‘0x%s’.
1700316Closed event notification conversation endpoint with handle ‘%s’, due to the following error: ‘%.*ls’.
1700416Event notification conversation on dialog handle ‘%s’ closed without an error.
1700516Event notification ‘%ls’ in database ‘%ls’ dropped due to send time service broker errors. Check to ensure the conversation handle, service broker contract, and service specified in the event notification are active.
1704916Unable to cycle error log file from ‘%ls’ to ‘%ls’ due to OS error ‘%s’. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access.”
1705116SQL Server evaluation period has expired.
1705316%ls: Operating system error %ls encountered.
1705416The current event was not reported to the operating system error log. Operating system error = %s. You may need to clear the operating system error log if it is full.
1705610The evaluation period for your edition of SQL Server expires in %d day(s).
1705716Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer to help diagnose the root cause.
1705816initerrlog: Could not open error log file ‘%s’. Operating system error = %s.
1706010%s
1706110Error: %d Severity: %d State: %d %s
1706316Error: %d Severity: %d State: %d %s
1706516SQL Server Assertion: File: <%s>, line = %d Failed Assertion = ‘%s’ %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
1706616SQL Server Assertion: File: <%s>, line=%d Failed Assertion = ‘%s’. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
1706716SQL Server Assertion: File: <%s>, line = %d %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
1706810PrintStack Request
1706910%s
1707016Clustered instances are not supported on this edition of SQL Server.
1707116SQL Server could not start due to a boot failure. Operating system error = %s.
1707217The Extended Event session could not be created.
1707316Executing ‘sp_server_diagnostics’ stored procedure in repeat mode with ‘insert into’ clause is not allowed.
1707416Assertion “%ls” with message “%ls” at <%ls>:%ld failed.
1707516Assertion “%ls” at <%ls>:%ld failed.
1707621Error spawning System Health Monitor thread: %ls
1710110(c) Microsoft Corporation.
1710216Failed to initialize Distributed COM (CoInitializeEx returned %lx). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
1710310All rights reserved.
1710410Server process ID is %ld.
1710510Could not open master database in system task thread context. Terminating server.
1710610Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
1710710Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
1710810Password policy update was successful.
1710910FallBack certificate was successfully created.
1711010Registry startup parameters: %.*ls
1711110Logging SQL Server messages in file ‘%s’.
1711216An invalid startup option ‘%s’ was supplied, either from the registry or the command prompt. Correct or remove the option.
1711316Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
1711416Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
1711510Command Line Startup Parameters:%.*ls
1711616Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
1711710The tempdb database has %ld data file(s).
1711810Database Instant File Initialization: %S_MSG. For security and performance considerations see the topic ‘Database Instant File Initialization’ in SQL Server Books Online. This is an informational message only. No user action is required.
1711910The number of concurrent user connections was reduced to %ld, because it exceeded the allowable limit for this edition of SQL Server. To avoid this message in the future, use sp_configure to permanently adjust the number of user connections within the licensed limit.
1712016SQL Server could not spawn %s thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
1712110SQL Server is started with trace flag %d, this may cause user to see some error messages masked using ‘%ls’.
1712210Trace flag %d is discontinued. Use the options provided with ALTER DATABASE.
1712310Logging to event log is disabled. Startup option ‘-%c’ is supplied, either from the registry or the command prompt.
1712410SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
1712510Using dynamic lock allocation.  Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node.  This is an informational message only.  No user action is required.
1712610SQL Server is now ready for client connections. This is an informational message; no user action is required.
1712716initdata: No memory for kernel buffer hash table.
1712816initdata: No memory for kernel buffers.
1712910initconfig: Warning: affinity specified is not valid. Defaulting to no affinity. Use ALTER SERVER CONFIGURATION SET PROCESS AFFINITY to configure the system to be compatible with the CPU mask on the system. You can also configure the system based on the number of licensed CPUs.
1713016Not enough memory for the configured number of locks. Attempting to start with a smaller lock hash table, which may impact performance. Contact the database administrator to configure more memory for this instance of the Database Engine.
1713116Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
1713216Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory.
1713316Launch of startup procedure ‘%s’ failed.
1713410The tempdb database data files are not configured with the same initial size and autogrowth settings. To reduce potential allocation contention, the initial size and autogrowth of the files should be same.
1713510Launched startup procedure ‘%s’.
1713610Clearing tempdb database.
1713710Starting up database ‘%.*ls’.
1713816Unable to allocate enough memory to start ‘%ls’. Reduce non-essential memory load or increase system memory.
1713910The SQL Server image %ls was allocated using the large pages option.
1714016Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
1714116Could not register Service Control Handler. Operating system error = %s.
1714216SQL Server service has been paused. No new connections will be allowed. To resume the service, use SQL Computer Manager or the Services application in Control Panel.
1714316%s: Could not set Service Control Status. Operating system error = %s.
1714410SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, use SQL Computer Manager or the Services application in Control Panel.
1714510Service Control Handler received an invalid control code = %d.
1714610SQL Server is allowing new connections in response to ‘continue’ request from Service Control Manager. This is an informational message only. No user action is required.
1714710SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
1714810SQL Server is terminating in response to a ‘stop’ request from Service Control Manager. This is an informational message only. No user action is required.
1714910Using the static lock allocation specified in the locks configuration option.  Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node.  This is an informational message only. No user action is required.
1715010Lock partitioning is enabled.  This is an informational message only. No user action is required.
1715210Node configuration: node %ld: CPU mask: 0x%0*I64x:%u Active CPU mask: 0x%0*I64x:%u. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
1715310Processor affinity turned on: node %d, processor mask 0x%0*I64x. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
1715510I/O affinity turned on, processor mask 0x%0*I64x. Disk I/Os will execute on CPUs per affinity I/O mask/affinity64 mask config option. This is an informational message only; no user action is required.
1715616initeventlog: Could not initiate the EventLog Service for the key ‘%s’, last error code is %d.
1715810The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required.
1715910The server is idle. This is an informational message only. No user action is required.
1716110SQL Server could not use the NO_BUFFERING option during I/O, because the master file sector size, %d, is incorrect. Move the master file to a drive with a correct sector size.
1716210SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
1716310SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
1716410SQL Server detected %d sockets with %d cores per socket and %d logical processors per socket, %d total logical processors; using %d logical processors based on SQL Server licensing. This is an informational message; no user action is required.
1716510The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.
1716610Initializing Microsoft Distributed Transaction Coordinator (MS DTC) resource manager [%ls] for server instance %ls. This is an informational message only. No user action is required.
1716710Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
1716910Unable to locate kernel HTTP driver Httpapi.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support the kernel HTTP driver.
1717010SQL Server native HTTP support is not available. Could not find function entry point ‘%hs’ in %hs. Error 0x%lx. Native HTTP access to SQL Server requires a later version of the operating system.
1717110SQL Server native HTTP support failed and will not be available. ‘%hs()’ failed. Error 0x%lx.
1717216SNIInitialize() failed with error 0x%lx.
1717310Ignoring trace flag %u specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup.
1717410Unable 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.
1717510The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
1717610This 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.
1717710This 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.
1717810Warning: Enterprise Server/CAL license used for this instance. This edition limits SQL Engine CPU utilization to 20 physical cores, or 40 logical cores with Hyper-threading enabled.
1717910SQL Server detected %d sockets with %d cores per socket and %d logical processors per socket, %d total logical processors; using %d logical processors based on SQL Server licensing.
1718116SNIInitializeListener() failed with error 0x%lx.
1718216TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
1718310Attempting to cycle error log. This is an informational message only; no user action is required.
1718410The error log has been reinitialized. See the previous log for older entries.
1718516Unable to update password policy.
1718616Failed to enqueue %s task. There may be insufficient memory.
1718716SQL 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
1718816SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
1718916SQL 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 operating system error log for information about possible related problems.%.*ls
1719016Initializing the FallBack certificate failed with error code: %d, state: %d, error number: %d.
1719116Cannot 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 session was terminated by a KILL command or because of severe errors.%.*ls
1719210Dedicated 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.
1719310SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
1719416The 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 for information on this error message: %d %.*ls %.*ls
1719516The 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 installed. See Books Online topic “Configuring Client Protocols and Network Libraries”.
1719610Preparing for eventual growth to %d GB with Hot Add Memory.
1719716Login failed due to timeout; the connection has been closed. This error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls
1719816Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attempt to connect to a different endpoint on the server.%.*ls
1719910Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag %d. This is an informational message only. No user action is required.
1720016Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
1720110Dedicated admin connection support was established for listening locally on port %d.
1720210Dedicated admin connection support was established for listening remotely on port %d.
1720316SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to the System Requirements section in BOL for further information.
1720416%ls: Could not open file %ls for file number %d.  OS error: %ls.
1720510File %ls in database %ls has been set to sparse by the file system but does not belong to a database snapshot. The file should be restored to correct the problem.
1720610File %ls, file number %d for dbid %d is successfully mapped for use by Hybrid Buffer Pool.
1720716%ls: Operating system error %ls occurred while creating or opening file ‘%ls’. Diagnose and correct the operating system error, and retry the operation.
1720816%s: File ‘%s’ has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database from backup.
1720910File %ls, file number %d for dbid %d: File size is not configured multiple of the minimum size of a large page for Hybrid Buffer Pool.
1725310SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file ‘%s’, %d, is invalid. Move the file to a disk with a valid sector size.
1725510Secondary TempDB file ‘%.*ls’ resides on a removable drive and therefore will not be attached during startup.
1725610Secondary TempDB file ‘%.*ls’ will not be attached during TempDB startup; Drive check failed with error ‘%ld’.
1725710System error while trying to initialize disk info; Error ‘%ld’
1725810No free space in the TempDB database
1725910Dedicated admin connection support was established for listening locally on named pipe [ %s ].
1726010Dedicated admin connection support was established for listening remotely on named pipe [ %s ].
1726116initdata: No shared memory for kernel buffers.
1726216Replicated master not available for server state initialization during startup.
1726316Contained availability group master database not available for server state initialization during startup.
1730016SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option ‘user connections’ to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
1730316The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
1730816%s: Process %d generated an access violation. SQL Server is terminating this process.
1731020A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
1731116SQL Server is terminating because of fatal exception %lx. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
1731216SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
1731310Unable to locate driver ntdll.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support this driver.
1740110Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required.
1740310Server resumed execution after being idle %d seconds. Reason: timer event.
1740410The server resumed execution after being idle for %d seconds.
1740524An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
1740610Server resumed execution after being idle %d seconds. Reason: resource pressure.
1740710The automatic soft-NUMA is already set to ‘%S_MSG’. No further action is necessary.
1740810The automatic soft-NUMA configuration has been set to ‘%S_MSG’. Restart SQL server for the new setting to take effect.
1740910Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than %lu physical cores.
1741010Automatic soft-NUMA was not enabled, because ‘NodeConfiguration’ key was detected in the registry at path ‘%ls’. Disable registry based soft-NUMA configuration in order to activate the automatic soft-NUMA configuration.
1755010DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
1755110DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
1755716DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
1755810Bypassing recovery for database ID %d. This is an informational message only. No user action is required.
1756010DBCC DBREPAIR: ‘%ls’ index restored for ‘%ls.%ls’.
1756110%ls index restored for %ls.%ls.
1757216DBCC cannot free DLL ‘%ls’. SQL Server requires this DLL in order to function properly.
1757310CHECKDB for database ‘%ls’ finished without errors on %ls (local time). This is an informational message only; no user action is required.
1765610Warning ******************
1765710Attempting to change default collation to %s.
1765810SQL Server started in single-user mode. This an informational message only. No user action is required.
1765910Warning: System table ID %d has been updated directly in database ID %d and cache coherence may not have been maintained. SQL Server should be restarted.
1766010Starting without recovery. This is an informational message only. No user action is required.
1766110Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
1766310Server name is ‘%s’. This is an informational message only. No user action is required.
1766410The NETBIOS name of the local node that is running the server is ‘%ls’. This is an informational message only. No user action is required.
1767410Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
1767610SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.
1775016Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls.
1775116Could not find the function %ls in the library %ls. Reason: %ls.
1775216SQL Server has insufficient memory to run the extended stored procedure ‘%ls’. Release server memory resources by closing connections or ending transactions.
1775316%.*ls can only be executed in the master database.
1780220The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. The connection has been closed. %.*ls
1780320There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
1780520The value in the usertype field of the login record is invalid. The value 0x01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server.%.*ls
1780620SSPI handshake failed with error code 0x%x, state %d while establishing a connection with integrated security; the connection has been closed. Reason: %.*ls %.*ls %.*ls
1780720Event ‘%ld’, which was received from the client, is not recognized by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent.
1780920Could not connect because the maximum number of ‘%ld’ user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.%.*ls
1781020Could not connect because the maximum number of ‘%ld’ dedicated administrator connections already exists. Before a new connection can be made, the existing dedicated administrator connection must be dropped, either by logging off or ending the process.%.*ls
1781110The maximum number of dedicated administrator connections for this instance is ‘%ld’
1781210Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required.
1781320The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
1781620Login to remote SQL Server failed with error %d: %.*ls
1781720Unsupport login ack packet response received when opening client connection.%.*ls
1781820Connection to remote SQL Server failed with error %d.
1782518Could 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.
1782618Could 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.
1782720There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
1782820The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
1782920A network error occurred while establishing a connection; the connection has been closed.%.*ls
1783020Network 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 reads %d ms, establishing SSL %d ms, network reads during SSL %d ms, network writes during SSL %d ms, secure calls during SSL %d ms, enqueued during SSL %d ms, negotiating SSPI %d ms, network reads during SSPI %d ms, network writes during SSPI %d ms, secure calls during SSPI %d ms, enqueued during SSPI %d ms, validating login %d ms, including user-defined login processing %d ms.%.*ls
1783220The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
1783520Encryption 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
1783620Length 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
1788116‘%ls’ is an unsupported Open Data Services API.
1788310Process %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.
1788410New 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” configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %d%%. System Idle: %d%%.
1788516An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
1788620The 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 session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
1788710IO 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.
1788810All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
1788916A 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
1789010A 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%%.
1789110Resource 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.
1789220Logon failed for login ‘%.*ls’ due to trigger execution.%.*ls
1789410Dispatcher (0x%lx) from dispatcher pool ‘%.*ls’ Worker 0x%p appears to be stuck on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
1789510sp_server_diagnostics running on Worker 0x%p appears to be non-yielding on Node %ld.
1789620The Tabular Data Stream (TDS) version 0x%x of the client library used to recover a dead connection is unsupported or unknown. The server could not recover the connection to the requested TDS version. The connection has been closed. %.*ls
1789720Session recovery feature data used in login record to open or recover a connection is structurally or semantically invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
1789816The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. Please use the client library which supports TDS Version 7.4 or higher (for example Microsoft SQL Server Native Client 11.0 or higher, ADO.NET 4.5 or higher, or Microsoft SQL Server JDBC 4.0 or higher). The connection has been closed.
1789916Login timer expired for the client connection.
1790020A network error occurred in the established connection; the connection has been closed.