错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 10 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 16943 — Could not complete cursor operation because the table schema changed after the cursor was declared.
- 16945 — The cursor was not declared.
- 16946 — Could not open the cursor because one or more of its tables have gone out of scope.
- 16947 — No rows were updated or deleted.
- 16948 — The variable '%.*ls' is not a cursor variable, but it is used in a place where a cursor variable is expected.
- 16949 — The variable '%.*ls' is a cursor variable, but it is used in a place where a cursor variable is not valid.
- 16950 — The variable '%.*ls' does not currently have a cursor allocated to it.
- 16951 — 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 pr…
- 16952 — A cursor variable cannot be used as a parameter to a remote procedure call.
- 16953 — Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isola…
- 16954 — Executing SQL directly; no cursor.
- 16955 — Could not create an acceptable cursor.
- 16956 — The created cursor is not of the requested type.
- 16957 — FOR UPDATE cannot be specified on a READ ONLY cursor.
- 16958 — Could not complete cursor operation because the set options have changed since the cursor was declared.
- 16959 — Unique table computation failed.
- 16960 — You have reached the maximum number of cursors allowed.
- 16961 — One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query.
- 16962 — The target object type is not updatable through a cursor.
- 16963 — You cannot specify scroll locking on a cursor that contains a remote table.
- 16964 — For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
- 16965 — Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch.
- 16966 — %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static …
- 16992 — The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to l…
- 16996 — %ls cannot take output parameters.
- 16998 — The asynchronous cursor worktable population thread spawn failed.
- 16999 — Internal Cursor Error: The cursor is in an invalid state.
- 17000 — Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ]
- 17001 — Failure to send an event notification instance of type '%s' on conversation handle '%s'. Error Code = '%s'.
- 17002 — Failed to post QUEUE_ACTIVATION event. Error code: '0x%s'.
- 17003 — Closed event notification conversation endpoint with handle '%s', due to the following error: '%.*ls'.
- 17004 — Event notification conversation on dialog handle '%s' closed without an error.
- 17005 — Event notification '%ls' in database '%ls' dropped due to send time service broker errors. Check to ensure the conversation handle, service broker con…
- 17049 — 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…
- 17051 — SQL Server evaluation period has expired.
- 17053 — %ls: Operating system error %ls encountered.
- 17054 — The current event was not reported to the operating system error log. Operating system error = %s. You may need to clear the operating system error lo…
- 17056 — The evaluation period for your edition of SQL Server expires in %d day(s).
- 17057 — Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer t…
- 17058 — initerrlog: Could not open error log file '%s'. Operating system error = %s.
- 17060 — %s
- 17061 — Error: %d Severity: %d State: %d %s
- 17063 — Error: %d Severity: %d State: %d %s
- 17065 — SQL Server Assertion: File: <%s>, line = %d Failed Assertion = '%s' %s. This error may be timing-related. If the error persists after rerunning the st…
- 17066 — SQL Server Assertion: File: <%s>, line=%d Failed Assertion = '%s'. This error may be timing-related. If the error persists after rerunning the stateme…
- 17067 — SQL Server Assertion: File: <%s>, line = %d %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKD…
- 17068 — PrintStack Request
- 17069 — %s
- 17070 — Clustered instances are not supported on this edition of SQL Server.
- 17071 — SQL Server could not start due to a boot failure. Operating system error = %s.
- 17072 — The Extended Event session could not be created.
- 17073 — Executing 'sp_server_diagnostics' stored procedure in repeat mode with 'insert into' clause is not allowed.
- 17074 — Assertion "%ls" with message "%ls" at <%ls>:%ld failed.
- 17075 — Assertion "%ls" at <%ls>:%ld failed.
- 17076 — Error spawning System Health Monitor thread: %ls
- 17077 — Error spawning Heartbeat Monitor thread: %ls
- 17101 — (c) Microsoft Corporation.
- 17102 — Failed to initialize Distributed COM (CoInitializeEx returned %lx). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM conf…
- 17103 — All rights reserved.
- 17104 — Server process ID is %ld.
- 17105 — Could not open master database in system task thread context. Terminating server.
- 17106 — Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
- 17107 — Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
- 17108 — Password policy update was successful.
- 17109 — FallBack certificate was successfully created.
- 17110 — Registry startup parameters: %.*ls
- 17111 — Logging SQL Server messages in file '%s'.
- 17112 — An invalid startup option '%s' was supplied, either from the registry or the command prompt. Correct or remove the option.
- 17113 — Error %ls occurred while opening file '%ls' to obtain configuration information at startup. An invalid startup option might have caused the error. Ver…
- 17114 — Error %ls occurred while opening file '%ls' to obtain configuration information at startup time. An invalid startup option might have caused the error…
- 17115 — Command Line Startup Parameters:%.*ls
- 17116 — Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configurati…
- 17117 — The tempdb database has %ld data file(s).
- 17118 — Database Instant File Initialization: %S_MSG. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL …
- 17119 — 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 me…
- 17120 — SQL Server could not spawn %s thread. Check the SQL Server error log and the operating system error log for information about possible related problem…
- 17121 — SQL Server is started with trace flag %d, this may cause user to see some error messages masked using '%ls'.
- 17122 — Trace flag %d is discontinued. Use the options provided with ALTER DATABASE.
- 17123 — Logging to event log is disabled. Startup option '-%c' is supplied, either from the registry or the command prompt.
- 17124 — SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
- 17125 — Using dynamic lock allocation. Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No…
- 17126 — SQL Server is now ready for client connections. This is an informational message; no user action is required.
- 17127 — initdata: No memory for kernel buffer hash table.
- 17128 — initdata: No memory for kernel buffers.
- 17129 — initconfig: Warning: affinity specified is not valid. Defaulting to no affinity. Use ALTER SERVER CONFIGURATION SET PROCESS AFFINITY to configure the …
- 17130 — Not enough memory for the configured number of locks. Attempting to start with a smaller lock hash table, which may impact performance. Contact the da…
- 17131 — Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
- 17132 — Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory.
- 17133 — Launch of startup procedure '%s' failed.
- 17134 — The tempdb database data files are not configured with the same initial size and autogrowth settings. To reduce potential allocation contention, the i…
- 17135 — Launched startup procedure '%s'.
- 17136 — Clearing tempdb database.
- 17137 — Starting up database '%.*ls'.
- 17138 — Unable to allocate enough memory to start '%ls'. Reduce non-essential memory load or increase system memory.
- 17139 — The SQL Server image %ls was allocated using the large pages option.
- 17140 — Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
- 17141 — Could not register Service Control Handler. Operating system error = %s.
- 17142 — 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…
- 17143 — %s: Could not set Service Control Status. Operating system error = %s.
- 17144 — SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, use SQL Computer Manager or t…
- 17145 — Service Control Handler received an invalid control code = %d.
- 17146 — SQL Server is allowing new connections in response to 'continue' request from Service Control Manager. This is an informational message only. No user …
- 17147 — SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
- 17148 — SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is requi…
- 17149 — Using the static lock allocation specified in the locks configuration option. Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node. This i…
- 17150 — Lock partitioning is enabled. This is an informational message only. No user action is required.
- 17152 — 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 …
- 17153 — Processor affinity turned on: node %d, processor mask 0x%0*I64x. Threads will execute on CPUs per affinity settings. This is an informational message;…
- 17155 — 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 infor…
- 17156 — initeventlog: Could not initiate the EventLog Service for the key '%s', last error code is %d.
- 17158 — The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required.
- 17159 — The server is idle. This is an informational message only. No user action is required.
- 17161 — 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 wi…
- 17162 — SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
- 17163 — SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
- 17164 — SQL Server detected %d sockets with %d cores per socket and %d logical processors per socket, %d total logical processors; using %d logical processors…
- 17165 — The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.
- 17166 — Initializing Microsoft Distributed Transaction Coordinator (MS DTC) resource manager [%ls] for server instance %ls. This is an informational message o…
- 17167 — Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration o…
- 17169 — 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 s…
- 17170 — 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 requi…
- 17171 — SQL Server native HTTP support failed and will not be available. '%hs()' failed. Error 0x%lx.
- 17172 — SNIInitialize() failed with error 0x%lx.
- 17173 — Ignoring trace flag %u specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup.
- 17174 — 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 …
- 17175 — The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
- 17176 — 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 re…
- 17177 — 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 requ…
- 17178 — Warning: Enterprise Server/CAL license used for this instance. This edition limits SQL Engine CPU utilization to 20 physical cores, or 40 logical core…
- 17179 — SQL Server detected %d sockets with %d cores per socket and %d logical processors per socket, %d total logical processors; using %d logical processors…
- 17181 — SNIInitializeListener() failed with error 0x%lx.
- 17182 — TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
- 17183 — Attempting to cycle error log. This is an informational message only; no user action is required.
- 17184 — The error log has been reinitialized. See the previous log for older entries.
- 17185 — Unable to update password policy.
- 17186 — Failed to enqueue %s task. There may be insufficient memory.
- 17187 — 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 in…
- 17188 — SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
- 17189 — 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 operating system…
- 17190 — Initializing the FallBack certificate failed with error code: %d, state: %d, error number: %d.
- 17191 — 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…
- 17192 — Dedicated admin connection support was not started because of error 0x%lx, status code: 0x%lx. This error typically indicates a socket-based error, su…
- 17193 — SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
- 17194 — 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 seque…
- 17195 — The server was unable to complete its initialization sequence because the available network libraries do not support the required level of encryption.…
- 17196 — Preparing for eventual growth to %d GB with Hot Add Memory.
- 17197 — 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.…
- 17198 — Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attemp…
- 17199 — Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated admini…
- 17200 — Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
- 17201 — Dedicated admin connection support was established for listening locally on port %d.
- 17202 — Dedicated admin connection support was established for listening remotely on port %d.
- 17203 — 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 Sys…
- 17204 — %ls: Could not open file %ls for file number %d. OS error: %ls.
- 17205 — File %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 …
- 17206 — File %ls, file number %d for dbid %d is successfully mapped for use by Hybrid Buffer Pool.
- 17207 — %ls: Operating system error %ls occurred while creating or opening file '%ls'. Diagnose and correct the operating system error, and retry the operatio…
- 17208 — %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 bac…
- 17209 — File %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.
- 17253 — 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 …
- 17255 — Secondary TempDB file '%.*ls' resides on a removable drive and therefore will not be attached during startup.
- 17256 — Secondary TempDB file '%.*ls' will not be attached during TempDB startup; Drive check failed with error '%ld'.
- 17257 — System error while trying to initialize disk info; Error '%ld'
- 17258 — No free space in the TempDB database
- 17259 — Dedicated admin connection support was established for listening locally on named pipe [ %s ].
- 17260 — Dedicated admin connection support was established for listening remotely on named pipe [ %s ].
- 17261 — initdata: No shared memory for kernel buffers.
- 17262 — Replicated master not available for server state initialization during startup.
- 17263 — Contained availability group master database not available for server state initialization during startup.
- 17264 — CPU vectorization level(s) detected: %ls
- 17300 — 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 a…
- 17303 — The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support …
- 17305 — SQL server is started in a safe boot mode. No new connections can be created. This is informational message.
- 17306 — Failed to exit safe mode either becuase we are not in safe mode or due to an error.
- 17307 — Failed to boot database in safe mode.
- 17308 — %s: Process %d generated an access violation. SQL Server is terminating this process.
- 17310 — A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services wit…
- 17311 — 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 e…
- 17312 — SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
- 17313 — 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 dr…
- 17401 — Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is requ…
- 17403 — Server resumed execution after being idle %d seconds. Reason: timer event.
- 17404 — The server resumed execution after being idle for %d seconds.
- 17405 — An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log fo…
- 17406 — Server resumed execution after being idle %d seconds. Reason: resource pressure.
- 17407 — The automatic soft-NUMA is already set to '%S_MSG'. No further action is necessary.
- 17408 — The automatic soft-NUMA configuration has been set to '%S_MSG'. Restart SQL server for the new setting to take effect.
- 17409 — Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than %lu physical cores.
- 17410 — Automatic soft-NUMA was not enabled, because 'NodeConfiguration' key was detected in the registry at path '%ls'. Disable registry based soft-NUMA conf…
- 17411 — Hardware offload configuration hasn't changed. Current configuration (0x%x) and mode (0x%x). No action required.
- 17412 — Hardware offload configuration has changed. Current configuration (0x%x) and mode (0x%x). New configuration (0x%x) and mode (0x%x). Restart SQL Server…
- 17413 — Loading accelerator library %.*ls failed with error 0x%x.
- 17414 — Retrieving the address of an exported function %.*ls in accelerator library %.*ls failed with error 0x%x.
- 17415 — %.*ls component enumeration failed with zero component count.
- 17416 — %.*ls component enumeration failed with mismatch in component count.
- 17417 — %.*ls %.*ls not compatible with SQL Server.
- 17418 — Detected %.*ls %.*ls.
- 17419 — %.*ls hardware detected on the system.
- 17420 — %.*ls hardware not found on the system.
- 17431 — %.*ls initialization failed with error %d.
- 17432 — %.*ls initialization succeeded.
- 17433 — %.*ls session creation failed with error %d.
- 17434 — %.*ls session successfully created.
- 17435 — %.*ls will be used in hardware mode.
- 17436 — This edition of SQL Server supports only software mode. %.*ls will be used in software mode.
- 17437 — %.*ls will be used in software mode.
- 17438 — %.*ls session alive check failed with error %d.
- 17439 — %.*ls session tear down failed with error %d.
- 17440 — %.*ls session close failed with error %d.
- 17441 — This operation requires %.*ls libraries to be loaded.
- 17442 — SQL Server detected the following NUMA node configuration (NUMA Node number %d, Processor Group number %d, CPU Mask 0x%0*I64x).
- 17443 — SOS Boot failed during stage: %ls.
- 17444 — SQL Server has been configured for lightweight pooling. Lightweight pooling is deprecated and will be removed in a future SQL Server version. For more…
- 17445 — CallExternalAPI protector setup failed.
- 17446 — Loading winaccel/os accelerator library %.*ls failed with error 0x%x.
- 17550 — DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
- 17551 — DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
- 17557 — DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
- 17558 — Bypassing recovery for database ID %d. This is an informational message only. No user action is required.
- 17560 — DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'.
- 17561 — %ls index restored for %ls.%ls.
- 17572 — DBCC cannot free DLL '%ls'. SQL Server requires this DLL in order to function properly.
- 17573 — CHECKDB for database '%ls' finished without errors on %ls (local time). This is an informational message only; no user action is required.
- 17656 — Warning ******************
- 17657 — Attempting to change default collation to %s.
- 17658 — SQL Server started in single-user mode. This an informational message only. No user action is required.
- 17659 — 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 restart…
- 17660 — Starting without recovery. This is an informational message only. No user action is required.
- 17661 — Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
- 17663 — Server name is '%s'. This is an informational message only. No user action is required.
- 17664 — 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 — Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
- 17676 — SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.
- 17681 — Loading default collation %s for this instance of SQL Server.
- 17750 — Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls.
- 17751 — Could not find the function %ls in the library %ls. Reason: %ls.
- 17752 — SQL Server has insufficient memory to run the extended stored procedure '%ls'. Release server memory resources by closing connections or ending transa…
- 17753 — %.*ls can only be executed in the master database.
- 17802 — 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…
- 17803 — There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has …
- 17805 — 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…
- 17806 — SSPI handshake failed with error code 0x%x, state %d while establishing a connection with integrated security; the connection has been closed. Reason:…
- 17807 — 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 conne…
- 17809 — Could not connect because the maximum number of '%ld' user connections has already been reached. The system administrator can use sp_configure to incr…
- 17810 — Could not connect because the maximum number of '%ld' dedicated administrator connections already exists. Before a new connection can be made, the exi…
- 17811 — The maximum number of dedicated administrator connections for this instance is '%ld'
- 17812 — Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required.
- 17813 — The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
- 17816 — Login to remote SQL Server failed with error %d: %.*ls
- 17817 — Unsupport login ack packet response received when opening client connection.%.*ls
- 17818 — Connection to remote SQL Server failed with error %d.
- 17819 — The SQL Server or the endpoint is configured to accept only strict (TDS 8.0 and above) connections. The connection has been closed.
- 17821 — A valid TLS certificate is not configured to accept strict (TDS 8.0 and above) connections. The connection has been closed.
- 17825 — 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: t…
- 17826 — Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately precedi…
- 17827 — There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
- 17828 — The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client libra…
- 17829 — A network error occurred while establishing a connection; the connection has been closed.%.*ls
- 17830 — 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 …
- 17832 — The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.…
- 17835 — Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade yo…
- 17836 — 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…
- 17881 — '%ls' is an unsupported Open Data Services API.
- 17883 — 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…
- 17884 — 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 con…
- 17885 — An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
- 17886 — 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 …
- 17887 — 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 — All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
- 17889 — A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this sessio…
- 17890 — A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (K…
- 17891 — 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. A…
- 17892 — Logon failed for login '%.*ls' due to trigger execution.%.*ls
- 17893 — Failed to get client host address while preparing to execute LOGON triggers.
- 17894 — 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, I…
- 17895 — sp_server_diagnostics running on Worker 0x%p appears to be non-yielding on Node %ld.
- 17896 — The 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 rec…
- 17897 — Session recovery feature data used in login record to open or recover a connection is structurally or semantically invalid; the connection has been cl…
- 17898 — The 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 …
- 17899 — Login timer expired for the client connection.
- 17900 — A network error occurred in the established connection; the connection has been closed.
- 18002 — Exception happened when running extended stored procedure '%.*ls' in the library '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; E…
- 18052 — Error: %d, Severity: %d, State: %d.
- 18053 — Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifica…
- 18054 — Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure …
- 18055 — Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, th…
- 18056 — The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been cau…
- 18057 — Error: Failed to set up execution context.
- 18058 — Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and…
- 18059 — The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connecti…
- 18060 — Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the message.
- 18061 — The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since…
- 18062 — Transaction priority: cleared a stale session execution-context (SETLS) pointer on SPID %d during connection context teardown. This is an internal sel…
- 18100 — Process ID %d was killed by hostname %.*ls, host process ID %d.
- 18113 — SQL Server shutdown after verifying system indexes.
- 18124 — The default collation was successfully changed.
- 18126 — Engine failed to load configuration for error detection, default configuration was applied.
- 18127 — Engine is marking DB %d [%.*ls] as SUSPECT in cloud DB mode due to error %d, severity %d, state %d.
- 18204 — %s: Backup device '%s' failed to %s. Operating system error %s.
- 18210 — %s: %s failure on backup device '%s'. Operating system error %s.
- 18225 — Tape '%s' (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required
- 18226 — Tape mount is being requested on drive '%s'. Expected volume has (Family ID %d, sequence %d).
- 18227 — Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action requi…
- 18228 — Tape mount request on drive '%s' is cancelled. This is an informational message only. No user action is required.
- 18257 — %s: Device or media does not support %s. To access this feature, use a different device or media.
- 18264 — Database backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, number of dump devices: %d, device in…
- 18265 — Log was backed up. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This …
- 18266 — Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device infor…
- 18267 — Database was restored: Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). I…
- 18268 — Log was restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This i…
- 18269 — Database file was restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is …
- 18270 — Database differential changes were backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, full backup…
- 18271 — Database changes were restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information…
- 18272 — During restore restart, an I/O error occurred on checkpoint file '%s' (operating system error %s). The statement is proceeding but cannot be restarted…
- 18273 — Could not clear '%s' bitmap in database '%s' because of error %d. As a result, the differential or bulk-logged bitmap overstates the amount of change …
- 18274 — Tape '%s' was dismounted from drive '%s'. This is an informational message. No user action is required.
- 18275 — Unnamed tape was dismounted from drive '%s'. This is an informational message. No user action is required.
- 18276 — Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump dev…
- 18277 — Database file changes were restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s).…
- 18279 — During a RESTORE operation, an I/O error occurred on checkpoint file '%s' (operating system error %s). Ensure that a valid storage location exists for…
- 18280 — The file %s is being removed from the database, but is not being removed from the filesystem because file snapshots are still associated with the file…
- 18300 — Reason: Infrastructure error occurred. Check for previous errors.
- 18301 — Reason: Could not find a login matching the name provided.
- 18302 — Reason: Failed to unprotect memory containing sensitive information.
- 18303 — Reason: Failed to unprotect memory containing sensitive information.
- 18304 — Reason: Could not find a login matching the name provided.
- 18305 — Reason: Attempting to use an NT account name with SQL Server Authentication.
- 18306 — Reason: An error occurred while evaluating the password.
- 18307 — Reason: Password did not match that for the login provided.
- 18308 — Reason: Invalid password provided.
- 18309 — Reason: Password validation failed with an infrastructure error. Check for previous errors.
- 18310 — Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.
- 18311 — Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors.
- 18312 — Reason: SQL Server service is paused. No new connections can be accepted at this time.
- 18313 — Reason: Interface for login to SQL Server is not supported.
- 18314 — Reason: Failed to open the specified database.
- 18315 — Reason: Failed to open the database for this login.
- 18316 — Reason: Unable to determine the initial language and date format.
- 18317 — Reason: The user must change the password, but it cannot be changed with the current connection settings.
- 18318 — Reason: Failed to unprotect memory containing sensitive information.
- 18319 — Reason: Simulation of a failure while redoing login on the connection.
- 18320 — Reason: SQL Server service is paused. Login could not be revalidated at this time.
- 18321 — Reason: Reinitialization of security context failed while revalidating the login on the connection.
- 18322 — Reason: Access to server validation failed while revalidating the login on the connection.
- 18323 — Reason: Failed to open the specified database while revalidating the login on the connection.
- 18324 — Reason: Failed to create the user instance while revalidating the login on the connection.
- 18325 — Reason: Failed to attach the specified database while revalidating the login on the connection.
- 18326 — Reason: Failed to open the database for this login while revalidating the login on the connection.
- 18327 — Reason: Failed to determine the language and date format while revalidating the login on the connection.
- 18328 — Reason: An exception was raised while revalidating the login on the connection. Check for previous errors.
- 18329 — Reason: Simulation of a failure while reauthenticating login.
- 18330 — Reason: SQL Server service is paused. Login cannot be reauthenticated at this time.
- 18331 — Reason: Failed to reinitialize security context while reauthenticating login.
- 18332 — Reason: Failed to access server for validation while reauthenticating login.
- 18333 — Reason: Failed to open the specified database while reauthenticating login.
- 18334 — Reason: An error occurred while reauthenticating login. Check for previous errors.
- 18335 — Reason: Could not retrieve database name or map database to an item.
- 18336 — Reason: Cannot connect with a login that does not specify a share.
- 18337 — Reason: Failed to open the explicitly specified database '%.*ls'.
- 18338 — Reason: Unable to determine the database name from the specified file name.
- 18339 — Reason: Failed to open the database '%.*ls' specified in the login properties.
- 18340 — Reason: Failed to store database name and collation. Check for previous errors.
- 18341 — . Reason: Current collation did not match the database's collation during connection reset.
- 18342 — Reason: Failed to send an environment change notification to a log shipping partner node.
- 18343 — Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection.
- 18344 — Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection.
- 18345 — Reason: Failed to open the database '%.*ls' configured in the login object while revalidating the login on the connection.
- 18346 — Reason: Failed to determine database name from a given file name while revalidating the login on the connection.
- 18347 — Reason: Failed to open the database '%.*ls' specified in the login properties while revalidating the login on the connection.
- 18348 — Reason: Failed to store database name and collation while revalidating the login on the connection. Check for previous errors.
- 18349 — Reason: Current collation did not match the database's collation during connection reset.
- 18350 — Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login.
- 18351 — Reason: Client impersonation failed.
- 18352 — Reason: Failed to revert impersonation to self.
- 18353 — Reason: Failed to get security token information.
- 18354 — Reason: Failed to duplicate of security token.
- 18355 — Reason: Failed attempted retry of a process token validation.
- 18356 — Reason: An error occurred while attempting to change password.
- 18357 — Reason: An attempt to login using SQL authentication failed. Server is configured for Integrated authentication only.
- 18358 — Reason: Could not find a user matching the name provided. [Database: '%.*ls']
- 18359 — Reason: Failed to unprotect memory containing sensitive information. [Database: '%.*ls']
- 18360 — Reason: Failed to unprotect memory containing sensitive information. [Database: '%.*ls']
- 18361 — Reason: Could not find a user matching the name provided. [Database: '%.*ls']
- 18362 — Reason: Attempting to use an invalid user type with SQL Server Authentication. [Database: '%.*ls']
- 18363 — Reason: An error occurred while evaluating the password. [Database: '%.*ls']
- 18364 — Reason: Password did not match that for the user provided. [Database: '%.*ls']
- 18365 — Reason: Invalid password provided. [Database: '%.*ls']
- 18366 — Reason: Password validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
- 18367 — Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
- 18368 — Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. [Database: '%.*ls']
- 18369 — attach
- 18370 — restore
- 18371 — Reason: The password hash is from an unsupported version of SQL Server. Reset the password or recreate the login.
- 18372 — Reason: An error occurred while obtaining a routing environment change notification.
- 18373 — Reason: Database could not accept user connections at this time.
- 18374 — Reason: An error occurred while recovering the Identity_Insert session state requested by the recovery login.
- 18375 — Reason: Failed to open the database '%.*ls' configured in the session recovery object while recovering the connection.
- 18376 — Reason: Failed to open the database '%.*ls' configured in the session recovery object while revalidating the login on the recovered connection.
- 18377 — Reason: The current collation did not match the database's collation as indicated by session recovery object in login.
- 18378 — Reason: An error occurred while recovering the @@identity session state requested by the recovery login.
- 18379 — Reason: The account is currently locked out. The system administrator can unlock it.
- 18380 — Reason: The certificate is invalid or expired.
- 18381 — Reason: The logical master database was not found.
- 18382 — Reason: Unable to retrieve client IP Address.
- 18383 — Reason: The client was blocked by the firewall.
- 18384 — Reason: Unable to open the logical master database.
- 18385 — Reason: Unable to connect to logical master database.
- 18386 — Reason: Remote authentication failed.
- 18387 — Reason: The DosGuard had an error while checking a connection.
- 18388 — Reason: The DosGuard rejected the connection.
- 18389 — Reason: Unable to retrieve server firewall rules.
- 18390 — Reason: An unknown error occurred while attempting to authenticate the user.
- 18391 — Reason: The login to SQL Azure DB failed due to empty username.
- 18392 — Reason: The login to SQL Azure DB failed due to empty password.
- 18393 — Reason: The login to SQL Azure DB failed due to empty password when using PreTDS7 client.
- 18394 — Reason: Opening the database requested by the user failed unexpectedly.
- 18395 — Reason: Authentication was successful, but database was not found on this logical server.
- 18396 — Reason: Authentication was successful, but database could not be found on current instance.
- 18397 — Reason: Unable to retrieve database firewall rules.
- 18398 — Reason: Catch exception from FindLogin during contained database authentication.
- 18399 — Reason: Unsecured connection to the database is disallowed. The secured connection string should be used instead. [Database: '%.*ls']
- 18400 — The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its res…
- 18401 — Login failed for user '%.*ls'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls
- 18451 — Login failed for user '%.*ls'. Only administrators may connect at this time.%.*ls
- 18452 — Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.%.*ls
- 18453 — Login succeeded for user '%.*ls'. Connection made using Integrated authentication.%.*ls
- 18454 — Login succeeded for user '%.*ls'. Connection made using SQL Server authentication.%.*ls
- 18455 — Login succeeded for user '%.*ls'.%.*ls
- 18456 — Login failed for user '%.*ls'.%.*ls%.*ls
- 18458 — Login failed. The number of simultaneous users already equals the %d registered licenses for this server. To increase the maximum number of simultaneo…
- 18459 — Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls
- 18460 — Login failed. The number of simultaneous users has already reached the limit of %d licenses for this '%ls' server. Additional licenses should be obtai…
- 18461 — Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls
- 18462 — The login failed for user "%.*ls". The password change failed. The password for the user is too recent to change. %.*ls
- 18463 — The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls
- 18464 — Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is too short…
- 18465 — Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is too long.…
- 18466 — Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet operating system policy requirements because it is not compl…
- 18467 — The login failed for user "%.*ls". The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls
- 18468 — The login failed for user "%.*ls". The password change failed. An unexpected error occurred during password validation. %.*ls
- 18469 — [CLIENT: %.*s%.*ls]
- 18470 — Login failed for user '%.*ls'. Reason: The account is disabled.%.*ls
- 18471 — The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls
- 18482 — Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.
- 18483 — Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login n…
- 18485 — Could not connect to server '%.*ls' because it is not configured to accept remote logins. Use the remote access configuration option to allow remote l…
- 18486 — Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls
- 18487 — Login failed for user '%.*ls'. Reason: The password of the account has expired.%.*ls
- 18488 — Login failed for user '%.*ls'. Reason: The password of the account must be changed.%.*ls
- 18489 — The dedicated administrator connection is in use by "%.*ls" on "%.*ls".%.*ls
- 18491 — SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinst…
- 18492 — SQL Server cannot start because the license agreement for this '%ls' version of SQL Server is invalid. The server is exiting. To proceed, reinstall SQ…
- 18493 — The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls
- 18494 — The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls
- 18495 — The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls
- 18496 — System Manufacturer: '%ls', System Model: '%ls'.
- 18497 — [SERVER: %.*s%.*ls]
- 18498 — Local time zone manager initialization failed. To identify the error, check the SQL Server error log.
- 18596 — %.*ls cannot start because your system is low on memory.
- 18597 — Your %.*ls installation is either corrupt or has been tampered with (%hs). Please uninstall then re-run setup to correct this problem
- 18598 — %.*ls could not find the default instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf…
- 18599 — %.*ls could not find the specified named instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.ex…
- 18749 — MaxCmdsInTran parameter for log reader cannot be set with CDC enabled on the db
- 18750 — %ls: The parameter '%ls' is not valid.
- 18751 — %ls procedure was called with the wrong number of parameters.
- 18752 — Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you execute…
- 18755 — Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations.
- 18756 — Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.
- 18757 — Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
- 18760 — Invalid %ls statement for article %d. Verify that the stored procedures that propagate changes to Subscribers use the appropriate call syntax, and the…
- 18761 — Commit record at {%08lx:%08lx:%04lx} has already been distributed.
- 18762 — Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.
- 18763 — Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0).
- 18764 — Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.
- 18765 — The "%s" log sequence number (LSN) that was specified for the replication log scan is invalid.
- 18766 — The replbeginlsn field in the DBTABLE is invalid.
- 18767 — The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}.
- 18768 — The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.
- 18769 — The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record.
- 18770 — The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.
- 18771 — Invalid storage type %d specified writing variant of type %d.
- 18772 — Invalid server data type (%d) specified in repl type lookup.
- 18773 — Could not locate text information records for the column "%.*ls", ID %d during command construction.
- 18774 — The stored procedure %s must be executed within a transaction.
- 18775 — The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.
- 18776 — An error occurred while waiting on the article cache access event.
- 18777 — %s: Error initializing MSMQ components
- 18778 — %s: Error opening Microsoft Message Queue %s
- 18780 — You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter.
- 18781 — The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', 'disk', 'tape' or 'url'.
- 18782 — Could not locate backup header information for database '%s' in the specified backup device. Specify a backup device that contains a backup of the Pub…
- 18783 — The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to use a sh…
- 18784 — The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder…
- 18786 — The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, use sp_changepublicatio…
- 18787 — Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications.
- 18788 — Column data not found as scan task has been aborted.
- 18790 — Cannot enable the option to initialize a subscription from a backup. This is not supported for non-SQL Server Publishers; it is only supported for tra…
- 18791 — The conditions for reading the log record of type %d have not be met.
- 18795 — The valid new types of a log based indexed view article are 'indexed view logbased', 'indexed view logbased manualfilter', 'indexed view logbased manu…
- 18796 — The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only.
- 18799 — Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in …
- 18801 — Unable to allocate memory for replication schema version node.
- 18802 — Cannot insert a new schema change into the systranschemas system table. HRESULT = '0x%x'. If the problem persists, contact Customer Support Services.
- 18803 — The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N'helptopics'.
- 18804 — Peer-to-peer replication has been enabled, and the Log Reader Agent was unable to find an Extended-Originator-Record (EOR) for a transaction that did …
- 18805 — The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication database and…
- 18806 — Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server.
- 18807 — Cannot find an object ID for the replication system table '%s'. Verify that the system table exists and is accessible by querying it directly. If it d…
- 18808 — Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent.
- 18809 — END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.
- 18810 — Cannot restart the scan on table '%s'. HRESULT = '0x%x'. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Serv…
- 18811 — Invalid %s log record.
- 18812 — Can not lock the database object in article cache.
- 18815 — Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.
- 18817 — Text information block not valid. Contact Customer Support Services.
- 18818 — Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
- 18819 — Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
- 18821 — The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services.
- 18823 — Invalid value %d for %s.
- 18826 — Failed to delete rows from the systranschemas table. HRESULT = '0x%x'. The rows will be deleted the next time replication executes the stored procedur…
- 18827 — The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %d transactions in the hash table, %d transac…
- 18828 — Invalid filter procedure definition.
- 18829 — Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
- 18830 — A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, current BE…
- 18832 — The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08lx:%08l…
- 18834 — An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlags 0x%x…
- 18835 — Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld, newS…
- 18836 — %s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %ld, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, offset …
- 18837 — Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to t…
- 18838 — The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subs…
- 18840 — Cannot locate database information in the article cache. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, back up the pu…
- 18842 — Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the Log Reader Agent. If the prob…
- 18843 — Failed to allocate or reallocate buffer for replication command, old size %d, new size %d.
- 18844 — Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication.
- 18845 — Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication.
- 18846 — Possible inconsistent state in the distribution database: dist_backup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute "sp_repldone…
- 18847 — Cannot retrieve the peer-to-peer database information. Contact Customer Support Services.
- 18849 — Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %d, rowsetId %I64d. Stop and resta…
- 18850 — Unexpected %s log record encountered, last FILESTREAMInfo node processed : {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, …
- 18851 — Failed to %s the replication context for TxF: {%I64d, %.*ls, %ld, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %I64d, %.*ls, {%08lx:%08lx:%04…
- 18852 — Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%ld'. If the problem persists, contact Customer Support Services.
- 18853 — Replication is skipping schema version logging because the systranschemas table is not present in database '%d'. This is an informational message only…
- 18854 — One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.
- 18855 — Can not rename the database name because it is published or it is a distribution database used by replication.
- 18856 — Agent '%s' is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details.
- 18857 — The subscription to this publication is not active yet. No user action is required.
- 18858 — Could not read data from replication table '%s'. If retrying does not fix the issue, drop and reconfigure replication.
- 18859 — Provided value for %ls parameter is invalid. Allowed values are %ls.
- 18860 — No RE Schema information found in cache for the table id %ld and transaction id %I64d.
- 18861 — RE Schema node could not be created in memory after 5 retries for Table id %ld and transaction id %I64d.
- 18896 — Failed to compare delete and insert log record for column ID %ld with table ID %ld
- 18897 — Access Denied.
- 18898 — Change Data Capture cannot be enabled for database '%s' because table '%s' already exists and is not a valid Microsoft system table. Drop the table an…
- 18899 — Change Data Capture was not enabled for database '%s' because the required unique clustered index 'uncsystranschemas' on table 'dbo.systranschemas' is…
- 19030 — SQL Trace ID %d was started by login "%s".
- 19031 — SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'.
- 19032 — SQL Trace was stopped due to server shutdown. Trace ID = '%d'. This is an informational message only; no user action is required.
- 19033 — Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
- 19034 — Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls
- 19035 — OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is …
- 19036 — The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the…
- 19049 — File '%.*ls' either does not exist or there was an error opening the file. Error = '%ls'.
- 19050 — Trace file name '%.*ls' is invalid.
- 19051 — Unknown error occurred in the trace.
- 19052 — The active trace must be stopped before modification.
- 19053 — The trace event ID is not valid.
- 19054 — The trace column ID is not valid.
- 19055 — Filters with the same event column ID must be grouped together.
- 19056 — The comparison operator in the filter is not valid.
- 19057 — The boolean operator in the filter is not valid.
- 19058 — The trace status is not valid.
- 19059 — Could not find the requested trace.
- 19060 — The trace option is not valid.
- 19061 — Cannot remove SPID trace column.
- 19062 — Could not create a trace file.
- 19063 — Not enough memory was available for trace.
- 19064 — The requested trace stop time has been already passed.
- 19065 — The parameter is not valid.
- 19066 — Cannot modify a restricted trace.
- 19067 — Cannot create a new trace because the trace file path is found in the existing traces.
- 19068 — The trace file path is not valid or not supported.
- 19069 — The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover option is enabled.
- 19070 — The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
- 19071 — Stopping the trace because the current trace file is full and the rollover option is not specified.
- 19096 — Fail to delete an old trace file '%ls'. Error = '%ls'.
- 19097 — Operating system error occurred while running %s. Error = %s.
- 19098 — An error occurred starting the default trace. Cause: %ls Use sp_configure to turn off and then turn on the 'default trace enabled' advanced server con…
- 19099 — Trace ID '%d' was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.
- 19100 — Initialization succeeded.
- 19101 — Initialization failed with an infrastructure error. Check for previous errors.
- 19102 — Unable to create a node listener object. Check for memory-related errors.
- 19103 — An error occurred while starting shared memory support.
- 19104 — All protocols are disabled.
- 19105 — Unable to create a node listener object for a special instance. Check for memory-related errors.
- 19106 — Unable to trim spaces in an IP address. Check TCP/IP protocol settings.
- 19107 — 'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings.
- 19108 — Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings.
- 19109 — Unable to configure MDAC-compatibility TCP/IP port in registry.
- 19110 — Unable to initialize the TCP/IP listener.
- 19111 — Unable to open TCP/IP protocol configuration key in registry.
- 19112 — Unable to retrieve TCP/IP protocol 'Enabled' registry setting.
- 19113 — Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting.
- 19114 — Unable to open TCP/IP protocol's 'IPAll' configuration key in registry.
- 19115 — Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key.
- 19116 — Unable to obtain list size for IP addresses configured for listening in registry.
- 19117 — Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors.
- 19118 — Unable to obtain list of IP addresses configured for listening in registry.
- 19119 — Unable to open TCP/IP protocol's registry key for a specific IP address.
- 19120 — Unable to retrieve 'Enabled' setting for a specific IP address.
- 19121 — Unable to retrieve 'Active' setting for a specific IP address.
- 19122 — Unable to retrieve 'IpAddress' value for a specific IP address.
- 19123 — 'IpAddress' registry value is the wrong type.
- 19124 — Unable to retrieve registry settings for a specific IP address.
- 19125 — Unable to deallocate structures representing registry key for a specific IP address.
- 19126 — Unable to retrieve registry settings for cluster environment.
- 19127 — Server is configured to listen on a specific IP address in a cluster environment.
- 19128 — The SQL Server Network Interface cannot check for a duplicate IP address in the SQL Server TCP listening settings.
- 19129 — The SQL Server Network Interface found a duplicate IP address in the SQL Server TCP listening settings. Remove the duplicate IP address by using SQL S…
- 19130 — Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings.
- 19131 — Unable to open Dedicated Administrator Connection configuration key in registry.
- 19132 — Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry.
- 19133 — Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection.
- 19134 — No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings.
- 19135 — Error starting Named Pipes support. Check protocol settings.
- 19136 — An error occurred starting VIA support. Check protocol settings.
- 19137 — Failed to allocate memory for SSL listening structures. Check for memory-related errors.
- 19138 — An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager.
- 19139 — Unable to add listener endpoints. Check for memory-related errors.
- 19140 — Unable to initialize the communication listeners.
- 19141 — Unable to retrieve SQL Server Network Interface library settings for a special instance.
- 19142 — Unable to retrieve SQL Server Network Interface library settings; the instance name is too long.
- 19143 — Unable to initialize the Shared Memory listener.
- 19144 — Unable to initialize the Named Pipes listener.
- 19145 — Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry.
- 19146 — Unable to initialize the VIA listener.
- 19147 — Unable to initialize the HTTP listener.
- 19148 — Unable to initialize SSL support.
- 19149 — Unable to configure MDAC-compatibility protocol list in registry.
- 19150 — Unable to open SQL Server Network Interface library configuration key in registry.
- 19151 — An error occurred while obtaining the Extended Protection setting. Check Network Configuration settings in SQL Server Configuration Manager.
- 19152 — The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
- 19153 — An error occurred while obtaining the Accepted SPNs list for Extended Protection. Check Network Configuration settings in SQL Server Configuration Man…
- 19154 — The configured value for the Accepted SPNs list is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
- 19155 — TDSSNIClient failed to allocate memory while loading Extended Protection configuration settings. Check for memory-related errors.
- 19156 — Failed to allocate memory for SSPI listening structures. Check for memory-related errors.
- 19157 — Unable to initialize the SSPI listener.
- 19158 — Unable to create connectivity Ring Buffer. Check for memory-related errors.
- 19159 — Unable to open 'Named Pipes' configuration key for Dedicated Administrator Connection in registry.
- 19160 — Unable to retrieve 'Enabled' registry settings for Named-Pipe Dedicated Administrator Connection.
- 19161 — No protocol is enabled for the Dedicated Administrator Connection.
- 19162 — Unable to retrieve 'PipeName' registry settings for Named-Pipe Dedicated Administrator Connection.
- 19163 — Error starting Named Pipes support for Dedicated Administrator Connection.
- 19164 — Unable to retrieve 'GroupName' registry settings for Named-Pipe Dedicated Administrator Connection.
- 19165 — Error starting Named Pipes support for Dedicated Administrator Connection.
- 19200 — Authentication succeeded.
- 19201 — The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream.
- 19202 — An error occurred while calling CompleteAuthToken for this security context. The operating system error code indicates the cause of failure.
- 19203 — The CompleteAuthToken API is not defined for the current Security Support Provider.
- 19204 — AcceptSecurityContext failed. The operating system error code indicates the cause of failure.
- 19205 — The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update the operating system or di…
- 19206 — The Channel Bindings from this client do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the d…
- 19207 — The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. The service might be under a…
- 19208 — The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update the operating system or di…
- 19209 — QueryContextAttributes could not retrieve Service Bindings. The operating system error code indicates the cause of failure.
- 19210 — The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this cl…
- 19211 — The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this cl…
- 19212 — The Service Class element of the received Service Principal Name (SPN) is not valid.
- 19213 — The IP Address element of the received Service Principal Name (SPN) is not valid.
- 19214 — The Host element of the received Service Principal Name (SPN) is not valid.
- 19215 — A memory allocation failed while validating the received Service Principal Name (SPN).
- 19216 — QueryContextAttributes succeeded but did not retrieve the received Service Principal Name (SPN).
- 19217 — WSAStringToAddress was unable to convert the IP Address element of the received Service Principal Name (SPN) to an address structure. The operating sy…
- 19218 — Could not wait on an event signaling IO completion for a cryptographic handshake.
- 19219 — A task to process a cryptographic handshake could not be enqueued.
- 19220 — An attempt to read a buffer from the network failed during a cryptographic handshake.
- 19221 — The connection was closed while attempting to process a read buffer during a cryptographic handshake.
- 19222 — The connection was closed while attempting to process a write buffer during a cryptographic handshake.
- 19223 — An attempt to write a buffer to the network failed during a cryptographic handshake.
- 19224 — AcquireCredentialsHandle failed. The operating system error code indicates the cause of the failure.
- 19225 — InitializeSecurityContext failed. The operating system error code indicates the cause of the failure.
- 19226 — QueryContextAttributes could not retrieve stream sizes. The operating system error code indicates the cause of the failure.
- 19227 — An attempt to resize a buffer failed.
- 19228 — An unexpected error occurred during a cryptographic handshake.
- 19229 — An invalid token was received during a cryptographic handshake.
- 19230 — Failed to allocate a packet for a network write during a cryptographic handshake.
- 19231 — Failed to allocate an object to perform a cryptographic handshake.
- 19232 — Failed to initialize an object to perform a cryptographic handshake.
- 19233 — A token from a cryptographic handshake was larger than allowed by SSPI.
- 19234 — The connection was closed while waiting for network IO during a cryptographic handshake.
- 19235 — An unexpected exception was thrown while processing a cryptographic handshake.
- 19236 — Negotiated security context is missing an integrity flag.
- 19238 — Negotiated security context is missing a confidentiality flag.
- 19239 — Negotiated security context has confidentiality flag present.
- 19240 — Negotiated security context is missing a sequence detection flag.
- 19241 — Negotiated security context is missing a replay detection flag.
- 19242 — Global credentials handle required for inbound connections.
- 19243 — SSPI structures too large for encryption.
- 19244 — SSPI structures too large for signature.
- 19245 — Empty output token is returned by SSPI during security context negotiation. Check for network packet corruption or other networking issues.
- 19246 — Incomplete message error is returned from SSPI but failed to proceed.
- 19300 — An invalid Pattern '%.*s' was provided. Error '%.*s' occurred during evaluation of the Pattern.
- 19301 — '%.*ls' value should be greater than or equal to %d but '%d' is provided in '%.*ls' function.
- 19302 — Maximum of '%d' flags can be provided. But you provided '%d' flags.
- 19303 — Invalid flag provided. '%.*s' are not valid flags. Only {c,i,s,m} flags are valid.
- 19304 — Currently, '%.*s' function does not support NVARCHAR(max)/VARCHAR(max) inputs.
- 19305 — Failed to replace '%.*ls' with replacement string '%.*ls' from start position '%d'.
- 19306 — The provided Pattern is too complex. Please retry by reducing the complexity of Pattern - '%.*ls'.
- 19307 — Encountered an unexpected '%.*ls' in the Pattern %.*s.
- 19308 — Missing '%.*ls' in the Pattern %.*s.
- 19309 — Invalid trailing backslash () provided at the end of the Pattern %.*s.
- 19310 — The supplied 'string_expression' value to '%.*ls' function exceeds the supported max length for regex operation.
- 19311 — The input for 'string_expression' exceeds the maximum allowed size of 2MB. Please ensure the input size is within the allowed limit and try again.
- 19312 — The query failed due to an unexpected error while compiling the regex pattern in the %.*ls function. Please retry and contact support if the error per…
- 19401 — The READ_ONLY_ROUTING_URL '%.*ls' specified for availability replica '%.*ls' is not valid. It does not follow the required format of 'TCP://system-add…
- 19402 — A duplicate availability replica '%.*ls' was specified in the READ_ONLY_ROUTING_LIST for availability replica '%.*ls'. Inspect the replica list that y…
- 19403 — The availability replica '%.*ls' specified in the READ_ONLY_ROUTING_LIST for availability replica '%.*ls' does not exist. Only availability replicas t…
- 19404 — An availability replica '%.*ls' that is specified in the READ_ONLY_ROUTING_LIST for availability replica '%.*ls' does not have a value set for READ_ON…
- 19405 — Failed to create, join or add replica to availability group '%.*ls', because node '%.*ls' is a possible owner for both replica '%.*ls' and '%.*ls'. If…
- 19406 — The state of the local availability replica in availability group '%.*ls' has changed from '%ls' to '%ls'. %ls. For more information, see the SQL Serv…
- 19407 — The lease between availability group '%.*ls' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance o…
- 19408 — The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the remote WSFC cluster, '%.*ls'. A…
- 19409 — The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the local WSFC cluster. An ALTER SE…
- 19410 — An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to a remote WSFC cluster failed. T…
- 19411 — The specified Windows Server Failover Clustering (WSFC) cluster, '%.*ls', is not ready to become the cluster context of Always On Availability Groups …
- 19412 — The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command failed. The current Windows Server Failover Clustering (WSFC) cluster contex…
- 19413 — An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context failed. This attempt failed …
- 19414 — An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to the specified WSFC cluster , '%…
- 19415 — Failed to process the registry key value '%.*ls' (Windows error code: %d), which holds the name of the remote Windows Server Failover Clustering (WSFC…
- 19416 — One or more databases in availability group '%.*ls' are not synchronized. On a synchronous-commit availability replica, ALTER AVAILABILITY GROUP <grou…
- 19417 — An attempt to fail over or create an availability group failed. This operation is not supported when Always On Availability Groups is running under a …
- 19418 — The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command failed because the local Windows Server Failover Clustering (WSFC) cluster n…
- 19419 — Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group '%.*ls' within the lease timeout per…
- 19420 — The availability group '%.*ls' is being asked to stop the lease renewal because the availability group is going offline. This is an informational mess…
- 19421 — SQL Server hosting availability group '%.*ls' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout…
- 19422 — The renewal of the lease between availability group '%.*ls' and the Windows Server Failover Cluster failed because SQL Server encountered Windows erro…
- 19423 — The lease of availability group '%.*ls' lease is no longer valid to start the lease renewal process.
- 19424 — The lease worker of availability group '%.*ls' is now sleeping the excess lease time (%u ms) supplied during online. This is an informational message …
- 19431 — Always On Availability Groups transport for availability database "%.*ls" has hit flow control boundary with log block whose LSN is %S_LSN. This error…
- 19432 — Always On Availability Groups transport has detected a missing log block for availability database "%.*ls". LSN of last applied log block is %S_LSN. L…
- 19433 — Always On: AG integrity check failed to find AG name to ID map entry with matching group ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
- 19434 — Always On: AG integrity check failed to find AG name to ID map entry with matching resource ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
- 19435 — Always On: AG integrity check failed for AG '%.*ls' with error %d, severity %d, state %d.
- 19436 — Always On: A failure [%d] was encountered while waiting for LSN %S_LSN to be hardened on the Commit Manager [%d] for database ID [%d] on partner ID [%…
- 19437 — Cannot set READ_ONLY_ROUTING_URL to NONE for availability replica '%.*ls' as it is being used in READ_ONLY_ROUTING_LIST of replica '%.*ls'. Please rem…
- 19450 — Failed to open a cluster network interface object: '%ls'. The WSFC cluster control API returned error code %d. The WSFC service may not be running or …
- 19451 — '%.*ls' and '%.*ls' belong to the same subnet. Only one IPv4 and/or one IPv6 address from each subnet is allowed. For an advanced configuration, see t…
- 19452 — The availability group listener (network name) with Windows Server Failover Clustering resource ID '%s', DNS name '%s', port %hu failed to start with …
- 19453 — The availability group listener (network name) with resource ID '%s', DNS name '%s', port %hu failed to start with this error: %u. Verify network and …
- 19454 — The availability group listener (network name) with resource ID '%s', DNS name '%s', port %hu failed to stop with this error: %u. Verify network and c…
- 19455 — The WSFC cluster does not have a public cluster network with an IPv4 subnet. This is a requirement to create an availability group DHCP listener. Conf…
- 19456 — None of the IP addresses configured for the availability group listener can be hosted by the server '%.*ls'. Either configure a public cluster network…
- 19457 — The specified IP Address '%.*ls' is not valid in the cluster-allowed IP range. Check with the network administrator to select values that are appropri…
- 19458 — The WSFC nodes that host the primary and secondary replicas belong to different subnets. DHCP across multiple subnets is not supported for availabilit…
- 19459 — The listener with DNS name '%.*ls' does not conform to SQL Server listener guidelines, and cannot be configured through SQL Server. Reconfigure the li…
- 19460 — The availability group listener with DNS name '%.*ls' is configured to use DHCP. For listeners with this configuration, IP addresses cannot be added t…
- 19461 — The WSFC node that hosts the primary replica belongs to multiple subnets. To use the DHCP option in a multi-subnet environment, supply an IPv4 IP addr…
- 19462 — Failed to obtain the WSFC node enumeration handle. The error code is %d. The WSFC service may not be running or may be inaccessible in its current sta…
- 19463 — The WSFC cluster network interface control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state…
- 19464 — The WSFC cluster network control API returned an invalid IP address. The WSFC service might have invalid data in its database or it is a not supported…
- 19465 — The WSFC management API returned an unrecognizable dependency expression: '%.*ls'. The WSFC service might have invalid data in its database or it is a…
- 19466 — Failed to obtain the WSFC resource dependency expression for cluster resource with name or ID '%ls' The error code is %d. The WSFC service may not be …
- 19467 — Failed to remove the resource dependency in which resource '%.*ls' is depending on resource '%.*ls' in the WSFC cluster. The error code is %d. The WSF…
- 19468 — The listener with DNS name '%.*ls' for the availability group '%.*ls' is already listening on the TCP port %u. Please choose a different TCP port for …
- 19469 — The specified listener with DNS name, '%.*ls', does not exist for the Availability Group '%.*ls'. Use an existing listener, or create a new listener.
- 19470 — Failed to delete a resource in the WSFC cluster because the resource '%.*ls' is not offline. Delete the resource using the Failover Cluster Management…
- 19471 — The WSFC cluster could not bring the Network Name resource with DNS name '%ls' online. The DNS name may have been taken or have a conflict with existi…
- 19472 — Failed to delete the WSFC cluster resource '%.*ls'. The error code is %d. The WSFC service may not be running or may be inaccessible in its current st…
- 19473 — Failed to add a resource dependency, making resource '%.*ls' depend on resource '%.*ls', in the WSFC cluster. The error code is %d. The WSFC service m…
- 19474 — Failed to set the resource dependency expression '%ls' for the WSFC resource '%.*ls'. The error code is %d. The WSFC service may not be running or may…
- 19475 — Cannot take the WSFC resource with ID '%.*ls' offline. The error code is %d. The WSFC service may not be running or may be inaccessible in its current…
- 19476 — The attempt to create the network name and IP address for the listener failed. If this is a WSFC availability group, the WSFC service may not be runni…
- 19477 — The availability group '%.*ls' already has a listener with DNS name '%.*ls'. Availability groups can have only one listener. Use the existing listener…
- 19478 — Failed to find a multi-string property (property name '%ls') of the WSFC resource with name or ID '%.*ls'. The system error code is %d. The WSFC servi…
- 19479 — The WSFC cluster network control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For info…
- 19480 — Failed to open a cluster network object: '%ls'. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be ina…
- 19481 — Failed to obtain the WSFC resource state for cluster resource with name or ID '%.*ls'. The WSFC resource state API returned error code %d. The WSFC se…
- 19482 — The port number, %u, that is specified is invalid. Valid port numbers range from 1 to 65535, inclusive. Select a port number in this range. If a port …
- 19483 — The format for the IP address, '%.*ls', is invalid. Please use a valid value for the IP address.
- 19484 — The specified IP Address, '%.*ls', is duplicated in the IP address list. Each IP address included in the listener configuration must be unique. Change…
- 19485 — The specified DNS name, '%.*ls', is invalid. The length of the DNS name needs to be between 1 and 63 characters, inclusive. Change the value of the DN…
- 19486 — The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on th…
- 19487 — Listener configuration changes were completed but listening status of the corresponding TCP provider could not be determined because of the error code…
- 19488 — The attempt to create the network name and IP address for the listener failed, and the attempt to roll back the resources for the Network Name and IP …
- 19489 — The attempt to create FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
- 19490 — The attempt to delete FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
- 19491 — Always On: The Windows Server Failover Clustering (WSFC) service was started using /forcequorum. This is an informational message only. No user action…
- 19492 — The availability database %ls in availailability group %ls is in an invalid state to perform an internal operation. Refer to the error code for more d…
- 19493 — Corrupt secondary replica %ls causing start scan to fail for database with ID %d. Refer to the SQL Server error log for information about the errors t…
- 19494 — Automatic seeding of availability database '%ls' in availability group '%.*ls' failed with a transient error. The operation will be retried.
- 19495 — Automatic seeding of availability database '%ls' in availability group '%.*ls' failed with an unrecoverable error. Correct the problem, then issue an …
- 19496 — Automatic seeding of availability database '%.*ls' in availability group '%.*ls' failed.
- 19497 — Conflicting option spec provided. DISTRIBUTED option cannot be combined with any other availability group options.
- 19498 — To create a distributed availability group, please specify the DISTRIBUTED option.
- 19499 — The specified listener URL '%.*ls' is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for a…
- 19501 — None of the specified availability groups exist locally. Please check your DDL and make sure there is one availability group exist locally.
- 19502 — Cannot create a distributed availability replica for availability group '%.*ls'. An availability replica of the specified availability group already e…
- 19503 — Cannot create a distributed availability replica for availability group '%.*ls'. Local availability group is participating in a distributed availabili…
- 19504 — Cannot failover a distributed availability replica for availability group '%.*ls'. Only force failover is supported in this version of SQL Server.
- 19505 — Cannot initiate a target seeding operation on a non-secondary/forwarder replica for availability group '%.*ls'. Replica state may have changed since w…
- 19506 — Local availability replica for availability group '%.*ls' has not been granted permission to create databases, but has a SEEDING_MODE of AUTOMATIC. Us…
- 19507 — Cannot create a distributed availability replica for availability group '%.*ls'. There is an already existing distributed availability group on top of…
- 19508 — 'ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Participant availability replica '%.*ls' not found in the distributed availabilit…
- 19509 — Cannot create a distributed availability group '%.*ls'. An availability group with the same name already exists.
- 19510 — Distributed availability group '%.*ls' not found. Rerun the command with an existing distributed availbility group.
- 19511 — Cannot join distributed availability group '%.*ls'. The local availability group '%.*ls' contains one or more databases. Remove all the databases or c…
- 19512 — The requested operation only applies to distributed availability group, and is not supported on the specified availability group '%.*ls'. Please make …
- 19513 — Cannot create a distributed availability replica for availability group '%.*ls'. Distributed availability group cannot be built on top of basic local …
- 19514 — Failed to wait for primary partner's transport up while starting up secondary remote replica.
- 19515 — Database partner is missing during database restart.
- 19516 — Creating Availability Group Listener '%.*ls' in Availability Group '%.*ls' with DISTRIBUTED_NETWORK_NAME option is not supported in non WSFC cluster.
- 19517 — The specified listener with DNS name, '%.*ls' in Availability Group '%.*ls' is a DISTRIBUTED_NETWORK_NAME listener. Cannot add IP to a DISTRIBUTED_NET…
- 19518 — The listener port '%.*ls' is in conflict with other Availability Group listeners. Retry the operation with a unique port.
- 19519 — Failed to set the WSFC cluster resource name to '%.*ls'. The error code is %d. The WSFC service may not be running or may be inaccessible in its curre…
- 19520 — The DISTRIBUTED_NETWORK_NAME resource name '%.*ls' should match the listener port number but is invalid now. Modify the resource name back to the port…
- 19521 — The attempt to create the distributed network name for the listener failed. The WSFC service may not be running or may be inaccessible in its current …
- 19522 — The attempt to retrieve local physical addresses from WSFC failed. Check the state of the WSFC cluster with the network administrator. Otherwise, cont…
- 19523 — The specified '%.*ls' of Availability Group must be less than 256 characters long.
- 19524 — Failed to create a database backup on a secondary replica for database "%.*ls.". Required information could not be committed on the primary replica. C…
- 19525 — Failed to create a database backup on a secondary replica for database "%.*ls.". The differential bitmaps could not be cleared and the checkpoint coul…
- 19526 — Failed to create a full backup on the secondary replica for database "%.*ls.". The primary database lock could not be acquired on the primary replica.…
- 19527 — Failed to initialize a full backup on the secondary replica for database "%.*ls.". Verify that the database is a member of the availability group, and…
- 19528 — Failed to create a full backup on secondary replica for database "%.*ls.". The checkpoint could not be run on the primary replica. Check the health of…
- 19529 — Failed to create a database backup on secondary replica for database "%ls". The checkpoint LSN from primary replica could not be redone. Check the hea…
- 19530 — The %ls operation is not allowed by the current availability group configuration. The required_synchronized_secondaries_to_commit needs to be 0 when c…
- 19531 — Database [%ls] failed to refresh lease info with fabric, request returned with [%ld]. Check the SQL Server error log on the exact failure.
- 19532 — While reverting to the common recovery point, database "%.*ls" retrieved a page that may not be consistent with existing pages or log records. To gain…
- 19533 — Cannot create distributed availability group '%.*ls' as it requires two Availaiblity Group Replicas, however %d were specified.
- 19534 — The attempt to remove IP address from the listener failed. If this is a WSFC availability group, the WSFC service may not be running or may be inacces…
- 19535 — The attempt to remove IP resource '%.*ls' from the listener failed since cluster resource is not offline. Cluster resource state is %d.
- 19536 — The default startup routine of database '%.*ls' that belongs to an availability group (Group ID: %d) cannot be skipped because SQL Server did not init…
- 19537 — The WSFC is already taking action against availability group '%.*ls'. SQL Server will attempt to online the availability group without interfering wit…
- 19538 — Availability group commit time has been set to %d millisecond(s). This value will take effect when the current replica is primary.
- 19539 — Unexpected error %d severity %d, state %d occurred while creating distributed availability group '%.*ls' with SQL Managed Instance. Drop the distribut…
- 19540 — Unexpected error occurred while handling distributed availability group.
- 19541 — Cannot create distributed availability group '%.*ls' with SQL Managed Instance on top of availability group '%.*ls'. An availability replica of the sp…
- 19542 — Unexpected error %d severity %d, state %d occurred while adding database '%.*ls' to availability group '%.*ls' participating in distributed availabili…
- 19543 — Unexpected error %d severity %d, state %d occurred while removing database '%.*ls' from availability group '%.*ls' participating in distributed availa…
- 19544 — Attempting to create an availability group with cluster_type set to NONE or EXTERNAL, with a name that is longer than 64 characters, is not supported.…
- 19545 — 'ALTER AVAILABILITY GROUP' command failed for internal distributed availability group '%.*ls'. Altering internal distributed availability groups is no…
- 19546 — 'ALTER DATABASE SET HADR' command failed for database '%.*ls'. This command is not supported for databases participating in distributed availability g…
- 19547 — The integrity check for distributed availability group '%.*ls' with SQL Managed Instance failed with error cause: '%S_MSG'. Corrective action: '%S_MSG…
- 19548 — The integrity check for distributed availability group '%.*ls' with SQL Managed Instance failed with error cause: 'An availability database '%.*ls' no…
- 19549 — Provided distributed availability group name '%.*ls' is invalid. Please provide a name of a distributed availability group with SQL Managed Instance.
- 19550 — Distributed availability group with managed instance does not support having multiple databases.
- 19551 — The CLUSTER_CONNECTION_OPTIONS argument can only be specified when the availability group uses a Windows Server failover cluster. Remove CLUSTER_CONNE…
- 19552 — The current value of HostNameInCertificate is too long. Current length: %ld characters, maximum length: %ld characters.
- 19553 — The current value of ServerCertificate is too long. Current length: %ld characters, maximum length: %ld characters.
- 19554 — Invalid key '%.*ls' in the %.*ls argument. For more information, see %.*ls.
- 19555 — The format of the '%.*ls' argument is invalid. The expected format is '<key=value>;<key=value>;...'. Spaces and semicolons in keys or values are not a…
- 19556 — Invalid value '%.*ls' for Encrypt. Valid values are Strict, Mandatory or Optional. For more information, see %.*ls.
- 19557 — Invalid value '%.*ls' for TrustServerCertificate. Valid values are Yes or No. For more information, see %.*ls.
- 19558 — Duplicate key '%.*ls' in %.*ls.
- 19559 — The key 'Encrypt' must be specified in %.*ls.
- 19560 — Online request to Windows Server Failover cluster is skipped after repeated resource online failures are detected for availability group '%.*ls'. The …
- 19561 — As a result of executing sys.sp_mi_dag_repair, database '%.*ls' was removed from availability group '%.*ls'.
- 19562 — As a result of executing sys.sp_mi_dag_repair, internal availability group '%.*ls' was removed from availability group '%.*ls'.
- 19563 — Can not execute sp_mi_dag_repair on availability group '%.*ls' as the local availability replica is not in the primary role.
- 19564 — A %ls backup for database "%.*ls" failed on a secondary replica because log truncation could not be disabled on the primary replica. Check the health …
- 19565 — An internal error occurred while accessing automatic seeding history. HRESULT: 0x%08x.
- 19566 — Database '%.*ls' cannot be reseeded because it is not part of an availability group.
- 19567 — Database '%.*ls' cannot be reseeded because the local availability replica is offline. Bring the local availability replica online and try again.
- 19568 — Database '%.*ls' cannot be reseeded because its availability group is not part of any Managed Instance link.
- 19569 — Database '%.*ls' cannot be reseeded because it was not found in the availability group '%.*ls'.
- 19570 — Database '%.*ls' cannot be reseeded because its internal link with Managed Instance could not be found. Run sys.sp_milink_repair to repair the interna…
- 19571 — Database '%.*ls' cannot be reseeded because the local availability replica is a secondary replica. The operation can only be performed when the local …
- 19572 — Started reseeding of internal Managed Instance link for database '%.*ls' in availability group '%.*ls'.
- 19573 — Database '%.*ls' cannot be reseeded because its availability group '%.*ls' is not part of the specified Managed Instance link '%.*ls'. Verify the Mana…
- 19601 — System error.
- 19602 — System error.
- 19603 — System error.
- 19604 — System error.
- 19605 — System error.
- 19606 — System error.
- 19607 — System error.
- 19608 — System error.
- 19609 — System error.
- 19610 — System error.
- 19611 — System error: "%ls".
- 19612 — System error: '%.*ls', '%.*ls'.
- 19613 — System error: '%.*ls'.
- 19614 — System error: '%.*ls'.
- 19615 — System error: '%s'.
- 19616 — System error: '%s'.
- 19617 — System error.
- 19618 — System error.
- 19619 — System error: %s.
- 19620 — System error: %ld.
- 19621 — System error: %s.
- 19701 — 1 row was rejected during query execution.
- 19702 — %ld rows were rejected during query execution.
- 19703 — Table manifest generation error.
- 19704 — Missing %ls in ROWSET_OPTIONS. It is required when %ls is set.
- 19705 — Failed to create a new database due to system error.
- 19706 — Database edition was not properly set or is missing in the DDL statement.
- 19707 — Failed to create a credential to access the data root container.
- 19708 — Artifact ID was not properly set or is missing in the DDL statement.
- 19709 — The specified bulk option '%ls' is not supported for file format '%ls'. Review the documentation for supported options.
- 19710 — Master key for database '%.*ls' was automatically created because it did not exist.
- 19711 — Failed to alter database due to system error.
- 19712 — The Create External Table as Select operation is not supported for the connector specified by external data source '%.*ls'.
- 19713 — Statistics on virtual column are not available.
- 19714 — Number of columns in PARTITION clause does not match number of partition columns in Delta schema.
- 19715 — Resolving schema for Delta Lake table '%ls' failed with error: Unable to read schema from Delta logs.
- 19716 — Data path was not properly set or is missing in the DDL statement.
- 19717 — SP '%.*ls' should be called under the explicitly started transaction (started with BEGIN TRAN).
- 19718 — Resolving Delta logs on path '%ls' warning: Partitioning column '%.*ls' not found in inferred or provided schema.
- 19719 — Failed to acquire mutex for DW DB attachment with result %lu.
- 19720 — Filter pushdown not supported for column type-filter param type pair.
- 19721 — DW database attachment task failed for database with ID %d (HRESULT = 0x%x).
- 19722 — DW database attachment task failed to notify MS upon its completion (HRESULT = 0x%x).
- 19723 — Database attachment failed because another database with ID %ld already exists.
- 19724 — Database could not be successfully attached to appropriate DB ID.
- 19725 — Column mapping is not enabled.
- 19726 — Feature '%ls' is not supported for table '%ls'.
- 19727 — Resolving schema for Delta Lake table '%ls' failed with error: Empty column name found in Delta logs.
- 19728 — Database could not be successfully detached.
- 19729 — Database(s) could not be successfully attached.
- 19730 — Database state could not be successfully fetched.
- 19731 — Failed calculating cardinality for '%.*ls'.
- 19732 — Login failed for user '%.*ls' due to no proper resource access. Only backend connections are allowed.%.*ls
- 19733 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19734 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19735 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19736 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19737 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19738 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19739 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19740 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19741 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19742 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19743 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19744 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19745 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19746 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19747 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19748 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19749 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19750 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19751 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19752 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19753 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19754 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19755 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19756 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19757 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19758 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19759 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19760 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19761 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19762 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19763 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19764 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19765 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19766 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19767 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19768 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19769 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19770 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19771 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19772 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19773 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19774 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19775 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19776 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19777 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19778 — Error encountered while parsing data: '%ls'. It might happen for one of the various reasons: \n1. Parquet file is corrupted. \n2. The file size define…
- 19779 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19780 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19781 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19782 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19783 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19784 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19785 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19786 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19787 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19788 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19789 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19790 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19791 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19792 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19793 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19794 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19795 — Failed to start database '%ls' for recovery.
- 19796 — Failed to read parquet file because the column segment for column '%ls' is too large. Underlying data description: '%ls'.
- 19797 — Operation %ls is not allowed in dbo schema.
- 19798 — An unexpected system error was reported (%ls, %ls).
- 19799 — Restore for database failed.
- 19801 — Lease metadata inconsistency has been detected on blob.
- 19802 — Partition column '%ls' has unsupported type.
- 19803 — Login failed for user '%.*ls' because the DMS moniker was not found. Only backend connections are allowed.%.*ls
- 19804 — Restore for database "%.*ls" is in progress.
- 19805 — Fetching DW database properties failed.
- 19806 — The provided file format is not supported. Please ensure the file is in one of the supported .ss formats (up to v5). Underlying data description: %ls.
- 19807 — Error encountered while parsing data: '%ls'. Underlying data description: %ls.
- 19808 — Error encountered while reading data: '%ls'. Underlying data description: %ls.
- 19809 — Error encountered while reading data: '%ls'. Underlying data description: %ls.
- 19810 — Login failed for user '%.*ls' as storage SAS token refresh was delayed or failed. Only backend connections are allowed.%.*ls
- 19811 — Maximum LOB value size has been exceeded for column '%ls'. Underlying data description: %ls.
- 19812 — CODEPAGEs different than 65001 and 1200 are not supported when CSV 2.0 is specified.
- 19813 — Failed to change lease order id.