Skip Navigation Links
Home
Articles
SQL Server 2012
SQL Server 2014
SQL Server 2016
FAQ
Forums
Practice Test
Bookstore
Tip of the Day : 2 Ways to Execute Operating System Commands From SQL Server Management Studio
Error Messages
Home > Tips & Tricks > Error Messages 11501 to 12000
SQL Server Error Messages - Errors 11501 to 12000

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
11501 16 The batch could not be analyzed because of compile errors.
11502 16 The type for parameter '%.*ls' cannot be deduced in this context.
11503 16 The parameter type cannot be deduced because a single expression contains two untyped parameters, '%.*ls' and '%.*ls'.
11504 16 The discovered type with user type id %d in database %d is invalid.
11505 16 The discovered type with the XML schema collection id %d in database %d is invalid.
11506 16 The parameter type for '%.*ls' cannot be uniquely deduced; two possibilities are '%ls' and '%ls'.
11507 16 The parameter type for '%.*ls' cannot be deduced because no type would make the query valid.
11508 16 The undeclared parameter '%.*ls' is used more than once in the batch being analyzed.
11509 16 The metadata could not be determined because the statement '%.*ls' is not compatible with the statement '%.*ls'.
11510 16 The metadata could not be determined because the statement '%.*ls' in the main batch is not compatible with the statement '%.*ls' in procedure '%.*ls'.
11511 16 The metadata could not be determined because the statement '%.*ls' in procedure '%.*ls' is not compatible with the statement '%.*ls' in the main batch.
11512 16 The metadata could not be determined because the statement '%.*ls' in procedure '%.*ls' is not compatible with the statement '%.*ls' in procedure '%.*ls'.
11513 16 The metadata could not be determined because statement '%.*ls' contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
11514 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
11515 16 The metadata could not be determined because statement '%.*ls' invokes a CLR procedure. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
11516 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' invokes a CLR procedure. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
11517 16 The metadata could not be determined because statement '%.*ls' invokes a CLR trigger.
11518 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' invokes a CLR trigger.
11519 16 The metadata could not be determined because statement '%.*ls' invokes an extended stored procedure.
11520 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' invokes an extended stored procedure.
11521 16 The metadata could not be determined because statement '%.*ls' uses an undeclared parameter in a context that affects its metadata.
11522 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' uses an undeclared parameter in a context that affects its metadata.
11523 16 The metadata could not be determined because statement '%.*ls' causes indirect recursion.
11524 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' causes indirect recursion.
11525 16 The metadata could not be determined because statement '%.*ls' uses a temp table.
11526 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' uses a temp table.
11527 16 The metadata could not be determined because statement '%.*ls' does not support metadata discovery.
11528 16 The metadata could not be determined because statement '%.*ls' in procedure '%.*ls' does not support metadata discovery.
11529 16 The metadata could not be determined because every code path results in an error; see previous errors for some of these.
11530 16 The metadata could not be determined because there are no code paths that reach the end of the batch.
11531 16 The object id '%d' passed to sys.dm_exec_describe_first_result_set_for_object refers to an object which is not a T-SQL procedure or trigger.
11532 16 The object id '%d' passed to sys.dm_exec_describe_first_result_set_for_object was invalid.
11533 16 Type '%.*ls' is not a valid object name for result set definition.
11534 16 Type '%.*ls' is invalid or not a table type.
11535 16 EXECUTE statement failed because its WITH RESULT SETS clause specified %d result set(s), and the statement tried to send more result sets than this.
11536 16 EXECUTE statement failed because its WITH RESULT SETS clause specified %d result set(s), but the statement only sent %d result set(s) at run time.
11537 16 EXECUTE statement failed because its WITH RESULT SETS clause specified %d column(s) for result set number %d, but the statement sent %d column(s) at run time.
11538 16 EXECUTE statement failed because its WITH RESULT SETS clause specified type '%ls' for column #%d in result set #%d, and the corresponding type sent at run time was '%ls'; there is no conversion between the two types.
11539 16 One of the types specified in WITH RESULT SETS clause has been modified after the EXECUTE statement started running. Please rerun the statement.
11541 16 sp_describe_first_result_set cannot be invoked when SET STATISTICS XML or SET STATISTICS PROFILE is on.
11542 16 sp_describe_undeclared_parameters failed to discover parameter metadata for remote procedure call because parameters were passed by name and by name parameter metadata discovery failed.
11543 16 SET STATISTICS XML ON and SET STATISTICS PROFILE ON are not allowed inside any procedure or batch that executes through an EXECUTE statement that has a WITH RESULT SETS clause.
11544 16 Could not deduce type for parameter in position '%d' for remote call to module '%.*ls'.
11545 16 Remote result set discovery cannot be done inside SELECT INTO.
11546 16 sp_showmemo_xml cannot run when the STATISTICS XML, STATISTICS PROFILE or SHOWPLAN set option is on. Set these options to OFF and re-run sp_showmemo_xml.
11547 16 Only one statement can be used as input parameter to sp_showmemo_xml. Modify the input parameter and re-run the stored procedure.
11548 16 The stored procedure 'sp_showmemo_xml' is not available in this edition of SQL Server.
11549 16 Using stored procedures is not supported. Modify the input parameter and re-run sp_showmemo_xml.
11550 16 The metadata could not be determined because remote metadata discovery failed for statement '%.*ls'.
11551 16 The metadata could not be determined because remote metadata discovery failed for statement '%.*ls' in procedure '%.*ls'.
11552 16 The @browse_information_mode parameter expects a tinyint with values 0, 1 or 2.
11553 16 EXECUTE statement failed because its WITH RESULT SETS clause specified a non-nullable type for column #%d in result set #%d, and the corresponding value sent at run time was null.

Error Severity Description
11601 15 %ls statements with a '%.*ls' option are not allowed.
11602 10 %ls statements are not verified.
11603 15 %ls statements are not allowed at the top level.
11605 15 %S_MSG are not allowed at the top level.
11606 15 Specifying server name in '%.*ls' is not allowed.
11607 15 Specifying database name for '%.*ls' in a %ls statement is not allowed.
11608 15 Creating temporary stored procedures is not allowed.
11609 16 An internal error occurred while building the project. %ls
11610 16 There is not enough memory to build the project.
11611 15 Specifying schema elements in the CREATE SCHEMA statement is not supported.
11612 15 Multiple statements in a T-SQL batch are not allowed at the top level.
11613 15 Numbered stored procedures are not supported.
11614 15 %ls is not supported.
11617 16 An unknown error has occurred trying to load '%hs'.
11618 15 Combining column level permissions with other permissions is not allowed in the same GRANT/DENY/REVOKE statement.
11619 16 There is not enough stack available to compile the statment.
11620 15 REVOKE statements can only be used to revoke column level permissions.
11621 10 SQL Server started in Language Service mode.
11622 16 CREATE ASSEMBLY can only be created FROM a constant binary expression.
11623 15 ALTER TABLE statements can only be used to add a single constraint.
11624 15 ALTER ROLE statements can only be used to add a member to a role.
11625 16 '%ls' is either corrupt, not readable or not accessible.
11651 10 %ls statements with a '%.*ls' option are not supported in a data-tier application.
11652 10 %ls statements are not supported at the top level in a data-tier application.
11653 10 Cannot execute as the user '%.*ls' because it does not exist.
11700 16 The increment for sequence object '<Sequence Name>' cannot be zero.
11701 16 The absolute value of the increment for sequence object '%.*ls' must be less than or equal to the difference between the minimum and maximum value of the sequence object.
11702 16 The sequence object '<Sequence Name>' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, or any user-defined data type that is based on one of the above integer data types.
11703 16 The start value for sequence object '%.*ls' must be between the minimum and maximum value of the sequence object.
11704 16 The current value '%.*ls' for sequence object '%.*ls' must be between the minimum and maximum value of the sequence object.
11705 16 The minimum value for sequence object '<Sequence Name>' must be less than its maximum value.
11706 16 The cache size for sequence object '%.*ls' must be greater than 0.
11707 10 The cache size for sequence object '%.*ls' has been set to NO CACHE.
11708 16 An invalid value was specified for argument '<Argument Name>' for the given data type.
11709 15 The 'RESTART WITH' argument cannot be used in a CREATE SEQUENCE statement.
11710 15 Argument 'START WITH' cannot be used in an ALTER SEQUENCE statement.
11711 15 Argument 'AS' cannot be used in an ALTER SEQUENCE statement.
11712 15 Argument '%.*ls' can not be specified more than once.
11714 15 Invalid sequence name '%.*ls'.
11715 15 No properties specified for ALTER SEQUENCE.
11716 15 NEXT VALUE FOR function does not support the PARTITION BY clause.
11717 15 NEXT VALUE FOR function does not support the OVER clause in default constraints, UPDATE statements, or MERGE statements.
11718 15 NEXT VALUE FOR function does not support an empty OVER clause.
11719 15
11720 15 NEXT VALUE FOR function is not allowed in the TOP, OVER, OUTPUT, ON, WHERE, GROUP BY, HAVING, or ORDER BY clauses.
11721 15 NEXT VALUE FOR function cannot be used directly in a statement that uses a DISTINCT, UNION, UNION ALL, EXCEPT or INTERSECT operator.
11722 15 NEXT VALUE FOR function is not allowed in the WHEN MATCHED clause, the WHEN NOT MATCHED clause, or the WHEN NOT MATCHED BY SOURCE clause of a merge statement.
11723 15 NEXT VALUE FOR function cannot be used directly in a statement that contains an ORDER BY clause unless the OVER clause is specified.
11724 15 An expression that contains a NEXT VALUE FOR function cannot be passed as an argument to a table-valued function.
11725 15 An expression that contains a NEXT VALUE FOR function cannot be passed as an argument to an aggregate.
11726 16 Object '%.*ls' is not a sequence object.
11727 16 NEXT VALUE FOR functions for a given sequence object must have exactly the same OVER clause definition.
11728 16 The sequence object '%.*ls' has reached its minimum or maximum value. Restart the sequence object to allow new values to be generated.
11729 10 The sequence object '%.*ls' cache size is greater than the number of available values; the cache size has been automatically set to accommodate the remaining sequence values.
11730 16 Database name cannot be specified for the sequence object in default constraints.
11731 16 A column that uses a sequence object in the default constraint must be present in the target columns list, if the same sequence object appears in a row constructor.
11732 16 The requested range for sequence object '%.*ls' exceeds the maximum or minimum limit. Retry with a smaller range.
11733 16 Parameter '%.*ls' must be a positive integer.
11734 16 NEXT VALUE FOR function is not allowed in the SELECT clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
11735 16 The target table of the INSERT statement cannot have DEFAULT constraints using the NEXT VALUE FOR function when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
11736 16 Only one instance of NEXT VALUE FOR function per sequence object is allowed in SET or SELECT with variable assignment.
11737 15 NEXT VALUE FOR function does not support the ROWS and RANGE clauses.
11738 16 The use of NEXT VALUE FOR function is not allowed in this context.
11739 16 NEXT VALUE FOR function cannot be used if ROWCOUNT option has been set, or the query contains TOP or OFFSET.
11740 16 NEXT VALUE FOR function cannot be used in a default constraint if ROWCOUNT option has been set, or the query contains TOP or OFFSET.
11741 16 NEXT VALUE FOR function cannot be used within CASE, CHOOSE, COALESCE, IIF, ISNULL and NULLIF.
11742 16 NEXT VALUE FOR function can only be used with MERGE if it is defined within a default constraint on the target table for insert actions.
11800 16 RESTORE WITH SNAPSHOTRESTOREPHASE=2 for database '%ls' failed because an earlier RESTORE WITH SNAPSHOTRESTOREPHASE=1 may have failed as a result of a network error. Retry the restore operation through SQL Writer after addressing any network issues and mak
11901 16 Column '%.*ls.%.*ls' is a federated column, while referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is not.
11902 16 Federation scheme key '%.*ls' is not a part of this federation.

Related Articles :