Database Engine events and errors

Article
12/30/2022
908 minutes to read

The table contains error message numbers and the description, which is the text of the error message from the sys.messages catalog view. Where applicable, the error number is a link to further information.

This list is not exhaustive. For a full list of all errors, query the sys.messages catalog view with the following query:

SELECT message_id AS Error,
    severity AS Severity,
    [Event Logged] = CASE is_event_logged
        WHEN 0 THEN 'No' ELSE 'Yes'
        END,
    [text] AS [Description]
FROM sys.messages
WHERE language_id = 1040 /* replace 1040 with the desired language ID, such as 1033 for US English*/
ORDER BY message_id;

Errors 0 to 999

Error	Severity	Event Logged	Description
21	20	No	Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
101	15	No	Query not allowed in Wait for.
102	15	No	Incorrect syntax near '%.*ls'.
103	15	No	The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d.
104	15	No	ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator.
105	15	No	Unclosed quotation mark after the character string '%.*ls'.
106	16	No	Too many table names in the query. The maximum allowable is %d.
107	15	No	The column prefix '%.*ls' does not match with a table name or alias name used in the query.
108	15	No	The ORDER BY position number %ld is out of range of the number of items in the select list.
109	15	No	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	15	No	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	15	No	'%ls' must be the first statement in a query batch.
112	15	No	Variables are not allowed in the %ls statement.
113	15	No	Missing end comment mark '*/'.
114	15	No	Browse mode is invalid for a statement that assigns values to a variable.
115	15	No	The FOR UPDATE clause is invalid for statements containing set operators.
116	15	No	Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
117	15	No	The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
119	15	No	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	15	No	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	15	No	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	15	No	The %ls option is allowed only with %ls syntax.
123	15	No	Batch/procedure exceeds maximum length of %d characters.
124	15	No	CREATE PROCEDURE contains no statements.
125	15	No	Case expressions may only be nested to level %d.
126	15	No	Invalid pseudocolumn "%.*ls".
127	15	No	A TOP N value may not be negative.
128	15	No	The name "%.*s" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.
129	15	No	Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
130	16	No	Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
131	15	No	The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d).
132	15	No	The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure.
133	15	No	A GOTO statement references the label '%.*ls' but the label has not been declared.
134	15	No	The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure.
135	15	No	Cannot use a BREAK statement outside the scope of a WHILE statement.
136	15	No	Cannot use a CONTINUE statement outside the scope of a WHILE statement.
137	15	No	Must declare the scalar variable "%.*ls".
138	15	No	Correlation clause in a subquery not permitted.
139	15	No	Cannot assign a default value to a local variable.
140	15	No	Can only use IF UPDATE within a CREATE TRIGGER statement.
141	15	No	A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
142	15	No	Incorrect syntax for definition of the '%ls' constraint.
143	15	No	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	15	No	Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
145	15	No	ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
146	15	No	Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
147	15	No	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	15	No	Incorrect time syntax in time string '%.*ls' used with WAITFOR.
149	15	No	Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax.
150	15	No	Both terms of an outer join must contain columns.
151	15	No	'%.*ls' is an invalid money value.
152	15	No	The same large data placement option "%.*ls" has been specified twice.
153	15	No	Invalid usage of the option %.*ls in the %ls statement.
154	15	No	%S_MSG is not allowed in %S_MSG.
155	15	No	'%.*ls' is not a recognized %ls option.
156	15	No	Incorrect syntax near the keyword '%.*ls'.
157	15	No	An aggregate may not appear in the set list of an UPDATE statement.
158	15	No	An aggregate may not appear in the OUTPUT clause.
159	15	No	Must specify the table name and index name for the DROP INDEX statement.
160	15	No	Rule does not contain a variable.
161	15	No	Rule contains more than one variable.
162	15	No	Invalid expression in the TOP clause.
163	15	No	The compute by list does not match the order by list.
164	15	No	Each GROUP BY expression must contain at least one column that is not an outer reference.
165	16	No	Privilege %ls may not be granted or revoked.
166	15	No	'%ls' does not allow specifying the database name as a prefix to the object name.
167	15	No	Cannot create %S_MSG on a temporary object.
168	15	No	The floating point value '%.*ls' is out of the range of computer representation (%d bytes).
169	15	No	A column has been specified more than once in the order by list. Columns in the order by list must be unique.
171	15	No	Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements.
172	15	No	Cannot use HOLDLOCK in browse mode.
173	15	No	The definition for column '%.*ls' must include a data type.
174	15	No	The %.*ls function requires %d argument(s).
175	15	No	An aggregate may not appear in a computed column expression or check constraint.
176	15	No	The FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement to be allowed.
177	15	No	The IDENTITY function can only be used when the SELECT statement has an INTO clause.
178	15	No	A RETURN statement with a return value cannot be used in this context.
179	15	No	Cannot use the OUTPUT option when passing a constant to a stored procedure.
180	15	No	There are too many parameters in this %ls statement. The maximum number is %d.
181	15	No	Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
182	15	No	Table and column names must be supplied for the READTEXT or WRITETEXT utility.
183	15	No	The scale (%d) for column '%.*ls' must be within the range %d to %d.
184	16	No	DEFAULT cannot be specified more than once for filegroups of the same content type.
185	15	No	Data stream is invalid for WRITETEXT statement in bulk form.
186	15	No	Data stream missing from WRITETEXT statement.
187	16	No	The valid range for MAX_QUEUE_READERS is 0 to 32767.
188	15	No	Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.
189	15	No	The %ls function requires %d to %d arguments.
190	15	No	An invalid date or time was specified in the statement.
191	15	No	Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
192	16	No	The scale must be less than or equal to the precision.
193	15	No	The object or column name starting with '%.*ls' is too long. The maximum length is %d characters.
194	15	No	A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
195	15	No	'%.*ls' is not a recognized %S_MSG.
196	15	No	SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.
197	15	No	EXECUTE cannot be used as a source when inserting into a table variable.
198	15	No	Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.
199	15	No	An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
201	16	No	Procedure or function '%.ls' expects parameter '%.ls', which was not supplied.
202	16	No	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	16	No	The name '%.*ls' is not a valid identifier.
204	20	Yes	Normalization error in node %ls.
205	16	No	All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.
206	16	No	Operand type clash: %ls is incompatible with %ls
207	16	No	Invalid column name '%.*ls'.
208	16	No	Invalid object name '%.*ls'.
209	16	No	Ambiguous column name '%.*ls'.
210	16	No	Conversion failed when converting datetime from binary/varbinary string.
211	23	Yes	Possible schema corruption. Run DBCC CHECKCATALOG.
212	16	No	Expression result length exceeds the maximum. %d max, %d found.
213	16	No	Column name or number of supplied values does not match table definition.
214	16	No	Procedure expects parameter '%ls' of type '%ls'.
215	16	No	Parameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
216	16	No	Parameters were not supplied for the function '%.*ls'.
217	16	No	Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
218	16	No	Could not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission.
219	16	No	The type '%.*ls' already exists, or you do not have permission to create it.
220	16	No	Arithmetic overflow error for data type %ls, value = %ld.
221	10	No	FIPS Warning: Implicit conversion from %ls to %ls.
222	16	No	The base type "%.*ls" is not a valid base type for the alias data type.
223	11	No	Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
224	11	No	Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
225	16	No	The parameters supplied for the %ls "%.*ls" are not valid.
226	16	No	%ls statement not allowed within multi-statement transaction.
227	15	No	%.*ls is not a valid function, property, or field.
228	15	No	Method '%.ls' of type '%.ls' in assembly '%.*ls' does not return any value.
229	14	No	The %ls permission was denied on the object '%.ls', database '%.ls', schema '%.*ls'.
230	14	No	The %ls permission was denied on the column '%.ls' of the object '%.ls", database '%.ls', schema '%.ls'.
231	11	No	No such default. ID = %ld, database ID = %d.
232	16	No	Arithmetic overflow error for type %ls, value = %f.
233	16	No	The column '%.ls' in table '%.ls' cannot be null.
233			A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
234	16	No	There is insufficient result space to convert a money value to %ls.
235	16	No	Cannot convert a char value to money. The char value has incorrect syntax.
236	16	No	The conversion from char data type to money resulted in a money overflow error.
237	16	No	There is insufficient result space to convert a money value to %ls.
239	16	No	Duplicate common table expression name '%.*ls' was specified.
240	16	No	Types don't match between the anchor and the recursive part in column "%.ls" of recursive query "%.ls".
241	16	No	Conversion failed when converting date and/or time from character string.
242	16	No	The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.
243	16	No	Type %.*ls is not a defined system type.
244	16	No	The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column.
245	16	No	Conversion failed when converting the %ls value '%.*ls' to data type %ls.
246	16	No	No anchor member was specified for recursive query "%.*ls".
247	16	No	An anchor member was found in the recursive part of recursive query "%.*ls".
248	16	No	The conversion of the %ls value '%.*ls' overflowed an int column.
249	16	No	The type "%ls" is not comparable. It cannot be used in the %ls clause.
251	16	No	Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
252	16	No	Recursive common table expression '%.*ls' does not contain a top-level UNION ALL operator.
253	16	No	Recursive member of a common table expression '%.*ls' has multiple recursive references.
254	16	No	Prefixed columns are not allowed in the column list of a PIVOT operator.
255	16	No	Pseudocolumns are not allowed in the column list of a PIVOT operator.
256	16	No	The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
257	16	No	Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
258	15	No	Cannot call methods on %ls.
259	16	No	Ad hoc updates to system catalogs are not allowed.
260	16	No	Disallowed implicit conversion from data type %ls to data type %ls, table '%.ls', column '%.ls'. Use the CONVERT function to run this query.
261	16	No	'%.*ls' is not a recognized function.
262	16	No	%ls permission denied in database '%.*ls'.
263	16	No	Must specify table to select from.
264	16	No	The column name '%.ls' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name '%.ls' may appear twice in the view definition.
265	16	No	The column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument.
266	16	No	Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld.
267	16	No	Object '%.*ls' cannot be found.
268	16	No	Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
270	16	No	Object '%.*ls' cannot be modified.
271	16	No	The column "%.*ls" cannot be modified because it is either a computed column or is the result of a UNION operator.
272	16	No	Cannot update a timestamp column.
273	16	No	Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.
275	16	No	Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.
276	16	No	Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.
277	16	No	The column "%.*ls" is specified multiple times in the column list of the UNPIVOT operator.
278	16	No	The text, ntext, and image data types cannot be used in a GROUP BY clause.
279	16	No	The text, ntext, and image data types are invalid in this subquery or aggregate expression.
280	16	No	Only base table columns are allowed in the TEXTPTR function.
281	16	No	%d is not a valid style number when converting from %ls to a character string.
282	10	No	The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
283	16	No	READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.
284	16	No	Rules cannot be bound to text, ntext, or image data types.
285	16	No	The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.
286	16	No	The logical tables INSERTED and DELETED cannot be updated.
287	16	No	The %ls statement is not allowed within a trigger.
288	16	No	The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
290	16	No	Invalid EXECUTE statement using object "%ls", method "%ls".
291	16	No	CAST or CONVERT: invalid attributes specified for type '%.*ls'
292	16	No	There is insufficient result space to convert a smallmoney value to %ls.
293	16	No	Cannot convert char value to smallmoney. The char value has incorrect syntax.
294	16	No	The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
295	16	No	Conversion failed when converting character string to smalldatetime data type.
297	16	No	The user does not have permission to perform this action.
300	14	No	%ls permission was denied on object '%.ls', database '%.ls'.
301	16	No	Query contains an outer-join request that is not permitted.
302	16	No	The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.
303	16	No	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.
304	16	No	'%d' is out of range for index option '%.*ls'. See sp_configure option '%ls' for valid values.
305	16	No	The XML data type cannot be compared or sorted, except when using the IS NULL operator.
306	16	No	The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
307	16	No	Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist.
308	16	No	Index '%.ls' on table '%.ls' (specified in the FROM clause) does not exist.
309	16	No	Cannot use index "%.ls" on table "%.ls" in a hint. XML indexes are not allowed in hints.
310	15	No	The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d.
311	16	No	Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables.
312	16	No	Cannot reference text, ntext, or image columns in a filter stored procedure.
313	16	No	An insufficient number of arguments were supplied for the procedure or function %.*ls.
314	16	No	Cannot use GROUP BY ALL with the special tables INSERTED or DELETED.
315	16	No	Index "%.ls" on table "%.ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
316	16	No	The index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
317	16	No	Table-valued function '%.*ls' cannot have a column alias.
318	16	No	The table (and its columns) returned by a table-valued method need to be aliased.
319	16	No	Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
320	16	No	The compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal.
321	15	No	%.*ls is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90.
322	15	No	The variable "%.*ls" is specified in the OPTIMIZE FOR clause, but is not used in the query.
323	16	No	The 'COMPUTE' clause is not allowed in a statement containing an INTERSECT or EXCEPT operator.
324	15	No	The 'ALL' version of the %.*ls operator is not supported.
325	15	No	Incorrect syntax near '%.*ls'. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
326	16	No	Multi-part identifier '%.ls' is ambiguous. Both columns '%.ls' and '%.*ls' exist.
327	16	No	Function call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist.
328	16	No	A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables.
329	16	No	Each GROUP BY expression must contain at least one column reference.
330	15	No	The target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression.
331	15	No	The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled triggers.
332	15	No	The target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint '%ls'.
333	15	No	The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule '%ls'.
334	15	No	The target table '%.*ls' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.
335	16	No	Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name '%.*ls' without parameters instead.
336	15	No	Incorrect syntax near '%.*ls'. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon.
337	10	No	Warning: the floating point value '%.*ls' is too small. It will be interpreted as 0.
338	16	No	READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.
339	16	No	DEFAULT or NULL are not allowed as explicit identity values.
340	16	No	Cannot create the trigger "%.ls" on view "%.ls". AFTER triggers cannot be created on views.
341	16	No	Replication filter procedures may not contain columns of large object, large value, XML or CLR type.
342	16	No	Column "%.ls" is not allowed in this context, and the user-defined function or aggregate "%.ls" could not be found.
343	15	No	Unknown object type '%.*ls' used in a CREATE, DROP, or ALTER statement.
344	16	No	Remote function reference '%.ls' is not allowed, and the column name '%.ls' could not be found or is ambiguous.
345	16	No	Function '%.*ls' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.
346	15	No	The parameter "%.*ls" cannot be declared READONLY since it is not a table-valued parameter.
347	16	No	The table-valued parameter "%.*ls" cannot be declared as an OUTPUT parameter.
348	16	No	The table variable "%.*ls" cannot be passed to a stored procedure with the OUTPUT option.
349	16	No	The procedure "%.ls" has no parameter named "%.ls".
350	16	No	The column "%.*ls" does not have a valid data type. A column cannot be of a user-defined table type.
351	16	No	Column, parameter, or variable %.ls. : Cannot find data type %.ls.
352	15	No	The table-valued parameter "%.*ls" must be declared with the READONLY option.
353	16	No	Function '%.*ls' is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound.
354	15	No	The target '%.*ls' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
355	15	No	The target table '%.*ls' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
356	15	No	The target table '%.*ls' of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint '%ls'.
357	15	No	The target table '%.*ls' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule '%ls'.
358	15	No	The target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'.
359	15	No	The target '%.*ls' of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used.
360	15	No	The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both.
361	16	No	The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns.
401	16	No	Unimplemented statement or expression %ls.
402	16	No	The data types %s and %s are incompatible in the %s operator.
403	16	No	Invalid operator for data type. Operator equals %ls, type equals %ls.
404	16	No	The column reference "inserted.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement.
405	16	No	A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.
406	16	No	%ls cannot be used in the PIVOT operator because it is not invariant to NULLs.
407	16	No	Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.
408	16	No	A constant expression was encountered in the ORDER BY list, position %i.
411	16	No	COMPUTE clause #%d, aggregate expression #%d is not in the select list.
412	16	No	The column "%.*ls" is not updatable because it is derived or constant.
413	16	No	Correlated parameters or sub-queries are not supported by the inline function "%.*ls".
414	16	No	UPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger.
415	16	No	DELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger.
416	16	No	The service queue "%.*ls" cannot be directly updated.
417	16	No	TOP is not allowed in an UPDATE or DELETE statement against a partitioned view.
418	16	No	Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'.
421	16	No	The %ls data type cannot be selected as DISTINCT because it is not comparable.
422	16	No	Common table expression defined but not used.
423	16	No	Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls".
424	16	No	Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column "%.ls", table "%.ls", in the %ls statement.
425	16	No	Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'.
426	16	No	The length %d of the receiving variable is less than the length %d of the column '%.*ls'.
427	20	Yes	Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.
428	16	No	Insert bulk cannot be used in a multi-statement batch.
432	16	No	Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls".
434	16	No	Function '%ls' is not allowed in the OUTPUT clause.
435	16	No	Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column "%.ls", table "%.ls", in the %ls statement.
438	16	No	Xml data type methods are not allowed in rules. The error occurred at table "%.*ls".
440	16	No	Internal query compilation error. The stack overflow could not be handled.
441	16	No	Cannot use the '%ls' function on a remote data source.
442	16	No	The NEST argument must be a column reference. Expressions are not allowed.
443	16	No	Invalid use of a side-effecting operator '%s' within a function.
444	16	No	Select statements included within a function cannot return data to a client.
445	16	No	COLLATE clause cannot be used on expressions containing a COLLATE clause.
446	16	No	Cannot resolve collation conflict for %ls operation.
447	16	No	Expression type %ls is invalid for COLLATE clause.
448	16	No	Invalid collation '%.*ls'.
449	16	No	Collation conflict caused by collate clauses with different collation '%.ls' and '%.ls'.
450	16	No	Code page translations are not supported for the text data type. From: %d To: %d.
451	16	No	Cannot resolve collation conflict for column %d in %ls statement.
452	16	No	COLLATE clause cannot be used on user-defined data types.
453	16	No	Collation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level.
454	16	No	The UNNEST argument must be a nested table column.
455	16	No	The last statement included within a function must be a return statement.
456	16	No	Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict.
457	16	No	Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict.
458	16	No	Cannot create the SELECT INTO target table "%.ls" because the xml column "%.ls" is typed with a schema collection "%.ls" from database "%.ls". Xml columns cannot refer to schemata across databases.
459	16	No	Collation '%.*ls' is supported on Unicode data types only and cannot be applied to char, varchar or text data types.
460	16	No	DISTINCT operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
461	16	No	TOP operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
462	16	No	Outer join is not allowed in the recursive part of a recursive common table expression '%.*ls'.
463	16	No	Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'.
464	16	No	Functions with side effects are not allowed in the recursive part of a recursive common table expression '%.*ls'.
465	16	No	Recursive references are not allowed in subqueries.
466	16	No	UNION operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
467	16	No	GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'.
468	16	No	Cannot resolve the collation conflict between "%.ls" and "%.ls" in the %ls operation.
469	16	No	An explicit column list must be specified for target table '%.*ls' when table hint KEEPIDENTITY is used and the table contains an identity column.
470	16	No	The synonym "%.ls" referenced synonym "%.ls". Synonym chaining is not allowed.
471	16	No	Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.
472	16	No	Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.
473	16	No	The incorrect value "%.*ls" is supplied in the PIVOT operator.
474	16	No	Unable to load the computed column definitions for table "%.*ls".
475	16	No	Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.
476	16	No	Invalid PERCENT tablesample size "%f" for table "%.*ls". The PERCENT tablesample size must be between 0 and 100.
477	16	No	Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer.
478	16	No	The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.
479	16	No	Invalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0.
480	16	No	The TABLESAMPLE clause cannot be used with the table function "%.*ls".
481	16	No	The TABLESAMPLE clause cannot be used with the linked server table "%.*ls".
482	16	No	Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.
483	16	No	The OUTPUT clause cannot be used in an INSERT...EXEC statement.
484	16	No	Cannot declare more than %d local variables.
485	16	No	Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column "%.ls" is typed with the schema collection "%.ls", which is registered in database "%.*ls".
486	16	No	%.*ls does not allow specifying a schema name as a prefix to the assembly name.
487	16	No	An invalid option was specified for the statement "%.*ls".
488	16	No	%s columns must be comparable. The type of column "%.*ls" is "%s", which is not comparable.
489	16	No	The OUTPUT clause cannot be specified because the target view "%.*ls" is a partitioned view.
490	16	No	The resync functionality is temporarily disabled.
491	16	No	A correlation name must be specified for the bulk rowset in the from clause.
492	16	No	Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate.
493	16	No	The column '%.*ls' that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
494	16	No	The TABLESAMPLE clause can only be used with local tables.
495	16	No	The return table column "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
496	16	No	The parameter "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
497	16	No	Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.
498	16	No	Invalid value in the TABLESAMPLE or the REPEATABLE clause.
499	16	No	Invalid parameter for the getchecksum function.
500	16	No	Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).
505	16	No	The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.
506	16	No	The invalid escape character "%.*ls" was specified in a %ls predicate.
507	16	No	Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.
509	11	No	User name '%.*ls' not found.
510	16	No	Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
511	16	No	Cannot create a row of size %d which is greater than the allowable maximum row size of %d.
512	16	No	Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
513	16	No	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'.
515	16	No	Cannot insert the value NULL into column '%.ls', table '%.ls'; column does not allow nulls. %ls fails.
517	16	No	Adding a value to a '%ls' column caused an overflow.
518	16	No	Cannot convert data type %ls to %ls.
522	16	No	The WAITFOR thread was evicted.
523	16	No	A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
524	16	No	A trigger returned a resultset and the server option 'disallow results from triggers' is true.
525	16	No	The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
526	16	No	%ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query.
527	16	No	Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.
529	16	No	Explicit conversion from data type %ls to %ls is not allowed.
530	16	No	The statement terminated. The maximum recursion %d has been exhausted before statement completion.
531	10	No	Cannot set NOCOUNT to OFF inside the trigger execution because the server option "disallow_results_from_triggers" is true or we are inside LOGON trigger execution.
532	16	No	The timestamp (changed to %S_TS) shows that the row has been updated by another user.
533	10	No	Cannot set XACT ABORT to OFF inside the trigger execution unless the database compatibility is 90.
534	16	No	'%.ls' failed because it is not supported in the edition of this SQL Server instance '%.ls'. See books online for more details on feature support in different SQL Server editions.
535	16	No	The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.
536	16	No	Invalid length parameter passed to the %ls function.
537	16	No	Invalid length parameter passed to the LEFT or SUBSTRING function.
539	16	No	Schema changed after the target table was created. Rerun the Select Into query.
540	16	Yes	There is insufficient system memory to run RAISERROR.
541	16	No	There is not enough stack to execute the statement
542	16	No	An invalid datetime value was encountered. Value exceeds the year 9999.
543	16	No	Creation of a return table failed for the table valued function '%.*ls'.
544	16	No	Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF.
545	16	No	Explicit value must be specified for identity column in table '%.*ls' either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.
547	16	No	The %ls statement conflicted with the %ls constraint "%.ls". The conflict occurred in database "%.ls", table "%.ls"%ls%.ls%ls.
548	16	No	The insert failed. It conflicted with an identity range check constraint in database '%.ls', replicated table '%.ls'%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.
549	16	No	The collation '%.ls' of receiving variable is not equal to the collation '%.ls' of column '%.*ls'.
550	16	No	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.
552	16	No	CryptoAPI function '%ls' failed. Error 0x%x: %ls
555	16	No	User-defined functions are not yet enabled.
556	16	No	INSERT EXEC failed because the stored procedure altered the schema of the target table.
557	16	No	Only functions and some extended stored procedures can be executed from within a function.
558	16	No	Remote function calls are not allowed within a function.
561	16	No	Failed to access file '%.*ls'
562	16	No	Failed to access file '%.*ls'. Files can be accessed only through shares
563	14	No	The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.
564	16	No	Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'.
565	18	No	A stack overflow occurred in the server while compiling the query. Please simplify the query.
566	21	Yes	An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the "-f" switch, and using SP_CONFIGURE.
567	16	No	File '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file.
568	16	No	Encountered an error or an unexpected end of trace file '%.*ls'.
569	16	No	The handle that was passed to %ls was invalid.
570	15	No	INSTEAD OF triggers do not support direct recursion. The trigger execution failed.
571	16	No	The specified attribute value for %ls is invalid.
572	16	No	Invalid regular expression "%.*ls" near the offset %d.
573	16	No	Evaluation of the regular expression is too complex: '%.*ls'.
574	16	No	%ls statement cannot be used inside a user transaction.
575	16	No	A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.
576	16	No	Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.
577	16	No	The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.
578	16	No	Insert Exec not allowed in WAITFOR queries.
579	16	No	Cannot execute WAITFOR query with snapshot isolation level.
582	16	No	Offset is greater than the length of the column to be updated in write.
583	16	No	Negative offset or length in write.
584	16	No	Select Into not allowed in WAITFOR queries.
585	16	No	Changing database context is not allowed when populating the resource database.
587	16	No	An invalid delayed CLR type fetch token is provided.
588	16	No	Multiple tasks within the session are using the same delayed CLR type fetch token at the same time.
589	16	No	This statement has attempted to access data whose access is restricted by the assembly.
590	16	No	RPC was aborted without execution.
591	16	No	%ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.
592	16	No	Cannot find %S_MSG ID %d in database ID %d.
593	10	No	fn_trace_gettable: XML conversion of trace data for event 165 failed.
594	10	No	fn_trace_gettable: XML conversion of trace data is not supported in fiber mode.
595	16	No	Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
596	16	No	Cannot continue the execution because the session is in the kill state.
597	16	No	The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).
598	16	No	An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
599	16	No	%.*ls: The length of the result exceeds the length limit (2GB) of the target large type.
601	12	No	Could not continue scan with NOLOCK due to data movement.
602	21	Yes	Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
603	21	Yes	Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
605	21	Yes	Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
606	21	Yes	Metadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG.
608	16	Yes	No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.
609	16	No	B+ tree is not empty when waking up on RowsetBulk.
610	16	Yes	Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption.
611	16	No	Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.
613	21	No	Could not find an entry for worktable rowset with partition ID %I64d in database %d.
615	21	Yes	Could not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again.
617	20	Yes	Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor.
622	16	No	The filegroup "%.*ls" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added.
627	16	No	Cannot use SAVE TRANSACTION within a distributed transaction.
628	16	No	Cannot issue SAVE TRANSACTION when there is no active transaction.
650	16	No	You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
651	16	No	Cannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited.
652	16	No	The index "%.ls" for table "%.ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified.
666	16	No	The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key.
667	16	No	The index "%.ls" for table "%.ls" (RowsetId %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, is being restored, or is defunct.
669	22	No	The row object is inconsistent. Please rerun the query.
670	16	No	Large object (LOB) data for table "%.ls" resides on an offline filegroup ("%.ls") that cannot be accessed.
671	16	No	Large object (LOB) data for table "%.ls" resides on a read-only filegroup ("%.ls"), which cannot be modified.
672	10	No	Failed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on database restart.
674	10	Yes	Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.
675	10	Yes	Worktable with partition ID %I64d was dropped successfully after repeated attempts.
676	10	Yes	Error occurred while attempting to drop worktable with partition ID %I64d.
677	10	Yes	Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.
678	10	Yes	Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error.
679	16	No	One of the partitions of index '%.ls' for table '%.ls'(partition ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result.
680	10	Yes	Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.
681	16	No	Attempting to set a non-NULL-able column's value to NULL.
682	16	No	Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.
683	22	No	An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption.
684	22	No	An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption.
685	22	No	An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
701	19	Yes	There is insufficient system memory in resource pool '%ls' to run this query.
708	10	Yes	Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications.
801	20	Yes	A buffer was encountered with an unexpected status of 0x%x.
802	17	No	There is insufficient memory available in the buffer pool.
803	10	Yes	simulated failure (DEBUG only)
805	10	Yes	restore pending
806	10	Yes	audit failure (a page read from disk failed to pass basic integrity checks)
807	10	Yes	(no disk or the wrong disk is in the drive)
808	10	Yes	insufficient bytes transferred
821	20	Yes	Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support.
822	21	Yes	Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
823	24	Yes	The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
824	24	Yes	SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
825	10	Yes	A read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
826	10	Yes	incorrect pageid (expected %d:%d; actual %d:%d)
829	21	Yes	Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
830	10	No	stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u))
831	20	No	Unable to deallocate a kept page.
832	24	Yes	A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.
833	10	No	SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file '%ls' in database '%ls' (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x
844	10	No	Time out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait.
845	17	No	Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
846	10	No	A time-out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Not continuing to wait.
847	10	Yes	Timeout occurred while waiting for latch: class '%ls', id %p, type %d, Task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait.
848	10	Yes	Using large pages for buffer pool.
849	10	Yes	Using locked pages for buffer pool.
850	10	Yes	%I64u MB of large page memory allocated.
851	10	No	the page is in an OFFLINE file which cannot be read
854	10	Yes	Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
855	10	Yes	Uncorrectable hardware memory corruption detected. Your system may become unstable. Check the Windows event log for more details.
856	10	Yes	SQL Server has detected hardware memory corruption in database '%ls', file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page.
902	16	No	To change the %ls, the database must be in state in which a checkpoint can be executed.
904	16	No	Database %ld cannot be autostarted during server shutdown or startup.
905	21	Yes	Database '%.ls' cannot be started in this edition of SQL Server because it contains a partition function '%.ls'. Only Enterprise edition of SQL Server supports partitioning.
907	16	No	The database "%ls" has inconsistent database or file metadata.
908	10	Yes	Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.
909	21	Yes	Database '%.ls' cannot be started in this edition of SQL Server because part or all of object '%.ls' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.
910	10	No	Database '%.ls' is upgrading script '%.ls' from level %d to level %d.
911	16	No	Database '%.*ls' does not exist. Make sure that the name is entered correctly.
912	16	No	Script level upgrade for database '%.ls' failed because upgrade step '%.ls' encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
913	22	Yes	Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.
914	21	No	Script level upgrade for database '%.ls' failed because upgrade step '%.ls' was aborted before completion. If the abort happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
915	21	No	Unable to obtain the current script level for database '%.*ls'. If the error happened during startup of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion.
916	14	No	The server principal "%.ls" is not able to access the database "%.ls" under the current security context.
917	21	No	An upgrade script batch failed to execute for database '%.*ls' due to compilation error. Check the previous error message for the line which caused compilation to fail.
918	21	No	Failed to load the engine script metadata from script DLL '%.*ls'. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error.
919	10	No	User '%.*ls' is changing database script level entry %d to a value of %d.
920	20	No	Only members of the sysadmin role can modify the database script level.
921	14	No	Database '%.*ls' has not been recovered yet. Wait and try again.
922	14	No	Database '%.*ls' is being recovered. Waiting until recovery is finished.
923	14	No	Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.
924	14	No	Database '%.*ls' is already open and can only have one user at a time.
925	19	Yes	Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
926	14	No	Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
927	14	No	Database '%.*ls' cannot be opened. It is in the middle of a restore.
928	20	Yes	During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
929	20	Yes	Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider.
930	21	Yes	Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support.
931	21	Yes	Attempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support.
932	21	Yes	SQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking.
933	21	Yes	Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server.
934	21	Yes	SQL Server cannot load database '%.*ls' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture.
935	21	Yes	The script level for '%.ls' in database '%.ls' cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database.
942	14	No	Database '%.*ls' cannot be opened because it is offline.
943	14	No	Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).
944	10	No	Converting database '%.*ls' from version %d to the current version %d.
945	16	No	Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
946	14	No	Cannot open database '%.*ls' version %d. Upgrade the database to the latest version.
947	16	Yes	Error while closing database '%.*ls'. Check for previous additional errors and retry the operation.
948	20	Yes	The database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.
949	16	No	tempdb is skipped. You cannot run a query that requires tempdb
950	20	Yes	Database '%.*ls' cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.
951	10	No	Database '%.*ls' running the upgrade step from version %d to version %d.
952	16	No	Database '%.*ls' is in transition. Try the statement later.
954	14	No	The database "%.*ls" cannot be opened. It is acting as a mirror database.
955	14	No	Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured.
956	14	No	Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.
957	17	No	Database '%.*ls' is enabled for Database Mirroring, The name of the database may not be changed.
958	10	Yes	The resource database build version is %.*ls. This is an informational message only. No user action is required.
959	20	Yes	The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
960	10	No	Warning: User "sys" (principal_id = %d) in database "%.ls" has been renamed to "%.ls". "sys" is a reserved user or schema name in this version of SQL Server.
961	10	No	Warning: Index "%.ls" (index_id = %d) on object ID %d in database "%.ls" was renamed to "%.*ls" because its name is a duplicate of another index on the same object.
962	10	No	Warning: Primary key or Unique constraint "%.ls" (object_id = %d) in database "%.ls" was renamed to "%.*ls" because its index was renamed.
963	10	No	Warning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.
964	10	No	Warning: System user '%.ls' was found missing from database '%.ls' and has been restored. This user is required for SQL Server operation.
965	10	No	Warning: A column nullability inconsistency was detected in the metadata of index "%.ls" (index_id = %d) on object ID %d in database "%.ls". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
966	10	No	Warning: Assembly "%.ls" in database "%.ls" has been renamed to "%.*ls" because the name of the assembly conflicts with a system assembly in this version of SQL Server.
967	10	No	Warning: The index "%.ls" on "%.ls"."%.*ls" is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported.
968	10	No	Warning: The XML facet on type "%.ls" in schema collection "%.ls" is updated from "%.ls" to "%.ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
969	10	No	Warning: The default or fixed value on XML element or attribute "%.ls" in schema collection "%.ls" is updated from "%.ls" to "%.ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.
970	10	No	Warning: The XML instances in the XML column "%.ls.%.ls.%.*ls" may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary XML index on these XML instances.
971	10	No	The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.ls' instead of the currently attached resource database at '%.ls'.
972	17	No	Could not use database '%d' during procedure execution.
973	10	Yes	Database %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove the FILESTREAM files and the FILESTREAM filegroups, or set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.
974	10	No	Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' failed as the database files do not exist.
975	10	Yes	System objects could not be updated in database '%.*ls' because it is read-only.
976	14	No	The target database, '%.*ls', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other d
977	10	No	Warning: Could not find associated index for the constraint '%.ls' on object_id '%d' in database '%.ls'.
978	14	No	The target database ('%.*ls') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.
979	14	No	The target database ('%.*ls') is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online.
980	21	Yes	SQL Server cannot load database '%.*ls' because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Se
981	10	No	Database manager will be using %d target database version.
982	14	No	Unable to access the '%.*ls' database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled re
983	14	No	Unable to access availability database '%.*ls' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation
984	21	Yes	Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.
985	10	Yes	Successfully installed the file '%ls' into folder '%ls'.
986	10	No	Couldn't get a clean bootpage for database '%.*ls' after %d tries. This is an informational message only. No user action is required.
987	23	Yes	A duplicate key insert was hit when updating system objects in database '%.*ls'.
988	14	No	Unable to access database '%.*ls' because it lacks a quorum of nodes for high availability. Try the operation again later.
989	16	No	Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect.
990	16	No	Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect.
991	16	No	Failed to take the host database '%.*ls' offline when one or more of its partition databases is marked as suspect.
992	16	No	Failed to get the shared lock on database '%.*ls'.
993	10	No	Redo for database '%.*ls' applied version upgrade step from %d to %d.
994	10	No	Warning: Index "%.ls" on "%.ls"."%.*ls" is disabled because it contains a computed column.
995	10	No	Warning: Index "%.ls" on "%.ls"."%.*ls" is disabled. It cannot be upgraded as it resides on a read-only filegroup.
996	10	No	Warning: Index "%.ls" on "%.ls"."%.*ls" is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of '%d' bytes.

Errors 1,000 to 1,999

Error	Severity	Event Logged	Description
1001	16	No	Line %d: Length or precision specification %d is invalid.
1002	16	No	Line %d: Specified scale %d is invalid.
1003	15	No	Line %d: %ls clause allowed only for %ls.
1004	16	No	Invalid column prefix '%.*ls': No table name specified
1005	15	No	Line %d: Invalid procedure number (%d). Must be between 1 and 32767.
1006	15	No	CREATE TRIGGER contains no statements.
1007	15	No	The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38).
1008	15	No	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.
1009	16	No	The keyword DEFAULT is not allowed in DBCC commands.
1010	15	No	Invalid escape character '%.*ls'.
1011	15	No	The correlation name '%.*ls' is specified multiple times in a FROM clause.
1012	15	No	The correlation name '%.ls' has the same exposed name as table '%.ls'.
1013	15	No	The objects "%.ls" and "%.ls" in the FROM clause have the same exposed names. Use correlation names to distinguish them.
1014	15	No	TOP clause contains an invalid value.
1015	15	No	An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the column being aggregated is an outer reference.
1016	15	No	Outer join operators cannot be specified in a query containing joined tables.
1018	15	No	Incorrect syntax near '%.*ls'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax.
1019	15	No	Invalid column list after object name in GRANT/REVOKE statement.
1020	15	No	Sub-entity lists (such as column or security expressions) cannot be specified for entity-level permissions.
1021	10	No	FIPS Warning: Line %d has the non-ANSI statement '%ls'.
1022	10	No	FIPS Warning: Line %d has the non-ANSI clause '%ls'.
1023	15	No	Invalid parameter %d specified for %ls.
1024	10	No	FIPS Warning: Line %d has the non-ANSI function '%ls'.
1025	10	No	FIPS Warning: The length of identifier '%.*ls' exceeds 18.
1026	16	No	GOTO cannot be used to jump into a TRY or CATCH scope.
1028	15	No	The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed in a GROUP BY ALL clause.
1029	15	No	Browse mode is invalid for subqueries and derived tables.
1030	16	No	Only constants are allowed here. Time literal is not permitted because it refers to the current date.
1031	15	No	Percent values must be between 0 and 100.
1032	16	No	Cannot use the column prefix '%.ls'. This must match the object in the UPDATE clause '%.ls'.
1033	16	No	The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified.
1034	15	No	Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration.
1035	15	No	Incorrect syntax near '%.ls', expected '%.ls'.
1036	15	No	File option %hs is required in this CREATE/ALTER DATABASE statement.
1037	15	No	The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions.
1038	15	No	An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
1039	16	No	Option '%.*ls' is specified more than once.
1041	15	No	Option %.*ls is not allowed for a LOG file.
1042	15	No	Conflicting %ls optimizer hints specified.
1043	16	No	'%hs' is not yet implemented.
1044	15	No	Cannot use an existing function name to specify a stored procedure name.
1045	15	No	Aggregates are not allowed in this context. Only scalar expressions are allowed.
1046	15	No	Subqueries are not allowed in this context. Only scalar expressions are allowed.
1047	15	No	Conflicting locking hints specified.
1048	15	No	Conflicting cursor options %ls and %ls.
1049	15	No	Mixing old and new syntax to specify cursor options is not allowed.
1050	15	No	This syntax is only allowed for parameterized queries.
1051	15	No	Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT.
1052	15	No	Conflicting %ls options "%ls" and "%ls".
1053	15	No	For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname".
1054	15	No	Syntax '%ls' is not allowed in schema-bound objects.
1055	15	No	'%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character.
1056	15	No	The number of elements in the select list exceeds the maximum allowed number of %d elements.
1057	15	No	The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION, INTERSECT or EXCEPT operator.
1058	15	No	Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration.
1059	15	No	Cannot set or reset the 'parseonly' option within a procedure or function.
1060	15	No	The number of rows in the TOP clause must be an integer.
1061	16	No	The text/ntext/image constants are not yet implemented.
1062	16	No	The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause.
1063	16	No	A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP.
1064	16	No	A filegroup cannot be used with log files.
1065	15	No	The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE, DELETE or MERGE statements.
1066	10	No	Warning. Line %d: The option '%ls' is obsolete and has no effect.
1067	15	No	The SET SHOWPLAN statements must be the only statements in the batch.
1068	16	No	Only one list of index hints per table is allowed.
1069	16	No	Index hints are only allowed in a FROM or OPTION clause.
1070	15	No	CREATE INDEX option '%.*ls' is no longer supported.
1071	16	No	Cannot specify a JOIN algorithm with a remote JOIN.
1072	16	No	A REMOTE hint can only be specified with an INNER JOIN clause.
1073	15	No	'%.ls' is not a recognized cursor option for cursor %.ls.
1074	15	No	Creation of temporary functions is not allowed.
1075	15	No	RETURN statements in scalar valued functions must include an argument.
1076	15	No	Function '%s' requires at least %d argument(s).
1077	15	No	INSERT into an identity column not allowed on table variables.
1078	15	No	'%.ls %.ls' is not a recognized option.
1079	15	No	A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor.
1080	15	No	The integer value %.*ls is out of range.
1081	16	No	%s does not allow specifying the database name as a prefix to the assembly name.
1082	15	No	%.*ls does not support synchronous trigger registration.
1083	15	No	OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers.
1084	15	No	'%.*ls' is an invalid event type.
1085	15	No	'%.*ls' event type does not support event notifications.
1086	16	No	The FOR XML clause is invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. To work around, wrap the SELECT containing a set operator using derived table syntax and apply FOR XML on top of it.
1087	15	No	Must declare the table variable "%.*ls".
1088	15	No	Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
1089	15	No	The SET FMTONLY OFF statement must be the last statement in the batch.
1090	15	No	Invalid default for parameter %d.
1091	15	No	The option "%ls" is not valid for this function.
1092	16	No	In this context %d statistics name(s) cannot be specified for option '%ls'.
1093	16	No	%.*ls is not a valid broker name.
1094	15	No	Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.
1095	15	No	%.*ls has already been specified as an event type.
1096	15	No	Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported.
1097	15	No	Cannot use If UPDATE within this CREATE TRIGGER statement.
1098	15	No	The specified event type(s) is/are not valid on the specified target object.
1099	15	No	The ON clause is not valid for this statement.
1101	17	Yes	Could not allocate a new page for database '%.ls' because of insufficient disk space in filegroup '%.ls'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
1105	17	Yes	Could not allocate space for object '%.ls'%.ls in database '%.ls' because the '%.ls' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
1119	16	No	Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.
1121	17	No	Space allocator cannot allocate page in database %d.
1122	14	No	Table error: Page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned.
1123	14	No	Table error: Page %S_PGID. Unexpected page type %d.
1124	14	No	Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid.
1125	14	No	Table error: Page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.
1126	14	No	Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row.
1127	14	No	Table error: Page %S_PGID. Test (%hs) failed. Values are %ld and %ld.
1128	14	No	Table error: Page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld.
1129	16	No	Could not cleanup deferred deallocations from filegroup '%.*ls'.
1130	10	Yes	Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost.
1131	10	Yes	Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.
1202	16	No	The database-principal '%.*ls' does not exist or user is not a member.
1203	20	Yes	Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
1204	19	Yes	The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
1205	13	No	Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
1206	18	No	The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
1207	10	Yes	Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB.
1208	21	Yes	Could not allocate initial %u lock blocks during startup. Can not start the server.
1209	21	Yes	Could not allocate initial %u lock owner blocks during startup. Can not start the server.
1210	21	Yes	Unable to allocate lock owner block during lock migration. Server halted.
1212	10	Yes	Lock not logged: %-30ls Mode: %s
1213	21	Yes	Error spawning Lock Monitor thread: %ls
1214	17	Yes	Internal Error. There are too many parallel transactions.
1220	17	No	No more lock classes available from transaction.
1221	20	Yes	The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider.
1222	16	No	Lock request time out period exceeded.
1223	16	No	Cannot release the application lock (Database Principal: '%.ls', Resource: '%.ls') because it is not currently held.
1224	16	No	An invalid application lock resource was passed to %ls.
1225	16	No	An invalid application lock mode was passed to %ls.
1226	16	No	An invalid application lock owner was passed to %ls.
1227	16	No	An invalid application lock time-out was passed to %ls.
1228	16	No	An invalid parameter "%ls" was passed to the application lock function or procedure.
1230	16	No	An invalid database principal was passed to %ls.
1401	21	Yes	Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Server service.
1402	20	Yes	Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mirroring partners.
1403	16	Yes	The witness for the mirroring session received error response %d (state %d) from server instance %.ls for database %.ls. For more information about the error, refer to the error log on this server instance and the partner server instance.
1404	16	No	The command failed because the database mirror is busy. Reissue the command later.
1405	16	No	The database "%.*ls" is already enabled for database mirroring.
1406	16	No	Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access.
1407	16	No	The remote copy of database "%.*ls" is not related to the local copy of the database.
1408	16	No	The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring.
1409	16	No	Database mirroring cannot be enabled for the remote copy of database "%.*ls". Restore database logs to the remote copy.
1410	16	No	The remote copy of database "%.*ls" is already enabled for database mirroring.
1411	16	No	The remote copy of database "%.*ls" has not had enough log backups applied to roll forward all of its files to a common point in time.
1412	16	No	The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log.
1413	16	Yes	Communications to the remote server instance '%.*ls' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started.
1414	16	No	The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
1415	16	No	The database mirroring operation for database "%.*ls" failed. The requested operation could not be performed.
1416	16	No	Database "%.*ls" is not configured for database mirroring.
1417	16	No	Database mirroring has been disabled by the administrator for database "%.*ls".
1418	16	No	The server network address "%.*ls" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
1419	16	No	The remote copy of database "%.*ls" cannot be opened. Check the database name and ensure that it is in the restoring state, and then reissue the command.
1420	16	No	Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration.
1421	16	Yes	Communications to the remote server instance '%.*ls' failed to complete before its timeout. The ALTER DATABASE command may have not completed. Retry the command.
1422	16	No	The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over.
1423	16	No	The property name is not supported.
1424	16	No	The remote server instance has a more recent value for the property '%.*ls'. Property value not changed.
1425	16	No	The property value is invalid for '%.*ls'. Property value not changed.
1426	16	No	To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these conditions are met, reissue the command.
1427	16	No	The server instance '%.*ls' could not act as the witness. The ALTER DATABASE SET WITNESS command failed.
1428	16	No	The request is refused because the responding server instance is not in a state to service the request.
1429	16	No	The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE SET WITNESS command failed.
1430	16	No	Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.
1431	16	No	Neither the partner nor the witness server instance for database "%.*ls" is available. Reissue the command when at least one of the instances becomes available.
1432	10	No	Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner.
1433	16	No	All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness associated with the database. Verify the status and when necessary repeat the command.
1434	16	Yes	Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls.
1435	16	Yes	%ls received unexpected database mirroring error response: status %u, severity %u, state %u, string %.*ls.
1436	16	No	The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server.
1437	16	Yes	Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase system memory.
1438	16	Yes	The server instance %ls rejected configure request; read its error log file for more information. The reason %u, and state %u, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry.
1439	16	No	There is currently no witness associated with database "%.*ls".
1440	10	Yes	Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required.
1441	10	Yes	Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
1442	10	Yes	Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required.
1443	10	Yes	Database mirroring has been terminated for database '%.*ls'. This is an informational message only. No user action is required.
1444	10	Yes	Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
1445	10	Yes	Bypassing recovery for database '%ls' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change.
1446	10	No	The "%.*ls" server instance is already acting as the witness.
1447	16	No	ALTER DATABASE "%.*ls" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command.
1448	16	No	The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command.
1449	16	No	ALTER DATABASE command failed due to an invalid server connection string.
1450	16	No	The ALTER DATABASE command failed because the worker thread cannot be created.
1451	16	No	Database mirroring information was not found in the system table.
1452	16	No	The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.
1453	17	Yes	'%.ls', the remote mirroring partner for database '%.ls', encountered error %d, status %d, severity %d. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.
1454	17	Yes	Database mirroring will be suspended. Server instance '%.ls' encountered error %d, state %d, severity %d when it was acting as a mirroring partner for database '%.ls'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages.
1455	16	No	The database mirroring service cannot be forced for database "%.*ls" because the database is not in the correct state to become the principal database.
1456	16	Yes	The ALTER DATABASE command could not be sent to the remote server instance '%.*ls'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
1457	23	Yes	Synchronization of the mirror database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The ALTER DATABASE command failed. Ensure that the principal database, if available, is back up and online, and then reconnect the mirror server instance and allow the mirror database to finish synchronizing.
1458	17	Yes	The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring has been suspended. Try to resolve the error condition, and resume mirroring.
1459	24	Yes	An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it.
1460	16	No	The database "%.*ls" is already configured for database mirroring on the remote server. Drop database mirroring on the remote server to establish a new partner.
1461	10	No	Database mirroring successfully repaired physical page %S_PGID in database "%.*ls" by obtaining a copy from the partner.
1462	16	No	Database mirroring is disabled due to a failed redo operation. Unable to resume.
1463	16	No	Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions.
1464	16	No	Database mirroring cannot be enabled for the remote copy of database "%.*ls" because the database is not in a recovering state. The remote database must be restored using WITH NORECOVERY.
1465	16	No	Database mirroring cannot be enabled because the "%.*ls" database is not in full recovery mode on both partners.
1466	16	No	Database mirroring cannot be enabled because the "%.*ls" database is read-only on one of the partners.
1467	16	No	Database mirroring cannot be enabled because the "%.*ls" database is in emergency or suspect mode on one of the partners.
1468	16	No	The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session.
1469	16	No	Database mirroring cannot be enabled because the "%.*ls" database is an auto-close database on one of the partners.
1470	16	No	The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls".
1471	16	No	The database mirroring connection terminated. Out of memory sending message for database "%.*ls".
1472	16	No	The database mirroring connection terminated. Communications error sending message for database "%.*ls".
1473	16	No	This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.
1474	16	No	Database mirroring connection error %d '%.ls' for '%.ls'.
1475	16	No	Database mirroring cannot be enabled because the "%.*ls" database may have bulk logged changes that have not been backed up. The last log backup on the principal must be restored on the mirror.
1476	16	No	Database mirroring timeout value %d exceeds the maximum value 32767.
1477	16	No	The database mirroring safety level must be FULL to manually failover database "%.*ls". Set safety level to FULL and retry.
1478	16	No	The mirror database, "%.*ls", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database.
1479	16	No	The mirroring connection to "%.ls" has timed out for database "%.ls" after %d seconds without a response. Check the service and network connections.
1480	10	No	The mirrored database "%.*ls" is changing roles from "%ls" to "%ls" due to %S_MSG.
1481	10	No	Database mirroring could not repair physical page %S_PGID in database "%.*ls". The mirroring partner could not be contacted or did not provide a copy of the page. Possible reasons include a lack of network connectivity or that the copy of the page kept by the partner is also corrupted. To learn whether the partners are currently connected, view the mirroring_state_desc column of the sys.database_mirroring catalog view. If they are connected, for information about why the partner could not provide a copy of the page, examine its error log entries from around the time when this message was reported. Try to resolve the error and resume mirroring.
1485	10	No	Database mirroring has been enabled on this instance of SQL Server.
1486	10	No	Database Mirroring Transport is disabled in the endpoint configuration.
1487	10	No	Database mirroring is starting %d parallel redo thread(s) with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
1488	16	No	Database mirroring cannot be enabled because the "%.*ls" database is in single user mode.
1489	10	No	Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.
1499	16	Yes	Database mirroring error: status %u, severity %u, state %u, string %.*ls.
1501	20	Yes	Sort failure. Contact Technical Support.
1505	16	No	The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name '%.ls' and the index name '%.ls'. The duplicate key value is %ls.
1509	20	Yes	Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support.
1510	17	No	Sort failed. Out of space or locks in database '%.*ls'.
1511	20	Yes	Sort cannot be reconciled with transaction log.
1522	20	Yes	Sort operation failed during an index build. The overwriting of the allocation page in database '%.*ls' was prevented by terminating the sort. Run DBCC CHECKDB to check for allocation and consistency errors. It may be necessary restore the database from backup.
1523	20	Yes	Sort failure. The incorrect extent could not be deallocated. Contact Technical Support.
1532	20	Yes	New sort run starting on page %S_PGID found an extent not marked as shared. Retry the transaction. If the problem persists, contact Technical Support.
1533	20	Yes	Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction.
1534	20	Yes	Extent %S_PGID not found in shared extent directory. Retry the transaction. If the problem persists, contact Technical Support.
1535	20	Yes	Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support.
1537	20	Yes	Cannot suspend a sort that is not in row input phase.
1538	20	Yes	Cannot insert a row into a sort when the sort is not in row input phase.
1540	16	No	Cannot sort a row of size %d, which is greater than the allowable maximum of %d. Consider resubmitting the query using the ROBUST PLAN hint.
1541	16	No	Sort failure. A defective CLR type comparison function is suspected.
1542	10	Yes	BobMgr::GetBuf: Sort Big Output Buffer write not complete after %d seconds.
1543	10	Yes	Operating system error '%ls' resulted from attempt to read the following: sort run page %S_PGID, in file '%ls', in database with ID %d. Sort is retrying the read.
1701	16	No	Creating or altering table '%.*ls' failed because the minimum row size would be %d, including %d bytes of internal overhead. This exceeds the maximum allowable table row size of %d bytes.
1702	16	No	CREATE TABLE failed because column '%.ls' in table '%.ls' exceeds the maximum of %d columns.
1706	16	No	The system table '%.*ls' can only be created or altered during an upgrade.
1707	16	No	Cannot specify TEXTIMAGE_ON filegroup for a partitioned table.
1708	10	No	Warning: The table "%.*ls" has been created, but its maximum row size exceeds the allowed maximum of %d bytes. INSERT or UPDATE to this table will fail if the resulting row exceeds the size limit.
1709	16	No	Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns.
1710	10	No	Cannot use alias type with rule or default bound to it as a column type in table variable or return table definition in table valued function. Type '%.*ls' has a %S_MSG bound to it.
1711	16	No	Cannot define PRIMARY KEY constraint on column '%.ls' in table '%.ls'. The computed column has to be persisted and not nullable.
1712	16	No	Online index operations can only be performed in Enterprise edition of SQL Server.
1713	16	No	Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger.
1714	16	No	Alter table failed because unique column IDs have been exhausted for table '%.*ls'.
1715	16	No	Foreign key '%.ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.ls'.
1716	16	No	FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, or add a FILESTREAM column to the table.
1717	16	No	FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause.
1718	16	No	Change tracking must be enabled on database '%.ls' before it can be enabled on table '%.ls'.
1719	16	No	FILESTREAM data cannot be placed on an empty filegroup.
1720	16	No	Cannot drop FILESTREAM filegroup or partition scheme since table '%.*ls' has FILESTREAM columns.
1721	16	No	Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes.
1722	16	No	Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme is not specified for FILESTREAM data.
1723	16	No	Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specified for FILESTREAM data but not for the table.
1724	16	No	Filegroup '%.*ls' is not a FILESTREAM filegroup or partition scheme of FILESTREAM filegroups.
1725	16	No	Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEAD OF trigger exists on the %S_MSG.
1726	16	No	Cannot add FILESTREAM filegroup or partition scheme since table '%.*ls' has a FILESTREAM filegroup or partition scheme already.
1727	16	No	Cannot create nonclustered index '%.ls' on table '%.ls' with the FILESTREAM_ON clause.
1728	16	No	Cannot create index '%.ls' on table '%.ls' because the computed column '%.*ls' uses a FILESTREAM column.
1729	16	No	Cannot create table '%.ls' because the partitioning column '%.ls' uses a FILESTREAM column.
1730	16	No	Creating or altering compressed table '%.*ls' failed because the uncompressed row size would be %d, including %d bytes of internal overhead. This exceeds the maximum allowable table row size of %d bytes.
1731	16	No	Cannot create the sparse column '%.ls' in the table '%.ls' because an option or data type specified is not valid. A sparse column must be nullable and cannot have the ROWGUIDCOL, IDENTITY, or FILESTREAM properties. A sparse column cannot be of the following data types: text, ntext, image, geometry, geography, or user-defined type.
1732	16	No	Cannot create the sparse column set '%.ls' in the table '%.ls' because a table cannot have more than one sparse column set. Modify the statement so that only one column is specified as COLUMN_SET FOR ALL_SPARSE_COLUMNS.
1733	16	No	Cannot create the sparse column set '%.ls' in the table '%.ls' because a sparse column set must be a nullable xml column. Modify the column definition to allow null values.
1734	16	No	Cannot create the sparse column set '%.ls' in the table '%.ls' because the table already contains one or more sparse columns. A sparse column set cannot be added to a table if the table contains a sparse column.
1736	16	No	The column '%.ls' in the table '%.ls' cannot be referenced in a CHECK constraint or computed column definition because the column is a sparse column set. A sparse column set cannot be referenced in a CHECK constraint or computed column definition.
1738	10	No	Cannot create table '%.*ls' with only a column set column and without any non-computed columns in the table.
1750	10	No	Could not create constraint. See previous errors.
1752	16	No	Column '%.ls' in table '%.ls' is invalid for creating a default constraint.
1753	16	No	Column '%.ls.%.ls' is not the same length or scale as referencing column '%.ls.%.ls' in foreign key '%.*ls'. Columns participating in a foreign key relationship must be defined with the same length and scale.
1754	16	No	Defaults cannot be created on columns with an IDENTITY attribute. Table '%.ls', column '%.ls'.
1755	16	No	Defaults cannot be created on columns of data type timestamp. Table '%.ls', column '%.ls'.
1756	10	No	Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary tables.
1757	16	No	Column '%.ls.%.ls' is not of same collation as referencing column '%.ls.%.ls' in foreign key '%.*ls'.
1758	16	No	Only a single constraint can be added or dropped online with no other operations in the same statement.
1759	16	No	Computed column '%.ls' in table '%.ls' is not allowed to be used in another computed-column definition.
1760	16	No	Constraints of type %ls cannot be created on columns of type %ls.
1761	16	No	Cannot create the foreign key "%.*ls" with the SET NULL referential action, because one or more referencing columns are not nullable.
1762	16	No	Cannot create the foreign key "%.*ls" with the SET DEFAULT referential action, because one or more referencing not-nullable columns lack a default constraint.
1763	16	No	Cross-database foreign key references are not supported. Foreign key '%.*ls'.
1764	16	No	Computed Column '%.ls' in table '%.ls' is invalid for use in '%ls' because it is not persisted.
1765	16	No	Foreign key '%.ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.ls'.
1766	16	No	Foreign key references to temporary tables are not supported. Foreign key '%.*ls'.
1767	16	No	Foreign key '%.ls' references invalid table '%.ls'.
1768	16	No	Foreign key '%.ls' references object '%.ls' which is not a user table.
1769	16	No	Foreign key '%.ls' references invalid column '%.ls' in referencing table '%.*ls'.
1770	16	No	Foreign key '%.ls' references invalid column '%.ls' in referenced table '%.*ls'.
1771	16	No	Cannot create foreign key '%.ls' because it references object '%.ls' whose clustered index '%.*ls' is disabled.
1772	16	No	Foreign key '%.*ls' is not valid. A system table cannot be used in a foreign key definition.
1773	16	No	Foreign key '%.ls' has implicit reference to object '%.ls' which does not have a primary key defined on it.
1774	16	No	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'.
1775	16	No	Cannot create foreign key '%.ls' because it references object '%.ls' whose PRIMARY KEY index '%.*ls' is disabled.
1776	16	No	There are no primary or candidate keys in the referenced table '%.ls' that match the referencing column list in the foreign key '%.ls'.
1778	16	No	Column '%.ls.%.ls' is not the same data type as referencing column '%.ls.%.ls' in foreign key '%.*ls'.
1779	16	No	Table '%.*ls' already has a primary key defined on it.
1781	16	No	Column already has a DEFAULT bound to it.
1784	16	No	Cannot create the foreign key '%.ls' because the referenced column '%.ls.%.*ls' is a non-persisted computed column.
1785	16	No	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	16	No	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	16	No	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	16	No	Cascading foreign key '%.ls' cannot be created where the referencing column '%.ls.%.*ls' is an identity column.
1789	16	No	Cannot use CHECKSUM(*) in a computed column definition.
1790	16	No	The name of a user-defined table type cannot start with a number (#) sign.
1791	16	No	A DEFAULT constraint cannot be created on the column '%.ls' in the table '%.ls' because the column is a sparse column or sparse column set. Sparse columns or sparse column sets cannot have a DEFAULT constraint.
1793	16	No	Cannot drop index '%.*ls' since a partition scheme is not specified for FILESTREAM data.
1801	16	No	Database '%.*ls' already exists. Choose a different database name.
1802	16	No	CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
1803	17	No	The CREATE DATABASE statement failed. The primary file must be at least %d MB to accommodate a copy of the model database.
1806	16	No	CREATE DATABASE failed. The default collation of database '%.ls' cannot be set to '%.ls'.
1807	17	No	Could not obtain exclusive lock on database '%.*ls'. Retry the operation later.
1810	16	No	The model database must be updatable before a new database can be created.
1812	16	No	CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option.
1813	16	No	Could not open new database '%.*ls'. CREATE DATABASE is aborted.
1814	10	Yes	Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
1815	16	No	The %ls property cannot be used with database snapshot files.
1816	16	No	Database snapshot on the system database %.*ls is not allowed.
1817	16	No	Only the owner of database "%.*s" or the system administrator can create a database snapshot on it.
1818	16	No	Primary log file '%ls' is missing and the database was not cleanly shut down so it cannot be rebuilt.
1819	10	No	Could not create default log file because the name was too long.
1821	16	No	Cannot create a database snapshot on another database snapshot.
1822	16	No	The database must be online to have a database snapshot.
1823	16	No	A database snapshot cannot be created because it failed to start.
1824	16	No	Cannot attach a database that was being restored.
1825	16	No	Filegroups and collations cannot be specified for database snapshots.
1826	16	No	User-defined filegroups are not allowed on "%ls".
1827	16	No	CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of %I64d MB per %S_MSG.
1828	16	No	The logical file name "%.*ls" is already in use. Choose a different name.
1829	16	No	The FOR ATTACH option requires that at least the primary file be specified.
1830	16	No	The files '%.ls' and '%.ls' are both primary files. A database can only have one primary file.
1831	16	No	File ONLINE/OFFLINE syntax cannot be used with CREATE DATABASE.
1832	20	No	Cannot attach the file '%.ls' as database '%.ls'.%.*ls
1833	16	No	File '%ls' cannot be reused until after the next BACKUP LOG operation.
1834	16	No	The file '%ls' cannot be overwritten. It is being used by database '%.*ls'.
1835	16	No	Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d.
1836	10	No	Cannot create the default data files because the name that was supplied is too long.
1837	16	No	The file name "%ls" is too long to create an alternate stream name.
1838	10	No	Offline database file(s) have been overwritten while being reverted to online state from a database snapshot. The reverted file might contain invalid pages. Please run database consistency checks to assess the data integrity.
1839	16	No	Could not create default data files because the name '%ls' is a reserved device name.
1842	16	No	The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than 2147483647 in units of both page size and percentage.
1843	10	Yes	Reverting database '%ls' to the point in time of database snapshot '%ls' with split point LSN %.*ls (0x%ls). This is an informational message only. No user action is required.
1844	16	No	%ls is not supported on %ls.
1845	16	No	Cannot find SQL Volume Shadow Copy Service (VSS) Writer in writer metadata document provided by VSS while creating auto-recovered VSS snapshot for online DBCC check.
1846	16	No	Cannot find SQL Volume Shadow Copy (VSS) Writer component for database '%ls' while creating auto-recovered VSS snapshot for online DBCC check.
1847	16	No	The current version of the operating system doesn't support auto-recovered Volume Shadow Copy (VSS) snapshots.
1848	16	No	Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database '%ls' for online DBCC check.
1849	16	No	CREATE DATABASE failed because FILESTREAM filegroups were declared and ALLOW_SNAPSHOT_ISOLATION or READ_COMMITTED_SNAPSHOT is set to ON in the model database. Either set ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to OFF in the model database, or create the database without declaring any FILESTREAM filegroups, set ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to OFF in the new database, and then use ALTER DATABASE to add FILESTREAM filegroups and files.
1901	16	No	Cannot create index or statistics '%.ls' on view '%.ls' because key column '%.*ls' is imprecise, computed and not persisted. Consider removing reference to column in view index or statistics key or changing column to be precise. If column is computed in base table consider marking it PERSISTED there.
1902	16	No	Cannot create more than one clustered index on %S_MSG '%.ls'. Drop the existing clustered index '%.ls' before creating another.
1904	16	No	The %S_MSG '%.ls' on table '%.ls' has %d column names in %S_MSG key list. The maximum limit for index or statistics key column list is %d.
1907	16	No	Cannot recreate index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index.
1908	16	No	Column '%.ls' is partitioning column of the index '%.ls'. Partition columns for a unique index must be a subset of the index key.
1909	16	No	Cannot use duplicate column names in %S_MSG. Column name '%.*ls' listed more than once.
1910	16	No	Could not create %S_MSG '%.*ls' because it exceeds the maximum of %d allowed per table or view.
1911	16	No	Column name '%.*ls' does not exist in the target table or view.
1912	16	No	Could not proceed with index DDL operation on %S_MSG '%.*ls' because it conflicts with another concurrent operation that is already in progress on the object. The concurrent operation could be an online index operation on the same object or another concurrent operation that moves index pages like DBCC SHRINKFILE.
1913	16	No	The operation failed because an index or statistics with name '%.ls' already exists on %S_MSG '%.ls'.
1914	16	No	Index cannot be created on object '%.*ls' because the object is not a user table or view.
1915	16	No	Cannot alter a non-unique index with ignore_dup_key index option. Index '%.*ls' is non-unique.
1916	16	No	CREATE INDEX options %ls and %ls are mutually exclusive.
1917	16	No	Cannot create, rebuild or drop an index on a local temporary table online. Perform the index operation offline.
1919	16	No	Column '%.ls' in table '%.ls' is of a type that is invalid for use as a key column in an index.
1921	16	No	Invalid %S_MSG '%.*ls' specified.
1922	16	No	Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. Use ALTER DATABASE to add one or more files to the filegroup.
1924	16	No	Filegroup '%.*ls' is read-only.
1925	16	No	Cannot convert a clustered index to a nonclustered index by using the DROP_EXISTING option. To change the index type from clustered to nonclustered, delete the clustered index, and then create a nonclustered index by using two separate statements.
1927	16	No	There are already statistics on table '%.ls' named '%.ls'.
1929	16	No	Statistics cannot be created on object '%.*ls' because the object is not a user table or view.
1930	16	No	Cannot convert a nonclustered index to a clustered index because a foreign key constraint references the index. Remove the foreign key constraint and then retry the operation.
1931	16	No	The SQL statement cannot be executed because filegroup '%.*ls' is offline. Use the sys.database_files or sys.master_files catalog view to determine the state of the files in this filegroup and then restore the offline file(s) from backup.
1934	16	No	%ls failed because the following SET options have incorrect settings: '%.*ls'. Verify that SET options are correct for use with %S_MSG.
1935	16	No	Cannot create index. Object '%.ls' was created with the following SET options off: '%.ls'.
1937	16	No	Cannot create %S_MSG on view '%.ls' because it references another view '%.ls'. Consider expanding referenced view's definition by hand in indexed view definition.
1938	16	No	Index cannot be created on view '%.ls' because the underlying object '%.ls' has a different owner.
1939	16	No	Cannot create %S_MSG on view '%.*ls' because the view is not schema bound.
1940	16	No	Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index.
1941	16	No	Cannot create nonunique clustered index on view '%.*ls' because only unique clustered indexes are allowed. Consider creating unique clustered index instead.
1942	16	No	Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, image, FILESTREAM or xml columns.
1944	16	No	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	10	No	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	16	No	Operation failed. The index entry of length %d bytes for the index '%.*ls' exceeds the maximum length of %d bytes.
1947	16	No	Cannot create %S_MSG on view "%.ls". The view contains a self join on "%.ls".
1949	16	No	Cannot create %S_MSG on view '%.*ls'. The function '%s' yields nondeterministic results. Use a deterministic system function, or modify the user-defined function to return deterministic results.
1956	16	No	Cannot create %S_MSG on the '%.ls' view because it uses the nondeterministic user-defined function '%.ls'. Remove the reference to the function, or make it deterministic.
1957	16	No	Cannot create %S_MSG on view '%.ls' because view uses imprecise user-defined function '%.ls'. Consider removing reference to function or altering it to be precise.
1959	16	No	Cannot create an index on a view or computed column because the compatibility level of this database is less than 80. Use sp_dbcmptlevel to raise the compatibility level of the database.
1961	16	No	Cannot create %S_MSG on view '%.ls'. The collation cast expression with collation name '%.ls' is non-deterministic because it is dependent on the operating system.
1962	16	No	Cannot create %S_MSG on view '%.ls' because column '%.ls' that is referenced by the view in the WHERE or GROUP BY clause is imprecise. Consider eliminating the column from the view, or altering the column to be precise.
1963	16	No	Cannot create %S_MSG on view "%.*ls". The view contains a convert that is imprecise or non-deterministic.
1964	16	No	Cannot create %S_MSG on view "%.*ls". The view contains an imprecise constant.
1965	16	No	Cannot create %S_MSG on view "%.*ls". The view contains an imprecise arithmetic operator.
1966	16	No	Cannot create %S_MSG on view '%.*ls'. The view contains an imprecise aggregate operator.
1967	16	No	Cannot create a new clustered index on a view online.
1968	16	No	Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option.
1969	16	No	Default FILESTREAM filegroup is not available in database '%.*ls'.
1970	10	No	Warning: Online index operation on table '%.*ls' will proceed but concurrent access to the table may be limited due to residual lock on the table from a previous operation in the same transaction.
1971	16	No	Cannot disable index '%.ls' on table '%.ls'. Permission denied to disable foreign key '%.ls' on table '%.ls' that uses this index.
1972	16	No	Cannot disable clustered index '%.ls' on table '%.ls'. Permission denied to alter the referencing view '%.*ls' while disabling its clustered index.
1973	16	No	Cannot perform the specified operation on disabled index '%.ls' on %S_MSG '%.ls'.
1974	16	No	Cannot perform the specified operation on %S_MSG '%.ls' because its clustered index '%.ls' is disabled.
1975	16	No	Index '%.*ls' row length exceeds the maximum permissible length of '%d' bytes.
1976	16	No	Cannot create index or statistics '%.ls' on view '%.ls' because cannot verify key column '%.*ls' is precise and deterministic. Consider removing column from index or statistics key, marking column persisted in base table if it is computed, or using non-CLR-derived column in key.
1977	16	No	Could not create %S_MSG '%.ls' on table '%.ls'. Only XML Index can be created on XML column '%.*ls'.
1978	16	No	Column '%.ls' in table '%.ls' is of a type that is invalid for use as a key column in an index or statistics.
1979	16	No	Cannot use index option ignore_dup_key to alter index '%.*ls' as it enforces a primary or unique constraint.
1980	16	No	Index cannot be created on computed column '%.ls' of table '%.ls' because the underlying object '%.*ls' has a different owner.
1981	10	No	Warning: The maximum length of the row exceeds the permissible limit of %d bytes. For some combination of large values, the insert/update operation will fail.
1982	16	No	Cannot create %S_MSG on view '%.ls' because the view references non-deterministic or imprecise member function '%.ls' on CLR type '%.*ls'. Consider removing reference to the function or altering the function to behave in a deterministic way. Do not declare a CLR function that behaves non-deterministically to have IsDeterministic=true, because that can lead to index corruption. See Books Online for details.
1983	16	No	Cannot create %S_MSG on view '%.*ls'. The function '%s' yields imprecise results. Use a precise system function, or modify the user-defined function to return precise results.
1984	16	No	Index '%.*ls' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds the maximum allowed length of '%d' bytes.
1985	16	No	Cannot create %S_MSG on view '%.*ls'. It contains one or more XML data type methods.
1986	10	No	Cannot replace non-hypothetical index '%.*ls' with a hypothetical index using the DROP_EXISTING option.
1987	16	No	Cannot %S_MSG %S_MSG '%.ls' on %S_MSG '%.ls' because its %S_MSG is disabled.
1988	16	No	Cannot rebuild clustered index '%.*ls' online because it is disabled.
1989	16	No	Cannot enable foreign key constraint '%.ls' as index '%.ls' on referenced key is disabled.
1990	16	No	Cannot define an index on a view with ignore_dup_key index option. Remove ignore_dup_key option and verify that view definition does not allow duplicates, or do not index view.
1991	16	No	Cannot disable clustered index '%.ls' on table '%.ls'. Permission denied to disable foreign key '%.ls' on table '%.ls' that references this table.
1992	10	No	Warning: Foreign key '%.ls' on table '%.ls' referencing table '%.ls' was disabled as a result of disabling the index '%.ls'.
1993	16	No	Cannot partition an index on a table variable or return table definition in table valued function.
1994	16	No	Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required.
1995	16	No	Cannot rebuild hypothetical index '%.*ls' online.
1996	16	No	Could not create index enforcing primary key constraint '%.*ls' using DROP_EXISTING option because table has an XML or spatial index. Drop the XML or spatial index, create the primary key contstraint, and recreate the XML or spatial index.
1997	16	No	Could not convert the XML or spatial index '%.*ls' to a relational index by using the DROP_EXISTING option. Drop the XML or spatial index and create a relational index with the same name.
1998	10	No	Warning: Clustered index '%.ls' on view '%.ls' referencing table '%.ls' was disabled as a result of disabling the index '%.ls'.
1999	16	No	Column '%.ls' in table '%.ls' is of a type that is invalid for use as included column in an index.

Errors 2,000 to 2,999

Error	Severity	Event Logged	Description
2002	16	No	Cannot create a procedure for replication with group number greater than one.
2003	16	No	Procedures with a group number cannot have parameters of XML or CLR types. Parameter '%.ls' of procedure '%.ls' has type '%ls'.
2004	16	No	Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number.
2007	10	No	The module '%.ls' depends on the missing object '%.ls'. The module will still be created; however, it cannot run successfully until the object exists.
2008	16	No	The object '%.*ls' is not a procedure so you cannot create another procedure under that group name.
2010	16	No	Cannot perform alter on '%.*ls' because it is an incompatible object type.
2011	16	No	Index hints cannot be specified within a schema-bound object.
2013	10	No	Warning: 'is_ms_shipped' property is turned off for %S_MSG '%.*ls' because you do not have permission to create or alter an object with this property.
2014	16	No	Remote access is not allowed from within a schema-bound object.
2020	16	No	The dependencies reported for entity "%.*ls" do not include references to columns. This is either because the entity references an object that does not exist or because of an error in one or more statements in the entity. Before rerunning the query, ensure that there are no errors in the entity and that all objects referenced by the entity exist.
2101	14	No	Cannot %S_MSG a server level %S_MSG for user '%.*ls' since there is no login corresponding to the user.
2102	16	No	Cannot %S_MSG %S_MSG '%.ls' since there is no user for login '%.ls' in database '%.*ls'.
2103	15	No	Cannot %S_MSG trigger '%.*s' because its schema is different from the schema of the target table or view.
2104	14	No	Cannot %S_MSG the %S_MSG '%.*ls', because you do not have permission.
2108	15	No	Cannot %S_MSG %S_MSG on '%.*ls' as the target is not in the current database.
2110	15	No	Cannot alter trigger '%.ls' on '%.ls' because this trigger does not belong to this object. Specify the correct trigger name or the correct target object name.
2111	16	No	Cannot %S_MSG trigger '%.ls' on %S_MSG '%.ls' because an INSTEAD OF %s trigger already exists on this object.
2112	16	No	Cannot create trigger '%.ls' on view '%.ls' because the view is defined with CHECK OPTION.
2113	16	No	Cannot %S_MSG INSTEAD OF DELETE or INSTEAD OF UPDATE TRIGGER '%.ls' on table '%.ls'. This is because the table has a FOREIGN KEY with cascading DELETE or UPDATE.
2114	16	No	Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column.
2115	16	No	Server level event notifications are disabled as the database msdb does not exist.
2116	16	No	Cannot CREATE EVENT NOTIFICATION to database '%.*ls' because it is not a valid broker database.
2117	16	No	Cannot %S_MSG INSTEAD OF trigger '%.ls' on %S_MSG '%.ls' because the %S_MSG has a FILESTREAM column.
2201	16	No	%sDerivation from "anySimpleType" by restriction is not permitted, and derivation by restriction from a type derived from "anySimpleType" by extension is allowed only if no constraining facets are specified.
2202	16	No	%sAn error has occurred while compiling the query. To obtain more detailed information about the error, the query must be run by a user with EXECUTE permissions on the xml schema collection used in the query.
2203	16	No	%sOnly 'http://www.w3.org/2001/XMLSchema#decimal?', 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed as predicates, found '%ls'
2204	16	No	%sOnly 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed in conditions and with logical operators, found '%ls'
2205	16	No	%s"%ls" was expected.
2206	16	No	%sNamespace prefix 'xml' can only be associated with the URI 'http://www.w3.org/XML/1998/namespace' and this URI cannot be used with other prefixes.
2207	16	No	%sOnly non-document nodes can be inserted. Found "%ls".
2208	16	No	%sThe URI that starts with '%ls' is too long. Maximum allowed length is %d characters.
2209	16	No	%sSyntax error near '%ls'
2210	16	No	%sHeterogeneous sequences are not allowed: found '%ls' and '%ls'
2211	16	No	%sSingleton (or empty sequence) required, found operand of type '%ls'
2212	16	No	%sInvalid source character '%c' (0x%02x) found in an identifier near '%ls'.
2213	16	No	%sCannot atomize/apply data() on expression that contains type '%ls' within inferred type '%ls'
2214	16	No	%sThe type '%ls' is not an atomic type
2215	16	No	%sThe value of attribute '%ls' exceeds 4000 characters, the maximum permitted in XML schema documents
2216	16	No	%sInvalid XPath value in "%ls".
2217	16	No	%s'%ls' or '%ls' expected
2218	16	No	%sThere is no attribute named '@%ls'
2219	16	No	%sThere is no attribute named '@%ls' in the type '%ls'.
2220	16	No	%sThere is no attribute named '@%ls:%ls'
2221	16	No	%sThere is no attribute named '@%ls:%ls' in the type '%ls'.
2222	16	No	%sInvalid source character 0x%02x found in an identifier near '%ls'.
2223	16	No	%sSyntax error near '%ls', expected an identifier.
2225	16	No	%sA string literal was expected
2226	16	No	%sThe target of 'insert' must be a single node, found '%ls'
2227	16	No	%sThe variable '%ls' was not found in the scope in which it was referenced.
2228	16	No	%sThe variable '%ls:%ls' was not found in the scope in which it was referenced.
2229	16	No	%sThe name "%ls" does not denote a namespace.
2230	16	No	%sThe name "%ls" has already been defined.
2231	16	No	%sThe name "%ls" does not denote a defined type.
2232	16	No	%sThe name "%ls:%ls" does not denote a defined type.
2233	16	No	%sThe operand of "%ls" has an invalid type.
2234	16	No	%sThe operator "%ls" cannot be applied to "%ls" and "%ls" operands.
2235	16	No	%sAn argument list was applied to a non-function term.
2236	16	No	%sThere are not enough actual arguments in the call to function "%ls".
2237	16	No	%sDerivation from anyType by extension is not supported in this release.
2238	16	No	%sToo many arguments in call to function '%ls'
2240	16	No	%sThe target of 'insert into' must be an element/document node, found '%ls'
2241	16	No	%sVariable expected: '$name'
2242	16	No	%sType specification expected.
2243	16	No	%sRelative path expression used without any context
2247	16	No	%sThe value is of type "%ls", which is not a subtype of the expected type "%ls".
2248	16	No	%sSyntax error near '%ls', expected 'as', 'into', 'before' or 'after'.
2249	16	No	%sThe target of 'insert before/after' must be an element/PI/comment/text node, found '%ls'
2256	16	No	%sSyntax error near '%ls', expected a "node test".
2258	16	No	%sThe position may not be specified when inserting an attribute node, found '%ls'
2260	16	No	%sThere is no element named '%ls'
2261	16	No	%sThere is no element named '%ls' in the type '%ls'.
2262	16	No	%sThere is no element named '%ls:%ls'
2263	16	No	%sThere is no element named "%ls:%ls" in the type "%ls".
2264	16	No	%sOnly non-document nodes may be deleted, found '%ls'
2266	16	No	%sExpected end tag '%ls:%ls'
2267	16	No	%sExpected end tag '%ls'
2268	16	No	%sEnd tag '/%ls:%ls' has no matching begin tag
2269	16	No	%sEnd tag '/%ls' has no matching begin tag
2270	16	No	%sDuplicate attribute '%ls:%ls'
2271	16	No	%sDuplicate attribute '%ls'
2272	16	No	%s'?>' expected
2273	16	No	%sUnterminated CDATA section
2274	16	No	%sUnterminated string constant (started on line %u)
2275	16	No	%sUnterminated XML declaration
2276	16	No	%sDerivation from 'QName' by restriction is not supported in this release
2277	16	No	%sA tag name may not contain the character '%c'
2278	16	No	%sA tag name may not start with the character '%c'
2279	16	No	%sA name/token may not start with the character '%c'
2280	16	No	%s<! was not followed by a valid construct
2281	16	No	%sCannot construct DTDs in XQuery
2282	16	No	%sInvalid entity reference
2283	16	No	%sThe character '%c' may not be part of an entity reference
2284	16	No	%sThe namespace prefix '%ls' has not been defined
2285	16	No	%sInvalid numeric entity reference
2291	16	No	%sNo root element was found.
2292	16	No	%sWhen a type with simple content restricts a type with mixed content, it must have an embedded simple type definition. Location: '%ls'.
2293	16	No	%sChoice cannot be empty unless minOccurs is 0. Location: '%ls'.
2294	16	No	%s'xml' is not allowed as a processing instruction target.
2297	16	No	%sElement <%ls> is not valid at location '%ls'.
2298	16	No	%sAttribute '%ls' is not valid at location '%ls'.
2299	16	No	%sRequired attribute "%ls" of XSD element "%ls" is missing.
2300	16	No	%sRequired sub-element "%ls" of XSD element "%ls" is missing.
2301	16	No	%sThe element "%ls" has already been defined.
2302	16	No	%sThe name "%ls" has already been defined in this scope.
2305	16	No	%sElement or attribute type specified more than once. Location: '%ls'.
2306	16	No	%sThe qualified name "%ls" was found in a context where only NCName is allowed.
2307	16	No	%sReference to an undefined name '%ls'
2308	16	No	%sReference to an undefined name '%ls' within namespace '%ls'
2309	16	No	%sThe value of "%ls" is not a valid number.
2310	16	No	%sThe attribute "%ls" is declared more than once.
2311	16	No	%sThe attribute "%ls" is declared more than once within "%ls".
2312	16	No	%sThe value of attribute '%ls' does not conform to the type definition 'http://www.w3.org/2001/XMLSchema#%ls': '%ls'.
2313	16	No	%sThe attribute "%ls" cannot have a value of "%ls".
2314	16	No	%sThe attribute "%ls" cannot have a negative value.
2315	16	No	%sThe attribute "%ls" should have a string value.
2316	16	No	%sThe required 'base' attribute is missing. Location: '%ls'.
2317	16	No	%sThe base type "%ls" defined on XSD element "%ls" is not a simple type.
2319	16	No	%sThis type may not have a '%ls' facet. Location: '%ls'.
2320	16	No	%sDuplicate facet '%ls' found at location '%ls'.
2321	16	No	%sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'.
2322	16	No	%sThe element type is not a subclass of the substitution group's head
2323	16	No	%sThe end tag '%ls' doesn't match opening tag '%ls' from line %u
2324	16	No	%sThe end tag '%ls:%ls' doesn't match opening tag '%ls' from line %u
2325	16	No	%sThe end tag '%ls' doesn't match opening tag '%ls:%ls' from line %u
2326	16	No	%sThe end tag '%ls:%ls' doesn't match opening tag '%ls:%ls' from line %u
2327	16	No	%sThe content or definition of <%ls> is missing.
2328	16	No	%sSchema namespace '%ls' doesn't match <include> directive's '%ls'
2329	16	No	%sThe string "%ls" is not a valid time duration value.
2331	16	No	%sRedefinition has to have itself as base type. Location: '%ls'.
2332	16	No	%s'%ls' may not be used with an 'empty' operand
2333	16	No	%sInvalid source character 0x%02x
2334	16	No	%sInvalid source character '%c' (0x%02x)
2335	16	No	%sNewline in character/string constant
2336	16	No	%s'%c' is not a valid octal digit (numbers starting with '0' are implicitly octal)
2337	16	No	%sThe target of 'replace' must be at most one node, found '%ls'
2338	16	No	%sThe second 'replace' operand must contain only nodes, found '%ls'
2339	16	No	%sEither a memberType attribute or a simpleType child must be present. Location: '%ls'.
2340	16	No	%sComment started on line %u has no end
2341	16	No	%sExpected hex character code following '\x'
2342	16	No	%sInvalid numeric constant.
2343	16	No	%sUnterminated text section - missing `
2348	16	No	%sA namespace URI should contain at least one non-whitespace character.
2349	16	No	%sAttempt to redefine namespace prefix '%ls'
2350	16	No	%sInvalid XML element content
2351	16	No	%sExpected 'first' or 'last'
2353	16	No	%s'to' or 'insert' or 'delete' expected
2354	16	No	%sInvalid source character encoding
2355	16	No	%s'else' expected
2356	16	No	%sThe target of 'replace value of' must be a non-metadata attribute or an element with simple typed content, found '%ls'
2357	16	No	%sA document node may only be replaced with another document node, found '%ls'
2358	16	No	%sDerivation with both a 'base' attribute and an embedded type definition is not supported in this release. Location: '%ls'.
2359	16	No	%sThe target of '%ls' may not be a constructed node
2360	16	No	%sCannot have both a 'name' and 'ref' attribute. Location: '%ls'.
2361	16	No	%sThe base type of an XSD extension or restriction type must be a simple type.
2362	16	No	%sXSD schema too complex
2363	16	No	%sXQuery too complex
2364	16	No	%sCannot implicitly convert from '%ls' to '%ls'
2365	16	No	%sCannot explicitly convert from '%ls' to '%ls'
2366	16	No	%s"%ls" has a circular definition.
2367	16	No	%sThe item type of an XSD list type must be a simple type. Location: '%ls'.
2368	16	No	%sCannot have element content in a complex type with simple content. Location: '%ls'.
2369	16	No	%sCannot have more than one group/sequence/choice/all within a restriction or extension. Location: '%ls'.
2370	16	No	%sNo more tokens expected at the end of the XQuery expression. Found '%ls'.
2371	16	No	%s'%ls' can only be used within a predicate or XPath selector
2372	16	No	%sMetadata attribute '@%ls:%ls' may not be used with '%ls'
2373	16	No	%s%ls is not supported with constructed XML
2374	16	No	%sA node or set of nodes is required for %ls
2375	16	No	%sAggregate function '%ls' expects a sequence argument
2376	16	No	%sOperand of a single numeric type expected
2377	16	No	%sResult of '%ls' expression is statically 'empty'
2378	16	No	%sExpected XML schema document
2379	16	No	%sThe name specified is not a valid XML name :'%ls'
2380	16	No	%sMixed content is not allowed at location '%ls'.
2382	16	No	%sInvalid combination of minOccurs and maxOccurs values, minOccurs has to be less than or equal to maxOccurs. Location: '%ls'.
2383	16	No	%sInvalid value '%ls' for the %ls attribute. The value has to be between 0 and %ld.
2384	16	No	%sInvalid element occurrence, element '%ls' was found multiple times in the context of element '%ls'
2385	16	No	Invalid target namespace specified
2386	16	No	%sThe value of '%ls' facet is outside of the allowed range
2387	16	No	%sCannot have both 'type' and 'ref' attributes. Location: '%ls'.
2388	16	No	%sInvalid element occurrence, element '%ls' has to appear first in the context of '%ls'
2389	16	No	%s'%ls' requires a singleton (or empty sequence), found operand of type '%ls'
2390	16	No	%sTop-level %s nodes are not supported
2391	16	No	%sRedefining XSD schemas is not supported
2392	16	No	%s'%ls::' is not a valid axis
2393	16	No	%sEither an itemType attribute or a simpleType child must be present. Location: '%ls'.
2394	16	No	%sThere is no function '%ls()'
2395	16	No	%sThere is no function '%ls:%ls()'
2396	16	No	%sAttribute may not appear outside of an element
2397	16	No	%sIdentifiers may not contain more than %u characters
2398	16	No	%sDuplicate id value found: '%ls'
2399	16	No	%sAn attribute cannot have a value of type '%ls', a simple type was expected
2501	16	No	Cannot find a table or object with the name "%.*ls". Check the system catalog.
2502	16	No	Memory object list dump failed due to temporary inconsistency in the memory object structure. Please try again.
2503	10	No	Successfully deleted the physical file '%ls'.
2504	16	No	Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls.
2505	16	No	The device '%.*ls' does not exist. Use sys.backup_devices to show available devices.
2506	16	No	Could not find a table or object name '%.ls' in database '%.ls'.
2507	16	No	The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS.
2508	16	No	The %.ls count for object "%.ls", index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE.
2509	16	No	DBCC CHECKCONSTRAINTS failed due to an internal query error.
2510	16	No	DBCC %ls error: %ls.
2511	16	No	Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d.
2512	16	No	Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S_PGID slot %d.
2514	16	No	A DBCC PAGE error has occurred: %ls.
2515	16	No	The page %S_PGID, object ID %d, index ID %d, partition ID %I64d, allocation unit ID %I64d (type %.*ls) has been modified, but is not marked as modified in the differential backup bitmap.
2516	16	Yes	Repair has invalidated the differential bitmap for database %.*ls. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup.
2517	16	Yes	Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again.
2518	10	No	Object ID %ld (object "%.*ls"): Computed columns and CLR types cannot be checked for this object because the common language runtime (CLR) is disabled.
2519	10	No	Computed columns and CLR types cannot be checked for object ID %ld (object "%.*ls") because the internal expression evaluator could not be initialized.
2520	16	No	Could not find database '%.*ls'. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists by querying the sys.databases catalog view.
2521	16	No	Could not find database ID %d. The database ID either does not exist, or the database was dropped before a statement tried to use it. Verify if the database ID exists by querying the sys.databases catalog view.
2522	16	No	Unable to process index %.ls of table %.ls because filegroup %.*ls is invalid.
2523	16	No	Filegroup %.*ls is invalid.
2524	16	No	Cannot process object ID %ld (object "%.*ls") because it is a Service Broker queue. Try the operation again with the object ID of the corresponding internal table for the queue, found in sys.internal_tables.
2525	16	No	Database file %.*ls is offline.
2526	16	No	Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.
2527	16	No	Unable to process index %.ls of table %.ls because filegroup %.*ls is offline.
2528	10	No	DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2529	16	No	Filegroup %.*ls is offline.
2530	16	No	The index "%.ls" on table "%.ls" is disabled.
2531	16	No	Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID.
2532	16	No	One or more WITH options specified are not valid for this command.
2533	16	No	Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
2534	16	No	Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), is allocated by another object.
2536	10	No	DBCC results for '%.*ls'.
2537	16	No	Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%hs) failed. The values are %I64d and %I64d.
2538	10	No	File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.
2539	10	No	The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.
2540	10	No	The system cannot self repair this error.
2541	10	No	DBCC UPDATEUSAGE: Usage counts updated for table '%.ls' (index '%.ls', partition %ld):
2542	10	No	DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.
2543	10	No	USED pages %.*ls: changed from (%I64d) to (%I64d) pages.
2544	10	No	RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.
2545	10	No	ROWS count: changed from (%I64d) to (%I64d) rows.
2546	10	No	Index '%.ls' on table '%.ls' is marked as disabled. Rebuild the index to bring it online.
2547	16	No	Unable to process object ID %ld (object "%.*ls") because it is a synonym. If the object referenced by the synonym is a table or view, retry the operation using the base object that the synonym references.
2548	10	No	DBCC: Compaction phase of index '%.*ls' is %d%% complete.
2549	10	No	DBCC: Defrag phase of index '%.*ls' is %d%% complete.
2550	16	No	The index "%.ls" (partition %ld) on table "%.ls" cannot be reorganized because it is being reorganized by another process.
2551	16	No	The indexes on table "%.*ls" cannot be reorganized because there is already an online index build or rebuild in progress on the table.
2552	16	No	The index "%.ls" (partition %ld) on table "%.ls" cannot be reorganized because page level locking is disabled.
2553	10	Yes	Table '%.ls' will not be available during reorganizing index '%.ls'. This is because the index reorganization operation performs inside a user transaction and the entire table is exclusively locked.
2554	16	No	The index "%.ls" (partition %ld) on table "%.ls" cannot be reorganized because the filegroup is read-only.
2555	16	No	Cannot move all contents of file "%.*ls" to other places to complete the emptyfile operation.
2556	16	No	There is insufficient space in the filegroup to complete the emptyfile operation.
2557	14	No	User '%.ls' does not have permission to run DBCC %ls for object '%.ls'.
2558	16	No	%I64d incorrect counts were detected in database '%.*ls'.
2559	16	No	The '%ls' and '%ls' options are not allowed on the same statement.
2560	16	No	Parameter %d is incorrect for this DBCC statement.
2561	16	No	Parameter %d is incorrect for this statement.
2562	16	No	Checking FILESTREAM filegroup "%.*ls" (ID %d) is not supported in DBCC CHECKFILEGROUP. Specify a filegroup containing user objects with FILESTREAM data instead.
2566	14	No	DBCC DBREINDEX cannot be used on system tables.
2567	14	No	DBCC INDEXDEFRAG cannot be used on system table indexes
2568	16	No	Page %S_PGID is out of range for this database or is in a log file.
2570	16	No	Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type "%.ls"). Column "%.ls" value is out of range for data type "%.*ls". Update column to a legal value.
2571	14	No	User '%.ls' does not have permission to run DBCC %.ls.
2572	16	No	DBCC cannot free DLL '%.*ls'. The DLL is in use.
2573	16	No	Could not find table or object ID %.*ls. Check system catalog.
2574	16	No	Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree.
2575	16	No	The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.
2576	16	No	The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.
2577	16	No	Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d.
2579	16	No	Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database.
2580	16	No	Table '%.*ls' is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table.
2581	10	No	DBCC cannot free the DLL "%.*ls". The DLL is not loaded.
2583	16	No	An incorrect number of parameters was given to the DBCC statement.
2585	16	No	Cannot find partition number %ld for table "%.*ls".
2586	16	No	Cannot find partition number %ld for index "%.ls", table "%.ls".
2587	16	No	The invalid partition number %ld was specified.
2588	16	No	Cannot find partition number %ld for index ID %d, object ID %d.
2589	16	No	Repair could not fix all errors on the first attempt.
2590	10	Yes	User "%.ls" is modifying bytes %d to %d of page %S_PGID in database "%.ls".
2591	16	No	Cannot find a row in the system catalog with the index ID %d for table "%.*ls".
2592	10	No	Repair: The %ls index successfully rebuilt for the object "%.ls" in database "%.ls".
2593	10	No	There are %I64d rows in %I64d pages for object "%.*ls".
2594	10	No	Cannot process rowset ID %I64d of object "%.ls" (ID %d), index "%.ls" (ID %d), because it resides on filegroup "%.*ls" (ID %d), which was not checked.
2596	16	No	The repair statement was not processed. The database cannot be in read-only mode.
2597	10	No	Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup.
2599	16	No	Cannot switch to in row text in table "%.*ls".
2601	14	No	Cannot insert duplicate key row in object '%.ls' with unique index '%.ls'.
2628	16	No	String or binary data would be truncated in table '%.ls', column '%.ls'. Truncated value: '%.*ls'.
2627	14	No	Violation of %ls constraint '%.ls'. Cannot insert duplicate key in object '%.ls'.
2701	10	No	Database name '%.*ls' ignored, referencing object in tempdb.
2702	16	No	Database '%.*ls' does not exist.
2703	16	No	Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once.
2704	16	No	Invalid partition scheme '%.*ls' specified.
2705	16	No	Column names in each table must be unique. Column name '%.ls' in table '%.ls' is specified more than once.
2706	11	No	Table '%.*ls' does not exist.
2707	16	No	Column '%.ls' in %S_MSG '%.ls' cannot be used in an index or statistics or as a partition key because it depends on a non-schemabound object.
2709	16	No	Column '%.ls' in %S_MSG '%.ls' cannot be used in an index or statistics or as a partition key because it does user or system data access.
2710	16	No	You are not the owner specified for the object '%.*ls' in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT).
2711	16	No	The definition of object "%.ls" in the resource database contains the non-ASCII character "%.ls".
2712	16	No	Database '%.*ls' can not be configured as a distribution database because it has change tracking enabled.
2714	16	No	There is already an object named '%.*ls' in the database.
2715	16	No	Column, parameter, or variable #%d: Cannot find data type %.*ls.
2716	16	No	Column, parameter, or variable #%d: Cannot specify a column width on data type %.*ls.
2717	15	No	The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed (%d).
2719	16	No	Upgrade of database "%.*ls" failed because it contains a user named "sys" which is a reserved user or schema name in this version of SQL Server.
2720	16	No	Cannot schema bind %S_MSG '%.ls' because it references system object '%.ls'.
2722	16	No	Xml data type methods are not allowed in expressions in this context.
2724	10	No	Parameter or variable '%.*ls' has an invalid data type.
2725	16	No	An online operation cannot be performed for %S_MSG '%.ls' because the index contains column '%.ls' of data type text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml, or large CLR type. For a nonclustered index, the column could be an include column of the index. For a clustered index, the column could be any column of the table. If DROP_EXISTING is used, the column could be part of a new or old index. The operation must be performed offline.
2726	16	No	Partition function '%.*ls' uses %d columns which does not match with the number of partition columns used to partition the table or index.
2727	11	No	Cannot find index '%.*ls'.
2728	16	No	Cannot partition on more than %d columns.
2729	16	No	Column '%.ls' in %S_MSG '%.ls' cannot be used in an index or statistics or as a partition key because it is non-deterministic.
2730	11	No	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	16	No	Column '%.*ls' has invalid width: %d.
2732	16	No	Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000.
2733	16	No	The %ls data type is invalid for return values.
2735	16	No	Cannot create primary xml or spatial index '%.ls' on '%.ls' because PRIMARY KEY constraint contains column(s) of type timestamp.
2738	16	No	A table can only have one timestamp column. Because table '%.ls' already has one, the column '%.ls' cannot be added.
2739	16	No	The text, ntext, and image data types are invalid for local variables.
2740	16	No	SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server.
2741	16	No	SET DATEFORMAT date order '%.*ls' is invalid.
2742	16	No	SET DATEFIRST %d is out of range.
2743	16	No	%ls statement requires %S_MSG parameter.
2744	16	No	Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed.
2745	10	No	Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process.
2747	16	No	Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters.
2748	16	No	Cannot specify %ls data type (parameter %d) as a substitution parameter.
2749	16	No	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	16	No	Column or parameter #%d: Specified column precision %d is greater than the maximum precision of %d.
2751	16	No	Column or parameter #%d: Specified column scale %d is greater than the specified precision of %d.
2752	16	No	Identity column '%.*ls' contains invalid SEED.
2753	16	No	Identity column '%.*ls' contains invalid INCREMENT.
2754	16	No	Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option.
2755	16	No	SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH \| NORMAL \| LOW \| [%d ... %d] of type integer}.
2756	16	No	Invalid value %d for state. Valid range is from %d to %d.
2759	16	No	CREATE SCHEMA failed due to previous errors.
2760	16	No	The specified schema name "%.*ls" either does not exist or you do not have permission to use it.
2761	16	No	The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.
2762	16	No	sp_setapprole was not invoked correctly. Refer to the documentation for more information.
2766	16	No	The definition for user-defined data type '%.*ls' has changed.
2767	15	No	Could not locate statistics '%.*ls' in the system catalogs.
2770	16	No	The SELECT INTO statement cannot have same source and destination tables.
2772	16	No	Cannot access temporary tables from within a function.
2773	16	No	The collation ID is corrupted because the sort order ID %d is not valid.
2774	16	No	Collation ID %d is invalid.
2775	16	No	The code page %d is not supported by the server.
2778	16	No	Only System Administrator can specify %s option for %s command.
2779	16	No	The %S_MSG '%.*ls' is an auto-drop system object. It cannot be used in queries or DDL.
2780	16	No	View '%.*ls' is not schemabound.
2782	16	No	Cannot create table "%.*ls": A table must have a clustered primary key in order to have XML data type columns.
2785	16	No	User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this context.
2786	16	No	The data type of substitution parameter %d does not match the expected type of the format specification.
2787	16	No	Invalid format specification: '%.*ls'.
2788	16	No	Synonyms are invalid in a schemabound object or a constraint expression.
2789	16	No	Must specify a two-part name for %S_MSG '%.*ls' in a schemabound object or a constraint expression.
2790	16	No	Cannot use a column of type TEXT, NTEXT, or IMAGE in a constraint expression.
2791	16	No	Could not resolve expression for Schema-bound object or constraint.
2792	16	No	Cannot specify a sql CLR type in a Schema-bound object or a constraint expression.
2793	16	No	Specified owner name '%.*ls' either does not exist or you do not have permission to act on its behalf.
2794	16	No	Message text expects more than the maximum number of arguments (%d).
2795	16	No	Could not %S_MSG %S_MSG because the new %S_MSG '%.ls' does not match the FILESTREAM %S_MSG '%.ls' of the table.
2796	16	No	Cannot specify database name with $partition in a Schema-bound object, computed column or constraint expression.
2797	16	No	The default schema does not exist.
2798	16	No	Cannot create index or statistics '%.ls' on table '%.ls' because SQL Server cannot verify that key column '%.*ls' is precise and deterministic. Consider removing column from index or statistics key, marking computed column persisted, or using non-CLR-derived column in key.
2799	16	No	Cannot create index or statistics '%.ls' on table '%.ls' because the computed column '%.*ls' is imprecise and not persisted. Consider removing column from index or statistics key or marking computed column persisted.
2801	16	No	The definition of object '%.*ls' has changed since it was compiled.
2802	10	No	SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations.
2803	10	No	SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2809	18	No	The request for %S_MSG '%.ls' failed because '%.ls' is a %S_MSG object.
2812	16	No	Could not find stored procedure '%.*ls'.
2813	16	No	%.*ls is not supported on this edition of SQL Server.
2814	10	No	A possible infinite recompile was detected for SQLHANDLE %hs, PlanHandle %hs, starting offset %d, ending offset %d. The last recompile reason was %d.
2628	16	No	String or binary data would be truncated in table '%.ls', column '%.ls'. Truncated value: '%.*ls'.

Errors 3,000 to 3,999

Error	Severity	Event Logged	Description
3002	16	No	Cannot BACKUP or RESTORE a database snapshot.
3003	10	No	This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before attempting to restore this differential backup.
3004	16	No	The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
3005	10	No	The differential partial backup is including a read-only filegroup, '%ls'. This filegroup was read-write when the base partial backup was created, but was later changed to read-only access. We recommend that you create a separate file backup of the '%ls' filegroup now, and then create a new partial backup to provide a new base for later differential partial backups.
3006	16	No	The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups are not allowed in the simple recovery model, and are never allowed for partial differential backups.
3007	16	No	The backup of the file or filegroup "%ls" is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data.
3008	16	No	The specified device type is not supported for backup mirroring.
3009	16	No	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.
3010	16	No	Invalid backup mirror specification. All mirrors must have the same number of members.
3011	16	No	All backup devices must be of the same general class (for example, DISK and TAPE).
3012	17	No	VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer.
3013	16	No	BACKUP DATABASE is terminating abnormally.
3014	10	No	%hs successfully processed %I64d pages in %d.%03d seconds (%d.%03d MB/sec).
3015	10	No	%hs is not yet implemented.
3016	16	No	Backup of file '%ls' is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taking the backup, or restrict the backup to exclude this file.
3017	16	No	The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Correct the problem, or reissue the command without RESTART.
3018	10	No	The restart-checkpoint file '%ls' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
3019	16	No	The restart-checkpoint file '%ls' is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The restart command must use the same syntax as the interrupted command, with the addition of the RESTART clause. Alternatively, reissue the current statement without the RESTART clause.
3021	16	No	Cannot perform a backup or restore operation within a transaction.
3022	10	No	This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate if you plan to set the filegroup to read-only followed by a differential file backup. Consult Books Online for more information on managing read-only data for the simple recovery model. In particular, consider how partial backups are used.
3023	16	No	Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
3024	16	No	You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
3025	16	No	Missing database name. Reissue the statement specifying a valid database name.
3027	16	No	The filegroup "%.ls" is not part of database "%.ls".
3028	10	No	The restart-checkpoint file '%ls' was corrupted and is being ignored. The RESTORE command will continue from the beginning as if RESTART had not been specified.
3031	16	No	Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement.
3032	16	No	One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options.
3033	16	No	BACKUP DATABASE cannot be used on a database opened in emergency mode.
3034	16	No	No files were selected to be processed. You may have selected one or more filegroups that have no members.
3035	16	No	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	16	No	The database "%ls" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire restore sequence is completed.
3038	16	No	The file name "%ls" is invalid as a backup device name. Reissue the BACKUP statement with a valid file name.
3039	16	No	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	10	No	An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected.
3041	16	Yes	BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages.
3042	10	No	BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the errors that were encountered.
3043	16	No	BACKUP '%ls' detected an error on page (%d:%d) in file '%ls'.
3044	16	No	Invalid zero-length device name. Reissue the BACKUP statement with a valid device name.
3045	16	No	BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "%.*ls" is not usable.
3046	16	No	Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
3047	16	No	The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files are stored when full path names are not provided. This path is also used to locate restart checkpoint files for RESTORE.
3049	16	No	BACKUP detected corruption in the database log. Check the errorlog for more information.
3050	16	No	SQL Server could not send the differential information for database file '%ls' of database '%ls\%ls' to the backup application because the differential information is too large to fit in memory, and an attempt to use a temporary file has failed.
3051	16	No	BACKUP LOG was unable to maintain mirroring consistency for database '%ls'. Database mirroring has been suspended.
3054	16	No	Differential file backups can include only read-only data for databases using the simple recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
3055	16	No	Backup destination "%.*ls" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement with a valid backup destination.
3056	16	No	The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file '%ls'.
3057	16	No	Invalid device name. The length of the device name provided exceeds supported limit (maximum length is:%d). Reissue the BACKUP statement with a valid device name.
3058	10	No	File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls.
3098	16	No	The backup cannot be performed because '%ls' was requested after the media was formatted with an incompatible structure. To append to this media set, either omit '%ls' or specify '%ls'. Alternatively, you can create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten.
3101	16	No	Exclusive access could not be obtained because the database is in use.
3102	16	No	%ls cannot process database '%ls' because it is in use by this session. It is recommended that the master database be used when performing this operation.
3103	16	No	A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTORE statement and provide a backup set which includes a full copy of at least the primary data file. The WITH PARTIAL clause of the RESTORE statement may not be used for any other purpose.
3104	16	No	RESTORE cannot operate on database '%ls' because it is configured for database mirroring. Use ALTER DATABASE to remove mirroring if you intend to restore the database.
3105	16	No	RESTORE cannot restore any more pages into file '%ls' because the maximum number of pages (%d) are already being restored. Either complete the restore sequence for the existing pages, or use RESTORE FILE to restore all pages in the file.
3106	16	No	The filegroup "%ls" is ambiguous. The identity in the backup set does not match the filegroup that is currently defined in the online database. To force the use of the filegroup in the backup set, take the database offline and then reissue the RESTORE command.
3107	16	No	The file "%ls" is ambiguous. The identity in the backup set does not match the file that is currently defined in the online database. To force the use of the file in the backup set, take the database offline and then reissue the RESTORE command.
3108	16	No	To restore the master database, the server must be running in single-user mode. For information on starting in single-user mode, see "How to: Start an Instance of SQL Server (sqlservr.exe)" in Books Online.
3109	16	No	Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not supported.
3110	14	No	User does not have permission to RESTORE database '%.*ls'.
3111	16	No	Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored.
3112	16	No	Cannot restore any database other than master when the server is in single user mode.
3113	16	No	Invalid data was detected.
3115	16	No	The database is using the simple recovery model. It is not possible to restore a subset of the read-write data.
3116	16	No	The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore.
3117	16	No	The log or differential backup cannot be restored because no files are ready to rollforward.
3118	16	No	The database "%ls" does not exist. RESTORE can only create a database when restoring either a full backup or a file backup of the primary file.
3119	16	No	Problems were identified while planning for the RESTORE statement. Previous messages provide details.
3120	16	No	This backup set will not be restored because all data has already been restored to a point beyond the time covered by this backup set.
3121	16	No	The file "%ls" is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue.
3122	16	No	File initialization failed. RESTORE cannot continue.
3123	16	No	Invalid database name '%.*ls' specified for backup or restore operation.
3125	16	No	The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the database. Restoring more data is required before recovery is possible. Either restore a full file backup taken since the data was marked read-only, or restore the most recent base backup for the target data followed by a differential file backup.
3127	16	Yes	The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is using the simple recovery model and the file is marked for read-write access. Therefore, only read-only files can be recovered by piecemeal restore.
3128	16	No	File '%ls' has an unsupported page size (%d).
3129	16	No	The contents of the file "%ls" are not consistent with a transition into the restore sequence. A restore from a backup set may be required.
3130	10	No	The filegroup "%ls" is selected. At the time of backup it was known by the name "%ls"'. RESTORE will continue operating upon the renamed filegroup.
3131	10	No	The file "%ls" is selected. At the time of backup it was known by the name "%ls". RESTORE will continue operating upon the renamed file.
3132	16	No	The media set has %d media families but only %d are provided. All members must be provided.
3133	16	No	The volume on device "%ls" is sequence number %d of media family %d, but sequence number %d of media family %d is expected. Check that the device specifications and loaded media are correct.
3134	10	Yes	The differential base attribute for file '%ls' of database '%ls' has been reset because the file has been restored from a backup taken on a conflicting recovery path. The restore was allowed because the file was read-only and was consistent with the current status of the database. Any future differential backup of this file will require a new differential base.
3135	16	No	The backup set in file '%ls' was created by %hs and cannot be used for this restore operation.
3136	16	No	This differential backup cannot be restored because the database has not been restored to the correct earlier state.
3137	16	No	Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files.
3138	16	No	The database cannot be reverted because FILESTREAM BLOBs are present.
3139	16	No	Restore to snapshot is not allowed with the master database.
3140	16	No	Could not adjust the space allocation for file '%ls'.
3141	16	No	The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database.
3142	16	No	File "%ls" cannot be restored over the existing "%ls". Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location.
3143	16	No	The data set on device '%ls' is not a SQL Server backup set.
3144	16	No	File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set.
3145	16	No	The STOPAT option is not supported for databases that use the SIMPLE recovery model.
3147	16	No	Backup and restore operations are not allowed on database tempdb.
3148	16	No	This RESTORE statement is invalid in the current context. The 'Recover Data Only' option is only defined for secondary filegroups when the database is in an online state. When the database is in an offline state filegroups cannot be specified.
3149	16	No	The file or filegroup "%ls" is not in a valid state for the "Recover Data Only" option to be used. Only secondary files in the OFFLINE or RECOVERY_PENDING state can be processed.
3150	10	No	The master database has been successfully restored. Shutting down SQL Server.
3151	21	Yes	Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online.
3153	16	No	The database is already fully recovered.
3154	16	No	The backup set holds a backup of a database other than the existing '%ls' database.
3155	16	No	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	16	No	File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identify a valid location for the file.
3159	16	No	The tail of the log for the database "%ls" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log.
3161	16	No	The primary file is unavailable. It must be restored or otherwise made available.
3163	16	No	The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.
3165	16	No	Database '%ls' was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online.
3166	16	No	RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement.
3167	16	No	RESTORE could not start database '%ls'.
3168	16	No	The backup of the system database on the device %ls cannot be restored because it was created by a different version of the server (%ls) than this server (%ls).
3169	16	No	The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
3170	16	No	The STANDBY filename is invalid.
3171	16	No	File %ls is defunct and cannot be restored into the online database.
3172	16	No	Filegroup %ls is defunct and cannot be restored into the online database.
3173	16	No	The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed up to reach the target point in time. The tail of the log for the database "%ls" has not been backed up. Use BACKUP LOG WITH NORECOVERY to back up the log, or use the WITH REPLACE clause in your RESTORE statement to overwrite the tail of the log.
3174	16	No	The file '%ls' cannot be moved by this RESTORE operation.
3175	10	No	RESTORE FILEGROUP="%ls" was specified, but not all of its files are present in the backup set. File "%ls" is missing. RESTORE will continue, but if you want all files to be restored, you must restore other backup sets.
3176	16	No	File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files.
3178	16	No	File %ls is not in the correct state to have this differential backup applied to it.
3179	16	No	The system database cannot be moved by RESTORE.
3180	16	No	This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.
3181	10	No	Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.
3182	16	No	The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR.
3183	16	No	RESTORE detected an error on page (%d:%d) in database "%ls" as read from the backup set.
3184	10	No	RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible.
3185	16	No	RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage.
3186	16	No	The backup set has been damaged. RESTORE will not attempt to apply this backup set.
3187	16	No	RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
3188	10	No	The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.
3189	16	No	Damage to the backup set was detected.
3190	16	No	Filegroup '%ls' cannot be restored because it does not exist in the backup set.
3191	16	No	Restore cannot continue because file '%ls' cannot be written. Ensure that all files in the database are writable.
3192	10	No	Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that is unavailable. Either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
3194	16	No	Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored.
3195	16	No	Page %S_PGID cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first log or differential backup taken since the file was added to the database.
3196	16	No	RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file.
3197	10	Yes	I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
3198	10	Yes	I/O was resumed on database %ls. No user action is required.
3199	16	No	RESTORE requires MAXTRANSFERSIZE=%u but %u was specified.
3201	16	No	Cannot open backup device '%ls'. Operating system error %ls.
3202	16	No	Write on "%ls" failed: %ls
3203	16	No	Read on "%ls" failed: %ls
3204	16	No	The backup or restore was aborted.
3205	16	No	Too many backup devices specified for backup or restore; only %d are allowed.
3206	16	No	Backup device '%.*ls' does not exist. To view existing backup devices, use the sys.backup_devices catalog view. To create a new backup device use either sp_addumpdevice or SQL Server Management Studio.
3207	16	No	Backup or restore requires at least one backup device. Rerun your statement specifying a backup device.
3208	16	No	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	16	No	Operation is not supported on user instances.
3210	16	No	The mirror member in drive "%ls" is inconsistent with the mirror member in drive "%ls".
3211	10	No	%d percent processed.
3212	16	No	The mirror device "%ls" and the mirror device "%ls" have different device specifications.
3213	16	No	Unable to unload one or more tapes. See the error log for details.
3214	16	No	Too many backup mirrors are specified. Only %d are allowed.
3215	16	No	Use WITH FORMAT to create a new mirrored backup set.
3216	16	No	RESTORE REWINDONLY is only applicable to tape devices.
3217	16	No	Invalid value specified for %ls parameter.
3218	16	No	Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
3219	16	No	The file or filegroup "%.*ls" cannot be selected for this operation.
3221	16	No	The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d.
3222	16	No	The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d.
3224	16	No	Cannot create worker thread.
3227	16	No	The backup media on "%ls" is part of media family %d which has already been processed on "%ls". Ensure that backup devices are correctly specified. For tape devices, ensure that the correct volumes are loaded.
3229	16	No	Request for device '%ls' timed out.
3230	16	No	Operation on device '%ls' exceeded retry count.
3231	16	No	The media loaded on "%ls" is formatted to support %d media families, but %d media families are expected according to the backup device specification.
3232	16	No	The volume mounted on "%ls" does not have the expected backup set identity. The volume may be obsolete due to a more recent overwrite of this media family. In that case, locate the correct volume with sequence number %d of media family %d.
3234	16	No	Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names.
3235	16	No	The file "%.*ls" is not part of database "%ls". You can only list files that are members of this database.
3239	16	No	The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server.
3240	16	No	Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set.
3241	16	No	The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family.
3242	16	No	The file on device '%ls' is not a valid Microsoft Tape Format backup set.
3243	16	No	The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d.
3244	16	No	Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation.
3245	16	No	Could not convert a string to or from Unicode, %ls.
3246	16	No	The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media.
3247	16	No	The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d.
3249	16	No	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	16	No	The value '%d' is not within range for the %ls parameter.
3251	10	No	The media family on device '%ls' is complete. The device is now being reused for one of the remaining families.
3253	16	No	The block size parameter must supply a value that is a power of 2.
3254	16	No	The volume on device '%ls' is empty.
3255	16	No	The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server.
3256	16	No	The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally.
3257	16	No	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	16	No	The volume on the device "%ls" is not part of the media set that is currently being processed. Ensure that the backup devices are loaded with the correct media.
3260	16	No	An internal buffer has become full.
3261	16	No	SQL Server cannot use the virtual device configuration.
3262	10	No	The backup set on file %d is valid.
3263	16	No	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	16	No	The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
3265	16	No	The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE.
3266	16	Yes	The backup data at the end of "%ls" is incorrectly formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on the media, use RESTORE HEADERONLY. To determine the usability of the backup sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reformat the media using BACKUP WITH FORMAT, which destroys all the backup sets.
3267	16	No	Insufficient resources to create UMS scheduler.
3268	16	No	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	16	No	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	16	No	An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance.
3271	16	No	A nonrecoverable I/O error occurred on file "%ls:" %ls.
3272	16	No	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.
3276	16	No	WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.
3277	16	No	WITH SNAPSHOT must be used with only one virtual device.
3278	16	No	Failed to encrypt string %ls
3279	16	No	Access is denied due to a password failure
3280	16	No	Backups on raw devices are not supported. '%ls' is a raw device.
3281	10	No	Released and initiated rewind on '%ls'.
3283	16	No	The file "%ls" failed to initialize correctly. Examine the error logs for more details.
3284	16	No	Filemark on device '%ls' is not aligned. Re-issue the restore statement with the same blocksize used to create the backupset: '%d' looks like a possible value.
3285	10	Yes	Filemark on device '%ls' appears not to be aligned. The restore operation will proceed using less efficient I/O. To avoid this, re-issue the Restore statement with the same blocksize used to create the backupset: '%d' looks like a possible value.
3301	21	Yes	The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database.
3302	21	Yes	Redoing of logged operations in database '%.*ls' failed to reach end of log at log record ID %S_LSN. This indicates corruption around log record ID %S_LSN. Restore the database from a full backup, or repair the database.
3313	21	Yes	During redoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
3314	21	Yes	During undoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
3315	21	Yes	During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database '%.*ls' under transaction %S_XID. Restore a backup of the database, or repair the database.
3316	21	Yes	During undo of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a full backup, or repair the database.
3401	10	Yes	Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery.
3402	10	Yes	The database '%ls' is marked %ls and is in a state that does not allow recovery to be run.
3403	10	Yes	Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
3404	10	Yes	Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
3406	10	Yes	%d transactions rolled forward in database '%.*ls' (%d). This is an informational message only. No user action is required.
3407	10	Yes	%d transactions rolled back in database '%.*ls' (%d). This is an informational message only. No user action is required.
3408	10	Yes	Recovery is complete. This is an informational message only. No user action is required.
3409	16	Yes	Performance counter shared memory setup failed with error %d. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
3410	10	Yes	Data in filegroup %s is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup if you never intend to recover it. Log truncation cannot occur until this condition is resolved.
3411	21	Yes	Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
3412	10	Yes	Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
3413	21	Yes	Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems.
3414	10	Yes	An error occurred during recovery, preventing the database '%.*ls' (database ID %d) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
3415	16	Yes	Database '%.*ls' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
3416	16	Yes	The server contains read-only files that must be made writable before the server can be recollated.
3417	21	Yes	Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
3418	10	Yes	Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain.
3419	16	Yes	Recovery for database '%.*ls' is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence.
3420	21	Yes	Database snapshot '%ls' has failed an IO operation and is marked suspect. It must be dropped and recreated.
3421	10	Yes	Recovery completed for database %ls (database ID %d) in %I64d second(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms.) This is an informational message only. No user action is required.
3422	10	Yes	Database %ls was shutdown due to error %d in routine '%hs'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
3429	10	Yes	Recovery could not determine the outcome of a cross-database transaction %S_XID, named '%.ls', in database '%.ls' (database ID %d). The coordinating database (database ID %d) was unavailable. The transaction was assumed to be committed. If the transaction was not committed, you can retry recovery when the coordinating database is available.
3431	21	Yes	Could not recover database '%.*ls' (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS DTC, restore from a full backup, or repair the database.
3434	20	Yes	Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation.
3437	21	Yes	An error occurred while recovering database '%.*ls'. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again.
3441	21	Yes	During startup of warm standby database '%.*ls' (database ID %d), its standby file ('%ls') was inaccessible to the RESTORE statement. The operating system error was '%ls'. Diagnose the operating system error, correct the problem, and retry startup.
3442	21	Yes	Recovery of warm standby database '%.*ls' (database ID %d) failed. There is insufficient room in the undo file. Increase the size of the undo file and retry recovery.
3443	21	Yes	Database '%.*ls' (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.
3445	21	Yes	File '%ls' is not a valid undo file for database '%.*ls (database ID %d). Verify the file path, and specify the correct file.
3446	16	No	Primary log file is not available for database '%.*ls'. The log cannot be backed up.
3447	16	No	Could not activate or scan all of the log files for database '%.*ls'.
3448	21	Yes	Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. 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. Restore or repair the database.
3449	21	Yes	SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
3450	10	Yes	Recovery of database '%.*ls' (%d) is %d%% complete (approximately %d seconds remain). Phase %d of 3. This is an informational message only. No user action is required.
3452	10	Yes	Recovery of database '%.ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.ls').
3453	16	No	This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible.
3454	10	Yes	Recovery is writing a checkpoint in database '%.*ls' (%d). This is an informational message only. No user action is required.
3456	21	Yes	Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the database.
3457	21	Yes	Transactional file system resource manager '%.*ls' failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.
3458	16	No	Recovery cannot scan database "%.*ls" for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up.
3505	14	No	Only the owner of database "%.*ls" or someone with relevant permissions can run the CHECKPOINT statement.
3604	10	No	Duplicate key was ignored.
3606	10	No	Arithmetic overflow occurred.
3607	10	No	Division by zero occurred.
3608	16	No	Cannot allocate a GUID for the token.
3609	16	No	The transaction ended in the trigger. The batch has been aborted.
3612	10	No	%hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms.
3613	10	No	SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms.
3615	10	No	Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob read-ahead reads %d.
3616	16	No	An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
3619	10	Yes	Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
3620	10	Yes	Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. Automatic checkpointing will be enabled when the database owner successfully checkpoints the database. Contact the database owner to either truncate the log file or add more disk space to the log. Then retry the CHECKPOINT statement.
3621	10	No	The statement has been terminated.
3622	10	No	Warning: An invalid floating point operation occurred.
3623	16	No	An invalid floating point operation occurred.
3624	20	Yes	A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
3625	20	Yes	'%hs' is not yet implemented.
3627	17	Yes	New parallel operation cannot be started due to too many parallel operations executing at this time. Use the "max worker threads" configuration option to increase the number of allowable threads, or reduce the number of parallel operations running on the system.
3628	24	Yes	The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator.
3633	16	Yes	The operating system returned the error '%ls' while attempting '%ls' on '%ls' at '%hs'(%d).
3634	16	Yes	The operating system returned the error '%ls' while attempting '%ls' on '%ls'.
3635	16	Yes	An error occurred while processing '%ls' metadata for database id %d, file id %d, and transaction='%.*ls'. Additional Context='%ls'. Location='%hs'(%d). Retry the operation; if the problem persists, contact the database administrator to review locking and memory configurations. Review the application for possible deadlock conflicts.
3636	16	No	An error occurred while processing '%ls' metadata for database id %d file id %d.
3637	16	No	A parallel operation cannot be started from a DAC connection.
3638	10	No	SQL text cache memory usage: %d pages. This is an informational message only; no user action is required.
3701	11	No	Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission.
3702	16	No	Cannot drop database "%.*ls" because it is currently in use.
3703	16	No	Cannot detach the %S_MSG '%.*ls' because it is currently in use.
3705	16	No	Cannot use DROP %ls with '%.ls' because '%.ls' is a %S_MSG. Use %ls.
3706	16	No	Cannot %S_MSG a database snapshot.
3707	16	No	Cannot detach a suspect or recovery pending database. It must be repaired or dropped.
3708	16	No	Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG.
3709	16	No	Cannot %S_MSG the database while the database snapshot "%.*ls" refers to it. Drop that database first.
3710	16	No	Cannot detach an opened database when the server is in minimally configured mode.
3716	16	No	The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG.
3717	16	No	Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.
3721	16	No	Type '%.ls' cannot be renamed because it is being referenced by object '%.ls'.
3723	16	No	An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement.
3724	16	No	Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for replication.
3725	16	No	The constraint '%.ls' is being referenced by table '%.ls', foreign key constraint '%.*ls'.
3726	16	No	Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint.
3727	10	No	Could not drop constraint. See previous errors.
3728	16	No	'%.*ls' is not a constraint.
3729	16	No	Cannot %ls '%.ls' because it is being referenced by object '%.ls'.
3730	16	No	Cannot drop the default constraint '%.*ls' while it is being used by a foreign key as SET DEFAULT referential action.
3732	16	No	Cannot drop type '%.ls' because it is being referenced by object '%.ls'. There may be other objects that reference this type.
3733	16	No	Constraint '%.ls' does not belong to table '%.ls'.
3734	16	No	Could not drop the primary key constraint '%.*ls' because the table has an XML or spatial index.
3735	16	No	The primary key constraint '%.ls' on table '%.ls' cannot be dropped because change tracking is enabled on the table. Change tracking requires a primary key constraint on the table. Disable change tracking before dropping the constraint.
3737	16	No	Could not delete file '%ls'. See the SQL Server error log for more information.
3738	10	No	Deleting database file '%ls'.
3739	11	No	Cannot %ls the index '%.*ls' because it is not a statistics collection.
3740	16	No	Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup.
3741	16	No	Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on an offline filegroup.
3743	16	No	The database '%.*ls' is enabled for database mirroring. Database mirroring must be removed before you drop the database.
3744	16	No	Only a single clause is allowed in a statement where an index is dropped online.
3745	16	No	Only a clustered index can be dropped online.
3746	16	No	Cannot drop the clustered index of view '%.*ls' because the view is being used for replication.
3747	16	No	Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index '%.ls' is created on view '%.ls'.
3748	16	No	Cannot drop nonclustered index '%.*ls' using drop clustered index clause.
3749	16	No	Cannot drop XML Index '%.*ls' using old 'Table.Index' syntax, use 'Index ON Table' syntax instead.
3750	10	No	Warning: Index '%.ls' on %S_MSG '%.ls' was disabled as a result of disabling the clustered index on the %S_MSG.
3751	16	No	Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with '%.ls' because '%.ls' is a %S_MSG. Use %ls.
3801	10	No	Warning: The index "%.ls" on "%.ls"."%.*ls" may be impacted by the collation upgrade. Run DBCC CHECKTABLE.
3802	10	No	Warning: The constraint "%.ls" on "%.ls"."%.*ls" may be impacted by the collation upgrade. Disable and enable WITH CHECK.
3803	10	No	Warning: The index "%.ls" on "%.ls"."%.*ls" is disabled because the implementation of the checksum function has changed.
3804	10	No	Warning: The check constraint "%.ls" on table "%.ls"."%.*ls" is disabled because the implementation of the checksum function has changed.
3805	10	No	Warning: Index "%.ls" on table "%.ls"."%.ls" might be corrupted because it references computed column "%.ls" containing a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify index. Consider using explicit CONVERT with deterministic date style such as 121. Computed column indexes referencing non-deterministic expressions can't be created in 90 compatibility mode. See Books Online topic "Creating Indexes on Computed Columns" for more information.
3806	10	No	Warning: Indexed view "%.ls"."%.ls" might be corrupted because it contains a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify view. Consider using explicit CONVERT with deterministic date style such as 121. Indexed views referencing non-deterministic expressions can't be created in 90 compatibility mode. See Books Online topic "Creating Indexed Views" for more information.
3807	17	No	Create failed because all available identifiers have been exhausted.
3808	10	No	Warning: The index "%.ls" on "%.ls"."%.*ls" is disabled because the index is defined on a view with ignore_dup_key index option. Drop the index and, if possible, recreate it without ignore_dup_key option. You may need to change the logical structure of the view to ensure all rows are unique.
3809	16	No	Upgrade of database "%.ls" failed because index "%.ls" on object ID %d has the same name as that of another index on the same table.
3810	10	No	Event notification "%.*ls" on assembly is dropped.
3811	10	No	Event notification "%.*ls" on service queue is dropped as broker instance is not specified.
3812	10	No	Event notification "%.*ls" on object is dropped.
3813	16	No	Upgrade of login '%.*ls' failed because its name or sid is a duplicate of another login or server role.
3814	16	No	Local login mapped to remote login '%.ls' on server '%.ls' is invalid. Drop and recreate the remote login before upgrade.
3815	16	No	Local login mapped to linked login '%.ls' on server '%.ls' is invalid. Drop and recreate the linked login before upgrade.
3816	16	No	Upgrade of login '%.*ls' failed because its password hash is invalid. Update the login password before upgrade.
3817	10	No	Warning: The index "%.ls" on "%.ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed.
3818	16	No	CUID column of 6 bytes cannot be added to index "%.ls" on object %.ls because row length would exceed the maximum permissible length of %d bytes.
3819	10	No	Warning: The check constraint "%.ls" on "%.ls"."%.*ls" was disabled and set as not trusted because the implementation of geometry and geography methods have changed.
3820	10	No	Warning: CUID column of 6 bytes has been added to index "%.ls" on object %.ls, but its maximum row size exceeds the allowed maximum of %d bytes. INSERT or UPDATE to this index will fail for some combination of large values.
3821	10	No	Warning: The foreign key constraint "%.ls" on "%.ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed.
3822	10	No	Warning: The heap "%.ls"."%.ls" has persisted computed columns that depends on a geometry or geography methods and may contain out-of-date information. Because of this, DBCC may report inconsistencies on this table. The persisted computed columns depending on geometry or geography methods should be unpersisted and persisted again to refresh the data.
3823	10	No	Warning: The object "%.ls"."%.ls" could not be bound and was ignored during upgrade. Consider reviewing and correcting its definition.
3851	10	No	An invalid row (%ls) was found in the system table sys.%ls%ls.
3852	10	No	Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
3853	10	No	Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
3854	10	No	Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (%ls) in sys.%ls%ls that is invalid.
3855	10	No	Attribute (%ls) exists without a row (%ls) in sys.%ls%ls.
3856	10	No	Attribute (%ls) exists but should not for row (%ls) in sys.%ls%ls.
3857	10	No	The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls.
3858	10	No	The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid value.
3859	10	No	Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE.
3860	10	No	Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use.
3862	10	No	CLR type '%.ls'.'%.ls' is disabled because the on disk format for this CLR type has been changed. Use DROP TYPE to remove this disabled type.
3864	23	Yes	Could not find an entry for index with ID %d on object with ID %d in database with ID %d. Possible schema corruption. Run DBCC CHECKDB.
3901	16	No	The transaction name must be specified when it is used with the mark option.
3902	16	No	The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
3903	16	No	The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
3904	21	No	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	16	No	Failed to update database "%.*ls" because the database is read-only.
3908	16	No	Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in bypass recovery mode.
3909	16	No	Session binding token is invalid.
3910	16	No	Transaction context in use by another session.
3912	16	No	Cannot bind using an XP token while the server is not in an XP call.
3913	16	Yes	TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server.
3914	16	No	The data type "%s" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max).
3915	16	No	Cannot use the ROLLBACK statement within an INSERT-EXEC statement.
3916	16	No	Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
3917	16	No	Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
3918	16	No	The statement or function must be executed in the context of a user transaction.
3919	16	No	Cannot enlist in the transaction because the transaction has already been committed or rolled back.
3920	10	No	The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
3921	16	No	Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started
3922	16	No	Cannot enlist in the transaction because the transaction does not exist.
3923	10	No	Cannot use transaction marks on database '%.*ls' with bulk-logged operations that have not been backed up. The mark is ignored.
3924	10	No	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	16	No	Invalid transaction mark name. The 'LSN:' prefix is reserved.
3926	10	No	The transaction active in this session has been committed or aborted by another session.
3927	10	No	The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction.
3928	16	No	The marked transaction "%.*ls" failed. A timeout occurred while attempting to place a mark in the log by committing the marked transaction. This can be caused by contention with Microsoft Distributed Transaction Coordinator (MS DTC) transactions or other local marked transaction that have prepared, but not committed or aborted. Try the operation again and if the error persists, determine the source of the contention.
3929	16	No	No distributed or bound transaction is allowed in single user database.
3930	16	No	The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
3931	16	No	The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
3932	16	No	The save point name "%.*ls" that was provided is too long. The maximum allowed length is %d characters.
3933	16	No	Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
3934	14	No	The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTION_CONTEXT.
3935	16	No	A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x.
3936	16	No	The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. '%.*ls' was one of the one or more files involved. ErorrCode: 0x%x
3937	16	No	While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver. Error code: 0x%0x.
3938	18	No	The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction. The transaction will be rolled back.
3939	16	No	An uncommittable transaction was detected at the beginning of the batch. The transaction was rolled back. This was caused by an error that occurred during the processing of a FILESTREAM request in the context of this transaction.
3950	16	No	Version store scan timed out when attempting to read the next row. Please try the statement again later when the system is not as busy.
3951	16	No	Transaction failed in database '%.*ls' because the statement was run under snapshot isolation but the transaction did not start in snapshot isolation. You cannot change the isolation level of the transaction to snapshot after the transaction has started unless the transaction was originally started under snapshot isolation level.
3952	16	No	Snapshot isolation transaction failed accessing database '%.*ls' because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation.
3953	16	No	Snapshot isolation transaction failed in database '%.*ls' because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered.
3954	16	No	Snapshot isolation transaction failed to start in database '%.*ls' because the ALTER DATABASE command that disallows snapshot isolation had started before this transaction began. The database is in transition to OFF state. You will either need to change the isolation level of the transaction or re-enable the snapshot isolation in the database.
3955	16	No	Snapshot isolation transaction failed in database '%.*ls' because the recovery was skipped for this database. You must recover the database before you can run a transaction under snapshot isolation.
3956	16	No	Snapshot isolation transaction failed to start in database '%.*ls' because the ALTER DATABASE command which enables snapshot isolation for this database has not finished yet. The database is in transition to pending ON state. You must wait until the ALTER DATABASE Command completes successfully.
3957	16	No	Snapshot isolation transaction failed in database '%.*ls' because the database did not allow snapshot isolation when the current transaction started. It may help to retry the transaction.
3958	16	No	Transaction aborted when accessing versioned row in table '%.ls' in database '%.ls'. Requested versioned row was not found. Your tempdb is probably out of space. Please refer to BOL on how to configure tempdb for versioning.
3959	10	Yes	Version store is full. New version(s) could not be added. A transaction that needs to access the version store may be rolled back. Please refer to BOL on how to configure tempdb for versioning.
3960	16	No	Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table '%.ls' directly or indirectly in database '%.ls' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.
3961	16	No	Snapshot isolation transaction failed in database '%.*ls' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
3962	16	No	Bind to another transaction while executing SQL Server internal query is not supported. Check your logon trigger definition and remove any sp_bindsession usage if any. If this error is not happening during logon trigger execution, contact production support team.
3963	16	No	Transaction failed in database '%.*ls' because distributed transactions are not supported under snapshot isolation.
3964	16	No	Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not versioned, a metadata change can lead to inconsistency if mixed within snapshot isolation.
3965	16	No	The PROMOTE TRANSACTION request failed because there is no local transaction active.
3966	17	No	Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient space in tempdb. This transaction was marked as a victim earlier because it may need the row version(s) that have already been removed to make space in tempdb. Retry the transaction
3967	17	Yes	Insufficient space in tempdb to hold row versions. Need to shrink the version store to free up some space in tempdb. Transaction (id=%I64d xsn=%I64d spid=%d elapsed_time=%d) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning.
3968	10	No	Snapshot isolation or read committed snapshot is not available in database '%.*ls' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
3969	16	No	Distributed transaction is not supported while running SQL Server internal query. Check your logon trigger definition and remove any distributed transaction usage if any. If this error is not happening during logon trigger execution, contact production support team.
3970	16	No	This operation conflicts with another pending operation on this transaction. The operation failed.
3971	16	No	The server failed to resume the transaction. Desc:%I64x.
3972	20	Yes	Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d.
3973	16	No	The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed.
3974	16	No	The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed.
3975	16	No	The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted.
3976	16	No	The transaction name has the odd length %d. The batch has been aborted.
3977	16	No	The savepoint name cannot be NULL. The batch has been aborted.
3978	16	No	Beginning a new transaction after rollback to save point is not allowed.
3979	16	No	The TM request is longer than expected. The request is not processed.
3980	16	No	The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy.
3981	16	No	The transaction operation cannot be performed because there are pending requests working on this transaction.
3982	16	No	New transaction is not allowed to be started while DTC or bound transaction is active.
3983	16	No	The operation failed because the session is not single threaded.
3984	16	No	Cannot acquire a database lock during a transaction change.
3985	16	No	An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.
3986	19	No	The transaction timestamps ran out. Restart the server.
3987	10	No	SNAPSHOT ISOLATION is always enabled in this database.
3988	16	No	New transaction is not allowed because there are other threads running in the session.
3989	16	No	New request is not allowed to start because it should come with valid transaction descriptor.
3990	16	No	Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
3991	16	No	The context transaction which was active before entering user defined routine, trigger or aggregate "%.*ls" has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.
3992	16	No	Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate "%.*ls". This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.
3993	16	No	The user transaction that has been started in user defined routine, trigger or aggregate "%.*ls" is not ended upon exiting from it. This is not allowed and the transaction will be rolled back. Change application logic to enforce strict transaction nesting.
3994	16	No	User defined routine, trigger or aggregate tried to rollback a transaction that is not started in that CLR level. An exception will be thrown to prevent execution of rest of the user defined routine, trigger or aggregate.
3995	16	No	Unknown transaction isolation level %d, valid value range is 0 to 5.
3996	16	No	Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction.
3997	16	No	A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back.
3998	16	No	Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.
3999	17	Yes	Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information.

Errors 4,000 to 4,999

Error	Severity	Event Logged	Description
4001	10	No	Client sends a sp_reset_connection while there is still pending requests, server is disconnecting.
4002	16	No	The incoming tabular data stream (TDS) protocol stream is incorrect. The stream ended unexpectedly.
4004	16	No	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.
4005	16	No	Cannot update columns from more than one underlying table in a single update call.
4006	16	No	You cannot delete rows from more than one underlying table in a single delete call.
4007	16	No	Cannot update or insert column "%.*ls". It may be an expression.
4008	16	No	The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver versions earlier than SQL Server 2005. Please resubmit the query using a more recent client driver.
4009	16	No	The incoming tabular data stream (TDS) protocol stream is incorrect. The TDS headers contained errors.
4010	16	No	The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors.
4011	16	No	The incoming tabular data stream (TDS) protocol stream is incorrect. The MARS TDS header contained errors.
4012	16	No	An invalid tabular data stream (TDS) collation was encountered.
4013	16	No	The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is missing.
4014	20	No	A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %d, output error: %d).
4015	16	No	Language requested in login '%.ls' is not an official name on this SQL Server. Using server-wide default %.ls instead.
4016	16	No	Language requested in 'login %.ls' is not an official name on this SQL Server. Using user default %.ls instead.
4017	16	No	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	16	No	User default language %.ls is not an official language name on this SQL Server. Using server-wide default %.ls instead.
4019	16	No	Language requested in login '%.*ls' is not an official language name on this SQL Server. Login fails.
4020	16	No	Default date order '%.ls' for language %.ls is invalid. Using mdy instead.
4021	16	No	Resetting the connection results in a different state than the initial login. The login fails.
4022	16	No	Bulk load data was expected but not sent. The batch will be terminated.
4027	16	No	Mount tape for %hs of database '%ls' on tape drive '%ls'.
4028	16	No	End of tape has been reached. Remove tape '%ls' and mount next tape for %hs of database '%ls'.
4030	10	No	The medium on device '%ls' expires on %hs and cannot be overwritten.
4035	10	No	Processed %I64d pages for database '%ls', file '%ls' on file %d.
4037	16	No	The user-specified MEDIANAME "%.*ls" does not match the MEDIANAME "%ls" of the device "%ls".
4038	16	No	Cannot find file ID %d on device '%ls'.
4060	11	No	Cannot open database "%.*ls" requested by the login. The login failed.
4061	11	No	Neither the database "%.*ls" requested by the login nor the user default database could be opened. The master database is being used instead.
4062	11	No	Cannot open user default database. Using master database instead.
4063	11	No	Cannot open database "%.ls" that was requested by the login. Using the user default database "%.ls" instead.
4064	11	No	Cannot open user default database. Login failed.
4065	16	Yes	User is trying to use '%.*ls' through ODS, which is not supported any more.
4066	16	No	Type IDs larger than 65535 cannot be sent to clients shipped in SQL Server 2000 or earlier.
4067	16	No	CLR type serialization failed because an invalid cookie was specified.
4068	20	No	sp_resetconnection was sent as part of a remote procedure call (RPC) batch, but it was not the last RPC in the batch. This connection will be terminated.
4069	16	No	The final value of the output parameter was null, and could not be sent to a 6.5 client expecting the parameter to be non-nullable.
4070	16	No	More than 255 columns were specified in the COMPUTE clause, and this metadata cannot be sent to a SQL Server version 6.5 client.
4071	10	No	The XP callback function '%.ls' failed in extended procedure '%.ls' because it was executed within an INSERT-EXEC statement which does not allow the extended procedure to send information other than result set.
4072	10	No	The XP callback function '%.ls' failed in extended procedure '%.ls' because the extended procedure is called inside an UDF which doesn't allow sending data.
4073	16	No	A return value of data type varchar(max), nvarchar(max), varbinary(max), XML or other large object type can not be returned to client driver versions earlier than SQL Server 2005. Please resubmit the query using a more recent client driver.
4074	16	No	Client drivers do not accept result sets that have more than 65,535 columns.
4075	16	No	The USE database statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
4076	16	No	The ALTER DATABASE statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
4077	20	No	The statement failed because the sql_variant value uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
4078	16	No	The statement failed because column '%.ls' (ID=%d) uses collation %.ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations.
4079	16	No	The statement failed due to arithmetic overflow when sending data stream.
4101	16	No	Aggregates on the right side of an APPLY cannot reference columns from the left side.
4102	15	No	The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM clause.
4103	15	No	%.*ls: Temporary views are not allowed.
4104	16	No	The multi-part identifier "%.*ls" could not be bound.
4105	16	No	User-defined functions, partition functions, and column references are not allowed in expressions in this context.
4106	16	No	Non-ANSI outer joins (= and =) are not allowed when a table that contains a column set is used in a query. Change the query to use ANSI outer joins.
4107	16	No	Inserting into remote tables or views is not allowed by using the BCP utility or by using BULK INSERT.
4108	16	No	Windowed functions can only appear in the SELECT or ORDER BY clauses.
4109	16	No	Windowed functions cannot be used in the context of another windowed function or aggregate.
4110	16	No	The argument type "%s" is invalid for argument %d of "%s".
4111	16	No	The CREATE SCHEMA statement should be followed by a name or authorization keyword.
4112	16	No	The ranking function "%.*ls" must have an ORDER BY clause.
4113	16	No	%.*ls is not a valid windowing function, and cannot be used with the OVER clause.
4114	16	No	The function '%.*ls' takes exactly %d argument(s).
4115	16	No	The reference to column "%.*ls" is not allowed in the argument of the TOP clause. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here.
4116	16	No	The function 'ntile' takes only a positive int or bigint expression as its input.
4117	16	No	Cannot retrieve table data for the query operation because the table "%.ls" schema is being altered too frequently. Because the table "%.ls" contains a computed column, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring.
4118	16	No	An invalid expression was specified in the FOR UPDATE clause.
4119	16	No	Default values cannot be assigned to property setters of columns with a CLR type.
4120	16	No	A user-defined function name cannot be prefixed with a database name in this context.
4121	16	No	Cannot find either column "%.ls" or the user-defined function or aggregate "%.ls", or the name is ambiguous.
4122	16	No	Remote table-valued function calls are not allowed.
4124	16	No	The parameters supplied for the batch are not valid.
4126	16	No	No full-text indexed columns were found.
4127	16	No	At least one of the arguments to COALESCE must be a typed NULL.
4128	16	No	An internal error occurred during remote query execution. Contact your SQL Server support professional and provide details about the query you were trying to run.
4129	16	No	The inline function "%.*ls" cannot take correlated parameters or subqueries because it uses a full-text operator.
4130	16	No	A duplicate hint was specified for the BULK rowset.
4131	16	No	A compile-time literal value is specified more than once for the variable "%.*ls" in one or more OPTIMIZE FOR clauses.
4132	16	No	The value specified for the variable "%.*ls" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's type.
4133	16	No	Only a scalar expression may be specified as the argument to the RETURN statement.
4134	16	Yes	Metadata stored on disk for computed column '%.ls' in table '%.ls' did not match the column definition. In order to avoid possible index corruption, please drop and recreate this computed column.
4135	16	No	Synonym '%.ls' is defined over queue '%.ls'. Synonyms on queues are not allowed.
4136	16	No	The hint '%.ls' cannot be used with the hint '%.ls'.
4137	16	No	A format file cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option.
4138	16	No	Conflicting locking hints are specified for table "%.*ls". This may be caused by a conflicting hint specified for a view.
4139	16	No	Cannot process the query because it references the common language runtime (CLR) table-valued function "%.ls" with a hint through view "%.ls".
4140	15	No	The READCOMMITTEDLOCK lock hint is not allowed on the target table of an INSERT statement.
4141	16	No	Nested CLR type updates are not allowed.
4142	16	No	Aggregates are not allowed in the RECEIVE list.
4143	16	No	The bulk openrowset provider is not a valid target for %.*ls.
4144	16	No	The hint '%.*ls' is not allowed when inserting into remote tables.
4145	15	No	An expression of non-boolean type specified in a context where a condition is expected, near '%.*ls'.
4146	16	No	Statistics can only be created on columns.
4147	15	No	The query uses non-ANSI outer join operators ("=" or "="). To run this query without modification, please set the compatibility level for current database to 80, using the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes.
4148	16	No	XML methods are not allowed in a GROUP BY clause.
4150	16	No	Hints are not allowed on recursive common table expression (CTE) references. Consider removing hint from recursive CTE reference '%.*ls'.
4151	16	No	The type of the first argument to NULLIF cannot be the NULL constant because the type of the first argument has to be known.
4152	16	No	Type "%.*ls" is not a CLR type.
4153	16	No	Cannot treat data type "%ls" as data type "%ls".
4154	16	No	UNNEST can only take an expression of type multiset.
4155	15	No	The SELECT list for the nested INSERT statement can only contain one item.
4156	16	No	The target of nested insert, nested update, or nested delete must be of type multiset.
4157	16	No	%.*ls is not a valid property, field, or method.
4158	16	No	The field "%.*ls" is referenced more than once in the set list, either directly or through a property.
4159	16	No	Delayed CLR type instances require local base table column as an argument.
4160	16	No	Could not find suitable key in table '%.*ls' for use in delayed CLR type fetching.
4161	16	No	Only CLR types are allowed in delayed CLR type fetching.
4162	16	No	A PROB_MATCH table can only be used inside of a PROB_MATCH query.
4163	16	No	A GROUP BY clause is required in a PROB_MATCH query.
4164	16	No	A GROUP BY clause in a PROB_MATCH query can only have key columns, and needs to include all the key columns.
4165	16	No	The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same constant and variable.
4166	16	No	Invalid PROB_MATCH subquery.
4167	16	No	Multiple PROB_MATCH subqueries can only refer to the same base table.
4168	16	No	Invalid PROB_MATCH project item in the PROB_MATCH SELECT list.
4169	16	No	Applying TREAT more than once to the same expression is not allowed in a full-text property reference.
4170	16	No	The (ANY) specification can only be applied to expressions of type multiset.
4171	16	No	Alias was not specified for an aggregate in the PROB_MATCH SELECT list.
4172	16	No	Incorrect use of full-text %s.
4173	16	No	%.*s is not a valid scoring function name.
4174	16	No	Delayed CLR type instantiation fetch value query may only reference column of a large object or large value type.
4175	16	No	Nested updates cannot be performed on CLR types that are not Format.Structured.
4176	16	No	Too many parameters were specified for FULLTEXTTABLE of type "Simple". The maximum number of parameters is %d.
4177	16	No	The FROM clause of a PROB_MATCH query must consist of a single derived table.
4184	16	No	Cannot retrieve table data for the query operation because the table "%.ls" schema is being altered too frequently. Because the table "%.ls" contains a filtered index or filtered statistics, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring.
4185	16	No	This action cannot be performed on a system type.
4186	16	No	Column '%ls.%.*ls' cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references a function that performs user or system data access. A function is assumed by default to perform data access if it is not schemabound. Consider removing the subquery or function from the column definition or removing the column from the OUTPUT clause.
4202	16	No	BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable.
4208	16	No	The statement %hs is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
4212	16	No	Cannot back up the log of the master database. Use BACKUP DATABASE instead.
4214	16	No	BACKUP LOG cannot be performed because there is no current database backup.
4215	10	No	The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure the Log Reader Agent or capture job is running or use sp_repldone to mark transactions as distributed or captured.
4217	10	No	BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups will duplicate the work of this backup.
4218	16	No	Bulk-logged operations exist in the database. Perform a BACKUP LOG.
4302	16	No	The option "%ls" conflicts with online restore. Remove the conflicting option and reissue the command.
4303	16	No	The roll forward start point is now at log sequence number (LSN) %.s. Additional roll forward past LSN %.s is required to complete the restore sequence.
4305	16	No	The log in this backup set begins at LSN %.ls, which is too recent to apply to the database. An earlier log backup that includes LSN %.ls can be restored.
4307	16	No	The online restore to database '%ls' failed. It may be appropriate to perform an offline restore instead. To force an offline restore, first take the database offline using the ALTER DATABASE statement.
4308	10	No	The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online.
4309	16	No	The state of file "%ls" prevents restoring individual pages. Only a file restore is currently possible.
4310	16	No	RESTORE PAGE is not allowed on file "%ls" because the file is not online.
4311	16	No	RESTORE PAGE is not allowed from backups taken with earlier versions of SQL Server.
4312	16	No	This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap.
4315	10	No	Some files still require more restore steps before the online restore sequence can be completed.
4318	16	No	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.
4319	16	No	A previous restore operation was interrupted and did not complete processing on file '%ls'. Either restore the backup set that was interrupted or restart the restore sequence.
4320	16	No	The file "%ls" was not fully restored by a database or file restore. The entire file must be successfully restored before applying this backup set.
4322	10	No	This backup set contains records that were logged before the designated point in time. The database is being left in the restoring state so that more roll forward can be performed.
4323	16	No	A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option.
4326	16	No	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	16	No	The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled forward to the end of the log.
4328	16	No	The file "%ls" is missing. Roll forward stops at log sequence number %.ls. The file is created at log sequence number (LSN) %.ls, dropped at LSN %.*ls. Restore the transaction log beyond the point in time when the file was dropped, or restore data to be consistent with rest of the database.
4329	10	No	This log file contains records logged before the designated mark. The database is being left in the Restoring state so you can apply another log file.
4330	16	No	This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time. For more information about recovery paths, see SQL Server Books Online.
4331	16	No	The database cannot be recovered because the files have been restored to inconsistent points in time.
4332	16	No	RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY.
4333	16	No	The database cannot be recovered because the log was not restored.
4334	16	No	The named mark does not identify a valid LSN.
4335	16	No	The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point.
4336	16	No	The filegroup "%ls" has been dropped and cannot be restored into the online database.
4337	16	No	The file "%ls" has been dropped and cannot be restored into the online database.
4338	16	No	The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use RESTORE DATABASE WITH RECOVERY to recover at the current point.
4339	10	No	This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are needed. Previous messages indicate reasons why recovery cannot occur at this point.
4340	16	No	The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause or use a clause that includes a timestamp.
4341	16	No	This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time.
4342	16	No	Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence. Omit the point-in-time clause or restore the primary filegroup.
4343	16	No	The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY can be used to accept the current recovery point.
4344	16	No	RESTORE PAGE is not allowed on read-only databases or filegroups.
4345	10	No	Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information.
4346	16	No	RESTORE PAGE is not allowed with databases that use the simple recovery model.
4347	16	No	The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH RECOVERY can be used to complete the transition to online.
4348	16	No	The online restore to database '%ls' failed. It may be appropriate to perform an offline restore instead. An offline restore is initiated by using BACKUP LOG WITH NORECOVERY.
4349	16	No	The log in this backup set begins at LSN %.ls, which is too recent to apply to the database. This restore sequence needs to initialize the log to start at LSN %.ls. Reissue the RESTORE LOG statement using an earlier log backup.
4350	16	No	The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %d pages were correctly identified. The problem was hit at character offset %d. Check that all pages are identified by numeric <file>:<page> pairs with commas separating each pair. For example: PAGE='1:57,2:31'.
4351	16	No	Backups taken on earlier versions of SQL Server are not supported by fn_dump_dblog.
4352	16	No	RESTORE LOG is not supported from this data backup because file '%ls' is too old. Use a regular log backup to continue the restore sequence.
4353	16	No	Conflicting file relocations have been specified for file '%.*ls'. Only a single WITH MOVE clause should be specified for any logical file name.
4354	10	Yes	The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is being upgraded from a prior version. Piecemeal restore is not supported when an upgrade is involved.
4355	16	No	The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE <x> FROM DATABASE_SNAPSHOT = <y>.
4356	10	No	Restore is complete on database '%ls'. The database is now available.
4357	16	No	Restore cannot take '%ls' offline because changes exist that require a log backup. Take a log backup and then retry the RESTORE.
4358	16	No	The database can not be brought online because file '%ls' is currently restored to LSN %.ls but must be restored to LSN %.ls.
4359	16	No	The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. The CONTINUE_AFTER_ERROR option can be used to force the recovery, but this should only be used if you do not intend to subsequently restore the FILESTREAM filegroups.
4360	16	No	RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
4403	16	No	Cannot update the view or function '%.*ls' because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
4405	16	No	View or function '%.*ls' is not updatable because the modification affects multiple base tables.
4406	16	No	Update or insert of view or function '%.*ls' failed because it contains a derived or constant field.
4408	19	Yes	Too many tables. The query and the views or functions in it exceed the limit of %d tables. Revise the query to reduce the number of tables.
4413	16	No	Could not use view or function '%.*ls' because of binding errors.
4414	16	No	Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%d) was exceeded.
4415	16	No	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	16	No	UNION ALL view '%.*ls' is not updatable because the definition contains a disallowed construct.
4417	16	No	Derived table '%.*ls' is not updatable because the definition contains a UNION operator.
4418	16	No	Derived table '%.*ls' is not updatable because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
4420	16	No	Derived table '%.*ls' is not updatable because the modification affects multiple base tables.
4421	16	No	Derived table '%.*ls' is not updatable because a column of the derived table is derived or constant.
4422	16	No	View '%.*ls' has an INSTEAD OF UPDATE trigger and cannot be a target of an UPDATE FROM statement.
4423	16	No	View '%.*ls' has an INSTEAD OF DELETE trigger and cannot be a target of a DELETE FROM statement.
4424	16	No	Joined tables cannot be specified in a query containing outer join operators. View or function '%.*ls' contains joined tables.
4425	16	No	Cannot specify outer join operators in a query containing joined tables. View or function '%.*ls' contains outer join operators.
4426	16	No	View '%.*ls' is not updatable because the definition contains a UNION operator.
4427	16	No	Cannot update the view "%.*ls" because it or a view it references was created with WITH CHECK OPTION and its definition contains the TOP clause.
4429	16	No	View or function '%.*ls' contains a self-reference. Views or functions cannot reference themselves directly or indirectly.
4430	10	No	Warning: Index hints supplied for view '%.*ls' will be ignored.
4431	16	No	Partitioned view '%.ls' is not updatable because table '%.ls' has a timestamp column.
4432	16	No	Partitioned view '%.ls' is not updatable because table '%.ls' has a DEFAULT constraint.
4433	16	No	Cannot INSERT into partitioned view '%.ls' because table '%.ls' has an IDENTITY constraint.
4434	16	No	Partitioned view '%.ls' is not updatable because table '%.ls' has an INSTEAD OF trigger.
4435	16	No	Partitioned view '%.ls' is not updatable because a value was not specified for partitioning column '%.ls'.
4436	16	No	UNION ALL view '%.*ls' is not updatable because a partitioning column was not found.
4437	16	No	Partitioned view '%.*ls' is not updatable as the target of a bulk operation.
4438	16	No	Partitioned view '%.*ls' is not updatable because it does not deliver all columns from its member tables.
4439	16	No	Partitioned view '%.ls' is not updatable because the source query contains references to partition table '%.ls'.
4440	16	No	UNION ALL view '%.ls' is not updatable because a primary key was not found on table '%.ls'.
4441	16	No	Partitioned view '%.ls' is not updatable because the table '%.ls' has an index on a computed column.
4442	16	No	UNION ALL view '%.ls' is not updatable because base table '%.ls' is used multiple times.
4443	16	No	UNION ALL view '%.ls' is not updatable because column '%.ls' of base table '%.*ls' is used multiple times.
4444	16	No	UNION ALL view '%.ls' is not updatable because the primary key of table '%.ls' is not included in the union result.
4445	16	No	UNION ALL view '%.ls' is not updatable because the primary key of table '%.ls' is not unioned with primary keys of preceding tables.
4446	16	No	Cannot update the UNION ALL view "%.ls" because the definition of column "%.ls" of view "%.*ls" is used by another view column.
4447	16	No	View '%.*ls' is not updatable because the definition contains a set operator.
4448	16	No	Cannot INSERT into partitioned view '%.*ls' because values were not supplied for all columns.
4449	16	No	Using defaults is not allowed in views that contain a set operator.
4450	16	No	Cannot update partitioned view '%.ls' because the definition of the view column '%.ls' in table '%.*ls' has an IDENTITY constraint.
4451	16	No	Views referencing tables on multiple servers are not updatable in the edition of this SQL Server instance '%.*ls'. See books online for more details on feature support in different SQL Server editions.
4452	16	No	Cannot UPDATE partitioning column '%.ls' of view '%.ls' because the table '%.*ls' has a CASCADE DELETE or CASCADE UPDATE constraint.
4453	16	No	Cannot UPDATE partitioning column '%.ls' of view '%.ls' because the table '%.*ls' has a INSERT, UPDATE or DELETE trigger.
4454	16	No	Cannot update the partitioned view "%.*ls" because the partitioning columns of its member tables have mismatched types.
4456	16	No	The partitioned view "%.*ls" is not updatable because one or more of the non-partitioning columns of its member tables have mismatched types.
4457	16	No	The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions.
4502	16	No	View or function '%.*ls' has more column names specified than columns defined.
4503	16	No	Could not create schemabound %S_MSG '%.*ls' because it references an object in another database.
4504	16	No	Could not create %S_MSG '%.ls' because CLR type '%.ls' does not exist in the target database '%.*ls'.
4505	16	No	CREATE VIEW failed because column '%.ls' in view '%.ls' exceeds the maximum of %d columns.
4506	16	No	Column names in each view or function must be unique. Column name '%.ls' in view or function '%.ls' is specified more than once.
4508	16	No	Views or functions are not allowed on temporary tables. Table names that begin with '#' denote temporary tables.
4510	16	No	Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable.
4511	16	No	Create View or Function failed because no column name was specified for column %d.
4512	16	No	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	16	No	Cannot schema bind %S_MSG '%.ls'. '%.ls' is not schema bound.
4514	16	No	CREATE FUNCTION failed because a column name is not specified for column %d.
4515	16	No	CREATE FUNCTION failed because column '%.ls' in function '%.ls' exceeds the maximum of %d columns.
4516	16	No	Cannot schema bind function '%.*ls' because it contains an EXECUTE statement.
4517	16	No	Service queue object cannot be used in schemabinding expressions. '%.*ls' is a service queue.
4519	16	No	Cannot %S_MSG %S_MSG '%.ls' on view '%.ls' because it is a system generated view that was created for optimization purposes.
4520	16	No	Cannot disable index on view '%.*ls' because it is a system generated view that was created for optimization purposes.
4521	16	No	Cannot use object '%.*ls' with autodrop object attribute in schemabinding expressions because it is a system generated view that was created for optimization purposes.
4522	16	No	Cannot alter view '%.*ls' because it is a system generated view that was created for optimization purposes.
4523	16	No	Cannot create trigger on view '%.*ls' because it is a system generated view that was created for optimization purposes.
4602	14	No	Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission.
4604	16	No	There is no such user or group '%.*ls' or you do not have permission.
4606	16	No	Granted or revoked privilege %ls is not compatible with object.
4610	16	No	You can only grant or revoke permissions on objects in the current database.
4611	16	No	To revoke or deny grantable privileges, specify the CASCADE option.
4613	16	No	Grantor does not have GRANT permission.
4615	16	No	Invalid column name '%.*ls'.
4616	16	No	You cannot perform this operation for the resource database.
4617	16	No	Cannot grant, deny or revoke permissions to or from special roles.
4618	16	No	You do not have permission to use %.*ls in the AS clause.
4619	16	No	CREATE DATABASE permission can only be granted in the master database.
4620	16	No	All permissions in a grant/deny/revoke statement should be at the same scope (e.g., server or database)
4621	16	No	Permissions at the server scope can only be granted when the current database is master
4622	16	No	Permissions at the server scope can only be granted to logins
4623	16	No	The all permission has been deprecated and is not available for this class of entity
4624	16	No	Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
4625	16	No	There is no such server principal %.*s or you do not have permission.
4627	16	No	Cannot grant, deny, or revoke the connect database permission to roles and application roles.
4628	16	No	The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
4629	16	No	Permissions on server scoped catalog views or system stored procedures or extended stored procedures can be granted only when the current database is master.
4701	16	No	Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
4707	16	No	Could not truncate object '%.ls' because it or one of its indexes resides on a READONLY filegroup '%.ls'.
4708	16	No	Could not truncate object '%.*ls' because it is not a table.
4709	16	No	You are not allowed to truncate the system table '%.*ls'.
4710	16	No	Could not truncate object '%.ls' because it or one of its indexes resides on an offline filegroup '%.ls'.
4711	16	No	Cannot truncate table '%.*ls' because it is published for replication or enabled for Change Data Capture.
4712	16	No	Cannot truncate table '%.*ls' because it is being referenced by a FOREIGN KEY constraint.
4801	16	No	Insert bulk is not supported over this access protocol.
4802	16	No	The SINGLE_LOB, SINGLE_CLOB, and SINGLE_NCLOB options are mutually exclusive with all other options.
4803	21	Yes	The bulk copy (bcp) client has sent a row length of %d. This is not a valid size. The maximum row size is %d. Use a supported client application programming interface (API).
4804	21	Yes	While reading current row from host, a premature end-of-message was encountered--an incoming data stream was interrupted when the server expected to see more data. The host program may have terminated. Ensure that you are using a supported client application programming interface (API).
4805	17	No	The front-end tool you are using does not support bulk load from host. Use the supported tools for this command.
4806	16	No	SINGLE_CLOB requires a double-byte character set (DBCS) (char) input file. The file specified is Unicode.
4807	21	Yes	The bulk copy (bcp) client sent a row length of %d. This size is not valid. The minimum row size is %d. Use a supported client application programming interface (API).
4808	16	No	Bulk copy operations cannot trigger bulk load statements.
4809	16	No	SINGLE_NCLOB requires a UNICODE (widechar) input file. The file specified is not Unicode.
4810	16	No	Expected the TEXT token in data stream for bulk copy of text or image data.
4811	16	No	Expected the column offset in data stream for bulk copy of text or image data.
4812	16	No	Expected the row offset in data stream for bulk copy of text or image data.
4813	16	No	Expected the text length in data stream for bulk copy of text, ntext, or image data.
4814	16	No	Bulk copy into a partitioned table is not supported for down-level clients.
4815	16	No	Received an invalid column length from the bcp client for colid %d.
4816	16	No	Invalid column type from bcp client for colid %d.
4817	16	No	Could not bulk load. The sorted column '%.*ls' is not valid. The ORDER hint is ignored.
4818	16	No	Could not bulk load. The sorted column '%.*ls' was specified more than once. The ORDER hint is ignored.
4819	16	No	Cannot bulk load. The bulk data stream was incorrectly specified as sorted or the data violates a uniqueness constraint imposed by the target table. Sort order incorrect for the following two rows: primary key of first row: %s, primary key of second row: %s.
4820	16	No	Cannot bulk load. Unknown version of format file "%s".
4821	16	No	Cannot bulk load. Error reading the number of columns from the format file "%s".
4822	16	No	Cannot bulk load. Invalid number of columns in the format file "%s".
4823	16	No	Cannot bulk load. Invalid column number in the format file "%s".
4824	16	No	Cannot bulk load. Invalid data type for column number %d in the format file "%s".
4825	16	No	Cannot bulk load. Invalid prefix for column number %d in the format file "%s".
4826	16	No	Cannot bulk load. Invalid column length for column number %d in the format file "%s".
4827	16	No	Cannot bulk load. Invalid column terminator for column number %d in the format file "%s".
4828	16	No	Cannot bulk load. Invalid destination table column number for source column %d in the format file "%s".
4829	16	No	Cannot bulk load. Error reading the destination table column name for source column %d in the format file "%s".
4830	10	No	Bulk load: DataFileType was incorrectly specified as char. DataFileType will be assumed to be widechar because the data file has a Unicode signature.
4831	10	No	Bulk load: DataFileType was incorrectly specified as widechar. DataFileType will be assumed to be char because the data file does not have a Unicode signature.
4832	16	No	Bulk load: An unexpected end of file was encountered in the data file.
4833	16	No	Bulk load: Version mismatch between the provider dynamic link library and the server executable.
4834	16	No	You do not have permission to use the bulk load statement.
4835	16	No	Bulk copying into a table with computed columns is not supported for downlevel clients.
4836	10	No	Warning: Table "%.*s" is published for merge replication. Reinitialize affected subscribers or execute sp_addtabletocontents to ensure that data added is included in the next synchronization.
4837	16	No	Cannot bulk copy into a table "%.*s" that is enabled for immediate-updating subscriptions.
4838	16	No	The bulk data source does not support the SQLNUMERIC or SQLDECIMAL data types.
4839	16	No	Cannot perform the bulk load. Invalid collation name for source column %d in the format file "%s".
4840	16	No	The bulk data source provider string has an invalid %ls property value %ls.
4841	16	No	The data source name is not a simple object name.
4842	16	No	The required FormatFile property is missing from the provider string of the server.
4843	16	No	The bulk data source provider string has a syntax error ('%lc') near character position %d.
4844	16	No	The bulk data source provider string has an unsupported property name (%ls).
4845	16	No	The bulk data source provider string has a syntax error near character position %d. Expected '%lc', but found '%lc'.
4846	16	No	The bulk data provider failed to allocate memory.
4847	16	No	Bulk copying into a table with bigint columns is not supported for versions earlier than SQL Server 2000.
4848	16	No	Bulk copying into a table with sql_variant columns is not supported for versions earlier than SQL Server 2000.
4855	16	No	Line %d in format file "%ls": unexpected element "%ls".
4856	16	No	Line %d in format file "%ls": unexpected info item.
4857	16	No	Line %d in format file "%ls": Attribute "%ls" could not be specified for this type.
4858	16	No	Line %d in format file "%ls": bad value %ls for attribute "%ls".
4859	16	No	Line %d in format file "%ls": required attribute "%ls" is missing.
4860	16	No	Cannot bulk load. The file "%ls" does not exist.
4861	16	No	Cannot bulk load because the file "%ls" could not be opened. Operating system error code %ls.
4862	16	No	Cannot bulk load because the file "%ls" could not be read. Operating system error code %ls.
4863	16	No	Bulk load data conversion error (truncation) for row %d, column %d (%ls).
4864	16	No	Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls).
4865	16	No	Cannot bulk load because the maximum number of errors (%d) was exceeded.
4866	16	No	The bulk load failed. The column is too long in the data file for row %d, column %d. Verify that the field terminator and row terminator are specified correctly. Bulk load failed due to invalid column value in CSV data file %ls in row %d, column %d
4867	16	No	Bulk load data conversion error (overflow) for row %d, column %d (%ls).
4868	16	No	The bulk load failed. The codepage "%d" is not installed. Install the codepage and run the command again.
4869	16	No	The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL.
4870	16	No	Cannot bulk load because of an error writing file "%ls". Operating system error code %ls.
4879	16	No
4871	16	No	Bulk load error while attempting to log errors.
4872	16	No	Line %d in format file "%ls": duplicate element id "%ls".
4873	16	No	Line %d in format file "%ls": referencing non-existing element id "%ls".
4874	16	No	Line %d in format file "%ls": duplicate element id reference "%ls".
4875	16	No	Invalid column attribute from bcp client for colid %d.
4876	16	No	The Bulk Insert operation of SQL Server Destination has timed out. Please consider increasing the value of Timeout property on the SQL Server Destination in the dataflow.
4877	16	No	Error parsing DTS stream when reading row %d, column %d.
4880	16	No	Cannot bulk load. When you use the FIRSTROW and LASTROW parameters, the value for FIRSTROW cannot be greater than the value for LASTROW.
4881	10	No	Note: Bulk Insert through a view may result in base table default values being ignored for NULL columns in the data file.
4882	16	No	Cannot bulk load. A prefix length, field length, or terminator is required for the source column %d in the format file "%s".
4883	16	No	The XML reader returned 0x%08X for the info item starting near line %d column %d in format file "%ls".
4884	16	No	Unknown error near info item starting near line %d column %d in format file "%ls".
4885	16	No	Cannot open file "%ls". A Windows NT Integrated Security login is required.
4886	16	No	Cannot open the file "%ls". Operating system error: %ls
4887	16	No	Cannot open the file "%ls". Only disk files are supported.
4888	16	No	Cannot open the file "%ls". The bulkadmin role membership is required.
4889	16	No	Cannot open the file "%ls". A unicode byte-order mark is missing.
4890	16	No	Insert bulk is not supported in showplan mode.
4891	16	No	Insert bulk failed due to a schema change of the target table.
4892	16	No	Bulk insert failed due to a schema change of the target table.
4893	16	No	Could not bulk load because SSIS file mapping object '%ls' could not be opened. Operating system error code %ls. Make sure you are accessing a local server via Windows security.
4894	21	Yes	COLMETADATA must be present when using bcp.
4895	21	Yes	Unicode data is odd byte size for column %d. Should be even byte size.
4896	16	No	Invalid column value from bcp client for colid %d.
4897	16	No	Received an invalid length for chunked LOB data for colid %d.
4900	16	No	The ALTER TABLE SWITCH statement failed for table '%.*ls'. It is not possible to switch the partition of a table that has change tracking enabled. Disable change tracking before using ALTER TABLE SWITCH.
4901	16	No	ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column '%.ls' cannot be added to non-empty table '%.ls' because it does not satisfy these conditions.
4902	16	No	Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
4903	10	No	Warning: The specified partition %d for the table '%.*ls' was ignored in ALTER TABLE SWITCH statement because the table is not partitioned.
4904	16	No	ALTER TABLE SWITCH statement failed. The specified partition %d of target table '%.*ls' must be empty.
4905	16	No	ALTER TABLE SWITCH statement failed. The target table '%.*ls' must be empty.
4906	16	No	'%ls' statement failed. The %S_MSG '%.ls' is %S_MSG partitioned while index '%.ls' is %S_MSG partitioned.
4907	16	No	'%ls' statement failed. The %S_MSG '%.ls' has %d partitions while index '%.ls' has %d partitions.
4908	16	No	'%ls' statement failed. The range boundary values used to partition the %S_MSG '%.ls' are different from the range boundary values used for index '%.ls'.
4909	16	No	Cannot alter '%.*ls' because it is not a table.
4911	16	No	Cannot specify a partitioned table without partition number in ALTER TABLE SWITCH statement. The table '%.*ls' is partitioned.
4912	16	No	'%ls' statement failed. The columns set used to partition the %S_MSG '%.ls' is different from the column set used to partition index '%.ls'.
4913	16	No	ALTER TABLE SWITCH statement failed. The table '%.ls' has clustered index '%.ls' while the table '%.*ls' does not have clustered index.
4914	16	No	The ALTER TABLE SWITCH statement failed. The table "%.*ls" has a disabled clustered index.
4915	16	No	'%ls' statement failed. The parameter type of the partition function used to partition the %S_MSG '%.ls' is different from the parameter type of the partition function used to partition index '%.ls'.
4916	16	No	Could not enable or disable the constraint. See previous errors.
4917	16	No	Constraint '%.*ls' does not exist.
4918	16	No	ALTER TABLE SWITCH statement failed because the table '%.*ls' has fulltext index on it.
4919	16	No	PERSISTED attribute cannot be altered on column '%.*ls' because this column is not computed.
4920	16	No	ALTER TABLE failed because trigger '%.ls' on table '%.ls' does not exist.
4921	16	No	ALTER TABLE failed because trigger '%.ls' does not belong to table '%.ls'.
4922	16	No	%ls %.*ls failed because one or more objects access this column.
4923	16	No	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	16	No	%ls failed because column '%.ls' does not exist in table '%.ls'.
4925	16	No	ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%.*ls' with ROWGUIDCOL property.
4926	16	No	ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%.*ls' with ROWGUIDCOL property.
4927	16	No	Cannot alter column '%.ls' to be data type %.ls.
4928	16	No	Cannot alter column '%.*ls' because it is '%ls'.
4929	16	No	Cannot alter the %S_MSG '%.*ls' because it is being published for replication.
4933	16	No	Computed column '%.ls' in table '%.ls' cannot be persisted because the column depends on a non-schemabound object.
4934	16	No	Computed column '%.ls' in table '%.ls' cannot be persisted because the column does user or system data access.
4935	16	No	ALTER TABLE ADD COLUMN cannot specify a FILESTREAM filegroup that differs from the existing one.
4936	16	No	Computed column '%.ls' in table '%.ls' cannot be persisted because the column is non-deterministic.
4938	16	No	ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.ls' is in filegroup '%.ls' and partition %d of %S_MSG '%.ls' is in filegroup '%.ls'.
4939	16	No	ALTER TABLE SWITCH statement failed. %S_MSG '%.ls' is in filegroup '%.ls' and partition %d of %S_MSG '%.ls' is in filegroup '%.ls'.
4940	16	No	ALTER TABLE SWITCH statement failed. %S_MSG '%.ls' is in filegroup '%.ls' and %S_MSG '%.ls' is in filegroup '%.ls'.
4941	16	No	ALTER TABLE SWITCH statement failed because the table '%.*ls' is marked for merge replication.
4942	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' at ordinal %d in table '%.ls' has a different name than the column '%.ls' at the same ordinal in table '%.ls'.
4943	16	No	ALTER TABLE SWITCH statement failed because table '%.ls' has %d columns and table '%.ls' has %d columns.
4944	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' has data type %s in source table '%.ls' which is different from its type %s in target table '%.*ls'.
4945	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same collation in tables '%.ls' and '%.*ls'.
4946	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same persistent attribute in tables '%.ls' and '%.*ls'.
4947	16	No	ALTER TABLE SWITCH statement failed. There is no identical index in source table '%.ls' for the index '%.ls' in target table '%.*ls' .
4948	16	No	ALTER TABLE SWITCH statement failed. The source table '%.ls' is in database '%.ls' while the target table '%.ls' is in database '%.ls'.
4949	16	No	ALTER TABLE SWITCH statement failed because the object '%.*ls' is not a user defined table.
4950	16	No	ALTER TABLE SWITCH statement failed because partition number %d does not exist in table '%.*ls'.
4951	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same FILESTREAM storage attribute in tables '%.ls' and '%.*ls'.
4952	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same ANSI trimming semantics in tables '%.ls' and '%.*ls'.
4953	16	No	ALTER TABLE SWITCH statement failed. The columns set used to partition the table '%.ls' is different from the column set used to partition the table '%.ls'.
4954	16	No	ALTER TABLE SWITCH statement failed. The table '%.ls' has inline limit of %d for text in row data which is different from value %d used by table '%.ls'.
4955	16	No	ALTER TABLE SWITCH statement failed. The source table '%.ls' and target table '%.ls' are same.
4956	16	No	ALTER TABLE SWITCH statement failed because the table '%.*ls' is not RANGE partitioned.
4957	16	No	'%ls' statement failed because the expression identifying partition number for the %S_MSG '%.*ls' is not of integer type.
4958	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same ROWGUIDCOL property in tables '%.ls' and '%.*ls'.
4959	16	No	ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.ls' has TEXT filegroup '%.ls' and partition %d of %S_MSG '%.ls' has TEXT filegroup '%.ls'.
4960	16	No	ALTER TABLE SWITCH statement failed. Check constraint '%.ls' in source table '%.ls' is NOCHECK constraint but the matching check constraint '%.ls' in target table '%.ls' is CHECK.
4961	16	No	ALTER TABLE SWITCH statement failed. Column '%.ls' in table '%.ls' is nullable and it is not nullable in '%.*ls'.
4962	16	No	ALTER TABLE SWITCH statement failed. Partition %d in table '%.*ls' is not a range partition.
4963	16	No	ALTER TABLE SWITCH statement failed. Partition %d is not valid for table '%.*ls'.
4964	16	No	ALTER TABLE SWITCH statement failed. Table '%.ls' has RULE constraint '%.ls'. SWITCH is not allowed on tables with RULE constraints.
4965	16	No	ALTER TABLE SWITCH statement failed. Column '%.ls' in table '%.ls' is computed column but the same column in '%.*ls' is not computed.
4966	16	No	ALTER TABLE SWITCH statement failed. Computed column '%.ls' defined as '%.ls' in table '%.ls' is different from the same column in table '%.ls' defined as '%.*ls'.
4967	16	No	ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table '%.ls' contains primary key for constraint '%.ls'.
4968	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has foreign key for constraint '%.ls' but source table '%.*ls' does not have corresponding key.
4969	16	No	ALTER TABLE SWITCH statement failed. Foreign key constraint '%.ls' is disabled in source table '%.ls' and the corresponding constraint '%.ls' is enabled in target table '%.ls'. The source table constraint must be enabled.
4970	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has a table level check constraint '%.ls' but the source table '%.*ls' does not have a corresponding constraint.
4971	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has a column level check constraint '%.ls' but the source table '%.*ls' does not have a corresponding constraint.
4972	16	No	ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table '%.ls' allows values that are not allowed by check constraints or partition function on target table '%.ls'.
4973	16	No	ALTER TABLE SWITCH statement failed. Range defined by partition %d in table '%.ls' is not a subset of range defined by partition %d in table '%.ls'.
4974	16	No	ALTER TABLE SWITCH statement failed. Foreign key constraint '%.ls' is NOCHECK in source table '%.ls' and the corresponding constraint '%.ls' is CHECK in target table '%.ls'. The source table constraint must be in CHECK.
4975	16	No	ALTER TABLE SWITCH statement failed. Check constraint '%.ls' in source table '%.ls' and check constraint '%.ls' in target table '%.ls' have different 'Not For Replication' settings.
4976	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has a check constraint '%.ls' on an XML column, but the source table '%.*ls' does not have an identical check constraint.
4977	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has a check constraint '%.ls' on a CLR type column, but the source table '%.*ls' does not have an identical check constraint.
4978	16	No	ALTER TABLE SWITCH statement failed. The partition %d in table '%.ls' resides in a read-only filegroup '%.ls'.
4979	16	No	ALTER TABLE SWITCH statement failed. The table '%.ls' resides in a readonly filegroup '%.ls'.
4980	16	No	ALTER TABLE SWITCH statement failed. The lobdata of partition %d in table '%.ls' resides in a readonly filegroup '%.ls'.
4981	16	No	ALTER TABLE SWITCH statement failed. The lobdata of table '%.ls' resides in a readonly filegroup '%.ls'.
4982	16	No	ALTER TABLE SWITCH statement failed. Check constraints of source table '%.ls' allow values that are not allowed by range defined by partition %d on target table '%.ls'.
4983	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' has an XML or spatial index '%.ls' on it. Only source table can have XML or spatial indexes in the ALTER TABLE SWITCH statement.
4984	16	No	ALTER TABLE SWITCH statement failed. Target table '%.ls' and source table '%.ls' have different vardecimal storage format values. Use stored procedure sp_tableoption to alter the 'vardecimal storage format' option for the tables to make sure that the values are the same.
4985	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same nullability attribute in tables '%.ls' and '%.*ls'.
4986	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same CLR type in tables '%.ls' and '%.*ls'.
4987	16	No	ALTER TABLE SWITCH statement failed because column '%.ls' does not have the same XML Schema Collection in tables '%.ls' and '%.*ls'.
4988	16	No	Cannot persist computed column '%.ls'. Underlying object '%.ls' has a different owner than table '%.*ls'.
4989	16	No	Cannot drop the ROWGUIDCOL property for column '%.ls' in table '%.ls' because the column is not the designated ROWGUIDCOL for the table.
4990	16	No	Cannot alter column '%.ls' in table '%.ls' to add or remove the FILESTREAM column attribute.
4991	16	No	Cannot alter NOT FOR REPLICATION attribute on column '%.ls' in table '%.ls' because this column is not an identity column.
4992	16	No	Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values computed column that are persisted.
4993	16	No	ALTER TABLE SWITCH statement failed. The table '%.ls' has different setting for Large Value Types Out Of Row table option as compared to table '%.ls'.
4994	16	No	Computed column '%.ls' in table '%.ls' cannot be persisted because the column type, '%.*ls', is a non-byte-ordered CLR type.
4995	16	No	Vardecimal storage format cannot be enabled on table '%.ls' because database '%.ls' is a system database. Vardecimal storage format is not available in system databases.
4996	16	No	Change tracking is already enabled for table '%.*ls'.
4997	16	No	Cannot enable change tracking on table '%.*ls'. Change tracking requires a primary key on the table. Create a primary key on the table before enabling change tracking.
4998	16	No	Change tracking is not enabled on table '%.*ls'.
4999	16	No	Cannot enable change tracking on table '%.*ls'. Change tracking does not support a primary key of type timestamp on a table.

Errors 5,000 to 5,999

Error	Severity	Event Logged	Description
5001	16	No	User must be in the master database.
5002	16	No	Database '%.*ls' does not exist. Verify the name in sys.databases and try the operation again.
5003	16	No	Database mirroring cannot be enabled while the database has offline files.
5004	16	No	To use ALTER DATABASE, the database must be in a writable state in which a checkpoint can be executed.
5006	16	No	Could not get exclusive use of %S_MSG '%.*ls' to perform the requested operation.
5008	16	No	This ALTER DATABASE statement is not supported. Correct the syntax and execute the statement again.
5009	16	No	One or more files listed in the statement could not be found or could not be initialized.
5010	16	No	Log file name cannot be generated from a raw device. The log file name and path must be specified.
5011	14	No	User does not have permission to alter database '%.*ls', the database does not exist, or the database is not in a state that allows access checks.
5012	16	No	The name of the primary filegroup cannot be changed.
5013	16	No	The master and model databases cannot have files added to them. ALTER DATABASE was aborted.
5014	16	No	The %S_MSG '%.ls' does not exist in database '%.ls'.
5015	16	No	ALTER DATABASE failed. The total size specified must be 1 MB or greater.
5016	16	No	Cannot change the name of the system database %.*ls.
5018	10	No	The file "%.*ls" has been modified in the system catalog. The new path will be used the next time the database is started.
5019	10	No	Cannot find entry in sys.master_files for file '%.*ls'.
5020	16	No	The primary data or log file cannot be removed from a database.
5021	10	No	The %S_MSG name '%.*ls' has been set.
5022	16	No	Log file '%ls' for this database is already active.
5023	16	No	The database must be suspect or in emergency mode to rebuild the log.
5024	16	No	No entry found for the primary log file in sysfiles1. Could not rebuild the log.
5025	16	No	The file '%ls' already exists. It should be renamed or deleted so that a new log file can be created.
5027	16	No	System databases master, model, and tempdb cannot have their logs rebuilt.
5028	16	No	The system could not activate enough of the database to rebuild the log.
5029	10	Yes	Warning: The log for database '%.*ls' has been rebuilt. Transactional consistency has been lost. The RESTORE chain was broken, and the server no longer has context on the previous log files, so you will need to know what they were. You should run DBCC CHECKDB to validate physical consistency. The database has been put in dbo-only mode. When you are ready to make the database available for use, you will need to reset database options and delete any extra log files.
5030	16	No	The database could not be exclusively locked to perform the operation.
5031	16	No	Cannot remove the file '%.*ls' because it is the only file in the DEFAULT filegroup.
5032	10	No	The file cannot be shrunk below page %ud until the log is backed up because it contains bulk logged pages.
5033	16	No	The maximum of %ld files per database has been exceeded.
5034	16	No	The file %ls is currently being autogrown or modified by another process. Try the operation again later.
5035	16	No	Filegroup '%.*ls' already exists in this database. Specify a different name or remove the conflicting filegroup if it is empty.
5036	16	No	MODIFY FILE failed. Specify logical name.
5038	16	No	MODIFY FILE failed for file "%.*ls". At least one property per file must be specified.
5039	16	No	MODIFY FILE failed. Specified size is less than or equal to current size.
5040	16	No	MODIFY FILE failed. Size is greater than MAXSIZE.
5041	16	No	MODIFY FILE failed. File '%.*ls' does not exist.
5042	16	No	The %S_MSG '%.*ls' cannot be removed because it is not empty.
5043	16	No	The %S_MSG '%.*ls' cannot be found in %ls.
5044	10	No	The %S_MSG '%.*ls' has been removed.
5045	16	No	The %S_MSG already has the '%ls' property set.
5046	10	No	The %S_MSG property '%ls' has been set.
5047	16	No	Cannot change the READONLY property of the PRIMARY filegroup.
5048	16	No	Cannot add, remove, or modify files in filegroup '%.*ls'. The filegroup is read-only.
5050	16	No	Cannot change the properties of empty filegroup '%.*ls'. The filegroup must contain at least one file.
5051	16	No	Cannot have a filegroup with the name 'DEFAULT'.
5052	16	No	%ls is not permitted while a database is in the %ls state.
5054	16	No	Could not cleanup worktable IAM chains to allow shrink or remove file operation. Please try again when tempdb is idle.
5055	16	No	Cannot add, remove, or modify file '%.*ls'. The file is read-only.
5056	16	No	Cannot add, remove, or modify a file in filegroup '%.*ls' because the filegroup is not online.
5057	16	No	Cannot add, remove, or modify file '%.*ls' because it is offline.
5058	16	No	Option '%.ls' cannot be set in database '%.ls'.
5059	16	No	Database '%.*ls' is in transition. Try the ALTER DATABASE statement later.
5060	10	No	Nonqualified transactions are being rolled back. Estimated rollback completion: %d%%.
5061	16	No	ALTER DATABASE failed because a lock could not be placed on database '%.*ls'. Try again later.
5062	16	No	The option "%.*ls" conflicts with another requested option. The options cannot both be requested at the same time.
5063	16	No	Database '%.*ls' is in warm standby. A warm-standby database is read-only.
5064	16	No	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	16	No	The file "%ls" is currently being scanned or used by a background or user process. Try the operation again later.
5066	16	No	Database options single user and dbo use only cannot be set at the same time.
5067	16	No	The database option TORN_PAGE_DETECTION is incompatible with the PAGE_CHECKSUM option.
5068	10	No	Failed to restart the current database. The current database is switched to master.
5069	16	No	ALTER DATABASE statement failed.
5070	16	No	Database state cannot be changed while other users are using the database '%.*ls'
5071	16	No	Rebuild log can only specify one file.
5072	16	No	ALTER DATABASE failed. The default collation of database '%.ls' cannot be set to %.ls.
5073	16	No	Cannot alter collation for database '%ls' because it is READONLY, OFFLINE, or marked SUSPECT.
5074	16	No	The %S_MSG '%.ls' is dependent on %S_MSG '%.ls'.
5075	16	No	The %S_MSG '%.*ls' is dependent on %S_MSG. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
5076	10	No	Warning: Changing default collation for database '%.*ls', which is used in replication. All replication databases should have the same default collation.
5077	16	No	Cannot change the state of non-data files or files in the primary filegroup.
5078	16	No	Cannot alter database options for "%ls" because it is READONLY, OFFLINE, or marked SUSPECT.
5079	10	No	Database "%.*ls" is %S_MSG for vardecimal storage format.
5080	16	No	Vardecimal storage format cannot be disabled for database "%.*ls" because the database is not under simple recovery model. Change the database recovery model to simple and then reissue the command.
5082	16	No	Cannot change the versioning state on database "%.*ls" together with another database state.
5083	16	No	The termination option is not supported when making versioning state changes.
5084	10	Yes	Setting database option %ls to %ls for database %.*ls.
5085	16	No	Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling database for versioning.
5086	16	No	Cannot disable vardecimal storage format for database "%.*ls" because there are one or more tables that have vardecimal storage format enabled. Disable the vardecimal storage format on all tables before disabling the vardecimal storage format for the database.
5087	16	No	The file content type mismatches with the content type of the filegroup.
5088	16	No	Change tracking is already enabled for database '%.*ls'.
5089	16	No	Change tracking is disabled for database '%.*ls'. Change tracking must be enabled on a database to modify change tracking settings.
5090	16	No	Database '%.*ls' is a system database. Change tracking settings cannot be modified for system databases.
5091	15	No	ALTER DATABASE change tracking option '%ls' was specified more than once. Each option can be specified only once.
5092	15	No	The value for change tracking option '%ls' is not valid. The value must be between %d and %d minutes.
5093	16	No	The operation cannot be performed on a database snapshot.
5094	16	No	The operation cannot be performed on a database with database snapshots or active DBCC replicas.
5095	16	No	A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file "%ls" before attempting to transition to read-only.
5096	16	No	The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file "%ls" before attempting to transition to SIMPLE.
5097	16	No	The container cannot be set to the offline state because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE statement.
5098	16	No	The container can not be dropped because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE operation.
5099	16	No	ALTER DATABASE failed because the READ_COMMITTED_SNAPSHOT and the ALLOW_SNAPSHOT_ISOLATION options cannot be set to ON when a database has FILESTREAM filegroups. To set READ_COMMITTED_SNAPSHOT or ALLOW_SNAPSHOT_ISOLATION to ON, you must remove the FILESTREAM filegroups from the database.
5102	22	No	Attempted to open a filegroup for the invalid ID %d in database "%.*ls".
5103	16	No	MAXSIZE cannot be less than SIZE for file '%ls'.
5104	16	No	File '%.*ls' already used.
5105	16	Yes	A file activation error occurred. The physical file name '%.*ls' may be incorrect. Diagnose and correct additional errors, and retry the operation.
5108	10	No	Log file '%.*ls' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
5110	16	No	The file "%.*ls" is on a network path that is not supported for database files.
5111	10	No	File activation failure. The physical file name "%.*ls" may be incorrect.
5112	10	Yes	FCB::SetSize dbid %d fileid %d oldSize %d newSize %d. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF to turn off the trace flag.
5113	10	No	The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure.
5114	16	No	Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. "%.*ls" is not an eligible file for a database snapshot.
5115	16	No	Only SQL Server database files can be specified for database snapshots. '%.*ls' is not a SQL Server database file.
5118	16	No	The file "%ls" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
5119	16	No	Cannot make the file "%.*ls" a sparse file. Make sure the file system supports sparse files.
5120	16	No	Unable to open the physical file "%.*ls". Operating system error %d: "%ls".
5121	16	No	The path specified by "%.*ls" is not in a valid directory.
5123	16	No	CREATE FILE encountered operating system error %ls while attempting to open or create the physical file '%.*ls'.
5124	16	Yes	The file header in '%ls' does not match the expected contents for file '%ls' of database '%ls'. The mismatch is possibly between the full-text catalog files and the related database. Perform a restore if necessary.
5125	24	No	File '%ls' appears to have been truncated by the operating system. Expected size is %I64d KB but actual size is %I64d KB.
5127	16	No	All files must be specified for database snapshot creation. Missing the file "%ls".
5128	17	No	Write to sparse file '%ls' failed due to lack of disk space.
5129	10	No	The log cannot be rebuilt when the primary file is read-only.
5130	10	No	The log cannot be rebuilt when database mirroring is enabled.
5131	10	No	The log was not rebuilt because there is more than one log file.
5132	16	No	The path specified by '%.*ls' cannot be used for FILESTREAM files because it is a raw device.
5133	16	No	Directory lookup for the file "%ls" failed with the operating system error %ls.
5134	16	No	The path that is specified by '%.*ls' cannot be used for FILESTREAM files because it is not on a supported file system.
5135	16	No	The path '%.*ls' cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online.
5136	16	No	The path specified by '%.*ls' cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container.
5144	10	Yes	Autogrow of file '%.ls' in database '%.ls' was cancelled by user or timed out after %d milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.
5145	10	Yes	Autogrow of file '%.ls' in database '%.ls' took %d milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
5149	16	No	MODIFY FILE encountered operating system error %ls while attempting to expand the physical file '%ls'.
5150	16	No	The size of a single log file must not be greater than 2 TB.
5159	24	No	Operating system error %.ls on file "%.ls" during %ls.
5161	16	Yes	An unexpected file id was encountered. File id %d was expected but %d was read from "%.*ls". Verify that files are mapped correctly in sys.master_files. ALTER DATABASE can be used to correct the mappings.
5169	16	No	FILEGROWTH cannot be greater than MAXSIZE for file '%.*ls'.
5170	16	Yes	Cannot create file '%ls' because it already exists. Change the file path or the file name, and retry the operation.
5171	16	No	%.*ls is not a primary database file.
5172	16	No	The header for file '%ls' is not a valid database file header. The %ls property is incorrect.
5173	16	Yes	One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
5174	16	No	Each file size must be greater than or equal to 512 KB.
5175	10	Yes	The file %.*ls has been expanded to allow recovery to succeed. After recovery completes, you can increase the size of the files in the database. Contact the system administrator for assistance.
5176	10	Yes	To allow recovery to succeed, the log file '%.*ls' has been expanded beyond its maximum size. After recovery completes, you should either increase the size of the log file in the database or schedule more frequent backups of the log (under the full or bulk-logged recovery model).
5177	16	Yes	An unexpected error occurred while checking the sector size for file '%.*ls'. Move the file to a local NTFS volume, where the sector size can be retrieved. Check the SQL Server error log for more information.
5178	16	Yes	Cannot use file '%.*ls' because it was originally formatted with sector size %d and is now on a volume with sector size %d. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
5179	16	Yes	Cannot use file '%.*ls', because it is on a volume with sector size %d. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
5180	22	Yes	Could not open File Control Bank (FCB) for invalid file ID %d in database '%.*ls'. Verify the file location. Execute DBCC CHECKDB.
5181	16	No	Could not restart database "%.*ls". Reverting to the previous status.
5182	10	Yes	New log file '%.*ls' was created.
5183	16	No	Cannot create the file "%ls". Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite an existing file.
5184	16	No	Cannot use file '%.*ls' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.
5185	16	No	Cannot find the matching log file for FILESTRAM file '%.*ls'.
5186	16	No	Encountered an error (NT status code 0x%x) while attempting to start the Transactional File System Resource Manager '%.*ls'.
5188	16	No	Encountered error (NT status code 0x%x) while attempting to perform redo for transactional file system resource manager '%.*ls'.
5189	16	No	Encountered error (NT status code 0x%x) while attempting to perform undo for transactional file system resource manager '%.*ls'.
5190	16	No	Encountered error (NT status code 0x%x) while attempting to checkpoint transactional file system resource manager '%.*ls'.
5194	16	No	The size for FILESTREAM log file '%.*ls' must be greater than or equal to 1 MB.
5195	16	No	The Cluster Service function call '%s' failed with error code '%s' while verifying the file path. Verify that your failover cluster is configured properly.
5196	10	No	The file "%ls" has been uncompressed.
5197	16	No	Encountered an error (%ls) while attempting to uncompress the file "%ls".
5198	16	No	The path specified by "%.*ls" is a UNC path. UNC path is not supported in failover clustered environment.
5199	16	No	The path specified by "%.*ls" is a raw device. Raw device path is not supported in failover clustered environment.
5201	10	No	DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because the file does not have enough free space to reclaim.
5202	10	No	DBCC SHRINKDATABASE for database ID %d is waiting for the snapshot transaction with timestamp %I64d and other snapshot transactions linked to timestamp %I64d or with timestamps older than %I64d to finish.
5203	10	No	DBCC SHRINKFILE for file ID %d is waiting for the snapshot transaction with timestamp %I64d and other snapshot transactions linked to timestamp %I64d or with timestamps older than %I64d to finish.
5204	16	No	Could not find allocation unit ID %I64d. Check sys.allocation_units.
5205	10	No	%.*ls: Moving page %d:%d failed.
5206	10	No	%.*ls: Page %d:%d could not be moved because it could not be read.
5207	10	No	%.*ls: Page %d:%d could not be moved because it is a work table page.
5208	10	No	%.*ls: Page %d:%d could not be moved because it is a work file page.
5209	10	No	%.*ls: Page %d:%d could not be moved because it is a dedicated allocation page.
5210	10	No	%.*ls: Page %d:%d could not be moved because it is an invalid page type.
5211	10	No	%.*ls: Page %d:%d could not be moved because it was deallocated during shrink.
5212	10	No	%.*ls: System table SYSFILES1 Page %d:%d could not be moved to other files because it only can reside in the primary file of the database.
5213	10	No	%.*ls: Page %d:%d could not be moved because its ownership was changed during shrink.
5214	10	No	%.*ls: Page %d:%d could not be moved because its page type was changed during shrink.
5215	10	No	%.*ls: Page %d:%d could not be moved because the partition to which it belonged was dropped.
5216	10	No	%.*ls: Heap page %d:%d could not be moved because the table to which it belonged was dropped.
5217	10	No	%.*ls: Page %d:%d could not be moved because it is an empty non-leaf level index page.
5218	10	No	%.*ls: Heap page %d:%d could not be moved because the table name could not be found.
5219	10	No	%.*ls: Heap page %d:%d could not be moved.
5220	10	No	%.*ls: Index Allocation Map (IAM) page %d:%d could not be moved.
5221	10	No	%.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allocation unit could not be moved.
5222	10	No	%.*ls: Page %d:%d from a dropped allocation unit could not be deallocated.
5223	10	No	%.*ls: Empty page %d:%d could not be deallocated.
5224	10	No	%.*ls: Empty large object page %d:%d could not be deallocated.
5225	10	No	%.*ls: Not all ghost records on the large object page %d:%d could be removed.
5226	10	No	%.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallocated.
5227	10	No	%.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallocated.
5228	16	No	Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. DBCC detected incomplete cleanup from an online index build operation. (The anti-matter column value is %d.)
5229	16	No	Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contains an anti-matter column, but is not a nonclustered index.
5230	10	No	The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB.
5231	10	No	Object ID %ld (object '%.*ls'): A deadlock occurred while trying to lock this object for checking. This object has been skipped and will not be processed.
5232	10	No	DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
5233	16	No	Table error: alloc unit ID %I64d, page %S_PGID. The test (%hs) failed. The values are %ld and %ld.
5234	10	No	DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because trying to adjust the space allocation for the file was failed.
5235	10	No	%lsDBCC %ls (%ls%ls%ls)%ls executed by %ls terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds.
5236	10	No	Unable to process object '%ls' because it is a four-part name, which is not supported by any DBCC command.
5237	10	No	DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to an internal query error.
5238	16	No	Unable to process object ID %ld (object '%.*ls') because it is a stored procedure or user-defined function, which is not supported by any DBCC command.
5239	16	No	Unable to process object ID %ld (object '%.*ls') because this DBCC command does not support objects of this type.
5240	10	No	File ID %d of database ID %d cannot be shrunk as it is either being shrunk by another process or is empty.
5241	10	No	File ID %d of database ID %d cannot be shrunk as the target shrink size (%I64d KB) is greater than the actual file size (%I64d KB).
5242	16	No	An inconsistency was detected during an internal operation in database '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support.
5243	16	No	An inconsistency was detected during an internal operation. Please contact technical support.
5244	16	No	Repair statement not processed. One or more files in the database are read-only and must be made writeable in order to run repair.
5245	16	No	Object ID %ld (object '%.*ls'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed.
5246	16	No	Repair operations cannot be performed on the MSSQLSYSTEMRESOURCE database. Consult Books Online topic "Resource Database" for more information.
5247	16	No	Repair: insert a secondary index row based on its base table row.
5248	10	No	Repair: Successfully %ls row in index "%ls" in database "%ls".
5249	10	No	%.*ls: Page %d:%d could not be moved because shrink could not lock the page.
5250	16	No	Database error: %ls page %S_PGID for database '%.*ls' (database ID %d) is invalid. This error cannot be repaired. You must restore from backup.
5251	10	No	%.*ls: Heap page %d:%d could not be moved because maintaining NC indexes associated with the heap failed.
5252	10	No	File ID %d of database ID %d cannot be shrunk to the expected size. The high concurrent workload is leading to too many deadlocks during the shrink operation. Re-run the shrink operation when the workload is lower.
5253	10	No	The check statement was aborted. DBCC CHECKALLOC cannot be run on TEMPDB.
5254	10	No	%.*ls: Heap page %d:%d could not be moved because the table to which it belonged was building the heap by another process.
5255	10	No	%.*ls: Page %d:%d could not be moved because it is a sort page.
5256	16	No	Table error: alloc unit ID %I64d, page %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID.
5257	10	No	%.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation.
5258	10	No	%.*ls: Heap page %d:%d could not be moved because building computed column expression failed.
5259	10	No	%.*ls: Heap page %d:%d could not be moved because populating computed column expression failed.
5260	16	No	Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): At least one record on page %S_PGID contains versioning information, but the VERSION_INFO bit in the page header is not set.
5261	10	No	%.*ls: Page %d:%d could not be moved because it has not been formatted.
5262	16	No	Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row contains a NULL versioning timestamp, but its version chain pointer is not NULL. Version chain points to page %S_PGID, slot %d.
5263	10	No	Found incorrect count(s) for table '%.ls', index '%.ls', partition %ld:
5264	10	No	DATA pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
5265	10	No	USED pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
5266	10	No	RSVD pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
5267	10	No	ROWS count: From system table - %I64d rows; Actual - %I64d rows.
5268	10	No	DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required.
5269	16	No	Check terminated. The transient database snapshot for database '%.*ls' (database ID %d) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details.
5270	10	No	%.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table.
5271	10	No	DBCC %ls could not output results for this command due to an internal failure. Review other errors for details.
5272	10	No	%.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively.
5273	10	No	%.*ls: Page %d:%d could not be moved because it belonged to an index/heap that was/is in build online.
5274	16	No	Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. %S_MSG is invalid for compressed page; the following internal test failed: %hs. Values are %ld and %ld.
5275	10	No	Exhaustive search of '%.*ls' (database ID %d) for inconsistencies completed. Processed %d of %d total searches. Elapsed time: %I64d milliseconds. This is an informational message only. No user action is required.
5276	10	No	Exhaustive search of '%.*ls' (database ID %d) for inconsistencies failed due to exception %d, state %d. This is an informational message only. No user action is required.
5277	10	No	Internal %lsdatabase snapshot has split point LSN = %08x:%08x:%04x and first LSN = %08x:%08x:%04x. This is an informational message only. No user action is required.
5301	16	No	Bulk load failed. User does not have ALTER TABLE permission on table '%.*ls'. ALTER TABLE permission is required on the target table of a bulk load if the target table contains triggers or check constraints, but the 'FIRE_TRIGGERS' or 'CHECK_CONSTRAINTS' bulk hints are not specified. ALTER TABLE permission is also required if the 'KEEPIDENTITY' bulk hint is specified.
5302	16	No	Mutator '%.ls' on '%.ls' cannot be called on a null value.
5303	16	No	The result of applying mutator '%.ls' on CLR type '%.ls' cannot be a null value.
5304	16	No	Bulk copy failed. User does not have ALTER TABLE permission on table '%.*ls'. ALTER TABLE permission is required on the target table of a bulk copy operation if the table has triggers or check constraints, but 'FIRE_TRIGGERS' or 'CHECK_CONSTRAINTS' bulk hints are not specified as options to the bulk copy command.
5305	16	No	The rowdump and lockres columns are only valid on tables and indexed views on which the NOEXPAND hint is specified.
5306	16	No	Cursor parameters are not allowed for functions. Variable '%.*ls' is of type cursor.
5307	16	No	Invalid parameter specified for sp_cursoropen.
5308	16	No	Windowed functions do not support integer indices as ORDER BY clause expressions.
5309	16	No	Windowed functions do not support constants as ORDER BY clause expressions.
5310	16	No	Aggregates are not allowed in the VALUES list of an INSERT statement.
5311	16	No	Invalid quote character '%lc'. A remote server or user command used an invalid quote character.
5312	16	No	The input to the function 'ntile' cannot be bound.
5313	16	No	Synonym '%.*ls' refers to an invalid object.
5315	16	No	The target of a MERGE statement cannot be a remote table, a remote view, or a view over remote tables.
5316	16	No	The target '%.*ls' of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the MERGE statement. In a MERGE statement, if any action has an enabled INSTEAD OF trigger on the target, then all actions must have enabled INSTEAD OF triggers.
5317	16	No	The target of a MERGE statement cannot be a partitioned view.
5318	16	No	In a MERGE statement, the source and target cannot have the same name or alias. Use different aliases for the source and target to ensure that they have unique names in the MERGE statement.
5319	16	No	Aggregates are not allowed in a WHEN clause of a MERGE statement.
5321	16	No	The '%ls' function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5322	16	No	An aggregate function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5323	15	No	Subqueries are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5324	15	No	In a MERGE statement, a '%S_MSG' clause with a search condition cannot appear after a '%S_MSG' clause with no search condition.
5325	15	No	The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset '%.*ls'. The order of the data must match the order specified in the ORDER hint for a BULK rowset. Update the ORDER hint to reflect the order in which the input data is ordered, or update the input data file to match the order specified by the ORDER hint.
5326	15	No	The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset '%.*ls'. The data in the data file must be unique if the UNIQUE hint is specified for a BULK rowset. Remove the UNIQUE hint, or update the input data file to ensure that the data is unique.
5327	15	No	The column '%.ls' does not have a valid data type for the ORDER hint specified for data source '%.ls'. The text, ntext, image, xml, varchar(max), nvarchar(max) and varbinary(max) data types cannot be used in the ORDER hint for a BULK rowset or CLR TVF.
5328	15	No	Cannot insert explicit value for the identity column '%.ls' in the target table '%.ls' of the INSERT statement when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5329	15	No	Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5330	16	No	Full-text predicates cannot appear in the OUTPUT clause.
5331	16	No	Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
5332	15	No	The order of the data in the stream does not conform to the ORDER hint specified for the CLR TVF '%.*ls'. The order of the data must match the order specified in the ORDER hint for a CLR TVF. Update the ORDER hint to reflect the order in which the input data is ordered, or update the CLR TVF to match the order specified by the ORDER hint.
5333	16	No	The identifier '%.*ls' cannot be bound. Only source columns are allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
5334	16	No	The identifier '%.*ls' cannot be bound. Only target columns are allowed in the 'WHEN NOT MATCHED BY SOURCE' clause of a MERGE statement.
5501	16	No	The FILESTREAM filegroup was dropped before the table can be created.
5502	16	No	The FILESTREAM container is inaccessible.
5503	10	No	Unable to find entry in sys.database_files for FILESTREAM file '%.*ls'.
5504	15	No	'PRIMARY' can only be specified for FILESTREAM log filegroup in a 'CONTAINS' clause.
5505	16	No	A table with FILESTREAM column(s) must have a non-NULL unique ROWGUID column.
5506	15	No	FILESTREAM data or log file cannot be named 'DEFAULT'.
5507	15	No	DEFAULT cannot be specified for FILESTREAM log filegroup '%.*ls'.
5508	15	No	FILESTREAM can only be declared for VARBINARY columns.
5509	15	No	The properties SIZE, MAXSIZE, or FILEGROWTH cannot be specified for the FILESTREAM data file '%.*ls'.
5510	15	No	LOG ON cannot be used for non-FILESTREAM file group '%.*ls'.
5511	23	No	FILESTREAM's file system log record '%.ls' under log folder '%.ls' is corrupted.
5512	16	Yes	Error 0x%x (%ls) was encountered while directory '%.*ls' was being truncated.
5513	16	No	The name that is specified for the associated log filegroup for FILESTREAM filegroup '%.*ls' is not valid.
5514	16	No	Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%.*ls' is not started.
5515	20	No	Cannot open the container directory '%.*ls' of the FILESTREAM file. The operating system has returned the Windows status code 0x%x.
5516	16	No	The FILESTREAM log filegroup '%.*ls' cannot be referred to by more than one FILESTREAM data filegroup.
5517	16	No	Too few or too many files specified for FILESTREAM(LOG) filegroup '%.*ls'.
5518	16	No	FILESTREAM path '%.*ls' is too long.
5519	16	No	A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups.
5520	16	No	FILESTREAM file '%.*ls' cannot be added because its destination filegroup cannot have more than one file.
5521	16	No	Error 0x%x (NT status code) was encountered when SQL Server attempts to retrieve '%.ls' from the Transaction File System Resource Manager located at '%.ls'.
5522	16	No	FILESTREAM data file cannot be removed because its log file has not been backed up.
5523	16	No	FILESTREAM data file group cannot be added to refer to an empty FILESTREAM log file group.
5524	16	No	Default FILESTREAM data filegroup cannot be removed unless it's the last FILESTREAM data filegroup left.
5525	16	No	The READ_ONLY, READ_WRITE, and ONLINE/OFFLINE properties cannot be modified on a FILESTREAM log filegroup.
5526	16	No	The FILESTREAM log file '%.*ls' cannot be removed because it is being referenced by a FILESTREAM data filegroup.
5527	16	No	The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist.
5528	16	No	A database can have at most one primary FILESTREAM log filegroup and log file.
5531	16	No	Error 0x%x (NT status code) was encountered when SQL Server attempts to change the logging mode of Transaction File System Resource Manager located at '%.ls' from '%.ls' to '%.*ls'.
5532	16	No	SQL Server cannot obtain the Kernel Transaction Manager's transaction context to perform file system operation.
5533	23	No	The FILESTREAM file system log record that has the LSN '%d:%d:%d' is missing. Log folder '%.*ls' is corrupted. Restore the database from a backup.
5534	23	No	SQL log record at LSN '%d:%d:%d' for database '%.*ls' is corrupted. Database cannot recover.
5535	23	No	FILESTREAM data container '%.*ls' is corrupted. Database cannot recover.
5536	23	No	FILESTREAM deleted folder '%.*ls' is corrupted. Database cannot recover.
5537	16	No	Function %ls is only valid on columns with the FILESTREAM attribute.
5538	16	No	Partial updates are not supported on columns that have a FILESTREAM as a source.
5539	16	No	The ROWGUIDCOL column associated with the FILESTREAM being used is not visible where method %ls is called.
5540	16	No	The FILESTREAM column cannot be used with method %ls because the associated ROWGUIDCOL of the base table is nullable or does not have a unique constraint.
5541	16	No	An open mode must be used when a FILESTREAM column is opened as a file.
5542	16	No	The FILESTREAM filegroup '%.*ls' has no files assigned to it. FILESTREAM data cannot be populated on this filegroup until a file is added.
5552	16	No	FILESTREAM file named with GUID '%.*ls' that belongs to FILESTREAM data file ID 0x%x does not exist or cannot be opened.
5553	16	No	SQL Server internal error. FILESTREAM manager cannot continue with current command.
5554	16	No	The total number of versions for a single file has reached the maximum limit set by the file system.
5555	16	No	The operation has failed because the FILESTREAM data cannot be renamed.
5570	16	No	FILESTREAM Failed to find the garbage collection table.
5571	23	No	Internal FILESTREAM error: failed to access the garbage collection table.
5572	23	No	Internal FILESTREAM error: failed to perform a filesystem operation because of a potential corruption.
5573	10	No	Internal FILESTREAM error: failed to access the tombstones table with HRESULT: 0x%x.
5574	16	No	A database cannot be enabled for both FILESTREAM storage and Database Mirroring.
5575	10	No	Operation '%ls' failed with HRESULT: %ls in file '%hs', line %d while executing sp_filestream_configure.
5578	16	No	A failure occurred while FILESTREAM configuration was being changed or applied. For more information, see the SQL Server error log.
5579	10	No	FILESTREAM: effective level = %d, configured level = %d, file system access share name = '%.*ls'.
5580	16	No	FILESTREAM InstanceGuid is null. Registry settings might be corrupted.
5581	10	No	FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have data in FILESTREAM columns, it will not be accessible after the SQL Server instance has been restarted.
5582	10	No	Machine reboot is required before the FILESTREAM feature settings can take effect.
5583	16	No	The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value must be 0, 1, 2, or 3.
5584	16	No	Another session is executing the sp_filestream_configure stored procedure. Check the updated configuration settings and retry the operation if necessary.
5586	10	No	The FILESTREAM feature is already configured to the specified level. No change has been made.
5588	16	No	Access to FILESTREAM data is not supported under snapshot isolation level.
5589	16	No	Access to FILESTREAM data is not supported under row versioning-based read committed snapshot isolation (RCSI).
5590	16	No	FILESTREAM operations are not supported on the platform.
5591	16	No	FILESTREAM feature is disabled.
5592	16	No	FILESTREAM feature doesn't have file system access enabled.
5593	16	No	FILESTREAM feature is not supported on WoW64. The feature is disabled.
5594	16	No	The value specified for the computer_name_format parameter to the .PathName() function is not valid.
5595	16	No	.PhysicalPathName is disabled.
5596	10	No	FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration.
5597	16	No	FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration Manager before enabling through sp_configure.
5598	16	No	FILESTREAM feature is not supported on user instances.
5600	16	No	The Cross Database Chaining option cannot be set to the specified value on the specified database.
5601	16	No	The service master key could not be force regenerated as requested by the -F startup option. The error number is %ld.
5602	16	No	The service master key regeneration was successful.
5603	16	No	The password for SA could not be force regenerated as requested by the -K startup option. The error number is %ld.
5604	16	No	The password regeneration attempt for SA was successful.
5701	10	No	Changed database context to '%.*ls'.
5702	10	No	SQL Server is terminating this process.
5703	10	No	Changed language setting to %.*ls.
5803	10	No	Unknown configuration (id = %d) encountered in sys.configurations.
5804	16	Yes	Character set, sort order, or collation cannot be changed at the server level because at least one database is not writable. Make the database writable, and retry the operation.
5805	16	No	Too few locks specified. Minimum %d.
5807	16	No	Recovery intervals above %d minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration.
5808	16	No	Ad hoc update to system catalogs is not supported.
5810	16	No	Valid values for the fill factor are 0 to 100.
5812	14	No	You do not have permission to run the RECONFIGURE statement.
5828	16	No	User connections are limited to %d.
5829	16	No	The specified user options value is invalid.
5831	16	No	Minimum server memory value (%d) must be less than or equal to the maximum value (%d).
5832	16	No	The affinity mask specified does not match the CPU mask on this system.
5833	16	No	The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
5834	16	No	The affinity mask specified conflicts with the IO affinity mask specified. Use the override option to force this configuration.
5835	16	No	Failed to start CPUs with the mask 0x%lx on the system.
5836	16	No	Lightweight pooling is not supported on this platform or in this edition of SQL Server.
5837	16	No	The service broker listen port cannot be dynamic. Valid port values are 1024-32767.
5838	16	No	The service broker connection authentication value is invalid.
5839	16	No	The service broker message forward store size cannot be set to 0.
5840	16	No	The service broker message forward mode is invalid.
5841	16	No	The default full-text language is not supported by the full-text search component.
5842	16	No	Too few worker threads are specified. The minimum is %d.
5843	16	No	Address Windowing Extensions (AWE) is not supported in this edition of SQL Server.
5844	16	No	User Instances are not supported in this edition of SQL Server.
5845	16	No	Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
5846	16	No	Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling".
5848	10	Yes	Physical CPU id %u has been hot added to node id %u as logical CPU id %u. This is an informational message only. No user action is required.
5849	10	Yes	Online CPU addition is not supported in the current edition of SQL Server.
5850	10	Yes	Online addition of CPU resources cannot be completed. A software non-uniform memory access (soft-NUMA) configuration was specified at SQL Server startup that does not allow online addition of CPU resources. To use the additional CPU resources, either add the new CPUs to the soft-NUMA configuration and restart SQL Server, or remove the soft-NUMA configuration and restart SQL Server.
5851	10	No	The AccessCheckResult quota must be greater than or equal to the bucket count
5852	10	No	The AccessCheckResult bucket count must be less than %d.
5854	10	No	The AccessCheckResult bucket count must be less than %d.
5904	17	Yes	Unable to issue checkpoint: there are not enough locks available. Background checkpoint process will remain suspended until locks are available. To free up locks, list transactions and their locks, and terminate transactions with the highest number of locks.

Errors 6,000 to 6,999

Error	Severity	Event Logged	Description
6001	10	No	SHUTDOWN is waiting for %d process(es) to complete.
6004	10	No	User does not have permission to perform this action.
6005	10	No	SHUTDOWN is in progress.
6006	10	Yes	Server shut down by %.ls from login %.ls.
6007	10	No	The SHUTDOWN statement cannot be executed within a transaction or by a stored procedure.
6101	16	No	Process ID %d is not a valid process ID. Choose a number between 1 and %d.
6102	14	No	User does not have permission to use the KILL statement.
6104	16	No	Cannot use KILL to kill your own process.
6106	16	No	Process ID %d is not an active process ID.
6107	14	No	Only user processes can be killed.
6108	16	No	KILL SPID WITH COMMIT/ABORT is not supported by Microsoft SQL Server. Use KILL UOW WITH COMMIT/ABORT to resolve in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC).
6109	10	No	SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%. Estimated time remaining: %d seconds.
6110	16	No	The distributed transaction with UOW %s does not exist.
6111	16	No	Another user has decided a different outcome for the distributed transaction associated with UOW %s.
6112	16	No	Distributed transaction with UOW %s is in prepared state. Only Microsoft Distributed Transaction Coordinator can resolve this transaction. KILL command failed.
6113	16	No	The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill the transaction instead.
6114	16	No	Distributed transaction with UOW %s is being used by another user. KILL command failed.
6115	16	No	KILL command cannot be used inside user transactions.
6117	16	No	There is a connection associated with the distributed transaction with UOW %s. First, kill the connection using KILL SPID syntax.
6118	16	No	The distributed transaction associated with UOW %s is not in PREPARED state. Use KILL UOW to kill the transaction instead.
6119	10	No	Distributed transaction with UOW %s is rolling back: estimated rollback completion: %d%%, estimated time left %d seconds.
6120	16	No	Status report cannot be obtained. Rollback operation for Process ID %d is not in progress.
6121	16	No	Status report cannot be obtained. Rollback operation for UOW %s is not in progress.
6200	16	No	Method "%ls" of type "%ls" in assembly "%.*ls" is marked as a mutator. Mutators cannot be used in the read-only portion of the query.
6201	16	No	Method "%ls" of type "%ls" in assembly "%.*ls" is not marked as a mutator. Only mutators can be used to update the value of a CLR type.
6202	16	No	Method "%ls" of type "%ls" in assembly "%.*ls" does not return a value.
6203	16	No	Method '%ls' of type '%ls' in assembly '%.*ls' cannot be marked as a mutator. A mutator method must be non-static, public, and returns void type.
6204	16	No	Trying to send a record with %d columns(s) in a result set with %d column(s).
6205	16	No	%s ASSEMBLY failed because assembly '%.*ls' was compiled with /UNSAFE option, but the assembly was not registered with the required PERMISSION_SET = UNSAFE option.
6206	16	No	Request submitted with too many parameters. The maximum number is %ld.
6207	16	No	Error converting %.*ls to fixed length binary type. The result would be padded and cannot be converted back.
6208	16	No	%s failed because the parameter count for the FillRow method should be one more than the SQL declaration for the table valued CLR function.
6209	16	No	Unsound ordering on CLR type "%.*ls": returning NULL on non-NULL inputs.
6210	16	No	CLR type '%.*ls' is not fully comparable.
6211	16	No	%s ASSEMBLY failed because type '%.ls' in %.ls assembly '%.ls' has a static field '%.ls'. Attributes of static fields in %.*ls assemblies must be marked readonly in Visual C#, ReadOnly in Visual Basic, or initonly in Visual C++ and intermediate language.
6212	16	No	%s ASSEMBLY failed because method '%.ls' on type '%.ls' in %.ls assembly '%.ls' is storing to a static field. Storing to a static field is not allowed in %.*ls assemblies.
6213	16	No	%s ASSEMBLY failed because method "%.ls" on type "%.ls" in %.ls assembly "%.ls" has a synchronized attribute. Explicit synchronization is not allowed in %.*ls assemblies.
6214	16	No	%s ASSEMBLY failed because assembly "%.*ls" has an unmanaged entry point.
6215	16	No	%s ASSEMBLY failed because method '%.ls' on type '%.ls' in %.ls assembly '%.ls' has invalid attribute 0x%x.
6216	16	No	%s ASSEMBLY failed because type "%.ls" in %.ls assembly "%.ls" has a finalizer. Finalizers are not allowed in %.ls assemblies.
6217	16	No	ALTER ASSEMBLY ADD FILE failed because the file, "%.*ls", being added is empty.
6218	16	No	%s ASSEMBLY for assembly '%.ls' failed because assembly '%.ls' failed verification. Check if the referenced assemblies are up-to-date and trusted (for external_access or unsafe) to execute in the database. CLR Verifier error messages if any will follow this message%.*ls
6219	16	No	%s ASSEMBLY failed because assembly source parameter %d has an unmanaged entry point.
6220	16	No	SELECT INTO failed because CLR type "%.*ls" does not exist in the target database.
6221	16	No	The cursor operation generated more than one row of different column metadata.
6222	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.*ls" is not valid for native serialization.
6223	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.ls" is of type "%.ls.%.*ls", which is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential".
6224	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.*ls" is marked with "System.NonSerializedAttribute". Native serialization types cannot have fields marked with "System.NonSerializedAttribute".
6225	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.ls" is of type "%.ls.%.*ls" which is a non-value type. Native serialization types can only have fields of blittable types. If you wish to have a field of any other type, consider using different kind of serialization format, such as User Defined Serialization.
6226	16	No	Type "%.ls.%.ls" is marked for user-defined serialization, but does not implement the "%.ls.%.ls" interface.
6227	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.ls" is of type "%.ls.%.ls", which is not blittable, or type "%.ls.%.*ls" has a recursive definition.
6228	16	No	Type "%.ls.%.ls" is marked for native serialization, but it contains non-blittable fields.
6229	16	No	Type "%.ls.%.ls" is marked for native serialization. It is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential".
6230	16	No	Type "%.ls.%.ls" is marked for native serialization, but field "%.ls" of type "%.ls.%.*ls" has field marshallers. Native serialization types cannot have field marshallers.
6231	16	No	Type "%.ls.%.ls" is marked for native serialization, but one of its base types "%.ls.%.ls" is not valid for native serialization.
6232	16	No	Type "%.ls.%.ls" is marked for native serialization, but base type "%.ls.%.ls" is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential".
6233	16	No	In proc data access is not allowed in an impersonated state.
6234	16	No	Data truncation error. Length (%d) exceeds maximum length (%d) for type '%.*ls'.
6235	16	No	Data serialization error. Length (%d) is less than fixed length (%d) for type '%.*ls'.
6236	16	No	%s ASSEMBLY failed because filename '%.*ls' is too long.
6237	16	No	%s ASSEMBLY failed because method "%.ls" on type "%.ls" in assembly "%.ls" has an invalid custom attribute "%.ls".
6238	16	No	%s ASSEMBLY failed because field "%.ls" in type "%.ls" in assembly "%.ls" has an invalid custom attribute "%.ls".
6239	16	No	%s ASSEMBLY failed because type "%.ls" in assembly "%.ls" has an invalid custom attribute "%.*ls".
6240	16	No	ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the indexed view '%s'.
6241	16	No	Trying to send a record with type or name of column %d differing from the type or name of the corresponding column of the result set.
6242	16	No	CREATE ASSEMBLY failed because the user "%.*ls" specified in the authorization clause does not exist.
6243	16	No	'%.ls.%.ls' is marked for native serialization, and has the MaxByteSize property specified in the '%.*ls' attribute. Native serialization objects can not specify MaxByteSize property, it is calculated by SQL Server.
6244	16	No	The size (%d) for "%.ls.%.ls" is not in the valid range. Size must be -1 or a number between 1 and 8000.
6245	16	No	Invalid serialization format (%d) for type "%.ls.%.ls".
6246	16	No	Assembly "%.ls" already exists in database "%.ls".
6247	16	No	Cannot create type because '%.ls.%.ls' cannot have fixed length if it has MaxByteSize set to -1.
6248	16	No	%s failed because the type '%s' contains a method '%s' specified by SqlUserDefinedType.ValidateMethodName that does not conform to the required specification because it has an invalid signature.
6249	16	No	The associated file "%.ls" already exists for assembly "%.ls".
6250	11	No	Assembly "%.ls" does not have an associated file "%.ls".
6251	16	No	ALTER ASSEMBLY failed because the assembly file parameter %d is not a valid expression.
6252	16	No	ALTER ASSEMBLY failed because a file name was not specified for the inline assembly file parameter %d.
6253	10	Yes	Common language runtime (CLR) functionality initialized using CLR version %ls from %ls.
6254	10	Yes	Common language runtime (CLR) functionality initialized.
6255	16	No	%s failed because type "%s" does not conform to the %s specification: missing custom attribute "%.*ls".
6258	16	No	Function signature of "FillRow" method (as designated by SqlFunctionAttribute.FillRowMethodName) does not match SQL declaration for table valued CLR function'%.*ls' due to column %d.
6260	16	No	An error occurred while getting new row from user defined Table Valued Function : %.*ls.
6261	16	No	The CLR type referenced by column "%.ls" of table variable "%.ls" has been dropped during the execution of the batch. Run the batch again.
6262	16	No	Assembly was not found in current database or version did not match.
6263	16	No	Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option.
6264	16	No	Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read".
6265	16	No	%s ASSEMBLY failed because type "%.ls" in %.ls assembly "%.ls" has a pinvokeimpl method. P/Invoke is not allowed in %.ls assemblies.
6266	10	No	Warning: Assembly "%.ls" was built using version %.ls of the .NET Framework. SQL Server currently uses version %s.
6267	16	No	Assembly "%.*ls" does not exist, or the user does not have permission to reference it.
6269	16	No	ALTER ASSEMBLY failed because the user-defined aggregate "%s" does not exist or is not correctly defined in the updated assembly.
6270	16	No	ALTER ASSEMBLY failed because the required method "%s" in type "%s" was not found with the same signature in the updated assembly.
6271	16	No	ALTER ASSEMBLY failed because the required field "%s" in type "%s" was not found with the same signature in the updated assembly.
6272	16	No	ALTER ASSEMBLY failed because required property '%s' in type '%s' was not found with the same signature in the updated assembly.
6273	16	No	ALTER ASSEMBLY failed because required type '%s' does not exist or is not correctly defined in the updated assembly.
6274	16	No	ALTER ASSEMBLY failed because the serialization format of type '%s' would change in the updated assembly. Persisted types are not allowed to change serialization formats.
6275	16	No	ALTER ASSEMBLY failed because the IsByteOrdered attribute of type '%s' would change in the updated assembly.
6276	16	No	ALTER ASSEMBLY failed because serialization data of type '%s' would change in the updated assembly. Persisted types are not allowed to change serialization data.
6277	16	No	ALTER ASSEMBLY failed because the MaxLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change MaxLen attribute.
6278	16	No	ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change IsFixedLen attribute.
6279	16	No	ALTER ASSEMBLY failed because the mutator attribute of method '%s' in type '%s' would change in the updated assembly, and the method is in use by the schema-bound function or view '%s'.
6280	16	No	ALTER ASSEMBLY failed because table, view or constraint '%s' depends on this assembly. Use WITH UNCHECKED DATA to skip checking for persisted data.
6281	16	No	ALTER ASSEMBLY failed because only members of the sysadmin role can use WITH UNCHECKED DATA.
6282	16	No	ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same.
6283	16	No	ALTER ASSEMBLY failed because only the assembly revision version number is allowed to change.
6284	16	No	ALTER ASSEMBLY failed because it is referenced by object '%.*ls'. Assemblies that are referenced by SQL objects cannot be made invisible.
6285	16	No	%s ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name "%.*ls".
6286	16	No	'%s' ASSEMBLY failed because a different version of assembly '%s', referenced by assembly '%s', is already in the database.
6287	16	No	ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the persisted computed column '%s' of table '%s'.
6288	16	No	ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%.*ls". Refer to column "has_unchecked_assembly_data" from system views "sys.tables" and "sys.views" to locate all such objects.
6289	16	Yes	Failed to allocate memory for common language runtime (CLR) functionality.
6290	10	Yes	AppDomain %i (%.*ls) unloaded.
6291	16	Yes	AppDomain %i (%.*ls) failed to unload with error code 0x%x.
6292	16	No	The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction.
6293	16	No	%.ls.%.ls.%.*ls: SqlFacetAttribute is invalid on a non-public member.
6294	16	No	%.ls.%.ls.%.ls: %.ls property of SqlFacetAttribute cannot be used in this context.
6295	16	No	%.ls.%.ls.%.ls: %.ls property of SqlFacetAttribute has an invalid value.
6296	16	No	%.ls.%.ls.%.*ls : SqlFacetAttribute cannot be applied to a property getter or a property setter. It should be applied to the property itself.
6297	16	No	%.ls.%.ls.%.*ls: The SqlFacetAttribute property IsFixedLength cannot be set to true when MaxSize is set to -1.
6298	16	No	%.ls.%.ls.%.*ls: The SqlFacetAttribute properties Precision and Scale have to be used together.
6299	10	No	AppDomain %i (%.*ls) created.
6302	16	No	The argument of CREATE or ALTER XML SCHEMA COLLECTION statement must be a string expression.
6303	16	No	XML parsing: Document parsing required too much memory
6304	16	No	XML parsing: An unexpected error has occurred in the XML parser.
6305	16	No	XQuery data manipulation expression required in XML data type method.
6306	16	No	Invalid XQuery expression passed to XML data type method.
6307	16	No	XML well-formedness check: Attribute cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
6308	16	No	XML well-formedness check: Duplicate attribute '%.*ls'. Rewrite your XQuery so it returns well-formed XML.
6309	16	No	XML well-formedness check: the data for node '%.*ls' contains a character (0x%04X) which is not allowed in XML.
6310	16	No	Altering existing schema components is not allowed. There was an attempt to modify an existing XML Schema component, component namespace: '%.ls' component name: '%.ls' component kind:%.*ls
6311	16	No	An internal XMLDB schema processor error occurred. Contact Technical Support for assistance.
6312	16	No	Could not find schema components with target namespace '%.ls' in collection '%.ls'.
6314	16	No	Collection specified does not exist in metadata : '%.*ls'
6315	16	No	XQuery: Cannot update with value '%.ls' as the canonical form of type '{%.ls}%.*ls' violates the required pattern. It is recommended that you not use pattern facets on non-string types.
6316	16	No	Specified component '%s' can not be dropped because it is used by component:'%s'
6317	16	No	XQuery: Cannot update with value '%.ls' because it failed validation against type '{%.ls}%.*ls'
6318	16	No	XQuery: String conversion failed during UPDATE validation
6320	16	No	XQuery: Only nillable elements or text nodes can be updated with empty sequence
6321	16	No	xml:space attribute must have a value of 'preserve' or 'default'. '%.*ls' is not valid.
6322	16	No	XML Parser ran out of memory. This could be caused by too many attributes or namespace declarations.
6323	16	No	The xml schema collection for variable '%.*ls' has been altered while the batch was being executed. Remove all XML schema collection DDL operations it is dependent on from the batch, and re-run the batch.
6324	16	No	DROP XML INDEX does not support any options.
6325	16	No	XQuery: Replacing the value of a node with an empty sequence is allowed only if '()' is used as the new value expression. The new value expression evaluated to an empty sequence but it is not '()'.
6326	16	No	XML well-formedness check: XML namespace declaration cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
6327	16	No	The specified xml schema collection ID is not valid: %d
6328	16	No	Specified collection '%.*ls' cannot be dropped because it is used by %S_MSG '%ls'.
6329	16	No	Unsupported usage of a QName typed value in node '%.*ls'
6330	16	No	Column '%.ls' on table '%.ls' is not of type XML, which is required to create an XML index on it.
6331	16	No	Primary XML Index '%.ls' already exists on column '%.ls' on table '%.*ls', and multiple Primary XML Indexes per column are not allowed.
6332	16	No	Table '%.*ls' needs to have a clustered primary key with less than %d columns in it in order to create a primary XML index on it.
6333	16	No	Could not find%ls XML index named '%.ls' on table '%.ls'
6334	16	No	Could not create the XML or spatial index on object '%.*ls' because that object is not a table. Create the index on the base table column.
6335	16	No	XML datatype instance has too many levels of nested nodes. Maximum allowed depth is %d levels.
6336	16	No	Maximum size of primary index of table '%.*ls' is %d bytes. CREATE XML INDEX requires that such size should be limited to %d bytes
6337	16	No	'%.*ls' is not a valid XML Index name because it starts with '%c' character. XML Index name should not start with '#' or '@'
6338	10	No	XML DTD has been stripped from one or more XML fragments. External subsets, if any, have been ignored.
6339	16	No	Specified collection '%.*ls' cannot be modified because it is SQL Server built-in XML Schema Collection.
6340	16	No	Xml schema collection '%.ls' referenced by table variable '%.ls' has been dropped or altered during the execution of the batch. Please re-run the batch.
6341	16	No	Xml schema collection referenced by column '%.ls' of table variable '%.ls' has been dropped or altered during the execution of the batch. Please re-run the batch.
6342	16	No	Cannot create primary xml or spatial index '%.ls' on table '%.ls', column '%.*ls', because the column is computed.
6343	16	No	Cannot create secondary xml index '%.*ls' without a USING XML INDEX clause.
6344	16	No	The primary xml index '%.ls' does not exist on table '%.ls' column '%.*ls'.
6345	16	No	The sparse column set '%.ls' in the table '%.ls' cannot be indexed by an XML index.
6346	16	No	Cannot convert a primary XML index to a secondary XML index using the DROP_EXISTING option. '%.*ls' is a primary XML index.
6347	16	No	Specified collection '%.*ls' cannot be altered because it does not exist or you do not have permission.
6348	16	No	Specified collection '%.*ls' cannot be created because it already exists or you do not have permission.
6350	16	No	The definition for xml schema collection '%.*ls' has changed.
6351	16	No	The xml schema collection for return parameter of module '%.*ls' has been altered while the batch was being executed. Please re-run the batch.
6352	16	No	Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as a string or untyped XML.
6353	16	No	Serialization of built-in schemata is not supported.
6354	16	No	Target string size is too small to represent the XML instance
6355	16	No	Conversion of one or more characters from XML to target collation impossible
6356	16	No	Failed to load DLL. Make sure xmlrw.dll exists in the SQL Server installation.
6357	16	No	Internal error: cannot locate CreateInfoSetReaderEx in xmlrw.dll. You may have an incorrect version of xmlrw.dll.
6358	16	No	%d is not a valid style number when converting to XML.
6359	16	No	Parsing XML with internal subset DTDs not allowed. Use CONVERT with style option 2 to enable limited internal subset DTD support.
6360	16	No	%d is not a valid style number when converting from XML.
6361	16	No	Invalid null parameter specified. XML Schema Collections can only be created from a non-null value.
6362	16	No	Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType.
6363	16	No	ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is schema bound. Remove the schema binding before trying to alter the collection.
6364	16	No	ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%.ls' did not succeed due to the following reason: '%.ls'. Either the schema or the specified data should be altered so that validation does not find any mismatches.
6365	16	No	An XML operation resulted an XML data type exceeding 2GB in size. Operation aborted.
6401	16	No	Cannot roll back %.*ls. No transaction or savepoint of that name was found.
6500	16	No	%ls failed because method '%ls' of class '%ls' in assembly '%ls' returns %ls, but CLR Triggers must return void.
6501	16	No	%s ASSEMBLY failed because it could not open the physical file "%.*ls": %ls.
6502	16	No	%s ASSEMBLY failed because it could not read from the physical file '%.*ls': %ls.
6503	16	No	Assembly '%.*ls' was not found in the SQL catalog.
6504	16	No	The value returned from %.ls.%.ls is not allowed to be NULL.
6505	16	No	Could not find Type '%s' in assembly '%s'.
6506	16	No	Could not find method '%s' for type '%s' in assembly '%s'
6507	16	No	Failed to open malformed assembly '%ls' with HRESULT 0x%x.
6508	16	No	Could not find field '%s' for type '%s' in assembly '%s'.
6509	16	No	An error occurred while gathering metadata from assembly '%ls' with HRESULT 0x%x.
6510	16	Yes	Common Language Runtime (CLR) %ls not installed properly. The CLR is required to use SQL/CLR features.
6511	16	Yes	Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You may fix the problem and try again later.
6512	16	Yes	Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You need to restart SQL Server to use CLR integration features.
6513	16	Yes	Failed to initialize the Common Language Runtime (CLR) %ls due to memory pressure. This is probably due to memory pressure in the MemToLeave region of memory. For more information, see the CLR integration documentation in SQL Server Books Online.
6514	16	No	Cannot use '%s' column in the result table of a streaming user-defined function (column '%.*ls').
6515	16	No	Schema collection database '%.*ls' does not exist or you do not have permission.
6516	16	No	There is no collection '%.ls' in metadata '%.ls'.
6517	16	Yes	Failed to create AppDomain "%.ls". %.ls
6518	16	No	Could not open system assembly ''%.*ls'': %ls.
6519	16	No	Type '%.*ls' is not yet supported for CLR operations.
6520	16	No	A .NET Framework error occurred during statement execution.
6521	16	No	A .NET Framework error occurred during statement execution: %.*ls.
6522	16	No	A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls.
6523	16	No	Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is static.
6524	16	No	Cannot use computed column in the result table of a streaming user-defined function (column '%.*ls').
6525	16	No	Cannot use '%s' constraint in the result table of a streaming user-defined function.
6526	16	No	Cannot use '%s' constraint in the result table of a streaming user-defined function (column '%.*ls').
6527	10	Yes	.NET Framework runtime has been stopped.
6528	16	No	Assembly '%.ls' was not found in the SQL catalog of database '%.ls'.
6529	16	No	ALTER ASSEMBLY failed because the identity of referenced assembly '%.*ls' has changed. Make sure the version, name, and public key have not changed.
6530	16	No	Cannot perform alter on '%.*ls' because it is an incompatible object type.
6531	16	No	%ls failed because the function '%ls' of class '%ls' of assembly '%.*ls' takes one or more parameters but CLR Triggers do not accept parameters.
6532	16	Yes	.NET Framework execution was aborted by escalation policy because of out of memory. %.*ls
6533	16	Yes	AppDomain %.ls was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource. %.ls
6534	16	Yes	AppDomain %.ls was unloaded by escalation policy to ensure the consistency of your application. Application failed to release a managed lock. %.ls
6535	16	No	.NET Framework execution was aborted. Another query caused the AppDomain %.ls to be unloaded. %.ls
6536	16	Yes	A fatal error occurred in the .NET Framework common language runtime. SQL Server is shutting down. If the error recurs after the server is restarted, contact Customer Support Services.
6537	16	Yes	The .NET Framework common language runtime was shut down by user code, such as in a user-defined function or CLR type. SQL Server is shutting down. Environment.Exit should not be used to exit the process. If the intent is to return an integer to indicate failure, use a scalar function or an output parameter instead.
6538	16	Yes	.NET Framework execution was aborted because of stack overflow. %.*ls
6539	16	No	Invalid serialization format (Format.Unknown) for type '%.ls.%.ls'.
6540	16	No	The assembly name '%.*ls' being registered has an illegal name that duplicates the name of a system assembly.
6541	16	No	ALTER ASSEMBLY failed because assembly '%.*ls' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files.
6542	16	No	Can not create object because %ls is a generic type.
6543	16	No	.NET Framework execution was aborted. The UDP/UDF/CLR type did not end thread affinity.
6544	16	No	%s ASSEMBLY for assembly '%.ls' failed because assembly '%.ls' is malformed or not a pure .NET assembly. %.*ls
6545	16	No	Enabling of execution statistics SET options is not allowed from within CLR procedure or function.
6546	16	No	Could not impersonate the execution context during the execution of '%.*ls'.
6547	16	No	An error occurred while getting method, property or field information for "%ls" of class "%ls" in assembly "%.*ls".
6548	16	No	CREATE ASSEMBLY failed because the assembly references assembly '%.*ls', which is owned by another user.
6549	16	No	A .NET Framework error occurred during execution of user defined routine or aggregate '%.*ls': %ls. User transaction, if any, will be rolled back.
6550	16	No	%s failed because parameter counts do not match.
6551	16	No	%s for "%.*ls" failed because T-SQL and CLR types for return value do not match.
6552	16	No	%s for "%.ls" failed because T-SQL and CLR types for parameter "%.ls" do not match.
6553	16	No	%s failed because of an invalid .NET Framework calling convention. Use the default .NET Framework calling convention.
6554	16	No	SQL assembly name '%.ls', and .NET Framework assembly name '%.ls' do not match. Assembly names must match.
6555	16	No	Assembly '%.ls' already exists for owner '%.ls' in database '%.*ls'.
6556	16	No	%s failed because it could not find type '%s' in assembly '%s'.
6557	16	No	%s failed because type '%s' does not conform to %s specification due to field '%s'.
6558	16	No	%s failed because type '%s' does not conform to %s specification due to method '%s'.
6559	20	Yes	Could not find type ID %d in database %.*ls. This is due to a schema inconsistency.
6560	16	No	Assembly "%.*ls" is a system assembly. This operation is permitted only with user assemblies.
6561	16	No	Could not find file '%s' in directory '%s%s'.
6562	16	No	Version mismatch between files '%s' (%d.%d.%d) and '%s' (%d.%d.%d).
6563	16	No	Method, property or field '%ls' in class '%ls' in assembly '%.*ls' has invalid return type.
6564	16	No	The method '%ls' in class '%ls' in assembly '%.*ls' has some invalid arguments. Value of type '%ls' is not valid for argument number %d.
6565	16	No	%s ASSEMBLY failed because the assembly source parameter %d is not a valid assembly.
6566	16	No	%s ASSEMBLY failed because the assembly source parameter %d is not a valid expression.
6567	16	No	%s failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, System.Nullable<System.Int32>, void.
6568	16	No	A .NET Framework error occurred while getting information from class "%.ls" in assembly "%.ls": %ls.
6569	16	No	'%.*ls' failed because parameter %d is not allowed to be null.
6570	16	No	Method '%ls' of class '%ls' in assembly '%.*ls' is generic. Generic methods are not supported.
6571	16	No	Class '%ls' in assembly '%.*ls' is generic. Generic types are not supported.
6572	16	No	More than one method, property or field was found with name '%ls' in class '%ls' in assembly '%.*ls'. Overloaded methods, properties or fields are not supported.
6573	16	No	Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not static.
6574	16	No	Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not public.
6575	16	No	Assembly names should be less than %d characters. Assembly name '%.*ls' is too long.
6576	16	No	Type '%ls' in assembly '%ls' is not public.
6577	16	No	CREATE TYPE failed because type '%s' does not conform to CLR type specification due to interface '%s'.
6578	16	No	Invalid attempt to continue operation after a severe error.
6579	16	No	Alter assembly from '%ls' to '%ls' is not a compatible upgrade.
6580	16	No	Declarations do not match for parameter %d. .NET Framework reference and T-SQL OUTPUT parameter declarations must match.
6581	16	No	Could not find assembly '%.ls' in directory '%.ls'.
6582	16	No	Assembly '%.*s' is not visible for creating SQL objects. Use ALTER ASSEMBLY to change the assembly visibility.
6583	16	No	Assembly '%.*s' cannot be used for creating SQL objects because it is a system assembly.
6584	16	No	Property or field '%ls' for type '%ls' in assembly '%ls' is not static
6585	16	No	Could not impersonate the client during assembly file operation.
6586	16	No	Assembly '%.*ls' could not be installed because existing policy would keep it from being used.
6587	16	No	Assembly reference '%ls' was redirected by external policy to '%ls'
6588	16	No	Assembly file operations are not allowed for Windows NT users activated by SETUSER.
6589	16	No	DROP ASSEMBLY failed because the specified assemblies are referenced by assembly '%ls'.
6590	16	No	DROP ASSEMBLY failed because '%ls' is referenced by object '%ls'.
6591	16	No	%s for "%.ls" failed because first parameter of "%.ls" method must be of type System.Object.
6592	16	No	Could not find property or field '%ls' for type '%ls' in assembly '%ls'.
6593	16	No	Property or field '%ls' for type '%ls' in assembly '%ls' is static.
6594	16	No	Could not read from property '%ls' for type '%ls' in assembly '%ls' because it does not have a get accessor.
6595	16	No	Could not assign to property '%ls' for type '%ls' in assembly '%ls' because it is read only.
6596	16	No	%s ASSEMBLY failed because assembly '%ls' is a system assembly. Consider creating a user assembly to wrap desired functionality.
6597	16	No	CREATE %s failed.
6598	16	No	DROP ASSEMBLY failed because '%ls' is referenced by CLR type '%ls'.
6599	16	No	Found an empty native serialization class '%.*ls'. Empty native serialization classes are not allowed.
6600	16	No	XML error: %.*ls
6601	10	No	The XML parse error 0x%x occurred on line number %d, near the XML text "%.*ls".
6602	16	No	The error description is '%.*ls'.
6603	16	No	XML parsing error: %.*ls
6605	16	No	%.*ls: Failed to obtain an IPersistStream interface on the XML text.
6607	16	No	%.*ls: The value supplied for parameter number %d is invalid.
6608	16	No	Failed to instantiate class "%ls". Verify that Msxmlsql.dll exists in the SQL Server installation.
6609	16	No	Invalid data type for the column "%ls". Allowed data types are CHAR/VARCHAR, NCHAR/NVARCHAR, TEXT/NTEXT, and XML.
6610	17	No	Failed to load Msxmlsql.dll.
6611	16	No	The XML data type is damaged.
6613	16	No	Specified value '%ls' already exists.
6621	16	No	XML encoding or decoding error occurred with object name '%.*ls'.
6622	16	No	Invalid data type for column "%ls". The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml.
6623	16	No	Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar.
6624	16	No	XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
6625	16	No	Could not convert the value for OPENXML column '%ls' to sql_variant data type. The value is too long. Change the data type of this column to text, ntext or image.
6626	16	No	Unexpected end of data stream.
6627	16	No	The size of the data chunk that was requested from the stream exceeds the allowed limit.
6628	16	No	%.*ls can only process untyped XML. Cast the input value to XML or to a string type.
6629	16	No	The result of the column expression for column "%ls" is not compatible with the requested type "XML". The result must be an element, text node, comment node, processing instruction, or document node.
6630	16	No	Element-centric mapping must be used with OPENXML when one of the columns is of type XML.
6631	16	No	The requested OpenXML document is currently in use by another thread, and cannot be used.
6632	16	No	Invalid data type for the column "%ls". CLR types cannot be used in an OpenXML WITH clause.
6633	16	No	The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version "%d.%d.%d". Require version "%d.%d.%d".
6634	16	No	OpenXML cannot be used as the target of a DML or OUTPUT INTO operation.
6700	16	No	XQuery: The ' %ls' operation is not supported.
6701	16	No	The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index.
6716	16	No	XML Node ID is invalid. Re-build the database if the problem persists.
6717	16	No	XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy.
6718	16	No	XQuery: Invalid ordpath string: "%s"
6739	16	No	XQuery: SQL type '%s' is not supported in XQuery.
6743	16	No	XQuery: The maximum allowed depth in XML instances is %d levels. One of the paths in the query tries to access nodes at a lower level.
6744	16	No	XQuery: One of the paths specified in the query is too deep. The maximum allowed depth is %d levels.
6745	16	No	XQuery: Internal compiler error.
6800	16	No	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	16	No	FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column.
6802	16	No	FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integer.
6803	16	No	FOR XML EXPLICIT requires the first column to hold positive integers that represent XML tag IDs.
6804	16	No	FOR XML EXPLICIT requires the second column to hold NULL or nonnegative integers that represent XML parent tag IDs.
6805	16	No	FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed.
6806	16	No	Undeclared tag ID %d is used in a FOR XML EXPLICIT query.
6807	16	No	Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query.
6808	16	No	XML tag ID %d could not be added. The server memory resources may be low.
6809	16	No	Unnamed tables cannot be used as XML identifiers as well as unnamed columns cannot be used for attribute names. Name unnamed columns/tables using AS in the SELECT statement.
6810	16	No	Column name '%.*ls' is repeated. The same attribute cannot be generated more than once on the same XML tag.
6811	16	No	FOR XML is incompatible with COMPUTE expressions. Remove the COMPUTE expression.
6812	16	No	XML tag ID %d that was originally declared as '%.ls' is being redeclared as '%.ls'.
6813	16	No	FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'.
6814	16	No	In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'.
6815	16	No	In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'.
6816	16	No	In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'.
6817	16	No	FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'.
6819	16	No	The FOR XML clause is not allowed in a %ls statement.
6820	16	No	FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'.
6821	16	No	GROUP BY and aggregate functions are currently not supported with FOR XML AUTO.
6824	16	No	In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid.
6825	16	No	ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML.
6826	16	No	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	16	No	FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted.
6828	16	No	XMLTEXT column '%.*ls' must be of a string data type or of type XML.
6829	16	No	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	16	No	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	16	No	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	16	No	FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary.
6833	16	No	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	16	No	XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag and its attributes.
6835	16	No	FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once.
6836	16	No	FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls' to precede element-centric IDREFS/NMTOKEN fields.
6838	16	No	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	16	No	FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that has IDREFS or NMTOKENS fields.
6840	16	No	Neither XMLDATA nor XMLSCHEMA supports namespace elements or attributes such as '%.*ls'. Run the SELECT FOR XML statement without it or remove the namespace prefix declaration.
6841	16	No	FOR XML could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data using FOR XML, convert it to binary, varbinary or image data type and use the BINARY BASE64 directive.
6842	16	No	Could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data convert it to binary, varbinary or image data type
6843	16	No	FOR XML EXPLICIT: XML data types and CLR types cannot be processed as CDATA in column name '%.*ls'. Consider converting XML to a string type. Consider converting CLR types to XML and then to a string type.
6844	16	No	Two (or more) elements named '%.*ls' are of different types and not direct siblings in the same level.
6845	16	No	Two (or more) elements named '%.*ls' are optional in the same level. Consider making them direct siblings or map NULL to xsi:nil
6846	16	No	XML name space prefix '%.ls' declaration is missing for FOR XML %.ls name '%.*ls'.
6847	16	No	The column '%.*ls' is of type sql_variant, which is not supported in attribute-centric FOR XML, with XML Schema.
6848	16	No	XMLDATA does not support the mapping of the type of column '%.*ls' to an XDR type. Please use XMLSCHEMA instead for AUTO and RAW mode.
6849	16	No	FOR XML PATH error in column '%.*ls' - '//' and leading and trailing '/' are not allowed in simple path expressions.
6850	16	No	%.ls name '%.ls' contains an invalid XML identifier as required by FOR XML; '%c'(0x%04X) is the first character at fault.
6851	16	No	Column '%.*ls' has invalid data type for attribute-centric XML serialization in FOR XML PATH.
6852	16	No	Attribute-centric column '%.*ls' must not come after a non-attribute-centric sibling in XML hierarchy in FOR XML PATH.
6853	16	No	Column '%.*ls': the last step in the path can't be applied to XML data type or CLR type in FOR XML PATH.
6854	16	No	Invalid column alias '%.*ls' for formatting column as XML processing instruction in FOR XML PATH - it must be in 'processing-instruction(target)' format.
6855	16	No	Inline schema is not supported with FOR XML PATH.
6856	16	No	FOR XML row XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
6857	16	No	FOR XML root XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
6858	16	No	XML schema URI contains character '%c'(0x%04X) which is not allowed in XML.
6859	16	No	Row tag name is only allowed with RAW or PATH mode of FOR XML.
6860	16	No	FOR XML directive XMLDATA is not allowed with ROOT directive or row tag name specified.
6861	16	No	Empty root tag name can't be specified with FOR XML.
6862	16	No	Empty FOR XML target inline schema URI is not allowed.
6863	16	No	Row tag omission (empty row tag name) is not compatible with XMLSCHEMA FOR XML directive.
6864	16	No	Row tag omission (empty row tag name) cannot be used with attribute-centric FOR XML serialization.
6865	16	No	FOR XML does not support CLR types - cast CLR types explicitly into one of the supported types in FOR XML queries.
6866	16	No	Use of a system reserved XML schema URI is not allowed.
6867	16	No	'xmlns' is invalid in XML tag name in FOR XML PATH, or when WITH XMLNAMESPACES is used with FOR XML.
6868	16	No	The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives.
6869	16	No	Attempt to redefine namespace prefix '%.*ls'
6870	16	No	Prefix '%.*ls' used in WITH XMLNAMESPACES clause contains an invalid XML identifier. '%c'(0x%04X) is the first character at fault.
6871	16	No	Prefix '%.*ls' used in WITH XMLNAMESPACES is reserved and cannot be used as a user-defined prefix.
6872	16	No	XML namespace prefix 'xml' can only be associated with the URI http://www.w3.org/XML/1998/namespace. This URI cannot be used with other prefixes.
6873	16	No	Redefinition of 'xsi' XML namespace prefix is not supported with ELEMENTS XSINIL option of FOR XML.
6874	16	No	Empty URI is not allowed in WITH XMLNAMESPACES clause.
6875	16	No	URI '%.*ls' used in WITH XMLNAMESPACES is invalid. '%c'(0x%04X) is the first character at fault.
6876	16	No	URI used in WITH XMLNAMESPACES is too long. The maximum length is %d characters.
6877	16	No	Empty namespace prefix is not allowed in WITH XMLNAMESPACES clause.
6878	16	No	FORXML XMLSCHEMA cannot be used with a typed XML column whose schema collection is empty.
6879	16	No	'xml' is an invalid XML processing instruction target. Possible attempt to construct XML declaration using XML processing instruction constructor. XML declaration construction with FOR XML is not supported.
6901	16	No	XML Validation: XML instance must be a document.
6902	16	No	XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support the use of the pattern or enumeration facet on lists of type QName.
6903	16	No	XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support inclusion of ID, QName, or list of QName among the member types of a union type.
6904	16	No	XML Validation: Found duplicate attribute '%s'. Location: %s
6905	16	No	XML Validation: Attribute '%s' is not permitted in this context. Location: %s
6906	16	No	XML Validation: Required attribute '%s' is missing. Location: %s
6907	16	No	Namespace URI too long: '%.*ls'.
6908	10	No	XML Validation: Invalid content. Expected element(s): %s. Location: %s
6909	16	No	XML Validation: Text node is not allowed at this location, the type was defined with element only content or with simple content. Location: %s
6910	16	No	XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support restriction of union types.
6911	16	No	XML Validation: Found duplicate element '%s' in all content model. Location: %s
6912	16	No	XML Validation: Element '%s' found in text only content model. Location: %s
6913	16	No	XML Validation: Declaration not found for element '%s'. Location: %s
6914	16	No	XML Validation: Type definition for type '%s' was not found, type definition is required before use in a type cast. Location: %s
6915	16	No	Element or attribute name too long: '%.*ls'.
6916	16	No	XML Validation: The content model of type or model group '%s' is ambiguous and thus violates the unique particle attribution constraint. Consult SQL Server Books Online for more information.
6917	16	No	XML Validation: Element '%ls' may not have xsi:nil="true" because it was not defined as nillable or because it has a fixed value constraint. Location: %ls
6918	16	No	XML Validation: Element '%s' must not have character or element children, because xsi:nil was set to true. Location: %s
6919	16	No	XML Validation: The type of element '%s' is abstract. Instantiation requires the use of xsi:type to specify a non-abstract type. Location: %s
6920	16	No	Invalid definition for type '%ls'. Cannot specify use="prohibited" for attribute '%ls' because there is no corresponding attribute in the base type.
6921	16	No	XML Validation: Element or attribute '%s' was defined as fixed, the element value has to be equal to value of 'fixed' attribute specified in definition. Location: %s
6922	16	No	XML Validation: Not able to resolve namespace for prefix:'%.*ls'
6923	16	No	XML Validation: Unexpected element(s): %s. Location: %s
6924	16	No	XML Validation: Text '%.*ls' found in attribute-only content model. Location: %s
6925	16	No	Invalid definition for element '%ls'. SQL Server does not currently permit additions to existing substitution groups via ALTER XML SCHEMA COLLECTION.
6926	16	No	XML Validation: Invalid simple type value: '%s'. Location: %s
6927	16	No	XML Validation: Invalid simple type value: '%ls'.
6928	16	No	XML Validation: XML instances of the content model of type or model group '%ls' can be validated in multiple ways and are not supported.
6929	16	No	XML Validation: Invalid QName for xsi:type attribute '%.*ls'.
6930	16	No	XML Validation: ID constraint check failed. Found attribute named '%.ls' with duplicate ID value '%.ls'. Location: %s
6931	16	No	XML Validation: IDREF constraint check failed. Found attribute named '%.ls' with reference to ID value '%.ls', which does not exist
6932	16	No	Invalid definition for element or attribute '%s'. Value constraints on components of type ID are not allowed.
6933	16	No	XML Validation: Invalid simple type operation, inserting into simple type is not permitted. Location: %s
6934	16	No	XML Validation: Element '%s' requires substitution, because it was defined as abstract. Location: %s
6935	16	No	XML Validation: ID or IDREF attribute exceeded the allowed maximum length. Location: %s
6936	16	No	XML Validation: Invalid cast for element '%s' from type '%s' to type '%s'. Location: %s
6937	16	No	XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on non-string types or range restrictions or enumerations on floating-point types. Location: %ls
6938	16	No	XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on non-string types or range restrictions or enumerations on floating-point types.
6939	16	No	XML Validation: The element '%ls' is mixed content with a fixed value and therefore not allowed to have element content. Location: %ls
6940	16	No	Invalid component named '%s' found in global scope. Only elements, attributes, types and groups can be defined in global context
6941	16	No	Invalid type definition for type '%s', types with complex content can only be derived from base types which have complex content
6942	16	No	Invalid type definition for type '%s', types with simple content can only be derived from base types which have simple content
6943	16	No	Invalid type definition for type '%s', the derivation was illegal because 'final' attribute was specified on the base type
6944	16	No	Invalid type definition for type '%s', '%s' facet is not restricting the value space
6945	16	No	Invalid facet value for facet '%s' in type definition '%s'
6946	16	No	Invalid type definition for type '%s', 'minLength' can not be greater than 'maxLength'
6947	16	No	XML Validation: Multiple ID attributes found on a single element. Location: %s
6948	16	No	Invalid type definition for type '%s', 'minLength' can not be greater than 'Length'
6949	16	No	Invalid type definition for type '%s', 'Length' can not be greater than 'maxLength'
6950	16	No	Invalid type definition for type '%s', 'fractionDigits' can not be greater than 'totalDigits'
6951	16	No	Invalid type definition for type '%s', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive'
6952	16	No	Invalid type definition for type '%s', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive'
6953	16	No	Invalid type definition for type '%s', recursive type definitions are not allowed
6954	16	No	Invalid group definition for group '%s', recursive group definitions are not allowed
6955	16	No	Invalid attribute definition for attribute '%s', attributes type has to be simple type
6956	16	No	Invalid type definition for type '%s', fixed facet '%s' can not be redefined to a different value.
6957	16	No	Invalid element definition, element '%s' is not valid derivation of element '%s'
6958	16	No	Invalid definition for type '%s'. An 'all' group may not appear as the child or parent of any other model group, it must have minOccurs = maxOccurs = 1, its child elements must have maxOccurs = 1
6959	16	No	Invalid definition, top level group definitions can not have model groups as siblings
6960	16	No	Component '%s' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional part is 28
6961	16	No	The system limit on the number of XML types has been reached. Redesign your database to use fewer XML types.
6962	16	No	'default' and 'fixed' values are not allowed on element of this type: '%s'
6963	16	No	'Default' or 'Fixed' value is longer than allowed, maximum length allowed is 4000 characters : '%s'
6964	16	No	Facet value is longer than allowed, maximum length allowed is 4000 characters : '%s'
6965	10	No	XML Validation: Invalid content. Expected element(s): %s. Found: element '%s' instead. Location: %s.
6966	10	No	Warning: Type '%s' is restricted by a facet '%s' that may impede full round-tripping of instances of this type
6967	16	No	Invalid type definition for type '%s'. The base and derived types must have the same value for 'mixed' unless deriving by restriction, in which case 'false' is always permitted for the derived type.
6968	16	No	Invalid type definition for type '%s'. Complex types cannot restrict simple types
6969	16	No	ID/IDREF validation consumed too much memory. Try reducing the number of ID and IDREF attributes. Rearranging the file so that elements with IDREF attributes appear after the elements which they reference may also be helpful.
6970	16	No	Invalid type definition for type '%s'. No type may have more than one attribute of any type derived from ID.
6971	16	No	Invalid type definition for type '%s'. Type contains attribute '%s' which is not allowed in base type.
6972	16	No	Invalid redefinition of attribute '%s' in type '%s'. Must be of a type which is a valid restriction of the corresponding attribute in the base type.
6973	16	No	Invalid redefinition of attribute '%s' in type '%s'. Must be required in the derived type if it is required in the base type.
6974	16	No	Invalid redefinition of attribute '%s' in type '%s'. Must be prohibited in the derived type if it is prohibited in the base type.
6975	16	No	Invalid redefinition of attribute '%s' in type '%s'. Must be fixed to the same value as in the derived type.
6976	16	No	Invalid redefinition of attribute '%s' in type '%s'. Derivation by extension may not redefine attributes.
6977	16	No	Invalid member type '%s' in union type '%s'. Unions may not have complex member types.
6978	16	No	Invalid item type for list type '%s'. The item type of a list may not itself be a list, and types derived from ID may not be used as item types in this release.
6979	16	No	Invalid restriction for type '%s'. The element in the restricted type must have the same name as and a more restrictive type than the corresponding element in the base type.
6980	16	No	Invalid restriction for type '%s'. The particle in the restricted type may not have an occurrence range more permissive than that of the corresponding particle in the base type.
6981	16	No	Invalid restriction for type '%s'. The element in the restricted type may not be nillable if the corresponding element in the base type is not.
6982	16	No	Invalid restriction for type '%s'. The element in the restricted type must be fixed to the same value as the corresponding element in the derived type.
6983	16	No	Invalid restriction for type '%s'. The element in the restricted type may not have a 'block' value more permissive than the corresponding element in the base type.
6984	16	No	Invalid restriction for type '%s'. The element in the restricted type must be in one of the namespaces allowed by the base type's wildcard.
6985	16	No	Invalid restriction for type '%s'. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard in the base type, and the processContents may not be more permissive.
6986	16	No	Invalid restriction for type '%s'. The effective total range of the model group in the restricted type must be a valid restriction of the occurrence range of the wildcard in the base type.
6987	16	No	Invalid restriction for type '%s'. An 'all' particle may be restricted only by 'all', 'element', or 'sequence'.
6988	16	No	Invalid restriction for type '%s'. A 'choice' particle may be restricted only by 'element', 'choice', or 'sequence'.
6989	16	No	Invalid restriction for type '%s'. A 'sequence' particle may be restricted only by 'element' or 'sequence'.
6990	16	No	Invalid restriction for type '%s'. Invalid model group restriction.
6991	16	No	Invalid restriction for type '%s'. If the base type has empty content, then the derived type must as well, and if the derived type has empty content, then the base type must be emptiable.
6992	16	No	The content model of type '%s' contains two elements with the same name '%s' and different types, nullability, or value constraints.
6993	16	No	Value constraint on use of attribute '%s' must be consistent with value constraint on its declaration.
6994	16	No	Invalid restriction for type '%s'. The attribute wildcard in the restricted type must be a valid subset of the corresponding attribute wildcard in the base type, and the processContents may not be more permissive.
6995	16	No	Invalid definition for type or element '%s'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived from them to be used as the type of an element or as the basis for derivation by extension.
6996	16	No	Invalid type definition for type '%s'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and 'maxExclusive' facets.
6997	16	No	Invalid definition for element '%s'. An element which has a fixed value may not also be nillable.
6998	16	No	Invalid type definition: Type or content model '%s' is too complicated. It may be necessary to reduce the number of enumerations or the size of the content model.
6999	16	No	Invalid definition for element or attribute '%s'. Value constraints on components of type QName are not supported in this release.

Errors 7,000 to 7,999

Error	Severity	Event Logged	Description
7000	16	No	OPENXML document handle parameter must be of data type int.
7001	16	No	OPENXML flags parameter must be of data type int.
7002	16	No	OPENXML XPath must be of a string data type, such as nvarchar.
7003	16	No	Only one OPENXML column can be of type %ls.
7004	16	No	OPENXML does not support retrieving schema from remote tables, as in '%.*ls'.
7005	16	No	OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument.
7006	16	No	OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement.
7007	16	No	OPENXML encountered unknown metaproperty '%.*ls'.
7008	16	No	The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag.
7009	16	No	OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument.
7101	16	No	You need an active user transaction in order to use text pointers for a table with the option "text in row" set to ON.
7102	20	Yes	Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
7104	16	No	Offset or size of data type is not valid. Data type must be of type int or smallint.
7105	22	Yes	The Database ID %d, Page %S_PGID, slot %d for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE.
7106	16	Yes	Internal error: An attempt was made to update a LOB data type using a read-only text pointer.
7107	16	No	You can have only 1,024 in-row text pointers in one transaction
7108	22	Yes	Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
7116	16	No	Offset %d is not in the range of available LOB data.
7117	16	No	Error reading large object (LOB) data from the tabular data stream (TDS).
7118	16	No	Only complete replacement is supported when assigning a large object (LOB) to itself.
7119	16	No	Attempting to grow LOB beyond maximum allowed size of %I64d bytes.
7122	16	No	Invalid text, ntext, or image pointer type. Must be binary(16).
7123	16	No	Invalid text, ntext, or image pointer value %hs.
7124	16	No	The offset and length specified in the READTEXT statement is greater than the actual data length of %ld.
7125	16	No	The text, ntext, or image pointer value conflicts with the column name specified.
7133	16	No	NULL textptr (text, ntext, or image pointer) passed to %ls function.
7134	16	No	LOB Locator is not supported as text pointer when using UPDATETEXT/WRITETEXT to update/write a text column.
7135	16	No	Deletion length %ld is not in the range of available text, ntext, or image data.
7137	16	No	%s is not allowed because the column is being processed by a concurrent snapshot or is being replicated to a non-SQL Server Subscriber or Published in a publication allowing Data Transformation Services (DTS) or tracked by Change Data Capture.
7138	16	No	The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or tracked by Change Data Capture.
7139	16	No	Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld.
7140	16	No	Cannot create additional orphans with the stored procedure sp_createorphan. Free up some of the orphan handles that you have created by inserting or deleting them.
7141	16	No	Must create orphaned text inside a user transaction.
7143	16	No	Invalid locator de-referenced.
7144	16	No	A text/ntext/image column referenced by a persisted or indexed computed column cannot be updated
7151	16	No	Insufficient buffer space to perform write operation.
7201	17	No	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	11	No	Could not find server '%.*ls' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
7212	16	No	Could not execute procedure '%.ls' on remote server '%.ls'.
7213	20	Yes	The attempt by the provider to pass remote stored procedure parameters to remote server '%.*ls' failed. Verify that the number of parameters, the order, and the values passed are correct.
7214	16	Yes	Remote procedure time out of %d seconds exceeded. Remote procedure '%.*ls' is canceled.
7215	16	No	Could not execute statement on remote server '%.*ls'.
7221	16	No	Could not relay results of procedure '%.ls' from remote server '%.ls'.
7301	16	No	Cannot obtain the required interface ("%ls") from OLE DB provider "%ls" for linked server "%ls".
7302	16	No	Cannot create an instance of OLE DB provider "%ls" for linked server "%ls".
7303	16	No	Cannot initialize the data source object of OLE DB provider "%ls" for linked server "%ls".
7304	16	No	Cannot connect using OLE DB provider "%ls" to linked server "%ls". Verify the connection parameters or login credentials associated with this linked server.
7305	16	No	Cannot create a statement object using OLE DB provider "%ls" for linked server "%ls".
7306	16	No	Cannot open the table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
7307	16	No	Cannot obtain the data source of a session from OLE DB provider "%ls" for linked server "%ls". This action must be supported by the provider.
7308	16	No	OLE DB provider '%ls' cannot be used for distributed queries because the provider is configured to run in single-threaded apartment mode.
7310	16	No	Cannot obtain the set of schema rowsets supported by OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a failure code when it is used.
7311	16	No	Cannot obtain the schema rowset "%ls" for OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a failure code when it is used.
7312	16	No	Invalid use of schema or catalog for OLE DB provider "%ls" for linked server "%ls". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.
7313	16	No	An invalid schema or catalog was specified for the provider "%ls" for linked server "%ls".
7314	16	No	The OLE DB provider "%ls" for linked server "%ls" does not contain the table "%ls". The table either does not exist or the current user does not have permissions on that table.
7315	16	No	The OLE DB provider "%ls" for linked server "%ls" contains multiple tables that match the name "%ls".
7316	16	No	Cannot use qualified table names (schema or catalog) with the OLE DB provider "%ls" for linked server "%ls" because it does not implement required functionality.
7317	16	No	The OLE DB provider "%ls" for linked server "%ls" returned an invalid schema definition.
7318	16	No	The OLE DB provider "%ls" for linked server "%ls" returned an invalid column definition for table "%ls".
7319	16	No	The OLE DB provider "%ls" for linked server "%ls" returned a "%ls" index "%ls" with the incorrect bookmark ordinal %d.
7320	16	No	Cannot execute the query "%ls" against OLE DB provider "%ls" for linked server "%ls". %ls
7321	16	No	An error occurred while preparing the query "%ls" for execution against OLE DB provider "%ls" for linked server "%ls". %ls
7322	16	No	A failure occurred while giving parameter information to OLE DB provider "%ls" for linked server "%ls".
7323	16	No	An error occurred while submitting the query text to OLE DB provider "%ls" for linked server "%ls".
7324	16	No	A failure occurred while setting parameter properties with OLE DB provider "%ls" for linked server "%ls".
7325	16	No	Objects exposing columns with CLR types are not allowed in distributed queries. Please use a pass-through query to access remote object '%ls'.
7330	16	No	Cannot fetch a row from OLE DB provider "%ls" for linked server "%ls".
7331	16	No	Rows from OLE DB provider "%ls" for linked server "%ls" cannot be released.
7332	16	No	Cannot rescan the result set from OLE DB provider "%ls" for linked server "%ls". %ls
7333	16	No	Cannot fetch a row using a bookmark from OLE DB provider "%ls" for linked server "%ls".
7339	16	No	OLE DB provider '%ls' for linked server '%ls' returned invalid data for column '%ls.%ls'.
7340	16	No	Cannot create a column accessor for OLE DB provider "%ls" for linked server "%ls".
7341	16	No	Cannot get the current row value of column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
7342	16	No	An unexpected NULL value was returned for column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". This column cannot be NULL.
7343	16	No	The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls". %ls
7344	16	No	The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls" because of column "%ls". %ls
7345	16	No	The OLE DB provider "%ls" for linked server "%ls" could not delete from table "%ls". %ls
7346	16	No	Cannot get the data of the row from the OLE DB provider "%ls" for linked server "%ls". %ls
7347	16	No	OLE DB provider '%ls' for linked server '%ls' returned data that does not match expected data length for column '%ls.%ls'. The (maximum) expected data length is %ls, while the returned data length is %ls.
7348	16	No	The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls". %ls. For possible cause of this issue, see the extended error message.
7349	16	No	The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls" because of column "%ls". %ls
7350	16	No	Cannot get the column information from OLE DB provider "%ls" for linked server "%ls".
7351	16	No	The OLE DB provider "%ls" for linked server "%ls" could not map ordinals for one or more columns of object "%ls".
7352	16	No	The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. The object "%ls" was missing the expected column "%ls".
7353	16	No	The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time.
7354	16	No	The OLE DB provider "%ls" for linked server "%ls" supplied invalid metadata for column "%ls". %ls
7355	16	No	The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The name was changed at execution time.
7356	16	No	The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The column "%ls" (compile-time ordinal %ld) of object "%ls" was reported to have a "%ls" of %ld at compile time and %ld at run time.
7357	16	No	Cannot process the object "%ls". The OLE DB provider "%ls" for linked server "%ls" indicates that either the object has no columns or the current user does not have permissions on that object.
7358	16	No	Cannot execute the query. The OLE DB provider "%ls" for linked server "%ls" did not provide an appropriate interface to access the text, ntext, or image column "%ls.%ls".
7359	16	No	The OLE DB provider "%ls" for linked server "%ls" reported a change in schema version between compile time ("%ls") and run time ("%ls") for table "%ls".
7360	16	No	Cannot get the length of a storage object from OLE DB provider "%ls" for linked server "%ls" for table "%ls", column "%ls".
7361	16	No	Cannot read a storage object from OLE DB provider "%ls" for linked server "%ls", for table "%ls", column "%ls".
7362	16	No	The OLE DB provider "%ls" for linked server "%ls" reported different metadata at run time for table "%ls", column "%ls".
7365	16	No	Cannot obtain optional metadata columns of columns rowset from OLE DB provider "%ls" for linked server "%ls".
7366	16	No	Cannot obtain columns rowset from OLE DB provider "%ls" for linked server "%ls".
7367	16	No	The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide the metadata column "%ls" at run time.
7368	16	No	The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide collation data for column "%ls".
7369	16	No	The OLE DB provider '%ls' for linked server '%ls' provided invalid collation. LCID = %08x, Compflags = %08x, SortOrder = '%.*ls'.
7370	16	No	One or more properties could not be set on the query for OLE DB provider "%ls" for linked server "%ls". %ls
7371	16	No	The server option 'collation name' in linked server '%ls' for OLE DB provider '%ls' has collation id %08x which is not supported by SQL Server.
7372	16	No	Cannot get properties from OLE DB provider "%ls" for linked server "%ls".
7373	16	No	Cannot set the initialization properties for OLE DB provider "%ls" for linked server "%ls".
7374	16	No	Cannot set the session properties for OLE DB provider "%ls" for linked server "%ls".
7375	16	No	Cannot open index "%ls" on table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
7376	16	No	Could not enforce the remote join hint for this query.
7377	16	No	Cannot specify an index hint for a remote data source.
7380	16	No	Table-valued parameters are not allowed in remote calls between servers.
7390	16	No	The requested operation could not be performed because OLE DB provider "%ls" for linked server "%ls" does not support the required transaction interface.
7391	16	No	The operation could not be performed because OLE DB provider "%ls" for linked server "%ls" was unable to begin a distributed transaction.
7392	16	No	Cannot start a transaction for OLE DB provider "%ls" for linked server "%ls".
7393	16	No	The OLE DB provider "%ls" for linked server "%ls" reported an error 0x%08X aborting the current transaction.
7394	16	No	The OLE DB provider "%ls" for linked server "%ls" reported an error committing the current transaction.
7395	16	No	Unable to start a nested transaction for OLE DB provider "%ls" for linked server "%ls". A nested transaction was required because the XACT_ABORT option was set to OFF.
7396	16	No	Varchar(max), nvarchar(max), varbinary(max) and large CLR type data types are not supported as return value or output parameter to remote queries.
7397	16	No	Remote function returned varchar(max), nvarchar(max), varbinary(max) or large CLR type value which is not supported.
7399	16	No	The OLE DB provider "%ls" for linked server "%ls" reported an error. %ls
7401	16	No	The OLE DB provider "%ls" returned invalid literal prefix/suffix string.
7403	16	No	The OLE DB provider "%ls" has not been registered.
7404	16	No	The server could not load DCOM.
7405	16	No	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.
7409	16	No	Could not start distributed query using integrated login because the user is logged in using SQL Server Authentication. Provide remote server login user ID and password in the connection string.
7410	16	No	Remote access is not allowed for impersonated security context.
7411	16	No	Server '%.*ls' is not configured for %ls.
7412	16	No	OLE DB provider "%ls" for linked server "%ls" returned message "%ls".
7413	16	No	Could not connect to linked server '%ls' (OLE DB Provider '%ls'). Enable delegation or use a remote SQL Server login for the current user.
7414	16	No	Invalid number of parameters. Rowset '%ls' expects %d parameter(s).
7415	16	No	Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server.
7416	16	No	Access to the remote server is denied because no login-mapping exists.
7417	16	No	GROUP BY ALL is not supported in queries that access remote tables if there is also a WHERE clause in the query.
7418	16	No	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	16	No	Lazy schema validation error. Linked server schema version has changed. Re-run the query.
7420	16	No	Remote access is not supported for transaction isolation level "%ls".
7421	10	No	Cannot fetch the rowset from OLE DB provider "%ls" for linked server "%ls". %ls.
7422	16	No	OLE DB provider "%ls" for linked server "%ls" returned an invalid index definition for table "%ls".
7423	16	No	The '%ls' OLE DB provider for the '%ls' linked server returned an invalid CLR type definition for the '%ls' table.
7424	10	No	OLE DB provider "%ls" for linked server "%ls" returned "%ls" with data type "%ls", which should be type "%ls".
7425	10	No	OLE DB provider "%ls" for linked server "%ls" returned an incorrect value for "%ls", which should be "%ls".
7426	10	No	OLE DB provider "%ls" for linked server "%ls" returned "%ls" without "%ls" being supported.
7427	10	No	OLE DB provider "%ls" for linked server "%ls" returned "%ls" for "%ls" during statistics gathering.
7428	10	No	OLE DB provider "%ls" for linked server "%ls" supported the schema lock interface, but returned "%ls" for "%ls".
7429	10	No	%hs SQL Server Remote Metadata Gather Time for Table %s.%s:%hs, CPU time = %lu ms, elapsed time = %lu ms.
7430	16	No	Out-of-process use of OLE DB provider "%ls" with SQL Server is not supported.
7431	16	No	Unable to delete OLE DB parameter properties.
7432	16	No	Heterogeneous queries and use of OLEDB providers are not supported in fiber mode.
7433	10	No	OLE DB provider '%ls' for linked server '%ls' returned truncated data for column '%ls.%ls'. The actual data length is %ls and truncated data length is %ls.
7435	16	No	The OLE DB provider "%ls" for linked server "%ls" returned unexpected NULL pointer for string column "%ls.%ls".
7601	16	No	Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because it is not full-text indexed.
7604	17	No	Full-text operation failed due to a time out.
7606	17	No	Could not find full-text index for database ID %d, table or indexed view ID %d.
7607	17	No	Search on full-text catalog '%ls' for database ID %d, table or indexed view ID %d with search condition '%ls' failed with unknown result (0x%x).
7608	16	No	An unknown full-text failure (0x%x) occurred during "%hs".
7609	17	No	Full-Text Search is not installed, or a full-text component cannot be loaded.
7610	16	No	Access is denied to "%.*ls", or the path is invalid.
7613	16	No	Cannot drop index '%.ls' because it enforces the full-text key for table or indexed view '%.ls'.
7614	16	No	Cannot alter or drop column '%.*ls' because it is enabled for Full-Text Search.
7615	16	No	A CONTAINS or FREETEXT predicate can only operate on one table or indexed view. Qualify the use of * with a table or indexed view name.
7616	16	No	Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. The functionality to disable and enable full-text search for a database is deprecated. Please change your application.
7617	16	No	Query does not reference the full-text indexed table or indexed view, or user does not have permission to perform this action.
7619	16	No	The execution of a full-text query failed. "%ls"
7620	16	No	The conversion to data type %ls failed for the full-text search key.
7621	16	No	Invalid use of full-text predicate in the HAVING clause.
7622	17	No	There is not sufficient disk space to complete this operation for the full-text catalog "%ls".
7624	16	No	Full-text catalog '%ls' is in an unusable state. Drop and re-create this full-text catalog.
7625	16	No	Full-text table or indexed view has more than one LCID among its full-text indexed columns.
7626	15	No	The top_n_by_rank argument ('%d') must be greater than or equal to zero.
7627	16	No	Cannot create the full-text catalog in the directory "%.*ls" for the clustered server. Only directories on a disk in the cluster group of the server can be used.
7629	17	No	Cannot open or query the full-text default path registry key. The full-text default catalog path is invalid.
7630	15	No	Syntax error near '%.ls' in the full-text search condition '%.ls'.
7632	15	No	The value of the Weight argument must be between 0.0 and 1.0.
7636	10	No	Warning: Request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently active for this table or indexed view.
7638	10	No	Warning: Request to stop change tracking has deleted all changes tracked on table or indexed view '%ls'.
7640	10	No	Warning: Request to stop tracking changes on table or indexed view '%.*ls' will not stop population currently in progress on the table or indexed view.
7641	16	No	Full-Text catalog '%ls' does not exist in database '%.*ls' or user does not have permission to perform this action.
7642	16	No	A full-text catalog named '%ls' already exists in this database. Use a different name.
7644	16	No	Full-text crawl manager has not been initialized. Any crawl started before the crawl manager was fully initialized will need to be restarted. Please restart SQL Server and retry the command. You should also check the error log to fix any failures that might have caused the crawl manager to fail.
7645	16	No	Null or empty full-text predicate.
7646	16	No	Fulltext predicate references columns from two different tables or indexed views '%.ls' and '%.ls' which is not allowed.
7647	10	No	Warning: Configuration of full-text catalog at '%ls' could not be saved during detach database.
7648	10	No	Warning: Failed to attach full-text catalog '%ls'.
7649	10	No	Warning: Failed to dismount full-text catalog at '%ls'.
7650	10	No	Warning: Failed to drop full-text catalog at '%ls'.
7651	10	No	Warning: The ongoing population is necessary to ensure an up-to-date index. If needed, stop change tracking first, and then deactivate the full-text index population.
7652	16	No	A full-text index for table or indexed view '%.*ls' has already been created.
7653	16	No	'%ls' is not a valid index to enforce a full-text search key. A full-text search key must be a unique, non-nullable, single-column index which is not offline, is not defined on a non-deterministic or imprecise nonpersisted computed column, does not have a filter, and has maximum size of %d bytes. Choose another index for the full-text key.
7654	16	No	Unable to obtain the population status of the table or indexed view '%.*ls'.
7655	16	No	TYPE COLUMN option must be specified with column of image or varbinary(max) type.
7656	16	No	Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode.
7657	10	No	Warning: Table or indexed view '%.*ls' 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.
7658	16	No	Table or indexed view '%.*ls' does not have a full-text index or user does not have permission to perform this action.
7659	16	No	Cannot activate full-text search for table or indexed view '%.*ls' because no columns have been enabled for full-text search.
7660	16	No	Full-text search must be activated on table or indexed view '%.*ls' before this operation can be performed.
7661	10	No	Warning: Full-text change tracking is currently enabled for table or indexed view '%.*ls'.
7662	10	No	Warning: Full-text auto propagation is currently enabled for table or indexed view '%.*ls'.
7663	16	No	Option 'WITH NO POPULATION' should not be used when change tracking is enabled.
7664	16	No	Full-text change tracking must be started on table or indexed view '%.*ls' before the changes can be flushed.
7665	16	No	Full Crawl must be executed on table or indexed view '%.*ls'. Columns affecting the index have been added or dropped since the last index full population.
7666	16	No	User does not have permission to perform this action.
7668	16	No	Cannot drop full-text catalog '%ls' because it contains a full-text index.
7669	10	No	Warning: Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode. Change tracking is stopped for this table or indexed view.
7670	16	No	Column '%.*ls' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column.
7671	16	No	Column '%.*ls' cannot be used as full-text type column for image column. It must be a character-based column with a size less or equal than %d characters.
7672	16	No	A full-text index cannot be created on the table or indexed view because duplicate column '%.*ls' is specified.
7673	10	No	Warning: Full-text change tracking is currently disabled for table or indexed view '%.*ls'.
7674	10	No	Warning: The fulltext catalog '%.*ls' is being dropped and is currently set as default.
7676	10	No	Warning: Full-text auto propagation is on. Stop crawl request is ignored.
7677	16	No	Column "%.*ls" is not full-text indexed.
7678	16	No	The following string is not defined as a language alias in syslanguages: %.*ls.
7679	16	No	Full-text index language of column "%.*ls" is not a language supported by full-text search.
7680	16	No	Default full-text index language is not a language supported by full-text search.
7681	10	No	Warning: Directory '%ls' does not have a valid full-text catalog. Full-text catalog header file or attach state file either is missing or corrupted. The full-text catalog cannot be attached.
7682	10	No	The component '%ls' reported error while indexing. Component path '%ls'.
7683	16	No	Errors were encountered during full-text index population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Please see full-text crawl logs for details.
7684	10	No	Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Failed to index the row.
7685	10	No	Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Attempt will be made to reindex it.
7689	16	No	Execution of a full-text operation failed. '%ls'
7690	16	No	Full-text operation failed because database is read only.
7691	16	No	Access is denied to full-text log path. Full-text logging is disabled for database '%ls', catalog '%ls' (database ID '%d', catalog ID '%d').
7692	16	No	Full-text catalog path '%.*ls' exceeded %d character limit.
7693	16	No	Full-text initialization failed to create a memory clerk.
7694	16	No	Failed to pause catalog for backup. Backup was aborted.
7696	16	No	Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed.
7697	10	No	Warning: Full-text index on table or indexed view '%.ls' in database '%.ls' has been changed after full-text catalog files backup. A full population is required to bring full-text index to a consistent state.
7698	16	No	GROUP BY ALL cannot be used in full text search queries.
7699	16	No	TYPE COLUMN option is not allowed for column types other than image or varbinary(max).
7702	16	No	Empty Partition function type-parameter-list is not allowed when defining a partition function.
7703	16	No	Can not create RANGE partition function with multiple parameter types.
7704	16	No	The type '%.*ls' is not valid for this operation.
7705	16	No	Could not implicitly convert range values type specified at ordinal %d to partition function parameter type.
7706	16	No	Partition function '%ls' is being used by one or more partition schemes.
7707	16	No	The associated partition function '%ls' generates more partitions than there are file groups mentioned in the scheme '%ls'.
7708	16	No	Duplicate range boundary values are not allowed in partition function boundary values list. Partition boundary values at ordinal %d and %d are equal.
7709	10	No	Warning: Range value list for partition function '%.ls' is not sorted by value. Mapping of partitions to filegroups during CREATE PARTITION SCHEME will use the sorted boundary values if the function '%.ls' is referenced in CREATE PARTITION SCHEME.
7710	10	No	Warning: The partition scheme '%.*ls' does not have any next used filegroup. Partition scheme has not been changed.
7711	16	No	The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table is partitioned.
7712	10	No	Partition scheme '%.ls' has been created successfully. '%.ls' is marked as the next used filegroup in partition scheme '%.*ls'.
7713	10	No	%d filegroups specified after the next used filegroup are ignored.
7714	16	No	Partition range value is missing.
7715	16	No	The specified partition range value could not be found.
7716	16	No	Can not create or alter a partition function to have zero partitions.
7717	16	No	The partition scheme "%.*ls" is currently being used to partition one or more tables.
7718	16	No	Partition range value cannot be specified for hash partitioning.
7719	16	No	CREATE/ALTER partition function failed as only a maximum of %d partitions can be created.
7720	16	No	Data truncated when converting range values to the partition function parameter type. The range value at ordinal %d requires data truncation.
7721	16	No	Duplicate range boundary values are not allowed in partition function boundary values list. The boundary value being added is already present at ordinal %d of the boundary value list.
7722	16	No	Invalid partition number %I64d specified for %S_MSG '%.*ls', partition number can range from 1 to %d.
7723	16	No	Only a single filegroup can be specified while creating partition scheme using option ALL to specify all the filegroups.
7724	16	No	Computed column cannot be used as a partition key if it is not persisted. Partition key column '%.ls' in table '%.ls' is not persisted.
7725	16	No	Alter partition function statement failed. Cannot repartition table '%.ls' by altering partition function '%.ls' because its clustered index '%.*ls' is disabled.
7726	16	No	Partition column '%.ls' has data type %s which is different from the partition function '%.ls' parameter data type %s.
7727	16	No	Collation of partition column '%.ls' does not match collation of corresponding parameter in partition function '%.ls'.
7728	16	No	Invalid partition range: %d TO %d. Lower bound must not be greater than upper bound.
7729	16	No	Cannot specify partition number in the %S_MSG %S_MSG statement as the %S_MSG '%.*ls' is not partitioned.
7730	16	No	Alter %S_MSG statement failed because partition number %d does not exist in %S_MSG '%.*ls'.
7731	16	No	Cannot specify partition number in Alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls'.
7732	16	No	Cannot specify partition number in Alter index statement along with keyword ALL to rebuild partitions of table '%.*ls' when the table does not have any regular indexes.
7733	16	No	'%ls' statement failed. The %S_MSG '%.ls' is partitioned while %S_MSG '%.ls' is not partitioned.
7734	10	No	The %S_MSG '%.ls' specified for the clustered index '%.ls' was used for table '%.ls' even though %S_MSG '%.ls' is specified for it.
7735	16	No	Cannot specify partition number in alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls' as %S_MSG is not partitioned.
7736	16	No	Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning.
7737	16	No	Filegroup %.ls is of a different filegroup type than the first filegroup in partition scheme %.ls
7738	16	No	Cannot enable compression for object '%.*ls'. Only SQL Server Enterprise Edition supports compression.
7801	15	No	The required parameter %.*ls was not specified.
7802	16	No	Functions that have a return type of "%.*ls" are unsupported through SOAP invocation.
7803	15	No	The clause %.ls can not be used in the %.ls statement.
7804	15	No	%.ls and %.ls can not share the same value.
7805	16	No	The parameter SITE can not be prefixed by a scheme such as 'https://'. Valid values for SITE include {'*' \| '+' \| 'site_name'}.
7806	16	No	The URL specified by endpoint '%.*ls' is already registered to receive requests or is reserved for use by another service.
7807	16	No	An error ('0x%x') occurred while attempting to register the endpoint '%.*ls'.
7808	10	No	The endpoint '%.*ls' could not be unregistered.
7809	10	No	Cannot find the object '%.*ls', because it does not exist or you do not have permission.
7810	15	No	The value '%d' is not within range for the '%.*ls' parameter.
7811	16	No	COMPUTE BY queries are not supported over SOAP.
7812	10	Yes	The endpoint '%.*ls' has been established in metadata, but HTTP listening has not been enabled because HTTP support did not start successfully. Verify that the operating system and the edition of SQL Server supports native HTTP access. Check the SQL Server error log for any errors that might have occurred while starting HTTP support.
7813	16	No	The parameter PATH must be supplied in its canonical form. An acceptable PATH is '%.*ls'.
7814	10	No	The specified value '%.*ls' already exists.
7815	10	No	The specified value '%.*ls' does not exist.
7816	15	No	A duplicate parameter was specified, '%.*ls'.
7817	16	No	The Base64 encoded input data was malformed for the parameter "%.*ls".
7818	16	No	The request exceeds an internal limit. Simplify or reduce the size of the request.
7819	15	No	The SOAP method object '%.*ls' must be specified using a fully qualified three-part name.
7820	16	No	SOAP namespaces beginning with '%.*ls' are disallowed because they are reserved for system use.
7821	10	No	Cannot find the database '%.*ls', because it does not exist or you do not have permission.
7822	16	No	An unexpected XML node "%.ls" (in the namespace "%.ls") was found in the "%.ls" element (in the "%.ls" namespace) of the SOAP request.
7823	16	No	The "%.ls" XML element (in the "%.ls" namespace) was expected in the "%.ls" element (in the "%.ls" namespace) of the SOAP request.
7824	16	No	The "%.ls" XML element (in the "%.ls" namespace) was expected as the topmost node of the SOAP request.
7825	16	No	A SOAP method element was expected in the "%.ls" element (in the "%.ls" namespace) of the SOAP request.
7826	16	No	Unexpected character data was found in the "%.ls" element (in the "%.ls" namespace) of the SOAP request.
7827	14	No	The user does not have permission to reserve and unreserve HTTP namespaces.
7828	11	No	The statement is not supported on this version of the operating system. Could not find Httpapi.dll in the path.
7829	11	No	The statement is not supported on this version of the operating system. Could not find function entry point '%.*ls' in Httpapi.dll.
7830	16	No	Unable to complete the operation because of an unexpected error.
7831	16	No	A reservation for this HTTP namespace (%.*ls) already exists.
7832	16	No	A reservation for this HTTP namespace (%.*ls) does not exist.
7833	16	No	The HTTP namespace (%.*ls) is in an invalid format. Specify the namespace in its canonical form.
7834	10	No	The reservation for the HTTP namespace (%.*ls) has been deleted. If there are any endpoints associated with this namespace, they will continue to receive and process requests until the server is restarted.
7835	16	Yes	Endpoint '%.*ls' has been disabled because it is insecurely configured. For a more information, attempt to start the endpoint using the ALTER ENDPOINT statement.
7836	20	No	A fatal error occurred while reading the input stream from the network. The maximum number of network packets in one request was exceeded. Try using bulk insert, increasing network packet size, or reducing the size of the request. The session will be terminated.
7847	16	No	XML data was found in the parameter '%.*ls' which is not an XML parameter. Please entitize any invalid XML character data in this parameter, or pass the parameter in typed as XSD:anyType or sqltypes:xml.
7848	15	No	An invalid or unsupported localeId was specified for parameter "%.*ls".
7849	15	No	Invalid sqlCompareOptions were specified for parameter "%.*ls".
7850	16	No	The SQL Server Service account does not have permission to register the supplied URL on the endpoint '%.*ls'. Use sp_reserve_http_namespace to explicitly reserve the URL namespace before you try to register the URL again.
7851	15	No	The %.ls attribute must be specified on the %.ls element of the parameter "%.ls" because it is of type %.ls.
7852	15	No	Parameter "%.ls": If the %.ls attribute appears on a parameter value node of type "%.ls" (in the namespace "%.ls"), it must refer to a CLR type.
7853	16	No	The URL specified as the path ("%.ls") is not in an absolute format, and must begin with "%.ls".
7854	16	No	The URL value specified for the "%.*ls" parameter is too long.
7855	15	No	Reading from HTTP input stream failed.
7856	16	No	XML parameters do not support non-unicode element or attribute values.
7857	16	No	Parameter "%.*ls": Function or procedure parameters with improperly formatted or deprecated names are not supported through Native SOAP access. Refer to documentation for rules concerning the proper naming of parameters.
7858	16	No	The "%.ls" XML element (in the "%.ls" namespace) in the "%.ls" element (in the "%.ls" namespace) of the SOAP request contained an invalid binary type.
7859	15	No	Parameter "%.ls": Parameter collation cannot be specified on the "%.ls" node (in the namespace "%.*ls").
7860	15	No	An endpoint's transport or content cannot be changed through the ALTER ENDPOINT statement. Use DROP ENDPOINT and execute the CREATE ENDPOINT statement to make these changes.
7861	15	No	%.ls endpoints can only be of the "FOR %.ls" type.
7862	16	No	An endpoint of the requested type already exists. Only one endpoint of this type is supported. Use ALTER ENDPOINT or DROP the existing endpoint and execute the CREATE ENDPOINT statement.
7863	16	No	The endpoint was not changed. The ALTER ENDPOINT statement did not contain any values to modify or update.
7864	16	No	CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection endpoint is reserved and cannot be updated.
7865	16	No	Web Services Description Language (WSDL) generation failed because the system was unable to query the metadata for the endpoint.
7866	16	No	XML attribute and element values larger than 4000 characters are only allowed within the SOAP Body node.
7867	15	No	An invalid sqlCollationVersion was specified for parameter "%.*ls".
7868	15	No	An invalid sqlSortId was specified for parameter "%.*ls".
7869	16	No	The endpoint name '%.ls' is reserved for used by SQL. Endpoint names cannot begin with '%.ls'.
7870	16	No	The AFFINITY clause is not supported for endpoints of this type.
7871	16	No	The clause "%.*ls" is not valid for this endpoint type.
7872	16	No	%.ls is not a parameter for procedure "%.ls", or it was supplied out of order.
7873	16	No	The endpoint "%.*ls" is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP Transact-SQL endpoints.
7874	16	No	An endpoint already exists with the bindings specified. Only one endpoint supported for a specific binding. Use ALTER ENDPOINT or DROP the existing endpoint and execute the CREATE ENDPOINT statement.
7875	16	No	An unexpected XML construct was found in the character data of the "%.ls" element (in the "%.ls" namespace) of the SOAP request.
7878	16	No	This "%.*ls ENDPOINT" statement is not supported on this edition of SQL Server.
7879	10	No	SQL Server is waiting for %d remaining sessions and connections to close. If these sessions are not closed within a reasonable amount of time, "polite" shutdown will be aborted. This message may appear several times before SQL Server is shutdown.
7880	10	No	SQL Server has successfully finished closing sessions and connections.
7881	10	No	SQL Server was unable to close sessions and connections in a reasonable amount of time and is aborting "polite" shutdown.
7882	16	No	OUTPUT was requested for parameter '%.*ls', which is not supported for a WEBMETHOD with FORMAT=NONE.
7883	16	No	User-defined functions cannot be used for a WEBMETHOD with FORMAT=NONE.
7884	20	Yes	Violation of tabular data stream (TDS) protocol. This is most often caused by a previous exception on this task. The last exception on the task was error %d, severity %d, address 0x%p. This connection will be terminated.
7885	20	Yes	Network error 0x%lx occurred while sending data to the client on process ID %d batch ID %d. A common cause for this error is if the client disconnected without reading the entire response from the server. This connection will be terminated.
7886	20	Yes	A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
7887	20	Yes	The IPv6 address specified is not supported. Only addresses that are in their numeric, canonical form are supported for listening.
7888	20	Yes	The IPv6 address specified is not supported. The server may not be configured to allow for IPv6 connectivity, or the address may not be in a recognized IPv6 format.
7889	16	No	The SOAP headers on the request have exceeded the size limits established for this endpoint. The endpoint owner may increase these limits via ALTER ENDPOINT.
7890	16	No	An error occurred while attempting to register the endpoint '%.*ls'. One or more of the ports specified in the CREATE ENDPOINT statement may be bound to another process. Attempt the statement again with a different port or use netstat to find the application currently using the port and resolve the conflict.
7891	10	No	Creation of a TSQL endpoint will result in the revocation of any 'Public' connect permissions on the '%.ls' endpoint. If 'Public' access is desired on this endpoint, reapply this permission using 'GRANT CONNECT ON ENDPOINT::[%.ls] to [public]'.
7892	16	No	Internal subset DTDs inside SOAP requests are not allowed.
7893	15	No	Parameter '%.ls': Incompatible XML attributes were present. The '%.ls' attribute and the '%.ls' attribute may not both be present on a parameter value node of type '%.ls' (in the namespace '%.*ls').
7894	16	Yes	Listening has not been started on the endpoint '%.*ls' found in metadata. Endpoint operations are disabled on this edition of SQL Server.
7895	14	No	Only a system administrator can specify a custom WSDL stored procedure on the endpoint.
7896	16	No	The column or parameter '%.*ls' uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier.
7897	10	No	Creating and altering SOAP endpoints will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
7898	10	Yes	SQL Server native SOAP support is now deprecated and will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
7899	16	No	The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier.
7901	16	No	The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.
7903	16	No	Table error: The orphaned file "%.ls" was found in the FILESTREAM directory ID %.ls for object ID %d, index ID %d, partition ID %I64d, column ID %d.
7904	16	No	Table error: Cannot find the FILESTREAM file "%.ls" for column ID %d (column directory ID %.ls) in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d.
7905	16	No	Database error: The directory "%.*ls" is not a valid FILESTREAM directory.
7906	16	No	Database error: The file "%.*ls" is not a valid FILESTREAM file.
7907	16	No	Table error: The directory "%.ls" under the rowset directory ID %.ls is not a valid FILESTREAM directory.
7908	16	No	Table error: The file "%.ls" in the rowset directory ID %.ls is not a valid FILESTREAM file.
7909	20	No	The emergency-mode repair failed.You must restore from backup.
7910	10	No	Repair: The page %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
7911	10	No	Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
7912	10	No	Repair: The extent %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
7913	10	No	Repair: The extent %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
7914	10	No	Repair: %ls page at %S_PGID has been rebuilt.
7915	10	No	Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt.
7916	10	No	Repair: Deleted record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), on page %S_PGID, slot %d. Indexes will be rebuilt.
7917	10	No	Repair: Converted forwarded record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), at page %S_PGID, slot %d to a data row.
7918	10	No	Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
7919	16	No	Repair statement not processed. Database needs to be in single user mode.
7920	10	No	Processed %ld entries in system catalog for database ID %d.
7921	16	No	Repair statement not processed. Database cannot be a snapshot.
7922	16	No	***************************************************************
7923	10	No	Table %.*ls Object ID %ld.
7924	10	No	Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d.
7925	10	No	Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents.
7926	16	No	Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
7927	10	No	Total number of extents is %I64d.
7928	16	No	The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
7929	16	No	Check statement aborted. Database contains deferred transactions.
7930	16	No	Mirroring must be removed from the database for this DBCC command.
7931	16	No	Database error: The FILESTREAM directory ID %.*ls for a partition was seen two times.
7932	16	No	Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d is in filegroup %d, but should be in filegroup %d.
7933	16	No	Table error: A FILESTREAM directory ID %.*ls exists for a partition, but the corresponding partition does not exist in the database.
7934	16	No	Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d was not found.
7935	16	No	Table error: A FILESTREAM directory ID %.*ls exists for a column of object ID %d, index ID %d, partition ID %I64d, but that column does not exist in the partition.
7936	16	No	Table error: The FILESTREAM directory ID %.*ls exists for column ID %d of object ID %d, index ID %d, partition ID %I64d, but that column is not a FILESTREAM column.
7937	16	No	Table error: The FILESTREAM directory ID %.*ls for column ID %d of object ID %d, index ID %d, partition ID %I64d was not found.
7938	16	No	Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name "%.*ls" twice in the column directory %d (for column ID %d).
7939	16	No	Cannot detach database '%.*ls' because it does not exist.
7940	16	No	System databases master, model, msdb, and tempdb cannot be detached.
7941	16	No	Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name "%.*ls" twice in the column ID %d (for column directory %d).
7942	10	No	DBCC %ls scanning '%.*ls' table...
7943	10	No	Table: '%.*ls' (%d); index ID: %d, database ID: %d
7944	10	No	%ls level scan performed.
7945	10	No	- Pages Scanned................................: %I64d
7946	10	No	- Extents Scanned..............................: %I64d
7947	10	No	- Extent Switches..............................: %I64d
7948	10	No	- Avg. Pages per Extent........................: %3.1f
7949	10	No	- Scan Density [Best Count:Actual Count].......: %4.2f%ls [%I64d:%I64d]
7950	10	No	- Logical Scan Fragmentation ..................: %4.2f%ls
7951	10	No	Warning: Could not complete filestream consistency checks due to an operating system error. Any consistency errors found in the filestream subsystem will be silenced. Please refer to other errors for more information. This condition is likely transient; try rerunning the command.
7952	10	No	- Extent Scan Fragmentation ...................: %4.2f%ls
7953	10	No	- Avg. Bytes Free per Page.....................: %3.1f
7954	10	No	- Avg. Page Density (full).....................: %4.2f%ls
7955	16	No	Invalid SPID %d specified.
7957	10	No	Cannot display the specified SPID's buffer; in transition.
7958	16	No	The specified SPID does not process input/output data streams.
7960	16	No	An invalid server process identifier (SPID) %d or batch ID %d was specified.
7961	16	No	Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.ls) , page ID %S_PGID, row ID %d. Column '%.ls' is a var column with a NULL value and non-zero data length
7962	16	No	Invalid BATCHID %d specified.
7963	16	No	Database error: The file "%.*ls" is not a valid FILESTREAM LOG file.
7964	10	No	Repair: Deleted FILESTREAM file "%.ls" for column ID %d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.ls) on page %S_PGID, slot %d.
7965	16	No	Table error: Could not check object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) page(s).
7966	10	No	Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped.
7968	10	No	Transaction information for database '%.*ls'.
7969	16	No	No active open transactions.
7970	10	No	%hsOldest active transaction:
7971	10	No	SPID (server process ID): %d%s
7972	10	No	UID (user ID) : %d
7974	10	No	Name : %.*ls
7975	10	No	LSN : (%d:%d:%d)
7977	10	No	Start time : %.*ls
7978	10	No	SID : %.*ls
7979	10	No	%hsReplicated Transaction Information:
7980	10	No	Oldest distributed LSN : (%d:%d:%d)
7982	10	No	Oldest non-distributed LSN : (%d:%d:%d)
7983	14	No	User '%.ls' does not have permission to run DBCC %ls for database '%.ls'.
7984	16	No	System table pre-checks: Object ID %d. Page %S_PGID has unexpected page type %d. Check statement terminated due to unrepairable error.
7985	16	No	System table pre-checks: Object ID %d. Could not read and latch page %S_PGID with latch type %ls. Check statement terminated due to unrepairable error.
7986	16	No	System table pre-checks: Object ID %d has cross-object chain linkage. Page %S_PGID points to %S_PGID in alloc unit ID %I64d (should be %I64d). Check statement terminated due to unrepairable error.
7987	16	No	System table pre-checks: Object ID %d has chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->prev = %S_PGID. Check statement terminated due to unrepairable error.
7988	16	No	System table pre-checks: Object ID %d. Loop in data chain detected at %S_PGID. Check statement terminated due to unrepairable error.
7992	16	No	Cannot shrink 'read only' database '%.*ls'.
7993	10	No	Cannot shrink file '%d' in database '%.*ls' to %u pages as it only contains %u pages.
7995	16	No	Database '%.*ls': consistency errors in system catalogs prevent further DBCC %ls processing.
7996	16	No	Extended stored procedures can only be created in the master database.
7997	16	No	'%.*ls' does not contain an identity column.
7998	16	No	Checking identity information: current identity value '%.hs', current column value '%.hs'.
7999	16	No	Could not find any index named '%.ls' for table '%.ls'.

Errors 8,000 to 8,999

Error	Severity	Event Logged	Description
8001	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter.
8002	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (XML) has an invalid database or schema specified.
8003	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is %d.
8004	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. The RPC name is invalid.
8005	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter name is invalid.
8006	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter status flags are invalid.
8007	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The chunking format is incorrect for a large object parameter of type 0x%02X.
8008	16	No	The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%d).
8009	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is unknown.
8010	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X is different from the one sent last time.
8011	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata.
8012	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata.
8013	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid instance length.
8014	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata.
8015	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is an untyped NULL but is marked as an output parameter.
8016	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid data length or metadata length.
8017	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid precision or scale.
8018	16	No	Invalid parameter %d ('%.*ls'): Data type 0x%02X is a deprecated large object, or LOB, but is marked as output parameter. Deprecated types are not supported as output parameters. Use current large object types instead.
8019	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid user type specified.
8020	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid length for serialization metadata.
8021	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid database specified.
8022	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.ls"): The supplied value is NULL and data type %.ls cannot be NULL. Check the source data for invalid values.
8023	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.ls"): The supplied value is not a valid instance of data type %.ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.
8024	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid collation for type-specific metadata.
8025	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has a maximum length different from the one sent last time.
8026	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has an actual length different from the one sent last time.
8027	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid schema specified.
8028	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.ls"): The supplied length is not valid for data type %.ls. Check the source data for invalid lengths. An example of an invalid length is data of nchar type with an odd length in bytes.
8029	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) unexpected token encountered processing a table-valued parameter.
8030	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (XML) has an invalid database or schema specified.
8031	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The chunking format is incorrect for a large object parameter of data type 0x%02X.
8032	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X is unknown.
8033	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata.
8034	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata.
8035	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid instance length.
8036	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata.
8037	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid data length or metadata length.
8038	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid precision or scale.
8039	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid user type specified.
8040	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid length for serialization metadata.
8041	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid database specified.
8042	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.ls"), row %I64d, column %d: The supplied value is NULL and data type %.ls cannot be NULL. Check the source data for invalid values.
8043	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.ls"), row %I64d, column %d: The supplied value is not a valid instance of data type %.ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.
8044	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid collation for type-specific metadata.
8045	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid schema specified.
8046	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.ls"), row %I64d, column %d: The supplied length is not valid for data type %.ls. Check the source data for invalid lengths. An example of an invalid length is data of nchar type with an odd length in bytes.
8047	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has a non-zero length database name specified. Database name is not allowed with a table-valued parameter, only schema name and type name are valid.
8048	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid schema specified.
8049	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid type name specified.
8050	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column count specified.
8051	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column name specified.
8052	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) timestamp column is required to be default.
8053	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column flag specified.
8054	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid ordering and uniqueness metadata specified.
8055	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid column ordering metadata specified.
8056	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has too many optional metadata tokens specified.
8057	16	No	Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type). The specified column is computed or default and has ordering or uniqueness set. Ordering and uniqueness can only be set on columns that have client supplied data.
8058	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d, to a parameterized string has no table type defined.
8059	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter "%.*ls", to a parameterized string has no table type defined.
8060	16	No	The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) is null and not set to default. A null table-valued parameter is required to be sent as a default parameter.
8061	16	No	The data for table-valued parameter "%.*ls" doesn't conform to the table type of the parameter.
8062	16	No	The data for the table-valued parameter %d doesn't conform to the table type of the parameter.
8063	16	No	The incoming tabular data stream (TDS) remote procedure call stream is sending an unlimited length CLR type. Parameter %d ("%.ls") is defined as type %.ls. This type is not supported by down-level clients. Send the serialized data of the large CLR type as varbinary(max), or upgrade the client driver to one that supports unlimited CLR types.
8064	16	No	Parameter %d ([%.ls].[%.ls].[%.*ls]): The CLR type does not exist or you do not have permissions to access it.
8101	16	No	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	16	No	Cannot update identity column '%.*ls'.
8105	16	No	'%.*ls' is not a user table. Cannot perform SET operation.
8106	16	No	Table '%.*ls' does not have the identity property. Cannot perform SET operation.
8107	16	No	IDENTITY_INSERT is already ON for table '%.ls.%.ls.%.ls'. Cannot perform SET operation for table '%.ls'.
8108	16	No	Cannot add identity column, using the SELECT INTO statement, to table '%.ls', which already has column '%.ls' that inherits the identity property.
8109	16	No	Attempting to add multiple identity columns to table '%.*ls' using the SELECT INTO statement.
8110	16	No	Cannot add multiple PRIMARY KEY constraints to table '%.*ls'.
8111	16	No	Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'.
8112	16	No	Cannot add more than one clustered index for constraints on table '%.*ls'.
8113	16	No	Incorrect use of the XML data type method '%.*ls'. A mutator method is expected in this context.
8114	16	No	Error converting data type %ls to %ls.
8115	16	No	Arithmetic overflow error converting %ls to data type %ls.
8116	16	No	Argument data type %ls is invalid for argument %d of %ls function.
8117	16	No	Operand data type %ls is invalid for %ls operator.
8118	16	No	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	16	No	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	16	No	Column '%.ls.%.ls' is invalid in the select list because it