search

Which of these statements about the destination component of communication is not correct?

1 Jahrs vor
Kommentare: 0
Ansichten: 77

Skip to main content

This browser is no longer supported.

Show

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Database engine errors

  • Article
  • 08/19/2022
  • 908 minutes to read

In this article

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 -2 to 999

ErrorSeverityEvent LoggedDescription
-2 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2).
-1 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1).
2 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
21 20 No Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
53 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider).
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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

ErrorSeverityEvent LoggedDescription
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 is not contained in either an aggregate function or the GROUP BY clause.
8121 16 No Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause.
8123 16 No A correlated expression is invalid because it is not in a GROUP BY clause.
8124 16 No Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression.
8125 16 No An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated.
8126 16 No Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause.
8127 16 No Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause.
8128 10 Yes Using '%s' version '%s' to execute extended stored procedure '%s'. This is an informational message only; no user action is required.
8129 16 No The new disk size must be greater than %d. Consider using DBCC SHRINKDB.
8131 10 Yes Extended stored procedure DLL '%s' does not export __GetXpVersion(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Services" in the documentation for more information.
8132 10 Yes Extended stored procedure DLL '%s' reports its version is %d.%d. The expected version is %d.%d.
8133 16 No None of the result expressions in a CASE specification can be NULL.
8134 16 No Divide by zero error encountered.
8135 16 No Table level constraint does not specify column list, table '%.*ls'.
8136 16 No Duplicate columns specified in %ls constraint key list, table '%.*ls'.
8137 16 No Incorrect use of the XML data type method '%.*ls'. A non-mutator method is expected in this context.
8138 16 No More than 16 columns specified in foreign key column list, table '%.*ls'.
8139 16 No Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'.
8140 16 No More than one key specified in column level %ls constraint, table '%.*ls'.
8141 16 No Column %ls constraint for column '%.*ls' references another column, table '%.*ls'.
8143 16 No Parameter '%.*ls' was supplied multiple times.
8144 16 No Procedure or function %.*ls has too many arguments specified.
8145 16 No %.*ls is not a parameter for procedure %.*ls.
8146 16 No Procedure %.*ls has no parameters and arguments were supplied.
8147 16 No Could not create IDENTITY attribute on nullable column '%.*ls', table '%.*ls'.
8148 16 No More than one column %ls constraint specified for column '%.*ls', table '%.*ls'.
8149 16 No OLE Automation objects are not supported in fiber mode.
8150 16 No Multiple NULL constraints were specified for column '%.*ls', table '%.*ls'.
8151 16 No Both a PRIMARY KEY and UNIQUE constraint have been defined for column '%.*ls', table '%.*ls'. Only one is allowed.
8152 16 No String or binary data would be truncated.
8153 10 No Warning: Null value is eliminated by an aggregate or other SET operation.
8154 15 No The table '%.*ls' is ambiguous.
8155 15 No No column name was specified for column %d of '%.*ls'.
8156 15 No The column '%.*ls' was specified multiple times for '%.*ls'.
8158 15 No '%.*ls' has more columns than were specified in the column list.
8159 15 No '%.*ls' has fewer columns than were specified in the column list.
8160 15 No A GROUPING or GROUPING_ID function can only be specified when there is a GROUP BY clause.
8161 15 No Argument %d of the %.*ls function does not match any of the expressions in the GROUP BY clause.
8162 16 No The formal parameter "%.*ls" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.
8164 16 No An INSERT EXEC statement cannot be nested.
8165 16 No Invalid subcommand value %d. Legal range from %d to %d.
8166 16 No Constraint name '%.*ls' not permitted. Constraint names cannot begin with a number sign (#).
8167 16 No The type of column "%.*ls" conflicts with the type of other columns specified in the UNPIVOT list.
8168 16 No Cannot create, drop, enable, or disable more than one constraint, column, or trigger named '%.*ls' in this context. Duplicate names are not allowed.
8169 16 No Conversion failed when converting from a character string to uniqueidentifier.
8170 16 No Insufficient result space to convert uniqueidentifier value to char.
8171 16 No Hint '%ls' on object '%.*ls' is invalid.
8172 16 No The argument %d of the XML data type method "%.*ls" must be a string literal.
8173 15 No Incorrect syntax was used to invoke the XML data type method '%.*ls'.
8174 16 No Schema lock with handle %d not found.
8175 10 No Could not find table %.*ls. Will try to resolve this table name later.
8176 16 No Resync procedure expects value of key '%.*ls', which was not supplied.
8177 16 No Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause.
8178 16 No The parameterized query '%.*ls' expects the parameter '%.*ls', which was not supplied.
8179 16 No Could not find prepared statement with handle %d.
8180 16 No Statement(s) could not be prepared.
8181 16 No Text for '%.*ls' is missing from the system catalog. The object must be dropped and re-created before it can be used.
8183 16 No Only UNIQUE or PRIMARY KEY constraints can be created on computed columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that computed columns be persisted.
8184 16 No Error in binarychecksum. There are no comparable columns in the binarychecksum input.
8185 16 No Error expanding "*": An incomparable column has been found in an underlying table or view.
8186 16 No Function '%.*ls' can be used only on user and system tables.
8187 16 Yes The prepared handle %d is currently being used by another command (error state: %d).
8188 16 No There is already a SQL type for assembly type "%.*ls" on assembly "%.*ls". Only one SQL type can be mapped to a given assembly type. CREATE TYPE fails.
8189 16 No You do not have permission to run '%ls'.
8190 16 No Cannot compile replication filter procedure without defining table being filtered.
8191 16 No Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements.
8192 16 No Replication filter procedures cannot have parameters.
8193 16 No Cannot execute a procedure marked FOR REPLICATION.
8195 16 No Cannot create "%.*ls" on "%.*ls". Insert, Update, and Delete triggers can only be created on user tables and views.
8196 16 No Duplicate column specified as ROWGUIDCOL.
8197 16 No The object '%.*ls' does not exist or is invalid for this operation.
8199 16 No In EXECUTE <procname>, procname can only be a literal or variable of type char, varchar, nchar, or nvarchar.
8301 10 No Use of level0type with value 'USER' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Users are now schema scoped and hence use level0type with value 'SCHEMA' and level1type with value 'USER' for extended properties on USER.
8302 10 No CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new development work, and plan to modify applications that currently use them. Use check constraints instead, which are created using the CHECK keyword of CREATE TABLE or ALTER TABLE.
8303 10 No CREATE DEFAULT and DROP DEFAULT will be removed in a future version of SQL Server. Avoid using CREATE DEFAULT and DROP DEFAULT in new development work, and plan to modify applications that currently use them. Instead, use default definitions created using the DEFAULT keyword of ALTER TABLE or CREATE TABLE.
8304 10 No INDEXKEY_PROPERTY 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 the feature. Use sys.index_columns instead.
8305 10 No The TEXT IN ROW feature will be removed in a future version of SQL Server. Avoid using sp_tableoption for TEXT IN ROW option in new development work, and plan to modify applications that currently use the text in row option. The preferred method of storing large data is through use of the varchar(max), nvarchar(max) and varbinary(max) data types.
8306 10 No Use of level0type with value 'TYPE' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Types are now schema scoped and hence use level0type with value 'SCHEMA' and level1type with value 'TYPE' for extended properties on TYPE.
8307 10 No FILE_ID 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 the feature. Use FILE_IDEX instead.
8308 10 No USER_ID will be removed from a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use DATABASE_PRINCIPAL_ID instead.
8310 16 No Cannot create (or open) named file mapping object '%ls'. SQL Server performance counters are disabled.
8311 16 No Unable to map view of file mapping object '%ls' into SQL Server process address space. SQL Server performance counters are disabled.
8312 16 No Cannot create (or open) named mutex '%ls'. SQL Server performance counters are disabled.
8313 16 No Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
8314 16 No SQL Server performance object '%ls' not found in registry. SQL Server performance counters are disabled.
8315 16 No SQL Server performance counter '%ls' not found in registry. SQL Server performance counters are disabled.
8316 16 No Cannot open registry key 'HKLM%ls'. SQL Server performance counters are disabled.
8317 16 No Cannot query value '%ls' associated with registry key 'HKLM%ls'. SQL Server performance counters are disabled.
8318 16 No There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters are disabled.
8319 16 No Windows kernel object '%ls' already exists. It's not owned by the SQL Server service account. SQL Server performance counters are disabled.
8320 10 No @@REMSERVER 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 the feature. Use linked servers and linked server stored procedures instead.
8350 10 No Use of NOLOCK or READUNCOMMITTED hints in the FROM clause of an UPDATE or DELETE statement on the target table of the statement ('%.*ls') is deprecated. These hints have no effect in this location. Microsoft recommends that you remove these hints from this statement. Support for these hints in this location will be removed in a future version of SQL Server.
8351 16 Yes A trace control request could not be processed because invalid parameters were specified when events were registered. Confirm that the parameters are within valid ranges.
8352 16 Yes Cannot find the requested trace template: id = %ls.
8353 16 Yes Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server.
8354 16 Yes Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls.
8355 16 Yes Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
8356 16 Yes Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future.
8357 16 Yes Event Tracing for Windows (ETW) failed to send event. This may be due to low resource conditions. The same send failure may not be reported in the future.
8358 16 Yes Event Tracing for Windows (ETW) failed to send event. Event message size exceeds limit. The same send failure may not be reported in the future.
8359 16 Yes SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported in the future.
8360 16 Yes SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future.
8379 10 No Old style RAISERROR (Format: RAISERROR integer string) will be removed in the next version of SQL Server. Avoid using this in new development work, and plan to modify applications that currently use it to use new style RAISERROR.
8380 10 No SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server '%.*ls'.
8381 10 No SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) for ad hoc connection to SQL Server.
8382 10 No Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version.
8383 10 No Specifying HOLDLOCK as a table hint without parentheses is a deprecated feature and will be removed in the next version of SQL Server.
8384 10 No Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints.
8385 10 No The select list of an aggregate indexed view must contain count_big(*) in 90 compatibility mode and higher.
8386 10 No Use of hint "%.*ls" on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove the use of this hint.
8387 10 No The indirect application of table hints to an invocation of a multi-statement table-valued function (TVF) through a view will be removed in a future version of SQL Server. Remove hints on references to view "%.*ls" because it references a multi-statement TVF.
8388 10 No The ability to return results from triggers 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.
8389 10 No The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work and plan to modify applications that currently use it.
8390 10 No The '::' function calling syntax will be removed in a future version of SQL Server. Replace it with "sys.".
8391 10 No The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX <1p-name> ON {<3p-table-name> | <3p-view-name> }
8393 10 No The ability to not specify a column name when the datatype is timestamp 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.
8394 10 No Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future version of SQL Server. Avoid using this syntax structure in new development work, and plan to modify applications that currently use the feature.
8396 10 No %ls 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. Use %ls instead.
8397 10 No The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types instead.
8398 10 No The use of more than two-part column names 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.
8399 10 No %ls 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.
8401 16 No This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue '%.*ls'.
8402 16 No The data type of the '%S_MSG' in the '%S_MSG' statement must be %s. The %s data type is not allowed.
8403 16 No The message type '%.*ls' is specified more than once. Remove the duplicate message type.
8404 16 No The service contract '%.*ls' is specified more than once. Remove the duplicate service contract.
8405 16 No An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.
8406 16 No The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d.
8407 16 No Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.
8408 16 No Target service '%.*ls' does not support contract '%.*ls'.
8409 16 No This message could not be delivered because the targeted service does not support the service contract. Targeted service: '%.*ls', service contract: '%.*ls'.
8410 16 No The conversation timer cannot be set beyond the conversation's lifetime.
8411 16 No The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.
8412 16 No The syntax of the service name '%.*ls' is invalid.
8413 16 No The syntax of the broker instance '%.*ls' is invalid. The specified broker instance is too long, the maximum size is 256 bytes.
8414 16 No The conversation group ID '%.*ls' is invalid in this context. Specify a different conversion group ID.
8415 16 No The activated task was aborted because the invoked stored procedure '%ls' did not issue COMMIT or ROLLBACK on one or more transactions that it begun.
8417 16 No The service contract name is NULL. Specify a service contract name.
8418 16 No The conversation handle is missing. Specify a conversation handle.
8419 16 No Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL.
8420 16 No The conversation group is missing. Specify a conversation group.
8421 16 No The service name is missing. Specify a service name.
8422 16 No The error description is missing. Specify a description of the error.
8423 16 No The service "%.*ls" is not found.
8424 16 No The error code and error description are missing. Specify both the error code and description of the error.
8425 16 No The service contract '%.*ls' is not found.
8426 16 No The conversation handle "%.*ls" is not found.
8427 16 No The conversation endpoint is not in a valid state for END CONVERSATION. The current endpoint state is '%ls'.
8428 16 No The message type "%.*ls" is not found.
8429 16 No The conversation endpoint is not in a valid state for SEND. The current endpoint state is '%ls'.
8430 16 No The message body failed the configured validation.
8431 16 No The message type '%.*ls' is not part of the service contract.
8432 16 No The message cannot be sent because the message type '%.*ls' is marked SENT BY TARGET in the contract, however this service is an Initiator.
8433 16 No The message body may not be NULL. A zero-length UNICODE or binary string is allowed.
8434 16 No The message cannot be sent because the message type '%.*ls' is marked SENT BY INTITIATOR in the contract, however this service is a Target.
8436 16 No The conversation group "%.*ls" is not found.
8437 16 No The message received was sent by a Target service, but the message type '%.*ls' is marked SENT BY INITIATOR in the contract.
8438 16 No The conversation endpoint is not in a valid state for MOVE CONVERSATION. The current endpoint state is '%ls'.
8439 16 No The destination conversation group '%.*ls' is invalid.
8440 23 Yes The conversation group exists, but no queue exists. Possible database corruption. Run DBCC CHECKDB.
8442 16 No There is no Service Broker active in the database. Change to a database context that contains a Service Broker.
8443 23 Yes The conversation with ID '%.*ls' and initiator: %d references a missing conversation group '%.*ls'. Run DBCC CHECKDB to analyze and repair the database.
8444 23 Yes The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB.
8445 16 No The conversation handle '%ls' is referencing an invalid conversation ID '%ls', initiator: %d.
8447 16 No A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations.
8450 16 No Assignments in the RECEIVE projection are not allowed in conjunction with the INTO clause.
8457 16 No The message received was sent by the initiator of the conversation, but the message type '%.*ls' is marked SENT BY TARGET in the contract.
8458 16 No The conversation endpoint is not in a valid state for BEGIN CONVERSATION TIMER. The current endpoint state is '%ls'.
8459 16 No The message size, including header information, exceeds the maximum allowed of %d.
8460 16 No The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation handle '%ls'.
8461 23 Yes An internal service broker error detected. Possible database corruption. Run DBCC CHECKDB.
8462 16 No The remote conversation endpoint is either in a state where no more messages can be exchanged, or it has been dropped.
8463 16 No Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem. If the problem persists, the database may be damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database.
8468 16 No Underlying service has been altered.
8469 16 No Remote service has been altered.
8470 16 No Remote service has been dropped.
8471 16 No An SNI call failed during a Service Broker/Database Mirroring transport operation. SNI error '%ls'.
8472 16 No The remote service has sent a message that contains invalid header fields.
8475 16 No The conversation endpoint with ID '%ls' and is_initiator: %d has been dropped.
8477 16 No An internal Service Broker error occurred (error = 0x%08x). This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems. The database may have been damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database.
8479 16 No Used by test in failpoint simulation.
8487 16 No The remote service contract has been dropped.
8489 16 No The dialog has exceeded the specified LIFETIME.
8490 16 No Cannot find the remote service '%.*ls' because it does not exist.
8492 16 No The service contract '%.*ls' must have at least one message SENT BY INITIATOR or ANY.
8493 16 No The alter of service '%.*ls' must change the queue or at least one contract.
8494 16 No You do not have permission to access the service '%.*ls'.
8495 16 No The conversation has already been acknowledged by another instance of this service.
8498 16 No The remote service has sent a message of type '%.*ls' that is not part of the local contract.
8499 16 No The remote service has sent a message body of type '%.*ls' that does not match the message body encoding format. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
8501 16 No MSDTC on server '%.*ls' is unavailable.
8502 20 Yes Unknown token '0x%x' received from Microsoft Distributed Transaction Coordinator (MS DTC) .
8504 20 Yes The import buffer for this transaction is not valid.
8506 20 Yes Cannot change transaction state from %hs to %hs. The change requested is not valid.
8508 10 No QueryInterface failed for "%ls": %ls.
8509 20 Yes Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls.
8510 20 Yes Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.
8511 16 Yes Unknown isolation level 0x%x requested from Microsoft Distributed Transaction Coordinator (MS DTC).
8512 20 Yes Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs.
8513 20 Yes Microsoft Distributed Transaction Coordinator (MS DTC) end transaction acknowledgement failed: %hs.
8514 20 Yes Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs.
8515 20 Yes Microsoft Distributed Transaction Coordinator (MS DTC) global state is not valid.
8517 20 Yes Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls.
8518 16 Yes Microsoft Distributed Transaction Coordinator (MS DTC) BEGIN TRANSACTION failed: %ls.
8519 16 No Current Microsoft Distributed Transaction Coordinator (MS DTC) transaction must be committed by remote client.
8520 16 Yes Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: %ls.
8521 20 Yes This awakening state is not valid: slept in %hs; awoke in %hs.
8522 20 Yes Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
8523 15 No PREPARE TRAN statement not allowed on MSDTC transaction.
8524 16 No The current transaction could not be exported to the remote provider. It has been rolled back.
8525 16 No Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
8526 16 No Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint.
8527 16 Yes An attempt to create a distributed transaction export token failed with this error: %ls. Contact your Microsoft Distributed Transaction Coordinator (MS DTC) system administrator.
8528 16 No The commit of the Kernel Transaction Manager (KTM) transaction failed: %d.
8529 16 No Unable to extract the Kernel Transaction Manager (KTM) transaction handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transaction: 0x%x.
8530 16 Yes The Windows kernel transaction manager creation failed: 0x%x.
8531 16 Yes The Windows kernel transaction manager failed to create the enlistment: 0x%08x.
8532 20 No Error while reading resource manager notification from Kernel Transaction Manager (KTM): %d.
8533 20 No Error while waiting for communication from Kernel Transaction Manager (KTM): %d.
8534 21 No The KTM RM for this database, %ls, failed to start: %d.
8535 16 Yes A savepoint operation in the Windows transactional file system failed: 0x%x.
8536 16 Yes Only single DB updates are allowed with FILESTREAM operations.
8537 16 No This transaction was aborted by Kernel Transaction Manager (KTM).
8538 16 No The current isolation level is not supported by the FILESTREAM 0x%x.
8539 10 Yes The distributed transaction with UOW %ls was forced to commit. MS DTC became temporarily unavailable and forced heuristic resolution of the transaction. This is an informational message only. No user action is required.
8540 10 Yes The distributed transaction with UOW %ls was forced to rollback.
8541 10 Yes System process ID %d tried to terminate the distributed transaction with Unit of Work ID %ls. This message occurs when the client executes a KILL statement on the distributed transaction.
8542 10 Yes Spid %d tried to commit the distributed transaction with UOW %ls.
8543 10 Yes Unable to commit a prepared transaction from the Microsoft Distributed Transaction Coordinator (MS DTC). Shutting down server to initiate resource manager (RM) recovery. When the RM recovers, it will query the transaction manager about the outcome of the in-doubt transaction, and commit or roll back accordingly.
8544 10 Yes Unknown status of commit of a two-phase commit transaction. Shutting down server. Restart server to complete recovery.
8545 10 Yes Unknown status '%d' from Reenlist call in rm_resolve.
8546 10 Yes Unable to load Microsoft Distributed Transaction Coordinator (MS DTC) library. This error indicates that MS DTC is not installed. Install MS DTC to proceed.
8547 10 Yes Resource Manager Creation Failed: %ls
8548 10 Yes DTC not initialized because it's unavailable
8549 10 Yes GetWhereaboutsSize call failed: %ls
8550 10 Yes MS DTC initialization failed because the transaction manager address is invalid. The protocol element used to carry address information may be too large. A network protocol analyzer may provide additional information about the cause. Contact your application support provider or Microsoft Product Support Services.
8551 16 No CoCreateGuid failed: %ls.
8552 20 No RegOpenKeyEx of "%ls" failed: %ls.
8553 20 No RegQueryValueEx of "%hs" failed: %ls.
8554 20 No IIDFromString failed for %hs, (%ls).
8555 10 Yes RegCloseKey failed: %ls
8556 10 Yes Microsoft Distributed Transaction Coordinator (MS DTC) initialization failed due to insufficient memory. It may be necessary to change some server configuration options to make more memory available.
8557 10 No The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
8558 20 Yes RegDeleteValue of "%hs" failed: %ls.
8560 10 Yes Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
8561 10 Yes Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
8562 10 Yes The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.
8563 10 Yes An error occurred while trying to determine the state of the RPCSS service. A call to "%ls" returned: %ls. This is an informational message only. No user action is required.
8565 16 Yes SQL Server failed to prepare DTC transaction. Failure code: %d.
8601 17 No Internal Query Processor Error: The query processor could not obtain access to a required interface.
8602 16 No Indexes used in hints must be explicitly included by the index tuning wizard.
8603 16 No Invalid syntax for internal DBCC REPAIR statement.
8604 16 No ALTER TABLE SWITCH statement failed. Table '%.*ls' has a column level check constraint '%.*ls' on column '%.*ls' that is not loadable for semantic validation.
8605 10 No Index creation operation will use %ld KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of %lu KB specified in "index create memory (KB)" option because the former has to be smaller than the latter.
8606 17 No This index operation requires %I64d KB of memory per DOP. The total requirement of %I64d KB for DOP of %lu is greater than the sp_configure value of %lu KB set for the advanced server configuration option "index create memory (KB)". Increase this setting or reduce DOP and rerun the query.
8607 16 No The table '%.*ls' cannot be modified because one or more nonclustered indexes reside in a filegroup which is not online.
8608 16 No The query could not be completed due to an online index build operation and must be recompiled.
8616 10 No The index hints for table '%.*ls' were ignored because the table was considered a fact table in the star join.
8618 16 No The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. If the query has a GROUP BY or ORDER BY clause, consider reducing the number and/or size of the fields in the clause. Consider using prefix (LEFT()) or hash (CHECKSUM()) of fields for grouping or prefix for ordering. Note however that this will change the behavior of the query.
8619 16 No The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. Resubmit your query without the ROBUST PLAN hint.
8621 16 No The query processor ran out of stack space during query optimization. Please simplify the query.
8622 16 No Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
8623 16 Yes The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
8624 16 Yes Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
8625 10 No Warning: The join order has been enforced because a local join hint is used.
8628 17 Yes A time out occurred while waiting to optimize the query. Rerun the query.
8630 17 No Internal Query Processor Error: The query processor encountered an unexpected error during execution.
8631 17 No Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it.
8632 17 No Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
8633 16 No The query processor could not produce a query plan because distributed query does not support materializing intermediate results with default in DML queries over remote sources. Try to use actual default values instead of default or split the update into multiple statements, one only containing the DEFAULT assignment, the other with the rest.
8634 17 No The query processor received an error from a cluster communication layer.
8635 16 No The query processor could not produce a query plan for a query with a spatial index hint. Reason: %S_MSG. Try removing the index hints or removing SET FORCEPLAN.
8636 16 No The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This is not supported for distributed queries.
8637 16 No The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while the target table of the modification has an index that is currently being built online. Consider waiting until the online index build is done before forcing the plan, or using another way to tune the query, such as updating statistics, or using a different hint or a manual query rewrite.
8642 17 No The query processor could not start the necessary thread resources for parallel query execution.
8644 16 No Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine.
8645 17 Yes A timeout occurred while waiting for memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query.
8646 21 Yes Unable to find index entry in index ID %d, of table %d, in database '%.*ls'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.
8648 20 Yes Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint.
8649 17 No The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator.
8651 17 No Could not perform the operation because the requested memory grant was not available in resource pool '%ls' (%ld). Rerun the query, reduce the query load, or check resource governor configuration setting.
8653 16 No The query processor is unable to produce a plan for the table or view '%.*ls' because the table resides in a filegroup which is not online.
8655 16 No The query processor is unable to produce a plan because the index '%.*ls' on table or view '%.*ls' is disabled.
8656 16 No The query processor could not produce a query plan. Resubmit the query after disabling trace flag %d.
8657 17 No Could not get the memory grant of %I64d KB because it exceeds the maximum configuration limit in workload group '%ls' (%ld) and resource pool '%ls' (%ld). Contact the server administrator to increase the memory usage limit.
8660 16 No Cannot create the clustered index "%.*ls" on view "%.*ls" because the select list of the view definition does not include all columns in the GROUP BY clause. Consider adding these columns to the select list.
8661 16 No Cannot create the clustered index "%.*ls" on view "%.*ls" because the index key includes columns that are not in the GROUP BY clause. Consider eliminating columns that are not in the GROUP BY clause from the index key.
8662 16 No Cannot create the clustered index "%.*ls" on view "%.*ls" because the view references an unknown value (SUM aggregate of nullable expression). Consider referencing only non-nullable values in SUM. ISNULL() may be useful for this.
8663 16 No Cannot create the clustered index "%.ls" on view "%.ls" because its select list does not include COUNT_BIG(). Consider adding COUNT_BIG() to the select list.
8665 16 No Cannot create the clustered index "%.*ls" on view "%.*ls" because no row can satisfy the view definition. Consider eliminating contradictions from the view definition.
8668 16 No Cannot create the clustered index '%.*ls' on view '%.*ls' because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from select list.
8669 16 No The attempt to maintain the indexed view "%.*ls" failed because it contains an expression on aggregate results, or because it contains a ranking or aggregate window function. Consider dropping the clustered index on the view, or changing the view definition.
8670 16 No Query optimizer reached the internal limit of the maximum number of views that can be used during optimization.
8671 16 No The attempt to maintain the indexed view "%.*ls" failed because of the ignore_dup_key option on index "%.*ls". Drop the index or re-create it without the ignore_dup_key index option.
8672 16 No The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows.
8673 16 No A MERGE statement is not valid if it triggers both the 'ON DELETE SET NULL' and 'ON UPDATE CASCADE' actions for a referential integrity constraint. Modify the actions performed by the MERGE statement to ensure that it does not trigger both these actions for a referential integrity constraint.
8680 17 No Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.
8682 16 No SELECT via cursor failed because in XML plan provided to USE PLAN hint, neither Populate nor Fetch plans are provided, and at least one must be present. For best likelihood of successful plan forcing, use an XML cursor plan captured from SQL Server without modification.
8683 16 No Could not force query plan because XML showplan provided in USE PLAN hint contains invalid Star Join specification. Consider specifying a USE PLAN hint that contains an unmodified XML showplan produced by SQL Server. This may allow you to force the plan.
8684 16 No A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified in USE PLAN hint. First consider removing USE PLAN hint. Then if necessary consider (1) updating statistics, (2) using other hints such as join hints, index hints, or the OPTIMIZE FOR hint, (3) rewriting query or breaking it down into two or more separate queries.
8685 16 No Query cannot be compiled because <CursorStmt> element appears in XML plan provided to USE PLAN but USE PLAN was applied to a non-cursor statement. Consider using an XML plan obtained from SQL Server for statement without modification.
8686 16 No Cursor plan forcing failed because input plan has more than one <Operation> node with OperationType=%ls. Consider using an XML cursor plan captured from SQL Server without modification.
8687 16 No Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with a USE PLAN hint. Consider removing USE PLAN hint and updating statistics or using different hints to influence query plan choice.
8688 16 No Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %ls is missing under <CursorPlan> element. Consider using an XML cursor plan captured from SQL Server without modification.
8689 16 No Database '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing database.
8690 16 No Query cannot be compiled because USE PLAN hint conflicts with hint %ls. Consider removing hint %ls.
8691 16 No Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF.
8693 16 No Cannot compile query because combination of LogicalOp = '%ls', PhysicalOp = '%ls', and sub_element = '%ls' under RelOp element in XML plan in USE PLAN hint is not valid. Use a recognized combination instead. Consider using an automatically generated XML plan without modification.
8694 16 No Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint.
8695 16 No Cannot execute query because of incorrectly formed XML plan in USE PLAN hint. Verify that XML plan is a legal plan suitable for plan forcing. See Books Online for additional details.
8696 16 No Cannot run query because of improperly formed Spool element with parent RelOp with NodeId %d in XML plan in USE PLAN hint. Verify that each Spool element's parent RelOp has unique NodeId attribute, and each Spool element has either a single RelOp sub-element, or a PrimaryNodeId attribute, but not both. PrimaryNodeId of Spool must reference NodeId of an existing RelOp with a Spool sub-element. Consider using unmodified XML showplan as USE PLAN hint.
8697 16 No Cannot run query because in XML plan provided to USE PLAN, element %ls must have %d %ls nodes as children, but has %d.
8698 16 No Query processor could not produce query plan because USE PLAN hint contains plan that could not be verified to be legal for query. Remove or replace USE PLAN hint. For best likelihood of successful plan forcing, verify that the plan provided in the USE PLAN hint is one generated automatically by SQL Server for the same query.
8699 16 No Cannot run query because it contains more than one USE PLAN hint. Use at most one USE PLAN hint.
8710 16 No Aggregate functions that are used with CUBE, ROLLUP, or GROUPING SET queries must provide for the merging of subaggregates. To fix this problem, remove the aggregate function or write the query using UNION ALL over GROUP BY clauses.
8711 16 No Multiple ordered aggregate functions in the same scope have mutually incompatible orderings.
8712 16 No Index '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified name.
8720 15 No Cannot execute query. There is more than one TABLE HINT clause specified for object '%.*ls'. Use at most one such TABLE HINT clause per table reference.
8721 15 No Cannot execute query. TABLE HINT in the OPTION clause leads to ambiguous reference for object '%.*ls'. Consider USE PLAN query hint instead.
8722 15 No Cannot execute query. Semantic affecting hint '%.*ls' appears in the '%.*ls' clause of object '%.*ls' but not in the corresponding '%.*ls' clause. Change the OPTION (TABLE HINTS...) clause so the semantic affecting hints match the WITH clause.
8723 15 No Cannot execute query. Object '%.*ls' is specified in the TABLE HINT clause, but is not used in the query or does not match the alias specified in the query. Table references in the TABLE HINT clause must match the WITH clause.
8724 15 No Cannot execute query. Table-valued or OPENROWSET function '%.*ls' cannot be specified in the TABLE HINT clause.
8901 16 No Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object.
8902 17 No Memory allocation error during DBCC processing.
8903 16 No Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID.
8904 16 No Extent %S_PGID in database ID %d is allocated by more than one allocation object.
8905 16 No Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it.
8906 16 No Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags '%hs'.
8907 16 No The spatial index, XML index or indexed view '%.*ls' (object ID %d) contains rows that were not produced by the view definition. This does not necessarily represent an integrity issue with the data in this database. For more information about troubleshooting DBCC errors on indexed views, see SQL Server Books Online.
8908 16 No The spatial index, XML index or indexed view '%.*ls' (object ID %d) does not contain all rows that the view definition produces. This does not necessarily represent an integrity issue with the data in this database. For more information about troubleshooting DBCC errors on spatial indexes, XML indexes, and indexed views, see SQL Server Books Online.
8909 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID.
8910 16 No Page %S_PGID in database ID %d is allocated to both object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), and object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
8911 10 No The error has been repaired.
8912 10 No %.*ls fixed %d allocation errors and %d consistency errors in database '%ls'.
8913 16 No Extent %S_PGID is allocated to '%ls' and at least one other object.
8914 10 No Incorrect PFS free space information for page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Expected value %hs, actual value %hs.
8915 10 No File %d (number of mixed extents = %I64d, mixed pages = %I64d).
8916 10 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), data extents %I64d, pages %I64d, mixed extent pages %I64d.
8917 10 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d.
8918 10 No (number of mixed extents = %I64d, mixed pages = %I64d) in this database.
8919 16 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The record count in the header (%d) does not match the number of records (%d) found on page %S_PGID.
8920 16 No Cannot perform a %ls operation inside a user transaction. Terminate the transaction and reissue the statement.
8921 16 No Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
8922 10 No Could not repair this error.
8923 10 No The repair level on the DBCC statement caused this repair to be bypassed.
8924 10 No Repairing this error requires other errors to be corrected first.
8925 16 No Table error: Cross object linkage: Page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), refers to page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
8926 16 No Table error: Cross object linkage: Parent page %S_PGID, slot %d in object %d, index %d, partition %I64d, AU %I64d (%.*ls), and page %S_PGID->next in object %d, index %d, partition %I64d, AU %I64d (%.*ls), refer to page %S_PGID but are not in the same object.
8927 16 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The ghosted record count in the header (%d) does not match the number of ghosted records (%d) found on page %S_PGID.
8928 16 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Page %S_PGID could not be processed. See other errors for details.
8929 16 No Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Errors found in off-row data with ID %I64d owned by %ls record identified by %.*ls
8930 16 No Database error: Database %d has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. Please restore from a backup.
8931 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 parent %S_PGID.
8932 16 No Could not find filegroup ID %d in sys.filegroups for database '%ls'.
8933 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The low key value on page %S_PGID (level %d) is not >= the key value in the parent %S_PGID slot %d.
8934 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The high key value on page %S_PGID (level %d) is not less than the low key value in the parent %S_PGID, slot %d of the next page %S_PGID.
8935 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.
8936 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID.
8937 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.
8938 16 No Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
8939 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Values are %ld and %ld.
8940 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned.
8941 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid.
8942 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row.
8943 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.
8944 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld.
8945 16 No Table error: Object ID %d, index ID %d will be rebuilt.
8946 16 No Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page.
8947 16 No Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.
8948 16 No Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
8949 10 No %.*ls fixed %d allocation errors and %d consistency errors in table '%ls' (object ID %d).
8950 16 No %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
8951 16 No Table error: table '%ls' (ID %d). Data row does not have a matching index row in the index '%ls' (ID %d). Possible missing or invalid keys for the index row matching:
8952 16 No Table error: table '%ls' (ID %d). Index row in index '%ls' (ID %d) does not match any data row. Possible extra or invalid keys for:
8953 10 No Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
8954 10 No %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
8955 16 No Data row (%d:%d:%d) identified by (%ls) with index values '%ls'.
8956 16 No Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
8957 10 Yes %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls
8958 10 No %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
8959 16 No Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.
8960 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column.
8961 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.
8962 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d.
8963 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.
8964 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced.
8965 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.
8966 22 Yes Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
8967 16 No An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
8968 16 No Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database.
8969 16 No Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.
8970 16 No Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column '%.*ls' was created NOT NULL, but is NULL in the row.
8971 16 No Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d
8972 16 No Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d.
8973 16 No CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.
8974 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d.
8975 10 No DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.
8976 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
8977 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.
8978 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
8979 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
8980 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
8981 16 No Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.
8982 16 No Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index.
8983 10 No File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
8984 16 No Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
8985 16 No Could not locate file '%.*ls' for database '%.*ls' in sys.database_files. The file either does not exist, or was dropped.
8986 16 No Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
8987 16 No No help available for DBCC statement '%.*ls'.
8988 16 No Row (%d:%d:%d) identified by (%ls).
8989 10 No %.*ls found %d allocation errors and %d consistency errors in database '%ls'.
8990 10 No %.*ls found %d allocation errors and %d consistency errors in table '%ls' (object ID %d).
8991 16 No 0x%p to 0x%p is not a valid address range.
8992 16 No Check Catalog Msg %d, State %d: %.*ls
8993 16 No Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
8994 16 No Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.
8995 16 No System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d.
8996 16 No IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) controls pages in filegroup %d, that should be in filegroup %d.
8997 16 No Service Broker Msg %d, State %d: %.*ls
8998 16 No Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID %d pages from %S_PGID to %S_PGID. See other errors for cause.
8999 10 No Database tempdb allocation errors prevent further %ls processing.

Errors 9,000 to 9,999

ErrorSeverityEvent LoggedDescription
9001 10 Yes The log for database '%.*ls' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
9002 17 Yes The transaction log for database '%.*ls' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
9003 20 Yes The log scan number %S_LSN passed to log scan in database '%.*ls' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
9004 21 Yes An error occurred while processing the log for database '%.*ls'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
9005 16 No Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid.
9006 10 No Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d.
9007 10 No Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file.
9008 10 No Cannot shrink log file %d (%s) because the logical log file located at the end of the file is in use.
9009 10 No Cannot shrink log file %d (%s) because of minimum log space required.
9010 14 No User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission
9011 14 No User does not have permission to query backup files with the virtual table DBLog. Only members of the sysadmin fixed server role has this permission
9012 10 No There have been %d misaligned log IOs which required falling back to synchronous IO. The current IO is on file %ls.
9013 10 No The tail of the log for database %ls is being rewritten to match the new sector size of %d bytes. %d bytes at offset %I64d in file %ls will be written.
9014 21 Yes An error occurred while processing the log for database '%.*ls'. THe log block version is higher than this server allows.
9015 24 Yes The log record at LSN %S_LSN is corrupted.
9016 21 Yes An error occurred while processing the log for database '%.*ls'. The log block could not be decrypted.
9017 10 No Database %ls has more than %d virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
9100 23 Yes Possible index corruption detected. Run DBCC CHECKDB.
9101 16 No auto statistics internal
9104 16 No auto statistics internal
9105 16 No The provided statistics stream is corrupt.
9106 16 No Histogram support not allowed for input data type 0x%08x.
9201 10 Yes %d active query notification subscription(s) in database '%.*ls' owned by security identification number '%.*ls' were dropped.
9202 16 No The query notification subscription message is invalid.
9204 16 No The query notification subscription timeout is invalid. The allowed range is 1 through 2147483647.
9205 16 No User "%.*ls" does not have permission to request query notification subscriptions on database "%.*ls".
9206 16 No The query notification subscription "%ld" cannot be deleted because it does not exist or it has already been fired.
9207 10 No The query notification dialog on conversation handle '%.*ls' closed due to the following error: '%.*ls'.
9208 16 No Query notification subscription could not get dialog endpoint. Could not open service broker dialog for service name '%.*ls' of broker instance '%.*ls'.
9209 16 No Query notification subscription could not begin dialog with service name '%.*ls' of broker instance '%.*ls'.
9210 10 No Query notification delivery could not send message on dialog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker: '%.*ls'.
9211 10 No Failed to check for pending query notifications in database "%d" because of the following error when opening the database: '%.*ls'.
9213 10 No Query notification subscription could not access database with id %d. Could not open broker dialog for service name '%.*ls' of broker instance '%.*ls'.
9214 16 No The query notification delivery failed to decode the error message from the Service Broker.
9215 16 No Query notification delivery failed to encode message. Delivery failed for notification '%.*ls'.
9216 10 No Failed to delete the expired query notification subscription "%d".
9217 10 No Failed to drop the unused internal query notification table "%d" in database "%d".
9218 16 No Query notifications reached the internal limit of the maximum number of objects.
9219 16 No The query notification subscriptions cleanup operation failed. See previous errors for details.
9220 10 No Query notification dialog on conversation handle '%.*ls' closed due to an unknown service broker error.
9221 10 No Query notification delivery could not get dialog endpoint for dialog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker '%.*ls'.
9222 16 No Internal query notification table has an outdated schema and the table has been dropped. Query notification cleanup has not been performed for this table.
9223 10 Yes %d active query notification subscription(s) owned by security identification number '%.*ls' were dropped.
9224 10 No Query notification delivery could not access database with id %d. Delivery failed for notification '%.*ls'.
9225 16 No The notification options identifier string has %d characters. The maximum allowed length is %d characters.
9226 16 No A string value within the notification options identifier is too long. String with prefix '%.*ls' must be %d characters or less.
9227 16 No Unmatched quote in notification options identifier string.
9228 16 No Name expected in notification options identifier option.
9229 16 No Unknown option name '%.*ls' present in notification options identifier. The following are valid option names: 'Service', 'Broker Instance', 'Local Database'. Option names cannot be quoted.
9230 16 No Option '%ls' was specified multiple times in the notification options identifier.
9231 16 No An equal (=) character was expected after the option name. Found '%.*ls' instead.
9232 16 No A semicolon (;) must be use to separate options in a notification options identifier. String '%.*ls' was found following an option.
9233 16 No The option 'Service' must be specified in the notification options identifier.
9234 16 No The options 'Broker Instance' and 'Local Database' were both specified in the notification options identifier.
9235 16 No Value missing for option '%ls' in notification options identifier.
9236 16 No Database %.*ls is not a valid local database.
9237 16 No Database %.*ls is not a valid broker database.
9238 16 No Query notification subscriptions are not allowed under an active application role context. Consider re-issuing the request without activating the application role.
9239 16 No Internal query notifications error: The garbage collector corrected an inconsistency.
9240 10 No Service broker dialog '%.*ls' could not be closed due to a broker error in database with id '%d' because of the following error in service broker: '%.*ls'.
9241 16 No Service broker dialog '%.*ls' could not be closed because the database with id '%d' is not available. Consider closing the dialogs manually once the database is available again.
9242 10 No Query notification delivery could not get dialog endpoint for dialog '%.*ls'. Query notification delivery failed because of the following error in service broker: '%.*ls'. See the error log for additional information.
9243 10 No Query notification delivery could not send message on dialog '%.*ls'. Query notification delivery failed because of the following error in service broker: '%.*ls'. See the error log for additional information.
9244 16 No Query notification cleanup could not access metadata for database "%d". Check whether the database is successfully restored and online.
9300 16 No %sIn this version of the server, the 'fn:id()' function only accepts an argument of type 'IDREF *'.
9301 16 No %sIn this version of the server, 'cast as <type>%s' is not available. Please use the 'cast as <type> ?' syntax.
9302 16 No %sThe context item in which the 'fn:id()' function is used must be a node.
9303 16 No %sSyntax error near '%ls', expected '%ls'.
9304 16 No %sThis version of the server only supports XQuery version '1.0'.
9305 16 No %sOnly type names followed by '?' are supported in the target of 'instance of'.
9306 16 No %sThe target of 'replace value of' cannot be a union type, found '%ls'.
9308 16 No %sThe argument of '%ls' must be of a single numeric primitive type or 'http://www.w3.org/2004/07/xpath-datatypes#untypedAtomic'. Found argument of type '%ls'.
9309 16 No %sThe target of 'replace value of' cannot be 'http://www.w3.org/2001/XMLSchema#anySimpleType', found '%ls'.
9310 16 No %sThe 'with' clause of 'replace value of' cannot contain constructed XML.
9311 16 No %sHeterogeneous sequences are not allowed in '%ls', found '%ls' and '%ls'.
9312 16 No %s'%ls' is not supported on simple typed or 'http://www.w3.org/2001/XMLSchema#anyType' elements, found '%ls'.
9313 16 No %sThis version of the server does not support multiple expressions or expressions mixed with strings in an attribute constructor.
9314 16 No %sCannot implicitly atomize or apply 'fn:data()' to complex content elements, found type '%ls' within inferred type '%ls'.
9315 16 No %sOnly constant expressions are supported for the name expression of computed element and attribute constructors.
9316 16 No %sCannot use 'xmlns' in the name expression of computed attribute constructor.
9317 16 No %sSyntax error near '%ls', expected string literal.
9318 16 No %sSyntax error at source character '0x%02x' near '%ls', expected string literal.
9319 16 No %sStatic simple type validation: Invalid simple type value '%ls'.
9320 16 No %sThe result of applying the 'parent' axis on the document node is statically 'empty'.
9321 16 No %sThe result of applying 'parent::%ls' is statically 'empty'.
9322 16 No %sTwo consecutive '-' can only appear in a comment constructor if they are used to close the comment ('-->').
9323 16 No %sUsing ':' in variable names is not supported in this version of the server.
9324 16 No %sFound '}' without matching '{'. If you want to use the characters '{' or '}', you need to escape them as '{{' or '}}' respectively.
9325 16 No %sComputed processing instruction constructors are not supported.
9326 16 No %sComputed comment constructors are not supported.
9327 16 No %sAll prolog entries need to end with ';', found '%ls'.
9328 16 No %sType specification expected, found '%ls'.
9330 16 No %sOnly comparable types are allowed in '%ls', found '%ls'.
9331 16 No %sSyntax error near '%ls', expected '%ls' or '%ls'.
9332 16 No %sSyntax error near '%ls', expected 'where', '(stable) order by' or 'return'.
9333 16 No %s'//' followed by 'self', 'parent' or 'descendant-or-self' axes is not supported when it encounters simple typed or 'http://www.w3.org/2001/XMLSchema#anyType' elements, found '%ls'.
9334 16 No %sThe 'form' attribute cannot be specified on a local attribute or element definition that has the 'ref' attribute. Location: '%ls'.
9335 16 No %sThe XQuery syntax '%ls' is not supported.
9336 16 No %sThe XML Schema syntax '%ls' is not supported.
9337 16 No %sThe XML Schema type 'NOTATION' is not supported.
9338 16 No %sThe value of a namespace declaration attribute must be a string literal. It cannot contain expressions.
9339 16 No %sThe 'form' attribute cannot be specified on a global attribute or element definition. Location: '%ls'.
9340 16 No %sExplicit import of the current target namespace is invalid. References to items in the current target namespace that have already been loaded in the schema collection will be resolved implicitly.
9341 16 No %sSyntax error near '%ls', expected a step expression.
9342 16 No %sAn XML instance is only supported as the direct source of an insert using sql:column/sql:variable.
9343 16 No %sThe XML instance referred to by sql:column() and sql:variable() must be either untyped XML or must be typed with the same XML schema collection as the context XML instance on which the XML method is being applied to.
9344 16 No %sThe SQL type '%s' is not supported with sql:column() and sql:variable().
9400 16 No XML parsing: line %d, character %d, unexpected end of input
9401 16 No XML parsing: line %d, character %d, unrecognized encoding
9402 16 No XML parsing: line %d, character %d, unable to switch the encoding
9403 16 No XML parsing: line %d, character %d, unrecognized input signature
9410 16 No XML parsing: line %d, character %d, whitespace expected
9411 16 No XML parsing: line %d, character %d, semicolon expected
9412 16 No XML parsing: line %d, character %d, '>' expected
9413 16 No XML parsing: line %d, character %d, A string literal was expected
9414 16 No XML parsing: line %d, character %d, equal expected
9415 16 No XML parsing: line %d, character %d, well formed check: no '<' in attribute value
9416 16 No XML parsing: line %d, character %d, hexadecimal digit expected
9417 16 No XML parsing: line %d, character %d, decimal digit expected
9418 16 No XML parsing: line %d, character %d, '[' expected
9419 16 No XML parsing: line %d, character %d, '(' expected
9420 16 No XML parsing: line %d, character %d, illegal xml character
9421 16 No XML parsing: line %d, character %d, illegal name character
9422 16 No XML parsing: line %d, character %d, incorrect document syntax
9423 16 No XML parsing: line %d, character %d, incorrect CDATA section syntax
9424 16 No XML parsing: line %d, character %d, incorrect comment syntax
9425 16 No XML parsing: line %d, character %d, incorrect conditional section syntax
9426 16 No XML parsing: line %d, character %d, incorrect ATTLIST declaration syntax
9427 16 No XML parsing: line %d, character %d, incorrect DOCTYPE declaration syntax
9428 16 No XML parsing: line %d, character %d, incorrect ELEMENT declaration syntax
9429 16 No XML parsing: line %d, character %d, incorrect ENTITY declaration syntax
9430 16 No XML parsing: line %d, character %d, incorrect NOTATION declaration syntax
9431 16 No XML parsing: line %d, character %d, NDATA expected
9432 16 No XML parsing: line %d, character %d, PUBLIC expected
9433 16 No XML parsing: line %d, character %d, SYSTEM expected
9434 16 No XML parsing: line %d, character %d, name expected
9435 16 No XML parsing: line %d, character %d, one root element
9436 16 No XML parsing: line %d, character %d, end tag does not match start tag
9437 16 No XML parsing: line %d, character %d, duplicate attribute
9438 16 No XML parsing: line %d, character %d, text/xmldecl not at the beginning of input
9439 16 No XML parsing: line %d, character %d, namespaces beginning with "xml" are reserved
9440 16 No XML parsing: line %d, character %d, incorrect text declaration syntax
9441 16 No XML parsing: line %d, character %d, incorrect xml declaration syntax
9442 16 No XML parsing: line %d, character %d, incorrect encoding name syntax
9443 16 No XML parsing: line %d, character %d, incorrect public identifier syntax
9444 16 No XML parsing: line %d, character %d, well formed check: pes in internal subset
9445 16 No XML parsing: line %d, character %d, well formed check: pes between declarations
9446 16 No XML parsing: line %d, character %d, well formed check: no recursion
9447 16 No XML parsing: line %d, character %d, entity content not well formed
9448 16 No XML parsing: line %d, character %d, well formed check: undeclared entity
9449 16 No XML parsing: line %d, character %d, well formed check: parsed entity
9450 16 No XML parsing: line %d, character %d, well formed check: no external entity references
9451 16 No XML parsing: line %d, character %d, incorrect processing instruction syntax
9452 16 No XML parsing: line %d, character %d, incorrect system identifier syntax
9453 16 No XML parsing: line %d, character %d, '?' expected
9454 16 No XML parsing: line %d, character %d, no ']]>' in element content
9455 16 No XML parsing: line %d, character %d, illegal qualified name character
9456 16 No XML parsing: line %d, character %d, multiple colons in qualified name
9457 16 No XML parsing: line %d, character %d, colon in name
9458 16 No XML parsing: line %d, character %d, redeclared prefix
9459 16 No XML parsing: line %d, character %d, undeclared prefix
9460 16 No XML parsing: line %d, character %d, non default namespace with empty uri
9461 16 No XML %ls starting with '%.*ls' is %d characters long, which exceeds the limit. Maximum allowed length is %d characters.
9462 16 No XML parsing: line %d, character %d, not all chunks of value have been read
9463 16 No XML parsing: line %d, character %d, xml:space has a non-legal value
9464 16 No XML parsing: line %d, character %d, 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.
9465 16 No XML parsing: line %d, character %d, XML namespace prefix 'xmlns' is reserved for use by XML.
9466 16 No XML parsing: line %d, character %d, XML namespace xml namespace URI (https://www.w3.org/XML/1998/namespace) must be assigned only to prefix 'xml'.
9467 16 No XML parsing: line %d, character %d, xmlns namespace URI (https://www.w3.org/2000/xmlns/) is reserved and must not be used.
9480 16 No XML parsing: line %d, character %d, unsupported xml
9500 16 No The data type '%.*ls' used in the VALUE method is invalid.
9501 16 No XQuery: Unable to resolve sql:variable('%.*ls'). The variable must be declared as a scalar TSQL variable.
9502 16 No The string literal provided for the argument %d of the '%.*ls' method must not exceed %d bytes.
9503 16 No Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls'. See previous error messages for more details.
9504 16 No Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls', invoked on column '%.*ls', table '%.*ls'. See previous error messages for more details.
9506 16 No The XMLDT method '%.*ls' can only be invoked on columns of type xml.
9507 16 No The XML data type method on a remote column used in this query can not be executed either locally or remotely. Please rewrite your query.
9508 16 No The reference parameter given to XMLDT method '%.*ls' was generated from a different XML instance than the one it is being applied to.
9509 16 No XMLUNNEST method requires typed xml column with single global element
9510 16 No Functionality not yet implemented: XMLNODEREFS cannot use references exposed by views.
9512 16 No Xml data type is not supported as a parameter to remote calls.
9513 16 No Error processing XML data type method '%.*ls'. The following SET options required by XML data type methods are not set: '%.*ls'.
9514 16 No Xml data type is not supported in distributed queries. Remote object '%.*ls' has xml column(s).
9515 16 No An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch.
9516 16 No XQuery: The name or one of the parts of a multi-part name supplied to %S_MSG('%.*ls') is empty. Empty names cannot be used to identify objects, columns or variables in SQL.
9517 16 No XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it is too long. Maximum length is %d, actual length is %d.
9518 16 No XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it contains invalid characters.
9519 16 No XQuery: The name supplied to sql:variable('%.*ls') is not a valid SQL variable name. Variable names must start with the '@' symbol followed by at least one character.
9520 16 No XQuery: '%.*ls' referenced by sql:variable() is not a valid system function name.
9521 16 No Error processing XML data type. The XML data type instance contains a negative xs:date or xs:dateTime value.
9522 16 No The XQuery modify method is not allowed on sparse column sets.
9523 16 No Cannot update the sparse column set '%.*ls' because the XML content supplied references the non-sparse column '%.*ls' which does not belong to this column set. The XML data used to update a sparse column set cannot reference columns that don't belong to the column set.
9524 16 No The XML content provided does not conform to the required XML format for sparse column sets.
9525 16 No The XML content that is supplied for the sparse column set '%.*ls' contains duplicate references to the column '%.*ls'. A column can only be referenced once in XML content supplied to a sparse column set.
9526 16 No In the XML content that is supplied for the sparse column set '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is out of range. The valid range is from 1 to %d.
9527 16 No In the XML content that is supplied for the column set '%.*ls', the sqltypes:scale attribute value on the element '%.*ls' is out of range. The valid range for the scale is from 0 to the specified precision.
9528 16 No In the XML content that is supplied for the column set '%.*ls', the '%.*ls' attribute on the element '%.*ls' is not valid. The attribute is valid only for sparse columns of data type sql_variant.
9529 16 No In the XML content that is supplied for the column set column '%.*ls', the sqlDBType:base64Encoded attribute on the element '%.*ls' is not valid. The base64Encoded attribute can only be used when the corresponding sparse column is of character data type (char, varchar, nchar, nvarchar), or if the sparse column is of data type sql_variant and the value of the xsi:type attribute is "Char", "VarChar", "NChar", or "NVarChar".
9530 16 No In the XML content that is supplied for the column set column '%.*ls, the '%.*ls' attribute on the element '%.*ls' is not valid. Remove the attribute.
9531 16 No In the XML content that is supplied for the column set column '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is not valid.
9532 16 No In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the column '%.*ls'.
9533 16 No In the XML that is supplied for the column set '%.*ls', the element '%.*ls' should reside in the global namespace. Remove the default namespace declaration or the prefix on the element.
9534 16 No In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the column '%.*ls'. Please refer to the Books-on-line for more details on providing XML conversion methods for CLR types.
9601 16 No Cannot relate to %S_MSG %.*ls because it is %S_MSG.
9605 10 No Conversation Priorities analyzed: %d.
9606 16 No The conversation priority with ID %d has been dropped.
9607 16 No The conversation priority with ID %d is referencing the missing service with ID %d.
9608 16 No The conversation priority with ID %d is referencing the missing service contract with ID %d.
9609 16 No The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
9610 16 No The service '%.*ls' in the FROM SERVICE clause must match the service '%.*ls' referenced by %s = '%.*ls'.
9611 16 No Cannot find the specified user '%.*ls'.
9613 16 No The queue '%.*ls' cannot be activated because the activation user is not specified.
9614 16 No The queue '%.*ls' cannot be activated because the activation stored procedure is either not specified or is invalid.
9615 16 No A message of type '%.*ls' failed XML validation on the target service. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
9616 16 No A message of type '%.*ls' was received and failed XML validation. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
9617 16 No The service queue "%.*ls" is currently disabled.
9618 16 No The message cannot be sent because the service queue '%.*ls' associated with the dialog is currently disabled and retention is on.
9619 16 No Failed to create remote service binding '%.*ls'. A remote service binding for service '%.*ls' already exists.
9620 16 No The activation stored procedure '%.*ls' is invalid. Functions are not allowed.
9621 16 No An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i.
9622 16 No The crypto provider context is not initialized.
9623 16 No The key passed in for this operation is in the wrong state.
9624 16 No The key size is unacceptable for this key object.
9625 16 No The key buffer size is inconsistent with the key modulus size.
9626 16 No An internal Service Broker error occurred: an object is in the wrong state for this operation. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems.
9627 16 No The hash buffer size is not correct for initializing the hash object.
9628 16 No The encryption/decryption data buffer size is not 8 byte aligned.
9629 16 No The decrypted signature size is wrong.
9630 16 No The signature did not verify the internal hash.
9631 16 No The salt size is unacceptable for this key object.
9632 16 No The salt buffer size is too small.
9633 16 No The passed in name is too long.
9634 16 No Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.
9635 16 No The certificate is not valid at this point in time.
9636 16 No The requested object was not found.
9637 16 No The passed in serialized object is incorrectly encoded.
9638 16 No The cer or pvk file size is too large.
9639 16 No A password was supplied and the pvk file is not encrypted.
9640 16 No The operation encountered an OS error.
9641 16 No A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for further information.
9642 16 No An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far endpoint address: '%.*hs')
9643 16 No An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i.
9644 16 No An error occurred in the service broker message dispatcher. Error: %i, State: %i.
9645 16 No An error occurred in the service broker manager, Error: %i, State: %i.
9646 16 No An error occurred in the timer event cache. Error %i, state %i.
9647 16 Yes Received a malformed message from the network. Unable to retrieve a broker message attribute from a message destined for database ID %d. This may indicate a network problem or that another application connected to the Service Broker endpoint.
9648 20 No The queue '%.*ls' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider increasing the number of MAX_QUEUE_READERS.
9649 16 Yes A security (SSPI) error occurred when connecting to another service broker: '%.*ls'. Check the Windows Event Log for more information.
9650 16 No A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '%ls'.
9651 16 No The system call failed during a Service Broker or Database Mirroring operation. System error: '%ls'.
9652 16 No Service Broker failed to retrieve the session key for encrypting a message.
9653 16 No The signature of activation stored procedure '%.*ls' is invalid. Parameters are not allowed.
9654 16 No Attempting to use database and it doesn't exist.
9655 16 Yes The transmission queue table structure in database is inconsistent. Possible database corruption.
9657 23 Yes The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware problems. Check the SQL Server error log and the Windows event logs for information on possible hardware problems. Restart SQL Server to rebuild tempdb.
9658 16 No Cannot access the transmission queue table in database.
9659 16 No The %s of route '%.*ls' cannot be empty.
9660 16 No The %s of route '%.*ls' must be less than %d characters long.
9661 16 No The SERVICE_NAME and BROKER_INSTANCE of route "%.*ls" must be specified when using mirroring.
9662 16 No Cannot specify BROKER_INSTANCE without SERVICE_NAME in route "%.*ls".
9663 16 No The system object cannot be modified.
9666 10 No The %S_MSG protocol transport is disabled or not configured.
9667 10 No Services analyzed: %d.
9668 10 No Service Queues analyzed: %d.
9669 10 No Conversation Endpoints analyzed: %d.
9670 10 No Remote Service Bindings analyzed: %d.
9671 16 No Messages with conversation ID '%ls' have been removed from the transmission queue.
9672 16 No Messages with conversation handle '%ls' and conversation group '%ls' have been removed from the queue with ID %d.
9673 16 No Activation has been disabled on the queue with ID %d.
9674 10 No Conversation Groups analyzed: %d.
9675 10 No Message Types analyzed: %d.
9676 10 No Service Contracts analyzed: %d.
9677 16 No The service contract with ID %d is referencing the missing message type with ID %d.
9678 16 No The service with ID %d is referencing the missing service contract with ID %d.
9679 16 No The service with ID %d is referencing the missing service queue with ID %d.
9680 16 No The conversation endpoint '%ls' is referencing the missing conversation group '%ls'.
9681 16 No The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service contract with ID %d.
9682 16 No The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service with ID %d.
9683 16 No The conversation group '%ls' is referencing the missing service with ID %d.
9684 16 No The service with ID %d has been dropped.
9685 16 No The service contract with ID %d has been dropped.
9686 16 No The conversation endpoint with handle '%ls' has been dropped.
9687 16 No The conversation group '%ls' has been dropped.
9688 10 No Service Broker manager has started.
9689 10 No Service Broker manager has shut down.
9690 10 Yes The %S_MSG protocol transport is now listening for connections.
9691 10 No The %S_MSG protocol transport has stopped listening for connections.
9692 16 No The %S_MSG protocol transport cannot listen on port %d because it is in use by another process.
9693 16 No The %S_MSG protocol transport could not listen for connections due to the following error: '%.*ls'.
9694 16 No Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
9695 16 No Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.
9696 16 No Cannot start the Service Broker primary event handler. This error is a symptom of another problem. Check the SQL Server error log for additional messages, and address this underlying problem.
9697 10 No Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
9698 16 No Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address the underlying problem.
9699 16 No Could not allocate memory for extra Service Broker tasks while adding CPUs.
9701 16 No Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem.
9704 16 No This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target service.
9705 16 No The messages in the queue with ID %d are referencing the invalid conversation handle '%ls'.
9706 16 No The stored procedure with ID %d is invalid but is referenced by the queue with ID %d.
9707 16 No The activation user with ID %d is invalid but is referenced by queue with ID %d.
9708 16 No The messages in the queue with ID %d are referencing the invalid conversation group '%ls'.
9709 16 No The messages in the queue with ID %d are referencing the invalid message type with ID %d.
9710 16 No The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation group '%ls'.
9711 16 No The transmission queue is referencing the invalid conversation ID '%ls'.
9712 16 No The remote service binding with ID %d is referencing the invalid service contract with ID %d.
9713 16 No The message type with ID %d is referencing the invalid XML schema collection ID %d.
9715 16 No The conversation endpoint with conversation handle '%ls' is in an inconsistent state. Check the SQL Server error logs and the Windows event logs for information on possible hardware problems. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data.
9716 16 No The conversation group '%ls' reports references to %d conversation handle(s), but actually references %d.
9717 16 No Cannot enable stored procedure activation on queue '%.*ls'. Event notification for queue_activation is already configured on this queue.
9718 16 No Cannot create event notification for queue_activation on queue "%.*ls". Stored procedure activation is already configured on this queue.
9719 16 No The database for this conversation endpoint is attached or restored.
9720 16 No The database for the remote conversation endpoint is attached or restored.
9721 10 No Service broker failed to clean up conversation endpoints on database '%.*ls'. Another problem is preventing SQL Server from completing this operation. Check the SQL Server error log for additional messages.
9723 10 No The database "%i" will not be started as the broker due to duplication in the broker instance ID.
9724 10 No The activated proc '%ls' running on queue '%ls' output the following: '%.*ls'
9725 16 No The invalid schema has been dropped from the message type with ID %d.
9726 16 No The remote service binding with ID %d has been dropped.
9727 16 Yes Dialog security is not available for this conversation because there is no remote service binding for the target service. Create a remote service binding, or specify ENCRYPTION = OFF in the BEGIN DIALOG statement.
9728 16 Yes Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped after the conversation was created.
9730 16 Yes Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security principal may have been dropped after the conversation was created.
9731 16 Yes Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: %i). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation.
9733 16 Yes There is no private key for the security certificate bound to database principal (Id: %i). The certificate may have been created or installed incorrectly. Reinstall the certificate, or create a new certificate.
9734 16 Yes The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.
9735 16 Yes The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.
9736 16 No An error occurred in dialog transmission: Error: %i, State: %i. %.*ls
9737 16 Yes The private key for the security certificate bound to the database principal (ID %i) is password protected. Password protected private keys are not supported for use with secure dialogs.
9738 16 No Cannot create task for Service Broker message dispatcher. This message is a symptom of another problem that is preventing SQL Server from creating tasks. Please check the SQL Server error log and the Windows event log for additional messages.
9739 16 No Message transmitter in service broker message dispatcher failed %d times
9740 16 No Cannot start the Service Broker message dispatcher. This error is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address this underlying problem.
9741 10 No The %S_MSG '%.*ls' was dropped on upgrade because it referenced a system contract that was dropped.
9742 16 No The activation stored procedure '%.*ls' is invalid. Temporary procedures may not be configured for activation.
9743 16 No The %s of route "%.*ls" must be an address when using mirroring.
9744 16 No The %s of route "%.*ls" is not a valid address.
9745 16 No The ADDRESS of route '%.*ls' cannot be 'TRANSPORT' when SERVICE_NAME is specified.
9746 16 No The LIFETIME of route '%.*ls' must be in the range %d to %d.
9747 16 No The ADDRESS and MIRROR_ADDRESS of route '%.*ls' cannot be the same.
9748 10 No The %S_MSG protocol transport is not available.
9749 10 No Target queue is busy; message(s) queued for delivery.
9750 10 No No route matches the destination service name for this conversation. Create a route to the destination service name for messages in this conversation to be delivered.
9751 10 No Authentication failed with error: '%.*ls'.
9752 10 No %S_MSG connection was refused. The user account of the remote server is not permitted to log in to this SQL Server: User account: '%.*ls', IP address: '%.*hs'.
9753 10 No The target service broker is unreachable.
9754 10 No Connection attempt failed with error: '%.*ls'.
9755 10 No An error occurred while receiving data: '%.*ls'.
9756 10 No An internal exception occurred while connecting to an adjacent broker: Error: %i, State: %i. %.*ls
9757 10 No Service Broker/Database Mirroring network protocol error occurred.
9758 10 No Login protocol negotiation error occurred.
9759 10 No An error occurred while sending data: '%.*ls'.
9761 16 Yes The Broker Configuration conversation on dialog handle '%s' closed due to an error. To troubleshoot this problem, investigate the error: '%.*ls'.
9762 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: No certificate was found.
9763 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is not valid at the current time.
9764 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is too large.
9765 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found has no associated private key.
9766 10 No An unknown internal error (%d) occurred while looking up the public key certificate associated with this SQL Server instance.
9767 16 Yes The security certificate bound to database principal (Id: %i) has been disabled for use with BEGIN DIALOG. See the Books Online topics "Certificates and Service Broker" for an overview and "ALTER CERTIFICATE (Transact-SQL)" for syntax to make a certificate ACTIVE FOR BEGIN_DIALOG.
9768 16 Yes A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER while conversations are being created.
9769 10 No Insufficient memory prevented the Service Broker/Database Mirroring Transport Manager from starting.
9770 10 No Locating routes and security information via the Broker Configuration Service.
9771 10 No The service broker manager is disabled in single-user mode.
9772 16 No The Service Broker in database "%.*ls" cannot be enabled because there is already an enabled Service Broker with the same ID.
9773 10 No The Service Broker in database "%d" is disabled because there is already an enabled Service Broker with the same ID.
9774 10 No Cannot create a new Service Broker in the attached read-only database "%.*ls". The Service Broker will be disabled.
9775 16 No Cannot create a new Service Broker in read-only database "%.*ls".
9776 16 No Cannot enable the Service Broker in database "%.*ls" because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s).
9777 10 No The Service Broker in database "%.*ls" will be disabled because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s).
9778 16 No Cannot create a new Service Broker in a mirrored database "%.*ls".
9779 10 No Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.
9780 10 No The service broker manager is initializing.
9781 10 No The service broker manager is shutting down.
9782 10 No An internal exception occurred while dispatching a message: Error: %i, State: %i. %.*ls
9783 10 No DNS lookup failed with error: '%.*ls'.
9784 10 No Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.
9785 10 No Invalid address specified: '%.*ls'.
9786 10 No Cannot retrieve user name from security context. Error: '%.*ls'. State: %hu.
9787 10 No An error occurred while processing broker mirroring routes. Error: %i. State: %i.
9788 10 No Unable to route the incoming message. The system database msdb containing routing information is not available.
9789 10 No Unable to route the incoming message. The system database msdb containing routing information is not available. The broker is disabled in msdb.
9790 10 No Unable to route the incoming message. The system database msdb containing routing information is in SINGLE USER mode.
9791 10 No The broker is disabled in the sender's database.
9792 10 No Could not forward the message because forwarding is disabled in this SQL Server instance.
9793 10 No The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied.
9794 10 No The broker mirroring manager has not fully initialized.
9795 10 No Could not find the target broker in the local SQL Server instance.
9796 10 No The target service name matched a LOCAL route, but there is no service by that name in the local SQL Server instance.
9797 10 No Classification has been delayed because the routing information is currently being updated.
9798 16 No The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
9801 16 No Error converting %.*ls to %ls. The result would be truncated.
9802 16 No The locale identifier (LCID) %d is not supported by SQL Server.
9803 16 No Invalid data for type "%ls".
9804 16 No Column or parameter #%d: Invalid fractional second precision %d specified for %ls data type. The maximum fractional second precision is %d.
9805 10 No Warning: converting %ls to %ls caused a loss of information.
9806 16 No The datepart %.*ls is not supported by date function %.*ls.
9807 16 No The input character string does not follow style %d, either change the input character string or use a different style.
9808 16 No This session's YDM date format is not supported when converting from this character string format to date, time, datetime2 or datetimeoffset. Change the session's date format or provide a style to the explicit conversion.
9809 16 No The style %d is not supported for conversions from %s to %s.
9810 16 No The datepart %.*ls is not supported by date function %.*ls for data type %s.
9811 16 No The system timezone information could not be retrieved.
9812 16 No The timezone provided to builtin function %.*ls is invalid.
9813 16 No The timezone provided to builtin function %.*ls would cause the datetimeoffset to overflow the range of valid date range in either UTC or local time.
9814 16 No The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. (Julian calendar) or July 18th, 622 C.E (proleptic Gregorian calendar).
9815 16 No Waitfor delay and waitfor time cannot be of type %s.
9816 16 No The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set.
9817 16 No The specified column set value causes the estimated row size to be at least %d bytes. This exceeds the maximum allowed row size of %d bytes. To reduce the row size, reduce the number of columns specified in the column set.
9901 16 Yes Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on disk space. Pausing all populations in progress until more space becomes available. Reason code: %d. Error: %ls. To resume populations, free up disk space.
9902 10 No Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on system resources. Any population in progress will be paused until more resources become available. Reason code: %d. Error: %ls. If this message occurs frequently, try to serialize full-text indexing for multiple catalogs.
9903 10 No The full-text catalog health monitor reported a failure for full-text catalog '%ls' (%d) in database '%ls' (%d). Reason code: %d. Error: %ls. The system will restart any in-progress population from the previous checkpoint. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required.
9904 10 No The full-text catalog '%ls' (%d) in database '%ls' (%d) will be remounted to recover from a failure. Reason code: %d. Error: %ls. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required.
9905 10 No Informational: Full-text indexer requested status change for catalog '%ls' ('%d') in database '%ls' ('%d'). New Status: %ls, Reason: %ls (%ls).
9906 10 No The full-text catalog monitor reported catalog '%ls' (%d) in database '%ls' (%d) in %ls state. This is an informational message only. No user action is required.
9907 10 No Error: Total number of items in full-text catalog ID '%d' in database ID '%d' exceeds the supported limit. See Books Online for troubleshooting assistance.
9908 10 No Changing the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). This is an informational message only. No user action is required.
9909 10 No Warning: Failed to change the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). Error: %ls.
9910 10 No Warning: Error occurred during full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %ls.
9911 10 No Informational: Full-text %ls population initialized for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Population sub-tasks: %d.
9912 10 No Error: Failed to initialize full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %d.
9913 10 No Informational: Resuming full-text population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). Prior number of documents processed: %d, error encountered: %d.
9914 16 No Error: Failed to resume full-text %ls population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: 0x%x. Repeat the operation that triggered the resume, or drop and re-create the index.
9915 10 No Reinitialized full-text %ls population for table '%ls' (table ID '%d', database ID '%d') after a temporary failure. Number of documents processed prior to failure: %d, errors encountered: %d. This is an informational message only. No user action is required.
9916 10 No Error: Failed to reinitialize full-text %ls population after a temporary failure for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %d.
9917 17 No An internal error occurred in full-text docid mapper.
9918 10 No Warning: Full-text catalog '%ls' uses FAT volume. Security and differential backup are not supported for the catalog.
9919 16 No Fulltext DDL command failed because SQL Server was started in single user mode.
9920 10 No Warning: Failed to get MSFTESQL indexer interface for full-text catalog '%ls' ('%d') in database '%ls' ('%d'). Error: %ls.
9921 16 No During upgrade fatal error 0x%x encountered in CoCreateGuid. Failed to resolve full-text catalog file name for '%ls'.
9922 10 No Warning: Full-text population for table or indexed view '%ls' failed to send batch of data to MSFTESQL service (table or indexed view ID '%d', catalog ID '%d', database ID '%d'). Error: %ls.
9923 10 No Warning: Full-text population for table or indexed view '%ls' reported low resources while sending a batch of data to MSFTESQL service (table or indexed view ID '%d', catalog ID '%d', database ID '%d'). Error: %ls.
9924 16 No Rebuild full-text catalog '%ls' failed: Catalog header file is read-only.
9925 16 No Rebuild full-text catalog '%ls' failed: Full-text catalog is read-only.
9926 10 No Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should.
9927 10 No Informational: The full-text search condition contained noise word(s).
9928 16 No Computed column '%.*ls' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column.
9929 16 No Computed column '%.*ls' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column must be deterministic, precise or persisted, with a size less or equal than %d characters.
9930 10 No Null document type provided. Row will not be full-text indexed.
9931 10 No Document type exceeds the maximum permitted length. Row will not be full-text indexed.
9932 10 No Document type value is malformed. Row will not be full-text indexed.
9933 10 No Internal error: The row cannot be full-text indexed. The protocol handler was invoked out of sequence. This is an informational message only. No user action is required.
9934 10 No Row was not found. It was deleted or updated while indexing was in progress.
9935 10 No Warning: Wordbreaker, filter, or protocol handler used by catalog '%ls' does not exist on this instance. Use sp_help_fulltext_catalog_components and sp_help_fulltext_system_components check for mismatching components. Rebuild catalog is recommended.
9936 10 No Informational: No full-text supported languages found.
9937 16 No Too many full-text columns or the full-text query is too complex to be executed.
9938 16 No Cannot find the specified user or role '%.*ls'.
9939 16 No Current user or role '%.*ls' does not have the required permission to set the owner.
9940 10 No Error: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is terminated due to the preceding error.
9941 10 No Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is being suspended by the system as the database is unavailable. System will resume the population whenever the database is available
9942 10 No Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') was cancelled by user.
9943 10 No Informational: Full-text %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documents processed: %d. Number of documents failed: %d. Number of documents that will be retried: %d.
9944 10 No Informational: Full-text retry pass of %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of retry documents processed: %d. Number of documents failed: %d.
9945 10 No Error: All Full-text populations in progress, for catalog '%ls' ('%d') in database '%ls' ('%d') were terminated due to error. Error: 0x%x.
9947 10 No Warning: Identity of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog cannot be attached.
9948 10 No Warning: Full-text catalog path '%ls' is invalid. It exceeds the length limit, or it is a relative path, or it is a hidden directory. The full-text catalog cannot be attached.
9949 10 No Warning: All Full-text populations in progress for full-text catalog '%ls' ('%d') in database '%ls' ('%d') are paused. Reason code: %d. Error: %ls. If this message occurs frequently, consult Books Online for indexing performance tuning assistance.
9950 10 No Informational: Full-text catalog health monitor reported a failure for catalog '%ls' ('%d') in database '%ls' ('%d'). Reason code: %d. Error: %ls. The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch.
9951 10 No Warning: Database %.*ls cannot be modified during detach because database is in read-only, standby, or shutdown state. Full-text catalog is not dropped, and '@keepfulltextindexfile = false' is ignored.
9952 10 No Informational: Full-text auto change tracking is turned off for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') due to fatal crawl error.
9953 16 No The path '%.*ls' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive.
9954 16 No SQL Server failed to communicate with filter daemon launch service (Windows error: %ls). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
9955 16 No SQL Server failed to create named pipe '%ls' to communicate with the full-text filter daemon (Windows error: %d). Either a named pipe already exists for a filter daemon host process, the system is low on resources, or the security identification number (SID) lookup for the filter daemon account group failed. To resolve this error, terminate any running full-text filter daemon processes, and if necessary reconfigure the full-text daemon launcher service account.
9959 16 No Cannot perform requested task because full-text memory manager is not initialized.
9960 16 No View '%.*ls' is not an indexed view. Full-text index is not allowed to be created on it.
9961 16 No Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified.
9962 16 No Failed to move full-text catalog from '%ls' to '%ls'. OS error '%ls'.
9963 10 No Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset.
9964 16 No Failed to finish full-text operation. Filegroup '%.*ls' is empty, read-only, or not online.
9965 16 No NULL or Invalid type of value specified for '%ls' parameter.
9966 16 No Cannot use full-text search in master, tempdb, or model database.
9967 10 No A default full-text catalog does not exist in database '%.*ls' or user does not have permission to perform this action.
9968 10 No Warning: No appropriate filter was found 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'. Some columns of the row were not indexed.
9969 10 No Warning: No appropriate wordbreaker was found 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'. Neutral wordbreaker was used for some columns of the row.
9970 16 No Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline.
9971 10 No Warning: No appropriate filter for embedded object was found 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'. Some embedded objects in the row could not be indexed.
9972 16 No Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE.
9973 10 No Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documents processed: %d. Number of documents failed: %d.
9974 10 No Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue when your start the same type of crawl again.
9975 10 No Warning: Only paused full population can be resumed. The command is ignored.
9977 10 No Warning: Last population complete time of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog is attached and it may need to be repopulated.
9978 10 No Warning: During upgrade full-text index on table '%ls' is disabled because at least one of full-text key column, full-text columns, or type columns is a non-deterministic or imprecise nonpersisted computed column.
9979 10 No Warning: During upgrade full-text catalog '%ls' in database '%ls' is set as offline because it failed to be created at path '%ls'. Please fix the full-text catalog path and rebuild the full-text catalog after upgrade.
9980 16 No Variable parameters can not be passed to fulltext predicates: contains, freetext and functions: containstable, freetexttable applied to remote table.
9982 16 No Cannot use full-text search in user instance.
9983 16 No The value '%ls' for the full-text component '%ls' is longer than the maximum permitted (%d characters). Please reduce the length of the value.
9984 10 No Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d').
9998 16 No The column '%.*ls' cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a full-text index, add fewer columns.
9999 16 No The column '%.*ls' in the table '%.*ls' cannot be used for full-text search because it is a sparse column set.

Errors 10,000 to 10,999

ErrorSeverityEvent LoggedDescription
10000 16 No Unknown provider error.
10001 16 No The provider reported an unexpected catastrophic failure.
10002 16 No The provider did not implement the functionality.
10003 16 No The provider ran out of memory.
10004 16 No One or more arguments were reported invalid by the provider.
10005 16 No The provider did not support an interface.
10006 16 No The provider indicated an invalid pointer was used.
10007 16 No The provider indicated an invalid handle was used.
10008 16 No The provider terminated the operation.
10009 16 No The provider did not give any information about the error.
10010 16 No The data necessary to complete this operation was not yet available to the provider.
10011 16 No Access denied.
10021 16 No Execution terminated by the provider because a resource limit was reached.
10022 16 No The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
10023 16 No The provider does not support the necessary method.
10024 16 No The provider indicates that the user did not have the permission to perform the operation.
10025 16 No Provider caused a server fault in an external process.
10026 16 No No command text was set.
10027 16 No Command was not prepared.
10028 16 No Authentication failed.
10032 16 No Cannot return multiple result sets (not supported by the provider).
10033 16 No The specified index does not exist or the provider does not support an index scan on this data source.
10034 16 No The specified table or view does not exist or contains errors.
10035 16 No No value was given for one or more of the required parameters.
10042 16 No Cannot set any properties while there is an open rowset.
10052 16 No The insertion was canceled by the provider during notification.
10053 16 No Could not convert the data value due to reasons other than sign mismatch or overflow.
10054 16 No The data value for one or more columns overflowed the type used by the provider.
10055 16 No The data violated the integrity constraints for one or more columns.
10056 16 No The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10057 16 No Cannot create the row. Would exceed the total number of active rows supported by the rowset.
10058 16 No The consumer cannot insert a new row before releasing previously-retrieved row handles.
10060 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
10061 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
10062 16 No The change was canceled by the provider during notification.
10063 16 No The change was canceled by the provider during notification.
10064 16 No Could not convert the data value due to reasons other than sign mismatch or overflow.
10065 16 No The data value for one or more columns overflowed the type used by the provider.
10066 16 No The data violated the integrity constraints for one or more columns.
10067 16 No The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10068 16 No The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
10069 16 No The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
10081 16 No The consumer could not delete the row. The insertion has been transmitted to the data source.
10085 16 No The rowset uses integrated indexes and there is no current index.
10086 16 No RestartPosition on the table was canceled during notification.
10087 16 No The table was built over a live data stream and the position cannot be restarted.
10088 16 No The provider did not release some of the existing rows.
10100 16 No The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.
10101 16 No Cannot create %S_MSG on view "%.ls" because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG() to simulate DISTINCT on grouping columns.
10102 16 No Cannot create %S_MSG on view "%.*ls" because it contains the TOP keyword. Consider removing TOP or not indexing the view.
10103 16 No Cannot create %S_MSG on view "%.*ls" because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view.
10104 16 No Cannot create %S_MSG on view "%.*ls" because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUERY, OPENROWSET, and OPENDATASOURCE.
10105 16 No Cannot create %S_MSG on view "%.*ls" because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view.
10106 16 No Cannot create %S_MSG on view "%.*ls" because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view.
10107 16 No Cannot create %S_MSG on view "%.*ls" because it references an internal system rowset provider. Consider not indexing this view.
10108 16 No Cannot create %S_MSG on view "%.*ls" because it uses table variable "%.*ls". Consider not indexing this view or removing the reference to the table variable.
10109 16 No Cannot create %S_MSG on view "%.*ls" because it references a SQL Server internal table.
10110 16 No Cannot create %S_MSG on view "%.*ls" because it references derived table "%.*ls" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.
10111 16 No Cannot create %S_MSG on view "%.*ls" because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY.
10112 16 No Cannot create %S_MSG on view "%.*ls" because it contains a join using an ODBC standard escape syntax. Consider using an ANSI join syntax instead.
10113 16 No Cannot create %S_MSG on view '%.*ls' because it contains an INNER join that specifies a join hint. Consider removing the join hint.
10114 16 No Cannot create %S_MSG on view "%.*ls" because it uses a LEFT, RIGHT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Consider using an INNER join instead.
10115 16 No Cannot create %S_MSG on view "%.*ls" because it uses the PIVOT operator. Consider not indexing this view.
10116 16 No Cannot create %S_MSG on view "%.*ls" because it uses the UNPIVOT operator. Consider not indexing this view.
10117 16 No Cannot create %S_MSG on view '%.*ls' because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view for each query that is an input to the UNION, INTERSECT, or EXCEPT operators of the original view.
10118 16 No Cannot create %S_MSG on view "%.ls" because the view uses the "" operator to select columns. Consider referencing columns by name instead.
10119 16 No Cannot create %S_MSG on view "%.*ls" because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
10121 16 No Cannot create %S_MSG on view "%.*ls" because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.
10122 16 No Cannot create %S_MSG on view "%.*ls" because it contains a HAVING clause. Consider removing the HAVING clause.
10123 16 No Cannot create %S_MSG on view "%.*ls" because it contains a COMPUTE clause. Consider not indexing this view, or using a GROUP BY or aggregate view instead to replace the COMPUTE calculation of aggregate results.
10124 16 No Cannot create %S_MSG on view "%.*ls" because it contains a join that uses deprecated Transact-SQL join syntax ( = and = ). Consider using = operator (non-outer-join) instead.
10125 16 No Cannot create %S_MSG on view "%.*ls" because it references an internal SQL Server column.
10126 16 No Cannot create %S_MSG on view "%.*ls" because it uses aggregate "%.*ls". Consider eliminating the aggregate, not indexing the view, or using alternate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUNT, substitute COUNT_BIG.
10127 16 No Cannot create %S_MSG on view "%.*ls" because it uses aggregate "%.ls" with the DISTINCT keyword. Consider not indexing this view or eliminating DISTINCT. Consider use of a GROUP BY or COUNT_BIG() view to simulate DISTINCT on grouping columns.
10128 16 No Cannot create %S_MSG on view "%.*ls" because it contains one or more subqueries. Consider changing the view to use only joins instead of subqueries. Alternatively, consider not indexing this view.
10129 16 No Cannot create %S_MSG on view "%.*ls" because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or not indexing the view.
10130 16 No Cannot create %S_MSG on view "%.*ls" because it references the inline or multistatement table-valued function "%.*ls". Consider expanding the function definition by hand in the view definition, or not indexing the view.
10131 16 No Cannot create %S_MSG on view "%.*ls" because it uses non-deterministic common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view or changing it to not use this function.
10132 16 No Cannot create %S_MSG on view "%.*ls" because it references imprecise common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view.
10133 16 No Cannot create %S_MSG on view "%.*ls" because it references table valued common language runtime (CLR) function "%.*ls". Consider removing reference to the function or not indexing the view.
10134 16 No Cannot create %S_MSG on view "%.*ls" because function "%.*ls" referenced by the view performs user or system data access.
10136 16 No Cannot create %S_MSG on view "%.*ls" because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY.
10137 16 No Cannot create %S_MSG on view "%.*ls" because it uses the aggregate COUNT. Use COUNT_BIG instead.
10138 16 No Cannot create %S_MSG on view "%.*ls" because it references common table expression "%.*ls". Views referencing common table expressions cannot be indexed. Consider not indexing the view, or removing the common table expression from the view definition.
10139 16 No Cannot create %S_MSG on view '%.ls' because its select list does not include a proper use of COUNT_BIG. Consider adding COUNT_BIG() to select list.
10140 16 No Cannot create %S_MSG on view '%.*ls' because the view uses an implicit conversion from string to datetime or smalldatetime. Use an explicit CONVERT with a deterministic style value.
10141 16 No Cannot create %S_MSG on view '%.*ls' because the view contains a table hint. Consider removing the hint.
10142 16 No Cannot create %S_MSG on view '%.*ls' because it references CLR routine (function or method) '%.*ls' outside non-key columns of SELECT list. Recreate or alter view so it does not reference CLR routines except in non-key columns of SELECT list, and then create index.
10143 16 No Cannot create %S_MSG on view "%.*ls" because it contains an APPLY. Consider not indexing the view, or removing APPLY.
10144 16 No Cannot create %S_MSG on view "%.*ls" because it contains a ranking or aggregate window function. Remove the function from the view definition or, alternatively, do not index the view.
10145 16 No Cannot create %S_MSG on view '%.*ls' because it uses the CHANGETABLE function.
10211 16 No Cannot create %S_MSG on the view '%.*ls' because it references a sparse column set. Views that contain a sparse column set cannot be indexed. Consider removing the sparse column set from the view or not indexing the view.
10227 16 No Cannot invoke mutator on a null CLR type value.
10240 16 No Field "%.*ls" of type "%.*ls.%.*ls" cannot be updated because the field is "%.*ls".
10300 16 No Could not find UdtExtensions.dll. Please check your installation.
10301 16 No Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %S_MSG). Please load the referenced assembly into the current database and retry your request.
10302 16 No Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %s). Please load the referenced assembly into the current database and retry your request.
10303 16 Yes Could not get path for SQL Server: '%ls'.
10304 16 No Could not create AppDomain manager: '%.*ls'.
10305 16 No Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions.
10306 16 No The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.
10307 16 No The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property.
10308 10 No The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name.
10309 10 No Warning: The Microsoft .NET Framework assembly '%.*ls' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
10310 10 Yes Warning: The SQL Server client assembly '%.*ls' you are registering is not fully tested in SQL Server hosted environment.
10311 10 Yes AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
10312 16 No AppDomain %i (%.*ls) is marked for unload due to memory pressure.
10313 16 No .NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token.
10314 16 No An error occurred while using the .NET Framework during %S_MSG. The server may be running out of resources. Try running the query again. If the problem persist, contact a support professional. %.*ls
10316 16 No An error occurred in the Microsoft .NET Framework while trying to load assembly id %d. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: %.*ls
10317 16 No The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found.
10318 16 No An error occurred trying to get file version info for the file '%s'.
10319 16 No '%.*ls' failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute.
10320 16 No UserDefinedType method call failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute.
10321 16 No Method name '%.*ls' is invalid for '%.*ls'.
10322 16 No Method name '%.*ls' is invalid for UserDefinedType method call.
10323 16 Yes Type %.*ls not found in database %.*ls
10324 16 No Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls
10325 16 Yes WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers.
10326 16 Yes The server is shutting down due to stack overflow in user's unmanaged code.
10327 14 No Two versions of assembly '%.*ls' cannot coexist in database '%.*ls'. Keep one version and drop the other.
10328 16 No %ls ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is not authorized for PERMISSION_SET = %ls. The assembly is authorized when either of the following is true: the database owner (DBO) has %ls permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with %ls permission.
10329 16 No There is not enough stack to create appdomain '%.*ls'.
10330 16 No .Net Framework execution was aborted. %.*ls
10331 16 No ALTER ASSEMBLY failed because serialization layout of type '%s' would change as a result of a change in type '%s' in the updated assembly. Persisted types are not allowed to change serialization layout.
10501 16 No Type '%ls' in assembly '%.*ls' derives from a generic type which is not supported for a CLR Type.
10502 16 No Cannot create plan guide '%.*ls' because type '%.*ls' provided is not allowed.
10503 16 No Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, matches the existing plan guide '%.*ls' in the database. Drop the existing plan guide before creating the new plan guide.
10504 16 No Operation '%.*ls' is not allowed.
10505 16 No Cannot create plan guide '%.*ls' because parameter @hints is incorrect. Use N'OPTION ( <query_hint> [ ,...n ] )'.
10506 16 No Cannot create plan guide '%.*ls' because value '%.*ls' provided for @module_or_batch is not legal two-part name. Use 'schema_name.object_name'.
10507 16 No Cannot create plan guide '%.*ls' because parameter @stmt has more than one statement.
10508 16 No Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, does not match any statement in the specified module or batch. Modify the values to match a statement in the module or batch.
10509 16 No Cannot '%ls' plan guide '%.*ls' because it does not exist or you do not have permission. Verify plan guide name and database of current session, and that you have needed permission.
10510 16 No Cannot create plan guide '%.*ls' because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is ineligible for use in a plan guide. Provide a single valid Transact-SQL statement or a valid starting position of the statement within the batch. To obtain a valid starting position, query the 'statement_start_offset' column in the sys.dm_exec_query_stats dynamic management function.
10512 16 No Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name.
10513 16 No Cannot create plan guide '%.*ls' because object '@module_or_batch' is encrypted. Consider tuning query using other techniques such as indexes and statistics.
10515 16 No Cannot %S_MSG %S_MSG '%.*ls' because it is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
10516 16 No Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission.
10517 16 No Cannot create plan guide '%.*ls' because @module_or_batch can not be compiled.
10518 16 No Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required.
10519 16 No Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide '%.*ls'. Alter permission on object referenced by plan guide, or alter database permission required.
10520 16 No Cannot create plan guide '%.*ls' because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statement_start_offset. Verify that the hints can be applied to the statement.
10521 16 No Cannot create plan guide '%.*ls' because @type was specified as '%ls' and a non-NULL value is specified for the parameter '%ls'. This type requires a NULL value for the parameter. Specify NULL for the parameter, or change the type to one that allows a non-NULL value for the parameter.
10522 16 No Cannot create plan guide '%.*ls' because @type was specified as '%ls' and the parameter '%ls' is NULL. This type requires a non-NULL value for the parameter. Specify a non-NULL value for the parameter, or change the type to one that allows a NULL value for the parameter.
10523 16 No Cannot create plan guide '%.*ls' because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) if @type is 'template'.
10524 16 No Cannot generate query template because @querytext does not contain a valid single query.
10525 10 No Cannot parameterize @querytext.
10526 16 No Plan guide '%.*ls' matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains was ignored. RECOMPILE is not supported on automatically parameterized statements. Consider dropping this plan guide or removing RECOMPILE from it.
10527 16 No Cannot drop %S_MSG '%.*ls' because its trigger '%.*ls' is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
10528 16 No Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object.
10529 16 No Cannot create plan guide '%.*ls' because its name is invalid. Plan guide name cannot begin with a '#' character.
10530 16 No Cannot create plan guide '%.*ls' because there is already a planguide '%.*ls' of @type 'template' on @stmt.
10531 16 No Cannot create plan guide '%.*ls' because the statement specified by @statement_start_offset does not match any statement in specified module or batch. Consider modifying @statement_start_offset to match a statement in module or batch.
10532 16 No Cannot create plan guide '%.*ls' from cache because the user does not have adequate permissions. Grant the VIEW SERVER STATE permission to the user creating the plan guide.
10533 16 No Cannot create plan guide '%.*ls' because the batch or module specified by @plan_handle does not contain a statement that is eligible for a plan guide. Specify a different value for @plan_handle.
10534 16 No Cannot create plan guide '%.*ls' because the plan guide name exceeds 124, the maximum number of characters allowed. Specify a name that contains fewer than 125 characters.
10535 16 No Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form <parameter_name> <parameter_type>, or specify NULL.
10536 16 No Cannot create plan guide '%.*ls' because a plan was not found in the plan cache that corresponds to the specified plan handle. Specify a cached plan handle. For a list of cached plan handles, query the sys.dm_exec_query_stats dynamic management view.
10537 16 No Cannot create plan guide '%.*ls' because the batch or module corresponding to the specified @plan_handle contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a statement_start_offset value for each statement.
10538 16 No Cannot enable plan guide '%.*ls' because the enabled plan guide '%.*ls' contains the same scope and starting offset value of the statement. Disable the existing plan guide before enabling the specified plan guide.
10539 16 No Cannot find the plan guide either because the specified plan guide ID is NULL or invalid, or you do not have permission on the object referenced by the plan guide. Verify that the plan guide ID is valid, the current session is set to the correct database context, and you have ALTER permission on the object referenced by the plan guide or ALTER DATABASE permission.
10601 16 No Cannot create plan guide '%.*ls' from cache because a query plan is not available for the statement with start offset %d.This problem can occur if the statement depends on database objects that have not yet been created. Make sure that all necessary database objects exist, and execute the statement before creating the plan guide.
10602 16 No Cannot specify included columns for a clustered index.
10603 16 No Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
10604 16 No Cannot rebuild clustered index '%.*ls' on view '%.*ls' because the view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disabled.
10605 16 No Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
10606 16 No Cannot disable primary key index "%.*ls" on table "%.*ls" because the table is published for replication.
10607 16 No Cannot disable the clustered index "%.*ls" on view "%.*ls" because the indexed view is published for replication.
10608 16 No The clustered index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Disable change tracking on the table before disabling the clustered index.
10609 16 No The index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Change tracking requires a primary key constraint on the table, and disabling the index will drop the constraint. Disable change tracking on the table before disabling the index.
10610 16 No Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is a computed column. Rewrite the filter expression so that it does not include this column.
10611 16 No Filtered index '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered indexes are only supported on tables. If you are trying to create a filtered index on a view, consider creating an indexed view with the filter expression incorporated in the view definition.
10612 16 No Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant of higher data type precedence or of a different collation. Converting a column to the data type of a constant is not supported for filtered %S_MSG. To resolve this error, explicitly convert the constant to the same data type and collation as the column '%.*ls'.
10617 16 No Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant that cannot be converted to the data type of the column. Rewrite the filter expression so that it does not include this comparison.
10618 16 No Index '%.*ls' could not be created or rebuilt. The key length for this index (%d bytes) exceeds the maximum allowed length of '%d' bytes when using the vardecimal storage format.
10619 16 No Cannot %S_MSG filtered index '%.*ls' on table '%.*ls' because the statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it does not use the IGNORE_DUP_KEY option.
10620 16 No Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is of a CLR data type. Rewrite the filter expression so that it does not include this column.
10621 16 No Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the filter expression contains a comparison with a literal NULL value. Rewrite the comparison to use the IS [NOT] NULL comparison operator to test for NULL values.
10622 16 No The index '%.*ls' on table '%.*ls' could not be created because the column '%.*ls' in the filter expression of the index is a column set.
10623 16 No Index '%.*ls' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set column.
10700 16 No Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user tables.
10701 15 No The table-valued parameter "%.*ls" is READONLY and cannot be modified.
10702 15 No The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement.
10703 15 No The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification.
10705 15 No Too many grouping sets. The maximum number is %d.
10706 15 No Subqueries are not allowed in the OUTPUT clause.
10707 15 No Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied.
10708 15 No The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 mode or higher.
10709 15 No DEFAULT is not allowed on the right hand side of "%.*ls"
10710 15 No The number of columns for each row in a table value constructor must be the same.
10711 15 No An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
10712 15 No An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement.
10713 15 No Non-ANSI outer join operators ("=" or "=") are not allowed in a MERGE statement. Use the OUTER JOIN keywords instead.
10714 15 No A MERGE statement must be terminated by a semi-colon (;).
10716 15 No An action of type '%S_MSG' cannot appear more than once in a '%S_MSG' clause of a MERGE statement.
10717 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause.
10718 15 No The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
10719 15 No Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements.
10720 15 No Non-ANSI outer join operators ("=" or "=") are not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. Use the OUTER JOIN keywords instead.
10721 15 No An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
10722 15 No The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
10723 15 No The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
10724 15 No In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of the form 'SET @variable = column = expression' are not valid in the SET clause of an UPDATE action in a MERGE statement. Modify the SET clause to only specify assignments of the form 'SET @variable = column' or 'SET @variable = expression'.
10725 15 No The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
10726 15 No Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
10727 15 No User defined aggregates do not support default parameters.
10728 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.
10729 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.
10730 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statement.
10731 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.
10732 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.
10733 15 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.
10734 16 No A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.
10735 15 No Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.
10736 15 No Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.*ls'.
10737 15 No A full-text stoplist statement must be terminated by a semi-colon (;).
10738 15 No In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specified. The PARTITION=ALL clause is used to reinforce that all partitions of the table or index will be rebuilt, even if only a subset is specified in the DATA_COMPRESSION clause.
10770 15 No The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.
10771 The construct 'feature' is not yet implemented with memory optimized tables.
10772 The construct 'feature' is not supported with natively compiled stored procedures.
10773 The construct 'feature' is not yet implemented with natively compiled stored procedures.
10785 The construct 'feature' is not supported with an active transaction that accesses memory optimized tables or natively compiled stored procedures.
10787 The construct 'feature' is not supported with a hash index.
10794 The construct 'feature' is not supported with construct.
10900 16 No The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.
10901 16 No Failed to configure resource governor during startup. Check SQL Server error log for specific error messages or check the consistency of master database by running DBCC CHECKCATALOG('master').
10902 16 No User does not have permission to alter the resource governor configuration.
10903 16 No User-defined function '%s' does not exist in master database, or the user does not have permission to access it.
10904 16 No The specified schema name '%.*ls' for classifier user-defined function either does not exist, or the user does not have permission to use it.
10905 16 No Resource governor configuration failed. There are active sessions in workload groups being dropped or moved to different resource pools. Disconnect all active sessions in the affected workload groups and try again.
10906 16 No Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicated administrator connection.
10907 16 No The object '%.*ls'.'%.*ls' is not a valid resource governor classifier user-defined function. A valid classifier user-defined function must be schema-bound, return sysname, and have no parameters.
10908 16 No Attribute '%.*ls' with value of %u is greater than attribute '%.*ls' with value of %u.
10909 16 No Attribute '%.*ls' with value of %u is less than attribute '%.*ls' with value of %u.
10910 16 No The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools.
10911 16 No The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all resource pools to exceed 100 percent. Reduce the value or modify other resource pools so that the sum is less than 100.
10912 16 No Requested operation cannot be performed because the resource pool '%.*ls' does not exist.
10913 16 No The operation could not be completed. Dropping predefined %S_MSG is not allowed.
10914 16 No Users are not allowed to %S_MSG the workload group '%.*ls' in the '%.*ls' resource pool.
10915 16 No The name of the %S_MSG '%.*ls' cannot begin with # of ##.
10916 16 No The operation could not be completed. Altering '%.*ls' %S_MSG is not allowed.
10917 16 No Cannot drop resource pool '%.*ls' because it contains workload group '%.*ls'. Drop or remove all workload groups using this resource pool before dropping it.
10918 16 No ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified.
10919 16 No Cannot create %S_MSG '%.*ls' because it already exists.
10920 16 No An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system administrator.
10921 16 No Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier.
10922 16 No The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG.
10923 16 No %ls failed. Rerun the statement.
10981 10 No %ls failed. The resource governor is not available in this edition of SQL Server. You can manipulate resource governor metadata but you will not be able to apply resource governor configuration. Only Enterprise edition of SQL Server supports resource governor.
10982 16 Yes Resource governor reconfiguration succeeded.
10983 16 No Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ID %ld for details. Classifier elapsed time: %I64u ms.
10984 16 No Resource governor '%ls' operation was canceled by user.

Errors 11,000 to 12,999

ErrorSeverityEvent LoggedDescription
11000 16 No Unknown status code for this column.
11001 16 No Non-NULL value successfully returned.
11001 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) (.Net SqlClient Data Provider
11002 16 No Deferred accessor validation occurred. Invalid binding for this column.
11003 16 No Could not convert the data value due to reasons other than sign mismatch or overflow.
11004 16 No Successfully returned a NULL value.
11005 16 No Successfully returned a truncated value.
11006 16 No Could not convert the data type because of a sign mismatch.
11007 16 No Conversion failed because the data value overflowed the data type used by the provider.
11008 16 No The provider cannot allocate memory or open another storage object on this column.
11009 16 No The provider cannot determine the value for this column.
11010 16 No The user did not have permission to write to the column.
11011 16 No The data value violated the integrity constraints for the column.
11012 16 No The data value violated the schema for the column.
11013 16 No The column had a bad status.
11014 16 No The column used the default value.
11015 16 No The column was skipped when setting data.
11031 16 No The row was successfully deleted.
11032 16 No The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source.
11033 16 No The row was released even though it had a pending change.
11034 16 No Deletion of the row was canceled during notification.
11036 16 No The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
11037 16 No The row has a pending delete or the deletion had been transmitted to the data source.
11038 16 No The row is a pending insert row.
11039 16 No DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source.
11040 16 No Deleting the row violated the integrity constraints for the column or table.
11041 16 No The row handle was invalid or was a row handle to which the current thread does not have access rights.
11042 16 No Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.
11043 16 No The row has a storage object open.
11044 16 No The provider ran out of memory and could not fetch the row.
11045 16 No User did not have sufficient permission to delete the row.
11046 16 No The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.
11047 16 No Updating did not meet the schema requirements.
11048 16 No There was a recoverable, provider-specific error, such as an RPC failure.
11100 16 No The provider indicates that conflicts occurred with other properties or requirements.
11101 16 No Could not obtain an interface required for text, ntext, or image access.
11102 16 No The provider could not support a required row lookup interface.
11103 16 No The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.
11104 16 No The provider could not support insertion on this table.
11105 16 No The provider could not support updates on this table.
11106 16 No The provider could not support deletion on this table.
11107 16 No The provider could not support a row lookup position.
11108 16 No The provider could not support a required property.
11109 16 No The provider does not support an index scan on this data source.
11201 16 No This message could not be delivered because the FROM service name is missing. The message origin is: '%ls'.
11202 16 No This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
11203 16 No This message has been dropped because the FROM broker instance is missing. The message origin is '%ls'.
11204 16 No This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: "%.*ls". Message origin: "%ls".
11205 16 No This message has been dropped because the TO service name is missing. The message origin is "%ls".
11206 16 No This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
11207 16 No This message has been dropped because the service contract name is missing. The message origin is "%ls".
11208 16 No This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name "%.*ls". Message origin: "%ls".
11209 16 No This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: '%ls'.
11210 16 No This message has been dropped because the TO service could not be found. Service name: "%.*ls". Message origin: "%ls".
11211 16 No This message has been dropped because the user does not have permission to access the target database. Database ID: %d. Message origin: &quot;%ls&quot;.
11212 16 No This message could not be delivered because the conversation endpoint has already been closed.
11213 16 No This message could not be delivered because this is not the first message in the conversation.
11214 16 No This message could not be delivered because the '%.*ls' contract could not be found or the service does not accept conversations for the contract.
11215 16 No This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: '%.*ls'.
11216 16 No This message could not be delivered because there is already another task processing this message.
11217 16 No This message could not be delivered because it is out of sequence with respect to the conversation. Conversation receive sequence number: %I64d, Message sequence number: %I64d.
11218 16 No This message could not be delivered because it is a duplicate.
11219 16 No This message could not be delivered because the destination queue has been disabled. Queue ID: %d.
11220 16 No This message could not be delivered because the TO broker instance is missing.
11221 16 No This message could not be delivered because there is an inconsistency in the message header.
11222 16 No This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Service Name: '%.*ls'. Conversation Endpoint TO Service Name: '%.*ls'.
11223 16 No This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Message service contract name: '%.*ls'. Conversation endpoint service contract name: '%.*ls'.
11224 16 No This message could not be delivered because another instance of this service program has already started conversing with this endpoint.
11225 16 No This message could not be delivered because the message type name could not be found. Message type name: '%.*ls'.
11226 16 No This message could not be delivered because the message type is not part of the service contract. Message type name: '%.*ls'. Service contract name: '%.*ls'.
11227 16 No This message could not be delivered because the initiator service has sent a message with a message type that can only be sent by the target. Message type name: '%.*ls'. Service contract name: '%.*ls'.
11228 16 No This message could not be delivered because the target service has sent a message with a message type that can only be sent by the initiator. Message type name: '%.*ls'. Service contract name: '%.*ls'.
11229 16 No This message could not be delivered because the security context could not be retrieved.
11230 16 No This message could not be delivered because the message could not be decrypted and validated.
11231 16 No This message could not be delivered because the conversation endpoint is not secured, however the message is secured.
11232 16 No This message could not be delivered because the conversation endpoint is secured, however the message is not secured.
11233 16 No This message has been dropped because the session key of the conversation endpoint does not match that of the message.
11234 16 No This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls.
11235 16 No Received a malformed message. The binary message class (%d:%d) is not defined. This may indicate network problems or that another application is connected to the Service Broker endpoint.
11236 16 No A corrupted message has been received. The binary header size of %d is expected, however the header size received was %d.
11237 16 No A %S_MSG message could not be processed due to insufficient memory. The message was dropped.
11238 16 No A corrupted message has been received. The private variable data segment is malformed.
11239 16 No A corrupted message has been received. The private variable data segment extends beyond the length of the message.
11240 16 No A corrupted message has been received. The binary message preamble is malformed.
11241 16 No A corrupted message has been received. The conversation security version number is not %d.%d.
11242 16 No A corrupted message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found: %d.
11243 16 No A corrupted message has been received. The public variable data element (%d) has been duplicated in this message.
11244 16 No A corrupted message has been received. The handshake validation header is malformed.
11245 16 No A corrupted message has been received. The maximum number of private variable data elements (%d) has been exceeded. Private variable data elements found: %d.
11246 16 No A corrupted message has been received. The private variable data element (%d) has been duplicated in this message.
11247 16 No A corrupted message has been received. The login negotiate header is invalid.
11248 16 No A corrupted message has been received. The SSPI login header is invalid.
11249 16 No A corrupted message has been received. The pre-master-secret is invalid.
11250 16 No A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11251 16 No A corrupted message has been received. The service pair security header source certificate and the signature must both be present or both be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11252 16 No A corrupted message has been received. The destination certificate serial number is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11253 16 No A corrupted message has been received. The service pair security header destination certificate, the key exchange key, the key exchange key ID, and the session key must all be present or all be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11254 16 No A corrupted message has been received. The session key ID is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11255 16 No A corrupted message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11256 16 No A corrupted message has been received. The MIC is present, however the message body or encryption flag is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11257 16 No A corrupted message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11258 16 No A corrupted message has been received. The MIC size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11259 16 No A corrupted message has been received. The certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11260 16 No A corrupted message has been received. The certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11261 16 No A corrupted message has been received. The destination certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11262 16 No A corrupted message has been received. The destination certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11263 16 No A corrupted message has been received. The service pair security header size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11264 16 No A corrupted message has been received. The key exchange key size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11265 16 No A corrupted message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11266 16 No A corrupted message has been received. The encrypted session key size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11267 16 No A corrupted message has been received. The session key ID size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11268 16 No A corrupted message has been received. The salt size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11269 16 No A corrupted message has been received. A UNICODE string is not two byte aligned within the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11270 16 No A corrupted message has been received. A UNICODE string is greater than the maximum allowed size of %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11271 16 No A corrupted message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11272 16 No A corrupted message has been received. The message ID must not be NULL.
11273 16 No A corrupted message has been received. The message body is not properly padded for encryption. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11274 16 No A corrupted message has been received. A sequence number is larger than allowed. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11275 16 No A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11276 16 No A corrupted message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11277 16 No A corrupted message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11278 16 No A corrupted message has been received. The message type is missing for this message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11279 16 No A corrupted message has been received. The message type must not be set in this message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11280 16 No A packet of size %lu bytes could not be processed because it exceeds the receive buffer count.
11281 16 No A corrupted message has been received. The private portion of the message header is malformed.
11282 16 No This message has been dropped due to licensing restrictions. See the documentation for further details.
11285 16 No This forwarded message has been dropped because the hops remaining count has reached 0.
11286 16 No Dropped this forwarded message because this SQL Server instance is out of memory.
11288 16 No This forwarded message has been dropped because a duplicate message is already being forwarded.
11289 16 No This forwarded message has been dropped because its memory usage would exceed the configured memory limit of %d bytes for forwarded messages.
11290 16 No This forwarded message was dropped because the message could not be delivered within the message time to live. This may indicate that the forwarding route is incorrectly configured or that the destination is unavailable.
11291 16 No This forwarded message has been dropped because the time consumed has exceeded the message's time to live of %u seconds (the message arrived with %u seconds consumed and used %u seconds in this broker).
11292 16 No The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events for the error.
11293 16 No This forwarded message has been dropped because a transport is shutdown.
11294 16 No This forwarded message has been dropped because the destination route is not valid.
11295 10 No Endpoint configuration change detected. Service Broker manager and transport will now restart.
11296 10 No Certificate change detected. Service Broker manager and transport will now restart.
11297 16 No A corrupted message has been received. The private variable data segment offset is incorrect.
11298 16 No A corrupted message has been received. The public variable data segment offset is incorrect.
11299 10 No A corrupted message has been received. An unsequenced message had a non-zero sequence number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
11300 10 Yes Error while committing a readonly or a TEMPDB XDES, Shutting down the server.
11301 10 Yes Error while performing transaction notification for object %p event %d.
11302 10 Yes Error during rollback. shutting down database (location: %d).
11303 10 Yes Error releasing reserved log space: %ls space %I64d, code %d, state %d.
11304 10 Yes Failed to record outcome of a local two-phase commit transaction. Taking database offline.
11400 16 No ALTER TABLE SWITCH statement failed. Index '%.*ls' on indexed view '%.*ls' uses partition function '%.*ls', but table '%.*ls' uses non-equivalent partition function '%.*ls'. Index on indexed view '%.*ls' and table '%.*ls' must use an equivalent partition function.
11401 16 No ALTER TABLE SWITCH statement failed. Table '%.*ls' is %S_MSG, but index '%.*ls' on indexed view '%.*ls' is %S_MSG.
11402 16 No ALTER TABLE SWITCH statement failed. Target table '%.*ls' is referenced by %d indexed view(s), but source table '%.*ls' is only referenced by %d indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the source table.
11403 16 No ALTER TABLE SWITCH statement failed. Indexed view '%.*ls' is not aligned with table '%.*ls'. The partitioning column '%.*ls' from the indexed view calculates its value from one or more columns or an expression, rather than directly selecting from the table partitioning column '%.*ls'. Change the indexed view definition, so that the partitioning column is directly selected from table partitioning column '%.*ls'.
11404 16 No ALTER TABLE SWITCH statement failed. Target table '%.*ls' is referenced by %d indexed view(s), but source table '%.*ls' is only referenced by %d matching indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the source table.
11405 16 No ALTER TABLE SWITCH statement failed. Table '%.*ls' is not aligned with the index '%.*ls' on indexed view '%.*ls'. The table is partitioned on column '%.*ls', but the index on the indexed view is partitioned on column '%.*ls', which is selected from a different column '%.*ls' in table '%.*ls'. Change the indexed view definition so that the partitioning column is the same as the table's partitioning column.
11406 16 No ALTER TABLE SWITCH statement failed. Source and target partitions have different values for the DATA_COMPRESSION option.
11407 16 No Vardecimal storage format can not be enabled for '%.*ls'. Only Enterprise edition of SQL Server supports vardecimal.
11408 16 No Cannot modify the column '%.*ls' in the table '%.*ls' to add or remove the COLUMN_SET attribute. To change a COLUMN_SET attribute of a column, either modify the table to remove the column and then add the column again, or drop and re-create the table.
11409 16 No Cannot remove the column set '%.*ls' in the table '%.*ls' because the table contains more than 1025 columns. Reduce the number of columns in the table to less than 1025.
11410 16 No Cannot modify the column '%.*ls' in the table '%.*ls' to a sparse column because the column has a default or rule bound to it. Unbind the rule or default from the column before designating the column as sparse.
11411 16 No Cannot add the sparse column '%.*ls' to the table '%.*ls' because the data type of the column has a default or rule bound to it. Unbind the rule or default from the data type before adding the sparse column to the table.
11412 16 No ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'.
11413 16 No ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same column set property in tables '%.*ls' and '%.*ls'.
11414 10 No Warning: Option %ls is not applicable to table %.*ls because it does not have a clustered index. This option will be applied only to the table's nonclustered indexes, if it has any.
11415 16 No Object '%.*ls' cannot be disabled or enabled. This action applies only to foreign key and check constraints.
11418 16 No Cannot %S_MSG table '%.*ls' because the table either contains sparse columns or a column set column which are incompatible with compression.
12002 16 No The requested %S_MSG index on column '%.*ls' of table '%.*ls' could not be created because the column type is not %S_MSG . Specify a column name that refers to a column with a %S_MSG data type.
12003 16 No Could not find spatial tessellation scheme '%.*ls'. Specify a valid tessellation scheme name in your USING clause.
12004 16 No Could not find the default spatial tessellation scheme for the column '%.*ls' on table '%.*ls'. Make sure that the column reference is correct, or specify the extension scheme in a USING clause.
12005 16 No Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax.
12006 16 No Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax.
12007 16 No The CREATE %S_MSG statement is missing the required parameter '%.*ls'. Validate the statement against the index-creation syntax.
12008 16 No Table '%.*ls' does not have a clustered primary key as required by the %S_MSG index. Make sure that the primary key column exists on the table before creating a %S_MSG index.
12009 16 No Could not find the %S_MSG index '%.*ls' on table '%.*ls'. Either no %S_MSG index with this name exists, or a non-%S_MSG index might be using the same name. Fix the index name, avoiding duplicates. If a relational index has the same name, drop the regular relational index.
12010 16 No Only one spatial index hint may appear per table, either as the first or the last hinted index.
12011 16 No The value of parameter '%.*ls' of CREATE %S_MSG must be less than %d.
12012 16 No The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d.
12013 16 No The value of parameter '%.*ls' of CREATE %S_MSG must be greater than the value of parameter '%.*ls'.
12014 16 No The '%.*ls' parameter of CREATE %S_MSG is incompletely defined. If the parameter has more than one part, all the parts must be defined.
12015 16 No The index option %.*ls in the CREATE %S_MSG statement has to appear before the general index options.
12016 16 No Creating a %S_MSG index requires that the primary key in the base table satisfy the following restrictions. The maximum number of primary-key columns is %d. The maximum combined per-row size of the primary-key columns is %d bytes. The primary key on the base table '%.*ls' has %d columns, and contains %d bytes. Alter the base table to satisfy the primary-key restrictions imposed by the %S_MSG index.
12017 10 No The spatial index is disabled or offline
12018 10 No The spatial object is not defined in the scope of the predicate
12019 10 No Spatial indexes do not support the comparand supplied in the predicate
12020 10 No Spatial indexes do not support the comparator supplied in the predicate
12021 10 No Spatial indexes do not support the method name supplied in the predicate
12022 10 No The comparand references a column that is defined below the predicate
12023 10 No The comparand in the comparison predicate is not deterministic
12024 10 No The spatial parameter references a column that is defined below the predicate
12025 10 No Could not find required binary spatial method in a condition
12026 10 No Could not find required comparison predicate
12100 16 No ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION option set to ON. To add FILESTREAM filegroups, you must set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.
12300 Computed columns are not supported with 'construct'.
12301 Nullable columns in the index key are not supported with 'construct'.
12302 Updating columns that are part of the PRIMARY KEY constraint is not supported with 'construct'.
12303 The 'number' clause is not supported with 'construct'.
12304 Using a memory optimized table type that uses the IDENTITY property with any of its columns is not supported when using the type outside the context of a natively compiled stored procedure.
12305 Inline table variables are not supported with 'construct'.
12306 Cursors are not supported with 'construct'.
12307 Default values for parameters in 'construct' must be constants.
12308 Table-valued functions are not supported with 'construct'.
12329 The data types char(n) and varchar(n) using a collation that has a code page other than 1252 are not supported with construct.
12980 16 No Supply either %s or %s to identify the log entries.
12981 16 No You must specify %s when creating a subplan.
12982 16 No Supply either %s or %s to identify the plan or sub-plan to be run.

Errors 13,000 to 13,999

ErrorSeverityEvent LoggedDescription
13001 16 No file name
13002 16 No audit
13003 16 No audit specification
13004 16 No audit name
13008 0 No receive
13010 0 No read
13012 0 No a USE database statement
13013 0 No a procedure, function or trigger
13014 0 No indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations
13015 0 No spatial index operations
13016 0 No an INTO clause
13018 0 No a COMPUTE clause
13019 0 No a SELECT INTO statement
13020 0 No option
13021 0 No offset option
13022 0 No statistics option
13024 0 No function name
13025 0 No varbinary (128) NOT NULL
13026 0 No parameter
13027 0 No convert specification
13028 0 No index
13029 0 No table
13030 0 No database
13031 0 No procedure
13032 0 No trigger
13033 0 No view
13034 0 No default
13035 0 No rule
13036 0 No system table
13037 0 No unknown type
13038 0 No SET option
13039 0 No column
13040 0 No type
13041 0 No character string
13042 0 No integer
13043 0 No identifier
13044 0 No number
13045 0 No indexes
13047 0 No object
13049 0 No built-in function name
13050 0 No aggregate function
13051 0 No XML INDEX
13052 0 No CLR type
13053 0 No xml schema collection
13054 0 No EXTENDED INDEX
13055 0 No SPATIAL INDEX
13056 0 No spatial
13057 0 No a planguide batch
13058 0 No geometry
13059 0 No conversation priority
13076 0 No an assignment
13077 0 No a cursor declaration
13078 0 No replication filter
13079 0 No variable assignment
13080 0 No statistics
13081 0 No file
13082 0 No filegroup
13083 0 No server
13084 0 No write
13085 0 No function
13086 0 No database collation
13087 0 No drop
13088 0 No alter
13089 0 No message type
13090 0 No contract
13092 0 No service
13093 0 No queue
13094 0 No table valued function
13095 0 No event notification
13096 0 No synonym
13097 0 No lock
13098 0 No thread
13099 0 No communication buffer
13100 0 No Common Language Runtime critical section
13101 0 No partition scheme
13102 10 No DETACH
13103 0 No HASH
13104 0 No RANGE
13105 0 No create
13106 0 No route
13107 0 No remote service binding
13108 0 No Initiator
13109 0 No Target
13110 0 No host synchronization object
13111 0 No generic waitable object
13112 0 No application role
13113 0 No schema
13114 0 No user
13115 0 No login
13116 0 No certificate
13117 0 No role
13118 0 No find
13119 0 No endpoint
13120 0 No sql:variable
13121 0 No sql:column
13122 0 No XML namespace
13123 0 No assembly
13124 0 No fulltext catalog
13125 16 No execute as
13126 16 No symmetric key
13127 16 No principal
13128 16 No security descriptor
13129 16 No hypothetical index
13130 16 No nonclustered index
13131 16 No credential
13132 0 No transfer
13133 0 No Cumulative wait time (ms) per second
13134 0 No Waits started per second
13135 0 No Waits in progress
13136 0 No Average wait time (ms)
13137 0 No Cumulative execution time (ms) per second
13138 0 No Execs started per second
13139 0 No Execs in progress
13140 0 No Average execution time (ms)
13141 16 No asymmetric key
13142 0 No an INSERT SELECT statement
13143 16 No partition function
13144 16 No partition scheme
13145 16 No encryption
13146 16 No signature
13147 16 No password
13148 16 No rename
13149 16 No end dialog
13150 16 No END CONVERSATION WITH ERROR
13151 16 No MOVE CONVERSATION
13152 16 No receive sequenced message
13153 16 No receive end conversation
13154 16 No receive end conversation with error
13155 16 No receive broker error
13156 16 No receive message acknowledgement
13157 16 No terminate conversation
13158 16 No broker error
13159 16 No countersignature
13160 16 No BEGIN CONVERSATION TIMER
13161 16 No fire conversation timer
13162 16 No END CONVERSATION WITH CLEANUP
13163 16 No BEGIN DIALOG CONVERSATION
13164 16 No SEND
13165 16 No conversation
13166 16 No conversation group
13167 16 No system
13168 16 No Service Broker
13169 16 No Database Mirroring
13170 0 No table or indexed view
13171 16 No conversation handle
13172 16 No GET CONVERSATION GROUP
13173 16 No master key
13174 16 No another assembly with same SQL name is already present in the current database
13175 16 No version, culture or public key mismatch
13176 0 No component
13177 16 No IL compilation
13178 16 No Inproc data access
13179 16 No DDL operations
13180 16 No execution cache cleanup
13181 16 No unspecified operation
13182 16 No dialog
13183 10 No The certificate's private key cannot be found
13184 10 No The certificate's private key size is incompatible with the crypto provider
13185 10 No The certificate's public key size is incompatible with the crypto provider
13186 10 No The certificate's private key size is incompatible with the encrypted key exchange key
13187 10 No The certificate's public key size is incompatible with the security header's signature
13188 10 No The certificate's private key is password protected
13189 10 No The key exchange key has an invalid size after being decrypted with the certificate private key
13190 10 No The database principal used to lookup the cert is invalid
13191 10 No The database principal has no mapping to a server principal
13192 10 No The certificate is disabled for BEGIN DIALOG
13193 16 No encryption algorithm
13194 16 No authentication protocol
13195 10 No Certificate not found
13196 10 No Certificate not yet valid
13197 10 No Certificate expired
13198 10 No Certificate is larger than maximum allowed size
13199 10 No message timestamp
13202 10 No TO BROKER INSTANCE
13203 10 No TO SERVICE
13204 10 No FROM BROKER INSTANCE
13205 10 No FROM SERVICE
13206 10 No SERVICE CONTRACT
13207 10 No MESSAGE TYPE
13208 10 No MESSAGE INTEGRITY CHECK
13209 10 No KEY SALT
13210 10 No SESSION KEY
13211 10 No KEY EXCHANGE KEY
13212 10 No SOURCE CERTIFICATE ISSUER NAME
13213 10 No SOURCE CERTIFICATE SERIAL NUMBER
13214 10 No DESTINATION CERTIFICATE ISSUER NAME
13215 10 No DESTINATION CERTIFICATE SERIAL NUMBER
13216 10 No SECURITY HEADER SIGNATURE
13217 10 No MESSAGE BODY
13218 10 No STATEMENT
13219 10 No clustered index
13220 10 No primary xml index
13221 10 No Failover
13222 10 No Auto Failover
13223 10 No Failover from partner
13224 10 No Role Synchronization
13225 10 No Force_Service_Allow_Data_Loss
13226 10 No add
13227 10 No to
13228 10 No from
13229 10 No enable
13230 10 No disable
13231 10 No remap
13232 10 No INSERT
13233 10 No UPDATE
13234 10 No DELETE
13235 10 No WHEN MATCHED
13236 10 No WHEN NOT MATCHED
13237 10 No WHEN NOT MATCHED BY SOURCE
13238 10 No TOP
13239 10 No GROUP BY
13240 10 No HAVING
13241 10 No ORDER BY
13242 10 No COMPUTE
13243 10 No OUTPUT INTO
13244 10 No SELECT
13245 10 No WHERE
13246 10 No unexpected
13254 10 No event
13255 10 No target
13256 10 No event action
13257 10 No event session
13258 10 No event package
13259 10 No event object
13260 10 No event predicate comparator
13261 10 No event attribute or predicate source
13262 10 No customizable attribute
13263 10 No event predicate
13264 10 No predicate source
13265 10 No event attribute
13266 10 No partitioned
13267 10 No not partitioned
13268 10 No resource pool
13269 10 No workload group
13270 10 No resource governor
13271 10 No move
13272 10 No UPDATETEXT
13273 10 No WRITETEXT
13274 10 No torn page (expected signature: 0x%08x; actual signature: 0x%08x)
13275 10 No incorrect checksum (expected: 0x%08x; actual: 0x%08x)
13276 10 No invalid protection option
13277 10 No invalid encryption key
13278 10 No unable to decrypt page
13279 10 No decryption failure (expected: 0x%08x; actual: 0x%08x)
13280 10 No unable to decrypt page due to missing DEK
13281 10 No CREATION_DISPOSITION
13282 10 No PROVIDER_KEY_NAME
13283 10 No key source
13284 10 No ENCRYPTION BY
13285 10 No public key
13286 10 No private key
13287 10 No cryptographic provider
13288 10 No cryptographic provider DLL path
13289 10 No cryptographic provider friendly name
13290 10 No version
13291 10 No guid
13292 10 No create credential for
13293 10 No cryptographic provider key name
13294 10 No key persistence
13295 10 No cryptographic provider key thumbprint length
13296 10 No cryptographic provider key blob length
13297 16 No encryption algorithm tag
13298 16 No name
13299 16 No thumbprint
13301 16 No IV(Initialization Vector) length
13302 16 No bit length
13303 16 No constraint
13373 16 No Anchor record
13374 16 No Page dictionary
13375 16 No Compression information structure
13376 10 No Fulltext Query String
13377 10 No Fulltext Query Language
13378 10 No Fulltext Query Max Keys
13379 10 No fulltext stoplist
13380 10 No Success - Consult EKM Provider for details
13381 10 No Failure - Consult EKM Provider for details
13382 10 No Insufficient Buffer - Consult EKM Provider for details
13383 10 No Not Supported - Consult EKM Provider for details
13384 10 No Object Not Found - Consult EKM Provider for details
13385 10 No Authentication Failure - Consult EKM Provider for details
13386 10 No Invalid Argument - Consult EKM Provider for details
13387 10 No Provider Error - No explanation is available, consult EKM Provider for details
13388 10 No Key Flags
13389 10 No Key Name
13390 10 No Key Type
13400 10 No Extended stored procedure API 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.
13401 10 No Non-ANSI '=' and '=' outer join operators will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use ANSI outer joins instead.
13402 10 No The ability to INSERT NULL values into TIMESTAMP columns 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. Use DEFAULT instead.
13403 10 No The ability to use string literals as column aliases 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. Use AS clause instead.
13404 10 No The ability to use '#' and '##' as the name of temporary tables and stored procedures 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.
13405 10 No The ability to use '@' and names that start with '@@' as Transact-SQL identifiers 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.
13406 10 No The ability to use the DEFAULT keyword as a default value 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.
13407 10 No FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use OPTION (FAST n) instead.
13408 10 No %ls will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
13409 10 No Collation '%ls' will be removed in a future version of SQL Server. Avoid using this collation in new development work, and plan to modify applications that currently use it.

Errors 14,000 to 14,999

ErrorSeverityEvent LoggedDescription
14002 16 No Could not find the 'Sync' subsystem with the task ID %ld.
14003 16 No You must supply a publication name.
14004 16 No %s must be in the current database.
14005 16 No Cannot drop the publication because at least one subscription exists for this publication. Drop all subscriptions to the publication before attempting to drop the publication. If the problem persists, replication metadata might be incorrect; consult Books Online for troubleshooting information.
14006 16 No Could not drop the publication.
14008 11 No There are no publications.
14009 11 No There are no articles for publication '%s'.
14010 16 No The remote server '%s' is not defined as a subscription server. Ensure you specify the server name rather than a network alias.
14011 16 No Unable to mark server '%s' as a non SQL Server subscriber.
14012 16 No The @status parameter value must be either 'active' or 'inactive'.
14013 16 No This database is not enabled for publication.
14014 16 No The synchronization method (@sync_method) must be '[bcp] native', '[bcp] character', 'concurrent', 'concurrent_c', 'database snapshot', or 'database snapshot character'.
14015 16 No The replication frequency (@repl_freq) must be either 'continuous' or 'snapshot'.
14016 16 No The publication '%s' already exists.
14017 16 No Invalid @restricted parameter value. Valid options are 'true' or 'false'.
14018 16 No Could not create the publication.
14019 16 No The @operation parameter value must be either add, drop, or alter.
14020 16 No Could not obtain the column ID for the specified column. Schema replication failed.
14021 16 No The column was not added correctly to the article.
14022 16 No The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'status', 'schema_option', or 'destination_owner'.
14023 16 No The type must be '[indexed view ]logbased[ (manualview|manualfilter|manualboth)]', '[serializable ]proc exec', or '(view|indexed view|proc|func|aggregate|synonym) schema only'.
14024 16 No The value of property 'subscriber_provider' cannot be NULL.
14025 10 No Article update successful.
14026 16 No The value of property 'subscriber_type is not a supported heterogeneous subscriber type. The value must be 1 (ODBC subscriber), or 3 (OLEDB subscriber).
14027 11 No %s does not exist in the current database.
14028 16 No Only user tables, materialized views, and stored procedures can be published as 'logbased' articles.
14029 16 No The vertical partition switch must be either 'true' or 'false'.
14030 16 No The article '%s' exists in publication '%s'.
14031 16 No User tables and views are the only valid synchronization objects.
14032 16 No The value of parameter %s cannot be 'all'. It is reserved by replication stored procedures.
14033 16 No Could not change replication frequency because there are active subscriptions on the publication.
14034 16 No The publication name (@publication) cannot be the keyword 'all'.
14035 16 No The replication option '%s' of database '%s' has already been set to true.
14036 16 No Could not enable database for publishing.
14037 16 No The replication option '%s' of database '%s' has been set to false.
14038 16 No Could not disable database for publishing.
14039 16 No Could not construct column clause for article view. Reduce the number of columns or create the view manually.
14040 16 No The server '%s' is already a Subscriber.
14041 16 No The '%s' property can only be changed if the publication is enabled for heterogeneous subscriptions. The publication is not enabled.
14042 16 No Could not create Subscriber.
14043 16 No The parameter %s passed to stored procedure %s cannot be NULL.
14044 16 No Unable to clear subscriber status for the server.
14045 16 No Unable to update subscriber_type in MSdistribution_agents table.
14046 16 No Could not drop article. A subscription exists on it.
14047 16 No Could not drop %s.
14048 16 No The server '%s' is not a Subscriber.
14049 16 No Stored procedures for replication are the only objects that can be used as a filter.
14050 11 No No subscription is on this publication or article.
14051 16 No The parameter value must be 'sync_type' or 'dest_db'.
14052 16 No The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize with backup", or "initialize from lsn".
14053 16 No The subscription could not be updated at this time.
14054 10 No The subscription was updated successfully.
14055 10 No The subscription does not exist.
14056 16 No The subscription could not be dropped at this time.
14057 16 No The subscription could not be created.
14058 16 No Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.
14059 16 No Materialized view articles cannot be created for publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts.
14060 16 No Subscriber parameters specifying provider properties must be NULL for SQL Server subscribers.
14061 16 No The @pre_creation_cmd parameter value must be 'none', 'drop', 'delete', or 'truncate'.
14062 10 No The Subscriber was dropped.
14063 11 No The remote server does not exist or has not been designated as a valid Subscriber.
14065 16 No The @status parameter value must be 'initiated', 'active', 'inactive', or 'subscribed'.
14066 16 No The previous status must be 'active', 'inactive', or 'subscribed'.
14067 16 No The status value is the same as the previous status value.
14068 16 No The subscription status of the object could not be changed.
14069 16 No Could not update sysarticles. The subscription status could not be changed.
14070 16 No Could not update the distribution database subscription table. The subscription status could not be changed.
14071 16 No Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
14074 16 No The server '%s' is already listed as a Publisher.
14075 16 No The Publisher could not be created at this time.
14076 16 No Could not grant replication login permission to '%s'.
14077 10 No The publication was updated successfully.
14078 16 No The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_internet', 'allow_push', 'allow_pull', 'allow_anonymous', or 'retention'.
14080 16 No The remote server "%s" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
14085 16 No The Subscriber information could not be obtained from the Distributor.
14088 16 No The table '%s' must have a primary key to be published using the transaction-based method.
14089 16 No The clustered index on materialized view '%s' may not contain nullable columns if it is to be published using the transaction-based method.
14090 16 No Error evaluating article synchronization object after column drop. The filter clause for article '%s' must not reference the dropped column.
14091 16 No The @type parameter passed to sp_helpreplicationdb must be either 'pub' or 'sub'.
14092 16 No Could not change article because there is an existing subscription to the article.
14093 16 No Cannot grant or revoke access directly on publication '%s' because it uses the default publication access list.
14094 16 No Could not subscribe to article '%s' because heterogeneous Subscriber '%s' does not support the @pre_creation_cmd parameter value 'truncate'.
14095 16 No The value for the @sync_method parameter is not valid. Could not subscribe to publication '%s' because non-SQL Server Subscriber '%s' only supports values of 'character', 'bcp character', 'concurrent_c', and 'database snapshot character' for the @sync_method parameter.
14096 16 No The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is 'drop'.
14097 16 No The 'status' value must be 'no column names', 'include column names', 'string literals', 'parameters', 'DTS horizontal partitions' or 'no DTS horizontal partitions'.
14098 16 No Cannot drop Distribution Publisher '%s'. The remote Publisher is using '%s' as Distributor. Disable publishing at the Publisher before attempting to drop this relationship.
14099 16 No The server '%s' is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisiting Distributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard.
14100 16 No Specify all articles when subscribing to a publication using concurrent snapshot processing.
14101 16 No The publication '%s' already has a Snapshot Agent defined.
14102 16 No Specify all articles when unsubscribing from a publication using concurrent snapshot processing.
14103 16 No Invalid "%s" value. Valid values are "publisher", "subscriber", or "both".
14105 10 No You have updated the distribution database property '%s' successfully.
14106 16 No Distribution retention periods must be greater than or equal to 0.
14107 10 No The @max_distretention value must be larger than the @min_distretention value.
14108 10 No Removed %ld history records from %s.
14109 10 No The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Windows Authentication).
14110 16 No For stored procedure articles, the @property parameter value must be 'description', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'schema_option', or 'destination_owner'.
14111 16 No The @pre_creation_cmd parameter value must be 'none' or 'drop'.
14112 16 No This procedure can be executed only against table-based articles.
14113 16 No Could not execute '%s'. Check '%s' in the install directory.
14114 16 No The server '%s' is not configured as a Distributor.
14115 16 No The property parameter value must be %s.
14117 16 No '%s' is not configured as a distribution database.
14118 16 No A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema only' article.
14119 16 No Could not add the distribution database '%s'. This distribution database already exists.
14120 16 No Could not drop the distribution database '%s'. This distributor database is associated with a Publisher.
14121 16 No Could not drop the Distributor '%s'. This Distributor has associated distribution databases.
14122 16 No The @article parameter value must be 'all' for immediate_sync publications.
14123 16 No The subscription @sync_type parameter value 'manual' is no longer supported.
14124 16 No A publication must have at least one article before a subscription to it can be created.
14126 16 No You do not have the required permissions to complete the operation.
14128 16 No Invalid @subscription_type parameter value. Valid options are 'push' or 'pull'.
14129 16 No The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication.
14135 16 No There is no subscription on Publisher '%s', publisher database '%s', publication '%s'.
14136 16 No The keyword 'all' is reserved by replication stored procedures.
14137 16 No The @value parameter value must be either 'true' or 'false'.
14138 16 No Invalid option name '%s'.
14139 16 No The replication system table '%s' already exists.
14143 16 No Cannot drop Distributor Publisher '%s'. There are Subscribers associated with it in the distribution database '%s'.
14144 16 No Cannot drop Subscriber '%s'. There are subscriptions for it in the publication database '%s'.
14146 16 No The article parameter '@schema_option' cannot be NULL.
14147 16 No Restricted publications are no longer supported.
14148 16 No Invalid '%s' value. Valid values are 'true' or 'false'.
14149 10 No Removed %ld replication history records in %s seconds (%ld row/secs).
14150 10 No Replication-%s: agent %s succeeded. %s
14151 18 Yes Replication-%s: agent %s failed. %s
14152 10 Yes Replication-%s: agent %s scheduled for retry. %s
14153 10 No Replication-%s: agent %s warning. %s
14154 16 No The Distributor parameter must be '@heartbeat_interval'.
14155 16 No Invalid article ID specified for procedure script generation.
14156 16 No The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format.
14157 10 Yes The subscription created by Subscriber '%s' to publication '%s' has expired and has been dropped.
14158 10 No Replication-%s: agent %s: %s.
14159 16 No Could not change property '%s' for article '%s' because there is an existing subscription to the article.
14160 10 Yes One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and change the expiration threshold value if necessary.
14161 10 Yes The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latency requirement.
14162 10 Yes One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14163 10 Yes One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14164 10 Yes One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14165 10 Yes One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14166 10 No Disable publishing ignored error msg %d, severity %d, state %d: %s.
14167 10 No Subscription expiration
14168 10 No Transactional replication latency
14169 10 No Long merge over dialup connection
14170 10 No Long merge over LAN connection
14171 10 No Slow merge over LAN connection
14172 10 No Slow merge over dialup connection
14173 16 No Failed to set publication parameter %s because it is not supported in Workgroup sku.
14196 10 No The agent has never been run.
14197 10 No Value of %s parameter should be in the set %s
14198 10 No The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct.
14199 10 No The specified job '%s' is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint.
14200 16 No The specified '%s' is invalid.
14201 10 No 0 (all steps) ..
14202 10 No before or after @active_start_time
14203 10 No sp_helplogins [excluding Windows NT groups]
14204 10 No 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions
14205 10 No (unknown)
14206 10 No 0..n seconds
14207 10 No -1 [no maximum], 0..n
14208 10 No 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend]
14209 10 No 0..127 [1 = Sunday .. 64 = Saturday]
14210 10 No notification
14211 10 No server
14212 10 No (all jobs)
14213 10 No Core Job Details:
14214 10 No Job Steps:
14215 10 No Job Schedules:
14216 10 No Job Target Servers:
14217 10 No SQL Server Warning: '%s' has performed a forced defection of TSX server '%s'. Run sp_delete_targetserver at the MSX in order to complete the defection.
14218 10 No hour
14219 10 No minute
14220 10 No second
14221 16 No This job has one or more notifications to operators other than '%s'. The job cannot be targeted at remote servers as currently defined.
14222 16 No Cannot rename the '%s' operator.
14223 16 No Cannot modify or delete operator '%s' while this server is a %s.
14224 10 No Warning: The server name given is not the current MSX server ('%s').
14225 16 No Warning: Could not determine local machine name. This prevents MSX operations from being posted.
14226 10 No %ld history entries purged.
14227 10 No Server defected from MSX '%s'. %ld job(s) deleted.
14228 10 No Server MSX enlistment changed from '%s' to '%s'.
14229 10 No Server enlisted into MSX '%s'.
14230 10 No SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted.
14231 10 No SP_POST_MSX_OPERATION Warning: The specified %s ('%s') is not involved in a multiserver job.
14232 16 No Specify either a job_name, job_id, or an originating_server.
14233 16 No Specify a valid job_id (or 0x00 for all jobs).
14234 16 No The specified '%s' is invalid (valid values are returned by %s).
14235 16 No The specified '%s' is invalid (valid values are greater than 0 but excluding %ld).
14236 10 No Warning: Non-existent step referenced by %s.
14237 16 No When an action of 'REASSIGN' is specified, the New Login parameter must also be supplied.
14238 10 No %ld jobs deleted.
14239 10 No %ld jobs reassigned to %s.
14240 10 No Job applied to %ld new servers.
14241 10 No Job removed from %ld servers.
14242 16 No Only a system administrator can reassign ownership of a job.
14243 10 No Job '%s' started successfully.
14245 16 No Specify either the @name, @id, or @loginname of the task(s) to be deleted.
14250 16 No The specified %s is too long. It must contain no more than %ld characters.
14251 16 No Cannot specify '%s' as the operator to be notified.
14252 16 No Cannot perform this action on a job you do not own.
14253 10 No %ld (of %ld) job(s) stopped successfully.
14254 10 No Job '%s' stopped successfully.
14255 16 No The owner ('%s') of this job is either an invalid login, or is not a valid user of database '%s'.
14256 16 No Cannot start the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
14257 16 No Cannot stop the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
14258 16 No Cannot perform this operation while SQLServerAgent is starting. Try again later.
14260 16 No You do not have sufficient permission to run this command. Contact your system administrator.
14261 16 No The specified %s ('%s') already exists.
14262 16 No The specified %s ('%s') does not exist.
14263 16 No Target server '%s' is already a member of group '%s'.
14264 16 No Target server '%s' is not a member of group '%s'.
14265 24 Yes The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and Windows System and Application event logs for possible causes.
14266 16 No The specified '%s' is invalid (valid values are: %s).
14267 16 No Cannot add a job to the '%s' job category.
14268 16 No There are no jobs at this server that originated from server '%s'.
14269 16 No Job '%s' is already targeted at server '%s'.
14270 16 No Job '%s' is not currently targeted at server '%s'.
14271 16 No A target server cannot be named '%s'.
14272 16 No Object-type and object-name must be supplied as a pair.
14273 16 No You must provide either @job_id or @job_name (and, optionally, @schedule_name), or @schedule_id.
14274 16 No Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.
14275 16 No The originating server must be either local server or MSX server.
14276 16 No '%s' is a permanent %s category and cannot be deleted.
14277 16 No The command script does not destroy all the objects that it creates. Revise the command script.
14278 16 No The schedule for this job is invalid (reason: %s).
14279 16 No Supply either @job_name, @job_id or @originating_server.
14280 16 No Supply either a job name (and job aspect), or one or more job filter parameters.
14281 10 No Warning: The @new_owner_login_name parameter is not necessary when specifying a 'DELETE' action.
14282 16 No Supply either a date (created or last modified) and a data comparator, or no date parameters at all.
14283 16 No Supply @target_server_groups or @target_servers, or both.
14284 16 No Cannot specify a job ID for a new job. An ID will be assigned by the procedure.
14285 16 No Cannot add a local job to a multiserver job category.
14286 16 No Cannot add a multiserver job to a local job category.
14287 16 No The '%s' supplied has an invalid %s.
14288 16 No %s cannot be before %s.
14289 16 No %s cannot contain '%s' characters.
14290 16 No This job is currently targeted at the local server so cannot also be targeted at a remote server.
14291 16 No This job is currently targeted at a remote server so cannot also be targeted at the local server.
14292 16 No There are two or more tasks named '%s'. Specify %s instead of %s to uniquely identify the task.
14293 16 No There are two or more jobs named '%s'. Specify %s instead of %s to uniquely identify the job.
14294 16 No Supply either %s or %s to identify the job.
14295 16 No Frequency Type 0x2 (OnDemand) is no longer supported.
14296 16 No This server is already enlisted into MSX '%s'.
14297 16 No Cannot enlist into the local machine.
14298 16 No This server is not currently enlisted into an MSX.
14299 16 No Server '%s' is an MSX. Cannot enlist one MSX into another MSX.
14301 16 No Logins other than the current user can only be seen by members of the sysadmin role.
14303 16 No Stored procedure '%s' failed to access registry key.
14304 16 No Stored procedure '%s' can run only on Windows 2000 servers.
14305 16 No Column '%.*ls' does not exist in table '%.*ls'.
14306 16 No The target server (TSX) version is not compatible with the master server (MSX) version (%ld.%ld.%ld).
14307 16 No Access to Integration Services package '%s' is denied.
14350 16 No Cannot initialize COM library because CoInitialize failed.
14351 16 No Cannot complete this operation because an unexpected error occurred.
14352 16 No Cannot find Active Directory information in the registry for this SQL Server instance. Run sp_ActiveDirectory_SCP again.
14353 16 No Cannot determine the service account for this SQL Server instance.
14354 16 No Cannot start the MSSQLServerADHelper service. Verify that the service account for this SQL Server instance has the necessary permissions to start the MSSQLServerADHelper service.
14355 16 No The MSSQLServerADHelper service is busy. Retry this operation later.
14356 16 No The Windows Active Directory client is not installed properly on the computer where this SQL Server instance is running. LoadLibrary failed to load ACTIVEDS.DLL.
14357 16 No Cannot list '%s' in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters.
14359 16 No Active Directory directory service is not enabled on the network, or it is not supported by the operating system.
14360 16 No %s is already configured as TSX machine
14362 16 No The MSX server must be running the Standard or Enterprise edition of SQL Server
14363 16 No The MSX server is not prepared for enlistments [there must be an operator named 'MSXOperator' defined at the MSX]
14364 16 No The TSX server is not currently enlisted
14365 16 No Specify a valid schedule_uid.
14366 16 No Only members of sysadmin role can modify the owner of a schedule.
14367 16 No One or more schedules were not deleted because they are being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job.
14368 16 No Schedule "%s" was not deleted because it is being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job.
14369 16 No The schedule ID "%s" is used by more than one job. Specify the job_id.
14370 16 No The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX).
14371 16 No There are two or more schedules named "%s". Specify %s instead of %s to uniquely identify the schedule.
14372 16 No The schedule was not deleted because it is being used by one or more jobs.
14373 16 No Supply either %s or %s to identify the schedule.
14374 16 No The specified schedule name "%s" is not associated with the job "%s".
14375 16 No More than one schedule named "%s" is attached to job "%s". Use "sp_update_schedule" to update schedules.
14376 16 No More than one schedule named "%s" is attached to job "%s". Use "sp_detach_schedule" to remove schedules from a job.
14377 16 No The schedule was not attached to the specified job. The schedule owner and the job owner must be the same or the operation must be performed by a sysadmin.
14378 16 No @sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility
14379 16 No Table '%s' foreign key 'originating_server_id' does not have a matching value in the referenced view 'dbo.sysoriginatingservers_view'.
14380 16 No Field 'originating_server_id' in table sysoriginatingservers is being referenced by either sysjobs or sysschedules.
14390 16 No Only members of role sysadmin can specify the %s parameter.
14391 16 No Only owner of a job or members of sysadmin role can detach a schedule.
14392 16 No Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can purge history of the job.
14393 16 No Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can start and stop the job.
14394 16 No Only owner of a job schedule or members of sysadmin role can modify or delete the job schedule.
14395 16 No '%s' is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy.
14396 16 No Only members of sysadmin server role can modify multi-server jobs
14397 16 No Only members of sysadmin server role can start/stop multi-server jobs
14398 16 No Only members of sysadmin server role can create multi-server jobs
14410 16 No You must supply either a plan_name or a plan_id.
14411 16 No Cannot delete this plan. The plan contains enlisted databases.
14412 16 No The destination database is already part of a log shipping plan.
14413 16 No This database is already log shipping.
14414 16 No A log shipping monitor is already defined.
14415 16 No The user name cannot be null when using SQL Server authentication.
14416 16 No This stored procedure must be run in msdb.
14417 16 No Cannot delete the monitor server while databases are participating in log shipping.
14418 16 No The specified @backup_file_name was not created from database '%s'.
14419 16 No The specified @backup_file_name is not a database backup.
14420 16 Yes The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.
14421 16 Yes The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.
14422 16 No Supply either @plan_id or @plan_name.
14423 16 No Other databases are enlisted on this plan and must be removed before the plan can be deleted.
14424 16 No The database '%s' is already involved in log shipping.
14425 16 No The database '%s' does not seem to be involved in log shipping.
14426 16 No A log shipping monitor is already defined. Call sp_define_log_shipping_monitor with @delete_existing = 1.
14427 16 No A user name is necessary for SQL Server security.
14428 16 No Could not remove the monitor as there are still databases involved in log shipping.
14429 16 No There are still secondary servers attached to this primary.
14430 16 No Destination path %s is not valid. Unable to list directory contents. Specify a valid destination path.
14440 16 No Could not set single user mode.
14441 16 No Role change succeeded.
14442 16 No Role change failed.
14450 16 No The specified @backup_file_name was not taken from database '%s'.
14451 16 No The specified @backup_file_name is not a database backup.
14500 16 No Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query.
14501 16 No An alert ('%s') has already been defined on this condition.
14502 16 No The @target_name parameter must be supplied when specifying an @enum_type of 'TARGET'.
14503 16 No The @target_name parameter should not be supplied when specifying an @enum_type of 'ALL' or 'ACTUAL'.
14504 16 No '%s' is the fail-safe operator. You must make another operator the fail-safe operator before '%s' can be dropped.
14505 16 No Specify a null %s when supplying a performance condition.
14506 16 No Cannot set alerts on message ID %ld.
14507 16 No A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'.
14508 16 No Specify both @wmi_namespace and @wmi_query.
14509 16 No Specify a valid %s when supplying a @wmi_namespace.
14510 16 No Specify a null %s when supplying a @wmi_namespace.
14511 16 No The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that the query has the correct syntax.
14512 16 No Specify a valid %s when supplying a @wmi_query.
14513 10 No Analysis query subsystem
14514 10 No Analysis command subsystem
14515 16 No Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name.
14516 16 No Proxy (%d) is not allowed for subsystem "%s" and user "%s". Grant permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy.
14517 16 No A proxy account is not allowed for a Transact-SQL subsystem.
14518 16 No Cannot delete proxy (%d). It is used by at least one jobstep. Change this proxy for all jobsteps first.
14519 16 No Only one of @login_name, @fixed_server_role, or @msdb_role should be specified.
14520 16 No %s is not a valid SQL Server standard login, Windows NT user, Windows NT group, or msdb database role.
14521 16 No %s is not a valid SQL Server fixed server role, Windows NT user, or Windows NT group.
14522 16 No '"%s" is not a valid role of an msdb database, Windows NT user, or Windows NT group.
14523 16 No %s has not been granted permission to use proxy "%s".
14524 16 No Supply either %s or %s.
14525 16 No Only members of sysadmin role are allowed to update or delete jobs owned by a different login.
14526 16 No The specified category "%s" does not exist for category class "%s".
14527 16 No Job "%s" cannot be used by an alert. It should first be associated with a server by calling sp_add_jobserver.
14528 16 No Job "%s" has no steps defined.
14529 16 No Proxy "%s" is not a valid Windows user.
14530 16 No The Transact-SQL subsystem cannot be executed under the context of a proxy account.
14531 16 No Permission to access proxy already granted. Verify current permissions assignments.
14532 16 No Supply both %s and %s, or none of them.
14533 16 No Use either a proxy or user_domain, user_name, or user_password parameter.
14534 16 No All user_domain, user_name, and user_password parameters should be defined.
14535 16 No The user_domain, user_name, and user_password parameters can be specified only for replication subsystems.
14536 16 No Only members of the sysadmin role can specify a "%s" parameter.
14537 16 No Execution in the context of disabled proxy (proxy_id = %d) is not allowed. Contact your system administrator.
14538 10 No SSIS package execution subsystem
14539 16 No Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX.
14540 16 No Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX.
14541 16 No The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX.
14542 16 No It is invalid for any TSQL step of a multiserver job to have a non-null %s value.
14543 16 No Login '%s' owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role.
14544 16 No This job is owned by '%s'. Only a job owned by a member of the %s role can be a multiserver job.
14545 16 No The %s parameter is not valid for a job step of type '%s'.
14546 16 No The %s parameter is not supported on Windows 95/98 platforms.
14547 10 No Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s.
14548 10 No Target server '%s' does not have any jobs assigned to it.
14549 10 No (Description not requested.)
14550 10 No Command-Line Subsystem
14551 10 No Replication Snapshot Subsystem
14552 10 No Replication Transaction-Log Reader Subsystem
14553 10 No Replication Distribution Subsystem
14554 10 No Replication Merge Subsystem
14555 10 No Active Scripting Subsystem
14556 10 No Transact-SQL Subsystem
14557 10 No [Internal]
14558 10 No (encrypted command)
14559 10 No (append output file)
14560 10 No (include results in history)
14561 10 No (normal)
14562 10 No (quit with success)
14563 10 No (quit with failure)
14564 10 No (goto next step)
14565 10 No (goto step)
14566 10 No (idle)
14567 10 No (below normal)
14568 10 No (above normal)
14569 10 No (time critical)
14570 10 No (Job outcome)
14571 10 No No description available.
14572 10 No @freq_interval must be at least 1 for a daily job.
14573 10 No @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job.
14574 10 No @freq_interval must be between 1 and 31 for a monthly job.
14575 10 No @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10).
14576 10 No @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job.
14577 10 No @freq_recurrence_factor must be at least 1.
14578 10 No Starts whenever the CPU usage has remained below %ld percent for %ld seconds.
14579 10 No Automatically starts when SQLServerAgent starts.
14580 10 No job
14581 10 No Replication Transaction Queue Reader Subsystem
14582 16 No Only a sysadmin can specify '@output_file_name' parameter for a jobstep.
14583 16 No Only a sysadmin can specify '@database_user_name' parameter.
14585 16 No Only the owner of DTS Package '%s' or a member of the sysadmin role may reassign its ownership.
14586 16 No Only the owner of DTS Package '%s' or a member of the sysadmin role may create new versions of it.
14587 16 No Only the owner of DTS Package '%s' or a member of the sysadmin role may drop it or any of its versions.
14588 10 No ID.VersionID =
14589 10 No [not specified]
14590 16 No DTS Package '%s' already exists with a different ID in this category.
14591 16 No SSIS folder '%s' already exists in the specified parent folder.
14592 16 No DTS Category '%s' was found in multiple parent categories. You must uniquely specify the category to be dropped.
14593 16 No SSIS folder '%s' contains packages and/or other folders. You must drop these first.
14594 10 No DTS Package
14595 16 No DTS Package '%s' exists in different categories. You must uniquely specify the package.
14596 16 No DTS Package '%s' exists in another category.
14597 16 No DTS Package ID '%s' already exists with a different name.
14598 16 No Cannot drop the Local, Repository, or LocalDefault DTS categories.
14599 10 No Name
14600 16 No Proxy "%s" has not been granted permission to use subsystem "%s".
14601 16 No Operator "%s" is not enabled and therefore cannot receive notifications.
14602 16 No Operator "%s" does not have an e-mail address specified.
14603 16 No Database Mail is not properly configured.
14604 16 No Both %s parameters (id and name) cannot be NULL
14605 16 No Both %s parameters (id and name) do not point to the same object
14606 16 No %s id is not valid
14607 16 No %s name is not valid
14608 16 No Either %s or %s parameter needs to be supplied
14609 16 No Mail database to user database association does not exist and therefore cannot be updated
14610 16 No Either @profile_name or @description parameter needs to be specified for update
14611 16 No Account sequence number must be supplied for update
14612 16 No Each principal should have at least one default profile
14614 16 No %s is not a valid mailserver_type
14615 16 No The @username parameter needs to be supplied if the @password is supplied.
14616 16 No Unable to retrieve the newly created credential [%s] from the credential store.
14617 16 No Mail host database specified is invalid
14618 16 No Parameter '%s' must be specified. This parameter cannot be NULL.
14619 16 No Received an error on the Service Broker conversation with Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for information.
14620 16 No The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information.
14621 16 No Parameter @attachmentencoding does not support the value "%s". The attachment encoding must be "MIME".
14622 16 No Parameter @importance does not support the value "%s". Mail importance must be one of LOW, NORMAL, or HIGH.
14623 16 No Parameter @sensitivity does not support the value "%s". Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL.
14624 16 No At least one of the following parameters must be specified. "%s".
14265 16 No Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query. A query must be specified to attach the results of the query.
14626 16 No Parameter @mailformat does not support the value "%s". The mail format must be TEXT or HTML.
14627 16 No Received error %d while sending a message as part of the %s operation. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information.
14628 16 No The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon ";".
14629 16 No There is no configuration parameter named "%s", or the value provided is not of the correct data type.
14630 16 No Database Mail is not permitted to send files with the file extension %s.
14631 16 No The current user ('%s') either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonate the user specified in the parameter @execute_query_as. Only members of the sysadmin fixed server role and members of the db_owner fixed database role can impersonate another user.
14632 16 No The user name %s specified in @execute_query_as is invalid. There is no user by that name.
14633 16 No The database name "%s" specified in @execute_query_database is invalid. There is no database by that name.
14634 10 No Warning: %s'
14635 10 No Mail queued.
14636 16 No No global profile is configured. Specify a profile name in the @profile_name parameter.
14637 10 No Activation failure.
14638 10 No Activation successful.
14639 10 No The mail queue was started by login "%s".
14640 10 No The mail queue stopped by login "%s".
14641 16 No Mail not queued. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
14642 10 No Default attachment encoding
14643 10 No Default dialog lifetime
14644 10 No Default maximum file size
14645 10 No Extensions not allowed in outgoing mails
14646 10 No Number of retry attempts for a mail server
14647 10 No Delay between each retry attempt to mail server
14648 10 No Minimum process lifetime in seconds
14649 16 No Unable to test profile. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
14650 16 No Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
14651 16 No Unable to test profile. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
14652 16 No Invalid message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
14653 16 No Invalid %s value received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
14654 10 No Unexpected message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
14655 16 No Invalid XML message format received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
14657 16 No Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded.
14658 16 No Failed to retrieve SQLPath for syssubsystems population.
14659 16 No Failed to retrieve VerSpecificRootDir for syssubsystems population.
14660 16 No Database Compatibility Level is too low. Compatibility Level must be Version80 or higher.
14661 16 No Query execution failed: %s
14662 10 No mailitem_id on conversation %s was not found in the sysmail_send_retries table. This mail item will not be sent.
14663 10 No Mail Id %d has exceeded the retry count. This mail item will not be sent.
14664 16 No Database Mail logging level: normal - 1, extended - 2 (default), verbose - 3
14665 10 No Mail items deletion is initiated by user "%s". %d items deleted.
14666 16 No User name cannot be supplied when using default credentials
14667 16 No Mail Id %d has been deleted from sysmail_mailitems table. This mail will not be sent.
14668 16 No Deleting profile %s failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of the profile.
14670 16 No Cannot delete the active collection set '%s'. Stop the collection set and then try to delete it again.
14671 16 No Cannot update the name or the parameters of the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to update the collection item again.
14672 16 No Cannot delete the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to delete the collection item again.
14673 16 No Cannot delete the collector type '%s'. Delete all collection items associated with this collector type and then try to delete it again.
14674 16 No Cannot upload data for the inactive collection set '%s'. Start the collection set and then try to upload the data again.
14675 16 No Cannot update the name, target, proxy_id, logging_level, or collection_mode, or add collection item to the active collection set '%s'. Stop the collection set and then try to update it again.
14676 16 No The user does not have permission to change '%s'. The user must be a member of data collector role '%s'.
14677 16 No The user does not have permission to perform this operation. The user must be a member of data collector role '%s'.
14678 16 No SQL Server Trace with id %d has been stopped and closed by external user. SQL Server Trace collector will attempt to re-create the trace.
14679 16 No The specified %s (%s) is not valid in this data warehouse.
14680 16 No Management Data Warehouse database can only be installed on an instance of SQL Server 2008 or higher.
14681 16 No Cannot perform this procedure when the collector is disabled. Enable the collector and then try again.
14682 16 No The state of the collection set has changed, but it will not start or stop until the collector is enabled.
14683 16 No A collection set in cached mode requires a schedule.
14684 16 No Caught error#: %d, Level: %d, State: %d, in Procedure: %s, Line: %d, with Message: %s
14685 16 No Collection set: '%s' does not contain any collection items, so starting the collection set will have no effect.
14686 16 No The MDWInstance and MDWDatabase parameters of the configuration store cannot be null.
14687 16 No Invalid value (%d) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload failures), 0 (cache no upload data), N (cache data from N previous upload failures, where N >= 1)
14688 16 No A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent.
14689 16 No A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and configure the management data warehouse.
14690 16 No Cannot perform this procedure when the collector is enabled. Disable the collector and then try again.
14691 16 No The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data.
14692 16 No Insufficient privileges to start collection set: '%s'. Only a member of the 'sysadmin' fixed server role can start a collection set without a SQL Server Agent proxy. Attach a SQL Server Agent proxy to the collection set before retrying.
14693 16 No A collection set cannot start without a schedule. Specify a schedule for the collection set.
14694 16 No Cannot upload data on-demand for the collection set '%s' in non-cached mode.
14695 16 No Cannot collect data on-demand for the collection set '%s' in cached mode.
14696 16 No Cannot update or delete a system collection set, or add new collection items to it.
14697 16 No Unable to convert showplan to XML. Error #%d on Line %d: %s
14698 10 No PowerShell Subsystem
14700 10 No Collects data about the disk and log usage for all databases.
14701 10 No Disk Usage
14702 10 No Disk Usage - Data Files
14703 10 No Disk Usage - Log Files
14704 10 No Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource bottlenecks, and Database Engine activity.
14705 10 No Server Activity
14706 10 No Server Activity - DMV Snapshots
14707 10 No Server Activity - Performance Counters
14708 10 No Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis of poor performing queries in relation to overall SQL Server Database Engine activity.
14709 10 No Query Statistics
14710 10 No Query Statistics - Query Activity
14711 10 No Changes to SQL dumper configuration will take effect when the collection set is restarted. To perform an immediate dump, use the dtutil /dump option.
14712 16 No Only dbo or members of dc_admin can install or upgrade instmdw.sql. Contact an administrator with sufficient permissions to perform this operation.
14713 21 No A management data warehouse cannot be installed to SQL Server Express Edition.
14714 16 No Attempting to upgrade a Management Data Warehouse of newer version '%s' with an older version '%s'. Upgrade aborted.

Errors 15,000 to 15,999

ErrorSeverityEvent LoggedDescription
15001 16 No Object '%ls' does not exist or is not a valid object for this operation.
15002 16 No The procedure '%s' cannot be executed within a transaction.
15003 16 No Only members of the %s role can execute this stored procedure.
15004 16 No Name cannot be NULL.
15005 10 No Statistics for all tables have been updated.
15006 16 No '%s' is not a valid name because it contains invalid characters.
15007 16 No '%s' is not a valid login or you do not have permission.
15008 16 No User '%s' does not exist in the current database.
15009 16 No The object '%s' does not exist in database '%s' or is invalid for this operation.
15010 16 No The database '%s' does not exist. Supply a valid database name. To see available databases, use sys.databases.
15011 16 No Database option '%s' does not exist. Specify a valid database option.
15012 16 No The device '%s' does not exist. Use sys.backup_devices to show available devices.
15013 10 No Table '%s': No columns without statistics found.
15014 16 No The role '%s' does not exist in the current database.
15015 16 No The server '%s' does not exist. Use sp_helpserver to show available servers.
15016 16 No The default '%s' does not exist.
15017 16 No The rule '%s' does not exist.
15018 10 No Table '%s': Creating statistics for the following columns:
15019 16 No The extended stored procedure '%s' does not exist.
15020 10 No Statistics have been created for the %d listed columns of the above tables.
15021 16 No Invalid value given for parameter %s. Specify a valid parameter value.
15022 16 No The specified user name is already aliased.
15023 16 No User, group, or role '%s' already exists in the current database.
15025 16 No The server principal '%s' already exists.
15026 16 No Logical device '%s' already exists.
15028 16 No The server '%s' already exists.
15032 16 No The database '%s' already exists. Specify a unique database name.
15033 16 No '%s' is not a valid official language name.
15034 16 No The application role password must not be NULL.
15036 16 No The data type '%s' does not exist or you do not have permission.
15040 16 No User-defined error messages must have an ID greater than 50000.
15041 16 No User-defined error messages must have a severity level between 1 and 25.
15042 10 No The @with_log parameter is ignored for messages that are not us_english version.
15043 16 No You must specify 'REPLACE' to overwrite an existing message.
15044 16 No The type "%s" is an unknown backup device type. Use the type "disk" or "tape".
15045 16 No The logical name cannot be NULL.
15046 16 No The physical name cannot be NULL.
15048 10 No Valid values of the database compatibility level are %d, %d, or %d.
15049 11 No Cannot unbind from '%s'. Use ALTER TABLE DROP CONSTRAINT.
15050 11 No Cannot bind default '%s'. The default must be created using the CREATE DEFAULT statement.
15051 11 No Cannot rename the table because it is published for replication.
15053 16 No Objects exist which are not owned by the database owner.
15054 10 No The current compatibility level is %d.
15056 10 No The suspect flag on the database "%s" is already reset.
15057 16 No List of %s name contains spaces, which are not allowed.
15058 16 No List of %s has too few names.
15059 16 No List of %s has too many names.
15060 16 No List of %s names contains name(s) which have '%s' non-alphabetic characters.
15061 16 No The add device request was denied. A physical device named "%s" already exists. Only one backup device may refer to any physical device name.
15062 16 No The guest user cannot be mapped to a login name.
15063 16 No The login already has an account under a different user name.
15065 16 No All user IDs have been assigned.
15066 16 No A default-name mapping of a remote login from remote server '%s' already exists.
15068 16 No A remote user '%s' already exists for remote server '%s'.
15069 16 No One or more users are using the database. The requested operation cannot be completed.
15070 10 No Object '%s' was successfully marked for recompilation.
15071 16 No Usage: sp_addmessage <msgnum>,<severity>,<msgtext> [,<language> [,FALSE | TRUE [,REPLACE]]]
15072 16 No Usage: sp_addremotelogin remoteserver [,loginname [,remotename]]
15074 10 No Warning: You must recover this database prior to access.
15076 16 No Default, table, and user data types must be in the current database.
15077 16 No Rule, table, and user data type must be in the current database.
15078 16 No The table or view must be in the current database.
15079 10 No Queries processed: %d.
15080 16 No Cannot use parameter %s for a Windows login.
15081 16 No Membership of the public role cannot be changed.
15083 16 No Physical data type '%s' does not accept a collation
15084 16 No The column or user data type must be in the current database.
15085 16 No Usage: sp_addtype name, 'data type' [,'NULL' | 'NOT NULL']
15096 16 No Could not find object '%ls' or you do not have required permission or the object is not valid for adding extended property.
15097 16 No The size associated with an extended property cannot be more than 7,500 bytes.
15098 16 No The name change cannot be performed because the SID of the new name does not match the old SID of the principal.
15099 16 No The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is OFF.
15100 16 No Usage: sp_bindefault defaultname, objectname [, 'futureonly']
15101 16 No Cannot bind a default to a computed column, a sparse column, or to a column of the following data types: timestamp, varchar(max), nvarchar(max), varbinary(max), xml, or CLR type.
15102 16 No Cannot bind a default to an identity column.
15103 16 No Cannot bind a default to a column created with or altered to have a default value.
15104 16 No You do not own a table named '%s' that has a column named '%s'.
15106 16 No Usage: sp_bindrule rulename, objectname [, 'futureonly']
15107 16 No Cannot bind a rule to a computed column, a sparse column, or to a column of the following data types: text, ntext, image, timestamp, varchar(max), nvarchar(max), varbinary(max), xml, or user-defined data type.
15108 16 No sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. Use CREATE TYPE for this purpose.
15109 16 No Cannot change the owner of the master, model, tempdb or distribution database.
15110 16 No The proposed new database owner is already a user or aliased in the database.
15112 11 No The third parameter for table option 'text in row' is invalid. It should be 'on', 'off', '0', or a number from 24 through 7000.
15113 16 No Too many failed login attempts. This account has been temporarily locked as a precaution against password guessing. A system administrator can unlock this login with the UNLOCK clause of ALTER LOGIN.
15114 16 No Password validation failed. The password for the user is too recent to change.
15115 16 No Password validation failed. The password cannot be used at this time.
15116 16 No Password validation failed. The password does not meet Windows policy requirements because it is too short.
15117 16 No Password validation failed. The password does not meet Windows policy requirements because it is too long.
15118 16 No Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.
15119 16 No Password validation failed. The password does not meet the requirements of the password filter DLL.
15120 16 No An unexpected error occurred during password validation.
15121 16 No An error occurred during the execution of %ls. A call to '%ls' failed with error code: '%d'.
15122 16 No The CHECK_EXPIRATION option cannot be used when CHECK_POLICY is OFF.
15123 16 No The configuration option '%s' does not exist, or it may be an advanced option.
15124 16 No The configuration option '%s' is not unique.
15125 16 No Trigger '%s' is not a trigger for '%s'.
15127 16 No Cannot set the default language to a language ID not defined in syslanguages.
15128 16 No The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned OFF when MUST_CHANGE is ON.
15129 16 No '%d' is not a valid value for configuration option '%s'.
15130 16 No There already exists a '%s' trigger for '%s'.
15131 16 No Usage: sp_dbremove <dbname> [,dropdev]
15133 16 No INSTEAD OF trigger '%s' cannot be associated with an order.
15134 16 No No alias exists for the specified user.
15135 16 No Object is invalid. Extended properties are not permitted on '%s', or the object does not exist.
15136 16 No The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped.
15137 16 No An error occurred during the execution of sp_xp_cmdshell_proxy_account. Possible reasons: the provided account was invalid or the '%.*ls' credential could not be created. Error code: '%d'.
15138 16 No The database principal owns a %S_MSG in the database, and cannot be dropped.
15141 16 No The server principal owns one or more %S_MSG(s) and cannot be dropped.
15143 16 No '%s' is not a valid option for the @updateusage parameter. Enter either 'true' or 'false'.
15144 16 No The role has members. It must be empty before it can be dropped.
15145 16 No An implicit %S_MSG creation has failed. Reason: The %S_MSG may have been dropped or its name may already be in use.
15146 16 No An encryption password must be provided to encrypt the private key of this %S_MSG.
15147 16 No No decryption password should be provided because the private key of this %S_MSG is encrypted by a master key.
15148 16 No The data type or table column '%s' does not exist or you do not have permission.
15149 16 No Principal doesn't exist or doesn't have sufficient privileges.
15150 16 No Cannot %S_MSG the %S_MSG '%.*ls'.
15151 16 No Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission.
15152 16 No Cannot update user instances. Reason: %ls. Error code: 0x%x.
15153 16 No The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '%.*ls' credential exists and contains valid information.
15154 16 No The database principal owns an %S_MSG and cannot be dropped.
15155 16 No The server principal owns a %S_MSG and cannot be dropped.
15156 16 No The password that you specified is too long. The password should have no more than %d characters.
15157 16 No Setuser failed because of one of the following reasons: the database principal '%.*ls' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.
15158 16 No Cannot initialize security.
15159 16 No Maximum impersonation nesting level exceeded (limit %d)..
15160 16 No Cannot issue impersonation token from non-primary impersonation context or for non-Windows user.
15161 16 No Cannot set application role '%.*ls' because it does not exist or the password is incorrect.
15162 16 No Unexpected error while creating impersonation token.
15163 16 No Invalid timeout value. Valid timeout is between 1 and 7200 sec.
15164 16 No '%.*ls' is not a valid login or cannot be issued impersonation token.
15165 16 No Could not find object '%ls' or you do not have permission.
15166 10 No Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored.
15167 16 No Cannot generate GUID.
15168 16 No Cannot rename the view '%s' and its columns and indexes because it is a system generated view that was created for optimization purposes.
15169 16 No The server option "%ls" is not available in this edition of SQL Server.
15170 16 No This login is the owner of %ld job(s). You must delete or reassign these jobs before the login can be dropped.
15171 16 No Cannot use the parameter "%s" for a certificate or asymmetric key login.
15172 16 No FallBack certificate must be created or dropped in master database in single user mode.
15173 16 No Login '%s' has granted one or more permission(s). Revoke the permission(s) before dropping the login.
15174 16 No Login '%s' owns one or more database(s). Change the owner of the database(s) before dropping the login.
15175 16 No Login '%s' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login.
15176 16 No The only valid @parameter value is 'WITH_LOG'.
15177 16 No Usage: sp_dropmessage <msg number> [,<language> | 'ALL']
15178 16 No Cannot drop or alter a message with an ID less than 50,000.
15179 16 No The message number %u or specified language version does not exist.
15182 16 No Cannot disable access to the guest user in master or tempdb.
15183 16 No The database principal owns objects in the database and cannot be dropped.
15184 16 No The database principal owns data types in the database and cannot be dropped.
15185 16 No There is no remote user '%s' mapped to local user '%s' from the remote server '%s'.
15186 16 No The server principal is set as the execution context of a trigger or event notification and cannot be dropped.
15187 10 No The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s).
15188 16 No Cannot create an index that does not include all security columns.
15189 16 No Cannot have more than one security column for a table.
15190 16 No There are still remote logins or linked logins for the server '%s'.
15192 16 No Cannot alter or drop the security column of a table.
15195 16 No The MUST_CHANGE option is not supported by this version of Microsoft Windows.
15196 16 No The current security context is non-revertible. The "Revert" statement failed.
15197 16 No There is no text for object '%s'.
15198 16 No The name supplied (%s) is not a user, role, or aliased login.
15199 16 No The current security context cannot be reverted. Please switch to the original database where '%ls' was called and try it again.
15200 16 No There are no remote servers defined.
15201 16 No There are no remote logins for the remote server '%s'.
15202 16 No There are no remote logins defined.
15203 16 No There are no remote logins for '%s'.
15204 16 No There are no remote logins for '%s' on remote server '%s'.
15205 16 No There are no servers defined.
15206 16 No Invalid Remote Server Option: '%s'.
15207 16 No The trusted option in remote login mapping is no longer supported.
15208 16 No The certificate, asymmetric key, or private key file does not exist or has invalid format.
15209 16 No An error occurred during encryption.
15212 16 No Invalid certificate subject. The certificate subject must have between 1 and %d characters.
15213 16 No Warning: The certificate you created has an invalid validity period; its expiration date precedes its start date.
15214 16 No Warning: The certificate you created is expired.
15215 16 No Warning: The certificate you created is not yet valid; its start date is in the future.
15216 16 No '%s' is not a valid option for the @delfile parameter.
15217 16 No Property cannot be updated or deleted. Property '%.*ls' does not exist for '%.*ls'.
15218 16 No Object '%s' is not a table.
15219 16 No Cannot change the owner of an indexed view.
15222 16 No Remote login option '%s' is not unique.
15223 11 No Error: The input parameter '%s' is not allowed to be null.
15224 11 No Error: The value for the @newname parameter contains invalid characters or violates a basic restriction (%s).
15225 11 No No item by the name of '%s' could be found in the current database '%s', given that @itemtype was input as '%s'.
15226 16 No Cannot create CLR types from an XML datatype.
15227 16 No The database '%s' cannot be renamed.
15229 16 No The argument specified for the "%.*ls" parameter of stored procedure sp_db_vardecimal_storage_format is not valid. Valid arguments are 'ON' or 'OFF'.
15230 16 No Error starting user instance. Error code: %d.
15232 16 No A certificate with name '%s' already exists or this certificate already has been added to the database.
15233 16 No Property cannot be added. Property '%.*ls' already exists for '%.*ls'.
15234 16 No Objects of this type have no space allocated.
15236 16 No Column '%s' has no default.
15237 16 No User data type '%s' has no default.
15238 16 No Column '%s' has no rule.
15239 16 No User data type '%s' has no rule.
15240 16 No Cannot write into file '%s'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
15241 16 No Usage: sp_dboption [dbname [,optname [,'true' | 'false']]]
15242 16 No Database option '%s' is not unique.
15243 16 No The option '%s' cannot be changed for the master database.
15244 16 No Only members of the sysadmin role or the database owner may set database options.
15246 16 No Cannot dump the private key of certificate '%s' because the private key cannot be found.
15247 16 No User does not have permission to perform this action.
15248 11 No Either the parameter @objname is ambiguous or the claimed @objtype (%s) is wrong.
15249 11 No Error: Explicit @objtype '%s' is unrecognized.
15250 16 No The database name component of the object qualifier must be the name of the current database.
15251 16 No Invalid '%s' specified. It must be %s.
15252 16 No The primary or foreign key table name must be given.
15253 11 No Syntax error parsing SQL identifier '%s'.
15254 16 No Users other than the database owner or guest exist in the database. Drop them before removing the database.
15255 11 No '%s' is not a valid value for @autofix. The only valid value is 'auto'.
15256 16 No Usage: sp_certify_removable <dbname> [,'auto']
15257 16 No The database that you are attempting to certify cannot be in use at the same time.
15258 16 No The database must be owned by a member of the sysadmin role before it can be removed.
15259 16 No The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys.
15260 16 No The format of the security descriptor string '%s' is invalid.
15261 16 No Usage: sp_create_removable <dbname>,<syslogical>,<sysphysical>,<syssize>,<loglogical>,<logphysical>,<logsize>,<datalogical1>,<dataphysical1>,<datasize1> [,<datalogical2>,<dataphysical2>,<datasize2>...<datalogical16>,<dataphysical16>,<datasize16>]
15262 10 No Invalid file size entered. All files must be at least 1 MB.
15263 16 No A SID in the security descriptor string '%s' could not be found in an account lookup operation.
15264 16 No Could not create the '%s' portion of the database.
15265 16 No An unexpected error has occurred in the processing of the security descriptor string '%s'.
15266 16 No Cannot make '%s' database removable.
15267 16 No A security descriptor with name '%s' already exists.
15268 10 Yes Authentication mode is %s.
15269 16 No Logical data device '%s' not created.
15271 16 No Invalid @with_log parameter value. Valid values are 'true' or 'false'.
15272 10 No The %s '%.*s' is not trusted to execute.
15273 10 No The decryption key is incorrect.
15274 16 No Access to the remote server is denied because the current security context is not trusted.
15276 16 No Cannot provision master key passwords for system databases.
15277 16 No The only valid @parameter_value values are 'true' or 'false'.
15278 16 No Login '%s' is already mapped to user '%s' in database '%s'.
15279 16 No You must add the us_english version of this message before you can add the '%s' version.
15280 16 No All localized versions of this message must be dropped before the us_english version can be dropped.
15281 10 No SQL Server blocked access to %S_MSG '%ls' of component '%.*ls' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of '%.*ls' by using sp_configure. For more information about enabling '%.*ls', see "Surface Area Configuration" in SQL Server Books Online.
15282 10 No A key with name '%.*ls' or user defined unique identifier already exists or you do not have permissions to create it.
15283 16 No The name '%s' contains too many characters.
15284 16 No The database principal has granted or denied permissions to objects in the database and cannot be dropped.
15285 16 No The special word '%s' cannot be used for a logical device name.
15286 16 No Terminating this procedure. The @action '%s' is unrecognized. Try 'REPORT', 'UPDATE_ONE', or 'AUTO_FIX'.
15287 16 No Terminating this procedure. '%s' is a forbidden value for the login name parameter in this procedure.
15288 10 No Please specify one decryptor to decrypt a key.
15289 16 No Terminating this procedure. Cannot have an open transaction when this is run.
15291 16 No Terminating this procedure. The %s name '%s' is absent or invalid.
15292 10 No The row for user '%s' will be fixed by updating its login link to a login already in existence.
15293 10 No Barring a conflict, the row for user '%s' will be fixed by updating its link to a new login.
15294 10 No The number of orphaned users fixed by adding new logins and then updating users was %d.
15295 10 No The number of orphaned users fixed by updating users was %d.
15296 16 No General cryptographic failure.
15297 16 No The certificate, asymmetric key, or private key data is invalid.
15299 16 No The signature of the public key is invalid.
15300 11 No No recognized letter is contained in the parameter value for General Permission Type (%s). Valid letters are in this set: %s .
15301 16 No Collation '%s' is supported for Unicode data types only and cannot be set at either the database or server level.
15302 11 No Database_Name should not be used to qualify owner.object for the parameter into this procedure.
15303 11 No The "user options" config value (%d) was rejected because it would set incompatible options.
15304 16 No The severity level of the '%s' version of this message must be the same as the severity level (%ld) of the us_english version.
15305 16 No The @TriggerType parameter value must be 'insert', 'update', or 'delete'.
15306 16 No Cannot change the compatibility level of replicated or distributed databases.
15307 16 No Could not change the merge publish option because the server is not set up for replication.
15309 16 No Cannot alter the trustworthy state of the model or tempdb databases.
15310 16 Yes Failed to configure user instance on startup. Error updating server metadata.
15311 16 No The file named '%s' does not exist.
15312 16 No The file named '%s' is a primary file and cannot be removed.
15313 10 No The key is not encrypted using the specified decryptor.
15314 10 No Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of Windows.
15315 10 No The key '%.*ls' is not open. Please open the key before using it.
15316 10 No Global temporary keys are not allowed. You can only use local temporary keys.
15317 10 No The master key file does not exist or has invalid format.
15318 10 No All fragments for database '%s' on device '%s' are now dedicated for log usage only.
15319 17 No Error: DBCC DBREPAIR REMAP failed for database '%s' (device '%s').
15320 16 No An error occurred while decrypting %S_MSG '%.*ls' that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation, but data that cannot be decrypted by the old master key will become unavailable.
15321 16 No There was some problem removing '%s' from sys.master_files.
15322 10 No File '%s' was removed from tempdb, and will take effect upon server restart.
15323 16 No The selected index does not exist on table '%s'.
15324 16 No The option %s cannot be changed for the '%s' database.
15325 16 No The current database does not contain a %s named '%ls'.
15326 10 No No extended stored procedures exist.
15327 10 No The database is now offline.
15328 10 No The database is offline already.
15329 16 No The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session before performing this operation. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15330 11 No There are no matching rows on which to report.
15331 11 No The user '%s' cannot take the action auto_fix due to duplicate SID.
15332 10 No The private key is already set for this file. To change it you should drop and re-create the certificate.
15333 11 No Error: The qualified @oldname references a database (%s) other than the current database.
15334 10 No The %S_MSG has a private key that is protected by a user defined password. That password needs to be provided to enable the use of the private key.
15335 11 No Error: The new name '%s' is already in use as a %s name and would cause a duplicate that is not permitted.
15336 16 No Object '%s' cannot be renamed because the object participates in enforced dependencies.
15337 10 No Caution: sys.sql_dependencies shows that other objects (views, procedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly.
15339 10 No Creating '%s'.
15342 10 No There is no private key provisioned for %S_MSG '%.*ls'.
15343 10 No The username and/or password passed in is invalid or the current process does not have sufficient privileges.
15344 16 No Ownership change for %S_MSG is not supported.
15345 16 No An entity of type %S_MSG cannot be owned by a role, a group, or by principals mapped to certificates or asymmetric keys.
15346 16 No Cannot change owner for an object that is owned by a parent object. Change the owner of the parent object instead.
15347 16 No Cannot transfer an object that is owned by a parent object.
15348 16 No Cannot transfer a schemabound object.
15349 16 No Cannot transfer an MS Shipped object.
15350 16 No An attempt to attach an auto-named database for file %.*ls failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
15351 10 No The CLR procedure/function/type being signed refers to an assembly that is not signed either by a strong name or an assembly.
15352 16 No The %S_MSG cannot be dropped because one or more entities are either signed or encrypted using it.
15353 16 No An entity of type %S_MSG cannot be owned by a role, a group, an approle, or by principals mapped to certificates or asymmetric keys.
15354 10 No Usage: sp_detach_db <dbname>, [TRUE|FALSE], [TRUE|FALSE]
15356 16 No The current application role has been dropped. The current security context contains no valid database user context.
15357 16 No The current security context was set by "%ls". It cannot be reverted by statement "%ls".
15358 10 No User-defined filegroups should be made read-only.
15359 16 No Cannot add functional unit '%.*ls' to component '%.*ls'. This unit has been already registered with the component.
15360 16 No An error occurred while trying to load the xpstar dll to read the agent proxy account from LSA.
15361 16 No An error occurred while trying to read the SQLAgent proxy account credentials from the LSA.
15362 16 No An error occurred while trying to create the '%.*ls' credential.
15364 16 Yes Failed to generate a user instance of SQL Server. Only an integrated connection can generate a user instance. The connection will be closed.%.*ls
15365 16 Yes Failed to generate a user instance of SQL Server. Only members of Builtin\Users can generate a user instance. The connection will be closed.%.*ls
15366 16 Yes Failed to generate a user instance of SQL Server due to low memory. The connection will be closed.%.*ls
15367 16 Yes Failed to generate a user instance of SQL Server due to a failure in generating a unique user instance name. The connection will be closed.%.*ls
15368 16 Yes Failed to generate a user instance of SQL Server due to a failure in reading registry keys. The connection will be closed.%.*ls
15369 16 Yes Failed to generate a user instance of SQL Server due to a failure in impersonating the client. The connection will be closed.%.*ls
15370 16 Yes Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.%.*ls
15371 16 Yes Failed to generate a user instance of SQL Server due to a failure in creating user instance event. The connection will be closed.%.*ls
15372 16 Yes Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.%.*ls
15373 16 Yes Failed to generate a user instance of SQL Server due to a failure in obtaining the user instance's process information. The connection will be closed.%.*ls
15374 16 Yes Failed to generate a user instance of SQL Server due to a failure in persisting the user instance information into system catalog. The connection will be closed.%.*ls
15375 16 Yes Failed to generate a user instance of SQL Server due to a failure in making a connection to the user instance. The connection will be closed.%.*ls
15376 16 Yes Failed to generate a user instance of SQL Server. Only the SQL Server Express version lets you generate a user instance. The connection will be closed.%.*ls
15377 16 Yes Failed to configure user instance on startup. Error adding user to sysadmin role.
15378 16 Yes Failed to configure user instance on startup. Error configuring system database entries in MASTER DB.
15380 16 Yes Failed to configure user instance on startup. Error configuring system database paths in MASTER DB.
15381 16 Yes Failed to generate a user instance of SQL Server due to a failure in updating security descriptor on the process of the user instance.
15382 16 Yes Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.%.*ls
15383 16 Yes Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.%.*ls
15384 16 Yes Failed to configure user instance on startup. Error updating Resource Manager ID.
15385 16 No No database principal is defined for sid '%.*ls'.
15386 16 No Another batch in the session is changing security context, new batch is not allowed to start.
15387 11 No If the qualified object name specifies a database, that database must be the current database.
15388 11 No There is no user table matching the input name '%s' in the current database or you do not have permission to access the table.
15389 11 No sp_indexoption is not supported for XML or spatial indexes. Use ALTER INDEX instead.
15390 11 No Input name '%s' does not have a matching user table or indexed view in the current database.
15391 11 No sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option for ALL the indexes.
15392 16 No The specified option '%s' is not supported by this edition of SQL Server and cannot be changed using sp_configure.
15393 16 No An error occurred while decrypting the password for linked login '%.*ls' that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15394 16 No Collation '%s' is not supported by the operating system
15395 11 No The qualified old name could not be found for item type '%s'.
15396 16 No An asymmetric key with name '%s' already exists or this asymmetric key already has been added to the database.
15397 16 No The %S_MSG is not protected by a password. A decryption password cannot be used for this operation.
15398 11 No Only objects in the master database owned by dbo can have the startup setting changed.
15399 11 No Could not change startup option because this option is restricted to objects that have no parameters.
15401 11 No Windows NT user or group '%s' not found. Check the name again.
15402 11 No '%s' is not a fixed server role.
15403 16 No The server principal "%.*ls" does not exist, does not have server access, or you do not have permission.
15404 16 No Could not obtain information about Windows NT group/user '%ls', error code %#lx.
15405 11 No Cannot use the special principal '%s'.
15406 16 No Cannot execute as the server principal because the principal "%.*ls" does not exist, this type of principal cannot be impersonated, or you do not have permission.
15407 11 No '%s' is not a valid Windows NT name. Give the complete name: <domain\username>.
15408 16 No %ls cannot be called in this batch because a simultaneous batch has called it.
15409 11 No '%s' is not a role.
15410 11 No User or role '%s' does not exist in this database.
15411 11 No Database principal or schema '%s' does not exist in this database.
15412 11 No '%s' is not a known fixed role.
15413 11 No Cannot make a role a member of itself.
15414 16 No Cannot set compatibility level because database has a view or computed column that is indexed. These indexes require a SQL Server compatible database.
15416 16 No Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]]
15418 16 No Only members of the sysadmin role or the database owner may set the database compatibility level.
15419 16 No Supplied parameter sid should be binary(16).
15420 16 No The group '%s' does not exist in this database.
15421 16 No The database principal owns a database role and cannot be dropped.
15422 16 No Application roles can only be activated at the ad hoc level.
15425 16 No No server principal is defined for sid '%.*ls'.
15426 16 No You must specify a provider name with this set of properties.
15427 16 No You must specify a provider name for unknown product '%ls'.
15428 16 No You cannot specify a provider or any properties for product '%ls'.
15429 16 No '%ls' is an invalid product name.
15431 16 No You must specify the @rolename parameter.
15432 16 No Stored procedure '%s' can only be executed at the ad hoc level.
15433 16 No Supplied parameter sid is in use.
15434 16 No Could not drop login '%s' as the user is currently logged in.
15435 10 No Database successfully published.
15436 10 No Database successfully enabled for subscriptions.
15437 10 No Database successfully published using merge replication.
15438 10 No Database is already online.
15439 10 No Database is now online.
15440 10 No Database is no longer published.
15441 10 No Database is no longer enabled for subscriptions.
15442 10 No Database is no longer enabled for merge publications.
15443 10 No Checkpointing database that was changed.
15448 16 No Encryption by the machine key cannot be added to the service master key because the service master key cannot be decrypted or does not exist.
15450 10 No New language inserted.
15451 16 No Dropping an encryption from the service master key failed. No encryption by the machine key exists.
15452 10 No No alternate languages are available.
15453 10 No us_english is always available, even though it is not in syslanguages.
15454 10 No Language deleted.
15455 16 No Adding an encryption to the service master key failed. An encryption by the machine key already exists.
15457 10 No Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE statement to install.
15458 10 No Database removed.
15459 10 No In the current database, the specified object references the following:
15460 10 No In the current database, the specified object is referenced by the following:
15461 10 No Object does not reference any object, and no objects reference it.
15462 10 No File '%s' closed.
15463 10 No Device dropped.
15464 16 No Unsupported private key format or key length.
15465 16 No The private key password is invalid.
15466 16 No An error occurred during decryption.
15468 16 No An error occurred during the generation of the %S_MSG.
15469 10 No No constraints are defined on object '%ls', or you do not have permissions.
15470 10 No No foreign keys reference table '%ls', or you do not have permissions on referencing tables.
15471 10 No The text for object '%ls' is encrypted.
15472 10 No The object '%ls' does not have any indexes, or you do not have permissions.
15474 16 No Invalid private key. The private key does not match the public key of the %S_MSG.
15475 10 No The database is renamed and in single user mode.
15477 10 No Caution: Changing any part of an object name could break scripts and stored procedures.
15482 16 No Cannot change the owner of a table that has an indexed view.
15490 10 No The dependent aliases were also dropped.
15497 10 No Could not add login using sp_addlogin (user = %s). Terminating this procedure.
15499 10 No The dependent aliases were mapped to the new database owner.
15500 10 No The dependent aliases were dropped.
15502 10 No Setting database owner to SA.
15503 10 No Giving ownership of all objects to the database owner.
15504 10 No Deleting users except guest and the database owner from the system catalog.
15505 16 No Cannot change owner of object '%ls' or one of its child objects because the new owner '%ls' already has an object with the same name.
15506 16 No An error occurred while signing.
15507 16 No A key required by this operation appears to be corrupted.
15508 16 No An error occurred while generating a key required by this operation.
15509 16 No The password cannot be dropped because another database may be using it.
15510 16 No Cannot enable a login that has an empty password.
15511 10 No Default bound to column.
15512 10 No Default bound to data type.
15513 10 No The new default has been bound to columns(s) of the specified user data type.
15514 10 No Rule bound to table column.
15515 10 No Rule bound to data type.
15516 10 No The new rule has been bound to column(s) of the specified user data type.
15517 16 No Cannot execute as the database principal because the principal "%.*ls" does not exist, this type of principal cannot be impersonated, or you do not have permission.
15518 16 No Cannot execute as the Windows token. It is not valid, or you do not have permission.
15519 10 No Default unbound from table column.
15520 10 No Default unbound from data type.
15521 10 No Columns of the specified user data type had their defaults unbound.
15522 10 No Rule unbound from table column.
15523 10 No Rule unbound from data type.
15524 10 No Columns of the specified user data type had their rules unbound.
15525 10 No sp_checknames is used to search for non 7-bit ASCII characters.
15526 10 No in several important columns of system tables. The following
15527 10 No columns are searched:
15528 10 No In master:
15529 16 No Cannot execute as the ticket. It is not valid, or you do not have permission.
15530 16 No The %S_MSG with name "%.*ls" already exists.
15531 16 No The security descriptor information is not valid.
15532 16 No The security descriptor is invalid because it does not contain information about its owner or about its primary group.
15533 16 No Invalid data type is supplied in the '%ls' statement.
15534 16 No Cookie generation failed in the '%ls' statement.
15535 16 No Cannot set a credential for principal '%.*ls'.
15536 10 No In all databases:
15537 16 No Login '%.*ls' does not have access to server.
15538 16 No Login '%.*ls' does not have access to database.
15539 16 No User '%s' cannot be dropped, it can only be disabled. The user is already disabled in the current database.
15540 16 No The identity string is too long. The identity string should contain no more than %d characters.
15541 16 No Cannot drop the credential '%.*ls' because it is used by a server principal.
15542 10 No Cannot create a key without specifying an encryptor.
15556 10 No Cannot decrypt or encrypt using the specified %S_MSG, either because it has no private key or because the password provided for the private key is incorrect.
15557 10 No There is already a %S_MSG by %S_MSG '%.*ls'.
15558 10 No Cannot drop %S_MSG by %S_MSG '%.*s'.
15559 10 No Cannot drop %S_MSG '%.*ls' because there is a %S_MSG mapped to it.
15560 10 No Cannot add or drop a signature on '%.*ls' because only modules can be signed.
15561 10 No Signatures based on certificates or asymmetric keys are the only options supported in this version of the product.
15562 10 No The module being executed is not trusted. Either the owner of the database of the module needs to be granted authenticate permission, or the module needs to be digitally signed.
15563 10 No The %S_MSG has no private key set for it.
15574 10 No This object does not have any statistics.
15575 10 No This object does not have any statistics or indexes.
15576 16 No You cannot set network name on server '%ls' because it is not a linked SQL Server.
15577 10 No Warning: A linked server that refers to the originating server is not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias.
15578 16 No There is already a master key in the database. Please drop it before performing this statement.
15579 16 No Adding an encryption to the symmetric key failed. An encryption by the same %S_MSG '%.*s' may already exist.
15580 16 No Cannot drop %S_MSG because %S_MSG '%.*s' is encrypted by it.
15581 16 No Please create a master key in the database or open the master key in the session before performing this operation.
15583 10 No The module being signed is marked to execute as owner. If the owner changes the signature will not be valid.
15584 10 No An error occurred while decrypting %S_MSG '%.*ls' that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15585 10 No The current master key cannot be decrypted. The error was ignored because the FORCE option was specified.
15586 16 No Error in synchronizing system certificates between master and resource database.
15587 16 No Cannot change owner of Assembly '%.*ls' since dependent assembly '%.*ls' is not owned by the new owner.
15588 10 No The old and new master keys are identical. No data re-encryption is required.
15589 16 No Cannot revert the current security context because the cookie is invalid.
15590 16 No Can only use the 'No Revert' or 'Cookie' options with the 'Execute As' statement at the adhoc level.
15591 16 No The current security context cannot be reverted using this statement. A cookie may or may not be needed with 'Revert' statement depending on how the context was set with 'Execute As' statement.
15592 16 No Cannot unset application role because none was set or the cookie is invalid.
15593 16 No An error occurred while decrypting the password for linked login '%.*ls' that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15594 16 No The password is already provisioned for the database '%.*ls'
15595 16 No The password cannot be dropped because it is not provisioned for the database '%.*ls'
15596 10 No Warning: use of a UNIQUE index, PRIMARY KEY constraint, or UNIQUE constraint on a table with row-level security can allow information disclosure.
15597 10 No Warning: use of an IDENTITY column on a table with row-level security can allow information disclosure.
15598 10 No Warning: use of an indexed view on a table with row-level security can allow information disclosure.
15599 10 No Warning: use of a FOREIGN KEY constraint on a table with row-level security enabled can allow information disclosure, modification, or deletion not authorized at the row level.
15600 15 No An invalid parameter or option was specified for procedure '%s'.
15601 16 No Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality to disable and enable full-text search for a database is deprecated. Please change your application.
15612 16 No DBCC DBCONTROL error. Database was not made read-only.
15615 16 No DBCC DBCONTROL error. Database was not made single user.
15622 10 No No permission to access database '%s'.
15625 10 No Option '%ls' not recognized for '%ls' parameter.
15626 10 No You attempted to acquire a transactional application lock without an active transaction.
15627 10 No sp_dboption command failed.
15635 16 No Cannot execute '%ls' because the database is in read-only access mode.
15645 16 No Column '%ls' does not exist.
15646 16 No Column '%ls' is not a computed column.
15647 10 No No views with schema binding reference table '%ls'.
15650 10 No Updating %s
15651 10 No %d index(es)/statistic(s) have been updated, %d did not require update.
15652 10 No %s has been updated...
15653 10 No %s, update is not necessary...
15654 10 No Table %s: cannot perform the operation on the table because its clustered index is disabled.
15656 16 No Cannot create user defined types from XML data type.
15657 16 No Vardecimal storage format is not available in system database '%s'.
15658 16 No Cannot run sp_resetstatus against a database snapshot.
15659 16 No The schema '%ls' specified for parameter schema_name does not exist.
15660 16 No Compressing XML index is not supported by the stored procedure sp_estimate_data_compression_savings.
15661 16 No Compressing temporary tables is not supported by the stored procedure sp_estimate_data_compression_savings.
15662 16 No Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings.

Errors 16,000 to 17,999

ErrorSeverityEvent LoggedDescription
16591 16 No Multiple logical file paths limit has been reached. Statement contains %ld logical file paths, maximum allowed limit is %d.
16594 16 No Path '%ls' was referenced multiple times in result set '%ls'.
16901 16 No %hs: This feature has not been implemented yet.
16902 16 No %ls: The value of the parameter %ls is invalid.
16903 16 No The "%ls" procedure was called with an incorrect number of parameters.
16904 16 No sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE.
16905 16 No The cursor is already open.
16906 17 No Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more.
16907 16 No %hs is not allowed in cursor statements.
16909 16 No %ls: The cursor identifier value provided (%x) is not valid.
16910 16 No The cursor %.*ls is currently used by another statement.
16911 16 No %hs: The fetch type %hs cannot be used with forward only cursors.
16914 16 No The "%ls" procedure was called with too many parameters.
16915 16 No A cursor with the name '%.*ls' already exists.
16916 16 No A cursor with the name '%.*ls' does not exist.
16917 16 No Cursor is not open.
16922 16 No Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
16924 16 No Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
16925 16 No The fetch type %hs cannot be used with dynamic cursors.
16926 16 No sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
16927 16 No Cannot fetch into text, ntext, and image variables.
16928 16 No sp_cursor: Exec statement is not allowed as source for cursor insert.
16929 16 No The cursor is READ ONLY.
16930 16 No The requested row is not in the fetch buffer.
16931 16 No There are no rows in the current fetch buffer.
16932 16 No The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.
16933 16 No The cursor does not include the table being modified or the table is not updatable through the cursor.
16934 10 No Optimistic concurrency check failed. The row was modified outside of this cursor.
16935 16 No No parameter values were specified for the sp_cursor-%hs statement.
16936 16 No sp_cursor: One or more values parameters were invalid.
16937 16 No A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
16938 16 No sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
16941 16 No Cursor updates are not allowed on tables opened with the NOLOCK option.
16942 16 No Could not generate asynchronous keyset. The cursor has been deallocated.
16943 16 No Could not complete cursor operation because the table schema changed after the cursor was declared.
16945 16 No The cursor was not declared.
16946 16 No Could not open the cursor because one or more of its tables have gone out of scope.
16947 16 No No rows were updated or deleted.
16948 16 No The variable '%.*ls' is not a cursor variable, but it is used in a place where a cursor variable is expected.
16949 16 No The variable '%.*ls' is a cursor variable, but it is used in a place where a cursor variable is not valid.
16950 10 No The variable '%.*ls' does not currently have a cursor allocated to it.
16951 16 No The variable '%.*ls' cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure.
16952 16 No A cursor variable cannot be used as a parameter to a remote procedure call.
16953 10 No Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor.
16954 16 No Executing SQL directly; no cursor.
16955 16 No Could not create an acceptable cursor.
16956 10 No The created cursor is not of the requested type.
16957 16 No FOR UPDATE cannot be specified on a READ ONLY cursor.
16958 16 No Could not complete cursor operation because the set options have changed since the cursor was declared.
16959 16 No Unique table computation failed.
16960 16 No You have reached the maximum number of cursors allowed.
16961 10 No One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query.
16962 16 No The target object type is not updatable through a cursor.
16963 16 No You cannot specify scroll locking on a cursor that contains a remote table.
16964 16 No For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
16965 16 No Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch.
16966 16 No %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors.
16992 16 No The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue.
16996 16 No %ls cannot take output parameters.
16998 16 No The asynchronous cursor worktable population thread spawn failed.
16999 20 Yes Internal Cursor Error: The cursor is in an invalid state.
17000 10 No Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ]
17001 16 Yes Failure to send an event notification instance of type '%s' on conversation handle '%s'. Error Code = '%s'.
17002 16 Yes Failed to post QUEUE_ACTIVATION event. Error code: '0x%s'.
17003 16 Yes Closed event notification conversation endpoint with handle '%s', due to the following error: '%.*ls'.
17004 16 Yes Event notification conversation on dialog handle '%s' closed without an error.
17005 16 Yes Event notification '%ls' in database '%ls' dropped due to send time service broker errors. Check to ensure the conversation handle, service broker contract, and service specified in the event notification are active.
17049 16 Yes Unable to cycle error log file from '%ls' to '%ls' due to OS error '%s'. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access."
17051 16 Yes SQL Server evaluation period has expired.
17053 16 Yes %ls: Operating system error %ls encountered.
17054 16 Yes The current event was not reported to the Windows Events log. Operating system error = %s. You may need to clear the Windows Events log if it is full.
17056 10 Yes The evaluation period for your edition of SQL Server expires in %d day(s).
17057 16 Yes Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer to help diagnose the root cause.
17058 16 Yes initerrlog: Could not open error log file '%s'. Operating system error = %s.
17060 10 Yes %s
17061 10 Yes Error: %d Severity: %d State: %d %s
17063 16 Yes Error: %d Severity: %d State: %d %s
17065 16 Yes SQL Server Assertion: File: <%s>, line = %d Failed Assertion = '%s' %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
17066 16 Yes SQL Server Assertion: File: <%s>, line=%d Failed Assertion = '%s'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
17067 16 Yes SQL Server Assertion: File: <%s>, line = %d %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
17068 10 No PrintStack Request
17069 10 Yes %s
17070 16 Yes Clustered instances are not supported on this edition of SQL Server.
17083 The body of a natively compiled stored procedure must be an ATOMIC block.
17084 The WITH clause of BEGIN ATOMIC statement must specify a value for the option '%ls'.
17101 10 Yes (c) 2005 Microsoft Corporation.
17102 16 Yes Failed to initialize Distributed COM (CoInitializeEx returned %lx). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
17103 10 Yes All rights reserved.
17104 10 Yes Server process ID is %ld.
17105 10 Yes Could not open master database in system task thread context. Terminating server.
17106 10 Yes Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
17107 10 No Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
17108 10 Yes Password policy update was successful.
17109 10 Yes FallBack certificate was successfully created.
17110 10 Yes Registry startup parameters: %.*ls
17111 10 Yes Logging SQL Server messages in file '%s'.
17112 16 Yes An invalid startup option %c was supplied, either from the registry or the command prompt. Correct or remove the option.
17113 16 Yes Error %ls occurred while opening file '%ls' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
17114 16 Yes Error %ls occurred while opening file '%ls' to obtain configuration information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
17115 10 Yes Command Line Startup Parameters:%.*ls
17116 16 Yes Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
17119 10 Yes The number of concurrent user connections was reduced to %ld, because it exceeded the allowable limit for this edition of SQL Server. To avoid this message in the future, use sp_configure to permanently adjust the number of user connections within the licensed limit.
17120 16 Yes SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
17121 10 Yes SQL Server is started with trace flag %d, this may cause user to see some error messages masked using '%ls'.
17123 10 Yes Logging to event log is disabled. Startup option '-%c' is supplied, either from the registry or the command prompt.
17124 10 Yes SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
17125 10 Yes Using dynamic lock allocation. Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required.
17126 10 Yes SQL Server is now ready for client connections. This is an informational message; no user action is required.
17127 16 Yes initdata: No memory for kernel buffer hash table.
17128 16 Yes initdata: No memory for kernel buffers.
17129 10 Yes initconfig: Warning: affinity mask specified is not valid. Defaulting to no affinity. Use sp_configure 'affinity mask' or 'affinity64 mask' to configure the system to be compatible with the CPU mask on the system. You can also configure the system based on the number of licensed CPUs.
17130 16 Yes Not enough memory for the configured number of locks. Attempting to start with a smaller lock hash table, which may impact performance. Contact the database administrator to configure more memory for this instance of the Database Engine.
17131 16 Yes Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
17132 16 Yes Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory.
17133 16 Yes Launch of startup procedure '%s' failed.
17135 10 Yes Launched startup procedure '%s'.
17136 10 Yes Clearing tempdb database.
17137 10 Yes Starting up database '%s'.
17138 16 Yes Unable to allocate enough memory to start '%ls'. Reduce non-essential memory load or increase system memory.
17140 16 Yes Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
17141 16 Yes Could not register Service Control Handler. Operating system error = %s.
17142 16 Yes SQL Server service has been paused. No new connections will be allowed. To resume the service, use SQL Computer Manager or the Services application in Control Panel.
17143 16 Yes %s: Could not set Service Control Status. Operating system error = %s.
17144 10 Yes SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, use SQL Computer Manager or the Services application in Control Panel.
17145 10 Yes Service Control Handler received an invalid control code = %d.
17146 10 Yes SQL Server is allowing new connections in response to 'continue' request from Service Control Manager. This is an informational message only. No user action is required.
17147 10 Yes SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
17148 10 Yes SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
17149 10 Yes Using the static lock allocation specified in the locks configuration option. Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required.
17150 10 Yes Lock partitioning is enabled. This is an informational message only. No user action is required.
17152 10 Yes Node configuration: node %ld: CPU mask: 0x%0I64x Active CPU mask: 0x%0I64x. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
17153 10 Yes Processor affinity turned on: processor mask 0x%0*I64x. Threads will execute on CPUs per affinity mask/affinity64 mask config option. This is an informational message; no user action is required.
17155 10 Yes I/O affinity turned on, processor mask 0x%0*I64x. Disk I/Os will execute on CPUs per affinity I/O mask/affinity64 mask config option. This is an informational message only; no user action is required.
17156 16 Yes initeventlog: Could not initiate the EventLog Service for the key '%s', last error code is %d.
17158 10 Yes The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required.
17159 10 Yes The server is idle. This is an informational message only. No user action is required.
17161 10 Yes SQL Server could not use the NO_BUFFERING option during I/O, because the master file sector size, %d, is incorrect. Move the master file to a drive with a correct sector size.
17162 10 Yes SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
17163 10 Yes SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
17164 10 Yes Detected %d CPUs. This is an informational message; no user action is required.
17165 10 Yes The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required.
17166 10 Yes Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
17167 10 Yes Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
17169 10 Yes Unable to locate kernel HTTP driver Httpapi.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support the kernel HTTP driver.
17170 10 Yes SQL Server native HTTP support is not available. Could not find function entry point '%hs' in %hs. Error 0x%lx. Native HTTP access to SQL Server requires a later version of the operating system.
17171 10 Yes SQL Server native HTTP support failed and will not be available. '%hs()' failed. Error 0x%lx.
17172 16 Yes SNIInitialize() failed with error 0x%lx.
17173 10 Yes Ignoring trace flag %d specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup.
17174 10 Yes Unable to initialize SQL Server native HTTP support due to insufficient resources. HTTP access to SQL Server will not be available. Error 0x%lx. This error typically indicates insufficient memory. Reduce non-essential memory load or increase system memory.
17175 10 Yes The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
17176 10 Yes This instance of SQL Server last reported using a process ID of %s at %s (local) %s (UTC). This is an informational message only; no user action is required.
17177 10 Yes This instance of SQL Server has been using a process ID of %s since %s (local) %s (UTC). This is an informational message only; no user action is required.
17178 10 Yes Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
17179 10 Yes Could not use Address Windowing Extensions because the 'lock pages in memory' privilege was not granted.
17180 10 Yes SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure.
17181 16 Yes SNIInitializeListener() failed with error 0x%lx.
17182 16 Yes TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls
17183 10 Yes Attempting to cycle error log. This is an informational message only; no user action is required.
17184 10 Yes The error log has been reinitialized. See the previous log for older entries.
17185 16 Yes Unable to update password policy.
17186 16 Yes Failed to enqueue %s task. There may be insufficient memory.
17187 16 Yes SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. %.*ls
17188 16 Yes SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
17189 16 Yes SQL Server failed with error code 0x%x to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.%.*ls
17190 16 Yes FallBack certificate initialization failed with error code: %d.
17191 16 Yes Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors.%.*ls
17192 10 Yes Dedicated admin connection support was not started because of error 0x%lx, status code: 0x%lx. This error typically indicates a socket-based error, such as a port already in use.
17193 10 Yes SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required.
17194 16 Yes The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message: %d %.*ls %.*ls
17195 16 Yes The server was unable to complete its initialization sequence because the available network libraries do not support the required level of encryption. The server process has stopped. Before restarting the server, verify that SSL certificates have been installed. See Books Online topic "Configuring Client Protocols and Network Libraries".
17196 10 Yes Preparing for eventual growth to %d GB with Hot Add Memory.
17197 16 Yes Login failed due to timeout; the connection has been closed. This error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls
17198 16 Yes Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attempt to connect to a different endpoint on the server.%.*ls
17199 10 Yes Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag %d. This is an informational message only. No user action is required.
17200 16 Yes Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
17201 10 Yes Dedicated admin connection support was established for listening locally on port %d.
17202 10 Yes Dedicated admin connection support was established for listening remotely on port %d.
17203 16 Yes SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to the System Requirements section in BOL for further information.
17204 16 Yes %ls: Could not open file %ls for file number %d. OS error: %ls.
17207 16 Yes %ls: Operating system error %ls occurred while creating or opening file '%ls'. Diagnose and correct the operating system error, and retry the operation.
17208 16 Yes %s: File '%s' has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database from backup.
17253 10 Yes SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file '%s', %d, is invalid. Move the file to a disk with a valid sector size.
17255 10 Yes Secondary TempDB file '%.*ls' resides on a removable drive and therefore will not be attached during startup.
17256 10 Yes Secondary TempDB file '%.*ls' will not be attached during TempDB startup; Drive check failed with error '%ld'.
17257 10 Yes System error while trying to initialize disk info; Error '%ld'
17258 10 Yes No free space in the TempDB database
17300 16 Yes SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
17303 16 Yes The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
17308 16 Yes %s: Process %d generated an access violation. SQL Server is terminating this process.
17310 20 Yes A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
17311 16 Yes SQL Server is terminating because of fatal exception %lx. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
17312 16 Yes SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
17313 10 Yes Unable to locate driver ntdll.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support this driver.
17401 10 Yes Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required.
17403 10 Yes Server resumed execution after being idle %d seconds. Reason: timer event.
17404 10 Yes The server resumed execution after being idle for %d seconds.
17405 24 Yes An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
17406 10 Yes Server resumed execution after being idle %d seconds. Reason: resource pressure.
17550 10 Yes DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17551 10 Yes DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17557 16 Yes DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
17558 10 Yes Bypassing recovery for database ID %d. This is an informational message only. No user action is required.
17560 10 Yes DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'.
17561 10 Yes %ls index restored for %ls.%ls.
17572 16 Yes DBCC cannot free DLL '%ls'. SQL Server requires this DLL in order to function properly.
17573 10 Yes CHECKDB for database '%ls' finished without errors on %ls (local time). This is an informational message only; no user action is required.
17656 10 Yes Warning ******************
17657 10 Yes Attempting to change default collation to %s.
17658 10 Yes SQL Server started in single-user mode. This an informational message only. No user action is required.
17659 10 Yes Warning: System table ID %d has been updated directly in database ID %d and cache coherence may not have been maintained. SQL Server should be restarted.
17660 10 Yes Starting without recovery. This is an informational message only. No user action is required.
17661 10 Yes Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
17663 10 Yes Server name is '%s'. This is an informational message only. No user action is required.
17664 10 Yes The NETBIOS name of the local node that is running the server is '%ls'. This is an informational message only. No user action is required.
17674 10 Yes Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
17676 10 Yes SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required.
17681 10 Yes Loading default collation %s for this instance of SQL Server.
17750 16 Yes Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls.
17751 16 Yes Could not find the function %ls in the library %ls. Reason: %ls.
17752 16 Yes SQL Server has insufficient memory to run the extended stored procedure '%ls'. Release server memory resources by closing connections or ending transactions.
17753 16 No %.*ls can only be executed in the master database.
17802 20 Yes The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. The connection has been closed. %.*ls
17803 20 Yes There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
17805 20 Yes The value in the usertype field of the login record is invalid. The value 0x01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server.%.*ls
17806 20 Yes SSPI handshake failed with error code 0x%x while establishing a connection with integrated security; the connection has been closed.%.*ls
17807 20 Yes Event '%ld', which was received from the client, is not recognized by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent.
17809 20 Yes Could not connect because the maximum number of '%ld' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.%.*ls
17810 20 Yes Could not connect because the maximum number of '%ld' dedicated administrator connections already exists. Before a new connection can be made, the existing dedicated administrator connection must be dropped, either by logging off or ending the process.%.*ls
17812 10 Yes Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required.
17813 20 Yes The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls
17825 18 Yes Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. Review the error log: the entry listed after this error contains the error code from the network library.
17826 18 Yes Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
17827 20 Yes There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
17828 20 Yes The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17829 20 Yes A network error occurred while establishing a connection; the connection has been closed.%.*ls
17830 20 Yes Network error code 0x%x occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms, network writes %d ms, network reads %d ms, establishing SSL %d ms, negotiating SSPI %d ms, validating login %d ms, including user-defined login processing %d ms.%.*ls
17832 20 Yes The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17835 20 Yes Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library.%.*ls
17836 20 Yes Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.%.*ls
17881 16 Yes '%ls' is an unsupported Open Data Services API.
17883 10 Yes Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yielding on Scheduler %ld. Thread creation time: %I64d. Approx Thread CPU Used: kernel %I64d ms, user %I64d ms. Process Utilization %d%%. System Idle %d%%. Interval: %I64d ms.
17884 10 Yes New queries assigned to process on Node %d have not been picked up by a worker thread in the last %d seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %d%%. System Idle: %d%%.
17885 16 No An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
17886 20 Yes The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
17887 10 Yes IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
17888 10 Yes All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%.
17889 16 Yes A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls
17890 10 Yes A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.
17891 10 Yes Resource Monitor (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Memory freed: %I64d KB. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
17892 14 Yes Logon failed for login '%.*ls' due to trigger execution.%.*ls
17894 10 Yes Dispatcher (0x%lx) from dispatcher pool '%.*ls' Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.

Errors 18,000 to 18,999

ErrorSeverityEvent LoggedDescription
18002 20 Yes Exception happened when running extended stored procedure '%.*ls' in the library '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
18052 16 No Error: %d, Severity: %d, State: %d.
18053 16 No Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
18054 16 Yes Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.
18055 20 Yes Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support.
18056 20 Yes The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
18057 20 Yes Error: Failed to set up execution context.
18058 17 Yes Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and resource file in localized directory matches the file under English directory. Also check memory usage.
18059 16 Yes The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online.
18060 16 Yes Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the message.
18061 20 Yes The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error message.
18100 10 Yes Process ID %d was killed by hostname %.*ls, host process ID %d.
18113 10 Yes SQL Server shutdown after verifying system indexes.
18124 10 Yes The default collation was successfully changed.
18204 16 Yes %s: Backup device '%s' failed to %s. Operating system error %s.
18210 16 Yes %s: %s failure on backup device '%s'. Operating system error %s.
18225 10 Yes Tape '%s' (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required
18226 10 Yes Tape mount is being requested on drive '%s'. Expected volume has (Family ID %d, sequence %d).
18227 10 Yes Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required.
18228 10 Yes Tape mount request on drive '%s' is cancelled. This is an informational message only. No user action is required.
18257 10 Yes %s: Device or media does not support %s. To access this feature, use a different device or media.
18264 10 Yes Database backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18265 10 Yes Log was backed up. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18266 10 Yes Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18267 10 Yes Database was restored: Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). Informational message. No user action required.
18268 10 Yes Log was restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18269 10 Yes Database file was restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18270 10 Yes Database differential changes were backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, full backup LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18271 10 Yes Database changes were restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18272 16 Yes During restore restart, an I/O error occurred on checkpoint file '%s' (operating system error %s). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.
18273 16 Yes Could not clear '%s' bitmap in database '%s' because of error %d. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the error occurred on a data backup, consider taking a data backup to create a new base for future differential backups.
18274 10 Yes Tape '%s' was dismounted from drive '%s'. This is an informational message. No user action is required.
18275 10 Yes Unnamed tape was dismounted from drive '%s'. This is an informational message. No user action is required.
18276 10 Yes Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18277 10 Yes Database file changes were restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18300 10 No Reason: Infrastructure error occurred. Check for previous errors.
18301 10 No Reason: Could not find a login matching the name provided.
18302 10 No Reason: Failed to unprotect memory containing sensitive information.
18303 10 No Reason: Failed to unprotect memory containing sensitive information.
18304 10 No Reason: Could not find a login matching the name provided.
18305 10 No Reason: Attempting to use an NT account name with SQL Server Authentication.
18306 10 No Reason: An error occurred while evaluating the password.
18307 10 No Reason: Password did not match that for the login provided.
18308 10 No Reason: Invalid password provided.
18309 10 No Reason: Password validation failed with an infrastructure error. Check for previous errors.
18310 10 No Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors.
18311 10 No Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors.
18312 10 No Reason: SQL Server service is paused. No new connections can be accepted at this time.
18313 10 No Reason: Interface for login to SQL Server is not supported.
18314 10 No Reason: Failed to open the specified database.
18315 10 No Reason: Failed to open the database for this login.
18316 10 No Reason: Unable to determine the initial language and date format.
18317 10 No Reason: The user must change the password, but it cannot be changed with the current connection settings.
18318 10 No Reason: Failed to unprotect memory containing sensitive information.
18319 10 No Reason: Simulation of a failure while redoing login on the connection.
18320 10 No Reason: SQL Server service is paused. Login could not be revalidated at this time.
18321 10 No Reason: Reinitialization of security context failed while revalidating the login on the connection.
18322 10 No Reason: Access to server validation failed while revalidating the login on the connection.
18323 10 No Reason: Failed to open the specified database while revalidating the login on the connection.
18324 10 No Reason: Failed to create the user instance while revalidating the login on the connection.
18325 10 No Reason: Failed to attach the specified database while revalidating the login on the connection.
18326 10 No Reason: Failed to open the database for this login while revalidating the login on the connection.
18327 10 No Reason: Failed to determine the language and date format while revalidating the login on the connection.
18328 10 No Reason: An exception was raised while revalidating the login on the connection. Check for previous errors.
18329 10 No Reason: Simulation of a failure while reauthenticating login.
18330 10 No Reason: SQL Server service is paused. Login cannot be reauthenticated at this time.
18331 10 No Reason: Failed to reinitialize security context while reauthenticating login.
18332 10 No Reason: Failed to access server for validation while reauthenticating login.
18333 10 No Reason: Failed to open the specified database while reauthenticating login.
18334 10 No Reason: An error occurred while reauthenticating login. Check for previous errors.
18335 10 No Reason: Could not retrieve database name or map database to an item.
18336 10 No Reason: Cannot connect with a login that does not specify a share.
18337 10 No Reason: Failed to open the explicitly specified database.
18338 10 No Reason: Unable to determine the database name from the specified file name.
18339 10 No Reason: Failed to open the database specified in the login properties.
18340 10 No Reason: Failed to store database name and collation. Check for previous errors.
18341 10 No . Reason: Current collation did not match the database's collation during connection reset.
18342 10 No Reason: Failed to send an environment change notification to a log shipping partner node.
18343 10 No Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection.
18344 10 No Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection.
18345 10 No Reason: Failed to open the database configured in the login object while revalidating the login on the connection.
18346 10 No Reason: Failed to determine database name from a given file name while revalidating the login on the connection.
18347 10 No Reason: Failed to open the database specified in the login properties while revalidating the login on the connection.
18348 10 No Reason: Failed to store database name and collation while revalidating the login on the connection. Check for previous errors.
18349 10 No Reason: Current collation did not match the database's collation during connection reset.
18350 10 No Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login.
18351 10 No Reason: Client impersonation failed.
18352 10 No Reason: Failed to revert impersonation to self.
18353 10 No Reason: Failed to get security token information.
18354 10 No Reason: Failed to duplicate of security token.
18355 10 No Reason: Failed attempted retry of a process token validation.
18356 10 No Reason: An error occurred while attempting to change password.
18357 10 No Reason: An attempt to login using SQL Server Authentication failed. Server is configured for Windows Authentication only.
18400 16 Yes The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.
18401 14 Yes Login failed for user '%.*ls'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls
18451 14 Yes Login failed for user '%.*ls'. Only administrators may connect at this time.%.*ls
18452 14 Yes Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication.%.*ls
18453 10 Yes Login succeeded for user '%.*ls'. Connection made using Windows Authentication.%.*ls
18454 10 Yes Login succeeded for user '%.*ls'. Connection made using SQL Server Authentication.%.*ls
18455 10 Yes Login succeeded for user '%.*ls'.%.*ls
18456 14 Yes Login failed for user '%.*ls'.%.*ls%.*ls
18458 14 Yes Login failed. The number of simultaneous users already equals the %d registered licenses for this server. To increase the maximum number of simultaneous users, obtain additional licenses and then register them through the Licensing item in Control Panel.%.*ls
18459 14 Yes Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls
18460 14 Yes Login failed. The number of simultaneous users has already reached the limit of %d licenses for this '%ls' server. Additional licenses should be obtained and installed or you should upgrade to a full version.%.*ls
18461 14 Yes Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls
18462 14 No The login failed for user "%.*ls". The password change failed. The password for the user is too recent to change. %.*ls
18463 14 No The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls
18464 14 No Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is too short.%.*ls
18465 14 No Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is too long.%.*ls
18466 14 No Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is not complex enough.%.*ls
18467 14 No The login failed for user "%.*ls". The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls
18468 14 No The login failed for user "%.*ls". The password change failed. An unexpected error occurred during password validation. %.*ls
18469 10 No [CLIENT: %.*hs]
18470 14 Yes Login failed for user '%.*ls'. Reason: The account is disabled.%.*ls
18471 14 No The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls
18482 16 Yes Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.
18483 16 Yes Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls.
18485 16 Yes Could not connect to server '%.*ls' because it is not configured to accept remote logins. Use the remote access configuration option to allow remote logins.%.*ls
18486 14 Yes Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls
18487 14 Yes Login failed for user '%.*ls'. Reason: The password of the account has expired.%.*ls
18488 14 Yes Login failed for user '%.*ls'. Reason: The password of the account must be changed.%.*ls
18489 10 No The dedicated administrator connection is in use by "%.*ls" on "%.*ls".%.*ls
18491 16 Yes SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.
18492 16 Yes SQL Server cannot start because the license agreement for this '%ls' version of SQL Server is invalid. The server is exiting. To proceed, reinstall SQL Server with a valid license.
18493 16 Yes The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls
18494 16 Yes The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls
18495 16 Yes The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls
18496 10 Yes System Manufacturer: '%ls', System Model: '%ls'.
18596 16 No %.*ls cannot start because your system is low on memory.
18597 16 No Your %.*ls installation is either corrupt or has been tampered with (%hs). Please uninstall then re-run setup to correct this problem
18598 16 No %.*ls could not find the default instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem.
18599 16 No %.*ls could not find the specified named instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem.
18750 16 No %ls: The parameter '%ls' is not valid.
18751 16 No %ls procedure was called with the wrong number of parameters.
18752 16 No Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.
18755 16 No Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations.
18756 16 No Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.
18757 16 No Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
18760 16 No Invalid %ls statement for article %d. Verify that the stored procedures that propagate changes to Subscribers use the appropriate call syntax, and then rerun the Log Reader Agent. Use sp_helparticle and sp_changearticle to view and change the call syntax.
18761 16 No Commit record at {%08lx:%08lx:%04lx} has already been distributed.
18762 16 No Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.
18763 16 No Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0).
18764 16 No Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.
18765 16 No The "%s" log sequence number (LSN) that was specified for the replication log scan is invalid.
18766 16 No The replbeginlsn field in the DBTABLE is invalid.
18767 16 No The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}.
18768 16 No The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}.
18769 16 No The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record.
18770 16 No The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.
18771 16 No Invalid storage type %d specified writing variant of type %d.
18772 16 No Invalid server data type (%d) specified in repl type lookup.
18773 16 No Could not locate text information records for the column "%.*ls", ID %d during command construction.
18774 16 No The stored procedure %s must be executed within a transaction.
18775 16 No The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.
18776 16 No An error occurred while waiting on the article cache access event.
18777 16 No %s: Error initializing MSMQ components
18778 16 No %s: Error opening Microsoft Message Queue %s
18780 16 No You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter.
18781 16 No The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', 'disk', or 'tape'.
18782 16 No Could not locate backup header information for database '%s' in the specified backup device. Specify a backup device that contains a backup of the Publisher database.
18783 16 No The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to use a shorter path for this Publisher, and then retry the operation.
18784 16 No The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation.
18786 16 No The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, use sp_changepublication: set 'allow_initialize_from_backup' to 'true'.
18787 16 No Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications.
18790 16 No Cannot enable the option to initialize a subscription from a backup. This is not supported for non-SQL Server Publishers; it is only supported for transactional publications from SQL Server Publishers.
18795 16 No The valid new types of a log based indexed view article are 'indexed view logbased', 'indexed view logbased manualfilter', 'indexed view logbased manualview', and 'indexed view logbased manualboth' only.
18796 16 No The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only.
18799 16 No Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database.
18801 16 No Unable to allocate memory for replication schema version node.
18802 16 No Cannot insert a new schema change into the systranschemas system table. HRESULT = '0x%x'. If the problem persists, contact Customer Support Services.
18803 16 No The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N'helptopics'.
18804 16 No Peer-to-peer replication has been enabled, and the Log Reader Agent was unable to find an Extended-Originator-Record (EOR) for a transaction that did not originate at this server. Contact Customer Support Services.
18805 16 No The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
18806 16 No Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server.
18807 16 No Cannot find an object ID for the replication system table '%s'. Verify that the system table exists and is accessible by querying it directly. If it does exist, stop and restart the Log Reader Agent; if it does not exist, drop and reconfigure replication.
18808 16 No Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent.
18809 16 No END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.
18810 16 No Cannot restart the scan on table '%s'. HRESULT = '0x%x'. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Services.
18811 16 No Invalid %s log record.
18812 16 No Can not lock the database object in article cache.
18815 16 No Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.
18817 16 No Text information block not valid. Contact Customer Support Services.
18818 16 No Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18819 16 No Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18821 16 No The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services.
18823 16 No Invalid value %d for %s.
18826 16 No Failed to delete rows from the systranschemas table. HRESULT = '0x%x'. The rows will be deleted the next time replication executes the stored procedure sp_replcmds.
18827 16 No The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %d transactions in the hash table, %d transactions processed, end of log LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
18828 16 No Invalid filter procedure definition.
18829 16 No Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18830 16 No A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, current BEGIN_UPDATE {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18832 16 No The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08lx:%08lx:%04lx}, current LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
18834 16 No An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d). Contact Customer Support Services.
18835 16 No Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d), text collection state %d. Contact product support.
18836 16 No %s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %ld, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, offset %I64d, oldSize %I64d, newSize %I64d}.
18837 16 No Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.
18838 16 No The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subscriptions to the publication.
18840 16 No Cannot locate database information in the article cache. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, back up the publication database, and then contact Customer Support Services.
18842 16 No Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.
18843 16 No Failed to allocate or reallocate buffer for replication command, old size %d, new size %d.
18844 16 No Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication.
18845 16 No Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication.
18846 16 No Possible inconsistent state in the distribution database: dist_backup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute "sp_repldone NULL, NULL, 0, 0, 1", and then execute sp_replflush. Reinitialize all subscriptions to the publication.
18847 16 No Cannot retrieve the peer-to-peer database information. Contact Customer Support Services.
18849 16 No Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %d, rowsetId %I64d. Stop and restart the Log Reader Agent. If the problem persists, back up the publication database and then contact Customer Support Services.
18850 16 No Unexpected %s log record encountered, last FILESTREAMInfo node processed : {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, {%08lx:%08lx:%04lx}}
18851 16 No Failed to %s the replication context for TxF: {%I64d, %.*ls, %ld, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %I64d, %.*ls, {%08lx:%08lx:%04lx}}. If the problem persists, contact product support.
18852 16 No Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%ld'. If the problem persists, contact Customer Support Services.
18853 10 No Replication is skipping schema version logging because the systranschemas table is not present in database '%d'. This is an informational message only. No user action is required.
18854 16 No One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.
18855 11 No Can not rename the database name because it is published or it is a distribution database used by replication.
18856 16 No Agent '%s' is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details.
18857 16 No The subscription to this publication is not active yet. No user action is required.
18896 16 No Failed to compare delete and insert log record for column ID %ld with table ID %ld

Errors 19,000 to 20,999

ErrorSeverityEvent LoggedDescription
19030 10 Yes SQL Trace ID %d was started by login "%s".
19031 10 Yes SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'.
19032 10 Yes SQL Trace was stopped due to server shutdown. Trace ID = '%d'. This is an informational message only; no user action is required.
19033 10 Yes Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
19034 21 Yes Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls
19035 16 Yes OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured.
19036 10 Yes The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.
19051 16 No Unknown error occurred in the trace.
19052 16 No The active trace must be stopped before modification.
19053 16 No The trace event ID is not valid.
19054 16 No The trace column ID is not valid.
19055 16 No Filters with the same event column ID must be grouped together.
19056 16 No The comparison operator in the filter is not valid.
19057 16 No The boolean operator in the filter is not valid.
19058 16 No The trace status is not valid.
19059 16 No Could not find the requested trace.
19060 16 No The trace option is not valid.
19061 16 No Cannot remove SPID trace column.
19062 16 No Could not create a trace file.
19063 16 No Not enough memory was available for trace.
19064 16 No The requested trace stop time has been already passed.
19065 16 No The parameter is not valid.
19066 16 No Cannot modify a restricted trace.
19067 16 No Cannot create a new trace because the trace file path is found in the existing traces.
19068 16 No The trace file path is not valid or not supported.
19069 16 No The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover option is enabled.
19070 16 No The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
19071 16 No Stopping the trace because the current trace file is full and the rollover option is not specified.
19096 16 No Fail to delete an old trace file '%ls'. Error = '%ls'.
19097 10 No Windows error occurred while running %s. Error = %s.
19098 16 Yes An error occurred starting the default trace. Cause: %ls Use sp_configure to turn off and then turn on the 'default trace enabled' advanced server configuration option.
19099 16 Yes Trace ID '%d' was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.
19100 10 No Initialization succeeded.
19101 10 No Initialization failed with an infrastructure error. Check for previous errors.
19102 10 No Unable to create a node listener object. Check for memory-related errors.
19103 10 No An error occurred while starting shared memory support.
19104 10 No All protocols are disabled.
19105 10 No Unable to create a node listener object for a special instance. Check for memory-related errors.
19106 10 No Unable to trim spaces in an IP address. Check TCP/IP protocol settings.
19107 10 No 'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings.
19108 10 No Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings.
19109 10 No Unable to configure MDAC-compatibility TCP/IP port in registry.
19110 10 No Unable to initialize the TCP/IP listener.
19111 10 No Unable to open TCP/IP protocol configuration key in registry.
19112 10 No Unable to retrieve TCP/IP protocol 'Enabled' registry setting.
19113 10 No Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting.
19114 10 No Unable to open TCP/IP protocol's 'IPAll' configuration key in registry.
19115 10 No Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key.
19116 10 No Unable to obtain list size for IP addresses configured for listening in registry.
19117 10 No Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors.
19118 10 No Unable to obtain list of IP addresses configured for listening in registry.
19119 10 No Unable to open TCP/IP protocol's registry key for a specific IP address.
19120 10 No Unable to retrieve 'Enabled' setting for a specific IP address.
19121 10 No Unable to retrieve 'Active' setting for a specific IP address.
19122 10 No Unable to retrieve 'IpAddress' value for a specific IP address.
19123 10 No 'IpAddress' registry value is the wrong type.
19124 10 No Unable to retrieve registry settings for a specific IP address.
19125 10 No Unable to deallocate structures representing registry key for a specific IP address.
19126 10 No Unable to retrieve registry settings for cluster environment.
19127 10 No Server is configured to listen on a specific IP address in a cluster environment.
19128 10 No Unable to check for a duplicate IP address in the network.
19129 10 No A duplicate IP address was detected in the network.
19130 10 No Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings.
19131 10 No Unable to open Dedicated Administrator Connection configuration key in registry.
19132 10 No Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry.
19133 10 No Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection.
19134 10 No No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings.
19135 10 No Error starting Named Pipes support. Check protocol settings.
19136 10 No An error occurred starting VIA support. Check protocol settings.
19137 10 No Failed to allocate memory SSL listening structures. Check for memory-related errors.
19138 10 No An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager.
19139 10 No Unable to add listener endpoints. Check for memory-related errors.
19140 10 No Unable to initialize the communication listeners.
19141 10 No Unable to retrieve SQL Server Network Interface library settings for a special instance.
19142 10 No Unable to retrieve SQL Server Network Interface library settings; the instance name is too long.
19143 10 No Unable to initialize the Shared Memory listener.
19144 10 No Unable to initialize the Named Pipes listener.
19145 10 No Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry.
19146 10 No Unable to initialize the VIA listener.
19147 10 No Unable to initialize the HTTP listener.
19148 10 No Unable to initialize SSL support.
19149 10 No Unable to configure MDAC-compatibility protocol list in registry.
19150 10 No Unable to open SQL Server Network Interface library configuration key in registry.
20001 10 No There is no nickname for article '%s' in publication '%s'.
20002 10 No The filter '%s' already exists for article '%s' in publication '%s'.
20003 10 No Could not generate nickname for '%s'.
20004 10 No Publication '%s' has the following property: '%s'. SQL Server subscribers below version '%s' will ignore this setting.
20005 18 No %ls: Cannot convert parameter %ls: Resulting colv would have too many entries.
20006 16 No Cannot make the change because the article might be in a publication that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 to acknowledge that such a subscription will be reinitialized.
20007 16 No The system tables for merge replication could not be dropped successfully.
20008 16 No The system tables for merge replication could not be created successfully.
20009 16 No The article '%s' could not be added to the publication '%s'.
20010 16 No The Snapshot Agent corresponding to the publication '%s' could not be dropped.
20011 16 No Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property.
20012 16 No The subscription type '%s' is not allowed on publication '%s'.
20013 16 No The publication property '%s' cannot be changed when there are subscriptions on it.
20014 16 No Invalid @schema_option value.
20015 16 No Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory.
20016 16 No Invalid @subscription_type value. Valid values are 'pull' or 'anonymous'.
20017 16 No The subscription on the Subscriber does not exist.
20018 16 No The @optional_command_line is too long. Use an agent definition file.
20019 16 No Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database.
20020 16 No The article resolver supplied is either invalid or nonexistent.
20021 16 No The subscription could not be found.
20022 16 No This article has now settings to disable uploads and compensate_for_errors=true. However, local and anonymous subscribers will behave as if compensate_for_errors=false.
20023 16 No Invalid @subscriber_type value. Valid options are 'local', 'global', or 'anonymous'.
20024 16 No The alt_snapshot_folder cannot be the same as the working directory.
20025 16 No The publication name must be unique. The specified publication name '%s' has already been used.
20026 16 No The publication '%s' does not exist.
20027 16 No The article '%s' does not exist.
20028 16 No The Distributor has not been installed correctly. Could not enable database for publishing.
20029 16 No The Distributor has not been installed correctly. Could not disable database for publishing.
20030 16 No The article '%s' already exists on another publication with a different column tracking option.
20031 16 No Could not delete the row because it does not exist.
20032 16 No '%s' is not defined as a Subscriber for '%s'.
20033 16 No Invalid publication type.
20034 16 No Publication '%s' does not support '%s' subscriptions.
20036 16 No The Distributor has not been installed correctly.
20037 16 No The article '%s' already exists in another publication with a different article resolver.
20038 16 No The article filter could not be added to the article '%s' in the publication '%s'.
20039 16 No The article filter could not be dropped from the article '%s' in the publication '%s'.
20040 16 No Could not drop the article(s) from the publication '%s'.
20041 16 No Transaction rolled back. Could not execute trigger. Retry your transaction.
20043 16 No Could not change the article '%s' because the publication has already been activated.
20044 16 No The priority property is invalid for local subscribers.
20045 16 No You must supply an article name.
20046 16 No The article does not exist.
20047 16 No You are not authorized to perform this operation.
20048 16 No To modify the priority of a subscription, run sp_changemergesubscription at the Publisher instead of using sp_changemergepullsubscription at subscriber. This is for backward compatibility only.
20049 16 No The priority value should not be larger than 100.0.
20050 16 No The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999.
20051 16 No The Subscriber is not registered.
20052 16 No The @metatype parameter value must be null, 1, 2, 5, or 6.
20053 16 No An article with a different %s value already exists for object '%s'.
20054 16 No Current database is not enabled for publishing.
20055 16 No Table '%s' cannot be published for merge replication because it has a timestamp column.
20056 16 No Table '%s' cannot be republished.
20057 16 No The profile name '%s' already exists for the specified agent type.
20058 16 No The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge)
20059 16 No The @profile_type must be 0 (System) or 1 (Custom)
20060 16 No Compatibility level cannot be smaller than 60.
20061 16 No The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.
20062 16 No Updating columns with the rowguidcol property is not allowed.
20063 16 No Table '%s' into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process can perform these operations.
20064 16 No Cannot drop profile. Either it is not defined or it is defined as the default profile.
20065 16 No Cannot drop profile because it is in use.
20066 16 No Profile not defined.
20067 16 No The parameter name '%s' already exists for the specified profile.
20068 16 No The article cannot be created on table '%s' because it has more than %d columns.
20069 16 No Cannot validate a merge article that uses looping join filters.
20070 16 No Cannot update subscription row.
20072 16 No Cannot update Subscriber information row.
20073 16 No Articles can be added or changed only at the Publisher.
20074 16 No Only a table object can be published as a "table" article for merge replication.
20075 16 No The 'status' parameter value must be either 'active' or 'unsynced'.
20076 16 No The @sync_mode parameter value must be 'native' or 'character'.
20077 16 No Problem encountered generating replica nickname.
20078 16 No The @property parameter value must be one of the following: 'sync_type', 'priority', 'description', 'subscriber_security_mode', 'subscriber_login', 'subscriber_password', 'publisher_security_mode', 'publisher_login', 'publisher_password', 'merge_job_login', or 'merge_job_password'.
20079 16 No Invalid @subscription_type parameter value. Valid options are 'push', 'pull', or 'both'.
20081 16 No Publication property '%s' cannot be NULL.
20084 16 No Publication '%s' cannot be subscribed to by Subscriber database '%s'.
20086 16 No Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column.
20087 16 No You cannot push an anonymous subscription.
20088 16 No Only assign priorities that are greater than or equal to 0 and less than 100.
20089 16 No Could not get license information correctly.
20090 16 No Could not get version information correctly.
20091 16 No sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions.
20092 16 No Table '%s' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publisher data modifications are disallowed until the upgrade completes and snapshot has successfully run. On subscriber data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher.
20093 16 No Merge replication upgrade is not complete until the snapshot agent is run for the publisher and the merge agent run for all the subscribers.
20100 16 No Cannot drop Subscriber '%s'. There are existing subscriptions.
20500 16 No The updatable Subscriber stored procedure '%s' does not exist.
20501 16 No Could not insert into sysarticleupdates using sp_articlecolumn.
20502 16 No Invalid '%s' value. Valid values are 'read only', 'sync tran', 'queued tran', or 'failover'.
20503 16 No Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions.
20504 16 No Immediate Updating Subscriptions: The xml values inserted/updated by Subscriber will be replicated as NULL to publisher.
20505 16 No Could not drop synchronous update stored procedure '%s' in '%s'.
20506 16 No Source table '%s' not found in '%s'.
20507 16 No Table '%s' not found in '%s'.
20508 11 No Updatable subscriptions: The text, ntext, or image values inserted at the Subscriber will be NULL.
20509 16 No Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber.
20510 16 No Updateable Subscriptions: Cannot update identity columns.
20511 16 No Updateable Subscriptions: Cannot update timestamp columns.
20512 16 No Updateable Subscriptions: Rolling back transaction.
20513 16 No Database '%s' does not contain any replication metadata for a row whose ROWGUIDCOL matches the value specified for the @rowguid parameter of sp_showrowreplicainfo. Verify that the value specified for @rowguid parameter is correct.
20514 10 No A rowcount validation request has been submitted to heterogeneous publisher %s for article %s of publication %s. Validation results will be posted to distribution history.
20515 16 No Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber.
20516 16 No Updateable Subscriptions: Replicated data is not updatable.
20518 16 No Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column.
20519 16 No Updateable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
20520 16 No Updateable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
20521 16 No sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles.
20522 16 No sp_MSmark_proc_norepl: invalid object name '%s'.
20523 16 No Could not validate the article '%s'. It is not activated.
20524 10 No Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast).
20525 10 No Table '%s' might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s).
20526 10 No Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast).
20527 10 No Table '%s' passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns.
20528 10 No Log Reader Agent startup message.
20529 10 No Starting agent.
20530 10 No Run agent.
20531 10 No Detect nonlogged agent shutdown.
20532 10 No Replication agent schedule.
20533 10 No Replication agents checkup
20534 10 No Detects replication agents that are not logging history actively.
20535 10 No Removes replication agent history from the distribution database.
20536 10 No Replication: agent failure
20537 10 No Replication: agent retry
20538 10 No Replication: expired subscription dropped
20539 10 No Replication Warning: %s (Threshold: %s)
20540 10 No Replication: agent success
20541 10 No Removes replicated transactions from the distribution database.
20542 10 No Detects and removes expired subscriptions from published databases.
20543 10 No @rowcount_only parameter must be the value 0,1, or 2. 0=7.0 compatible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in version 8.0.
20545 10 No Default agent profile
20546 10 No Verbose history agent profile.
20547 10 No Agent profile for detailed history logging.
20548 10 No Slow link agent profile.
20549 10 No Agent profile for low bandwidth connections.
20550 10 No Windows Synchronization Manager profile
20551 10 No Profile used by the Windows Synchronization Manager.
20552 10 No Could not clean up the distribution transaction tables.
20553 10 No Could not clean up the distribution history tables.
20554 10 No The replication agent has not logged a progress message in %ld minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.
20555 10 No 6.x publication.
20556 10 No Heartbeats detected for all running replication agents.
20557 10 Yes Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'.
20558 10 No Table '%s' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically.
20559 10 No Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used.
20560 10 No An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested.
20561 10 No Generated expected rowcount value of %s for %s.
20565 10 No Replication: Subscriber has failed data validation
20566 10 No Replication: Subscriber has passed data validation
20567 10 No Agent history clean up: %s
20568 10 No Distribution clean up: %s
20569 10 No Expired subscription clean up
20570 10 No Reinitialize subscriptions having data validation failures
20571 10 No Reinitializes all subscriptions that have data validation failures.
20572 10 Yes Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure.
20573 10 No Replication: Subscription reinitialized after validation failure
20574 10 Yes Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation.
20575 10 No Subscriber '%s' subscription to article '%s' in publication '%s' passed data validation.
20576 10 No Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure.
20577 10 No No entries were found in msdb..sysreplicationalerts.
20578 10 No Replication: agent custom shutdown
20579 10 No Generated expected rowcount value of %s and expected checksum value of %s for %s.
20580 10 No Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'.
20581 10 No Cannot drop server '%s' because it is used as a Distributor in replication.
20582 10 No Cannot drop server '%s' because it is used as a Publisher in replication.
20583 10 No Cannot drop server '%s' because it is used as a Subscriber in replication.
20584 10 No Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication.
20585 16 No Validation Failure. Object '%s' does not exist.
20586 16 No (default destination)
20587 16 No Invalid '%s' value for stored procedure '%s'.
20588 16 No The subscription is not initialized. Run the Distribution Agent first.
20589 10 No Agent profile for replicated queued transaction reader.
20590 16 No The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data transformations.
20591 16 No Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows data transformations.
20592 16 No 'dts horizontal partitions' and 'no dts horizontal partitions' are not valid 'status' values because the publication does not allow data transformations.
20593 16 No Cannot modify publication '%s'. The sync_method cannot be changed to 'native', or 'concurrent' because the publication is enabled for heterogeneous subscribers.
20594 16 No A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions.
20595 16 No Skipping error signaled.
20596 16 No Only '%s' or members of db_owner can drop the anonymous agent.
20597 10 No Dropped %d anonymous subscription(s).
20598 16 No The row was not found at the Subscriber when applying the replicated command.
20599 16 No Continue on data consistency errors.
20600 10 No Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers.
20601 10 No Invalid value specified for agent parameter 'SkipErrors'.
20602 10 No The value specified for agent parameter 'SkipErrors' is too long.
20603 10 No The agent profile cannot be used by heterogeneous Subscribers.
20604 10 No You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'.
20605 10 No Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot.
20606 10 No Reinitialized subscription(s).
20607 10 No Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing snapshot.
20608 10 No Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active subscriptions.
20609 16 No Cannot attach subscription file '%s'. Make sure that it is a valid subscription copy file.
20610 16 No Cannot run '%s' when the Log Reader Agent is replicating the database.
20611 16 No Cannot add the article. Publications that allow transformable subscriptions with Data Transformation Services (DTS) can only include tables and indexed views that are published as tables.
20612 16 No Checksum validation is not supported because the publication allows DTS. Use row count only validation.
20613 16 No Validation is not supported for articles that are set up for DTS horizontal partitions.
20614 16 No Validation is not supported for heterogeneous Subscribers.
20615 16 No Unable to add a heterogeneous subscription to the publication. The publication is not enabled for heterogeneous subscriptions.
20616 10 No High Volume Server-to-Server Profile
20617 10 No Merge agent profile optimized for the high volume server-to-server synchronization scenario.
20618 16 No You must have CREATE DATABASE permission to attach a subscription database.
20619 16 No Server user '%s' is not a valid user in database '%s'. Add the user account or 'guest' user account into the database first.
20620 11 No The security mode specified requires the server '%s' to be registered as a linked server. Use sp_addlinkedserver to add the server.
20621 11 No Cannot copy a subscription database to an existing database.
20622 11 No Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode.
20623 11 No You cannot validate article '%s' unless you have 'SELECT ALL' permission on table '%s'.
20624 16 No The value specified for the @login parameter is not valid. User '%s' is not a user in database '%s'. Add the user account to the database before attempting to execute the stored procedures sp_grant_publication_access or sp_revoke_publication_access.
20625 16 No Cannot create the merge replication publication access list (PAL) database role for publication '%s'. This role is used by replication to control access to the publication. Verify that you have sufficient permissions to create roles in the publication database.
20626 16 No Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter.
20627 16 No Partition id has to be greater than or equal to 0.
20628 16 No Failed to generate dynamic snapshot.
20629 16 No Failed to get partition id information.
20630 16 No Cannot create partitioned snapshot job. A job already exists for publication '%ls' that uses the values you specified for the @suser_sname and/or @host_name parameters of sp_adddynamicsnapshot_job. If the job that already exists is not working correctly, use sp_dropdynamicsnapshot_job to drop it and create a new one using sp_adddynamicsnapshot_job.
20631 16 No Cannot find a location in which to generate a partitioned snapshot. Verify that the there is a valid snapshot folder specified for the publication. This can be the default folder associated with the Distributor or an alternate folder associated with the publication.
20632 16 No Failed to create a dynamic snapshot job to generate the dynamic snapshot.
20633 16 No Cannot start the partitioned snapshot job. Verify that SQL Server Agent is running on the Distributor.
20634 16 No The root publication information could not be found on the republisher.
20635 16 No A push subscription to '%ls' was found. Cannot add a pull subscription agent for a push subscription.
20636 16 No Cannot generate merge replication stored procedures for article '%s'. Stored procedures are generated on the Publisher when the Snapshot Agent runs or when a data definition language action is performed; they are generated on the Subscriber when the snapshot is applied by the Merge Agent. Verify that the agents have the appropriate permissions to create procedures, and that the procedures do not already exist.
20637 10 No The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign key relationships between published tables. Article '%s' references one or more articles that will be created after it is created. Change the processing_order property using sp_changemergearticle.
20638 10 No Merge table articles do not support different values for the @source_object and @destination_object parameters of sp_addmergearticle. Either do not specify a value for @destination_object, or specify the same value for both parameters.
20639 16 No Cannot enable the publication to support non-SQL Server subscriptions because the publication is enabled for updatable subscriptions. To support non-SQL Server subscriptions, drop the existing publication and create a new one with the properties allow_sync_tran and allow_queued_tran set to 'false'.
20640 16 No Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.
20641 16 No Failed to check if the subset_filterclause has a dynamic function in it.
20642 16 No Cannot add article '%s' with one or more dynamic functions in the subset_filterclause '%s' to publication '%s' because the publication could have active subscriptions. Set @force_reinit_subscription to 1 to add the article and reinitialize all active subscriptions.
20643 16 No Cannot change the value of validate_subscriber_info for publication '%s' because the publication has active subscriptions. Set @force_reinit_subscription to 1 to change the value and reinitialize all active subscriptions.
20644 16 No Invalid value "%s" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none".
20645 16 No The property "%s" cannot be modified for publications that are enabled for non-SQL Server subscriptions.
20646 16 No Peer-to-peer publications do not support %s. Change the value for parameter '%s'.
20647 16 No Cannot modify property '%s'. The publication is used in a peer-to-peer topology, which does not allow this property to be modified after the publication is created.
20648 16 No An article already exists for table "%s" with a different value for the @delete_tracking property. The value must be the same for all publications in which the table is published. Use the stored procedures sp_helpmergearticle and sp_changemergearticle to view and modify the property in the other article(s).
20649 16 No Publications enabled for heterogeneous subscriptions do not support %s. Please change the '%s' parameter value.
20650 16 No Cannot enable data definition language (DDL) replication (a value of "true" for the @replicate_ddl parameter) for publication "%s". This is because the compatibility level of the publication is lower than 90RTM. For new publications, in the stored procedure sp_addmergepublication, set the @publication_compatibility_level parameter to 90RTM; for existing publications, use sp_changemergepublication.
20651 16 No Publication "%s" "%s". Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower, disable the feature and then call the stored procedure sp_changemergepublication to lower the compatibility level.
20652 16 No Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.
20653 16 No Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.
20654 16 No Dynamic snapshots are only valid for merge publications.
20655 16 No The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history table in the distribution database. Ensure that a standard snapshot is up-to-date and available.
20656 16 No The @subset_filterclause parameter cannot reference a computed column.
20657 16 No The value for the @pub_identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity column "%s" is %s.
20658 16 No The value for the @identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity column "%s" is %s.
20659 11 No The value of IDENT_CURRENT ("%s") is greater than the value in the max_used column of the MSmerge_identity_range system table.
20660 16 No The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range.
20661 16 No The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range.
20662 16 No The republisher does not have a range of identity values from the root Publisher '%s' that it can assign to its Subscribers. Ensure that the republisher has a server subscription to the publication at the root Publisher, and then run the Merge Agent to synchronize with the root Publisher.
20663 16 No The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @identityrangemanagementoption property is "auto".
20664 16 No The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have all been used. Change the data type in the identity column.
20665 16 No The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run the Merge Agent to synchronize with the root Publisher.
20666 16 No Cannot refresh the identity range and/or the check constraint on the Publisher. Ensure the following: that the value in the identity column has not reached the maximum for the data type in the identity column; and that the user who made the last insert has the privileges to drop and re-create the check constraint.
20667 16 No Cannot allocate an identity range for article "%s". The article is not enabled for automatic identity range management.
20668 16 No Not enough range available to allocate a new range for a subscriber.
20669 16 No Object referenced by the given @article or @artid '%s' could not be found.
20670 16 No Cannot add, drop, or alter the identity range check constraint for table %s. This constraint is used by replication for automatic identity range management. This error typically occurs if the user who made the last insert in the table does not have permission to make schema changes on the table. If this error occurs at the Publisher, run sp_adjustpublisheridentityrange; if it occurs at the Subscriber, run the Merge Agent.
20671 16 No Cannot find the identity range allocation entry for the Subscriber in the MSmerge_identity_range table. Reinitialize the subscription.
20672 16 No A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering.
20673 16 No A value for the parameter @host_name was specified, but no articles in the publication use SUSER_SNAME() for parameterized filtering.
20674 16 No The publication does not use dynamic filtering.
20675 16 No The identity range values cannot be NULL.
20676 11 No Cannot refresh the Publisher identity range for article "%s". Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity range.
20677 11 No Cannot add article "%s" with automatic identity range management. The article is already published in a transactional publication with automatic identity range management.
20678 11 No Could not find the regular snapshot job for the specified publication '%s'.
20679 11 No Cannot execute the stored procedure sp_adjustpublisheridentityrange on the current database because the database is a republisher or a Subscriber. To adjust the identity range at a republisher or a Subscriber, synchronize with the root Publisher.
20680 16 No Failed to get metadata for a batch of rows.
20681 10 No Cannot specify a value of 1, 2, or 3 for the parameter @partition_options because publication "%s" has a compatibility level lower than 90RTM. Use the stored procedure sp_changemergepublication to set publication_compatibility_level to 90RTM.
20682 10 No Failed deletion of rows in batched delete attempt on table %s.
20683 16 No Failed batched deletion on download only article %s.
20684 16 No Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent.
20685 16 No Cannot drop the filter '%s' . The filter specified for the @filtername parameter cannot be found.
20686 16 No Parameter '%s' cannot be NULL or empty when this procedure is run from a '%s' database.
20687 16 No Parameter '%s' must be NULL when this procedure is not being run from a '%s' database.
20688 16 No The tracer token ID (%d) could not be found for Publisher %s, database %s, publication %s. Use the stored procedure sp_helptracertokens to retrieve a list of valid tracer token IDs.
20689 16 No The check for a Publisher needing a new identity range allocation failed on table %s. This check occurs every time the Merge Agent and Snapshot Agent run. Rerun the Merge Agent or Snapshot Agent.
20690 16 No Cannot set up the Publisher identity range for table %s. Verify that appropriate ranges were specified when the article was created, and then rerun the Snapshot Agent.
20691 16 No Merge replication upgrade of SQL Server 2005 metadata and triggers on the subscriber failed.
20692 16 No One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_tombstone; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication.
20693 16 No One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_contents; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication.
20694 16 No One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch updates can improve the performance of merge replication.
20695 16 No Only %ld out of %ld rows were updated in the batched update procedure for table %s; other rows could not be updated because they have been deleted. No action is required, but if this condition occurs frequently, determine if update-delete conflicts can be avoided. Batch updates can be helpful for performance.
20696 16 No The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication.
20697 16 No Cannot drop article %s from publication %s. In this publication, this is the only article that uses a parameterized filter. Dropping this article changes the publication to a static publication, which requires reinitialization of all Subscribers. To drop the article and reinitialize all active subscriptions, specify a value of 1 for the @force_reinit_subscription parameter of sp_dropmergepublication.
20698 16 No A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering.
20699 16 No A value for the parameter @suser_sname was not specified while publication uses SUSER_SNAME() for dynamic filtering.
20701 16 No The dynamic snapshot job schedule could not be changed on the distributor.
20702 16 No The dynamic snapshot job schedule could not be changed due to one or more errors.
20703 16 No One or more rows inserted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20704 16 No The datatype of the identity column of table '%s' is tinyint. tinyint does not have enough numbers available for merge auto identity range. Change the identity column to have a larger datatype and add the merge article with merge auto identity range management.
20705 10 No Cannot set @conflict_logging to 'both' because publication '%s' has a compatibility level lower than 90. Set @publication_compatibility_level to '90RTM' when creating the publication or use sp_changemergepublication to set publication_compatibility_level to '90RTM'.
20706 10 No The max or min allowed identity numbers for the identity column could not be found for the given article.
20707 10 No Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors.
20708 10 No An article is not allowed to be part of a logical record when it has a custom business logic resolver.
20709 10 No The merge process could not clean up the conflict table "%s" for publication "%s".
20710 16 No Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for publisher '%s', publisher_db '%s', publication '%s' and article '%s'.
20711 16 No The dynamic filters property for publication '%s' has been incorrectly set. Use sp_changemergepublication to reset the value to true if the publication uses parameterized filters and false if it does not.
20712 16 No Unable to acquire the replication merge administrative application lock for database '%s'. This could be due an active snapshot running while the schema change (DDL) or the administrative proc change was attempted.
20713 16 No Replication merge admin stored procedure '%s' failed for publication '%s'. This could be due an active snapshot running while the admin proc was called.
20714 16 No Failed to prepare article '%s' in publication '%s' for merge replication.
20715 16 No Failed to create merge replication triggers for object '%s'.
20716 16 No Failed to create publication views for merge replication publication '%s'.
20717 16 No sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings to change the settings or sp_dropmergelogsettings to remove the settings.
20718 16 No Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. Use sp_addmergelogsettings to add the settings.
20719 16 No sp_changemergelogsettings failed to update log settings. Check the parameter values.
20720 16 No Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'.
20721 16 No sp_dropmergelogsettings failed to remove log settings.
20722 16 No '%s' failed. The value for parameter '%s' is not valid. Valid values are @support_options [0 - 5], @log_severity [1 - 4], @log_file_size [2,000,000 - 999,000,000], @no_of_log_files [2 - 500], @upload_interval [0 - 40320], @delete_after_upload [0 - 1].
20723 16 No Computed column "%s" can only be added to publication after its depending object "%s" is added.
20724 16 No Could not find a valid command line for the dynamic snapshot job with job_id '%s' for publication '%s'.
20725 16 No Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id '%s' in publication '%s'.
20726 16 No Failed to change the dynamic snapshot location in one or more dynamic snapshot jobs for the given publication.
20727 16 No An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'.
20728 16 No Failed to restore the max allocated identity value for article '%s' in publication '%s'.
20729 16 No The max identity value allocation for article '%s' in publication '%s' could not be found on the distributor.
20730 16 No Setting @upload_first to 'true' requires the publication to be at publication_compatibility_level of '80RTM' or higher. Use sp_changemergepublication to set publication_compatibility_level to '80RTM' or higher if you want to use this feature.
20731 16 No This edition of SQL Server does not support publications. Dropping existing publications.
20732 10 No Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead.
20733 16 No One or more rows updated in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20734 16 No One or more rows deleted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20735 16 No Cannot add article '%s' to publication '%s'. The publication already contains 256 articles, which is the maximum.
20736 10 No Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead.
20737 10 No Warning: To allow replication of FILESTREAM data to perform optimally and reduce memory utilization, the 'stream_blob_columns' property has been set to 'true'. To force FILESTREAM table articles to not use blob streaming, use sp_changemergearticle to set 'stream_blob_columns' to 'false'.
20738 11 No Cannot add article '%s' with sparse column or column set to merge publication since merge replication does not support sparse columns and column set.
20739 16 No The DDL operation is not supported for article '%s'. If the column in the DDL operation is enabled for FILESTREAM or is of type hierarchyid, geometry, geography, datetime2, date, time, or datetimeoffset, the publication compatibility level must be at least 100RTM. For DDL operations that involve FILESTREAM and hierarchyid columns, the snapshot mode must be native. Character mode, which is required for SQL Server Compact Subscribers, is not supported.
20800 16 No Cannot reinitialize the article '%s' in subscription '%s:%s' to publication '%s'. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead.
20801 16 No Cannot reinitialize the subscription. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead.
20802 16 No Cannot publish objects from the replication administrative user schema [%s]. This schema owns all replication procedures and metadata tables, but it cannot own published objects. Use a different schema for objects that will be published.
20803 16 No Peer-To-Peer topologies require identical articles in publications at all nodes prior to synchronizing. Articles in publication [%s].[%s].[%s] do not match articles in [%s].[%s].[%s].
20804 16 No Articles can only be included in a single peer-to-peer publication. [%s].[%s] is already included in the peer-to-peer publication '%s'.
20805 16 No Peer-to-peer topologies require identical publication names on each Publisher. You are attempting to republish object [%s].[%s] that is already being published in the peer-to-peer publication [%s].[%s].[%s].
20806 16 No An error occurred while executing a peer-to-peer forwarding command. Contact Customer Support Services.
20807 16 No No peers were found for %s:%s:%s. If you encounter this error when executing the stored procedure sp_requestpeerresponse, verify that subscriptions have been created before attempting to call the procedure again. If you encounter this error in other circumstances, contact Customer Support Services.
20808 16 No The peer-to-peer publication '%s' does not exist. Execute sp_helppublication to view a list of publication names.
20809 16 No Peer-To-Peer topologies require identical publication names on each publisher. The distribution agent for publication [%s].[%s].[%s] is attempting to synchronize articles that exist in publication [%s].[%s].[%s].
20810 16 No The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type article.
20811 16 No Replication monitoring refresher for %s.
20812 16 No The specified source object must be a synonym if it is published as a 'synonym schema only' type article.
20813 16 No Only members of the sysadmin fixed server role can modify a %s that does not have a job with a proxy account defined.
20814 10 No Distribution Profile for OLEDB streaming
20815 10 No Distribution agent profile enabled for the processing LOB data using OLEDB streaming.
20816 10 No Peer-To-Peer publishers are only supported on Enterprise class editions of SQL Server. This instance is %s.
20817 16 No An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'.

Errors 21,000 to 21,999

ErrorSeverityEvent LoggedDescription
21000 16 No Cannot subscribe to an inactive publication.
21001 16 No Cannot add a Distribution Agent at the Subscriber for a push subscription.
21002 16 No The Distribution Agent for this subscription already exists (%s).
21003 16 No Changing publication names is no longer supported.
21004 16 No Cannot publish the database object '%s' because it is encrypted.
21005 10 No For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible.
21006 16 No Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpublisher.
21007 16 No Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor.
21008 16 No Cannot uninstall the Distributor because there are Subscribers defined.
21009 16 No The specified filter procedure is already associated with a table.
21010 16 No Removed %ld replicated transactions consisting of %ld statements in %ld seconds (%ld rows/sec).
21011 16 No Deactivated subscriptions.
21012 16 No Cannot change the 'allow_push' property of the publication to "false". There are push subscriptions on the publication.
21013 16 No Cannot change the 'allow_pull' property of the publication to "false". There are pull subscriptions on the publication.
21014 16 No The @optname parameter value must be 'transactional' or 'merge'.
21015 16 No The replication option '%s' has been set to TRUE already.
21016 16 No The replication option '%s' has been set to FALSE already.
21017 16 No Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQL Server 2000 compatible binary checksum operation can be performed on this article.
21018 16 No There are too many consecutive snapshot transactions in the distribution database. Run the Log Reader Agent again or clean up the distribution database.
21019 10 No Distribution agent for subscription added.
21020 10 No no comment specified.
21021 16 No Drop the Distributor before you uninstall replication.
21022 16 No If set 'immediate_sync' property of a publication to true then must also set 'independent_agent' property to true.
21023 16 No '%s' is no longer supported.
21024 16 No The stored procedure '%s' is already published as an incompatible type.
21025 16 No The string being encrypted cannot have null characters.
21026 16 No Cannot have an anonymous subscription on a publication that does not have an independent agent.
21027 16 No '%s' replication stored procedures are not installed. You must reinstall SQL Server with Replication.
21028 16 No Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication.
21029 16 No Cannot drop a push subscription entry at the Subscriber unless @drop_push is 'true'.
21030 16 No Names of SQL Server replication agents cannot be changed.
21031 16 No 'post_script' is not supported for stored procedure articles.
21032 16 No Could not subscribe because non-SQL Server Subscriber '%s' does not support 'sync tran' update mode.
21033 16 No Cannot drop server '%s' as Distribution Publisher because there are databases enabled for replication on that server.
21034 16 No Rows inserted or updated at the Subscriber cannot be outside the article partition.
21035 16 No You have updated the Publisher property '%s' successfully.
21036 16 No Another %s agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent.
21037 16 No Invalid working directory '%s'.
21038 16 No Windows Authentication is not supported by the server.
21039 16 No The article '%s' contains the destination owner '%s'. Non-SQL Server Subscribers require articles to have the destination owner of NULL.
21040 16 No Publication '%s' does not exist.
21041 16 No A remote distribution Publisher is not allowed on this server version.
21042 16 No The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running on Windows NT 4.0.
21043 16 No The Distributor is not installed.
21044 16 No Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing.
21045 16 No Cannot uninstall the Distributor because there are databases enabled for publishing or merge publishing.
21046 16 No Cannot change distribution Publisher property 'distribution_db' because the Publisher is using the current distribution database.
21047 16 No Cannot drop the local distribution Publisher because there are Subscribers defined.
21048 16 No Cannot add login '%s' to the publication access list because it does not have access to the distribution server '%s'.
21049 16 No The login '%s' does not have access permission on publication '%s' because it is not in the publication access list.
21050 16 No Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation.
21051 16 No Could not subscribe because non-SQL Server Subscriber '%s' does not support custom stored procedures.
21052 16 No Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator is running, and that the subscription is active and initialized. If the subscription uses Microsoft Message Queueing, ensure the proper permissions are set on the queue.
21053 16 No Input property parameter is not valid. See SQL Server Books Online for a list of valid parameters for sp_changemergepublication.
21054 16 No The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers with updating subscriptions). Ensure sp_link_publication has been used to configure the linked server properly, and ensure that the login used to connect to the Publisher is in the publication access list.
21055 15 No Invalid value for parameter %s specified for %s.
21056 16 No The subscription to publication '%s' has expired or does not exist.
21057 16 No Anonymous Subscribers cannot have updatable subscriptions.
21058 16 No An updatable subscription to publication '%s' on Subscriber '%s' already exists.
21059 16 No Cannot reinitialize subscriptions of non-immediate_sync publications.
21060 16 No Could not subscribe because non-SQL Server Subscriber '%s' does not support parameterized statements.
21061 16 No Invalid article status %d specified when adding article '%s'.
21062 16 No The row size of table '%s' exceeds the replication limit of 6,000 bytes.
21063 16 No Table '%s' cannot participate in updatable subscriptions because it is published for merge replication.
21064 16 No The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Queue Reader Agent for subscription initialization. Try again after the (re)initialization completes.
21070 16 No This subscription does not support automatic reinitialization (subscribed with the 'no sync' option). To reinitialize this subscription, you must drop and re-create the subscription.
21071 10 No Cannot reinitialize article '%s' in subscription '%s:%s' to publication '%s' (subscribed with the 'no sync' option).
21072 16 No The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subscription to receive data.
21073 16 No The publication specified does not exist.
21074 16 No The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.
21075 10 No The initial snapshot for publication '%s' is not yet available.
21076 10 No The initial snapshot for article '%s' is not yet available.
21077 10 No Deactivated initial snapshot for anonymous publication(s). New subscriptions must wait for the next scheduled snapshot.
21078 16 No Table '%s' does not exist in the Subscriber database.
21079 16 No The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it.
21080 16 No The 'msrepl_tran_version' column must be in the vertical partition of the article that is enabled for updatable subscriptions; it cannot be dropped.
21081 16 No Server setting 'Allow triggers to be fired which fire other triggers (nested triggers)' must exist on updatable Subscribers.
21082 16 No Database property 'IsRecursiveTriggersEnabled' has to be false for subscription databases at Subscribers that allow updatable subscriptions.
21083 16 No Database compatibility level at immediate updating Subscribers cannot be less than 70.
21084 16 No Publication '%s' does not allow anonymous subscriptions.
21085 16 No The retention period must be less than the retention period for the distribution database.
21086 16 No The retention period for the distribution database must be greater than the retention period of any existing non-merge publications.
21087 16 No Client subscriptions and anonymous subscriptions cannot republish data. To republish data from this database, the subscription to the root Publisher must be a server subscription with a priority greater than 0. Drop the current subscription and create a server subscription.
21088 10 No The initial snapshot for the publication is not yet available.
21089 16 No Only members of the sysadmin fixed server role can perform this operation.
21090 16 No Cannot upgrade merge replication metadata. Attempt the upgrade again by running the Merge Agent for the Subscriber or by running the Snapshot Agent for the Publisher.
21091 16 No Global subscribers with priority 0 are not allowed to create merge publications.
21101 10 No The custom command name %s specified for parameter %s will be ignored. A system generated name will be used instead. The publication allows %s and command names need not be specified.
21105 16 No This edition of SQL Server cannot act as a Publisher or Distributor for replication.
21106 16 No This edition of SQL Server does not support publications.
21107 16 No '%ls' is not a table or view.
21108 16 No This edition of SQL Server does not support transactional publications.
21109 16 No The parameters @xact_seqno_start and @xact_seqno_end must be identical if @command_id is specified.
21110 16 No @xact_seqno_start and @publisher_database_id must be specified if @command_id is specified.
21111 16 No '%s' is not a valid parameter for the Snapshot Agent.
21112 16 No '%s' is not a valid parameter for the Log Reader Agent.
21113 16 No '%s' is not a valid parameter for the Distribution Agent.
21114 16 No '%s' is not a valid parameter for the Merge Agent.
21115 16 No %d is not a valid value for the '%s' parameter. The value must be a positive integer.
21116 16 No '%s' is not a valid value for the '%s' parameter. The value must be 1, 2, or 3.
21117 16 No '%s' is not a valid value for the '%s' parameter. The value must be 0, 1, or 2.
21118 16 No '%s' is not a valid value for the '%s' parameter. The value must be greater than or equal to 0 and less than or equal to 10,000.
21119 16 No %s is not a valid value for the '%s' parameter. The value must be a non-negative integer.
21120 16 No Only members of the sysadmin fixed server role or db_owner fixed database role, or the owner of the subscription can drop subscription '%s' to publication '%s'.
21121 16 No Only members of the sysadmin fixed server role and '%s' can drop the pull subscription to the publication '%s'.
21122 16 No Cannot drop the distribution database '%s' because it is currently in use.
21123 16 No The agent profile '%s' could not be found at the Distributor.
21124 16 No Cannot find the table name or the table owner corresponding to the alternative table ID(nickname) '%d' in sysmergearticles.
21125 16 No A table used in merge replication must have at least one non-computed column.
21126 16 No Pull subscriptions cannot be created in the same database as the publication.
21127 16 No Only global merge subscriptions can be added to database '%s'.
21128 16 No Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first.
21129 16 No Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first.
21130 16 No Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first.
21131 16 No There are existing subscriptions to heterogeneous publication '%s'. To add new articles, first drop the existing subscriptions to the publication.
21132 16 No Cannot create transactional subscription to merge publication '%s'. The publication type should be either transactional(0) or snapshot(1) for this operation.
21133 16 No Publication '%s' is not enabled to use an independent agent.
21134 16 No The specified job ID must identify a Distribution Agent or a Merge Agent job.
21135 16 No Detected inconsistencies in the replication agent table. The specified job ID does not correspond to an entry in '%ls'.
21136 16 No Detected inconsistencies in the replication agent table. The specified job ID corresponds to multiple entries in '%ls'.
21137 16 No This procedure supports only remote execution of push subscription agents.
21138 16 No The 'offload_server' property cannot be the same as the Distributor name.
21139 16 No Could not determine the Subscriber name for distributed agent execution.
21140 16 No Agent execution cannot be distributed to a Subscriber that resides on the same server as the Distributor.
21141 16 No The @change_active flag may not be specified for articles with manual filters or views.
21142 16 No The SQL Server '%s' could not obtain Windows group membership information for login '%s'. Verify that the Windows account has access to the domain of the login.
21143 16 No The custom stored procedure schema option is invalid for a snapshot publication article.
21144 16 No Cannot subscribe to publication of sync_type 'dump database' because the Subscriber has subscriptions to other publications.
21145 16 No Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type 'dump database'.
21146 16 No @use_ftp cannot be 'true' while @alt_snapshot_folder is neither NULL nor empty.
21147 16 No The '%s' database is not published for merge replication.
21148 16 No Both @subscriber and @subscriberdb must be specified with non-null values simultaneously, or both must be left unspecified.
21149 16 No The '%s' database is not published for transactional or snapshot replication.
21150 16 No Unable to determine the snapshot folder for the specified subscription because the specified Subscriber is not known to the Distributor.
21151 16 No Pre- and post-snapshot commands are not supported for a publication that may support non-SQL Server Subscribers by using the character-mode bcp as the synchronization method.
21152 16 No Cannot create a subscription of sync_type 'none' to a publication using the 'concurrent' or 'concurrent_c' synchronization method.
21153 16 No Cannot create article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber.
21154 16 No Cannot change article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber.
21155 16 No Cannot change article '%s'. articles that are part of a concurrent synchronization publication can not have ins_cmd/del_cmd which exceeds %d characters .
21156 16 No The @status parameter value must be 'initiated' or 'active'.
21157 16 No The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined.
21158 16 No For a publication to be enabled for the Internet, the 'ftp_address' property must not be null.
21159 16 No If a publication is enabled for the Internet, the 'alt_snapshot_folder' property must be non-empty.
21160 16 No The 'ftp_port' property must be a non-negative integer < 65536.
21161 16 No Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers.
21162 16 No It is invalid to exclude the rowguid column for the table from the partition.
21163 16 No It is not possible to add column '%s' to article '%s' because the snapshot for publication '%s' has been run.
21164 16 No Column '%s' cannot be included in a vertical partition because it is neither nullable nor defined with a default value.
21165 16 No Column '%s' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value.
21166 16 No Column '%s' does not exist.
21167 16 No The specified job ID does not represent a %s agent job for any push subscription in this database.
21168 16 No Only members of the sysadmin fixed server role, members of the db_owner fixed database role, and owners of subscriptions served by the specified replication agent job can modify the agent offload settings.
21169 16 No Could not identify the Publisher '%s' at the Distributor '%s'. Make sure that the server '%s' is registered at the Distributor.
21170 16 No The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, SQL Server 2005, and OLE DB Subscribers can use transformable subscriptions.
21171 16 No Could not find package '%s' in msdb at server '%s'.
21172 16 No The publication has to be in 'character', 'concurrent_c', or 'database snapshot character' bcp mode to allow DTS.
21173 16 No The publication has to be 'independent_agent type' to allow DTS.
21174 16 No Because this publication allows transformable subscriptions using DTS, it requires autogenerated stored procedures and parameterized commands, which are set using default value for the @status.
21175 16 No You cannot change the ins_cmd, upd_cmd, or del_cmd article properties because the publication allows Data Transformation Services or updatable subscriptions.
21176 16 No Only members of the sysadmin fixed server role, db_owner fixed database role, or the creator of the subscription can change the subscription properties.
21177 16 No Could not create column list because it is too long. Create the list manually.
21178 16 No Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions using DTS. To allow transformable subscriptions, you must drop the publication and then and re-create it, specifying that transformable subscriptions are allowed.
21179 16 No Invalid @dts_package_location parameter value. Valid options are 'Distributor' or 'Subscriber'.
21180 16 No A publication that allows DTS cannot be enabled for updatable subscriptions.
21181 16 No @dts_package_name can be set for push subscriptions only.
21182 16 No The @agent_type parameter must be one of 'distribution', 'merge', or NULL.
21183 16 No Invalid property name '%s'.
21184 16 No %s parameter is incorrect: it should be '%s', '%s' or '%s'.
21185 16 No The subscription is not initialized or not created for failover mode operations.
21186 16 No Subscription for Publisher '%s' does not have a valid queue_id.
21187 16 No The current mode is the same as the requested mode.
21188 10 No Changed update mode from [%s] to [%s].
21189 16 No The queue for this subscription with queue_id = '%s' is not empty. Run the Queue Reader Agent to make sure the queue is empty before setting mode from [queued] to [immediate].
21190 10 No Overriding queue check for setting mode from [%s] to [%s].
21192 16 No MSrepl_tran_version column is a predefined column used for replication and can be only of data type uniqueidentifier
21193 16 No @identity_range, @pub_identity_range, or @threshold cannot be NULL when @identityrangemanagementoption is set to AUTO.
21194 16 No Cannot support identity range management because this table does not have an identity column.
21195 16 No A valid identity range is not available. Check the data type of the identity column.
21196 16 No Identity automation failed.
21197 16 No Failed to allocate new identity range.
21198 16 No Schema replication failed.
21199 16 No This change cannot take effect until you run the snapshot again.
21200 16 No Publication '%s' does not exist.
21201 16 No Dropping a column that is being used by a merge filter clause is not allowed.
21202 16 No It is not possible to drop column '%s' to article '%s' because the snapshot for publication '%s' has already been run.
21203 10 No Duplicate rows found in %s. Unique index not created.
21204 16 No The publication '%s' does not allow subscription copy or its subscription has not been synchronized.
21205 16 No The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes.
21206 16 No Cannot resolve load hint for object %d because the object is not a user table.
21207 16 No Cannot find source object ID information for article %d.
21208 16 No This step failed because column '%s' exists in the vertical partition.
21209 16 No This step failed because column '%s' does not exist in the vertical partition.
21210 16 No The publication must be immediate_sync type to allow subscription copy.
21211 16 No The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach it using sp_attach_subscription.
21212 16 No Cannot copy subscription. Only single file subscription databases are supported for this operation.
21213 16 No Subscribers cannot subscribe to publications that allow DTS without using a DTS package.
21214 16 No Cannot create file '%s' because it already exists.
21215 16 No An alternate synchronization partner can be configured only at the Publisher.
21216 16 No Publisher '%s', publisher database '%s', and publication '%s' are not valid synchronization partners.
21217 10 No Publication of '%s' data from Publisher '%s'.
21218 16 No The creation_script property cannot be NULL if a schema option of 0x0000000000000000 is specified for the article.
21219 16 No The specified source object must be a stored procedure object if it is published as a 'proc schema only' type article.
21220 16 No Unable to add the article '%s' because a snapshot has been generated for the publication '%s'.
21221 16 No The specified source object must be a view object if it is going to be as a 'view schema only' type article.
21222 16 No The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, 0x00001000, 0x00002000, 0x00400000, 0x02000000, 0x08000000, 0x10000000, 0x20000000, 0x40000000, and 0x80000000.
21223 16 No The @pre_creation_command parameter for a schema only article must be either 'none' or 'drop'.
21224 16 No '%s' is not a valid property for a schema only article.
21225 16 No The 'offload_server' property cannot be NULL or empty if the pull subscription agent is to be enabled for remote activation.
21226 16 No The database '%s' does not have a pull subscription to the specified publication.
21227 16 No The 'offload_server' property cannot be the same as the Subscriber server name.
21228 16 No The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' type article.
21229 16 No The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, 0x00002000, 0x00040000, 0x00100000, 0x00200000, 0x00400000, 0x00800000, 0x01000000, 0x08000000, 0x40000000, and 0x80000000.
21230 16 No Do not call this stored procedure for schema change because the current database is not enabled for replication.
21231 16 No Automatic identity range support is useful only for publications that allow updating subscribers.
21232 16 No Identity range values must be positive integers that are greater than 1.
21233 16 No Threshold value must be from 1 through 100.
21234 16 No Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set 'identity_insert' settings at the Subscriber.
21235 16 No Article property '%s' can be set only when the article uses automatic identity range management.
21236 16 No The subscription(s) to Publisher '%s' does not allow subscription copy or it has not been synchronized.
21237 16 No There is a push subscription to Publisher '%s'. Only pull and anonymous subscriptions can be copied.
21238 16 No This database either is a publisher, or there is a push subscription to publication '%s'. Only pull and anonymous subscriptions can be copied.
21239 16 No Cannot copy subscriptions because there is no synchronized subscription found in the database.
21240 16 No The table '%s' is already published as another article with a different automatic identity support option.
21241 16 No The threshold value should be from 1 through 100.
21242 16 No Conflict table for article '%s' could not be created successfully.
21243 16 No Publisher '%s', publication database '%s', and publication '%s' could not be added to the list of synchronization partners.
21244 16 No Character mode publication does not support vertical filtering when the base table does not support column-level tracking.
21245 16 No Table '%s' is not part of publication '%s'.
21246 16 No This step failed because table '%s' is not part of any publication.
21247 16 No Cannot create file at '%s'. Ensure the file path is valid.
21248 16 No Cannot attach subscription file '%s'. Ensure the file path is valid and the file is updatable.
21249 16 No OLE DB or ODBC Subscribers cannot subscribe to article '%s' in publication '%s' because the article has a timestamp column and the publication is 'allow_queued_tran' (allows queued updating subscriptions).
21250 16 No Primary key column '%s' cannot be excluded from a vertical partition.
21251 16 No Publisher '%s', publisher database '%s', publication '%s' could not be removed from the list of synchronization partners.
21252 16 No It is invalid to remove the default Publisher '%s', publication database '%s', and publication '%s' from the list of synchronization partners
21253 16 No Parameter '@add_to_active_directory' cannot be set to TRUE because Active Directory client package is not installed properly on the machine where SQL Server is running.
21254 16 No The Active Directory operation on publication '%s' could not be completed because Active Directory client package is not installed properly on the machine where SQL Server is running.
21255 16 No Column '%s' already exists in table '%s'.
21256 16 No A column used in filter clause '%s' either does not exist in the table '%s' or cannot be excluded from the current partition.
21257 16 No Invalid property '%s' for article '%s'.
21258 16 No You must first drop all existing merge publications to add an anonymous or local subscription to database '%s'.
21259 16 No Invalid property value '%s'. See SQL Server Books Online for a list of valid parameters for sp_changemergearticle.
21260 16 No Schema replication failed because database '%s' on server '%s' is not the original Publisher of table '%s'.
21261 16 No The offload server must be specified if the agent for this subscription is to be offloaded for remote execution.
21262 16 No Failed to drop column '%s' from the partition because a computed column is accessing it.
21263 16 No Parameter '%s' cannot be NULL or an empty string.
21264 16 No Column '%s' cannot be dropped from table '%s' because it is a primary key column.
21265 16 No Column '%s' cannot be dropped from table '%s' because there is a unique index accessing this column.
21266 16 No Cannot publish table '%s' for both a merge publication and a publication with the updatable subscribers option.
21267 10 No Invalid value for queue type was specified. Valid values = (%s).
21268 10 No Cannot change the parameter %s while there are subscriptions to the publication.
21269 16 No Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication.
21270 10 No Queued snapshot publication property '%s' cannot have the value '%s'.
21272 16 No Cannot clean up the meta data for publication '%s' because other publications are using one or more articles in this publication.
21273 16 No You must upgrade the Subscriber to SQL Server 2000 to create updatable subscriptions when the Publisher is SQL Server 2000 or higher.
21274 16 No Invalid publication name '%s'.
21275 16 No Cannot publish the schema-bound view '%ls'. The value specified for the @type parameter must be "indexed view schema only" (for snapshot or transactional replication) or "indexed view logbased" (for transactional replication only).
21276 16 No The type must be 'table' or '( view | indexed view | proc | func ) schema only'.
21277 16 No Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view schema only" or "indexed view logbased") can be used only for indexed views. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique clustered index.
21278 16 No Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view logbased") requires that the view be schema bound with a unique clustered index. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique clustered index.
21279 16 No The 'schema_option' property for a merge article cannot be changed after a snapshot is generated for the publication. To change the 'schema_option' property of this article the corresponding merge publication must be dropped and re-created.
21280 16 No Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at transaction level.
21281 16 No Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level.
21282 16 No @identity_range, @pub_identity_range, and @threshold must be NULL when @identityrangemanagementoption is set to 'none' or 'manual'.
21283 16 No Column '%s' of table '%s' cannot be excluded from a vertical partition because there is a computed column that depends on it.
21284 16 No Failed to drop column '%s' from table '%s'.
21285 16 No Failed to add column '%s' to table '%s'.
21286 16 No Conflict table '%s' does not exist.
21287 16 No The specified @destination_folder is not a valid path of an existing folder.
21288 16 No Could not create the snapshot directory structure in the specified @destination_folder.
21289 16 No Either the snapshot files have not been generated or they have been cleaned up.
21290 16 No The identity range value provided has exceeded the maximum value allowed.
21291 16 No The specified automatic identity support parameters conflict with the settings in another article.
21292 16 No Object '%s' cannot be published twice in the same publication.
21293 10 No Warning: adding updatable subscription for article '%s' may cause data inconsistency as the source table is already subscribed to '%s'
21294 16 No Either @publisher (and @publisher_db) or @subscriber (and @subscriber_db) must be specified, but both cannot be specified.
21295 16 No Publication '%s' does not contain any article that uses automatic identity range management.
21296 16 No Parameter @resync_type must be either 0, 1, 2.
21297 16 No Invalid resync type. No validation has been performed for this subscription.
21298 16 No Failed to resynchronize this subscription.
21299 16 No Invalid Subscriber partition validation expression '%s'.
21300 10 No The resolver information was specified without specifying the resolver to be used for article '%s'. The default resolver will be used.
21301 16 No The resolver information should be specified while using the '%s' resolver.
21302 16 No The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%s' resolver.
21303 16 No The article '%s' should enable column tracking to use the '%s' resolver. The default resolver will be used to resolve conflicts on this article.
21304 16 No The merge triggers could not be created on the table '%s'.
21305 16 No The schema change information could not be updated at the subscription database.
21306 16 No The copy of the subscription could not be made because the subscription to publication '%s' has expired.
21307 16 No The subscription could not be attached because the subscription to publication '%s' has expired.
21308 10 No Rowcount validation profile.
21309 10 No Profile used by the Merge Agent to perform rowcount validation.
21310 10 No Rowcount and checksum validation profile.
21311 10 No Profile used by the Merge Agent to perform rowcount and checksum validation.
21312 10 No Cannot change this publication property because there are active subscriptions to this publication.
21313 10 No Subscriber partition validation expression must be NULL for static publications.
21314 10 No There must be one and only one of '%s' and '%s' that is not NULL.
21315 10 No Failed to adjust Publisher identity range for table '%s'.
21316 10 No Failed to adjust Publisher identity range for publication '%s'.
21317 10 No A push subscription to the publication '%s' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions.
21318 10 No Table '%s' must have at least one column that is included in the vertical partition.
21319 16 No Could not find the Snapshot Agent command line for the specified publication. Check that a valid regular snapshot job exists on the distributor.
21320 16 No The version of the Distributor cannot be lower than the version of the Publisher.
21321 16 No The parameter @dynamic_snapshot_location cannot be an empty string.
21322 16 No This publication logs conflicts on both replicas. Pre-SQL Server 2005 subscribers will not honor this setting.
21323 16 No A dynamic snapshot job can be scheduled only for a publication with dynamic filtering enabled.
21324 16 No A Snapshot Agent must be added for the specified publication before a dynamic snapshot job can be scheduled.
21325 16 No Could not find the Snapshot Agent ID for the specified publication.
21326 16 No Could not find the dynamic snapshot job with a '%ls' of '%ls' for the specified publication.
21327 16 No '%ls' is not a valid dynamic snapshot job name.
21328 16 No The specified dynamic snapshot job name '%ls' is already in use. Try the operation again with a different job name.
21329 16 No Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_snapshot_jobname, can be specified with a nondefault value.
21330 16 No Cannot create a sub-directory under the snapshot folder (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to create a sub-directory under the snapshot folder.
21331 16 No Cannot copy user script file to the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories.
21332 16 No Failed to retrieve information about the publication : %ls. Check the name again.
21333 16 No A generation that was expected to be in %s.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription database, reinitialize the subscription. If this error occurred in a publication database, restore the database from a backup.
21334 16 No Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant
21335 16 No Warning: column '%s' already exists in the vertical partition.
21336 16 No Warning: column '%s' does not exist in the vertical partition.
21337 16 No Invalid @subscriber_type value. Valid options are 'local' and 'global'.
21338 16 No Cannot execute sp_dropmergearticle if the publication has a Subscriber that is running on a version of SQL Server 2000 or earlier. Drop and re-create the publication without the article '%s' or set the publication compatibility level of publication '%s' to '90RTM' before calling sp_dropmergearticle.
21339 10 No Warning: the publication uses a feature that is only supported only by subscribers running '%s' or higher.
21340 16 No On Demand user script cannot be applied to the snapshot publication.
21341 16 No @dynamic_snapshot_location cannot be a non-empty string while @alt_snapshot_folder is neither empty nor null.
21342 16 No @dynamic_snapshot_location cannot be a non-empty string while @use_ftp is 'true'.
21343 16 No Could not find stored procedure '%s'.
21344 16 No Invalid value specified for %ls parameter.
21345 16 No Excluding the last column in the partition is not allowed.
21346 16 No Failed to change the owner of '%s' to '%s'.
21347 16 No Column '%s' cannot be excluded from the vertical partitioning because there is a unique index accessing this column.
21348 16 No Invalid property name '%s'.
21349 10 No Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because decentralized conflict logging is designated.
21350 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a compressed snapshot is used.
21351 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because vertical filters are being used.
21352 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because schema replication is performed.
21353 10 No Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide reinitialization is performed.
21354 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because publication wide reinitialization is performed.
21355 10 No Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because merge metadata cleanup task is performed.
21356 10 No Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide validation task is performed.
21357 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because data types new in SQL Server 2000 exist in one of its articles.
21358 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because at least one timestamp column exists in one of its articles.
21359 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because automatic identity ranges are being used.
21360 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a new article has been added to the publication after its snapshot has been generated.
21361 16 No The specified @agent_jobid is not a valid job id for a '%s' agent job.
21362 16 No Merge filter '%s' does not exist.
21363 16 No Failed to add publication '%s' to Active Directory. %s
21364 16 No Could not add article '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
21365 16 No Could not add article '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions.
21366 16 No Could not add filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
21367 16 No Could not add filter '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions.
21368 16 No The specified offload server name contains the invalid character '%s'.
21369 16 No Could not remove publication '%s' from Active Directory.
21370 16 No The resync date specified '%s' is not a valid date.
21371 10 No Could not propagate the change on publication '%s' to Active Directory.
21372 16 No Cannot drop filter '%s' from publication '%s' because its snapshot has been run and this publication could have active subscriptions. Set @force_reinit_subscription to 1 to reinitialize all subscriptions and drop the filter.
21373 11 No Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available.
21374 10 No Upgrading distribution settings and system objects in database %s.
21375 10 No Upgrading publication settings and system objects in database %s.
21376 11 No Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available.
21377 10 No Upgrading subscription settings and system objects in database %s.
21378 16 No Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again.
21379 16 No Cannot drop article '%s' from publication '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
21380 16 No Cannot add timestamp column without forcing reinitialization. Set @force_reinit_subscription to 1 to force reinitialization.
21381 16 No Cannot add (drop) column to table '%s' because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subscription to 1 to force reinitialization.
21382 16 No Cannot drop filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
21383 16 No Cannot enable a merge publication on this server because the working directory of its Distributors is not using a UNC path.
21384 16 No The specified subscription does not exist or has not been synchronized yet.
21385 16 No Snapshot failed to process publication '%s'. Possibly due to active schema change activity or new articles being added.
21386 16 No Schema change failed on object '%s'. Possibly due to active snapshot or other schema change activity.
21387 16 No The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider using the default mechanism instead of the dynamic snapshot for initializing the specified subscription.
21388 10 No The concurrent snapshot for publication '%s' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication must be restarted until a complete snapshot is generated.
21389 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because column-level collation is scripted out with the article schema creation script.
21390 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because extended properties are scripted out with the article schema creation script.
21391 10 No Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because it contains schema-only articles.
21392 16 No Row filter(%s) is invalid for column partition(%s) for article '%s' in publication '%s'.
21393 16 No Dropping row filter(%s) for article '%s' in '%s'. Reissue sp_articlefilter and sp_articleview to create a row filter.
21394 16 No Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include DRI constraints.
21395 10 No This column cannot be included in a transactional publication because the column ID is greater than 255.
21396 16 No The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Server Books Online for a list of valid values.
21397 16 No The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at the Distributor. Retry the operation again with a more up-to-date log, differential, or full database backup.
21398 16 No Could not complete setting up the no-sync subscription at the Distributor while the distribution cleanup agent is running. The operation has a greater chance of success if the distribution cleanup agent is temporarily disabled.
21399 16 No The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable at the Distributor. Specify a higher LSN.
21400 16 No Article property must be changed at the original Publisher of article '%s'.
21401 16 No Article name cannot be 'all'.
21402 16 No Incorrect value for parameter '%s'.
21403 10 No The 'max_concurrent_dynamic_snapshots' publication property must be greater than or equal to zero.
21404 10 No '%s' is not a valid value for the '%s' parameter. The value must be a positive integer greater than 300 or 0.
21405 10 No '%s' is not a valid value for the '%s' parameter. The value must be an integer greater than or equal to %d.
21406 10 No '%s' is not a valid value for the '%s' parameter. The value must be 0 or 1.
21407 16 No Cannot create the subscription. If you specify a value of "initialize with backup" for the @sync_type parameter, you must subscribe to all articles in the publication by specifying a value of "all" for the @article parameter.
21408 16 No Cannot create the subscription. You must specify a value of "Active" or "Subscribed" for the @status parameter. This is because the value specified for the @sync_type parameter is "initialize with backup" or "replication support only".
21409 16 No Only one of parameters %s and %s can be set.
21410 16 No Snapshot Agent startup message.
21411 16 No Distribution Agent startup message.
21412 16 No Merge Agent startup message.
21413 16 No Failed to acquire the application lock indicating the front of the queue.
21414 10 No Unexpected failure acquiring an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available.
21415 10 No Unexpected failure releasing an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available.
21416 10 No Property '%s' of article '%s' cannot be changed.
21417 10 No Having a queue timeout value of over 12 hours is not allowed.
21419 10 No Filter '%s' of article '%s' cannot be changed.
21420 10 No Subscription property '%s' cannot be changed.
21421 10 No Article '%s' cannot be dropped because there are other articles using it as a join article.
21422 16 No Queue Reader Agent startup message.
21423 16 No Either the publication '%s' does not exist or you do not have sufficient permissions to access it. Ensure that the publication exists and that the account under which the Merge Agent connects to the Publisher is included in the publication access list (PAL).
21424 16 No The @publisher parameter must be NULL for SQL Server publishers.
21425 16 No The @publisher parameter may not be NULL for heterogeneous publishers.
21426 16 No No shared agent subscription exists for publication '%s' and the subscriber/subscriber database pair '%s'/'%s'.
21450 16 No The replication %s could not be upgraded for %s databases. Ensure that %s is upgraded and execute %s again.
21451 16 No The %s %s (%s) login (%s) password has been changed.
21452 10 No Warning: The %s agent job has been implicitly created and will run under the SQL Server Agent Service Account.
21454 16 No The internal procedure sp_MStran_is_snapshot_required must be executed at the Distributor if the @run_at_distributor parameter has a value of 1. If the problem persists, contact Microsoft Customer Support Services.
21456 16 No Value provided for parameter %s is not valid.
21460 16 No The primary key for source table "%s" includes the timestamp column "%s". Cannot create the article for the specified publication because it allows updating Subscribers.
21481 16 No Cannot create replication subscription(s) in the master database. Choose another database for creating subscriptions.
21482 16 No %s can only be executed in the "%s" database.
21484 16 No Article validation was requested for snapshot publication "%s". Article validation is only valid for transactional publications.
21485 16 No Tracer tokens cannot be posted for a snapshot publication.
21486 16 No An error occurred while logging the tracer token history information. The tracer token could not be posted.
21487 16 No An error occurred while inserting the tracer token to the log. The tracer token could not be posted.
21488 16 No No active subscriptions were found. The publication must have active subscriptions in order to post a tracer token.
21489 16 No A database '%s' already exists. If you intend this to be your distribution database set @existing_db = 1.
21490 16 No The value specified for the %s parameter of sp_mergearticlecolumn must be '%s'. A value of 'true' is allowed only when this procedure is called by another replication procedure. Either set the value of the @schema_replication parameter to 'false' or do not specify a value.
21499 16 No The procedure %s failed to %s the resource %s. Server error = %d.
21500 10 No Invalid subscription type is specified. A subscription to publication '%s' already exists in the database with a different subscription type.
21501 10 No The supplied resolver information does not specify a valid column name to be used for conflict resolution by '%s'.
21502 10 No The publication '%s' does not allow the subscription to synchronize to an alternate synchronization partner.
21503 10 No Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes have completed.
21504 10 No Cleanup of merge meta data at republisher '%s'.'%s' could not be performed because merge processes are propagating changes to the republisher. All subscriptions to this republisher must be reinitialized.
21505 10 No Changes to publication '%s' cannot be merged because it has been marked inactive.
21506 10 No sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge meta data cleanup.
21507 10 No All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data cleanup.
21508 10 No Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes have completed.
21509 10 No Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed after all republishers have quiesced their changes.
21510 10 No Data changes are not allowed while cleanup of merge meta data is in progress.
21511 10 No Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row.
21512 18 No %ls: The %ls parameter is shorter than the minimum required size.
21514 16 No Cannot complete the requested operation in the subscription database because a snapshot is currently being delivered to the database. Perform the operation again at a later time. To stop the delivery of the snapshot, stop the Distribution Agent or Merge Agent associated with the subscription.
21515 18 No Replication custom procedures will not be scripted because the specified publication '%s' is a snapshot publication.
21516 10 No Transactional replication custom procedures for publication '%s' from database '%s':
21517 10 No Replication custom procedures will not be scripted for article '%s' because the auto-generate custom procedures schema option is not enabled.
21518 10 No Replication custom procedures for article '%s':
21519 10 No Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements.
21520 10 No Custom procedure will not be scripted because '%s' is not a recognized article update command syntax.
21521 16 No Some generation values are above the upper limit of %d used in SQL Server 2000. Change the publication_compatibility_level of the publication to 90 to make this work.
21522 16 No This article cannot use the '%s' feature because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication '%s' to '90RTM'.
21523 16 No Adding column '%s' to table '%s' failed. Articles can have at most %d columns, including columns that have been filtered.
21525 16 No A lightweight replica must be anonymous.
21526 16 No Article '%s' already belongs to a subscription with a different value for the @lightweight property.
21527 16 No Publication '%s' cannot be added to database '%s', because a publication with a lower compatibility level already exists. All merge publications in a database must have the same compatibility level.
21528 16 No Publication '%s' cannot be added to database '%s', because a publication with a higher compatibility level already exists. All merge publications in a database must have the same compatibiliy level.
21530 10 No The schema change failed during execution of an internal replication procedure. For corrective action, see the other error messages that accompany this error message.
21531 10 No The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republishing hierarchy, DDL commands can only be executed at the root Publisher, not at any of the republishing Subscribers.
21532 10 No Cannot add a data definition language trigger for replicating '%.*ls' events.
21533 10 No Cannot insert information into the schema change tracking table sysmergeschemachange.
21535 16 No The article '%s' is already published in another publication, and is set to use nonoverlapping partitions with multiple subscribers per partition (@partition_options = 2). This setting does not permit the article to be included in more than one publication.
21537 16 No The column '%s' in table '%s' is involved in a foreign key relationship with a column in table '%s', but this column was not found in the specified join clause. A logical record relationship between these tables should include this column.
21538 16 No Table '%s' cannot have table '%s' as a parent in a logical record relationship because it already has a different parent table. A logical record relationship allows only one parent table for a given child table.
21539 16 No A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from the parent table to the child table. Either change the value of the @filter_type parameter, or set the @join_unique_key parameter to 1.
21540 16 No You cannot drop a column defined as data type uniqueidentifier with the rowguidcol property because merge replication uses this column for tracking. To drop the column, you must first drop the table from all publications and subscriptions.
21541 16 No Cannot complete ALTER TABLE command. Do not execute the command 'ALTER TABLE table_name DISABLE TRIGGER ALL' on a published table. Reissue multiple 'ALTER TABLE table_name DISABLE TRIGGER trigger_name' statements to disable each trigger individually on the given table.
21542 16 No Encountered server error %d while executing <%s>.
21543 16 No The schema for the article %s was either not generated properly or was not applied properly during initial synchronization. This may be due to permissions issues. Verify whether the object exists, and whether the necessary permissions are granted.
21544 10 No Value specified for the publication property replicate_ddl is not valid. The value must be 1 or 0.
21545 16 No You cannot disable a trigger used by merge replication on a published table. To drop the trigger, drop the table from the publication.
21546 16 No Cannot replicate the ALTER TABLE command. It contains multiple DROP commands, including a DROP command for a column that is not included in all subscriptions to this article. Use a single DROP command in each ALTER TABLE command.
21547 16 No Encountered server error %d while restoring the log for database %s.
21548 16 No Cannot execute sp_change_subscription_properties. This stored procedure can only be used for publications that have at least one pull subscription.
21549 16 No Cannot add the computed column '%s' to the publication. You must first add all columns on which this column depends; you cannot filter any of these colunmns from the article.
21550 16 No Before you drop the column from the publication, all computed columns that depend on column '%s' must be dropped.
21551 16 No Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation.
21552 16 No Merge data definition language (DDL) error: Dropping a column used in a row filter or a join filter is not allowed. To drop a column used in a row filter, first change the row filter using sp_changemergearticle. To drop a column used in a join filter, first drop the join filter using sp_dropmergefilter.
21561 16 No The value specified for parameter %s = %d is not valid.
21564 16 No The table %s contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it must be set to NOT NULL. Replication failed to alter this column, so you must drop the column and then add the table as an article again using sp_addarticle. Replication will then add the column to the table.
21567 16 No The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications that allow updating subscriptions. If you do not require updating subscriptions, specify a different call format. If you do require updating subscriptions, you must drop the publication and re-create it to specify that updating subscriptions are allowed.
21569 16 No The article %s in the publication %s does not have a valid conflict table entry in the system table sysarticleupdates. This entry is required for publications that allow queued updating subscriptions. Check for errors in the last run of the Snapshot Agent.
21570 16 No Cannot create the logical record relationship. Table '%s' does not have a foreign key referencing table '%s'. A logical record relationship requires a foreign key relationship between the parent and child tables.
21571 16 No Cannot create the logical record relationship in publication '%s'. The use_partition_groups option for the publication must be set to "true" in order to use logical records. Use sp_changemergepublication to set the option to "true".
21572 16 No Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is disabled. To create the logical record relationship, first enable the foreign key constraint.
21573 16 No Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is defined with the NOT FOR REPLICATION option. To add the logical record relationship, first drop the foreign key constraint, and then re-create it without the NOT FOR REPLICATION option.
21574 16 No Cannot add a logical record relationship because the article '%s' is published in publication '%s', which has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM.
21575 16 No The value specified for the property filter_type is not valid. Valid values are 1 (join filter only), 2 (logical record relation only), and 3 (join filter and logical record relation).
21576 16 No Cannot add a logical record relationship between tables '%s' and '%s' because the foreign key column '%s' in table '%s' allows NULL values. Alter the column to disallow NULL values.
21578 16 No In order to use partition_options of 2 (non overlapping partitions with multiple subscriptions per partition) or 3 (non overlapping partitions one subscription per partition) the publication '%s' must be enabled to use partition groups functionality. Use sp_changemergepublication to set 'use_partition_groups' to 'true'.
21579 16 No Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in multiple join filters. Either select a value of 0 or 1 for the @partition_options parameter, or drop all but one of the join filters by using sp_dropmergefilter.
21580 16 No Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in both a row filter and a join filter. Either select a value of 0 or 1 for the @partition_options parameter; drop the join filter by using sp_dropmergefilter; or change the row filter by using sp_changemergepublication.
21581 16 No Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a join filter with a join_unique_key value of 0. Either select a value of 0 or 1 for the @partition_options parameter, or use sp_changemergefilter to specify a value of 1 for join_unique_key.
21582 16 No Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a direct or indirect join filter relationship with parent article "%s". The parent article does not use the same value for partition_options. Use sp_changemergepublication to change the value for one of the articles.
21583 16 No Cannot update the column in article '%s'. The article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property, and the column is involved in a row filter and/or a join filter. In this situation, the column cannot be updated at a Subscriber or republisher; it must be updated at the top-level Publisher.
21584 16 No Cannot insert the row for article '%s'. The row does not belong to the Subscriber's partition, and the article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property. Nonoverlapping partitions do not allow out-of-partition inserts.
21585 16 No Cannot specify custom article ordering in publication '%s' because the publication has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM.
21597 16 No The article includes only the rowguidcol column. You must publish at least one other column.
21598 16 No Modifying DDL triggers created by replication is disallowed since these are required to track DDL changes.
21599 16 No The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; self-joins are not permitted.
21600 16 No Non-SQL Server Publisher [%s] cannot be found. Execute sp_helpdistpublishers to view a list of available Publishers.
21601 16 No The value of the parameter @type must be 'logbased' for Oracle publications.
21603 16 No The refresh of Oracle publisher '%s' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta data has been retained in its failed state to help in diagnosing the cause of the failure. When the problem has been diagnosed and resolved, rerun sp_refresh_heterogeneous_publisher to complete the refresh.
21604 16 No The non-SQL Server Publisher vendor is not valid. Attempt to add the Publisher again. If the problem persists, contact Microsoft Customer Support Services.
21605 16 No Non-SQL Server Publishers must be configured in the context of the distribution database. Execute sp_adddistpublisher in the context of the distribution database.
21606 16 No Parameter "%s" is for non-SQL Server Publishers only. The value of this parameter must be "%s" for a SQL Server Publisher.
21607 16 No sp_refresh_heterogeneous_publisher was unable to obtain publisher information for Oracle publisher '%s'. sp_refresh_heterogeneous_publisher may only be called to refresh Oracle publishers currently defined at the distributor.
21608 16 No Cannot use a value of TRUE for the parameter @ignore_distributor. The value must be FALSE for a non-SQL Server Publisher.
21609 16 No Non-SQL Server publications do not support updatable subscriptions. The properties allow_sync_tran and allow_queued_tran must be "false".
21610 16 No The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher '%s' did not alter any meta data at the Oracle publisher. Make certain that the correct Oracle publisher has been identified and that the requirements for refreshing the Oracle publisher have been met.
21611 16 No Cannot drop the distribution Publisher "%s" because it has publications defined. Drop the publications first.
21612 16 No For non-SQL Server Publishers, the value of the @sync_method parameter must be "character" or "concurrent_c".
21613 16 No Constraint column '%s' not found in table '%s'.
21614 16 No Index column '%s' not found in table '%s',
21615 16 No Unable to find table information for article %s. Local distributor cache may be corrupt.
21616 16 No Cannot find column [%s] in the article. Verify that the column exists in the underlying table, and that it is included in the article.
21617 16 No Unable to run SQL*PLUS. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21617 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21618 16 No The Publisher '%s' does not exist. To view a list of Publishers, use the stored procedure sp_helpdistpublisher.
21619 16 No Must provide both @SelectColumnList and @InsColumnList.
21620 16 No The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21620 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21621 16 No Unable to create the public synonym %s. Verify that the replication administrative user has been granted the CREATE SYNONYM permission.
21622 16 No Unable to grant SELECT permission on the public synonym %s. Verify that the replication administrative user has sufficient permissions.
21623 16 No Unable to update the public synonym 'MSSQLSERVERDISTRIBUTOR' to mark Oracle instance '%s' as a SQL Server publisher.
21624 16 No Unable to locate the registered Oracle OLEDB provider, OraOLEDB.Oracle, at distributor '%s'. Make certain that a current version of the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21624 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21625 16 No Unable to update the publisher table HREPL_PUBLISHER at the Oracle instance '%s'.
21626 16 No Unable to connect to Oracle database server '%s' using the Oracle OLEDB provider OraOLEDB.Oracle. For addition information, see SQL Server Error 21626 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21627 16 No Unable to connect to Oracle database server '%s' using the Microsoft OLEDB provider MSDAORA. For addition information, see SQL Server Error 21627 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21628 16 No Unable to update the registry of distributor '%s' to allow Oracle OLEDB provider OraOLEDB.Oracle to run in process with SQL Server. Make certain that current login is authorized to modify SQL Server owned registry keys. For addition information, see SQL Server Error 21628 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21629 16 No The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not present at the distributor. Make certain that the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21629 in Troubleshooting Oracle Publishers in SQL Server Books Online.
21630 16 No Unable to determine whether the table '%s' is still being published. Contact Customer Support Services.
21631 16 No Cannot unpublish table '%s'; the remote call to the Oracle Publisher failed. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect but the problem persists, drop and reconfigure Oracle publishing.
21632 16 No The parameter %s is not supported for non-SQL Server publications. The value specified for this parameter must be %s.
21633 16 No The publication '%s' could not be added because non-SQL Server Publishers only support the @sync_method parameter values "character" or "concurrent_c".
21634 16 No The parameter %s does not support the value '%s' when using non-SQL Server publications. The value must be %s.
21635 16 No An unsupported schema option combination was specified. Non-SQL Server publications only support the following schema options: 0x01, 0x02, 0x10, 0x40, 0x80, 0x4000, and 0x8000.
21637 16 No %s is required for heterogeneous publications.
21638 16 No You have specified a value of '%s' for the @repl_freq parameter of sp_addpublication. For non-SQL Server publications, this requires one of the following values for the @sync_method parameter: %s.
21639 16 No Heterogeneous publishers can not use trusted connections, set @trusted to false.
21640 16 No Non-SQL Server Publishers do not support a value of 1 for the parameter @thirdparty_flag. When executing the stored procedure sp_adddistpublisher, specify a value of 0 for the parameter.
21641 16 No The "%s" parameter is for non-SQL Server Publishers only. It must be NULL for SQL Server Publishers.
21642 16 No Heterogeneous publishers require a linked server. A linked server named '%s' already exists. Please remove linked server or choose a different publisher name.
21643 16 No The value specified for the parameter '%s' must be MSSQLSERVER, ORACLE, or ORACLE GATEWAY.
21644 16 No %s value of '%s' is not supported for heterogeneous subscribers, must be %s.
21645 16 No The value '%s' is not a valid non-SQL Server Publisher type. For SQL Server 2005, the value must be ORACLE or ORACLE GATEWAY.
21646 16 No The Oracle server [%s] is already defined as the Publisher [%s] on the Distributor [%s].[%s]. Drop the Publisher or drop the public synonym [%s].
21647 16 No The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ensure it is granted the documented permissions.
21649 16 No Cannot change the property '%s'. Non-SQL Server Publishers do not support this property.
21650 16 No The value specified for @rowcount_only for the article '%s' is not 1. For an article in a publication from a non-SQL Server Publisher, 1 is the only valid setting for this parameter.
21651 16 No Failed to execute the HREPL.%s request to Oracle Publisher '%s'. Verify that the Oracle package code exists on the Publisher, and that the replication administrative user account has sufficient permissions.
21653 16 No The database management system (DBMS) %s %s does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms.
21654 16 No The data type %s does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings.
21655 16 No The data type %s already exists.
21656 16 No The data type mapping for %s does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings.
21657 16 No The data type mapping for %s already exists.
21658 16 No The data type mapping does not exist. Verify the list of mappings by querying msdb.dbo.sysdatatypemappings.
21659 16 No Cannot execute this procedure for a SQL Server Publisher. The Publisher must be a non-SQL Server Publisher.
21660 16 No The value specified for the parameter @full_or_fast for article '%s' must be 0, 1, or 2.
21661 16 No The value specified for the @shutdown_agent parameter for article '%s' must be 0 or 1.
21662 16 No The source object [%s].[%s] on the non-SQL Server Publisher was either not found or is not supported. If the object exists, verify that it meets the requirements for being published.
21663 16 No Cannot find a valid primary key for the source table [%s].[%s]. A valid primary key is required to publish the table. Add or correct the primary key definition on the source table.
21664 16 No Index [%s] contains unique nullable column.
21665 16 No Key [%s] contains unique nullable column.
21666 16 No Cannot specify more than %d column names for the index or primary key because this exceeds the maximum number of columns supported by SQL Server. %d columns were specified.
21667 16 No The index "%s" was not created. The index has a key length of at least %d bytes. The maximum key length supported by SQL Server is %d bytes.
21668 16 No The constraint "%s" was not created because one or more columns in the constraint is not published. Either include all columns in the published article, or alter the constraint to remove columns that are not published.
21669 16 No Column [%s] cannot be published because it uses an unsupported data type [%s]. View supported data types by querying msdb.dbo.sysdatatypemappings.
21670 16 No Connection to server [%s] failed.
21671 16 No Cannot execute the procedure. Administration of a non-SQL Server Publisher must be performed at the associated SQL Server Distributor. Execute the procedure at the Distributor.
21672 16 No The login '%s' has insufficient authorization to execute this command.
21673 16 No Test connection to publisher [%s] failed. Verify authentication information.
21674 16 No Unable to update the linked server [%s] for the login [%s].
21675 16 No Cannot specify more than %d indexes for a single table. %d indexes specified. Excess indexes have been ignored.
21676 16 No Heterogeneous subscriber '%s' could not add a subscription for heterogeneous publication '%s' because publication sync method is not 'character', 'concurrent_c', or 'database snapshot character'.
21677 16 No Heterogeneous publisher '%s' cannot be defined as a subscriber.
21678 16 No The parameter "%s" can be set to "%s" only when "%s" is set to "%s".
21679 16 No Peer-to-peer publications only support a '%s' parameter value of %s.
21680 16 No The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %s, OriginatorDB %s, OriginatorDBVersion %d, OriginatorPublicationID %d. Stop and restart the Distribution Agent. If the problem persists, contact Customer Support Services.
21681 16 No The current user '%s' does not have a valid linked server login mapping for non-SQL Server Publisher [%s]. Replication connects to the Publisher through a linked server; use the stored procedure sp_addlinkedsrvlogin to map the user's login to this linked server.
21682 16 No Cannot publish table [%s].[%s]. The replication administraive user requires an explicit SELECT grant, or a SELECT grant through PUBLIC, in order to publish this table. A role-based SELECT grant, if one exists, is not sufficient.
21683 16 No Cannot verify administrator login privileges for Oracle Publisher %s. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS.
21684 16 No The replication administrative user for Oracle Publisher "%s" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql for the required permissions.
21685 16 No Request '%s' for Oracle schema filter for Oracle publisher '%s' failed.
21686 16 No The operation "%s" is not valid. Valid operations are "add", "drop", and "help".
21687 16 No Schema filters are supported only for Oracle Publishers. The Publisher "%s" is a "%s" Publisher.
21688 16 No The current login '%s' is not in the publication access list (PAL) of any publication at Publisher '%s'. Use a login that is in the PAL, or add this login to the PAL.
21689 16 No A NULL @schema value is invalid for add and drop schema filter operations.
21690 10 No The subscriber db cannot be the same as the publisher db when the subscriber is the same as the publisher
21691 10 No sp_mergesubscription_cleanup should be called on the subscription database
21692 16 No Failed to script the subscriber stored procedures for article '%s' in publication '%s'
21694 16 No %s cannot be null or empty when %s is set to 0 (SQL Server Authentication). Specify a login or set security mode to 1 (Windows Authentication).
21695 10 No The replication agent job '%s' was not removed because it has a non-standard name; manually remove the job when it is no longer in use.
21696 16 No The stored procedure only applies to Oracle Publishers. The Publisher '%s' is a %s Publisher.
21698 16 No The parameter '%s' is no longer supported.
21699 10 No Unable to reuse view '%s' because it was not found. Re-creating all system table views. This is an informational message only. No user action is required.
21701 16 No Microsoft SQL Server Additive Conflict Resolver
21702 16 No Microsoft SQL Server Averaging Conflict Resolver
21703 16 No Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver
21704 16 No Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver
21705 16 No Microsoft SQL Server Download Only Conflict Resolver
21706 16 No Microsoft SQL Server Maximum Conflict Resolver
21707 16 No Microsoft SQL Server Merge Text Columns Conflict Resolver
21708 16 No Microsoft SQL Server Minimum Conflict Resolver
21709 16 No Microsoft SQL Server Priority Column Resolver
21710 16 No Microsoft SQL Server Subscriber Always Wins Conflict Resolver
21711 16 No Microsoft SQL Server Upload Only Conflict Resolver
21712 16 No Microsoft SQLServer Stored Procedure Resolver
21715 16 No Cannot register the article resolver %s. This can occur if the account under which SQL Server is running does not have access to the distribution database. Add the class ID and the custom resolver name manually to the MSmerge_articleresolver table in the distribution database.
21717 16 No The article resolver name cannot be an empty string or NULL. Specify a valid value for the @article_resolver parameter.
21718 16 No For a COM resolver, the @resolver_clsid cannot be an empty string or NULL. Specify a valid value for @resolver_clsid.
21719 10 No The Subscriber '%s':'%s' was not marked for reinitialization at the Publisher because the subscription is either anonymous or not valid. Verify that valid values were specified for the @subscriber and @subscriber_db parameters of sp_reinitmergesubscription.
21720 16 No Cannot find a job that matches the ID or name specified in the parameters @dynamic_snapshot_jobid or @dynamic_snapshot_jobname. Verify the values specified for those parameters.
21721 10 No UserScripts
21722 16 No Failed to add an extended trigger for replicating the '%.*ls' event.
21723 16 No The value specified for the @pubid parameter of procedure '%s' is not valid or is NULL. Verify that the Merge Agent is running correctly. Reinitalize the subscription if the problem persists.
21724 10 No Cannot add the foreign key %s with the CASCADE option because table %s is published. Add the NOT FOR REPLICATION clause to the foreign key definition.
21725 16 No Cannot alter the view. An indexed view replicated as a table cannot be altered to a nonindexed view. Drop the view from the publication before attempting to alter it.
21727 14 No Cannot complete the replication operation. The security check for the current user is failing. Only members of the sysadmin fixed server role, or db_owner or db_ddladmin fixed database roles can perform this operation.
21728 16 No The article can support logical record level conflict detection only if it uses logical record conflict resolution.
21729 16 No The @keep_partition_changes property cannot be set to "true." This is because the @publication_compatibility_level property is set to 90RTM or higher and the @use_partition_groups property is set to "true." Set a lower compatibility level or set the @use_partition_groups property to "false."
21730 16 No Table '%s' can not be replicated because it contains imprecise Primary Key column, please recreate table without 'persisted' clause and try again.
21731 16 No Cannot add a constraint or default without an explicit name, because the table is included in a publication that replicates DDL events. Specify a unique name for the constraint and then reissue the DDL statement.
21732 16 No Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parameter '%s'.
21733 16 No Cannot open database %s. The upgrade of replication %s could not be performed. Run %s again from the %s database when the %s is accessible.
21734 16 No Peer-to-peer publications do not support replicating timestamp columns as varbinary(8). You cannot add an article with this option, nor add or alter a table to include a timestamp column as varbinary(8).
21735 16 No Source object [%s].[%s] is a temporary object and cannot be published.
21736 16 No Unable to relocate the article log table to a different tablespace. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect, but the problem persists, it might be caused by insufficient permissions or insufficient space in the tablespace; check for any Oracle error messages.
21737 16 No The property '%s' is not valid for '%s' Publishers.
21738 16 No The property '%s' is not valid for %s publications.
21739 16 No Cannot alter property '%s'. You must first call the stored procedure sp_articleview to initialize the article; the property can then be altered.
21740 16 No Oracle subscriber '%s' not found. Loopback support cannot be checked.
21741 16 No Unable to retrieve distributor information from Oracle publisher '%s'. Bi-directional publishing requires Oracle publisher to exist before the Oracle subscriber.
21742 16 No The Oracle Publisher name is '%s' and the Oracle Subscriber name is '%s'. Bidirectional Oracle publishing requires the Oracle Publisher and Subscriber names to be the same.
21743 16 No Unable to retrieve the originator information for the Oracle subscriber '%s'.
21744 16 No Oracle bidirectional publishing requires parameter '%s' to have a value of '%s'.
21745 16 No Cannot generate a filter view or procedure. Verify that the value specified for the @filter_clause parameter of sp_addarticle can be added to the WHERE clause of a SELECT statement to produce a valid query.
21746 16 No The '%s' character length must not exceed %d.
21747 16 No Cannot establish a connection to the Oracle Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS.
21748 16 No The article was dropped at the Distributor, but information at the Publisher '%s' was not dropped. No action is required; the information is cleaned up if the Publisher is dropped.
21749 16 No The Publisher was dropped at the Distributor, but information on the Publisher '%s' was not dropped. Connect to the Oracle Publisher with SQL*PLUS and drop the replication administrative user.
21750 16 No The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table.
21751 16 No Cannot publish view %s as a table because it does not have a unique clustered index. Publish the view as a view, or add a unique clustered index.
21752 16 No The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber that have updates pending in the queue.
21753 16 No The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ensure your queued subscriptions are properly initialized by running the Snapshot Agent, Distribution Agent, and Queue Reader Agent.
21754 16 No Processing has been terminated. The resultset for sp_getqueuedrows is larger than 16,000, the maximum size that the procedure can return. Run the Queue Reader Agent to flush the queue at the Subscriber before executing this procedure again.
21755 16 No Failed to mark '%s' as a system object.
21756 16 No Based on article settings, table %s should have an identity column, but it does not have one. Verify article settings with sp_helparticle and change them if necessary with sp_changearticle.
21757 16 No The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, but a value of 'read-only' was specified for the @update_mode parameter of sp_addsubscription. To allow updates, you must drop and then re-create the subscription, specifying a different value for @update_mode.
21758 16 No Cannot find a valid Queue Reader Agent ID for the subscription to Publisher %s, database %s, publication %s. The specified subscription to an updating Subscriber publication is not initialized. Run the Snapshot Agent, Distribution Agent, and Queue Reader Agent to initialize the subscription.
21759 16 No Cannot add the column '%s' to the table '%s'. The table already contains the maximum number of columns allowed for an article in a merge publication (246 columns).
21760 11 No Cannot execute the replication script in the 'master' database; the current session will be terminated. The script must be executed in the distribution database, and the master database cannot serve as the distribution database.
21761 20 No Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the script.
21762 10 No The distribution database '%s' has a compatibility level of %d, which is different from that of the master database. The two compatibility levels must be the same, so the distribution database level is being changed to %d. This is an informational message only. No user action is required.
21763 16 No Message Queuing Service is not running. Start this service and retry the operation.
21764 16 No Cannot create the publication. Specifying a value of 'msmq' for the parameter @queue_type is supported only on Microsoft Windows NT platforms. Specify a value of 'sql' for this parameter.
21765 10 No The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow NULLs for updating subscribers.
21766 16 No Table %s contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter of sp_addarticle is set to 'none'. To support immediate updating subscriptions, specify a value of 'manual' or 'auto' for @identitymanagementoption.
21767 10 No Warning: The parameter '%s' is obsolete and is available only for backwards compatibility. It will not be available in future releases. Instead of this parameter, use the parameter '%s'.
21768 16 No When executing sp_adddistributor for a remote Distributor, you must use a password. The password specified for the @password parameter must be the same when the procedure is executed at the Publisher and at the Distributor.
21769 10 No Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, errors will likely occur when moving data from the Publisher to the Subscriber.
21770 10 No Data type mapping from '%s' to '%s' does not exist. Review source and destination data type, length, precision, scale, and nullability. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings.
21771 16 No %s is not within the supported range of %d and %d.
21772 16 No Property "%s" requires the parameters @force_invalidate_snapshot and @force_reinit_subscription to be set to "true".
21773 10 No The distribution database '%s' cannot be opened due to inaccessible files. The database will be dropped, but distribution database cleanup tasks will not occur. Check the database and server error logs for more information about why the database files cannot be accessed.
21774 16 No This procedure is supported only for non-SQL Server Publishers. The Publisher '%s', on which you are executing the procedure, is a SQL Server Publisher.
21775 16 No Failed to generate column bitmap for article '%s'.
21776 16 No Failed to generate published column bitmap for article '%s'.
21777 16 No Failed to generate article view name for article '%s'.
21778 16 No Cannot add Publisher objects to the Oracle Publisher for article '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
21779 10 No Cannot use the specified data type mapping. The matching destination data type for source type %s cannot be found. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings. Verify that the length, precision, scale, and nullability of the source type are correct.
21780 16 No The non-SQL Server Publisher is missing one or more %s objects. Drop and re-create the Publisher and the replication administrative user schema.
21781 16 No Unable to retrieve heterogeneous metadata. Verify connection information
21782 16 No Cannot add primary key column '%s' to article '%s'. If the Publisher is a non-SQL Server Publisher, the primary key could have violated SQL Server limits for number and length of columns. For more information, see errors returned by sp_addarticle.
21783 16 No Cannot add the Publisher triggers and the article log table to the Oracle Publisher for the article '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
21784 16 No You must specify a non-NULL value for the @rowfilter parameter.
21785 16 No Failure to query Oracle XactSet Job attributes for publisher '%s'.
21786 16 No Failure to refresh Oracle XactSet Job for publisher '%s'.
21787 16 No Failure to query Oracle Xact batching enabled flag for publisher '%s'.
21788 16 No Invalid parameter passed to sp_IHSetXactBatching. The bit flag to enable/disable Xact batching must be 0 or 1.
21789 16 No Failure to set the Oracle Xact batching enabled flag for publisher '%s'.
21790 16 No Cannot publish the table '%s.%s' from the Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
21791 16 No The table '%s.%s' already appears in a transactional publication on Oracle Gateway Publisher '%s'. When using the Oracle Gateway option, a table published using transactional replication can only be included in one publication. To publish this table in more than one publication, you must reconfigure the Oracle Publisher to use the Oracle Complete option.
21792 16 No The table '%s.%s' already appears in the transactional publication '%s' on Publisher '%s'. The Oracle Gateway publishing option (the default) allows a table to be included as an article in any number of snapshot publications, but only in one transactional publication. To publish a table in more than one transactional publication, use the Oracle Complete publishing option. To change publishing options, you must drop and reconfigure the Publisher.
21793 16 No Non-SQL Server Publishers are supported only in the Enterprise and Developer editions of SQL Server. The edition of this instance is %s.
21794 16 No The value specified for the @propertyname parameter is not valid. Use one of the following values: %s.
21795 16 No The value specified for property %s is not valid. Use one of the following values: %s.
21796 16 No The property "xactsetjobinterval" must be assigned a value greater than or equal to 0.
21797 16 No Cannot create the agent job. '%s' must be a valid Windows login in the form : 'MACHINE\Login' or 'DOMAIN\Login'. See the documentation for '%s'.
21798 16 No Cannot execute the replication administrative procedure. The '%s' agent job must be added through '%s' before continuing. See the documentation for '%s'.
21799 16 No The %s agent for Publisher (%s), database (%s), publication (%s) cannot be found. Create the agent with the appropriate procedure: sp_addpublication_snapshot, sp_addlogreader_agent, or sp_addqreader_agent.
21800 16 No The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up.
21801 16 No The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. Check for any errors returned by sp_createagentparameter and errors returned by SQL Server during execution of sp_createagentparameter.
21802 16 No The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value must be an integer less than or equal to '%d'. Verify that replication is installed properly.
21803 16 No Cannot update agent parameter metadata. Replication could not insert parameter '%s' into table '%s'. Verify that replication is properly installed. Check errors returned by SQL Server during execution of sp_createagentparameter.
21804 16 No The value '%d' specified for the @agent_type parameter of sp_getagentparameterlist is not valid. Specify a valid value of 1, 2, 3, 4, or 9.
21805 16 No The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value.
21806 16 No The agent profile creation process cannot validate the specified agent parameter value: the profile_id %d does not exist or it does not support the parameter %s. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value.
21807 16 No For a .NET Assembly Business Logic Handler, the @resolver_clsid must be specified as NULL.
21808 16 No For a .NET Assembly Business Logic Handler, the @resolver_info must contain the class name in '%s' that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface.
21809 10 No DDL replication is not enabled for database '%ls' because its compatibility level is less than 80.
21810 16 No Identity column can only be added to a published table with 'Not For Replication' clause
21811 16 No Cannot drop the column '%s' because it is used by replication: it is referenced in a filter or view by article '%s'. To drop the column, you must first remove the filter from the article.
21812 16 No Cannot perform "Disable Trigger All" on table %s because it belongs to a publication that supports updatable subscriptions (replication adds triggers to tables for these types of publications). You may, however, disable user triggers individually. Specify an individual user trigger name to disable.
21813 16 No Can not disable trigger %s on table %s because it is required by updatable publication.
21814 16 No DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, '%s', '%s' "and try again
21815 16 No Can not alter replicated object '%s' to 'with encrypted'.
21816 16 No An invalid value was specified for parameter '%s'. The value must be '%s' when changing this property.
21817 16 No The property '%s' is only valid for push subscriptions.
21818 10 No The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, see the "sp_addsubscriber" documentation.
21819 16 No Cannot change the property '%s' . This property is only valid for subscriptions that allow updating at the Subscriber. The subscription against which the procedure was called does not allow updates at the Subscriber.
21820 16 No Cannot write to the script file in the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available. Also ensure that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories.
21821 16 No Specify one and only one of the parameters - %s or %s.
21822 16 No Cannot perform %s on %s as entry already exists.
21823 16 No Cannot perform %s on %s as entry does not exist.
21824 16 No Can not add constraints to multiple columns because table %s is published but column %s is not in all active partitions, please use separate DDL statement.
21825 16 No Can not drop constraints in the same DDL statement which drops columns from table %s because the table is published, please use separate DDL statement.
21826 16 No The property '%s' is valid only for %s subscriptions. Use '%s' for %s subscriptions.
21827 16 No The %s parameters have been deprecated and should no longer be used. For more information, see the '%s' documentation.
21828 16 No The proxy account for jobstep_uid (%s) could not be found.
21830 16 No You cannot specify schema_option 0x4 (script identity as identity rather than the base data type) for article '%s'. The value specified for the parameter @identityrangemanagementoption is NONE. To replicate identity as identity, the value must be MANUAL or AUTO for publications that do not support queued updating subscriptions.
21831 16 No The %s already exists. Use '%s' to change any settings/properties.
21832 16 No Only members of the sysadmin fixed server role can perform this operation without specifying %s.
21833 16 No An error occurred when creating a trace event at Oracle publisher '%s'. The trace event could not be posted.
21834 16 No The primary key for '%s.%s' has %d columns. SQL Server supports a maximum of %d columns. Redefine the primary key so that it has no more than the maximum number of columns.
21835 16 No The index for the primary key '%s.%s' is at least %d bytes. SQL Server supports a maximum key length of %d bytes. Reduce the number of columns in the primary key or redefine the columns to use smaller data types.
21836 16 No The distribution agent must be run in single subscription stream mode prior to resetting the subscription xact_seqno.
21837 16 No A replication agent job (%s) for this subscription already exists.
21838 16 No The %s parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling '%s'.
21839 16 No Article '%s' can not support schema_option 0x20 or 0x2000000000 because it contains computed column, check/default constraint or primary key which is based on CLR type column, change @schema_option setting and try again.
21840 16 No Can not add CLR type based computed column or check constraint to table '%s' because article '%s' supports schema_option 0x20.
21841 10 No DDL replication is forcing reinitialization because either publication'%s' uses character mode bcp, or timestamp/identity column is being replicated as base type only for article '%s'.
21842 16 No %s can only be specified/changed for heterogeneous publications when %s is set to %s.
21843 16 No Article '%s' can not be added, an indexed view published as 'indexed view logbased' and a stored procedure in either form of 'proc exec' can not be published if their common base table is also published.
21844 16 No Can not alter XML, CLR type or MAX type column because table is published and article '%s' supports the schema option to map this to a base column type.
21845 16 No Can not alter procedure '%s' to depend on an indexed view published as 'indexed view logbased' or a base table because the indexed view depends on this table as well.
21846 16 No Cannot find a distribution agent job for the specified transactional or snapshot push subscription.
21847 16 No Cannot find a merge agent job for the specified merge push subscription.
21848 16 No The specified pull subscription is not configured with a synchronization agent job.
21850 16 No The property "%s" cannot be changed to "%s" after the value has already been set to "%s".
21851 16 No Peer-to-peer publications only support a "%s" value of %s. Article "%s" currently has a "%s" value of %s. This value must be changed to continue.
21852 16 No Peer-to-peer publications do not support %s. Article "%s" currently has %s. This must be changed to continue.
21853 10 No Warning: The "%s" property for %s "%s" has been changed to "%s" because it is required by %s.
21854 10 No Could not add new article to publication '%s' because of active schema change activities or a snapshot is being generated.
21855 16 No The login %s provided in sp_link_publication is not mapped to any user in publishing database %s.
21856 16 No For a .NET Assembly Business Logic Handler, the .NET Assembly name should be the name of a valid assembly in '%s' that contains the class that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface. Check the registration of the business logic handler to make sure the .NET Assembly name was specified correctly.
21857 10 No Forcing re-initialization for article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore process, please re-create the index and re-sync your data.
21858 16 No Snapshot can not process article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore process, please re-create the index and re-run snapshot.
21859 16 No Cannot change subscription property '%s' because there is no entry for this subscription in the MSsubscription_properties table. Call sp_addmergepullsubscription_agent before changing this property.
21860 10 No Table '%s' in database '%s' is subscribing to transactional queued publication and published for merge for uploading changes, this may cause non-convergence between transactional publisher and subscriber.
21861 16 No The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated.
21862 16 No FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or 'database snapshot character'.
21863 16 No Cannot add the SPARSE property to a column for the article '%s' because merge replication does not support sparse columns.
21864 16 No Cannot publish the article '%s' or add the COLUMN_SET attribute set to its base table '%s' because replication does not support column sets.
21865 16 No The '%s' publication property must be either 'true' or 'false'.
21866 16 No The publication property '%s' can only be set to '%s' when the publication property '%s' is set to '%s'.
21867 16 No ALTER TABLE SWITCH statement failed. The table '%s' belongs to a publication which does not allow switching of partitions
21868 16 No ALTER TABLE SWITCH statement failed. The statement is not allowed because one or more of the tables in this statement is an article with a different destination table or owner.
21869 16 No Cannot add filter between proposed parent article '%s' and proposed child article '%s' since this would introduce a cycle in the filter relationships. The proposed parent is already being filtered by the child.
21871 Publisher %s of database %s has not been redirected.
21879 16 No Unable to query the redirected server '%s' for original publisher '%s' and publisher database '%s' to determine the name of the remote server; Error %d, Error message '%s'.
21889 The SQL Server instance '%s' is not a replication publisher. Run sp_adddistributor on SQL Server instance '%s' with distributor '%s' in order to enable the instance to host the publishing database '%s'. Make certain to specify the same login and password as that used for the original publisher.
21892 Unable to query sys.availability_replicas at the availability group primary associated with virtual network name '%s' for the server names of the member replicas: error = %d, error message = %s.'
21893 The subscribers ( %s ) of original publisher '%s' do not appear as remote servers at redirected publisher '%s'. Run sp_addlinkedserver at the redirected publisher to add these subscribers as remote servers.
21898 The publisher '%s' uses distribution database '%s' and not '%s' which is required in order to host the publishing database '%s'. Run sp_changedistpublisher at distributor '%s' to change the distribution database used by the publisher to '%s'.
21899 The query at the redirected publisher '%s' to determine whether there were sysserver entries for the subscribers of the original publisher '%s' failed with error '%d', error message '%s'.

Errors 22,000 to 22,999

ErrorSeverityEvent LoggedDescription
22101 16 No The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask returned by the CHANGETABLE(CHANGES ...) function.
22102 16 No The arguments supplied are not valid for the CHANGES option of the CHANGETABLE function.
22103 16 No The arguments supplied are not valid for the VERSION option of the CHANGETABLE function.
22104 16 No A table returned by the CHANGETABLE function must be aliased.
22105 16 No Change tracking is not enabled on table '%.*ls'.
22106 16 No The CHANGETABLE function does not support remote data sources.
22107 16 No Object '%.*ls' is of a data type that is not supported by the CHANGETABLE function. The object must be a user-defined table.
22108 16 No The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SELECT statement.
22109 16 No The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128.
22110 16 No The number of columns specified in the CHANGETABLE(VERSION ...) function does not match the number of primary key columns for table '%.*ls'.
22111 16 No The column '%.*ls' specified in the CHANGETABLE(VERSION ...) function is not part of the primary key for table '%.*ls'.
22112 16 No Each primary key column must be specified once in the CHANGETABLE(VERSION ...) function. The column '%.*ls' is specified more than once.
22113 16 No %S_MSG is not allowed because the table is being tracked for change tracking.
22114 16 No Change tracking options for ALTER DATABASE cannot be combined with other ALTER DATABASE options.
22115 16 No Change tracking is enabled for one or more tables in database '%.*ls'. Disable change tracking on each table before disabling it for the database. Use the sys.change_tracking_tables catalog view to obtain a list of tables for which change tracking is enabled.
22116 16 No Change tracking is not supported by this edition of SQL Server.
22500 16 No Unexpected
22501 16 No All articles in the publication passed data validation (rowcount and checksum).
22502 16 No Not All articles in the publication passed data validation (rowcount only)
22503 16 No Initializing.
22504 16 No Applying the snapshot to the Subscriber.
22505 16 No The merge completed with no data changes processed.
22506 16 No No data needed to be merged.
22507 16 No Uploading data changes to the Publisher.
22508 16 No Downloading data changes to the Subscriber.
22509 16 No Retrieving subscription information.
22510 16 No Retrieving publication information.
22511 16 No The merge completed successfully.
22512 16 No Cannot use partition groups with unfiltered publications. Set "use_partition_groups" to "false" using sp_changemergepublication.
22513 16 No Cannot use partition groups because the join filter between the following articles contains one or more functions: "%s" and "%s".
22514 16 No Cannot use partition groups because one or more filters reference the following view, which contains functions: "%s".
22515 16 No The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
22516 16 No The publication "%s" was defined as having dynamic filters, but it does not contain any dynamic filters.
22517 16 No The publication was defined as having no dynamic filters, but contains one or more dynamic filters.
22518 16 No Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: '%s'.
22519 16 No Cannot add a logical record relationship between tables "%s" and "%s" because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
22520 10 No A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
22521 10 No Unable to synchronize the row because the row was updated by a different process outside of replication.
22522 16 No Article '%s' cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot be included in multiple publications or subscriptions, and cannot be republished. To include the article in multiple publications, use sp_changemergearticle to specify a different value for the partition_options property of the existing article.
22523 16 No An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article "%s".
22524 16 No Article '%s' is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the existing article or change the existing article using sp_changemergearticle.
22525 16 No The publication "%s" cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
22526 16 No An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
22527 16 No Invalid value specified for %s. Valid values are 'day', 'days', 'dd', 'year', 'years', 'yy', 'yyyy', 'month', 'months', 'mm', 'week', 'weeks', 'wk', 'hour', 'hours', 'hh', 'minute', 'minutes', 'mi'.
22528 16 No Cannot use a retention period unit other than "days" for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
22529 16 No Cannot change the retention period unit for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
22530 16 No Cannot update any column in article "%s" that is used in a logical record relationship clause.
22531 10 No Initialization.
22532 10 No Upload of Subscriber changes to the Publisher.
22533 10 No Download of Publisher changes to the Subscriber.
22534 16 No Character mode publication does not support partitioned tables.
22535 16 No For heterogeneous publications, the %s parameters should be specified when calling "%s".
22536 16 No The %s parameter value cannot be updated or changed for heterogeneous publications.
22537 16 No The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher).
22538 16 No Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures.
22539 16 No Use of parameters %s is invalid when parameter %s is set to %s.
22540 16 No Cannot change publication "%s" to use sync_mode of "character", because it contains one or more logical record relationships.
22541 16 No Cannot add a logical record relationship in publication "%s" because it uses sync_mode of "character" and could have SQL Server Compact Edition subscribers.
22542 16 No Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subscriber changes), and 3 (disable_outofpartition_subscriber_changes).
22543 16 No When the publication property @allow_partition_realignment is set to "false", the article property @subscriber_upload_options for all articles in the publication must be set to disable uploads.
22544 10 No Warning: The procedure sp_mergecleanupmetadata has been deprecated. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadataretentioncleanup every time it runs, so manual cleanup of metadata is not needed. Ignoring passed-in parameters and calling sp_mergemetadataretentioncleanup.
22545 16 No Cannot add a logical record relationship in publication "%s" because it allows Web synchronization.
22546 16 No Cannot change publication "%s" to allow Web synchronization because it contains one or more logical record relationships.
22547 16 No A concurrent snapshot is not allowed for snapshot publications.
22548 16 No Vertical partitioning is only allowed for log-based articles.
22549 16 No A shared distribution agent (%s) already exists for this subscription.
22550 16 No Cannot drop identity column "%s" from the vertical partition when identityrangemanagementoption is set to auto.
22551 16 No The type "%s" is invalid. Valid types are "merge", "tran", and "both".
22552 16 No A valid value for parameter "@resync_date_str" needs to be provided when "@resync_type" is set to 2.
22553 16 No The parameter "@resync_type" is set to "%d" but this subscription has never been successfully validated.
22554 16 No Cannot change publication "%s" to use the sync_mode of "character" because it uses a retention period unit other than "day". Use sp_changemergepublication to set the retention period unit to "day".
22555 16 No Cannot set the retention period unit to a value other than "day" for publication "%s" because it uses the sync_mode of "character" and may have SQL Server Compact Edition subscribers.
22556 16 No Invalid value for the property "%s". Valid values are 1 and 0.
22557 16 No The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication "%s" to 90RTM.
22558 16 No The status of the schema change could not be updated.
22559 16 No The status of the schema change must be "active" or "skipped".
22560 16 No Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function "%s".
22561 16 No The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication "%s" to 90RTM.
22562 16 No Cannot change the compatibility level of a publication to a value lower than the existing value.
22563 16 No contains one or more articles that do not upload changes
22564 16 No uses ddl replication
22565 16 No uses other than day as unit of retention period
22566 16 No uses logical records
22567 16 No contains one or more articles that use subscription-based or partition-based filtering
22568 16 No contains one or more articles which will not compensate for errors
22569 16 No contains one or more schema only articles
22570 16 No contains one or more articles that use automatic identity range management
22571 16 No contains one or more articles that use datatypes new in SQL Server 2000
22572 16 No contains one or more articles with a timestamp column
22573 16 No uses snapshot compression with snapshot_in_defaultfolder set to false
22574 16 No contains one or more articles that use vertical partitioning
22575 16 No When article property 'published_in_tran_pub' is set to 'true' then article property 'upload_options' has to be set to disable uploads.
22576 10 No Invalid failover_mode value of %d was specified for [%s].[%s].[%s], setting to 0 [immediate].
22577 16 No Failed to add subscription because the allowed number of %s subscriptions for SQL Workgroup Edition Publisher '%s' would be exceeded. The maximum allowed number is %d.
22578 16 No Cannot change publication "%s" to disallow use_partition_groups because it contains one or more logical record relationships. When using logical record relationships the publication must set the @use_partition_groups property to 'true'.
22579 16 No The subscription to publication '%s' was not found but a shared agent does exist. To specify a subscription to a publication that is replicated via a shared agent specify '%s' for the publication name.
22580 16 No Cannot publish database '%s' because it is marked as published on a different server. Before attempting to publish this database, execute sp_replicationdboption, specifying a value of FALSE for 'publish' and 'merge publish'.
22581 16 No Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'sync_mode' of 1 (character mode). Specify a 'sync_mode' of 0 (native mode) for the publication by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
22582 16 No Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'publication_compatibility_level' of less than "90RTM" (SQL Server 2005). Specify a 'publication_compatibility_level' greater than or equal to "90RTM" by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
22583 16 No Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for articles that have a 'schema_option' set to 0x20000000. This converts large object data types to data types that are supported on earlier versions of Microsoft SQL Server. Remove this 'schema_option' setting by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
22584 10 No Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead.
22585 10 No The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%s'. Enabling this option after the article is created can cause replication to fail when the data in a FILESTREAM column exceeds 2GB and there is a conflict during replication. If you want FILESTREAM data to be replicated, drop and re-create the article, and specify the appropriate schema option when you re-create the article.
22586 16 No Column '%s' cannot be added or modified in article '%s' of publication '%s'. The DDL operatoin on hierarchyid and FILESTREAM columns is not supported for publications that have a 'sync_mode' of 1 (character mode) or with a lower than 90RTM backward compatibility level.
22801 16 No Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
22802 16 No Starting the Change Data Capture Cleanup Agent job using low watermark %s.
22803 16 No Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
22804 16 No Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %s but Distributor information cannot be retrieved to determine the state of the logreader agent. Make the Distributor database available, or disable distribution.
22805 10 No For more information, query the sys.dm_cdc_errors dynamic management view.
22806 16 No The originator ID '%s' is not valid. You must specify a non-zero ID that has never been used in the topology.
22807 16 No The publication property '%s' cannot be modified because the peer-to-peer publication '%s' is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection.
22808 16 No Cannot execute procedure '%s'. Publication '%s' must be enabled for peer-to-peer replication before you execute this procedure. To enable the publication for peer-to-peer replication, use sp_changepublication.
22809 10 No The existing conflict table '%s' was dropped.
22810 16 No The @action parameter value is not valid. Valid values are 'enable' and 'disable'.
22811 16 No The roundtrip time-out must be greater than 0.
22812 10 No The roundtrip '%s' finished with timeout: %d seconds.
22813 10 No The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are SQL Server 2008 or later versions.
22814 10 No The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology.
22815 10 No A conflict of type '%s' was detected at peer %d between peer %d (incoming), transaction id %s and peer %d (on disk), transaction id %s
22816 16 No The qualified table name '%s' is too long to be enabled for peer-to-peer conflict detection.
22817 10 No %s has %s.
22818 10 No A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was skipped.
22819 10 No A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming delete was skipped by peer %d. The conflict has to be resolved manually to guarantee data convergence between the peers. For steps on how to resolve the conflict refer to BOL.
22820 10 No A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d.
22821 10 No An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d.
22822 10 No An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d.
22823 10 No An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Check the priority of the destination peer and run data validation to ensure the delete conflict did not result in data non-convergence.
22824 10 No An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d.
22825 10 No An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d.
22827 16 No Peer-to-peer conflict detection alert
22828 16 No The publication '%s' was already %s for peer-to-peer conflict detection.
22829 16 No The command %s failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d.
22830 16 No Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22831 16 No Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22832 16 No Could not update the metadata that indicates table %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22833 16 No Could not update the metadata that indicates table %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22834 16 No Could not modify the verbose logging status for table %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22835 16 No Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22836 16 No Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22837 16 No Could not delete table entries or drop objects associated with capture instance '%s'. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22838 16 No All columns of a CDC unique index must be defined as NOT NULL. Index '%s' selected as the CDC unique index for source table '%s.%s' does not meet this requirement. Define all columns of the selected index as NOT NULL or select another unique index as the CDC index and resubmit the request.
22840 16 No The application lock request '%s' needed to modify Change Data Capture metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 = canceled; -3 = deadlock victim; -999 validation or other call error. Examine the error cause and resbmit the request.
22841 16 No Could not upgrade the metadata for database '%s' that is enabled for Change Data Capture. The failure occurred when executing the action '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22842 16 No ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
22843 16 No ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
22844 16 No The '%s' option must be either 1 or 0.
22850 16 No The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying the cleanup job, specify a positive threshold value. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the threshold value associated with the job to a non-negative value by using the sp_cdc_change_job stored procedure.
22851 16 No Could not update cdc.change_tables to indicate a change in the low water mark for database %s.
22852 10 No Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22853 10 No Could not delete obsolete entries in the cdc.lsn_time_mapping table for database %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request.
22854 16 No Can not enable Change Data Capture on table '%s' or add ColumnSet column to it because CDC does not support ColumnSet.
22855 10 No Warning: The @allow_partition_switch parameter is set to 1. Change data capture will not track changes introduced in the table resulting from a partition switch which will cause data inconsistency when changes are consumed. Refer to books online for more information about partition switching behavior when using Change Data Capture.
22856 10 No Warning: The @allow_partition_switch parameter is set to 0. ALTER TABLE ... SWITCH PARTITION statement will be disallowed on this partitioned table. Refer to books online for more information about partition switching behavior when using Change Data Capture.
22857 10 No Warning: The @allow_partition_switch parameter must be 1 for tables that are not partitioned. The explicit setting of the parameter to 0 was ignored. Refer to books online for more information about partition switching behavior when using Change Data Capture.
22858 16 No Unable to add entries to the Change Data Capture LSN time mapping table to reflect dml changes applied to the tracked tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22859 16 No Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22860 16 No Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22861 10 No Unable to upgrade database '%s'. Error '%d' was raised: '%s'. Use the reported error to determine the cause of the failure and then execute sys.sp_cdc_vupgrade in the database context to rerun upgrade.
22862 16 No The database snapshot '%s' does not exist. Correct the parameter value and resubmit the request.
22863 16 No Failed to insert rows into Change Data Capture change tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22864 16 No The call to sp_MScdc_capture_job by the Capture Job for database '%s' failed. Look at previous errors for the cause of the failure.
22901 16 No The database '%s' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.
22902 16 No Caller is not authorized to initiate the requested action. Sysadmin privileges are required.
22903 16 No Another connection is already running 'sp_replcmds' for Change Data Capture in the current database.
22904 16 No Caller is not authorized to initiate the requested action. DBO privileges are required.
22905 10 No Database '%s' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.
22906 16 No The database '%s' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' already exists in the current database. These objects are required exclusively by Change Data Capture. Drop or rename the user or schema and retry the operation.
22907 16 No Parameter @role_name cannot be empty. Specify a value for @role_name and retry the operation. Supply null as the value if no role is to be used to gate access to captured change data.
22908 16 No Could not create the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22909 16 No Failed to cleanup the cdc.lsn_time_mapping table in database '%s' when the last database table enabled for Change Data Capture was disabled. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22910 16 No The cleanup request for database '%s' failed. The database is not enabled for Change Data Capture.
22911 16 No The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same database. When Change Data Capture and transactional replication are both enabled on a database, use the logreader agent to extract the log changes.
22913 16 No Could not drop the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22914 16 No Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation when Change Data Capture is enabled for a database.
22916 16 No Could not grant SELECT permission for the change enumeration functions for capture instance '%s' and source table '%s.%s' for the specified role. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22918 16 No One or more columns in the list of included columns was not a captured column of the change table %s.
22919 16 No One or more columns in the list of columns needing update flags was not a captured column of the change table %s.
22920 16 No The named capture instance %s does not exist for database %s.
22921 16 No Unable to generate scripts for all capture instances that the caller is authorized to access. To generate all such scripts, the parameters @column_list and @update_flag_list must both be null or empty.'
22923 16 No Could not compute the new low endpoint for database '%s' from retention %d. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22924 16 No Could not clean up change tables for database '%s'. A failure occurred when attempting to clean up the database change tables based upon the current retention time. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22925 16 No The number of columns captured by capture instance '%s' exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to specify a subset of the columns less than or equal to the maximum allowed and resubmit the request.
22926 16 No Could not create a capture instance because the capture instance name '%s' already exists in the current database. Specify an explicit unique name for the parameter @capture_instance.
22927 16 No Capture instance name '%s' exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint.
22928 16 No Index name '%s' is not an index for table '%s.%s'. Specify a valid index name for the table.
22929 16 No Index '%s' must be either a primary key or a unique index for table '%s.%s'. Specify an index that meets at least one of these requirements.
22930 16 No Could not locate '%s' as a column of source table '%s.%s'. Specify a valid column name.
22931 16 No Source table '%s.%s' does not exist in the current database. Ensure that the correct database context is set. Specify a valid schema and table name for the database.
22932 16 No Capture instance name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules.
22938 16 No Role name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules.
22939 16 No The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate unique index has been specified.
22940 16 No Could not remove DDL history entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22941 16 No Could not retrieve column information for index '%s' of source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22942 16 No Columns specified in the captured column list could not be mapped to columns in source table '%s.%s'. Verify that the columns specified in the parameter @captured_column_list are delimited properly and match columns in the source table.
22943 16 No Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key columns of the source table, or the columns defined for the index specified in the parameter @index_name to the list of captured columns and retry the operation.
22944 16 No Could not create the specified database role '%s' for gating access to change table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22945 16 No Could not add column information to the cdc.index_columns system table for the specified index for source table '%s.%s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22946 16 No Could not add column information to the cdc.captured_columns system table for source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22947 16 No Could not create the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22948 16 No Could not create the change enumeration functions for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22949 16 No Could not update the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22950 16 No Could not remove index column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22951 16 No Could not remove captured column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22952 16 No Could not drop Change Data Capture objects created for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22953 16 No Could not remove Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22954 16 No Could not cleanup change tables for capture instance '%s' using low end point %s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22955 16 No Could not obtain the maximum LSN for the database from function 'sys.fn_cdc_get_max_lsn'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22956 16 No Could not obtain the minimum LSN of the change table associated with capture instance '%s' from function 'sys.fn_cdc_get_min_lsn'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22957 16 No LSN %s, specified as the new low end point for the change table associated with capture instance '%s', is not within the Change Data Capture timeline [%s, %s].
22958 16 No Could not create the function to query for all changes for capture instance '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22959 16 No Could not create the function to query for net changes for capture instance '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22960 16 No Change data capture instance '%s' has not been enabled for the source table '%s.%s'. Use sys.sp_cdc_help_change_data_capture to verify the capture instance name and retry the operation.
22961 16 No Could not create a nonclustered index to support net change tracking for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22962 16 No Two capture instances already exist for source table '%s.%s'. A table can have at most two capture instances. If the current tracking options are not appropriate, disable change tracking for the obsolete instance by using sys.sp_cdc_disable_table and retry the operation.
22963 16 No Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
22964 16 No LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping table. Choose an LSN value that satisfies this requirement.
22965 16 No A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more information, see 'Delimited Identifiers' in Books Online.
22966 16 No Could not create table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22967 16 No Could not create a clustered index for table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22968 16 No Could not create DDL trigger '%s' when enabling Change Data Capture for database '%s'. Additional messages in the SQL Server error log and system event log may provide more detail.
22970 16 No The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0.
22971 16 No Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual settings on the server and examine memory usage to see if another application is excessively consuming memory.
22972 16 No When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other parameter must also be non-null and non-empty.
22973 16 No The specified filegroup '%s' is not a valid filegroup for database '%s'. Specify a valid existing filegroup or create the named filegroup, and retry the operation.
22974 16 No Tables contained in the cdc schema cannot be enabled for Change Data Capture.
22975 16 No Source table '%s' contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and ensure that these columns are excluded from the list.
22976 16 No Could not alter column '%s' of change table '%s' in response to a data type change in the corresponding column of the source table '%s'. The Change Data Capture meta data for source table '%s' no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22977 16 No Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22978 16 No Could not update the cdc.captured_columns entry for column '%s' of change table '%s' to reflect a data type change in the corresponding column of the source table '%s'. Change Data Capture column meta data for table '%s' no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22979 16 No The unique index '%s' on table '%s' is used by Change Data Capture. The constraint using this index cannot be dropped or disabled.
22980 16 No The unique index '%s' on table '%s.%s' is disabled and cannot be used as a unique index by Change Data Capture. Enable the index.
22981 16 No Object does not exist or access is denied.
22982 16 No Could not create internal stored procedures used to populate the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems.
22983 16 No The unique index '%s' on source table '%s' is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on the table.
22984 16 No An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. Retry the operation.
22985 16 No Change data capture has not been enabled for source table '%s.%s'. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in the sys.tables catalog view.
22986 16 No Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory.
22987 16 No Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory.
22988 16 No This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, and Enterprise Evaluation editions.
22989 16 No Could not enable Change Data Capture for database '%s'. Change data capture is not supported on system databases, or on a distribution database.
22990 16 No The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds).
22991 16 No The value specified for the parameter @maxtrans must be greater than 0.
22992 16 No The specified @job_type, %s, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate a capture job, or N'cleanup' to indicate a cleanup job.
22993 16 No The Change Data Capture job table containing job information for database '%s' cannot be found in the msdb system database. Run the stored procedure 'sys.sp_cdc_add_job' to create the appropriate CDC capture or cleanup job. The stored procedure will create the required job table.
22994 16 No The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the retention value associated with the job to a non-negative value less than 52594800 by using the sp_cdc_change_job stored procedure.
22995 16 No A value for the parameter @retention cannot be specified when the job type is 'capture'. Specify NULL for the parameter, or omit the parameter from the statement.
22996 16 No When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values.
22997 16 No The Change Data Capture '%s' job does not exist in the system table 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' to add the Change Data Capture job.
22998 16 No The value specified for the parameter @continuous must be 0 or 1.
22999 16 No The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure 'sys.sp_cdc_scan' is not being run in continuous mode.

Errors 23,000 to 25,999

ErrorSeverityEvent LoggedDescription
23003 17 No The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again.
23100 16 No Invalid input parameter(s).
23101 16 No Access is denied.
23102 16 No Item does not exist {ItemId: %ls}.
23103 16 No Folder already exists {ItemId: %ls}.
23104 16 No Folder does not exist {ItemId: %ls}.
23105 16 No Operation violates hierarchical namespace uniqueness.
23106 16 No Container is not empty {ItemId: %ls}.
23107 16 No Item cannot be copied onto itself.
23108 16 No Scoping path does not exist or is invalid.
23109 16 No Container does not exist.
23110 16 No No more items to enumerate.
23111 16 No Item does not exist in the given scope {ItemId: %ls, Scope: %ls}.
23112 16 No Transaction not in active state.
23113 16 No Item either does not exist or it is not a file-backed one.
23114 16 No Sharing violation.
23115 16 No Transaction bindtoken must be null when called within the context of a transaction.
23116 16 No Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls}.
23117 16 No File-backed item does not exist {ItemId: %ls}.
23200 16 No ItemId of folder '%ls' not found.
23201 16 No Share '%ls' does not exist in Catalog.
23202 16 No Could not delete Share '%ls' in Catalog.
23203 16 No Store item not found in Catalog.
23204 16 No Could not delete Store item in Catalog.
23205 16 No Store database name not found in Catalog.
23206 16 No Could not create share to the ItemPath '%ls'.
23207 16 No Could not add Share item for '%ls' in Catalog.
23208 16 No ItemPath '%ls' does not exist in Store.
23209 16 No Could not update Store state in Catalog.
23210 16 No Itempath '%ls' is a file-backed item or within its sub-tree.
23211 16 No Could not start Store Manager. Please look in WinFS UT Log for details.
23212 16 No Itempath '%ls' is a compound item.
23401 16 No Operation failed with HRESULT 0x%x.
23402 16 No Multiple store items were found for the given store name in the catalog.
23403 16 No Cannot create a store with the specified name, it already exists.
23404 16 No Cannot delete the system stores (Catalog or DefaultStore)
23405 16 No Store not found.
23406 16 No A share with the same name already exists.
23407 16 No Could not find a share with the specified name.
23408 16 No The specified itempath is invalid.
23409 16 No Cannot delete system shares (Catalog or DefaultStore)
23410 16 No System error occurred {ErrorCode: %d}.
23411 16 No WinFS could not find the specified volume.
23412 16 No WinFS Store manager is not ready for requests.
23413 16 No WinFS Store Manager currently does not support non-system volumes.
23414 16 No There was a timeout trying to get a lock on the volume object for this operation.
23415 16 No The specified volume is not mounted or is not supported by WinFS
23416 16 No Access Denied. Look in the WinFS UT log for more details.
23417 16 No Invalid argument(S)
23418 16 No Itempath is a compound item.
23419 16 No Itempath is a file-backed item or within it's sub tree.
23420 16 No Itempath does not exist in Store.
23421 16 No Not enough memory available in the system to process the request.
23422 16 No The Disk or File Group is full.
23423 16 No Error accessing files on disk. Refer to the WinFS UT log for more information.
23424 16 No The database operation was rolled back due to a deadlock. Refer to WinFS UT log for details.
23425 16 No Cannot call sp_winfs_deletestore on a connection to the store specified for delete.
23426 16 No Could not initialize the WSM memory clerk during startup.
23427 16 No Could not initialize the WSM memory object during startup.
23428 16 No Could not initialize WSM tracing during startup.
23500 16 No Item container does not exist.
23501 16 No Owning Item does not exist.
23502 16 No NamespaceName is empty or exceeds the maximum length.
23503 16 No Invalid Source endpoint type
23504 16 No Invalid Target endpoint type
23505 16 No A File-backed item must be a compound item type.
23506 16 No A File Backed Item may not contain other Items.
23509 16 No Source Item does not exist.
23510 16 No Item with name already exists in container.
23511 16 No New container cannot be a sub-container of item.
23513 16 No Item does not exist.
23515 16 No Item can not be deleted if it has children
23519 16 No Target Item does not exist.
23525 16 No Invalid Namespace Name.
23530 16 No Operation can not be called inside a un-committable transaction
23536 16 No Win32 file handle is open for item
23573 16 No Cannot change ContainerId when replacing item.
23579 16 No This procedure is reserved and cannot be called.
23587 16 No File stream cannot be null.
23588 16 No Container ids must be the same.
23996 16 No The request could not be performed because of an device I/O error.
23997 16 No System error occurred {ErrorCode: %d}.
23998 16 No Not enough memory available in the system to process the request.
23999 16 No Unspecified error(s) occurred.
25002 16 No The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is correct, and that the Publisher is enabled as a remote Publisher at the Distributor.
25003 16 No Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database.
25005 16 No It is invalid to drop the default constraint on the rowguid column that is used by merge replication.
25006 16 No The new column cannot be added to article '%s' because it has more than %d replicated columns.
25007 16 No Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the changes and synchronize the data.
25008 16 No The merge replication views could not be regenerated after performing the data definition language (DDL) operation.
25009 16 No Invalid value '%s' specified while executing sp_changemergearticle on article '%s' for the 'identityrangemanagementoption' property.
25010 16 No The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle @publication, @article, "identityrangemanagementoption", "none" to disable merge identity management, which will also drop the constraint.
25012 16 No Cannot add an identity column since the table is published for merge replication.
25013 16 No Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than '90RTM'. Use sp_repladdcolumn or sp_repldropcolumn.
25014 16 No sp_repladdcolumn does not allow adding columns of datatypes that are new to this release.
25015 10 No Schema Changes and Bulk Inserts
25016 10 No Prepare Dynamic Snapshot
25017 16 No Failed to execute the command "%s" through xp_cmdshell. Detailed error information is returned in a result set.
25018 16 No Precomputed partitions cannot be used because articles "%s" and "%s" are part of a join filter and at least one of them has a constraint with a CASCADE action defined.
25019 16 No The logical record relationship between articles "%s" and "%s" cannot be added because at least one of the articles has a constraint with a CASCADE action defined.
25020 16 No The article cannot be created on table '%s' because it has more than %d columns and column-level tracking is being used. Either reduce the number of columns in the table or change to row-level tracking.
25021 16 No Replication stored procedure sp_MSupdategenhistory failed to update the generation '%s'. This generation will be retried in the next merge.
25022 16 No The snapshot storage option (@snapshot_storage_option) must be 'file system', or 'database'.
25023 16 No Stored procedures containing table-value parameters cannot be published as '[serializable] proc exec' articles.
25024 16 No A snapshot storage option of 'database' is incompatible with the use of character mode bcp for snapshot generation.
25025 16 No Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse columns.
25026 16 No The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded.
25601 17 No The extended event engine is out of memory.
25602 17 No The %S_MSG, "%.*ls", encountered a configuration error during initialization. Object cannot be added to the event session.
25603 17 No The %S_MSG, "%.*ls", could not be added. The maximum number of singleton targets has been reached.
25604 17 No The extended event engine is disabled.
25605 17 No The %S_MSG, "%.*ls", could not be added. The maximum number of packages has been reached.
25606 17 No The extended event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information about possible related problems.
25607 17 No The extended event engine has been disabled by startup options. Features that depend on extended events may fail to start.
25623 16 No The %S_MSG name, "%.*ls", is invalid, or the object could not be found
25624 16 No The constraints of %S_MSG name, "%.*ls", have been violated. The object does not support binding to actions or predicates. Event not added to event session.
25625 16 No The %S_MSG, "%.*ls", already exists in the event session. Object cannot be added to the event session.
25629 16 No For %S_MSG, "%.*ls", the customizable attribute, "%ls", does not exist.
25630 16 No The predicate expression bound to %S_MSG ,"%.*ls", has mismatching types.
25631 16 No The %S_MSG, "%.*ls", already exists. Choose a unique name for the event session.
25632 16 No The specified buffer size is less than the minimum size.
25633 16 No The buffer size specified exceeds the maximum size.
25634 16 No The dispatch latency specified is below the minimum size.
25635 16 No An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be added to a session, the session must have a maximum memory greater than 0.
25636 16 No Source and comparator types of the predicate do not match.
25638 16 No Event data exceeded allowed maximum.
25639 16 No The %S_MSG, "%.*ls", exceeds the number of allowable bound actions.
25640 16 No Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0.
25641 16 No For %S_MSG, "%.*ls", the parameter "%ls" passed is invalid. %ls
25642 16 No Mandatory customizable attributes are missing for %S_MSG, "%.*ls".
25643 16 No The %S_MSG, "%.*ls", can not be added to an event session that specifies no event loss.
25644 16 No The %S_MSG, "%.*ls", cannot be bound to the event session.
25646 16 No The %S_MSG name, "%.*ls", is invalid.
25647 16 No The %S_MSG, "%.*ls", could not be found. Ensure that the object exists and the name is spelled correctly.
25648 16 No The %S_MSG, "%.*ls", could not be found. Ensure that the package exists and the name is spelled correctly.
25649 16 No Two of the actions/predicates for %S_MSG, "%.*ls", can not coexist. Please remove one.
25650 16 No For %S_MSG, "%.*ls" the customizable attribute, "%ls", was specified multiple times.
25651 16 No For %S_MSG, "%.*ls", the value specified for customizable attribute, "%ls", did not match the expected type, "%ls".
25653 16 No The %S_MSG, "%.*ls", does not exist in the event session. Object cannot be dropped from the event session.
25699 17 No The extended event engine failed unexpectedly while performing an operation.
25701 15 No Invalid event session name "%.*ls". Temporary event sessions are not allowed.
25702 16 No The event session option, "%.*ls", is set more than once. Remove the duplicate session option and re-issue the statement.
25703 16 No The event session option, "%.*ls", has an invalid value. Correct the value and re-issue the statement.
25704 16 No The event session has already been stopped.
25705 16 No The event session has already been started.
25706 16 No The %S_MSG, "%.*ls", could not be found.
25707 16 No Event session option "%.*ls" cannot be changed while the session is running. Stop the event session before changing this session option.
25708 16 No The "%.*ls" specified exceeds the maximum allowed value. Specify a smaller configuration value.
25709 16 No One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
25710 16 Yes Event session "%.*ls" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
25711 16 No Failed to parse an event predicate.
25712 16 No An invalid comparison operator was specified for an event predicate.
25713 16 No The value specified for %S_MSG, "%.*ls", %S_MSG, "%.*ls", is invalid.
25715 16 No The predicate on event "%ls" is invalid. Operator '%ls' is not defined for type "%ls", %S_MSG: "%.*ls".
25716 16 No The predicate on event, "%.*ls", exceeds the maximum length of %d characters.
25717 16 No The operating system returned error %ls while reading from the file '%s'.
25718 16 No The log file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it.
25719 16 No Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query.
25720 10 No 'sys.fn_xe_file_target_read_file' is skipping records from "%.*ls" at offset %I64d.
25721 16 No The metadata file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it.
25722 16 No The offset %d is invalid for log file "%s". Specify an offset that exists in the log file and retry your query.
25723 16 No An error occurred while obtaining metadata information from the file "%s". The file may be damaged.
25724 16 No Predicate too large for display
25807 16 No The %d KB buffer size specified is too low for the ETW target. Increase the size and retry your command.
25809 16 No The log file path "%ls" to the ETW target is invalid. Verify that the path exists and that the SQL Server startup account has access to the log file.
25810 16 No The session name specified exceeds the maximum length of %d characters.
25811 16 No The operating system returned error 5 (ACCESS_DENIED) while creating an ETW tracing session. Ensure that the SQL Server startup account is a member of the 'Performance Log Users' group and then retry your command.
25812 16 No The field '%ls' is invalid for the event '%ls'. Verify that the field exists and try your command again.
25813 16 No The action "%ls" does not exist. Verify that the action exists and try your command again.
25814 16 No The filtering event "%ls" does not exist. Verify that the event exists and try your command again.
25815 16 No The source type, %d, is invalid. Valid types are 0 for event fields or 1 for actions.
25816 16 No The slot count, %d, exceeds the maximum slot count size of %d. Reduce the slot count value and try your command again.
25817 16 No The column or action name specified exceeds the maximum length of %d characters.
25818 16 No The event "%ls" was not found.
25819 16 No The column "%ls" was not found.
25820 16 No The action "%ls" was not found.
25821 16 No The number of begin and end columns must match. Specify the same number of columns for begin and end matching.
25822 16 No The number of begin and end actions must match. Specify the same number of actions for begin and end matching.
25824 16 No The begin and end columns at position %d are not of the same type. Specify matching columns that are the same type and try your command again.
25825 16 No The begin and end action at postition %d are not of the same type. Specify matching actions that are the same type and try your command again.
25827 16 No The operating system returned error %d while creating the file '%ls'. Verify that the path exists and that the SQL Server startup account has access to the location.
25833 16 No Counter target could not add package "%ls" to the list of packages to count. Events from this package will not be counted.
25834 16 No Ring Buffer target could not add package "%ls" to the package occurrence list. Events from this package will not be kept based on occurrence number.

Errors 26,000 to 27,999

ErrorSeverityEvent LoggedDescription
26010 10 Yes The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %#x. Check certificates to make sure they are valid.
26011 16 Yes The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
26012 16 Yes The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support.
26013 10 Yes The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption.
26014 16 Yes Unable to load user-specified certificate [Cert Hash(sha1) "%hs"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.
26015 16 Yes Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.
26017 10 Yes Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
26018 10 Yes A self-generated certificate was successfully loaded for encryption.
26022 10 Yes Server is listening on [ %hs <%hs> %d].
26023 16 Yes Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp port is already in use.
26024 16 Yes Server failed to listen on %hs <%hs> %d. Error: %#x. To proceed, notify your system administrator.
26025 10 Yes HTTP authentication succeeded for user '%.*ls'.%.*ls
26026 14 Yes HTTP authentication failed.%.*ls
26027 10 Yes Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
26028 10 Yes Server named pipe provider is ready to accept connection on [ %hs ].
26029 16 Yes Server named pipe provider failed to listen on [ %hs ]. Error: %#x
26030 10 Yes Server shared memory provider is ready for clients to connect to [ %hs ].
26031 16 Yes Server shared memory provider failed to initialize. Error: %#x
26032 10 Yes Server VIA provider is ready for clients to connect to [ %hs:%d ].
26033 16 Yes Server VIA provider failed to initialize. Error: %#x
26034 10 Yes The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination.
26035 16 Yes The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x.
26036 10 Yes Server named pipe connections are restricted to local access only. This is an informational message only. No user action is required.
26037 10 Yes The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
26038 10 Yes The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors.
26039 16 Yes The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.
26040 17 Yes Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26041 10 Yes Server TCP provider has successfully reestablished listening on port [ %d ].
26042 17 Yes Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26043 10 Yes Server HTTP provider has successfully reestablished listening.
26044 17 Yes Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26045 10 Yes Server named pipe provider has successfully reestablished listening on [ %hs ].
26046 17 Yes Server shared memory provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
26047 10 Yes Server shared memory provider has successfully reestablished listening.
26048 10 Yes Server local connection provider is ready to accept connection on [ %hs ].
26049 16 Yes Server local connection provider failed to listen on [ %hs ]. Error: %#x
26050 17 Yes Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening.
26051 10 Yes Server local connection provider has successfully re-established listening on [ %hs ].
26052 10 Yes SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is an informational message only. No user action is required.
26053 16 Yes SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. There may be insufficient memory. Free up additional memory, then turn the node off and on again. If the failure persists repeat this multiple times or restart the SQL Server.
26054 16 Yes Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: %#x.
26055 16 Yes The SQL Server failed to initialize VIA support library [%hs]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: %#x.
26056 10 Yes Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port through the SQL Server Browser Service. Error: %#x.
26057 16 Yes Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: %#x.
26058 16 Yes A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.
26059 10 Yes The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
26060 10 Yes The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
26061 10 Yes Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem with the network configuration of the computer. Error: %#x.
26062 16 Yes Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.
27001 16 No Reserved error message. Should never be issued.
27002 16 No A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection.
27003 16 No Bad token encountered during tokenization.
27004 16 No Unexpected token type encountered during tokenization.
27005 16 No Error Tolerant Index is corrupt.
27006 16 No Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt.
27007 16 No Attempt to delete from empty ridlist. Error Tolerant Index is corrupt.
27008 16 No rid to be deleted not found in rid-list. Error Tolerant Index is corrupt.
27009 16 No Error Tolerant Index frequencies must be non-negative. Error Tolerant Index is corrupt.
27010 16 No Attempt to insert row whose ID is already present. Error Tolerant Index is corrupt.
27011 16 No No ridlist provided for appending. Error Tolerant Index is corrupt.
27012 16 No Cannot delete token. Error Tolerant Index is corrupt.
27013 16 No Tokenizer object has no delimiter set. Error Tolerant Index is corrupt.
27014 16 No Deletion failed because token does not occur in index. Error Tolerant Index is corrupt.
27015 16 No Unexpected ridlist length. Error Tolerant Index is corrupt.
27016 16 No Cannot connect to Error Tolerant Index. Bad or missing SqlCommand object.
27017 16 No Failed to drop index on reference table copy.
27018 16 No Could not retrieve metadata from Error Tolerant Index. The index is probably corrupt.
27019 16 No Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
27022 16 No An error specific to fuzzy lookup table maintenance has occurred.
27023 16 No A system error occurred during execution of fuzzy lookup table maintenance.
27024 16 No Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt.
27025 16 No Argument is not a valid hex string. Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
27026 16 No Negative count in Error Tolerant Index metadata. The index is probably corrupt.
27027 16 No Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt.
27028 16 No Invalid Error Tolerant Index metadata. The index is probably corrupt.
27029 16 No Invalid Error Tolerant Index metadata version.
27030 16 No Missing metadata. The Error Tolerant Index is probably corrupt.
27031 16 No Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt.
27032 16 No Error Tolerant Index Metadata string too long. Index is probably corrupt.
27033 16 No Error Tolerant Index Metadata length limit exceeded.
27034 16 No Unexpected end of Error Tolerant Index metadata. Index is probably corrupt.
27037 16 No No table name provided for Error Tolerant Index. The index is probably corrupt.
27038 16 No No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt.
27039 16 No No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt.
27040 16 No No Error Tolerant Index metadata string provided for initialization. Index is probably corrupt.
27041 16 No No Error Tolerant Index metadata provided for serialization. The index is probably corrupt.
27042 16 No Could not lookup object_id. No object name provided.
27043 16 No Could not lookup object_id. Null command object provided.
27044 16 No Open connection required. Cannot query Error Tolerant Index.
27045 16 No Cannot write to null output buffer. Could not update Error Tolerant Index. The index is probably corrupt.
27046 16 No Output buffer provided is too small. Could not update Error Tolerant Index. The index is probably corrupt.
27047 16 No The number of min-hash q-grams per token must be positive.
27048 16 No Could not create index on reference table copy.
27049 16 No Reference table (or internal copy) missing integer identity column. Error tolerant index is probably corrupt.
27050 16 No The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps in sequence.
27051 16 No Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted.
27052 16 No Table maintenance insertion failed.
27053 16 No A positive q-gram length is required for tokenization.
27054 16 No Maintenance trigger already installed on this reference table.
27055 16 No Missing extended property on maintenance trigger.
27056 16 No Maintenance trigger name out of sync with Error Tolerant Index metadata. Index is probably corrupt.
27058 16 No A SQL error occurred during execution of fuzzy lookup table maintenance.
27059 16 No Could not lookup object_id. The reference table or maintenance trigger could not be found.
27060 16 No The Error Tolerant Index table name provided is not a valid SQL identifier.
27061 16 No The Error Tolerant Index table name provided refers to a missing table. Check sys.tables.
27062 16 No An auxiliary Fuzzy Lookup table maintenance table is missing.
27063 16 No An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed.
27064 16 No The row deleted from the reference table could not be located in the reference table copy.
27065 16 No Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt.

Errors 28,000 to 30,999

ErrorSeverityEvent LoggedDescription
28000 16 No The decrypted session key has an unexpected size.
28001 16 No A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28002 16 No Cannot start service broker manager. Operating system error: %ls.
28003 16 No An internal service broker error occurred. Operating system error: %ls.
28004 16 No This message could not be delivered because the '%S_MSG' action cannot be performed in the '%.*ls' state.
28005 16 No An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls
28006 14 No User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission.
28007 16 No A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28008 16 No The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}' is invalid.
28009 16 No The crypto API has detected bad data while trying to perform a decryption operation.
28010 16 No This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d.
28011 16 No This message could not be delivered because its %S_MSG has expired or is invalid.
28012 16 No The Service Broker in the target database is unavailable: '%S_MSG'.
28013 16 No The service broker is administratively disabled.
28014 16 No The database is in read-only mode.
28015 16 No The database is in single-user mode.
28016 16 No The message has been dropped because the service broker in the target database is unavailable: '%S_MSG'.
28017 16 No The message has been dropped because the target service broker is unreachable.
28018 16 No The database is a replica of a mirrored database.
28019 16 No System error %d occurred while creating a new message element GUID for this forwarded message.
28020 16 No Could not create user token for user %d in database %d.
28021 16 No One or more messages could not be delivered to the local service targeted by this dialog.
28022 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.
28023 10 No An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.
28024 16 Yes The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid.
28025 16 Yes The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.
28026 10 No Connection handshake failed. Not enough memory available. State %d.
28027 10 No Connection handshake failed. There is no compatible %S_MSG. State %d.
28028 10 No Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.
28029 10 No Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.
28030 10 No Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.
28031 10 No Connection handshake failed. An OS call failed: (%x) %ls. State %d.
28032 10 No A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.
28033 10 No A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d.
28034 10 No Connection handshake failed. The login '%.*ls' does not have CONNECT permission on the endpoint. State %d.
28035 10 No Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
28036 10 No Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d.
28037 10 No Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d.
28038 10 No Connection handshake failed. The handshake verification failed. State %d.
28039 10 No Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.
28040 10 No A corrupted message has been received. The adjacent error message header is invalid.
28041 16 No A corrupted message has been received. The encrypted payload offset is invalid (%d).
28042 16 No A corrupted message has been received. The arbitration request header is invalid.
28043 16 No A corrupted message has been received. The arbitration response header is invalid.
28044 16 No A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28045 10 No Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d.
28046 10 Yes %S_MSG Login succeeded for user '%.*ls'. Authentication mode: %.*ls. %.*ls
28047 10 Yes %S_MSG login attempt failed with error: '%.*ls'. %.*ls
28048 10 Yes %S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls
28050 10 No The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
28051 10 No Could not save a dialog session key. A master key is required in the database to save the session key.
28052 16 No Cannot decrypt session key while regenerating master key with FORCE option.
28053 16 No Service Broker could not upgrade conversation session keys in database '%.*ls' to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker.
28054 16 No Service Broker needs to access the master key in the database '%.*ls'. Error code:%d. The master key has to exist and the service master key encryption is required.
28055 16 No The certificate '%.*ls' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
28056 16 No This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: '%.*ls'.
28057 10 No Service Broker in database '%.*ls' has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.
28058 16 No Service Broker could not upgrade this conversation during a database upgrade operation.
28059 16 No Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
28060 16 No The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
28061 16 No A corrupted message has been received. The adjacent message integrity check signature could not be validated.
28062 16 No A corrupted message has been received. The signed dialog message header is invalid.
28063 16 No A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28064 16 No A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28065 16 No A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28066 16 No A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28067 16 No A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28068 16 No A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28069 16 Yes Unexpected session key when encrypting a dialog message.
28070 10 No Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
28072 16 No A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.
28073 16 No An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
28074 16 No Service Broker could not upgrade conversation with conversation_handle '%ls'. Use END CONVERSATION ... WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE ... SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE ... SET NEW_BROKER to delete all conversations in this database.
28075 10 No The broker in the sender's database is in single user mode. Messages cannot be delivered while in single user mode.
28076 10 No Could not query the FIPS compliance mode flag from registry. Error %ls.
28077 10 No %S_MSG transport is running in FIPS compliance mode. This is an informational message only. No user action is required.
28078 10 No The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
28079 10 No Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
28080 10 No Connection handshake failed. The %S_MSG endpoint is not configured. State %d.
28081 10 No Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
28082 10 No Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
28083 16 No The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys.
28084 10 No An error occurred in Service Broker internal activation while trying to scan the user queue '%ls' for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required.
28085 16 No The activated task was ended because the associated queue was dropped.
28086 16 No The activated task was ended because either the queue or activation was disabled.
28087 16 No The activated task was aborted because the invoked stored procedure '%ls' did not execute RECEIVE.
28088 16 No The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possible output from the activation stored procedure.
28089 16 No The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas.
28090 16 No An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available.
28098 10 No A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.
28099 10 No During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state.
28101 16 No User '%.*ls%.*ls' does not have permission to debug the requested client connection.
28102 16 No Batch execution is terminated because of debugger request.
28201 10 No SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.
28102 16 No Batch execution is terminated because of debugger request.
28201 10 No SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.
29001 16 No To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
29003 16 No Invalid parameter combinations.
29004 16 No Unknown property specified: %s.
30003 16 No A fulltext system view or stvf cannot open database id %d.
30004 16 No A fulltext system view or stvf cannot open user table object id %d.
30005 16 No The name specified for full-text index fragment %.*ls is not valid.
30006 16 No A fulltext system view or stvf cannot open fulltext index for user table object id %d.
30007 16 No Parameters of dm_fts_index_keywords and dm_fts_index_keywords_by_document cannot be null.
30008 16 No The level number specified for function fn_fulltext_compindex is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index. Use the correct level number.
30009 16 No The argument data type '%ls' specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar.
30020 16 No The full-text query parameter for %S_MSG is not valid.
30022 10 No Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION.
30023 16 No The fulltext stoplist '%.*ls' does not exist or the current user does not have permission to perform this action. Verify that the correct stoplist name is specified and that the user had the permission required by the Transact-SQL statement.
30024 16 No The fulltext stoplist '%.*ls' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name.
30028 17 No Failed to get pipeline interface for '%ls', resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
30029 17 No The full-text host controller failed to start. Error: 0x%X.
30031 17 No A full-text master merge failed on full-text catalog '%ls' in database '%.*ls' with error 0x%08X.
30032 16 No The stoplist '%.*ls' does not contain fulltext stopword '%.*ls' with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transact-SQL statement.
30033 16 No The stoplist '%.*ls' already contains full-text stopword '%.*ls' with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Transact-SQL statement.
30034 16 No Full-text stoplist '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text index by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FULLTEXT INDEX. Then retry dropping the stoplist.
30037 16 No An argument passed to a fulltext function is not valid.
30038 17 No Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
30039 17 No Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
30043 16 No Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
30044 16 No The user does not have permission to alter the current default stoplist '%.*ls'. To change the default stoplist of the database, ALTER permission is required on both new and old default stoplists.
30045 17 No Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
30046 16 No SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running. To re-start the FDHost process, run the sp_fulltext_service 'restart_all_fdhosts' command or restart the SQL Server instance.
30047 16 No The user does not have permission to %.*ls stoplist '%.*ls'.
30048 10 No Informational: Ignoring duplicate thesaurus rule '%ls' while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the <sub> section of an expansion rule or the <pat> section of a replacement rule. This causes an ambiguity and hence this phrase will be ignored.
30049 17 No Fulltext thesaurus internal error (HRESULT = '0x%08x')
30050 16 No Both the thesaurus file for lcid '%d' and the global thesaurus could not be loaded.
30051 16 No Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: '%ls'.
30052 16 No The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs successfully, use only six or fewer terms. Modify the query to simplify the condition by removing prefixes or repeated terms.
30053 16 No Word breaking timed out for the full-text query string. This can happen if the wordbreaker took a long time to process the full-text query string, or if a large number of queries are running on the server. Try running the query again under a lighter load.
30055 10 No Full-text catalog import has started for full-text catalog '%ls' in database '%ls'.
30056 10 No Full-text catalog import has finished for full-text catalog '%ls' in database '%ls'. %d fragments and %d keywords were processed.
30057 10 No Upgrade option '%ls' is being used for full-text catalog '%ls' in database '%ls'.
30059 16 No A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); catalog name is %s (id: %d); table name %s (id: %d). Fix the errors that are logged in the full-text crawl log. Then, resume the population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name RESUME POPULATION.
30060 16 No The import population for database %ls (id: %d), catalog %ls (id: %d) is being cancelled because of a fatal error ('%ls'). Fix the errors that are logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching it, or by taking the database offline and bringing it back online. If the error is not recoverable, rebuild the full-text catalog.
30061 17 No The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server after the issue is fixed.
30062 17 No The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
30063 10 No Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid.
30064 17 No SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation.
30067 10 No Warning: The detach operation cannot delete a full-text index created on table '%ls' in database '%ls' because the index is on a read-only filegroup. To drop the full-text index, re-attach the database, change the read-only filegroup to read/write access and then detach it. This warning will not fail the database detach operation.
30068 10 No During the database upgrade, the full-text filter component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls'; Full path is '%.*ls'.
30069 11 No The full-text filter component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls'). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the filter component.
30070 10 No During the database upgrade, the full-text word-breaker component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls'. Full path is '%.*ls'. Language requested is %d. Language used is %d.
30071 11 No The full-text word-breaker component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls', language requested is %d, language used is %d). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the word-breaker component.
30072 10 No During the database upgrade, the full-text protocol handler component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls'. Full path is '%.*ls'. Program ID is '%.*ls'.
30073 11 No The full-text protocol handler component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls', program ID is '%.*ls'). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the protocol handler component.
30074 17 No The master merge of full-text catalog '%ls' in database '%.*ls' was cancelled.
30075 10 No Full-text crawls for database ID: %d, table ID: %d, catalog ID: %d will be stopped since the clustered index on the table has been altered or dropped. Crawl will need to re-start from the beginning.
30076 10 No Full-text crawl forward progress information for database ID: %d, table ID: %d, catalog ID: %d has been reset due to the modification of the clustered index. Crawl will re-start from the beginning when it is unpaused.
30077 16 No The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values for full-text queries that contain an OPTIMIZE FOR query hint. Modify the OPTIMIZE FOR query hint value to be a single, non-empty term.
30078 10 No The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type of full-text logical operator.
30079 10 No The full text query ignored UNKNOWN in the OPTIMIZE FOR hint.
30080 16 No The full-text population on table '%ls' cannot be started because the full-text catalog is importing data from existing catalogs. After the import operation finishes, rerun the command.
30081 10 No A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query with the new trace flag settings.
30082 16 No Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery.
30083 16 No Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery.
30084 16 No The full-text index cannot be created because filegroup '%.*ls' does not exist or the filegroup name is incorrectly specified. Specify a valid filegroup name.
30085 16 No A stoplist cache cannot be generated while processing a full-text query or performing full-text indexing. There is not enough memory to load the stoplist cache. Rerun the query or indexing command when more resources are available.
30086 16 No The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically be retried using a smaller batch size.
30087 16 No Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
30088 10 No The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary.
30089 17 No The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically.
30090 10 No A new instance of the full-text filter daemon host process has been successfully started.
30091 10 No A request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently paused. Either resume or stop the paused population. To resume it, use the following Transact-SQL statement: ALTER FULLTEXT INDEX ON %.*ls RESUME POPULATION. To stop it, use the following statement: ALTER FULLTEXT INDEX ON %.*ls STOP POPULATION.
30092 16 No Full-text stoplist ID '%d' does not exist.
30093 17 No The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a valid state. This can prevent SQL Server from initializing critical system objects. Full-text queries will fail until this issue is resolved. Try stopping SQL Server and any filter daemon host processes and then restarting the instance of SQL Server.
30094 17 No The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to allocate memory or create tasks. Try restarting the instance of SQL Server.
30095 10 No The version of the language components used by full-text catalog '%ls' in database '%ls' is different from the version of the language components included this version of SQL Server. The full-text catalog will still be imported as part of database upgrade. To avoid any possible inconsistencies of query results, consider rebuilding the full-text catalog.
30096 10 No A full-text retry pass of %ls population started for table or indexed view '%ls'. Table or indexed view ID is '%d'. Database ID is '%d'.
30097 10 No The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs for the catalog ID %d in database ID %d. Try to reattach this database. If this fails, then the catalog will need to be dropped or recreated before attach.
30098 10 No An internal query to load data for a crawl on database '%.*ls' and table '%.*ls' failed with error code %d. Check the sql error code for more information about the condition causing this failure. The crawl needs to be restarted after this condition is removed.
30099 17 No Fulltext internal error

Errors 31,000 to 41,400

ErrorSeverityEvent LoggedDescription
31001 16 No The session '%s' already exists. Use a different session name.
31002 16 No This operation can be performed only by the owner of the session.
31003 16 No User does not have enough permissions to tune one or more of the databases specified.
32001 10 No Log shipping backup log job for %s.
32002 10 No Log shipping copy job for %s:%s.
32003 10 No Log shipping restore log job for %s:%s.
32004 10 No Log shipping backup log job step.
32005 10 No Log shipping copy job step.
32006 10 No Log shipping restore log job step.
32007 16 No Database %s is not ONLINE.
32008 16 No Database %s is not ONLINE. The backup job will not be performed until this database is brought online.
32009 16 No A log shipping primary entry already exists for database %s.
32010 16 No Database %s does not exist as log shipping primary.
32011 16 No Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first.
32012 16 No Secondary %s.%s already exists for primary %s.
32013 16 No A log shipping entry already exists for secondary database %s.
32014 16 No Database %s does not exist as log shipping secondary.
32015 16 No The primary database %s cannot have SIMPLE recovery for log shipping to work properly.
32016 16 No The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing.
32017 16 No Log shipping is supported on Enterprise, Developer, Standard and Workgroup editions of SQL Server. This instance has %s and is not supported.
32018 16 No Log shipping is not installed on this instance.
32019 10 No Log shipping alert job.
32020 10 No Log shipping alert job step.
32021 10 No Log shipping alert job schedule.
32022 16 No Cannot add a log shipping job with name %s. A job with same name already exists in the system and this job does not belong to log shipping category.
32023 16 No An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first.
32024 16 No An entry for primary server %s, primary database %s already exists.
32025 16 No Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first.
32026 10 No Log shipping Primary Server Alert.
32027 10 No Log shipping Secondary Server Alert.
32028 16 No Invalid value = %d for parameter @threshold_alert was specified.
32029 10 No Log shipping backup agent [%s] has verified log backup file '%s.wrk' and renamed it as '%s.trn'. This is an informational message only. No user action is required.
32030 10 No Could not query monitor information for log shipping primary %s.%s from monitor server %s.
32031 10 No Could not query monitor information for log shipping secondary %s.%s from monitor server %s.
32032 16 No Invalid value '%d' for update period. Update period should be between 1 and 120 minutes.
32033 16 No The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring
32034 16 No An internal error occurred when setting up the database mirroring monitoring job.
32035 16 No An internal error occurred when modifying the database mirroring monitoring job.
32036 16 No Parameter(s) out of range.
32037 16 No The units for the update period for the database mirroring monitor job have been changed.
32038 16 No An internal error has occurred in the database mirroring monitor.
32039 16 No The database '%s' is not being mirrored. No update of the base table was done.
32040 16 No The alert for 'oldest unsent transaction' has been raised. The current value of '%d' surpasses the threshold '%d'.
32041 16 No The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them.
32042 16 No The alert for 'unsent log' has been raised. The current value of '%d' surpasses the threshold '%d'.
32043 16 No The alert for 'unrestored log' has been raised. The current value of '%d' surpasses the threshold '%d'.
32044 16 No The alert for 'mirror commit overhead' has been raised. The current value of '%d' surpasses the threshold '%d'.
32045 16 No '%s' must be executed in msdb.
32046 16 No Only members of the sysadmin fixed server role or the 'dbm_monitor' role in msdb can perform this operation.
32047 15 No Database Mirroring Monitor Job
32048 15 No Database Mirroring Monitor Schedule
32049 16 No The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job.
32050 16 No Alerts cannot be created on the system databases, master, msdb, model or tempdb.
32051 10 No System administrator privilege is required to update the base table. The base table was not updated.
32052 16 No Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
32053 16 No The server name, given by '@@servername', is currently null.
32054 16 No There was an error establishing a link to the remote monitor server.
32055 16 No There was an error configuring the remote monitor server.
33001 16 No Cannot drop the option because the option is not specified on %S_MSG.
33002 16 No Access to %ls %ls is blocked because the signature is not valid.
33003 16 No DDL statement is not allowed.
33004 16 No The password of login '%.*ls' is invalid. A new password should be set for this login without specifying the old password.
33005 16 No Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x.
33006 16 No WITH SIGNATURE option cannot be specified on database.
33007 16 No Cannot encrypt symmetric key with itself.
33008 16 No Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG.
33009 16 No The database owner SID recorded in the master database differs from the database owner SID recorded in database '%.*ls'. You should correct this situation by resetting the owner of database '%.*ls' using the ALTER AUTHORIZATION statement.
33010 16 No The MUST_CHANGE option cannot be specified together with the HASHED option.
33011 16 No The %S_MSG private key cannot be dropped because one or more entities are encrypted by it.
33012 10 No Cannot %S_MSG signature %S_MSG %S_MSG '%.*ls'. Signature already exists or cannot be added.
33013 16 No A %S_MSG by %S_MSG '%.*s' does not exist.
33014 16 No Cannot countersign '%.*s'. Only modules can be countersigned.
33015 16 No The database principal is referenced by a %S_MSG in the database, and cannot be dropped.
33016 16 No The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins.
33017 16 No Cannot remap a user of one type to a login of a different type. For example, a SQL user must be mapped to a SQL login; it cannot be remapped to a Windows login.
33018 16 No Cannot remap user to login '%.*s', because the login is already mapped to a user in the database.
33019 16 No Cannot create implicit user for the special login '%.*s'.
33020 16 No A HASHED password cannot be set for a login that has CHECK_POLICY turned on.
33021 16 Yes Failed to generate a user instance of SQL Server. Only local user accounts, interactive users accounts, service accounts, or batch accounts can generate a user instance. The connection will be closed.%.*ls
33022 16 No Cannot obtain cryptographic provider properties. Provider error code: %d.
33023 16 No The %S_MSG is too long. Maximum allowed length is %d bytes.
33024 16 No Cryptographic provider %S_MSG '%ls' in dll is different from the guid recorded in system catalog for provider with id %d.
33025 16 No Invalid cryptograpihic provider property: %S_MSG.
33026 16 No Cryptographic provider with guid '%ls' already exists.
33027 Failed to load cryptographic provider '%.*ls' due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures.
33027 16 No Cannot load library '%.*ls'. See errorlog for more information.
33028 16 No Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%S_MSG)
33029 16 No Cannot initialize cryptographic provider. Provider error code: %d. (%S_MSG)
33030 16 No Cryptographic provider is not available.
33031 16 No Cryptographic provider '%.*ls' is in disabled.
33032 16 Yes SQL Crypto API version '%02d.%02d' implemented by provider is not supported. Supported version is '%02d.%02d'.
33033 16 No Specified key type or option '%S_MSG' is not supported by the provider.
33034 16 No Cannot specify algorithm for existing key.
33035 16 No Cannot create key '%.*ls' in the provider. Provider error code: %d. (%S_MSG)
33036 10 No Cannot drop the key with thumbprint '%.*ls' in the provider.
33037 16 No Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG)
33038 16 No Operation is not supported by cryptographic provider key.
33039 16 No Invalid algorithm '%.*ls'. Provider error code: %d. (%S_MSG)
33040 16 No Cryptographic provider key cannot be encrypted by password or other key.
33041 16 Yes Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server.
33042 16 No Cannot add %S_MSG because it is already mapped to a login.
33043 16 No Cannot add %S_MSG '%.*ls' because there is already %S_MSG specified for the login.
33044 16 No Cannot drop %S_MSG because there is %S_MSG referencing this provider.
33045 16 No Cannot drop %S_MSG because it is not mapped to this login.
33046 16 No Server principal '%.*ls' has no credential associated with %S_MSG '%.*ls'.
33047 16 No Fail to obtain or decrypt secret for %S_MSG '%.*ls'.
33048 16 No Cannot use %S_MSG under non-primary security context.
33049 16 No Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG)
33050 16 No Cannot create key '%.*ls' in the provider. Provider does not allow specifying key names.
33051 16 No Invalid algorithm id: %d. Provider error code: %d. (%S_MSG)
33052 16 No Cryptographic provider key cannot be a temporary key.
33053 16 No Extensible Key Management is disabled or not supported on this edition of SQL Server. Use sp_configure 'EKM provider enabled' to enable it.
33054 16 No Extensible key management is not supported in this edition of SQL Server.
33055 16 No Exception happened when calling cryptographic provider '%.*ls' in the API '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
33056 16 No Cannnot impersonate login '%.*ls' to access %S_MSG '%.*ls'.
33057 10 No Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still use it. Restart the server to disable the provider for all users.
33058 10 No Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the server to drop the provider for all users.
33070 16 No The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must be at least 2 MB.
33071 16 No This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command.
33072 16 No The audit log file path is invalid.
33073 16 No Cannot find %S_MSG '%.*ls' or you do not have the required permissions.
33074 16 No Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database.
33075 16 No Auditing is not available in this edition of SQL Server. For more information about feature support in the editions of SQL Server, see SQL Server Books Online.
33076 16 No The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB.
33077 16 No RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE.
33079 16 No Cannot bind a default or rule to the CLR type '%s' because an existing sparse column uses this data type. Modify the data type of the sparse column or remove the sparse designation of the column.
33080 10 No Cryptographic provider library '%.*ls' loaded into memory. This is an informational message only. No user action is required.
33081 10 No Failed to load cryptographic provider '%.*ls' due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures.
33082 16 No Cannot find Cryptographic provider library with guid '%ls'.
33083 16 No Cannot create %S_MSG for %S_MSG '%ls' because it is not supported by the extensible key management provider '%ls'.
33084 16 No The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. Symmetric keys created from an EKM provider are opened automatically for principals who can successfully authenticate with the cryptographic provider.
33085 10 No One or more methods cannot be found in cryptographic provider library '%.*ls'.
33086 10 No SQL Server Audit failed to record %ls action.
33087 16 No %S_MSG property of the key returned by EKM provider doesn't match the expected value
33088 16 No The algorithm: %.*ls is not supported for EKM operations by SQL Server
33089 16 No Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG)
33090 10 No Attempting to load library '%.*ls' into memory. This is an informational message only. No user action is required.
33091 10 No Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
33101 16 No Cannot use %S_MSG '%.*ls', because its private key is not present or it is not protected by the database master key. SQL Server requires the ability to automatically access the private key of the %S_MSG used for this operation.
33102 16 No Cannot encrypt a system database. Database encryption operations cannot be performed for 'master', 'model', 'tempdb', 'msdb', or 'resource' databases.
33103 16 No A database encryption key already exists for this database.
33104 16 No A database encryption key does not exist for this database.
33105 16 No Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the database encryption key.
33106 16 No Cannot change database encryption state because no database encryption key is set.
33107 16 No Cannot enable database encryption because it is already enabled.
33108 16 No Cannot disable database encryption because it is already disabled.
33109 16 No Cannot disable database encryption while an encryption, decryption, or key change scan is in progress.
33110 16 No Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
33111 16 No Cannot find server %S_MSG with thumbprint '%.*ls'.
33112 10 No Beginning database encryption scan for database '%.*ls'.
33113 10 No Database encryption scan for database '%.*ls' is complete.
33114 10 No Database encryption scan for database '%.*ls' was aborted. Reissue ALTER DB to resume the scan.
33115 16 No CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
33116 16 No CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%.*ls'. Try again later.
33117 16 No Transparent Data Encryption 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.
33118 16 No Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
33119 16 No Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.
33120 16 No In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
33121 16 No The %S_MSG '%ls' does not have a login associated with it. Create a login and credential for this key to automatically access the extensible key management provider '%ls'.
33122 16 No This command requires a database encryption scan on database '%.*ls'. However, the database has changes from previous encryption scans that are pending log backup. Take a log backup and retry the command.
33123 16 No Cannot drop or alter the database encryption key since it is currently in use on a mirror. Retry the command after all the previous reencryption scans have propagated to the mirror or after mirroring is disabled.
33124 10 No Database encryption scan for database '%.*ls' cannot complete since one or more files are offline. Bring the files online to run the scan to completion.
33128 Encryption failed. Key uses deprecated algorithm '%.*ls' which is no longer supported.
33129 Cannot use ALTER_LOGIN with the DISABLE argument to deny access to a Windows group.
33201 17 No An error occurred in reading from the audit file or file-pattern: '%s'. The SQL service account may not have Read permission on the files, or the pattern may be returning one or more corrupt files.
33202 17 No SQL Server Audit could not write to file '%s'.
33203 17 No SQL Server Audit could not write to the event log.
33204 17 No SQL Server Audit could not write to the security log.
33205 10 No Audit event: %s.
33206 17 No SQL Server Audit failed to create the audit file '%s'. Make sure that the disk is not full and that the SQL service account has the required permissions to create and write to the file.
33207 17 No SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log.
33208 17 No SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
33209 10 No Audit '%.*ls' has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server was started with the -m flag.
33210 10 No SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
33211 15 No A list of subentities, such as columns, cannot be specified for entity-level audits.
33212 15 No There is an invalid column list after the object name in the AUDIT SPECIFICATION statement.
33213 16 No All actions in an audit specification statement must be at the same scope.
33214 17 No The operation cannot be performed because SQL Server Audit has not been started.
33215 10 No One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with each error.
33216 10 No SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
33217 10 No SQL Server Audit is starting the audits. This is an informational message. No user action is required.
33218 10 No SQL Server Audit has started the audits. This is an informational message. No user action is required.
33219 10 No The server was stopped because SQL Server Audit '%.*ls' is configured to shut down on failure. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
33220 16 No Audit actions at the server scope can only be granted when the current database is master.
33221 16 No You can only create audit actions on objects in the current database.
33222 10 No Audit '%.*ls' failed to %.*ls. For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_XE_LOG'.
33223 16 No ALTER SERVER AUDIT requires the STATE option to be specified without using any other options.
33224 16 No The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command.
33225 16 No The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file set. Verify the file name and offset location, and then rerun the command.
33226 10 No The fn_get_audit_file function is skipping records from '%.*ls' at offset %I64d.
33227 16 No The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher.
33228 16 No You cannot configure SQL Server Audit to shutdown the server because you do not have the permission to shut down the server. Contact your system administrator.
33229 16 No Changes to an audit specification must be done while the audit specification is disabled.
33230 16 No An audit specification for audit '%.*ls' already exists.
33231 16 No You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements.
33301 16 No The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and %d characters long.
33302 16 No The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and 10.
33303 16 No A conversation priority already exists in the database with either the name '%.*ls' or the properties %ls='%ls', %ls='%ls', and %ls='%.*ls'. Either use a unique name or a unique set of properties.
34001 16 No Dialog with queue 'syspolicy_event_queue' has encountered an error: %s.
34002 16 No Dialog with queue 'syspolicy_event_queue' has ended.
34003 16 No Error number %d was encountered while processing an event. The error message is: %s.
34004 16 No Execution mode %d is not a valid execution mode.
34010 16 No %s '%s' already exists in the database.
34011 16 No Specified value for property %s cannot be used with execution mode %d.
34012 16 No Cannot delete %s referenced by a %s.
34013 16 No %s '%s' is referenced by a '%s'. Cannot add another reference.
34014 16 No Facet does not exist.
34015 16 No Policy group %s does not exist.
34016 16 No Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed.
34017 16 No Automated policies cannot reference conditions that contain script.
34018 16 No Target type "%s" is not a valid target type.
34019 16 No Object "%s" is invalid.
34020 16 No Configuration option "%s" is unknown.
34021 16 No Invalid value type for configuration option "%s". Expecting "%s".
34022 16 No Policy automation is turned off.
34050 16 No %ls
34051 16 No %ls
34052 16 No %ls
34053 16 No %ls
34054 16 No Policy Management cannot be enabled on this edition of SQL Server.
34101 20 Yes An error was encountered during object serialization operation. Examine the state to find out more details about this error.
34102 16 Yes An object in serialized stream has version %u but maximum supported version of this class is %u.
34103 16 Yes Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements.
34104 16 No An error was encountered during object serialization operation. The object that failed serialization is %hs.
35001 16 No Parent Server Group does not exist.
35002 16 No Server type and parent Server Group type are not the same
35003 16 No Cannot move node to one of its children
35004 16 No Could not find server group
35005 16 No An invalid value NULL was passed in for @server_group_id.
35006 16 No An invalid value NULL was passed in for @server_id.
35007 16 No Could not find shared registered server.
35008 16 No Cannot delete system shared server groups.
35009 16 No An invalid value NULL was passed in for @server_type.
35010 16 No An invalid value %d was passed in for parameter @server_type.
35011 16 No The @server_name parameter cannot be a relative name.
35012 16 No You cannot add a shared registered server with the same name as the Configuration Server.
35250 16 No The connection to the primary replica is not active. The command cannot be processed.
41030 Failed to open the Windows Server Failover Clustering registry subkey '%.*ls' (Error code %d). The parent key is the cluster root key. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. If the corresponding availability group has been dropped, this error is expected. For information about this error code, see "System Error Codes" in the Windows Development documentation.
41301 A previous transaction that the current transaction took a dependency on has aborted, and the current transaction can no longer commit.
41302 The current transaction attempted to update a record that has been updated since this transaction started. The transaction was aborted.
41305 The current transaction failed to commit due to a repeatable read validation failure.
41307 The row size limit of number bytes for memory optimized tables has been exceeded. Please simplify the table definition.
41325 The current transaction failed to commit due to a serializable validation failure.
41332 Memory optimized tables and natively compiled stored procedures cannot be accessed or created when the session TRANSACTION ISOLATION LEVEL is set to SNAPSHOT.
41333 The following transactions must access memory optimized tables and natively compiled stored procedures under snapshot isolation: RepeatableRead transactions, Serializable transactions, and transactions that access tables that are not memory optimized in RepeatableRead or Serializable isolation.
41342 The model of the processor on the system does not support creating construct. This error typically occurs with older processors.
41349 Warning: Encryption was enabled for a database that contains one or more memory optimized tables with durability SCHEMA_AND_DATA. The data in these memory optimized tables will not be encrypted.
41350 Warning: A memory optimized table with durability SCHEMA_AND_DATA was created in a database that is enabled for encryption. The data in the memory optimized table will not be encrypted.
41359 A query that accesses memory optimized tables using the READ COMMITTED isolation level, cannot access disk based tables when the database option READ_COMMITTED_SNAPSHOT is set to ON. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).
41365 Merge request for transaction range '%ld, %ld' on database %.*ls was not scheduled. The checkpoint files representing the range are either not available for merge or part of an ongoing merge.
41368 Accessing memory optimized tables using the READ COMMITTED isolation level is supported only for autocommit transactions. It is not supported for explicit or implicit transactions. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).
41396 The sort operation exceeded the buffer limit. The stored procedure execution was aborted. Consult SQL Server Books Online for more information.
41399 The sort operation is too complex. Consult SQL Server Books Online for more information.

Errors 41,400 to 42109

ErrorSeverityEvent LoggedDescription
42108 20 No Can not connect to the SQL pool since it is paused. Please resume the SQL pool and try again.
42109 20 No The SQL pool is warming up. Please try again.

See also

  • Understanding Database Engine Errors
  • Cause and Resolution of Database Engine Errors

statements destination component communication correct

zusammenhängende Posts

In the context of socially responsible investing which of the following statements is incorrect
In the context of socially responsible investing which of the following statements is incorrect

Which of the following statements reflects the socioeconomic model of social responsibility?
Which of the following statements reflects the socioeconomic model of social responsibility?

Which of the following statements best explains the activity levels of trypsin shown in Figure 1
Which of the following statements best explains the activity levels of trypsin shown in Figure 1

The diagram provides a useful model to illustrate which of these statements about gene expression
The diagram provides a useful model to illustrate which of these statements about gene expression

Which of the following statements accurately reflects the relationship of the amount of sleep that an individual receives as a function of age?
Which of the following statements accurately reflects the relationship of the amount of sleep that an individual receives as a function of age?

According to your textbook, all of the following statements are true about research except
According to your textbook, all of the following statements are true about research except

What kind of business ownership is best described by these statements I am the only owner of my business I take all the risks of doing business I keep all the profits?
What kind of business ownership is best described by these statements I am the only owner of my business I take all the risks of doing business I keep all the profits?

Which of the following statements is true about the specialization of function in a hemisphere of the brain quizlet?
Which of the following statements is true about the specialization of function in a hemisphere of the brain quizlet?

Each of the following statements about key performance indicators (kpis) are correct, except:
Each of the following statements about key performance indicators (kpis) are correct, except:

Which accounting concept states that omitting or misstating this information could influence users ofthe financial statements?
Which accounting concept states that omitting or misstating this information could influence users ofthe financial statements?

Werbung

NEUESTEN NACHRICHTEN

A set of formalized rules and standards that describe what a company expects
1 Jahrs vor . durch AffiliatedTicker
How do you protect against a similar incident occurring again in the future?
1 Jahrs vor . durch EducationalBonus
Wann blockiert das Hinterrad beim Motorrad?
1 Jahrs vor . durch All-whiteBattery
Antrag auf Erhöhung des Grades der Behinderung Sachsen
1 Jahrs vor . durch RainyRegulator
Wer ist englischer meister geworden
1 Jahrs vor . durch MainCatholicism
Was macht der nat typ für einen unterschied
1 Jahrs vor . durch Million-dollarOverseer
Using threats or intimidation to persuade someone is which influence tactic?
1 Jahrs vor . durch AbandonedDispatcher
Wie spät ist es Schreib die Uhrzeit auf?
1 Jahrs vor . durch WealthyHearth
Süßigkeiten die es nicht mehr gibt
1 Jahrs vor . durch GovernmentalCutter
Was hilft gegen Migräne mit Aura
1 Jahrs vor . durch InsatiableEarnings

Werbung

Populer

Werbung

Um

Legal

Hilfe

Sozial

homeendefrkoptzhitthtr
Urheberrechte © © 2024 ihoctot Inc.