Skip Navigation Links
Home
Articles
SQL Server 2012
SQL Server 2014
SQL Server 2016
FAQ
Forums
Practice Test
Bookstore
Tip of the Day : SQL Server 2012 Management Studio Keyboard Shortcuts - Cut and Paste
Error Messages
Home > Tips & Tricks > Error Messages 10501 to 11000
SQL Server Error Messages - Errors 10501 to 11000

A message number uniquely identifies each error message and the error message text describes the problem.  The error message text often includes placeholders for information (such as object names) to be inserted in the error message when it is displayed.  Unfortunately, the error message text does not tell you how to solve or work around the problem.  In this series of Error Messages list, we will try to provide you with ways on how to overcome or work around certain error messages.

Some error messages are self-explanatory and can easily be fixed, such as "Invalid object name".  Others are harder to fix or work around, especially by those who are new to SQL Server.  It is the intent of this page and succeeding pages (to come) to assist you in addressing or working around SQL Server error messages.

Error Severity Description
10501 16 Cannot create plan guide '%.*ls' because type '%.*ls' provided is not allowed.
10502 16 Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, matches the existing plan guide '%.*ls' in the database. Drop the existing plan guide before creating the new p
10503 16 Operation '%.*ls' is not allowed.
10504 16 Cannot create plan guide '%.*ls' because parameter @hints is incorrect. Use N'OPTION ( <query_hintgt; [ ,...n ] )'.
10505 16 Cannot create plan guide '%.*ls' because value '%.*ls' provided for @module_or_batch is not legal two-part name. Use 'schema_name.object_name'.
10506 16 Cannot create plan guide '%.*ls' because parameter @stmt has more than one statement.
10507 16 Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, does not match any statement in the specified module or batch. Modify the values to match a statement in the mo
10508 16 Cannot '%ls' plan guide '%.*ls' because it does not exist or you do not have permission. Verify plan guide name and database of current session, and that you have needed permission.
10509 16 Cannot create plan guide '%.*ls' because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is ineligible for use in a plan guide. Provide a single valid Transact-SQL statement or a valid starting position of the
10510 16 Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name.
10512 16 Cannot create plan guide '%.*ls' because object '@module_or_batch' is encrypted. Consider tuning query using other techniques such as indexes and statistics.
10513 16 Cannot %S_MSG %S_MSG '%.*ls' because it is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
10515 16 Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission.
10516 16 Cannot create plan guide '%.*ls' because @module_or_batch can not be compiled.
10517 16 Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required.
10518 16 Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide '%.*ls'. Alter permission on object referenced by plan guide, or alter database permission required.
10519 16 Cannot create plan guide '%.*ls' because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statement_start_offset. Verify that the hints can be applied to the statement.
10520 16 Cannot create plan guide '%.*ls' because @type was specified as '%ls' and a non-NULL value is specified for the parameter '%ls'. This type requires a NULL value for the parameter. Specify NULL for the parameter, or change the type to one that allows a non
10521 16 Cannot create plan guide '%.*ls' because @type was specified as '%ls' and the parameter '%ls' is NULL. This type requires a non-NULL value for the parameter. Specify a non-NULL value for the parameter, or change the type to one that allows a NULL value fo
10522 16 Cannot create plan guide '%.*ls' because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) if @type is 'template'.
10523 16 Cannot generate query template because @querytext does not contain a valid single query.
10524 16 Cannot parameterize @querytext.
10525 10 Plan guide '%.*ls' matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains was ignored. RECOMPILE is not supported on automatically parameterized statements. Consider dropping thi
10526 16 Cannot drop %S_MSG '%.*ls' because its trigger '%.*ls' is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
10527 16 Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object.
10528 16 Cannot create plan guide '%.*ls' because its name is invalid. Plan guide name cannot begin with a '#' character.
10529 16 Cannot create plan guide '%.*ls' because there is already a planguide '%.*ls' of @type 'template' on @stmt.
10530 16 Cannot create plan guide '%.*ls' because the statement specified by @statement_start_offset does not match any statement in specified module or batch. Consider modifying @statement_start_offset to match a statement in module or batch.
10531 16 Cannot create plan guide '%.*ls' from cache because the user does not have adequate permissions. Grant the VIEW SERVER STATE permission to the user creating the plan guide.
10532 16 Cannot create plan guide '%.*ls' because the batch or module specified by @plan_handle does not contain a statement that is eligible for a plan guide. Specify a different value for @plan_handle.
10533 16 Cannot create plan guide '%.*ls' because the plan guide name exceeds 124, the maximum number of characters allowed. Specify a name that contains fewer than 125 characters.
10534 16 Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form <parameter_namegt; <parameter_typegt;, or specify NULL.
10535 16 Cannot create plan guide '%.*ls' because a plan was not found in the plan cache that corresponds to the specified plan handle. Specify a cached plan handle. For a list of cached plan handles, query the sys.dm_exec_query_stats dynamic management view.
10536 16 Cannot create plan guide '%.*ls' because the batch or module corresponding to the specified @plan_handle contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a statement_start_offset valu
10537 16 Cannot enable plan guide '%.*ls' because the enabled plan guide '%.*ls' contains the same scope and starting offset value of the statement. Disable the existing plan guide before enabling the specified plan guide.
10538 16 Cannot find the plan guide either because the specified plan guide ID is NULL or invalid, or you do not have permission on the object referenced by the plan guide. Verify that the plan guide ID is valid, the current session is set to the correct database
10539 16 Cannot create plan guide '%.*ls' from cache because a query plan is not available for the statement with start offset %d.This problem can occur if the statement depends on database objects that have not yet been created. Make sure that all necessary datab
10601 16 Cannot specify included columns for a clustered index.
10602 16 Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
10603 16 Cannot rebuild clustered index '%.*ls' on view '%.*ls' because the view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disabled.
10604 16 Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
10605 16 Cannot disable primary key index "%.*ls" on table "%.*ls" because the table is published for replication.
10606 16 Cannot disable the clustered index "%.*ls" on view "%.*ls" because the indexed view is published for replication.
10607 16 The clustered index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Disable change tracking on the table before disabling the clustered index.
10608 16 The index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Change tracking requires a primary key constraint on the table, and disabling the index will drop the constraint. Disable change tracking on the table bef
10609 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is a computed column. Rewrite the filter expression so that it does not include this column.
10610 16 Filtered index '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered indexes are only supported on tables. If you are trying to create a filtered index on a view, consider creating an indexed view with the filter expression
10611 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant of higher data type precedence or of a different collation. Converting a column to the data type of a constant is no
10612 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant that cannot be converted to the data type of the column. Rewrite the filter expression so that it does not include t
10617 16 Index '%.*ls' could not be created or rebuilt. The key length for this index (%d bytes) exceeds the maximum allowed length of '%d' bytes when using the vardecimal storage format.
10618 16 Cannot %S_MSG filtered index '%.*ls' on table '%.*ls' because the statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it does not use the IGNORE_DUP_KEY option.
10619 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is of a CLR data type. Rewrite the filter expression so that it does not include this column.
10620 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the filter expression contains a comparison with a literal NULL value. Rewrite the comparison to use the IS [NOT] NULL comparison operator to test for NULL values.
10621 16 The index '%.*ls' on table '%.*ls' could not be created because the column '%.*ls' in the filter expression of the index is a column set.
10622 16 The %S_MSG '%.*ls' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set column.
10623 16 Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user tables.
10631 16 Index '%.*ls' could not be created or rebuilt. A unique or clustered index on a federated table must contain the federated column.
10632 16 Index '%.*ls' could not be created. Views cannot be indexed in a federated database.
10633 16 Invalid online index creation operation
10700 16 The table-valued parameter "%.*ls" is READONLY and cannot be modified.
10701 15 The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement.
10702 15 The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification.
10703 15 Too many grouping sets. The maximum number is %d.
10704 15 To rethrow an error, a THROW statement must be used inside a CATCH block. Insert the THROW statement inside a CATCH block, or add error parameters to the THROW statement.
10705 15 Subqueries are not allowed in the OUTPUT clause.
10706 15 Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied.
10707 15 The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 mode or higher.
10708 15 DEFAULT is not allowed on the right hand side of "%.*ls"
10709 15 The number of columns for each row in a table value constructor must be the same.
10710 15 An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
10711 15 An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement.
10713 15 A MERGE statement must be terminated by a semi-colon (;).
10714 15 An action of type '%S_MSG' cannot appear more than once in a '%S_MSG' clause of a MERGE statement.
10716 15 A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause.
10717 15 The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
10718 15 Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements.
10720 15 An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
10721 15 The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
10722 15 The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
10723 15 In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of the form 'SET @variable = column = expression' are not valid in the SET clause of an UPDATE action in a
10724 15 The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
10725 15 Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
10726 15 User defined aggregates do not support default parameters.
10727 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.
10728 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.
10729 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statement.
10730 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.
10731 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.
10732 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.
10733 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.
10734 16 Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.
10735 15 Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.*ls'.
10736 15 A full-text stoplist statement must be terminated by a semi-colon (;).
10737 15 In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specified. The PARTITION=ALL clause is used to reinforce that all partitions of the table or index will be rebuil
10738 15 The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.
10739 15 The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.
10740 15 A search property list statement must end with a semicolon (;).
10741 15 A TOP can not be used in the same query or sub-query as a OFFSET.
10742 15 The offset specified in a OFFSET clause may not be negative.
10743 15 The number of rows provided for a OFFSET clause must be an integer.
10744 15 The number of rows provided for a FETCH clause must be greater then zero.
10745 15 The FORCESCAN hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
10746 15 The FORCESCAN hint is specified simultaneously with the FORCESEEK hint. Remove one of the hints and resubmit the query.
10747 15 The parameterized FORCESEEK hint cannot be simultaneously used with INDEX hints or a non-parameterized FORCESEEK hint on the same object. Use either INDEX hints and a non-parameterized FORCESEEK hint or use a parameterized FORCESEEK hint without INDEX hin
10748 15 There are multiple FORCESEEK hints specified on the same table or view. Remove the extra FORCESEEK hints and resubmit the query.
10749 15 The FORCESEEK hint cannot be used with index 0. Correct the index provided to the FORCESEEK hint and resubmit the query.
10750 15 The FORCESCAN hint cannot be used with more than one INDEX hint. Remove the extra INDEX hints and resubmit the query.

Error Severity Description
10751 15 The ORDER BY in WITHIN GROUP clause of '%.*ls' function must have exactly one expression.
10752 15 The function '%.*ls' may not have a window frame.
10753 15 The function '%.*ls' must have an OVER clause.
10754 15 The function '%.*ls' must have a WITHIN GROUP clause.
10755 15 The function '%.*ls' takes between %d and %d arguments.
10756 15 Window frame with ROWS or RANGE must have an ORDER BY clause.
10757 15 The function '%.*ls' may not have a WITHIN GROUP clause.
10758 15 The function '%.*ls' may not have ORDER BY in OVER clause.
10759 15 Use of DISTINCT is not allowed with the OVER clause.
10760 16 Scale argument is not valid. Valid expressions for data type %ls scale argument are integer constants and integer constant expressions.
10761 16 Invalid data type %.*ls in function %.*ls.
10762 16 The %.*ls function is not allowed in the current compatibility mode. It is only allowed in 110 mode or higher.
10763 15 GROUP BY clause can only contain one query hint. Remove the extra hints and re-run the query.
10764 15 Number of grouping columns in the query exceeded maximum number allowed. SQL Server allows 64k grouping columns. Reduce number of grouping columns and re-run the query.
10765 15 DISTRIBUTED_AGG and CENTRAL_AGG hints cannot be used with a CUBE or ROLLUP clause. Modify the query and re-run it.
10766 15 CENTRAL_AGG must be specified after all columns in the GROUP BY clause. Modify the query and re-run it.
10767 15 DISTRIBUTED_AGG hint cannot be used when the GROUP BY clause contains the same column more than once. Modify the query and re-run it.
10768 15 LABEL hint can only be used one time in the query. Modify the query and re-run it.
10770 15 The %S_MSG '%ls' is not supported with in-memory tables.
10771 15 The %S_MSG '%ls' is not yet implemented with in-memory tables.
10772 15 The %S_MSG '%ls' is not supported with natively compiled stored procedures.
10773 15 The %S_MSG '%ls' is not yet implemented with natively compiled stored procedures.
10774 16 Index '%.*ls' cannot be created on an in-memory table because it is non-covering.
10775 16 Table or view '%.*ls' is not an in-memory table and cannot be accessed from a natively compiled stored procedure.
10776 16 Table '%.*ls' is an in-memory table and can only be accessed from a natively compiled stored procedure.
10777 16 Procedure '%.*ls' cannot be executed because it is a natively compiled procedure that has not been deployed.
10778 16 Cannot create a hekaton table without columns.
10779 16 Deployment failed for procedure '%.*ls' because of compilation errors.
10780 16 Conversion from '%ls' to '%ls' is not yet implemented with natively compiled stored procedures.
10781 16 The object '%.*ls' is not an in-memory table.
10782 16 BEGIN ATOMIC is only supported inside natively compiled stored procedures.
10783 16 The body of a natively compiled stored procedures must be an ATOMIC block.
10784 16 The WITH clause of BEGIN ATOMIC statement must specify value for the option '%ls'.
10785 15 The %S_MSG '%ls' is not supported with an active xtp transaction.
10786 16 The ALTER AVAILABILITY GROUP command failed because it contained multiple MODIFY REPLICA options: %ls. Enter a separate ALTER AVAILABILITY GROUP ... MODIFY REPLICA command for each replica option that you want to modify.
10800 16 The listener for the WSFC resource '%.*ls' failed to start, and returned error code %d, '%.*ls'. For more information about this error code, see "System Error Codes" in the Windows Development Documentation.
10801 16 Failed to stop the listener for Windows Failover Cluster resource '%.*ls'. Error: %d. %.*ls
10802 10 Failed to enqueue a task to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is added manually or SQL Server is restarted. SQLOS error code: %d.
10900 16 Failed to configure resource governor during startup. Check SQL Server error log for specific error messages or check the consistency of master database by running DBCC CHECKCATALOG('master').
10901 16 User does not have permission to alter the resource governor configuration.
10902 16 User-defined function '%s' does not exist in master database, or the user does not have permission to access it.
10903 16 The specified schema name '%.*ls' for classifier user-defined function either does not exist, or the user does not have permission to use it.
10904 16 Resource governor configuration failed. There are active sessions in workload groups being dropped or moved to different resource pools. Disconnect all active sessions in the affected workload groups and try again.
10905 16 Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicated administrator connection.
10906 16 The object '%.*ls'.'%.*ls' is not a valid resource governor classifier user-defined function. A valid classifier user-defined function must be schema-bound, return sysname, and have no parameters.
10907 16 Attribute '%.*ls' with value of %u is greater than attribute '%.*ls' with value of %u.
10908 16 Attribute '%.*ls' with value of %u is less than attribute '%.*ls' with value of %u.
10909 16 The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools.
10910 16 The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all resource pools on scheduler %u to exceed 100 percent. Reduce the value for one or more pools, or change pool affinity, so that the sum is less than o
10911 16 Requested operation cannot be performed because the resource pool '%.*ls' does not exist.
10912 16 The operation could not be completed. Dropping predefined %S_MSG is not allowed.
10913 16 Users are not allowed to %S_MSG the workload group '%.*ls' in the '%.*ls' resource pool.
10914 16 The name of the %S_MSG '%.*ls' cannot begin with # of ##.
10915 16 The operation could not be completed. Altering '%.*ls' %S_MSG is not allowed.
10916 16 Cannot drop resource pool '%.*ls' because it contains workload group '%.*ls'. Drop or remove all workload groups using this resource pool before dropping it.
10917 16 ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified.
10918 16 Cannot create %S_MSG '%.*ls' because it already exists.
10919 16 An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system administrator.
10920 16 Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier.
10921 16 The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG.
10922 16 %ls failed. Rerun the statement.
10923 16 %ls failed. The resource governor is not available in this edition of SQL Server. You can manipulate resource governor metadata but you will not be able to apply resource governor configuration. Only Enterprise edition of SQL Server supports resource gov
10924 16 The pool affinity range is invalid. The lower bound %d must be less than the upper bound %d.
10925 16 A %S_MSG value was specified more than one time in the pool affinity range list.
10926 16 The %S_MSG range that specifies %S_MSG %d to %d includes at least one %S_MSG that is not available to the current instance. The maximum %S_MSG number that is available to this instance is %d.
10927 16 The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all workload groups using resource pool '%.*ls' to exceed 100 percent. Reduce the value or modify other workload groups so that the sum is less than or e
10981 10 Resource governor reconfiguration succeeded.
10982 16 Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID %ld for details. Classifier elapsed time: %I64u ms.
10983 16 Resource governor '%ls' operation was canceled by user.
10984 16 Resource governor reconfiguration failed.
11000 16 Unknown status code for this column.

Related Articles :