#15522 medium
Errors

Description 15522 10 No Rule unbound from table column. 15523 10 No Rule unbound from data type. 15524 10 No Columns of the specified user data type had their rules unbound. 15525 10 No sp_checknames

#io#severity-medium
#15558 medium
Errors

Description 15558 10 No Cannot drop %S_MSG by %S_MSG '%.*s'. 15559 10 No Cannot drop %S_MSG '%.*ls' because there is a %S_MSG mapped to it. 15560 10 No Cannot add or drop a signature on '%.*ls' becaus

#io#severity-medium
#15586 medium
Errors

Description 15586 16 No Error in synchronizing system certificates between master and resource database.

#io#severity-medium
#15612 medium
Errors

Description 15612 16 No DBCC DBCONTROL error. Database was not made read-only. 15615 16 No DBCC DBCONTROL error. Database was not made single user. 15622 10 No No permission to access database '%s'. 1

#io#severity-medium
#15663 medium
Errors

'Description 15663 16 No Feature "sp_addserver" is no longer supported. Replace remote servers by using linked servers. 15664 16 No Cannot set key ''%ls'' in the session context. The key has been set as '

#io#severity-medium
#15714 medium
Errors

Description 15714 16 Yes Cannot execute stored procedure on this database type.

#io#severity-medium
#15808 medium
Errors

Description 15808 16 No Schema cannot be determined from data files for file format '%.*ls'. Please use WITH clause of OPENROWSET to define schema.

#io#severity-medium
#15826 medium
Errors

Description argument is out of range. 15826 16 No Filename function prefix '%s' does not match the alias name. 15827 16 No The filename function requires 0 arguments. 15828 16 No The filepath function

#io#severity-medium
#15843 medium
Errors

Description 15843 16 No An error occurred while processing file '%ls'. HRESULT = '0x%x'. 15844 16 No Data type '%s' is currently not supported. 15845 16 No Data type '%s' is not supported. 15846 16 No

#io#severity-medium
#15864 medium
Errors

Description 15864 16 No Openrowset statistics for specified openrowset source do not exist. Please, correct '%.*ls' OPENROWSET query argument to make sure that you specify good OPENROWSET options. 158

#io#severity-medium
#15886 medium
Errors

Description 15886 16 No Non-recoverable IO failure has occurred targeting '%ls' (details: {Operation = '%ls', HRESULT = '%ls'}). 15887 16 No USE statement does not support switching to '%ls' database.

#connection#severity-medium
#16001 medium
Errors

Description 16001 16 No Data masking is not supported for the data type of column '%.*ls'. 16002 16 No Invalid data masking function in column '%.*ls'.

#io#severity-medium
#16106 medium
Errors

Description 16106 16 No Option '%.*ls' is empty. 16107 16 No Schema '%.*ls' was not found or you do not have permission to access it. 16108 16 No Table '%.*ls' was not found or you do not have permiss

#io#severity-medium
#16208 medium
Errors

Description 16208 15 No The function '%.*ls' does not support %.*ls. 16209 15 No The PARTITION=ALL clause must be specified to enable XML compression for the table or index.

#io#severity-medium
#16506 medium
Errors

Description 16506 16 No The column name starting with '%.*ls' is too long. The maximum length is %d characters. Underlying data description: %ls. 16507 16 No String or binary data would be truncated w

#io#severity-medium
#16522 medium
Errors

Description 16522 10 No %.*ls input argument should be a OPENROWSET BULK query which uses external extraction. 16523 16 Yes Execution service has shut down so performing distributed computation cannot

#io#severity-medium
#16543 medium
Errors

Description 16543 16 No %ls is not supported for specified file format. 16544 16 No The maximum reject threshold is reached. 16545 10 No Warning: Rejected rows encountered during execution. 16546 16 N

#io#severity-medium
#16559 medium
Errors

Description specify explicit column schema in WITH clause and assign UTF8 collation to VARCHAR columns. 16559 16 No CODEPAGE different than 65001 is not supported when CSV 2.0 is specified. 16560 16 N

#io#severity-medium
#16577 medium
Errors

Description 16577 16 No Number of wildcards in LOCATION must match the number of columns in PARTITION clause. 16578 16 No The column name '%.*ls' specified in the PARTITION option does not match any c

#io#severity-medium
#16596 medium
Errors

Description 16596 16 No The specified location is invalid: '%ls'. 16597 16 No The specified storage account does not have hierarchical namespace enabled. 16598 16 No Cannot access the specified locati

#io#severity-medium
#16616 medium
Errors

Description 16616 16 No Cannot update sync schema because the data type change is not supported. 16617 16 No Sync group '%ls' is not ready to update sync schema because there are some ongoing operatio

#io#severity-medium
#16634 medium
Errors

Description 16634 16 No Sync agent '%ls' is invalid. 16635 16 No Cannot create sync group '%ls' because the maximum number of basic sync groups can be created is %d.

#io#severity-medium
#16655 medium
Errors

Description 16655 16 No Cannot add column '%ls' from table '%ls' to schema because the data type of this column is '%ls'.

#io#severity-medium
#16720 medium
Errors

Description 16720 16 No LTR Backup Copy/Storage Update feature is not supported for Hyperscale Database LTR Backups currently. 16721 16 No LTR Migration not supported between source and target databas

#io#severity-medium
#16735 medium
Errors

Description 16735 16 No The provided long-term retention backup resource ID or backup name is incorrect. 16901 16 No %hs: This feature has not been implemented yet. 16902 16 No %ls: The value of the p

#io#severity-medium
#16931 medium
Errors

Description 16931 16 No There are no rows in the current fetch buffer. 16932 16 No The cursor has a FOR UPDATE list and the requested column to be updated is not in this list. 16933 16 No The cursor d

#io#severity-medium
#16953 medium
Errors

Description call. 16953 10 No Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning

#io#severity-medium
#17001 medium
Errors

Description 17001 16 Yes Failure to send an event notification instance of type '%s' on conversation handle '%s'. Error Code = '%s'. 17002 16 Yes Failed to post QUEUE_ACTIVATION event. Error code: '0x

#io#severity-medium
#17066 medium
Errors

Here are some possible reasons for an assert failure to occur: A common reason for assert failures are issues in the product that lead to the conditions not to be true. These issues need to be investi

#corruption#severity-medium
#17108 medium
Errors

Description initialize and are disabled. 17108 10 Yes Password policy update was successful. 17109 10 Yes FallBack certificate was successfully created. 17110 10 Yes Registry startup parameters: %.*ls

#connection#severity-medium
#17123 medium
Errors

Description DATABASE. 17123 10 Yes Logging to event log is disabled. Startup option '-%c' is supplied, either from the registry or the command prompt. 17124 10 Yes SQL Server has been configured for l

#connection#severity-medium
#17139 medium
Errors

Description 17139 10 Yes The SQL Server image %ls was allocated using the large pages option. 17140 16 Yes Could not dispatch SQL Server by Service Control Manager. Operating system error = %s. 17141

#connection#severity-medium
#17156 medium
Errors

Description 17156 16 Yes initeventlog: Could not initiate the EventLog Service for the key '%s', last error code is %d. 17158 10 Yes The server resumed execution after being idle %d seconds. This is a

#io#severity-medium
#17173 medium
Errors

Description 17173 10 Yes 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.

#connection#severity-medium
#17189 medium
Errors

Description 17189 16 Yes 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 error log for informatio

#connection#severity-medium
#17200 medium
Errors

Description 17200 16 Yes Changing the remote access settings for the Dedicated Admin Connection failed with x%lx, status code 0x%lx.

#connection#severity-medium
#17204 medium
Errors

If a user database runs into these errors, that database will be left in the RECOVERY_PENDING state and applications cannot access the database. If a system database encounters these errors, the SQL S

#io#severity-medium
#17207 medium
Errors

scenarios, you may see both 17207 and 17204 errors and in other occasions you might just see one of them. If a user database runs into these errors, that database will be left in the RECOVERY_PENDING

#io#severity-medium
#17260 medium
Errors

Description 17260 10 Yes Dedicated admin connection support was established for listening remotely on named pipe [ %s ]. 17261 16 Yes initdata: No shared memory for kernel buffers. 17262 16 Yes Replic

#connection#severity-medium
#17313 medium
Errors

Description 17313 10 Yes Unable to locate driver ntdll.dll in path. SQL Server native HTTP support is not available. x%lx Your operating system may not support this driver. 17401 10 Yes Server resumed

#corruption#severity-medium
#17418 medium
Errors

Description 17418 10 Yes Detected %.*ls %.*ls. 17419 10 Yes %.*ls hardware detected on the system. 17420 10 Yes %.*ls hardware not found on the system.

#io#severity-medium
#17572 medium
Errors

Description 17572 16 Yes DBCC cannot free DLL '%ls'. SQL Server requires this DLL in order to function properly. 17573 10 Yes CHECKDB for database '%ls' finished without errors on %ls (local time). Th

#connection#severity-medium
#17803 medium
Errors

Description closed. %.*ls 17803 20 Yes There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed

#connection#severity-medium
#17821 medium
Errors

Description 17821 20 No A valid TLS certificate is not configured to accept strict (TDS 8.0 and above) connections. The connection has been closed.

#connection#severity-medium
#17832 medium
Errors

If the token was improperly created or damaged during transmission, SQL Server cannot offer additional information about the problem.

#io#severity-medium
#17883 medium
Errors

If kernel mode time climbs quickly, the thread is spending most its time in the operating system, and requires kernel debugging to determine the root cause of this behavior.

#io#severity-medium
#17890 medium
Errors

For detailed t-shooting steps, see MSSQLSERVER_17890 1. Configure SQL Server Max Server Memory to a value that allows for the OS and other process use have memory available.

#io#severity-medium
#17892 medium
Errors

No description available.

#io#severity-medium
#17896 medium
Errors

Description 17896 20 Yes The Tabular Data Stream (TDS) version 0x%x of the client library used to recover a dead connection is unsupported or unknown.

#connection#severity-medium
#18002 medium
Errors

Description 18002 20 Yes Exception happened when running extended stored procedure '%.*ls' in the library '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. To

#connection#severity-medium
#18113 medium
Errors

Description 18113 10 Yes SQL Server shutdown after verifying system indexes. 18124 10 Yes The default collation was successfully changed.

#io#severity-medium
#18210 medium
Errors

are helpful in that you get a timestamp of when a backup failed.

#io#severity-medium
#18268 medium
Errors

Description 18268 10 Yes 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 is an informational messag

#io#severity-medium
#18280 medium
Errors

Description the checkpoint file and try the operation again.

#connection#severity-medium
#18320 medium
Errors

Description 18320 10 No Reason: SQL Server service is paused. Login could not be revalidated at this time.

#connection#severity-medium
#18339 medium
Errors

Description 18339 10 No Reason: Failed to open the database '%.*ls' specified in the login properties. 18340 10 No Reason: Failed to store database name and collation. Check for previous errors. 18341

#connection#severity-medium
#18358 medium
Errors

Description 18358 10 No Reason: Could not find a user matching the name provided. [Database: '%.*ls'] 18359 10 No Reason: Failed to unprotect memory containing sensitive information. [Database: '%.*ls

#connection#severity-medium
#18376 medium
Errors

Description 18376 10 Yes Reason: Failed to open the database '%.*ls' configured in the session recovery object while revalidating the login on the recovered connection. 18377 10 No Reason: The current

#connection#severity-medium
#18397 medium
Errors

Description 18397 10 No Reason: Unable to retrieve database firewall rules. 18398 10 No Reason: Catch exception from FindLogin during contained database authentication. 18399 10 No Reason: Unsecured c

#connection#severity-medium
#18456 medium
Errors

- Grant the login access to the database by creating the corresponding user (for example, ) Also, check the extensive list of error codes at Troubleshooting . For more troubleshooting help, see Troub

#connection#severity-medium
#18463 medium
Errors

'Description 18463 14 No The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls 18464 14 No Login failed for user ''%.*ls''. Reason: Password chang'

#connection#severity-medium
#18491 medium
Errors

Description 18491 16 Yes SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server. 18492 16

#connection#severity-medium
#18755 medium
Errors

Description 18755 16 No Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations. 18756 16 No Could not retrieve replication information for table %d.

#io#severity-medium
#18775 medium
Errors

Description 18775 16 No The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.

#io#severity-medium
#18799 medium
Errors

Description 18799 16 No Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database. 1880

#io#severity-medium
#18818 medium
Errors

Description 18818 16 No Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18819 16 No Failed to lock the current log record at log sequence number (LS

#io#severity-medium
#18837 medium
Errors

Description 18837 16 No Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication. 18838 16 N

#io#severity-medium
#18853 medium
Errors

Description returned '%ld'. If the problem persists, contact Customer Support Services.

#io#severity-medium
#19030 medium
Errors

'Description 19030 10 Yes SQL Trace ID %d was started by login "%s". 19031 10 Yes SQL Trace stopped. Trace ID = ''%d''. Login Name = ''%s''. 19032 10 Yes SQL Trace was stopped due to server shutdown. Trace'

#io#severity-medium
#19063 medium
Errors

Description 19063 16 No Not enough memory was available for trace. 19064 16 No The requested trace stop time has been already passed. 19065 16 No The parameter is not valid. 19066 16 No Cannot modify

#io#severity-medium
#19108 medium
Errors

Description 19108 10 No Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings. 19109 10 No Unable to configure MDAC-compatibility TCP/IP port in registry. 19110 10 No Unab

#io#severity-medium
#19129 medium
Errors

Description 19129 10 No 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 Server Configuration Manage

#connection#severity-medium
#19148 medium
Errors

Description 19148 10 No Unable to initialize SSL support. 19149 10 No Unable to configure MDAC-compatibility protocol list in registry. 19150 10 No Unable to open SQL Server Network Interface library

#connection#severity-medium
#19200 medium
Errors

Description 19200 10 No Authentication succeeded. 19201 10 No The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream. 19202 10 No An

#connection#severity-medium
#19213 medium
Errors

Description 19213 10 No The IP Address element of the received Service Principal Name (SPN) is not valid. 19214 10 No The Host element of the received Service Principal Name (SPN) is not valid. 19215

#connection#severity-medium
#19231 medium
Errors

Description 19231 10 No Failed to allocate an object to perform a cryptographic handshake. 19232 10 No Failed to initialize an object to perform a cryptographic handshake. 19233 10 No A token from a c

#connection#severity-medium
#19306 medium
Errors

Description 19306 16 No The provided Pattern is too complex. Please retry by reducing the complexity of Pattern - '%.*ls'. 19307 16 No Encountered an unexpected '%.*ls' in the Pattern %.*s. 19308 16 N

#io#severity-medium
#19405 medium
Errors

Description 19405 16 No 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 one replica is failover c

#io#severity-medium
#19412 medium
Errors

Description CONFIGURATION SET HADR CLUSTER CONTEXT = 'remote_wsfc_cluster_name' command. 19412 16 No The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command failed. The current Windo

#io#severity-medium
#19419 medium
Errors

Description Clustering (WSFC) cluster name,'%.*ls', was specified. Retry the command, specifying the name of a remote WSFC cluster. 19419 16 No Windows Server Failover Cluster did not receive a proces

#io#severity-medium
#19436 medium
Errors

Description error %d, severity %d, state %d. 19436 16 No Always On Availability Groups: A failure [%d] was encountered while waiting for LSN %S_LSN to be hardened on the Commit Manager [%d] for databa

#io#severity-medium
#19458 medium
Errors

Description for the cluster-allowed IP range. 19458 16 No The WSFC nodes that host the primary and secondary replicas belong to different subnets.

#io#severity-medium
#19468 medium
Errors

'Description error code, see "System Error Codes" in the Windows Development documentation. 19468 16 No The listener with DNS name ''%.*ls'' for the availability group ''%.*ls'' is already listening on the'

#io#severity-medium
#19477 medium
Errors

Description the WSFC cluster and validate the network name and IP address with the network administrator. Otherwise, contact your primary support provider. 19477 16 No The availability group '%.*ls' a

#io#severity-medium
#19487 medium
Errors

'Description For information about altering an availability group listener, see the "ALTER AVAILABILITY GROUP (Transact-SQL)" topic in SQL Server Books Online. 19487 16 No Listener configuration change'

#io#severity-medium
#19497 medium
Errors

Description 19497 16 No Conflicting option spec provided. DISTRIBUTED option cannot be combined with any other availability group options.

#io#severity-medium
#19511 medium
Errors

Description existing distributed availability group. 19511 16 No Cannot join distributed availability group '%.*ls'. The local availability group '%.*ls' contains one or more databases.

#io#severity-medium
#19523 medium
Errors

Description contact your primary support provider. 19523 16 No The specified '%.*ls' of Availability Group must be less than 256 characters long.

#io#severity-medium
#19533 medium
Errors

Description 19533 16 No Cannot create distributed availability group '%.*ls' as it requires two Availaiblity Group Replicas, however %d were specified.

#io#severity-medium
#19545 medium
Errors

Description Please change the name of availability group '%.*ls' to be 64 characters or less and try again. 19545 16 No 'ALTER AVAILABILITY GROUP' command failed for internal distributed availability

#connection#severity-medium
#19558 medium
Errors

Description 19558 16 No Duplicate key '%.*ls' in %.*ls. 19559 16 No The key 'Encrypt' must be specified in %.*ls. 19601 16 No System error. 19602 16 No System error. 19603 16 No System error. 19604 16

#io#severity-medium
#19704 medium
Errors

Description 19704 16 No Missing %ls in ROWSET_OPTIONS. It is required when %ls is set. 19705 17 No Failed to create a new database due to system error.

#io#severity-medium
#19724 medium
Errors

Description 19724 17 No Database could not be successfully attached to appropriate DB ID. 19725 16 No Column mapping is not enabled. 19726 16 No Feature '%ls' is not supported for table '%ls'. 19727 1

#connection#severity-medium
#19743 medium
Errors

Description 19743 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19744 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19745

#io#severity-medium
#19759 medium
Errors

Description 19759 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19760 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19761

#io#severity-medium
#19775 medium
Errors

Description 19775 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19776 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19777

#io#severity-medium
#19790 medium
Errors

Description 19790 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19791 16 No Error encountered while parsing data: '%ls'. Underlying data description: %ls. 19792

#connection#severity-medium
#19810 medium
Errors

Description 19810 17 Yes Login failed for user '%.*ls' as storage SAS token refresh was delayed or failed. Only backend connections are allowed.%.*ls 19811 16 No Maximum LOB value size has been exceed

#connection#severity-medium
#19828 medium
Errors

Description 19828 16 No Column count mismatch, the column count in the file doesn't match column count in the table schema. Column '%ls' is not present in the file. Set the MATCH_COLUMN_COUNT option t

#io#severity-medium
#20006 medium
Errors

Description 20006 16 No Cannot make the change because the article might be in a publication that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 to acknowledge that such a

#io#severity-medium