ID SEV TEXT 21 20 Warning: Fatal error %d occurred at %S_DATE.

Note the error and time, and contact your system administrator. 101 15 Query not allowed in Waitfor. 102 15 Incorrect syntax near '%.*ls'. 103 15 The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d. 104 15 ORDER BY items must appear in the select list if the statement c ontains a UNION, INTERSECT or EXCEPT operator. 105 15 Unclosed quotation mark after the character string '%.*ls'. 106 16 Too many table names in the query. The maximum allowable is %d. 107 15 The column prefix '%.*ls' does not match with a table name or al ias name used in the query. 108 15 The ORDER BY position number %ld is out of range of the number o f items in the select list. 109 15 There are more columns in the INSERT statement than values speci fied in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 110 15 There are fewer columns in the INSERT statement than values spec ified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 111 15 '%ls' must be the first statement in a query batch. 112 15 Variables are not allowed in the %ls statement. 113 15 Missing end comment mark '*/'. 114 15 Browse mode is invalid for a statement that assigns values to a variable. 115 15 The FOR UPDATE clause is invalid for statements containing set o perators. 116 15 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. 117 15 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. 119 15 Must pass parameter number %d and subsequent parameters as '@nam e = value'. After the form '@name = value' has been used, all subsequent paramet ers must be passed in the form '@name = value'. 120 15 The select list for the INSERT statement contains fewer items th an the insert list. The number of SELECT values must match the number of INSERT columns. 121 15 The select list for the INSERT statement contains more items tha n the insert list. The number of SELECT values must match the number of INSERT c olumns. 122 15 The %ls option is allowed only with %ls syntax. 123 15 Batch/procedure exceeds maximum length of %d characters. 124 15 CREATE PROCEDURE contains no statements. 125 15 Case expressions may only be nested to level %d. 126 15 Invalid pseudocolumn "%.*ls". 127 15 A TOP N or FETCH rowcount value may not be negative. 128 15 The name "%.*s" is not permitted in this context. Valid expressi ons are constants, constant expressions, and (in some contexts) variables. Colum n names are not permitted. 129 15 Fillfactor %d is not a valid percentage; fillfactor must be betw een 1 and 100. 130 16 Cannot perform an aggregate function on an expression containing an aggregate or a subquery. 131 15 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum al lowed for any data type (%d). 132 15 The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure. 133 15 A GOTO statement references the label '%.*ls' but the label has not been declared.

134 15 The variable name '%.*ls' has already been declared. Variable na mes must be unique within a query batch or stored procedure. 135 15 Cannot use a BREAK statement outside the scope of a WHILE statem ent. 136 15 Cannot use a CONTINUE statement outside the scope of a WHILE sta tement. 137 15 Must declare the scalar variable "%.*ls". 138 15 Correlation clause in a subquery not permitted. 139 15 Cannot assign a default value to a local variable. 140 15 Can only use IF UPDATE within a CREATE TRIGGER statement. 141 15 A SELECT statement that assigns a value to a variable must not b e combined with data-retrieval operations. 142 15 Incorrect syntax for definition of the '%ls' constraint. 144 15 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. 145 15 ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 146 15 Could not allocate ancillary table for a subquery. Maximum numbe r of tables in a query (%d) exceeded. 147 15 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 a ggregated is an outer reference. 148 15 Incorrect time syntax in time string '%.*ls' used with WAITFOR. 149 15 Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax. 151 15 '%.*ls' is an invalid money value. 152 15 The same large data placement option "%.*ls" has been specified twice. 153 15 Invalid usage of the option %.*ls in the %ls statement. 154 15 %S_MSG is not allowed in %S_MSG. 155 15 '%.*ls' is not a recognized %ls option. 156 15 Incorrect syntax near the keyword '%.*ls'. 157 15 An aggregate may not appear in the set list of an UPDATE stateme nt. 158 15 An aggregate may not appear in the OUTPUT clause. 159 15 Must specify the table name and index name for the DROP INDEX st atement. 160 15 Rule does not contain a variable. 161 15 Rule contains more than one variable. 162 15 Invalid expression in a TOP or OFFSET clause. 164 15 Each GROUP BY expression must contain at least one column that i s not an outer reference. 165 16 Privilege %ls may not be granted or revoked. 166 15 '%ls' does not allow specifying the database name as a prefix to the object name. 167 15 Cannot create %S_MSG on a temporary object. 168 15 The floating point value '%.*ls' is out of the range of computer representation (%d bytes). 169 15 A column has been specified more than once in the order by list. Columns in the order by list must be unique. 171 15 Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE s tatements. 172 15 Cannot use HOLDLOCK in browse mode. 173 15 The definition for column '%.*ls' must include a data type. 174 15 The %.*ls function requires %d argument(s). 175 15 An aggregate may not appear in a computed column expression or c heck constraint. 176 15 The FOR BROWSE clause is no longer supported in views. 177 15 The IDENTITY function can only be used when the SELECT statement has an INTO clause.

178 15 A RETURN statement with a return value cannot be used in this co ntext. 179 15 Cannot use the OUTPUT option when passing a constant to a stored procedure. 180 15 There are too many parameters in this %ls statement. The maximum number is %d. 181 15 Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or C REATE FUNCTION statement. 182 15 Table and column names must be supplied for the READTEXT or WRIT ETEXT utility. 183 15 The scale (%d) for column '%.*ls' must be within the range %d to %d. 184 16 DEFAULT cannot be specified more than once for filegroups of the same content type. 185 15 Data stream is invalid for WRITETEXT statement in bulk form. 186 15 Data stream missing from WRITETEXT statement. 187 16 The valid range for MAX_QUEUE_READERS is 0 to 32767. 188 15 Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file. 189 15 The %ls function requires %d to %d arguments. 190 15 An invalid date or time was specified in the statement. 191 15 Some part of your SQL statement is nested too deeply. Rewrite th e query or break it up into smaller queries. 192 16 The scale must be less than or equal to the precision. 193 15 The object or column name starting with '%.*ls' is too long. The maximum length is %d characters. 194 15 A SELECT INTO statement cannot contain a SELECT statement that a ssigns values to a variable. 195 15 '%.*ls' is not a recognized %S_MSG. 196 15 SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator. 197 15 EXECUTE cannot be used as a source when inserting into a table v ariable. 198 15 Browse mode is invalid for statements containing a UNION, INTERS ECT or EXCEPT operator. 199 15 An INSERT statement cannot contain a SELECT statement that assig ns values to a variable. 201 16 Procedure or function '%.*ls' expects parameter '%.*ls', which w as not supplied. 202 16 Invalid type '%s' for WAITFOR. Supported data types are CHAR/VAR CHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. 203 16 The name '%.*ls' is not a valid identifier. 204 20 Normalization error in node %ls. 205 16 All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists. 206 16 Operand type clash: %ls is incompatible with %ls 207 16 Invalid column name '%.*ls'. 208 16 Invalid object name '%.*ls'. 209 16 Ambiguous column name '%.*ls'. 210 16 Conversion failed when converting datetime from binary/varbinary string. 211 23 Possible schema corruption. Run DBCC CHECKCATALOG. 212 16 Expression result length exceeds the maximum. %d max, %d found. 213 16 Column name or number of supplied values does not match table de finition. 214 16 Procedure expects parameter '%ls' of type '%ls'. 215 16 Parameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. 216 16 Parameters were not supplied for the function '%.*ls'.

217 16 Maximum stored procedure, function, trigger, or view nesting lev el exceeded (limit %d). 218 16 Could not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission. 219 16 The type '%.*ls' already exists, or you do not have permission t o create it. 220 16 Arithmetic overflow error for data type %ls, value = %ld. 221 10 FIPS Warning: Implicit conversion from %ls to %ls. 222 16 The base type "%.*ls" is not a valid base type for the alias dat a type. 223 11 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. 224 11 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. 225 16 The parameters supplied for the %ls "%.*ls" are not valid. 226 16 %ls statement not allowed within multi-statement transaction. 227 15 "%.*ls" is not a valid function, property, or field. 228 15 Method '%.*ls' of type '%.*ls' in assembly '%.*ls' does not retu rn any value. 229 14 The %ls permission was denied on the object '%.*ls', database '% .*ls', schema '%.*ls'. 230 14 The %ls permission was denied on the column '%.*ls' of the objec t '%.*ls', database '%.*ls', schema '%.*ls'. 231 11 No such default. ID = %ld, database ID = %d. 232 16 Arithmetic overflow error for type %ls, value = %f. 233 16 The column '%.*ls' in table '%.*ls' cannot be null. 234 16 There is insufficient result space to convert a money value to % ls. 235 16 Cannot convert a char value to money. The char value has incorre ct syntax. 236 16 The conversion from char data type to money resulted in a money overflow error. 237 16 There is insufficient result space to convert a money value to % ls. 239 16 Duplicate common table expression name '%.*ls' was specified. 240 16 Types don't match between the anchor and the recursive part in c olumn "%.*ls" of recursive query "%.*ls". 241 16 Conversion failed when converting date and/or time from characte r string. 242 16 The conversion of a %ls data type to a %ls data type resulted in an out-of-range value. 243 16 Type %.*ls is not a defined system type. 244 16 The conversion of the %ls value '%.*ls' overflowed an %hs column . Use a larger integer column. 245 16 Conversion failed when converting the %ls value '%.*ls' to data type %ls. 246 16 No anchor member was specified for recursive query "%.*ls". 247 16 An anchor member was found in the recursive part of recursive qu ery "%.*ls". 248 16 The conversion of the %ls value '%.*ls' overflowed an int column . 249 16 The type "%ls" is not comparable. It cannot be used in the %ls c lause. 251 16 Could not allocate ancillary table for query optimization. Maxim um number of tables in a query (%d) exceeded. 252 16 Recursive common table expression '%.*ls' does not contain a top -level UNION ALL operator. 253 16 Recursive member of a common table expression '%.*ls' has multip le recursive references. 254 16 Prefixed columns are not allowed in the column list of a PIVOT o

perator. 255 16 Pseudocolumns are not allowed in the column list of a PIVOT oper ator. 256 16 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. 257 16 Implicit conversion from data type %ls to %ls is not allowed. Us e the CONVERT function to run this query. 258 15 Cannot call methods on %ls. 259 16 Ad hoc updates to system catalogs are not allowed. 260 16 Disallowed implicit conversion from data type %ls to data type % ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query. 261 16 '%.*ls' is not a recognized function. 262 16 %ls permission denied in database '%.*ls'. 263 16 Must specify table to select from. 264 16 The column name '%.*ls' is specified more than once in the SET c lause or column list of an INSERT. A column cannot be assigned more than one val ue in the same clause. Modify the clause to make sure that a column is updated o nly once. If this statement updates or inserts columns into a view, column alia sing can conceal the duplication in your code. 265 16 The column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument. 266 16 Transaction count after EXECUTE indicates a mismatching number o f BEGIN and COMMIT statements. Previous count = %ld, current count = %ld. 267 16 Object '%.*ls' cannot be found. 268 16 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. 270 16 Object '%.*ls' cannot be modified. 271 16 The column "%.*ls" cannot be modified because it is either a com puted column or is the result of a UNION operator. 272 16 Cannot update a timestamp column. 273 16 Cannot insert an explicit value into a timestamp column. Use INS ERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. 275 16 Prefixes are not allowed in value or pivot columns of an UNPIVOT operator. 276 16 Pseudocolumns are not allowed as value or pivot columns of an UN PIVOT operator. 277 16 The column "%.*ls" is specified multiple times in the column lis t of the UNPIVOT operator. 278 16 The text, ntext, and image data types cannot be used in a GROUP BY clause. 279 16 The text, ntext, and image data types are invalid in this subque ry or aggregate expression. 280 16 Only base table columns are allowed in the TEXTPTR function. 281 16 %d is not a valid style number when converting from %ls to a cha racter string. 282 10 The '%.*ls' procedure attempted to return a status of NULL, whic h is not allowed. A status of 0 will be returned instead. 283 16 READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. 284 16 Rules cannot be bound to text, ntext, or image data types. 285 16 The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be use d with views or functions. 286 16 The logical tables INSERTED and DELETED cannot be updated. 287 16 The %ls statement is not allowed within a trigger. 288 16 The PATINDEX function operates on char, nchar, varchar, nvarchar , text, and ntext data types only. 289 16 Cannot construct data type %ls, some of the arguments have value s which are not valid. 290 16 Invalid EXECUTE statement using object "%ls", method "%ls".

291 16 CAST or CONVERT: invalid attributes specified for type '%.*ls' 292 16 There is insufficient result space to convert a smallmoney value to %ls. 293 16 Cannot convert char value to smallmoney. The char value has inco rrect syntax. 294 16 The conversion from char data type to smallmoney data type resul ted in a smallmoney overflow error. 295 16 Conversion failed when converting character string to smalldatet ime data type. 297 16 The user does not have permission to perform this action. 300 14 %ls permission was denied on object '%.*ls', database '%.*ls'. 301 16 Query contains an outer-join request that is not permitted. 302 16 The newsequentialid() built-in function can only be used in a DE FAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or AL TER TABLE statement. It cannot be combined with other operators to form a comple x scalar expression. 303 16 The table '%.*ls' is an inner member of an outer-join clause. Th is is not allowed if the table also participates in a regular join clause. 304 16 '%d' is out of range for index option '%.*ls'. See sp_configure option '%ls' for valid values. 305 16 The XML data type cannot be compared or sorted, except when usin g the IS NULL operator. 306 16 The text, ntext, and image data types cannot be compared or sort ed, except when using IS NULL or LIKE operator. 307 16 Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist. 308 16 Index '%.*ls' on table '%.*ls' (specified in the FROM clause) do es not exist. 309 16 Cannot use index "%.*ls" on table "%.*ls" in a hint. XML indexes are not allowed in hints. 310 15 The value %d specified for the MAXRECURSION option exceeds the a llowed maximum of %d. 311 16 Cannot use text, ntext, or image columns in the 'inserted' and ' deleted' tables. 312 16 Cannot reference text, ntext, or image columns in a filter store d procedure. 313 16 An insufficient number of arguments were supplied for the proced ure or function %.*ls. 314 16 Cannot use GROUP BY ALL with the special tables INSERTED or DELE TED. 315 16 Index "%.*ls" on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 316 16 The index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 317 16 Table-valued function '%.*ls' cannot have a column alias. 318 16 The table (and its columns) returned by a table-valued method ne ed to be aliased. 319 16 Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context c lause, the previous statement must be terminated with a semicolon. 320 16 The compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal. 321 15 "%.*ls" is not a recognized table hints option. If it is intende d as a parameter to a table-valued function or to the CHANGETABLE function, ensu re that your database compatibility mode is set to 90. 322 15 The variable "%.*ls" is specified in the OPTIMIZE FOR clause, bu t is not used in the query. 324 15 The 'ALL' version of the %.*ls operator is not supported. 325 15 Incorrect syntax near '%.*ls'. You may need to set the compatibi lity level of the current database to a higher value to enable this feature. See

help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. 326 16 Multi-part identifier '%.*ls' is ambiguous. Both columns '%.*ls' and '%.*ls' exist. 327 16 Function call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist. 328 16 A cursor plan could not be generated for the given statement bec ause the textptr() function was used on a LOB column from one of the base tables . 329 16 Each GROUP BY expression must contain at least one column refere nce. 330 15 The target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression. 331 15 The target table '%.*ls' of the OUTPUT INTO clause cannot have a ny enabled triggers. 332 15 The target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constr aint '%ls'. 333 15 The target table '%.*ls' of the OUTPUT INTO clause cannot have a ny enabled check constraints or any enabled rules. Found check constraint or rul e '%ls'. 334 15 The target table '%.*ls' of the DML statement cannot have any en abled triggers if the statement contains an OUTPUT clause without INTO clause. 335 16 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 param eters instead. 336 15 Incorrect syntax near '%.*ls'. If this is intended to be a commo n table expression, you need to explicitly terminate the previous statement with a semi-colon. 337 10 Warning: the floating point value '%.*ls' is too small. It will be interpreted as 0. 338 16 READEXT, WRITETEXT, and UPDATETEXT statements cannot be used wit h views, remote tables, and inserted or deleted tables inside triggers. 339 16 DEFAULT or NULL are not allowed as explicit identity values. 340 16 Cannot create the trigger "%.*ls" on view "%.*ls". AFTER trigger s cannot be created on views. 341 16 Replication filter procedures may not contain columns of large o bject, large value, XML or CLR type. 342 16 Column "%.*ls" is not allowed in this context, and the user-defi ned function or aggregate "%.*ls" could not be found. 343 15 Unknown object type '%.*ls' used in a CREATE, DROP, or ALTER sta tement. 344 16 Remote function reference '%.*ls' is not allowed, and the column name '%.*ls' could not be found or is ambiguous. 345 16 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 fu nction is assumed by default to perform data access if it is not schemabound. 346 15 The parameter "%.*ls" can not be declared READONLY since it is n ot a table-valued parameter. 347 16 The table-valued parameter "%.*ls" cannot be declared as an OUTP UT parameter. 348 16 The table variable "%.*ls" can not be passed to a stored procedu re with the OUTPUT option. 349 16 The procedure "%.*ls" has no parameter named "%.*ls". 350 16 The column "%.*ls" does not have a valid data type. A column can not be of a user-defined table type. 351 16 Column, parameter, or variable %.*ls. : Cannot find data type %. *ls. 352 15 The table-valued parameter "%.*ls" must be declared with the REA DONLY option. 353 16 Function '%.*ls' is not allowed in the %S_MSG clause when the FR

OM 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 perfo rm this access. By default, a function is assumed to perform data access if it i s not schema-bound. 354 16 The target '%.*ls' of the INSERT statement cannot be a view or c ommon table expression when the FROM clause contains a nested INSERT, UPDATE, DE LETE, or MERGE statement. 355 16 The target table '%.*ls' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 356 16 The target table '%.*ls' of the INSERT statement cannot be on ei ther side of a (primary key, foreign key) relationship when the FROM clause cont ains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constr aint '%ls'. 357 16 The target table '%.*ls' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule '%ls'. 358 16 The target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'. 359 16 The target '%.*ls' of an OUTPUT INTO clause has an index with th e ignore_dup_key option and cannot be used when an OUTPUT clause is also used. 360 16 The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both. 361 16 The number of target columns that are specified in an INSERT, UP DATE, or MERGE statement exceeds the maximum of %d. This total number includes i dentity, 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 . 362 16 The query processor could not produce a query plan because the n ame '%.*ls' in the FORCESEEK hint on table or view '%.*ls' did not match the key column names of the index '%.*ls'. 363 16 The query processor could not produce a query plan because the F ORCESEEK hint on table or view '%.*ls' cannot be used with the %S_MSG specified by index '%.*ls'. 364 16 The query processor could not produce a query plan because the F ORCESEEK hint on view '%.*ls' is used without a NOEXPAND hint. Resubmit the quer y with the NOEXPAND hint or remove the FORCESEEK hint on the view. 365 16 The query processor could not produce a query plan because the F ORCESEEK hint on table or view '%.*ls' specified more seek columns than the numb er of key columns in index '%.*ls'. 366 16 The query processor could not produce a query plan because the F ORCESEEK hint on table or view '%.*ls' cannot be used with the column store inde x '%.*ls'. 401 16 Unimplemented statement or expression %ls. 402 16 The data types %s and %s are incompatible in the %s operator. 403 16 Invalid operator for data type. Operator equals %ls, type equals %ls. 404 16 The column reference "inserted.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement. 405 16 A remote table cannot be used as a DML target in a statement whi ch includes an OUTPUT clause or a nested DML statement. 406 16 %ls cannot be used in the PIVOT operator because it is not invar iant to NULLs. 407 16 Internal error. The string routine in file %hs, line %d failed w ith HRESULT 0x%x. 408 16 A constant expression was encountered in the ORDER BY list, posi tion %i. 412 16 The column "%.*ls" is not updatable because it is derived or con

stant. 413 16 Correlated parameters or sub-queries are not supported by the in line function "%.*ls". 414 16 UPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger. 415 16 DELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger. 416 16 The service queue "%.*ls" cannot be directly updated. 417 16 TOP is not allowed in an UPDATE or DELETE statement against a pa rtitioned view. 418 16 Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'. 421 16 The %ls data type cannot be selected as DISTINCT because it is n ot comparable. 422 16 Common table expression defined but not used. 423 16 Xml data type methods are not supported in check constraints. Cr eate a scalar user-defined function to wrap the method invocation. The error occ urred at table "%.*ls". 424 16 Xml data type methods are not supported in computed column defin itions of table variables and return tables of table-valued functions. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement. 425 16 Data type %ls of receiving variable is not equal to the data typ e %ls of column '%.*ls'. 426 16 The length %d of the receiving variable is less than the length %d of the column '%.*ls'. 427 20 Could not load the definition for constraint ID %d in database I D %d. Run DBCC CHECKCATALOG to verify the integrity of the database. 428 16 Insert bulk cannot be used in a multi-statement batch. 432 16 Xml data type methods are not supported in check constraints any more. Please drop the constraint or create a scalar user-defined function to wra p the method invocation. The error occurred at table "%.*ls". 434 16 Function '%ls' is not allowed in the OUTPUT clause. 435 16 Xml data type methods are not supported in computed column defin itions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement. 438 16 Xml data type methods are not allowed in rules. The error occurr ed at table "%.*ls". 440 16 Internal query compilation error. The stack overflow could not b e handled. 441 16 Cannot use the '%ls' function on a remote data source. 442 16 The NEST argument must be a column reference. Expressions are no t allowed. 443 16 Invalid use of a side-effecting operator '%s' within a function. 444 16 Select statements included within a function cannot return data to a client. 445 16 COLLATE clause cannot be used on expressions containing a COLLAT E clause. 446 16 Cannot resolve collation conflict between "%ls" and "%ls" in %ls operator for %ls operation. 447 16 Expression type %ls is invalid for COLLATE clause. 448 16 Invalid collation '%.*ls'. 449 16 Collation conflict caused by collate clauses with different coll ation '%.*ls' and '%.*ls'. 450 16 Code page translations are not supported for the text data type. From: %d To: %d. 451 16 Cannot resolve collation conflict between "%ls" and "%ls" in %ls operator occurring in %ls statement column %d. 452 16 COLLATE clause cannot be used on user-defined data types. 453 16 Collation '%.*ls' is supported on Unicode data types only and ca nnot be set at the database or server level.

454 16 The UNNEST argument must be a nested table column. 455 16 The last statement included within a function must be a return s tatement. 456 16 Implicit conversion of %ls value to %ls cannot be performed beca use the resulting collation is unresolved due to collation conflict between "%ls " and "%ls" in %ls operator. 457 16 Implicit conversion of %ls value to %ls cannot be performed beca use the collation of the value is unresolved due to a collation conflict between "%ls" and "%ls" in %ls operator. 458 16 Cannot create the SELECT INTO target table "%.*ls" because the x ml column "%.*ls" is typed with a schema collection "%.*ls" from database "%.*ls ". Xml columns cannot refer to schemata across databases. 459 16 Collation '%.*ls' is supported on Unicode data types only and ca nnot be applied to char, varchar or text data types. 460 16 DISTINCT operator is not allowed in the recursive part of a recu rsive common table expression '%.*ls'. 461 16 The TOP or OFFSET operator is not allowed in the recursive part of a recursive common table expression '%.*ls'. 462 16 Outer join is not allowed in the recursive part of a recursive c ommon table expression '%.*ls'. 463 16 Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'. 464 16 Functions with side effects are not allowed in the recursive par t of a recursive common table expression '%.*ls'. 465 16 Recursive references are not allowed in subqueries. 466 16 UNION operator is not allowed in the recursive part of a recursi ve common table expression '%.*ls'. 467 16 GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'. 468 16 Cannot resolve the collation conflict between "%.*ls" and "%.*ls " in the %ls operation. 469 16 An explicit column list must be specified for target table '%.*l s' when table hint KEEPIDENTITY is used and the table contains an identity colum n. 470 16 The synonym "%.*ls" referenced synonym "%.*ls". Synonym chaining is not allowed. 471 16 Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGL E_NCLOB, can be specified. 472 16 Either a format file or one of the three options SINGLE_BLOB, SI NGLE_CLOB, or SINGLE_NCLOB must be specified. 473 16 The incorrect value "%.*ls" is supplied in the PIVOT operator. 474 16 Unable to load the computed column definitions for table "%.*ls" . 475 16 Invalid SAMPLE clause. Only table names in the FROM clause of SE LECT, UPDATE, and DELETE queries may be sampled. 476 16 Invalid PERCENT tablesample size "%f" for table "%.*ls". The PER CENT tablesample size must be between 0 and 100. 477 16 Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer. 478 16 The TABLESAMPLE clause cannot be used in a view definition or in line table function definition. 479 16 Invalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0. 480 16 The TABLESAMPLE clause cannot be used with the table function "% .*ls". 481 16 The TABLESAMPLE clause cannot be used with the linked server tab le "%.*ls". 482 16 Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause. 483 16 The OUTPUT clause cannot be used in an INSERT...EXEC statement.

484 16 Cannot declare more than %d local variables. 485 16 Views and inline functions cannot return xml columns that are ty ped with a schema collection registered in a database other than current. Column "%.*ls" is typed with the schema collection "%.*ls", which is registered in dat abase "%.*ls". 486 16 "%.*ls" does not allow specifying a schema name as a prefix to t he assembly name. 487 16 An invalid option was specified for the statement "%.*ls". 488 16 %s columns must be comparable. The type of column "%.*ls" is "%s ", which is not comparable. 489 16 The OUTPUT clause cannot be specified because the target view "% .*ls" is a partitioned view. 490 16 The resync functionality is temporarily disabled. 491 16 A correlation name must be specified for the bulk rowset in the from clause. 492 16 Duplicate column names are not allowed in result sets obtained t hrough OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate. 493 16 The column '%.*ls' that was returned from the nodes() method can not be used directly. It can only be used with one of the four XML data type met hods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL chec ks. 494 16 The TABLESAMPLE clause can only be used with local tables. 495 16 The return table column "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 496 16 The parameter "%.*ls" is not the same type as the type it was cr eated with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 497 16 Variables are not allowed in the TABLESAMPLE or REPEATABLE claus es. 498 16 Invalid value in the TABLESAMPLE or the REPEATABLE clause. 499 16 Invalid parameter for the getchecksum function. 500 16 Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s). 505 16 The current user account was invoked with SETUSER or SP_SETAPPRO LE. Changing databases is not allowed. 506 16 The invalid escape character "%.*ls" was specified in a %ls pred icate. 507 16 Invalid argument for SET ROWCOUNT. Must be a non-null non-negati ve integer. 509 11 User name '%.*ls' not found. 510 16 Cannot create a worktable row larger than allowable maximum. Res ubmit your query with the ROBUST PLAN hint. 511 16 Cannot create a row of size %d which is greater than the allowab le maximum row size of %d. 512 16 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an exp ression. 513 16 A column insert or update conflicts with a rule imposed by a pre vious CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'. 515 16 Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails. 517 16 Adding a value to a '%ls' column caused an overflow. 518 16 Cannot convert data type %ls to %ls. 522 16 The WAITFOR thread was evicted. 523 16 A trigger returned a resultset and/or was running with SET NOCOU NT OFF while another outstanding result set was active. 524 16 A trigger returned a resultset and the server option 'disallow r esults from triggers' is true.

525 16 The column that was returned from the nodes() method cannot be c onverted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 526 16 %ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query. 527 16 Implicit conversion between XML types constrained by different X ML schema collections is not allowed. Use the CONVERT function to run this query . 529 16 Explicit conversion from data type %ls to %ls is not allowed. 530 16 The statement terminated. The maximum recursion %d has been exha usted before statement completion. 531 10 Cannot set NOCOUNT to OFF inside the trigger execution because t he server option "disallow_results_from_triggers" is true or we are inside LOGON trigger execution. 532 16 The timestamp (changed to %S_TS) shows that the row has been upd ated by another user. 533 15 Cannot set XACT ABORT to OFF inside the trigger execution. 534 16 '%.*ls' failed because it is not supported in the edition of thi s SQL Server instance '%.*ls'. See books online for more details on feature supp ort in different SQL Server editions. 535 16 The datediff function resulted in an overflow. The number of dat eparts separating two date/time instances is too large. Try to use datediff with a less precise datepart. 536 16 Invalid length parameter passed to the %ls function. 537 16 Invalid length parameter passed to the LEFT or SUBSTRING functio n. 539 16 Schema changed after the target table was created. Rerun the Sel ect Into query. 540 16 There is insufficient system memory to run RAISERROR. 541 16 There is not enough stack to execute the statement 542 16 An invalid datetime value was encountered. Value exceeds the yea r 9999. 543 16 Creation of a return table failed for the table valued function '%.*ls'. 544 16 Cannot insert explicit value for identity column in table '%.*ls ' when IDENTITY_INSERT is set to OFF. 545 16 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 ins erting into a NOT FOR REPLICATION identity column. 547 16 The %ls statement conflicted with the %ls constraint "%.*ls". Th e conflict occurred in database "%.*ls", table "%.*ls"%ls%.*ls%ls. 548 16 The insert failed. It conflicted with an identity range check co nstraint in database '%.*ls', replicated table '%.*ls'%ls%.*ls%ls. If the identi ty column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. 549 16 The collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'. 550 16 The attempted insert or update failed because the target view ei ther specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTIO N and one or more rows resulting from the operation did not qualify under the CH ECK OPTION constraint. 552 16 CryptoAPI function '%ls' failed. Error 0x%x: %ls 555 16 User-defined functions are not yet enabled. 556 16 INSERT EXEC failed because the stored procedure altered the sche ma of the target table. 557 16 Only functions and some extended stored procedures can be execut ed from within a function.

558 16 Remote function calls are not allowed within a function. 561 16 Failed to access file '%.*ls' 562 16 Failed to access file '%.*ls'. Files can be accessed only throug h shares 563 14 The transaction for the INSERT EXEC statement has been rolled ba ck. The INSERT EXEC operation will be terminated. 564 16 Attempted to create a record with a fixed length of '%d'. Maximu m allowable fixed length is '%d'. 565 18 A stack overflow occurred in the server while compiling the quer y. Please simplify the query. 566 21 An error occurred while writing an audit trace. SQL Server is sh utting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by start ing the server at the command prompt with the "-f" switch, and using SP_CONFIGUR E. 567 16 File '%.*ls' is not a recognizable trace file. 568 16 Encountered an error or an unexpected end of trace file '%.*ls'. 569 16 The handle that was passed to %ls was invalid. 570 15 INSTEAD OF triggers do not support direct recursion. The trigger execution failed. 571 16 The specified attribute value for %ls is invalid. 572 16 Invalid regular expression "%.*ls" near the offset %d. 573 16 Evaluation of the regular expression is too complex: '%.*ls'. 574 16 %ls statement cannot be used inside a user transaction. 575 16 A LOGON trigger returned a resultset. Modify the LOGON trigger t o not return resultsets. 576 16 Cannot create a row that has sparse data of size %d which is gre ater than the allowable maximum sparse data size of %d. 577 16 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647. 578 16 Insert Exec not allowed in WAITFOR queries. 579 16 Can not execute WAITFOR query with snapshot isolation level. 582 16 Offset is greater than the length of the column to be updated in write. 583 16 Negative offset or length in write. 584 16 Select Into not allowed in WAITFOR queries. 585 16 Changing database context is not allowed when populating the res ource database. 586 16 The prepared statement handle %d is not valid in this context. Please verify that current database, user default schema, and ANSI_NULLS and QUO TED_IDENTIFIER set options are not changed since the handle is prepared. 587 16 An invalid delayed CLR type fetch token is provided. 588 16 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time. 589 16 This statement has attempted to access data whose access is rest ricted by the assembly. 590 16 RPC was aborted without execution. 591 16 %ls: The formal parameter "%ls" was defined as OUTPUT, but the a ctual parameter was not declared as OUTPUT. 592 16 Cannot find %S_MSG ID %d in database ID %d. 593 10 fn_trace_gettable: XML conversion of trace data for event 165 fa iled. 594 10 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode. 595 16 Bulk Insert with another outstanding result set should be run wi th XACT_ABORT on. 596 16 Cannot continue the execution because the session is in the kill state. 597 16 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).

598 16 An error occurred while executing CREATE/ALTER DB. Please look a t the previous error for more information. 599 16 %.*ls: The length of the result exceeds the length limit (2GB) o f the target large type. 601 12 Could not continue scan with NOLOCK due to data movement. 602 21 Could not find an entry for table or index with partition ID %I6 4d in database %d. This error can occur if a stored procedure references a dropp ed table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 603 21 Could not find an entry for table or index with object ID %d (pa rtition ID %I64d) in database %d. This error can occur if a stored procedure ref erences a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 605 21 Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d. 606 21 Metadata inconsistency. Filegroup id %ld specified for table '% .*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG. 608 16 No catalog entry found for partition ID %I64d in database %d. Th e metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption. 609 16 BTree is not empty when waking up on RowsetBulk. 610 16 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption. 611 16 Cannot insert or update a row because total variable column size , including overhead, is %d bytes more than the limit. 613 21 Could not find an entry for worktable rowset with partition ID % I64d in database %d. 614 16 Could not locate bookmark due to data movement. 615 21 Could not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again. 617 20 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor. 622 16 The filegroup "%.*ls" has no files assigned to it. Tables, index es, text columns, ntext columns, and image columns cannot be populated on this f ilegroup until a file is added. 627 16 Cannot use SAVE TRANSACTION within a distributed transaction. 628 16 Cannot issue SAVE TRANSACTION when there is no active transactio n. 650 16 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. 651 16 Cannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited. 652 16 The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified. 657 16 Increased partitions support cannot be removed in this version o f SQL Server. 666 16 The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the ind ex may resolve this; otherwise, use another clustering key. 667 16 The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, is being re stored, or is defunct. 669 22 The row object is inconsistent. Please rerun the query. 670 16 Large object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed. 671 16 Large object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified. 672 10 Failed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on data base restart.

674 10 Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used duri ng bulk-insert operations. Restart the server to resolve this problem. 675 10 Worktable with partition ID %I64d was dropped successfully after %d repeated attempts. 676 10 Error occurred while attempting to drop worktable with partition ID %I64d. 677 10 Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational messag e only. No user action is required. 678 10 Active rowset for partition ID %I64d found at the end of the bat ch. This error may indicate incorrect exception handling. Use the current activi ty window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the er ror. 679 16 One of the partitions of index '%.*ls' for table '%.*ls'(partiti on ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result. 680 10 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d. 681 16 Attempting to set a non-NULL-able column's value to NULL. 682 16 Internal error. Buffer provided to read column value is too smal l. Run DBCC CHECKDB to check for any corruption. 683 22 An internal error occurred while trying to convert between varia ble-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption. 684 22 An internal error occurred while attempting to convert between c ompressed and uncompressed storage formats. Run DBCC CHECKDB to check for any c orruption. 685 22 An internal error occurred while attempting to retrieve a backpo inter for a heap forwarded record. 686 22 The maximum level of the B-Tree for rowset %I64d has been reache d. SQL Server only supports upto 255 levels. 687 16 Cannot compress a nchar or nvarchar column that has an odd numbe r of bytes. 688 16 Operation not allowed due to an active online index build. 689 16 Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation. 701 19 There is insufficient system memory in resource pool '%ls' to ru n this query. 708 10 Server is running low on virtual address space or machine is run ning low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications. 801 20 A buffer was encountered with an unexpected status of 0x%x. 802 17 There is insufficient memory available in the buffer pool. 803 10 simulated failure (DEBUG only) 805 10 restore pending 806 10 audit failure (a page read from disk failed to pass basic integr ity checks) 807 10 (no disk or the wrong disk is in the drive) 808 10 insufficient bytes transferred 821 20 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_PAG E. Contact Technical Support. 822 21 Could not start I/O operation for request %S_BLKIOPTR. Contact T echnical Support. 823 24 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 e rror log and system event log may provide more detail. This is a severe system-l evel error condition that threatens database integrity and must be corrected imm

ediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online . 824 24 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 %#016I64 x in file '%ls'. Additional messages in the SQL Server error log or system even t log may provide more detail. This is a severe error condition that threatens d atabase integrity and must be corrected immediately. Complete a full database co nsistency check (DBCC CHECKDB). This error can be caused by many factors; for mo re information, see SQL Server Books Online. 825 10 A read of the file '%ls' at offset %#016I64x succeeded after fai ling %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 da tabase integrity and must be corrected. Complete a full database consistency che ck (DBCC CHECKDB). This error can be caused by many factors; for more informatio n, see SQL Server Books Online. 826 10 incorrect pageid (expected %d:%d; actual %d:%d) 829 21 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore. 830 10 stale page (a page read returned a log sequence number (LSN) (%u :%u:%u) that is older than the last one that was written (%u:%u:%u)) 831 20 Unable to deallocate a kept page. 832 24 A page that should have been constant has changed (expected chec ksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption. 833 10 SQL Server has encountered %d occurrence(s) of I/O requests taki ng longer than %d seconds to complete on file [%ls] in database [%ls] (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x 844 10 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 seconds, flags 0x%I64x, owning task 0x%p. Continuing to wai t. 845 17 Time-out occurred while waiting for buffer latch type %d for pag e %S_PGID, database ID %d. 846 10 A time-out occurred while waiting for buffer latch -- type %d, b p %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Not continuing to wait. 847 10 Timeout occurred while waiting for latch: class '%ls', id %p, ty pe %d, Task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Con tinuing to wait. 848 10 Using large pages in the memory manager. 849 10 Using locked pages in the memory manager. 850 10 %I64u MB of large page memory allocated. 851 10 the page is in an OFFLINE file which cannot be read 852 10 Using conventional memory in the memory manager. 853 10 Latch acquire failed due to too many concurrent latches. type %d , Task 0x%p : %d 854 10 Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption. 855 10 Uncorrectable hardware memory corruption detected. Your system m ay become unstable. Please check the Windows event log for more details. 856 10 SQL Server has detected hardware memory corruption in database ' %ls', file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully rec overed the page. 902 16 To change the %ls, the database must be in state in which a chec kpoint can be executed. 904 16 Database %ld cannot be autostarted during server shutdown or sta rtup. 905 21 Database '%.*ls' cannot be started in this edition of SQL Server

because it contains a partition function '%.*ls'. Only Enterprise edition of SQ L Server supports partitioning. 907 16 The database "%ls" has inconsistent database or file metadata. 908 10 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available. 909 21 Database '%.*ls' cannot be started in this edition of SQL Server because part or all of object '%.*ls' is enabled with data compression or varde cimal storage format. Data compression and vardecimal storage format are only su pported on SQL Server Enterprise Edition. 910 10 Database '%.*ls' is upgrading script '%.*ls' from level %d to le vel %d. 911 16 Database '%.*ls' does not exist. Make sure that the name is ente red correctly. 912 21 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' encountered error %d, state %d, severity %d. This is a serious err or 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 previ ous errorlog entries for errors, take the appropriate corrective actions and restart the database so that the script upgrade steps run to completion. 913 22 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 y ou do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. 914 21 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' was aborted before completion. If the abort happened during upgrad e of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriat e corrective actions and re-start the database so that the script upgrade steps run to completion. 915 21 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 entr ies for errors, take the appropriate corrective actions and re-start the databa se so that script upgrade may run to completion. 916 14 The server principal "%.*ls" is not able to access the database "%.*ls" under the current security context. 917 21 An upgrade script batch failed to execute for database '%.*ls' d ue to compilation error. Check the previous error message for the line which ca used compilation to fail. 918 21 Failed to load the engine script metadata from script DLL '%.*ls '. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error. 919 10 User '%.*ls' is changing database script level entry %d to a val ue of %d. 920 20 Only members of the sysadmin role can modify the database script level. 921 14 Database '%.*ls' has not been recovered yet. Wait and try again. 922 14 Database '%.*ls' is being recovered. Waiting until recovery is f inished. 923 14 Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it. 924 14 Database '%.*ls' is already open and can only have one user at a time. 925 19 Maximum number of databases used for each query has been exceede d. The maximum allowed is %d. 926 14 Database '%.*ls' cannot be opened. It has been marked SUSPECT by

recovery. See the SQL Server errorlog for more information. 927 14 Database '%.*ls' cannot be opened. It is in the middle of a rest ore. 928 20 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause. 929 20 Unable to close a database that is not currently open. The appli cation should reconnect and try again. If this action does not correct the probl em, contact your primary support provider. 930 21 Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support. 932 21 SQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support chang e 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 track ing. 933 21 Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server. 934 21 SQL Server cannot load database '%.*ls' because Change Data Capt ure is enabled. The currently installed edition of SQL Server does not support C hange Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture. 935 21 The script level for '%.*ls' in database '%.*ls' cannot be downg raded from %d to %d, which is supported by this server. This usually implies tha t 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. 936 16 Database '%.*ls' can not be used in this edition of SQL Server. 937 21 Database '%.*ls' cannot be upgraded because '%.*ls' functionalit y is not available in the current edition of SQL Server. 941 16 Database '%.*ls' cannot be opened because it is not started. Ret ry when the database is started. 942 14 Database '%.*ls' cannot be opened because it is offline. 943 14 Database '%.*ls' cannot be opened because its version (%d) is la ter than the current server version (%d). 944 10 Converting database '%.*ls' from version %d to the current versi on %d. 945 16 Database '%.*ls' cannot be opened due to inaccessible files or i nsufficient memory or disk space. See the SQL Server errorlog for details. 946 14 Cannot open database '%.*ls' version %d. Upgrade the database to the latest version. 947 16 Error while closing database '%.*ls'. Check for previous additio nal errors and retry the operation. 948 20 The database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported. 949 16 tempdb is skipped. You cannot run a query that requires tempdb 950 20 Database '%.*ls' cannot be upgraded because its non-release vers ion (%d) is not supported by this version of SQL Server. You cannot open a datab ase that is incompatible with this version of sqlservr.exe. You must re-create t he database. 951 10 Database '%.*ls' running the upgrade step from version %d to ver sion %d. 952 16 Database '%.*ls' is in transition. Try the statement later. 954 14 The database "%.*ls" cannot be opened. It is acting as a mirror database. 955 14 Database %.*ls is enabled for Database Mirroring, but the databa se lacks quorum: the database cannot be opened. Check the partner and witness c onnections if configured. 956 14 Database %.*ls is enabled for Database Mirroring, but has not ye t synchronized with its partner. Try the operation again later.

957 17 Database '%.*ls' is enabled for database mirroring or has joined an availability group. The name of the database cannot be changed. 958 10 The resource database build version is %.*ls. This is an informa tional message only. No user action is required. 959 20 The resource database version is %d and this server supports ver sion %d. Restore the correct version or reinstall SQL Server. 960 10 Warning: User "sys" (principal_id = %d) in database "%.*ls" has been renamed to "%.*ls". "sys" is a reserved user or schema name in this version of SQL Server. 961 10 Warning: Index "%.*ls" (index_id = %d) on object ID %d in databa se "%.*ls" was renamed to "%.*ls" because its name is a duplicate of another ind ex on the same object. 962 10 Warning: Primary key or Unique constraint "%.*ls" (object_id = % d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed. 963 10 Warning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER D ATABASE to bring the database online. The database will come online in restricte d_user state. 964 10 Warning: System user '%.*ls' was found missing from database '%. *ls' and has been restored. This user is required for SQL Server operation. 965 10 Warning: A column nullability inconsistency was detected in the metadata of index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls". T he index may be corrupt. Run DBCC CHECKTABLE to verify consistency. 966 10 Warning: Assembly "%.*ls" in database "%.*ls" has been renamed t o "%.*ls" because the name of the assembly conflicts with a system assembly in t his version of SQL Server. 967 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled becaus e the XML data bound to it may contain negative values for xs:date and xs:dateTi me which are not longer supported. 968 10 Warning: The XML facet on type "%.*ls" in schema collection "%.* ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negat ive years inside values of type xs:date or xs:dateTime. 969 10 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:d ateTime. 970 10 Warning: The XML instances in the XML column "%.*ls.%.*ls.%.*ls" may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary XML index on these XML instances . 971 10 The resource database has been detected in two different locatio ns. Attaching the resource database in the same directory as sqlservr.exe at '%. *ls' instead of the currently attached resource database at '%.*ls'. 972 17 Could not use database '%d' during procedure execution. 974 10 Attaching the resource database in the same directory as sqlserv r.exe at '%.*ls' failed as the database files do not exist. 975 10 System objects could not be updated in database '%.*ls' because it is read-only. 976 14 The target database, '%.*ls', is participating in an availabilit y group and is currently not accessible for queries. Either data movement is sus pended or the availability replica is not enabled for read access. To allow read -only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more in formation, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online . 977 10 Warning: Could not find associated index for the constraint '%.* ls' on object_id '%d' in database '%.*ls'. 978 14 The target database ('%.*ls') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Onlin

e. 979 14 The target database ('%.*ls') is in an availability group and cu rrently does not allow read only connections. For more information about applica tion intent, see SQL Server Books Online. 980 21 SQL Server cannot load database '%.*ls' because it contains a co lumnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by usi ng a supported edition of SQL Server, or upgrade the instance of SQL Server to a version that supports columnstore index. 981 10 Database manager will be using %d target database version. 982 14 Unable to access the '%.*ls' database because no online secondar y replicas are enabled for read-only access. Check the availability group config uration to verify that at least one secondary replica is configured for read-onl y access. Wait for an enabled replica to come online, and retry your read-only o peration. 983 14 Unable to access database '%.*ls' because its replica role is RE SOLVING which does not allow connections. Try the operation again later. 984 21 Failed to perform a versioned copy of sqlscriptdowngrade.dll fro m Binn to Binn\Cache folder. VerInstallFile API failed with error code %d. 985 10 Successfully installed the file '%ls' into folder '%ls'. 1001 16 Line %d: Length or precision specification %d is invalid. 1002 16 Line %d: Specified scale %d is invalid. 1003 15 Line %d: %ls clause allowed only for %ls. 1004 16 Invalid column prefix '%.*ls': No table name specified 1005 15 Line %d: Invalid procedure number (%d). Must be between 1 and 32 767. 1006 15 CREATE TRIGGER contains no statements. 1007 15 The %S_MSG '%.*ls' is out of the range for numeric representatio n (maximum precision 38). 1008 15 The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only allowed when ordering by an expression referencing a column name. 1009 16 The keyword DEFAULT is not allowed in DBCC commands. 1010 15 Invalid escape character '%.*ls'. 1011 15 The correlation name '%.*ls' is specified multiple times in a FR OM clause. 1012 15 The correlation name '%.*ls' has the same exposed name as table '%.*ls'. 1013 15 The objects "%.*ls" and "%.*ls" in the FROM clause have the same exposed names. Use correlation names to distinguish them. 1014 15 A TOP or FETCH clause contains an invalid value. 1015 15 An aggregate cannot appear in an ON clause unless it is in a sub query contained in a HAVING clause or select list, and the column being aggregat ed is an outer reference. 1016 15 Outer join operators cannot be specified in a query containing j oined tables. 1017 15 The %ls hint cannot be specified more than once. 1018 15 Incorrect syntax near '%.*ls'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Bo oks Online for proper syntax. 1019 15 Invalid column list after object name in GRANT/REVOKE statement. 1020 15 Sub-entity lists (such as column or security expressions) cannot be specified for entity-level permissions. 1021 10 FIPS Warning: Line %d has the non-ANSI statement '%ls'. 1022 10 FIPS Warning: Line %d has the non-ANSI clause '%ls'. 1023 15 Invalid parameter %d specified for %ls. 1024 10 FIPS Warning: Line %d has the non-ANSI function '%ls'. 1025 10 FIPS Warning: The length of identifier '%.*ls' exceeds 18. 1026 16 GOTO cannot be used to jump into a TRY or CATCH scope. 1028 15 The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed i

n a GROUP BY ALL clause. 1029 15 Browse mode is invalid for subqueries and derived tables. 1030 16 Only constants are allowed here. Time literal is not permitted b ecause it refers to the current date. 1031 15 Percent values must be between 0 and 100. 1032 16 Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'. 1033 16 The ORDER BY clause is invalid in views, inline functions, deriv ed tables, subqueries, and common table expressions, unless TOP, OFFSET or FOR X ML is also specified. 1034 15 Syntax error: Duplicate specification of the action "%.*s" in th e trigger declaration. 1035 15 Incorrect syntax near '%.*ls', expected '%.*ls'. 1036 15 File option %hs is required in this CREATE/ALTER DATABASE statem ent. 1037 15 The CASCADE, WITH GRANT or AS options cannot be specified with s tatement permissions. 1038 15 An object or column name is missing or empty. For SELECT INTO st atements, verify each column has a name. For other statements, look for empty al ias names. Aliases defined as "" or [] are not allowed. Change the alias to a va lid name. 1039 16 Option '%.*ls' is specified more than once. 1041 15 Option %.*ls is not allowed for a LOG file. 1042 15 Conflicting %ls optimizer hints specified. 1043 16 '%.*ls' is not yet implemented. 1044 15 Cannot use an existing function name to specify a stored procedu re name. 1045 15 Aggregates are not allowed in this context. Only scalar expressi ons are allowed. 1046 15 Subqueries are not allowed in this context. Only scalar expressi ons are allowed. 1047 15 Conflicting locking hints specified. 1048 15 Conflicting cursor options %ls and %ls. 1049 15 Mixing old and new syntax to specify cursor options is not allow ed. 1050 15 This syntax is only allowed for parameterized queries. 1051 15 Cursor parameters in a stored procedure must be declared with OU TPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT. 1052 15 Conflicting %ls options "%ls" and "%ls". 1053 15 For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname". 1054 15 Syntax '%ls' is not allowed in schema-bound objects. 1055 15 '%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character. 1056 15 The number of elements in the select list exceeds the maximum al lowed number of %d elements. 1057 15 The IDENTITY function cannot be used with a SELECT INTO statemen t containing a UNION, INTERSECT or EXCEPT operator. 1058 15 Cannot specify both READ_ONLY and FOR READ ONLY on a cursor decl aration. 1059 15 Cannot set or reset the 'parseonly' option within a procedure or function. 1060 15 The number of rows provided for a TOP or FETCH clauses row count parameter must be an integer. 1061 16 The text/ntext/image constants are not yet implemented. 1062 16 The TOP N WITH TIES clause is not allowed without a correspondin g ORDER BY clause. 1063 16 A filegroup cannot be added using ALTER DATABASE ADD FILE. Use A LTER DATABASE ADD FILEGROUP.

1064 16 A filegroup cannot be used with log files. 1065 15 The NOLOCK and READUNCOMMITTED lock hints are not allowed for ta rget tables of INSERT, UPDATE, DELETE or MERGE statements. 1066 10 Warning. Line %d: The option '%ls' is obsolete and has no effect . 1067 15 The SET SHOWPLAN statements must be the only statements in the b atch. 1068 16 Only one list of index hints per table is allowed. 1069 16 Index hints are only allowed in a FROM or OPTION clause. 1070 15 CREATE INDEX option '%.*ls' is no longer supported. 1071 16 Cannot specify a JOIN algorithm with a remote JOIN. 1072 16 A REMOTE hint can only be specified with an INNER JOIN clause. 1073 15 '%.*ls' is not a recognized cursor option for cursor %.*ls. 1074 15 Creation of temporary functions is not allowed. 1075 15 RETURN statements in scalar valued functions must include an arg ument. 1076 15 Function '%s' requires at least %d argument(s). 1077 15 INSERT into an identity column not allowed on table variables. 1078 15 '%.*ls %.*ls' is not a recognized option. 1079 15 A variable cannot be used to specify a search condition in a ful ltext predicate when accessed through a cursor. 1080 15 The integer value %.*ls is out of range. 1081 16 %s does not allow specifying the database name as a prefix to th e assembly name. 1082 15 "%.*ls" does not support synchronous trigger registration. 1083 15 OWNER is not a valid option for EXECUTE AS in the context of ser ver and database level triggers. 1084 15 '%.*ls' is an invalid event type. 1085 15 '%.*ls' event type does not support event notifications. 1086 16 The FOR XML clause is invalid in views, inline functions, derive d 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 XM L on top of it. 1087 15 Must declare the table variable "%.*ls". 1088 15 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 1089 15 The SET FMTONLY OFF statement must be the last statement in the batch. 1090 15 Invalid default for parameter %d. 1091 15 The option "%ls" is not valid for this function. 1092 16 In this context %d statistics name(s) cannot be specified for op tion '%ls'. 1093 16 "%.*ls" is not a valid broker name. 1094 15 Cannot specify a schema name as a prefix to the trigger name for database and server level triggers. 1095 15 "%.*ls" has already been specified as an event type. 1096 15 Default parameter values for CLR types, nvarchar(max), varbinary (max), and xml are not supported. 1097 15 Cannot use If UPDATE within this CREATE TRIGGER statement. 1098 15 The specified event type(s) is/are not valid on the specified ta rget object. 1099 15 The ON clause is not valid for this statement. 1101 17 Could not allocate a new page for database '%.*ls' because of in sufficient disk space in filegroup '%.*ls'. Create the necessary space by droppi ng objects in the filegroup, adding additional files to the filegroup, or settin g autogrowth on for existing files in the filegroup. 1105 17 Could not allocate space for object '%.*ls'%.*ls in database '%. *ls' because the '%.*ls' filegroup is full. Create disk space by deleting unneed ed files, dropping objects in the filegroup, adding additional files to the file group, or setting autogrowth on for existing files in the filegroup.

1119 16 Removing IAM page %S_PGID failed because someone else is using t he object that this IAM page belongs to. 1121 17 Space allocator cannot allocate page in database %d. 1122 14 Table error: Page %S_PGID. Test (%ls) failed. Address 0x%x is no t aligned. 1123 14 Table error: Page %S_PGID. Unexpected page type %d. 1124 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x %x is invalid. 1125 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, row exten ds into free space at 0x%x. 1126 14 Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x %x overlaps with the prior row. 1127 14 Table error: Page %S_PGID. Test (%ls) failed. Values are %ld and %ld. 1128 14 Table error: Page (%d:%d), row %d. Test (%.*ls) failed. Values a re %ld and %ld. 1129 16 Could not cleanup deferred deallocations from filegroup '%.*ls'. 1130 10 Error while allocating extent for a worktable. Extent %S_PGID i n TEMPDB may have been lost. 1131 10 Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next t ime. This is an informational message only. No user action is required. 1202 16 The database-principal '%.*ls' does not exist or user is not a m ember. 1203 20 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 conditi on. If the problem persists, contact the database administrator. 1204 19 The instance of the SQL Server Database Engine cannot obtain a L OCK resource at this time. Rerun your statement when there are fewer active user s. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. 1205 13 Transaction (Process ID %d) was deadlocked on %.*ls resources wi th another process and has been chosen as the deadlock victim. Rerun the transac tion. 1206 18 The Microsoft Distributed Transaction Coordinator (MS DTC) has c ancelled the distributed transaction. 1207 10 Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB . 1208 21 Could not allocate initial %u lock blocks during startup. Can n ot start the server. 1209 21 Could not allocate initial %u lock owner blocks during startup. Can not start the server. 1210 21 Unable to allocate lock owner block during lock migration. Serve r halted. 1212 10 Lock not logged: %-30ls Mode: %s 1213 21 Error spawning Lock Monitor thread: %ls 1214 17 Internal Error. There are too many parallel transactions. 1220 17 No more lock classes available from transaction. 1221 20 The Database Engine is attempting to release a group of locks th at are not currently held by the transaction. Retry the transaction. If the prob lem persists, contact your support provider. 1222 16 Lock request time out period exceeded. 1223 16 Cannot release the application lock (Database Principal: '%.*ls' , Resource: '%.*ls') because it is not currently held. 1224 16 An invalid application lock resource was passed to %ls. 1225 16 An invalid application lock mode was passed to %ls. 1226 16 An invalid application lock owner was passed to %ls. 1227 16 An invalid application lock time-out was passed to %ls. 1228 16 An invalid parameter "%ls" was passed to the application lock fu nction or procedure.

1230 16 An invalid database principal was passed to %ls. 1401 21 Startup of the database-mirroring master thread routine failed f or the following reason: %ls. Correct the cause of this error, and restart the S QL Server service. 1402 20 Witness did not find an entry for database mirroring GUID {%.8x%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. R etry the command, or reset the witness from one of the database mirroring partne rs. 1403 16 The witness for the mirroring session received error response %d (state %d) from server instance %.*ls for database %.*ls. For more information about the error, refer to the error log on this server instance and the partner server instance. 1404 16 The command failed because the database mirror is busy. Reissue the command later. 1405 16 The database "%.*ls" is already enabled for database mirroring. 1406 16 Unable to force service safely. Remove database mirroring and re cover database "%.*ls" to gain access. 1407 16 The remote copy of database "%.*ls" is not related to the local copy of the database. 1408 16 The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring or to join it to the availability group. You need t o apply missing log records to the remote database by restoring the current log backups from the principal/primary database. 1409 16 Database "%.*ls" requires database logs to be restored either on the future mirror database before you can enable database mirroring or on a sec ondary availability database before you can join it to the availability group. R estore current log backups from the principal database or primary database. 1410 16 The remote copy of database "%.*ls" is already enabled for datab ase mirroring. 1411 16 The remote copy of database "%.*ls" has not had enough log backu ps applied to roll forward all of its files to a common point in time. 1412 16 The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log. 1413 16 Communications to the remote server instance '%.*ls' failed befo re database mirroring was fully started. The ALTER DATABASE command failed. Retr y the command when the remote database is started. 1414 16 The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed. 1415 16 The database mirroring operation for database "%.*ls" failed. Th e requested operation could not be performed. 1416 16 Database "%.*ls" is not configured for database mirroring. 1417 16 Database mirroring has been disabled by the administrator for da tabase "%.*ls". 1418 16 The server network address "%.*ls" can not be reached or does no t exist. Check the network address name and that the ports for the local and rem ote endpoints are operational. 1419 16 The remote copy of database "%.*ls" cannot be opened. Check the database name and ensure that it is in the restoring state, and then reissue the command. 1420 16 Database mirroring was unable to obtain the network hostname. Op erating system error %ls encountered. Verify the network configuration. 1421 16 Communications to the remote server instance '%.*ls' failed to c omplete before its timeout. The ALTER DATABASE command may have not completed. R etry the command. 1422 16 The mirror server instance is not caught up to the recent change s to database "%.*ls". Unable to fail over. 1423 16 The property name is not supported. 1424 16 The remote server instance has a more recent value for the prope rty '%.*ls'. Property value not changed. 1425 16 The property value is invalid for '%.*ls'. Property value not c

hanged. 1426 16 To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these co nditions are met, reissue the command. 1427 16 The server instance '%.*ls' could not act as the witness. The AL TER DATABASE SET WITNESS command failed. 1428 16 The request is refused because the responding server instance is not in a state to service the request. 1429 16 The witness server instance name must be distinct from both of t he server instances that manage the database. The ALTER DATABASE SET WITNESS com mand failed. 1430 16 Database '%.*ls' is in an unstable state for removing database m irroring, so recovery may fail. Verify the data after recovery. 1431 16 Neither the partner nor the witness server instance for database "%.*ls" is available. Reissue the command when at least one of the instances be comes available. 1432 10 Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner. 1433 16 All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness ass ociated with the database. Verify the status and when necessary repeat the comma nd. 1434 16 Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls. 1435 16 %ls received unexpected database mirroring error response: statu s %u, severity %u, state %u, string %.*ls. 1436 16 The Service Broker ID for the remote copy of database "%.*ls" do es not match the ID on the principal server. 1437 16 Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase syste m memory. 1438 16 The server instance %ls rejected configure request; read its err or log file for more information. The reason %u, and state %u, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry. 1439 16 There is currently no witness associated with database "%.*ls". 1440 10 Database mirroring is active with database '%.*ls' as the princi pal copy. This is an informational message only. No user action is required. 1441 10 Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required. 1442 10 Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required. 1443 10 Database mirroring has been terminated for database '%.*ls'. Thi s is an informational message only. No user action is required. 1444 10 Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message onl y. No user action is required. 1445 10 Bypassing recovery for database '%ls' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring s ession. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change. 1446 10 The "%.*ls" server instance is already acting as the witness. 1447 16 ALTER DATABASE "%.*ls" command cannot be executed until both par tner server instances are up, running, and connected. Start the partner and reis sue the command. 1448 16 The remote copy of database "%.*ls" does not exist. Check the da tabase name and reissue the command. 1449 16 ALTER DATABASE command failed due to an invalid server connectio

n string. 1450 16 The ALTER DATABASE command failed because the worker thread cann ot be created. 1451 16 Database mirroring information was not found in the system table . 1452 16 The partner server instance name must be distinct from the serve r instance that manages the database. The ALTER DATABASE SET PARTNER command fai led. 1453 17 '%.*ls', the remote mirroring partner for database '%.*ls', enco untered error %d, status %d, severity %d. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirrori ng and re-establish the mirror server instance. 1454 17 Database mirroring will be suspended. Server instance '%.*ls' en countered error %d, state %d, severity %d when it was acting as a mirroring part ner for database '%.*ls'. The database mirroring partners might try to recover a utomatically from the error and resume the mirroring session. For more informati on, view the error log for additional error messages. 1455 16 The database mirroring service cannot be forced for database "%. *ls" because the database is not in the correct state to become the principal da tabase. 1456 16 The ALTER DATABASE command could not be sent to the remote serve r instance '%.*ls'. The database mirroring configuration was not changed. Verify that the server is connected, and try again. 1457 23 Synchronization of the mirror database, '%.*ls', was interrupted , leaving the database in an inconsistent state. The ALTER DATABASE command fail ed. 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 fini sh synchronizing. 1458 17 The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirro ring has been suspended. Try to resolve the error condition, and resume mirrorin g. 1459 24 An error occurred while accessing the database mirroring metadat a. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it. 1460 16 The database "%.*ls" is already configured for database mirrorin g on the remote server. Drop database mirroring on the remote server to establis h a new partner. 1461 10 Database mirroring successfully repaired physical page %S_PGID i n database "%.*ls" by obtaining a copy from the partner. 1462 16 Database mirroring is disabled due to a failed redo operation. U nable to resume. 1463 16 Database mirroring is not available in the edition of this SQL S erver instance. See books online for more details on feature support in differen t SQL Server editions. 1464 16 Database "%.*ls" is not in a recovering state which is required for a mirror database or secondary database. The remote database must be restore d using WITH NORECOVERY. 1465 16 Database "%.*ls" database is not in full recovery mode on each o f the server instances. The full recovery model is required for a database to pa rticipate in database mirroring or in an availability group. 1466 16 Database "%.*ls" is read-only on one of the server instances whi ch is incompatible with participating in database mirroring or in an availabilit y group. Set the database to read-write mode, and retry the operation. 1467 16 Database "%.*ls" database is in emergency or suspect mode on one of the partners which is incompatible with participating in database mirroring or in an availability group. 1468 16 The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session or an availability group. Some oper ations are not allowed on a database that is participating in a database mirrori

ng session or in an availability group. 1469 16 Database "%.*ls" is an auto-close database on one of the partner swhich is incompatible with participating in database mirroring or in an availab ility group. 1470 16 The alter database for this partner config values may only be in itiated on the current principal server for database "%.*ls". 1471 16 The database mirroring connection terminated. Out of memory send ing message for database "%.*ls". 1472 16 The database mirroring connection terminated. Communications err or sending message for database "%.*ls". 1473 16 This SQL Server edition does not allow changing the safety level . ALTER DATABASE command failed. 1474 16 Database mirroring connection error %d '%.*ls' for '%.*ls'. 1475 16 Database "%.*ls" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database . Then restore this backup either on the mirror database to enable database mirr oring or on every secondary database to enable you to join it to the availabilit y group. 1476 16 Database mirroring timeout value %d exceeds the maximum value 32 767. 1477 16 The database mirroring safety level must be FULL to manually fai lover database "%.*ls". Set safety level to FULL and retry. 1478 16 The mirror database, "%.*ls", has insufficient transaction log d ata to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database. 1479 16 The mirroring connection to "%.*ls" has timed out for database " %.*ls" after %d seconds without a response. Check the service and network conne ctions. 1480 10 The %S_MSG database "%.*ls" is changing roles from "%ls" to "%ls " because the mirroring session or availability group failed over due to %S_MSG. This is an informational message only. No user action is required. 1481 10 Database mirroring could not repair physical page %S_PGID in dat abase "%.*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 th at 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 th e sys.database_mirroring catalog view. If they are connected, for information ab out 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. 1482 10 Database mirroring failed to get snapshot synchrinization lock. 1485 10 Database mirroring has been enabled on this instance of SQL Serv er. 1486 10 Database Mirroring Transport is disabled in the endpoint configu ration. 1487 10 Database mirroring is starting %d parallel redo thread(s) with d atabase '%.*ls' as the mirror copy. This is an informational message only. No us er action is required. 1488 16 Database "%.*ls" database is in single user mode which is incomp atible with participating in database mirroring or in an availability group. Set database to multi-user mode, and retry the operation. 1489 10 Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information. 1490 16 The remote copy of database "%.*ls" has not been restored to a l og backup that includes all filestream data files. 1499 16 Database mirroring error: status %u, severity %u, state %u, stri ng %.*ls. 1501 20 Sort failure. Contact Technical Support. 1505 16 The CREATE UNIQUE INDEX statement terminated because a duplicate

key was found for the object name '%.*ls' and the index name '%.*ls'. The dupli cate key value is %ls. 1509 20 Row comparison failed during sort because of an unknown data typ e on a key column. Metadata might be corrupt. Contact Technical Support. 1510 17 Sort failed. Out of space or locks in database '%.*ls'. 1511 20 Sort cannot be reconciled with transaction log. 1522 20 Sort operation failed during an index build. The overwriting of the allocation page in database '%.*ls' was prevented by terminating the sort. R un DBCC CHECKDB to check for allocation and consistency errors. It may be necess ary restore the database from backup. 1523 20 Sort failure. The incorrect extent could not be deallocated. Con tact Technical Support. 1532 20 New sort run starting on page %S_PGID found an extent not marked as shared. Retry the transaction. If the problem persists, contact Technical Su pport. 1533 20 Cannot share extent %S_PGID. The correct extents could not be id entified. Retry the transaction. 1534 20 Extent %S_PGID not found in shared extent directory. Retry the t ransaction. If the problem persists, contact Technical Support. 1535 20 Cannot share extent %S_PGID. Shared extent directory is full. Re try the transaction. If the problem persists, contact Technical Support. 1537 20 Cannot suspend a sort that is not in row input phase. 1538 20 Cannot insert a row into a sort when the sort is not in row inpu t phase. 1540 16 Cannot sort a row of size %d, which is greater than the allowabl e maximum of %d. Consider resubmitting the query using the ROBUST PLAN hint. 1541 16 Sort failure. A defective CLR type comparison function is suspec ted. 1542 10 BobMgr::GetBuf: Sort Big Output Buffer write not complete after %d seconds. 1543 10 SQL Server encountered: '%ls' resulting from an attempt to read the following: sort run page %S_PGID, in file '%ls', in database with ID %d. Sor t is retrying the read. 1701 16 Creating or altering table '%.*ls' failed because the minimum ro w size would be %d, including %d bytes of internal overhead. This exceeds the ma ximum allowable table row size of %d bytes. 1702 16 CREATE TABLE failed because column '%.*ls' in table '%.*ls' exce eds the maximum of %d columns. 1706 16 The system table '%.*ls' can only be created or altered during a n upgrade. 1707 16 Cannot specify TEXTIMAGE_ON filegroup for a partitioned table. 1708 10 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 wi ll fail if the resulting row exceeds the size limit. 1709 16 Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), non-FILESTREAM varbinary(max), xml or large CLR typ e columns. 1710 10 Cannot use alias type with rule or default bound to it as a colu mn type in table variable or return table definition in table valued function. T ype '%.*ls' has a %S_MSG bound to it. 1711 16 Cannot define PRIMARY KEY constraint on column '%.*ls' in table '%.*ls'. The computed column has to be persisted and not nullable. 1712 16 Online index operations can only be performed in Enterprise edit ion of SQL Server. 1713 16 Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger. 1714 16 Alter table failed because unique column IDs have been exhausted for table '%.*ls'. 1715 16 Foreign key '%.*ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.*ls'.

1716 16 FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, or add a FILESTREA M column to the table. 1717 16 FILESTREAM_ON cannot be specified together with a partition sche me in the ON clause. 1718 16 Change tracking must be enabled on database '%.*ls' before it ca n be enabled on table '%.*ls'. 1719 16 FILESTREAM data cannot be placed on an empty filegroup. 1720 16 Cannot drop FILESTREAM filegroup or partition scheme since table '%.*ls' has FILESTREAM columns. 1721 16 Altering table '%.*ls' failed because the row size using vardeci mal storage format exceeds the maximum allowed table row size of %d bytes. 1722 16 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme is not spe cified for FILESTREAM data. 1723 16 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specif ied for FILESTREAM data but not for the table. 1724 16 Filegroup '%.*ls' is not a FILESTREAM filegroup or partition sch eme of FILESTREAM filegroups. 1725 16 Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEA D OF trigger exists on the %S_MSG. 1726 16 Cannot add FILESTREAM filegroup or partition scheme since table '%.*ls' has a FILESTREAM filegroup or partition scheme already. 1727 16 Cannot create non-clustered index '%.*ls' on table '%.*ls' with the FILESTREAM_ON clause. 1728 16 Cannot create index '%.*ls' on table '%.*ls' because the compute d column '%.*ls' uses a FILESTREAM column. 1729 16 Cannot create table '%.*ls' because the partitioning column '%.* ls' uses a FILESTREAM column. 1730 16 Creating or altering compressed table '%.*ls' failed because the uncompressed row size would be %d, including %d bytes of internal overhead. Thi s exceeds the maximum allowable table row size of %d bytes. 1731 16 Cannot create the sparse column '%.*ls' in the table '%.*ls' bec ause an option or data type specified is not valid. A sparse column must be null able and cannot have the ROWGUIDCOL, IDENTITY, or FILESTREAM properties. A spars e column cannot be of the following data types: text, ntext, image, geometry, ge ography, or user-defined type. 1732 16 Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a table cannot have more than one sparse column set. Modify the stateme nt so that only one column is specified as COLUMN_SET FOR ALL_SPARSE_COLUMNS. 1733 16 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 de finition to allow null values. 1734 16 Cannot create the sparse column set '%.*ls' in the table '%.*ls' because the table already contains one or more sparse columns. A sparse column set cannot be added to a table if the table contains a sparse column. 1736 16 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. 1738 10 Cannot create table '%.*ls' with only a column set column and wi thout any non-computed columns in the table. 1750 10 Could not create constraint. See previous errors. 1752 16 Column '%.*ls' in table '%.*ls' is invalid for creating a defaul t constraint. 1753 16 Column '%.*ls.%.*ls' is not the same length or scale as referenc ing column '%.*ls.%.*ls' in foreign key '%.*ls'. Columns participating in a fore ign key relationship must be defined with the same length and scale. 1754 16 Defaults cannot be created on columns with an IDENTITY attribute . Table '%.*ls', column '%.*ls'. 1755 16 Defaults cannot be created on columns of data type timestamp. Ta

ble '%.*ls', column '%.*ls'. 1756 10 Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary ta bles. 1757 16 Column '%.*ls.%.*ls' is not of same collation as referencing col umn '%.*ls.%.*ls' in foreign key '%.*ls'. 1758 16 Only a single constraint can be added or dropped online with no other operations in the same statement. 1759 16 Computed column '%.*ls' in table '%.*ls' is not allowed to be us ed in another computed-column definition. 1760 16 Constraints of type %ls cannot be created on columns of type %ls . 1761 16 Cannot create the foreign key "%.*ls" with the SET NULL referent ial action, because one or more referencing columns are not nullable. 1762 16 Cannot create the foreign key "%.*ls" with the SET DEFAULT refer ential action, because one or more referencing not-nullable columns lack a defau lt constraint. 1763 16 Cross-database foreign key references are not supported. Foreign key '%.*ls'. 1764 16 Computed Column '%.*ls' in table '%.*ls' is invalid for use in ' %ls' because it is not persisted. 1765 16 Foreign key '%.*ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.*ls'. 1766 16 Foreign key references to temporary tables are not supported. Fo reign key '%.*ls'. 1767 16 Foreign key '%.*ls' references invalid table '%.*ls'. 1768 16 Foreign key '%.*ls' references object '%.*ls' which is not a use r table. 1769 16 Foreign key '%.*ls' references invalid column '%.*ls' in referen cing table '%.*ls'. 1770 16 Foreign key '%.*ls' references invalid column '%.*ls' in referen ced table '%.*ls'. 1771 16 Cannot create foreign key '%.*ls' because it references object ' %.*ls' whose clustered index '%.*ls' is disabled. 1772 16 Foreign key '%.*ls' is not valid. A system table cannot be used in a foreign key definition. 1773 16 Foreign key '%.*ls' has implicit reference to object '%.*ls' whi ch does not have a primary key defined on it. 1774 16 The number of columns in the referencing column list for foreign key '%.*ls' does not match those of the primary key in the referenced table '%. *ls'. 1775 16 Cannot create foreign key '%.*ls' because it references object ' %.*ls' whose PRIMARY KEY index '%.*ls' is disabled. 1776 16 There are no primary or candidate keys in the referenced table ' %.*ls' that match the referencing column list in the foreign key '%.*ls'. 1778 16 Column '%.*ls.%.*ls' is not the same data type as referencing co lumn '%.*ls.%.*ls' in foreign key '%.*ls'. 1779 16 Table '%.*ls' already has a primary key defined on it. 1781 16 Column already has a DEFAULT bound to it. 1782 16 Cannot drop index '%.*ls' since a partition scheme is not specif ied for base data. 1784 16 Cannot create the foreign key '%.*ls' because the referenced col umn '%.*ls.%.*ls' is a non-persisted computed column. 1785 16 Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. 1786 16 Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with cascading referential integrity constraints. 1787 16 Cannot define foreign key constraint '%.*ls' with cascaded DELET

E or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDAT E TRIGGER defined on it. 1788 16 Cascading foreign key '%.*ls' cannot be created where the refere ncing column '%.*ls.%.*ls' is an identity column. 1789 16 Cannot use CHECKSUM(*) in a computed column, constraint, or defa ult definition. 1790 16 The name of a user-defined table type cannot start with a number (#) sign. 1791 16 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. Sp arse columns or sparse column sets cannot have a DEFAULT constraint. 1792 16 Alter table '%.*ls' failed because the added fixed column might cause existing data to go beyond the maximum allowable table row size of %d byte s. 1793 16 Cannot federate a temporary table. 1794 16 Column '%.*ls' is invalid for federating the table '%.*ls'. 1795 16 Nullable column '%.*ls' cannot be used to federate the table '%. *ls'. 1796 16 Computed column '%.*ls' cannot be used to federate the table '%. *ls'. 1797 16 Sparse column '%.*ls' cannot be used to federate the table '%.*l s'. 1798 16 Federated tables cannot be created in a non-federated database. 1799 16 Column '%.*ls' cannot be used to federate the table '%.*ls' beca use it does not match the federation key type. 1801 16 Database '%.*ls' already exists. Choose a different database nam e. 1802 16 CREATE DATABASE failed. Some file names listed could not be crea ted. Check related errors. 1803 17 The CREATE DATABASE statement failed. The primary file must be a t least %d MB to accommodate a copy of the model database. 1806 16 CREATE DATABASE failed. The default collation of database '%.*ls ' cannot be set to '%.*ls'. 1807 17 Could not obtain exclusive lock on database '%.*ls'. Retry the o peration later. 1810 16 The model database must be updatable before a new database can b e created. 1812 16 CREATE DATABASE failed. COLLATE clause cannot be used with the F OR ATTACH option. 1813 16 Could not open new database '%.*ls'. CREATE DATABASE is aborted. 1814 10 Could not create tempdb. You may not have enough disk space avai lable. Free additional disk space by deleting other files on the tempdb drive an d then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. 1815 16 The %ls property cannot be used with database snapshot files. 1816 16 Database snapshot on the system database %.*ls is not allowed. 1817 16 Only the owner of database "%.*s" or the system administrator ca n create a database snapshot on it. 1818 16 Primary log file '%ls' is missing and the database was not clean ly shut down so it cannot be rebuilt. 1819 10 Could not create default log file because the name was too long. 1821 16 Cannot create a database snapshot on another database snapshot. 1822 16 The database must be online to have a database snapshot. 1823 16 A database snapshot cannot be created because it failed to start . 1824 16 Cannot attach a database that was being restored. 1825 16 Filegroups and collations cannot be specified for database snaps hots. 1826 16 User-defined filegroups are not allowed on "%ls". 1827 16 CREATE DATABASE or ALTER DATABASE failed because the resulting c

umulative database size would exceed your licensed limit of %I64d MB per %S_MSG. 1828 16 The logical file name "%.*ls" is already in use. Choose a differ ent name. 1829 16 The FOR ATTACH option requires that at least the primary file be specified. 1830 16 The files '%.*ls' and '%.*ls' are both primary files. A database can only have one primary file. 1831 16 File ONLINE/OFFLINE syntax cannot be used with CREATE DATABASE. 1832 20 Cannot attach the file '%.*ls' as database '%.*ls'.%.*ls 1833 16 File '%ls' cannot be reused until after the next BACKUP LOG oper ation. If the database is participating in an availability group, a dropped file can be reused only after the truncation LSN of the primary availability replica has passed the drop LSN of the file and a subsequent BACKUP LOG operation has c ompleted. 1834 16 The file '%ls' cannot be overwritten. It is being used by datab ase '%.*ls'. 1835 16 Unable to create/attach any new database because the number of e xisting databases has reached the maximum number allowed: %d. 1836 10 Cannot create the default files because the name that was suppli ed is too long. 1837 16 The file name "%ls" is too long to create an alternate stream na me. 1838 10 Offline database file(s) have been overwritten while being rever ted to online state from a database snapshot. The reverted file might contain in valid pages. Please run database consistency checks to assess the data integrity . 1839 16 Could not create default data files because the name '%ls' is a reserved device name. 1840 16 Could not create snapshot database because it is not supported o n READONLY single-file user databases. 1841 16 CREATE DATABASE failed. CONTAINMENT clause cannot be used with t he FOR ATTACH option. 1842 16 The file size, max size cannot be greater than 2147483647 in uni ts of a page size. The file growth cannot be greater than 2147483647 in units of both page size and percentage. 1843 10 Reverting database '%ls' to the point in time of database snapsh ot '%ls' with split point LSN %.*ls (0x%ls). This is an informational message on ly. No user action is required. 1844 16 %ls is not supported on %ls. 1845 16 Cannot find SQL Volume Shadow Copy Service (VSS) Writer in write r metadata document provided by VSS while creating auto-recovered VSS snapshot f or online DBCC check. 1846 16 Cannot find SQL Volume Shadow Copy (VSS) Writer component for da tabase '%ls' while creating auto-recovered VSS snapshot for online DBCC check. 1847 16 The current version of the operating system doesn't support auto -recovered Volume Shadow Copy (VSS) snapshots. 1848 16 Volume Shadow Copy Service (VSS) failed to create an auto-recove red snapshot of database '%ls' for online DBCC check. 1851 16 File name '%.*ls' as relative path is too long after prefixed wi th default path '%ls'. 1852 21 Error occured when shrinking the physical file. Please check ERR ORLOG for more detail. 1853 16 The logical database file '%.*ls' cannot be found. Specify the f ull path for the file. 1854 16 The original file name '%.*ls' for logical database file '%.*ls' is too long to be combined with the full path to the new primary data file loca tion. 1855 16 System table sysfiles1 is corrupted. 1856 16 Cannot attach file '%.*ls' as database '%.*ls' because this data base name is already attached with file '%.*ls'

1857 16 Cannot attach file '%.*ls' as database '%.*ls' because this file is already in use for database '%.*ls' 1858 16 Could not create snapshot database because user database is stil l in recovery. 1901 16 Cannot create index or statistics '%.*ls' on view '%.*ls' becaus e 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 pr ecise. If column is computed in base table consider marking it PERSISTED there. 1902 16 Cannot create more than one clustered index on %S_MSG '%.*ls'. D rop the existing clustered index '%.*ls' before creating another. 1904 16 The %S_MSG '%.*ls' on table '%.*ls' has %d columns in the key li st. The maximum limit for %S_MSG key column list is %d. 1907 16 Cannot recreate index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index. 1908 16 Column '%.*ls' is partitioning column of the index '%.*ls'. Part ition columns for a unique index must be a subset of the index key. 1909 16 Cannot use duplicate column names in %S_MSG. Column name '%.*ls' listed more than once. 1910 16 Could not create %S_MSG '%.*ls' because it exceeds the maximum o f %d allowed per table or view. 1911 16 Column name '%.*ls' does not exist in the target table or view. 1912 16 Could not proceed with index DDL operation on %S_MSG '%.*ls' bec ause it conflicts with another concurrent operation that is already in progress on the object. The concurrent operation could be an online index operation on th e same object or another concurrent operation that moves index pages like DBCC S HRINKFILE. 1913 16 The operation failed because an index or statistics with name '% .*ls' already exists on %S_MSG '%.*ls'. 1914 16 Index cannot be created on object '%.*ls' because the object is not a user table or view. 1915 16 Cannot alter a non-unique index with ignore_dup_key index option . Index '%.*ls' is non-unique. 1916 16 CREATE INDEX options %ls and %ls are mutually exclusive. 1917 16 Cannot create, rebuild or drop an index on a local temporary tab le online. Perform the index operation offline. 1919 16 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index. 1921 16 Invalid %S_MSG '%.*ls' specified. 1922 16 Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. Use ALTER DATABASE to add one or more files to the filegroup. 1924 16 Filegroup '%.*ls' is read-only. 1925 16 Cannot convert a clustered index to a nonclustered index by usin g the DROP_EXISTING option. To change the index type from clustered to noncluste red, delete the clustered index, and then create a nonclustered index by using t wo separate statements. 1927 16 There are already statistics on table '%.*ls' named '%.*ls'. 1929 16 Statistics cannot be created on object '%.*ls' because the objec t is not a user table or view. 1930 16 Cannot convert a nonclustered index to a clustered index because a foreign key constraint references the index. Remove the foreign key constrain t and then retry the operation. 1931 16 The SQL statement cannot be executed because filegroup '%.*ls' i s offline. Use the sys.database_files or sys.master_files catalog view to determ ine the state of the files in this filegroup and then restore the offline file(s ) from backup. 1934 16 %ls failed because the following SET options have incorrect sett ings: '%.*ls'. Verify that SET options are correct for use with %S_MSG. 1935 16 Cannot create index. Object '%.*ls' was created with the followi ng SET options off: '%.*ls'.

1937 16 Cannot create %S_MSG on view '%.*ls' because it references anoth er view '%.*ls'. Consider expanding referenced view's definition by hand in inde xed view definition. 1938 16 Index cannot be created on view '%.*ls' because the underlying o bject '%.*ls' has a different owner. 1939 16 Cannot create %S_MSG on view '%.*ls' because the view is not sch ema bound. 1940 16 Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index. 1941 16 Cannot create nonunique clustered index on view '%.*ls' because only unique clustered indexes are allowed. Consider creating unique clustered in dex instead. 1942 16 Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, i mage, FILESTREAM or xml columns. 1943 16 The index "%.*ls" on table "%.*ls" cannot be reorganized because page level locking is disabled. 1944 16 Index '%.*ls' was not created because the index key size is at l east %d bytes. The index key size cannot exceed 900 bytes. If the index key incl udes implicit key columns, the index key size cannot exceed 1800 bytes. 1945 10 Warning! The maximum key length is %d bytes. The index '%.*ls' h as maximum length of %d bytes. For some combination of large values, the insert/ update operation will fail. 1946 16 Operation failed. The index entry of length %d bytes for the ind ex '%.*ls' exceeds the maximum length of %d bytes. 1947 16 Cannot create %S_MSG on view "%.*ls". The view contains a self j oin on "%.*ls". 1949 16 Cannot create %S_MSG on view '%.*ls'. The function '%s' yields n ondeterministic results. Use a deterministic system function, or modify the user -defined function to return deterministic results. 1956 16 Cannot create %S_MSG on the '%.*ls' view because it uses the non deterministic user-defined function '%.*ls'. Remove the reference to the functio n, or make it deterministic. 1957 16 Cannot create %S_MSG on view '%.*ls' because view uses imprecise user-defined function '%.*ls'. Consider removing reference to function or alter ing it to be precise. 1959 16 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 rais e the compatibility level of the database. 1961 16 Cannot create %S_MSG on view '%.*ls'. The collation cast express ion with collation name '%.*ls' is non-deterministic because it is dependent on the operating system. 1962 16 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. Conside r eliminating the column from the view, or altering the column to be precise. 1963 16 Cannot create %S_MSG on view "%.*ls". The view contains a conver t that is imprecise or non-deterministic. 1964 16 Cannot create %S_MSG on view "%.*ls". The view contains an impre cise constant. 1965 16 Cannot create %S_MSG on view "%.*ls". The view contains an impre cise arithmetic operator. 1966 16 Cannot create %S_MSG on view '%.*ls'. The view contains an impre cise aggregate operator. 1967 16 Cannot create a new clustered index on a view online. 1968 16 Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option. 1969 16 Default FILESTREAM filegroup is not available in database '%.*ls '. 1970 10 Warning: Online index operation on table '%.*ls' will proceed bu t concurrent access to the table may be limited due to residual lock on the tabl e from a previous operation in the same transaction.

1971 16 Cannot disable index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that uses this index. 1972 16 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permiss ion denied to alter the referencing view '%.*ls' while disabling its clustered i ndex. 1973 16 Cannot perform the specified operation on disabled index '%.*ls' on %S_MSG '%.*ls'. 1974 16 Cannot perform the specified operation on %S_MSG '%.*ls' because its clustered index '%.*ls' is disabled. 1975 16 Index '%.*ls' row length exceeds the maximum permissible length of '%d' bytes. 1976 16 Cannot create index or statistics '%.*ls' on view '%.*ls' becaus e cannot verify key column '%.*ls' is precise and deterministic. Consider removi ng column from index or statistics key, marking column persisted in base table i f it is computed, or using non-CLR-derived column in key. 1977 16 Could not create %S_MSG '%.*ls' on table '%.*ls'. Only XML Index can be created on XML column '%.*ls'. 1978 16 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index or statistics. 1979 16 Cannot use index option ignore_dup_key to alter index '%.*ls' as it enforces a primary or unique constraint. 1980 16 Index cannot be created on computed column '%.*ls' of table '%.* ls' because the underlying object '%.*ls' has a different owner. 1981 10 Warning: The maximum length of the row exceeds the permissible l imit of %d bytes. For some combination of large values, the insert/update operat ion will fail. 1982 16 Cannot create %S_MSG on view '%.*ls' because the view references non-deterministic or imprecise member function '%.*ls' on CLR type '%.*ls'. Con sider removing reference to the function or altering the function to behave in a deterministic way. Do not declare a CLR function that behaves non-deterministi cally to have IsDeterministic=true, because that can lead to index corruption. S ee Books Online for details. 1983 16 Cannot create %S_MSG on view '%.*ls'. The function '%s' yields i mprecise results. Use a precise system function, or modify the user-defined func tion to return precise results. 1984 16 Index '%.*ls' cannot be created or rebuilt. The specified row le ngth for this index using the vardecimal storage format exceeds the maximum allo wed length of '%d' bytes. 1985 16 Cannot create %S_MSG on view '%.*ls'. It contains one or more XM L data type methods. 1986 10 Cannot replace non-hypothetical index '%.*ls' with a hypothetica l index using the DROP_EXISTING option. 1987 16 Cannot %S_MSG %S_MSG '%.*ls' on %S_MSG '%.*ls' because its %S_MS G is disabled. 1988 16 Cannot rebuild clustered index '%.*ls' online because it is disa bled. 1989 16 Cannot enable foreign key constraint '%.*ls' as index '%.*ls' on referenced key is disabled. 1990 16 Cannot define an index on a view with ignore_dup_key index optio n. Remove ignore_dup_key option and verify that view definition does not allow d uplicates, or do not index view. 1991 16 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permiss ion denied to disable foreign key '%.*ls' on table '%.*ls' that references this table. 1992 10 Warning: Foreign key '%.*ls' on table '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'. 1993 16 Cannot partition an index on a table variable or return table de finition in table valued function. 1994 16 Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required.

1995 16 Cannot rebuild hypothetical index '%.*ls' online. 1996 16 Could not create index enforcing primary key constraint '%.*ls' using DROP_EXISTING option because table has an XML or spatial index. Drop the X ML or spatial index, create the primary key contstraint, and recreate the XML or spatial index. 1997 16 Could not convert the XML or spatial index '%.*ls' to a relati onal index by using the DROP_EXISTING option. Drop the XML or spatial index and create a relational index with the same name. 1998 10 Warning: Clustered index '%.*ls' on view '%.*ls' referencing tab le '%.*ls' was disabled as a result of disabling the index '%.*ls'. 1999 16 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as included column in an index. 2002 16 Cannot create a procedure for replication with group number grea ter than one. 2003 16 Procedures with a group number cannot have parameters of XML or CLR types. Parameter '%.*ls' of procedure '%.*ls' has type '%ls'. 2004 16 Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number. 2005 16 The table '%.*ls' is unavailable and needs to be rebuilt. Rebuil d the table offline. 2007 10 The module '%.*ls' depends on the missing object '%.*ls'. The mo dule will still be created; however, it cannot run successfully until the object exists. 2008 16 The object '%.*ls' is not a procedure so you cannot create anoth er procedure under that group name. 2010 16 Cannot perform alter on '%.*ls' because it is an incompatible ob ject type. 2011 16 Index hints cannot be specified within a schema-bound object. 2013 10 Warning: 'is_ms_shipped' property is turned off for %S_MSG '%.*l s' because you do not have permission to create or alter an object with this pro perty. 2014 16 Remote access is not allowed from within a schema-bound object. 2020 16 The dependencies reported for entity "%.*ls" might not include r eferences to all 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 ent ity. Before rerunning the query, ensure that there are no errors in the entity and that all objects referenced by the entity exist. 2021 16 The referenced entity '%.*ls' was modified during DDL execution. Please retry the operation. 2022 16 Parsing errors were encountered in the %S_MSG '%.*ls'. The depen dencies referenced from this object could not be determined. 2101 14 Cannot %S_MSG a server level %S_MSG for user '%.*ls' since there is no login corresponding to the user. 2102 16 Cannot %S_MSG %S_MSG '%.*ls' since there is no user for login '% .*ls' in database '%.*ls'. 2103 15 Cannot %S_MSG trigger '%.*s' because its schema is different fro m the schema of the target table or view. 2104 14 Cannot %S_MSG the %S_MSG '%.*ls', because you do not have permis sion. 2108 15 Cannot %S_MSG %S_MSG on '%.*ls' as the target is not in the curr ent database. 2110 15 Cannot alter trigger '%.*ls' on '%.*ls' because this trigger doe s not belong to this object. Specify the correct trigger name or the correct tar get object name. 2111 16 Cannot %S_MSG trigger '%.*ls' on %S_MSG '%.*ls' because an INSTE AD OF %s trigger already exists on this object. 2112 16 Cannot create trigger '%.*ls' on view '%.*ls' because the view i s defined with CHECK OPTION. 2113 16 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 cascadi

ng DELETE or UPDATE. 2114 16 Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column. 2115 16 Server level event notifications are disabled as the database ms db does not exist. 2116 16 Cannot CREATE EVENT NOTIFICATION to database '%.*ls' because it is not a valid broker database. 2117 16 Cannot %S_MSG INSTEAD OF trigger '%.*ls' on %S_MSG '%.*ls' becau se the %S_MSG has a FILESTREAM column. 2201 16 %sDerivation from "anySimpleType" by restriction is not permitte d, and derivation by restriction from a type derived from "anySimpleType" by ext ension is allowed only if no constraining facets are specified. 2202 16 %sAn error has occurred while compiling the query. To obtain mor e detailed information about the error, the query must be run by a user with EXE CUTE permissions on the xml schema collection used in the query. 2203 16 %sOnly 'http://www.w3.org/2001/XMLSchema#decimal?', 'http://www. w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed as predicates, found '%ls' 2204 16 %sOnly 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed in conditions and with logical operators, found '%ls' 2205 16 %s"%ls" was expected. 2206 16 %sNamespace prefix 'xml' can only be associated with the URI 'ht tp://www.w3.org/XML/1998/namespace' and this URI cannot be used with other prefi xes. 2207 16 %sOnly non-document nodes can be inserted. Found "%ls". 2208 16 %sThe URI that starts with '%ls' is too long. Maximum allowed le ngth is %d characters. 2209 16 %sSyntax error near '%ls' 2210 16 %sHeterogeneous sequences are not allowed: found '%ls' and '%ls' 2211 16 %sSingleton (or empty sequence) required, found operand of type '%ls' 2212 16 %sInvalid source character '%c' (0x%02x) found in an identifier near '%ls'. 2213 16 %sCannot atomize/apply data() on expression that contains type ' %ls' within inferred type '%ls' 2214 16 %sThe type '%ls' is not an atomic type 2215 16 %sThe value of attribute '%ls' exceeds 4000 characters, the maxi mum permitted in XML schema documents 2216 16 %sInvalid XPath value in "%ls". 2217 16 %s'%ls' or '%ls' expected 2218 16 %sThere is no attribute named '@%ls' 2219 16 %sThere is no attribute named '@%ls' in the type '%ls'. 2220 16 %sThere is no attribute named '@%ls:%ls' 2221 16 %sThere is no attribute named '@%ls:%ls' in the type '%ls'. 2222 16 %sInvalid source character 0x%02x found in an identifier near '% ls'. 2223 16 %sSyntax error near '%ls', expected an identifier. 2225 16 %sA string literal was expected 2226 16 %sThe target of 'insert' must be a single node, found '%ls' 2227 16 %sThe variable '%ls' was not found in the scope in which it was referenced. 2228 16 %sThe variable '%ls:%ls' was not found in the scope in which it was referenced. 2229 16 %sThe name "%ls" does not denote a namespace. 2230 16 %sThe name "%ls" has already been defined. 2231 16 %sThe name "%ls" does not denote a defined type. 2232 16 %sThe name "%ls:%ls" does not denote a defined type. 2233 16 %sThe operand of "%ls" has an invalid type. 2234 16 %sThe operator "%ls" cannot be applied to "%ls" and "%ls" operan ds.

2235 16 %sAn argument list was applied to a non-function term. 2236 16 %sThere are not enough actual arguments in the call to function "%ls". 2237 16 %sDerivation from anyType by extension is not supported in this release. 2238 16 %sToo many arguments in call to function '%ls' 2240 16 %sThe target of 'insert into' must be an element/document node, found '%ls' 2241 16 %sVariable expected: '$name' 2242 16 %sType specification expected. 2243 16 %sRelative path expression used without any context 2247 16 %sThe value is of type "%ls", which is not a subtype of the expe cted type "%ls". 2248 16 %sSyntax error near '%ls', expected 'as', 'into', 'before' or 'a fter'. 2249 16 %sThe target of 'insert before/after' must be an element/PI/comm ent/text node, found '%ls' 2256 16 %sSyntax error near '%ls', expected a "node test". 2258 16 %sThe position may not be specified when inserting an attribute node, found '%ls' 2260 16 %sThere is no element named '%ls' 2261 16 %sThere is no element named '%ls' in the type '%ls'. 2262 16 %sThere is no element named '%ls:%ls' 2263 16 %sThere is no element named "%ls:%ls" in the type "%ls". 2264 16 %sOnly non-document nodes may be deleted, found '%ls' 2266 16 %sExpected end tag '%ls:%ls' 2267 16 %sExpected end tag '%ls' 2268 16 %sEnd tag '/%ls:%ls' has no matching begin tag 2269 16 %sEnd tag '/%ls' has no matching begin tag 2270 16 %sDuplicate attribute '%ls:%ls' 2271 16 %sDuplicate attribute '%ls' 2272 16 %s'?>' expected 2273 16 %sUnterminated CDATA section 2274 16 %sUnterminated string constant (started on line %u) 2275 16 %sUnterminated XML declaration 2276 16 %sDerivation from 'QName' by restriction is not supported in thi s release 2277 16 %sA tag name may not contain the character '%c' 2278 16 %sA tag name may not start with the character '%c' 2279 16 %sA name/token may not start with the character '%c' 2280 16 %s<! was not followed by a valid construct 2281 16 %sCannot construct DTDs in XQuery 2282 16 %sInvalid entity reference 2283 16 %sThe character '%c' may not be part of an entity reference 2284 16 %sThe namespace prefix '%ls' has not been defined 2285 16 %sInvalid numeric entity reference 2291 16 %sNo root element was found. 2292 16 %sWhen a type with simple content restricts a type with mixed co ntent, it must have an embedded simple type definition. Location: '%ls'. 2293 16 %sChoice cannot be empty unless minOccurs is 0. Location: '%ls'. 2294 16 %s'xml' is not allowed as a processing instruction target. 2297 16 %sElement <%ls> is not valid at location '%ls'. 2298 16 %sAttribute '%ls' is not valid at location '%ls'. 2299 16 %sRequired attribute "%ls" of XSD element "%ls" is missing. 2300 16 %sRequired sub-element "%ls" of XSD element "%ls" is missing. 2301 16 %sThe element "%ls" has already been defined. 2302 16 %sThe name "%ls" has already been defined in this scope. 2305 16 %sElement or attribute type specified more than once. Location: '%ls'. 2306 16 %sThe qualified name "%ls" was found in a context where only NCN

ame is allowed. 2307 16 %sReference to an undefined name '%ls' 2308 16 %sReference to an undefined name '%ls' within namespace '%ls' 2309 16 %sThe value of "%ls" is not a valid number. 2310 16 %sThe attribute "%ls" is declared more than once. 2311 16 %sThe attribute "%ls" is declared more than once within "%ls". 2312 16 %sThe value of attribute '%ls' does not conform to the type defi nition 'http://www.w3.org/2001/XMLSchema#%ls': '%ls'. 2313 16 %sThe attribute "%ls" cannot have a value of "%ls". 2314 16 %sThe attribute "%ls" cannot have a negative value. 2315 16 %sThe attribute "%ls" should have a string value. 2316 16 %sThe required 'base' attribute is missing. Location: '%ls'. 2317 16 %sThe base type "%ls" defined on XSD element "%ls" is not a simp le type. 2319 16 %sThis type may not have a '%ls' facet. Location: '%ls'. 2320 16 %sDuplicate facet '%ls' found at location '%ls'. 2321 16 %sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'. 2322 16 %sThe element type is not a subclass of the substitution group's head 2323 16 %sThe end tag '%ls' doesn't match opening tag '%ls' from line %u 2324 16 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls' from lin e %u 2325 16 %sThe end tag '%ls' doesn't match opening tag '%ls:%ls' from lin e %u 2326 16 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls:%ls' from line %u 2327 16 %sThe content or definition of <%ls> is missing. 2328 16 %sSchema namespace '%ls' doesn't match <include> directive's '%l s' 2329 16 %sThe string "%ls" is not a valid time duration value. 2331 16 %sRedefinition has to have itself as base type. Location: '%ls'. 2332 16 %s'%ls' may not be used with an 'empty' operand 2333 16 %sInvalid source character 0x%02x 2334 16 %sInvalid source character '%c' (0x%02x) 2335 16 %sNewline in character/string constant 2336 16 %s'%c' is not a valid octal digit (numbers starting with '0' are implicitly octal) 2337 16 %sThe target of 'replace' must be at most one node, found '%ls' 2338 16 %sThe second 'replace' operand must contain only nodes, found '% ls' 2339 16 %sEither a memberType attribute or a simpleType child must be pr esent. Location: '%ls'. 2340 16 %sComment started on line %u has no end 2341 16 %sExpected hex character code following '\\x' 2342 16 %sInvalid numeric constant. 2343 16 %sUnterminated text section - missing ` 2348 16 %sA namespace URI should contain at least one non-whitespace cha racter. 2349 16 %sAttempt to redefine namespace prefix '%ls' 2350 16 %sInvalid XML element content 2351 16 %sExpected 'first' or 'last' 2353 16 %s'to' or 'insert' or 'delete' expected 2354 16 %sInvalid source character encoding 2355 16 %s'else' expected 2356 16 %sThe target of 'replace value of' must be a non-metadata attrib ute or an element with simple typed content, found '%ls' 2357 16 %sA document node may only be replaced with another document nod e, found '%ls' 2358 16 %sDerivation with both a 'base' attribute and an embedded type d

efinition is not supported in this release. Location: '%ls'. 2359 16 %sThe target of '%ls' may not be a constructed node 2360 16 %sCannot have both a 'name' and 'ref' attribute. Location: '%ls' . 2361 16 %sThe base type of an XSD extension or restriction type must be a simple type. 2362 16 %sXSD schema too complex 2363 16 %sXQuery too complex 2364 16 %sCannot implicitly convert from '%ls' to '%ls' 2365 16 %sCannot explicitly convert from '%ls' to '%ls' 2366 16 %s"%ls" has a circular definition. 2367 16 %sThe item type of an XSD list type must be a simple type. Locat ion: '%ls'. 2368 16 %sCannot have element content in a complex type with simple cont ent. Location: '%ls'. 2369 16 %sCannot have more than one group/sequence/choice/all within a r estriction or extension. Location: '%ls'. 2370 16 %sNo more tokens expected at the end of the XQuery expression. F ound '%ls'. 2371 16 %s'%ls' can only be used within a predicate or XPath selector 2372 16 %sMetadata attribute '@%ls:%ls' may not be used with '%ls' 2373 16 %s%ls is not supported with constructed XML 2374 16 %sA node or set of nodes is required for %ls 2375 16 %sAggregate function '%ls' expects a sequence argument 2376 16 %sOperand of a single numeric type expected 2377 16 %sResult of '%ls' expression is statically 'empty' 2378 16 %sExpected XML schema document 2379 16 %sThe name specified is not a valid XML name :'%ls' 2380 16 %sMixed content is not allowed at location '%ls'. 2382 16 %sInvalid combination of minOccurs and maxOccurs values, minOccu rs has to be less than or equal to maxOccurs. Location: '%ls'. 2383 16 %sInvalid value '%ls' for the %ls attribute. The value has to be between 0 and %ld. 2384 16 %sInvalid element occurrence, element '%ls' was found multiple t imes in the context of element '%ls' 2385 16 Invalid target namespace specified 2386 16 %sThe value of '%ls' facet is outside of the allowed range 2387 16 %sCannot have both 'type' and 'ref' attributes. Location: '%ls'. 2388 16 %sInvalid element occurrence, element '%ls' has to appear first in the context of '%ls' 2389 16 %s'%ls' requires a singleton (or empty sequence), found operand of type '%ls' 2390 16 %sTop-level %s nodes are not supported 2391 16 %sRedefining XSD schemas is not supported 2392 16 %s'%ls::' is not a valid axis 2393 16 %sEither an itemType attribute or a simpleType child must be pre sent. Location: '%ls'. 2394 16 %sThere is no function '%ls()' 2395 16 %sThere is no function '%ls:%ls()' 2396 16 %sAttribute may not appear outside of an element 2397 16 %sIdentifiers may not contain more than %u characters 2398 16 %sDuplicate id value found: '%ls' 2399 16 %sAn attribute cannot have a value of type '%ls', a simple type was expected 2431 10 Error [%d, %d, %d] occurred while attempting to deallocate workf ile extent with extent ID [%d:%d]. 2501 16 Cannot find a table or object with the name "%.*ls". Check the s ystem catalog. 2502 16 Memory object list dump failed due to temporary inconsistency in the memory object structure. Please try again.

2503 10 Successfully deleted the physical file '%ls'. 2504 16 Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls. 2505 16 The device '%.*ls' does not exist. Use sys.backup_devices to sho w available devices. 2506 16 Could not find a table or object name '%.*ls' in database '%.*ls '. 2507 16 The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS. 2508 16 The %.*ls count for object "%.*ls", index ID %d, partition ID %I 64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE. 2509 16 DBCC CHECKCONSTRAINTS failed due to an internal query error. Ple ase run DBCC CHECKDATABASE to ensure your data consistency. 2510 16 DBCC %ls error: %ls. 2511 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d . 2512 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S _PGID slot %d. 2514 16 A DBCC PAGE error has occurred: %ls. 2515 16 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 m odified in the differential backup bitmap. 2516 16 Repair has invalidated the differential bitmap for database %.*l s. The differential backup chain is broken. You must perform a full database bac kup before you can perform a differential backup. 2517 16 Bulk-logging has been turned on for database %.*ls. To ensure th at all data has been secured, run backup log operations again. 2518 10 Object ID %ld (object "%.*ls"): Computed columns and CLR types c annot be checked for this object because the common language runtime (CLR) is di sabled. 2519 10 Computed columns and CLR types cannot be checked for object ID % ld (object "%.*ls") because the internal expression evaluator could not be initi alized. 2520 16 Could not find database '%.*ls'. The database either does not ex ist, or was dropped before a statement tried to use it. Verify if the database e xists by querying the sys.databases catalog view. 2521 16 Could not find database ID %d. The database ID either does not e xist, or the database was dropped before a statement tried to use it. Verify if the database ID exists by querying the sys.databases catalog view. 2522 16 Unable to process index %.*ls of table %.*ls because filegroup % .*ls is invalid. 2523 16 Filegroup %.*ls is invalid. 2524 16 Cannot process object ID %ld (object "%.*ls") because it is a Se rvice Broker queue. Try the operation again with the object ID of the correspond ing internal table for the queue, found in sys.internal_tables. 2525 16 Database file %.*ls is offline. 2526 16 Incorrect DBCC statement. Check the documentation for the correc t DBCC syntax and options. 2527 16 Unable to process index %.*ls of table %.*ls because filegroup % .*ls is offline. 2528 10 DBCC execution completed. If DBCC printed error messages, contac t your system administrator. 2529 16 Filegroup %.*ls is offline. 2530 16 The index "%.*ls" on table "%.*ls" is disabled. 2531 16 Table error: object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID. 2532 16 One or more WITH options specified are not valid for this comman

d. 2533 16 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 ma y be invalid or may have an incorrect alloc unit ID in its header. 2534 16 Table error: page %S_PGID, whose header indicates that it is all ocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (ty pe %.*ls), is allocated by another object. 2536 10 DBCC results for '%.*ls'. 2537 16 Table error: object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%.*ls) fai led. The values are %I64d and %I64d. 2538 10 File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d. 2539 10 The total number of extents = %I64d, used pages = %I64d, and res erved pages = %I64d in this database. 2540 10 The system cannot self repair this error. 2541 10 DBCC UPDATEUSAGE: Usage counts updated for table '%.*ls' (index '%.*ls', partition %ld): 2542 10 DATA pages %.*ls: changed from (%I64d) to (%I64d) pages. 2543 10 USED pages %.*ls: changed from (%I64d) to (%I64d) pages. 2544 10 RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages. 2545 10 ROWS count: changed from (%I64d) to (%I64d) rows. 2546 10 Index '%.*ls' on table '%.*ls' is marked as disabled. Rebuild th e index to bring it online. 2547 16 Unable to process object ID %ld (object "%.*ls") because it is a synonym. If the object referenced by the synonym is a table or view, retry the operation using the base object that the synonym references. 2548 10 DBCC: Compaction phase of index '%.*ls' is %d%% complete. 2549 10 DBCC: Defrag phase of index '%.*ls' is %d%% complete. 2550 16 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reo rganized because it is being reorganized by another process. 2551 16 The indexes on table "%.*ls" cannot be reorganized because there is already an online index build or rebuild in progress on the table. 2552 16 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reo rganized because page level locking is disabled. 2553 10 Table '%.*ls' will not be available during reorganizing index ' %.*ls'. This is because the index reorganization operation performs inside a us er transaction and the entire table is exclusively locked. 2554 16 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reo rganized because the filegroup is read-only. 2555 16 Cannot move all contents of file "%.*ls" to other places to comp lete the emptyfile operation. 2556 16 There is insufficient space in the filegroup to complete the emp tyfile operation. 2557 14 User '%.*ls' does not have permission to run DBCC %ls for object '%.*ls'. 2558 16 %I64d incorrect counts were detected in database '%.*ls'. 2559 16 The '%ls' and '%ls' options are not allowed on the same statemen t. 2560 16 Parameter %d is incorrect for this DBCC statement. 2561 16 Parameter %d is incorrect for this statement. 2562 16 Checking FILESTREAM filegroup "%.*ls" (ID %d) is not supported i n DBCC CHECKFILEGROUP. Specify a filegroup containing user objects with FILESTR EAM data instead. 2563 16 DBCC SHRINKFILE for FILESTREAM containers requires EMPTYFILE opt ion and does not allow any other options. 2566 14 DBCC DBREINDEX cannot be used on system tables. 2567 14 DBCC INDEXDEFRAG cannot be used on system table indexes 2568 16 Page %S_PGID is out of range for this database or is in a log fi le.

2570 16 Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type "%.*ls"). Column "%.*ls" value is out of range for data type "%.*ls". Update column to a legal value. 2571 14 User '%.*ls' does not have permission to run DBCC %.*ls. 2572 16 DBCC cannot free DLL '%.*ls'. The DLL is in use. 2573 16 Could not find table or object ID %.*ls. Check system catalog. 2574 16 Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree. 2575 16 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 %I6 4d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan. 2576 16 The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan. 2577 16 Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d. 2579 16 Table error: Extent %S_PGID in object ID %d, index ID %d, partit ion ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this datab ase. 2580 16 Table '%.*ls' is either a system or temporary table. DBCC CLEANT ABLE cannot be applied to a system or temporary table. 2581 10 DBCC cannot free the DLL "%.*ls". The DLL is not loaded. 2583 16 An incorrect number of parameters was given to the DBCC statemen t. 2585 16 Cannot find partition number %ld for table "%.*ls". 2586 16 Cannot find partition number %ld for index "%.*ls", table "%.*ls ". 2587 16 The invalid partition number %ld was specified. 2588 16 Cannot find partition number %ld for index ID %d, object ID %d. 2589 16 Repair could not fix all errors on the first attempt. 2590 10 User "%.*ls" is modifying bytes %d to %d of page %S_PGID in data base "%.*ls". 2591 16 Cannot find a row in the system catalog with the index ID %d for table "%.*ls". 2592 10 Repair: The %ls index successfully rebuilt for the object "%.*ls " in database "%.*ls". 2593 10 There are %I64d rows in %I64d pages for object "%.*ls". 2594 10 Cannot process rowset ID %I64d of object "%.*ls" (ID %d), index "%.*ls" (ID %d), because it resides on filegroup "%.*ls" (ID %d), which was not checked. 2596 16 The repair statement was not processed. The database cannot be i n read-only mode. 2597 10 Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup. 2598 16 Check cannot proceed on any objects belonging to database "%.*ls " because it is currently in recovery. 2599 16 Cannot switch to in row text in table "%.*ls". 2601 14 Cannot insert duplicate key row in object '%.*ls' with unique in dex '%.*ls'. The duplicate key value is %ls. 2627 14 Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'. The duplicate key value is %ls. 2700 16 There are too many statements in the batch; the maximum number i s %d 2701 10 Database name '%.*ls' ignored, referencing object in tempdb. 2702 16 Database '%.*ls' does not exist. 2703 16 Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once.

2704 16 Invalid partition scheme '%.*ls' specified. 2705 16 Column names in each table must be unique. Column name '%.*ls' i n table '%.*ls' is specified more than once. 2706 11 Table '%.*ls' does not exist. 2707 16 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or s tatistics or as a partition key because it depends on a non-schemabound object. 2709 16 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or s tatistics or as a partition key because it does user or system data access. 2710 16 You are not the owner specified for the object '%.*ls' in this s tatement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT). 2711 16 The definition of object "%.*ls" in the resource database contai ns the non-ASCII character "%.*ls". 2712 16 Database '%.*ls' can not be configured as a distribution databas e because it has change tracking enabled. 2714 16 There is already an object named '%.*ls' in the database. 2715 16 Column, parameter, or variable #%d: Cannot find data type %.*ls. 2716 16 Column, parameter, or variable #%d: Cannot specify a column widt h on data type %.*ls. 2717 15 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum al lowed (%d). 2719 16 Upgrade of database "%.*ls" failed because it contains a user na med "sys" which is a reserved user or schema name in this version of SQL Server. 2720 16 Cannot schema bind %S_MSG '%.*ls' because it references system o bject '%.*ls'. 2722 16 Xml data type methods are not allowed in expressions in this con text. 2724 10 Parameter or variable '%.*ls' has an invalid data type. 2725 16 An online operation cannot be performed for %S_MSG '%.*ls' becau se the index contains column '%.*ls' of data type text, ntext, image or FILESTRE AM. For a non-clustered index, the column could be an include column of the inde x. For a clustered index, the column could be any column of the table. If DROP_E XISTING is used, the column could be part of a new or old index. The operation m ust be performed offline. 2726 16 Partition function '%.*ls' uses %d columns which does not match with the number of partition columns used to partition the table or index. 2727 11 Cannot find index '%.*ls'. 2728 16 Cannot partition on more than %d columns. 2729 16 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or s tatistics or as a partition key because it is non-deterministic. 2730 11 Cannot create procedure '%.*ls' with a group number of %d becaus e a procedure with the same name and a group number of 1 does not currently exis t in the database. Must execute CREATE PROCEDURE '%.*ls';1 first. 2731 16 Column '%.*ls' has invalid width: %d. 2732 16 Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000. 2733 16 The %ls data type is invalid for return values. 2735 16 Cannot create primary xml or spatial index '%.*ls' on '%.*ls' be cause PRIMARY KEY constraint contains column(s) of type timestamp. 2738 16 A table can only have one timestamp column. Because table '%.*ls ' already has one, the column '%.*ls' cannot be added. 2739 16 The text, ntext, and image data types are invalid for local vari ables. 2740 16 SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server. 2741 16 SET DATEFORMAT date order '%.*ls' is invalid. 2742 16 SET DATEFIRST %d is out of range. 2743 16 %ls option requires %S_MSG parameter. 2744 16 Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed. 2745 10 Process ID %d has raised user error %d, severity %d. SQL Server

is terminating this process. 2747 16 Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters. 2748 16 Cannot specify %ls data type (parameter %d) as a substitution pa rameter. 2749 16 Identity column '%.*ls' must be of data type int, bigint, smalli nt, tinyint, or decimal or numeric with a scale of 0, and constrained to be nonn ullable. 2750 16 Column or parameter #%d: Specified column precision %d is greate r than the maximum precision of %d. 2751 16 Column or parameter #%d: Specified column scale %d is greater th an the specified precision of %d. 2752 16 Identity column '%.*ls' contains invalid SEED. 2753 16 Identity column '%.*ls' contains invalid INCREMENT. 2754 16 Error severity levels greater than %d can only be specified by m embers of the sysadmin role, using the WITH LOG option. 2755 16 SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d ... %d] of type integer}. 2756 16 Invalid value %d for state. Valid range is from %d to %d. 2759 16 CREATE SCHEMA failed due to previous errors. 2760 16 The specified schema name "%.*ls" either does not exist or you d o not have permission to use it. 2761 16 The ROWGUIDCOL property can only be specified on the uniqueident ifier data type. 2762 16 sp_setapprole was not invoked correctly. Refer to the documentat ion for more information. 2766 16 The definition for user-defined data type '%.*ls' has changed. 2767 15 Could not locate statistics '%.*ls' in the system catalogs. 2770 16 The SELECT INTO statement cannot have same source and destinatio n tables. 2772 16 Cannot access temporary tables from within a function. 2773 16 The collation ID is corrupted because the sort order ID %d is no t valid. 2774 16 Collation ID %d is invalid. 2775 16 The code page %d is not supported by the server. 2778 16 Only System Administrator can specify %s option for %s command. 2779 16 The %S_MSG '%.*ls' is an auto-drop system object. It cannot be u sed in queries or DDL. 2780 16 View '%.*ls' is not schemabound. 2782 16 Cannot create table "%.*ls": A table must have a clustered prima ry key in order to have XML data type columns. 2785 16 User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this context. 2786 16 The data type of substitution parameter %d does not match the ex pected type of the format specification. 2787 16 Invalid format specification: '%.*ls'. 2788 16 Synonyms are invalid in a schemabound object or a constraint exp ression. 2789 16 Must specify a two-part name for %S_MSG '%.*ls' in a schemabound object or a constraint expression. 2790 16 Cannot use a column of type TEXT, NTEXT, or IMAGE in a constrain t expression. 2791 16 Could not resolve expression for Schema-bound object or constrai nt. 2792 16 Cannot specify a sql CLR type in a Schema-bound object or a cons traint expression. 2793 16 Specified owner name '%.*ls' either does not exist or you do not have permission to act on its behalf. 2794 16 Message text expects more than the maximum number of arguments ( %d).

2795 16 Could not %S_MSG %S_MSG because the new %S_MSG '%.*ls' does not match the FILESTREAM %S_MSG '%.*ls' of the table. 2796 16 Cannot specify database name with $partition in a Schema-bound o bject, computed column or constraint expression. 2797 16 The default schema does not exist. 2798 16 Cannot create index or statistics '%.*ls' on table '%.*ls' becau se SQL Server cannot verify that key column '%.*ls' is precise and deterministic . Consider removing column from index or statistics key, marking computed column persisted, or using non-CLR-derived column in key. 2799 16 Cannot create index or statistics '%.*ls' on table '%.*ls' becau se the computed column '%.*ls' is imprecise and not persisted. Consider removing column from index or statistics key or marking computed column persisted. 2801 16 The definition of object '%.*ls' has changed since it was compil ed. 2802 10 SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBC C FREESYSTEMCACHE' operations. 2803 10 SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to some database maintenance or reconfigure operations. 2809 16 The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MS G object. 2812 16 Could not find stored procedure '%.*ls'. 2813 16 "%.*ls" is not supported on this edition of SQL Server. 2814 10 A possible infinite recompile was detected for SQLHANDLE %hs, Pl anHandle %hs, starting offset %d, ending offset %d. The last recompile reason w as %d. 3002 16 Cannot BACKUP or RESTORE a database snapshot. 3003 10 This BACKUP WITH DIFFERENTIAL will be based on more than one fil e backup. All those file backups must be restored before attempting to restore t his differential backup. 3004 16 The primary filegroup cannot be backed up as a file backup becau se the database is using the SIMPLE recovery model. Consider taking a partial ba ckup by specifying READ_WRITE_FILEGROUPS. 3005 10 The differential partial backup is including a read-only filegro up, '%ls'. This filegroup was read-write when the base partial backup was create d, but was later changed to read-only access. We recommend that you create a sep arate file backup of the '%ls' filegroup now, and then create a new partial back up to provide a new base for later differential partial backups. 3006 16 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 bac kups. 3007 16 The backup of the file or filegroup "%ls" is not permitted becau se it is not online. Container state: "%ls" (%d). Restore status: %d. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection t o include only online data. 3008 16 The specified device type is not supported for backup mirroring. 3009 16 Could not insert a backup or restore history/detail record in th e msdb database. This may indicate a problem with the msdb database. The backup/ restore operation was still successful. 3010 16 Invalid backup mirror specification. All mirrors must have the s ame number of members. 3011 16 All backup devices must be of the same general class (for exampl e, DISK and TAPE). 3012 17 VDI ran out of buffer when SQL Server attempted to send differen tial information to SQL Writer. 3013 16 %hs is terminating abnormally. 3014 10 %hs successfully processed %I64d pages in %d.%03d seconds (%d.%0 3d MB/sec).

3015 10 %hs is not yet implemented. 3016 16 Backup of file '%ls' is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taki ng the backup, or restrict the backup to exclude this file. 3017 16 The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Correct the problem, or reissue the command without RESTART . 3018 10 The restart-checkpoint file '%ls' was not found. The RESTORE com mand will continue from the beginning as if RESTART had not been specified. 3019 16 The restart-checkpoint file '%ls' is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The res tart command must use the same syntax as the interrupted command, with the addit ion of the RESTART clause. Alternatively, reissue the current statement without the RESTART clause. 3021 16 Cannot perform a backup or restore operation within a transactio n. 3022 10 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 Book s Online for more information on managing read-only data for the simple recovery model. In particular, consider how partial backups are used. 3023 16 Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the stat ement after the current backup or file manipulation operation is completed. 3024 16 You can only perform a full backup of the master database. Use B ACKUP DATABASE to back up the entire master database. 3025 16 Missing database name. Reissue the statement specifying a valid database name. 3027 16 The filegroup "%.*ls" is not part of database "%.*ls". 3028 10 The restart-checkpoint file '%ls' was corrupted and is being ign ored. The RESTORE command will continue from the beginning as if RESTART had not been specified. 3031 16 Option '%ls' conflicts with option(s) '%ls'. Remove the conflict ing option and reissue the statement. 3032 16 One or more of the options (%ls) are not supported for this stat ement. Review the documentation for supported options. 3033 16 BACKUP DATABASE cannot be used on a database opened in emergency mode. 3034 16 No files were selected to be processed. You may have selected on e or more filegroups that have no members. 3035 16 Cannot perform a differential backup for database "%ls", because a current database backup does not exist. Perform a full database backup by rei ssuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. 3036 16 The database "%ls" is in warm-standby state (set by executing RE STORE WITH STANDBY) and cannot be backed up until the entire restore sequence is completed. 3038 16 The file name "%ls" is invalid as a backup device name. Reissue the BACKUP statement with a valid file name. 3039 16 Cannot perform a differential backup for file '%ls' because a cu rrent file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFF ERENTIAL option. 3040 10 An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected. 3041 16 BACKUP failed to complete the command %.*ls. Check the backup ap plication log for detailed messages. 3042 10 BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information abou t the errors that were encountered. 3043 16 BACKUP '%ls' detected an error on page (%d:%d) in file '%ls'. 3044 16 Invalid zero-length device name. Reissue the BACKUP statement wi

th a valid device name. 3045 16 BACKUP or RESTORE requires the NTFS file system for FILESTREAM a nd full-text support. The path "%.*ls" is not usable. 3046 16 Inconsistent metadata has been encountered. The only possible ba ckup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TR UNCATE option. 3047 16 The BackupDirectory registry key is not configured correctly. Th is 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 checkpoin t files for RESTORE. 3049 16 BACKUP detected corruption in the database log. Check the errorl og for more information. 3050 16 SQL Server could not send the differential information for datab ase file '%ls' of database '%ls\\%ls' to the backup application because the diff erential information is too large to fit in memory, and an attempt to use a temp orary file has failed. 3051 16 BACKUP LOG was unable to maintain mirroring consistency for data base '%ls'. Database mirroring has been suspended. 3052 16 BACKUP LOG was unable to log updates for for database '%ls'. Sub sequent log backups will be required to advance the backup point from %S_LSN to %S_LSN after log space is made available for logging them. 3054 16 Differential file backups can include only read-only data for da tabases using the simple recovery model. Consider taking a partial backup by spe cifying READ_WRITE_FILEGROUPS. 3055 16 Backup destination "%.*ls" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement wi th a valid backup destination. 3056 16 The backup operation has detected an unexpected file in a FILEST REAM container. The backup operation will continue and include file '%ls'. 3057 16 Invalid device name. The length of the device name provided exce eds supported limit (maximum length is:%d). Reissue the BACKUP statement with a valid device name. 3058 10 File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls. 3059 16 This BACKUP or RESTORE command is not supported on a database mi rror or secondary replica. 3060 10 The restart-checkpoint file '%ls' was corrupted. The restored da tabase can not be recovered. Restart the RESTORE sequence. 3061 16 The restart-checkpoint file '%ls' could not be opened. Operatin g system error '%ls'. Make the file available and retry the operation or, resta rt the RESTORE sequence. 3062 16 Cannot backup from a HADRON secondary because it is not in Synch ronizing or Synchronized state. 3098 16 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 me dia set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten. 3101 16 Exclusive access could not be obtained because the database is i n use. 3102 16 %ls cannot process database '%ls' because it is in use by this s ession. It is recommended that the master database be used when performing this operation. 3103 16 A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTO RE statement and provide a backup set which includes a full copy of at least the primary data file. The WITH PARTIAL clause of the RESTORE statement may not be used for any other purpose. 3104 16 RESTORE cannot operate on database '%ls' because it is configure d for database mirroring or has joined an availability group. If you intend to r

estore the database, use ALTER DATABASE to remove mirroring or to remove the dat abase from its availability group. 3105 16 RESTORE cannot restore any more pages into file '%ls' because th e maximum number of pages (%d) are already being restored. Either complete the r estore sequence for the existing pages, or use RESTORE FILE to restore all pages in the file. 3106 16 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 a nd then reissue the RESTORE command. 3107 16 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 t he use of the file in the backup set, take the database offline and then reissue the RESTORE command. 3108 16 To restore the master database, the server must be running in si ngle-user mode. For information on starting in single-user mode, see "How to: St art an Instance of SQL Server (sqlservr.exe)" in Books Online. 3109 16 Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT a re not supported. 3110 14 User does not have permission to RESTORE database '%.*ls'. 3111 16 Page %S_PGID is a control page which cannot be restored in isola tion. To repair this page, the entire file must be restored. 3112 16 Cannot restore any database other than master when the server is in single user mode. 3113 16 Invalid data was detected. 3115 16 The database is using the simple recovery model. It is not possi ble to restore a subset of the read-write data. 3116 16 The supplied backup is not on the same recovery path as the data base, and is ineligible for use for an online file restore. 3117 16 The log or differential backup cannot be restored because no fil es are ready to rollforward. 3118 16 The database "%ls" does not exist. RESTORE can only create a dat abase when restoring either a full backup or a file backup of the primary file. 3119 16 Problems were identified while planning for the RESTORE statemen t. Previous messages provide details. 3120 16 This backup set will not be restored because all data has alread y been restored to a point beyond the time covered by this backup set. 3121 16 The file "%ls" is on a recovery path that is inconsistent with a pplication of this backup set. RESTORE cannot continue. 3122 16 File initialization failed. RESTORE cannot continue. 3123 16 Invalid database name '%.*ls' specified for backup or restore op eration. 3125 16 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 m ore data is required before recovery is possible. Either restore a full file bac kup taken since the data was marked read-only, or restore the most recent base b ackup for the target data followed by a differential file backup. 3127 16 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 f ile is marked for read-write access. Therefore, only read-only files can be reco vered by piecemeal restore. 3128 16 File '%ls' has an unsupported page size (%d). 3129 16 The contents of the file "%ls" are not consistent with a transit ion into the restore sequence. A restore from a backup set may be required. 3130 10 The filegroup "%ls" is selected. At the time of backup it was kn own by the name "%ls"'. RESTORE will continue operating upon the renamed filegro up. 3131 10 The file "%ls" is selected. At the time of backup it was known b y the name "%ls". RESTORE will continue operating upon the renamed file.

3132 16 The media set has %d media families but only %d are provided. Al l members must be provided. 3133 16 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 devic e specifications and loaded media are correct. 3134 10 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 conf licting recovery path. The restore was allowed because the file was read-only an d was consistent with the current status of the database. Any future differentia l backup of this file will require a new differential base. 3135 16 The backup set in file '%ls' was created by %hs and cannot be us ed for this restore operation. 3136 16 This differential backup cannot be restored because the database has not been restored to the correct earlier state. 3137 16 Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or th ere are missing files. 3138 16 The database cannot be reverted because FILESTREAM BLOBs are pre sent. 3139 16 Restore to snapshot is not allowed with the master database. 3140 16 Could not adjust the space allocation for file '%ls'. 3141 16 The database to be restored was named '%ls'. Reissue the stateme nt using the WITH REPLACE option to overwrite the '%ls' database. 3142 16 File "%ls" cannot be restored over the existing "%ls". Reissue t he RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location. 3143 16 The data set on device '%ls' is not a SQL Server backup set. 3144 16 File '%.*ls' was not backed up in file %d on device '%ls'. The f ile cannot be restored from this backup set. 3145 16 The STOPAT option is not supported for databases that use the SI MPLE recovery model. 3147 16 Backup and restore operations are not allowed on database tempdb . 3148 16 This RESTORE statement is invalid in the current context. The 'R ecover Data Only' option is only defined for secondary filegroups when the datab ase is in an online state. When the database is in an offline state filegroups c annot be specified. 3149 16 The file or filegroup "%ls" is not in a valid state for the "Rec over Data Only" option to be used. Only secondary files in the OFFLINE or RECOVE RY_PENDING state can be processed. 3150 10 The master database has been successfully restored. Shutting dow n SQL Server. 3151 21 Failed to restore master database. Shutting down SQL Server. Che ck the error logs, and rebuild the master database. For more information about h ow to rebuild the master database, see SQL Server Books Online. 3153 16 The database is already fully recovered. 3154 16 The backup set holds a backup of a database other than the exist ing '%ls' database. 3155 16 The RESTORE operation cannot proceed because one or more files h ave been added or dropped from the database since the backup set was created. 3156 16 File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identif y a valid location for the file. 3159 16 The tail of the log for the database "%ls" has not been backed u p. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do n ot want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE state ment to just overwrite the contents of the log. 3161 16 The primary file is unavailable. It must be restored or otherwis e made available. 3163 16 The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.

3165 16 Database '%ls' was restored, however an error was encountered wh ile replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online. 3166 16 RESTORE DATABASE could not drop database '%ls'. Drop the databas e and then reissue the RESTORE DATABASE statement. 3167 16 RESTORE could not start database '%ls'. 3168 16 The backup of the system database on the device %ls cannot be re stored because it was created by a different version of the server (%ls) than th is server (%ls). 3169 16 The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. 3170 16 The STANDBY filename is invalid. 3171 16 File %ls is defunct and cannot be restored into the online datab ase. 3172 16 Filegroup %ls is defunct and cannot be restored into the online database. 3173 16 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 t arget point in time. The tail of the log for the database "%ls" has not been bac ked up. Use BACKUP LOG WITH NORECOVERY to back up the log, or use the WITH REPLA CE clause in your RESTORE statement to overwrite the tail of the log. 3174 16 The file '%ls' cannot be moved by this RESTORE operation. 3175 10 RESTORE FILEGROUP="%ls" was specified, but not all of its files are present in the backup set. File "%ls" is missing. RESTORE will continue, but if you want all files to be restored, you must restore other backup sets. 3176 16 File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files. 3178 16 File %ls is not in the correct state to have this differential b ackup applied to it. 3179 16 The system database cannot be moved by RESTORE. 3180 16 This backup cannot be restored using WITH STANDBY because a data base upgrade is needed. Reissue the RESTORE without WITH STANDBY. 3181 10 Attempting to restore this backup may encounter storage space pr oblems. Subsequent messages will provide details. 3182 16 The backup set cannot be restored because the database was damag ed when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ER ROR. 3183 16 RESTORE detected an error on page (%d:%d) in database "%ls" as r ead from the backup set. 3184 10 RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible. 3185 16 RESTORE cannot apply this backup set because the database is sus pect. Restore a backup set that repairs the damage. 3186 16 The backup set has been damaged. RESTORE will not attempt to app ly this backup set. 3187 16 RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information. 3188 10 The backup set was written with damaged data by a BACKUP WITH CO NTINUE_AFTER_ERROR. 3189 16 Damage to the backup set was detected. 3190 16 Filegroup '%ls' cannot be restored because it does not exist in the backup set. 3191 16 Restore cannot continue because file '%ls' cannot be written. En sure that all files in the database are writable. 3192 10 Restore was successful but deferred transactions remain. These t ransactions cannot be resolved because there are data that is unavailable. Eithe r use RESTORE to make that data available or drop the filegroups if you never ne ed this data again. Dropping the filegroup results in a defunct filegroup.

3194 16 Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored. 3195 16 Page %S_PGID cannot be restored from this backup set. RESTORE PA GE can only be used from full backup sets or from the first log or differential backup taken since the file was added to the database. 3196 16 RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file. 3197 10 I/O is frozen on database %ls. No user action is required. Howev er, if I/O is not resumed promptly, you could cancel the backup. 3198 10 I/O was resumed on database %ls. No user action is required. 3199 16 RESTORE requires MAXTRANSFERSIZE=%u but %u was specified. 3201 16 Cannot open backup device '%ls'. Operating system error %ls. 3202 16 Write on "%ls" failed: %ls 3203 16 Read on "%ls" failed: %ls 3204 16 The backup or restore was aborted. 3205 16 Too many backup devices specified for backup or restore; only %d are allowed. 3206 16 Backup device '%.*ls' does not exist. To view existing backup de vices, use the sys.backup_devices catalog view. To create a new backup device us e either sp_addumpdevice or SQL Server Management Studio. 3207 16 Backup or restore requires at least one backup device. Rerun you r statement specifying a backup device. 3208 16 Unexpected end of file while reading beginning of backup set. Co nfirm that the media contains a valid SQL Server backup set, and see the console error log for more details. 3209 16 Operation is not supported on user instances. 3210 16 The mirror member in drive "%ls" is inconsistent with the mirror member in drive "%ls". 3211 10 %d percent processed. 3212 16 The mirror device "%ls" and the mirror device "%ls" have differe nt device specifications. 3213 16 Unable to unload one or more tapes. See the error log for detail s. 3214 16 Too many backup mirrors are specified. Only %d are allowed. 3215 16 Use WITH FORMAT to create a new mirrored backup set. 3216 16 RESTORE REWINDONLY is only applicable to tape devices. 3217 16 Invalid value specified for %ls parameter. 3218 16 Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server ed itions. 3219 16 The file or filegroup "%.*ls" cannot be selected for this operat ion. 3221 16 The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d. 3222 16 The WriteFileEx system function executed on file '%ls' only wrot e %d bytes, expected %d. 3224 16 Cannot create worker thread. 3227 16 The backup media on "%ls" is part of media family %d which has a lready been processed on "%ls". Ensure that backup devices are correctly specifi ed. For tape devices, ensure that the correct volumes are loaded. 3229 16 Request for device '%ls' timed out. 3230 16 Operation on device '%ls' exceeded retry count. 3231 16 The media loaded on "%ls" is formatted to support %d media famil ies, but %d media families are expected according to the backup device specifica tion. 3232 16 The volume mounted on "%ls" does not have the expected backup se t identity. The volume may be obsolete due to a more recent overwrite of this me dia family. In that case, locate the correct volume with sequence number %d of m edia family %d. 3234 16 Logical file '%.*ls' is not part of database '%ls'. Use RESTORE

FILELISTONLY to list the logical file names. 3235 16 The file "%.*ls" is not part of database "%ls". You can only lis t files that are members of this database. 3239 16 The backup set on device '%ls' uses a feature of the Microsoft T ape Format not supported by SQL Server. 3240 16 Backup to mirrored media sets requires all mirrors to append. Pr ovide all members of the set, or reformat a new media set. 3241 16 The media family on device '%ls' is incorrectly formed. SQL Serv er cannot process this media family. 3242 16 The file on device '%ls' is not a valid Microsoft Tape Format ba ckup set. 3243 16 The media family on device '%ls' was created using Microsoft Tap e Format version %d.%d. SQL Server supports version %d.%d. 3244 16 Descriptor block size exceeds %d bytes. Use a shorter name and/o r description string and retry the operation. 3245 16 Could not convert a string to or from Unicode, %ls. 3246 16 The media family on device '%ls' is marked as nonappendable. Rei ssue the statement using the INIT option to overwrite the media. 3247 16 The volume on device '%ls' has the wrong media sequence number ( %d). Remove it and insert volume %d. 3249 16 The volume on device '%ls' is a continuation volume for the back up set. Remove it and insert the volume holding the start of the backup set. 3250 16 The value '%d' is not within range for the %ls parameter. 3251 10 The media family on device '%ls' is complete. The device is now being reused for one of the remaining families. 3253 16 The block size parameter must supply a value that is a power of 2. 3254 16 The volume on device '%ls' is empty. 3255 16 The data set on device '%ls' is a SQL Server backup set not comp atible with this version of SQL Server. 3256 16 The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally. 3257 16 There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64 u bytes are available. 3258 16 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 th e correct media. 3260 16 An internal buffer has become full. 3261 16 SQL Server cannot use the virtual device configuration. 3262 10 The backup set on file %d is valid. 3263 16 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 vo lume, or sequence number %d of family %d for the current set. 3264 16 The operation did not proceed far enough to allow RESTART. Reiss ue the statement without the RESTART qualifier. 3265 16 The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. 3266 16 The backup data at the end of "%ls" is incorrectly formatted. Ba ckup sets on the media might be damaged and unusable. To determine the backup se ts on the media, use RESTORE HEADERONLY. To determine the usability of the backu p sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reform at the media using BACKUP WITH FORMAT, which destroys all the backup sets. 3267 16 Insufficient resources to create UMS scheduler. 3268 16 Cannot use the backup file '%ls' because it was originally forma tted with sector size %d and is now on a device with sector size %d. 3269 16 Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d. 3270 16 An internal consistency error has occurred. This error is simila r to an assert. Contact technical support for assistance.

3271 16 A nonrecoverable I/O error occurred on file "%ls:" %ls. 3272 16 The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the stat ement using a compatible block size. 3276 16 WITH SNAPSHOT can be used only if the backup set was created WIT H SNAPSHOT. 3277 16 WITH SNAPSHOT must be used with only one virtual device. 3278 16 Failed to encrypt string %ls 3279 16 Access is denied due to a password failure 3280 16 Backups on raw devices are not supported. '%ls' is a raw device. 3281 10 Released and initiated rewind on '%ls'. 3283 16 The file "%ls" failed to initialize correctly. Examine the error logs for more details. 3284 16 Filemark on device '%ls' is not aligned. Re-issue the Restore st atement with the same blocksize used to create the backupset: '%d' looks like a possible value. 3285 10 Filemark on device '%ls' appears not to be aligned. The restore operation will proceed using less efficient I/O. To avoid this, re-issue the Re store statement with the same blocksize used to create the backupset: '%d' looks like a possible value. 3286 16 Backup failed because there is a mismatch in file metadata for f ile %d. 3301 21 The transaction log contains a record (logop %d) that is not val id. The log has been corrupted. Restore the database from a full backup, or repa ir the database. 3302 21 Redoing of logged operations in database '%.*ls' failed to reach end of log at log record ID %S_LSN. This indicates corruption around log recor d ID %S_LSN. Restore the database from a full backup, or repair the database. 3303 10 Remote harden of transaction '%.*ls' (ID 0x%016I64x %ls) started at %S_DATE in database '%ls' at LSN %S_LSN failed. 3313 21 During redoing of a logged operation in database '%.*ls', an err or occurred at log record ID %S_LSN. Typically, the specific failure is previous ly logged as an error in the Windows Event Log service. Restore the database fro m a full backup, or repair the database. 3314 21 During undoing of a logged operation in database '%.*ls', an err or occurred at log record ID %S_LSN. Typically, the specific failure is logged p reviously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database. 3315 21 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' und er transaction %S_XID. Restore a backup of the database, or repair the database. 3316 21 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 fr om a full backup, or repair the database. 3401 10 Errors occurred during recovery while rolling back a transaction . The transaction was deferred. Restore the bad page or file, and re-run recover y. 3402 10 The database '%ls' is marked %ls and is in a state that does not allow recovery to be run. 3403 10 Recovering only master database because traceflag 3608 was speci fied. This is an informational message only. No user action is required. 3404 10 Failed to check for new installation or a renamed server at star tup. The logic for this check has failed unexpectedly. Run setup again, or fix t he problematic registry key. 3406 10 %d transactions rolled forward in database '%.*ls' (%d:%d). This is an informational message only. No user action is required. 3407 10 %d transactions rolled back in database '%.*ls' (%d:%d). This is an informational message only. No user action is required. 3408 10 Recovery is complete. This is an informational message only. No user action is required.

3409 16 Performance counter shared memory setup failed with error %d. Re install sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions. 3410 10 Data in filegroup %s is offline, and deferred transactions exist . Use RESTORE to recover the filegroup, or drop the filegroup if you never inten d to recover it. Log truncation cannot occur until this condition is resolved. 3411 21 Configuration block version %d is not a valid version number. SQ L Server is exiting. Restore the master database or reinstall. 3412 10 Warning: The server instance was started using minimal configura tion startup option (-f). Starting an instance of SQL Server with minimal config uration places the server in single-user mode automatically. After the server h as been started with minimal configuration, you should change the appropriate se rver option value or values, stop, and then restart the server. 3413 21 Database ID %d. Could not mark database as suspect. Getnext NC s can on sys.databases.database_id failed. Refer to previous errors in the error l og to identify the cause and correct any associated problems. 3414 10 An error occurred during recovery, preventing the database '%ls' (%d:%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 Techn ical Support. 3415 16 Database '%.*ls' cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the fil es. Make the database or files writeable, and rerun recovery. 3416 16 The server contains read-only files that must be made writable b efore the server can be recollated. 3417 21 Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more informati on about how to rebuild the master database, see SQL Server Books Online. 3418 10 Recovery is unable to defer error %d. Errors can only be deferre d in databases using the full recovery model and an active backup log chain. 3419 16 Recovery for database '%.*ls' is being skipped because it requir es an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence. 3420 21 Database snapshot '%ls' has failed an IO operation and is marked suspect. It must be dropped and recreated. 3421 10 Recovery completed for database %ls (database ID %d) in %I64d se cond(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms.) This is an informatio nal message only. No user action is required. 3422 10 Database %ls was shutdown due to error %d in routine '%hs'. Rest art for non-snapshot databases will be attempted after all connections to the da tabase are aborted. 3429 10 Recovery could not determine the outcome of a cross-database tra nsaction %S_XID, named '%.*ls', in database '%.*ls' (database ID %d:%d). The coo rdinating database (database ID %d:%d) was unavailable. The transaction was assu med to be committed. If the transaction was not committed, you can retry recover y when the coordinating database is available. 3431 21 Could not recover database '%.*ls' (database ID %d) because of u nresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (M S DTC) transactions were prepared, but MS DTC was unable to determine the resolu tion. To resolve, either fix MS DTC, restore from a full backup, or repair the d atabase. 3434 20 Cannot change sort order or locale. An unexpected failure occurr ed 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 an d correct previous errors and then retry the operation. 3437 21 An error occurred while recovering database '%.*ls'. Unable to c onnect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the co mpletion status of transaction %S_XID. Fix MS DTC, and run recovery again. 3441 21 During startup of warm standby database '%.*ls' (database ID %d) , its standby file ('%ls') was inaccessible to the RESTORE statement. The operat

ing system error was '%ls'. Diagnose the operating system error, correct the pro blem, and retry startup. 3443 21 Database '%ls' (database ID %d:%d) was marked for standby or rea d-only use, but has been modified. The RESTORE LOG statement cannot be performed . Restore the database from a backup. 3445 21 File '%ls' is not a valid undo file for database '%.*ls (databas e ID %d). Verify the file path, and specify the correct file. 3446 16 Primary log file is not available for database '%ls' (%d:%d). T he log cannot be backed up. 3447 16 Could not activate or scan all of the log files for database '%. *ls'. 3448 21 Rollback encountered a page with a log sequence number (LSN) les s than the original log record LSN. Could not undo log record %S_LSN, for transa ction ID %S_XID, on page %S_PGID, database '%ls' (%d:%d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. Restore or rep air the database. 3449 21 SQL Server must shut down in order to recover a database (databa se 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 a nother startup, repair or restore the database. 3450 10 Recovery of database '%.*ls' (%d) is %d%% complete (approximatel y %d seconds remain). Phase %d of 3. This is an informational message only. No u ser action is required. 3452 10 Recovery of database '%.*ls' (%d) detected possible identity val ue inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls'). 3453 16 This version cannot redo any index creation or non-logged operat ion done by SQL Server 7.0. Further roll forward is not possible. 3454 10 Recovery is writing a checkpoint in database '%.*ls' (%d). This is an informational message only. No user action is required. 3456 21 Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, allocation unit %I64d, database '%.*ls' (database ID %d). Page: LS N = %S_LSN, allocation unit = %I64d, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the datab ase. 3457 21 Transactional file system resource manager '%.*ls' failed to rec over. For more information, see the accompanying error message, which determines the appropriate user action. 3458 16 Recovery cannot scan database "%.*ls" for dropped allocation uni ts because an unexpected error has occurred. These allocation units cannot be cl eaned up. 3459 16 Recovery of database "%.*ls" failed to redo a file add for file "%.*ls". Please delete the file and retry. 3505 14 Only the owner of database "%.*ls" or someone with relevant perm issions can run the CHECKPOINT statement. 3604 10 Duplicate key was ignored. 3605 16 Schema verification failed for database '%.*ls'. 3606 10 Arithmetic overflow occurred. 3607 10 Division by zero occurred. 3608 16 Cannot allocate a GUID for the token. 3609 16 The transaction ended in the trigger. The batch has been aborted . 3611 10 %hs SQL Server Execution Times:%hs CPU time not measured under fiber mode, elapsed time = %lu ms. 3612 10 %hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms. 3613 10 SQL Server parse and compile time: %hs CPU time = %lu ms, elap sed time = %lu ms. 3615 10 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-ah ead reads %d.

3616 16 An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back. 3619 10 Could not write a checkpoint record in database %ls because the log is out of space. Contact the database administrator to truncate the log or a llocate more space to the database log files. 3620 10 Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. Automatic checkpointing will be enabled when the databa se owner successfully checkpoints the database. Contact the database owner to ei ther truncate the log file or add more disk space to the log. Then retry the CHE CKPOINT statement. 3621 10 The statement has been terminated. 3622 10 Warning: An invalid floating point operation occurred. 3623 16 An invalid floating point operation occurred. 3624 20 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 sen t to Microsoft. An update might be available from Microsoft in the latest Servic e Pack or in a QFE from Technical Support. 3625 20 '%hs' is not yet implemented. 3627 17 New parallel operation cannot be started due to too many paralle l operations executing at this time. Use the "max worker threads" configuration option to increase the number of allowable threads, or reduce the number of para llel operations running on the system. 3628 24 The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator. 3633 16 The operating system returned the error '%ls' while attempting ' %ls' on '%ls' at '%hs'(%d). 3634 16 The operating system returned the error '%ls' while attempting ' %ls' on '%ls'. 3635 16 An error occurred while processing '%ls' metadata for database i d %d, file id %d, and transaction='%.*ls'. Additional Context='%ls'. Location='% hs'(%d). Retry the operation; if the problem persists, contact the database admi nistrator to review locking and memory configurations. Review the application fo r possible deadlock conflicts. 3636 16 An error occurred while processing '%ls' metadata for database i d %d file id %d. 3637 16 A parallel operation cannot be started from a DAC connection. 3639 16 This operation is not supported on a single-file DB. 3641 10 Total logical reads %lu, physical reads %lu, writes %lu. 3642 10 Table '%.*ls'. Segment reads %u, segment skipped %u. 3701 11 Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or y ou do not have permission. 3702 16 Cannot drop database "%.*ls" because it is currently in use. 3703 16 Cannot detach the %S_MSG '%.*ls' because it is currently in use. 3705 16 Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Us e %ls. 3706 16 Cannot %S_MSG a database snapshot. 3707 16 Cannot detach a suspect or recovery pending database. It must be repaired or dropped. 3708 16 Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG. 3709 16 Cannot %S_MSG the database while the database snapshot "%.*ls" r efers to it. Drop that database first. 3710 16 Cannot detach an opened database when the server is in minimally configured mode. 3716 16 The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG. 3717 16 Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.

3721 16 Type '%.*ls' cannot be renamed because it is being referenced by object '%.*ls'. 3723 16 An explicit DROP INDEX is not allowed on index '%.*ls'. It is be ing used for %ls constraint enforcement. 3724 16 Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for re plication. 3725 16 The constraint '%.*ls' is being referenced by table '%.*ls', for eign key constraint '%.*ls'. 3726 16 Could not drop object '%.*ls' because it is referenced by a FORE IGN KEY constraint. 3727 10 Could not drop constraint. See previous errors. 3728 16 '%.*ls' is not a constraint. 3729 16 Cannot %ls '%.*ls' because it is being referenced by object '%.* ls'. 3730 16 Cannot drop the default constraint '%.*ls' while it is being use d by a foreign key as SET DEFAULT referential action. 3732 16 Cannot drop type '%.*ls' because it is being referenced by objec t '%.*ls'. There may be other objects that reference this type. 3733 16 Constraint '%.*ls' does not belong to table '%.*ls'. 3734 16 Could not drop the primary key constraint '%.*ls' because the ta ble has an XML or spatial index. 3735 16 The primary key constraint '%.*ls' on table '%.*ls' cannot be dr opped because change tracking is enabled on the table. Change tracking requires a primary key constraint on the table. Disable change tracking before dropping t he constraint. 3737 16 Could not delete file '%ls'. See the SQL Server error log for mo re information. 3738 10 Deleting database file '%ls'. 3739 11 Cannot %ls the index '%.*ls' because it is not a statistics coll ection. 3740 16 Cannot drop the %S_MSG '%.*ls' because at least part of the tabl e resides on a read-only filegroup. 3741 16 Cannot drop the %S_MSG '%.*ls' because at least part of the tabl e resides on an offline filegroup. 3743 16 The database '%.*ls' is enabled for database mirroring. Database mirroring must be removed before you drop the database. 3744 16 Only a single clause is allowed in a statement where an index is dropped online. 3745 16 Only a clustered index can be dropped online. 3746 16 Cannot drop the clustered index of view '%.*ls' because the view is being used for replication. 3747 16 Cannot drop a clustered index created on a view using drop clust ered index clause. Clustered index '%.*ls' is created on view '%.*ls'. 3748 16 Cannot drop non-clustered index '%.*ls' using drop clustered ind ex clause. 3749 16 Cannot drop XML Index '%.*ls' using old 'Table.Index' syntax, us e 'Index ON Table' syntax instead. 3750 10 Warning: Index '%.*ls' on %S_MSG '%.*ls' was disabled as a resul t of disabling the clustered index on the %S_MSG. 3751 16 Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with '%. *ls' because '%.*ls' is a %S_MSG. Use %ls. 3752 16 The database '%.*ls' is currently joined to an availability grou p. Before you can drop the database, you need to remove it from the availatilit y group. 3800 16 Column name '%.*ls' is not sufficiently different from the names of other columns in the table '%.*ls'. 3801 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" may be impacted by the collation upgrade. Run DBCC CHECKTABLE. 3802 10 Warning: The constraint "%.*ls" on "%.*ls"."%.*ls" may be impact ed by the collation upgrade. Disable and enable WITH CHECK.

3803 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled becaus e the implementation of the checksum function has changed. 3804 10 Warning: The check constraint "%.*ls" on table "%.*ls"."%.*ls" i s disabled because the implementation of the checksum function has changed. 3805 10 Warning: Index "%.*ls" on table "%.*ls"."%.*ls" might be corrupt ed because it references computed column "%.*ls" containing a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify index. Consider us ing explicit CONVERT with deterministic date style such as 121. Computed column indexes referencing non-deterministic expressions can't be created in 90 compati bility mode. See Books Online topic "Creating Indexes on Computed Columns" for m ore information. 3806 10 Warning: Indexed view "%.*ls"."%.*ls" might be corrupted because it contains a non-deterministic conversion from string to date. Run DBCC CHECKT ABLE to verify view. Consider using explicit CONVERT with deterministic date sty le such as 121. Indexed views referencing non-deterministic expressions can't be created in 90 compatibility mode. See Books Online topic "Creating Indexed View s" for more information. 3807 17 Create failed because all available identifiers have been exhaus ted. 3808 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled becaus e the index is defined on a view with ignore_dup_key index option. Drop the inde x and, if possible, recreate it without ignore_dup_key option. You may need to c hange the logical structure of the view to ensure all rows are unique. 3809 16 Upgrade of database "%.*ls" failed because index "%.*ls" on obje ct ID %d has the same name as that of another index on the same table. 3810 10 Event notification "%.*ls" on assembly is dropped. 3811 10 Event notification "%.*ls" on service queue is dropped as broker instance is not specified. 3812 10 Event notification "%.*ls" on object is dropped. 3813 16 Upgrade of login '%.*ls' failed because its name or sid is a dup licate of another login or server role. 3814 16 Local login mapped to remote login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the remote login before upgrade. 3815 16 Local login mapped to linked login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the linked login before upgrade. 3816 16 Upgrade of login '%.*ls' failed because its password hash is inv alid. Update the login password before upgrade. 3817 10 Warning: The index "%.*ls" on "%.*ls"."%.*ls" was disabled becau se the implementation of "%.*ls" have changed. 3818 20 Invalid or unexpected message received. 3819 10 Warning: The check constraint "%.*ls" on "%.*ls"."%.*ls" was dis abled and set as not trusted because the implementation of "%.*ls" have changed. 3821 10 Warning: The foreign key constraint "%.*ls" on "%.*ls"."%.*ls" w as disabled because the implementation of '%.*ls' have changed. 3822 10 Warning: The heap "%.*ls"."%.*ls" has persisted computed columns that depends on a geometry or geography methods and may contain out-of-date inf ormation. Because of this, DBCC may report inconsistencies on this table. The p ersisted computed columns depending on geometry or geography methods should be u npersisted and persisted again to refresh the data. 3823 10 Warning: The object "%.*ls"."%.*ls" could not be bound and was i gnored during upgrade. Consider reviewing and correcting its definition. 3827 10 Warning: The table "%.*ls"."%.*ls" is unavailable because it con tains a persisted computed column that depends on "%.*ls", the implementation of which has changed. Rebuild the table offline and reconstruct the persisted comp uted column. 3829 10 Metadata cache entry %d:%d in database ID(%d) is not checked for coherency due to lock timeout. 3830 10 Metadata cache coherency check for database ID(%d) did not find any inconsistency. 3851 10 An invalid row (%ls) was found in the system table sys.%ls%ls.

3852 10 Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sy s.%ls%ls. 3853 10 Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a match ing row (%ls) in sys.%ls%ls. 3854 10 Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (% ls) in sys.%ls%ls that is invalid. 3855 10 Attribute (%ls) exists without a row (%ls) in sys.%ls%ls. 3856 10 Attribute (%ls) exists but should not for row (%ls) in sys.%ls%l s. 3857 10 The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls. 3858 10 The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid va lue. 3859 10 Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE. 3860 10 Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use. 3862 10 CLR type '%.*ls'.'%.*ls' is disabled because the on disk format for this CLR type has been changed. Use DROP TYPE to remove this disabled type. 3864 23 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. 3865 16 The operation on object '%.*ls' is blocked. The object is a File Table system defined object and user modifications are not allowed. 3866 10 The operation on FileTable system defined object '%.*ls' was all owed because of traceflag settings. To prevent this informational message from a ppearing in the error log, use DBCC TRACEOFF to turn off the trace flag. 3867 10 The FileTable object '%.*ls' contains system defined constraints that cannot be modified as long as the FILETABLE_NAMESPACE option is enabled on the table. Only user defined constraints have been updated. 3901 16 The transaction name must be specified when it is used with the mark option. 3902 16 The COMMIT TRANSACTION request has no corresponding BEGIN TRANSA CTION. 3903 16 The ROLLBACK TRANSACTION request has no corresponding BEGIN TRAN SACTION. 3904 21 Cannot unsplit logical page %S_PGID in object '%.*ls', in databa se '%.*ls'. Both pages together contain more data than will fit on one page. 3906 16 Failed to update database "%.*ls" because the database is read-o nly. 3908 16 Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in emergency mode or is damaged and must be restarted. 3909 16 Session binding token is invalid. 3910 16 Transaction context in use by another session. 3912 16 Cannot bind using an XP token while the server is not in an XP c all. 3913 16 TDS reset connection protocol error. Client driver requested bot h ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server. 3914 16 The data type "%s" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max). 3915 16 Cannot use the ROLLBACK statement within an INSERT-EXEC statemen t. 3916 16 Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first. 3917 16 Session is bound to a transaction context that is in use. Other statements in the batch were ignored. 3918 16 The statement or function must be executed in the context of a u ser transaction. 3919 16 Cannot enlist in the transaction because the transaction has alr

eady been committed or rolled back. 3920 10 The WITH MARK option only applies to the first BEGIN TRAN WITH M ARK statement. The option is ignored. 3921 16 Cannot get a transaction token if there is no transaction active . Reissue the statement after a transaction has been started 3922 16 Cannot enlist in the transaction because the transaction does no t exist. 3923 10 Cannot use transaction marks on database '%.*ls' with bulk-logge d operations that have not been backed up. The mark is ignored. 3924 10 The session was enlisted in an active user transaction while try ing to bind to a new transaction. The session has defected from the previous use r transaction. 3925 16 Invalid transaction mark name. The 'LSN:' prefix is reserved. 3926 10 The transaction active in this session has been committed or abo rted by another session. 3927 10 The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction. 3928 16 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, det ermine the source of the contention. 3929 16 No distributed or bound transaction is allowed in single user da tabase. 3930 16 The current transaction cannot be committed and cannot support o perations that write to the log file. Roll back the transaction. 3931 16 The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction. 3932 16 The save point name "%.*ls" that was provided is too long. The m aximum allowed length is %d characters. 3933 16 Cannot promote the transaction to a distributed transaction beca use there is an active save point in this transaction. 3934 14 The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTIO N_CONTEXT. 3935 16 A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x. 3936 16 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 com mit time or a disk I/O error may have occurred. '%.*ls' was one of the one or mo re files involved. ErorrCode: 0x%x 3937 16 While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver. Error code : 0x%0x. 3938 18 The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction. The trans action will be rolled back. 3939 16 An uncommittable transaction was detected at the beginning of th e batch. The transaction was rolled back. This was caused by an error that occur red during the processing of a FILESTREAM request in the context of this transac tion. 3948 16 The transaction was terminated because of the availability repli ca config/state change or because ghost records are being deleted on the primary and the secondary availability replica that might be needed by queries running under snapshot isolation. Retry the transaction. 3949 16 Transaction aborted when accessing versioned row in table '%.*ls ' in database '%.*ls'. Requested versioned row was not found because the readabl e secondary access is not allowed for the operation that attempted to create the version. This might be timing related, so try the query again later.

3950 16 Version store scan timed out when attempting to read the next ro w. Please try the statement again later when the system is not as busy. 3951 16 Transaction failed in database '%.*ls' because the statement was run under snapshot isolation but the transaction did not start in snapshot isol ation. You cannot change the isolation level of the transaction to snapshot afte r the transaction has started unless the transaction was originally started unde r snapshot isolation level. 3952 16 Snapshot isolation transaction failed accessing database '%.*ls' because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation. 3953 16 Snapshot isolation transaction failed in database '%.*ls' becaus e the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered. 3954 16 Snapshot isolation transaction failed to start in database '%.*l s' because the ALTER DATABASE command that disallows snapshot isolation had star ted before this transaction began. The database is in transition to OFF state. Y ou will either need to change the isolation level of the transaction or re-enabl e the snapshot isolation in the database. 3955 16 Snapshot isolation transaction failed in database '%.*ls' becaus e the recovery was skipped for this database. You must recover the database befo re you can run a transaction under snapshot isolation. 3956 16 Snapshot isolation transaction failed to start in database '%.*l s' because the ALTER DATABASE command which enables snapshot isolation for this database has not finished yet. The database is in transition to pending ON state . You must wait until the ALTER DATABASE Command completes successfully. 3957 16 Snapshot isolation transaction failed in database '%.*ls' becaus e the database did not allow snapshot isolation when the current transaction sta rted. It may help to retry the transaction. 3958 16 Transaction aborted when accessing versioned row in table '%.*ls ' in database '%.*ls'. Requested versioned row was not found. Your tempdb is pro bably out of space. Please refer to BOL on how to configure tempdb for versionin g. 3959 10 Version store is full. New version(s) could not be added. A tran saction that needs to access the version store may be rolled back. Please refer to BOL on how to configure tempdb for versioning. 3960 16 Snapshot isolation transaction aborted due to update conflict. Y ou cannot use snapshot isolation to access table '%.*ls' directly or indirectly in database '%.*ls' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. 3961 16 Snapshot isolation transaction failed in database '%.*ls' becaus e the object accessed by the statement has been modified by a DDL statement in a nother concurrent transaction since the start of this transaction. It is disall owed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation. 3962 16 Bind to another transaction while executing SQL Server internal query is not supported. Check your logon trigger definition and remove any sp_bi ndsession usage if any. If this error is not happening during logon trigger exec ution, contact production support team. 3963 16 Transaction failed in database '%.*ls' because distributed trans actions are not supported under snapshot isolation. 3964 16 Transaction failed because this DDL statement is not allowed ins ide a snapshot isolation transaction. Since metadata is not versioned, a metadat a change can lead to inconsistency if mixed within snapshot isolation. 3965 16 The PROMOTE TRANSACTION request failed because there is no local transaction active. 3966 17 Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient s pace in tempdb. This transaction was marked as a victim earlier because it may n eed the row version(s) that have already been removed to make space in tempdb. R

etry the transaction 3967 17 Insufficient space in tempdb to hold row versions. Need to shri nk 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 b ack if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning. 3968 10 Snapshot isolation or read committed snapshot is not available i n database '%.*ls' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started w ith snapshot isolation will fail and a query running under read committed snapsh ot will succeed but will resort back to lock based read committed. 3969 16 Distributed transaction is not supported while running SQL Serve r internal query. Check your logon trigger definition and remove any distributed transaction usage if any. If this error is not happening during logon trigger e xecution, contact production support team. 3970 16 This operation conflicts with another pending operation on this transaction. The operation failed. 3971 16 The server failed to resume the transaction. Desc:%I64x. 3972 20 Incoming Tabular Data Stream (TDS) protocol is incorrect. Transa ction Manager event has wrong length. Event type: %d. Expected length: %d. Actua l length: %d. 3973 16 The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed. 3974 16 The number of databases in exclusive mode usage under a workspac e is limited. Because the limit has been exceeded, the operation failed. 3975 16 The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted. 3976 16 The transaction name has the odd length %d. The batch has been a borted. 3977 16 The savepoint name cannot be NULL. The batch has been aborted. 3978 16 Beginning a new transaction after rollback to save point is not allowed. 3979 16 The TM request is longer than expected. The request is not proce ssed. 3980 16 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 th e same session, which makes the session busy. 3981 16 The transaction operation cannot be performed because there are pending requests working on this transaction. 3982 16 New transaction is not allowed to be started while DTC or bound transaction is active. 3983 16 The operation failed because the session is not single threaded. 3984 16 Cannot acquire a database lock during a transaction change. 3985 16 An error occurred during the changing of transaction context. Th is is usually caused by low memory in the system. Try to free up more memory. 3986 19 The transaction timestamps ran out. Restart the server. 3987 10 SNAPSHOT ISOLATION is always enabled in this database. 3988 16 New transaction is not allowed because there are other threads r unning in the session. 3989 16 New request is not allowed to start because it should come with valid transaction descriptor. 3990 16 Transaction is not allowed to commit inside of a user defined ro utine, trigger or aggregate because the transaction is not started in that CLR l evel. Change application logic to enforce strict transaction nesting. 3991 16 The context transaction which was active before entering user de fined routine, trigger or aggregate "%.*ls" has been ended inside of it, which i s not allowed. Change application logic to enforce strict transaction nesting. 3992 16 Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate "%.*ls". This is not allowed and user tran

saction will be rolled back. Change application logic to enforce strict transact ion nesting. 3993 16 The user transaction that has been started in user defined routi ne, 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 enf orce strict transaction nesting. 3994 16 User defined routine, trigger or aggregate tried to rollback a t ransaction that is not started in that CLR level. An exception will be thrown to prevent execution of rest of the user defined routine, trigger or aggregate. 3995 16 Unknown transaction isolation level %d, valid value range is 0 t o 5. 3996 16 Snapshot isolation level is not supported for distributed transa ction. Use another isolation level or do not use distributed transaction. 3997 16 A transaction that was started in a MARS batch is still active a t the end of the batch. The transaction is rolled back. 3998 16 Uncommittable transaction is detected at the end of the batch. T he transaction is rolled back. 3999 17 Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information. 4001 10 Client sends a sp_reset_connection while there is still pending requests, server is disconnecting. 4002 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The stream ended unexpectedly. 4004 16 Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. 4005 16 Cannot update columns from more than one underlying table in a s ingle update call. 4006 16 You cannot delete rows from more than one underlying table in a single delete call. 4007 16 Cannot update or insert column "%.*ls". It may be an expression. 4008 16 The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver versions earlier than SQL Server 2005. Please resubmit the query using a more recent client driver. 4009 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The TDS headers contained errors. 4010 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The Query Notification TDS header contained errors. 4011 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The MARS TDS header contained errors. 4012 16 An invalid tabular data stream (TDS) collation was encountered. 4013 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The multiple active result sets (MARS) TDS header is missing. 4014 20 A fatal error occurred while reading the input stream from the n etwork. The session will be terminated (input error: %d, output error: %d). 4015 16 Language requested in login '%.*ls' is not an official name on t his SQL Server. Using server-wide default %.*ls instead. 4016 16 Language requested in 'login %.*ls' is not an official name on t his SQL Server. Using user default %.*ls instead. 4017 16 Neither the language requested in 'login %.*ls' nor user default language %.*ls is an official language name on this SQL Server. Using server-wi de default %.*ls instead. 4018 16 User default language %.*ls is not an official language name on this SQL Server. Using server-wide default %.*ls instead. 4019 16 Language requested in login '%.*ls' is not an official language name on this SQL Server. Login fails. 4020 16 Default date order '%.*ls' for language %.*ls is invalid. Using mdy instead. 4021 16 Resetting the connection results in a different state than the i nitial login. The login fails. 4022 16 Bulk load data was expected but not sent. The batch will be term

inated. 4027 16 Mount tape for %hs of database '%ls' on tape drive '%ls'. 4028 16 End of tape has been reached. Remove tape '%ls' and mount next t ape for %hs of database '%ls'. 4030 10 The medium on device '%ls' expires on %hs and cannot be overwrit ten. 4035 10 Processed %I64d pages for database '%ls', file '%ls' on file %d. 4037 16 The user-specified MEDIANAME "%.*ls" does not match the MEDIANAM E "%ls" of the device "%ls". 4038 16 Cannot find file ID %d on device '%ls'. 4060 11 Cannot open database "%.*ls" requested by the login. The login f ailed. 4061 11 Neither the database "%.*ls" requested by the login nor the user default database could be opened. The master database is being used instead. 4062 11 Cannot open user default database. Using master database instead . 4063 11 Cannot open database "%.*ls" that was requested by the login. Us ing the user default database "%.*ls" instead. 4064 11 Cannot open user default database. Login failed. 4065 16 User is trying to use '%.*ls' through ODS, which is not supporte d any more. 4066 16 Type IDs larger than 65535 cannot be sent to clients shipped in SQL Server 2000 or earlier. 4067 16 CLR type serialization failed because an invalid cookie was spec ified. 4068 20 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 te rminated. 4069 16 The final value of the output parameter was null, and could not be sent to a 6.5 client expecting the parameter to be non-nullable. 4070 16 More than 255 columns were specified in the COMPUTE clause, and this metadata cannot be sent to a SQL Server version 6.5 client. 4071 10 The XP callback function '%.*ls' failed in extended procedure '% .*ls' because it was executed within an INSERT-EXEC statement which does not all ow the extended procedure to send information other than result set. 4072 10 The XP callback function '%.*ls' failed in extended procedure '% .*ls' because the extended procedure is called inside an UDF which doesn't allow sending data. 4073 16 A return value of data type varchar(max), nvarchar(max), varbina ry(max), XML or other large object type can not be returned to client driver ver sions earlier than SQL Server 2005. Please resubmit the query using a more rece nt client driver. 4074 16 Client drivers do not accept result sets that have more than 65, 535 columns. 4075 16 The USE database statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client opera ting 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 chan ging collations. 4076 16 The ALTER DATABASE statement failed because the database collati on %.*ls is not recognized by older client drivers. Try upgrading the client ope rating system or applying a service update to the database client software, or u se a different collation. See SQL Server Books Online for more information on ch anging collations. 4077 20 The statement failed because the sql_variant value uses collatio n %.*ls, which is not recognized by older client drivers. Try upgrading the clie nt operating system or applying a service update to the database client software , or use a different collation. See SQL Server Books Online for more information on changing collations. 4078 16 The statement failed because column '%.*ls' (ID=%d) uses collati

on %.*ls, which is not recognized by older client drivers. Try upgrading the cli ent operating system or applying a service update to the database client softwar e, or use a different collation. See SQL Server Books Online for more informatio n on changing collations. 4079 16 The statement failed due to arithmetic overflow when sending dat a stream. 4080 16 The incoming tabular data stream (TDS) protocol stream is incorr ect. The TRACE TDS header contained errors. 4081 16 The parameter '%.*ls' was deduced to be a table-valued parameter , which cannot be sent by client driver versions earlier than SQL Server 2008. P lease resubmit the query using a more recent client driver. 4101 16 Aggregates on the right side of an APPLY cannot reference column s from the left side. 4102 15 The READPAST lock hint is only allowed on target tables of UPDAT E and DELETE and on tables specified in an explicit FROM clause. 4103 15 "%.*ls": Temporary views are not allowed. 4104 16 The multi-part identifier "%.*ls" could not be bound. 4105 16 User-defined functions, partition functions, and column referenc es are not allowed in expressions in this context. 4107 16 Inserting into remote tables or views is not allowed by using th e BCP utility or by using BULK INSERT. 4108 16 Windowed functions can only appear in the SELECT or ORDER BY cla uses. 4109 16 Windowed functions cannot be used in the context of another wind owed function or aggregate. 4110 16 The argument type "%s" is invalid for argument %d of "%s". 4111 16 The CREATE SCHEMA statement should be followed by a name or auth orization keyword. 4112 16 The function '%.*ls' must have an OVER clause with ORDER BY. 4113 16 The function '%.*ls' is not a valid windowing function, and cann ot be used with the OVER clause. 4114 16 The function '%.*ls' takes exactly %d argument(s). 4115 16 The reference to column "%.*ls" is not allowed in an argument to a TOP, OFFSET, or FETCH clause. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here. 4116 16 The function 'ntile' takes only a positive int or bigint express ion as its input. 4117 16 Cannot retrieve table data for the query operation because the t able "%.*ls" schema is being altered too frequently. Because the table "%.*ls" c ontains 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 Serv er Profiler to identify what schema-altering operations are occurring. 4118 16 An invalid expression was specified in the FOR UPDATE clause. 4119 16 Default values cannot be assigned to property setters of columns with a CLR type. 4120 16 A user-defined function name cannot be prefixed with a database name in this context. 4121 16 Cannot find either column "%.*ls" or the user-defined function o r aggregate "%.*ls", or the name is ambiguous. 4122 16 Remote table-valued function calls are not allowed. 4124 16 The parameters supplied for the batch are not valid. 4126 16 No full-text indexed columns were found. 4127 16 At least one of the arguments to COALESCE must be an expression that is not the NULL constant. 4128 16 An internal error occurred during remote query execution. Contac t your SQL Server support professional and provide details about the query you w ere trying to run. 4129 16 The inline function "%.*ls" cannot take correlated parameters or subqueries because it uses a full-text operator. 4130 16 A duplicate hint was specified for the BULK rowset.

4131 16 A compile-time literal value is specified more than once for the variable "%.*ls" in one or more OPTIMIZE FOR clauses. 4132 16 The value specified for the variable "%.*ls" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's type. 4133 16 Only a scalar expression may be specified as the argument to the RETURN statement. 4134 16 Metadata stored on disk for computed column '%.*ls' in table '%. *ls' did not match the column definition. In order to avoid possible index corru ption, please drop and recreate this computed column. 4135 16 Synonym '%.*ls' is defined over queue '%.*ls'. Synonyms on queue s are not allowed. 4136 16 The hint '%.*ls' cannot be used with the hint '%.*ls'. 4137 16 A format file cannot be specified together with SINGLE_BLOB, SIN GLE_CLOB or SINGLE_NCLOB option. 4138 16 Conflicting locking hints are specified for table "%.*ls". This may be caused by a conflicting hint specified for a view. 4139 16 Cannot process the query because it references the common langua ge runtime (CLR) table-valued function "%.*ls" with a hint through view "%.*ls". 4140 15 The READCOMMITTEDLOCK lock hint is not allowed on the target tab le of an INSERT statement. 4141 16 Nested CLR type updates are not allowed. 4142 16 Aggregates are not allowed in the RECEIVE list. 4143 16 The bulk openrowset provider is not a valid target for %.*ls. 4144 16 The hint '%.*ls' is not allowed when inserting into remote table s. 4145 15 An expression of non-boolean type specified in a context where a condition is expected, near '%.*ls'. 4146 16 Statistics can only be created on columns. 4148 16 XML methods are not allowed in a GROUP BY clause. 4150 16 Hints are not allowed on recursive common table expression (CTE) references. Consider removing hint from recursive CTE reference '%.*ls'. 4151 16 The type of the first argument to NULLIF cannot be the NULL cons tant because the type of the first argument has to be known. 4152 16 Type "%.*ls" is not a CLR type. 4153 16 Cannot treat data type "%ls" as data type "%ls". 4154 16 UNNEST can only take an expression of type multiset. 4155 15 The SELECT list for the nested INSERT statement can only contain one item. 4156 16 The target of nested insert, nested update, or nested delete mus t be of type multiset. 4157 16 "%.*ls" is not a valid property, field, or method. 4158 16 The field "%.*ls" is referenced more than once in the set list, either directly or through a property. 4159 16 Delayed CLR type instances require local base table column as an argument. 4160 16 Could not find suitable key in table '%.*ls' for use in delayed CLR type fetching. 4161 16 Only CLR types are allowed in delayed CLR type fetching. 4162 16 A PROB_MATCH table can only be used inside of a PROB_MATCH query . 4163 16 A GROUP BY clause is required in a PROB_MATCH query. 4164 16 A GROUP BY clause in a PROB_MATCH query can only have key column s, and needs to include all the key columns. 4165 16 The score override argument, if present in one of the subqueries , must be present in all subqueries and must be the same constant and variable. 4166 16 Invalid PROB_MATCH subquery. 4167 16 Multiple PROB_MATCH subqueries can only refer to the same base t able. 4168 16 Invalid PROB_MATCH project item in the PROB_MATCH SELECT list. 4169 16 Applying TREAT more than once to the same expression is not allo

wed in a full-text property reference. 4170 16 The (ANY) specification can only be applied to expressions of ty pe multiset. 4171 16 Alias was not specified for an aggregate in the PROB_MATCH SELEC T list. 4172 16 Incorrect use of full-text %s. 4173 16 "%.*s" is not a valid scoring function name. 4174 16 Delayed CLR type instantiation fetch value query may only refere nce column of a large object or large value type. 4175 16 Nested updates cannot be performed on CLR types that are not For mat.Structured. 4176 16 Too many parameters were specified for FULLTEXTTABLE of type "Si mple". The maximum number of parameters is %d. 4177 16 The FROM clause of a PROB_MATCH query must consist of a single d erived table. 4184 16 Cannot retrieve table data for the query operation because the t able "%.*ls" schema is being altered too frequently. Because the table "%.*ls" c ontains a filtered index or filtered statistics, changes to the table schema req uire 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 ar e occurring. 4185 16 This action cannot be performed on a system type. 4186 16 Column '%ls.%.*ls' cannot be referenced in the OUTPUT clause bec ause the column definition contains a subquery or references a function that per forms user or system data access. A function is assumed by default to perform da ta access if it is not schemabound. Consider removing the subquery or function f rom the column definition or removing the column from the OUTPUT clause. 4187 16 Data type %ls of receiving variable cannot store all values of t he data type %ls of column '%.*ls' without data loss. 4188 16 Column or parameter '%.*ls' has type '%ls' and collation '%.*ls' . The legacy LOB types do not support Unicode supplementary characters whose cod epoints are U+10000 or greater. Change the column or parameter type to varchar(m ax), nvarchar(max) or use a collation which does not have the _SC flag. 4189 16 Cannot convert to text/ntext or collate to '%.*ls' because these legacy LOB types do not support the Unicode supplementary characters whose code points are U+10000 or greater. Use types varchar(max), nvarchar(max), or a colla tion which does not have the _SC flag. 4190 16 PIVOT operator is not allowed in the recursive part of a recursi ve common table expression '%.*ls'. 4191 16 Cannot resolve collation conflict for %ls operation. 4192 16 Cannot resolve collation conflict. 4193 16 '%.*ls' is not a valid window frame and cannot be used with the OVER clause. 4194 15 RANGE is only supported with UNBOUNDED and CURRENT ROW window fr ame delimiters. 4195 16 The reference to column "%.*ls" is not allowed in an argument to the NTILE function. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here. 4196 16 Column '%ls.%.*ls' cannot be referenced in the OUTPUT clause bec ause the column definition contains an expression using a window function. 4197 16 An internal query compilation error occured during binding. 4202 16 BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable. 4208 16 The statement %hs is not allowed while the recovery model is SIM PLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE. 4212 16 Cannot back up the log of the master database. Use BACKUP DATABA SE instead. 4214 16 BACKUP LOG cannot be performed because there is no current datab ase backup. 4215 10 The log was not truncated because records at the beginning of th

e log are pending replication or Change Data Capture. Ensure the Log Reader Agen t or capture job is running or use sp_repldone to mark transactions as distribut ed or captured. 4217 10 BACKUP LOG cannot modify the database because the database is re ad-only. The backup will continue, although subsequent backups will duplicate th e work of this backup. 4218 16 Bulk-logged operations exist in the database. Perform a BACKUP L OG. 4302 16 The option "%ls" conflicts with online restore. Remove the confl icting option and reissue the command. 4303 16 The roll forward start point is now at log sequence number (LSN) %.*s. Additional roll forward past LSN %.*s is required to complete the restore sequence. 4305 16 The log in this backup set begins at LSN %.*ls, which is too rec ent to apply to the database. An earlier log backup that includes LSN %.*ls can be restored. 4307 16 The online restore to database '%ls' failed. It may be appropria te to perform an offline restore instead. To force an offline restore, first tak e the database offline using the ALTER DATABASE statement. 4308 10 The online restore is complete, but WITH NORECOVERY was specifie d. Use RESTORE WITH RECOVERY to bring affected data online. 4309 16 The state of file "%ls" prevents restoring individual pages. On ly a file restore is currently possible. 4310 16 RESTORE PAGE is not allowed on file "%ls" because the file is no t online. 4311 16 RESTORE PAGE is not allowed from backups taken with earlier vers ions of SQL Server. 4312 16 This log cannot be restored because a gap in the log chain was c reated. Use more recent data backups to bridge the gap. 4315 10 Some files still require more restore steps before the online re store sequence can be completed. 4318 16 File '%ls' has been rolled forward to LSN %.*ls. This log termin ates at LSN %.*ls, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY. 4319 16 A previous restore operation was interrupted and did not complet e processing on file '%ls'. Either restore the backup set that was interrupted o r restart the restore sequence. 4320 16 The file "%ls" was not fully restored by a database or file rest ore. The entire file must be successfully restored before applying this backup s et. 4322 10 This backup set contains records that were logged before the des ignated point in time. The database is being left in the restoring state so that more roll forward can be performed. 4323 16 A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option. 4326 16 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 %.*l s can be restored. 4327 16 The log in this backup set contains bulk-logged changes. Point-i n-time recovery was inhibited. The database has been rolled forward to the end o f the log. 4328 16 The file "%ls" is missing. Roll forward stops at log sequence nu mber %.*ls. The file is created at log sequence number (LSN) %.*ls, dropped at L SN %.*ls. Restore the transaction log beyond the point in time when the file was dropped, or restore data to be consistent with rest of the database. 4329 10 This log file contains records logged before the designated mark . The database is being left in the Restoring state so you can apply another log file. 4330 16 This backup set cannot be applied because it is on a recovery pa

th 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 poi nt. 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 t o a different point in time. For more information about recovery paths, see SQL Server Books Online. 4331 16 The database cannot be recovered because the files have been res tored to inconsistent points in time. 4332 16 RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY. 4333 16 The database cannot be recovered because the log was not restore d. 4334 16 The named mark does not identify a valid LSN. 4335 16 The specified STOPAT time is too early. All or part of the datab ase is already rolled forward beyond that point. 4336 16 The filegroup "%ls" has been dropped and cannot be restored into the online database. 4337 16 The file "%ls" has been dropped and cannot be restored into the online database. 4338 16 The STOPAT clause specifies a point too early to allow this back up set to be restored. Choose a different stop point or use RESTORE DATABASE WIT H RECOVERY to recover at the current point. 4339 10 This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are n eeded. Previous messages indicate reasons why recovery cannot occur at this poin t. 4340 16 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 in cludes a timestamp. 4341 16 This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time. 4342 16 Point-in-time recovery is not possible unless the primary filegr oup is part of the restore sequence. Omit the point-in-time clause or restore th e primary filegroup. 4343 16 The database has been rolled forward to the end of this backup s et and beyond the specified point in time. RESTORE WITH RECOVERY can be used to accept the current recovery point. 4344 16 RESTORE PAGE is not allowed on read-only databases or filegroups . 4345 10 Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except mainten ance of the suspect_pages table. Check the error log for more information. 4346 16 RESTORE PAGE is not allowed with databases that use the simple r ecovery model. 4347 16 The current restore sequence was previously interrupted during t he transition to the online state. RESTORE DATABASE WITH RECOVERY can be used to complete the transition to online. 4348 16 The online restore to database '%ls' failed. It may be appropria te to perform an offline restore instead. An offline restore is initiated by usi ng BACKUP LOG WITH NORECOVERY. 4349 16 The log in this backup set begins at LSN %.*ls, which is too rec ent 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 ba ckup. 4350 16 The list of pages provided with the RESTORE PAGE statement is in correctly formatted. Prior to the problem %d pages were correctly identified. Th e problem was hit at character offset %d. Check that all pages are identified by numeric <file>:<page> pairs with commas separating each pair. For example: PAG E='1:57,2:31'. 4351 16 Backups taken on earlier versions of SQL Server are not supporte

d by fn_dump_dblog. 4352 16 RESTORE LOG is not supported from this data backup because file '%ls' is too old. Use a regular log backup to continue the restore sequence. 4353 16 Conflicting file relocations have been specified for file '%.*ls '. Only a single WITH MOVE clause should be specified for any logical file name. 4354 10 The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is being upgraded from a prior version. Piec emeal restore is not supported when an upgrade is involved. 4355 16 The revert command is incorrectly specified. The RESTORE stateme nt must be of the form: RESTORE DATABASE <x> FROM DATABASE_SNAPSHOT = <y>. 4356 10 Restore is complete on database '%ls'. The database is now avai lable. 4357 16 Restore cannot take '%ls' offline because changes exist that req uire a log backup. Take a log backup and then retry the RESTORE. 4358 16 The database can not be brought online because file '%ls' is cur rently restored to LSN %.*ls but must be restored to LSN %.*ls. 4359 16 The STOPAT option cannot be used with this partial restore seque nce because one or more FILESTREAM filegroups are not included. The CONTINUE_AFT ER_ERROR option can be used to force the recovery, but this should only be used if you do not intend to subsequently restore the FILESTREAM filegroups. 4360 16 RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Executio n of the RESTORE command was aborted. 4403 16 Cannot update the view or function '%.*ls' because it contains a ggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator. 4405 16 View or function '%.*ls' is not updatable because the modificati on affects multiple base tables. 4406 16 Update or insert of view or function '%.*ls' failed because it c ontains a derived or constant field. 4408 19 Too many tables. The query and the views or functions in it exce ed the limit of %d tables. Revise the query to reduce the number of tables. 4413 16 Could not use view or function '%.*ls' because of binding errors . 4414 16 Could not allocate ancillary table for view or function resoluti on. The maximum number of tables in a query (%d) was exceeded. 4415 16 View '%.*ls' is not updatable because either it was created WITH CHECK OPTION or it spans a view created WITH CHECK OPTION and the target table is referenced multiple times in the resulting query. 4416 16 UNION ALL view '%.*ls' is not updatable because the definition c ontains a disallowed construct. 4417 16 Derived table '%.*ls' is not updatable because the definition co ntains a UNION operator. 4418 16 Derived table '%.*ls' is not updatable because it contains aggre gates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator. 4420 16 Derived table '%.*ls' is not updatable because the modification affects multiple base tables. 4421 16 Derived table '%.*ls' is not updatable because a column of the d erived table is derived or constant. 4422 16 View '%.*ls' has an INSTEAD OF UPDATE trigger and cannot be a ta rget of an UPDATE FROM statement. 4423 16 View '%.*ls' has an INSTEAD OF DELETE trigger and cannot be a ta rget of a DELETE FROM statement. 4424 16 Joined tables cannot be specified in a query containing outer jo in operators. View or function '%.*ls' contains joined tables. 4425 16 Cannot specify outer join operators in a query containing joined tables. View or function '%.*ls' contains outer join operators. 4426 16 View '%.*ls' is not updatable because the definition contains a UNION operator. 4427 16 Cannot update the view "%.*ls" because it or a view it reference s was created with WITH CHECK OPTION and its definition contains a TOP or OFFSET clause.

4429 16 View or function '%.*ls' contains a self-reference. Views or fun ctions cannot reference themselves directly or indirectly. 4430 10 Warning: Index hints supplied for view '%.*ls' will be ignored. 4431 16 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a timestamp column. 4432 16 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a DEFAULT constraint. 4433 16 Cannot INSERT into partitioned view '%.*ls' because table '%.*ls ' has an IDENTITY constraint. 4434 16 Partitioned view '%.*ls' is not updatable because table '%.*ls' has an INSTEAD OF trigger. 4435 16 Partitioned view '%.*ls' is not updatable because a value was no t specified for partitioning column '%.*ls'. 4436 16 UNION ALL view '%.*ls' is not updatable because a partitioning c olumn was not found. 4437 16 Partitioned view '%.*ls' is not updatable as the target of a bul k operation. 4438 16 Partitioned view '%.*ls' is not updatable because it does not de liver all columns from its member tables. 4439 16 Partitioned view '%.*ls' is not updatable because the source que ry contains references to partition table '%.*ls'. 4440 16 UNION ALL view '%.*ls' is not updatable because a primary key wa s not found on table '%.*ls'. 4441 16 Partitioned view '%.*ls' is not updatable because the table '%.* ls' has an index on a computed column. 4442 16 UNION ALL view '%.*ls' is not updatable because base table '%.*l s' is used multiple times. 4443 16 UNION ALL view '%.*ls' is not updatable because column '%.*ls' o f base table '%.*ls' is used multiple times. 4444 16 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not included in the union result. 4445 16 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not unioned with primary keys of preceding tables. 4446 16 Cannot update the UNION ALL view "%.*ls" because the definition of column "%.*ls" of view "%.*ls" is used by another view column. 4447 16 View '%.*ls' is not updatable because the definition contains a set operator. 4448 16 Cannot INSERT into partitioned view '%.*ls' because values were not supplied for all columns. 4449 16 Using defaults is not allowed in views that contain a set operat or. 4450 16 Cannot update partitioned view '%.*ls' because the definition of the view column '%.*ls' in table '%.*ls' has an IDENTITY constraint. 4451 16 Views referencing tables on multiple servers are not updatable i n the edition of this SQL Server instance '%.*ls'. See books online for more det ails on feature support in different SQL Server editions. 4452 16 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' becaus e the table '%.*ls' has a CASCADE DELETE or CASCADE UPDATE constraint. 4453 16 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' becaus e the table '%.*ls' has a INSERT, UPDATE or DELETE trigger. 4454 16 Cannot update the partitioned view "%.*ls" because the partition ing columns of its member tables have mismatched types. 4456 16 The partitioned view "%.*ls" is not updatable because one or mor e of the non-partitioning columns of its member tables have mismatched types. 4457 16 The attempted insert or update of the partitioned view failed be cause the value of the partitioning column does not belong to any of the partiti ons. 4502 16 View or function '%.*ls' has more column names specified than co lumns defined. 4503 16 Could not create schemabound %S_MSG '%.*ls' because it reference

s an object in another database. 4504 16 Could not create %S_MSG '%.*ls' because CLR type '%.*ls' does no t exist in the target database '%.*ls'. 4505 16 CREATE VIEW failed because column '%.*ls' in view '%.*ls' exceed s the maximum of %d columns. 4506 16 Column names in each view or function must be unique. Column nam e '%.*ls' in view or function '%.*ls' is specified more than once. 4508 16 Views or functions are not allowed on temporary tables. Table na mes that begin with '#' denote temporary tables. 4510 16 Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable. 4511 16 Create View or Function failed because no column name was specif ied for column %d. 4512 16 Cannot schema bind %S_MSG '%.*ls' because name '%.*ls' is invali d for schema binding. Names must be in two-part format and an object cannot refe rence itself. 4513 16 Cannot schema bind %S_MSG '%.*ls'. '%.*ls' is not schema bound. 4514 16 CREATE FUNCTION failed because a column name is not specified fo r column %d. 4515 16 CREATE FUNCTION failed because column '%.*ls' in function '%.*ls ' exceeds the maximum of %d columns. 4516 16 Cannot schema bind function '%.*ls' because it contains an EXECU TE statement. 4517 16 Service queue object cannot be used in schemabinding expressions . '%.*ls' is a service queue. 4519 16 Cannot %S_MSG %S_MSG '%.*ls' on view '%.*ls' because it is a sys tem generated view that was created for optimization purposes. 4520 16 Cannot disable index on view '%.*ls' because it is a system gene rated view that was created for optimization purposes. 4521 16 Cannot use object '%.*ls' with autodrop object attribute in sche mabinding expressions because it is a system generated view that was created for optimization purposes. 4522 16 Cannot alter view '%.*ls' because it is a system generated view that was created for optimization purposes. 4523 16 Cannot create trigger on view '%.*ls' because it is a system gen erated view that was created for optimization purposes. 4602 14 Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission. 4604 16 There is no such user or group '%.*ls' or you do not have permis sion. 4606 16 Granted or revoked privilege %ls is not compatible with object. 4610 16 You can only grant or revoke permissions on objects in the curre nt database. 4611 16 To revoke or deny grantable privileges, specify the CASCADE opti on. 4613 16 Grantor does not have GRANT permission. 4615 16 Invalid column name '%.*ls'. 4616 16 You cannot perform this operation for the resource database. 4617 16 Cannot grant, deny or revoke permissions to or from special role s. 4618 16 You do not have permission to use %.*ls in the AS clause. 4619 16 CREATE DATABASE permission can only be granted in the master dat abase. 4620 16 All permissions in a grant/deny/revoke statement should be at th e same scope (e.g., server or database) 4621 16 Permissions at the server scope can only be granted when the cur rent database is master 4622 16 Permissions at the server scope can only be granted to logins 4623 16 The all permission has been deprecated and is not available for this class of entity

4624 16 Cannot grant, deny, or revoke permissions to sa, dbo, entity own er, information_schema, sys, or yourself. 4625 16 There is no such server principal %.*s or you do not have permis sion. 4627 16 Cannot grant, deny, or revoke the connect database permission to application roles. 4628 16 The ALL permission is deprecated and maintained only for compati bility. It DOES NOT imply ALL permissions defined on the entity. 4629 16 Permissions on server scoped catalog views or system stored proc edures or extended stored procedures can be granted only when the current databa se is master. 4701 16 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 4707 16 Could not truncate object '%.*ls' because it or one of its index es resides on a READONLY filegroup '%.*ls'. 4708 16 Could not truncate object '%.*ls' because it is not a table. 4709 16 You are not allowed to truncate the system table '%.*ls'. 4710 16 Could not truncate object '%.*ls' because it or one of its index es resides on an offline filegroup '%.*ls'. 4711 16 Cannot truncate table '%.*ls' because it is published for replic ation or enabled for Change Data Capture. 4712 16 Cannot truncate table '%.*ls' because it is being referenced by a FOREIGN KEY constraint. 4801 16 Insert bulk is not supported over this access protocol. 4802 16 The SINGLE_LOB, SINGLE_CLOB, and SINGLE_NCLOB options are mutual ly exclusive with all other options. 4803 21 The bulk copy (bcp) client has sent a row length of %d. This is not a valid size. The maximum row size is %d. Use a supported client application programming interface (API). 4804 21 While reading current row from host, a premature end-of-message was encountered--an incoming data stream was interrupted when the server expecte d to see more data. The host program may have terminated. Ensure that you are us ing a supported client application programming interface (API). 4805 17 The front-end tool you are using does not support bulk load from host. Use the supported tools for this command. 4806 16 SINGLE_CLOB requires a double-byte character set (DBCS) (char) i nput file. The file specified is Unicode. 4807 21 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 progr amming interface (API). 4808 16 Bulk copy operations cannot trigger bulk load statements. 4809 16 SINGLE_NCLOB requires a UNICODE (widechar) input file. The file specified is not Unicode. 4810 16 Expected the TEXT token in data stream for bulk copy of text or image data. 4811 16 Expected the column offset in data stream for bulk copy of text or image data. 4812 16 Expected the row offset in data stream for bulk copy of text or image data. 4813 16 Expected the text length in data stream for bulk copy of text, n text, or image data. 4814 16 Bulk copy into a partitioned table is not supported for down-lev el clients. 4815 16 Received an invalid column length from the bcp client for colid %d. 4816 16 Invalid column type from bcp client for colid %d. 4817 16 Could not bulk load. The sorted column '%.*ls' is not valid. The ORDER hint is ignored. 4818 16 Could not bulk load. The sorted column '%.*ls' was specified mor e than once. The ORDER hint is ignored.

4819 16 Cannot bulk load. The bulk data stream was incorrectly specified as sorted or the data violates a uniqueness constraint imposed by the target ta ble. Sort order incorrect for the following two rows: primary key of first row: %s, primary key of second row: %s. 4820 16 Cannot bulk load. Unknown version of format file "%s". 4821 16 Cannot bulk load. Error reading the number of columns from the f ormat file "%s". 4822 16 Cannot bulk load. Invalid number of columns in the format file " %s". 4823 16 Cannot bulk load. Invalid column number in the format file "%s". 4824 16 Cannot bulk load. Invalid data type for column number %d in the format file "%s". 4825 16 Cannot bulk load. Invalid prefix for column number %d in the for mat file "%s". 4826 16 Cannot bulk load. Invalid column length for column number %d in the format file "%s". 4827 16 Cannot bulk load. Invalid column terminator for column number %d in the format file "%s". 4828 16 Cannot bulk load. Invalid destination table column number for so urce column %d in the format file "%s". 4829 16 Cannot bulk load. Error reading the destination table column nam e for source column %d in the format file "%s". 4830 10 Bulk load: DataFileType was incorrectly specified as char. DataF ileType will be assumed to be widechar because the data file has a Unicode signa ture. 4831 10 Bulk load: DataFileType was incorrectly specified as widechar. D ataFileType will be assumed to be char because the data file does not have a Uni code signature. 4832 16 Bulk load: An unexpected end of file was encountered in the data file. 4833 16 Bulk load: Version mismatch between the provider dynamic link li brary and the server executable. 4834 16 You do not have permission to use the bulk load statement. 4835 16 Bulk copying into a table with computed columns is not supported for downlevel clients. 4836 10 Warning: Table "%.*s" is published for merge replication. Reinit ialize affected subscribers or execute sp_addtabletocontents to ensure that data added is included in the next synchronization. 4837 16 Cannot bulk copy into a table "%.*s" that is enabled for immedia te-updating subscriptions. 4838 16 The bulk data source does not support the SQLNUMERIC or SQLDECIM AL data types. 4839 16 Cannot perform the bulk load. Invalid collation name for source column %d in the format file "%s". 4840 16 The bulk data source provider string has an invalid %ls property value %ls. 4841 16 The data source name is not a simple object name. 4842 16 The required FormatFile property is missing from the provider st ring of the server. 4843 16 The bulk data source provider string has a syntax error ('%lc') near character position %d. 4844 16 The bulk data source provider string has an unsupported property name (%ls). 4845 16 The bulk data source provider string has a syntax error near cha racter position %d. Expected '%lc', but found '%lc'. 4846 16 The bulk data provider failed to allocate memory. 4847 16 Bulk copying into a table with bigint columns is not supported f or versions earlier than SQL Server 2000. 4848 16 Bulk copying into a table with sql_variant columns is not suppor ted for versions earlier than SQL Server 2000.

4855 16 Line %d in format file "%ls": unexpected element "%ls". 4856 16 Line %d in format file "%ls": unexpected info item. 4857 16 Line %d in format file "%ls": Attribute "%ls" could not be speci fied for this type. 4858 16 Line %d in format file "%ls": bad value %ls for attribute "%ls". 4859 16 Line %d in format file "%ls": required attribute "%ls" is missin g. 4860 16 Cannot bulk load. The file "%ls" does not exist. 4861 16 Cannot bulk load because the file "%ls" could not be opened. Ope rating system error code %ls. 4862 16 Cannot bulk load because the file "%ls" is incomplete or could n ot be read. Operating system error code %ls. 4863 16 Bulk load data conversion error (truncation) for row %d, column %d (%ls). 4864 16 Bulk load data conversion error (type mismatch or invalid charac ter for the specified codepage) for row %d, column %d (%ls). 4865 16 Cannot bulk load because the maximum number of errors (%d) was e xceeded. 4866 16 The bulk load failed. The column is too long in the data file fo r row %d, column %d. Verify that the field terminator and row terminator are spe cified correctly. 4867 16 Bulk load data conversion error (overflow) for row %d, column %d (%ls). 4868 16 The bulk load failed. The codepage "%d" is not installed. Instal l the codepage and run the command again. 4869 16 The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL. 4870 16 Cannot bulk load because of an error writing file "%ls". Operati ng system error code %ls. 4871 16 Bulk load error while attempting to log errors. 4872 16 Line %d in format file "%ls": duplicate element id "%ls". 4873 16 Line %d in format file "%ls": referencing non-existing element i d "%ls". 4874 16 Line %d in format file "%ls": duplicate element id reference "%l s". 4875 16 Invalid column attribute from bcp client for colid %d. 4876 16 The Bulk Insert operation of SQL Server Destination has timed ou t. Please consider increasing the value of Timeout property on the SQL Server De stination in the dataflow. 4877 16 Error parsing DTS stream when reading row %d, column %d. 4880 16 Cannot bulk load. When you use the FIRSTROW and LASTROW paramete rs, the value for FIRSTROW cannot be greater than the value for LASTROW. 4881 10 Note: Bulk Insert through a view may result in base table defaul t values being ignored for NULL columns in the data file. 4882 16 Cannot bulk load. A prefix length, field length, or terminator i s required for the source column %d in the format file "%s". 4883 16 The XML reader returned 0x%08X for the info item starting near l ine %d column %d in format file "%ls". 4884 16 Unknown error near info item starting near line %d column %d in format file "%ls". 4885 16 Cannot open file "%ls". A Windows NT Integrated Security login i s required. 4886 16 Cannot open the file "%ls". Operating system error: %ls 4887 16 Cannot open the file "%ls". Only disk files are supported. 4888 16 Cannot open the file "%ls". The bulkadmin role membership is req uired. 4889 16 Cannot open the file "%ls". A unicode byte-order mark is missing . 4890 16 Insert bulk is not supported in showplan mode. 4891 16 Insert bulk failed due to a schema change of the target table.

4892 16 Bulk insert failed due to a schema change of the target table. 4893 16 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 l ocal server via Windows security. 4894 21 COLMETADATA must be present when using bcp. 4895 21 Unicode data is odd byte size for column %d. Should be even byte size. 4896 16 Invalid column value from bcp client for colid %d. 4897 16 Received an invalid length for chunked LOB data for colid %d. 4900 16 The ALTER TABLE SWITCH statement failed for table '%.*ls'. It is not possible to switch the partition of a table that has change tracking enable d. Disable change tracking before using ALTER TABLE SWITCH. 4901 16 ALTER TABLE only allows columns to be added that can contain nul ls, or have a DEFAULT definition specified, or the column being added is an iden tity or timestamp column, or alternatively if none of the previous conditions ar e 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 thes e conditions. 4902 16 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 4903 10 Warning: The specified partition %d for the table '%.*ls' was ig nored in ALTER TABLE SWITCH statement because the table is not partitioned. 4904 16 ALTER TABLE SWITCH statement failed. The specified partition %d of target table '%.*ls' must be empty. 4905 16 ALTER TABLE SWITCH statement failed. The target table '%.*ls' mu st be empty. 4906 16 '%ls' statement failed. The %S_MSG '%.*ls' is %S_MSG partitioned while index '%.*ls' is %S_MSG partitioned. 4907 16 '%ls' statement failed. The %S_MSG '%.*ls' has %d partitions whi le index '%.*ls' has %d partitions. 4908 16 '%ls' statement failed. The range boundary values used to partit ion the %S_MSG '%.*ls' are different from the range boundary values used for ind ex '%.*ls'. 4909 16 Cannot alter '%.*ls' because it is not a table. 4911 16 Cannot specify a partitioned table without partition number in A LTER TABLE SWITCH statement. The table '%.*ls' is partitioned. 4912 16 '%ls' statement failed. The columns set used to partition the %S _MSG '%.*ls' is different from the column set used to partition index '%.*ls'. 4913 16 ALTER TABLE SWITCH statement failed. The table '%.*ls' has clust ered index '%.*ls' while the table '%.*ls' does not have clustered index. 4914 16 The ALTER TABLE SWITCH statement failed. The table "%.*ls" has a disabled clustered index. 4915 16 '%ls' statement failed. The parameter type of the partition func tion used to partition the %S_MSG '%.*ls' is different from the parameter type o f the partition function used to partition index '%.*ls'. 4916 16 Could not enable or disable the constraint. See previous errors. 4917 16 Constraint '%.*ls' does not exist. 4918 16 ALTER TABLE SWITCH statement failed because the table '%.*ls' ha s fulltext index on it. 4919 16 PERSISTED attribute cannot be altered on column '%.*ls' because this column is not computed. 4920 16 ALTER TABLE failed because trigger '%.*ls' on table '%.*ls' does not exist. 4921 16 ALTER TABLE failed because trigger '%.*ls' does not belong to ta ble '%.*ls'. 4922 16 %ls %.*ls failed because one or more objects access this column. 4923 16 ALTER TABLE DROP COLUMN failed because '%.*ls' is the only data column in table '%.*ls'. A table must have at least one data column. 4924 16 %ls failed because column '%.*ls' does not exist in table '%.*ls '.

4925 16 ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%.*ls' with ROWGUIDCOL property. 4926 16 ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%.*ls' with ROWGUIDCOL property. 4927 16 Cannot alter column '%.*ls' to be data type %.*ls. 4928 16 Cannot alter column '%.*ls' because it is '%ls'. 4929 16 Cannot alter the %S_MSG '%.*ls' because it is being published fo r replication. 4933 16 Computed column '%.*ls' in table '%.*ls' cannot be persisted bec ause the column depends on a non-schemabound object. 4934 16 Computed column '%.*ls' in table '%.*ls' cannot be persisted bec ause the column does user or system data access. 4935 16 ALTER TABLE ADD COLUMN cannot specify a FILESTREAM filegroup tha t differs from the existing one. 4936 16 Computed column '%.*ls' in table '%.*ls' cannot be persisted bec ause the column is non-deterministic. 4938 16 ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.* ls' is in filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' is in filegroup ' %.*ls'. 4939 16 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegr oup '%.*ls' and partition %d of %S_MSG '%.*ls' is in filegroup '%.*ls'. 4940 16 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegr oup '%.*ls' and %S_MSG '%.*ls' is in filegroup '%.*ls'. 4941 16 ALTER TABLE SWITCH statement failed because the table '%.*ls' is marked for merge replication. 4942 16 ALTER TABLE SWITCH statement failed because column '%.*ls' at or dinal %d in table '%.*ls' has a different name than the column '%.*ls' at the sa me ordinal in table '%.*ls'. 4943 16 ALTER TABLE SWITCH statement failed because table '%.*ls' has %d columns and table '%.*ls' has %d columns. 4944 16 ALTER TABLE SWITCH statement failed because column '%.*ls' has d ata type %s in source table '%.*ls' which is different from its type %s in targe t table '%.*ls'. 4945 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'. 4946 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same persistent attribute in tables '%.*ls' and '%.*ls'. 4947 16 ALTER TABLE SWITCH statement failed. There is no identical index in source table '%.*ls' for the index '%.*ls' in target table '%.*ls' . 4948 16 ALTER TABLE SWITCH statement failed. The source table '%.*ls' is in database '%.*ls' while the target table '%.*ls' is in database '%.*ls'. 4949 16 ALTER TABLE SWITCH statement failed because the object '%.*ls' i s not a user defined table. 4950 16 ALTER TABLE SWITCH statement failed because partition number %d does not exist in table '%.*ls'. 4951 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same FILESTREAM storage attribute in tables '%.*ls' and '%.*ls'. 4952 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same ANSI trimming semantics in tables '%.*ls' and '%.*ls'. 4953 16 ALTER TABLE SWITCH statement failed. The columns set used to par tition the table '%.*ls' is different from the column set used to partition the table '%.*ls'. 4954 16 ALTER TABLE SWITCH statement failed. The table '%.*ls' has inlin e limit of %d for text in row data which is different from value %d used by tabl e '%.*ls'. 4955 16 ALTER TABLE SWITCH statement failed. The source table '%.*ls' an d target table '%.*ls' are same. 4957 16 '%ls' statement failed because the expression identifying partit ion number for the %S_MSG '%.*ls' is not of integer type. 4958 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does

not have the same ROWGUIDCOL property in tables '%.*ls' and '%.*ls'. 4959 16 ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.* ls' has TEXT filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' has TEXT fileg roup '%.*ls'. 4960 16 ALTER TABLE SWITCH statement failed. Check constraint '%.*ls' in source table '%.*ls' is NOCHECK constraint but the matching check constraint '% .*ls' in target table '%.*ls' is CHECK. 4961 16 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%. *ls' is nullable and it is not nullable in '%.*ls'. 4963 16 ALTER TABLE SWITCH statement failed. Partition %d is not valid f or table '%.*ls'. 4964 16 ALTER TABLE SWITCH statement failed. Table '%.*ls' has RULE cons traint '%.*ls'. SWITCH is not allowed on tables with RULE constraints. 4965 16 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%. *ls' is computed column but the same column in '%.*ls' is not computed. 4966 16 ALTER TABLE SWITCH statement failed. Computed column '%.*ls' def ined as '%.*ls' in table '%.*ls' is different from the same column in table '%.* ls' defined as '%.*ls'. 4967 16 ALTER TABLE SWITCH statement failed. SWITCH is not allowed becau se source table '%.*ls' contains primary key for constraint '%.*ls'. 4968 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has fo reign key for constraint '%.*ls' but source table '%.*ls' does not have correspo nding key. 4969 16 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 enable d. 4970 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a table level check constraint '%.*ls' but the source table '%.*ls' does not have a corresponding constraint. 4971 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a column level check constraint '%.*ls' but the source table '%.*ls' does not have a corresponding constraint. 4972 16 ALTER TABLE SWITCH statement failed. Check constraints or partit ion function of source table '%.*ls' allows values that are not allowed by check constraints or partition function on target table '%.*ls'. 4973 16 ALTER TABLE SWITCH statement failed. Range defined by partition %d in table '%.*ls' is not a subset of range defined by partition %d in table '% .*ls'. 4974 16 ALTER TABLE SWITCH statement failed. Foreign key constraint '%.* ls' is NOCHECK in source table '%.*ls' and the corresponding constraint '%.*ls' is CHECK in target table '%.*ls'. The source table constraint must be in CHECK. 4975 16 ALTER TABLE SWITCH statement failed. Check constraint '%.*ls' in source table '%.*ls' and check constraint '%.*ls' in target table '%.*ls' have different 'Not For Replication' settings. 4976 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a check constraint '%.*ls' on an XML column, but the source table '%.*ls' does not have an identical check constraint. 4977 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a check constraint '%.*ls' on a CLR type column, but the source table '%.*ls' does not have an identical check constraint. 4978 16 ALTER TABLE SWITCH statement failed. The partition %d in table '%.*ls' resides in a read-only filegroup '%.*ls'. 4979 16 ALTER TABLE SWITCH statement failed. The table '%.*ls' resides in a readonly filegroup '%.*ls'. 4980 16 ALTER TABLE SWITCH statement failed. The lobdata of partition % d in table '%.*ls' resides in a readonly filegroup '%.*ls'. 4981 16 ALTER TABLE SWITCH statement failed. The lobdata of table '%.*l s' resides in a readonly filegroup '%.*ls'. 4982 16 ALTER TABLE SWITCH statement failed. Check constraints of source

table '%.*ls' allow values that are not allowed by range defined by partition % d on target table '%.*ls'. 4983 16 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 i ndexes in the ALTER TABLE SWITCH statement. 4984 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' and so urce table '%.*ls' have different vardecimal storage format values. Use stored p rocedure sp_tableoption to alter the 'vardecimal storage format' option for the tables to make sure that the values are the same. 4985 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same nullability attribute in tables '%.*ls' and '%.*ls'. 4986 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same CLR type in tables '%.*ls' and '%.*ls'. 4987 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same XML Schema Collection in tables '%.*ls' and '%.*ls'. 4988 16 Cannot persist computed column '%.*ls'. Underlying object '%.*ls ' has a different owner than table '%.*ls'. 4989 16 Cannot drop the ROWGUIDCOL property for column '%.*ls' in table '%.*ls' because the column is not the designated ROWGUIDCOL for the table. 4990 16 Cannot alter column '%.*ls' in table '%.*ls' to add or remove th e FILESTREAM column attribute. 4991 16 Cannot alter NOT FOR REPLICATION attribute on column '%.*ls' in table '%.*ls' because this column is not an identity column. 4992 16 Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user t able that does not have any of large value types varchar(max), nvarchar(max), va rbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values computed column that are persisted. 4993 16 ALTER TABLE SWITCH statement failed. The table '%.*ls' has diffe rent setting for Large Value Types Out Of Row table option as compared to table '%.*ls'. 4994 16 Computed column '%.*ls' in table '%.*ls' cannot be persisted bec ause the column type, '%.*ls', is a non-byte-ordered CLR type. 4995 16 Vardecimal storage format cannot be enabled on table '%.*ls' bec ause database '%.*ls' is a system database. Vardecimal storage format is not ava ilable in system databases. 4996 16 Change tracking is already enabled for table '%.*ls'. 4997 16 Cannot enable change tracking on table '%.*ls'. Change tracking requires a primary key on the table. Create a primary key on the table before en abling change tracking. 4998 16 Change tracking is not enabled on table '%.*ls'. 4999 16 Cannot enable change tracking on table '%.*ls'. Change tracking does not support a primary key of type timestamp on a table. 5001 16 User must be in the master database. 5002 16 Database '%.*ls' does not exist. Verify the name in sys.database s and try the operation again. 5003 16 Database mirroring cannot be enabled while the database has offl ine files. 5004 16 To use ALTER DATABASE, the database must be in a writable state in which a checkpoint can be executed. 5005 16 Specified recovery time of %I64d seconds is less than zero or mo re than the maximum of %d seconds. 5006 16 Could not get exclusive use of %S_MSG '%.*ls' to perform the req uested operation. 5008 16 This ALTER DATABASE statement is not supported. Correct the synt ax and execute the statement again. 5009 16 One or more files listed in the statement could not be found or could not be initialized. 5010 16 Log file name cannot be generated from a raw device. The log fil e name and path must be specified. 5011 14 User does not have permission to alter database '%.*ls', the dat

abase does not exist, or the database is not in a state that allows access check s. 5012 16 The name of the primary filegroup cannot be changed. 5013 16 The master and model databases cannot have files added to them. ALTER DATABASE was aborted. 5014 16 The %S_MSG '%.*ls' does not exist in database '%.*ls'. 5015 16 ALTER DATABASE failed. The total size specified must be 1 MB or greater. 5016 16 Cannot change the name of the system database %.*ls. 5018 10 The file "%.*ls" has been modified in the system catalog. The ne w path will be used the next time the database is started. 5019 10 Cannot find entry in sys.master_files for file '%.*ls'. 5020 16 The primary data or log file cannot be removed from a database. 5021 10 The %S_MSG name '%.*ls' has been set. 5022 16 Log file '%ls' for this database is already active. 5023 16 The database must be suspect or in emergency mode to rebuild the log. 5024 16 No entry found for the primary log file in sysfiles1. Could not rebuild the log. 5025 16 The file '%ls' already exists. It should be renamed or deleted s o that a new log file can be created. 5027 16 System databases master, model, and tempdb cannot have their log s rebuilt. 5028 16 The system could not activate enough of the database to rebuild the log. 5029 10 Warning: The log for database '%.*ls' has been rebuilt. Transact ional 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 the y were. You should run DBCC CHECKDB to validate physical consistency. The databa se has been put in dbo-only mode. When you are ready to make the database availa ble for use, you will need to reset database options and delete any extra log fi les. 5030 16 The database could not be exclusively locked to perform the oper ation. 5031 16 Cannot remove the file '%.*ls' because it is the only file in th e DEFAULT filegroup. 5032 10 The file cannot be shrunk below page %d until the log is backed up because it contains bulk logged pages. 5033 16 The maximum of %ld files per database has been exceeded. 5034 16 The file %ls is currently being autogrown or modified by another process. Try the operation again later. 5035 16 Filegroup '%.*ls' already exists in this database. Specify a dif ferent name or remove the conflicting filegroup if it is empty. 5036 16 MODIFY FILE failed. Specify logical name. 5038 16 MODIFY FILE failed for file "%.*ls". At least one property per f ile must be specified. 5039 16 MODIFY FILE failed. Specified size is less than or equal to curr ent size. 5040 16 MODIFY FILE failed. Size is greater than MAXSIZE. 5041 16 MODIFY FILE failed. File '%.*ls' does not exist. 5042 16 The %S_MSG '%.*ls' cannot be removed because it is not empty. 5043 16 The %S_MSG '%.*ls' cannot be found in %ls. 5044 10 The %S_MSG '%.*ls' has been removed. 5045 16 The %S_MSG already has the '%ls' property set. 5046 10 The %S_MSG property '%ls' has been set. 5047 16 Cannot change the READONLY property of the PRIMARY filegroup. 5048 16 Cannot add, remove, or modify files in filegroup '%.*ls'. The fi legroup is read-only. 5050 16 Cannot change the properties of empty filegroup '%.*ls'. The fil egroup must contain at least one file.

5051 16 Cannot have a filegroup with the name 'DEFAULT'. 5052 16 %ls is not permitted while a database is in the %ls state. 5054 16 Could not cleanup worktable IAM chains to allow shrink or remove file operation. Please try again when tempdb is idle. 5055 16 Cannot add, remove, or modify file '%.*ls'. The file is read-onl y. 5056 16 Cannot add, remove, or modify a file in filegroup '%.*ls' becaus e the filegroup is not online. 5057 16 Cannot add, remove, or modify file '%.*ls' because it is offline . 5058 16 Option '%.*ls' cannot be set in database '%.*ls'. 5059 16 Database '%.*ls' is in transition. Try the ALTER DATABASE statem ent later. 5060 10 Nonqualified transactions are being rolled back. Estimated rollb ack completion: %d%%. 5061 16 ALTER DATABASE failed because a lock could not be placed on data base '%.*ls'. Try again later. 5062 16 The option "%.*ls" conflicts with another requested option. The options cannot both be requested at the same time. 5063 16 Database '%.*ls' is in warm standby. A warm-standby database is read-only. 5064 16 Changes to the state or options of database '%.*ls' cannot be ma de at this time. The database is in single-user mode, and a user is currently co nnected to it. 5065 16 The file "%ls" is currently being scanned or used by a backgroun d or user process. Try the operation again later. 5066 16 Database options single user and dbo use only cannot be set at t he same time. 5067 16 The database option TORN_PAGE_DETECTION is incompatible with the PAGE_CHECKSUM option. 5068 10 Failed to restart the current database. The current database is switched to master. 5069 16 ALTER DATABASE statement failed. 5070 16 Database state cannot be changed while other users are using the database '%.*ls' 5071 16 Rebuild log can only specify one file. 5072 16 ALTER DATABASE failed. The default collation of database '%.*ls' cannot be set to %.*ls. 5073 16 Cannot alter collation for database '%ls' because it is READONLY , OFFLINE, or marked SUSPECT. 5074 16 The %S_MSG '%.*ls' is dependent on %S_MSG '%.*ls'. 5075 16 The %S_MSG '%.*ls' is dependent on %S_MSG. The database collatio n cannot be changed if a schema-bound object depends on it. Remove the dependenc ies on the database collation and then retry the operation. 5076 10 Warning: Changing default collation for database '%.*ls', which is used in replication. All replication databases should have the same default c ollation. 5077 16 Cannot change the state of non-data files or files in the primar y filegroup. 5078 16 Cannot alter database options for "%ls" because it is READONLY, OFFLINE, or marked SUSPECT. 5079 10 Database "%.*ls" is %S_MSG for vardecimal storage format. 5080 16 Vardecimal storage format cannot be disabled for database "%.*ls " because the database is not under simple recovery model. Change the database r ecovery model to simple and then reissue the command. 5081 16 The value for change tracking option '%ls' is not valid. The val ue must be a positive number. 5082 16 Cannot change the versioning state on database "%.*ls" together with another database state. 5083 16 The termination option is not supported when making versioning s

tate changes. 5084 10 Setting database option %ls to %ls for database '%.*ls'. 5085 16 Alter database command failed because SQL Server was started wit h one or more undocumented trace flags that prevent enabling/disabling database for versioning. 5086 16 Cannot disable vardecimal storage format for database "%.*ls" be cause there are one or more tables that have vardecimal storage format enabled. Disable the vardecimal storage format on all tables before disabling the vardeci mal storage format for the database. 5087 16 The file content type mismatches with the content type of the fi legroup. 5088 16 Change tracking is already enabled for database '%.*ls'. 5089 16 Change tracking is disabled for database '%.*ls'. Change trackin g must be enabled on a database to modify change tracking settings. 5090 16 Database '%.*ls' is a system database. Change tracking settings cannot be modified for system databases. 5091 15 ALTER DATABASE change tracking option '%ls' was specified more t han once. Each option can be specified only once. 5092 15 The value for change tracking option '%ls' is not valid. The val ue must be between %d and %d minutes. 5093 16 The operation cannot be performed on a database snapshot. 5094 16 The operation cannot be performed on a database with database sn apshots or active DBCC replicas. 5095 16 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 in volving file "%ls" before attempting to transition to read-only. 5096 16 The recovery model cannot be changed to SIMPLE when any files ar e subject to a RESTORE PAGE operation. Complete the restore sequence involving file "%ls" before attempting to transition to SIMPLE. 5097 16 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 DA TABASE statement. 5098 16 The container can not be dropped because changes exist that requ ire a log backup. Take a log backup and then retry the ALTER DATABASE operation . 5102 22 Attempted to open a filegroup for the invalid ID %d in database "%.*ls". 5103 16 MAXSIZE cannot be less than SIZE for file '%ls'. 5104 16 File '%.*ls' already used. 5105 16 A file activation error occurred. The physical file name '%.*ls' may be incorrect. Diagnose and correct additional errors, and retry the operati on. 5108 10 Log file '%.*ls' does not match the primary file. It may be fro m a different database or the log may have been rebuilt previously. 5110 16 The file "%.*ls" is on a network path that is not supported for system database files. 5111 10 File activation failure. The physical file name "%.*ls" may be i ncorrect. 5112 10 FCB::SetSize dbid %d fileid %d oldSize %d newSize %d. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF t o turn off the trace flag. 5113 10 The log cannot be rebuilt because there were open transactions/u sers 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 w as manually deleted or lost due to a hardware or environment failure. 5114 16 Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. "%.*ls" is not an eligible file for a database snapshot. 5115 16 Only SQL Server database files can be specified for database sna pshots. '%.*ls' is not a SQL Server database file.

5118 16 The file "%ls" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed. 5119 16 Cannot make the file "%.*ls" a sparse file. Make sure the file s ystem supports sparse files. 5120 16 Unable to open the physical file "%.*ls". Operating system error %d: "%ls". 5121 16 The path specified by "%.*ls" is not in a valid directory. 5123 16 CREATE FILE encountered operating system error %ls while attempt ing to open or create the physical file '%.*ls'. 5124 16 The file header in '%ls' does not match the expected contents fo r file '%ls' of database '%ls'. The mismatch is possibly between the full-text c atalog files and the related database. Perform a restore if necessary. 5125 24 File '%ls' appears to have been truncated by the operating syste m. Expected size is %I64d KB but actual size is %I64d KB. 5127 16 All files must be specified for database snapshot creation. Miss ing the file "%ls". 5128 17 Write to sparse file '%ls' failed due to lack of disk space. 5129 10 The log cannot be rebuilt when the primary file is read-only. 5130 10 The log cannot be rebuilt when database mirroring is enabled. 5131 10 The log was not rebuilt because there is more than one log file. 5132 16 The path specified by '%.*ls' cannot be used for FILESTREAM file s because it is a raw device. 5133 16 Directory lookup for the file "%ls" failed with the operating sy stem error %ls. 5134 16 The path that is specified by '%.*ls' cannot be used for FILESTR EAM files because it is not on a supported file system. 5135 16 The path '%.*ls' cannot be used for FILESTREAM files. For inform ation about supported paths, see SQL Server Books Online. 5136 16 The path specified by '%.*ls' cannot be used for a FILESTREAM co ntainer since it is contained in another FILESTREAM container. 5144 10 Autogrow of file '%.*ls' in database '%.*ls' was cancelled by us er or timed out after %d milliseconds. Use ALTER DATABASE to set a smaller FILE GROWTH value for this file or to explicitly set a new file size. 5145 10 Autogrow of file '%.*ls' in database '%.*ls' took %d millisecond s. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file. 5149 16 MODIFY FILE encountered operating system error %ls while attempt ing to expand the physical file '%ls'. 5150 16 The size of a single log file must not be greater than 2 TB. 5159 24 Operating system error %.*ls on file "%.*ls" during %ls. 5161 16 An unexpected file id was encountered. File id %d was expected b ut %d was read from "%.*ls". Verify that files are mapped correctly in sys.maste r_files. ALTER DATABASE can be used to correct the mappings. 5169 16 FILEGROWTH cannot be greater than MAXSIZE for file '%.*ls'. 5170 16 Cannot create file '%ls' because it already exists. Change the f ile path or the file name, and retry the operation. 5171 16 %.*ls is not a primary database file. 5172 16 The header for file '%ls' is not a valid database file header. T he %ls property is incorrect. 5173 16 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 correc t files. If this is an existing database, the file may be corrupted and should be restored from a backup. 5174 16 Each file size must be greater than or equal to 512 KB. 5175 10 The file %.*ls has been expanded to allow recovery to succeed. A fter recovery completes, you can increase the size of the files in the database. Contact the system administrator for assistance. 5176 10 To allow recovery to succeed, the log file '%.*ls' has been expa nded beyond its maximum size. After recovery completes, you should either increa se the size of the log file in the database or schedule more frequent backups of the log (under the full or bulk-logged recovery model).

5177 16 An unexpected error occurred while checking the sector size for file '%.*ls'. Move the file to a local NTFS volume, where the sector size can be retrieved. Check the SQL Server error log for more information. 5178 16 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 v olume with a sector size that is the same as or smaller than the original sector size. 5179 16 Cannot use file '%.*ls', because it is on a volume with sector s ize %d. SQL Server supports a maximum sector size of 4096 bytes. Move the file t o a volume with a compatible sector size. 5180 22 Could not open File Control Block (FCB) for invalid file ID %d i n database '%.*ls'. Verify the file location. Execute DBCC CHECKDB. 5181 16 Could not restart database "%.*ls". Reverting to the previous st atus. 5182 10 New log file '%.*ls' was created. 5183 16 Cannot create the file "%ls". Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite an existing file. 5184 16 Cannot use file '%.*ls' for clustered server. Only formatted fil es on which the cluster resource of the server has a dependency can be used. Eit her the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it. 5185 16 Cannot find the matching log file for FILESTRAM file '%.*ls'. 5186 16 Encountered an error (NT status code 0x%x) while attempting to s tart the Transactional File System Resource Manager '%.*ls'. 5188 16 Encountered error (NT status code 0x%x) while attempting to perf orm redo for transactional file system resource manager '%.*ls'. 5189 16 Encountered error (NT status code 0x%x) while attempting to perf orm undo for transactional file system resource manager '%.*ls'. 5190 16 Encountered error (NT status code 0x%x) while attempting to chec kpoint transactional file system resource manager '%.*ls'. 5191 10 Local directory '%.*ls' is used for tempdb in a clustered server . This directory must exist on each cluster node and SQL Server service has read /write permission on it. 5194 16 The size for FILESTREAM log file '%.*ls' must be greater than or equal to 1 MB. 5195 16 The Cluster Service function call '%s' failed with error code '% s' while verifying the file path. Verify that your failover cluster is configure d properly. 5196 10 The file "%ls" has been uncompressed. 5197 16 Encountered an error (%ls) while attempting to uncompress the fi le "%ls". 5198 16 The path specified by "%.*ls" is a UNC path. UNC path is not sup ported in failover clustered environment. 5199 16 The path specified by "%.*ls" is a raw device. Raw device path i s not supported in failover clustered environment. 5201 10 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped be cause the file does not have enough free space to reclaim. 5202 10 DBCC SHRINKDATABASE for database ID %d is waiting for the snapsh ot transaction with timestamp %I64d and other snapshot transactions linked to ti mestamp %I64d or with timestamps older than %I64d to finish. 5203 10 DBCC SHRINKFILE for file ID %d is waiting for the snapshot trans action with timestamp %I64d and other snapshot transactions linked to timestamp %I64d or with timestamps older than %I64d to finish. 5204 16 Could not find allocation unit ID %I64d. Check sys.allocation_un its. 5205 10 %.*ls: Moving page %d:%d failed. 5206 10 %.*ls: Page %d:%d could not be moved because it could not be rea d. 5207 10 %.*ls: Page %d:%d could not be moved because it is a work table page.

5208 10 %.*ls: Page %d:%d could not be moved because it is a work file p age. 5209 10 %.*ls: Page %d:%d could not be moved because it is a dedicated a llocation page. 5210 10 %.*ls: Page %d:%d could not be moved because it is an invalid pa ge type. 5211 10 %.*ls: Page %d:%d could not be moved because it was deallocated during shrink. 5212 10 %.*ls: System table SYSFILES1 Page %d:%d could not be moved to o ther files because it only can reside in the primary file of the database. 5213 10 %.*ls: Page %d:%d could not be moved because its ownership was c hanged during shrink. 5214 10 %.*ls: Page %d:%d could not be moved because its page type was c hanged during shrink. 5215 10 %.*ls: Page %d:%d could not be moved because the partition to wh ich it belonged was dropped. 5216 10 %.*ls: Heap page %d:%d could not be moved because the table to w hich it belonged was dropped. 5217 10 %.*ls: Page %d:%d could not be moved because it is an empty nonleaf level index page. 5218 10 %.*ls: Heap page %d:%d could not be moved because the table name could not be found. 5219 10 %.*ls: Heap page %d:%d could not be moved. 5220 10 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved. 5221 10 %.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allo cation unit could not be moved. 5222 10 %.*ls: Page %d:%d from a dropped allocation unit could not be de allocated. 5223 10 %.*ls: Empty page %d:%d could not be deallocated. 5224 10 %.*ls: Empty large object page %d:%d could not be deallocated. 5225 10 %.*ls: Not all ghost records on the large object page %d:%d coul d be removed. If there are active queries on readable secondary replicas check t he current ghost cleanup boundary. 5226 10 %.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallo cated. 5227 10 %.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallo cated. 5228 16 Table error: object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID, row %d. DBCC detected incomplete cle anup from an online index build operation. (The anti-matter column value is %d.) 5229 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls) contains an anti-matter column, but is not a nonclu stered index. 5230 10 The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB. 5231 10 Object ID %ld (object '%.*ls'): A deadlock occurred while trying to lock this object for checking. This object has been skipped and will not be processed. 5232 10 DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TA BLOCK was specified. 5233 16 Table error: alloc unit ID %I64d, page %S_PGID. The test (%.*ls) failed. The values are %ld and %ld. 5234 10 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped be cause trying to adjust the space allocation for the file was failed. 5235 10 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds. 5236 10 Unable to process object '%ls' because it is a four-part name, w hich is not supported by any DBCC command. 5237 10 DBCC cross-rowset check failed for object '%.*ls' (object ID %d)

due to an internal query error. 5238 16 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 c ommand. 5239 16 Unable to process object ID %ld (object '%.*ls') because this DB CC command does not support objects of this type. 5240 10 File ID %d of database ID %d cannot be shrunk as it is either be ing shrunk by another process or is empty. 5241 10 File ID %d of database ID %d cannot be shrunk as the target shri nk size (%I64d KB) is greater than the actual file size (%I64d KB). 5242 16 An inconsistency was detected during an internal operation in da tabase '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support. 5243 16 An inconsistency was detected during an internal operation. Plea se contact technical support. 5244 16 Repair statement not processed. One or more files in the databa se are read-only and must be made writeable in order to run repair. 5245 16 Object ID %ld (object '%.*ls'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed. 5246 16 Repair operations cannot be performed on the MSSQLSYSTEMRESOURCE database. Consult Books Online topic "Resource Database" for more information. 5247 16 Repair: insert a secondary index row based on its base table ro w. 5248 10 Repair: Successfully %ls row in index "%ls" in database "%ls". 5249 10 %.*ls: Page %d:%d could not be moved because shrink could not lo ck the page. 5250 16 Database error: %ls page %S_PGID for database '%.*ls' (database ID %d) is invalid. This error cannot be repaired. You must restore from backup . 5251 10 %.*ls: Heap page %d:%d could not be moved because maintaining NC indexes associated with the heap failed. 5252 10 File ID %d of database ID %d cannot be shrunk to the expected si ze. The high concurrent workload is leading to too many deadlocks during the shr ink operation. Re-run the shrink operation when the workload is lower. 5253 10 The check statement was aborted. DBCC CHECKALLOC cannot be run o n TEMPDB. 5254 10 %.*ls: Heap page %d:%d could not be moved because the table to w hich it belonged was building the heap by another process. 5255 10 %.*ls: Page %d:%d could not be moved because it is a sort page. 5256 16 Table error: alloc unit ID %I64d, page %S_PGID contains an incor rect page ID in its page header. The PageId in the page header = %S_PGID. 5257 10 %.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation. 5258 10 %.*ls: Heap page %d:%d could not be moved because building compu ted column expression failed. 5259 10 %.*ls: Heap page %d:%d could not be moved because populating com puted column expression failed. 5260 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls): At least one record on page %S_PGID contains versioning informa tion, but the VERSION_INFO bit in the page header is not set. 5261 10 %.*ls: Page %d:%d could not be moved because it has not been for matted. 5262 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (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_PGI D, slot %d. 5263 10 Found incorrect count(s) for table '%.*ls', index '%.*ls', parti tion %ld: 5264 10 DATA pages %.*ls: From system table - %I64d pages; Actual - %I64d pages.

5265 10 USED pages %.*ls: From system table - %I64d pages; Actual - %I64d pages. 5266 10 RSVD pages %.*ls: From system table - %I64d pages; Actual - %I64d pages. 5267 10 ROWS count: From system table - %I64d rows; Actual - %I64 d rows. 5268 10 DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required. 5269 16 Check terminated. The transient database snapshot for database '%.*ls' (database ID %d) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details. 5270 10 %.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table. 5271 10 DBCC %ls could not output results for this command due to an int ernal failure. Review other errors for details. 5272 10 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively. 5273 10 %.*ls: Page %d:%d could not be moved because it belonged to an i ndex/heap that was/is in build online. 5274 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. %S_MSG is invalid for compressed pa ge; the following internal test failed: %.*ls. Values are %ld and %ld. 5275 10 Exhaustive search of '%.*ls' (database ID %d) for inconsistencie s completed. Processed %d of %d total searches. Elapsed time: %I64d millisecon ds. This is an informational message only. No user action is required. 5276 10 Exhaustive search of '%.*ls' (database ID %d) for inconsistencie s failed due to exception %d, state %d. This is an informational message only. No user action is required. 5277 10 Internal %lsdatabase snapshot has split point LSN = %08x:%08x:%0 4x and first LSN = %08x:%08x:%04x. 5278 10 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_P GID, database '%.*ls' (database ID %d), LSN = %S_LSN, type = %ld, isInSparseFile = %d. Please re-run this DBCC command." 5280 16 An unexpected protocol element was recevied during the execution of a consistency check command. Retry the operation. 5281 10 Estimated TEMPDB space (in KB) needed for %s on database %.*ls = %I64d. 5282 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. The header of the page is invalid: the IS_IN_SYSXACT flag bit is set. 5283 10 The Cross Rowset check on columnstore index object ID %d, index ID %d, partition ID %I64d. Drop and recreate the columnstore index. 5284 16 The replicated index '%.*ls' (object ID %d) and one or more of i ts clones do not contain the same rows. 5286 10 %.*ls: Page %d:%d could not be moved because it belongs to an ac tive online index build with LOBs. 5287 10 DBCC THROWERROR bypass exception. This is an informational messa ge only. No user action is required. 5301 16 Bulk load failed. User does not have ALTER TABLE permission on t able '%.*ls'. ALTER TABLE permission is required on the target table of a bulk l oad if the target table contains triggers or check constraints, but the 'FIRE_T RIGGERS' or 'CHECK_CONSTRAINTS' bulk hints are not specified. ALTER TABLE permis sion is also required if the 'KEEPIDENTITY' bulk hint is specified. 5302 16 Mutator '%.*ls' on '%.*ls' cannot be called on a null value. 5303 16 The result of applying mutator '%.*ls' on CLR type '%.*ls' canno t be a null value. 5304 16 Bulk copy failed. User does not have ALTER TABLE permission on t able '%.*ls'. ALTER TABLE permission is required on the target table of a bulk c

opy 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 cop y command. 5305 16 The rowdump and lockres columns are only valid on tables and ind exed views on which the NOEXPAND hint is specified. 5306 16 Cursor parameters are not allowed for functions. Variable '%.*ls ' is of type cursor. 5307 16 Invalid parameter specified for sp_cursoropen. 5308 16 Windowed functions and NEXT VALUE FOR functions do not support i nteger indices as ORDER BY clause expressions. 5309 16 Windowed functions and NEXT VALUE FOR functions do not support c onstants as ORDER BY clause expressions. 5310 16 Aggregates are not allowed in the VALUES list of an INSERT state ment. 5311 16 Invalid quote character '%lc'. A remote server or user command used an invalid quote character. 5312 16 The input to the function 'ntile' cannot be bound. 5313 16 Synonym '%.*ls' refers to an invalid object. 5315 16 The target of a MERGE statement cannot be a remote table, a remo te view, or a view over remote tables. 5316 16 The target '%.*ls' of the MERGE statement has an INSTEAD OF trig ger on some, but not all, of the actions specified in the MERGE statement. In a MERGE statement, if any action has an enabled INSTEAD OF trigger on the target, then all actions must have enabled INSTEAD OF triggers. 5317 16 The target of a MERGE statement cannot be a partitioned view. 5318 16 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 t hey have unique names in the MERGE statement. 5319 16 Aggregates are not allowed in a WHEN clause of a MERGE statement . 5321 16 The '%ls' function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5322 16 An aggregate function is not allowed in the %S_MSG clause when t he FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5323 15 Subqueries are not allowed in the %S_MSG clause when the FROM cl ause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5324 15 In a MERGE statement, a '%S_MSG' clause with a search condition cannot appear after a '%S_MSG' clause with no search condition. 5325 15 The order of the data in the data file does not conform to the O RDER hint specified for the BULK rowset '%.*ls'. The order of the data must matc h 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 da ta file to match the order specified by the ORDER hint. 5326 15 The data in the data file does not conform to the UNIQUE hint sp ecified 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 upda te the input data file to ensure that the data is unique. 5327 15 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(m ax), nvarchar(max) and varbinary(max) data types cannot be used in the ORDER hin t for a BULK rowset or CLR TVF. 5328 15 Cannot insert explicit value for the identity column '%.*ls' in the target table '%.*ls' of the INSERT statement when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5329 15 Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5330 16 Full-text predicates cannot appear in the OUTPUT clause. 5331 16 Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 5332 15 The order of the data in the stream does not conform to the ORDE

R hint specified for the CLR TVF '%.*ls'. The order of the data must match the o rder 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 th e order specified by the ORDER hint. 5333 16 The identifier '%.*ls' cannot be bound. Only source columns and columns in the clause scope are allowed in the 'WHEN NOT MATCHED' clause of a ME RGE statement. 5334 16 The identifier '%.*ls' cannot be bound. Only target columns and columns in the clause scope are allowed in the 'WHEN NOT MATCHED BY SOURCE' clau se of a MERGE statement. 5335 16 The data type %ls cannot be used as an operand to the UNION, INT ERSECT or EXCEPT operators because it is not comparable. 5501 16 The FILESTREAM filegroup was dropped before the table can be cre ated. 5502 16 The FILESTREAM container is inaccessible. 5503 10 Unable to find entry in sys.database_files for FILESTREAM file ' %.*ls'. 5504 15 'PRIMARY' can only be specified for FILESTREAM log filegroup in a 'CONTAINS' clause. 5505 16 A table that has FILESTREAM columns must have a nonnull unique c olumn with the ROWGUIDCOL property. 5506 15 FILESTREAM data or log file cannot be named 'DEFAULT'. 5507 15 DEFAULT cannot be specified for FILESTREAM log filegroup '%.*ls' . 5508 15 FILESTREAM can only be declared for VARBINARY columns. 5509 15 The properties SIZE or FILEGROWTH cannot be specified for the FI LESTREAM data file '%.*ls'. 5510 15 LOG ON cannot be used for non-FILESTREAM file group '%.*ls'. 5511 23 FILESTREAM's file system log record '%.*ls' under log folder '%. *ls' is corrupted. 5512 16 Error 0x%x (%ls) was encountered while directory '%.*ls' was bei ng truncated. 5513 16 The name that is specified for the associated log filegroup for FILESTREAM filegroup '%.*ls' is not valid. 5514 16 Transactional replication/Change Data Capture cannot proceed bec ause Transactional File System Resource Manager at '%.*ls' is not started. 5515 20 Cannot open the container directory '%.*ls' of the FILESTREAM fi le. The operating system has returned the Windows status code 0x%x. 5516 16 The FILESTREAM log filegroup '%.*ls' cannot be referred to by mo re than one FILESTREAM data filegroup. 5517 16 FILESTREAM container MAXSIZE must be greater than or equal to 51 2 KB. 5518 16 FILESTREAM path '%.*ls' is too long. 5519 16 A database must have primary FILESTREAM log filegroup and log fi le in order for it to contain other FILESTREAM filegroups. 5520 16 Upgrade of FILESTREAM container ID %d in the database ID %d fail ed because of container size recalculation error. Examine the previous errorlog entries for errors, and take the appropriate corrective actions. 5521 16 Error 0x%x (NT status code) was encountered when SQL Server atte mpts to retrieve '%.*ls' from the Transaction File System Resource Manager locat ed at '%.*ls'. 5522 16 FILESTREAM data file cannot be removed because its log file has not been backed up. 5523 16 FILESTREAM data file group cannot be added to refer to an empty FILESTREAM log file group. 5524 16 Default FILESTREAM data filegroup cannot be removed unless it's the last FILESTREAM data filegroup left. 5525 16 The READ_ONLY, READ_WRITE, and ONLINE/OFFLINE properties cannot be modified on a FILESTREAM log filegroup. 5526 16 The FILESTREAM log file '%.*ls' cannot be removed because it is

being referenced by a FILESTREAM data filegroup. 5527 16 The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist. 5528 16 A database can have at most one primary FILESTREAM log filegroup and log file. 5529 16 Failed to remove a FILESTREAM file. The database is a primary da tabase in an availability group. Wait for the FILESTREAM data files to be harden ed on every secondary availability replica. Then retry the drop file operation. 5531 16 Error 0x%x (NT status code) was encountered when SQL Server atte mpts to change the logging mode of Transaction File System Resource Manager loca ted at '%.*ls' from '%.*ls' to '%.*ls'. 5532 16 SQL Server cannot obtain the Kernel Transaction Manager's transa ction context to perform file system operation. 5533 23 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 backu p. 5534 23 SQL log record at LSN '%d:%d:%d' for database '%.*ls' is corrupt ed. Database cannot recover. 5535 23 FILESTREAM data container '%.*ls' is corrupted. Database cannot recover. 5536 23 FILESTREAM deleted folder '%.*ls' is corrupted. Database cannot recover. 5537 16 Function %ls is only valid on columns with the FILESTREAM attrib ute. 5538 16 Partial updates are not supported on columns that have a FILESTR EAM as a source. 5539 16 The ROWGUIDCOL column associated with the FILESTREAM being used is not visible where method %ls is called. 5540 16 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 c onstraint. 5541 16 An open mode must be used when a FILESTREAM column is opened as a file. 5542 16 The FILESTREAM filegroup '%.*ls' has no files assigned to it. FI LESTREAM data cannot be populated on this filegroup until a file is added. 5543 10 FILESTREAM: effective level = %d (remote access disabled), confi gured level = %d, file system access share name = '%.*ls'. 5544 10 FILESTREAM: effective level = %d (remote access enabled), config ured level = %d, file system access share name = '%.*ls'. 5550 16 Too many Filestream containers were specified for Filestream Fil egroup '%.*ls'. Specifying more than one Filestream Container per Filestream Fil egroup is not supported in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions. 5551 16 FILESTREAM file '%.*ls' cannot be added because its destination filegroup cannot have more than one file. Specifying more than one Filestream Co ntainer per Filestream Filegroup is not supported in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server ed itions. 5552 16 FILESTREAM file named with GUID '%.*ls' that belongs to FILESTRE AM data file ID 0x%x does not exist or cannot be opened. 5553 16 SQL Server internal error. FILESTREAM manager cannot continue wi th current command. 5554 16 The total number of versions for a single file has reached the m aximum limit set by the file system. 5555 16 The operation has failed because the FILESTREAM data cannot be r enamed. 5556 16 The database '%.*ls' does not exist or does not support FILESTRE AM. Supply a valid database name. To see available databases, use sys.databases. 5557 16 The FILESTREAM container '%.*ls' does not exist or cannot be pro

cessed. Supply a valid FILESTREAM container name. To see available containers, u se sys.databases_files. 5558 16 Database '%.*ls' should be in single-user mode. 5559 16 Could not open the database '%.*ls'. 5560 16 Access to the FILESTREAM tombstone table for the database '%.*ls ' cannot be performed at the moment because it conflicts with another activity, such as background GC operation, backup operation, DBCC CHECK* operation or on-g oing snapshot creation. 5561 16 FILESTREAM garbage collector operation was aborted on the databa se '%.*ls'. 5570 16 FILESTREAM Failed to find the garbage collection table. 5571 23 Internal FILESTREAM error: failed to access the garbage collecti on table. 5572 23 Internal FILESTREAM error: failed to perform a filesystem operat ion because of a potential corruption. 5573 10 Internal FILESTREAM error: failed to access the tombstones table with HRESULT: 0x%x. 5574 16 A database cannot be enabled for both FILESTREAM storage and Dat abase Mirroring. 5575 10 Operation '%ls' failed with HRESULT: %ls in file '%hs', line %d while executing sp_filestream_configure. 5578 16 A failure occurred while FILESTREAM configuration was being chan ged or applied. For more information, see the SQL Server error log. 5579 10 FILESTREAM: effective level = %d, configured level = %d, file sy stem access share name = '%.*ls'. 5580 16 FILESTREAM InstanceGuid is null. Registry settings might be corr upted. 5581 10 FILESTREAM feature has been disabled. Restart the instance of SQ L Server for the settings to fully take effect. If you have data in FILESTREAM c olumns, it will not be accessible after the SQL Server instance has been restart ed. 5582 10 Machine reboot is required before the FILESTREAM feature setting s can take effect. 5583 16 The specified value for the enable_level parameter of the sp_fil estream_configure stored procedure is not valid. The value must be 0, 1, 2, or 3 . 5584 16 Another session is executing the sp_filestream_configure stored procedure. Check the updated configuration settings and retry the operation if n ecessary. 5586 10 The FILESTREAM feature is already configured to the specified le vel. No change has been made. 5590 16 FILESTREAM operations are not supported on the platform. 5591 16 FILESTREAM feature is disabled. 5592 16 FILESTREAM feature doesn't have file system access enabled. 5593 16 FILESTREAM feature is not supported on WoW64. The feature is dis abled. 5594 16 The value specified for the computer_name_format parameter of th e .%ls() function is not valid. 5595 16 .PhysicalPathName is disabled. 5596 10 FILESTREAM feature configuration might be inconsistent. To rese t the configuration, use the sp_configure stored procedure. 5597 16 FILESTREAM feature could not be initialized. The Windows Adminis trator must enable FILESTREAM on the instance using Configuration Manager before enabling through sp_configure. 5598 10 FILESTREAM feature is not supported on user instances. 5600 16 The Cross Database Chaining option cannot be set to the specifie d value on the specified database. 5601 16 The service master key could not be force regenerated as request ed by the -F startup option. The error number is %ld. 5602 10 The service master key regeneration was successful.

5603 16 The password for SA could not be force regenerated as requested by the -K startup option. The error number is %ld. 5604 10 The password regeneration attempt for SA was successful. 5605 16 The password for SA account could not be force regenerated and/o r SA account cannot be disabled as requested by the -K startup option and the -T 1617 trace flag. 5701 10 Changed database context to '%.*ls'. 5702 10 SQL Server is terminating this process. 5703 10 Changed language setting to %.*ls. 5803 10 Unknown configuration (id = %d) encountered in sys.configuration s. 5804 16 Character set, sort order, or collation cannot be changed at the server level because at least one database is not writable. Make the database w ritable, and retry the operation. 5805 16 Too few locks specified. Minimum %d. 5807 16 Recovery intervals above %d minutes not recommended. Use the REC ONFIGURE WITH OVERRIDE statement to force this configuration. 5808 16 Ad hoc update to system catalogs is not supported. 5810 16 Valid values for the fill factor are 0 to 100. 5812 14 You do not have permission to run the RECONFIGURE statement. 5828 16 User connections are limited to %d. 5829 16 The specified user options value is invalid. 5831 16 Minimum server memory value (%d) must be less than or equal to t he maximum value (%d). 5832 16 The affinity mask specified does not match the CPU mask on this system. 5833 16 The affinity mask specified is greater than the number of CPUs s upported or licensed on this edition of SQL Server. 5834 16 The affinity specified conflicts with the IO affinity mask speci fied. Change the affinity setting to use different CPUs than those specified in the IO affinity mask. 5835 16 Failed to start CPUs with the mask 0x%lx on the system. 5836 16 Lightweight pooling is not supported on this platform or in this edition of SQL Server. 5837 16 The service broker listen port cannot be dynamic. Valid port va lues are 1024-32767. 5838 16 The service broker connection authentication value is invalid. 5839 16 The service broker message forward store size cannot be set to 0 . 5840 16 The service broker message forward mode is invalid. 5841 16 The default full-text language is not supported by the full-text search component. 5842 16 Too few worker threads are specified. The minimum is %d. 5844 16 User Instances are not supported in this edition of SQL Server. 5846 16 Common language runtime (CLR) execution is not supported under l ightweight pooling. Disable one of two options: "clr enabled" or "lightweight po oling". 5848 10 Physical CPU id %u has been hot added to node id %u as logical C PU id %u. This is an informational message only. No user action is required. 5849 10 Online CPU addition is not supported in the current edition of S QL Server. 5850 10 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 additi onal CPU resources, either add the new CPUs to the soft-NUMA configuration and r estart SQL Server, or remove the soft-NUMA configuration and restart SQL Server. 5851 10 The AccessCheckResult quota must be greater than or equal to the bucket count 5852 10 The AccessCheckResult bucket count must be less than %d. 5853 16 The affinity range is invalid. The lower bound %d must be less t

han the upper bound %d. 5854 16 A %S_MSG value was specified more than one time in the range lis t for an ALTER SERVER CONFIGURATION SET PROCESS AFFINITY statement. 5855 16 The affinity setting was not changed. This can be caused by low system resources. 5856 16 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. 5857 10 CPU 5858 10 NUMANODE 5859 16 The current affinity setting specifies the use of more than 64 p rocessors. Before you use sp_configure to change affinity settings, remove thes e processors by using ALTER SERVER CONFIGURATION. 5860 10 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. 5861 16 A %S_MSG with id %d does not exist on this system. Use sys.dm_o s_schedulers to locate valid %S_MSGs for this system. 5862 16 The number of max worker threads is set too low. On this compute r, the number must be more than %u. You should increase the number of max worker threads. 5863 16 Could not change the value of the '%.*ls' property. Operating sy stem error %ls 5864 16 IO affinity is not supported on this edition of sql server. 5901 16 One or more recovery units belonging to database '%.*ls' failed to generate a checkpoint. This is typically caused by lack of system resources s uch as disk or memory, or in some cases due to database corruption. Examine prev ious entries in the error log for more detailed information on this failure. 5904 17 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. 6001 10 SHUTDOWN is waiting for %d process(es) to complete. 6004 10 User does not have permission to perform this action. 6005 10 SHUTDOWN is in progress. 6006 10 Server shut down by %.*ls from login %.*ls. 6007 10 The SHUTDOWN statement cannot be executed within a transaction o r by a stored procedure. 6101 16 Session ID %d is not valid. 6102 14 User does not have permission to use the KILL statement. 6104 16 Cannot use KILL to kill your own process. 6106 16 Process ID %d is not an active process ID. 6107 14 Only user processes can be killed. 6108 16 KILL SPID WITH COMMIT/ROLLBACK is not supported by Microsoft SQL Server. Use KILL UOW WITH COMMIT/ROLLBACK to resolve in-doubt distributed trans actions involving Microsoft Distributed Transaction Coordinator (MS DTC). 6109 10 SPID %d: transaction rollback in progress. Estimated rollback co mpletion: %d%%. Estimated time remaining: %d seconds. 6110 16 The distributed transaction with UOW %s does not exist. 6111 16 Another user has decided a different outcome for the distributed transaction associated with UOW %s. 6112 16 Distributed transaction with UOW %s is in prepared state. Only M icrosoft Distributed Transaction Coordinator can resolve this transaction. KILL command failed. 6113 16 The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ROLLBACK syntax to kill the transaction instead . 6114 16 Distributed transaction with UOW %s is being used by another use r. KILL command failed. 6115 16 KILL command cannot be used inside user transactions. 6117 16 There is a connection associated with the distributed transactio

n with UOW %s. First, kill the connection using KILL SPID syntax. 6118 16 The distributed transaction associated with UOW %s is not in PRE PARED state. Use KILL UOW to kill the transaction instead. 6119 10 Distributed transaction with UOW %s is rolling back: estimated r ollback completion: %d%%, estimated time left %d seconds. 6120 16 Status report cannot be obtained. Rollback operation for Process ID %d is not in progress. 6121 16 Status report cannot be obtained. Rollback operation for UOW %s is not in progress. 6200 16 Method "%ls" of type "%ls" in assembly "%.*ls" is marked as a mu tator. Mutators cannot be used in the read-only portion of the query. 6201 16 Method "%ls" of type "%ls" in assembly "%.*ls" is not marked as a mutator. Only mutators can be used to update the value of a CLR type. 6202 16 Method "%ls" of type "%ls" in assembly "%.*ls" does not return a value. 6203 16 Method '%ls' of type '%ls' in assembly '%.*ls' cannot be marked as a mutator. A mutator method must be non-static, public, and returns void type . 6204 16 Trying to send a record with %d columns(s) in a result set with %d column(s). 6205 16 %s ASSEMBLY failed because assembly '%.*ls' was compiled with /U NSAFE option, but the assembly was not registered with the required PERMISSION_S ET = UNSAFE option. 6206 16 Request submitted with too many parameters. The maximum number is %ld. 6207 16 Error converting %.*ls to fixed length binary type. The result w ould be padded and cannot be converted back. 6208 16 %s failed because the parameter count for the FillRow method sho uld be one more than the SQL declaration for the table valued CLR function. 6209 16 Unsound ordering on CLR type "%.*ls": returning NULL on non-NULL inputs. 6210 16 CLR type '%.*ls' is not fully comparable. 6211 16 %s ASSEMBLY failed because type '%.*ls' in %.*ls assembly '%.*ls ' has a static field '%.*ls'. Attributes of static fields in %.*ls assemblies mu st be marked readonly in Visual C#, ReadOnly in Visual Basic, or initonly in Vi sual C++ and intermediate language. 6212 16 %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %. *ls assembly '%.*ls' is storing to a static field. Storing to a static field is not allowed in %.*ls assemblies. 6213 16 %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in %.* ls assembly "%.*ls" has a synchronized attribute. Explicit synchronization is no t allowed in %.*ls assemblies. 6214 16 %s ASSEMBLY failed because assembly "%.*ls" has an unmanaged ent ry point. 6215 16 %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %. *ls assembly '%.*ls' has invalid attribute 0x%x. 6216 16 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls " has a finalizer. Finalizers are not allowed in %.*ls assemblies. 6217 16 ALTER ASSEMBLY ADD FILE failed because the file, "%.*ls", being added is empty. 6218 16 %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' failed verification. Check if the referenced assemblies are up-to-date and trus ted (for external_access or unsafe) to execute in the database. CLR Verifier err or messages if any will follow this message%.*ls 6219 16 %s ASSEMBLY failed because assembly source parameter %d has an u nmanaged entry point. 6220 16 SELECT INTO failed because CLR type "%.*ls" does not exist in th e target database. 6221 16 The cursor operation generated more than one row of different co lumn metadata.

6222 16 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is not valid for native serialization. 6223 16 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not marked wit h "LayoutKind.Sequential". Native serialization requires the type to be marked w ith "LayoutKind.Sequential". 6224 16 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is marked with "System.NonSerializedAttribute". N ative serialization types cannot have fields marked with "System.NonSerializedAt tribute". 6225 16 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 typ e. Native serialization types can only have fields of blittable types. If you wi sh to have a field of any other type, consider using different kind of serializa tion format, such as User Defined Serialization. 6226 16 Type "%.*ls.%.*ls" is marked for user-defined serialization, but does not implement the "%.*ls.%.*ls" interface. 6227 16 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not blittable, or type "%.*ls.%.*ls" has a recursive definition. 6228 16 Type "%.*ls.%.*ls" is marked for native serialization, but it co ntains non-blittable fields. 6229 16 Type "%.*ls.%.*ls" is marked for native serialization. It is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential". 6230 16 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" has field marshallers. Native serialization types cannot have field marshallers. 6231 16 Type "%.*ls.%.*ls" is marked for native serialization, but one o f its base types "%.*ls.%.*ls" is not valid for native serialization. 6232 16 Type "%.*ls.%.*ls" is marked for native serialization, but base type "%.*ls.%.*ls" is not marked with "LayoutKind.Sequential". Native serializat ion requires the type to be marked with "LayoutKind.Sequential". 6233 16 In proc data access is not allowed in an impersonated state. 6234 16 Data truncation error. Length (%d) exceeds maximum length (%d) f or type '%.*ls'. 6235 16 Data serialization error. Length (%d) is less than fixed length (%d) for type '%.*ls'. 6236 16 %s ASSEMBLY failed because filename '%.*ls' is too long. 6237 16 %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in ass embly "%.*ls" has an invalid custom attribute "%.*ls". 6238 16 %s ASSEMBLY failed because field "%.*ls" in type "%.*ls" in asse mbly "%.*ls" has an invalid custom attribute "%.*ls". 6239 16 %s ASSEMBLY failed because type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls". 6240 16 ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the indexed view '%s '. 6241 16 Trying to send a record with type or name of column %d differing from the type or name of the corresponding column of the result set. 6242 16 CREATE ASSEMBLY failed because the user "%.*ls" specified in the authorization clause does not exist. 6243 16 '%.*ls.%.*ls' is marked for native serialization, and has the Ma xByteSize property specified in the '%.*ls' attribute. Native serialization obje cts can not specify MaxByteSize property, it is calculated by SQL Server. 6244 16 The size (%d) for "%.*ls.%.*ls" is not in the valid range. Size must be -1 or a number between 1 and 8000. 6245 16 Invalid serialization format (%d) for type "%.*ls.%.*ls". 6246 16 Assembly "%.*ls" already exists in database "%.*ls". 6247 16 Cannot create type because '%.*ls.%.*ls' cannot have fixed lengt

h if it has MaxByteSize set to -1. 6248 16 %s failed because the type '%s' contains a method '%s' specified by SqlUserDefinedType.ValidateMethodName that does not conform to the required specification because it has an invalid signature. 6249 16 The associated file "%.*ls" already exists for assembly "%.*ls". 6250 11 Assembly "%.*ls" does not have an associated file "%.*ls". 6251 16 ALTER ASSEMBLY failed because the assembly file parameter %d is not a valid expression. 6252 16 ALTER ASSEMBLY failed because a file name was not specified for the inline assembly file parameter %d. 6253 10 Common language runtime (CLR) functionality initialized using CL R version %ls from %ls. 6254 10 Common language runtime (CLR) functionality initialized. 6255 16 %s failed because type "%s" does not conform to the %s specifica tion: missing custom attribute "%.*ls". 6256 16 SqlPipe request submitted with too many columns. The maximum nu mber is %d. 6257 16 CREATE ASSEMBLY for assembly '%.*ls' failed because the assembly is built for an unsupported version of the Common Language Runtime. 6258 16 Function signature of "FillRow" method (as designated by SqlFunc tionAttribute.FillRowMethodName) does not match SQL declaration for table valued CLR function'%.*ls' due to column %d. 6259 16 Assembly '%.*ls' could not be loaded because it failed verificat ion. %.*ls 6260 16 An error occurred while getting new row from user defined Table Valued Function : %.*ls. 6261 16 The CLR type referenced by column "%.*ls" of table variable "%.* ls" has been dropped during the execution of the batch. Run the batch again. 6262 16 Assembly was not found in current database or version did not ma tch. 6263 16 Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. 6264 16 Data access failed because the .NET Framework routine is not mar ked with "DataAccessKind.Read" or "SystemDataAccessKind.Read". 6265 16 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls " has a pinvokeimpl method. P/Invoke is not allowed in %.*ls assemblies. 6266 10 Warning: Assembly "%.*ls" was built using version %.*ls of the . NET Framework. SQL Server currently uses version %s. 6267 16 Assembly "%.*ls" does not exist, or the user does not have permi ssion to reference it. 6269 16 ALTER ASSEMBLY failed because the user-defined aggregate "%s" do es not exist or is not correctly defined in the updated assembly. 6270 16 ALTER ASSEMBLY failed because the required method "%s" in type " %s" was not found with the same signature in the updated assembly. 6271 16 ALTER ASSEMBLY failed because the required field "%s" in type "% s" was not found with the same signature in the updated assembly. 6272 16 ALTER ASSEMBLY failed because required property '%s' in type '%s ' was not found with the same signature in the updated assembly. 6273 16 ALTER ASSEMBLY failed because required type '%s' does not exist or is not correctly defined in the updated assembly. 6274 16 ALTER ASSEMBLY failed because the serialization format of type ' %s' would change in the updated assembly. Persisted types are not allowed to cha nge serialization formats. 6275 16 ALTER ASSEMBLY failed because the IsByteOrdered attribute of typ e '%s' would change in the updated assembly. 6276 16 ALTER ASSEMBLY failed because serialization data of type '%s' wo uld change in the updated assembly. Persisted types are not allowed to change se rialization data. 6277 16 ALTER ASSEMBLY failed because the MaxLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change

MaxLen attribute. 6278 16 ALTER ASSEMBLY failed because the IsFixedLen attribute of type ' %s' would change in the updated assembly. Persisted types are not allowed to cha nge IsFixedLen attribute. 6279 16 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 b y the schema-bound function or view '%s'. 6280 16 ALTER ASSEMBLY failed because table, view or constraint '%s' dep ends on this assembly. Use WITH UNCHECKED DATA to skip checking for persisted da ta. 6281 16 ALTER ASSEMBLY failed because only members of the sysadmin role can use WITH UNCHECKED DATA. 6282 16 ALTER ASSEMBLY failed because the referenced assemblies would ch ange. The referenced assembly list must remain the same. 6283 16 ALTER ASSEMBLY failed because only the assembly revision version number is allowed to change. 6284 16 ALTER ASSEMBLY failed because it is referenced by object '%.*ls' . Assemblies that are referenced by SQL objects cannot be made invisible. 6285 16 %s ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name "%.*ls" . 6286 16 '%s' ASSEMBLY failed because a different version of assembly '%s ', referenced by assembly '%s', is already in the database. 6287 16 ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the persisted comput ed column '%s' of table '%s'. 6288 16 ALTER ASSEMBLY has marked data as unchecked in one or more objec ts in database "%.*ls". Refer to column "has_unchecked_assembly_data" from syste m views "sys.tables" and "sys.views" to locate all such objects. 6289 16 Failed to allocate memory for common language runtime (CLR) func tionality. 6290 10 AppDomain %i (%.*ls) unloaded. 6291 16 AppDomain %i (%.*ls) failed to unload with error code 0x%x. 6292 16 The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction. 6293 16 %.*ls.%.*ls.%.*ls: SqlFacetAttribute is invalid on a non-public member. 6294 16 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute cannot be used in this context. 6295 16 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute has an in valid value. 6296 16 %.*ls.%.*ls.%.*ls : SqlFacetAttribute cannot be applied to a pro perty getter or a property setter. It should be applied to the property itself. 6297 16 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute property IsFixedLength cannot be set to true when MaxSize is set to -1. 6298 16 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute properties Precision an d Scale have to be used together. 6299 10 AppDomain %i (%.*ls) created. 6302 16 The argument of CREATE or ALTER XML SCHEMA COLLECTION statement must be a string expression. 6303 16 XML parsing: Document parsing required too much memory 6304 16 XML parsing: An unexpected error has occurred in the XML parser. 6305 16 XQuery data manipulation expression required in XML data type me thod. 6306 16 Invalid XQuery expression passed to XML data type method. 6307 16 XML well-formedness check: Attribute cannot appear outside of el ement declaration. Rewrite your XQuery so it returns well-formed XML. 6308 16 XML well-formedness check: Duplicate attribute '%.*ls'. Rewrite your XQuery so it returns well-formed XML. 6309 16 XML well-formedness check: the data for node '%.*ls' contains a

character (0x%04X) which is not allowed in XML. 6310 16 Altering existing schema components is not allowed. There was a n attempt to modify an existing XML Schema component, component namespace: '%.*l s' component name: '%.*ls' component kind:%.*ls 6311 16 An internal XMLDB schema processor error occurred. Contact Techn ical Support for assistance. 6312 16 Could not find schema components with target namespace '%.*ls' i n collection '%.*ls'. 6314 16 Collection specified does not exist in metadata : '%.*ls' 6315 16 XQuery: Cannot update with value '%.*ls' as the canonical form o f type '{%.*ls}%.*ls' violates the required pattern. It is recommended that you not use pattern facets on non-string types. 6316 16 Specified component '%s' can not be dropped because it is used b y component:'%s' 6317 16 XQuery: Cannot update with value '%.*ls' because it failed valid ation against type '{%.*ls}%.*ls' 6318 16 XQuery: String conversion failed during UPDATE validation 6320 16 XQuery: Only nillable elements or text nodes can be updated with empty sequence 6321 16 xml:space attribute must have a value of 'preserve' or 'default' . '%.*ls' is not valid. 6322 16 XML Parser ran out of memory. This could be caused by too many a ttributes or namespace declarations. 6323 16 The xml schema collection for variable '%.*ls' has been altered while the batch was being executed. Remove all XML schema collection DDL operati ons it is dependent on from the batch, and re-run the batch. 6324 16 DROP XML INDEX does not support any options. 6325 16 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 expressi on evaluated to an empty sequence but it is not '()'. 6326 16 XML well-formedness check: XML namespace declaration cannot appe ar outside of element declaration. Rewrite your XQuery so it returns well-formed XML. 6327 16 The specified xml schema collection ID is not valid: %d 6328 16 Specified collection '%.*ls' cannot be dropped because it is use d by %S_MSG '%ls'. 6329 16 Unsupported usage of a QName typed value in node '%.*ls' 6330 16 Column '%.*ls' on table '%.*ls' is not of type XML, which is req uired to create an XML index on it. 6331 16 Primary XML Index '%.*ls' already exists on column '%.*ls' on ta ble '%.*ls', and multiple Primary XML Indexes per column are not allowed. 6332 16 Table '%.*ls' needs to have a clustered primary key with less th an %d columns in it in order to create a primary XML index on it. 6333 16 Could not find%ls XML index named '%.*ls' on table '%.*ls' 6334 16 Could not create the XML or spatial index on object '%.*ls' beca use that object is not a table. Create the index on the base table column. 6335 16 XML datatype instance has too many levels of nested nodes. Maxim um allowed depth is %d levels. 6336 16 Maximum size of primary index of table '%.*ls' is %d bytes. CREA TE XML INDEX requires that such size should be limited to %d bytes 6337 16 '%.*ls' is not a valid XML Index name because it starts with '%c ' character. XML Index name should not start with '#' or '@' 6338 10 XML DTD has been stripped from one or more XML fragments. Exter nal subsets, if any, have been ignored. 6339 16 Specified collection '%.*ls' cannot be modified because it is SQ L Server built-in XML Schema Collection. 6340 16 Xml schema collection '%.*ls' referenced by table variable '%.*l s' has been dropped or altered during the execution of the batch. Please re-run the batch. 6341 16 Xml schema collection referenced by column '%.*ls' of table vari

able '%.*ls' has been dropped or altered during the execution of the batch. Plea se re-run the batch. 6342 16 Cannot create primary xml or spatial index '%.*ls' on table '%.* ls', column '%.*ls', because the column is computed. 6343 16 Cannot create secondary xml index '%.*ls' without a USING XML IN DEX clause. 6344 16 The primary xml index '%.*ls' does not exist on table '%.*ls' co lumn '%.*ls'. 6345 16 The sparse column set '%.*ls' in the table '%.*ls' cannot be ind exed by an XML index. 6346 16 Cannot convert a primary XML index to a secondary XML index usin g the DROP_EXISTING option. '%.*ls' is a primary XML index. 6347 16 Specified collection '%.*ls' cannot be altered because it does n ot exist or you do not have permission. 6348 16 Specified collection '%.*ls' cannot be created because it alread y exists or you do not have permission. 6350 16 The definition for xml schema collection '%.*ls' has changed. 6351 16 The xml schema collection for return parameter of module '%.*ls' has been altered while the batch was being executed. Please re-run the batch. 6352 16 Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as a string or untyped X ML. 6353 16 Serialization of built-in schemata is not supported. 6354 16 Target string size is too small to represent the XML instance 6355 16 Conversion of one or more characters from XML to target collatio n impossible 6356 16 Failed to load DLL. Make sure xmlrw.dll exists in the SQL Serve r installation. 6357 16 Internal error: cannot locate CreateInfoSetReaderEx in xmlrw.dll . You may have an incorrect version of xmlrw.dll. 6358 16 %d is not a valid style number when converting to XML. 6359 16 Parsing XML with internal subset DTDs not allowed. Use CONVERT w ith style option 2 to enable limited internal subset DTD support. 6360 16 %d is not a valid style number when converting from XML. 6361 16 Invalid null parameter specified. XML Schema Collections can onl y be created from a non-null value. 6362 16 Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. 6363 16 ALTER SCHEMA COLLECTION failed. It cannot be performed on a sche ma collection that allows laxly validated content and is schema bound. Remove th e schema binding before trying to alter the collection. 6364 16 ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in t able '%.*ls' did not succeed due to the following reason: '%.*ls'. Either the sc hema or the specified data should be altered so that validation does not find an y mismatches. 6365 16 An XML operation resulted an XML data type exceeding 2GB in size . Operation aborted. 6366 16 Invalid type for element '%s'. SQL Server does not permit the bu ilt-in XML Schema types 'ID' and 'IDREF' or types derived from them to be used a s the type of an element. %S_MSG %s 6401 16 Cannot roll back %.*ls. No transaction or savepoint of that name was found. 6500 16 %ls failed because method '%ls' of class '%ls' in assembly '%ls' returns %ls, but CLR Triggers must return void. 6501 16 %s ASSEMBLY failed because it could not open the physical file ' %.*ls': %ls. 6502 16 %s ASSEMBLY failed because it could not read from the physical f ile '%.*ls': %ls. 6503 16 Assembly '%.*ls' was not found in the SQL catalog. 6504 16 The value returned from %.*ls.%.*ls is not allowed to be NULL.

6505 16 Could not find Type '%s' in assembly '%s'. 6506 16 Could not find method '%s' for type '%s' in assembly '%s' 6507 16 Failed to open malformed assembly '%ls' with HRESULT 0x%x. 6508 16 Could not find field '%s' for type '%s' in assembly '%s'. 6509 16 An error occurred while gathering metadata from assembly '%ls' w ith HRESULT 0x%x. 6510 16 This functionality requires .NET Framework 4. Please install .NE T Framework 4 to use this functionality. 6511 16 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You may fix the problem and try again later. 6512 16 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You need to restart SQL Server to use CLR integration features. 6513 16 Failed to initialize the Common Language Runtime (CLR) %ls due t o memory pressure. This is probably due to memory pressure in the MemToLeave reg ion of memory. For more information, see the CLR integration documentation in SQ L Server Books Online. 6514 16 Cannot use '%s' column in the result table of a streaming user-d efined function (column '%.*ls'). 6515 16 Schema collection database '%.*ls' does not exist or you do not have permission. 6516 16 There is no collection '%.*ls' in metadata '%.*ls'. 6517 16 Failed to create AppDomain "%.*ls". %.*ls 6518 16 Could not open system assembly ''%.*ls'': %ls. 6519 16 Type '%.*ls' is not yet supported for CLR operations. 6520 16 A .NET Framework error occurred during statement execution. 6521 16 A .NET Framework error occurred during statement execution: %.*l s. 6522 16 A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls. 6523 16 Method, property or field '%ls' of class '%ls' in assembly '%.*l s' is static. 6524 16 Cannot use computed column in the result table of a streaming us er-defined function (column '%.*ls'). 6525 16 Cannot use '%s' constraint in the result table of a streaming us er-defined function. 6526 16 Cannot use '%s' constraint in the result table of a streaming us er-defined function (column '%.*ls'). 6527 10 .NET Framework runtime has been stopped. 6528 16 Assembly '%.*ls' was not found in the SQL catalog of database '% .*ls'. 6529 16 ALTER ASSEMBLY failed because the identity of referenced assembl y '%.*ls' has changed. Make sure the version, name, and public key have not chan ged. 6530 16 Cannot perform alter on '%.*ls' because it is an incompatible ob ject type. 6531 16 %ls failed because the function '%ls' of class '%ls' of assembly '%.*ls' takes one or more parameters but CLR Triggers do not accept parameters. 6532 16 .NET Framework execution was aborted by escalation policy becaus e of out of memory. %.*ls 6533 16 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critic al resource. %.*ls 6534 16 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Application failed to release a managed lock. % .*ls 6535 16 .NET Framework execution was aborted. Another query caused the A ppDomain %.*ls to be unloaded. %.*ls 6536 16 A fatal error occurred in the .NET Framework common language run time. SQL Server is shutting down. If the error recurs after the server is resta rted, contact Customer Support Services.

6537 16 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 do wn. 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 param eter instead. 6538 16 .NET Framework execution was aborted because of stack overflow. %.*ls 6539 16 Invalid serialization format (Format.Unknown) for type '%.*ls.%. *ls'. 6540 16 The assembly name '%.*ls' being registered has an illegal name t hat duplicates the name of a system assembly. 6541 16 ALTER ASSEMBLY failed because assembly '%.*ls' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files. 6542 16 Can not create object because %ls is a generic type. 6543 16 .NET Framework execution was aborted. The UDP/UDF/CLR type did n ot end thread affinity. 6544 16 %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is malformed or not a pure .NET assembly. %.*ls 6545 16 Enabling of execution statistics SET options is not allowed from within CLR procedure or function. 6546 16 Could not impersonate the execution context during the execution of '%.*ls'. 6547 16 An error occurred while getting method, property or field inform ation for "%ls" of class "%ls" in assembly "%.*ls". 6548 16 CREATE ASSEMBLY failed because the assembly references assembly '%.*ls', which is owned by another user. 6549 16 A .NET Framework error occurred during execution of user defined routine or aggregate '%.*ls': %ls. User transaction, if any, will be rolled bac k. 6550 16 %s failed because parameter counts do not match. 6551 16 %s for "%.*ls" failed because T-SQL and CLR types for return val ue do not match. 6552 16 %s for "%.*ls" failed because T-SQL and CLR types for parameter "%.*ls" do not match. 6553 16 %s failed because of an invalid .NET Framework calling conventio n. Use the default .NET Framework calling convention. 6554 16 SQL assembly name '%.*ls', and .NET Framework assembly name '%.* ls' do not match. Assembly names must match. 6555 16 Assembly '%.*ls' already exists for owner '%.*ls' in database '% .*ls'. 6556 16 %s failed because it could not find type '%s' in assembly '%s'. 6557 16 %s failed because type '%s' does not conform to %s specification due to field '%s'. 6558 16 %s failed because type '%s' does not conform to %s specification due to method '%s'. 6559 20 Could not find type ID %d in database %.*ls. This is due to a sc hema inconsistency. 6560 16 Assembly "%.*ls" is a system assembly. This operation is permit ted only with user assemblies. 6561 16 Could not find file '%s' in directory '%s%s'. 6562 16 Version mismatch between files '%ls' (%d.%d.%d) and '%ls' (%d.%d .%d). 6563 16 Method, property or field '%ls' in class '%ls' in assembly '%.*l s' has invalid return type. 6564 16 The method '%ls' in class '%ls' in assembly '%.*ls' has some inv alid parameter declaration for parameter number %d. 6565 16 %s ASSEMBLY failed because the assembly source parameter %d is n ot a valid assembly. 6566 16 %s ASSEMBLY failed because the assembly source parameter %d is n ot a valid expression.

6567 16 %s failed because a CLR Procedure may only be defined on CLR met hods that return either SqlInt32, System.Int32, System.Nullable<System.Int32>, v oid. 6568 16 A .NET Framework error occurred while getting information from c lass "%.*ls" in assembly "%.*ls": %ls. 6569 16 '%.*ls' failed because parameter %d is not allowed to be null. 6570 16 Method '%ls' of class '%ls' in assembly '%.*ls' is generic. Gene ric methods are not supported. 6571 16 Class '%ls' in assembly '%.*ls' is generic. Generic types are no t supported. 6572 16 More than one method, property or field was found with name '%ls ' in class '%ls' in assembly '%.*ls'. Overloaded methods, properties or fields a re not supported. 6573 16 Method, property or field '%ls' of class '%ls' in assembly '%.*l s' is not static. 6574 16 Method, property or field '%ls' of class '%ls' in assembly '%.*l s' is not public. 6575 16 Assembly names should be less than %d characters. Assembly name '%.*ls' is too long. 6576 16 Type '%ls' in assembly '%ls' is not public. 6577 16 CREATE TYPE failed because type '%s' does not conform to CLR typ e specification due to interface '%s'. 6578 16 Invalid attempt to continue operation after a severe error. 6579 16 Alter assembly from '%ls' to '%ls' is not a compatible upgrade. 6580 16 Declarations do not match for parameter %d. .NET Framework refer ence and T-SQL OUTPUT parameter declarations must match. 6581 16 Could not find assembly '%.*ls' in directory '%.*ls'. 6582 16 Assembly '%.*s' is not visible for creating SQL objects. Use ALT ER ASSEMBLY to change the assembly visibility. 6583 16 Assembly '%.*s' cannot be used for creating SQL objects because it is a system assembly. 6584 16 Property or field '%ls' for type '%ls' in assembly '%ls' is not static 6585 16 Could not impersonate the client during assembly file operation. 6586 16 Assembly '%.*ls' could not be installed because existing policy would keep it from being used. 6587 16 Assembly reference '%ls' was redirected by external policy to '% ls' 6588 16 Assembly file operations are not allowed for Windows NT users ac tivated by SETUSER. 6589 16 DROP ASSEMBLY failed because the specified assemblies are refere nced by assembly '%ls'. 6590 16 DROP ASSEMBLY failed because '%ls' is referenced by object '%ls' . 6591 16 %s for "%.*ls" failed because first parameter of "%.*ls" method must be of type System.Object. 6592 16 Could not find property or field '%ls' for type '%ls' in assembl y '%ls'. 6593 16 Property or field '%ls' for type '%ls' in assembly '%ls' is stat ic. 6594 16 Could not read from property '%ls' for type '%ls' in assembly '% ls' because it does not have a get accessor. 6595 16 Could not assign to property '%ls' for type '%ls' in assembly '% ls' because it is read only. 6596 16 %s ASSEMBLY failed because assembly '%ls' is a system assembly. Consider creating a user assembly to wrap desired functionality. 6597 16 CREATE %s failed. 6598 16 DROP ASSEMBLY failed because '%ls' is referenced by CLR type '%l s'. 6599 16 Found an empty native serialization class '%.*ls'. Empty native

serialization classes are not allowed. 6600 16 XML error: %.*ls 6601 10 The XML parse error 0x%x occurred on line number %d, near the XM L text "%.*ls". 6602 16 The error description is '%.*ls'. 6603 16 XML parsing error: %.*ls 6605 16 %.*ls: Failed to obtain an IPersistStream interface on the XML t ext. 6607 16 %.*ls: The value supplied for parameter number %d is invalid. 6608 16 Failed to instantiate class "%ls". Verify that Msxmlsql.dll exis ts in the SQL Server installation. 6609 16 Invalid data type for the column "%ls". Allowed data types are C HAR/VARCHAR, NCHAR/NVARCHAR, TEXT/NTEXT, and XML. 6610 17 Failed to load Msxmlsql.dll. 6611 16 The XML data type is damaged. 6613 16 Specified value '%ls' already exists. 6621 16 XML encoding or decoding error occurred with object name '%.*ls' . 6622 16 Invalid data type for column "%ls". The data type cannot be text , ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml. 6623 16 Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar. 6624 16 XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents. 6625 16 Could not convert the value for OPENXML column '%ls' to sql_vari ant data type. The value is too long. Change the data type of this column to tex t, ntext or image. 6626 16 Unexpected end of data stream. 6627 16 The size of the data chunk that was requested from the stream ex ceeds the allowed limit. 6628 16 %.*ls can only process untyped XML. Cast the input value to XML or to a string type. 6629 16 The result of the column expression for column "%ls" is not comp atible with the requested type "XML". The result must be an element, text node, comment node, processing instruction, or document node. 6630 16 Element-centric mapping must be used with OPENXML when one of th e columns is of type XML. 6631 16 The requested OpenXML document is currently in use by another th read, and cannot be used. 6632 16 Invalid data type for the column "%ls". CLR types cannot be used in an OpenXML WITH clause. 6633 16 The version of MSXMLSQL.DLL that was found is older than the min imum required version. Found version "%d.%d.%d". Require version "%d.%d.%d". 6634 16 OpenXML cannot be used as the target of a DML or OUTPUT INTO ope ration. 6700 16 XQuery: The ' %ls' operation is not supported. 6701 16 The version of the XML index that you are trying to use is not s upported anymore. Please drop and recreate the XML index. 6716 16 XML Node ID is invalid. Re-build the database if the problem pe rsists. 6717 16 XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy. 6718 16 XQuery: Invalid ordpath string: "%s" 6739 16 XQuery: SQL type '%s' is not supported in XQuery. 6743 16 XQuery: The maximum allowed depth in XML instances is %d levels. One of the paths in the query tries to access nodes at a lower level. 6744 16 XQuery: One of the paths specified in the query is too deep. The maximum allowed depth is %d levels. 6745 16 XQuery: Internal compiler error. 6800 16 FOR XML AUTO requires at least one table for generating XML tags

. Use FOR XML RAW or add a FROM clause with a table name. 6801 16 FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column. 6802 16 FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integ er. 6803 16 FOR XML EXPLICIT requires the first column to hold positive inte gers that represent XML tag IDs. 6804 16 FOR XML EXPLICIT requires the second column to hold NULL or nonn egative integers that represent XML parent tag IDs. 6805 16 FOR XML EXPLICIT stack overflow occurred. Circular parent tag re lationships are not allowed. 6806 16 Undeclared tag ID %d is used in a FOR XML EXPLICIT query. 6807 16 Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query. 6808 16 XML tag ID %d could not be added. The server memory resources ma y be low. 6809 16 Unnamed tables cannot be used as XML identifiers as well as unna med columns cannot be used for attribute names. Name unnamed columns/tables usin g AS in the SELECT statement. 6810 16 Column name '%.*ls' is repeated. The same attribute cannot be ge nerated more than once on the same XML tag. 6812 16 XML tag ID %d that was originally declared as '%.*ls' is being r edeclared as '%.*ls'. 6813 16 FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDRE F, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'. 6814 16 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'. 6815 16 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'. 6816 16 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'. 6817 16 FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'. 6819 16 The FOR XML clause is not allowed in a %ls statement. 6820 16 FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'. 6821 16 GROUP BY and aggregate functions are currently not supported wit h FOR XML AUTO. 6824 16 In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid. 6825 16 ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML. 6826 16 Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after the element to which they belong. 6827 16 FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted. 6828 16 XMLTEXT column '%.*ls' must be of a string data type or of type XML. 6829 16 FOR XML EXPLICIT and RAW modes currently do not support addressi ng binary data as URLs in column '%.*ls'. Remove the column, or use the BINARY B ASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COL UMN' syntax. 6830 16 FOR XML AUTO could not find the table owning the following colum n '%.*ls' to create a URL address for it. Remove the column, or use the BINARY B ASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COL UMN' syntax. 6831 16 FOR XML AUTO requires primary keys to create references for '%.* ls'. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form if no primary keys exist.

6832 16 FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary. 6833 16 Parent tag ID %d is not among the open tags. FOR XML EXPLICIT re quires parent tags to be opened first. Check the ordering of the result set. 6834 16 XMLTEXT field '%.*ls' contains an invalid XML document. Check th e root tag and its attributes. 6835 16 FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE on ly once. 6836 16 FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS f ield '%.*ls' to precede element-centric IDREFS/NMTOKEN fields. 6838 16 Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either speci fy ELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive. 6839 16 FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' t hat has IDREFS or NMTOKENS fields. 6840 16 Neither XMLDATA nor XMLSCHEMA supports namespace elements or att ributes such as '%.*ls'. Run the SELECT FOR XML statement without it or remove t he namespace prefix declaration. 6841 16 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 dat a using FOR XML, convert it to binary, varbinary or image data type and use the BINARY BASE64 directive. 6842 16 Could not serialize the data for node '%.*ls' because it contain s a character (0x%04X) which is not allowed in XML. To retrieve this data conver t it to binary, varbinary or image data type 6843 16 FOR XML EXPLICIT: XML data types and CLR types cannot be process ed as CDATA in column name '%.*ls'. Consider converting XML to a string type. Co nsider converting CLR types to XML and then to a string type. 6844 16 Two (or more) elements named '%.*ls' are of different types and not direct siblings in the same level. 6845 16 Two (or more) elements named '%.*ls' are optional in the same le vel. Consider making them direct siblings or map NULL to xsi:nil 6846 16 XML name space prefix '%.*ls' declaration is missing for FOR XML %.*ls name '%.*ls'. 6847 16 The column '%.*ls' is of type sql_variant, which is not supporte d in attribute-centric FOR XML, with XML Schema. 6848 16 XMLDATA does not support the mapping of the type of column '%.*l s' to an XDR type. Please use XMLSCHEMA instead for AUTO and RAW mode. 6849 16 FOR XML PATH error in column '%.*ls' - '//' and leading and trai ling '/' are not allowed in simple path expressions. 6850 16 %.*ls name '%.*ls' contains an invalid XML identifier as require d by FOR XML; '%c'(0x%04X) is the first character at fault. 6851 16 Column '%.*ls' has invalid data type for attribute-centric XML s erialization in FOR XML PATH. 6852 16 Attribute-centric column '%.*ls' must not come after a non-attri bute-centric sibling in XML hierarchy in FOR XML PATH. 6853 16 Column '%.*ls': the last step in the path can't be applied to XM L data type or CLR type in FOR XML PATH. 6854 16 Invalid column alias '%.*ls' for formatting column as XML proces sing instruction in FOR XML PATH - it must be in 'processing-instruction(target) ' format. 6855 16 Inline schema is not supported with FOR XML PATH. 6856 16 FOR XML row XML tag name contains an invalid XML identifier; '%c '(0x%04X) is the first character at fault. 6857 16 FOR XML root XML tag name contains an invalid XML identifier; '% c'(0x%04X) is the first character at fault. 6858 16 XML schema URI contains character '%c'(0x%04X) which is not allo wed in XML. 6859 16 Row tag name is only allowed with RAW or PATH mode of FOR XML. 6860 16 FOR XML directive XMLDATA is not allowed with ROOT directive or

row tag name specified. 6861 16 Empty root tag name can't be specified with FOR XML. 6862 16 Empty FOR XML target inline schema URI is not allowed. 6863 16 Row tag omission (empty row tag name) is not compatible with XML SCHEMA FOR XML directive. 6864 16 Row tag omission (empty row tag name) cannot be used with attrib ute-centric FOR XML serialization. 6865 16 FOR XML does not support CLR types - cast CLR types explicitly i nto one of the supported types in FOR XML queries. 6866 16 Use of a system reserved XML schema URI is not allowed. 6867 16 'xmlns' is invalid in XML tag name in FOR XML PATH, or when WITH XMLNAMESPACES is used with FOR XML. 6868 16 The following FOR XML features are not supported with WITH XMLNA MESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives. 6869 16 Attempt to redefine namespace prefix '%.*ls' 6870 16 Prefix '%.*ls' used in WITH XMLNAMESPACES clause contains an inv alid XML identifier. '%c'(0x%04X) is the first character at fault. 6871 16 Prefix '%.*ls' used in WITH XMLNAMESPACES is reserved and cannot be used as a user-defined prefix. 6872 16 XML namespace prefix 'xml' can only be associated with the URI h ttp://www.w3.org/XML/1998/namespace. This URI cannot be used with other prefixes . 6873 16 Redefinition of 'xsi' XML namespace prefix is not supported with ELEMENTS XSINIL option of FOR XML. 6874 16 Empty URI is not allowed in WITH XMLNAMESPACES clause. 6875 16 URI '%.*ls' used in WITH XMLNAMESPACES is invalid. '%c'(0x%04X) is the first character at fault. 6876 16 URI used in WITH XMLNAMESPACES is too long. The maximum length i s %d characters. 6877 16 Empty namespace prefix is not allowed in WITH XMLNAMESPACES clau se. 6878 16 FORXML XMLSCHEMA cannot be used with a typed XML column whose sc hema collection is empty. 6879 16 'xml' is an invalid XML processing instruction target. Possible attempt to construct XML declaration using XML processing instruction constructo r. XML declaration construction with FOR XML is not supported. 6901 16 XML Validation: XML instance must be a document. 6902 16 XML Validation: Invalid definition for type '%ls'. SQL Server do es not currently support the use of the pattern or enumeration facet on lists of type QName. 6903 16 XML Validation: Invalid definition for type '%ls'. SQL Server do es not currently support inclusion of ID, QName, or list of QName among the memb er types of a union type. 6904 16 XML Validation: Found duplicate attribute '%s'. %S_MSG %s 6905 16 XML Validation: Attribute '%s' is not permitted in this context. %S_MSG %s 6906 16 XML Validation: Required attribute '%s' is missing. %S_MSG %s 6907 16 Namespace URI too long: '%.*ls'. 6908 10 XML Validation: Invalid content. Expected element(s): %s. %S_MSG %s 6909 16 XML Validation: Text node is not allowed at this location, the t ype was defined with element only content or with simple content. %S_MSG %s 6910 16 XML Validation: Invalid definition for type '%ls'. SQL Server do es not currently support restriction of union types. 6911 16 XML Validation: Found duplicate element '%s' in all content mode l. %S_MSG %s 6912 16 XML Validation: Element '%s' found in text only content model. % S_MSG %s 6913 16 XML Validation: Declaration not found for element '%s'. %S_MSG % s

6914 16 XML Validation: Type definition for type '%s' was not found, typ e definition is required before use in a type cast. %S_MSG %s 6915 16 Element or attribute name too long: '%.*ls'. 6916 16 XML Validation: The content model of type or model group '%s' is ambiguous and thus violates the unique particle attribution constraint. Consult SQL Server Books Online for more information. 6917 16 XML Validation: Element '%ls' may not have xsi:nil="true" becaus e it was not defined as nillable or because it has a fixed value constraint. %S_ MSG %ls 6918 16 XML Validation: Element '%s' must not have character or element children, because xsi:nil was set to true. %S_MSG %s 6919 16 XML Validation: The type of element '%s' is abstract. Instantiat ion requires the use of xsi:type to specify a non-abstract type. %S_MSG %s 6920 16 Invalid definition for type '%ls'. Cannot specify use="prohibite d" for attribute '%ls' because there is no corresponding attribute in the base t ype. 6921 16 XML Validation: Element or attribute '%s' was defined as fixed, the element value has to be equal to value of 'fixed' attribute specified in def inition. %S_MSG %s 6922 16 XML Validation: Not able to resolve namespace for prefix:'%.*ls' 6923 16 XML Validation: Unexpected element(s): %s. %S_MSG %s 6924 16 XML Validation: Text '%.*ls' found in attribute-only content mod el. %S_MSG %s 6925 16 Invalid definition for element '%ls'. SQL Server does not curren tly permit additions to existing substitution groups via ALTER XML SCHEMA COLLEC TION. 6926 16 XML Validation: Invalid simple type value: '%s'. %S_MSG %s 6927 16 XML Validation: Invalid simple type value: '%ls'. 6928 16 XML Validation: XML instances of the content model of type or mo del group '%ls' can be validated in multiple ways and are not supported. 6929 16 XML Validation: Invalid QName for xsi:type attribute '%.*ls'. 6930 16 XML Validation: ID constraint check failed. Found attribute name d '%.*ls' with duplicate ID value '%.*ls'. %S_MSG %s 6931 16 XML Validation: IDREF constraint check failed. Found attribute n amed '%.*ls' with reference to ID value '%.*ls', which does not exist 6932 16 Invalid definition for element or attribute '%s'. Value constrai nts on components of type ID are not allowed. 6933 16 XML Validation: Invalid simple type operation, inserting into si mple type is not permitted. %S_MSG %s 6934 16 XML Validation: Element '%s' requires substitution, because it w as defined as abstract. %S_MSG %s 6935 16 XML Validation: ID or IDREF attribute exceeded the allowed maxim um length. %S_MSG %s 6936 16 XML Validation: Invalid cast for element '%s' from type '%s' to type '%s'. %S_MSG %s 6937 16 XML Validation: The canonical form of the value '%ls' is not val id according to the specified type. This can result from the use of pattern face ts on non-string types or range restrictions or enumerations on floating-point t ypes. %S_MSG %ls 6938 16 XML Validation: The canonical form of the value '%ls' is not val id according to the specified type. This can result from the use of pattern face ts on non-string types or range restrictions or enumerations on floating-point t ypes. 6939 16 XML Validation: The element '%ls' is mixed content with a fixed value and therefore not allowed to have element content. %S_MSG %ls 6940 16 Invalid component named '%s' found in global scope. Only element s, attributes, types and groups can be defined in global context 6941 16 Invalid type definition for type '%s', types with complex conten t can only be derived from base types which have complex content 6942 16 Invalid type definition for type '%s', types with simple content

can only be derived from base types which have simple content 6943 16 Invalid type definition for type '%s', the derivation was illega l because 'final' attribute was specified on the base type 6944 16 Invalid type definition for type '%s', '%s' facet is not restric ting the value space 6945 16 Invalid facet value for facet '%s' in type definition '%s' 6946 16 Invalid type definition for type '%s', 'minLength' can not be gr eater than 'maxLength' 6947 16 XML Validation: Multiple ID attributes found on a single element . %S_MSG %s 6948 16 Invalid type definition for type '%s', 'minLength' can not be gr eater than 'Length' 6949 16 Invalid type definition for type '%s', 'Length' can not be great er than 'maxLength' 6950 16 Invalid type definition for type '%s', 'fractionDigits' can not be greater than 'totalDigits' 6951 16 Invalid type definition for type '%s', 'minInclusive' must be le ss than or equal to 'maxInclusive' and less than 'maxExclusive' 6952 16 Invalid type definition for type '%s', 'minExclusive' must be le ss than or equal to 'maxExclusive' and less than 'maxInclusive' 6953 16 Invalid type definition for type '%s', recursive type definition s are not allowed 6954 16 Invalid group definition for group '%s', recursive group definit ions are not allowed 6955 16 Invalid attribute definition for attribute '%s', attributes type has to be simple type 6956 16 Invalid type definition for type '%s', fixed facet '%s' can not be redefined to a different value. 6957 16 Invalid element definition, element '%s' is not valid derivation of element '%s' 6958 16 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 = maxOcc urs = 1, its child elements must have maxOccurs = 1 6959 16 Invalid definition, top level group definitions can not have mod el groups as siblings 6960 16 Component '%s' is outside of allowed range. Maximum for 'fractio nDigits' is 10 and maximum number of digits for non fractional part is 28 6961 16 The system limit on the number of XML types has been reached. R edesign your database to use fewer XML types. 6962 16 'default' and 'fixed' values are not allowed on element of this type: '%s' 6963 16 'Default' or 'Fixed' value is longer than allowed, maximum lengt h allowed is 4000 characters : '%s' 6964 16 Facet value is longer than allowed, maximum length allowed is 40 00 characters : '%s' 6965 10 XML Validation: Invalid content. Expected element(s): %s. Found: element '%s' instead. %S_MSG %s. 6966 10 Warning: Type '%s' is restricted by a facet '%s' that may impede full round-tripping of instances of this type 6967 16 Invalid type definition for type '%s'. The base and derived type s must have the same value for 'mixed' unless deriving by restriction, in which case 'false' is always permitted for the derived type. 6968 16 Invalid type definition for type '%s'. Complex types cannot rest rict simple types 6969 16 ID/IDREF validation consumed too much memory. Try reducing the n umber of ID and IDREF attributes. Rearranging the file so that elements with IDR EF attributes appear after the elements which they reference may also be helpful . 6970 16 Invalid type definition for type '%s'. No type may have more tha n one attribute of any type derived from ID.

6971 16 Invalid type definition for type '%s'. Type contains attribute ' %s' which is not allowed in base type. 6972 16 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 t ype. 6973 16 Invalid redefinition of attribute '%s' in type '%s'. Must be req uired in the derived type if it is required in the base type. 6974 16 Invalid redefinition of attribute '%s' in type '%s'. Must be pro hibited in the derived type if it is prohibited in the base type. 6975 16 Invalid redefinition of attribute '%s' in type '%s'. Must be fix ed to the same value as in the derived type. 6976 16 Invalid redefinition of attribute '%s' in type '%s'. Derivation by extension may not redefine attributes. 6977 16 Invalid member type '%s' in union type '%s'. Unions may not have complex member types. 6978 16 Invalid item type for list type '%s'. The item type of a list ma y not itself be a list, and types derived from ID may not be used as item types in this release. 6979 16 Invalid restriction for type '%s'. The element in the restricted type must have the same name as and a more restrictive type than the correspond ing element in the base type. 6980 16 Invalid restriction for type '%s'. The particle in the restricte d type may not have an occurrence range more permissive than that of the corresp onding particle in the base type. 6981 16 Invalid restriction for type '%s'. The element in the restricted type may not be nillable if the corresponding element in the base type is not. 6982 16 Invalid restriction for type '%s'. The element in the restricted type must be fixed to the same value as the corresponding element in the derive d type. 6983 16 Invalid restriction for type '%s'. The element in the restricted type may not have a 'block' value more permissive than the corresponding elemen t in the base type. 6984 16 Invalid restriction for type '%s'. The element in the restricted type must be in one of the namespaces allowed by the base type's wildcard. 6985 16 Invalid restriction for type '%s'. The Wildcard in the restricte d type must be a valid subset of the corresponding wildcard in the base type, an d the processContents may not be more permissive. 6986 16 Invalid restriction for type '%s'. The effective total range of the model group in the restricted type must be a valid restriction of the occurr ence range of the wildcard in the base type. 6987 16 Invalid restriction for type '%s'. An 'all' particle may be rest ricted only by 'all', 'element', or 'sequence'. 6988 16 Invalid restriction for type '%s'. A 'choice' particle may be re stricted only by 'element', 'choice', or 'sequence'. 6989 16 Invalid restriction for type '%s'. A 'sequence' particle may be restricted only by 'element' or 'sequence'. 6990 16 Invalid restriction for type '%s'. Invalid model group restricti on. 6991 16 Invalid restriction for type '%s'. If the base type has empty co ntent, then the derived type must as well, and if the derived type has empty con tent, then the base type must be emptiable. 6992 16 The content model of type '%s' contains two elements with the sa me name '%s' and different types, nullability, or value constraints. 6993 16 Value constraint on use of attribute '%s' must be consistent wit h value constraint on its declaration. 6994 16 Invalid restriction for type '%s'. The attribute wildcard in the restricted type must be a valid subset of the corresponding attribute wildcard in the base type, and the processContents may not be more permissive. 6995 16 Invalid definition for type '%s'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived from them to be use

d as the type of an element or as the basis for derivation by extension. 6996 16 Invalid type definition for type '%s'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and 'maxExclusive' facets. 6997 16 Invalid definition for element '%s'. An element which has a fixe d value may not also be nillable. 6998 16 Invalid type definition: Type or content model '%s' is too compl icated. It may be necessary to reduce the number of enumerations or the size of the content model. 6999 16 Invalid definition for element or attribute '%s'. Value constrai nts on components of type QName are not supported in this release. 7000 16 OPENXML document handle parameter must be of data type int. 7001 16 OPENXML flags parameter must be of data type int. 7002 16 OPENXML XPath must be of a string data type, such as nvarchar. 7003 16 Only one OPENXML column can be of type %ls. 7004 16 OPENXML does not support retrieving schema from remote tables, a s in '%.*ls'. 7005 16 OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument. 7006 16 OPENXML encountered a problem identifying the metaproperty names pace prefix. Consider removing the namespace parameter from the corresponding sp _xml_preparedocument statement. 7007 16 OPENXML encountered unknown metaproperty '%.*ls'. 7008 16 The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag. 7009 16 OPENXML allows only one metaproperty namespace prefix declaratio n in sp_xml_preparedocument. 7101 16 You need an active user transaction in order to use text pointer s for a table with the option "text in row" set to ON. 7102 20 Internal Error: Text manager cannot continue with current statem ent. Run DBCC CHECKTABLE. 7104 16 Offset or size of data type is not valid. Data type must be of t ype int or smallint. 7105 22 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 uncommitte d data on a data page. Run DBCC CHECKTABLE. 7106 16 Internal error: An attempt was made to update a LOB data type us ing a read-only text pointer. 7107 16 You can have only 1,024 in-row text pointers in one transaction 7108 22 Database ID %d, page %S_PGID, slot %d, link number %d is invalid . Run DBCC CHECKTABLE. 7116 16 Offset %d is not in the range of available LOB data. 7117 16 Error reading large object (LOB) data from the tabular data stre am (TDS). 7118 16 Only complete replacement is supported when assigning a large ob ject (LOB) to itself. 7119 16 Attempting to grow LOB beyond maximum allowed size of %I64d byte s. 7122 16 Invalid text, ntext, or image pointer type. Must be binary(16). 7123 16 Invalid text, ntext, or image pointer value %hs. 7124 16 The offset and length specified in the READTEXT statement is gre ater than the actual data length of %ld. 7125 16 The text, ntext, or image pointer value conflicts with the colum n name specified. 7133 16 NULL textptr (text, ntext, or image pointer) passed to %ls funct ion. 7134 16 LOB Locator is not supported as text pointer when using UPDATETE XT/WRITETEXT to update/write a text column. 7135 16 Deletion length %ld is not in the range of available text, ntext , or image data. 7137 16 %s is not allowed because the column is being processed by a con

current snapshot or is being replicated to a non-SQL Server Subscriber or Publis hed in a publication allowing Data Transformation Services (DTS) or tracked by C hange Data Capture. 7138 16 The WRITETEXT statement is not allowed because the column is bei ng replicated with Data Transformation Services (DTS) or tracked by Change Data Capture. 7139 16 Length of LOB data (%I64d) to be replicated exceeds configured m aximum %ld. Use the stored procedure sp_configure to increase the configured max imum value for max text repl size option, which defaults to 65536. A configured value of -1 indicates no limit, other that the limit imposed by the data type. 7140 16 Cannot create additional orphans with the stored procedure sp_cr eateorphan. Free up some of the orphan handles that you have created by insertin g or deleting them. 7141 16 Must create orphaned text inside a user transaction. 7143 16 Invalid locator de-referenced. 7144 16 A text/ntext/image column referenced by a persisted or indexed c omputed column cannot be updated 7151 16 Insufficient buffer space to perform write operation. 7201 17 Could not execute procedure on remote server '%.*ls' because SQL Server is not configured for remote access. Ask your system administrator to re configure SQL Server to allow remote access. 7202 11 Could not find server '%.*ls' in sys.servers. Verify that the co rrect server name was specified. If necessary, execute the stored procedure sp_a ddlinkedserver to add the server to sys.servers. 7212 16 Could not execute procedure '%.*ls' on remote server '%.*ls'. 7213 20 The attempt by the provider to pass remote stored procedure para meters to remote server '%.*ls' failed. Verify that the number of parameters, t he order, and the values passed are correct. 7214 16 Remote procedure time out of %d seconds exceeded. Remote procedu re '%.*ls' is canceled. 7215 16 Could not execute statement on remote server '%.*ls'. 7221 16 Could not relay results of procedure '%.*ls' from remote server '%.*ls'. 7301 16 Cannot obtain the required interface ("%ls") from OLE DB provide r "%ls" for linked server "%ls". 7302 16 Cannot create an instance of OLE DB provider "%ls" for linked se rver "%ls". 7303 16 Cannot initialize the data source object of OLE DB provider "%ls " for linked server "%ls". 7304 16 Cannot connect using OLE DB provider "%ls" to linked server "%ls ". Verify the connection parameters or login credentials associated with this li nked server. 7305 16 Cannot create a statement object using OLE DB provider "%ls" for linked server "%ls". 7306 16 Cannot open the table "%ls" from OLE DB provider "%ls" for linke d server "%ls". %ls 7307 16 Cannot obtain the data source of a session from OLE DB provider "%ls" for linked server "%ls". This action must be supported by the provider. 7308 16 OLE DB provider '%ls' cannot be used for distributed queries bec ause the provider is configured to run in single-threaded apartment mode. 7310 16 Cannot obtain the set of schema rowsets supported by OLE DB prov ider "%ls" for linked server "%ls". The provider supports the interface, but ret urns a failure code when it is used. 7311 16 Cannot obtain the schema rowset "%ls" for OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a fail ure code when it is used. 7312 16 Invalid use of schema or catalog for OLE DB provider "%ls" for l inked server "%ls". A four-part name was supplied, but the provider does not exp ose the necessary interfaces to use a catalog or schema. 7313 16 An invalid schema or catalog was specified for the provider "%ls

" for linked server "%ls". 7314 16 The OLE DB provider "%ls" for linked server "%ls" does not conta in the table "%ls". The table either does not exist or the current user does not have permissions on that table. 7315 16 The OLE DB provider "%ls" for linked server "%ls" contains multi ple tables that match the name "%ls". 7316 16 Cannot use qualified table names (schema or catalog) with the OL E DB provider "%ls" for linked server "%ls" because it does not implement requir ed functionality. 7317 16 The OLE DB provider "%ls" for linked server "%ls" returned an in valid schema definition. 7318 16 The OLE DB provider "%ls" for linked server "%ls" returned an in valid column definition for table "%ls". 7319 16 The OLE DB provider "%ls" for linked server "%ls" returned a "%l s" index "%ls" with the incorrect bookmark ordinal %d. 7320 16 Cannot execute the query "%ls" against OLE DB provider "%ls" for linked server "%ls". %ls 7321 16 An error occurred while preparing the query "%ls" for execution against OLE DB provider "%ls" for linked server "%ls". %ls 7322 16 A failure occurred while giving parameter information to OLE DB provider "%ls" for linked server "%ls". 7323 16 An error occurred while submitting the query text to OLE DB prov ider "%ls" for linked server "%ls". 7324 16 A failure occurred while setting parameter properties with OLE D B provider "%ls" for linked server "%ls". 7325 16 Objects exposing columns with CLR types are not allowed in distr ibuted queries. Please use a pass-through query to access remote object '%ls'. 7326 16 An error occurred while retrieving the query text from OLE DB pr ovider "%ls" for linked server "%ls". 7327 16 A failure occurred while retrieving parameter information to OLE DB provider "%ls" for linked server "%ls". 7330 16 Cannot fetch a row from OLE DB provider "%ls" for linked server "%ls". 7331 16 Rows from OLE DB provider "%ls" for linked server "%ls" cannot b e released. 7332 16 Cannot rescan the result set from OLE DB provider "%ls" for link ed server "%ls". %ls 7333 16 Cannot fetch a row using a bookmark from OLE DB provider "%ls" f or linked server "%ls". 7339 16 OLE DB provider '%ls' for linked server '%ls' returned invalid d ata for column '%ls.%ls'. 7340 16 Cannot create a column accessor for OLE DB provider "%ls" for li nked server "%ls". 7341 16 Cannot get the current row value of column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". %ls 7342 16 An unexpected NULL value was returned for column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". This column cannot be NULL. 7343 16 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls". %ls 7344 16 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls" because of column "%ls". %ls 7345 16 The OLE DB provider "%ls" for linked server "%ls" could not dele te from table "%ls". %ls 7346 16 Cannot get the data of the row from the OLE DB provider "%ls" fo r linked server "%ls". %ls 7347 16 OLE DB provider '%ls' for linked server '%ls' returned data that does not match expected data length for column '%ls.%ls'. The (maximum) expecte d data length is %ls, while the returned data length is %ls. 7348 16 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 extend

ed error message. 7349 16 The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls" because of column "%ls". %ls 7350 16 Cannot get the column information from OLE DB provider "%ls" for linked server "%ls". 7351 16 The OLE DB provider "%ls" for linked server "%ls" could not map ordinals for one or more columns of object "%ls". 7352 16 The OLE DB provider "%ls" for linked server "%ls" supplied incon sistent metadata. The object "%ls" was missing the expected column "%ls". 7353 16 The OLE DB provider "%ls" for linked server "%ls" supplied incon sistent metadata. An extra column was supplied during execution that was not fou nd at compile time. 7354 16 The OLE DB provider "%ls" for linked server "%ls" supplied inval id metadata for column "%ls". %ls 7355 16 The OLE DB provider "%ls" for linked server "%ls" supplied incon sistent metadata for a column. The name was changed at execution time. 7356 16 The OLE DB provider "%ls" for linked server "%ls" supplied incon sistent metadata for a column. The column "%ls" (compile-time ordinal %ld) of ob ject "%ls" was reported to have a "%ls" of %ld at compile time and %ld at run ti me. 7357 16 Cannot process the object "%ls". The OLE DB provider "%ls" for l inked server "%ls" indicates that either the object has no columns or the curren t user does not have permissions on that object. 7358 16 Cannot execute the query. The OLE DB provider "%ls" for linked s erver "%ls" did not provide an appropriate interface to access the text, ntext, or image column "%ls.%ls". 7359 16 The OLE DB provider "%ls" for linked server "%ls" reported a cha nge in schema version between compile time ("%ls") and run time ("%ls") for tabl e "%ls". 7360 16 Cannot get the length of a storage object from OLE DB provider " %ls" for linked server "%ls" for table "%ls", column "%ls". 7361 16 Cannot read a storage object from OLE DB provider "%ls" for link ed server "%ls", for table "%ls", column "%ls". 7362 16 The OLE DB provider "%ls" for linked server "%ls" reported diffe rent metadata at run time for table "%ls", column "%ls". 7365 16 Cannot obtain optional metadata columns of columns rowset from O LE DB provider "%ls" for linked server "%ls". 7366 16 Cannot obtain columns rowset from OLE DB provider "%ls" for link ed server "%ls". 7367 16 The OLE DB provider "%ls" for linked server "%ls" supports colum n level collation, but failed to provide the metadata column "%ls" at run time. 7368 16 The OLE DB provider "%ls" for linked server "%ls" supports colum n level collation, but failed to provide collation data for column "%ls". 7369 16 The OLE DB provider '%ls' for linked server '%ls' provided inval id collation. LCID = %08x, Compflags = %08x, SortOrder = '%.*ls'. 7370 16 One or more properties could not be set on the query for OLE DB provider "%ls" for linked server "%ls". %ls 7371 16 The server option 'collation name' in linked server '%ls' for OL E DB provider '%ls' has collation id %08x which is not supported by SQL Server. 7372 16 Cannot get properties from OLE DB provider "%ls" for linked serv er "%ls". 7373 16 Cannot set the initialization properties for OLE DB provider "%l s" for linked server "%ls". 7374 16 Cannot set the session properties for OLE DB provider "%ls" for linked server "%ls". 7375 16 Cannot open index "%ls" on table "%ls" from OLE DB provider "%ls " for linked server "%ls". %ls 7376 16 Could not enforce the remote join hint for this query. 7377 16 Cannot specify an index hint for a remote data source. 7380 16 Table-valued parameters are not allowed in remote calls between

servers. 7390 16 The requested operation could not be performed because OLE DB pr ovider "%ls" for linked server "%ls" does not support the required transaction i nterface. 7391 16 The operation could not be performed because OLE DB provider "%l s" for linked server "%ls" was unable to begin a distributed transaction. 7392 16 Cannot start a transaction for OLE DB provider "%ls" for linked server "%ls". 7393 16 The OLE DB provider "%ls" for linked server "%ls" reported an er ror 0x%08X aborting the current transaction. 7394 16 The OLE DB provider "%ls" for linked server "%ls" reported an er ror committing the current transaction. 7395 16 Unable to start a nested transaction for OLE DB provider "%ls" f or linked server "%ls". A nested transaction was required because the XACT_ABORT option was set to OFF. 7396 16 Varchar(max), nvarchar(max), varbinary(max) and large CLR type d ata types are not supported as return value or output parameter to remote querie s. 7397 16 Remote function returned varchar(max), nvarchar(max), varbinary( max) or large CLR type value which is not supported. 7399 16 The OLE DB provider "%ls" for linked server "%ls" reported an er ror. %ls 7401 16 The OLE DB provider "%ls" returned invalid literal prefix/suffix string. 7403 16 The OLE DB provider "%ls" has not been registered. 7404 16 The server could not load DCOM. 7405 16 Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS o ptions to be set for the connection. This ensures consistent query semantics. En able these options and then reissue your query. 7409 16 Could not start distributed query using integrated login because the user is logged in using SQL Server authentication. Provide remote server lo gin user ID and password in the connection string. 7410 16 Remote access is not allowed for impersonated security context. 7411 16 Server '%.*ls' is not configured for %ls. 7412 16 OLE DB provider "%ls" for linked server "%ls" returned message " %ls". 7413 16 Could not connect to linked server '%ls' (OLE DB Provider '%ls') . Enable delegation or use a remote SQL Server login for the current user. 7414 16 Invalid number of parameters. Rowset '%ls' expects %d parameter( s). 7415 16 Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server. 7416 16 Access to the remote server is denied because no login-mapping e xists. 7417 16 GROUP BY ALL is not supported in queries that access remote tabl es if there is also a WHERE clause in the query. 7418 16 Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider. 7419 16 Lazy schema validation error. Linked server schema version has c hanged. Re-run the query. 7420 16 Remote access is not supported for transaction isolation level " %ls". 7421 10 Cannot fetch the rowset from OLE DB provider "%ls" for linked se rver "%ls". %ls. 7422 16 OLE DB provider "%ls" for linked server "%ls" returned an invali d index definition for table "%ls". 7423 16 The '%ls' OLE DB provider for the '%ls' linked server returned a n invalid CLR type definition for the '%ls' table. 7424 10 OLE DB provider "%ls" for linked server "%ls" returned "%ls" wit h data type "%ls", which should be type "%ls".

7425 10 OLE DB provider "%ls" for linked server "%ls" returned an incorr ect value for "%ls", which should be "%ls". 7426 10 OLE DB provider "%ls" for linked server "%ls" returned "%ls" wit hout "%ls" being supported. 7427 10 OLE DB provider "%ls" for linked server "%ls" returned "%ls" for "%ls" during statistics gathering. 7428 10 OLE DB provider "%ls" for linked server "%ls" supported the sche ma lock interface, but returned "%ls" for "%ls". 7429 10 %hs SQL Server Remote Metadata Gather Time for Table %s.%s:%hs, CPU time = %lu ms, elapsed time = %lu ms. 7430 16 Out-of-process use of OLE DB provider "%ls" with SQL Server is n ot supported. 7431 16 Unable to delete OLE DB parameter properties. 7432 16 Heterogeneous queries and use of OLEDB providers are not support ed in fiber mode. 7433 10 OLE DB provider '%ls' for linked server '%ls' returned truncated data for column '%ls.%ls'. The actual data length is %ls and truncated data len gth is %ls. 7435 16 The OLE DB provider "%ls" for linked server "%ls" returned unexp ected NULL pointer for string column "%ls.%ls". 7436 16 The query processor could not produce a query plan because FORCE SEEK or FORCESCAN hints on table or view '%.*ls' cannot be used with remote data sources. Remove the hints and resubmit the query. 7437 16 Linked servers cannot be used under impersonation without a mapp ing for the impersonated login. 7438 16 The 32-bit OLE DB provider "%ls" cannot be loaded in-process on a 64-bit SQL Server. 7601 16 Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' be cause it is not full-text indexed. 7604 17 Full-text operation failed due to a time out. 7606 17 Could not find full-text index for database ID %d, table or inde xed view ID %d. 7607 17 Search on full-text catalog '%ls' for database ID %d, table or i ndexed view ID %d with search condition '%ls' failed with unknown result (0x%x). 7608 16 An unknown full-text failure (0x%x) occurred during "%hs". 7609 17 Full-Text Search is not installed, or a full-text component cann ot be loaded. 7610 16 Access is denied to "%.*ls", or the path is invalid. 7613 16 Cannot drop index '%.*ls' because it enforces the full-text key for table or indexed view '%.*ls'. 7614 16 Cannot alter or drop column '%.*ls' because it is enabled for Fu ll-Text Search. 7615 16 A CONTAINS or FREETEXT predicate can only operate on one table o r indexed view. Qualify the use of * with a table or indexed view name. 7616 16 Full-Text Search is not enabled for the current database. Use sp _fulltext_database to enable full-text search for the database. The functionalit y to disable and enable full-text search for a database is deprecated. Please ch ange your application. 7617 16 Query does not reference the full-text indexed table or indexed view, or user does not have permission to perform this action. 7619 16 The execution of a full-text query failed. "%ls" 7620 16 The conversion to data type %ls failed for the full-text search key. 7621 16 Invalid use of full-text predicate in the HAVING clause. 7622 17 There is not sufficient disk space to complete this operation fo r the full-text catalog "%ls". 7624 16 Full-text catalog '%ls' is in an unusable state. Drop and re-cre ate this full-text catalog. 7625 16 Full-text table or indexed view has more than one LCID among its full-text indexed columns.

7626 15 The top_n_by_rank argument ('%d') must be greater than or equal to zero. 7627 16 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 se rver can be used. 7629 17 Cannot open or query the full-text default path registry key. Th e full-text default catalog path is invalid. 7630 15 Syntax error near '%.*ls' in the full-text search condition '%.* ls'. 7632 15 The value of the Weight argument must be between 0.0 and 1.0. 7636 10 Warning: Request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently active for this table or indexed view. 7638 10 Warning: Request to stop change tracking has deleted all changes tracked on table or indexed view '%ls'. 7640 10 Warning: Request to stop tracking changes on table or indexed vi ew '%.*ls' will not stop population currently in progress on the table or indexe d view. 7641 16 Full-Text catalog '%ls' does not exist in database '%.*ls' or us er does not have permission to perform this action. 7642 16 A full-text catalog named '%ls' already exists in this database. Use a different name. 7644 16 Full-text crawl manager has not been initialized. Any crawl star ted before the crawl manager was fully initialized will need to be restarted. Pl ease restart SQL Server and retry the command. You should also check the error l og to fix any failures that might have caused the crawl manager to fail. 7645 16 Null or empty full-text predicate. 7646 16 Fulltext predicate references columns from two different tables or indexed views '%.*ls' and '%.*ls' which is not allowed. 7647 10 Warning: Configuration of full-text catalog at '%ls' could not b e saved during detach database. 7648 10 Warning: Failed to attach full-text catalog '%ls'. 7649 10 Warning: Failed to dismount full-text catalog at '%ls'. 7650 10 Warning: Failed to drop full-text catalog at '%ls'. 7651 10 Warning: The ongoing population is necessary to ensure an up-todate index. If needed, stop change tracking first, and then deactivate the fulltext index population. 7652 16 A full-text index for table or indexed view '%.*ls' has already been created. 7653 16 '%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 i s not offline, is not defined on a non-deterministic or imprecise nonpersisted c omputed column, does not have a filter, and has maximum size of %d bytes. Choose another index for the full-text key. 7654 16 Unable to obtain the population status of the table or indexed v iew '%.*ls'. 7655 16 TYPE COLUMN option must be specified with column of image or var binary(max) type. 7656 16 Full-text index for table or indexed view '%.*ls' cannot be popu lated because the database is in single-user access mode. 7657 10 Warning: Table or indexed view '%.*ls' has full-text indexed col umns that are of type image, text, or ntext. Full-text change tracking cannot tr ack WRITETEXT or UPDATETEXT operations performed on these columns. 7658 16 Table or indexed view '%.*ls' does not have a full-text index or user does not have permission to perform this action. 7659 16 Cannot activate full-text search for table or indexed view '%.*l s' because no columns have been enabled for full-text search. 7660 16 Full-text search must be activated on table or indexed view '%.* ls' before this operation can be performed. 7661 10 Warning: Full-text change tracking is currently enabled for tabl

e or indexed view '%.*ls'. 7662 10 Warning: Full-text auto propagation is currently enabled for tab le or indexed view '%.*ls'. 7663 16 Option 'WITH NO POPULATION' should not be used when change track ing is enabled. 7664 16 Full-text change tracking must be started on table or indexed vi ew '%.*ls' before the changes can be flushed. 7665 16 Full Crawl must be executed on table or indexed view '%.*ls'. Co lumns affecting the index have been added or dropped since the last index full p opulation. 7666 16 User does not have permission to perform this action. 7668 16 Cannot drop full-text catalog '%ls' because it contains a full-t ext index. 7669 10 Warning: Full-text index for table or indexed view '%.*ls' canno t be populated because the database is in single-user access mode. Change tracki ng is stopped for this table or indexed view. 7670 16 Column '%.*ls' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column. 7671 16 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 c haracters. 7672 16 A full-text index cannot be created on the table or indexed view because duplicate column '%.*ls' is specified. 7673 10 Warning: Full-text change tracking is currently disabled for tab le or indexed view '%.*ls'. 7674 10 Warning: The fulltext catalog '%.*ls' is being dropped and is cu rrently set as default. 7676 10 Warning: Full-text auto propagation is on. Stop crawl request is ignored. 7677 16 Column "%.*ls" is not full-text indexed. 7678 16 The following string is not defined as a language alias in sysla nguages: %.*ls. 7679 16 Full-text index language of column "%.*ls" is not a language sup ported by full-text search. 7680 16 Default full-text index language is not a language supported by full-text search. 7681 10 Warning: Directory '%ls' does not have a valid full-text catalog . Full-text catalog header file or attach state file either is missing or corrup ted. The full-text catalog cannot be attached. 7682 10 The component '%ls' reported error while indexing. Component pat h '%ls'. 7683 16 Errors were encountered during full-text index population for ta ble or indexed view '%ls', database '%ls' (table or indexed view ID '%d', databa se ID '%d'). Please see full-text crawl logs for details. 7684 10 Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-t ext key value '%ls'. Failed to index the row. 7685 10 Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-t ext key value '%ls'. Attempt will be made to reindex it. 7686 10 Cannot use a CONTAINS, FREETEXT, CONTAINSTABLE or FREETEXTTABLE construct on table or indexed view '%.*ls' because none of its columns are fulltext indexed. Register at least one column for full-text search using ALTER FULL TEXT INDEX statement. 7689 16 Execution of a full-text operation failed. '%ls' 7690 16 Full-text operation failed because database is read only. 7691 16 Access is denied to full-text log path. Full-text logging is dis abled for database '%ls', catalog '%ls' (database ID '%d', catalog ID '%d'). 7692 16 Full-text catalog path '%.*ls' exceeded %d character limit. 7693 16 Full-text initialization failed to create a memory clerk.

7694 16 Failed to pause catalog for backup. Backup was aborted. 7696 16 Invalid locale ID was specified. Please verify that the locale I D is correct and corresponding language resource has been installed. 7697 10 Warning: Full-text index on table or indexed view '%.*ls' in dat abase '%.*ls' has been changed after full-text catalog files backup. A full popu lation is required to bring full-text index to a consistent state. 7698 16 GROUP BY ALL cannot be used in full text search queries. 7699 16 TYPE COLUMN option is not allowed for column types other than im age or varbinary(max). 7702 16 Empty Partition function type-parameter-list is not allowed when defining a partition function. 7703 16 Can not create RANGE partition function with multiple parameter types. 7704 16 The type '%.*ls' is not valid for this operation. 7705 16 Could not implicitly convert range values type specified at ordi nal %d to partition function parameter type. 7706 16 Partition function '%ls' is being used by one or more partition schemes. 7707 16 The associated partition function '%ls' generates more partition s than there are file groups mentioned in the scheme '%ls'. 7708 16 Duplicate range boundary values are not allowed in partition fun ction boundary values list. Partition boundary values at ordinal %d and %d are e qual. 7709 10 Warning: Range value list for partition function '%.*ls' is not sorted by value. Mapping of partitions to filegroups during CREATE PARTITION SCH EME will use the sorted boundary values if the function '%.*ls' is referenced in CREATE PARTITION SCHEME. 7710 10 Warning: The partition scheme '%.*ls' does not have any next use d filegroup. Partition scheme has not been changed. 7711 16 The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table is partitioned. 7712 10 Partition scheme '%.*ls' has been created successfully. '%.*ls' is marked as the next used filegroup in partition scheme '%.*ls'. 7713 10 %d filegroups specified after the next used filegroup are ignore d. 7714 16 Partition range value is missing. 7715 16 The specified partition range value could not be found. 7716 16 Can not create or alter a partition function to have zero partit ions. 7717 16 The partition scheme "%.*ls" is currently being used to partitio n one or more tables. 7718 16 Partition range value cannot be specified for hash partitioning. 7719 16 CREATE/ALTER partition function failed as only a maximum of %d p artitions can be created. 7720 16 Data truncated when converting range values to the partition fun ction parameter type. The range value at ordinal %d requires data truncation. 7721 16 Duplicate range boundary values are not allowed in partition fun ction boundary values list. The boundary value being added is already present at ordinal %d of the boundary value list. 7722 16 Invalid partition number %I64d specified for %S_MSG '%.*ls', par tition number can range from 1 to %d. 7723 16 Only a single filegroup can be specified while creating partitio n scheme using option ALL to specify all the filegroups. 7724 16 Computed column cannot be used as a partition key if it is not p ersisted. Partition key column '%.*ls' in table '%.*ls' is not persisted. 7725 16 Alter partition function statement failed. Cannot repartition ta ble '%.*ls' by altering partition function '%.*ls' because its clustered index ' %.*ls' is disabled. 7726 16 Partition column '%.*ls' has data type %s which is different fro m the partition function '%.*ls' parameter data type %s.

7727 16 Collation of partition column '%.*ls' does not match collation o f corresponding parameter in partition function '%.*ls'. 7728 16 Invalid partition range: %d TO %d. Lower bound must not be great er than upper bound. 7729 16 Cannot specify partition number in the %S_MSG %S_MSG statement a s the %S_MSG '%.*ls' is not partitioned. 7730 16 Alter %S_MSG statement failed because partition number %d does n ot exist in %S_MSG '%.*ls'. 7731 16 Cannot specify partition number in Alter %S_MSG statement to reb uild or reorganize a partition of %S_MSG '%.*ls'. 7732 16 Cannot specify partition number in Alter index statement along w ith keyword ALL to rebuild partitions of table '%.*ls' when the table does not h ave any regular indexes. 7733 16 '%ls' statement failed. The %S_MSG '%.*ls' is partitioned while %S_MSG '%.*ls' is not partitioned. 7734 10 The %S_MSG '%.*ls' specified for the clustered index '%.*ls' was used for table '%.*ls' even though %S_MSG '%.*ls' is specified for it. 7735 16 Cannot specify partition number in alter %S_MSG statement to reb uild or reorganize a partition of %S_MSG '%.*ls' as %S_MSG is not partitioned. 7736 16 Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning. 7737 16 Filegroup %.*ls is of a different filegroup type than the first filegroup in partition scheme %.*ls 7738 16 Cannot enable compression for object '%.*ls'. Only SQL Server En terprise Edition supports compression. 7801 15 The required parameter %.*ls was not specified. 7802 16 Functions that have a return type of "%.*ls" are unsupported thr ough SOAP invocation. 7803 15 The clause %.*ls can not be used in the %.*ls statement. 7804 15 %.*ls and %.*ls can not share the same value. 7805 16 The parameter SITE can not be prefixed by a scheme such as 'http ://'. Valid values for SITE include {'*' | '+' | 'site_name'}. 7806 16 The URL specified by endpoint '%.*ls' is already registered to r eceive requests or is reserved for use by another service. 7807 16 An error ('0x%x') occurred while attempting to register the endp oint '%.*ls'. 7808 10 The endpoint '%.*ls' could not be unregistered. 7809 10 Cannot find the object '%.*ls', because it does not exist or you do not have permission. 7810 15 The value '%d' is not within range for the '%.*ls' parameter. 7811 16 COMPUTE BY queries are not supported over SOAP. 7812 10 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 H TTP access. Check the SQL Server error log for any errors that might have occurr ed while starting HTTP support. 7813 16 The parameter PATH must be supplied in its canonical form. An a cceptable PATH is '%.*ls'. 7814 10 The specified value '%.*ls' already exists. 7815 10 The specified value '%.*ls' does not exist. 7816 15 A duplicate parameter was specified, '%.*ls'. 7817 16 The Base64 encoded input data was malformed for the parameter "% .*ls". 7818 16 The request exceeds an internal limit. Simplify or reduce the si ze of the request. 7819 15 The SOAP method object '%.*ls' must be specified using a fully q ualified three-part name. 7820 16 SOAP namespaces beginning with '%.*ls' are disallowed because th ey are reserved for system use. 7821 10 Cannot find the database '%.*ls', because it does not exist or y

ou do not have permission. 7822 16 An unexpected XML node "%.*ls" (in the namespace "%.*ls") was fo und in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 7823 16 The "%.*ls" XML element (in the "%.*ls" namespace) was expected in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 7824 16 The "%.*ls" XML element (in the "%.*ls" namespace) was expected as the topmost node of the SOAP request. 7825 16 A SOAP method element was expected in the "%.*ls" element (in th e "%.*ls" namespace) of the SOAP request. 7826 16 Unexpected character data was found in the "%.*ls" element (in t he "%.*ls" namespace) of the SOAP request. 7827 14 The user does not have permission to reserve and unreserve HTTP namespaces. 7828 11 The statement is not supported on this version of the operating system. Could not find Httpapi.dll in the path. 7829 11 The statement is not supported on this version of the operating system. Could not find function entry point '%.*ls' in Httpapi.dll. 7830 16 Unable to complete the operation because of an unexpected error. 7831 16 A reservation for this HTTP namespace (%.*ls) already exists. 7832 16 A reservation for this HTTP namespace (%.*ls) does not exist. 7833 16 The HTTP namespace (%.*ls) is in an invalid format. Specify the namespace in its canonical form. 7834 10 The reservation for the HTTP namespace (%.*ls) has been deleted. If there are any endpoints associated with this namespace, they will continue t o receive and process requests until the server is restarted. 7835 16 Endpoint '%.*ls' has been disabled because it is insecurely conf igured. For a more information, attempt to start the endpoint using the ALTER EN DPOINT statement. 7836 20 A fatal error occurred while reading the input stream from the n etwork. The maximum number of network packets in one request was exceeded. Try u sing bulk insert, increasing network packet size, or reducing the size of the re quest. The session will be terminated. 7847 16 XML data was found in the parameter '%.*ls' which is not an XML parameter. Please entitize any invalid XML character data in this parameter, or pass the parameter in typed as XSD:anyType or sqltypes:xml. 7848 15 An invalid or unsupported localeId was specified for parameter " %.*ls". 7849 15 Invalid sqlCompareOptions were specified for parameter "%.*ls". 7850 16 The SQL Server Service account does not have permission to regis ter the supplied URL on the endpoint '%.*ls'. Use sp_reserve_http_namespace to explicitly reserve the URL namespace before you try to register the URL again. 7851 15 The %.*ls attribute must be specified on the %.*ls element of th e parameter "%.*ls" because it is of type %.*ls. 7852 15 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 t ype. 7853 16 The URL specified as the path ("%.*ls") is not in an absolute fo rmat, and must begin with "%.*ls". 7854 16 The URL value specified for the "%.*ls" parameter is too long. 7855 15 Reading from HTTP input stream failed. 7856 16 XML parameters do not support non-unicode element or attribute v alues. 7857 16 Parameter "%.*ls": Function or procedure parameters with imprope rly formatted or deprecated names are not supported through Native SOAP access. Refer to documentation for rules concerning the proper naming of parameters. 7858 16 The "%.*ls" XML element (in the "%.*ls" namespace) in the "%.*ls " element (in the "%.*ls" namespace) of the SOAP request contained an invalid bi nary type. 7859 15 Parameter "%.*ls": Parameter collation cannot be specified on th e "%.*ls" node (in the namespace "%.*ls").

7860 15 An endpoint's transport or content cannot be changed through the ALTER ENDPOINT statement. Use DROP ENDPOINT and execute the CREATE ENDPOINT sta tement to make these changes. 7861 15 "%.*ls" endpoints can only be of the "FOR %.*ls" type. 7862 16 An endpoint of the requested type already exists. Only one endp oint of this type is supported. Use ALTER ENDPOINT or DROP the existing endpoin t and execute the CREATE ENDPOINT statement. 7863 16 The endpoint was not changed. The ALTER ENDPOINT statement did n ot contain any values to modify or update. 7864 16 CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection endpoint is reserved and cannot be updated. 7865 16 Web Services Description Language (WSDL) generation failed becau se the system was unable to query the metadata for the endpoint. 7866 16 XML attribute and element values larger than 4000 characters are only allowed within the SOAP Body node. 7867 15 An invalid sqlCollationVersion was specified for parameter "%.*l s". 7868 15 An invalid sqlSortId was specified for parameter "%.*ls". 7869 16 The endpoint name '%.*ls' is reserved for used by SQL. Endpoint names cannot begin with '%.*ls'. 7870 16 The AFFINITY clause is not supported for endpoints of this type. 7871 16 The clause "%.*ls" is not valid for this endpoint type. 7872 16 "%.*ls" is not a parameter for procedure "%.*ls", or it was supp lied out of order. 7873 16 The endpoint "%.*ls" is a built-in endpoint and cannot be droppe d. Use the protocol configuration utilities to ADD or DROP Transact-SQL endpoint s. 7874 16 An endpoint already exists with the bindings specified. Only on e endpoint supported for a specific binding. Use ALTER ENDPOINT or DROP the exi sting endpoint and execute the CREATE ENDPOINT statement. 7875 16 An unexpected XML construct was found in the character data of t he "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 7878 16 This "%.*ls ENDPOINT" statement is not supported on this edition of SQL Server. 7879 10 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 S QL Server is shutdown. 7880 10 SQL Server has successfully finished closing sessions and connec tions. 7881 10 SQL Server was unable to close sessions and connections in a rea sonable amount of time and is aborting "polite" shutdown. 7882 16 OUTPUT was requested for parameter '%.*ls', which is not support ed for a WEBMETHOD with FORMAT=NONE. 7883 16 User-defined functions cannot be used for a WEBMETHOD with FORMA T=NONE. 7884 20 Violation of tabular data stream (TDS) protocol. This is most of ten caused by a previous exception on this task. The last exception on the task was error %d, severity %d, address 0x%p. This connection will be terminated. 7885 20 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 disco nnected without reading the entire response from the server. This connection wil l be terminated. 7886 20 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 UNC OMMITTED isolation level. This connection will be terminated. 7887 20 The IPv6 address specified is not supported. Only addresses tha t are in their numeric, canonical form are supported for listening. 7888 20 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 re cognized IPv6 format. 7889 16 The SOAP headers on the request have exceeded the size limits es tablished for this endpoint. The endpoint owner may increase these limits via A LTER ENDPOINT. 7890 16 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 con flict. 7891 10 Creation of a TSQL endpoint will result in the revocation of any 'Public' connect permissions on the '%.*ls' endpoint. If 'Public' access is de sired on this endpoint, reapply this permission using 'GRANT CONNECT ON ENDPOINT ::[%.*ls] to [public]'. 7892 16 Internal subset DTDs inside SOAP requests are not allowed. 7893 15 Parameter '%.*ls': Incompatible XML attributes were present. T he '%.*ls' attribute and the '%.*ls' attribute may not both be present on a para meter value node of type '%.*ls' (in the namespace '%.*ls'). 7894 16 Listening has not been started on the endpoint '%.*ls' found in metadata. Endpoint operations are disabled on this edition of SQL Server. 7895 14 Only a system administrator can specify a custom WSDL stored pro cedure on the endpoint. 7896 16 The column or parameter '%.*ls' uses a data type not supported b y SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. 7897 10 Creating and altering SOAP endpoints will be removed in a future version of SQL Server. Avoid using this feature in new development work, and pl an to modify applications that currently use it. 7898 10 SQL Server native SOAP support is now deprecated and will be rem oved in a future version of SQL Server. Avoid using this feature in new developm ent work, and plan to modify applications that currently use it. 7899 16 The return value uses a data type not supported by SOAP. SOAP o nly supports data types supported in SQL Server 2005 or earlier. 7901 16 The repair statement was not processed. This level of repair is not supported when the database is in emergency mode. 7903 16 Table error: The orphaned file "%.*ls" was found in the FILESTRE AM directory ID %.*ls container ID %d for object ID %d, index ID %d, partition I D %I64d, column ID %d. 7904 16 Table error: Cannot find the FILESTREAM file "%.*ls" for column ID %d (column directory ID %.*ls container ID %d) in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d. 7905 16 Database error: The directory "%.*ls" is not a valid FILESTREAM directory in container ID %d. 7906 16 Database error: The file "%.*ls" is not a valid FILESTREAM file in container ID %d. 7907 16 Table error: The directory "%.*ls" under the rowset directory ID %.*ls is not a valid FILESTREAM directory in container ID %d. 7908 16 Table error: The file "%.*ls" in the rowset directory ID %.*ls i s not a valid FILESTREAM file in container ID %d. 7909 20 The emergency-mode repair failed.You must restore from backup. 7910 10 Repair: The page %S_PGID has been allocated to object ID %d, ind ex ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 7911 10 Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 7912 10 Repair: The extent %S_PGID has been allocated to object ID %d, i ndex ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 7913 10 Repair: The extent %S_PGID has been deallocated from object ID % d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 7914 10 Repair: %ls page at %S_PGID has been rebuilt. 7915 10 Repair: IAM chain for object ID %d, index ID %d, partition ID %I 64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID an

d will be rebuilt. 7916 10 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 w ill be rebuilt. 7917 10 Repair: Converted forwarded record for object ID %d, index ID %d , partition ID %I64d, alloc unit ID %I64d (type %.*ls), at page %S_PGID, slot %d to a data row. 7918 10 Repair: Page %S_PGID next and %S_PGID previous pointers have bee n set to match each other in object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). 7919 16 Repair statement not processed. Database needs to be in single u ser mode. 7920 10 Processed %ld entries in system catalog for database ID %d. 7921 16 Repair statement not processed. Database cannot be a snapshot. 7922 16 *************************************************************** 7923 10 Table %.*ls Object ID %ld. 7924 10 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls ). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d. 7925 10 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls ). %I64d pages used in %I64d dedicated extents. 7926 16 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 lo cked. See Books Online for details of when this behavior is expected and what wo rkarounds exist. Also see previous errors for more details. 7927 10 Total number of extents is %I64d. 7928 16 The database snapshot for online checks could not be created. Ei ther the reason is given in a previous error or one of the underlying volumes do es not support sparse files or alternate streams. Attempting to get exclusive ac cess to run checks offline. 7929 16 Check statement aborted. Database contains deferred transaction s. 7930 16 Mirroring must be removed from the database for this DBCC comman d. 7931 16 Database error: The FILESTREAM directory ID %.*ls for a partitio n was seen two times. 7932 16 Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d is in filegroup %d, but should be in filegroup %d. 7933 16 Table error: A FILESTREAM directory ID %.*ls exists for a partit ion, but the corresponding partition does not exist in the database. 7934 16 DBCC CHECK cannot proceed on database %.*ls because it is a Seco ndary Replica and either Snapshot creation failed or the WITH TABLOCK option was specified. Secondary Replica databases cannot be exclusively locked for DBCC CH ECK. Reason may have been given in previous error. 7935 16 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 exis t in the partition. 7936 16 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. 7938 16 Table error: object ID %d, index ID %d, partition ID %I64d proce ssing encountered file name "%.*ls" twice in the column directory %d container I D %d (for column ID %d). 7939 16 Cannot detach database '%.*ls' because it does not exist. 7940 16 System databases master, model, msdb, and tempdb cannot be detac hed. 7941 16 Table error: object ID %d, index ID %d, partition ID %I64d proce ssing encountered file name "%.*ls" twice in the column ID %d (for column direct ory %d container ID %d). 7942 10 DBCC %ls scanning '%.*ls' table...

7943 10 Table: '%.*ls' (%d); index ID: %d, database ID: %d 7944 10 %ls level scan performed. 7945 10 - Pages Scanned................................: %I64d 7946 10 - Extents Scanned..............................: %I64d 7947 10 - Extent Switches..............................: %I64d 7948 10 - Avg. Pages per Extent........................: %3.1f 7949 10 - Scan Density [Best Count:Actual Count].......: %4.2f%ls [%I64d :%I64d] 7950 10 - Logical Scan Fragmentation ..................: %4.2f%ls 7951 10 Warning: Could not complete filestream consistency checks due t o an operating system error. Any consistency errors found in the filestream sub system will be silenced. Please refer to other errors for more information. Th is condition is likely transient; try rerunning the command. 7952 10 - Extent Scan Fragmentation ...................: %4.2f%ls 7953 10 - Avg. Bytes Free per Page.....................: %3.1f 7954 10 - Avg. Page Density (full).....................: %4.2f%ls 7955 16 Invalid SPID %d specified. 7956 16 Table error: The FILESTREAM file "%.*ls" for column ID %d was fo und in column directory ID %.*ls of container ID %d but should be in container I D %d in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d. 7957 10 Cannot display the specified SPID's buffer; in transition. 7958 16 The specified SPID does not process input/output data streams. 7960 16 An invalid server process identifier (SPID) %d or batch ID %d wa s specified. 7961 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls) , page ID %S_PGID, row ID %d. Column '%.*ls' is a var column wit h a NULL value and non-zero data length 7962 16 Invalid BATCHID %d specified. 7963 16 Database error: The file "%.*ls" is not a valid FILESTREAM LOG f ile in container ID %d. 7964 10 Repair: Deleted FILESTREAM file "%.*ls" for column ID %d, for ob ject ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d. 7965 16 Table error: Could not check object ID %d, index ID %d, partitio n ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) pag e(s). 7966 10 Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped. 7968 10 Transaction information for database '%.*ls'. 7969 16 No active open transactions. 7970 10 %hsOldest active transaction: 7971 10 SPID (server process ID): %d%s 7972 10 UID (user ID) : %d 7974 10 Name : %.*ls 7975 10 LSN : (%d:%d:%d) 7977 10 Start time : %.*ls 7978 10 SID : %.*ls 7979 10 %hsReplicated Transaction Information: 7980 10 Oldest distributed LSN : (%d:%d:%d) 7982 10 Oldest non-distributed LSN : (%d:%d:%d) 7983 14 User '%.*ls' does not have permission to run DBCC %ls for databa se '%.*ls'. 7984 16 System table pre-checks: Object ID %d. Page %S_PGID has unexpect ed page type %d. Check statement terminated due to unrepairable error. 7985 16 System table pre-checks: Object ID %d. Could not read and latch page %S_PGID with latch type %s. Check statement terminated due to unrepairable error. 7986 16 System table pre-checks: Object ID %d has cross-object chain lin kage. Page %S_PGID points to %S_PGID in alloc unit ID %I64d (should be %I64d). C

heck statement terminated due to unrepairable error. 7987 16 System table pre-checks: Object ID %d has chain linkage mismatch . %S_PGID->next = %S_PGID, but %S_PGID->prev = %S_PGID. Check statement terminat ed due to unrepairable error. 7988 16 System table pre-checks: Object ID %d. Loop in data chain detect ed at %S_PGID. Check statement terminated due to unrepairable error. 7989 16 Checking identity information: current identity value '%.*hs'. 7992 16 Cannot shrink 'read only' database '%.*ls'. 7993 10 Cannot shrink file '%d' in database '%.*ls' to %u pages as it on ly contains %u pages. 7994 10 DBCC CheckDatabase on resource database will be skipped because user '%.*ls' does not have permission. 7995 16 Database '%.*ls': consistency errors in system catalogs prevent further DBCC %ls processing. 7996 16 Extended stored procedures can only be created in the master dat abase. 7997 16 '%.*ls' does not contain an identity column. 7998 16 Checking identity information: current identity value '%.*hs', c urrent column value '%.*hs'. 7999 16 Could not find any index named '%.*ls' for table '%.*ls'. 8001 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter. 8002 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (XML) has an invalid database or schema specified. 8003 16 The incoming request has too many parameters. The server support s a maximum of %d parameters. Reduce the number of parameters and resend the req uest. 8004 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. The RPC name is invalid. 8005 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d: The parameter name is invalid. 8006 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d: The parameter status flags are in valid. 8007 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The chunking format is incorrect for a large object parameter of type 0x%02X. 8008 16 The number of params passed to sp_execute is not equal to the nu mber of params used when the handle was prepared (%d). 8009 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is unk nown. 8010 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X is different from the one sent last time. 8011 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_v ariant) has an invalid length for type-specific metadata. 8012 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_v ariant) has an invalid precision or scale for type-specific metadata. 8013 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_v ariant) has an invalid instance length. 8014 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_v ariant) has an invalid type for type-specific metadata.

8015 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is an untyped NULL but is marked as an output parameter. 8016 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid data length or metadata length. 8017 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid precision or scale. 8018 16 Invalid parameter %d ('%.*ls'): Data type 0x%02X is a deprecate d large object, or LOB, but is marked as output parameter. Deprecated types are not supported as output parameters. Use current large object types instead. 8019 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid user type specified. 8020 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid length for serialization metadata. 8021 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid database specified. 8022 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied value is N ULL and data type %.*ls cannot be NULL. Check the source data for invalid values . 8023 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied value is n ot a valid instance of data type %.*ls. Check the source data for invalid values . An example of an invalid value is data of numeric type with scale greater than precision. 8024 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_ variant) has an invalid collation for type-specific metadata. 8025 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has a maximum length different from the one sent last time. 8026 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has an actual length different from the one sent last time. 8027 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid schema specified. 8028 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 exa mple of an invalid length is data of nchar type with an odd length in bytes. 8029 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) an unexpected token was e ncountered processing a table-valued parameter. 8030 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (XML) has an invalid database or schema specified. 8031 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The chunking format is incorrect for a large object parameter of dat a type 0x%02X. 8032 16 The incoming tabular data stream (TDS) remote procedure call (RP

C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X is unknown. 8033 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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-specif ic metadata. 8034 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata. 8035 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid instance length. 8036 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata. 8037 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid data length or metadata length. 8038 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid precision or scale. 8039 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid user type specified. 8040 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid length for serialization metadata. 8041 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid database specified. 8042 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The supplied value is NULL and data type %.*ls cannot be NULL. Check the source data for invalid values. 8043 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 n umeric type with scale greater than precision. 8044 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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-sp ecific metadata. 8045 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid schema specified. 8046 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 sour ce data for invalid lengths. An example of an invalid length is data of nchar ty pe with an odd length in bytes. 8047 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 dat abase name specified. Database name is not allowed with a table-valued paramete r, only schema name and type name are valid. 8048 16 The incoming tabular data stream (TDS) remote procedure call (RP

C) 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 spe cified. 8049 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid type name specified. 8050 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 cou nt specified. 8051 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 nam e specified. 8052 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) timestamp column is requi red to be default. 8053 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 fla g specified. 8054 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid ordering and uniqueness metadata specified. 8055 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid column orderi ng metadata specified. 8056 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 met adata tokens specified. 8057 16 Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type). The specified column is computed or defa ult and has ordering or uniqueness set. Ordering and uniqueness can only be set on columns that have client supplied data. 8058 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter %d, to a parameterized s tring has no table type defined. 8059 16 The incoming tabular data stream (TDS) remote procedure call (RP C) protocol stream is incorrect. Table-valued parameter "%.*ls", to a parameteri zed string has no table type defined. 8060 16 The incoming tabular data stream (TDS) remote procedure call (RP C) 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 de fault. A null table-valued parameter is required to be sent as a default parame ter. 8061 16 The data for table-valued parameter "%.*ls" doesn't conform to t he table type of the parameter. 8062 16 The data for the table-valued parameter %d doesn't conform to th e table type of the parameter. 8063 16 The incoming tabular data stream (TDS) remote procedure call str eam is sending an unlimited length CLR type. Parameter %d ("%.*ls") is defined a s type %.*ls. This type is not supported by down-level clients. Send the seriali zed data of the large CLR type as varbinary(max), or upgrade the client driver t o one that supports unlimited CLR types. 8064 16 Parameter %d ([%.*ls].[%.*ls].[%.*ls]): The CLR type does not ex

ist or you do not have permissions to access it. 8101 16 An explicit value for the identity column in table '%.*ls' can o nly be specified when a column list is used and IDENTITY_INSERT is ON. 8102 16 Cannot update identity column '%.*ls'. 8105 16 '%.*ls' is not a user table. Cannot perform SET operation. 8106 16 Table '%.*ls' does not have the identity property. Cannot perfor m SET operation. 8107 16 IDENTITY_INSERT is already ON for table '%.*ls.%.*ls.%.*ls'. Can not perform SET operation for table '%.*ls'. 8108 16 Cannot add identity column, using the SELECT INTO statement, to table '%.*ls', which already has column '%.*ls' that inherits the identity prope rty. 8109 16 Attempting to add multiple identity columns to table '%.*ls' usi ng the SELECT INTO statement. 8110 16 Cannot add multiple PRIMARY KEY constraints to table '%.*ls'. 8111 16 Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'. 8112 16 Cannot add more than one clustered index for constraints on tabl e '%.*ls'. 8113 16 Incorrect use of the XML data type method '%.*ls'. A mutator met hod is expected in this context. 8114 16 Error converting data type %ls to %ls. 8115 16 Arithmetic overflow error converting %ls to data type %ls. 8116 16 Argument data type %ls is invalid for argument %d of %ls functio n. 8117 16 Operand data type %ls is invalid for %ls operator. 8118 16 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause. 8119 16 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause. 8120 16 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. 8121 16 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause. 8123 16 A correlated expression is invalid because it is not in a GROUP BY clause. 8124 16 Multiple columns are specified in an aggregated expression conta ining an outer reference. If an expression being aggregated contains an outer re ference, then that outer reference must be the only column referenced in the exp ression. 8125 16 An aggregated expression containing an outer reference must be c ontained in either the select list, or a HAVING clause subquery in the query who se FROM clause contains the table with the column being aggregated. 8126 16 Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because i t is not contained in an aggregate function and there is no GROUP BY clause. 8127 16 Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because i t is not contained in either an aggregate function or the GROUP BY clause. 8128 10 Using '%s' version '%s' to execute extended stored procedure '%s '. This is an informational message only; no user action is required. 8129 16 The new disk size must be greater than %d. Consider using DBCC S HRINKDB. 8131 10 Extended stored procedure DLL '%s' does not export __GetXpVersio n(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Se rvices" in the documentation for more information. 8132 10 Extended stored procedure DLL '%s' reports its version is %d.%d. The expected version is %d.%d. 8133 16 At least one of the result expressions in a CASE specification m ust be an expression other than the NULL constant. 8134 16 Divide by zero error encountered. 8135 16 Table level constraint does not specify column list, table '%.*l

s'. 8136 16 Duplicate columns specified in %ls constraint key list, table '% .*ls'. 8137 16 Incorrect use of the XML data type method '%.*ls'. A non-mutator method is expected in this context. 8138 16 More than 16 columns specified in foreign key column list, table '%.*ls'. 8139 16 Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'. 8140 16 More than one key specified in column level %ls constraint, tabl e '%.*ls'. 8141 16 Column %ls constraint for column '%.*ls' references another colu mn, table '%.*ls'. 8143 16 Parameter '%.*ls' was supplied multiple times. 8144 16 Procedure or function %.*ls has too many arguments specified. 8145 16 %.*ls is not a parameter for procedure %.*ls. 8146 16 Procedure %.*ls has no parameters and arguments were supplied. 8147 16 Could not create IDENTITY attribute on nullable column '%.*ls', table '%.*ls'. 8148 16 More than one column %ls constraint specified for column '%.*ls' , table '%.*ls'. 8149 16 OLE Automation objects are not supported in fiber mode. 8150 16 Multiple NULL constraints were specified for column '%.*ls', tab le '%.*ls'. 8151 16 Both a PRIMARY KEY and UNIQUE constraint have been defined for c olumn '%.*ls', table '%.*ls'. Only one is allowed. 8152 16 String or binary data would be truncated. 8153 10 Warning: Null value is eliminated by an aggregate or other SET o peration. 8154 15 The table '%.*ls' is ambiguous. 8155 15 No column name was specified for column %d of '%.*ls'. 8156 15 The column '%.*ls' was specified multiple times for '%.*ls'. 8158 15 '%.*ls' has more columns than were specified in the column list. 8159 15 '%.*ls' has fewer columns than were specified in the column list . 8160 15 A GROUPING or GROUPING_ID function can only be specified when th ere is a GROUP BY clause. 8161 15 Argument %d of the %.*ls function does not match any of the expr essions in the GROUP BY clause. 8162 16 The formal parameter "%.*ls" was not declared as an OUTPUT param eter, but the actual parameter passed in requested output. 8164 16 An INSERT EXEC statement cannot be nested. 8165 16 Invalid subcommand value %d. Legal range from %d to %d. 8166 16 Constraint name '%.*ls' not permitted. Constraint names cannot b egin with a number sign (#). 8167 16 The type of column "%.*ls" conflicts with the type of other colu mns specified in the UNPIVOT list. 8168 16 Cannot create, drop, enable, or disable more than one constraint , column, or trigger named '%.*ls' in this context. Duplicate names are not allo wed. 8169 16 Conversion failed when converting from a character string to uni queidentifier. 8170 16 Insufficient result space to convert uniqueidentifier value to c har. 8171 16 Hint '%ls' on object '%.*ls' is invalid. 8172 16 The argument %d of the XML data type method "%.*ls" must be a st ring literal. 8173 15 Incorrect syntax was used to invoke the XML data type method '%. *ls'. 8174 16 Schema lock with handle %d not found.

8175 10 Could not find table %.*ls. Will try to resolve this table name later. 8176 16 Resync procedure expects value of key '%.*ls', which was not sup plied. 8177 16 Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause. 8178 16 The parameterized query '%.*ls' expects the parameter '%.*ls', w hich was not supplied. 8179 16 Could not find prepared statement with handle %d. 8180 16 Statement(s) could not be prepared. 8181 16 Text for '%.*ls' is missing from the system catalog. The object must be dropped and re-created before it can be used. 8183 16 Only UNIQUE or PRIMARY KEY constraints can be created on compute d columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that compu ted columns be persisted. 8184 16 Error in binarychecksum. There are no comparable columns in the binarychecksum input. 8185 16 Error expanding "*": An incomparable column has been found in an underlying table or view. 8186 16 Function '%.*ls' can be used only on user and system tables. 8187 16 The prepared handle %d is currently being used by another comman d (error state: %d). 8188 16 There is already a SQL type for assembly type "%.*ls" on assembl y "%.*ls". Only one SQL type can be mapped to a given assembly type. CREATE TYPE fails. 8189 16 You do not have permission to run '%ls'. 8190 16 Cannot compile replication filter procedure without defining tab le being filtered. 8191 16 Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements. 8192 16 Replication filter procedures cannot have parameters. 8193 16 Cannot execute a procedure marked FOR REPLICATION. 8195 16 Cannot create "%.*ls" on "%.*ls". Insert, Update, and Delete tri ggers can only be created on user tables and views. 8196 16 Duplicate column specified as ROWGUIDCOL. 8197 16 The object '%.*ls' does not exist or is invalid for this operati on. 8199 16 In EXECUTE <procname>, procname can only be a literal or variabl e of type char, varchar, nchar, or nvarchar. 8301 10 Use of level0type with value 'USER' in procedure sp_addextendedp roperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valu ed 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 level0t ype with value 'SCHEMA' and level1type with value 'USER' for extended properties on USER. 8302 10 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 inste ad, which are created using the CHECK keyword of CREATE TABLE or ALTER TABLE. 8303 10 CREATE DEFAULT and DROP DEFAULT will be removed in a future vers ion of SQL Server. Avoid using CREATE DEFAULT and DROP DEFAULT in new developmen t work, and plan to modify applications that currently use them. Instead, use de fault definitions created using the DEFAULT keyword of ALTER TABLE or CREATE TAB LE. 8304 10 INDEXKEY_PROPERTY will be removed in a future version of SQL Ser ver. Avoid using this feature in new development work, and plan to modify applic ations that currently use the feature. Use sys.index_columns instead. 8305 10 The TEXT IN ROW feature will be removed in a future version of S QL Server. Avoid using sp_tableoption for TEXT IN ROW option in new development work, and plan to modify applications that currently use the text in row option.

The preferred method of storing large data is through use of the varchar(max), nvarchar(max) and varbinary(max) data types. 8306 10 Use of level0type with value 'TYPE' in procedure sp_addextendedp roperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valu ed 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 level0t ype with value 'SCHEMA' and level1type with value 'TYPE' for extended properties on TYPE. 8307 10 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 tha t currently use the feature. Use FILE_IDEX instead. 8308 10 USER_ID will be removed from a future version of SQL Server. Avo id using this feature in new development work, and plan to modify applications t hat currently use the feature. Use DATABASE_PRINCIPAL_ID instead. 8310 16 Cannot create (or open) named file mapping object '%ls'. SQL Ser ver performance counters are disabled. 8311 16 Unable to map view of file mapping object '%ls' into SQL Server process address space. SQL Server performance counters are disabled. 8312 16 Cannot create (or open) named mutex '%ls'. SQL Server performanc e counters are disabled. 8313 16 Error in mapping SQL Server performance object/counter indexes t o object/counter names. SQL Server performance counters are disabled. 8314 16 SQL Server performance object '%ls' not found in registry. SQL S erver performance counters are disabled. 8315 16 SQL Server performance counter '%ls' not found in registry. SQL Server performance counters are disabled. 8316 16 Cannot open registry key 'HKLM\%ls'. SQL Server performance coun ters are disabled. 8317 16 Cannot query value '%ls' associated with registry key 'HKLM\%ls' . SQL Server performance counters are disabled. 8318 16 There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters are disabled. 8319 16 Windows kernel object '%ls' already exists. It's not owned by th e SQL Server service account. SQL Server performance counters are disabled. 8320 10 @@REMSERVER will be removed in a future version of SQL Server. A void using this feature in new development work, and plan to modify applications that currently use the feature. Use linked servers and linked server stored pro cedures instead. 8350 10 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 dep recated. These hints have no effect in this location. Microsoft recommends that you remove these hints from this statement. Support for these hints in this loca tion will be removed in a future version of SQL Server. 8351 16 A trace control request could not be processed because invalid p arameters were specified when events were registered. Confirm that the parameter s are within valid ranges. 8352 16 Cannot find the requested trace template: id = %ls. 8353 16 Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server. 8354 16 Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls. 8355 16 Server-level event notifications can not be delivered. Either Se rvice Broker is disabled in msdb, or msdb failed to start. Event notifications i n other databases could be affected as well. Bring msdb online, or enable Servic e Broker. 8356 16 Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future. 8357 16 Event Tracing for Windows (ETW) failed to send event. This may b e due to low resource conditions. The same send failure may not be reported in t

he future. 8358 16 Event Tracing for Windows (ETW) failed to send event. Event mess age size exceeds limit. The same send failure may not be reported in the future. 8359 16 SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported in the future. 8360 16 SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future . 8379 10 Old style RAISERROR (Format: RAISERROR integer string) will be r emoved in the next version of SQL Server. Avoid using this in new development wo rk, and plan to modify applications that currently use it to use new style RAISE RROR. 8380 10 SQLOLEDB is no longer a supported provider. Please use SQL Nativ e Client (SQLNCLI) to connect to SQL Server using linked server '%.*ls'. 8381 10 SQLOLEDB is no longer a supported provider. Please use SQL Nativ e Client (SQLNCLI) for ad hoc connection to SQL Server. 8382 10 Specifying table hints without using a WITH keyword is a depreca ted feature and will be removed in a future version. 8383 10 Specifying HOLDLOCK as a table hint without parentheses is a dep recated feature and will be removed in the next version of SQL Server. 8384 10 Use of space as a separator for table hints is a deprecated feat ure and will be removed in a future version. Use a comma to separate individual table hints. 8385 10 The select list of an aggregate indexed view must contain count_ big(*) in 90 compatibility mode and higher. 8386 10 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 s tatement to remove the use of this hint. 8387 10 The indirect application of table hints to an invocation of a mu lti-statement table-valued function (TVF) through a view will be removed in a fu ture version of SQL Server. Remove hints on references to view "%.*ls" because i t references a multi-statement TVF. 8388 10 The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 8389 10 The ALL permission will be removed in a future version of SQL Se rver. Avoid using this permission in new development work and plan to modify app lications that currently use it. 8390 10 The '::' function calling syntax will be removed in a future ver sion of SQL Server. Replace it with "sys.". 8391 10 The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX <1p-name> ON {<3p-table-name> | <3p-view-name> } 8393 10 The ability to not specify a column name when the datatype is ti mestamp will be removed in a future version of SQL Server. Avoid using this feat ure in new development work, and plan to modify applications that currently use it. 8394 10 Usage of deprecated index option syntax. The deprecated relation al index option syntax structure will be removed in a future version of SQL Serv er. Avoid using this syntax structure in new development work, and plan to modif y applications that currently use the feature. 8396 10 %ls will be removed in a future version of SQL Server. Avoid usi ng this feature in new development work, and plan to modify applications that cu rrently use it. Use %ls instead. 8397 10 The TEXT, NTEXT, and IMAGE data types will be removed in a futur e version of SQL Server. Avoid using them in new development work, and plan to m odify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types instead. 8398 10 The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

8399 10 %ls will be removed in a future version of SQL Server. Avoid usi ng this feature in new development work, and plan to modify applications that cu rrently use it. 8401 16 This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue '%.* ls'. 8402 16 The data type of the '%S_MSG' in the '%S_MSG' statement must be %s. The %s data type is not allowed. 8403 16 The message type '%.*ls' is specified more than once. Remove th e duplicate message type. 8404 16 The service contract '%.*ls' is specified more than once. Remov e the duplicate service contract. 8405 16 An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State : %i. 8406 16 The dialog lifetime can not be NULL. Specify a valid dialog life time value from %d to %d. 8407 16 Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Serv ice Broker endpoint. 8408 16 Target service '%.*ls' does not support contract '%.*ls'. 8409 16 This message could not be delivered because the targeted service does not support the service contract. Targeted service: '%.*ls', service contr act: '%.*ls'. 8410 16 The conversation timer cannot be set beyond the conversation's l ifetime. 8411 16 The dialog lifetime value of %d is outside the allowable range o f %d to %d. Specify a valid dialog lifetime value. 8412 16 The syntax of the service name '%.*ls' is invalid. 8413 16 The syntax of the broker instance '%.*ls' is invalid. The specif ied broker instance is too long, the maximum size is 256 bytes. 8414 16 The conversation group ID '%.*ls' is invalid in this context. Sp ecify a different conversion group ID. 8415 16 The activated task was aborted because the invoked stored proced ure '%ls' did not issue COMMIT or ROLLBACK on one or more transactions that it b egun. 8417 16 The service contract name is NULL. Specify a service contract n ame. 8418 16 The conversation handle is missing. Specify a conversation handl e. 8419 16 Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL. 8420 16 The conversation group is missing. Specify a conversation group. 8421 16 The service name is missing. Specify a service name. 8422 16 The error description is missing. Specify a description of the e rror. 8423 16 The service "%.*ls" is not found. 8424 16 The error code and error description are missing. Specify both t he error code and description of the error. 8425 16 The service contract '%.*ls' is not found. 8426 16 The conversation handle "%.*ls" is not found. 8427 16 The conversation endpoint is not in a valid state for END CONVER SATION. The current endpoint state is '%ls'. 8428 16 The message type "%.*ls" is not found. 8429 16 The conversation endpoint is not in a valid state for SEND. The current endpoint state is '%ls'. 8430 16 The message body failed the configured validation. 8431 16 The message type '%.*ls' is not part of the service contract. 8432 16 The message cannot be sent because the message type '%.*ls' is m arked SENT BY TARGET in the contract, however this service is an Initiator.

8433 16 The message body may not be NULL. A zero-length UNICODE or bina ry string is allowed. 8434 16 The message cannot be sent because the message type '%.*ls' is m arked SENT BY INTITIATOR in the contract, however this service is a Target. 8435 16 The conversation handle "%.*ls" at position %d is not found. 8436 16 The conversation group "%.*ls" is not found. 8437 16 The message received was sent by a Target service, but the messa ge type '%.*ls' is marked SENT BY INITIATOR in the contract. 8438 16 The conversation endpoint is not in a valid state for MOVE CONVE RSATION. The current endpoint state is '%ls'. 8439 16 The destination conversation group '%.*ls' is invalid. 8440 23 The conversation group exists, but no queue exists. Possible da tabase corruption. Run DBCC CHECKDB. 8441 16 The conversation handle at position %d is missing. Specify a con versation handle. 8442 16 There is no Service Broker active in the database. Change to a d atabase context that contains a Service Broker. 8443 23 The conversation with ID '%.*ls' and initiator: %d references a missing conversation group '%.*ls'. Run DBCC CHECKDB to analyze and repair the d atabase. 8444 23 The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB. 8445 16 The conversation handle '%ls' is referencing an invalid conversa tion ID '%ls', initiator: %d. 8447 16 A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations. 8450 16 Assignments in the RECEIVE projection are not allowed in conjunc tion with the INTO clause. 8451 16 The conversation handle '%.*ls' at position %d appears more than once. 8457 16 The message received was sent by the initiator of the conversati on, but the message type '%.*ls' is marked SENT BY TARGET in the contract. 8458 16 The conversation endpoint is not in a valid state for BEGIN CONV ERSATION TIMER. The current endpoint state is '%ls'. 8459 16 The message size, including header information, exceeds the maxi mum allowed of %d. 8460 16 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation handle '%ls'. 8461 23 An internal service broker error detected. Possible database co rruption. Run DBCC CHECKDB. 8462 16 The remote conversation endpoint is either in a state where no m ore messages can be exchanged, or it has been dropped. 8463 16 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. I f the problem persists, the database may be damaged. To recover the database, re store the database from a clean backup. If no clean backup is available, conside r running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the dat abase. 8468 16 Underlying service has been altered. 8469 16 Remote service has been altered. 8470 16 Remote service has been dropped. 8471 16 An SNI call failed during a Service Broker/Database Mirroring tr ansport operation. SNI error '%ls'. 8472 16 The remote service has sent a message that contains invalid head er fields. 8475 16 The conversation endpoint with ID '%ls' and is_initiator: %d has been dropped. 8477 16 An internal Service Broker error occurred (error = 0x%08x). This error indicates a serious problem with SQL Server. Check the SQL Server error l

og and the Windows event logs for information pointing to possible hardware prob lems. The database may have been damaged. To recover the database, restore the d atabase from a clean backup. If no clean backup is available, consider running D BCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database. 8479 16 Used by test in failpoint simulation. 8487 16 The remote service contract has been dropped. 8489 16 The dialog has exceeded the specified LIFETIME. 8490 16 Cannot find the remote service '%.*ls' because it does not exist . 8492 16 The service contract '%.*ls' must have at least one message SENT BY INITIATOR or ANY. 8493 16 The alter of service '%.*ls' must change the queue or at least o ne contract. 8494 16 You do not have permission to access the service '%.*ls'. 8495 16 The conversation has already been acknowledged by another instan ce of this service. 8498 16 The remote service has sent a message of type '%.*ls' that is no t part of the local contract. 8499 16 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 wi th Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 8501 16 MSDTC on server '%.*ls' is unavailable. 8502 20 Unknown token '0x%x' received from Microsoft Distributed Transac tion Coordinator (MS DTC) . 8504 20 The import buffer for this transaction is not valid. 8506 20 Cannot change transaction state from %hs to %hs. The change requ ested is not valid. 8508 10 QueryInterface failed for "%ls": %ls. 8509 20 Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls. 8510 20 Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager fo r this transaction. The transaction may have been stopped by the client or the r esource manager. 8511 16 Unknown isolation level 0x%x requested from Microsoft Distribute d Transaction Coordinator (MS DTC). 8512 20 Microsoft Distributed Transaction Coordinator (MS DTC) commit tr ansaction acknowledgement failed: %hs. 8513 20 Microsoft Distributed Transaction Coordinator (MS DTC) end trans action acknowledgement failed: %hs. 8514 20 Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE a cknowledgement failed: %hs. 8515 20 Microsoft Distributed Transaction Coordinator (MS DTC) global st ate is not valid. 8517 20 Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls. 8518 16 Microsoft Distributed Transaction Coordinator (MS DTC) BEGIN TRA NSACTION failed: %ls. 8519 16 Current Microsoft Distributed Transaction Coordinator (MS DTC) t ransaction must be committed by remote client. 8520 16 Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: %ls. 8521 20 This awakening state is not valid: slept in %hs; awoke in %hs. 8522 20 Microsoft Distributed Transaction Coordinator (MS DTC) has stopp ed this transaction. 8523 15 PREPARE TRAN statement not allowed on MSDTC transaction. 8524 16 The current transaction could not be exported to the remote prov ider. It has been rolled back. 8525 16 Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.

8526 16 Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint. 8527 16 An attempt to create a distributed transaction export token fail ed with this error: %ls. Contact your Microsoft Distributed Transaction Coordina tor (MS DTC) system administrator. 8528 16 The commit of the Kernel Transaction Manager (KTM) transaction f ailed: %d. 8529 16 Unable to extract the Kernel Transaction Manager (KTM) transacti on handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transa ction: 0x%x. 8530 16 The Windows kernel transaction manager creation failed: 0x%x. 8531 16 The Windows kernel transaction manager failed to create the enli stment: 0x%08x. 8532 20 Error while reading resource manager notification from Kernel Tr ansaction Manager (KTM): %d. 8533 20 Error while waiting for communication from Kernel Transaction Ma nager (KTM): %d. 8534 21 The KTM RM for this database, %ls, failed to start: %d. 8535 16 A savepoint operation in the Windows transactional file system f ailed: 0x%x. 8536 16 Only single DB updates are allowed with FILESTREAM operations. 8537 16 This transaction was aborted by Kernel Transaction Manager (KTM) . 8538 16 The current isolation level is not supported by the FILESTREAM 0 x%x. 8539 10 The distributed transaction with UOW %ls was forced to commit. M S DTC became temporarily unavailable and forced heuristic resolution of the tran saction. This is an informational message only. No user action is required. 8540 10 The distributed transaction with UOW %ls was forced to rollback. 8541 10 System process ID %d tried to terminate the distributed transact ion with Unit of Work ID %ls. This message occurs when the client executes a KIL L statement on the distributed transaction. 8542 10 Spid %d tried to commit the distributed transaction with UOW %ls . 8543 10 Unable to commit a prepared transaction from the Microsoft Distr ibuted Transaction Coordinator (MS DTC). Shutting down server to initiate resour ce manager (RM) recovery. When the RM recovers, it will query the transaction ma nager about the outcome of the in-doubt transaction, and commit or roll back acc ordingly. 8544 10 Unknown status of commit of a two-phase commit transaction. Shut ting down server. Restart server to complete recovery. 8545 10 Unknown status '%d' from Reenlist call in rm_resolve. 8546 10 Unable to load Microsoft Distributed Transaction Coordinator (MS DTC) library. This error indicates that MS DTC is not installed. Install MS DTC to proceed. 8547 10 Resource Manager Creation Failed: %ls 8548 10 DTC not initialized because it's unavailable 8549 10 GetWhereaboutsSize call failed: %ls 8550 10 MS DTC initialization failed because the transaction manager add ress is invalid. The protocol element used to carry address information may be t oo large. A network protocol analyzer may provide additional information about t he cause. Contact your application support provider or Microsoft Product Support Services. 8551 16 CoCreateGuid failed: %ls. 8552 20 RegOpenKeyEx of \"%ls\" failed: %ls. 8553 20 RegQueryValueEx of \"%hs\" failed: %ls. 8554 20 IIDFromString failed for %hs, (%ls). 8555 10 RegCloseKey failed: %ls 8556 10 Microsoft Distributed Transaction Coordinator (MS DTC) initializ ation failed due to insufficient memory. It may be necessary to change some serv

er configuration options to make more memory available. 8557 10 The Microsoft Distributed Transaction Coordinator (MS DTC) servi ce could not be contacted. If you would like distributed transaction functional ity, please start this service. 8558 20 RegDeleteValue of \"%hs\" failed: %ls. 8560 10 Attempting to recover in-doubt distributed transactions involvin g Microsoft Distributed Transaction Coordinator (MS DTC). This is an information al message only. No user action is required. 8561 10 Recovery of any in-doubt distributed transactions involving Micr osoft Distributed Transaction Coordinator (MS DTC) has completed. This is an inf ormational message only. No user action is required. 8562 10 The connection has been lost with Microsoft Distributed Transact ion Coordinator (MS DTC). Recovery of any in-doubt distributed transactions invo lving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user ac tion is required. 8563 10 An error occurred while trying to determine the state of the RPC SS service. A call to "%ls" returned: %ls. This is an informational message on ly. No user action is required. 8565 16 SQL Server failed to prepare DTC transaction. Failure code: %d. 8601 17 Internal Query Processor Error: The query processor could not ob tain access to a required interface. 8602 16 Indexes used in hints must be explicitly included by the index t uning wizard. 8603 16 Invalid syntax for internal DBCC REPAIR statement. 8604 16 ALTER TABLE SWITCH statement failed. Table '%.*ls' has a column level check constraint '%.*ls' on column '%.*ls' that is not loadable for semant ic validation. 8605 10 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 s pecified in "index create memory (KB)" option because the former has to be small er than the latter. 8606 17 This index operation requires %I64d KB of memory per DOP. The to tal requirement of %I64d KB for DOP of %lu is greater than the sp_configure valu e of %lu KB set for the advanced server configuration option "index create memor y (KB)". Increase this setting or reduce DOP and rerun the query. 8607 16 The table '%.*ls' cannot be modified because one or more non-clu stered indexes reside in a filegroup which is not online. 8608 16 The query could not be completed due to an online index build o peration and must be recompiled. 8616 10 The index hints for table '%.*ls' were ignored because the table was considered a fact table in the star join. 8618 16 The query processor could not produce a query plan because a wor ktable 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 c lause in the query. If the query has a GROUP BY or ORDER BY clause, consider red ucing 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. Not e however that this will change the behavior of the query. 8619 16 The query processor could not produce a query plan because a wor ktable 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 c lause in the query. Resubmit your query without the ROBUST PLAN hint. 8621 16 The query processor ran out of stack space during query optimiza tion. Please simplify the query. 8622 16 Query processor could not produce a query plan because of the hi nts defined in this query. Resubmit the query without specifying any hints and w ithout using SET FORCEPLAN. 8623 16 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 compl

ex 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 er ror, contact Customer Support Services for more information. 8624 16 Internal Query Processor Error: The query processor could not pr oduce a query plan. For more information, contact Customer Support Services. 8625 10 Warning: The join order has been enforced because a local join h int is used. 8628 17 A time out occurred while waiting to optimize the query. Rerun t he query. 8630 17 Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x%x). 8631 17 Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it. 8632 17 Internal error: An expression services limit has been reached. P lease look for potentially complex expressions in your query, and try to simplif y them. 8633 16 The query processor could not produce a query plan because distr ibuted query does not support materializing intermediate results with default in DML queries over remote sources. Try to use actual default values instead of de fault or split the update into multiple statements, one only containing the DEFA ULT assignment, the other with the rest. 8634 17 The query processor received an error from a cluster communicati on layer. 8635 16 The query processor could not produce a query plan for a query w ith a spatial index hint. Reason: %S_MSG. Try removing the index hints or remo ving SET FORCEPLAN. 8636 16 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 fo r distributed queries. 8637 16 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 waitin g 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 o r a manual query rewrite. 8642 17 The query processor could not start the necessary thread resourc es for parallel query execution. 8644 16 Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine. 8645 17 A timeout occurred while waiting for memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query. 8646 21 Unable to find index entry in index ID %d, of table %d, in datab ase '%.*ls'. The indicated index is corrupt or there is a problem with the curre nt update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, co ntact product support. 8648 20 Could not insert a row larger than the page size into a hash tab le. Resubmit the query using the ROBUST PLAN optimization hint. 8649 17 The query has been canceled because the estimated cost of this q uery (%d) exceeds the configured threshold of %d. Contact the system administrat or. 8651 17 Could not perform the operation because the requested memory gra nt was not available in resource pool '%ls' (%ld). Rerun the query, reduce the query load, or check resource governor configuration setting. 8653 16 The query processor is unable to produce a plan for the table or view '%.*ls' because the table resides in a filegroup which is not online. 8655 16 The query processor is unable to produce a plan because the inde x '%.*ls' on table or view '%.*ls' is disabled. 8656 16 The query processor could not produce a query plan. Resubmit the query after disabling trace flag %d. 8657 17 Could not get the memory grant of %I64d KB because it exceeds th

e maximum configuration limit in workload group '%ls' (%ld) and resource pool '% ls' (%ld). Contact the server administrator to increase the memory usage limit. 8658 17 Cannot start the columnstore index build because it requires at least %I64d KB, while the maximum memory grant is limited to %I64d KB per query in workload group '%ls' (%ld) and resource pool '%ls' (%ld). Retry after modifyi ng columnstore index to contain fewer columns, or after increasing the maximum m emory grant limit with Resource Governor. 8659 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e for clustered indexes on aggregate views without GROUP BY, the only distributi on option supported is DISTRIBUTION=NONE. 8660 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e the select list of the view definition does not include all columns in the GRO UP BY clause. Consider adding these columns to the select list. 8661 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e the index key includes columns that are not in the GROUP BY clause. Consider e liminating columns that are not in the GROUP BY clause from the index key. 8662 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e the view references an unknown value (SUM aggregate of nullable expression). C onsider referencing only non-nullable values in SUM. ISNULL() may be useful for this. 8663 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e its select list does not include COUNT_BIG(*). Consider adding COUNT_BIG(*) to the select list. 8665 16 Cannot create the clustered index "%.*ls" on view "%.*ls" becaus e no row can satisfy the view definition. Consider eliminating contradictions fr om the view definition. 8668 16 Cannot create the clustered index '%.*ls' on view '%.*ls' becaus e the select list of the view contains an expression on result of aggregate func tion or grouping column. Consider removing expression on result of aggregate fun ction or grouping column from select list. 8669 16 The attempt to maintain the indexed view "%.*ls" failed because it contains an expression on aggregate results, or because it contains a ranking or aggregate window function. Consider dropping the clustered index on the view , or changing the view definition. 8670 16 Query optimizer reached the internal limit of the maximum number of views that can be used during optimization. 8671 16 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 wi thout the ignore_dup_key index option. 8672 16 The MERGE statement attempted to UPDATE or DELETE the same row m ore 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 r ow, or use the GROUP BY clause to group the source rows. 8673 16 A MERGE statement is not valid if it triggers both the 'ON DELET E SET NULL' and 'ON UPDATE CASCADE' actions for a referential integrity constrai nt. Modify the actions performed by the MERGE statement to ensure that it does n ot trigger both these actions for a referential integrity constraint. 8674 16 The query processor is unable to produce a plan. The table '%.*l s' is unavailable because the heap is corrupted. Take the database offline to re build the table and heap, and then run the query processor again. 8675 17 A timeout occurred while waiting for remote memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query. 8676 16 Invalid plan. 8680 17 Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase. 8681 17 Internal Query Processor Error: The query processor encountered an unexpected error during processing. [%ls] 8682 16 SELECT via cursor failed because in XML plan provided to USE PLA N hint, neither Populate nor Fetch plans are provided, and at least one must be

present. For best likelihood of successful plan forcing, use an XML cursor plan captured from SQL Server without modification. 8683 16 Could not force query plan because XML showplan provided in USE PLAN hint contains invalid Star Join specification. Consider specifying a USE PL AN hint that contains an unmodified XML showplan produced by SQL Server. This ma y allow you to force the plan. 8684 16 A query plan could not be found because optimizer exceeded numbe r of allowed operations while searching for plan specified in USE PLAN hint. Fir st consider removing USE PLAN hint. Then if necessary consider (1) updating stat istics, (2) using other hints such as join hints, index hints, or the OPTIMIZE F OR hint, (3) rewriting query or breaking it down into two or more separate queri es. 8685 16 Query cannot be compiled because <CursorStmt> element appears in XML plan provided to USE PLAN but USE PLAN was applied to a non-cursor statemen t. Consider using an XML plan obtained from SQL Server for statement without mod ification. 8686 16 Cursor plan forcing failed because input plan has more than one <Operation> node with OperationType=%ls. Consider using an XML cursor plan captu red from SQL Server without modification. 8687 16 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. Con sider removing USE PLAN hint and updating statistics or using different hints to influence query plan choice. 8688 16 Cursor plan forcing failed because in XML plan provided to USE P LAN, required element %ls is missing under <CursorPlan> element. Consider using an XML cursor plan captured from SQL Server without modification. 8689 16 Database '%.*ls', specified in the USE PLAN hint, does not exist . Specify an existing database. 8690 16 Query cannot be compiled because USE PLAN hint conflicts with hi nt %ls. Consider removing hint %ls. 8691 16 Query cannot be compiled because USE PLAN hint conflicts with SE T %ls ON. Consider setting %ls OFF. 8693 16 Cannot compile query because combination of LogicalOp = '%ls', P hysicalOp = '%ls', and sub_element = '%ls' under RelOp element in XML plan in US E PLAN hint is not valid. Use a recognized combination instead. Consider using a n automatically generated XML plan without modification. 8694 16 Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint. 8695 16 Cannot execute query because of incorrectly formed XML plan in U SE PLAN hint. Verify that XML plan is a legal plan suitable for plan forcing. Se e Books Online for additional details. 8696 16 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 Spoo l 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 s ub-element. Consider using unmodified XML showplan as USE PLAN hint. 8697 16 Cannot run query because in XML plan provided to USE PLAN, eleme nt %ls must have %d %ls nodes as children, but has %d. 8698 16 Query processor could not produce query plan because USE PLAN hi nt contains plan that could not be verified to be legal for query. Remove or rep lace 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 Ser ver for the same query. 8699 16 Cannot run query because it contains more than one USE PLAN hint . Use at most one USE PLAN hint. 8709 16 Error due to negative or NULL window delimiter. 8710 16 Aggregate functions that are used with CUBE, ROLLUP, or GROUPING SET queries must provide for the merging of subaggregates. To fix this problem, remove the aggregate function or write the query using UNION ALL over GROUP BY

clauses. 8711 16 Multiple ordered aggregate functions in the same scope have mutu ally incompatible orderings. 8712 16 Index '%.*ls', specified in the USE PLAN hint, does not exist. S pecify an existing index, or create an index with the specified name. 8713 16 Could not force query plan because of a problem in an indexed vi ew referenced in the plan. 8720 15 Cannot execute query. There is more than one TABLE HINT clause s pecified for object '%.*ls'. Use at most one such TABLE HINT clause per table re ference. 8721 15 Cannot execute query. TABLE HINT in the OPTION clause leads to a mbiguous reference for object '%.*ls'. Consider USE PLAN query hint instead. 8722 15 Cannot execute query. Semantic affecting hint '%.*ls' appears in the '%.*ls' clause of object '%.*ls' but not in the corresponding '%.*ls' claus e. Change the OPTION (TABLE HINTS...) clause so the semantic affecting hints ma tch the WITH clause. 8723 15 Cannot execute query. Object '%.*ls' is specified in the TABLE H INT clause, but is not used in the query or does not match the alias specified i n the query. Table references in the TABLE HINT clause must match the WITH claus e. 8724 15 Cannot execute query. Table-valued or OPENROWSET function '%.*ls ' cannot be specified in the TABLE HINT clause. 8725 17 Subproc thread aborted during parallel query execution. 8726 16 Input parameter of %.*ls function must be a constant. 8727 16 Input parameter of percentile function is outside of range [0, 1 ]. 8728 16 ORDER BY list of RANGE window frame cannot contain expressions o f LOB type. 8729 16 ORDER BY list of RANGE window frame has total size of %lu bytes. Largest size supported is %lu bytes. 8730 16 Offset parameter for Lag and Lead functions cannot be a negative value. 8731 15 REDISTRIBUTE and REDUCE hints expect the first join condition to be an equality comparison of columns. Modify the query and re-run it. 8732 15 REPLICATE and REDUCE hints can only be used with inner joins. Mo dify the query and re-run it. 8901 16 Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object. 8902 17 Memory allocation error during DBCC processing. 8903 16 Extent %S_PGID in database ID %d is allocated in both GAM %S_PGI D and SGAM %S_PGID. 8904 16 Extent %S_PGID in database ID %d is allocated by more than one a llocation object. 8905 16 Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it. 8906 16 Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags '%hs'. 8907 16 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 mor e information about troubleshooting DBCC errors on indexed views, see SQL Server Books Online. 8908 16 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 mor e information about troubleshooting DBCC errors on spatial indexes, XML indexes, and indexed views, see SQL Server Books Online. 8909 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page ID %S_PGID contains an incorrect page ID in i ts page header. The PageId in the page header = %S_PGID.

8910 16 Page %S_PGID in database ID %d is allocated to both object ID %d , index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), and object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 8911 10 The error has been repaired. 8912 10 %.*ls fixed %d allocation errors and %d consistency errors in da tabase '%ls'. 8913 16 Extent %S_PGID is allocated to '%ls' and at least one other obje ct. 8914 10 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). Expect ed value %hs, actual value %hs. 8915 10 File %d (number of mixed extents = %I64d, mixed pages = %I64d). 8916 10 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), data extents %I64d, pages %I64d, mixed extent pages %I64d. 8917 10 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d. 8918 10 (number of mixed extents = %I64d, mixed pages = %I64d) in this database. 8919 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls): The record count in the header (%d) does not match the number o f records (%d) found on page %S_PGID. 8920 16 Cannot perform a %ls operation inside a user transaction. Termin ate the transaction and reissue the statement. 8921 16 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors. 8922 10 Could not repair this error. 8923 10 The repair level on the DBCC statement caused this repai r to be bypassed. 8924 10 Repairing this error requires other errors to be correct ed first. 8925 16 Table error: Cross object linkage: Page %S_PGID, slot %d, in obj ect ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), re fers to page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 8926 16 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->nex t in object %d, index %d, partition %I64d, AU %I64d (%.*ls), refer to page %S_PG ID but are not in the same object. 8927 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls): The ghosted record count in the header (%d) does not match the number of ghosted records (%d) found on page %S_PGID. 8928 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls): Page %S_PGID could not be processed. See other errors for deta ils. 8929 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I6 4d (type %.*ls): Errors found in off-row data with ID %I64d owned by %ls record identified by %.*ls 8930 16 Database error: Database %d has inconsistent metadata. This erro r cannot be repaired and prevents further DBCC processing. Please restore from a backup. 8931 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from parent %S_PGID. 8932 16 Could not find filegroup ID %d in sys.filegroups for database '% ls'. 8933 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The low key value on page %S_PGID (level %d) is no t >= the key value in the parent %S_PGID slot %d.

8934 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The high key value on page %S_PGID (level %d) is n ot less than the low key value in the parent %S_PGID, slot %d of the next page % S_PGID. 8935 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c 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 th is page. 8936 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_ PGID, but %S_PGID->Prev = %S_PGID. 8937 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d. 8938 16 Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d. 8939 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Values are %ld and %ld. 8940 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Address 0x%x is not aligned. 8941 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x is invalid. 8942 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x overlaps with the prior row. 8943 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, row ex tends into free space at 0x%x. 8944 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls), page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld. 8945 16 Table error: Object ID %d, index ID %d will be rebuilt. 8946 16 Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page. 8947 16 Table error: Multiple IAM pages for object ID %d, index ID %d, p artition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID. 8948 16 Database error: Page %S_PGID is marked with the wrong type in PF S page %S_PGID. PFS status 0x%x expected 0x%x. 8949 10 %.*ls fixed %d allocation errors and %d consistency errors in ta ble '%ls' (object ID %d). 8950 16 %.*ls fixed %d allocation errors and %d consistency errors not a ssociated with any single object. 8951 16 Table error: table '%ls' (ID %d). Data row does not have a match ing index row in the index '%ls' (ID %d). Possible missing or invalid keys for t he index row matching: 8952 16 Table error: table '%ls' (ID %d). Index row in index '%ls' (ID % d) does not match any data row. Possible extra or invalid keys for: 8953 10 Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page % S_PGID, slot %d. 8954 10 %.*ls found %d allocation errors and %d consistency errors not a ssociated with any single object. 8955 16 Data row (%d:%d:%d) identified by (%ls) with index values '%ls'. 8956 16 Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls). 8957 10 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and r

epaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls 8958 10 %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls). 8959 16 Table error: IAM page %S_PGID for object ID %d, index ID %d, par tition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID. 8960 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid co mplex column. 8961 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d does not match its reference from page %S_PGID, slot %d. 8962 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d has incorrect node type %d. 8963 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d has type %d. It cannot be placed on a page of type %d. 8964 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d is not referenced. 8965 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan . 8966 22 Unable to read and latch page %S_PGID with latch type %ls. %ls f ailed. 8967 16 An internal error occurred in DBCC that prevented further proces sing. Contact Customer Support Services. 8968 16 Table error: %ls page %S_PGID (object ID %d, index ID %d, partit ion ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this data base. 8969 16 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 pag e %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID. 8970 16 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 creat ed NOT NULL, but is NULL in the row. 8971 16 Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S _PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d 8972 16 Forwarded row referenced by more than one row. Object ID %d, par tition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorre ctly points to the forwarded row page %S_PGID, slot %d, which correctly refers b ack to page %S_PGID, slot %d. 8973 16 CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice. 8974 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, te xt ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d. 8975 10 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 f or more information on this error. 8976 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors. 8977 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered. 8978 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo

c unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem. 8979 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (un known) and previous (page %S_PGID) nodes. Possible bad root entry in system cata log. 8980 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child p age %S_PGID and previous child %S_PGID, but they were not encountered. 8981 16 Table error: Object ID %d, index ID %d, partition ID %I64d, allo c unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID . Neither %S_PGID nor its parent were encountered. Possible bad chain linkage. 8982 16 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 %.*l s) but is not in the same index. 8983 10 File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d. 8984 16 Table error: object ID %d, index ID %d, partition ID %I64d. A ro w should be on partition number %d but was found in partition number %d. Possibl e extra or invalid keys for: 8985 16 Could not locate file '%.*ls' for database '%.*ls' in sys.databa se_files. The file either does not exist, or was dropped. 8986 16 Too many errors found (%d) for object ID %d. To see all error me ssages rerun the statement using "WITH ALL_ERRORMSGS". 8987 16 No help available for DBCC statement '%.*ls'. 8988 16 Row (%d:%d:%d) identified by (%ls). 8989 10 %.*ls found %d allocation errors and %d consistency errors in da tabase '%ls'. 8990 10 %.*ls found %d allocation errors and %d consistency errors in ta ble '%ls' (object ID %d). 8991 16 0x%p to 0x%p is not a valid address range. 8992 16 Check Catalog Msg %d, State %d: %.*ls 8993 16 Object ID %d, forwarding row page %S_PGID, slot %d points to pag e %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error. 8994 16 Object ID %d, forwarded row page %S_PGID, slot %d should be poin ted to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row . Possible allocation error. 8995 16 System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d. 8996 16 IAM page %S_PGID for object ID %d, index ID %d, partition ID %I6 4d, alloc unit ID %I64d (type %.*ls) controls pages in filegroup %d, that should be in filegroup %d. 8997 16 Service Broker Msg %d, State %d: %.*ls 8998 16 Page errors on the GAM, SGAM, or PFS pages prevent allocation in tegrity checks in database ID %d pages from %S_PGID to %S_PGID. See other errors for cause. 8999 10 Database tempdb allocation errors prevent further %ls processing . 9001 21 The log for database '%.*ls' is not available. Check the event l og for related error messages. Resolve any errors and restart the database. 9002 17 The transaction log for database '%ls' is full due to '%ls'. 9003 20 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 (.l df) does not match the data file (.mdf). If this error occurred during replicati on, re-create the publication. Otherwise, restore from backup if the problem res ults in a failure during startup. 9004 21 An error occurred while processing the log for database '%.*ls'. If possible, restore from backup. If a backup is not available, it might be ne cessary to rebuild the log.

9005 16 Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid. 9006 10 Cannot shrink log file %d (%s) because total number of logical l og files cannot be fewer than %d. 9007 10 Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file. 9008 10 Cannot shrink log file %d (%s) because the logical log file loca ted at the end of the file is in use. 9009 10 Cannot shrink log file %d (%s) because of minimum log space requ ired. 9010 14 User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission 9011 14 User does not have permission to query backup files with the vir tual table DBLog. Only members of the sysadmin fixed server role has this permis sion 9012 10 There have been %d misaligned log IOs which required falling bac k to synchronous IO. The current IO is on file %ls. 9013 10 The tail of the log for database %ls is being rewritten to match the new sector size of %d bytes. %d bytes at offset %I64d in file %ls will be written. 9014 21 An error occurred while processing the log for database '%ls'. T he log block version %d is unsupported. This server supports log version %d to % d. 9015 24 The log record at LSN %S_LSN is corrupted. 9016 21 An error occurred while processing the log for database '%.*ls'. The log block could not be decrypted. 9017 10 Database %ls has more than %d virtual log files which is excessi ve. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number o f virtual log files. 9018 16 The log for database '%ls' does not allow user writes. 9019 21 The virtual log file sequence 0x%08x at offset 0x%016I64x bytes in file '%ls' is active and cannot be overwritten with sequence 0x%08x for datab ase '%ls'. 9020 16 The log for database '%ls' failed to grow while shrink in progre ss. Please retry. 9021 16 Cannot accept virtual log file sequence 0x%08x for database '%ls ' because file %d does not exist yet. 9022 14 The log can not be initialized because the log files are not ful ly formatted. 9023 16 The log for database '%ls' cannot be shrunk until all secondarie s have moved past the point where the log was added.. 9100 23 Possible index corruption detected. Run DBCC CHECKDB. 9101 16 auto statistics internal 9104 16 auto statistics internal 9105 16 The provided statistics stream is corrupt. 9106 16 Histogram support not allowed for input data type 0x%08x. 9107 16 The name, '%.*ls', is invalid. The suffix '_readonly_database_st atistic' is reserved. Select another name without using the reserved suffix. 9201 10 %d active query notification subscription(s) in database '%.*ls' owned by security identification number '%.*ls' were dropped. 9202 16 The query notification subscription message is invalid. 9204 16 The query notification subscription timeout is invalid. The allo wed range is 1 through 2147483647. 9205 16 User "%.*ls" does not have permission to request query notificat ion subscriptions on database "%.*ls". 9206 16 The query notification subscription "%ld" cannot be deleted beca use it does not exist or it has already been fired. 9207 10 The query notification dialog on conversation handle '%.*ls' clo

sed due to the following error: '%.*ls'. 9208 16 Query notification subscription could not get dialog endpoint. C ould not open service broker dialog for service name '%.*ls' of broker instance '%.*ls'. 9209 16 Query notification subscription could not begin dialog with serv ice name '%.*ls' of broker instance '%.*ls'. 9210 10 Query notification delivery could not send message on dialog '%. *ls'. Delivery failed for notification '%.*ls' because of the following error in service broker: '%.*ls'. 9211 10 Failed to check for pending query notifications in database "%d" because of the following error when opening the database: '%.*ls'. 9213 10 Query notification subscription could not access database with i d %d. Could not open broker dialog for service name '%.*ls' of broker instance ' %.*ls'. 9214 16 The query notification delivery failed to decode the error messa ge from the Service Broker. 9215 16 Query notification delivery failed to encode message. Delivery f ailed for notification '%.*ls'. 9216 10 Failed to delete the expired query notification subscription "%d ". 9217 10 Failed to drop the unused internal query notification table "%d" in database "%d". 9218 16 Query notifications reached the internal limit of the maximum nu mber of objects. 9219 16 The query notification subscriptions cleanup operation failed. S ee previous errors for details. 9220 10 Query notification dialog on conversation handle '%.*ls' closed due to an unknown service broker error. 9221 10 Query notification delivery could not get dialog endpoint for di alog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker '%.*ls'. 9222 16 Internal query notification table has an outdated schema and the table has been dropped. Query notification cleanup has not been performed for t his table. 9223 10 %d active query notification subscription(s) owned by security i dentification number '%.*ls' were dropped. 9224 10 Query notification delivery could not access database with id %d . Delivery failed for notification '%.*ls'. 9225 16 The notification options identifier string has %d characters. Th e maximum allowed length is %d characters. 9226 16 A string value within the notification options identifier is too long. String with prefix '%.*ls' must be %d characters or less. 9227 16 Unmatched quote in notification options identifier string. 9228 16 Name expected in notification options identifier option. 9229 16 Unknown option name '%.*ls' present in notification options iden tifier. The following are valid option names: 'Service', 'Broker Instance', 'Loc al Database'. Option names cannot be quoted. 9230 16 Option '%ls' was specified multiple times in the notification op tions identifier. 9231 16 An equal (=) character was expected after the option name. Found '%.*ls' instead. 9232 16 A semicolon (;) must be use to separate options in a notificatio n options identifier. String '%.*ls' was found following an option. 9233 16 The option 'Service' must be specified in the notification optio ns identifier. 9234 16 The options 'Broker Instance' and 'Local Database' were both spe cified in the notification options identifier. 9235 16 Value missing for option '%ls' in notification options identifie r. 9236 16 Database %.*ls is not a valid local database.

9237 16 Database %.*ls is not a valid broker database. 9238 16 Query notification subscriptions are not allowed under an active application role context. Consider re-issuing the request without activating th e application role. 9239 16 Internal query notifications error: The garbage collector correc ted an inconsistency. 9240 10 Service broker dialog '%.*ls' could not be closed due to a broke r error in database with id '%d' because of the following error in service broke r: '%.*ls'. 9241 16 Service broker dialog '%.*ls' could not be closed because the da tabase with id '%d' is not available. Consider closing the dialogs manually once the database is available again. 9242 10 Query notification delivery could not get dialog endpoint for di alog '%.*ls'. Query notification delivery failed because of the following error in service broker: '%.*ls'. See the error log for additional information. 9243 10 Query notification delivery could not send message on dialog '%. *ls'. Query notification delivery failed because of the following error in servi ce broker: '%.*ls'. See the error log for additional information. 9244 16 Query notification cleanup could not access metadata for databas e "%d". Check whether the database is successfully restored and online. 9245 16 During the last time interval %d query notification errors were suppressed. 9300 16 %sIn this version of the server, the 'fn:id()' function only acc epts an argument of type 'IDREF *'. 9301 16 %sIn this version of the server, 'cast as <type>%s' is not avail able. Please use the 'cast as <type> ?' syntax. 9302 16 %sThe context item in which the 'fn:id()' function is used must be a node. 9303 16 %sSyntax error near '%ls', expected '%ls'. 9304 16 %sThis version of the server only supports XQuery version '1.0'. 9305 16 %sOnly type names followed by '?' are supported in the target of 'instance of'. 9306 16 %sThe target of 'replace value of' cannot be a union type, found '%ls'. 9308 16 %sThe argument of '%ls' must be of a single numeric primitive ty pe or 'http://www.w3.org/2004/07/xpath-datatypes#untypedAtomic'. Found argument of type '%ls'. 9309 16 %sThe target of 'replace value of' cannot be 'http://www.w3.org/ 2001/XMLSchema#anySimpleType', found '%ls'. 9310 16 %sThe 'with' clause of 'replace value of' cannot contain constru cted XML. 9311 16 %sHeterogeneous sequences are not allowed in '%ls', found '%ls' and '%ls'. 9312 16 %s'%ls' is not supported on simple typed or 'http://www.w3.org/2 001/XMLSchema#anyType' elements, found '%ls'. 9313 16 %sThis version of the server does not support multiple expressio ns or expressions mixed with strings in an attribute constructor. 9314 16 %sCannot implicitly atomize or apply 'fn:data()' to complex cont ent elements, found type '%ls' within inferred type '%ls'. 9315 16 %sOnly constant expressions are supported for the name expressio n of computed element and attribute constructors. 9316 16 %sCannot use 'xmlns' in the name expression of computed attribut e constructor. 9317 16 %sSyntax error near '%ls', expected string literal. 9318 16 %sSyntax error at source character '0x%02x' near '%ls', expected string literal. 9319 16 %sStatic simple type validation: Invalid simple type value '%ls' . 9320 16 %sThe result of applying the 'parent' axis on the document node is statically 'empty'.

9321 16 %sThe result of applying 'parent::%ls' is statically 'empty'. 9322 16 %sTwo consecutive '-' can only appear in a comment constructor i f they are used to close the comment ('-->'). 9323 16 %sUsing ':' in variable names is not supported in this version o f the server. 9324 16 %sFound '}' without matching '{'. If you want to use the charact ers '{' or '}', you need to escape them as '{{' or '}}' respectively. 9325 16 %sComputed processing instruction constructors are not supported . 9326 16 %sComputed comment constructors are not supported. 9327 16 %sAll prolog entries need to end with ';', found '%ls'. 9328 16 %sType specification expected, found '%ls'. 9330 16 %sOnly comparable types are allowed in '%ls', found '%ls'. 9331 16 %sSyntax error near '%ls', expected '%ls' or '%ls'. 9332 16 %sSyntax error near '%ls', expected 'where', '(stable) order by' or 'return'. 9333 16 %s'//' followed by 'self', 'parent' or 'descendant-or-self' axes is not supported when it encounters simple typed or 'http://www.w3.org/2001/XML Schema#anyType' elements, found '%ls'. 9334 16 %sThe 'form' attribute cannot be specified on a local attribute or element definition that has the 'ref' attribute. Location: '%ls'. 9335 16 %sThe XQuery syntax '%ls' is not supported. 9336 16 %sThe XML Schema syntax '%ls' is not supported. 9337 16 %sThe XML Schema type 'NOTATION' is not supported. 9338 16 %sThe value of a namespace declaration attribute must be a strin g literal. It cannot contain expressions. 9339 16 %sThe 'form' attribute cannot be specified on a global attribute or element definition. Location: '%ls'. 9340 16 %sExplicit import of the current target namespace is invalid. Re ferences to items in the current target namespace that have already been loaded in the schema collection will be resolved implicitly. 9341 16 %sSyntax error near '%ls', expected a step expression. 9342 16 %sAn XML instance is only supported as the direct source of an i nsert using sql:column/sql:variable. 9343 16 %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 collectio n as the context XML instance on which the XML method is being applied to. 9344 16 %sThe SQL type '%s' is not supported with sql:column() and sql:v ariable(). 9400 16 XML parsing: line %d, character %d, unexpected end of input 9401 16 XML parsing: line %d, character %d, unrecognized encoding 9402 16 XML parsing: line %d, character %d, unable to switch the encodin g 9403 16 XML parsing: line %d, character %d, unrecognized input signature 9410 16 XML parsing: line %d, character %d, whitespace expected 9411 16 XML parsing: line %d, character %d, semicolon expected 9412 16 XML parsing: line %d, character %d, '>' expected 9413 16 XML parsing: line %d, character %d, A string literal was expecte d 9414 16 XML parsing: line %d, character %d, equal expected 9415 16 XML parsing: line %d, character %d, well formed check: no '<' in attribute value 9416 16 XML parsing: line %d, character %d, hexadecimal digit expected 9417 16 XML parsing: line %d, character %d, decimal digit expected 9418 16 XML parsing: line %d, character %d, '[' expected 9419 16 XML parsing: line %d, character %d, '(' expected 9420 16 XML parsing: line %d, character %d, illegal xml character 9421 16 XML parsing: line %d, character %d, illegal name character 9422 16 XML parsing: line %d, character %d, incorrect document syntax 9423 16 XML parsing: line %d, character %d, incorrect CDATA section synt

ax 9424 16 XML parsing: 9425 16 XML parsing: n syntax 9426 16 XML parsing: n syntax 9427 16 XML parsing: n syntax 9428 16 XML parsing: n syntax 9429 16 XML parsing: syntax 9430 16 XML parsing: on syntax 9431 16 XML parsing: 9432 16 XML parsing: 9433 16 XML parsing: 9434 16 XML parsing: 9435 16 XML parsing: 9436 16 XML parsing: tag 9437 16 XML parsing: 9438 16 XML parsing: nning of input 9439 16 XML parsing: ml" are reserved 9440 16 XML parsing: yntax 9441 16 XML parsing: ntax 9442 16 XML parsing: ax 9443 16 XML parsing: syntax 9444 16 XML parsing: ternal subset 9445 16 XML parsing: en declarations 9446 16 XML parsing: ion 9447 16 XML parsing: ed 9448 16 XML parsing: d entity 9449 16 XML parsing: tity 9450 16 XML parsing: al entity references 9451 16 XML parsing: tion syntax 9452 16 XML parsing: syntax 9453 16 XML parsing: 9454 16 XML parsing: 9455 16 XML parsing: cter 9456 16 XML parsing: name 9457 16 XML parsing: 9458 16 XML parsing:

line %d, character %d, incorrect comment syntax line %d, character %d, incorrect conditional sectio line %d, character %d, incorrect ATTLIST declaratio line %d, character %d, incorrect DOCTYPE declaratio line %d, character %d, incorrect ELEMENT declaratio line %d, character %d, incorrect ENTITY declaration line %d, character %d, incorrect NOTATION declarati line line line line line line %d, %d, %d, %d, %d, %d, character character character character character character %d, %d, %d, %d, %d, %d, NDATA expected PUBLIC expected SYSTEM expected name expected one root element end tag does not match start

line %d, character %d, duplicate attribute line %d, character %d, text/xmldecl not at the begi line %d, character %d, namespaces beginning with "x line %d, character %d, incorrect text declaration s line %d, character %d, incorrect xml declaration sy line %d, character %d, incorrect encoding name synt line %d, character %d, incorrect public identifier line %d, character %d, well formed check: pes in in line %d, character %d, well formed check: pes betwe line %d, character %d, well formed check: no recurs line %d, character %d, entity content not well form line %d, character %d, well formed check: undeclare line %d, character %d, well formed check: parsed en line %d, character %d, well formed check: no extern line %d, character %d, incorrect processing instruc line %d, character %d, incorrect system identifier line %d, character %d, '?' expected line %d, character %d, no ']]>' in element content line %d, character %d, illegal qualified name chara line %d, character %d, multiple colons in qualified line %d, character %d, colon in name line %d, character %d, redeclared prefix

9459 16 XML parsing: line %d, character %d, undeclared prefix 9460 16 XML parsing: line %d, character %d, non default namespace with e mpty uri 9461 16 XML %ls starting with '%.*ls' is %d characters long, which excee ds the limit. Maximum allowed length is %d characters. 9462 16 XML parsing: line %d, character %d, not all chunks of value have been read 9463 16 XML parsing: line %d, character %d, xml:space has a non-legal va lue 9464 16 XML parsing: line %d, character %d, XML namespace prefix 'xml' c an only be associated with the URI http://www.w3.org/XML/1998/namespace. This UR I cannot be used with other prefixes. 9465 16 XML parsing: line %d, character %d, XML namespace prefix 'xmlns' is reserved for use by XML. 9466 16 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' . 9467 16 XML parsing: line %d, character %d, xmlns namespace URI (http:// www.w3.org/2000/xmlns/) is reserved and must not be used. 9480 16 XML parsing: line %d, character %d, unsupported xml 9500 16 The data type '%.*ls' used in the VALUE method is invalid. 9501 16 XQuery: Unable to resolve sql:variable('%.*ls'). The variable mu st be declared as a scalar TSQL variable. 9502 16 The string literal provided for the argument %d of the '%.*ls' m ethod must not exceed %d bytes. 9503 16 Errors and/or warnings occurred when processing the XQuery state ment for XML data type method '%.*ls'. See previous error messages for more deta ils. 9504 16 Errors and/or warnings occurred when processing the XQuery state ment for XML data type method '%.*ls', invoked on column '%.*ls', table '%.*ls'. See previous error messages for more details. 9506 16 The XMLDT method '%.*ls' can only be invoked on columns of type xml. 9507 16 The XML data type method on a remote column used in this query c an not be executed either locally or remotely. Please rewrite your query. 9508 16 The reference parameter given to XMLDT method '%.*ls' was genera ted from a different XML instance than the one it is being applied to. 9509 16 XMLUNNEST method requires typed xml column with single global el ement 9510 16 Functionality not yet implemented: XMLNODEREFS cannot use refere nces exposed by views. 9512 16 Xml data type is not supported as a parameter to remote calls. 9513 16 Error processing XML data type method '%.*ls'. The following SET options required by XML data type methods are not set: '%.*ls'. 9514 16 Xml data type is not supported in distributed queries. Remote ob ject '%.*ls' has xml column(s). 9515 16 An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch. 9516 16 XQuery: The name or one of the parts of a multi-part name suppli ed to %S_MSG('%.*ls') is empty. Empty names cannot be used to identify objects, columns or variables in SQL. 9517 16 XQuery: The name or one of the parts of a multi-part name that s tarts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it is to o long. Maximum length is %d, actual length is %d. 9518 16 XQuery: The name or one of the parts of a multi-part name that s tarts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it conta ins invalid characters. 9519 16 XQuery: The name supplied to sql:variable('%.*ls') is not a vali d SQL variable name. Variable names must start with the '@' symbol followed by a t least one character.

9520 16 XQuery: '%.*ls' referenced by sql:variable() is not a valid syst em function name. 9521 16 Error processing XML data type. The XML data type instance conta ins a negative xs:date or xs:dateTime value. 9522 16 The XQuery modify method is not allowed on sparse column sets. 9523 16 Cannot update the sparse column set '%.*ls' because the XML cont ent supplied references the non-sparse column '%.*ls' which does not belong to t his column set. The XML data used to update a sparse column set cannot reference columns that don't belong to the column set. 9524 16 The XML content provided does not conform to the required XML fo rmat for sparse column sets. 9525 16 The XML content that is supplied for the sparse column set '%.*l s' contains duplicate references to the column '%.*ls'. A column can only be ref erenced once in XML content supplied to a sparse column set. 9526 16 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 v alid range is from 1 to %d. 9527 16 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 v alid range for the scale is from 0 to the specified precision. 9528 16 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 vali d only for sparse columns of data type sql_variant. 9529 16 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 col umn is of character data type (char, varchar, nchar, nvarchar), or if the sparse column is of data type sql_variant and the value of the xsi:type attribute is " Char", "VarChar", "NChar", or "NVarChar". 9530 16 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 attr ibute. 9531 16 In the XML content that is supplied for the column set column '% .*ls', the '%.*ls' attribute value on the element '%.*ls' is not valid. 9532 16 In the query/DML operation involving column set '%.*ls', conve rsion failed when converting from the data type '%ls' to the data type '%ls' for the column '%.*ls'. 9533 16 In the XML that is supplied for the column set '%.*ls', the elem ent '%.*ls' should reside in the global namespace. Remove the default namespace declaration or the prefix on the element. 9534 16 In the query/DML operation involving column set '%.*ls', conve rsion 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 provi ding XML conversion methods for CLR types. 9601 16 Cannot relate to %S_MSG %.*ls because it is %S_MSG. 9602 16 Failed to start a system task with error code %d, state %d. 9605 10 Conversation Priorities analyzed: %d. 9606 16 The conversation priority with ID %d has been dropped. 9607 16 The conversation priority with ID %d is referencing the missing service with ID %d. 9608 16 The conversation priority with ID %d is referencing the missing service contract with ID %d. 9609 16 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. 9610 16 The service '%.*ls' in the FROM SERVICE clause must match the se rvice '%.*ls' referenced by %s = '%.*ls'. 9611 16 Cannot find the specified user '%.*ls'. 9613 16 The queue '%.*ls' cannot be activated because the activation use r is not specified. 9614 16 The queue '%.*ls' cannot be activated because the activation sto

red procedure is either not specified or is invalid. 9615 16 A message of type '%.*ls' failed XML validation on the target se rvice. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiat or: %d, and Message sequence number: %I64d. 9616 16 A message of type '%.*ls' was received and failed XML validation . %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: % d, and Message sequence number: %I64d. 9617 16 The service queue "%.*ls" is currently disabled. 9618 16 The message cannot be sent because the service queue '%.*ls' ass ociated with the dialog is currently disabled and retention is on. 9619 16 Failed to create remote service binding '%.*ls'. A remote servic e binding for service '%.*ls' already exists. 9620 16 The activation stored procedure '%.*ls' is invalid. Functions ar e not allowed. 9621 16 An error occurred while processing a message in the Service Brok er and Database Mirroring transport: error %i, state %i. 9622 16 The crypto provider context is not initialized. 9623 16 The key passed in for this operation is in the wrong state. 9624 16 The key size is unacceptable for this key object. 9625 16 The key buffer size is inconsistent with the key modulus size. 9626 16 An internal Service Broker error occurred: an object is in the w rong state for this operation. This error indicates a serious problem with SQL S erver. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems. 9627 16 The hash buffer size is not correct for initializing the hash ob ject. 9628 16 The encryption/decryption data buffer size is not 8 byte aligned . 9629 16 The decrypted signature size is wrong. 9630 16 The signature did not verify the internal hash. 9631 16 The salt size is unacceptable for this key object. 9632 16 The salt buffer size is too small. 9633 16 The passed in name is too long. 9634 16 Service Broker was unable to allocate memory for cryptographic o perations. This message is a symptom of another problem. Check the SQL Server er ror log for additional messages, and address the underlying problem. 9635 16 The certificate is not valid at this point in time. 9636 16 The requested object was not found. 9637 16 The passed in serialized object is incorrectly encoded. 9638 16 The cer or pvk file size is too large. 9639 16 A password was supplied and the pvk file is not encrypted. 9640 16 The operation encountered an OS error. 9641 16 A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event l ogs for further information. 9642 16 An error occurred in a Service Broker/Database Mirroring transpo rt connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far e ndpoint address: '%.*hs') 9643 16 An error occurred in the Service Broker/Database Mirroring trans port manager: Error: %i, State: %i. 9644 16 An error occurred in the service broker message dispatcher. Erro r: %i, State: %i. 9645 16 An error occurred in the service broker manager, Error: %i, Stat e: %i. 9646 16 An error occurred in the timer event cache. Error %i, state %i. 9647 16 Received a malformed message from the network. Unable to retriev e a broker message attribute from a message destined for database ID %d. This ma y indicate a network problem or that another application connected to the Servic e Broker endpoint. 9648 20 The queue '%.*ls' has been enabled for activation, but the MAX_Q

UEUE_READERS is zero. No procedures will be activated. Consider increasing the n umber of MAX_QUEUE_READERS. 9649 16 A security (SSPI) error occurred when connecting to another serv ice broker: '%.*ls'. Check the Windows Event Log for more information. 9650 16 A system cryptographic call failed during a Service Broker or Da tabase Mirroring operation: system error '%ls'. 9651 16 The system call failed during a Service Broker or Database Mirro ring operation. System error: '%ls'. 9652 16 Service Broker failed to retrieve the session key for encrypting a message. 9653 16 The signature of activation stored procedure '%.*ls' is invalid. Parameters are not allowed. 9654 16 Attempting to use database and it doesn't exist. 9655 16 The transmission queue table structure in database is inconsiste nt. Possible database corruption. 9656 16 An error occurred in the service broker multicast manager, Error : %i, State: %i. 9657 23 The structure of the Service Broker transmission work-table in t empdb is incorrect or corrupt. This indicates possible database corruption or ha rdware problems. Check the SQL Server error log and the Windows event logs for i nformation on possible hardware problems. Restart SQL Server to rebuild tempdb. 9658 16 Cannot access the transmission queue table in database. 9659 16 The %s of route '%.*ls' cannot be empty. 9660 16 The %s of route '%.*ls' must be less than %d characters long. 9661 16 The SERVICE_NAME and BROKER_INSTANCE of route "%.*ls" must be sp ecified when using mirroring. 9662 16 Cannot specify BROKER_INSTANCE without SERVICE_NAME in route "%. *ls". 9663 16 The system object cannot be modified. 9666 10 The %S_MSG endpoint is in disabled or stopped state. 9667 10 Services analyzed: %d. 9668 10 Service Queues analyzed: %d. 9669 10 Conversation Endpoints analyzed: %d. 9670 10 Remote Service Bindings analyzed: %d. 9671 16 Messages with conversation ID '%ls' have been removed from the t ransmission queue. 9672 16 Messages with conversation handle '%ls' and conversation group ' %ls' have been removed from the queue with ID %d. 9673 16 Activation has been disabled on the queue with ID %d. 9674 10 Conversation Groups analyzed: %d. 9675 10 Message Types analyzed: %d. 9676 10 Service Contracts analyzed: %d. 9677 16 The service contract with ID %d is referencing the missing messa ge type with ID %d. 9678 16 The service with ID %d is referencing the missing service contra ct with ID %d. 9679 16 The service with ID %d is referencing the missing service queue with ID %d. 9680 16 The conversation endpoint '%ls' is referencing the missing conve rsation group '%ls'. 9681 16 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service contract with ID %d. 9682 16 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service with ID %d. 9683 16 The conversation group '%ls' is referencing the missing service with ID %d. 9684 16 The service with ID %d has been dropped. 9685 16 The service contract with ID %d has been dropped. 9686 16 The conversation endpoint with handle '%ls' has been dropped. 9687 16 The conversation group '%ls' has been dropped.

9688 10 Service Broker manager has started. 9689 10 Service Broker manager has shut down. 9690 10 The %S_MSG endpoint is now listening for connections. 9691 10 The %S_MSG endpoint has stopped listening for connections. 9692 16 The %S_MSG endpoint cannot listen on port %d because it is in us e by another process. 9693 16 The %S_MSG endpoint cannot listen for connections due to the fol lowing error: '%.*ls'. 9694 16 Could not start Service Broker manager. Check the SQL Server err or log and the Windows error log for additional error messages. 9695 16 Could not allocate enough memory to start the Service Broker tas k manager. This message is a symptom of another problem. Check the SQL Server er ror log for additional messages, and address the underlying problem. 9696 16 Cannot start the Service Broker primary event handler. This erro r is a symptom of another problem. Check the SQL Server error log for additional messages, and address this underlying problem. 9697 10 Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages. 9698 16 Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address the underlying problem. 9699 16 Could not allocate memory for extra Service Broker tasks while a dding CPUs. 9701 16 Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows eve nt log for additional messages and address the underlying problem. 9704 16 This message could not be delivered because it failed XML valida tion. This failure occurred while the message was being delivered to the target service. 9705 16 The messages in the queue with ID %d are referencing the invalid conversation handle '%ls'. 9706 16 The stored procedure with ID %d is invalid but is referenced by the queue with ID %d. 9707 16 The activation user with ID %d is invalid but is referenced by q ueue with ID %d. 9708 16 The messages in the queue with ID %d are referencing the invalid conversation group '%ls'. 9709 16 The messages in the queue with ID %d are referencing the invalid message type with ID %d. 9710 16 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation group '%ls'. 9711 16 The transmission queue is referencing the invalid conversation I D '%ls'. 9712 16 The remote service binding with ID %d is referencing the invalid service contract with ID %d. 9713 16 The message type with ID %d is referencing the invalid XML schem a collection ID %d. 9715 16 The conversation endpoint with conversation handle '%ls' is in a n 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 run ning DBCC CHECKDB. Note that DBCC CHECKDB may remove data. 9716 16 The conversation group '%ls' reports references to %d conversati on handle(s), but actually references %d. 9717 16 Cannot enable stored procedure activation on queue '%.*ls'. Even t notification for queue_activation is already configured on this queue. 9718 16 Cannot create event notification for queue_activation on queue " %.*ls". Stored procedure activation is already configured on this queue. 9719 16 The database for this conversation endpoint is attached or resto

red. 9720 16 The database for the remote conversation endpoint is attached or restored. 9721 10 Service broker failed to clean up conversation endpoints on data base '%.*ls'. Another problem is preventing SQL Server from completing this oper ation. Check the SQL Server error log for additional messages. 9723 10 The database "%i" will not be started as the broker due to dupli cation in the broker instance ID. 9724 10 The activated proc '%ls' running on queue '%ls' output the follo wing: '%.*ls' 9725 16 The invalid schema has been dropped from the message type with I D %d. 9726 16 The remote service binding with ID %d has been dropped. 9727 16 Dialog security is not available for this conversation because t here is no remote service binding for the target service. Create a remote servic e binding, or specify ENCRYPTION = OFF in the BEGIN DIALOG statement. 9728 16 Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped af ter the conversation was created. 9730 16 Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security prin cipal may have been dropped after the conversation was created. 9731 16 Dialog security is unavailable for this conversation because the re is no security certificate bound to the database principal (Id: %i). Either c reate a certificate for the principal, or specify ENCRYPTION = OFF when beginnin g the conversation. 9733 16 There is no private key for the security certificate bound to da tabase principal (Id: %i). The certificate may have been created or installed in correctly. Reinstall the certificate, or create a new certificate. 9734 16 The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic s ervice provider. The key length must be a multiple of 64 bytes. 9735 16 The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic se rvice provider. The key length must be a multiple of 64 bytes. 9736 16 An error occurred in dialog transmission: Error: %i, State: %i. %.*ls 9737 16 The private key for the security certificate bound to the databa se principal (ID %i) is password protected. Password protected private keys are not supported for use with secure dialogs. 9738 16 Cannot create task for Service Broker message dispatcher. This m essage is a symptom of another problem that is preventing SQL Server from creati ng tasks. Please check the SQL Server error log and the Windows event log for ad ditional messages. 9739 16 Message transmitter in service broker message dispatcher failed %d times 9740 16 Cannot start the Service Broker message dispatcher. This error i s a symptom of another problem. Check the SQL Server error log and the Windows e vent log for additional messages, and address this underlying problem. 9741 10 The %S_MSG '%.*ls' was dropped on upgrade because it referenced a system contract that was dropped. 9742 16 The activation stored procedure '%.*ls' is invalid. Temporary pr ocedures may not be configured for activation. 9743 16 The %s of route "%.*ls" must be an address when using mirroring. 9744 16 The %s of route "%.*ls" is not a valid address. 9745 16 The ADDRESS of route '%.*ls' cannot be 'TRANSPORT' when SERVICE_ NAME is specified. 9746 16 The LIFETIME of route '%.*ls' must be in the range %d to %d. 9747 16 The ADDRESS and MIRROR_ADDRESS of route '%.*ls' cannot be the sa me.

9748 10 The %S_MSG protocol transport is not available. 9749 10 Target queue is busy; message(s) queued for delivery. 9750 10 No route matches the destination service name for this conversat ion. Create a route to the destination service name for messages in this convers ation to be delivered. 9751 10 Authentication failed with error: '%.*ls'. 9752 10 %S_MSG connection was refused. The user account of the remote se rver is not permitted to log in to this SQL Server: User account: '%.*ls', IP ad dress: '%.*hs'. 9753 10 The target service broker is unreachable. 9754 10 Connection attempt failed with error: '%.*ls'. 9755 10 An error occurred while receiving data: '%.*ls'. 9756 10 An internal exception occurred while connecting to an adjacent b roker: Error: %i, State: %i. %.*ls 9757 10 Service Broker/Database Mirroring network protocol error occurre d. 9758 10 Login protocol negotiation error occurred. 9759 10 An error occurred while sending data: '%.*ls'. 9760 10 The connection has been idle for over %d seconds. 9761 16 The Broker Configuration conversation on dialog handle '%s' clos ed due to an error. To troubleshoot this problem, investigate the error: '%.*ls' . 9762 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: No certificate was found. 9763 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: The certificate found is not valid at th e current time. 9764 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: The certificate found is too large. 9765 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: The certificate found has no associated private key. 9766 10 An unknown internal error (%d) occurred while looking up the pub lic key certificate associated with this SQL Server instance. 9767 16 The security certificate bound to database principal (Id: %i) ha s been disabled for use with BEGIN DIALOG. See the Books Online topics "Certific ates and Service Broker" for an overview and "ALTER CERTIFICATE (Transact-SQL)" for syntax to make a certificate ACTIVE FOR BEGIN_DIALOG. 9768 16 A database user associated with the secure conversation was drop ped before credentials had been exchanged with the far endpoint. Avoid using DRO P USER while conversations are being created. 9769 10 Insufficient memory prevented the Service Broker/Database Mirror ing Transport Manager from starting. 9770 10 Locating routes and security information via the Broker Configur ation Service. 9771 10 The service broker manager is disabled in single-user mode. 9772 16 The Service Broker in database "%.*ls" cannot be enabled because there is already an enabled Service Broker with the same ID. 9773 10 The Service Broker in database "%d" is disabled because there is already an enabled Service Broker with the same ID. 9774 10 Cannot create a new Service Broker in the attached read-only dat abase "%.*ls". The Service Broker will be disabled. 9775 16 Cannot create a new Service Broker in read-only database "%.*ls" . 9776 16 Cannot enable the Service Broker in database "%.*ls" because the Service Broker GUID in the database (%s) does not match the one in sys.database s (%s). 9777 10 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.datab ases (%s).

9778 16 Cannot create a new Service Broker in a mirrored database "%.*ls ". 9779 10 Service Broker received an END CONVERSATION message on this conv ersation. Service Broker will not transmit the message; it will be held until th e application ends the conversation. 9780 10 The service broker manager is initializing. 9781 10 The service broker manager is shutting down. 9782 10 An internal exception occurred while dispatching a message: Erro r: %i, State: %i. %.*ls 9783 10 DNS lookup failed with error: '%.*ls'. 9784 10 Service Broker received an error message on this conversation. S ervice Broker will not transmit the message; it will be held until the applicati on ends the conversation. 9785 10 Invalid address specified: '%.*ls'. 9786 10 Cannot retrieve user name from security context. Error: '%.*ls'. State: %hu. 9787 10 An error occurred while processing broker mirroring routes. Erro r: %i. State: %i. 9788 10 Unable to route the incoming message. The system database msdb c ontaining routing information is not available. 9789 10 Unable to route the incoming message. The system database msdb c ontaining routing information is not available. The broker is disabled in msdb. 9790 10 Unable to route the incoming message. The system database msdb c ontaining routing information is in SINGLE USER mode. 9791 10 The broker is disabled in the sender's database. 9792 10 Could not forward the message because forwarding is disabled in this SQL Server instance. 9793 10 The target service name could not be found. Ensure that the serv ice name is specified correctly and/or the routing information has been supplied . 9794 10 The broker mirroring manager has not fully initialized. 9795 10 Could not find the target broker in the local SQL Server instanc e. 9796 10 The target service name matched a LOCAL route, but there is no s ervice by that name in the local SQL Server instance. 9797 10 Classification has been delayed because the routing information is currently being updated. 9798 16 The message could not be delivered because it could not be class ified. Enable broker message classification trace to see the reason for the fail ure. 9799 10 The connection was closed by the remote end, or an error occurre d while receiving data: '%.*ls' 9801 16 Error converting %.*ls to %ls. The result would be truncated. 9802 16 The locale identifier (LCID) %d is not supported by SQL Server. 9803 16 Invalid data for type "%ls". 9804 16 Column or parameter #%d: Invalid fractional second precision %d specified for %ls data type. The maximum fractional second precision is %d. 9805 10 Warning: converting %ls to %ls caused a loss of information. 9806 16 The datepart %.*ls is not supported by date function %.*ls. 9807 16 The input character string does not follow style %d, either chan ge the input character string or use a different style. 9808 16 This session's YDM date format is not supported when converting from this character string format to date, time, datetime2 or datetimeoffset. Ch ange the session's date format or provide a style to the explicit conversion. 9809 16 The style %d is not supported for conversions from %s to %s. 9810 16 The datepart %.*ls is not supported by date function %.*ls for d ata type %s. 9811 16 The system timezone information could not be retrieved. 9812 16 The timezone provided to builtin function %.*ls is invalid. 9813 16 The timezone provided to builtin function %.*ls would cause the

datetimeoffset to overflow the range of valid date range in either UTC or local time. 9814 16 The date provided is before the start of the Hijri calendar whic h in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. (Julian calendar) or July 18th, 622 C.E (proleptic Gregorian calendar). 9815 16 Waitfor delay and waitfor time cannot be of type %s. 9816 16 The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set. 9817 16 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. 9818 16 The culture parameter '%.*ls' provided in the function call is n ot supported. 9819 16 Error converting string value '%.*ls' into data type %ls using c ulture '%.*ls'. 9901 16 Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low o n disk space. Pausing all populations in progress until more space becomes avail able. Reason code: %d. Error: %ls. To resume populations, free up disk space. 9902 10 Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low o n system resources. Any population in progress will be paused until more resourc es become available. Reason code: %d. Error: %ls. If this message occurs frequen tly, try to serialize full-text indexing for multiple catalogs. 9903 10 The full-text catalog health monitor reported a failure for full -text catalog '%ls' (%d) in database '%ls' (%d). Reason code: %d. Error: %ls. Th e system will restart any in-progress population from the previous checkpoint. I f this message occurs frequently, consult SQL Server Books Online for troublesho oting assistance. This is an informational message only. No user action is requi red. 9904 10 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 messag e occurs frequently, consult SQL Server Books Online for troubleshooting assista nce. This is an informational message only. No user action is required. 9905 10 Informational: Full-text indexer requested status change for cat alog '%ls' ('%d') in database '%ls' ('%d'). New Status: %ls, Reason: %ls (%ls). 9906 10 The full-text catalog monitor reported catalog '%ls' (%d) in dat abase '%ls' (%d) in %ls state. This is an informational message only. No user ac tion is required. 9907 10 Error: Total number of items in full-text catalog ID '%d' in dat abase ID '%d' exceeds the supported limit. See Books Online for troubleshooting assistance. 9908 10 Changing the status to %ls for full-text catalog '%ls' (%d) in d atabase '%ls' (%d). This is an informational message only. No user action is req uired. 9909 10 Warning: Failed to change the status to %ls for full-text catalo g '%ls' (%d) in database '%ls' (%d). Error: %ls. 9910 10 Warning: Error occurred during full-text %ls population for tabl e or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %ls. 9911 10 Informational: Full-text %ls population initialized for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Populatio n sub-tasks: %d. 9912 10 Error: Failed to initialize full-text %ls population for table o r indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %d. 9913 10 Informational: Resuming full-text population for table or indexe d view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d') . Prior number of documents processed: %d, error encountered: %d. 9914 16 Error: Failed to resume full-text %ls population for table or in dexed 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 r

e-create the index. 9915 10 Reinitialized full-text %ls population for table '%ls' (table ID '%d', database ID '%d') after a temporary failure. Number of documents processe d prior to failure: %d, errors encountered: %d. This is an informational message only. No user action is required. 9916 10 Error: Failed to reinitialize full-text %ls population after a t emporary failure for table or indexed view '%ls', database '%ls' (table or index ed view ID '%d', database ID '%d'). Error: %d. 9917 17 An internal error occurred in full-text docid mapper. 9918 10 Warning: Full-text catalog '%ls' uses FAT volume. Security and d ifferential backup are not supported for the catalog. 9919 16 Fulltext DDL command failed because SQL Server was started in si ngle user mode. 9920 10 Warning: Failed to get MSFTESQL indexer interface for full-text catalog '%ls' ('%d') in database '%ls' ('%d'). Error: %ls. 9921 16 During upgrade fatal error 0x%x encountered in CoCreateGuid. Fai led to resolve full-text catalog file name for '%ls'. 9922 10 Warning: Full-text population for table or indexed view '%ls' fa iled to send batch of data to MSFTESQL service (table or indexed view ID '%d', c atalog ID '%d', database ID '%d'). Error: %ls. 9923 10 Warning: Full-text population for table or indexed view '%ls' re ported low resources while sending a batch of data to MSFTESQL service (table or indexed view ID '%d', catalog ID '%d', database ID '%d'). Error: %ls. 9924 16 Rebuild full-text catalog '%ls' failed: Catalog header file is r ead-only. 9925 16 Rebuild full-text catalog '%ls' failed: Full-text catalog is rea d-only. 9926 10 Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should. 9927 10 Informational: The full-text search condition contained noise wo rd(s). 9928 16 Computed column '%.*ls' cannot be used for full-text search beca use it is nondeterministic or imprecise nonpersisted computed column. 9929 16 Computed column '%.*ls' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column must be deterministic, precise or persisted, with a size less or equal than %d characters. 9930 10 Null document type provided. Row will not be full-text indexed. 9931 10 Document type exceeds the maximum permitted length. Row will not be full-text indexed. 9932 10 Document type value is malformed. Row will not be full-text inde xed. 9933 10 Internal error: The row cannot be full-text indexed. The protoco l handler was invoked out of sequence. This is an informational message only. No user action is required. 9934 10 Row was not found. It was deleted or updated while indexing was in progress. 9935 10 Warning: Wordbreaker, filter, or protocol handler used by catalo g '%ls' does not exist on this instance. Use sp_help_fulltext_catalog_components and sp_help_fulltext_system_components check for mismatching components. Rebuil d catalog is recommended. 9936 10 Informational: No full-text supported languages found. 9937 16 Too many full-text columns or the full-text query is too complex to be executed. 9938 16 Cannot find the specified user or role '%.*ls'. 9939 16 Current user or role '%.*ls' does not have the required permissi on to set the owner. 9940 10 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 prece ding error. 9941 10 Informational: Full-text %ls population for table or indexed vie

w '%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 whe never the database is available 9942 10 Informational: Full-text %ls population for table or indexed vie w '%ls' (table or indexed view ID '%d', database ID '%d') was cancelled by user . 9943 10 Informational: Full-text %ls population completed for table or i ndexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of d ocuments processed: %d. Number of documents failed: %d. Number of documents that will be retried: %d. 9944 10 Informational: Full-text retry pass of %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d' ). Number of retry documents processed: %d. Number of documents failed: %d. 9945 10 Error: All Full-text populations in progress, for catalog '%ls' ('%d') in database '%ls' ('%d') were terminated due to error. Error: 0x%x. 9947 10 Warning: Identity of full-text catalog in directory '%ls' does n ot match database '%.*ls'. The full-text catalog cannot be attached. 9948 10 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, or it is a UNC PATH. The full-text catalog cannot be attached, rebuild the catalog to reso lve it. 9949 10 Warning: All Full-text populations in progress for full-text cat alog '%ls' ('%d') in database '%ls' ('%d') are paused. Reason code: %d. Error: % ls. If this message occurs frequently, consult Books Online for indexing perform ance tuning assistance. 9950 10 Informational: Full-text catalog health monitor reported a failu re for catalog '%ls' ('%d') in database '%ls' ('%d'). Reason code: %d. Error: %l s. The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch. 9951 10 Warning: Database %.*ls cannot be modified during detach because database is in read-only, standby, or shutdown state. Full-text catalog is not dropped, and '@keepfulltextindexfile = false' is ignored. 9952 10 Informational: Full-text auto change tracking is turned off for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') du e to fatal crawl error. 9953 16 The path '%.*ls' has invalid attributes. It needs to be a direct ory. It must not be hidden, read-only, or on a removable drive. 9954 16 SQL Server failed to communicate with filter daemon launch servi ce (Windows error: %ls). Full-Text filter daemon process failed to start. Fulltext search functionality will not be available. 9955 16 SQL Server failed to create named pipe '%ls' to communicate with the full-text filter daemon (Windows error: %d). Either a named pipe already ex ists for a filter daemon host process, the system is low on resources, or the se curity identification number (SID) lookup for the filter daemon account group fa iled. To resolve this error, terminate any running full-text filter daemon proce sses, and if necessary reconfigure the full-text daemon launcher service account . 9959 16 Cannot perform requested task because full-text memory manager i s not initialized. 9960 16 View '%.*ls' is not an indexed view. Full-text index is not allo wed to be created on it. 9961 16 Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified. 9962 16 Failed to move full-text catalog from '%ls' to '%ls'. OS error ' %ls'. 9963 10 Inconsistent accent sensitivity of full-text catalog is detected . Full-text catalog for catalog ID '%d', database ID '%d' is reset. 9964 16 Failed to finish full-text operation. Filegroup '%.*ls' is empty , read-only, or not online. 9965 16 NULL or Invalid type of value specified for '%ls' parameter.

9966 16 Cannot use full-text search in master, tempdb, or model database . 9967 10 A default full-text catalog does not exist in database '%.*ls' o r user does not have permission to perform this action. 9968 10 Warning: No appropriate filter was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', datab ase ID '%d'), full-text key value '%ls'. Some columns of the row were not indexe d. 9969 10 Warning: No appropriate wordbreaker was found during full-text i ndex 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 s ome columns of the row. 9970 16 Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline. 9971 10 Warning: No appropriate filter for embedded object was found dur ing 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 objec ts in the row could not be indexed. 9972 16 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 O NLINE. 9973 10 Informational: Full-text %ls population paused for table or inde xed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of docu ments processed: %d. Number of documents failed: %d. 9974 10 Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue w hen your start the same type of crawl again. 9975 10 Warning: Only paused full population can be resumed. The command is ignored. 9977 10 Warning: Last population complete time of full-text catalog in d irectory '%ls' does not match database '%.*ls'. The full-text catalog is attache d and it may need to be repopulated. 9978 10 Warning: During upgrade full-text index on table '%ls' is disabl ed because at least one of full-text key column, full-text columns, or type colu mns is a non-deterministic or imprecise nonpersisted computed column. 9979 10 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 th e full-text catalog path and rebuild the full-text catalog after upgrade. 9980 16 Variable parameters can not be passed to fulltext predicates: co ntains, freetext and functions: containstable, freetexttable applied to remote t able. 9982 16 Cannot use full-text search in user instance. 9983 16 The value '%ls' for the full-text component '%ls' is longer than the maximum permitted (%d characters). Please reduce the length of the value. 9984 10 Informational: Full-text %ls population paused for table or inde xed view '%ls' (table or indexed view ID '%d', database ID '%d'). 9985 16 There is not enough memory to generate a search property list ca che. Rerun your full-text indexing statement when more resources are available. 9986 16 A search property list cache cannot be generated during full-tex t indexing. Attempting to query the registered search properties caused an inter nal error as indicated by the HRESULT error code, ((HRESULT = '0x%08x'). 9987 15 The max gap argument in NEAR clause must be either the word MAX or an integer greater than or equal to 0. 9988 15 The number of query terms in NEAR clause must be less than or eq ual to 64. 9998 16 The column '%.*ls' cannot be added to a full-text index. Full-te xt indexes are limited to 1024 columns. When you create a full-text index, add f ewer columns. 9999 16 The column '%.*ls' in the table '%.*ls' cannot be used for fulltext search because it is a sparse column set.

10000 16 Unknown provider error. 10001 16 The provider reported an unexpected catastrophic failure. 10002 16 The provider did not implement the functionality. 10003 16 The provider ran out of memory. 10004 16 One or more arguments were reported invalid by the provider. 10005 16 The provider did not support an interface. 10006 16 The provider indicated an invalid pointer was used. 10007 16 The provider indicated an invalid handle was used. 10008 16 The provider terminated the operation. 10009 16 The provider did not give any information about the error. 10010 16 The data necessary to complete this operation was not yet availa ble to the provider. 10011 16 Access denied. 10021 16 Execution terminated by the provider because a resource limit wa s reached. 10022 16 The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned. 10023 16 The provider does not support the necessary method. 10024 16 The provider indicates that the user did not have the permission to perform the operation. 10025 16 Provider caused a server fault in an external process. 10026 16 No command text was set. 10027 16 Command was not prepared. 10028 16 Authentication failed. 10032 16 Cannot return multiple result sets (not supported by the provide r). 10033 16 The specified index does not exist or the provider does not supp ort an index scan on this data source. 10034 16 The specified table or view does not exist or contains errors. 10035 16 No value was given for one or more of the required parameters. 10042 16 Cannot set any properties while there is an open rowset. 10052 16 The insertion was canceled by the provider during notification. 10053 16 Could not convert the data value due to reasons other than sign mismatch or overflow. 10054 16 The data value for one or more columns overflowed the type used by the provider. 10055 16 The data violated the integrity constraints for one or more colu mns. 10056 16 The number of rows that have pending changes has exceeded the li mit specified by the DBPROP_MAXPENDINGROWS property. 10057 16 Cannot create the row. Would exceed the total number of active r ows supported by the rowset. 10058 16 The consumer cannot insert a new row before releasing previously -retrieved row handles. 10062 16 The change was canceled by the provider during notification. 10063 16 Could not convert the data value due to reasons other than sign mismatch or overflow. 10064 16 The data value for one or more columns overflowed the type used by the provider. 10065 16 The data violated the integrity constraints for one or more colu mns. 10066 16 The number of rows that have pending changes has exceeded the li mit specified by the DBPROP_MAXPENDINGROWS property. 10067 16 The rowset was using optimistic concurrency and the value of a c olumn has been changed after the containing row was last fetched or resynchroniz ed. 10068 16 The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source. 10069 16 The consumer could not delete the row. The insertion has been tr ansmitted to the data source.

10081 16 The rowset uses integrated indexes and there is no current index . 10085 16 RestartPosition on the table was canceled during notification. 10086 16 The table was built over a live data stream and the position can not be restarted. 10087 16 The provider did not release some of the existing rows. 10088 16 The order of the columns was not specified in the object that cr eated the rowset. The provider had to reexecute the command to reposition the ne xt fetch position to its initial position, and the order of the columns changed. 10100 16 Cannot create %S_MSG on view "%.*ls" because it contains the DIS TINCT keyword. Consider removing DISTINCT from the view or not indexing the view . Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG(*) to si mulate DISTINCT on grouping columns. 10101 16 Cannot create %S_MSG on view "%.*ls" because it contains the TOP or OFFSET keyword. Consider removing the TOP or OFFSET or not indexing the view . 10102 16 Cannot create %S_MSG on view "%.*ls" because it contains the TAB LESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view. 10103 16 Cannot create %S_MSG on view "%.*ls" because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OP ENQUERY, OPENROWSET, and OPENDATASOURCE. 10104 16 Cannot create %S_MSG on view "%.*ls" because it references a tab le using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view. 10105 16 Cannot create %S_MSG on view "%.*ls" because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view. 10106 16 Cannot create %S_MSG on view "%.*ls" because it references an in ternal system rowset provider. Consider not indexing this view. 10107 16 Cannot create %S_MSG on view "%.*ls" because it uses table varia ble "%.*ls". Consider not indexing this view or removing the reference to the ta ble variable. 10108 16 Cannot create %S_MSG on view "%.*ls" because it references a SQL Server internal table. 10109 16 Cannot create %S_MSG on view "%.*ls" because it references deriv ed table "%.*ls" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view. 10110 16 Cannot create %S_MSG on view "%.*ls" because it contains an OUTE R APPLY. Consider not indexing the view, or removing OUTER APPLY. 10111 16 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 . 10112 16 Cannot create %S_MSG on view '%.*ls' because it contains an INNE R join that specifies a join hint. Consider removing the join hint. 10113 16 Cannot create %S_MSG on view "%.*ls" because it uses a LEFT, RIG HT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Conside r using an INNER join instead. 10114 16 Cannot create %S_MSG on view "%.*ls" because it uses the PIVOT o perator. Consider not indexing this view. 10115 16 Cannot create %S_MSG on view "%.*ls" because it uses the UNPIVOT operator. Consider not indexing this view. 10116 16 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 operato rs of the original view. 10117 16 Cannot create %S_MSG on view "%.*ls" because the view uses the " *" operator to select columns. Consider referencing columns by name instead. 10118 16 Cannot create %S_MSG on view "%.*ls" because it contains a GROUP BY ALL. Consider using a GROUP BY instead. 10119 16 Cannot create %S_MSG on view "%.*ls" because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.

10121 16 Cannot create %S_MSG on view "%.*ls" because it contains a HAVIN G clause. Consider removing the HAVING clause. 10124 16 Cannot create %S_MSG on view "%.*ls" because it references an in ternal SQL Server column. 10125 16 Cannot create %S_MSG on view "%.*ls" because it uses aggregate " %.*ls". Consider eliminating the aggregate, not indexing the view, or using alte rnate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUN T, substitute COUNT_BIG. 10126 16 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. 10127 16 Cannot create %S_MSG on view "%.*ls" because it contains one or more subqueries. Consider changing the view to use only joins instead of subquer ies. Alternatively, consider not indexing this view. 10128 16 Cannot create %S_MSG on view "%.*ls" because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or n ot indexing the view. 10129 16 Cannot create %S_MSG on view "%.*ls" because it references the i nline or multistatement table-valued function "%.*ls". Consider expanding the fu nction definition by hand in the view definition, or not indexing the view. 10130 16 Cannot create %S_MSG on view "%.*ls" because it uses non-determi nistic common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view or changing it to not use this function. 10131 16 Cannot create %S_MSG on view "%.*ls" because it references impre cise common language runtime (CLR) table-valued function "%.*ls". Consider not i ndexing the view. 10132 16 Cannot create %S_MSG on view "%.*ls" because it references table valued common language runtime (CLR) function "%.*ls". Consider removing refere nce to the function or not indexing the view. 10133 16 Cannot create %S_MSG on view "%.*ls" because function "%.*ls" re ferenced by the view performs user or system data access. 10134 16 Cannot create %S_MSG on view "%.*ls" because it contains more th an one APPLY. Consider not indexing the view, or using only one APPLY. 10136 16 Cannot create %S_MSG on view "%.*ls" because it uses the aggrega te COUNT. Use COUNT_BIG instead. 10137 16 Cannot create %S_MSG on view "%.*ls" because it references commo n table expression "%.*ls". Views referencing common table expressions cannot be indexed. Consider not indexing the view, or removing the common table expressio n from the view definition. 10138 16 Cannot create %S_MSG on view '%.*ls' because its select list doe s not include a proper use of COUNT_BIG. Consider adding COUNT_BIG(*) to select list. 10139 16 Cannot create %S_MSG on view '%.*ls' because the view uses an im plicit conversion from string to datetime or smalldatetime. Use an explicit CONV ERT with a deterministic style value. 10140 16 Cannot create %S_MSG on view '%.*ls' because the view contains a table hint. Consider removing the hint. 10141 16 Cannot create %S_MSG on view '%.*ls' because it references CLR r outine (function or method) '%.*ls' outside non-key columns of SELECT list. Recr eate or alter view so it does not reference CLR routines except in non-key colum ns of SELECT list, and then create index. 10142 16 Cannot create %S_MSG on view "%.*ls" because it contains an APPL Y. Consider not indexing the view, or removing APPLY. 10143 16 Cannot create %S_MSG on view "%.*ls" because it contains a ranki ng or aggregate window function. Remove the function from the view definition or , alternatively, do not index the view. 10144 16 Cannot create %S_MSG on view '%.*ls' because it uses the CHANGET ABLE function. 10145 16 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. Co nsider removing the sparse column set from the view or not indexing the view. 10146 16 Cannot create %S_MSG on the view '%.*ls' because it uses the SEM ANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE f unction. 10211 16 Cannot invoke mutator on a null CLR type value. 10227 16 Field "%.*ls" of type "%.*ls.%.*ls" cannot be updated because th e field is "%.*ls". 10240 16 Could not find UdtExtensions.dll. Please check your installation . 10300 16 Assembly '%.*ls' references assembly '%.*ls', which is not prese nt in the current database. SQL Server attempted to locate and automatically loa d the referenced assembly from the same location where referring assembly came f rom, but that operation has failed (reason: %S_MSG). Please load the referenced assembly into the current database and retry your request. 10301 16 Assembly '%.*ls' references assembly '%.*ls', which is not prese nt in the current database. SQL Server attempted to locate and automatically loa d the referenced assembly from the same location where referring assembly came f rom, but that operation has failed (reason: %s). Please load the referenced asse mbly into the current database and retry your request. 10302 16 Could not get path for SQL Server: '%ls'. 10303 16 Could not create AppDomain manager: '%.*ls'. 10304 16 Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions. 10305 16 The Init method for a CLR table-valued function must be annotate d with SqlFunctionAttribute. 10306 16 The SqlFunctionAttribute of the Init method for a CLR table-valu ed function must set the FillRowMethodName property. 10307 16 The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name. 10308 10 Warning: The Microsoft .NET Framework assembly '%.*ls' you are r egistering is not fully tested in the SQL Server hosted environment and is not s upported. In the future, if you upgrade or service this assembly or the .NET Fra mework, your CLR integration routine may stop working. Please refer SQL Server B ooks Online for more details. 10309 10 Warning: The SQL Server client assembly '%.*ls' you are register ing is not fully tested in SQL Server hosted environment. 10310 10 AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations. 10311 10 AppDomain %i (%.*ls) is marked for unload due to memory pressure . 10312 16 .NET Framework execution was aborted. The UDP/UDF/CLR type did n ot revert thread token. 10313 16 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 10314 16 An error occurred in the Microsoft .NET Framework while trying t o load assembly id %d. The server may be running out of resources, or the assemb ly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the q uery again, or check documentation to see how to solve the assembly trust issues . For more information about this error: %.*ls 10316 16 The app domain with specified version id (%d) was unloaded due t o memory pressure and could not be found. 10317 16 An error occurred trying to get file version info for the file ' %s'. 10318 16 '%.*ls' failed because parameter %d of method '%.*ls' of type '% .*ls' is annotated with unsupported attribute System.ParamArrayAttribute. 10319 16 UserDefinedType method call failed because parameter %d of metho d '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamAr rayAttribute.

10320 16 Method name '%.*ls' is invalid for '%.*ls'. 10321 16 Method name '%.*ls' is invalid for UserDefinedType method call. 10322 16 Type %.*ls not found in database %.*ls 10323 16 Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls 10324 16 WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T -SQL triggers and not to CLR triggers. 10325 16 The server is shutting down due to stack overflow in user's unma naged code. 10326 16 Two versions of assembly '%.*ls' cannot coexist in database '%.* ls'. Keep one version and drop the other. 10327 14 %ls ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls ' is not authorized for PERMISSION_SET = %ls. The assembly is authorized when e ither 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. 10328 16 There is not enough stack to create appdomain '%.*ls'. 10329 16 .Net Framework execution was aborted. %.*ls 10330 16 ALTER ASSEMBLY failed because serialization layout of type '%s' would change as a result of a change in type '%s' in the updated assembly. Persi sted types are not allowed to change serialization layout. 10331 16 Type '%ls' in assembly '%.*ls' derives from a generic type which is not supported for a CLR Type. 10332 16 Assembly "%.*ls" was built using version %.*ls of the .NET Frame work. SQL Server currently uses version %s. 10333 16 Failed to obtain ICLRAppDomainResourceMonitor interface from CLR . The error code from CLR was: 0x%x. As a result, resource monitoring won't work for AppDomain with ID %d. 10334 16 Changing the database compatibility level has caused data to be marked as unchecked in one or more objects in database %s. Refer to the column h as_unchecked_assembly_data in the sys.tables and sys.views to locate all such ob jects. 10335 16 The Common Language Runtime (CLR) was loaded in an unsupported m anner. This can occur if an extended stored procedure or OLE Automation object r unning in SQL Server calls into managed code before the CLR integration runtime host loads the CLR. You need to restart SQL Server to use CLR integration featur es. 10336 10 Failed to enque task to start CLR during SQL server startup. Err or code: %u. CLR will be started in an on-demand fashion. 10337 16 An internal error occurred. 10338 16 Verification of assembly failed. Could not open the physical fil e '%.*ls': %ls. 10339 16 Verification of assembly failed. Could not read from the physica l file "%.*ls": %ls. 10501 16 Cannot create plan guide '%.*ls' because type '%.*ls' provided i s not allowed. 10502 16 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. 10503 16 Operation '%.*ls' is not allowed. 10504 16 Cannot create plan guide '%.*ls' because parameter @hints is inc orrect. Use N'OPTION ( <query_hint> [ ,...n ] )'. 10505 16 Cannot create plan guide '%.*ls' because value '%.*ls' provided for @module_or_batch is not legal two-part name. Use 'schema_name.object_name'. 10506 16 Cannot create plan guide '%.*ls' because parameter @stmt has mor e than one statement. 10507 16 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. 10508 16 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. 10509 16 Cannot create plan guide '%.*ls' because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is inelig ible 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 st arting position, query the 'statement_start_offset' column in the sys.dm_exec_qu ery_stats dynamic management function. 10510 16 Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name. 10512 16 Cannot create plan guide '%.*ls' because object '@module_or_batc h' is encrypted. Consider tuning query using other techniques such as indexes an d statistics. 10513 16 Cannot %S_MSG %S_MSG '%.*ls' because it is referenced by plan gu ide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed. 10515 16 Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission. 10516 16 Cannot create plan guide '%.*ls' because @module_or_batch can no t be compiled. 10517 16 Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required. 10518 16 Cannot execute sp_control_plan_guide because of insufficient per missions to control plan guide '%.*ls'. Alter permission on object referenced by plan guide, or alter database permission required. 10519 16 Cannot create plan guide '%.*ls' because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statemen t_start_offset. Verify that the hints can be applied to the statement. 10520 16 Cannot create plan guide '%.*ls' because @type was specified as '%ls' and a non-NULL value is specified for the parameter '%ls'. This type requi res a NULL value for the parameter. Specify NULL for the parameter, or change th e type to one that allows a non-NULL value for the parameter. 10521 16 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 t he parameter. Specify a non-NULL value for the parameter, or change the type to one that allows a NULL value for the parameter. 10522 16 Cannot create plan guide '%.*ls' because @hints has illegal valu e. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIM PLE) if @type is 'template'. 10523 16 Cannot generate query template because @querytext does not conta in a valid single query. 10524 16 Cannot parameterize @querytext. 10525 10 Plan guide '%.*ls' matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it co ntains was ignored. RECOMPILE is not supported on automatically parameterized st atements. Consider dropping this plan guide or removing RECOMPILE from it. 10526 16 Cannot drop %S_MSG '%.*ls' because its trigger '%.*ls' is refere nced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide fir st. Record the plan guide definition for future use if needed. 10527 16 Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object. 10528 16 Cannot create plan guide '%.*ls' because its name is invalid. Pl an guide name cannot begin with a '#' character. 10529 16 Cannot create plan guide '%.*ls' because there is already a plan guide '%.*ls' of @type 'template' on @stmt. 10530 16 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. 10531 16 Cannot create plan guide '%.*ls' from cache because the user doe s not have adequate permissions. Grant the VIEW SERVER STATE permission to the u ser creating the plan guide. 10532 16 Cannot create plan guide '%.*ls' because the batch or module spe cified by @plan_handle does not contain a statement that is eligible for a plan guide. Specify a different value for @plan_handle. 10533 16 Cannot create plan guide '%.*ls' because the plan guide name exc eeds 124, the maximum number of characters allowed. Specify a name that contains fewer than 125 characters. 10534 16 Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form <parameter_name> <parameter_t ype>, or specify NULL. 10535 16 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_stat s dynamic management view. 10536 16 Cannot create plan guide '%.*ls' because the batch or module cor responding to the specified @plan_handle contains more than 1000 eligible statem ents. Create a plan guide for each statement in the batch or module by specifyin g a statement_start_offset value for each statement. 10537 16 Cannot enable plan guide '%.*ls' because the enabled plan guide '%.*ls' contains the same scope and starting offset value of the statement. Disa ble the existing plan guide before enabling the specified plan guide. 10538 16 Cannot find the plan guide either because the specified plan gui de 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 obj ect referenced by the plan guide or ALTER DATABASE permission. 10539 16 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. Mak e sure that all necessary database objects exist, and execute the statement befo re creating the plan guide. 10601 16 Cannot specify included columns for a clustered index. 10602 16 Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement i s not allowed. 10603 16 Cannot rebuild clustered index '%.*ls' on view '%.*ls' because t he view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disa bled. 10604 16 Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified. 10605 16 Cannot disable primary key index "%.*ls" on table "%.*ls" becaus e the table is published for replication. 10606 16 Cannot disable the clustered index "%.*ls" on view "%.*ls" becau se the indexed view is published for replication. 10607 16 The clustered index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Disable change tracking on the ta ble before disabling the clustered index. 10608 16 The index '%.*ls' on table '%.*ls' cannot be disabled because th e table has change tracking enabled. Change tracking requires a primary key cons traint on the table, and disabling the index will drop the constraint. Disable c hange tracking on the table before disabling the index. 10609 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' becau se the column '%.*ls' in the filter expression is a computed column. Rewrite the filter expression so that it does not include this column. 10610 16 Filtered index '%.*ls' cannot be created on object '%.*ls' becau se 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 v

iew with the filter expression incorporated in the view definition. 10611 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' becau se the column '%.*ls' in the filter expression is compared with a constant of hi gher data type precedence or of a different collation. Converting a column to th e 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 th e column '%.*ls'. 10612 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' becau se 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 expressio n so that it does not include this comparison. 10617 16 Index '%.*ls' could not be created or rebuilt. The key length fo r this index (%d bytes) exceeds the maximum allowed length of '%d' bytes when us ing the vardecimal storage format. 10618 16 Cannot %S_MSG filtered index '%.*ls' on table '%.*ls' because th e statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it does not use the IGNORE_DUP_KEY option. 10619 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' becau se the column '%.*ls' in the filter expression is of a CLR data type. Rewrite th e filter expression so that it does not include this column. 10620 16 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' becau se the filter expression contains a comparison with a literal NULL value. Rewrit e the comparison to use the IS [NOT] NULL comparison operator to test for NULL v alues. 10621 16 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. 10622 16 The %S_MSG '%.*ls' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set co lumn. 10623 16 Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user t ables. 10631 16 Index '%.*ls' could not be created or rebuilt. A unique or clust ered index on a federated table must contain the federated column. 10632 16 Index '%.*ls' could not be created. Views cannot be indexed in a federated database. 10633 16 Invalid online index creation operation 10700 16 The table-valued parameter "%.*ls" is READONLY and cannot be mod ified. 10701 15 The READONLY option cannot be used in an EXECUTE or CREATE AGGRE GATE statement. 10702 15 The WITH CUBE and WITH ROLLUP options are not permitted with a R OLLUP, CUBE, or GROUPING SETS specification. 10703 15 Too many grouping sets. The maximum number is %d. 10704 15 To rethrow an error, a THROW statement must be used inside a CAT CH block. Insert the THROW statement inside a CATCH block, or add error paramete rs to the THROW statement. 10705 15 Subqueries are not allowed in the OUTPUT clause. 10706 15 Too many expressions are specified in the GROUP BY clause. The m aximum number is %d when grouping sets are supplied. 10707 15 The CUBE() and ROLLUP() grouping constructs are not allowed in t he current compatibility mode. They are only allowed in 100 mode or higher. 10708 15 DEFAULT is not allowed on the right hand side of "%.*ls" 10709 15 The number of columns for each row in a table value constructor must be the same. 10710 15 An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCH ED' clause of a MERGE statement. 10711 15 An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement. 10713 15 A MERGE statement must be terminated by a semi-colon (;).

10714 15 An action of type '%S_MSG' cannot appear more than once in a '%S _MSG' clause of a MERGE statement. 10716 15 A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause. 10717 15 The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 10718 15 Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements. 10720 15 An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. 10721 15 The WHERE CURRENT OF clause is not allowed in a nested INSERT, U PDATE, DELETE, or MERGE statement. 10722 15 The DISTINCT keyword is not allowed when the FROM clause contain s a nested INSERT, UPDATE, DELETE, or MERGE statement. 10723 15 In a MERGE statement, a variable cannot be set to a column and e xpression in the same assignment in the SET clause of an UPDATE action. Assignme nts of the form 'SET @variable = column = expression' are not valid in the SET c lause of an UPDATE action in a MERGE statement. Modify the SET clause to only sp ecify assignments of the form 'SET @variable = column' or 'SET @variable = expre ssion'. 10724 15 The FORCESEEK hint is not allowed for target tables of INSERT, U PDATE, or DELETE statements. 10725 15 Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. 10726 15 User defined aggregates do not support default parameters. 10727 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed on either side of a JOIN or APPLY operator. 10728 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed as the table source of a PIVOT or UNPIVOT operator. 10729 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed in a SELECT statement that is not the immediate source of rows for an INSERT statement. 10730 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed in the FROM clause of an UPDATE or DELETE statement. 10731 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed inside another nested INSERT, UPDATE, DELETE, or MERGE statement. 10732 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed on either side of a UNION, INTERSECT, or EXCEPT operator. 10733 15 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allow ed in the USING clause of a MERGE statement. 10734 16 Variable assignment is not allowed in a statement containing a t op level UNION, INTERSECT or EXCEPT operator. 10735 15 Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.* ls'. 10736 15 A full-text stoplist statement must be terminated by a semi-colo n (;). 10737 15 In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be sp ecified. The PARTITION=ALL clause is used to reinforce that all partitions of th e table or index will be rebuilt, even if only a subset is specified in the DATA _COMPRESSION clause. 10738 15 The number of row value expressions in the INSERT statement exce eds the maximum allowed number of %d row values. 10739 15 The insert column list used in the MERGE statement cannot contai n multi-part identifiers. Use single part identifiers instead. 10740 15 A search property list statement must end with a semicolon (;). 10741 15 A TOP can not be used in the same query or sub-query as a OFFSET . 10742 15 The offset specified in a OFFSET clause may not be negative. 10743 15 The number of rows provided for a OFFSET clause must be an integ

er. 10744 15 The number of rows provided for a FETCH clause must be greater t hen zero. 10745 15 The FORCESCAN hint is not allowed for target tables of INSERT, U PDATE, or DELETE statements. 10746 15 The FORCESCAN hint is specified simultaneously with the FORCESEE K hint. Remove one of the hints and resubmit the query. 10747 15 The parameterized FORCESEEK hint cannot be simultaneously used w ith INDEX hints or a non-parameterized FORCESEEK hint on the same object. Use ei ther INDEX hints and a non-parameterized FORCESEEK hint or use a parameterized F ORCESEEK hint without INDEX hints for each table or view. 10748 15 There are multiple FORCESEEK hints specified on the same table o r view. Remove the extra FORCESEEK hints and resubmit the query. 10749 15 The FORCESEEK hint cannot be used with index 0. Correct the inde x provided to the FORCESEEK hint and resubmit the query. 10750 15 The FORCESCAN hint cannot be used with more than one INDEX hint. Remove the extra INDEX hints and resubmit the query. 10751 15 The ORDER BY in WITHIN GROUP clause of '%.*ls' function must hav e exactly one expression. 10752 15 The function '%.*ls' may not have a window frame. 10753 15 The function '%.*ls' must have an OVER clause. 10754 15 The function '%.*ls' must have a WITHIN GROUP clause. 10755 15 The function '%.*ls' takes between %d and %d arguments. 10756 15 Window frame with ROWS or RANGE must have an ORDER BY clause. 10757 15 The function '%.*ls' may not have a WITHIN GROUP clause. 10758 15 The function '%.*ls' may not have ORDER BY in OVER clause. 10759 15 Use of DISTINCT is not allowed with the OVER clause. 10760 16 Scale argument is not valid. Valid expressions for data type %ls scale argument are integer constants and integer constant expressions. 10761 16 Invalid data type %.*ls in function %.*ls. 10762 16 The %.*ls function is not allowed in the current compatibility m ode. It is only allowed in 110 mode or higher. 10763 15 GROUP BY clause can only contain one query hint. Remove the extr a hints and re-run the query. 10764 15 Number of grouping columns in the query exceeded maximum number allowed. SQL Server allows 64k grouping columns. Reduce number of grouping colum ns and re-run the query. 10765 15 DISTRIBUTED_AGG and CENTRAL_AGG hints cannot be used with a CUBE or ROLLUP clause. Modify the query and re-run it. 10766 15 CENTRAL_AGG must be specified after all columns in the GROUP BY clause. Modify the query and re-run it. 10767 15 DISTRIBUTED_AGG hint cannot be used when the GROUP BY clause con tains the same column more than once. Modify the query and re-run it. 10768 15 LABEL hint can only be used one time in the query. Modify the qu ery and re-run it. 10770 15 The %S_MSG '%ls' is not supported with in-memory tables. 10771 15 The %S_MSG '%ls' is not yet implemented with in-memory tables. 10772 15 The %S_MSG '%ls' is not supported with natively compiled stored procedures. 10773 15 The %S_MSG '%ls' is not yet implemented with natively compiled s tored procedures. 10774 16 Index '%.*ls' cannot be created on an in-memory table because it is non-covering. 10775 16 Table or view '%.*ls' is not an in-memory table and cannot be ac cessed from a natively compiled stored procedure. 10776 16 Table '%.*ls' is an in-memory table and can only be accessed fro m a natively compiled stored procedure. 10777 16 Procedure '%.*ls' cannot be executed because it is a natively co mpiled procedure that has not been deployed. 10778 16 Cannot create a hekaton table without columns.

10779 16 Deployment failed for procedure '%.*ls' because of compilation e rrors. 10780 16 Conversion from '%ls' to '%ls' is not yet implemented with nativ ely compiled stored procedures. 10781 16 The object '%.*ls' is not an in-memory table. 10782 16 BEGIN ATOMIC is only supported inside natively compiled stored p rocedures. 10783 16 The body of a natively compiled stored procedures must be an ATO MIC block. 10784 16 The WITH clause of BEGIN ATOMIC statement must specify value for the option '%ls'. 10785 15 The %S_MSG '%ls' is not supported with an active xtp transaction . 10786 16 The ALTER AVAILABILITY GROUP command failed because it contained multiple MODIFY REPLICA options: %ls. Enter a separate ALTER AVAILABILITY GROU P ... MODIFY REPLICA command for each replica option that you want to modify. 10800 16 The listener for the WSFC resource '%.*ls' failed to start, and returned error code %d, '%.*ls'. For more information about this error code, see "System Error Codes" in the Windows Development Documentation. 10801 16 Failed to stop the listener for Windows Failover Cluster resourc e '%.*ls'. Error: %d. %.*ls 10802 10 Failed to enqueue a task to register a Service Principal Name (S PN) for the SQL Server service. Kerberos authentication will not be possible unt il a SPN is added manually or SQL Server is restarted. SQLOS error code: %d. 10900 16 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'). 10901 16 User does not have permission to alter the resource governor con figuration. 10902 16 User-defined function '%s' does not exist in master database, or the user does not have permission to access it. 10903 16 The specified schema name '%.*ls' for classifier user-defined fu nction either does not exist, or the user does not have permission to use it. 10904 16 Resource governor configuration failed. There are active session s in workload groups being dropped or moved to different resource pools. Disconn ect all active sessions in the affected workload groups and try again. 10905 16 Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicate d administrator connection. 10906 16 The object '%.*ls'.'%.*ls' is not a valid resource governor clas sifier user-defined function. A valid classifier user-defined function must be s chema-bound, return sysname, and have no parameters. 10907 16 Attribute '%.*ls' with value of %u is greater than attribute '%. *ls' with value of %u. 10908 16 Attribute '%.*ls' with value of %u is less than attribute '%.*ls ' with value of %u. 10909 16 The resource pool cannot be created. The maximum number of resou rce pools cannot exceed current limit of %u including predefined resource pools. 10910 16 The operation could not be completed. The specified '%.*ls' val ue, %u, causes the sum of minimums on all resource pools on scheduler %u to exce ed 100 percent. Reduce the value for one or more pools, or change pool affinity, so that the sum is less than or equal to 100. 10911 16 Requested operation cannot be performed because the resource poo l '%.*ls' does not exist. 10912 16 The operation could not be completed. Dropping predefined %S_MSG is not allowed. 10913 16 Users are not allowed to %S_MSG the workload group '%.*ls' in th e '%.*ls' resource pool. 10914 16 The name of the %S_MSG '%.*ls' cannot begin with # of ##. 10915 16 The operation could not be completed. Altering '%.*ls' %S_MSG is

not allowed. 10916 16 Cannot drop resource pool '%.*ls' because it contains workload g roup '%.*ls'. Drop or remove all workload groups using this resource pool before dropping it. 10917 16 ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified. 10918 16 Cannot create %S_MSG '%.*ls' because it already exists. 10919 16 An error occurred while reading the resource governor configurat ion from master database. Check the integrity of master database or contact the system administrator. 10920 16 Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier. 10921 16 The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG. 10922 16 %ls failed. Rerun the statement. 10923 16 %ls failed. The resource governor is not available in this edit ion of SQL Server. You can manipulate resource governor metadata but you will no t be able to apply resource governor configuration. Only Enterprise edition of S QL Server supports resource governor. 10924 16 The pool affinity range is invalid. The lower bound %d must be l ess than the upper bound %d. 10925 16 A %S_MSG value was specified more than one time in the pool affi nity range list. 10926 16 The %S_MSG range that specifies %S_MSG %d to %d includes at leas t one %S_MSG that is not available to the current instance. The maximum %S_MSG number that is available to this instance is %d. 10927 16 The operation could not be completed. The specified '%.*ls' val ue, %u, causes the sum of minimums on all workload groups using resource pool '% .*ls' to exceed 100 percent. Reduce the value or modify other workload groups so that the sum is less than or equal to 100. 10981 10 Resource governor reconfiguration succeeded. 10982 16 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. 10983 16 Resource governor '%ls' operation was canceled by user. 10984 16 Resource governor reconfiguration failed. 11000 16 Unknown status code for this column. 11001 16 Non-NULL value successfully returned. 11002 16 Deferred accessor validation occurred. Invalid binding for this column. 11003 16 Could not convert the data value due to reasons other than sign mismatch or overflow. 11004 16 Successfully returned a NULL value. 11005 16 Successfully returned a truncated value. 11006 16 Could not convert the data type because of a sign mismatch. 11007 16 Conversion failed because the data value overflowed the data typ e used by the provider. 11008 16 The provider cannot allocate memory or open another storage obje ct on this column. 11009 16 The provider cannot determine the value for this column. 11010 16 The user did not have permission to write to the column. 11011 16 The data value violated the integrity constraints for the column . 11012 16 The data value violated the schema for the column. 11013 16 The column had a bad status. 11014 16 The column used the default value. 11015 16 The column was skipped when setting data. 11031 16 The row was successfully deleted. 11032 16 The table was in immediate-update mode, and deleting a single ro w caused more than one row to be deleted in the data source. 11033 16 The row was released even though it had a pending change.

11034 16 Deletion of the row was canceled during notification. 11036 16 The rowset was using optimistic concurrency and the value of a c olumn has been changed after the containing row was last fetched or resynchroniz ed. 11037 16 The row has a pending delete or the deletion had been transmitte d to the data source. 11038 16 The row is a pending insert row. 11039 16 DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion fo r the row has been transmitted to the data source. 11040 16 Deleting the row violated the integrity constraints for the colu mn or table. 11041 16 The row handle was invalid or was a row handle to which the curr ent thread does not have access rights. 11042 16 Deleting the row would exceed the limit for pending changes spec ified by the rowset property DBPROP_MAXPENDINGROWS. 11043 16 The row has a storage object open. 11044 16 The provider ran out of memory and could not fetch the row. 11045 16 User did not have sufficient permission to delete the row. 11046 16 The table was in immediate-update mode and the row was not delet ed due to reaching a limit on the server, such as query execution timing out. 11047 16 Updating did not meet the schema requirements. 11048 16 There was a recoverable, provider-specific error, such as an RPC failure. 11100 16 The provider indicates that conflicts occurred with other proper ties or requirements. 11101 16 Could not obtain an interface required for text, ntext, or image access. 11102 16 The provider could not support a required row lookup interface. 11103 16 The provider could not support an interface required for the UPD ATE/DELETE/INSERT statements. 11104 16 The provider could not support insertion on this table. 11105 16 The provider could not support updates on this table. 11106 16 The provider could not support deletion on this table. 11107 16 The provider could not support a row lookup position. 11108 16 The provider could not support a required property. 11109 16 The provider does not support an index scan on this data source. 11201 16 This message could not be delivered because the FROM service nam e is missing. The message origin is: '%ls'. 11202 16 This message has been dropped because the FROM service name exce eds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls". 11203 16 This message has been dropped because the FROM broker instance i s missing. The message origin is '%ls'. 11204 16 This message has been dropped because the FROM broker instance e xceeds the maximum size of %d bytes. Broker instance: "%.*ls". Message origin: " %ls". 11205 16 This message has been dropped because the TO service name is mis sing. The message origin is "%ls". 11206 16 This message has been dropped because the TO service name exceed s the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls". 11207 16 This message has been dropped because the service contract name is missing. The message origin is "%ls". 11208 16 This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name "%.*ls". Message origin: "%l s". 11209 16 This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: '%ls '. 11210 16 This message has been dropped because the TO service could not b e found. Service name: "%.*ls". Message origin: "%ls". 11211 16 This message has been dropped because the user does not have per

mission to access the target database. Database ID: %d. Message origin: &amp;quo t;%ls&amp;quot;. 11212 16 This message could not be delivered because the conversation end point has already been closed. 11213 16 This message could not be delivered because this is not the firs t message in the conversation. 11214 16 This message could not be delivered because the '%.*ls' contract could not be found or the service does not accept conversations for the contrac t. 11215 16 This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: '%.*ls'. 11216 16 This message could not be delivered because there is already ano ther task processing this message. 11217 16 This message could not be delivered because it is out of sequenc e with respect to the conversation. Conversation receive sequence number: %I64d, Message sequence number: %I64d. 11218 16 This message could not be delivered because it is a duplicate. 11219 16 This message could not be delivered because the destination queu e has been disabled. Queue ID: %d. 11220 16 This message could not be delivered because the TO broker instan ce is missing. 11221 16 This message could not be delivered because there is an inconsis tency in the message header. 11222 16 This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Service Name: '%.*ls'. Conversation Endpoint TO Service Name: '%.*ls'. 11223 16 This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Messa ge service contract name: '%.*ls'. Conversation endpoint service contract name: '%.*ls'. 11224 16 This message could not be delivered because another instance of this service program has already started conversing with this endpoint. 11225 16 This message could not be delivered because the message type nam e could not be found. Message type name: '%.*ls'. 11226 16 This message could not be delivered because the message type is not part of the service contract. Message type name: '%.*ls'. Service contract n ame: '%.*ls'. 11227 16 This message could not be delivered because the initiator servic e has sent a message with a message type that can only be sent by the target. Me ssage type name: '%.*ls'. Service contract name: '%.*ls'. 11228 16 This message could not be delivered because the target service h as sent a message with a message type that can only be sent by the initiator. Me ssage type name: '%.*ls'. Service contract name: '%.*ls'. 11229 16 This message could not be delivered because the security context could not be retrieved. 11230 16 This message could not be delivered because the message could no t be decrypted and validated. 11231 16 This message could not be delivered because the conversation end point is not secured, however the message is secured. 11232 16 This message could not be delivered because the conversation end point is secured, however the message is not secured. 11233 16 This message has been dropped because the session key of the con versation endpoint does not match that of the message. 11234 16 This message could not be delivered because an internal error wa s encountered while processing it. Error code %d, state %d: %.*ls. 11235 16 Received a malformed message. The binary message class (%d:%d) i s not defined. This may indicate network problems or that another application is connected to the Service Broker endpoint. 11236 16 A corrupted message has been received. The binary header size of

%d is expected, however the header size received was %d. 11237 16 A %S_MSG message could not be processed due to insufficient memo ry. The message was dropped. 11238 16 A corrupted message has been received. The private variable data segment is malformed. 11239 16 A corrupted message has been received. The private variable data segment extends beyond the length of the message. 11240 16 A corrupted message has been received. The binary message preamb le is malformed. 11241 16 A corrupted message has been received. The conversation security version number is not %d.%d. 11242 16 A corrupted message has been received. The maximum number of pub lic variable data elements (%d) has been exceeded. Public variable data elements found: %d. 11243 16 A corrupted message has been received. The public variable data element (%d) has been duplicated in this message. 11244 16 A corrupted message has been received. The handshake validation header is malformed. 11245 16 A corrupted message has been received. The maximum number of pri vate variable data elements (%d) has been exceeded. Private variable data elemen ts found: %d. 11246 16 A corrupted message has been received. The private variable data element (%d) has been duplicated in this message. 11247 16 A corrupted message has been received. The login negotiate heade r is invalid. 11248 16 A corrupted message has been received. The SSPI login header is invalid. 11249 16 A corrupted message has been received. The pre-master-secret is invalid. 11250 16 A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11251 16 A corrupted message has been received. The service pair security header source certificate and the signature must both be present or both be abs ent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, a nd Message sequence number: %I64d. 11252 16 A corrupted message has been received. The destination certifica te serial number is missing. This occurred in the message with Conversation ID ' %.*ls', Initiator: %d, and Message sequence number: %I64d. 11253 16 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 m essage with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11254 16 A corrupted message has been received. The session key ID is mis sing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11255 16 A corrupted message has been received. The encryption flag is se t, however the message body, MIC or salt is missing. This occurred in the messag e with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64 d. 11256 16 A corrupted message has been received. The MIC is present, howev er the message body or encryption flag is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11257 16 A corrupted message has been received. The MIC and session key I D are in an invalid state. This occurred in the message with Conversation ID '%. *ls', Initiator: %d, and Message sequence number: %I64d. 11258 16 A corrupted message has been received. The MIC size is %d, howev er it must be no greater than %d bytes in length. This occurred in the message w ith Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.

11259 16 A corrupted message has been received. The certificate serial nu mber size is %d, however it must be no greater than %d bytes in length. This occ urred in the message with Conversation ID '%.*ls', Initiator: %d, and Message se quence number: %I64d. 11260 16 A corrupted message has been received. The certificate issuer na me size is %d, however it must be no greater than %d bytes in length. This occur red in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequ ence number: %I64d. 11261 16 A corrupted message has been received. The destination certifica te serial number size is %d, however it must be no greater than %d bytes in leng th. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, an d Message sequence number: %I64d. 11262 16 A corrupted message has been received. The destination certifica te issuer name size is %d, however it must be no greater than %d bytes in length . This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11263 16 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 n umber: %I64d. 11264 16 A corrupted message has been received. The key exchange key size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d . 11265 16 A corrupted message has been received. The key exchange key ID i s invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11266 16 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 Conv ersation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11267 16 A corrupted message has been received. The session key ID size i s %d, however it must be %d bytes. This occurred in the message with Conversatio n ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11268 16 A corrupted message has been received. The salt size is %d, howe ver it must be %d bytes. This occurred in the message with Conversation ID '%.*l s', Initiator: %d, and Message sequence number: %I64d. 11269 16 A corrupted message has been received. A UNICODE string is not t wo byte aligned within the message. This occurred in the message with Conversati on ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11270 16 A corrupted message has been received. A UNICODE string is great er than the maximum allowed size of %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11271 16 A corrupted message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ID '%.*ls', Initiato r: %d, and Message sequence number: %I64d. 11272 16 A corrupted message has been received. The message ID must not b e NULL. 11273 16 A corrupted message has been received. The message body is not p roperly padded for encryption. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11274 16 A corrupted message has been received. A sequence number is larg er than allowed. This occurred in the message with Conversation ID '%.*ls', Init iator: %d, and Message sequence number: %I64d. 11275 16 A corrupted message has been received. The End of Conversation a nd Error flags are both set. This occurred in the message with Conversation ID ' %.*ls', Initiator: %d, and Message sequence number: %I64d. 11276 16 A corrupted message has been received. The End of Conversation f lag has been set on an unsequenced message. This occurred in the message with Co nversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11277 16 A corrupted message has been received. The End of Conversation a

nd Error flags may not be set in the first sequenced message. This occurred in t he message with Conversation ID '%.*ls', Initiator: %d, and Message sequence num ber: %I64d. 11278 16 A corrupted message has been received. The message type is missi ng for this message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11279 16 A corrupted message has been received. The message type must not be set in this message. This occurred in the message with Conversation ID '%.*l s', Initiator: %d, and Message sequence number: %I64d. 11280 16 A packet of size %lu bytes could not be processed because it exc eeds the receive buffer count. 11281 16 A corrupted message has been received. The private portion of th e message header is malformed. 11282 16 This message has been dropped due to licensing restrictions. See the documentation for further details. 11285 16 This forwarded message has been dropped because the hops remaini ng count has reached 0. 11286 16 Dropped this forwarded message because this SQL Server instance is out of memory. 11288 16 This forwarded message has been dropped because a duplicate mess age is already being forwarded. 11289 16 This forwarded message has been dropped because its memory usage would exceed the configured memory limit of %d bytes for forwarded messages. 11290 16 This forwarded message was dropped because the message could not be delivered within the message time to live. This may indicate that the forwar ding route is incorrectly configured or that the destination is unavailable. 11291 16 This forwarded message has been dropped because the time consume d has exceeded the message's time to live of %u seconds (the message arrived wit h %u seconds consumed and used %u seconds in this broker). 11292 16 The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events for the error. 11293 16 This forwarded message has been dropped because a transport is s hutdown. 11294 16 This forwarded message has been dropped because the destination route is not valid. 11295 10 Endpoint configuration change detected. Service Broker manager and transport will now restart. 11296 10 Certificate change detected. Service Broker manager and transpo rt will now restart. 11297 16 A corrupted message has been received. The private variable data segment offset is incorrect. 11298 16 A corrupted message has been received. The public variable data segment offset is incorrect. 11299 10 A corrupted message has been received. An unsequenced message ha d a non-zero sequence number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 11300 10 Error wile committing a readonly or a TEMPDB XDES, Shutting down the server. 11301 10 Error while performing transaction notification for object %p ev ent %d. 11302 10 Error during rollback. shutting down database (location: %d). 11303 10 Error releasing reserved log space: %ls space %I64d, code %d, st ate %d. 11304 10 Failed to record outcome of a local two-phase commit transaction . Taking database offline. 11306 16 Forward progress on this transaction is disallowed. Transaction has been rolled back. 11313 16 This operation must be executed within a parallel nested transac tion. 11314 16 The stored procedure %.*ls must be executed within a user transa

ction. 11315 16 The isolation level specified for the PNT child transaction does not match the current isolation level for the parent. 11316 16 %ls statement cannot be used inside a parallel nested transactio n. 11317 16 Parallel plan with updates is not supported inside a parallel ne sted transaction. 11318 16 The stored procedure '%.*ls' cannot be executed through MARS con nection. 11319 16 Bound sessions and user parallel nested transactions cannot be u sed in the same transaction. 11320 16 Cannot create a User Parallel Nested Transaction, the maximum nu mber of parallel nested transactions is reached. 11321 16 This operation cannot be executed within an active transaction. 11400 16 ALTER TABLE SWITCH statement failed. Index '%.*ls' on indexed vi ew '%.*ls' uses partition function '%.*ls', but table '%.*ls' uses non-equivalen t partition function '%.*ls'. Index on indexed view '%.*ls' and table '%.*ls' mu st use an equivalent partition function. 11401 16 ALTER TABLE SWITCH statement failed. Table '%.*ls' is %S_MSG, bu t index '%.*ls' on indexed view '%.*ls' is %S_MSG. 11402 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' is ref erenced by %d indexed view(s), but source table '%.*ls' is only referenced by %d indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the source table. 11403 16 ALTER TABLE SWITCH statement failed. Indexed view '%.*ls' is not aligned with table '%.*ls'. The partitioning column '%.*ls' from the indexed vi ew calculates its value from one or more columns or an expression, rather than d irectly selecting from the table partitioning column '%.*ls'. Change the indexed view definition, so that the partitioning column is directly selected from tabl e partitioning column '%.*ls'. 11404 16 ALTER TABLE SWITCH statement failed. Target table '%.*ls' is ref erenced 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 l east one matching indexed view on the source table. 11405 16 ALTER TABLE SWITCH statement failed. Table '%.*ls' is not aligne d with the index '%.*ls' on indexed view '%.*ls'. The table is partitioned on co lumn '%.*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 tabl e's partitioning column. 11406 16 ALTER TABLE SWITCH statement failed. Source and target partition s have different values for the DATA_COMPRESSION option. 11407 16 Vardecimal storage format can not be enabled for '%.*ls'. Only E nterprise edition of SQL Server supports vardecimal. 11408 16 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, e ither modify the table to remove the column and then add the column again, or dr op and re-create the table. 11409 16 Cannot remove the column set '%.*ls' in the table '%.*ls' becaus e the table contains more than 1025 columns. Reduce the number of columns in th e table to less than 1025. 11410 16 Cannot modify the column '%.*ls' in the table '%.*ls' to a spars e column because the column has a default or rule bound to it. Unbind the rule o r default from the column before designating the column as sparse. 11411 16 Cannot add the sparse column '%.*ls' to the table '%.*ls' becaus e the data type of the column has a default or rule bound to it. Unbind the rule or default from the data type before adding the sparse column to the table. 11412 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'. 11413 16 ALTER TABLE SWITCH statement failed because column '%.*ls' does

not have the same column set property in tables '%.*ls' and '%.*ls'. 11414 10 Warning: Option %ls is not applicable to table %.*ls because it does not have a clustered index. This option will be applied only to the table's nonclustered indexes, if it has any. 11415 16 Object '%.*ls' cannot be disabled or enabled. This action applie s only to foreign key and check constraints. 11418 16 Cannot %S_MSG table '%.*ls' because the table either contains sp arse columns or a column set column which are incompatible with compression. 11419 16 Cannot alter or drop column '%.*ls' because the table '%.*ls' is federated on it. 11501 16 The batch could not be analyzed because of compile errors. 11502 16 The type for parameter '%.*ls' cannot be deduced in this context . 11503 16 The parameter type cannot be deduced because a single expression contains two untyped parameters, '%.*ls' and '%.*ls'. 11504 16 The discovered type with user type id %d in database %d is inval id. 11505 16 The discovered type with the XML schema collection id %d in data base %d is invalid. 11506 16 The parameter type for '%.*ls' cannot be uniquely deduced; two p ossibilities are '%ls' and '%ls'. 11507 16 The parameter type for '%.*ls' cannot be deduced because no type would make the query valid. 11508 16 The undeclared parameter '%.*ls' is used more than once in the b atch being analyzed. 11509 16 The metadata could not be determined because the statement '%.*l s' is not compatible with the statement '%.*ls'. 11510 16 The metadata could not be determined because the statement '%.*l s' in the main batch is not compatible with the statement '%.*ls' in procedure ' %.*ls'. 11511 16 The metadata could not be determined because the statement '%.*l s' in procedure '%.*ls' is not compatible with the statement '%.*ls' in the main batch. 11512 16 The metadata could not be determined because the statement '%.*l s' in procedure '%.*ls' is not compatible with the statement '%.*ls' in procedur e '%.*ls'. 11513 16 The metadata could not be determined because statement '%.*ls' c ontains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly d escribe the result set. 11514 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set. 11515 16 The metadata could not be determined because statement '%.*ls' i nvokes a CLR procedure. Consider using the WITH RESULT SETS clause to explicitl y describe the result set. 11516 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' invokes a CLR procedure. Consider using the WITH RESULT SET S clause to explicitly describe the result set. 11517 16 The metadata could not be determined because statement '%.*ls' i nvokes a CLR trigger. 11518 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' invokes a CLR trigger. 11519 16 The metadata could not be determined because statement '%.*ls' i nvokes an extended stored procedure. 11520 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' invokes an extended stored procedure. 11521 16 The metadata could not be determined because statement '%.*ls' u ses an undeclared parameter in a context that affects its metadata. 11522 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' uses an undeclared parameter in a context that affects its m

etadata. 11523 16 The metadata could not be determined because statement '%.*ls' c auses indirect recursion. 11524 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' causes indirect recursion. 11525 16 The metadata could not be determined because statement '%.*ls' u ses a temp table. 11526 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' uses a temp table. 11527 16 The metadata could not be determined because statement '%.*ls' d oes not support metadata discovery. 11528 16 The metadata could not be determined because statement '%.*ls' i n procedure '%.*ls' does not support metadata discovery. 11529 16 The metadata could not be determined because every code path res ults in an error; see previous errors for some of these. 11530 16 The metadata could not be determined because there are no code p aths that reach the end of the batch. 11531 16 The object id '%d' passed to sys.dm_exec_describe_first_result_s et_for_object refers to an object which is not a T-SQL procedure or trigger. 11532 16 The object id '%d' passed to sys.dm_exec_describe_first_result_s et_for_object was invalid. 11533 16 Type '%.*ls' is not a valid object name for result set definitio n. 11534 16 Type '%.*ls' is invalid or not a table type. 11535 16 EXECUTE statement failed because its WITH RESULT SETS clause spe cified %d result set(s), and the statement tried to send more result sets than t his. 11536 16 EXECUTE statement failed because its WITH RESULT SETS clause spe cified %d result set(s), but the statement only sent %d result set(s) at run tim e. 11537 16 EXECUTE statement failed because its WITH RESULT SETS clause spe cified %d column(s) for result set number %d, but the statement sent %d column(s ) at run time. 11538 16 EXECUTE statement failed because its WITH RESULT SETS clause spe cified type '%ls' for column #%d in result set #%d, and the corresponding type s ent at run time was '%ls'; there is no conversion between the two types. 11539 16 One of the types specified in WITH RESULT SETS clause has been m odified after the EXECUTE statement started running. Please rerun the statement . 11541 16 sp_describe_first_result_set cannot be invoked when SET STATISTI CS XML or SET STATISTICS PROFILE is on. 11542 16 sp_describe_undeclared_parameters failed to discover parameter m etadata for remote procedure call because parameters were passed by name and by name parameter metadata discovery failed. 11543 16 SET STATISTICS XML ON and SET STATISTICS PROFILE ON are not allo wed inside any procedure or batch that executes through an EXECUTE statement tha t has a WITH RESULT SETS clause. 11544 16 Could not deduce type for parameter in position '%d' for remote call to module '%.*ls'. 11545 16 Remote result set discovery cannot be done inside SELECT INTO. 11546 16 sp_showmemo_xml cannot run when the STATISTICS XML, STATISTICS P ROFILE or SHOWPLAN set option is on. Set these options to OFF and re-run sp_sho wmemo_xml. 11547 16 Only one statement can be used as input parameter to sp_showmemo _xml. Modify the input parameter and re-run the stored procedure. 11548 16 The stored procedure 'sp_showmemo_xml' is not available in this edition of SQL Server. 11549 16 Using stored procedures is not supported. Modify the input param eter and re-run sp_showmemo_xml. 11550 16 The metadata could not be determined because remote metadata dis

covery failed for statement '%.*ls'. 11551 16 The metadata could not be determined because remote metadata dis covery failed for statement '%.*ls' in procedure '%.*ls'. 11552 16 The @browse_information_mode parameter expects a tinyint with va lues 0, 1 or 2. 11553 16 EXECUTE statement failed because its WITH RESULT SETS clause spe cified a non-nullable type for column #%d in result set #%d, and the correspondi ng value sent at run time was null. 11601 15 %ls statements with a '%.*ls' option are not allowed. 11602 10 %ls statements are not verified. 11603 15 %ls statements are not allowed at the top level. 11605 15 %S_MSG are not allowed at the top level. 11606 15 Specifying server name in '%.*ls' is not allowed. 11607 15 Specifying database name for '%.*ls' in a %ls statement is not a llowed. 11608 15 Creating temporary stored procedures is not allowed. 11609 16 An internal error occurred while building the project. %ls 11610 16 There is not enough memory to build the project. 11611 15 Specifying schema elements in the CREATE SCHEMA statement is not supported. 11612 15 Multiple statements in a T-SQL batch are not allowed at the top level. 11613 15 Numbered stored procedures are not supported. 11614 15 %ls is not supported. 11617 16 An unknown error has occurred trying to load '%hs'. 11618 15 Combining column level permissions with other permissions is not allowed in the same GRANT/DENY/REVOKE statement. 11619 16 There is not enough stack available to compile the statment. 11620 15 REVOKE statements can only be used to revoke column level permis sions. 11621 10 SQL Server started in Language Service mode. 11622 16 CREATE ASSEMBLY can only be created FROM a constant binary expre ssion. 11623 15 ALTER TABLE statements can only be used to add a single constrai nt. 11624 15 ALTER ROLE statements can only be used to add a member to a role . 11625 16 '%ls' is either corrupt, not readable or not accessible. 11651 10 %ls statements with a '%.*ls' option are not supported in a data -tier application. 11652 10 %ls statements are not supported at the top level in a data-tier application. 11653 10 Cannot execute as the user '%.*ls' because it does not exist. 11700 16 The increment for sequence object '%.*ls' cannot be zero. 11701 16 The absolute value of the increment for sequence object '%.*ls' must be less than or equal to the difference between the minimum and maximum val ue of the sequence object. 11702 16 The sequence object '%.*ls' must be of data type int, bigint, sm allint, tinyint, or decimal or numeric with a scale of 0, or any user-defined da ta type that is based on one of the above integer data types. 11703 16 The start value for sequence object '%.*ls' must be between the minimum and maximum value of the sequence object. 11704 16 The current value '%.*ls' for sequence object '%.*ls' must be be tween the minimum and maximum value of the sequence object. 11705 16 The minimum value for sequence object '%.*ls' must be less than its maximum value. 11706 16 The cache size for sequence object '%.*ls' must be greater than 0. 11707 10 The cache size for sequence object '%.*ls' has been set to NO CA CHE.

11708 16 An invalid value was specified for argument '%.*ls' for the give n data type. 11709 15 The 'RESTART WITH' argument cannot be used in a CREATE SEQUENCE statement. 11710 15 Argument 'START WITH' cannot be used in an ALTER SEQUENCE statem ent. 11711 15 Argument 'AS' cannot be used in an ALTER SEQUENCE statement. 11712 15 Argument '%.*ls' can not be specified more than once. 11714 15 Invalid sequence name '%.*ls'. 11715 15 No properties specified for ALTER SEQUENCE. 11716 15 NEXT VALUE FOR function does not support the PARTITION BY clause . 11717 15 NEXT VALUE FOR function does not support the OVER clause in defa ult constraints, UPDATE statements, or MERGE statements. 11718 15 NEXT VALUE FOR function does not support an empty OVER clause. 11719 15 NEXT VALUE FOR function is not allowed in check constraints, def ault objects, computed columns, views, user-defined functions, user-defined aggr egates, user-defined table types, sub-queries, common table expressions, or deri ved tables. 11720 15 NEXT VALUE FOR function is not allowed in the TOP, OVER, OUTPUT, ON, WHERE, GROUP BY, HAVING, or ORDER BY clauses. 11721 15 NEXT VALUE FOR function cannot be used directly in a statement t hat uses a DISTINCT, UNION, UNION ALL, EXCEPT or INTERSECT operator. 11722 15 NEXT VALUE FOR function is not allowed in the WHEN MATCHED claus e, the WHEN NOT MATCHED clause, or the WHEN NOT MATCHED BY SOURCE clause of a me rge statement. 11723 15 NEXT VALUE FOR function cannot be used directly in a statement t hat contains an ORDER BY clause unless the OVER clause is specified. 11724 15 An expression that contains a NEXT VALUE FOR function cannot be passed as an argument to a table-valued function. 11725 15 An expression that contains a NEXT VALUE FOR function cannot be passed as an argument to an aggregate. 11726 16 Object '%.*ls' is not a sequence object. 11727 16 NEXT VALUE FOR functions for a given sequence object must have e xactly the same OVER clause definition. 11728 16 The sequence object '%.*ls' has reached its minimum or maximum v alue. Restart the sequence object to allow new values to be generated. 11729 10 The sequence object '%.*ls' cache size is greater than the numbe r of available values; the cache size has been automatically set to accommodate the remaining sequence values. 11730 16 Database name cannot be specified for the sequence object in def ault constraints. 11731 16 A column that uses a sequence object in the default constraint m ust be present in the target columns list, if the same sequence object appears i n a row constructor. 11732 16 The requested range for sequence object '%.*ls' exceeds the maxi mum or minimum limit. Retry with a smaller range. 11733 16 Parameter '%.*ls' must be a positive integer. 11734 16 NEXT VALUE FOR function is not allowed in the SELECT clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 11735 16 The target table of the INSERT statement cannot have DEFAULT con straints using the NEXT VALUE FOR function when the FROM clause contains a neste d INSERT, UPDATE, DELETE, or MERGE statement. 11736 16 Only one instance of NEXT VALUE FOR function per sequence object is allowed in SET or SELECT with variable assignment. 11737 15 NEXT VALUE FOR function does not support the ROWS and RANGE clau ses. 11738 16 The use of NEXT VALUE FOR function is not allowed in this contex t. 11739 16 NEXT VALUE FOR function cannot be used if ROWCOUNT option has be

en set, or the query contains TOP or OFFSET. 11740 16 NEXT VALUE FOR function cannot be used in a default constraint i f ROWCOUNT option has been set, or the query contains TOP or OFFSET. 11741 16 NEXT VALUE FOR function cannot be used within CASE, CHOOSE, COAL ESCE, IIF, ISNULL and NULLIF. 11742 16 NEXT VALUE FOR function can only be used with MERGE if it is def ined within a default constraint on the target table for insert actions. 11800 16 RESTORE WITH SNAPSHOTRESTOREPHASE=2 for database '%ls' failed be cause an earlier RESTORE WITH SNAPSHOTRESTOREPHASE=1 may have failed as a result of a network error. Retry the restore operation through SQL Writer after addres sing any network issues and making sure that SQL Server is running. 11901 16 Column '%.*ls.%.*ls' is a federated column, while referencing co lumn '%.*ls.%.*ls' in foreign key '%.*ls' is not. 11902 16 Federation scheme key '%.*ls' is not a part of this federation. 12002 16 The requested %S_MSG index on column '%.*ls' of table '%.*ls' co uld not be created because the column type is not %S_MSG . Specify a column name that refers to a column with a %S_MSG data type. 12003 16 Could not find spatial tessellation scheme '%.*ls' for column of type %.*ls. Specify a valid tessellation scheme name in your USING clause. 12004 16 Could not find the default spatial tessellation scheme for the c olumn '%.*ls' on table '%.*ls'. Make sure that the column reference is correct, or specify the extension scheme in a USING clause. 12005 16 Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax. 12006 16 Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax. 12007 16 The CREATE %S_MSG statement is missing the required parameter '% .*ls'. Validate the statement against the index-creation syntax. 12008 16 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 b efore creating a %S_MSG index. 12009 16 Could not find the %S_MSG index '%.*ls' on table '%.*ls'. Either no %S_MSG index with this name exists, or a non-%S_MSG index might be using the same name. Fix the index name, avoiding duplicates. If a relational index has the same name, drop the regular relational index. 12010 16 Only one spatial index hint may appear per table, either as the first or the last hinted index. 12011 16 The value of parameter '%.*ls' of CREATE %S_MSG must be less tha n %d. 12012 16 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d. 12013 16 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than the value of parameter '%.*ls'. 12014 16 The '%.*ls' parameter of CREATE %S_MSG is incompletely defined. If the parameter has more than one part, all the parts must be defined. 12015 16 The index option %.*ls in the CREATE %S_MSG statement has to app ear before the general index options. 12016 16 Creating a %S_MSG index requires that the primary key in the ba se table satisfy the following restrictions. The maximum number of primary-key c olumns 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 b y the %S_MSG index. 12017 10 The spatial index is disabled or offline 12018 10 The spatial object is not defined in the scope of the predicate 12019 10 Spatial indexes do not support the comparand supplied in the pre dicate 12020 10 Spatial indexes do not support the comparator supplied in the pr edicate 12021 10 Spatial indexes do not support the method name supplied in the p

redicate 12022 10 The comparand references a column that is defined below the pred icate 12023 10 The comparand in the comparison predicate is not deterministic 12024 10 The spatial parameter references a column that is defined below the predicate 12025 10 Could not find required binary spatial method in a condition 12026 10 Could not find required comparison predicate 12101 16 Cannot disable change tracking on database '%.*ls' while client connections are waiting on change notification. Please close those connections before disabling change tracking. 12104 15 ALTER DATABASE CURRENT failed because '%.*ls' is a system databa se. System databases cannot be altered by using the CURRENT keyword. Use the dat abase name to alter a system database. 12800 16 The reference to temp table name '%.*ls' is ambiguous and cannot be resolved. Use either '%.*ls' or '%.*ls'. 12801 16 The reference to cursor name '%.*ls' is ambiguous and cannot be resolved. Possible candidates are '%.*ls' and '%.*ls'. 12803 16 Containment cannot be enabled for database '%.*ls' because it is a system database. 12804 16 Feature or option "%ls" breaches containment in a contained data base. Please see Books Online topic Understanding Contained Databases for more i nformation on contained databases. 12805 16 Index name '%.*ls' is too long. Maximum length for temp table in dex name is %d characters. 12807 16 The option '%.*ls' cannot be set on non-contained database. 12808 16 The option '%.*ls' cannot be set on a database while containment is being set to NONE. 12810 16 The option '%.*ls' was specified multiple times. 12811 16 The user options for the instance must be set to 0 in order to % S_MSG a contained database. 12813 16 Errors were encountered in the %S_MSG '%.*ls' during compilation of the object. Either the containment option of the database '%.*ls' was change d, or this object was present in model db and the user tried to create a new con tained database. 12814 16 The object referenced as '%.*ls' resolves differently in the tar get metadata collation '%.*ls' than in the current metadata collation '%.*ls'. 12815 16 The column referenced as '%.*ls' resolves differently in the tar get metadata collation '%.*ls' than in the current metadata collation '%.*ls'. 12816 16 The type or XML schema collection referenced as '%.*ls' resolves differently in the target metadata collation '%.*ls' than in the current metada ta collation '%.*ls'. 12817 16 The reference to the variable, parameter or goto label '%.*ls' r esolves differently in the target metadata collation '%.*ls' than in the current metadata collation '%.*ls'. 12818 16 RECONFIGURE failed. Attempting to change the 'contained database authentication' value to 0 while there are existing contained databases require s a RECONFIGURE WITH OVERRIDE. 12819 16 sp_migrate_user_to_contained cannot be used in a non-contained d atabase (a database with CONTAINMENT set to NONE). 12820 16 sp_migrate_user_to_contained can not be used with a user with a password or a user type other than SQL Login. 12821 16 sp_migrate_user_to_contained cannot be used on a user used in th e EXECUTE AS clause of a signed module. 12822 16 sp_migrate_user_to_contained cannot be used to copy a password t o an old hash algorithm. 12823 16 sp_migrate_user_to_contained can not find the login for user '%. *ls'. 12824 16 The sp_configure value 'contained database authentication' must be set to 1 in order to %S_MSG a contained database. You may need to use RECONF

IGURE to set the value_in_use. 12825 16 The database cannot be contained; this functionality is not avai lable in the current edition of SQL Server. 12826 16 RECONFIGURE WITH OVERRIDE set the 'contained database authentica tion' to 0 while there are contained databases in use. This will disrupt authent ication for contained users and will not allow new contained databases to be cre ated. 12827 16 User-named %ls constraint '%.*ls' is not allowed on temp table ' %.*ls' because it is being created in a contained database. Please consult the B ooks Online topic Understanding Contained Databases for more information on cont ained databases. 12828 16 User-defined %S_MSG '%.*ls' in tempdb cannot be referenced from local temp table '%.*ls' because the temp table is being created in a contained database. Please consult the Books Online topic Understanding Contained Database s for more information on contained databases. 12829 16 The stored procedure '%.*ls' refers to a group of numbered store d procedures. Numbered stored procedures are not available in contained database s. Please consult the Books Online topic Understanding Contained Databases for m ore information on contained databases. 12830 16 The sp_configure 'user options' setting must be zero if the Data base Engine has contained databases. 12831 16 Database '%.*ls' is a contained database. The option 'contained database authentication' setting is 0. Users with passwords will not be able to login to contained databases. 12832 16 The database '%.*ls' could not be created or altered to a contai ned database, because the schema bound %S_MSG '%.*ls' depends on builtin functio n '%s'. In a contained database, the output collation of this builtin function h as changed to '%.*ls', which differs from the collation used in a non-contained database. 12833 16 The database '%.*ls' could not be created or altered to a contai ned database, because the check constraint '%.*ls' on table '%.*ls' depends on b uiltin function '%s'. In a contained database, the output collation of this buil tin function has changed to '%.*ls', which differs from the collation used in a non-contained database. 12834 16 The database '%.*ls' could not be created or altered to a contai ned database, because the computed column '%.*ls' on %S_MSG '%.*ls' depends on b uiltin function '%s'. In a contained database, the output collation of this buil tin function has changed to '%.*ls', which differs from the collation used in a non-contained database. 12835 10 The definition of the %S_MSG '%.*ls' was refreshed as part of al tering the containment option of the database '%.*ls' because the object depends on builtin function '%s'. In a contained database, the output collation of this builtin function has changed to '%.*ls', which differs from the collation used in a non-contained database. 12836 16 ALTER DATABASE statement failed. The containment option of the d atabase '%.*ls' could not be altered because compilation errors were encountered during validation of SQL modules. See previous errors. 12837 16 CREATE DATABASE statement failed. The contained database '%.*ls' could not be created because compilation errors were encountered during validat ion of SQL modules. See previous errors. 12838 16 Replication, Change Data Capture and Change Tracking are not sup ported in contained databases. The database '%.*ls' cannot be altered to a conta ined database, since it has one of these options turned on. 12839 16 Replication, Change Data Capture and Change Tracking are not sup ported in contained databases. The option cannot be enabled on the contained dat abase '%s'. 12840 16 CREATE DATABASE failed. Recollating the database failed while cr eating the partially contained database '%.*ls', with a default data collation o f '%.*ls'. 12841 16 ALTER DATABASE failed. Recollating the database failed while alt

ering the database '%.*ls' to containment='%ls'. 12842 16 The COLLATE CATALOG_DEFAULT clause cannot be used in a constrain t, computed column, index filter expression, or any schema-bound object. 12843 16 The containment state of database '%.*ls' does not match the val ue in master. Contained database functionality will not work as expected. Detach and re-attach the database to correct the database state in master. 12980 16 Supply either %s or %s to identify the log entries. 12981 16 You must specify %s when creating a subplan. 12982 16 Supply either %s or %s to identify the plan or sub-plan to be ru n. 13001 16 file name 13002 16 audit 13003 16 audit specification 13004 16 audit name 13005 16 server role 13006 16 server principal 13008 0 receive 13010 0 read 13012 0 a USE database statement 13013 0 a procedure, function or trigger 13014 0 indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations 13015 0 spatial index operations 13016 0 an INTO clause 13019 0 a SELECT INTO statement 13020 0 option 13021 0 offset option 13022 0 statistics option 13024 0 function name 13025 0 varbinary (128) NOT NULL 13026 0 parameter 13027 0 convert specification 13028 0 index 13029 0 table 13030 0 database 13031 0 procedure 13032 0 trigger 13033 0 view 13034 0 default 13035 0 rule 13036 0 system table 13037 0 unknown type 13038 0 SET option 13039 0 column 13040 0 type 13041 0 character string 13042 0 integer 13043 0 identifier 13044 0 number 13045 0 indexes 13047 0 object 13049 0 built-in function name 13050 0 aggregate function 13051 0 XML INDEX 13052 0 CLR type 13053 0 xml schema collection 13054 0 EXTENDED INDEX 13055 0 SPATIAL INDEX 13056 0 spatial

13057 13058 13059 13060 13076 13077 13078 13079 13080 13081 13082 13083 13084 13085 13086 13087 13088 13089 13090 13092 13093 13094 13095 13096 13097 13098 13099 13100 13101 13102 13105 13106 13107 13108 13109 13110 13111 13112 13113 13114 13115 13116 13117 13118 13119 13120 13121 13122 13123 13124 13125 13126 13127 13128 13129 13130 13131 13132 13133 13134

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16 16 16 16 16 16 16 0 0 0

a planguide batch geometry or geography conversation priority tablegroup an assignment a cursor declaration replication filter variable assignment statistics file filegroup server write function database collation drop alter message type contract service queue table valued function event notification synonym lock thread communication buffer Common Language Runtime critical section partition scheme DETACH create route remote service binding Initiator Target host synchronization object generic waitable object application role schema user login certificate role find endpoint sql:variable sql:column XML namespace assembly fulltext catalog execute as symmetric key principal security descriptor hypothetical index nonclustered index credential transfer Cumulative wait time (ms) per second Waits started per second

13135 0 Waits in progress 13136 0 Average wait time (ms) 13137 0 Cumulative execution time (ms) per second 13138 0 Execs started per second 13139 0 Execs in progress 13140 0 Average execution time (ms) 13141 16 asymmetric key 13142 0 an INSERT SELECT statement 13143 16 partition function 13144 16 partition scheme 13145 16 encryption 13146 16 signature 13147 16 password 13148 16 rename 13149 16 end dialog 13150 16 END CONVERSATION WITH ERROR 13151 16 MOVE CONVERSATION 13152 16 receive sequenced message 13153 16 receive end conversation 13154 16 receive end conversation with error 13155 16 receive broker error 13156 16 receive message acknowledgement 13157 16 terminate conversation 13158 16 broker error 13159 16 countersignature 13160 16 BEGIN CONVERSATION TIMER 13161 16 fire conversation timer 13162 16 END CONVERSATION WITH CLEANUP 13163 16 BEGIN DIALOG CONVERSATION 13164 16 SEND 13165 16 conversation 13166 16 conversation group 13167 16 system 13168 16 Service Broker 13169 16 Database Mirroring 13170 0 table or indexed view 13171 16 conversation handle 13172 16 GET CONVERSATION GROUP 13173 16 master key 13174 16 another assembly with same SQL name is already present in the cu rrent database 13175 16 version, culture or public key mismatch 13176 0 component 13177 16 IL compilation 13178 16 Inproc data access 13179 16 DDL operations 13180 16 execution cache cleanup 13181 16 unspecified operation 13182 16 dialog 13183 10 The certificate's private key cannot be found 13184 10 The certificate's private key size is incompatible with the cryp to provider 13185 10 The certificate's public key size is incompatible with the crypt o provider 13186 10 The certificate's private key size is incompatible with the encr ypted key exchange key 13187 10 The certificate's public key size is incompatible with the secur ity header's signature 13188 10 The certificate's private key is password protected 13189 10 The key exchange key has an invalid size after being decrypted w

ith the certificate private key 13190 10 The database principal used to lookup the cert is invalid 13191 10 The database principal has no mapping to a server principal 13192 10 The certificate is disabled for BEGIN DIALOG 13193 16 encryption algorithm 13194 16 authentication protocol 13195 10 Certificate not found 13196 10 Certificate not yet valid 13197 10 Certificate expired 13198 10 Certificate is larger than maximum allowed size 13199 10 message timestamp 13202 10 TO BROKER INSTANCE 13203 10 TO SERVICE 13204 10 FROM BROKER INSTANCE 13205 10 FROM SERVICE 13206 10 SERVICE CONTRACT 13207 10 MESSAGE TYPE 13208 10 MESSAGE INTEGRITY CHECK 13209 10 KEY SALT 13210 10 SESSION KEY 13211 10 KEY EXCHANGE KEY 13212 10 SOURCE CERTIFICATE ISSUER NAME 13213 10 SOURCE CERTIFICATE SERIAL NUMBER 13214 10 DESTINATION CERTIFICATE ISSUER NAME 13215 10 DESTINATION CERTIFICATE SERIAL NUMBER 13216 10 SECURITY HEADER SIGNATURE 13217 10 MESSAGE BODY 13218 10 STATEMENT 13219 10 clustered index 13220 10 primary xml index 13221 10 manual failover 13222 10 automatic failover 13223 10 failover from partner 13224 10 role synchronization 13225 10 FORCE_SERVICE_ALLOW_DATA_LOSS 13226 10 add 13227 10 to 13228 10 from 13229 10 enable 13230 10 disable 13231 10 remap 13232 10 INSERT 13233 10 UPDATE 13234 10 DELETE 13235 10 WHEN MATCHED 13236 10 WHEN NOT MATCHED 13237 10 WHEN NOT MATCHED BY SOURCE 13238 10 TOP or OFFSET 13239 10 GROUP BY 13240 10 HAVING 13241 10 ORDER BY 13243 10 OUTPUT INTO 13244 10 SELECT 13245 10 WHERE 13246 10 unexpected 13247 10 The crypto API has detected bad data while trying to perform a d ecryption operation 13248 10 OUTPUT 13249 10 Temporary tables 13250 10 Labels

13251 13252 13254 13255 13256 13257 13258 13259 13260 13261 13262 13263 13264 13265 13266 13267 13268 13269 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13287 13288 13289 13290 13291 13292 13293 13294 13295 13296 13297 13298 13299 13301 13302 13303 13304 13373 13374 13375 13376 13377 13378 13379 13380

10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 16 16 16 16 16 16 16 16 16 16 10 10 10 10 10

availability group type table event target event action event session event package event object event predicate comparator event attribute or predicate source customizable attribute event predicate predicate source event attribute partitioned not partitioned resource pool workload group resource governor move UPDATETEXT WRITETEXT torn page (expected signature: 0x%08x; actual signature: 0x%08x) incorrect checksum (expected: 0x%08x; actual: 0x%08x) invalid protection option invalid encryption key unable to decrypt page decryption failure (expected: 0x%08x; actual: 0x%08x) unable to decrypt page due to missing DEK CREATION_DISPOSITION PROVIDER_KEY_NAME key source ENCRYPTION BY public key private key cryptographic provider cryptographic provider DLL path cryptographic provider friendly name version guid create credential for cryptographic provider key name key persistence cryptographic provider key thumbprint length cryptographic provider key blob length encryption algorithm tag name thumbprint IV(Initialization Vector) length bit length constraint database encryption key Anchor record Page dictionary Compression information structure Fulltext Query String Fulltext Query Language Fulltext Query Max Keys fulltext stoplist Success - Consult EKM Provider for details

13381 10 Failure - Consult EKM Provider for details 13382 10 Insufficient Buffer - Consult EKM Provider for details 13383 10 Not Supported - Consult EKM Provider for details 13384 10 Object Not Found - Consult EKM Provider for details 13385 10 Authentication Failure - Consult EKM Provider for details 13386 10 Invalid Argument - Consult EKM Provider for details 13387 10 Provider Error - No explanation is available, consult EKM Provid er for details 13388 10 Key Flags 13389 10 Key Name 13390 10 Key Type 13391 10 Location: 13392 10 Location relative to the specified target node: 13393 10 search property list 13394 10 MERGE 13395 10 PAD_INDEX 13396 10 FILLFACTOR 13397 10 SORT_IN_TEMPDB 13398 10 IGNORE_DUP_KEY 13399 10 STATISTICS_NORECOMPUTE 13400 10 Extended stored procedure API will be removed in a future versio n of SQL Server. Avoid using this feature in new development work, and plan to m odify applications that currently use it. 13402 10 The ability to INSERT NULL values into TIMESTAMP columns will be removed in a future version of SQL Server. Avoid using this feature in new deve lopment work, and plan to modify applications that currently use it. Use DEFAULT instead. 13403 10 The ability to use string literals as column aliases will be rem oved in a future version of SQL Server. Avoid using this feature in new developm ent work, and plan to modify applications that currently use it. Use AS clause i nstead. 13404 10 The ability to use '#' and '##' as the name of temporary tables and stored procedures will be removed in a future version of SQL Server. Avoid u sing this feature in new development work, and plan to modify applications that currently use it. 13405 10 The ability to use '@' and names that start with '@@' as Transac t-SQL identifiers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that curr ently use it. 13406 10 The ability to use the DEFAULT keyword as a default value will b e removed in a future version of SQL Server. Avoid using this feature in new dev elopment work, and plan to modify applications that currently use it. 13407 10 FASTFIRSTROW hint will be removed in the next version of SQL Ser ver. Avoid using this feature in new development work, and plan to modify applic ations that currently use it. Use OPTION (FAST n) instead. 13408 10 %ls will be removed in the next version of SQL Server. Avoid usi ng this feature in new development work, and plan to modify applications that cu rrently use it. 13409 10 Collation '%ls' will be removed in a future version of SQL Serve r. Avoid using this collation in new development work, and plan to modify applic ations that currently use it. 14002 16 Could not find the 'Sync' subsystem with the task ID %ld. 14003 16 You must supply a publication name. 14004 16 %s must be in the current database. 14005 16 Cannot drop the publication because at least one subscription ex ists for this publication. Drop all subscriptions to the publication before atte mpting to drop the publication. If the problem persists, replication metadata mi ght be incorrect; consult Books Online for troubleshooting information. 14006 16 Could not drop the publication. 14008 11 There are no publications.

14009 11 There are no articles for publication '%s'. 14010 16 The remote server '%s' is not defined as a subscription server. Ensure you specify the server name rather than a network alias. 14011 16 Unable to mark server '%s' as a non SQL Server subscriber. 14012 16 The @status parameter value must be either 'active' or 'inactive '. 14013 16 This database is not enabled for publication. 14014 16 The synchronization method (@sync_method) must be '[bcp] native' , '[bcp] character', 'concurrent', 'concurrent_c', 'database snapshot', or 'data base snapshot character'. 14015 16 The replication frequency (@repl_freq) must be either 'continuou s' or 'snapshot'. 14016 16 The publication '%s' already exists. 14017 16 Invalid @restricted parameter value. Valid options are 'true' or 'false'. 14018 16 Could not create the publication. 14019 16 The @operation parameter value must be either add, drop, or alte r. 14020 16 Could not obtain the column ID for the specified column. Schema replication failed. 14021 16 The column was not added correctly to the article. 14022 16 The @property parameter value must be either 'description', 'sy nc_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', 'dest_table', 'de st_object', 'creation_script', 'pre_creation_cmd', 'status', 'schema_option', or 'destination_owner'. 14023 16 The type must be '[indexed view ]logbased[ (manualview|manualfil ter|manualboth)]', '[serializable ]proc exec', or '(view|indexed view|proc|func |aggregate|synonym) schema only'. 14024 16 The value of property 'subscriber_provider' cannot be NULL. 14025 10 Article update successful. 14026 16 The value of property 'subscriber_type is not a supported hetero geneous subscriber type. The value must be 1 (ODBC subscriber), or 3 (OLEDB sub scriber). 14027 11 %s does not exist in the current database. 14028 16 Only user tables, materialized views, and stored procedures can be published as 'logbased' articles. 14029 16 The vertical partition switch must be either 'true' or 'false'. 14030 16 The article '%s' exists in publication '%s'. 14031 16 User tables and views are the only valid synchronization objects . 14032 16 The value of parameter %s cannot be 'all'. It is reserved by rep lication stored procedures. 14033 16 Could not change replication frequency because there are active subscriptions on the publication. 14034 16 The publication name (@publication) cannot be the keyword 'all'. 14035 16 The replication option '%s' of database '%s' has already been se t to true. 14036 16 Could not enable database for publishing. 14037 16 The replication option '%s' of database '%s' has been set to fal se. 14038 16 Could not disable database for publishing. 14039 16 Could not construct column clause for article view. Reduce the n umber of columns or create the view manually. 14040 16 The server '%s' is already a Subscriber. 14041 16 The '%s' property can only be changed if the publication is enab led for heterogeneous subscriptions. The publication is not enabled. 14042 16 Could not create Subscriber. 14043 16 The parameter %s passed to stored procedure %s cannot be NULL. 14044 16 Unable to clear subscriber status for the server. 14045 16 Unable to update subscriber_type in MSdistribution_agents table.

14046 16 Could not drop article. A subscription exists on it. 14047 16 Could not drop %s. 14048 16 The server '%s' is not a Subscriber. 14049 16 Stored procedures for replication are the only objects that can be used as a filter. 14050 11 No subscription is on this publication or article. 14051 16 The parameter value must be 'sync_type' or 'dest_db'. 14052 16 The @sync_type parameter value must be "automatic", "none", "rep lication support only", "initialize with backup", or "initialize from lsn". 14053 16 The subscription could not be updated at this time. 14054 10 The subscription was updated successfully. 14055 10 The subscription does not exist. 14056 16 The subscription could not be dropped at this time. 14057 16 The subscription could not be created. 14058 16 Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publicati on is allowed in each subscription database. Drop the subscription and add it ag ain if necessary. If the problem persists, replication metadata might be incorre ct; see Books Online for troubleshooting information. 14059 16 Materialized view articles cannot be created for publications wi th the properties allow_sync_tran, allow_queued_tran, or allow_dts. 14060 16 Subscriber parameters specifying provider properties must be NUL L for SQL Server subscribers. 14061 16 The @pre_creation_cmd parameter value must be 'none', 'drop', 'd elete', or 'truncate'. 14062 10 The Subscriber was dropped. 14063 11 The remote server does not exist or has not been designated as a valid Subscriber. 14065 16 The @status parameter value must be 'initiated', 'active', 'inac tive', or 'subscribed'. 14066 16 The previous status must be 'active', 'inactive', or 'subscribed '. 14067 16 The status value is the same as the previous status value. 14068 16 The subscription status of the object could not be changed. 14069 16 Could not update sysarticles. The subscription status could not be changed. 14070 16 Could not update the distribution database subscription table. T he subscription status could not be changed. 14071 16 Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor. 14074 16 The server '%s' is already listed as a Publisher. 14075 16 The Publisher could not be created at this time. 14076 16 Could not grant replication login permission to '%s'. 14077 10 The publication was updated successfully. 14078 16 The parameter must be 'description', 'taskid', 'sync_method', 's tatus', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_i nternet', 'allow_push', 'allow_pull', 'allow_anonymous', or 'retention'. 14080 16 The remote server "%s" does not exist, or has not been designate d as a valid Publisher, or you may not have permission to see available Publishe rs. 14085 16 The Subscriber information could not be obtained from the Distri butor. 14088 16 The table '%s' must have a primary key to be published using the transaction-based method. 14089 16 The clustered index on materialized view '%s' may not contain nu llable columns if it is to be published using the transaction-based method. 14090 16 Error evaluating article synchronization object after column dro p. The filter clause for article '%s' must not reference the dropped column. 14091 16 The @type parameter passed to sp_helpreplicationdb must be eithe

r 'pub' or 'sub'. 14092 16 Could not change article because there is an existing subscripti on to the article. 14093 16 Cannot grant or revoke access directly on publication '%s' becau se it uses the default publication access list. 14094 16 Could not subscribe to article '%s' because heterogeneous Subscr iber '%s' does not support the @pre_creation_cmd parameter value 'truncate'. 14095 16 The value for the @sync_method parameter is not valid. Could not subscribe to publication '%s' because non-SQL Server Subscriber '%s' only suppo rts values of 'character', 'bcp character', 'concurrent_c', and 'database snaps hot character' for the @sync_method parameter. 14096 16 The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is 'drop'. 14097 16 The 'status' value must be 'no column names', 'include column na mes', 'string literals', 'parameters', 'DTS horizontal partitions' or 'no DTS ho rizontal partitions'. 14098 16 Cannot drop Distribution Publisher '%s'. The remote Publisher is using '%s' as Distributor. Disable publishing at the Publisher before attemptin g to drop this relationship. 14099 16 The server '%s' is already defined as a Distributor. To reconfig ure the server as a Distributor, you must first uninstall the exisiting Distribu tor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard. 14100 16 Specify all articles when subscribing to a publication using con current snapshot processing. 14101 16 The publication '%s' already has a Snapshot Agent defined. 14102 16 Specify all articles when unsubscribing from a publication using concurrent snapshot processing. 14103 16 Invalid "%s" value. Valid values are "publisher", "subscriber", or "both". 14105 10 You have updated the distribution database property '%s' success fully. 14106 16 Distribution retention periods must be greater than or equal to 0. 14107 10 The @max_distretention value must be larger than the @min_distre tention value. 14108 10 Removed %ld history records from %s. 14109 10 The @security_mode parameter value must be 0 (SQL Server Authent ication) or 1 (Windows Authentication). 14110 16 For stored procedure articles, the @property parameter value mus t be 'description', 'dest_table', 'dest_object', 'creation_script', 'pre_creatio n_cmd', 'schema_option', or 'destination_owner'. 14111 16 The @pre_creation_cmd parameter value must be 'none' or 'drop'. 14112 16 This procedure can be executed only against table-based articles . 14113 16 Could not execute '%s'. Check '%s' in the install directory. 14114 16 The server '%s' is not configured as a Distributor. 14115 16 The property parameter value must be %s. 14117 16 '%s' is not configured as a distribution database. 14118 16 A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema only' article. 14119 16 Could not add the distribution database '%s'. This distribution database already exists. 14120 16 Could not drop the distribution database '%s'. This distributor database is associated with a Publisher. 14121 16 Could not drop the Distributor '%s'. This Distributor has associ ated distribution databases. 14122 16 The @article parameter value must be 'all' for immediate_sync pu blications. 14123 16 The subscription @sync_type parameter value 'manual' is no longe

r supported. 14124 16 A publication must have at least one article before a subscripti on to it can be created. 14126 16 You do not have the required permissions to complete the operati on. 14128 16 Invalid @subscription_type parameter value. Valid options are 'p ush' or 'pull'. 14129 16 The @status parameter value must be NULL for 'automatic' sync_ty pe when you add subscriptions to an immediate_sync publication. 14135 16 There is no subscription on Publisher '%s', publisher database ' %s', publication '%s'. 14136 16 The keyword 'all' is reserved by replication stored procedures. 14137 16 The @value parameter value must be either 'true' or 'false'. 14138 16 Invalid option name '%s'. 14139 16 The replication system table '%s' already exists. 14143 16 Cannot drop Distributor Publisher '%s'. There are Subscribers as sociated with it in the distribution database '%s'. 14144 16 Cannot drop Subscriber '%s'. There are subscriptions for it in t he publication database '%s'. 14146 16 The article parameter '@schema_option' cannot be NULL. 14147 16 Restricted publications are no longer supported. 14148 16 Invalid '%s' value. Valid values are 'true' or 'false'. 14149 10 Removed %ld replication history records in %s seconds (%ld row/s ecs). 14150 10 Replication-%s: agent %s succeeded. %s 14151 18 Replication-%s: agent %s failed. %s 14152 10 Replication-%s: agent %s scheduled for retry. %s 14153 10 Replication-%s: agent %s warning. %s 14154 16 The Distributor parameter must be '@heartbeat_interval'. 14155 16 Invalid article ID specified for procedure script generation. 14156 16 The custom stored procedure calling the format for the %s comman d specified in the article definition does not match the %s format. 14157 10 The subscription created by Subscriber '%s' to publication '%s' has expired and has been dropped. 14158 10 Replication-%s: agent %s: %s. 14159 16 Could not change property '%s' for article '%s' because there is an existing subscription to the article. 14160 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and change the expiration threshold value if necessary. 14161 10 The threshold [%s:%s] for the publication [%s] has been set. Mak e sure that the logreader and distribution agents are running and can match the latency requirement. 14162 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary. 14163 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary. 14164 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary. 14165 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary. 14166 10 Disable publishing ignored error msg %d, severity %d, state %d: %s. 14167 10 Subscription expiration 14168 10 Transactional replication latency 14169 10 Long merge over dialup connection

14170 10 Long merge over LAN connection 14171 10 Slow merge over LAN connection 14172 10 Slow merge over dialup connection 14196 10 The agent has never been run. 14197 10 Value of %s parameter should be in the set %s 14198 10 The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct. 14199 10 The specified job '%s' is not created for maintenance plans. Ver ify that the job has at least one step calling xp_sqlmaint. 14200 16 The specified '%s' is invalid. 14201 10 0 (all steps) .. 14202 10 before or after @active_start_time 14203 10 sp_helplogins [excluding Windows NT groups] 14204 10 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions) 14205 10 (unknown) 14206 10 0..n seconds 14207 10 -1 [no maximum], 0..n 14208 10 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend] 14209 10 0..127 [1 = Sunday .. 64 = Saturday] 14210 10 notification 14211 10 server 14212 10 (all jobs) 14213 10 Core Job Details: 14214 10 Job Steps: 14215 10 Job Schedules: 14216 10 Job Target Servers: 14217 10 SQL Server Warning: '%s' has performed a forced defection of TSX server '%s'. Run sp_delete_targetserver at the MSX in order to complete the def ection. 14218 10 hour 14219 10 minute 14220 10 second 14221 16 This job has one or more notifications to operators other than ' %s'. The job cannot be targeted at remote servers as currently defined. 14222 16 Cannot rename the '%s' operator. 14223 16 Cannot modify or delete operator '%s' while this server is a %s. 14224 10 Warning: The server name given is not the current MSX server ('% s'). 14225 16 Warning: Could not determine local machine name. This prevents M SX operations from being posted. 14226 10 %ld history entries purged. 14227 10 Server defected from MSX '%s'. %ld job(s) deleted. 14228 10 Server MSX enlistment changed from '%s' to '%s'. 14229 10 Server enlisted into MSX '%s'. 14230 10 SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted. 14231 10 SP_POST_MSX_OPERATION Warning: The specified %s ('%s') is not in volved in a multiserver job. 14232 16 Specify either a job_name, job_id, or an originating_server. 14233 16 Specify a valid job_id (or 0x00 for all jobs). 14234 16 The specified '%s' is invalid (valid values are returned by %s). 14235 16 The specified '%s' is invalid (valid values are greater than 0 b ut excluding %ld). 14236 10 Warning: Non-existent step referenced by %s. 14237 16 When an action of 'REASSIGN' is specified, the New Login paramet er must also be supplied. 14238 10 %ld jobs deleted. 14239 10 %ld jobs reassigned to %s. 14240 10 Job applied to %ld new servers. 14241 10 Job removed from %ld servers.

14242 16 Only a system administrator can reassign ownership of a job. 14243 10 Job '%s' started successfully. 14245 16 Specify either the @name, @id, or @loginname of the task(s) to b e deleted. 14250 16 The specified %s is too long. It must contain no more than %ld c haracters. 14251 16 Cannot specify '%s' as the operator to be notified. 14252 16 Cannot perform this action on a job you do not own. 14253 10 %ld (of %ld) job(s) stopped successfully. 14254 10 Job '%s' stopped successfully. 14255 16 The owner ('%s') of this job is either an invalid login, or is n ot a valid user of database '%s'. 14256 16 Cannot start the job "%s" (ID %s) because it does not have any j ob server or servers defined. Associate the job with a job server by calling sp_ add_jobserver. 14257 16 Cannot stop the job "%s" (ID %s) because it does not have any jo b server or servers defined. Associate the job with a job server by calling sp_a dd_jobserver. 14258 16 Cannot perform this operation while SQLServerAgent is starting. Try again later. 14260 16 You do not have sufficient permission to run this command. Conta ct your system administrator. 14261 16 The specified %s ('%s') already exists. 14262 16 The specified %s ('%s') does not exist. 14263 16 Target server '%s' is already a member of group '%s'. 14264 16 Target server '%s' is not a member of group '%s'. 14265 24 The MSSQLServer service terminated unexpectedly. Check the SQL S erver error log and Windows System and Application event logs for possible cause s. 14266 16 The specified '%s' is invalid (valid values are: %s). 14267 16 Cannot add a job to the '%s' job category. 14268 16 There are no jobs at this server that originated from server '%s '. 14269 16 Job '%s' is already targeted at server '%s'. 14270 16 Job '%s' is not currently targeted at server '%s'. 14271 16 A target server cannot be named '%s'. 14272 16 Object-type and object-name must be supplied as a pair. 14273 16 You must provide either @job_id or @job_name (and, optionally, @ schedule_name), or @schedule_id. 14274 16 Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. 14275 16 The originating server must be either local server or MSX server . 14276 16 '%s' is a permanent %s category and cannot be deleted. 14277 16 The command script does not destroy all the objects that it crea tes. Revise the command script. 14278 16 The schedule for this job is invalid (reason: %s). 14279 16 Supply either @job_name, @job_id or @originating_server. 14280 16 Supply either a job name (and job aspect), or one or more job fi lter parameters. 14281 10 Warning: The @new_owner_login_name parameter is not necessary wh en specifying a 'DELETE' action. 14282 16 Supply either a date (created or last modified) and a data compa rator, or no date parameters at all. 14283 16 Supply @target_server_groups or @target_servers, or both. 14284 16 Cannot specify a job ID for a new job. An ID will be assigned by the procedure. 14285 16 Cannot add a local job to a multiserver job category. 14286 16 Cannot add a multiserver job to a local job category. 14287 16 The '%s' supplied has an invalid %s.

14288 16 %s cannot be before %s. 14289 16 %s cannot contain '%s' characters. 14290 16 This job is currently targeted at the local server so cannot als o be targeted at a remote server. 14291 16 This job is currently targeted at a remote server so cannot also be targeted at the local server. 14292 16 There are two or more tasks named '%s'. Specify %s instead of %s to uniquely identify the task. 14293 16 There are two or more jobs named '%s'. Specify %s instead of %s to uniquely identify the job. 14294 16 Supply either %s or %s to identify the job. 14295 16 Frequency Type 0x2 (OnDemand) is no longer supported. 14296 16 This server is already enlisted into MSX '%s'. 14297 16 Cannot enlist into the local machine. 14298 16 This server is not currently enlisted into an MSX. 14299 16 Server '%s' is an MSX. Cannot enlist one MSX into another MSX. 14301 16 Logins other than the current user can only be seen by members o f the sysadmin role. 14305 16 Column '%.*ls' does not exist in table '%.*ls'. 14306 16 The target server (TSX) version is not compatible with the maste r server (MSX) version (%ld.%ld.%ld). 14307 16 Access to Integration Services package '%s' is denied. 14350 16 Cannot initialize COM library because CoInitialize failed. 14351 16 Cannot complete this operation because an unexpected error occur red. 14353 16 Cannot determine the service account for this SQL Server instanc e. 14357 16 Cannot list '%s' in Active Directory because the name is too lon g. Active Directory common names cannot exceed 64 characters. 14360 16 %s is already configured as TSX machine 14362 16 The MSX server must be running the Standard or Enterprise editio n of SQL Server 14363 16 The MSX server is not prepared for enlistments [there must be an operator named 'MSXOperator' defined at the MSX] 14364 16 The TSX server is not currently enlisted 14365 16 Specify a valid schedule_uid. 14366 16 Only members of sysadmin role can modify the owner of a schedule . 14367 16 One or more schedules were not deleted because they are being us ed by at least one other job. Use "sp_detach_schedule" to remove schedules from a job. 14368 16 Schedule "%s" was not deleted because it is being used by at lea st one other job. Use "sp_detach_schedule" to remove schedules from a job. 14369 16 The schedule ID "%s" is used by more than one job. Specify the j ob_id. 14370 16 The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX). 14371 16 There are two or more schedules named "%s". Specify %s instead o f %s to uniquely identify the schedule. 14372 16 The schedule was not deleted because it is being used by one or more jobs. 14373 16 Supply either %s or %s to identify the schedule. 14374 16 The specified schedule name "%s" is not associated with the job "%s". 14375 16 More than one schedule named "%s" is attached to job "%s". Use " sp_update_schedule" to update schedules. 14376 16 More than one schedule named "%s" is attached to job "%s". Use " sp_detach_schedule" to remove schedules from a job. 14377 16 The schedule was not attached to the specified job. The caller m ust own the job or the operation must be performed by a sysadmin.

14378 16 @sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility 14379 16 Table '%s' foreign key 'originating_server_id' does not have a m atching value in the referenced view 'dbo.sysoriginatingservers_view'. 14380 16 Field 'originating_server_id' in table sysoriginatingservers is being referenced by either sysjobs or sysschedules. 14390 16 Only members of role sysadmin can specify the %s parameter. 14391 16 Only owner of a job or members of sysadmin role can detach a sch edule. 14392 16 Only owner of a job or members of role sysadmin or SQLAgentOpera torRole can purge history of the job. 14393 16 Only owner of a job or members of role sysadmin or SQLAgentOpera torRole can start and stop the job. 14394 16 Only owner of a job schedule or members of sysadmin role can mod ify or delete the job schedule. 14395 16 '%s' is a member of sysadmin server role and cannot be granted t o or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy. 14396 16 Only members of sysadmin server role can modify multi-server job s 14397 16 Only members of sysadmin server role can start/stop multi-server jobs 14398 16 Only members of sysadmin server role can create multi-server job s 14399 16 Current proxy_id %d and new proxy_id %d cannot be the same. 14400 16 Proxy %d does not have access to subsystem %d. Please use sp_gra nt_proxy_to_subsystem to grant permissions to this proxy. 14410 16 You must supply either a plan_name or a plan_id. 14411 16 Cannot delete this plan. The plan contains enlisted databases. 14412 16 The destination database is already part of a log shipping plan. 14413 16 This database is already log shipping. 14414 16 A log shipping monitor is already defined. 14415 16 The user name cannot be null when using SQL Server authenticatio n. 14416 16 This stored procedure must be run in msdb. 14417 16 Cannot delete the monitor server while databases are participati ng in log shipping. 14418 16 The specified @backup_file_name was not created from database '% s'. 14419 16 The specified @backup_file_name is not a database backup. 14420 16 The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check ag ent log and logshipping monitor information. 14421 16 The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Resto red latency is %d minutes. Check agent log and logshipping monitor information. 14422 16 Supply either @plan_id or @plan_name. 14423 16 Other databases are enlisted on this plan and must be removed be fore the plan can be deleted. 14424 16 The database '%s' is already involved in log shipping. 14425 16 The database '%s' does not seem to be involved in log shipping. 14426 16 A log shipping monitor is already defined. Call sp_define_log_sh ipping_monitor with @delete_existing = 1. 14427 16 A user name is necessary for SQL Server security. 14428 16 Could not remove the monitor as there are still databases involv ed in log shipping. 14429 16 There are still secondary servers attached to this primary. 14430 16 Destination path %s is not valid. Unable to list directory conte nts. Specify a valid destination path. 14440 16 Could not set single user mode.

14441 16 Role change succeeded. 14442 16 Role change failed. 14450 16 The specified @backup_file_name was not taken from database '%s' . 14451 16 The specified @backup_file_name is not a database backup. 14500 16 Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query. 14501 16 An alert ('%s') has already been defined on this condition. 14502 16 The @target_name parameter must be supplied when specifying an @ enum_type of 'TARGET'. 14503 16 The @target_name parameter should not be supplied when specifyin g an @enum_type of 'ALL' or 'ACTUAL'. 14504 16 '%s' is the fail-safe operator. You must make another operator t he fail-safe operator before '%s' can be dropped. 14505 16 Specify a null %s when supplying a performance condition. 14506 16 Cannot set alerts on message ID %ld. 14507 16 A performance condition must be formatted as: 'object_name|count er_name|instance_name|comparator(> or < or =)|numeric value'. 14508 16 Specify both @wmi_namespace and @wmi_query. 14509 16 Specify a valid %s when supplying a @wmi_namespace. 14510 16 Specify a null %s when supplying a @wmi_namespace. 14511 16 The @wmi_query could not be executed in the @wmi_namespace provi ded. Verify that an event class selected in the query exists in the namespace an d that the query has the correct syntax. 14512 16 Specify a valid %s when supplying a @wmi_query. 14513 10 Analysis query subsystem 14514 10 Analysis command subsystem 14515 16 Only a member of the sysadmin server role can add a job for a di fferent owner with @owner_login_name. 14516 16 Proxy (%d) is not allowed for subsystem "%s" and user "%s". Gran t permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy. 14517 16 A proxy account is not allowed for a Transact-SQL subsystem. 14518 16 Cannot delete proxy (%d). It is used by at least one jobstep. Ch ange this proxy for all jobsteps by calling sp_reassign_proxy. 14519 16 Only one of @login_name, @fixed_server_role, or @msdb_role shoul d be specified. 14520 16 "%s" is not a valid SQL Server standard login, Windows NT user, Windows NT group, or msdb database role. 14521 16 "%s" is not a valid SQL Server fixed server role, Windows NT use r, or Windows NT group. 14522 16 '"%s" is not a valid role of an msdb database, Windows NT user, or Windows NT group. 14523 16 "%s" has not been granted permission to use proxy "%s". 14524 16 Supply either %s or %s. 14525 16 Only members of sysadmin role are allowed to update or delete jo bs owned by a different login. 14526 16 The specified category "%s" does not exist for category class "% s". 14527 16 Job "%s" cannot be used by an alert. It should first be associat ed with a server by calling sp_add_jobserver. 14528 16 Job "%s" has no steps defined. 14529 16 Proxy "%s" is not a valid Windows user. 14530 16 The Transact-SQL subsystem cannot be executed under the context of a proxy account. 14531 16 Permission to access proxy already granted. Verify current permi ssions assignments. 14532 16 Supply both %s and %s, or none of them. 14533 16 Use either a proxy or user_domain, user_name, or user_password p arameter. 14534 16 All user_domain, user_name, and user_password parameters should

be defined. 14535 16 The user_domain, user_name, and user_password parameters can be specified only for replication subsystems. 14536 16 Only members of the sysadmin role can specify a "%s" parameter. 14537 16 Execution in the context of disabled proxy (proxy_id = %d) is no t allowed. Contact your system administrator. 14538 10 SSIS package execution subsystem 14539 16 Only a Standard or Enterprise edition of SQL Server can be enlis ted into an MSX. 14540 16 Only a SQL Server running on Microsoft Windows NT can be enliste d into an MSX. 14541 16 The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX. 14542 16 It is invalid for any TSQL step of a multiserver job to have a n on-null %s value. 14543 16 Login '%s' owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role. 14544 16 This job is owned by '%s'. Only a job owned by a member of the % s role can be a multiserver job. 14545 16 The %s parameter is not valid for a job step of type '%s'. 14546 16 The %s parameter is not supported on Windows 95/98 platforms. 14547 10 Warning: This change will not be downloaded by the target server (s) until an %s for the job is posted using %s. 14548 10 Target server '%s' does not have any jobs assigned to it. 14549 10 (Description not requested.) 14550 10 Command-Line Subsystem 14551 10 Replication Snapshot Subsystem 14552 10 Replication Transaction-Log Reader Subsystem 14553 10 Replication Distribution Subsystem 14554 10 Replication Merge Subsystem 14555 10 Active Scripting Subsystem 14556 10 Transact-SQL Subsystem 14557 10 [Internal] 14558 10 (encrypted command) 14559 10 (append output file) 14560 10 (include results in history) 14561 10 (normal) 14562 10 (quit with success) 14563 10 (quit with failure) 14564 10 (goto next step) 14565 10 (goto step) 14566 10 (idle) 14567 10 (below normal) 14568 10 (above normal) 14569 10 (time critical) 14570 10 (Job outcome) 14571 10 No description available. 14572 10 @freq_interval must be at least 1 for a daily job. 14573 10 @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job. 14574 10 @freq_interval must be between 1 and 31 for a monthly job. 14575 10 @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10). 14576 10 @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Satur day, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job. 14577 10 @freq_recurrence_factor must be at least 1. 14578 10 Starts whenever the CPU usage has remained below %ld percent for %ld seconds. 14579 10 Automatically starts when SQLServerAgent starts. 14580 10 job

14581 10 Replication Transaction Queue Reader Subsystem 14582 16 Only a sysadmin can specify '@output_file_name' parameter for a jobstep. 14583 16 Only a sysadmin can specify '@database_user_name' parameter. 14585 16 Only the owner of DTS Package '%s' or a member of the sysadmin r ole may reassign its ownership. 14586 16 Only the owner of DTS Package '%s' or a member of the sysadmin r ole may create new versions of it. 14587 16 Only the owner of DTS Package '%s' or a member of the sysadmin r ole may drop it or any of its versions. 14588 10 ID.VersionID = 14589 10 [not specified] 14590 16 DTS Package '%s' already exists with a different ID in this cate gory. 14591 16 SSIS folder '%s' already exists in the specified parent folder. 14592 16 DTS Category '%s' was found in multiple parent categories. You m ust uniquely specify the category to be dropped. 14593 16 SSIS folder '%s' contains packages and/or other folders. You mus t drop these first. 14594 10 DTS Package 14595 16 DTS Package '%s' exists in different categories. You must unique ly specify the package. 14596 16 DTS Package '%s' exists in another category. 14597 16 DTS Package ID '%s' already exists with a different name. 14598 16 Cannot drop the Local, Repository, or LocalDefault DTS categorie s. 14599 10 Name 14600 16 Proxy "%s" has not been granted permission to use subsystem "%s" . 14601 16 Operator "%s" is not enabled and therefore cannot receive notifi cations. 14602 16 Operator "%s" does not have an e-mail address specified. 14603 16 Database Mail is not properly configured. 14604 16 Both %s parameters (id and name) cannot be NULL 14605 16 Both %s parameters (id and name) do not point to the same object 14606 16 %s id is not valid 14607 16 %s name is not valid 14608 16 Either %s or %s parameter needs to be supplied 14609 16 Mail database to user database association does not exist and th erefore cannot be updated 14610 16 Either @profile_name or @description parameter needs to be speci fied for update 14611 16 Account sequence number must be supplied for update 14612 16 Each principal should have at least one default profile 14613 16 The specified '%s' cannot use commas (,) to separate addresses: '%s'. To continue, use semicolons (;) to separate addresses. 14614 16 %s is not a valid mailserver_type 14615 16 The @username parameter needs to be supplied if the @password is supplied. 14616 16 Unable to retrieve the newly created credential [%s] from the cr edential store. 14617 16 Mail host database specified is invalid 14618 16 Parameter '%s' must be specified. This parameter cannot be NULL. 14619 16 Received an error on the Service Broker conversation with Databa se Mail. Database Mail may not be available, or may have encountered an error. C heck the Database Mail error log for information. 14620 16 The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have en countered an error. Check the Database Mail error log for more information. 14621 16 Parameter @attachmentencoding does not support the value "%s". T

he attachment encoding must be "MIME". 14622 16 Parameter @importance does not support the value "%s". Mail impo rtance must be one of LOW, NORMAL, or HIGH. 14623 16 Parameter @sensitivity does not support the value "%s". Mail sen sitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL. 14624 16 At least one of the following parameters must be specified. "%s" . 14625 16 Parameter @attach_query_result_as_file cannot be 1 (true) when n o value is specified for parameter @query. A query must be specified to attach t he results of the query. 14626 16 Parameter @mailformat does not support the value "%s". The mail format must be TEXT or HTML. 14627 16 Received error %d while sending a message as part of the %s oper ation. Database Mail may not be available, or may have encountered an error. Che ck the Database Mail error log for more information. 14628 16 The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon ";". 14629 16 There is no configuration parameter named "%s", or the value pro vided is not of the correct data type. 14630 16 Database Mail is not permitted to send files with the file exten sion %s. 14631 16 The current user ('%s') either does not have permission to acces s the database specified in the parameter @execute_query_database or cannot impe rsonate the user specified in the parameter @execute_query_as. Only members of t he sysadmin fixed server role and members of the db_owner fixed database role ca n impersonate another user. 14632 16 The user name %s specified in @execute_query_as is invalid. Ther e is no user by that name. 14633 16 The database name "%s" specified in @execute_query_database is i nvalid. There is no database by that name. 14634 10 Warning: %s' 14635 10 Mail (Id: %d) queued. 14636 16 No global profile is configured. Specify a profile name in the @ profile_name parameter. 14637 10 Activation failure. 14638 10 Activation successful. 14639 10 The mail queue was started by login "%s". 14640 10 The mail queue stopped by login "%s". 14641 16 Mail not queued. Database Mail is stopped. Use sysmail_start_sp to start Database Mail. 14642 10 Default attachment encoding 14643 10 Default dialog lifetime 14644 10 Default maximum file size 14645 10 Extensions not allowed in outgoing mails 14646 10 Number of retry attempts for a mail server 14647 10 Delay between each retry attempt to mail server 14648 10 Minimum process lifetime in seconds 14649 16 Unable to test profile. Database Mail is stopped. Use sysmail_st art_sp to start Database Mail. 14650 16 Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery. 14651 16 Unable to test profile. Service Broker message delivery is not e nabled in this database. Use the ALTER DATABASE statement to enable Service Brok er message delivery. 14652 16 Invalid message received on the ExternalMailQueue. conversation_ handle: %s. message_type_name: %s. message body: %s. 14653 16 Invalid %s value received on the ExternalMailQueue. conversation _handle: %s. message_type_name: %s. message body: %s. 14654 10 Unexpected message received on the ExternalMailQueue. conversati on_handle: %s. message_type_name: %s. message body: %s.

14655 16 Invalid XML message format received on the ExternalMailQueue. co nversation_handle: %s. message_type_name: %s. message body: %s. 14657 16 Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded. 14658 16 Failed to retrieve SQLPath for syssubsystems population. 14659 16 Failed to retrieve VerSpecificRootDir for syssubsystems populati on. 14660 16 Database Compatibility Level is too low. Compatibility Level mus t be Version80 or higher. 14661 16 Query execution failed: %s 14662 10 mailitem_id on conversation %s was not found in the sysmail_send _retries table. This mail item will not be sent. 14663 10 Mail Id %d has exceeded the retry count. This mail item will not be sent. 14664 16 Database Mail logging level: normal - 1, extended - 2 (default), verbose - 3 14665 10 Mail items deletion is initiated by user "%s". %d items deleted. 14666 16 User name cannot be supplied when using default credentials 14667 16 Mail Id %d has been deleted from sysmail_mailitems table. This m ail will not be sent. 14668 16 Deleting profile %s failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of t he profile. 14670 16 Cannot delete the active collection set '%s'. Stop the collectio n set and then try to delete it again. 14671 16 Cannot update the name or the parameters of the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to update the collection item again. 14672 16 Cannot delete the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to delete the collection item aga in. 14673 16 Cannot delete the collector type '%s'. Delete all collection ite ms associated with this collector type and then try to delete it again. 14674 16 Cannot upload data for the inactive collection set '%s'. Start t he collection set and then try to upload the data again. 14675 16 Cannot update the name, target, proxy_id, logging_level, or coll ection_mode, or add collection item to the active collection set '%s'. Stop the collection set and then try to update it again. 14676 16 The user does not have permission to change '%s'. The user must be a member of data collector role '%s'. 14677 16 The user does not have permission to perform this operation. The user must be a member of data collector role '%s'. 14678 16 SQL Server Trace with id %d has been stopped and closed by exter nal user. SQL Server Trace collector will attempt to re-create the trace. 14679 16 The specified %s (%s) is not valid in this data warehouse. 14680 16 Management Data Warehouse database can only be installed on an i nstance of SQL Server 2008 or higher. 14681 16 Cannot perform this procedure when the collector is disabled. En able the collector and then try again. 14682 16 The state of the collection set has changed, but it will not sta rt or stop until the collector is enabled. 14683 16 A collection set in cached mode requires a schedule. 14684 16 Caught error#: %d, Level: %d, State: %d, in Procedure: %s, Line: %d, with Message: %s 14685 16 Collection set: '%s' does not contain any collection items, so s tarting the collection set will have no effect. 14686 16 The MDWInstance and MDWDatabase parameters of the configuration store cannot be null. 14687 16 Invalid value (%d) of the @cache_window parameter. Allowable val ues are: -1 (cache all upload data from previous upload failures), 0 (cache no u

pload data), N (cache data from N previous upload failures, where N >= 1) 14688 16 A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent. 14689 16 A collection set cannot start if the management data warehouse i s not configured. Run the instmdw.sql script to create and configure the managem ent data warehouse. 14690 16 Cannot perform this procedure when the collector is enabled. Dis able the collector and then try again. 14691 16 The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. 14692 16 Insufficient priveleges to start collection set: '%s'. Only a me mber of the 'sysadmin' fixed server role can start a collection set without a SQ L Server Agent proxy. Attach a SQL Server Agent proxy to the collection set befo re retrying. 14693 16 A collection set cannot start without a schedule. Specify a sche dule for the collection set. 14694 16 Cannot upload data on-demand for the collection set '%s' in noncached mode. 14695 16 Cannot collect data on-demand for the collection set '%s' in cac hed mode. 14696 16 Cannot update or delete a system collection set, or add new col lection items to it. 14697 16 Unable to convert showplan to XML. Error #%d on Line %d: %s 14698 10 PowerShell Subsystem 14699 16 Data Collector cannot be enabled when SQL Server Agent is stoppe d. Start SQL Server Agent. 14700 10 Collects data about the disk and log usage for all databases. 14701 10 Disk Usage 14702 10 Disk Usage - Data Files 14703 10 Disk Usage - Log Files 14704 10 Collects top-level performance indicators for the computer and t he Database Engine. Enables analysis of resource use, resource bottlenecks, and Database Engine activity. 14705 10 Server Activity 14706 10 Server Activity - DMV Snapshots 14707 10 Server Activity - Performance Counters 14708 10 Collects query statistics, T-SQL text, and query plans of most o f the statements that affect performance. Enables analysis of poor performing qu eries in relation to overall SQL Server Database Engine activity. 14709 10 Query Statistics 14710 10 Query Statistics - Query Activity 14711 10 Changes to SQL dumper configuration will take effect when the co llection set is restarted. To perform an immediate dump, use the dtutil /dump op tion. 14712 16 Only dbo or members of dc_admin can install or upgrade instmdw.s ql. Contact an administrator with sufficient permissions to perform this operati on. 14713 21 A management data warehouse cannot be installed to SQL Server Ex press Edition. 14714 16 Attempting to upgrade a Management Data Warehouse of newer versi on '%s' with an older version '%s'. Upgrade aborted. 14715 10 Collects data about instances of SQL Server that are managed in the SQL Server Utility. 14716 10 Utility Information 14718 10 Utility Information - Managed Instance 14719 16 "%s" has not been granted permission to use proxy. 14720 16 The operation failed because credential '%s' identity is not a v alid Windows account 15001 16 Object '%ls' does not exist or is not a valid object for this op eration.

15002 16 The procedure '%s' cannot be executed within a transaction. 15003 16 Only members of the %s role can execute this stored procedure. 15004 16 Name cannot be NULL. 15005 10 Statistics for all tables have been updated. 15006 16 '%s' is not a valid name because it contains invalid characters. 15007 16 '%s' is not a valid login or you do not have permission. 15008 16 User '%s' does not exist in the current database. 15009 16 The object '%s' does not exist in database '%s' or is invalid fo r this operation. 15010 16 The database '%s' does not exist. Supply a valid database name. To see available databases, use sys.databases. 15011 16 Database option '%s' does not exist. Specify a valid database op tion. 15012 16 The device '%s' does not exist. Use sys.backup_devices to show a vailable devices. 15013 10 Table '%s': No columns without statistics found. 15014 16 The role '%s' does not exist in the current database. 15015 16 The server '%s' does not exist. Use sp_helpserver to show availa ble servers. 15016 16 The default '%s' does not exist. 15017 16 The rule '%s' does not exist. 15018 10 Table '%s': Creating statistics for the following columns: 15019 16 The extended stored procedure '%s' does not exist. 15020 10 Statistics have been created for the %d listed columns of the ab ove tables. 15021 16 Invalid value given for parameter %s. Specify a valid parameter value. 15022 16 The specified user name is already aliased. 15023 16 User, group, or role '%s' already exists in the current database . 15025 16 The server principal '%s' already exists. 15026 16 Logical device '%s' already exists. 15028 16 The server '%s' already exists. 15032 16 The database '%s' already exists. Specify a unique database name . 15033 16 '%s' is not a valid official language name. 15034 16 The application role password must not be NULL. 15036 16 The data type '%s' does not exist or you do not have permission. 15040 16 User-defined error messages must have an ID greater than 50000. 15041 16 User-defined error messages must have a severity level between 1 and 25. 15042 10 The @with_log parameter is ignored for messages that are not us_ english version. 15043 16 You must specify 'REPLACE' to overwrite an existing message. 15044 16 The type "%s" is an unknown backup device type. Use the type "di sk" or "tape". 15045 16 The logical name cannot be NULL. 15046 16 The physical name cannot be NULL. 15048 10 Valid values of the database compatibility level are %d, %d, or %d. 15049 11 Cannot unbind from '%s'. Use ALTER TABLE DROP CONSTRAINT. 15050 11 Cannot bind default '%s'. The default must be created using the CREATE DEFAULT statement. 15051 11 Cannot rename the table because it is published for replication. 15053 16 Objects exist which are not owned by the database owner. 15054 10 The current compatibility level is %d. 15056 10 The suspect flag on the database "%s" is already reset. 15057 16 List of %s name contains spaces, which are not allowed. 15058 16 List of %s has too few names. 15059 16 List of %s has too many names.

15060 16 List of %s names contains name(s) which have '%s' non-alphabetic characters. 15061 16 The add device request was denied. A physical device named "%s" already exists. Only one backup device may refer to any physical device name. 15062 16 The guest user cannot be mapped to a login name. 15063 16 The login already has an account under a different user name. 15065 16 All user IDs have been assigned. 15066 16 A default-name mapping of a remote login from remote server '%s' already exists. 15068 16 A remote user '%s' already exists for remote server '%s'. 15069 16 One or more users are using the database. The requested operatio n cannot be completed. 15070 10 Object '%s' was successfully marked for recompilation. 15071 16 Usage: sp_addmessage <msgnum>,<severity>,<msgtext> [,<language> [,FALSE | TRUE [,REPLACE]]] 15072 16 Usage: sp_addremotelogin remoteserver [,loginname [,remotename]] 15074 10 Warning: You must recover this database prior to access. 15076 16 Default, table, and user data types must be in the current datab ase. 15077 16 Rule, table, and user data type must be in the current database. 15078 16 The table or view must be in the current database. 15079 10 Queries processed: %d. 15080 16 Cannot use parameter %s for a Windows login. 15081 16 Membership of the public role cannot be changed. 15083 16 Physical data type '%s' does not accept a collation 15084 16 The column or user data type must be in the current database. 15085 16 Usage: sp_addtype name, 'data type' [,'NULL' | 'NOT NULL'] 15096 16 Could not find object '%ls' or you do not have required permissi on or the object is not valid for adding extended property. 15097 16 The size associated with an extended property cannot be more tha n 7,500 bytes. 15098 16 The name change cannot be performed because the SID of the new n ame does not match the old SID of the principal. 15099 16 The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is O FF. 15100 16 Usage: sp_bindefault defaultname, objectname [, 'futureonly'] 15101 16 Cannot bind a default to a computed column, a sparse column, or to a column of the following data types: timestamp, varchar(max), nvarchar(max), varbinary(max), xml, or CLR type. 15102 16 Cannot bind a default to an identity column. 15103 16 Cannot bind a default to a column created with or altered to hav e a default value. 15104 16 You do not own a table named '%s' that has a column named '%s'. 15106 16 Usage: sp_bindrule rulename, objectname [, 'futureonly'] 15107 16 Cannot bind a rule to a computed column, a sparse column, or to a column of the following data types: text, ntext, image, timestamp, varchar(max ), nvarchar(max), varbinary(max), xml, or user-defined data type. 15108 16 sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. Use CREATE TYPE for th is purpose. 15109 16 Cannot change the owner of the master, model, tempdb or distribu tion database. 15110 16 The proposed new database owner is already a user or aliased in the database. 15112 11 The third parameter for table option 'text in row' is invalid. I t should be 'on', 'off', '0', '1' or a number from 24 through 7000. 15113 16 Too many failed login attempts. This account has been temporaril y locked as a precaution against password guessing. A system administrator can u nlock this login with the UNLOCK clause of ALTER LOGIN. 15114 16 Password validation failed. The password for the user is too rec

ent to change. 15115 16 Password validation failed. The password cannot be used at this time. 15116 16 Password validation failed. The password does not meet Windows p olicy requirements because it is too short. 15117 16 Password validation failed. The password does not meet Windows p olicy requirements because it is too long. 15118 16 Password validation failed. The password does not meet Windows p olicy requirements because it is not complex enough. 15119 16 Password validation failed. The password does not meet the requi rements of the password filter DLL. 15120 16 An unexpected error occurred during password validation. 15121 16 An error occurred during the execution of %ls. A call to '%ls' f ailed with error code: '%d'. 15122 16 The CHECK_EXPIRATION option cannot be used when CHECK_POLICY is OFF. 15123 16 The configuration option '%s' does not exist, or it may be an ad vanced option. 15124 16 The configuration option '%s' is not unique. 15125 16 Trigger '%s' is not a trigger for '%s'. 15127 16 Cannot set the default language to a language ID not defined in syslanguages. 15128 16 The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned O FF when MUST_CHANGE is ON. 15129 16 '%d' is not a valid value for configuration option '%s'. 15130 16 There already exists a '%s' trigger for '%s'. 15131 16 Usage: sp_dbremove <dbname> [,dropdev] 15133 16 INSTEAD OF trigger '%s' cannot be associated with an order. 15134 16 No alias exists for the specified user. 15135 16 Object is invalid. Extended properties are not permitted on '%s' , or the object does not exist. 15136 16 The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped. 15137 16 An error occurred during the execution of sp_xp_cmdshell_proxy_a ccount. Possible reasons: the provided account was invalid or the '%.*ls' creden tial could not be created. Error code: %ls, Error Status: %d. 15138 16 The database principal owns a %S_MSG in the database, and cannot be dropped. 15141 16 The server principal owns one or more %S_MSG(s) and cannot be dr opped. 15143 16 '%s' is not a valid option for the @updateusage parameter. Enter either 'true' or 'false'. 15144 16 The role has members. It must be empty before it can be dropped. 15145 16 An implicit %S_MSG creation has failed. Reason: The %S_MSG may h ave been dropped or its name may already be in use. 15146 16 An encryption password must be provided to encrypt the private k ey of this %S_MSG. 15147 16 No decryption password should be provided because the private ke y of this %S_MSG is encrypted by a master key. 15148 16 The data type or table column '%s' does not exist or you do not have permission. 15149 16 Principal doesn't exist or doesn't have sufficient privileges. 15150 16 Cannot %S_MSG the %S_MSG '%.*ls'. 15151 16 Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or y ou do not have permission. 15152 16 Cannot update user instances. Reason: %ls. Error code: 0x%x. 15153 16 The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '%.*ls' credential exists and contains valid inform ation. 15154 16 The database principal owns an %S_MSG and cannot be dropped.

15155 16 The server principal owns a %S_MSG and cannot be dropped. 15156 16 The password that you specified is too long. The password should have no more than %d characters. 15157 16 Setuser failed because of one of the following reasons: the data base principal '%.*ls' does not exist, its corresponding server principal does n ot have server access, this type of database principal cannot be impersonated, o r you do not have permission. 15158 16 Cannot initialize security. 15159 16 Maximum impersonation nesting level exceeded (limit %d).. 15160 16 Cannot issue impersonation token from non-primary impersonation context or for non-Windows user. 15161 16 Cannot set application role '%.*ls' because it does not exist or the password is incorrect. 15162 16 Unexpected error while creating impersonation token. 15163 16 Invalid timeout value. Valid timeout is between 1 and 7200 sec. 15164 16 '%.*ls' is not a valid login or cannot be issued impersonation t oken. 15165 16 Could not find object '%ls' or you do not have permission. 15166 10 Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored. 15167 16 Cannot generate GUID. 15168 16 Cannot rename the view '%s' and its columns and indexes because it is a system generated view that was created for optimization purposes. 15169 16 The server option "%ls" is not available in this edition of SQL Server. 15170 16 This login is the owner of %ld job(s). You must delete or reassi gn these jobs before the login can be dropped. 15171 16 Cannot use the parameter "%s" for a certificate or asymmetric ke y login. 15172 16 FallBack certificate must be created or dropped in master databa se in single user mode. 15173 16 Server principal '%s' has granted one or more permission(s). Rev oke the permission(s) before dropping the server principal. 15174 16 Login '%s' owns one or more database(s). Change the owner of the database(s) before dropping the login. 15175 16 Login '%s' is aliased or mapped to a user in one or more databas e(s). Drop the user or alias before dropping the login. 15176 16 The only valid @parameter value is 'WITH_LOG'. 15177 16 Usage: sp_dropmessage <msg number> [,<language> | 'ALL'] 15178 16 Cannot drop a message with an ID less than 50,000. 15179 16 The message number %u or specified language version does not exi st. 15182 16 Cannot disable access to the guest user in master or tempdb. 15183 16 The database principal owns objects in the database and cannot b e dropped. 15184 16 The database principal owns data types in the database and canno t be dropped. 15185 16 There is no remote user '%s' mapped to local user '%s' from the remote server '%s'. 15186 16 The server principal is set as the execution context of a trigge r or event notification and cannot be dropped. 15187 10 The %S_MSG cannot be dropped because it is used by one or more % S_MSG(s). 15188 16 Cannot create an index that does not include all security column s. 15189 16 Cannot have more than one security column for a table. 15190 16 There are still remote logins or linked logins for the server '% s'. 15192 16 Cannot alter or drop the security column of a table. 15195 16 The MUST_CHANGE option is not supported by this version of Micro

soft Windows. 15196 16 The current security context is non-revertible. The "Revert" sta tement failed. 15197 16 There is no text for object '%s'. 15198 16 The name supplied (%s) is not a user, role, or aliased login. 15199 16 The current security context cannot be reverted. Please switch t o the original database where '%ls' was called and try it again. 15200 16 There are no remote servers defined. 15201 16 There are no remote logins for the remote server '%s'. 15202 16 There are no remote logins defined. 15203 16 There are no remote logins for '%s'. 15204 16 There are no remote logins for '%s' on remote server '%s'. 15205 16 There are no servers defined. 15206 16 Invalid Remote Server Option: '%s'. 15207 16 The trusted option in remote login mapping is no longer supporte d. 15208 16 The certificate, asymmetric key, or private key file is not vali d or does not exist; or you do not have permissions for it. 15209 16 An error occurred during encryption. 15212 16 Invalid certificate subject. The certificate subject must have b etween 1 and %d characters. 15213 16 Warning: The certificate you created has an invalid validity per iod; its expiration date precedes its start date. 15214 16 Warning: The certificate you created is expired. 15215 16 Warning: The certificate you created is not yet valid; its start date is in the future. 15216 16 '%s' is not a valid option for the @delfile parameter. 15217 16 Property cannot be updated or deleted. Property '%.*ls' does not exist for '%.*ls'. 15218 16 Object '%s' is not a table. 15219 16 Cannot change the owner of an indexed view. 15222 16 Remote login option '%s' is not unique. 15223 11 Error: The input parameter '%s' is not allowed to be null. 15224 11 Error: The value for the @newname parameter contains invalid cha racters or violates a basic restriction (%s). 15225 11 No item by the name of '%s' could be found in the current databa se '%s', given that @itemtype was input as '%s'. 15226 16 Cannot create alias types from an XML datatype. 15227 16 The database '%s' cannot be renamed. 15229 16 The argument specified for the "%.*ls" parameter of stored proce dure sp_db_vardecimal_storage_format is not valid. Valid arguments are 'ON' or ' OFF'. 15230 16 Error starting user instance. Error code: %d. 15231 16 The argument specified for the '@increased_partitions' parameter of stored procedure sp_db_increased_partitions is not valid. Valid arguments ar e 'ON', 'OFF', 'TRUE' and 'FALSE'. 15232 16 A certificate with name '%s' already exists or this certificate already has been added to the database. 15233 16 Property cannot be added. Property '%.*ls' already exists for '% .*ls'. 15234 16 Objects of this type have no space allocated. 15236 16 Column '%s' has no default. 15237 16 User data type '%s' has no default. 15238 16 Column '%s' has no rule. 15239 16 User data type '%s' has no rule. 15240 16 Cannot write into file '%s'. Verify that you have write permissi ons, that the file path is valid, and that the file does not already exist. 15241 16 Usage: sp_dboption [dbname [,optname [,'true' | 'false']]] 15242 16 Database option '%s' is not unique. 15243 16 The option '%s' cannot be changed for the master database.

15244 16 Only members of the sysadmin role or the database owner may set database options. 15246 16 Cannot dump the private key of certificate '%s' because the priv ate key cannot be found. 15247 16 User does not have permission to perform this action. 15248 11 Either the parameter @objname is ambiguous or the claimed @objty pe (%s) is wrong. 15249 11 Error: Explicit @objtype '%s' is unrecognized. 15250 16 The database name component of the object qualifier must be the name of the current database. 15251 16 Invalid '%s' specified. It must be %s. 15252 16 The primary or foreign key table name must be given. 15253 11 Syntax error parsing SQL identifier '%s'. 15254 16 Users other than the database owner or guest exist in the databa se. Drop them before removing the database. 15255 11 '%s' is not a valid value for @autofix. The only valid value is 'auto'. 15256 16 Usage: sp_certify_removable <dbname> [,'auto'] 15257 16 The database that you are attempting to certify cannot be in use at the same time. 15258 16 The database must be owned by a member of the sysadmin role befo re it can be removed. 15259 16 The DEFAULT_SCHEMA clause cannot be used with principals mapped to certificates or asymmetric keys. 15260 16 The format of the security descriptor string '%s' is invalid. 15261 16 Usage: sp_create_removable <dbname>,<syslogical>,<sysphysical>,< syssize>,<loglogical>,<logphysical>,<logsize>,<datalogical1>,<dataphysical1>,<da tasize1> [,<datalogical2>,<dataphysical2>,<datasize2>...<datalogical16>,<dataphy sical16>,<datasize16>] 15262 10 Invalid file size entered. All files must be at least 1 MB. 15263 16 A SID in the security descriptor string '%s' could not be found in an account lookup operation. 15264 16 Could not create the '%s' portion of the database. 15265 16 An unexpected error has occurred in the processing of the securi ty descriptor string '%s'. 15266 16 Cannot make '%s' database removable. 15267 16 A security descriptor with name '%s' already exists. 15268 10 Authentication mode is %s. 15269 16 Logical data device '%s' not created. 15271 16 Invalid @with_log parameter value. Valid values are 'true' or 'f alse'. 15272 10 The %s '%.*s' is not trusted to execute. 15273 10 The decryption key is incorrect. 15274 16 Access to the remote server is denied because the current securi ty context is not trusted. 15276 16 Cannot provision master key passwords for system databases. 15277 16 The only valid @parameter_value values are 'true' or 'false'. 15278 16 Login '%s' is already mapped to user '%s' in database '%s'. 15279 16 You must add the us_english version of this message before you c an add the '%s' version. 15280 16 All localized versions of this message must be dropped before th e us_english version can be dropped. 15281 10 SQL Server blocked access to %S_MSG '%ls' of component '%.*ls' b ecause this component is turned off as part of the security configuration for th is server. A system administrator can enable the use of '%.*ls' by using sp_conf igure. For more information about enabling '%.*ls', search for '%.*ls' in SQL Se rver Books Online. 15282 10 A key with name '%.*ls' or user defined unique identifier alread y exists or you do not have permissions to create it. 15283 16 The name '%s' contains too many characters.

15284 16 The database principal has granted or denied permissions to obje cts in the database and cannot be dropped. 15285 16 The special word '%s' cannot be used for a logical device name. 15286 16 Terminating this procedure. The @action '%s' is unrecognized. Tr y 'REPORT', 'UPDATE_ONE', or 'AUTO_FIX'. 15287 16 Terminating this procedure. '%s' is a forbidden value for the lo gin name parameter in this procedure. 15288 10 Please specify one decryptor to decrypt a key. 15289 16 Terminating this procedure. Cannot have an open transaction when this is run. 15291 16 Terminating this procedure. The %s name '%s' is absent or invali d. 15292 10 The row for user '%s' will be fixed by updating its login link t o a login already in existence. 15293 10 Barring a conflict, the row for user '%s' will be fixed by updat ing its link to a new login. 15294 10 The number of orphaned users fixed by adding new logins and then updating users was %d. 15295 10 The number of orphaned users fixed by updating users was %d. 15296 16 General cryptographic failure. 15297 16 The certificate, asymmetric key, or private key data is invalid. 15299 16 The signature of the public key is invalid. 15300 11 No recognized letter is contained in the parameter value for Gen eral Permission Type (%s). Valid letters are in this set: %s . 15301 16 Collation '%s' is supported for Unicode data types only and cann ot be set at either the database or server level. 15302 11 Database_Name should not be used to qualify owner.object for the parameter into this procedure. 15303 11 The "user options" config value (%d) was rejected because it wou ld set incompatible options. 15304 16 The severity level of the '%s' version of this message must be t he same as the severity level (%ld) of the us_english version. 15305 16 The @TriggerType parameter value must be 'insert', 'update', or 'delete'. 15306 16 Cannot change the compatibility level of replicated or distribut ed databases. 15307 16 Could not change the merge publish option because the server is not set up for replication. 15309 16 Cannot alter the trustworthy state of the model or tempdb databa ses. 15310 16 Failed to configure user instance on startup. Error updating ser ver metadata. 15311 16 The file named '%s' does not exist. 15312 16 The file named '%s' is a primary file and cannot be removed. 15313 10 The key is not encrypted using the specified decryptor. 15314 10 Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of Window s. 15315 10 The key '%.*ls' is not open. Please open the key before using it . 15316 10 Global temporary keys are not allowed. You can only use local te mporary keys. 15317 10 The master key file does not exist or has invalid format. 15318 10 All fragments for database '%s' on device '%s' are now dedicated for log usage only. 15319 17 Error: DBCC DBREPAIR REMAP failed for database '%s' (device '%s' ). 15320 16 An error occurred while decrypting %S_MSG '%.*ls' that was encry pted by the old master key. The FORCE option can be used to ignore this error an d continue the operation, but data that cannot be decrypted by the old master ke

y will become unavailable. 15321 16 There was some problem removing '%s' from sys.master_files. 15322 10 File '%s' was removed from tempdb, and will take effect upon ser ver restart. 15323 16 The selected index does not exist on table '%s'. 15324 16 The option %s cannot be changed for the '%s' database. 15325 16 The current database does not contain a %s named '%ls'. 15326 10 No extended stored procedures exist. 15327 10 The database is now offline. 15328 10 The database is offline already. 15329 16 The current master key cannot be decrypted. If this is a databas e master key, you should attempt to open it in the session before performing thi s operation. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost. 15330 11 There are no matching rows on which to report. 15331 11 The user '%s' cannot take the action auto_fix due to duplicate S ID. 15332 10 The private key is already set for this file. To change it you s hould drop and re-create the certificate. 15333 11 Error: The qualified @oldname references a database (%s) other t han the current database. 15334 10 The %S_MSG has a private key that is protected by a user defined password. That password needs to be provided to enable the use of the private k ey. 15335 11 Error: The new name '%s' is already in use as a %s name and woul d cause a duplicate that is not permitted. 15336 16 Object '%s' cannot be renamed because the object participates in enforced dependencies. 15337 10 Caution: sys.sql_dependencies shows that other objects (views, p rocedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly. 15339 10 Creating '%s'. 15342 10 There is no private key provisioned for %S_MSG '%.*ls'. 15343 10 The username and/or password passed in is invalid or the current process does not have sufficient privileges. 15344 16 Ownership change for %S_MSG is not supported. 15345 16 An entity of type %S_MSG cannot be owned by a role, a group, or by principals mapped to certificates or asymmetric keys. 15346 16 Cannot change owner for an object that is owned by a parent obje ct. Change the owner of the parent object instead. 15347 16 Cannot transfer an object that is owned by a parent object. 15348 16 Cannot transfer a schemabound object. 15349 16 Cannot transfer an MS Shipped object. 15350 16 An attempt to attach an auto-named database for file %.*ls faile d. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. 15351 10 The CLR procedure/function/type being signed refers to an assemb ly that is not signed either by a strong name or an assembly. 15352 16 The %S_MSG cannot be dropped because one or more entities are ei ther signed or encrypted using it. 15353 16 An entity of type %S_MSG cannot be owned by a role, a group, an approle, or by principals mapped to certificates or asymmetric keys. 15354 10 Usage: sp_detach_db <dbname>, [TRUE|FALSE], [TRUE|FALSE] 15356 16 The current application role has been dropped. The current secur ity context contains no valid database user context. 15357 16 The current security context was set by "%ls". It cannot be reve rted by statement "%ls". 15358 10 User-defined filegroups should be made read-only. 15359 16 Cannot add functional unit '%.*ls' to component '%.*ls'. This un it has been already registered with the component.

15360 16 An error occurred while trying to load the xpstar dll to read th e agent proxy account from LSA. 15361 16 An error occurred while trying to read the SQLAgent proxy accoun t credentials from the LSA. 15362 16 An error occurred while trying to create the '%.*ls' credential. 15364 16 Failed to generate a user instance of SQL Server. Only an integr ated connection can generate a user instance. The connection will be closed.%.*l s 15365 16 Failed to generate a user instance of SQL Server. Only members o f Builtin\Users can generate a user instance. The connection will be closed.%.*l s 15366 16 Failed to generate a user instance of SQL Server due to low memo ry. The connection will be closed.%.*ls 15367 16 Failed to generate a user instance of SQL Server due to a failur e in generating a unique user instance name. The connection will be closed.%.*ls 15368 16 Failed to generate a user instance of SQL Server due to a failur e in reading registry keys. The connection will be closed.%.*ls 15369 16 Failed to generate a user instance of SQL Server due to a failur e in impersonating the client. The connection will be closed.%.*ls 15370 16 Failed to generate a user instance of SQL Server due to a failur e in copying database files. The connection will be closed.%.*ls 15371 16 Failed to generate a user instance of SQL Server due to a failur e in creating user instance event. The connection will be closed.%.*ls 15372 16 Failed to generate a user instance of SQL Server due to a failur e in starting the process for the user instance. The connection will be closed.% .*ls 15373 16 Failed to generate a user instance of SQL Server due to a failur e in obtaining the user instance's process information. The connection will be c losed.%.*ls 15374 16 Failed to generate a user instance of SQL Server due to a failur e in persisting the user instance information into system catalog. The connectio n will be closed.%.*ls 15375 16 Failed to generate a user instance of SQL Server due to a failur e in making a connection to the user instance. The connection will be closed.%.* ls 15376 16 Failed to generate a user instance of SQL Server. Only the SQL S erver Express version lets you generate a user instance. The connection will be closed.%.*ls 15377 16 Failed to configure user instance on startup. Error adding user to sysadmin role. 15378 16 Failed to configure user instance on startup. Error configuring system database entries in MASTER DB. 15380 16 Failed to configure user instance on startup. Error configuring system database paths in MASTER DB. 15381 16 Failed to generate a user instance of SQL Server due to a failur e in updating security descriptor on the process of the user instance. 15382 16 Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.%.*ls 15383 16 Generating user instances in SQL Server is disabled. Use sp_conf igure 'user instances enabled' to generate user instances.%.*ls 15384 16 Failed to configure user instance on startup. Error updating Res ource Manager ID. 15385 16 No database principal is defined for sid '%.*ls'. 15386 16 Another batch in the session is changing security context, new b atch is not allowed to start. 15387 11 If the qualified object name specifies a database, that database must be the current database. 15388 11 There is no user table matching the input name '%s' in the curre nt database or you do not have permission to access the table.

15389 11 sp_indexoption is not supported for XML or spatial indexes. Use ALTER INDEX instead. 15390 11 Input name '%s' does not have a matching user table or indexed v iew in the current database. 15391 11 sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option for ALL the indexe s. 15392 16 The specified option '%s' is not supported by this edition of SQ L Server and cannot be changed using sp_configure. 15393 16 An error occurred while decrypting the password for linked login '%.*ls' that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the ol d master key will be lost. 15394 16 Collation '%s' is not supported by the operating system 15395 11 The qualified old name could not be found for item type '%s'. 15396 16 An asymmetric key with name '%s' already exists or this asymmetr ic key already has been added to the database. 15397 16 The %S_MSG is not protected by a password. A decryption password cannot be used for this operation. 15398 11 Only objects in the master database owned by dbo can have the st artup setting changed. 15399 11 Could not change startup option because this option is restricte d to objects that have no parameters. 15401 11 Windows NT user or group '%s' not found. Check the name again. 15402 11 '%s' is not a fixed server role. 15403 16 The server principal "%.*ls" does not exist, does not have serve r access, or you do not have permission. 15404 16 Could not obtain information about Windows NT group/user '%ls', error code %#lx. 15405 11 Cannot use the special principal '%s'. 15406 16 Cannot execute as the server principal because the principal "%. *ls" does not exist, this type of principal cannot be impersonated, or you do no t have permission. 15407 11 '%s' is not a valid Windows NT name. Give the complete name: <do main\username>. 15408 16 "%ls" cannot be called in this batch because a simultaneous batc h has called it. 15409 11 '%s' is not a role. 15410 11 User or role '%s' does not exist in this database. 15411 11 Database principal or schema '%s' does not exist in this databas e. 15412 11 '%s' is not a known fixed role. 15413 11 Cannot make a role a member of itself. 15414 16 Cannot set compatibility level because database has a view or co mputed column that is indexed. These indexes require a SQL Server compatible dat abase. 15416 16 Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]] 15418 16 Only members of the sysadmin role or the database owner may set the database compatibility level. 15419 16 Supplied parameter sid should be binary(16). 15420 16 The group '%s' does not exist in this database. 15421 16 The database principal owns a database role and cannot be droppe d. 15422 16 Application roles can only be activated at the ad hoc level. 15425 16 No server principal is defined for sid '%.*ls'. 15426 16 You must specify a provider name with this set of properties. 15427 16 You must specify a provider name for unknown product '%ls'. 15428 16 You cannot specify a provider or any properties for product '%ls '. 15429 16 '%ls' is an invalid product name.

15431 16 You must specify the @rolename parameter. 15432 16 Stored procedure '%s' can only be executed at the ad hoc level. 15433 16 Supplied parameter sid is in use. 15434 16 Could not drop login '%s' as the user is currently logged in. 15435 10 Database successfully published. 15436 10 Database successfully enabled for subscriptions. 15437 10 Database successfully published using merge replication. 15438 10 Database is already online. 15439 10 Database is now online. 15440 10 Database is no longer published. 15441 10 Database is no longer enabled for subscriptions. 15442 10 Database is no longer enabled for merge publications. 15443 10 Checkpointing database that was changed. 15448 16 Encryption by the machine key cannot be added to the service mas ter key because the service master key cannot be decrypted or does not exist. 15450 10 New language inserted. 15451 16 Dropping an encryption from the service master key failed. No en cryption by the machine key exists. 15452 10 No alternate languages are available. 15453 10 us_english is always available, even though it is not in syslang uages. 15454 10 Language deleted. 15455 16 Adding an encryption to the service master key failed. An encryp tion by the machine key already exists. 15457 10 Configuration option '%ls' changed from %ld to %ld. Run the RECO NFIGURE statement to install. 15458 10 Database removed. 15459 10 In the current database, the specified object references the fol lowing: 15460 10 In the current database, the specified object is referenced by t he following: 15461 10 Object does not reference any object, and no objects reference i t. 15462 10 File '%s' closed. 15463 10 Device dropped. 15464 16 Unsupported private key format or key length. 15465 16 The private key password is invalid. 15466 16 An error occurred during decryption. 15468 16 An error occurred during the generation of the %S_MSG. 15469 10 No constraints are defined on object '%ls', or you do not have p ermissions. 15470 10 No foreign keys reference table '%ls', or you do not have permis sions on referencing tables. 15471 10 The text for object '%ls' is encrypted. 15472 10 The object '%ls' does not have any indexes, or you do not have p ermissions. 15474 16 Invalid private key. The private key does not match the public k ey of the %S_MSG. 15475 10 The database is renamed and in single user mode. 15477 10 Caution: Changing any part of an object name could break scripts and stored procedures. 15482 16 Cannot change the owner of a table that has an indexed view. 15490 10 The dependent aliases were also dropped. 15497 10 Could not add login using sp_addlogin (user = %s). Terminating t his procedure. 15499 10 The dependent aliases were mapped to the new database owner. 15500 10 The dependent aliases were dropped. 15502 10 Setting database owner to SA. 15503 10 Giving ownership of all objects to the database owner. 15504 10 Deleting users except guest and the database owner from the syst

em catalog. 15505 16 Cannot change owner of object '%ls' or one of its child objects because the new owner '%ls' already has an object with the same name. 15506 16 An error occurred while signing. 15507 16 A key required by this operation appears to be corrupted. 15508 16 An error occurred while generating a key required by this operat ion. 15509 16 The password cannot be dropped because another database may be u sing it. 15510 16 Cannot enable a login that has an empty password. 15511 10 Default bound to column. 15512 10 Default bound to data type. 15513 10 The new default has been bound to columns(s) of the specified us er data type. 15514 10 Rule bound to table column. 15515 10 Rule bound to data type. 15516 10 The new rule has been bound to column(s) of the specified user d ata type. 15517 16 Cannot execute as the database principal because the principal " %.*ls" does not exist, this type of principal cannot be impersonated, or you do not have permission. 15518 16 Cannot execute as the Windows token. It is not valid, or you do not have permission. 15519 10 Default unbound from table column. 15520 10 Default unbound from data type. 15521 10 Columns of the specified user data type had their defaults unbou nd. 15522 10 Rule unbound from table column. 15523 10 Rule unbound from data type. 15524 10 Columns of the specified user data type had their rules unbound. 15525 10 sp_checknames is used to search for non 7-bit ASCII characters. 15526 10 in several important columns of system tables. The following 15527 10 columns are searched: 15528 10 In master: 15529 16 Cannot execute as the ticket. It is not valid, or you do not hav e permission. 15530 16 The %S_MSG with name "%.*ls" already exists. 15531 16 The security descriptor information is not valid. 15532 16 The security descriptor is invalid because it does not contain i nformation about its owner or about its primary group. 15533 16 Invalid data type is supplied in the '%ls' statement. 15534 16 Cookie generation failed in the '%ls' statement. 15535 16 Cannot set a credential for principal '%.*ls'. 15536 10 In all databases: 15537 16 Login '%.*ls' does not have access to server. 15538 16 Login '%.*ls' does not have access to database. 15539 16 User '%s' cannot be dropped, it can only be disabled. The user i s already disabled in the current database. 15540 16 The identity string is too long. The identity string should cont ain no more than %d characters. 15541 16 Cannot drop the credential '%.*ls' because it is used by a serve r principal. 15542 10 Cannot create a key without specifying an encryptor. 15556 10 Cannot decrypt or encrypt using the specified %S_MSG, either bec ause it has no private key or because the password provided for the private key is incorrect. 15557 10 There is already a %S_MSG by %S_MSG '%.*ls'. 15558 10 Cannot drop %S_MSG by %S_MSG '%.*s'. 15559 10 Cannot drop %S_MSG '%.*ls' because there is a %S_MSG mapped to i t.

15560 10 Cannot add or drop a signature on '%.*ls' because only modules c an be signed. 15561 10 Signatures based on certificates or asymmetric keys are the only options supported in this version of the product. 15562 10 The module being executed is not trusted. Either the owner of th e database of the module needs to be granted authenticate permission, or the mod ule needs to be digitally signed. 15563 10 The %S_MSG has no private key set for it. 15574 10 This object does not have any statistics. 15575 10 This object does not have any statistics or indexes. 15576 16 You cannot set network name on server '%ls' because it is not a linked SQL Server. 15577 10 Warning: A linked server that refers to the originating server i s not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias. 15578 16 There is already a master key in the database. Please drop it be fore performing this statement. 15579 16 Adding an encryption to the symmetric key failed. An encryption by the same %S_MSG '%.*s' may already exist. 15580 16 Cannot drop %S_MSG because %S_MSG '%.*s' is encrypted by it. 15581 16 Please create a master key in the database or open the master ke y in the session before performing this operation. 15583 10 The module being signed is marked to execute as owner. If the ow ner changes the signature will not be valid. 15584 10 An error occurred while decrypting %S_MSG '%.*ls' that was encry pted by the old master key. The error was ignored because the FORCE option was s pecified. 15585 10 The current master key cannot be decrypted. The error was ignore d because the FORCE option was specified. 15586 16 Error in synchronizing system certificates between master and re source database. 15587 16 Cannot change owner of Assembly '%.*ls' since dependent assembly '%.*ls' is not owned by the new owner. 15588 10 The old and new master keys are identical. No data re-encryption is required. 15589 16 Cannot revert the current security context because the cookie is invalid. 15590 16 Can only use the 'No Revert' or 'Cookie' options with the 'Execu te As' statement at the adhoc level. 15591 16 The current security context cannot be reverted using this state ment. A cookie may or may not be needed with 'Revert' statement depending on how the context was set with 'Execute As' statement. 15592 16 Cannot unset application role because none was set or the cookie is invalid. 15593 16 An error occurred while decrypting the password for linked login '%.*ls' that was encrypted by the old master key. The error was ignored because the FORCE option was specified. 15594 16 The password is already provisioned for the database '%.*ls' 15595 16 The password cannot be dropped because it is not provisioned for the database '%.*ls' 15596 10 Warning: use of a UNIQUE index, PRIMARY KEY constraint, or UNIQU E constraint on a table with row-level security can allow information disclosure . 15597 10 Warning: use of an IDENTITY column on a table with row-level sec urity can allow information disclosure. 15598 10 Warning: use of an indexed view on a table with row-level securi ty can allow information disclosure. 15599 10 Auditing and permissions can't be set on local temporary objects . 15600 15 An invalid parameter or option was specified for procedure '%s'.

15601 16 Full-Text Search is not enabled for the current database. Use sp _fulltext_database to enable Full-Text Search. The functionality to disable and enable full-text search for a database is deprecated. Please change your applica tion. 15612 16 DBCC DBCONTROL error. Database was not made read-only. 15615 16 DBCC DBCONTROL error. Database was not made single user. 15622 10 No permission to access database '%s'. 15625 10 Option '%ls' not recognized for '%ls' parameter. 15626 10 You attempted to acquire a transactional application lock withou t an active transaction. 15627 10 sp_dboption command failed. 15635 16 Cannot execute '%ls' because the database is in read-only access mode. 15645 16 Column '%ls' does not exist. 15646 16 Column '%ls' is not a computed column. 15647 10 No views with schema binding reference table '%ls'. 15650 10 Updating %s 15651 10 %d index(es)/statistic(s) have been updated, %d did not requ ire update. 15652 10 %s has been updated... 15653 10 %s, update is not necessary... 15654 10 Table %s: cannot perform the operation on the table because its clustered index is disabled. 15656 16 Cannot create user defined types from XML data type. 15657 16 Vardecimal storage format is not available in system database '% s'. 15658 16 Cannot run sp_resetstatus against a database snapshot. 15659 16 The schema '%ls' specified for parameter schema_name does not ex ist. 15660 16 Compressing XML index is not supported by the stored procedure s p_estimate_data_compression_savings. 15661 16 Compressing temporary tables is not supported by the stored proc edure sp_estimate_data_compression_savings. 15662 16 Compressing tables with sparse columns or column sets is not sup ported by the stored procedure sp_estimate_data_compression_savings. 15663 16 Feature "sp_addserver" is no longer supported. Replace remote se rvers by using linked servers. 16901 16 %hs: This feature has not been implemented yet. 16902 16 %ls: The value of the parameter %ls is invalid. 16903 16 The "%ls" procedure was called with an incorrect number of param eters. 16904 16 sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE. 16905 16 The cursor is already open. 16906 17 Temporary storage used by the cursor to store large object varia ble values referred by the cursor query is not usable any more. 16907 16 %hs is not allowed in cursor statements. 16909 16 %ls: The cursor identifier value provided (%x) is not valid. 16910 16 The cursor %.*ls is currently used by another statement. 16911 16 %hs: The fetch type %hs cannot be used with forward only cursors . 16914 16 The "%ls" procedure was called with too many parameters. 16915 16 A cursor with the name '%.*ls' already exists. 16916 16 A cursor with the name '%.*ls' does not exist. 16917 16 Cursor is not open. 16922 16 Cursor Fetch: Implicit conversion from data type %s to %s is not allowed. 16924 16 Cursorfetch: The number of variables declared in the INTO list m ust match that of selected columns. 16925 16 The fetch type %hs cannot be used with dynamic cursors.

16926 16 sp_cursoroption: The column ID (%d) does not correspond to a tex t, ntext, or image column. 16927 16 Cannot fetch into text, ntext, and image variables. 16928 16 sp_cursor: Exec statement is not allowed as source for cursor in sert. 16929 16 The cursor is READ ONLY. 16930 16 The requested row is not in the fetch buffer. 16931 16 There are no rows in the current fetch buffer. 16932 16 The cursor has a FOR UPDATE list and the requested column to be updated is not in this list. 16933 16 The cursor does not include the table being modified or the tabl e is not updatable through the cursor. 16934 10 Optimistic concurrency check failed. The row was modified outsid e of this cursor. 16935 16 No parameter values were specified for the sp_cursor-%hs stateme nt. 16936 16 sp_cursor: One or more values parameters were invalid. 16937 16 A server cursor cannot be opened on the given statement or state ments. Use a default result set or client cursor. 16938 16 sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMP UTE BY, or variable assignments. 16941 16 Cursor updates are not allowed on tables opened with the NOLOCK option. 16942 16 Could not generate asynchronous keyset. The cursor has been deal located. 16943 16 Could not complete cursor operation because the table schema cha nged after the cursor was declared. 16945 16 The cursor was not declared. 16946 16 Could not open the cursor because one or more of its tables have gone out of scope. 16947 16 No rows were updated or deleted. 16948 16 The variable '%.*ls' is not a cursor variable, but it is used in a place where a cursor variable is expected. 16949 16 The variable '%.*ls' is a cursor variable, but it is used in a p lace where a cursor variable is not valid. 16950 10 The variable '%.*ls' does not currently have a cursor allocated to it. 16951 16 The variable '%.*ls' cannot be used as a parameter because a CUR SOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure. 16952 16 A cursor variable cannot be used as a parameter to a remote proc edure call. 16953 10 Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor. 16954 16 Executing SQL directly; no cursor. 16955 16 Could not create an acceptable cursor. 16956 10 The created cursor is not of the requested type. 16957 16 FOR UPDATE cannot be specified on a READ ONLY cursor. 16958 16 Could not complete cursor operation because the set options have changed since the cursor was declared. 16959 16 Unique table computation failed. 16960 16 You have reached the maximum number of cursors allowed. 16961 10 One or more FOR UPDATE columns have been adjusted to the first i nstance of their table in the query. 16962 16 The target object type is not updatable through a cursor. 16963 16 You cannot specify scroll locking on a cursor that contains a re mote table. 16964 16 For the optimistic cursor, timestamp columns are required if the

update or delete targets are remote. 16965 16 Cursor scroll locks were invalidated due to a transaction defect . Reissue the UPDATE or DELETE statement after a cursor fetch. 16966 16 %ls: Specified concurrency control option %d (%ls) is incompatib le with static or fast forward only cursors. Only read-only is compatible with s tatic or fast forward only cursors. 16992 16 The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielde d to let the asynchronous population to continue. 16996 16 %ls cannot take output parameters. 16998 16 The asynchronous cursor worktable population thread spawn failed . 16999 20 Internal Cursor Error: The cursor is in an invalid state. 17000 10 Usage: sp_autostats <table_name> [, {ON|OFF} [, <index_name>] ] 17001 16 Failure to send an event notification instance of type '%s' on c onversation handle '%s'. Error Code = '%s'. 17002 16 Failed to post QUEUE_ACTIVATION event. Error code: '0x%s'. 17003 16 Closed event notification conversation endpoint with handle '%s' , due to the following error: '%.*ls'. 17004 16 Event notification conversation on dialog handle '%s' closed wit hout an error. 17005 16 Event notification '%ls' in database '%ls' dropped due to send t ime service broker errors. Check to ensure the conversation handle, service brok er contract, and service specified in the event notification are active. 17049 16 Unable to cycle error log file from '%ls' to '%ls' due to OS err or '%s'. A process outside of SQL Server may be preventing SQL Server from readi ng the files. As a result, errorlog entries may be lost and it may not be possib le to view some SQL Server errorlogs. Make sure no other processes have locked t he file with write-only access." 17051 16 SQL Server evaluation period has expired. 17053 16 %ls: Operating system error %ls encountered. 17054 16 The current event was not reported to the Windows Events log. Op erating system error = %s. You may need to clear the Windows Events log if it is full. 17056 10 The evaluation period for your edition of SQL Server expires in %d day(s). 17057 16 Security context for operating system objects could not be creat ed. SQL Server cannot be started. Look for corresponding entries in the event vi ewer to help diagnose the root cause. 17058 16 initerrlog: Could not open error log file '%s'. Operating system error = %s. 17060 10 %s 17061 10 Error: %d Severity: %d State: %d %s 17063 16 Error: %d Severity: %d State: %d %s 17065 16 SQL Server Assertion: File: <%s>, line = %d Failed Assertion = ' %s' %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 17066 16 SQL Server Assertion: File: <%s>, line=%d Failed Assertion = '%s '. This error may be timing-related. If the error persists after rerunning the s tatement, use DBCC CHECKDB to check the database for structural integrity, or re start the server to ensure in-memory data structures are not corrupted. 17067 16 SQL Server Assertion: File: <%s>, line = %d %s. This error may b e timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 17068 10 PrintStack Request 17069 10 %s 17070 16 Clustered instances are not supported on this edition of SQL Ser ver.

17071 16 SQL Server could not start due to a boot failure. Operating syst em error = %s. 17072 17 The Extended Event session could not be created. 17073 16 Executing 'sp_server_diagnostics' stored procedure in repeat mod e with 'insert into' clause is not allowed. 17074 16 Assertion "%ls" with message "%ls" at <%ls>:%ld failed. 17075 16 Assertion "%ls" at <%ls>:%ld failed. 17076 21 Error spawning System Health Monitor thread: %ls 17101 10 (c) Microsoft Corporation. 17102 16 Failed to initialize Distributed COM (CoInitializeEx returned %l x). Heterogeneous queries and remote procedure calls are disabled. Check the DCO M configuration using Component Services in Control Panel. 17103 10 All rights reserved. 17104 10 Server process ID is %ld. 17105 10 Could not open master database in system task thread context. Te rminating server. 17106 10 Common Criteria compliance mode is enabled. This is an informati onal message only; no user action is required. 17107 10 Perfmon counters for resource governor pools and groups failed t o initialize and are disabled. 17108 10 Password policy update was successful. 17109 10 FallBack certificate was successfully created. 17110 10 Registry startup parameters: %.*ls 17111 10 Logging SQL Server messages in file '%s'. 17112 16 An invalid startup option '%s' was supplied, either from the reg istry or the command prompt. Correct or remove the option. 17113 16 Error %ls occurred while opening file '%ls' to obtain configurat ion information at startup. An invalid startup option might have caused the erro r. Verify your startup options, and correct or remove them if necessary. 17114 16 Error %ls occurred while opening file '%ls' to obtain configurat ion information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary. 17115 10 Command Line Startup Parameters:%.*ls 17116 16 Failed to initialize distributed COM; DCOM is not installed. Het erogeneous queries and remote procedure calls are disabled. Check the DCOM confi guration using Component Services in Control Panel. 17119 10 The number of concurrent user connections was reduced to %ld, be cause it exceeded the allowable limit for this edition of SQL Server. To avoid t his message in the future, use sp_configure to permanently adjust the number of user connections within the licensed limit. 17120 16 SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. 17121 10 SQL Server is started with trace flag %d, this may cause user to see some error messages masked using '%ls'. 17123 10 Logging to event log is disabled. Startup option '-%c' is suppli ed, either from the registry or the command prompt. 17124 10 SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required. 17125 10 Using dynamic lock allocation. Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required. 17126 10 SQL Server is now ready for client connections. This is an infor mational message; no user action is required. 17127 16 initdata: No memory for kernel buffer hash table. 17128 16 initdata: No memory for kernel buffers. 17129 10 initconfig: Warning: affinity specified is not valid. Defaulting to no affinity. Use ALTER SERVER CONFIGURATION SET PROCESS AFFINITY to configur e the system to be compatible with the CPU mask on the system. You can also conf igure the system based on the number of licensed CPUs. 17130 16 Not enough memory for the configured number of locks. Attempting

to start with a smaller lock hash table, which may impact performance. Contact the database administrator to configure more memory for this instance of the Dat abase Engine. 17131 16 Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory. 17132 16 Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory. 17133 16 Launch of startup procedure '%s' failed. 17135 10 Launched startup procedure '%s'. 17136 10 Clearing tempdb database. 17137 10 Starting up database '%.*ls'. 17138 16 Unable to allocate enough memory to start '%ls'. Reduce non-esse ntial memory load or increase system memory. 17139 10 The SQL Server image %ls was allocated using the large pages opt ion. 17140 16 Could not dispatch SQL Server by Service Control Manager. Operat ing system error = %s. 17141 16 Could not register Service Control Handler. Operating system err or = %s. 17142 16 SQL Server service has been paused. No new connections will be a llowed. To resume the service, use SQL Computer Manager or the Services applicat ion in Control Panel. 17143 16 %s: Could not set Service Control Status. Operating system error = %s. 17144 10 SQL Server is not allowing new connections because the Service C ontrol Manager requested a pause. To resume the service, use SQL Computer Manage r or the Services application in Control Panel. 17145 10 Service Control Handler received an invalid control code = %d. 17146 10 SQL Server is allowing new connections in response to 'continue' request from Service Control Manager. This is an informational message only. No user action is required. 17147 10 SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. 17148 10 SQL Server is terminating in response to a 'stop' request from S ervice Control Manager. This is an informational message only. No user action is required. 17149 10 Using the static lock allocation specified in the locks configur ation option. Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required. 17150 10 Lock partitioning is enabled. This is an informational message only. No user action is required. 17152 10 Node configuration: node %ld: CPU mask: 0x%0*I64x:%u Active CPU mask: 0x%0*I64x:%u. This message provides a description of the NUMA configuratio n for this computer. This is an informational message only. No user action is re quired. 17153 10 Processor affinity turned on: node %d, processor mask 0x%0*I64x. Threads will execute on CPUs per affinity settings. This is an informational me ssage; no user action is required. 17155 10 I/O affinity turned on, processor mask 0x%0*I64x. Disk I/Os will execute on CPUs per affinity I/O mask/affinity64 mask config option. This is an informational message only; no user action is required. 17156 16 initeventlog: Could not initiate the EventLog Service for the ke y '%s', last error code is %d. 17158 10 The server resumed execution after being idle %d seconds. This i s an informational message only. No user action is required. 17159 10 The server is idle. This is an informational message only. No us er action is required. 17161 10 SQL Server could not use the NO_BUFFERING option during I/O, bec ause the master file sector size, %d, is incorrect. Move the master file to a dr ive with a correct sector size.

17162 10 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 17163 10 SQL Server is starting at high priority base (=13). This is an i nformational message only. No user action is required. 17164 10 SQL Server detected %d sockets with %d cores per socket and %d l ogical processors per socket, %d total logical processors; using %d logical proc essors based on SQL Server licensing. This is an informational message; no user action is required. 17165 10 The RANU instance is terminating in response to its internal tim e out. This is an informational message only. No user action is required. 17166 10 Attempting to initialize Microsoft Distributed Transaction Coord inator (MS DTC). This is an informational message only. No user action is requir ed. 17167 10 Support for distributed transactions was not enabled for this in stance of the Database Engine because it was started using the minimal configura tion option. This is an informational message only. No user action is required. 17169 10 Unable to locate kernel HTTP driver Httpapi.dll in path. SQL Ser ver native HTTP support is not available. Error: 0x%lx Your operating system may not support the kernel HTTP driver. 17170 10 SQL Server native HTTP support is not available. Could not find function entry point '%hs' in %hs. Error 0x%lx. Native HTTP access to SQL Server requires a later version of the operating system. 17171 10 SQL Server native HTTP support failed and will not be available. '%hs()' failed. Error 0x%lx. 17172 16 SNIInitialize() failed with error 0x%lx. 17173 10 Ignoring trace flag %u specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server start up. 17174 10 Unable to initialize SQL Server native HTTP support due to insuf ficient resources. HTTP access to SQL Server will not be available. Error 0x%lx. This error typically indicates insufficient memory. Reduce non-essential memory load or increase system memory. 17175 10 The registry settings for SNI protocol configuration are incorre ct. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx. 17176 10 This instance of SQL Server last reported using a process ID of %s at %s (local) %s (UTC). This is an informational message only; no user action is required. 17177 10 This instance of SQL Server has been using a process ID of %s si nce %s (local) %s (UTC). This is an informational message only; no user action i s required. 17181 16 SNIInitializeListener() failed with error 0x%lx. 17182 16 TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls 17183 10 Attempting to cycle error log. This is an informational message only; no user action is required. 17184 10 The error log has been reinitialized. See the previous log for o lder entries. 17185 16 Unable to update password policy. 17186 16 Failed to enqueue %s task. There may be insufficient memory. 17187 16 SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. %.*ls 17188 16 SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls 17189 16 SQL Server failed with error code 0x%x to spawn a thread to proc ess a new login or connection. Check the SQL Server error log and the Windows ev ent logs for information about possible related problems.%.*ls 17190 16 Initializing the FallBack certificate failed with error code: %d , state: %d, error number: %d.

17191 16 Cannot accept a new connection because the session has been term inated. This error occurs when a new batch execution is attempted on a session t hat is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or becaus e of severe errors.%.*ls 17192 10 Dedicated admin connection support was not started because of er ror 0x%lx, status code: 0x%lx. This error typically indicates a socket-based err or, such as a port already in use. 17193 10 SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required. 17194 16 The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configur ed the server. See Books Online for information on this error message: %d %.*ls %.*ls 17195 16 The server was unable to complete its initialization sequence be cause the available network libraries do not support the required level of encry ption. The server process has stopped. Before restarting the server, verify that SSL certificates have been installed. See Books Online topic "Configuring Clien t Protocols and Network Libraries". 17196 10 Preparing for eventual growth to %d GB with Hot Add Memory. 17197 16 Login failed due to timeout; the connection has been closed. Thi s error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls 17198 16 Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attempt to connect to a different endpoint on the server.%.*ls 17199 10 Dedicated administrator connection support was not started becau se it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag %d. This is an informational message only. No user action is required. 17200 16 Changing the remote access settings for the Dedicated Admin Conn ection failed with error 0x%lx, status code 0x%lx. 17201 10 Dedicated admin connection support was established for listening locally on port %d. 17202 10 Dedicated admin connection support was established for listening remotely on port %d. 17203 16 SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to t he System Requirements section in BOL for further information. 17204 16 %ls: Could not open file %ls for file number %d. OS error: %ls. 17205 10 File %ls in database %ls has been set to sparse by the file syst em but does not belong to a database snapshot. The file should be restored to co rrect the problem. 17207 16 %ls: Operating system error %ls occurred while creating or openi ng file '%ls'. Diagnose and correct the operating system error, and retry the op eration. 17208 16 %s: File '%s' has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database fr om backup. 17253 10 SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file '%s', %d, is invalid. Move the file to a disk with a valid sector size. 17255 10 Secondary TempDB file '%.*ls' resides on a removable drive and t herefore will not be attached during startup. 17256 10 Secondary TempDB file '%.*ls' will not be attached during TempDB startup; Drive check failed with error '%ld'. 17257 10 System error while trying to initialize disk info; Error '%ld' 17258 10 No free space in the TempDB database 17300 16 SQL Server was unable to run a new system task, either because t

here is insufficient memory or the number of configured sessions exceeds the max imum allowed in the server. Verify that the server has adequate memory. Use sp_c onfigure with option 'user connections' to check the maximum number of user conn ections allowed. Use sys.dm_exec_sessions to check the current number of session s, including user processes. 17303 16 The session with SPID %d was found to be invalid during terminat ion, possibly because of corruption in the session structure. Contact Product Su pport Services. 17308 16 %s: Process %d generated an access violation. SQL Server is term inating this process. 17310 20 A user request from the session with SPID %d generated a fatal e xception. SQL Server is terminating this session. Contact Product Support Servic es with the dump produced in the log directory. 17311 16 SQL Server is terminating because of fatal exception %lx. This e rror may be caused by an unhandled Win32 or C++ exception, or by an access viola tion encountered during exception handling. Check the SQL error log for any rela ted stack dumps or messages. This exception forces SQL Server to shutdown. To re cover from this error, restart the server (unless SQLAgent is configured to auto restart). 17312 16 SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d). 17313 10 Unable to locate driver ntdll.dll in path. SQL Server native HTT P support is not available. Error: 0x%lx Your operating system may not support t his driver. 17401 10 Server resumed execution after being idle %d seconds: user activ ity awakened the server. This is an informational message only. No user action i s required. 17403 10 Server resumed execution after being idle %d seconds. Reason: ti mer event. 17404 10 The server resumed execution after being idle for %d seconds. 17405 24 An image corruption/hotpatch detected while reporting exceptiona l situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG. log for details. 17406 10 Server resumed execution after being idle %d seconds. Reason: re source pressure. 17407 10 SQL Server has initialized support for the advanced user mode sc heduling. This is an informational message; no user action is required. 17550 10 DBCC TRACEON %d, server process ID (SPID) %d. This is an informa tional message only; no user action is required. 17551 10 DBCC TRACEOFF %d, server process ID (SPID) %d. This is an inform ational message only; no user action is required. 17557 16 DBCC DBRECOVER failed for database ID %d. Restore the database f rom a backup. 17558 10 Bypassing recovery for database ID %d. This is an informational message only. No user action is required. 17560 10 DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'. 17561 10 %ls index restored for %ls.%ls. 17572 16 DBCC cannot free DLL '%ls'. SQL Server requires this DLL in orde r to function properly. 17573 10 CHECKDB for database '%ls' finished without errors on %ls (local time). This is an informational message only; no user action is required. 17656 10 Warning ****************** 17657 10 Attempting to change default collation to %s. 17658 10 SQL Server started in single-user mode. This an informational me ssage only. No user action is required. 17659 10 Warning: System table ID %d has been updated directly in databas e ID %d and cache coherence may not have been maintained. SQL Server should be r estarted. 17660 10 Starting without recovery. This is an informational message only . No user action is required.

17661 10 Recovering all databases, but not clearing tempdb. This is an in formational message only. No user action is required. 17663 10 Server name is '%s'. This is an informational message only. No u ser action is required. 17664 10 The NETBIOS name of the local node that is running the server is '%ls'. This is an informational message only. No user action is required. 17674 10 Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d. 17676 10 SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required. 17681 10 Loading default collation %s for this instance of SQL Server. 17750 16 Could not load the DLL %ls, or one of the DLLs it references. Re ason: %ls. 17751 16 Could not find the function %ls in the library %ls. Reason: %ls. 17752 16 SQL Server has insufficient memory to run the extended stored pr ocedure '%ls'. Release server memory resources by closing connections or ending transactions. 17753 16 %.*ls can only be executed in the master database. 17802 20 The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. The connection has been closed. %.*ls 17803 20 There was a memory allocation failure during connection establis hment. Reduce nonessential memory load, or increase system memory. The connectio n has been closed.%.*ls 17805 20 The value in the usertype field of the login record is invalid. The value 0x01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect t o SQL Server.%.*ls 17806 20 SSPI handshake failed with error code 0x%x, state %d while estab lishing a connection with integrated security; the connection has been closed. R eason: %.*ls %.*ls %.*ls 17807 20 Event '%ld', which was received from the client, is not recogniz ed by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent. 17809 20 Could not connect because the maximum number of '%ld' user conne ctions has already been reached. The system administrator can use sp_configure t o increase the maximum value. The connection has been closed.%.*ls 17810 20 Could not connect because the maximum number of '%ld' dedicated administrator connections already exists. Before a new connection can be made, t he existing dedicated administrator connection must be dropped, either by loggin g off or ending the process.%.*ls 17812 10 Dedicated administrator connection has been disconnected. This i s an informational message only. No user action is required. 17813 20 The requested service has been stopped or disabled and is unavai lable at this time. The connection has been closed.%.*ls 17825 18 Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. Review the error log: the entry listed after this error contains the error code from the network library. 17826 18 Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately p receding this one in the error log. 17827 20 There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls 17828 20 The prelogin packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls 17829 20 A network error occurred while establishing a connection; the co nnection has been closed.%.*ls

17830 20 Network error code 0x%x occurred while establishing a connection ; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms , network writes %d ms, network reads %d ms, establishing SSL %d ms, network re ads during SSL %d ms, network writes during SSL %d ms, secure calls during SSL % d ms, enqueued during SSL %d ms, negotiating SSPI %d ms, network reads during S SPI %d ms, network writes during SSPI %d ms, secure calls during SSPI %d ms, en queued during SSPI %d ms, validating login %d ms, including user-defined login p rocessing %d ms.%.*ls 17832 20 The login packet used to open the connection is structurally inv alid; the connection has been closed. Please contact the vendor of the client li brary.%.*ls 17835 20 Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgr ade your client library.%.*ls 17836 20 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.%.*ls 17881 16 '%ls' is an unsupported Open Data Services API. 17883 10 Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yieldi ng on Scheduler %ld. Thread creation time: %I64d. Approx Thread CPU Used: kernel %I64d ms, user %I64d ms. Process Utilization %d%%. System Idle %d%%. Interval: %I64d ms. 17884 10 New queries assigned to process on Node %d have not been picked up by a worker thread in the last %d seconds. Blocking or long-running queries c an contribute to this condition, and may degrade client response time. Use the " max worker threads" configuration option to increase number of allowable threads , or optimize current running queries. SQL Process Utilization: %d%%. System Idl e: %d%%. 17885 16 An unexpected query string was passed to a Web Service Descripti on Language (WSDL) generation procedure. 17886 20 The server will drop the connection, because the client driver h as sent multiple requests while the session is in single-user mode. This error o ccurs when a client sends a request to reset the connection while there are batc hes still running in the session, or when the client sends a request while the s ession is resetting a connection. Please contact the client driver vendor. 17887 10 IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yie lding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I 64d. 17888 10 All schedulers on Node %d appear deadlocked due to a large numbe r of worker threads waiting on %ls. Process Utilization %d%%. 17889 16 A new connection was rejected because the maximum number of conn ections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls 17890 10 A significant part of sql server process memory has been paged o ut. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%. 17891 10 Resource Monitor (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Memory freed: %I64d KB. Last wait: %ls. Approx CPU Used: kernel %I6 4d ms, user %I64d ms, Interval: %I64d. 17892 20 Logon failed for login '%.*ls' due to trigger execution.%.*ls 17894 10 Dispatcher (0x%lx) from dispatcher pool '%.*ls' Worker 0x%p appe ars to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d. 17895 10 sp_server_diagnostics running on Worker 0x%p appears to be non-y ielding on Node %ld. 18002 20 Exception happened when running extended stored procedure '%.*ls ' in the library '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. 18052 16 Error: %d, Severity: %d, State: %d.

18053 16 Error: %d, Severity: %d, State: %d. (Params:%ls). The error is p rinted in terse mode because there was error during formatting. Tracing, ETW, no tifications etc are skipped. 18054 16 Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. 18055 20 Exception %d, %d occurred when the server tried to reset connect ion %d. Because the server cannot recover from the failure to reset the connecti on, the connection has been dropped. Please contact Microsoft technical support. 18056 20 The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have be en caused by an earlier operation failing. Check the error logs for failed opera tions immediately before this error message. 18057 20 Error: Failed to set up execution context. 18058 17 Failed to load format string for error %d, language id %d. Opera ting system error: %s. Check that the resource file matches SQL Server executabl e, and resource file in localized directory matches the file under English direc tory. Also check memory usage. 18059 16 The connection has been dropped because the principal that opene d it subsequently assumed a new security context, and then tried to reset the co nnection under its impersonated security context. This scenario is not supported . See "Impersonation Overview" in Books Online. 18060 16 Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the messa ge. 18061 20 The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations i mmediately before this error message. 18100 10 Process ID %d was killed by hostname %.*ls, host process ID %d. 18113 10 SQL Server shutdown after verifying system indexes. 18124 10 The default collation was successfully changed. 18125 10 Engine didn't find configuration for error detection, default co nfiguration was applied. 18126 10 Engine failed to load configuration for error detection, default configuration was applied. 18127 10 Engine takes DB offline in cloud DB mode due to %d, %d. 18204 16 %s: Backup device '%s' failed to %s. Operating system error %s. 18210 16 %s: %s failure on backup device '%s'. Operating system error %s. 18225 10 Tape '%s' (family ID %d, sequence %d, media_set_guid %s) is moun ted on tape drive '%s'. This is an informational message only. No user action re quired 18226 10 Tape mount is being requested on drive '%s'. Expected volume has (Family ID %d, sequence %d). 18227 10 Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is m ounted on tape drive '%s'. This is an informational message only. No user action required. 18228 10 Tape mount request on drive '%s' is cancelled. This is an inform ational message only. No user action is required. 18257 10 %s: Device or media does not support %s. To access this feature, use a different device or media. 18264 10 Database backed up. Database: %s, creation date(time): %s(%s), p ages dumped: %I64d, first LSN: %s, last LSN: %s, number of dump devices: %d, dev ice information: (%s). This is an informational message only. No user action is required. 18265 10 Log was backed up. Database: %s, creation date(time): %s(%s), fi rst LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 18266 10 Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device

information: (%s). This is an informational message only. No user action is req uired. 18267 10 Database was restored: Database: %s, creation date(time): %s(%s) , first LSN: %s, last LSN: %s, number of dump devices: %d, device information: ( %s). Informational message. No user action required. 18268 10 Log was restored. Database: %s, creation date(time): %s(%s), fir st LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 18269 10 Database file was restored. Database: %s, creation date(time): % s(%s), file list: (%s), number of dump devices: %d, device information: (%s). Th is is an informational message. No user action is required. 18270 10 Database differential changes were backed up. Database: %s, crea tion date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, full backup LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 18271 10 Database changes were restored. Database: %s, creation date(time ): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device infor mation: (%s). This is an informational message. No user action is required. 18272 16 During restore restart, an I/O error occurred on checkpoint file '%s' (operating system error %s). The statement is proceeding but cannot be res tarted. Ensure that a valid storage location exists for the checkpoint file. 18273 16 Could not clear '%s' bitmap in database '%s' because of error %d . As a result, the differential or bulk-logged bitmap overstates the amount of c hange that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backu p sets to be larger than necessary. Typically, the cause of this error is insuff icient resources. Investigate the failure and resolve the cause. If the error oc curred on a data backup, consider taking a data backup to create a new base for future differential backups. 18274 10 Tape '%s' was dismounted from drive '%s'. This is an information al message. No user action is required. 18275 10 Unnamed tape was dismounted from drive '%s'. This is an informat ional message. No user action is required. 18276 10 Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of du mp devices: %d, device information: (%s). This is an informational message only. No user action is required. 18277 10 Database file changes were restored. Database: %s, creation date (time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 18279 16 During a RESTORE operation, an I/O error occurred on checkpoint file '%s' (operating system error %s). Ensure that a valid storage location exi sts for the checkpoint file and try the operation again. 18300 10 Reason: Infrastructure error occurred. Check for previous error s. 18301 10 Reason: Could not find a login matching the name provided. 18302 10 Reason: Failed to unprotect memory containing sensitive informa tion. 18303 10 Reason: Failed to unprotect memory containing sensitive informa tion. 18304 10 Reason: Could not find a login matching the name provided. 18305 10 Reason: Attempting to use an NT account name with SQL Server Au thentication. 18306 10 Reason: An error occurred while evaluating the password. 18307 10 Reason: Password did not match that for the login provided. 18308 10 Reason: Invalid password provided. 18309 10 Reason: Password validation failed with an infrastructure error . Check for previous errors. 18310 10 Reason: Token-based server access validation failed with an inf rastructure error. Check for previous errors.

18311 10 Reason: Login-based server access validation failed with an inf rastructure error. Check for previous errors. 18312 10 Reason: SQL Server service is paused. No new connections can be accepted at this time. 18313 10 Reason: Interface for login to SQL Server is not supported. 18314 10 Reason: Failed to open the specified database. 18315 10 Reason: Failed to open the database for this login. 18316 10 Reason: Unable to determine the initial language and date forma t. 18317 10 Reason: The user must change the password, but it cannot be cha nged with the current connection settings. 18318 10 Reason: Failed to unprotect memory containing sensitive informa tion. 18319 10 Reason: Simulation of a failure while redoing login on the conn ection. 18320 10 Reason: SQL Server service is paused. Login could not be revali dated at this time. 18321 10 Reason: Reinitialization of security context failed while reval idating the login on the connection. 18322 10 Reason: Access to server validation failed while revalidating t he login on the connection. 18323 10 Reason: Failed to open the specified database while revalidatin g the login on the connection. 18324 10 Reason: Failed to create the user instance while revalidating t he login on the connection. 18325 10 Reason: Failed to attach the specified database while revalidat ing the login on the connection. 18326 10 Reason: Failed to open the database for this login while revali dating the login on the connection. 18327 10 Reason: Failed to determine the language and date format while revalidating the login on the connection. 18328 10 Reason: An exception was raised while revalidating the login on the connection. Check for previous errors. 18329 10 Reason: Simulation of a failure while reauthenticating login. 18330 10 Reason: SQL Server service is paused. Login cannot be reauthent icated at this time. 18331 10 Reason: Failed to reinitialize security context while reauthent icating login. 18332 10 Reason: Failed to access server for validation while reauthenti cating login. 18333 10 Reason: Failed to open the specified database while reauthentic ating login. 18334 10 Reason: An error occurred while reauthenticating login. Check f or previous errors. 18335 10 Reason: Could not retrieve database name or map database to an item. 18336 10 Reason: Cannot connect with a login that does not specify a sha re. 18337 10 Reason: Failed to open the explicitly specified database '%.*ls '. 18338 10 Reason: Unable to determine the database name from the specifie d file name. 18339 10 Reason: Failed to open the database '%.*ls' specified in the lo gin properties. 18340 10 Reason: Failed to store database name and collation. Check for previous errors. 18341 10 . Reason: Current collation did not match the database's collati on during connection reset. 18342 10 Reason: Failed to send an environment change notification to a log shipping partner node.

18343 10 Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection. 18344 10 Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection. 18345 10 Reason: Failed to open the database '%.*ls' configured in the l ogin object while revalidating the login on the connection. 18346 10 Reason: Failed to determine database name from a given file nam e while revalidating the login on the connection. 18347 10 Reason: Failed to open the database '%.*ls' specified in the lo gin properties while revalidating the login on the connection. 18348 10 Reason: Failed to store database name and collation while reval idating the login on the connection. Check for previous errors. 18349 10 Reason: Current collation did not match the database's collatio n during connection reset. 18350 10 Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. 18351 10 Reason: Client impersonation failed. 18352 10 Reason: Failed to revert impersonation to self. 18353 10 Reason: Failed to get security token information. 18354 10 Reason: Failed to duplicate of security token. 18355 10 Reason: Failed attempted retry of a process token validation. 18356 10 Reason: An error occurred while attempting to change password. 18357 10 Reason: An attempt to login using SQL authentication failed. Se rver is configured for Windows authentication only. 18358 10 Reason: Could not find a user matching the name provided. [Data base: '%.*ls'] 18359 10 Reason: Failed to unprotect memory containing sensitive informa tion. [Database: '%.*ls'] 18360 10 Reason: Failed to unprotect memory containing sensitive informa tion. [Database: '%.*ls'] 18361 10 Reason: Could not find a user matching the name provided. [Data base: '%.*ls'] 18362 10 Reason: Attempting to use an invalid user type with SQL Server Authentication. [Database: '%.*ls'] 18363 10 Reason: An error occurred while evaluating the password. [Datab ase: '%.*ls'] 18364 10 Reason: Password did not match that for the user provided. [Dat abase: '%.*ls'] 18365 10 Reason: Invalid password provided. [Database: '%.*ls'] 18366 10 Reason: Password validation failed with an infrastructure error . Check for previous errors. [Database: '%.*ls'] 18367 10 Reason: Token-based server access validation failed with an inf rastructure error. Check for previous errors. [Database: '%.*ls'] 18368 10 Reason: Login-based server access validation failed with an inf rastructure error. Check for previous errors. [Database: '%.*ls'] 18369 10 attach 18370 10 restore 18371 10 Reason: The password hash is from an unsupported version of SQL Server. Reset the password or recreate the login. 18372 10 Reason: An error occurred while obtaining a routing environment change notification. 18373 10 Reason: Database could not accept user connections at this time. 18400 16 The background checkpoint thread has encountered an unrecoverabl e error. The checkpoint process is terminating so that the thread can clean up i ts resources. This is an informational message only. No user action is required. 18401 14 Login failed for user '%.*ls'. Reason: Server is in script upgra de mode. Only administrator can connect at this time.%.*ls 18451 14 Login failed for user '%.*ls'. Only administrators may connect a t this time.%.*ls 18452 14 Login failed. The login is from an untrusted domain and cannot b

e used with Windows authentication.%.*ls 18453 10 Login succeeded for user '%.*ls'. Connection made using Windows authentication.%.*ls 18454 10 Login succeeded for user '%.*ls'. Connection made using SQL Serv er authentication.%.*ls 18455 10 Login succeeded for user '%.*ls'.%.*ls 18456 14 Login failed for user '%.*ls'.%.*ls%.*ls 18458 14 Login failed. The number of simultaneous users already equals th e %d registered licenses for this server. To increase the maximum number of simu ltaneous users, obtain additional licenses and then register them through the Li censing item in Control Panel.%.*ls 18459 14 Login failed. The workstation licensing limit for SQL Server acc ess has already been reached.%.*ls 18460 14 Login failed. The number of simultaneous users has already reach ed the limit of %d licenses for this '%ls' server. Additional licenses should be obtained and installed or you should upgrade to a full version.%.*ls 18461 14 Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls 18462 14 The login failed for user "%.*ls". The password change failed. T he password for the user is too recent to change. %.*ls 18463 14 The login failed for user "%.*ls". The password change failed. T he password cannot be used at this time. %.*ls 18464 14 Login failed for user '%.*ls'. Reason: Password change failed. T he password does not meet Windows policy requirements because it is too short.%. *ls 18465 14 Login failed for user '%.*ls'. Reason: Password change failed. T he password does not meet Windows policy requirements because it is too long.%.* ls 18466 14 Login failed for user '%.*ls'. Reason: Password change failed. T he password does not meet Windows policy requirements because it is not complex enough.%.*ls 18467 14 The login failed for user "%.*ls". The password change failed. T he password does not meet the requirements of the password filter DLL. %.*ls 18468 14 The login failed for user "%.*ls". The password change failed. A n unexpected error occurred during password validation. %.*ls 18469 10 [CLIENT: %.*hs] 18470 14 Login failed for user '%.*ls'. Reason: The account is disabled.% .*ls 18471 14 The login failed for user "%.*ls". The password change failed. T he user does not have permission to change the password. %.*ls 18482 16 Could not connect to server '%.*ls' because '%.*ls' is not defin ed as a remote server. Verify that you have specified the correct server name. % .*ls. 18483 16 Could not connect to server '%.*ls' because '%.*ls' is not defin ed as a remote login at the server. Verify that you have specified the correct l ogin name. %.*ls. 18485 16 Could not connect to server '%.*ls' because it is not configured to accept remote logins. Use the remote access configuration option to allow re mote logins.%.*ls 18486 14 Login failed for user '%.*ls' because the account is currently l ocked out. The system administrator can unlock it. %.*ls 18487 14 Login failed for user '%.*ls'. Reason: The password of the acco unt has expired.%.*ls 18488 14 Login failed for user '%.*ls'. Reason: The password of the acco unt must be changed.%.*ls 18489 10 The dedicated administrator connection is in use by "%.*ls" on " %.*ls".%.*ls 18491 16 SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.

18492 16 SQL Server cannot start because the license agreement for this ' %ls' version of SQL Server is invalid. The server is exiting. To proceed, reinst all SQL Server with a valid license. 18493 16 The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls 18494 16 The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls 18495 16 The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls 18496 10 System Manufacturer: '%ls', System Model: '%ls'. 18596 16 %.*ls cannot start because your system is low on memory. 18597 16 Your %.*ls installation is either corrupt or has been tampered w ith (%hs). Please uninstall then re-run setup to correct this problem 18598 16 %.*ls could not find the default instance (%.*ls) - error %d. Pl ease specify the name of an existing instance on the invocation of sqlservr.exe. \n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem. 18599 16 %.*ls could not find the specified named instance (%.*ls) - erro r %d. Please specify the name of an existing instance on the invocation of sqlse rvr.exe.\n\nIf you believe that your installation is corrupt or has been tampere d with, uninstall then re-run setup to correct this problem. 18750 16 %ls: The parameter '%ls' is not valid. 18751 16 %ls procedure was called with the wrong number of parameters. 18752 16 Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you e xecuted a log-related procedure, drop the connection over which the procedure wa s executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure. 18755 16 Could not allocate memory for replication. Verify that SQL Serve r has sufficient memory for all operations. 18756 16 Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent. 18757 16 Unable to execute procedure. The database is not published. Exec ute the procedure in a database that is published for replication. 18760 16 Invalid %ls statement for article %d. Verify that the stored pro cedures that propagate changes to Subscribers use the appropriate call syntax, a nd then rerun the Log Reader Agent. Use sp_helparticle and sp_changearticle to v iew and change the call syntax. 18761 16 Commit record at {%08lx:%08lx:%04lx} has already been distribute d. 18762 16 Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:% 08lx:%04lx}. Check DBTABLE. 18763 16 Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as ( 0:0:0). 18764 16 Execution of filter stored procedure %d failed. See the SQL Serv er errorlog for more information. 18765 16 The "%s" log sequence number (LSN) that was specified for the re plication log scan is invalid. 18766 16 The replbeginlsn field in the DBTABLE is invalid. 18767 16 The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}. 18768 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occu rs before the current start of replication in the log {%08lx:%08lx:%04lx}. 18769 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is n ot a replicated commit record. 18770 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is n ot present in the transaction log. 18771 16 Invalid storage type %d specified writing variant of type %d. 18772 16 Invalid server data type (%d) specified in repl type lookup. 18773 16 Could not locate text information records for the column "%.*ls"

, ID %d during command construction. 18774 16 The stored procedure %s must be executed within a transaction. 18775 16 The Log Reader Agent encountered an unexpected log record of typ e %u encountered while processing DML operation. 18776 16 An error occurred while waiting on the article cache access even t. 18777 16 %s: Error initializing MSMQ components 18778 16 %s: Error opening Microsoft Message Queue %s 18780 16 You have specified a value for the @dts_package_password paramet er. You must also specify a value for the @dts_package_name parameter. 18781 16 The value specified for the @backupdevicetype parameter is not v alid. The value must be 'logical', 'disk', or 'tape'. 18782 16 Could not locate backup header information for database '%s' in the specified backup device. Specify a backup device that contains a backup of t he Publisher database. 18783 16 The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to u se a shorter path for this Publisher, and then retry the operation. 18784 16 The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation. 18786 16 The specified publication does not allow subscriptions to be ini tialized from a backup. To allow initialization from a backup, use sp_changepubl ication: set 'allow_initialize_from_backup' to 'true'. 18787 16 Snapshot publications cannot use the option to initialize a subs cription from a backup. This option is only supported for transactional publicat ions. 18790 16 Cannot enable the option to initialize a subscription from a bac kup. This is not supported for non-SQL Server Publishers; it is only supported f or transactional publications from SQL Server Publishers. 18795 16 The valid new types of a log based indexed view article are 'ind exed view logbased', 'indexed view logbased manualfilter', 'indexed view logbase d manualview', and 'indexed view logbased manualboth' only. 18796 16 The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only . 18799 16 Only users who are members of the following roles can perform th is operation: sysadmin fixed server role; dbowner or dbcreator fixed database ro le in the current database. 18801 16 Unable to allocate memory for replication schema version node. 18802 16 Cannot insert a new schema change into the systranschemas system table. HRESULT = '0x%x'. If the problem persists, contact Customer Support Serv ices. 18803 16 The topic %.*ls is not a supported help topic. To see the list o f supported topics, execute the stored procedure sp_replhelp N'helptopics'. 18804 16 Peer-to-peer replication has been enabled, and the Log Reader Ag ent was unable to find an Extended-Originator-Record (EOR) for a transaction tha t did not originate at this server. Contact Customer Support Services. 18805 16 The Log-Scan Process failed to construct a replicated command fr om log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication databa se and contact Customer Support Services. 18806 16 Cannot initialize the replication resource. Ensure that SQL Serv er has sufficient memory. If the problem persists, restart SQL Server. 18807 16 Cannot find an object ID for the replication system table '%s'. Verify that the system table exists and is accessible by querying it directly. I f it does exist, stop and restart the Log Reader Agent; if it does not exist, dr op and reconfigure replication. 18808 16 Article information is not valid. Stop the Log Reader Agent, exe cute the stored procedure sp_replflush, and then restart the Log Reader Agent. 18809 16 END_UPDATE log record {%08lx:%08lx:%04lx} encountered without ma

tching BEGIN_UPDATE. 18810 16 Cannot restart the scan on table '%s'. HRESULT = '0x%x'. Stop an d restart the Log Reader Agent. If the problem persists, contact Customer Suppor t Services. 18811 16 Invalid %s log record. 18812 16 Can not lock the database object in article cache. 18815 16 Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services. 18817 16 Text information block not valid. Contact Customer Support Servi ces. 18818 16 Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18819 16 Failed to lock the current log record at log sequence number (LS N) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18821 16 The rowset does not contain any column with offset %d. Back up t he publication database and contact Customer Support Services. 18823 16 Invalid value %d for %s. 18826 16 Failed to delete rows from the systranschemas table. HRESULT = ' 0x%x'. The rows will be deleted the next time replication executes the stored pr ocedure sp_replcmds. 18827 16 The Log Reader Agent scanned to the end of the log before proces sing all transactions in the hash table. %d transactions in the hash table, %d t ransactions processed, end of log LSN {%08lx:%08lx:%04lx}. Back up the publicati on database and contact Customer Support Services. 18828 16 Invalid filter procedure definition. 18829 16 Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18830 16 A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, curr ent BEGIN_UPDATE {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18832 16 The Log Reader Agent scanned to the end of the log while process ing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08l x:%08lx:%04lx}, current LSN {%08lx:%08lx:%04lx}. Back up the publication databas e and contact Customer Support Services. 18834 16 An unexpected Text Information Begin (TIB) log record was encoun tered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlag s 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d). Contact Customer Support S ervices. 18835 16 Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld , newSize %I64d, oldSize %I64d), text collection state %d. Contact product supp ort. 18836 16 %s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %l d, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, o ffset %I64d, oldSize %I64d, newSize %I64d}. 18837 16 Cannot find rowset ID %I64d in the current schema. Stop and rest art the Log Reader Agent. If the problem persists, reinitialize all subscription s to the publication. 18838 16 The Log Reader Agent encountered a NULL command that is not vali d. Restart the agent if it has stopped. If the problem persists, reinitialize al l subscriptions to the publication. 18840 16 Cannot locate database information in the article cache. Stop an d restart SQL Server and the Log Reader Agent. If the problem persists, back up the publication database, and then contact Customer Support Services. 18842 16 Failed to retrieve the oldest active log sequence number (LSN) f rom a commit record. Stop and restart SQL Server and the Log Reader Agent. If th e problem persists, reinitialize all subscriptions to the publication. 18843 16 Failed to allocate or reallocate buffer for replication command, old size %d, new size %d. 18844 16 Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08l

x:%08lx:%04lx}. Reinitialize all subscriptions to the publication. 18845 16 Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication. 18846 16 Possible inconsistent state in the distribution database: dist_b ackup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute "sp_re pldone NULL, NULL, 0, 0, 1", and then execute sp_replflush. Reinitialize all sub scriptions to the publication. 18847 16 Cannot retrieve the peer-to-peer database information. Contact C ustomer Support Services. 18849 16 Failed to evaluate the filter procedure or computed column. Cann ot find the column offset information for column ID %d, rowsetId %I64d. Stop and restart the Log Reader Agent. If the problem persists, back up the publication database and then contact Customer Support Services. 18850 16 Unexpected %s log record encountered, last FILESTREAMInfo node p rocessed : {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, % I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, { %08lx:%08lx:%04lx}} 18851 16 Failed to %s the replication context for TxF: {%I64d, %.*ls, %ld , %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %I64d, %.*ls, {%08lx:%08 lx:%04lx}}. If the problem persists, contact product support. 18852 16 Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%ld'. If the problem persists, contact Customer Support Services . 18853 10 Replication is skipping schema version logging because the systr anschemas table is not present in database '%d'. This is an informational messag e only. No user action is required. 18854 16 One or more subscriptions have been marked inactive. Drop and re -create all subscriptions for this node that are failing with this error. 18855 11 Can not rename the database name because it is published or it i s a distribution database used by replication. 18856 16 Agent '%s' is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details. 18857 16 The subscription to this publication is not active yet. No user action is required. 18896 16 Failed to compare delete and insert log record for column ID %ld with table ID %ld 19030 10 SQL Trace ID %d was started by login "%s". 19031 10 SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'. 19032 10 SQL Trace was stopped due to server shutdown. Trace ID = '%d'. T his is an informational message only; no user action is required. 19033 10 Server started with '-f' option. Auditing will not be started. T his is an informational message only; no user action is required. 19034 21 Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls 19035 16 OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DC OM is properly installed and configured. 19036 10 The OLE DB initialization service failed to load. Reinstall Micr osoft Data Access Components. If the problem persists, contact product support f or the OLEDB provider. 19049 16 File '%.*ls' either does not exist or there was an error opening the file. Error = '%ls'. 19050 16 Trace file name '%.*ls' is invalid. 19051 16 Unknown error occurred in the trace. 19052 16 The active trace must be stopped before modification. 19053 16 The trace event ID is not valid. 19054 16 The trace column ID is not valid. 19055 16 Filters with the same event column ID must be grouped together. 19056 16 The comparison operator in the filter is not valid. 19057 16 The boolean operator in the filter is not valid.

19058 16 The trace status is not valid. 19059 16 Could not find the requested trace. 19060 16 The trace option is not valid. 19061 16 Cannot remove SPID trace column. 19062 16 Could not create a trace file. 19063 16 Not enough memory was available for trace. 19064 16 The requested trace stop time has been already passed. 19065 16 The parameter is not valid. 19066 16 Cannot modify a restricted trace. 19067 16 Cannot create a new trace because the trace file path is found i n the existing traces. 19068 16 The trace file path is not valid or not supported. 19069 16 The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover option is enabled. 19070 16 The default trace cannot be stopped or modified. Use SP_CONFIGUR E to turn it off. 19071 16 Stopping the trace because the current trace file is full and th e rollover option is not specified. 19096 16 Fail to delete an old trace file '%ls'. Error = '%ls'. 19097 10 Windows error occurred while running %s. Error = %s. 19098 16 An error occurred starting the default trace. Cause: %ls Use sp _configure to turn off and then turn on the 'default trace enabled' advanced ser ver configuration option. 19099 16 Trace ID '%d' was stopped because of an error. Cause: %ls. Resta rt the trace after correcting the problem. 19100 10 Initialization succeeded. 19101 10 Initialization failed with an infrastructure error. Check for pr evious errors. 19102 10 Unable to create a node listener object. Check for memory-relate d errors. 19103 10 An error occurred while starting shared memory support. 19104 10 All protocols are disabled. 19105 10 Unable to create a node listener object for a special instance. Check for memory-related errors. 19106 10 Unable to trim spaces in an IP address. Check TCP/IP protocol se ttings. 19107 10 'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings. 19108 10 Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings. 19109 10 Unable to configure MDAC-compatibility TCP/IP port in registry. 19110 10 Unable to initialize the TCP/IP listener. 19111 10 Unable to open TCP/IP protocol configuration key in registry. 19112 10 Unable to retrieve TCP/IP protocol 'Enabled' registry setting. 19113 10 Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting. 19114 10 Unable to open TCP/IP protocol's 'IPAll' configuration key in re gistry. 19115 10 Unable to retrieve registry settings from TCP/IP protocol's 'IPA ll' configuration key. 19116 10 Unable to obtain list size for IP addresses configured for liste ning in registry. 19117 10 Failed to allocate memory for IP addresses configured for listen ing. Check for memory-related errors. 19118 10 Unable to obtain list of IP addresses configured for listening i n registry. 19119 10 Unable to open TCP/IP protocol's registry key for a specific IP address. 19120 10 Unable to retrieve 'Enabled' setting for a specific IP address. 19121 10 Unable to retrieve 'Active' setting for a specific IP address. 19122 10 Unable to retrieve 'IpAddress' value for a specific IP address.

19123 10 'IpAddress' registry value is the wrong type. 19124 10 Unable to retrieve registry settings for a specific IP address. 19125 10 Unable to deallocate structures representing registry key for a specific IP address. 19126 10 Unable to retrieve registry settings for cluster environment. 19127 10 Server is configured to listen on a specific IP address in a clu ster environment. 19128 10 The SQL Server Network Interface cannot check for a duplicate IP address in the SQL Server TCP listening settings. 19129 10 The SQL Server Network Interface found a duplicate IP address in the SQL Server TCP listening settings. Remove the duplicate IP address by usin g SQL Server Configuration Manager. 19130 10 Unable to open SQL Server Network Interface library configuratio n key in registry for Dedicated Administrator Connection settings. 19131 10 Unable to open Dedicated Administrator Connection configuration key in registry. 19132 10 Unable to open TCP/IP configuration key for Dedicated Administra tor Connection in registry. 19133 10 Unable to retrieve dynamic TCP/IP ports registry settings for De dicated Administrator Connection. 19134 10 No or more than one dynamic TCP/IP port is configured for Dedica ted Administrator Connection in registry settings. 19135 10 Error starting Named Pipes support. Check protocol settings. 19137 10 Failed to allocate memory for SSL listening structures. Check fo r memory-related errors. 19138 10 An error occurred while obtaining or using the certificate for S SL. Check settings in Configuration Manager. 19139 10 Unable to add listener endpoints. Check for memory-related error s. 19140 10 Unable to initialize the communication listeners. 19141 10 Unable to retrieve SQL Server Network Interface library settings for a special instance. 19142 10 Unable to retrieve SQL Server Network Interface library settings ; the instance name is too long. 19143 10 Unable to initialize the Shared Memory listener. 19144 10 Unable to initialize the Named Pipes listener. 19145 10 Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. 19147 10 Unable to initialize the HTTP listener. 19148 10 Unable to initialize SSL support. 19149 10 Unable to configure MDAC-compatibility protocol list in registry . 19150 10 Unable to open SQL Server Network Interface library configuratio n key in registry. 19151 10 An error occurred while obtaining the Extended Protection settin g. Check Network Configuration settings in SQL Server Configuration Manager. 19152 10 The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration Manager. 19153 10 An error occurred while obtaining the Accepted SPNs list for Ext ended Protection. Check Network Configuration settings in SQL Server Configurati on Manager. 19154 10 The configured value for the Accepted SPNs list is not valid. Ch eck Network Configuration settings in SQL Server Configuration Manager. 19155 10 TDSSNIClient failed to allocate memory while loading Extended Pr otection configuration settings. Check for memory-related errors. 19156 10 Failed to allocate memory for SSPI listening structures. Check f or memory-related errors. 19157 10 Unable to initialize the SSPI listener. 19158 10 Unable to create connectivity Ring Buffer. Check for memory-rela ted errors.

19200 10 Authentication succeeded. 19201 10 The transport protocol does not provide an authentication contex t, and there is no authentication token in the TDS stream. 19202 10 An error occurred while calling CompleteAuthToken for this secur ity context. The Windows error code indicates the cause of failure. 19203 10 The CompleteAuthToken API is not defined for the current Securit y Support Provider. 19204 10 AcceptSecurityContext failed. The Windows error code indicates t he cause of failure. 19205 10 The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection. 19206 10 The Channel Bindings from this client do not match the establish ed Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider might need to be upgraded to support Extended Protection. Clo sing the connection. 19207 10 The Channel Bindings from this client are missing or do not matc h the established Transport Layer Security (TLS) Channel. The service might be u nder attack, or the data provider or client operating system might need to be up graded to support Extended Protection. Closing the connection. 19208 10 The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection. 19209 10 QueryContextAttributes could not retrieve Service Bindings. The Windows error code indicates the cause of failure. 19210 10 The server Extended Protection level is set to Allowed or Requir ed, and the client did not provide a Service Principal Name (SPN). To connect, t his client must support Extended Protection. You might have to install an operat ing system service pack that allows for Service Binding and Channel Binding. 19211 10 The server Extended Protection level is set to Allowed or Requir ed, and the client did not provide a Service Principal Name (SPN). To connect, t his client must support Extended Protection. You might have to update the SQL Se rver driver on the client. 19212 10 The Service Class element of the received Service Principal Name (SPN) is not valid. 19213 10 The IP Address element of the received Service Principal Name (S PN) is not valid. 19214 10 The Host element of the received Service Principal Name (SPN) is not valid. 19215 10 A memory allocation failed while validating the received Service Principal Name (SPN). 19216 10 QueryContextAttributes succeeded but did not retrieve the receiv ed Service Principal Name (SPN). 19217 10 WSAStringToAddress was unable to convert the IP Address element of the received Service Principal Name (SPN) to an address structure. The Window s error code indicates the cause of failure. 19218 10 Could not wait on an event signaling IO completion for a cryptog raphic handshake. 19219 10 A task to process a cryptographic handshake could not be enqueue d. 19220 10 An attempt to read a buffer from the network failed during a cry ptographic handshake. 19221 10 The connection was closed while attempting to process a read buf fer during a cryptographic handshake. 19222 10 The connection was closed while attempting to process a write bu ffer during a cryptographic handshake. 19223 10 An attempt to write a buffer to the network failed during a cryp tographic handshake. 19224 10 AcquireCredentialsHandle failed. The Windows error code indicate s the cause of the failure.

19225 10 InitializeSecurityContext failed. The Windows error code indicat es the cause of the failure. 19226 10 QueryContextAttributes could not retrieve stream sizes. The Wind ows error code indicates the cause of the failure. 19227 10 An attempt to resize a buffer failed. 19228 10 An unexpected error occurred during a cryptographic handshake. 19229 10 An invalid token was received during a cryptographic handshake. 19230 10 Failed to allocate a packet for a network write during a cryptog raphic handshake. 19231 10 Failed to allocate an object to perform a cryptographic handshak e. 19232 10 Failed to initialize an object to perform a cryptographic handsh ake. 19233 10 A token from a cryptographic handshake was larger than allowed b y SSPI. 19234 10 The connection was closed while waiting for network IO during a cryptographic handshake. 19235 10 An unexpected exception was thrown while processing a cryptograp hic handshake. 19236 10 Negotiated security context is missing an integrity flag. 19238 10 Negotiated security context is missing a confidentiality flag. 19239 10 Negotiated security context has confidentiality flag present. 19240 10 Negotiated security context is missing a sequence detection flag . 19241 10 Negotiated security context is missing a replay detection flag. 19242 10 Global credentials handle required for inbound connections. 19243 10 SSPI structures too large for encryption. 19244 10 SSPI structures too large for signature. 19245 10 Empty output token is returned by SSPI during security context n egotiation. Check for network packet corruption or other networking issues. 19401 16 The READ_ONLY_ROUTING_URL '%.*ls' specified for availability rep lica '%.*ls' is not valid. It does not follow the required format of 'TCP://syst em-address:port'. For information about the correct routing URL format, see the CREATE AVAILABILITY GROUP documentation in SQL Server Books Online. 19402 16 A duplicate availability replica '%.*ls' was specified in the RE AD_ONLY_ROUTING_LIST for availability replica '%.*ls'. Inspect the replica list that you specified in your command, and remove the duplicate replica name or nam es from the list. Then retry the command. 19403 16 The availability replica '%.*ls' specified in the READ_ONLY_ROUT ING_LIST for availability replica '%.*ls' does not exist. Only availability repl icas that belong to the specified availability group '%.*ls' can be added to thi s list. To get the names of availability replicas in a given availability group, select replica_server_name from sys.availability_replicas and name from sys.ava ilability_groups. For more information, see SQL Server Books Online. 19404 16 An availability replica '%.*ls' that is specified in the READ_ON LY_ROUTING_LIST for availability replica '%.*ls' does not have a value set for R EAD_ONLY_ROUTING_URL. Ensure a READ_ONLY_ROUTING_URL is set for each availabilit y replica in the availability group. Specify a valid READ_ONLY_ROUTING_URL for e ach replica that you want to added to the READ_ONLY_ROUTING_LIST. If you are alt ering availability replicas of an existing availability group, you can get the n ames of availability replicas in a given availability group, select replica_serv er_name from sys.availability_replicas and name from sys.availability_groups. Fo r more information, see SQL Server Books Online. 19405 16 Failed to create, join or add replica to availability group '%.* ls', because node '%.*ls' is a possible owner for both replica '%.*ls' and '%.*l s'. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again. 19406 10 The state of the local availability replica in availability grou p '%.*ls' has changed from '%ls' to '%ls'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For mor

e information, see the availability group dashboard, SQL Server error log, Windo ws Server Failover Cluster management console or Windows Server Failover Cluster log. 19407 16 The lease between availability group '%.*ls' and the Windows Ser ver Failover Cluster has expired. A connectivity issue occurred between the inst ance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding avail ability group resource in the Windows Server Failover Cluster. 19450 16 Failed to open a cluster network interface object: '%ls'. The WS FC cluster control API returned error code %d. The WSFC service may not be runni ng or may be inaccessible in its current state. For information about this erro r code, see "System Error Codes" in the Windows Development documentation. 19451 16 '%.*ls' and '%.*ls' belong to the same subnet. Only one IPv4 and /or one IPv6 address from each subnet is allowed. For an advanced configuration, see the Windows Server Failover Clustering (WSFC) administrator to create a cus tomized configuration through the Cluster Manager. 19452 16 The availability group listener (network name) with Windows Serv er Failover Clustering resource ID '%s', DNS name '%s', port %hu failed to start with a permanent error: %u. Verify port numbers, DNS names and other related ne twork configuration, then retry the operation. 19453 16 The availability group listener (network name) with Windows Serv er Failover Clustering resource ID '%s', DNS name '%s', port %hu failed to start with this error: %u. Verify network and cluster configuration and logs. 19454 16 The availability group listener (network name) with Windows Serv er Failover Clustering resource ID '%s', DNS name '%s', port %hu failed to stop with this error: %u. Verify network and cluster configuration and logs. 19455 16 The WSFC cluster does not have a public cluster network with an IPv4 subnet. This is a requirement to create an availability group DHCP listener . Configure a public network for the cluster with an IPv4 subnet, and try to cre ate the listener. 19456 16 None of the IP addresses configured for the availability group l istener can be hosted by the server '%.*ls'. Either configure a public cluster n etwork on which one of the specified IP addresses can be hosted, or add another listener IP address which can be hosted on a public cluster network for this ser ver. 19457 16 The specified IP Address '%.*ls' is not valid in the cluster-all owed IP range. Check with the network administrator to select values that are ap propriate for the cluster-allowed IP range. 19458 16 The WSFC nodes that host the primary and secondary replicas belo ng to different subnets. DHCP across multiple subnets is not supported for avail ability replicas. Use the static IP option to configure the availability group l istener. 19459 16 The listener with DNS name '%.*ls' does not conform to SQL Serve r listener guidelines, and cannot be configured through SQL Server. Reconfigure the listener through the WSFC Cluster Manager. 19460 16 The availability group listener with DNS name '%.*ls' is configu red to use DHCP. For listeners with this configuration, IP addresses cannot be a dded through SQL Server. To add IP addresses to the listener, drop the DHCP list ener and create it again configured to use static IP addresses. 19461 16 The WSFC node that hosts the primary replica belongs to multiple subnets. To use the DHCP option in a multi-subnet environment, supply an IPv4 I P address and subnet mask of the subnet for the listener. 19462 16 Failed to obtain the WSFC node enumeration handle. The error cod e is %d. The WSFC service may not be running or may be inaccessible in its curr ent state, or the specified cluster resource handle is invalid. For information about this error code, see "System Error Codes" in the Windows Development docu mentation. 19463 16 The WSFC cluster network interface control API returned error co de %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the W

indows Development documentation. 19464 16 The WSFC cluster network control API returned an invalid IP addr ess. The WSFC service might have invalid data in its database or it is a not sup ported version. 19465 16 The WSFC management API returned an unrecognizable dependency ex pression: '%.*ls'. The WSFC service might have invalid data in its database or i t is a not supported version. 19466 16 Failed to obtain the WSFC resource dependency expression for clu ster resource with name or ID '%ls' The error code is %d. The WSFC service may n ot be running or may be inaccessible in its current state. For information abou t this error code, see "System Error Codes" in the Windows Development documenta tion. 19467 16 Failed to remove the resource dependency in which resource '%.*l s' is depending on resource '%.*ls' in the WSFC cluster. The error code is %d. T he WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, s ee "System Error Codes" in the Windows Development documentation. 19468 16 The listener with DNS name '%.*ls' for the availability group '% .*ls' is already listening on the TCP port %u. Please choose a different TCP por t for the listener. If there is a problem with the listener, try restarting the listener to correct the problem. 19469 16 The specified listener with DNS name, '%.*ls', does not exist fo r the Availability Group '%.*ls'. Use an existing listener, or create a new list ener. 19470 16 Failed to delete a resource in the WSFC cluster because the reso urce '%.*ls' is not offline. Delete the resource using the Failover Cluster Mana gement tool (cluadmin.msc). 19471 16 The WSFC cluster could not bring the Network Name resource with DNS name '%ls' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information. 19472 16 Failed to delete the WSFC cluster resource '%.*ls'. The error co de is %d. The WSFC service may not be running or may be inaccessible in its curr ent state, or the specified arguments are invalid. For information about this er ror code, see "System Error Codes" in the Windows Development documentation. 19473 16 Failed to add a resource dependency, making resource '%.*ls' dep end on resource '%.*ls', in the WSFC cluster. The error code is %d. The WSFC ser vice may not be running or may be inaccessible in its current state, or the spec ified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 19474 16 Failed to set the resource dependency expression '%ls' for the W SFC resource '%.*ls'. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are inva lid. For information about this error code, see "System Error Codes" in the Wind ows Development documentation. 19475 16 Cannot take the WSFC resource with ID '%.*ls' offline. The error code is %d. The WSFC service may not be running or may be inaccessible in its c urrent state. For information about this error code, see "System Error Codes" i n the Windows Development documentation. 19476 16 The attempt to create the network name and IP address for the li stener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may b e incorrect. Check the state of the WSFC cluster and validate the network name a nd IP address with the network administrator. 19477 16 The availability group '%.*ls' already has a listener with DNS n ame '%.*ls'. Availability groups can have only one listener. Use the existing l istener, or drop the existing listener and create a new one. 19478 16 Failed to find a multi-string property (property name '%ls') of the WSFC resource with name or ID '%.*ls'. The system error code is %d. The WSF

C service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "Sy stem Error Codes" in the Windows Development documentation. 19479 16 The WSFC cluster network control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. F or information about this error code, see "System Error Codes" in the Windows De velopment documentation. 19480 16 Failed to open a cluster network object: '%ls'. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, se e "System Error Codes" in the Windows Development documentation. 19481 16 Failed to obtain the WSFC resource state for cluster resource wi th name or ID '%.*ls'. The WSFC resource state API returned error code %d. The W SFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Deve lopment documentation. 19482 16 The port number, %u, that is specified is invalid. Valid port nu mbers range from 1 to 65535, inclusive. Select a port number in this range. If a port number is not provided, the default number 1433 is used. 19483 16 The format for the IP address, '%.*ls', is invalid. Please use a valid value for the IP address. 19484 16 The specified IP Address, '%.*ls', is duplicated in the IP addre ss list. Each IP address included in the listener configuration must be unique. Change the statement to remove or replace the duplicated values. 19485 16 The specified DNS name, '%.*ls', is invalid. The length of the D NS name needs to be between 1 and 63 characters, inclusive. Change the value of the DNS name to meet this requirement. 19486 16 The configuration changes to the availability group listener wer e completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port [%.*ls:%d]. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For informati on about altering an availability group listener, see the "ALTER AVAILABILITY GR OUP (Transact-SQL)" topic in SQL Server Books Online. 19487 16 Listener configuration changes were completed but listening stat us of the corresponding TCP provider could not be determined because of the erro r code: %u. Check the system error log to determine if the TCP provider is liste ning or a listener restart is needed. 19488 16 The attempt to create the network name and IP address for the li stener failed, and the attempt to roll back the resources for the Network Name a nd IP Address resources has also failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and v alidate the network name and IP address with the network administrator. Ensure t hat no Network Name or IP Address resource from this operation still exists in t he cluster. 19489 16 The attempt to create FILESTREAM RsFx endpoint failed with HRESU LT 0x%x. 19490 16 The attempt to delete FILESTREAM RsFx endpoint failed with HRESU LT 0x%x. 20001 10 There is no nickname for article '%s' in publication '%s'. 20002 10 The filter '%s' already exists for article '%s' in publication ' %s'. 20003 10 Could not generate nickname for '%s'. 20004 10 Publication '%s' has the following property: '%s'. SQL Server su bscribers below version '%s' will ignore this setting. 20005 18 %ls: Cannot convert parameter %ls: Resulting colv would have too many entries. 20006 16 Cannot make the change because the article might be in a publica tion that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 to acknowledge that such a subscription will be reinitialized.

20007 16 The system tables for merge replication could not be dropped suc cessfully. 20008 16 The system tables for merge replication could not be created suc cessfully. 20009 16 The article '%s' could not be added to the publication '%s'. 20010 16 The Snapshot Agent corresponding to the publication '%s' could n ot be dropped. 20011 16 Cannot set incompatible publication properties. The 'allow_anony mous' property of a publication depends on the 'immediate_sync' property. 20012 16 The subscription type '%s' is not allowed on publication '%s'. 20013 16 The publication property '%s' cannot be changed when there are s ubscriptions on it. 20014 16 Invalid @schema_option value. 20015 16 Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. 20016 16 Invalid @subscription_type value. Valid values are 'pull' or 'an onymous'. 20017 16 The subscription on the Subscriber does not exist. 20018 16 The @optional_command_line is too long. Use an agent definition file. 20019 16 Replication database option '%s' cannot be set unless the databa se is a publishing database or a distribution database. 20020 16 The article resolver supplied is either invalid or nonexistent. 20021 16 The subscription could not be found. 20022 16 This article has now settings to disable uploads and compensate_ for_errors=true. However, local and anonymous subscribers will behave as if comp ensate_for_errors=false. 20023 16 Invalid @subscriber_type value. Valid options are 'local', 'glob al', or 'anonymous'. 20024 16 The alt_snapshot_folder cannot be the same as the working direct ory. 20025 16 The publication name must be unique. The specified publication n ame '%s' has already been used. 20026 16 The publication '%s' does not exist. 20027 16 The article '%s' does not exist. 20028 16 The Distributor has not been installed correctly. Could not enab le database for publishing. 20029 16 The Distributor has not been installed correctly. Could not disa ble database for publishing. 20030 16 The article '%s' already exists on another publication with a di fferent column tracking option. 20031 16 Could not delete the row because it does not exist. 20032 16 '%s' is not defined as a Subscriber for '%s'. 20033 16 Invalid publication type. 20034 16 Publication '%s' does not support '%s' subscriptions. 20036 16 The Distributor has not been installed correctly. 20037 16 The article '%s' already exists in another publication with a di fferent article resolver. 20038 16 The article filter could not be added to the article '%s' in the publication '%s'. 20039 16 The article filter could not be dropped from the article '%s' in the publication '%s'. 20040 16 Could not drop the article(s) from the publication '%s'. 20041 16 Transaction rolled back. Could not execute trigger. Retry your t ransaction. 20043 16 Could not change the article '%s' because the publication has al ready been activated. 20044 16 The priority property is invalid for local subscribers. 20045 16 You must supply an article name. 20046 16 The article does not exist.

20047 16 You are not authorized to perform this operation. 20048 16 To modify the priority of a subscription, run sp_changemergesubs cription at the Publisher instead of using sp_changemergepullsubscription at sub scriber. This is for backward compatibility only. 20049 16 The priority value should not be larger than 100.0. 20050 16 The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999. 20051 16 The Subscriber is not registered. 20052 16 The @metatype parameter value must be null, 1, 2, 5, or 6. 20053 16 An article with a different %s value already exists for object ' %s'. 20054 16 Current database is not enabled for publishing. 20055 16 Table '%s' cannot be published for merge replication because it has a timestamp column. 20056 16 Table '%s' cannot be republished. 20057 16 The profile name '%s' already exists for the specified agent typ e. 20058 16 The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribu tion), or 4 (Merge) 20059 16 The @profile_type must be 0 (System) or 1 (Custom) 20060 16 Compatibility level cannot be smaller than 60. 20061 16 The compatibility level of this database must be set to 70 or hi gher to be enabled for merge publishing. 20062 16 Updating columns with the rowguidcol property is not allowed. 20063 16 Table '%s' into which you are trying to insert, update, or delet e data has been marked as read-only. Only the merge process can perform these op erations. 20064 16 Cannot drop profile. Either it is not defined or it is defined a s the default profile. 20065 16 Cannot drop profile because it is in use. 20066 16 Profile not defined. 20067 16 The parameter name '%s' already exists for the specified profile . 20068 16 The article cannot be created on table '%s' because it has more than %d columns. 20069 16 Cannot validate a merge article that uses looping join filters. 20070 16 Cannot update subscription row. 20072 16 Cannot update Subscriber information row. 20073 16 Articles can be added or changed only at the Publisher. 20074 16 Only a table object can be published as a "table" article for me rge replication. 20075 16 The 'status' parameter value must be either 'active' or 'unsynce d'. 20076 16 The @sync_mode parameter value must be 'native' or 'character'. 20077 16 Problem encountered generating replica nickname. 20078 16 The @property parameter value must be one of the following: 'syn c_type', 'priority', 'description', 'subscriber_security_mode', 'subscriber_logi n', 'subscriber_password', 'publisher_security_mode', 'publisher_login', 'publis her_password', 'merge_job_login', or 'merge_job_password'. 20079 16 Invalid @subscription_type parameter value. Valid options are 'p ush', 'pull', or 'both'. 20081 16 Publication property '%s' cannot be NULL. 20084 16 Publication '%s' cannot be subscribed to by Subscriber database '%s'. 20086 16 Publication '%s' does not support the nosync type because it con tains a table that does not have a rowguidcol column. 20087 16 You cannot push an anonymous subscription. 20088 16 Only assign priorities that are greater than or equal to 0 and l ess than 100. 20089 16 Could not get license information correctly.

20090 16 Could not get version information correctly. 20091 16 sp_mergesubscription_cleanup is used to clean up push subscripti ons. Use sp_dropmergepullsubscription to clean up pull or anonymous subscription s. 20092 16 Table '%s' into which you are trying to insert, update, or delet e data is currently being upgraded or initialized for merge replication. On the publisher data modifications are disallowed until the upgrade completes and snap shot has successfully run. On subscriber data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher. 20093 16 Merge replication upgrade is not complete until the snapshot age nt is run for the publisher and the merge agent run for all the subscribers. 20100 16 Cannot drop Subscriber '%s'. There are existing subscriptions. 20500 16 The updatable Subscriber stored procedure '%s' does not exist. 20501 16 Could not insert into sysarticleupdates using sp_articlecolumn. 20502 16 Invalid '%s' value. Valid values are 'read only', 'sync tran', ' queued tran', or 'failover'. 20503 16 Invalid '%s' value in '%s'. The publication is not enabled for ' %s' updatable subscriptions. 20504 16 Immediate Updating Subscriptions: The xml values inserted/update d by Subscriber will be replicated as NULL to publisher. 20505 16 Could not drop synchronous update stored procedure '%s' in '%s'. 20506 16 Source table '%s' not found in '%s'. 20507 16 Table '%s' not found in '%s'. 20508 11 Updatable subscriptions: The text, ntext, or image values insert ed at the Subscriber will be NULL. 20509 16 Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber. 20510 16 Updateable Subscriptions: Cannot update identity columns. 20511 16 Updateable Subscriptions: Cannot update timestamp columns. 20512 16 Updateable Subscriptions: Rolling back transaction. 20513 16 Database '%s' does not contain any replication metadata for a ro w whose ROWGUIDCOL matches the value specified for the @rowguid parameter of sp_ showrowreplicainfo. Verify that the value specified for @rowguid parameter is co rrect. 20514 10 A rowcount validation request has been submitted to heterogeneou s publisher %s for article %s of publication %s. Validation results will be pos ted to distribution history. 20515 16 Updateable Subscriptions: Rows do not match between Publisher an d Subscriber. Run the Distribution Agent to refresh rows at the Subscriber. 20516 16 Updateable Subscriptions: Replicated data is not updatable. 20518 16 Updateable Subscriptions: INSERT and DELETE operations are not s upported unless published table has a timestamp column. 20519 16 Updateable Subscriptions: INSERT operations on tables with ident ity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. 20520 16 Updateable Subscriptions: UPDATE operations on tables with ident ity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. 20521 16 sp_MSmark_proc_norepl: must be a member of the db_owner or sysad min roles. 20522 16 sp_MSmark_proc_norepl: invalid object name '%s'. 20523 16 Could not validate the article '%s'. It is not activated. 20524 10 Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast). 20525 10 Table '%s' might be out of synchronization. Rowcounts (actual: % s, expected %s). Checksum values (actual: %s, expected: %s). 20526 10 Table '%s' passed rowcount (%s) validation. Rowcount method %d u sed (0 = Full, 1 = Fast). 20527 10 Table '%s' passed rowcount (%s) and checksum validation. Checksu

m is not compared for any text or image columns. 20528 10 Log Reader Agent startup message. 20529 10 Starting agent. 20530 10 Run agent. 20531 10 Detect nonlogged agent shutdown. 20532 10 Replication agent schedule. 20533 10 Replication agents checkup 20534 10 Detects replication agents that are not logging history actively . 20535 10 Removes replication agent history from the distribution database . 20536 10 Replication: agent failure 20537 10 Replication: agent retry 20538 10 Replication: expired subscription dropped 20539 10 Replication Warning: %s (Threshold: %s) 20540 10 Replication: agent success 20541 10 Removes replicated transactions from the distribution database. 20542 10 Detects and removes expired subscriptions from published databas es. 20543 10 @rowcount_only parameter must be the value 0,1, or 2. 0=7.0 comp atible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in version 8.0. 20545 10 Default agent profile 20546 10 Verbose history agent profile. 20547 10 Agent profile for detailed history logging. 20548 10 Slow link agent profile. 20549 10 Agent profile for low bandwidth connections. 20550 10 Windows Synchronization Manager profile 20551 10 Profile used by the Windows Synchronization Manager. 20552 10 Could not clean up the distribution transaction tables. 20553 10 Could not clean up the distribution history tables. 20554 10 The replication agent has not logged a progress message in %ld m inutes. This might indicate an unresponsive agent or high system activity. Verif y that records are being replicated to the destination and that connections to t he Subscriber, Publisher, and Distributor are still active. 20555 10 6.x publication. 20556 10 Heartbeats detected for all running replication agents. 20557 10 Agent shutdown. For more information, see the SQL Server Agent j ob history for job '%s'. 20558 10 Table '%s' passed full rowcount validation after failing the fas t check. DBCC UPDATEUSAGE will be initiated automatically. 20559 10 Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used. 20560 10 An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested. 20561 10 Generated expected rowcount value of %s for %s. 20565 10 Replication: Subscriber has failed data validation 20566 10 Replication: Subscriber has passed data validation 20567 10 Agent history clean up: %s 20568 10 Distribution clean up: %s 20569 10 Expired subscription clean up 20570 10 Reinitialize subscriptions having data validation failures 20571 10 Reinitializes all subscriptions that have data validation failur es. 20572 10 Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure. 20573 10 Replication: Subscription reinitialized after validation failure 20574 10 Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation. 20575 10 Subscriber '%s' subscription to article '%s' in publication '%s'

passed data validation. 20576 10 Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure. 20577 10 No entries were found in msdb..sysreplicationalerts. 20578 10 Replication: agent custom shutdown 20579 10 Generated expected rowcount value of %s and expected checksum va lue of %s for %s. 20580 10 Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'. 20581 10 Cannot drop server '%s' because it is used as a Distributor in r eplication. 20582 10 Cannot drop server '%s' because it is used as a Publisher in rep lication. 20583 10 Cannot drop server '%s' because it is used as a Subscriber in re plication. 20584 10 Cannot drop server '%s' because it is used as a Subscriber to re mote Publisher '%s' in replication. 20585 16 Validation Failure. Object '%s' does not exist. 20586 16 (default destination) 20587 16 Invalid '%s' value for stored procedure '%s'. 20588 16 The subscription is not initialized. Run the Distribution Agent first. 20589 10 Agent profile for replicated queued transaction reader. 20590 16 The article property 'status' cannot include bit 64, 'DTS horizo ntal partitions' because the publication does not allow data transformations. 20591 16 Only 'DTS horizontal partitions' and 'no DTS horizontal partitio ns' are valid 'status' values because the publication allows data transformation s. 20592 16 'dts horizontal partitions' and 'no dts horizontal partitions' a re not valid 'status' values because the publication does not allow data transfo rmations. 20593 16 Cannot modify publication '%s'. The sync_method cannot be chang ed to 'native', or 'concurrent' because the publication is enabled for heterogen eous subscribers. 20594 16 A push subscription to the publication exists. Use sp_subscripti on_cleanup to drop defunct push subscriptions. 20595 16 Skipping error signaled. 20596 16 Only '%s' or members of db_owner can drop the anonymous agent. 20597 10 Dropped %d anonymous subscription(s). 20598 16 The row was not found at the Subscriber when applying the replic ated command. 20599 16 Continue on data consistency errors. 20600 10 Agent profile for skipping data consistency errors. It can be us ed only by SQL Server Subscribers. 20601 10 Invalid value specified for agent parameter 'SkipErrors'. 20602 10 The value specified for agent parameter 'SkipErrors' is too long . 20603 10 The agent profile cannot be used by heterogeneous Subscribers. 20604 10 You do not have permissions to run agents for push subscriptions . Make sure that you specify the agent parameter 'SubscriptionType'. 20605 10 Invalidated the existing snapshot of the publication. Run the Sn apshot Agent again to generate a new snapshot. 20606 10 Reinitialized subscription(s). 20607 10 Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the exist ing snapshot. 20608 10 Cannot make the change because there are active subscriptions. S et @force_reinit_subscription to 1 to force the change and reinitialize the acti ve subscriptions. 20609 16 Cannot attach subscription file '%s'. Make sure that it is a val

id subscription copy file. 20610 16 Cannot run '%s' when the Log Reader Agent is replicating the dat abase. 20611 16 Cannot add the article. Publications that allow transformable su bscriptions with Data Transformation Services (DTS) can only include tables and indexed views that are published as tables. 20612 16 Checksum validation is not supported because the publication all ows DTS. Use row count only validation. 20613 16 Validation is not supported for articles that are set up for DTS horizontal partitions. 20614 16 Validation is not supported for heterogeneous Subscribers. 20615 16 Unable to add a heterogeneous subscription to the publication. The publication is not enabled for heterogeneous subscriptions. 20616 10 High Volume Server-to-Server Profile 20617 10 Merge agent profile optimized for the high volume server-to-serv er synchronization scenario. 20618 16 You must have CREATE DATABASE permission to attach a subscriptio n database. 20619 16 Server user '%s' is not a valid user in database '%s'. Add the u ser account or 'guest' user account into the database first. 20620 11 The security mode specified requires the server '%s' to be regis tered as a linked server. Use sp_addlinkedserver to add the server. 20621 11 Cannot copy a subscription database to an existing database. 20622 11 Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode. 20623 11 You cannot validate article '%s' unless you have 'SELECT ALL' pe rmission on table '%s'. 20624 16 The value specified for the @login parameter is not valid. User '%s' is not a user in database '%s'. Add the user account to the database before attempting to execute the stored procedures sp_grant_publication_access or sp_r evoke_publication_access. 20625 16 Cannot create the merge replication publication access list (PAL ) database role for publication '%s'. This role is used by replication to contro l access to the publication. Verify that you have sufficient permissions to crea te roles in the publication database. 20626 16 Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter. 20627 16 Partition id has to be greater than or equal to 0. 20628 16 Failed to generate dynamic snapshot. 20629 16 Failed to get partition id information. 20630 16 Cannot create partitioned snapshot job. A job already exists for publication '%ls' that uses the values you specified for the @suser_sname and/o r @host_name parameters of sp_adddynamicsnapshot_job. If the job that already ex ists is not working correctly, use sp_dropdynamicsnapshot_job to drop it and cre ate a new one using sp_adddynamicsnapshot_job. 20631 16 Cannot find a location in which to generate a partitioned snapsh ot. Verify that the there is a valid snapshot folder specified for the publicati on. This can be the default folder associated with the Distributor or an alterna te folder associated with the publication. 20632 16 Failed to create a dynamic snapshot job to generate the dynamic snapshot. 20633 16 Cannot start the partitioned snapshot job. Verify that SQL Serve r Agent is running on the Distributor. 20634 16 The root publication information could not be found on the repub lisher. 20635 16 A push subscription to '%ls' was found. Cannot add a pull subscr iption agent for a push subscription. 20636 16 Cannot generate merge replication stored procedures for article '%s'. Stored procedures are generated on the Publisher when the Snapshot Agent r uns or when a data definition language action is performed; they are generated o

n the Subscriber when the snapshot is applied by the Merge Agent. Verify that th e agents have the appropriate permissions to create procedures, and that the pro cedures do not already exist. 20637 10 The article order specified in the @processing_order parameter o f sp_addmergearticle does not reflect the primary key-foreign key relationships between published tables. Article '%s' references one or more articles that will be created after it is created. Change the processing_order property using sp_c hangemergearticle. 20638 10 Merge table articles do not support different values for the @so urce_object and @destination_object parameters of sp_addmergearticle. Either do not specify a value for @destination_object, or specify the same value for both parameters. 20639 16 Cannot enable the publication to support non-SQL Server subscrip tions because the publication is enabled for updatable subscriptions. To support non-SQL Server subscriptions, drop the existing publication and create a new on e with the properties allow_sync_tran and allow_queued_tran set to 'false'. 20640 16 Cannot change enabled for heterogeneous subscriptions property w hile there are subscriptions to the publication. 20641 16 Failed to check if the subset_filterclause has a dynamic functio n in it. 20642 16 Cannot add article '%s' with one or more dynamic functions in th e subset_filterclause '%s' to publication '%s' because the publication could hav e active subscriptions. Set @force_reinit_subscription to 1 to add the article a nd reinitialize all active subscriptions. 20643 16 Cannot change the value of validate_subscriber_info for publicat ion '%s' because the publication has active subscriptions. Set @force_reinit_sub scription to 1 to change the value and reinitialize all active subscriptions. 20644 16 Invalid value "%s" specified for the parameter @identityrangeman gementoption. Valid values are "auto", "manual", or "none". 20645 16 The property "%s" cannot be modified for publications that are e nabled for non-SQL Server subscriptions. 20646 16 Peer-to-peer publications do not support %s. Change the value fo r parameter '%s'. 20647 16 Cannot modify property '%s'. The publication is used in a peer-t o-peer topology, which does not allow this property to be modified after the pub lication is created. 20648 16 An article already exists for table "%s" with a different value for the @delete_tracking property. The value must be the same for all publicatio ns in which the table is published. Use the stored procedures sp_helpmergearticl e and sp_changemergearticle to view and modify the property in the other article (s). 20649 16 Publications enabled for heterogeneous subscriptions do not supp ort %s. Please change the '%s' parameter value. 20650 16 Cannot enable data definition language (DDL) replication (a valu e of "true" for the @replicate_ddl parameter) for publication "%s". This is beca use the compatibility level of the publication is lower than 90RTM. For new publ ications, in the stored procedure sp_addmergepublication, set the @publication_c ompatibility_level parameter to 90RTM; for existing publications, use sp_changem ergepublication. 20651 16 Publication "%s" "%s". Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower , disable the feature and then call the stored procedure sp_changemergepublicati on to lower the compatibility level. 20652 16 Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again. 20653 16 Cannot have a dynamic snapshot job with both dynamic_filter_logi n and dynamic_filter_hostname being NULL. 20654 16 Dynamic snapshots are only valid for merge publications. 20655 16 The partitioned snapshot process cannot complete. Cannot retriev e the maximum timestamp information from the MSsnapshot_history table in the dis

tribution database. Ensure that a standard snapshot is up-to-date and available. 20656 16 The @subset_filterclause parameter cannot reference a computed c olumn. 20657 16 The value for the @pub_identity_range parameter must be a multip le of the increment for the identity column. The increment for table "%s" and id entity column "%s" is %s. 20658 16 The value for the @identity_range parameter must be a multiple o f the increment for the identity column. The increment for table "%s" and identi ty column "%s" is %s. 20659 11 The value of IDENT_CURRENT ("%s") is greater than the value in t he max_used column of the MSmerge_identity_range system table. 20660 16 The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range. 20661 16 The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range. 20662 16 The republisher does not have a range of identity values from th e root Publisher '%s' that it can assign to its Subscribers. Ensure that the rep ublisher has a server subscription to the publication at the root Publisher, and then run the Merge Agent to synchronize with the root Publisher. 20663 16 The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for t he @identityrangemanagementoption property is "auto". 20664 16 The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have all been used. Chan ge the data type in the identity column. 20665 16 The republisher does not have a range of identity values from th e root Publisher that it can assign to its Subscribers. Run the Merge Agent to s ynchronize with the root Publisher. 20666 16 Cannot refresh the identity range and/or the check constraint on the Publisher. Ensure the following: that the value in the identity column has not reached the maximum for the data type in the identity column; and that the u ser who made the last insert has the privileges to drop and re-create the check constraint. 20667 16 Cannot allocate an identity range for article "%s". The article is not enabled for automatic identity range management. 20668 16 Not enough range available to allocate a new range for a subscri ber. 20669 16 Object referenced by the given @article or @artid '%s' could not be found. 20670 16 Cannot add, drop, or alter the identity range check constraint f or table %s. This constraint is used by replication for automatic identity range management. This error typically occurs if the user who made the last insert in the table does not have permission to make schema changes on the table. If this error occurs at the Publisher, run sp_adjustpublisheridentityrange; if it occur s at the Subscriber, run the Merge Agent. 20671 16 Cannot find the identity range allocation entry for the Subscrib er in the MSmerge_identity_range table. Reinitialize the subscription. 20672 16 A value for the parameter @host_name was specified, but no artic les in the publication use HOST_NAME() for parameterized filtering. 20673 16 A value for the parameter @host_name was specified, but no artic les in the publication use SUSER_SNAME() for parameterized filtering. 20674 16 The publication does not use dynamic filtering. 20675 16 The identity range values cannot be NULL. 20676 11 Cannot refresh the Publisher identity range for article "%s". Ex ecute the stored procedure sp_adjustpublisheridentityrange to refresh the identi ty range. 20677 11 Cannot add article "%s" with automatic identity range management . The article is already published in a transactional publication with automatic identity range management. 20678 11 Could not find the regular snapshot job for the specified public

ation '%s'. 20679 11 Cannot execute the stored procedure sp_adjustpublisheridentityra nge on the current database because the database is a republisher or a Subscribe r. To adjust the identity range at a republisher or a Subscriber, synchronize wi th the root Publisher. 20680 16 Failed to get metadata for a batch of rows. 20681 10 Cannot specify a value of 1, 2, or 3 for the parameter @partitio n_options because publication "%s" has a compatibility level lower than 90RTM. U se the stored procedure sp_changemergepublication to set publication_compatibili ty_level to 90RTM. 20682 10 Failed deletion of rows in batched delete attempt on table %s. 20683 16 Failed batched deletion on download only article %s. 20684 16 Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent. 20685 16 Cannot drop the filter '%s' . The filter specified for the @filt ername parameter cannot be found. 20686 16 Parameter '%s' cannot be NULL or empty when this procedure is ru n from a '%s' database. 20687 16 Parameter '%s' must be NULL when this procedure is not being run from a '%s' database. 20688 16 The tracer token ID (%d) could not be found for Publisher %s, da tabase %s, publication %s. Use the stored procedure sp_helptracertokens to retri eve a list of valid tracer token IDs. 20689 16 The check for a Publisher needing a new identity range allocatio n failed on table %s. This check occurs every time the Merge Agent and Snapshot Agent run. Rerun the Merge Agent or Snapshot Agent. 20690 16 Cannot set up the Publisher identity range for table %s. Verify that appropriate ranges were specified when the article was created, and then re run the Snapshot Agent. 20691 16 Merge replication upgrade of SQL Server 2005 metadata and trigge rs on the subscriber failed. 20692 16 One or more rows to be inserted in the batch insert procedure fo r table %s were present in MSmerge_tombstone; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replic ation. 20693 16 One or more rows to be inserted in the batch insert procedure fo r table %s were present in MSmerge_contents; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No a ction is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replica tion. 20694 16 One or more rows to be updated for table %s contain changes in t he column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this conditio n occurs frequently, verify that data is partitioned optimally. Batch updates ca n improve the performance of merge replication. 20695 16 Only %ld out of %ld rows were updated in the batched update proc edure for table %s; other rows could not be updated because they have been delet ed. No action is required, but if this condition occurs frequently, determine if update-delete conflicts can be avoided. Batch updates can be helpful for perfor mance. 20696 16 The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication. 20697 16 Cannot drop article %s from publication %s. In this publication, this is the only article that uses a parameterized filter. Dropping this articl e changes the publication to a static publication, which requires reinitializati on of all Subscribers. To drop the article and reinitialize all active subscript ions, specify a value of 1 for the @force_reinit_subscription parameter of sp_d

ropmergepublication. 20698 16 A value for the parameter @host_name was not specified while pub lication uses HOST_NAME() for dynamic filtering. 20699 16 A value for the parameter @suser_sname was not specified while p ublication uses SUSER_SNAME() for dynamic filtering. 20701 16 The dynamic snapshot job schedule could not be changed on the di stributor. 20702 16 The dynamic snapshot job schedule could not be changed due to on e or more errors. 20703 16 One or more rows inserted in table '%s' were out of partition wh ile the table was published with 'partition_options' set to %d. 20704 16 The datatype of the identity column of table '%s' is tinyint. ti nyint does not have enough numbers available for merge auto identity range. Chan ge the identity column to have a larger datatype and add the merge article with merge auto identity range management. 20705 10 Cannot set @conflict_logging to 'both' because publication '%s' has a compatibility level lower than 90. Set @publication_compatibility_level to '90RTM' when creating the publication or use sp_changemergepublication to set p ublication_compatibility_level to '90RTM'. 20706 10 The max or min allowed identity numbers for the identity column could not be found for the given article. 20707 10 Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors. 20708 10 An article is not allowed to be part of a logical record when it has a custom business logic resolver. 20709 10 The merge process could not clean up the conflict table "%s" for publication "%s". 20710 16 Incorrect identity range allocation was detected when logging id entity range allocation information on the distributor for publisher '%s', publi sher_db '%s', publication '%s' and article '%s'. 20711 16 The dynamic filters property for publication '%s' has been incor rectly set. Use sp_changemergepublication to reset the value to true if the publ ication uses parameterized filters and false if it does not. 20712 16 Unable to acquire the replication merge administrative applicati on lock for database '%s'. This could be due an active snapshot running while th e schema change (DDL) or the administrative proc change was attempted. 20713 16 Replication merge admin stored procedure '%s' failed for publica tion '%s'. This could be due an active snapshot running while the admin proc was called. 20714 16 Failed to prepare article '%s' in publication '%s' for merge rep lication. 20715 16 Failed to create merge replication triggers for object '%s'. 20716 16 Failed to create publication views for merge replication publica tion '%s'. 20717 16 sp_addmergelogsettings failed to add log settings. If log settin gs already exist for this subscription then use sp_changemergelogsettings to cha nge the settings or sp_dropmergelogsettings to remove the settings. 20718 16 Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. Use sp_addmergelogsettings to add the settings. 20719 16 sp_changemergelogsettings failed to update log settings. Check t he parameter values. 20720 16 Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. 20721 16 sp_dropmergelogsettings failed to remove log settings. 20722 16 '%s' failed. The value for parameter '%s' is not valid. Valid va lues are @support_options [0 - 5], @log_severity [1 - 4], @log_file_size [2,000, 000 - 999,000,000], @no_of_log_files [2 - 500], @upload_interval [0 - 40320], @d elete_after_upload [0 - 1]. 20723 16 Computed column "%s" can only be added to publication after its depending object "%s" is added.

20724 16 Could not find a valid command line for the dynamic snapshot job with job_id '%s' for publication '%s'. 20725 16 Unable to update the dynamic snapshot location for the dynamic s napshot job with job_id '%s' in publication '%s'. 20726 16 Failed to change the dynamic snapshot location in one or more dy namic snapshot jobs for the given publication. 20727 16 An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'. 20728 16 Failed to restore the max allocated identity value for article ' %s' in publication '%s'. 20729 16 The max identity value allocation for article '%s' in publicatio n '%s' could not be found on the distributor. 20730 16 Setting @upload_first to 'true' requires the publication to be a t publication_compatibility_level of '80RTM' or higher. Use sp_changemergepublic ation to set publication_compatibility_level to '80RTM' or higher if you want to use this feature. 20731 16 This edition of SQL Server does not support publications. Droppi ng existing publications. 20732 10 Warning: Values of some of the flags specified in the 'schema_op tion' property are not compatible with the publication's compatibility level. Th e modified schema_option value of '%s' will be used instead. 20733 16 One or more rows updated in table '%s' were out of partition whi le the table was published with 'partition_options' set to %d. 20734 16 One or more rows deleted in table '%s' were out of partition whi le the table was published with 'partition_options' set to %d. 20735 16 Cannot add article '%s' to publication '%s'. The publication alr eady contains 256 articles, which is the maximum. 20736 10 Warning: Values of some of the flags specified in the 'schema_op tion' property are not compatible with the publication's compatibility level. Th e modified schema_option value of '%s' will be used instead. 20737 10 Warning: To allow replication of FILESTREAM data to perform opti mally and reduce memory utilization, the 'stream_blob_columns' property has been set to 'true'. To force FILESTREAM table articles to not use blob streaming, u se sp_changemergearticle to set 'stream_blob_columns' to 'false'. 20738 11 Cannot add article '%s' with sparse column or column set to merg e publication since merge replication does not support sparse columns and column set. 20739 16 The DDL operation is not supported for article '%s'. If the colu mn in the DDL operation is enabled for FILESTREAM or is of type hierarchyid, geo metry, geography, datetime2, date, time, or datetimeoffset, the publication comp atibility level must be at least 100RTM. For DDL operations that involve FILESTR EAM and hierarchyid columns, the snapshot mode must be native. Character mode, w hich is required for SQL Server Compact Subscribers, is not supported. 20800 16 Cannot reinitialize the article '%s' in subscription '%s:%s' to publication '%s'. The publication is enabled for peer-to-peer transactional repl ication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead. 20801 16 Cannot reinitialize the subscription. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead . 20802 16 Cannot publish objects from the replication administrative user schema [%s]. This schema owns all replication procedures and metadata tables, bu t it cannot own published objects. Use a different schema for objects that will be published. 20803 16 Peer-To-Peer topologies require identical articles in publicatio ns at all nodes prior to synchronizing. Articles in publication [%s].[%s].[%s] d o not match articles in [%s].[%s].[%s]. 20804 16 Articles can only be included in a single peer-to-peer publicati on. [%s].[%s] is already included in the peer-to-peer publication '%s'.

20805 16 Peer-to-peer topologies require identical publication names on e ach Publisher. You are attempting to republish object [%s].[%s] that is already being published in the peer-to-peer publication [%s].[%s].[%s]. 20806 16 An error occurred while executing a peer-to-peer forwarding comm and. Contact Customer Support Services. 20807 16 No peers were found for %s:%s:%s. If you encounter this error wh en executing the stored procedure sp_requestpeerresponse, verify that subscripti ons have been created before attempting to call the procedure again. If you enco unter this error in other circumstances, contact Customer Support Services. 20808 16 The peer-to-peer publication '%s' does not exist. Execute sp_hel ppublication to view a list of publication names. 20809 16 Peer-To-Peer topologies require identical publication names on e ach publisher. The distribution agent for publication [%s].[%s].[%s] is attempti ng to synchronize articles that exist in publication [%s].[%s].[%s]. 20810 16 The specified source object must be a user-defined aggregate obj ect if it is published as an 'aggregate schema only' type article. 20811 16 Replication monitoring refresher for %s. 20812 16 The specified source object must be a synonym if it is published as a 'synonym schema only' type article. 20813 16 Only members of the sysadmin fixed server role can modify a %s t hat does not have a job with a proxy account defined. 20814 10 Distribution Profile for OLEDB streaming 20815 10 Distribution agent profile enabled for the processing LOB data u sing OLEDB streaming. 20816 10 Peer-To-Peer publishers are only supported on Enterprise class e ditions of SQL Server. This instance is %s. 20817 16 An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'. 21000 16 Cannot subscribe to an inactive publication. 21001 16 Cannot add a Distribution Agent at the Subscriber for a push sub scription. 21002 16 The Distribution Agent for this subscription already exists (%s) . 21003 16 Changing publication names is no longer supported. 21004 16 Cannot publish the database object '%s' because it is encrypted. 21005 10 For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible. 21006 16 Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpub lisher. 21007 16 Cannot add the remote Distributor. Make sure that the local serv er is configured as a Publisher at the Distributor. 21008 16 Cannot uninstall the Distributor because there are Subscribers d efined. 21009 16 The specified filter procedure is already associated with a tabl e. 21010 16 Removed %ld replicated transactions consisting of %ld statements in %ld seconds (%ld rows/sec). 21011 16 Deactivated subscriptions. 21012 16 Cannot change the 'allow_push' property of the publication to "f alse". There are push subscriptions on the publication. 21013 16 Cannot change the 'allow_pull' property of the publication to "f alse". There are pull subscriptions on the publication. 21014 16 The @optname parameter value must be 'transactional' or 'merge'. 21015 16 The replication option '%s' has been set to TRUE already. 21016 16 The replication option '%s' has been set to FALSE already. 21017 16 Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQL Server 2000 compatible binary checksum operation can be performed on thi s article. 21018 16 There are too many consecutive snapshot transactions in the dist

ribution database. Run the Log Reader Agent again or clean up the distribution database. 21019 10 Distribution agent for subscription added. 21020 10 no comment specified. 21021 16 Drop the Distributor before you uninstall replication. 21022 16 If set 'immediate_sync' property of a publication to true then m ust also set 'independent_agent' property to true. 21023 16 '%s' is no longer supported. 21024 16 The stored procedure '%s' is already published as an incompatibl e type. 21025 16 The string being encrypted cannot have null characters. 21026 16 Cannot have an anonymous subscription on a publication that does not have an independent agent. 21027 16 '%s' replication stored procedures are not installed. You must r einstall SQL Server with Replication. 21028 16 Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication. 21029 16 Cannot drop a push subscription entry at the Subscriber unless @ drop_push is 'true'. 21030 16 Names of SQL Server replication agents cannot be changed. 21031 16 'post_script' is not supported for stored procedure articles. 21032 16 Could not subscribe because non-SQL Server Subscriber '%s' does not support 'sync tran' update mode. 21033 16 Cannot drop server '%s' as Distribution Publisher because there are databases enabled for replication on that server. 21034 16 Rows inserted or updated at the Subscriber cannot be outside the article partition. 21035 16 You have updated the Publisher property '%s' successfully. 21036 16 Another %s agent for the subscription or subscriptions is runnin g, or the server is working on a previous request by the same agent. 21037 16 Invalid working directory '%s'. 21038 16 Windows Authentication is not supported by the server. 21039 16 The article '%s' contains the destination owner '%s'. Non-SQL Se rver Subscribers require articles to have the destination owner of NULL. 21040 16 Publication '%s' does not exist. 21041 16 A remote distribution Publisher is not allowed on this server ve rsion. 21042 16 The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running on Windows NT 4.0. 21043 16 The Distributor is not installed. 21044 16 Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing. 21045 16 Cannot uninstall the Distributor because there are databases ena bled for publishing or merge publishing. 21046 16 Cannot change distribution Publisher property 'distribution_db' because the Publisher is using the current distribution database. 21047 16 Cannot drop the local distribution Publisher because there are S ubscribers defined. 21048 16 Cannot add login '%s' to the publication access list because it does not have access to the distribution server '%s'. 21049 16 The login '%s' does not have access permission on publication '% s' because it is not in the publication access list. 21050 16 Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with suffici ent permissions to perform this operation. 21051 16 Could not subscribe because non-SQL Server Subscriber '%s' does not support custom stored procedures. 21052 16 Cannot write to the message queue for the queued updating subscr iption. Ensure that Microsoft Distributed Transaction Coordinator is running, an d that the subscription is active and initialized. If the subscription uses Micr

osoft Message Queueing, ensure the proper permissions are set on the queue. 21053 16 Input property parameter is not valid. See SQL Server Books Onli ne for a list of valid parameters for sp_changemergepublication. 21054 16 The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers w ith updating subscriptions). Ensure sp_link_publication has been used to configu re the linked server properly, and ensure that the login used to connect to the Publisher is in the publication access list. 21055 15 Invalid value for parameter %s specified for %s. 21056 16 The subscription to publication '%s' has expired or does not exi st. 21057 16 Anonymous Subscribers cannot have updatable subscriptions. 21058 16 An updatable subscription to publication '%s' on Subscriber '%s' already exists. 21059 16 Cannot reinitialize subscriptions of non-immediate_sync publicat ions. 21060 16 Could not subscribe because non-SQL Server Subscriber '%s' does not support parameterized statements. 21061 16 Invalid article status %d specified when adding article '%s'. 21062 16 The row size of table '%s' exceeds the replication limit of 6,00 0 bytes. 21063 16 Table '%s' cannot participate in updatable subscriptions because it is published for merge replication. 21064 16 The subscription is uninitialized or unavailable for immediate u pdating as it is marked for reinitialization. If using queued failover option, r un Queue Reader Agent for subscription initialization. Try again after the (re)i nitialization completes. 21070 16 This subscription does not support automatic reinitialization (s ubscribed with the 'no sync' option). To reinitialize this subscription, you mus t drop and re-create the subscription. 21071 10 Cannot reinitialize article '%s' in subscription '%s:%s' to publ ication '%s' (subscribed with the 'no sync' option). 21072 16 The subscription has not been synchronized within the maximum re tention period or it has been dropped at the Publisher. You must reinitialize th e subscription to receive data. 21073 16 The publication specified does not exist. 21074 16 The subscription(s) have been marked inactive and must be reinit ialized. NoSync subscriptions will need to be dropped and recreated. 21075 10 The initial snapshot for publication '%s' is not yet available. 21076 10 The initial snapshot for article '%s' is not yet available. 21077 10 Deactivated initial snapshot for anonymous publication(s). New s ubscriptions must wait for the next scheduled snapshot. 21078 16 Table '%s' does not exist in the Subscriber database. 21079 16 The RPC security information for the Publisher is missing or inv alid. Use sp_link_publication to specify it. 21080 16 The 'msrepl_tran_version' column must be in the vertical partiti on of the article that is enabled for updatable subscriptions; it cannot be drop ped. 21081 16 Server setting 'Allow triggers to be fired which fire other trig gers (nested triggers)' must exist on updatable Subscribers. 21082 16 Database property 'IsRecursiveTriggersEnabled' has to be false f or subscription databases at Subscribers that allow updatable subscriptions. 21083 16 Database compatibility level at immediate updating Subscribers c annot be less than 70. 21084 16 Publication '%s' does not allow anonymous subscriptions. 21085 16 The retention period must be less than the retention period for the distribution database. 21086 16 The retention period for the distribution database must be great er than the retention period of any existing non-merge publications. 21087 16 Client subscriptions and anonymous subscriptions cannot republis

h data. To republish data from this database, the subscription to the root Publi sher must be a server subscription with a priority greater than 0. Drop the curr ent subscription and create a server subscription. 21088 10 The initial snapshot for the publication is not yet available. 21089 16 Only members of the sysadmin fixed server role can perform this operation. 21090 16 Cannot upgrade merge replication metadata. Attempt the upgrade a gain by running the Merge Agent for the Subscriber or by running the Snapshot Ag ent for the Publisher. 21091 16 Global subscribers with priority 0 are not allowed to create mer ge publications. 21092 10 The Change Tracking manual cleanup procedure for database %s has been executed 21101 10 The custom command name %s specified for parameter %s will be ig nored. A system generated name will be used instead. The publication allows %s a nd command names need not be specified. 21105 16 This edition of SQL Server cannot act as a Publisher or Distribu tor for replication. 21106 16 This edition of SQL Server does not support publications. 21107 16 '%ls' is not a table or view. 21108 16 This edition of SQL Server does not support transactional public ations. 21109 16 The parameters @xact_seqno_start and @xact_seqno_end must be ide ntical if @command_id is specified. 21110 16 @xact_seqno_start and @publisher_database_id must be specified i f @command_id is specified. 21111 16 '%s' is not a valid parameter for the Snapshot Agent. 21112 16 '%s' is not a valid parameter for the Log Reader Agent. 21113 16 '%s' is not a valid parameter for the Distribution Agent. 21114 16 '%s' is not a valid parameter for the Merge Agent. 21115 16 %d is not a valid value for the '%s' parameter. The value must b e a positive integer. 21116 16 '%s' is not a valid value for the '%s' parameter. The value must be 1, 2, or 3. 21117 16 '%s' is not a valid value for the '%s' parameter. The value must be 0, 1, or 2. 21118 16 '%s' is not a valid value for the '%s' parameter. The value must be greater than or equal to 0 and less than or equal to 10,000. 21119 16 %s is not a valid value for the '%s' parameter. The value must b e a non-negative integer. 21120 16 Only members of the sysadmin fixed server role or db_owner fixed database role, or the owner of the subscription can drop subscription '%s' to p ublication '%s'. 21121 16 Only members of the sysadmin fixed server role and '%s' can drop the pull subscription to the publication '%s'. 21122 16 Cannot drop the distribution database '%s' because it is current ly in use. 21123 16 The agent profile '%s' could not be found at the Distributor. 21124 16 Cannot find the table name or the table owner corresponding to t he alternative table ID(nickname) '%d' in sysmergearticles. 21125 16 A table used in merge replication must have at least one non-com puted column. 21126 16 Pull subscriptions cannot be created in the same database as the publication. 21127 16 Only global merge subscriptions can be added to database '%s'. 21128 16 Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure t o set the firing order for trigger '%s' to first. 21129 16 Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure t

o set the firing order for trigger '%s' to first. 21130 16 Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure t o set the firing order for trigger '%s' to first. 21131 16 There are existing subscriptions to heterogeneous publication '% s'. To add new articles, first drop the existing subscriptions to the publicatio n. 21132 16 Cannot create transactional subscription to merge publication '% s'. The publication type should be either transactional(0) or snapshot(1) for th is operation. 21133 16 Publication '%s' is not enabled to use an independent agent. 21134 16 The specified job ID must identify a Distribution Agent or a Mer ge Agent job. 21135 16 Detected inconsistencies in the replication agent table. The spe cified job ID does not correspond to an entry in '%ls'. 21136 16 Detected inconsistencies in the replication agent table. The spe cified job ID corresponds to multiple entries in '%ls'. 21137 16 This procedure supports only remote execution of push subscripti on agents. 21138 16 The 'offload_server' property cannot be the same as the Distribu tor name. 21139 16 Could not determine the Subscriber name for distributed agent ex ecution. 21140 16 Agent execution cannot be distributed to a Subscriber that resid es on the same server as the Distributor. 21141 16 The @change_active flag may not be specified for articles with m anual filters or views. 21142 16 The SQL Server '%s' could not obtain Windows group membership in formation for login '%s'. Verify that the Windows account has access to the doma in of the login. 21143 16 The custom stored procedure schema option is invalid for a snaps hot publication article. 21144 16 Cannot subscribe to publication of sync_type 'dump database' bec ause the Subscriber has subscriptions to other publications. 21145 16 Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type 'dump database'. 21146 16 @use_ftp cannot be 'true' while @alt_snapshot_folder is neither NULL nor empty. 21147 16 The '%s' database is not published for merge replication. 21148 16 Both @subscriber and @subscriberdb must be specified with non-nu ll values simultaneously, or both must be left unspecified. 21149 16 The '%s' database is not published for transactional or snapshot replication. 21150 16 Unable to determine the snapshot folder for the specified subscr iption because the specified Subscriber is not known to the Distributor. 21151 16 Pre- and post-snapshot commands are not supported for a publicat ion that may support non-SQL Server Subscribers by using the character-mode bcp as the synchronization method. 21152 16 Cannot create a subscription of sync_type 'none' to a publicatio n using the 'concurrent' or 'concurrent_c' synchronization method. 21153 16 Cannot create article '%s'. All articles that are part of a conc urrent synchronization publication must use stored procedures to apply changes t o the Subscriber. 21154 16 Cannot change article '%s'. All articles that are part of a con current synchronization publication must use stored procedures to apply changes to the Subscriber. 21155 16 Cannot change article '%s'. articles that are part of a concurr ent synchronization publication can not have ins_cmd/del_cmd which exceeds %d ch aracters . 21156 16 The @status parameter value must be 'initiated' or 'active'.

21157 16 The snapshot compression option can be enabled only for a public ation having an alternate snapshot generation folder defined. 21158 16 For a publication to be enabled for the Internet, the 'ftp_addre ss' property must not be null. 21159 16 If a publication is enabled for the Internet, the 'alt_snapshot_ folder' property must be non-empty. 21160 16 The 'ftp_port' property must be a non-negative integer < 65536. 21161 16 Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers. 21162 16 It is invalid to exclude the rowguid column for the table from t he partition. 21163 16 It is not possible to add column '%s' to article '%s' because th e snapshot for publication '%s' has been run. 21164 16 Column '%s' cannot be included in a vertical partition because i t is neither nullable nor defined with a default value. 21165 16 Column '%s' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value. 21166 16 Column '%s' does not exist. 21167 16 The specified job ID does not represent a %s agent job for any p ush subscription in this database. 21168 16 Only members of the sysadmin fixed server role, members of the d b_owner fixed database role, and owners of subscriptions served by the specified replication agent job can modify the agent offload settings. 21169 16 Could not identify the Publisher '%s' at the Distributor '%s'. M ake sure that the server '%s' is registered at the Distributor. 21170 16 The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, SQL Server 2005, and O LE DB Subscribers can use transformable subscriptions. 21171 16 Could not find package '%s' in msdb at server '%s'. 21172 16 The publication has to be in 'character', 'concurrent_c', or 'da tabase snapshot character' bcp mode to allow DTS. 21173 16 The publication has to be 'independent_agent type' to allow DTS. 21174 16 Because this publication allows transformable subscriptions usin g DTS, it requires autogenerated stored procedures and parameterized commands, w hich are set using default value for the @status. 21175 16 You cannot change the ins_cmd, upd_cmd, or del_cmd article prope rties because the publication allows Data Transformation Services or updatable s ubscriptions. 21176 16 Only members of the sysadmin fixed server role, db_owner fixed d atabase role, or the creator of the subscription can change the subscription pro perties. 21177 16 Could not create column list because it is too long. Create the list manually. 21178 16 Data Transformation Services (DTS) properties cannot be set beca use the publication does not allow transformable subscriptions using DTS. To all ow transformable subscriptions, you must drop the publication and then and re-cr eate it, specifying that transformable subscriptions are allowed. 21179 16 Invalid @dts_package_location parameter value. Valid options are 'Distributor' or 'Subscriber'. 21180 16 A publication that allows DTS cannot be enabled for updatable su bscriptions. 21181 16 @dts_package_name can be set for push subscriptions only. 21182 16 The @agent_type parameter must be one of 'distribution', 'merge' , or NULL. 21183 16 Invalid property name '%s'. 21184 16 %s parameter is incorrect: it should be '%s', '%s' or '%s'. 21185 16 The subscription is not initialized or not created for failover mode operations. 21186 16 Subscription for Publisher '%s' does not have a valid queue_id. 21187 16 The current mode is the same as the requested mode.

21188 10 Changed update mode from [%s] to [%s]. 21189 16 The queue for this subscription with queue_id = '%s' is not empt y. Run the Queue Reader Agent to make sure the queue is empty before setting mod e from [queued] to [immediate]. 21190 10 Overriding queue check for setting mode from [%s] to [%s]. 21192 16 MSrepl_tran_version column is a predefined column used for repli cation and can be only of data type uniqueidentifier 21193 16 @identity_range, @pub_identity_range, or @threshold cannot be NU LL when @identityrangemanagementoption is set to AUTO. 21194 16 Cannot support identity range management because this table does not have an identity column. 21195 16 A valid identity range is not available. Check the data type of the identity column. 21196 16 Identity automation failed. 21197 16 Failed to allocate new identity range. 21198 16 Schema replication failed. 21199 16 This change cannot take effect until you run the snapshot again. 21200 16 Publication '%s' does not exist. 21201 16 Dropping a column that is being used by a merge filter clause is not allowed. 21202 16 It is not possible to drop column '%s' to article '%s' because t he snapshot for publication '%s' has already been run. 21203 10 Duplicate rows found in %s. Unique index not created. 21204 16 The publication '%s' does not allow subscription copy or its sub scription has not been synchronized. 21205 16 The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes. 21206 16 Cannot resolve load hint for object %d because the object is not a user table. 21207 16 Cannot find source object ID information for article %d. 21208 16 This step failed because column '%s' exists in the vertical part ition. 21209 16 This step failed because column '%s' does not exist in the verti cal partition. 21210 16 The publication must be immediate_sync type to allow subscriptio n copy. 21211 16 The database is attached from a subscription copy file without u sing sp_attach_subscription. Drop the database and reattach it using sp_attach_s ubscription. 21212 16 Cannot copy subscription. Only single file subscription database s are supported for this operation. 21213 16 Subscribers cannot subscribe to publications that allow DTS with out using a DTS package. 21214 16 Cannot create file '%s' because it already exists. 21215 16 An alternate synchronization partner can be configured only at t he Publisher. 21216 16 Publisher '%s', publisher database '%s', and publication '%s' ar e not valid synchronization partners. 21217 10 Publication of '%s' data from Publisher '%s'. 21218 16 The creation_script property cannot be NULL if a schema option o f 0x0000000000000000 is specified for the article. 21219 16 The specified source object must be a stored procedure object if it is published as a 'proc schema only' type article. 21220 16 Unable to add the article '%s' because a snapshot has been gener ated for the publication '%s'. 21221 16 The specified source object must be a view object if it is going to be as a 'view schema only' type article. 21222 16 The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, 0x00001000, 0x00002000 , 0x00400000, 0x02000000, 0x08000000, 0x10000000, 0x20000000, 0x40000000, and 0x

80000000. 21223 16 The @pre_creation_command parameter for a schema only article mu st be either 'none' or 'drop'. 21224 16 '%s' is not a valid property for a schema only article. 21225 16 The 'offload_server' property cannot be NULL or empty if the pul l subscription agent is to be enabled for remote activation. 21226 16 The database '%s' does not have a pull subscription to the speci fied publication. 21227 16 The 'offload_server' property cannot be the same as the Subscrib er server name. 21228 16 The specified source object must be a user-defined function obje ct if it is going to be published as a 'func schema only' type article. 21229 16 The schema options available for a view schema article are: 0x00 000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, 0x00002000, 0x00040000, 0x00100000, 0x00200000, 0x00400000, 0x00800000, 0x01000000, 0x080000 00, 0x40000000, and 0x80000000. 21230 16 Do not call this stored procedure for schema change because the current database is not enabled for replication. 21231 16 Automatic identity range support is useful only for publications that allow updating subscribers. 21232 16 Identity range values must be positive integers that are greater than 1. 21233 16 Threshold value must be from 1 through 100. 21234 16 Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set 'identity_insert' settings at the Subscriber. 21235 16 Article property '%s' can be set only when the article uses auto matic identity range management. 21236 16 The subscription(s) to Publisher '%s' does not allow subscriptio n copy or it has not been synchronized. 21237 16 There is a push subscription to Publisher '%s'. Only pull and an onymous subscriptions can be copied. 21238 16 This database either is a publisher, or there is a push subscrip tion to publication '%s'. Only pull and anonymous subscriptions can be copied. 21239 16 Cannot copy subscriptions because there is no synchronized subsc ription found in the database. 21240 16 The table '%s' is already published as another article with a di fferent automatic identity support option. 21241 16 The threshold value should be from 1 through 100. 21242 16 Conflict table for article '%s' could not be created successfull y. 21243 16 Publisher '%s', publication database '%s', and publication '%s' could not be added to the list of synchronization partners. 21244 16 Character mode publication does not support vertical filtering w hen the base table does not support column-level tracking. 21245 16 Table '%s' is not part of publication '%s'. 21246 16 This step failed because table '%s' is not part of any publicati on. 21247 16 Cannot create file at '%s'. Ensure the file path is valid. 21248 16 Cannot attach subscription file '%s'. Ensure the file path is va lid and the file is updatable. 21249 16 OLE DB or ODBC Subscribers cannot subscribe to article '%s' in p ublication '%s' because the article has a timestamp column and the publication i s 'allow_queued_tran' (allows queued updating subscriptions). 21250 16 Primary key column '%s' cannot be excluded from a vertical parti tion. 21251 16 Publisher '%s', publisher database '%s', publication '%s' could not be removed from the list of synchronization partners. 21252 16 It is invalid to remove the default Publisher '%s', publication database '%s', and publication '%s' from the list of synchronization partners

21253 16 Parameter '@add_to_active_directory' cannot be set to TRUE becau se Active Directory client package is not installed properly on the machine wher e SQL Server is running. 21254 16 The Active Directory operation on publication '%s' could not be completed because Active Directory client package is not installed properly on t he machine where SQL Server is running. 21255 16 Column '%s' already exists in table '%s'. 21256 16 A column used in filter clause '%s' either does not exist in the table '%s' or cannot be excluded from the current partition. 21257 16 Invalid property '%s' for article '%s'. 21258 16 You must first drop all existing merge publications to add an an onymous or local subscription to database '%s'. 21259 16 Invalid property value '%s'. See SQL Server Books Online for a l ist of valid parameters for sp_changemergearticle. 21260 16 Schema replication failed because database '%s' on server '%s' i s not the original Publisher of table '%s'. 21261 16 The offload server must be specified if the agent for this subsc ription is to be offloaded for remote execution. 21262 16 Failed to drop column '%s' from the partition because a computed column is accessing it. 21263 16 Parameter '%s' cannot be NULL or an empty string. 21264 16 Column '%s' cannot be dropped from table '%s' because it is a pr imary key column. 21265 16 Column '%s' cannot be dropped from table '%s' because there is a unique index accessing this column. 21266 16 Cannot publish table '%s' for both a merge publication and a pub lication with the updatable subscribers option. 21267 10 Invalid value for queue type was specified. Valid values = (%s). 21268 10 Cannot change the parameter %s while there are subscriptions to the publication. 21269 16 Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication. 21270 10 Queued snapshot publication property '%s' cannot have the value '%s'. 21272 16 Cannot clean up the meta data for publication '%s' because other publications are using one or more articles in this publication. 21273 16 You must upgrade the Subscriber to SQL Server 2000 to create upd atable subscriptions when the Publisher is SQL Server 2000 or higher. 21274 16 Invalid publication name '%s'. 21275 16 Cannot publish the schema-bound view '%ls'. The value specified for the @type parameter must be "indexed view schema only" (for snapshot or tran sactional replication) or "indexed view logbased" (for transactional replication only). 21276 16 The type must be 'table' or '( view | indexed view | proc | func ) schema only'. 21277 16 Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view schema only" or "indexed view logbased") can be used only for indexed views. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique cluste red index. 21278 16 Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view logbased") requires that the view be schema b ound with a unique clustered index. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique cl ustered index. 21279 16 The 'schema_option' property for a merge article cannot be chang ed after a snapshot is generated for the publication. To change the 'schema_opti on' property of this article the corresponding merge publication must be dropped and re-created. 21280 16 Publication '%s' cannot be subscribed to by Subscriber database

'%s' because it contains one or more articles that have been subscribed to by th e same Subscriber database at transaction level. 21281 16 Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by th e same Subscriber database at merge level. 21282 16 @identity_range, @pub_identity_range, and @threshold must be NUL L when @identityrangemanagementoption is set to 'none' or 'manual'. 21283 16 Column '%s' of table '%s' cannot be excluded from a vertical par tition because there is a computed column that depends on it. 21284 16 Failed to drop column '%s' from table '%s'. 21285 16 Failed to add column '%s' to table '%s'. 21286 16 Conflict table '%s' does not exist. 21287 16 The specified @destination_folder is not a valid path of an exis ting folder. 21288 16 Could not create the snapshot directory structure in the specifi ed @destination_folder. 21289 16 Either the snapshot files have not been generated or they have b een cleaned up. 21290 16 The identity range value provided has exceeded the maximum value allowed. 21291 16 The specified automatic identity support parameters conflict wit h the settings in another article. 21292 16 Object '%s' cannot be published twice in the same publication. 21293 10 Warning: adding updatable subscription for article '%s' may caus e data inconsistency as the source table is already subscribed to '%s' 21294 16 Either @publisher (and @publisher_db) or @subscriber (and @subsc riber_db) must be specified, but both cannot be specified. 21295 16 Publication '%s' does not contain any article that uses automati c identity range management. 21296 16 Parameter @resync_type must be either 0, 1, 2. 21297 16 Invalid resync type. No validation has been performed for this s ubscription. 21298 16 Failed to resynchronize this subscription. 21299 16 Invalid Subscriber partition validation expression '%s'. 21300 10 The resolver information was specified without specifying the re solver to be used for article '%s'. The default resolver will be used. 21301 16 The resolver information should be specified while using the '%s ' resolver. 21302 16 The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%s' resolver. 21303 16 The article '%s' should enable column tracking to use the '%s' r esolver. The default resolver will be used to resolve conflicts on this article. 21304 16 The merge triggers could not be created on the table '%s'. 21305 16 The schema change information could not be updated at the subscr iption database. 21306 16 The copy of the subscription could not be made because the subsc ription to publication '%s' has expired. 21307 16 The subscription could not be attached because the subscription to publication '%s' has expired. 21308 10 Rowcount validation profile. 21309 10 Profile used by the Merge Agent to perform rowcount validation. 21310 10 Rowcount and checksum validation profile. 21311 10 Profile used by the Merge Agent to perform rowcount and checksum validation. 21312 10 Cannot change this publication property because there are active subscriptions to this publication. 21313 10 Subscriber partition validation expression must be NULL for stat ic publications. 21314 10 There must be one and only one of '%s' and '%s' that is not NULL .

21315 10 Failed to adjust Publisher identity range for table '%s'. 21316 10 Failed to adjust Publisher identity range for publication '%s'. 21317 10 A push subscription to the publication '%s' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. 21318 10 Table '%s' must have at least one column that is included in the vertical partition. 21319 16 Could not find the Snapshot Agent command line for the specified publication. Check that a valid regular snapshot job exists on the distributor. 21320 16 The version of the Distributor cannot be lower than the version of the Publisher. 21321 16 The parameter @dynamic_snapshot_location cannot be an empty stri ng. 21322 16 This publication logs conflicts on both replicas. Pre-SQL Server 2005 subscribers will not honor this setting. 21323 16 A dynamic snapshot job can be scheduled only for a publication w ith dynamic filtering enabled. 21324 16 A Snapshot Agent must be added for the specified publication bef ore a dynamic snapshot job can be scheduled. 21325 16 Could not find the Snapshot Agent ID for the specified publicati on. 21326 16 Could not find the dynamic snapshot job with a '%ls' of '%ls' fo r the specified publication. 21327 16 '%ls' is not a valid dynamic snapshot job name. 21328 16 The specified dynamic snapshot job name '%ls' is already in use. Try the operation again with a different job name. 21329 16 Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_ snapshot_jobname, can be specified with a nondefault value. 21330 16 Cannot create a sub-directory under the snapshot folder (%ls). E nsure that there is enough disk space available, and that the account under whic h the Snapshot Agent runs has permissions to create a sub-directory under the sn apshot folder. 21331 16 Cannot copy user script file to the snapshot folder at the Distr ibutor (%ls). Ensure that there is enough disk space available, and that the acc ount under which the Snapshot Agent runs has permissions to write to the snapsho t folder and its subdirectories. 21332 16 Failed to retrieve information about the publication : %ls. Chec k the name again. 21333 16 A generation that was expected to be in %s.dbo.MSmerge_genhistor y could not be found. If this error occurred in a subscription database, reiniti alize the subscription. If this error occurred in a publication database, restor e the database from a backup. 21334 16 Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant 21335 16 Warning: column '%s' already exists in the vertical partition. 21336 16 Warning: column '%s' does not exist in the vertical partition. 21337 16 Invalid @subscriber_type value. Valid options are 'local' and 'g lobal'. 21338 16 Cannot execute sp_dropmergearticle if the publication has a Subs criber that is running on a version of SQL Server 2000 or earlier. Drop and re-c reate the publication without the article '%s' or set the publication compatibil ity level of publication '%s' to '90RTM' before calling sp_dropmergearticle. 21339 10 Warning: the publication uses a feature that is only supported o nly by subscribers running '%s' or higher. 21340 16 On Demand user script cannot be applied to the snapshot publicat ion. 21341 16 @dynamic_snapshot_location cannot be a non-empty string while @a lt_snapshot_folder is neither empty nor null. 21342 16 @dynamic_snapshot_location cannot be a non-empty string while @u se_ftp is 'true'. 21343 16 Could not find stored procedure '%s'.

21344 16 Invalid value specified for %ls parameter. 21345 16 Excluding the last column in the partition is not allowed. 21346 16 Failed to change the owner of '%s' to '%s'. 21347 16 Column '%s' cannot be excluded from the vertical partitioning be cause there is a unique index accessing this column. 21348 16 Invalid property name '%s'. 21349 10 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because decentralized conflict lo gging is designated. 21350 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because a compressed snapshot is used. 21351 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because vertical filters are being used. 21352 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because schema replication is performed. 21353 10 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide reinitia lization is performed. 21354 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because publication wide reinitialization is pe rformed. 21355 10 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because merge metadata cleanup ta sk is performed. 21356 10 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide validati on task is performed. 21357 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because data types new in SQL Server 2000 exist in one of its articles. 21358 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because at least one timestamp column exists in one of its articles. 21359 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because automatic identity ranges are being use d. 21360 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because a new article has been added to the pub lication after its snapshot has been generated. 21361 16 The specified @agent_jobid is not a valid job id for a '%s' agen t job. 21362 16 Merge filter '%s' does not exist. 21363 16 Failed to add publication '%s' to Active Directory. %s 21364 16 Could not add article '%s' because a snapshot is already generat ed. Set @force_invalidate_snapshot to 1 to force this and invalidate the existin g snapshot. 21365 16 Could not add article '%s' because there are active subscription s. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions. 21366 16 Could not add filter '%s' because a snapshot is already generate d. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. 21367 16 Could not add filter '%s' because there are active subscriptions . Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions. 21368 16 The specified offload server name contains the invalid character '%s'. 21369 16 Could not remove publication '%s' from Active Directory. 21370 16 The resync date specified '%s' is not a valid date. 21371 10 Could not propagate the change on publication '%s' to Active Dir

ectory. 21372 16 Cannot drop filter '%s' from publication '%s' because its snapsh ot has been run and this publication could have active subscriptions. Set @force _reinit_subscription to 1 to reinitialize all subscriptions and drop the filter. 21373 11 Could not open database %s. Replication settings and system obje cts could not be upgraded. If the database is used for replication, run sp_vupgr ade_replication in the [master] database when the database is available. 21374 10 Upgrading distribution settings and system objects in database % s. 21375 10 Upgrading publication settings and system objects in database %s . 21376 11 Could not open database %s. Replication settings and system obje cts could not be upgraded. If the database is used for replication, run sp_vupgr ade_replication in the [master] database when the database is available. 21377 10 Upgrading subscription settings and system objects in database % s. 21378 16 Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again. 21379 16 Cannot drop article '%s' from publication '%s' because a snapsho t is already generated. Set @force_invalidate_snapshot to 1 to force this and in validate the existing snapshot. 21380 16 Cannot add timestamp column without forcing reinitialization. Se t @force_reinit_subscription to 1 to force reinitialization. 21381 16 Cannot add (drop) column to table '%s' because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subs cription to 1 to force reinitialization. 21382 16 Cannot drop filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing s napshot. 21383 16 Cannot enable a merge publication on this server because the wor king directory of its Distributors is not using a UNC path. 21384 16 The specified subscription does not exist or has not been synchr onized yet. 21385 16 Snapshot failed to process publication '%s'. Possibly due to act ive schema change activity or new articles being added. 21386 16 Schema change failed on object '%s'. Possibly due to active snap shot or other schema change activity. 21387 16 The expanded dynamic snapshot view definition of one of the arti cles exceeds the system limit of 3499 characters. Consider using the default mec hanism instead of the dynamic snapshot for initializing the specified subscripti on. 21388 10 The concurrent snapshot for publication '%s' is not available be cause it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snaps hot Agent for the publication must be restarted until a complete snapshot is gen erated. 21389 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because column-level collation is scripted out with the article schema creation script. 21390 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because extended properties are scripted out wi th the article schema creation script. 21391 10 Warning: only Subscribers running SQL Server 2000 or later can s ynchronize with publication '%s' because it contains schema-only articles. 21392 16 Row filter(%s) is invalid for column partition(%s) for article ' %s' in publication '%s'. 21393 16 Dropping row filter(%s) for article '%s' in '%s'. Reissue sp_art iclefilter and sp_articleview to create a row filter. 21394 16 Invalid schema option specified for publication that allows upda

ting subscribers. Need to set the schema option to include DRI constraints. 21395 10 This column cannot be included in a transactional publication be cause the column ID is greater than 255. 21396 16 The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Se rver Books Online for a list of valid values. 21397 16 The transactions required for synchronizing the nosync subscript ion created from the specified backup are unavailable at the Distributor. Retry the operation again with a more up-to-date log, differential, or full database b ackup. 21398 16 Could not complete setting up the no-sync subscription at the Di stributor while the distribution cleanup agent is running. The operation has a g reater chance of success if the distribution cleanup agent is temporarily disabl ed. 21399 16 The transactions required for synchronizing the subscription wit h the specified log sequence number (LSN) are unavailable at the Distributor. Sp ecify a higher LSN. 21400 16 Article property must be changed at the original Publisher of ar ticle '%s'. 21401 16 Article name cannot be 'all'. 21402 16 Incorrect value for parameter '%s'. 21403 10 The 'max_concurrent_dynamic_snapshots' publication property must be greater than or equal to zero. 21404 10 '%s' is not a valid value for the '%s' parameter. The value must be a positive integer greater than 300 or 0. 21405 10 '%s' is not a valid value for the '%s' parameter. The value must be an integer greater than or equal to %d. 21406 10 '%s' is not a valid value for the '%s' parameter. The value must be 0 or 1. 21407 16 Cannot create the subscription. If you specify a value of "initi alize with backup" for the @sync_type parameter, you must subscribe to all artic les in the publication by specifying a value of "all" for the @article parameter . 21408 16 Cannot create the subscription. You must specify a value of "Act ive" or "Subscribed" for the @status parameter. This is because the value specif ied for the @sync_type parameter is "initialize with backup" or "replication sup port only". 21409 16 Only one of parameters %s and %s can be set. 21410 16 Snapshot Agent startup message. 21411 16 Distribution Agent startup message. 21412 16 Merge Agent startup message. 21413 16 Failed to acquire the application lock indicating the front of t he queue. 21414 10 Unexpected failure acquiring an application lock. Ensure that th e account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when the re are more server resources available. 21415 10 Unexpected failure releasing an application lock. Ensure that th e account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when the re are more server resources available. 21416 10 Property '%s' of article '%s' cannot be changed. 21417 10 Having a queue timeout value of over 12 hours is not allowed. 21419 10 Filter '%s' of article '%s' cannot be changed. 21420 10 Subscription property '%s' cannot be changed. 21421 10 Article '%s' cannot be dropped because there are other articles using it as a join article. 21422 16 Queue Reader Agent startup message. 21423 16 Either the publication '%s' does not exist or you do not have su fficient permissions to access it. Ensure that the publication exists and that t

he account under which the Merge Agent connects to the Publisher is included in the publication access list (PAL). 21424 16 The @publisher parameter must be NULL for SQL Server publishers. 21425 16 The @publisher parameter may not be NULL for heterogeneous publi shers. 21426 16 No shared agent subscription exists for publication '%s' and the subscriber/subscriber database pair '%s'/'%s'. 21450 16 The replication %s could not be upgraded for %s databases. Ensur e that %s is upgraded and execute %s again. 21451 16 The %s %s (%s) login (%s) password has been changed. 21452 10 Warning: The %s agent job has been implicitly created and will r un under the SQL Server Agent Service Account. 21454 16 The internal procedure sp_MStran_is_snapshot_required must be ex ecuted at the Distributor if the @run_at_distributor parameter has a value of 1. If the problem persists, contact Microsoft Customer Support Services. 21456 16 Value provided for parameter %s is not valid. 21460 16 The primary key for source table "%s" includes the timestamp col umn "%s". Cannot create the article for the specified publication because it all ows updating Subscribers. 21481 16 Cannot create replication subscription(s) in the master database . Choose another database for creating subscriptions. 21482 16 %s can only be executed in the "%s" database. 21484 16 Article validation was requested for snapshot publication "%s". Article validation is only valid for transactional publications. 21485 16 Tracer tokens cannot be posted for a snapshot publication. 21486 16 An error occurred while logging the tracer token history informa tion. The tracer token could not be posted. 21487 16 An error occurred while inserting the tracer token to the log. T he tracer token could not be posted. 21488 16 No active subscriptions were found. The publication must have ac tive subscriptions in order to post a tracer token. 21489 16 A database '%s' already exists. If you intend this to be your di stribution database set @existing_db = 1. 21490 16 The value specified for the %s parameter of sp_mergearticlecolum n must be '%s'. A value of 'true' is allowed only when this procedure is called by another replication procedure. Either set the value of the @schema_replicatio n parameter to 'false' or do not specify a value. 21499 16 The procedure %s failed to %s the resource %s. Server error = %d . 21500 10 Invalid subscription type is specified. A subscription to public ation '%s' already exists in the database with a different subscription type. 21501 10 The supplied resolver information does not specify a valid colum n name to be used for conflict resolution by '%s'. 21502 10 The publication '%s' does not allow the subscription to synchron ize to an alternate synchronization partner. 21503 10 Cleanup of merge meta data cannot be performed while merge proce sses are running. Retry this operation after the merge processes have completed. 21504 10 Cleanup of merge meta data at republisher '%s'.'%s' could not be performed because merge processes are propagating changes to the republisher. A ll subscriptions to this republisher must be reinitialized. 21505 10 Changes to publication '%s' cannot be merged because it has been marked inactive. 21506 10 sp_mergecompletecleanup cannot be executed before sp_mergeprepar ecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge meta data cleanup. 21507 10 All prerequisites for cleaning up merge meta data have been comp leted. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data cleanup. 21508 10 Cleanup of merge meta data cannot be performed while merge proce sses are running. Cleanup will proceed after the merge processes have completed.

21509 10 Cleanup of merge meta data cannot be performed because some repu blishers have not quiesced their changes. Cleanup will proceed after all republi shers have quiesced their changes. 21510 10 Data changes are not allowed while cleanup of merge meta data is in progress. 21511 10 Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row. 21512 18 %ls: The %ls parameter is shorter than the minimum required size . 21514 16 Cannot complete the requested operation in the subscription data base because a snapshot is currently being delivered to the database. Perform th e operation again at a later time. To stop the delivery of the snapshot, stop th e Distribution Agent or Merge Agent associated with the subscription. 21515 18 Replication custom procedures will not be scripted because the s pecified publication '%s' is a snapshot publication. 21516 10 Transactional replication custom procedures for publication '%s' from database '%s': 21517 10 Replication custom procedures will not be scripted for article ' %s' because the auto-generate custom procedures schema option is not enabled. 21518 10 Replication custom procedures for article '%s': 21519 10 Custom procedures will not be scripted for article update comman ds based on direct INSERT, UPDATE, or DELETE statements. 21520 10 Custom procedure will not be scripted because '%s' is not a reco gnized article update command syntax. 21521 16 Some generation values are above the upper limit of %d used in S QL Server 2000. Change the publication_compatibility_level of the publication to 90 to make this work. 21522 16 This article cannot use the '%s' feature because the publication compatibility level is less than 90. Use sp_changemergepublication to set the p ublication_compatibility_level of publication '%s' to '90RTM'. 21523 16 Adding column '%s' to table '%s' failed. Articles can have at mo st %d columns, including columns that have been filtered. 21525 16 A lightweight replica must be anonymous. 21526 16 Article '%s' already belongs to a subscription with a different value for the @lightweight property. 21527 16 Publication '%s' cannot be added to database '%s', because a pub lication with a lower compatibility level already exists. All merge publications in a database must have the same compatibility level. 21528 16 Publication '%s' cannot be added to database '%s', because a pub lication with a higher compatibility level already exists. All merge publication s in a database must have the same compatibiliy level. 21530 10 The schema change failed during execution of an internal replica tion procedure. For corrective action, see the other error messages that accompa ny this error message. 21531 10 The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republ ishing hierarchy, DDL commands can only be executed at the root Publisher, not a t any of the republishing Subscribers. 21532 10 Cannot add a data definition language trigger for replicating '% .*ls' events. 21533 10 Cannot insert information into the schema change tracking table sysmergeschemachange. 21535 16 The article '%s' is already published in another publication, an d is set to use nonoverlapping partitions with multiple subscribers per partitio n (@partition_options = 2). This setting does not permit the article to be inclu ded in more than one publication. 21537 16 The column '%s' in table '%s' is involved in a foreign key relat ionship with a column in table '%s', but this column was not found in the specif ied join clause. A logical record relationship between these tables should inclu de this column.

21538 16 Table '%s' cannot have table '%s' as a parent in a logical recor d relationship because it already has a different parent table. A logical record relationship allows only one parent table for a given child table. 21539 16 A logical record relationship, specified by the @filter_type par ameter, requires a one-to-one or a one-to-many join from the parent table to the child table. Either change the value of the @filter_type parameter, or set the @join_unique_key parameter to 1. 21540 16 You cannot drop a column defined as data type uniqueidentifier w ith the rowguidcol property because merge replication uses this column for track ing. To drop the column, you must first drop the table from all publications and subscriptions. 21541 16 Cannot complete ALTER TABLE command. Do not execute the command 'ALTER TABLE table_name DISABLE TRIGGER ALL' on a published table. Reissue multi ple 'ALTER TABLE table_name DISABLE TRIGGER trigger_name' statements to disable each trigger individually on the given table. 21542 16 Encountered server error %d while executing <%s>. 21543 16 The schema for the article %s was either not generated properly or was not applied properly during initial synchronization. This may be due to p ermissions issues. Verify whether the object exists, and whether the necessary p ermissions are granted. 21544 10 Value specified for the publication property replicate_ddl is no t valid. The value must be 1 or 0. 21545 16 You cannot disable a trigger used by merge replication on a publ ished table. To drop the trigger, drop the table from the publication. 21546 16 Cannot replicate the ALTER TABLE command. It contains multiple D ROP commands, including a DROP command for a column that is not included in all subscriptions to this article. Use a single DROP command in each ALTER TABLE com mand. 21547 16 Encountered server error %d while restoring the log for database %s. 21548 16 Cannot execute sp_change_subscription_properties. This stored pr ocedure can only be used for publications that have at least one pull subscripti on. 21549 16 Cannot add the computed column '%s' to the publication. You must first add all columns on which this column depends; you cannot filter any of th ese colunmns from the article. 21550 16 Before you drop the column from the publication, all computed co lumns that depend on column '%s' must be dropped. 21551 16 Only members of the sysadmin or db_owner or db_ddladmin roles ca n perform this operation. 21552 16 Merge data definition language (DDL) error: Dropping a column us ed in a row filter or a join filter is not allowed. To drop a column used in a r ow filter, first change the row filter using sp_changemergearticle. To drop a co lumn used in a join filter, first drop the join filter using sp_dropmergefilter. 21561 16 The value specified for parameter %s = %d is not valid. 21564 16 The table %s contains the column msrepl_tran_version, which is u sed by replication. The column is set to NULL, but it must be set to NOT NULL. R eplication failed to alter this column, so you must drop the column and then add the table as an article again using sp_addarticle. Replication will then add th e column to the table. 21567 16 The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications that allow updating s ubscriptions. If you do not require updating subscriptions, specify a different call format. If you do require updating subscriptions, you must drop the publica tion and re-create it to specify that updating subscriptions are allowed. 21569 16 The article %s in the publication %s does not have a valid confl ict table entry in the system table sysarticleupdates. This entry is required fo r publications that allow queued updating subscriptions. Check for errors in the last run of the Snapshot Agent. 21570 16 Cannot create the logical record relationship. Table '%s' does n

ot have a foreign key referencing table '%s'. A logical record relationship requ ires a foreign key relationship between the parent and child tables. 21571 16 Cannot create the logical record relationship in publication '%s '. The use_partition_groups option for the publication must be set to "true" in order to use logical records. Use sp_changemergepublication to set the option to "true". 21572 16 Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is disabled. To create the logical record relatio nship, first enable the foreign key constraint. 21573 16 Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is defined with the NOT FOR REPLICATION option. T o add the logical record relationship, first drop the foreign key constraint, an d then re-create it without the NOT FOR REPLICATION option. 21574 16 Cannot add a logical record relationship because the article '%s ' is published in publication '%s', which has a compatibility level lower than 9 0RTM. Use sp_changemergepublication to set the publication_compatibility_level t o 90RTM. 21575 16 The value specified for the property filter_type is not valid. V alid values are 1 (join filter only), 2 (logical record relation only), and 3 (j oin filter and logical record relation). 21576 16 Cannot add a logical record relationship between tables '%s' and '%s' because the foreign key column '%s' in table '%s' allows NULL values. Alte r the column to disallow NULL values. 21578 16 In order to use partition_options of 2 (non overlapping partitio ns with multiple subscriptions per partition) or 3 (non overlapping partitions o ne subscription per partition) the publication '%s' must be enabled to use parti tion groups functionality. Use sp_changemergepublication to set 'use_partition_g roups' to 'true'. 21579 16 Article "%s" in publication "%s" does not qualify for the partit ion option that you specified. You cannot specify a value of 2 or 3 (nonoverlap ping partitions) for the @partition_options parameter because the article is inv olved in multiple join filters. Either select a value of 0 or 1 for the @partiti on_options parameter, or drop all but one of the join filters by using sp_dropme rgefilter. 21580 16 Article "%s" in publication "%s" does not qualify for the partit ion option that you specified. You cannot specify a value of 2 or 3 (nonoverlap ping partitions) for the @partition_options parameter because the article is inv olved in both a row filter and a join filter. Either select a value of 0 or 1 fo r the @partition_options parameter; drop the join filter by using sp_dropmergefi lter; or change the row filter by using sp_changemergepublication. 21581 16 Article "%s" in publication "%s" does not qualify for the partit ion option that you specified. You cannot specify a value of 2 or 3 (nonoverlap ping partitions) for the @partition_options parameter because the article has a join filter with a join_unique_key value of 0. Either select a value of 0 or 1 f or the @partition_options parameter, or use sp_changemergefilter to specify a va lue of 1 for join_unique_key. 21582 16 Article "%s" in publication "%s" does not qualify for the partit ion option that you specified. You cannot specify a value of 2 or 3 (nonoverlap ping partitions) for the @partition_options parameter because the article has a direct or indirect join filter relationship with parent article "%s". The parent article does not use the same value for partition_options. Use sp_changemergepu blication to change the value for one of the articles. 21583 16 Cannot update the column in article '%s'. The article has a valu e of 2 or 3 (nonoverlapping partitions) for the partition_options property, and the column is involved in a row filter and/or a join filter. In this situation, the column cannot be updated at a Subscriber or republisher; it must be updated at the top-level Publisher. 21584 16 Cannot insert the row for article '%s'. The row does not belong to the Subscriber's partition, and the article has a value of 2 or 3 (nonoverlap ping partitions) for the partition_options property. Nonoverlapping partitions d

o not allow out-of-partition inserts. 21585 16 Cannot specify custom article ordering in publication '%s' becau se the publication has a compatibility level lower than 90RTM. Use sp_changemerg epublication to set the publication_compatibility_level to 90RTM. 21597 16 The article includes only the rowguidcol column. You must publis h at least one other column. 21598 16 Modifying DDL triggers created by replication is disallowed sinc e these are required to track DDL changes. 21599 16 The parameters @article and @join_articlename cannot have the sa me value. Specify different articles for the two parameters; self-joins are not permitted. 21600 16 Non-SQL Server Publisher [%s] cannot be found. Execute sp_helpdi stpublishers to view a list of available Publishers. 21601 16 The value of the parameter @type must be 'logbased' for Oracle p ublications. 21603 16 The refresh of Oracle publisher '%s' by sp_refresh_heterogeneous _publisher was not successful. The Oracle publisher meta data has been retained in its failed state to help in diagnosing the cause of the failure. When the pro blem has been diagnosed and resolved, rerun sp_refresh_heterogeneous_publisher t o complete the refresh. 21604 16 The non-SQL Server Publisher vendor is not valid. Attempt to add the Publisher again. If the problem persists, contact Microsoft Customer Suppor t Services. 21605 16 Non-SQL Server Publishers must be configured in the context of t he distribution database. Execute sp_adddistpublisher in the context of the dist ribution database. 21606 16 Parameter "%s" is for non-SQL Server Publishers only. The value of this parameter must be "%s" for a SQL Server Publisher. 21607 16 sp_refresh_heterogeneous_publisher was unable to obtain publishe r information for Oracle publisher '%s'. sp_refresh_heterogeneous_publisher may only be called to refresh Oracle publishers currently defined at the distributor . 21608 16 Cannot use a value of TRUE for the parameter @ignore_distributor . The value must be FALSE for a non-SQL Server Publisher. 21609 16 Non-SQL Server publications do not support updatable subscriptio ns. The properties allow_sync_tran and allow_queued_tran must be "false". 21610 16 The failed attempt by sp_refresh_heterogeneous_publisher to refr esh publisher '%s' did not alter any meta data at the Oracle publisher. Make cer tain that the correct Oracle publisher has been identified and that the requirem ents for refreshing the Oracle publisher have been met. 21611 16 Cannot drop the distribution Publisher "%s" because it has publi cations defined. Drop the publications first. 21612 16 For non-SQL Server Publishers, the value of the @sync_method par ameter must be "character" or "concurrent_c". 21613 16 Constraint column '%s' not found in table '%s'. 21614 16 Index column '%s' not found in table '%s', 21615 16 Unable to find table information for article %s. Local distribut or cache may be corrupt. 21616 16 Cannot find column [%s] in the article. Verify that the column e xists in the underlying table, and that it is included in the article. 21617 16 Unable to run SQL*PLUS. Make certain that a current version of t he Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21617 in Troubleshooting Oracle Publishers in SQL Server B ooks Online. 21618 16 The Publisher '%s' does not exist. To view a list of Publishers, use the stored procedure sp_helpdistpublisher. 21619 16 Must provide both @SelectColumnList and @InsColumnList. 21620 16 The version of SQL*PLUS that is accessible through the system Pa th variable is not current enough to support Oracle publishing. Make certain tha t a current version of the Oracle client code is installed at the distributor. F

or addition information, see SQL Server Error 21620 in Troubleshooting Oracle Pu blishers in SQL Server Books Online. 21621 16 Unable to create the public synonym %s. Verify that the replicat ion administrative user has been granted the CREATE SYNONYM permission. 21622 16 Unable to grant SELECT permission on the public synonym %s. Veri fy that the replication administrative user has sufficient permissions. 21623 16 Unable to update the public synonym 'MSSQLSERVERDISTRIBUTOR' to mark Oracle instance '%s' as a SQL Server publisher. 21624 16 Unable to locate the registered Oracle OLEDB provider, OraOLEDB. Oracle, at distributor '%s'. Make certain that a current version of the Oracle O LEDB provider is installed and registered at the distributor. For addition infor mation, see SQL Server Error 21624 in Troubleshooting Oracle Publishers in SQL S erver Books Online. 21625 16 Unable to update the publisher table HREPL_PUBLISHER at the Orac le instance '%s'. 21626 16 Unable to connect to Oracle database server '%s' using the Oracl e OLEDB provider OraOLEDB.Oracle. For addition information, see SQL Server Error 21626 in Troubleshooting Oracle Publishers in SQL Server Books Online. 21627 16 Unable to connect to Oracle database server '%s' using the Micro soft OLEDB provider MSDAORA. For addition information, see SQL Server Error 2162 7 in Troubleshooting Oracle Publishers in SQL Server Books Online. 21628 16 Unable to update the registry of distributor '%s' to allow Oracl e OLEDB provider OraOLEDB.Oracle to run in process with SQL Server. Make certain that current login is authorized to modify SQL Server owned registry keys. For addition information, see SQL Server Error 21628 in Troubleshooting Oracle Publi shers in SQL Server Books Online. 21629 16 The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not present at the distribu tor. Make certain that the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21629 in Trouble shooting Oracle Publishers in SQL Server Books Online. 21630 16 Unable to determine whether the table '%s' is still being publis hed. Contact Customer Support Services. 21631 16 Cannot unpublish table '%s'; the remote call to the Oracle Publi sher failed. Verify that the replication administrative user login can connect t o the Oracle Publisher using SQL*PLUS. If you can connect but the problem persis ts, drop and reconfigure Oracle publishing. 21632 16 The parameter %s is not supported for non-SQL Server publicatio ns. The value specified for this parameter must be %s. 21633 16 The publication '%s' could not be added because non-SQL Server P ublishers only support the @sync_method parameter values "character" or "concurr ent_c". 21634 16 The parameter %s does not support the value '%s' when using nonSQL Server publications. The value must be %s. 21635 16 An unsupported schema option combination was specified. Non-SQL Server publications only support the following schema options: 0x01, 0x02, 0x10, 0x40, 0x80, 0x4000, and 0x8000. 21637 16 %s is required for heterogeneous publications. 21638 16 You have specified a value of '%s' for the @repl_freq parameter of sp_addpublication. For non-SQL Server publications, this requires one of the following values for the @sync_method parameter: %s. 21639 16 Heterogeneous publishers can not use trusted connections, set @t rusted to false. 21640 16 Non-SQL Server Publishers do not support a value of 1 for the pa rameter @thirdparty_flag. When executing the stored procedure sp_adddistpublishe r, specify a value of 0 for the parameter. 21641 16 The "%s" parameter is for non-SQL Server Publishers only. It mus t be NULL for SQL Server Publishers. 21642 16 Heterogeneous publishers require a linked server. A linked serv er named '%s' already exists. Please remove linked server or choose a different

publisher name. 21643 16 The value specified for the parameter '%s' must be MSSQLSERVER, ORACLE, or ORACLE GATEWAY. 21644 16 %s value of '%s' is not supported for heterogeneous subscribers, must be %s. 21645 16 The value '%s' is not a valid non-SQL Server Publisher type. For SQL Server 2005, the value must be ORACLE or ORACLE GATEWAY. 21646 16 The Oracle server [%s] is already defined as the Publisher [%s] on the Distributor [%s].[%s]. Drop the Publisher or drop the public synonym [%s] . 21647 16 The Oracle Publisher support package could not be loaded. Drop t he replication administrative user schema and re-create it; ensure it is granted the documented permissions. 21649 16 Cannot change the property '%s'. Non-SQL Server Publishers do no t support this property. 21650 16 The value specified for @rowcount_only for the article '%s' is n ot 1. For an article in a publication from a non-SQL Server Publisher, 1 is the only valid setting for this parameter. 21651 16 Failed to execute the HREPL.%s request to Oracle Publisher '%s'. Verify that the Oracle package code exists on the Publisher, and that the repli cation administrative user account has sufficient permissions. 21653 16 The database management system (DBMS) %s %s does not exist. Veri fy the supported DBMS and versions by querying msdb.dbo.MSdbms. 21654 16 The data type %s does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings. 21655 16 The data type %s already exists. 21656 16 The data type mapping for %s does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings. 21657 16 The data type mapping for %s already exists. 21658 16 The data type mapping does not exist. Verify the list of mapping s by querying msdb.dbo.sysdatatypemappings. 21659 16 Cannot execute this procedure for a SQL Server Publisher. The Pu blisher must be a non-SQL Server Publisher. 21660 16 The value specified for the parameter @full_or_fast for article '%s' must be 0, 1, or 2. 21661 16 The value specified for the @shutdown_agent parameter for articl e '%s' must be 0 or 1. 21662 16 The source object [%s].[%s] on the non-SQL Server Publisher was either not found or is not supported. If the object exists, verify that it meets the requirements for being published. 21663 16 Cannot find a valid primary key for the source table [%s].[%s]. A valid primary key is required to publish the table. Add or correct the primary key definition on the source table. 21664 16 Index [%s] contains unique nullable column. 21665 16 Key [%s] contains unique nullable column. 21666 16 Cannot specify more than %d column names for the index or primar y key because this exceeds the maximum number of columns supported by SQL Server . %d columns were specified. 21667 16 The index "%s" was not created. The index has a key length of at least %d bytes. The maximum key length supported by SQL Server is %d bytes. 21668 16 The constraint "%s" was not created because one or more columns in the constraint is not published. Either include all columns in the published article, or alter the constraint to remove columns that are not published. 21669 16 Column [%s] cannot be published because it uses an unsupported d ata type [%s]. View supported data types by querying msdb.dbo.sysdatatypemapping s. 21670 16 Connection to server [%s] failed. 21671 16 Cannot execute the procedure. Administration of a non-SQL Server Publisher must be performed at the associated SQL Server Distributor. Execute t he procedure at the Distributor.

21672 16 The login '%s' has insufficient authorization to execute this co mmand. 21673 16 Test connection to publisher [%s] failed. Verify authentication information. 21674 16 Unable to update the linked server [%s] for the login [%s]. 21675 16 Cannot specify more than %d indexes for a single table. %d inde xes specified. Excess indexes have been ignored. 21676 16 Heterogeneous subscriber '%s' could not add a subscription for h eterogeneous publication '%s' because publication sync method is not 'character' , 'concurrent_c', or 'database snapshot character'. 21677 16 Heterogeneous publisher '%s' cannot be defined as a subscriber. 21678 16 The parameter "%s" can be set to "%s" only when "%s" is set to " %s". 21679 16 Peer-to-peer publications only support a '%s' parameter value of %s. 21680 16 The Distribution Agent was unable to update the cached log seque nce numbers (LSNs) for Originator %s, OriginatorDB %s, OriginatorDBVersion %d, O riginatorPublicationID %d. Stop and restart the Distribution Agent. If the probl em persists, contact Customer Support Services. 21681 16 The current user '%s' does not have a valid linked server login mapping for non-SQL Server Publisher [%s]. Replication connects to the Publishe r through a linked server; use the stored procedure sp_addlinkedsrvlogin to map the user's login to this linked server. 21682 16 Cannot publish table [%s].[%s]. The replication administraive us er requires an explicit SELECT grant, or a SELECT grant through PUBLIC, in order to publish this table. A role-based SELECT grant, if one exists, is not suffici ent. 21683 16 Cannot verify administrator login privileges for Oracle Publishe r %s. Verify connection information and ensure that you can connect to the Publi sher through a tool like SQL*PLUS. 21684 16 The replication administrative user for Oracle Publisher "%s" ha s insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql f or the required permissions. 21685 16 Request '%s' for Oracle schema filter for Oracle publisher '%s' failed. 21686 16 The operation "%s" is not valid. Valid operations are "add", "dr op", and "help". 21687 16 Schema filters are supported only for Oracle Publishers. The Pub lisher "%s" is a "%s" Publisher. 21688 16 The current login '%s' is not in the publication access list (PA L) of any publication at Publisher '%s'. Use a login that is in the PAL, or add this login to the PAL. 21689 16 A NULL @schema value is invalid for add and drop schema filter o perations. 21690 10 The subscriber db cannot be the same as the publisher db when th e subscriber is the same as the publisher 21691 10 sp_mergesubscription_cleanup should be called on the subscriptio n database 21692 16 Failed to script the subscriber stored procedures for article '% s' in publication '%s' 21694 16 %s cannot be null or empty when %s is set to 0 (SQL Server Authe ntication). Specify a login or set security mode to 1 (Windows Authentication). 21695 10 The replication agent job '%s' was not removed because it has a non-standard name; manually remove the job when it is no longer in use. 21696 16 The stored procedure only applies to Oracle Publishers. The Publ isher '%s' is a %s Publisher. 21698 16 The parameter '%s' is no longer supported. 21699 10 Unable to reuse view '%s' because it was not found. Re-creating all system table views. This is an informational message only. No user action is required.

21701 16 Microsoft SQL Server Additive Conflict Resolver 21702 16 Microsoft SQL Server Averaging Conflict Resolver 21703 16 Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver 21704 16 Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver 21705 16 Microsoft SQL Server Download Only Conflict Resolver 21706 16 Microsoft SQL Server Maximum Conflict Resolver 21707 16 Microsoft SQL Server Merge Text Columns Conflict Resolver 21708 16 Microsoft SQL Server Minimum Conflict Resolver 21709 16 Microsoft SQL Server Priority Column Resolver 21710 16 Microsoft SQL Server Subscriber Always Wins Conflict Resolver 21711 16 Microsoft SQL Server Upload Only Conflict Resolver 21712 16 Microsoft SQLServer Stored Procedure Resolver 21715 16 Cannot register the article resolver %s. This can occur if the a ccount under which SQL Server is running does not have access to the distributio n database. Add the class ID and the custom resolver name manually to the MSmerg e_articleresolver table in the distribution database. 21717 16 The article resolver name cannot be an empty string or NULL. Spe cify a valid value for the @article_resolver parameter. 21718 16 For a COM resolver, the @resolver_clsid cannot be an empty strin g or NULL. Specify a valid value for @resolver_clsid. 21719 10 The Subscriber '%s':'%s' was not marked for reinitialization at the Publisher because the subscription is either anonymous or not valid. Verify that valid values were specified for the @subscriber and @subscriber_db paramete rs of sp_reinitmergesubscription. 21720 16 Cannot find a job that matches the ID or name specified in the p arameters @dynamic_snapshot_jobid or @dynamic_snapshot_jobname. Verify the value s specified for those parameters. 21721 10 UserScripts 21722 16 Failed to add an extended trigger for replicating the '%.*ls' ev ent. 21723 16 The value specified for the @pubid parameter of procedure '%s' i s not valid or is NULL. Verify that the Merge Agent is running correctly. Reinit alize the subscription if the problem persists. 21724 10 Cannot add the foreign key %s with the CASCADE option because ta ble %s is published. Add the NOT FOR REPLICATION clause to the foreign key defin ition. 21725 16 Cannot alter the view. An indexed view replicated as a table can not be altered to a nonindexed view. Drop the view from the publication before a ttempting to alter it. 21727 14 Cannot complete the replication operation. The security check fo r the current user is failing. Only members of the sysadmin fixed server role, o r db_owner or db_ddladmin fixed database roles can perform this operation. 21728 16 The article can support logical record level conflict detection only if it uses logical record conflict resolution. 21729 16 The @keep_partition_changes property cannot be set to "true." Th is is because the @publication_compatibility_level property is set to 90RTM or h igher and the @use_partition_groups property is set to "true." Set a lower compa tibility level or set the @use_partition_groups property to "false." 21730 16 Table '%s' can not be replicated because it contains imprecise P rimary Key column, please recreate table without 'persisted' clause and try agai n. 21731 16 Cannot add a constraint or default without an explicit name, bec ause the table is included in a publication that replicates DDL events. Specify a unique name for the constraint and then reissue the DDL statement. 21732 16 Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parame ter '%s'. 21733 16 Cannot open database %s. The upgrade of replication %s could not be performed. Run %s again from the %s database when the %s is accessible. 21734 16 Peer-to-peer publications do not support replicating timestamp c

olumns as varbinary(8). You cannot add an article with this option, nor add or a lter a table to include a timestamp column as varbinary(8). 21735 16 Source object [%s].[%s] is a temporary object and cannot be publ ished. 21736 16 Unable to relocate the article log table to a different tablespa ce. Verify that the replication administrative user login can connect to the Ora cle Publisher using SQL*PLUS. If you can connect, but the problem persists, it m ight be caused by insufficient permissions or insufficient space in the tablespa ce; check for any Oracle error messages. 21737 16 The property '%s' is not valid for '%s' Publishers. 21738 16 The property '%s' is not valid for %s publications. 21739 16 Cannot alter property '%s'. You must first call the stored proce dure sp_articleview to initialize the article; the property can then be altered. 21740 16 Oracle subscriber '%s' not found. Loopback support cannot be ch ecked. 21741 16 Unable to retrieve distributor information from Oracle publisher '%s'. Bi-directional publishing requires Oracle publisher to exist before the O racle subscriber. 21742 16 The Oracle Publisher name is '%s' and the Oracle Subscriber name is '%s'. Bidirectional Oracle publishing requires the Oracle Publisher and Subs criber names to be the same. 21743 16 Unable to retrieve the originator information for the Oracle sub scriber '%s'. 21744 16 Oracle bidirectional publishing requires parameter '%s' to have a value of '%s'. 21745 16 Cannot generate a filter view or procedure. Verify that the valu e specified for the @filter_clause parameter of sp_addarticle can be added to th e WHERE clause of a SELECT statement to produce a valid query. 21746 16 The '%s' character length must not exceed %d. 21747 16 Cannot establish a connection to the Oracle Publisher '%s'. Veri fy connection information and ensure that you can connect to the Publisher throu gh a tool like SQL*PLUS. 21748 16 The article was dropped at the Distributor, but information at t he Publisher '%s' was not dropped. No action is required; the information is cle aned up if the Publisher is dropped. 21749 16 The Publisher was dropped at the Distributor, but information on the Publisher '%s' was not dropped. Connect to the Oracle Publisher with SQL*PL US and drop the replication administrative user. 21750 16 The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table. 21751 16 Cannot publish view %s as a table because it does not have a uni que clustered index. Publish the view as a view, or add a unique clustered index . 21752 16 The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber tha t have updates pending in the queue. 21753 16 The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ens ure your queued subscriptions are properly initialized by running the Snapshot A gent, Distribution Agent, and Queue Reader Agent. 21754 16 Processing has been terminated. The resultset for sp_getqueuedro ws is larger than 16,000, the maximum size that the procedure can return. Run th e Queue Reader Agent to flush the queue at the Subscriber before executing this procedure again. 21755 16 Failed to mark '%s' as a system object. 21756 16 Based on article settings, table %s should have an identity colu mn, but it does not have one. Verify article settings with sp_helparticle and ch ange them if necessary with sp_changearticle. 21757 16 The subscription is read-only. The publication that this subscri ption synchronizes with allows updates at the Subscriber, but a value of 'read-o

nly' was specified for the @update_mode parameter of sp_addsubscription. To allo w updates, you must drop and then re-create the subscription, specifying a diffe rent value for @update_mode. 21758 16 Cannot find a valid Queue Reader Agent ID for the subscription t o Publisher %s, database %s, publication %s. The specified subscription to an up dating Subscriber publication is not initialized. Run the Snapshot Agent, Distri bution Agent, and Queue Reader Agent to initialize the subscription. 21759 16 Cannot add the column '%s' to the table '%s'. The table already contains the maximum number of columns allowed for an article in a merge publica tion (246 columns). 21760 11 Cannot execute the replication script in the 'master' database; the current session will be terminated. The script must be executed in the distr ibution database, and the master database cannot serve as the distribution datab ase. 21761 20 Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of t he script. 21762 10 The distribution database '%s' has a compatibility level of %d, which is different from that of the master database. The two compatibility level s must be the same, so the distribution database level is being changed to %d. T his is an informational message only. No user action is required. 21763 16 Message Queuing Service is not running. Start this service and r etry the operation. 21764 16 Cannot create the publication. Specifying a value of 'msmq' for the parameter @queue_type is supported only on Microsoft Windows NT platforms. S pecify a value of 'sql' for this parameter. 21765 10 The column msrepl_tran_version has been predefined and allows NU LLs. This column will be dropped and recreated to not allow NULLs for updating s ubscribers. 21766 16 Table %s contains an identity column that is marked as Not For R eplication, but the @identitymanagementoption parameter of sp_addarticle is set to 'none'. To support immediate updating subscriptions, specify a value of 'manu al' or 'auto' for @identitymanagementoption. 21767 10 Warning: The parameter '%s' is obsolete and is available only fo r backwards compatibility. It will not be available in future releases. Instead of this parameter, use the parameter '%s'. 21768 16 When executing sp_adddistributor for a remote Distributor, you m ust use a password. The password specified for the @password parameter must be t he same when the procedure is executed at the Publisher and at the Distributor. 21769 10 Custom data type mappings are not supported. You must validate t he correctness of the mapping. If mappings are not compatible, errors will likel y occur when moving data from the Publisher to the Subscriber. 21770 10 Data type mapping from '%s' to '%s' does not exist. Review sour ce and destination data type, length, precision, scale, and nullability. Query t he system table msdb.dbo.sysdatatypemappings for a list of supported mappings. 21771 16 %s is not within the supported range of %d and %d. 21772 16 Property "%s" requires the parameters @force_invalidate_snapshot and @force_reinit_subscription to be set to "true". 21773 10 The distribution database '%s' cannot be opened due to inaccessi ble files. The database will be dropped, but distribution database cleanup tasks will not occur. Check the database and server error logs for more information a bout why the database files cannot be accessed. 21774 16 This procedure is supported only for non-SQL Server Publishers. The Publisher '%s', on which you are executing the procedure, is a SQL Server Pu blisher. 21775 16 Failed to generate column bitmap for article '%s'. 21776 16 Failed to generate published column bitmap for article '%s'. 21777 16 Failed to generate article view name for article '%s'. 21778 16 Cannot add Publisher objects to the Oracle Publisher for article '%s'. Verify connection information and ensure that you can connect to the Publ

isher through a tool like SQL*PLUS. Ensure that the replication administrative u ser schema has the required permissions. 21779 10 Cannot use the specified data type mapping. The matching destina tion data type for source type %s cannot be found. Query the system table msdb.d bo.sysdatatypemappings for a list of supported mappings. Verify that the length, precision, scale, and nullability of the source type are correct. 21780 16 The non-SQL Server Publisher is missing one or more %s objects. Drop and re-create the Publisher and the replication administrative user schema. 21781 16 Unable to retrieve heterogeneous metadata. Verify connection in formation 21782 16 Cannot add primary key column '%s' to article '%s'. If the Publi sher is a non-SQL Server Publisher, the primary key could have violated SQL Serv er limits for number and length of columns. For more information, see errors ret urned by sp_addarticle. 21783 16 Cannot add the Publisher triggers and the article log table to t he Oracle Publisher for the article '%s'. Verify connection information and ensu re that you can connect to the Publisher through a tool like SQL*PLUS. Ensure th at the replication administrative user schema has the required permissions. 21784 16 You must specify a non-NULL value for the @rowfilter parameter. 21785 16 Failure to query Oracle XactSet Job attributes for publisher '%s '. 21786 16 Failure to refresh Oracle XactSet Job for publisher '%s'. 21787 16 Failure to query Oracle Xact batching enabled flag for publisher '%s'. 21788 16 Invalid parameter passed to sp_IHSetXactBatching. The bit flag to enable/disable Xact batching must be 0 or 1. 21789 16 Failure to set the Oracle Xact batching enabled flag for publish er '%s'. 21790 16 Cannot publish the table '%s.%s' from the Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema ha s the required permissions. 21791 16 The table '%s.%s' already appears in a transactional publication on Oracle Gateway Publisher '%s'. When using the Oracle Gateway option, a table published using transactional replication can only be included in one publicati on. To publish this table in more than one publication, you must reconfigure the Oracle Publisher to use the Oracle Complete option. 21792 16 The table '%s.%s' already appears in the transactional publicati on '%s' on Publisher '%s'. The Oracle Gateway publishing option (the default) al lows a table to be included as an article in any number of snapshot publications , but only in one transactional publication. To publish a table in more than one transactional publication, use the Oracle Complete publishing option. To change publishing options, you must drop and reconfigure the Publisher. 21793 16 Non-SQL Server Publishers are supported only in the Enterprise a nd Developer editions of SQL Server. The edition of this instance is %s. 21794 16 The value specified for the @propertyname parameter is not valid . Use one of the following values: %s. 21795 16 The value specified for property %s is not valid. Use one of the following values: %s. 21796 16 The property "xactsetjobinterval" must be assigned a value great er than or equal to 0. 21797 16 Cannot create the agent job. '%s' must be a valid Windows login in the form : 'MACHINE\Login' or 'DOMAIN\Login'. See the documentation for '%s'. 21798 16 Cannot execute the replication administrative procedure. The '%s ' agent job must be added through '%s' before continuing. See the documentation for '%s'. 21799 16 The %s agent for Publisher (%s), database (%s), publication (%s) cannnot be found. Create the agent with the appropriate procedure: sp_addpublic ation_snapshot, sp_addlogreader_agent, or sp_addqreader_agent. 21800 16 The common generation watermark is invalid at this replica since

it does not exist or metadata for changes not yet propagated may have been clea ned up. 21801 16 The stored procedure sp_createagentparameter failed to add one o r more parameters to the system table msdb.dbo.MSagentparameterlist. Check for a ny errors returned by sp_createagentparameter and errors returned by SQL Server during execution of sp_createagentparameter. 21802 16 The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The va lue must be an integer less than or equal to '%d'. Verify that replication is in stalled properly. 21803 16 Cannot update agent parameter metadata. Replication could not in sert parameter '%s' into table '%s'. Verify that replication is properly install ed. Check errors returned by SQL Server during execution of sp_createagentparame ter. 21804 16 The value '%d' specified for the @agent_type parameter of sp_get agentparameterlist is not valid. Specify a valid value of 1, 2, 3, 4, or 9. 21805 16 The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The va lue must be an integer. Verify that replication is installed properly and that s p_add_agent_parameter is invoked with a valid value. 21806 16 The agent profile creation process cannot validate the specified agent parameter value: the profile_id %d does not exist or it does not support the parameter %s. The value must be an integer. Verify that replication is insta lled properly and that sp_add_agent_parameter is invoked with a valid value. 21807 16 For a .NET Assembly Business Logic Handler, the @resolver_clsid must be specified as NULL. 21808 16 For a .NET Assembly Business Logic Handler, the @resolver_info m ust contain the class name in '%s' that implements the Microsoft.SqlServer.Repli cation.BusinessLogicSupport.BusinessLogicModule interface. 21809 10 DDL replication is not enabled for database '%ls' because its co mpatibility level is less than 80. 21810 16 Identity column can only be added to a published table with 'Not For Replication' clause 21811 16 Cannot drop the column '%s' because it is used by replication: i t is referenced in a filter or view by article '%s'. To drop the column, you mus t first remove the filter from the article. 21812 16 Cannot perform "Disable Trigger All" on table %s because it belo ngs to a publication that supports updatable subscriptions (replication adds tri ggers to tables for these types of publications). You may, however, disable user triggers individually. Specify an individual user trigger name to disable. 21813 16 Can not disable trigger %s on table %s because it is required by updatable publication. 21814 16 DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, '%s', '%s' "and try again 21815 16 Can not alter replicated object '%s' to 'with encrypted'. 21816 16 An invalid value was specified for parameter '%s'. The value mus t be '%s' when changing this property. 21817 16 The property '%s' is only valid for push subscriptions. 21818 10 The parameters for security, batch size, and scheduling have bee n deprecated and should no longer be used. For more information, see the "sp_add subscriber" documentation. 21819 16 Cannot change the property '%s' . This property is only valid fo r subscriptions that allow updating at the Subscriber. The subscription against which the procedure was called does not allow updates at the Subscriber. 21820 16 Cannot write to the script file in the snapshot folder at the Di stributor (%ls). Ensure that there is enough disk space available. Also ensure t hat the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories. 21821 16 Specify one and only one of the parameters - %s or %s.

21822 16 Cannot perform %s on %s as entry already exists. 21823 16 Cannot perform %s on %s as entry does not exist. 21824 16 Can not add constraints to multiple columns because table %s is published but column %s is not in all active partitions, please use separate DDL statement. 21825 16 Can not drop constraints in the same DDL statement which drops c olumns from table %s because the table is published, please use separate DDL sta tement. 21826 16 The property '%s' is valid only for %s subscriptions. Use '%s' f or %s subscriptions. 21827 16 The %s parameters have been deprecated and should no longer be u sed. For more information, see the '%s' documentation. 21828 16 The proxy account for jobstep_uid (%s) could not be found. 21830 16 You cannot specify schema_option 0x4 (script identity as identit y rather than the base data type) for article '%s'. The value specified for the parameter @identityrangemanagementoption is NONE. To replicate identity as ident ity, the value must be MANUAL or AUTO for publications that do not support queue d updating subscriptions. 21831 16 The %s already exists. Use '%s' to change any settings/propertie s. 21832 16 Only members of the sysadmin fixed server role can perform this operation without specifying %s. 21833 16 An error occurred when creating a trace event at Oracle publishe r '%s'. The trace event could not be posted. 21834 16 The primary key for '%s.%s' has %d columns. SQL Server supports a maximum of %d columns. Redefine the primary key so that it has no more than th e maximum number of columns. 21835 16 The index for the primary key '%s.%s' is at least %d bytes. SQL Server supports a maximum key length of %d bytes. Reduce the number of columns i n the primary key or redefine the columns to use smaller data types. 21836 16 The distribution agent must be run in single subscription stream mode prior to resetting the subscription xact_seqno. 21837 16 A replication agent job (%s) for this subscription already exist s. 21838 16 The %s parameter(s) have been deprecated from this procedure. Th e value(s) should now be specified when calling '%s'. 21839 16 Article '%s' can not support schema_option 0x20 or 0x2000000000 because it contains computed column, check/default constraint or primary key whi ch is based on CLR type column, change @schema_option setting and try again. 21840 16 Can not add CLR type based computed column or check constraint t o table '%s' because article '%s' supports schema_option 0x20. 21841 10 DDL replication is forcing reinitialization because either publi cation'%s' uses character mode bcp, or timestamp/identity column is being replic ated as base type only for article '%s'. 21842 16 %s can only be specified/changed for heterogeneous publications when %s is set to %s. 21843 16 Article '%s' can not be added, an indexed view published as 'ind exed view logbased' and a stored procedure in either form of 'proc exec' can not be published if their common base table is also published. 21844 16 Can not alter XML, CLR type or MAX type column because table is published and article '%s' supports the schema option to map this to a base colu mn type. 21845 16 Can not alter procedure '%s' to depend on an indexed view publis hed as 'indexed view logbased' or a base table because the indexed view depends on this table as well. 21846 16 Cannot find a distribution agent job for the specified transacti onal or snapshot push subscription. 21847 16 Cannot find a merge agent job for the specified merge push subsc ription. 21848 16 The specified pull subscription is not configured with a synchro

nization agent job. 21850 16 The property "%s" cannot be changed to "%s" after the value has already been set to "%s". 21851 16 Peer-to-peer publications only support a "%s" value of %s. Artic le "%s" currently has a "%s" value of %s. This value must be changed to continue . 21852 16 Peer-to-peer publications do not support %s. Article "%s" curren tly has %s. This must be changed to continue. 21853 10 Warning: The "%s" property for %s "%s" has been changed to "%s" because it is required by %s. 21854 10 Could not add new article to publication '%s' because of active schema change activities or a snapshot is being generated. 21855 16 The login %s provided in sp_link_publication is not mapped to an y user in publishing database %s. 21856 16 For a .NET Assembly Business Logic Handler, the .NET Assembly na me should be the name of a valid assembly in '%s' that contains the class that i mplements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogic Module interface. Check the registration of the business logic handler to make s ure the .NET Assembly name was specified correctly. 21857 10 Forcing re-initialization for article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or res tore process, please re-create the index and re-sync your data. 21858 16 Snapshot can not process article '%s' in publication '%s', the c lustered index on indexed view '%s' may have been dropped by upgrade or restore process, please re-create the index and re-run snapshot. 21859 16 Cannot change subscription property '%s' because there is no ent ry for this subscription in the MSsubscription_properties table. Call sp_addmerg epullsubscription_agent before changing this property. 21860 10 Table '%s' in database '%s' is subscribing to transactional queu ed publication and published for merge for uploading changes, this may cause non -convergence between transactional publisher and subscriber. 21861 16 The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated. 21862 16 FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or 'database snapshot ch aracter'. 21863 16 Cannot add the SPARSE property to a column for the article '%s' because merge replication does not support sparse columns. 21864 16 Cannot publish the article '%s' or add the COLUMN_SET attribute set to its base table '%s' because replication does not support column sets. 21865 16 The '%s' publication property must be either 'true' or 'false'. 21866 16 The publication property '%s' can only be set to '%s' when the p ublication property '%s' is set to '%s'. 21867 16 ALTER TABLE SWITCH statement failed. The table '%s' belongs to a publication which does not allow switching of partitions 21868 16 ALTER TABLE SWITCH statement failed. The statement is not allowe d because one or more of the tables in this statement is an article with a diffe rent destination table or owner. 21869 16 Cannot add filter between proposed parent article '%s' and propo sed child article '%s' since this would introduce a cycle in the filter relation ships. The proposed parent is already being filtered by the child. 21870 16 Distribution agent encountered a deadlock while applying command s in SubscriptionStreams mode. Spid %u waiting on lock (type '%s', mode '%s') f or index '%s' of table '%s'. 21871 16 Publisher %s of database %s has not been redirected. 21872 16 The availability group associated with Virtual Network Name '%s' has no replicas. 21873 16 You are not authorized to run the stored procedure %s. 21874 16 The stored procedure %s must be run from a distirbution database . The current database %s is not a distribution database.

21875 16 The parameters @original_publisher and @publisher_db to stored p rocedure '%s' may not be NULL. 21876 16 The distributor '%s' is not the distributor for original publish er '%s' and publisher database '%s'. 21877 16 The original publisher '%s' for database '%s' is not a remote se rver for the distributor. 21878 16 Unable to create a linked server to use in contacting the remote publisher for original publisher '%s', publisher database '%s', and redirected publisher '%s'. The command '%s' failed with Error '%d', Error Message '%s'. 21879 16 Unable to query the redirected server '%s' for original publishe r '%s' and publisher database '%s' to determine the name of the remote server; E rror %d, Error message '%s'. 21880 16 The virtual network name '%s' has been used to identify the redi rected publisher for original publisher '%s' and database '%s'. The availability group associated with this virtual network name, however, does not include the publisher database. 21881 16 The database '%s' at the redirected publisher '%s' for original publisher '%s' and database '%s' is either not synchronized or is not active. 21882 16 The database '%s' at the redirected publisher '%s' for original publisher '%s' and database '%s' belongs to a HADRon availability group and must be redirected to its associated HADRon Virtual Network Name. 21883 16 The query at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', error message '%s'. 21884 16 The query at the redirected publisher '%s' to determine the heal th of the availability group associated with publisher database '%s' failed with error '%d', error message '%s'. 21885 16 The return code of the failed call was '%d'. 21886 16 The remote server name returned was null. 21887 16 The query at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', error message '%s'. 21888 16 The SQL Server instance '%s' is not configured to support replic ation. To enable the SQL Server instance to serve as a replication publisher, co nfigure the instance for replication. 21889 16 The SQL Server instance '%s' is not a replication publisher. Run sp_adddistributor on SQL Server instance '%s' with distributor '%s' in order to enable the instance to host the publishing database '%s'. Make certain to speci fy the same login and password as that used for the original publisher. 21890 16 The SQL Server instance '%s' with distributor '%s' and distribut ion database '%s' cannot be used with publisher database '%s'. Reconfigure the p ublisher to make use of distributor '%s' and distribution database '%s. 21891 16 The publisher '%s' with distributor '%s' is not known as a publi sher at distributor '%s'. Run sp_adddistpublisher at distributor '%s' to enable the remote server to host the publishing database '%s'. 21892 16 Unable to query sys.availability_replicas at the availability gr oup primary associated with virtual network name '%s' for the server names of th e member replicas: error = %d, error message = %s.', 21893 16 The subscribers ( %s ) of original publisher '%s' do not appear as remote servers at redirected publisher '%s'. Run sp_addlinkedserver at the re directed publisher to add these subscribers as remote servers. 21894 16 Unable to configure a linked server to query replica host server '%s': return code = %d. 21895 16 One or more publisher validation errors were encountered for rep lica host '%s'. 21896 16 The query at the redirected publisher '%s' to determine whether the SQL Server instance is a replication publisher failed with error '%d', error message '%s'. 21897 16 The query to determine whether the local distributor '%s' is the distributor for remote publisher '%s' failed with error '%d', error message '%s

'. 21898 16 The publisher '%s' uses distribution database '%s' and not '%s' which is required in order to host the publishing database '%s'. Run sp_changedi stpublisher at distributor '%s' to change the distribution database used by the publisher to '%s'. 21899 16 The query at the redirected publisher '%s' to determine whether there were sysserver entries for the subscribers of the original publisher '%s' failed with error '%d', error message '%s'. 22101 16 The value supplied for the change_columns argument of CHANGE_TRA CKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask retur ned by the CHANGETABLE(CHANGES ...) function. 22102 16 The arguments supplied are not valid for the CHANGES option of t he CHANGETABLE function. 22103 16 The arguments supplied are not valid for the VERSION option of t he CHANGETABLE function. 22104 16 A table returned by the CHANGETABLE function must be aliased. 22105 16 Change tracking is not enabled on table '%.*ls'. 22106 16 The CHANGETABLE function does not support remote data sources. 22107 16 Object '%.*ls' is of a data type that is not supported by the CH ANGETABLE function. The object must be a user-defined table. 22108 16 The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SE LECT statement. 22109 16 The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clau se must be of type varbinary data type with a maximum length of 128. 22110 16 The number of columns specified in the CHANGETABLE(VERSION ...) function does not match the number of primary key columns for table '%.*ls'. 22111 16 The column '%.*ls' specified in the CHANGETABLE(VERSION ...) fun ction is not part of the primary key for table '%.*ls'. 22112 16 Each primary key column must be specified once in the CHANGETABL E(VERSION ...) function. The column '%.*ls' is specified more than once. 22113 16 %S_MSG is not allowed because the table is being tracked for cha nge tracking. 22114 16 Change tracking options for ALTER DATABASE cannot be combined wi th other ALTER DATABASE options. 22115 16 Change tracking is enabled for one or more tables in database '% .*ls'. Disable change tracking on each table before disabling it for the databas e. Use the sys.change_tracking_tables catalog view to obtain a list of tables fo r which change tracking is enabled. 22116 16 Change tracking is not supported by this edition of SQL Server. 22117 16 For databases that are members of a secondary availability repli ca, change tracking is not supported. Run change tracking queries on the databas es in the primary availability replica. 22500 16 Unexpected 22501 16 All articles in the publication passed data validation (rowcount and checksum). 22502 16 Not All articles in the publication passed data validation (rowc ount only) 22503 16 Initializing. 22504 16 Applying the snapshot to the Subscriber. 22505 16 The merge completed with no data changes processed. 22506 16 No data needed to be merged. 22507 16 Uploading data changes to the Publisher. 22508 16 Downloading data changes to the Subscriber. 22509 16 Retrieving subscription information. 22510 16 Retrieving publication information. 22511 16 The merge completed successfully. 22512 16 Cannot use partition groups with unfiltered publications. Set "u se_partition_groups" to "false" using sp_changemergepublication. 22513 16 Cannot use partition groups because the join filter between the following articles contains one or more functions: "%s" and "%s".

22514 16 Cannot use partition groups because one or more filters referenc e the following view, which contains functions: "%s". 22515 16 The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the article s in the publication. To use precomputed partitions, ensure that no circular joi n filter relationships exist. 22516 16 The publication "%s" was defined as having dynamic filters, but it does not contain any dynamic filters. 22517 16 The publication was defined as having no dynamic filters, but co ntains one or more dynamic filters. 22518 16 Cannot use column of type image, ntext, xml, CLR type, varchar(m ax), nvarchar(max), or varbinary(max) in a subset or join filter for article: '% s'. 22519 16 Cannot add a logical record relationship between tables "%s" and "%s" because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbina ry(max) column was referenced in the join clause. 22520 10 A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for d etails. 22521 10 Unable to synchronize the row because the row was updated by a d ifferent process outside of replication. 22522 16 Article '%s' cannot be published because it is published in anot her merge publication. An article that has a value of 3 for the @partition_optio ns parameter of sp_addmergearticle (nonoverlapping partitions with a single subs cription per partition) cannot be included in multiple publications or subscript ions, and cannot be republished. To include the article in multiple publications , use sp_changemergearticle to specify a different value for the partition_optio ns property of the existing article. 22523 16 An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Che ck article "%s". 22524 16 Article '%s' is published in another merge publication, with a d ifferent value specified for the @partition_options parameter of sp_addmergearti cle. The specified value must be the same in all merge publications. Either spec ify the same value as the existing article or change the existing article using sp_changemergearticle. 22525 16 The publication "%s" cannot allow multiple subscriptions per par tition if it contains articles using @partition_options = 3. 22526 16 An invalid value was specified for %s. Valid values are 0 (none) , 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscripti ons per partition), and 3 (nonoverlapping partitions with single subscription pe r partition). 22527 16 Invalid value specified for %s. Valid values are 'day', 'days', 'dd', 'year', 'years', 'yy', 'yyyy', 'month', 'months', 'mm', 'week', 'weeks', ' wk', 'hour', 'hours', 'hh', 'minute', 'minutes', 'mi'. 22528 16 Cannot use a retention period unit other than "days" for publica tion "%s" because the compatibility level of the publication is lower than 90. U se sp_changemergepublication to set publication_compatibility_level to 90RTM. 22529 16 Cannot change the retention period unit for publication "%s" bec ause the compatibility level of the publication is lower than 90. Use sp_changem ergepublication to set publication_compatibility_level to 90RTM. 22530 16 Cannot update any column in article "%s" that is used in a logic al record relationship clause. 22531 10 Initialization. 22532 10 Upload of Subscriber changes to the Publisher. 22533 10 Download of Publisher changes to the Subscriber. 22534 16 Character mode publication does not support partitioned tables. 22535 16 For heterogeneous publications, the %s parameters should be spec ified when calling "%s".

22536 16 The %s parameter value cannot be updated or changed for heteroge neous publications. 22537 16 The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher). 22538 16 Only replication jobs or job schedules can be added, modified, d ropped or viewed through replication stored procedures. 22539 16 Use of parameters %s is invalid when parameter %s is set to %s. 22540 16 Cannot change publication "%s" to use sync_mode of "character", because it contains one or more logical record relationships. 22541 16 Cannot add a logical record relationship in publication "%s" bec ause it uses sync_mode of "character" and could have SQL Server Compact Edition subscribers. 22542 16 Invalid value for property @subscriber_upload_options. Valid val ues are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subs criber changes), and 3 (disable_outofpartition_subscriber_changes). 22543 16 When the publication property @allow_partition_realignment is se t to "false", the article property @subscriber_upload_options for all articles i n the publication must be set to disable uploads. 22544 10 Warning: The procedure sp_mergecleanupmetadata has been deprecat ed. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadatarete ntioncleanup every time it runs, so manual cleanup of metadata is not needed. Ig noring passed-in parameters and calling sp_mergemetadataretentioncleanup. 22545 16 Cannot add a logical record relationship in publication "%s" bec ause it allows Web synchronization. 22546 16 Cannot change publication "%s" to allow Web synchronization beca use it contains one or more logical record relationships. 22547 16 A concurrent snapshot is not allowed for snapshot publications. 22548 16 Vertical partitioning is only allowed for log-based articles. 22549 16 A shared distribution agent (%s) already exists for this subscri ption. 22550 16 Cannot drop identity column "%s" from the vertical partition whe n identityrangemanagementoption is set to auto. 22551 16 The type "%s" is invalid. Valid types are "merge", "tran", and " both". 22552 16 A valid value for parameter "@resync_date_str" needs to be provi ded when "@resync_type" is set to 2. 22553 16 The parameter "@resync_type" is set to "%d" but this subscriptio n has never been successfully validated. 22554 16 Cannot change publication "%s" to use the sync_mode of "characte r" because it uses a retention period unit other than "day". Use sp_changemergep ublication to set the retention period unit to "day". 22555 16 Cannot set the retention period unit to a value other than "day" for publication "%s" because it uses the sync_mode of "character" and may have SQL Server Compact Edition subscribers. 22556 16 Invalid value for the property "%s". Valid values are 1 and 0. 22557 16 The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication "%s" to 90RTM. 22558 16 The status of the schema change could not be updated. 22559 16 The status of the schema change must be "active" or "skipped". 22560 16 Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function "%s". 22561 16 The requested operation failed because the publication compatibi lity level is less than 90. Use sp_changemergepublication to set the publication _compatibility_level of publication "%s" to 90RTM. 22562 16 Cannot change the compatibility level of a publication to a valu e lower than the existing value. 22563 16 contains one or more articles that do not upload changes 22564 16 uses ddl replication 22565 16 uses other than day as unit of retention period

22566 16 uses logical records 22567 16 contains one or more articles that use subscription-based or par tition-based filtering 22568 16 contains one or more articles which will not compensate for erro rs 22569 16 contains one or more schema only articles 22570 16 contains one or more articles that use automatic identity range management 22571 16 contains one or more articles that use datatypes new in SQL Serv er 2000 22572 16 contains one or more articles with a timestamp column 22573 16 uses snapshot compression with snapshot_in_defaultfolder set to false 22574 16 contains one or more articles that use vertical partitioning 22575 16 When article property 'published_in_tran_pub' is set to 'true' t hen article property 'upload_options' has to be set to disable uploads. 22576 10 Invalid failover_mode value of %d was specified for [%s].[%s].[% s], setting to 0 [immediate]. 22578 16 Cannot change publication "%s" to disallow use_partition_groups because it contains one or more logical record relationships. When using logical record relationships the publication must set the @use_partition_groups propert y to 'true'. 22579 16 The subscription to publication '%s' was not found but a shared agent does exist. To specify a subscription to a publication that is replicated via a shared agent specify '%s' for the publication name. 22580 16 Cannot publish database '%s' because it is marked as published o n a different server. Before attempting to publish this database, execute sp_rep licationdboption, specifying a value of FALSE for 'publish' and 'merge publish'. 22581 16 Article '%s' cannot be added or modified in publication '%s'. Th e replication of FILESTREAM columns is not supported for publications that have a 'sync_mode' of 1 (character mode). Specify a 'sync_mode' of 0 (native mode) fo r the publication by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replica ted. 22582 16 Article '%s' cannot be added or modified in publication '%s'. Th e replication of FILESTREAM columns is not supported for publications that have a 'publication_compatibility_level' of less than "90RTM" (SQL Server 2005). Spec ify a 'publication_compatibility_level' greater than or equal to "90RTM" by usin g sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated. 22583 16 Article '%s' cannot be added or modified in publication '%s'. Th e replication of FILESTREAM columns is not supported for articles that have a 's chema_option' set to 0x20000000. This converts large object data types to data t ypes that are supported on earlier versions of Microsoft SQL Server. Remove this 'schema_option' setting by using sp_addmergepublication or sp_changemergepublic ation, or partition the article vertically so that the FILESTREAM column is not replicated. 22584 10 Warning: Values of some of the flags specified in the 'schema_op tion' property are not compatible with the publication's compatibility level. Th e modified schema_option value of '%s' will be used instead. 22585 10 The schema option to script out the FILESTREAM attribute on varb inary(max) columns has been enabled for article '%s'. Enabling this option after the article is created can cause replication to fail when the data in a FILESTR EAM column exceeds 2GB and there is a conflict during replication. If you want F ILESTREAM data to be replicated, drop and re-create the article, and specify the appropriate schema option when you re-create the article. 22586 16 Column '%s' cannot be added or modified in article '%s' of publi cation '%s'. The DDL operatoin on hierarchyid and FILESTREAM columns is not supp orted for publications that have a 'sync_mode' of 1 (character mode) or with a l ower than 90RTM backward compatibility level.

22801 16 Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynami c management view. 22802 16 Starting the Change Data Capture Cleanup Agent job using low wat ermark %s. 22803 16 Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management vie w. 22804 16 Change Data Capture cannot proceed with the job-related action b ecause transactional replication is enabled on database %s but Distributor infor mation cannot be retrieved to determine the state of the logreader agent. Make t he Distributor database available, or disable distribution. 22805 10 For more information, query the sys.dm_cdc_errors dynamic manage ment view. 22806 16 The originator ID '%s' is not valid. You must specify a non-zero ID that has never been used in the topology. 22807 16 The publication property '%s' cannot be modified because the pee r-to-peer publication '%s' is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection. 22808 16 Cannot execute procedure '%s'. Publication '%s' must be enabled for peer-to-peer replication before you execute this procedure. To enable the pu blication for peer-to-peer replication, use sp_changepublication. 22809 10 The existing conflict table '%s' was dropped. 22810 16 The @action parameter value is not valid. Valid values are 'enab le' and 'disable'. 22811 16 The roundtrip time-out must be greater than 0. 22812 10 The roundtrip '%s' finished with timeout: %d seconds. 22813 10 The topology contains peer node versions that do not support con flict detection. To use conflict detection, ensure that all nodes in the topolog y are SQL Server 2008 or later versions. 22814 10 The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology. 22815 10 A conflict of type '%s' was detected at peer %d between peer %d (incoming), transaction id %s and peer %d (on disk), transaction id %s 22816 16 The qualified table name '%s' is too long to be enabled for peer -to-peer conflict detection. 22817 10 %s has %s. 22818 10 A delete-delete conflict was detected and resolved. The row coul d not be deleted from the peer since the row does not exist. The incoming delete was skipped. 22819 10 A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming de lete was skipped by peer %d. The conflict has to be resolved manually to guarant ee data convergence between the peers. For steps on how to resolve the conflict refer to BOL. 22820 10 A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d. 22821 10 An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d . 22822 10 An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d . 22823 10 An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipp ed. Check the priority of the destination peer and run data validation to ensure the delete conflict did not result in data non-convergence. 22824 10 An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d

. 22825 10 An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d . 22827 16 Peer-to-peer conflict detection alert 22828 16 The publication '%s' was already %s for peer-to-peer conflict de tection. 22829 16 The command %s failed. The values specified for the @ins_cmd, @d el_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d. 22830 16 Could not update the metadata that indicates database %s is enab led for Change Data Capture. The failure occurred when executing the command '%s '. The error returned was %d: '%s'. Use the action and error to determine the ca use of the failure and resubmit the request. 22831 16 Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine th e cause of the failure and resubmit the request. 22832 16 Could not update the metadata that indicates table %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 22833 16 Could not update the metadata that indicates table %s is not ena bled for Change Data Capture. The failure occurred when executing the command '% s'. The error returned was %d: '%s'. Use the action and error to determine the c ause of the failure and resubmit the request. 22834 16 Could not modify the the verbose logging status for table %s. Th e failure occurred when executing the command '%s'. The error returned was %d: ' %s'. Use the action and error to determine the cause of the failure and resubmit the request. 22835 16 Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing t he command '%s'. The error returned was %d: '%s'. Use the action and error to de termine the cause of the failure and resubmit the request. 22836 16 Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to dete rmine the cause of the failure and resubmit the request. 22837 16 Could not delete table entries or drop objects associated with c apture instance '%s'. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 22838 16 All columns of a CDC unique index must be defined as NOT NULL. I ndex '%s' selected as the CDC unique index for source table '%s.%s' does not mee t this requirement. Define all columns of the selected index as NOT NULL or sele ct another unique index as the CDC index and resubmit the request. 22840 16 The application lock request '%s' needed to modify Change Data C apture metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 = canceled; -3 = deadlock victim; -999 validation or other call er ror. Examine the error cause and resbmit the request. 22841 16 Could not upgrade the metadata for database '%s' that is enabled for Change Data Capture. The failure occurred when executing the action '%s'. T he error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 22842 16 ALTER TABLE SWITCH statement failed because the partitioned dest ination table is enabled for Change Data Capture and does not have @allow_partit ion_switch set to 1. 22843 16 ALTER TABLE SWITCH statement failed because the partitioned sour ce table is enabled for Change Data Capture and does not have @allow_partition_s witch set to 1.

22844 16 The '%s' option must be either 1 or 0. 22850 16 The threshold value specified for the Change Data Capture cleanu p process must be greater than 0. When creating or modifying the cleanup job, sp ecify a positive threshold value. If this error is encountered when executing th e sys.sp_cdc_cleanup_change_table stored procedure, reset the threshold value as sociated with the job to a non-negative value by using the sp_cdc_change_job sto red procedure. 22851 16 Could not update cdc.change_tables to indicate a change in the l ow water mark for database %s. 22852 10 Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the requ est. 22853 10 Could not delete obsolete entries in the cdc.lsn_time_mapping ta ble for database %s. The failure occurred when executing the command '%s'. The e rror returned was %d: '%s'. Use the action and error to determine the cause of t he failure and resubmit the request. 22854 16 Can not enable Change Data Capture on table '%s' or add ColumnSe t column to it because CDC does not support ColumnSet. 22855 10 Warning: The @allow_partition_switch parameter is set to 1. Chan ge data capture will not track changes introduced in the table resulting from a partition switch which will cause data inconsistency when changes are consumed. Refer to books online for more information about partition switching behavior wh en using Change Data Capture. 22856 10 Warning: The @allow_partition_switch parameter is set to 0. ALTE R TABLE ... SWITCH PARTITION statement will be disallowed on this partitioned ta ble. Refer to books online for more information about partition switching behavi or when using Change Data Capture. 22857 10 Warning: The @allow_partition_switch parameter must be 1 for tab les that are not partitioned. The explicit setting of the parameter to 0 was ign ored. Refer to books online for more information about partition switching behav ior when using Change Data Capture. 22858 16 Unable to add entries to the Change Data Capture LSN time mappin g table to reflect dml changes applied to the tracked tables. Refer to previous errors in the current session to identify the cause and correct any associated p roblems. 22859 16 Log Scan process failed in processing log records. Refer to prev ious errors in the current session to identify the cause and correct any associa ted problems. 22860 16 Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any as sociated problems. 22861 10 Unable to upgrade database '%s'. Error '%d' was raised: '%s'. Us e the reported error to determine the cause of the failure and then execute sys. sp_cdc_vupgrade in the database context to rerun upgrade. 22862 16 The database snapshot '%s' does not exist. Correct the parameter value and resubmit the request. 22863 16 Failed to insert rows into Change Data Capture change tables. Re fer to previous errors in the current session to identify the cause and correct any associated problems. 22864 16 The call to sp_MScdc_capture_job by the Capture Job for database '%s' failed. Look at previous errors for the cause of the failure. 22865 16 The number of columns in the index '%s', used as the unique row identifier to support net changes for table '%s'.'%s', exceeds the limit of 14 c olumns. Set the parameter @supports_net_changes to 0 or use the @index_name para meter to identify a unique index with fewer than 15 columns as the unique row id entifier and resubmit the request. 22901 16 The database '%s' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on

the databases enabled for Change Data Capture, query the is_cdc_enabled column i n the sys.databases catalog view. 22902 16 Caller is not authorized to initiate the requested action. Sysad min privileges are required. 22903 16 Another connection is already running 'sp_replcmds' for Change D ata Capture in the current database. 22904 16 Caller is not authorized to initiate the requested action. DBO p rivileges are required. 22905 10 Database '%s' is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view. 22906 16 The database '%s' cannot be enabled for Change Data Capture beca use a database user named 'cdc' or a schema named 'cdc' already exists in the cu rrent database. These objects are required exclusively by Change Data Capture. D rop or rename the user or schema and retry the operation. 22907 16 Parameter @role_name cannot be empty. Specify a value for @role_ name and retry the operation. Supply null as the value if no role is to be used to gate access to captured change data. 22908 16 Could not create the Change Data Capture objects in database '%s '. Refer to previous errors in the current session to identify the cause and cor rect any associated problems. 22909 16 Failed to cleanup the cdc.lsn_time_mapping table in database '%s ' when the last database table enabled for Change Data Capture was disabled. Ref er to previous errors in the current session to identify the cause and correct a ny associated problems. 22910 16 The cleanup request for database '%s' failed. The database is n ot enabled for Change Data Capture. 22911 16 The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same database. When Change Data Capture and transactional replication are both enabl ed on a database, use the logreader agent to extract the log changes. 22913 16 Could not drop the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and corre ct any associated problems. 22914 16 Only members of the sysadmin or db_owner or db_ddladmin roles ca n perform this operation when Change Data Capture is enabled for a database. 22916 16 Could not grant SELECT permission for the change enumeration fun ctions for capture instance '%s' and source table '%s.%s' for the specified role . Refer to previous errors in the current session to identify the cause and corr ect any associated problems. 22918 16 One or more columns in the list of included columns was not a ca ptured column of the change table %s. 22919 16 One or more columns in the list of columns needing update flags was not a captured column of the change table %s. 22920 16 The named capture instance %s does not exist for database %s. 22921 16 Unable to generate scripts for all capture instances that the ca ller is authorized to access. To generate all such scripts, the parameters @colu mn_list and @update_flag_list must both be null or empty.' 22923 16 Could not compute the new low endpoint for database '%s' from re tention %d. Refer to previous errors in the current session to identify the caus e and correct any associated problems. 22924 16 Could not clean up change tables for database '%s'. A failure oc curred when attempting to clean up the database change tables based upon the cur rent retention time. Refer to previous errors in the current session to identify the cause and correct any associated problems. 22925 16 The number of columns captured by capture instance '%s' exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to spec ify a subset of the columns less than or equal to the maximum allowed and resubm it the request.

22926 16 Could not create a capture instance because the capture instance name '%s' already exists in the current database. Specify an explicit unique na me for the parameter @capture_instance. 22927 16 Capture instance name '%s' exceeds the length limit of 100 chara cters. Specify a name that satisfies the length constraint. 22928 16 Index name '%s' is not an index for table '%s.%s'. Specify a val id index name for the table. 22929 16 Index '%s' must be either a primary key or a unique index for ta ble '%s.%s'. Specify an index that meets at least one of these requirements. 22930 16 Could not locate '%s' as a column of source table '%s.%s'. Speci fy a valid column name. 22931 16 Source table '%s.%s' does not exist in the current database. Ens ure that the correct database context is set. Specify a valid schema and table n ame for the database. 22932 16 Capture instance name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules. 22938 16 Role name '%s' is invalid. Specify a valid name. See the topic ' Identifiers' in SQL Server Books Online for object name rules. 22939 16 The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate unique index has been specified. 22940 16 Could not remove DDL history entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous e rrors in the current session to identify the cause and correct any associated pr oblems. 22941 16 Could not retrieve column information for index '%s' of source t able '%s.%s'. Refer to previous errors in the current session to identify the ca use and correct any associated problems. 22942 16 Columns specified in the captured column list could not be mappe d to columns in source table '%s.%s'. Verify that the columns specified in the p arameter @captured_column_list are delimited properly and match columns in the s ource table. 22943 16 Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key col umns of the source table, or the columns defined for the index specified in the parameter @index_name to the list of captured columns and retry the operation. 22944 16 Could not create the specified database role '%s' for gating acc ess to change table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 22945 16 Could not add column information to the cdc.index_columns system table for the specified index for source table '%s.%s. Refer to previous errors in the current session to identify the cause and correct any associated problem s. 22946 16 Could not add column information to the cdc.captured_columns sys tem table for source table '%s.%s'. Refer to previous errors in the current sess ion to identify the cause and correct any associated problems. 22947 16 Could not create the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identif y the cause and correct any associated problems. 22948 16 Could not create the change enumeration functions for capture in stance '%s' and source table '%s.%s'. Refer to previous errors in the current se ssion to identify the cause and correct any associated problems. 22949 16 Could not update the Change Data Capture metadata for capture in stance '%s' and source table '%s.%s'. Refer to previous errors in the current se ssion to identify the cause and correct any associated problems. 22950 16 Could not remove index column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated p roblems. 22951 16 Could not remove captured column entries in the Change Data Capt

ure metadata for capture instance '%s' and source table '%s.%s'. Refer to previo us errors in the current session to identify the cause and correct any associate d problems. 22952 16 Could not drop Change Data Capture objects created for capture i nstance '%s' and source table '%s.%s'. Refer to previous errors in the current s ession to identify the cause and correct any associated problems. 22953 16 Could not remove Change Data Capture metadata for capture instan ce '%s' and source table '%s.%s'. Refer to previous errors in the current sessio n to identify the cause and correct any associated problems. 22954 16 Could not cleanup change tables for capture instance '%s' using low end point %s. Refer to previous errors in the current session to identify th e cause and correct any associated problems. 22955 16 Could not obtain the maximum LSN for the database from function 'sys.fn_cdc_get_max_lsn'. Refer to previous errors in the current session to ide ntify the cause and correct any associated problems. 22956 16 Could not obtain the minimum LSN of the change table associated with capture instance '%s' from function 'sys.fn_cdc_get_min_lsn'. Refer to prev ious errors in the current session to identify the cause and correct any associa ted problems. 22957 16 LSN %s, specified as the new low end point for the change table associated with capture instance '%s', is not within the Change Data Capture tim eline [%s, %s]. 22958 16 Could not create the function to query for all changes for captu re instance '%s'. Refer to previous errors in the current session to identify th e cause and correct any associated problems. 22959 16 Could not create the function to query for net changes for captu re instance '%s'. Refer to previous errors in the current session to identify th e cause and correct any associated problems. 22960 16 Change data capture instance '%s' has not been enabled for the s ource table '%s.%s'. Use sys.sp_cdc_help_change_data_capture to verify the captu re instance name and retry the operation. 22961 16 Could not create a nonclustered index to support net change trac king for capture instance '%s' and source table '%s.%s'. Refer to previous error s in the current session to identify the cause and correct any associated proble ms. 22962 16 Two capture instances already exist for source table '%s.%s'. A table can have at most two capture instances. If the current tracking options ar e not appropriate, disable change tracking for the obsolete instance by using sy s.sp_cdc_disable_table and retry the operation. 22963 16 Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation. 22964 16 LSN %s, specified as the new low end point for change table clea nup must represent the start_lsn value of a current entry in the cdc.lsn_time_ma pping table. Choose an LSN value that satisfies this requirement. 22965 16 A quoted column in the column list is not properly terminated. V erify that columns are correctly delimited and retry the operation. For more inf ormation, see 'Delimited Identifiers' in Books Online. 22966 16 Could not create table dbo.systranschemas in database '%s'. Refe r to previous errors in the current session to identify the cause and correct an y associated problems. 22967 16 Could not create a clustered index for table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify th e cause and correct any associated problems. 22968 16 Could not create DDL trigger '%s' when enabling Change Data Capt ure for database '%s'. Additional messages in the SQL Server error log and syste m event log may provide more detail. 22970 16 The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0. 22971 16 Could not allocate memory for the log reader history cache. Veri fy that SQL Server has sufficient memory for all operations. Check the physical

and virtual settings on the server and examine memory usage to see if another ap plication is excessively consuming memory. 22972 16 When calling stored procedure [sys].sp_cdc_help_change_data capt ure, if either @source_schema or @source_name is non-null and non-empty, the oth er parameter must also be non-null and non-empty. 22973 16 The specified filegroup '%s' is not a valid filegroup for databa se '%s'. Specify a valid existing filegroup or create the named filegroup, and r etry the operation. 22974 16 Tables contained in the cdc schema cannot be enabled for Change Data Capture. 22975 16 Source table '%s' contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and e nsure that these columns are excluded from the list. 22976 16 Could not alter column '%s' of change table '%s' in response to a data type change in the corresponding column of the source table '%s'. The Cha nge Data Capture meta data for source table '%s' no longer accurately reflects t he source table. Refer to previous errors in the current session to identify the cause and correct any associated problems. 22977 16 Unable to update DDL history information to reflect columns chan ges applied to the tracked table associated with change table '%s'. Refer to pre vious errors in the current session to identify the cause and correct any associ ated problems. 22978 16 Could not update the cdc.captured_columns entry for column '%s' of change table '%s' to reflect a data type change in the corresponding column o f the source table '%s'. Change Data Capture column meta data for table '%s' no longer accurately reflects the source table. Refer to previous errors in the cur rent session to identify the cause and correct any associated problems. 22979 16 The unique index '%s' on table '%s' is used by Change Data Captu re. The constraint using this index cannot be dropped or disabled. 22980 16 The unique index '%s' on table '%s.%s' is disabled and cannot be used as a unique index by Change Data Capture. Enable the index. 22981 16 Object does not exist or access is denied. 22982 16 Could not create internal stored procedures used to populate the change table for capture instance '%s' and source table '%s.%s'. Refer to previ ous errors in the current session to identify the cause and correct any associat ed problems. 22983 16 The unique index '%s' on source table '%s' is used by Change Dat a Capture. To alter or drop the index, you must first disable Change Data Captur e on the table. 22984 16 An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be trans ient. Retry the operation. 22985 16 Change data capture has not been enabled for source table '%s.%s '. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in t he sys.tables catalog view. 22986 16 Could not allocate memory for Change Data Capture population. Ve rify that SQL Server has sufficient memory for all operations. Check the physica l and virtual memory settings on the server and examine memory usage to see if a nother application is consuming excessive memory. 22987 16 Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for a ll operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory . 22988 16 This instance of SQL Server is the %s. Change data capture is on ly available in the Enterprise, Developer, and Enterprise Evaluation editions. 22989 16 Could not enable Change Data Capture for database '%s'. Change d ata capture is not supported on system databases, or on a distribution database.

22990 16 The value specified for the parameter @pollinginterval cannot ex ceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds). 22991 16 The value specified for the parameter @maxtrans must be greater than 0. 22992 16 The specified @job_type, %s, is not supported. The value specifi ed for the parameter @job_type must be N'capture' to indicate a capture job, or N'cleanup' to indicate a cleanup job. 22993 16 The Change Data Capture job table containing job information for database '%s' cannot be found in the msdb system database. Run the stored proce dure 'sys.sp_cdc_add_job' to create the appropriate CDC capture or cleanup job. The stored procedure will create the required job table. 22994 16 The retention value specified for the Change Data Capture cleanu p process must be greater than 0 and less than or equal to 52594800. When creati ng or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this error is encountered when executing the sys.sp_cdc_cl eanup_change_table stored procedure, reset the retention value associated with t he job to a non-negative value less than 52594800 by using the sp_cdc_change_job stored procedure. 22995 16 A value for the parameter @retention cannot be specified when th e job type is 'capture'. Specify NULL for the parameter, or omit the parameter f rom the statement. 22996 16 When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values. 22997 16 The Change Data Capture '%s' job does not exist in the system ta ble 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' to add th e Change Data Capture job. 22998 16 The value specified for the parameter @continuous must be 0 or 1 . 22999 16 The value specified for the parameter @pollinginterval must be n ull or 0 when the stored procedure 'sys.sp_cdc_scan' is not being run in continu ous mode. 23003 17 The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again. 23100 16 Invalid input parameter(s). 23101 16 Access is denied. 23102 16 Item does not exist {ItemId: %ls}. 23103 16 Folder already exists {ItemId: %ls}. 23104 16 Folder does not exist {ItemId: %ls}. 23105 16 Operation violates hierarchical namespace uniqueness. 23106 16 Container is not empty {ItemId: %ls}. 23107 16 Item cannot be copied onto itself. 23108 16 Scoping path does not exist or is invalid. 23109 16 Container does not exist. 23110 16 No more items to enumerate. 23111 16 Item does not exist in the given scope {ItemId: %ls, Scope: %ls} . 23112 16 Transaction not in active state. 23113 16 Item either does not exist or it is not a file-backed one. 23114 16 Sharing violation. 23115 16 Transaction bindtoken must be null when called within the contex t of a transaction. 23116 16 Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls} . 23117 16 File-backed item does not exist {ItemId: %ls}. 23200 16 ItemId of folder '%ls' not found. 23201 16 Share '%ls' does not exist in Catalog. 23202 16 Could not delete Share '%ls' in Catalog. 23203 16 Store item not found in Catalog. 23204 16 Could not delete Store item in Catalog.

23205 16 Store database name not found in Catalog. 23206 16 Could not create share to the ItemPath '%ls'. 23207 16 Could not add Share item for '%ls' in Catalog. 23208 16 ItemPath '%ls' does not exist in Store. 23209 16 Could not update Store state in Catalog. 23210 16 Itempath '%ls' is a file-backed item or within it's sub-tree. 23211 16 Could not start Store Manager. Please look in WinFS UT Log for d etails. 23212 16 Itempath '%ls' is a compound item. 23500 16 Item container does not exist. 23501 16 Owning Item does not exist. 23502 16 NamespaceName is empty or exceeds the maximum length. 23503 16 Invalid Source endpoint type 23504 16 Invalid Target endpoint type 23505 16 A File-backed item must be a compound item type. 23506 16 A File Backed Item may not contain other Items. 23509 16 Source Item does not exist. 23510 16 Item with name already exists in container. 23511 16 New container cannot be a sub-container of item. 23513 16 Item does not exist. 23515 16 Item can not be deleted if it has children 23519 16 Target Item does not exist. 23525 16 Invalid Namespace Name. 23530 16 Operation can not be called inside a un-committable transaction 23536 16 Win32 file handle is open for item 23573 16 Cannot change ContainerId when replacing item. 23579 16 This procedure is reserved and cannot be called. 23587 16 File stream cannot be null. 23588 16 Container ids must be the same. 23996 16 The request could not be performed because of an device I/O erro r. 23997 16 System error occurred {ErrorCode: %d}. 23998 16 Not enough memory available in the system to process the request . 23999 16 Unspecified error(s) occurred. 25002 16 The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is cor rect, and that the Publisher is enabled as a remote Publisher at the Distributor . 25003 16 Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution databa se. 25005 16 It is invalid to drop the default constraint on the rowguid colu mn that is used by merge replication. 25006 16 The new column cannot be added to article '%s' because it has mo re than %d replicated columns. 25007 16 Cannot synchronize the subscription because the schemas of the a rticle at the Publisher and the Subscriber do not match. It is likely that pendi ng schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the changes and synchronize the data. 25008 16 The merge replication views could not be regenerated after perfo rming the data definition language (DDL) operation. 25009 16 Invalid value '%s' specified while executing sp_changemergeartic le on article '%s' for the 'identityrangemanagementoption' property. 25010 16 The constraint is used by merge replication for identity managem ent and cannot be dropped directly. Execute sp_changemergearticle @publication, @article, "identityrangemanagementoption", "none" to disable merge identity mana gement, which will also drop the constraint. 25012 16 Cannot add an identity column since the table is published for m erge replication.

25013 16 Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than '90RT M'. Use sp_repladdcolumn or sp_repldropcolumn. 25014 16 sp_repladdcolumn does not allow adding columns of datatypes that are new to this release. 25015 10 Schema Changes and Bulk Inserts 25016 10 Prepare Dynamic Snapshot 25017 16 Failed to execute the command "%s" through xp_cmdshell. Detailed error information is returned in a result set. 25018 16 Precomputed partitions cannot be used because articles "%s" and "%s" are part of a join filter and at least one of them has a constraint with a CASCADE action defined. 25019 16 The logical record relationship between articles "%s" and "%s" c annot be added because at least one of the articles has a constraint with a CASC ADE action defined. 25020 16 The article cannot be created on table '%s' because it has more than %d columns and column-level tracking is being used. Either reduce the numbe r of columns in the table or change to row-level tracking. 25021 16 Replication stored procedure sp_MSupdategenhistory failed to upd ate the generation '%s'. This generation will be retried in the next merge. 25022 16 The snapshot storage option (@snapshot_storage_option) must be ' file system', or 'database'. 25023 16 Stored procedures containing table-value parameters cannot be pu blished as '[serializable] proc exec' articles. 25024 16 A snapshot storage option of 'database' is incompatible with the use of character mode bcp for snapshot generation. 25025 16 Cannot add a sparse column or a sparse column set because the ta ble is published for merge replication. Merge replication does not support spars e columns. 25026 16 The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution databas e is not properly upgraded. 25601 17 The Extended Event engine is out of memory. 25602 17 The %S_MSG, "%.*ls", encountered a configuration error during in itialization. Object cannot be added to the event session. %ls 25603 17 The %S_MSG, "%.*ls", could not be added. The maximum number of singleton targets has been reached. 25604 17 The Extended Event engine is disabled. 25605 17 The %S_MSG, "%.*ls", could not be added. The maximum number of p ackages has been reached. 25606 17 The Extended Event engine could not be initialized. Check the SQ L Server error log and the Windows event logs for information about possible rel ated problems. 25607 17 The Extended Event engine has been disabled by startup options. Features that depend on Extended Events may fail to start. 25608 17 The Extended Event engine could not allocate record for local th read/fiber. 25623 16 The %S_MSG name, "%.*ls", is invalid, or the object could not be found 25624 16 The constraints of %S_MSG name, "%.*ls", have been violated. The object does not support binding to actions or predicates. Event not added to e vent session. 25625 16 The %S_MSG, "%.*ls", already exists in the event session. Object cannot be added to the event session. 25626 16 The %S_MSG, "%.*ls", was specified multiple times. 25629 16 For %S_MSG, "%.*ls", the customizable attribute, "%ls", does not exist. 25630 16 The predicate expression bound to %S_MSG ,"%.*ls", has mismatchi ng types. 25631 16 The %S_MSG, "%.*ls", already exists. Choose a unique name for t

he event session. 25632 16 The specified buffer size is less than the minimum size. 25633 16 The buffer size specified exceeds the maximum size. 25634 16 The dispatch latency specified is below the minimum size. 25635 16 An attempt was made to add an asynchronous target to a session w ith a maximum memory of 0. For asynchronous targets to be added to a session, th e session must have a maximum memory greater than 0. 25636 16 Source and comparator types of the predicate do not match. 25639 16 The %S_MSG, "%.*ls", exceeds the number of allowable bound actio ns. 25640 16 Maximum event size is smaller than configured event session memo ry. Specify a larger value for maximum event size, or specify 0. 25641 16 For %S_MSG, "%.*ls", the parameter "%ls" passed is invalid. %ls 25642 16 Mandatory customizable attributes are missing for %S_MSG, "%.*ls ". 25643 16 The %S_MSG, "%.*ls", can not be added to an event session that s pecifies no event loss. 25644 16 The %S_MSG, "%.*ls", cannot be bound to the event session. 25646 16 The %S_MSG name, "%.*ls", is invalid. 25647 16 The %S_MSG, "%.*ls", could not be found. Ensure that the object exists and the name is spelled correctly. 25648 16 The %S_MSG, "%.*ls", could not be found. Ensure that the package exists and the name is spelled correctly. 25649 16 Two of the actions/predicates for %S_MSG, "%.*ls", can not coexi st. Please remove one. 25650 16 For %S_MSG, "%.*ls" the customizable attribute, "%ls", was speci fied multiple times. 25651 16 For %S_MSG, "%.*ls", the value specified for customizable attrib ute, "%ls", did not match the expected type, "%ls". 25653 16 The %S_MSG, "%.*ls", does not exist in the event session. Object cannot be dropped from the event session. 25654 16 Insuficient buffer space to copy error message. 25655 16 Internal Extended Event error: invalid message code. 25656 16 Error validating action. %ls 25657 16 Error validating predicate. %ls 25658 16 The %S_MSG name "%.*ls" is not unique. 25664 16 Internal Extended Event error: invalid package ID. 25699 17 The Extended Event engine failed unexpectedly while performing a n operation. 25701 15 Invalid event session name "%.*ls". Temporary event sessions are not allowed. 25702 16 The event session option, "%.*ls", is set more than once. Remove the duplicate session option and re-issue the statement. 25703 16 The event session option, "%.*ls", has an invalid value. Correct the value and re-issue the statement. 25704 16 The event session has already been stopped. 25705 16 The event session has already been started. 25706 16 The %S_MSG, "%.*ls", could not be found. 25707 16 Event session option "%.*ls" cannot be changed while the session is running. Stop the event session before changing this session option. 25708 16 The "%.*ls" specified exceeds the maximum allowed value. Specify a smaller configuration value. 25709 16 One or more event sessions failed to start. Refer to previous er rors in the current session to identify the cause, and correct any associated pr oblems. 25710 16 Event session "%.*ls" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problem s. 25711 16 Failed to parse an event predicate. 25712 16 An invalid comparison operator was specified for an event predic

ate. 25713 16 The value specified for %S_MSG, "%.*ls", %S_MSG, "%.*ls", is inv alid. 25715 16 The predicate on event "%ls" is invalid. Operator '%ls' is not defined for type "%ls", %S_MSG: "%.*ls". 25716 16 The predicate on event, "%.*ls", exceeds the maximum length of % d characters. 25717 16 The operating system returned error %ls while reading from the f ile '%s'. 25718 16 The log file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it. 25719 16 Initial file name and initial offset must be specified as a pair . Please correct the parameters and retry your query. 25720 10 'sys.fn_xe_file_target_read_file' is skipping records from "%.*l s" at offset %I64d. 25721 16 The metadata file name "%s" is invalid. Verify that the file exi sts and that the SQL Server service account has access to it. 25722 16 The offset %I64d is invalid for log file "%s". Specify an offse t that exists in the log file and retry your query. 25723 16 An error occurred while obtaining metadata information from the file "%s". The file may be damaged. 25724 16 Predicate too large for display. 25725 16 An error occurred while trying to flush all running Extended Eve nt sessions. Some events may be lost. 25727 16 The Extended Events session named "%.*ls" has either been stoppe d or dropped and can no longer be accessed. 25728 16 The Extended Events session named "%.*ls" could not be found. Ma ke sure the session exists and is started. 25729 17 The event data stream was disconnected due to an internal error. 25730 10 The Extended Events session named "%.*ls" was modified during th e upgrade and one of the bucketizer targets was excluded from the Extended Event s session. Only one bucketizer target is supported for each Extended Events sess ion. 25732 16 One or more event sessions failed to reconcile their runtime sta tes. Refer to previous errors in the current session to identify the cause, and correct any associated problems. 25733 16 Event session "%.*ls" failed to reconcile its runtime state. Ref er to previous errors in the current session to identify the cause, and correct any associated problems. 25734 16 The file pattern "%s" represents a full path. Use only relative paths with no drive letters. 25735 16 The source option %d is invalid. 25736 16 A damaged buffer was found in file "%s" at offset %I64d, no furt her events will be read from the file. 26010 10 The server could not load the certificate it needs to initiate a n SSL connection. It returned the following error: %#x. Check certificates to ma ke sure they are valid. 26011 16 The server was unable to initialize encryption because of a prob lem with a security library. The security library may be missing. Verify that se curity.dll exists on the system. 26012 16 The server has attempted to initialize SSL encryption when it ha s already been initialized. This indicates a problem with SQL Server. Contact Te chnical Support. 26013 10 The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption. 26014 16 Unable to load user-specified certificate [Cert Hash(sha1) "%hs" ]. The server will not accept a connection. You should verify that the certifica te is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. 26015 16 Unable to load user-specified certificate. Because connection en

cryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See "Configuring Cer tificate for Use by SSL" in Books Online. 26017 10 Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 26018 10 A self-generated certificate was successfully loaded for encrypt ion. 26022 10 Server is listening on [ %hs <%hs> %d]. 26023 16 Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp por t is already in use. 26024 16 Server failed to listen on %hs <%hs> %d. Error: %#x. To proceed, notify your system administrator. 26025 10 HTTP authentication succeeded for user '%.*ls'.%.*ls 26026 14 HTTP authentication failed.%.*ls 26028 10 Server named pipe provider is ready to accept connection on [ %h s ]. 26029 16 Server named pipe provider failed to listen on [ %hs ]. Error: % #x 26034 10 The SQL Server Network Interface library was unable to execute p olite termination due to outstanding connections. It will proceed with immediat e termination. 26035 16 The SQL Server Network Interface library was unable to close soc ket handle due to a closesocket failure under memory pressure. Winsock error cod e: %#x. 26037 10 The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: %# x, state: %d. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication polici es and if the SPN has not been manually registered. 26038 10 The SQL Server Network Interface library could not deregister th e Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d . Administrator should deregister this SPN manually to avoid client authenticati on errors. 26039 16 The SQL Server Network Interface library was unable to load SPN related library. Error: %#x. 26040 17 Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reest ablish listening. 26041 10 Server TCP provider has successfully reestablished listening on port [ %d ]. 26042 17 Server HTTP provider has stopped listening due to a failure. Err or: %#x, state: %d. The server will automatically attempt to reestablish listeni ng. 26043 10 Server HTTP provider has successfully reestablished listening. 26044 17 Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re establish listening. 26045 10 Server named pipe provider has successfully reestablished listen ing on [ %hs ]. 26048 10 Server local connection provider is ready to accept connection o n [ %hs ]. 26049 16 Server local connection provider failed to listen on [ %hs ]. Er ror: %#x 26050 17 Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening. 26051 10 Server local connection provider has successfully re-established listening on [ %hs ]. 26052 10 SQL Server Network Interfaces initialized listeners on node %ld

of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. T his is an informational message only. No user action is required. 26053 16 SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x% 0*I64x. There may be insufficient memory. Free up additional memory, then turn t he node off and on again. If the failure persists repeat this multiple times or restart the SQL Server. 26054 16 Could not find any IP address that this SQL Server instance depe nds upon. Make sure that the cluster service is running, that the dependency re lationship between SQL Server and Network Name resources is correct, and that th e IP addresses on which this SQL Server instance depends are available. Error c ode: %#x. 26056 10 Failed to update the dedicated administrator connection (DAC) po rt number in the registry. Clients may not be able to discover the correct DAC p ort through the SQL Server Browser Service. Error: %#x. 26057 16 Failed to determine the fully qualified domain name of the compu ter while initializing SSL support. This might indicate a problem with the netwo rk configuration of the computer. Error: %#x. 26058 16 A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections. 26059 10 The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. 26060 10 The SQL Server Network Interface library successfully deregister ed the Service Principal Name (SPN) [ %ls ] for the SQL Server service. 26061 10 Failed to determine the fully qualified domain name of the compu ter while composing the Service Principal Name (SPN). This might indicate a prob lem with the network configuration of the computer. Error: %#x. 26062 16 Invalid parameter detected while initializing TCP listening port . Error: %#x, state: %d. Contact Technical Support. 26064 10 SQL Server could not listen on IP address [%s] because the clust er resource '%s' is not online (state = %d). This is an informational message an d may indicate that resource '%s' has OR type of dependency on several IP addres ses some of which are currently offline or in a failed state. Further action is only required if it is generally possible to bind the IP address of the cluster resource '%s' to a network segment on the current hosting node. 26065 16 Extended Protection for the SQL Server Database Engine is enable d, but the operating system does not support Extended Protection. Connection att empts using Windows Authentication might fail. Check for an operating system ser vice pack to allow for Extended Protection through Service Binding and Channel B inding, or disable Extended Protection for the Database Engine. 26066 16 An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Windows Authentication might fail. Error: %d. 26067 10 The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Windows return code: %#x, state: %d. Failure to register a SPN might cause integrated authentic ation to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authenticatio n policies and if the SPN has not been manually registered. 26068 10 The SQL Server Network Interface library could not deregister th e Service Principal Name (SPN) [ %ls ] for the SQL Server service. Error: %#x, s tate: %d. Administrator should deregister this SPN manually to avoid client auth entication errors. 26069 10 Started listening on virtual network name '%ls'. No user action is required. 26070 10 Stopped listening on virtual network name '%ls'. No user action is required. 26071 16 Failed to load the Cluster Resource Libraries: clusapi.dll and r esutils.dll. SQL Server will be unable to accept TCP connections on clustered li steners.

26072 10 Found multiple dependent virtual network names for the Windows F ailover Cluster Resource '%ls'. SQL Server will only listen on the first virtual network name resource: '%ls'. This may indicate that there is an incorrect conf iguration of the Windows Failover Cluster Resources for SQL Server. 26073 16 TCP connection closed but a child process of SQL Server may be h olding a duplicate of the connection's socket. Consider enabling the TcpAbortiv eClose SQL Server registry setting and restarting SQL Server. If the problem per sists, contact Technical Support. 26075 16 Failed to start a listener for virtual network name '%ls'. Error : %d. 26076 10 SQL Server is attempting to register a Service Principal Name (S PN) for the SQL Server service. Kerberos authentication will not be possible unt il a SPN is registered for the SQL Server service. This is an informational mess age. No user action is required. 27001 16 Reserved error message. Should never be issued. 27002 16 A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection. 27003 16 Bad token encountered during tokenization. 27004 16 Unexpected token type encountered during tokenization. 27005 16 Error Tolerant Index is corrupt. 27006 16 Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt. 27007 16 Attempt to delete from empty ridlist. Error Tolerant Index is c orrupt. 27008 16 rid to be deleted not found in rid-list. Error Tolerant Index i s corrupt. 27009 16 Error Tolerant Index frequencies must be non-negative. Error To lerant Index is corrupt. 27010 16 Attempt to insert row whose ID is already present. Error Tolera nt Index is corrupt. 27011 16 No ridlist provided for appending. Error Tolerant Index is corr upt. 27012 16 Cannot delete token. Error Tolerant Index is corrupt. 27013 16 Tokenizer object has no delimiter set. Error Tolerant Index is corrupt. 27014 16 Deletion failed because token does not occur in index. Error To lerant Index is corrupt. 27015 16 Unexpected ridlist length. Error Tolerant Index is corrupt. 27016 16 Cannot connect to Error Tolerant Index. Bad or missing SqlComma nd object. 27017 16 Failed to drop index on reference table copy. 27018 16 Could not retrieve metadata from Error Tolerant Index. The inde x is probably corrupt. 27019 16 Could not initialize from metadata contained in Error Tolerant I ndex. The index is probably corrupt. 27022 16 An error specific to fuzzy lookup table maintenance has occurred . 27023 16 A system error occurred during execution of fuzzy lookup table m aintenance. 27024 16 Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt. 27025 16 Argument is not a valid hex string. Could not initialize from m etadata contained in Error Tolerant Index. The index is probably corrupt. 27026 16 Negative count in Error Tolerant Index metadata. The index is p robably corrupt. 27027 16 Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt. 27028 16 Invalid Error Tolerant Index metadata. The index is probably co rrupt. 27029 16 Invalid Error Tolerant Index metadata version.

27030 16 Missing metadata. The Error Tolerant Index is probably corrupt. 27031 16 Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt. 27032 16 Error Tolerant Index Metadata string too long. Index is probabl y corrupt. 27033 16 Error Tolerant Index Metadata length limit exceeded. 27034 16 Unexpected end of Error Tolerant Index metadata. Index is proba bly corrupt. 27037 16 No table name provided for Error Tolerant Index. The index is p robably corrupt. 27038 16 No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt. 27039 16 No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt. 27040 16 No Error Tolerant Index metadata string provided for initializat ion. Index is probably corrupt. 27041 16 No Error Tolerant Index metadata provided for serialization. Th e index is probably corrupt. 27042 16 Could not lookup object_id. No object name provided. 27043 16 Could not lookup object_id. Null command object provided. 27044 16 Open connection required. Cannot query Error Tolerant Index. 27045 16 Cannot write to null output buffer. Could not update Error Tole rant Index. The index is probably corrupt. 27046 16 Output buffer provided is too small. Could not update Error Tol erant Index. The index is probably corrupt. 27047 16 The number of min-hash q-grams per token must be positive. 27048 16 Could not create index on reference table copy. 27049 16 Reference table (or internal copy) missing integer identity colu mn. Error tolerant index is probably corrupt. 27050 16 The maximum allow integer identity value has been reached. Cons ider re-building the error tolerant index to use any gaps in sequence. 27051 16 Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted. 27052 16 Table maintenance insertion failed. 27053 16 A positive q-gram length is required for tokenization. 27054 16 Maintenance trigger already installed on this reference table. 27055 16 Missing extended property on maintenance trigger. 27056 16 Maintenance trigger name out of sync with Error Tolerant Index m etadata. Index is probably corrupt. 27058 16 A SQL error occurred during execution of fuzzy lookup table main tenance. 27059 16 Could not lookup object_id. The reference table or maintenance trigger could not be found. 27060 16 The Error Tolerant Index table name provided is not a valid SQL identifier. 27061 16 The Error Tolerant Index table name provided refers to a missing table. Check sys.tables. 27062 16 An auxiliary Fuzzy Lookup table maintenance table is missing. 27063 16 An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed. 27064 16 The row deleted from the reference table could not be located in the reference table copy. 27065 16 Fuzzy Lookup Table Maintenance is not installed or the Error Tol erant Index is corrupt. 27100 16 The input parameter, '%ls', cannot be null. Provide a valid valu e for this parameter. 27101 16 The value specified for the input parameter, '%ls', is not valid . Provide a valid value for this parameter. 27102 16 The input parameter, '%ls', cannot be empty. Provide a valid val ue for this parameter.

27103 16 Cannot find the execution instance '%I64d' because it does not e xist or you do not have sufficient permissions. 27104 16 Cannot find the folder '%ls' because it does not exist or you do not have sufficient permissions. 27105 16 Cannot find the operation '%I64d' because it does not exist or y ou do not have sufficient permissions. 27106 16 Cannot find the parameter '%ls' because it does not exist. 27107 16 The specified %ls already exists. 27108 16 The path for '%ls' cannot be found. The operation will now exit. 27109 16 Cannot find the project '%ls' because it does not exist or you d o not have sufficient permissions. 27110 16 Default permissions for the project cannot be granted to the use r. Make sure that the user can be assigned these permissions. 27111 16 Cannot find the reference '%I64d' because it is not part of the project or you do not have sufficient permissions. 27112 16 Unable to update the row in the table, '%ls'. Make sure that thi s row exists. 27113 16 Unable to delete one or more rows in the table, '%ls'. Make sure that these rows exist. 27114 16 Cannot find the reference '%I64d' because it does not exist or y ou do not have sufficient permissions. 27115 16 Cannot find the target folder '%ls' because it does not exist or you do not have sufficient permissions. 27116 16 Conversion failed while performing encryption. 27117 16 Failed to decrypt the project. The symmetric key that was used t o encrypt it may have been deleted. Delete the project and deploy it again. 27118 16 Failed to deploy the project. Try again later. 27119 16 Failed to encrypt the project named '%ls'. The symmetric key may have been deleted. Delete the project and deploy it again. 27120 16 Failed to grant permission '%ls'. 27121 16 The project is currently running or has completed. An instance o f execution can only be started once. 27122 16 Unable to perform impact analysis and lineage. The package data or configuration data might not be valid. To validate package data, open the pac kage in Business Intelligence Development Studio. To validate configuration data , open the configuration XML file in an XML editor. 27123 16 The operation cannot be started by an account that uses SQL Serv er Authentication. Start the operation with an account that uses Windows Authent ication. 27124 16 Integration Services server cannot stop the operation. The speci fied operation with ID '%I64d' is not valid or is not running. 27125 16 Integration Services server cannot stop the operation. The speci fied operation is not in a consistent state and cannot be stopped. 27126 16 Integration Services server cannot stop the operation. The speci fied operation is already in Stopping state. 27127 16 The Integration Services catalog '%ls' does not exists. 27128 16 The name '%ls' is not valid. It consists of characters that are not allowed. 27129 16 The folder '%ls' already exists or you have not been granted the appropriate permissions to change it. 27130 16 Integration Services server was unable to impersonate the caller . Windows returned error code: %ls. 27131 16 Integration Services server was unable to start the process, '%l s'. Windows returned error code: %ls. 27132 16 Integration Services server was unable to create process compone nt, '%ls'. Windows returned error code: %ls. 27133 16 Integration Services server was unable to wait for process, '%ls ', to finish. Windows returned error code: %ls. 27135 16 The database, '%ls', already exists. Rename or remove the existi ng database, and then run SQL Server Setup again.

27136 16 The required components for the 32-bit edition of Integration Se rvices cannot be found. Run SQL Server Setup to add the required components. 27137 16 The registry key for the system setting '%ls' could not be found . The operation will now exit. 27138 16 The input parameter cannot be null. Provide a valid value for th e parameter. 27139 16 Integration Services server cannot be configured because there a re active operations. Wait until there are no active operations, and then try to configure the server again. 27140 16 The operation cannot be started because the user is not a member of the database role, '%ls', or the server role, '%ls'. Log in as a member of o ne of these roles, and then try to start the operation again. 27142 16 '%ls' is not a valid environment name. It consists of characters that are not allowed. 27143 16 Cannot access the operation with ID, '%I64d'. Verify that the us er has appropriate permissions. 27145 16 '%ls' is not a valid project name. It consists of characters tha t are not allowed. 27146 16 Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it. 27147 16 The data type of the input value is not compatible with the data type of the '%ls'. 27148 16 The data type of the parameter does not match the data type of t he environment variable. 27149 16 Integration Services server cannot perform the requested operati on on the specified package now, because the package is in pending state. Wait u ntil the package is not in pending state, and try to perform the operation again . 27150 16 The version of the project has changed since the instance of the execution has been created. Create a new execution instance and try again. 27151 10 The restore operation for project '%ls' from version '%I64d' has started. 27152 10 The restore operation for project '%ls' to version '%I64d' has c ompleted. 27153 16 Default permissions for the operation cannot be granted to the u ser. Make sure that the user can be assigned these permissions. 27154 16 The @sensitive parameter is missing. This parameter is used to i ndicate if the parameter contains a sensitive value. 27155 16 Project restore has failed. You cannot restore a project having an object_version_lsn that is the same as the current project. 27156 16 The Integration Services server property, '%ls', cannot be found . Check the name of the property and try again. 27157 16 The environment '%ls' already exists or you have not been grante d the appropriate permissions to create it. 27158 16 Error number, %d, occurred in the procedure, '%ls', at line numb er, %d. The error message was: '%ls' The error level was %d and the state was %d . 27159 16 Data type of the input value is not supported. 27161 10 Warning: the requested permission has already been granted to th e user. The duplicate request will be ignored. 27162 16 The property, '%ls', cannot be changed because the Integration S ervices database is not in single-user mode. In Management Studio, in the Databa se Properties dialog box, set the Restrict Access property to single-user mode. Then, try to change the value of the property again. 27163 16 The value for the Integration Services server property, '%ls', i s not valid. In Management Studio, in the Integration Services Properties dialog box, enter a valid value for this property. 27165 10 Warning: During startup, the Integration Services server marked operation %I64d (type %d, status %d) as terminated. Please check the operation/e vent log for operation details.

27166 16 The installed version of SQL Server does not support the install ation of the Integration Services server. Update SQL Server, and then try instal ling the Integration Services server again. 27167 16 Failed to change the encryption algorithm to '%ls'. An error occ urred while encrypting the environment variables with the '%ls' algorithm. 27168 16 Failed to change the encryption algorithm to '%ls'. An error occ urred while encrypting the parameter values using the '%ls' algorithm. 27169 16 Failed to create a log entry for the requested operation. 27170 16 Failed to retrieve the project named '%ls'. 27171 16 The value specified is not valid. A value of data type '%ls' is required. 27172 16 The certificate and symmetric key used to encrypt project '%ls' does not exist or you do not have sufficient permissions. 27173 16 The environment variable '%ls' already exists. 27175 16 The execution has already completed. 27176 16 The parameter '%ls' does not exist or you do not have sufficient permissions. 27177 16 Environment names must be unique. There is already an environmen t named '%ls'. 27178 16 Unable to execute the project named '%ls'. You do not have suffi cient permissions. 27179 16 The object version does not match the project id or you do not h ave sufficient permissions. 27180 16 %ls is not a valid environment variable name. It consists of cha racters that are not allowed. 27181 16 The project '%ls' already exists or you have not been granted th e appropriate permissions to access it. 27182 16 The environment '%s' does not exist or you have not been granted the appropriate permissions to access it. 27183 16 The environment variable '%ls' does not exist or you have not be en granted the appropriate permissions to access it. 27184 16 In order to execute this package, you need to specify values for the required parameters. 27185 16 The validation record for ID '%I64d' does not exist or you have not been granted the appropriate permissions to access it. 27186 16 One or more environment variables could not be found in the refe renced environment. 27187 16 The project does not exist or you have not been granted the appr opriate permissions to access it. 27188 16 Only members of the ssis_admin or sysadmin server roles can crea te, delete, or rename a catalog folder. 27189 16 Catalog folder name cannot be NULL or an empty string. 27190 16 The folder '%ls' already exists or you have not been granted the appropriate permissions to create it. 27191 16 The '%d' permission is not applicable to objects of type '%d'. G rant, deny, or revoke of this permission is not allowed. 27192 16 The caller has not been granted the MANAGEPERMISSION permission for the specified object. 27193 16 SQL Server %ls is required to install Integration Services. It c annot be installed on this version of SQL Server. 27194 16 Cannot find the project because it does not exist or you do not have sufficient permissions. 27195 16 The operation failed because the execution timed out. 27196 16 Failed to delete the folder '%ls' because it is not empty. Only empty folders can be deleted. 27197 16 The specified %ls %ld does not exist. 27198 16 Failed to locate records for the specified operation (ID %I64d). 27199 16 %ls is not a valid folder name. It consists of characters that a re not allowed. 27200 16 The project is missing the specified environment reference.

27201 16 Values are missing for required parameters in this package. Spec ify values in order to start the validation. 27202 16 This project is missing one or more environment references. In o rder to use environment variables, specify the corresponding environment referen ce identifier. 27203 16 Failed to deploy project. For more information, query the operat ion_messages view for the operation identifier '%I64d'. 27204 16 Failed to create environment reference. This project already has an reference to the specified environment. 27205 16 Some of the property values for this parameter are missing. 27206 16 Failed to deploy project to the folder '%ls'. You do not have su fficient permissions to deploy this project. 27207 16 Failed to locate one or more variables in the environment '%ls'. 27208 16 The environment reference '%I64d' is not associated with the pro ject. 27209 16 Failed to create environment to the folder '%ls'. You do not hav e sufficient permissions to create this environment. 27210 16 Conversion failed when converting the %ls to data type %ls. 27212 16 Data tap can only be added or removed when the execution status is created. 27213 16 The package path and data flow path ID strings already exist for the execution ID %I64d. Provide package path and data flow path ID strings that are not in the catalog.execution_data_taps view. 27214 16 The data flow task GUID '%ls' and the data flow path ID string a lready exist for the execution ID %I64d. Provide a data flow task GUID and a dat a flow path ID string that are not in the catalog.execution_data_taps view. 27215 16 The data tap '%I64d' does not exist, or you do not have sufficie nt permissions to remove it. Provide a valid data tap ID. 27216 16 The number of rows must be a non-negative value. Specify a valid value. 27217 16 The logging level '%d' is undefined. Provide one of the followin g logging levels: 0 (None), 1 (Basic), 2 (Performance), 3 (Verbose). 27218 16 The Integration Services Server cannot find the running process for execution ID %I64d. Provide a valid execution ID. 27219 16 Caller does not have permissions to execute the stored procedure . 27220 16 SSISDB database does not exist. Create the SSISDB database. 27221 16 Unable to map an environment variable with the sensitive propert y set to True, to a parameter with the sensitive property set to False. Ensure t hat the property settings match. 27222 16 The required components for the 64-bit edition of Integration Se rvices cannot be found. Run SQL Server Setup to install the required components . 27223 16 Cannot move the project to folder '%ls' due to insufficient perm issions. 27224 16 The parameter value cannot be changed after the execution has be en started. 27225 16 The property cannot be overridden after the execution has been s tarted. 27226 16 The database principal has granted or denied permissions to cata log objects in the database and cannot be dropped. 28000 16 The decrypted session key has an unexpected size. 28001 16 A corrupted message has been received. It contains invalid flags . This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28002 16 Cannot start service broker manager. Operating system error: %ls . 28003 16 An internal service broker error occurred. Operating system erro r: %ls. 28004 16 This message could not be delivered because the '%S_MSG' action

cannot be performed in the '%.*ls' state. 28005 16 An exception occurred while enqueueing a message in the target q ueue. Error: %d, State: %d. %.*ls 28006 14 User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_own er fixed database role have this permission. 28007 16 A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in th e message with Conversation ID '%.*ls', Initiator: %d, and Message sequence numb er: %I64d. 28008 16 The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%. 2x%.2x%.2x}' is invalid. 28009 16 The crypto API has detected bad data while trying to perform a d ecryption operation. 28010 16 This message could not be delivered because it contains an inval id acknowledged message number. Highest expected message number: %I64d. Acknowle dged message number: %I64d, fragment number: %d. 28011 16 This message could not be delivered because its %S_MSG has expir ed or is invalid. 28012 16 The Service Broker in the target database is unavailable: '%S_MS G'. 28013 16 The service broker is administratively disabled. 28014 16 The database is in read-only mode. 28015 16 The database is in single-user mode. 28016 16 The message has been dropped because the service broker in the t arget database is unavailable: '%S_MSG'. 28017 16 The message has been dropped because the target service broker i s unreachable. 28018 16 The database is a replica of a mirrored database. 28019 16 System error %d occurred while creating a new message element GU ID for this forwarded message. 28020 16 Could not create user token for user %d in database %d. 28021 16 One or more messages could not be delivered to the local service targeted by this dialog. 28022 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: The certificate is not yet valid. 28023 10 An error occurred while looking up the public key certificate as sociated with this SQL Server instance: The certificate has expired. 28024 16 The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a cer tificate that is currently valid. 28025 16 The security certificate bound to database principal (Id: %i) ha s expired. Create or install a new certificate for the database principal. 28026 10 Connection handshake failed. Not enough memory available. State %d. 28027 10 Connection handshake failed. There is no compatible %S_MSG. Stat e %d. 28028 10 Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d. 28029 10 Connection handshake failed. Unexpected event (%d) for current c ontext (%d). State %d. 28030 10 Connection handshake failed. A call to the SQL Server Network In terface failed: (%x) %ls. State %d. 28031 10 Connection handshake failed. An OS call failed: (%x) %ls. State %d. 28032 10 A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will b e closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d. 28033 10 A new connection was established with the same peer. This connec

tion lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user a ction is required. State %d. 28034 10 Connection handshake failed. The login '%.*ls' does not have CON NECT permission on the endpoint. State %d. 28035 10 Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d. 28036 10 Connection handshake failed. The certificate used by this endpoi nt was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the meta data integrity of the endpoints. State %d. 28037 10 Connection handshake failed. Error %d occurred while initializin g the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d. 28038 10 Connection handshake failed. The handshake verification failed. State %d. 28039 10 Connection handshake failed. The receive SSPI packet is not of t ype of the negotiated package. State %d. 28040 10 A corrupted message has been received. The adjacent error messag e header is invalid. 28041 16 A corrupted message has been received. The encrypted payload off set is invalid (%d). 28042 16 A corrupted message has been received. The arbitration request h eader is invalid. 28043 16 A corrupted message has been received. The arbitration response header is invalid. 28044 16 A corrupted message has been received. It is not encrypted and s igned using the currently configured endpoint algorithm. This occurred in the me ssage with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28045 10 Connection handshake failed. The certificate used by the peer do es not match the one in MASTER database with same issuer name and serial number. State %d. 28046 10 %S_MSG Login succeeded for user '%.*ls'. Authentication mode: %. *ls. %.*ls 28047 10 %S_MSG login attempt failed with error: '%.*ls'. %.*ls 28048 10 %S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls 28050 10 The session keys for this conversation could not be created or a ccessed. The database master key is required for this operation. 28051 10 Could not save a dialog session key. A master key is required in the database to save the session key. 28052 16 Cannot decrypt session key while regenerating master key with FO RCE option. 28053 16 Service Broker could not upgrade conversation session keys in da tabase '%.*ls' to encrypted format (Error: %d). The Service Broker in this datab ase was disabled. A master key is required to the database in order to enable th e broker. 28054 16 Service Broker needs to access the master key in the database '% .*ls'. Error code:%d. The master key has to exist and the service master key enc ryption is required. 28055 16 The certificate '%.*ls' is not valid for endpoint authentication . The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certi ficate expiration date. 28056 16 This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: '%.*ls'. 28057 10 Service Broker in database '%.*ls' has a pending conversation up grade operation. A database master key in the database is required for this oper ation to complete.

28058 16 Service Broker could not upgrade this conversation during a data base upgrade operation. 28059 16 Connection handshake failed. The received premaster secret of si ze %d does not have the expected size of %d. State %d. 28060 16 The AES encryption algorithm is only supported on Windows XP, Wi ndows Server 2003 or later versions. 28061 16 A corrupted message has been received. The adjacent message inte grity check signature could not be validated. 28062 16 A corrupted message has been received. The signed dialog message header is invalid. 28063 16 A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28064 16 A corrupted message has been received. A string variable data fi eld is not a valid UNICODE string: %S_MSG. This occurred in the message with Con versation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28065 16 A corrupted message has been received. The unsigned dialog messa ge header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28066 16 A corrupted message has been received. The security dialog messa ge header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28067 16 A corrupted message has been received. The encrypted offset of t he envelope does not match the payload encrypted offset. This occurred in the me ssage with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 28068 16 A corrupted message has been received. The envelope payload is b igger than the message. This occurred in the message with Conversation ID '%.*ls ', Initiator: %d, and Message sequence number: %I64d. 28069 16 Unexpected session key when encrypting a dialog message. 28070 10 Connection handshake failed. The received SSPI message Confirm s tatus is unexpected. State %d. 28072 16 A serious error occurred in the Service Broker message transmitt er (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds. 28073 16 An out of memory condition has occurred in the Service Broker me ssage transmitter (operation %i). Message transmission will resume in %i seconds . 28074 16 Service Broker could not upgrade conversation with conversation_ handle '%ls'. Use END CONVERSATION ... WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE ... SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE ... SET NEW_BROKER to delete all conversations in this database. 28075 10 The broker in the sender's database is in single user mode. Mess ages cannot be delivered while in single user mode. 28076 10 Could not query the FIPS compliance mode flag from registry. Err or %ls. 28077 10 %S_MSG endpoint is running in FIPS compliance mode. This is an i nformational message only. No user action is required. 28078 10 The RC4 encryption algorithm is not supported when running in FI PS compliance mode. 28079 10 Connection handshake failed. The received SSPI packet is not of the expected direction. State %d. 28080 10 Connection handshake failed. The %S_MSG endpoint is not configur ed. State %d. 28081 10 Connection handshake failed. An unexpected status %d was returne d when trying to send a handshake message. State %d. 28082 10 Connection handshake failed. An unexpected internal failure occu rred when trying to marshal a message. State %d. 28083 16 The database principal '%.*ls' cannot be used in a remote servic

e binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or a symmetric keys. 28084 10 An error occurred in Service Broker internal activation while tr ying to scan the user queue '%ls' for its status. Error: %i, State: %i. %.*ls Th is is an informational message only. No user action is required. 28085 16 The activated task was ended because the associated queue was dr opped. 28086 16 The activated task was ended because either the queue or activat ion was disabled. 28087 16 The activated task was aborted because the invoked stored proced ure '%ls' did not execute RECEIVE. 28088 16 The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possibl e output from the activation stored procedure. 28089 16 The database principal '%.*ls' cannot be used in a remote servic e binding because it cannot own certificates. This is a special user for backwar d compatibility with implicitly connected user schemas. 28090 16 An error occurred while deleting sent messages from the transmis sion queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available. 28091 10 Starting endpoint for %S_MSG with no authentication is not supp orted. 28098 10 A previously existing connection with the same peer was found af ter DNS lookup. This connection will be closed. All traffic will be redirected t o the previously existing connection. This is an informational message only. No user action is required. State %d. 28099 10 During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now res erved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or ren ame the user object from the original (pre-upgraded) database on an older versio n of SQL Server and then retry the database upgrade process by using CREATE DATA BASE FOR ATTACH. Functionality that relies on the reserved object may not functi on correctly if you continue to use the database in the current state. 28101 16 User '%.*ls\%.*ls' does not have permission to debug the request ed client connection. 28102 16 Batch execution is terminated because of debugger request. 28201 10 SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE canno t be found. 29001 16 To connect to this server you must use SQL Server Management Stu dio or SQL Server Management Objects (SMO). 29003 16 Invalid parameter combinations. 29004 16 Unknown property specified: %s. 29801 16 GDM request processing failed. See previous error for details. 29802 16 GDM failed to allocate message via communication stack API. 29803 10 Global Deadlock Monitor is inactive. This is an informational me ssage only. No user action is required. 30003 16 A fulltext system view or stvf cannot open database id %d. 30004 16 A fulltext system view or stvf cannot open user table object id %d. 30005 16 The name specified for full-text index fragment %.*ls is not val id. 30006 16 A fulltext system view or stvf cannot open fulltext index for us er table object id %d. 30007 16 Parameters of dm_fts_index_keywords, dm_fts_index_keywords_by_do cument, and dm_fts_index_keywords_by_property cannot be null. 30008 16 This is an internal error when invoking the TVF to access the fu ll-text index. The level number specified for the TVF is not valid. Valid level

numbers start from 0 and must be less than the number of levels of the compresse d index. 30009 16 The argument data type '%ls' specified for the full-text query i s not valid. Allowed data types are char, varchar, nchar, nvarchar. 30020 16 The full-text query parameter for %S_MSG is not valid. 30022 10 Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an incons istent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION. 30023 16 The fulltext stoplist '%.*ls' does not exist or the current user does not have permission to perform this action. Verify that the correct stopli st name is specified and that the user had the permission required by the Transa ct-SQL statement. 30024 16 The fulltext stoplist '%.*ls' already exists in the current data base. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name. 30025 16 The search property list '%.*ls' does not exist or you do not ha ve permission to perform this action. Verify that the correct search property li st name is specified and that you have the permission required by the Transact-S QL statement. For a list of the search property lists on the current database, u se the sys.registered_search_property_lists catalog view. For information about permissions required by a Transact-SQL statement, see the Transact-SQL reference topic for the statement in SQL Server Books Online. 30026 16 The search property list '%.*ls' already exists in the current d atabase. Duplicate search property list names are not allowed. Rerun the stateme nt and specify a unique name for the search property list. For a list of the sea rch property lists on the current database, use the sys.registered_search_proper ty_lists catalog view. 30027 10 The full-text index is in an inconsistent state because the sear ch property list of the full-text index was reconfigured using the WITH NO POPUL ATION clause. To bring the full-text index into a consistent state, start a full population using the statement ALTER FULLTEXT INDEX ON <table_name> START FULL POPULATION;. This is a warning. No user action is necessary. 30028 17 Failed to get pipeline interface for '%ls', resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host. 30029 17 The full-text host controller failed to start. Error: 0x%X. 30030 16 The search property '%.*ls' does not exist, or you do not have p ermission to perform this action. Verify that the correct search property is spe cified and that you have the permission required by the Transact-SQL statement. For a list of the search properties on the current database, use the sys.registe red_search_properties catalog view. For information about the permissions requir ed by a Transact-SQL statement, see the Transact-SQL reference topic for the sta tement in SQL Server Books Online. 30031 17 A full-text master merge failed on full-text catalog '%ls' in da tabase '%.*ls' with error 0x%08X. 30032 16 The stoplist '%.*ls' does not contain fulltext stopword '%.*ls' with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transact-SQL statement. 30033 16 The stoplist '%.*ls' already contains full-text stopword '%.*ls' with locale ID %d. Specify a unique stopword and locale identifier (LCID) in th e Transact-SQL statement. 30034 16 Full-text stoplist '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is usin g a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.full text_indexes catalog view, and then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text ind ex by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FU LLTEXT INDEX. Then retry dropping the stoplist.

30035 16 The search property '%.*ls' already exists in the search propert y list. Specify a search property name that is unique within the specified searc h property list. For a list of the search properties on the current database, us e the sys.registered_search_properties catalog view. 30036 16 Search property list '%.*ls' cannot be dropped because it is bei ng used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the sys.registered_search_property_lists catalog view , and then obtain the object ID of every table or indexed view whose full-text i ndex is associated with this search property list from the object_id and propert y_list_id columns of the sys.fulltext_indexes catalog view . For each full-text index, either remove the search property list or drop the full-text index, if it is no longer needed. To remove the search property list, use ALTER FULLTEXT IND EX ON <table_name> SET SEARCH PROPERTY LIST OFF;. To drop a full-text index, use DROP FULLTEXT INDEX ON <table_name>;. 30037 16 An argument passed to a fulltext function is not valid. 30038 17 Fulltext index error during compression or decompression. Full-t ext index may be corrupted on disk. Run dbcc checkdatabase and re-populate the i ndex. 30039 17 Data coming back to the SQL Server process from the filter daemo n host is corrupted. This may be caused by a bad filter. The batch for the index ing operation will automatically be retried using a smaller batch size. 30040 10 During a full-text crawl of table or indexed view '%ls', an unre gistered property, '%ls', was found in batch ID %d. This property will be indexe d as part of the generic content and will be unavailable for property-scoped ful l-text queries. Table or indexed view ID is '%d'. Database ID is '%d'. For infor mation about registering properties and updating the full-text index of a table or indexed view, see the full-text search documentation in SQL Server Books Onli ne. This is an informational message. No user action is necessary. 30041 10 The master merge started at the end of the full crawl of table o r indexed view '%ls' failed with HRESULT = '0x%08x'. Database ID is '%d', table id is %d, catalog ID: %d. 30043 16 Stopwords of zero length cannot be added to a full-text stoplist . Specify a unique stopword that contains at least one character. 30044 16 The user does not have permission to alter the current default s toplist '%.*ls'. To change the default stoplist of the database, ALTER permissio n is required on both new and old default stoplists. 30045 17 Fulltext index error during compression or decompression. Full-t ext index may be corrupted on disk. Run dbcc checkdatabase and re-populate the i ndex. 30046 16 SQL Server encountered error 0x%x while communicating with fulltext filter daemon host (FDHost) process. Make sure that the FDHost process is r unning. To re-start the FDHost process, run the sp_fulltext_service 'restart_all _fdhosts' command or restart the SQL Server instance. 30047 16 The user does not have permission to %.*ls stoplist '%.*ls'. 30048 10 Informational: Ignoring duplicate thesaurus rule '%ls' while loa ding thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the <sub> section of an expansion rule or the <pat> section of a replace ment rule. This causes an ambiguity and hence this phrase will be ignored. 30049 17 Fulltext thesaurus internal error (HRESULT = '0x%08x') 30050 16 Both the thesaurus file for lcid '%d' and the global thesaurus c ould not be loaded. 30051 16 Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: '%ls'. 30052 16 The full-text query has a very complex NEAR clause in the CONTAI NS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs succes sfully, use only six or fewer terms. Modify the query to simplify the condition by removing prefixes or repeated terms. 30053 16 An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service

account missing privileges, malfunctioning IFilters, communication channel issu es with FDHost and sqlservr.exe, etc. 30055 10 Full-text catalog import has started for full-text catalog '%ls' in database '%ls'. 30056 10 Full-text catalog import has finished for full-text catalog '%ls ' in database '%ls'. %d fragments and %d keywords were processed. 30057 10 Upgrade option '%ls' is being used for full-text catalog '%ls' i n database '%ls'. 30058 16 Properties of zero length cannot be added to a search property l ist. Specify a search property name that contains at least one character and tha t is unique to the specified search property list. For a list of the search prop erties on the current database, use the sys.registered_search_properties catalog view. 30059 16 A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); catalog name is %s (id: %d); table name %s (id: %d). Fix the errors that a re logged in the full-text crawl log. Then, resume the population. The basic Tra nsact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name RESUME POPULATI ON. 30060 16 The import population for database %ls (id: %d), catalog %ls (id : %d) is being cancelled because of a fatal error ('%ls'). Fix the errors that a re logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching it, or by taking the database offline and bringin g it back online. If the error is not recoverable, rebuild the full-text catalog . 30061 17 The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service accou nt does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server after the issue is fixed. 30062 17 The SQL Server failed to load FDHost service group sid. This mig ht be because installation is corrupted. 30063 10 Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid. 30064 17 SQL Server failed to set security information on the full-text F ilterData directory in the FTData folder. Full-text indexing of some types of do cuments may fail until this issue is resolved. You will need to repair the SQL S erver installation. 30065 10 Filegroup '%ls' is offline, readonly, or no data file. Full-text population on table '%ls' is not resumed. Resume full-text population after fix ing the filegroup status. 30067 10 Warning: The detach operation cannot delete a full-text index cr eated on table '%ls' in database '%ls' because the index is on a read-only fileg roup. To drop the full-text index, re-attach the database, change the read-only filegroup to read/write access and then detach it. This warning will not fail th e database detach operation. 30068 10 During the database upgrade, the full-text filter component '%ls ' that is used by catalog '%ls' was successfully verified. Component version is '%ls'; Full path is '%.*ls'. 30069 11 The full-text filter component '%ls' used to populate catalog '% ls' in a previous SQL Server release is not the current version (component versi on is '%ls', full path is '%.*ls'). This may cause search results to differ slig htly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the filter component. 30070 10 During the database upgrade, the full-text word-breaker componen t '%ls' that is used by catalog '%ls' was successfully verified. Component versi on is '%ls'. Full path is '%.*ls'. Language requested is %d. Language used is %d . 30071 11 The full-text word-breaker component '%ls' used to populate cata log '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls', language requested is %d, language used

is %d). This may cause search results to differ slightly from previous releases . To avoid this, rebuild the full-text catalog using the current version of the word-breaker component. 30072 10 During the database upgrade, the full-text protocol handler comp onent '%ls' that is used by catalog '%ls' was successfully verified. Component v ersion is '%ls'. Full path is '%.*ls'. Program ID is '%.*ls'. 30073 11 The full-text protocol handler component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (compo nent version is '%ls', full path is '%.*ls', program ID is '%.*ls'). This may ca use search results to differ slightly from previous releases. To avoid this, reb uild the full-text catalog using the current version of the protocol handler com ponent. 30074 17 The master merge of full-text catalog '%ls' in database '%.*ls' was cancelled. 30075 10 Full-text crawls for database ID: %d, table ID: %d, catalog ID: %d will be stopped since the clustered index on the table has been altered or dr opped. Crawl will need to re-start from the beginning. 30076 10 Full-text crawl forward progress information for database ID: %d , table ID: %d, catalog ID: %d has been reset due to the modification of the clu stered index. Crawl will re-start from the beginning when it is unpaused. 30077 16 The full-text query did not use the value specified for the OPTI MIZE FOR query hint. Only single terms are allowed as values for full-text queri es that contain an OPTIMIZE FOR query hint. Modify the OPTIMIZE FOR query hint v alue to be a single, non-empty term. 30078 10 The fulltext query did not use the value specified for the OPTIM IZE FOR hint because the query contained more than one type of full-text logical operator. 30079 10 The full text query ignored UNKNOWN in the OPTIMIZE FOR hint. 30080 16 The full-text population on table '%ls' cannot be started becaus e the full-text catalog is importing data from existing catalogs. After the impo rt operation finishes, rerun the command. 30081 10 A cached plan was compiled using trace flags that are incompatib le with the current values. Consider recompiling the query with the new trace fl ag settings. 30082 16 Full-text predicates cannot appear in an aggregate expression. P lace the aggregate expression in a subquery. 30083 16 Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery. 30084 16 The full-text index cannot be created because filegroup '%.*ls' does not exist or the filegroup name is incorrectly specified. Specify a valid f ilegroup name. 30085 16 A stoplist cache cannot be generated while processing a full-tex t query or performing full-text indexing. There is not enough memory to load the stoplist cache. Rerun the query or indexing command when more resources are ava ilable. 30086 16 The system ran out of memory while building a full-text index. T he batch for the full-text indexing operation will automatically be retried usin g a smaller batch size. 30087 17 Data coming back to the SQL Server process from the filter daemo n host is corrupted. This may be caused by a bad filter. The batch for the index ing operation will automatically be retried using a smaller batch size. 30088 10 The full-text filter daemon host process has stopped normally. T he process will be automatically restarted if necessary. 30089 17 The fulltext filter daemon host (FDHost) process has stopped abn ormally. This can occur if an incorrectly configured or malfunctioning linguisti c component, such as a wordbreaker, stemmer or filter has caused an irrecoverabl e error during full-text indexing or query processing. The process will be resta rted automatically. 30090 10 A new instance of the full-text filter daemon host process has b een successfully started.

30091 10 A request to start a full-text index population on table or inde xed view '%.*ls' is ignored because a population is currently paused. Either res ume or stop the paused population. To resume it, use the following Transact-SQL statement: ALTER FULLTEXT INDEX ON %.*ls RESUME POPULATION. To stop it, use the following statement: ALTER FULLTEXT INDEX ON %.*ls STOP POPULATION. 30092 16 Full-text stoplist ID '%d' does not exist. 30093 17 The SQL Server word-breaking client failed to initialize. This m ight be because a filter daemon host process is not in a valid state. This can p revent SQL Server from initializing critical system objects. Full-text queries w ill fail until this issue is resolved. Try stopping SQL Server and any filter da emon host processes and then restarting the instance of SQL Server. 30094 17 The full-text indexing pipeline could not be initialized. This m ight be because the resources on the system are too low to allocate memory or cr eate tasks. Try restarting the instance of SQL Server. 30095 10 The version of the language components used by full-text catalog '%ls' in database '%ls' is different from the version of the language component s included this version of SQL Server. The full-text catalog will still be impor ted as part of database upgrade. To avoid any possible inconsistencies of query results, consider rebuilding the full-text catalog. 30096 10 A full-text retry pass of %ls population started for table or in dexed view '%ls'. Table or indexed view ID is '%d'. Database ID is '%d'. 30097 10 The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs for the catalog I D %d in database ID %d. Try to reattach this database. If this fails, then the c atalog will need to be dropped or recreated before attach. 30098 10 An internal query to load data for a crawl on database '%.*ls' a nd table '%.*ls' failed with error code %d. Check the sql error code for more in formation about the condition causing this failure. The crawl needs to be restar ted after this condition is removed. 30099 17 Fulltext internal error 31001 16 The session '%s' already exists. Use a different session name. 31002 16 This operation can be performed only by the owner of the session . 31003 16 User does not have enough permissions to tune one or more of the databases specified. 31201 16 Property-scoped full-text queries cannot be specified on the spe cified table because its full-text index is not configured for property searchin g. To support property-scoped searches, the full-text index must be associated w ith a search property list and repopulated. The Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON <table_name> SET SEARCH PROPERTY LIST <property_list_na me>;. 31202 10 Reconfiguring the search property list of the full-text index ha s truncated the existing data in the index. Until the full-text index has been f ully repopulated, full-text queries will return partial results. The ALTER FULLT EXT INDEX <table_name> SET SEARCH PROPERTY LIST ...; statement automatically iss ues a full population, but if the ALTER FULLTEXT INDEX statement specified the W ITH NO POPULATION clause, you must run a full population on the full-text index using ALTER FULLTEXT INDEX ON <table_name> START FULL POPULATION;. This is a war ning. 31203 10 Warning Master Merge operation was not done for dbid %d, objid % d, so querying index will be slow. Please run alter fulltext catalog reorganize. 32001 32002 32003 32004 32005 32006 32007 32008 10 10 10 10 10 10 16 10 Log shipping backup log job for %s. Log shipping copy job for %s:%s. Log shipping restore log job for %s:%s. Log shipping backup log job step. Log shipping copy job step. Log shipping restore log job step. Database %s is not ONLINE. Database %s is not ONLINE. The backup job will not be performed

until this database is brought online. 32009 16 A log shipping primary entry already exists for database %s. 32010 16 Database %s does not exist as log shipping primary. 32011 16 Primary Database %s has active log shipping secondary database(s ). Drop the secondary database(s) first. 32012 16 Secondary %s.%s already exists for primary %s. 32013 16 A log shipping entry already exists for secondary database %s. 32014 16 Database %s does not exist as log shipping secondary. 32015 16 The primary database %s cannot have SIMPLE recovery for log ship ping to work properly. 32016 16 The specified agent_id %s or agent_type %d do not form a valid p air for log shipping monitoring processing. 32017 16 Log shipping is supported on Enterprise, Developer and Standard editions of SQL Server. This instance has %s and is not supported. 32018 16 Log shipping is not installed on this instance. 32019 10 Log shipping alert job. 32020 10 Log shipping alert job step. 32021 10 Log shipping alert job schedule. 32022 16 Cannot add a log shipping job with name %s. A job with same name already exists in the system and this job does not belong to log shipping categ ory. 32023 16 An entry for primary server %s, primary database %s does not exi st on this secondary. Register the primary first. 32024 16 An entry for primary server %s, primary database %s already exis ts. 32025 16 Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first. 32026 10 Log shipping Primary Server Alert. 32027 10 Log shipping Secondary Server Alert. 32028 16 Invalid value = %d for parameter @threshold_alert was specified. 32029 10 Log shipping backup agent [%s] has verified log backup file '%s. wrk' and renamed it as '%s.trn'. This is an informational message only. No user action is required. 32030 10 Could not query monitor information for log shipping primary %s. %s from monitor server %s. 32031 10 Could not query monitor information for log shipping secondary % s.%s from monitor server %s. 32032 16 Invalid value '%d' for update period. Update period should be be tween 1 and 120 minutes. 32033 16 The update job for the database mirroring monitor already exists . To change the update period, use sys.sp_dbmmonitorchangemonitoring 32034 16 An internal error occurred when setting up the database mirrorin g monitoring job. 32035 16 An internal error occurred when modifying the database mirroring monitoring job. 32036 16 Parameter(s) out of range. 32037 16 The units for the update period for the database mirroring monit or job have been changed. 32038 16 An internal error has occurred in the database mirroring monitor . 32039 16 The database '%s' is not being mirrored. No update of the base t able was done. 32040 16 The alert for 'oldest unsent transaction' has been raised. The c urrent value of '%d' surpasses the threshold '%d'. 32041 16 The database mirroring monitor base tables have not been created . Please run sys.sp_dbmmonitorupdate to create them. 32042 16 The alert for 'unsent log' has been raised. The current value of '%d' surpasses the threshold '%d'. 32043 16 The alert for 'unrestored log' has been raised. The current valu e of '%d' surpasses the threshold '%d'.

32044 16 The alert for 'mirror commit overhead' has been raised. The curr ent value of '%d' surpasses the threshold '%d'. 32045 16 '%s' must be executed in msdb. 32046 16 Only members of the sysadmin fixed server role or the 'dbm_monit or' role in msdb can perform this operation. 32047 15 Database Mirroring Monitor Job 32048 15 Database Mirroring Monitor Schedule 32049 16 The database mirroring monitoring job does not exist. Run sp_dbm monitoraddmonitoring to setup the job. 32050 16 Alerts cannot be created on the system databases, master, msdb, model or tempdb. 32051 10 System administrator privilege is required to update the base ta ble. The base table was not updated. 32052 16 Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation. 32053 16 The server name, given by '@@servername', is currently null. 32054 16 There was an error establishing a link to the remote monitor ser ver. 32055 16 There was an error configuring the remote monitor server. 33001 16 Cannot drop the option because the option is not specified on %S _MSG. 33002 16 Access to %ls %ls is blocked because the signature is not valid. 33003 16 DDL statement is not allowed. 33004 16 The password of login '%.*ls' is invalid. A new password should be set for this login without specifying the old password. 33005 16 Cannot find the certificate or asymmetric key from the file %.*l s. ErrorCode: 0x%x. 33006 16 WITH SIGNATURE option cannot be specified on database. 33007 16 Cannot encrypt symmetric key with itself. 33008 16 Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SC HEMA or SYS %S_MSG. 33009 16 The database owner SID recorded in the master database differs f rom the database owner SID recorded in database '%.*ls'. You should correct this situation by resetting the owner of database '%.*ls' using the ALTER AUTHORIZAT ION statement. 33010 16 The MUST_CHANGE option cannot be specified together with the HAS HED option. 33011 16 The %S_MSG private key cannot be dropped because one or more ent ities are encrypted by it. 33012 10 Cannot %S_MSG signature %S_MSG %S_MSG '%.*ls'. Signature already exists or cannot be added. 33013 16 A %S_MSG by %S_MSG '%.*s' does not exist. 33014 16 Cannot countersign '%.*s'. Only modules can be countersigned. 33015 16 The database principal is referenced by a %S_MSG in the database , and cannot be dropped. 33016 16 The user cannot be remapped to a login. Remapping can only be do ne for users that were mapped to Windows or SQL logins. 33017 16 Cannot remap a user of one type to a login of a different type. For example, a SQL user must be mapped to a SQL login; it cannot be remapped to a Windows login. 33018 16 Cannot remap user to login '%.*s', because the login is already mapped to a user in the database. 33019 16 Cannot create implicit user for the special login '%.*s'. 33020 16 A HASHED password cannot be set for a login that has CHECK_POLIC Y turned on. 33021 16 Failed to generate a user instance of SQL Server. Only local use r accounts, interactive users accounts, service accounts, or batch accounts can generate a user instance. The connection will be closed.%.*ls 33022 16 Cannot obtain cryptographic provider properties. Provider error code: %d.

33023 16 The %S_MSG is too long. Maximum allowed length is %d bytes. 33024 16 Cryptographic provider %S_MSG '%ls' in dll is different from the guid recorded in system catalog for provider with id %d. 33025 16 Invalid cryptograpihic provider property: %S_MSG. 33026 16 Cryptographic provider with guid '%ls' already exists. 33027 16 Cannot load library '%.*ls'. See errorlog for more information. 33028 16 Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%S_MSG) 33029 16 Cannot initialize cryptographic provider. Provider error code: % d. (%S_MSG) 33030 16 Cryptographic provider is not available. 33031 16 Cryptographic provider '%.*ls' is in disabled. 33032 16 SQL Crypto API version '%02d.%02d' implemented by provider is no t supported. Supported version is '%02d.%02d'. 33033 16 Specified key type or option '%S_MSG' is not supported by the pr ovider. 33034 16 Cannot specify algorithm for existing key. 33035 16 Cannot create key '%.*ls' in the provider. Provider error code: %d. (%S_MSG) 33036 10 Cannot drop the key with thumbprint '%.*ls' in the provider. 33037 16 Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG) 33038 16 Operation is not supported by cryptographic provider key. 33039 16 Invalid algorithm '%.*ls'. Provider error code: %d. (%S_MSG) 33040 16 Cryptographic provider key cannot be encrypted by password or ot her key. 33041 16 Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server. 33042 16 Cannot add %S_MSG because it is already mapped to a login. 33043 16 Cannot add %S_MSG '%.*ls' because there is already %S_MSG specif ied for the login. 33044 16 Cannot drop %S_MSG because there is %S_MSG referencing this prov ider. 33045 16 Cannot drop %S_MSG because it is not mapped to this login. 33046 16 Server principal '%.*ls' has no credential associated with %S_MS G '%.*ls'. 33047 16 Fail to obtain or decrypt secret for %S_MSG '%.*ls'. 33048 16 Cannot use %S_MSG under non-primary security context. 33049 16 Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG) 33050 16 Cannot create key '%.*ls' in the provider. Provider does not all ow specifying key names. 33051 16 Invalid algorithm id: %d. Provider error code: %d. (%S_MSG) 33052 16 Cryptographic provider key cannot be a temporary key. 33053 16 Extensible Key Management is disabled or not supported on this e dition of SQL Server. Use sp_configure 'EKM provider enabled' to enable it. 33054 16 Extensible key management is not supported in this edition of SQ L Server. 33055 16 Exception happened when calling cryptographic provider '%.*ls' i n the API '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Ex ception code: 0x%lx. 33056 16 Cannnot impersonate login '%.*ls' to access %S_MSG '%.*ls'. 33057 10 Cryptographic provider is now disabled. However users who have a n open cryptographic session with the provider can still use it. Restart the ser ver to disable the provider for all users. 33058 10 Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the serv er to drop the provider for all users. 33059 16 An error occurred while trying to flush all running audit sessio

ns. Some events may be lost. 33060 16 The format of supplied parameter sid is invalid. The sid might b e incorrect or the sid might describe the wrong type of user. 33069 16 CREATE CERTIFICATE statement cannot mix file and binary modes. R ewrite the statement using only the FILE or the BINARY keyword. 33070 16 The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must be at least 2 MB. 33071 16 This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command. 33072 16 The audit log file path is invalid. 33073 16 Cannot find %S_MSG '%.*ls' or you do not have the required permi ssions. 33074 16 Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operati on must be performed in the master database. 33075 16 Granular auditing is not available in this edition of SQL Server . For more information about feature support in the editions of SQL Server, see SQL Server Books Online. 33076 16 The specified maximum size limit is greater than the maximum val ue allowed. The maximum size limit must be less than 16777215 TB. 33077 16 RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UN LIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE. 33078 16 The containment setting in the master database does not match th e property of the database files. Use ALTER DATABASE to reset the containment pr operty. 33079 16 Cannot bind a default or rule to the CLR type '%s' because an ex isting sparse column uses this data type. Modify the data type of the sparse col umn or remove the sparse designation of the column. 33080 10 Cryptographic provider library '%.*ls' loaded into memory. This is an informational message only. No user action is required. 33081 10 Failed to verify Authenticode signature on DLL '%.*ls'. 33082 16 Cannot find Cryptographic provider library with guid '%ls'. 33083 16 Cannot create %S_MSG for %S_MSG '%ls' because it is not supporte d by the extensible key management provider '%ls'. 33084 16 The OPEN SYMMETRIC KEY statement cannot reference a symmetric ke y created from an Extensible Key Management (EKM) provider. Symmetric keys creat ed from an EKM provider are opened automatically for principals who can successf ully authenticate with the cryptographic provider. 33085 10 One or more methods cannot be found in cryptographic provider li brary '%.*ls'. 33086 10 SQL Server Audit failed to record %ls action. 33087 16 %S_MSG property of the key returned by EKM provider doesn't matc h the expected value 33088 16 The algorithm: %.*ls is not supported for EKM operations by SQL Server 33089 16 Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG) 33090 10 Attempting to load library '%.*ls' into memory. This is an infor mational message only. No user action is required. 33091 10 Warning: The certificate used for encrypting the database encryp tion key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever bec omes unavailable or if you must restore or attach the database on another server , you must have backups of both the certificate and the private key or you will not be able to open the database. 33092 10 Failed to verify the Authenticode signature of '%.*ls'. Signatur e verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that thi s is not an authentic release of SQL Server. Install a genuine copy of SQL Serve r or contact customer support. 33093 16 The Windows user or group '%s' is local or built-in. Use a Windo

ws domain user or domain group. 33094 10 An error occurred during Service Master Key %S_MSG 33095 10 Service Master Key could not be decrypted using one of its encry ptions. See sys.key_encryptions for details. 33096 10 A generic failure occurred during Service Master Key encryption or decryption. 33099 16 You cannot add server-scoped catalog views, system stored proced ures, or extended stored procedures to a database audit specification in a user database. Instead add them to a database audit specification in the master datab ase. 33101 16 Cannot use %S_MSG '%.*ls', because its private key is not presen t or it is not protected by the database master key. SQL Server requires the abi lity to automatically access the private key of the %S_MSG used for this operati on. 33102 16 Cannot encrypt a system database. Database encryption operations cannot be performed for 'master', 'model', 'tempdb', 'msdb', or 'resource' data bases. 33103 16 A database encryption key already exists for this database. 33104 16 A database encryption key does not exist for this database. 33105 16 Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the databa se encryption key. 33106 16 Cannot change database encryption state because no database encr yption key is set. 33107 16 Cannot enable database encryption because it is already enabled. 33108 16 Cannot disable database encryption because it is already disable d. 33109 16 Cannot disable database encryption while an encryption, decrypti on, or key change scan is in progress. 33110 16 Cannot change database encryption key while an encryption, decry ption, or key change scan is in progress. 33111 16 Cannot find server %S_MSG with thumbprint '%.*ls'. 33112 10 Beginning database encryption scan for database '%.*ls'. 33113 10 Database encryption scan for database '%.*ls' is complete. 33114 10 Database encryption scan for database '%.*ls' was aborted. Reiss ue ALTER DB to resume the scan. 33115 16 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later. 33116 16 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%.*ls'. Try again later. 33117 16 Transparent Data Encryption is not available in the edition of t his SQL Server instance. See books online for more details on feature support in different SQL Server editions. 33118 16 Cannot enable or modify database encryption on a database that i s read-only, has read-only files or is not recovered. 33119 16 Cannot modify filegroup read-only/read-write state while an encr yption transition is in progress. 33120 16 In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider. 33121 16 The %S_MSG '%ls' does not have a login associated with it. Crea te a login and credential for this key to automatically access the extensible ke y management provider '%ls'. 33122 16 This command requires a database encryption scan on database '%. *ls'. However, the database has changes from previous encryption scans that are pending log backup. Take a log backup and retry the command. 33123 16 Cannot drop or alter the database encryption key since it is cur rently in use on a mirror or secondary availability replica. Retry the command a fter all the previous reencryption scans have propagated to the mirror or second ary availability replicas or after availability relationship has been disabled. 33124 10 Database encryption scan for database '%.*ls' cannot complete si

nce one or more files are offline. Bring the files online to run the scan to com pletion. 33125 10 Can not create login token because there are too many secondary principals. The maximum number of allowed secondary principals allowed is %lu. T o fix this, remove the login from a server role. 33126 10 Database encryption key is corrupted and cannot be read. 33127 16 The %S_MSG cannot be dropped because it is used by one or more d atabases to encrypt a Database Encryption Key. 33128 16 Encryption failed. Key uses deprecated algorithm '%.*ls' which i s no longer supported. 33129 16 Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission instead. 33201 17 An error occurred in reading from the audit file or file-pattern : '%s'. The SQL service account may not have Read permission on the files, or th e pattern may be returning one or more corrupt files. 33202 17 SQL Server Audit could not write to file '%s'. 33203 17 SQL Server Audit could not write to the event log. 33204 17 SQL Server Audit could not write to the security log. 33205 10 Audit event: %s. 33206 17 SQL Server Audit failed to create the audit file '%s'. Make sure that the disk is not full and that the SQL service account has the required per missions to create and write to the file. 33207 17 SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log . 33208 17 SQL Server Audit failed to access the security log. Make sure th at the SQL service account has the required permissions to access the security l og. 33209 10 Audit '%.*ls' has been changed to ON_FAILURE=CONTINUE because th e server was started by using the -m flag. because the server was started with t he -m flag. 33210 10 SQL Server Audit failed to start, and the server is being shut d own. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass A udit-generated shutdowns when the server is starting. 33211 15 A list of subentities, such as columns, cannot be specified for entity-level audits. 33212 15 There is an invalid column list after the object name in the AUD IT SPECIFICATION statement. 33213 16 All actions in an audit specification statement must be at the s ame scope. 33214 17 The operation cannot be performed because SQL Server Audit has n ot been started. 33215 10 One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with ea ch error. 33216 10 SQL Server was started using the -f flag. SQL Server Audit is di sabled. This is an informational message. No user action is required. 33217 10 SQL Server Audit is starting the audits. This is an informationa l message. No user action is required. 33218 10 SQL Server Audit has started the audits. This is an informationa l message. No user action is required. 33219 10 The server was stopped because SQL Server Audit '%.*ls' is confi gured to shut down on failure. To troubleshoot this issue, use the -m flag (Sing le User Mode) to bypass Audit-generated shutdowns when the server is starting. 33220 16 Audit actions at the server scope can only be granted when the c urrent database is master. 33221 16 You can only create audit actions on objects in the current data base. 33222 10 Audit '%.*ls' failed to %.*ls. For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_t

ype = 'RING_BUFFER_XE_LOG'. 33223 16 ALTER SERVER AUDIT requires the STATE option to be specified wit hout using any other options. 33224 16 The specified pattern did not return any files or does not repre sent a valid file share. Verify the pattern parameter and rerun the command. 33225 16 The specified values for initial_file_name and audit_record_offs et do not represent a valid location within the audit file set. Verify the file name and offset location, and then rerun the command. 33226 10 The fn_get_audit_file function is skipping records from '%.*ls' at offset %I64d. 33227 16 The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher. 33228 16 You cannot configure SQL Server Audit to shutdown the server bec ause you do not have the permission to shut down the server. Contact your system administrator. 33229 16 Changes to an audit specification must be done while the audit s pecification is disabled. 33230 16 An audit specification for audit '%.*ls' already exists. 33231 16 You can only specify securable classes DATABASE, SCHEMA, or OBJE CT in AUDIT SPECIFICATION statements. 33232 16 You may not add a role to Sysadmin. 33233 16 You can only create a user with a password in a contained databa se. 33234 16 The parameter %s cannot be provided for users that cannot authen ticate in a database. 33235 16 The parameter %s cannot be provided for users that cannot authen ticate in a database. Remove the WITHOUT LOGIN or PASSWORD clause. 33236 16 The default language parameter can only be provided for users in a contained database. 33237 16 Cannot use parameter %s for Windows users or groups. 33238 16 MAX_FILES and MAX_ROLLOVER_FILES options cannot be specified tog hether. 33239 16 An error occurred while auditing this operation. Fix the error i n the audit and then retry this operation. 33240 16 A failure occurred during initializing of an Audit. See the erro rlog for details. 33241 16 Failed to configure user instance on startup. Error updating the idle timeout. 33242 16 When providing a sid, the user must be a user without login or a user with password. 33243 16 Failed to generate a user instance of SQL Server due to a failur e in setting access control list on the user instance's process. The connection will be closed.%.*ls 33301 16 The %ls that is specified for conversation priority '%.*ls' is n ot valid. The value must be between 1 and %d characters long. 33302 16 The %ls that is specified for conversation priority '%.*ls' is n ot valid. The value must be between 1 and 10. 33303 16 A conversation priority already exists in the database with eith er the name '%.*ls' or the properties %ls='%ls', %ls='%ls', and %ls='%.*ls'. Eit her use a unique name or a unique set of properties. 33304 16 The transmission queue row with conversation handle '%ls' and me ssage sequence number %d references a missing multicast message body row with re ference %d. 33305 16 The multicast message body row with reference %d should have ref erence count value of %d. 33306 16 The unreferenced message with reference %d has been deleted from the message body table. 33307 16 The message with reference %d has been updated to a reference co unt of %d in the message body table. 33308 10 The queue %d in database %d has activation enabled and contains

unlocked messages but no RECEIVE has been executed for %u seconds. 33309 10 Cannot start cluster endpoint because the default %S_MSG endpoin t configuration has not been loaded yet. 33401 16 FILESTREAM database options cannot be set on system databases su ch as '%.*ls'. 33402 16 An invalid directory name '%.*ls' was specified. Use a valid Win dows directory name. 33403 16 The case-sensitive or binary collation '%.*ls' cannot be used wi th the COLLATE_FILENAME option. Change the collation to a case-insensitive colla tion type. 33404 16 The database default collation '%.*ls' is case sensitive and can not be used to create a FileTable. Specify a case insensitive collation with the COLLATE_FILENAME option. 33405 16 An error occurred during the %S_MSG %S_MSG operation on a FileTa ble object. (HRESULT = '0x%08x'). 33406 16 An invalid filename, '%.*ls', caused a FileTable check constrain t error. Use a valid Windows filename. 33407 16 An invalid path locator caused a FileTable check constraint erro r. The path locator cannot indicate a root row. Correct the path locator or use the default value. 33408 16 The operation caused a FileTable check constraint error. A dire ctory entry cannot have a data stream associated with the row. Remove the blob d ata or clear the is_directory flag. 33409 16 The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated with the row. Inse rt file data or use 0x to insert a zero length file. 33410 16 An invalid path locator caused a FileTable check constraint erro r. The parent of a row's path locator must be a directory, not a file. Correct the path locator to refer to a parent that is a directory. 33411 16 The option '%.*ls' is only valid when used on a FileTable. Remov e the option from the statement. 33412 16 The option '%.*ls' is not valid when used with the '%.*ls' synta x. Remove the option from the statement. 33413 16 The option '%.*ls' can only be specified once in a statement. Re move the duplicate option from the statement. 33414 16 FileTable objects require the FILESTREAM database option DIRECTO RY_NAME to be non-NULL. To create a FileTable in the database '%.*ls', set the D IRECTORY_NAME option to a non-NULL value using ALTER DATABASE. Or, to set the DI RECTORY_NAME option to NULL, in the database '%.*ls' disable or drop the existin g FileTables. 33415 16 FILESTREAM DIRECTORY_NAME '%.*s' attempting to be set on databas e '%.*s' is not unique in this SQL Server instance. Provide a unique value for t he database option FILESTREAM DIRECTORY_NAME to enable non-transacted access. 33416 10 When the FILESTREAM database option NON_TRANSACTED_ACCESS is set to FULL and the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION options are on, T-SQL and transactional read access to FILESTREAM data in the context o f a FILETABLE is blocked. 33417 16 An invalid path locator caused a FileTable check constraint erro r. The path locator has a level of %d, which is deeper than the limit of %d sup ported by FileTable. Reduce the depth of the directory hierarchy. 33418 16 FILETABLE_DIRECTORY '%.*s' attempting to be set on table '%.*s' is not unique in the database '%.*s'. Provide a unique value for the option FILE TABLE_DIRECTORY to this operation. 33419 16 Function %ls is only valid on the varbinary(max) FILESTREAM colu mn in a FileTable. 33420 16 Unable to process object '%.*s' because it is a three-part or fo ur-part name. Specifying the server or database is not supported in the object i dentifer. 33421 16 The object name '%.*s' is not a valid FileTable object. 33422 16 The column '%.*s' cannot be added to table '%.*s' as it is a Fil

eTable. Adding columns to the fixed schema of a FileTable object is not permitte d. 33423 16 Invalid FileTable path name or format. 33424 16 Invalid computer host name in the FileTable path. 33425 16 Invalid share name in the FileTable path. 33426 16 INSERT, UPDATE, DELETE, or MERGE to FileTable '%.*ls' is not all owed inside a trigger on a FileTable. 33427 16 Function %ls is not allowed on the deleted table inside a trigge r. 33428 14 User does not have permission to kill non-transacted FILESTREAM handles in database ID %d. 33429 16 The non-transacted FILESTREAM handle %d does not exist. 33430 10 Killed %d non-transactional FILESTREAM handles from database ID %d. 33431 16 An invalid path locator caused a FileTable check constraint erro r. The path locator has a length of %d, which is longer than the limit of %d al lowed for depth %d. Reduce the length of the path locator. 33433 10 Unable to perform the Filetable lost update recovery for databas e id %d. 33434 16 The current state of the database '%.*s' is not compatible with the specified FILESTREAM non-transacted access level. The database may be read o nly, single user or set to emergency state. 33435 16 Cannot publish the FileTable '%ls' for replication. Replication is not supported for FileTable objects. 33436 16 Cannot enable Change Data Capture on the FileTable '%ls'. Chang e Data Capture is not supported for FileTable objects. 33437 16 Cannot publish the logbased view '%ls' for replication. Replica tion is not supported for logbased views that depend on FileTable objects. 33438 16 Cannot enable Change Tracking on the FileTable '%.*ls'. Change Tracking is not supported for FileTable objects. 33439 16 Cannot use IGNORE_CONSTRAINTS hint when inserting into FileTable '%.*ls', unless FILETABLE_NAMESPACE is disabled. 33440 16 When inserting into FileTable '%.*ls' using BCP or BULK INSERT, either CHECK_CONSTRAINTS option needs to be on, or FILETABLE_NAMESPACE needs to be disabled on the table. 33441 16 The FileTable '%.*s' cannot be partitioned. Partitioning is not supported on FileTable objects. 33442 16 The handle ID %d is opened against the server root share and can not be killed. The lifetime of the handle is controlled by the client who origin ally opened it. 33443 16 The database '%.*s' cannot be enabled for both FILESTREAM non-tr ansacted access and Database Mirroring. 33444 16 The database '%.*s' cannot be enabled for both FILESTREAM non-tr ansacted access and HADR. 33445 16 The database '%.*s' is a readable secondary database in an avail ability group and cannot be enabled for FILESTREAM non-transacted access. 33446 16 The FILESTREAM database configuration cannot be changed for data base '%.*s'. The database is either a mirror database in Database Mirroring, or is in a secondary replica of an AlwaysOn availability group. Connect to the se rver instance that hosts the primary database replica, and retry the operation. 33447 16 Cannot access file_stream column in FileTable '%.*ls', because F ileTable doesn't support row versioning. Either set transaction level to somethi ng other than READ COMMITTED SNAPSHOT or SNAPSHOT, or use READCOMMITTEDLOCK tabl e hint. 33448 16 Cannot disable clustered index '%.*ls' on FileTable '%.*ls' beca use the FILETABLE_NAMESPACE is enabled. 33449 10 FILESTREAM File I/O access is enabled, but no listener for the a vailability group is created. A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windo ws Server Failover Clustering (WSFC) node. This might limit the usability of FIL

ESTEAM File I/0 access after an availability group failover. Therefore, we recom mend that you create a listener for each availability group. For information abo ut how to create an availability group listener, see SQL Server Books Online. 33450 10 FILESTREAM File I/O access is enabled. One or more availability groups ('%ls') currently do not have a listener. A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windows Server Failover Clustering (WSFC) node. This might limit the usability of FILESTEAM File I/0 access after an availability group failover. Therefore, we recommend that you create a listener for each availability group. For information about how to create an availability group listener, see SQL Ser ver Books Online. 34001 16 Dialog with queue 'syspolicy_event_queue' has encountered an err or: %s. 34002 16 Dialog with queue 'syspolicy_event_queue' has ended. 34003 16 Error number %d was encountered while processing an event. The e rror message is: %s. 34004 16 Execution mode %d is not a valid execution mode. 34010 16 %s '%s' already exists in the database. 34011 16 Specified value for property %s cannot be used with execution mo de %d. 34012 16 Cannot delete %s referenced by a %s. 34013 16 %s '%s' is referenced by a '%s'. Cannot add another reference. 34014 16 Facet does not exist. 34015 16 Policy group %s does not exist. 34016 16 Invalid target filer: %s. Only filters that restrict the first l evel below the Server node are allowed. 34017 16 Automated policies cannot reference conditions that contain scri pt. 34018 16 Target type "%s" is not a valid target type. 34019 16 Object "%s" is invalid. 34020 16 Configuration option "%s" is unknown. 34021 16 Invalid value type for configuration option "%s". Expecting "%s" . 34022 16 Policy automation is turned off. 34050 16 %ls 34051 16 %ls 34052 16 %ls 34053 16 %ls 34054 16 Policy Management cannot be enabled on this edition of SQL Serve r. 34101 20 An error was encountered during object serialization operation. Examine the state to find out more details about this error. 34102 16 An object in serialized stream has version %u but maximum suppor ted version of this class is %u. 34103 16 Error in formatter during serialize/deserialize. Required to pro cess %d elements but processed only %d elements. 34104 16 An error was encountered during object serialization operation. The object that failed serialization is %hs. 34901 16 The global lock manager encountered a severe failure. 35001 16 Parent Server Group does not exist. 35002 16 Server type and parent Server Group type are not the same 35003 16 Cannot move node to one of its children 35004 16 Could not find server group 35005 16 An invalid value NULL was passed in for @server_group_id. 35006 16 An invalid value NULL was passed in for @server_id. 35007 16 Could not find shared registered server. 35008 16 Cannot delete system shared server groups. 35009 16 An invalid value NULL was passed in for @server_type. 35010 16 An invalid value %d was passed in for parameter @server_type. 35011 16 The @server_name parameter cannot be a relative name.

35012 16 You cannot add a shared registered server with the same name as the Configuration Server. 35100 16 Error number %d in the THROW statement is outside the valid rang e. Specify an error number in the valid range of 50000 to 2147483647. 35201 10 A connection timeout has occurred while attempting to establish a connection to availability replica '%ls' with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance. 35202 10 A connection for availability group '%ls' from availability repl ica '%ls' with id [%ls] to '%ls' with id [%ls] has been successfully establishe d. This is an informational message only. No user action is required. 35203 16 Unable to establish a connection between instance '%ls' with id [%ls] and '%ls' with id [%ls] due to a transport version mismatch. 35204 10 The connection between server instances '%ls' with id [%ls] and '%ls' with id [%ls] has been disabled because the database mirroring endpoint wa s either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT T ransact-SQL statement with STATE = STARTED. 35205 16 Could not start the AlwaysOn Availability Groups transport manag er. This failure probably occurred because a low memory condition existed when t he message dispatcher started up. If so, other internal tasks might also have ex perienced errors. Check the SQL Server error log and the Windows error log for a dditional error messages. If a low memory condition exists, investigate and corr ect its cause. 35206 10 A connection timeout has occurred on a previously established co nnection to availability replica '%ls' with id [%ls]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolv ing role. 35207 16 Connection attempt on availability group id '%ls' from replica i d '%ls' to replica id '%ls' failed because of error %d, severity %d, state %d. 35208 16 Availability-group DDL operations are permitted only when you ar e using the master database. Run the USE MASTER command, and retry your availab ility-group DDL command. 35209 16 The %ls operation failed for availability replica '%.*ls', becau se the backup priority value is outside the valid range. The valid range is betw een %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation. 35210 16 Failed to modify options for availability replica '%.*ls' in ava ilability group '%.*ls'. The specified availability group does not contain an av ailability replica with specified name. Verify that availability group name and availability replica name are correct, then retry the operation. 35211 16 The %ls operation is not allowed. The operation attempted to ch ange the configuration of availability replica '%.*ls' to the asynchronous-commi t availability mode with automatic failover, which is an invalid configuration. Either change the failover mode to manual or the availability mode to synchrono us commit, and retry the operation. 35212 16 The %ls operation is not allowed by the current availability-gro up configuration. This operation would exceed the maximum number of %d synchron ous-commit availability replicas in availability group '%.*ls'. Change one of t he existing synchronous-commit replicas to the asynchronous-commit availability mode, and retry the operation. 35213 16 The %ls operation is not allowed by the current availability-gro up configuration. This operation would exceed the maximum number of %d automati c failover targets in availability group '%.*ls'. Change one of the existing sy nchronous-commit replicas to the manual failover mode, and retry the operation. 35214 16 The %ls operation failed for availability replica '%.*ls'. The minimum value for session timeout is %d. Retry the operation specifying a valid session-timeout value. 35215 16 The %ls operation is not allowed on availability replica '%.*ls' , because automatic failover mode is an invalid configuration on a SQL Server Fa ilover Cluster Instance. Retry the operation by specifying manual failover mode

. 35217 16 The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade AlwaysOn Availability Groups performance. Use the "max worke r threads" configuration option to increase number of allowable threads. 35220 16 Could not process the operation. AlwaysOn Availability Groups re plica manager is waiting for the host computer to start a Windows Server Failove r Clustering (WSFC) cluster and join it. Either the local computer is not a clus ter node, or the local cluster node is not online. If the computer is a cluster node, wait for it to join the cluster. If the computer is not a cluster node, ad d the computer to a WSFC cluster. Then, retry the operation. 35221 16 Could not process the operation. AlwaysOn Availability Groups re plica manager is disabled on this instance of SQL Server. Enable AlwaysOn Availa bility Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable AlwaysOn Availability Groups, see SQL Server Books Online . 35222 16 Could not process the operation. AlwaysOn Availability Groups do es not have permissions to access the Windows Server Failover Clustering (WSFC) cluster. Disable and re-enable AlwaysOn Availability Groups by using the SQL Se rver Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable AlwaysOn Av ailability Groups, see SQL Server Books Online. 35223 16 Cannot add %d availability replica(s) to availability group '%.* ls'. The availability group already contains %d replica(s), and the maximum num ber of replicas supported in an availability group is %d. 35224 16 Could not process the operation. AlwaysOn Availability Groups f ailed to load the required Windows Server Failover Clustering (WSFC) library. Ve rify that the computer is a node in a WSFC cluster. You will need to restart th e SQL Server instance to reload the required library functions. 35225 16 Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support A lwaysOn Availability Groups. Reinstall SQL Server in the native 64-bit edition, and re-enable AlwaysOn Availability Groups. Then, restart the SQL Server servic e, and retry the operation. For information about how to enable and disable Alwa ysOn Availability Groups, see SQL Server Books Online. 35226 16 Could not process the operation. AlwaysOn Availability Groups h as not started because the instance of SQL Server is not running as a service. R estart the server instance as a service, and retry the operation. 35228 16 The attempt to set the failure condition level for availability group '%.*ls' failed. The specified level value is out of the valid range [%u, % u]. Reenter the command specifying a valid failure condition level value. 35229 16 The attempt to set the health check timeout value for availabili ty group '%.*ls' failed. The specified timeout value is less than %u millisecond s. Reenter the command specifying a valid health check timeout value. 35230 16 The specified computer name is either an empty string or is long er than %d Unicode characters. Reenter the command specifying a valid computer n ame. 35231 16 The specified server instance name, '%ls', is invalid. Reenter t he command specifying a valid instance name. 35232 16 The specified endpoint URL '%.*ls' is invalid. Reenter the comma nd specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online. 35233 16 Cannot create an availability group containing %d availability r eplica(s). The maximum number of availability replicas in an availability g roup is %d. Reenter your CREATE AVAILABILITY GROUP command specifying from one to five availability replicas. 35234 16 Database name '%ls' was specified more than once. Reenter the co mmand, specifying each database name only once. 35235 16 The system name '%ls' was specified more than once in the REPLIC

A ON clause of this command. Reenter the command, specifying a different instanc e of SQL Server for each replica. 35236 15 The endpoint URL was not specified for the availability replica hosted by server instance '%.*ls'. Reenter the command, specifying the endpoint URL of this instance of SQL Server. 35237 16 None of the specified replicas for availability group %.*ls maps to the instance of SQL Server to which you are connected. Reenter the command, specifying this server instance to host one of the replicas. This replica will b e the initial primary replica. 35238 16 Database '%.*ls' cannot be added to availability group '%.*ls'. The database does not exist on this SQL Server instance. Verify that the datab ase name is correct, then retry the operation. 35239 16 The ALTER DATABASE <database-name> SET HADR SUSPEND (or SET HADR RESUME) statement failed on database '%.*ls' of availability group '%.*ls''. Ei ther the availability group does not contain the specified database, or the data base has not joined the availability group, or the database has not yet started. Reenter the command after the database is online and has joined the availabilit y group. 35240 16 Database '%.*ls' cannot be joined to or unjoined from availabili ty group '%.*ls'. This operation is not supported on the primary replica of the availability group. 35242 16 Cannot complete this ALTER DATABASE <database-name> SET HADR ope ration on database '%.*ls'. The database is not joined to an availability group. After the database has joined the availability group, retry the command. 35243 16 Failed to set resource property '%.*ls' for availability group ' %.*ls'. The operation encountered SQL Server error %d. When the cause of the e rror has been resolved, retry the ALTER AVAILABILITY GROUP command later. 35244 16 Database '%.*ls' cannot be added to availability group '%.*ls'. The database is currently joined to another availability group. Verify that th e database name is correct and that the database is not joined to an availabilit y group, then retry the operation. 35246 16 Failed to create the availability group. A SQL Server instance n ame could not be validated because the dynamic link library (DLL) file '%ls' cou ld not be located (Windows System Error %d). Verify that the specified server in stance exists. If it exists, the DLL file might be missing from the server insta nce. 35247 16 Failed to create the availability group. A SQL Server instance n ame could not be validated because the dynamic link library (DLL) file '%ls' cou ld not be loaded (Windows System Error %d). 35249 16 An attempt to add or join a system database, '%.*ls', to an avai lability group failed. Specify only user databases for this operation. 35250 16 The connection to the primary replica is not active. The comman d cannot be processed. 35251 16 This command can be run only on the primary replica. Connect to the primary replica, and retry the command. 35252 16 The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command. 35253 16 Database "%.*ls" is not in the correct state to become the prima ry database. The log must be restored from the previous primary replica to brin g the database out of out of the reinitializing state. 35254 16 An error occurred while accessing the availability group metadat a. Remove this database or replica from the availability group, and reconfigure the availability group to add the database or replica again. For more informatio n, see the ALTER AVAILABILITY GROUP Transact-SQL statement in SQL Server Books O nline. 35255 16 An attempt to start database '%.*ls' failed because the database is already started and online. 35256 16 The session timeout value was exceeded while waiting for a respo nse from the other availability replica in the session. That replica or the netw ork might be down, or the command might be misconfigured. If the partner is runn

ing and visible over the network, retry the command using correctly configured p artner-connection parameters. 35257 16 AlwaysOn Availability Groups Send Error (Error code 0x%X, "NOT OK") was returned when sending a message for database ID %d. If the partner is r unning and visible over the network, retry the command using correctly configure d partner-connection parameters. 35259 16 Database '%.*ls' is already participating in a different availa bility group. 35260 16 During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and grou p database ID %ls. Recovery was terminated. The most likely cause of this error is that the availability group manager is not running, but the cause could be a metadata error. Ensure that the availability group manager and the WSFC cluster are started, and retry the recovery operation. 35261 16 Attempt to perform an AlwaysOn Availability Groups operation on a system database, '%ls', failed. System databases are not supported by AlwaysO n Availability Groups. 35262 17 Skipping the default startup of database '%.*ls' because the dat abase belongs to an availability group (Group ID: %d). The database will be sta rted by the availability group. This is an informational message only. No user a ction is required. 35263 16 During the undo phase, a function call (%ls) to the primary repl ica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Server error log for the primary replica. If an error occurred on the primar y database, you might need to suspend the secondary database, fix the issue on t he primary database, and then resume the database. 35264 10 AlwaysOn Availability Groups data movement for database '%.*ls' has been suspended for the following reason: "%S_MSG" (Source ID %d; Source stri ng: '%.*ls'). To resume data movement on the database, you will need to resume t he database manually. For information about how to resume an availability databa se, see SQL Server Books Online. 35265 10 AlwaysOn Availability Groups data movement for database '%.*ls' has been resumed. This is an informational message only. No user action is requi red. 35266 10 AlwaysOn Availability Groups connection with %S_MSG database est ablished for %S_MSG database '%.*ls' on the availability replica with Replica ID : {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational m essage only. No user action is required. 35267 10 AlwaysOn Availability Groups connection with %S_MSG database ter minated for %S_MSG database '%.*ls' on the availability replica with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational me ssage only. No user action is required. 35268 16 Synchronization of a secondary database, '%.*ls', was interrupte d, leaving the database in an inconsistent state. The database will enter the RE STORING state. To complete recovery and bring the database online, use current l og backups from the primary database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log b ackups. 35269 21 Synchronization of a secondary database, '%.*ls', was interrupte d, leaving the database in an inconsistent state. The database will be marked SU SPECT. To return the database to a consistent state, restore it from a clean dat abase backup followed by all subsequent log backups. 35270 10 Received a corrupt FileStream transport message. The '%ls' messa ge section is invalid. 35272 16 Either nvalid parameters were supplied for sys.sp_availability_g roup_command_internal or user does not have permissions to execute this procedur e. 35273 10 Bypassing recovery for database '%ls' because it is marked as an inaccessible availability database. The session with the primary replica was in

terrupted while reverting the database to the common recovery point. Either the WSFC node lacks quorum or the communications links are broken because of problem s with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, you need to determine wha t has changed in the session configuration and undo the change. 35274 10 Recovery for availability database '%ls' is pending until the se condary replica receives additional transaction log from the primary before it c omplete and come online. Ensure that the server instance that hosts the primary replica is running. 35275 16 A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the '%.*ls' d atabase in a potentially damaged state. The database cannot be joined while in t his state. Restore the database, and retry the join operation. 35276 17 Failed to allocate and schedule an AlwaysOn Availability Groups task for database '%ls'. Manual intervention may be required to resume synchroni zation of the database. If the problem persists, you might need to restart the l ocal instance of SQL Server. 35278 16 Availability database '%.*ls', which is in the secondary role, i s being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required. 35279 16 The attempt to join database '%.*ls' to the availability group w as rejected by the primary database with error '%d'. For more information, see t he SQL Server error log for the primary replica. 35280 16 Database '%.*ls' cannot be added to availability group '%.*ls'. The database is already joined to the specified availability group. Verify tha t the database name is correct and that the database is not joined to an availab ility group, then retry the operation. 35281 16 Database '%.*ls' cannot be removed from availability group '%.*l s'. The database is not joined to the specified availability group. Verify tha t the database name and the availability group name are correct, then retry the operation. 35282 16 Availability replica '%.*ls' cannot be added to availability gro up '%.*ls'. The availability group already contains an availability replica wit h the specified name. Verify that the availability replica name and the availab ility group name are correct, then retry the operation. 35283 16 Availability replica '%.*ls' cannot be removed from availability group '%.*ls'. The availability group does not contain an availability replica with the specified name. Verify that the availability replica name is correct, then retry the operation. 35284 16 Availability replica '%.*ls' cannot be removed from availability group '%.*ls', because this replica is on the local instance of SQL Server. If the local availability replica is a secondary replica, connect to the server in stance that is currently hosting the primary replica, and re-run the command. 35285 16 The recovery LSN %S_LSN was identified for the database with ID %d. This is an informational message only. No user action is required. 35286 16 Using the recovery LSN %S_LSN stored in the metadata for the dat abase with ID %d. This is an informational message only. No user action is requi red. 35287 16 AlwaysOn Availability Groups transport for availability database "%.*ls" failed to decompress the log block whose LSN is %S_LSN. This error can be caused by a corrupt network packet or a compression version mismatch. The d atabase replica has been put into the SUSPENDED state. Resume the availability database. If the error keeps reoccurring, investigate the root cause. 35288 16 AlwaysOn Availability Groups log apply for availability database "%.*ls" has received an out-of-order log block. The expected LSN was %S_LSN. The received LSN was %S_LSN. The database replica has been put into the SUSPEND ED state. Resume the availability database. If the error reoccurs, contact Cus tomer Support Services. 35289 16 Failed to send request for file '%.*ls' to the '%.*ls' primary d atabase for the local secondary database. Resuming the database will be retried

automatically. 35290 16 Failed to wait for completion of file requests from the '%.*ls' primary database for the local secondary database. Resuming the database will be retried automatically. 35291 10 Failed to acquire exclusive access to the extended recovery fork stack (error %d). If the problem persists, you might need to restart the instan ce of SQL Server. 35292 16 An internal error occurred when performing an operation on exten ded recovery forks. This is an informational message only. No user action is req uired. 35293 16 Error in retrieving extended recovery forks from the primary rep lica. The extended-recovery-fork stack changed while being retrieved by the seco ndary replica. Retry the operation. 35294 16 Log backup for database "%.*ls" on a secondary replica failed be cause a synchronization point could not be established on the primary database. Either locks could not be acquired on the primary database or the database is no t operating as part of the availability replica. Check the database status in th e SQL Server error log of the server instance that is hosting the current primar y replica. If the primary database is participating in the availability group, r etry the operation. 35295 16 Log backup for database "%.*ls" on a secondary replica failed be cause the last backup LSN (0x%ls) from the primary database is greater than the current local redo LSN (0x%ls). No log records need to be backed up at this time . Retry the log-backup operation later. 35296 16 Log backup for database "%.*ls" on secondary replica failed bec ause the new backup information could not be committed on primary database. Chec k the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating i n the availability group, retry the operation. 35297 10 Log backup for database "%.*ls" on secondary replica created bac kup files successfully but could not ensure that a backup point has been committ ed on the primary. This is an informational message only. Preserve this log ba ckup along with the other log backups of this database. 35298 10 The backup on the secondary database "%.*ls" was terminated, but a terminate backup message could not be sent to the primary replica. This is an informational message only. The primary replica should detect this error and cl ean up its backup history accordingly. 35299 10 Nonqualified transactions are being rolled back in database %.*l s for an AlwaysOn Availability Groups state change. Estimated rollback completio n: %d%%. This is an informational message only. No user action is required. 35301 15 CREATE INDEX statement failed because a columnstore index cannot be unique. Create the columnstore index without the UNIQUE keyword or create a unique index without the COLUMNSTORE keyword. 35302 15 CREATE INDEX statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. Create the columnsto re index without specifying a sort order. 35305 15 CREATE INDEX statement failed because a columnstore index cannot be created on a view. Consider creating a columnstore index on the base table o r creating an index without the COLUMNSTORE keyword on the view. 35307 15 CREATE INDEX statement failed because column '%.*ls' on table '% .*ls' is a computed column and a columnstore index cannot be created on a comput ed column. Consider creating a nonclustered columnstore index on a subset of col umns that does not include the column. 35308 15 CREATE INDEX statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without the predicat e filter. 35309 15 CREATE INDEX statement failed because a columnstore index cannot be created on a sparse column. Consider creating a nonclustered columnstore ind ex on a subset of columns that does not include any sparse columns. 35311 15 CREATE INDEX statement failed because a columnstore index cannot

have included columns. Create the columnstore index on the desired columns wi thout specifying any included columns. 35312 15 CREATE INDEX statement failed because a columnstore index cannot be created on a column with filestream data. Consider creating a nonclustered c olumnstore index on a subset of columns that does not include any columns with f ilestream data. 35313 15 CREATE INDEX statement failed because specifying FILESTREAM_ON i s not allowed when creating a columnstore index. Consider creating a columnstore index on columns without filestream data and omit the FILESTREAM_ON specificati on. 35314 15 CREATE INDEX statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore index on a subset of columns in the table that does not contain a column set or any sp arse columns. 35315 15 CREATE INDEX statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more details o n feature support in different SQL Server editions. 35316 15 CREATE INDEX statement failed because a columnstore index must b e partition-aligned with the base table. Create the columnstore index using the same partition function and same (or equivalent) partition scheme as the base ta ble. If the base table is not partitioned, create a nonpartitioned columnstore index. 35317 15 CREATE INDEX statement failed because specifying %S_MSG is not a llowed when creating a columnstore index. Consider creating a columnstore index without specifying %S_MSG. 35318 15 CREATE INDEX statement failed because the %S_MSG option is not a llowed when creating a columnstore index. Create the columnstore index without s pecifying the %S_MSG option. 35320 15 CREATE INDEX statement failed because specifying DATA_COMPRESSIO N is not allowed when creating a columnstore index. Consider creating a columnst ore index without specifying DATA_COMPRESSION. Columnstore indexes are always c ompressed automatically. 35325 15 ALTER TABLE statement failed because the definition of a column cannot be changed if the column is part of a columnstore index. Consider droppin g the columnstore index, altering the column, then creating a new columnstore in dex. 35326 15 ALTER INDEX statement failed because a columnstore index cannot be reorganized. Reorganization of a columnstore index is not necessary. 35327 15 ALTER INDEX REBUILD statement failed because specifying %S_MSG i s not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying %S_MSG. 35328 15 ALTER INDEX REBUILD statement failed because the %S_MSG option i s not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying the %S_MSG option. 35329 15 ALTER INDEX REBUILD statement failed because specifying DATA_COM PRESSION is not allowed when rebuilding a columnstore index. Rebuild the columns tore index without specifying DATA_COMPRESSION. Columnstore indexes are always compressed automatically. 35330 16 %S_MSG statement failed because data cannot be updated in a tabl e with a columnstore index. Consider disabling the columnstore index before issu ing the %S_MSG statement, then rebuilding the columnstore index after %S_MSG is complete. 35334 15 DBCC DBREINDEX failed because specifying FILLFACTOR is not allow ed when creating or rebuilding a columnstore index. Rebuild the columnstore inde x without specifying FILLFACTOR. 35336 15 CREATE INDEX statement failed because specifying key list is mis sing when creating an index. Create the index with specifying key list . 35337 16 UPDATE STATISTICS failed because statistics cannot be updated on a columnstore index. UPDATE STATISTICS is valid only when used with the STATS_ STREAM option.

35338 16 Clustered columnstore index is not supported. 35339 16 Multiple nonclustered columnstore indexes are not supported. 35340 16 Conversion between columnstore index and relational index is not supported. 35341 16 CREATE INDEX statement failed. A columnstore index cannot includ e a decimal or numeric data type with a precision greater than 18. Reduce the p recision of column '%.*ls' to 18 or omit column '%.*ls'. 35342 16 CREATE INDEX statement failed. A columnstore index cannot includ e a datetimeoffset data type with a precision greater than 2. Reduce the precisi on of column '%.*ls' to 2 or omit column '%.*ls'. 35343 15 CREATE INDEX statement failed. Column '%.*ls'has a data type tha t cannot participate in a columnstore index. Omit column '%.*ls'. 35344 16 MERGE clause of ALTER PARTITION statement failed because two non empty partitions containing a columnstore index cannot be merged. Consider disab ling the columnstore index before issuing the ALTER PARTITION statement, then re building the columnstore index after ALTER PARTITION is complete. 35345 16 MERGE clause of ALTER PARTITION statement failed because two par titions on different filegroups cannot be merged if either partition contains co lumnstore index data. Consider disabling the columnstore index before issuing th e ALTER PARTITION statement, then rebuilding the columnstore index after ALTER P ARTITION is complete. 35346 16 SPLIT clause of ALTER PARTITION statement failed because the par tition is not empty. Only empty partitions can be split in when a columnstore i ndex exists on the table. Consider disabling the columnstore index before issuin g the ALTER PARTITION statement, then rebuilding the columnstore index after ALT ER PARTITION is complete. 35347 16 The stored procedure, sp_tableoption failed because a table with a nonclustered columnstore index cannot be altered to use vardecimal storage fo rmat. Consider dropping the columnstore index. 35348 16 CREATE INDEX statement failed because table '%.*ls' uses vardeci mal storage format. A columnstore index cannot be created on a table using varde cimal storage. Consider rebuilding the table without vardecimal storage. 35349 16 TRUNCATE TABLE statement failed because table '%.*ls' has a colu mnstore index on it. A table with a columnstore index cannot be truncated. Consi der dropping the columnstore index then truncating the table. 35350 16 CREATE INDEX statement failed because a columnstore index on a p artitioned table must be partition-aligned with the base table. Consider droppin g the columnstore index before creating a new clustered index. 35351 16 DROP INDEX statement failed because a columnstore index on a par titioned table must be partition-aligned with the base table (heap). Consider dr opping the columnstore index before dropping a clustered index. 35352 16 %S_MSG statement failed because the operation cannot be performe d online on a table with a columnstore index. Perform the operation without spec ifying the ONLINE option or drop (or disable) the columnstore index before perfo rming the operation using the ONLINE option. 35353 16 %s cannot be enabled on a table with a columnstore index. Consi der dropping columnstore index '%s' on table '%s'. 35354 16 CREATE INDEX statement failed because a columnstore index cannot be created on a table enabled for %S_MSG. Consider disabling %S_MSG and then c reating the columnstore index. 35355 16 CREATE INDEX statement failed. Column '%.*ls' is either a primar y key or a partitioning key that must be included, but a columnstore index canno t include a decimal or numeric data type with a precision greater than 18. Consi der reducing the precision of column '%.*ls' to 18. 35356 16 CREATE INDEX statement failed. Column '%.*ls' is either a primar y key or a partitioning key that must be included, but a columnstore index canno t include a datetimeoffset data type with a precision greater than 2. Consider r educing the precision of column '%.*ls' to 2. 35357 15 CREATE INDEX statement failed. Column '%.*ls' is either a primar y key or a partitioning key that must be included, but '%.*ls'has a data type th

at cannot participate in a columnstore index. 35401 10 ONLINE 35402 10 ALLOW_ROW_LOCKS 35403 10 ALLOW_PAGE_LOCKS 35404 16 sequence 35405 10 decryption 35406 10 creation 35409 10 Replication 35410 10 Change Tracking 35411 10 Change Data Capture 35412 16 CloudDB Async Transport 35413 16 CloudDB Async Transport Forwarder 35415 10 mirrored 35417 10 primary 35418 10 secondary 35419 16 feature 35420 16 operation 35421 16 statement 35422 16 index option 35423 16 table option 35424 16 operator 35425 16 value 35426 16 system column 35427 16 set option 35428 16 query hint 35429 16 transaction isolation level 35430 16 in memory index 35431 10 SCHEDULER 35432 10 NUMANODE 35433 16 federation 35434 16 federation distribution 35435 16 system database 35436 16 federation member database 35437 16 non federation member database 35438 16 federation root database 36001 16 %s '%s' already exists in the database. 36002 16 instance_id already exists in the database. 36003 16 %s '%s' already exists for the given DAC instance. 36004 16 DacInstance with the specified instance_id does not exist. 36005 16 Dac root - database %s does not exist. 36006 16 Dac Policy with the specified policy id already exists in the pa rts table. 36007 16 Dac Part the policy refers to, does not exist. 36008 16 Dac Policy refers to a non-existent Policy. 36009 16 %s '%s' already exists in the Dac Parts. 36010 16 The caller must be a member of the dbcreator fixed server role t o perform this action. 36011 16 The caller must be sysadmin or the creator of the history entry being updated. 36012 10 Unable to execute T-SQL within procedure due to SQL Server limit ation.\nPlease execute following T-SQL in database '%s' context after this proce dure finishes:\n%s 36101 16 Process ID %d is not an active process ID. 37001 16 This operation is not allowed since there are dependent objects pending installation. 37002 16 Cannot find the database '%s', because it does not exist or you do not have permission to access it. 37003 16 This operation is not allowed because a utility control point al ready exists on this instance of SQL Server. 37004 16 The specified instance of SQL Server cannot be used as a utility

control point because the feature is not enabled in SQL Server '%s'. 37005 16 The specified instance of SQL Server cannot be managed by a util ity control point because the feature is not enabled in SQL Server '%s'. 37006 16 Cannot perform the operation because the specified instance of S QL Server is not enrolled in a SQL Server utility. 37007 16 An error occurred during upload to the SQL Server utility contro l point. 37008 16 The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role. 37009 16 The operation cannot continue. The specified instance of SQL Ser ver is not a SQL Server utility control point. 37010 16 The operation cannot continue. The SQL Server utility control po int has managed instances of SQL Server enrolled. 38001 16 Cannot find the file id %d in the database '%s'. 38002 16 Only users having %s permission can execute this stored procedur e. 40000 16 Replicated tables support only local (non-DTC) two-phase commit involving the master database. 40001 16 Secondary kill was initiated during commit. 40002 16 Replicated row is not found. 40003 16 Unexpected operation in replicated message. 40004 16 Column count does not match. 40005 16 Duplicated transaction id. 40006 16 Unknown transaction id. 40007 16 Invalid nesting level. 40008 16 Replication target database is not found. 40009 16 Transaction state locally does not match the expected state. 40010 16 Replicated transactions across databases are not allowed. 40011 16 Replicated target table %ld is not found. 40012 16 Replicated target index %ld on table %ld is not found. 40013 16 Replicated target schema %.*ls is not found. 40014 16 Multiple databases can not be used in the same transaction. 40015 16 This functionality is not supported on replicated tables. 40016 16 The partitioning key column '%.*ls' must be one of the keys of ' %.*ls.%.*ls.%.*ls' index. 40017 16 Partition key can not be changed. 40018 16 Partition key value is outside of the valid partition key range. 40019 16 The partition key column '%.*ls' of table '%.*ls.%.*ls' is nulla ble or does not match the partition key type defined in the table group. 40020 16 The database is in transition and transactions are being termina ted. 40021 16 The low and high keys specified for the partition are invalid. Low must be less than high. 40022 16 A partition with overlapping key ranges already exists. 40023 16 The name %s is too long. 40024 16 The last committed CSN (%d, %I64d) was not found in the log. The last seen CSN was (%d, %I64d). 40028 16 The tablegroup name '%.*ls.%.*ls' is not valid. 40029 16 Replicated tables can have at most %d columns. 40030 16 Can not perform replica operation because the replica does not e xist in local partition map. 40031 16 The partition key column for table '%.*ls.%.*ls' is undefined. 40032 16 Unsupported use of LOB in online index build. 40033 16 Attempted CSN epoch switch is not allowed. The new CSN is (%d,%I 64d), the current CSN is (%d,%I64d). 40034 16 CSN being added must be equal last CSN+1. The new CSN is (%d,%I6 4d), the current CSN is (%d,%I64d). 40035 16 CSN being added must be equal or greater than the last CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). 40036 16 Can not perform replica operation because this node is not the s

econdary for this partition. 40037 16 The epoch being started must not have been used. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). 40038 16 Can not get ack to rollback replication message. 40039 16 Can not get ack to commit replication message. 40041 16 Corrupted column status. 40042 16 Corrupted column length. 40043 16 Corrupted variable data. Actual remaining bytes is %d, expected %d bytes. 40044 16 Corrupted fixed size data. Actual remaining bytes %d, expected % d bytes. 40045 16 Message version mismatch. Actual version is %d and the expected is %d. 40046 16 The minimum required message version %d for message type %d is u nsupported. 40047 16 Invalid use of parent transaction. 40048 16 Corrupted fragmented row flow sequence. 40049 16 Corrupted fragmented row. 40050 16 Corrupted LOB row. 40051 16 Use of UPDATETEXT on replicated tables is not supported. 40052 16 Parallel queries are not supported on replicated tables. 40053 16 Attempt to replicate a non-replicated system table %ld. 40054 16 Tables without a clustered index are not supported in this versi on of SQL Server. Please create a clustered index and try again. 40056 16 Master, tempdb, model and mssqlsystemresource databases can not be replicated. 40057 16 Table is not enabled for replication. 40058 16 Unsupported replicated table usage option. Refer to the state to identify the cause. 40060 16 Attempt to replicate out of partition already locked for interna l use. 40061 16 Unknown rowset id. 40062 16 Incorrect replica role transition. 40063 16 Replica is not found. 40064 16 Attempt to add a CSN to an invalid CSN vector. The new CSN is (% d,%I64d), the current CSN is (%d,%I64d). 40065 16 CSN vector can be reinitialized only with initial or invalid CSN . The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). 40066 16 Transport destination is not found. 40067 16 Corrupted row sequence. 40068 16 Idempotent mode has been used on an unknown transaction. 40069 16 Could not obtain rowset interface. 40070 16 CSN mismatch detected. The local CSN is (%d,%I64d), the remote C SN is (%d,%I64d). 40071 16 This partition does not have enough valid secondaries to start a DML transaction. The needed count is %ld, the current counts are %ld (main quor um) and %ld (transient quorum). 40072 16 Corrupted rowset metadata sequence. 40073 16 Partitioned tables are not supported. 40074 16 Partition key is not found is the target rowset or is nullable o r not part of index keys. 40075 16 Column schema mismatch for rowset %ls.%ls.%ls column %ld. 40076 16 Too few columns from remote rowset %ls.%ls.%ls. 40077 16 Remote rowset %ls.%ls.%ls column %ld is not found locally. 40078 16 The persisted queue logging has failed. 40079 16 A non-null variable length value is received for a column that i s shorter locally. 40080 16 Corrupted (too long) packed row. 40081 16 Cardinality of index should not be less then zero. 40082 16 Induced exception for testing purposes.

40083 16 Corrupted CSN vector. 40084 16 Multiple modifications to CSN vector in the same transaction are not supported. 40085 16 The primary partition has lost the quorum. New transactions can not start. 40086 16 Primary hit an error with this secondary. 40087 16 Replica with the specified version is not found. 40088 16 CSN being set is outside the CSN epoch range. The new CSN is (%d ,%I64d), the current CSN is (%d,%I64d). 40089 16 The index configuration for table %ld index %ld does not match t he source. 40090 16 The primary partition is in transition and the transaction can n ot commit. 40091 16 Truncation CSN is mismatched. The truncation CSN is (%d,%I64d), the current CSN is (%d,%I64d). 40092 16 This index %ld state for table %ld does not match the source. 40093 16 Replication background task hit a lock timeout. User transaction s will be killed and the operation will be retried. 40094 16 Incompatible key metadata change. The scan can not be resumed. 40095 13 Replication transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. The o peration will be retried. 40096 16 Critical replication task could not start. State is %d. 40097 16 The begin transaction message was not found when scanning persis ted replication queue. 40098 16 Mismatched partition id found in the transaction log. 40099 16 Invalid nested transaction count found in the transaction log. 40101 16 The partition does not have persisted queues enabled. 40102 16 The partition can not have persisted queues modified in this sta te. 40103 16 The partition can not be changed inside a persisted object. 40104 16 Only sysadmin can execute this stored procedure '%.*ls'. 40105 16 The local partition map for database %.*ls is starting up in red uced functionality mode because of log full. Pending partition deletes will not be processed until the log is truncated. 40106 16 The schema scope set in the session is not the current schema sc ope for the current partition. Please rerun your query. 40108 16 The filtered replica is not a subset of the primary replica. Thi s is only possible for table groups without a partition key. 40109 16 Number of parameters specified for procedure or function %.*ls i s incorrect. 40130 16 Replication quorum parameter is %d. It should be >= 1 and <= 32. 40131 16 IDENTIFIER, and 40132 16 ions. 40133 15 40134 16 40135 15 40136 15 le user mode. 40137 15 40138 16 40139 16 . 40140 16 in the current 40141 16 this query. Partition key type '%.*ls' is not supported. Only BIGINT, UNIQUE VARBINARY(n) (0<n<=512) datatypes are supported currently. Before dropping a table group, you have to delete all the partit This operation is not supported in this version of SQL Server. get_new_rowversion() can only be used in an active transaction. This system metadata view is not supported. Could not disable versioning because the database is not in sing Could not refresh options for all scoped databases. Query references entities from multiple partitions. The data node does not host a replica of the requested partition Set partition failed since a different partition already was set transaction. Partition has to be set using sp_set_partition before executing

40142 16 Accessing a different partition in the same transaction is not a llowed. 40143 16 The replica that the data node hosts for the requested partition is not primary. 40144 16 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 40145 16 Database is not found. 40146 16 Table group object is not found. 40147 16 Stored procedure '%.*ls' is only for CloudDB. 40148 16 The existing persisted queue snapshot CSN (%d, %I64d) at %S_LSN is greater than the requested snapshot CSN (%d, %I64d) at %S_LSN. 40149 16 The database does not host any partitions. 40151 16 Partition is in transactionally inconsistent state. 40152 16 Partition delete expects no context transaction. 40153 16 The current database has been shutdown. The current database has been switched to master. 40157 16 Too many secondaries. At most 32 are currently supported. 40158 16 Could not change database collation for database id %d. 40159 16 Database scoping cannot be run inside a transaction. 40160 16 Heartbeat message version mismatch. Actual version is %d and the expected is %d. 40161 16 Invalid partition type. Only 1 or 2 is supported. 40162 16 The replica that the data node hosts for the requested partition is not transactionally consistent. 40163 16 Become nothing expects no context transaction. 40166 16 A CloudDB reconfiguration is going on and all new user transacti ons are aborted. 40167 21 A paired CloudDB fabric node failed and database %d must be shut down. 40170 16 Catchup of secondary at %s:%s:%s:%d has failed. 40171 16 Table group name (single part name) should not be longer than nv archar(64). 40172 16 The partition is not in a state that allows deletion. 40173 16 This requested operation can not performed as this partition is in delete process. 40174 16 The partition is in transition and transactions are being termin ated. 40175 16 Add a secondary with wait can not be used in a transaction. 40176 16 Rename a partition can not be used in a transaction. 40177 16 The new table group does not match the existing table group for the renaming partition. 40178 16 A partition with same name already exists. 40179 16 Fabric-database ('%.*ls') cannot be paired, the monitor thread i s not running. 40180 16 Fabric-database ('%.*ls') cannot be paired, the database is alre ady paired. 40181 16 Fabric-database ('%.*ls') cannot be paired, the supplied mutex ( '%.*ls') could not be opened. Error code: %d 40182 16 The schema scope %ld being created is not empty. 40183 16 Could not create database side pairing mutex for database ('%.*l s'). Error code: %d 40185 16 Secondary failure report expects no context transaction. 40186 16 The data node does not host a replica of the requested partition with the requested version. 40187 16 The metadata record for the partition does not exist. 40192 16 Catchup of secondary at %s:%s:%s:%d has been cancelled. 40193 16 The maximum allowed number of database is already paired. 40194 16 Table %s has a partition key already. Explicitly specifying a ne w partition key is not allowed. Please use "Alter table". 40195 16 %ls FOR SID command is not supported in this version of SQL Serv

er. 40196 16 A varbinary can not be longer than max length specified. 40197 16 The service has encountered an error processing your request. Pl ease try again. Error code %d. 40198 16 Only a primary replica can be configured as a forwarder. 40199 16 There should be no context transaction when entering the forward er pending state. 40201 16 Destination server name is too long. 40202 16 Corrupted composite message. 40203 16 Could not register AsyncTransport endpoint. 40204 16 Dispatch sequence number maintenance failure 40205 16 Maximum transport queue size reached. 40206 16 Heartbeat lease time is less than the heartbeat worker interval. 40207 16 Async transport test failed. 40208 16 Corrupted received message format. 40209 17 Duplicate destination id. 40301 16 Invalid lock mode or resource received in lock request. 40302 16 Invalid identity value. 40303 16 Enter idempotent sequence. 40304 16 Target object %ld is not found. 40305 16 The current object is not a relation. 40306 16 Cannot create an index %ld on object %ld. 40307 16 Cannot find index %ld on object %ld. 40308 16 Metadata replication protocol error. 40309 16 Partition %ld is not found 40310 16 Converting a clustered index into a heap is not supported. 40311 16 Switching out partitions not supported. 40312 16 Inconsistent index build state. 40313 16 Not all rowsets could be deleted. 40314 16 Identity column not found on object %ld. 40501 20 The service is currently busy. Retry the request after 10 second s. Incident ID: %ls. Code: %d 40502 16 Duplicate group id settings specified. 40503 16 Database field %ls contains invalid value '%.*ls'. Expected dat a type %ls. 40504 16 Switching Databases is not supported. Use a new connection to c onnect to a different Database. 40505 16 Incorrect user credentials. 40506 16 Specified SID is invalid for this version of SQL Server. 40507 16 '%.*ls' cannot be invoked with parameters in this version of SQL Server. 40508 16 USE statement is not supported to switch between databases. Use a new connection to connect to a different Database. 40510 16 Statement '%.*ls' is not supported in this version of SQL Server . 40511 16 Built-in function '%.*ls' is not supported in this version of SQ L Server. 40512 16 Deprecated feature '%ls' is not supported in this version of SQL Server. 40513 16 Server variable '%.*ls' is not supported in this version of SQL Server. 40514 16 '%ls' is not supported in this version of SQL Server. 40515 16 Reference to database and/or server name in '%.*ls' is not suppo rted in this version of SQL Server. 40516 16 Global temp objects are not supported in this version of SQL Ser ver. 40517 16 Keyword or statement option '%.*ls' is not supported in this ver sion of SQL Server. 40518 16 DBCC command '%.*ls' is not supported in this version of SQL Ser ver.

40519 16 Invalid value '%.*ls' of login field in gateway magic syntax. 40520 16 Securable class '%S_MSG' not supported in this version of SQL Se rver. 40521 16 Securable class '%S_MSG' not supported in the server scope in th is version of SQL Server. 40522 16 Database principal '%.*ls' type is not supported in this version of SQL Server. 40523 16 Implicit user '%.*ls' creation is not supported in this version of SQL Server. Explicitly create the user before using it. 40524 16 Data type '%.*ls' is not supported in this version of SQL Server . 40525 16 WITH %ls' is not supported in this version of SQL Server. 40526 16 '%.*ls' rowset provider not supported in this version of SQL Ser ver. 40527 16 Linked servers are not supported in this version of SQL Server. 40528 16 Users cannot be mapped to certificates, asymmetric keys, or Wind ows logins in this version of SQL Server. 40529 16 Built-in function '%.*ls' in impersonation context is not suppor ted in this version of SQL Server. 40530 16 The %.*ls statement must be the only statement in the batch. 40531 11 Server name cannot be determined. It must appear as the first s egment of the server's dns name (servername.%.*ls). Some libraries do not send the server name, in which case the server name must be included as part of the u ser name (username@servername). In addition, if both formats are used, the serv er names must match. 40532 11 Cannot open server "%.*ls" requested by the login. The login fa iled. 40533 16 Server '%.*ls' already exists. 40534 16 A valid SID is already associated with the database owner. 40535 16 Properties for schema scope '%.*ls' already exist. 40537 16 User '%.*ls' not found in the database. 40541 16 Procedure cannot be called from inside a partition. 40542 16 Incorrect number of parameters specified for procedure. 40543 16 Invalid %S_MSG name specified. Length should be between 1 and %d . 40544 20 The database has reached its size quota. Partition or delete dat a, drop indexes, or consult the documentation for possible resolutions. Incident ID: %ls. Code: %d 40545 20 The service is experiencing a problem that is currently under in vestigation. Incident ID: %ls. Code: %d 40548 16 Granting CONNECT permission to the guest user in database '%.*ls ' is not permitted. 40549 16 Session is terminated because you have a long running transactio n. Try shortening your transaction. 40550 16 The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction. 40551 16 The session has been terminated because of excessive TEMPDB usag e. Try modifying your query to reduce temporary table space usage. 40552 16 The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction. 40553 16 The session has been terminated because of excessive memory usag e. Try modifying your query to process fewer rows. 40561 16 Database copy failed. Either the source or target database does not exist. 40562 16 Database copy failed. The source database has been dropped. 40563 16 Database copy failed. The target database has been dropped. 40564 16 Database copy failed. Database copy failed due to an internal e rror. Please drop target database and try again.</value> 40565 16 Database copy failed. No more than 1 concurrent database copy fr om the same source is allowed. Please drop target database and try again later.

40566 16 Database copy failed due to an internal error. Please drop targe t database and try again. 40567 16 Database copy failed due to an internal error. Please drop targe t database and try again. 40568 16 Database copy failed. Either the source or the target database h as become unavailable. Please drop target database and try again. 40569 16 Database copy failed. Target database has become unavailable. Pl ease drop target database and try again. 40570 16 Database copy failed due to an internal error. Please drop targe t database and try again later. 40571 16 Database copy failed due to an internal error. Please drop targ et database and try again later. 40572 16 Cannot obtain primary partition lock for CloudDB auto partition upgrade. 40573 16 Cannot upgrade CloudDB auto partitions in database '%.*ls' becau se the physical database is read only. 40574 16 Permissions for system stored procedures, server scoped catalog views, and extended stored procedures cannot be changed in this version of SQL S erver. 40575 16 Data type '%.*ls' is not supported in a federated database. 40576 16 Table DDL on non-temporary tables is not supported in a filtered connection. 40577 16 The constraint '%ls' is not supported in a federated database. 40578 16 Statement '%.*ls' is not supported in a filtered connection. 40579 16 DML statements are not supported on non-federated tables in a fi ltered connection. 40580 16 Statement '%.*ls' is not supported in a federated database. 40581 16 Logically filtered secondaries are only supported if the seconda ry is a forwarder. 40582 16 Federation member metadata for a database cannot be changed when there are logically filtered secondaries attached (split is running). 40583 16 Federation member does not exist for the given member id and fed eration root 40590 16 The Gpm is in rebuild and cannot be accessed as it is not yet co nsistent. 40601 16 Server Admin user already exists. 40602 16 Could not create login. Please try again later. 40603 16 Cannot execute procedure because current user is not Gateway. 40604 16 Could not %.*ls because it would exceed the quota of the server. 40606 16 Databases cannot be attached in this version of SQL Server. 40607 16 Windows logins are not supported in this version of SQL Server. 40608 10 This session has been assigned a tracing ID of '%.*ls'. Provide this tracing ID to customer support when you need assistance. 40609 16 '%.*ls' is not a valid IPv4 address. 40610 16 The IP address that starts with '%.*ls' is too long. Maximum len gth is %d. 40611 16 Servers can have at most 128 firewall rules defined. 40612 16 Spec proc was executed against a silo that cannot be upgraded to include firewall objects. 40613 17 Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer su pport, and provide them the session tracing ID of '%.*ls'. 40614 16 Start IP address of firewall rule cannot exceed End IP address. 40615 16 Cannot open server '%.*ls' requested by the login. Client with I P address '%.*ls' is not allowed to access the server. To enable access, use th e SQL Azure Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range. It may take up to five mi nutes for this change to take effect. 40616 16 '%.*ls' is not a valid login name in this version of SQL Server. 40617 16 The firewall rule name that starts with '%.*ls' is too long. Max

imum length is %d. 40618 16 The firewall rule name cannot be empty. 40619 16 The edition '%.*ls' does not support the database max size '%d G B'. 40620 16 The login failed for user "%.*ls". The password change failed. P assword change during login is not supported in this version of SQL Server. 40621 16 metric type 40622 16 metric data 40623 16 Reauthentication failed for login "%.*ls". Within the past reaut hentification interval, the login has become invalid due to a password change, a dropped login, or other cause. Please retry login. 40624 16 Operation is not allowed because server '%.*ls' is disabled. 40625 17 Provisioning (creating, altering, or dropping) SQLAzure servers and databases is currently disabled. This most frequently occurs for brief peri ods during system maintenance. 40626 20 The ALTER DATABASE command is in process. Please wait at least five minutes before logging into database '%.*ls', in order for the command to c omplete. Some system catalogs may be out of date until the command completes. If you have altered the database name, use the NEW database name for future acti vity. 40627 20 Operation on server '%.*ls' and database '%.*ls' is in progress. Please wait a few minutes before trying again. 40628 16 Failed to update database "%.*ls" because the database is read-o nly. Please contact your Azure service owner. There may be billing related issue s with your Azure account. 40629 16 An edition could not be determined from maxsize '%d'. Specify a valid maxsize value. 40630 16 Password validation failed. The password does not meet policy re quirements because it is too short. 40631 16 The password that you specified is too long. The password should have no more than %d characters. 40632 16 Password validation failed. The password does not meet policy re quirements because it is not complex enough. 40633 16 '%.*ls' is not a valid database edition in this version of SQL S erver. 40634 16 This stored procedure can only be executed in the master databas e. 40635 16 Client with IP address "%.*ls" is temporarily blocked. 40636 16 Cannot use reserved database name '%.*ls' in this operation. 40637 17 Database copy is currently disabled. 40638 16 Invalid subscription id '%.*ls'. Subscription does not exist. 40639 16 Request does not conform to schema: %.*ls. 40640 20 The server encountered an unexpected exception. 40641 16 The specified location is invalid. 40642 17 The server is currently too busy. Please try again later. 40643 16 The specified x-ms-version header value is invalid. 40644 14 Failed to authorize access to the specified subscription. 40645 16 Servername "%.*ls" cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name. 40646 16 Subscription ID cannot be empty. 40647 16 Subscription '%.*ls' does not have the server '%.*ls'. 40648 17 Too many requests have been performed. Please retry later. 40649 16 Invalid content-type is specified. Only application/xml is supp orted. 40650 16 Subscription '%.*ls' does not exist or is not ready for the oper ation. 40651 16 Failed to create server because the subscription '%.*ls' is disa bled. 40652 16 Cannot move or create server. Subscription '%.*ls' will exceed s

erver quota. 40653 16 Could not find database '%.*ls' at time '%.*ls' that can be rest ored. 40654 16 Specified subregion '%.*ls' is invalid. 40655 16 Database 'master' cannot be restored. 40656 16 Quota for maximum number of concurrent restores has been exceede d. 40657 16 Restore is not enabled on the server. 40658 16 Quota for number of restores has been exceeded. 40659 16 Could not successfully restore database because the maximum dura tion for processing a restore has elapsed. 40660 16 Could not successfully restore database. This request has been a ssigned a tracing ID of '%.*ls'. Provide this tracing ID to customer support wh en you need assistance. 40661 16 Restore has been cancelled by a system administrator. 40662 16 An internal error was encountered when processing the restore re quest. This request has been assigned a tracing ID of '%.*ls'. Provide this tra cing ID to customer support when you need assistance. 40663 16 Database '%.*ls' is currently being restored and cannot be dropp ed. Please wait for restore to complete. 40664 16 Database 'master' cannot be copied. 40665 16 '%.*ls' is not a supported collation. 40666 16 '%.*ls' is a unicode-only collation and cannot be a default coll ation for a database. 40667 15 Specifying a LOGIN is not allowed in a federation member. 40668 16 '%.*ls' is not a valid user name or you do not have permission. 40701 16 XML format used for specifying rules is invalid. %.*ls. 40702 16 Failed to parse XML rules. 40703 16 Invalid attribute name '%.*ls' in %.*ls. 40704 16 Invalid element name '%.*ls' in %.*ls. 40705 16 Invalid Feature type '%.*ls' in %.*ls. 40706 16 Feature name '%.*ls' does not exist. 40707 16 Invalid index value '%.*ls' in %.*ls. 40708 16 Invalid param count '%.*ls' in %.*ls. 40709 16 operator attribute is missing in %.*ls. 40711 16 Rule name '%.*ls' does not exist. 40712 16 Invalid usage of %.*ls. 40713 16 Invalid values supplied for <parameter> element in %.*ls. 40714 16 Out of memory. 40715 16 Invalid operator type %.*ls in %.*ls. 40716 16 Invalid input type %.*ls in %.*ls. 40717 16 index attribute is missing in %.*ls. 40718 16 one of inputtype, isnull and format attributes is required in %. *ls. 40719 16 Failed to get %s lock on %s rules. 40720 16 Rule name '%.*ls' already exists. 40721 16 Only one of inputtype, isnull and format attributes is required in %.*ls. 40722 16 Failed to clear proc cache. 40723 16 Rule name cannot exceed more than %d characters. 40724 16 Unexpected Operator attribute in %.*ls. 41000 16 Failed to obtain the local Windows Server Failover Clustering (W SFC) handle (Error code %d). The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see "Sy stem Error Codes" in the Windows Development documentation. 41001 16 Failed to obtain local computer name (Error code %d). The suppl ied buffer may be too small, or there is a system error. For information about this error code, see "System Error Codes" in the Windows Development documentati on. 41002 16 Failed to obtain the local Windows Server Failover Clustering (W

SFC) node handle (Error code %d). The WSFC service may not be running or may no t be accessible in its current state. For information about this error code, se e "System Error Codes" in the Windows Development documentation. 41003 16 Failed to obtain the local Windows Server Failover Clustering (W SFC) node ID (Error code %d). The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see "S ystem Error Codes" in the Windows Development documentation. 41004 16 Failed to obtain the Windows Server Failover Clustering (WSFC) g roup handle for cluster group with name or ID '%s' (Error code %d). The WSFC se rvice may not be running or may not be accessible in its current state, or the s pecified cluster group name or ID is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41005 16 Failed to obtain the Windows Server Failover Clustering (WSFC) r esource handle for cluster resource with name or ID '%s' (Error code %d). The W SFC service may not be running or may not be accessible in its current state, or the specified cluster resource name or ID is invalid. For information about th is error code, see "System Error Codes" in the Windows Development documentation . 41006 16 Failed to create the Windows Server Failover Clustering (WSFC) g roup with name '%s' (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41007 16 The Windows Server Failover Clustering (WSFC) group control API returned error code %d. The WSFC service may not be running or may not be acces sible in its current state, or the specified arguments are invalid. For informa tion about this error code, see "System Error Codes" in the Windows Development documentation. 41008 16 Failed to create the Windows Server Failover Clustering (WSFC) r esource with name '%s' and type '%s' (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified clust er resource name or type is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41009 16 The Windows Server Failover Clustering (WSFC) resource control A PI returned error code %d. The WSFC service may not be running or may not be ac cessible in its current state, or the specified arguments are invalid. For info rmation about this error code, see "System Error Codes" in the Windows Developme nt documentation. 41010 16 Failed to bring the Windows Server Failover Clustering (WSFC) gr oup online (Error code %d). The WSFC service may not be running or may not be a ccessible in its current state, or the specified cluster group name is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41011 16 Failed to take the Windows Server Failover Clustering (WSFC) gro up offline (Error code %d). The WSFC service may not be running or may not be a ccessible in its current state, or the specified cluster group name is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41012 16 The Windows Server Failover Clustering (WSFC) node control API r eturned error code %d. The WSFC service may not be running or may not be access ible in its current state, or the specified arguments are invalid. For informat ion about this error code, see "System Error Codes" in the Windows Development d ocumentation. 41013 16 Failed to obtain the Windows Server Failover Clustering (WSFC) r esource enumeration handle (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster resourc e handle is invalid. For information about this error code, see "System Error C odes" in the Windows Development documentation. 41014 16 Failed to enumerate the Windows Server Failover Clustering (WSFC ) resources (Error code %d). The WSFC service may not be running or may not be

accessible in its current state, or the specified cluster resource enumeration h andle is invalid. For information about this error code, see "System Error Code s" in the Windows Development documentation. 41015 16 Failed to obtain the Windows Server Failover Clustering (WSFC) n ode handle (Error code %d). The WSFC service may not be running or may not be a ccessible in its current state, or the specified cluster node name is invalid. For information about this error code, see "System Error Codes" in the Windows D evelopment documentation. 41016 16 Failed to remove a node from the possible owner list of a Window s Server Failover Clustering (WSFC) resource (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specifi ed cluster resource or node handle is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41017 16 Failed to add a node to the possible owner list of a Windows Ser ver Failover Clustering (WSFC) resource (Error code %d). The WSFC service may n ot be running or may not be accessible in its current state, or the specified cl uster resource or node handle is invalid. For information about this error code , see "System Error Codes" in the Windows Development documentation. 41018 16 Failed to move a Windows Server Failover Clustering (WSFC) group to the local node (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster group or node h andle is invalid. For information about this error code, see "System Error Code s" in the Windows Development documentation. 41019 16 Failed to drop a Windows Server Failover Clustering (WSFC) group with name or ID '%.*ls' (Error code %d). The WSFC service may not be running o r may not be accessible in its current state, or the specified cluster group nam e or ID is invalid. For information about this error code, see "System Error Co des" in the Windows Development documentation. 41020 16 Failed to find a String property (property name '%s') of the Win dows Server Failover Clustering (WSFC) resource with name or ID '%.*ls' (Error c ode %d). The WSFC service may not be running or may not be accessible in its cu rrent state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41021 16 Failed to find a DWORD property (property name '%s') of the Wind ows Server Failover Clustering (WSFC) resource with ID '%.*ls' (Error code %d). The WSFC service may not be running or may not be accessible in its current sta te, or the specified arguments are invalid. For information about this error co de, see "System Error Codes" in the Windows Development documentation. 41022 16 Failed to create a Windows Server Failover Clustering (WSFC) not ification port with notification filter %d and notification key %d (Error code % d). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this erro r code, see "System Error Codes" in the Windows Development documentation. 41023 16 The Windows Server Failover Clustering (WSFC) change handle is i nvalid because a WSFC notification port has not been created or has been closed. Create a new WSFC notification port and retry the operation. 41024 16 Failed to register additional Windows Server Failover Clustering (WSFC) change notifications with notification filter %d and notification key %d (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information a bout this error code, see "System Error Codes" in the Windows Development docume ntation. 41025 16 Failed to receive Windows Server Failover Clustering (WSFC) chan ge notifications (Error code %d). The WSFC service may not be running or may no t be accessible in its current state, or the specified arguments are invalid. F or information about this error code, see "System Error Codes" in the Windows De velopment documentation. 41026 10 Failed to create the Windows Server Failover Clustering (WSFC) g roup with name '%ls'. The WSFC group with the specified name already exists. R etry the operation with a group name that is unique in the cluster.

41027 16 Failed to start the Windows Server Failover Clustering (WSFC) ch ange listener (SQLOS error code %d). SQL Server may not have sufficient resourc es to start the WSFC change listener. If the condition persists, the SQL Server instance may need to be restarted. 41028 16 Failed to open Windows Server Failover Clustering (WSFC) registr y root key (Error code %d). The WSFC service may not be running or may not be a ccessible in its current state, or the specified arguments are invalid. For inf ormation about this error code, see "System Error Codes" in the Windows Developm ent documentation. 41029 16 Failed to open the Windows Server Failover Clustering (WSFC) res ource registry key '%.*ls' (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are i nvalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41030 16 Failed to open the Windows Server Failover Clustering registry s ubkey '%.*ls' (Error code %d). The parent key is %sthe cluster root key. The W SFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. If the corresponding availability group ha s been dropped, this error is expected. For information about this error code, s ee "System Error Codes" in the Windows Development documentation. 41031 16 Failed to create the Windows Server Failover Clustering (WSFC) r egistry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root ke y. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41032 16 Failed to delete the Windows Server Failover Clustering (WSFC) r egistry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root ke y. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41033 16 Failed to retrieve the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%.*ls' (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specif ied arguments are invalid. For information about this error code, see "System E rror Codes" in the Windows Development documentation. 41034 16 Failed to set the Windows Server Failover Clustering (WSFC) regi stry value corresponding to name '%.*ls' (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified a rguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41035 16 Failed to enumerate Windows Server Failover Clustering (WSFC) re gistry value (Error code %d). The WSFC service may not be running or may not be accessible in its current state or the specified arguments are invalid. For in formation about this error code, see "System Error Codes" in the Windows Develop ment documentation. 41036 16 Failed to delete the Windows Server Failover Clustering (WSFC) r egistry value corresponding to name '%.*ls' (Error code %d). The WSFC service m ay not be running or may not be accessible in its current state, or the specifie d arguments are invalid. For information about this error code, see "System Err or Codes" in the Windows Development documentation. 41037 16 Failed to obtain a Windows Server Failover Clustering (WSFC) obj ect enumeration handle for objects of type %d (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specif ied arguments are invalid. For information about this error code, see "System E rror Codes" in the Windows Development documentation. 41038 16 Failed to enumerate Windows Server Failover Clustering (WSFC) ob jects (Error code %d). The WSFC service may not be running or may not be access ible in its current state, or the specified cluster object enumeration handle is invalid. For information about this error code, see "System Error Codes" in th e Windows Development documentation.

41039 16 An availability group replica already exists on the Windows Serv er Failover Clustering (WSFC) node '%.*ls'. Each WSFC node can contain only one replica of an availability group. Please choose another WSFC node to host the new replica. 41040 16 Failed to remove the availability group replica '%.*ls' from ava ilability group '%.*ls'. The availability group does not contain a replica with the specified name. Verify the availability group and replica names and then r etry the operation. 41041 16 SQL Server instance to Windows Server Failover Clustering (WSFC) node map entry cannot be found for the SQL Server instance '%.*ls' and WSFC gro up ID '%.*ls'. The specified SQL Server instance name is invalid, or the corres ponding registry entry does not exist. Verify the SQL Server instance name and retry the operation. 41042 16 The availability group '%.*ls' already exists. This error could be caused by a previous failed CREATE AVAILABILITY GROUP or DROP AVAILABILITY G ROUP operation. If the availability group name you specified is correct, try dr opping the availability group and then retry CREATE AVAILABILITY GROUP operation . 41043 16 For availability group '%.*ls', the value of the name-to-ID map entry is invalid. The binary value should contain a Windows Server Failover Clu stering (WSFC) resource ID, a WSFC group ID, and their corresponding lengths in characters. The availability group name may be incorrect, or the availability g roup configuration data may be corrupt. If this error persists, you may need to drop and recreate the availability group. 41044 16 Availability group name to ID map entry for availability group ' %.*ls' cannot be found in the Windows Server Failover Clustering (WSFC) store. The availability group name may be incorrect, or the availability group may not exist in this Windows Server Failover Cluster. Verify the availability group ex ists and that the availability group name is correct and then retry the operatio n. 41045 16 Cannot add database '%.*ls' to the availability group '%.*ls', b ecause there is already a database with the same name in the availability group. Please verify that the database and availability group names specified are cor rect. 41046 16 Cannot add replica '%.*ls' to the availability group '%.*ls', be cause there is already a replica with the same name in the availability group. Please verify the replica and availability group names specified are correct. 41047 16 Failed to obtain the Windows Server Failover Clustering (WSFC) n ode state for the local WSFC node (Error code %d). The WSFC service may not be running or may not be accessible in its current state. For information about th is error code, see "System Error Codes" in the Windows Development documentation . 41048 10 AlwaysOn Availability Groups: Local Windows Server Failover Clus tering service has become unavailable. This is an informational message only. No user action is required. 41049 10 AlwaysOn Availability Groups: Local Windows Server Failover Clus tering node is no longer online. This is an informational message only. No user action is required. 41050 10 AlwaysOn Availability Groups: Waiting for local Windows Server F ailover Clustering service to start. This is an informational message only. No u ser action is required. 41051 10 AlwaysOn Availability Groups: Local Windows Server Failover Clus tering service started. This is an informational message only. No user action is required. 41052 10 AlwaysOn Availability Groups: Waiting for local Windows Server F ailover Clustering node to start. This is an informational message only. No user action is required. 41053 10 AlwaysOn Availability Groups: Local Windows Server Failover Clus tering node started. This is an informational message only. No user action is re quired.

41054 10 AlwaysOn Availability Groups: Waiting for local Windows Server F ailover Clustering node to come online. This is an informational message only. N o user action is required. 41055 10 AlwaysOn Availability Groups: Local Windows Server Failover Clus tering node is online. This is an informational message only. No user action is required. 41056 16 Availability replica '%.*ls' of availability group '%.*ls' canno t be brought online on this SQL Server instance. Another replica of the same av ailability group is already online on the local Windows Server Failover Clusteri ng (WSFC) node. Each WSFC node can host only one replica of an availability gro up, regardless of the number of SQL Server instances on the node. Use the ALTER AVAILABILITY GROUP command to correct the availability group configuration. Th en, if the other replica is no longer being hosted on this WSFC node, restart th is instance of SQL Server to bring the local replica of the availability group o nline. 41057 16 Failed to create the Windows Server Failover Clustering (WSFC) r esource with name '%ls'. The WSFC resource with the specified name already exis ts. Retry the operation with a resource name that is unique in the cluster. 41058 10 AlwaysOn: The local replica of availability group '%.*ls' is sta rting. This is an informational message only. No user action is required. 41059 10 AlwaysOn: Availability group '%.*ls' was removed while the avail ability replica on this instance of SQL Server was offline. The local replica w ill be removed now. This is an informational message only. No user action is req uired. 41060 16 The Cyclic Redundancy Check (CRC) value generated for the retrie ved availability group configuration data from the Windows Server Failover Clust ering (WSFC) store does not match that stored with the data for the availability group with ID '%.*ls'. The availability group data in the WSFC store may have been modified outside SQL Server, or the data is corrupt. If the error persists , you may need to drop and recreate the availability group. 41061 10 AlwaysOn: The local replica of availability group '%.*ls' is sto pping. This is an informational message only. No user action is required. 41062 16 The ID of availability group '%.*ls' in local data store is inco nsistent with that in the Windows Server Failover Clustering (WSFC) data store. The availability group may have been dropped and recreated while the SQL Server instance was offline, or while the WSFC node was down. To resolve this error, drop the availability group and then recreate it. 41063 16 Windows Server Failover Clustering (WSFC) detected that the avai lability group resource with ID '%.*ls' was online when the availability group w as not actually online. The attempt to synchronize the WSFC resource state with the availability group state failed (Error code: %d). For information about th is error code, see "System Error Codes" in the Windows Development documentation . 41064 16 Failed to set local node as sole preferred owner for the Windows Server Failover Clustering (WSFC) group with ID '%.*ls' (Error code: %d). The WSFC group might be in state that cannot accept the request. For information ab out this error code, see "System Error Codes" in the Windows Development documen tation. 41065 16 Cannot bring the Windows Server Failover Clustering (WSFC) resou rce (ID: '%.*ls') online at this time. The WSFC resource is not in a state that can accept the request. Wait for the WSFC resource to enter a terminal state, and retry the operation. For information about this error, see error code 5023 in "System Error Codes" in the Windows Development documentation. 41066 16 Cannot bring the Windows Server Failover Clustering (WSFC) resou rce (ID '%.*ls') online (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the WSFC resource may not be in a state that could accept the request. For information about this error code, s ee "System Error Codes" in the Windows Development documentation. 41067 16 Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name '%.*ls') at this time. The WSFC group is not in a state that could

accept the request. Please wait for the WSFC group to enter a terminal state an d then retry the operation. For information about this error, see error code 50 23 in "System Error Codes" in the Windows Development documentation. 41068 16 Failed to enumerate the Windows Server Failover Clustering (WSFC ) registry key (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Deve lopment documentation. 41069 16 The existence of availability group data for the availability gr oup '%.*ls' in the Windows Server Failover Clustering (WSFC) store could not be determined. The local WSFC node may be down, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation has failed. Please use DROP AVAILABI LITY GROUP command to clean up previously failed operations. Verify that the lo cal WSFC node is up before retrying the operation. 41070 16 Configuration data for the availability group with Windows Serve r Failover Clustering (WSFC) resource ID '%.*ls' is not found in the WSFC data s tore. The availability group may have been dropped, or a previous CREATE AVAILA BILITY GROUP or DROP AVAILABILITY GROUP operation has failed. Please use DROP A VAILABILITY GROUP command to clean up previously failed operations before retryi ng the current operation. 41071 16 Cannot read the persisted configuration of AlwaysOn availability group with corresponding Windows Server Failover Clustering (WSFC) resource ID '%.*ls'. The persisted configuration is written by a higher-version SQL Server that hosts the primary availability replica. Upgrade the local SQL Server insta nce to allow the local availability replica to become a secondary replica. 41072 16 The ID of availability group '%.*ls' in local data store does no t exist in the Windows Server Failover Clustering (WSFC) data store. The availa bility group may have been dropped but the current WSFC node was not notified. To resolve this error, try to recreate the availability group. 41073 16 The database '%.*ls' cannot be removed from availability group ' %.*ls'. This database does not belong to the availability group. 41074 10 AlwaysOn: The local replica of availability group '%.*ls' is pre paring to transition to the primary role in response to a request from the Windo ws Server Failover Clustering (WSFC) cluster. This is an informational message o nly. No user action is required. 41075 10 AlwaysOn: The local replica of availability group '%.*ls' is pre paring to transition to the resolving role in response to a request from the Win dows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required. 41076 10 AlwaysOn: Availability group '%.*ls' is going offline because it is being removed. This is an informational message only. No user action is requ ired. 41077 16 Cannot bring the Windows Server Failover Clustering (WSFC) group (ID '%.*ls') online at this time. The WSFC group is not in a state that could accept the request. Please wait for the WSFC group to enter a terminal state an d then retry the operation. For information about this error, see error code 50 23 in "System Error Codes" in the Windows Development documentation. 41078 16 Failed to delete the Windows Server Failover Clustering (WSFC) r egistry value corresponding to name '%.*ls', because a registry entry with the s pecified name does not exist. Check that the registry value name is correct, an d retry the operation. 41079 16 Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name '%.*ls'), because the WSFC group does not exist. Specify a valid WS FC group ID or name and retry the operation. For information about this error, see error code 5013 in "System Error Codes" in the Windows Development documenta tion. 41080 16 Failed to delete SQL Server instance name to Windows Server Fail over Clustering node name map entry for the local availability replica of availa bility group '%.*ls'. The operation encountered SQL Server error %d and has bee n terminated. Refer to the SQL Server error log for details about this SQL Serv

er error and corrective actions. 41081 16 Failed to destroy the Windows Server Failover Clustering group c orresponding to availability group '%.*ls'. The operation encountered SQL Serve r error %d and has been terminated. Refer to the SQL Server error log for detai ls about this SQL Server error and corrective actions. 41082 16 Failed to obtain the name of local Windows Server Failover Clust er (Error code %d). The WSFC service may not be running or may not be accessibl e in its current state. For information about this error code, see "System Erro r Codes" in the Windows Development documentation. 41083 16 Failed to obtain the cluster quorum resource (Error code %d). T he WSFC service may not be running or may not be accessible in its current state . For information about this error code, see "System Error Codes" in the Window s Development documentation. 41084 16 The Windows Server Failover Clustering (WSFC) cluster control AP I returned error code %d. The WSFC service may not be running or may not be acce ssible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation. 41085 16 Failed to find a DWORD property (property name '%s') of the Wind ows Server Failover Clustering (WSFC) (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified argu ments are invalid. For information about this error code, see "System Error Cod es" in the Windows Development documentation. 41086 16 Failed to retrieve the Paxos tag from the Windows Server Failove r Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Veri fy whether the 'HKLM\Cluster\PaxosTag' registry value exists in the WSFC registr y hive. 41087 16 Error in parsing the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whether the 'HKLM\Cluster\PaxosTag' is in the format outlined in the Microsoft Knowledge Base article KB 947713 ("The implications of using the /forcequorum sw itch to start the Cluster service in Windows Server 2008"). 41088 16 Failed to determine if the Windows Server Failover Clustering (W SFC) service is in Force Quorum state. The prerequisite QFE hotfix, KB 2494036, might not yet be installed on your Windows Server 2008/Windows Server 2008 R2 sy stems. For more information, see Microsoft Knowledge Base article KB 2494036 ("A hotfix is available to let you configure a cluster node that does not have quor um votes in Windows Server 2008 and in Windows Server 2008 R2"). 41089 10 AlwaysOn Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user act ion is required. 41090 10 Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception %d. 41091 10 AlwaysOn: The local replica of availability group '%.*ls' is goi ng offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. 41092 10 AlwaysOn: The availability replica manager is going offline beca use %ls. This is an informational message only. No user action is required. 41093 10 AlwaysOn: The local replica of availability group '%.*ls' is goi ng offline because the corresponding resource in the Windows Server Failover Clu stering (WSFC) cluster is no longer online. This is an informational message onl y. No user action is required. 41094 10 AlwaysOn: The local replica of availability group '%.*ls' is res tarting because the existing primary replica restarted or the availability group failed over to a new primary replica. This is an informational message only. No user action is required. 41095 10 AlwaysOn: Explicitly transitioning the state of the Windows Serv er Failover Clustering (WSFC) resource that corresponds to availability group '% .*ls' to Failed. The resource state is not consistent with the availability grou p state in the instance of SQL Server. The WSFC resource state indicates that t he local availability replica is the primary replica, but the local replica is n

ot in the primary role. This is an informational message only. No user action is required. 41096 10 AlwaysOn: The local replica of availability group '%.*ls' is bei ng removed. The instance of SQL Server failed to validate the integrity of the a vailability group configuration in the Windows Server Failover Clustering (WSFC) store. This is expected if the availability group has been removed from anothe r instance of SQL Server. This is an informational message only. No user action is required. 41097 10 AlwaysOn: The local replica of availability group '%.*ls' is goi ng offline. This replica failed to read the persisted configuration because of a version mismatch. This is an informational message only. No user action is requ ired. 41098 10 AlwaysOn: The local replica of availability group '%.*ls' is res tarting, because it failed to read the persisted configuration. This is an infor mational message only. No user action is required. 41099 10 AlwaysOn: The local replica of availability group '%.*ls' is goi ng offline. This replica failed to read the persisted configuration, and it has exhausted the maximum for restart attempts. This is an informational message onl y. No user action is required. 41100 16 The availability group '%.*ls' and/or its local availability rep lica does not exist. Verify that the specified availability group name is corre ct, and that the local availability replica has joined the availability group, t hen retry the operation. 41101 16 The availability group with Windows Server Failover Clustering r esource ID '%.*ls' and/or its local availability replica does not exist. Verify that the specified availability resource ID is correct, and that the local avai lability replica has joined the availability group, then retry the operation. 41102 10 Failed to persist configuration data of availability group '%.*l s' in the Windows Server Failover Clustering (WSFC) cluster. The local availabi lity replica either is not the primary replica or is shutting down. 41103 10 Startup of the AlwaysOn Availability Replica Manager has been te rminated, because the 'FixQuorum' property of Windows Server Failover Clustering (WSFC) is not present. The prerequisite QFE hotfix, KB 2494036, might not yet b e installed on your Windows Server 2008/Windows Server 2008 R2 systems. For more information, see Microsoft Knowledge Base article KB 2494036 ("A hotfix is avai lable to let you configure a cluster node that does not have quorum votes in Win dows Server 2008 and in Windows Server 2008 R2"). 41104 16 Failover of the availability group '%.*ls' to the local replica failed because the availability group resource did not come online due to a prev ious error. To identify that error, check the SQL Server error log and the Windo ws Server Failover Cluster logs and system event logs. For information about how to view events and logs for a Windows Server Failover Clustering (WSFC) cluster , see Windows Server documentation. 41105 16 Failed to create the Windows Server Failover Clustering (WSFC) r esource with name '%s' and type '%s'. The resource type is not registered in th e WSFC cluster. The WSFC cluster many have been destroyed and created again. T o register the resource type in the WSFC cluster, disable and then enable Always On in the SQL Server Configuration Manager. 41106 16 Cannot create an availability replica for availability group '%. *ls'. An availability replica of the specified availability group already exist s on this instance of SQL Server. Verify that the specified availability group name is correct and unique, then retry the operation. To remove the existing av ailability replica, run DROP AVAILABILITY GROUP command. 41107 16 Availability group '%.*ls' failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%d) when obtaining handl es for Lease events. Resolve the windows error and retry the availability group operation. 41108 16 An error occurred while removing availability group '%.*ls'. The DROP AVAILABILITY GROUP command removed the availability group configuration fr om the local metadata. However, the attempt to remove this configuration from th

e Windows Server Failover Clustering (WSFC) cluster failed because the AlwaysOn Availability Groups manager is not online (SQL Server error: %d). To remove the availability group configuration from the WSFC cluster, re-enter the command. 41109 17 Could not enqueue a task (SQL OS error: 0x%x) for process action s for the availability group '%.*ls'. Most likely, the instance of SQL Server i s low on resources. Check the SQL Server error log to determine the cause of the failure. Retry the operation later, and if this condition persists, contact you r database administrator. 41110 10 AlwaysOn: The availability replica manager is starting. This is an informational message only. No user action is required. 41111 10 AlwaysOn: The availability replica manager is waiting for the in stance of SQL Server to allow client connections. This is an informational messa ge only. No user action is required. 41112 16 A Windows Server Failover Clustering (WSFC) API required by avai lability groups has not been loaded. AlwaysOn Availability Groups replica manage r is not enabled on the local instance SQL Server. If the server instance is run ning an edition of SQL Server that supports AlwaysOn Availability Groups, you ca n enable the it by using the SQL Server Configuration Manager. 41113 16 Cannot failover availability group '%.*ls' to this instance of S QL Server because a failover command is already pending on the local replica of this availability group. Wait for the pending failover command to complete befo re issuing another command on the local replica of this availability group. 41114 16 Cannot create an availability group named '%.*ls' because it alr eady exists in a system table. 41115 16 Cannot create the availability group named '%.*ls' because its a vailability group ID (ID: '%.*ls') already exists in a system table. 41116 16 Cannot create an availability group named '%.*ls' with replica I D '%.*ls' because this ID already exists in a system table. 41117 16 Cannot map local database ID %d to the availability database ID '%.*ls' within availability group '%.*ls'. This database is already mapped to an availability group. 41118 16 Cannot map database ID %d to the availability database ID '%.*ls ' within availability group '%.*ls'. Another local database, (ID %d). is already mapped to this availability database. 41119 16 Could not find the availability group ID %d in the system table. 41120 16 Failed to start task to process a down notification for the loca l Windows Server Failover Clustering (WSFC) node (SQL OS error: %d). Possible ca uses are no worker threads are available or there is insufficient memory. Check the state of the local WSFC node. If this problem persists, you might need to re start the instance of SQL Server. 41121 10 The local availability replica of availability group '%.*ls' can not accept signal '%s' in its current replica role, '%s', and state (configurati on is %s in Windows Server Failover Clustering store, local availability replica has %s joined). The availability replica signal is invalid given the current r eplica role. When the signal is permitted based on the current role of the loca l availability replica, retry the operation. 41122 16 Cannot failover availability group '%.*ls' to this instance of S QL Server. The local availability replica is already the primary replica of the availability group. To failover this availability group to another instance of SQL Server, run the failover command on that instance of SQL Server. If local instance of SQL Server is intended to host the primary replica of the availabili ty group, then no action is required. 41126 16 Operation on the local availability replica of availability grou p '%.*ls' failed. The local copy of the availability group configuration does n ot exist or has not been initialized. Verify that the availability group exists and that the local copy of the configuration is initialized, and retry the oper ation. 41127 16 Attempt to set database mapping state where the local database i d %d is not mapped to any availability group. 41128 16 Failed to perform database operation '%s' on database '%.*ls' (I

D %d) in availability group '%.*ls'. The database might be in an incorrect stat e for the operation. If the problem persists, you may need to restart the SQL S erver instance. 41129 16 Failed to schedule or execute database operation '%s' on databas e '%.*ls' (Database ID: %d) in availability group '%.*ls' (SQL OS error: %d). T he instance of SQL Server may have insufficient resources to carry out the datab ase operation. If the problem persists, you might need to restart the server ins tance. 41130 16 Operation '%s' on a database '%.*ls' (Database ID: %d) in availa bility group '%.*ls' failed with SQL Server error %d (Error details: "%.*ls"). The operation has been rolled back. See previous error messages in the SQL Serv er error log for more details. If the problem persists, you might need to restar t the instance of SQL Server. 41131 10 Failed to bring availability group '%.*ls' online. The operatio n timed out. Verify that the local Windows Server Failover Clustering (WSFC) nod e is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again. 41132 16 Cannot join database '%.*ls' to availability group '%.*ls'. The specified database does not belong to the availability group. Verify the names of the database and the availability group, and retry the command specifying th e correct names. 41133 10 Cannot remove database '%.*ls' from availability group '%.*ls'. Either the database does not belong to the availability group, or the database has not joined the group. Verify the database and availability group names, and retry the command. 41134 16 Cannot bring the availability group '%.*ls' online. The local i nstance was not the previous primary replica when the availability group went of fline, not all databases are synchronized, and no force failover command was iss ued on the local availability replica. To designate the local availability repl ica as the primary replica of the availability group, run the force failover com mand on this instance of SQL Server. 41135 10 Startup of AlwaysOn Availability Groups replica manager failed d ue to SQL Server error %d. To determine the cause of this error, check the SQL Server error log for the preceding error. 41136 16 Failed to join the availability replica to availability group '% .*ls' because the group is not online. Either bring the availability group onli ne, or drop and recreate it. Then retry the join operation. 41137 10 Abandoning a database operation '%ls' on availability database ' %.*ls' of availability group '%.*ls'. The sequence number of local availability replica has changed (Previous sequence number: %u, current sequence number: %u) . This is an informational message only. No user action is required. 41138 17 Cannot accept AlwaysOn Availability Groups operation operation o n database '%.*ls' of availability group '%.*ls'. The database is currently pro cessing another operation that might change the database state. Retry the operat ion later. If the condition persists, contact the database administrator. 41139 10 Failed to set database information for availability group %.*ls. The local availability replica is not the primary replica, or it is shutting d own. This is an informational message only. No user action is required. 41140 16 Availability group '%.*ls' cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is not the primary replic a. Connect to the server instance that is currently hosting the primary replica of this availability group, and rerun the command. 41141 16 Failed to set availability group database information for availa bility group %.*ls. The local availability replica is not the primary, or is sh utting down. This is an informational message only. No user action is required. 41142 16 The availability replica for availability group '%.*ls' on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group, or the WSFC clus ter was started in Force Quorum mode. If the cluster was started in Force Quorum

mode or the availability replica uses the asynchronous-commit mode, consider pe rforming a forced manual failover (with possible data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planne d manual failover to this secondary replica (without data loss). For more inform ation, see SQL Server Books Online. 41143 16 Cannot process the operation. The local replica of availability Group '%.*ls' is in a failed state. A previous operation to read or update per sisted configuration data for the availability group has failed. To recover fro m this failure, either restart the local Windows Server Failover Clustering (WSF C) service or restart the local instance of SQL Server. 41144 16 The local availability replica of availability group '%.*ls' is in a failed state. The replica failed to read or update the persisted configura tion data (SQL Server error: %d). To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server. 41145 10 Cannot join database '%.*ls' to availability group '%.*ls'. The database has already joined the availability group. This is an informational m essage. No user action is required. 41146 16 Failed to bring Availability Group '%.*ls' online. The Windows Server Failover Clustering (WSFC) service may not be running, or it may not be a ccessible in its current state. Please verify the local WSFC node is up and the n retry the operation. 41147 10 AlwaysOn Availability Groups was not started because %ls. This is an informational message. No user action is required. 41148 16 Cannot add or join database '%.*ls' to availability group '%.*ls '. The database does not exist on this instance of SQL Server. Verify the data base name and that the database exists on the server instance. Then retry the o peration, specifying the correct database name. 41149 16 Operation on the availability group '%.*ls' has been cancelled o r terminated, either because of a connection timeout or cancellation by user. T his is an informational message. No user action is required. 41150 16 Failed to take availability group '%.*ls' offline. The Windows Server Failover Clustering (WSFC) service may not be running, or it may not be a ccessible in its current state. Verify the local WSFC node is up and then retry the operation. 41151 16 Error accessing the Availability Groups manager. The local Avai lability Groups manager has not been initialized. Wait until the Availability G roups manager is in a state that allows access, and retry the operation. 41152 16 Failed to create availability group '%.*ls'. The operation enco untered SQL Server error %d and has been rolled back. Check the SQL Server erro r log for more details. When the cause of the error has been resolved, retry CR EATE AVAILABILITY GROUP command. 41153 16 Failed to create availability group '%.*ls'. The operation enco untered SQL Server error %d. An attempt to roll back the operation failed. Che ck the SQL Server error log for more details. Then execute the DROP AVAILABILIT Y GROUP command to clean up any metadata that might remain from the failed attem pt to create the availability group. 41154 16 Cannot failover availability group '%.*ls' to this SQL Server in stance. The availability group is still being created. Verify that the specifi ed availability group name is correct. Wait for CREATE AVAILABILITY GROUP comma nd to finish, then retry the operation. 41155 16 Cannot failover availability group '%.*ls' to this instance of S QL Server. The availability group is being dropped. Verify that the specified availability group name is correct. The availability group may need to be recre ated if the drop operation was unintentional. 41156 16 Cannot drop availability group '%.*ls' from this instance of SQL Server. The availability group is either being dropped, or the local availabil ity replica is being removed from the availability group. Verify that the speci fied availability group name is correct. Wait for the current operation to comp lete, then retry the command if necessary.

41157 16 Cannot remove the local availability replica from availability g roup '%.*ls' from this instance of SQL Server. The availability group is either being dropped, or the local availability replica is being disjoined. Verify th at the specified availability group name is correct. Wait for the current opera tion to complete, then retry the command if necessary. 41158 16 Failed to join local availability replica to availability group '%.*ls'. The operation encountered SQL Server error %d and has been rolled back . Check the SQL Server error log for more details. When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP JOIN command. 41159 16 Failed to join local availability replica to availability group '%.*ls'. The operation encountered SQL Server error %d. An attempt to rollback the operation failed. Check SQL Server error log for more details. Run DROP A VAILABILITY GROUP command to clean up any metadata that might remain from the av ailability group. 41160 16 Failed to designate the local availability replica of availabili ty group '%.*ls' as the primary replica. The operation encountered SQL Server e rror %d and has been terminated. Check the preceding error and the SQL Server e rror log for more details about the error and corrective actions. 41161 16 Failed to validate the Cyclic Redundancy Check (CRC) of the conf iguration of availability group '%.*ls'. The operation encountered SQL Server e rror %d, and the availability group has been taken offline to protect its config uration and the consistency of its joined databases. Check the SQL Server error log for more details. If configuration data corruption occurred, the availabil ity group might need to be dropped and recreated. 41162 16 Failed to validate sequence number of the configuration of avail ability group '%.*ls'. The in-memory sequence number does not match the persist ed sequence number. The availability group and/or the local availability replic a will be restarted automatically. No user action is required at this time. 41163 16 An error occurred while waiting for the local availability repli ca of availability group '%.*ls' to transition to the primary role. The operati on encountered SQL OS error %d and has been terminated. Verify that the Windows Server Failover Clustering (WSFC) cluster and the availability group are in the correct states for the command, and then retry the command. 41164 16 An error occurred while waiting for the local availability repli ca of availability group '%.*ls' to transition to the resolving role. The opera tion encountered SQL OS error %d and has been terminated. Verify that the Windo ws Server Failover Clustering (WSFC) cluster and the availability group are in t he correct states for the command, and then retry the command. 41165 16 A timeout error occurred while waiting to access the local avail ability replica of availability group '%.*ls'. The availability replica is curr ently being accessed by another operation. Wait for the in-progress operation t o complete, and then retry the command. 41166 16 An error occurred while waiting to access the local availability replica of availability group '%.*ls'. The operation encountered SQL OS error %d, and has been terminated. Verify that the local availability replica is in t he correct state, and then retry the command. 41167 16 An error occurred while attempting to access availability replic a '%.*ls' in availability group '%.*ls'. The availability replica is not found in the availability group configuration. Verify that the availability group and availability replica names are correct, then retry the command. 41168 16 An error occurred while attempting to access availability replic a with ID '%.*ls' in availability group '%.*ls'. The availability replica is no t found in the availability group configuration. Verify that the availability g roup name and availability replica ID are correct, then retry the command. 41169 16 An error occurred while attempting to access the availability gr oup database with ID '%.*ls' in availability group '%.*ls'. The availability da tabase is not found in the availability group configuration. Verify that the av ailability group name and availability database ID are correct, then retry the c ommand. 41170 10 Post-online processing for availability group '%.*ls' has been t

erminated. Either post-online processing has already completed, the local avail ability replica is no longer the primary replica, or the availability group is b eing dropped. This is an informational message. No user action is required. 41171 16 Failed to create availability group '%.*ls', because a Windows S erver Failover Cluster (WSFC) group with the specified name already exists. The operation has been rolled back successfully. To retry creating an availability group, either remove or rename the existing WSFC group, or retry the operation specifying a different availability group name. 41172 16 An error occurred while dropping availability group '%.*ls' from Windows Server Failover Clustering (WSFC) cluster and from the local metadata. The operation encountered SQL OS error %d, and has been terminated. Verify tha t the specified availability group name is correct, and then retry the command. 41173 16 An error occurred while removing the local availability replica from availability group '%.*ls'. The operation encountered SQL OS error %d, and has been terminated. Verify that the specified availability group name is corr ect, and then retry the command. 41174 10 Failed to start the task of the Windows Server Failover Clusteri ng (WSFC) event notification worker (SQL OS error: %d). If the problem persists , you might need to restart the instance of SQL Server. 41175 10 Failed to stop the task of WSFC event notification worker (SQL O S error: %d). If the problem persists, you might need to restart the instance o f SQL Server. 41176 10 Failed to acquire exclusive access to local availability group c onfiguration data (SQL OS error: %d). If the problem persists, you might need t o restart the instance of SQL Server. 41177 16 The availability replica of the specified availability group '%. *ls' is being dropped. Wait for the completion of the drop command and retry th e operation later. 41178 16 Cannot drop availability group '%.*ls' from this SQL Server inst ance. The availability group is currently being created. Verify that the speci fied availability group name is correct. Wait for the current operation to comp lete, then retry the command if necessary. 41179 16 Cannot remove the local availability replica from availability g roup '%.*ls' from this instance of SQL Server. The availability group is curren tly being created. Verify that the specified availability group name is correct . Wait for the current operation to complete, and then retry the command if nec essary. 41180 16 Attempt to access non-existent or uninitialized availability gro up with ID '%.*ls'. This is usually an internal condition, such as the availabi lity group is being dropped or the local WSFC node has lost quorum. In such case s, and no user action is required. 41181 16 The local availability replica of availability group '%.*ls' did not become primary. A concurrent operation may have changed the state of the a vailability group in Windows Server Failover Cluster. Verify that the availabil ity group state in Windows Server Failover Cluster is correct, then retry the op eration. 41182 16 Failed to set the local availability replica of availability gro up '%.*ls' as joined in Windows Server Failover Clustering (WSFC) database. Eit her the local availability replica is no longer the primary, or the WSFC service is not accessible. Verify that the local WSFC node is online, and that the loc al availability replica is the primary replica. Then retry the operation. 41183 16 Failed to modify availability replica options for availability g roup '%.*ls'. Before the availability group configuration could be updated, the operation encountered SQL Server error %d. The operation has been rolled back. Refer to the SQL Server error log for more information. Verify that the local Windows Server Failover Clustering (WSFC) node is online, and retry the command . 41184 16 Failed to modify availability replica options for availability g roup '%.*ls'. The availability group configuration has been updated. However, the operation encountered SQL Server error %d while applying the new configurati

on to the local availability replica. The operation has been terminated. Refer to the SQL Server error log for more information. Verify that the local Window s Server Failover Clustering (WSFC) node is online. Use the ALTER AVAILABILITY GROUP command to undo the changes made to the availability group configuration. 41185 10 Replica option specified in ALTER AVAILABILITY GROUP '%.*ls' MOD IFY DDL is same is cached availability group configuration. 41186 16 Availability group '%.*ls' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is still being created. Ver ify that the specified availability group name is correct. Wait for CREATE AVAI LABILITY GROUP command to finish, and then retry the operation. 41187 16 Availability group '%.*ls' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is being dropped. Verify th at the specified availability group name is correct. The availability group may need to be recreated if it was dropped unintentionally. 41188 16 Availability group '%.*ls' failed to process %s-%s command. The operation encountered SQL Server error %d before the availability group configu ration could be updated, and has been rolled back. Refer to the SQL Server erro r log for details. Verify that the local Windows Server Failover Clustering (WS FC) node is online, and then retry the command. 41189 16 Availability group '%.*ls' failed to process the %s-%s command. The availability group configuration has been updated. However, the operation encountered SQL Server error %d while applying the new configuration to the loca l availability replica, and has been terminated. Refer to the SQL Server error log for details . Verify that the local Windows Server Failover Clustering node is online. Use an ALTER AVAILABILITY GROUP command to undo the changes to the availability group configuration. 41190 16 Availability group '%.*ls' failed to process %s-%s command. The local availability replica is not in a state that could process the command. V erify that the availability group is online and that the local availability repl ica is the primary replica, then retry the command. 41191 16 The local availability replica of availability group '%.*ls' can not become the primary replica. The last-known primary availability replica is of a higher version than the local availability replica. Upgrade the local inst ance of SQL Server to the same or later version as the server instance that is h osting the current primary availability replica, and then retry the command. 41192 17 Creating and scheduling a worker task for AlwaysOn Availability Groups failed due to lack of resources (SQL OS error %d). Processing of new ac tions might be delayed or stalled until the resource limits are resolved. Reduce the memory or thread count on the instance of SQL Server to allow new threads t o get scheduled. If new tasks are scheduled the problem might resolve itself. H owever, if the problem persists, you might need to restart the local instance of SQL Server. 41193 10 Cannot join database '%.*ls' to availability group '%.*ls'. The database is in the process of being removed from the availability group. When the remove-database operation completes, the database will no longer be joined t o the availability group. Then retry the join-database command. 41194 16 An error occurred while waiting for the local availability repli ca for availability group '%.*ls' to complet post-online work. The operation en countered SQL OS error %d and has been terminated. Verify that the Windows Serv er Failover Clustering (WSFC) cluster and the availability group are in the corr ect states for the command. Then retry the command. 41195 16 Availability group '%.*ls' failed to process the WSFC lease-rene wal command. The local availability replica lease is no longer valid to process the lease renewal command. Availability replica lease expired. This is an inform ational message only. No user action is required. 41196 16 Failed to create availability group '%.*ls', because a Windows S erver Failover Cluster (WSFC) group with the specified name already exists. An attempt to rollback the operation failed. Check the SQL Server error log for mo re details. To manually clean up the partially created availability group, run the DROP AVAILABILITY GROUP command. Reenter your CREATE AVAILABILITY GROUP com

mand specifying a unique availability group name. 41197 15 The FAILOVER_MODE option has not been specified for the replica '%.*ls'. Reenter the command, specifying a failover mode for the replica. 41198 15 The AVAILABILITY_MODE option has not been specified for the repl ica '%.*ls'. Reenter the command, specifying an availability mode for the replic a. 41199 16 The specified command is invalid because the AlwaysOn Availabili ty Groups feature is not supported by this edition of SQL Server. For informatio n about features supported by the editions of SQL Server, see SQL Server Books O nline. 41201 16 The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTIC SIMILARITYDETAILSTABLE functions do not support remote data sources. 41202 16 The source table '%.*ls' specified in the SEMANTICSIMILARITYTABL E, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function doesn't hav e a full-text index that uses the STATISTICAL_SEMANTICS option. A full-text ind ex using the STATISTICAL_SEMANTICS option is required to use this function. 41203 16 The column '%.*ls' specified in the SEMANTICSIMILARITYTABLE, SEM ANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function is not full-text indexed with the STATISTICAL_SEMANTICS option. The column must be full-text ind exed using the STATISTICAL_SEMANTICS option to be used in this function. 41204 16 The source_key parameter is required in the SEMANTICSIMILARITYTA BLE function. 41205 10 Error %d occurred during semantic index population for table or indexed view '%.*ls' (table or indexed view ID %d, database ID %d, document ID % d) 41206 10 An ALTER FULLTEXT INDEX statement cannot remove the 'STATISTICAL _SEMANTICS' option from the last column in the index that has the option set whe n a "WITH NO POPULATION" clause is specified. Remove the "WITH NO POPULATION" cl ause. 41207 10 A locale ID that is not supported was specified for a column wit h 'STATISTICAL_SEMANTICS'. Please verify that the locale ID is correct and that the corresponding language statistics has been installed. 41208 10 Warning: The population for table or indexed view '%ls' (table o r indexed view ID '%d', database ID '%d') encountered a document with full-text key value '%ls' that specifies a language not supported for semantic indexing. S ome columns of the row will not be part of the semantic index. 41209 10 A semantic language statistics database is not registered. Fulltext indexes using 'STATISTICAL_SEMANTICS' cannot be created or populated. 41210 10 The semantic language statistics database is not accessible or n ot valid. Full-text indexes using 'STATISTICAL_SEMANTICS' cannot be created or p opulated. 41211 16 A semantic language statistics database is already registered. 41212 16 No semantic language statistics database is registered. 41213 16 The database '%.*ls' does not exist or the database format is no t valid. Provide a valid semantic language statistics database name. 41214 16 An error occurred while trying to register the semantic language statistics database. 41215 16 The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTIC SIMILARITYDETAILSTABLE functions do not support update or insert. 41300 16 The current transaction cannot support any operations. Roll back the transaction. 41301 17 A previous transaction that the current transaction took a depen dency on has aborted and the current transaction can no longer commit. 41302 16 The current transaction attempted to update a record that has be en updated since this transaction started. The statement was terminated. 41303 16 The number of buckets for an in-memory table index must be a pow er of 2. 41304 10 The current value of option '%.*ls' for table '%.*ls', index '%. *ls' is %d. 41305 16 The current transaction failed to commit. Transaction state is %

d, result is %d, error is x%08lx. 41306 16 The nest limit of %d for conditional blocks and exception blocks for natively compiled stored procedures has been exceeded. Please simplify the stored procedure. 41307 16 The row size limit of %d for in-memory tables has been exceeded. Please simplify the table definition. 41308 16 The database %d has been deployed since the last drop database. 41309 16 Unable to load the compiled DLL for database %d. 41310 16 The database %d is not currently deployed. 41311 16 The file %.*ls could not be opened. GetLastError = 0x%x; 41312 16 Unable to call into the C compiler. GetLastError = 0x%x; 41313 16 The C compiler encountered a failure. The exit code was %d. 41314 16 Conversion of parameter default for parameter '%.*ls' failed. 41315 16 Checkpoint operation failed. 41316 16 Restore operation failed. 41317 16 A user transaction cannot call natively compiled procedures from more than one database. 41318 16 Distributed transactions are not supported for in-memory tables. 41319 16 At most %d conjuncts are allowed in queries inside compiled stor ed procedures. 41397 16 The database %d has not been deployed or has been dropped since it last was, so it cannot be dropped. 41398 16 The directory for temporary files "DRIVE:\Hekaton" cannot be fou nd. 41399 16 The error message for HRESULT 0x%x hasn't been implemented yet. 41401 16 WSFC cluster service is offline. 41402 16 The WSFC cluster is offline, and this availability group is not available. This issue can be caused by a cluster service issue or by the loss of quorum in the cluster. 41403 16 Availability group is offline. 41404 16 The availability group is offline, and is unavailable. This issu e can be caused by a failure in the server instance that hosts the primary repli ca or by the WSFC availability group resource going offline. 41405 16 Availability group is not ready for automatic failover. 41406 16 The availability group is not ready for automatic failover. The primary replica and a secondary replica are configured for automatic failover, h owever, the secondary replica is not ready for an automatic failover. Possibly t he secondary replica is unavailable, or its data synchronization state is curren tly not in the SYNCHRONIZED synchronization state. 41407 16 Some availability replicas are not synchronizing data. 41408 16 In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the prim ary replica. 41409 16 Some synchronous replicas are not synchronized. 41410 16 In this availability group, at least one synchronous replica is not currently synchronized. The replica synchronization state could be either SY NCHONIZING or NOT SYNCHRONIZING. 41411 16 Some availability replicas do not have a healthy role. 41412 16 In this availability group, at least one availability replica do es not currently have the primary or secondary role. 41413 16 Some availability replicas are disconnected. 41414 16 In this availability group, at least one secondary replica is no t connected to the primary replica. The connected state is DISCONNECTED. 41415 16 Availability replica does not have a healthy role. 41416 16 The role of this availability replica is unhealthy. The replica does not have either the primary or secondary role. 41417 16 Availability replica is disconnected. 41418 16 This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED. 41419 16 Data synchronization state of some availability database is not

healthy. 41420 16 At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit a vailability replica, all availability databases should be in the SYNCHRONIZING s tate. If this is a synchronous-commit availability replica, all availability dat abases should be in the SYNCHRONIZED state. 41421 16 Availability database is suspended. 41422 16 Either a database administrator or the system has suspended data synchronization on this availability database. 41423 16 Secondary database is not joined. 41424 16 This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete. For information abo ut how to join a secondary database to an availability group, see SQL Server Boo ks Online. 41425 16 Data synchronization state of availability database is not healt hy. 41426 16 The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability da tabase should be in the SYNCHRONIZING state. On a synchronous-commit replica, ev ery availability database should be in the SYNCHRONIZED state. 41427 16 Availability replica is not joined. 41428 16 This secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the join state must be Joined Standalone Instance (1) or Joined Failover Cluste r (2). For information about how-to join a secondary replica to an availability group, see SQL Server Books Online. 45001 16 %ls operation failed. Specified federation name does not exist. 45002 16 %ls operation failed. Specified federation distribution name %.* ls is not valid. 45003 16 %ls operation failed. Specified data type is not supported as a federation distribution. 45004 16 %ls operation failed. Specified value is not valid for federatio n distribution %.*ls and federation %.*ls. 45005 16 Filter value cannot be set or was already set for this session. 45006 16 The federation key value is out of bounds for this member. 45007 16 %ls cannot be run while another federation operation is in progr ess on federation %.*ls and member with id %d. 45008 16 A partition in a table group that has a partition key defined is not allowed to be a federation member. 45014 16 %ls is not supported on %S_MSG. 45015 16 Specified federation operation id is already in use. 45016 16 Specified federation %.*ls does not exist. 45017 16 %ls operation failed. Specified federation name %.*ls is not val id. 45018 16 Specified federation operation id is invalid for %ls operation. 45019 16 %ls operation failed. Federation is in invalid state. 45020 16 %ls operation failed. %d is not a valid federation id. 45021 16 %ls operation failed. %d is not a valid federation member id. 45022 16 A column insert or update conflicts with a federation member ran ge. The statement was terminated. The conflict occurred in database '%.*ls', tab le '%.*ls', column '%.*ls'. 45023 16 %ls cannot be called on %S_MSG. 45024 16 ALTER FEDERATION SPLIT operation failed. Specified boundary valu e already exists for federation distribution %.*ls and federation %.*ls. 45025 16 %ls operation failed. Specified boundary value is not valid for federation distribution %.*ls and federation %.*ls. 45026 16 %ls operation failed. Specified boundary value does not exist fo r federation distribution %.*ls and federation %.*ls. 45027 16 %ls operation failed. Specified type information is not valid fo r federation distribution.

45028 16 %ls operation failed. Specified boundary value is not valid for current federation member. 45029 16 %ls operation failed. The federation distribution scheme size ca nnot exceed 900 bytes. 45030 15 The USE FEDERATION statement is missing the required %.*ls optio n. Provide the option in the WITH clause of the statement. 45031 16 The USE FEDERATION statement is not supported on a connection wh ich has multiple active result sets (MARS) enabled. 45032 16 The USE FEDERATION statement is not allowed under non-revertible impersonated security context. 45033 16 Federation member %d is not available. Another command is creat ing or dropping it. 45034 16 Federation member database cannot be dropped using DROP DATABASE . 45035 16 Federation member database cannot be renamed using ALTER DATABAS E. 45036 16 ALTER FEDERATION SPLIT operation has been aborted. The %.*ls fed eration was dropped while the split was still in progress. 45037 16 ALTER FEDERATION SPLIT operation failed due to an internal error . This request has been assigned a tracing ID of '%.*ls'. Provide this tracing ID to customer support when you need assistance. 45038 16 CREATE DATABASE AS COPY OF %S_MSG is not supported. 45039 16 Federation member database cannot be restored. 49901 10 The number of max worker threads that is configured %u is less t han the minimum allowed on this computer. The default number of %u will be used instead. To change the number of max worker threads, use sp_configure 'max worke r threads'. 49902 10 There are not enough worker threads available for the number of CPUs. This is because one or more CPUs were added. To increase the number of wo rker threads, use sp_configure 'max worker threads'. 49903 10 Detected %I64d MB of RAM. This is an informational message; no u ser action is required. 49904 10 The service account is '%.*ls'. This is an informational message ; no user action is required. 49905 10 Error %u occurred while opening parameters file '%s'. Verify tha t the file exists, and if it exists, verify that it is a valid parameters file. 49906 10 Error %u occurred while processing parameters from either the re gistry or the command prompt. Verify your parameters. 49907 10 Ignored deprecated SQL Server startup parameters from the regist ry: %.*ls 49908 10 The following SQL Server startup parameters are either deprecate d or incorrectly specified: %.*ls 49909 10 Multiple instances of SQL server are installed on this computer. Renter the command, specifying the -s parameter with the name of the instance t hat you want to start. 49910 10 Software Usage Metrics is disabled. 49911 10 Software Usage Metrics failed to start. 49912 10 Software Usage Metrics is enabled. 49913 10 The server could not load DCOM. Software Usage Metrics cannot be started without DCOM.