TSQL Error Messages
This section contains the TSQL error messages for InterSystems IRIS® data platform. To use these messages, your application’s TSQL procedure must reference the master..sysmessages system table. InterSystems IRIS does not support all TSQL features mentioned in these messages.
TSQL Error Codes - 0 to 99
Error Code | Description |
---|---|
1 | Version date of last upgrade: 10/11/90 |
21 | Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. |
TSQL Error Codes - 100 to 199
Error Code | Description |
---|---|
102 | Incorrect syntax near '%.*ls'. |
103 | The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d. |
104 | ORDER BY items must appear in the select list if the statement contains a UNION operator. |
105 | Unclosed quotation mark before the character string '%.*ls'. |
106 | Too many table names in the query. The maximum allowable is %d. |
107 | The column prefix '%.*ls' does not match with a table name or alias name used in the query. |
108 | The ORDER BY position number %ld is out of range of the number of items in the select list. |
109 | There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. |
110 | There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. |
111 | '%ls' must be the first statement in a query batch. |
112 | Variables are not allowed in the %ls statement. |
113 | Missing end comment mark '*/'. |
114 | Browse mode is invalid for a statement that assigns values to a variable. |
116 | Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. |
117 | The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. |
118 | Only members of the sysadmin role can specify the %ls option for the %ls statement. |
119 | Must pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters must be passed in the form '@name = value'. |
120 | The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns. |
121 | The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns. |
122 | The %ls option is allowed only with %ls syntax. |
123 | Batch/procedure exceeds maximum length of %d characters. |
124 | CREATE PROCEDURE contains no statements. |
125 | Case expressions may only be nested to level %d. |
128 | The name '%.*ls' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted. |
129 | Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. |
130 | Cannot perform an aggregate function on an expression containing an aggregate or a subquery. |
131 | The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d). |
132 | The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure. |
133 | A GOTO statement references the label '%.*ls' but the label has not been declared. |
134 | The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure. |
135 | Cannot use a BREAK statement outside the scope of a WHILE statement. |
136 | Cannot use a CONTINUE statement outside the scope of a WHILE statement. |
137 | Must declare the variable '%.*ls'. |
138 | Correlation clause in a subquery not permitted. |
139 | Cannot assign a default value to a local variable. |
140 | Can only use IF UPDATE within a CREATE TRIGGER statement. |
141 | A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations. |
142 | Incorrect syntax for definition of the '%ls' constraint. |
143 | A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list. |
144 | Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. |
145 | ORDER BY items must appear in the select list if SELECT DISTINCT is specified. |
146 | Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded. |
147 | An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference. |
148 | Incorrect time syntax in time string '%.*ls' used with WAITFOR. |
149 | Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax. |
150 | Both terms of an outer join must contain columns. |
151 | '%.*ls' is an invalid money value. |
153 | Invalid usage of the option %.*ls in the %ls statement. |
154 | %S_MSG is not allowed in %S_MSG. |
155 | '%.*ls' is not a recognized %ls option. |
156 | Incorrect syntax near the keyword '%.*ls'. |
157 | An aggregate may not appear in the set list of an UPDATE statement. |
159 | For DROP INDEX, you must give both the table and the index name, in the form tablename.indexname. |
160 | Rule does not contain a variable. |
161 | Rule contains more than one variable. |
163 | The compute by list does not match the order by list. |
164 | GROUP BY expressions must refer to column names that appear in the select list. |
165 | Privilege %ls may not be granted or revoked. |
166 | '%ls' does not allow specifying the database name as a prefix to the object name. |
167 | Cannot create a trigger on a temporary object. |
168 | The %S_MSG '%.*ls' is out of the range of computer representation (%d bytes). |
169 | A column has been specified more than once in the order by list. Columns in the order by list must be unique. |
170 | Line %d: Incorrect syntax near '%.*ls'. |
171 | Cannot use SELECT INTO in browse mode. |
172 | Cannot use HOLDLOCK in browse mode. |
173 | The definition for column '%.*ls' must include a data type. |
174 | The %ls function requires %d arguments. |
177 | The IDENTITY function can only be used when the SELECT statement has an INTO clause. |
178 | A RETURN statement with a return value cannot be used in this context. |
179 | Cannot use the OUTPUT option when passing a constant to a stored procedure. |
180 | There are too many parameters in this %ls statement. The maximum number is %d. |
181 | Cannot use the OUTPUT option in a DECLARE statement. |
182 | Table and column names must be supplied for the READTEXT or WRITETEXT utility. |
183 | The scale (%d) for column '%.*ls' must be within the range %d to %d. |
185 | Data stream is invalid for WRITETEXT statement in bulk form. |
186 | Data stream missing from WRITETEXT statement. |
188 | Cannot specify a log device in a CREATE DATABASE statement without also specifying at least one non-log device. |
189 | The %ls function requires %d to %d arguments. |
191 | Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries. |
192 | The scale must be less than or equal to the precision. |
193 | The object or column name starting with '%.*ls' is too long. The maximum length is %d characters. |
194 | A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable. |
195 | '%.*ls' is not a recognized %S_MSG. |
196 | SELECT INTO must be the first query in an SQL statement containing a UNION operator. |
197 | EXECUTE cannot be used as a source when inserting into a table variable. |
198 | Browse mode is invalid for statements containing a UNION operator. |
199 | An INSERT statement cannot contain a SELECT statement that assigns values to a variable. |
TSQL Error Codes - 200 to 299
Error Code | Description |
---|---|
201 | Procedure '%.*ls' expects parameter '%.*ls', which was not supplied. |
202 | Invalid type '%s' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. |
203 | The name '%.*ls' is not a valid identifier. |
204 | Normalization error in node %ls. |
205 | All queries in an SQL statement containing a UNION operator must have an equal number of expressions in their target lists. |
206 | Operand type clash: %ls is incompatible with %ls |
207 | Invalid column name '%.*ls'. |
208 | Invalid object name '%.*ls'. |
209 | Ambiguous column name '%.*ls'. |
210 | Syntax error converting datetime from binary/varbinary string. |
212 | Expression result length exceeds the maximum. %d max, %d found. |
213 | Insert Error: Column name or number of supplied values does not match table definition. |
214 | Procedure expects parameter '%ls' of type '%ls'. |
217 | Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d). |
220 | Arithmetic overflow error for data type %ls, value = %ld. |
221 | FIPS Warning: Implicit conversion from %ls to %ls. |
223 | Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. |
224 | Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. |
226 | %ls statement not allowed within multi-statement transaction. |
229 | %ls permission denied on object '%.*ls', database '%.*ls', owner '%.*ls'. |
230 | %ls permission denied on column '%.*ls' of object '%.*ls', database '%.*ls', owner '%.*ls'. |
231 | No such default. ID = %ld, database ID = %d. |
232 | Arithmetic overflow error for type %ls, value = %f. |
233 | The column '%.*ls' in table '%.*ls' cannot be null. |
234 | There is insufficient result space to convert a money value to %ls. |
235 | Cannot convert a char value to money. The char value has incorrect syntax. |
236 | The conversion from char data type to money resulted in a money overflow error. |
237 | There is insufficient result space to convert a money value to %ls. |
238 | There is insufficient result space to convert the %ls value (= %d) to the money data type. |
241 | Syntax error converting datetime from character string. |
242 | The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value. |
243 | Type %.*ls is not a defined system type. |
244 | The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column. |
245 | Syntax error converting the %ls value '%.*ls' to a column of data type %ls. |
248 | The conversion of the %ls value '%.*ls' overflowed an int column. Maximum integer value exceeded. |
251 | Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded. |
256 | The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. |
257 | Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query. |
259 | Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this. |
260 | Disallowed implicit conversion from data type %ls to data type %ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query. |
261 | '%.*ls' is not a recognized function. |
262 | %ls permission denied in database '%.*ls'. |
263 | Must specify table to select from. |
264 | Column name '%.*ls' appears more than once in the result column list. |
266 | Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = %ld, current count = %ld. |
267 | Object '%.*ls' cannot be found. |
268 | Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. |
270 | Object '%.*ls' cannot be modified. |
271 | Column '%.*ls' cannot be modified because it is a computed column. |
272 | Cannot update a timestamp column. |
273 | Cannot insert a non-null value into a timestamp column. Use INSERT with a column list or with a default of NULL for the timestamp column. |
278 | The text, ntext, and image data types cannot be used in a GROUP BY clause. |
279 | The text, ntext, and image data types are invalid in this subquery or aggregate expression. |
280 | Only text, ntext, and image columns are valid with the TEXTPTR function. |
281 | %d is not a valid style number when converting from %ls to a character string. |
282 | The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. |
283 | READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. |
284 | Rules cannot be bound to text, ntext, or image data types. |
285 | The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions. |
286 | The logical tables INSERTED and DELETED cannot be updated. |
287 | The %ls statement is not allowed within a trigger. |
288 | The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. |
291 | CAST or CONVERT: invalid attributes specified for type '%.*ls' |
292 | There is insufficient result space to convert a smallmoney value to %ls. |
293 | Cannot convert char value to smallmoney. The char value has incorrect syntax. |
294 | The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. |
295 | Syntax error converting character string to smalldatetime data type. |
296 | The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value. |
298 | The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error. |
299 | The DATEADD function was called with bad type %ls. |
TSQL Error Codes - 300 to 399
Error Code | Description |
---|---|
301 | Query contains an outer-join request that is not permitted. |
303 | The table '%.*ls' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause. |
306 | The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. |
307 | Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist. |
308 | Index '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist. |
311 | Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables. |
312 | Cannot reference text, ntext, or image columns in a filter stored procedure. |
313 | An insufficient number of arguments were supplied for the procedure or function %.*ls. |
314 | Cannot use GROUP BY ALL with the special tables INSERTED or DELETED. |
TSQL Error Codes - 400 to 499
Error Code | Description |
---|---|
401 | Unimplemented statement or expression %ls. |
403 | Invalid operator for data type. Operator equals %ls, type equals %ls. |
409 | The %ls operation cannot take a %ls data type as an argument. |
410 | COMPUTE clause #%d 'BY' expression #%d is not in the order by list. |
411 | COMPUTE clause #%d, aggregate expression #%d is not in the select list. |
420 | The text, ntext, and image data types cannot be used in an ORDER BY clause. |
425 | Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'. |
426 | The length %d of the receiving variable is less than the length %d of the column '%.*ls'. |
427 | Could not load sysprocedures entries for constraint ID %d in database ID %d. |
428 | Could not find row in sysconstraints for constraint ID %d in database ID %d. |
429 | Could not find new constraint ID %d in sysconstraints, database ID %d, at compile time. |
430 | Could not resolve table name for object ID %d, database ID %d, when compiling foreign key. |
431 | Could not bind foreign key constraint. Too many tables involved in the query. |
433 | Could not find CHECK constraint for '%.*ls', although the table is flagged as having one. |
436 | Could not open referenced table ID %d in database ID %d. |
437 | Could not resolve the referenced column name in table ID %d. |
438 | Could not resolve the referencing column name in table ID %d. |
439 | Could not find FOREIGN KEY constraints for table '%.*ls' in database ID %d although the table is flagged as having them. |
441 | Cannot use the '%ls' function on a remote data source. |
443 | Invalid use of '%s' within a function. |
444 | Select statements included within a function cannot return data to a client. |
445 | COLLATE clause cannot be used on expressions containing a COLLATE clause. |
446 | Cannot resolve collation conflict for %ls operation. |
447 | Expression type %ls is invalid for COLLATE clause. |
448 | Invalid collation '%.*ls'. |
449 | Collation conflict caused by collate clauses with different collation '%.*ls' and '%.*ls'. |
450 | Code page translations are not supported for the text data type. From: %d To: %d. |
451 | Cannot resolve collation conflict for column %d in %ls statement. |
452 | COLLATE clause cannot be used on user-defined data types. |
453 | Collation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level. |
455 | The last statement included within a function must be a return statement. |
456 | Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict. |
457 | Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict. |
TSQL Error Codes - 500 to 599
Error Code | Description |
---|---|
502 | The SQL Debugging Interface (SDI) requires that SQL Server, when started as a service, must not log on as System Account. Reset to log on as user account using Control Panel. |
503 | Unable to send symbol information to debugger on %ls for connection %d. Debugging disabled. |
504 | Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on %.*ls. Debugging disabled for connection %d. |
505 | Current user account was invoked with SETUSER. Changing databases is not allowed. |
506 | Invalid escape character '%.*ls' was specified in a LIKE predicate. |
507 | Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer. |
508 | Unable to connect to debugger on %ls (Error = 0x%08x). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on %.*ls. Debugging disabled for connection %d. |
509 | User name '%.*ls' not found. |
510 | Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint. |
511 | Cannot create a row of size %d which is greater than the allowable maximum of %d. |
512 | Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. |
513 | A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'. |
514 | Unable to communicate with debugger on %ls (Error = 0x%08x). Debugging disabled for connection %d. |
515 | Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails. |
516 | Attempt to initialize OLE library failed. Check for correct versions of OLE DLLs on this machine. |
517 | Adding a value to a '%ls' column caused overflow. |
518 | Cannot convert data type %ls to %ls. |
520 | SQL Server no longer supports version %d of the SQL Debugging Interface (SDI). |
528 | System error detected during attempt to use the 'upsleep' system function. |
529 | Explicit conversion from data type %ls to %ls is not allowed. |
532 | The timestamp (changed to %S_TS) shows that the row has been updated by another user. |
535 | Difference of two datetime columns caused overflow at runtime. |
536 | Invalid length parameter passed to the substring function. |
538 | Cannot find '%.*ls'. This language may have been dropped. Contact your system administrator. |
542 | An invalid datetime value was encountered. Value exceeds the year 9999. |
544 | Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF. |
545 | Explicit value must be specified for identity column in table '%.*ls' when IDENTITY_INSERT is set to ON. |
547 | %ls statement conflicted with %ls %ls constraint '%.*ls'. The conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls. |
548 | The identity range managed by replication is full and must be updated by a replication agent. The %ls conflict occurred in database '%.*ls', table '%.*ls'%ls%.*ls%ls. Sp_adjustpublisheridentityrange can be called to get a new identity range. |
550 | The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint. |
551 | The checksum has changed to %d. This shows that the row has been updated by another user. |
552 | CryptoAPI function '%ls' failed. Error 0x%x: %ls |
555 | User-defined functions are not yet enabled. |
556 | INSERT EXEC failed because the stored procedure altered the schema of the target table. |
557 | Only functions and extended stored procedures can be executed from within a function. |
558 | Remote function calls are not allowed within a function. |
561 | Failed to access file '%.*ls' |
562 | Failed to access file '%.*ls'. Files can be accessed only through shares |
563 | The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated. |
564 | Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'. |
565 | The server encountered a stack overflow during compile time. |
566 | Error writing audit trace. SQL Server is shutting down. |
567 | File '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file. |
568 | Server encountered an error '%.*ls'. |
TSQL Error Codes - 600 to 699
Error Code | Description |
---|---|
601 | Could not continue scan with NOLOCK due to data movement. |
602 | Could not find row in sysindexes for database ID %d, object ID %ld, index ID %d. Run DBCC CHECKTABLE on sysindexes. |
604 | Could not find row in sysobjects for object ID %ld in database '%.*ls'. Run DBCC CHECKTABLE on sysobjects. |
605 | Attempt to fetch logical page %S_PGID in database '%.*ls' belongs to object '%.*ls', not to object '%.*ls'. |
607 | Insufficient room was allocated for search arguments in the session descriptor for object '%.*ls'. Only %d search arguments were anticipated. |
615 | Could not find database table ID %d, name '%.*ls'. |
617 | Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. |
618 | A varno of %d was passed to the opentable system function. The largest valid value is %d. |
622 | Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and text, ntext, and image columns cannot be populated on this filegroup until a file is added. |
623 | Could not retrieve row from page by RID because logical page %S_PGID is not a data page. %S_RID. %S_PAGE. |
624 | Could not retrieve row from page by RID because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE, DBID %d. |
625 | Cannot retrieve row from page %S_PGID by RID because the slotid (%d) is not valid. |
626 | Cannot use ROLLBACK with a savepoint within a distributed transaction. |
627 | Cannot use SAVE TRANSACTION within a distributed transaction. |
628 | Cannot issue SAVE TRANSACTION when there is no active transaction. |
635 | Process %d tried to remove DES resource lock %S_DES, which it does not hold. |
637 | Index shrink program returned invalid status of 0. |
639 | Could not fetch logical page %S_PGID, database ID %d. The page is not currently allocated. |
644 | Could not find the index entry for RID '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'. |
649 | Could not find the clustered index entry for page %S_PGID, object ID %ld, status 0x%x. Index page %S_PGID, in database '%.*ls', was searched for this entry. |
650 | You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. |
651 | Cannot use %hs granularity hint on table '%.*ls' because locking at the specified granularity is inhibited. |
652 | Index ID %d for table '%.*ls' resides on a read-only filegroup which cannot be modified. |
653 | Two buffers are conflicting for the same keep slot in table '%.*ls'. |
654 | No slots are free to keep buffers for table '%.*ls'. |
655 | Expected to find buffer in keep slot for table '%.*ls'. |
666 | Maximum system-generated unique value for a duplicate group exceeded for table ID %d, index ID %d. Dropping and re-creating the index may fix the problem; otherwise use another clustering key. |
667 | Index %d for table '%.*ls' resides on offline filegroup that cannot be accessed. |
TSQL Error Codes - 700 to 799
Error Code | Description |
---|---|
701 | There is insufficient system memory to run this query. |
708 | Warning: Due to low virtual memory, special reserved memory used %d times since startup. Increase virtual memory on server. |
TSQL Error Codes - 800 to 899
Error Code | Description |
---|---|
802 | No more buffers can be stolen. |
804 | Could not find buffer 0x%lx holding logical page %S_PGID in the SDES 0x%lx kept buffer pool for object '%.*ls'. |
809 | Buffer 0x%lx, allocation page %S_PGID, in database '%.*ls' is not in allocation buffer pool in PSS (process status structure). Contact Technical Support. |
813 | Logical page %S_PGID in database ID %d is already hashed. |
816 | Process ID %d tried to remove a buffer resource lock %S_BUF that it does not hold in SDES %S_SDES. Contact Technical Support. |
818 | There is no room to hold the buffer resource lock %S_BUF in SDES %S_SDES. Contact Technical Support. |
821 | Could not unhash buffer at 0x%lx with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. |
822 | Could not start I/O for request %S_BLKIOPTR. |
823 | I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'. |
834 | The bufclean system function was called on dirty buffer (page %S_PGID, stat %#x/%#x, objid %#x, sstat%#x). |
840 | Device '%.*ls' (physical name '%.*ls', virtual device number %d) is not available. Contact the system administrator for assistance. |
844 | Time out occurred while waiting for buffer latch type %d, bp %#x, page %S_PGID, stat %#x, object ID %d:%d:%d, waittime %d. Continuing to wait. |
845 | Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d. |
TSQL Error Codes - 900 to 999
Error Code | Description |
---|---|
901 | Could not find descriptor for database ID %d, object ID %ld in hash table after hashing it. |
902 | To change the %ls, the database must be in state in which a checkpoint can be executed. |
903 | Could not find row in sysindexes for clustered index on system catalog %ld in database ID %d. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database. |
906 | Could not locate row in sysobjects for system catalog '%.*ls' in database '%.*ls'. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysobjects in this database. |
911 | Could not locate entry in sysdatabases for database '%.*ls'. No entry found with that name. Make sure that the name is entered correctly. |
913 | Could not find database ID %d. Database may not be activated yet or may be in transition. |
916 | Server user '%.*ls' is not a valid user in database '%.*ls'. |
921 | Database '%.*ls' has not been recovered yet. Wait and try again. |
922 | Database '%.*ls' is being recovered. Waiting until recovery is finished. |
923 | Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it. |
924 | Database '%.*ls' is already open and can only have one user at a time. |
925 | Maximum number of databases used for each query has been exceeded. The maximum allowed is %d. |
926 | Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. |
927 | Database '%.*ls' cannot be opened. It is in the middle of a restore. |
929 | Attempting to close a database that is not already open. Contact Technical Support. |
941 | Cannot open database '%.*ls'. It has not been upgraded to the latest format. |
942 | Database '%.*ls' cannot be opened because it is offline. |
943 | Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d). |
944 | Converting database '%.*ls' from version %d to the current version %d. |
945 | Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. |
946 | Cannot open database '%.*ls' version %d. Upgrade the database to the latest version. |
947 | Error while closing database '%.*ls' cleanly. |
948 | Database '%.*ls' cannot be upgraded. Database is version %d and this server supports version %d. |
949 | tempdb is skipped. You cannot run a query that requires tempdb |
950 | Database '%.*ls' cannot be upgraded - database has a version (%d) earlier than SQL Server 7.0(%d). |
951 | Database '%.*ls' running the upgrade step from version %d to version %d. |
952 | Database '%.*ls' is in transition. Try the statement later. |
953 | Warning: Index '%ls' on '%ls' in database '%ls' may be corrupt because of expression evaluation changes in this release. Drop and re-create the index. |
TSQL Error Codes - 1000 to 1099
Error Code | Description |
---|---|
1001 | Line %d: Length or precision specification %d is invalid. |
1002 | Line %d: Specified scale %d is invalid. |
1003 | Line %d: %ls clause allowed only for %ls. |
1004 | Invalid column prefix '%.*ls': No table name specified |
1005 | Line %d: Invalid procedure number (%d). Must be between 1 and 32767. |
1006 | CREATE TRIGGER contains no statements. |
1007 | The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38). |
1008 | 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 | Invalid escape character '%.*ls'. |
1011 | The correlation name '%.*ls' is specified multiple times in a FROM clause. |
1012 | The correlation name '%.*ls' has the same exposed name as table '%.*ls'. |
1013 | Tables or functions '%.*ls' and '%.*ls' have the same exposed names. Use correlation names to distinguish them. |
1014 | TOP clause contains an invalid value. |
1015 | 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 | Outer join operators cannot be specified in a query containing joined tables. |
1019 | Invalid column list after object name in GRANT/REVOKE statement. |
1020 | Column list cannot be specified for object-level permissions. |
1021 | FIPS Warning: Line %d has the non-ANSI statement '%ls'. |
1022 | FIPS Warning: Line %d has the non-ANSI clause '%ls'. |
1023 | Invalid parameter %d specified for %ls. |
1024 | FIPS Warning: Line %d has the non-ANSI function '%ls'. |
1025 | FIPS Warning: The length of identifier '%.*ls' exceeds 18. |
1027 | Too many expressions are specified in the GROUP BY clause. The maximum number is %d when either CUBE or ROLLUP is specified. |
1028 | The CUBE and ROLLUP options are not allowed in a GROUP BY ALL clause. |
1029 | Browse mode is invalid for subqueries and derived tables. |
1031 | Percent values must be between 0 and 100. |
1032 | Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'. |
1033 | The ORDER BY clause is invalid in views, inline functions, derived tables, and subqueries, unless TOP is also specified. |
1035 | Incorrect syntax near '%.*ls', expected '%.*ls'. |
1036 | File option %hs is required in this CREATE/ALTER DATABASE statement. |
1037 | The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions. |
1038 | Cannot use empty object or column names. Use a single space if necessary. |
1039 | Option '%.*ls' is specified more than once. |
1040 | Mixing old and new syntax in CREATE/ALTER DATABASE statement is not allowed. |
1041 | Option %.*ls is not allowed for a LOG file. |
1042 | Conflicting %ls optimizer hints specified. |
1043 | '%hs' is not yet implemented. |
1044 | Cannot use an existing function name to specify a stored procedure name. |
1045 | Aggregates are not allowed in this context. Only scalar expressions are allowed. |
1046 | Subqueries are not allowed in this context. Only scalar expressions are allowed. |
1047 | Conflicting locking hints specified. |
1048 | Conflicting cursor options %ls and %ls. |
1049 | Mixing old and new syntax to specify cursor options is not allowed. |
1050 | This syntax is only allowed within the stored procedure sp_executesql. |
1051 | 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 | Conflicting %ls options %ls and %ls. |
1053 | For DROP STATISTICS, you must give both the table and the column name in the form 'tablename.column'. |
1054 | Syntax '%ls' is not allowed in schema-bound objects. |
1055 | '%.*ls' is an invalid name because it contains a NULL character. |
1056 | The maximum number of elements in the select list is %d and you have supplied %d. |
1057 | The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION operator. |
1058 | Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration. |
1059 | Cannot set or reset the %ls option within a procedure. |
1060 | The number of rows in the TOP clause must be an integer. |
1061 | The text/ntext/image constants are not yet implemented. |
1062 | The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause. |
1063 | A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP. |
1064 | A filegroup cannot be used with log files. |
1065 | The NOLOCK, READUNCOMMITTED, and READPAST lock hints are only allowed in a SELECT statement. |
1066 | Warning. Line %d: The option '%ls' is obsolete and has no effect. |
1067 | The SET SHOWPLAN statements must be the only statements in the batch. |
1068 | Only one list of index hints per table is allowed. |
1069 | Index hints are only allowed in a FROM clause. |
1070 | CREATE INDEX option '%.*ls' is no longer supported. |
1071 | Cannot specify a JOIN algorithm with a remote JOIN. |
1072 | A REMOTE hint can only be specified with an INNER JOIN clause. |
1073 | '%.*ls' is not a recognized cursor option for cursor %.*ls. |
1074 | Creation of temporary functions is not allowed. |
1075 | RETURN statements in scalar valued functions must include an argument. |
1076 | Function '%s' requires at least %d argument(s). |
1077 | INSERT into an identity column not allowed on table variables. |
1078 | '%.*ls %.*ls' is not a recognized option. |
1079 | A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor. |
TSQL Error Codes - 1100 to 1199
Error Code | Description |
---|---|
1101 | 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 | 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 | 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 | Could not allocate space for object '%.*ls' in database '%.*ls' because the '%.*ls' filegroup is full. |
1109 | 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. |
TSQL Error Codes - 1200 to 1299
Error Code | Description |
---|---|
1201 | The page_lock system function was called with a mode %d that is not permitted. |
1203 | Process ID %d attempting to unlock unowned resource %.*ls. |
1204 | 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 | Transaction (Process ID %d) was deadlocked on {%Z} resources with another process and has been chosen as the deadlock victim. Rerun the transaction. |
1206 | Transaction manager has canceled the distributed transaction. |
1211 | Process ID %d was chosen as the deadlock victim with P_BACKOUT bit set. |
1220 | No more lock classes available from transaction. |
1221 | Invalid lock class for release call. |
1222 | Lock request time out period exceeded. |
1223 | Attempting to release application lock '%.*ls' that is not currently held. |
TSQL Error Codes - 1500 to 1599
Error Code | Description |
---|---|
1501 | Sort failure. |
1505 | CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID %d. Most significant primary key is '%S_KEY'. |
1507 | Warning: Deleted duplicate row. Primary key is '%S_KEY'. |
1508 | CREATE INDEX terminated because a duplicate row was found. Primary key is '%S_KEY'. |
1509 | Row compare failure. |
1510 | Sort failed. Out of space or locks in database '%.*ls'. |
1511 | Sort cannot be reconciled with transaction log. |
1522 | Sort failure. Prevented overwriting of allocation page in database '%.*ls' by terminating sort. |
1523 | Sort failure. Prevented incorrect extent deallocation by aborting sort. |
1528 | Character data comparison failure. An unrecognized Sort-Map-Element type (%d) was found in the server-wide default sort table at SMEL entry [%d]. |
1529 | Character data comparison failure. A list of Sort-Map-Elements from the server-wide default sort table does not end properly. This list begins at SMEL entry [%d]. |
1530 | CREATE INDEX with DROP_EXISTING was aborted because a row was out of order. Most significant offending primary key is '%S_KEY'. Explicitly drop and create the index instead. |
1531 | The SORTED_DATA_REORG option cannot be used for a nonclustered index if the keys are not unique within the table. CREATE INDEX was aborted because of duplicate keys. Primary key is '%S_KEY'. |
1532 | New sort run starting on page %S_PGID found extent not marked as shared. |
1533 | Cannot share extent %S_PGID among more than eight sort runs. |
1534 | Extent %S_PGID not found in shared extent directory. |
1535 | Cannot share extent %S_PGID with shared extent directory full. |
1536 | Cannot build a nonclustered index on a memory-only work table. |
1537 | Cannot suspend a sort not in row input phase. |
1538 | Cannot insert into a sort not in row input phase. |
1540 | Cannot sort a row of size %d, which is greater than the allowable maximum of %d. |
TSQL Error Codes - 1600 to 1699
Error Code | Description |
---|---|
1619 | Could not open tempdb. Cannot continue. |
1620 | Cannot start C2 audit trace. SQL Server is shutting down. |
1621 | Server started with '-f'. Auditing will not be started. |
TSQL Error Codes - 1700 to 1799
Error Code | Description |
---|---|
1701 | Creation of table '%.*ls' failed because the row size would be %d, including internal overhead. This exceeds the maximum allowable table row size, %d. |
1702 | CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns. |
1703 | Could not allocate disk space for a work table in database '%.*ls'. You may be able to free up space by using BACKUP LOG, or you may want to extend the size of the database by using ALTER DATABASE. |
1704 | Only members of the sysadmin role can create the system table '%.*ls'. |
1705 | You must create system table '%.*ls' in the master database. |
1706 | System table '%.*ls' was not created, because ad hoc updates to system catalogs are not enabled. |
1708 | Warning: The table '%.*ls' has been created but its maximum row size (%d) exceeds the maximum number of bytes per row (%d). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds %d bytes. |
1709 | Cannot use TEXTIMAGE_ON when a table has no text, ntext, or image columns. |
1750 | Could not create constraint. See previous errors. |
1752 | Could not create DEFAULT for column '%.*ls' as it is not a valid column in the table '%.*ls'. |
1753 | Column '%.*ls.%.*ls' is not the same length as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. |
1754 | Defaults cannot be created on columns with an IDENTITY attribute. Table '%.*ls', column '%.*ls'. |
1755 | Defaults cannot be created on columns of data type timestamp. Table '%.*ls', column '%.*ls'. |
1756 | Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. |
1757 | Column '%.*ls.%.*ls' is not of same collation as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. |
1759 | Invalid column '%.*ls' is specified in a constraint or computed-column definition. |
1760 | Constraints of type %ls cannot be created on columns of type %ls. |
1763 | Cross-database foreign key references are not supported. Foreign key '%.*ls'. |
1766 | Foreign key references to temporary tables are not supported. Foreign key '%.*ls'. |
1767 | Foreign key '%.*ls' references invalid table '%.*ls'. |
1768 | Foreign key '%.*ls' references object '%.*ls' which is not a user table. |
1769 | Foreign key '%.*ls' references invalid column '%.*ls' in referencing table '%.*ls'. |
1770 | Foreign key '%.*ls' references invalid column '%.*ls' in referenced table '%.*ls'. |
1772 | Foreign key '%.*ls' defines an invalid relationship between a user table and system table. |
1773 | Foreign key '%.*ls' has implicit reference to object '%.*ls' which does not have a primary key defined on it. |
1774 | The number of columns in the referencing column list for foreign key '%.*ls' does not match those of the primary key in the referenced table '%.*ls'. |
1776 | There are no primary or candidate keys in the referenced table '%.*ls' that match the referencing column list in the foreign key '%.*ls'. |
1777 | User does not have correct permissions on referenced table '%.*ls' to create foreign key '%.*ls'. |
1778 | Column '%.*ls.%.*ls' is not the same data type as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. |
1779 | Table '%.*ls' already has a primary key defined on it. |
1780 | Could not find column ID %d in syscolumns for object ID %d in database ID %d. |
1781 | Column already has a DEFAULT bound to it. |
1784 | Cannot create the foreign key '%.*ls' because the referenced column '%.*ls.%.*ls' is a computed column. |
1785 | Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. |
1786 | Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with cascading referential integrity constraints. |
1787 | Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIGGER defined on it. |
1788 | Cascading foreign key '%.*ls' cannot be created where the referencing column '%.*ls.%.*ls' is an identity column. |
1789 | Cannot use CHECKSUM(*) in a computed column definition. |
TSQL Error Codes - 1800 to 1899
Error Code | Description |
---|---|
1801 | Database '%.*ls' already exists. |
1802 | CREATE DATABASE failed. Some file names listed could not be created. Check previous errors. |
1803 | CREATE DATABASE failed. Could not allocate enough disk space for a new database on the named disks. Total space allocated must be at least %d MB to accommodate a copy of the model database. |
1804 | There is no disk named '%.*ls'. Checking other disk names. |
1805 | The CREATE DATABASE process is allocating %.2f MB on disk '%.*ls'. |
1806 | CREATE DATABASE failed. The default collation of database '%.*ls' cannot be set to '%.*ls'. |
1807 | Could not obtain exclusive lock on database '%.*ls'. Retry the operation later. |
1808 | Default devices are not supported. |
1809 | To achieve optimal performance, update all statistics on the '%.*ls' database by running sp_updatestats. |
1811 | '%.*ls' is the wrong type of device for CREATE DATABASE or ALTER DATABASE. Check sysdevices. The statement is aborted. |
1812 | CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option. |
1813 | Could not open new database '%.*ls'. CREATE DATABASE is aborted. |
1814 | Could not create tempdb. If space is low, extend the amount of space and restart. |
1818 | Primary log file '%ls' is missing and the database was not cleanly shut down so it cannot be rebuilt. |
1819 | Could not create default log file because the name was too long. |
1820 | Disk '%.*ls' is already completely used by other databases. It can be expanded with DISK RESIZE. |
1826 | User-defined filegroups are not allowed on '%hs'. |
1827 | CREATE/ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of %d MB per %S_MSG. |
1828 | The file named '%.*ls' is already in use. Choose another name. |
1829 | The FOR ATTACH option requires that at least the primary file be specified. |
1830 | The files '%.*ls' and '%.*ls' are both primary files. A database can only have one primary file. |
1832 | Could not attach database '%.*ls' to file '%.*ls'. |
1833 | File '%ls' cannot be reused until after the next BACKUP LOG operation. |
1834 | The file '%ls' cannot be overwritten. It is being used by database '%.*ls'. |
1835 | Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d. |
TSQL Error Codes - 1900 to 1999
Error Code | Description |
---|---|
1901 | Column '%.*ls'. Cannot create index on a column of bit data type. |
1902 | Cannot create more than one clustered index on table '%.*ls'. Drop the existing clustered index '%.*ls' before creating another. |
1903 | Index keys are too large. The %d bytes needed to represent the keys for index %d exceeds the size limit of %d bytes. |
1904 | Cannot specify more than %d column names for statistics or index key list. %d specified. |
1905 | Could not find 'zero' row for index '%.*ls' the table in sysindexes. |
1906 | Cannot create an index on '%.*ls', because this table does not exist in database '%.*ls'. |
1907 | Cannot re-create index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index. |
1909 | Cannot use duplicate column names in index key list. Column name '%.*ls' listed more than once. |
1910 | Cannot create more than %d nonclustered indices or column statistics on one table. |
1911 | Column name '%.*ls' does not exist in the target table. |
1913 | There is already an index on table '%.*ls' named '%.*ls'. |
1914 | Index cannot be created on object '%.*ls' because the object is not a user table or view. |
1916 | CREATE INDEX options %ls and %ls are mutually exclusive. |
1918 | Index (ID = %d) is being rebuilt. |
1919 | Column '%.*ls'. Cannot create index on a column of text, ntext, or image data type. |
1920 | Skipping rebuild of index ID %d, which is on a read-only filegroup. |
1921 | Invalid filegroup '%.*ls' specified. |
1922 | Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and text, ntext, and image columns cannot be created on this filegroup. |
1923 | The clustered index has been dropped. |
1924 | Filegroup '%.*ls' is read-only. |
1925 | Cannot convert a clustered index to a nonclustered index using the DROP_EXISTING option. |
1926 | Cannot create a clustered index because nonclustered index ID %d is on a read-only filegroup. |
1927 | There are already statistics on table '%.*ls' named '%.*ls'. |
1928 | Cannot create statistics on table '%.*ls' because this table does not exist in database '%.*ls'. |
1929 | Statistics cannot be created on object '%.*ls' because the object is not a user table or view. |
1931 | Filegroup '%.*ls' is offline. |
1932 | Cannot create a clustered index because nonclustered index ID %d is on an offline filegroup. |
1933 | Cannot create index because the key column '%.*ls' is non-deterministic or imprecise. |
1934 | %ls failed because the following SET options have incorrect settings: '%.*ls'. |
1935 | Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'. |
1936 | Cannot %ls the %S_MSG '%.*ls'. It contains one or more disallowed constructs. |
1937 | Cannot index the view '%.*ls'. It references another view or function '%.*ls'. |
1938 | Index cannot be created on %S_MSG '%.*ls' because the underlying object '%.*ls' has a different owner. |
1939 | Cannot create %S_MSG on view '%.*ls' because the view is not schema bound. |
1940 | Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index. |
1941 | Nonunique clustered index cannot be created on view '%.*ls' because only unique clustered indexes are allowed. |
1942 | Index cannot be created on view '%.*ls' because the view contains text, ntext or image columns. |
1943 | Index cannot be created on view '%.*ls' because the view has one or more nondeterministic expressions. |
1944 | Index '%.*ls' was not created. This index has a key length of at least %d bytes. The maximum permissible key length is %d bytes. |
1945 | Warning! The maximum key length is %d bytes. The index '%.*ls' has maximum length of %d bytes. For some combination of large values, the insert/update operation will fail. |
1946 | Operation failed. The index entry of length %d bytes for the index '%.*ls' exceeds the maximum length of %d bytes. |
1947 | Index cannot be created on view '%.*ls' because the view contains a self-join on '%.*ls'. |
1948 | Duplicate index names '%.*ls' and '%.*ls' detected on table '%.*ls'. |
1949 | Index on view '%.*ls' cannot be created because function '%s' yields nondeterministic results. |
1950 | Index on view '%.*ls' cannot be created because the view contains an imprecise expression in a GROUP BY clause |
1951 | Index on view '%.*ls' cannot be created because the view contains an imprecise expression in the WHERE clause. |
1952 | Index on view '%.*ls' cannot be created because the view contains an imprecise expression in a join. |
1953 | Index on view '%.*ls' cannot be created because some arguments are missing in a built-in function. |
1954 | Index on view '%.*ls' cannot be created because the view uses a column bound to a rule. |
1955 | Index on view '%.*ls' cannot be created because the view contains a nondeterministic computed column. |
1956 | Index on view '%.*ls' cannot be created because the view uses a nondeterministic user-defined function. |
1957 | Index on view '%.*ls' cannot be created because the view requires a conversion involving dates or variants. |
1958 | This edition of SQL Server does not support indexed views. |
1959 | Cannot create index on view or computed column because this database is not SQL Server compatible. |
TSQL Error Codes - 2000 to 2099
Error Code | Description |
---|---|
2001 | Cannot use duplicate parameter names. Parameter name '%.*ls' listed more than once. |
2004 | Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number. |
2007 | Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object '%.*ls'. The stored procedure will still be created. |
2008 | The object '%.*ls' is not a procedure so you cannot create another procedure under that group name. |
2009 | Procedure '%.*ls' was created despite delayed name resolution warnings (if any). |
2010 | Cannot perform alter on %.*ls because it is an incompatible object type. |
2011 | Index hints cannot be specified within a schema-bound object. |
2012 | User-defined variables cannot be declared within a schema-bound object. |
TSQL Error Codes - 2100 to 2199
Error Code | Description |
---|---|
2106 | Cannot create a trigger on table '%.*ls', because this table does not exist in database '%.*ls'. |
2108 | Cannot create a trigger on table '%.*ls' because you can only create a trigger on a table in the current database. |
2110 | Cannot alter trigger '%.*ls' for table '%.*ls' because this trigger does not belong to this table. |
2111 | Cannot %s trigger '%.*ls' for %S_MSG '%.*ls' because an INSTEAD OF %s trigger already exists. |
2112 | Cannot %s trigger '%.*ls' for view '%.*ls' because it is defined with the CHECK OPTION. |
2113 | Cannot %s INSTEAD OF DELETE or UPDATE TRIGGER '%.*ls' on table '%.*ls' because the table has a FOREIGN KEY with cascaded DELETE or UPDATE. |
2114 | Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column. |
TSQL Error Codes - 2500 to 2599
Error Code | Description |
---|---|
2501 | Could not find a table or object named '%.*ls'. Check sysobjects. |
2502 | Could not start transaction. |
2503 | Successfully deleted the physical file '%ls'. |
2504 | Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls. |
2505 | The device '%.*ls' does not exist. Use sp_helpdevice to show available devices. |
2506 | Could not find a table or object name '%.*ls' in database '%.*ls'. |
2511 | Table error: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d. |
2512 | Table error: Object ID %d, Index ID %d. Duplicate keys on page %S_PGID slot %d and page %S_PGID slot %d. |
2513 | Table error: Object ID %ld (object '%.*ls') does not match between '%.*ls' and '%.*ls'. |
2514 | Table error: Data type %ld (type '%.*ls') does not match between '%.*ls' and '%.*ls'. |
2515 | Page %S_PGID, object ID %d, index ID %d has been modified but is not marked modified in the differential backup bitmap. |
2516 | The differential bitmap was invalidated for database %.*ls. A full database backup is required before a differential backup can be performed. |
2517 | The minimally logged operation status has been turned on for database %.*ls. Rerun backup log operations to ensure that all data has been secured. |
2519 | Unable to process table %.*ls because filegroup %.*ls is invalid. |
2520 | Could not find database '%.*ls'. Check sysdatabases. |
2521 | Could not find database ID %d. Check sysdatabases. |
2522 | Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid. |
2523 | Filegroup %.*ls is invalid. |
2524 | Unable to process table %.*ls because filegroup %.*ls is offline. |
2525 | Database file %.*ls is offline. |
2526 | Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options. |
2527 | Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline. |
2528 | DBCC execution completed. If DBCC printed error messages, contact your system administrator. |
2529 | Filegroup %.*ls is offline. |
2530 | Secondary index entries were missing or did not match the data in the table. Use the WITH TABLOCK option and run the command again to display the failing records. |
2531 | Table error: Object ID %d, index ID %d B-tree level mismatch, page %S_PGID. Level %d does not match level %d from previous %S_PGID. |
2532 | DBCC SHRINKFILE could not shrink file %ls. Log files are not supported. |
2533 | Table error: Page %S_PGID allocated to object ID %d, index ID %d was not seen. Page may be invalid or have incorrect object ID information in its header. |
2534 | Table error: Page %S_PGID with object ID %d, index ID %d in its header is allocated by another object. |
2535 | Table error: Page %S_PGID is allocated to object ID %d, index ID %d, not to object ID %d, index ID %d found in page header. |
2536 | DBCC results for '%.*ls'. |
2537 | Table error: Object ID %d, index ID %d, page %S_PGID, row %d. Record check (%hs) failed. Values are %ld and %ld. |
2538 | File %d. Number of extents = %ld, used pages = %ld, reserved pages = %ld. |
2539 | Total number of extents = %ld, used pages = %ld, reserved pages = %ld in this database. |
2540 | The system cannot self repair this error. |
2541 | DBCC UPDATEUSAGE: sysindexes row updated for table '%.*ls' (index ID %ld): |
2542 | DATA pages: Changed from (%ld) to (%ld) pages. |
2543 | USED pages: Changed from (%ld) to (%ld) pages. |
2544 | RSVD pages: Changed from (%ld) to (%ld) pages. |
2545 | ROWS count: Changed from (%I64d) to (%I64d) rows. |
2546 | Index '%.*ls' on table '%.*ls' is marked offline. Rebuild the index to bring it online. |
2547 | Performing second pass of index checks. |
2548 | DBCC: Compaction phase of index '%.*ls' is %d%% complete. |
2549 | DBCC: Defrag phase of index '%.*ls' is %d%% complete. |
2557 | User '%.*ls' does not have permission to run DBCC %ls for object '%.*ls'. |
2559 | The '%ls' and '%ls' options are not allowed on the same statement. |
2560 | Parameter %d is incorrect for this DBCC statement. |
2562 | '%ls' cannot access object '%.*ls' because it is not a table. |
2566 | DBCC DBREINDEX cannot be used on system tables. |
2567 | DBCC INDEXDEFRAG cannot be used on system table indexes |
2568 | Page %S_PGID is out of range for this database or is in a log file. |
2570 | Warning: Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value. |
2571 | User '%.*ls' does not have permission to run DBCC %.*ls. |
2572 | DBCC cannot free DLL '%.*ls'. The DLL is in use. |
2573 | Database '%.*ls' is not marked suspect. You cannot drop it with DBCC. |
2574 | Object ID %d, index ID %d: Page %S_PGID is empty. This is not permitted at level %d of the B-tree. |
2575 | IAM page %S_PGID is pointed to by the next pointer of IAM page %S_PGID object ID %d index ID %d but was not detected in the scan. |
2576 | IAM page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID object ID %d index ID %d but was not detected in the scan. |
2577 | Chain sequence numbers are out of order in IAM chain for object ID %d, index ID %d. Page %S_PGID sequence number %d points to page %S_PGID sequence number %d. |
2578 | Minimally logged extents were found in GAM interval starting at page %S_PGID but the minimally logged flag is not set in the database table. |
2579 | Table error: Extent %S_PGID object ID %d, index ID %d is beyond the range of this database. |
2580 | Table '%.*ls' is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table. |
2583 | An incorrect number of parameters was given to the DBCC statement. |
2588 | Page %S_PGID was expected to be the first page of a text, ntext, or image value. |
2590 | User '%.*ls' is modifying bytes %d to %d of page %S_PGID in database '%.*ls'. |
2591 | Could not find row in sysindexes with index ID %d for table '%.*ls'. |
2592 | %ls index successfully restored for object '%.*ls' in database '%.*ls'. |
2593 | There are %I64d rows in %ld pages for object '%.*ls'. |
2594 | Invalid index ID (%d) specified. |
2595 | Database '%.*ls' must be set to single user mode before executing this statement. |
2597 | The database is not open. Execute a 'USE %.*ls' statement and rerun the DBCC statement. |
2598 | Clustered indexes on sysobjects and sysindexes cannot be re-created. |
TSQL Error Codes - 2600 to 2699
Error Code | Description |
---|---|
2601 | Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'. |
2603 | No space left on logical page %S_PGID of index ID %d for object '%.*ls' when inserting row on an index page. This situation should have been handled while traversing the index. |
2617 | Buffer holding logical page %S_PGID not found in keep pool in SDES for object '%.*ls'. Contact Technical Support. |
2624 | Could not insert into table %S_DES because row length %d is less than the minimum length %d. |
2627 | Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'. |
TSQL Error Codes - 2700 to 2799
Error Code | Description |
---|---|
2701 | Database name '%.*ls' ignored, referencing object in tempdb. |
2702 | Database '%.*ls' does not exist. |
2705 | Column names in each table must be unique. Column name '%.*ls' in table '%.*ls' is specified more than once. |
2706 | Table '%.*ls' does not exist. |
2710 | You are not the owner specified for the object '%.*ls' in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT). |
2714 | There is already an object named '%.*ls' in the database. |
2715 | Column or parameter #%d: Cannot find data type %.*ls. |
2716 | Column or parameter #%d: Cannot specify a column width on data type %.*ls. |
2717 | The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed (%d). |
2718 | Column or parameter #%d: Cannot specify null values on a column of data type bit. |
2721 | Could not find a default segment to create the table on. Ask your system administrator to specify a default segment in syssegments. |
2724 | Parameter '%.*ls' has an invalid data type. |
2727 | Cannot find index '%.*ls'. |
2730 | Cannot create procedure '%.*ls' with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE '%.*ls';1 first. |
2731 | Column '%.*ls' has invalid width: %d. |
2732 | Error number %ld is invalid. The number must be from %ld through %ld |
2734 | The user name '%.*ls' does not exist in sysusers. |
2736 | Owner name specified is a group name. Objects cannot be owned by groups. |
2737 | Message passed to %hs must be of type char, varchar, nchar, or nvarchar. |
2738 | A table can only have one timestamp column. Because table '%.*ls' already has one, the column '%.*ls' cannot be added. |
2739 | The text, ntext, and image data types are invalid for local variables. |
2740 | SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server. |
2741 | SET DATEFORMAT date order '%.*ls' is invalid. |
2742 | SET DATEFIRST %d is out of range. |
2743 | %ls statement requires %S_MSG parameter. |
2744 | Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed. |
2745 | Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process. |
2746 | Cannot specify user error format string with a length exceeding %d bytes. |
2747 | Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters. |
2748 | Cannot specify %ls data type (RAISERROR parameter %d) as a substitution parameter for RAISERRROR. |
2749 | Identity column '%.*ls' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, and constrained to be nonnullable. |
2750 | Column or parameter #%d: Specified column precision %d is greater than the maximum precision of %d. |
2751 | Column or parameter #%d: Specified column scale %d is greater than the specified precision of %d. |
2752 | Identity column '%.*ls' contains invalid SEED. |
2753 | Identity column '%.*ls' contains invalid INCREMENT. |
2754 | Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option. |
2755 | SET DEADLOCK_PRIORITY option '%.*ls' is invalid. |
2756 | Invalid value %d for state. Valid range is from %d to %d. |
2757 | RAISERROR failed due to invalid parameter substitution(s) for error %d, severity %d, state %d. |
2758 | %hs could not locate entry for error %d in sysmessages. |
2759 | CREATE SCHEMA failed due to previous errors. |
2760 | Specified owner name '%.*ls' either does not exist or you do not have permission to use it. |
2761 | The ROWGUIDCOL property can only be specified on the uniqueidentifier data type. |
2762 | sp_setapprole was not invoked correctly. Refer to the documentation for more information. |
2763 | Could not find application role '%.*ls'. |
2764 | Incorrect password supplied for application role '%.*ls'. |
2765 | Could not locate statistics for column '%.*ls' in the system catalogs. |
2766 | The definition for user-defined data type '%.*ls' has changed. |
2767 | Could not locate statistics '%.*ls' in the system catalogs. |
2768 | Statistics for %ls '%.*ls'. |
2769 | Column '%.*ls'. Cannot create statistics on a column of data type %ls. |
2770 | The SELECT INTO statement cannot have same source and destination tables. |
2771 | Cannot create statistics on table '%.*ls'. This table is a virtual system table. |
2772 | Cannot access temporary tables from within a function. |
2773 | Sort order ID %d is invalid. |
2774 | Collation ID %d is invalid. |
2775 | Code page %d is not supported by the operating system. |
2777 | Database '%.*ls' contains columns or parameters with the following code page(s) not supported by the operating system: %ls. |
TSQL Error Codes - 2800 to 2899
Error Code | Description |
---|---|
2801 | The definition of object '%.*ls' has changed since it was compiled. |
2809 | The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object. |
2812 | Could not find stored procedure '%.*ls'. |
TSQL Error Codes - 3000 to 3099
Error Code | Description |
---|---|
3009 | Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful. |
3011 | All backup devices must be of the same general class (for example, DISK and TAPE). |
3013 | %hs is terminating abnormally. |
3014 | %hs successfully processed %d pages in %d.%03d seconds (%d.%03d MB/sec). |
3015 | %hs is not yet implemented. |
3016 | File '%ls' of database '%ls' has been removed or shrunk since this backup or restore operation was interrupted. The operation cannot be restarted. |
3017 | Could not resume interrupted backup or restore operation. See the SQL Server error log for more information. |
3018 | There is no interrupted backup or restore operation to restart. Reissue the statement without the RESTART clause. |
3019 | The checkpoint file was for a different backup or restore operation. Reissue the statement without the RESTART clause. |
3020 | The backup operation cannot be restarted as the log has been truncated. Reissue the statement without the RESTART clause. |
3021 | Cannot perform a backup or restore operation within a transaction. |
3023 | Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed. |
3024 | You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database. |
3025 | Missing database name. Reissue the statement specifying a valid database name. |
3026 | Could not find filegroup ID %d in sysfilegroups for database '%ls'. |
3027 | Could not find filegroup '%.*ls' in sysfilegroups for database '%.*ls'. |
3028 | Operation checkpoint file is invalid. Could not restart operation. Reissue the statement without the RESTART option. |
3031 | Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement. |
3032 | One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options. |
3033 | BACKUP DATABASE cannot be used on a database opened in emergency mode. |
3034 | No files were selected to be processed. You may have selected one or more filegroups that have no members. |
3035 | Cannot perform a differential backup for database '%ls', because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. |
3036 | Database '%ls' is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire load sequence is completed. |
3037 | Minimally logged operations have occurred prior to this WITH RESTART command. Reissue the BACKUP statement without WITH RESTART. |
3038 | The filename '%ls' is invalid as a backup device name. Reissue the BACKUP statement with a valid filename. |
3039 | Cannot perform a differential backup for file '%ls' because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option. |
3040 | An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected. |
3041 | BACKUP failed to complete the command %.*ls |
TSQL Error Codes - 3100 to 3199
Error Code | Description |
---|---|
3101 | Exclusive access could not be obtained because the database is in use. |
3108 | RESTORE DATABASE must be used in single user mode when trying to restore the master database. |
3110 | User does not have permission to RESTORE database '%.*ls'. |
3112 | Cannot restore any database other than master when the server is in single user mode. |
3113 | The database owner (DBO) does not have an entry in sysusers in database '%.*ls'. |
3114 | Database '%.*ls' does not have an entry in sysdatabases. |
3123 | Invalid database name '%.*ls' specified for backup or restore operation. |
3127 | Temporary Message: The backup set does not contain pages for file '%ls'. |
3128 | File '%ls' has an unsupported page size (%d). |
3129 | Temporary Message: File '%ls' has changed size from %d to %d bytes. |
3132 | The media set for database '%ls' has %d family members but only %d are provided. All members must be provided. |
3133 | The volume on device '%ls' is not a member of the media family. |
3135 | The backup set in file '%ls' was created by %hs and cannot be used for this restore operation. |
3136 | Cannot apply the backup on device '%ls' to database '%ls'. |
3138 | One or more files in the backup set are no longer part of database '%ls'. |
3140 | Could not adjust the space allocation for file '%ls'. |
3141 | The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database. |
3142 | File '%ls' cannot be restored over the existing '%ls'. Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files. |
3143 | The data set on device '%ls' is not a SQL Server backup set. |
3144 | File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set. |
3145 | The STOPAT option is not supported for RESTORE DATABASE. You can use the STOPAT option with RESTORE LOG. |
3146 | None of the newly-restored files had been modified after the backup was taken, so no further recovery actions are required. The database is now available for use. |
3147 | Backup and restore operations are not allowed on database tempdb. |
3148 | Media recovery for ALTER DATABASE is not yet implemented. The database cannot be rolled forward. |
3150 | The master database has been successfully restored. Shutting down SQL Server. |
3151 | The master database failed to restore. Use the rebuildm utility to rebuild the master database. Shutting down SQL Server. |
3152 | Cannot overwrite file '%ls' because it is marked as read-only. |
3153 | The database is already fully recovered. |
3154 | The backup set holds a backup of a database other than the existing '%ls' database. |
3155 | The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created. |
3156 | File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identify a valid location for the file. |
3157 | The logical file (%d) is named '%ls'. RESTORE will not overwrite it from '%ls'. |
3158 | Could not create one or more files. Consider using the WITH MOVE option to identify valid locations. |
3159 | The tail of the log for database '%ls' has not been backed up. Back up the log and rerun the RESTORE statement specifying the FILE clause. |
3160 | Could not update primary file information in sysdatabases. |
3161 | The primary file is unavailable. It must be restored or otherwise made available. |
3162 | The database has on-disk structure version %d. The server supports version %d and can only restore such a database that was inactive when it was backed up. This database was not inactive. |
3163 | The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted. |
3164 | Cannot roll forward the database with on-disk structure version %d. The server supports version %d. Reissue the RESTORE statement WITH RECOVERY. |
3165 | Could not adjust the replication state of database '%ls'. The database was successfully restored, however its replication state is indeterminate. See the Troubleshooting Replication section in SQL Server Books Online. |
3166 | RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement. |
3167 | RESTORE could not start database '%ls'. |
3168 | The backup of the system database on device %ls cannot be restored because it was created by a different version of the server (%u) than this server (%u). |
3169 | The backed-up database has on-disk structure version %d. The server supports version %d and cannot restore or upgrade this database. |
3170 | The STANDBY filename is invalid. |
3171 | Cannot restore file %ls because the file is offline. |
3172 | Cannot restore filegroup %ls because the filegroup is offline. |
3174 | The file '%ls' cannot be moved by this RESTORE operation. |
3175 | The filegroup '%ls' cannot be restored because all of the files are not present in the backup set. File '%ls' is missing. |
3176 | File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files. |
3177 | Only members of the dbcreator and sysadmin roles can execute the %ls statement. |
3178 | File %ls is not in the correct state to have this differential backup applied to it. |
3179 | The system database cannot be moved by RESTORE. |
3180 | This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY. |
TSQL Error Codes - 3200 to 3299
Error Code | Description |
---|---|
3201 | Cannot open backup device '%ls'. Device error or device off-line. See the SQL Server error log for more details. |
3202 | Write on '%ls' failed, status = %ld. See the SQL Server error log for more details. |
3203 | Read on '%ls' failed, status = %ld. See the SQL Server error log for more details. |
3204 | Operator aborted backup or restore. See the error messages returned to the console for more details. |
3205 | Too many backup devices specified for backup or restore; only %d are allowed. |
3206 | No entry in sysdevices for backup device '%.*ls'. Update sysdevices and rerun statement. |
3207 | Backup or restore requires at least one backup device. Rerun your statement specifying a backup device. |
3208 | Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error log for more details. |
3209 | '%.*ls' is not a backup device. Check sysdevices. |
3211 | %d percent %hs. |
3217 | Invalid value specified for %ls parameter. |
3221 | The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d. |
3222 | The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d. |
3224 | Cannot create worker thread. |
3227 | The volume on device '%ls' is a duplicate of stripe set member %d. |
3229 | Request for device '%ls' timed out. |
3230 | Operation on device '%ls' exceeded retry count. |
3234 | Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names. |
3235 | File '%ls' is not part of database '%ls'. You can only list files that are members of this database. |
3237 | Option not supported for Named Pipe-based backup sets. |
3239 | The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server. |
3241 | The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family. |
3242 | The file on device '%ls' is not a valid Microsoft Tape Format backup set. |
3243 | The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d. |
3244 | Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation. |
3245 | Could not convert a string to or from Unicode, %ls. |
3246 | The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media. |
3247 | The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d. |
3248 | >>> VOLUME SWITCH <<< (not for output!) |
3249 | The volume on device '%ls' is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set. |
3250 | The value '%d' is not within range for the %ls parameter. |
3251 | The media family on device '%ls' is complete. The device is now being reused for one of the remaining families. |
3253 | The block size parameter must supply a value that is a power of 2. |
3254 | The volume on device '%ls' is empty. |
3255 | The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server. |
3256 | The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally. |
3257 | There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64u bytes are available. |
3258 | The volume on device '%ls' belongs to a different media set. |
3259 | The volume on device '%ls' is not part of a multiple family media set. BACKUP WITH FORMAT can be used to form a new media set. |
3260 | An internal buffer has become full. |
3261 | SQL Server cannot use the virtual device configuration. |
3262 | The backup set is valid. |
3263 | Cannot use the volume on device '%ls' as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, or sequence number %d of family %d for the current set. |
3264 | The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier. |
3265 | The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. |
3266 | The backup data in '%ls' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. |
3267 | Insufficient resources to create UMS scheduler. |
3268 | Cannot use the backup file '%ls' because it was originally formatted with sector size %d and is now on a device with sector size %d. |
3269 | Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d. |
3270 | An internal consistency error occurred. Contact Technical Support for assistance. |
3271 | Nonrecoverable I/O error occurred on file '%ls'. |
3272 | The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement using a compatible block size. |
3273 | The BUFFERCOUNT parameter must supply a value that allows at least one buffer per backup device. |
3274 | Incorrect checksum computed for the backup set on device %ls. The backup set cannot be restored. |
3275 | I/O request 0x%08x failed I/O verification. See the error log for a description. |
3276 | WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT. |
3277 | WITH SNAPSHOT must be used with only one virtual device. |
3278 | Failed to encrypt string %ls |
3279 | Access is denied due to a password failure |
3280 | Backups on raw devices are not supported. '%ls' is a raw device. |
3281 | Released and initiated rewind on '%ls'. |
TSQL Error Codes - 3300 to 3399
Error Code | Description |
---|---|
3301 | Invalid log record found in the transaction log (logop %d). |
3313 | Error while redoing logged operation in database '%.*ls'. Error at log record ID %S_LSN. |
3314 | Error while undoing logged operation in database '%.*ls'. Error at log record ID %S_LSN. |
3315 | During rollback, process %d was expected to hold mode %d lock at level %d for row %S_RID in database '%.*ls' under transaction %S_XID. |
TSQL Error Codes - 3400 to 3499
Error Code | Description |
---|---|
3405 | Recovering database '%.*ls'. |
3406 | %d transactions rolled forward in database '%.*ls' (%d). |
3407 | %d transactions rolled back in database '%.*ls' (%d). |
3408 | Recovery complete. |
3413 | Database ID %d. Could not mark database as suspect. Getnext NC scan on sysdatabases.dbid failed. |
3414 | Database '%.*ls' (database ID %d) could not recover. Contact Technical Support. |
3415 | Database '%.*ls' is read-only or has read-only files and must be made writable before it can be upgraded. |
3417 | Cannot recover the master database. Exiting. |
3429 | Warning: The outcome of transaction %S_XID, named '%.*ls' in database '%.*ls' (database ID %d), could not be determined because the coordinating database (database ID %d) could not be opened. The transaction was assumed to be committed. |
3430 | Warning: Could not determine the outcome of transaction %S_XID, named '%.*ls' in database '%.*ls' (with ID %d) because the coordinating database (ID %d) did not contain the outcome. The transaction was assumed to be committed. |
3431 | Could not recover database '%.*ls' (database ID %d) due to unresolved transaction outcomes. |
3432 | Warning: syslanguages is missing. |
3433 | Name is truncated to '%.*ls'. The maximum name length is %d. |
3434 | Cannot change sort order or locale. Server shutting down. Restart SQL Server to continue with sort order unchanged. |
3435 | Sort order or locale cannot be changed because user objects or user databases exist. |
3436 | Cannot rebuild index for the '%.*ls' table in the '%.*ls' database. |
3437 | Error recovering database '%.*ls'. Could not connect to MSDTC to check the completion status of transaction %S_XID. |
3438 | Database '%.*ls' (database ID %d) failed to recover because transaction first LSN is not equal to LSN in checkpoint. Contact Technical Support. |
3439 | Database '%.*ls' (database ID %d). The DBCC RECOVERDB statement failed due to previous errors. |
3440 | Database '%.*ls' (database ID %d). The DBCC RECOVERDB statement can only be run after a RESTORE statement that used the WITH NORECOVERY option. |
3441 | Database '%.*ls' (database ID %d). The RESTORE statement could not access file '%ls'. Error was '%ls'. |
3442 | Database '%.*ls' (database ID %d). The size of the undo file is insufficient. |
3443 | Database '%.*ls' (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. |
3445 | File '%ls' is not a valid undo file for database '%.*ls', database ID %d. |
3446 | Primary log file is not available for database '%.*ls'. The log cannot be backed up. |
3447 | Could not activate or scan all of the log files for database '%.*ls'. |
3448 | Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. |
3449 | An error has occurred that requires SQL Server to shut down so that recovery can be performed on database ID %d. |
3450 | Recovery of database '%.*ls' (%d) is %d%% complete (approximately %d more seconds) (Phase %d of 3). |
3451 | Recovery has failed because reexecution of CREATE INDEX found inconsistencies between target filegroup '%ls' (%d) and source filegroup '%ls' (%d). Restore both filegroups before attempting further RESTORE LOG operations. |
3452 | Recovery of database '%.*ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls'). |
3453 | This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible. |
3454 | Recovery is checkpointing database '%.*ls' (%d) |
3455 | Analysis of database '%.*ls' (%d) is %d%% complete (approximately %d more seconds) |
3456 | Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (%d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. |
TSQL Error Codes - 3500 to 3599
Error Code | Description |
---|---|
3501 | Could not find row in sysdatabases for database ID %d at checkpoint time. |
3505 | Only the owner of database '%.*ls' can run the CHECKPOINT statement. |
3508 | Could not get an exclusive lock on the database '%.*ls'. Make sure that no other users are currently using this database, and rerun the CHECKPOINT statement. |
3509 | Could not set database '%.*ls' %ls read-only user mode because you could not exclusively lock the database. |
3510 | Database '%.*ls' cannot be changed from read-only because the primary and/or log file(s) are not writable. |
TSQL Error Codes - 3600 to 3699
Error Code | Description |
---|---|
3604 | Duplicate key was ignored. |
3605 | Duplicate row was ignored. |
3606 | Arithmetic overflow occurred. |
3607 | Division by zero occurred. |
3608 | Cannot allocate a GUID for the token. |
3612 | %hsSQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms. |
3613 | SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms. |
3615 | Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d. |
3618 | The transaction has been terminated. |
3619 | Could not write a CHECKPOINT record in database ID %d because the log is out of space. |
3620 | Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. It will continue when the database owner successfully checkpoints the database. Free up some space or extend the database and then run the CHECKPOINT statement. |
3621 | The statement has been terminated. |
3622 | A domain error occurred. |
3625 | '%hs' is not yet implemented. |
3627 | Could not create worker thread. |
3628 | A floating point exception occurred in the user process. Current transaction is canceled. |
3629 | This SQL Server has been optimized for %d concurrent queries. This limit has been exceeded by %d queries and performance may be adversely affected. |
3630 | Concurrency violations since %ls%s 1 2 3 4 5 6 7 8 9 10-100 >100%s%6u%6u%6u%6u%6u%6u%6u%6u%6u%8u%6u |
3631 | Concurrency violations will be written to the SQL Server error log. |
3632 | Concurrency violations will not be written to the SQL Server error log. |
TSQL Error Codes - 3700 to 3799
Error Code | Description |
---|---|
3701 | Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist in the system catalog. |
3702 | Cannot drop the %S_MSG '%.*ls' because it is currently in use. |
3703 | Cannot detach the %S_MSG '%.*ls' because it is currently in use. |
3704 | User does not have permission to perform this operation on %S_MSG '%.*ls'. |
3705 | Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use DROP %ls. |
3708 | Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG. |
3716 | The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG. |
3718 | Could not drop index '%.*ls' because the table or clustered index entry cannot be found in the sysindexes system table. |
3723 | An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement. |
3724 | Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for replication. |
3725 | The constraint '%.*ls' is being referenced by table '%.*ls', foreign key constraint '%.*ls'. |
3726 | Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint. |
3727 | Could not drop constraint. See previous errors. |
3728 | '%.*ls' is not a constraint. |
3729 | Cannot %ls '%.*ls' because it is being referenced by object '%.*ls'. |
3733 | Constraint '%.*ls' does not belong to table '%.*ls'. |
3736 | Cannot drop the %S_MSG '%.*ls' because it is being used for distribution. |
3737 | Could not delete file '%ls'. See the SQL Server error log for more information. |
3738 | Deleting database file '%ls'. |
3739 | Cannot %ls the index '%.*ls' because it is not a statistics collection. |
3740 | Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup. |
3741 | Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on an offline filegroup. |
TSQL Error Codes - 3900 to 3999
Error Code | Description |
---|---|
3902 | The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION. |
3903 | The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. |
3904 | Cannot unsplit logical page %S_PGID in object '%.*ls', in database '%.*ls'. Both pages together contain more data than will fit on one page. |
3906 | Could not run BEGIN TRANSACTION in database '%.*ls' because the database is read-only. |
3908 | Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in bypass recovery mode. |
3909 | Session binding token is invalid. |
3910 | Transaction context in use by another session. |
3912 | Cannot bind using an XP token while the server is not in an XP call. |
3914 | The data type '%s' is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, or nvarchar. |
3915 | Cannot use the ROLLBACK statement within an INSERT-EXEC statement. |
3916 | Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first. |
3917 | Session is bound to a transaction context that is in use. Other statements in the batch were ignored. |
3918 | Statement must be executed in the context of a user transaction. |
3919 | Cannot enlist in the transaction because the transaction has already been committed or rolled back. |
3920 | The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored. |
3921 | Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started |
3922 | Cannot enlist in the transaction because the transaction does not exist. |
3923 | Cannot use transaction marks on database '%.*ls' with bulk-logged operations that have not been backed up. The mark is ignored. |
3924 | The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction. |
3925 | Invalid transaction mark name. The 'LSN:' prefix is reserved. |
3926 | The transaction active in this session has been committed or aborted by another session. |
3927 | The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction. |
3928 | The marked transaction '%.*ls' failed. A Deadlock was encountered while attempting to place the mark in the log. |
TSQL Error Codes - 4000 to 4099
Error Code | Description |
---|---|
4003 | ODS error. Server is terminating this connection. |
4004 | Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. |
4015 | Language requested in login '%.*ls' is not an official name on this SQL Server. Using server-wide default %.*ls instead. |
4016 | Language requested in 'login %.*ls' is not an official name on this SQL Server. Using user default %.*ls instead. |
4017 | Neither the language requested in 'login %.*ls' nor user default language %.*ls is an official language name on this SQL Server. Using server-wide default %.*ls instead. |
4018 | User default language %.*ls is not an official language name on this SQL Server. Using server-wide default %.*ls instead. |
4019 | Language requested in login '%.*ls' is not an official language name on this SQL Server. Login fails. |
4020 | Default date order '%.*ls' for language %.*ls is invalid. Using mdy instead. |
4027 | Mount tape for %hs of database '%ls'. |
4028 | End of tape has been reached. Remove tape '%ls' and mount next tape for %hs of database '%ls'. |
4030 | The medium on device '%ls' expires on %hs and cannot be overwritten. |
4035 | Processed %d pages for database '%ls', file '%ls' on file %d. |
4037 | User-specified volume ID '%ls' does not match the volume ID '%ls' of the device '%ls'. |
4038 | Cannot find file ID %d on device '%ls'. |
4060 | Cannot open database requested in login '%.*ls'. Login fails. |
4061 | Cannot open either database requested in login (%.*ls) or user default database. Using master database instead. |
4062 | Cannot open user default database. Using master database instead. |
4063 | Cannot open database requested in login (%.*ls). Using user default '%.*ls' instead. |
4064 | Cannot open user default database. Login failed. |
TSQL Error Codes - 4200 to 4299
Error Code | Description |
---|---|
4208 | The statement %hs is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE. |
4212 | Cannot back up the log of the master database. Use BACKUP DATABASE instead. |
4214 | There is no current database backup. This log backup cannot be used to roll forward a preceding database backup. |
4215 | The log was not truncated because records at the beginning of the log are pending replication. Ensure the Log Reader Agent is running or use sp_repldone to mark transactions as distributed. |
4216 | Minimally logged operations cannot be backed up when the database is unavailable. |
4217 | BACKUP LOG cannot modify the database because database is read-only. The backup will continue,although subsequent backups will duplicate the work of this backup. |
TSQL Error Codes - 4300 to 4399
Error Code | Description |
---|---|
4301 | Database in use. The system administrator must have exclusive use of the database to restore the log. |
4304 | A USER ATTENTION signal raised during RESTORE LOG is being ignored until the current restore completes. |
4305 | The log in this backup set begins at LSN %.*ls, which is too late to apply to the database. An earlier log backup that includes LSN %.*ls can be restored. |
4306 | The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence, specifying WITH NORECOVERY or WITH STANDBY for all but the final step. |
4316 | Can only RESTORE LOG in the master database if SQL Server is in single user mode. |
4318 | File '%ls' has been rolled forward to LSN %.*ls. This log terminates at LSN %.*ls, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY. |
4320 | File '%ls' was only partially restored by a database or file restore. The entire file must be successfully restored before applying the log. |
4322 | This log file contains records logged before the designated point-in-time. The database is being left in load state so you can apply another log file. |
4323 | The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database. |
4324 | Backup history older than %ls has been deleted. |
4325 | Could not delete entries for backup set ID '%ls'. |
4326 | The log in this backup set terminates at LSN %.*ls, which is too early to apply to the database. A more recent log backup that includes LSN %.*ls can be restored. |
4327 | The log in this backup set contains minimally logged changes. Point-in-time recovery is inhibited. RESTORE will roll forward to end of logs without recovering the database. |
4328 | File '%ls' is missing. Rollforward stops at log sequence number %.*ls. File is created at LSN %.*ls, dropped at LSN %.*ls. Restore transaction log beyond beyond point in time when file was dropped or restore data to be consistent with rest of database. |
4329 | This log file contains records logged before the designated mark. The database is being left in load state so you can apply another log file. |
4330 | The log in this backup set cannot be applied because it is on a recovery path inconsistent with the database. |
4331 | The database cannot be recovered because the files have been restored to inconsistent points in time. |
4332 | RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY. |
4333 | The database cannot be recovered because the log was not restored. |
4334 | The named mark does not identify a valid LSN. |
TSQL Error Codes - 4400 to 4499
Error Code | Description |
---|---|
4403 | View or function '%.*ls' is not updatable because it contains aggregates. |
4404 | View or function '%.*ls' is not updatable because the definition contains the DISTINCT clause. |
4405 | View or function '%.*ls' is not updatable because the modification affects multiple base tables. |
4406 | Update or insert of view or function '%.*ls' failed because it contains a derived or constant field. |
4408 | The query and the views or functions in it exceed the limit of %d tables. |
4413 | Could not use view or function '%.*ls' because of binding errors. |
4414 | Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%d) was exceeded. |
4415 | View '%.*ls' is not updatable because either it was created WITH CHECK OPTION or it spans a view created WITH CHECK OPTION and the target table is referenced multiple times in the resulting query. |
4416 | UNION ALL view '%.*ls' is not updatable because the definition contains a disallowed construct. |
4417 | Derived table '%.*ls' is not updatable because the definition contains a UNION operator. |
4418 | Derived table '%.*ls' is not updatable because it contains aggregates. |
4419 | Derived table '%.*ls' is not updatable because the definition contains the DISTINCT clause. |
4420 | Derived table '%.*ls' is not updatable because the modification affects multiple base tables. |
4421 | Derived table '%.*ls' is not updatable because a column of the derived table is derived or constant. |
4422 | View '%.*ls' has an INSTEAD OF UPDATE trigger and cannot be a target of an UPDATE FROM statement. |
4423 | View '%.*ls' has an INSTEAD OF DELETE trigger and cannot be a target of a DELETE FROM statement. |
4424 | Joined tables cannot be specified in a query containing outer join operators. View or function '%.*ls' contains joined tables. |
4425 | Cannot specify outer join operators in a query containing joined tables. View or function '%.*ls' contains outer join operators. |
4427 | The view or function '%.*ls' is not updatable because the definition contains the TOP clause. |
4428 | The derived table '%.*ls' is not updatable because the definition contains the TOP clause. |
4429 | View or function '%.*ls' contains a self-reference. Views or functions cannot reference themselves directly or indirectly. |
4430 | Warning: Index hints supplied for view '%.*ls' will be ignored. |
4431 | Partitioned view '%.*ls' is not updatable because table '%.*ls' has a timestamp column. |
4432 | Partitioned view '%.*ls' is not updatable because table '%.*ls' has a DEFAULT constraint. |
4433 | Cannot INSERT into partitioned view '%.*ls' because table '%.*ls' has an IDENTITY constraint. |
4434 | Partitioned view '%.*ls' is not updatable because table '%.*ls' has an INSTEAD OF trigger. |
4435 | Partitioned view '%.*ls' is not updatable because a value was not specified for partitioning column '%.*ls'. |
4436 | UNION ALL view '%.*ls' is not updatable because a partitioning column was not found. |
4437 | Partitioned view '%.*ls' is not updatable as the target of a bulk operation. |
4438 | Partitioned view '%.*ls' is not updatable because it does not deliver all columns from its member tables. |
4439 | Partitioned view '%.*ls' is not updatable because the source query contains references to partition table '%.*ls'. |
4440 | UNION ALL view '%.*ls' is not updatable because a primary key was not found on table '%.*ls'. |
4441 | Partitioned view '%.*ls' is not updatable because the table '%.*ls' has an index on a computed column. |
4442 | UNION ALL view '%.*ls' is not updatable because base table '%.*ls' is used multiple times. |
4443 | UNION ALL view '%.*ls' is not updatable because column '%.*ls' of base table '%.*ls' is used multiple times. |
4444 | UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not included in the union result. |
4445 | UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not unioned with primary keys of preceding tables. |
4446 | UNION ALL view '%.*ls' is not updatable because the definiton of column '%.*ls' of view '%.*ls' is used by another view column. |
4447 | View '%.*ls' is not updatable because the definition contains a set operator. |
4448 | Cannot INSERT into partitioned view '%.*ls' because values were not supplied for all columns. |
4449 | Using defaults is not allowed in views that contain a set operator. |
4450 | Cannot update partitioned view '%.*ls' because the definition of the view column '%.*ls' in table '%.*ls' has a IDENTITY constraint. |
4451 | Views referencing tables on multiple servers are not updatable on this SKU of SQL Server. |
4452 | Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a CASCADE DELETE or CASCADE UPDATE constraint. |
4453 | Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a INSERT, UPDATE or DELETE trigger. |
TSQL Error Codes - 4500 to 4599
Error Code | Description |
---|---|
4501 | View or function '%.*ls' has more columns defined than column names given. |
4502 | View or function '%.*ls' has more column names specified than columns defined. |
4505 | CREATE VIEW failed because column '%.*ls' in view '%.*ls' exceeds the maximum of %d columns. |
4506 | Column names in each view or function must be unique. Column name '%.*ls' in view or function '%.*ls' is specified more than once. |
4508 | Views or functions are not allowed on temporary tables. Table names that begin with '#' denote temporary tables. |
4509 | Could not perform CREATE VIEW because WITH %ls was specified and the view contains set operators. |
4510 | Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable. |
4511 | Create View or Function failed because no column name was specified for column %d. |
4512 | Cannot schema bind %S_MSG '%.*ls' because name '%.*ls' is invalid for schema binding. Names must be in two-part format and an object cannot reference itself. |
4513 | Cannot schema bind %S_MSG '%.*ls'. '%.*ls' is not schema bound. |
4514 | CREATE FUNCTION failed because a column name is not specified for column %d. |
4515 | CREATE FUNCTION failed because column '%.*ls' in function '%.*ls' exceeds the maximum of %d columns. |
4516 | Cannot schema bind function '%.*ls' because it contains an EXECUTE statement. |
TSQL Error Codes - 4600 to 4699
Error Code | Description |
---|---|
4602 | Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission. |
4604 | There is no such user or group '%.*ls'. |
4606 | Granted or revoked privilege %ls is not compatible with object. |
4610 | You can only grant or revoke permissions on objects in the current database. |
4611 | To revoke grantable privileges, specify the CASCADE option with REVOKE. |
4613 | Grantor does not have GRANT permission. |
4615 | Invalid column name '%.*ls'. |
4617 | Cannot grant, deny or revoke permissions to or from special roles. |
4618 | You do not have permission to use %.*ls in the AS clause. |
4619 | CREATE DATABASE permission can only be granted in the master database. |
TSQL Error Codes - 4700 to 4799
Error Code | Description |
---|---|
4701 | Could not truncate table '%.*ls' because this table does not exist in database '%.*ls'. |
4706 | Could not truncate table '%.*ls' because there is not enough room in the log to record the deallocation of all the index and data pages. |
4707 | Could not truncate object '%.*ls' because it or one of its indexes resides on a READONLY filegroup. |
4708 | Could not truncate object '%.*ls' because it is not a table. |
4709 | You are not allowed to truncate the system table '%.*ls'. |
4711 | Cannot truncate table '%.*ls' because it is published for replication. |
4712 | Cannot truncate table '%.*ls' because it is being referenced by a FOREIGN KEY constraint. |
TSQL Error Codes - 4800 to 4899
Error Code | Description |
---|---|
4803 | Received invalid row length %d from bcp client. Maximum row size is %d. |
4804 | Premature end-of-message while reading current row from host. Host program may have terminated. |
4805 | The front-end tool you are using does not support the feature of bulk insert from host. Use the proper tools for this command. |
4807 | Received invalid row length %d from bcp client. Minimum row size is %d. |
4808 | Bulk copy operations cannot trigger BULK INSERT statements. |
4810 | Expected the TEXT token in data stream for bulk copy of text or image data. |
4811 | Expected the column offset in data stream for bulk copy of text or image data. |
4812 | Expected the row offset in data stream for bulk copy of text or image data. |
4813 | Expected the text length in data stream for bulk copy of text, ntext, or image data. |
4815 | Received invalid column length from bcp client. |
4817 | Could not bulk insert. Invalid sorted column '%.*ls'. Assuming data stream is not sorted. |
4818 | Could not bulk insert. Sorted column '%.*ls' was specified more than once. Assuming data stream is not sorted. |
4819 | Could not bulk insert. Bulk data stream was incorrectly specified as sorted. |
4820 | Could not bulk insert. Unknown version of format file '%s'. |
4821 | Could not bulk insert. Error reading the number of columns from format file '%s'. |
4822 | Could not bulk insert. Invalid number of columns in format file '%s'. |
4823 | Could not bulk insert. Invalid column number in format file '%s'. |
4824 | Could not bulk insert. Invalid data type for column number %d in format file '%s'. |
4825 | Could not bulk insert. Invalid prefix for column number %d in format file '%s'. |
4826 | Could not bulk insert. Invalid column length for column number %d in format file '%s'. |
4827 | Could not bulk insert. Invalid column terminator for column number %d in format file '%s'. |
4828 | Could not bulk insert. Invalid destination table column number for source column %d in format file '%s'. |
4829 | Could not bulk insert. Error reading destination table column name for source column %d in format file '%s'. |
4830 | Bulk Insert: DataFileType was incorrectly specified as char. DataFileType will be assumed to be widechar because the data file has a Unicode signature. |
4831 | Bulk Insert: DataFileType was incorrectly specified as widechar. DataFileType will be assumed to be char because the data file does not have a Unicode signature. |
4832 | Bulk Insert: Unexpected end-of-file (EOF) encountered in data file. |
4833 | Bulk Insert: Version mismatch between the provider dynamic link library and the server executable. |
4834 | You do not have permission to use the BULK INSERT statement. |
4835 | Bulk copying into a table with computed columns is not supported for downlevel clients. |
4837 | Error: Cannot bulk copy into a table '%s' enabled for immediate-updating subscriptions |
4838 | The bulk data source does not support the SQLNUMERIC or SQLDECIMAL data types. |
4839 | Cannot perform bulk insert. Invalid collation name for source column %d in format file '%s'. |
4840 | The bulk data source provider string has an invalid %ls property value %ls. |
4841 | The data source name is not a simple object name. |
4842 | The required FormatFile property is missing from the provider string of the server. |
4843 | The bulk data source provider string has a syntax error ('%lc') near character position %d. |
4844 | The bulk data source provider string has an unsupported property name (%ls). |
4845 | The bulk data source provider string has a syntax error near character position %d. Expected '%lc', but found '%lc'. |
4846 | The bulk data provider failed to allocate memory. |
4847 | Bulk copying into a table with bigint columns is not supported for versions earlier than SQL Server 2000. |
4848 | Bulk copying into a table with sql_variant columns is not supported for versions earlier than SQL Server 2000. |
4849 | Could not import table '%ls'. Error %d. |
4850 | Data import: Table '%ls' is already locked by another user. |
4851 | Data import: Table '%ls' already has data. Skipping to next table. |
4852 | Data import: Table '%ls' does not exist or it is not a user table. |
4853 | %hs |
4854 | %hs |
4860 | Could not bulk insert. File '%ls' does not exist. |
4861 | Could not bulk insert because file '%ls' could not be opened. Operating system error code %ls. |
4862 | Could not bulk insert because file '%ls' could not be read. Operating system error code %ls. |
4863 | Bulk insert data conversion error (truncation) for row %d, column %d (%ls). |
4864 | Bulk insert data conversion error (type mismatch) for row %d, column %d (%ls). |
4865 | Could not bulk insert because the maximum number of errors (%d) was exceeded. |
4866 | Bulk Insert fails. Column is too long in the data file for row %d, column %d. Make sure the field terminator and row terminator are specified correctly. |
4867 | Bulk insert data conversion error (overflow) for row %d, column %d (%ls). |
4868 | Bulk Insert fails. Codepage '%d' is not installed. Install the codepage and run the command again. |
4869 | Bulk Insert failed. Unexpected NULL value in data file row %d, column %d. Destination column (%ls) is defined NOT NULL. |
4880 | Could not bulk insert. When using the FIRSTROW and LASTROW parameters, the value for FIRSTROW cannot be greater than the value for LASTROW. |
4881 | Note: Bulk Insert through a view may result in base table default values being ignored for NULL columns in the data file. |
4882 | Could not bulk insert. Prefix length, field length, or terminator required for source column %d in format file '%s'. |
TSQL Error Codes - 4900 to 4999
Error Code | Description |
---|---|
4901 | ALTER TABLE only allows columns to be added that can contain nulls or have a DEFAULT definition specified. Column '%.*ls' cannot be added to table '%.*ls' because it does not allow nulls and does not specify a DEFAULT definition. |
4902 | Cannot alter table '%.*ls' because this table does not exist in database '%.*ls'. |
4909 | Cannot alter '%.*ls' because it is not a table. |
4910 | Only the owner or members of the sysadmin role can alter table '%.*ls'. |
4916 | Could not enable or disable the constraint. See previous errors. |
4917 | Constraint '%.*ls' does not exist. |
4920 | ALTER TABLE failed because trigger '%.*ls' on table '%.*ls' does not exist. |
4921 | ALTER TABLE failed because trigger '%.*ls' does not belong to table '%.*ls'. |
4922 | %ls %.*ls failed because one or more objects access this column. |
4923 | ALTER TABLE DROP COLUMN failed because '%.*ls' is the only data column in table '%.*ls'. A table must have at least one data column. |
4924 | %ls failed because column '%.*ls' does not exist in table '%.*ls'. |
4925 | ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%.*ls' with ROWGUIDCOL property. |
4926 | ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%.*ls' with ROWGUIDCOL property. |
4927 | Cannot alter column '%.*ls' to be data type %.*ls. |
4928 | Cannot alter column '%.*ls' because it is '%ls'. |
4929 | Cannot alter the %S_MSG '%.*ls' because it is being published for replication. |
4930 | Warning: Columns added to the replicated table %S_MSG '%.*ls' will be ignored by existing articles. |
4931 | Cannot add columns to %S_MSG '%.*ls' because it is being published for merge replication. |
4932 | ALTER TABLE DROP COLUMN failed because '%.*ls' is currently replicated. |
TSQL Error Codes - 5000 to 5099
Error Code | Description |
---|---|
5001 | User must be in the master database. |
5002 | Database '%.*ls' does not exist. Check sysdatabases. |
5004 | To use ALTER DATABASE, the database must be in a writable state in which a checkpoint can be executed. |
5005 | Extending database by %.2f MB on disk '%.*ls'. |
5006 | Could not get exclusive use of %S_MSG '%.*ls' to perform the requested operation. |
5008 | This ALTER DATABASE statement is not supported. |
5009 | ALTER DATABASE failed. Some disk names listed in the statement were not found. Check that the names exist and are spelled correctly before rerunning the statement. |
5010 | Log file name cannot be generated from a raw device. The log file name and path must be specified. |
5011 | User does not have permission to alter database '%.*ls'. |
5012 | The name of the primary filegroup cannot be changed. |
5013 | The master and model databases cannot have files added to them. ALTER DATABASE was aborted. |
5014 | The %S_MSG '%.*ls' does not exist in database '%.*ls'. |
5015 | ALTER DATABASE failed. The total size specified must be 1 MB or greater. |
5016 | System databases master, model, and tempdb cannot have their names changed. |
5017 | ALTER DATABASE failed. Database '%.*ls' was not created with 'FOR LOAD' option. |
5018 | File '%.*ls' modified in sysaltfiles. Delete old file after restarting SQL Server. |
5019 | Cannot find entry in sysaltfiles for file '%.*ls'. |
5020 | The primary data or log file cannot be removed from a database. |
5021 | The %S_MSG name '%.*ls' has been set. |
5022 | Log file '%ls' for this database is already active. |
5023 | Database must be put in bypass recovery mode to rebuild the log. |
5024 | No entry found for the primary log file in sysfiles1. Could not rebuild the log. |
5025 | The file '%ls' already exists. It should be renamed or deleted so that a new log file can be created. |
5026 | Could not create a new log file with file '%.*ls'. See previous errors. |
5027 | System databases master, model, and tempdb cannot have their logs rebuilt. |
5028 | The system could not activate enough of the database to rebuild the log. |
5029 | Warning: The log for database '%.*ls' has been rebuilt. Transactional consistency has been lost. DBCC CHECKDB should be run to validate physical consistency. Database options will have to be reset, and extra log files may need to be deleted. |
5030 | The database could not be exclusively locked to perform the operation. |
5031 | Cannot remove the file '%.*ls' because it is the only file in the DEFAULT filegroup. |
5032 | The file cannot be shrunk below page %ud until the log is backed up because it contains bulk logged pages. |
5035 | Filegroup '%.*ls' already exists in this database. |
5036 | MODIFY FILE failed. Specify logical name. |
5037 | MODIFY FILE failed. Do not specify physical name. |
5038 | MODIFY FILE failed for file "%.*ls". At least one property per file must be specified. |
5039 | MODIFY FILE failed. Specified size is less than current size. |
5040 | MODIFY FILE failed. Size is greater than MAXSIZE. |
5041 | MODIFY FILE failed. File '%.*ls' does not exist. |
5042 | The %S_MSG '%.*ls' cannot be removed because it is not empty. |
5043 | The %S_MSG '%.*ls' cannot be found in %ls. |
5044 | The %S_MSG '%.*ls' has been removed. |
5045 | The %S_MSG already has the '%ls' property set. |
5046 | The %S_MSG property '%ls' has been set. |
5047 | Cannot change the READONLY property of the PRIMARY filegroup. |
5048 | Cannot add, remove, or modify files in filegroup '%.*ls'. The filegroup is read-only. |
5049 | Cannot extend file '%ls' using this syntax as it was not created with DISK INIT. Use ALTER DATABASE MODIFY FILE. |
5050 | Cannot change the properties of empty filegroup '%.*ls'. The filegroup must contain at least one file. |
5051 | Cannot have a filegroup with the name 'DEFAULT'. |
5053 | The maximum of %ld filegroups per database has been exceeded. |
5054 | Could not cleanup worktable IAM chains to allow shrink or remove file operation. Please try again when tempdb is idle. |
5055 | Cannot add, remove, or modify file '%.*ls'. The file is read-only. |
5056 | Cannot add, remove, or modify a file in filegroup '%.*ls' because the filegroup is offline. |
5057 | Cannot add, remove, or modify file '%.*ls' because it is offline. |
5058 | Option '%.*ls' cannot be set in database '%.*ls'. |
5059 | Database '%.*ls' is in transition. Try the ALTER DATABASE statement later. |
5060 | Nonqualified transactions are being rolled back. Estimated rollback completion: %d%%. |
5061 | ALTER DATABASE failed because a lock could not be placed on database '%.*ls'. Try again later. |
5062 | Option '%.*ls' cannot be set at the same time as another option setting. |
5063 | Database '%.*ls' is in warm standby. A warm-standby database is read-only. |
5064 | Changes to the state or options of database '%.*ls' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it. |
5065 | Database '%.*ls' cannot be opened. |
5066 | Database options single user and dbo use only cannot be set at the same time. |
5068 | Failed to restart the current database. The current database is switched to master. |
5069 | ALTER DATABASE statement failed. |
5070 | Database state cannot be changed while other users are using the database '%.*ls' |
5072 | ALTER DATABASE failed. The default collation of database '%.*ls' cannot be set to %.*ls. |
5073 | Cannot alter collation for database '%ls' because it is READONLY, OFFLINE, or marked SUSPECT. |
5074 | The %S_MSG '%.*ls' is dependent on %S_MSG '%.*ls'. |
5075 | The %S_MSG '%.*ls' is dependent on %S_MSG. |
5076 | Warning: Changing default collation for database '%.*ls', which is used in replication. It is recommend that all replication database have the same default collation. |
TSQL Error Codes - 5100 to 5199
Error Code | Description |
---|---|
5101 | You must supply parameters for the DISK %hs statement. Usage: %hs. |
5102 | No such statement DISK %.*ls. |
5103 | MAXSIZE cannot be less than SIZE for file '%ls'. |
5104 | File '%.*ls' already used. |
5105 | Device activation error. The physical file name '%.*ls' may be incorrect. |
5106 | Parameter '%hs' requires value of data type '%hs'. |
5107 | Value is wrong data type for parameter '%hs' (requires data type '%hs'). |
5108 | Log file '%.*ls' does not match the primary file. It may be from a different database or the log may have been rebuilt previously. |
5109 | No such parameter '%.*ls'. |
5110 | File '%.*ls' is on a network device not supported for database files. |
5116 | You do not have permission to run DISK statements. |
5117 | Could not run DISK statement. You must be in the master database to run this statement. |
5122 | Each disk file size must be greater than or equal to 1 MB. |
5123 | CREATE FILE encountered operating system error %ls while attempting to open or create the physical file '%.*ls'. |
5126 | The logical device '%.*ls' does not exist in sysdevices. |
5146 | The %hs of %d is out of range. It must be between %d and %d. |
5148 | Could not set the file size to the desired amount. The operating system file size limit may have been reached. |
5149 | MODIFY FILE encountered operating system error %ls while attempting to expand the physical file. |
5150 | The size of a single log file must not be greater than 2 TB. |
5151 | The %hs statement is obsolete and no longer supported. |
5157 | I/O error encountered in the writelog system function during backout. |
5158 | Warning: Media in device '%.*ls' may have been changed. |
5159 | Operating system error %.*ls on device '%.*ls' during %ls. |
5160 | Cannot take '%.*ls' offline because the database is in use. |
5162 | Cannot find '%.*ls' in sysdatabases. |
5163 | Cannot open '%.*ls' to take offline. |
5164 | Usage: DBCC DBCONTROL(dbname,ONLINE|OFFLINE) |
5165 | Cannot explicitly open or close master database. |
5167 | Database '%.*ls' is already offline. |
5168 | File '%.*ls' is on a network drive, which is not allowed. |
5169 | FILEGROWTH cannot be greater than MAXSIZE for file '%.*ls'. |
5170 | Cannot create file '%ls' because it already exists. |
5171 | %.*ls is not a primary database file. |
5172 | The header for file '%ls' is not a valid database file header. The %ls property is incorrect. |
5173 | Cannot associate files with different databases. |
5174 | Each file size must be greater than or equal to 512 KB. |
5175 | The file '%.*ls' has been expanded to prevent recovery from failing. Contact the system administrator for further assistance. |
5176 | The file '%.*ls' has been expanded beyond its maximum size to prevent recovery from failing. Contact the system administrator for further assistance. |
5177 | Encountered an unexpected error while checking the sector size for file '%.*ls'. Check the SQL Server error log for more information. |
5178 | Cannot use file '%.*ls' because it was originally formatted with sector size %d and is now on a device with sector size %d. |
5179 | Cannot use file '%.*ls', which is on a device with sector size %d. SQL Server supports a maximum sector size of 4096 bytes. |
5180 | Could not open FCB for invalid file ID %d in database '%.*ls'. |
5181 | Could not restart database '%.*ls'. Reverting back to old status. |
5182 | New log file '%.*ls' was created. |
5183 | File '%ls' cannot be created. Use WITH MOVE to specify a usable physical file name. |
5184 | Cannot use file '%.*ls' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. |
TSQL Error Codes - 5700 to 5799
Error Code | Description |
---|---|
5701 | Changed database context to '%.*ls'. |
5702 | SQL Server is terminating this process. |
5703 | Changed language setting to %.*ls. |
TSQL Error Codes - 5800 to 5899
Error Code | Description |
---|---|
5803 | Unknown config number (%d) in sysconfigures. |
5804 | Character set, sort order, or collation cannot be changed because at least one database is not writable. |
5805 | Too few locks specified. Minimum %d. |
5807 | Recovery intervals above %d minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration. |
5808 | Ad hoc updates to system catalogs not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration. |
5809 | Average time slices above %d milliseconds not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration. |
5810 | Valid values for the fill factor are 0 to 100. |
5812 | You do not have permission to run the RECONFIGURE statement. |
5823 | Cannot reconfigure SQL Server to use sort order ID %d, because the row for that sort order does not exist in syscharsets. |
5828 | User connections are limited to %d. |
5829 | The specified user options value is invalid. |
5830 | The default collation for SQL Server has been reconfigured. Restart SQL Server to rebuild the table indexes on columns of character data types. |
5831 | Minimum server memory value (%d) must be less than or equal to the maximum value (%d). |
TSQL Error Codes - 5900 to 5999
Error Code | Description |
---|---|
5904 | Background checkpoint process suspended until locks are available. |
TSQL Error Codes - 6000 to 6099
Error Code | Description |
---|---|
6001 | SHUTDOWN is waiting for %d process(es) to complete. |
6002 | SHUTDOWN is in progress. Log off. |
6004 | User does not have permission to perform this action. |
6005 | SHUTDOWN is in progress. |
6006 | Server shut down by request. |
6007 | The SHUTDOWN statement cannot be executed within a transaction or by a stored procedure. |
TSQL Error Codes - 6100 to 6199
Error Code | Description |
---|---|
6101 | Process ID %d is not a valid process ID. Choose a number between 1 and %d. |
6102 | User does not have permission to use the KILL statement. |
6103 | Could not do cleanup for the killed process. Received message %d. |
6104 | Cannot use KILL to kill your own process. |
6106 | Process ID %d is not an active process ID. |
6107 | Only user processes can be killed. |
6108 | KILL SPID WITH COMMIT/ABORT is not supported by Microsoft SQL Server 2000. Use Microsoft Distributed Transaction Coordinator to resolve distributed transactions. |
6109 | SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%. Estimated time remaining: %d seconds. |
6110 | The distributed transaction with UOW %s does not exist. |
6111 | Another user has decided a different outcome for the distributed transaction associated with UOW %s. |
6112 | Distributed transaction with UOW %s is in prepared state. Only Microsoft Distributed Transaction Coordinator can resolve this transaction. KILL command failed. |
6113 | The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill the transaction instead. |
6114 | Distributed transaction with UOW %s is being used by another user. KILL command failed. |
6115 | KILL command cannot be used inside user transactions. |
6116 | KILL command failed. |
6117 | There is a connection associated with the distributed transaction with UOW %s. First, kill the connection using KILL SPID syntax. |
6118 | The distributed transaction associated with UOW %s is not in PREPARED state. Use KILL UOW to kill the transaction instead. |
6119 | Distributed transaction with UOW %s is rolling back: estimated rollback completion: %d%%, estimated time left %d seconds. |
6120 | Status report cannot be obtained. Rollback operation for Process ID %d is not in progress. |
6121 | Status report cannot be obtained. Rollback operation for UOW %s is not in progress. |
TSQL Error Codes - 6400 to 6499
Error Code | Description |
---|---|
6401 | Cannot roll back %.*ls. No transaction or savepoint of that name was found. |
TSQL Error Codes - 6600 to 6799
Error Code | Description |
---|---|
6600 | XML error: %.*ls |
6601 | XML parser returned the error code %d from line number %d, source '%.*ls'. |
6602 | The error description is '%.*ls'. |
6603 | XML parsing error: %.*ls |
6604 | XML stored procedures are not supported in fibers mode. |
6605 | %.*ls: Failed to obtain an IPersistStream interface on the XML text. |
6606 | %.*ls: Failed to save the XML text stream. The server resources may be too low. |
6607 | %.*ls: The value supplied for parameter number %d is invalid. |
6608 | Failed to instantiate class '%ls'. Make sure Msxml2.dll exists in the SQL Server installation. |
6609 | Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, nvarchar, text, and ntext. |
6610 | Failed to load Msxml2.dll. |
6612 | Invalid data type for the column indicated by the parameter '%ls'. Valid data types are int, bigint, smallint, and tinyint. |
6613 | Specified value '%ls' already exists. |
6614 | Value specified for column '%ls' is the same for column '%ls'. An element cannot be its own parent. |
6615 | Invalid data type is specified for column '%ls'. Valid data types are int, bigint, smallint, and tinyint. |
6616 | Parameter '%ls' is required when the parent of the element to be added is missing and must be inserted. |
6617 | The specified edge table has an invalid format. Column '%ls' is missing or has an invalid data type. |
6618 | Column '%ls' in the specified edge table has an invalid or null value. |
6619 | XML node of type %d named '%ls' cannot be created . |
6620 | XML attribute or element cannot be created for column '%ls'. |
6621 | XML encoding or decoding error occurred with object name '%.*ls'. |
6622 | Invalid data type for column '%ls'. Data type cannot be text, ntext, image, or binary. |
6623 | Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar. |
6624 | XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents. |
TSQL Error Codes - 6800 to 6899
Error Code | Description |
---|---|
6800 | FOR XML AUTO requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name. |
6801 | FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column. |
6802 | FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integer. |
6803 | FOR XML EXPLICIT requires the first column to hold positive integers that represent XML tag IDs. |
6804 | FOR XML EXPLICIT requires the second column to hold NULL or nonnegative integers that represent XML parent tag IDs. |
6805 | FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed. |
6806 | Undeclared tag ID %d is used in a FOR XML EXPLICIT query. |
6807 | Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query. |
6808 | XML tag ID %d could not be added. The server memory resources may be low. |
6809 | Unnamed column or table names cannot be used as XML identifiers. Name unnamed columns using AS in the SELECT statement. |
6810 | Column name '%.*ls' is repeated. The same attribute cannot be generated more than once on the same XML tag. |
6811 | FOR XML is incompatible with COMPUTE expressions. Remove the COMPUTE expression. |
6812 | XML tag ID %d that was originally declared as '%.*ls' is being redeclared as '%.*ls'. |
6813 | FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'. |
6814 | In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'. |
6815 | In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'. |
6816 | In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'. |
6817 | FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'. |
6818 | In the FOR XML EXPLICIT clause, CDATA attributes must be unnamed in '%.*ls'. |
6819 | The FOR XML clause is not allowed in a %ls statement. |
6820 | FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'. |
6821 | GROUP BY and aggregate functions are currently not supported with FOR XML AUTO. |
6824 | In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid. |
6825 | ELEMENTS mode requires FOR XML AUTO. |
6826 | Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after the element to which they belong. |
6827 | FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted. |
6828 | XMLTEXT column '%.*ls' must be of a string data type. |
6829 | FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%.*ls'. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax. |
6830 | FOR XML AUTO could not find the table owning the following column '%.*ls' to create a URL address for it. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax. |
6831 | FOR XML AUTO requires primary keys to create references for '%.*ls'. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form if no primary keys exist. |
6832 | FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary. |
6833 | Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requires parent tags to be opened first. Check the ordering of the result set. |
6834 | XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag and its attributes. |
6835 | FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once. |
6836 | FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls' to precede element-centric IDREFS/NMTOKEN fields. |
6837 | The XMLTEXT document attribute that starts with '%.*ls' is too long. Maximum length is %d. |
6838 | Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either specify ELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive. |
6839 | FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that has IDREFS or NMTOKENS fields. |
6840 | XMLDATA does not support namespace elements or attributes such as '%.*ls'. Run the SELECT FOR XML statement without XMLDATA or remove the namespace prefix declaration. |
TSQL Error Codes - 7000 to 7099
Error Code | Description |
---|---|
7000 | OPENXML document handle parameter must be of data type int. |
7001 | OPENXML flags parameter must be of data type int. |
7002 | OPENXML XPath must be of a string data type, such as nvarchar. |
7003 | Only one OPENXML column can be of type %ls. |
7004 | OPENXML does not support retrieving schema from remote tables, as in '%.*ls'. |
7005 | OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument. |
7006 | OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement. |
7007 | OPENXML encountered unknown metaproperty '%.*ls'. |
7008 | The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag. |
7009 | OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument. |
TSQL Error Codes - 7100 to 7199
Error Code | Description |
---|---|
7101 | You cannot use a text pointer for a table with option 'text in row' set to ON. |
7102 | SQL Server Internal Error. Text manager cannot continue with current statement. |
7103 | You cannot set option 'text in row' for table %s. |
7104 | Offset or size type is invalid. Must be int or smallint data type. |
7105 | Page %S_PGID, slot %d for text, ntext, or image node does not exist. |
7106 | You cannot update a blob with a read-only text pointer |
7107 | You can have only 1,024 in-row text pointers in one transaction |
7116 | Offset %d is not in the range of available text, ntext, or image data. |
7122 | Invalid text, ntext, or image pointer type. Must be binary(16). |
7123 | Invalid text, ntext, or image pointer value %hs. |
7124 | The offset and length specified in the READTEXT statement is greater than the actual data length of %ld. |
7125 | The text, ntext, or image pointer value conflicts with the column name specified. |
7126 | The text, ntext, or image pointer value references a data page with an invalid text, ntext, or image status. |
7127 | The text, ntext, or image pointer value references a data page with an invalid timestamp. |
7128 | The text, ntext, or image pointer value references a data page that is no longer allocated. |
7130 | %ls WITH NO LOG is not valid at this time. Use sp_dboption to set the 'select into/bulkcopy' option on for database '%.*ls'. |
7133 | NULL textptr (text, ntext, or image pointer) passed to %ls function. |
7135 | Deletion length %ld is not in the range of available text, ntext, or image data. |
7137 | %s is not allowed because the column is being processed by a concurrent snapshot and is being replicated to a non-SQL Server Subscriber or Published in a publication allowing Data Transformation Services (DTS). |
7138 | The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS). |
7139 | Length of text, ntext, or image data (%ld) to be replicated exceeds configured maximum %ld. |
7141 | Must create orphaned text inside a user transaction. |
7142 | Must drop orphaned text before committing the transaction. |
7143 | Invalid locator de-referenced. |
TSQL Error Codes - 7200 to 7299
Error Code | Description |
---|---|
7201 | Could not execute procedure on remote server '%.*ls' because SQL Server is not configured for remote access. Ask your system administrator to reconfigure SQL Server to allow remote access. |
7202 | Could not find server '%.*ls' in sysservers. Execute sp_addlinkedserver to add the server to sysservers. |
7212 | Could not execute procedure '%.*ls' on remote server '%.*ls'. |
7213 | Could not set up parameter for remote server '%.*ls'. |
7214 | Remote procedure time out of %d seconds exceeded. Remote procedure '%.*ls' is canceled. |
7221 | Could not relay results of procedure '%.*ls' from remote server '%.*ls'. |
7300 | OLE DB error trace [%ls]. |
TSQL Error Codes - 7300 to 7399
Error Code | Description |
---|---|
7301 | Could not obtain a required interface from OLE DB provider '%ls'. |
7302 | Could not create an instance of OLE DB provider '%ls'. |
7303 | Could not initialize data source object of OLE DB provider '%ls'. %ls |
7304 | Could not create a new session on OLE DB provider '%ls'. |
7305 | Could not create a statement object using OLE DB provider '%ls'. |
7306 | Could not open table '%ls' from OLE DB provider '%ls'. %ls |
7307 | Could not obtain the data source of a session from OLE DB provider '%ls'. This action must be supported by the provider. |
7310 | Could not obtain the schema options for OLE DB provider '%ls'. The provider supports the interface, but returns a failure code when it is used. |
7311 | Could not obtain the schema rowset for OLE DB provider '%ls'. The provider supports the interface, but returns a failure code when it is used. |
7312 | Invalid use of schema and/or catalog for OLE DB provider '%ls'. A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog and/or schema. |
7313 | Invalid schema or catalog specified for provider '%ls'. |
7314 | OLE DB provider '%ls' does not contain table '%ls'. The table either does not exist or the current user does not have permissions on that table. |
7315 | OLE DB provider '%ls' contains multiple tables that match the name '%ls'. |
7316 | Could not use qualified table names (schema or catalog) with OLE DB provider '%ls' because it does not implement required functionality. |
7317 | OLE DB provider '%ls' returned an invalid schema definition. |
7318 | OLE DB provider '%ls' returned an invalid column definition. |
7319 | OLE DB provider '%ls' returned a '%ls' index '%ls' with incorrect bookmark ordinal %d. |
7320 | Could not execute query against OLE DB provider '%ls'. %ls |
7321 | An error occurred while preparing a query for execution against OLE DB provider '%ls'. %ls |
7322 | A failure occurred while giving parameter information to OLE DB provider '%ls'. %ls |
7323 | An error occurred while submitting the query text to OLE DB provider '%ls'. %ls |
7330 | Could not fetch a row from OLE DB provider '%ls'. %ls |
7331 | Rows from OLE DB provider '%ls' cannot be released. %ls |
7332 | Could not rescan the result set from OLE DB provider '%ls'. %ls |
7333 | Could not fetch a row using a bookmark from OLE DB provider '%ls'. %ls |
7340 | Could not create a column accessor for OLE DB provider '%ls'. %ls |
7341 | Could not get the current row value of column '%ls.%ls' from the OLE DB provider '%ls'. %ls |
7342 | Unexpected NULL value returned for column '%ls.%ls' from the OLE DB provider '%ls'. This column cannot be NULL. |
7343 | OLE DB provider '%ls' could not %ls table '%ls'. %ls |
7344 | OLE DB provider '%ls' could not %ls table '%ls' because of column '%ls'. %ls |
7345 | OLE DB provider '%ls' could not delete from table '%ls'. %ls |
7346 | Could not get the data of the row from the OLE DB provider '%ls'. %ls |
7347 | OLE DB provider '%ls' returned an unexpected data length for the fixed-length column '%ls.%ls'. The expected data length is %ls, while the returned data length is %ls. |
7348 | OLE DB provider '%ls' could not set range for table '%ls'.%ls |
7349 | OLE DB provider '%ls' could not set range for table '%ls' because of column '%ls'.%ls |
7350 | Could not get the column information from the OLE DB provider '%ls'. |
7351 | OLE DB provider '%ls' could not map ordinals for one or more columns of object '%ls'. |
7352 | OLE DB provider '%ls' supplied inconsistent metadata. The object '%ls' was missing expected column '%ls'. |
7353 | OLE DB provider '%ls' supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time. |
7354 | OLE DB provider '%ls' supplied invalid metadata for column '%ls'. %ls |
7355 | OLE DB provider '%ls' supplied inconsistent metadata for a column. The name was changed at execution time. |
7356 | OLE DB provider '%ls' supplied inconsistent metadata for a column. Metadata information was changed at execution time. |
7357 | Could not process object '%ls'. The OLE DB provider '%ls' indicates that the object has no columns. |
7358 | Could not execute query. The OLE DB provider '%ls' did not provide an appropriate interface to access the text, ntext, or image column '%ls.%ls'. |
7359 | The OLE DB provider '%ls' reported a schema version for table '%ls' that changed between compilation and execution. |
7360 | Could not get the length of a storage object from the OLE DB provider '%ls' for table '%ls', column '%ls'. |
7361 | Could not read a storage object from the OLE DB provider '%ls', for table '%ls', column '%ls'. |
7362 | The OLE DB provider '%ls' reported different meta data at for table '%ls' column '%ls'. |
7365 | Could not obtain optional metadata columns of columns rowset from the OLE DB provider '%ls'. |
7366 | Could not obtain columns rowset from OLE DB provider '%ls'. The provider supports the interface, but returns a failure code when used. |
7367 | The OLE DB provider '%ls' supports column-level collation, but failed to provide metadata column '%ls' at . |
7368 | The OLE DB provider '%ls' supports column-level collation, but failed to provide collation data for column '%ls'. |
7369 | The OLE DB provider '%ls' provided invalid collation. %ls. |
7370 | One or more properties could not be set on the query for OLE DB provider '%ls'. %ls |
7371 | One or more properties could not be set on the table for OLE DB provider '%ls'. |
7372 | Cannot get properties from OLE DB provider '%ls'. |
7373 | Could not set the initialization properties for the OLE DB provider '%ls'. |
7374 | Could not set the session properties for the OLE DB provider '%ls'. |
7375 | Could not open index '%ls' on table '%ls' from OLE DB provider '%ls'. %ls |
7376 | Could not enforce the remote join hint for this query. |
7377 | Cannot specify an index or locking hint for a remote data source. |
7378 | The update/delete operation requires a unique key or a clustered index on the remote table. |
7379 | OLE DB provider '%ls' returned an unexpected '%ls' for the decimal/numeric column '%ls.%ls'. The expected data length is '%ls', while the returned data length is '%ls'. |
7390 | The requested operation could not be performed because the OLE DB provider '%ls' does not support the required transaction interface. |
7391 | The operation could not be performed because the OLE DB provider '%ls' was unable to begin a distributed transaction. |
7392 | Could not start a transaction for OLE DB provider '%ls'. |
7393 | OLE DB provider '%ls' reported an error aborting the current transaction. |
7394 | OLE DB provider '%ls' reported an error committing the current transaction. |
7395 | Unable to start a nested transaction for OLE DB provider '%ls'. A nested transaction was required because the XACT_ABORT option was set to OFF. |
7399 | OLE DB provider '%ls' reported an error. %ls |
TSQL Error Codes - 7400 to 7499
Error Code | Description |
---|---|
7401 | Cannot create OLE DB provider enumeration object installed with SQL Server. Verify installation. |
7403 | Could not locate registry entry for OLE DB provider '%ls'. |
7404 | The server could not load DCOM. |
7405 | Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query. |
7410 | Remote access not allowed for Windows NT user activated by SETUSER. |
7411 | Server '%.*ls' is not configured for %ls. |
7413 | Could not perform a Windows NT authenticated login because delegation is not available. |
7414 | Invalid number of parameters. Rowset '%ls' expects %d parameter(s). |
7415 | Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server. |
7416 | Access to the remote server is denied because no login-mapping exists. |
7417 | GROUP BY ALL is not supported in queries that access remote tables if there is also a WHERE clause in the query. |
7418 | Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider. |
7419 | Lazy schema validation error. Linked server schema version has changed. Re-run the query. |
TSQL Error Codes - 7600 to 7699
Error Code | Description |
---|---|
7601 | Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because it is not full-text indexed. |
7602 | The Full-Text Service (Microsoft Search) is not available. The system administrator must start this service. |
7603 | Syntax error in search condition, or empty or null search condition '%ls'. |
7604 | Full-text operation failed due to a time out. |
7605 | Full-text catalog '%ls' has been lost. Use sp_fulltext_catalog to rebuild and to repopulate this full-text catalog. |
7606 | Could not find full-text index for database ID %d, table ID %d. Use sp_fulltext_table to deactivate then activate this index. |
7607 | Search on full-text catalog '%ls' for database ID %d, table ID %d with search condition '%ls' failed with unknown result (%x). |
7608 | An unknown full-text failure (%x) occurred in function %hs on full-text catalog '%ls'. |
7609 | Full-Text Search is not installed, or a full-text component cannot be loaded. |
7610 | Access is denied to '%ls', or the path is invalid. Full-text search was not installed properly. |
7611 | Warning: Request to start a population in full-text catalog '%ls' ignored because a population is currently active for this full-text catalog. |
7612 | %d is not a valid value for full-text system resource usage. |
7613 | Cannot drop index '%.*ls' because it enforces the full-text key for table '%.*ls'. |
7614 | Cannot alter or drop column '%.*ls' because it is enabled for Full-Text Search. |
7615 | A CONTAINS or FREETEXT predicate can only operate on one table. Qualify the use of * with a table name. |
7616 | Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. |
7617 | Query does not reference the full-text indexed table. |
7618 | %d is not a valid value for a full-text connection time out. |
7620 | Conversion to data type %ls failed for full-text search key value 0x%ls. |
7621 | Invalid use of full-text predicate in the HAVING clause. |
7622 | Full-text catalog '%ls' lacks sufficient disk space to complete this operation. |
7623 | Full-text query failed because full-text catalog '%ls' is not yet ready for queries. |
7624 | Full-text catalog '%ls' is in a unusable state. Drop and re-create this full-text catalog. |
7625 | Full-text table has more than one LCID among its full-text indexed columns. |
7626 | The top_n_by_rank argument ('%d') must be greater than zero. |
7627 | Full-text catalog in directory '%ls' for clustered server cannot be created. Only directories on a disk in the cluster group of the server can be used. |
7628 | Cannot copy Schema.txt to '%.*ls' because access is denied or the path is invalid. Full-text search was not installed properly. |
7629 | Cannot open or query registry key '%.*ls'. |
7630 | Syntax error occurred near '%.*ls' in search condition '%.*ls'. |
7631 | Syntax error occurred near '%.*ls'. Expected '%.*ls' in search condition '%.*ls'. |
7632 | The value of the Weight argument must be between 0.0 and 1.0. |
7633 | The syntax <content search condition> OR NOT <content boolean term> is not allowed. |
7634 | Stack overflow occurred in parsing search condition '%.*ls'. |
7635 | The Microsoft Search service cannot be administered under the present user account |
7636 | Warning: Request to start a full-text index population on table '%ls' is ignored because a population is currently active for this table. |
7637 | Value %d is not valid for full-text data time-out. |
7638 | Warning: Request to stop change tracking has deleted all changes tracked on table '%ls'. |
7639 | Cannot use a full-text predicate on %S_MSG '%.*ls' because it is not located on the local server. |
7640 | Warning: Request to stop tracking changes on table '%ls' will not stop population currently in progress on the table. |
7641 | Full-Text catalog '%ls' does not exist. |
7642 | A full-text catalog named '%ls' already exists in this database. |
TSQL Error Codes - 7900 to 7999
Error Code | Description |
---|---|
7905 | The object specified is neither a table nor a constraint |
7908 | The table '%.*ls' was created with the NO_LOG option. |
7910 | Repair: Page %S_PGID has been allocated to object ID %d, index ID %d. |
7911 | Repair: Page %S_PGID has been deallocated from object ID %d, index ID %d. |
7912 | Repair: Extent %S_PGID has been allocated to object ID %d, index ID %d. |
7913 | Repair: Extent %S_PGID has been deallocated from object ID %d, index ID %d. |
7914 | Repair: %ls page at %S_PGID has been rebuilt. |
7915 | Repair: IAM chain for object ID %d, index ID %d, has been truncated before page %S_PGID and will be rebuilt. |
7916 | Repair: Deleted record for object ID %d, index ID %d, on page %S_PGID, slot %d. Indexes will be rebuilt. |
7917 | Repair: Converted forwarded record for object ID %d, index ID %d, at page %S_PGID, slot %d to a data row. |
7918 | Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d. |
7919 | Repair statement not processed. Database needs to be in single user mode. |
7920 | Processed %ld entries in sysindexes for database ID %d. |
7922 | *************************************************************** |
7923 | Table %.*ls Object ID %ld. |
7924 | Index ID %ld. FirstIAM %S_PGID. Root %S_PGID. Dpages %ld. |
7925 | Index ID %d. %ld pages used in %ld dedicated extents. |
7927 | Total number of extents is %ld. |
7932 | The indexes for '%.*ls' are already correct. They will not be rebuilt. |
7933 | One or more indexes contain errors. They will be rebuilt. |
7934 | The table '%.*ls' has no indexes. |
7935 | REINDEX received an exception. Statement terminated. |
7937 | The data in table '%.*ls' is possibly inconsistent. REINDEX terminated. Run DBCC CHECKTABLE and report errors to your system administrator. |
7939 | Cannot detach database '%.*ls' because it does not exist. |
7940 | System databases master, model, msdb, and tempdb cannot be detached. |
7941 | Trace option(s) not enabled for this connection. Use 'DBCC TRACEON()'. |
7942 | DBCC %ls scanning '%.*ls' table... |
7943 | Table: '%.*ls' (%d); index ID: %d, database ID: %d |
7944 | %ls level scan performed. |
7945 | - Pages Scanned................................: %lu |
7946 | - Extents Scanned..............................: %lu |
7947 | - Extent Switches..............................: %lu |
7948 | - Avg. Pages per Extent........................: %3.1f |
7949 | - Scan Density [Best Count:Actual Count].......: %4.2f%ls [%lu:%lu] |
7950 | - Logical Scan Fragmentation ..................: %4.2f%ls |
7951 | - Physical Scan Fragmentation .................: %4.2f%ls |
7952 | - Extent Scan Fragmentation ...................: %4.2f%ls |
7953 | - Avg. Bytes Free per Page.....................: %3.1f |
7954 | - Avg. Page Density (full).....................: %4.2f%ls |
7955 | Invalid SPID %d specified. |
7956 | Permission to execute DBCC %ls denied. |
7957 | Cannot display the specified SPID's buffer; in transition. |
7958 | The specified SPID does not process input/output data streams. |
7959 | The DBCC statement is not supported in this release. |
7961 | Object ID %d, index ID %d, page ID %S_PGID, row ID %d. Column '%.*ls' is a var column with a NULL value and non-zero data length. |
7962 | Upgrade requires SQL Server to be started in single user mode. Restart SQL Server with the -m flag. |
7963 | Upgrade encountered a fatal error. See the SQL Server errorlog for more information. |
7965 | Table error: Could not check object ID %d, index ID %d due to invalid allocation (IAM) page(s). |
7966 | Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped. |
7968 | Transaction information for database '%.*ls'. |
7969 | No active open transactions. |
7970 | %hsOldest active transaction: |
7971 | SPID (server process ID) : %d |
7972 | UID (user ID) : %d |
7974 | Name : %.*ls |
7975 | LSN : (%d:%d:%d) |
7977 | Start time : %.*ls |
7979 | %hsReplicated Transaction Information: |
7980 | Oldest distributed LSN : (%d:%d:%d) |
7982 | Oldest non-distributed LSN : (%d:%d:%d) |
7983 | User '%.*ls' does not have permission to run DBCC %ls for database '%.*ls'. |
7984 | Invalid object name '%.*ls'. |
7985 | The object name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. |
7986 | Warning: Pinning tables should be carefully considered. If a pinned table is larger, or grows larger, than the available data cache, the server may need to be restarted and the table unpinned. |
7991 | System table mismatch: Table '%.*ls', object ID %d has index ID 1 in sysindexes but the status in sysobjects does not have the clustered bit set. The table will be checked as a heap. |
7992 | Cannot shrink 'read only' database '%.*ls'. |
7993 | Cannot shrink file '%d' in database '%.*ls' to %d pages as it only contains %d pages. |
7994 | Object ID %d, index ID %d: FirstIAM field in sysindexes is %S_PGID. FirstIAM for statistics only and dummy index entries should be (0:0). |
7995 | Database '%ls' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further %ls processing. |
7996 | Extended stored procedures can only be created in the master database. |
7997 | '%.*ls' does not contain an identity column. |
7998 | Checking identity information: current identity value '%.*hs', current column value '%.*hs'. |
7999 | Could not find any index named '%.*ls' for table '%.*ls'. |
TSQL Error Codes - 8100 to 8199
Error Code | Description |
---|---|
8101 | An explicit value for the identity column in table '%.*ls' can only be specified when a column list is used and IDENTITY_INSERT is ON. |
8102 | Cannot update identity column '%.*ls'. |
8103 | Table '%.*ls' does not exist or cannot be opened for SET operation. |
8104 | The current user is not the database or object owner of table '%.*ls'. Cannot perform SET operation. |
8105 | '%.*ls' is not a user table. Cannot perform SET operation. |
8106 | Table '%.*ls' does not have the identity property. Cannot perform SET operation. |
8107 | IDENTITY_INSERT is already ON for table '%.*ls.%.*ls.%.*ls'. Cannot perform SET operation for table '%.*ls'. |
8108 | Cannot add identity column, using the SELECT INTO statement, to table '%.*ls', which already has column '%.*ls' that inherits the identity property. |
8109 | Attempting to add multiple identity columns to table '%.*ls' using the SELECT INTO statement. |
8110 | Cannot add multiple PRIMARY KEY constraints to table '%.*ls'. |
8111 | Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'. |
8112 | Cannot add more than one clustered index for constraints on table '%.*ls'. |
8114 | Error converting data type %ls to %ls. |
8115 | Arithmetic overflow error converting %ls to data type %ls. |
8116 | Argument data type %ls is invalid for argument %d of %ls function. |
8117 | Operand data type %ls is invalid for %ls operator. |
8118 | Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause. |
8119 | Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause. |
8120 | Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. |
8121 | Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause. |
8122 | Only the first query in a UNION statement can have a SELECT with an assignment. |
8123 | A correlated expression is invalid because it is not in a GROUP BY clause. |
8124 | Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression. |
8125 | An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated. |
8126 | Column name '%.*ls.%.*ls' is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause. |
8127 | Column name '%.*ls.%.*ls' is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause. |
8128 | Using '%s' version '%s' to execute extended stored procedure '%s'. |
8129 | The new disk size must be greater than %d. Consider using DBCC SHRINKDB. |
8130 | The device is not a database device. Only database devices can be expanded. |
8131 | Extended stored procedure DLL '%s' does not export __GetXpVersion(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Services" in the documentation for more information. |
8132 | Extended stored procedure DLL '%s' reports its version is %d.%d. Server expects version %d.%d. |
8133 | None of the result expressions in a CASE specification can be NULL. |
8134 | Divide by zero error encountered. |
8135 | Table level constraint does not specify column list, table '%.*ls'. |
8136 | Duplicate columns specified in %ls constraint key list, table '%.*ls'. |
8138 | More than 16 columns specified in foreign key column list, table '%.*ls'. |
8139 | Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'. |
8140 | More than one key specified in column level %ls constraint, table '%.*ls'. |
8141 | Column %ls constraint for column '%.*ls' references another column, table '%.*ls'. |
8142 | Subqueries are not supported in %ls constraints, table '%.*ls'. |
8143 | Parameter '%.*ls' was supplied multiple times. |
8144 | Procedure or function %.*ls has too many arguments specified. |
8145 | %.*ls is not a parameter for procedure %.*ls. |
8146 | Procedure %.*ls has no parameters and arguments were supplied. |
8147 | Could not create IDENTITY attribute on nullable column '%.*ls', table '%.*ls'. |
8148 | More than one column %ls constraint specified for column '%.*ls', table '%.*ls'. |
8149 | OLE Automation objects are not supported in fiber mode. |
8150 | Multiple NULL constraints were specified for column '%.*ls', table '%.*ls'. |
8151 | Both a PRIMARY KEY and UNIQUE constraint have been defined for column '%.*ls', table '%.*ls'. Only one is allowed. |
8152 | String or binary data would be truncated. |
8153 | Warning: Null value is eliminated by an aggregate or other SET operation. |
8154 | The table '%.*ls' is ambiguous. |
8155 | No column was specified for column %d of '%.*ls'. |
8156 | The column '%.*ls' was specified multiple times for '%.*ls'. |
8157 | All the queries in a query expression containing a UNION operator must have the same number of expressions in their select lists. |
8158 | '%.*ls' has more columns than were specified in the column list. |
8159 | '%.*ls' has fewer columns than were specified in the column list. |
8160 | A grouping function can only be specified when either CUBE or ROLLUP is specified in the GROUP BY clause. |
8161 | A grouping function argument does not match any of the expressions in the GROUP BY clause. |
8162 | Formal parameter '%.*ls' was defined as OUTPUT but the actual parameter not declared OUTPUT. |
8163 | The text, ntext, or image data type cannot be selected as DISTINCT. |
8164 | An INSERT EXEC statement cannot be nested. |
8165 | Invalid subcommand value %d. Legal range from %d to %d. |
8166 | Constraint name '%.*ls' not permitted. Constraint names cannot begin with a number sign (#). |
8168 | Cannot create two constraints named '%.*ls'. Duplicate constraint names are not allowed. |
8169 | Syntax error converting from a character string to uniqueidentifier. |
8170 | Insufficient result space to convert uniqueidentifier value to char. |
8171 | Hint '%ls' on object '%.*ls' is invalid. |
8175 | Could not find table %.*ls. Will try to resolve this table name later. |
8176 | Resync procedure expects value of key '%.*ls', which was not supplied. |
8177 | Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause. |
8178 | Prepared statement '%.*ls' expects parameter %.*ls, which was not supplied. |
8179 | Could not find prepared statement with handle %d. |
8180 | Statement(s) could not be prepared. |
8181 | Text for '%.*ls' is missing from syscomments. The object must be dropped and re-created before it can be used. |
8183 | Only UNIQUE or PRIMARY KEY constraints are allowed on computed columns. |
8184 | Error expanding '*': all columns incomparable, '*' expanded to zero columns. |
8185 | Error expanding '*': An uncomparable column has been found in an underlying table or view. |
8186 | Function '%.*ls' can be used only on user and system tables. |
8190 | Cannot compile replication filter procedure without defining table being filtered. |
8191 | Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements. |
8192 | Replication filter procedures cannot have parameters. |
8193 | Cannot execute a procedure marked FOR REPLICATION. |
8194 | Cannot execute a USE statement while an application role is active. |
8196 | Duplicate column specified as ROWGUIDCOL. |
8197 | Windows NT user '%.*ls' does not have server access. |
8198 | Could not obtain information about Windows NT group/user '%ls'. |
8199 | In EXECUTE <procname>, procname can only be a literal or variable of type char, varchar, nchar, or nvarchar. |
TSQL Error Codes - 8500 to 8599
Error Code | Description |
---|---|
8501 | MSDTC on server '%.*ls' is unavailable. |
8502 | Unknown MSDTC token '0x%x' received. |
8504 | Invalid transaction import buffer. |
8506 | Invalid transaction state change requested from %hs to %hs. |
8508 | QueryInterface failed for '%hs': %hs. |
8509 | Import of MSDTC transaction failed: %hs. |
8510 | Enlist of MSDTC transaction failed: %hs. |
8511 | Unknown isolation level %d requested from MSDTC. |
8512 | MSDTC Commit acknowledgment failed: %hs. |
8513 | MSDTC Abort acknowledgment failed: %hs. |
8514 | MSDTC PREPARE acknowledgment failed: %hs. |
8515 | MSDTC Global state is invalid. |
8517 | Failed to get MSDTC PREPARE information: %hs. |
8518 | MSDTC BEGIN TRANSACTION failed: %hs. |
8519 | Current MSDTC transaction must be committed by remote client. |
8520 | Commit of internal MSDTC transaction failed: %hs. |
8521 | Invalid awakening state. Slept in %hs; awoke in %hs. |
8522 | Distributed transaction aborted by MSDTC. |
8523 | PREPARE TRAN statement not allowed on MSDTC transaction. |
8524 | The current transaction could not be exported to the remote provider. It has been rolled back. |
8525 | Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. |
TSQL Error Codes - 8600 to 8699
Error Code | Description |
---|---|
8601 | Internal Query Processor Error: The query processor could not obtain access to a required interface. |
8602 | Indexes used in hints must be explicitly included by the index tuning wizard. |
8616 | The index hints for table '%.*ls' were ignored because the table was considered a fact table in the star join. |
8617 | Invalid Query: CUBE and ROLLUP cannot compute distinct aggregates. |
8618 | Warning: The query processor could not produce a query plan from the optimizer because the total length of all the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes. |
8619 | Warning: The query processor could not produce a query plan from the optimizer because the total length of all the columns in the GROUP BY or ORDER BY clause exceeds 8000 bytes. Resubmit your query without the ROBUST PLAN hint. |
8620 | Internal Query Processor Error: The query processor encountered an internal limit overflow. |
8621 | Internal Query Processor Error: The query processor ran out of stack space during query optimization. |
8622 | Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN. |
8623 | Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information. |
8624 | Internal SQL Server error. |
8625 | Warning: The join order has been enforced because a local join hint is used. |
8626 | Only text pointers are allowed in work tables, never text, ntext, or image columns. The query processor produced a query plan that required a text, ntext, or image column in a work table. |
8627 | The query processor could not produce a query plan because of the combination of hints and text, ntext, or image data passing through operators using work tables. |
8628 | A time out occurred while waiting to optimize the query. Rerun the query. |
8629 | The query processor could not produce a query plan from the optimizer because a query cannot update a text, ntext, or image column and a clustering key at the same time. |
8630 | Internal Query Processor Error: The query processor encountered an unexpected error during execution. |
8640 | Internal Query Processor Error: The query processor encountered an unexpected work table error during execution. |
8642 | The query processor could not start the necessary thread resources for parallel query execution. |
8644 | Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine. |
8645 | A time out occurred while waiting for memory resources to execute the query. Rerun the query. |
8646 | The index entry for row ID %.*hs was not found in index ID %d, of table %d, in database '%.*ls'. |
8647 | Scan on sysindexes for database ID %d, object ID %ld, returned a duplicate index ID %d. Run DBCC CHECKTABLE on sysindexes. |
8648 | Could not insert a row larger than the page size into a hash table. Resubmit the query with the ROBUST PLAN hint. |
8649 | The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator. |
8650 | Intra-query parallelism caused your server command (process ID #%d) to deadlock. Rerun the query without intra-query parallelism by using the query hint option (maxdop 1). |
8651 | Could not perform the requested operation because the minimum query memory is not available. Decrease the configured value for the 'min memory per query' server configuration option. |
8653 | Warning: The query processor is unable to produce a plan because the table '%.*ls' is marked OFFLINE. |
8654 | A cursor plan could not be generated for the given statement because it contains textptr ( inrow lob ). |
8660 | An index cannot be created on the view '%.*ls' because the view definition does not include all the columns in the GROUP BY clause. |
8661 | A clustered index cannot be created on the view '%.*ls' because the index key includes columns which are not in the GROUP BY clause. |
8662 | An index cannot be created on the view '%.*ls' because the view definition includes an unknown value (the sum of a nullable expression). |
8663 | An index cannot be created on the view '%.*ls' because the view definition does not include count_big(*). |
8664 | An index cannot be created on the view '%.*ls' because the view definition includes duplicate column names. |
8665 | An index cannot be created on the view '%.*ls' because no row can satisfy the view definition. |
8666 | Warning: The optimizer cannot use the index because the select list of the view contains a non-aggregate expression. |
8667 | Warning: The optimizer cannot use the index because the group-by list in the view forms a key and is redundant. |
8680 | Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase. |
TSQL Error Codes - 8900 to 8999
Error Code | Description |
---|---|
8901 | Deadlock detected during DBCC. Complete the transaction in progress and retry this statement. |
8902 | Memory allocation error during DBCC processing. |
8903 | Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID. |
8904 | Extent %S_PGID in database ID %d is allocated by more than one allocation object. |
8905 | Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it. |
8906 | Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags '%hs'. |
8908 | Table error: Database ID %d, object ID %d, index ID %d. Chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->prev = %S_PGID. |
8909 | Table error: Object ID %d, index ID %d, page ID %S_PGID. The PageId in the page header = %S_PGID. |
8910 | Page %S_PGID in database ID %d is allocated to both object ID %d, index ID %d, and object ID %d, index ID %d. |
8911 | The error has been repaired. |
8912 | %.*ls fixed %d allocation errors and %d consistency errors in database '%ls'. |
8913 | Extent %S_PGID is allocated to '%ls' and at least one other object. |
8914 | Incorrect PFS free space information for page %S_PGID, object ID %d, index ID %d, in database ID %d. Expected value %hs, actual value %hs. |
8915 | File %d (number of mixed extents = %ld, mixed pages = %ld). |
8916 | Object ID %ld, Index ID %ld, data extents %ld, pages %ld, mixed extent pages %ld. |
8917 | Object ID %ld, Index ID %ld, index extents %ld, pages %ld, mixed extent pages %ld. |
8918 | (number of mixed extents = %ld, mixed pages = %ld) in this database. |
8919 | Single page allocation %S_PGID in table %ls, object ID %d, index ID %d is not allocated in PFS page ID %S_PGID. |
8920 | Cannot perform a %ls operation inside a user transaction. Terminate the transaction and reissue the statement. |
8921 | CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors. |
8922 | Could not repair this error. |
8923 | The repair level on the DBCC statement caused this repair to be bypassed. |
8924 | Repairing this error requires other errors to be corrected first. |
8925 | Table error: Cross object linkage: Page %S_PGID, slot %d, in object ID %d, index ID %d, refers to page %S_PGID, slot %d, in object ID %d, index ID %d. |
8926 | Table error: Cross object linkage: Parent page %S_PGID, slot %d, in object ID %d, index ID %d, and page %S_PGID, slot %d, in object ID %d, index ID %d, next refer to page %S_PGID but are not in the same object. |
8927 | Object ID %d, index ID %d: The ghosted record count (%d) in the header does not match the number of ghosted records (%d) found on page %S_PGID. |
8928 | Object ID %d, index ID %d: Page %S_PGID could not be processed. See other errors for details. |
8929 | Object ID %d: Errors found in text ID %I64d owned by data record identified by %.*ls. |
8930 | Table error: Object ID %d, index ID %d cross-object chain linkage. Page %S_PGID points to %S_PGID in object ID %d, index ID %d. |
8931 | Table error: Object ID %d, index ID %d B-tree level mismatch, page %S_PGID. Level %d does not match level %d from parent %S_PGID. |
8932 | Table error: Object ID %d, index ID %d, column '%.*ls'. The column ID %d is not valid for this table. The valid range is from 1 to %d. |
8933 | Table error: Object ID %d, index ID %d. The low key value on page %S_PGID (level %d) is not %ls the key value in the parent %S_PGID slot %d. |
8934 | Table error: Object ID %d, index ID %d. The high key value on page %S_PGID (level %d) is not less than the low key value in the parent %S_PGID, slot %d of the next page %S_PGID. |
8935 | Table error: Object ID %d, index ID %d. The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page. |
8936 | Table error: Object ID %d, index ID %d. B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID. |
8937 | Table error: Object ID %d, index ID %d. B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d. |
8938 | Table error: Page %S_PGID, Object ID %d, index ID %d. Unexpected page type %d. |
8939 | Table error: Object ID %d, index ID %d, page %S_PGID. Test (%hs) failed. Values are %ld and %ld. |
8940 | Table error: Object ID %d, index ID %d, page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned. |
8941 | Table error: Object ID %d, index ID %d, page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid. |
8942 | Table error: Object ID %d, index ID %d, page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row. |
8943 | Table error: Object ID %d, index ID %d, page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x. |
8944 | Table error: Object ID %d, index ID %d, page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld. |
8945 | Table error: Object ID %d, index ID %d will be rebuilt. |
8946 | Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, object ID and page ID on the page. |
8947 | Table error: Multiple IAM pages for object ID %d, index ID %d contain allocations for the same interval. IAM pages %S_PGID and %S_PGID. |
8948 | Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x. |
8949 | %.*ls fixed %d allocation errors and %d consistency errors in table '%ls' (object ID %d). |
8950 | %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object. |
8951 | Table error: Table '%ls' (ID %d). Missing or invalid key in index '%ls' (ID %d) for the row: |
8952 | Table error: Database '%ls', index '%ls.%ls' (ID %d) (index ID %d). Extra or invalid key for the keys: |
8953 | Repair: Deleted text column, text ID %I64d, for object ID %d on page %S_PGID, slot %d. |
8954 | %.*ls found %d allocation errors and %d consistency errors not associated with any single object. |
8955 | Data row (%d:%d:%d) identified by (%ls) has index values (%ls). |
8956 | Index row (%d:%d:%d) with values (%ls) points to the data row identified by (%ls). |
8957 | DBCC %ls (%ls%ls%ls) executed by %ls found %d errors and repaired %d errors. |
8958 | %ls is the minimum repair level for the errors found by DBCC %ls (%ls %ls). |
8959 | Table error: IAM page %S_PGID for object ID %d, index ID %d is linked in the IAM chain for object ID %d, index ID %d by page %S_PGID. |
8960 | Table error: Page %S_PGID, slot %d, column %d is not a valid complex column. |
8961 | Table error: Object ID %d. The text, ntext, or image node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d. |
8962 | Table error: The text, ntext, or image node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d. |
8963 | Table error: The text, ntext, or image node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d. |
8964 | Table error: Object ID %d. The text, ntext, or image node at page %S_PGID, slot %d, text ID %I64d is not referenced. |
8965 | Table error: Object ID %d. The text, ntext, or image node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan. |
8966 | Could not read and latch page %S_PGID with latch type %ls. %ls failed. |
8967 | Table error: Invalid value detected in %ls for Object ID %d, index ID %d. Row skipped. |
8968 | Table error: %ls page %S_PGID (object ID %d, index ID %d) is out of the range of this database. |
8969 | Table error: IAM chain linkage error: Object ID %d, index ID %d. The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID. |
8970 | Row error: Object ID %d, index ID %d, page ID %S_PGID, row ID %d. Column '%.*ls' was created NOT NULL, but is NULL in the row. |
8971 | Forwarded row mismatch: Object ID %d, page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d. |
8972 | Forwarded row referenced by more than one row. Object ID %d, page %S_PGID, slot %d incorrectly points to forwarded row page %S_PGID, slot %d; the forwarded row correctly refers back to page %S_PGID, slot %d. |
8973 | CHECKTABLE processing of object ID %d, index ID %d encountered page %S_PGID, slot %d twice. Possible internal error or allocation fault. |
8974 | Text node referenced by more than one node. Object ID %d, text, ntext, or image node page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d. |
8975 | Table error: Object ID %d, index ID %d. The child page pointer %S_PGID on PageId %S_PGID, slot %d is not a valid page for this database. |
8976 | Table error: Object ID %d, index ID %d. Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors. |
8977 | Table error: Object ID %d, index ID %d. Parent node for page %S_PGID was not encountered. |
8978 | Table error: Object ID %d, index ID %d. Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem. |
8979 | Table error: Object ID %d, index ID %d. Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in sysindexes. |
8980 | Table error: Object ID %d, index ID %d. Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered. |
8981 | Table error: Object ID %d, index ID %d. The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage. |
8982 | Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d refers to page %S_PGID in object ID %d, index ID %d but is not in the same index. |
8983 | File %d. Extents %d, used pages %d, reserved pages %d, mixed extents %d, mixed pages %d. |
8984 | Object ID %d, index ID %d. Allocations for %S_PGID. IAM %S_PGID, extents %d, used pages %d, mixed pages %d. |
8985 | Could not locate file '%.*ls' in sysfiles. |
8986 | Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS". |
8987 | No help available for DBCC statement '%.*ls'. |
8988 | The schema for database '%ls' is changing. May find spurious allocation problems due to schema changes in progress. |
8989 | %.*ls found %d allocation errors and %d consistency errors in database '%ls'. |
8990 | %.*ls found %d allocation errors and %d consistency errors in table '%ls' (object ID %d). |
8991 | 0x%.8x + 0x%.8x bytes is not a valid address range. |
8992 | Database ID %d, object '%ls' (ID %d). Loop in data chain detected at %S_PGID. |
8993 | Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error. |
8994 | Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error. |
8995 | System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d. |
8996 | IAM page %S_PGID for object ID %d, index ID %d controls pages in filegroup %d, that should be in filegroup %d. |
8997 | Single page allocation %S_PGID for object ID %d, index ID %d is in filegroup %d; it should be in filegroup %d. |
8998 | Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID %d pages from %S_PGID to %S_PGID. See other errors for cause. |
8999 | Database tempdb allocation errors prevent further %ls processing. |
TSQL Error Codes - 9000 to 9099
Error Code | Description |
---|---|
9001 | The log for database '%.*ls' is not available. |
9002 | The log file for database '%.*ls' is full. Back up the transaction log for the database to free up some log space. |
9003 | The LSN %S_LSN passed to log scan in database '%.*ls' is invalid. |
9004 | An error occurred while processing the log for database '%.*ls'. |
9005 | Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid. |
9006 | Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d. |
9007 | Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file. |
9008 | Cannot shrink log file %d (%s) because all logical log files are in use. |
9009 | Cannot shrink log file %d (%s) because of minimum log space required. |
9010 | User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission |
TSQL Error Codes - 10000 to 10999
Error Code | Description |
---|---|
10000 | Unknown provider error. |
10001 | The provider reported an unexpected catastrophic failure. |
10002 | The provider did not implement the functionality. |
10003 | The provider ran out of memory. |
10004 | One or more arguments were reported invalid by the provider. |
10005 | The provider did not support an interface. |
10006 | The provider indicated an invalid pointer was used. |
10007 | The provider indicated an invalid handle was used. |
10008 | The provider terminated the operation. |
10009 | The provider did not give any information about the error. |
10010 | The data necessary to complete this operation was not yet available to the provider. |
10011 | Access denied. |
10021 | Execution terminated by the provider because a resource limit was reached. |
10022 | The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned. |
10023 | The provider does not support the necessary method. |
10024 | The provider indicates that the user did not have the permission to perform the operation. |
10025 | Provider caused a server fault in an external process. |
10026 | No command text was set. |
10027 | Command was not prepared. |
10028 | Authentication failed. |
10031 | An error occurred because one or more properties could not be set. |
10032 | Cannot return multiple result sets (not supported by the provider). |
10033 | The specified index does not exist or the provider does not support an index scan on this data source. |
10034 | The specified table does not exist. |
10035 | No value was given for one or more of the required parameters. |
10041 | Could not set any property values. |
10042 | Cannot set any properties while there is an open rowset. |
10051 | An error occurred while setting the data. |
10052 | The insertion was canceled by the provider during notification. |
10053 | Could not convert the data value due to reasons other than sign mismatch or overflow. |
10054 | The data value for one or more columns overflowed the type used by the provider. |
10055 | The data violated the integrity constraints for one or more columns. |
10056 | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
10057 | Cannot create the row. Would exceed the total number of active rows supported by the rowset. |
10058 | The consumer cannot insert a new row before releasing previously-retrieved row handles. |
10061 | An error occurred while setting data for one or more columns. |
10062 | The change was canceled by the provider during notification. |
10063 | Could not convert the data value due to reasons other than sign mismatch or overflow. |
10064 | The data value for one or more columns overflowed the type used by the provider. |
10065 | The data violated the integrity constraints for one or more columns. |
10066 | The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. |
10067 | The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized. |
10068 | The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source. |
10069 | The consumer could not delete the row. The insertion has been transmitted to the data source. |
10075 | An error occurred while deleting the row. |
10081 | The rowset uses integrated indexes and there is no current index. |
10085 | RestartPosition on the table was canceled during notification. |
10086 | The table was built over a live data stream and the position cannot be restarted. |
10087 | The provider did not release some of the existing rows. |
10088 | The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed. |
TSQL Error Codes - 11000 to 11999
Error Code | Description |
---|---|
11000 | Unknown status code for this column. |
11001 | Non-NULL value successfully returned. |
11002 | Deferred accessor validation occurred. Invalid binding for this column. |
11003 | Could not convert the data value due to reasons other than sign mismatch or overflow. |
11004 | Successfully returned a NULL value. |
11005 | Successfully returned a truncated value. |
11006 | Could not convert the data type because of a sign mismatch. |
11007 | Conversion failed because the data value overflowed the data type used by the provider. |
11008 | The provider cannot allocate memory or open another storage object on this column. |
11009 | The provider cannot determine the value for this column. |
11010 | The user did not have permission to write to the column. |
11011 | The data value violated the integrity constraints for the column. |
11012 | The data value violated the schema for the column. |
11013 | The column had a bad status. |
11014 | The column used the default value. |
11015 | The column was skipped when setting data. |
11031 | The row was successfully deleted. |
11032 | The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. |
11033 | The row was released even though it had a pending change. |
11034 | Deletion of the row was canceled during notification. |
11036 | The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized. |
11037 | The row has a pending delete or the deletion had been transmitted to the data source. |
11038 | The row is a pending insert row. |
11039 | DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source. |
11040 | Deleting the row violated the integrity constraints for the column or table. |
11041 | The row handle was invalid or was a row handle to which the current thread does not have access rights. |
11042 | Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS. |
11043 | The row has a storage object open. |
11044 | The provider ran out of memory and could not fetch the row. |
11045 | User did not have sufficient permission to delete the row. |
11046 | The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out. |
11047 | Updating did not meet the schema requirements. |
11048 | There was a recoverable, provider-specific error, such as an RPC failure. |
11100 | The provider indicates that conflicts occurred with other properties or requirements. |
11101 | Could not obtain an interface required for text, ntext, or image access. |
11102 | The provider could not support a required row lookup interface. |
11103 | The provider could not support an interface required for the UPDATE/DELETE/INSERT statements. |
11104 | The provider could not support insertion on this table. |
11105 | The provider could not support updates on this table. |
11106 | The provider could not support deletion on this table. |
11107 | The provider could not support a row lookup position. |
11108 | The provider could not support a required property. |
11109 | The provider does not support an index scan on this data source. |
TSQL Error Codes - 13000 to 13999
Error Code | Description |
---|---|
13001 | data page |
13002 | index page |
13003 | leaf page |
13004 | last |
13005 | root |
13006 | read from |
13007 | send to |
13008 | receive |
13009 | send |
13010 | read |
13011 | wait |
13012 | a USE database statement |
13013 | a procedure or trigger |
13014 | a DISTINCT clause |
13015 | a view |
13016 | an INTO clause |
13017 | an ORDER BY clause |
13018 | a COMPUTE clause |
13019 | a SELECT INTO statement |
13020 | option |
13021 | offset option |
13022 | statistics option |
13023 | parameter option |
13024 | function name |
13025 | varbinary (128) NOT NULL |
13026 | parameter |
13027 | convert specification |
13028 | index |
13029 | table |
13030 | database |
13031 | procedure |
13032 | trigger |
13033 | view |
13034 | default |
13035 | rule |
13036 | system table |
13037 | unknown type |
13038 | SET statement |
13039 | column |
13040 | type |
13041 | character string |
13042 | integer |
13043 | identifier |
13044 | number |
13045 | integer value |
13046 | floating point value |
13047 | object |
13048 | column heading |
13076 | an assignment |
13077 | a cursor declaration |
13078 | replication filter |
13079 | variable assignment |
13080 | statistics |
13081 | file |
13082 | filegroup |
13083 | server |
13084 | write |
13085 | function |
13086 | database collation |
13087 | drop |
13088 | alter |
TSQL Error Codes - 14000 to 14999
Error Code | Description |
---|---|
14002 | Could not find the 'Sync' subsystem with the task ID %ld. |
14003 | You must supply a publication name. |
14004 | %s must be in the current database. |
14005 | Could not drop publication. A subscription exists to it. |
14006 | Could not drop the publication. |
14008 | There are no publications. |
14009 | There are no articles for publication '%s'. |
14010 | The remote server is not defined as a subscription server. |
14012 | The @status parameter value must be either 'active' or 'inactive'. |
14013 | This database is not enabled for publication. |
14014 | The synchronization method (@sync_method) must be '[bcp] native', '[bcp] character', 'concurrent' or 'concurrent_c'. |
14015 | The replication frequency (@repl_freq) must be either 'continuous' or 'snapshot'. |
14016 | The publication '%s' already exists. |
14017 | Invalid @restricted parameter value. Valid options are 'true' or 'false'. |
14018 | Could not create the publication. |
14019 | The @operation parameter value must be either 'add' or 'drop'. |
14020 | Could not obtain the column ID for the specified column. Schema replication failed. |
14021 | The column was not added correctly to the article. |
14022 | The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'status', 'schema_option', or 'destination_owner'. |
14023 | The type must be '[indexed view] logbased', '[indexed view] logbased manualfilter', '[indexed view] logbased manualview', '[indexed view] logbased manualboth', or '( view | indexed view | proc | func ) schema only'. |
14025 | Article update successful. |
14027 | %s does not exist in the current database. |
14028 | Only user tables, materialized views, and stored procedures can be published as 'logbased' articles. |
14029 | The vertical partition switch must be either 'true' or 'false'. |
14030 | The article '%s' exists in publication '%s'. |
14031 | User tables and views are the only valid synchronization objects. |
14032 | The value of parameter %s cannot be 'all'. It is reserved by replication stored procedures. |
14033 | Could not change replication frequency because there are active subscriptions on the publication. |
14034 | The publication name (@publication) cannot be the keyword 'all'. |
14035 | The replication option '%s' of database '%s' has already been set to true. |
14036 | Could not enable database for publishing. |
14037 | The replication option '%s' of database '%s' has been set to false. |
14038 | Could not disable database for publishing. |
14039 | Could not construct column clause for article view. Reduce the number of columns or create the view manually. |
14040 | The server '%s' is already a Subscriber. |
14042 | Could not create Subscriber. |
14043 | The parameter %s cannot be NULL. |
14046 | Could not drop article. A subscription exists on it. |
14047 | Could not drop %s. |
14048 | The server '%s' is not a Subscriber. |
14049 | Stored procedures for replication are the only objects that can be used as a filter. |
14050 | No subscription is on this publication or article. |
14051 | The parameter value must be 'sync_type' or 'dest_db'. |
14052 | The @sync_type parameter value must be 'automatic' or 'none'. |
14053 | The subscription could not be updated at this time. |
14054 | The subscription was updated successfully. |
14055 | The subscription does not exist. |
14056 | The subscription could not be dropped at this time. |
14057 | The subscription could not be created. |
14058 | The subscription already exists. |
14059 | Materialized view articles cannot be created for publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts. |
14061 | The @pre_creation_cmd parameter value must be 'none', 'drop', 'delete', or 'truncate'. |
14062 | The Subscriber was dropped. |
14063 | The remote server does not exist or has not been designated as a valid Subscriber. |
14065 | The @status parameter value must be 'initiated', 'active', 'inactive', or 'subscribed'. |
14066 | The previous status must be 'active', 'inactive', or 'subscribed'. |
14067 | The status value is the same as the previous status value. |
14068 | Could not update sysobjects. The subscription status could not be changed. |
14069 | Could not update sysarticles. The subscription status could not be changed. |
14070 | Could not update the distribution database subscription table. The subscription status could not be changed. |
14071 | Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor. |
14074 | The server '%s' is already listed as a Publisher. |
14075 | The Publisher could not be created at this time. |
14076 | Could not grant replication login permission to '%s'. |
14077 | The publication was updated successfully. |
14078 | The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_internet', 'allow_push', 'allow_pull', 'allow_anonymous', or 'retention'. |
14080 | The remote server does not exist or has not been designated as a valid Publisher. |
14085 | The Subscriber information could not be obtained from the Distributor. |
14088 | The table '%s' must have a primary key to be published using the transaction-based method. |
14089 | The clustered index on materialized view '%s' may not contain nullable columns if it is to be published using the transaction-based method. |
14090 | Error evaluating article synchronization object after column drop. The filter clause for article '%s' must not reference the dropped column. |
14091 | The @type parameter passed to sp_helpreplicationdb must be either 'pub' or 'sub'. |
14092 | Could not change article because there is an existing subscription to the article. |
14093 | Cannot grant or revoke access directly on publication '%s' because it uses the default publication access list. |
14094 | Could not subscribe to article '%s' because heterogeneous Subscriber '%s' does not support the @pre_creation_cmd parameter value 'truncate'. |
14095 | Could not subscribe to publication '%s' because heterogeneous Subscriber '%s' only supports the @sync_method parameter value 'bcp character' . |
14096 | The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is 'drop'. |
14097 | The 'status' value must be 'no column names', 'include column names', 'string literals', 'parameters', 'DTS horizontal partitions' or 'no DTS horizontal partitions'. |
14098 | Cannot drop Distribution Publisher '%s'. The remote Publisher is using '%s' as Distributor. |
14099 | The server '%s' is already defined as a Distributor. |
TSQL Error Codes - 14100 to 14199
Error Code | Description |
---|---|
14100 | Specify all articles when subscribing to a publication using concurrent snapshot processing. |
14101 | The publication '%s' already has a Snapshot Agent defined. |
14102 | Specify all articles when unsubscribing from a publication using concurrent snapshot processing. |
14105 | You have updated the distribution database property '%s' successfully. |
14106 | Distribution retention periods must be greater than 0. |
14107 | The @max_distretention value must be larger than the @min_distretention value. |
14108 | Removed %ld history records from %s. |
14109 | The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Windows Authentication). |
14110 | For stored procedure articles, the @property parameter value must be 'description', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'schema_option', or 'destination_owner'. |
14111 | The @pre_creation_cmd parameter value must be 'none' or 'drop'. |
14112 | This procedure can be executed only against table-based articles. |
14113 | Could not execute '%s'. Check '%s' in the install directory. |
14114 | '%s' is not configured as a Distributor. |
14115 | The property parameter value must be %s. |
14117 | '%s' is not configured as a distribution database. |
14118 | A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema only' article. |
14119 | Could not add the distribution database '%s'. This distribution database already exists. |
14120 | Could not drop the distribution database '%s'. This distributor database is associated with a Publisher. |
14121 | Could not drop the Distributor '%s'. This Distributor has associated distribution databases. |
14122 | The @article parameter value must be 'all' for immediate_sync publications. |
14123 | The subscription @sync_type parameter value 'manual' is no longer supported. |
14124 | A publication must have at least one article before a subscription to it can be created. |
14126 | You do not have the required permissions to complete the operation. |
14128 | Invalid @subscription_type parameter value. Valid options are 'push' or 'pull'. |
14129 | The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication. |
14135 | There is no subscription on Publisher '%s', publisher database '%s', publication '%s'. |
14136 | The keyword 'all' is reserved by replication stored procedures. |
14137 | The @value parameter value must be either 'true' or 'false'. |
14138 | Invalid option name '%s'. |
14139 | The replication system table '%s' already exists. |
14143 | Cannot drop Distributor Publisher '%s'. There are Subscribers associated with it in the distribution database '%s'. |
14144 | Cannot drop Subscriber '%s'. There are subscriptions from it in the publication database '%s'. |
14146 | The article parameter '@schema_option' cannot be NULL. |
14147 | Restricted publications are no longer supported. |
14148 | Invalid '%s' value. Valid values are 'true' or 'false'. |
14149 | Removed %ld replication history records in %s seconds (%ld row/secs). |
14150 | Replication-%s: agent %s succeeded. %s |
14151 | Replication-%s: agent %s failed. %s |
14152 | Replication-%s: agent %s scheduled for retry. %s |
14153 | Replication-%s: agent %s warning. %s |
14154 | The Distributor parameter must be '@heartbeat_interval'. |
14155 | Invalid article ID specified for procedure script generation. |
14156 | The custom stored procedure was not specified in the article definition. |
14157 | The subscription created by Subscriber '%s' to publication '%s' has expired and has been dropped. |
14158 | Replication-%s: agent %s: %s. |
14159 | Could not change property '%s' for article '%s' because there is an existing subscription to the article. |
14199 | The specified job "%s" is not created for maintenance plans. |
TSQL Error Codes - 14200 to 14299
Error Code | Description |
---|---|
14200 | The specified '%s' is invalid. |
14201 | 0 (all steps) .. |
14202 | before or after @active_start_time |
14203 | sp_helplogins [excluding Windows NT groups] |
14204 | 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions) |
14205 | (unknown) |
14206 | 0..n seconds |
14207 | -1 [no maximum], 0..n |
14208 | 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend] |
14209 | 0..127 [1 = Sunday .. 64 = Saturday] |
14210 | notification |
14211 | server |
14212 | (all jobs) |
14213 | Core Job Details: |
14214 | Job Steps: |
14215 | Job Schedules: |
14216 | Job Target Servers: |
14217 | SQL Server Warning: '%s' has performed a forced defection of TSX server '%s'. Run sp_delete_targetserver at the MSX in order to complete the defection. |
14218 | hour |
14219 | minute |
14220 | second |
14221 | This job has one or more notifications to operators other than '%s'. The job cannot be targeted at remote servers as currently defined. |
14222 | Cannot rename the '%s' operator. |
14223 | Cannot modify or delete operator '%s' while this server is a %s. |
14224 | Warning: The server name given is not the current MSX server ('%s'). |
14225 | Warning: Could not determine local machine name. This prevents MSX operations from being posted. |
14226 | %ld history entries purged. |
14227 | Server defected from MSX '%s'. %ld job(s) deleted. |
14228 | Server MSX enlistment changed from '%s' to '%s'. |
14229 | Server enlisted into MSX '%s'. |
14230 | SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted. |
14231 | SP_POST_MSX_OPERATION Warning: The specified %s ('%s') is not involved in a multiserver job. |
14232 | Specify either a job_name, job_id, or an originating_server. |
14233 | Specify a valid job_id (or 0x00 for all jobs). |
14234 | The specified '%s' is invalid (valid values are returned by %s). |
14235 | The specified '%s' is invalid (valid values are greater than 0 but excluding %ld). |
14236 | Warning: Non-existent step referenced by %s. |
14237 | When an action of 'REASSIGN' is specified, the New Login parameter must also be supplied. |
14238 | %ld jobs deleted. |
14239 | %ld jobs reassigned to %s. |
14240 | Job applied to %ld new servers. |
14241 | Job removed from %ld servers. |
14242 | Only a system administrator can reassign ownership of a job. |
14243 | Job '%s' started successfully. |
14244 | Only a system administrator can reassign tasks. |
14245 | Specify either the @name, @id, or @loginname of the task(s) to be deleted. |
14246 | Specify either the @currentname or @id of the task to be updated. |
14247 | Only a system administrator can view tasks owned by others. |
14248 | This login is the owner of %ld job(s). You must delete or reassign these jobs before the login can be dropped. |
14249 | Specify either @taskname or @oldloginname when reassigning a task. |
14250 | The specified %s is too long. It must contain no more than %ld characters. |
14251 | Cannot specify '%s' as the operator to be notified. |
14252 | Cannot perform this action on a job you do not own. |
14253 | %ld (of %ld) job(s) stopped successfully. |
14254 | Job '%s' stopped successfully. |
14255 | The owner ('%s') of this job is either an invalid login, or is not a valid user of database '%s'. |
14256 | Cannot start job '%s' (ID %s) because it does not have any job server(s) defined. |
14257 | Cannot stop job '%s' (ID %s) because it does not have any job server(s) defined. |
14258 | Cannot perform this operation while SQLServerAgent is starting. Try again later. |
14259 | A schedule (ID %ld, '%s') for this job with this definition already exists. |
14260 | You do not have sufficient permission to run this command. |
14261 | The specified %s ('%s') already exists. |
14262 | The specified %s ('%s') does not exist. |
14263 | Target server '%s' is already a member of group '%s'. |
14264 | Target server '%s' is not a member of group '%s'. |
14265 | The MSSQLServer service terminated unexpectedly. |
14266 | The specified '%s' is invalid (valid values are: %s). |
14267 | Cannot add a job to the '%s' job category. |
14268 | There are no jobs at this server that originated from server '%s'. |
14269 | Job '%s' is already targeted at server '%s'. |
14270 | Job '%s' is not currently targeted at server '%s'. |
14271 | A target server cannot be named '%s'. |
14272 | Object-type and object-name must be supplied as a pair. |
14273 | You must provide either @job_id or @job_name (and, optionally, @schedule_name), or @schedule_id. |
14274 | Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. |
14275 | The originating server must be either '(local)' or '%s'. |
14276 | '%s' is a permanent %s category and cannot be deleted. |
14277 | The command script does not destroy all the objects that it creates. Revise the command script. |
14278 | The schedule for this job is invalid (reason: %s). |
14279 | Supply either @job_name or @originating_server. |
14280 | Supply either a job name (and job aspect), or one or more job filter parameters. |
14281 | Warning: The @new_owner_login_name parameter is not necessary when specifying a 'DELETE' action. |
14282 | Supply either a date (created or last modified) and a data comparator, or no date parameters at all. |
14283 | Supply @target_server_groups or @target_servers, or both. |
14284 | Cannot specify a job ID for a new job. An ID will be assigned by the procedure. |
14285 | Cannot add a local job to a multiserver job category. |
14286 | Cannot add a multiserver job to a local job category. |
14287 | The '%s' supplied has an invalid %s. |
14288 | %s cannot be before %s. |
14289 | %s cannot contain '%s' characters. |
14290 | This job is currently targeted at the local server so cannot also be targeted at a remote server. |
14291 | This job is currently targeted at a remote server so cannot also be targeted at the local server. |
14292 | There are two or more tasks named '%s'. Specify %s instead of %s to uniquely identify the task. |
14293 | There are two or more jobs named '%s'. Specify %s instead of %s to uniquely identify the job. |
14294 | Supply either %s or %s to identify the job. |
14295 | Frequency Type 0x2 (OnDemand) is no longer supported. |
14296 | This server is already enlisted into MSX '%s'. |
14297 | Cannot enlist into the local machine. |
14298 | This server is not currently enlisted into an MSX. |
14299 | Server '%s' is an MSX. Cannot enlist one MSX into another MSX. |
TSQL Error Codes - 14300 to 14399
Error Code | Description |
---|---|
14300 | Circular dependencies exist. Dependency evaluation cannot continue. |
14301 | Logins other than the current user can only be seen by members of the sysadmin role. |
14302 | You must upgrade your client to version 6.5 of SQL-DMO and SQL Server Enterprise Manager to connect to this server. The upgraded versions will administer both SQL Server version 6.5 and 6.0 (if sqlole65.sql is run). |
14303 | Stored procedure '%s' failed to access registry key. |
14304 | Stored procedure '%s' can run only on Windows 2000 servers. |
14350 | Cannot initialize COM library because CoInitialize failed. |
14351 | Cannot complete this operation because an unexpected error occurred. |
14352 | Cannot find Active Directory information in the registry for this SQL Server instance. Run sp_ActiveDirectory_SCP again. |
14353 | Cannot determine the service account for this SQL Server instance. |
14354 | Cannot start the MSSQLServerADHelper service. Verify that the service account for this SQL Server instance has the necessary permissions to start the MSSQLServerADHelper service. |
14355 | The MSSQLServerADHelper service is busy. Retry this operation later. |
14356 | The Windows Active Directory client is not installed properly on the computer where this SQL Server instance is running. LoadLibrary failed to load ACTIVEDS.DLL. |
14357 | Cannot list '%s' in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters. |
14358 | Cannot determine the SQL Server Agent proxy account for this SQL Server instance or the account is not a domain user account. Use xp_sqlagent_proxy_account to configure SQL Server Agent to use a domain user account as the proxy account. |
TSQL Error Codes - 14400 to 14499
Error Code | Description |
---|---|
14410 | You must supply either a plan_name or a plan_id. |
14411 | Cannot delete this plan. The plan contains enlisted databases. |
14412 | The destination database is already part of a log shipping plan. |
14413 | This database is already log shipping. |
14414 | A log shipping monitor is already defined. |
14415 | The user name cannot be null when using SQL Server authentication. |
14416 | This stored procedure must be run in msdb. |
14417 | Cannot delete the monitor server while databases are participating in log shipping. |
14418 | The specified @backup_file_name was not created from database '%s'. |
14419 | The specified @backup_file_name is not a database backup. |
14420 | The log shipping source %s.%s has not backed up for %s minutes. |
14421 | The log shipping destination %s.%s is out of sync by %s minutes. |
14422 | Supply either @plan_id or @plan_name. |
14423 | Other databases are enlisted on this plan and must be removed before the plan can be deleted. |
14424 | The database '%s' is already involved in log shipping. |
14425 | The database '%s' does not seem to be involved in log shipping. |
14426 | A log shipping monitor is already defined. Call sp_define_log_shipping_monitor with @delete_existing = 1. |
14427 | A user name is necessary for SQL Server security. |
14428 | Could not remove the monitor as there are still databases involved in log shipping. |
14429 | There are still secondary servers attached to this primary. |
14430 | Invalid destination path %s. |
14440 | Could not set single user mode. |
14441 | Role change succeeded. |
14442 | Role change failed. |
14450 | The specified @backup_file_name was not taken from database '%s'. |
14451 | The specified @backup_file_name is not a database backup. |
TSQL Error Codes - 14500 to 14599
Error Code | Description |
---|---|
14500 | Supply either a non-zero message ID, non-zero severity, or non-null performance condition. |
14501 | An alert ('%s') has already been defined on this condition. |
14502 | The @target_name parameter must be supplied when specifying an @enum_type of 'TARGET'. |
14503 | The @target_name parameter should not be supplied when specifying an @enum_type of 'ALL' or 'ACTUAL'. |
14504 | '%s' is the fail-safe operator. You must make another operator the fail-safe operator before '%s' can be dropped. |
14505 | Specify a null %s when supplying a performance condition. |
14506 | Cannot set alerts on message ID %ld. |
14507 | A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'. |
14539 | Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX. |
14540 | Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX. |
14541 | The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX. |
14542 | It is invalid for any TSQL step of a multiserver job to have a non-null %s value. |
14543 | Login '%s' owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role. |
14544 | This job is owned by '%s'. Only a job owned by a member of the %s role can be a multiserver job. |
14545 | The %s parameter is not valid for a job step of type '%s'. |
14546 | The %s parameter is not supported on Windows 95/98 platforms. |
14547 | Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s. |
14548 | Target server '%s' does not have any jobs assigned to it. |
14549 | (Description not requested.) |
14550 | Command-Line Subsystem |
14551 | Replication Snapshot Subsystem |
14552 | Replication Transaction-Log Reader Subsystem |
14553 | Replication Distribution Subsystem |
14554 | Replication Merge Subsystem |
14555 | Active Scripting Subsystem |
14556 | Transact-SQL Subsystem |
14557 | [Internal] |
14558 | (encrypted command) |
14559 | (append output file) |
14560 | (include results in history) |
14561 | (normal) |
14562 | (quit with success) |
14563 | (quit with failure) |
14564 | (goto next step) |
14565 | (goto step) |
14566 | (idle) |
14567 | (below normal) |
14568 | (above normal) |
14569 | (time critical) |
14570 | (Job outcome) |
14571 | No description available. |
14572 | @freq_interval must be at least 1 for a daily job. |
14573 | @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job. |
14574 | @freq_interval must be between 1 and 31 for a monthly job. |
14575 | @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10). |
14576 | @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job. |
14577 | @freq_recurrence_factor must be at least 1. |
14578 | Starts whenever the CPU usage has remained below %ld percent for %ld seconds. |
14579 | Automatically starts when SQLServerAgent starts. |
14580 | job |
14581 | Replication Transaction Queue Reader Subsystem |
14585 | Only the owner of DTS Package '%s' or a member of the sysadmin role may reassign its ownership. |
14586 | Only the owner of DTS Package '%s' or a member of the sysadmin role may create new versions of it. |
14587 | Only the owner of DTS Package '%s' or a member of the sysadmin role may drop it or any of its versions. |
14588 | ID.VersionID = |
14589 | [not specified] |
14590 | DTS Package '%s' already exists with a different ID in this category. |
14591 | DTS Category '%s' already exists in the specified parent category. |
14592 | DTS Category '%s' was found in multiple parent categories. You must uniquely specify the category to be dropped. |
14593 | DTS Category '%s' contains packages and/or other categories. You must drop these first, or specify a recursive drop. |
14594 | DTS Package |
14595 | DTS Package '%s' exists in different categories. You must uniquely specify the package. |
14596 | DTS Package '%s' exists in another category. |
14597 | DTS Package ID '%s' already exists with a different name. |
14598 | Cannot drop the Local, Repository, or LocalDefault DTS categories. |
14599 | Name |
TSQL Error Codes - 15000 to 15099
Error Code | Description |
---|---|
15001 | Object '%ls' does not exist or is not a valid object for this operation. |
15002 | The procedure '%s' cannot be executed within a transaction. |
15003 | Only members of the %s role can execute this stored procedure. |
15004 | Name cannot be NULL. |
15005 | Statistics for all tables have been updated. |
15006 | '%s' is not a valid name because it contains invalid characters. |
15007 | The login '%s' does not exist. |
15008 | User '%s' does not exist in the current database. |
15009 | The object '%s' does not exist in database '%s'. |
15010 | The database '%s' does not exist. Use sp_helpdb to show available databases. |
15011 | Database option '%s' does not exist. |
15012 | The device '%s' does not exist. Use sp_helpdevice to show available devices. |
15013 | Table '%s': No columns without statistics found. |
15014 | The role '%s' does not exist in the current database. |
15015 | The server '%s' does not exist. Use sp_helpserver to show available servers. |
15016 | The default '%s' does not exist. |
15017 | The rule '%s' does not exist. |
15018 | Table '%s': Creating statistics for the following columns: |
15019 | The extended stored procedure '%s' does not exist. |
15020 | Statistics have been created for the %d listed columns of the above tables. |
15021 | There are no remote users mapped to any local user from remote server '%s'. |
15022 | The specified user name is already aliased. |
15023 | User or role '%s' already exists in the current database. |
15024 | The group '%s' already exists in the current database. |
15025 | The login '%s' already exists. |
15026 | Logical device '%s' already exists. |
15027 | There are no remote users mapped to local user '%s' from remote server '%s'. |
15028 | The server '%s' already exists. |
15029 | The data type '%s' already exists in the current database. |
15030 | The read-only bit cannot be turned off because the database is in standby mode. |
15031 | 'Virtual_device' device added. |
15032 | The database '%s' already exists. |
15033 | '%s' is not a valid official language name. |
15034 | The application role password must not be NULL. |
15035 | '%s' is not a database device. |
15036 | The data type '%s' does not exist. |
15037 | The physical data type '%s' does not allow nulls. |
15038 | User-defined data types based on timestamp are not allowed. |
15039 | The language %s already exists in syslanguages. |
15040 | User-defined error messages must have an ID greater than 50000. |
15041 | User-defined error messages must have a severity level between 1 and 25. |
15043 | You must specify 'REPLACE' to overwrite an existing message. |
15044 | '%s' is an unknown device type. Use 'disk', 'tape', or 'pipe'. |
15045 | The logical name cannot be NULL. |
15046 | The physical name cannot be NULL. |
15047 | The only permitted options for a tape device are 'skip' and 'noskip'. |
15048 | Valid values of database compatibility level are %d, %d, %d, or %d. |
15049 | Cannot unbind from '%s'. Use ALTER TABLE DROP CONSTRAINT. |
15050 | Cannot bind default '%s'. The default must be created using the CREATE DEFAULT statement. |
15051 | Cannot rename the table because it is published for replication. |
15052 | Prior to updating sysdatabases entry for database '%s', mode = %d and status = %d (status suspect_bit = %d). |
15053 | Objects exist which are not owned by the database owner. |
15054 | The current compatibility level is %d. |
15055 | Error. Updating sysdatabases returned @@error <> 0. |
15056 | No row in sysdatabases was updated because mode and status are already correctly reset. No error and no changes made. |
15057 | List of %s name contains spaces, which are not allowed. |
15058 | List of %s has too few names. |
15059 | List of %s has too many names. |
15060 | List of %s names contains name(s) which have '%s' non-alphabetic characters. |
15061 | Add device request denied. A physical device named '%s' already exists. |
15062 | The guest user cannot be mapped to a login name. |
15063 | The login already has an account under a different user name. |
15064 | PRIMARY KEY and UNIQUE KEY constraints do not have space allocated. |
15065 | All user IDs have been assigned. |
15066 | A default-name mapping of a remote login from remote server '%s' already exists. |
15067 | '%s' is not a local user. Remote login denied. |
15068 | A remote user '%s' already exists for remote server '%s'. |
15069 | One or more users are using the database. The requested operation cannot be completed. |
15070 | Object '%s' was successfully marked for recompilation. |
15071 | Usage: sp_addmessage <msgnum>,<severity>,<msgtext> [,<language> [,FALSE | TRUE [,REPLACE]]] |
15072 | Usage: sp_addremotelogin remoteserver [, loginame [,remotename]] |
15073 | For row in sysdatabases for database '%s', the status bit %d was forced off and mode was forced to 0. |
15074 | Warning: You must recover this database prior to access. |
15075 | The data type '%s' is reserved for future use. |
15076 | Default, table, and user data types must be in the current database. |
15077 | Rule, table, and user data type must be in the current database. |
15078 | The table or view must be in the current database. |
15079 | Queries processed: %d. |
15081 | Membership of the public role cannot be changed. |
15082 | NULL is not an acceptable parameter value for this procedure. Use a percent sign instead. |
15083 | Physical data type '%s' does not accept a collation |
15084 | The column or user data type must be in the current database. |
15085 | Usage: sp_addtype name, 'data type' [,'NULL' | 'NOT NULL'] |
15086 | Invalid precision specified. Precision must be between 1 and 38. |
15087 | Invalid scale specified. Scale must be less than precision and positive. |
15088 | The physical data type is fixed length. You cannot specify the length. |
15089 | Cannot change the '%s' option of a database while another user is in the database. |
15090 | There is already a local server. |
15091 | You must specify a length with this physical data type. |
15092 | Invalid length specified. Length must be between 1 and 8000 bytes. |
15093 | '%s' is not a valid date order. |
15094 | '%s' is not a valid first day. |
15095 | Insert into syslanguages failed. Language not added. |
15097 | The size associated with an extended property cannot be more than 7,500 bytes. |
TSQL Error Codes - 15100 to 15199
Error Code | Description |
---|---|
15100 | Usage: sp_bindefault defaultname, objectname [, 'futureonly'] |
15101 | Cannot bind a default to a column of data type timestamp. |
15102 | Cannot bind a default to an identity column. |
15103 | Cannot bind a default to a column created with or altered to have a default value. |
15104 | You do not own a table named '%s' that has a column named '%s'. |
15105 | You do not own a data type with that name. |
15106 | Usage: sp_bindrule rulename, objectname [, 'futureonly'] |
15107 | Cannot bind a rule to a column of data type text, ntext, image, or timestamp. |
15109 | Cannot change the owner of the master database. |
15110 | The proposed new database owner is already a user in the database. |
15111 | The proposed new database owner is already aliased in the database. |
15112 | The third parameter for table option 'text in row' is invalid. It should be 'on', 'off', '0', or a number from 24 through 7000. |
15123 | The configuration option '%s' does not exist, or it may be an advanced option. |
15124 | The configuration option '%s' is not unique. |
15125 | Trigger '%s' is not a trigger for '%s'. |
15126 | Trigger '%s' was not found. |
15127 | Cannot set the default language to a language ID not defined in syslanguages. |
15129 | '%d' is not a valid value for configuration option '%s'. |
15130 | Table '%s' already has a '%s' trigger for '%s'. |
15131 | Usage: sp_dbremove <dbname> [,dropdev] |
15132 | Cannot change default database belonging to someone else. |
15133 | INSTEAD OF trigger '%s' cannot be associated with an order. |
15134 | No alias exists for the specified user. |
15135 | Object is invalid. Extended properties are not permitted on '%s', or the object does not exist. |
15139 | The device is a RAM disk and cannot be used as a default device. |
15140 | Usage: sp_diskdefault logicalname {defaulton | defaultoff} |
15142 | Cannot drop the role '%s'. |
15143 | '%s' is not a valid option for the @updateusage parameter. Enter either 'true' or 'false'. |
15144 | The role has members. It must be empty before it can be dropped. |
15174 | Login '%s' owns one or more database(s). Change the owner of the following database(s) before dropping login: |
15175 | Login '%s' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login. |
15176 | The only valid @parameter value is 'WITH_LOG'. |
15177 | Usage: sp_dropmessage <msg number> [,<language> | 'ALL'] |
15178 | Cannot drop a message with an ID less than 50000. |
15179 | Message number %u does not exist. |
15180 | Cannot drop. The data type is being used. |
15181 | Cannot drop the database owner. |
15182 | Cannot drop the guest user from master or tempdb. |
15183 | The user owns objects in the database and cannot be dropped. |
15184 | The user owns data types in the database and cannot be dropped. |
15185 | There is no remote user '%s' mapped to local user '%s' from the remote server '%s'. |
15190 | There are still remote logins for the server '%s'. |
15191 | Usage: sp_dropserver server [, droplogins] |
15193 | This procedure can only be used on system tables. |
15194 | Cannot re-create index on this table. |
15197 | There is no text for object '%s'. |
15198 | The name supplied (%s) is not a user, role, or aliased login. |
TSQL Error Codes - 15200 to 15299
Error Code | Description |
---|---|
15200 | There are no remote servers defined. |
15201 | There are no remote logins for the remote server '%s'. |
15202 | There are no remote logins defined. |
15203 | There are no remote logins for '%s'. |
15204 | There are no remote logins for '%s' on remote server '%s'. |
15205 | There are no servers defined. |
15206 | Invalid Remote Server Option: '%s'. |
15210 | Only members of the sysadmin role can use the loginame option. The password was not changed. |
15211 | Old (current) password incorrect for user. The password was not changed. |
15216 | '%s' is not a valid option for the @delfile parameter. |
15217 | Property cannot be updated or deleted. Property '%s' does not exist for '%s'. |
15218 | Object '%s' is not a table. |
15220 | Usage: sp_remoteoption [remoteserver, loginame, remotename, optname, {true | false}] |
15221 | Remote login option does not exist or cannot be set by user. Run sp_remoteoption with no parameters to see options. |
15222 | Remote login option '%s' is not unique. |
15223 | Error: The input parameter '%s' is not allowed to be null. |
15224 | Error: The value for the @newname parameter contains invalid characters or violates a basic restriction (%s). |
15225 | No item by the name of '%s' could be found in the current database '%s', given that @itemtype was input as '%s'. |
15227 | The database '%s' cannot be renamed. |
15228 | A member of the sysadmin role must set database '%s' to single user mode with sp_dboption before it can be renamed. |
15233 | Property cannot be added. Property '%s' already exists for '%s'. |
15234 | Object is stored in sysprocedures and has no space allocated directly. |
15235 | Views do not have space allocated. |
15236 | Column '%s' has no default. |
15237 | User data type '%s' has no default. |
15238 | Column '%s' has no rule. |
15239 | User data type '%s' has no rule. |
15241 | Usage: sp_dboption [dbname [,optname [,'true' | 'false']]] |
15242 | Database option '%s' is not unique. |
15243 | The option '%s' cannot be changed for the master database. |
15244 | Only members of the sysadmin role or the database owner may set database options. |
15245 | DBCC DBCONTROL error. Database was not placed offline. |
15247 | User does not have permission to perform this action. |
15248 | Error: The parameter @oldname is either ambiguous or the claimed @itemtype (%s) was wrong. |
15249 | Error: Explicit @itemtype '%s' is unrecognized (%d). |
15250 | The database name component of the object qualifier must be the name of the current database. |
15251 | Invalid '%s' specified. It must be %s. |
15252 | The primary or foreign key table name must be given. |
15253 | Syntax error parsing SQL identifier '%s'. |
15254 | Users other than the database owner or guest exist in the database. Drop them before removing the database. |
15255 | '%s' is not a valid value for @autofix. The only valid value is 'auto'. |
15256 | Usage: sp_certify_removable <dbname> [,'auto'] |
15257 | The database that you are attempting to certify cannot be in use at the same time. |
15258 | The database must be owned by a member of the sysadmin role before it can be removed. |
15261 | Usage: sp_create_removable <dbname>,<syslogical>,<sysphysical>,<syssize>,<loglogical>,<logphysical>,<logsize>,<datalogical1>,<dataphysical1>,<datasize1> [,<datalogical2>,<dataphysical2>,<datasize2>...<datalogical16>,<dataphysical16>,<datasize16>] |
15262 | Invalid file size entered. All files must be at least 1 MB. |
15264 | Could not create the '%s' portion of the database. |
15266 | Cannot make '%s' database removable. |
15269 | Logical data device '%s' not created. |
15270 | You cannot specify a length for user data types based on sysname. |
15271 | Invalid @with_log parameter value. Valid values are 'true' or 'false'. |
15275 | FOREIGN KEY constraints do not have space allocated. |
15277 | The only valid @parameter_value values are 'true' or 'false'. |
15278 | Login '%s' is already mapped to user '%s' in database '%s'. |
15279 | You must add the us_english version of this message before you can add the '%s' version. |
15280 | All localized versions of this message must be dropped before the us_english version can be dropped. |
15283 | The name '%s' contains too many characters. |
15284 | The user has granted or revoked privileges to the following in the database and cannot be dropped. |
15285 | The special word '%s' cannot be used for a logical device name. |
15286 | Terminating this procedure. The @action '%s' is unrecognized. Try 'REPORT', 'UPDATE_ONE', or 'AUTO_FIX'. |
15287 | Terminating this procedure. '%s' is a forbidden value for the login name parameter in this procedure. |
15289 | Terminating this procedure. Cannot have an open transaction when this is run. |
15290 | Terminating this procedure. The Action '%s' is incompatible with the other parameter values ('%s', '%s'). |
15291 | Terminating this procedure. The %s name '%s' is absent or invalid. |
15292 | The row for user '%s' will be fixed by updating its login link to a login already in existence. |
15293 | Barring a conflict, the row for user '%s' will be fixed by updating its link to a new login. Consider changing the new password from null. |
15294 | The number of orphaned users fixed by adding new logins and then updating users was %d. |
15295 | The number of orphaned users fixed by updating users was %d. |
15298 | New login created. |
TSQL Error Codes - 15300 to 15399
Error Code | Description |
---|---|
15300 | No recognized letter is contained in the parameter value for General Permission Type (%s). Valid letters are in this set: %s . |
15301 | Collation '%s' is supported for Unicode data types only and cannot be set at either the database or server level. |
15302 | Database_Name should not be used to qualify owner.object for the parameter into this procedure. |
15303 | The "user options" config value (%d) was rejected because it would set incompatible options. |
15304 | The severity level of the '%s' version of this message must be the same as the severity level (%ld) of the us_english version. |
15305 | The @TriggerType parameter value must be 'insert', 'update', or 'delete'. |
15306 | Cannot change the compatibility level of replicated or distributed databases. |
15307 | Could not change the merge publish option because the server is not set up for replication. |
15308 | You must set database '%s' to single user mode with sp_dboption before fixing indexes on system tables. |
15311 | The file named '%s' does not exist. |
15312 | The file named '%s' is a primary file and cannot be removed. |
15318 | All fragments for database '%s' on device '%s' are now dedicated for log usage only. |
15319 | Error: DBCC DBREPAIR REMAP failed for database '%s' (device '%s'). |
15321 | There was some problem removing '%s' from sysaltfiles. |
15322 | File '%s' was removed from tempdb, and will take effect upon server restart. |
15323 | The selected index does not exist on table '%s'. |
15324 | The option %s cannot be changed for the '%s' database. |
15325 | The current database does not contain a %s named '%ls'. |
15326 | No extended stored procedures exist. |
15327 | The database is now offline. |
15328 | The database is offline already. |
15330 | There are no matching rows on which to report. |
15331 | The user '%s' cannot take the action auto_fix due to duplicate SID. |
15333 | Error: The qualified @oldname references a database (%s) other than the current database. |
15335 | Error: The @newname value '%s' is already in use as a %s name and would cause a duplicate that is not permitted. |
15336 | Object '%s' cannot be renamed because the object participates in enforced dependencies. |
15337 | Caution: sysdepends shows that other objects (views, procedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly. |
15338 | The %s was renamed to '%s'. |
15339 | Creating '%s'. |
15340 | Alias user added. |
15341 | Granted database access to '%s'. |
15354 | Usage: sp_detach_db <dbname>, [TRUE|FALSE] |
15358 | User-defined filegroups should be made read-only. |
15363 | The role '%s' already exists in the current database. |
15379 | The server option value '%s' supplied is unrecognized. |
15387 | If the qualified object name specifies a database, that database must be the current database. |
15388 | There is no user table matching the input name '%s' in the current database. |
15390 | Input name '%s' does not have a matching user table or indexed view in the current database. |
15394 | Collation '%s' is not supported by the operating system |
15395 | The qualified old name could not be found for item type '%s'. |
15398 | Only objects in the master database owned by dbo can have the startup setting changed. |
15399 | Could not change startup option because this option is restricted to objects that have no parameters. |
TSQL Error Codes - 15400 to 15499
Error Code | Description |
---|---|
15401 | Windows NT user or group '%s' not found. Check the name again. |
15402 | '%s' is not a fixed server role. |
15405 | Cannot use the reserved user or role name '%s'. |
15407 | '%s' is not a valid Windows NT name. Give the complete name: <domain\username>. |
15409 | '%s' is not a role. |
15410 | User or role '%s' does not exist in this database. |
15412 | '%s' is not a known fixed role. |
15413 | Cannot make a role a member of itself. |
15414 | Cannot set compatibility level because database has a view or computed column that is indexed. These indexes require a SQL Server compatible database. |
15415 | User is a member of more than one group. sp_changegroup is set up for backward compatibility and expects membership in one group at most. |
15416 | Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]] |
15417 | Cannot change the compatibility level of the '%s' database. |
15418 | Only members of the sysadmin role or the database owner may set the database compatibility level. |
15419 | Supplied parameter @sid should be binary(16). |
15420 | The group '%s' does not exist in this database. |
15421 | The user owns role(s) in the database and cannot be dropped. |
15422 | Application roles can only be activated at the ad hoc level. |
15423 | The password for application role '%s' has been changed. |
15424 | New role added. |
15425 | New application role added. |
15426 | You must specify a provider name with this set of properties. |
15427 | You must specify a provider name for unknown product '%ls'. |
15428 | You cannot specify a provider or any properties for product '%ls'. |
15429 | '%ls' is an invalid product name. |
15430 | Limit exceeded for number of servers. |
15431 | You must specify the @rolename parameter. |
15432 | Stored procedure '%s' can only be executed at the ad hoc level. |
15433 | Supplied parameter @sid is in use. |
15434 | Could not drop login '%s' as the user is currently logged in. |
15435 | Database successfully published. |
15436 | Database successfully enabled for subscriptions. |
15437 | Database successfully published using merge replication. |
15438 | Database is already online. |
15439 | Database is now online. |
15440 | Database is no longer published. |
15441 | Database is no longer enabled for subscriptions. |
15442 | Database is no longer enabled for merge publications. |
15443 | Checkpointing database that was changed. |
15444 | 'Disk' device added. |
15445 | 'Diskette' device added. |
15446 | 'Tape' device added. |
15447 | 'Pipe' device added. |
15449 | Type added. |
15450 | New language inserted. |
15452 | No alternate languages are available. |
15453 | us_english is always available, even though it is not in syslanguages. |
15454 | Language deleted. |
15456 | Valid configuration options are: |
15457 | Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE statement to install. |
15458 | Database removed. |
15459 | In the current database, the specified object references the following: |
15460 | In the current database, the specified object is referenced by the following: |
15461 | Object does not reference any object, and no objects reference it. |
15462 | File '%s' closed. |
15463 | Device dropped. |
15467 | Type has been dropped. |
15469 | No constraints have been defined for this object. |
15470 | No foreign keys reference this table. |
15471 | The object comments have been encrypted. |
15472 | The object does not have any indexes. |
15473 | Settable remote login options. |
15475 | The database is renamed and in single user mode. |
15476 | A member of the sysadmin role must reset the database to multiuser mode with sp_dboption. |
15477 | Caution: Changing any part of an object name could break scripts and stored procedures. |
15478 | Password changed. |
15479 | Login dropped. |
15480 | Could not grant login access to '%s'. |
15481 | Granted login access to '%s'. |
15482 | Could not deny login access to '%s'. |
15483 | Denied login access to '%s'. |
15484 | Could not revoke login access from '%s'. |
15485 | Revoked login access from '%s'. |
15486 | Default database changed. |
15487 | %s's default language is changed to %s. |
15488 | '%s' added to role '%s'. |
15489 | '%s' dropped from role '%s'. |
15490 | The dependent aliases were also dropped. |
15491 | User has been dropped from current database. |
15492 | Alias user dropped. |
15493 | Role dropped. |
15494 | The application role '%s' is now active. |
15495 | Application role dropped. |
15496 | Group changed. |
15497 | Could not add login using sp_addlogin (user = %s). Terminating this procedure. |
15498 | Inside txn_1a_, update failed. Will roll back (1a1). |
15499 | The dependent aliases were mapped to the new database owner. |
TSQL Error Codes - 15500 to 15599
Error Code | Description |
---|---|
15500 | The dependent aliases were dropped. |
15501 | Database owner changed. |
15502 | Setting database owner to SA. |
15503 | Giving ownership of all objects to the database owner. |
15504 | Deleting users except guest and the database owner from sysusers. |
15505 | Cannot change owner of object '%ls' or one of its child objects because the new owner '%ls' already has an object with the same name. |
15511 | Default bound to column. |
15512 | Default bound to data type. |
15513 | The new default has been bound to columns(s) of the specified user data type. |
15514 | Rule bound to table column. |
15515 | Rule bound to data type. |
15516 | The new rule has been bound to column(s) of the specified user data type. |
15519 | Default unbound from table column. |
15520 | Default unbound from data type. |
15521 | Columns of the specified user data type had their defaults unbound. |
15522 | Rule unbound from table column. |
15523 | Rule unbound from data type. |
15524 | Columns of the specified user data type had their rules unbound. |
15525 | sp_checknames is used to search for non 7-bit ASCII characters. |
15526 | in several important columns of system tables. The following |
15527 | columns are searched: |
15528 | In master: |
15536 | In all databases: |
15543 | Looking for non 7-bit ASCII characters in the system tables of database '%s'. |
15544 | Table.column '%s' |
15545 | The following database names contain non 7-bit ASCII characters. |
15546 | If you wish to change these names, use '%s'. |
15547 | The following logins have default database names that contain |
15548 | non 7-bit ASCII characters. If you wish to change these names use |
15549 | sp_defaultdb. |
15550 | The following servers have 'initialization file' names that contain |
15551 | non 7-bit ASCII characters. If you wish to change these names, |
15552 | use UPDATE. |
15553 | Database '%s' has no object, user, and so on |
15554 | names that contain non 7-bit ASCII characters. |
15555 | The database name provided '%s' must be the current database when executing this stored procedure. |
15564 | The following device names contain non 7-bit ASCII characters. |
15565 | The following login names contain non 7-bit ASCII characters. |
15566 | The following remote login names contain non 7-bit ASCII characters. |
15567 | The following server names contain non 7-bit ASCII characters. |
15568 | The following column and parameter names contain non 7-bit ASCII characters. |
15569 | The following index names contain non 7-bit ASCII characters. |
15570 | The following object names contain non 7-bit ASCII characters. |
15571 | The following segment names contain non 7-bit ASCII characters. |
15572 | The following data type names contain non 7-bit ASCII characters. |
15573 | The following user or role names contain non 7-bit ASCII characters. |
15574 | This object does not have any statistics. |
15575 | This object does not have any statistics or indexes. |
15576 | You cannot set network name on server '%ls' because it is not a linked SQL Server. |
15577 | Warning: A linked server that refers to the originating server is not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias. |
TSQL Error Codes - 15600 to 15699
Error Code | Description |
---|---|
15600 | An invalid parameter or option was specified for procedure '%s'. |
15601 | Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. |
15604 | Cannot drop full-text catalog '%ls' because it contains a full-text index. |
15605 | A full-text index for table '%ls' has already been created. |
15606 | You must first create a full-text index on table '%ls'. |
15607 | '%ls' is not a valid index to enforce a full-text search key. You must specify a unique, non-nullable, single-column index. |
15608 | Full-text search has already been activated for table '%ls'. |
15609 | Cannot activate full-text search for table '%ls' because no columns have been enabled for full-text search. |
15610 | You must deactivate full-text search on table '%ls' before adding columns to or removing columns from the full-text index. |
15611 | Column '%ls' of table '%ls' cannot be used for full-text search because it is not a character-based column. |
15612 | DBCC DBCONTROL error. Database was not made read-only. |
15613 | The database is now read-only. |
15614 | The database already is read-only. |
15615 | DBCC DBCONTROL error. Database was not made single user. |
15616 | The database is now single user. |
15617 | The database already is single user. |
15618 | The database is now read/write. |
15619 | The database already is read/write. |
15620 | The database is now multiuser. |
15621 | The database already is multiuser. |
15622 | No permission to access database '%s'. |
15623 | Enabling %ls option for database '%ls'. |
15624 | Disabling %ls option for database '%ls'. |
15625 | Option '%ls' not recognized for '%ls' parameter. |
15626 | You attempted to acquire a transactional application lock without an active transaction. |
15627 | sp_dboption command failed. |
15630 | Full-text search must be activated on table '%ls' before this operation can be performed. |
15631 | Full-text change tracking is currently enabled for table '%ls'. |
15632 | Full-text change tracking must be started on table '%ls' before full-text auto propagation can begin. |
15633 | Full-text auto propagation is currently enabled for table '%ls'. |
15634 | Full-text change tracking must be started on table '%ls' before the changes can be flushed. |
15635 | Cannot execute '%ls' because the database is in read-only access mode. |
15636 | Full-text catalog '%ls' cannot be populated because the database is in single-user access mode. |
15637 | Full-text index for table '%ls' cannot be populated because the database is in single-user access mode. |
15638 | Warning: Full-text index for table '%ls' cannot be populated because the database is in single-user access mode. Change tracking is stopped for this table. Use sp_fulltext_table to start change tracking. |
15639 | Warning: Table '%s' does not have the option 'text in row' enabled and has full-text indexed columns that are of type image, text, or ntext. Full-text change tracking cannot track WRITETEXT or UPDATETEXT operations performed on these columns. |
15640 | sp_fulltext_table 'start_full' must be executed on table '%ls'. Columns affecting the index have been added or dropped since the last index full population. |
15642 | The ongoing population is necessary to ensure an up-to-date index. If needed, stop change tracking, and then deactivate the full-text index population. |
15643 | Warning: This operation did not succeed on one or more tables. A table may be inactive, or a full-text index population may already be active. |
15644 | Full-text index population failed to start on this table. Execute sp_fulltext_table '%ls', '%ls' to update the index. |
15645 | Column '%ls' does not exist. |
15646 | Column '%ls' is not a computed column. |
15647 | No views with schema binding reference this table. |
TSQL Error Codes - 16800 to 16899
Error Code | Description |
---|---|
16801 | sp_dropwebtask requires at least one defined parameter @outputfile or @procname. |
16802 | sp_dropwebtask cannot find the specified task. |
16803 | sp_runwebtask requires at least one defined parameter @outputfile or @procname. |
16804 | SQL Web Assistant: Could not establish a local connection to SQL Server. |
16805 | SQL Web Assistant: Could not execute the SQL statement. |
16806 | SQL Web Assistant: Could not bind the parameter to the SQL statement. |
16807 | SQL Web Assistant: Could not obtain a bind token. |
16808 | SQL Web Assistant: Could not find the existing trigger. This could be due to encryption. |
16809 | SQL Web Assistant failed on the call to SQLGetData. |
16810 | SQL Web Assistant failed on the call to SQLFetch. |
16811 | SQL Web Assistant failed to bind a results column. |
16812 | SQL Web Assistant: The @query parameter must be specified. |
16813 | SQL Web Assistant: Parameters can be passed either by name or position. |
16814 | SQL Web Assistant: Invalid parameter. |
16815 | SQL Web Assistant: @procname is not valid. |
16816 | SQL Web Assistant: @outputfile is not valid. |
16817 | SQL Web Assistant: Could not read the given file. |
16820 | SQL Web Assistant failed because the state of the Web task in msdb..MSwebtasks is invalid. |
16821 | SQL Web Assistant: Could not open the output file. |
16822 | SQL Web Assistant: Could not open the template file. |
16823 | SQL Web Assistant: Could not allocate enough memory to satisfy this request. |
16824 | SQL Web Assistant: The template file specified in the Web task has a bad size. |
16825 | SQL Web Assistant: Could not read the template file. |
16826 | SQL Web Assistant: Could not find the specified marker for data insertion in the template file. |
16827 | SQL Web Assistant: Could not write to the output file. |
16828 | SQL Web Assistant: @tabborder must be tinyint. |
16829 | SQL Web Assistant: @singlerow must be 0 or 1. Cannot specify this parameter with @nrowsperpage. |
16830 | SQL Web Assistant: The @blobfmt parameter specification is invalid. |
16831 | SQL Web Assistant: The output file name is mandatory for every column specified in the @blobfmt parameter. |
16832 | SQL Web Assistant: Procedure called with too many parameters. |
16833 | SQL Web Assistant: @nrowsperpage must be a positive number and it cannot be used with @singlerow. |
16834 | SQL Web Assistant: Read/write operation on text, ntext, or image column failed. |
16838 | SQL Web Assistant: Could not find the table in the HTML file. |
16839 | SQL Web Assistant: Could not find the matching end table tag in the HTML file. |
16841 | SQL Web Assistant: The @datachg parameter cannot be specified with the given @whentype value. |
16842 | SQL Web Assistant: Could not find and drop the necessary trigger for updating the Web page. |
16843 | SQL Web Assistant: Could not add the necessary trigger for the @datachg parameter. There could be an existing trigger on the table with missing or encrypted text. |
16844 | SQL Web Assistant: Incorrect syntax for the @datachg parameter. |
16845 | SQL Web Assistant: @datachg must be specified for the given @whentype option. |
16846 | SQL Web Assistant: @unittype and/or @numunits must be specified for the given @whentype option. |
16847 | SQL Web Assistant: @fixedfont must be 0 or 1. |
16848 | SQL Web Assistant: @bold must be 0 or 1. |
16849 | SQL Web Assistant: @italic must be 0 or 1. |
16850 | SQL Web Assistant: @colheaders must be 0 or 1. |
16851 | SQL Web Assistant: @lastupdated must be 0 or 1. |
16852 | SQL Web Assistant: @HTMLheader must be in the range 1 to 6. |
16853 | SQL Web Assistant: @username is not valid. |
16854 | SQL Web Assistant: @dbname is not valid. |
16855 | SQL Web Assistant: @whentype must be in the range 1 to 9. |
16856 | SQL Web Assistant: @unittype must be in the range 1 to 4. |
16857 | SQL Web Assistant: @targetdate is invalid. It must be a valid date after 1900-01-01. |
16858 | SQL Web Assistant: The @targettime parameter must be between 0 and 240000. |
16859 | SQL Web Assistant: @dayflags must be 1, 2, 4, 8, 16, 32, or 64. |
16860 | SQL Web Assistant: @numunits must be greater than 0. |
16861 | SQL Web Assistant: @targetdate must be specified for the given @whentype option. |
16862 | SQL Web Assistant: @dayflags must be specified for the given @whentype option. |
16863 | SQL Web Assistant: URL specification is invalid. |
16864 | SQL Web Assistant: @blobfmt is invalid. The file must include the full path to the output_file location. |
16865 | SQL Web Assistant: URL hyperlink text column must not be of the image data type. |
16866 | SQL Web Assistant: Could not obtain the number of columns in @query. |
16867 | SQL Web Assistant: URL hyperlink text column is missing in @query. |
16868 | SQL Web Assistant failed on the call to SQLColAttribute. |
16869 | SQL Web Assistant: Columns of data type image cannot have a template. |
16870 | SQL Web Assistant: Internal error. Could not read @ parameters. |
16871 | SQL Web Assistant: Invalid @charset. Execute sp_enumcodepages for a list of character sets. |
16873 | SQL Web Assistant: Invalid @codepage. Execute sp_enumcodepages for a list of code pages. |
16874 | SQL Web Assistant: Internal error. Cannot translate to the specified code page. |
16875 | SQL Web Assistant: Translation to the desired code page is unavailable on this system. |
16876 | SQL Web Assistant: Internal error. Could not obtain COM interface ID. |
16877 | SQL Web Assistant: Internal error. Could not obtain COM language ID. |
16878 | SQL Web Assistant: Internal error. Could not initialize COM library. |
16879 | SQL Web Assistant: Internal error. Could not translate from Unicode to the specified code page. |
16880 | SQL Web Assistant: Internal error. Could not create translation object. Make sure that the file MLang.dll is in your system directory. |
16881 | SQL Web Assistant: This version is not supported on Win32s of Windows 3.1. |
16882 | SQL Web Assistant: Web task not found. Verify the name of the task for possible errors. |
16883 | SQL Web Assistant: Could not list Web task parameters. xp_readwebtask requires @procname. |
16884 | SQL Web Assistant: Procedure name is required to convert Web tasks. |
16885 | SQL Web Assistant: Could not upgrade the Web task to 7.0. The Web task will remain in 6.5 format and will need to be re-created. |
16886 | SQL Web Assistant: Could not update Web tasks system table. The Web task remains in 6.5 format. |
16887 | SQL Web Assistant: @procname parameter is missing. The parameter is required to upgrade a Web task to 7.0. |
16888 | SQL Web Assistant: Source code page is not supported on the system. Ensure @charset and @codepage language files are installed on your system. |
16889 | SQL Web Assistant: Could not send Web task row to the client. |
16890 | SQL Web Assistant: ODS error occurred. Could not send Web task parameters. |
TSQL Error Codes - 16900 to 16999
Error Code | Description |
---|---|
16901 | %hs: This feature has not been implemented yet. |
16902 | %hs: The value of parameter %hs is invalid. |
16903 | %hs procedure called with incorrect number of parameters. |
16904 | sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE. |
16905 | The cursor is already open. |
16907 | %hs is not allowed in cursor statements. |
16909 | %hs: The cursor identifier value provided (%x) is not valid. |
16911 | %hs: The fetch type %hs cannot be used with forward only cursors. |
16914 | %hs procedure called with too many parameters. |
16915 | A cursor with the name '%.*ls' already exists. |
16916 | A cursor with the name '%.*ls' does not exist. |
16917 | Cursor is not open. |
16922 | Cursor Fetch: Implicit conversion from data type %s to %s is not allowed. |
16924 | Cursorfetch: The number of variables declared in the INTO list must match that of selected columns. |
16925 | The fetch type %hs cannot be used with dynamic cursors. |
16926 | sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column. |
16927 | Cannot fetch into text, ntext, and image variables. |
16929 | The cursor is READ ONLY. |
16930 | The requested row is not in the fetch buffer. |
16931 | There are no rows in the current fetch buffer. |
16932 | The cursor has a FOR UPDATE list and the requested column to be updated is not in this list. |
16933 | The cursor does not include the table being modified or the table is not updatable through the cursor. |
16934 | Optimistic concurrency check failed. The row was modified outside of this cursor. |
16935 | No parameter values were specified for the sp_cursor-%hs statement. |
16936 | sp_cursor: One or more values parameters were invalid. |
16937 | A server cursor is not allowed on a remote stored procedure or stored procedure with more than one SELECT statement. Use a default result set or client cursor. |
16938 | sp_cursoropen/sp_cursorprepare: The statement parameter can only be a single select or a single stored procedure. |
16940 | Cannot specify UPDLOCK or TABLOCKX with READ ONLY or INSENSITIVE cursors. |
16941 | Cursor updates are not allowed on tables opened with the NOLOCK option. |
16942 | Could not generate asynchronous keyset. The cursor has been deallocated. |
16943 | Could not complete cursor operation because the table schema changed after the cursor was declared. |
16944 | Cannot specify UPDLOCK or TABLOCKX on a read-only table in a cursor. |
16945 | The cursor was not declared. |
16946 | Could not open the cursor because one or more of its tables have gone out of scope. |
16947 | No rows were updated or deleted. |
16948 | The variable '%.*ls' is not a cursor variable, but it is used in a place where a cursor variable is expected. |
16949 | The variable '%.*ls' is a cursor variable, but it is used in a place where a cursor variable is not valid. |
16950 | The variable '%.*ls' does not currently have a cursor allocated to it. |
16951 | The 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. |
16952 | A cursor variable cannot be used as a parameter to a remote procedure call. |
16953 | Remote 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. |
16954 | Executing SQL directly; no cursor. |
16955 | Could not create an acceptable cursor. |
16956 | Cursor created was not of the requested type. |
16957 | FOR UPDATE cannot be specified on a READ ONLY cursor. |
16958 | Could not complete cursor operation because the set options have changed since the cursor was declared. |
16959 | Unique table computation failed. |
16960 | You have reached the maximum number of cursors allowed. |
16961 | One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query. |
16962 | The target object type is not updatable through a cursor. |
16963 | You cannot specify scroll locking on a cursor that contains a remote table. |
16996 | %hs cannot take output parameters. |
16998 | Internal Cursor Error: A cursor work table operation failed. |
16999 | Internal Cursor Error: The cursor is in an invalid state. |
TSQL Error Codes - 17000 to 17099
Error Code | Description |
---|---|
17000 | Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ] |
17050 | The '%ls' option is ignored in this edition of SQL Server. |
17052 | %1 |
17053 | %1: Operating system error %2 encountered. |
17054 | LogEvent: Failed to report the current event. Operating system error = %1. |
17055 | %1 :%n%2 |
17059 | Operating system error %1!d!: %2!hs!. |
17065 | SQL Server Assertion: File: <%1>, line = %2!d! %nFailed Assertion = '%3' %4. |
17066 | SQL Server Assertion: File: <%1>, line=%2!d! %nFailed Assertion = '%3'. |
17067 | SQL Server Assertion: File: <%1>, line = %2!d! %n%3. |
17068 | PrintStack Request |
TSQL Error Codes - 17100 to 17199
Error Code | Description |
---|---|
17104 | Server Process ID is %1!ld!. |
17112 | Invalid command option %1!c!. |
17113 | initconfig: Error %2 opening '%1' for configuration information. |
17114 | initconfig: Error %2 reading configuration information from '%1'. |
17117 | initconfig: Number of user connections reduced to %1!ld!. |
17118 | upinit: Warning: Could not raise priority of %1 thread. |
17119 | initconfig: Number of server processes reduced to %1!ld!. |
17120 | SQL Server could not spawn %1 thread. |
17122 | initdata: Warning: Could not set working set size to %1!d! KB. |
17124 | SQL Server configured for %1 mode processing. |
17125 | Using %1 lock allocation. [%2!d!] Lock Blocks, [%3!d!] Lock Owner Blocks. |
17126 | SQL Server is ready for client connections |
17127 | initdata: No memory for kernel buffer hash table. |
17128 | initdata: No memory for kernel buffers. |
17130 | initdata: No memory for kernel locks. |
17131 | initdata: Not enough memory for descriptor hash tables. |
17132 | initdata: Not enough memory for descriptors. |
17134 | initmaster: Could not allocate process status structure (PSS). |
17138 | Could not allocate enough memory to initialize '%1'. |
17140 | Could not dispatch SQL Server by Service Control Manager. Operating system error = %1. |
17141 | Could not register Service Control Handler. Operating system error = %1. |
17142 | SQL Server has been paused. No new connections will be allowed. |
17143 | %1: Could not set Service Control Status. Operating system error = %2. |
17144 | SQL Server is disallowing new connections due to 'pause' request from Service Control Manager. |
17145 | Service Control Handler received an invalid control code = %1!d!. |
17146 | SQL Server is allowing new connections due to 'continue' request from Service Control Manager. |
17147 | SQL Server terminating because of system shutdown. |
17148 | SQL Server is terminating due to 'stop' request from Service Control Manager. |
17151 | Maximum number of pages in batch I/O is limited to %1!ld!. |
17154 | initdata: Not enough memory for procedure cache/hash table. |
17156 | initeventlog: Could not initiate the EventLog Service for the key '%1'. |
17157 | %1: Could not initialize Communication Layer. |
17160 | Could not use SQLEVN70.DLL version '%1'. SQLEVN70.DLL version '%2' was expected. |
17161 | Master device sector size is %1!d!. SQL Server cannot use the NO_BUFFERING option during I/O. |
17162 | SQL Server is starting at priority class '%1'(%2!d! %3 detected). |
17168 | SQL Server shut down because configured codepage %1!d! is not supported by the |
TSQL Error Codes - 17200 to 17299
Error Code | Description |
---|---|
17204 | %1: Could not open device %2 for virtual device number (VDN) %3!d!. |
17207 | %1: Operating system error %3 during the creation/opening of physical device %2. |
17208 | %1: File '%2' has an incorrect size (%3!d! MB, should be %4!d! MB). |
17218 | %1: Operating system error %2 on device '%3' (virtual page %4). |
17249 | %1: Negative outstanding I/O count in process ID = %2!d!. |
17252 | %1: Actual bytes transferred (%2!d!) does not match requested amount (%3!d!) on device '%4' (virtual page %5). |
17253 | The sector size for device %1 is %2!d!. SQL Server cannot use the NO_BUFFERING option during I/O on this device. |
17254 | Warning: Cannot use NO_BUFFERING option on '%1'. Operating system error %2. |
TSQL Error Codes - 17300 to 17399
Error Code | Description |
---|---|
17300 | Not enough memory for process status structure (PSS) allocation. |
17302 | The maximum limit for connections has been reached. |
17303 | freepss: Bad process status structure (PSS) value. |
17304 | Warning: Clean_process system function called from another thread. Outstanding I/O may not complete. |
17308 | %1: Process %2!d! generated an access violation. SQL Server is terminating this process. |
17309 | The current contents of process' input buffer are '%1'. |
17310 | %1: Process %2!d! generated fatal exception %3!lx! %4. SQL Server is terminating this process. |
17311 | SQL Server is aborting. Fatal exception %1!lx! caught. |
TSQL Error Codes - 17400 to 17499
Error Code | Description |
---|---|
17402 | Database '%1' set to single user mode. |
17422 | closetable: Called with null session descriptor (SDES), server process ID (SPID) %1!d!. |
17423 | closetable: Table already closed for session descriptor (SDES) %1!08lx!. |
17424 | Warning: OPEN OBJECTS parameter may be too low. |
17426 | Run sp_configure to increase the parameter value. |
17429 | The srchindex system function failed for index ID = %1!d!, sridoff = %2!d!. |
17430 | Database '%1' set to read only mode. |
TSQL Error Codes - 17500 to 17599
Error Code | Description |
---|---|
17550 | DBCC TRACEON %d, server process ID (SPID) %d. |
17551 | DBCC TRACEOFF %d, server process ID (SPID) %d. |
17557 | DBCC DBRECOVER failed for database ID %d. |
17558 | *** Bypassing recovery for database ID %d. |
17560 | DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'. |
17561 | %ls index restored for %ls.%ls. |
17569 | DBCC cannot find the library initialization function %ls. |
17570 | DBCC cannot find the function %ls in the library %ls. |
17571 | DBCC function %ls in the library %ls generated an access violation. SQL Server is terminating process %d. |
17572 | DBCC cannot free DLL %ls. SQL Server depends on this DLL to function properly. |
TSQL Error Codes - 17600 to 17699
Error Code | Description |
---|---|
17654 | Warning: Process status structure (PSS) found with open session descriptor (SDES). PSPID %1!d!, PSUID %2!d!, PCURDB %3!d!, range entry %4!d!, SDESP 0x%5!lx!, object ID %6!ld!. |
17657 | Attempting to change default collation to %1. |
17658 | SQL Server started in single user mode. Updates allowed to system catalogs. |
17660 | Starting without recovery. |
17661 | Recovering all databases but not clearing tempdb. |
17669 | Table still open. Database ID %1!d!, table ID %2!ld!. |
17674 | Login: %1 %2, server process ID (SPID): %3!d!, kernel process ID (KPID): %4!d!. |
17676 | SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. |
TSQL Error Codes - 17700 to 17799
Error Code | Description |
---|---|
17750 | Cannot load the DLL %ls, or one of the DLLs it references. Reason: %ls. |
17751 | Cannot find the function %ls in the library %ls. Reason: %ls. |
17752 | Extended procedure memory allocation failed for '%ls'. |
17753 | %.*ls can only be executed in the master database. |
TSQL Error Codes - 17800 to 17899
Error Code | Description |
---|---|
17801 | Unknown internal error value. |
17803 | Insufficient memory available. |
17804 | Invalid 'nbytes' value. |
17805 | Invalid buffer received from client. |
17807 | Invalid event '%1!ld!'. |
17808 | Invalid starting position specified. |
17809 | Could not connect. The maximum number of '%1!ld!' configured user connections are already connected. The system administrator can change the maximum to a higher value using sp_configure. |
17814 | Invalid function parameter. |
17815 | No longer waiting for client connections using Net-Library'%1!hs!'. |
17820 | Invalid data type parameter. |
17822 | Could not load Net-Library '%1!hs!'. |
17824 | Could not write to Net-Library '%1!hs!', loginname '%2!ls!', hostname '%3!ls!'. Connection closed. |
17825 | Could not close Net-Library '%1!hs!'. |
17826 | Could not set up Net-Library '%1!hs!'. |
17831 | Could not load Net-Library '%1!hs!' version '%2!hs!'. Need Net-Library version '%3!hs!' or greater. |
17832 | Connection opened but invalid login packet(s) sent. Connection closed. |
17833 | Net-Library %1!hs!' is already in use. |
17834 | Using '%1!hs!' version '%2!hs!'. |
17837 | char data type%0 |
17838 | variable-length char data type%0 |
17839 | binary data type%0 |
17840 | variable-length binary data type%0 |
17841 | 1-byte integer data type%0 |
17842 | 2-byte integer data type%0 |
17843 | 4-byte integer data type%0 |
17844 | bit data type%0 |
17845 | datetime data type%0 |
17846 | datetime data type, nulls allowed%0 |
17847 | money data type%0 |
17848 | money data type, nulls allowed%0 |
17849 | 4-byte float data type, nulls allowed%0 |
17850 | 8-byte float data type%0 |
17851 | 8-byte float data type, nulls allowed%0 |
17852 | 4-byte datetime data type, nulls allowed%0 |
17853 | 4-byte money data type%0 |
17854 | event type%0 |
17855 | done packet status field%0 |
17856 | error severity type%0 |
17857 | 4-byte integer data type, nulls allowed%0 |
17858 | image data type%0 |
17859 | text data type%0 |
17868 | numeric data type%0 |
17869 | numeric data type, nulls allowed%0 |
17870 | decimal data type%0 |
17871 | decimal data type, nulls allowed%0 |
17872 | bit data type, nulls allowed%0 |
17873 | 8000-byte variable-length binary data type%0 |
17874 | 8000-byte variable-length character data type%0 |
17875 | 8000-byte binary data type%0 |
17876 | 8000-byte character data type%0 |
17877 | 8000-byte Unicode character data type%0 |
17878 | 8000-byte Unicode variable-length character data type%0 |
17879 | Unicode text data type%0 |
17880 | uniqueidentifier data type%0 |
17881 | '%1!ls!' is an unsupported Open Data Services API. |
17882 | Error accepting connection request via Net-Library '%1!hs!'. Execution continuing. |
TSQL Error Codes - 18000 to 18099
Error Code | Description |
---|---|
18002 | Stored function '%.*ls' in the library '%.*ls' generated an access violation. SQL Server is terminating process %d. |
18052 | Error: %1!d!, Severity: %2!d!, State: %3!d!. |
18053 | Error: %1!d!, Severity: %2!d!, State: %3!d!%n%4%5. |
TSQL Error Codes - 18100 to 18199
Error Code | Description |
---|---|
18100 | Process ID %d killed by hostname %.*ls, host process ID %d. |
18113 | SQL Server shutdown after verifying system indexes. |
18124 | Default collation successfully changed. |
TSQL Error Codes - 18200 to 18299
Error Code | Description |
---|---|
18200 | %1: Backup device ID %2!d! out of range. |
18201 | ksconsole: Cannot create ConsBufMutex: %1. |
18203 | ksconsole: Cannot create %1 : %2. |
18204 | %1: Backup device '%2' failed to %3. Operating system error = %4. |
18205 | %1: Could not initialize console operation. |
18207 | %1: Null request packet. |
18208 | %1: Backup device ID %2!d! is not active. |
18209 | ksconsole: Could not send request to console client. |
18210 | %1: %2 failure on backup device '%3'. Operating system error %4. |
18211 | ksconsole: Could not receive request from console client. |
18213 | ksconsole: Console input request for type 0x%1!x!, ID 0x%2!x! failed. |
18214 | %1: Server console thread not running. |
18215 | %1: Response type 0x%2!x!, ID 0x%3!x! not found in request. |
18216 | %1: Could not access console mutex. Operating system error %2. |
18217 | %1: Type 0x%2!x! not implemented. |
18218 | %1: Incorrect number of parameters: %2!d!. |
18219 | ksconsole: Could not close console connection. |
18221 | ksconsole: Reinitializing the console. |
18223 | %1: No console client connected. Start CONSOLE.EXE. |
18225 | Tape '%1' (Family ID: %2, sequence %3) mounted on tape drive '%4'. |
18227 | Unnamed tape (Family ID: %1, sequence %2) mounted on tape drive '%3'. |
18257 | %1: Device or media does not support %2. |
18264 | Database backed up: Database: %1, creation date(time): %2(%3), pages dumped: %4!d!, first LSN: %5, last LSN: %6, number of dump devices: %9!d!, device information: (%10). |
18265 | Log backed up: Database: %1, creation date(time): %2(%3), first LSN: %4, last LSN: %5, number of dump devices: %7!d!, device information: (%8). |
18266 | Database file backed up: Database: %1, creation date(time): %2(%3), file list: (%4), pages dumped: %5!d!, number of dump devices: %8!d!, device information: (%9). |
18267 | Database restored: Database: %1, creation date(time): %2(%3), first LSN: %4, last LSN: %5, number of dump devices: %7!d!, device information: (%8). |
18268 | Log restored: Database: %1, creation date(time): %2(%3), first LSN: %4, last LSN: %5, number of dump devices: %7!d!, device information: (%8). |
18269 | Database file restored: Database: %1, creation date(time): %2(%3), file list: (%4), number of dump devices: %6!d!, device information: (%7). |
18270 | Database differential changes backed up: Database: %1, creation date(time): %2(%3), pages dumped: %4!d!, first LSN: %5, last LSN: %6, full backup LSN: %7, number of dump devices: %10!d!, device information: (%11). |
18271 | Database changes restored: Database: %1, creation date(time): %2(%3), first LSN: %4, last LSN: %5, number of dump devices: %7!d!, device information: (%8). |
18272 | I/O error on backup or restore restart-checkpoint file '%1'. Operating system error %2. The statement is proceeding but is non-restartable. |
18273 | Could not clear '%1' bitmap in database '%2' due to error %3!d!. A subsequent backup operation may be slower/larger than normal. |
18274 | Tape '%1' (Family ID: %2, sequence %3) dismounted from tape drive '%4'. |
18275 | Unnamed tape (Family ID: %1, sequence %2) dismounted from tape drive '%3'. |
18276 | Database file differential changes backed up: Database: %1, creation date(time): %2(%3), file list: (%4), pages dumped: %5!d!, number of dump devices: %8!d!, device information: (%9). |
18277 | Database file changes restored: Database: %1, creation date(time): %2(%3), file list: (%4), number of dump devices: %6!d!, device information: (%7). |
18278 | Database log truncated: Database: %1. |
TSQL Error Codes - 18400 to 18499
Error Code | Description |
---|---|
18400 | Checkpoint process is terminating due to a fatal exception. |
18450 | Login failed for user '%ls'. Reason: Not defined as a valid user of a trusted SQL Server connection. |
18451 | Login failed for user '%ls'. Only administrators may connect at this time. |
18452 | Login failed for user '%ls'. Reason: Not associated with a trusted SQL Server connection. |
18453 | Login succeeded for user '%ls'. Connection: Trusted. |
18454 | Login succeeded for user '%ls'. Connection: Non-Trusted. |
18455 | Login succeeded for user '%ls'. |
18456 | Login failed for user '%ls'. |
18457 | Login failed for user '%ls'. Reason: User name contains a mapping character or is longer than 30 characters. |
18458 | Login failed. The maximum simultaneous user count of %d licenses for this server has been exceeded. Additional licenses should be obtained and registered through the Licensing application in the Windows NT Control Panel. |
18459 | Login failed. The maximum workstation licensing limit for SQL Server access has been exceeded. |
18460 | Login failed. The maximum simultaneous user count of %d licenses for this '%ls' server has been exceeded. Additional licenses should be obtained and installed or you should upgrade to a full version. |
18461 | Login failed for user '%ls'. Reason: Server is in single user mode. Only one administrator can connect at this time. |
18482 | Could not connect to server '%ls' because '%ls' is not defined as a remote server. |
18483 | Could not connect to server '%ls' because '%ls' is not defined as a remote login at the server. |
18485 | Could not connect to server '%ls' because it is not configured for remote access. |
18490 | Maximum number of processors supported is '%1!ld!'. |
18491 | Could not start due to invalid serial number. |
18492 | The license agreement has been violated for this '%1' version of SQL Server. Cannot start. |
TSQL Error Codes - 18500 to 18599
Error Code | Description |
---|---|
18500 | Could not load startup handler DLL '%1'. |
18501 | Could not load startup handler function '%1'. |
18502 | Could not add startup handler '%1'. |
TSQL Error Codes - 18600 to 18699
Error Code | Description |
---|---|
18666 | Could not free up descriptor in rel_desclosed() system function. |
TSQL Error Codes - 18700 to 18799
Error Code | Description |
---|---|
18750 | %ls: The parameter '%ls' is invalid. |
18751 | %ls procedure called with incorrect number of parameters. |
18752 | Another log reader is replicating the database. |
18754 | Could not open table %d. |
18755 | Could not allocate memory for replication. |
18756 | Could not get replication information for table %d. |
18757 | The database is not published. |
18759 | Replication failure. File '%ls', line %d. |
18760 | Invalid %ls statement for article %d. |
18761 | Commit record at (%ls) has already been distributed. Check DBTABLE. |
18762 | Invalid begin LSN (%ls) for commit record (%ls). Check DBTABLE. |
18763 | Commit record (%ls) reports oldest active LSN as (0:0:0). |
18764 | Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information. |
18765 | Begin LSN specified for replication log scan is invalid. |
18766 | The replbeginlsn field in the DBTABLE is invalid. |
18767 | The specified begin LSN (%ls) for replication log scan occurs before replbeginlsn (%ls). |
18768 | The specified LSN (%ls) for repldone log scan occurs before the current start of replication in the log (%ls). |
18769 | The specified LSN (%ls) for repldone log scan is not a replicated commit record. |
18770 | The specified LSN (%ls) for repldone log scan is not present in the transaction log. |
18771 | Invalid storage type %d specified writing variant of type %d. |
18772 | Invalid server data type (%d) specified in repl type lookup. |
18773 | Could not locate text information records for column %d during command construction. |
18774 | The stored procedure sp_replsetoriginator must be executed within a transaction. |
18775 | The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation. |
18776 | An error occurred while waiting on the article cache access event. |
18777 | %s: Error initializing MSMQ components |
18778 | %s: Error opening Microsoft Message Queue %s |
TSQL Error Codes - 18800 to 18899
Error Code | Description |
---|---|
18800 | Warning: Index '%1' on '%2' in database '%3' may be corrupt because of expression evaluation changes in this release. Drop and re-create the index. |
18831 | ;// Database ID %d. Could not find object descriptor for object ID %ld. |
18833 | Database ID %d. Could not find clustered index on system table ID %ld. This index should exist in all databases. Run DBCC CHECKTABLE on sysindexes in the database. |
18836 | Database ID %d. Could not find object ID %ld in sysobjects. This system catalog should exist in all databases. Run DBCC CHECKTABLE on sysobjects in this database. |
18841 | Could not locate entry in sysdatabases for database '%.*ls'. No entry found with that name. |
18843 | Could not find database ID %d in sysdatabases. |
18872 | Rec_finish: getnext SCAN_NOINDEX on sysdatabases.dbid=%d failed. |
18874 | Rec_complete: Could not open controlling database (ID %d) of controlling database in multi-database transaction |
18875 | Recovering database '%.*s'. |
18876 | %d transactions rolled forward in database '%.*ls' (%d). |
18877 | %d transactions rolled back in database '%.*ls' (%d). |
18883 | ;//Database ID %d: Attempt to mark database SUSPECT. Getnext NC scan on sysobjects.dbid failed. |
18884 | ;//Database '%.*s' (ID %d). Recovery failed. Run DBCC. |
18885 | Page #%lx from table ID #%ld, database ID #%d, not found in cache. |
18886 | Page #%lx from sysindexes in database ID #%X not in cache after reading it into cache. |
18887 | Cannot recover the master database. Exiting. |
18892 | Extent ID %ld which should belong to syslogs belongs to object ID %ld. |
18894 | No more room in the transaction table. |
18895 | Transaction (%d, %d) not found in the transaction table. |
18901 | Could not build an allocation map for the database '%.*s'. Database does not have a DBINFO structure. |
TSQL Error Codes - 19000 to 19099
Error Code | Description |
---|---|
19000 | ODBC error encountered, State = %1, native error = %2, error message = %3. |
19001 | Windows NT Error encountered, %1. |
19002 | MS SQL SNMP Extension Agent starting, %1, version %2. |
19003 | MS SQL SNMP Extension Agent reconnecting. |
19004 | MS SQL SNMP Extension Agent stopping. |
19010 | RPC Net-Library listening on: %1. |
19011 | SuperSocket info: %1. |
19012 | SuperSocket Info: Bind failed on TCP port %1. |
19013 | SQL server listening on %1. |
19014 | Invalid Protocol specified for a %1 instance: %2. |
19015 | Encryption requested but no valid certificate was found. SQL Server terminating. |
TSQL Error Codes - 20000 to 20099
Error Code | Description |
---|---|
20001 | There is no nickname for article '%s' in publication '%s'. |
20002 | The filter '%s' already exists for article '%s' in publication '%s'. |
20003 | Could not generate nickname for '%s'. |
20007 | The system tables for merge replication could not be dropped successfully. |
20008 | The system tables for merge replication could not be created successfully. |
20009 | The article '%s' could not be added to the publication '%s'. |
20010 | The Snapshot Agent corresponding to the publication '%s' could not be dropped. |
20011 | Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property. |
20012 | The subscription type '%s' is not allowed on publication '%s'. |
20013 | The publication property '%s' cannot be changed when there are subscriptions on it. |
20014 | Invalid @schema_option value. |
20015 | Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. |
20016 | Invalid @subscription_type value. Valid values are 'pull' or 'anonymous'. |
20017 | The subscription on the Subscriber does not exist. |
20018 | The @optional_command_line is too long. Use an agent definition file. |
20019 | Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database. |
20020 | The article resolver supplied is either invalid or nonexistent. |
20021 | The subscription could not be found. |
20023 | Invalid @subscriber_type value. Valid options are 'local', 'global', 'anonymous', or 'repub'. |
20025 | The publication name must be unique. The specified publication name '%s' has already been used. |
20026 | The publication '%s' does not exist. |
20027 | The article '%s' does not exist. |
20028 | The Distributor has not been installed correctly. Could not enable database for publishing. |
20029 | The Distributor has not been installed correctly. Could not disable database for publishing. |
20030 | The article '%s' already exists on another publication with a different column tracking option. |
20031 | Could not delete the row because it does not exist. |
20032 | '%s' is not defined as a Subscriber for '%s'. |
20033 | Invalid publication type. |
20034 | Publication '%s' does not support '%s' subscriptions. |
20036 | The Distributor has not been installed correctly. |
20037 | The article '%s' already exists in another publication with a different article resolver. |
20038 | The article filter could not be added to the article '%s' in the publication '%s'. |
20039 | The article filter could not be dropped from the article '%s' in the publication '%s'. |
20040 | Could not drop the article(s) from the publication '%s'. |
20041 | Transaction rolled back. Could not execute trigger. Retry your transaction. |
20043 | Could not change the article '%s' because the publication has already been activated. |
20044 | The priority property is invalid for local subscribers. |
20045 | You must supply an article name. |
20046 | The article does not exist. |
20047 | You are not authorized to perform this operation. |
20049 | The priority value should not be larger than 100.0. |
20050 | The retention period must be greater than or equal to %d. |
20051 | The Subscriber is not registered. |
20054 | Current database is not enabled for publishing. |
20055 | Table '%s' cannot be published for merge replication because it has a timestamp column. |
20056 | Table '%s' cannot be republished. |
20057 | The profile name '%s' already exists for the specified agent type. |
20058 | The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge) |
20059 | The @profile_type must be 0 (System) or 1 (Custom) |
20060 | Compatibility level cannot be smaller than 60. |
20061 | The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing. |
20062 | Updating columns with the rowguidcol property is not allowed. |
20064 | Cannot drop profile. Either it is not defined or it is defined as the default profile. |
20065 | Cannot drop profile because it is in use. |
20066 | Profile not defined. |
20067 | The parameter name '%s' already exists for the specified profile. |
20068 | The article cannot be created on table '%s' because it has more than %d columns. |
20069 | Cannot validate a merge article that uses looping join filters. |
20070 | Cannot update subscription row. |
20072 | Cannot update Subscriber information row. |
20073 | Articles can be added or changed only at the Publisher. |
20074 | Only a table object can be published as a "table" article for merge replication. |
20075 | The 'status' parameter value must be either 'active' or 'unsynced'. |
20076 | The @sync_mode parameter value must be 'native' or 'character'. |
20077 | Problem encountered generating replica nickname. |
20078 | The @property parameter value must be 'sync_type', 'priority', or 'description'. |
20079 | Invalid @subscription_type parameter value. Valid options are 'push', 'pull', or 'both'. |
20081 | Publication property '%s' cannot be NULL. |
20084 | Publication '%s' cannot be subscribed to by Subscriber database '%s'. |
20086 | Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column. |
20087 | You cannot push an anonymous subscription. |
20088 | Only assign priorities that are greater than or equal to 0 and less than 100. |
20089 | Could not get license information correctly. |
20090 | Could not get version information correctly. |
20091 | sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions. |
20100 | Cannot drop Subscriber '%s'. There are existing subscriptions. |
TSQL Error Codes - 20500 to 20599
Error Code | Description |
---|---|
20500 | The updatable Subscriber stored procedure '%s' does not exist in sysobjects. |
20501 | Could not insert into sysarticleupdates using sp_articlecolumn. |
20502 | Invalid '%s' value. Valid values are 'read only', 'sync tran', 'queued tran', or 'failover'. |
20503 | Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions. |
20505 | Could not drop synchronous update stored procedure '%s' in '%s'. |
20506 | Source table '%s' not found in '%s'. |
20507 | Table '%s' not found in '%s'. |
20508 | Updatable Subscriptions: The text/ntext/image values inserted at Subscriber will be NULL. |
20509 | Updatable Subscriptions: The text/ntext/image values cannot be updated at Subscriber. |
20510 | Updatable Subscriptions: Cannot update identity columns. |
20511 | Updatable Subscriptions: Cannot update timestamp columns. |
20512 | Updatable Subscriptions: Rolling back transaction. |
20515 | Updatable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber. |
20516 | Updatable Subscriptions: Replicated data is not updatable. |
20517 | Updatable Subscriptions: Update of replica's primary key is not allowed unless published table has a timestamp column. |
20518 | Updatable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column. |
20519 | Updatable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. |
20520 | Updatable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. |
20521 | sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles. |
20522 | sp_MSmark_proc_norepl: invalid object name '%s'. |
20523 | Could not validate the article '%s'. It is not activated. |
20524 | Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast). |
20525 | Table '%s' might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s). |
20526 | Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast). |
20527 | Table '%s' passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns. |
20528 | Log Reader Agent startup message. |
20529 | Starting agent. |
20530 | Run agent. |
20531 | Detect nonlogged agent shutdown. |
20532 | Replication agent schedule. |
20533 | Replication agents checkup |
20534 | Detects replication agents that are not logging history actively. |
20535 | Removes replication agent history from the distribution database. |
20536 | Replication: agent failure |
20537 | Replication: agent retry |
20538 | Replication: expired subscription dropped |
20540 | Replication: agent success |
20541 | Removes replicated transactions from the distribution database. |
20542 | Detects and removes expired subscriptions from published databases. |
20543 | @rowcount_only parameter must be the value 0,1, or 2. 0=7.0 compatible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in version 8.0. |
20545 | Default agent profile |
20546 | Verbose history agent profile. |
20547 | Agent profile for detailed history logging. |
20548 | Slow link agent profile. |
20549 | Agent profile for low bandwidth connections. |
20550 | Windows Synchronization Manager profile |
20551 | Profile used by the Windows Synchronization Manager. |
20552 | Could not clean up the distribution transaction tables. |
20553 | Could not clean up the distribution history tables. |
20554 | The agent is suspect. No response within last %ld minutes. |
20555 | 6.x publication. |
20556 | Heartbeats detected for all running replication agents. |
20557 | Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'. |
20558 | Table '%s' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically. |
20559 | Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used. |
20560 | An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested. |
20561 | Generated expected rowcount value of %s for %s. |
20562 | User delete. |
20563 | No longer belongs in this partial. |
20564 | System delete. |
20565 | Replication: Subscriber has failed data validation |
20566 | Replication: Subscriber has passed data validation |
20567 | Agent history clean up: %s |
20568 | Distribution clean up: %s |
20569 | Expired subscription clean up |
20570 | Reinitialize subscriptions having data validation failures |
20571 | Reinitializes all subscriptions that have data validation failures. |
20572 | Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure. |
20573 | Replication: Subscription reinitialized after validation failure |
20574 | Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation. |
20575 | Subscriber '%s' subscription to article '%s' in publication '%s' passed data validation. |
20576 | Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure. |
20577 | No entries were found in msdb..sysreplicationalerts. |
20578 | Replication: agent custom shutdown |
20579 | Generated expected rowcount value of %s and expected checksum value of %s for %s. |
20580 | Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'. |
20581 | Cannot drop server '%s' because it is used as a Distributor in replication. |
20582 | Cannot drop server '%s' because it is used as a Publisher in replication. |
20583 | Cannot drop server '%s' because it is used as a Subscriber in replication. |
20584 | Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication. |
20585 | Validation Failure. Object '%s' does not exist. |
20586 | (default destination) |
20587 | Invalid '%s' value for stored procedure '%s'. |
20588 | The subscription is not initialized. Run the Distribution Agent first. |
20589 | Agent profile for replicated queued transaction reader. |
20590 | The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data transformations. |
20591 | Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows data transformations. |
20592 | 'dts horizontal partitions' and 'no dts horizontal partitions' are not valid 'status' values because the publication does not allow data transformations. |
20593 | Cannot modify publication '%s'. The sync_method cannot be changed to 'native', 'concurrent' or 'concurrent_c' because the publication has subscriptions from ODBC or OLE DB Subscribers. |
20594 | A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions. |
20595 | Skipping error signaled. |
20596 | Only '%s' or members of db_owner can drop the anonymous agent. |
20597 | Dropped %d anonymous subscription(s). |
20598 | The row was not found at the Subscriber when applying the replicated command. |
20599 | Continue on data consistency errors. |
TSQL Error Codes - 20600 to 20699
Error Code | Description |
---|---|
20600 | Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers. |
20601 | Invalid value specified for agent parameter 'SkipErrors'. |
20602 | The value specified for agent parameter 'SkipErrors' is too long. |
20603 | The agent profile cannot be used by heterogeneous Subscribers. |
20604 | You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'. |
20605 | Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot. |
20606 | Reinitialized subscription(s). |
20607 | Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing snapshot. |
20608 | Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active subscriptions. |
20609 | Cannot attach subscription file '%s'. Make sure that it is a valid subscription copy file. |
20610 | Cannot run '%s' when the Log Reader Agent is replicating the database. |
20611 | Only table or indexed view to table articles are allowed in publications that allow DTS. |
20612 | Checksum validation is not supported because the publication allows DTS. Use row count only validation. |
20613 | Validation is not supported for articles that are set up for DTS horizontal partitions. |
20614 | Validation is not supported for heterogeneous Subscribers. |
20616 | High Volume Server-to-Server Profile |
20617 | Merge agent profile optimized for the high volume server-to-server synchronization scenario. |
20618 | You must have CREATE DATABASE permission to attach a subscription database. |
20619 | Server user '%s' is not a valid user in database '%s'. Add the user account or 'guest' user account into the database first. |
20620 | The security mode specified requires the server '%s' in sysservers. Use sp_addlinkedserver to add the server. |
20621 | Cannot copy a subscription database to an existing database. |
20622 | Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode. |
20623 | You cannot validate article '%s' unless you have 'SELECT ALL' permission on table '%s'. |
TSQL Error Codes - 21000 to 21099
Error Code | Description |
---|---|
21000 | Cannot subscribe to an inactive publication. |
21001 | Cannot add a Distribution Agent at the Subscriber for a push subscription. |
21002 | The Distribution Agent for this subscription already exists (%s). |
21003 | Changing publication names is no longer supported. |
21004 | Cannot publish the database object '%s' because it is encrypted. |
21005 | For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible. |
21006 | Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpublisher. |
21007 | Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor. |
21008 | Cannot uninstall the Distributor because there are Subscribers defined. |
21009 | The specified filter procedure is already associated with a table. |
21010 | Removed %ld replicated transactions consisting of %ld statements in %ld seconds (%ld rows/sec). |
21011 | Deactivated subscriptions. |
21012 | Cannot change the 'allow_push' property of the publication to "false". There are push subscriptions on the publication. |
21013 | Cannot change the 'allow_pull' property of the publication to "false". There are pull subscriptions on the publication. |
21014 | The @optname parameter value must be 'transactional' or 'merge'. |
21015 | The replication option '%s' has been set to TRUE already. |
21016 | The replication option '%s' has been set to FALSE already. |
21017 | Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQL Server 2000 compatible binary checksum operation can be performed on this page. |
21018 | There are too many consecutive snapshot transactions in the distribution database. Run the Log Reader Agent again or clean up the distribution database. |
21021 | Drop the Distributor before you uninstall replication. |
21022 | Cannot set incompatible publication properties. The 'immediate_sync' property of a publication is dependent on the 'independent agent' property of a publication. |
21023 | '%s' is no longer supported. |
21024 | The stored procedure '%s' is already published as an incompatible type. |
21025 | The string being encrypted cannot have null characters. |
21026 | Cannot have an anonymous subscription on a publication that does not have an independent agent. |
21027 | '%s' replication stored procedures are not installed. Use sp_replicationoption to install them. |
21028 | Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication. |
21029 | Cannot drop a push subscription entry at the Subscriber unless @drop_push is 'true'. |
21030 | Names of SQL Server replication agents cannot be changed. |
21031 | 'post_script' is not supported for stored procedure articles. |
21032 | Could not subscribe because non-SQL Server Subscriber '%s' does not support 'sync tran' update mode. |
21033 | Cannot drop server '%s' as Distribution Publisher because there are databases enabled for replication on that server. |
21034 | Rows inserted or updated at the Subscriber cannot be outside the article partition. |
21035 | You have updated the Publisher property '%s' successfully. |
21036 | Another %s agent for the subscription(s) is running. |
21037 | Invalid working directory '%s'. |
21038 | Windows Authentication is not supported by the server. |
21039 | The destination owner name is not supported for publications that can have heterogeneous Subscribers. Use native mode bcp for this functionality. |
21040 | Publication '%s' does not exist. |
21041 | A remote distribution Publisher is not allowed on this server version. |
21042 | The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running on Windows NT 4.0. |
21043 | The Distributor is not installed. |
21044 | Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing. |
21045 | Cannot uninstall the Distributor because there are databases enabled for publishing or merge publishing. |
21046 | Cannot change distribution Publisher property 'distribution_db' because the remote Publisher is using the current distribution database. |
21047 | Cannot drop the local distribution Publisher because there are Subscribers defined. |
21048 | Cannot add login '%s' to the publication access list because it does not have access to the distribution server '%s'. |
21049 | The login '%s' does not have access permission on publication '%s' because it is not in the publication access list. |
21050 | Only members of the sysadmin or db_owner roles can perform this operation. |
21051 | Could not subscribe because non-SQL Server Subscriber '%s' does not support custom stored procedures. |
21052 | Queued Updating Subscriptions: write to message queue failed. |
21053 | The parameter must be one of the following: 'description', 'status', 'retention', 'sync_mode', 'allow_push', 'allow_pull', 'allow_anonymous', 'enabled_for_internet', 'centralized_conflicts', 'conflict_retention', or 'snapshot_ready'. |
21054 | Updatable Subscribers: RPC to Publisher failed. |
21055 | Invalid parameter %s specified for %s. |
21056 | The subscription to publication '%s' has expired and does not exist. |
21057 | Anonymous Subscribers cannot have updatable subscriptions. |
21058 | An updatable subscription to publication '%s' on Subscriber '%s' already exists. |
21059 | Cannot reinitialize subscriptions of non-immediate_sync publications. |
21060 | Could not subscribe because non-SQL Server Subscriber '%s' does not support parameterized statements. |
21061 | Invalid article status %d specified when adding article '%s'. |
21062 | The row size of table '%s' exceeds the replication limit of 6,000 bytes. |
21063 | Table '%s' cannot participate in updatable subscriptions because it is published for merge replication. |
21064 | The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Queue Reader Agent for subscription initialization. Try again after the (re)initialization completes. |
21070 | This subscription does not support automatic reinitialization (subscribed with the 'no sync' option). To reinitialize this subscription, you must drop and re-create the subscription. |
21071 | Cannot reinitialize article '%s' in subscription '%s:%s' to publication '%s' (subscribed with the 'no sync' option). |
21072 | The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subscription to receive data. |
21073 | The publication specified does not exist. |
21074 | The subscription has been marked inactive and must be reinitialized at the Publisher. Contact the database administrator. |
21075 | The initial snapshot for publication '%s' is not yet available. |
21076 | The initial snapshot for article '%s' is not yet available. |
21077 | Deactivated initial snapshot for anonymous publication(s). New subscriptions must wait for the next scheduled snapshot. |
21078 | Table '%s' does not exist in the Subscriber database. |
21079 | The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it. |
21080 | The 'msrepl_tran_version' column must be in the vertical partition of the article that is enabled for updatable subscriptions; it cannot be dropped. |
21081 | Server setting 'Allow triggers to be fired which fire other triggers (nested triggers)' must exist on updatable Subscribers. |
21082 | Database property 'IsRecursiveTriggersEnabled' has to be false for subscription databases at Subscribers that allow updatable subscriptions. |
21083 | Database compatibility level at immediate updating Subscribers cannot be less than 70. |
21084 | Publication '%s' does not allow anonymous subscriptions. |
21085 | The retention period must be less than the retention period for the distribution database. |
21086 | The retention period for the distribution database must be greater than the retention period of any existing non-merge publications. |
21087 | Anonymous Subscribers or Subscribers at this server are not allowed to create merge publications. |
21088 | The initial snapshot for the publication is not yet available. |
TSQL Error Codes - 21100 to 21199
Error Code | Description |
---|---|
21107 | '%ls' is not a table or view. |
21108 | This edition of SQL Server does not support transactional publications. |
21109 | The parameters @xact_seqno_start and @xact_seqno_end must be identical if @command_id is specified. |
21110 | @xact_seqno_start and @publisher_database_id must be specified if @command_id is specified. |
21111 | '%s' is not a valid parameter for the Snapshot Agent. |
21112 | '%s' is not a valid parameter for the Log Reader Agent. |
21113 | '%s' is not a valid parameter for the Distribution Agent. |
21114 | '%s' is not a valid parameter for the Merge Agent. |
21115 | '%s' is not a valid value for the '%s' parameter. The value must be a positive integer. |
21116 | '%s' is not a valid value for the '%s' parameter. The value must be 1, 2, or 3. |
21117 | '%s' is not a valid value for the '%s' parameter. The value must be 0, 1, or 2. |
21118 | '%s' is not a valid value for the '%s' parameter. The value must be greater than or equal to 0 and less than or equal to 10,000. |
21119 | '%s' is not a valid value for the '%s' parameter. The value must be a non-negative integer. |
21120 | Only members of the sysadmin fixed server role and db_owner fixed database role can drop subscription '%s' to publication '%s'. |
21121 | Only members of the sysadmin fixed server role and '%s' can drop the pull subscription to the publication '%s'. |
21122 | Cannot drop the distribution database '%s' because it is currently in use. |
21123 | The agent profile '%s' could not be found at the Distributor. |
21124 | Cannot find the table name or the table owner corresponding to the alternative table ID(nickname) '%d' in sysmergearticles. |
21125 | A table used in merge replication must have at least one non-computed column. |
21126 | Pull subscriptions cannot be created in the same database as the publication. |
21127 | Only global merge subscriptions can be added to database '%s'. |
21128 | Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. |
21129 | Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. |
21130 | Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. |
21131 | There are existing subscriptions to heterogeneous publication '%s'. To add new articles, first drop the existing subscriptions to the publication. |
21132 | Cannot create transactional subscription to merge publication '%s'. The publication type should be either transactional(0) or snapshot(1) for this operation. |
21133 | Publication '%s' is not enabled to use an independent agent. |
21134 | The specified job ID must identify a Distribution Agent or a Merge Agent job. |
21135 | Detected inconsistencies in the replication agent table. The specified job ID does not correspond to an entry in '%ls'. |
21136 | Detected inconsistencies in the replication agent table. The specified job ID corresponds to multiple entries in '%ls'. |
21137 | This procedure supports only remote execution of push subscription agents. |
21138 | The 'offload_server' property cannot be the same as the Distributor name. |
21139 | Could not determine the Subscriber name for distributed agent execution. |
21140 | Agent execution cannot be distributed to a Subscriber that resides on the same server as the Distributor. |
21141 | The @change_active flag may not be specified for articles with manual filters or views. |
21142 | The SQL Server '%s' could not obtain Windows group membership information for login '%s'. Verify that the Windows account has access to the domain of the login. |
21143 | The custom stored procedure schema option is invalid for a snapshot publication article. |
21144 | Cannot subscribe to publication of sync_type 'dump database' because the Subscriber has subscriptions to other publications. |
21145 | Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type 'dump database'. |
21146 | @use_ftp cannot be 'true' while @alt_snapshot_folder is neither NULL nor empty. |
21147 | The '%s' database is not published for merge replication. |
21148 | Both @subscriber and @subscriberdb must be specified with non-null values simultaneously, or both must be left unspecified. |
21149 | The '%s' database is not published for transactional or snapshot replication. |
21150 | Unable to determine the snapshot folder for the specified subscription because the specified Subscriber is not known to the Distributor. |
21151 | Pre- and post-snapshot commands are not supported for a publication that may support non-SQL Server Subscribers by using the character-mode bcp as the synchronization method. |
21152 | Cannot create a subscription of sync_type 'none' to a publication using the 'concurrent' or 'concurrent_c' synchronization method. |
21153 | Cannot create article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber. |
21154 | Cannot change article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber. |
21156 | The @status parameter value must be 'initiated' or 'active'. |
21157 | The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined. |
21158 | For a publication to be enabled for the Internet, the 'ftp_address' property must not be null. |
21159 | If a publication is enabled for the Internet, the 'alt_snapshot_folder' property must be non-empty. |
21160 | The @ftp_port parameter cannot be NULL. |
21161 | Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers. |
21162 | It is invalid to exclude the rowguid column for the table from the partition. |
21163 | It is not possible to add column '%s' to article '%s' because the snapshot for publication '%s' has been run. |
21164 | Column '%s' cannot be included in a vertical partition because it is neither nullable nor defined with a default value. |
21165 | Column '%s' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value. |
21166 | Column '%s' does not exist. |
21167 | The specified job ID does not represent a %s agent job for any push subscription in this database. |
21168 | Only members of the sysadmin fixed server role, members of the db_owner fixed database role, and owners of subscriptions served by the specified replication agent job can modify the agent offload settings. |
21169 | Could not identify the Publisher '%s' at the Distributor '%s'. Make sure that '%s' is registered in the sysservers table at the Distributor. |
21170 | Only a SQL Server 2000 or OLE DB Subscriber can use DTS. |
21171 | Could not find package '%s' in msdb at server '%s'. |
21172 | The publication has to be in 'character' or 'concurrent_c' bcp mode to allow DTS. |
21173 | The publication has to be 'independent_agent type' to allow DTS. |
21174 | You must use default values for @ins_cmd, @upd_cmd, and @del_cmd, and @status can be only 16 or 80 because the publication allows DTS. |
21175 | You cannot change 'ins_cmd','upd_cmd', or 'del_cmd' article properties because the publication allows DTS or queued updating option. |
21176 | Only members of the sysadmin fixed server role, db_owner fixed database role, or the creator of the subscription can change the subscription properties. |
21177 | Could not create column list because it is too long. Create the list manually. |
21178 | DTS properties cannot be set because the publication does not allow for data transformation. |
21179 | Invalid @dts_package_location parameter value. Valid options are 'Distributor' or 'Subscriber'. |
21180 | A publication that allows DTS cannot be enabled for updatable subscriptions. |
21181 | @dts_package_name can be set for push subscriptions only. |
21182 | The @agent_type parameter must be one of 'distribution', 'merge', or NULL. |
21183 | Invalid property name '%s'. |
21184 | %s parameter is incorrect: it should be '%s', '%s' or '%s'. |
21185 | The subscription is not initialized or not created for failover mode operations. |
21186 | Subscription for Publisher '%s' does not have a valid queue_id. |
21187 | The current mode is the same as the requested mode. |
21188 | Changed update mode from [%s] to [%s]. |
21189 | The queue for this subscription with queue_id = '%s' is not empty. Run the Queue Reader Agent to make sure the queue is empty before setting mode from [queued] to [immediate]. |
21190 | Overriding queue check for setting mode from [%s] to [%s]. |
21191 | Values for @ins_cmd, @upd_cmd, and @del_cmd can be only [%s], [%s] and [%s] respectively because the publication allows queued transactions. |
21192 | MSrepl_tran_version column is a predefined column used for replication and can be only of data type uniqueidentifier |
21193 | @identity_range, @pub_identity_range, or @threshold cannot be NULL when @auto_identity_support is set to TRUE. |
21194 | Cannot support identity_range_control because this table does not have an identity column. |
21195 | A valid identity range is not available. Check the data type of the identity column. |
21196 | Identity automation failed. |
21197 | Failed to allocate new identity range. |
21198 | Schema replication failed. |
21199 | This change cannot take effect until you run the snapshot again. |
TSQL Error Codes - 21200 to 21299
Error Code | Description |
---|---|
21200 | Publication '%s' does not exist. |
21201 | Dropping a column that is being used by a merge filter clause is not allowed. |
21202 | It is not possible to drop column '%s' to article '%s' because the snapshot for publication '%s' has already been run. |
21203 | Duplicate rows found in %s. Unique index not created. |
21204 | The publication '%s' does not allow subscription copy or its subscription has not been synchronized. |
21205 | The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes. |
21206 | Cannot resolve load hint for object %d because the object is not a user table. |
21207 | Cannot find source object ID information for article %d. |
21208 | This step failed because column '%s' exists in the vertical partition. |
21209 | This step failed because column '%s' does not exist in the vertical partition. |
21210 | The publication must be immediate_sync type to allow subscription copy. |
21211 | The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach it using sp_attach_subscription. |
21212 | Cannot copy subscription. Only single file subscription databases are supported for this operation. |
21213 | Non-SQL Server Subscribers cannot subscribe to publications that allow DTS without using a DTS package. |
21214 | Cannot create file '%s' because it already exists. |
21215 | An alternate synchronization partner can be configured only at the Publisher. |
21216 | Publisher '%s', publisher database '%s', and publication '%s' are not valid synchronization partners. |
21217 | Publication of '%s' data from Publisher '%s'. |
21218 | The creation_script property cannot be NULL if a schema option of 0x0000000000000000 is specified for the article. |
21219 | The specified source object must be a stored procedure object if it is published as a 'proc schema only' type article. |
21220 | Unable to add the article '%s' because a snapshot has been generated for the publication '%s'. |
21221 | The specified source object must be a view object if it is going to be as a 'view schema only' type article. |
21222 | The @schema_option parameter for a procedure or function schema article can include only the options 0x0000000000000001 or 0x0000000000002000. |
21223 | The @pre_creation_command parameter for a schema only article must be either 'none' or 'drop'. |
21224 | '%s' is not a valid property for a schema only article. |
21225 | The 'offload_server' property cannot be NULL or empty if the pull subscription agent is to be enabled for remote activation. |
21226 | The database '%s' does not have a pull subscription to the specified publication. |
21227 | The 'offload_server' property cannot be the same as the Subscriber server name. |
21228 | The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' type article. |
21229 | The only schema options available for a view schema article are: 0x0000000000000001, 0x0000000000000010, 0x0000000000000040, 0x0000000000000100, and 0x0000000000002000. |
21230 | Do not call this stored procedure for schema change because the current database is not enabled for replication. |
21231 | Automatic identity range support is useful only for publications that allow queued updating. |
21232 | Identity range values must be positive numbers that are greater than 1. |
21233 | Threshold value must be from 1 through 100. |
21234 | Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set 'identity_insert' settings at the Subscriber. |
21235 | Article property '%s' can be set only when the article uses automatic identity range management. |
21236 | The subscription(s) to Publisher '%s' does not allow subscription copy or it has not been synchronized. |
21237 | There is a push subscription to Publisher '%s'. Only pull and anonymous subscriptions can be copied. |
21238 | There is a push subscription to publication '%s'. Only pull and anonymous subscriptions can be copied. |
21239 | Cannot copy subscriptions because there is no synchronized subscription found in the database. |
21240 | The table '%s' is already published as another article with a different automatic identity support option. |
21241 | The threshold value should be from 0 through 99. |
21242 | Conflict table for article '%s' could not be created successfully. |
21243 | Publisher '%s', publication database '%s', and publication '%s' could not be added to the list of synchronization partners. |
21244 | Character mode publication does not support vertical filtering when the base table does not support column-level tracking. |
21245 | Table '%s' is not part of publication '%s'. |
21246 | This step failed because table '%s' is not part of any publication. |
21247 | Cannot create file at '%s'. Ensure the file path is valid. |
21248 | Cannot attach subscription file '%s'. Ensure the file path is valid and the file is updatable. |
21249 | OLE DB or ODBC Subscribers cannot subscribe to article '%s' in publication '%s' because the article has a timestamp column and the publication is 'allow_queued_tran' (allows queued updating subscriptions). |
21250 | Primary key column '%s' cannot be excluded from a vertical partition. |
21251 | Publisher '%s', publisher database '%s', publication '%s' could not be removed from the list of synchronization partners. |
21252 | It is invalid to remove the default Publisher '%s', publication database '%s', and publication '%s' from the list of synchronization partners |
21253 | Parameter '@add_to_active_directory' cannot be set to TRUE because Active Directory client package is not installed properly on the machine where SQL Server is running. |
21254 | The Active Directory operation on publication '%s' could not be completed bacause Active Directory client package is not installed properly on the machine where SQL Server is running. |
21255 | Column '%s' already exists in table '%s'. |
21256 | A column used in filter clause '%s' either does not exist in the table '%s' or cannot be excluded from the current partition. |
21257 | Invalid property '%s' for article '%s'. |
21258 | You must first drop all existing merge publications to add an anonymous or local subscription to database '%s'. |
21259 | Invalid property value '%s'. |
21260 | Schema replication failed because database '%s' on server '%s' is not the original Publisher of table '%s'. |
21261 | The offload server must be specified if the agent for this subscription is to be offloaded for remote execution. |
21262 | Failed to drop column '%s' from the partition because a computed column is accessing it. |
21263 | Parameter '%s' cannot be NULL or an empty string. |
21264 | Column '%s' cannot be dropped from table '%s' because it is a primary key column. |
21265 | Column '%s' cannot be dropped from table '%s' because there is a unique index accessing this column. |
21266 | Cannot publish table '%s' for both a merge publication and a publication with the queued updating option . |
21267 | Invalid value for queue type was specified. Valid values = (%s). |
21268 | Cannot change queue type while there are subscriptions to the publication. |
21269 | Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication. |
21270 | Queued snapshot publication property '%s' cannot have the value '%s'. |
21272 | Cannot clean up the meta data for publication '%s' because other publications are using one or more articles in this publication. |
21273 | You must upgrade the Subscriber to SQL Server 2000 to create updatable subscriptions to SQL Server 2000 Publishers. |
21274 | Invalid publication name '%s'. |
21275 | The schema-bound view '%ls' can be published only as 'indexed view schema only' or a log-based indexed view (transactional only) article. |
21276 | The type must be 'table' or '( view | indexed view | proc | func ) schema only'. |
21277 | The source object '%ls' must be a schema-bound view to be published as 'indexed view schema only' or a log-based indexed view article. |
21278 | The source object '%ls' must be a schema-bound view with at least a clustered index to be published as a log-based indexed view article. |
21279 | The 'schema_option' property for a merge article cannot be changed after a snapshot is generated for the publication. To change the 'schema_option' property of this page the corresponding merge publication must be dropped and re-created. |
21280 | Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at transaction level. |
21281 | Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level. |
21282 | @identity_range, @pub_identity_range, and @threshold must be NULL when @auto_identity_support is set to FALSE. |
21283 | Column '%s' of table '%s' cannot be excluded from a vertical partition because there is a computed column that depends on it. |
21284 | Failed to drop column '%s' from table '%s'. |
21285 | Failed to add column '%s' to table '%s'. |
21286 | Conflict table '%s' does not exist. |
21287 | The specified @destination_folder is not a valid path of an existing folder. |
21288 | Could not create the snapshot directory structure in the specified @destination_folder. |
21289 | Either the snapshot files have not been generated or they have been cleaned up. |
21290 | Identity range value is too large for the data type of the identity column. |
21291 | The specified automatic identity support parameters conflict with the settings in another article. |
21292 | Object '%s' cannot be published twice in the same publication. |
21293 | Warning: adding updatable subscription for article '%s' may cause data inconsistency as the source table is already subscribed to '%s' |
21294 | Either @publisher (and @publisher_db) or @subscriber (and @subscriber_db) must be specified, but both cannot be specified. |
21295 | Publication '%s' does not contain any article that uses automatic identity range management. |
21296 | Parameter @resync_type must be either 0, 1, 2. |
21297 | Invalid resync type. No validation has been performed for this subscription. |
21298 | Failed to resynchronize this subscription. |
21299 | Invalid Subscriber partition validation expression '%s'. |
TSQL Error Codes - 21300 to 21399
Error Code | Description |
---|---|
21300 | The resolver information was specified without specifying the resolver to be used for article '%s'. The default resolver will be used. |
21301 | The resolver information should be specified while using the '%s' resolver. |
21302 | The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%s' resolver. |
21303 | The article '%s' should enable column tracking to use the '%s' resolver. The default resolver will be used to resolve conflicts on this page. |
21304 | The merge triggers could not be created on the table '%s'. |
21305 | The schema change information could not be updated at the subscription database. |
21306 | The copy of the subscription could not be made because the subscription to publication '%s' has expired. |
21307 | The subscription could not be attached because the subscription to publication '%s' has expired. |
21308 | Rowcount validation profile. |
21309 | Profile used by the Merge Agent to perform rowcount validation. |
21310 | Rowcount and checksum validation profile. |
21311 | Profile used by the Merge Agent to perform rowcount and checksum validation. |
21312 | Cannot change this publication property because there are active subscriptions to this publication. |
21313 | Subscriber partition validation expression must be NULL for static publications. |
21314 | There must be one and only one of '%s' and '%s' that is not NULL. |
21315 | Failed to adjust Publisher identity range for table '%s'. |
21316 | Failed to adjust Publisher identity range for publication '%s'. |
21317 | A push subscription to the publication '%s' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. |
21318 | Table '%s' must have at least one column that is included in the vertical partition. |
21319 | Could not find the Snapshot Agent command line for the specified publication. |
21320 | This version of the Publisher cannot use a SQL Server 7.0 Distributor. |
21321 | The parameter @dynamic_snapshot_location cannot be an empty string. |
21323 | A dynamic snapshot job can be scheduled only for a publication with dynamic filtering enabled. |
21324 | A Snapshot Agent must be added for the specified publication before a dynamic snapshot job can be scheduled. |
21325 | Could not find the Snapshot Agent ID for the specified publication. |
21326 | Could not find the dynamic snapshot job with a '%ls' of '%ls' for the specified publication. |
21327 | '%ls' is not a valid dynamic snapshot job name. |
21328 | The specified dynamic snapshot job name '%ls' is already in use. Try the operation again with a different job name. |
21329 | Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_snapshot_jobname, can be specified with a nondefault value. |
21330 | Failed to create a sub-directory under the replication working directory.(%ls) |
21331 | Failed to copy user script file to the Distributor.(%ls) |
21332 | Failed to retrieve information about the publication : %ls. Check the name again. |
21333 | Protocol error. Message indicates a generation has disappeared. |
21334 | Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant |
21335 | Warning: column '%s' already exists in the vertical partition already. |
21336 | Warning: column '%s' does not exist in the vertical partition. |
21337 | Invalid @subscriber_type value. Valid options are 'local' and 'global'. |
21338 | Cannot drop article '%s' from publication '%s' because its snapshot has been run and this publication could have active subscriptions. |
21339 | Warning: the publication uses a feature that is only supported only by Ssubscribers running '%s' or higher. |
21340 | On Demand user script cannot be applied to the snapshot publication. |
21341 | @dynamic_snapshot_location cannot be a non-empty string while @alt_snapshot_folder is neither empty nor null. |
21342 | @dynamic_snapshot_location cannot be a non-empty string while @use_ftp is 'true'. |
21343 | Could not find stored procedure '%s'. |
21344 | Invalid value specified for %ls parameter. |
21345 | Excluding the last column in the partition is not allowed. |
21346 | Failed to change the owner of '%s' to '%s'. |
21347 | Column '%s' cannot be excluded from the vertical partitioning because there is a unique index accessing this column. |
21348 | Invalid property name '%s'. |
21349 | Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because decentralized conflict logging is designated. |
21350 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because a compressed snapshot is used. |
21351 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because vertical filters are being used. |
21352 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because schema replication is performed. |
21353 | Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide reinitialization is performed. |
21354 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because publication wide reinitialization is performed. |
21355 | Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because merge metadata cleanup task is performed. |
21356 | Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide validation task is performed. |
21357 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because data types new in SQL Server 2000 exist in one of its articles. |
21358 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because at least one timestamp column exists in one of its articles.. |
21359 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because automatic identity ranges are being used. |
21360 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because a new article has been added to the publication after its snapshot has been generated. |
21361 | The specified @agent_jobid is not a valid job id for a '%s' agent job. |
21362 | Merge filter '%s' does not exist. |
21363 | Failed to add publication '%s' to Active Directory. %s |
21364 | Could not add article '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. |
21365 | Could not add article '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reintialize the active subscriptions. |
21366 | Could not add filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. |
21367 | Could not add filter '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reintialize the active subscriptions. |
21368 | The specified offload server name contains the invalid character '%s'. |
21369 | Could not remove publication '%s' from Active Directory. |
21370 | The resync date specified '%s' is not a valid date. |
21371 | Could not propagate the change on publication '%s' to Active Directory. |
21372 | Cannot drop filter '%s' from publication '%s' because its snapshot has been run and this publication could have active subscriptions. |
21373 | Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available. |
21374 | Upgrading distribution settings and system objects in database %s. |
21375 | Upgrading publication settings and system objects in database %s. |
21376 | Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available. |
21377 | Upgrading subscription settings and system objects in database %s. |
21378 | Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again. |
21379 | Cannot drop article '%s' from publication '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. |
21380 | Cannot add identity column without forcing reinitialization. Set @force_reinit_subscription to 1 to force reinitialization. |
21381 | Cannot add (drop) column to table '%s' because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subscription to 1 to force reinitialization. |
21382 | Cannot drop filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. |
21383 | Cannot enable a merge publication on this server because the working directory of its Distributors is not using a UNC path. |
21384 | The specified subscription does not exist or has not been synchronized yet. |
21385 | Snapshot failed to process publication '%s'. Possibly due to active schema change activity. |
21386 | Schema change failed on publication '%s'. Possibly due to active snapshot or other schema change activity. |
21387 | The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider using the default mechanism instead of the dynamic snapshot for initializing the specified subscription. |
21388 | The concurrent snapshot for publication '%s' has not been activated by the Log Reader Agent. |
21389 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because column-level collation is scripted out with the article schema creation script. |
21390 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because extended properties are scripted out with the article schema creation script. |
21391 | Warning: only Subscribers running SQL Server 2000 can synchronize with publication '%s' because it contains schema-only articles. |
21392 | Row filter(%s) is invalid for column partition(%s) for article '%s' in publication '%s'. |
21393 | Dropping row filter(%s) for article '%s' in '%s'. Reissue sp_articlefilter and sp_articleview to create a row filter. |
21394 | Invalid schema option specified for Queued updating publication. Need to set the schema option to include DRI constraints. |
21395 | This column cannot be included in a transactional publication because the column ID is greater than 255. |
21396 | The subscription is marked inactive and must be dropped and re-created. |
TSQL Error Codes - 21400 to 21499
Error Code | Description |
---|---|
21400 | Article property must be changed at the original Publisher of article '%s'. |
21401 | Article name cannot be 'all'. |
21402 | Incorrect value for parameter '%s'. |
21403 | The 'max_concurrent_dynamic_snapshots' publication property must be greater than or equal to zero. |
21404 | '%s' is not a valid value for the '%s' parameter. The value must be a positive integer greater than 300 or 0. |
21405 | '%s' is not a valid value for the '%s' parameter. The value must be an integer greater than or equal to %d. |
21406 | '%s' is not a valid value for the '%s' parameter. The value must be 0 or 1. |
21413 | Failed to acquire the application lock indicating the front of the queue. |
21414 | Unexpected failure acquiring application lock. |
21415 | Unexpected failure releasing application lock. |
21416 | Property '%s' of article '%s' cannot be changed. |
21417 | Having a queue timeout value of over 12 hours is not allowed. |
21418 | Failed to add column '%s' to table '%s' because of metadata overflow. |
21419 | Filter '%s' of article '%s' cannot be changed. |
21420 | Subscription property '%s' cannot be changed. |
21421 | Article '%s' cannot be dropped because there are other articles using it as a join article. |
TSQL Error Codes - 21500 to 21599
Error Code | Description |
---|---|
21500 | Invalid subscription type is specified. A subscription to publication '%s' already exists in the database with a different subscription type. |
21501 | The supplied resolver information does not specify a valid column name to be used for conflict resolution by '%s'. |
21502 | The publication '%s' does not allow the subscription to synchronize to an alternate synchronization partner. |
21503 | Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes have completed. |
21504 | Cleanup of merge meta data at republisher '%s'.'%s' could not be performed because merge processes are propagating changes to the republisher. All subscriptions to this republisher must be reinitialized. |
21505 | Changes to publication '%s' cannot be merged because it has been marked inactive. |
21506 | sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge meta data cleanup. |
21507 | All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data cleanup. |
21508 | Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes have completed. |
21509 | Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed after all republishers have quiesced their changes. |
21510 | Data changes are not allowed while cleanup of merge meta data is in progress. |
21511 | Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row. |