SQL Server error messages list 16000 to 18000

SQL Server error messages list 16000 to 18000.

Following is the list of error messages for sql server (16000 to 18000):

error severity description
16901 16 %hs: This feature has not been implemented yet.
16902 16 %ls: The value of the parameter %ls is invalid.
16903 16 The “%ls” procedure was called with an incorrect number of parameters.
16904 16 sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE.
16905 16 The cursor is already open.
16906 17 Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more.
16907 16 %hs is not allowed in cursor statements.
16909 16 %ls: The cursor identifier value provided (%x) is not valid.
16910 16 The cursor %.*ls is currently used by another statement.
16911 16 %hs: The fetch type %hs cannot be used with forward only cursors.
16914 16 The “%ls” procedure was called with too many parameters.
16915 16 A cursor with the name ‘%.*ls’ already exists.
16916 16 A cursor with the name ‘%.*ls’ does not exist.
16917 16 Cursor is not open.
16922 16 Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
16924 16 Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
16925 16 The fetch type %hs cannot be used with dynamic cursors.
16926 16 sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
16927 16 Cannot fetch into text, ntext, and image variables.
16928 16 sp_cursor: Exec statement is not allowed as source for cursor insert.
16929 16 The cursor is READ ONLY.
16930 16 The requested row is not in the fetch buffer.
16931 16 There are no rows in the current fetch buffer.
16932 16 The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.
16933 16 The cursor does not include the table being modified or the table is not updatable through the cursor.
16934 10 Optimistic concurrency check failed. The row was modified outside of this cursor.
16935 16 No parameter values were specified for the sp_cursor-%hs statement.
16936 16 sp_cursor: One or more values parameters were invalid.
16937 16 A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
16938 16 sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
16941 16 Cursor updates are not allowed on tables opened with the NOLOCK option.
16942 16 Could not generate asynchronous keyset. The cursor has been deallocated.
16943 16 Could not complete cursor operation because the table schema changed after the cursor was declared.
16945 16 The cursor was not declared.
16946 16 Could not open the cursor because one or more of its tables have gone out of scope.
16947 16 No rows were updated or deleted.
16948 16 The variable ‘%.*ls’ is not a cursor variable, but it is used in a place where a cursor variable is expected.
16949 16 The variable ‘%.*ls’ is a cursor variable, but it is used in a place where a cursor variable is not valid.
16950 10 The variable ‘%.*ls’ does not currently have a cursor allocated to it.
16951 16 The variable ‘%.*ls’ cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure.
16952 16 A cursor variable cannot be used as a parameter to a remote procedure call.
16953 10 Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor.
16954 16 Executing SQL directly; no cursor.
16955 16 Could not create an acceptable cursor.
16956 10 The created cursor is not of the requested type.
16957 16 FOR UPDATE cannot be specified on a READ ONLY cursor.
16958 16 Could not complete cursor operation because the set options have changed since the cursor was declared.
16959 16 Unique table computation failed.
16960 16 You have reached the maximum number of cursors allowed.
16961 10 One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query.
16962 16 The target object type is not updatable through a cursor.
16963 16 You cannot specify scroll locking on a cursor that contains a remote table.
16964 16 For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
16965 16 Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch.
16966 16 %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors.
16992 16 The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue.
16996 16 %ls cannot take output parameters.
16998 16 The asynchronous cursor worktable population thread spawn failed.
16999 20 Internal Cursor Error: The cursor is in an invalid state.
17000 10 Usage: sp_autostats [, {ON|OFF} [, ] ]
17001 16 Failure to send an event notification instance of type ‘%s’ on conversation handle ‘%s’. Error Code = ‘%s’.
17002 16 Failed to post QUEUE_ACTIVATION event. Error code: ‘0x%s’.
17003 16 Closed event notification conversation endpoint with handle ‘%s’, due to the following error: ‘%.*ls’.
17004 16 Event notification conversation on dialog handle ‘%s’ closed without an error.
17005 16 Event 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.
17049 16 Unable 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 erro
17051 16 SQL Server evaluation period has expired.
17053 16 %ls: Operating system error %ls encountered.
17054 16 The current event was not reported to the Windows Events log. Operating system error = %s. You may need to clear the Windows Events log if it is full.
17056 10 The evaluation period for your edition of SQL Server expires in %d day(s).
17057 16 Security 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.
17058 16 initerrlog: Could not open error log file ‘%s’. Operating system error = %s.
17060 10 %s
17061 10 Error: %d Severity: %d State: %d %s
17063 16 Error: %d Severity: %d State: %d %s
17065 16 SQL 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
17066 16 SQL 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-m
17067 16 SQL 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 structur
17068 10 PrintStack Request
17069 10 %s
17070 16 Clustered instances are not supported on this edition of SQL Server.
17071 16 SQL Server could not start due to a boot failure. Operating system error = %s.
17101 10 (c) Microsoft Corporation.
17102 16 Failed 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.
17103 10 All rights reserved.
17104 10 Server process ID is %ld.
17105 10 Could not open master database in system task thread context. Terminating server.
17106 10 Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
17107 10 Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
17108 10 Password policy update was successful.
17109 10 FallBack certificate was successfully created.
17110 10 Registry startup parameters: %.*ls
17111 10 Logging SQL Server messages in file ‘%s’.
17112 16 An invalid startup option %c was supplied, either from the registry or the command prompt. Correct or remove the option.
17113 16 Error %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.
17114 16 Error %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.
17115 10 Command Line Startup Parameters:%.*ls
17116 16 Failed 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.
17119 10 The 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 lic
17120 16 SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
17121 10 SQL Server is started with trace flag %d, this may cause user to see some error messages masked using ‘%ls’.
17123 10 Logging to event log is disabled. Startup option ‘-%c’ is supplied, either from the registry or the command prompt.
17124 10 SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
17125 10 Using 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.
17126 10 SQL Server is now ready for client connections. This is an informational message; no user action is required.
17127 16 initdata: No memory for kernel buffer hash table.
17128 16 initdata: No memory for kernel buffers.
17129 10 initconfig: 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 n
17130 16 Not 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.
17131 16 Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
17132 16 Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory.
17133 16 Launch of startup procedure ‘%s’ failed.
17135 10 Launched startup procedure ‘%s’.
17136 10 Clearing tempdb database.
17137 10 Starting up database ‘%s’.
17138 16 Unable to allocate enough memory to start ‘%ls’. Reduce non-essential memory load or increase system memory.
17139 10 The SQL Server image was allocated using the large pages option.
17140 16 Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
17141 16 Could not register Service Control Handler. Operating system error = %s.
17142 16 SQL 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.
17143 16 %s: Could not set Service Control Status. Operating system error = %s.
17144 10 SQL 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.
17145 10 Service Control Handler received an invalid control code = %d.
17146 10 SQL 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.
17147 10 SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
17148 10 SQL Server is terminating in response to a ‘stop’ request from Service Control Manager. This is an informational message only. No user action is required.
17149 10 Using 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.
17150 10 Lock partitioning is enabled. This is an informational message only. No user action is required.
17152 10 Node 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.
17153 10 Processor 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.
17155 10 I/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.
17156 16 initeventlog: Could not initiate the EventLog Service for the key ‘%s’, last error code is %d.
17158 10 The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required.
17159 10 The server is idle. This is an informational message only. No user action is required.
17161 10 SQL 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.
17162 10 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
17163 10 SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
17164 10 Detected %d CPUs. This is an informational message; no user action is required.
17165 10 The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.
17166 10 Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
17167 10 Support 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.
17169 10 Unable 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.
17170 10 SQL 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.
17171 10 SQL Server native HTTP support failed and will not be available. ‘%hs()’ failed. Error 0x%lx.
17172 16 SNIInitialize() failed with error 0x%lx.
17173 10 Ignoring trace flag %d specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup.
17174 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
17175 10 The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
17176 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.
17177 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.
17178 10 Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
17179 10 Could not use Address Windowing Extensions because the ‘lock pages in memory’ privilege was not granted.
17180 10 SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure.
17181 16 SNIInitializeListener() failed with error 0x%lx.
17182 16 TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
17183 10 Attempting to cycle error log. This is an informational message only; no user action is required.
17184 10 The error log has been reinitialized. See the previous log for older entries.
17185 16 Unable to update password policy.
17186 16 Failed to enqueue %s task. There may be insufficient memory.
17187 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
17188 16 SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
17189 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
17190 16 Initializing the FallBack certificate failed with error code: %d, state: %d, error number: %d.
17191 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
17192 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.
17193 10 SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
17194 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
17195 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
17196 10 Preparing for eventual growth to %d GB with Hot Add Memory.
17197 16 Login 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
17198 16 Connection 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
17199 10 Dedicated 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
17200 16 Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
17201 10 Dedicated admin connection support was established for listening locally on port %d.
17202 10 Dedicated admin connection support was established for listening remotely on port %d.
17203 16 SQL 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.
17204 16 %ls: Could not open file %ls for file number %d. OS error: %ls.
17207 16 %ls: Operating system error %ls occurred while creating or opening file ‘%ls’. Diagnose and correct the operating system error, and retry the operation.
17208 16 %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.
17253 10 SQL 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.
17255 10 Secondary TempDB file ‘%.*ls’ resides on a removable drive and therefore will not be attached during startup.
17256 10 Secondary TempDB file ‘%.*ls’ will not be attached during TempDB startup; Drive check failed with error ‘%ld’.
17257 10 System error while trying to initialize disk info; Error ‘%ld’
17258 10 No free space in the TempDB database
17300 16 SQL 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 conn
17303 16 The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
17308 16 %s: Process %d generated an access violation. SQL Server is terminating this process.
17310 20 A 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.
17311 16 SQL 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. Th
17312 16 SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
17313 10 Unable 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.
17401 10 Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required.
17403 10 Server resumed execution after being idle %d seconds. Reason: timer event.
17404 10 The server resumed execution after being idle for %d seconds.
17405 24 An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
17406 10 Server resumed execution after being idle %d seconds. Reason: resource pressure.
17407 10 SQL Server has initialized support for the advanced user mode scheduling. This is an informational message; no user action is required.
17550 10 DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17551 10 DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17557 16 DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
17558 10 Bypassing recovery for database ID %d. This is an informational message only. No user action is required.
17560 10 DBCC DBREPAIR: ‘%ls’ index restored for ‘%ls.%ls’.
17561 10 %ls index restored for %ls.%ls.
17572 16 DBCC cannot free DLL ‘%ls’. SQL Server requires this DLL in order to function properly.
17573 10 CHECKDB for database ‘%ls’ finished without errors on %ls (local time). This is an informational message only; no user action is required.
17656 10 Warning ******************
17657 10 Attempting to change default collation to %s.
17658 10 SQL Server started in single-user mode. This an informational message only. No user action is required.
17659 10 Warning: 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.
17660 10 Starting without recovery. This is an informational message only. No user action is required.
17661 10 Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
17663 10 Server name is ‘%s’. This is an informational message only. No user action is required.
17664 10 The NETBIOS name of the local node that is running the server is ‘%ls’. This is an informational message only. No user action is required.
17674 10 Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
17676 10 SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.
17681 10 Loading default collation %s for this instance of SQL Server.
17750 16 Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls.
17751 16 Could not find the function %ls in the library %ls. Reason: %ls.
17752 16 SQL Server has insufficient memory to run the extended stored procedure ‘%ls’. Release server memory resources by closing connections or ending transactions.
17753 16 %.*ls can only be executed in the master database.
17802 20 The 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
17803 20 There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
17805 20 The 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
17806 20 SSPI handshake failed with error code 0x%x, state %d while establishing a connection with integrated security; the connection has been closed. Reason: %.*ls %.*ls.
17807 20 Event ‘%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.
17809 20 Could 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
17810 20 Could 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.%.*
17812 10 Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required.
17813 20 The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
17825 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.
17826 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.
17827 20 There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
17828 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
17829 20 A network error occurred while establishing a connection; the connection has been closed.%.*ls
17830 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 r
17832 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
17835 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
17836 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
17881 16 ‘%ls’ is an unsupported Open Data Services API.
17883 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.
17884 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
17885 16 An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
17886 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
17887 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.
17888 10 All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
17889 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
17890 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%%.
17891 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.
17892 20 Logon failed for login ‘%.*ls’ due to trigger execution.%.*ls
17894 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.

sql server error list 16000 to 18000
sql server error list error codes 16000 to 18000
sql server error numbers 16000 to 18000
sql server error list 2005 16000 to 18000
sql server error list 2008 16000 to 18000
sql server 2008 error message list 16000 to 18000
sql server errors logs
sql server errors list table

(Visited 748 times, 1 visits today)