Web.QHMIT.com

SQL Server System Errors: 17000 - 17999

List of error messages between 17000 and 17999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text
17000100Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ]
17001161Failure to send an event notification instance of type '%s' on conversation handle '%s'. Error Code = '%s'.
17002161Failed to post QUEUE_ACTIVATION event. Error code: '0x%s'.
17003161Closed event notification conversation endpoint with handle '%s', due to the following error: '%.*ls'.
17004161Event notification conversation on dialog handle '%s' closed without an error.
17005161Event 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.
17049161Unable 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."
17051161SQL Server evaluation period has expired.
17053161%ls: Operating system error %ls encountered.
17054161The 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.
17056101The evaluation period for your edition of SQL Server expires in %d day(s).
17057161Security 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.
17058161initerrlog: Could not open error log file '%s'. Operating system error = %s.
17060101%s
17061101Error: %d Severity: %d State: %d %s
17063161Error: %d Severity: %d State: %d %s
17065161SQL 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.
17066161SQL 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.
17067161SQL 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.
17068100PrintStack Request
17069101%s
17070161Clustered instances are not supported on this edition of SQL Server.
17071161SQL Server could not start due to a boot failure. Operating system error = %s.
17072171The Extended Event session could not be created.
17073161Executing 'sp_server_diagnostics' stored procedure in repeat mode with 'insert into' clause is not allowed.
17074161Assertion "%ls" with message "%ls" at <%ls>:%ld failed.
17075161Assertion "%ls" at <%ls>:%ld failed.
17076211Error spawning System Health Monitor thread: %ls
17101101(c) Microsoft Corporation.
17102161Failed 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.
17103101All rights reserved.
17104101Server process ID is %ld.
17105101Could not open master database in system task thread context. Terminating server.
17106101Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
17107100Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
17108101Password policy update was successful.
17109101FallBack certificate was successfully created.
17110101Registry startup parameters: %.*ls
17111101Logging SQL Server messages in file '%s'.
17112161An invalid startup option '%s' was supplied, either from the registry or the command prompt. Correct or remove the option.
17113161Error %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.
17114161Error %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.
17115101Command Line Startup Parameters:%.*ls
17116161Failed 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.
17117101The tempdb database has %ld data file(s).
17118101Database 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.
17119101The 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.
17120161SQL Server could not spawn %s thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
17121101SQL Server is started with trace flag %d, this may cause user to see some error messages masked using '%ls'.
17122101Trace flag %d is discontinued. Use the options provided with ALTER DATABASE.
17123101Logging to event log is disabled. Startup option '-%c' is supplied, either from the registry or the command prompt.
17124101SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
17125101Using 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.
17126101SQL Server is now ready for client connections. This is an informational message; no user action is required.
17127161initdata: No memory for kernel buffer hash table.
17128161initdata: No memory for kernel buffers.
17129101initconfig: 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.
17130161Not 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.
17131161Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
17132161Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory.
17133161Launch of startup procedure '%s' failed.
17134101The 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.
17135101Launched startup procedure '%s'.
17136101Clearing tempdb database.
17137101Starting up database '%.*ls'.
17138161Unable to allocate enough memory to start '%ls'. Reduce non-essential memory load or increase system memory.
17139101The SQL Server image %ls was allocated using the large pages option.
17140161Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
17141161Could not register Service Control Handler. Operating system error = %s.
17142161SQL 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.
17143161%s: Could not set Service Control Status. Operating system error = %s.
17144101SQL 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.
17145101Service Control Handler received an invalid control code = %d.
17146101SQL 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.
17147101SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
17148101SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
17149101Using 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.
17150101Lock partitioning is enabled. This is an informational message only. No user action is required.
17152101Node 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.
17153101Processor 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.
17155101I/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.
17156161initeventlog: Could not initiate the EventLog Service for the key '%s', last error code is %d.
17158101The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required.
17159101The server is idle. This is an informational message only. No user action is required.
17161101SQL 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.
17162101SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
17163101SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
17164101SQL 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.
17165101The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.
17166101Initializing Microsoft Distributed Transaction Coordinator (MS DTC) resource manager [%ls] for server instance %ls. This is an informational message only. No user action is required.
17167101Support 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.
17169101Unable 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.
17170101SQL 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.
17171101SQL Server native HTTP support failed and will not be available. '%hs()' failed. Error 0x%lx.
17172161SNIInitialize() failed with error 0x%lx.
17173101Ignoring trace flag %u specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup.
17174101Unable 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.
17175101The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
17176101This 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.
17177101This 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.
17181161SNIInitializeListener() failed with error 0x%lx.
17182161TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
17183101Attempting to cycle error log. This is an informational message only; no user action is required.
17184101The error log has been reinitialized. See the previous log for older entries.
17185161Unable to update password policy.
17186161Failed to enqueue %s task. There may be insufficient memory.
17187161SQL 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
17188161SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
17189161SQL 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
17190161Initializing the FallBack certificate failed with error code: %d, state: %d, error number: %d.
17191161Cannot 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
17192101Dedicated 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.
17193101SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
17194161The 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
17195161The 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".
17196101Preparing for eventual growth to %d GB with Hot Add Memory.
17197161Login 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
17198161Connection 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
17199101Dedicated 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.
17200161Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
17201101Dedicated admin connection support was established for listening locally on port %d.
17202101Dedicated admin connection support was established for listening remotely on port %d.
17203161SQL 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.
17204161%ls: Could not open file %ls for file number %d. OS error: %ls.
17205101File %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.
17207161%ls: Operating system error %ls occurred while creating or opening file '%ls'. Diagnose and correct the operating system error, and retry the operation.
17208161%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.
17253101SQL 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.
17255101Secondary TempDB file '%.*ls' resides on a removable drive and therefore will not be attached during startup.
17256101Secondary TempDB file '%.*ls' will not be attached during TempDB startup; Drive check failed with error '%ld'.
17257101System error while trying to initialize disk info; Error '%ld'
17258101No free space in the TempDB database
17259101Dedicated admin connection support was established for listening locally on named pipe [ %s ].
17260101Dedicated admin connection support was established for listening remotely on named pipe [ %s ].
17300161SQL 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.
17303161The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
17308161%s: Process %d generated an access violation. SQL Server is terminating this process.
17310201A 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.
17311161SQL 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).
17312161SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
17313101Unable 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.
17401101Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required.
17403101Server resumed execution after being idle %d seconds. Reason: timer event.
17404101The server resumed execution after being idle for %d seconds.
17405241An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
17406101Server resumed execution after being idle %d seconds. Reason: resource pressure.
17407101The automatic soft-NUMA is already set to '%S_MSG'. No further action is necessary.
17408101The automatic soft-NUMA configuration has been set to '%S_MSG'. Restart SQL server for the new setting to take effect.
17409101Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than %lu physical cores.
17410101Automatic 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.
17550101DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17551101DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17557161DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
17558101Bypassing recovery for database ID %d. This is an informational message only. No user action is required.
17560101DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'.
17561101%ls index restored for %ls.%ls.
17572161DBCC cannot free DLL '%ls'. SQL Server requires this DLL in order to function properly.
17573101CHECKDB for database '%ls' finished without errors on %ls (local time). This is an informational message only; no user action is required.
17656101Warning ******************
17657101Attempting to change default collation to %s.
17658101SQL Server started in single-user mode. This an informational message only. No user action is required.
17659101Warning: 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.
17660101Starting without recovery. This is an informational message only. No user action is required.
17661101Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
17663101Server name is '%s'. This is an informational message only. No user action is required.
17664101The NETBIOS name of the local node that is running the server is '%ls'. This is an informational message only. No user action is required.
17674101Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
17676101SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.
17750161Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls.
17751161Could not find the function %ls in the library %ls. Reason: %ls.
17752161SQL Server has insufficient memory to run the extended stored procedure '%ls'. Release server memory resources by closing connections or ending transactions.
17753160%.*ls can only be executed in the master database.
17802201The 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
17803201There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
17805201The 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
17806201SSPI 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
17807201Event '%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.
17809201Could 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
17810201Could 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
17811101The maximum number of dedicated administrator connections for this instance is '%ld'
17812101Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required.
17813201The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
17816200Login to remote SQL Server failed with error %d: %.*ls
17817200Unsupport login ack packet response received when opening client connection.%.*ls
17818200Connection to remote SQL Server failed with error %d.
17825181Could 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.
17826181Could 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.
17827201There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
17828201The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17829201A network error occurred while establishing a connection; the connection has been closed.%.*ls
17830201Network 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
17832201The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17835201Encryption 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
17836201Length 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
17881161'%ls' is an unsupported Open Data Services API.
17883101Process %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.
17884101New 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%%.
17885160An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
17886201The 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.
17887101IO 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.
17888101All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
17889161A 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
17890101A 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%%.
17891101Resource 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.
17892201Logon failed for login '%.*ls' due to trigger execution.%.*ls
17894101Dispatcher (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.
17895101sp_server_diagnostics running on Worker 0x%p appears to be non-yielding on Node %ld.
17896201The 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
17897201Session 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
17898161The 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.
17899161Login timer expired for the client connection.
17900201A network error occurred in the established connection; the connection has been closed.