SQL Server Error Messages 16001 to 17000

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

SQL Server Error Messages 16001 to 17000

ErrorCodeSeverityErrorMessage
1600116Data masking is not supported for the data type of column ‘%.*ls’.
1600216Invalid data masking function in column ‘%.*ls’.
1600316The data type of column ‘%.*ls’ does not support data masking function ‘%.*ls’.
1600416Incorrect number of parameters for data masking function ‘%.*ls’ for column ‘%.*ls’.
1600516Invalid argument for data masking function ‘%.*ls’ for column ‘%.*ls’.
1600616Invalid data masking format for function ‘%.*ls’ in column ‘%.*ls’.
1600716The column ‘%.*ls’ does not have a data masking function.
1600816Cannot add a masking function to a column that is encrypted.
1600916Cannot add a masking function to a column used as a sparse column set.
1601016External script cannot be executed on masked data columns.
1601116The data masking function for column ‘%.*ls’ is too long.
1601216The query accessed too many different databases.
1601316Cannot add a masking function to a column used in a key to a fulltext index.
1601416Failed to create fulltext index because key column ‘%.*ls’ has a masking function defined on it.
1601516The index on view ‘%.*ls’ cannot be created because the view is referencing table ‘%.*ls’ with masked columns.
1601616Cannot add a masking function to a column used in a sparse column set.
1610116Option ‘%.*ls’ is not supported for sensitivity classification.
1610216Object name specified ‘%.*ls’ is not valid.
1610316Sensitivity classification is not supported for the specified object.
1610416Sensitivity classification option ‘%.*ls’ was repeated.
1610516Option ‘%.*ls’ is too long (max %d chars).
1610616Option ‘%.*ls’ is empty.
1610716Schema ‘%.*ls’ was not found or you do not have permission to access it.
1610816Table ‘%.*ls’ was not found or you do not have permission to access it.
1610916Column ‘%.*ls’ was not found in table ‘%.*ls’ or you do not have permission to access it.
1611016Specification of database part of object name is not supported.
1611116Sensitivity classification operations cannot be used on computed column ‘%.*ls’.
1611216Sensitivity classifications cannot be added to a history table directly.
1611316Sensitivity rank must not be provided as string.
1611416Sensitivity rank must be one of the following: NONE, LOW, MEDIUM, HIGH, CRITICAL.
1611516‘%.*ls’ option’s value must be provided as string.
1611616Object ‘%.*ls’ is not a table.
1620016The statement failed because ‘APPROX_COUNT_DISTINCT’ does not support DISTINCT <column-name> parameters. Consider using ‘APPROX_COUNT_DISTINCT’ without DISTINCT, or COUNT or COUNT_BIG with DISTINCT.
1620116The statement failed because ‘%.*ls’ does not support DISTINCT <column-name> parameters.
1620216Keyword or statement option ‘%.*ls’ is not supported on the ‘%.*ls’ platform.
1620315The option “INLINE=ON” is not valid for this function. Check the documentation for the constructs supported with INLINE option in a function.
1620415Invalid column ordinal provided for column %d. Column ordinal has to be greater than zero.
1620515Invalid read length provided in OPENROWSET query. Length has to be greater than zero.
1630116User ‘%.*ls’ not found.
1630216Role ‘%.*ls’ not found.
1630316‘%.*ls’ is not a feature than can be restricted.
1630416‘%.*ls’ is not an object class than can be restricted.
1630516The database does not support feature restrictions.
1630616Failed to add the feature restriction.
1630716Failed to drop the feature restriction.
1630816Invalid parameter ‘%.*ls’: Must be unicode string with length between 1 and 127.
1630916Feature restrictions are not allowed for the dbo user.
1660116Credential of database ‘%ls’ are invalid.
1660216Cannot delete sync agent ‘%ls’ because it is used by sync member ‘%ls’.
1660316Cannot add database ‘%ls’ into sync group because the database name is invalid.
1660416Hub database ‘%ls’ is invalid.
1660516Member database ‘%ls’ is invalid.
1660616Database ‘%ls’ cannot be deleted because it is used as a sync metadata database which still contains sync groups and/or sync agents.
1660716Sync metadata database ‘%ls’ is invalid.
1660816Cannot create or update sync group because the sync group name ‘%ls’ is invalid.
1660916Cannot create or update sync group ‘%ls’ because the conflict resolution policy is invalid.
1661016Cannot create sync group because the sync group name ‘%ls’ is used.
1661116Cannot create or update sync group ‘%ls’ because the sync schema contains circular reference.
1661216Cannot create or update sync group ‘%ls’ because the table ‘%ls’ in sync schema contains no clustered index.
1661316Cannot delete sync group ‘%ls’ because the sync group is syncing.
1661416Cannot create or update sync group ‘%ls’ because database ‘%ls’ is invalid.
1661516Cannot create or update sync group ‘%ls’ because the sync interval is invalid.
1661616Cannot update sync schema because the data type change is not supported.
1661716Sync group ‘%ls’ is not ready to update sync schema because there are some ongoing operations on the sync group.
1661816Cannot update sync schema because some columns are missing in database ‘%ls’.
1661916Cannot update sync schema because some tables are missing in database ‘%ls’.
1662016Cannot update sync schema because the format of sync schema is invalid.
1662116Sync group ‘%ls’ is not in active state. Make sure the sync schema of it is set.
1662216Hub database ‘%ls’ is suspended because the credential of it is invalid.
1662316Sync group ‘%ls’ is invalid.
1662416Cannot create or update sync member because the sync member name ‘%ls’ is invalid.
1662516Cannot create or update the sync member ‘%ls’ because the database type ‘%ls’ provided is invalid.
1662616Cannot create or update the sync member ‘%ls’ because the sync direction ‘%ls’ provided is invalid.
1662716Cannot create or update the sync member ‘%ls’ because the sync agent ‘%ls’ provided is invalid.
1662816Cannot create or update the sync member ‘%ls’ because the SQL Server database ID ‘%ls’ provided is invalid.
1662916Cannot create sync member because the sync member name ‘%ls’ provided is used.
1663016Cannot create sync member ‘%ls’ because the database ‘%ls’ provided is already added as a sync member.
1663116Cannot delete sync member ‘%ls’ when it is syncing.
1663216Sync member ‘%ls’ does not exist.
1663316Cannot create sync agent because the sync agent name ‘%ls’ provided is used.
1663416Sync agent ‘%ls’ is invalid.
1663516Cannot create sync group ‘%ls’ because the maximum number of basic sync groups can be created is %d.
1663616Cannot create sync member ‘%ls’ because the maximum number of sync members can be created in a sync group is %d.
1663716Cannot create or update sync group ‘%ls’ because the maximum count of tables in sync schema is %d.
1663816Cannot create or update sync group ‘%ls’ because the table ‘%ls’ in sync schema contains no primary key.
1663916Cannot create or update sync group ‘%ls’ because the sync schema provided contains unsupported column data type.
1664016Cannot refresh schema of the database ‘%ls’.
1664116Cannot create sync agent ‘%ls’ under a different SQL Server than the one of sync metadata database.
1664216Conflict logging retention period parameter is required if conflict logging is turned on.
1664316Data Sync conflict logging feature is not enabled.
1664416Value for data Sync conflict logging retention in days should be positive or zero.
1664516The sync group is already being dropped.
1664616The sync member is already being dropped.
1664716Failed to perform data sync operation: %ls
1664816The sync database specified (%ls\\%ls) does not match the existing sync database (%ls\\%ls).
1664916Hub logical server %ls does not exist.
1665016The sync agent %ls already exists.
1665116The sync agent with the id %ls already exists.
1665216Cannot update the sync group because it is currently being dropped.
1665316Cannot use datawarehouse edition in data sync.
1665416Cannot use logical master in data sync.
1690116%hs: This feature has not been implemented yet.
1690216%ls: The value of the parameter %ls is invalid.
1690316The “%ls” procedure was called with an incorrect number of parameters.
1690416sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE.
1690516The cursor is already open.
1690617Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more.
1690716%hs is not allowed in cursor statements.
1690916%ls: The cursor identifier value provided (%x) is not valid.
1691016The cursor %.*ls is currently used by another statement.
1691116%hs: The fetch type %hs cannot be used with forward only cursors.
1691416The “%ls” procedure was called with too many parameters.
1691516A cursor with the name ‘%.*ls’ already exists.
1691616A cursor with the name ‘%.*ls’ does not exist.
1691716Cursor is not open.
1692216Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
1692416Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
1692516The fetch type %hs cannot be used with dynamic cursors.
1692616sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
1692716Cannot fetch into text, ntext, and image variables.
1692816sp_cursor: Exec statement is not allowed as source for cursor insert.
1692916The cursor is READ ONLY.
1693016The requested row is not in the fetch buffer.
1693116There are no rows in the current fetch buffer.
1693216The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.
1693316The cursor does not include the table being modified or the table is not updatable through the cursor.
1693410Optimistic concurrency check failed. The row was modified outside of this cursor.
1693516No parameter values were specified for the sp_cursor-%hs statement.
1693616sp_cursor: One or more values parameters were invalid.
1693716A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
1693816sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
1694116Cursor updates are not allowed on tables opened with the NOLOCK option.
1694216Could not generate asynchronous keyset. The cursor has been deallocated.
1694316Could not complete cursor operation because the table schema changed after the cursor was declared.
1694516The cursor was not declared.
1694616Could not open the cursor because one or more of its tables have gone out of scope.
1694716No rows were updated or deleted.
1694816The variable ‘%.*ls’ is not a cursor variable, but it is used in a place where a cursor variable is expected.
1694916The variable ‘%.*ls’ is a cursor variable, but it is used in a place where a cursor variable is not valid.
1695010The variable ‘%.*ls’ does not currently have a cursor allocated to it.
1695116The variable ‘%.*ls’ cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure.
1695216A cursor variable cannot be used as a parameter to a remote procedure call.
1695310Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor.
1695416Executing SQL directly; no cursor.
1695516Could not create an acceptable cursor.
1695610The created cursor is not of the requested type.
1695716FOR UPDATE cannot be specified on a READ ONLY cursor.
1695816Could not complete cursor operation because the set options have changed since the cursor was declared.
1695916Unique table computation failed.
1696016You have reached the maximum number of cursors allowed.
1696110One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query.
1696216The target object type is not updatable through a cursor.
1696316You cannot specify scroll locking on a cursor that contains a remote table.
1696416For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
1696516Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch.
1696616%ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors.
1699216The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue.
1699616%ls cannot take output parameters.
1699816The asynchronous cursor worktable population thread spawn failed.
1699920Internal Cursor Error: The cursor is in an invalid state.
1700010Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ]