Skip Navigation Links
Home
Functions
Tips & Tricks
SQL Server 2005
SQL Server 2008
SQL Server 2012
FAQ
Forums
Practice Test
Bookstore
Tip of the Day : Example Uses of the NEWID Function
Home > Tips & Tricks > Error Messages 1001 to 1500
SQL Server Error Messages - Errors 1001 to 1500

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
1001 16 Line %d: Length or precision specification %d is invalid.
1002 16 Line %d: Specified scale %d is invalid.
1003 15 Line %d: %ls clause allowed only for %ls.
1004 16 Invalid column prefix '%.*ls': No table name specified
1005 15 Line %d: Invalid procedure number (%d). Must be between 1 and 32767.
1006 15 CREATE TRIGGER contains no statements.
1007 15 The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38).
1008 15 The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only allowed when ordering by an expression referencing a column name.
1010 15 Invalid escape character '%.*ls'.
1011 15 The correlation name '%.*ls' is specified multiple times in a FROM clause.
1012 15 The correlation name '%.*ls' has the same exposed name as table '%.*ls'.
1013 15 Tables or functions "Object Name" and "Object Name" have the same exposed names. Use correlation names to distinguish them.
1014 15 TOP clause contains an invalid value.
1015 15 An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the column being aggregated is an outer reference.
1016 15 Outer join operators cannot be specified in a query containing joined tables.
1017 15 The %ls hint cannot be specified more than once.
1018 15 Incorrect syntax near '%.*ls'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax.
1019 15 Invalid column list after object name in GRANT/REVOKE statement.
1020 15 Column list cannot be specified for object-level permissions.
1021 10 FIPS Warning: Line %d has the non-ANSI statement '%ls'.
1022 10 FIPS Warning: Line %d has the non-ANSI clause '%ls'.
1023 15 Invalid parameter %d specified for %ls.
1024 10 FIPS Warning: Line %d has the non-ANSI function '%ls'.
1025 10 FIPS Warning: The length of identifier '%.*ls' exceeds 18.
1026 16 GOTO cannot be used to jump into a TRY or CATCH scope.
1027 15 Too many expressions are specified in the GROUP BY clause. The maximum number is %d when either CUBE or ROLLUP is specified.
1028 15 The CUBE and ROLLUP options are not allowed in a GROUP BY ALL clause.
1029 15 Browse mode is invalid for subqueries and derived tables.
1030 16 Only constants are allowed here. Time literal is not permitted because it refers to the current date.
1031 15 Percent values must be between 0 and 100.
1032 16 Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'.
1033 16 The ORDER BY clause is invalid in views, inline functions, derived tables, and subqueries, unless TOP is also specified.
1034 15 Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration.
1035 15 Incorrect syntax near '%.*ls', expected '%.*ls'.
1036 15 File option %hs is required in this CREATE/ALTER DATABASE statement.
1037 15 The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions.
1038 15 Cannot use empty object or column names. Use a single space if necessary.
1039 15 Option '%.*ls' is specified more than once.
1040 15 Mixing old and new syntax in CREATE/ALTER DATABASE statement is not allowed.
1041 15 Option %.*ls is not allowed for a LOG file.
1042 15 Conflicting %ls optimizer hints specified.
1043 15 '%hs' is not yet implemented.
1044 15 Cannot use an existing function name to specify a stored procedure name.
1045 15 Aggregates are not allowed in this context. Only scalar expressions are allowed.
1046 15 Subqueries are not allowed in this context. Only scalar expressions are allowed.
1047 15 Conflicting locking hints specified.
1048 15 Conflicting cursor options %ls and %ls.
1049 15 Mixing old and new syntax to specify cursor options is not allowed.
1050 15 This syntax is only allowed within the stored procedure sp_executesql.
1051 15 Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT.
1052 15 Conflicting %ls options %ls and %ls.
1053 15 For DROP STATISTICS, you must give both the table and the column name in the form 'tablename.column'.
1054 15 Syntax '%ls' is not allowed in schema-bound objects.
1055 15 '%.*ls' is an invalid name because it contains a NULL character.
1056 15 The maximum number of elements in the select list is %d and you have supplied %d.
1057 15 The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION operator.
1058 15 Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration.
1059 15 Cannot set or reset the %ls option within a procedure.
1060 15 The number of rows in the TOP clause must be an integer.
1061 16 The text/ntext/image constants are not yet implemented.
1062 16 The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause.
1063 16 A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP.
1064 16 A filegroup cannot be used with log files.
1065 15 The NOLOCK, READUNCOMMITTED, and READPAST lock hints are only allowed in a SELECT statement.
1066 10 Warning. Line %d: The option '%ls' is obsolete and has no effect.
1067 15 The SET SHOWPLAN statements must be the only statements in the batch.
1068 16 Only one list of index hints per table is allowed.
1069 16 Index hints are only allowed in a FROM clause.
1070 15 CREATE INDEX option '%.*ls' is no longer supported.
1071 16 Cannot specify a JOIN algorithm with a remote JOIN.
1072 16 A REMOTE hint can only be specified with an INNER JOIN clause.
1073 15 '%.*ls' is not a recognized cursor option for cursor %.*ls.
1074 15 Creation of temporary functions is not allowed.
1075 15 RETURN statements in scalar valued functions must include an argument.
1076 15 Function '%s' requires at least %d argument(s).
1077 15 INSERT into an identity column not allowed on table variables.
1078 15 '%.*ls %.*ls' is not a recognized option.
1079 15 A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor.
1080 15 The integer value %.*ls is out of range.
1081 16 %s does not allow specifying the database name as a prefix to the assembly name.
1082 15 "%.*ls" does not support synchronous trigger registration.
1083 15 OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers.
1084 15 '%.*ls' is an invalid event type.
1085 15 '%.*ls' event type does not support event notifications.
1086 16 The FOR XML clause is invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. To work around, wrap the SELECT containing a set operator using derived table syntax and apply FOR XML on top of it.
1087 15 Must declare the table variable "%.*ls".
1088 15 Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
1089 15 The SET FMTONLY OFF statement must be the last statement in the batch.
1090 15 Invalid default for parameter %d.
1091 15 The option "%ls" is not valid for this function.
1092 16 In this context %d statistics name(s) cannot be specified for option '%ls'.
1093 16 "%.*ls" is not a valid broker name.
1094 15 Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.
1095 15 "%.*ls" has already been specified as an event type.
1096 15 Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported.
1097 15 Cannot use If UPDATE within this CREATE TRIGGER statement.
1098 15 The specified event type(s) is/are not valid on the specified target object.
1099 15 The ON clause is not valid for this statement.
1101 17 Could not allocate new page for database '%.*ls'. There are no more pages available in filegroup %.*ls. Space can be created by dropping objects, adding additional files, or allowing file growth.
1102 22 IAM page %S_PGID for object ID %ld is incorrect. The %S_MSG ID on page is %ld; should be %ld. The entry in sysindexes may be incorrect or the IAM page may contain an error.
1103 21 Allocation page %S_PGID in database '%.*ls' has different segment ID than that of the object which is being allocated to. Run DBCC CHECKALLOC.
1105 17 Could not allocate space for object '%.*ls' in database '%.*ls' because the '%.*ls' filegroup is full.
1109 21 Could not read allocation page %S_PGID because either the object ID (%ld) is not correct, or the page ID (%S_PGID) is not correct.
1119 16 Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.
1121 17 Space allocator cannot allocate page in database %d.
1122 14 Table error: Page %S_PGID. Test (%ls) failed. Address 0x%x is not aligned.
1123 14 Table error: Page %S_PGID. Unexpected page type %d.
1124 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x is invalid.
1125 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, row extends into free space at 0x%x.
1126 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x overlaps with the prior row.
1127 14 Table error: Page %S_PGID. Test (%ls) failed. Values are %ld and %ld.
1128 14 Table error: Page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.
1129 16 Could not cleanup deferred deallocations from filegroup '%.*ls'.
1130 10 Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost.
1131 10 Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.
1202 16 The database-principal '%.*ls' does not exist or user is not a member.
1203 20 Process ID %d attempting to unlock unowned resource %.*ls.
1204 19 The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration.
1205 13 Transaction (Process ID %d) was deadlocked on {%Z} resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
1206 18 Transaction manager has canceled the distributed transaction.
1207 10 Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB.
1208 21 Could not allocate initial %u lock blocks during startup. Can not start the server.
1209 21 Could not allocate initial %u lock owner blocks during startup. Can not start the server.
1210 21 Unable to allocate lock owner block during lock migration. Server halted.
1211 13 Process ID %d was chosen as the deadlock victim with P_BACKOUT bit set.
1212 10 Lock not logged: %-30ls Mode: %s
1213 21 Error spawning Lock Monitor thread: %ls
1214 17 Internal Error. There are too many parallel transactions.
1220 17 No more lock classes available from transaction.
1221 20 The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider.
1222 13 Lock request time out period exceeded.
1223 16 Attempting to release application lock '%.*ls' that is not currently held.
1224 16 An invalid application lock resource was passed to %ls.
1225 16 An invalid application lock mode was passed to %ls.
1226 16 An invalid application lock owner was passed to %ls.
1227 16 An invalid application lock time-out was passed to %ls.
1228 16 An invalid parameter "%ls" was passed to the application lock function or procedure.
1230 16 An invalid database principal was passed to %ls.

Error Severity Description
1401 21 Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Server service.
1402 20 Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mir
1403 16 The witness for the mirroring session received error response %d (state %d) from server instance %.*ls for database %.*ls. For more information about the error, refer to the error log on this server instance and
1404 16 The command failed because the database mirror is busy. Reissue the command later.
1405 16 The database "%.*ls" is already enabled for database mirroring.
1406 16 Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access.
1407 16 The remote copy of database "%.*ls" is not related to the local copy of the database.
1408 16 The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring or to join it to the availability group. You need to apply missing log records to the remote database by restoring the
1409 16 Database "%.*ls" requires database logs to be restored either on the future mirror database before you can enable database mirroring or on a secondary availability database before you can join it to the availabi
1410 16 The remote copy of database "%.*ls" is already enabled for database mirroring.
1411 16 The remote copy of database "%.*ls" has not had enough log backups applied to roll forward all of its files to a common point in time.
1412 16 The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log.
1413 16 Communications to the remote server instance '%.*ls' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started.
1414 16 The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
1415 16 The database mirroring operation for database "%.*ls" failed. The requested operation could not be performed.
1416 16 Database "%.*ls" is not configured for database mirroring.
1417 16 Database mirroring has been disabled by the administrator for database "%.*ls".
1418 16 The server network address "%.*ls" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
1419 16 The remote copy of database "%.*ls" cannot be opened. Check the database name and ensure that it is in the restoring state, and then reissue the command.
1420 16 Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration.
1421 16 Communications to the remote server instance '%.*ls' failed to complete before its timeout. The ALTER DATABASE command may have not completed. Retry the command.
1422 16 The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over.
1423 16 The property name is not supported.
1424 16 The remote server instance has a more recent value for the property '%.*ls'. Property value not changed.
1425 16 The property value is invalid for '%.*ls'. Property value not changed.
1426 16 To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these conditions are met, reissue the command.
1427 16 The server instance '%.*ls' could not act as the witness. The ALTER DATABASE SET WITNESS command failed.
1428 16 The request is refused because the responding server instance is not in a state to service the request.
1429 16 The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE SET WITNESS command failed.
1430 16 Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.
1431 16 Neither the partner nor the witness server instance for database "%.*ls" is available. Reissue the command when at least one of the instances becomes available.
1432 10 Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner.
1433 16 All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness associated with the database. Verify the status and when necessary rep
1434 16 Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls.
1435 16 %ls received unexpected database mirroring error response: status %u, severity %u, state %u, string %.*ls.
1436 16 The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server.
1437 16 Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase system memory.
1438 16 The server instance %ls rejected configure request; read its error log file for more information. The reason %u, and state %u, can be of use for diagnostics by Microsoft. This is a transient error hence retrying
1439 16 There is currently no witness associated with database "%.*ls".
1440 10 Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required.
1441 10 Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
1442 10 Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required.
1443 10 Database mirroring has been terminated for database '%.*ls'. This is an informational message only. No user action is required.
1444 10 Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
1445 10 Bypassing recovery for database '%ls' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications lin
1446 10 The "%.*ls" server instance is already acting as the witness.
1447 16 ALTER DATABASE "%.*ls" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command.
1448 16 The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command.
1449 16 ALTER DATABASE command failed due to an invalid server connection string.
1450 16 The ALTER DATABASE command failed because the worker thread cannot be created.
1451 16 Database mirroring information was not found in the system table.
1452 16 The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.
1453 17 '%.*ls', the remote mirroring partner for database '%.*ls', encountered error %d, status %d, severity %d. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or r
1454 17 Database mirroring will be suspended. Server instance '%.*ls' encountered error %d, state %d, severity %d when it was acting as a mirroring partner for database '%.*ls'. The database mirroring partners might try
1455 16 The database mirroring service cannot be forced for database "%.*ls" because the database is not in the correct state to become the principal database.
1456 16 The ALTER DATABASE command could not be sent to the remote server instance '%.*ls'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
1457 23 Synchronization of the mirror database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The ALTER DATABASE command failed. Ensure that the principal database, if available, is back up an
1458 17 The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring has been suspended. Try to resolve the error condition, and re
1459 24 An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it.
1460 16 The database "%.*ls" is already configured for database mirroring on the remote server. Drop database mirroring on the remote server to establish a new partner.
1461 10 Database mirroring successfully repaired physical page %S_PGID in database "%.*ls" by obtaining a copy from the partner.
1462 16 Database mirroring is disabled due to a failed redo operation. Unable to resume.
1463 16 Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions.
1464 16 Database "%.*ls" is not in a recovering state which is required for a mirror database or secondary database. The remote database must be restored using WITH NORECOVERY.
1465 16 Database "%.*ls" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group.
1466 16 Database "%.*ls" is read-only on one of the server instances which is incompatible with participating in database mirroring or in an availability group. Set the database to read-write mode, and retry the operati
1467 16 Database "%.*ls" database is in emergency or suspect mode on one of the partners which is incompatible with participating in database mirroring or in an availability group.
1468 16 The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a dat
1469 16 Database "%.*ls" is an auto-close database on one of the partnerswhich is incompatible with participating in database mirroring or in an availability group.
1470 16 The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls".
1471 16 The database mirroring connection terminated. Out of memory sending message for database "%.*ls".
1472 16 The database mirroring connection terminated. Communications error sending message for database "%.*ls".
1473 16 This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.
1474 16 Database mirroring connection error %d '%.*ls' for '%.*ls'.
1475 16 Database "%.*ls" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. Then restore this backup either on the mirror database to enable
1476 16 Database mirroring timeout value %d exceeds the maximum value 32767.
1477 16 The database mirroring safety level must be FULL to manually failover database "%.*ls". Set safety level to FULL and retry.
1478 16 The mirror database, "%.*ls", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or
1479 16 The mirroring connection to "%.*ls" has timed out for database "%.*ls" after %d seconds without a response. Check the service and network connections.
1480 10 The %S_MSG database "%.*ls" is changing roles from "%ls" to "%ls" because the mirroring session or availability group failed over due to %S_MSG. This is an informational message only. No user action is required.
1481 10 Database mirroring could not repair physical page %S_PGID in database "%.*ls". The mirroring partner could not be contacted or did not provide a copy of the page. Possible reasons include a lack of network conne
1482 10 Database mirroring failed to get snapshot synchrinization lock.
1485 10 Database mirroring has been enabled on this instance of SQL Server.
1486 10 Database Mirroring Transport is disabled in the endpoint configuration.
1487 10 Database mirroring is starting %d parallel redo thread(s) with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
1488 16 Database "%.*ls" database is in single user mode which is incompatible with participating in database mirroring or in an availability group. Set database to multi-user mode, and retry the operation.
1489 10 Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.
1490 16 The remote copy of database "%.*ls" has not been restored to a log backup that includes all filestream data files.
1499 16 Database mirroring error: status %u, severity %u, state %u, string %.*ls.

Related Articles :