arachnode.net
An Open Source C# web crawler with Lucene.NET search using SQL Server 2008/2012/2014/2016/CE An Open Source C# web crawler with Lucene.NET search using MongoDB/RavenDB/Hadoop

Completely Open Source @ GitHub

Does arachnode.net scale? | Download the latest release
SQL Server 2008 Error Messages 1-5000
Experimental

Syndication

Row message_id Message 1 21 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
2 101 Query not allowed in Waitfor.
3 102 Incorrect syntax near '%.*ls'.
4 103 The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d.
5 104 ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator.
6 105 Unclosed quotation mark after the character string '%.*ls'.
7 106 Too many table names in the query. The maximum allowable is %d.
8 107 The column prefix '%.*ls' does not match with a table name or alias name used in the query.
9 108 The ORDER BY position number %ld is out of range of the number of items in the select list.
10 109 There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
11 110 There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
12 111 '%ls' must be the first statement in a query batch.
13 112 Variables are not allowed in the %ls statement.
14 113 Missing end comment mark '*/'.
15 114 Browse mode is invalid for a statement that assigns values to a variable.
16 115 The FOR UPDATE clause is invalid for statements containing set operators.
17 116 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
18 117 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
19 119 Must pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters must be passed in the form '@name = value'.
20 120 The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns.
21 121 The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns.
22 122 The %ls option is allowed only with %ls syntax.
23 123 Batch/procedure exceeds maximum length of %d characters.
24 124 CREATE PROCEDURE contains no statements.
25 125 Case expressions may only be nested to level %d.
26 126 Invalid pseudocolumn "%.*ls".
27 127 A TOP N value may not be negative.
28 128 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.
29 129 Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
30 130 Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
31 131 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d).
32 132 The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure.
33 133 A GOTO statement references the label '%.*ls' but the label has not been declared.
34 134 The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure.
35 135 Cannot use a BREAK statement outside the scope of a WHILE statement.
36 136 Cannot use a CONTINUE statement outside the scope of a WHILE statement.
37 137 Must declare the scalar variable "%.*ls".
38 138 Correlation clause in a subquery not permitted.
39 139 Cannot assign a default value to a local variable.
40 140 Can only use IF UPDATE within a CREATE TRIGGER statement.
41 141 A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
42 142 Incorrect syntax for definition of the '%ls' constraint.
43 143 A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list.
44 144 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
45 145 ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
46 146 Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
47 147 An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference.
48 148 Incorrect time syntax in time string '%.*ls' used with WAITFOR.
49 149 Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax.
50 150 Both terms of an outer join must contain columns.
51 151 '%.*ls' is an invalid money value.
52 152 The same large data placement option "%.*ls" has been specified twice.
53 153 Invalid usage of the option %.*ls in the %ls statement.
54 154 %S_MSG is not allowed in %S_MSG.
55 155 '%.*ls' is not a recognized %ls option.
56 156 Incorrect syntax near the keyword '%.*ls'.
57 157 An aggregate may not appear in the set list of an UPDATE statement.
58 158 An aggregate may not appear in the OUTPUT clause.
59 159 Must specify the table name and index name for the DROP INDEX statement.
60 160 Rule does not contain a variable.
61 161 Rule contains more than one variable.
62 162 Invalid expression in the TOP clause.
63 163 The compute by list does not match the order by list.
64 164 Each GROUP BY expression must contain at least one column that is not an outer reference.
65 165 Privilege %ls may not be granted or revoked.
66 166 '%ls' does not allow specifying the database name as a prefix to the object name.
67 167 Cannot create %S_MSG on a temporary object.
68 168 The floating point value '%.*ls' is out of the range of computer representation (%d bytes).
69 169 A column has been specified more than once in the order by list. Columns in the order by list must be unique.
70 171 Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements.
71 172 Cannot use HOLDLOCK in browse mode.
72 173 The definition for column '%.*ls' must include a data type.
73 174 The %.*ls function requires %d argument(s).
74 175 An aggregate may not appear in a computed column expression or check constraint.
75 176 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.
76 177 The IDENTITY function can only be used when the SELECT statement has an INTO clause.
77 178 A RETURN statement with a return value cannot be used in this context.
78 179 Cannot use the OUTPUT option when passing a constant to a stored procedure.
79 180 There are too many parameters in this %ls statement. The maximum number is %d.
80 181 Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
81 182 Table and column names must be supplied for the READTEXT or WRITETEXT utility.
82 183 The scale (%d) for column '%.*ls' must be within the range %d to %d.
83 184 DEFAULT cannot be specified more than once for filegroups of the same content type.
84 185 Data stream is invalid for WRITETEXT statement in bulk form.
85 186 Data stream missing from WRITETEXT statement.
86 187 The valid range for MAX_QUEUE_READERS is 0 to 32767.
87 188 Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.
88 189 The %ls function requires %d to %d arguments.
89 190 An invalid date or time was specified in the statement.
90 191 Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
91 192 The scale must be less than or equal to the precision.
92 193 The object or column name starting with '%.*ls' is too long. The maximum length is %d characters.
93 194 A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
94 195 '%.*ls' is not a recognized %S_MSG.
95 196 SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.
96 197 EXECUTE cannot be used as a source when inserting into a table variable.
97 198 Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.
98 199 An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
99 201 Procedure or function '%.*ls' expects parameter '%.*ls', which was not supplied.
100 202 Invalid type '%s' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types.
101 203 The name '%.*ls' is not a valid identifier.
102 204 Normalization error in node %ls.
103 205 All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.
104 206 Operand type clash: %ls is incompatible with %ls
105 207 Invalid column name '%.*ls'.
106 208 Invalid object name '%.*ls'.
107 209 Ambiguous column name '%.*ls'.
108 210 Conversion failed when converting datetime from binary/varbinary string.
109 211 Possible schema corruption. Run DBCC CHECKCATALOG.
110 212 Expression result length exceeds the maximum. %d max, %d found.
111 213 Column name or number of supplied values does not match table definition.
112 214 Procedure expects parameter '%ls' of type '%ls'.
113 215 Parameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
114 216 Parameters were not supplied for the function '%.*ls'.
115 217 Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
116 218 Could not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission.
117 219 The type '%.*ls' already exists, or you do not have permission to create it.
118 220 Arithmetic overflow error for data type %ls, value = %ld.
119 221 FIPS Warning: Implicit conversion from %ls to %ls.
120 222 The base type "%.*ls" is not a valid base type for the alias data type.
121 223 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
122 224 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
123 225 The parameters supplied for the %ls "%.*ls" are not valid.
124 226 %ls statement not allowed within multi-statement transaction.
125 227 "%.*ls" is not a valid function, property, or field.
126 228 Method '%.*ls' of type '%.*ls' in assembly '%.*ls' does not return any value.
127 229 The %ls permission was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'.
128 230 The %ls permission was denied on the column '%.*ls' of the object '%.*ls", database '%.*ls', schema '%.*ls'.
129 231 No such default. ID = %ld, database ID = %d.
130 232 Arithmetic overflow error for type %ls, value = %f.
131 233 The column '%.*ls' in table '%.*ls' cannot be null.
132 234 There is insufficient result space to convert a money value to %ls.
133 235 Cannot convert a char value to money. The char value has incorrect syntax.
134 236 The conversion from char data type to money resulted in a money overflow error.
135 237 There is insufficient result space to convert a money value to %ls.
136 239 Duplicate common table expression name '%.*ls' was specified.
137 240 Types don't match between the anchor and the recursive part in column "%.*ls" of recursive query "%.*ls".
138 241 Conversion failed when converting date and/or time from character string.
139 242 The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.
140 243 Type %.*ls is not a defined system type.
141 244 The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column.
142 245 Conversion failed when converting the %ls value '%.*ls' to data type %ls.
143 246 No anchor member was specified for recursive query "%.*ls".
144 247 An anchor member was found in the recursive part of recursive query "%.*ls".
145 248 The conversion of the %ls value '%.*ls' overflowed an int column.
146 249 The type "%ls" is not comparable. It cannot be used in the %ls clause.
147 251 Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
148 252 Recursive common table expression '%.*ls' does not contain a top-level UNION ALL operator.
149 253 Recursive member of a common table expression '%.*ls' has multiple recursive references.
150 254 Prefixed columns are not allowed in the column list of a PIVOT operator.
151 255 Pseudocolumns are not allowed in the column list of a PIVOT operator.
152 256 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
153 257 Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
154 258 Cannot call methods on %ls.
155 259 Ad hoc updates to system catalogs are not allowed.
156 260 Disallowed implicit conversion from data type %ls to data type %ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query.
157 261 '%.*ls' is not a recognized function.
158 262 %ls permission denied in database '%.*ls'.
159 263 Must specify table to select from.
160 264 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.
161 265 The column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument.
162 266 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld.
163 267 Object '%.*ls' cannot be found.
164 268 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
165 270 Object '%.*ls' cannot be modified.
166 271 The column "%.*ls" cannot be modified because it is either a computed column or is the result of a UNION operator.
167 272 Cannot update a timestamp column.
168 273 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.
169 275 Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.
170 276 Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.
171 277 The column "%.*ls" is specified multiple times in the column list of the UNPIVOT operator.
172 278 The text, ntext, and image data types cannot be used in a GROUP BY clause.
173 279 The text, ntext, and image data types are invalid in this subquery or aggregate expression.
174 280 Only base table columns are allowed in the TEXTPTR function.
175 281 %d is not a valid style number when converting from %ls to a character string.
176 282 The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
177 283 READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.
178 284 Rules cannot be bound to text, ntext, or image data types.
179 285 The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.
180 286 The logical tables INSERTED and DELETED cannot be updated.
181 287 The %ls statement is not allowed within a trigger.
182 288 The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
183 290 Invalid EXECUTE statement using object "%ls", method "%ls".
184 291 CAST or CONVERT: invalid attributes specified for type '%.*ls'
185 292 There is insufficient result space to convert a smallmoney value to %ls.
186 293 Cannot convert char value to smallmoney. The char value has incorrect syntax.
187 294 The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
188 295 Conversion failed when converting character string to smalldatetime data type.
189 297 The user does not have permission to perform this action.
190 300 %ls permission was denied on object '%.*ls', database '%.*ls'.
191 301 Query contains an outer-join request that is not permitted.
192 302 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.
193 303 The table '%.*ls' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.
194 304 '%d' is out of range for index option '%.*ls'. See sp_configure option '%ls' for valid values.
195 305 The XML data type cannot be compared or sorted, except when using the IS NULL operator.
196 306 The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
197 307 Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist.
198 308 Index '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist.
199 309 Cannot use index "%.*ls" on table "%.*ls" in a hint. XML indexes are not allowed in hints.
200 310 The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d.
201 311 Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables.
202 312 Cannot reference text, ntext, or image columns in a filter stored procedure.
203 313 An insufficient number of arguments were supplied for the procedure or function %.*ls.
204 314 Cannot use GROUP BY ALL with the special tables INSERTED or DELETED.
205 315 Index "%.*ls" on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
206 316 The index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
207 317 Table-valued function '%.*ls' cannot have a column alias.
208 318 The table (and its columns) returned by a table-valued method need to be aliased.
209 319 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.
210 320 The compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal.
211 321 "%.*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.
212 322 The variable "%.*ls" is specified in the OPTIMIZE FOR clause, but is not used in the query.
213 323 The 'COMPUTE' clause is not allowed in a statement containing an INTERSECT or EXCEPT operator.
214 324 The 'ALL' version of the %.*ls operator is not supported.
215 325 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.
216 326 Multi-part identifier '%.*ls' is ambiguous. Both columns '%.*ls' and '%.*ls' exist.
217 327 Function call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist.
218 328 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.
219 329 Each GROUP BY expression must contain at least one column reference.
220 330 The target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression.
221 331 The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled triggers.
222 332 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'.
223 333 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'.
224 334 The target table '%.*ls' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.
225 335 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.
226 336 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.
227 337 Warning: the floating point value '%.*ls' is too small. It will be interpreted as 0.
228 338 READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.
229 339 DEFAULT or NULL are not allowed as explicit identity values.
230 340 Cannot create the trigger "%.*ls" on view "%.*ls". AFTER triggers cannot be created on views.
231 341 Replication filter procedures may not contain columns of large object, large value, XML or CLR type.
232 342 Column "%.*ls" is not allowed in this context, and the user-defined function or aggregate "%.*ls" could not be found.
233 343 Unknown object type '%.*ls' used in a CREATE, DROP, or ALTER statement.
234 344 Remote function reference '%.*ls' is not allowed, and the column name '%.*ls' could not be found or is ambiguous.
235 345 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.
236 346 The parameter "%.*ls" can not be declared READONLY since it is not a table-valued parameter.
237 347 The table-valued parameter "%.*ls" cannot be declared as an OUTPUT parameter.
238 348 The table variable "%.*ls" can not be passed to a stored procedure with the OUTPUT option.
239 349 The procedure "%.*ls" has no parameter named "%.*ls".
240 350 The column "%.*ls" does not have a valid data type. A column cannot be of a user-defined table type.
241 351 Column, parameter, or variable %.*ls. : Cannot find data type %.*ls.
242 352 The table-valued parameter "%.*ls" must be declared with the READONLY option.
243 353 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.
244 354 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.
245 355 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.
246 356 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'.
247 357 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'.
248 358 The target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'.
249 359 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.
250 360 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.
251 361 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.
252 401 Unimplemented statement or expression %ls.
253 402 The data types %s and %s are incompatible in the %s operator.
254 403 Invalid operator for data type. Operator equals %ls, type equals %ls.
255 404 The column reference "inserted.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement.
256 405 A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.
257 406 %ls cannot be used in the PIVOT operator because it is not invariant to NULLs.
258 407 Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.
259 408 A constant expression was encountered in the ORDER BY list, position %i.
260 411 COMPUTE clause #%d, aggregate expression #%d is not in the select list.
261 412 The column "%.*ls" is not updatable because it is derived or constant.
262 413 Correlated parameters or sub-queries are not supported by the inline function "%.*ls".
263 414 UPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger.
264 415 DELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger.
265 416 The service queue "%.*ls" cannot be directly updated.
266 417 TOP is not allowed in an UPDATE or DELETE statement against a partitioned view.
267 418 Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'.
268 421 The %ls data type cannot be selected as DISTINCT because it is not comparable.
269 422 Common table expression defined but not used.
270 423 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".
271 424 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.
272 425 Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'.
273 426 The length %d of the receiving variable is less than the length %d of the column '%.*ls'.
274 427 Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.
275 428 Insert bulk cannot be used in a multi-statement batch.
276 432 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".
277 434 Function '%ls' is not allowed in the OUTPUT clause.
278 435 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.
279 438 Xml data type methods are not allowed in rules. The error occurred at table "%.*ls".
280 440 Internal query compilation error. The stack overflow could not be handled.
281 441 Cannot use the '%ls' function on a remote data source.
282 442 The NEST argument must be a column reference. Expressions are not allowed.
283 443 Invalid use of a side-effecting operator '%s' within a function.
284 444 Select statements included within a function cannot return data to a client.
285 445 COLLATE clause cannot be used on expressions containing a COLLATE clause.
286 446 Cannot resolve collation conflict for %ls operation.
287 447 Expression type %ls is invalid for COLLATE clause.
288 448 Invalid collation '%.*ls'.
289 449 Collation conflict caused by collate clauses with different collation '%.*ls' and '%.*ls'.
290 450 Code page translations are not supported for the text data type. From: %d To: %d.
291 451 Cannot resolve collation conflict for column %d in %ls statement.
292 452 COLLATE clause cannot be used on user-defined data types.
293 453 Collation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level.
294 454 The UNNEST argument must be a nested table column.
295 455 The last statement included within a function must be a return statement.
296 456 Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict.
297 457 Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict.
298 458 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.
299 459 Collation '%.*ls' is supported on Unicode data types only and cannot be applied to char, varchar or text data types.
300 460 DISTINCT operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
301 461 TOP operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
302 462 Outer join is not allowed in the recursive part of a recursive common table expression '%.*ls'.
303 463 Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'.
304 464 Functions with side effects are not allowed in the recursive part of a recursive common table expression '%.*ls'.
305 465 Recursive references are not allowed in subqueries.
306 466 UNION operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.
307 467 GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'.
308 468 Cannot resolve the collation conflict between "%.*ls" and "%.*ls" in the %ls operation.
309 469 An explicit column list must be specified for target table '%.*ls' when table hint KEEPIDENTITY is used and the table contains an identity column.
310 470 The synonym "%.*ls" referenced synonym "%.*ls". Synonym chaining is not allowed.
311 471 Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.
312 472 Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.
313 473 The incorrect value "%.*ls" is supplied in the PIVOT operator.
314 474 Unable to load the computed column definitions for table "%.*ls".
315 475 Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.
316 476 Invalid PERCENT tablesample size "%f" for table "%.*ls". The PERCENT tablesample size must be between 0 and 100.
317 477 Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer.
318 478 The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.
319 479 Invalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0.
320 480 The TABLESAMPLE clause cannot be used with the table function "%.*ls".
321 481 The TABLESAMPLE clause cannot be used with the linked server table "%.*ls".
322 482 Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.
323 483 The OUTPUT clause cannot be used in an INSERT...EXEC statement.
324 484 Cannot declare more than %d local variables.
325 485 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".
326 486 "%.*ls" does not allow specifying a schema name as a prefix to the assembly name.
327 487 An invalid option was specified for the statement "%.*ls".
328 488 %s columns must be comparable. The type of column "%.*ls" is "%s", which is not comparable.
329 489 The OUTPUT clause cannot be specified because the target view "%.*ls" is a partitioned view.
330 490 The resync functionality is temporarily disabled.
331 491 A correlation name must be specified for the bulk rowset in the from clause.
332 492 Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate.
333 493 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.
334 494 The TABLESAMPLE clause can only be used with local tables.
335 495 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.
336 496 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.
337 497 Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.
338 498 Invalid value in the TABLESAMPLE or the REPEATABLE clause.
339 499 Invalid parameter for the getchecksum function.
340 500 Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).
341 505 The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.
342 506 The invalid escape character "%.*ls" was specified in a %ls predicate.
343 507 Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.
344 509 User name '%.*ls' not found.
345 510 Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.
346 511 Cannot create a row of size %d which is greater than the allowable maximum row size of %d.
347 512 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
348 513 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'.
349 515 Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
350 517 Adding a value to a '%ls' column caused an overflow.
351 518 Cannot convert data type %ls to %ls.
352 522 The WAITFOR thread was evicted.
353 523 A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
354 524 A trigger returned a resultset and the server option 'disallow results from triggers' is true.
355 525 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.
356 526 %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.
357 527 Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.
358 529 Explicit conversion from data type %ls to %ls is not allowed.
359 530 The statement terminated. The maximum recursion %d has been exhausted before statement completion.
360 531 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.
361 532 The timestamp (changed to %S_TS) shows that the row has been updated by another user.
362 533 Cannot set XACT ABORT to OFF inside the trigger execution unless the database compatibility is 90.
363 534 '%.*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.
364 535 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.
365 536 Invalid length parameter passed to the %ls function.
366 537 Invalid length parameter passed to the LEFT or SUBSTRING function.
367 539 Schema changed after the target table was created. Rerun the Select Into query.
368 540 There is insufficient system memory to run RAISERROR.
369 541 There is not enough stack to execute the statement
370 542 An invalid datetime value was encountered. Value exceeds the year 9999.
371 543 Creation of a return table failed for the table valued function '%.*ls'.
372 544 Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF.
373 545 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.
374 547 The %ls statement conflicted with the %ls constraint "%.*ls". The conflict occurred in database "%.*ls", table "%.*ls"%ls%.*ls%ls.
375 548 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.
376 549 The collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'.
377 550 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.
378 552 CryptoAPI function '%ls' failed. Error 0x%x: %ls
379 555 User-defined functions are not yet enabled.
380 556 INSERT EXEC failed because the stored procedure altered the schema of the target table.
381 557 Only functions and some extended stored procedures can be executed from within a function.
382 558 Remote function calls are not allowed within a function.
383 561 Failed to access file '%.*ls'
384 562 Failed to access file '%.*ls'. Files can be accessed only through shares
385 563 The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.
386 564 Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'.
387 565 A stack overflow occurred in the server while compiling the query. Please simplify the query.
388 566 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.
389 567 File '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file.
390 568 Encountered an error or an unexpected end of trace file '%.*ls'.
391 569 The handle that was passed to %ls was invalid.
392 570 INSTEAD OF triggers do not support direct recursion. The trigger execution failed.
393 571 The specified attribute value for %ls is invalid.
394 572 Invalid regular expression "%.*ls" near the offset %d.
395 573 Evaluation of the regular expression is too complex: '%.*ls'.
396 574 %ls statement cannot be used inside a user transaction.
397 575 A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.
398 576 Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.
399 577 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.
400 578 Insert Exec not allowed in WAITFOR queries.
401 579 Can not execute WAITFOR query with snapshot isolation level.
402 582 Offset is greater than the length of the column to be updated in write.
403 583 Negative offset or length in write.
404 584 Select Into not allowed in WAITFOR queries.
405 585 Changing database context is not allowed when populating the resource database.
406 587 An invalid delayed CLR type fetch token is provided.
407 588 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time.
408 589 This statement has attempted to access data whose access is restricted by the assembly.
409 590 RPC was aborted without execution.
410 591 %ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.
411 592 Cannot find %S_MSG ID %d in database ID %d.
412 593 fn_trace_gettable: XML conversion of trace data for event 165 failed.
413 594 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode.
414 595 Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
415 596 Cannot continue the execution because the session is in the kill state.
416 597 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).
417 598 An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.
418 599 %.*ls: The length of the result exceeds the length limit (2GB) of the target large type.
419 601 Could not continue scan with NOLOCK due to data movement.
420 602 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.
421 603 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.
422 605 Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.
423 606 Metadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG.
424 608 No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.
425 609 BTree is not empty when waking up on RowsetBulk.
426 610 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption.
427 611 Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.
428 613 Could not find an entry for worktable rowset with partition ID %I64d in database %d.
429 615 Could not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again.
430 617 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.
431 622 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.
432 627 Cannot use SAVE TRANSACTION within a distributed transaction.
433 628 Cannot issue SAVE TRANSACTION when there is no active transaction.
434 650 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.
435 651 Cannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited.
436 652 The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified.
437 666 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.
438 667 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.
439 669 The row object is inconsistent. Please rerun the query.
440 670 Large object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed.
441 671 Large object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified.
442 672 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.
443 674 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.
444 675 Worktable with partition ID %I64d was dropped successfully after repeated attempts.
445 676 Error occurred while attempting to drop worktable with partition ID %I64d.
446 677 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.
447 678 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.
448 679 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.
449 680 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.
450 681 Attempting to set a non-NULL-able column's value to NULL.
451 682 Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.
452 683 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.
453 684 An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption.
454 685 An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.
455 686 Cannot compress a nchar or nvarchar column that has an odd number of bytes.
456 701 There is insufficient system memory in resource pool '%ls' to run this query.
457 708 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.
458 801 A buffer was encountered with an unexpected status of 0x%x.
459 802 There is insufficient memory available in the buffer pool.
460 803 simulated failure (DEBUG only)
461 805 restore pending
462 806 audit failure (a page read from disk failed to pass basic integrity checks)
463 807 (no disk or the wrong disk is in the drive)
464 808 insufficient bytes transferred
465 821 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.
466 822 Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.
467 823 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.
468 824 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.
469 825 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.
470 826 incorrect pageid (expected %d:%d; actual %d:%d)
471 829 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
472 830 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))
473 831 Unable to deallocate a kept page.
474 832 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.
475 833 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
476 844 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.
477 845 Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
478 846 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.
479 847 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.
480 848 Using large pages for buffer pool.
481 849 Using locked pages for buffer pool.
482 850 %I64u MB of large page memory allocated.
483 851 the page is in an OFFLINE file which cannot be read
484 902 To change the %ls, the database must be in state in which a checkpoint can be executed.
485 904 Database %ld cannot be autostarted during server shutdown or startup.
486 905 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.
487 907 The database "%ls" has inconsistent database or file metadata.
488 908 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.
489 909 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.
490 910 Database '%.*ls' is upgrading script '%.*ls' from level %d to level %d.
491 911 Database '%.*ls' does not exist. Make sure that the name is entered correctly.
492 912 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.
493 913 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.
494 914 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.
495 915 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.
496 916 The server principal "%.*ls" is not able to access the database "%.*ls" under the current security context.
497 917 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.
498 918 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.
499 919 User '%.*ls' is changing database script level entry %d to a value of %d.
500 920 Only members of the sysadmin role can modify the database script level.
501 921 Database '%.*ls' has not been recovered yet. Wait and try again.
502 922 Database '%.*ls' is being recovered. Waiting until recovery is finished.
503 923 Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.
504 924 Database '%.*ls' is already open and can only have one user at a time.
505 925 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.
506 926 Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
507 927 Database '%.*ls' cannot be opened. It is in the middle of a restore.
508 928 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.
509 929 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.
510 930 Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support.
511 931 Attempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support.
512 932 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.
513 933 Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server.
514 934 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.
515 935 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.
516 942 Database '%.*ls' cannot be opened because it is offline.
517 943 Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).
518 944 Converting database '%.*ls' from version %d to the current version %d.
519 945 Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
520 946 Cannot open database '%.*ls' version %d. Upgrade the database to the latest version.
521 947 Error while closing database '%.*ls'. Check for previous additional errors and retry the operation.
522 948 The database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.
523 949 tempdb is skipped. You cannot run a query that requires tempdb
524 950 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.
525 951 Database '%.*ls' running the upgrade step from version %d to version %d.
526 952 Database '%.*ls' is in transition. Try the statement later.
527 954 The database "%.*ls" cannot be opened. It is acting as a mirror database.
528 955 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.
529 956 Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.
530 957 Database '%.*ls' is enabled for Database Mirroring, The name of the database may not be changed.
531 958 The resource database build version is %.*ls. This is an informational message only. No user action is required.
532 959 The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.
533 960 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.
534 961 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.
535 962 Warning: Primary key or Unique constraint "%.*ls" (object_id = %d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed.
536 963 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.
537 964 Warning: System user '%.*ls' was found missing from database '%.*ls' and has been restored. This user is required for SQL Server operation.
538 965 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.
539 966 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.
540 967 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.
541 968 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.
542 969 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.
543 970 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.
544 971 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'.
545 972 Could not use database '%d' during procedure execution.
546 1001 Line %d: Length or precision specification %d is invalid.
547 1002 Line %d: Specified scale %d is invalid.
548 1003 Line %d: %ls clause allowed only for %ls.
549 1004 Invalid column prefix '%.*ls': No table name specified
550 1005 Line %d: Invalid procedure number (%d). Must be between 1 and 32767.
551 1006 CREATE TRIGGER contains no statements.
552 1007 The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38).
553 1008 The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only allowed when ordering by an expression referencing a column name.
554 1009 The keyword DEFAULT is not allowed in DBCC commands.
555 1010 Invalid escape character '%.*ls'.
556 1011 The correlation name '%.*ls' is specified multiple times in a FROM clause.
557 1012 The correlation name '%.*ls' has the same exposed name as table '%.*ls'.
558 1013 The objects "%.*ls" and "%.*ls" in the FROM clause have the same exposed names. Use correlation names to distinguish them.
559 1014 TOP clause contains an invalid value.
560 1015 An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the column being aggregated is an outer reference.
561 1016 Outer join operators cannot be specified in a query containing joined tables.
562 1018 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.
563 1019 Invalid column list after object name in GRANT/REVOKE statement.
564 1020 Sub-entity lists (such as column or security expressions) cannot be specified for entity-level permissions.
565 1021 FIPS Warning: Line %d has the non-ANSI statement '%ls'.
566 1022 FIPS Warning: Line %d has the non-ANSI clause '%ls'.
567 1023 Invalid parameter %d specified for %ls.
568 1024 FIPS Warning: Line %d has the non-ANSI function '%ls'.
569 1025 FIPS Warning: The length of identifier '%.*ls' exceeds 18.
570 1026 GOTO cannot be used to jump into a TRY or CATCH scope.
571 1028 The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed in a GROUP BY ALL clause.
572 1029 Browse mode is invalid for subqueries and derived tables.
573 1030 Only constants are allowed here. Time literal is not permitted because it refers to the current date.
574 1031 Percent values must be between 0 and 100.
575 1032 Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'.
576 1033 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.
577 1034 Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration.
578 1035 Incorrect syntax near '%.*ls', expected '%.*ls'.
579 1036 File option %hs is required in this CREATE/ALTER DATABASE statement.
580 1037 The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions.
581 1038 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.
582 1039 Option '%.*ls' is specified more than once.
583 1041 Option %.*ls is not allowed for a LOG file.
584 1042 Conflicting %ls optimizer hints specified.
585 1043 '%hs' is not yet implemented.
586 1044 Cannot use an existing function name to specify a stored procedure name.
587 1045 Aggregates are not allowed in this context. Only scalar expressions are allowed.
588 1046 Subqueries are not allowed in this context. Only scalar expressions are allowed.
589 1047 Conflicting locking hints specified.
590 1048 Conflicting cursor options %ls and %ls.
591 1049 Mixing old and new syntax to specify cursor options is not allowed.
592 1050 This syntax is only allowed for parameterized queries.
593 1051 Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT.
594 1052 Conflicting %ls options "%ls" and "%ls".
595 1053 For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname".
596 1054 Syntax '%ls' is not allowed in schema-bound objects.
597 1055 '%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character.
598 1056 The number of elements in the select list exceeds the maximum allowed number of %d elements.
599 1057 The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION, INTERSECT or EXCEPT operator.
600 1058 Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration.
601 1059 Cannot set or reset the 'parseonly' option within a procedure or function.
602 1060 The number of rows in the TOP clause must be an integer.
603 1061 The text/ntext/image constants are not yet implemented.
604 1062 The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause.
605 1063 A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP.
606 1064 A filegroup cannot be used with log files.
607 1065 The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE, DELETE or MERGE statements.
608 1066 Warning. Line %d: The option '%ls' is obsolete and has no effect.
609 1067 The SET SHOWPLAN statements must be the only statements in the batch.
610 1068 Only one list of index hints per table is allowed.
611 1069 Index hints are only allowed in a FROM or OPTION clause.
612 1070 CREATE INDEX option '%.*ls' is no longer supported.
613 1071 Cannot specify a JOIN algorithm with a remote JOIN.
614 1072 A REMOTE hint can only be specified with an INNER JOIN clause.
615 1073 '%.*ls' is not a recognized cursor option for cursor %.*ls.
616 1074 Creation of temporary functions is not allowed.
617 1075 RETURN statements in scalar valued functions must include an argument.
618 1076 Function '%s' requires at least %d argument(s).
619 1077 INSERT into an identity column not allowed on table variables.
620 1078 '%.*ls %.*ls' is not a recognized option.
621 1079 A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor.
622 1080 The integer value %.*ls is out of range.
623 1081 %s does not allow specifying the database name as a prefix to the assembly name.
624 1082 "%.*ls" does not support synchronous trigger registration.
625 1083 OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers.
626 1084 '%.*ls' is an invalid event type.
627 1085 '%.*ls' event type does not support event notifications.
628 1086 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.
629 1087 Must declare the table variable "%.*ls".
630 1088 Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
631 1089 The SET FMTONLY OFF statement must be the last statement in the batch.
632 1090 Invalid default for parameter %d.
633 1091 The option "%ls" is not valid for this function.
634 1092 In this context %d statistics name(s) cannot be specified for option '%ls'.
635 1093 "%.*ls" is not a valid broker name.
636 1094 Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.
637 1095 "%.*ls" has already been specified as an event type.
638 1096 Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported.
639 1097 Cannot use If UPDATE within this CREATE TRIGGER statement.
640 1098 The specified event type(s) is/are not valid on the specified target object.
641 1099 The ON clause is not valid for this statement.
642 1101 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.
643 1105 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.
644 1119 Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.
645 1121 Space allocator cannot allocate page in database %d.
646 1122 Table error: Page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned.
647 1123 Table error: Page %S_PGID. Unexpected page type %d.
648 1124 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid.
649 1125 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.
650 1126 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row.
651 1127 Table error: Page %S_PGID. Test (%hs) failed. Values are %ld and %ld.
652 1128 Table error: Page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld.
653 1129 Could not cleanup deferred deallocations from filegroup '%.*ls'.
654 1130 Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost.
655 1131 Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required.
656 1202 The database-principal '%.*ls' does not exist or user is not a member.
657 1203 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.
658 1204 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.
659 1205 Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
660 1206 The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
661 1207 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.
662 1208 Could not allocate initial %u lock blocks during startup. Can not start the server.
663 1209 Could not allocate initial %u lock owner blocks during startup. Can not start the server.
664 1210 Unable to allocate lock owner block during lock migration. Server halted.
665 1212 Lock not logged: %-30ls Mode: %s
666 1213 Error spawning Lock Monitor thread: %ls
667 1214 Internal Error. There are too many parallel transactions.
668 1220 No more lock classes available from transaction.
669 1221 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.
670 1222 Lock request time out period exceeded.
671 1223 Cannot release the application lock (Database Principal: '%.*ls', Resource: '%.*ls') because it is not currently held.
672 1224 An invalid application lock resource was passed to %ls.
673 1225 An invalid application lock mode was passed to %ls.
674 1226 An invalid application lock owner was passed to %ls.
675 1227 An invalid application lock time-out was passed to %ls.
676 1228 An invalid parameter "%ls" was passed to the application lock function or procedure.
677 1230 An invalid database principal was passed to %ls.
678 1401 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.
679 1402 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.
680 1403 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.
681 1404 The command failed because the database mirror is busy. Reissue the command later.
682 1405 The database "%.*ls" is already enabled for database mirroring.
683 1406 Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access.
684 1407 The remote copy of database "%.*ls" is not related to the local copy of the database.
685 1408 The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring.
686 1409 Database mirroring cannot be enabled for the remote copy of database "%.*ls". Restore database logs to the remote copy.
687 1410 The remote copy of database "%.*ls" is already enabled for database mirroring.
688 1411 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.
689 1412 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.
690 1413 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.
691 1414 The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
692 1415 The database mirroring operation for database "%.*ls" failed. The requested operation could not be performed.
693 1416 Database "%.*ls" is not configured for database mirroring.
694 1417 Database mirroring has been disabled by the administrator for database "%.*ls".
695 1418 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.
696 1419 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.
697 1420 Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration.
698 1421 Communications to the remote server instance '%.*ls' failed to complete before its timeout. The ALTER DATABASE command may have not completed. Retry the command.
699 1422 The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over.
700 1423 The property name is not supported.
701 1424 The remote server instance has a more recent value for the property '%.*ls'. Property value not changed.
702 1425 The property value is invalid for '%.*ls'. Property value not changed.
703 1426 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.
704 1427 The server instance '%.*ls' could not act as the witness. The ALTER DATABASE SET WITNESS command failed.
705 1428 The request is refused because the responding server instance is not in a state to service the request.
706 1429 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.
707 1430 Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.
708 1431 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.
709 1432 Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner.
710 1433 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.
711 1434 Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls.
712 1435 %ls received unexpected database mirroring error response: status %u, severity %u, state %u, string %.*ls.
713 1436 The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server.
714 1437 Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase system memory.
715 1438 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.
716 1439 There is currently no witness associated with database "%.*ls".
717 1440 Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required.
718 1441 Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required.
719 1442 Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required.
720 1443 Database mirroring has been terminated for database '%.*ls'. This is an informational message only. No user action is required.
721 1444 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.
722 1445 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.
723 1446 The "%.*ls" server instance is already acting as the witness.
724 1447 ALTER DATABASE "%.*ls" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command.
725 1448 The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command.
726 1449 ALTER DATABASE command failed due to an invalid server connection string.
727 1450 The ALTER DATABASE command failed because the worker thread cannot be created.
728 1451 Database mirroring information was not found in the system table.
729 1452 The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed.
730 1453 '%.*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.
731 1454 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.
732 1455 The database mirroring service cannot be forced for database "%.*ls" because the database is not in the correct state to become the principal database.
733 1456 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.
734 1457 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.
735 1458 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.
736 1459 An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it.
737 1460 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.
738 1461 Database mirroring successfully repaired physical page %S_PGID in database "%.*ls" by obtaining a copy from the partner.
739 1462 Database mirroring is disabled due to a failed redo operation. Unable to resume.
740 1463 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.
741 1464 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.
742 1465 Database mirroring cannot be enabled because the "%.*ls" database is not in full recovery mode on both partners.
743 1466 Database mirroring cannot be enabled because the "%.*ls" database is read-only on one of the partners.
744 1467 Database mirroring cannot be enabled because the "%.*ls" database is in emergency or suspect mode on one of the partners.
745 1468 The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session.
746 1469 Database mirroring cannot be enabled because the "%.*ls" database is an auto-close database on one of the partners.
747 1470 The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls".
748 1471 The database mirroring connection terminated. Out of memory sending message for database "%.*ls".
749 1472 The database mirroring connection terminated. Communications error sending message for database "%.*ls".
750 1473 This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.
751 1474 Database mirroring connection error %d '%.*ls' for '%.*ls'.
752 1475 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.
753 1476 Database mirroring timeout value %d exceeds the maximum value 32767.
754 1477 The database mirroring safety level must be FULL to manually failover database "%.*ls". Set safety level to FULL and retry.
755 1478 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.
756 1479 The mirroring connection to "%.*ls" has timed out for database "%.*ls" after %d seconds without a response. Check the service and network connections.
757 1480 The mirrored database "%.*ls" is changing roles from "%ls" to "%ls" due to %S_MSG.
758 1481 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.
759 1485 Database mirroring has been enabled on this instance of SQL Server.
760 1486 Database Mirroring Transport is disabled in the endpoint configuration.
761 1487 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.
762 1488 Database mirroring cannot be enabled because the "%.*ls" database is in single user mode.
763 1489 Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.
764 1499 Database mirroring error: status %u, severity %u, state %u, string %.*ls.
765 1501 Sort failure. Contact Technical Support.
766 1505 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.
767 1509 Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support.
768 1510 Sort failed. Out of space or locks in database '%.*ls'.
769 1511 Sort cannot be reconciled with transaction log.
770 1522 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.
771 1523 Sort failure. The incorrect extent could not be deallocated. Contact Technical Support.
772 1532 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.
773 1533 Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction.
774 1534 Extent %S_PGID not found in shared extent directory. Retry the transaction. If the problem persists, contact Technical Support.
775 1535 Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support.
776 1537 Cannot suspend a sort that is not in row input phase.
777 1538 Cannot insert a row into a sort when the sort is not in row input phase.
778 1540 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.
779 1541 Sort failure. A defective CLR type comparison function is suspected.
780 1542 BobMgr::GetBuf: Sort Big Output Buffer write not complete after %d seconds.
781 1543 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.
782 1701 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.
783 1702 CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns.
784 1706 The system table '%.*ls' can only be created or altered during an upgrade.
785 1707 Cannot specify TEXTIMAGE_ON filegroup for a partitioned table.
786 1708 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.
787 1709 Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns.
788 1710 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.
789 1711 Cannot define PRIMARY KEY constraint on column '%.*ls' in table '%.*ls'. The computed column has to be persisted and not nullable.
790 1712 Online index operations can only be performed in Enterprise edition of SQL Server.
791 1713 Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger.
792 1714 Alter table failed because unique column IDs have been exhausted for table '%.*ls'.
793 1715 Foreign key '%.*ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.*ls'.
794 1716 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.
795 1717 FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause.
796 1718 Change tracking must be enabled on database '%.*ls' before it can be enabled on table '%.*ls'.
797 1719 FILESTREAM data cannot be placed on an empty filegroup.
798 1720 Cannot drop FILESTREAM filegroup or partition scheme since table '%.*ls' has FILESTREAM columns.
799 1721 Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes.
800 1722 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme is not specified for FILESTREAM data.
801 1723 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specified for FILESTREAM data but not for the table.
802 1724 Filegroup '%.*ls' is not a FILESTREAM filegroup or partition scheme of FILESTREAM filegroups.
803 1725 Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEAD OF trigger exists on the %S_MSG.
804 1726 Cannot add FILESTREAM filegroup or partition scheme since table '%.*ls' has a FILESTREAM filegroup or partition scheme already.
805 1727 Cannot create non-clustered index '%.*ls' on table '%.*ls' with the FILESTREAM_ON clause.
806 1728 Cannot create index '%.*ls' on table '%.*ls' because the computed column '%.*ls' uses a FILESTREAM column.
807 1729 Cannot create table '%.*ls' because the partitioning column '%.*ls' uses a FILESTREAM column.
808 1730 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.
809 1731 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.
810 1732 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.
811 1733 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.
812 1734 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.
813 1736 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 a CHECK constraint or computed column definition.
814 1738 Cannot create table '%.*ls' with only a column set column and without any non-computed columns in the table.
815 1750 Could not create constraint. See previous errors.
816 1752 Column '%.*ls' in table '%.*ls' is invalid for creating a default constraint.
817 1753 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.
818 1754 Defaults cannot be created on columns with an IDENTITY attribute. Table '%.*ls', column '%.*ls'.
819 1755 Defaults cannot be created on columns of data type timestamp. Table '%.*ls', column '%.*ls'.
820 1756 Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary tables.
821 1757 Column '%.*ls.%.*ls' is not of same collation as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
822 1758 Only a single constraint can be added or dropped online with no other operations in the same statement.
823 1759 Computed column '%.*ls' in table '%.*ls' is not allowed to be used in another computed-column definition.
824 1760 Constraints of type %ls cannot be created on columns of type %ls.
825 1761 Cannot create the foreign key "%.*ls" with the SET NULL referential action, because one or more referencing columns are not nullable.
826 1762 Cannot create the foreign key "%.*ls" with the SET DEFAULT referential action, because one or more referencing not-nullable columns lack a default constraint.
827 1763 Cross-database foreign key references are not supported. Foreign key '%.*ls'.
828 1764 Computed Column '%.*ls' in table '%.*ls' is invalid for use in '%ls' because it is not persisted.
829 1765 Foreign key '%.*ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.*ls'.
830 1766 Foreign key references to temporary tables are not supported. Foreign key '%.*ls'.
831 1767 Foreign key '%.*ls' references invalid table '%.*ls'.
832 1768 Foreign key '%.*ls' references object '%.*ls' which is not a user table.
833 1769 Foreign key '%.*ls' references invalid column '%.*ls' in referencing table '%.*ls'.
834 1770 Foreign key '%.*ls' references invalid column '%.*ls' in referenced table '%.*ls'.
835 1771 Cannot create foreign key '%.*ls' because it references object '%.*ls' whose clustered index '%.*ls' is disabled.
836 1772 Foreign key '%.*ls' is not valid. A system table cannot be used in a foreign key definition.
837 1773 Foreign key '%.*ls' has implicit reference to object '%.*ls' which does not have a primary key defined on it.
838 1774 The number of columns in the referencing column list for foreign key '%.*ls' does not match those of the primary key in the referenced table '%.*ls'.
839 1775 Cannot create foreign key '%.*ls' because it references object '%.*ls' whose PRIMARY KEY index '%.*ls' is disabled.
840 1776 There are no primary or candidate keys in the referenced table '%.*ls' that match the referencing column list in the foreign key '%.*ls'.
841 1778 Column '%.*ls.%.*ls' is not the same data type as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
842 1779 Table '%.*ls' already has a primary key defined on it.
843 1781 Column already has a DEFAULT bound to it.
844 1784 Cannot create the foreign key '%.*ls' because the referenced column '%.*ls.%.*ls' is a non-persisted computed column.
845 1785 Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.
846 1786 Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with cascading referential integrity constraints.
847 1787 Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIGGER defined on it.
848 1788 Cascading foreign key '%.*ls' cannot be created where the referencing column '%.*ls.%.*ls' is an identity column.
849 1789 Cannot use CHECKSUM(*) in a computed column definition.
850 1790 The name of a user-defined table type cannot start with a number (#) sign.
851 1791 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.
852 1801 Database '%.*ls' already exists. Choose a different database name.
853 1802 CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
854 1803 The CREATE DATABASE statement failed. The primary file must be at least %d MB to accommodate a copy of the model database.
855 1806 CREATE DATABASE failed. The default collation of database '%.*ls' cannot be set to '%.*ls'.
856 1807 Could not obtain exclusive lock on database '%.*ls'. Retry the operation later.
857 1810 The model database must be updatable before a new database can be created.
858 1812 CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option.
859 1813 Could not open new database '%.*ls'. CREATE DATABASE is aborted.
860 1814 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.
861 1815 The %ls property cannot be used with database snapshot files.
862 1816 Database snapshot on the system database %.*ls is not allowed.
863 1817 Only the owner of database "%.*s" or the system administrator can create a database snapshot on it.
864 1818 Primary log file '%ls' is missing and the database was not cleanly shut down so it cannot be rebuilt.
865 1819 Could not create default log file because the name was too long.
866 1821 Cannot create a database snapshot on another database snapshot.
867 1822 The database must be online to have a database snapshot.
868 1823 A database snapshot cannot be created because it failed to start.
869 1824 Cannot attach a database that was being restored.
870 1825 Filegroups and collations cannot be specified for database snapshots.
871 1826 User-defined filegroups are not allowed on "%ls".
872 1827 CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of %I64d MB per %S_MSG.
873 1828 The logical file name "%.*ls" is already in use. Choose a different name.
874 1829 The FOR ATTACH option requires that at least the primary file be specified.
875 1830 The files '%.*ls' and '%.*ls' are both primary files. A database can only have one primary file.
876 1831 File ONLINE/OFFLINE syntax cannot be used with CREATE DATABASE.
877 1832 Cannot attach the file '%.*ls' as database '%.*ls'.%.*ls
878 1833 File '%ls' cannot be reused until after the next BACKUP LOG operation.
879 1834 The file '%ls' cannot be overwritten. It is being used by database '%.*ls'.
880 1835 Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d.
881 1836 Cannot create the default data files because the name that was supplied is too long.
882 1837 The file name "%ls" is too long to create an alternate stream name.
883 1838 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.
884 1839 Could not create default data files because the name '%ls' is a reserved device name.
885 1840 Could not create snapshot database because it is not supported on READONLY single-file user databases.
886 1842 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.
887 1843 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.
888 1844 %ls is not supported on %ls.
889 1845 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.
890 1846 Cannot find SQL Volume Shadow Copy (VSS) Writer component for database '%ls' while creating auto-recovered VSS snapshot for online DBCC check.
891 1847 The current version of the operating system doesn't support auto-recovered Volume Shadow Copy (VSS) snapshots.
892 1848 Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database '%ls' for online DBCC check.
893 1901 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.
894 1902 Cannot create more than one clustered index on %S_MSG '%.*ls'. Drop the existing clustered index '%.*ls' before creating another.
895 1904 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.
896 1907 Cannot recreate index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index.
897 1908 Column '%.*ls' is partitioning column of the index '%.*ls'. Partition columns for a unique index must be a subset of the index key.
898 1909 Cannot use duplicate column names in %S_MSG. Column name '%.*ls' listed more than once.
899 1910 Could not create %S_MSG '%.*ls' because it exceeds the maximum of %d allowed per table or view.
900 1911 Column name '%.*ls' does not exist in the target table or view.
901 1912 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.
902 1913 The operation failed because an index or statistics with name '%.*ls' already exists on %S_MSG '%.*ls'.
903 1914 Index cannot be created on object '%.*ls' because the object is not a user table or view.
904 1915 Cannot alter a non-unique index with ignore_dup_key index option. Index '%.*ls' is non-unique.
905 1916 CREATE INDEX options %ls and %ls are mutually exclusive.
906 1917 Cannot create, rebuild or drop an index on a local temporary table online. Perform the index operation offline.
907 1919 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index.
908 1921 Invalid %S_MSG '%.*ls' specified.
909 1922 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.
910 1924 Filegroup '%.*ls' is read-only.
911 1925 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.
912 1927 There are already statistics on table '%.*ls' named '%.*ls'.
913 1929 Statistics cannot be created on object '%.*ls' because the object is not a user table or view.
914 1930 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.
915 1931 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.
916 1934 %ls failed because the following SET options have incorrect settings: '%.*ls'. Verify that SET options are correct for use with %S_MSG.
917 1935 Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'.
918 1937 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.
919 1938 Index cannot be created on view '%.*ls' because the underlying object '%.*ls' has a different owner.
920 1939 Cannot create %S_MSG on view '%.*ls' because the view is not schema bound.
921 1940 Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index.
922 1941 Cannot create nonunique clustered index on view '%.*ls' because only unique clustered indexes are allowed. Consider creating unique clustered index instead.
923 1942 Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, image, FILESTREAM or xml columns.
924 1944 Index '%.*ls' was not created. This index has a key length of at least %d bytes. The maximum permissible key length is %d bytes.
925 1945 Warning! The maximum key length is %d bytes. The index '%.*ls' has maximum length of %d bytes. For some combination of large values, the insert/update operation will fail.
926 1946 Operation failed. The index entry of length %d bytes for the index '%.*ls' exceeds the maximum length of %d bytes.
927 1947 Cannot create %S_MSG on view "%.*ls". The view contains a self join on "%.*ls".
928 1949 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.
929 1956 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.
930 1957 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.
931 1959 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.
932 1961 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.
933 1962 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.
934 1963 Cannot create %S_MSG on view "%.*ls". The view contains a convert that is imprecise or non-deterministic.
935 1964 Cannot create %S_MSG on view "%.*ls". The view contains an imprecise constant.
936 1965 Cannot create %S_MSG on view "%.*ls". The view contains an imprecise arithmetic operator.
937 1966 Cannot create %S_MSG on view '%.*ls'. The view contains an imprecise aggregate operator.
938 1967 Cannot create a new clustered index on a view online.
939 1968 Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option.
940 1969 Default FILESTREAM filegroup is not available in database '%.*ls'.
941 1970 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.
942 1971 Cannot disable index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that uses this index.
943 1972 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to alter the referencing view '%.*ls' while disabling its clustered index.
944 1973 Cannot perform the specified operation on disabled index '%.*ls' on %S_MSG '%.*ls'.
945 1974 Cannot perform the specified operation on %S_MSG '%.*ls' because its clustered index '%.*ls' is disabled.
946 1975 Index '%.*ls' row length exceeds the maximum permissible length of '%d' bytes.
947 1976 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.
948 1977 Could not create %S_MSG '%.*ls' on table '%.*ls'. Only XML Index can be created on XML column '%.*ls'.
949 1978 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index or statistics.
950 1979 Cannot use index option ignore_dup_key to alter index '%.*ls' as it enforces a primary or unique constraint.
951 1980 Index cannot be created on computed column '%.*ls' of table '%.*ls' because the underlying object '%.*ls' has a different owner.
952 1981 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.
953 1982 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.
954 1983 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.
955 1984 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.
956 1985 Cannot create %S_MSG on view '%.*ls'. It contains one or more XML data type methods.
957 1986 Cannot replace non-hypothetical index '%.*ls' with a hypothetical index using the DROP_EXISTING option.
958 1987 Cannot %S_MSG %S_MSG '%.*ls' on %S_MSG '%.*ls' because its %S_MSG is disabled.
959 1988 Cannot rebuild clustered index '%.*ls' online because it is disabled.
960 1989 Cannot enable foreign key constraint '%.*ls' as index '%.*ls' on referenced key is disabled.
961 1990 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.
962 1991 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that references this table.
963 1992 Warning: Foreign key '%.*ls' on table '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.
964 1993 Cannot partition an index on a table variable or return table definition in table valued function.
965 1994 Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required.
966 1995 Cannot rebuild hypothetical index '%.*ls' online.
967 1996 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.
968 1997 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.
969 1998 Warning: Clustered index '%.*ls' on view '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'.
970 1999 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as included column in an index.
971 2002 Cannot create a procedure for replication with group number greater than one.
972 2003 Procedures with a group number cannot have parameters of XML or CLR types. Parameter '%.*ls' of procedure '%.*ls' has type '%ls'.
973 2004 Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number.
974 2007 The module '%.*ls' depends on the missing object '%.*ls'. The module will still be created; however, it cannot run successfully until the object exists.
975 2008 The object '%.*ls' is not a procedure so you cannot create another procedure under that group name.
976 2010 Cannot perform alter on '%.*ls' because it is an incompatible object type.
977 2011 Index hints cannot be specified within a schema-bound object.
978 2013 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.
979 2014 Remote access is not allowed from within a schema-bound object.
980 2020 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.
981 2101 Cannot %S_MSG a server level %S_MSG for user '%.*ls' since there is no login corresponding to the user.
982 2102 Cannot %S_MSG %S_MSG '%.*ls' since there is no user for login '%.*ls' in database '%.*ls'.
983 2103 Cannot %S_MSG trigger '%.*s' because its schema is different from the schema of the target table or view.
984 2104 Cannot %S_MSG the %S_MSG '%.*ls', because you do not have permission.
985 2108 Cannot %S_MSG %S_MSG on '%.*ls' as the target is not in the current database.
986 2110 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.
987 2111 Cannot %S_MSG trigger '%.*ls' on %S_MSG '%.*ls' because an INSTEAD OF %s trigger already exists on this object.
988 2112 Cannot create trigger '%.*ls' on view '%.*ls' because the view is defined with CHECK OPTION.
989 2113 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.
990 2114 Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column.
991 2115 Server level event notifications are disabled as the database msdb does not exist.
992 2116 Cannot CREATE EVENT NOTIFICATION to database '%.*ls' because it is not a valid broker database.
993 2117 Cannot %S_MSG INSTEAD OF trigger '%.*ls' on %S_MSG '%.*ls' because the %S_MSG has a FILESTREAM column.
994 2201 %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.
995 2202 %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.
996 2203 %sOnly 'http://www.w3.org/2001/XMLSchema#decimal?', 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed as predicates, found '%ls'
997 2204 %sOnly 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed in conditions and with logical operators, found '%ls'
998 2205 %s"%ls" was expected.
999 2206 %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.
1000 2207 %sOnly non-document nodes can be inserted. Found "%ls".
1001 2208 %sThe URI that starts with '%ls' is too long. Maximum allowed length is %d characters.
1002 2209 %sSyntax error near '%ls'
1003 2210 %sHeterogeneous sequences are not allowed: found '%ls' and '%ls'
1004 2211 %sSingleton (or empty sequence) required, found operand of type '%ls'
1005 2212 %sInvalid source character '%c' (0x%02x) found in an identifier near '%ls'.
1006 2213 %sCannot atomize/apply data() on expression that contains type '%ls' within inferred type '%ls'
1007 2214 %sThe type '%ls' is not an atomic type
1008 2215 %sThe value of attribute '%ls' exceeds 4000 characters, the maximum permitted in XML schema documents
1009 2216 %sInvalid XPath value in "%ls".
1010 2217 %s'%ls' or '%ls' expected
1011 2218 %sThere is no attribute named '@%ls'
1012 2219 %sThere is no attribute named '@%ls' in the type '%ls'.
1013 2220 %sThere is no attribute named '@%ls:%ls'
1014 2221 %sThere is no attribute named '@%ls:%ls' in the type '%ls'.
1015 2222 %sInvalid source character 0x%02x found in an identifier near '%ls'.
1016 2223 %sSyntax error near '%ls', expected an identifier.
1017 2225 %sA string literal was expected
1018 2226 %sThe target of 'insert' must be a single node, found '%ls'
1019 2227 %sThe variable '%ls' was not found in the scope in which it was referenced.
1020 2228 %sThe variable '%ls:%ls' was not found in the scope in which it was referenced.
1021 2229 %sThe name "%ls" does not denote a namespace.
1022 2230 %sThe name "%ls" has already been defined.
1023 2231 %sThe name "%ls" does not denote a defined type.
1024 2232 %sThe name "%ls:%ls" does not denote a defined type.
1025 2233 %sThe operand of "%ls" has an invalid type.
1026 2234 %sThe operator "%ls" cannot be applied to "%ls" and "%ls" operands.
1027 2235 %sAn argument list was applied to a non-function term.
1028 2236 %sThere are not enough actual arguments in the call to function "%ls".
1029 2237 %sDerivation from anyType by extension is not supported in this release.
1030 2238 %sToo many arguments in call to function '%ls'
1031 2240 %sThe target of 'insert into' must be an element/document node, found '%ls'
1032 2241 %sVariable expected: '$name'
1033 2242 %sType specification expected.
1034 2243 %sRelative path expression used without any context
1035 2247 %sThe value is of type "%ls", which is not a subtype of the expected type "%ls".
1036 2248 %sSyntax error near '%ls', expected 'as', 'into', 'before' or 'after'.
1037 2249 %sThe target of 'insert before/after' must be an element/PI/comment/text node, found '%ls'
1038 2256 %sSyntax error near '%ls', expected a "node test".
1039 2258 %sThe position may not be specified when inserting an attribute node, found '%ls'
1040 2260 %sThere is no element named '%ls'
1041 2261 %sThere is no element named '%ls' in the type '%ls'.
1042 2262 %sThere is no element named '%ls:%ls'
1043 2263 %sThere is no element named "%ls:%ls" in the type "%ls".
1044 2264 %sOnly non-document nodes may be deleted, found '%ls'
1045 2266 %sExpected end tag '%ls:%ls'
1046 2267 %sExpected end tag '%ls'
1047 2268 %sEnd tag '/%ls:%ls' has no matching begin tag
1048 2269 %sEnd tag '/%ls' has no matching begin tag
1049 2270 %sDuplicate attribute '%ls:%ls'
1050 2271 %sDuplicate attribute '%ls'
1051 2272 %s'?>' expected
1052 2273 %sUnterminated CDATA section
1053 2274 %sUnterminated string constant (started on line %u)
1054 2275 %sUnterminated XML declaration
1055 2276 %sDerivation from 'QName' by restriction is not supported in this release
1056 2277 %sA tag name may not contain the character '%c'
1057 2278 %sA tag name may not start with the character '%c'
1058 2279 %sA name/token may not start with the character '%c'
1059 2280 %s

1060 2281 %sCannot construct DTDs in XQuery
1061 2282 %sInvalid entity reference
1062 2283 %sThe character '%c' may not be part of an entity reference
1063 2284 %sThe namespace prefix '%ls' has not been defined
1064 2285 %sInvalid numeric entity reference
1065 2291 %sNo root element was found.
1066 2292 %sWhen a type with simple content restricts a type with mixed content, it must have an embedded simple type definition. Location: '%ls'.
1067 2293 %sChoice cannot be empty unless minOccurs is 0. Location: '%ls'.
1068 2294 %s'xml' is not allowed as a processing instruction target.
1069 2297 %sElement <%ls> is not valid at location '%ls'.
1070 2298 %sAttribute '%ls' is not valid at location '%ls'.
1071 2299 %sRequired attribute "%ls" of XSD element "%ls" is missing.
1072 2300 %sRequired sub-element "%ls" of XSD element "%ls" is missing.
1073 2301 %sThe element "%ls" has already been defined.
1074 2302 %sThe name "%ls" has already been defined in this scope.
1075 2305 %sElement or attribute type specified more than once. Location: '%ls'.
1076 2306 %sThe qualified name "%ls" was found in a context where only NCName is allowed.
1077 2307 %sReference to an undefined name '%ls'
1078 2308 %sReference to an undefined name '%ls' within namespace '%ls'
1079 2309 %sThe value of "%ls" is not a valid number.
1080 2310 %sThe attribute "%ls" is declared more than once.
1081 2311 %sThe attribute "%ls" is declared more than once within "%ls".
1082 2312 %sThe value of attribute '%ls' does not conform to the type definition 'http://www.w3.org/2001/XMLSchema#%ls': '%ls'.
1083 2313 %sThe attribute "%ls" cannot have a value of "%ls".
1084 2314 %sThe attribute "%ls" cannot have a negative value.
1085 2315 %sThe attribute "%ls" should have a string value.
1086 2316 %sThe required 'base' attribute is missing. Location: '%ls'.
1087 2317 %sThe base type "%ls" defined on XSD element "%ls" is not a simple type.
1088 2319 %sThis type may not have a '%ls' facet. Location: '%ls'.
1089 2320 %sDuplicate facet '%ls' found at location '%ls'.
1090 2321 %sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'.
1091 2322 %sThe element type is not a subclass of the substitution group's head
1092 2323 %sThe end tag '%ls' doesn't match opening tag '%ls' from line %u
1093 2324 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls' from line %u
1094 2325 %sThe end tag '%ls' doesn't match opening tag '%ls:%ls' from line %u
1095 2326 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls:%ls' from line %u
1096 2327 %sThe content or definition of <%ls> is missing.
1097 2328 %sSchema namespace '%ls' doesn't match directive's '%ls'
1098 2329 %sThe string "%ls" is not a valid time duration value.
1099 2331 %sRedefinition has to have itself as base type. Location: '%ls'.
1100 2332 %s'%ls' may not be used with an 'empty' operand
1101 2333 %sInvalid source character 0x%02x
1102 2334 %sInvalid source character '%c' (0x%02x)
1103 2335 %sNewline in character/string constant
1104 2336 %s'%c' is not a valid octal digit (numbers starting with '0' are implicitly octal)
1105 2337 %sThe target of 'replace' must be at most one node, found '%ls'
1106 2338 %sThe second 'replace' operand must contain only nodes, found '%ls'
1107 2339 %sEither a memberType attribute or a simpleType child must be present. Location: '%ls'.
1108 2340 %sComment started on line %u has no end
1109 2341 %sExpected hex character code following '\\x'
1110 2342 %sInvalid numeric constant.
1111 2343 %sUnterminated text section - missing `
1112 2348 %sA namespace URI should contain at least one non-whitespace character.
1113 2349 %sAttempt to redefine namespace prefix '%ls'
1114 2350 %sInvalid XML element content
1115 2351 %sExpected 'first' or 'last'
1116 2353 %s'to' or 'insert' or 'delete' expected
1117 2354 %sInvalid source character encoding
1118 2355 %s'else' expected
1119 2356 %sThe target of 'replace value of' must be a non-metadata attribute or an element with simple typed content, found '%ls'
1120 2357 %sA document node may only be replaced with another document node, found '%ls'
1121 2358 %sDerivation with both a 'base' attribute and an embedded type definition is not supported in this release. Location: '%ls'.
1122 2359 %sThe target of '%ls' may not be a constructed node
1123 2360 %sCannot have both a 'name' and 'ref' attribute. Location: '%ls'.
1124 2361 %sThe base type of an XSD extension or restriction type must be a simple type.
1125 2362 %sXSD schema too complex
1126 2363 %sXQuery too complex
1127 2364 %sCannot implicitly convert from '%ls' to '%ls'
1128 2365 %sCannot explicitly convert from '%ls' to '%ls'
1129 2366 %s"%ls" has a circular definition.
1130 2367 %sThe item type of an XSD list type must be a simple type. Location: '%ls'.
1131 2368 %sCannot have element content in a complex type with simple content. Location: '%ls'.
1132 2369 %sCannot have more than one group/sequence/choice/all within a restriction or extension. Location: '%ls'.
1133 2370 %sNo more tokens expected at the end of the XQuery expression. Found '%ls'.
1134 2371 %s'%ls' can only be used within a predicate or XPath selector
1135 2372 %sMetadata attribute '@%ls:%ls' may not be used with '%ls'
1136 2373 %s%ls is not supported with constructed XML
1137 2374 %sA node or set of nodes is required for %ls
1138 2375 %sAggregate function '%ls' expects a sequence argument
1139 2376 %sOperand of a single numeric type expected
1140 2377 %sResult of '%ls' expression is statically 'empty'
1141 2378 %sExpected XML schema document
1142 2379 %sThe name specified is not a valid XML name :'%ls'
1143 2380 %sMixed content is not allowed at location '%ls'.
1144 2382 %sInvalid combination of minOccurs and maxOccurs values, minOccurs has to be less than or equal to maxOccurs. Location: '%ls'.
1145 2383 %sInvalid value '%ls' for the %ls attribute. The value has to be between 0 and %ld.
1146 2384 %sInvalid element occurrence, element '%ls' was found multiple times in the context of element '%ls'
1147 2385 Invalid target namespace specified
1148 2386 %sThe value of '%ls' facet is outside of the allowed range
1149 2387 %sCannot have both 'type' and 'ref' attributes. Location: '%ls'.
1150 2388 %sInvalid element occurrence, element '%ls' has to appear first in the context of '%ls'
1151 2389 %s'%ls' requires a singleton (or empty sequence), found operand of type '%ls'
1152 2390 %sTop-level %s nodes are not supported
1153 2391 %sRedefining XSD schemas is not supported
1154 2392 %s'%ls::' is not a valid axis
1155 2393 %sEither an itemType attribute or a simpleType child must be present. Location: '%ls'.
1156 2394 %sThere is no function '%ls()'
1157 2395 %sThere is no function '%ls:%ls()'
1158 2396 %sAttribute may not appear outside of an element
1159 2397 %sIdentifiers may not contain more than %u characters
1160 2398 %sDuplicate id value found: '%ls'
1161 2399 %sAn attribute cannot have a value of type '%ls', a simple type was expected
1162 2501 Cannot find a table or object with the name "%.*ls". Check the system catalog.
1163 2502 Memory object list dump failed due to temporary inconsistency in the memory object structure. Please try again.
1164 2503 Successfully deleted the physical file '%ls'.
1165 2504 Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls.
1166 2505 The device '%.*ls' does not exist. Use sys.backup_devices to show available devices.
1167 2506 Could not find a table or object name '%.*ls' in database '%.*ls'.
1168 2507 The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS.
1169 2508 The %.*ls count for object "%.*ls", index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE.
1170 2509 DBCC CHECKCONSTRAINTS failed due to an internal query error.
1171 2510 DBCC %ls error: %ls.
1172 2511 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.
1173 2512 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.
1174 2514 A DBCC PAGE error has occurred: %ls.
1175 2515 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.
1176 2516 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.
1177 2517 Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again.
1178 2518 Object ID %ld (object "%.*ls"): Computed columns and CLR types cannot be checked for this object because the common language runtime (CLR) is disabled.
1179 2519 Computed columns and CLR types cannot be checked for object ID %ld (object "%.*ls") because the internal expression evaluator could not be initialized.
1180 2520 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.
1181 2521 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.
1182 2522 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid.
1183 2523 Filegroup %.*ls is invalid.
1184 2524 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.
1185 2525 Database file %.*ls is offline.
1186 2526 Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.
1187 2527 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline.
1188 2528 DBCC execution completed. If DBCC printed error messages, contact your system administrator.
1189 2529 Filegroup %.*ls is offline.
1190 2530 The index "%.*ls" on table "%.*ls" is disabled.
1191 2531 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.
1192 2532 One or more WITH options specified are not valid for this command.
1193 2533 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.
1194 2534 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.
1195 2536 DBCC results for '%.*ls'.
1196 2537 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.
1197 2538 File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.
1198 2539 The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.
1199 2540 The system cannot self repair this error.
1200 2541 DBCC UPDATEUSAGE: Usage counts updated for table '%.*ls' (index '%.*ls', partition %ld):
1201 2542 DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.
1202 2543 USED pages %.*ls: changed from (%I64d) to (%I64d) pages.
1203 2544 RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.
1204 2545 ROWS count: changed from (%I64d) to (%I64d) rows.
1205 2546 Index '%.*ls' on table '%.*ls' is marked as disabled. Rebuild the index to bring it online.
1206 2547 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.
1207 2548 DBCC: Compaction phase of index '%.*ls' is %d%% complete.
1208 2549 DBCC: Defrag phase of index '%.*ls' is %d%% complete.
1209 2550 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because it is being reorganized by another process.
1210 2551 The indexes on table "%.*ls" cannot be reorganized because there is already an online index build or rebuild in progress on the table.
1211 2552 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because page level locking is disabled.
1212 2553 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.
1213 2554 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because the filegroup is read-only.
1214 2555 Cannot move all contents of file "%.*ls" to other places to complete the emptyfile operation.
1215 2556 There is insufficient space in the filegroup to complete the emptyfile operation.
1216 2557 User '%.*ls' does not have permission to run DBCC %ls for object '%.*ls'.
1217 2558 %I64d incorrect counts were detected in database '%.*ls'.
1218 2559 The '%ls' and '%ls' options are not allowed on the same statement.
1219 2560 Parameter %d is incorrect for this DBCC statement.
1220 2561 Parameter %d is incorrect for this statement.
1221 2562 Checking FILESTREAM filegroup "%.*ls" (ID %d) is not supported in DBCC CHECKFILEGROUP. Specify a filegroup containing user objects with FILESTREAM data instead.
1222 2566 DBCC DBREINDEX cannot be used on system tables.
1223 2567 DBCC INDEXDEFRAG cannot be used on system table indexes
1224 2568 Page %S_PGID is out of range for this database or is in a log file.
1225 2570 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.
1226 2571 User '%.*ls' does not have permission to run DBCC %.*ls.
1227 2572 DBCC cannot free DLL '%.*ls'. The DLL is in use.
1228 2573 Could not find table or object ID %.*ls. Check system catalog.
1229 2574 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.
1230 2575 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.
1231 2576 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.
1232 2577 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.
1233 2579 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.
1234 2580 Table '%.*ls' is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table.
1235 2581 DBCC cannot free the DLL "%.*ls". The DLL is not loaded.
1236 2583 An incorrect number of parameters was given to the DBCC statement.
1237 2585 Cannot find partition number %ld for table "%.*ls".
1238 2586 Cannot find partition number %ld for index "%.*ls", table "%.*ls".
1239 2587 The invalid partition number %ld was specified.
1240 2588 Cannot find partition number %ld for index ID %d, object ID %d.
1241 2589 Repair could not fix all errors on the first attempt.
1242 2590 User "%.*ls" is modifying bytes %d to %d of page %S_PGID in database "%.*ls".
1243 2591 Cannot find a row in the system catalog with the index ID %d for table "%.*ls".
1244 2592 Repair: The %ls index successfully rebuilt for the object "%.*ls" in database "%.*ls".
1245 2593 There are %I64d rows in %I64d pages for object "%.*ls".
1246 2594 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.
1247 2596 The repair statement was not processed. The database cannot be in read-only mode.
1248 2597 Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup.
1249 2599 Cannot switch to in row text in table "%.*ls".
1250 2601 Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'.
1251 2627 Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'.
1252 2700 There are too many statements in the batch; the maximum number is %d
1253 2701 Database name '%.*ls' ignored, referencing object in tempdb.
1254 2702 Database '%.*ls' does not exist.
1255 2703 Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once.
1256 2704 Invalid partition scheme '%.*ls' specified.
1257 2705 Column names in each table must be unique. Column name '%.*ls' in table '%.*ls' is specified more than once.
1258 2706 Table '%.*ls' does not exist.
1259 2707 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.
1260 2709 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.
1261 2710 You are not the owner specified for the object '%.*ls' in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT).
1262 2711 The definition of object "%.*ls" in the resource database contains the non-ASCII character "%.*ls".
1263 2712 Database '%.*ls' can not be configured as a distribution database because it has change tracking enabled.
1264 2714 There is already an object named '%.*ls' in the database.
1265 2715 Column, parameter, or variable #%d: Cannot find data type %.*ls.
1266 2716 Column, parameter, or variable #%d: Cannot specify a column width on data type %.*ls.
1267 2717 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed (%d).
1268 2719 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.
1269 2720 Cannot schema bind %S_MSG '%.*ls' because it references system object '%.*ls'.
1270 2722 Xml data type methods are not allowed in expressions in this context.
1271 2724 Parameter or variable '%.*ls' has an invalid data type.
1272 2725 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 non-clustered 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.
1273 2726 Partition function '%.*ls' uses %d columns which does not match with the number of partition columns used to partition the table or index.
1274 2727 Cannot find index '%.*ls'.
1275 2728 Cannot partition on more than %d columns.
1276 2729 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it is non-deterministic.
1277 2730 Cannot create procedure '%.*ls' with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE '%.*ls';1 first.
1278 2731 Column '%.*ls' has invalid width: %d.
1279 2732 Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000.
1280 2733 The %ls data type is invalid for return values.
1281 2735 Cannot create primary xml or spatial index '%.*ls' on '%.*ls' because PRIMARY KEY constraint contains column(s) of type timestamp.
1282 2738 A table can only have one timestamp column. Because table '%.*ls' already has one, the column '%.*ls' cannot be added.
1283 2739 The text, ntext, and image data types are invalid for local variables.
1284 2740 SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server.
1285 2741 SET DATEFORMAT date order '%.*ls' is invalid.
1286 2742 SET DATEFIRST %d is out of range.
1287 2743 %ls statement requires %S_MSG parameter.
1288 2744 Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed.
1289 2745 Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process.
1290 2747 Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters.
1291 2748 Cannot specify %ls data type (parameter %d) as a substitution parameter.
1292 2749 Identity column '%.*ls' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, and constrained to be nonnullable.
1293 2750 Column or parameter #%d: Specified column precision %d is greater than the maximum precision of %d.
1294 2751 Column or parameter #%d: Specified column scale %d is greater than the specified precision of %d.
1295 2752 Identity column '%.*ls' contains invalid SEED.
1296 2753 Identity column '%.*ls' contains invalid INCREMENT.
1297 2754 Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option.
1298 2755 SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d ... %d] of type integer}.
1299 2756 Invalid value %d for state. Valid range is from %d to %d.
1300 2759 CREATE SCHEMA failed due to previous errors.
1301 2760 The specified schema name "%.*ls" either does not exist or you do not have permission to use it.
1302 2761 The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.
1303 2762 sp_setapprole was not invoked correctly. Refer to the documentation for more information.
1304 2766 The definition for user-defined data type '%.*ls' has changed.
1305 2767 Could not locate statistics '%.*ls' in the system catalogs.
1306 2770 The SELECT INTO statement cannot have same source and destination tables.
1307 2772 Cannot access temporary tables from within a function.
1308 2773 The collation ID is corrupted because the sort order ID %d is not valid.
1309 2774 Collation ID %d is invalid.
1310 2775 The code page %d is not supported by the server.
1311 2778 Only System Administrator can specify %s option for %s command.
1312 2779 The %S_MSG '%.*ls' is an auto-drop system object. It cannot be used in queries or DDL.
1313 2780 View '%.*ls' is not schemabound.
1314 2782 Cannot create table "%.*ls": A table must have a clustered primary key in order to have XML data type columns.
1315 2785 User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this context.
1316 2786 The data type of substitution parameter %d does not match the expected type of the format specification.
1317 2787 Invalid format specification: '%.*ls'.
1318 2788 Synonyms are invalid in a schemabound object or a constraint expression.
1319 2789 Must specify a two-part name for %S_MSG '%.*ls' in a schemabound object or a constraint expression.
1320 2790 Cannot use a column of type TEXT, NTEXT, or IMAGE in a constraint expression.
1321 2791 Could not resolve expression for Schema-bound object or constraint.
1322 2792 Cannot specify a sql CLR type in a Schema-bound object or a constraint expression.
1323 2793 Specified owner name '%.*ls' either does not exist or you do not have permission to act on its behalf.
1324 2794 Message text expects more than the maximum number of arguments (%d).
1325 2795 Could not %S_MSG %S_MSG because the new %S_MSG '%.*ls' does not match the FILESTREAM %S_MSG '%.*ls' of the table.
1326 2796 Cannot specify database name with $partition in a Schema-bound object, computed column or constraint expression.
1327 2797 The default schema does not exist.
1328 2798 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.
1329 2799 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.
1330 2801 The definition of object '%.*ls' has changed since it was compiled.
1331 2802 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.
1332 2803 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.
1333 2809 The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object.
1334 2812 Could not find stored procedure '%.*ls'.
1335 2813 "%.*ls" is not supported on this edition of SQL Server.
1336 2814 A possible infinite recompile was detected for SQLHANDLE %hs, PlanHandle %hs, starting offset %d, ending offset %d. The last recompile reason was %d.
1337 3002 Cannot BACKUP or RESTORE a database snapshot.
1338 3003 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.
1339 3004 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.
1340 3005 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.
1341 3006 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.
1342 3007 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.
1343 3008 The specified device type is not supported for backup mirroring.
1344 3009 Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
1345 3010 Invalid backup mirror specification. All mirrors must have the same number of members.
1346 3011 All backup devices must be of the same general class (for example, DISK and TAPE).
1347 3012 VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer.
1348 3013 %hs is terminating abnormally.
1349 3014 %hs successfully processed %I64d pages in %d.%03d seconds (%d.%03d MB/sec).
1350 3015 %hs is not yet implemented.
1351 3016 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.
1352 3017 The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Correct the problem, or reissue the command without RESTART.
1353 3018 The restart-checkpoint file '%ls' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
1354 3019 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.
1355 3021 Cannot perform a backup or restore operation within a transaction.
1356 3022 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.
1357 3023 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.
1358 3024 You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
1359 3025 Missing database name. Reissue the statement specifying a valid database name.
1360 3027 The filegroup "%.*ls" is not part of database "%.*ls".
1361 3028 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.
1362 3031 Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement.
1363 3032 One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options.
1364 3033 BACKUP DATABASE cannot be used on a database opened in emergency mode.
1365 3034 No files were selected to be processed. You may have selected one or more filegroups that have no members.
1366 3035 Cannot perform a differential backup for database "%ls", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.
1367 3036 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.
1368 3038 The file name "%ls" is invalid as a backup device name. Reissue the BACKUP statement with a valid file name.
1369 3039 Cannot perform a differential backup for file '%ls' because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option.
1370 3040 An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected.
1371 3041 BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages.
1372 3042 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.
1373 3043 BACKUP '%ls' detected an error on page (%d:%d) in file '%ls'.
1374 3044 Invalid zero-length device name. Reissue the BACKUP statement with a valid device name.
1375 3045 BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "%.*ls" is not usable.
1376 3046 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.
1377 3047 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.
1378 3049 BACKUP detected corruption in the database log. Check the errorlog for more information.
1379 3050 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.
1380 3051 BACKUP LOG was unable to maintain mirroring consistency for database '%ls'. Database mirroring has been suspended.
1381 3054 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.
1382 3055 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.
1383 3056 The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file '%ls'.
1384 3057 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.
1385 3058 File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls.
1386 3098 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.
1387 3101 Exclusive access could not be obtained because the database is in use.
1388 3102 %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.
1389 3103 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.
1390 3104 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.
1391 3105 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.
1392 3106 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.
1393 3107 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.
1394 3108 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.
1395 3109 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.
1396 3110 User does not have permission to RESTORE database '%.*ls'.
1397 3111 Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored.
1398 3112 Cannot restore any database other than master when the server is in single user mode.
1399 3113 Invalid data was detected.
1400 3115 The database is using the simple recovery model. It is not possible to restore a subset of the read-write data.
1401 3116 The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore.
1402 3117 The log or differential backup cannot be restored because no files are ready to rollforward.
1403 3118 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.
1404 3119 Problems were identified while planning for the RESTORE statement. Previous messages provide details.
1405 3120 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.
1406 3121 The file "%ls" is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue.
1407 3122 File initialization failed. RESTORE cannot continue.
1408 3123 Invalid database name '%.*ls' specified for backup or restore operation.
1409 3125 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.
1410 3127 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.
1411 3128 File '%ls' has an unsupported page size (%d).
1412 3129 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.
1413 3130 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.
1414 3131 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.
1415 3132 The media set has %d media families but only %d are provided. All members must be provided.
1416 3133 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.
1417 3134 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.
1418 3135 The backup set in file '%ls' was created by %hs and cannot be used for this restore operation.
1419 3136 This differential backup cannot be restored because the database has not been restored to the correct earlier state.
1420 3137 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.
1421 3138 The database cannot be reverted because FILESTREAM BLOBs are present.
1422 3139 Restore to snapshot is not allowed with the master database.
1423 3140 Could not adjust the space allocation for file '%ls'.
1424 3141 The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database.
1425 3142 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.
1426 3143 The data set on device '%ls' is not a SQL Server backup set.
1427 3144 File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set.
1428 3145 The STOPAT option is not supported for databases that use the SIMPLE recovery model.
1429 3147 Backup and restore operations are not allowed on database tempdb.
1430 3148 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.
1431 3149 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.
1432 3150 The master database has been successfully restored. Shutting down SQL Server.
1433 3151 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.
1434 3153 The database is already fully recovered.
1435 3154 The backup set holds a backup of a database other than the existing '%ls' database.
1436 3155 The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created.
1437 3156 File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identify a valid location for the file.
1438 3159 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.
1439 3161 The primary file is unavailable. It must be restored or otherwise made available.
1440 3163 The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.
1441 3165 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.
1442 3166 RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement.
1443 3167 RESTORE could not start database '%ls'.
1444 3168 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).
1445 3169 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.
1446 3170 The STANDBY filename is invalid.
1447 3171 File %ls is defunct and cannot be restored into the online database.
1448 3172 Filegroup %ls is defunct and cannot be restored into the online database.
1449 3173 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.
1450 3174 The file '%ls' cannot be moved by this RESTORE operation.
1451 3175 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.
1452 3176 File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files.
1453 3178 File %ls is not in the correct state to have this differential backup applied to it.
1454 3179 The system database cannot be moved by RESTORE.
1455 3180 This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.
1456 3181 Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.
1457 3182 The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR.
1458 3183 RESTORE detected an error on page (%d:%d) in database "%ls" as read from the backup set.
1459 3184 RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible.
1460 3185 RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage.
1461 3186 The backup set has been damaged. RESTORE will not attempt to apply this backup set.
1462 3187 RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
1463 3188 The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.
1464 3189 Damage to the backup set was detected.
1465 3190 Filegroup '%ls' cannot be restored because it does not exist in the backup set.
1466 3191 Restore cannot continue because file '%ls' cannot be written. Ensure that all files in the database are writable.
1467 3192 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.
1468 3194 Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored.
1469 3195 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.
1470 3196 RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file.
1471 3197 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.
1472 3198 I/O was resumed on database %ls. No user action is required.
1473 3199 RESTORE requires MAXTRANSFERSIZE=%u but %u was specified.
1474 3201 Cannot open backup device '%ls'. Operating system error %ls.
1475 3202 Write on "%ls" failed: %ls
1476 3203 Read on "%ls" failed: %ls
1477 3204 The backup or restore was aborted.
1478 3205 Too many backup devices specified for backup or restore; only %d are allowed.
1479 3206 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.
1480 3207 Backup or restore requires at least one backup device. Rerun your statement specifying a backup device.
1481 3208 Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error log for more details.
1482 3209 Operation is not supported on user instances.
1483 3210 The mirror member in drive "%ls" is inconsistent with the mirror member in drive "%ls".
1484 3211 %d percent processed.
1485 3212 The mirror device "%ls" and the mirror device "%ls" have different device specifications.
1486 3213 Unable to unload one or more tapes. See the error log for details.
1487 3214 Too many backup mirrors are specified. Only %d are allowed.
1488 3215 Use WITH FORMAT to create a new mirrored backup set.
1489 3216 RESTORE REWINDONLY is only applicable to tape devices.
1490 3217 Invalid value specified for %ls parameter.
1491 3218 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.
1492 3219 The file or filegroup "%.*ls" cannot be selected for this operation.
1493 3221 The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d.
1494 3222 The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d.
1495 3224 Cannot create worker thread.
1496 3227 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.
1497 3229 Request for device '%ls' timed out.
1498 3230 Operation on device '%ls' exceeded retry count.
1499 3231 The media loaded on "%ls" is formatted to support %d media families, but %d media families are expected according to the backup device specification.
1500 3232 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.
1501 3234 Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names.
1502 3235 The file "%.*ls" is not part of database "%ls". You can only list files that are members of this database.
1503 3239 The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server.
1504 3240 Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set.
1505 3241 The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family.
1506 3242 The file on device '%ls' is not a valid Microsoft Tape Format backup set.
1507 3243 The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d.
1508 3244 Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation.
1509 3245 Could not convert a string to or from Unicode, %ls.
1510 3246 The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media.
1511 3247 The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d.
1512 3249 The volume on device '%ls' is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set.
1513 3250 The value '%d' is not within range for the %ls parameter.
1514 3251 The media family on device '%ls' is complete. The device is now being reused for one of the remaining families.
1515 3253 The block size parameter must supply a value that is a power of 2.
1516 3254 The volume on device '%ls' is empty.
1517 3255 The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server.
1518 3256 The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally.
1519 3257 There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64u bytes are available.
1520 3258 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.
1521 3260 An internal buffer has become full.
1522 3261 SQL Server cannot use the virtual device configuration.
1523 3262 The backup set on file %d is valid.
1524 3263 Cannot use the volume on device '%ls' as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, or sequence number %d of family %d for the current set.
1525 3264 The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
1526 3265 The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE.
1527 3266 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.
1528 3267 Insufficient resources to create UMS scheduler.
1529 3268 Cannot use the backup file '%ls' because it was originally formatted with sector size %d and is now on a device with sector size %d.
1530 3269 Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d.
1531 3270 An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance.
1532 3271 A nonrecoverable I/O error occurred on file "%ls:" %ls.
1533 3272 The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement using a compatible block size.
1534 3276 WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.
1535 3277 WITH SNAPSHOT must be used with only one virtual device.
1536 3278 Failed to encrypt string %ls
1537 3279 Access is denied due to a password failure
1538 3280 Backups on raw devices are not supported. '%ls' is a raw device.
1539 3281 Released and initiated rewind on '%ls'.
1540 3283 The file "%ls" failed to initialize correctly. Examine the error logs for more details.
1541 3284 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.
1542 3301 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.
1543 3302 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.
1544 3313 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.
1545 3314 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.
1546 3315 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.
1547 3316 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.
1548 3401 Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery.
1549 3402 The database '%ls' is marked %ls and is in a state that does not allow recovery to be run.
1550 3403 Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
1551 3404 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.
1552 3406 %d transactions rolled forward in database '%.*ls' (%d). This is an informational message only. No user action is required.
1553 3407 %d transactions rolled back in database '%.*ls' (%d). This is an informational message only. No user action is required.
1554 3408 Recovery is complete. This is an informational message only. No user action is required.
1555 3409 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.
1556 3410 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.
1557 3411 Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
1558 3412 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.
1559 3413 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.
1560 3414 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.
1561 3415 Database '%.*ls' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
1562 3416 The server contains read-only files that must be made writable before the server can be recollated.
1563 3417 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.
1564 3418 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.
1565 3419 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.
1566 3420 Database snapshot '%ls' has failed an IO operation and is marked suspect. It must be dropped and recreated.
1567 3421 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.
1568 3422 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.
1569 3429 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.
1570 3431 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.
1571 3434 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.
1572 3437 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.
1573 3441 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.
1574 3442 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.
1575 3443 Database '%.*ls' (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.
1576 3445 File '%ls' is not a valid undo file for database '%.*ls (database ID %d). Verify the file path, and specify the correct file.
1577 3446 Primary log file is not available for database '%.*ls'. The log cannot be backed up.
1578 3447 Could not activate or scan all of the log files for database '%.*ls'.
1579 3448 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.
1580 3449 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.
1581 3450 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.
1582 3452 Recovery of database '%.*ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls').
1583 3453 This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible.
1584 3454 Recovery is writing a checkpoint in database '%.*ls' (%d). This is an informational message only. No user action is required.
1585 3456 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.
1586 3457 Transactional file system resource manager '%.*ls' failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.
1587 3458 Recovery cannot scan database "%.*ls" for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up.
1588 3505 Only the owner of database "%.*ls" or someone with relevant permissions can run the CHECKPOINT statement.
1589 3604 Duplicate key was ignored.
1590 3605 Schema verification failed for database '%.*ls'.
1591 3606 Arithmetic overflow occurred.
1592 3607 Division by zero occurred.
1593 3608 Cannot allocate a GUID for the token.
1594 3609 The transaction ended in the trigger. The batch has been aborted.
1595 3612 %hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms.
1596 3613 SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms.
1597 3615 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.
1598 3616 An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
1599 3619 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.
1600 3620 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.
1601 3621 The statement has been terminated.
1602 3622 Warning: An invalid floating point operation occurred.
1603 3623 An invalid floating point operation occurred.
1604 3624 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.
1605 3625 '%hs' is not yet implemented.
1606 3627 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.
1607 3628 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.
1608 3633 The operating system returned the error '%ls' while attempting '%ls' on '%ls' at '%hs'(%d).
1609 3634 The operating system returned the error '%ls' while attempting '%ls' on '%ls'.
1610 3635 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.
1611 3636 An error occurred while processing '%ls' metadata for database id %d file id %d.
1612 3637 A parallel operation cannot be started from a DAC connection.
1613 3638 SQL text cache memory usage: %d pages. This is an informational message only; no user action is required.
1614 3639 This operation is not supported on a single-file DB.
1615 3701 Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission.
1616 3702 Cannot drop database "%.*ls" because it is currently in use.
1617 3703 Cannot detach the %S_MSG '%.*ls' because it is currently in use.
1618 3705 Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls.
1619 3706 Cannot %S_MSG a database snapshot.
1620 3707 Cannot detach a suspect or recovery pending database. It must be repaired or dropped.
1621 3708 Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG.
1622 3709 Cannot %S_MSG the database while the database snapshot "%.*ls" refers to it. Drop that database first.
1623 3710 Cannot detach an opened database when the server is in minimally configured mode.
1624 3716 The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG.
1625 3717 Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.
1626 3721 Type '%.*ls' cannot be renamed because it is being referenced by object '%.*ls'.
1627 3723 An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement.
1628 3724 Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for replication.
1629 3725 The constraint '%.*ls' is being referenced by table '%.*ls', foreign key constraint '%.*ls'.
1630 3726 Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint.
1631 3727 Could not drop constraint. See previous errors.
1632 3728 '%.*ls' is not a constraint.
1633 3729 Cannot %ls '%.*ls' because it is being referenced by object '%.*ls'.
1634 3730 Cannot drop the default constraint '%.*ls' while it is being used by a foreign key as SET DEFAULT referential action.
1635 3732 Cannot drop type '%.*ls' because it is being referenced by object '%.*ls'. There may be other objects that reference this type.
1636 3733 Constraint '%.*ls' does not belong to table '%.*ls'.
1637 3734 Could not drop the primary key constraint '%.*ls' because the table has an XML or spatial index.
1638 3735 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.
1639 3737 Could not delete file '%ls'. See the SQL Server error log for more information.
1640 3738 Deleting database file '%ls'.
1641 3739 Cannot %ls the index '%.*ls' because it is not a statistics collection.
1642 3740 Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup.
1643 3741 Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on an offline filegroup.
1644 3743 The database '%.*ls' is enabled for database mirroring. Database mirroring must be removed before you drop the database.
1645 3744 Only a single clause is allowed in a statement where an index is dropped online.
1646 3745 Only a clustered index can be dropped online.
1647 3746 Cannot drop the clustered index of view '%.*ls' because the view is being used for replication.
1648 3747 Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index '%.*ls' is created on view '%.*ls'.
1649 3748 Cannot drop non-clustered index '%.*ls' using drop clustered index clause.
1650 3749 Cannot drop XML Index '%.*ls' using old 'Table.Index' syntax, use 'Index ON Table' syntax instead.
1651 3750 Warning: Index '%.*ls' on %S_MSG '%.*ls' was disabled as a result of disabling the clustered index on the %S_MSG.
1652 3751 Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls.
1653 3801 Warning: The index "%.*ls" on "%.*ls"."%.*ls" may be impacted by the collation upgrade. Run DBCC CHECKTABLE.
1654 3802 Warning: The constraint "%.*ls" on "%.*ls"."%.*ls" may be impacted by the collation upgrade. Disable and enable WITH CHECK.
1655 3803 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the implementation of the checksum function has changed.
1656 3804 Warning: The check constraint "%.*ls" on table "%.*ls"."%.*ls" is disabled because the implementation of the checksum function has changed.
1657 3805 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.
1658 3806 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.
1659 3807 Create failed because all available identifiers have been exhausted.
1660 3808 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.
1661 3809 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.
1662 3810 Event notification "%.*ls" on assembly is dropped.
1663 3811 Event notification "%.*ls" on service queue is dropped as broker instance is not specified.
1664 3812 Event notification "%.*ls" on object is dropped.
1665 3813 Upgrade of login '%.*ls' failed because its name or sid is a duplicate of another login or server role.
1666 3814 Local login mapped to remote login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the remote login before upgrade.
1667 3815 Local login mapped to linked login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the linked login before upgrade.
1668 3816 Upgrade of login '%.*ls' failed because its password hash is invalid. Update the login password before upgrade.
1669 3817 Warning: The index "%.*ls" on "%.*ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed.
1670 3818 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.
1671 3819 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.
1672 3820 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.
1673 3821 Warning: The foreign key constraint "%.*ls" on "%.*ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed.
1674 3822 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.
1675 3823 Warning: The object "%.*ls"."%.*ls" could not be bound and was ignored during upgrade. Consider reviewing and correcting its definition.
1676 3851 An invalid row (%ls) was found in the system table sys.%ls%ls.
1677 3852 Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
1678 3853 Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
1679 3854 Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (%ls) in sys.%ls%ls that is invalid.
1680 3855 Attribute (%ls) exists without a row (%ls) in sys.%ls%ls.
1681 3856 Attribute (%ls) exists but should not for row (%ls) in sys.%ls%ls.
1682 3857 The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls.
1683 3858 The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid value.
1684 3859 Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE.
1685 3860 Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use.
1686 3862 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.
1687 3864 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.
1688 3901 The transaction name must be specified when it is used with the mark option.
1689 3902 The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
1690 3903 The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
1691 3904 Cannot unsplit logical page %S_PGID in object '%.*ls', in database '%.*ls'. Both pages together contain more data than will fit on one page.
1692 3906 Failed to update database "%.*ls" because the database is read-only.
1693 3908 Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in bypass recovery mode.
1694 3909 Session binding token is invalid.
1695 3910 Transaction context in use by another session.
1696 3912 Cannot bind using an XP token while the server is not in an XP call.
1697 3913 TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server.
1698 3914 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).
1699 3915 Cannot use the ROLLBACK statement within an INSERT-EXEC statement.
1700 3916 Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
1701 3917 Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
1702 3918 The statement or function must be executed in the context of a user transaction.
1703 3919 Cannot enlist in the transaction because the transaction has already been committed or rolled back.
1704 3920 The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
1705 3921 Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started
1706 3922 Cannot enlist in the transaction because the transaction does not exist.
1707 3923 Cannot use transaction marks on database '%.*ls' with bulk-logged operations that have not been backed up. The mark is ignored.
1708 3924 The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction.
1709 3925 Invalid transaction mark name. The 'LSN:' prefix is reserved.
1710 3926 The transaction active in this session has been committed or aborted by another session.
1711 3927 The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction.
1712 3928 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.
1713 3929 No distributed or bound transaction is allowed in single user database.
1714 3930 The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
1715 3931 The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
1716 3932 The save point name "%.*ls" that was provided is too long. The maximum allowed length is %d characters.
1717 3933 Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
1718 3934 The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTION_CONTEXT.
1719 3935 A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x.
1720 3936 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
1721 3937 While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver. Error code: 0x%0x.
1722 3938 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.
1723 3939 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.
1724 3950 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.
1725 3951 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.
1726 3952 Snapshot isolation transaction failed accessing database '%.*ls' because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation.
1727 3953 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.
1728 3954 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.
1729 3955 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.
1730 3956 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.
1731 3957 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.
1732 3958 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.
1733 3959 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.
1734 3960 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.
1735 3961 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.
1736 3962 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.
1737 3963 Transaction failed in database '%.*ls' because distributed transactions are not supported under snapshot isolation.
1738 3964 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.
1739 3965 The PROMOTE TRANSACTION request failed because there is no local transaction active.
1740 3966 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
1741 3967 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.
1742 3968 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.
1743 3969 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.
1744 3970 This operation conflicts with another pending operation on this transaction. The operation failed.
1745 3971 The server failed to resume the transaction. Desc:%I64x.
1746 3972 Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d.
1747 3973 The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed.
1748 3974 The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed.
1749 3975 The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted.
1750 3976 The transaction name has the odd length %d. The batch has been aborted.
1751 3977 The savepoint name cannot be NULL. The batch has been aborted.
1752 3978 Beginning a new transaction after rollback to save point is not allowed.
1753 3979 The TM request is longer than expected. The request is not processed.
1754 3980 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.
1755 3981 The transaction operation cannot be performed because there are pending requests working on this transaction.
1756 3982 New transaction is not allowed to be started while DTC or bound transaction is active.
1757 3983 The operation failed because the session is not single threaded.
1758 3984 Cannot acquire a database lock during a transaction change.
1759 3985 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.
1760 3986 The transaction timestamps ran out. Restart the server.
1761 3987 SNAPSHOT ISOLATION is always enabled in this database.
1762 3988 New transaction is not allowed because there are other threads running in the session.
1763 3989 New request is not allowed to start because it should come with valid transaction descriptor.
1764 3990 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.
1765 3991 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.
1766 3992 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.
1767 3993 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.
1768 3994 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.
1769 3995 Unknown transaction isolation level %d, valid value range is 0 to 5.
1770 3996 Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction.
1771 3997 A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back.
1772 3998 Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.
1773 3999 Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information.
1774 4001 Client sends a sp_reset_connection while there is still pending requests, server is disconnecting.
1775 4002 The incoming tabular data stream (TDS) protocol stream is incorrect. The stream ended unexpectedly.
1776 4004 Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier.
1777 4005 Cannot update columns from more than one underlying table in a single update call.
1778 4006 You cannot delete rows from more than one underlying table in a single delete call.
1779 4007 Cannot update or insert column "%.*ls". It may be an expression.
1780 4008 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.
1781 4009 The incoming tabular data stream (TDS) protocol stream is incorrect. The TDS headers contained errors.
1782 4010 The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors.
1783 4011 The incoming tabular data stream (TDS) protocol stream is incorrect. The MARS TDS header contained errors.
1784 4012 An invalid tabular data stream (TDS) collation was encountered.
1785 4013 The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is missing.
1786 4014 A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %d, output error: %d).
1787 4015 Language requested in login '%.*ls' is not an official name on this SQL Server. Using server-wide default %.*ls instead.
1788 4016 Language requested in 'login %.*ls' is not an official name on this SQL Server. Using user default %.*ls instead.
1789 4017 Neither the language requested in 'login %.*ls' nor user default language %.*ls is an official language name on this SQL Server. Using server-wide default %.*ls instead.
1790 4018 User default language %.*ls is not an official language name on this SQL Server. Using server-wide default %.*ls instead.
1791 4019 Language requested in login '%.*ls' is not an official language name on this SQL Server. Login fails.
1792 4020 Default date order '%.*ls' for language %.*ls is invalid. Using mdy instead.
1793 4021 Resetting the connection results in a different state than the initial login. The login fails.
1794 4022 Bulk load data was expected but not sent. The batch will be terminated.
1795 4027 Mount tape for %hs of database '%ls' on tape drive '%ls'.
1796 4028 End of tape has been reached. Remove tape '%ls' and mount next tape for %hs of database '%ls'.
1797 4030 The medium on device '%ls' expires on %hs and cannot be overwritten.
1798 4035 Processed %I64d pages for database '%ls', file '%ls' on file %d.
1799 4037 The user-specified MEDIANAME "%.*ls" does not match the MEDIANAME "%ls" of the device "%ls".
1800 4038 Cannot find file ID %d on device '%ls'.
1801 4060 Cannot open database "%.*ls" requested by the login. The login failed.
1802 4061 Neither the database "%.*ls" requested by the login nor the user default database could be opened. The master database is being used instead.
1803 4062 Cannot open user default database. Using master database instead.
1804 4063 Cannot open database "%.*ls" that was requested by the login. Using the user default database "%.*ls" instead.
1805 4064 Cannot open user default database. Login failed.
1806 4065 User is trying to use '%.*ls' through ODS, which is not supported any more.
1807 4066 Type IDs larger than 65535 cannot be sent to clients shipped in SQL Server 2000 or earlier.
1808 4067 CLR type serialization failed because an invalid cookie was specified.
1809 4068 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.
1810 4069 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.
1811 4070 More than 255 columns were specified in the COMPUTE clause, and this metadata cannot be sent to a SQL Server version 6.5 client.
1812 4071 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.
1813 4072 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.
1814 4073 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.
1815 4074 Client drivers do not accept result sets that have more than 65,535 columns.
1816 4075 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.
1817 4076 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.
1818 4077 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.
1819 4078 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.
1820 4079 The statement failed due to arithmetic overflow when sending data stream.
1821 4101 Aggregates on the right side of an APPLY cannot reference columns from the left side.
1822 4102 The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM clause.
1823 4103 "%.*ls": Temporary views are not allowed.
1824 4104 The multi-part identifier "%.*ls" could not be bound.
1825 4105 User-defined functions, partition functions, and column references are not allowed in expressions in this context.
1826 4106 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.
1827 4107 Inserting into remote tables or views is not allowed by using the BCP utility or by using BULK INSERT.
1828 4108 Windowed functions can only appear in the SELECT or ORDER BY clauses.
1829 4109 Windowed functions cannot be used in the context of another windowed function or aggregate.
1830 4110 The argument type "%s" is invalid for argument %d of "%s".
1831 4111 The CREATE SCHEMA statement should be followed by a name or authorization keyword.
1832 4112 The ranking function "%.*ls" must have an ORDER BY clause.
1833 4113 "%.*ls" is not a valid windowing function, and cannot be used with the OVER clause.
1834 4114 The function '%.*ls' takes exactly %d argument(s).
1835 4115 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.
1836 4116 The function 'ntile' takes only a positive int or bigint expression as its input.
1837 4117 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.
1838 4118 An invalid expression was specified in the FOR UPDATE clause.
1839 4119 Default values cannot be assigned to property setters of columns with a CLR type.
1840 4120 A user-defined function name cannot be prefixed with a database name in this context.
1841 4121 Cannot find either column "%.*ls" or the user-defined function or aggregate "%.*ls", or the name is ambiguous.
1842 4122 Remote table-valued function calls are not allowed.
1843 4124 The parameters supplied for the batch are not valid.
1844 4126 No full-text indexed columns were found.
1845 4127 At least one of the arguments to COALESCE must be a typed NULL.
1846 4128 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.
1847 4129 The inline function "%.*ls" cannot take correlated parameters or subqueries because it uses a full-text operator.
1848 4130 A duplicate hint was specified for the BULK rowset.
1849 4131 A compile-time literal value is specified more than once for the variable "%.*ls" in one or more OPTIMIZE FOR clauses.
1850 4132 The value specified for the variable "%.*ls" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's type.
1851 4133 Only a scalar expression may be specified as the argument to the RETURN statement.
1852 4134 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.
1853 4135 Synonym '%.*ls' is defined over queue '%.*ls'. Synonyms on queues are not allowed.
1854 4136 The hint '%.*ls' cannot be used with the hint '%.*ls'.
1855 4137 A format file cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option.
1856 4138 Conflicting locking hints are specified for table "%.*ls". This may be caused by a conflicting hint specified for a view.
1857 4139 Cannot process the query because it references the common language runtime (CLR) table-valued function "%.*ls" with a hint through view "%.*ls".
1858 4140 The READCOMMITTEDLOCK lock hint is not allowed on the target table of an INSERT statement.
1859 4141 Nested CLR type updates are not allowed.
1860 4142 Aggregates are not allowed in the RECEIVE list.
1861 4143 The bulk openrowset provider is not a valid target for %.*ls.
1862 4144 The hint '%.*ls' is not allowed when inserting into remote tables.
1863 4145 An expression of non-boolean type specified in a context where a condition is expected, near '%.*ls'.
1864 4146 Statistics can only be created on columns.
1865 4147 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.
1866 4148 XML methods are not allowed in a GROUP BY clause.
1867 4150 Hints are not allowed on recursive common table expression (CTE) references. Consider removing hint from recursive CTE reference '%.*ls'.
1868 4151 The type of the first argument to NULLIF cannot be the NULL constant because the type of the first argument has to be known.
1869 4152 Type "%.*ls" is not a CLR type.
1870 4153 Cannot treat data type "%ls" as data type "%ls".
1871 4154 UNNEST can only take an expression of type multiset.
1872 4155 The SELECT list for the nested INSERT statement can only contain one item.
1873 4156 The target of nested insert, nested update, or nested delete must be of type multiset.
1874 4157 "%.*ls" is not a valid property, field, or method.
1875 4158 The field "%.*ls" is referenced more than once in the set list, either directly or through a property.
1876 4159 Delayed CLR type instances require local base table column as an argument.
1877 4160 Could not find suitable key in table '%.*ls' for use in delayed CLR type fetching.
1878 4161 Only CLR types are allowed in delayed CLR type fetching.
1879 4162 A PROB_MATCH table can only be used inside of a PROB_MATCH query.
1880 4163 A GROUP BY clause is required in a PROB_MATCH query.
1881 4164 A GROUP BY clause in a PROB_MATCH query can only have key columns, and needs to include all the key columns.
1882 4165 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.
1883 4166 Invalid PROB_MATCH subquery.
1884 4167 Multiple PROB_MATCH subqueries can only refer to the same base table.
1885 4168 Invalid PROB_MATCH project item in the PROB_MATCH SELECT list.
1886 4169 Applying TREAT more than once to the same expression is not allowed in a full-text property reference.
1887 4170 The (ANY) specification can only be applied to expressions of type multiset.
1888 4171 Alias was not specified for an aggregate in the PROB_MATCH SELECT list.
1889 4172 Incorrect use of full-text %s.
1890 4173 "%.*s" is not a valid scoring function name.
1891 4174 Delayed CLR type instantiation fetch value query may only reference column of a large object or large value type.
1892 4175 Nested updates cannot be performed on CLR types that are not Format.Structured.
1893 4176 Too many parameters were specified for FULLTEXTTABLE of type "Simple". The maximum number of parameters is %d.
1894 4177 The FROM clause of a PROB_MATCH query must consist of a single derived table.
1895 4184 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.
1896 4185 This action cannot be performed on a system type.
1897 4186 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.
1898 4202 BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable.
1899 4208 The statement %hs is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
1900 4212 Cannot back up the log of the master database. Use BACKUP DATABASE instead.
1901 4214 BACKUP LOG cannot be performed because there is no current database backup.
1902 4215 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.
1903 4217 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.
1904 4218 Bulk-logged operations exist in the database. Perform a BACKUP LOG.
1905 4302 The option "%ls" conflicts with online restore. Remove the conflicting option and reissue the command.
1906 4303 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.
1907 4305 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.
1908 4307 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.
1909 4308 The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online.
1910 4309 The state of file "%ls" prevents restoring individual pages. Only a file restore is currently possible.
1911 4310 RESTORE PAGE is not allowed on file "%ls" because the file is not online.
1912 4311 RESTORE PAGE is not allowed from backups taken with earlier versions of SQL Server.
1913 4312 This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap.
1914 4315 Some files still require more restore steps before the online restore sequence can be completed.
1915 4318 File '%ls' has been rolled forward to LSN %.*ls. This log terminates at LSN %.*ls, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY.
1916 4319 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.
1917 4320 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.
1918 4322 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.
1919 4323 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.
1920 4326 The log in this backup set terminates at LSN %.*ls, which is too early to apply to the database. A more recent log backup that includes LSN %.*ls can be restored.
1921 4327 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.
1922 4328 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.
1923 4329 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.
1924 4330 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.
1925 4331 The database cannot be recovered because the files have been restored to inconsistent points in time.
1926 4332 RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY.
1927 4333 The database cannot be recovered because the log was not restored.
1928 4334 The named mark does not identify a valid LSN.
1929 4335 The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point.
1930 4336 The filegroup "%ls" has been dropped and cannot be restored into the online database.
1931 4337 The file "%ls" has been dropped and cannot be restored into the online database.
1932 4338 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.
1933 4339 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.
1934 4340 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.
1935 4341 This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time.
1936 4342 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.
1937 4343 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.
1938 4344 RESTORE PAGE is not allowed on read-only databases or filegroups.
1939 4345 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.
1940 4346 RESTORE PAGE is not allowed with databases that use the simple recovery model.
1941 4347 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.
1942 4348 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.
1943 4349 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.
1944 4350 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 : pairs with commas separating each pair. For example: PAGE='1:57,2:31'.
1945 4351 Backups taken on earlier versions of SQL Server are not supported by fn_dump_dblog.
1946 4352 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.
1947 4353 Conflicting file relocations have been specified for file '%.*ls'. Only a single WITH MOVE clause should be specified for any logical file name.
1948 4354 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.
1949 4355 The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE FROM DATABASE_SNAPSHOT = .
1950 4356 Restore is complete on database '%ls'. The database is now available.
1951 4357 Restore cannot take '%ls' offline because changes exist that require a log backup. Take a log backup and then retry the RESTORE.
1952 4358 The database can not be brought online because file '%ls' is currently restored to LSN %.*ls but must be restored to LSN %.*ls.
1953 4359 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.
1954 4360 RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
1955 4403 Cannot update the view or function '%.*ls' because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
1956 4405 View or function '%.*ls' is not updatable because the modification affects multiple base tables.
1957 4406 Update or insert of view or function '%.*ls' failed because it contains a derived or constant field.
1958 4408 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.
1959 4413 Could not use view or function '%.*ls' because of binding errors.
1960 4414 Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%d) was exceeded.
1961 4415 View '%.*ls' is not updatable because either it was created WITH CHECK OPTION or it spans a view created WITH CHECK OPTION and the target table is referenced multiple times in the resulting query.
1962 4416 UNION ALL view '%.*ls' is not updatable because the definition contains a disallowed construct.
1963 4417 Derived table '%.*ls' is not updatable because the definition contains a UNION operator.
1964 4418 Derived table '%.*ls' is not updatable because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator.
1965 4420 Derived table '%.*ls' is not updatable because the modification affects multiple base tables.
1966 4421 Derived table '%.*ls' is not updatable because a column of the derived table is derived or constant.
1967 4422 View '%.*ls' has an INSTEAD OF UPDATE trigger and cannot be a target of an UPDATE FROM statement.
1968 4423 View '%.*ls' has an INSTEAD OF DELETE trigger and cannot be a target of a DELETE FROM statement.
1969 4424 Joined tables cannot be specified in a query containing outer join operators. View or function '%.*ls' contains joined tables.
1970 4425 Cannot specify outer join operators in a query containing joined tables. View or function '%.*ls' contains outer join operators.
1971 4426 View '%.*ls' is not updatable because the definition contains a UNION operator.
1972 4427 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.
1973 4429 View or function '%.*ls' contains a self-reference. Views or functions cannot reference themselves directly or indirectly.
1974 4430 Warning: Index hints supplied for view '%.*ls' will be ignored.
1975 4431 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a timestamp column.
1976 4432 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a DEFAULT constraint.
1977 4433 Cannot INSERT into partitioned view '%.*ls' because table '%.*ls' has an IDENTITY constraint.
1978 4434 Partitioned view '%.*ls' is not updatable because table '%.*ls' has an INSTEAD OF trigger.
1979 4435 Partitioned view '%.*ls' is not updatable because a value was not specified for partitioning column '%.*ls'.
1980 4436 UNION ALL view '%.*ls' is not updatable because a partitioning column was not found.
1981 4437 Partitioned view '%.*ls' is not updatable as the target of a bulk operation.
1982 4438 Partitioned view '%.*ls' is not updatable because it does not deliver all columns from its member tables.
1983 4439 Partitioned view '%.*ls' is not updatable because the source query contains references to partition table '%.*ls'.
1984 4440 UNION ALL view '%.*ls' is not updatable because a primary key was not found on table '%.*ls'.
1985 4441 Partitioned view '%.*ls' is not updatable because the table '%.*ls' has an index on a computed column.
1986 4442 UNION ALL view '%.*ls' is not updatable because base table '%.*ls' is used multiple times.
1987 4443 UNION ALL view '%.*ls' is not updatable because column '%.*ls' of base table '%.*ls' is used multiple times.
1988 4444 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not included in the union result.
1989 4445 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not unioned with primary keys of preceding tables.
1990 4446 Cannot update the UNION ALL view "%.*ls" because the definition of column "%.*ls" of view "%.*ls" is used by another view column.
1991 4447 View '%.*ls' is not updatable because the definition contains a set operator.
1992 4448 Cannot INSERT into partitioned view '%.*ls' because values were not supplied for all columns.
1993 4449 Using defaults is not allowed in views that contain a set operator.
1994 4450 Cannot update partitioned view '%.*ls' because the definition of the view column '%.*ls' in table '%.*ls' has an IDENTITY constraint.
1995 4451 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.
1996 4452 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a CASCADE DELETE or CASCADE UPDATE constraint.
1997 4453 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a INSERT, UPDATE or DELETE trigger.
1998 4454 Cannot update the partitioned view "%.*ls" because the partitioning columns of its member tables have mismatched types.
1999 4456 The partitioned view "%.*ls" is not updatable because one or more of the non-partitioning columns of its member tables have mismatched types.
2000 4457 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.
2001 4502 View or function '%.*ls' has more column names specified than columns defined.
2002 4503 Could not create schemabound %S_MSG '%.*ls' because it references an object in another database.
2003 4504 Could not create %S_MSG '%.*ls' because CLR type '%.*ls' does not exist in the target database '%.*ls'.
2004 4505 CREATE VIEW failed because column '%.*ls' in view '%.*ls' exceeds the maximum of %d columns.
2005 4506 Column names in each view or function must be unique. Column name '%.*ls' in view or function '%.*ls' is specified more than once.
2006 4508 Views or functions are not allowed on temporary tables. Table names that begin with '#' denote temporary tables.
2007 4510 Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable.
2008 4511 Create View or Function failed because no column name was specified for column %d.
2009 4512 Cannot schema bind %S_MSG '%.*ls' because name '%.*ls' is invalid for schema binding. Names must be in two-part format and an object cannot reference itself.
2010 4513 Cannot schema bind %S_MSG '%.*ls'. '%.*ls' is not schema bound.
2011 4514 CREATE FUNCTION failed because a column name is not specified for column %d.
2012 4515 CREATE FUNCTION failed because column '%.*ls' in function '%.*ls' exceeds the maximum of %d columns.
2013 4516 Cannot schema bind function '%.*ls' because it contains an EXECUTE statement.
2014 4517 Service queue object cannot be used in schemabinding expressions. '%.*ls' is a service queue.
2015 4519 Cannot %S_MSG %S_MSG '%.*ls' on view '%.*ls' because it is a system generated view that was created for optimization purposes.
2016 4520 Cannot disable index on view '%.*ls' because it is a system generated view that was created for optimization purposes.
2017 4521 Cannot use object '%.*ls' with autodrop object attribute in schemabinding expressions because it is a system generated view that was created for optimization purposes.
2018 4522 Cannot alter view '%.*ls' because it is a system generated view that was created for optimization purposes.
2019 4523 Cannot create trigger on view '%.*ls' because it is a system generated view that was created for optimization purposes.
2020 4602 Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission.
2021 4604 There is no such user or group '%.*ls' or you do not have permission.
2022 4606 Granted or revoked privilege %ls is not compatible with object.
2023 4610 You can only grant or revoke permissions on objects in the current database.
2024 4611 To revoke or deny grantable privileges, specify the CASCADE option.
2025 4613 Grantor does not have GRANT permission.
2026 4615 Invalid column name '%.*ls'.
2027 4616 You cannot perform this operation for the resource database.
2028 4617 Cannot grant, deny or revoke permissions to or from special roles.
2029 4618 You do not have permission to use %.*ls in the AS clause.
2030 4619 CREATE DATABASE permission can only be granted in the master database.
2031 4620 All permissions in a grant/deny/revoke statement should be at the same scope (e.g., server or database)
2032 4621 Permissions at the server scope can only be granted when the current database is master
2033 4622 Permissions at the server scope can only be granted to logins
2034 4623 The all permission has been deprecated and is not available for this class of entity
2035 4624 Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
2036 4625 There is no such server principal %.*s or you do not have permission.
2037 4627 Cannot grant, deny, or revoke the connect database permission to roles and application roles.
2038 4628 The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
2039 4629 Permissions on server scoped catalog views or system stored procedures or extended stored procedures can be granted only when the current database is master.
2040 4701 Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
2041 4707 Could not truncate object '%.*ls' because it or one of its indexes resides on a READONLY filegroup '%.*ls'.
2042 4708 Could not truncate object '%.*ls' because it is not a table.
2043 4709 You are not allowed to truncate the system table '%.*ls'.
2044 4710 Could not truncate object '%.*ls' because it or one of its indexes resides on an offline filegroup '%.*ls'.
2045 4711 Cannot truncate table '%.*ls' because it is published for replication or enabled for Change Data Capture.
2046 4712 Cannot truncate table '%.*ls' because it is being referenced by a FOREIGN KEY constraint.
2047 4801 Insert bulk is not supported over this access protocol.
2048 4802 The SINGLE_LOB, SINGLE_CLOB, and SINGLE_NCLOB options are mutually exclusive with all other options.
2049 4803 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).
2050 4804 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).
2051 4805 The front-end tool you are using does not support bulk load from host. Use the supported tools for this command.
2052 4806 SINGLE_CLOB requires a double-byte character set (DBCS) (char) input file. The file specified is Unicode.
2053 4807 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).
2054 4808 Bulk copy operations cannot trigger bulk load statements.
2055 4809 SINGLE_NCLOB requires a UNICODE (widechar) input file. The file specified is not Unicode.
2056 4810 Expected the TEXT token in data stream for bulk copy of text or image data.
2057 4811 Expected the column offset in data stream for bulk copy of text or image data.
2058 4812 Expected the row offset in data stream for bulk copy of text or image data.
2059 4813 Expected the text length in data stream for bulk copy of text, ntext, or image data.
2060 4814 Bulk copy into a partitioned table is not supported for down-level clients.
2061 4815 Received an invalid column length from the bcp client for colid %d.
2062 4816 Invalid column type from bcp client for colid %d.
2063 4817 Could not bulk load. The sorted column '%.*ls' is not valid. The ORDER hint is ignored.
2064 4818 Could not bulk load. The sorted column '%.*ls' was specified more than once. The ORDER hint is ignored.
2065 4819 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.
2066 4820 Cannot bulk load. Unknown version of format file "%s".
2067 4821 Cannot bulk load. Error reading the number of columns from the format file "%s".
2068 4822 Cannot bulk load. Invalid number of columns in the format file "%s".
2069 4823 Cannot bulk load. Invalid column number in the format file "%s".
2070 4824 Cannot bulk load. Invalid data type for column number %d in the format file "%s".
2071 4825 Cannot bulk load. Invalid prefix for column number %d in the format file "%s".
2072 4826 Cannot bulk load. Invalid column length for column number %d in the format file "%s".
2073 4827 Cannot bulk load. Invalid column terminator for column number %d in the format file "%s".
2074 4828 Cannot bulk load. Invalid destination table column number for source column %d in the format file "%s".
2075 4829 Cannot bulk load. Error reading the destination table column name for source column %d in the format file "%s".
2076 4830 Bulk load: DataFileType was incorrectly specified as char. DataFileType will be assumed to be widechar because the data file has a Unicode signature.
2077 4831 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.
2078 4832 Bulk load: An unexpected end of file was encountered in the data file.
2079 4833 Bulk load: Version mismatch between the provider dynamic link library and the server executable.
2080 4834 You do not have permission to use the bulk load statement.
2081 4835 Bulk copying into a table with computed columns is not supported for downlevel clients.
2082 4836 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.
2083 4837 Cannot bulk copy into a table "%.*s" that is enabled for immediate-updating subscriptions.
2084 4838 The bulk data source does not support the SQLNUMERIC or SQLDECIMAL data types.
2085 4839 Cannot perform the bulk load. Invalid collation name for source column %d in the format file "%s".
2086 4840 The bulk data source provider string has an invalid %ls property value %ls.
2087 4841 The data source name is not a simple object name.
2088 4842 The required FormatFile property is missing from the provider string of the server.
2089 4843 The bulk data source provider string has a syntax error ('%lc') near character position %d.
2090 4844 The bulk data source provider string has an unsupported property name (%ls).
2091 4845 The bulk data source provider string has a syntax error near character position %d. Expected '%lc', but found '%lc'.
2092 4846 The bulk data provider failed to allocate memory.
2093 4847 Bulk copying into a table with bigint columns is not supported for versions earlier than SQL Server 2000.
2094 4848 Bulk copying into a table with sql_variant columns is not supported for versions earlier than SQL Server 2000.
2095 4855 Line %d in format file "%ls": unexpected element "%ls".
2096 4856 Line %d in format file "%ls": unexpected info item.
2097 4857 Line %d in format file "%ls": Attribute "%ls" could not be specified for this type.
2098 4858 Line %d in format file "%ls": bad value %ls for attribute "%ls".
2099 4859 Line %d in format file "%ls": required attribute "%ls" is missing.
2100 4860 Cannot bulk load. The file "%ls" does not exist.
2101 4861 Cannot bulk load because the file "%ls" could not be opened. Operating system error code %ls.
2102 4862 Cannot bulk load because the file "%ls" could not be read. Operating system error code %ls.
2103 4863 Bulk load data conversion error (truncation) for row %d, column %d (%ls).
2104 4864 Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls).
2105 4865 Cannot bulk load because the maximum number of errors (%d) was exceeded.
2106 4866 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.
2107 4867 Bulk load data conversion error (overflow) for row %d, column %d (%ls).
2108 4868 The bulk load failed. The codepage "%d" is not installed. Install the codepage and run the command again.
2109 4869 The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL.
2110 4870 Cannot bulk load because of an error writing file "%ls". Operating system error code %ls.
2111 4871 Bulk load error while attempting to log errors.
2112 4872 Line %d in format file "%ls": duplicate element id "%ls".
2113 4873 Line %d in format file "%ls": referencing non-existing element id "%ls".
2114 4874 Line %d in format file "%ls": duplicate element id reference "%ls".
2115 4875 Invalid column attribute from bcp client for colid %d.
2116 4876 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.
2117 4877 Error parsing DTS stream when reading row %d, column %d.
2118 4880 Cannot bulk load. When you use the FIRSTROW and LASTROW parameters, the value for FIRSTROW cannot be greater than the value for LASTROW.
2119 4881 Note: Bulk Insert through a view may result in base table default values being ignored for NULL columns in the data file.
2120 4882 Cannot bulk load. A prefix length, field length, or terminator is required for the source column %d in the format file "%s".
2121 4883 The XML reader returned 0x%08X for the info item starting near line %d column %d in format file "%ls".
2122 4884 Unknown error near info item starting near line %d column %d in format file "%ls".
2123 4885 Cannot open file "%ls". A Windows NT Integrated Security login is required.
2124 4886 Cannot open the file "%ls". Operating system error: %ls
2125 4887 Cannot open the file "%ls". Only disk files are supported.
2126 4888 Cannot open the file "%ls". The bulkadmin role membership is required.
2127 4889 Cannot open the file "%ls". A unicode byte-order mark is missing.
2128 4890 Insert bulk is not supported in showplan mode.
2129 4891 Insert bulk failed due to a schema change of the target table.
2130 4892 Bulk insert failed due to a schema change of the target table.
2131 4893 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.
2132 4894 COLMETADATA must be present when using bcp.
2133 4895 Unicode data is odd byte size for column %d. Should be even byte size.
2134 4896 Invalid column value from bcp client for colid %d.
2135 4897 Received an invalid length for chunked LOB data for colid %d.
2136 4900 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.
2137 4901 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.
2138 4902 Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
2139 4903 Warning: The specified partition %d for the table '%.*ls' was ignored in ALTER TABLE SWITCH statement because the table is not partitioned.
2140 4904 ALTER TABLE SWITCH statement failed. The specified partition %d of target table '%.*ls' must be empty.
2141 4905 ALTER TABLE SWITCH statement failed. The target table '%.*ls' must be empty.
2142 4906 '%ls' statement failed. The %S_MSG '%.*ls' is %S_MSG partitioned while index '%.*ls' is %S_MSG partitioned.
2143 4907 '%ls' statement failed. The %S_MSG '%.*ls' has %d partitions while index '%.*ls' has %d partitions.
2144 4908 '%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'.
2145 4909 Cannot alter '%.*ls' because it is not a table.
2146 4911 Cannot specify a partitioned table without partition number in ALTER TABLE SWITCH statement. The table '%.*ls' is partitioned.
2147 4912 '%ls' statement failed. The columns set used to partition the %S_MSG '%.*ls' is different from the column set used to partition index '%.*ls'.
2148 4913 ALTER TABLE SWITCH statement failed. The table '%.*ls' has clustered index '%.*ls' while the table '%.*ls' does not have clustered index.
2149 4914 The ALTER TABLE SWITCH statement failed. The table "%.*ls" has a disabled clustered index.
2150 4915 '%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'.
2151 4916 Could not enable or disable the constraint. See previous errors.
2152 4917 Constraint '%.*ls' does not exist.
2153 4918 ALTER TABLE SWITCH statement failed because the table '%.*ls' has fulltext index on it.
2154 4919 PERSISTED attribute cannot be altered on column '%.*ls' because this column is not computed.
2155 4920 ALTER TABLE failed because trigger '%.*ls' on table '%.*ls' does not exist.
2156 4921 ALTER TABLE failed because trigger '%.*ls' does not belong to table '%.*ls'.
2157 4922 %ls %.*ls failed because one or more objects access this column.
2158 4923 ALTER TABLE DROP COLUMN failed because '%.*ls' is the only data column in table '%.*ls'. A table must have at least one data column.
2159 4924 %ls failed because column '%.*ls' does not exist in table '%.*ls'.
2160 4925 ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%.*ls' with ROWGUIDCOL property.
2161 4926 ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%.*ls' with ROWGUIDCOL property.
2162 4927 Cannot alter column '%.*ls' to be data type %.*ls.
2163 4928 Cannot alter column '%.*ls' because it is '%ls'.
2164 4929 Cannot alter the %S_MSG '%.*ls' because it is being published for replication.
2165 4933 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column depends on a non-schemabound object.
2166 4934 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column does user or system data access.
2167 4935 ALTER TABLE ADD COLUMN cannot specify a FILESTREAM filegroup that differs from the existing one.
2168 4936 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column is non-deterministic.
2169 4938 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'.
2170 4939 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' is in filegroup '%.*ls'.
2171 4940 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegroup '%.*ls' and %S_MSG '%.*ls' is in filegroup '%.*ls'.
2172 4941 ALTER TABLE SWITCH statement failed because the table '%.*ls' is marked for merge replication.
2173 4942 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'.
2174 4943 ALTER TABLE SWITCH statement failed because table '%.*ls' has %d columns and table '%.*ls' has %d columns.
2175 4944 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'.
2176 4945 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'.
2177 4946 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same persistent attribute in tables '%.*ls' and '%.*ls'.
2178 4947 ALTER TABLE SWITCH statement failed. There is no identical index in source table '%.*ls' for the index '%.*ls' in target table '%.*ls' .
2179 4948 ALTER TABLE SWITCH statement failed. The source table '%.*ls' is in database '%.*ls' while the target table '%.*ls' is in database '%.*ls'.
2180 4949 ALTER TABLE SWITCH statement failed because the object '%.*ls' is not a user defined table.
2181 4950 ALTER TABLE SWITCH statement failed because partition number %d does not exist in table '%.*ls'.
2182 4951 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same FILESTREAM storage attribute in tables '%.*ls' and '%.*ls'.
2183 4952 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same ANSI trimming semantics in tables '%.*ls' and '%.*ls'.
2184 4953 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'.
2185 4954 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'.
2186 4955 ALTER TABLE SWITCH statement failed. The source table '%.*ls' and target table '%.*ls' are same.
2187 4956 ALTER TABLE SWITCH statement failed because the table '%.*ls' is not RANGE partitioned.
2188 4957 '%ls' statement failed because the expression identifying partition number for the %S_MSG '%.*ls' is not of integer type.
2189 4958 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same ROWGUIDCOL property in tables '%.*ls' and '%.*ls'.
2190 4959 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'.
2191 4960 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.
2192 4961 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%.*ls' is nullable and it is not nullable in '%.*ls'.
2193 4962 ALTER TABLE SWITCH statement failed. Partition %d in table '%.*ls' is not a range partition.
2194 4963 ALTER TABLE SWITCH statement failed. Partition %d is not valid for table '%.*ls'.
2195 4964 ALTER TABLE SWITCH statement failed. Table '%.*ls' has RULE constraint '%.*ls'. SWITCH is not allowed on tables with RULE constraints.
2196 4965 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%.*ls' is computed column but the same column in '%.*ls' is not computed.
2197 4966 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'.
2198 4967 ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table '%.*ls' contains primary key for constraint '%.*ls'.
2199 4968 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has foreign key for constraint '%.*ls' but source table '%.*ls' does not have corresponding key.
2200 4969 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.
2201 4970 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.
2202 4971 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.
2203 4972 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'.
2204 4973 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'.
2205 4974 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.
2206 4975 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.
2207 4976 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.
2208 4977 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.
2209 4978 ALTER TABLE SWITCH statement failed. The partition %d in table '%.*ls' resides in a read-only filegroup '%.*ls'.
2210 4979 ALTER TABLE SWITCH statement failed. The table '%.*ls' resides in a readonly filegroup '%.*ls'.
2211 4980 ALTER TABLE SWITCH statement failed. The lobdata of partition %d in table '%.*ls' resides in a readonly filegroup '%.*ls'.
2212 4981 ALTER TABLE SWITCH statement failed. The lobdata of table '%.*ls' resides in a readonly filegroup '%.*ls'.
2213 4982 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'.
2214 4983 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.
2215 4984 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.
2216 4985 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same nullability attribute in tables '%.*ls' and '%.*ls'.
2217 4986 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same CLR type in tables '%.*ls' and '%.*ls'.
2218 4987 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same XML Schema Collection in tables '%.*ls' and '%.*ls'.
2219 4988 Cannot persist computed column '%.*ls'. Underlying object '%.*ls' has a different owner than table '%.*ls'.
2220 4989 Cannot drop the ROWGUIDCOL property for column '%.*ls' in table '%.*ls' because the column is not the designated ROWGUIDCOL for the table.
2221 4990 Cannot alter column '%.*ls' in table '%.*ls' to add or remove the FILESTREAM column attribute.
2222 4991 Cannot alter NOT FOR REPLICATION attribute on column '%.*ls' in table '%.*ls' because this column is not an identity column.
2223 4992 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.
2224 4993 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'.
2225 4994 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column type, '%.*ls', is a non-byte-ordered CLR type.
2226 4995 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.
2227 4996 Change tracking is already enabled for table '%.*ls'.
2228 4997 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.
2229 4998 Change tracking is not enabled on table '%.*ls'.
2230 4999 Cannot enable change tracking on table '%.*ls'. Change tracking does not support a primary key of type timestamp on a table.
2231 5001 User must be in the master database.
2232 5002 Database '%.*ls' does not exist. Verify the name in sys.databases and try the operation again.
2233 5003 Database mirroring cannot be enabled while the database has offline files.
2234 5004 To use ALTER DATABASE, the database must be in a writable state in which a checkpoint can be executed.
2235 5006 Could not get exclusive use of %S_MSG '%.*ls' to perform the requested operation.
2236 5008 This ALTER DATABASE statement is not supported. Correct the syntax and execute the statement again.
2237 5009 One or more files listed in the statement could not be found or could not be initialized.
2238 5010 Log file name cannot be generated from a raw device. The log file name and path must be specified.
2239 5011 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.
2240 5012 The name of the primary filegroup cannot be changed.
2241 5013 The master and model databases cannot have files added to them. ALTER DATABASE was aborted.
2242 5014 The %S_MSG '%.*ls' does not exist in database '%.*ls'.
2243 5015 ALTER DATABASE failed. The total size specified must be 1 MB or greater.
2244 5016 Cannot change the name of the system database %.*ls.
2245 5018 The file "%.*ls" has been modified in the system catalog. The new path will be used the next time the database is started.
2246 5019 Cannot find entry in sys.master_files for file '%.*ls'.
2247 5020 The primary data or log file cannot be removed from a database.
2248 5021 The %S_MSG name '%.*ls' has been set.
2249 5022 Log file '%ls' for this database is already active.
2250 5023 The database must be suspect or in emergency mode to rebuild the log.
2251 5024 No entry found for the primary log file in sysfiles1. Could not rebuild the log.
2252 5025 The file '%ls' already exists. It should be renamed or deleted so that a new log file can be created.
2253 5027 System databases master, model, and tempdb cannot have their logs rebuilt.
2254 5028 The system could not activate enough of the database to rebuild the log.
2255 5029 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.
2256 5030 The database could not be exclusively locked to perform the operation.
2257 5031 Cannot remove the file '%.*ls' because it is the only file in the DEFAULT filegroup.
2258 5032 The file cannot be shrunk below page %ud until the log is backed up because it contains bulk logged pages.
2259 5033 The maximum of %ld files per database has been exceeded.
2260 5034 The file %ls is currently being autogrown or modified by another process. Try the operation again later.
2261 5035 Filegroup '%.*ls' already exists in this database. Specify a different name or remove the conflicting filegroup if it is empty.
2262 5036 MODIFY FILE failed. Specify logical name.
2263 5038 MODIFY FILE failed for file "%.*ls". At least one property per file must be specified.
2264 5039 MODIFY FILE failed. Specified size is less than or equal to current size.
2265 5040 MODIFY FILE failed. Size is greater than MAXSIZE.
2266 5041 MODIFY FILE failed. File '%.*ls' does not exist.
2267 5042 The %S_MSG '%.*ls' cannot be removed because it is not empty.
2268 5043 The %S_MSG '%.*ls' cannot be found in %ls.
2269 5044 The %S_MSG '%.*ls' has been removed.
2270 5045 The %S_MSG already has the '%ls' property set.
2271 5046 The %S_MSG property '%ls' has been set.
2272 5047 Cannot change the READONLY property of the PRIMARY filegroup.
2273 5048 Cannot add, remove, or modify files in filegroup '%.*ls'. The filegroup is read-only.
2274 5050 Cannot change the properties of empty filegroup '%.*ls'. The filegroup must contain at least one file.
2275 5051 Cannot have a filegroup with the name 'DEFAULT'.
2276 5052 %ls is not permitted while a database is in the %ls state.
2277 5054 Could not cleanup worktable IAM chains to allow shrink or remove file operation. Please try again when tempdb is idle.
2278 5055 Cannot add, remove, or modify file '%.*ls'. The file is read-only.
2279 5056 Cannot add, remove, or modify a file in filegroup '%.*ls' because the filegroup is not online.
2280 5057 Cannot add, remove, or modify file '%.*ls' because it is offline.
2281 5058 Option '%.*ls' cannot be set in database '%.*ls'.
2282 5059 Database '%.*ls' is in transition. Try the ALTER DATABASE statement later.
2283 5060 Nonqualified transactions are being rolled back. Estimated rollback completion: %d%%.
2284 5061 ALTER DATABASE failed because a lock could not be placed on database '%.*ls'. Try again later.
2285 5062 The option "%.*ls" conflicts with another requested option. The options cannot both be requested at the same time.
2286 5063 Database '%.*ls' is in warm standby. A warm-standby database is read-only.
2287 5064 Changes to the state or options of database '%.*ls' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it.
2288 5065 The file "%ls" is currently being scanned or used by a background or user process. Try the operation again later.
2289 5066 Database options single user and dbo use only cannot be set at the same time.
2290 5067 The database option TORN_PAGE_DETECTION is incompatible with the PAGE_CHECKSUM option.
2291 5068 Failed to restart the current database. The current database is switched to master.
2292 5069 ALTER DATABASE statement failed.
2293 5070 Database state cannot be changed while other users are using the database '%.*ls'
2294 5071 Rebuild log can only specify one file.
2295 5072 ALTER DATABASE failed. The default collation of database '%.*ls' cannot be set to %.*ls.
2296 5073 Cannot alter collation for database '%ls' because it is READONLY, OFFLINE, or marked SUSPECT.
2297 5074 The %S_MSG '%.*ls' is dependent on %S_MSG '%.*ls'.
2298 5075 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.
2299 5076 Warning: Changing default collation for database '%.*ls', which is used in replication. All replication databases should have the same default collation.
2300 5077 Cannot change the state of non-data files or files in the primary filegroup.
2301 5078 Cannot alter database options for "%ls" because it is READONLY, OFFLINE, or marked SUSPECT.
2302 5079 Database "%.*ls" is %S_MSG for vardecimal storage format.
2303 5080 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.
2304 5081 The value for change tracking option '%ls' is not valid. The value must be a positive number.
2305 5082 Cannot change the versioning state on database "%.*ls" together with another database state.
2306 5083 The termination option is not supported when making versioning state changes.
2307 5084 Setting database option %ls to %ls for database %.*ls.
2308 5085 Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling database for versioning.
2309 5086 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.
2310 5087 The file content type mismatches with the content type of the filegroup.
2311 5088 Change tracking is already enabled for database '%.*ls'.
2312 5089 Change tracking is disabled for database '%.*ls'. Change tracking must be enabled on a database to modify change tracking settings.
2313 5090 Database '%.*ls' is a system database. Change tracking settings cannot be modified for system databases.
2314 5091 ALTER DATABASE change tracking option '%ls' was specified more than once. Each option can be specified only once.
2315 5092 The value for change tracking option '%ls' is not valid. The value must be between %d and %d minutes.
2316 5093 The operation cannot be performed on a database snapshot.
2317 5094 The operation cannot be performed on a database with database snapshots or active DBCC replicas.
2318 5095 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.
2319 5096 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.
2320 5097 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.
2321 5098 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.
2322 5102 Attempted to open a filegroup for the invalid ID %d in database "%.*ls".
2323 5103 MAXSIZE cannot be less than SIZE for file '%ls'.
2324 5104 File '%.*ls' already used.
2325 5105 A file activation error occurred. The physical file name '%.*ls' may be incorrect. Diagnose and correct additional errors, and retry the operation.
2326 5108 Log file '%.*ls' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
2327 5110 The file "%.*ls" is on a network path that is not supported for database files.
2328 5111 File activation failure. The physical file name "%.*ls" may be incorrect.
2329 5112 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.
2330 5113 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.
2331 5114 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.
2332 5115 Only SQL Server database files can be specified for database snapshots. '%.*ls' is not a SQL Server database file.
2333 5118 The file "%ls" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2334 5119 Cannot make the file "%.*ls" a sparse file. Make sure the file system supports sparse files.
2335 5120 Unable to open the physical file "%.*ls". Operating system error %d: "%ls".
2336 5121 The path specified by "%.*ls" is not in a valid directory.
2337 5123 CREATE FILE encountered operating system error %ls while attempting to open or create the physical file '%.*ls'.
2338 5124 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.
2339 5125 File '%ls' appears to have been truncated by the operating system. Expected size is %I64d KB but actual size is %I64d KB.
2340 5127 All files must be specified for database snapshot creation. Missing the file "%ls".
2341 5128 Write to sparse file '%ls' failed due to lack of disk space.
2342 5129 The log cannot be rebuilt when the primary file is read-only.
2343 5130 The log cannot be rebuilt when database mirroring is enabled.
2344 5131 The log was not rebuilt because there is more than one log file.
2345 5132 The path specified by '%.*ls' cannot be used for FILESTREAM files because it is a raw device.
2346 5133 Directory lookup for the file "%ls" failed with the operating system error %ls.
2347 5134 The path that is specified by '%.*ls' cannot be used for FILESTREAM files because it is not on a supported file system.
2348 5135 The path '%.*ls' cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online.
2349 5136 The path specified by '%.*ls' cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container.
2350 5144 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.
2351 5145 Autogrow of file '%.*ls' in database '%.*ls' took %d milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
2352 5149 MODIFY FILE encountered operating system error %ls while attempting to expand the physical file '%ls'.
2353 5150 The size of a single log file must not be greater than 2 TB.
2354 5159 Operating system error %.*ls on file "%.*ls" during %ls.
2355 5161 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.
2356 5169 FILEGROWTH cannot be greater than MAXSIZE for file '%.*ls'.
2357 5170 Cannot create file '%ls' because it already exists. Change the file path or the file name, and retry the operation.
2358 5171 %.*ls is not a primary database file.
2359 5172 The header for file '%ls' is not a valid database file header. The %ls property is incorrect.
2360 5173 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.
2361 5174 Each file size must be greater than or equal to 512 KB.
2362 5175 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.
2363 5176 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).
2364 5177 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.
2365 5178 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.
2366 5179 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.
2367 5180 Could not open File Control Bank (FCB) for invalid file ID %d in database '%.*ls'. Verify the file location. Execute DBCC CHECKDB.
2368 5181 Could not restart database "%.*ls". Reverting to the previous status.
2369 5182 New log file '%.*ls' was created.
2370 5183 Cannot create the file "%ls". Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite an existing file.
2371 5184 Cannot use file '%.*ls' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. 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.
2372 5185 Cannot find the matching log file for FILESTRAM file '%.*ls'.
2373 5186 Encountered an error (NT status code 0x%x) while attempting to start the Transactional File System Resource Manager '%.*ls'.
2374 5188 Encountered error (NT status code 0x%x) while attempting to perform redo for transactional file system resource manager '%.*ls'.
2375 5189 Encountered error (NT status code 0x%x) while attempting to perform undo for transactional file system resource manager '%.*ls'.
2376 5190 Encountered error (NT status code 0x%x) while attempting to checkpoint transactional file system resource manager '%.*ls'.
2377 5194 The size for FILESTREAM log file '%.*ls' must be greater than or equal to 1 MB.
2378 5195 The Cluster Service function call '%s' failed with error code '%s' while verifying the file path. Verify that your failover cluster is configured properly.
2379 5196 The file "%ls" has been uncompressed.
2380 5197 Encountered an error (%ls) while attempting to uncompress the file "%ls".
2381 5198 The path specified by "%.*ls" is a UNC path. UNC path is not supported in failover clustered environment.
2382 5199 The path specified by "%.*ls" is a raw device. Raw device path is not supported in failover clustered environment.
2383 5201 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because the file does not have enough free space to reclaim.
2384 5202 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.
2385 5203 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.
2386 5204 Could not find allocation unit ID %I64d. Check sys.allocation_units.
2387 5205 %.*ls: Moving page %d:%d failed.
2388 5206 %.*ls: Page %d:%d could not be moved because it could not be read.
2389 5207 %.*ls: Page %d:%d could not be moved because it is a work table page.
2390 5208 %.*ls: Page %d:%d could not be moved because it is a work file page.
2391 5209 %.*ls: Page %d:%d could not be moved because it is a dedicated allocation page.
2392 5210 %.*ls: Page %d:%d could not be moved because it is an invalid page type.
2393 5211 %.*ls: Page %d:%d could not be moved because it was deallocated during shrink.
2394 5212 %.*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.
2395 5213 %.*ls: Page %d:%d could not be moved because its ownership was changed during shrink.
2396 5214 %.*ls: Page %d:%d could not be moved because its page type was changed during shrink.
2397 5215 %.*ls: Page %d:%d could not be moved because the partition to which it belonged was dropped.
2398 5216 %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was dropped.
2399 5217 %.*ls: Page %d:%d could not be moved because it is an empty non-leaf level index page.
2400 5218 %.*ls: Heap page %d:%d could not be moved because the table name could not be found.
2401 5219 %.*ls: Heap page %d:%d could not be moved.
2402 5220 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved.
2403 5221 %.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allocation unit could not be moved.
2404 5222 %.*ls: Page %d:%d from a dropped allocation unit could not be deallocated.
2405 5223 %.*ls: Empty page %d:%d could not be deallocated.
2406 5224 %.*ls: Empty large object page %d:%d could not be deallocated.
2407 5225 %.*ls: Not all ghost records on the large object page %d:%d could be removed.
2408 5226 %.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallocated.
2409 5227 %.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallocated.
2410 5228 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.)
2411 5229 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.
2412 5230 The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB.
2413 5231 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.
2414 5232 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.
2415 5233 Table error: alloc unit ID %I64d, page %S_PGID. The test (%hs) failed. The values are %ld and %ld.
2416 5234 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because trying to adjust the space allocation for the file was failed.
2417 5235 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds.
2418 5236 Unable to process object '%ls' because it is a four-part name, which is not supported by any DBCC command.
2419 5237 DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to an internal query error.
2420 5238 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.
2421 5239 Unable to process object ID %ld (object '%.*ls') because this DBCC command does not support objects of this type.
2422 5240 File ID %d of database ID %d cannot be shrunk as it is either being shrunk by another process or is empty.
2423 5241 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).
2424 5242 An inconsistency was detected during an internal operation in database '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support.
2425 5243 An inconsistency was detected during an internal operation. Please contact technical support.
2426 5244 Repair statement not processed. One or more files in the database are read-only and must be made writeable in order to run repair.
2427 5245 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.
2428 5246 Repair operations cannot be performed on the MSSQLSYSTEMRESOURCE database. Consult Books Online topic "Resource Database" for more information.
2429 5247 Repair: insert a secondary index row based on its base table row.
2430 5248 Repair: Successfully %ls row in index "%ls" in database "%ls".
2431 5249 %.*ls: Page %d:%d could not be moved because shrink could not lock the page.
2432 5250 Database error: %ls page %S_PGID for database '%.*ls' (database ID %d) is invalid. This error cannot be repaired. You must restore from backup.
2433 5251 %.*ls: Heap page %d:%d could not be moved because maintaining NC indexes associated with the heap failed.
2434 5252 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.
2435 5253 The check statement was aborted. DBCC CHECKALLOC cannot be run on TEMPDB.
2436 5254 %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was building the heap by another process.
2437 5255 %.*ls: Page %d:%d could not be moved because it is a sort page.
2438 5256 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.
2439 5257 %.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation.
2440 5258 %.*ls: Heap page %d:%d could not be moved because building computed column expression failed.
2441 5259 %.*ls: Heap page %d:%d could not be moved because populating computed column expression failed.
2442 5260 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.
2443 5261 %.*ls: Page %d:%d could not be moved because it has not been formatted.
2444 5262 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.
2445 5263 Found incorrect count(s) for table '%.*ls', index '%.*ls', partition %ld:
2446 5264 DATA pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
2447 5265 USED pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
2448 5266 RSVD pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.
2449 5267 ROWS count: From system table - %I64d rows; Actual - %I64d rows.
2450 5268 DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required.
2451 5269 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.
2452 5270 %.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table.
2453 5271 DBCC %ls could not output results for this command due to an internal failure. Review other errors for details.
2454 5272 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively.
2455 5273 %.*ls: Page %d:%d could not be moved because it belonged to an index/heap that was/is in build online.
2456 5274 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.
2457 5275 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.
2458 5276 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.
2459 5277 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.
2460 5278 DBCC encountered a page with an LSN greater than the current end of log LSN %S_LSN for its internal database snapshot. Could not read page %S_PGID, database '%.*ls' (database ID %d), LSN = %S_LSN, type = %ld, isInSparseFile = %d. Please re-run this DBCC command."
2461 5301 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.
2462 5302 Mutator '%.*ls' on '%.*ls' cannot be called on a null value.
2463 5303 The result of applying mutator '%.*ls' on CLR type '%.*ls' cannot be a null value.
2464 5304 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.
2465 5305 The rowdump and lockres columns are only valid on tables and indexed views on which the NOEXPAND hint is specified.
2466 5306 Cursor parameters are not allowed for functions. Variable '%.*ls' is of type cursor.
2467 5307 Invalid parameter specified for sp_cursoropen.
2468 5308 Windowed functions do not support integer indices as ORDER BY clause expressions.
2469 5309 Windowed functions do not support constants as ORDER BY clause expressions.
2470 5310 Aggregates are not allowed in the VALUES list of an INSERT statement.
2471 5311 Invalid quote character '%lc'. A remote server or user command used an invalid quote character.
2472 5312 The input to the function 'ntile' cannot be bound.
2473 5313 Synonym '%.*ls' refers to an invalid object.
2474 5315 The target of a MERGE statement cannot be a remote table, a remote view, or a view over remote tables.
2475 5316 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.
2476 5317 The target of a MERGE statement cannot be a partitioned view.
2477 5318 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.
2478 5319 Aggregates are not allowed in a WHEN clause of a MERGE statement.
2479 5321 The '%ls' function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
2480 5322 An aggregate function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
2481 5323 Subqueries are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
2482 5324 In a MERGE statement, a '%S_MSG' clause with a search condition cannot appear after a '%S_MSG' clause with no search condition.
2483 5325 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.
2484 5326 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.
2485 5327 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.
2486 5328 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.
2487 5329 Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
2488 5330 Full-text predicates cannot appear in the OUTPUT clause.
2489 5331 Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
2490 5332 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.
2491 5333 The identifier '%.*ls' cannot be bound. Only source columns are allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
2492 5334 The identifier '%.*ls' cannot be bound. Only target columns are allowed in the 'WHEN NOT MATCHED BY SOURCE' clause of a MERGE statement.
2493 5501 The FILESTREAM filegroup was dropped before the table can be created.
2494 5502 The FILESTREAM container is inaccessible.
2495 5503 Unable to find entry in sys.database_files for FILESTREAM file '%.*ls'.
2496 5504 'PRIMARY' can only be specified for FILESTREAM log filegroup in a 'CONTAINS' clause.
2497 5505 A table with FILESTREAM column(s) must have a non-NULL unique ROWGUID column.
2498 5506 FILESTREAM data or log file cannot be named 'DEFAULT'.
2499 5507 DEFAULT cannot be specified for FILESTREAM log filegroup '%.*ls'.
2500 5508 FILESTREAM can only be declared for VARBINARY columns.
2501 5509 The properties SIZE, MAXSIZE, or FILEGROWTH cannot be specified for the FILESTREAM data file '%.*ls'.
2502 5510 LOG ON cannot be used for non-FILESTREAM file group '%.*ls'.
2503 5511 FILESTREAM's file system log record '%.*ls' under log folder '%.*ls' is corrupted.
2504 5512 Error 0x%x (%ls) was encountered while directory '%.*ls' was being truncated.
2505 5513 The name that is specified for the associated log filegroup for FILESTREAM filegroup '%.*ls' is not valid.
2506 5514 Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%.*ls' is not started.
2507 5515 Cannot open the container directory '%.*ls' of the FILESTREAM file. The operating system has returned the Windows status code 0x%x.
2508 5516 The FILESTREAM log filegroup '%.*ls' cannot be referred to by more than one FILESTREAM data filegroup.
2509 5517 Too few or too many files specified for FILESTREAM(LOG) filegroup '%.*ls'.
2510 5518 FILESTREAM path '%.*ls' is too long.
2511 5519 A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups.
2512 5520 FILESTREAM file '%.*ls' cannot be added because its destination filegroup cannot have more than one file.
2513 5521 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'.
2514 5522 FILESTREAM data file cannot be removed because its log file has not been backed up.
2515 5523 FILESTREAM data file group cannot be added to refer to an empty FILESTREAM log file group.
2516 5524 Default FILESTREAM data filegroup cannot be removed unless it's the last FILESTREAM data filegroup left.
2517 5525 The READ_ONLY, READ_WRITE, and ONLINE/OFFLINE properties cannot be modified on a FILESTREAM log filegroup.
2518 5526 The FILESTREAM log file '%.*ls' cannot be removed because it is being referenced by a FILESTREAM data filegroup.
2519 5527 The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist.
2520 5528 A database can have at most one primary FILESTREAM log filegroup and log file.
2521 5531 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'.
2522 5532 SQL Server cannot obtain the Kernel Transaction Manager's transaction context to perform file system operation.
2523 5533 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.
2524 5534 SQL log record at LSN '%d:%d:%d' for database '%.*ls' is corrupted. Database cannot recover.
2525 5535 FILESTREAM data container '%.*ls' is corrupted. Database cannot recover.
2526 5536 FILESTREAM deleted folder '%.*ls' is corrupted. Database cannot recover.
2527 5537 Function %ls is only valid on columns with the FILESTREAM attribute.
2528 5538 Partial updates are not supported on columns that have a FILESTREAM as a source.
2529 5539 The ROWGUIDCOL column associated with the FILESTREAM being used is not visible where method %ls is called.
2530 5540 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.
2531 5541 An open mode must be used when a FILESTREAM column is opened as a file.
2532 5542 The FILESTREAM filegroup '%.*ls' has no files assigned to it. FILESTREAM data cannot be populated on this filegroup until a file is added.
2533 5552 FILESTREAM file named with GUID '%.*ls' that belongs to FILESTREAM data file ID 0x%x does not exist or cannot be opened.
2534 5553 SQL Server internal error. FILESTREAM manager cannot continue with current command.
2535 5554 The total number of versions for a single file has reached the maximum limit set by the file system.
2536 5555 The operation has failed because the FILESTREAM data cannot be renamed.
2537 5570 FILESTREAM Failed to find the garbage collection table.
2538 5571 Internal FILESTREAM error: failed to access the garbage collection table.
2539 5572 Internal FILESTREAM error: failed to perform a filesystem operation because of a potential corruption.
2540 5573 Internal FILESTREAM error: failed to access the tombstones table with HRESULT: 0x%x.
2541 5574 A database cannot be enabled for both FILESTREAM storage and Database Mirroring.
2542 5575 Operation '%ls' failed with HRESULT: %ls in file '%hs', line %d while executing sp_filestream_configure.
2543 5578 A failure occurred while FILESTREAM configuration was being changed or applied. For more information, see the SQL Server error log.
2544 5579 FILESTREAM: effective level = %d, configured level = %d, file system access share name = '%.*ls'.
2545 5580 FILESTREAM InstanceGuid is null. Registry settings might be corrupted.
2546 5581 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.
2547 5582 Machine reboot is required before the FILESTREAM feature settings can take effect.
2548 5583 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.
2549 5584 Another session is executing the sp_filestream_configure stored procedure. Check the updated configuration settings and retry the operation if necessary.
2550 5586 The FILESTREAM feature is already configured to the specified level. No change has been made.
2551 5590 FILESTREAM operations are not supported on the platform.
2552 5591 FILESTREAM feature is disabled.
2553 5592 FILESTREAM feature doesn't have file system access enabled.
2554 5593 FILESTREAM feature is not supported on WoW64. The feature is disabled.
2555 5594 The value specified for the computer_name_format parameter to the .PathName() function is not valid.
2556 5595 .PhysicalPathName is disabled.
2557 5596 FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration.
2558 5597 FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration Manager before enabling through sp_configure.
2559 5598 FILESTREAM feature is not supported on user instances.
2560 5600 The Cross Database Chaining option cannot be set to the specified value on the specified database.
2561 5601 The service master key could not be force regenerated as requested by the -F startup option. The error number is %ld.
2562 5602 The service master key regeneration was successful.
2563 5603 The password for SA could not be force regenerated as requested by the -K startup option. The error number is %ld.
2564 5604 The password regeneration attempt for SA was successful.
2565 5701 Changed database context to '%.*ls'.
2566 5702 SQL Server is terminating this process.
2567 5703 Changed language setting to %.*ls.
2568 5803 Unknown configuration (id = %d) encountered in sys.configurations.
2569 5804 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.
2570 5805 Too few locks specified. Minimum %d.
2571 5807 Recovery intervals above %d minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration.
2572 5808 Ad hoc update to system catalogs is not supported.
2573 5810 Valid values for the fill factor are 0 to 100.
2574 5812 You do not have permission to run the RECONFIGURE statement.
2575 5828 User connections are limited to %d.
2576 5829 The specified user options value is invalid.
2577 5831 Minimum server memory value (%d) must be less than or equal to the maximum value (%d).
2578 5832 The affinity mask specified does not match the CPU mask on this system.
2579 5833 The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
2580 5834 The affinity specified conflicts with the IO affinity mask specified. Change the affinity setting to use different CPUs than those specified in the IO affinity mask.
2581 5835 Failed to start CPUs with the mask 0x%lx on the system.
2582 5836 Lightweight pooling is not supported on this platform or in this edition of SQL Server.
2583 5837 The service broker listen port cannot be dynamic. Valid port values are 1024-32767.
2584 5838 The service broker connection authentication value is invalid.
2585 5839 The service broker message forward store size cannot be set to 0.
2586 5840 The service broker message forward mode is invalid.
2587 5841 The default full-text language is not supported by the full-text search component.
2588 5842 Too few worker threads are specified. The minimum is %d.
2589 5843 Address Windowing Extensions (AWE) is not supported in this edition of SQL Server.
2590 5844 User Instances are not supported in this edition of SQL Server.
2591 5845 Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
2592 5846 Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling".
2593 5848 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.
2594 5849 Online CPU addition is not supported in the current edition of SQL Server.
2595 5850 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.
2596 5851 The AccessCheckResult quota must be greater than or equal to the bucket count
2597 5852 The AccessCheckResult bucket count must be less than %d.
2598 5853 The affinity range is invalid. The lower bound %d must be less than the upper bound %d.
2599 5854 A %S_MSG value was specified more than one time in the range list for an ALTER SERVER CONFIGURATION SET PROCESS AFFINITY statement.
2600 5855 The affinity setting was not changed. This can be caused by low system resources.
2601 5856 The %S_MSG range that specifies %S_MSG %d includes at least one %S_MSG that is not available to the current instance. The maximum %S_MSG number that is available to this instance is %d.
2602 5857 CPU
2603 5858 NUMANODE
2604 5859 The current affinity setting specifies the use of more that 64 processors. Before you use sp_configure to change affinity settings, remove these processors by using ALTER SERVER CONFIGURATION.
2605 5860 Affinity changed for node %d: from 0x%0*I64x:%u to 0x%0*I64x:%u. This is an informational message only. No user action is required.
2606 5861 A %S_MSG with id %d does not exist on this system. Use sys.dm_os_schedulers to locate valid %S_MSGs for this system.
2607 5862 The number of max worker threads is set too low. On this computer, the number must be more than %u. You should increase the number of max worker threads.
2608 5904 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.
2609 6001 SHUTDOWN is waiting for %d process(es) to complete.
2610 6004 User does not have permission to perform this action.
2611 6005 SHUTDOWN is in progress.
2612 6006 Server shut down by %.*ls from login %.*ls.
2613 6007 The SHUTDOWN statement cannot be executed within a transaction or by a stored procedure.
2614 6101 Process ID %d is not a valid process ID. Choose a number between 1 and %d.
2615 6102 User does not have permission to use the KILL statement.
2616 6104 Cannot use KILL to kill your own process.
2617 6106 Process ID %d is not an active process ID.
2618 6107 Only user processes can be killed.
2619 6108 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).
2620 6109 SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%. Estimated time remaining: %d seconds.
2621 6110 The distributed transaction with UOW %s does not exist.
2622 6111 Another user has decided a different outcome for the distributed transaction associated with UOW %s.
2623 6112 Distributed transaction with UOW %s is in prepared state. Only Microsoft Distributed Transaction Coordinator can resolve this transaction. KILL command failed.
2624 6113 The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill the transaction instead.
2625 6114 Distributed transaction with UOW %s is being used by another user. KILL command failed.
2626 6115 KILL command cannot be used inside user transactions.
2627 6117 There is a connection associated with the distributed transaction with UOW %s. First, kill the connection using KILL SPID syntax.
2628 6118 The distributed transaction associated with UOW %s is not in PREPARED state. Use KILL UOW to kill the transaction instead.
2629 6119 Distributed transaction with UOW %s is rolling back: estimated rollback completion: %d%%, estimated time left %d seconds.
2630 6120 Status report cannot be obtained. Rollback operation for Process ID %d is not in progress.
2631 6121 Status report cannot be obtained. Rollback operation for UOW %s is not in progress.
2632 6200 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.
2633 6201 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.
2634 6202 Method "%ls" of type "%ls" in assembly "%.*ls" does not return a value.
2635 6203 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.
2636 6204 Trying to send a record with %d columns(s) in a result set with %d column(s).
2637 6205 %s ASSEMBLY failed because assembly '%.*ls' was compiled with /UNSAFE option, but the assembly was not registered with the required PERMISSION_SET = UNSAFE option.
2638 6206 Request submitted with too many parameters. The maximum number is %ld.
2639 6207 Error converting %.*ls to fixed length binary type. The result would be padded and cannot be converted back.
2640 6208 %s failed because the parameter count for the FillRow method should be one more than the SQL declaration for the table valued CLR function.
2641 6209 Unsound ordering on CLR type "%.*ls": returning NULL on non-NULL inputs.
2642 6210 CLR type '%.*ls' is not fully comparable.
2643 6211 %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.
2644 6212 %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.
2645 6213 %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.
2646 6214 %s ASSEMBLY failed because assembly "%.*ls" has an unmanaged entry point.
2647 6215 %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %.*ls assembly '%.*ls' has invalid attribute 0x%x.
2648 6216 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a finalizer. Finalizers are not allowed in %.*ls assemblies.
2649 6217 ALTER ASSEMBLY ADD FILE failed because the file, "%.*ls", being added is empty.
2650 6218 %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
2651 6219 %s ASSEMBLY failed because assembly source parameter %d has an unmanaged entry point.
2652 6220 SELECT INTO failed because CLR type "%.*ls" does not exist in the target database.
2653 6221 The cursor operation generated more than one row of different column metadata.
2654 6222 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is not valid for native serialization.
2655 6223 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".
2656 6224 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".
2657 6225 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.
2658 6226 Type "%.*ls.%.*ls" is marked for user-defined serialization, but does not implement the "%.*ls.%.*ls" interface.
2659 6227 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.
2660 6228 Type "%.*ls.%.*ls" is marked for native serialization, but it contains non-blittable fields.
2661 6229 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".
2662 6230 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.
2663 6231 Type "%.*ls.%.*ls" is marked for native serialization, but one of its base types "%.*ls.%.*ls" is not valid for native serialization.
2664 6232 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".
2665 6233 In proc data access is not allowed in an impersonated state.
2666 6234 Data truncation error. Length (%d) exceeds maximum length (%d) for type '%.*ls'.
2667 6235 Data serialization error. Length (%d) is less than fixed length (%d) for type '%.*ls'.
2668 6236 %s ASSEMBLY failed because filename '%.*ls' is too long.
2669 6237 %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
2670 6238 %s ASSEMBLY failed because field "%.*ls" in type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
2671 6239 %s ASSEMBLY failed because type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls".
2672 6240 ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the indexed view '%s'.
2673 6241 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.
2674 6242 CREATE ASSEMBLY failed because the user "%.*ls" specified in the authorization clause does not exist.
2675 6243 '%.*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.
2676 6244 The size (%d) for "%.*ls.%.*ls" is not in the valid range. Size must be -1 or a number between 1 and 8000.
2677 6245 Invalid serialization format (%d) for type "%.*ls.%.*ls".
2678 6246 Assembly "%.*ls" already exists in database "%.*ls".
2679 6247 Cannot create type because '%.*ls.%.*ls' cannot have fixed length if it has MaxByteSize set to -1.
2680 6248 %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.
2681 6249 The associated file "%.*ls" already exists for assembly "%.*ls".
2682 6250 Assembly "%.*ls" does not have an associated file "%.*ls".
2683 6251 ALTER ASSEMBLY failed because the assembly file parameter %d is not a valid expression.
2684 6252 ALTER ASSEMBLY failed because a file name was not specified for the inline assembly file parameter %d.
2685 6253 Common language runtime (CLR) functionality initialized using CLR version %ls from %ls.
2686 6254 Common language runtime (CLR) functionality initialized.
2687 6255 %s failed because type "%s" does not conform to the %s specification: missing custom attribute "%.*ls".
2688 6257 CREATE ASSEMBLY for assembly '%.*ls' failed because the assembly is built for an unsupported version of the Common Language Runtime.
2689 6258 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.
2690 6260 An error occurred while getting new row from user defined Table Valued Function : %.*ls.
2691 6261 The CLR type referenced by column "%.*ls" of table variable "%.*ls" has been dropped during the execution of the batch. Run the batch again.
2692 6262 Assembly was not found in current database or version did not match.
2693 6263 Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option.
2694 6264 Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read".
2695 6265 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a pinvokeimpl method. P/Invoke is not allowed in %.*ls assemblies.
2696 6266 Warning: Assembly "%.*ls" was built using version %.*ls of the .NET Framework. SQL Server currently uses version %s.
2697 6267 Assembly "%.*ls" does not exist, or the user does not have permission to reference it.
2698 6269 ALTER ASSEMBLY failed because the user-defined aggregate "%s" does not exist or is not correctly defined in the updated assembly.
2699 6270 ALTER ASSEMBLY failed because the required method "%s" in type "%s" was not found with the same signature in the updated assembly.
2700 6271 ALTER ASSEMBLY failed because the required field "%s" in type "%s" was not found with the same signature in the updated assembly.
2701 6272 ALTER ASSEMBLY failed because required property '%s' in type '%s' was not found with the same signature in the updated assembly.
2702 6273 ALTER ASSEMBLY failed because required type '%s' does not exist or is not correctly defined in the updated assembly.
2703 6274 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.
2704 6275 ALTER ASSEMBLY failed because the IsByteOrdered attribute of type '%s' would change in the updated assembly.
2705 6276 ALTER ASSEMBLY failed because serialization data of type '%s' would change in the updated assembly. Persisted types are not allowed to change serialization data.
2706 6277 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.
2707 6278 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.
2708 6279 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'.
2709 6280 ALTER ASSEMBLY failed because table, view or constraint '%s' depends on this assembly. Use WITH UNCHECKED DATA to skip checking for persisted data.
2710 6281 ALTER ASSEMBLY failed because only members of the sysadmin role can use WITH UNCHECKED DATA.
2711 6282 ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same.
2712 6283 ALTER ASSEMBLY failed because only the assembly revision version number is allowed to change.
2713 6284 ALTER ASSEMBLY failed because it is referenced by object '%.*ls'. Assemblies that are referenced by SQL objects cannot be made invisible.
2714 6285 %s ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name "%.*ls".
2715 6286 '%s' ASSEMBLY failed because a different version of assembly '%s', referenced by assembly '%s', is already in the database.
2716 6287 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'.
2717 6288 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.
2718 6289 Failed to allocate memory for common language runtime (CLR) functionality.
2719 6290 AppDomain %i (%.*ls) unloaded.
2720 6291 AppDomain %i (%.*ls) failed to unload with error code 0x%x.
2721 6292 The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction.
2722 6293 %.*ls.%.*ls.%.*ls: SqlFacetAttribute is invalid on a non-public member.
2723 6294 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute cannot be used in this context.
2724 6295 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute has an invalid value.
2725 6296 %.*ls.%.*ls.%.*ls : SqlFacetAttribute cannot be applied to a property getter or a property setter. It should be applied to the property itself.
2726 6297 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute property IsFixedLength cannot be set to true when MaxSize is set to -1.
2727 6298 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute properties Precision and Scale have to be used together.
2728 6299 AppDomain %i (%.*ls) created.
2729 6302 The argument of CREATE or ALTER XML SCHEMA COLLECTION statement must be a string expression.
2730 6303 XML parsing: Document parsing required too much memory
2731 6304 XML parsing: An unexpected error has occurred in the XML parser.
2732 6305 XQuery data manipulation expression required in XML data type method.
2733 6306 Invalid XQuery expression passed to XML data type method.
2734 6307 XML well-formedness check: Attribute cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
2735 6308 XML well-formedness check: Duplicate attribute '%.*ls'. Rewrite your XQuery so it returns well-formed XML.
2736 6309 XML well-formedness check: the data for node '%.*ls' contains a character (0x%04X) which is not allowed in XML.
2737 6310 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
2738 6311 An internal XMLDB schema processor error occurred. Contact Technical Support for assistance.
2739 6312 Could not find schema components with target namespace '%.*ls' in collection '%.*ls'.
2740 6314 Collection specified does not exist in metadata : '%.*ls'
2741 6315 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.
2742 6316 Specified component '%s' can not be dropped because it is used by component:'%s'
2743 6317 XQuery: Cannot update with value '%.*ls' because it failed validation against type '{%.*ls}%.*ls'
2744 6318 XQuery: String conversion failed during UPDATE validation
2745 6320 XQuery: Only nillable elements or text nodes can be updated with empty sequence
2746 6321 xml:space attribute must have a value of 'preserve' or 'default'. '%.*ls' is not valid.
2747 6322 XML Parser ran out of memory. This could be caused by too many attributes or namespace declarations.
2748 6323 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.
2749 6324 DROP XML INDEX does not support any options.
2750 6325 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 '()'.
2751 6326 XML well-formedness check: XML namespace declaration cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML.
2752 6327 The specified xml schema collection ID is not valid: %d
2753 6328 Specified collection '%.*ls' cannot be dropped because it is used by %S_MSG '%ls'.
2754 6329 Unsupported usage of a QName typed value in node '%.*ls'
2755 6330 Column '%.*ls' on table '%.*ls' is not of type XML, which is required to create an XML index on it.
2756 6331 Primary XML Index '%.*ls' already exists on column '%.*ls' on table '%.*ls', and multiple Primary XML Indexes per column are not allowed.
2757 6332 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.
2758 6333 Could not find%ls XML index named '%.*ls' on table '%.*ls'
2759 6334 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.
2760 6335 XML datatype instance has too many levels of nested nodes. Maximum allowed depth is %d levels.
2761 6336 Maximum size of primary index of table '%.*ls' is %d bytes. CREATE XML INDEX requires that such size should be limited to %d bytes
2762 6337 '%.*ls' is not a valid XML Index name because it starts with '%c' character. XML Index name should not start with '#' or '@'
2763 6338 XML DTD has been stripped from one or more XML fragments. External subsets, if any, have been ignored.
2764 6339 Specified collection '%.*ls' cannot be modified because it is SQL Server built-in XML Schema Collection.
2765 6340 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.
2766 6341 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.
2767 6342 Cannot create primary xml or spatial index '%.*ls' on table '%.*ls', column '%.*ls', because the column is computed.
2768 6343 Cannot create secondary xml index '%.*ls' without a USING XML INDEX clause.
2769 6344 The primary xml index '%.*ls' does not exist on table '%.*ls' column '%.*ls'.
2770 6345 The sparse column set '%.*ls' in the table '%.*ls' cannot be indexed by an XML index.
2771 6346 Cannot convert a primary XML index to a secondary XML index using the DROP_EXISTING option. '%.*ls' is a primary XML index.
2772 6347 Specified collection '%.*ls' cannot be altered because it does not exist or you do not have permission.
2773 6348 Specified collection '%.*ls' cannot be created because it already exists or you do not have permission.
2774 6350 The definition for xml schema collection '%.*ls' has changed.
2775 6351 The xml schema collection for return parameter of module '%.*ls' has been altered while the batch was being executed. Please re-run the batch.
2776 6352 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.
2777 6353 Serialization of built-in schemata is not supported.
2778 6354 Target string size is too small to represent the XML instance
2779 6355 Conversion of one or more characters from XML to target collation impossible
2780 6356 Failed to load DLL. Make sure xmlrw.dll exists in the SQL Server installation.
2781 6357 Internal error: cannot locate CreateInfoSetReaderEx in xmlrw.dll. You may have an incorrect version of xmlrw.dll.
2782 6358 %d is not a valid style number when converting to XML.
2783 6359 Parsing XML with internal subset DTDs not allowed. Use CONVERT with style option 2 to enable limited internal subset DTD support.
2784 6360 %d is not a valid style number when converting from XML.
2785 6361 Invalid null parameter specified. XML Schema Collections can only be created from a non-null value.
2786 6362 Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType.
2787 6363 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.
2788 6364 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.
2789 6365 An XML operation resulted an XML data type exceeding 2GB in size. Operation aborted.
2790 6401 Cannot roll back %.*ls. No transaction or savepoint of that name was found.
2791 6500 %ls failed because method '%ls' of class '%ls' in assembly '%ls' returns %ls, but CLR Triggers must return void.
2792 6501 %s ASSEMBLY failed because it could not open the physical file "%.*ls": %ls.
2793 6502 %s ASSEMBLY failed because it could not read from the physical file '%.*ls': %ls.
2794 6503 Assembly '%.*ls' was not found in the SQL catalog.
2795 6504 The value returned from %.*ls.%.*ls is not allowed to be NULL.
2796 6505 Could not find Type '%s' in assembly '%s'.
2797 6506 Could not find method '%s' for type '%s' in assembly '%s'
2798 6507 Failed to open malformed assembly '%ls' with HRESULT 0x%x.
2799 6508 Could not find field '%s' for type '%s' in assembly '%s'.
2800 6509 An error occurred while gathering metadata from assembly '%ls' with HRESULT 0x%x.
2801 6510 This functionality requires .NET Framework 3.5 SP1. Please install .NET Framework 3.5 SP1 to use this functionality.
2802 6511 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You may fix the problem and try again later.
2803 6512 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You need to restart SQL Server to use CLR integration features.
2804 6513 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.
2805 6514 Cannot use '%s' column in the result table of a streaming user-defined function (column '%.*ls').
2806 6515 Schema collection database '%.*ls' does not exist or you do not have permission.
2807 6516 There is no collection '%.*ls' in metadata '%.*ls'.
2808 6517 Failed to create AppDomain "%.*ls". %.*ls
2809 6518 Could not open system assembly ''%.*ls'': %ls.
2810 6519 Type '%.*ls' is not yet supported for CLR operations.
2811 6520 A .NET Framework error occurred during statement execution.
2812 6521 A .NET Framework error occurred during statement execution: %.*ls.
2813 6522 A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls.
2814 6523 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is static.
2815 6524 Cannot use computed column in the result table of a streaming user-defined function (column '%.*ls').
2816 6525 Cannot use '%s' constraint in the result table of a streaming user-defined function.
2817 6526 Cannot use '%s' constraint in the result table of a streaming user-defined function (column '%.*ls').
2818 6527 .NET Framework runtime has been stopped.
2819 6528 Assembly '%.*ls' was not found in the SQL catalog of database '%.*ls'.
2820 6529 ALTER ASSEMBLY failed because the identity of referenced assembly '%.*ls' has changed. Make sure the version, name, and public key have not changed.
2821 6530 Cannot perform alter on '%.*ls' because it is an incompatible object type.
2822 6531 %ls failed because the function '%ls' of class '%ls' of assembly '%.*ls' takes one or more parameters but CLR Triggers do not accept parameters.
2823 6532 .NET Framework execution was aborted by escalation policy because of out of memory. %.*ls
2824 6533 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource. %.*ls
2825 6534 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Application failed to release a managed lock. %.*ls
2826 6535 .NET Framework execution was aborted. Another query caused the AppDomain %.*ls to be unloaded. %.*ls
2827 6536 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.
2828 6537 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.
2829 6538 .NET Framework execution was aborted because of stack overflow. %.*ls
2830 6539 Invalid serialization format (Format.Unknown) for type '%.*ls.%.*ls'.
2831 6540 The assembly name '%.*ls' being registered has an illegal name that duplicates the name of a system assembly.
2832 6541 ALTER ASSEMBLY failed because assembly '%.*ls' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files.
2833 6542 Can not create object because %ls is a generic type.
2834 6543 .NET Framework execution was aborted. The UDP/UDF/CLR type did not end thread affinity.
2835 6544 %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is malformed or not a pure .NET assembly. %.*ls
2836 6545 Enabling of execution statistics SET options is not allowed from within CLR procedure or function.
2837 6546 Could not impersonate the execution context during the execution of '%.*ls'.
2838 6547 An error occurred while getting method, property or field information for "%ls" of class "%ls" in assembly "%.*ls".
2839 6548 CREATE ASSEMBLY failed because the assembly references assembly '%.*ls', which is owned by another user.
2840 6549 A .NET Framework error occurred during execution of user defined routine or aggregate '%.*ls': %ls. User transaction, if any, will be rolled back.
2841 6550 %s failed because parameter counts do not match.
2842 6551 %s for "%.*ls" failed because T-SQL and CLR types for return value do not match.
2843 6552 %s for "%.*ls" failed because T-SQL and CLR types for parameter "%.*ls" do not match.
2844 6553 %s failed because of an invalid .NET Framework calling convention. Use the default .NET Framework calling convention.
2845 6554 SQL assembly name '%.*ls', and .NET Framework assembly name '%.*ls' do not match. Assembly names must match.
2846 6555 Assembly '%.*ls' already exists for owner '%.*ls' in database '%.*ls'.
2847 6556 %s failed because it could not find type '%s' in assembly '%s'.
2848 6557 %s failed because type '%s' does not conform to %s specification due to field '%s'.
2849 6558 %s failed because type '%s' does not conform to %s specification due to method '%s'.
2850 6559 Could not find type ID %d in database %.*ls. This is due to a schema inconsistency.
2851 6560 Assembly "%.*ls" is a system assembly. This operation is permitted only with user assemblies.
2852 6561 Could not find file '%s' in directory '%s%s'.
2853 6562 Version mismatch between files '%s' (%d.%d.%d) and '%s' (%d.%d.%d).
2854 6563 Method, property or field '%ls' in class '%ls' in assembly '%.*ls' has invalid return type.
2855 6564 The method '%ls' in class '%ls' in assembly '%.*ls' has some invalid arguments. Value of type '%ls' is not valid for argument number %d.
2856 6565 %s ASSEMBLY failed because the assembly source parameter %d is not a valid assembly.
2857 6566 %s ASSEMBLY failed because the assembly source parameter %d is not a valid expression.
2858 6567 %s failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, System.Nullable, void.
2859 6568 A .NET Framework error occurred while getting information from class "%.*ls" in assembly "%.*ls": %ls.
2860 6569 '%.*ls' failed because parameter %d is not allowed to be null.
2861 6570 Method '%ls' of class '%ls' in assembly '%.*ls' is generic. Generic methods are not supported.
2862 6571 Class '%ls' in assembly '%.*ls' is generic. Generic types are not supported.
2863 6572 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.
2864 6573 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not static.
2865 6574 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not public.
2866 6575 Assembly names should be less than %d characters. Assembly name '%.*ls' is too long.
2867 6576 Type '%ls' in assembly '%ls' is not public.
2868 6577 CREATE TYPE failed because type '%s' does not conform to CLR type specification due to interface '%s'.
2869 6578 Invalid attempt to continue operation after a severe error.
2870 6579 Alter assembly from '%ls' to '%ls' is not a compatible upgrade.
2871 6580 Declarations do not match for parameter %d. .NET Framework reference and T-SQL OUTPUT parameter declarations must match.
2872 6581 Could not find assembly '%.*ls' in directory '%.*ls'.
2873 6582 Assembly '%.*s' is not visible for creating SQL objects. Use ALTER ASSEMBLY to change the assembly visibility.
2874 6583 Assembly '%.*s' cannot be used for creating SQL objects because it is a system assembly.
2875 6584 Property or field '%ls' for type '%ls' in assembly '%ls' is not static
2876 6585 Could not impersonate the client during assembly file operation.
2877 6586 Assembly '%.*ls' could not be installed because existing policy would keep it from being used.
2878 6587 Assembly reference '%ls' was redirected by external policy to '%ls'
2879 6588 Assembly file operations are not allowed for Windows NT users activated by SETUSER.
2880 6589 DROP ASSEMBLY failed because the specified assemblies are referenced by assembly '%ls'.
2881 6590 DROP ASSEMBLY failed because '%ls' is referenced by object '%ls'.
2882 6591 %s for "%.*ls" failed because first parameter of "%.*ls" method must be of type System.Object.
2883 6592 Could not find property or field '%ls' for type '%ls' in assembly '%ls'.
2884 6593 Property or field '%ls' for type '%ls' in assembly '%ls' is static.
2885 6594 Could not read from property '%ls' for type '%ls' in assembly '%ls' because it does not have a get accessor.
2886 6595 Could not assign to property '%ls' for type '%ls' in assembly '%ls' because it is read only.
2887 6596 %s ASSEMBLY failed because assembly '%ls' is a system assembly. Consider creating a user assembly to wrap desired functionality.
2888 6597 CREATE %s failed.
2889 6598 DROP ASSEMBLY failed because '%ls' is referenced by CLR type '%ls'.
2890 6599 Found an empty native serialization class '%.*ls'. Empty native serialization classes are not allowed.
2891 6600 XML error: %.*ls
2892 6601 The XML parse error 0x%x occurred on line number %d, near the XML text "%.*ls".
2893 6602 The error description is '%.*ls'.
2894 6603 XML parsing error: %.*ls
2895 6605 %.*ls: Failed to obtain an IPersistStream interface on the XML text.
2896 6607 %.*ls: The value supplied for parameter number %d is invalid.
2897 6608 Failed to instantiate class "%ls". Verify that Msxmlsql.dll exists in the SQL Server installation.
2898 6609 Invalid data type for the column "%ls". Allowed data types are CHAR/VARCHAR, NCHAR/NVARCHAR, TEXT/NTEXT, and XML.
2899 6610 Failed to load Msxmlsql.dll.
2900 6611 The XML data type is damaged.
2901 6613 Specified value '%ls' already exists.
2902 6621 XML encoding or decoding error occurred with object name '%.*ls'.
2903 6622 Invalid data type for column "%ls". The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml.
2904 6623 Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar.
2905 6624 XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
2906 6625 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.
2907 6626 Unexpected end of data stream.
2908 6627 The size of the data chunk that was requested from the stream exceeds the allowed limit.
2909 6628 %.*ls can only process untyped XML. Cast the input value to XML or to a string type.
2910 6629 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.
2911 6630 Element-centric mapping must be used with OPENXML when one of the columns is of type XML.
2912 6631 The requested OpenXML document is currently in use by another thread, and cannot be used.
2913 6632 Invalid data type for the column "%ls". CLR types cannot be used in an OpenXML WITH clause.
2914 6633 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".
2915 6634 OpenXML cannot be used as the target of a DML or OUTPUT INTO operation.
2916 6700 XQuery: The ' %ls' operation is not supported.
2917 6701 The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index.
2918 6716 XML Node ID is invalid. Re-build the database if the problem persists.
2919 6717 XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy.
2920 6718 XQuery: Invalid ordpath string: "%s"
2921 6739 XQuery: SQL type '%s' is not supported in XQuery.
2922 6743 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.
2923 6744 XQuery: One of the paths specified in the query is too deep. The maximum allowed depth is %d levels.
2924 6745 XQuery: Internal compiler error.
2925 6800 FOR XML AUTO requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name.
2926 6801 FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column.
2927 6802 FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integer.
2928 6803 FOR XML EXPLICIT requires the first column to hold positive integers that represent XML tag IDs.
2929 6804 FOR XML EXPLICIT requires the second column to hold NULL or nonnegative integers that represent XML parent tag IDs.
2930 6805 FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed.
2931 6806 Undeclared tag ID %d is used in a FOR XML EXPLICIT query.
2932 6807 Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query.
2933 6808 XML tag ID %d could not be added. The server memory resources may be low.
2934 6809 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.
2935 6810 Column name '%.*ls' is repeated. The same attribute cannot be generated more than once on the same XML tag.
2936 6811 FOR XML is incompatible with COMPUTE expressions. Remove the COMPUTE expression.
2937 6812 XML tag ID %d that was originally declared as '%.*ls' is being redeclared as '%.*ls'.
2938 6813 FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'.
2939 6814 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'.
2940 6815 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'.
2941 6816 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'.
2942 6817 FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'.
2943 6819 The FOR XML clause is not allowed in a %ls statement.
2944 6820 FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'.
2945 6821 GROUP BY and aggregate functions are currently not supported with FOR XML AUTO.
2946 6824 In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid.
2947 6825 ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML.
2948 6826 Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after the element to which they belong.
2949 6827 FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted.
2950 6828 XMLTEXT column '%.*ls' must be of a string data type or of type XML.
2951 6829 FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%.*ls'. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax.
2952 6830 FOR XML AUTO could not find the table owning the following column '%.*ls' to create a URL address for it. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax.
2953 6831 FOR XML AUTO requires primary keys to create references for '%.*ls'. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form if no primary keys exist.
2954 6832 FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary.
2955 6833 Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requires parent tags to be opened first. Check the ordering of the result set.
2956 6834 XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag and its attributes.
2957 6835 FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once.
2958 6836 FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls' to precede element-centric IDREFS/NMTOKEN fields.
2959 6838 Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either specify ELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive.
2960 6839 FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that has IDREFS or NMTOKENS fields.
2961 6840 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.
2962 6841 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.
2963 6842 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
2964 6843 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.
2965 6844 Two (or more) elements named '%.*ls' are of different types and not direct siblings in the same level.
2966 6845 Two (or more) elements named '%.*ls' are optional in the same level. Consider making them direct siblings or map NULL to xsi:nil
2967 6846 XML name space prefix '%.*ls' declaration is missing for FOR XML %.*ls name '%.*ls'.
2968 6847 The column '%.*ls' is of type sql_variant, which is not supported in attribute-centric FOR XML, with XML Schema.
2969 6848 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.
2970 6849 FOR XML PATH error in column '%.*ls' - '//' and leading and trailing '/' are not allowed in simple path expressions.
2971 6850 %.*ls name '%.*ls' contains an invalid XML identifier as required by FOR XML; '%c'(0x%04X) is the first character at fault.
2972 6851 Column '%.*ls' has invalid data type for attribute-centric XML serialization in FOR XML PATH.
2973 6852 Attribute-centric column '%.*ls' must not come after a non-attribute-centric sibling in XML hierarchy in FOR XML PATH.
2974 6853 Column '%.*ls': the last step in the path can't be applied to XML data type or CLR type in FOR XML PATH.
2975 6854 Invalid column alias '%.*ls' for formatting column as XML processing instruction in FOR XML PATH - it must be in 'processing-instruction(target)' format.
2976 6855 Inline schema is not supported with FOR XML PATH.
2977 6856 FOR XML row XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
2978 6857 FOR XML root XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault.
2979 6858 XML schema URI contains character '%c'(0x%04X) which is not allowed in XML.
2980 6859 Row tag name is only allowed with RAW or PATH mode of FOR XML.
2981 6860 FOR XML directive XMLDATA is not allowed with ROOT directive or row tag name specified.
2982 6861 Empty root tag name can't be specified with FOR XML.
2983 6862 Empty FOR XML target inline schema URI is not allowed.
2984 6863 Row tag omission (empty row tag name) is not compatible with XMLSCHEMA FOR XML directive.
2985 6864 Row tag omission (empty row tag name) cannot be used with attribute-centric FOR XML serialization.
2986 6865 FOR XML does not support CLR types - cast CLR types explicitly into one of the supported types in FOR XML queries.
2987 6866 Use of a system reserved XML schema URI is not allowed.
2988 6867 'xmlns' is invalid in XML tag name in FOR XML PATH, or when WITH XMLNAMESPACES is used with FOR XML.
2989 6868 The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives.
2990 6869 Attempt to redefine namespace prefix '%.*ls'
2991 6870 Prefix '%.*ls' used in WITH XMLNAMESPACES clause contains an invalid XML identifier. '%c'(0x%04X) is the first character at fault.
2992 6871 Prefix '%.*ls' used in WITH XMLNAMESPACES is reserved and cannot be used as a user-defined prefix.
2993 6872 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.
2994 6873 Redefinition of 'xsi' XML namespace prefix is not supported with ELEMENTS XSINIL option of FOR XML.
2995 6874 Empty URI is not allowed in WITH XMLNAMESPACES clause.
2996 6875 URI '%.*ls' used in WITH XMLNAMESPACES is invalid. '%c'(0x%04X) is the first character at fault.
2997 6876 URI used in WITH XMLNAMESPACES is too long. The maximum length is %d characters.
2998 6877 Empty namespace prefix is not allowed in WITH XMLNAMESPACES clause.
2999 6878 FORXML XMLSCHEMA cannot be used with a typed XML column whose schema collection is empty.
3000 6879 '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.
3001 6901 XML Validation: XML instance must be a document.
3002 6902 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.
3003 6903 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.
3004 6904 XML Validation: Found duplicate attribute '%s'. Location: %s
3005 6905 XML Validation: Attribute '%s' is not permitted in this context. Location: %s
3006 6906 XML Validation: Required attribute '%s' is missing. Location: %s
3007 6907 Namespace URI too long: '%.*ls'.
3008 6908 XML Validation: Invalid content. Expected element(s): %s. Location: %s
3009 6909 XML Validation: Text node is not allowed at this location, the type was defined with element only content or with simple content. Location: %s
3010 6910 XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support restriction of union types.
3011 6911 XML Validation: Found duplicate element '%s' in all content model. Location: %s
3012 6912 XML Validation: Element '%s' found in text only content model. Location: %s
3013 6913 XML Validation: Declaration not found for element '%s'. Location: %s
3014 6914 XML Validation: Type definition for type '%s' was not found, type definition is required before use in a type cast. Location: %s
3015 6915 Element or attribute name too long: '%.*ls'.
3016 6916 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.
3017 6917 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
3018 6918 XML Validation: Element '%s' must not have character or element children, because xsi:nil was set to true. Location: %s
3019 6919 XML Validation: The type of element '%s' is abstract. Instantiation requires the use of xsi:type to specify a non-abstract type. Location: %s
3020 6920 Invalid definition for type '%ls'. Cannot specify use="prohibited" for attribute '%ls' because there is no corresponding attribute in the base type.
3021 6921 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
3022 6922 XML Validation: Not able to resolve namespace for prefix:'%.*ls'
3023 6923 XML Validation: Unexpected element(s): %s. Location: %s
3024 6924 XML Validation: Text '%.*ls' found in attribute-only content model. Location: %s
3025 6925 Invalid definition for element '%ls'. SQL Server does not currently permit additions to existing substitution groups via ALTER XML SCHEMA COLLECTION.
3026 6926 XML Validation: Invalid simple type value: '%s'. Location: %s
3027 6927 XML Validation: Invalid simple type value: '%ls'.
3028 6928 XML Validation: XML instances of the content model of type or model group '%ls' can be validated in multiple ways and are not supported.
3029 6929 XML Validation: Invalid QName for xsi:type attribute '%.*ls'.
3030 6930 XML Validation: ID constraint check failed. Found attribute named '%.*ls' with duplicate ID value '%.*ls'. Location: %s
3031 6931 XML Validation: IDREF constraint check failed. Found attribute named '%.*ls' with reference to ID value '%.*ls', which does not exist
3032 6932 Invalid definition for element or attribute '%s'. Value constraints on components of type ID are not allowed.
3033 6933 XML Validation: Invalid simple type operation, inserting into simple type is not permitted. Location: %s
3034 6934 XML Validation: Element '%s' requires substitution, because it was defined as abstract. Location: %s
3035 6935 XML Validation: ID or IDREF attribute exceeded the allowed maximum length. Location: %s
3036 6936 XML Validation: Invalid cast for element '%s' from type '%s' to type '%s'. Location: %s
3037 6937 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
3038 6938 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.
3039 6939 XML Validation: The element '%ls' is mixed content with a fixed value and therefore not allowed to have element content. Location: %ls
3040 6940 Invalid component named '%s' found in global scope. Only elements, attributes, types and groups can be defined in global context
3041 6941 Invalid type definition for type '%s', types with complex content can only be derived from base types which have complex content
3042 6942 Invalid type definition for type '%s', types with simple content can only be derived from base types which have simple content
3043 6943 Invalid type definition for type '%s', the derivation was illegal because 'final' attribute was specified on the base type
3044 6944 Invalid type definition for type '%s', '%s' facet is not restricting the value space
3045 6945 Invalid facet value for facet '%s' in type definition '%s'
3046 6946 Invalid type definition for type '%s', 'minLength' can not be greater than 'maxLength'
3047 6947 XML Validation: Multiple ID attributes found on a single element. Location: %s
3048 6948 Invalid type definition for type '%s', 'minLength' can not be greater than 'Length'
3049 6949 Invalid type definition for type '%s', 'Length' can not be greater than 'maxLength'
3050 6950 Invalid type definition for type '%s', 'fractionDigits' can not be greater than 'totalDigits'
3051 6951 Invalid type definition for type '%s', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive'
3052 6952 Invalid type definition for type '%s', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive'
3053 6953 Invalid type definition for type '%s', recursive type definitions are not allowed
3054 6954 Invalid group definition for group '%s', recursive group definitions are not allowed
3055 6955 Invalid attribute definition for attribute '%s', attributes type has to be simple type
3056 6956 Invalid type definition for type '%s', fixed facet '%s' can not be redefined to a different value.
3057 6957 Invalid element definition, element '%s' is not valid derivation of element '%s'
3058 6958 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
3059 6959 Invalid definition, top level group definitions can not have model groups as siblings
3060 6960 Component '%s' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional part is 28
3061 6961 The system limit on the number of XML types has been reached. Redesign your database to use fewer XML types.
3062 6962 'default' and 'fixed' values are not allowed on element of this type: '%s'
3063 6963 'Default' or 'Fixed' value is longer than allowed, maximum length allowed is 4000 characters : '%s'
3064 6964 Facet value is longer than allowed, maximum length allowed is 4000 characters : '%s'
3065 6965 XML Validation: Invalid content. Expected element(s): %s. Found: element '%s' instead. Location: %s.
3066 6966 Warning: Type '%s' is restricted by a facet '%s' that may impede full round-tripping of instances of this type
3067 6967 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.
3068 6968 Invalid type definition for type '%s'. Complex types cannot restrict simple types
3069 6969 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.
3070 6970 Invalid type definition for type '%s'. No type may have more than one attribute of any type derived from ID.
3071 6971 Invalid type definition for type '%s'. Type contains attribute '%s' which is not allowed in base type.
3072 6972 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.
3073 6973 Invalid redefinition of attribute '%s' in type '%s'. Must be required in the derived type if it is required in the base type.
3074 6974 Invalid redefinition of attribute '%s' in type '%s'. Must be prohibited in the derived type if it is prohibited in the base type.
3075 6975 Invalid redefinition of attribute '%s' in type '%s'. Must be fixed to the same value as in the derived type.
3076 6976 Invalid redefinition of attribute '%s' in type '%s'. Derivation by extension may not redefine attributes.
3077 6977 Invalid member type '%s' in union type '%s'. Unions may not have complex member types.
3078 6978 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.
3079 6979 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.
3080 6980 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.
3081 6981 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.
3082 6982 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.
3083 6983 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.
3084 6984 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.
3085 6985 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.
3086 6986 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.
3087 6987 Invalid restriction for type '%s'. An 'all' particle may be restricted only by 'all', 'element', or 'sequence'.
3088 6988 Invalid restriction for type '%s'. A 'choice' particle may be restricted only by 'element', 'choice', or 'sequence'.
3089 6989 Invalid restriction for type '%s'. A 'sequence' particle may be restricted only by 'element' or 'sequence'.
3090 6990 Invalid restriction for type '%s'. Invalid model group restriction.
3091 6991 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.
3092 6992 The content model of type '%s' contains two elements with the same name '%s' and different types, nullability, or value constraints.
3093 6993 Value constraint on use of attribute '%s' must be consistent with value constraint on its declaration.
3094 6994 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.
3095 6995 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.
3096 6996 Invalid type definition for type '%s'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and 'maxExclusive' facets.
3097 6997 Invalid definition for element '%s'. An element which has a fixed value may not also be nillable.
3098 6998 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.
3099 6999 Invalid definition for element or attribute '%s'. Value constraints on components of type QName are not supported in this release.
3100 7000 OPENXML document handle parameter must be of data type int.
3101 7001 OPENXML flags parameter must be of data type int.
3102 7002 OPENXML XPath must be of a string data type, such as nvarchar.
3103 7003 Only one OPENXML column can be of type %ls.
3104 7004 OPENXML does not support retrieving schema from remote tables, as in '%.*ls'.
3105 7005 OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument.
3106 7006 OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement.
3107 7007 OPENXML encountered unknown metaproperty '%.*ls'.
3108 7008 The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag.
3109 7009 OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument.
3110 7101 You need an active user transaction in order to use text pointers for a table with the option "text in row" set to ON.
3111 7102 Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
3112 7104 Offset or size of data type is not valid. Data type must be of type int or smallint.
3113 7105 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.
3114 7106 Internal error: An attempt was made to update a LOB data type using a read-only text pointer.
3115 7107 You can have only 1,024 in-row text pointers in one transaction
3116 7108 Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
3117 7116 Offset %d is not in the range of available LOB data.
3118 7117 Error reading large object (LOB) data from the tabular data stream (TDS).
3119 7118 Only complete replacement is supported when assigning a large object (LOB) to itself.
3120 7119 Attempting to grow LOB beyond maximum allowed size of %I64d bytes.
3121 7122 Invalid text, ntext, or image pointer type. Must be binary(16).
3122 7123 Invalid text, ntext, or image pointer value %hs.
3123 7124 The offset and length specified in the READTEXT statement is greater than the actual data length of %ld.
3124 7125 The text, ntext, or image pointer value conflicts with the column name specified.
3125 7133 NULL textptr (text, ntext, or image pointer) passed to %ls function.
3126 7134 LOB Locator is not supported as text pointer when using UPDATETEXT/WRITETEXT to update/write a text column.
3127 7135 Deletion length %ld is not in the range of available text, ntext, or image data.
3128 7137 %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.
3129 7138 The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or tracked by Change Data Capture.
3130 7139 Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld.
3131 7140 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.
3132 7141 Must create orphaned text inside a user transaction.
3133 7143 Invalid locator de-referenced.
3134 7144 A text/ntext/image column referenced by a persisted or indexed computed column cannot be updated
3135 7151 Insufficient buffer space to perform write operation.
3136 7201 Could not execute procedure on remote server '%.*ls' because SQL Server is not configured for remote access. Ask your system administrator to reconfigure SQL Server to allow remote access.
3137 7202 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.
3138 7212 Could not execute procedure '%.*ls' on remote server '%.*ls'.
3139 7213 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.
3140 7214 Remote procedure time out of %d seconds exceeded. Remote procedure '%.*ls' is canceled.
3141 7215 Could not execute statement on remote server '%.*ls'.
3142 7221 Could not relay results of procedure '%.*ls' from remote server '%.*ls'.
3143 7301 Cannot obtain the required interface ("%ls") from OLE DB provider "%ls" for linked server "%ls".
3144 7302 Cannot create an instance of OLE DB provider "%ls" for linked server "%ls".
3145 7303 Cannot initialize the data source object of OLE DB provider "%ls" for linked server "%ls".
3146 7304 Cannot connect using OLE DB provider "%ls" to linked server "%ls". Verify the connection parameters or login credentials associated with this linked server.
3147 7305 Cannot create a statement object using OLE DB provider "%ls" for linked server "%ls".
3148 7306 Cannot open the table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
3149 7307 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.
3150 7308 OLE DB provider '%ls' cannot be used for distributed queries because the provider is configured to run in single-threaded apartment mode.
3151 7310 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.
3152 7311 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.
3153 7312 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.
3154 7313 An invalid schema or catalog was specified for the provider "%ls" for linked server "%ls".
3155 7314 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.
3156 7315 The OLE DB provider "%ls" for linked server "%ls" contains multiple tables that match the name "%ls".
3157 7316 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.
3158 7317 The OLE DB provider "%ls" for linked server "%ls" returned an invalid schema definition.
3159 7318 The OLE DB provider "%ls" for linked server "%ls" returned an invalid column definition for table "%ls".
3160 7319 The OLE DB provider "%ls" for linked server "%ls" returned a "%ls" index "%ls" with the incorrect bookmark ordinal %d.
3161 7320 Cannot execute the query "%ls" against OLE DB provider "%ls" for linked server "%ls". %ls
3162 7321 An error occurred while preparing the query "%ls" for execution against OLE DB provider "%ls" for linked server "%ls". %ls
3163 7322 A failure occurred while giving parameter information to OLE DB provider "%ls" for linked server "%ls".
3164 7323 An error occurred while submitting the query text to OLE DB provider "%ls" for linked server "%ls".
3165 7324 A failure occurred while setting parameter properties with OLE DB provider "%ls" for linked server "%ls".
3166 7325 Objects exposing columns with CLR types are not allowed in distributed queries. Please use a pass-through query to access remote object '%ls'.
3167 7330 Cannot fetch a row from OLE DB provider "%ls" for linked server "%ls".
3168 7331 Rows from OLE DB provider "%ls" for linked server "%ls" cannot be released.
3169 7332 Cannot rescan the result set from OLE DB provider "%ls" for linked server "%ls". %ls
3170 7333 Cannot fetch a row using a bookmark from OLE DB provider "%ls" for linked server "%ls".
3171 7339 OLE DB provider '%ls' for linked server '%ls' returned invalid data for column '%ls.%ls'.
3172 7340 Cannot create a column accessor for OLE DB provider "%ls" for linked server "%ls".
3173 7341 Cannot get the current row value of column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
3174 7342 An unexpected NULL value was returned for column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". This column cannot be NULL.
3175 7343 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls". %ls
3176 7344 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls" because of column "%ls". %ls
3177 7345 The OLE DB provider "%ls" for linked server "%ls" could not delete from table "%ls". %ls
3178 7346 Cannot get the data of the row from the OLE DB provider "%ls" for linked server "%ls". %ls
3179 7347 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.
3180 7348 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.
3181 7349 The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls" because of column "%ls". %ls
3182 7350 Cannot get the column information from OLE DB provider "%ls" for linked server "%ls".
3183 7351 The OLE DB provider "%ls" for linked server "%ls" could not map ordinals for one or more columns of object "%ls".
3184 7352 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. The object "%ls" was missing the expected column "%ls".
3185 7353 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.
3186 7354 The OLE DB provider "%ls" for linked server "%ls" supplied invalid metadata for column "%ls". %ls
3187 7355 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The name was changed at execution time.
3188 7356 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.
3189 7357 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.
3190 7358 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".
3191 7359 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".
3192 7360 Cannot get the length of a storage object from OLE DB provider "%ls" for linked server "%ls" for table "%ls", column "%ls".
3193 7361 Cannot read a storage object from OLE DB provider "%ls" for linked server "%ls", for table "%ls", column "%ls".
3194 7362 The OLE DB provider "%ls" for linked server "%ls" reported different metadata at run time for table "%ls", column "%ls".
3195 7365 Cannot obtain optional metadata columns of columns rowset from OLE DB provider "%ls" for linked server "%ls".
3196 7366 Cannot obtain columns rowset from OLE DB provider "%ls" for linked server "%ls".
3197 7367 The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide the metadata column "%ls" at run time.
3198 7368 The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide collation data for column "%ls".
3199 7369 The OLE DB provider '%ls' for linked server '%ls' provided invalid collation. LCID = %08x, Compflags = %08x, SortOrder = '%.*ls'.
3200 7370 One or more properties could not be set on the query for OLE DB provider "%ls" for linked server "%ls". %ls
3201 7371 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.
3202 7372 Cannot get properties from OLE DB provider "%ls" for linked server "%ls".
3203 7373 Cannot set the initialization properties for OLE DB provider "%ls" for linked server "%ls".
3204 7374 Cannot set the session properties for OLE DB provider "%ls" for linked server "%ls".
3205 7375 Cannot open index "%ls" on table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls
3206 7376 Could not enforce the remote join hint for this query.
3207 7377 Cannot specify an index hint for a remote data source.
3208 7380 Table-valued parameters are not allowed in remote calls between servers.
3209 7390 The requested operation could not be performed because OLE DB provider "%ls" for linked server "%ls" does not support the required transaction interface.
3210 7391 The operation could not be performed because OLE DB provider "%ls" for linked server "%ls" was unable to begin a distributed transaction.
3211 7392 Cannot start a transaction for OLE DB provider "%ls" for linked server "%ls".
3212 7393 The OLE DB provider "%ls" for linked server "%ls" reported an error 0x%08X aborting the current transaction.
3213 7394 The OLE DB provider "%ls" for linked server "%ls" reported an error committing the current transaction.
3214 7395 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.
3215 7396 Varchar(max), nvarchar(max), varbinary(max) and large CLR type data types are not supported as return value or output parameter to remote queries.
3216 7397 Remote function returned varchar(max), nvarchar(max), varbinary(max) or large CLR type value which is not supported.
3217 7399 The OLE DB provider "%ls" for linked server "%ls" reported an error. %ls
3218 7401 The OLE DB provider "%ls" returned invalid literal prefix/suffix string.
3219 7403 The OLE DB provider "%ls" has not been registered.
3220 7404 The server could not load DCOM.
3221 7405 Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query.
3222 7409 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.
3223 7410 Remote access is not allowed for impersonated security context.
3224 7411 Server '%.*ls' is not configured for %ls.
3225 7412 OLE DB provider "%ls" for linked server "%ls" returned message "%ls".
3226 7413 Could not connect to linked server '%ls' (OLE DB Provider '%ls'). Enable delegation or use a remote SQL Server login for the current user.
3227 7414 Invalid number of parameters. Rowset '%ls' expects %d parameter(s).
3228 7415 Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server.
3229 7416 Access to the remote server is denied because no login-mapping exists.
3230 7417 GROUP BY ALL is not supported in queries that access remote tables if there is also a WHERE clause in the query.
3231 7418 Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider.
3232 7419 Lazy schema validation error. Linked server schema version has changed. Re-run the query.
3233 7420 Remote access is not supported for transaction isolation level "%ls".
3234 7421 Cannot fetch the rowset from OLE DB provider "%ls" for linked server "%ls". %ls.
3235 7422 OLE DB provider "%ls" for linked server "%ls" returned an invalid index definition for table "%ls".
3236 7423 The '%ls' OLE DB provider for the '%ls' linked server returned an invalid CLR type definition for the '%ls' table.
3237 7424 OLE DB provider "%ls" for linked server "%ls" returned "%ls" with data type "%ls", which should be type "%ls".
3238 7425 OLE DB provider "%ls" for linked server "%ls" returned an incorrect value for "%ls", which should be "%ls".
3239 7426 OLE DB provider "%ls" for linked server "%ls" returned "%ls" without "%ls" being supported.
3240 7427 OLE DB provider "%ls" for linked server "%ls" returned "%ls" for "%ls" during statistics gathering.
3241 7428 OLE DB provider "%ls" for linked server "%ls" supported the schema lock interface, but returned "%ls" for "%ls".
3242 7429 %hs SQL Server Remote Metadata Gather Time for Table %s.%s:%hs, CPU time = %lu ms, elapsed time = %lu ms.
3243 7430 Out-of-process use of OLE DB provider "%ls" with SQL Server is not supported.
3244 7431 Unable to delete OLE DB parameter properties.
3245 7432 Heterogeneous queries and use of OLEDB providers are not supported in fiber mode.
3246 7433 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.
3247 7435 The OLE DB provider "%ls" for linked server "%ls" returned unexpected NULL pointer for string column "%ls.%ls".
3248 7601 Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because it is not full-text indexed.
3249 7604 Full-text operation failed due to a time out.
3250 7606 Could not find full-text index for database ID %d, table or indexed view ID %d.
3251 7607 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).
3252 7608 An unknown full-text failure (0x%x) occurred during "%hs".
3253 7609 Full-Text Search is not installed, or a full-text component cannot be loaded.
3254 7610 Access is denied to "%.*ls", or the path is invalid.
3255 7613 Cannot drop index '%.*ls' because it enforces the full-text key for table or indexed view '%.*ls'.
3256 7614 Cannot alter or drop column '%.*ls' because it is enabled for Full-Text Search.
3257 7615 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.
3258 7616 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.
3259 7617 Query does not reference the full-text indexed table or indexed view, or user does not have permission to perform this action.
3260 7619 The execution of a full-text query failed. "%ls"
3261 7620 The conversion to data type %ls failed for the full-text search key.
3262 7621 Invalid use of full-text predicate in the HAVING clause.
3263 7622 There is not sufficient disk space to complete this operation for the full-text catalog "%ls".
3264 7624 Full-text catalog '%ls' is in an unusable state. Drop and re-create this full-text catalog.
3265 7625 Full-text table or indexed view has more than one LCID among its full-text indexed columns.
3266 7626 The top_n_by_rank argument ('%d') must be greater than or equal to zero.
3267 7627 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.
3268 7629 Cannot open or query the full-text default path registry key. The full-text default catalog path is invalid.
3269 7630 Syntax error near '%.*ls' in the full-text search condition '%.*ls'.
3270 7632 The value of the Weight argument must be between 0.0 and 1.0.
3271 7636 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.
3272 7638 Warning: Request to stop change tracking has deleted all changes tracked on table or indexed view '%ls'.
3273 7640 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.
3274 7641 Full-Text catalog '%ls' does not exist in database '%.*ls' or user does not have permission to perform this action.
3275 7642 A full-text catalog named '%ls' already exists in this database. Use a different name.
3276 7644 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.
3277 7645 Null or empty full-text predicate.
3278 7646 Fulltext predicate references columns from two different tables or indexed views '%.*ls' and '%.*ls' which is not allowed.
3279 7647 Warning: Configuration of full-text catalog at '%ls' could not be saved during detach database.
3280 7648 Warning: Failed to attach full-text catalog '%ls'.
3281 7649 Warning: Failed to dismount full-text catalog at '%ls'.
3282 7650 Warning: Failed to drop full-text catalog at '%ls'.
3283 7651 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.
3284 7652 A full-text index for table or indexed view '%.*ls' has already been created.
3285 7653 '%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.
3286 7654 Unable to obtain the population status of the table or indexed view '%.*ls'.
3287 7655 TYPE COLUMN option must be specified with column of image or varbinary(max) type.
3288 7656 Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode.
3289 7657 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.
3290 7658 Table or indexed view '%.*ls' does not have a full-text index or user does not have permission to perform this action.
3291 7659 Cannot activate full-text search for table or indexed view '%.*ls' because no columns have been enabled for full-text search.
3292 7660 Full-text search must be activated on table or indexed view '%.*ls' before this operation can be performed.
3293 7661 Warning: Full-text change tracking is currently enabled for table or indexed view '%.*ls'.
3294 7662 Warning: Full-text auto propagation is currently enabled for table or indexed view '%.*ls'.
3295 7663 Option 'WITH NO POPULATION' should not be used when change tracking is enabled.
3296 7664 Full-text change tracking must be started on table or indexed view '%.*ls' before the changes can be flushed.
3297 7665 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.
3298 7666 User does not have permission to perform this action.
3299 7668 Cannot drop full-text catalog '%ls' because it contains a full-text index.
3300 7669 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.
3301 7670 Column '%.*ls' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column.
3302 7671 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.
3303 7672 A full-text index cannot be created on the table or indexed view because duplicate column '%.*ls' is specified.
3304 7673 Warning: Full-text change tracking is currently disabled for table or indexed view '%.*ls'.
3305 7674 Warning: The fulltext catalog '%.*ls' is being dropped and is currently set as default.
3306 7676 Warning: Full-text auto propagation is on. Stop crawl request is ignored.
3307 7677 Column "%.*ls" is not full-text indexed.
3308 7678 The following string is not defined as a language alias in syslanguages: %.*ls.
3309 7679 Full-text index language of column "%.*ls" is not a language supported by full-text search.
3310 7680 Default full-text index language is not a language supported by full-text search.
3311 7681 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.
3312 7682 The component '%ls' reported error while indexing. Component path '%ls'.
3313 7683 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.
3314 7684 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.
3315 7685 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.
3316 7689 Execution of a full-text operation failed. '%ls'
3317 7690 Full-text operation failed because database is read only.
3318 7691 Access is denied to full-text log path. Full-text logging is disabled for database '%ls', catalog '%ls' (database ID '%d', catalog ID '%d').
3319 7692 Full-text catalog path '%.*ls' exceeded %d character limit.
3320 7693 Full-text initialization failed to create a memory clerk.
3321 7694 Failed to pause catalog for backup. Backup was aborted.
3322 7696 Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed.
3323 7697 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.
3324 7698 GROUP BY ALL cannot be used in full text search queries.
3325 7699 TYPE COLUMN option is not allowed for column types other than image or varbinary(max).
3326 7702 Empty Partition function type-parameter-list is not allowed when defining a partition function.
3327 7703 Can not create RANGE partition function with multiple parameter types.
3328 7704 The type '%.*ls' is not valid for this operation.
3329 7705 Could not implicitly convert range values type specified at ordinal %d to partition function parameter type.
3330 7706 Partition function '%ls' is being used by one or more partition schemes.
3331 7707 The associated partition function '%ls' generates more partitions than there are file groups mentioned in the scheme '%ls'.
3332 7708 Duplicate range boundary values are not allowed in partition function boundary values list. Partition boundary values at ordinal %d and %d are equal.
3333 7709 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.
3334 7710 Warning: The partition scheme '%.*ls' does not have any next used filegroup. Partition scheme has not been changed.
3335 7711 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.
3336 7712 Partition scheme '%.*ls' has been created successfully. '%.*ls' is marked as the next used filegroup in partition scheme '%.*ls'.
3337 7713 %d filegroups specified after the next used filegroup are ignored.
3338 7714 Partition range value is missing.
3339 7715 The specified partition range value could not be found.
3340 7716 Can not create or alter a partition function to have zero partitions.
3341 7717 The partition scheme "%.*ls" is currently being used to partition one or more tables.
3342 7718 Partition range value cannot be specified for hash partitioning.
3343 7719 CREATE/ALTER partition function failed as only a maximum of %d partitions can be created.
3344 7720 Data truncated when converting range values to the partition function parameter type. The range value at ordinal %d requires data truncation.
3345 7721 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.
3346 7722 Invalid partition number %I64d specified for %S_MSG '%.*ls', partition number can range from 1 to %d.
3347 7723 Only a single filegroup can be specified while creating partition scheme using option ALL to specify all the filegroups.
3348 7724 Computed column cannot be used as a partition key if it is not persisted. Partition key column '%.*ls' in table '%.*ls' is not persisted.
3349 7725 Alter partition function statement failed. Cannot repartition table '%.*ls' by altering partition function '%.*ls' because its clustered index '%.*ls' is disabled.
3350 7726 Partition column '%.*ls' has data type %s which is different from the partition function '%.*ls' parameter data type %s.
3351 7727 Collation of partition column '%.*ls' does not match collation of corresponding parameter in partition function '%.*ls'.
3352 7728 Invalid partition range: %d TO %d. Lower bound must not be greater than upper bound.
3353 7729 Cannot specify partition number in the %S_MSG %S_MSG statement as the %S_MSG '%.*ls' is not partitioned.
3354 7730 Alter %S_MSG statement failed because partition number %d does not exist in %S_MSG '%.*ls'.
3355 7731 Cannot specify partition number in Alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls'.
3356 7732 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.
3357 7733 '%ls' statement failed. The %S_MSG '%.*ls' is partitioned while %S_MSG '%.*ls' is not partitioned.
3358 7734 The %S_MSG '%.*ls' specified for the clustered index '%.*ls' was used for table '%.*ls' even though %S_MSG '%.*ls' is specified for it.
3359 7735 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.
3360 7736 Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning.
3361 7737 Filegroup %.*ls is of a different filegroup type than the first filegroup in partition scheme %.*ls
3362 7738 Cannot enable compression for object '%.*ls'. Only SQL Server Enterprise Edition supports compression.
3363 7801 The required parameter %.*ls was not specified.
3364 7802 Functions that have a return type of "%.*ls" are unsupported through SOAP invocation.
3365 7803 The clause %.*ls can not be used in the %.*ls statement.
3366 7804 %.*ls and %.*ls can not share the same value.
3367 7805 The parameter SITE can not be prefixed by a scheme such as 'http://'. Valid values for SITE include {'*' | '+' | 'site_name'}.
3368 7806 The URL specified by endpoint '%.*ls' is already registered to receive requests or is reserved for use by another service.
3369 7807 An error ('0x%x') occurred while attempting to register the endpoint '%.*ls'.
3370 7808 The endpoint '%.*ls' could not be unregistered.
3371 7809 Cannot find the object '%.*ls', because it does not exist or you do not have permission.
3372 7810 The value '%d' is not within range for the '%.*ls' parameter.
3373 7811 COMPUTE BY queries are not supported over SOAP.
3374 7812 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.
3375 7813 The parameter PATH must be supplied in its canonical form. An acceptable PATH is '%.*ls'.
3376 7814 The specified value '%.*ls' already exists.
3377 7815 The specified value '%.*ls' does not exist.
3378 7816 A duplicate parameter was specified, '%.*ls'.
3379 7817 The Base64 encoded input data was malformed for the parameter "%.*ls".
3380 7818 The request exceeds an internal limit. Simplify or reduce the size of the request.
3381 7819 The SOAP method object '%.*ls' must be specified using a fully qualified three-part name.
3382 7820 SOAP namespaces beginning with '%.*ls' are disallowed because they are reserved for system use.
3383 7821 Cannot find the database '%.*ls', because it does not exist or you do not have permission.
3384 7822 An unexpected XML node "%.*ls" (in the namespace "%.*ls") was found in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request.
3385 7823 The "%.*ls" XML element (in the "%.*ls" namespace) was expected in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request.
3386 7824 The "%.*ls" XML element (in the "%.*ls" namespace) was expected as the topmost node of the SOAP request.
3387 7825 A SOAP method element was expected in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request.
3388 7826 Unexpected character data was found in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request.
3389 7827 The user does not have permission to reserve and unreserve HTTP namespaces.
3390 7828 The statement is not supported on this version of the operating system. Could not find Httpapi.dll in the path.
3391 7829 The statement is not supported on this version of the operating system. Could not find function entry point '%.*ls' in Httpapi.dll.
3392 7830 Unable to complete the operation because of an unexpected error.
3393 7831 A reservation for this HTTP namespace (%.*ls) already exists.
3394 7832 A reservation for this HTTP namespace (%.*ls) does not exist.
3395 7833 The HTTP namespace (%.*ls) is in an invalid format. Specify the namespace in its canonical form.
3396 7834 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.
3397 7835 Endpoint '%.*ls' has been disabled because it is insecurely configured. For a more information, attempt to start the endpoint using the ALTER ENDPOINT statement.
3398 7836 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.
3399 7847 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.
3400 7848 An invalid or unsupported localeId was specified for parameter "%.*ls".
3401 7849 Invalid sqlCompareOptions were specified for parameter "%.*ls".
3402 7850 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.
3403 7851 The %.*ls attribute must be specified on the %.*ls element of the parameter "%.*ls" because it is of type %.*ls.
3404 7852 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.
3405 7853 The URL specified as the path ("%.*ls") is not in an absolute format, and must begin with "%.*ls".
3406 7854 The URL value specified for the "%.*ls" parameter is too long.
3407 7855 Reading from HTTP input stream failed.
3408 7856 XML parameters do not support non-unicode element or attribute values.
3409 7857 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.
3410 7858 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.
3411 7859 Parameter "%.*ls": Parameter collation cannot be specified on the "%.*ls" node (in the namespace "%.*ls").
3412 7860 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.
3413 7861 "%.*ls" endpoints can only be of the "FOR %.*ls" type.
3414 7862 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.
3415 7863 The endpoint was not changed. The ALTER ENDPOINT statement did not contain any values to modify or update.
3416 7864 CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection endpoint is reserved and cannot be updated.
3417 7865 Web Services Description Language (WSDL) generation failed because the system was unable to query the metadata for the endpoint.
3418 7866 XML attribute and element values larger than 4000 characters are only allowed within the SOAP Body node.
3419 7867 An invalid sqlCollationVersion was specified for parameter "%.*ls".
3420 7868 An invalid sqlSortId was specified for parameter "%.*ls".
3421 7869 The endpoint name '%.*ls' is reserved for used by SQL. Endpoint names cannot begin with '%.*ls'.
3422 7870 The AFFINITY clause is not supported for endpoints of this type.
3423 7871 The clause "%.*ls" is not valid for this endpoint type.
3424 7872 "%.*ls" is not a parameter for procedure "%.*ls", or it was supplied out of order.
3425 7873 The endpoint "%.*ls" is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP Transact-SQL endpoints.
3426 7874 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.
3427 7875 An unexpected XML construct was found in the character data of the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request.
3428 7878 This "%.*ls ENDPOINT" statement is not supported on this edition of SQL Server.
3429 7879 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.
3430 7880 SQL Server has successfully finished closing sessions and connections.
3431 7881 SQL Server was unable to close sessions and connections in a reasonable amount of time and is aborting "polite" shutdown.
3432 7882 OUTPUT was requested for parameter '%.*ls', which is not supported for a WEBMETHOD with FORMAT=NONE.
3433 7883 User-defined functions cannot be used for a WEBMETHOD with FORMAT=NONE.
3434 7884 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.
3435 7885 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.
3436 7886 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.
3437 7887 The IPv6 address specified is not supported. Only addresses that are in their numeric, canonical form are supported for listening.
3438 7888 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.
3439 7889 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.
3440 7890 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.
3441 7891 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]'.
3442 7892 Internal subset DTDs inside SOAP requests are not allowed.
3443 7893 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').
3444 7894 Listening has not been started on the endpoint '%.*ls' found in metadata. Endpoint operations are disabled on this edition of SQL Server.
3445 7895 Only a system administrator can specify a custom WSDL stored procedure on the endpoint.
3446 7896 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.
3447 7897 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.
3448 7898 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.
3449 7899 The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier.
3450 7901 The repair statement was not processed. This level of repair is not supported when the database is in emergency mode.
3451 7903 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.
3452 7904 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.
3453 7905 Database error: The directory "%.*ls" is not a valid FILESTREAM directory.
3454 7906 Database error: The file "%.*ls" is not a valid FILESTREAM file.
3455 7907 Table error: The directory "%.*ls" under the rowset directory ID %.*ls is not a valid FILESTREAM directory.
3456 7908 Table error: The file "%.*ls" in the rowset directory ID %.*ls is not a valid FILESTREAM file.
3457 7909 The emergency-mode repair failed.You must restore from backup.
3458 7910 Repair: The page %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
3459 7911 Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
3460 7912 Repair: The extent %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
3461 7913 Repair: The extent %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
3462 7914 Repair: %ls page at %S_PGID has been rebuilt.
3463 7915 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.
3464 7916 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.
3465 7917 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.
3466 7918 Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
3467 7919 Repair statement not processed. Database needs to be in single user mode.
3468 7920 Processed %ld entries in system catalog for database ID %d.
3469 7921 Repair statement not processed. Database cannot be a snapshot.
3470 7922 ***************************************************************
3471 7923 Table %.*ls Object ID %ld.
3472 7924 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d.
3473 7925 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents.
3474 7926 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.
3475 7927 Total number of extents is %I64d.
3476 7928 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.
3477 7929 Check statement aborted. Database contains deferred transactions.
3478 7930 Mirroring must be removed from the database for this DBCC command.
3479 7931 Database error: The FILESTREAM directory ID %.*ls for a partition was seen two times.
3480 7932 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.
3481 7933 Table error: A FILESTREAM directory ID %.*ls exists for a partition, but the corresponding partition does not exist in the database.
3482 7934 Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d was not found.
3483 7935 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.
3484 7936 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.
3485 7937 Table error: The FILESTREAM directory ID %.*ls for column ID %d of object ID %d, index ID %d, partition ID %I64d was not found.
3486 7938 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).
3487 7939 Cannot detach database '%.*ls' because it does not exist.
3488 7940 System databases master, model, msdb, and tempdb cannot be detached.
3489 7941 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).
3490 7942 DBCC %ls scanning '%.*ls' table...
3491 7943 Table: '%.*ls' (%d); index ID: %d, database ID: %d
3492 7944 %ls level scan performed.
3493 7945 - Pages Scanned................................: %I64d
3494 7946 - Extents Scanned..............................: %I64d
3495 7947 - Extent Switches..............................: %I64d
3496 7948 - Avg. Pages per Extent........................: %3.1f
3497 7949 - Scan Density [Best Count:Actual Count].......: %4.2f%ls [%I64d:%I64d]
3498 7950 - Logical Scan Fragmentation ..................: %4.2f%ls
3499 7951 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.
3500 7952 - Extent Scan Fragmentation ...................: %4.2f%ls
3501 7953 - Avg. Bytes Free per Page.....................: %3.1f
3502 7954 - Avg. Page Density (full).....................: %4.2f%ls
3503 7955 Invalid SPID %d specified.
3504 7957 Cannot display the specified SPID's buffer; in transition.
3505 7958 The specified SPID does not process input/output data streams.
3506 7960 An invalid server process identifier (SPID) %d or batch ID %d was specified.
3507 7961 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
3508 7962 Invalid BATCHID %d specified.
3509 7963 Database error: The file "%.*ls" is not a valid FILESTREAM LOG file.
3510 7964 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.
3511 7965 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).
3512 7966 Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped.
3513 7968 Transaction information for database '%.*ls'.
3514 7969 No active open transactions.
3515 7970 %hsOldest active transaction:
3516 7971 SPID (server process ID): %d%s
3517 7972 UID (user ID) : %d
3518 7974 Name : %.*ls
3519 7975 LSN : (%d:%d:%d)
3520 7977 Start time : %.*ls
3521 7978 SID : %.*ls
3522 7979 %hsReplicated Transaction Information:
3523 7980 Oldest distributed LSN : (%d:%d:%d)
3524 7982 Oldest non-distributed LSN : (%d:%d:%d)
3525 7983 User '%.*ls' does not have permission to run DBCC %ls for database '%.*ls'.
3526 7984 System table pre-checks: Object ID %d. Page %S_PGID has unexpected page type %d. Check statement terminated due to unrepairable error.
3527 7985 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.
3528 7986 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.
3529 7987 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.
3530 7988 System table pre-checks: Object ID %d. Loop in data chain detected at %S_PGID. Check statement terminated due to unrepairable error.
3531 7992 Cannot shrink 'read only' database '%.*ls'.
3532 7993 Cannot shrink file '%d' in database '%.*ls' to %u pages as it only contains %u pages.
3533 7995 Database '%.*ls': consistency errors in system catalogs prevent further DBCC %ls processing.
3534 7996 Extended stored procedures can only be created in the master database.
3535 7997 '%.*ls' does not contain an identity column.
3536 7998 Checking identity information: current identity value '%.*hs', current column value '%.*hs'.
3537 7999 Could not find any index named '%.*ls' for table '%.*ls'.
3538 8001 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter.
3539 8002 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.
3540 8003 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.
3541 8004 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. The RPC name is invalid.
3542 8005 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter name is invalid.
3543 8006 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter status flags are invalid.
3544 8007 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.
3545 8008 The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%d).
3546 8009 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is unknown.
3547 8010 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.
3548 8011 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.
3549 8012 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.
3550 8013 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.
3551 8014 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.
3552 8015 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.
3553 8016 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.
3554 8017 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.
3555 8018 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.
3556 8019 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.
3557 8020 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.
3558 8021 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.
3559 8022 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.
3560 8023 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.
3561 8024 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.
3562 8025 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.
3563 8026 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.
3564 8027 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.
3565 8028 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.
3566 8029 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.
3567 8030 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.
3568 8031 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.
3569 8032 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.
3570 8033 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.
3571 8034 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.
3572 8035 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.
3573 8036 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.
3574 8037 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.
3575 8038 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.
3576 8039 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.
3577 8040 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.
3578 8041 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.
3579 8042 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.
3580 8043 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.
3581 8044 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.
3582 8045 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.
3583 8046 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.
3584 8047 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.
3585 8048 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.
3586 8049 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.
3587 8050 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.
3588 8051 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.
3589 8052 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.
3590 8053 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.
3591 8054 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.
3592 8055 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.
3593 8056 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.
3594 8057 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.
3595 8058 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.
3596 8059 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.
3597 8060 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.
3598 8061 The data for table-valued parameter "%.*ls" doesn't conform to the table type of the parameter.
3599 8062 The data for the table-valued parameter %d doesn't conform to the table type of the parameter.
3600 8063 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.
3601 8064 Parameter %d ([%.*ls].[%.*ls].[%.*ls]): The CLR type does not exist or you do not have permissions to access it.
3602 8101 An explicit value for the identity column in table '%.*ls' can only be specified when a column list is used and IDENTITY_INSERT is ON.
3603 8102 Cannot update identity column '%.*ls'.
3604 8105 '%.*ls' is not a user table. Cannot perform SET operation.
3605 8106 Table '%.*ls' does not have the identity property. Cannot perform SET operation.
3606 8107 IDENTITY_INSERT is already ON for table '%.*ls.%.*ls.%.*ls'. Cannot perform SET operation for table '%.*ls'.
3607 8108 Cannot add identity column, using the SELECT INTO statement, to table '%.*ls', which already has column '%.*ls' that inherits the identity property.
3608 8109 Attempting to add multiple identity columns to table '%.*ls' using the SELECT INTO statement.
3609 8110 Cannot add multiple PRIMARY KEY constraints to table '%.*ls'.
3610 8111 Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'.
3611 8112 Cannot add more than one clustered index for constraints on table '%.*ls'.
3612 8113 Incorrect use of the XML data type method '%.*ls'. A mutator method is expected in this context.
3613 8114 Error converting data type %ls to %ls.
3614 8115 Arithmetic overflow error converting %ls to data type %ls.
3615 8116 Argument data type %ls is invalid for argument %d of %ls function.
3616 8117 Operand data type %ls is invalid for %ls operator.
3617 8118 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause.
3618 8119 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause.
3619 8120 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.
3620 8121 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause.
3621 8123 A correlated expression is invalid because it is not in a GROUP BY clause.
3622 8124 Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression.
3623 8125 An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated.
3624 8126 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.
3625 8127 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.
3626 8128 Using '%s' version '%s' to execute extended stored procedure '%s'. This is an informational message only; no user action is required.
3627 8129 The new disk size must be greater than %d. Consider using DBCC SHRINKDB.
3628 8131 Extended stored procedure DLL '%s' does not export __GetXpVersion(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Services" in the documentation for more information.
3629 8132 Extended stored procedure DLL '%s' reports its version is %d.%d. The expected version is %d.%d.
3630 8133 None of the result expressions in a CASE specification can be NULL.
3631 8134 Divide by zero error encountered.
3632 8135 Table level constraint does not specify column list, table '%.*ls'.
3633 8136 Duplicate columns specified in %ls constraint key list, table '%.*ls'.
3634 8137 Incorrect use of the XML data type method '%.*ls'. A non-mutator method is expected in this context.
3635 8138 More than 16 columns specified in foreign key column list, table '%.*ls'.
3636 8139 Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'.
3637 8140 More than one key specified in column level %ls constraint, table '%.*ls'.
3638 8141 Column %ls constraint for column '%.*ls' references another column, table '%.*ls'.
3639 8143 Parameter '%.*ls' was supplied multiple times.
3640 8144 Procedure or function %.*ls has too many arguments specified.
3641 8145 %.*ls is not a parameter for procedure %.*ls.
3642 8146 Procedure %.*ls has no parameters and arguments were supplied.
3643 8147 Could not create IDENTITY attribute on nullable column '%.*ls', table '%.*ls'.
3644 8148 More than one column %ls constraint specified for column '%.*ls', table '%.*ls'.
3645 8149 OLE Automation objects are not supported in fiber mode.
3646 8150 Multiple NULL constraints were specified for column '%.*ls', table '%.*ls'.
3647 8151 Both a PRIMARY KEY and UNIQUE constraint have been defined for column '%.*ls', table '%.*ls'. Only one is allowed.
3648 8152 String or binary data would be truncated.
3649 8153 Warning: Null value is eliminated by an aggregate or other SET operation.
3650 8154 The table '%.*ls' is ambiguous.
3651 8155 No column name was specified for column %d of '%.*ls'.
3652 8156 The column '%.*ls' was specified multiple times for '%.*ls'.
3653 8158 '%.*ls' has more columns than were specified in the column list.
3654 8159 '%.*ls' has fewer columns than were specified in the column list.
3655 8160 A GROUPING or GROUPING_ID function can only be specified when there is a GROUP BY clause.
3656 8161 Argument %d of the %.*ls function does not match any of the expressions in the GROUP BY clause.
3657 8162 The formal parameter "%.*ls" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output.
3658 8164 An INSERT EXEC statement cannot be nested.
3659 8165 Invalid subcommand value %d. Legal range from %d to %d.
3660 8166 Constraint name '%.*ls' not permitted. Constraint names cannot begin with a number sign (#).
3661 8167 The type of column "%.*ls" conflicts with the type of other columns specified in the UNPIVOT list.
3662 8168 Cannot create, drop, enable, or disable more than one constraint, column, or trigger named '%.*ls' in this context. Duplicate names are not allowed.
3663 8169 Conversion failed when converting from a character string to uniqueidentifier.
3664 8170 Insufficient result space to convert uniqueidentifier value to char.
3665 8171 Hint '%ls' on object '%.*ls' is invalid.
3666 8172 The argument %d of the XML data type method "%.*ls" must be a string literal.
3667 8173 Incorrect syntax was used to invoke the XML data type method '%.*ls'.
3668 8174 Schema lock with handle %d not found.
3669 8175 Could not find table %.*ls. Will try to resolve this table name later.
3670 8176 Resync procedure expects value of key '%.*ls', which was not supplied.
3671 8177 Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause.
3672 8178 The parameterized query '%.*ls' expects the parameter '%.*ls', which was not supplied.
3673 8179 Could not find prepared statement with handle %d.
3674 8180 Statement(s) could not be prepared.
3675 8181 Text for '%.*ls' is missing from the system catalog. The object must be dropped and re-created before it can be used.
3676 8183 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.
3677 8184 Error in binarychecksum. There are no comparable columns in the binarychecksum input.
3678 8185 Error expanding "*": An incomparable column has been found in an underlying table or view.
3679 8186 Function '%.*ls' can be used only on user and system tables.
3680 8187 The prepared handle %d is currently being used by another command (error state: %d).
3681 8188 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.
3682 8189 You do not have permission to run '%ls'.
3683 8190 Cannot compile replication filter procedure without defining table being filtered.
3684 8191 Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements.
3685 8192 Replication filter procedures cannot have parameters.
3686 8193 Cannot execute a procedure marked FOR REPLICATION.
3687 8195 Cannot create "%.*ls" on "%.*ls". Insert, Update, and Delete triggers can only be created on user tables and views.
3688 8196 Duplicate column specified as ROWGUIDCOL.
3689 8197 The object '%.*ls' does not exist or is invalid for this operation.
3690 8199 In EXECUTE , procname can only be a literal or variable of type char, varchar, nchar, or nvarchar.
3691 8301 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.
3692 8302 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.
3693 8303 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.
3694 8304 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.
3695 8305 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.
3696 8306 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.
3697 8307 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.
3698 8308 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.
3699 8310 Cannot create (or open) named file mapping object '%ls'. SQL Server performance counters are disabled.
3700 8311 Unable to map view of file mapping object '%ls' into SQL Server process address space. SQL Server performance counters are disabled.
3701 8312 Cannot create (or open) named mutex '%ls'. SQL Server performance counters are disabled.
3702 8313 Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
3703 8314 SQL Server performance object '%ls' not found in registry. SQL Server performance counters are disabled.
3704 8315 SQL Server performance counter '%ls' not found in registry. SQL Server performance counters are disabled.
3705 8316 Cannot open registry key 'HKLM\%ls'. SQL Server performance counters are disabled.
3706 8317 Cannot query value '%ls' associated with registry key 'HKLM\%ls'. SQL Server performance counters are disabled.
3707 8318 There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters are disabled.
3708 8319 Windows kernel object '%ls' already exists. It's not owned by the SQL Server service account. SQL Server performance counters are disabled.
3709 8320 @@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.
3710 8350 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.
3711 8351 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.
3712 8352 Cannot find the requested trace template: id = %ls.
3713 8353 Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server.
3714 8354 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.
3715 8355 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.
3716 8356 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.
3717 8357 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.
3718 8358 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.
3719 8359 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.
3720 8360 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.
3721 8379 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.
3722 8380 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server '%.*ls'.
3723 8381 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) for ad hoc connection to SQL Server.
3724 8382 Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version.
3725 8383 Specifying HOLDLOCK as a table hint without parentheses is a deprecated feature and will be removed in the next version of SQL Server.
3726 8384 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.
3727 8385 The select list of an aggregate indexed view must contain count_big(*) in 90 compatibility mode and higher.
3728 8386 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.
3729 8387 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.
3730 8388 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.
3731 8389 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.
3732 8390 The '::' function calling syntax will be removed in a future version of SQL Server. Replace it with "sys.".
3733 8391 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> }
3734 8393 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.
3735 8394 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.
3736 8396 %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.
3737 8397 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.
3738 8398 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.
3739 8399 %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.
3740 8401 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'.
3741 8402 The data type of the '%S_MSG' in the '%S_MSG' statement must be %s. The %s data type is not allowed.
3742 8403 The message type '%.*ls' is specified more than once. Remove the duplicate message type.
3743 8404 The service contract '%.*ls' is specified more than once. Remove the duplicate service contract.
3744 8405 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.
3745 8406 The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d.
3746 8407 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.
3747 8408 Target service '%.*ls' does not support contract '%.*ls'.
3748 8409 This message could not be delivered because the targeted service does not support the service contract. Targeted service: '%.*ls', service contract: '%.*ls'.
3749 8410 The conversation timer cannot be set beyond the conversation's lifetime.
3750 8411 The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.
3751 8412 The syntax of the service name '%.*ls' is invalid.
3752 8413 The syntax of the broker instance '%.*ls' is invalid. The specified broker instance is too long, the maximum size is 256 bytes.
3753 8414 The conversation group ID '%.*ls' is invalid in this context. Specify a different conversion group ID.
3754 8415 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.
3755 8417 The service contract name is NULL. Specify a service contract name.
3756 8418 The conversation handle is missing. Specify a conversation handle.
3757 8419 Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL.
3758 8420 The conversation group is missing. Specify a conversation group.
3759 8421 The service name is missing. Specify a service name.
3760 8422 The error description is missing. Specify a description of the error.
3761 8423 The service "%.*ls" is not found.
3762 8424 The error code and error description are missing. Specify both the error code and description of the error.
3763 8425 The service contract '%.*ls' is not found.
3764 8426 The conversation handle "%.*ls" is not found.
3765 8427 The conversation endpoint is not in a valid state for END CONVERSATION. The current endpoint state is '%ls'.
3766 8428 The message type "%.*ls" is not found.
3767 8429 The conversation endpoint is not in a valid state for SEND. The current endpoint state is '%ls'.
3768 8430 The message body failed the configured validation.
3769 8431 The message type '%.*ls' is not part of the service contract.
3770 8432 The message cannot be sent because the message type '%.*ls' is marked SENT BY TARGET in the contract, however this service is an Initiator.
3771 8433 The message body may not be NULL. A zero-length UNICODE or binary string is allowed.
3772 8434 The message cannot be sent because the message type '%.*ls' is marked SENT BY INTITIATOR in the contract, however this service is a Target.
3773 8436 The conversation group "%.*ls" is not found.
3774 8437 The message received was sent by a Target service, but the message type '%.*ls' is marked SENT BY INITIATOR in the contract.
3775 8438 The conversation endpoint is not in a valid state for MOVE CONVERSATION. The current endpoint state is '%ls'.
3776 8439 The destination conversation group '%.*ls' is invalid.
3777 8440 The conversation group exists, but no queue exists. Possible database corruption. Run DBCC CHECKDB.
3778 8442 There is no Service Broker active in the database. Change to a database context that contains a Service Broker.
3779 8443 The conversation with ID '%.*ls' and initiator: %d references a missing conversation group '%.*ls'. Run DBCC CHECKDB to analyze and repair the database.
3780 8444 The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB.
3781 8445 The conversation handle '%ls' is referencing an invalid conversation ID '%ls', initiator: %d.
3782 8447 A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations.
3783 8450 Assignments in the RECEIVE projection are not allowed in conjunction with the INTO clause.
3784 8457 The message received was sent by the initiator of the conversation, but the message type '%.*ls' is marked SENT BY TARGET in the contract.
3785 8458 The conversation endpoint is not in a valid state for BEGIN CONVERSATION TIMER. The current endpoint state is '%ls'.
3786 8459 The message size, including header information, exceeds the maximum allowed of %d.
3787 8460 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation handle '%ls'.
3788 8461 An internal service broker error detected. Possible database corruption. Run DBCC CHECKDB.
3789 8462 The remote conversation endpoint is either in a state where no more messages can be exchanged, or it has been dropped.
3790 8463 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.
3791 8468 Underlying service has been altered.
3792 8469 Remote service has been altered.
3793 8470 Remote service has been dropped.
3794 8471 An SNI call failed during a Service Broker/Database Mirroring transport operation. SNI error '%ls'.
3795 8472 The remote service has sent a message that contains invalid header fields.
3796 8475 The conversation endpoint with ID '%ls' and is_initiator: %d has been dropped.
3797 8477 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.
3798 8479 Used by test in failpoint simulation.
3799 8487 The remote service contract has been dropped.
3800 8489 The dialog has exceeded the specified LIFETIME.
3801 8490 Cannot find the remote service '%.*ls' because it does not exist.
3802 8492 The service contract '%.*ls' must have at least one message SENT BY INITIATOR or ANY.
3803 8493 The alter of service '%.*ls' must change the queue or at least one contract.
3804 8494 You do not have permission to access the service '%.*ls'.
3805 8495 The conversation has already been acknowledged by another instance of this service.
3806 8498 The remote service has sent a message of type '%.*ls' that is not part of the local contract.
3807 8499 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.
3808 8501 MSDTC on server '%.*ls' is unavailable.
3809 8502 Unknown token '0x%x' received from Microsoft Distributed Transaction Coordinator (MS DTC) .
3810 8504 The import buffer for this transaction is not valid.
3811 8506 Cannot change transaction state from %hs to %hs. The change requested is not valid.
3812 8508 QueryInterface failed for "%ls": %ls.
3813 8509 Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls.
3814 8510 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.
3815 8511 Unknown isolation level 0x%x requested from Microsoft Distributed Transaction Coordinator (MS DTC).
3816 8512 Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs.
3817 8513 Microsoft Distributed Transaction Coordinator (MS DTC) end transaction acknowledgement failed: %hs.
3818 8514 Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs.
3819 8515 Microsoft Distributed Transaction Coordinator (MS DTC) global state is not valid.
3820 8517 Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls.
3821 8518 Microsoft Distributed Transaction Coordinator (MS DTC) BEGIN TRANSACTION failed: %ls.
3822 8519 Current Microsoft Distributed Transaction Coordinator (MS DTC) transaction must be committed by remote client.
3823 8520 Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: %ls.
3824 8521 This awakening state is not valid: slept in %hs; awoke in %hs.
3825 8522 Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
3826 8523 PREPARE TRAN statement not allowed on MSDTC transaction.
3827 8524 The current transaction could not be exported to the remote provider. It has been rolled back.
3828 8525 Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
3829 8526 Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint.
3830 8527 An attempt to create a distributed transaction export token failed with this error: %ls. Contact your Microsoft Distributed Transaction Coordinator (MS DTC) system administrator.
3831 8528 The commit of the Kernel Transaction Manager (KTM) transaction failed: %d.
3832 8529 Unable to extract the Kernel Transaction Manager (KTM) transaction handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transaction: 0x%x.
3833 8530 The Windows kernel transaction manager creation failed: 0x%x.
3834 8531 The Windows kernel transaction manager failed to create the enlistment: 0x%08x.
3835 8532 Error while reading resource manager notification from Kernel Transaction Manager (KTM): %d.
3836 8533 Error while waiting for communication from Kernel Transaction Manager (KTM): %d.
3837 8534 The KTM RM for this database, %ls, failed to start: %d.
3838 8535 A savepoint operation in the Windows transactional file system failed: 0x%x.
3839 8536 Only single DB updates are allowed with FILESTREAM operations.
3840 8537 This transaction was aborted by Kernel Transaction Manager (KTM).
3841 8538 The current isolation level is not supported by the FILESTREAM 0x%x.
3842 8539 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.
3843 8540 The distributed transaction with UOW %ls was forced to rollback.
3844 8541 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.
3845 8542 Spid %d tried to commit the distributed transaction with UOW %ls.
3846 8543 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.
3847 8544 Unknown status of commit of a two-phase commit transaction. Shutting down server. Restart server to complete recovery.
3848 8545 Unknown status '%d' from Reenlist call in rm_resolve.
3849 8546 Unable to load Microsoft Distributed Transaction Coordinator (MS DTC) library. This error indicates that MS DTC is not installed. Install MS DTC to proceed.
3850 8547 Resource Manager Creation Failed: %ls
3851 8548 DTC not initialized because it's unavailable
3852 8549 GetWhereaboutsSize call failed: %ls
3853 8550 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.
3854 8551 CoCreateGuid failed: %ls.
3855 8552 RegOpenKeyEx of \"%ls\" failed: %ls.
3856 8553 RegQueryValueEx of \"%hs\" failed: %ls.
3857 8554 IIDFromString failed for %hs, (%ls).
3858 8555 RegCloseKey failed: %ls
3859 8556 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.
3860 8557 The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
3861 8558 RegDeleteValue of \"%hs\" failed: %ls.
3862 8560 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.
3863 8561 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.
3864 8562 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.
3865 8563 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.
3866 8565 SQL Server failed to prepare DTC transaction. Failure code: %d.
3867 8601 Internal Query Processor Error: The query processor could not obtain access to a required interface.
3868 8602 Indexes used in hints must be explicitly included by the index tuning wizard.
3869 8603 Invalid syntax for internal DBCC REPAIR statement.
3870 8604 ALTER TABLE SWITCH statement failed. Table '%.*ls' has a column level check constraint '%.*ls' on column '%.*ls' that is not loadable for semantic validation.
3871 8605 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.
3872 8606 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.
3873 8607 The table '%.*ls' cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online.
3874 8608 The query could not be completed due to an online index build operation and must be recompiled.
3875 8616 The index hints for table '%.*ls' were ignored because the table was considered a fact table in the star join.
3876 8618 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.
3877 8619 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.
3878 8621 The query processor ran out of stack space during query optimization. Please simplify the query.
3879 8622 Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
3880 8623 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.
3881 8624 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
3882 8625 Warning: The join order has been enforced because a local join hint is used.
3883 8628 A time out occurred while waiting to optimize the query. Rerun the query.
3884 8630 Internal Query Processor Error: The query processor encountered an unexpected error during execution.
3885 8631 Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it.
3886 8632 Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
3887 8633 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.
3888 8634 The query processor received an error from a cluster communication layer.
3889 8635 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.
3890 8636 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.
3891 8637 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.
3892 8642 The query processor could not start the necessary thread resources for parallel query execution.
3893 8644 Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine.
3894 8645 A timeout occurred while waiting for memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query.
3895 8646 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.
3896 8648 Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint.
3897 8649 The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator.
3898 8651 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.
3899 8653 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.
3900 8655 The query processor is unable to produce a plan because the index '%.*ls' on table or view '%.*ls' is disabled.
3901 8656 The query processor could not produce a query plan. Resubmit the query after disabling trace flag %d.
3902 8657 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.
3903 8660 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.
3904 8661 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.
3905 8662 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.
3906 8663 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.
3907 8665 Cannot create the clustered index "%.*ls" on view "%.*ls" because no row can satisfy the view definition. Consider eliminating contradictions from the view definition.
3908 8668 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.
3909 8669 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.
3910 8670 Query optimizer reached the internal limit of the maximum number of views that can be used during optimization.
3911 8671 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.
3912 8672 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.
3913 8673 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.
3914 8680 Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase.
3915 8682 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.
3916 8683 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.
3917 8684 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.
3918 8685 Query cannot be compiled because 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.
3919 8686 Cursor plan forcing failed because input plan has more than one node with OperationType=%ls. Consider using an XML cursor plan captured from SQL Server without modification.
3920 8687 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.
3921 8688 Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %ls is missing under element. Consider using an XML cursor plan captured from SQL Server without modification.
3922 8689 Database '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing database.
3923 8690 Query cannot be compiled because USE PLAN hint conflicts with hint %ls. Consider removing hint %ls.
3924 8691 Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF.
3925 8693 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.
3926 8694 Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint.
3927 8695 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.
3928 8696 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.
3929 8697 Cannot run query because in XML plan provided to USE PLAN, element %ls must have %d %ls nodes as children, but has %d.
3930 8698 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.
3931 8699 Cannot run query because it contains more than one USE PLAN hint. Use at most one USE PLAN hint.
3932 8710 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.
3933 8711 Multiple ordered aggregate functions in the same scope have mutually incompatible orderings.
3934 8712 Index '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified name.
3935 8720 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.
3936 8721 Cannot execute query. TABLE HINT in the OPTION clause leads to ambiguous reference for object '%.*ls'. Consider USE PLAN query hint instead.
3937 8722 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.
3938 8723 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.
3939 8724 Cannot execute query. Table-valued or OPENROWSET function '%.*ls' cannot be specified in the TABLE HINT clause.
3940 8901 Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object.
3941 8902 Memory allocation error during DBCC processing.
3942 8903 Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID.
3943 8904 Extent %S_PGID in database ID %d is allocated by more than one allocation object.
3944 8905 Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it.
3945 8906 Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags '%hs'.
3946 8907 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.
3947 8908 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.
3948 8909 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.
3949 8910 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).
3950 8911 The error has been repaired.
3951 8912 %.*ls fixed %d allocation errors and %d consistency errors in database '%ls'.
3952 8913 Extent %S_PGID is allocated to '%ls' and at least one other object.
3953 8914 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.
3954 8915 File %d (number of mixed extents = %I64d, mixed pages = %I64d).
3955 8916 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), data extents %I64d, pages %I64d, mixed extent pages %I64d.
3956 8917 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d.
3957 8918 (number of mixed extents = %I64d, mixed pages = %I64d) in this database.
3958 8919 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.
3959 8920 Cannot perform a %ls operation inside a user transaction. Terminate the transaction and reissue the statement.
3960 8921 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
3961 8922 Could not repair this error.
3962 8923 The repair level on the DBCC statement caused this repair to be bypassed.
3963 8924 Repairing this error requires other errors to be corrected first.
3964 8925 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).
3965 8926 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.
3966 8927 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.
3967 8928 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.
3968 8929 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
3969 8930 Database error: Database %d has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. Please restore from a backup.
3970 8931 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.
3971 8932 Could not find filegroup ID %d in sys.filegroups for database '%ls'.
3972 8933 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.
3973 8934 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.
3974 8935 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.
3975 8936 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.
3976 8937 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.
3977 8938 Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
3978 8939 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.
3979 8940 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.
3980 8941 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.
3981 8942 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.
3982 8943 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.
3983 8944 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.
3984 8945 Table error: Object ID %d, index ID %d will be rebuilt.
3985 8946 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.
3986 8947 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.
3987 8948 Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
3988 8949 %.*ls fixed %d allocation errors and %d consistency errors in table '%ls' (object ID %d).
3989 8950 %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
3990 8951 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:
3991 8952 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:
3992 8953 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.
3993 8954 %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
3994 8955 Data row (%d:%d:%d) identified by (%ls) with index values '%ls'.
3995 8956 Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
3996 8957 %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
3997 8958 %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
3998 8959 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.
3999 8960 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.
4000 8961 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.
4001 8962 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.
4002 8963 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.
4003 8964 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.
4004 8965 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.
4005 8966 Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
4006 8967 An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
4007 8968 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.
4008 8969 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.
4009 8970 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.
4010 8971 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
4011 8972 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.
4012 8973 CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.
4013 8974 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.
4014 8975 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.
4015 8976 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.
4016 8977 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.
4017 8978 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.
4018 8979 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.
4019 8980 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.
4020 8981 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.
4021 8982 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.
4022 8983 File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
4023 8984 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:
4024 8985 Could not locate file '%.*ls' for database '%.*ls' in sys.database_files. The file either does not exist, or was dropped.
4025 8986 Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
4026 8987 No help available for DBCC statement '%.*ls'.
4027 8988 Row (%d:%d:%d) identified by (%ls).
4028 8989 %.*ls found %d allocation errors and %d consistency errors in database '%ls'.
4029 8990 %.*ls found %d allocation errors and %d consistency errors in table '%ls' (object ID %d).
4030 8991 0x%p to 0x%p is not a valid address range.
4031 8992 Check Catalog Msg %d, State %d: %.*ls
4032 8993 Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
4033 8994 Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.
4034 8995 System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d.
4035 8996 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.
4036 8997 Service Broker Msg %d, State %d: %.*ls
4037 8998 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.
4038 8999 Database tempdb allocation errors prevent further %ls processing.
4039 9001 The log for database '%.*ls' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
4040 9002 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
4041 9003 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.
4042 9004 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.
4043 9005 Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid.
4044 9006 Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d.
4045 9007 Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file.
4046 9008 Cannot shrink log file %d (%s) because the logical log file located at the end of the file is in use.
4047 9009 Cannot shrink log file %d (%s) because of minimum log space required.
4048 9010 User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission
4049 9011 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
4050 9012 There have been %d misaligned log IOs which required falling back to synchronous IO. The current IO is on file %ls.
4051 9013 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.
4052 9014 An error occurred while processing the log for database '%.*ls'. THe log block version is higher than this server allows.
4053 9015 The log record at LSN %S_LSN is corrupted.
4054 9016 An error occurred while processing the log for database '%.*ls'. The log block could not be decrypted.
4055 9100 Possible index corruption detected. Run DBCC CHECKDB.
4056 9101 auto statistics internal
4057 9104 auto statistics internal
4058 9105 The provided statistics stream is corrupt.
4059 9106 Histogram support not allowed for input data type 0x%08x.
4060 9201 %d active query notification subscription(s) in database '%.*ls' owned by security identification number '%.*ls' were dropped.
4061 9202 The query notification subscription message is invalid.
4062 9204 The query notification subscription timeout is invalid. The allowed range is 1 through 2147483647.
4063 9205 User "%.*ls" does not have permission to request query notification subscriptions on database "%.*ls".
4064 9206 The query notification subscription "%ld" cannot be deleted because it does not exist or it has already been fired.
4065 9207 The query notification dialog on conversation handle '%.*ls' closed due to the following error: '%.*ls'.
4066 9208 Query notification subscription could not get dialog endpoint. Could not open service broker dialog for service name '%.*ls' of broker instance '%.*ls'.
4067 9209 Query notification subscription could not begin dialog with service name '%.*ls' of broker instance '%.*ls'.
4068 9210 Query notification delivery could not send message on dialog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker: '%.*ls'.
4069 9211 Failed to check for pending query notifications in database "%d" because of the following error when opening the database: '%.*ls'.
4070 9213 Query notification subscription could not access database with id %d. Could not open broker dialog for service name '%.*ls' of broker instance '%.*ls'.
4071 9214 The query notification delivery failed to decode the error message from the Service Broker.
4072 9215 Query notification delivery failed to encode message. Delivery failed for notification '%.*ls'.
4073 9216 Failed to delete the expired query notification subscription "%d".
4074 9217 Failed to drop the unused internal query notification table "%d" in database "%d".
4075 9218 Query notifications reached the internal limit of the maximum number of objects.
4076 9219 The query notification subscriptions cleanup operation failed. See previous errors for details.
4077 9220 Query notification dialog on conversation handle '%.*ls' closed due to an unknown service broker error.
4078 9221 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'.
4079 9222 Internal query notification table has an outdated schema and the table has been dropped. Query notification cleanup has not been performed for this table.
4080 9223 %d active query notification subscription(s) owned by security identification number '%.*ls' were dropped.
4081 9224 Query notification delivery could not access database with id %d. Delivery failed for notification '%.*ls'.
4082 9225 The notification options identifier string has %d characters. The maximum allowed length is %d characters.
4083 9226 A string value within the notification options identifier is too long. String with prefix '%.*ls' must be %d characters or less.
4084 9227 Unmatched quote in notification options identifier string.
4085 9228 Name expected in notification options identifier option.
4086 9229 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.
4087 9230 Option '%ls' was specified multiple times in the notification options identifier.
4088 9231 An equal (=) character was expected after the option name. Found '%.*ls' instead.
4089 9232 A semicolon (;) must be use to separate options in a notification options identifier. String '%.*ls' was found following an option.
4090 9233 The option 'Service' must be specified in the notification options identifier.
4091 9234 The options 'Broker Instance' and 'Local Database' were both specified in the notification options identifier.
4092 9235 Value missing for option '%ls' in notification options identifier.
4093 9236 Database %.*ls is not a valid local database.
4094 9237 Database %.*ls is not a valid broker database.
4095 9238 Query notification subscriptions are not allowed under an active application role context. Consider re-issuing the request without activating the application role.
4096 9239 Internal query notifications error: The garbage collector corrected an inconsistency.
4097 9240 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'.
4098 9241 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.
4099 9242 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.
4100 9243 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.
4101 9244 Query notification cleanup could not access metadata for database "%d". Check whether the database is successfully restored and online.
4102 9300 %sIn this version of the server, the 'fn:id()' function only accepts an argument of type 'IDREF *'.
4103 9301 %sIn this version of the server, 'cast as %s' is not available. Please use the 'cast as ?' syntax.
4104 9302 %sThe context item in which the 'fn:id()' function is used must be a node.
4105 9303 %sSyntax error near '%ls', expected '%ls'.
4106 9304 %sThis version of the server only supports XQuery version '1.0'.
4107 9305 %sOnly type names followed by '?' are supported in the target of 'instance of'.
4108 9306 %sThe target of 'replace value of' cannot be a union type, found '%ls'.
4109 9308 %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'.
4110 9309 %sThe target of 'replace value of' cannot be 'http://www.w3.org/2001/XMLSchema#anySimpleType', found '%ls'.
4111 9310 %sThe 'with' clause of 'replace value of' cannot contain constructed XML.
4112 9311 %sHeterogeneous sequences are not allowed in '%ls', found '%ls' and '%ls'.
4113 9312 %s'%ls' is not supported on simple typed or 'http://www.w3.org/2001/XMLSchema#anyType' elements, found '%ls'.
4114 9313 %sThis version of the server does not support multiple expressions or expressions mixed with strings in an attribute constructor.
4115 9314 %sCannot implicitly atomize or apply 'fn:data()' to complex content elements, found type '%ls' within inferred type '%ls'.
4116 9315 %sOnly constant expressions are supported for the name expression of computed element and attribute constructors.
4117 9316 %sCannot use 'xmlns' in the name expression of computed attribute constructor.
4118 9317 %sSyntax error near '%ls', expected string literal.
4119 9318 %sSyntax error at source character '0x%02x' near '%ls', expected string literal.
4120 9319 %sStatic simple type validation: Invalid simple type value '%ls'.
4121 9320 %sThe result of applying the 'parent' axis on the document node is statically 'empty'.
4122 9321 %sThe result of applying 'parent::%ls' is statically 'empty'.
4123 9322 %sTwo consecutive '-' can only appear in a comment constructor if they are used to close the comment ('-->').
4124 9323 %sUsing ':' in variable names is not supported in this version of the server.
4125 9324 %sFound '}' without matching '{'. If you want to use the characters '{' or '}', you need to escape them as '{{' or '}}' respectively.
4126 9325 %sComputed processing instruction constructors are not supported.
4127 9326 %sComputed comment constructors are not supported.
4128 9327 %sAll prolog entries need to end with ';', found '%ls'.
4129 9328 %sType specification expected, found '%ls'.
4130 9330 %sOnly comparable types are allowed in '%ls', found '%ls'.
4131 9331 %sSyntax error near '%ls', expected '%ls' or '%ls'.
4132 9332 %sSyntax error near '%ls', expected 'where', '(stable) order by' or 'return'.
4133 9333 %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'.
4134 9334 %sThe 'form' attribute cannot be specified on a local attribute or element definition that has the 'ref' attribute. Location: '%ls'.
4135 9335 %sThe XQuery syntax '%ls' is not supported.
4136 9336 %sThe XML Schema syntax '%ls' is not supported.
4137 9337 %sThe XML Schema type 'NOTATION' is not supported.
4138 9338 %sThe value of a namespace declaration attribute must be a string literal. It cannot contain expressions.
4139 9339 %sThe 'form' attribute cannot be specified on a global attribute or element definition. Location: '%ls'.
4140 9340 %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.
4141 9341 %sSyntax error near '%ls', expected a step expression.
4142 9342 %sAn XML instance is only supported as the direct source of an insert using sql:column/sql:variable.
4143 9343 %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.
4144 9344 %sThe SQL type '%s' is not supported with sql:column() and sql:variable().
4145 9400 XML parsing: line %d, character %d, unexpected end of input
4146 9401 XML parsing: line %d, character %d, unrecognized encoding
4147 9402 XML parsing: line %d, character %d, unable to switch the encoding
4148 9403 XML parsing: line %d, character %d, unrecognized input signature
4149 9410 XML parsing: line %d, character %d, whitespace expected
4150 9411 XML parsing: line %d, character %d, semicolon expected
4151 9412 XML parsing: line %d, character %d, '>' expected
4152 9413 XML parsing: line %d, character %d, A string literal was expected
4153 9414 XML parsing: line %d, character %d, equal expected
4154 9415 XML parsing: line %d, character %d, well formed check: no '<' in attribute value
4155 9416 XML parsing: line %d, character %d, hexadecimal digit expected
4156 9417 XML parsing: line %d, character %d, decimal digit expected
4157 9418 XML parsing: line %d, character %d, '[' expected
4158 9419 XML parsing: line %d, character %d, '(' expected
4159 9420 XML parsing: line %d, character %d, illegal xml character
4160 9421 XML parsing: line %d, character %d, illegal name character
4161 9422 XML parsing: line %d, character %d, incorrect document syntax
4162 9423 XML parsing: line %d, character %d, incorrect CDATA section syntax
4163 9424 XML parsing: line %d, character %d, incorrect comment syntax
4164 9425 XML parsing: line %d, character %d, incorrect conditional section syntax
4165 9426 XML parsing: line %d, character %d, incorrect ATTLIST declaration syntax
4166 9427 XML parsing: line %d, character %d, incorrect DOCTYPE declaration syntax
4167 9428 XML parsing: line %d, character %d, incorrect ELEMENT declaration syntax
4168 9429 XML parsing: line %d, character %d, incorrect ENTITY declaration syntax
4169 9430 XML parsing: line %d, character %d, incorrect NOTATION declaration syntax
4170 9431 XML parsing: line %d, character %d, NDATA expected
4171 9432 XML parsing: line %d, character %d, PUBLIC expected
4172 9433 XML parsing: line %d, character %d, SYSTEM expected
4173 9434 XML parsing: line %d, character %d, name expected
4174 9435 XML parsing: line %d, character %d, one root element
4175 9436 XML parsing: line %d, character %d, end tag does not match start tag
4176 9437 XML parsing: line %d, character %d, duplicate attribute
4177 9438 XML parsing: line %d, character %d, text/xmldecl not at the beginning of input
4178 9439 XML parsing: line %d, character %d, namespaces beginning with "xml" are reserved
4179 9440 XML parsing: line %d, character %d, incorrect text declaration syntax
4180 9441 XML parsing: line %d, character %d, incorrect xml declaration syntax
4181 9442 XML parsing: line %d, character %d, incorrect encoding name syntax
4182 9443 XML parsing: line %d, character %d, incorrect public identifier syntax
4183 9444 XML parsing: line %d, character %d, well formed check: pes in internal subset
4184 9445 XML parsing: line %d, character %d, well formed check: pes between declarations
4185 9446 XML parsing: line %d, character %d, well formed check: no recursion
4186 9447 XML parsing: line %d, character %d, entity content not well formed
4187 9448 XML parsing: line %d, character %d, well formed check: undeclared entity
4188 9449 XML parsing: line %d, character %d, well formed check: parsed entity
4189 9450 XML parsing: line %d, character %d, well formed check: no external entity references
4190 9451 XML parsing: line %d, character %d, incorrect processing instruction syntax
4191 9452 XML parsing: line %d, character %d, incorrect system identifier syntax
4192 9453 XML parsing: line %d, character %d, '?' expected
4193 9454 XML parsing: line %d, character %d, no ']]>' in element content
4194 9455 XML parsing: line %d, character %d, illegal qualified name character
4195 9456 XML parsing: line %d, character %d, multiple colons in qualified name
4196 9457 XML parsing: line %d, character %d, colon in name
4197 9458 XML parsing: line %d, character %d, redeclared prefix
4198 9459 XML parsing: line %d, character %d, undeclared prefix
4199 9460 XML parsing: line %d, character %d, non default namespace with empty uri
4200 9461 XML %ls starting with '%.*ls' is %d characters long, which exceeds the limit. Maximum allowed length is %d characters.
4201 9462 XML parsing: line %d, character %d, not all chunks of value have been read
4202 9463 XML parsing: line %d, character %d, xml:space has a non-legal value
4203 9464 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.
4204 9465 XML parsing: line %d, character %d, XML namespace prefix 'xmlns' is reserved for use by XML.
4205 9466 XML parsing: line %d, character %d, XML namespace xml namespace URI (http://www.w3.org/XML/1998/namespace) must be assigned only to prefix 'xml'.
4206 9467 XML parsing: line %d, character %d, xmlns namespace URI (http://www.w3.org/2000/xmlns/) is reserved and must not be used.
4207 9480 XML parsing: line %d, character %d, unsupported xml
4208 9500 The data type '%.*ls' used in the VALUE method is invalid.
4209 9501 XQuery: Unable to resolve sql:variable('%.*ls'). The variable must be declared as a scalar TSQL variable.
4210 9502 The string literal provided for the argument %d of the '%.*ls' method must not exceed %d bytes.
4211 9503 Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls'. See previous error messages for more details.
4212 9504 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.
4213 9506 The XMLDT method '%.*ls' can only be invoked on columns of type xml.
4214 9507 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.
4215 9508 The reference parameter given to XMLDT method '%.*ls' was generated from a different XML instance than the one it is being applied to.
4216 9509 XMLUNNEST method requires typed xml column with single global element
4217 9510 Functionality not yet implemented: XMLNODEREFS cannot use references exposed by views.
4218 9512 Xml data type is not supported as a parameter to remote calls.
4219 9513 Error processing XML data type method '%.*ls'. The following SET options required by XML data type methods are not set: '%.*ls'.
4220 9514 Xml data type is not supported in distributed queries. Remote object '%.*ls' has xml column(s).
4221 9515 An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch.
4222 9516 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.
4223 9517 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.
4224 9518 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.
4225 9519 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.
4226 9520 XQuery: '%.*ls' referenced by sql:variable() is not a valid system function name.
4227 9521 Error processing XML data type. The XML data type instance contains a negative xs:date or xs:dateTime value.
4228 9522 The XQuery modify method is not allowed on sparse column sets.
4229 9523 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.
4230 9524 The XML content provided does not conform to the required XML format for sparse column sets.
4231 9525 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.
4232 9526 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.
4233 9527 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.
4234 9528 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.
4235 9529 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".
4236 9530 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.
4237 9531 In the XML content that is supplied for the column set column '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is not valid.
4238 9532 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'.
4239 9533 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.
4240 9534 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.
4241 9601 Cannot relate to %S_MSG %.*ls because it is %S_MSG.
4242 9605 Conversation Priorities analyzed: %d.
4243 9606 The conversation priority with ID %d has been dropped.
4244 9607 The conversation priority with ID %d is referencing the missing service with ID %d.
4245 9608 The conversation priority with ID %d is referencing the missing service contract with ID %d.
4246 9609 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
4247 9610 The service '%.*ls' in the FROM SERVICE clause must match the service '%.*ls' referenced by %s = '%.*ls'.
4248 9611 Cannot find the specified user '%.*ls'.
4249 9613 The queue '%.*ls' cannot be activated because the activation user is not specified.
4250 9614 The queue '%.*ls' cannot be activated because the activation stored procedure is either not specified or is invalid.
4251 9615 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.
4252 9616 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.
4253 9617 The service queue "%.*ls" is currently disabled.
4254 9618 The message cannot be sent because the service queue '%.*ls' associated with the dialog is currently disabled and retention is on.
4255 9619 Failed to create remote service binding '%.*ls'. A remote service binding for service '%.*ls' already exists.
4256 9620 The activation stored procedure '%.*ls' is invalid. Functions are not allowed.
4257 9621 An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i.
4258 9622 The crypto provider context is not initialized.
4259 9623 The key passed in for this operation is in the wrong state.
4260 9624 The key size is unacceptable for this key object.
4261 9625 The key buffer size is inconsistent with the key modulus size.
4262 9626 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.
4263 9627 The hash buffer size is not correct for initializing the hash object.
4264 9628 The encryption/decryption data buffer size is not 8 byte aligned.
4265 9629 The decrypted signature size is wrong.
4266 9630 The signature did not verify the internal hash.
4267 9631 The salt size is unacceptable for this key object.
4268 9632 The salt buffer size is too small.
4269 9633 The passed in name is too long.
4270 9634 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.
4271 9635 The certificate is not valid at this point in time.
4272 9636 The requested object was not found.
4273 9637 The passed in serialized object is incorrectly encoded.
4274 9638 The cer or pvk file size is too large.
4275 9639 A password was supplied and the pvk file is not encrypted.
4276 9640 The operation encountered an OS error.
4277 9641 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.
4278 9642 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')
4279 9643 An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i.
4280 9644 An error occurred in the service broker message dispatcher. Error: %i, State: %i.
4281 9645 An error occurred in the service broker manager, Error: %i, State: %i.
4282 9646 An error occurred in the timer event cache. Error %i, state %i.
4283 9647 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.
4284 9648 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.
4285 9649 A security (SSPI) error occurred when connecting to another service broker: '%.*ls'. Check the Windows Event Log for more information.
4286 9650 A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '%ls'.
4287 9651 The system call failed during a Service Broker or Database Mirroring operation. System error: '%ls'.
4288 9652 Service Broker failed to retrieve the session key for encrypting a message.
4289 9653 The signature of activation stored procedure '%.*ls' is invalid. Parameters are not allowed.
4290 9654 Attempting to use database and it doesn't exist.
4291 9655 The transmission queue table structure in database is inconsistent. Possible database corruption.
4292 9657 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.
4293 9658 Cannot access the transmission queue table in database.
4294 9659 The %s of route '%.*ls' cannot be empty.
4295 9660 The %s of route '%.*ls' must be less than %d characters long.
4296 9661 The SERVICE_NAME and BROKER_INSTANCE of route "%.*ls" must be specified when using mirroring.
4297 9662 Cannot specify BROKER_INSTANCE without SERVICE_NAME in route "%.*ls".
4298 9663 The system object cannot be modified.
4299 9666 The %S_MSG protocol transport is disabled or not configured.
4300 9667 Services analyzed: %d.
4301 9668 Service Queues analyzed: %d.
4302 9669 Conversation Endpoints analyzed: %d.
4303 9670 Remote Service Bindings analyzed: %d.
4304 9671 Messages with conversation ID '%ls' have been removed from the transmission queue.
4305 9672 Messages with conversation handle '%ls' and conversation group '%ls' have been removed from the queue with ID %d.
4306 9673 Activation has been disabled on the queue with ID %d.
4307 9674 Conversation Groups analyzed: %d.
4308 9675 Message Types analyzed: %d.
4309 9676 Service Contracts analyzed: %d.
4310 9677 The service contract with ID %d is referencing the missing message type with ID %d.
4311 9678 The service with ID %d is referencing the missing service contract with ID %d.
4312 9679 The service with ID %d is referencing the missing service queue with ID %d.
4313 9680 The conversation endpoint '%ls' is referencing the missing conversation group '%ls'.
4314 9681 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service contract with ID %d.
4315 9682 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service with ID %d.
4316 9683 The conversation group '%ls' is referencing the missing service with ID %d.
4317 9684 The service with ID %d has been dropped.
4318 9685 The service contract with ID %d has been dropped.
4319 9686 The conversation endpoint with handle '%ls' has been dropped.
4320 9687 The conversation group '%ls' has been dropped.
4321 9688 Service Broker manager has started.
4322 9689 Service Broker manager has shut down.
4323 9690 The %S_MSG protocol transport is now listening for connections.
4324 9691 The %S_MSG protocol transport has stopped listening for connections.
4325 9692 The %S_MSG protocol transport cannot listen on port %d because it is in use by another process.
4326 9693 The %S_MSG protocol transport could not listen for connections due to the following error: '%.*ls'.
4327 9694 Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
4328 9695 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.
4329 9696 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.
4330 9697 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.
4331 9698 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.
4332 9699 Could not allocate memory for extra Service Broker tasks while adding CPUs.
4333 9701 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.
4334 9704 This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target service.
4335 9705 The messages in the queue with ID %d are referencing the invalid conversation handle '%ls'.
4336 9706 The stored procedure with ID %d is invalid but is referenced by the queue with ID %d.
4337 9707 The activation user with ID %d is invalid but is referenced by queue with ID %d.
4338 9708 The messages in the queue with ID %d are referencing the invalid conversation group '%ls'.
4339 9709 The messages in the queue with ID %d are referencing the invalid message type with ID %d.
4340 9710 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation group '%ls'.
4341 9711 The transmission queue is referencing the invalid conversation ID '%ls'.
4342 9712 The remote service binding with ID %d is referencing the invalid service contract with ID %d.
4343 9713 The message type with ID %d is referencing the invalid XML schema collection ID %d.
4344 9715 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.
4345 9716 The conversation group '%ls' reports references to %d conversation handle(s), but actually references %d.
4346 9717 Cannot enable stored procedure activation on queue '%.*ls'. Event notification for queue_activation is already configured on this queue.
4347 9718 Cannot create event notification for queue_activation on queue "%.*ls". Stored procedure activation is already configured on this queue.
4348 9719 The database for this conversation endpoint is attached or restored.
4349 9720 The database for the remote conversation endpoint is attached or restored.
4350 9721 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.
4351 9723 The database "%i" will not be started as the broker due to duplication in the broker instance ID.
4352 9724 The activated proc '%ls' running on queue '%ls' output the following: '%.*ls'
4353 9725 The invalid schema has been dropped from the message type with ID %d.
4354 9726 The remote service binding with ID %d has been dropped.
4355 9727 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.
4356 9728 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.
4357 9730 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.
4358 9731 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.
4359 9733 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.
4360 9734 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.
4361 9735 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.
4362 9736 An error occurred in dialog transmission: Error: %i, State: %i. %.*ls
4363 9737 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.
4364 9738 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.
4365 9739 Message transmitter in service broker message dispatcher failed %d times
4366 9740 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.
4367 9741 The %S_MSG '%.*ls' was dropped on upgrade because it referenced a system contract that was dropped.
4368 9742 The activation stored procedure '%.*ls' is invalid. Temporary procedures may not be configured for activation.
4369 9743 The %s of route "%.*ls" must be an address when using mirroring.
4370 9744 The %s of route "%.*ls" is not a valid address.
4371 9745 The ADDRESS of route '%.*ls' cannot be 'TRANSPORT' when SERVICE_NAME is specified.
4372 9746 The LIFETIME of route '%.*ls' must be in the range %d to %d.
4373 9747 The ADDRESS and MIRROR_ADDRESS of route '%.*ls' cannot be the same.
4374 9748 The %S_MSG protocol transport is not available.
4375 9749 Target queue is busy; message(s) queued for delivery.
4376 9750 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.
4377 9751 Authentication failed with error: '%.*ls'.
4378 9752 %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'.
4379 9753 The target service broker is unreachable.
4380 9754 Connection attempt failed with error: '%.*ls'.
4381 9755 An error occurred while receiving data: '%.*ls'.
4382 9756 An internal exception occurred while connecting to an adjacent broker: Error: %i, State: %i. %.*ls
4383 9757 Service Broker/Database Mirroring network protocol error occurred.
4384 9758 Login protocol negotiation error occurred.
4385 9759 An error occurred while sending data: '%.*ls'.
4386 9761 The Broker Configuration conversation on dialog handle '%s' closed due to an error. To troubleshoot this problem, investigate the error: '%.*ls'.
4387 9762 An error occurred while looking up the public key certificate associated with this SQL Server instance: No certificate was found.
4388 9763 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.
4389 9764 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is too large.
4390 9765 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found has no associated private key.
4391 9766 An unknown internal error (%d) occurred while looking up the public key certificate associated with this SQL Server instance.
4392 9767 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.
4393 9768 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.
4394 9769 Insufficient memory prevented the Service Broker/Database Mirroring Transport Manager from starting.
4395 9770 Locating routes and security information via the Broker Configuration Service.
4396 9771 The service broker manager is disabled in single-user mode.
4397 9772 The Service Broker in database "%.*ls" cannot be enabled because there is already an enabled Service Broker with the same ID.
4398 9773 The Service Broker in database "%d" is disabled because there is already an enabled Service Broker with the same ID.
4399 9774 Cannot create a new Service Broker in the attached read-only database "%.*ls". The Service Broker will be disabled.
4400 9775 Cannot create a new Service Broker in read-only database "%.*ls".
4401 9776 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).
4402 9777 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).
4403 9778 Cannot create a new Service Broker in a mirrored database "%.*ls".
4404 9779 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.
4405 9780 The service broker manager is initializing.
4406 9781 The service broker manager is shutting down.
4407 9782 An internal exception occurred while dispatching a message: Error: %i, State: %i. %.*ls
4408 9783 DNS lookup failed with error: '%.*ls'.
4409 9784 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.
4410 9785 Invalid address specified: '%.*ls'.
4411 9786 Cannot retrieve user name from security context. Error: '%.*ls'. State: %hu.
4412 9787 An error occurred while processing broker mirroring routes. Error: %i. State: %i.
4413 9788 Unable to route the incoming message. The system database msdb containing routing information is not available.
4414 9789 Unable to route the incoming message. The system database msdb containing routing information is not available. The broker is disabled in msdb.
4415 9790 Unable to route the incoming message. The system database msdb containing routing information is in SINGLE USER mode.
4416 9791 The broker is disabled in the sender's database.
4417 9792 Could not forward the message because forwarding is disabled in this SQL Server instance.
4418 9793 The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied.
4419 9794 The broker mirroring manager has not fully initialized.
4420 9795 Could not find the target broker in the local SQL Server instance.
4421 9796 The target service name matched a LOCAL route, but there is no service by that name in the local SQL Server instance.
4422 9797 Classification has been delayed because the routing information is currently being updated.
4423 9798 The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
4424 9801 Error converting %.*ls to %ls. The result would be truncated.
4425 9802 The locale identifier (LCID) %d is not supported by SQL Server.
4426 9803 Invalid data for type "%ls".
4427 9804 Column or parameter #%d: Invalid fractional second precision %d specified for %ls data type. The maximum fractional second precision is %d.
4428 9805 Warning: converting %ls to %ls caused a loss of information.
4429 9806 The datepart %.*ls is not supported by date function %.*ls.
4430 9807 The input character string does not follow style %d, either change the input character string or use a different style.
4431 9808 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.
4432 9809 The style %d is not supported for conversions from %s to %s.
4433 9810 The datepart %.*ls is not supported by date function %.*ls for data type %s.
4434 9811 The system timezone information could not be retrieved.
4435 9812 The timezone provided to builtin function %.*ls is invalid.
4436 9813 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.
4437 9814 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).
4438 9815 Waitfor delay and waitfor time cannot be of type %s.
4439 9816 The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set.
4440 9817 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.
4441 9901 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.
4442 9902 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.
4443 9903 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.
4444 9904 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.
4445 9905 Informational: Full-text indexer requested status change for catalog '%ls' ('%d') in database '%ls' ('%d'). New Status: %ls, Reason: %ls (%ls).
4446 9906 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.
4447 9907 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.
4448 9908 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.
4449 9909 Warning: Failed to change the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). Error: %ls.
4450 9910 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.
4451 9911 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.
4452 9912 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.
4453 9913 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.
4454 9914 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.
4455 9915 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.
4456 9916 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.
4457 9917 An internal error occurred in full-text docid mapper.
4458 9918 Warning: Full-text catalog '%ls' uses FAT volume. Security and differential backup are not supported for the catalog.
4459 9919 Fulltext DDL command failed because SQL Server was started in single user mode.
4460 9920 Warning: Failed to get MSFTESQL indexer interface for full-text catalog '%ls' ('%d') in database '%ls' ('%d'). Error: %ls.
4461 9921 During upgrade fatal error 0x%x encountered in CoCreateGuid. Failed to resolve full-text catalog file name for '%ls'.
4462 9922 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.
4463 9923 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.
4464 9924 Rebuild full-text catalog '%ls' failed: Catalog header file is read-only.
4465 9925 Rebuild full-text catalog '%ls' failed: Full-text catalog is read-only.
4466 9926 Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should.
4467 9927 Informational: The full-text search condition contained noise word(s).
4468 9928 Computed column '%.*ls' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column.
4469 9929 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.
4470 9930 Null document type provided. Row will not be full-text indexed.
4471 9931 Document type exceeds the maximum permitted length. Row will not be full-text indexed.
4472 9932 Document type value is malformed. Row will not be full-text indexed.
4473 9933 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.
4474 9934 Row was not found. It was deleted or updated while indexing was in progress.
4475 9935 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.
4476 9936 Informational: No full-text supported languages found.
4477 9937 Too many full-text columns or the full-text query is too complex to be executed.
4478 9938 Cannot find the specified user or role '%.*ls'.
4479 9939 Current user or role '%.*ls' does not have the required permission to set the owner.
4480 9940 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.
4481 9941 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
4482 9942 Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') was cancelled by user.
4483 9943 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.
4484 9944 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.
4485 9945 Error: All Full-text populations in progress, for catalog '%ls' ('%d') in database '%ls' ('%d') were terminated due to error. Error: 0x%x.
4486 9947 Warning: Identity of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog cannot be attached.
4487 9948 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.
4488 9949 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.
4489 9950 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.
4490 9951 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.
4491 9952 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.
4492 9953 The path '%.*ls' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive.
4493 9954 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.
4494 9955 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.
4495 9959 Cannot perform requested task because full-text memory manager is not initialized.
4496 9960 View '%.*ls' is not an indexed view. Full-text index is not allowed to be created on it.
4497 9961 Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified.
4498 9962 Failed to move full-text catalog from '%ls' to '%ls'. OS error '%ls'.
4499 9963 Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset.
4500 9964 Failed to finish full-text operation. Filegroup '%.*ls' is empty, read-only, or not online.
4501 9965 NULL or Invalid type of value specified for '%ls' parameter.
4502 9966 Cannot use full-text search in master, tempdb, or model database.
4503 9967 A default full-text catalog does not exist in database '%.*ls' or user does not have permission to perform this action.
4504 9968 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.
4505 9969 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.
4506 9970 Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline.
4507 9971 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.
4508 9972 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.
4509 9973 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.
4510 9974 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.
4511 9975 Warning: Only paused full population can be resumed. The command is ignored.
4512 9977 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.
4513 9978 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.
4514 9979 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.
4515 9980 Variable parameters can not be passed to fulltext predicates: contains, freetext and functions: containstable, freetexttable applied to remote table.
4516 9982 Cannot use full-text search in user instance.
4517 9983 The value '%ls' for the full-text component '%ls' is longer than the maximum permitted (%d characters). Please reduce the length of the value.
4518 9984 Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d').
4519 9998 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.
4520 9999 The column '%.*ls' in the table '%.*ls' cannot be used for full-text search because it is a sparse column set.
4521 10000 Unknown provider error.
4522 10001 The provider reported an unexpected catastrophic failure.
4523 10002 The provider did not implement the functionality.
4524 10003 The provider ran out of memory.
4525 10004 One or more arguments were reported invalid by the provider.
4526 10005 The provider did not support an interface.
4527 10006 The provider indicated an invalid pointer was used.
4528 10007 The provider indicated an invalid handle was used.
4529 10008 The provider terminated the operation.
4530 10009 The provider did not give any information about the error.
4531 10010 The data necessary to complete this operation was not yet available to the provider.
4532 10011 Access denied.
4533 10021 Execution terminated by the provider because a resource limit was reached.
4534 10022 The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
4535 10023 The provider does not support the necessary method.
4536 10024 The provider indicates that the user did not have the permission to perform the operation.
4537 10025 Provider caused a server fault in an external process.
4538 10026 No command text was set.
4539 10027 Command was not prepared.
4540 10028 Authentication failed.
4541 10032 Cannot return multiple result sets (not supported by the provider).
4542 10033 The specified index does not exist or the provider does not support an index scan on this data source.
4543 10034 The specified table or view does not exist or contains errors.
4544 10035 No value was given for one or more of the required parameters.
4545 10042 Cannot set any properties while there is an open rowset.
4546 10052 The insertion was canceled by the provider during notification.
4547 10053 Could not convert the data value due to reasons other than sign mismatch or overflow.
4548 10054 The data value for one or more columns overflowed the type used by the provider.
4549 10055 The data violated the integrity constraints for one or more columns.
4550 10056 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
4551 10057 Cannot create the row. Would exceed the total number of active rows supported by the rowset.
4552 10058 The consumer cannot insert a new row before releasing previously-retrieved row handles.
4553 10062 The change was canceled by the provider during notification.
4554 10063 Could not convert the data value due to reasons other than sign mismatch or overflow.
4555 10064 The data value for one or more columns overflowed the type used by the provider.
4556 10065 The data violated the integrity constraints for one or more columns.
4557 10066 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
4558 10067 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
4559 10068 The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
4560 10069 The consumer could not delete the row. The insertion has been transmitted to the data source.
4561 10081 The rowset uses integrated indexes and there is no current index.
4562 10085 RestartPosition on the table was canceled during notification.
4563 10086 The table was built over a live data stream and the position cannot be restarted.
4564 10087 The provider did not release some of the existing rows.
4565 10088 The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.
4566 10100 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.
4567 10101 Cannot create %S_MSG on view "%.*ls" because it contains the TOP keyword. Consider removing TOP or not indexing the view.
4568 10102 Cannot create %S_MSG on view "%.*ls" because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view.
4569 10103 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.
4570 10104 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.
4571 10105 Cannot create %S_MSG on view "%.*ls" because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view.
4572 10106 Cannot create %S_MSG on view "%.*ls" because it references an internal system rowset provider. Consider not indexing this view.
4573 10107 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.
4574 10108 Cannot create %S_MSG on view "%.*ls" because it references a SQL Server internal table.
4575 10109 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.
4576 10110 Cannot create %S_MSG on view "%.*ls" because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY.
4577 10111 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.
4578 10112 Cannot create %S_MSG on view '%.*ls' because it contains an INNER join that specifies a join hint. Consider removing the join hint.
4579 10113 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.
4580 10114 Cannot create %S_MSG on view "%.*ls" because it uses the PIVOT operator. Consider not indexing this view.
4581 10115 Cannot create %S_MSG on view "%.*ls" because it uses the UNPIVOT operator. Consider not indexing this view.
4582 10116 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.
4583 10117 Cannot create %S_MSG on view "%.*ls" because the view uses the "*" operator to select columns. Consider referencing columns by name instead.
4584 10118 Cannot create %S_MSG on view "%.*ls" because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
4585 10119 Cannot create %S_MSG on view "%.*ls" because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.
4586 10121 Cannot create %S_MSG on view "%.*ls" because it contains a HAVING clause. Consider removing the HAVING clause.
4587 10122 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.
4588 10123 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.
4589 10124 Cannot create %S_MSG on view "%.*ls" because it references an internal SQL Server column.
4590 10125 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.
4591 10126 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.
4592 10127 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.
4593 10128 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.
4594 10129 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.
4595 10130 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.
4596 10131 Cannot create %S_MSG on view "%.*ls" because it references imprecise common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view.
4597 10132 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.
4598 10133 Cannot create %S_MSG on view "%.*ls" because function "%.*ls" referenced by the view performs user or system data access.
4599 10134 Cannot create %S_MSG on view "%.*ls" because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY.
4600 10136 Cannot create %S_MSG on view "%.*ls" because it uses the aggregate COUNT. Use COUNT_BIG instead.
4601 10137 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.
4602 10138 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.
4603 10139 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.
4604 10140 Cannot create %S_MSG on view '%.*ls' because the view contains a table hint. Consider removing the hint.
4605 10141 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.
4606 10142 Cannot create %S_MSG on view "%.*ls" because it contains an APPLY. Consider not indexing the view, or removing APPLY.
4607 10143 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.
4608 10144 Cannot create %S_MSG on view '%.*ls' because it uses the CHANGETABLE function.
4609 10145 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.
4610 10211 Cannot invoke mutator on a null CLR type value.
4611 10227 Field "%.*ls" of type "%.*ls.%.*ls" cannot be updated because the field is "%.*ls".
4612 10240 Could not find UdtExtensions.dll. Please check your installation.
4613 10300 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.
4614 10301 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.
4615 10302 Could not get path for SQL Server: '%ls'.
4616 10303 Could not create AppDomain manager: '%.*ls'.
4617 10304 Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions.
4618 10305 The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.
4619 10306 The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property.
4620 10307 The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name.
4621 10308 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.
4622 10309 Warning: The SQL Server client assembly '%.*ls' you are registering is not fully tested in SQL Server hosted environment.
4623 10310 AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
4624 10311 AppDomain %i (%.*ls) is marked for unload due to memory pressure.
4625 10312 .NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token.
4626 10313 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
4627 10314 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
4628 10316 The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found.
4629 10317 An error occurred trying to get file version info for the file '%s'.
4630 10318 '%.*ls' failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute.
4631 10319 UserDefinedType method call failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute.
4632 10320 Method name '%.*ls' is invalid for '%.*ls'.
4633 10321 Method name '%.*ls' is invalid for UserDefinedType method call.
4634 10322 Type %.*ls not found in database %.*ls
4635 10323 Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls
4636 10324 WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers.
4637 10325 The server is shutting down due to stack overflow in user's unmanaged code.
4638 10326 Two versions of assembly '%.*ls' cannot coexist in database '%.*ls'. Keep one version and drop the other.
4639 10327 %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.
4640 10328 There is not enough stack to create appdomain '%.*ls'.
4641 10329 .Net Framework execution was aborted. %.*ls
4642 10330 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.
4643 10331 Type '%ls' in assembly '%.*ls' derives from a generic type which is not supported for a CLR Type.
4644 10501 Cannot create plan guide '%.*ls' because type '%.*ls' provided is not allowed.
4645 10502 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.
4646 10503 Operation '%.*ls' is not allowed.
4647 10504 Cannot create plan guide '%.*ls' because parameter @hints is incorrect. Use N'OPTION ( [ ,...n ] )'.
4648 10505 Cannot create plan guide '%.*ls' because value '%.*ls' provided for @module_or_batch is not legal two-part name. Use 'schema_name.object_name'.
4649 10506 Cannot create plan guide '%.*ls' because parameter @stmt has more than one statement.
4650 10507 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.
4651 10508 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.
4652 10509 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.
4653 10510 Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name.
4654 10512 Cannot create plan guide '%.*ls' because object '@module_or_batch' is encrypted. Consider tuning query using other techniques such as indexes and statistics.
4655 10513 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.
4656 10515 Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission.
4657 10516 Cannot create plan guide '%.*ls' because @module_or_batch can not be compiled.
4658 10517 Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required.
4659 10518 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.
4660 10519 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.
4661 10520 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.
4662 10521 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.
4663 10522 Cannot create plan guide '%.*ls' because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) if @type is 'template'.
4664 10523 Cannot generate query template because @querytext does not contain a valid single query.
4665 10524 Cannot parameterize @querytext.
4666 10525 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.
4667 10526 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.
4668 10527 Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object.
4669 10528 Cannot create plan guide '%.*ls' because its name is invalid. Plan guide name cannot begin with a '#' character.
4670 10529 Cannot create plan guide '%.*ls' because there is already a planguide '%.*ls' of @type 'template' on @stmt.
4671 10530 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.
4672 10531 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.
4673 10532 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.
4674 10533 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.
4675 10534 Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form , or specify NULL.
4676 10535 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.
4677 10536 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.
4678 10537 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.
4679 10538 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.
4680 10539 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.
4681 10601 Cannot specify included columns for a clustered index.
4682 10602 Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
4683 10603 Cannot rebuild clustered index '%.*ls' on view '%.*ls' because the view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disabled.
4684 10604 Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
4685 10605 Cannot disable primary key index "%.*ls" on table "%.*ls" because the table is published for replication.
4686 10606 Cannot disable the clustered index "%.*ls" on view "%.*ls" because the indexed view is published for replication.
4687 10607 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.
4688 10608 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.
4689 10609 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.
4690 10610 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.
4691 10611 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'.
4692 10612 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.
4693 10617 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.
4694 10618 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.
4695 10619 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.
4696 10620 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.
4697 10621 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.
4698 10622 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.
4699 10623 Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user tables.
4700 10700 The table-valued parameter "%.*ls" is READONLY and cannot be modified.
4701 10701 The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement.
4702 10702 The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification.
4703 10703 Too many grouping sets. The maximum number is %d.
4704 10705 Subqueries are not allowed in the OUTPUT clause.
4705 10706 Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied.
4706 10707 The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 mode or higher.
4707 10708 DEFAULT is not allowed on the right hand side of "%.*ls"
4708 10709 The number of columns for each row in a table value constructor must be the same.
4709 10710 An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
4710 10711 An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement.
4711 10712 Non-ANSI outer join operators ("*=" or "=*") are not allowed in a MERGE statement. Use the OUTER JOIN keywords instead.
4712 10713 A MERGE statement must be terminated by a semi-colon (;).
4713 10714 An action of type '%S_MSG' cannot appear more than once in a '%S_MSG' clause of a MERGE statement.
4714 10716 A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause.
4715 10717 The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
4716 10718 Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements.
4717 10719 Non-ANSI outer join operators ("*=" or "=*") are not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. Use the OUTER JOIN keywords instead.
4718 10720 An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
4719 10721 The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
4720 10722 The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
4721 10723 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'.
4722 10724 The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
4723 10725 Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
4724 10726 User defined aggregates do not support default parameters.
4725 10727 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.
4726 10728 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.
4727 10729 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.
4728 10730 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.
4729 10731 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.
4730 10732 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.
4731 10733 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.
4732 10734 Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.
4733 10735 Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.*ls'.
4734 10736 A full-text stoplist statement must be terminated by a semi-colon (;).
4735 10737 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.
4736 10738 The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.
4737 10739 The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.
4738 10900 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').
4739 10901 User does not have permission to alter the resource governor configuration.
4740 10902 User-defined function '%s' does not exist in master database, or the user does not have permission to access it.
4741 10903 The specified schema name '%.*ls' for classifier user-defined function either does not exist, or the user does not have permission to use it.
4742 10904 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.
4743 10905 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.
4744 10906 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.
4745 10907 Attribute '%.*ls' with value of %u is greater than attribute '%.*ls' with value of %u.
4746 10908 Attribute '%.*ls' with value of %u is less than attribute '%.*ls' with value of %u.
4747 10909 The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools.
4748 10910 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.
4749 10911 Requested operation cannot be performed because the resource pool '%.*ls' does not exist.
4750 10912 The operation could not be completed. Dropping predefined %S_MSG is not allowed.
4751 10913 Users are not allowed to %S_MSG the workload group '%.*ls' in the '%.*ls' resource pool.
4752 10914 The name of the %S_MSG '%.*ls' cannot begin with # of ##.
4753 10915 The operation could not be completed. Altering '%.*ls' %S_MSG is not allowed.
4754 10916 Cannot drop resource pool '%.*ls' because it contains workload group '%.*ls'. Drop or remove all workload groups using this resource pool before dropping it.
4755 10917 ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified.
4756 10918 Cannot create %S_MSG '%.*ls' because it already exists.
4757 10919 An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system administrator.
4758 10920 Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier.
4759 10921 The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG.
4760 10922 %ls failed. Rerun the statement.
4761 10923 %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.
4762 10981 Resource governor reconfiguration succeeded.
4763 10982 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.
4764 10983 Resource governor '%ls' operation was canceled by user.
4765 10984 Resource governor reconfiguration failed.
4766 11000 Unknown status code for this column.
4767 11001 Non-NULL value successfully returned.
4768 11002 Deferred accessor validation occurred. Invalid binding for this column.
4769 11003 Could not convert the data value due to reasons other than sign mismatch or overflow.
4770 11004 Successfully returned a NULL value.
4771 11005 Successfully returned a truncated value.
4772 11006 Could not convert the data type because of a sign mismatch.
4773 11007 Conversion failed because the data value overflowed the data type used by the provider.
4774 11008 The provider cannot allocate memory or open another storage object on this column.
4775 11009 The provider cannot determine the value for this column.
4776 11010 The user did not have permission to write to the column.
4777 11011 The data value violated the integrity constraints for the column.
4778 11012 The data value violated the schema for the column.
4779 11013 The column had a bad status.
4780 11014 The column used the default value.
4781 11015 The column was skipped when setting data.
4782 11031 The row was successfully deleted.
4783 11032 The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source.
4784 11033 The row was released even though it had a pending change.
4785 11034 Deletion of the row was canceled during notification.
4786 11036 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
4787 11037 The row has a pending delete or the deletion had been transmitted to the data source.
4788 11038 The row is a pending insert row.
4789 11039 DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source.
4790 11040 Deleting the row violated the integrity constraints for the column or table.
4791 11041 The row handle was invalid or was a row handle to which the current thread does not have access rights.
4792 11042 Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.
4793 11043 The row has a storage object open.
4794 11044 The provider ran out of memory and could not fetch the row.
4795 11045 User did not have sufficient permission to delete the row.
4796 11046 The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.
4797 11047 Updating did not meet the schema requirements.
4798 11048 There was a recoverable, provider-specific error, such as an RPC failure.
4799 11100 The provider indicates that conflicts occurred with other properties or requirements.
4800 11101 Could not obtain an interface required for text, ntext, or image access.
4801 11102 The provider could not support a required row lookup interface.
4802 11103 The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.
4803 11104 The provider could not support insertion on this table.
4804 11105 The provider could not support updates on this table.
4805 11106 The provider could not support deletion on this table.
4806 11107 The provider could not support a row lookup position.
4807 11108 The provider could not support a required property.
4808 11109 The provider does not support an index scan on this data source.
4809 11201 This message could not be delivered because the FROM service name is missing. The message origin is: '%ls'.
4810 11202 This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
4811 11203 This message has been dropped because the FROM broker instance is missing. The message origin is '%ls'.
4812 11204 This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: "%.*ls". Message origin: "%ls".
4813 11205 This message has been dropped because the TO service name is missing. The message origin is "%ls".
4814 11206 This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
4815 11207 This message has been dropped because the service contract name is missing. The message origin is "%ls".
4816 11208 This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name "%.*ls". Message origin: "%ls".
4817 11209 This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: '%ls'.
4818 11210 This message has been dropped because the TO service could not be found. Service name: "%.*ls". Message origin: "%ls".
4819 11211 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;.
4820 11212 This message could not be delivered because the conversation endpoint has already been closed.
4821 11213 This message could not be delivered because this is not the first message in the conversation.
4822 11214 This message could not be delivered because the '%.*ls' contract could not be found or the service does not accept conversations for the contract.
4823 11215 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'.
4824 11216 This message could not be delivered because there is already another task processing this message.
4825 11217 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.
4826 11218 This message could not be delivered because it is a duplicate.
4827 11219 This message could not be delivered because the destination queue has been disabled. Queue ID: %d.
4828 11220 This message could not be delivered because the TO broker instance is missing.
4829 11221 This message could not be delivered because there is an inconsistency in the message header.
4830 11222 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'.
4831 11223 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'.
4832 11224 This message could not be delivered because another instance of this service program has already started conversing with this endpoint.
4833 11225 This message could not be delivered because the message type name could not be found. Message type name: '%.*ls'.
4834 11226 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'.
4835 11227 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'.
4836 11228 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'.
4837 11229 This message could not be delivered because the security context could not be retrieved.
4838 11230 This message could not be delivered because the message could not be decrypted and validated.
4839 11231 This message could not be delivered because the conversation endpoint is not secured, however the message is secured.
4840 11232 This message could not be delivered because the conversation endpoint is secured, however the message is not secured.
4841 11233 This message has been dropped because the session key of the conversation endpoint does not match that of the message.
4842 11234 This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls.
4843 11235 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.
4844 11236 A corrupted message has been received. The binary header size of %d is expected, however the header size received was %d.
4845 11237 A %S_MSG message could not be processed due to insufficient memory. The message was dropped.
4846 11238 A corrupted message has been received. The private variable data segment is malformed.
4847 11239 A corrupted message has been received. The private variable data segment extends beyond the length of the message.
4848 11240 A corrupted message has been received. The binary message preamble is malformed.
4849 11241 A corrupted message has been received. The conversation security version number is not %d.%d.
4850 11242 A corrupted message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found: %d.
4851 11243 A corrupted message has been received. The public variable data element (%d) has been duplicated in this message.
4852 11244 A corrupted message has been received. The handshake validation header is malformed.
4853 11245 A corrupted message has been received. The maximum number of private variable data elements (%d) has been exceeded. Private variable data elements found: %d.
4854 11246 A corrupted message has been received. The private variable data element (%d) has been duplicated in this message.
4855 11247 A corrupted message has been received. The login negotiate header is invalid.
4856 11248 A corrupted message has been received. The SSPI login header is invalid.
4857 11249 A corrupted message has been received. The pre-master-secret is invalid.
4858 11250 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.
4859 11251 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.
4860 11252 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.
4861 11253 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.
4862 11254 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.
4863 11255 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.
4864 11256 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.
4865 11257 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.
4866 11258 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.
4867 11259 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.
4868 11260 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.
4869 11261 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.
4870 11262 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.
4871 11263 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.
4872 11264 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.
4873 11265 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.
4874 11266 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.
4875 11267 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.
4876 11268 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.
4877 11269 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.
4878 11270 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.
4879 11271 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.
4880 11272 A corrupted message has been received. The message ID must not be NULL.
4881 11273 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.
4882 11274 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.
4883 11275 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.
4884 11276 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.
4885 11277 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.
4886 11278 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.
4887 11279 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.
4888 11280 A packet of size %lu bytes could not be processed because it exceeds the receive buffer count.
4889 11281 A corrupted message has been received. The private portion of the message header is malformed.
4890 11282 This message has been dropped due to licensing restrictions. See the documentation for further details.
4891 11285 This forwarded message has been dropped because the hops remaining count has reached 0.
4892 11286 Dropped this forwarded message because this SQL Server instance is out of memory.
4893 11288 This forwarded message has been dropped because a duplicate message is already being forwarded.
4894 11289 This forwarded message has been dropped because its memory usage would exceed the configured memory limit of %d bytes for forwarded messages.
4895 11290 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.
4896 11291 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).
4897 11292 The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events for the error.
4898 11293 This forwarded message has been dropped because a transport is shutdown.
4899 11294 This forwarded message has been dropped because the destination route is not valid.
4900 11295 Endpoint configuration change detected. Service Broker manager and transport will now restart.
4901 11296 Certificate change detected. Service Broker manager and transport will now restart.
4902 11297 A corrupted message has been received. The private variable data segment offset is incorrect.
4903 11298 A corrupted message has been received. The public variable data segment offset is incorrect.
4904 11299 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.
4905 11300 Error wile committing a readonly or a TEMPDB XDES, Shutting down the server.
4906 11301 Error while performing transaction notification for object %p event %d.
4907 11302 Error during rollback. shutting down database (location: %d).
4908 11303 Error releasing reserved log space: %ls space %I64d, code %d, state %d.
4909 11304 Failed to record outcome of a local two-phase commit transaction. Taking database offline.
4910 11400 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.
4911 11401 ALTER TABLE SWITCH statement failed. Table '%.*ls' is %S_MSG, but index '%.*ls' on indexed view '%.*ls' is %S_MSG.
4912 11402 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.
4913 11403 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'.
4914 11404 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.
4915 11405 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.
4916 11406 ALTER TABLE SWITCH statement failed. Source and target partitions have different values for the DATA_COMPRESSION option.
4917 11407 Vardecimal storage format can not be enabled for '%.*ls'. Only Enterprise edition of SQL Server supports vardecimal.
4918 11408 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.
4919 11409 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.
4920 11410 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.
4921 11411 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.
4922 11412 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'.
4923 11413 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same column set property in tables '%.*ls' and '%.*ls'.
4924 11414 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.
4925 11415 Object '%.*ls' cannot be disabled or enabled. This action applies only to foreign key and check constraints.
4926 11418 Cannot %S_MSG table '%.*ls' because the table either contains sparse columns or a column set column which are incompatible with compression.
4927 11551 ABR - Operation is aborted; error '0x%x'
4928 11552 ABR - Insufficient disk space to write backup'
4929 11553 ABR - Cannot create temporary backup file '%.*ls'; error '0x%x'
4930 11554 ABR - Cannot create the virtual device set interface; error '0x%x'
4931 11555 ABR - Database '%ls' is corrupt
4932 11556 ABR - Database backup for '%ls' is corrupt
4933 11557 ABR - The backup file '%.*ls' does not exist; error '0x%x'
4934 11558 ABR - Cannot open the backup file '%.*ls'; error '0x%x'
4935 11559 ABR - Cannot create the backupset metadata; error '0x%x'
4936 11560 ABR - Cannot delete the backupset metadata; error '0x%x'
4937 11561 ABR - Cannot delete a backup file
4938 11562 ABR - Can not acquire a lock on database '%ls'
4939 11563 ABR - Transaction log for database '%ls' is corrupt
4940 11564 ABR - Cannot find the IO throttler for drive '%.*ls'
4941 11565 ABR - Cannot open device '%.*ls'; error '0x%x'
4942 11566 ABR - Cannot query device '%.*ls'; error '0x%x'
4943 11567 ABR - Database '%ls' is offline.
4944 11599 ABR - Unknown ABR error
4945 12002 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.
4946 12003 Could not find spatial tessellation scheme '%.*ls'. Specify a valid tessellation scheme name in your USING clause.
4947 12004 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.
4948 12005 Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax.
4949 12006 Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax.
4950 12007 The CREATE %S_MSG statement is missing the required parameter '%.*ls'. Validate the statement against the index-creation syntax.
4951 12008 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.
4952 12009 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.
4953 12010 Only one spatial index hint may appear per table, either as the first or the last hinted index.
4954 12011 The value of parameter '%.*ls' of CREATE %S_MSG must be less than %d.
4955 12012 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d.
4956 12013 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than the value of parameter '%.*ls'.
4957 12014 The '%.*ls' parameter of CREATE %S_MSG is incompletely defined. If the parameter has more than one part, all the parts must be defined.
4958 12015 The index option %.*ls in the CREATE %S_MSG statement has to appear before the general index options.
4959 12016 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.
4960 12017 The spatial index is disabled or offline
4961 12018 The spatial object is not defined in the scope of the predicate
4962 12019 Spatial indexes do not support the comparand supplied in the predicate
4963 12020 Spatial indexes do not support the comparator supplied in the predicate
4964 12021 Spatial indexes do not support the method name supplied in the predicate
4965 12022 The comparand references a column that is defined below the predicate
4966 12023 The comparand in the comparison predicate is not deterministic
4967 12024 The spatial parameter references a column that is defined below the predicate
4968 12025 Could not find required binary spatial method in a condition
4969 12026 Could not find required comparison predicate
4970 12101 Cannot disable change tracking on database '%.*ls' while client connections are waiting on change notification. Please close those connections before disabling change tracking.
4971 12980 Supply either %s or %s to identify the log entries.
4972 12981 You must specify %s when creating a subplan.
4973 12982 Supply either %s or %s to identify the plan or sub-plan to be run.
4974 13001 file name
4975 13002 audit
4976 13003 audit specification
4977 13004 audit name
4978 13008 receive
4979 13010 read
4980 13012 a USE database statement
4981 13013 a procedure, function or trigger
4982 13014 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
4983 13015 spatial index operations
4984 13016 an INTO clause
4985 13018 a COMPUTE clause
4986 13019 a SELECT INTO statement
4987 13020 option
4988 13021 offset option
4989 13022 statistics option
4990 13024 function name
4991 13025 varbinary (128) NOT NULL
4992 13026 parameter
4993 13027 convert specification
4994 13028 index
4995 13029 table
4996 13030 database
4997 13031 procedure
4998 13032 trigger
4999 13033 view
5000 13034 default


Posted Tue, Feb 26 2013 12:17 PM by arachnode.net
An Open Source C# web crawler with Lucene.NET search using SQL 2008/2012/CE

copyright 2004-2017, arachnode.net LLC