Index of all Sqlserver error codes and solutions

Solution ID Description Links Comments
23003 The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again. 0 0
23100 Invalid input parameter(s). 0 0
23101 Access is denied. 0 0
23102 Item does not exist {ItemId: %ls}. 0 0
23103 Folder already exists {ItemId: %ls}. 0 0
23104 Folder does not exist {ItemId: %ls}. 0 0
23105 Operation violates hierarchical namespace uniqueness. 0 0
23106 Container is not empty {ItemId: %ls}. 0 0
23107 Item cannot be copied onto itself. 0 0
23108 Scoping path does not exist or is invalid. 0 0
23109 Container does not exist. 0 0
23110 No No more items to enumerate. 0 0
23111 Item does not exist in the given scope {ItemId: %ls, Scope: %ls}. 0 0
23112 Transaction not in active state. 0 0
23113 Item either does not exist or it is not a file-backed one. 0 0
23114 Sharing violation. 0 0
23115 Transaction bindtoken must be null when called within the context of a transaction. 0 0
23116 Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls}. 0 0
23117 File-backed item does not exist {ItemId: %ls}. 0 0
23200 ItemId of folder '%ls' not found. 0 0
23201 Share '%ls' does not exist in Catalog. 0 0
23202 Could not delete Share '%ls' in Catalog. 0 0
23203 Store item not found in Catalog. 0 0
23204 Could not delete Store item in Catalog. 0 0
23205 Store database name not found in Catalog. 0 0
23206 Could not create share to the ItemPath '%ls'. 0 0
23207 Could not add Share item for '%ls' in Catalog. 0 0
23208 ItemPath '%ls' does not exist in Store. 0 0
23209 Could not update Store state in Catalog. 0 0
23210 Itempath '%ls' is a file-backed item or within it's sub-tree. 0 0
23211 Could not start Store Manager. Please look in WinFS UT Log for details. 0 0
23212 Itempath '%ls' is a compound item. 0 0
23401 Operation failed with HRESULT 0x%x. 0 0
23402 Multiple store items were found for the given store name in the catalog. 0 0
23403 Cannot create a store with the specified name, it already exists. 0 0
23404 Cannot delete the system stores (Catalog or DefaultStore) 0 0
23405 Store not found. 0 0
23406 A share with the same name already exists. 0 0
23407 Could not find a share with the specified name. 0 0
23408 The specified itempath is invalid. 0 0
23409 Cannot delete system shares (Catalog or DefaultStore) 0 0
23410 System error occurred {ErrorCode: %d}. 0 0
23411 WinFS could not find the specified volume. 0 0
23412 WinFS Store manager is not ready for requests. 0 0
23413 WinFS Store Manager currently does not support non-system volumes. 0 0
23414 There was a timeout trying to get a lock on the volume object for this operation. 0 0
23415 The specified volume is not mounted or is not supported by WinFS 0 0
23416 Access Denied. Look in the WinFS UT log for more details. 0 0
23417 Invalid argument(S) 0 0
23418 Itempath is a compound item. 0 0
23419 Itempath is a file-backed item or within it's sub tree. 0 0
23420 Itempath does not exist in Store. 0 0
23421 Not enough memory available in the system to process the request. 0 0
23422 The Disk or File Group is full. 0 0
23423 Error accessing files on disk. Refer to the WinFS UT log for more information. 0 0
23424 The database operation was rolled back due to a deadlock. Refer to WinFS UT log for details. 0 0
23425 Cannot call sp_winfs_deletestore on a connection to the store specified for delete. 0 0
23426 Could not initialize the WSM memory clerk during startup. 0 0
23427 Could not initialize the WSM memory object during startup. 0 0
23428 Could not initialize WSM tracing during startup. 0 0
23500 Item container does not exist. 0 0
23501 Owning Item does not exist. 0 0
23502 NamespaceName is empty or exceeds the maximum length. 0 0
23503 Invalid Source endpoint type 0 0
23504 Invalid Target endpoint type 0 0
23505 A File-backed item must be a compound item type. 0 0
23506 A File Backed Item may not contain other Items. 0 0
23509 Source Item does not exist. 0 0
23510 Item with name already exists in container. 0 0
23511 New container cannot be a sub-container of item. 0 0
23513 Item does not exist. 0 0
23515 Item can not be deleted if it has children 0 0
23519 Target Item does not exist. 0 0
23525 Invalid Namespace Name. 0 0
23530 Operation can not be called inside a un-committable transaction 0 0
23536 Win32 file handle is open for item 0 0
23573 Cannot change ContainerId when replacing item. 0 0
23579 This procedure is reserved and cannot be called. 0 0
23587 File stream cannot be null. 0 0
23588 Container ids must be the same. 0 0
23996 The request could not be performed because of an device I/O error. 0 0
23997 System error occurred {ErrorCode: %d}. 0 0
23998 Not enough memory available in the system to process the request. 0 0
23999 Unspecified error(s) occurred. 0 0
8001 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter. 0 0
8002 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (XML) has an invalid database or schema specified. 0 0
8003 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is %d. 0 0
8004 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. The RPC name is invalid. 0 0
8005 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter name is invalid. 0 0
8006 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter status flags are invalid. 0 0
8007 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The chunking format is incorrect for a large object parameter of type 0x%02X. 0 0
8008 The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%d). 0 0
8009 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is unknown. 0 0
8010 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X is different from the one sent last time. 0 0
8011 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata. 0 0
8012 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata. 0 0
8013 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid instance length. 0 0
8014 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata. 0 0
8015 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X is an untyped NULL but is marked as an output parameter. 0 0
8016 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid data length or metadata length. 0 0
8017 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X has an invalid precision or scale. 0 0
8018 Invalid parameter %d ('%.*ls'): Data type 0x%02X is a deprecated large object, or LOB, but is marked as output parameter. Deprecated types are not supported as output parameters. Use current large object types instead. 0 0
8019 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid user type specified. 0 0
8020 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid length for serialization metadata. 0 0
8021 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid database specified. 0 0
8022 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied value is NULL and data type %.*ls cannot be NULL. Check the source data for invalid values. 0 0
8023 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied value is not a valid instance of data type %.*ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision. 0 0
8024 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type 0x%02X (sql_variant) has an invalid collation for type-specific metadata. 0 0
8025 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has a maximum length different from the one sent last time. 0 0
8026 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has an actual length different from the one sent last time. 0 0
8027 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): Data type "0x%02X" (CLR type) has an invalid schema specified. 0 0
8028 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d ("%.*ls"): The supplied length is not valid for data type %.*ls. Check the source data for invalid lengths. An example of an invalid length is data of nchar type with an odd length in bytes. 0 0
8029 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) unexpected token encountered processing a table-valued parameter. 0 0
8030 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (XML) has an invalid database or schema specified. 0 0
8031 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The chunking format is incorrect for a large object parameter of data type 0x%02X. 0 0
8032 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X is unknown. 0 0
8033 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata. 0 0
8034 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata. 0 0
8035 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid instance length. 0 0
8036 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata. 0 0
8037 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid data length or metadata length. 0 0
8038 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X has an invalid precision or scale. 0 0
8039 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid user type specified. 0 0
8040 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid length for serialization metadata. 0 0
8041 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid database specified. 0 0
8042 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The supplied value is NULL and data type %.*ls cannot be NULL. Check the source data for invalid values. 0 0
8043 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The supplied value is not a valid instance of data type %.*ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision. 0 0
8044 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid collation for type-specific metadata. 0 0
8045 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (CLR type) has an invalid schema specified. 0 0
8046 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: The supplied length is not valid for data type %.*ls. Check the source data for invalid lengths. An example of an invalid length is data of nchar type with an odd length in bytes. 0 0
8047 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has a non-zero length database name specified. Database name is not allowed with a table-valued parameter, only schema name and type name are valid. 0 0
8048 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid schema specified. 0 0
8049 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid type name specified. 0 0
8050 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column count specified. 0 0
8051 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column name specified. 0 0
8052 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) timestamp column is required to be default. 0 0
8053 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has an invalid column flag specified. 0 0
8054 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid ordering and uniqueness metadata specified. 0 0
8055 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has invalid column ordering metadata specified. 0 0
8056 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) has too many optional metadata tokens specified. 0 0
8057 Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type). The specified column is computed or default and has ordering or uniqueness set. Ordering and uniqueness can only be set on columns that have client supplied data. 0 0
8058 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d, to a parameterized string has no table type defined. 0 0
8059 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter "%.*ls", to a parameterized string has no table type defined. 0 0
8060 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d ("%.*ls"), row %I64d, column %d: Data type 0x%02X (user-defined table type) is null and not set to default. A null table-valued parameter is required to be sent as a default parameter. 0 0
8061 The data for table-valued parameter "%.*ls" doesn't conform to the table type of the parameter. 0 0
8062 The data for the table-valued parameter %d doesn't conform to the table type of the parameter. 0 0
8063 The incoming tabular data stream (TDS) remote procedure call stream is sending an unlimited length CLR type. Parameter %d ("%.*ls") is defined as type %.*ls. This type is not supported by down-level clients. Send the serialized data of the large CLR type as varbinary(max), or upgrade the client driver to one that supports unlimited CLR types. 0 0
8064 Parameter %d ([%.*ls].[%.*ls].[%.*ls]): The CLR type does not exist or you do not have permissions to access it. 0 0
8101 An explicit value for the identity column in table '%.*ls' can only be specified when a column list is used and IDENTITY_INSERT is ON. 0 0
8102 Cannot update identity column '%.*ls'. 0 0
8105 '%.*ls' is not a user table. Cannot perform SET operation. 0 0
8106 Table '%.*ls' does not have the identity property. Cannot perform SET operation. 0 0
8107 IDENTITY_INSERT is already ON for table '%.*ls.%.*ls.%.*ls'. Cannot perform SET operation for table '%.*ls'. 0 0
8108 Cannot add identity column, using the SELECT INTO statement, to table '%.*ls', which already has column '%.*ls' that inherits the identity property. 0 0
8109 Attempting to add multiple identity columns to table '%.*ls' using the SELECT INTO statement. 0 0
8110 Cannot add multiple PRIMARY KEY constraints to table '%.*ls'. 0 0
8111 Cannot define PRIMARY KEY constraint on nullable column in table '%.*ls'. 0 0
8112 Cannot add more than one clustered index for constraints on table '%.*ls'. 0 0
8113 Incorrect use of the XML data type method '%.*ls'. A mutator method is expected in this context. 0 0
8114 Error converting data type %ls to %ls. 0 0
8115 Arithmetic overflow error converting %ls to data type %ls. 0 0
8116 Argument data type %ls is invalid for argument %d of %ls function. 0 0
8117 Operand data type %ls is invalid for %ls operator. 0 0
8118 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause. 0 0
8119 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause. 0 0
8120 Column '%.*ls.%.*ls' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. 0 0
8121 Column '%.*ls.%.*ls' is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause. 0 0
8123 A correlated expression is invalid because it is not in a GROUP BY clause. 0 0
8124 Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression. 0 0
8125 An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated. 0 0
8126 Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause. 0 0
8127 Column "%.*ls.%.*ls" is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause. 0 0
8128 Using '%s' version '%s' to execute extended stored procedure '%s'. This is an informational message only; no user action is required. 0 0
8129 The new disk size must be greater than %d. Consider using DBCC SHRINKDB. 0 0
8131 Extended stored procedure DLL '%s' does not export __GetXpVersion(). Refer to the topic "Backward Compatibility Details (Level 1) - Open Data Services" in the documentation for more information. 0 0
8132 Extended stored procedure DLL '%s' reports its version is %d.%d. The expected version is %d.%d. 0 0
8133 None of the result expressions in a CASE specification can be NULL. 0 0
8134 Divide by zero error encountered. 0 0
8135 Table level constraint does not specify column list, table '%.*ls'. 0 0
8136 Duplicate columns specified in %ls constraint key list, table '%.*ls'. 0 0
8137 Incorrect use of the XML data type method '%.*ls'. A non-mutator method is expected in this context. 0 0
8138 More than 16 columns specified in foreign key column list, table '%.*ls'. 0 0
8139 Number of referencing columns in foreign key differs from number of referenced columns, table '%.*ls'. 0 0
8140 More than one key specified in column level %ls constraint, table '%.*ls'. 0 0
8141 Column %ls constraint for column '%.*ls' references another column, table '%.*ls'. 0 0
8143 Parameter '%.*ls' was supplied multiple times. 0 0
8144 Procedure or function %.*ls has too many arguments specified. 0 0
8145 %.*ls is not a parameter for procedure %.*ls. 0 0
8146 Procedure %.*ls has no parameters and arguments were supplied. 0 0
8147 Could not create IDENTITY attribute on nullable column '%.*ls', table '%.*ls'. 0 0
8148 More than one column %ls constraint specified for column '%.*ls', table '%.*ls'. 0 0
8149 OLE Automation objects are not supported in fiber mode. 0 0
8150 Multiple NULL constraints were specified for column '%.*ls', table '%.*ls'. 0 0
8151 Both a PRIMARY KEY and UNIQUE constraint have been defined for column '%.*ls', table '%.*ls'. Only one is allowed. 0 0
8152 String or binary data would be truncated. 0 0
8153 Warning: Null value is eliminated by an aggregate or other SET operation. 0 0
8154 The table '%.*ls' is ambiguous. 0 0
8155 No No column name was specified for column %d of '%.*ls'. 0 0
8156 The column '%.*ls' was specified multiple times for '%.*ls'. 0 0
8158 '%.*ls' has more columns than were specified in the column list. 0 0
8159 '%.*ls' has fewer columns than were specified in the column list. 0 0
8160 A GROUPING or GROUPING_ID function can only be specified when there is a GROUP BY clause. 0 0
8161 Argument %d of the %.*ls function does not match any of the expressions in the GROUP BY clause. 0 0
8162 The formal parameter "%.*ls" was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. 0 0
8164 An INSERT EXEC statement cannot be nested. 0 0
8165 Invalid subcommand value %d. Legal range from %d to %d. 0 0
8166 Constraint name '%.*ls' not permitted. Constraint names cannot begin with a number sign ( 0 0
8167 The type of column "%.*ls" conflicts with the type of other columns specified in the UNPIVOT list. 0 0
8168 Cannot create, drop, enable, or disable more than one constraint, column, or trigger named '%.*ls' in this context. Duplicate names are not allowed. 0 0
8169 Conversion failed when converting from a character string to uniqueidentifier. 0 0
8170 Insufficient result space to convert uniqueidentifier value to char. 0 0
8171 Hint '%ls' on object '%.*ls' is invalid. 0 0
8172 The argument %d of the XML data type method "%.*ls" must be a string literal. 0 0
8173 Incorrect syntax was used to invoke the XML data type method '%.*ls'. 0 0
8174 Schema lock with handle %d not found. 0 0
8175 Could not find table %.*ls. Will try to resolve this table name later. 0 0
8176 Resync procedure expects value of key '%.*ls', which was not supplied. 0 0
8177 Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause. 0 0
8178 The parameterized query '%.*ls' expects the parameter '%.*ls', which was not supplied. 0 0
8179 Could not find prepared statement with handle %d. 0 0
8180 Statement(s) could not be prepared. 0 0
8181 Text for '%.*ls' is missing from the system catalog. The object must be dropped and re-created before it can be used. 0 0
8183 Only UNIQUE or PRIMARY KEY constraints can be created on computed columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that computed columns be persisted. 0 0
8184 Error in binarychecksum. There are no comparable columns in the binarychecksum input. 0 0
8185 Error expanding "*": An incomparable column has been found in an underlying table or view. 0 0
8186 Function '%.*ls' can be used only on user and system tables. 0 0
8187 The prepared handle %d is currently being used by another command (error state: %d). 0 0
8188 There is already a SQL type for assembly type "%.*ls" on assembly "%.*ls". Only one SQL type can be mapped to a given assembly type. CREATE TYPE fails. 0 0
8189 You do not have permission to run '%ls'. 0 0
8190 Cannot compile replication filter procedure without defining table being filtered. 0 0
8191 Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements. 0 0
8192 Replication filter procedures cannot have parameters. 0 0
8193 Cannot execute a procedure marked FOR REPLICATION. 0 0
8195 Cannot create "%.*ls" on "%.*ls". Insert, Update, and Delete triggers can only be created on user tables and views. 0 0
8196 Duplicate column specified as ROWGUIDCOL. 0 0
8197 The object '%.*ls' does not exist or is invalid for this operation. 0 0
8199 In EXECUTE , procname can only be a literal or variable of type char, varchar, nchar, or nvarchar. 0 0
8301 Use of level0type with value 'USER' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Users are now schema scoped and hence use level0type with value 'SCHEMA' and level1type with value 'USER' for extended properties on USER. 0 0
8302 CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new development work, and plan to modify applications that currently use them. Use check constraints instead, which are created using the CHECK keyword of CREATE TABLE or ALTER TABLE. 0 0
8303 CREATE DEFAULT and DROP DEFAULT will be removed in a future version of SQL Server. Avoid using CREATE DEFAULT and DROP DEFAULT in new development work, and plan to modify applications that currently use them. Instead, use default definitions created using the DEFAULT keyword of ALTER TABLE or CREATE TABLE. 0 0
8304 INDEXKEY_PROPERTY will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use sys.index_columns instead. 0 0
8305 The TEXT IN ROW feature will be removed in a future version of SQL Server. Avoid using sp_tableoption for TEXT IN ROW option in new development work, and plan to modify applications that currently use the text in row option. The preferred method of storing large data is through use of the varchar(max), nvarchar(max) and varbinary(max) data types. 0 0
8306 Use of level0type with value 'TYPE' in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Types are now schema scoped and hence use level0type with value 'SCHEMA' and level1type with value 'TYPE' for extended properties on TYPE. 0 0
8307 FILE_ID will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use FILE_IDEX instead. 0 0
8308 USER_ID will be removed from a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use DATABASE_PRINCIPAL_ID instead. 0 0
8310 Cannot create (or open) named file mapping object '%ls'. SQL Server performance counters are disabled. 0 0
8311 Unable to map view of file mapping object '%ls' into SQL Server process address space. SQL Server performance counters are disabled. 0 0
8312 Cannot create (or open) named mutex '%ls'. SQL Server performance counters are disabled. 0 0
8313 Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled. 0 0
8314 SQL Server performance object '%ls' not found in registry. SQL Server performance counters are disabled. 0 0
8315 SQL Server performance counter '%ls' not found in registry. SQL Server performance counters are disabled. 0 0
8316 Cannot open registry key 'HKLM\%ls'. SQL Server performance counters are disabled. 0 0
8317 Cannot query value '%ls' associated with registry key 'HKLM\%ls'. SQL Server performance counters are disabled. 0 0
8318 There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters are disabled. 0 0
8319 Windows kernel object '%ls' already exists. It's not owned by the SQL Server service account. SQL Server performance counters are disabled. 0 0
8320 @@REMSERVER will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use linked servers and linked server stored procedures instead. 0 0
8350 Use of NOLOCK or READUNCOMMITTED hints in the FROM clause of an UPDATE or DELETE statement on the target table of the statement ('%.*ls') is deprecated. These hints have no effect in this location. Microsoft recommends that you remove these hints from this statement. Support for these hints in this location will be removed in a future version of SQL Server. 0 0
8351 A trace control request could not be processed because invalid parameters were specified when events were registered. Confirm that the parameters are within valid ranges. 0 0
8352 Cannot find the requested trace template: id = %ls. 0 0
8353 Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server. 0 0
8354 Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls. 0 0
8355 Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker. 0 0
8356 Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future. 0 0
8357 Event Tracing for Windows (ETW) failed to send event. This may be due to low resource conditions. The same send failure may not be reported in the future. 0 0
8358 Event Tracing for Windows (ETW) failed to send event. Event message size exceeds limit. The same send failure may not be reported in the future. 0 0
8359 SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported in the future. 0 0
8360 SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future. 0 0
8379 Old style RAISERROR (Format: RAISERROR integer string) will be removed in the next version of SQL Server. Avoid using this in new development work, and plan to modify applications that currently use it to use new style RAISERROR. 0 0
8380 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server '%.*ls'. 0 0
8381 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) for ad hoc connection to SQL Server. 0 0
8382 Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version. 0 0
8383 Specifying HOLDLOCK as a table hint without parentheses is a deprecated feature and will be removed in the next version of SQL Server. 0 0
8384 Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints. 0 0
8385 The select list of an aggregate indexed view must contain count_big(*) in 90 compatibility mode and higher. 0 0
8386 Use of hint "%.*ls" on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove the use of this hint. 0 0
8387 The indirect application of table hints to an invocation of a multi-statement table-valued function (TVF) through a view will be removed in a future version of SQL Server. Remove hints on references to view "%.*ls" because it references a multi-statement TVF. 0 0
8388 The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
8389 The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work and plan to modify applications that currently use it. 0 0
8390 The '::' function calling syntax will be removed in a future version of SQL Server. Replace it with "sys.". 0 0
8391 The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX <1p-name> ON {<3p-table-name> | <3p-view-name> } 0 0
8393 The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
8394 Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future version of SQL Server. Avoid using this syntax structure in new development work, and plan to modify applications that currently use the feature. 0 0
8396 %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use %ls instead. 0 0
8397 The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types instead. 0 0
8398 The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
8399 %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
8401 This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue '%.*ls'. 0 0
8402 The data type of the '%S_MSG' in the '%S_MSG' statement must be %s. The %s data type is not allowed. 0 0
8403 The message type '%.*ls' is specified more than once. Remove the duplicate message type. 0 0
8404 The service contract '%.*ls' is specified more than once. Remove the duplicate service contract. 0 0
8405 An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i. 0 0
8406 The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d. 0 0
8407 Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint. 0 0
8408 Target service '%.*ls' does not support contract '%.*ls'. 0 0
8409 This message could not be delivered because the targeted service does not support the service contract. Targeted service: '%.*ls', service contract: '%.*ls'. 0 0
8410 The conversation timer cannot be set beyond the conversation's lifetime. 0 0
8411 The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value. 0 0
8412 The syntax of the service name '%.*ls' is invalid. 0 0
8413 The syntax of the broker instance '%.*ls' is invalid. The specified broker instance is too long, the maximum size is 256 bytes. 0 0
8414 The conversation group ID '%.*ls' is invalid in this context. Specify a different conversion group ID. 0 0
8415 The activated task was aborted because the invoked stored procedure '%ls' did not issue COMMIT or ROLLBACK on one or more transactions that it begun. 0 0
8417 The service contract name is NULL. Specify a service contract name. 0 0
8418 The conversation handle is missing. Specify a conversation handle. 0 0
8419 Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL. 0 0
8420 The conversation group is missing. Specify a conversation group. 0 0
8421 The service name is missing. Specify a service name. 0 0
8422 The error description is missing. Specify a description of the error. 0 0
8423 The service "%.*ls" is not found. 0 0
8424 The error code and error description are missing. Specify both the error code and description of the error. 0 0
8425 The service contract '%.*ls' is not found. 0 0
8426 The conversation handle "%.*ls" is not found. 0 0
8427 The conversation endpoint is not in a valid state for END CONVERSATION. The current endpoint state is '%ls'. 0 0
8428 The message type "%.*ls" is not found. 0 0
8429 The conversation endpoint is not in a valid state for SEND. The current endpoint state is '%ls'. 0 0
8430 The message body failed the configured validation. 0 0
8431 The message type '%.*ls' is not part of the service contract. 0 0
8432 The message cannot be sent because the message type '%.*ls' is marked SENT BY TARGET in the contract, however this service is an Initiator. 0 0
8433 The message body may not be NULL. A zero-length UNICODE or binary string is allowed. 0 0
8434 The message cannot be sent because the message type '%.*ls' is marked SENT BY INTITIATOR in the contract, however this service is a Target. 0 0
8436 The conversation group "%.*ls" is not found. 0 0
8437 The message received was sent by a Target service, but the message type '%.*ls' is marked SENT BY INITIATOR in the contract. 0 0
8438 The conversation endpoint is not in a valid state for MOVE CONVERSATION. The current endpoint state is '%ls'. 0 0
8439 The destination conversation group '%.*ls' is invalid. 0 0
8440 The conversation group exists, but no queue exists. Possible database corruption. Run DBCC CHECKDB. 0 0
8442 There is no Service Broker active in the database. Change to a database context that contains a Service Broker. 0 0
8443 The conversation with ID '%.*ls' and initiator: %d references a missing conversation group '%.*ls'. Run DBCC CHECKDB to analyze and repair the database. 0 0
8444 The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB. 0 0
8445 The conversation handle '%ls' is referencing an invalid conversation ID '%ls', initiator: %d. 0 0
8447 A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations. 0 0
8450 Assignments in the RECEIVE projection are not allowed in conjunction with the INTO clause. 0 0
8457 The message received was sent by the initiator of the conversation, but the message type '%.*ls' is marked SENT BY TARGET in the contract. 0 0
8458 The conversation endpoint is not in a valid state for BEGIN CONVERSATION TIMER. The current endpoint state is '%ls'. 0 0
8459 The message size, including header information, exceeds the maximum allowed of %d. 0 0
8460 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation handle '%ls'. 0 0
8461 An internal service broker error detected. Possible database corruption. Run DBCC CHECKDB. 0 0
8462 The remote conversation endpoint is either in a state where no more messages can be exchanged, or it has been dropped. 0 0
8463 Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem. If the problem persists, the database may be damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database. 0 0
8468 Underlying service has been altered. 0 0
8469 Remote service has been altered. 0 0
8470 Remote service has been dropped. 0 0
8471 An SNI call failed during a Service Broker/Database Mirroring transport operation. SNI error '%ls'. 0 0
8472 The remote service has sent a message that contains invalid header fields. 0 0
8475 The conversation endpoint with ID '%ls' and is_initiator: %d has been dropped. 0 0
8477 An internal Service Broker error occurred (error = 0x%08x). This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems. The database may have been damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database. 0 0
8479 Used by test in failpoint simulation. 0 0
8487 The remote service contract has been dropped. 0 0
8489 The dialog has exceeded the specified LIFETIME. 0 0
8490 Cannot find the remote service '%.*ls' because it does not exist. 0 0
8492 The service contract '%.*ls' must have at least one message SENT BY INITIATOR or ANY. 0 0
8493 The alter of service '%.*ls' must change the queue or at least one contract. 0 0
8494 You do not have permission to access the service '%.*ls'. 0 0
8495 The conversation has already been acknowledged by another instance of this service. 0 0
8498 The remote service has sent a message of type '%.*ls' that is not part of the local contract. 0 0
8499 The remote service has sent a message body of type '%.*ls' that does not match the message body encoding format. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
8501 MSDTC on server '%.*ls' is unavailable. 0 0
8502 Unknown token '0x%x' received from Microsoft Distributed Transaction Coordinator (MS DTC) . 0 0
8504 The import buffer for this transaction is not valid. 0 0
8506 Cannot change transaction state from %hs to %hs. The change requested is not valid. 0 0
8508 QueryInterface failed for "%ls": %ls. 0 0
8509 Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls. 0 0
8510 Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager. 0 0
8511 Unknown isolation level 0x%x requested from Microsoft Distributed Transaction Coordinator (MS DTC). 0 0
8512 Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs. 0 0
8513 Microsoft Distributed Transaction Coordinator (MS DTC) end transaction acknowledgement failed: %hs. 0 0
8514 Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs. 0 0
8515 Microsoft Distributed Transaction Coordinator (MS DTC) global state is not valid. 0 0
8517 Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls. 0 0
8518 Microsoft Distributed Transaction Coordinator (MS DTC) BEGIN TRANSACTION failed: %ls. 0 0
8519 Current Microsoft Distributed Transaction Coordinator (MS DTC) transaction must be committed by remote client. 0 0
8520 Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: %ls. 0 0
8521 This awakening state is not valid: slept in %hs; awoke in %hs. 0 0
8522 Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction. 0 0
8523 PREPARE TRAN statement not allowed on MSDTC transaction. 0 0
8524 The current transaction could not be exported to the remote provider. It has been rolled back. 0 0
8525 Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. 0 0
8526 Cannot go remote while the session is enlisted in a distributed transaction that has an active savepoint. 0 0
8527 An attempt to create a distributed transaction export token failed with this error: %ls. Contact your Microsoft Distributed Transaction Coordinator (MS DTC) system administrator. 0 0
8528 The commit of the Kernel Transaction Manager (KTM) transaction failed: %d. 0 0
8529 Unable to extract the Kernel Transaction Manager (KTM) transaction handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transaction: 0x%x. 0 0
8530 The Windows kernel transaction manager creation failed: 0x%x. 0 0
8531 The Windows kernel transaction manager failed to create the enlistment: 0x%08x. 0 0
8532 Error while reading resource manager notification from Kernel Transaction Manager (KTM): %d. 0 0
8533 Error while waiting for communication from Kernel Transaction Manager (KTM): %d. 0 0
8534 The KTM RM for this database, %ls, failed to start: %d. 0 0
8535 A savepoint operation in the Windows transactional file system failed: 0x%x. 0 0
8536 Only single DB updates are allowed with FILESTREAM operations. 0 0
8537 This transaction was aborted by Kernel Transaction Manager (KTM). 0 0
8538 The current isolation level is not supported by the FILESTREAM 0x%x. 0 0
8539 The distributed transaction with UOW %ls was forced to commit. MS DTC became temporarily unavailable and forced heuristic resolution of the transaction. This is an informational message only. No user action is required. 0 0
8540 The distributed transaction with UOW %ls was forced to rollback. 0 0
8541 System process ID %d tried to terminate the distributed transaction with Unit of Work ID %ls. This message occurs when the client executes a KILL statement on the distributed transaction. 0 0
8542 Spid %d tried to commit the distributed transaction with UOW %ls. 0 0
8543 Unable to commit a prepared transaction from the Microsoft Distributed Transaction Coordinator (MS DTC). Shutting down server to initiate resource manager (RM) recovery. When the RM recovers, it will query the transaction manager about the outcome of the in-doubt transaction, and commit or roll back accordingly. 0 0
8544 Unknown status of commit of a two-phase commit transaction. Shutting down server. Restart server to complete recovery. 0 0
8545 Unknown status '%d' from Reenlist call in rm_resolve. 0 0
8546 Unable to load Microsoft Distributed Transaction Coordinator (MS DTC) library. This error indicates that MS DTC is not installed. Install MS DTC to proceed. 0 0
8547 Resource Manager Creation Failed: %ls 0 0
8548 DTC not initialized because it's unavailable 0 0
8549 GetWhereaboutsSize call failed: %ls 0 0
8550 MS DTC initialization failed because the transaction manager address is invalid. The protocol element used to carry address information may be too large. A network protocol analyzer may provide additional information about the cause. Contact your application support provider or Microsoft Product Support Services. 0 0
8551 CoCreateGuid failed: %ls. 0 0
8552 RegOpenKeyEx of \"%ls\" failed: %ls. 0 0
8553 RegQueryValueEx of \"%hs\" failed: %ls. 0 0
8554 IIDFromString failed for %hs, (%ls). 0 0
8555 RegCloseKey failed: %ls 0 0
8556 Microsoft Distributed Transaction Coordinator (MS DTC) initialization failed due to insufficient memory. It may be necessary to change some server configuration options to make more memory available. 0 0
8557 The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service. 0 0
8558 RegDeleteValue of \"%hs\" failed: %ls. 0 0
8560 Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 0 0
8561 Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required. 0 0
8562 The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required. 0 0
8563 An error occurred while trying to determine the state of the RPCSS service. A call to "%ls" returned: %ls. This is an informational message only. No user action is required. 0 0
8565 SQL Server failed to prepare DTC transaction. Failure code: %d. 0 0
8601 Internal Query Processor Error: The query processor could not obtain access to a required interface. 0 0
8602 Indexes used in hints must be explicitly included by the index tuning wizard. 0 0
8603 Invalid syntax for internal DBCC REPAIR statement. 0 0
8604 ALTER TABLE SWITCH statement failed. Table '%.*ls' has a column level check constraint '%.*ls' on column '%.*ls' that is not loadable for semantic validation. 0 0
8605 Index creation operation will use %ld KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of %lu KB specified in "index create memory (KB)" option because the former has to be smaller than the latter. 0 0
8606 This index operation requires %I64d KB of memory per DOP. The total requirement of %I64d KB for DOP of %lu is greater than the sp_configure value of %lu KB set for the advanced server configuration option "index create memory (KB)". Increase this setting or reduce DOP and rerun the query. 0 0
8607 The table '%.*ls' cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online. 0 0
8608 The query could not be completed due to an online index build operation and must be recompiled. 0 0
8616 The index hints for table '%.*ls' were ignored because the table was considered a fact table in the star join. 0 0
8618 The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. If the query has a GROUP BY or ORDER BY clause, consider reducing the number and/or size of the fields in the clause. Consider using prefix (LEFT()) or hash (CHECKSUM()) of fields for grouping or prefix for ordering. Note however that this will change the behavior of the query. 0 0
8619 The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. Resubmit your query without the ROBUST PLAN hint. 0 0
8621 The query processor ran out of stack space during query optimization. Please simplify the query. 0 0
8622 Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN. 0 0
8623 The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information. 0 0
8624 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. 0 0
8625 Warning: The join order has been enforced because a local join hint is used. 0 0
8628 A time out occurred while waiting to optimize the query. Rerun the query. 0 0
8630 Internal Query Processor Error: The query processor encountered an unexpected error during execution. 0 0
8631 Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it. 0 0
8632 Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them. 0 0
8633 The query processor could not produce a query plan because distributed query does not support materializing intermediate results with default in DML queries over remote sources. Try to use actual default values instead of default or split the update into multiple statements, one only containing the DEFAULT assignment, the other with the rest. 0 0
8634 The query processor received an error from a cluster communication layer. 0 0
8635 The query processor could not produce a query plan for a query with a spatial index hint. Reason: %S_MSG. Try removing the index hints or removing SET FORCEPLAN. 0 0
8636 The query processor could not produce a query plan because there is a subquery in the predicate of the full outer join. This is not supported for distributed queries. 0 0
8637 The query processor could not produce a query plan because a USE PLAN hint was used for a query that modifies data while the target table of the modification has an index that is currently being built online. Consider waiting until the online index build is done before forcing the plan, or using another way to tune the query, such as updating statistics, or using a different hint or a manual query rewrite. 0 0
8642 The query processor could not start the necessary thread resources for parallel query execution. 0 0
8644 Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine. 0 0
8645 A timeout occurred while waiting for memory resources to execute the query in resource pool '%ls' (%ld). Rerun the query. 0 0
8646 Unable to find index entry in index ID %d, of table %d, in database '%.*ls'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support. 0 0
8648 Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint. 0 0
8649 The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator. 0 0
8651 Could not perform the operation because the requested memory grant was not available in resource pool '%ls' (%ld). Rerun the query, reduce the query load, or check resource governor configuration setting. 0 0
8653 The query processor is unable to produce a plan for the table or view '%.*ls' because the table resides in a filegroup which is not online. 0 0
8655 The query processor is unable to produce a plan because the index '%.*ls' on table or view '%.*ls' is disabled. 0 0
8656 The query processor could not produce a query plan. Resubmit the query after disabling trace flag %d. 0 0
8657 Could not get the memory grant of %I64d KB because it exceeds the maximum configuration limit in workload group '%ls' (%ld) and resource pool '%ls' (%ld). Contact the server administrator to increase the memory usage limit. 0 0
8660 Cannot create the clustered index "%.*ls" on view "%.*ls" because the select list of the view definition does not include all columns in the GROUP BY clause. Consider adding these columns to the select list. 0 0
8661 Cannot create the clustered index "%.*ls" on view "%.*ls" because the index key includes columns that are not in the GROUP BY clause. Consider eliminating columns that are not in the GROUP BY clause from the index key. 0 0
8662 Cannot create the clustered index "%.*ls" on view "%.*ls" because the view references an unknown value (SUM aggregate of nullable expression). Consider referencing only non-nullable values in SUM. ISNULL() may be useful for this. 0 0
8663 Cannot create the clustered index "%.*ls" on view "%.*ls" because its select list does not include COUNT_BIG(*). Consider adding COUNT_BIG(*) to the select list. 0 0
8665 Cannot create the clustered index "%.*ls" on view "%.*ls" because no row can satisfy the view definition. Consider eliminating contradictions from the view definition. 0 0
8668 Cannot create the clustered index '%.*ls' on view '%.*ls' because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from select list. 0 0
8669 The attempt to maintain the indexed view "%.*ls" failed because it contains an expression on aggregate results, or because it contains a ranking or aggregate window function. Consider dropping the clustered index on the view, or changing the view definition. 0 0
8670 Query optimizer reached the internal limit of the maximum number of views that can be used during optimization. 0 0
8671 The attempt to maintain the indexed view "%.*ls" failed because of the ignore_dup_key option on index "%.*ls". Drop the index or re-create it without the ignore_dup_key index option. 0 0
8672 The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows. 0 0
8673 A MERGE statement is not valid if it triggers both the 'ON DELETE SET NULL' and 'ON UPDATE CASCADE' actions for a referential integrity constraint. Modify the actions performed by the MERGE statement to ensure that it does not trigger both these actions for a referential integrity constraint. 0 0
8680 Internal Query Processor Error: The query processor encountered an unexpected error during the processing of a remote query phase. 0 0
8682 SELECT via cursor failed because in XML plan provided to USE PLAN hint, neither Populate nor Fetch plans are provided, and at least one must be present. For best likelihood of successful plan forcing, use an XML cursor plan captured from SQL Server without modification. 0 0
8683 Could not force query plan because XML showplan provided in USE PLAN hint contains invalid Star Join specification. Consider specifying a USE PLAN hint that contains an unmodified XML showplan produced by SQL Server. This may allow you to force the plan. 0 0
8684 A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified in USE PLAN hint. First consider removing USE PLAN hint. Then if necessary consider (1) updating statistics, (2) using other hints such as join hints, index hints, or the OPTIMIZE FOR hint, (3) rewriting query or breaking it down into two or more separate queries. 0 0
8685 Query cannot be compiled because element appears in XML plan provided to USE PLAN but USE PLAN was applied to a non-cursor statement. Consider using an XML plan obtained from SQL Server for statement without modification. 0 0
8686 Cursor plan forcing failed because input plan has more than one node with OperationType=%ls. Consider using an XML cursor plan captured from SQL Server without modification. 0 0
8687 Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with a USE PLAN hint. Consider removing USE PLAN hint and updating statistics or using different hints to influence query plan choice. 0 0
8688 Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %ls is missing under element. Consider using an XML cursor plan captured from SQL Server without modification. 0 0
8689 Database '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing database. 0 0
8690 Query cannot be compiled because USE PLAN hint conflicts with hint %ls. Consider removing hint %ls. 0 0
8691 Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF. 0 0
8693 Cannot compile query because combination of LogicalOp = '%ls', PhysicalOp = '%ls', and sub_element = '%ls' under RelOp element in XML plan in USE PLAN hint is not valid. Use a recognized combination instead. Consider using an automatically generated XML plan without modification. 0 0
8694 Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint. 0 0
8695 Cannot execute query because of incorrectly formed XML plan in USE PLAN hint. Verify that XML plan is a legal plan suitable for plan forcing. See Books Online for additional details. 0 0
8696 Cannot run query because of improperly formed Spool element with parent RelOp with NodeId %d in XML plan in USE PLAN hint. Verify that each Spool element's parent RelOp has unique NodeId attribute, and each Spool element has either a single RelOp sub-element, or a PrimaryNodeId attribute, but not both. PrimaryNodeId of Spool must reference NodeId of an existing RelOp with a Spool sub-element. Consider using unmodified XML showplan as USE PLAN hint. 0 0
8697 Cannot run query because in XML plan provided to USE PLAN, element %ls must have %d %ls nodes as children, but has %d. 0 0
8698 Query processor could not produce query plan because USE PLAN hint contains plan that could not be verified to be legal for query. Remove or replace USE PLAN hint. For best likelihood of successful plan forcing, verify that the plan provided in the USE PLAN hint is one generated automatically by SQL Server for the same query. 0 0
8699 Cannot run query because it contains more than one USE PLAN hint. Use at most one USE PLAN hint. 0 0
8710 Aggregate functions that are used with CUBE, ROLLUP, or GROUPING SET queries must provide for the merging of subaggregates. To fix this problem, remove the aggregate function or write the query using UNION ALL over GROUP BY clauses. 0 0
8711 Multiple ordered aggregate functions in the same scope have mutually incompatible orderings. 0 0
8712 Index '%.*ls', specified in the USE PLAN hint, does not exist. Specify an existing index, or create an index with the specified name. 0 0
8720 Cannot execute query. There is more than one TABLE HINT clause specified for object '%.*ls'. Use at most one such TABLE HINT clause per table reference. 0 0
8721 Cannot execute query. TABLE HINT in the OPTION clause leads to ambiguous reference for object '%.*ls'. Consider USE PLAN query hint instead. 0 0
8722 Cannot execute query. Semantic affecting hint '%.*ls' appears in the '%.*ls' clause of object '%.*ls' but not in the corresponding '%.*ls' clause. Change the OPTION (TABLE HINTS...) clause so the semantic affecting hints match the WITH clause. 0 0
8723 Cannot execute query. Object '%.*ls' is specified in the TABLE HINT clause, but is not used in the query or does not match the alias specified in the query. Table references in the TABLE HINT clause must match the WITH clause. 0 0
8724 Cannot execute query. Table-valued or OPENROWSET function '%.*ls' cannot be specified in the TABLE HINT clause. 0 0
8901 Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object. 0 0
8902 Memory allocation error during DBCC processing. 0 0
8903 Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID. 0 0
8904 Extent %S_PGID in database ID %d is allocated by more than one allocation object. 0 0
8905 Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it. 0 0
8906 Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags '%hs'. 0 0
8907 The spatial index, XML index or indexed view '%.*ls' (object ID %d) contains rows that were not produced by the view definition. This does not necessarily represent an integrity issue with the data in this database. For more information about troubleshooting DBCC errors on indexed views, see SQL Server Books Online. 0 0
8908 The spatial index, XML index or indexed view '%.*ls' (object ID %d) does not contain all rows that the view definition produces. This does not necessarily represent an integrity issue with the data in this database. For more information about troubleshooting DBCC errors on spatial indexes, XML indexes, and indexed views, see SQL Server Books Online. 0 0
8909 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID. 0 0
8910 Page %S_PGID in database ID %d is allocated to both object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), and object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
8911 The error has been repaired. 0 0
8912 %.*ls fixed %d allocation errors and %d consistency errors in database '%ls'. 0 0
8913 Extent %S_PGID is allocated to '%ls' and at least one other object. 0 0
8914 Incorrect PFS free space information for page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Expected value %hs, actual value %hs. 0 0
8915 File %d (number of mixed extents = %I64d, mixed pages = %I64d). 0 0
8916 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), data extents %I64d, pages %I64d, mixed extent pages %I64d. 0 0
8917 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d. 0 0
8918 (number of mixed extents = %I64d, mixed pages = %I64d) in this database. 0 0
8919 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The record count in the header (%d) does not match the number of records (%d) found on page %S_PGID. 0 0
8920 Cannot perform a %ls operation inside a user transaction. Terminate the transaction and reissue the statement. 0 0
8921 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors. 0 0
8922 Could not repair this error. 0 0
8923 The repair level on the DBCC statement caused this repair to be bypassed. 0 0
8924 Repairing this error requires other errors to be corrected first. 0 0
8925 Table error: Cross object linkage: Page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), refers to page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
8926 Table error: Cross object linkage: Parent page %S_PGID, slot %d in object %d, index %d, partition %I64d, AU %I64d (%.*ls), and page %S_PGID->next in object %d, index %d, partition %I64d, AU %I64d (%.*ls), refer to page %S_PGID but are not in the same object. 0 0
8927 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The ghosted record count in the header (%d) does not match the number of ghosted records (%d) found on page %S_PGID. 0 0
8928 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Page %S_PGID could not be processed. See other errors for details. 0 0
8929 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Errors found in off-row data with ID %I64d owned by %ls record identified by %.*ls 0 0
8930 Database error: Database %d has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. Please restore from a backup. 0 0
8931 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from parent %S_PGID. 0 0
8932 Could not find filegroup ID %d in sys.filegroups for database '%ls'. 0 0
8933 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The low key value on page %S_PGID (level %d) is not >= the key value in the parent %S_PGID slot %d. 0 0
8934 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The high key value on page %S_PGID (level %d) is not less than the low key value in the parent %S_PGID, slot %d of the next page %S_PGID. 0 0
8935 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page. 0 0
8936 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID. 0 0
8937 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d. 0 0
8938 Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d. 0 0
8939 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Values are %ld and %ld. 0 0
8940 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned. 0 0
8941 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid. 0 0
8942 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row. 0 0
8943 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x. 0 0
8944 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld. 0 0
8945 Table error: Object ID %d, index ID %d will be rebuilt. 0 0
8946 Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page. 0 0
8947 Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID. 0 0
8948 Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x. 0 0
8949 %.*ls fixed %d allocation errors and %d consistency errors in table '%ls' (object ID %d). 0 0
8950 %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object. 0 0
8951 Table error: table '%ls' (ID %d). Data row does not have a matching index row in the index '%ls' (ID %d). Possible missing or invalid keys for the index row matching: 0 0
8952 Table error: table '%ls' (ID %d). Index row in index '%ls' (ID %d) does not match any data row. Possible extra or invalid keys for: 0 0
8953 Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d. 0 0
8954 %.*ls found %d allocation errors and %d consistency errors not associated with any single object. 0 0
8955 Data row (%d:%d:%d) identified by (%ls) with index values '%ls'. 0 0
8956 Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls). 0 0
8957 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls 0 0
8958 %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls). 0 0
8959 Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID. 0 0
8960 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column. 0 0
8961 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d. 0 0
8962 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d. 0 0
8963 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d. 0 0
8964 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced. 0 0
8965 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan. 0 0
8966 Unable to read and latch page %S_PGID with latch type %ls. %ls failed. 0 0
8967 An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services. 0 0
8968 Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database. 0 0
8969 Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID. 0 0
8970 Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column '%.*ls' was created NOT NULL, but is NULL in the row. 0 0
8971 Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d 0 0
8972 Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d. 0 0
8973 CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice. 0 0
8974 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d. 0 0
8975 DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error. 0 0
8976 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors. 0 0
8977 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered. 0 0
8978 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem. 0 0
8979 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog. 0 0
8980 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered. 0 0
8981 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage. 0 0
8982 Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index. 0 0
8983 File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d. 0 0
8984 Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for: 0 0
8985 Could not locate file '%.*ls' for database '%.*ls' in sys.database_files. The file either does not exist, or was dropped. 0 0
8986 Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS". 0 0
8987 No No help available for DBCC statement '%.*ls'. 0 0
8988 Row (%d:%d:%d) identified by (%ls). 0 0
8989 %.*ls found %d allocation errors and %d consistency errors in database '%ls'. 0 0
8990 %.*ls found %d allocation errors and %d consistency errors in table '%ls' (object ID %d). 0 0
8991 0x%p to 0x%p is not a valid address range. 0 0
8992 Check Catalog Msg %d, State %d: %.*ls 0 0
8993 Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error. 0 0
8994 Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error. 0 0
8995 System table '%.*ls' (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d. 0 0
8996 IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) controls pages in filegroup %d, that should be in filegroup %d. 0 0
8997 Service Broker Msg %d, State %d: %.*ls 0 0
8998 Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID %d pages from %S_PGID to %S_PGID. See other errors for cause. 0 0
8999 Database tempdb allocation errors prevent further %ls processing. 0 0
3002 Cannot BACKUP or RESTORE a database snapshot. 0 0
3003 This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before attempting to restore this differential backup. 0 0
3004 The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS. 0 0
3005 The differential partial backup is including a read-only filegroup, '%ls'. This filegroup was read-write when the base partial backup was created, but was later changed to read-only access. We recommend that you create a separate file backup of the '%ls' filegroup now, and then create a new partial backup to provide a new base for later differential partial backups. 0 0
3006 The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups are not allowed in the simple recovery model, and are never allowed for partial differential backups. 0 0
3007 The backup of the file or filegroup "%ls" is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. 0 0
3008 The specified device type is not supported for backup mirroring. 0 0
3009 Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful. 0 0
3010 Invalid backup mirror specification. All mirrors must have the same number of members. 0 0
3011 All backup devices must be of the same general class (for example, DISK and TAPE). 0 0
3012 VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer. 0 0
3013 %hs is terminating abnormally. 0 0
3014 %hs successfully processed %I64d pages in %d.%03d seconds (%d.%03d MB/sec). 0 0
3015 %hs is not yet implemented. 0 0
3016 Backup of file '%ls' is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taking the backup, or restrict the backup to exclude this file. 0 0
3017 The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Correct the problem, or reissue the command without RESTART. 0 0
3018 The restart-checkpoint file '%ls' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified. 0 0
3019 The restart-checkpoint file '%ls' is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The restart command must use the same syntax as the interrupted command, with the addition of the RESTART clause. Alternatively, reissue the current statement without the RESTART clause. 0 0
3021 Cannot perform a backup or restore operation within a transaction. 0 0
3022 This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate if you plan to set the filegroup to read-only followed by a differential file backup. Consult Books Online for more information on managing read-only data for the simple recovery model. In particular, consider how partial backups are used. 0 0
3023 Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed. 0 0
3024 You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database. 0 0
3025 Missing database name. Reissue the statement specifying a valid database name. 0 0
3027 The filegroup "%.*ls" is not part of database "%.*ls". 0 0
3028 The restart-checkpoint file '%ls' was corrupted and is being ignored. The RESTORE command will continue from the beginning as if RESTART had not been specified. 0 0
3031 Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement. 0 0
3032 One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options. 0 0
3033 BACKUP DATABASE cannot be used on a database opened in emergency mode. 0 0
3034 No No files were selected to be processed. You may have selected one or more filegroups that have no members. 0 0
3035 Cannot perform a differential backup for database "%ls", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. 0 0
3036 The database "%ls" is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire restore sequence is completed. 0 0
3038 The file name "%ls" is invalid as a backup device name. Reissue the BACKUP statement with a valid file name. 0 0
3039 Cannot perform a differential backup for file '%ls' because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option. 0 0
3040 An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected. 0 0
3041 BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages. 0 0
3042 BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the errors that were encountered. 0 0
3043 BACKUP '%ls' detected an error on page (%d:%d) in file '%ls'. 0 0
3044 Invalid zero-length device name. Reissue the BACKUP statement with a valid device name. 0 0
3045 BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path "%.*ls" is not usable. 0 0
3046 Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option. 0 0
3047 The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files are stored when full path names are not provided. This path is also used to locate restart checkpoint files for RESTORE. 0 0
3049 BACKUP detected corruption in the database log. Check the errorlog for more information. 0 0
3050 SQL Server could not send the differential information for database file '%ls' of database '%ls\\%ls' to the backup application because the differential information is too large to fit in memory, and an attempt to use a temporary file has failed. 0 0
3051 BACKUP LOG was unable to maintain mirroring consistency for database '%ls'. Database mirroring has been suspended. 0 0
3054 Differential file backups can include only read-only data for databases using the simple recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS. 0 0
3055 Backup destination "%.*ls" supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement with a valid backup destination. 0 0
3056 The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file '%ls'. 0 0
3057 Invalid device name. The length of the device name provided exceeds supported limit (maximum length is:%d). Reissue the BACKUP statement with a valid device name. 0 0
3058 File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls. 0 0
3098 The backup cannot be performed because '%ls' was requested after the media was formatted with an incompatible structure. To append to this media set, either omit '%ls' or specify '%ls'. Alternatively, you can create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten. 0 0
3101 Exclusive access could not be obtained because the database is in use. 0 0
3102 %ls cannot process database '%ls' because it is in use by this session. It is recommended that the master database be used when performing this operation. 0 0
3103 A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTORE statement and provide a backup set which includes a full copy of at least the primary data file. The WITH PARTIAL clause of the RESTORE statement may not be used for any other purpose. 0 0
3104 RESTORE cannot operate on database '%ls' because it is configured for database mirroring. Use ALTER DATABASE to remove mirroring if you intend to restore the database. 0 0
3105 RESTORE cannot restore any more pages into file '%ls' because the maximum number of pages (%d) are already being restored. Either complete the restore sequence for the existing pages, or use RESTORE FILE to restore all pages in the file. 0 0
3106 The filegroup "%ls" is ambiguous. The identity in the backup set does not match the filegroup that is currently defined in the online database. To force the use of the filegroup in the backup set, take the database offline and then reissue the RESTORE command. 0 0
3107 The file "%ls" is ambiguous. The identity in the backup set does not match the file that is currently defined in the online database. To force the use of the file in the backup set, take the database offline and then reissue the RESTORE command. 0 0
3108 To restore the master database, the server must be running in single-user mode. For information on starting in single-user mode, see "How to: Start an Instance of SQL Server (sqlservr.exe)" in Books Online. 0 0
3109 Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not supported. 0 0
3110 User does not have permission to RESTORE database '%.*ls'. 0 0
3111 Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored. 0 0
3112 Cannot restore any database other than master when the server is in single user mode. 0 0
3113 Invalid data was detected. 0 0
3115 The database is using the simple recovery model. It is not possible to restore a subset of the read-write data. 0 0
3116 The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore. 0 0
3117 The log or differential backup cannot be restored because no files are ready to rollforward. 0 0
3118 The database "%ls" does not exist. RESTORE can only create a database when restoring either a full backup or a file backup of the primary file. 0 0
3119 Problems were identified while planning for the RESTORE statement. Previous messages provide details. 0 0
3120 This backup set will not be restored because all data has already been restored to a point beyond the time covered by this backup set. 0 0
3121 The file "%ls" is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue. 0 0
3122 File initialization failed. RESTORE cannot continue. 0 0
3123 Invalid database name '%.*ls' specified for backup or restore operation. 0 0
3125 The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the database. Restoring more data is required before recovery is possible. Either restore a full file backup taken since the data was marked read-only, or restore the most recent base backup for the target data followed by a differential file backup. 0 0
3127 The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is using the simple recovery model and the file is marked for read-write access. Therefore, only read-only files can be recovered by piecemeal restore. 0 0
3128 File '%ls' has an unsupported page size (%d). 0 0
3129 The contents of the file "%ls" are not consistent with a transition into the restore sequence. A restore from a backup set may be required. 0 0
3130 The filegroup "%ls" is selected. At the time of backup it was known by the name "%ls"'. RESTORE will continue operating upon the renamed filegroup. 0 0
3131 The file "%ls" is selected. At the time of backup it was known by the name "%ls". RESTORE will continue operating upon the renamed file. 0 0
3132 The media set has %d media families but only %d are provided. All members must be provided. 0 0
3133 The volume on device "%ls" is sequence number %d of media family %d, but sequence number %d of media family %d is expected. Check that the device specifications and loaded media are correct. 0 0
3134 The differential base attribute for file '%ls' of database '%ls' has been reset because the file has been restored from a backup taken on a conflicting recovery path. The restore was allowed because the file was read-only and was consistent with the current status of the database. Any future differential backup of this file will require a new differential base. 0 0
3135 The backup set in file '%ls' was created by %hs and cannot be used for this restore operation. 0 0
3136 This differential backup cannot be restored because the database has not been restored to the correct earlier state. 0 0
3137 Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files. 0 0
3138 The database cannot be reverted because FILESTREAM BLOBs are present. 0 0
3139 Restore to snapshot is not allowed with the master database. 0 0
3140 Could not adjust the space allocation for file '%ls'. 0 0
3141 The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database. 0 0
3142 File "%ls" cannot be restored over the existing "%ls". Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location. 0 0
3143 The data set on device '%ls' is not a SQL Server backup set. 0 0
3144 File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set. 0 0
3145 The STOPAT option is not supported for databases that use the SIMPLE recovery model. 0 0
3147 Backup and restore operations are not allowed on database tempdb. 0 0
3148 This RESTORE statement is invalid in the current context. The 'Recover Data Only' option is only defined for secondary filegroups when the database is in an online state. When the database is in an offline state filegroups cannot be specified. 0 0
3149 The file or filegroup "%ls" is not in a valid state for the "Recover Data Only" option to be used. Only secondary files in the OFFLINE or RECOVERY_PENDING state can be processed. 0 0
3150 The master database has been successfully restored. Shutting down SQL Server. 0 0
3151 Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online. 0 0
3153 The database is already fully recovered. 0 0
3154 The backup set holds a backup of a database other than the existing '%ls' database. 0 0
3155 The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created. 0 0
3156 File '%ls' cannot be restored to '%ls'. Use WITH MOVE to identify a valid location for the file. 0 0
3159 The tail of the log for the database "%ls" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log. 0 0
3161 The primary file is unavailable. It must be restored or otherwise made available. 0 0
3163 The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted. 0 0
3165 Database '%ls' was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online. 0 0
3166 RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement. 0 0
3167 RESTORE could not start database '%ls'. 0 0
3168 The backup of the system database on the device %ls cannot be restored because it was created by a different version of the server (%ls) than this server (%ls). 0 0
3169 The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. 0 0
3170 The STANDBY filename is invalid. 0 0
3171 File %ls is defunct and cannot be restored into the online database. 0 0
3172 Filegroup %ls is defunct and cannot be restored into the online database. 0 0
3173 The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed up to reach the target point in time. The tail of the log for the database "%ls" has not been backed up. Use BACKUP LOG WITH NORECOVERY to back up the log, or use the WITH REPLACE clause in your RESTORE statement to overwrite the tail of the log. 0 0
3174 The file '%ls' cannot be moved by this RESTORE operation. 0 0
3175 RESTORE FILEGROUP="%ls" was specified, but not all of its files are present in the backup set. File "%ls" is missing. RESTORE will continue, but if you want all files to be restored, you must restore other backup sets. 0 0
3176 File '%ls' is claimed by '%ls'(%d) and '%ls'(%d). The WITH MOVE clause can be used to relocate one or more files. 0 0
3178 File %ls is not in the correct state to have this differential backup applied to it. 0 0
3179 The system database cannot be moved by RESTORE. 0 0
3180 This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY. 0 0
3181 Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details. 0 0
3182 The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR. 0 0
3183 RESTORE detected an error on page (%d:%d) in database "%ls" as read from the backup set. 0 0
3184 RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible. 0 0
3185 RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage. 0 0
3186 The backup set has been damaged. RESTORE will not attempt to apply this backup set. 0 0
3187 RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information. 0 0
3188 The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR. 0 0
3189 Damage to the backup set was detected. 0 0
3190 Filegroup '%ls' cannot be restored because it does not exist in the backup set. 0 0
3191 Restore cannot continue because file '%ls' cannot be written. Ensure that all files in the database are writable. 0 0
3192 Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that is unavailable. Either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup. 0 0
3194 Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored. 0 0
3195 Page %S_PGID cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first log or differential backup taken since the file was added to the database. 0 0
3196 RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file. 0 0
3197 I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup. 0 0
3198 I/O was resumed on database %ls. No user action is required. 0 0
3199 RESTORE requires MAXTRANSFERSIZE=%u but %u was specified. 0 0
3201 Cannot open backup device '%ls'. Operating system error %ls. 0 0
3202 Write on "%ls" failed: %ls 0 0
3203 Read on "%ls" failed: %ls 0 0
3204 The backup or restore was aborted. 0 0
3205 Too many backup devices specified for backup or restore; only %d are allowed. 0 0
3206 Backup device '%.*ls' does not exist. To view existing backup devices, use the sys.backup_devices catalog view. To create a new backup device use either sp_addumpdevice or SQL Server Management Studio. 0 0
3207 Backup or restore requires at least one backup device. Rerun your statement specifying a backup device. 0 0
3208 Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error log for more details. 0 0
3209 Operation is not supported on user instances. 0 0
3210 The mirror member in drive "%ls" is inconsistent with the mirror member in drive "%ls". 0 0
3211 %d percent processed. 0 0
3212 The mirror device "%ls" and the mirror device "%ls" have different device specifications. 0 0
3213 Unable to unload one or more tapes. See the error log for details. 0 0
3214 Too many backup mirrors are specified. Only %d are allowed. 0 0
3215 Use WITH FORMAT to create a new mirrored backup set. 0 0
3216 RESTORE REWINDONLY is only applicable to tape devices. 0 0
3217 Invalid value specified for %ls parameter. 0 0
3218 Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions. 0 0
3219 The file or filegroup "%.*ls" cannot be selected for this operation. 0 0
3221 The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d. 0 0
3222 The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d. 0 0
3224 Cannot create worker thread. 0 0
3227 The backup media on "%ls" is part of media family %d which has already been processed on "%ls". Ensure that backup devices are correctly specified. For tape devices, ensure that the correct volumes are loaded. 0 0
3229 Request for device '%ls' timed out. 0 0
3230 Operation on device '%ls' exceeded retry count. 0 0
3231 The media loaded on "%ls" is formatted to support %d media families, but %d media families are expected according to the backup device specification. 0 0
3232 The volume mounted on "%ls" does not have the expected backup set identity. The volume may be obsolete due to a more recent overwrite of this media family. In that case, locate the correct volume with sequence number %d of media family %d. 0 0
3234 Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names. 0 0
3235 The file "%.*ls" is not part of database "%ls". You can only list files that are members of this database. 0 0
3239 The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server. 0 0
3240 Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set. 0 0
3241 The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family. 0 0
3242 The file on device '%ls' is not a valid Microsoft Tape Format backup set. 0 0
3243 The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d. 0 0
3244 Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation. 0 0
3245 Could not convert a string to or from Unicode, %ls. 0 0
3246 The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media. 0 0
3247 The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d. 0 0
3249 The volume on device '%ls' is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set. 0 0
3250 The value '%d' is not within range for the %ls parameter. 0 0
3251 The media family on device '%ls' is complete. The device is now being reused for one of the remaining families. 0 0
3253 The block size parameter must supply a value that is a power of 2. 0 0
3254 The volume on device '%ls' is empty. 0 0
3255 The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server. 0 0
3256 The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally. 0 0
3257 There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64u bytes are available. 0 0
3258 The volume on the device "%ls" is not part of the media set that is currently being processed. Ensure that the backup devices are loaded with the correct media. 0 0
3260 An internal buffer has become full. 0 0
3261 SQL Server cannot use the virtual device configuration. 0 0
3262 The backup set on file %d is valid. 0 0
3263 Cannot use the volume on device '%ls' as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, or sequence number %d of family %d for the current set. 0 0
3264 The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier. 0 0
3265 The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. 0 0
3266 The backup data at the end of "%ls" is incorrectly formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on the media, use RESTORE HEADERONLY. To determine the usability of the backup sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reformat the media using BACKUP WITH FORMAT, which destroys all the backup sets. 0 0
3267 Insufficient resources to create UMS scheduler. 0 0
3268 Cannot use the backup file '%ls' because it was originally formatted with sector size %d and is now on a device with sector size %d. 0 0
3269 Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d. 0 0
3270 An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance. 0 0
3271 A nonrecoverable I/O error occurred on file "%ls:" %ls. 0 0
3272 The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement using a compatible block size. 0 0
3276 WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT. 0 0
3277 WITH SNAPSHOT must be used with only one virtual device. 0 0
3278 Failed to encrypt string %ls 0 0
3279 Access is denied due to a password failure 0 0
3280 Backups on raw devices are not supported. '%ls' is a raw device. 0 0
3281 Released and initiated rewind on '%ls'. 0 0
3283 The file "%ls" failed to initialize correctly. Examine the error logs for more details. 0 0
3284 Filemark on device '%ls' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: '%d' looks like a possible value. 0 0
3301 The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database. 0 0
3302 Redoing of logged operations in database '%.*ls' failed to reach end of log at log record ID %S_LSN. This indicates corruption around log record ID %S_LSN. Restore the database from a full backup, or repair the database. 0 0
3313 During redoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database. 0 0
3314 During undoing of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database. 0 0
3315 During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database '%.*ls' under transaction %S_XID. Restore a backup of the database, or repair the database. 0 0
3316 During undo of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a full backup, or repair the database. 0 0
3401 Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery. 0 0
3402 The database '%ls' is marked %ls and is in a state that does not allow recovery to be run. 0 0
3403 Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required. 0 0
3404 Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key. 0 0
3406 %d transactions rolled forward in database '%.*ls' (%d). This is an informational message only. No user action is required. 0 0
3407 %d transactions rolled back in database '%.*ls' (%d). This is an informational message only. No user action is required. 0 0
3408 Recovery is complete. This is an informational message only. No user action is required. 0 0
3409 Performance counter shared memory setup failed with error %d. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions. 0 0
3410 Data in filegroup %s is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup if you never intend to recover it. Log truncation cannot occur until this condition is resolved. 0 0
3411 Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall. 0 0
3412 Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server. 0 0
3413 Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems. 0 0
3414 An error occurred during recovery, preventing the database '%.*ls' (database ID %d) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support. 0 0
3415 Database '%.*ls' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery. 0 0
3416 The server contains read-only files that must be made writable before the server can be recollated. 0 0
3417 Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online. 0 0
3418 Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain. 0 0
3419 Recovery for database '%.*ls' is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence. 0 0
3420 Database snapshot '%ls' has failed an IO operation and is marked suspect. It must be dropped and recreated. 0 0
3421 Recovery completed for database %ls (database ID %d) in %I64d second(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms.) This is an informational message only. No user action is required. 0 0
3422 Database %ls was shutdown due to error %d in routine '%hs'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted. 0 0
3429 Recovery could not determine the outcome of a cross-database transaction %S_XID, named '%.*ls', in database '%.*ls' (database ID %d). The coordinating database (database ID %d) was unavailable. The transaction was assumed to be committed. If the transaction was not committed, you can retry recovery when the coordinating database is available. 0 0
3431 Could not recover database '%.*ls' (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS DTC, restore from a full backup, or repair the database. 0 0
3434 Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation. 0 0
3437 An error occurred while recovering database '%.*ls'. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again. 0 0
3441 During startup of warm standby database '%.*ls' (database ID %d), its standby file ('%ls') was inaccessible to the RESTORE statement. The operating system error was '%ls'. Diagnose the operating system error, correct the problem, and retry startup. 0 0
3442 Recovery of warm standby database '%.*ls' (database ID %d) failed. There is insufficient room in the undo file. Increase the size of the undo file and retry recovery. 0 0
3443 Database '%.*ls' (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup. 0 0
3445 File '%ls' is not a valid undo file for database '%.*ls (database ID %d). Verify the file path, and specify the correct file. 0 0
3446 Primary log file is not available for database '%.*ls'. The log cannot be backed up. 0 0
3447 Could not activate or scan all of the log files for database '%.*ls'. 0 0
3448 Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. Restore or repair the database. 0 0
3449 SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database. 0 0
3450 Recovery of database '%.*ls' (%d) is %d%% complete (approximately %d seconds remain). Phase %d of 3. This is an informational message only. No user action is required. 0 0
3452 Recovery of database '%.*ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls'). 0 0
3453 This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible. 0 0
3454 Recovery is writing a checkpoint in database '%.*ls' (%d). This is an informational message only. No user action is required. 0 0
3456 Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the database. 0 0
3457 Transactional file system resource manager '%.*ls' failed to recover. For more information, see the accompanying error message, which determines the appropriate user action. 0 0
3458 Recovery cannot scan database "%.*ls" for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up. 0 0
3505 Only the owner of database "%.*ls" or someone with relevant permissions can run the CHECKPOINT statement. 0 0
3604 Duplicate key was ignored. 0 0
3606 Arithmetic overflow occurred. 0 0
3607 Division by zero occurred. 0 0
3608 Cannot allocate a GUID for the token. 0 0
3609 The transaction ended in the trigger. The batch has been aborted. 0 0
3612 %hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms. 0 0
3613 SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms. 0 0
3615 Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob read-ahead reads %d. 0 0
3616 An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back. 0 0
3619 Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files. 0 0
3620 Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. Automatic checkpointing will be enabled when the database owner successfully checkpoints the database. Contact the database owner to either truncate the log file or add more disk space to the log. Then retry the CHECKPOINT statement. 0 0
3621 The statement has been terminated. 0 0
3622 Warning: An invalid floating point operation occurred. 0 0
3623 An invalid floating point operation occurred. 0 0
3624 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 0 0
3625 '%hs' is not yet implemented. 0 0
3627 New parallel operation cannot be started due to too many parallel operations executing at this time. Use the "max worker threads" configuration option to increase the number of allowable threads, or reduce the number of parallel operations running on the system. 0 0
3628 The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator. 0 0
3633 The operating system returned the error '%ls' while attempting '%ls' on '%ls' at '%hs'(%d). 0 0
3634 The operating system returned the error '%ls' while attempting '%ls' on '%ls'. 0 0
3635 An error occurred while processing '%ls' metadata for database id %d, file id %d, and transaction='%.*ls'. Additional Context='%ls'. Location='%hs'(%d). Retry the operation; if the problem persists, contact the database administrator to review locking and memory configurations. Review the application for possible deadlock conflicts. 0 0
3636 An error occurred while processing '%ls' metadata for database id %d file id %d. 0 0
3637 A parallel operation cannot be started from a DAC connection. 0 0
3638 SQL text cache memory usage: %d pages. This is an informational message only; no user action is required. 0 0
3701 Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission. 0 0
3702 Cannot drop database "%.*ls" because it is currently in use. 0 0
3703 Cannot detach the %S_MSG '%.*ls' because it is currently in use. 0 0
3705 Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls. 0 0
3706 Cannot %S_MSG a database snapshot. 0 0
3707 Cannot detach a suspect or recovery pending database. It must be repaired or dropped. 0 0
3708 Cannot %S_MSG the %S_MSG '%.*ls' because it is a system %S_MSG. 0 0
3709 Cannot %S_MSG the database while the database snapshot "%.*ls" refers to it. Drop that database first. 0 0
3710 Cannot detach an opened database when the server is in minimally configured mode. 0 0
3716 The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG. 0 0
3717 Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default. 0 0
3721 Type '%.*ls' cannot be renamed because it is being referenced by object '%.*ls'. 0 0
3723 An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement. 0 0
3724 Cannot %S_MSG the %S_MSG '%.*ls' because it is being used for replication. 0 0
3725 The constraint '%.*ls' is being referenced by table '%.*ls', foreign key constraint '%.*ls'. 0 0
3726 Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint. 0 0
3727 Could not drop constraint. See previous errors. 0 0
3728 '%.*ls' is not a constraint. 0 0
3729 Cannot %ls '%.*ls' because it is being referenced by object '%.*ls'. 0 0
3730 Cannot drop the default constraint '%.*ls' while it is being used by a foreign key as SET DEFAULT referential action. 0 0
3732 Cannot drop type '%.*ls' because it is being referenced by object '%.*ls'. There may be other objects that reference this type. 0 0
3733 Constraint '%.*ls' does not belong to table '%.*ls'. 0 0
3734 Could not drop the primary key constraint '%.*ls' because the table has an XML or spatial index. 0 0
3735 The primary key constraint '%.*ls' on table '%.*ls' cannot be dropped because change tracking is enabled on the table. Change tracking requires a primary key constraint on the table. Disable change tracking before dropping the constraint. 0 0
3737 Could not delete file '%ls'. See the SQL Server error log for more information. 0 0
3738 Deleting database file '%ls'. 0 0
3739 Cannot %ls the index '%.*ls' because it is not a statistics collection. 0 0
3740 Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup. 0 0
3741 Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on an offline filegroup. 0 0
3743 The database '%.*ls' is enabled for database mirroring. Database mirroring must be removed before you drop the database. 0 0
3744 Only a single clause is allowed in a statement where an index is dropped online. 0 0
3745 Only a clustered index can be dropped online. 0 0
3746 Cannot drop the clustered index of view '%.*ls' because the view is being used for replication. 0 0
3747 Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index '%.*ls' is created on view '%.*ls'. 0 0
3748 Cannot drop non-clustered index '%.*ls' using drop clustered index clause. 0 0
3749 Cannot drop XML Index '%.*ls' using old 'Table.Index' syntax, use 'Index ON Table' syntax instead. 0 0
3750 Warning: Index '%.*ls' on %S_MSG '%.*ls' was disabled as a result of disabling the clustered index on the %S_MSG. 0 0
3751 Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with '%.*ls' because '%.*ls' is a %S_MSG. Use %ls. 0 0
3801 Warning: The index "%.*ls" on "%.*ls"."%.*ls" may be impacted by the collation upgrade. Run DBCC CHECKTABLE. 0 0
3802 Warning: The constraint "%.*ls" on "%.*ls"."%.*ls" may be impacted by the collation upgrade. Disable and enable WITH CHECK. 0 0
3803 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the implementation of the checksum function has changed. 0 0
3804 Warning: The check constraint "%.*ls" on table "%.*ls"."%.*ls" is disabled because the implementation of the checksum function has changed. 0 0
3805 Warning: Index "%.*ls" on table "%.*ls"."%.*ls" might be corrupted because it references computed column "%.*ls" containing a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify index. Consider using explicit CONVERT with deterministic date style such as 121. Computed column indexes referencing non-deterministic expressions can't be created in 90 compatibility mode. See Books Online topic "Creating Indexes on Computed Columns" for more information. 0 0
3806 Warning: Indexed view "%.*ls"."%.*ls" might be corrupted because it contains a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify view. Consider using explicit CONVERT with deterministic date style such as 121. Indexed views referencing non-deterministic expressions can't be created in 90 compatibility mode. See Books Online topic "Creating Indexed Views" for more information. 0 0
3807 Create failed because all available identifiers have been exhausted. 0 0
3808 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the index is defined on a view with ignore_dup_key index option. Drop the index and, if possible, recreate it without ignore_dup_key option. You may need to change the logical structure of the view to ensure all rows are unique. 0 0
3809 Upgrade of database "%.*ls" failed because index "%.*ls" on object ID %d has the same name as that of another index on the same table. 0 0
3810 Event notification "%.*ls" on assembly is dropped. 0 0
3811 Event notification "%.*ls" on service queue is dropped as broker instance is not specified. 0 0
3812 Event notification "%.*ls" on object is dropped. 0 0
3813 Upgrade of login '%.*ls' failed because its name or sid is a duplicate of another login or server role. 0 0
3814 Local login mapped to remote login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the remote login before upgrade. 0 0
3815 Local login mapped to linked login '%.*ls' on server '%.*ls' is invalid. Drop and recreate the linked login before upgrade. 0 0
3816 Upgrade of login '%.*ls' failed because its password hash is invalid. Update the login password before upgrade. 0 0
3817 Warning: The index "%.*ls" on "%.*ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed. 0 0
3818 CUID column of 6 bytes cannot be added to index "%.*ls" on object %.*ls because row length would exceed the maximum permissible length of %d bytes. 0 0
3819 Warning: The check constraint "%.*ls" on "%.*ls"."%.*ls" was disabled and set as not trusted because the implementation of geometry and geography methods have changed. 0 0
3820 Warning: CUID column of 6 bytes has been added to index "%.*ls" on object %.*ls, but its maximum row size exceeds the allowed maximum of %d bytes. INSERT or UPDATE to this index will fail for some combination of large values. 0 0
3821 Warning: The foreign key constraint "%.*ls" on "%.*ls"."%.*ls" was disabled because the implementation of geometry and geography methods have changed. 0 0
3822 Warning: The heap "%.*ls"."%.*ls" has persisted computed columns that depends on a geometry or geography methods and may contain out-of-date information. Because of this, DBCC may report inconsistencies on this table. The persisted computed columns depending on geometry or geography methods should be unpersisted and persisted again to refresh the data. 0 0
3823 Warning: The object "%.*ls"."%.*ls" could not be bound and was ignored during upgrade. Consider reviewing and correcting its definition. 0 0
3851 An invalid row (%ls) was found in the system table sys.%ls%ls. 0 0
3852 Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls. 0 0
3853 Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls. 0 0
3854 Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (%ls) in sys.%ls%ls that is invalid. 0 0
3855 Attribute (%ls) exists without a row (%ls) in sys.%ls%ls. 0 0
3856 Attribute (%ls) exists but should not for row (%ls) in sys.%ls%ls. 0 0
3857 The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls. 0 0
3858 The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid value. 0 0
3859 Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE. 0 0
3860 Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use. 0 0
3862 CLR type '%.*ls'.'%.*ls' is disabled because the on disk format for this CLR type has been changed. Use DROP TYPE to remove this disabled type. 0 0
3864 Could not find an entry for index with ID %d on object with ID %d in database with ID %d. Possible schema corruption. Run DBCC CHECKDB. 0 0
3901 The transaction name must be specified when it is used with the mark option. 0 0
3902 The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION. 0 0
3903 The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. 0 0
3904 Cannot unsplit logical page %S_PGID in object '%.*ls', in database '%.*ls'. Both pages together contain more data than will fit on one page. 0 0
3906 Failed to update database "%.*ls" because the database is read-only. 0 0
3908 Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in bypass recovery mode. 0 0
3909 Session binding token is invalid. 0 0
3910 Transaction context in use by another session. 0 0
3912 Cannot bind using an XP token while the server is not in an XP call. 0 0
3913 TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server. 0 0
3914 The data type "%s" is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max). 0 0
3915 Cannot use the ROLLBACK statement within an INSERT-EXEC statement. 0 0
3916 Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first. 0 0
3917 Session is bound to a transaction context that is in use. Other statements in the batch were ignored. 0 0
3918 The statement or function must be executed in the context of a user transaction. 0 0
3919 Cannot enlist in the transaction because the transaction has already been committed or rolled back. 0 0
3920 The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored. 0 0
3921 Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started 0 0
3922 Cannot enlist in the transaction because the transaction does not exist. 0 0
3923 Cannot use transaction marks on database '%.*ls' with bulk-logged operations that have not been backed up. The mark is ignored. 0 0
3924 The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction. 0 0
3925 Invalid transaction mark name. The 'LSN:' prefix is reserved. 0 0
3926 The transaction active in this session has been committed or aborted by another session. 0 0
3927 The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction. 0 0
3928 The marked transaction "%.*ls" failed. A timeout occurred while attempting to place a mark in the log by committing the marked transaction. This can be caused by contention with Microsoft Distributed Transaction Coordinator (MS DTC) transactions or other local marked transaction that have prepared, but not committed or aborted. Try the operation again and if the error persists, determine the source of the contention. 0 0
3929 No No distributed or bound transaction is allowed in single user database. 0 0
3930 The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. 0 0
3931 The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction. 0 0
3932 The save point name "%.*ls" that was provided is too long. The maximum allowed length is %d characters. 0 0
3933 Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction. 0 0
3934 The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTION_CONTEXT. 0 0
3935 A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x. 0 0
3936 The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. '%.*ls' was one of the one or more files involved. ErorrCode: 0x%x 0 0
3937 While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver. Error code: 0x%0x. 0 0
3938 The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction. The transaction will be rolled back. 0 0
3939 An uncommittable transaction was detected at the beginning of the batch. The transaction was rolled back. This was caused by an error that occurred during the processing of a FILESTREAM request in the context of this transaction. 0 0
3950 Version store scan timed out when attempting to read the next row. Please try the statement again later when the system is not as busy. 0 0
3951 Transaction failed in database '%.*ls' because the statement was run under snapshot isolation but the transaction did not start in snapshot isolation. You cannot change the isolation level of the transaction to snapshot after the transaction has started unless the transaction was originally started under snapshot isolation level. 0 0
3952 Snapshot isolation transaction failed accessing database '%.*ls' because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation. 0 0
3953 Snapshot isolation transaction failed in database '%.*ls' because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered. 0 0
3954 Snapshot isolation transaction failed to start in database '%.*ls' because the ALTER DATABASE command that disallows snapshot isolation had started before this transaction began. The database is in transition to OFF state. You will either need to change the isolation level of the transaction or re-enable the snapshot isolation in the database. 0 0
3955 Snapshot isolation transaction failed in database '%.*ls' because the recovery was skipped for this database. You must recover the database before you can run a transaction under snapshot isolation. 0 0
3956 Snapshot isolation transaction failed to start in database '%.*ls' because the ALTER DATABASE command which enables snapshot isolation for this database has not finished yet. The database is in transition to pending ON state. You must wait until the ALTER DATABASE Command completes successfully. 0 0
3957 Snapshot isolation transaction failed in database '%.*ls' because the database did not allow snapshot isolation when the current transaction started. It may help to retry the transaction. 0 0
3958 Transaction aborted when accessing versioned row in table '%.*ls' in database '%.*ls'. Requested versioned row was not found. Your tempdb is probably out of space. Please refer to BOL on how to configure tempdb for versioning. 0 0
3959 Version store is full. New version(s) could not be added. A transaction that needs to access the version store may be rolled back. Please refer to BOL on how to configure tempdb for versioning. 0 0
3960 Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table '%.*ls' directly or indirectly in database '%.*ls' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. 0 0
3961 Snapshot isolation transaction failed in database '%.*ls' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation. 0 0
3962 Bind to another transaction while executing SQL Server internal query is not supported. Check your logon trigger definition and remove any sp_bindsession usage if any. If this error is not happening during logon trigger execution, contact production support team. 0 0
3963 Transaction failed in database '%.*ls' because distributed transactions are not supported under snapshot isolation. 0 0
3964 Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not versioned, a metadata change can lead to inconsistency if mixed within snapshot isolation. 0 0
3965 The PROMOTE TRANSACTION request failed because there is no local transaction active. 0 0
3966 Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient space in tempdb. This transaction was marked as a victim earlier because it may need the row version(s) that have already been removed to make space in tempdb. Retry the transaction 0 0
3967 Insufficient space in tempdb to hold row versions. Need to shrink the version store to free up some space in tempdb. Transaction (id=%I64d xsn=%I64d spid=%d elapsed_time=%d) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning. 0 0
3968 Snapshot isolation or read committed snapshot is not available in database '%.*ls' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed. 0 0
3969 Distributed transaction is not supported while running SQL Server internal query. Check your logon trigger definition and remove any distributed transaction usage if any. If this error is not happening during logon trigger execution, contact production support team. 0 0
3970 This operation conflicts with another pending operation on this transaction. The operation failed. 0 0
3971 The server failed to resume the transaction. Desc:%I64x. 0 0
3972 Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d. 0 0
3973 The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed. 0 0
3974 The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed. 0 0
3975 The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted. 0 0
3976 The transaction name has the odd length %d. The batch has been aborted. 0 0
3977 The savepoint name cannot be NULL. The batch has been aborted. 0 0
3978 Beginning a new transaction after rollback to save point is not allowed. 0 0
3979 The TM request is longer than expected. The request is not processed. 0 0
3980 The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy. 0 0
3981 The transaction operation cannot be performed because there are pending requests working on this transaction. 0 0
3982 New transaction is not allowed to be started while DTC or bound transaction is active. 0 0
3983 The operation failed because the session is not single threaded. 0 0
3984 Cannot acquire a database lock during a transaction change. 0 0
3985 An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory. 0 0
3986 The transaction timestamps ran out. Restart the server. 0 0
3987 SNAPSHOT ISOLATION is always enabled in this database. 0 0
3988 New transaction is not allowed because there are other threads running in the session. 0 0
3989 New request is not allowed to start because it should come with valid transaction descriptor. 0 0
3990 Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting. 0 0
3991 The context transaction which was active before entering user defined routine, trigger or aggregate "%.*ls" has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting. 0 0
3992 Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate "%.*ls". This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting. 0 0
3993 The user transaction that has been started in user defined routine, trigger or aggregate "%.*ls" is not ended upon exiting from it. This is not allowed and the transaction will be rolled back. Change application logic to enforce strict transaction nesting. 0 0
3994 User defined routine, trigger or aggregate tried to rollback a transaction that is not started in that CLR level. An exception will be thrown to prevent execution of rest of the user defined routine, trigger or aggregate. 0 0
3995 Unknown transaction isolation level %d, valid value range is 0 to 5. 0 0
3996 Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction. 0 0
3997 A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back. 0 0
3998 Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. 0 0
3999 Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information. 0 0
5001 User must be in the master database. 0 0
5002 Database '%.*ls' does not exist. Verify the name in sys.databases and try the operation again. 0 0
5003 Database mirroring cannot be enabled while the database has offline files. 0 0
5004 To use ALTER DATABASE, the database must be in a writable state in which a checkpoint can be executed. 0 0
5006 Could not get exclusive use of %S_MSG '%.*ls' to perform the requested operation. 0 0
5008 This ALTER DATABASE statement is not supported. Correct the syntax and execute the statement again. 0 0
5009 One or more files listed in the statement could not be found or could not be initialized. 0 0
5010 Log file name cannot be generated from a raw device. The log file name and path must be specified. 0 0
5011 User does not have permission to alter database '%.*ls', the database does not exist, or the database is not in a state that allows access checks. 0 0
5012 The name of the primary filegroup cannot be changed. 0 0
5013 The master and model databases cannot have files added to them. ALTER DATABASE was aborted. 0 0
5014 The %S_MSG '%.*ls' does not exist in database '%.*ls'. 0 0
5015 ALTER DATABASE failed. The total size specified must be 1 MB or greater. 0 0
5016 Cannot change the name of the system database %.*ls. 0 0
5018 The file "%.*ls" has been modified in the system catalog. The new path will be used the next time the database is started. 0 0
5019 Cannot find entry in sys.master_files for file '%.*ls'. 0 0
5020 The primary data or log file cannot be removed from a database. 0 0
5021 The %S_MSG name '%.*ls' has been set. 0 0
5022 Log file '%ls' for this database is already active. 0 0
5023 The database must be suspect or in emergency mode to rebuild the log. 0 0
5024 No No entry found for the primary log file in sysfiles1. Could not rebuild the log. 0 0
5025 The file '%ls' already exists. It should be renamed or deleted so that a new log file can be created. 0 0
5027 System databases master, model, and tempdb cannot have their logs rebuilt. 0 0
5028 The system could not activate enough of the database to rebuild the log. 0 0
5029 Warning: The log for database '%.*ls' has been rebuilt. Transactional consistency has been lost. The RESTORE chain was broken, and the server no longer has context on the previous log files, so you will need to know what they were. You should run DBCC CHECKDB to validate physical consistency. The database has been put in dbo-only mode. When you are ready to make the database available for use, you will need to reset database options and delete any extra log files. 0 0
5030 The database could not be exclusively locked to perform the operation. 0 0
5031 Cannot remove the file '%.*ls' because it is the only file in the DEFAULT filegroup. 0 0
5032 The file cannot be shrunk below page %ud until the log is backed up because it contains bulk logged pages. 0 0
5033 The maximum of %ld files per database has been exceeded. 0 0
5034 The file %ls is currently being autogrown or modified by another process. Try the operation again later. 0 0
5035 Filegroup '%.*ls' already exists in this database. Specify a different name or remove the conflicting filegroup if it is empty. 0 0
5036 MODIFY FILE failed. Specify logical name. 0 0
5038 MODIFY FILE failed for file "%.*ls". At least one property per file must be specified. 0 0
5039 MODIFY FILE failed. Specified size is less than or equal to current size. 0 0
5040 MODIFY FILE failed. Size is greater than MAXSIZE. 0 0
5041 MODIFY FILE failed. File '%.*ls' does not exist. 0 0
5042 The %S_MSG '%.*ls' cannot be removed because it is not empty. 0 0
5043 The %S_MSG '%.*ls' cannot be found in %ls. 0 0
5044 The %S_MSG '%.*ls' has been removed. 0 0
5045 The %S_MSG already has the '%ls' property set. 0 0
5046 The %S_MSG property '%ls' has been set. 0 0
5047 Cannot change the READONLY property of the PRIMARY filegroup. 0 0
5048 Cannot add, remove, or modify files in filegroup '%.*ls'. The filegroup is read-only. 0 0
5050 Cannot change the properties of empty filegroup '%.*ls'. The filegroup must contain at least one file. 0 0
5051 Cannot have a filegroup with the name 'DEFAULT'. 0 0
5052 %ls is not permitted while a database is in the %ls state. 0 0
5054 Could not cleanup worktable IAM chains to allow shrink or remove file operation. Please try again when tempdb is idle. 0 0
5055 Cannot add, remove, or modify file '%.*ls'. The file is read-only. 0 0
5056 Cannot add, remove, or modify a file in filegroup '%.*ls' because the filegroup is not online. 0 0
5057 Cannot add, remove, or modify file '%.*ls' because it is offline. 0 0
5058 Option '%.*ls' cannot be set in database '%.*ls'. 0 0
5059 Database '%.*ls' is in transition. Try the ALTER DATABASE statement later. 0 0
5060 Nonqualified transactions are being rolled back. Estimated rollback completion: %d%%. 0 0
5061 ALTER DATABASE failed because a lock could not be placed on database '%.*ls'. Try again later. 0 0
5062 The option "%.*ls" conflicts with another requested option. The options cannot both be requested at the same time. 0 0
5063 Database '%.*ls' is in warm standby. A warm-standby database is read-only. 0 0
5064 Changes to the state or options of database '%.*ls' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it. 0 0
5065 The file "%ls" is currently being scanned or used by a background or user process. Try the operation again later. 0 0
5066 Database options single user and dbo use only cannot be set at the same time. 0 0
5067 The database option TORN_PAGE_DETECTION is incompatible with the PAGE_CHECKSUM option. 0 0
5068 Failed to restart the current database. The current database is switched to master. 0 0
5069 ALTER DATABASE statement failed. 0 0
5070 Database state cannot be changed while other users are using the database '%.*ls' 0 0
5071 Rebuild log can only specify one file. 0 0
5072 ALTER DATABASE failed. The default collation of database '%.*ls' cannot be set to %.*ls. 0 0
5073 Cannot alter collation for database '%ls' because it is READONLY, OFFLINE, or marked SUSPECT. 0 0
5074 The %S_MSG '%.*ls' is dependent on %S_MSG '%.*ls'. 0 0
5075 The %S_MSG '%.*ls' is dependent on %S_MSG. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation. 0 0
5076 Warning: Changing default collation for database '%.*ls', which is used in replication. All replication databases should have the same default collation. 0 0
5077 Cannot change the state of non-data files or files in the primary filegroup. 0 0
5078 Cannot alter database options for "%ls" because it is READONLY, OFFLINE, or marked SUSPECT. 0 0
5079 Database "%.*ls" is %S_MSG for vardecimal storage format. 0 0
5080 Vardecimal storage format cannot be disabled for database "%.*ls" because the database is not under simple recovery model. Change the database recovery model to simple and then reissue the command. 0 0
5082 Cannot change the versioning state on database "%.*ls" together with another database state. 0 0
5083 The termination option is not supported when making versioning state changes. 0 0
5084 Setting database option %ls to %ls for database %.*ls. 0 0
5085 Alter database command failed because SQL Server was started with one or more undocumented trace flags that prevent enabling/disabling database for versioning. 0 0
5086 Cannot disable vardecimal storage format for database "%.*ls" because there are one or more tables that have vardecimal storage format enabled. Disable the vardecimal storage format on all tables before disabling the vardecimal storage format for the database. 0 0
5087 The file content type mismatches with the content type of the filegroup. 0 0
5088 Change tracking is already enabled for database '%.*ls'. 0 0
5089 Change tracking is disabled for database '%.*ls'. Change tracking must be enabled on a database to modify change tracking settings. 0 0
5090 Database '%.*ls' is a system database. Change tracking settings cannot be modified for system databases. 0 0
5091 ALTER DATABASE change tracking option '%ls' was specified more than once. Each option can be specified only once. 0 0
5092 The value for change tracking option '%ls' is not valid. The value must be between %d and %d minutes. 0 0
5093 The operation cannot be performed on a database snapshot. 0 0
5094 The operation cannot be performed on a database with database snapshots or active DBCC replicas. 0 0
5095 A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file "%ls" before attempting to transition to read-only. 0 0
5096 The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file "%ls" before attempting to transition to SIMPLE. 0 0
5097 The container cannot be set to the offline state because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE statement. 0 0
5098 The container can not be dropped because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE operation. 0 0
5099 ALTER DATABASE failed because the READ_COMMITTED_SNAPSHOT and the ALLOW_SNAPSHOT_ISOLATION options cannot be set to ON when a database has FILESTREAM filegroups. To set READ_COMMITTED_SNAPSHOT or ALLOW_SNAPSHOT_ISOLATION to ON, you must remove the FILESTREAM filegroups from the database. 0 0
5102 Attempted to open a filegroup for the invalid ID %d in database "%.*ls". 0 0
5103 MAXSIZE cannot be less than SIZE for file '%ls'. 0 0
5104 File '%.*ls' already used. 0 0
5105 A file activation error occurred. The physical file name '%.*ls' may be incorrect. Diagnose and correct additional errors, and retry the operation. 0 0
5108 Log file '%.*ls' does not match the primary file. It may be from a different database or the log may have been rebuilt previously. 0 0
5110 The file "%.*ls" is on a network path that is not supported for database files. 0 0
5111 File activation failure. The physical file name "%.*ls" may be incorrect. 0 0
5112 FCB::SetSize dbid %d fileid %d oldSize %d newSize %d. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF to turn off the trace flag. 0 0
5113 The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure. 0 0
5114 Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. "%.*ls" is not an eligible file for a database snapshot. 0 0
5115 Only SQL Server database files can be specified for database snapshots. '%.*ls' is not a SQL Server database file. 0 0
5118 The file "%ls" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed. 0 0
5119 Cannot make the file "%.*ls" a sparse file. Make sure the file system supports sparse files. 0 0
5120 Unable to open the physical file "%.*ls". Operating system error %d: "%ls". 0 0
5121 The path specified by "%.*ls" is not in a valid directory. 0 0
5123 CREATE FILE encountered operating system error %ls while attempting to open or create the physical file '%.*ls'. 0 0
5124 The file header in '%ls' does not match the expected contents for file '%ls' of database '%ls'. The mismatch is possibly between the full-text catalog files and the related database. Perform a restore if necessary. 0 0
5125 File '%ls' appears to have been truncated by the operating system. Expected size is %I64d KB but actual size is %I64d KB. 0 0
5127 All files must be specified for database snapshot creation. Missing the file "%ls". 0 0
5128 Write to sparse file '%ls' failed due to lack of disk space. 0 0
5129 The log cannot be rebuilt when the primary file is read-only. 0 0
5130 The log cannot be rebuilt when database mirroring is enabled. 0 0
5131 The log was not rebuilt because there is more than one log file. 0 0
5132 The path specified by '%.*ls' cannot be used for FILESTREAM files because it is a raw device. 0 0
5133 Directory lookup for the file "%ls" failed with the operating system error %ls. 0 0
5134 The path that is specified by '%.*ls' cannot be used for FILESTREAM files because it is not on a supported file system. 0 0
5135 The path '%.*ls' cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online. 0 0
5136 The path specified by '%.*ls' cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container. 0 0
5144 Autogrow of file '%.*ls' in database '%.*ls' was cancelled by user or timed out after %d milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size. 0 0
5145 Autogrow of file '%.*ls' in database '%.*ls' took %d milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file. 0 0
5149 MODIFY FILE encountered operating system error %ls while attempting to expand the physical file '%ls'. 0 0
5150 The size of a single log file must not be greater than 2 TB. 0 0
5159 Operating system error %.*ls on file "%.*ls" during %ls. 0 0
5161 An unexpected file id was encountered. File id %d was expected but %d was read from "%.*ls". Verify that files are mapped correctly in sys.master_files. ALTER DATABASE can be used to correct the mappings. 0 0
5169 FILEGROWTH cannot be greater than MAXSIZE for file '%.*ls'. 0 0
5170 Cannot create file '%ls' because it already exists. Change the file path or the file name, and retry the operation. 0 0
5171 %.*ls is not a primary database file. 0 0
5172 The header for file '%ls' is not a valid database file header. The %ls property is incorrect. 0 0
5173 One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup. 0 0
5174 Each file size must be greater than or equal to 512 KB. 0 0
5175 The file %.*ls has been expanded to allow recovery to succeed. After recovery completes, you can increase the size of the files in the database. Contact the system administrator for assistance. 0 0
5176 To allow recovery to succeed, the log file '%.*ls' has been expanded beyond its maximum size. After recovery completes, you should either increase the size of the log file in the database or schedule more frequent backups of the log (under the full or bulk-logged recovery model). 0 0
5177 An unexpected error occurred while checking the sector size for file '%.*ls'. Move the file to a local NTFS volume, where the sector size can be retrieved. Check the SQL Server error log for more information. 0 0
5178 Cannot use file '%.*ls' because it was originally formatted with sector size %d and is now on a volume with sector size %d. Move the file to a volume with a sector size that is the same as or smaller than the original sector size. 0 0
5179 Cannot use file '%.*ls', because it is on a volume with sector size %d. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 0 0
5180 Could not open File Control Bank (FCB) for invalid file ID %d in database '%.*ls'. Verify the file location. Execute DBCC CHECKDB. 0 0
5181 Could not restart database "%.*ls". Reverting to the previous status. 0 0
5182 New log file '%.*ls' was created. 0 0
5183 Cannot create the file "%ls". Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite an existing file. 0 0
5184 Cannot use file '%.*ls' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it. 0 0
5185 Cannot find the matching log file for FILESTRAM file '%.*ls'. 0 0
5186 Encountered an error (NT status code 0x%x) while attempting to start the Transactional File System Resource Manager '%.*ls'. 0 0
5188 Encountered error (NT status code 0x%x) while attempting to perform redo for transactional file system resource manager '%.*ls'. 0 0
5189 Encountered error (NT status code 0x%x) while attempting to perform undo for transactional file system resource manager '%.*ls'. 0 0
5190 Encountered error (NT status code 0x%x) while attempting to checkpoint transactional file system resource manager '%.*ls'. 0 0
5194 The size for FILESTREAM log file '%.*ls' must be greater than or equal to 1 MB. 0 0
5195 The Cluster Service function call '%s' failed with error code '%s' while verifying the file path. Verify that your failover cluster is configured properly. 0 0
5196 The file "%ls" has been uncompressed. 0 0
5197 Encountered an error (%ls) while attempting to uncompress the file "%ls". 0 0
5198 The path specified by "%.*ls" is a UNC path. UNC path is not supported in failover clustered environment. 0 0
5199 The path specified by "%.*ls" is a raw device. Raw device path is not supported in failover clustered environment. 0 0
5201 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because the file does not have enough free space to reclaim. 0 0
5202 DBCC SHRINKDATABASE for database ID %d is waiting for the snapshot transaction with timestamp %I64d and other snapshot transactions linked to timestamp %I64d or with timestamps older than %I64d to finish. 0 0
5203 DBCC SHRINKFILE for file ID %d is waiting for the snapshot transaction with timestamp %I64d and other snapshot transactions linked to timestamp %I64d or with timestamps older than %I64d to finish. 0 0
5204 Could not find allocation unit ID %I64d. Check sys.allocation_units. 0 0
5205 %.*ls: Moving page %d:%d failed. 0 0
5206 %.*ls: Page %d:%d could not be moved because it could not be read. 0 0
5207 %.*ls: Page %d:%d could not be moved because it is a work table page. 0 0
5208 %.*ls: Page %d:%d could not be moved because it is a work file page. 0 0
5209 %.*ls: Page %d:%d could not be moved because it is a dedicated allocation page. 0 0
5210 %.*ls: Page %d:%d could not be moved because it is an invalid page type. 0 0
5211 %.*ls: Page %d:%d could not be moved because it was deallocated during shrink. 0 0
5212 %.*ls: System table SYSFILES1 Page %d:%d could not be moved to other files because it only can reside in the primary file of the database. 0 0
5213 %.*ls: Page %d:%d could not be moved because its ownership was changed during shrink. 0 0
5214 %.*ls: Page %d:%d could not be moved because its page type was changed during shrink. 0 0
5215 %.*ls: Page %d:%d could not be moved because the partition to which it belonged was dropped. 0 0
5216 %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was dropped. 0 0
5217 %.*ls: Page %d:%d could not be moved because it is an empty non-leaf level index page. 0 0
5218 %.*ls: Heap page %d:%d could not be moved because the table name could not be found. 0 0
5219 %.*ls: Heap page %d:%d could not be moved. 0 0
5220 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved. 0 0
5221 %.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allocation unit could not be moved. 0 0
5222 %.*ls: Page %d:%d from a dropped allocation unit could not be deallocated. 0 0
5223 %.*ls: Empty page %d:%d could not be deallocated. 0 0
5224 %.*ls: Empty large object page %d:%d could not be deallocated. 0 0
5225 %.*ls: Not all ghost records on the large object page %d:%d could be removed. 0 0
5226 %.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallocated. 0 0
5227 %.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallocated. 0 0
5228 Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. DBCC detected incomplete cleanup from an online index build operation. (The anti-matter column value is %d.) 0 0
5229 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contains an anti-matter column, but is not a nonclustered index. 0 0
5230 The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB. 0 0
5231 Object ID %ld (object '%.*ls'): A deadlock occurred while trying to lock this object for checking. This object has been skipped and will not be processed. 0 0
5232 DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified. 0 0
5233 Table error: alloc unit ID %I64d, page %S_PGID. The test (%hs) failed. The values are %ld and %ld. 0 0
5234 DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because trying to adjust the space allocation for the file was failed. 0 0
5235 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds. 0 0
5236 Unable to process object '%ls' because it is a four-part name, which is not supported by any DBCC command. 0 0
5237 DBCC cross-rowset check failed for object '%.*ls' (object ID %d) due to an internal query error. 0 0
5238 Unable to process object ID %ld (object '%.*ls') because it is a stored procedure or user-defined function, which is not supported by any DBCC command. 0 0
5239 Unable to process object ID %ld (object '%.*ls') because this DBCC command does not support objects of this type. 0 0
5240 File ID %d of database ID %d cannot be shrunk as it is either being shrunk by another process or is empty. 0 0
5241 File ID %d of database ID %d cannot be shrunk as the target shrink size (%I64d KB) is greater than the actual file size (%I64d KB). 0 0
5242 An inconsistency was detected during an internal operation in database '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support. 0 0
5243 An inconsistency was detected during an internal operation. Please contact technical support. 0 0
5244 Repair statement not processed. One or more files in the database are read-only and must be made writeable in order to run repair. 0 0
5245 Object ID %ld (object '%.*ls'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed. 0 0
5246 Repair operations cannot be performed on the MSSQLSYSTEMRESOURCE database. Consult Books Online topic "Resource Database" for more information. 0 0
5247 Repair: insert a secondary index row based on its base table row. 0 0
5248 Repair: Successfully %ls row in index "%ls" in database "%ls". 0 0
5249 %.*ls: Page %d:%d could not be moved because shrink could not lock the page. 0 0
5250 Database error: %ls page %S_PGID for database '%.*ls' (database ID %d) is invalid. This error cannot be repaired. You must restore from backup. 0 0
5251 %.*ls: Heap page %d:%d could not be moved because maintaining NC indexes associated with the heap failed. 0 0
5252 File ID %d of database ID %d cannot be shrunk to the expected size. The high concurrent workload is leading to too many deadlocks during the shrink operation. Re-run the shrink operation when the workload is lower. 0 0
5253 The check statement was aborted. DBCC CHECKALLOC cannot be run on TEMPDB. 0 0
5254 %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was building the heap by another process. 0 0
5255 %.*ls: Page %d:%d could not be moved because it is a sort page. 0 0
5256 Table error: alloc unit ID %I64d, page %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID. 0 0
5257 %.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation. 0 0
5258 %.*ls: Heap page %d:%d could not be moved because building computed column expression failed. 0 0
5259 %.*ls: Heap page %d:%d could not be moved because populating computed column expression failed. 0 0
5260 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): At least one record on page %S_PGID contains versioning information, but the VERSION_INFO bit in the page header is not set. 0 0
5261 %.*ls: Page %d:%d could not be moved because it has not been formatted. 0 0
5262 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row contains a NULL versioning timestamp, but its version chain pointer is not NULL. Version chain points to page %S_PGID, slot %d. 0 0
5263 Found incorrect count(s) for table '%.*ls', index '%.*ls', partition %ld: 0 0
5264 DATA pages %.*ls: From system table - %I64d pages; Actual - %I64d pages. 0 0
5265 USED pages %.*ls: From system table - %I64d pages; Actual - %I64d pages. 0 0
5266 RSVD pages %.*ls: From system table - %I64d pages; Actual - %I64d pages. 0 0
5267 ROWS count: From system table - %I64d rows; Actual - %I64d rows. 0 0
5268 DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required. 0 0
5269 Check terminated. The transient database snapshot for database '%.*ls' (database ID %d) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details. 0 0
5270 %.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table. 0 0
5271 DBCC %ls could not output results for this command due to an internal failure. Review other errors for details. 0 0
5272 %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively. 0 0
5273 %.*ls: Page %d:%d could not be moved because it belonged to an index/heap that was/is in build online. 0 0
5274 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. %S_MSG is invalid for compressed page; the following internal test failed: %hs. Values are %ld and %ld. 0 0
5275 Exhaustive search of '%.*ls' (database ID %d) for inconsistencies completed. Processed %d of %d total searches. Elapsed time: %I64d milliseconds. This is an informational message only. No user action is required. 0 0
5276 Exhaustive search of '%.*ls' (database ID %d) for inconsistencies failed due to exception %d, state %d. This is an informational message only. No user action is required. 0 0
5277 Internal %lsdatabase snapshot has split point LSN = %08x:%08x:%04x and first LSN = %08x:%08x:%04x. This is an informational message only. No user action is required. 0 0
5301 Bulk load failed. User does not have ALTER TABLE permission on table '%.*ls'. ALTER TABLE permission is required on the target table of a bulk load if the target table contains triggers or check constraints, but the 'FIRE_TRIGGERS' or 'CHECK_CONSTRAINTS' bulk hints are not specified. ALTER TABLE permission is also required if the 'KEEPIDENTITY' bulk hint is specified. 0 0
5302 Mutator '%.*ls' on '%.*ls' cannot be called on a null value. 0 0
5303 The result of applying mutator '%.*ls' on CLR type '%.*ls' cannot be a null value. 0 0
5304 Bulk copy failed. User does not have ALTER TABLE permission on table '%.*ls'. ALTER TABLE permission is required on the target table of a bulk copy operation if the table has triggers or check constraints, but 'FIRE_TRIGGERS' or 'CHECK_CONSTRAINTS' bulk hints are not specified as options to the bulk copy command. 0 0
5305 The rowdump and lockres columns are only valid on tables and indexed views on which the NOEXPAND hint is specified. 0 0
5306 Cursor parameters are not allowed for functions. Variable '%.*ls' is of type cursor. 0 0
5307 Invalid parameter specified for sp_cursoropen. 0 0
5308 Windowed functions do not support integer indices as ORDER BY clause expressions. 0 0
5309 Windowed functions do not support constants as ORDER BY clause expressions. 0 0
5310 Aggregates are not allowed in the VALUES list of an INSERT statement. 0 0
5311 Invalid quote character '%lc'. A remote server or user command used an invalid quote character. 0 0
5312 The input to the function 'ntile' cannot be bound. 0 0
5313 Synonym '%.*ls' refers to an invalid object. 0 0
5315 The target of a MERGE statement cannot be a remote table, a remote view, or a view over remote tables. 0 0
5316 The target '%.*ls' of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the MERGE statement. In a MERGE statement, if any action has an enabled INSTEAD OF trigger on the target, then all actions must have enabled INSTEAD OF triggers. 0 0
5317 The target of a MERGE statement cannot be a partitioned view. 0 0
5318 In a MERGE statement, the source and target cannot have the same name or alias. Use different aliases for the source and target to ensure that they have unique names in the MERGE statement. 0 0
5319 Aggregates are not allowed in a WHEN clause of a MERGE statement. 0 0
5321 The '%ls' function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5322 An aggregate function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5323 Subqueries are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5324 In a MERGE statement, a '%S_MSG' clause with a search condition cannot appear after a '%S_MSG' clause with no search condition. 0 0
5325 The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset '%.*ls'. The order of the data must match the order specified in the ORDER hint for a BULK rowset. Update the ORDER hint to reflect the order in which the input data is ordered, or update the input data file to match the order specified by the ORDER hint. 0 0
5326 The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset '%.*ls'. The data in the data file must be unique if the UNIQUE hint is specified for a BULK rowset. Remove the UNIQUE hint, or update the input data file to ensure that the data is unique. 0 0
5327 The column '%.*ls' does not have a valid data type for the ORDER hint specified for data source '%.*ls'. The text, ntext, image, xml, varchar(max), nvarchar(max) and varbinary(max) data types cannot be used in the ORDER hint for a BULK rowset or CLR TVF. 0 0
5328 Cannot insert explicit value for the identity column '%.*ls' in the target table '%.*ls' of the INSERT statement when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5329 Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5330 Full-text predicates cannot appear in the OUTPUT clause. 0 0
5331 Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
5332 The order of the data in the stream does not conform to the ORDER hint specified for the CLR TVF '%.*ls'. The order of the data must match the order specified in the ORDER hint for a CLR TVF. Update the ORDER hint to reflect the order in which the input data is ordered, or update the CLR TVF to match the order specified by the ORDER hint. 0 0
5333 The identifier '%.*ls' cannot be bound. Only source columns are allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement. 0 0
5334 The identifier '%.*ls' cannot be bound. Only target columns are allowed in the 'WHEN NOT MATCHED BY SOURCE' clause of a MERGE statement. 0 0
5501 The FILESTREAM filegroup was dropped before the table can be created. 0 0
5502 The FILESTREAM container is inaccessible. 0 0
5503 Unable to find entry in sys.database_files for FILESTREAM file '%.*ls'. 0 0
5504 'PRIMARY' can only be specified for FILESTREAM log filegroup in a 'CONTAINS' clause. 0 0
5505 A table with FILESTREAM column(s) must have a non-NULL unique ROWGUID column. 0 0
5506 FILESTREAM data or log file cannot be named 'DEFAULT'. 0 0
5507 DEFAULT cannot be specified for FILESTREAM log filegroup '%.*ls'. 0 0
5508 FILESTREAM can only be declared for VARBINARY columns. 0 0
5509 The properties SIZE, MAXSIZE, or FILEGROWTH cannot be specified for the FILESTREAM data file '%.*ls'. 0 0
5510 LOG ON cannot be used for non-FILESTREAM file group '%.*ls'. 0 0
5511 FILESTREAM's file system log record '%.*ls' under log folder '%.*ls' is corrupted. 0 0
5512 Error 0x%x (%ls) was encountered while directory '%.*ls' was being truncated. 0 0
5513 The name that is specified for the associated log filegroup for FILESTREAM filegroup '%.*ls' is not valid. 0 0
5514 Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%.*ls' is not started. 0 0
5515 Cannot open the container directory '%.*ls' of the FILESTREAM file. The operating system has returned the Windows status code 0x%x. 0 0
5516 The FILESTREAM log filegroup '%.*ls' cannot be referred to by more than one FILESTREAM data filegroup. 0 0
5517 Too few or too many files specified for FILESTREAM(LOG) filegroup '%.*ls'. 0 0
5518 FILESTREAM path '%.*ls' is too long. 0 0
5519 A database must have primary FILESTREAM log filegroup and log file in order for it to contain other FILESTREAM filegroups. 0 0
5520 FILESTREAM file '%.*ls' cannot be added because its destination filegroup cannot have more than one file. 0 0
5521 Error 0x%x (NT status code) was encountered when SQL Server attempts to retrieve '%.*ls' from the Transaction File System Resource Manager located at '%.*ls'. 0 0
5522 FILESTREAM data file cannot be removed because its log file has not been backed up. 0 0
5523 FILESTREAM data file group cannot be added to refer to an empty FILESTREAM log file group. 0 0
5524 Default FILESTREAM data filegroup cannot be removed unless it's the last FILESTREAM data filegroup left. 0 0
5525 The READ_ONLY, READ_WRITE, and ONLINE/OFFLINE properties cannot be modified on a FILESTREAM log filegroup. 0 0
5526 The FILESTREAM log file '%.*ls' cannot be removed because it is being referenced by a FILESTREAM data filegroup. 0 0
5527 The primary FILESTREAM log file cannot be dropped because other FILESTREAM filegroups exist. 0 0
5528 A database can have at most one primary FILESTREAM log filegroup and log file. 0 0
5531 Error 0x%x (NT status code) was encountered when SQL Server attempts to change the logging mode of Transaction File System Resource Manager located at '%.*ls' from '%.*ls' to '%.*ls'. 0 0
5532 SQL Server cannot obtain the Kernel Transaction Manager's transaction context to perform file system operation. 0 0
5533 The FILESTREAM file system log record that has the LSN '%d:%d:%d' is missing. Log folder '%.*ls' is corrupted. Restore the database from a backup. 0 0
5534 SQL log record at LSN '%d:%d:%d' for database '%.*ls' is corrupted. Database cannot recover. 0 0
5535 FILESTREAM data container '%.*ls' is corrupted. Database cannot recover. 0 0
5536 FILESTREAM deleted folder '%.*ls' is corrupted. Database cannot recover. 0 0
5537 Function %ls is only valid on columns with the FILESTREAM attribute. 0 0
5538 Partial updates are not supported on columns that have a FILESTREAM as a source. 0 0
5539 The ROWGUIDCOL column associated with the FILESTREAM being used is not visible where method %ls is called. 0 0
5540 The FILESTREAM column cannot be used with method %ls because the associated ROWGUIDCOL of the base table is nullable or does not have a unique constraint. 0 0
5541 An open mode must be used when a FILESTREAM column is opened as a file. 0 0
5542 The FILESTREAM filegroup '%.*ls' has no files assigned to it. FILESTREAM data cannot be populated on this filegroup until a file is added. 0 0
5552 FILESTREAM file named with GUID '%.*ls' that belongs to FILESTREAM data file ID 0x%x does not exist or cannot be opened. 0 0
5553 SQL Server internal error. FILESTREAM manager cannot continue with current command. 0 0
5554 The total number of versions for a single file has reached the maximum limit set by the file system. 0 0
5555 The operation has failed because the FILESTREAM data cannot be renamed. 0 0
5570 FILESTREAM Failed to find the garbage collection table. 0 0
5571 Internal FILESTREAM error: failed to access the garbage collection table. 0 0
5572 Internal FILESTREAM error: failed to perform a filesystem operation because of a potential corruption. 0 0
5573 Internal FILESTREAM error: failed to access the tombstones table with HRESULT: 0x%x. 0 0
5574 A database cannot be enabled for both FILESTREAM storage and Database Mirroring. 0 0
5575 Operation '%ls' failed with HRESULT: %ls in file '%hs', line %d while executing sp_filestream_configure. 0 0
5578 A failure occurred while FILESTREAM configuration was being changed or applied. For more information, see the SQL Server error log. 0 0
5579 FILESTREAM: effective level = %d, configured level = %d, file system access share name = '%.*ls'. 0 0
5580 FILESTREAM InstanceGuid is null. Registry settings might be corrupted. 0 0
5581 FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have data in FILESTREAM columns, it will not be accessible after the SQL Server instance has been restarted. 0 0
5582 Machine reboot is required before the FILESTREAM feature settings can take effect. 0 0
5583 The specified value for the enable_level parameter of the sp_filestream_configure stored procedure is not valid. The value must be 0, 1, 2, or 3. 0 0
5584 Another session is executing the sp_filestream_configure stored procedure. Check the updated configuration settings and retry the operation if necessary. 0 0
5586 The FILESTREAM feature is already configured to the specified level. No change has been made. 0 0
5588 Access to FILESTREAM data is not supported under snapshot isolation level. 0 0
5589 Access to FILESTREAM data is not supported under row versioning-based read committed snapshot isolation (RCSI). 0 0
5590 FILESTREAM operations are not supported on the platform. 0 0
5591 FILESTREAM feature is disabled. 0 0
5592 FILESTREAM feature doesn't have file system access enabled. 0 0
5593 FILESTREAM feature is not supported on WoW64. The feature is disabled. 0 0
5594 The value specified for the computer_name_format parameter to the .PathName() function is not valid. 0 0
5595 .PhysicalPathName is disabled. 0 0
5596 FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration. 0 0
5597 FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration Manager before enabling through sp_configure. 0 0
5598 FILESTREAM feature is not supported on user instances. 0 0
5600 The Cross Database Chaining option cannot be set to the specified value on the specified database. 0 0
5601 The service master key could not be force regenerated as requested by the -F startup option. The error number is %ld. 0 0
5602 The service master key regeneration was successful. 0 0
5603 The password for SA could not be force regenerated as requested by the -K startup option. The error number is %ld. 0 0
5604 The password regeneration attempt for SA was successful. 0 0
5701 Changed database context to '%.*ls'. 0 0
5702 SQL Server is terminating this process. 0 0
5703 Changed language setting to %.*ls. 0 0
5803 Unknown configuration (id = %d) encountered in sys.configurations. 0 0
5804 Character set, sort order, or collation cannot be changed at the server level because at least one database is not writable. Make the database writable, and retry the operation. 0 0
5805 Too few locks specified. Minimum %d. 0 0
5807 Recovery intervals above %d minutes not recommended. Use the RECONFIGURE WITH OVERRIDE statement to force this configuration. 0 0
5808 Ad hoc update to system catalogs is not supported. 0 0
5810 Valid values for the fill factor are 0 to 100. 0 0
5812 You do not have permission to run the RECONFIGURE statement. 0 0
5828 User connections are limited to %d. 0 0
5829 The specified user options value is invalid. 0 0
5831 Minimum server memory value (%d) must be less than or equal to the maximum value (%d). 0 0
5832 The affinity mask specified does not match the CPU mask on this system. 0 0
5833 The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server. 0 0
5834 The affinity mask specified conflicts with the IO affinity mask specified. Use the override option to force this configuration. 0 0
5835 Failed to start CPUs with the mask 0x%lx on the system. 0 0
5836 Lightweight pooling is not supported on this platform or in this edition of SQL Server. 0 0
5837 The service broker listen port cannot be dynamic. Valid port values are 1024-32767. 0 0
5838 The service broker connection authentication value is invalid. 0 0
5839 The service broker message forward store size cannot be set to 0. 0 0
5840 The service broker message forward mode is invalid. 0 0
5841 The default full-text language is not supported by the full-text search component. 0 0
5842 Too few worker threads are specified. The minimum is %d. 0 0
5843 Address Windowing Extensions (AWE) is not supported in this edition of SQL Server. 0 0
5844 User Instances are not supported in this edition of SQL Server. 0 0
5845 Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process. 0 0
5846 Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling". 0 0
5848 Physical CPU id %u has been hot added to node id %u as logical CPU id %u. This is an informational message only. No user action is required. 0 0
5849 Online CPU addition is not supported in the current edition of SQL Server. 0 0
5850 Online addition of CPU resources cannot be completed. A software non-uniform memory access (soft-NUMA) configuration was specified at SQL Server startup that does not allow online addition of CPU resources. To use the additional CPU resources, either add the new CPUs to the soft-NUMA configuration and restart SQL Server, or remove the soft-NUMA configuration and restart SQL Server. 0 0
5851 The AccessCheckResult quota must be greater than or equal to the bucket count 0 0
5852 The AccessCheckResult bucket count must be less than %d. 0 0
5854 The AccessCheckResult bucket count must be less than %d. 0 0
5904 Unable to issue checkpoint: there are not enough locks available. Background checkpoint process will remain suspended until locks are available. To free up locks, list transactions and their locks, and terminate transactions with the highest number of locks. 0 0
21000 Cannot subscribe to an inactive publication. 0 0
21001 Cannot add a Distribution Agent at the Subscriber for a push subscription. 0 0
21002 The Distribution Agent for this subscription already exists (%s). 0 0
21003 Changing publication names is no longer supported. 0 0
21004 Cannot publish the database object '%s' because it is encrypted. 0 0
21005 For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible. 0 0
21006 Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpublisher. 0 0
21007 Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor. 0 0
21008 Cannot uninstall the Distributor because there are Subscribers defined. 0 0
21009 The specified filter procedure is already associated with a table. 0 0
21010 Removed %ld replicated transactions consisting of %ld statements in %ld seconds (%ld rows/sec). 0 0
21011 Deactivated subscriptions. 0 0
21012 Cannot change the 'allow_push' property of the publication to "false". There are push subscriptions on the publication. 0 0
21013 Cannot change the 'allow_pull' property of the publication to "false". There are pull subscriptions on the publication. 0 0
21014 The @optname parameter value must be 'transactional' or 'merge'. 0 0
21015 The replication option '%s' has been set to TRUE already. 0 0
21016 The replication option '%s' has been set to FALSE already. 0 0
21017 Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQL Server 2000 compatible binary checksum operation can be performed on this article. 0 0
21018 There are too many consecutive snapshot transactions in the distribution database. Run the Log Reader Agent again or clean up the distribution database. 0 0
21019 Distribution agent for subscription added. 0 0
21020 no comment specified. 0 0
21021 Drop the Distributor before you uninstall replication. 0 0
21022 If set 'immediate_sync' property of a publication to true then must also set 'independent_agent' property to true. 0 0
21023 '%s' is no longer supported. 0 0
21024 The stored procedure '%s' is already published as an incompatible type. 0 0
21025 The string being encrypted cannot have null characters. 0 0
21026 Cannot have an anonymous subscription on a publication that does not have an independent agent. 0 0
21027 '%s' replication stored procedures are not installed. You must reinstall SQL Server with Replication. 0 0
21028 Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication. 0 0
21029 Cannot drop a push subscription entry at the Subscriber unless @drop_push is 'true'. 0 0
21030 Names of SQL Server replication agents cannot be changed. 0 0
21031 'post_script' is not supported for stored procedure articles. 0 0
21032 Could not subscribe because non-SQL Server Subscriber '%s' does not support 'sync tran' update mode. 0 0
21033 Cannot drop server '%s' as Distribution Publisher because there are databases enabled for replication on that server. 0 0
21034 Rows inserted or updated at the Subscriber cannot be outside the article partition. 0 0
21035 You have updated the Publisher property '%s' successfully. 0 0
21036 Another %s agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent. 0 0
21037 Invalid working directory '%s'. 0 0
21038 Windows Authentication is not supported by the server. 0 0
21039 The article '%s' contains the destination owner '%s'. Non-SQL Server Subscribers require articles to have the destination owner of NULL. 0 0
21040 Publication '%s' does not exist. 0 0
21041 A remote distribution Publisher is not allowed on this server version. 0 0
21042 The distribution Publisher property, 'distributor_password', has no usage and is not supported for a Distributor running on Windows NT 4.0. 0 0
21043 The Distributor is not installed. 0 0
21044 Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing. 0 0
21045 Cannot uninstall the Distributor because there are databases enabled for publishing or merge publishing. 0 0
21046 Cannot change distribution Publisher property 'distribution_db' because the Publisher is using the current distribution database. 0 0
21047 Cannot drop the local distribution Publisher because there are Subscribers defined. 0 0
21048 Cannot add login '%s' to the publication access list because it does not have access to the distribution server '%s'. 0 0
21049 The login '%s' does not have access permission on publication '%s' because it is not in the publication access list. 0 0
21050 Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation. 0 0
21051 Could not subscribe because non-SQL Server Subscriber '%s' does not support custom stored procedures. 0 0
21052 Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator is running, and that the subscription is active and initialized. If the subscription uses Microsoft Message Queueing, ensure the proper permissions are set on the queue. 0 0
21053 Input property parameter is not valid. See SQL Server Books Online for a list of valid parameters for sp_changemergepublication. 0 0
21054 The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers with updating subscriptions). Ensure sp_link_publication has been used to configure the linked server properly, and ensure that the login used to connect to the Publisher is in the publication access list. 0 0
21055 Invalid value for parameter %s specified for %s. 0 0
21056 The subscription to publication '%s' has expired or does not exist. 0 0
21057 Anonymous Subscribers cannot have updatable subscriptions. 0 0
21058 An updatable subscription to publication '%s' on Subscriber '%s' already exists. 0 0
21059 Cannot reinitialize subscriptions of non-immediate_sync publications. 0 0
21060 Could not subscribe because non-SQL Server Subscriber '%s' does not support parameterized statements. 0 0
21061 Invalid article status %d specified when adding article '%s'. 0 0
21062 The row size of table '%s' exceeds the replication limit of 6,000 bytes. 0 0
21063 Table '%s' cannot participate in updatable subscriptions because it is published for merge replication. 0 0
21064 The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Queue Reader Agent for subscription initialization. Try again after the (re)initialization completes. 0 0
21070 This subscription does not support automatic reinitialization (subscribed with the 'no sync' option). To reinitialize this subscription, you must drop and re-create the subscription. 0 0
21071 Cannot reinitialize article '%s' in subscription '%s:%s' to publication '%s' (subscribed with the 'no sync' option). 0 0
21072 The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subscription to receive data. 0 0
21073 The publication specified does not exist. 0 0
21074 The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. 0 0
21075 The initial snapshot for publication '%s' is not yet available. 0 0
21076 The initial snapshot for article '%s' is not yet available. 0 0
21077 Deactivated initial snapshot for anonymous publication(s). New subscriptions must wait for the next scheduled snapshot. 0 0
21078 Table '%s' does not exist in the Subscriber database. 0 0
21079 The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it. 0 0
21080 The 'msrepl_tran_version' column must be in the vertical partition of the article that is enabled for updatable subscriptions; it cannot be dropped. 0 0
21081 Server setting 'Allow triggers to be fired which fire other triggers (nested triggers)' must exist on updatable Subscribers. 0 0
21082 Database property 'IsRecursiveTriggersEnabled' has to be false for subscription databases at Subscribers that allow updatable subscriptions. 0 0
21083 Database compatibility level at immediate updating Subscribers cannot be less than 70. 0 0
21084 Publication '%s' does not allow anonymous subscriptions. 0 0
21085 The retention period must be less than the retention period for the distribution database. 0 0
21086 The retention period for the distribution database must be greater than the retention period of any existing non-merge publications. 0 0
21087 Client subscriptions and anonymous subscriptions cannot republish data. To republish data from this database, the subscription to the root Publisher must be a server subscription with a priority greater than 0. Drop the current subscription and create a server subscription. 0 0
21088 The initial snapshot for the publication is not yet available. 0 0
21089 Only members of the sysadmin fixed server role can perform this operation. 0 0
21090 Cannot upgrade merge replication metadata. Attempt the upgrade again by running the Merge Agent for the Subscriber or by running the Snapshot Agent for the Publisher. 0 0
21091 Global subscribers with priority 0 are not allowed to create merge publications. 0 0
21101 The custom command name %s specified for parameter %s will be ignored. A system generated name will be used instead. The publication allows %s and command names need not be specified. 0 0
21105 This edition of SQL Server cannot act as a Publisher or Distributor for replication. 0 0
21106 This edition of SQL Server does not support publications. 0 0
21107 '%ls' is not a table or view. 0 0
21108 This edition of SQL Server does not support transactional publications. 0 0
21109 The parameters @xact_seqno_start and @xact_seqno_end must be identical if @command_id is specified. 0 0
21110 @xact_seqno_start and @publisher_database_id must be specified if @command_id is specified. 0 0
21111 '%s' is not a valid parameter for the Snapshot Agent. 0 0
21112 '%s' is not a valid parameter for the Log Reader Agent. 0 0
21113 '%s' is not a valid parameter for the Distribution Agent. 0 0
21114 '%s' is not a valid parameter for the Merge Agent. 0 0
21115 %d is not a valid value for the '%s' parameter. The value must be a positive integer. 0 0
21116 '%s' is not a valid value for the '%s' parameter. The value must be 1, 2, or 3. 0 0
21117 '%s' is not a valid value for the '%s' parameter. The value must be 0, 1, or 2. 0 0
21118 '%s' is not a valid value for the '%s' parameter. The value must be greater than or equal to 0 and less than or equal to 10,000. 0 0
21119 %s is not a valid value for the '%s' parameter. The value must be a non-negative integer. 0 0
21120 Only members of the sysadmin fixed server role or db_owner fixed database role, or the owner of the subscription can drop subscription '%s' to publication '%s'. 0 0
21121 Only members of the sysadmin fixed server role and '%s' can drop the pull subscription to the publication '%s'. 0 0
21122 Cannot drop the distribution database '%s' because it is currently in use. 0 0
21123 The agent profile '%s' could not be found at the Distributor. 0 0
21124 Cannot find the table name or the table owner corresponding to the alternative table ID(nickname) '%d' in sysmergearticles. 0 0
21125 A table used in merge replication must have at least one non-computed column. 0 0
21126 Pull subscriptions cannot be created in the same database as the publication. 0 0
21127 Only global merge subscriptions can be added to database '%s'. 0 0
21128 Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. 0 0
21129 Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. 0 0
21130 Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger '%s' to first. 0 0
21131 There are existing subscriptions to heterogeneous publication '%s'. To add new articles, first drop the existing subscriptions to the publication. 0 0
21132 Cannot create transactional subscription to merge publication '%s'. The publication type should be either transactional(0) or snapshot(1) for this operation. 0 0
21133 Publication '%s' is not enabled to use an independent agent. 0 0
21134 The specified job ID must identify a Distribution Agent or a Merge Agent job. 0 0
21135 Detected inconsistencies in the replication agent table. The specified job ID does not correspond to an entry in '%ls'. 0 0
21136 Detected inconsistencies in the replication agent table. The specified job ID corresponds to multiple entries in '%ls'. 0 0
21137 This procedure supports only remote execution of push subscription agents. 0 0
21138 The 'offload_server' property cannot be the same as the Distributor name. 0 0
21139 Could not determine the Subscriber name for distributed agent execution. 0 0
21140 Agent execution cannot be distributed to a Subscriber that resides on the same server as the Distributor. 0 0
21141 The @change_active flag may not be specified for articles with manual filters or views. 0 0
21142 The SQL Server '%s' could not obtain Windows group membership information for login '%s'. Verify that the Windows account has access to the domain of the login. 0 0
21143 The custom stored procedure schema option is invalid for a snapshot publication article. 0 0
21144 Cannot subscribe to publication of sync_type 'dump database' because the Subscriber has subscriptions to other publications. 0 0
21145 Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type 'dump database'. 0 0
21146 @use_ftp cannot be 'true' while @alt_snapshot_folder is neither NULL nor empty. 0 0
21147 The '%s' database is not published for merge replication. 0 0
21148 Both @subscriber and @subscriberdb must be specified with non-null values simultaneously, or both must be left unspecified. 0 0
21149 The '%s' database is not published for transactional or snapshot replication. 0 0
21150 Unable to determine the snapshot folder for the specified subscription because the specified Subscriber is not known to the Distributor. 0 0
21151 Pre- and post-snapshot commands are not supported for a publication that may support non-SQL Server Subscribers by using the character-mode bcp as the synchronization method. 0 0
21152 Cannot create a subscription of sync_type 'none' to a publication using the 'concurrent' or 'concurrent_c' synchronization method. 0 0
21153 Cannot create article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber. 0 0
21154 Cannot change article '%s'. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber. 0 0
21155 Cannot change article '%s'. articles that are part of a concurrent synchronization publication can not have ins_cmd/del_cmd which exceeds %d characters . 0 0
21156 The @status parameter value must be 'initiated' or 'active'. 0 0
21157 The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined. 0 0
21158 For a publication to be enabled for the Internet, the 'ftp_address' property must not be null. 0 0
21159 If a publication is enabled for the Internet, the 'alt_snapshot_folder' property must be non-empty. 0 0
21160 The 'ftp_port' property must be a non-negative integer < 65536. 0 0
21161 Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers. 0 0
21162 It is invalid to exclude the rowguid column for the table from the partition. 0 0
21163 It is not possible to add column '%s' to article '%s' because the snapshot for publication '%s' has been run. 0 0
21164 Column '%s' cannot be included in a vertical partition because it is neither nullable nor defined with a default value. 0 0
21165 Column '%s' cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value. 0 0
21166 Column '%s' does not exist. 0 0
21167 The specified job ID does not represent a %s agent job for any push subscription in this database. 0 0
21168 Only members of the sysadmin fixed server role, members of the db_owner fixed database role, and owners of subscriptions served by the specified replication agent job can modify the agent offload settings. 0 0
21169 Could not identify the Publisher '%s' at the Distributor '%s'. Make sure that the server '%s' is registered at the Distributor. 0 0
21170 The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, SQL Server 2005, and OLE DB Subscribers can use transformable subscriptions. 0 0
21171 Could not find package '%s' in msdb at server '%s'. 0 0
21172 The publication has to be in 'character', 'concurrent_c', or 'database snapshot character' bcp mode to allow DTS. 0 0
21173 The publication has to be 'independent_agent type' to allow DTS. 0 0
21174 Because this publication allows transformable subscriptions using DTS, it requires autogenerated stored procedures and parameterized commands, which are set using default value for the @status. 0 0
21175 You cannot change the ins_cmd, upd_cmd, or del_cmd article properties because the publication allows Data Transformation Services or updatable subscriptions. 0 0
21176 Only members of the sysadmin fixed server role, db_owner fixed database role, or the creator of the subscription can change the subscription properties. 0 0
21177 Could not create column list because it is too long. Create the list manually. 0 0
21178 Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions using DTS. To allow transformable subscriptions, you must drop the publication and then and re-create it, specifying that transformable subscriptions are allowed. 0 0
21179 Invalid @dts_package_location parameter value. Valid options are 'Distributor' or 'Subscriber'. 0 0
21180 A publication that allows DTS cannot be enabled for updatable subscriptions. 0 0
21181 @dts_package_name can be set for push subscriptions only. 0 0
21182 The @agent_type parameter must be one of 'distribution', 'merge', or NULL. 0 0
21183 Invalid property name '%s'. 0 0
21184 %s parameter is incorrect: it should be '%s', '%s' or '%s'. 0 0
21185 The subscription is not initialized or not created for failover mode operations. 0 0
21186 Subscription for Publisher '%s' does not have a valid queue_id. 0 0
21187 The current mode is the same as the requested mode. 0 0
21188 Changed update mode from [%s] to [%s]. 0 0
21189 The queue for this subscription with queue_id = '%s' is not empty. Run the Queue Reader Agent to make sure the queue is empty before setting mode from [queued] to [immediate]. 0 0
21190 Overriding queue check for setting mode from [%s] to [%s]. 0 0
21192 MSrepl_tran_version column is a predefined column used for replication and can be only of data type uniqueidentifier 0 0
21193 @identity_range, @pub_identity_range, or @threshold cannot be NULL when @identityrangemanagementoption is set to AUTO. 0 0
21194 Cannot support identity range management because this table does not have an identity column. 0 0
21195 A valid identity range is not available. Check the data type of the identity column. 0 0
21196 Identity automation failed. 0 0
21197 Failed to allocate new identity range. 0 0
21198 Schema replication failed. 0 0
21199 This change cannot take effect until you run the snapshot again. 0 0
21200 Publication '%s' does not exist. 0 0
21201 Dropping a column that is being used by a merge filter clause is not allowed. 0 0
21202 It is not possible to drop column '%s' to article '%s' because the snapshot for publication '%s' has already been run. 0 0
21203 Duplicate rows found in %s. Unique index not created. 0 0
21204 The publication '%s' does not allow subscription copy or its subscription has not been synchronized. 0 0
21205 The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes. 0 0
21206 Cannot resolve load hint for object %d because the object is not a user table. 0 0
21207 Cannot find source object ID information for article %d. 0 0
21208 This step failed because column '%s' exists in the vertical partition. 0 0
21209 This step failed because column '%s' does not exist in the vertical partition. 0 0
21210 The publication must be immediate_sync type to allow subscription copy. 0 0
21211 The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach it using sp_attach_subscription. 0 0
21212 Cannot copy subscription. Only single file subscription databases are supported for this operation. 0 0
21213 Subscribers cannot subscribe to publications that allow DTS without using a DTS package. 0 0
21214 Cannot create file '%s' because it already exists. 0 0
21215 An alternate synchronization partner can be configured only at the Publisher. 0 0
21216 Publisher '%s', publisher database '%s', and publication '%s' are not valid synchronization partners. 0 0
21217 Publication of '%s' data from Publisher '%s'. 0 0
21218 The creation_script property cannot be NULL if a schema option of 0x0000000000000000 is specified for the article. 0 0
21219 The specified source object must be a stored procedure object if it is published as a 'proc schema only' type article. 0 0
21220 Unable to add the article '%s' because a snapshot has been generated for the publication '%s'. 0 0
21221 The specified source object must be a view object if it is going to be as a 'view schema only' type article. 0 0
21222 The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, 0x00001000, 0x00002000, 0x00400000, 0x02000000, 0x08000000, 0x10000000, 0x20000000, 0x40000000, and 0x80000000. 0 0
21223 The @pre_creation_command parameter for a schema only article must be either 'none' or 'drop'. 0 0
21224 '%s' is not a valid property for a schema only article. 0 0
21225 The 'offload_server' property cannot be NULL or empty if the pull subscription agent is to be enabled for remote activation. 0 0
21226 The database '%s' does not have a pull subscription to the specified publication. 0 0
21227 The 'offload_server' property cannot be the same as the Subscriber server name. 0 0
21228 The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' type article. 0 0
21229 The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, 0x00002000, 0x00040000, 0x00100000, 0x00200000, 0x00400000, 0x00800000, 0x01000000, 0x08000000, 0x40000000, and 0x80000000. 0 0
21230 Do not call this stored procedure for schema change because the current database is not enabled for replication. 0 0
21231 Automatic identity range support is useful only for publications that allow updating subscribers. 0 0
21232 Identity range values must be positive integers that are greater than 1. 0 0
21233 Threshold value must be from 1 through 100. 0 0
21234 Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set 'identity_insert' settings at the Subscriber. 0 0
21235 Article property '%s' can be set only when the article uses automatic identity range management. 0 0
21236 The subscription(s) to Publisher '%s' does not allow subscription copy or it has not been synchronized. 0 0
21237 There is a push subscription to Publisher '%s'. Only pull and anonymous subscriptions can be copied. 0 0
21238 This database either is a publisher, or there is a push subscription to publication '%s'. Only pull and anonymous subscriptions can be copied. 0 0
21239 Cannot copy subscriptions because there is no synchronized subscription found in the database. 0 0
21240 The table '%s' is already published as another article with a different automatic identity support option. 0 0
21241 The threshold value should be from 1 through 100. 0 0
21242 Conflict table for article '%s' could not be created successfully. 0 0
21243 Publisher '%s', publication database '%s', and publication '%s' could not be added to the list of synchronization partners. 0 0
21244 Character mode publication does not support vertical filtering when the base table does not support column-level tracking. 0 0
21245 Table '%s' is not part of publication '%s'. 0 0
21246 This step failed because table '%s' is not part of any publication. 0 0
21247 Cannot create file at '%s'. Ensure the file path is valid. 0 0
21248 Cannot attach subscription file '%s'. Ensure the file path is valid and the file is updatable. 0 0
21249 OLE DB or ODBC Subscribers cannot subscribe to article '%s' in publication '%s' because the article has a timestamp column and the publication is 'allow_queued_tran' (allows queued updating subscriptions). 0 0
21250 Primary key column '%s' cannot be excluded from a vertical partition. 0 0
21251 Publisher '%s', publisher database '%s', publication '%s' could not be removed from the list of synchronization partners. 0 0
21252 It is invalid to remove the default Publisher '%s', publication database '%s', and publication '%s' from the list of synchronization partners 0 0
21253 Parameter '@add_to_active_directory' cannot be set to TRUE because Active Directory client package is not installed properly on the machine where SQL Server is running. 0 0
21254 The Active Directory operation on publication '%s' could not be completed because Active Directory client package is not installed properly on the machine where SQL Server is running. 0 0
21255 Column '%s' already exists in table '%s'. 0 0
21256 A column used in filter clause '%s' either does not exist in the table '%s' or cannot be excluded from the current partition. 0 0
21257 Invalid property '%s' for article '%s'. 0 0
21258 You must first drop all existing merge publications to add an anonymous or local subscription to database '%s'. 0 0
21259 Invalid property value '%s'. See SQL Server Books Online for a list of valid parameters for sp_changemergearticle. 0 0
21260 Schema replication failed because database '%s' on server '%s' is not the original Publisher of table '%s'. 0 0
21261 The offload server must be specified if the agent for this subscription is to be offloaded for remote execution. 0 0
21262 Failed to drop column '%s' from the partition because a computed column is accessing it. 0 0
21263 Parameter '%s' cannot be NULL or an empty string. 0 0
21264 Column '%s' cannot be dropped from table '%s' because it is a primary key column. 0 0
21265 Column '%s' cannot be dropped from table '%s' because there is a unique index accessing this column. 0 0
21266 Cannot publish table '%s' for both a merge publication and a publication with the updatable subscribers option. 0 0
21267 Invalid value for queue type was specified. Valid values = (%s). 0 0
21268 Cannot change the parameter %s while there are subscriptions to the publication. 0 0
21269 Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication. 0 0
21270 Queued snapshot publication property '%s' cannot have the value '%s'. 0 0
21272 Cannot clean up the meta data for publication '%s' because other publications are using one or more articles in this publication. 0 0
21273 You must upgrade the Subscriber to SQL Server 2000 to create updatable subscriptions when the Publisher is SQL Server 2000 or higher. 0 0
21274 Invalid publication name '%s'. 0 0
21275 Cannot publish the schema-bound view '%ls'. The value specified for the @type parameter must be "indexed view schema only" (for snapshot or transactional replication) or "indexed view logbased" (for transactional replication only). 0 0
21276 The type must be 'table' or '( view | indexed view | proc | func ) schema only'. 0 0
21277 Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view schema only" or "indexed view logbased") can be used only for indexed views. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique clustered index. 0 0
21278 Cannot publish the source object '%ls'. The value specified for the @type parameter ("indexed view logbased") requires that the view be schema bound with a unique clustered index. Either specify a value of "view schema only" for the @type parameter, or modify the view to be schema bound with a unique clustered index. 0 0
21279 The 'schema_option' property for a merge article cannot be changed after a snapshot is generated for the publication. To change the 'schema_option' property of this article the corresponding merge publication must be dropped and re-created. 0 0
21280 Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at transaction level. 0 0
21281 Publication '%s' cannot be subscribed to by Subscriber database '%s' because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level. 0 0
21282 @identity_range, @pub_identity_range, and @threshold must be NULL when @identityrangemanagementoption is set to 'none' or 'manual'. 0 0
21283 Column '%s' of table '%s' cannot be excluded from a vertical partition because there is a computed column that depends on it. 0 0
21284 Failed to drop column '%s' from table '%s'. 0 0
21285 Failed to add column '%s' to table '%s'. 0 0
21286 Conflict table '%s' does not exist. 0 0
21287 The specified @destination_folder is not a valid path of an existing folder. 0 0
21288 Could not create the snapshot directory structure in the specified @destination_folder. 0 0
21289 Either the snapshot files have not been generated or they have been cleaned up. 0 0
21290 The identity range value provided has exceeded the maximum value allowed. 0 0
21291 The specified automatic identity support parameters conflict with the settings in another article. 0 0
21292 Object '%s' cannot be published twice in the same publication. 0 0
21293 Warning: adding updatable subscription for article '%s' may cause data inconsistency as the source table is already subscribed to '%s' 0 0
21294 Either @publisher (and @publisher_db) or @subscriber (and @subscriber_db) must be specified, but both cannot be specified. 0 0
21295 Publication '%s' does not contain any article that uses automatic identity range management. 0 0
21296 Parameter @resync_type must be either 0, 1, 2. 0 0
21297 Invalid resync type. No validation has been performed for this subscription. 0 0
21298 Failed to resynchronize this subscription. 0 0
21299 Invalid Subscriber partition validation expression '%s'. 0 0
21300 The resolver information was specified without specifying the resolver to be used for article '%s'. The default resolver will be used. 0 0
21301 The resolver information should be specified while using the '%s' resolver. 0 0
21302 The resolver information should specify a column with data type, datetime, or smalldatetime while using the '%s' resolver. 0 0
21303 The article '%s' should enable column tracking to use the '%s' resolver. The default resolver will be used to resolve conflicts on this article. 0 0
21304 The merge triggers could not be created on the table '%s'. 0 0
21305 The schema change information could not be updated at the subscription database. 0 0
21306 The copy of the subscription could not be made because the subscription to publication '%s' has expired. 0 0
21307 The subscription could not be attached because the subscription to publication '%s' has expired. 0 0
21308 Rowcount validation profile. 0 0
21309 Profile used by the Merge Agent to perform rowcount validation. 0 0
21310 Rowcount and checksum validation profile. 0 0
21311 Profile used by the Merge Agent to perform rowcount and checksum validation. 0 0
21312 Cannot change this publication property because there are active subscriptions to this publication. 0 0
21313 Subscriber partition validation expression must be NULL for static publications. 0 0
21314 There must be one and only one of '%s' and '%s' that is not NULL. 0 0
21315 Failed to adjust Publisher identity range for table '%s'. 0 0
21316 Failed to adjust Publisher identity range for publication '%s'. 0 0
21317 A push subscription to the publication '%s' already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions. 0 0
21318 Table '%s' must have at least one column that is included in the vertical partition. 0 0
21319 Could not find the Snapshot Agent command line for the specified publication. Check that a valid regular snapshot job exists on the distributor. 0 0
21320 The version of the Distributor cannot be lower than the version of the Publisher. 0 0
21321 The parameter @dynamic_snapshot_location cannot be an empty string. 0 0
21322 This publication logs conflicts on both replicas. Pre-SQL Server 2005 subscribers will not honor this setting. 0 0
21323 A dynamic snapshot job can be scheduled only for a publication with dynamic filtering enabled. 0 0
21324 A Snapshot Agent must be added for the specified publication before a dynamic snapshot job can be scheduled. 0 0
21325 Could not find the Snapshot Agent ID for the specified publication. 0 0
21326 Could not find the dynamic snapshot job with a '%ls' of '%ls' for the specified publication. 0 0
21327 '%ls' is not a valid dynamic snapshot job name. 0 0
21328 The specified dynamic snapshot job name '%ls' is already in use. Try the operation again with a different job name. 0 0
21329 Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_snapshot_jobname, can be specified with a nondefault value. 0 0
21330 Cannot create a sub-directory under the snapshot folder (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to create a sub-directory under the snapshot folder. 0 0
21331 Cannot copy user script file to the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories. 0 0
21332 Failed to retrieve information about the publication : %ls. Check the name again. 0 0
21333 A generation that was expected to be in %s.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription database, reinitialize the subscription. If this error occurred in a publication database, restore the database from a backup. 0 0
21334 Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant 0 0
21335 Warning: column '%s' already exists in the vertical partition. 0 0
21336 Warning: column '%s' does not exist in the vertical partition. 0 0
21337 Invalid @subscriber_type value. Valid options are 'local' and 'global'. 0 0
21338 Cannot execute sp_dropmergearticle if the publication has a Subscriber that is running on a version of SQL Server 2000 or earlier. Drop and re-create the publication without the article '%s' or set the publication compatibility level of publication '%s' to '90RTM' before calling sp_dropmergearticle. 0 0
21339 Warning: the publication uses a feature that is only supported only by subscribers running '%s' or higher. 0 0
21340 On Demand user script cannot be applied to the snapshot publication. 0 0
21341 @dynamic_snapshot_location cannot be a non-empty string while @alt_snapshot_folder is neither empty nor null. 0 0
21342 @dynamic_snapshot_location cannot be a non-empty string while @use_ftp is 'true'. 0 0
21343 Could not find stored procedure '%s'. 0 0
21344 Invalid value specified for %ls parameter. 0 0
21345 Excluding the last column in the partition is not allowed. 0 0
21346 Failed to change the owner of '%s' to '%s'. 0 0
21347 Column '%s' cannot be excluded from the vertical partitioning because there is a unique index accessing this column. 0 0
21348 Invalid property name '%s'. 0 0
21349 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because decentralized conflict logging is designated. 0 0
21350 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a compressed snapshot is used. 0 0
21351 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because vertical filters are being used. 0 0
21352 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because schema replication is performed. 0 0
21353 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide reinitialization is performed. 0 0
21354 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because publication wide reinitialization is performed. 0 0
21355 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because merge metadata cleanup task is performed. 0 0
21356 Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication '%s' because publication wide validation task is performed. 0 0
21357 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because data types new in SQL Server 2000 exist in one of its articles. 0 0
21358 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because at least one timestamp column exists in one of its articles. 0 0
21359 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because automatic identity ranges are being used. 0 0
21360 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because a new article has been added to the publication after its snapshot has been generated. 0 0
21361 The specified @agent_jobid is not a valid job id for a '%s' agent job. 0 0
21362 Merge filter '%s' does not exist. 0 0
21363 Failed to add publication '%s' to Active Directory. %s 0 0
21364 Could not add article '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. 0 0
21365 Could not add article '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions. 0 0
21366 Could not add filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. 0 0
21367 Could not add filter '%s' because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions. 0 0
21368 The specified offload server name contains the invalid character '%s'. 0 0
21369 Could not remove publication '%s' from Active Directory. 0 0
21370 The resync date specified '%s' is not a valid date. 0 0
21371 Could not propagate the change on publication '%s' to Active Directory. 0 0
21372 Cannot drop filter '%s' from publication '%s' because its snapshot has been run and this publication could have active subscriptions. Set @force_reinit_subscription to 1 to reinitialize all subscriptions and drop the filter. 0 0
21373 Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available. 0 0
21374 Upgrading distribution settings and system objects in database %s. 0 0
21375 Upgrading publication settings and system objects in database %s. 0 0
21376 Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available. 0 0
21377 Upgrading subscription settings and system objects in database %s. 0 0
21378 Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again. 0 0
21379 Cannot drop article '%s' from publication '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. 0 0
21380 Cannot add timestamp column without forcing reinitialization. Set @force_reinit_subscription to 1 to force reinitialization. 0 0
21381 Cannot add (drop) column to table '%s' because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subscription to 1 to force reinitialization. 0 0
21382 Cannot drop filter '%s' because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot. 0 0
21383 Cannot enable a merge publication on this server because the working directory of its Distributors is not using a UNC path. 0 0
21384 The specified subscription does not exist or has not been synchronized yet. 0 0
21385 Snapshot failed to process publication '%s'. Possibly due to active schema change activity or new articles being added. 0 0
21386 Schema change failed on object '%s'. Possibly due to active snapshot or other schema change activity. 0 0
21387 The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider using the default mechanism instead of the dynamic snapshot for initializing the specified subscription. 0 0
21388 The concurrent snapshot for publication '%s' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication must be restarted until a complete snapshot is generated. 0 0
21389 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because column-level collation is scripted out with the article schema creation script. 0 0
21390 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because extended properties are scripted out with the article schema creation script. 0 0
21391 Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication '%s' because it contains schema-only articles. 0 0
21392 Row filter(%s) is invalid for column partition(%s) for article '%s' in publication '%s'. 0 0
21393 Dropping row filter(%s) for article '%s' in '%s'. Reissue sp_articlefilter and sp_articleview to create a row filter. 0 0
21394 Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include DRI constraints. 0 0
21395 This column cannot be included in a transactional publication because the column ID is greater than 255. 0 0
21396 The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Server Books Online for a list of valid values. 0 0
21397 The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at the Distributor. Retry the operation again with a more up-to-date log, differential, or full database backup. 0 0
21398 Could not complete setting up the no-sync subscription at the Distributor while the distribution cleanup agent is running. The operation has a greater chance of success if the distribution cleanup agent is temporarily disabled. 0 0
21399 The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable at the Distributor. Specify a higher LSN. 0 0
21400 Article property must be changed at the original Publisher of article '%s'. 0 0
21401 Article name cannot be 'all'. 0 0
21402 Incorrect value for parameter '%s'. 0 0
21403 The 'max_concurrent_dynamic_snapshots' publication property must be greater than or equal to zero. 0 0
21404 '%s' is not a valid value for the '%s' parameter. The value must be a positive integer greater than 300 or 0. 0 0
21405 '%s' is not a valid value for the '%s' parameter. The value must be an integer greater than or equal to %d. 0 0
21406 '%s' is not a valid value for the '%s' parameter. The value must be 0 or 1. 0 0
21407 Cannot create the subscription. If you specify a value of "initialize with backup" for the @sync_type parameter, you must subscribe to all articles in the publication by specifying a value of "all" for the @article parameter. 0 0
21408 Cannot create the subscription. You must specify a value of "Active" or "Subscribed" for the @status parameter. This is because the value specified for the @sync_type parameter is "initialize with backup" or "replication support only". 0 0
21409 Only one of parameters %s and %s can be set. 0 0
21410 Snapshot Agent startup message. 0 0
21411 Distribution Agent startup message. 0 0
21412 Merge Agent startup message. 0 0
21413 Failed to acquire the application lock indicating the front of the queue. 0 0
21414 Unexpected failure acquiring an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available. 0 0
21415 Unexpected failure releasing an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available. 0 0
21416 Property '%s' of article '%s' cannot be changed. 0 0
21417 Having a queue timeout value of over 12 hours is not allowed. 0 0
21419 Filter '%s' of article '%s' cannot be changed. 0 0
21420 Subscription property '%s' cannot be changed. 0 0
21421 Article '%s' cannot be dropped because there are other articles using it as a join article. 0 0
21422 Queue Reader Agent startup message. 0 0
21423 Either the publication '%s' does not exist or you do not have sufficient permissions to access it. Ensure that the publication exists and that the account under which the Merge Agent connects to the Publisher is included in the publication access list (PAL). 0 0
21424 The @publisher parameter must be NULL for SQL Server publishers. 0 0
21425 The @publisher parameter may not be NULL for heterogeneous publishers. 0 0
21426 No No shared agent subscription exists for publication '%s' and the subscriber/subscriber database pair '%s'/'%s'. 0 0
21450 The replication %s could not be upgraded for %s databases. Ensure that %s is upgraded and execute %s again. 0 0
21451 The %s %s (%s) login (%s) password has been changed. 0 0
21452 Warning: The %s agent job has been implicitly created and will run under the SQL Server Agent Service Account. 0 0
21454 The internal procedure sp_MStran_is_snapshot_required must be executed at the Distributor if the @run_at_distributor parameter has a value of 1. If the problem persists, contact Microsoft Customer Support Services. 0 0
21456 Value provided for parameter %s is not valid. 0 0
21460 The primary key for source table "%s" includes the timestamp column "%s". Cannot create the article for the specified publication because it allows updating Subscribers. 0 0
21481 Cannot create replication subscription(s) in the master database. Choose another database for creating subscriptions. 0 0
21482 %s can only be executed in the "%s" database. 0 0
21484 Article validation was requested for snapshot publication "%s". Article validation is only valid for transactional publications. 0 0
21485 Tracer tokens cannot be posted for a snapshot publication. 0 0
21486 An error occurred while logging the tracer token history information. The tracer token could not be posted. 0 0
21487 An error occurred while inserting the tracer token to the log. The tracer token could not be posted. 0 0
21488 No No active subscriptions were found. The publication must have active subscriptions in order to post a tracer token. 0 0
21489 A database '%s' already exists. If you intend this to be your distribution database set @existing_db = 1. 0 0
21490 The value specified for the %s parameter of sp_mergearticlecolumn must be '%s'. A value of 'true' is allowed only when this procedure is called by another replication procedure. Either set the value of the @schema_replication parameter to 'false' or do not specify a value. 0 0
21499 The procedure %s failed to %s the resource %s. Server error = %d. 0 0
21500 Invalid subscription type is specified. A subscription to publication '%s' already exists in the database with a different subscription type. 0 0
21501 The supplied resolver information does not specify a valid column name to be used for conflict resolution by '%s'. 0 0
21502 The publication '%s' does not allow the subscription to synchronize to an alternate synchronization partner. 0 0
21503 Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes have completed. 0 0
21504 Cleanup of merge meta data at republisher '%s'.'%s' could not be performed because merge processes are propagating changes to the republisher. All subscriptions to this republisher must be reinitialized. 0 0
21505 Changes to publication '%s' cannot be merged because it has been marked inactive. 0 0
21506 sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge meta data cleanup. 0 0
21507 All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data cleanup. 0 0
21508 Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes have completed. 0 0
21509 Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed after all republishers have quiesced their changes. 0 0
21510 Data changes are not allowed while cleanup of merge meta data is in progress. 0 0
21511 Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row. 0 0
21512 %ls: The %ls parameter is shorter than the minimum required size. 0 0
21514 Cannot complete the requested operation in the subscription database because a snapshot is currently being delivered to the database. Perform the operation again at a later time. To stop the delivery of the snapshot, stop the Distribution Agent or Merge Agent associated with the subscription. 0 0
21515 Replication custom procedures will not be scripted because the specified publication '%s' is a snapshot publication. 0 0
21516 Transactional replication custom procedures for publication '%s' from database '%s': 0 0
21517 Replication custom procedures will not be scripted for article '%s' because the auto-generate custom procedures schema option is not enabled. 0 0
21518 Replication custom procedures for article '%s': 0 0
21519 Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements. 0 0
21520 Custom procedure will not be scripted because '%s' is not a recognized article update command syntax. 0 0
21521 Some generation values are above the upper limit of %d used in SQL Server 2000. Change the publication_compatibility_level of the publication to 90 to make this work. 0 0
21522 This article cannot use the '%s' feature because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication '%s' to '90RTM'. 0 0
21523 Adding column '%s' to table '%s' failed. Articles can have at most %d columns, including columns that have been filtered. 0 0
21525 A lightweight replica must be anonymous. 0 0
21526 Article '%s' already belongs to a subscription with a different value for the @lightweight property. 0 0
21527 Publication '%s' cannot be added to database '%s', because a publication with a lower compatibility level already exists. All merge publications in a database must have the same compatibility level. 0 0
21528 Publication '%s' cannot be added to database '%s', because a publication with a higher compatibility level already exists. All merge publications in a database must have the same compatibiliy level. 0 0
21530 The schema change failed during execution of an internal replication procedure. For corrective action, see the other error messages that accompany this error message. 0 0
21531 The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republishing hierarchy, DDL commands can only be executed at the root Publisher, not at any of the republishing Subscribers. 0 0
21532 Cannot add a data definition language trigger for replicating '%.*ls' events. 0 0
21533 Cannot insert information into the schema change tracking table sysmergeschemachange. 0 0
21535 The article '%s' is already published in another publication, and is set to use nonoverlapping partitions with multiple subscribers per partition (@partition_options = 2). This setting does not permit the article to be included in more than one publication. 0 0
21537 The column '%s' in table '%s' is involved in a foreign key relationship with a column in table '%s', but this column was not found in the specified join clause. A logical record relationship between these tables should include this column. 0 0
21538 Table '%s' cannot have table '%s' as a parent in a logical record relationship because it already has a different parent table. A logical record relationship allows only one parent table for a given child table. 0 0
21539 A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from the parent table to the child table. Either change the value of the @filter_type parameter, or set the @join_unique_key parameter to 1. 0 0
21540 You cannot drop a column defined as data type uniqueidentifier with the rowguidcol property because merge replication uses this column for tracking. To drop the column, you must first drop the table from all publications and subscriptions. 0 0
21541 Cannot complete ALTER TABLE command. Do not execute the command 'ALTER TABLE table_name DISABLE TRIGGER ALL' on a published table. Reissue multiple 'ALTER TABLE table_name DISABLE TRIGGER trigger_name' statements to disable each trigger individually on the given table. 0 0
21542 Encountered server error %d while executing <%s>. 0 0
21543 The schema for the article %s was either not generated properly or was not applied properly during initial synchronization. This may be due to permissions issues. Verify whether the object exists, and whether the necessary permissions are granted. 0 0
21544 Value specified for the publication property replicate_ddl is not valid. The value must be 1 or 0. 0 0
21545 You cannot disable a trigger used by merge replication on a published table. To drop the trigger, drop the table from the publication. 0 0
21546 Cannot replicate the ALTER TABLE command. It contains multiple DROP commands, including a DROP command for a column that is not included in all subscriptions to this article. Use a single DROP command in each ALTER TABLE command. 0 0
21547 Encountered server error %d while restoring the log for database %s. 0 0
21548 Cannot execute sp_change_subscription_properties. This stored procedure can only be used for publications that have at least one pull subscription. 0 0
21549 Cannot add the computed column '%s' to the publication. You must first add all columns on which this column depends; you cannot filter any of these colunmns from the article. 0 0
21550 Before you drop the column from the publication, all computed columns that depend on column '%s' must be dropped. 0 0
21551 Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation. 0 0
21552 Merge data definition language (DDL) error: Dropping a column used in a row filter or a join filter is not allowed. To drop a column used in a row filter, first change the row filter using sp_changemergearticle. To drop a column used in a join filter, first drop the join filter using sp_dropmergefilter. 0 0
21561 The value specified for parameter %s = %d is not valid. 0 0
21564 The table %s contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it must be set to NOT NULL. Replication failed to alter this column, so you must drop the column and then add the table as an article again using sp_addarticle. Replication will then add the column to the table. 0 0
21567 The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications that allow updating subscriptions. If you do not require updating subscriptions, specify a different call format. If you do require updating subscriptions, you must drop the publication and re-create it to specify that updating subscriptions are allowed. 0 0
21569 The article %s in the publication %s does not have a valid conflict table entry in the system table sysarticleupdates. This entry is required for publications that allow queued updating subscriptions. Check for errors in the last run of the Snapshot Agent. 0 0
21570 Cannot create the logical record relationship. Table '%s' does not have a foreign key referencing table '%s'. A logical record relationship requires a foreign key relationship between the parent and child tables. 0 0
21571 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". 0 0
21572 Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is disabled. To create the logical record relationship, first enable the foreign key constraint. 0 0
21573 Cannot add a logical record relationship because the foreign key constraint '%s' on table '%s' is defined with the NOT FOR REPLICATION option. To add the logical record relationship, first drop the foreign key constraint, and then re-create it without the NOT FOR REPLICATION option. 0 0
21574 Cannot add a logical record relationship because the article '%s' is published in publication '%s', which has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM. 0 0
21575 The value specified for the property filter_type is not valid. Valid values are 1 (join filter only), 2 (logical record relation only), and 3 (join filter and logical record relation). 0 0
21576 Cannot add a logical record relationship between tables '%s' and '%s' because the foreign key column '%s' in table '%s' allows NULL values. Alter the column to disallow NULL values. 0 0
21578 In order to use partition_options of 2 (non overlapping partitions with multiple subscriptions per partition) or 3 (non overlapping partitions one subscription per partition) the publication '%s' must be enabled to use partition groups functionality. Use sp_changemergepublication to set 'use_partition_groups' to 'true'. 0 0
21579 Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in multiple join filters. Either select a value of 0 or 1 for the @partition_options parameter, or drop all but one of the join filters by using sp_dropmergefilter. 0 0
21580 Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in both a row filter and a join filter. Either select a value of 0 or 1 for the @partition_options parameter; drop the join filter by using sp_dropmergefilter; or change the row filter by using sp_changemergepublication. 0 0
21581 Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a join filter with a join_unique_key value of 0. Either select a value of 0 or 1 for the @partition_options parameter, or use sp_changemergefilter to specify a value of 1 for join_unique_key. 0 0
21582 Article "%s" in publication "%s" does not qualify for the partition option that you specified. You cannot specify a value of 2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a direct or indirect join filter relationship with parent article "%s". The parent article does not use the same value for partition_options. Use sp_changemergepublication to change the value for one of the articles. 0 0
21583 Cannot update the column in article '%s'. The article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property, and the column is involved in a row filter and/or a join filter. In this situation, the column cannot be updated at a Subscriber or republisher; it must be updated at the top-level Publisher. 0 0
21584 Cannot insert the row for article '%s'. The row does not belong to the Subscriber's partition, and the article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property. Nonoverlapping partitions do not allow out-of-partition inserts. 0 0
21585 Cannot specify custom article ordering in publication '%s' because the publication has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM. 0 0
21597 The article includes only the rowguidcol column. You must publish at least one other column. 0 0
21598 Modifying DDL triggers created by replication is disallowed since these are required to track DDL changes. 0 0
21599 The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; self-joins are not permitted. 0 0
21600 Non-SQL Server Publisher [%s] cannot be found. Execute sp_helpdistpublishers to view a list of available Publishers. 0 0
21601 The value of the parameter @type must be 'logbased' for Oracle publications. 0 0
21603 The refresh of Oracle publisher '%s' by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta data has been retained in its failed state to help in diagnosing the cause of the failure. When the problem has been diagnosed and resolved, rerun sp_refresh_heterogeneous_publisher to complete the refresh. 0 0
21604 The non-SQL Server Publisher vendor is not valid. Attempt to add the Publisher again. If the problem persists, contact Microsoft Customer Support Services. 0 0
21605 Non-SQL Server Publishers must be configured in the context of the distribution database. Execute sp_adddistpublisher in the context of the distribution database. 0 0
21606 Parameter "%s" is for non-SQL Server Publishers only. The value of this parameter must be "%s" for a SQL Server Publisher. 0 0
21607 sp_refresh_heterogeneous_publisher was unable to obtain publisher information for Oracle publisher '%s'. sp_refresh_heterogeneous_publisher may only be called to refresh Oracle publishers currently defined at the distributor. 0 0
21608 Cannot use a value of TRUE for the parameter @ignore_distributor. The value must be FALSE for a non-SQL Server Publisher. 0 0
21609 Non-SQL Server publications do not support updatable subscriptions. The properties allow_sync_tran and allow_queued_tran must be "false". 0 0
21610 The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher '%s' did not alter any meta data at the Oracle publisher. Make certain that the correct Oracle publisher has been identified and that the requirements for refreshing the Oracle publisher have been met. 0 0
21611 Cannot drop the distribution Publisher "%s" because it has publications defined. Drop the publications first. 0 0
21612 For non-SQL Server Publishers, the value of the @sync_method parameter must be "character" or "concurrent_c". 0 0
21613 Constraint column '%s' not found in table '%s'. 0 0
21614 Index column '%s' not found in table '%s', 0 0
21615 Unable to find table information for article %s. Local distributor cache may be corrupt. 0 0
21616 Cannot find column [%s] in the article. Verify that the column exists in the underlying table, and that it is included in the article. 0 0
21617 Unable to run SQL*PLUS. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21617 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21618 The Publisher '%s' does not exist. To view a list of Publishers, use the stored procedure sp_helpdistpublisher. 0 0
21619 Must provide both @SelectColumnList and @InsColumnList. 0 0
21620 The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21620 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21621 Unable to create the public synonym %s. Verify that the replication administrative user has been granted the CREATE SYNONYM permission. 0 0
21622 Unable to grant SELECT permission on the public synonym %s. Verify that the replication administrative user has sufficient permissions. 0 0
21623 Unable to update the public synonym 'MSSQLSERVERDISTRIBUTOR' to mark Oracle instance '%s' as a SQL Server publisher. 0 0
21624 Unable to locate the registered Oracle OLEDB provider, OraOLEDB.Oracle, at distributor '%s'. Make certain that a current version of the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21624 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21625 Unable to update the publisher table HREPL_PUBLISHER at the Oracle instance '%s'. 0 0
21626 Unable to connect to Oracle database server '%s' using the Oracle OLEDB provider OraOLEDB.Oracle. For addition information, see SQL Server Error 21626 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21627 Unable to connect to Oracle database server '%s' using the Microsoft OLEDB provider MSDAORA. For addition information, see SQL Server Error 21627 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21628 Unable to update the registry of distributor '%s' to allow Oracle OLEDB provider OraOLEDB.Oracle to run in process with SQL Server. Make certain that current login is authorized to modify SQL Server owned registry keys. For addition information, see SQL Server Error 21628 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21629 The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not present at the distributor. Make certain that the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21629 in Troubleshooting Oracle Publishers in SQL Server Books Online. 0 0
21630 Unable to determine whether the table '%s' is still being published. Contact Customer Support Services. 0 0
21631 Cannot unpublish table '%s'; the remote call to the Oracle Publisher failed. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect but the problem persists, drop and reconfigure Oracle publishing. 0 0
21632 The parameter %s is not supported for non-SQL Server publications. The value specified for this parameter must be %s. 0 0
21633 The publication '%s' could not be added because non-SQL Server Publishers only support the @sync_method parameter values "character" or "concurrent_c". 0 0
21634 The parameter %s does not support the value '%s' when using non-SQL Server publications. The value must be %s. 0 0
21635 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. 0 0
21637 %s is required for heterogeneous publications. 0 0
21638 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. 0 0
21639 Heterogeneous publishers can not use trusted connections, set @trusted to false. 0 0
21640 Non-SQL Server Publishers do not support a value of 1 for the parameter @thirdparty_flag. When executing the stored procedure sp_adddistpublisher, specify a value of 0 for the parameter. 0 0
21641 The "%s" parameter is for non-SQL Server Publishers only. It must be NULL for SQL Server Publishers. 0 0
21642 Heterogeneous publishers require a linked server. A linked server named '%s' already exists. Please remove linked server or choose a different publisher name. 0 0
21643 The value specified for the parameter '%s' must be MSSQLSERVER, ORACLE, or ORACLE GATEWAY. 0 0
21644 %s value of '%s' is not supported for heterogeneous subscribers, must be %s. 0 0
21645 The value '%s' is not a valid non-SQL Server Publisher type. For SQL Server 2005, the value must be ORACLE or ORACLE GATEWAY. 0 0
21646 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]. 0 0
21647 The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ensure it is granted the documented permissions. 0 0
21649 Cannot change the property '%s'. Non-SQL Server Publishers do not support this property. 0 0
21650 The value specified for @rowcount_only for the article '%s' is not 1. For an article in a publication from a non-SQL Server Publisher, 1 is the only valid setting for this parameter. 0 0
21651 Failed to execute the HREPL.%s request to Oracle Publisher '%s'. Verify that the Oracle package code exists on the Publisher, and that the replication administrative user account has sufficient permissions. 0 0
21653 The database management system (DBMS) %s %s does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms. 0 0
21654 The data type %s does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings. 0 0
21655 The data type %s already exists. 0 0
21656 The data type mapping for %s does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings. 0 0
21657 The data type mapping for %s already exists. 0 0
21658 The data type mapping does not exist. Verify the list of mappings by querying msdb.dbo.sysdatatypemappings. 0 0
21659 Cannot execute this procedure for a SQL Server Publisher. The Publisher must be a non-SQL Server Publisher. 0 0
21660 The value specified for the parameter @full_or_fast for article '%s' must be 0, 1, or 2. 0 0
21661 The value specified for the @shutdown_agent parameter for article '%s' must be 0 or 1. 0 0
21662 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. 0 0
21663 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. 0 0
21664 Index [%s] contains unique nullable column. 0 0
21665 Key [%s] contains unique nullable column. 0 0
21666 Cannot specify more than %d column names for the index or primary key because this exceeds the maximum number of columns supported by SQL Server. %d columns were specified. 0 0
21667 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. 0 0
21668 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. 0 0
21669 Column [%s] cannot be published because it uses an unsupported data type [%s]. View supported data types by querying msdb.dbo.sysdatatypemappings. 0 0
21670 Connection to server [%s] failed. 0 0
21671 Cannot execute the procedure. Administration of a non-SQL Server Publisher must be performed at the associated SQL Server Distributor. Execute the procedure at the Distributor. 0 0
21672 The login '%s' has insufficient authorization to execute this command. 0 0
21673 Test connection to publisher [%s] failed. Verify authentication information. 0 0
21674 Unable to update the linked server [%s] for the login [%s]. 0 0
21675 Cannot specify more than %d indexes for a single table. %d indexes specified. Excess indexes have been ignored. 0 0
21676 Heterogeneous subscriber '%s' could not add a subscription for heterogeneous publication '%s' because publication sync method is not 'character', 'concurrent_c', or 'database snapshot character'. 0 0
21677 Heterogeneous publisher '%s' cannot be defined as a subscriber. 0 0
21678 The parameter "%s" can be set to "%s" only when "%s" is set to "%s". 0 0
21679 Peer-to-peer publications only support a '%s' parameter value of %s. 0 0
21680 The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %s, OriginatorDB %s, OriginatorDBVersion %d, OriginatorPublicationID %d. Stop and restart the Distribution Agent. If the problem persists, contact Customer Support Services. 0 0
21681 The current user '%s' does not have a valid linked server login mapping for non-SQL Server Publisher [%s]. Replication connects to the Publisher through a linked server; use the stored procedure sp_addlinkedsrvlogin to map the user's login to this linked server. 0 0
21682 Cannot publish table [%s].[%s]. The replication administraive user requires an explicit SELECT grant, or a SELECT grant through PUBLIC, in order to publish this table. A role-based SELECT grant, if one exists, is not sufficient. 0 0
21683 Cannot verify administrator login privileges for Oracle Publisher %s. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. 0 0
21684 The replication administrative user for Oracle Publisher "%s" has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql for the required permissions. 0 0
21685 Request '%s' for Oracle schema filter for Oracle publisher '%s' failed. 0 0
21686 The operation "%s" is not valid. Valid operations are "add", "drop", and "help". 0 0
21687 Schema filters are supported only for Oracle Publishers. The Publisher "%s" is a "%s" Publisher. 0 0
21688 The current login '%s' is not in the publication access list (PAL) of any publication at Publisher '%s'. Use a login that is in the PAL, or add this login to the PAL. 0 0
21689 A NULL @schema value is invalid for add and drop schema filter operations. 0 0
21690 The subscriber db cannot be the same as the publisher db when the subscriber is the same as the publisher 0 0
21691 sp_mergesubscription_cleanup should be called on the subscription database 0 0
21692 Failed to script the subscriber stored procedures for article '%s' in publication '%s' 0 0
21694 %s cannot be null or empty when %s is set to 0 (SQL Server Authentication). Specify a login or set security mode to 1 (Windows Authentication). 0 0
21695 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. 0 0
21696 The stored procedure only applies to Oracle Publishers. The Publisher '%s' is a %s Publisher. 0 0
21698 The parameter '%s' is no longer supported. 0 0
21699 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. 0 0
21701 Microsoft SQL Server Additive Conflict Resolver 0 0
21702 Microsoft SQL Server Averaging Conflict Resolver 0 0
21703 Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver 0 0
21704 Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver 0 0
21705 Microsoft SQL Server Download Only Conflict Resolver 0 0
21706 Microsoft SQL Server Maximum Conflict Resolver 0 0
21707 Microsoft SQL Server Merge Text Columns Conflict Resolver 0 0
21708 Microsoft SQL Server Minimum Conflict Resolver 0 0
21709 Microsoft SQL Server Priority Column Resolver 0 0
21710 Microsoft SQL Server Subscriber Always Wins Conflict Resolver 0 0
21711 Microsoft SQL Server Upload Only Conflict Resolver 0 0
21712 Microsoft SQLServer Stored Procedure Resolver 0 0
21715 Cannot register the article resolver %s. This can occur if the account under which SQL Server is running does not have access to the distribution database. Add the class ID and the custom resolver name manually to the MSmerge_articleresolver table in the distribution database. 0 0
21717 The article resolver name cannot be an empty string or NULL. Specify a valid value for the @article_resolver parameter. 0 0
21718 For a COM resolver, the @resolver_clsid cannot be an empty string or NULL. Specify a valid value for @resolver_clsid. 0 0
21719 The Subscriber '%s':'%s' was not marked for reinitialization at the Publisher because the subscription is either anonymous or not valid. Verify that valid values were specified for the @subscriber and @subscriber_db parameters of sp_reinitmergesubscription. 0 0
21720 Cannot find a job that matches the ID or name specified in the parameters @dynamic_snapshot_jobid or @dynamic_snapshot_jobname. Verify the values specified for those parameters. 0 0
21721 UserScripts 0 0
21722 Failed to add an extended trigger for replicating the '%.*ls' event. 0 0
21723 The value specified for the @pubid parameter of procedure '%s' is not valid or is NULL. Verify that the Merge Agent is running correctly. Reinitalize the subscription if the problem persists. 0 0
21724 Cannot add the foreign key %s with the CASCADE option because table %s is published. Add the NOT FOR REPLICATION clause to the foreign key definition. 0 0
21725 Cannot alter the view. An indexed view replicated as a table cannot be altered to a nonindexed view. Drop the view from the publication before attempting to alter it. 0 0
21727 Cannot complete the replication operation. The security check for the current user is failing. Only members of the sysadmin fixed server role, or db_owner or db_ddladmin fixed database roles can perform this operation. 0 0
21728 The article can support logical record level conflict detection only if it uses logical record conflict resolution. 0 0
21729 The @keep_partition_changes property cannot be set to "true." This is because the @publication_compatibility_level property is set to 90RTM or higher and the @use_partition_groups property is set to "true." Set a lower compatibility level or set the @use_partition_groups property to "false." 0 0
21730 Table '%s' can not be replicated because it contains imprecise Primary Key column, please recreate table without 'persisted' clause and try again. 0 0
21731 Cannot add a constraint or default without an explicit name, because the table is included in a publication that replicates DDL events. Specify a unique name for the constraint and then reissue the DDL statement. 0 0
21732 Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parameter '%s'. 0 0
21733 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. 0 0
21734 Peer-to-peer publications do not support replicating timestamp columns as varbinary(8). You cannot add an article with this option, nor add or alter a table to include a timestamp column as varbinary(8). 0 0
21735 Source object [%s].[%s] is a temporary object and cannot be published. 0 0
21736 Unable to relocate the article log table to a different tablespace. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect, but the problem persists, it might be caused by insufficient permissions or insufficient space in the tablespace; check for any Oracle error messages. 0 0
21737 The property '%s' is not valid for '%s' Publishers. 0 0
21738 The property '%s' is not valid for %s publications. 0 0
21739 Cannot alter property '%s'. You must first call the stored procedure sp_articleview to initialize the article; the property can then be altered. 0 0
21740 Oracle subscriber '%s' not found. Loopback support cannot be checked. 0 0
21741 Unable to retrieve distributor information from Oracle publisher '%s'. Bi-directional publishing requires Oracle publisher to exist before the Oracle subscriber. 0 0
21742 The Oracle Publisher name is '%s' and the Oracle Subscriber name is '%s'. Bidirectional Oracle publishing requires the Oracle Publisher and Subscriber names to be the same. 0 0
21743 Unable to retrieve the originator information for the Oracle subscriber '%s'. 0 0
21744 Oracle bidirectional publishing requires parameter '%s' to have a value of '%s'. 0 0
21745 Cannot generate a filter view or procedure. Verify that the value specified for the @filter_clause parameter of sp_addarticle can be added to the WHERE clause of a SELECT statement to produce a valid query. 0 0
21746 The '%s' character length must not exceed %d. 0 0
21747 Cannot establish a connection to the Oracle Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. 0 0
21748 The article was dropped at the Distributor, but information at the Publisher '%s' was not dropped. No action is required; the information is cleaned up if the Publisher is dropped. 0 0
21749 The Publisher was dropped at the Distributor, but information on the Publisher '%s' was not dropped. Connect to the Oracle Publisher with SQL*PLUS and drop the replication administrative user. 0 0
21750 The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table. 0 0
21751 Cannot publish view %s as a table because it does not have a unique clustered index. Publish the view as a view, or add a unique clustered index. 0 0
21752 The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber that have updates pending in the queue. 0 0
21753 The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ensure your queued subscriptions are properly initialized by running the Snapshot Agent, Distribution Agent, and Queue Reader Agent. 0 0
21754 Processing has been terminated. The resultset for sp_getqueuedrows is larger than 16,000, the maximum size that the procedure can return. Run the Queue Reader Agent to flush the queue at the Subscriber before executing this procedure again. 0 0
21755 Failed to mark '%s' as a system object. 0 0
21756 Based on article settings, table %s should have an identity column, but it does not have one. Verify article settings with sp_helparticle and change them if necessary with sp_changearticle. 0 0
21757 The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, but a value of 'read-only' was specified for the @update_mode parameter of sp_addsubscription. To allow updates, you must drop and then re-create the subscription, specifying a different value for @update_mode. 0 0
21758 Cannot find a valid Queue Reader Agent ID for the subscription to Publisher %s, database %s, publication %s. The specified subscription to an updating Subscriber publication is not initialized. Run the Snapshot Agent, Distribution Agent, and Queue Reader Agent to initialize the subscription. 0 0
21759 Cannot add the column '%s' to the table '%s'. The table already contains the maximum number of columns allowed for an article in a merge publication (246 columns). 0 0
21760 Cannot execute the replication script in the 'master' database; the current session will be terminated. The script must be executed in the distribution database, and the master database cannot serve as the distribution database. 0 0
21761 Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the script. 0 0
21762 The distribution database '%s' has a compatibility level of %d, which is different from that of the master database. The two compatibility levels must be the same, so the distribution database level is being changed to %d. This is an informational message only. No user action is required. 0 0
21763 Message Queuing Service is not running. Start this service and retry the operation. 0 0
21764 Cannot create the publication. Specifying a value of 'msmq' for the parameter @queue_type is supported only on Microsoft Windows NT platforms. Specify a value of 'sql' for this parameter. 0 0
21765 The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow NULLs for updating subscribers. 0 0
21766 Table %s contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter of sp_addarticle is set to 'none'. To support immediate updating subscriptions, specify a value of 'manual' or 'auto' for @identitymanagementoption. 0 0
21767 Warning: The parameter '%s' is obsolete and is available only for backwards compatibility. It will not be available in future releases. Instead of this parameter, use the parameter '%s'. 0 0
21768 When executing sp_adddistributor for a remote Distributor, you must use a password. The password specified for the @password parameter must be the same when the procedure is executed at the Publisher and at the Distributor. 0 0
21769 Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, errors will likely occur when moving data from the Publisher to the Subscriber. 0 0
21770 Data type mapping from '%s' to '%s' does not exist. Review source and destination data type, length, precision, scale, and nullability. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings. 0 0
21771 %s is not within the supported range of %d and %d. 0 0
21772 Property "%s" requires the parameters @force_invalidate_snapshot and @force_reinit_subscription to be set to "true". 0 0
21773 The distribution database '%s' cannot be opened due to inaccessible files. The database will be dropped, but distribution database cleanup tasks will not occur. Check the database and server error logs for more information about why the database files cannot be accessed. 0 0
21774 This procedure is supported only for non-SQL Server Publishers. The Publisher '%s', on which you are executing the procedure, is a SQL Server Publisher. 0 0
21775 Failed to generate column bitmap for article '%s'. 0 0
21776 Failed to generate published column bitmap for article '%s'. 0 0
21777 Failed to generate article view name for article '%s'. 0 0
21778 Cannot add Publisher objects to the Oracle Publisher for article '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions. 0 0
21779 Cannot use the specified data type mapping. The matching destination data type for source type %s cannot be found. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings. Verify that the length, precision, scale, and nullability of the source type are correct. 0 0
21780 The non-SQL Server Publisher is missing one or more %s objects. Drop and re-create the Publisher and the replication administrative user schema. 0 0
21781 Unable to retrieve heterogeneous metadata. Verify connection information 0 0
21782 Cannot add primary key column '%s' to article '%s'. If the Publisher is a non-SQL Server Publisher, the primary key could have violated SQL Server limits for number and length of columns. For more information, see errors returned by sp_addarticle. 0 0
21783 Cannot add the Publisher triggers and the article log table to the Oracle Publisher for the article '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions. 0 0
21784 You must specify a non-NULL value for the @rowfilter parameter. 0 0
21785 Failure to query Oracle XactSet Job attributes for publisher '%s'. 0 0
21786 Failure to refresh Oracle XactSet Job for publisher '%s'. 0 0
21787 Failure to query Oracle Xact batching enabled flag for publisher '%s'. 0 0
21788 Invalid parameter passed to sp_IHSetXactBatching. The bit flag to enable/disable Xact batching must be 0 or 1. 0 0
21789 Failure to set the Oracle Xact batching enabled flag for publisher '%s'. 0 0
21790 Cannot publish the table '%s.%s' from the Publisher '%s'. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions. 0 0
21791 The table '%s.%s' already appears in a transactional publication on Oracle Gateway Publisher '%s'. When using the Oracle Gateway option, a table published using transactional replication can only be included in one publication. To publish this table in more than one publication, you must reconfigure the Oracle Publisher to use the Oracle Complete option. 0 0
21792 The table '%s.%s' already appears in the transactional publication '%s' on Publisher '%s'. The Oracle Gateway publishing option (the default) allows a table to be included as an article in any number of snapshot publications, but only in one transactional publication. To publish a table in more than one transactional publication, use the Oracle Complete publishing option. To change publishing options, you must drop and reconfigure the Publisher. 0 0
21793 Non-SQL Server Publishers are supported only in the Enterprise and Developer editions of SQL Server. The edition of this instance is %s. 0 0
21794 The value specified for the @propertyname parameter is not valid. Use one of the following values: %s. 0 0
21795 The value specified for property %s is not valid. Use one of the following values: %s. 0 0
21796 The property "xactsetjobinterval" must be assigned a value greater than or equal to 0. 0 0
21797 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'. 0 0
21798 Cannot execute the replication administrative procedure. The '%s' agent job must be added through '%s' before continuing. See the documentation for '%s'. 0 0
21799 The %s agent for Publisher (%s), database (%s), publication (%s) cannnot be found. Create the agent with the appropriate procedure: sp_addpublication_snapshot, sp_addlogreader_agent, or sp_addqreader_agent. 0 0
21800 The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. 0 0
21801 The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. Check for any errors returned by sp_createagentparameter and errors returned by SQL Server during execution of sp_createagentparameter. 0 0
21802 The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value must be an integer less than or equal to '%d'. Verify that replication is installed properly. 0 0
21803 Cannot update agent parameter metadata. Replication could not insert parameter '%s' into table '%s'. Verify that replication is properly installed. Check errors returned by SQL Server during execution of sp_createagentparameter. 0 0
21804 The value '%d' specified for the @agent_type parameter of sp_getagentparameterlist is not valid. Specify a valid value of 1, 2, 3, 4, or 9. 0 0
21805 The agent profile creation process cannot validate the specified agent parameter value. '%s' is not a valid value for the '%s' parameter. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value. 0 0
21806 The agent profile creation process cannot validate the specified agent parameter value: the profile_id %d does not exist or it does not support the parameter %s. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value. 0 0
21807 For a .NET Assembly Business Logic Handler, the @resolver_clsid must be specified as NULL. 0 0
21808 For a .NET Assembly Business Logic Handler, the @resolver_info must contain the class name in '%s' that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface. 0 0
21809 DDL replication is not enabled for database '%ls' because its compatibility level is less than 80. 0 0
21810 Identity column can only be added to a published table with 'Not For Replication' clause 0 0
21811 Cannot drop the column '%s' because it is used by replication: it is referenced in a filter or view by article '%s'. To drop the column, you must first remove the filter from the article. 0 0
21812 Cannot perform "Disable Trigger All" on table %s because it belongs to a publication that supports updatable subscriptions (replication adds triggers to tables for these types of publications). You may, however, disable user triggers individually. Specify an individual user trigger name to disable. 0 0
21813 Can not disable trigger %s on table %s because it is required by updatable publication. 0 0
21814 DDL replication failed to refresh custom procedures, please run "exec sp_register_custom_scripting 'CUSTOM_SCRIPT', your_script, '%s', '%s' "and try again 0 0
21815 Can not alter replicated object '%s' to 'with encrypted'. 0 0
21816 An invalid value was specified for parameter '%s'. The value must be '%s' when changing this property. 0 0
21817 The property '%s' is only valid for push subscriptions. 0 0
21818 The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, see the "sp_addsubscriber" documentation. 0 0
21819 Cannot change the property '%s' . This property is only valid for subscriptions that allow updating at the Subscriber. The subscription against which the procedure was called does not allow updates at the Subscriber. 0 0
21820 Cannot write to the script file in the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available. Also ensure that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories. 0 0
21821 Specify one and only one of the parameters - %s or %s. 0 0
21822 Cannot perform %s on %s as entry already exists. 0 0
21823 Cannot perform %s on %s as entry does not exist. 0 0
21824 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. 0 0
21825 Can not drop constraints in the same DDL statement which drops columns from table %s because the table is published, please use separate DDL statement. 0 0
21826 The property '%s' is valid only for %s subscriptions. Use '%s' for %s subscriptions. 0 0
21827 The %s parameters have been deprecated and should no longer be used. For more information, see the '%s' documentation. 0 0
21828 The proxy account for jobstep_uid (%s) could not be found. 0 0
21830 You cannot specify schema_option 0x4 (script identity as identity rather than the base data type) for article '%s'. The value specified for the parameter @identityrangemanagementoption is NONE. To replicate identity as identity, the value must be MANUAL or AUTO for publications that do not support queued updating subscriptions. 0 0
21831 The %s already exists. Use '%s' to change any settings/properties. 0 0
21832 Only members of the sysadmin fixed server role can perform this operation without specifying %s. 0 0
21833 An error occurred when creating a trace event at Oracle publisher '%s'. The trace event could not be posted. 0 0
21834 The primary key for '%s.%s' has %d columns. SQL Server supports a maximum of %d columns. Redefine the primary key so that it has no more than the maximum number of columns. 0 0
21835 The index for the primary key '%s.%s' is at least %d bytes. SQL Server supports a maximum key length of %d bytes. Reduce the number of columns in the primary key or redefine the columns to use smaller data types. 0 0
21836 The distribution agent must be run in single subscription stream mode prior to resetting the subscription xact_seqno. 0 0
21837 A replication agent job (%s) for this subscription already exists. 0 0
21838 The %s parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling '%s'. 0 0
21839 Article '%s' can not support schema_option 0x20 or 0x2000000000 because it contains computed column, check/default constraint or primary key which is based on CLR type column, change @schema_option setting and try again. 0 0
21840 Can not add CLR type based computed column or check constraint to table '%s' because article '%s' supports schema_option 0x20. 0 0
21841 DDL replication is forcing reinitialization because either publication'%s' uses character mode bcp, or timestamp/identity column is being replicated as base type only for article '%s'. 0 0
21842 %s can only be specified/changed for heterogeneous publications when %s is set to %s. 0 0
21843 Article '%s' can not be added, an indexed view published as 'indexed view logbased' and a stored procedure in either form of 'proc exec' can not be published if their common base table is also published. 0 0
21844 Can not alter XML, CLR type or MAX type column because table is published and article '%s' supports the schema option to map this to a base column type. 0 0
21845 Can not alter procedure '%s' to depend on an indexed view published as 'indexed view logbased' or a base table because the indexed view depends on this table as well. 0 0
21846 Cannot find a distribution agent job for the specified transactional or snapshot push subscription. 0 0
21847 Cannot find a merge agent job for the specified merge push subscription. 0 0
21848 The specified pull subscription is not configured with a synchronization agent job. 0 0
21850 The property "%s" cannot be changed to "%s" after the value has already been set to "%s". 0 0
21851 Peer-to-peer publications only support a "%s" value of %s. Article "%s" currently has a "%s" value of %s. This value must be changed to continue. 0 0
21852 Peer-to-peer publications do not support %s. Article "%s" currently has %s. This must be changed to continue. 0 0
21853 Warning: The "%s" property for %s "%s" has been changed to "%s" because it is required by %s. 0 0
21854 Could not add new article to publication '%s' because of active schema change activities or a snapshot is being generated. 0 0
21855 The login %s provided in sp_link_publication is not mapped to any user in publishing database %s. 0 0
21856 For a .NET Assembly Business Logic Handler, the .NET Assembly name should be the name of a valid assembly in '%s' that contains the class that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface. Check the registration of the business logic handler to make sure the .NET Assembly name was specified correctly. 0 0
21857 Forcing re-initialization for article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore process, please re-create the index and re-sync your data. 0 0
21858 Snapshot can not process article '%s' in publication '%s', the clustered index on indexed view '%s' may have been dropped by upgrade or restore process, please re-create the index and re-run snapshot. 0 0
21859 Cannot change subscription property '%s' because there is no entry for this subscription in the MSsubscription_properties table. Call sp_addmergepullsubscription_agent before changing this property. 0 0
21860 Table '%s' in database '%s' is subscribing to transactional queued publication and published for merge for uploading changes, this may cause non-convergence between transactional publisher and subscriber. 0 0
21861 The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated. 0 0
21862 FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or 'database snapshot character'. 0 0
21863 Cannot add the SPARSE property to a column for the article '%s' because merge replication does not support sparse columns. 0 0
21864 Cannot publish the article '%s' or add the COLUMN_SET attribute set to its base table '%s' because replication does not support column sets. 0 0
21865 The '%s' publication property must be either 'true' or 'false'. 0 0
21866 The publication property '%s' can only be set to '%s' when the publication property '%s' is set to '%s'. 0 0
21867 ALTER TABLE SWITCH statement failed. The table '%s' belongs to a publication which does not allow switching of partitions 0 0
21868 ALTER TABLE SWITCH statement failed. The statement is not allowed because one or more of the tables in this statement is an article with a different destination table or owner. 0 0
21869 Cannot add filter between proposed parent article '%s' and proposed child article '%s' since this would introduce a cycle in the filter relationships. The proposed parent is already being filtered by the child. 0 0
13001 file name 0 0
13002 audit 0 0
13003 audit specification 0 0
13004 audit name 0 0
13008 receive 0 0
13010 read 0 0
13012 a USE database statement 0 0
13013 a procedure, function or trigger 0 0
13014 indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations 0 0
13015 spatial index operations 0 0
13016 an INTO clause 0 0
13018 a COMPUTE clause 0 0
13019 a SELECT INTO statement 0 0
13020 option 0 0
13021 offset option 0 0
13022 statistics option 0 0
13024 function name 0 0
13025 varbinary (128) NOT NULL 0 0
13026 parameter 0 0
13027 convert specification 0 0
13028 index 0 0
13029 table 0 0
13030 database 0 0
13031 procedure 0 0
13032 trigger 0 0
13033 view 0 0
13034 default 0 0
13035 rule 0 0
13036 system table 0 0
13037 unknown type 0 0
13038 SET option 0 0
13039 column 0 0
13040 type 0 0
13041 character string 0 0
13042 integer 0 0
13043 identifier 0 0
13044 number 0 0
13045 indexes 0 0
13047 object 0 0
13049 built-in function name 0 0
13050 aggregate function 0 0
13051 XML INDEX 0 0
13052 CLR type 0 0
13053 xml schema collection 0 0
13054 EXTENDED INDEX 0 0
13055 SPATIAL INDEX 0 0
13056 spatial 0 0
13057 a planguide batch 0 0
13058 geometry 0 0
13059 conversation priority 0 0
13076 an assignment 0 0
13077 a cursor declaration 0 0
13078 replication filter 0 0
13079 variable assignment 0 0
13080 statistics 0 0
13081 file 0 0
13082 filegroup 0 0
13083 server 0 0
13084 write 0 0
13085 function 0 0
13086 database collation 0 0
13087 drop 0 0
13088 alter 0 0
13089 message type 0 0
13090 contract 0 0
13092 service 0 0
13093 queue 0 0
13094 table valued function 0 0
13095 event notification 0 0
13096 synonym 0 0
13097 lock 0 0
13098 thread 0 0
13099 communication buffer 0 0
13100 Common Language Runtime critical section 0 0
13101 partition scheme 0 0
13102 DETACH 0 0
13103 HASH 0 0
13104 RANGE 0 0
13105 create 0 0
13106 route 0 0
13107 remote service binding 0 0
13108 Initiator 0 0
13109 Target 0 0
13110 host synchronization object 0 0
13111 generic waitable object 0 0
13112 application role 0 0
13113 schema 0 0
13114 user 0 0
13115 login 0 0
13116 certificate 0 0
13117 role 0 0
13118 find 0 0
13119 endpoint 0 0
13120 sql:variable 0 0
13121 sql:column 0 0
13122 XML namespace 0 0
13123 assembly 0 0
13124 fulltext catalog 0 0
13125 execute as 0 0
13126 symmetric key 0 0
13127 principal 0 0
13128 security descriptor 0 0
13129 hypothetical index 0 0
13130 nonclustered index 0 0
13131 credential 0 0
13132 transfer 0 0
13133 Cumulative wait time (ms) per second 0 0
13134 Waits started per second 0 0
13135 Waits in progress 0 0
13136 Average wait time (ms) 0 0
13137 Cumulative execution time (ms) per second 0 0
13138 Execs started per second 0 0
13139 Execs in progress 0 0
13140 Average execution time (ms) 0 0
13141 asymmetric key 0 0
13142 an INSERT SELECT statement 0 0
13143 partition function 0 0
13144 partition scheme 0 0
13145 encryption 0 0
13146 signature 0 0
13147 password 0 0
13148 rename 0 0
13149 end dialog 0 0
13150 END CONVERSATION WITH ERROR 0 0
13151 MOVE CONVERSATION 0 0
13152 receive sequenced message 0 0
13153 receive end conversation 0 0
13154 receive end conversation with error 0 0
13155 receive broker error 0 0
13156 receive message acknowledgement 0 0
13157 terminate conversation 0 0
13158 broker error 0 0
13159 countersignature 0 0
13160 BEGIN CONVERSATION TIMER 0 0
13161 fire conversation timer 0 0
13162 END CONVERSATION WITH CLEANUP 0 0
13163 BEGIN DIALOG CONVERSATION 0 0
13164 SEND 0 0
13165 conversation 0 0
13166 conversation group 0 0
13167 system 0 0
13168 Service Broker 0 0
13169 Database Mirroring 0 0
13170 table or indexed view 0 0
13171 conversation handle 0 0
13172 GET CONVERSATION GROUP 0 0
13173 master key 0 0
13174 another assembly with same SQL name is already present in the current database 0 0
13175 version, culture or public key mismatch 0 0
13176 component 0 0
13177 IL compilation 0 0
13178 Inproc data access 0 0
13179 DDL operations 0 0
13180 execution cache cleanup 0 0
13181 unspecified operation 0 0
13182 dialog 0 0
13183 The certificate's private key cannot be found 0 0
13184 The certificate's private key size is incompatible with the crypto provider 0 0
13185 The certificate's public key size is incompatible with the crypto provider 0 0
13186 The certificate's private key size is incompatible with the encrypted key exchange key 0 0
13187 The certificate's public key size is incompatible with the security header's signature 0 0
13188 The certificate's private key is password protected 0 0
13189 The key exchange key has an invalid size after being decrypted with the certificate private key 0 0
13190 The database principal used to lookup the cert is invalid 0 0
13191 The database principal has no mapping to a server principal 0 0
13192 The certificate is disabled for BEGIN DIALOG 0 0
13193 encryption algorithm 0 0
13194 authentication protocol 0 0
13195 Certificate not found 0 0
13196 Certificate not yet valid 0 0
13197 Certificate expired 0 0
13198 Certificate is larger than maximum allowed size 0 0
13199 message timestamp 0 0
13202 TO BROKER INSTANCE 0 0
13203 TO SERVICE 0 0
13204 FROM BROKER INSTANCE 0 0
13205 FROM SERVICE 0 0
13206 SERVICE CONTRACT 0 0
13207 MESSAGE TYPE 0 0
13208 MESSAGE INTEGRITY CHECK 0 0
13209 KEY SALT 0 0
13210 SESSION KEY 0 0
13211 KEY EXCHANGE KEY 0 0
13212 SOURCE CERTIFICATE ISSUER NAME 0 0
13213 SOURCE CERTIFICATE SERIAL NUMBER 0 0
13214 DESTINATION CERTIFICATE ISSUER NAME 0 0
13215 DESTINATION CERTIFICATE SERIAL NUMBER 0 0
13216 SECURITY HEADER SIGNATURE 0 0
13217 MESSAGE BODY 0 0
13218 STATEMENT 0 0
13219 clustered index 0 0
13220 primary xml index 0 0
13221 Failover 0 0
13222 Auto Failover 0 0
13223 Failover from partner 0 0
13224 Role Synchronization 0 0
13225 Force_Service_Allow_Data_Loss 0 0
13226 add 0 0
13227 to 0 0
13228 from 0 0
13229 enable 0 0
13230 disable 0 0
13231 remap 0 0
13232 INSERT 0 0
13233 UPDATE 0 0
13234 DELETE 0 0
13235 WHEN MATCHED 0 0
13236 WHEN NOT MATCHED 0 0
13237 WHEN NOT MATCHED BY SOURCE 0 0
13238 TOP 0 0
13239 GROUP BY 0 0
13240 HAVING 0 0
13241 ORDER BY 0 0
13242 COMPUTE 0 0
13243 OUTPUT INTO 0 0
13244 SELECT 0 0
13245 WHERE 0 0
13246 unexpected 0 0
13254 event 0 0
13255 target 0 0
13256 event action 0 0
13257 event session 0 0
13258 event package 0 0
13259 event object 0 0
13260 event predicate comparator 0 0
13261 event attribute or predicate source 0 0
13262 customizable attribute 0 0
13263 event predicate 0 0
13264 predicate source 0 0
13265 event attribute 0 0
13266 partitioned 0 0
13267 not partitioned 0 0
13268 resource pool 0 0
13269 workload group 0 0
13270 resource governor 0 0
13271 move 0 0
13272 UPDATETEXT 0 0
13273 WRITETEXT 0 0
13274 torn page (expected signature: 0x%08x; actual signature: 0x%08x) 0 0
13275 incorrect checksum (expected: 0x%08x; actual: 0x%08x) 0 0
13276 invalid protection option 0 0
13277 invalid encryption key 0 0
13278 unable to decrypt page 0 0
13279 decryption failure (expected: 0x%08x; actual: 0x%08x) 0 0
13280 unable to decrypt page due to missing DEK 0 0
13281 CREATION_DISPOSITION 0 0
13282 PROVIDER_KEY_NAME 0 0
13283 key source 0 0
13284 ENCRYPTION BY 0 0
13285 public key 0 0
13286 private key 0 0
13287 cryptographic provider 0 0
13288 cryptographic provider DLL path 0 0
13289 cryptographic provider friendly name 0 0
13290 version 0 0
13291 guid 0 0
13292 create credential for 0 0
13293 cryptographic provider key name 0 0
13294 key persistence 0 0
13295 cryptographic provider key thumbprint length 0 0
13296 cryptographic provider key blob length 0 0
13297 encryption algorithm tag 0 0
13298 name 0 0
13299 thumbprint 0 0
13301 IV(Initialization Vector) length 0 0
13302 bit length 0 0
13303 constraint 0 0
13373 Anchor record 0 0
13374 Page dictionary 0 0
13375 Compression information structure 0 0
13376 Fulltext Query String 0 0
13377 Fulltext Query Language 0 0
13378 Fulltext Query Max Keys 0 0
13379 fulltext stoplist 0 0
13380 Success - Consult EKM Provider for details 0 0
13381 Failure - Consult EKM Provider for details 0 0
13382 Insufficient Buffer - Consult EKM Provider for details 0 0
13383 Not Supported - Consult EKM Provider for details 0 0
13384 Object Not Found - Consult EKM Provider for details 0 0
13385 Authentication Failure - Consult EKM Provider for details 0 0
13386 Invalid Argument - Consult EKM Provider for details 0 0
13387 Provider Error - No explanation is available, consult EKM Provider for details 0 0
13388 Key Flags 0 0
13389 Key Name 0 0
13390 Key Type 0 0
13400 Extended stored procedure API will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
13401 Non-ANSI '*=' and '=*' outer join operators will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use ANSI outer joins instead. 0 0
13402 The ability to INSERT NULL values into TIMESTAMP columns will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use DEFAULT instead. 0 0
13403 The ability to use string literals as column aliases will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use AS clause instead. 0 0
13404 The ability to use ' 0 1
13405 The ability to use '@' and names that start with '@@' as Transact-SQL identifiers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
13406 The ability to use the DEFAULT keyword as a default value will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
13407 FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use OPTION (FAST n) instead. 0 0
13408 %ls will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
13409 Collation '%ls' will be removed in a future version of SQL Server. Avoid using this collation in new development work, and plan to modify applications that currently use it. 0 0
-1 An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1). 0 0
-2 Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2). 0 0
2 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server ) (.Net SqlClient Data Provider) 0 0
21 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. 0 0
53 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server ) (.Net SqlClient Data Provider). 0 0
101 Query not allowed in Waitfor. 0 0
102 Incorrect syntax near '%.*ls'. 0 0
103 The %S_MSG that starts with '%.*ls' is too long. Maximum length is %d. 0 0
104 ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator. 0 0
105 Unclosed quotation mark after the character string '%.*ls'. 0 0
106 Too many table names in the query. The maximum allowable is %d. 0 0
107 The column prefix '%.*ls' does not match with a table name or alias name used in the query. 0 0
108 The ORDER BY position number %ld is out of range of the number of items in the select list. 0 0
109 There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 0 0
110 There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 0 0
111 '%ls' must be the first statement in a query batch. 0 0
112 Variables are not allowed in the %ls statement. 0 0
113 Missing end comment mark '*/'. 0 0
114 Browse mode is invalid for a statement that assigns values to a variable. 0 0
115 The FOR UPDATE clause is invalid for statements containing set operators. 0 0
116 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. 0 0
117 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. 0 0
119 Must pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters must be passed in the form '@name = value'. 0 0
120 The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns. 0 0
121 The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns. 0 0
122 The %ls option is allowed only with %ls syntax. 0 0
123 Batch/procedure exceeds maximum length of %d characters. 0 0
124 CREATE PROCEDURE contains no statements. 0 0
125 Case expressions may only be nested to level %d. 0 0
126 Invalid pseudocolumn "%.*ls". 0 0
127 A TOP N value may not be negative. 0 0
128 The name "%.*s" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted. 0 0
129 Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. 0 0
130 Cannot perform an aggregate function on an expression containing an aggregate or a subquery. 0 0
131 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d). 0 0
132 The label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure. 0 0
133 A GOTO statement references the label '%.*ls' but the label has not been declared. 0 0
134 The variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure. 0 0
135 Cannot use a BREAK statement outside the scope of a WHILE statement. 0 0
136 Cannot use a CONTINUE statement outside the scope of a WHILE statement. 0 0
137 Must declare the scalar variable "%.*ls". 0 0
138 Correlation clause in a subquery not permitted. 0 0
139 Cannot assign a default value to a local variable. 0 0
140 Can only use IF UPDATE within a CREATE TRIGGER statement. 0 0
141 A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations. 0 0
142 Incorrect syntax for definition of the '%ls' constraint. 0 0
143 A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list. 0 0
144 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. 0 0
145 ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 0 0
146 Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded. 0 0
147 An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference. 0 0
148 Incorrect time syntax in time string '%.*ls' used with WAITFOR. 0 0
149 Time value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax. 0 0
150 Both terms of an outer join must contain columns. 0 0
151 '%.*ls' is an invalid money value. 0 0
152 The same large data placement option "%.*ls" has been specified twice. 0 0
153 Invalid usage of the option %.*ls in the %ls statement. 0 0
154 %S_MSG is not allowed in %S_MSG. 0 0
155 '%.*ls' is not a recognized %ls option. 0 0
156 Incorrect syntax near the keyword '%.*ls'. 0 0
157 An aggregate may not appear in the set list of an UPDATE statement. 0 0
158 An aggregate may not appear in the OUTPUT clause. 0 0
159 Must specify the table name and index name for the DROP INDEX statement. 0 0
160 Rule does not contain a variable. 0 0
161 Rule contains more than one variable. 0 0
162 Invalid expression in the TOP clause. 0 0
163 The compute by list does not match the order by list. 0 0
164 Each GROUP BY expression must contain at least one column that is not an outer reference. 0 0
165 Privilege %ls may not be granted or revoked. 0 0
166 '%ls' does not allow specifying the database name as a prefix to the object name. 0 0
167 Cannot create %S_MSG on a temporary object. 0 0
168 The floating point value '%.*ls' is out of the range of computer representation (%d bytes). 0 0
169 A column has been specified more than once in the order by list. Columns in the order by list must be unique. 0 0
171 Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements. 0 0
172 Cannot use HOLDLOCK in browse mode. 0 0
173 The definition for column '%.*ls' must include a data type. 0 0
174 The %.*ls function requires %d argument(s). 0 0
175 An aggregate may not appear in a computed column expression or check constraint. 0 0
176 The FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement to be allowed. 0 0
177 The IDENTITY function can only be used when the SELECT statement has an INTO clause. 0 0
178 A RETURN statement with a return value cannot be used in this context. 0 0
179 Cannot use the OUTPUT option when passing a constant to a stored procedure. 0 0
180 There are too many parameters in this %ls statement. The maximum number is %d. 0 0
181 Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. 0 0
182 Table and column names must be supplied for the READTEXT or WRITETEXT utility. 0 0
183 The scale (%d) for column '%.*ls' must be within the range %d to %d. 0 0
184 DEFAULT cannot be specified more than once for filegroups of the same content type. 0 0
185 Data stream is invalid for WRITETEXT statement in bulk form. 0 0
186 Data stream missing from WRITETEXT statement. 0 0
187 The valid range for MAX_QUEUE_READERS is 0 to 32767. 0 0
188 Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file. 0 0
189 The %ls function requires %d to %d arguments. 0 0
190 An invalid date or time was specified in the statement. 0 0
191 Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries. 0 0
192 The scale must be less than or equal to the precision. 0 0
193 The object or column name starting with '%.*ls' is too long. The maximum length is %d characters. 0 0
194 A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable. 0 0
195 '%.*ls' is not a recognized %S_MSG. 0 0
196 SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator. 0 0
197 EXECUTE cannot be used as a source when inserting into a table variable. 0 0
198 Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator. 0 0
199 An INSERT statement cannot contain a SELECT statement that assigns values to a variable. 0 0
201 Procedure or function '%.*ls' expects parameter '%.*ls', which was not supplied. 0 0
202 Invalid type '%s' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. 0 0
203 The name '%.*ls' is not a valid identifier. 0 0
204 Normalization error in node %ls. 0 0
205 All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists. 0 0
206 Operand type clash: %ls is incompatible with %ls 0 0
207 Invalid column name '%.*ls'. 0 0
208 Invalid object name '%.*ls'. 0 0
209 Ambiguous column name '%.*ls'. 0 0
210 Conversion failed when converting datetime from binary/varbinary string. 0 0
211 Possible schema corruption. Run DBCC CHECKCATALOG. 0 0
212 Expression result length exceeds the maximum. %d max, %d found. 0 0
213 Column name or number of supplied values does not match table definition. 0 0
214 Procedure expects parameter '%ls' of type '%ls'. 0 0
215 Parameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. 0 0
216 Parameters were not supplied for the function '%.*ls'. 0 0
217 Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d). 0 0
218 Could not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission. 0 0
219 The type '%.*ls' already exists, or you do not have permission to create it. 0 0
220 Arithmetic overflow error for data type %ls, value = %ld. 0 0
221 FIPS Warning: Implicit conversion from %ls to %ls. 0 0
222 The base type "%.*ls" is not a valid base type for the alias data type. 0 0
223 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. 0 0
224 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. 0 0
225 The parameters supplied for the %ls "%.*ls" are not valid. 0 0
226 %ls statement not allowed within multi-statement transaction. 0 0
227 %.*ls is not a valid function, property, or field. 0 0
228 Method '%.*ls' of type '%.*ls' in assembly '%.*ls' does not return any value. 0 0
229 The %ls permission was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'. 0 0
230 The %ls permission was denied on the column '%.*ls' of the object '%.*ls", database '%.*ls', schema '%.*ls'. 0 0
231 No No such default. ID = %ld, database ID = %d. 0 0
232 Arithmetic overflow error for type %ls, value = %f. 0 0
233 The column '%.*ls' in table '%.*ls' cannot be null. 0 0
233 A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) 0 0
234 There is insufficient result space to convert a money value to %ls. 0 0
235 Cannot convert a char value to money. The char value has incorrect syntax. 0 0
236 The conversion from char data type to money resulted in a money overflow error. 0 0
237 There is insufficient result space to convert a money value to %ls. 0 0
239 Duplicate common table expression name '%.*ls' was specified. 0 0
240 Types don't match between the anchor and the recursive part in column "%.*ls" of recursive query "%.*ls". 0 0
241 Conversion failed when converting date and/or time from character string. 0 0
242 The conversion of a %ls data type to a %ls data type resulted in an out-of-range value. 0 0
243 Type %.*ls is not a defined system type. 0 0
244 The conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column. 0 0
245 Conversion failed when converting the %ls value '%.*ls' to data type %ls. 0 0
246 No No anchor member was specified for recursive query "%.*ls". 0 0
247 An anchor member was found in the recursive part of recursive query "%.*ls". 0 0
248 The conversion of the %ls value '%.*ls' overflowed an int column. 0 0
249 The type "%ls" is not comparable. It cannot be used in the %ls clause. 0 0
251 Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded. 0 0
252 Recursive common table expression '%.*ls' does not contain a top-level UNION ALL operator. 0 0
253 Recursive member of a common table expression '%.*ls' has multiple recursive references. 0 0
254 Prefixed columns are not allowed in the column list of a PIVOT operator. 0 0
255 Pseudocolumns are not allowed in the column list of a PIVOT operator. 0 0
256 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. 0 0
257 Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query. 0 0
258 Cannot call methods on %ls. 0 0
259 Ad hoc updates to system catalogs are not allowed. 0 0
260 Disallowed implicit conversion from data type %ls to data type %ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query. 0 0
261 '%.*ls' is not a recognized function. 0 0
262 %ls permission denied in database '%.*ls'. 0 0
263 Must specify table to select from. 0 0
264 The column name '%.*ls' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name '%.*ls' may appear twice in the view definition. 0 0
265 The column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument. 0 0
266 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld. 0 0
267 Object '%.*ls' cannot be found. 0 0
268 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. 0 0
270 Object '%.*ls' cannot be modified. 0 0
271 The column "%.*ls" cannot be modified because it is either a computed column or is the result of a UNION operator. 0 0
272 Cannot update a timestamp column. 0 0
273 Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. 0 0
275 Prefixes are not allowed in value or pivot columns of an UNPIVOT operator. 0 0
276 Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator. 0 0
277 The column "%.*ls" is specified multiple times in the column list of the UNPIVOT operator. 0 0
278 The text, ntext, and image data types cannot be used in a GROUP BY clause. 0 0
279 The text, ntext, and image data types are invalid in this subquery or aggregate expression. 0 0
280 Only base table columns are allowed in the TEXTPTR function. 0 0
281 %d is not a valid style number when converting from %ls to a character string. 0 0
282 The '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. 0 0
283 READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. 0 0
284 Rules cannot be bound to text, ntext, or image data types. 0 0
285 The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions. 0 0
286 The logical tables INSERTED and DELETED cannot be updated. 0 0
287 The %ls statement is not allowed within a trigger. 0 0
288 The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. 0 0
290 Invalid EXECUTE statement using object "%ls", method "%ls". 0 0
291 CAST or CONVERT: invalid attributes specified for type '%.*ls' 0 0
292 There is insufficient result space to convert a smallmoney value to %ls. 0 0
293 Cannot convert char value to smallmoney. The char value has incorrect syntax. 0 0
294 The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. 0 0
295 Conversion failed when converting character string to smalldatetime data type. 0 0
297 The user does not have permission to perform this action. 0 0
300 %ls permission was denied on object '%.*ls', database '%.*ls'. 0 0
301 Query contains an outer-join request that is not permitted. 0 0
302 The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression. 0 0
303 The table '%.*ls' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause. 0 0
304 '%d' is out of range for index option '%.*ls'. See sp_configure option '%ls' for valid values. 0 0
305 The XML data type cannot be compared or sorted, except when using the IS NULL operator. 0 0
306 The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 0 0
307 Index ID %d on table '%.*ls' (specified in the FROM clause) does not exist. 0 0
308 Index '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist. 0 0
309 Cannot use index "%.*ls" on table "%.*ls" in a hint. XML indexes are not allowed in hints. 0 0
310 The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d. 0 0
311 Cannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables. 0 0
312 Cannot reference text, ntext, or image columns in a filter stored procedure. 0 0
313 An insufficient number of arguments were supplied for the procedure or function %.*ls. 0 0
314 Cannot use GROUP BY ALL with the special tables INSERTED or DELETED. 0 0
315 Index "%.*ls" on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 0 0
316 The index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 0 0
317 Table-valued function '%.*ls' cannot have a column alias. 0 0
318 The table (and its columns) returned by a table-valued method need to be aliased. 0 0
319 Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. 0 0
320 The compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal. 0 0
321 %.*ls is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90. 0 0
322 The variable "%.*ls" is specified in the OPTIMIZE FOR clause, but is not used in the query. 0 0
323 The 'COMPUTE' clause is not allowed in a statement containing an INTERSECT or EXCEPT operator. 0 0
324 The 'ALL' version of the %.*ls operator is not supported. 0 0
325 Incorrect syntax near '%.*ls'. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. 0 0
326 Multi-part identifier '%.*ls' is ambiguous. Both columns '%.*ls' and '%.*ls' exist. 0 0
327 Function call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist. 0 0
328 A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables. 0 0
329 Each GROUP BY expression must contain at least one column reference. 0 0
330 The target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression. 0 0
331 The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled triggers. 0 0
332 The target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint '%ls'. 0 0
333 The target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule '%ls'. 0 0
334 The target table '%.*ls' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. 0 0
335 Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name '%.*ls' without parameters instead. 0 0
336 Incorrect syntax near '%.*ls'. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon. 0 0
337 Warning: the floating point value '%.*ls' is too small. It will be interpreted as 0. 0 0
338 READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers. 0 0
339 DEFAULT or NULL are not allowed as explicit identity values. 0 0
340 Cannot create the trigger "%.*ls" on view "%.*ls". AFTER triggers cannot be created on views. 0 0
341 Replication filter procedures may not contain columns of large object, large value, XML or CLR type. 0 0
342 Column "%.*ls" is not allowed in this context, and the user-defined function or aggregate "%.*ls" could not be found. 0 0
343 Unknown object type '%.*ls' used in a CREATE, DROP, or ALTER statement. 0 0
344 Remote function reference '%.*ls' is not allowed, and the column name '%.*ls' could not be found or is ambiguous. 0 0
345 Function '%.*ls' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound. 0 0
346 The parameter "%.*ls" can not be declared READONLY since it is not a table-valued parameter. 0 0
347 The table-valued parameter "%.*ls" cannot be declared as an OUTPUT parameter. 0 0
348 The table variable "%.*ls" can not be passed to a stored procedure with the OUTPUT option. 0 0
349 The procedure "%.*ls" has no parameter named "%.*ls". 0 0
350 The column "%.*ls" does not have a valid data type. A column cannot be of a user-defined table type. 0 0
351 Column, parameter, or variable %.*ls. : Cannot find data type %.*ls. 0 0
352 The table-valued parameter "%.*ls" must be declared with the READONLY option. 0 0
353 Function '%.*ls' is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound. 0 0
354 The target '%.*ls' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
355 The target table '%.*ls' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
356 The target table '%.*ls' of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint '%ls'. 0 0
357 The target table '%.*ls' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule '%ls'. 0 0
358 The target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'. 0 0
359 The target '%.*ls' of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used. 0 0
360 The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both. 0 0
361 The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns. 0 0
401 Unimplemented statement or expression %ls. 0 0
402 The data types %s and %s are incompatible in the %s operator. 0 0
403 Invalid operator for data type. Operator equals %ls, type equals %ls. 0 0
404 The column reference "inserted.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement. 0 0
405 A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement. 0 0
406 %ls cannot be used in the PIVOT operator because it is not invariant to NULLs. 0 0
407 Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x. 0 0
408 A constant expression was encountered in the ORDER BY list, position %i. 0 0
411 COMPUTE clause 0 0
412 The column "%.*ls" is not updatable because it is derived or constant. 0 0
413 Correlated parameters or sub-queries are not supported by the inline function "%.*ls". 0 0
414 UPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger. 0 0
415 DELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger. 0 0
416 The service queue "%.*ls" cannot be directly updated. 0 0
417 TOP is not allowed in an UPDATE or DELETE statement against a partitioned view. 0 0
418 Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'. 0 0
421 The %ls data type cannot be selected as DISTINCT because it is not comparable. 0 0
422 Common table expression defined but not used. 0 0
423 Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls". 0 0
424 Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement. 0 0
425 Data type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'. 0 0
426 The length %d of the receiving variable is less than the length %d of the column '%.*ls'. 0 0
427 Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database. 0 0
428 Insert bulk cannot be used in a multi-statement batch. 0 0
432 Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls". 0 0
434 Function '%ls' is not allowed in the OUTPUT clause. 0 0
435 Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement. 0 0
438 Xml data type methods are not allowed in rules. The error occurred at table "%.*ls". 0 0
440 Internal query compilation error. The stack overflow could not be handled. 0 0
441 Cannot use the '%ls' function on a remote data source. 0 0
442 The NEST argument must be a column reference. Expressions are not allowed. 0 0
443 Invalid use of a side-effecting operator '%s' within a function. 0 0
444 Select statements included within a function cannot return data to a client. 0 0
445 COLLATE clause cannot be used on expressions containing a COLLATE clause. 0 0
446 Cannot resolve collation conflict for %ls operation. 0 0
447 Expression type %ls is invalid for COLLATE clause. 0 0
448 Invalid collation '%.*ls'. 0 0
449 Collation conflict caused by collate clauses with different collation '%.*ls' and '%.*ls'. 0 0
450 Code page translations are not supported for the text data type. From: %d To: %d. 0 0
451 Cannot resolve collation conflict for column %d in %ls statement. 0 0
452 COLLATE clause cannot be used on user-defined data types. 0 0
453 Collation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level. 0 0
454 The UNNEST argument must be a nested table column. 0 0
455 The last statement included within a function must be a return statement. 0 0
456 Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict. 0 0
457 Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict. 0 0
458 Cannot create the SELECT INTO target table "%.*ls" because the xml column "%.*ls" is typed with a schema collection "%.*ls" from database "%.*ls". Xml columns cannot refer to schemata across databases. 0 0
459 Collation '%.*ls' is supported on Unicode data types only and cannot be applied to char, varchar or text data types. 0 0
460 DISTINCT operator is not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
461 TOP operator is not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
462 Outer join is not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
463 Functions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
464 Functions with side effects are not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
465 Recursive references are not allowed in subqueries. 0 0
466 UNION operator is not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
467 GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'. 0 0
468 Cannot resolve the collation conflict between "%.*ls" and "%.*ls" in the %ls operation. 0 0
469 An explicit column list must be specified for target table '%.*ls' when table hint KEEPIDENTITY is used and the table contains an identity column. 0 0
470 The synonym "%.*ls" referenced synonym "%.*ls". Synonym chaining is not allowed. 0 0
471 Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified. 0 0
472 Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified. 0 0
473 The incorrect value "%.*ls" is supplied in the PIVOT operator. 0 0
474 Unable to load the computed column definitions for table "%.*ls". 0 0
475 Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled. 0 0
476 Invalid PERCENT tablesample size "%f" for table "%.*ls". The PERCENT tablesample size must be between 0 and 100. 0 0
477 Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer. 0 0
478 The TABLESAMPLE clause cannot be used in a view definition or inline table function definition. 0 0
479 Invalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0. 0 0
480 The TABLESAMPLE clause cannot be used with the table function "%.*ls". 0 0
481 The TABLESAMPLE clause cannot be used with the linked server table "%.*ls". 0 0
482 Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause. 0 0
483 The OUTPUT clause cannot be used in an INSERT...EXEC statement. 0 0
484 Cannot declare more than %d local variables. 0 0
485 Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column "%.*ls" is typed with the schema collection "%.*ls", which is registered in database "%.*ls". 0 0
486 %.*ls does not allow specifying a schema name as a prefix to the assembly name. 0 0
487 An invalid option was specified for the statement "%.*ls". 0 0
488 %s columns must be comparable. The type of column "%.*ls" is "%s", which is not comparable. 0 0
489 The OUTPUT clause cannot be specified because the target view "%.*ls" is a partitioned view. 0 0
490 The resync functionality is temporarily disabled. 0 0
491 A correlation name must be specified for the bulk rowset in the from clause. 0 0
492 Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate. 0 0
493 The column '%.*ls' that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 0 0
494 The TABLESAMPLE clause can only be used with local tables. 0 0
495 The return table column "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 0 0
496 The parameter "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 0 0
497 Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses. 0 0
498 Invalid value in the TABLESAMPLE or the REPEATABLE clause. 0 0
499 Invalid parameter for the getchecksum function. 0 0
500 Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s). 0 0
505 The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed. 0 0
506 The invalid escape character "%.*ls" was specified in a %ls predicate. 0 0
507 Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer. 0 0
509 User name '%.*ls' not found. 0 0
510 Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint. 0 0
511 Cannot create a row of size %d which is greater than the allowable maximum row size of %d. 0 0
512 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 0 0
513 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'. 0 0
515 Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails. 0 0
517 Adding a value to a '%ls' column caused an overflow. 0 0
518 Cannot convert data type %ls to %ls. 0 0
522 The WAITFOR thread was evicted. 0 0
523 A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active. 0 0
524 A trigger returned a resultset and the server option 'disallow results from triggers' is true. 0 0
525 The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 0 0
526 %ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query. 0 0
527 Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query. 0 0
529 Explicit conversion from data type %ls to %ls is not allowed. 0 0
530 The statement terminated. The maximum recursion %d has been exhausted before statement completion. 0 0
531 Cannot set NOCOUNT to OFF inside the trigger execution because the server option "disallow_results_from_triggers" is true or we are inside LOGON trigger execution. 0 0
532 The timestamp (changed to %S_TS) shows that the row has been updated by another user. 0 0
533 Cannot set XACT ABORT to OFF inside the trigger execution unless the database compatibility is 90. 0 0
534 '%.*ls' failed because it is not supported in the edition of this SQL Server instance '%.*ls'. See books online for more details on feature support in different SQL Server editions. 0 0
535 The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart. 0 0
536 Invalid length parameter passed to the %ls function. 0 0
537 Invalid length parameter passed to the LEFT or SUBSTRING function. 0 0
539 Schema changed after the target table was created. Rerun the Select Into query. 0 0
540 There is insufficient system memory to run RAISERROR. 0 0
541 There is not enough stack to execute the statement 0 0
542 An invalid datetime value was encountered. Value exceeds the year 9999. 0 0
543 Creation of a return table failed for the table valued function '%.*ls'. 0 0
544 Cannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF. 0 0
545 Explicit value must be specified for identity column in table '%.*ls' either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column. 0 0
547 The %ls statement conflicted with the %ls constraint "%.*ls". The conflict occurred in database "%.*ls", table "%.*ls"%ls%.*ls%ls. 0 0
548 The insert failed. It conflicted with an identity range check constraint in database '%.*ls', replicated table '%.*ls'%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. 0 0
549 The collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'. 0 0
550 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint. 0 0
552 CryptoAPI function '%ls' failed. Error 0x%x: %ls 0 0
555 User-defined functions are not yet enabled. 0 0
556 INSERT EXEC failed because the stored procedure altered the schema of the target table. 0 0
557 Only functions and some extended stored procedures can be executed from within a function. 0 0
558 Remote function calls are not allowed within a function. 0 0
561 Failed to access file '%.*ls' 0 0
562 Failed to access file '%.*ls'. Files can be accessed only through shares 0 0
563 The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated. 0 0
564 Attempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'. 0 0
565 A stack overflow occurred in the server while compiling the query. Please simplify the query. 0 0
566 An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the "-f" switch, and using SP_CONFIGURE. 0 0
567 File '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file. 0 0
568 Encountered an error or an unexpected end of trace file '%.*ls'. 0 0
569 The handle that was passed to %ls was invalid. 0 0
570 INSTEAD OF triggers do not support direct recursion. The trigger execution failed. 0 0
571 The specified attribute value for %ls is invalid. 0 0
572 Invalid regular expression "%.*ls" near the offset %d. 0 0
573 Evaluation of the regular expression is too complex: '%.*ls'. 0 0
574 %ls statement cannot be used inside a user transaction. 0 0
575 A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets. 0 0
576 Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d. 0 0
577 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647. 0 0
578 Insert Exec not allowed in WAITFOR queries. 0 0
579 Can not execute WAITFOR query with snapshot isolation level. 0 0
582 Offset is greater than the length of the column to be updated in write. 0 0
583 Negative offset or length in write. 0 0
584 Select Into not allowed in WAITFOR queries. 0 0
585 Changing database context is not allowed when populating the resource database. 0 0
587 An invalid delayed CLR type fetch token is provided. 0 0
588 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time. 0 0
589 This statement has attempted to access data whose access is restricted by the assembly. 0 0
590 RPC was aborted without execution. 0 0
591 %ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT. 0 0
592 Cannot find %S_MSG ID %d in database ID %d. 0 0
593 fn_trace_gettable: XML conversion of trace data for event 165 failed. 0 0
594 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode. 0 0
595 Bulk Insert with another outstanding result set should be run with XACT_ABORT on. 0 0
596 Cannot continue the execution because the session is in the kill state. 0 0
597 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP). 0 0
598 An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information. 0 0
599 %.*ls: The length of the result exceeds the length limit (2GB) of the target large type. 0 0
601 Could not continue scan with NOLOCK due to data movement. 0 0
602 Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 0 0
603 Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 0 0
605 Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d. 0 0
606 Metadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG. 0 0
608 No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption. 0 0
609 BTree is not empty when waking up on RowsetBulk. 0 0
610 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption. 0 0
611 Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit. 0 0
613 Could not find an entry for worktable rowset with partition ID %I64d in database %d. 0 0
615 Could not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again. 0 0
617 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor. 0 0
622 The filegroup "%.*ls" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added. 0 0
627 Cannot use SAVE TRANSACTION within a distributed transaction. 0 0
628 Cannot issue SAVE TRANSACTION when there is no active transaction. 0 0
650 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. 0 0
651 Cannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited. 0 0
652 The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified. 0 0
666 The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key. 0 0
667 The index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, is being restored, or is defunct. 0 0
669 The row object is inconsistent. Please rerun the query. 0 0
670 Large object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed. 0 0
671 Large object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified. 0 0
672 Failed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on database restart. 0 0
674 Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem. 0 0
675 Worktable with partition ID %I64d was dropped successfully after repeated attempts. 0 0
676 Error occurred while attempting to drop worktable with partition ID %I64d. 0 0
677 Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required. 0 0
678 Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error. 0 0
679 One of the partitions of index '%.*ls' for table '%.*ls'(partition ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result. 0 0
680 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d. 0 0
681 Attempting to set a non-NULL-able column's value to NULL. 0 0
682 Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption. 0 0
683 An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption. 0 0
684 An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption. 0 0
685 An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record. 0 0
701 There is insufficient system memory in resource pool '%ls' to run this query. 0 0
708 Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications. 0 0
801 A buffer was encountered with an unexpected status of 0x%x. 0 0
802 There is insufficient memory available in the buffer pool. 0 0
803 simulated failure (DEBUG only) 0 0
805 restore pending 0 0
806 audit failure (a page read from disk failed to pass basic integrity checks) 0 0
807 (no disk or the wrong disk is in the drive) 0 0
808 insufficient bytes transferred 0 0
821 Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support. 0 0
822 Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support. 0 0
823 The operating system returned error %ls to SQL Server during a %S_MSG at offset % 0 0
824 SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset % 0 0
825 A read of the file '%ls' at offset % 0 0
826 incorrect pageid (expected %d:%d; actual %d:%d) 0 0
829 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore. 0 0
830 stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u)) 0 0
831 Unable to deallocate a kept page. 0 0
832 A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption. 0 0
833 SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database [%ls] (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: % 0 0
844 Time out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat % 0 0
845 Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d. 0 0
846 A time-out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat % 0 0
847 Timeout occurred while waiting for latch: class '%ls', id %p, type %d, Task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait. 0 0
848 Using large pages for buffer pool. 0 0
849 Using locked pages for buffer pool. 0 0
850 %I64u MB of large page memory allocated. 0 0
851 the page is in an OFFLINE file which cannot be read 0 0
902 To change the %ls, the database must be in state in which a checkpoint can be executed. 0 0
904 Database %ld cannot be autostarted during server shutdown or startup. 0 0
905 Database '%.*ls' cannot be started in this edition of SQL Server because it contains a partition function '%.*ls'. Only Enterprise edition of SQL Server supports partitioning. 0 0
907 The database "%ls" has inconsistent database or file metadata. 0 0
908 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available. 0 0
909 Database '%.*ls' cannot be started in this edition of SQL Server because part or all of object '%.*ls' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition. 0 0
910 Database '%.*ls' is upgrading script '%.*ls' from level %d to level %d. 0 0
911 Database '%.*ls' does not exist. Make sure that the name is entered correctly. 0 0
912 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 0 0
913 Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. 0 0
914 Script level upgrade for database '%.*ls' failed because upgrade step '%.*ls' was aborted before completion. If the abort happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 0 0
915 Unable to obtain the current script level for database '%.*ls'. If the error happened during startup of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion. 0 0
916 The server principal "%.*ls" is not able to access the database "%.*ls" under the current security context. 0 0
917 An upgrade script batch failed to execute for database '%.*ls' due to compilation error. Check the previous error message for the line which caused compilation to fail. 0 0
918 Failed to load the engine script metadata from script DLL '%.*ls'. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error. 0 0
919 User '%.*ls' is changing database script level entry %d to a value of %d. 0 0
920 Only members of the sysadmin role can modify the database script level. 0 0
921 Database '%.*ls' has not been recovered yet. Wait and try again. 0 0
922 Database '%.*ls' is being recovered. Waiting until recovery is finished. 0 0
923 Database '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it. 0 0
924 Database '%.*ls' is already open and can only have one user at a time. 0 0
925 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d. 0 0
926 Database '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. 0 0
927 Database '%.*ls' cannot be opened. It is in the middle of a restore. 0 0
928 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause. 0 0
929 Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider. 0 0
930 Attempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support. 0 0
931 Attempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support. 0 0
932 SQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking. 0 0
933 Database '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server. 0 0
934 SQL Server cannot load database '%.*ls' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture. 0 0
935 The script level for '%.*ls' in database '%.*ls' cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database. 0 0
942 Database '%.*ls' cannot be opened because it is offline. 0 0
943 Database '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d). 0 0
944 Converting database '%.*ls' from version %d to the current version %d. 0 0
945 Database '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 0 0
946 Cannot open database '%.*ls' version %d. Upgrade the database to the latest version. 0 0
947 Error while closing database '%.*ls'. Check for previous additional errors and retry the operation. 0 0
948 The database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported. 0 0
949 tempdb is skipped. You cannot run a query that requires tempdb 0 0
950 Database '%.*ls' cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. 0 0
951 Database '%.*ls' running the upgrade step from version %d to version %d. 0 0
952 Database '%.*ls' is in transition. Try the statement later. 0 0
954 The database "%.*ls" cannot be opened. It is acting as a mirror database. 0 0
955 Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured. 0 0
956 Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later. 0 0
957 Database '%.*ls' is enabled for Database Mirroring, The name of the database may not be changed. 0 0
958 The resource database build version is %.*ls. This is an informational message only. No user action is required. 0 0
959 The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server. 0 0
960 Warning: User "sys" (principal_id = %d) in database "%.*ls" has been renamed to "%.*ls". "sys" is a reserved user or schema name in this version of SQL Server. 0 0
961 Warning: Index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls" was renamed to "%.*ls" because its name is a duplicate of another index on the same object. 0 0
962 Warning: Primary key or Unique constraint "%.*ls" (object_id = %d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed. 0 0
963 Warning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state. 0 0
964 Warning: System user '%.*ls' was found missing from database '%.*ls' and has been restored. This user is required for SQL Server operation. 0 0
965 Warning: A column nullability inconsistency was detected in the metadata of index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency. 0 0
966 Warning: Assembly "%.*ls" in database "%.*ls" has been renamed to "%.*ls" because the name of the assembly conflicts with a system assembly in this version of SQL Server. 0 0
967 Warning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported. 0 0
968 Warning: The XML facet on type "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 0 0
969 Warning: The default or fixed value on XML element or attribute "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 0 0
970 Warning: The XML instances in the XML column "%.*ls.%.*ls.%.*ls" may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary XML index on these XML instances. 0 0
971 The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' instead of the currently attached resource database at '%.*ls'. 0 0
972 Could not use database '%d' during procedure execution. 0 0
973 Database %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove the FILESTREAM files and the FILESTREAM filegroups, or set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF. 0 0
35001 Parent Server Group does not exist. 0 0
35002 Server type and parent Server Group type are not the same 0 0
35003 Cannot move node to one of its children 0 0
35004 Could not find server group 0 0
35005 An invalid value NULL was passed in for @server_group_id. 0 0
35006 An invalid value NULL was passed in for @server_id. 0 0
35007 Could not find shared registered server. 0 0
35008 Cannot delete system shared server groups. 0 0
35009 An invalid value NULL was passed in for @server_type. 0 0
35010 An invalid value %d was passed in for parameter @server_type. 0 0
35011 The @server_name parameter cannot be a relative name. 0 0
35012 You cannot add a shared registered server with the same name as the Configuration Server. 0 0
4001 Client sends a sp_reset_connection while there is still pending requests, server is disconnecting. 0 0
4002 The incoming tabular data stream (TDS) protocol stream is incorrect. The stream ended unexpectedly. 0 0
4004 Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. 0 0
4005 Cannot update columns from more than one underlying table in a single update call. 0 0
4006 You cannot delete rows from more than one underlying table in a single delete call. 0 0
4007 Cannot update or insert column "%.*ls". It may be an expression. 0 0
4008 The data types varchar(max), nvarchar(max), varbinary(max), and XML cannot be used in the compute clause by client driver versions earlier than SQL Server 2005. Please resubmit the query using a more recent client driver. 0 0
4009 The incoming tabular data stream (TDS) protocol stream is incorrect. The TDS headers contained errors. 0 0
4010 The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors. 0 0
4011 The incoming tabular data stream (TDS) protocol stream is incorrect. The MARS TDS header contained errors. 0 0
4012 An invalid tabular data stream (TDS) collation was encountered. 0 0
4013 The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is missing. 0 0
4014 A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: %d, output error: %d). 0 0
4015 Language requested in login '%.*ls' is not an official name on this SQL Server. Using server-wide default %.*ls instead. 0 0
4016 Language requested in 'login %.*ls' is not an official name on this SQL Server. Using user default %.*ls instead. 0 0
4017 Neither the language requested in 'login %.*ls' nor user default language %.*ls is an official language name on this SQL Server. Using server-wide default %.*ls instead. 0 0
4018 User default language %.*ls is not an official language name on this SQL Server. Using server-wide default %.*ls instead. 0 0
4019 Language requested in login '%.*ls' is not an official language name on this SQL Server. Login fails. 0 0
4020 Default date order '%.*ls' for language %.*ls is invalid. Using mdy instead. 0 0
4021 Resetting the connection results in a different state than the initial login. The login fails. 0 0
4022 Bulk load data was expected but not sent. The batch will be terminated. 0 0
4027 Mount tape for %hs of database '%ls' on tape drive '%ls'. 0 0
4028 End of tape has been reached. Remove tape '%ls' and mount next tape for %hs of database '%ls'. 0 0
4030 The medium on device '%ls' expires on %hs and cannot be overwritten. 0 0
4035 Processed %I64d pages for database '%ls', file '%ls' on file %d. 0 0
4037 The user-specified MEDIANAME "%.*ls" does not match the MEDIANAME "%ls" of the device "%ls". 0 0
4038 Cannot find file ID %d on device '%ls'. 0 0
4060 Cannot open database "%.*ls" requested by the login. The login failed. 0 0
4061 Neither the database "%.*ls" requested by the login nor the user default database could be opened. The master database is being used instead. 0 0
4062 Cannot open user default database. Using master database instead. 0 0
4063 Cannot open database "%.*ls" that was requested by the login. Using the user default database "%.*ls" instead. 0 0
4064 Cannot open user default database. Login failed. 0 0
4065 User is trying to use '%.*ls' through ODS, which is not supported any more. 0 0
4066 Type IDs larger than 65535 cannot be sent to clients shipped in SQL Server 2000 or earlier. 0 0
4067 CLR type serialization failed because an invalid cookie was specified. 0 0
4068 sp_resetconnection was sent as part of a remote procedure call (RPC) batch, but it was not the last RPC in the batch. This connection will be terminated. 0 0
4069 The final value of the output parameter was null, and could not be sent to a 6.5 client expecting the parameter to be non-nullable. 0 0
4070 More than 255 columns were specified in the COMPUTE clause, and this metadata cannot be sent to a SQL Server version 6.5 client. 0 0
4071 The XP callback function '%.*ls' failed in extended procedure '%.*ls' because it was executed within an INSERT-EXEC statement which does not allow the extended procedure to send information other than result set. 0 0
4072 The XP callback function '%.*ls' failed in extended procedure '%.*ls' because the extended procedure is called inside an UDF which doesn't allow sending data. 0 0
4073 A return value of data type varchar(max), nvarchar(max), varbinary(max), XML or other large object type can not be returned to client driver versions earlier than SQL Server 2005. Please resubmit the query using a more recent client driver. 0 0
4074 Client drivers do not accept result sets that have more than 65,535 columns. 0 0
4075 The USE database statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations. 0 0
4076 The ALTER DATABASE statement failed because the database collation %.*ls is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations. 0 0
4077 The statement failed because the sql_variant value uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations. 0 0
4078 The statement failed because column '%.*ls' (ID=%d) uses collation %.*ls, which is not recognized by older client drivers. Try upgrading the client operating system or applying a service update to the database client software, or use a different collation. See SQL Server Books Online for more information on changing collations. 0 0
4079 The statement failed due to arithmetic overflow when sending data stream. 0 0
4101 Aggregates on the right side of an APPLY cannot reference columns from the left side. 0 0
4102 The READPAST lock hint is only allowed on target tables of UPDATE and DELETE and on tables specified in an explicit FROM clause. 0 0
4103 %.*ls: Temporary views are not allowed. 0 0
4104 The multi-part identifier "%.*ls" could not be bound. 0 0
4105 User-defined functions, partition functions, and column references are not allowed in expressions in this context. 0 0
4106 Non-ANSI outer joins (*= and =*) are not allowed when a table that contains a column set is used in a query. Change the query to use ANSI outer joins. 0 0
4107 Inserting into remote tables or views is not allowed by using the BCP utility or by using BULK INSERT. 0 0
4108 Windowed functions can only appear in the SELECT or ORDER BY clauses. 0 0
4109 Windowed functions cannot be used in the context of another windowed function or aggregate. 0 0
4110 The argument type "%s" is invalid for argument %d of "%s". 0 0
4111 The CREATE SCHEMA statement should be followed by a name or authorization keyword. 0 0
4112 The ranking function "%.*ls" must have an ORDER BY clause. 0 0
4113 %.*ls is not a valid windowing function, and cannot be used with the OVER clause. 0 0
4114 The function '%.*ls' takes exactly %d argument(s). 0 0
4115 The reference to column "%.*ls" is not allowed in the argument of the TOP clause. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here. 0 0
4116 The function 'ntile' takes only a positive int or bigint expression as its input. 0 0
4117 Cannot retrieve table data for the query operation because the table "%.*ls" schema is being altered too frequently. Because the table "%.*ls" contains a computed column, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring. 0 0
4118 An invalid expression was specified in the FOR UPDATE clause. 0 0
4119 Default values cannot be assigned to property setters of columns with a CLR type. 0 0
4120 A user-defined function name cannot be prefixed with a database name in this context. 0 0
4121 Cannot find either column "%.*ls" or the user-defined function or aggregate "%.*ls", or the name is ambiguous. 0 0
4122 Remote table-valued function calls are not allowed. 0 0
4124 The parameters supplied for the batch are not valid. 0 0
4126 No No full-text indexed columns were found. 0 0
4127 At least one of the arguments to COALESCE must be a typed NULL. 0 0
4128 An internal error occurred during remote query execution. Contact your SQL Server support professional and provide details about the query you were trying to run. 0 0
4129 The inline function "%.*ls" cannot take correlated parameters or subqueries because it uses a full-text operator. 0 0
4130 A duplicate hint was specified for the BULK rowset. 0 0
4131 A compile-time literal value is specified more than once for the variable "%.*ls" in one or more OPTIMIZE FOR clauses. 0 0
4132 The value specified for the variable "%.*ls" in the OPTIMIZE FOR clause could not be implicitly converted to that variable's type. 0 0
4133 Only a scalar expression may be specified as the argument to the RETURN statement. 0 0
4134 Metadata stored on disk for computed column '%.*ls' in table '%.*ls' did not match the column definition. In order to avoid possible index corruption, please drop and recreate this computed column. 0 0
4135 Synonym '%.*ls' is defined over queue '%.*ls'. Synonyms on queues are not allowed. 0 0
4136 The hint '%.*ls' cannot be used with the hint '%.*ls'. 0 0
4137 A format file cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option. 0 0
4138 Conflicting locking hints are specified for table "%.*ls". This may be caused by a conflicting hint specified for a view. 0 0
4139 Cannot process the query because it references the common language runtime (CLR) table-valued function "%.*ls" with a hint through view "%.*ls". 0 0
4140 The READCOMMITTEDLOCK lock hint is not allowed on the target table of an INSERT statement. 0 0
4141 Nested CLR type updates are not allowed. 0 0
4142 Aggregates are not allowed in the RECEIVE list. 0 0
4143 The bulk openrowset provider is not a valid target for %.*ls. 0 0
4144 The hint '%.*ls' is not allowed when inserting into remote tables. 0 0
4145 An expression of non-boolean type specified in a context where a condition is expected, near '%.*ls'. 0 0
4146 Statistics can only be created on columns. 0 0
4147 The query uses non-ANSI outer join operators ("*=" or "=*"). To run this query without modification, please set the compatibility level for current database to 80, using the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes. 0 0
4148 XML methods are not allowed in a GROUP BY clause. 0 0
4150 Hints are not allowed on recursive common table expression (CTE) references. Consider removing hint from recursive CTE reference '%.*ls'. 0 0
4151 The type of the first argument to NULLIF cannot be the NULL constant because the type of the first argument has to be known. 0 0
4152 Type "%.*ls" is not a CLR type. 0 0
4153 Cannot treat data type "%ls" as data type "%ls". 0 0
4154 UNNEST can only take an expression of type multiset. 0 0
4155 The SELECT list for the nested INSERT statement can only contain one item. 0 0
4156 The target of nested insert, nested update, or nested delete must be of type multiset. 0 0
4157 %.*ls is not a valid property, field, or method. 0 0
4158 The field "%.*ls" is referenced more than once in the set list, either directly or through a property. 0 0
4159 Delayed CLR type instances require local base table column as an argument. 0 0
4160 Could not find suitable key in table '%.*ls' for use in delayed CLR type fetching. 0 0
4161 Only CLR types are allowed in delayed CLR type fetching. 0 0
4162 A PROB_MATCH table can only be used inside of a PROB_MATCH query. 0 0
4163 A GROUP BY clause is required in a PROB_MATCH query. 0 0
4164 A GROUP BY clause in a PROB_MATCH query can only have key columns, and needs to include all the key columns. 0 0
4165 The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same constant and variable. 0 0
4166 Invalid PROB_MATCH subquery. 0 0
4167 Multiple PROB_MATCH subqueries can only refer to the same base table. 0 0
4168 Invalid PROB_MATCH project item in the PROB_MATCH SELECT list. 0 0
4169 Applying TREAT more than once to the same expression is not allowed in a full-text property reference. 0 0
4170 The (ANY) specification can only be applied to expressions of type multiset. 0 0
4171 Alias was not specified for an aggregate in the PROB_MATCH SELECT list. 0 0
4172 Incorrect use of full-text %s. 0 0
4173 %.*s is not a valid scoring function name. 0 0
4174 Delayed CLR type instantiation fetch value query may only reference column of a large object or large value type. 0 0
4175 Nested updates cannot be performed on CLR types that are not Format.Structured. 0 0
4176 Too many parameters were specified for FULLTEXTTABLE of type "Simple". The maximum number of parameters is %d. 0 0
4177 The FROM clause of a PROB_MATCH query must consist of a single derived table. 0 0
4184 Cannot retrieve table data for the query operation because the table "%.*ls" schema is being altered too frequently. Because the table "%.*ls" contains a filtered index or filtered statistics, changes to the table schema require a refresh of all table data. Retry the query operation, and if the problem persists, use SQL Server Profiler to identify what schema-altering operations are occurring. 0 0
4185 This action cannot be performed on a system type. 0 0
4186 Column '%ls.%.*ls' cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references a function that performs user or system data access. A function is assumed by default to perform data access if it is not schemabound. Consider removing the subquery or function from the column definition or removing the column from the OUTPUT clause. 0 0
4202 BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable. 0 0
4208 The statement %hs is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE. 0 0
4212 Cannot back up the log of the master database. Use BACKUP DATABASE instead. 0 0
4214 BACKUP LOG cannot be performed because there is no current database backup. 0 0
4215 The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure the Log Reader Agent or capture job is running or use sp_repldone to mark transactions as distributed or captured. 0 0
4217 BACKUP LOG cannot modify the database because the database is read-only. The backup will continue, although subsequent backups will duplicate the work of this backup. 0 0
4218 Bulk-logged operations exist in the database. Perform a BACKUP LOG. 0 0
4302 The option "%ls" conflicts with online restore. Remove the conflicting option and reissue the command. 0 0
4303 The roll forward start point is now at log sequence number (LSN) %.*s. Additional roll forward past LSN %.*s is required to complete the restore sequence. 0 0
4305 The log in this backup set begins at LSN %.*ls, which is too recent to apply to the database. An earlier log backup that includes LSN %.*ls can be restored. 0 0
4307 The online restore to database '%ls' failed. It may be appropriate to perform an offline restore instead. To force an offline restore, first take the database offline using the ALTER DATABASE statement. 0 0
4308 The online restore is complete, but WITH NORECOVERY was specified. Use RESTORE WITH RECOVERY to bring affected data online. 0 0
4309 The state of file "%ls" prevents restoring individual pages. Only a file restore is currently possible. 0 0
4310 RESTORE PAGE is not allowed on file "%ls" because the file is not online. 0 0
4311 RESTORE PAGE is not allowed from backups taken with earlier versions of SQL Server. 0 0
4312 This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap. 0 0
4315 Some files still require more restore steps before the online restore sequence can be completed. 0 0
4318 File '%ls' has been rolled forward to LSN %.*ls. This log terminates at LSN %.*ls, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY. 0 0
4319 A previous restore operation was interrupted and did not complete processing on file '%ls'. Either restore the backup set that was interrupted or restart the restore sequence. 0 0
4320 The file "%ls" was not fully restored by a database or file restore. The entire file must be successfully restored before applying this backup set. 0 0
4322 This backup set contains records that were logged before the designated point in time. The database is being left in the restoring state so that more roll forward can be performed. 0 0
4323 A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option. 0 0
4326 The log in this backup set terminates at LSN %.*ls, which is too early to apply to the database. A more recent log backup that includes LSN %.*ls can be restored. 0 0
4327 The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled forward to the end of the log. 0 0
4328 The file "%ls" is missing. Roll forward stops at log sequence number %.*ls. The file is created at log sequence number (LSN) %.*ls, dropped at LSN %.*ls. Restore the transaction log beyond the point in time when the file was dropped, or restore data to be consistent with rest of the database. 0 0
4329 This log file contains records logged before the designated mark. The database is being left in the Restoring state so you can apply another log file. 0 0
4330 This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time. For more information about recovery paths, see SQL Server Books Online. 0 0
4331 The database cannot be recovered because the files have been restored to inconsistent points in time. 0 0
4332 RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY. 0 0
4333 The database cannot be recovered because the log was not restored. 0 0
4334 The named mark does not identify a valid LSN. 0 0
4335 The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point. 0 0
4336 The filegroup "%ls" has been dropped and cannot be restored into the online database. 0 0
4337 The file "%ls" has been dropped and cannot be restored into the online database. 0 0
4338 The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use RESTORE DATABASE WITH RECOVERY to recover at the current point. 0 0
4339 This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are needed. Previous messages indicate reasons why recovery cannot occur at this point. 0 0
4340 The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause or use a clause that includes a timestamp. 0 0
4341 This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time. 0 0
4342 Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence. Omit the point-in-time clause or restore the primary filegroup. 0 0
4343 The database has been rolled forward to the end of this backup set and beyond the specified point in time. RESTORE WITH RECOVERY can be used to accept the current recovery point. 0 0
4344 RESTORE PAGE is not allowed on read-only databases or filegroups. 0 0
4345 Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information. 0 0
4346 RESTORE PAGE is not allowed with databases that use the simple recovery model. 0 0
4347 The current restore sequence was previously interrupted during the transition to the online state. RESTORE DATABASE WITH RECOVERY can be used to complete the transition to online. 0 0
4348 The online restore to database '%ls' failed. It may be appropriate to perform an offline restore instead. An offline restore is initiated by using BACKUP LOG WITH NORECOVERY. 0 0
4349 The log in this backup set begins at LSN %.*ls, which is too recent to apply to the database. This restore sequence needs to initialize the log to start at LSN %.*ls. Reissue the RESTORE LOG statement using an earlier log backup. 0 0
4350 The list of pages provided with the RESTORE PAGE statement is incorrectly formatted. Prior to the problem %d pages were correctly identified. The problem was hit at character offset %d. Check that all pages are identified by numeric : pairs with commas separating each pair. For example: PAGE='1:57,2:31'. 0 0
4351 Backups taken on earlier versions of SQL Server are not supported by fn_dump_dblog. 0 0
4352 RESTORE LOG is not supported from this data backup because file '%ls' is too old. Use a regular log backup to continue the restore sequence. 0 0
4353 Conflicting file relocations have been specified for file '%.*ls'. Only a single WITH MOVE clause should be specified for any logical file name. 0 0
4354 The file '%.*ls' of restored database '%ls' is being left in the defunct state because the database is being upgraded from a prior version. Piecemeal restore is not supported when an upgrade is involved. 0 0
4355 The revert command is incorrectly specified. The RESTORE statement must be of the form: RESTORE DATABASE FROM DATABASE_SNAPSHOT = . 0 0
4356 Restore is complete on database '%ls'. The database is now available. 0 0
4357 Restore cannot take '%ls' offline because changes exist that require a log backup. Take a log backup and then retry the RESTORE. 0 0
4358 The database can not be brought online because file '%ls' is currently restored to LSN %.*ls but must be restored to LSN %.*ls. 0 0
4359 The STOPAT option cannot be used with this partial restore sequence because one or more FILESTREAM filegroups are not included. The CONTINUE_AFTER_ERROR option can be used to force the recovery, but this should only be used if you do not intend to subsequently restore the FILESTREAM filegroups. 0 0
4360 RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted. 0 0
4403 Cannot update the view or function '%.*ls' because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator. 0 0
4405 View or function '%.*ls' is not updatable because the modification affects multiple base tables. 0 0
4406 Update or insert of view or function '%.*ls' failed because it contains a derived or constant field. 0 0
4408 Too many tables. The query and the views or functions in it exceed the limit of %d tables. Revise the query to reduce the number of tables. 0 0
4413 Could not use view or function '%.*ls' because of binding errors. 0 0
4414 Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%d) was exceeded. 0 0
4415 View '%.*ls' is not updatable because either it was created WITH CHECK OPTION or it spans a view created WITH CHECK OPTION and the target table is referenced multiple times in the resulting query. 0 0
4416 UNION ALL view '%.*ls' is not updatable because the definition contains a disallowed construct. 0 0
4417 Derived table '%.*ls' is not updatable because the definition contains a UNION operator. 0 0
4418 Derived table '%.*ls' is not updatable because it contains aggregates, or a DISTINCT or GROUP BY clause, or PIVOT or UNPIVOT operator. 0 0
4420 Derived table '%.*ls' is not updatable because the modification affects multiple base tables. 0 0
4421 Derived table '%.*ls' is not updatable because a column of the derived table is derived or constant. 0 0
4422 View '%.*ls' has an INSTEAD OF UPDATE trigger and cannot be a target of an UPDATE FROM statement. 0 0
4423 View '%.*ls' has an INSTEAD OF DELETE trigger and cannot be a target of a DELETE FROM statement. 0 0
4424 Joined tables cannot be specified in a query containing outer join operators. View or function '%.*ls' contains joined tables. 0 0
4425 Cannot specify outer join operators in a query containing joined tables. View or function '%.*ls' contains outer join operators. 0 0
4426 View '%.*ls' is not updatable because the definition contains a UNION operator. 0 0
4427 Cannot update the view "%.*ls" because it or a view it references was created with WITH CHECK OPTION and its definition contains the TOP clause. 0 0
4429 View or function '%.*ls' contains a self-reference. Views or functions cannot reference themselves directly or indirectly. 0 0
4430 Warning: Index hints supplied for view '%.*ls' will be ignored. 0 0
4431 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a timestamp column. 0 0
4432 Partitioned view '%.*ls' is not updatable because table '%.*ls' has a DEFAULT constraint. 0 0
4433 Cannot INSERT into partitioned view '%.*ls' because table '%.*ls' has an IDENTITY constraint. 0 0
4434 Partitioned view '%.*ls' is not updatable because table '%.*ls' has an INSTEAD OF trigger. 0 0
4435 Partitioned view '%.*ls' is not updatable because a value was not specified for partitioning column '%.*ls'. 0 0
4436 UNION ALL view '%.*ls' is not updatable because a partitioning column was not found. 0 0
4437 Partitioned view '%.*ls' is not updatable as the target of a bulk operation. 0 0
4438 Partitioned view '%.*ls' is not updatable because it does not deliver all columns from its member tables. 0 0
4439 Partitioned view '%.*ls' is not updatable because the source query contains references to partition table '%.*ls'. 0 0
4440 UNION ALL view '%.*ls' is not updatable because a primary key was not found on table '%.*ls'. 0 0
4441 Partitioned view '%.*ls' is not updatable because the table '%.*ls' has an index on a computed column. 0 0
4442 UNION ALL view '%.*ls' is not updatable because base table '%.*ls' is used multiple times. 0 0
4443 UNION ALL view '%.*ls' is not updatable because column '%.*ls' of base table '%.*ls' is used multiple times. 0 0
4444 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not included in the union result. 0 0
4445 UNION ALL view '%.*ls' is not updatable because the primary key of table '%.*ls' is not unioned with primary keys of preceding tables. 0 0
4446 Cannot update the UNION ALL view "%.*ls" because the definition of column "%.*ls" of view "%.*ls" is used by another view column. 0 0
4447 View '%.*ls' is not updatable because the definition contains a set operator. 0 0
4448 Cannot INSERT into partitioned view '%.*ls' because values were not supplied for all columns. 0 0
4449 Using defaults is not allowed in views that contain a set operator. 0 0
4450 Cannot update partitioned view '%.*ls' because the definition of the view column '%.*ls' in table '%.*ls' has an IDENTITY constraint. 0 0
4451 Views referencing tables on multiple servers are not updatable in the edition of this SQL Server instance '%.*ls'. See books online for more details on feature support in different SQL Server editions. 0 0
4452 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a CASCADE DELETE or CASCADE UPDATE constraint. 0 0
4453 Cannot UPDATE partitioning column '%.*ls' of view '%.*ls' because the table '%.*ls' has a INSERT, UPDATE or DELETE trigger. 0 0
4454 Cannot update the partitioned view "%.*ls" because the partitioning columns of its member tables have mismatched types. 0 0
4456 The partitioned view "%.*ls" is not updatable because one or more of the non-partitioning columns of its member tables have mismatched types. 0 0
4457 The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions. 0 0
4502 View or function '%.*ls' has more column names specified than columns defined. 0 0
4503 Could not create schemabound %S_MSG '%.*ls' because it references an object in another database. 0 0
4504 Could not create %S_MSG '%.*ls' because CLR type '%.*ls' does not exist in the target database '%.*ls'. 0 0
4505 CREATE VIEW failed because column '%.*ls' in view '%.*ls' exceeds the maximum of %d columns. 0 0
4506 Column names in each view or function must be unique. Column name '%.*ls' in view or function '%.*ls' is specified more than once. 0 0
4508 Views or functions are not allowed on temporary tables. Table names that begin with ' 0 0
4510 Could not perform CREATE VIEW because WITH %ls was specified and the view is not updatable. 0 0
4511 Create View or Function failed because no column name was specified for column %d. 0 0
4512 Cannot schema bind %S_MSG '%.*ls' because name '%.*ls' is invalid for schema binding. Names must be in two-part format and an object cannot reference itself. 0 0
4513 Cannot schema bind %S_MSG '%.*ls'. '%.*ls' is not schema bound. 0 0
4514 CREATE FUNCTION failed because a column name is not specified for column %d. 0 0
4515 CREATE FUNCTION failed because column '%.*ls' in function '%.*ls' exceeds the maximum of %d columns. 0 0
4516 Cannot schema bind function '%.*ls' because it contains an EXECUTE statement. 0 0
4517 Service queue object cannot be used in schemabinding expressions. '%.*ls' is a service queue. 0 0
4519 Cannot %S_MSG %S_MSG '%.*ls' on view '%.*ls' because it is a system generated view that was created for optimization purposes. 0 0
4520 Cannot disable index on view '%.*ls' because it is a system generated view that was created for optimization purposes. 0 0
4521 Cannot use object '%.*ls' with autodrop object attribute in schemabinding expressions because it is a system generated view that was created for optimization purposes. 0 0
4522 Cannot alter view '%.*ls' because it is a system generated view that was created for optimization purposes. 0 0
4523 Cannot create trigger on view '%.*ls' because it is a system generated view that was created for optimization purposes. 0 0
4602 Only members of the sysadmin role can grant or revoke the CREATE DATABASE permission. 0 0
4604 There is no such user or group '%.*ls' or you do not have permission. 0 0
4606 Granted or revoked privilege %ls is not compatible with object. 0 0
4610 You can only grant or revoke permissions on objects in the current database. 0 0
4611 To revoke or deny grantable privileges, specify the CASCADE option. 0 0
4613 Grantor does not have GRANT permission. 0 0
4615 Invalid column name '%.*ls'. 0 0
4616 You cannot perform this operation for the resource database. 0 0
4617 Cannot grant, deny or revoke permissions to or from special roles. 0 0
4618 You do not have permission to use %.*ls in the AS clause. 0 0
4619 CREATE DATABASE permission can only be granted in the master database. 0 0
4620 All permissions in a grant/deny/revoke statement should be at the same scope (e.g., server or database) 0 0
4621 Permissions at the server scope can only be granted when the current database is master 0 0
4622 Permissions at the server scope can only be granted to logins 0 0
4623 The all permission has been deprecated and is not available for this class of entity 0 0
4624 Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself. 0 0
4625 There is no such server principal %.*s or you do not have permission. 0 0
4627 Cannot grant, deny, or revoke the connect database permission to roles and application roles. 0 0
4628 The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity. 0 0
4629 Permissions on server scoped catalog views or system stored procedures or extended stored procedures can be granted only when the current database is master. 0 0
4701 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 0 0
4707 Could not truncate object '%.*ls' because it or one of its indexes resides on a READONLY filegroup '%.*ls'. 0 0
4708 Could not truncate object '%.*ls' because it is not a table. 0 0
4709 You are not allowed to truncate the system table '%.*ls'. 0 0
4710 Could not truncate object '%.*ls' because it or one of its indexes resides on an offline filegroup '%.*ls'. 0 0
4711 Cannot truncate table '%.*ls' because it is published for replication or enabled for Change Data Capture. 0 0
4712 Cannot truncate table '%.*ls' because it is being referenced by a FOREIGN KEY constraint. 0 0
4801 Insert bulk is not supported over this access protocol. 0 0
4802 The SINGLE_LOB, SINGLE_CLOB, and SINGLE_NCLOB options are mutually exclusive with all other options. 0 0
4803 The bulk copy (bcp) client has sent a row length of %d. This is not a valid size. The maximum row size is %d. Use a supported client application programming interface (API). 0 0
4804 While reading current row from host, a premature end-of-message was encountered--an incoming data stream was interrupted when the server expected to see more data. The host program may have terminated. Ensure that you are using a supported client application programming interface (API). 0 0
4805 The front-end tool you are using does not support bulk load from host. Use the supported tools for this command. 0 0
4806 SINGLE_CLOB requires a double-byte character set (DBCS) (char) input file. The file specified is Unicode. 0 0
4807 The bulk copy (bcp) client sent a row length of %d. This size is not valid. The minimum row size is %d. Use a supported client application programming interface (API). 0 0
4808 Bulk copy operations cannot trigger bulk load statements. 0 0
4809 SINGLE_NCLOB requires a UNICODE (widechar) input file. The file specified is not Unicode. 0 0
4810 Expected the TEXT token in data stream for bulk copy of text or image data. 0 0
4811 Expected the column offset in data stream for bulk copy of text or image data. 0 0
4812 Expected the row offset in data stream for bulk copy of text or image data. 0 0
4813 Expected the text length in data stream for bulk copy of text, ntext, or image data. 0 0
4814 Bulk copy into a partitioned table is not supported for down-level clients. 0 0
4815 Received an invalid column length from the bcp client for colid %d. 0 0
4816 Invalid column type from bcp client for colid %d. 0 0
4817 Could not bulk load. The sorted column '%.*ls' is not valid. The ORDER hint is ignored. 0 0
4818 Could not bulk load. The sorted column '%.*ls' was specified more than once. The ORDER hint is ignored. 0 0
4819 Cannot bulk load. The bulk data stream was incorrectly specified as sorted or the data violates a uniqueness constraint imposed by the target table. Sort order incorrect for the following two rows: primary key of first row: %s, primary key of second row: %s. 0 0
4820 Cannot bulk load. Unknown version of format file "%s". 0 0
4821 Cannot bulk load. Error reading the number of columns from the format file "%s". 0 0
4822 Cannot bulk load. Invalid number of columns in the format file "%s". 0 0
4823 Cannot bulk load. Invalid column number in the format file "%s". 0 0
4824 Cannot bulk load. Invalid data type for column number %d in the format file "%s". 0 0
4825 Cannot bulk load. Invalid prefix for column number %d in the format file "%s". 0 0
4826 Cannot bulk load. Invalid column length for column number %d in the format file "%s". 0 0
4827 Cannot bulk load. Invalid column terminator for column number %d in the format file "%s". 0 0
4828 Cannot bulk load. Invalid destination table column number for source column %d in the format file "%s". 0 0
4829 Cannot bulk load. Error reading the destination table column name for source column %d in the format file "%s". 0 0
4830 Bulk load: DataFileType was incorrectly specified as char. DataFileType will be assumed to be widechar because the data file has a Unicode signature. 0 0
4831 Bulk load: DataFileType was incorrectly specified as widechar. DataFileType will be assumed to be char because the data file does not have a Unicode signature. 0 0
4832 Bulk load: An unexpected end of file was encountered in the data file. 0 0
4833 Bulk load: Version mismatch between the provider dynamic link library and the server executable. 0 0
4834 You do not have permission to use the bulk load statement. 0 0
4835 Bulk copying into a table with computed columns is not supported for downlevel clients. 0 0
4836 Warning: Table "%.*s" is published for merge replication. Reinitialize affected subscribers or execute sp_addtabletocontents to ensure that data added is included in the next synchronization. 0 0
4837 Cannot bulk copy into a table "%.*s" that is enabled for immediate-updating subscriptions. 0 0
4838 The bulk data source does not support the SQLNUMERIC or SQLDECIMAL data types. 0 0
4839 Cannot perform the bulk load. Invalid collation name for source column %d in the format file "%s". 0 0
4840 The bulk data source provider string has an invalid %ls property value %ls. 0 0
4841 The data source name is not a simple object name. 0 0
4842 The required FormatFile property is missing from the provider string of the server. 0 0
4843 The bulk data source provider string has a syntax error ('%lc') near character position %d. 0 0
4844 The bulk data source provider string has an unsupported property name (%ls). 0 0
4845 The bulk data source provider string has a syntax error near character position %d. Expected '%lc', but found '%lc'. 0 0
4846 The bulk data provider failed to allocate memory. 0 0
4847 Bulk copying into a table with bigint columns is not supported for versions earlier than SQL Server 2000. 0 0
4848 Bulk copying into a table with sql_variant columns is not supported for versions earlier than SQL Server 2000. 0 0
4855 Line %d in format file "%ls": unexpected element "%ls". 0 0
4856 Line %d in format file "%ls": unexpected info item. 0 0
4857 Line %d in format file "%ls": Attribute "%ls" could not be specified for this type. 0 0
4858 Line %d in format file "%ls": bad value %ls for attribute "%ls". 0 0
4859 Line %d in format file "%ls": required attribute "%ls" is missing. 0 0
4860 Cannot bulk load. The file "%ls" does not exist. 0 0
4861 Cannot bulk load because the file "%ls" could not be opened. Operating system error code %ls. 0 0
4862 Cannot bulk load because the file "%ls" could not be read. Operating system error code %ls. 0 0
4863 Bulk load data conversion error (truncation) for row %d, column %d (%ls). 0 0
4864 Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls). 0 0
4865 Cannot bulk load because the maximum number of errors (%d) was exceeded. 0 0
4866 The bulk load failed. The column is too long in the data file for row %d, column %d. Verify that the field terminator and row terminator are specified correctly. 0 0
4867 Bulk load data conversion error (overflow) for row %d, column %d (%ls). 0 0
4868 The bulk load failed. The codepage "%d" is not installed. Install the codepage and run the command again. 0 0
4869 The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL. 0 0
4870 Cannot bulk load because of an error writing file "%ls". Operating system error code %ls. 0 0
4871 Bulk load error while attempting to log errors. 0 0
4872 Line %d in format file "%ls": duplicate element id "%ls". 0 0
4873 Line %d in format file "%ls": referencing non-existing element id "%ls". 0 0
4874 Line %d in format file "%ls": duplicate element id reference "%ls". 0 0
4875 Invalid column attribute from bcp client for colid %d. 0 0
4876 The Bulk Insert operation of SQL Server Destination has timed out. Please consider increasing the value of Timeout property on the SQL Server Destination in the dataflow. 0 0
4877 Error parsing DTS stream when reading row %d, column %d. 0 0
4880 Cannot bulk load. When you use the FIRSTROW and LASTROW parameters, the value for FIRSTROW cannot be greater than the value for LASTROW. 0 0
4881 Note: Bulk Insert through a view may result in base table default values being ignored for NULL columns in the data file. 0 0
4882 Cannot bulk load. A prefix length, field length, or terminator is required for the source column %d in the format file "%s". 0 0
4883 The XML reader returned 0x%08X for the info item starting near line %d column %d in format file "%ls". 0 0
4884 Unknown error near info item starting near line %d column %d in format file "%ls". 0 0
4885 Cannot open file "%ls". A Windows NT Integrated Security login is required. 0 0
4886 Cannot open the file "%ls". Operating system error: %ls 0 0
4887 Cannot open the file "%ls". Only disk files are supported. 0 0
4888 Cannot open the file "%ls". The bulkadmin role membership is required. 0 0
4889 Cannot open the file "%ls". A unicode byte-order mark is missing. 0 0
4890 Insert bulk is not supported in showplan mode. 0 0
4891 Insert bulk failed due to a schema change of the target table. 0 0
4892 Bulk insert failed due to a schema change of the target table. 0 0
4893 Could not bulk load because SSIS file mapping object '%ls' could not be opened. Operating system error code %ls. Make sure you are accessing a local server via Windows security. 0 0
4894 COLMETADATA must be present when using bcp. 0 0
4895 Unicode data is odd byte size for column %d. Should be even byte size. 0 0
4896 Invalid column value from bcp client for colid %d. 0 0
4897 Received an invalid length for chunked LOB data for colid %d. 0 0
4900 The ALTER TABLE SWITCH statement failed for table '%.*ls'. It is not possible to switch the partition of a table that has change tracking enabled. Disable change tracking before using ALTER TABLE SWITCH. 0 0
4901 ALTER TABLE only allows columns to be added that can contain nulls, or have a DEFAULT definition specified, or the column being added is an identity or timestamp column, or alternatively if none of the previous conditions are satisfied the table must be empty to allow addition of this column. Column '%.*ls' cannot be added to non-empty table '%.*ls' because it does not satisfy these conditions. 0 0
4902 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 0 0
4903 Warning: The specified partition %d for the table '%.*ls' was ignored in ALTER TABLE SWITCH statement because the table is not partitioned. 0 0
4904 ALTER TABLE SWITCH statement failed. The specified partition %d of target table '%.*ls' must be empty. 0 0
4905 ALTER TABLE SWITCH statement failed. The target table '%.*ls' must be empty. 0 0
4906 '%ls' statement failed. The %S_MSG '%.*ls' is %S_MSG partitioned while index '%.*ls' is %S_MSG partitioned. 0 0
4907 '%ls' statement failed. The %S_MSG '%.*ls' has %d partitions while index '%.*ls' has %d partitions. 0 0
4908 '%ls' statement failed. The range boundary values used to partition the %S_MSG '%.*ls' are different from the range boundary values used for index '%.*ls'. 0 0
4909 Cannot alter '%.*ls' because it is not a table. 0 0
4911 Cannot specify a partitioned table without partition number in ALTER TABLE SWITCH statement. The table '%.*ls' is partitioned. 0 0
4912 '%ls' statement failed. The columns set used to partition the %S_MSG '%.*ls' is different from the column set used to partition index '%.*ls'. 0 0
4913 ALTER TABLE SWITCH statement failed. The table '%.*ls' has clustered index '%.*ls' while the table '%.*ls' does not have clustered index. 0 0
4914 The ALTER TABLE SWITCH statement failed. The table "%.*ls" has a disabled clustered index. 0 0
4915 '%ls' statement failed. The parameter type of the partition function used to partition the %S_MSG '%.*ls' is different from the parameter type of the partition function used to partition index '%.*ls'. 0 0
4916 Could not enable or disable the constraint. See previous errors. 0 0
4917 Constraint '%.*ls' does not exist. 0 0
4918 ALTER TABLE SWITCH statement failed because the table '%.*ls' has fulltext index on it. 0 0
4919 PERSISTED attribute cannot be altered on column '%.*ls' because this column is not computed. 0 0
4920 ALTER TABLE failed because trigger '%.*ls' on table '%.*ls' does not exist. 0 0
4921 ALTER TABLE failed because trigger '%.*ls' does not belong to table '%.*ls'. 0 0
4922 %ls %.*ls failed because one or more objects access this column. 0 0
4923 ALTER TABLE DROP COLUMN failed because '%.*ls' is the only data column in table '%.*ls'. A table must have at least one data column. 0 0
4924 %ls failed because column '%.*ls' does not exist in table '%.*ls'. 0 0
4925 ALTER TABLE ALTER COLUMN ADD ROWGUIDCOL failed because a column already exists in table '%.*ls' with ROWGUIDCOL property. 0 0
4926 ALTER TABLE ALTER COLUMN DROP ROWGUIDCOL failed because a column does not exist in table '%.*ls' with ROWGUIDCOL property. 0 0
4927 Cannot alter column '%.*ls' to be data type %.*ls. 0 0
4928 Cannot alter column '%.*ls' because it is '%ls'. 0 0
4929 Cannot alter the %S_MSG '%.*ls' because it is being published for replication. 0 0
4933 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column depends on a non-schemabound object. 0 0
4934 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column does user or system data access. 0 0
4935 ALTER TABLE ADD COLUMN cannot specify a FILESTREAM filegroup that differs from the existing one. 0 0
4936 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column is non-deterministic. 0 0
4938 ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.*ls' is in filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' is in filegroup '%.*ls'. 0 0
4939 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' is in filegroup '%.*ls'. 0 0
4940 ALTER TABLE SWITCH statement failed. %S_MSG '%.*ls' is in filegroup '%.*ls' and %S_MSG '%.*ls' is in filegroup '%.*ls'. 0 0
4941 ALTER TABLE SWITCH statement failed because the table '%.*ls' is marked for merge replication. 0 0
4942 ALTER TABLE SWITCH statement failed because column '%.*ls' at ordinal %d in table '%.*ls' has a different name than the column '%.*ls' at the same ordinal in table '%.*ls'. 0 0
4943 ALTER TABLE SWITCH statement failed because table '%.*ls' has %d columns and table '%.*ls' has %d columns. 0 0
4944 ALTER TABLE SWITCH statement failed because column '%.*ls' has data type %s in source table '%.*ls' which is different from its type %s in target table '%.*ls'. 0 0
4945 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'. 0 0
4946 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same persistent attribute in tables '%.*ls' and '%.*ls'. 0 0
4947 ALTER TABLE SWITCH statement failed. There is no identical index in source table '%.*ls' for the index '%.*ls' in target table '%.*ls' . 0 0
4948 ALTER TABLE SWITCH statement failed. The source table '%.*ls' is in database '%.*ls' while the target table '%.*ls' is in database '%.*ls'. 0 0
4949 ALTER TABLE SWITCH statement failed because the object '%.*ls' is not a user defined table. 0 0
4950 ALTER TABLE SWITCH statement failed because partition number %d does not exist in table '%.*ls'. 0 0
4951 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same FILESTREAM storage attribute in tables '%.*ls' and '%.*ls'. 0 0
4952 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same ANSI trimming semantics in tables '%.*ls' and '%.*ls'. 0 0
4953 ALTER TABLE SWITCH statement failed. The columns set used to partition the table '%.*ls' is different from the column set used to partition the table '%.*ls'. 0 0
4954 ALTER TABLE SWITCH statement failed. The table '%.*ls' has inline limit of %d for text in row data which is different from value %d used by table '%.*ls'. 0 0
4955 ALTER TABLE SWITCH statement failed. The source table '%.*ls' and target table '%.*ls' are same. 0 0
4956 ALTER TABLE SWITCH statement failed because the table '%.*ls' is not RANGE partitioned. 0 0
4957 '%ls' statement failed because the expression identifying partition number for the %S_MSG '%.*ls' is not of integer type. 0 0
4958 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same ROWGUIDCOL property in tables '%.*ls' and '%.*ls'. 0 0
4959 ALTER TABLE SWITCH statement failed. Partition %d of %S_MSG '%.*ls' has TEXT filegroup '%.*ls' and partition %d of %S_MSG '%.*ls' has TEXT filegroup '%.*ls'. 0 0
4960 ALTER TABLE SWITCH statement failed. Check constraint '%.*ls' in source table '%.*ls' is NOCHECK constraint but the matching check constraint '%.*ls' in target table '%.*ls' is CHECK. 0 0
4961 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%.*ls' is nullable and it is not nullable in '%.*ls'. 0 0
4962 ALTER TABLE SWITCH statement failed. Partition %d in table '%.*ls' is not a range partition. 0 0
4963 ALTER TABLE SWITCH statement failed. Partition %d is not valid for table '%.*ls'. 0 0
4964 ALTER TABLE SWITCH statement failed. Table '%.*ls' has RULE constraint '%.*ls'. SWITCH is not allowed on tables with RULE constraints. 0 0
4965 ALTER TABLE SWITCH statement failed. Column '%.*ls' in table '%.*ls' is computed column but the same column in '%.*ls' is not computed. 0 0
4966 ALTER TABLE SWITCH statement failed. Computed column '%.*ls' defined as '%.*ls' in table '%.*ls' is different from the same column in table '%.*ls' defined as '%.*ls'. 0 0
4967 ALTER TABLE SWITCH statement failed. SWITCH is not allowed because source table '%.*ls' contains primary key for constraint '%.*ls'. 0 0
4968 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has foreign key for constraint '%.*ls' but source table '%.*ls' does not have corresponding key. 0 0
4969 ALTER TABLE SWITCH statement failed. Foreign key constraint '%.*ls' is disabled in source table '%.*ls' and the corresponding constraint '%.*ls' is enabled in target table '%.*ls'. The source table constraint must be enabled. 0 0
4970 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a table level check constraint '%.*ls' but the source table '%.*ls' does not have a corresponding constraint. 0 0
4971 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a column level check constraint '%.*ls' but the source table '%.*ls' does not have a corresponding constraint. 0 0
4972 ALTER TABLE SWITCH statement failed. Check constraints or partition function of source table '%.*ls' allows values that are not allowed by check constraints or partition function on target table '%.*ls'. 0 0
4973 ALTER TABLE SWITCH statement failed. Range defined by partition %d in table '%.*ls' is not a subset of range defined by partition %d in table '%.*ls'. 0 0
4974 ALTER TABLE SWITCH statement failed. Foreign key constraint '%.*ls' is NOCHECK in source table '%.*ls' and the corresponding constraint '%.*ls' is CHECK in target table '%.*ls'. The source table constraint must be in CHECK. 0 0
4975 ALTER TABLE SWITCH statement failed. Check constraint '%.*ls' in source table '%.*ls' and check constraint '%.*ls' in target table '%.*ls' have different 'Not For Replication' settings. 0 0
4976 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a check constraint '%.*ls' on an XML column, but the source table '%.*ls' does not have an identical check constraint. 0 0
4977 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has a check constraint '%.*ls' on a CLR type column, but the source table '%.*ls' does not have an identical check constraint. 0 0
4978 ALTER TABLE SWITCH statement failed. The partition %d in table '%.*ls' resides in a read-only filegroup '%.*ls'. 0 0
4979 ALTER TABLE SWITCH statement failed. The table '%.*ls' resides in a readonly filegroup '%.*ls'. 0 0
4980 ALTER TABLE SWITCH statement failed. The lobdata of partition %d in table '%.*ls' resides in a readonly filegroup '%.*ls'. 0 0
4981 ALTER TABLE SWITCH statement failed. The lobdata of table '%.*ls' resides in a readonly filegroup '%.*ls'. 0 0
4982 ALTER TABLE SWITCH statement failed. Check constraints of source table '%.*ls' allow values that are not allowed by range defined by partition %d on target table '%.*ls'. 0 0
4983 ALTER TABLE SWITCH statement failed. Target table '%.*ls' has an XML or spatial index '%.*ls' on it. Only source table can have XML or spatial indexes in the ALTER TABLE SWITCH statement. 0 0
4984 ALTER TABLE SWITCH statement failed. Target table '%.*ls' and source table '%.*ls' have different vardecimal storage format values. Use stored procedure sp_tableoption to alter the 'vardecimal storage format' option for the tables to make sure that the values are the same. 0 0
4985 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same nullability attribute in tables '%.*ls' and '%.*ls'. 0 0
4986 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same CLR type in tables '%.*ls' and '%.*ls'. 0 0
4987 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same XML Schema Collection in tables '%.*ls' and '%.*ls'. 0 0
4988 Cannot persist computed column '%.*ls'. Underlying object '%.*ls' has a different owner than table '%.*ls'. 0 0
4989 Cannot drop the ROWGUIDCOL property for column '%.*ls' in table '%.*ls' because the column is not the designated ROWGUIDCOL for the table. 0 0
4990 Cannot alter column '%.*ls' in table '%.*ls' to add or remove the FILESTREAM column attribute. 0 0
4991 Cannot alter NOT FOR REPLICATION attribute on column '%.*ls' in table '%.*ls' because this column is not an identity column. 0 0
4992 Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values computed column that are persisted. 0 0
4993 ALTER TABLE SWITCH statement failed. The table '%.*ls' has different setting for Large Value Types Out Of Row table option as compared to table '%.*ls'. 0 0
4994 Computed column '%.*ls' in table '%.*ls' cannot be persisted because the column type, '%.*ls', is a non-byte-ordered CLR type. 0 0
4995 Vardecimal storage format cannot be enabled on table '%.*ls' because database '%.*ls' is a system database. Vardecimal storage format is not available in system databases. 0 0
4996 Change tracking is already enabled for table '%.*ls'. 0 0
4997 Cannot enable change tracking on table '%.*ls'. Change tracking requires a primary key on the table. Create a primary key on the table before enabling change tracking. 0 0
4998 Change tracking is not enabled on table '%.*ls'. 0 0
4999 Cannot enable change tracking on table '%.*ls'. Change tracking does not support a primary key of type timestamp on a table. 0 0
7000 OPENXML document handle parameter must be of data type int. 0 0
7001 OPENXML flags parameter must be of data type int. 0 0
7002 OPENXML XPath must be of a string data type, such as nvarchar. 0 0
7003 Only one OPENXML column can be of type %ls. 0 0
7004 OPENXML does not support retrieving schema from remote tables, as in '%.*ls'. 0 0
7005 OPENXML requires a metaproperty namespace to be declared if 'mp' is used for another namespace in sp_xml_preparedocument. 0 0
7006 OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement. 0 0
7007 OPENXML encountered unknown metaproperty '%.*ls'. 0 0
7008 The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag. 0 0
7009 OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument. 0 0
7101 You need an active user transaction in order to use text pointers for a table with the option "text in row" set to ON. 0 0
7102 Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE. 0 0
7104 Offset or size of data type is not valid. Data type must be of type int or smallint. 0 0
7105 The Database ID %d, Page %S_PGID, slot %d for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE. 0 0
7106 Internal error: An attempt was made to update a LOB data type using a read-only text pointer. 0 0
7107 You can have only 1,024 in-row text pointers in one transaction 0 0
7108 Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE. 0 0
7116 Offset %d is not in the range of available LOB data. 0 0
7117 Error reading large object (LOB) data from the tabular data stream (TDS). 0 0
7118 Only complete replacement is supported when assigning a large object (LOB) to itself. 0 0
7119 Attempting to grow LOB beyond maximum allowed size of %I64d bytes. 0 0
7122 Invalid text, ntext, or image pointer type. Must be binary(16). 0 0
7123 Invalid text, ntext, or image pointer value %hs. 0 0
7124 The offset and length specified in the READTEXT statement is greater than the actual data length of %ld. 0 0
7125 The text, ntext, or image pointer value conflicts with the column name specified. 0 0
7133 NULL textptr (text, ntext, or image pointer) passed to %ls function. 0 0
7134 LOB Locator is not supported as text pointer when using UPDATETEXT/WRITETEXT to update/write a text column. 0 0
7135 Deletion length %ld is not in the range of available text, ntext, or image data. 0 0
7137 %s is not allowed because the column is being processed by a concurrent snapshot or is being replicated to a non-SQL Server Subscriber or Published in a publication allowing Data Transformation Services (DTS) or tracked by Change Data Capture. 0 0
7138 The WRITETEXT statement is not allowed because the column is being replicated with Data Transformation Services (DTS) or tracked by Change Data Capture. 0 0
7139 Length of LOB data (%I64d) to be replicated exceeds configured maximum %ld. 0 0
7140 Cannot create additional orphans with the stored procedure sp_createorphan. Free up some of the orphan handles that you have created by inserting or deleting them. 0 0
7141 Must create orphaned text inside a user transaction. 0 0
7143 Invalid locator de-referenced. 0 0
7144 A text/ntext/image column referenced by a persisted or indexed computed column cannot be updated 0 0
7151 Insufficient buffer space to perform write operation. 0 0
7201 Could not execute procedure on remote server '%.*ls' because SQL Server is not configured for remote access. Ask your system administrator to reconfigure SQL Server to allow remote access. 0 0
7202 Could not find server '%.*ls' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. 0 0
7212 Could not execute procedure '%.*ls' on remote server '%.*ls'. 0 0
7213 The attempt by the provider to pass remote stored procedure parameters to remote server '%.*ls' failed. Verify that the number of parameters, the order, and the values passed are correct. 0 0
7214 Remote procedure time out of %d seconds exceeded. Remote procedure '%.*ls' is canceled. 0 0
7215 Could not execute statement on remote server '%.*ls'. 0 0
7221 Could not relay results of procedure '%.*ls' from remote server '%.*ls'. 0 0
7301 Cannot obtain the required interface ("%ls") from OLE DB provider "%ls" for linked server "%ls". 0 0
7302 Cannot create an instance of OLE DB provider "%ls" for linked server "%ls". 0 0
7303 Cannot initialize the data source object of OLE DB provider "%ls" for linked server "%ls". 0 0
7304 Cannot connect using OLE DB provider "%ls" to linked server "%ls". Verify the connection parameters or login credentials associated with this linked server. 0 0
7305 Cannot create a statement object using OLE DB provider "%ls" for linked server "%ls". 0 0
7306 Cannot open the table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7307 Cannot obtain the data source of a session from OLE DB provider "%ls" for linked server "%ls". This action must be supported by the provider. 0 0
7308 OLE DB provider '%ls' cannot be used for distributed queries because the provider is configured to run in single-threaded apartment mode. 0 0
7310 Cannot obtain the set of schema rowsets supported by OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a failure code when it is used. 0 0
7311 Cannot obtain the schema rowset "%ls" for OLE DB provider "%ls" for linked server "%ls". The provider supports the interface, but returns a failure code when it is used. 0 0
7312 Invalid use of schema or catalog for OLE DB provider "%ls" for linked server "%ls". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema. 0 0
7313 An invalid schema or catalog was specified for the provider "%ls" for linked server "%ls". 0 0
7314 The OLE DB provider "%ls" for linked server "%ls" does not contain the table "%ls". The table either does not exist or the current user does not have permissions on that table. 0 0
7315 The OLE DB provider "%ls" for linked server "%ls" contains multiple tables that match the name "%ls". 0 0
7316 Cannot use qualified table names (schema or catalog) with the OLE DB provider "%ls" for linked server "%ls" because it does not implement required functionality. 0 0
7317 The OLE DB provider "%ls" for linked server "%ls" returned an invalid schema definition. 0 0
7318 The OLE DB provider "%ls" for linked server "%ls" returned an invalid column definition for table "%ls". 0 0
7319 The OLE DB provider "%ls" for linked server "%ls" returned a "%ls" index "%ls" with the incorrect bookmark ordinal %d. 0 0
7320 Cannot execute the query "%ls" against OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7321 An error occurred while preparing the query "%ls" for execution against OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7322 A failure occurred while giving parameter information to OLE DB provider "%ls" for linked server "%ls". 0 0
7323 An error occurred while submitting the query text to OLE DB provider "%ls" for linked server "%ls". 0 0
7324 A failure occurred while setting parameter properties with OLE DB provider "%ls" for linked server "%ls". 0 0
7325 Objects exposing columns with CLR types are not allowed in distributed queries. Please use a pass-through query to access remote object '%ls'. 0 0
7330 Cannot fetch a row from OLE DB provider "%ls" for linked server "%ls". 0 0
7331 Rows from OLE DB provider "%ls" for linked server "%ls" cannot be released. 0 0
7332 Cannot rescan the result set from OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7333 Cannot fetch a row using a bookmark from OLE DB provider "%ls" for linked server "%ls". 0 0
7339 OLE DB provider '%ls' for linked server '%ls' returned invalid data for column '%ls.%ls'. 0 0
7340 Cannot create a column accessor for OLE DB provider "%ls" for linked server "%ls". 0 0
7341 Cannot get the current row value of column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7342 An unexpected NULL value was returned for column "%ls.%ls" from OLE DB provider "%ls" for linked server "%ls". This column cannot be NULL. 0 0
7343 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls". %ls 0 0
7344 The OLE DB provider "%ls" for linked server "%ls" could not %ls table "%ls" because of column "%ls". %ls 0 0
7345 The OLE DB provider "%ls" for linked server "%ls" could not delete from table "%ls". %ls 0 0
7346 Cannot get the data of the row from the OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7347 OLE DB provider '%ls' for linked server '%ls' returned data that does not match expected data length for column '%ls.%ls'. The (maximum) expected data length is %ls, while the returned data length is %ls. 0 0
7348 The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls". %ls. For possible cause of this issue, see the extended error message. 0 0
7349 The OLE DB provider "%ls" for linked server "%ls" could not set the range for table "%ls" because of column "%ls". %ls 0 0
7350 Cannot get the column information from OLE DB provider "%ls" for linked server "%ls". 0 0
7351 The OLE DB provider "%ls" for linked server "%ls" could not map ordinals for one or more columns of object "%ls". 0 0
7352 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. The object "%ls" was missing the expected column "%ls". 0 0
7353 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time. 0 0
7354 The OLE DB provider "%ls" for linked server "%ls" supplied invalid metadata for column "%ls". %ls 0 0
7355 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The name was changed at execution time. 0 0
7356 The OLE DB provider "%ls" for linked server "%ls" supplied inconsistent metadata for a column. The column "%ls" (compile-time ordinal %ld) of object "%ls" was reported to have a "%ls" of %ld at compile time and %ld at run time. 0 0
7357 Cannot process the object "%ls". The OLE DB provider "%ls" for linked server "%ls" indicates that either the object has no columns or the current user does not have permissions on that object. 0 0
7358 Cannot execute the query. The OLE DB provider "%ls" for linked server "%ls" did not provide an appropriate interface to access the text, ntext, or image column "%ls.%ls". 0 0
7359 The OLE DB provider "%ls" for linked server "%ls" reported a change in schema version between compile time ("%ls") and run time ("%ls") for table "%ls". 0 0
7360 Cannot get the length of a storage object from OLE DB provider "%ls" for linked server "%ls" for table "%ls", column "%ls". 0 0
7361 Cannot read a storage object from OLE DB provider "%ls" for linked server "%ls", for table "%ls", column "%ls". 0 0
7362 The OLE DB provider "%ls" for linked server "%ls" reported different metadata at run time for table "%ls", column "%ls". 0 0
7365 Cannot obtain optional metadata columns of columns rowset from OLE DB provider "%ls" for linked server "%ls". 0 0
7366 Cannot obtain columns rowset from OLE DB provider "%ls" for linked server "%ls". 0 0
7367 The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide the metadata column "%ls" at run time. 0 0
7368 The OLE DB provider "%ls" for linked server "%ls" supports column level collation, but failed to provide collation data for column "%ls". 0 0
7369 The OLE DB provider '%ls' for linked server '%ls' provided invalid collation. LCID = %08x, Compflags = %08x, SortOrder = '%.*ls'. 0 0
7370 One or more properties could not be set on the query for OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7371 The server option 'collation name' in linked server '%ls' for OLE DB provider '%ls' has collation id %08x which is not supported by SQL Server. 0 0
7372 Cannot get properties from OLE DB provider "%ls" for linked server "%ls". 0 0
7373 Cannot set the initialization properties for OLE DB provider "%ls" for linked server "%ls". 0 0
7374 Cannot set the session properties for OLE DB provider "%ls" for linked server "%ls". 0 0
7375 Cannot open index "%ls" on table "%ls" from OLE DB provider "%ls" for linked server "%ls". %ls 0 0
7376 Could not enforce the remote join hint for this query. 0 0
7377 Cannot specify an index hint for a remote data source. 0 0
7380 Table-valued parameters are not allowed in remote calls between servers. 0 0
7390 The requested operation could not be performed because OLE DB provider "%ls" for linked server "%ls" does not support the required transaction interface. 0 0
7391 The operation could not be performed because OLE DB provider "%ls" for linked server "%ls" was unable to begin a distributed transaction. 0 0
7392 Cannot start a transaction for OLE DB provider "%ls" for linked server "%ls". 0 0
7393 The OLE DB provider "%ls" for linked server "%ls" reported an error 0x%08X aborting the current transaction. 0 0
7394 The OLE DB provider "%ls" for linked server "%ls" reported an error committing the current transaction. 0 0
7395 Unable to start a nested transaction for OLE DB provider "%ls" for linked server "%ls". A nested transaction was required because the XACT_ABORT option was set to OFF. 0 0
7396 Varchar(max), nvarchar(max), varbinary(max) and large CLR type data types are not supported as return value or output parameter to remote queries. 0 0
7397 Remote function returned varchar(max), nvarchar(max), varbinary(max) or large CLR type value which is not supported. 0 0
7399 The OLE DB provider "%ls" for linked server "%ls" reported an error. %ls 0 0
7401 The OLE DB provider "%ls" returned invalid literal prefix/suffix string. 0 0
7403 The OLE DB provider "%ls" has not been registered. 0 0
7404 The server could not load DCOM. 0 0
7405 Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query. 0 0
7409 Could not start distributed query using integrated login because the user is logged in using SQL Server Authentication. Provide remote server login user ID and password in the connection string. 0 0
7410 Remote access is not allowed for impersonated security context. 0 0
7411 Server '%.*ls' is not configured for %ls. 0 0
7412 OLE DB provider "%ls" for linked server "%ls" returned message "%ls". 0 0
7413 Could not connect to linked server '%ls' (OLE DB Provider '%ls'). Enable delegation or use a remote SQL Server login for the current user. 0 0
7414 Invalid number of parameters. Rowset '%ls' expects %d parameter(s). 0 0
7415 Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server. 0 0
7416 Access to the remote server is denied because no login-mapping exists. 0 0
7417 GROUP BY ALL is not supported in queries that access remote tables if there is also a WHERE clause in the query. 0 0
7418 Text, image, or ntext column was too large to send to the remote data source due to the storage interface used by the provider. 0 0
7419 Lazy schema validation error. Linked server schema version has changed. Re-run the query. 0 0
7420 Remote access is not supported for transaction isolation level "%ls". 0 0
7421 Cannot fetch the rowset from OLE DB provider "%ls" for linked server "%ls". %ls. 0 0
7422 OLE DB provider "%ls" for linked server "%ls" returned an invalid index definition for table "%ls". 0 0
7423 The '%ls' OLE DB provider for the '%ls' linked server returned an invalid CLR type definition for the '%ls' table. 0 0
7424 OLE DB provider "%ls" for linked server "%ls" returned "%ls" with data type "%ls", which should be type "%ls". 0 0
7425 OLE DB provider "%ls" for linked server "%ls" returned an incorrect value for "%ls", which should be "%ls". 0 0
7426 OLE DB provider "%ls" for linked server "%ls" returned "%ls" without "%ls" being supported. 0 0
7427 OLE DB provider "%ls" for linked server "%ls" returned "%ls" for "%ls" during statistics gathering. 0 0
7428 OLE DB provider "%ls" for linked server "%ls" supported the schema lock interface, but returned "%ls" for "%ls". 0 0
7429 %hs SQL Server Remote Metadata Gather Time for Table %s.%s:%hs, CPU time = %lu ms, elapsed time = %lu ms. 0 0
7430 Out-of-process use of OLE DB provider "%ls" with SQL Server is not supported. 0 0
7431 Unable to delete OLE DB parameter properties. 0 0
7432 Heterogeneous queries and use of OLEDB providers are not supported in fiber mode. 0 0
7433 OLE DB provider '%ls' for linked server '%ls' returned truncated data for column '%ls.%ls'. The actual data length is %ls and truncated data length is %ls. 0 0
7435 The OLE DB provider "%ls" for linked server "%ls" returned unexpected NULL pointer for string column "%ls.%ls". 0 0
7601 Cannot use a CONTAINS or FREETEXT predicate on %S_MSG '%.*ls' because it is not full-text indexed. 0 0
7604 Full-text operation failed due to a time out. 0 0
7606 Could not find full-text index for database ID %d, table or indexed view ID %d. 0 0
7607 Search on full-text catalog '%ls' for database ID %d, table or indexed view ID %d with search condition '%ls' failed with unknown result (0x%x). 0 0
7608 An unknown full-text failure (0x%x) occurred during "%hs". 0 0
7609 Full-Text Search is not installed, or a full-text component cannot be loaded. 0 0
7610 Access is denied to "%.*ls", or the path is invalid. 0 0
7613 Cannot drop index '%.*ls' because it enforces the full-text key for table or indexed view '%.*ls'. 0 0
7614 Cannot alter or drop column '%.*ls' because it is enabled for Full-Text Search. 0 0
7615 A CONTAINS or FREETEXT predicate can only operate on one table or indexed view. Qualify the use of * with a table or indexed view name. 0 0
7616 Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. The functionality to disable and enable full-text search for a database is deprecated. Please change your application. 0 0
7617 Query does not reference the full-text indexed table or indexed view, or user does not have permission to perform this action. 0 0
7619 The execution of a full-text query failed. "%ls" 0 0
7620 The conversion to data type %ls failed for the full-text search key. 0 0
7621 Invalid use of full-text predicate in the HAVING clause. 0 0
7622 There is not sufficient disk space to complete this operation for the full-text catalog "%ls". 0 0
7624 Full-text catalog '%ls' is in an unusable state. Drop and re-create this full-text catalog. 0 0
7625 Full-text table or indexed view has more than one LCID among its full-text indexed columns. 0 0
7626 The top_n_by_rank argument ('%d') must be greater than or equal to zero. 0 0
7627 Cannot create the full-text catalog in the directory "%.*ls" for the clustered server. Only directories on a disk in the cluster group of the server can be used. 0 0
7629 Cannot open or query the full-text default path registry key. The full-text default catalog path is invalid. 0 0
7630 Syntax error near '%.*ls' in the full-text search condition '%.*ls'. 0 0
7632 The value of the Weight argument must be between 0.0 and 1.0. 0 0
7636 Warning: Request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently active for this table or indexed view. 0 0
7638 Warning: Request to stop change tracking has deleted all changes tracked on table or indexed view '%ls'. 0 0
7640 Warning: Request to stop tracking changes on table or indexed view '%.*ls' will not stop population currently in progress on the table or indexed view. 0 0
7641 Full-Text catalog '%ls' does not exist in database '%.*ls' or user does not have permission to perform this action. 0 0
7642 A full-text catalog named '%ls' already exists in this database. Use a different name. 0 0
7644 Full-text crawl manager has not been initialized. Any crawl started before the crawl manager was fully initialized will need to be restarted. Please restart SQL Server and retry the command. You should also check the error log to fix any failures that might have caused the crawl manager to fail. 0 0
7645 Null or empty full-text predicate. 0 0
7646 Fulltext predicate references columns from two different tables or indexed views '%.*ls' and '%.*ls' which is not allowed. 0 0
7647 Warning: Configuration of full-text catalog at '%ls' could not be saved during detach database. 0 0
7648 Warning: Failed to attach full-text catalog '%ls'. 0 0
7649 Warning: Failed to dismount full-text catalog at '%ls'. 0 0
7650 Warning: Failed to drop full-text catalog at '%ls'. 0 0
7651 Warning: The ongoing population is necessary to ensure an up-to-date index. If needed, stop change tracking first, and then deactivate the full-text index population. 0 0
7652 A full-text index for table or indexed view '%.*ls' has already been created. 0 0
7653 '%ls' is not a valid index to enforce a full-text search key. A full-text search key must be a unique, non-nullable, single-column index which is not offline, is not defined on a non-deterministic or imprecise nonpersisted computed column, does not have a filter, and has maximum size of %d bytes. Choose another index for the full-text key. 0 0
7654 Unable to obtain the population status of the table or indexed view '%.*ls'. 0 0
7655 TYPE COLUMN option must be specified with column of image or varbinary(max) type. 0 0
7656 Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode. 0 0
7657 Warning: Table or indexed view '%.*ls' has full-text indexed columns that are of type image, text, or ntext. Full-text change tracking cannot track WRITETEXT or UPDATETEXT operations performed on these columns. 0 0
7658 Table or indexed view '%.*ls' does not have a full-text index or user does not have permission to perform this action. 0 0
7659 Cannot activate full-text search for table or indexed view '%.*ls' because no columns have been enabled for full-text search. 0 0
7660 Full-text search must be activated on table or indexed view '%.*ls' before this operation can be performed. 0 0
7661 Warning: Full-text change tracking is currently enabled for table or indexed view '%.*ls'. 0 0
7662 Warning: Full-text auto propagation is currently enabled for table or indexed view '%.*ls'. 0 0
7663 Option 'WITH NO POPULATION' should not be used when change tracking is enabled. 0 0
7664 Full-text change tracking must be started on table or indexed view '%.*ls' before the changes can be flushed. 0 0
7665 Full Crawl must be executed on table or indexed view '%.*ls'. Columns affecting the index have been added or dropped since the last index full population. 0 0
7666 User does not have permission to perform this action. 0 0
7668 Cannot drop full-text catalog '%ls' because it contains a full-text index. 0 0
7669 Warning: Full-text index for table or indexed view '%.*ls' cannot be populated because the database is in single-user access mode. Change tracking is stopped for this table or indexed view. 0 0
7670 Column '%.*ls' cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column. 0 0
7671 Column '%.*ls' cannot be used as full-text type column for image column. It must be a character-based column with a size less or equal than %d characters. 0 0
7672 A full-text index cannot be created on the table or indexed view because duplicate column '%.*ls' is specified. 0 0
7673 Warning: Full-text change tracking is currently disabled for table or indexed view '%.*ls'. 0 0
7674 Warning: The fulltext catalog '%.*ls' is being dropped and is currently set as default. 0 0
7676 Warning: Full-text auto propagation is on. Stop crawl request is ignored. 0 0
7677 Column "%.*ls" is not full-text indexed. 0 0
7678 The following string is not defined as a language alias in syslanguages: %.*ls. 0 0
7679 Full-text index language of column "%.*ls" is not a language supported by full-text search. 0 0
7680 Default full-text index language is not a language supported by full-text search. 0 0
7681 Warning: Directory '%ls' does not have a valid full-text catalog. Full-text catalog header file or attach state file either is missing or corrupted. The full-text catalog cannot be attached. 0 0
7682 The component '%ls' reported error while indexing. Component path '%ls'. 0 0
7683 Errors were encountered during full-text index population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Please see full-text crawl logs for details. 0 0
7684 Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Failed to index the row. 0 0
7685 Error '%ls' occurred during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Attempt will be made to reindex it. 0 0
7689 Execution of a full-text operation failed. '%ls' 0 0
7690 Full-text operation failed because database is read only. 0 0
7691 Access is denied to full-text log path. Full-text logging is disabled for database '%ls', catalog '%ls' (database ID '%d', catalog ID '%d'). 0 0
7692 Full-text catalog path '%.*ls' exceeded %d character limit. 0 0
7693 Full-text initialization failed to create a memory clerk. 0 0
7694 Failed to pause catalog for backup. Backup was aborted. 0 0
7696 Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed. 0 0
7697 Warning: Full-text index on table or indexed view '%.*ls' in database '%.*ls' has been changed after full-text catalog files backup. A full population is required to bring full-text index to a consistent state. 0 0
7698 GROUP BY ALL cannot be used in full text search queries. 0 0
7699 TYPE COLUMN option is not allowed for column types other than image or varbinary(max). 0 0
7702 Empty Partition function type-parameter-list is not allowed when defining a partition function. 0 0
7703 Can not create RANGE partition function with multiple parameter types. 0 0
7704 The type '%.*ls' is not valid for this operation. 0 0
7705 Could not implicitly convert range values type specified at ordinal %d to partition function parameter type. 0 0
7706 Partition function '%ls' is being used by one or more partition schemes. 0 0
7707 The associated partition function '%ls' generates more partitions than there are file groups mentioned in the scheme '%ls'. 0 0
7708 Duplicate range boundary values are not allowed in partition function boundary values list. Partition boundary values at ordinal %d and %d are equal. 0 0
7709 Warning: Range value list for partition function '%.*ls' is not sorted by value. Mapping of partitions to filegroups during CREATE PARTITION SCHEME will use the sorted boundary values if the function '%.*ls' is referenced in CREATE PARTITION SCHEME. 0 0
7710 Warning: The partition scheme '%.*ls' does not have any next used filegroup. Partition scheme has not been changed. 0 0
7711 The DATA_COMPRESSION option was specified more than once for the table, or for at least one of its partitions if the table is partitioned. 0 0
7712 Partition scheme '%.*ls' has been created successfully. '%.*ls' is marked as the next used filegroup in partition scheme '%.*ls'. 0 0
7713 %d filegroups specified after the next used filegroup are ignored. 0 0
7714 Partition range value is missing. 0 0
7715 The specified partition range value could not be found. 0 0
7716 Can not create or alter a partition function to have zero partitions. 0 0
7717 The partition scheme "%.*ls" is currently being used to partition one or more tables. 0 0
7718 Partition range value cannot be specified for hash partitioning. 0 0
7719 CREATE/ALTER partition function failed as only a maximum of %d partitions can be created. 0 0
7720 Data truncated when converting range values to the partition function parameter type. The range value at ordinal %d requires data truncation. 0 0
7721 Duplicate range boundary values are not allowed in partition function boundary values list. The boundary value being added is already present at ordinal %d of the boundary value list. 0 0
7722 Invalid partition number %I64d specified for %S_MSG '%.*ls', partition number can range from 1 to %d. 0 0
7723 Only a single filegroup can be specified while creating partition scheme using option ALL to specify all the filegroups. 0 0
7724 Computed column cannot be used as a partition key if it is not persisted. Partition key column '%.*ls' in table '%.*ls' is not persisted. 0 0
7725 Alter partition function statement failed. Cannot repartition table '%.*ls' by altering partition function '%.*ls' because its clustered index '%.*ls' is disabled. 0 0
7726 Partition column '%.*ls' has data type %s which is different from the partition function '%.*ls' parameter data type %s. 0 0
7727 Collation of partition column '%.*ls' does not match collation of corresponding parameter in partition function '%.*ls'. 0 0
7728 Invalid partition range: %d TO %d. Lower bound must not be greater than upper bound. 0 0
7729 Cannot specify partition number in the %S_MSG %S_MSG statement as the %S_MSG '%.*ls' is not partitioned. 0 0
7730 Alter %S_MSG statement failed because partition number %d does not exist in %S_MSG '%.*ls'. 0 0
7731 Cannot specify partition number in Alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls'. 0 0
7732 Cannot specify partition number in Alter index statement along with keyword ALL to rebuild partitions of table '%.*ls' when the table does not have any regular indexes. 0 0
7733 '%ls' statement failed. The %S_MSG '%.*ls' is partitioned while %S_MSG '%.*ls' is not partitioned. 0 0
7734 The %S_MSG '%.*ls' specified for the clustered index '%.*ls' was used for table '%.*ls' even though %S_MSG '%.*ls' is specified for it. 0 0
7735 Cannot specify partition number in alter %S_MSG statement to rebuild or reorganize a partition of %S_MSG '%.*ls' as %S_MSG is not partitioned. 0 0
7736 Partition function can only be created in Enterprise edition of SQL Server. Only Enterprise edition of SQL Server supports partitioning. 0 0
7737 Filegroup %.*ls is of a different filegroup type than the first filegroup in partition scheme %.*ls 0 0
7738 Cannot enable compression for object '%.*ls'. Only SQL Server Enterprise Edition supports compression. 0 0
7801 The required parameter %.*ls was not specified. 0 0
7802 Functions that have a return type of "%.*ls" are unsupported through SOAP invocation. 0 0
7803 The clause %.*ls can not be used in the %.*ls statement. 0 0
7804 %.*ls and %.*ls can not share the same value. 0 0
7805 The parameter SITE can not be prefixed by a scheme such as 'http://'. Valid values for SITE include {'*' | '+' | 'site_name'}. 0 0
7806 The URL specified by endpoint '%.*ls' is already registered to receive requests or is reserved for use by another service. 0 0
7807 An error ('0x%x') occurred while attempting to register the endpoint '%.*ls'. 0 0
7808 The endpoint '%.*ls' could not be unregistered. 0 0
7809 Cannot find the object '%.*ls', because it does not exist or you do not have permission. 0 0
7810 The value '%d' is not within range for the '%.*ls' parameter. 0 0
7811 COMPUTE BY queries are not supported over SOAP. 0 0
7812 The endpoint '%.*ls' has been established in metadata, but HTTP listening has not been enabled because HTTP support did not start successfully. Verify that the operating system and the edition of SQL Server supports native HTTP access. Check the SQL Server error log for any errors that might have occurred while starting HTTP support. 0 0
7813 The parameter PATH must be supplied in its canonical form. An acceptable PATH is '%.*ls'. 0 0
7814 The specified value '%.*ls' already exists. 0 0
7815 The specified value '%.*ls' does not exist. 0 0
7816 A duplicate parameter was specified, '%.*ls'. 0 0
7817 The Base64 encoded input data was malformed for the parameter "%.*ls". 0 0
7818 The request exceeds an internal limit. Simplify or reduce the size of the request. 0 0
7819 The SOAP method object '%.*ls' must be specified using a fully qualified three-part name. 0 0
7820 SOAP namespaces beginning with '%.*ls' are disallowed because they are reserved for system use. 0 0
7821 Cannot find the database '%.*ls', because it does not exist or you do not have permission. 0 0
7822 An unexpected XML node "%.*ls" (in the namespace "%.*ls") was found in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 0 0
7823 The "%.*ls" XML element (in the "%.*ls" namespace) was expected in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 0 0
7824 The "%.*ls" XML element (in the "%.*ls" namespace) was expected as the topmost node of the SOAP request. 0 0
7825 A SOAP method element was expected in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 0 0
7826 Unexpected character data was found in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 0 0
7827 The user does not have permission to reserve and unreserve HTTP namespaces. 0 0
7828 The statement is not supported on this version of the operating system. Could not find Httpapi.dll in the path. 0 0
7829 The statement is not supported on this version of the operating system. Could not find function entry point '%.*ls' in Httpapi.dll. 0 0
7830 Unable to complete the operation because of an unexpected error. 0 0
7831 A reservation for this HTTP namespace (%.*ls) already exists. 0 0
7832 A reservation for this HTTP namespace (%.*ls) does not exist. 0 0
7833 The HTTP namespace (%.*ls) is in an invalid format. Specify the namespace in its canonical form. 0 0
7834 The reservation for the HTTP namespace (%.*ls) has been deleted. If there are any endpoints associated with this namespace, they will continue to receive and process requests until the server is restarted. 0 0
7835 Endpoint '%.*ls' has been disabled because it is insecurely configured. For a more information, attempt to start the endpoint using the ALTER ENDPOINT statement. 0 0
7836 A fatal error occurred while reading the input stream from the network. The maximum number of network packets in one request was exceeded. Try using bulk insert, increasing network packet size, or reducing the size of the request. The session will be terminated. 0 0
7847 XML data was found in the parameter '%.*ls' which is not an XML parameter. Please entitize any invalid XML character data in this parameter, or pass the parameter in typed as XSD:anyType or sqltypes:xml. 0 0
7848 An invalid or unsupported localeId was specified for parameter "%.*ls". 0 0
7849 Invalid sqlCompareOptions were specified for parameter "%.*ls". 0 0
7850 The SQL Server Service account does not have permission to register the supplied URL on the endpoint '%.*ls'. Use sp_reserve_http_namespace to explicitly reserve the URL namespace before you try to register the URL again. 0 0
7851 The %.*ls attribute must be specified on the %.*ls element of the parameter "%.*ls" because it is of type %.*ls. 0 0
7852 Parameter "%.*ls": If the %.*ls attribute appears on a parameter value node of type "%.*ls" (in the namespace "%.*ls"), it must refer to a CLR type. 0 0
7853 The URL specified as the path ("%.*ls") is not in an absolute format, and must begin with "%.*ls". 0 0
7854 The URL value specified for the "%.*ls" parameter is too long. 0 0
7855 Reading from HTTP input stream failed. 0 0
7856 XML parameters do not support non-unicode element or attribute values. 0 0
7857 Parameter "%.*ls": Function or procedure parameters with improperly formatted or deprecated names are not supported through Native SOAP access. Refer to documentation for rules concerning the proper naming of parameters. 0 0
7858 The "%.*ls" XML element (in the "%.*ls" namespace) in the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request contained an invalid binary type. 0 0
7859 Parameter "%.*ls": Parameter collation cannot be specified on the "%.*ls" node (in the namespace "%.*ls"). 0 0
7860 An endpoint's transport or content cannot be changed through the ALTER ENDPOINT statement. Use DROP ENDPOINT and execute the CREATE ENDPOINT statement to make these changes. 0 0
7861 %.*ls endpoints can only be of the "FOR %.*ls" type. 0 0
7862 An endpoint of the requested type already exists. Only one endpoint of this type is supported. Use ALTER ENDPOINT or DROP the existing endpoint and execute the CREATE ENDPOINT statement. 0 0
7863 The endpoint was not changed. The ALTER ENDPOINT statement did not contain any values to modify or update. 0 0
7864 CREATE/ALTER ENDPOINT cannot be used to update the endpoint with this information. The Dedicated Administrator Connection endpoint is reserved and cannot be updated. 0 0
7865 Web Services Description Language (WSDL) generation failed because the system was unable to query the metadata for the endpoint. 0 0
7866 XML attribute and element values larger than 4000 characters are only allowed within the SOAP Body node. 0 0
7867 An invalid sqlCollationVersion was specified for parameter "%.*ls". 0 0
7868 An invalid sqlSortId was specified for parameter "%.*ls". 0 0
7869 The endpoint name '%.*ls' is reserved for used by SQL. Endpoint names cannot begin with '%.*ls'. 0 0
7870 The AFFINITY clause is not supported for endpoints of this type. 0 0
7871 The clause "%.*ls" is not valid for this endpoint type. 0 0
7872 %.*ls is not a parameter for procedure "%.*ls", or it was supplied out of order. 0 0
7873 The endpoint "%.*ls" is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP Transact-SQL endpoints. 0 0
7874 An endpoint already exists with the bindings specified. Only one endpoint supported for a specific binding. Use ALTER ENDPOINT or DROP the existing endpoint and execute the CREATE ENDPOINT statement. 0 0
7875 An unexpected XML construct was found in the character data of the "%.*ls" element (in the "%.*ls" namespace) of the SOAP request. 0 0
7878 This "%.*ls ENDPOINT" statement is not supported on this edition of SQL Server. 0 0
7879 SQL Server is waiting for %d remaining sessions and connections to close. If these sessions are not closed within a reasonable amount of time, "polite" shutdown will be aborted. This message may appear several times before SQL Server is shutdown. 0 0
7880 SQL Server has successfully finished closing sessions and connections. 0 0
7881 SQL Server was unable to close sessions and connections in a reasonable amount of time and is aborting "polite" shutdown. 0 0
7882 OUTPUT was requested for parameter '%.*ls', which is not supported for a WEBMETHOD with FORMAT=NONE. 0 0
7883 User-defined functions cannot be used for a WEBMETHOD with FORMAT=NONE. 0 0
7884 Violation of tabular data stream (TDS) protocol. This is most often caused by a previous exception on this task. The last exception on the task was error %d, severity %d, address 0x%p. This connection will be terminated. 0 0
7885 Network error 0x%lx occurred while sending data to the client on process ID %d batch ID %d. A common cause for this error is if the client disconnected without reading the entire response from the server. This connection will be terminated. 0 0
7886 A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated. 0 0
7887 The IPv6 address specified is not supported. Only addresses that are in their numeric, canonical form are supported for listening. 0 0
7888 The IPv6 address specified is not supported. The server may not be configured to allow for IPv6 connectivity, or the address may not be in a recognized IPv6 format. 0 0
7889 The SOAP headers on the request have exceeded the size limits established for this endpoint. The endpoint owner may increase these limits via ALTER ENDPOINT. 0 0
7890 An error occurred while attempting to register the endpoint '%.*ls'. One or more of the ports specified in the CREATE ENDPOINT statement may be bound to another process. Attempt the statement again with a different port or use netstat to find the application currently using the port and resolve the conflict. 0 0
7891 Creation of a TSQL endpoint will result in the revocation of any 'Public' connect permissions on the '%.*ls' endpoint. If 'Public' access is desired on this endpoint, reapply this permission using 'GRANT CONNECT ON ENDPOINT::[%.*ls] to [public]'. 0 0
7892 Internal subset DTDs inside SOAP requests are not allowed. 0 0
7893 Parameter '%.*ls': Incompatible XML attributes were present. The '%.*ls' attribute and the '%.*ls' attribute may not both be present on a parameter value node of type '%.*ls' (in the namespace '%.*ls'). 0 0
7894 Listening has not been started on the endpoint '%.*ls' found in metadata. Endpoint operations are disabled on this edition of SQL Server. 0 0
7895 Only a system administrator can specify a custom WSDL stored procedure on the endpoint. 0 0
7896 The column or parameter '%.*ls' uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. 0 0
7897 Creating and altering SOAP endpoints will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
7898 SQL Server native SOAP support is now deprecated and will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 0 0
7899 The return value uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server 2005 or earlier. 0 0
7901 The repair statement was not processed. This level of repair is not supported when the database is in emergency mode. 0 0
7903 Table error: The orphaned file "%.*ls" was found in the FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d, column ID %d. 0 0
7904 Table error: Cannot find the FILESTREAM file "%.*ls" for column ID %d (column directory ID %.*ls) in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d. 0 0
7905 Database error: The directory "%.*ls" is not a valid FILESTREAM directory. 0 0
7906 Database error: The file "%.*ls" is not a valid FILESTREAM file. 0 0
7907 Table error: The directory "%.*ls" under the rowset directory ID %.*ls is not a valid FILESTREAM directory. 0 0
7908 Table error: The file "%.*ls" in the rowset directory ID %.*ls is not a valid FILESTREAM file. 0 0
7909 The emergency-mode repair failed.You must restore from backup. 0 0
7910 Repair: The page %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
7911 Repair: The page %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
7912 Repair: The extent %S_PGID has been allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
7913 Repair: The extent %S_PGID has been deallocated from object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
7914 Repair: %ls page at %S_PGID has been rebuilt. 0 0
7915 Repair: IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), has been truncated before page %S_PGID and will be rebuilt. 0 0
7916 Repair: Deleted record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), on page %S_PGID, slot %d. Indexes will be rebuilt. 0 0
7917 Repair: Converted forwarded record for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), at page %S_PGID, slot %d to a data row. 0 0
7918 Repair: Page %S_PGID next and %S_PGID previous pointers have been set to match each other in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). 0 0
7919 Repair statement not processed. Database needs to be in single user mode. 0 0
7920 Processed %ld entries in system catalog for database ID %d. 0 0
7921 Repair statement not processed. Database cannot be a snapshot. 0 0
7923 Table %.*ls Object ID %ld. 0 0
7924 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). FirstIAM %S_PGID. Root %S_PGID. Dpages %I64d. 0 0
7925 Index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). %I64d pages used in %I64d dedicated extents. 0 0
7926 Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details. 0 0
7927 Total number of extents is %I64d. 0 0
7928 The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline. 0 0
7929 Check statement aborted. Database contains deferred transactions. 0 0
7930 Mirroring must be removed from the database for this DBCC command. 0 0
7931 Database error: The FILESTREAM directory ID %.*ls for a partition was seen two times. 0 0
7932 Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d is in filegroup %d, but should be in filegroup %d. 0 0
7933 Table error: A FILESTREAM directory ID %.*ls exists for a partition, but the corresponding partition does not exist in the database. 0 0
7934 Table error: The FILESTREAM directory ID %.*ls for object ID %d, index ID %d, partition ID %I64d was not found. 0 0
7935 Table error: A FILESTREAM directory ID %.*ls exists for a column of object ID %d, index ID %d, partition ID %I64d, but that column does not exist in the partition. 0 0
7936 Table error: The FILESTREAM directory ID %.*ls exists for column ID %d of object ID %d, index ID %d, partition ID %I64d, but that column is not a FILESTREAM column. 0 0
7937 Table error: The FILESTREAM directory ID %.*ls for column ID %d of object ID %d, index ID %d, partition ID %I64d was not found. 0 0
7938 Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name "%.*ls" twice in the column directory %d (for column ID %d). 0 0
7939 Cannot detach database '%.*ls' because it does not exist. 0 0
7940 System databases master, model, msdb, and tempdb cannot be detached. 0 0
7941 Table error: object ID %d, index ID %d, partition ID %I64d processing encountered file name "%.*ls" twice in the column ID %d (for column directory %d). 0 0
7942 DBCC %ls scanning '%.*ls' table... 0 0
7943 Table: '%.*ls' (%d); index ID: %d, database ID: %d 0 0
7944 %ls level scan performed. 0 0
7945 - Pages Scanned................................: %I64d 0 0
7946 - Extents Scanned..............................: %I64d 0 0
7947 - Extent Switches..............................: %I64d 0 0
7948 - Avg. Pages per Extent........................: %3.1f 0 0
7949 - Scan Density [Best Count:Actual Count].......: %4.2f%ls [%I64d:%I64d] 0 0
7950 - Logical Scan Fragmentation ..................: %4.2f%ls 0 0
7951 Warning: Could not complete filestream consistency checks due to an operating system error. Any consistency errors found in the filestream subsystem will be silenced. Please refer to other errors for more information. This condition is likely transient; try rerunning the command. 0 0
7952 - Extent Scan Fragmentation ...................: %4.2f%ls 0 0
7953 - Avg. Bytes Free per Page.....................: %3.1f 0 0
7954 - Avg. Page Density (full).....................: %4.2f%ls 0 0
7955 Invalid SPID %d specified. 0 0
7957 Cannot display the specified SPID's buffer; in transition. 0 0
7958 The specified SPID does not process input/output data streams. 0 0
7960 An invalid server process identifier (SPID) %d or batch ID %d was specified. 0 0
7961 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) , page ID %S_PGID, row ID %d. Column '%.*ls' is a var column with a NULL value and non-zero data length 0 0
7962 Invalid BATCHID %d specified. 0 0
7963 Database error: The file "%.*ls" is not a valid FILESTREAM LOG file. 0 0
7964 Repair: Deleted FILESTREAM file "%.*ls" for column ID %d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d. 0 0
7965 Table error: Could not check object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) page(s). 0 0
7966 Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped. 0 0
7968 Transaction information for database '%.*ls'. 0 0
7969 No No active open transactions. 0 0
7970 %hsOldest active transaction: 0 0
7971 SPID (server process ID): %d%s 0 0
7972 UID (user ID) : %d 0 0
7974 Name : %.*ls 0 0
7975 LSN : (%d:%d:%d) 0 0
7977 Start time : %.*ls 0 0
7978 SID : %.*ls 0 0
7979 %hsReplicated Transaction Information: 0 0
7980 Oldest distributed LSN : (%d:%d:%d) 0 0
7982 Oldest non-distributed LSN : (%d:%d:%d) 0 0
7983 User '%.*ls' does not have permission to run DBCC %ls for database '%.*ls'. 0 0
7984 System table pre-checks: Object ID %d. Page %S_PGID has unexpected page type %d. Check statement terminated due to unrepairable error. 0 0
7985 System table pre-checks: Object ID %d. Could not read and latch page %S_PGID with latch type %ls. Check statement terminated due to unrepairable error. 0 0
7986 System table pre-checks: Object ID %d has cross-object chain linkage. Page %S_PGID points to %S_PGID in alloc unit ID %I64d (should be %I64d). Check statement terminated due to unrepairable error. 0 0
7987 System table pre-checks: Object ID %d has chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->prev = %S_PGID. Check statement terminated due to unrepairable error. 0 0
7988 System table pre-checks: Object ID %d. Loop in data chain detected at %S_PGID. Check statement terminated due to unrepairable error. 0 0
7992 Cannot shrink 'read only' database '%.*ls'. 0 0
7993 Cannot shrink file '%d' in database '%.*ls' to %u pages as it only contains %u pages. 0 0
7995 Database '%.*ls': consistency errors in system catalogs prevent further DBCC %ls processing. 0 0
7996 Extended stored procedures can only be created in the master database. 0 0
7997 '%.*ls' does not contain an identity column. 0 0
7998 Checking identity information: current identity value '%.*hs', current column value '%.*hs'. 0 0
7999 Could not find any index named '%.*ls' for table '%.*ls'. 0 0
19030 SQL Trace ID %d was started by login "%s". 0 0
19031 SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'. 0 0
19032 SQL Trace was stopped due to server shutdown. Trace ID = '%d'. This is an informational message only; no user action is required. 0 0
19033 Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required. 0 0
19034 Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls 0 0
19035 OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured. 0 0
19036 The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider. 0 0
19051 Unknown error occurred in the trace. 0 0
19052 The active trace must be stopped before modification. 0 0
19053 The trace event ID is not valid. 0 0
19054 The trace column ID is not valid. 0 0
19055 Filters with the same event column ID must be grouped together. 0 0
19056 The comparison operator in the filter is not valid. 0 0
19057 The boolean operator in the filter is not valid. 0 0
19058 The trace status is not valid. 0 0
19059 Could not find the requested trace. 0 0
19060 The trace option is not valid. 0 0
19061 Cannot remove SPID trace column. 0 0
19062 Could not create a trace file. 0 0
19063 Not enough memory was available for trace. 0 0
19064 The requested trace stop time has been already passed. 0 0
19065 The parameter is not valid. 0 0
19066 Cannot modify a restricted trace. 0 0
19067 Cannot create a new trace because the trace file path is found in the existing traces. 0 0
19068 The trace file path is not valid or not supported. 0 0
19069 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. 0 0
19070 The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off. 0 0
19071 Stopping the trace because the current trace file is full and the rollover option is not specified. 0 0
19096 Fail to delete an old trace file '%ls'. Error = '%ls'. 0 0
19097 Windows error occurred while running %s. Error = %s. 0 0
19098 An error occurred starting the default trace. Cause: %ls Use sp_configure to turn off and then turn on the 'default trace enabled' advanced server configuration option. 0 0
19099 Trace ID '%d' was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem. 0 0
19100 Initialization succeeded. 0 0
19101 Initialization failed with an infrastructure error. Check for previous errors. 0 0
19102 Unable to create a node listener object. Check for memory-related errors. 0 0
19103 An error occurred while starting shared memory support. 0 0
19104 All protocols are disabled. 0 0
19105 Unable to create a node listener object for a special instance. Check for memory-related errors. 0 0
19106 Unable to trim spaces in an IP address. Check TCP/IP protocol settings. 0 0
19107 'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings. 0 0
19108 Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings. 0 0
19109 Unable to configure MDAC-compatibility TCP/IP port in registry. 0 0
19110 Unable to initialize the TCP/IP listener. 0 0
19111 Unable to open TCP/IP protocol configuration key in registry. 0 0
19112 Unable to retrieve TCP/IP protocol 'Enabled' registry setting. 0 0
19113 Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting. 0 0
19114 Unable to open TCP/IP protocol's 'IPAll' configuration key in registry. 0 0
19115 Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. 0 0
19116 Unable to obtain list size for IP addresses configured for listening in registry. 0 0
19117 Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors. 0 0
19118 Unable to obtain list of IP addresses configured for listening in registry. 0 0
19119 Unable to open TCP/IP protocol's registry key for a specific IP address. 0 0
19120 Unable to retrieve 'Enabled' setting for a specific IP address. 0 0
19121 Unable to retrieve 'Active' setting for a specific IP address. 0 0
19122 Unable to retrieve 'IpAddress' value for a specific IP address. 0 0
19123 'IpAddress' registry value is the wrong type. 0 0
19124 Unable to retrieve registry settings for a specific IP address. 0 0
19125 Unable to deallocate structures representing registry key for a specific IP address. 0 0
19126 Unable to retrieve registry settings for cluster environment. 0 0
19127 Server is configured to listen on a specific IP address in a cluster environment. 0 0
19128 Unable to check for a duplicate IP address in the network. 0 0
19129 A duplicate IP address was detected in the network. 0 0
19130 Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings. 0 0
19131 Unable to open Dedicated Administrator Connection configuration key in registry. 0 0
19132 Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry. 0 0
19133 Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection. 0 0
19134 No No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings. 0 0
19135 Error starting Named Pipes support. Check protocol settings. 0 0
19136 An error occurred starting VIA support. Check protocol settings. 0 0
19137 Failed to allocate memory SSL listening structures. Check for memory-related errors. 0 0
19138 An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager. 0 0
19139 Unable to add listener endpoints. Check for memory-related errors. 0 0
19140 Unable to initialize the communication listeners. 0 0
19141 Unable to retrieve SQL Server Network Interface library settings for a special instance. 0 0
19142 Unable to retrieve SQL Server Network Interface library settings; the instance name is too long. 0 0
19143 Unable to initialize the Shared Memory listener. 0 0
19144 Unable to initialize the Named Pipes listener. 0 0
19145 Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. 0 0
19146 Unable to initialize the VIA listener. 0 0
19147 Unable to initialize the HTTP listener. 0 0
19148 Unable to initialize SSL support. 0 0
19149 Unable to configure MDAC-compatibility protocol list in registry. 0 0
19150 Unable to open SQL Server Network Interface library configuration key in registry. 0 0
14002 Could not find the 'Sync' subsystem with the task ID %ld. 0 0
14003 You must supply a publication name. 0 0
14004 %s must be in the current database. 0 0
14005 Cannot drop the publication because at least one subscription exists for this publication. Drop all subscriptions to the publication before attempting to drop the publication. If the problem persists, replication metadata might be incorrect; consult Books Online for troubleshooting information. 0 0
14006 Could not drop the publication. 0 0
14008 There are no publications. 0 0
14009 There are no articles for publication '%s'. 0 0
14010 The remote server '%s' is not defined as a subscription server. Ensure you specify the server name rather than a network alias. 0 0
14011 Unable to mark server '%s' as a non SQL Server subscriber. 0 0
14012 The @status parameter value must be either 'active' or 'inactive'. 0 0
14013 This database is not enabled for publication. 0 0
14014 The synchronization method (@sync_method) must be '[bcp] native', '[bcp] character', 'concurrent', 'concurrent_c', 'database snapshot', or 'database snapshot character'. 0 0
14015 The replication frequency (@repl_freq) must be either 'continuous' or 'snapshot'. 0 0
14016 The publication '%s' already exists. 0 0
14017 Invalid @restricted parameter value. Valid options are 'true' or 'false'. 0 0
14018 Could not create the publication. 0 0
14019 The @operation parameter value must be either add, drop, or alter. 0 0
14020 Could not obtain the column ID for the specified column. Schema replication failed. 0 0
14021 The column was not added correctly to the article. 0 0
14022 The @property parameter value must be either 'description', 'sync_object', 'type', 'ins_cmd', 'del_cmd', 'upd_cmd', 'filter', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'status', 'schema_option', or 'destination_owner'. 0 0
14023 The type must be '[indexed view ]logbased[ (manualview|manualfilter|manualboth)]', '[serializable ]proc exec', or '(view|indexed view|proc|func|aggregate|synonym) schema only'. 0 0
14024 The value of property 'subscriber_provider' cannot be NULL. 0 0
14025 Article update successful. 0 0
14026 The value of property 'subscriber_type is not a supported heterogeneous subscriber type. The value must be 1 (ODBC subscriber), or 3 (OLEDB subscriber). 0 0
14027 %s does not exist in the current database. 0 0
14028 Only user tables, materialized views, and stored procedures can be published as 'logbased' articles. 0 0
14029 The vertical partition switch must be either 'true' or 'false'. 0 0
14030 The article '%s' exists in publication '%s'. 0 0
14031 User tables and views are the only valid synchronization objects. 0 0
14032 The value of parameter %s cannot be 'all'. It is reserved by replication stored procedures. 0 0
14033 Could not change replication frequency because there are active subscriptions on the publication. 0 0
14034 The publication name (@publication) cannot be the keyword 'all'. 0 0
14035 The replication option '%s' of database '%s' has already been set to true. 0 0
14036 Could not enable database for publishing. 0 0
14037 The replication option '%s' of database '%s' has been set to false. 0 0
14038 Could not disable database for publishing. 0 0
14039 Could not construct column clause for article view. Reduce the number of columns or create the view manually. 0 0
14040 The server '%s' is already a Subscriber. 0 0
14041 The '%s' property can only be changed if the publication is enabled for heterogeneous subscriptions. The publication is not enabled. 0 0
14042 Could not create Subscriber. 0 0
14043 The parameter %s passed to stored procedure %s cannot be NULL. 0 0
14044 Unable to clear subscriber status for the server. 0 0
14045 Unable to update subscriber_type in MSdistribution_agents table. 0 0
14046 Could not drop article. A subscription exists on it. 0 0
14047 Could not drop %s. 0 0
14048 The server '%s' is not a Subscriber. 0 0
14049 Stored procedures for replication are the only objects that can be used as a filter. 0 0
14050 No No subscription is on this publication or article. 0 0
14051 The parameter value must be 'sync_type' or 'dest_db'. 0 0
14052 The @sync_type parameter value must be "automatic", "none", "replication support only", "initialize with backup", or "initialize from lsn". 0 0
14053 The subscription could not be updated at this time. 0 0
14054 The subscription was updated successfully. 0 0
14055 The subscription does not exist. 0 0
14056 The subscription could not be dropped at this time. 0 0
14057 The subscription could not be created. 0 0
14058 Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information. 0 0
14059 Materialized view articles cannot be created for publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts. 0 0
14060 Subscriber parameters specifying provider properties must be NULL for SQL Server subscribers. 0 0
14061 The @pre_creation_cmd parameter value must be 'none', 'drop', 'delete', or 'truncate'. 0 0
14062 The Subscriber was dropped. 0 0
14063 The remote server does not exist or has not been designated as a valid Subscriber. 0 0
14065 The @status parameter value must be 'initiated', 'active', 'inactive', or 'subscribed'. 0 0
14066 The previous status must be 'active', 'inactive', or 'subscribed'. 0 0
14067 The status value is the same as the previous status value. 0 0
14068 The subscription status of the object could not be changed. 0 0
14069 Could not update sysarticles. The subscription status could not be changed. 0 0
14070 Could not update the distribution database subscription table. The subscription status could not be changed. 0 0
14071 Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor. 0 0
14074 The server '%s' is already listed as a Publisher. 0 0
14075 The Publisher could not be created at this time. 0 0
14076 Could not grant replication login permission to '%s'. 0 0
14077 The publication was updated successfully. 0 0
14078 The parameter must be 'description', 'taskid', 'sync_method', 'status', 'repl_freq', 'restricted', 'retention', 'immediate_sync', 'enabled_for_internet', 'allow_push', 'allow_pull', 'allow_anonymous', or 'retention'. 0 0
14080 The remote server "%s" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers. 0 0
14085 The Subscriber information could not be obtained from the Distributor. 0 0
14088 The table '%s' must have a primary key to be published using the transaction-based method. 0 0
14089 The clustered index on materialized view '%s' may not contain nullable columns if it is to be published using the transaction-based method. 0 0
14090 Error evaluating article synchronization object after column drop. The filter clause for article '%s' must not reference the dropped column. 0 0
14091 The @type parameter passed to sp_helpreplicationdb must be either 'pub' or 'sub'. 0 0
14092 Could not change article because there is an existing subscription to the article. 0 0
14093 Cannot grant or revoke access directly on publication '%s' because it uses the default publication access list. 0 0
14094 Could not subscribe to article '%s' because heterogeneous Subscriber '%s' does not support the @pre_creation_cmd parameter value 'truncate'. 0 0
14095 The value for the @sync_method parameter is not valid. Could not subscribe to publication '%s' because non-SQL Server Subscriber '%s' only supports values of 'character', 'bcp character', 'concurrent_c', and 'database snapshot character' for the @sync_method parameter. 0 0
14096 The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is 'drop'. 0 0
14097 The 'status' value must be 'no column names', 'include column names', 'string literals', 'parameters', 'DTS horizontal partitions' or 'no DTS horizontal partitions'. 0 0
14098 Cannot drop Distribution Publisher '%s'. The remote Publisher is using '%s' as Distributor. Disable publishing at the Publisher before attempting to drop this relationship. 0 0
14099 The server '%s' is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisiting Distributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard. 0 0
14100 Specify all articles when subscribing to a publication using concurrent snapshot processing. 0 0
14101 The publication '%s' already has a Snapshot Agent defined. 0 0
14102 Specify all articles when unsubscribing from a publication using concurrent snapshot processing. 0 0
14103 Invalid "%s" value. Valid values are "publisher", "subscriber", or "both". 0 0
14105 You have updated the distribution database property '%s' successfully. 0 0
14106 Distribution retention periods must be greater than or equal to 0. 0 0
14107 The @max_distretention value must be larger than the @min_distretention value. 0 0
14108 Removed %ld history records from %s. 0 0
14109 The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Windows Authentication). 0 0
14110 For stored procedure articles, the @property parameter value must be 'description', 'dest_table', 'dest_object', 'creation_script', 'pre_creation_cmd', 'schema_option', or 'destination_owner'. 0 0
14111 The @pre_creation_cmd parameter value must be 'none' or 'drop'. 0 0
14112 This procedure can be executed only against table-based articles. 0 0
14113 Could not execute '%s'. Check '%s' in the install directory. 0 0
14114 The server '%s' is not configured as a Distributor. 0 0
14115 The property parameter value must be %s. 0 0
14117 '%s' is not configured as a distribution database. 0 0
14118 A stored procedure can be published only as a 'serializable proc exec' article, a 'proc exec' article, or a 'proc schema only' article. 0 0
14119 Could not add the distribution database '%s'. This distribution database already exists. 0 0
14120 Could not drop the distribution database '%s'. This distributor database is associated with a Publisher. 0 0
14121 Could not drop the Distributor '%s'. This Distributor has associated distribution databases. 0 0
14122 The @article parameter value must be 'all' for immediate_sync publications. 0 0
14123 The subscription @sync_type parameter value 'manual' is no longer supported. 0 0
14124 A publication must have at least one article before a subscription to it can be created. 0 0
14126 You do not have the required permissions to complete the operation. 0 0
14128 Invalid @subscription_type parameter value. Valid options are 'push' or 'pull'. 0 0
14129 The @status parameter value must be NULL for 'automatic' sync_type when you add subscriptions to an immediate_sync publication. 0 0
14135 There is no subscription on Publisher '%s', publisher database '%s', publication '%s'. 0 0
14136 The keyword 'all' is reserved by replication stored procedures. 0 0
14137 The @value parameter value must be either 'true' or 'false'. 0 0
14138 Invalid option name '%s'. 0 0
14139 The replication system table '%s' already exists. 0 0
14143 Cannot drop Distributor Publisher '%s'. There are Subscribers associated with it in the distribution database '%s'. 0 0
14144 Cannot drop Subscriber '%s'. There are subscriptions for it in the publication database '%s'. 0 0
14146 The article parameter '@schema_option' cannot be NULL. 0 0
14147 Restricted publications are no longer supported. 0 0
14148 Invalid '%s' value. Valid values are 'true' or 'false'. 0 0
14149 Removed %ld replication history records in %s seconds (%ld row/secs). 0 0
14150 Replication-%s: agent %s succeeded. %s 0 0
14151 Replication-%s: agent %s failed. %s 0 0
14152 Replication-%s: agent %s scheduled for retry. %s 0 0
14153 Replication-%s: agent %s warning. %s 0 0
14154 The Distributor parameter must be '@heartbeat_interval'. 0 0
14155 Invalid article ID specified for procedure script generation. 0 0
14156 The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format. 0 0
14157 The subscription created by Subscriber '%s' to publication '%s' has expired and has been dropped. 0 0
14158 Replication-%s: agent %s: %s. 0 0
14159 Could not change property '%s' for article '%s' because there is an existing subscription to the article. 0 0
14160 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. 0 0
14161 The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latency requirement. 0 0
14162 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. 0 0
14163 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. 0 0
14164 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. 0 0
14165 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. 0 0
14166 Disable publishing ignored error msg %d, severity %d, state %d: %s. 0 0
14167 Subscription expiration 0 0
14168 Transactional replication latency 0 0
14169 Long merge over dialup connection 0 0
14170 Long merge over LAN connection 0 0
14171 Slow merge over LAN connection 0 0
14172 Slow merge over dialup connection 0 0
14173 Failed to set publication parameter %s because it is not supported in Workgroup sku. 0 0
14196 The agent has never been run. 0 0
14197 Value of %s parameter should be in the set %s 0 0
14198 The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct. 0 0
14199 The specified job '%s' is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint. 0 0
14200 The specified '%s' is invalid. 0 0
14201 01 10 No 0 (all steps) .. 0 0
14202 before or after @active_start_time 0 0
14203 sp_helplogins [excluding Windows NT groups] 0 0
14204 04 10 No 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions) 0 0
14205 (unknown) 0 0
14206 0..n seconds 0 0
14207 -1 [no maximum], 0..n 0 0
14208 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend] 0 0
14209 0..127 [1 = Sunday .. 64 = Saturday] 0 0
14210 notification 0 0
14211 server 0 0
14212 (all jobs) 0 0
14213 Core Job Details: 0 0
14214 Job Steps: 0 0
14215 Job Schedules: 0 0
14216 Job Target Servers: 0 0
14217 SQL Server Warning: '%s' has performed a forced defection of TSX server '%s'. Run sp_delete_targetserver at the MSX in order to complete the defection. 0 0
14218 hour 0 0
14219 minute 0 0
14220 second 0 0
14221 This job has one or more notifications to operators other than '%s'. The job cannot be targeted at remote servers as currently defined. 0 0
14222 Cannot rename the '%s' operator. 0 0
14223 Cannot modify or delete operator '%s' while this server is a %s. 0 0
14224 Warning: The server name given is not the current MSX server ('%s'). 0 0
14225 Warning: Could not determine local machine name. This prevents MSX operations from being posted. 0 0
14226 %ld history entries purged. 0 0
14227 Server defected from MSX '%s'. %ld job(s) deleted. 0 0
14228 Server MSX enlistment changed from '%s' to '%s'. 0 0
14229 Server enlisted into MSX '%s'. 0 0
14230 SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted. 0 0
14231 SP_POST_MSX_OPERATION Warning: The specified %s ('%s') is not involved in a multiserver job. 0 0
14232 Specify either a job_name, job_id, or an originating_server. 0 0
14233 Specify a valid job_id (or 0x00 for all jobs). 0 0
14234 The specified '%s' is invalid (valid values are returned by %s). 0 0
14235 The specified '%s' is invalid (valid values are greater than 0 but excluding %ld). 0 0
14236 Warning: Non-existent step referenced by %s. 0 0
14237 When an action of 'REASSIGN' is specified, the New Login parameter must also be supplied. 0 0
14238 %ld jobs deleted. 0 0
14239 %ld jobs reassigned to %s. 0 0
14240 Job applied to %ld new servers. 0 0
14241 Job removed from %ld servers. 0 0
14242 Only a system administrator can reassign ownership of a job. 0 0
14243 Job '%s' started successfully. 0 0
14245 Specify either the @name, @id, or @loginname of the task(s) to be deleted. 0 0
14250 The specified %s is too long. It must contain no more than %ld characters. 0 0
14251 Cannot specify '%s' as the operator to be notified. 0 0
14252 Cannot perform this action on a job you do not own. 0 0
14253 %ld (of %ld) job(s) stopped successfully. 0 0
14254 Job '%s' stopped successfully. 0 0
14255 The owner ('%s') of this job is either an invalid login, or is not a valid user of database '%s'. 0 0
14256 Cannot start the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver. 0 0
14257 Cannot stop the job "%s" (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver. 0 0
14258 Cannot perform this operation while SQLServerAgent is starting. Try again later. 0 0
14260 You do not have sufficient permission to run this command. Contact your system administrator. 0 0
14261 The specified %s ('%s') already exists. 0 0
14262 The specified %s ('%s') does not exist. 0 0
14263 Target server '%s' is already a member of group '%s'. 0 0
14264 Target server '%s' is not a member of group '%s'. 0 0
14265 The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and Windows System and Application event logs for possible causes. 0 0
14266 The specified '%s' is invalid (valid values are: %s). 0 0
14267 Cannot add a job to the '%s' job category. 0 0
14268 There are no jobs at this server that originated from server '%s'. 0 0
14269 Job '%s' is already targeted at server '%s'. 0 0
14270 Job '%s' is not currently targeted at server '%s'. 0 0
14271 A target server cannot be named '%s'. 0 0
14272 Object-type and object-name must be supplied as a pair. 0 0
14273 You must provide either @job_id or @job_name (and, optionally, @schedule_name), or @schedule_id. 0 0
14274 Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. 0 0
14275 The originating server must be either local server or MSX server. 0 0
14276 '%s' is a permanent %s category and cannot be deleted. 0 0
14277 The command script does not destroy all the objects that it creates. Revise the command script. 0 0
14278 The schedule for this job is invalid (reason: %s). 0 0
14279 Supply either @job_name, @job_id or @originating_server. 0 0
14280 Supply either a job name (and job aspect), or one or more job filter parameters. 0 0
14281 Warning: The @new_owner_login_name parameter is not necessary when specifying a 'DELETE' action. 0 0
14282 Supply either a date (created or last modified) and a data comparator, or no date parameters at all. 0 0
14283 Supply @target_server_groups or @target_servers, or both. 0 0
14284 Cannot specify a job ID for a new job. An ID will be assigned by the procedure. 0 0
14285 Cannot add a local job to a multiserver job category. 0 0
14286 Cannot add a multiserver job to a local job category. 0 0
14287 The '%s' supplied has an invalid %s. 0 0
14288 %s cannot be before %s. 0 0
14289 %s cannot contain '%s' characters. 0 0
14290 This job is currently targeted at the local server so cannot also be targeted at a remote server. 0 0
14291 This job is currently targeted at a remote server so cannot also be targeted at the local server. 0 0
14292 There are two or more tasks named '%s'. Specify %s instead of %s to uniquely identify the task. 0 0
14293 There are two or more jobs named '%s'. Specify %s instead of %s to uniquely identify the job. 0 0
14294 Supply either %s or %s to identify the job. 0 0
14295 Frequency Type 0x2 (OnDemand) is no longer supported. 0 0
14296 This server is already enlisted into MSX '%s'. 0 0
14297 Cannot enlist into the local machine. 0 0
14298 This server is not currently enlisted into an MSX. 0 0
14299 Server '%s' is an MSX. Cannot enlist one MSX into another MSX. 0 0
14301 Logins other than the current user can only be seen by members of the sysadmin role. 0 0
14303 Stored procedure '%s' failed to access registry key. 0 0
14304 Stored procedure '%s' can run only on Windows 2000 servers. 0 0
14305 Column '%.*ls' does not exist in table '%.*ls'. 0 0
14306 The target server (TSX) version is not compatible with the master server (MSX) version (%ld.%ld.%ld). 0 0
14307 Access to Integration Services package '%s' is denied. 0 0
14350 Cannot initialize COM library because CoInitialize failed. 0 0
14351 Cannot complete this operation because an unexpected error occurred. 0 0
14352 Cannot find Active Directory information in the registry for this SQL Server instance. Run sp_ActiveDirectory_SCP again. 0 0
14353 Cannot determine the service account for this SQL Server instance. 0 0
14354 Cannot start the MSSQLServerADHelper service. Verify that the service account for this SQL Server instance has the necessary permissions to start the MSSQLServerADHelper service. 0 0
14355 The MSSQLServerADHelper service is busy. Retry this operation later. 0 0
14356 The Windows Active Directory client is not installed properly on the computer where this SQL Server instance is running. LoadLibrary failed to load ACTIVEDS.DLL. 0 0
14357 Cannot list '%s' in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters. 0 0
14359 Active Directory directory service is not enabled on the network, or it is not supported by the operating system. 0 0
14360 %s is already configured as TSX machine 0 0
14362 The MSX server must be running the Standard or Enterprise edition of SQL Server 0 0
14363 The MSX server is not prepared for enlistments [there must be an operator named 'MSXOperator' defined at the MSX] 0 0
14364 The TSX server is not currently enlisted 0 0
14365 Specify a valid schedule_uid. 0 0
14366 Only members of sysadmin role can modify the owner of a schedule. 0 0
14367 One or more schedules were not deleted because they are being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job. 0 0
14368 Schedule "%s" was not deleted because it is being used by at least one other job. Use "sp_detach_schedule" to remove schedules from a job. 0 0
14369 The schedule ID "%s" is used by more than one job. Specify the job_id. 0 0
14370 The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX). 0 0
14371 There are two or more schedules named "%s". Specify %s instead of %s to uniquely identify the schedule. 0 0
14372 The schedule was not deleted because it is being used by one or more jobs. 0 0
14373 Supply either %s or %s to identify the schedule. 0 0
14374 The specified schedule name "%s" is not associated with the job "%s". 0 0
14375 More than one schedule named "%s" is attached to job "%s". Use "sp_update_schedule" to update schedules. 0 0
14376 More than one schedule named "%s" is attached to job "%s". Use "sp_detach_schedule" to remove schedules from a job. 0 0
14377 The schedule was not attached to the specified job. The schedule owner and the job owner must be the same or the operation must be performed by a sysadmin. 0 0
14378 @sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility 0 0
14379 Table '%s' foreign key 'originating_server_id' does not have a matching value in the referenced view 'dbo.sysoriginatingservers_view'. 0 0
14380 Field 'originating_server_id' in table sysoriginatingservers is being referenced by either sysjobs or sysschedules. 0 0
14390 Only members of role sysadmin can specify the %s parameter. 0 0
14391 Only owner of a job or members of sysadmin role can detach a schedule. 0 0
14392 Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can purge history of the job. 0 0
14393 Only owner of a job or members of role sysadmin or SQLAgentOperatorRole can start and stop the job. 0 0
14394 Only owner of a job schedule or members of sysadmin role can modify or delete the job schedule. 0 0
14395 '%s' is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy. 0 0
14396 Only members of sysadmin server role can modify multi-server jobs 0 0
14397 Only members of sysadmin server role can start/stop multi-server jobs 0 0
14398 Only members of sysadmin server role can create multi-server jobs 0 0
14410 You must supply either a plan_name or a plan_id. 0 0
14411 Cannot delete this plan. The plan contains enlisted databases. 0 0
14412 The destination database is already part of a log shipping plan. 0 0
14413 This database is already log shipping. 0 0
14414 A log shipping monitor is already defined. 0 0
14415 The user name cannot be null when using SQL Server authentication. 0 0
14416 This stored procedure must be run in msdb. 0 0
14417 Cannot delete the monitor server while databases are participating in log shipping. 0 0
14418 The specified @backup_file_name was not created from database '%s'. 0 0
14419 The specified @backup_file_name is not a database backup. 0 0
14420 The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information. 0 0
14421 The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information. 0 0
14422 Supply either @plan_id or @plan_name. 0 0
14423 Other databases are enlisted on this plan and must be removed before the plan can be deleted. 0 0
14424 The database '%s' is already involved in log shipping. 0 0
14425 The database '%s' does not seem to be involved in log shipping. 0 0
14426 A log shipping monitor is already defined. Call sp_define_log_shipping_monitor with @delete_existing = 1. 0 0
14427 A user name is necessary for SQL Server security. 0 0
14428 Could not remove the monitor as there are still databases involved in log shipping. 0 0
14429 There are still secondary servers attached to this primary. 0 0
14430 Destination path %s is not valid. Unable to list directory contents. Specify a valid destination path. 0 0
14440 Could not set single user mode. 0 0
14441 Role change succeeded. 0 0
14442 Role change failed. 0 0
14450 The specified @backup_file_name was not taken from database '%s'. 0 0
14451 The specified @backup_file_name is not a database backup. 0 0
14500 Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query. 0 0
14501 An alert ('%s') has already been defined on this condition. 0 0
14502 The @target_name parameter must be supplied when specifying an @enum_type of 'TARGET'. 0 0
14503 The @target_name parameter should not be supplied when specifying an @enum_type of 'ALL' or 'ACTUAL'. 0 0
14504 '%s' is the fail-safe operator. You must make another operator the fail-safe operator before '%s' can be dropped. 0 0
14505 Specify a null %s when supplying a performance condition. 0 0
14506 Cannot set alerts on message ID %ld. 0 0
14507 A performance condition must be formatted as: 'object_name|counter_name|instance_name|comparator(> or < or =)|numeric value'. 0 0
14508 Specify both @wmi_namespace and @wmi_query. 0 0
14509 Specify a valid %s when supplying a @wmi_namespace. 0 0
14510 Specify a null %s when supplying a @wmi_namespace. 0 0
14511 The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that the query has the correct syntax. 0 0
14512 Specify a valid %s when supplying a @wmi_query. 0 0
14513 Analysis query subsystem 0 0
14514 Analysis command subsystem 0 0
14515 Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name. 0 0
14516 Proxy (%d) is not allowed for subsystem "%s" and user "%s". Grant permission by calling sp_grant_proxy_to_subsystem or sp_grant_login_to_proxy. 0 0
14517 A proxy account is not allowed for a Transact-SQL subsystem. 0 0
14518 Cannot delete proxy (%d). It is used by at least one jobstep. Change this proxy for all jobsteps first. 0 0
14519 Only one of @login_name, @fixed_server_role, or @msdb_role should be specified. 0 0
14520 %s is not a valid SQL Server standard login, Windows NT user, Windows NT group, or msdb database role. 0 0
14521 %s is not a valid SQL Server fixed server role, Windows NT user, or Windows NT group. 0 0
14522 '"%s" is not a valid role of an msdb database, Windows NT user, or Windows NT group. 0 0
14523 %s has not been granted permission to use proxy "%s". 0 0
14524 Supply either %s or %s. 0 0
14525 Only members of sysadmin role are allowed to update or delete jobs owned by a different login. 0 0
14526 The specified category "%s" does not exist for category class "%s". 0 0
14527 Job "%s" cannot be used by an alert. It should first be associated with a server by calling sp_add_jobserver. 0 0
14528 Job "%s" has no steps defined. 0 0
14529 Proxy "%s" is not a valid Windows user. 0 0
14530 The Transact-SQL subsystem cannot be executed under the context of a proxy account. 0 0
14531 Permission to access proxy already granted. Verify current permissions assignments. 0 0
14532 Supply both %s and %s, or none of them. 0 0
14533 Use either a proxy or user_domain, user_name, or user_password parameter. 0 0
14534 All user_domain, user_name, and user_password parameters should be defined. 0 0
14535 The user_domain, user_name, and user_password parameters can be specified only for replication subsystems. 0 0
14536 Only members of the sysadmin role can specify a "%s" parameter. 0 0
14537 Execution in the context of disabled proxy (proxy_id = %d) is not allowed. Contact your system administrator. 0 0
14538 SSIS package execution subsystem 0 0
14539 Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX. 0 0
14540 Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX. 0 0
14541 The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX. 0 0
14542 It is invalid for any TSQL step of a multiserver job to have a non-null %s value. 0 0
14543 Login '%s' owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role. 0 0
14544 This job is owned by '%s'. Only a job owned by a member of the %s role can be a multiserver job. 0 0
14545 The %s parameter is not valid for a job step of type '%s'. 0 0
14546 The %s parameter is not supported on Windows 95/98 platforms. 0 0
14547 Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s. 0 0
14548 Target server '%s' does not have any jobs assigned to it. 0 0
14549 (Description not requested.) 0 0
14550 Command-Line Subsystem 0 0
14551 Replication Snapshot Subsystem 0 0
14552 Replication Transaction-Log Reader Subsystem 0 0
14553 Replication Distribution Subsystem 0 0
14554 Replication Merge Subsystem 0 0
14555 Active Scripting Subsystem 0 0
14556 Transact-SQL Subsystem 0 0
14557 [Internal] 0 0
14558 (encrypted command) 0 0
14559 (append output file) 0 0
14560 (include results in history) 0 0
14561 (normal) 0 0
14562 (quit with success) 0 0
14563 (quit with failure) 0 0
14564 (goto next step) 0 0
14565 (goto step) 0 0
14566 (idle) 0 0
14567 (below normal) 0 0
14568 (above normal) 0 0
14569 (time critical) 0 0
14570 (Job outcome) 0 0
14571 No No description available. 0 0
14572 @freq_interval must be at least 1 for a daily job. 0 0
14573 @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job. 0 0
14574 @freq_interval must be between 1 and 31 for a monthly job. 0 0
14575 @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10). 0 0
14576 @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job. 0 0
14577 @freq_recurrence_factor must be at least 1. 0 0
14578 Starts whenever the CPU usage has remained below %ld percent for %ld seconds. 0 0
14579 Automatically starts when SQLServerAgent starts. 0 0
14580 job 0 0
14581 Replication Transaction Queue Reader Subsystem 0 0
14582 Only a sysadmin can specify '@output_file_name' parameter for a jobstep. 0 0
14583 Only a sysadmin can specify '@database_user_name' parameter. 0 0
14585 Only the owner of DTS Package '%s' or a member of the sysadmin role may reassign its ownership. 0 0
14586 Only the owner of DTS Package '%s' or a member of the sysadmin role may create new versions of it. 0 0
14587 Only the owner of DTS Package '%s' or a member of the sysadmin role may drop it or any of its versions. 0 0
14588 ID.VersionID = 0 0
14589 [not specified] 0 0
14590 DTS Package '%s' already exists with a different ID in this category. 0 0
14591 SSIS folder '%s' already exists in the specified parent folder. 0 0
14592 DTS Category '%s' was found in multiple parent categories. You must uniquely specify the category to be dropped. 0 0
14593 SSIS folder '%s' contains packages and/or other folders. You must drop these first. 0 0
14594 DTS Package 0 0
14595 DTS Package '%s' exists in different categories. You must uniquely specify the package. 0 0
14596 DTS Package '%s' exists in another category. 0 0
14597 DTS Package ID '%s' already exists with a different name. 0 0
14598 Cannot drop the Local, Repository, or LocalDefault DTS categories. 0 0
14599 Name 0 0
14600 Proxy "%s" has not been granted permission to use subsystem "%s". 0 0
14601 Operator "%s" is not enabled and therefore cannot receive notifications. 0 0
14602 Operator "%s" does not have an e-mail address specified. 0 0
14603 Database Mail is not properly configured. 0 0
14604 Both %s parameters (id and name) cannot be NULL 0 0
14605 Both %s parameters (id and name) do not point to the same object 0 0
14606 %s id is not valid 0 0
14607 %s name is not valid 0 0
14608 Either %s or %s parameter needs to be supplied 0 0
14609 Mail database to user database association does not exist and therefore cannot be updated 0 0
14610 Either @profile_name or @description parameter needs to be specified for update 0 0
14611 Account sequence number must be supplied for update 0 0
14612 Each principal should have at least one default profile 0 0
14614 %s is not a valid mailserver_type 0 0
14615 The @username parameter needs to be supplied if the @password is supplied. 0 0
14616 Unable to retrieve the newly created credential [%s] from the credential store. 0 0
14617 Mail host database specified is invalid 0 0
14618 Parameter '%s' must be specified. This parameter cannot be NULL. 0 0
14619 Received an error on the Service Broker conversation with Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for information. 0 0
14620 The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information. 0 0
14621 Parameter @attachmentencoding does not support the value "%s". The attachment encoding must be "MIME". 0 0
14622 Parameter @importance does not support the value "%s". Mail importance must be one of LOW, NORMAL, or HIGH. 0 0
14623 Parameter @sensitivity does not support the value "%s". Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL. 0 0
14624 At least one of the following parameters must be specified. "%s". 0 0
14625 Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query. A query must be specified to attach the results of the query. 0 0
14626 Parameter @mailformat does not support the value "%s". The mail format must be TEXT or HTML. 0 0
14627 Received error %d while sending a message as part of the %s operation. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information. 0 0
14628 The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon ";". 0 0
14629 There is no configuration parameter named "%s", or the value provided is not of the correct data type. 0 0
14630 Database Mail is not permitted to send files with the file extension %s. 0 0
14631 The current user ('%s') either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonate the user specified in the parameter @execute_query_as. Only members of the sysadmin fixed server role and members of the db_owner fixed database role can impersonate another user. 0 0
14632 The user name %s specified in @execute_query_as is invalid. There is no user by that name. 0 0
14633 The database name "%s" specified in @execute_query_database is invalid. There is no database by that name. 0 0
14634 Warning: %s' 0 0
14635 Mail queued. 0 0
14636 No No global profile is configured. Specify a profile name in the @profile_name parameter. 0 0
14637 Activation failure. 0 0
14638 Activation successful. 0 0
14639 The mail queue was started by login "%s". 0 0
14640 The mail queue stopped by login "%s". 0 0
14641 Mail not queued. Database Mail is stopped. Use sysmail_start_sp to start Database Mail. 0 0
14642 Default attachment encoding 0 0
14643 Default dialog lifetime 0 0
14644 Default maximum file size 0 0
14645 Extensions not allowed in outgoing mails 0 0
14646 Number of retry attempts for a mail server 0 0
14647 Delay between each retry attempt to mail server 0 0
14648 Minimum process lifetime in seconds 0 0
14649 Unable to test profile. Database Mail is stopped. Use sysmail_start_sp to start Database Mail. 0 0
14650 Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery. 0 0
14651 Unable to test profile. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery. 0 0
14652 Invalid message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 0 0
14653 Invalid %s value received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 0 0
14654 Unexpected message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 0 0
14655 Invalid XML message format received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 0 0
14657 Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded. 0 0
14658 Failed to retrieve SQLPath for syssubsystems population. 0 0
14659 Failed to retrieve VerSpecificRootDir for syssubsystems population. 0 0
14660 Database Compatibility Level is too low. Compatibility Level must be Version80 or higher. 0 0
14661 Query execution failed: %s 0 0
14662 mailitem_id on conversation %s was not found in the sysmail_send_retries table. This mail item will not be sent. 0 0
14663 Mail Id %d has exceeded the retry count. This mail item will not be sent. 0 0
14664 Database Mail logging level: normal - 1, extended - 2 (default), verbose - 3 0 0
14665 Mail items deletion is initiated by user "%s". %d items deleted. 0 0
14666 User name cannot be supplied when using default credentials 0 0
14667 Mail Id %d has been deleted from sysmail_mailitems table. This mail will not be sent. 0 0
14668 Deleting profile %s failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of the profile. 0 0
14670 Cannot delete the active collection set '%s'. Stop the collection set and then try to delete it again. 0 0
14671 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. 0 0
14672 Cannot delete the collection item '%s' in the active collection set '%s'. Stop the collection set and then try to delete the collection item again. 0 0
14673 Cannot delete the collector type '%s'. Delete all collection items associated with this collector type and then try to delete it again. 0 0
14674 Cannot upload data for the inactive collection set '%s'. Start the collection set and then try to upload the data again. 0 0
14675 Cannot update the name, target, proxy_id, logging_level, or collection_mode, or add collection item to the active collection set '%s'. Stop the collection set and then try to update it again. 0 0
14676 The user does not have permission to change '%s'. The user must be a member of data collector role '%s'. 0 0
14677 The user does not have permission to perform this operation. The user must be a member of data collector role '%s'. 0 0
14678 SQL Server Trace with id %d has been stopped and closed by external user. SQL Server Trace collector will attempt to re-create the trace. 0 0
14679 The specified %s (%s) is not valid in this data warehouse. 0 0
14680 Management Data Warehouse database can only be installed on an instance of SQL Server 2008 or higher. 0 0
14681 Cannot perform this procedure when the collector is disabled. Enable the collector and then try again. 0 0
14682 The state of the collection set has changed, but it will not start or stop until the collector is enabled. 0 0
14683 A collection set in cached mode requires a schedule. 0 0
14684 Caught error 0 0
14685 Collection set: '%s' does not contain any collection items, so starting the collection set will have no effect. 0 0
14686 The MDWInstance and MDWDatabase parameters of the configuration store cannot be null. 0 0
14687 Invalid value (%d) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload failures), 0 (cache no upload data), N (cache data from N previous upload failures, where N >= 1) 0 0
14688 A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent. 0 0
14689 A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and configure the management data warehouse. 0 0
14690 Cannot perform this procedure when the collector is enabled. Disable the collector and then try again. 0 0
14691 The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data. 0 0
14692 Insufficient priveleges to start collection set: '%s'. Only a member of the 'sysadmin' fixed server role can start a collection set without a SQL Server Agent proxy. Attach a SQL Server Agent proxy to the collection set before retrying. 0 0
14693 A collection set cannot start without a schedule. Specify a schedule for the collection set. 0 0
14694 Cannot upload data on-demand for the collection set '%s' in non-cached mode. 0 0
14695 Cannot collect data on-demand for the collection set '%s' in cached mode. 0 0
14696 Cannot update or delete a system collection set, or add new collection items to it. 0 0
14697 Unable to convert showplan to XML. Error 0 0
14698 PowerShell Subsystem 0 0
14700 Collects data about the disk and log usage for all databases. 0 0
14701 Disk Usage 0 0
14702 Disk Usage - Data Files 0 0
14703 Disk Usage - Log Files 0 0
14704 Collects top-level performance indicators for the computer and the Database Engine. Enables analysis of resource use, resource bottlenecks, and Database Engine activity. 0 0
14705 Server Activity 0 0
14706 Server Activity - DMV Snapshots 0 0
14707 Server Activity - Performance Counters 0 0
14708 Collects query statistics, T-SQL text, and query plans of most of the statements that affect performance. Enables analysis of poor performing queries in relation to overall SQL Server Database Engine activity. 0 0
14709 Query Statistics 0 0
14710 Query Statistics - Query Activity 0 0
14711 Changes to SQL dumper configuration will take effect when the collection set is restarted. To perform an immediate dump, use the dtutil /dump option. 0 0
14712 Only dbo or members of dc_admin can install or upgrade instmdw.sql. Contact an administrator with sufficient permissions to perform this operation. 0 0
14713 A management data warehouse cannot be installed to SQL Server Express Edition. 0 0
14714 Attempting to upgrade a Management Data Warehouse of newer version '%s' with an older version '%s'. Upgrade aborted. 0 0
30003 A fulltext system view or stvf cannot open database id %d. 0 0
30004 A fulltext system view or stvf cannot open user table object id %d. 0 0
30005 The name specified for full-text index fragment %.*ls is not valid. 0 0
30006 A fulltext system view or stvf cannot open fulltext index for user table object id %d. 0 0
30007 Parameters of dm_fts_index_keywords and dm_fts_index_keywords_by_document cannot be null. 0 0
30008 The level number specified for function fn_fulltext_compindex is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index. Use the correct level number. 0 0
30009 The argument data type '%ls' specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar. 0 0
30020 The full-text query parameter for %S_MSG is not valid. 0 0
30022 Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION. 0 0
30023 The fulltext stoplist '%.*ls' does not exist or the current user does not have permission to perform this action. Verify that the correct stoplist name is specified and that the user had the permission required by the Transact-SQL statement. 0 0
30024 The fulltext stoplist '%.*ls' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name. 0 0
30028 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. 0 0
30029 The full-text host controller failed to start. Error: 0x%X. 0 0
30031 A full-text master merge failed on full-text catalog '%ls' in database '%.*ls' with error 0x%08X. 0 0
30032 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. 0 0
30033 The stoplist '%.*ls' already contains full-text stopword '%.*ls' with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Transact-SQL statement. 0 0
30034 Full-text stoplist '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text index by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FULLTEXT INDEX. Then retry dropping the stoplist. 0 0
30037 An argument passed to a fulltext function is not valid. 0 0
30038 Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index. 0 0
30039 Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size. 0 0
30043 Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character. 0 0
30044 The user does not have permission to alter the current default stoplist '%.*ls'. To change the default stoplist of the database, ALTER permission is required on both new and old default stoplists. 0 0
30045 Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index. 0 0
30046 SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running. To re-start the FDHost process, run the sp_fulltext_service 'restart_all_fdhosts' command or restart the SQL Server instance. 0 0
30047 The user does not have permission to %.*ls stoplist '%.*ls'. 0 0
30048 Informational: Ignoring duplicate thesaurus rule '%ls' while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the section of an expansion rule or the section of a replacement rule. This causes an ambiguity and hence this phrase will be ignored. 0 0
30049 Fulltext thesaurus internal error (HRESULT = '0x%08x') 0 0
30050 Both the thesaurus file for lcid '%d' and the global thesaurus could not be loaded. 0 0
30051 Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: '%ls'. 0 0
30052 The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs successfully, use only six or fewer terms. Modify the query to simplify the condition by removing prefixes or repeated terms. 0 0
30053 Word breaking timed out for the full-text query string. This can happen if the wordbreaker took a long time to process the full-text query string, or if a large number of queries are running on the server. Try running the query again under a lighter load. 0 0
30055 Full-text catalog import has started for full-text catalog '%ls' in database '%ls'. 0 0
30056 Full-text catalog import has finished for full-text catalog '%ls' in database '%ls'. %d fragments and %d keywords were processed. 0 0
30057 Upgrade option '%ls' is being used for full-text catalog '%ls' in database '%ls'. 0 0
30059 A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); catalog name is %s (id: %d); table name %s (id: %d). Fix the errors that are logged in the full-text crawl log. Then, resume the population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name RESUME POPULATION. 0 0
30060 The import population for database %ls (id: %d), catalog %ls (id: %d) is being cancelled because of a fatal error ('%ls'). Fix the errors that are logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching it, or by taking the database offline and bringing it back online. If the error is not recoverable, rebuild the full-text catalog. 0 0
30061 The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server after the issue is fixed. 0 0
30062 The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted. 0 0
30063 Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid. 0 0
30064 SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation. 0 0
30067 Warning: The detach operation cannot delete a full-text index created on table '%ls' in database '%ls' because the index is on a read-only filegroup. To drop the full-text index, re-attach the database, change the read-only filegroup to read/write access and then detach it. This warning will not fail the database detach operation. 0 0
30068 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'. 0 0
30069 The full-text filter component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls'). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the filter component. 0 0
30070 During the database upgrade, the full-text word-breaker component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls'. Full path is '%.*ls'. Language requested is %d. Language used is %d. 0 0
30071 The full-text word-breaker component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls', language requested is %d, language used is %d). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the word-breaker component. 0 0
30072 During the database upgrade, the full-text protocol handler component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls'. Full path is '%.*ls'. Program ID is '%.*ls'. 0 0
30073 The full-text protocol handler component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is '%ls', full path is '%.*ls', program ID is '%.*ls'). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the protocol handler component. 0 0
30074 The master merge of full-text catalog '%ls' in database '%.*ls' was cancelled. 0 0
30075 Full-text crawls for database ID: %d, table ID: %d, catalog ID: %d will be stopped since the clustered index on the table has been altered or dropped. Crawl will need to re-start from the beginning. 0 0
30076 Full-text crawl forward progress information for database ID: %d, table ID: %d, catalog ID: %d has been reset due to the modification of the clustered index. Crawl will re-start from the beginning when it is unpaused. 0 0
30077 The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values for full-text queries that contain an OPTIMIZE FOR query hint. Modify the OPTIMIZE FOR query hint value to be a single, non-empty term. 0 0
30078 The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type of full-text logical operator. 0 0
30079 The full text query ignored UNKNOWN in the OPTIMIZE FOR hint. 0 0
30080 The full-text population on table '%ls' cannot be started because the full-text catalog is importing data from existing catalogs. After the import operation finishes, rerun the command. 0 0
30081 A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query with the new trace flag settings. 0 0
30082 Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery. 0 0
30083 Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery. 0 0
30084 The full-text index cannot be created because filegroup '%.*ls' does not exist or the filegroup name is incorrectly specified. Specify a valid filegroup name. 0 0
30085 A stoplist cache cannot be generated while processing a full-text query or performing full-text indexing. There is not enough memory to load the stoplist cache. Rerun the query or indexing command when more resources are available. 0 0
30086 The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically be retried using a smaller batch size. 0 0
30087 Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size. 0 0
30088 The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary. 0 0
30089 The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically. 0 0
30090 A new instance of the full-text filter daemon host process has been successfully started. 0 0
30091 A request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently paused. Either resume or stop the paused population. To resume it, use the following Transact-SQL statement: ALTER FULLTEXT INDEX ON %.*ls RESUME POPULATION. To stop it, use the following statement: ALTER FULLTEXT INDEX ON %.*ls STOP POPULATION. 0 0
30092 Full-text stoplist ID '%d' does not exist. 0 0
30093 The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a valid state. This can prevent SQL Server from initializing critical system objects. Full-text queries will fail until this issue is resolved. Try stopping SQL Server and any filter daemon host processes and then restarting the instance of SQL Server. 0 0
30094 The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to allocate memory or create tasks. Try restarting the instance of SQL Server. 0 0
30095 The version of the language components used by full-text catalog '%ls' in database '%ls' is different from the version of the language components included this version of SQL Server. The full-text catalog will still be imported as part of database upgrade. To avoid any possible inconsistencies of query results, consider rebuilding the full-text catalog. 0 0
30096 A full-text retry pass of %ls population started for table or indexed view '%ls'. Table or indexed view ID is '%d'. Database ID is '%d'. 0 0
30097 The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs for the catalog ID %d in database ID %d. Try to reattach this database. If this fails, then the catalog will need to be dropped or recreated before attach. 0 0
30098 An internal query to load data for a crawl on database '%.*ls' and table '%.*ls' failed with error code %d. Check the sql error code for more information about the condition causing this failure. The crawl needs to be restarted after this condition is removed. 0 0
30099 Fulltext internal error 0 0
31001 The session '%s' already exists. Use a different session name. 0 0
31002 This operation can be performed only by the owner of the session. 0 0
31003 User does not have enough permissions to tune one or more of the databases specified. 0 0
32001 Log shipping backup log job for %s. 0 0
32002 Log shipping copy job for %s:%s. 0 0
32003 Log shipping restore log job for %s:%s. 0 0
32004 Log shipping backup log job step. 0 0
32005 Log shipping copy job step. 0 0
32006 Log shipping restore log job step. 0 0
32007 Database %s is not ONLINE. 0 0
32008 Database %s is not ONLINE. The backup job will not be performed until this database is brought online. 0 0
32009 A log shipping primary entry already exists for database %s. 0 0
32010 Database %s does not exist as log shipping primary. 0 0
32011 Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first. 0 0
32012 Secondary %s.%s already exists for primary %s. 0 0
32013 A log shipping entry already exists for secondary database %s. 0 0
32014 Database %s does not exist as log shipping secondary. 0 0
32015 The primary database %s cannot have SIMPLE recovery for log shipping to work properly. 0 0
32016 The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing. 0 0
32017 Log shipping is supported on Enterprise, Developer, Standard and Workgroup editions of SQL Server. This instance has %s and is not supported. 0 0
32018 Log shipping is not installed on this instance. 0 0
32019 Log shipping alert job. 0 0
32020 Log shipping alert job step. 0 0
32021 Log shipping alert job schedule. 0 0
32022 Cannot add a log shipping job with name %s. A job with same name already exists in the system and this job does not belong to log shipping category. 0 0
32023 An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first. 0 0
32024 An entry for primary server %s, primary database %s already exists. 0 0
32025 Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first. 0 0
32026 Log shipping Primary Server Alert. 0 0
32027 Log shipping Secondary Server Alert. 0 0
32028 Invalid value = %d for parameter @threshold_alert was specified. 0 0
32029 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. 0 0
32030 Could not query monitor information for log shipping primary %s.%s from monitor server %s. 0 0
32031 Could not query monitor information for log shipping secondary %s.%s from monitor server %s. 0 0
32032 Invalid value '%d' for update period. Update period should be between 1 and 120 minutes. 0 0
32033 The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring 0 0
32034 An internal error occurred when setting up the database mirroring monitoring job. 0 0
32035 An internal error occurred when modifying the database mirroring monitoring job. 0 0
32036 Parameter(s) out of range. 0 0
32037 The units for the update period for the database mirroring monitor job have been changed. 0 0
32038 An internal error has occurred in the database mirroring monitor. 0 0
32039 The database '%s' is not being mirrored. No update of the base table was done. 0 0
32040 The alert for 'oldest unsent transaction' has been raised. The current value of '%d' surpasses the threshold '%d'. 0 0
32041 The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them. 0 0
32042 The alert for 'unsent log' has been raised. The current value of '%d' surpasses the threshold '%d'. 0 0
32043 The alert for 'unrestored log' has been raised. The current value of '%d' surpasses the threshold '%d'. 0 0
32044 The alert for 'mirror commit overhead' has been raised. The current value of '%d' surpasses the threshold '%d'. 0 0
32045 '%s' must be executed in msdb. 0 0
32046 Only members of the sysadmin fixed server role or the 'dbm_monitor' role in msdb can perform this operation. 0 0
32047 Database Mirroring Monitor Job 0 0
32048 Database Mirroring Monitor Schedule 0 0
32049 The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job. 0 0
32050 Alerts cannot be created on the system databases, master, msdb, model or tempdb. 0 0
32051 System administrator privilege is required to update the base table. The base table was not updated. 0 0
32052 Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation. 0 0
32053 The server name, given by '@@servername', is currently null. 0 0
32054 There was an error establishing a link to the remote monitor server. 0 0
32055 There was an error configuring the remote monitor server. 0 0
33001 Cannot drop the option because the option is not specified on %S_MSG. 0 0
33002 Access to %ls %ls is blocked because the signature is not valid. 0 0
33003 DDL statement is not allowed. 0 0
33004 The password of login '%.*ls' is invalid. A new password should be set for this login without specifying the old password. 0 0
33005 Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x. 0 0
33006 WITH SIGNATURE option cannot be specified on database. 0 0
33007 Cannot encrypt symmetric key with itself. 0 0
33008 Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG. 0 0
33009 The database owner SID recorded in the master database differs from the database owner SID recorded in database '%.*ls'. You should correct this situation by resetting the owner of database '%.*ls' using the ALTER AUTHORIZATION statement. 0 0
33010 The MUST_CHANGE option cannot be specified together with the HASHED option. 0 0
33011 The %S_MSG private key cannot be dropped because one or more entities are encrypted by it. 0 0
33012 Cannot %S_MSG signature %S_MSG %S_MSG '%.*ls'. Signature already exists or cannot be added. 0 0
33013 A %S_MSG by %S_MSG '%.*s' does not exist. 0 0
33014 Cannot countersign '%.*s'. Only modules can be countersigned. 0 0
33015 The database principal is referenced by a %S_MSG in the database, and cannot be dropped. 0 0
33016 The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins. 0 0
33017 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. 0 0
33018 Cannot remap user to login '%.*s', because the login is already mapped to a user in the database. 0 0
33019 Cannot create implicit user for the special login '%.*s'. 0 0
33020 A HASHED password cannot be set for a login that has CHECK_POLICY turned on. 0 0
33021 Failed to generate a user instance of SQL Server. Only local user accounts, interactive users accounts, service accounts, or batch accounts can generate a user instance. The connection will be closed.%.*ls 0 0
33022 Cannot obtain cryptographic provider properties. Provider error code: %d. 0 0
33023 The %S_MSG is too long. Maximum allowed length is %d bytes. 0 0
33024 Cryptographic provider %S_MSG '%ls' in dll is different from the guid recorded in system catalog for provider with id %d. 0 0
33025 Invalid cryptograpihic provider property: %S_MSG. 0 0
33026 Cryptographic provider with guid '%ls' already exists. 0 0
33027 Failed to load cryptographic provider '%.*ls' due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures. 0 0
33027 Cannot load library '%.*ls'. See errorlog for more information. 0 0
33028 Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%S_MSG) 0 0
33029 Cannot initialize cryptographic provider. Provider error code: %d. (%S_MSG) 0 0
33030 Cryptographic provider is not available. 0 0
33031 Cryptographic provider '%.*ls' is in disabled. 0 0
33032 SQL Crypto API version '%02d.%02d' implemented by provider is not supported. Supported version is '%02d.%02d'. 0 0
33033 Specified key type or option '%S_MSG' is not supported by the provider. 0 0
33034 Cannot specify algorithm for existing key. 0 0
33035 Cannot create key '%.*ls' in the provider. Provider error code: %d. (%S_MSG) 0 0
33036 Cannot drop the key with thumbprint '%.*ls' in the provider. 0 0
33037 Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG) 0 0
33038 Operation is not supported by cryptographic provider key. 0 0
33039 Invalid algorithm '%.*ls'. Provider error code: %d. (%S_MSG) 0 0
33040 Cryptographic provider key cannot be encrypted by password or other key. 0 0
33041 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. 0 0
33042 Cannot add %S_MSG because it is already mapped to a login. 0 0
33043 Cannot add %S_MSG '%.*ls' because there is already %S_MSG specified for the login. 0 0
33044 Cannot drop %S_MSG because there is %S_MSG referencing this provider. 0 0
33045 Cannot drop %S_MSG because it is not mapped to this login. 0 0
33046 Server principal '%.*ls' has no credential associated with %S_MSG '%.*ls'. 0 0
33047 Fail to obtain or decrypt secret for %S_MSG '%.*ls'. 0 0
33048 Cannot use %S_MSG under non-primary security context. 0 0
33049 Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG) 0 0
33050 Cannot create key '%.*ls' in the provider. Provider does not allow specifying key names. 0 0
33051 Invalid algorithm id: %d. Provider error code: %d. (%S_MSG) 0 0
33052 Cryptographic provider key cannot be a temporary key. 0 0
33053 Extensible Key Management is disabled or not supported on this edition of SQL Server. Use sp_configure 'EKM provider enabled' to enable it. 0 0
33054 Extensible key management is not supported in this edition of SQL Server. 0 0
33055 Exception happened when calling cryptographic provider '%.*ls' in the API '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx. 0 0
33056 Cannnot impersonate login '%.*ls' to access %S_MSG '%.*ls'. 0 0
33057 Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still use it. Restart the server to disable the provider for all users. 0 0
33058 Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the server to drop the provider for all users. 0 0
33070 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. 0 0
33071 This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command. 0 0
33072 The audit log file path is invalid. 0 0
33073 Cannot find %S_MSG '%.*ls' or you do not have the required permissions. 0 0
33074 Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database. 0 0
33075 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. 0 0
33076 The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB. 0 0
33077 RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE. 0 0
33079 Cannot bind a default or rule to the CLR type '%s' because an existing sparse column uses this data type. Modify the data type of the sparse column or remove the sparse designation of the column. 0 0
33080 Cryptographic provider library '%.*ls' loaded into memory. This is an informational message only. No user action is required. 0 0
33081 Failed to load cryptographic provider '%.*ls' due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures. 0 0
33082 Cannot find Cryptographic provider library with guid '%ls'. 0 0
33083 Cannot create %S_MSG for %S_MSG '%ls' because it is not supported by the extensible key management provider '%ls'. 0 0
33084 The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. Symmetric keys created from an EKM provider are opened automatically for principals who can successfully authenticate with the cryptographic provider. 0 0
33085 One or more methods cannot be found in cryptographic provider library '%.*ls'. 0 0
33086 SQL Server Audit failed to record %ls action. 0 0
33087 %S_MSG property of the key returned by EKM provider doesn't match the expected value 0 0
33088 The algorithm: %.*ls is not supported for EKM operations by SQL Server 0 0
33089 Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG) 0 0
33090 Attempting to load library '%.*ls' into memory. This is an informational message only. No user action is required. 0 0
33091 Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database. 0 0
33101 Cannot use %S_MSG '%.*ls', because its private key is not present or it is not protected by the database master key. SQL Server requires the ability to automatically access the private key of the %S_MSG used for this operation. 0 0
33102 Cannot encrypt a system database. Database encryption operations cannot be performed for 'master', 'model', 'tempdb', 'msdb', or 'resource' databases. 0 0
33103 A database encryption key already exists for this database. 0 0
33104 A database encryption key does not exist for this database. 0 0
33105 Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the database encryption key. 0 0
33106 Cannot change database encryption state because no database encryption key is set. 0 0
33107 Cannot enable database encryption because it is already enabled. 0 0
33108 Cannot disable database encryption because it is already disabled. 0 0
33109 Cannot disable database encryption while an encryption, decryption, or key change scan is in progress. 0 0
33110 Cannot change database encryption key while an encryption, decryption, or key change scan is in progress. 0 0
33111 Cannot find server %S_MSG with thumbprint '%.*ls'. 0 0
33112 Beginning database encryption scan for database '%.*ls'. 0 0
33113 Database encryption scan for database '%.*ls' is complete. 0 0
33114 Database encryption scan for database '%.*ls' was aborted. Reissue ALTER DB to resume the scan. 0 0
33115 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later. 0 0
33116 CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%.*ls'. Try again later. 0 0
33117 Transparent Data Encryption is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions. 0 0
33118 Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered. 0 0
33119 Cannot modify filegroup read-only/read-write state while an encryption transition is in progress. 0 0
33120 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. 0 0
33121 The %S_MSG '%ls' does not have a login associated with it. Create a login and credential for this key to automatically access the extensible key management provider '%ls'. 0 0
33122 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. 0 0
33123 Cannot drop or alter the database encryption key since it is currently in use on a mirror. Retry the command after all the previous reencryption scans have propagated to the mirror or after mirroring is disabled. 0 0
33124 Database encryption scan for database '%.*ls' cannot complete since one or more files are offline. Bring the files online to run the scan to completion. 0 0
33201 An error occurred in reading from the audit file or file-pattern: '%s'. The SQL service account may not have Read permission on the files, or the pattern may be returning one or more corrupt files. 0 0
33202 SQL Server Audit could not write to file '%s'. 0 0
33203 SQL Server Audit could not write to the event log. 0 0
33204 SQL Server Audit could not write to the security log. 0 0
33205 Audit event: %s. 0 0
33206 SQL Server Audit failed to create the audit file '%s'. Make sure that the disk is not full and that the SQL service account has the required permissions to create and write to the file. 0 0
33207 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. 0 0
33208 SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log. 0 0
33209 Audit '%.*ls' has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server was started with the -m flag. 0 0
33210 SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting. 0 0
33211 A list of subentities, such as columns, cannot be specified for entity-level audits. 0 0
33212 There is an invalid column list after the object name in the AUDIT SPECIFICATION statement. 0 0
33213 All actions in an audit specification statement must be at the same scope. 0 0
33214 The operation cannot be performed because SQL Server Audit has not been started. 0 0
33215 One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with each error. 0 0
33216 SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required. 0 0
33217 SQL Server Audit is starting the audits. This is an informational message. No user action is required. 0 0
33218 SQL Server Audit has started the audits. This is an informational message. No user action is required. 0 0
33219 The server was stopped because SQL Server Audit '%.*ls' is configured to shut down on failure. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting. 0 0
33220 Audit actions at the server scope can only be granted when the current database is master. 0 0
33221 You can only create audit actions on objects in the current database. 0 0
33222 Audit '%.*ls' failed to %.*ls. For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_XE_LOG'. 0 0
33223 ALTER SERVER AUDIT requires the STATE option to be specified without using any other options. 0 0
33224 The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command. 0 0
33225 The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file set. Verify the file name and offset location, and then rerun the command. 0 0
33226 The fn_get_audit_file function is skipping records from '%.*ls' at offset %I64d. 0 0
33227 The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher. 0 0
33228 You cannot configure SQL Server Audit to shutdown the server because you do not have the permission to shut down the server. Contact your system administrator. 0 0
33229 Changes to an audit specification must be done while the audit specification is disabled. 0 0
33230 An audit specification for audit '%.*ls' already exists. 0 0
33231 You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements. 0 0
33301 The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and %d characters long. 0 0
33302 The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and 10. 0 0
33303 A conversation priority already exists in the database with either the name '%.*ls' or the properties %ls='%ls', %ls='%ls', and %ls='%.*ls'. Either use a unique name or a unique set of properties. 0 0
34001 Dialog with queue 'syspolicy_event_queue' has encountered an error: %s. 0 0
34002 Dialog with queue 'syspolicy_event_queue' has ended. 0 0
34003 Error number %d was encountered while processing an event. The error message is: %s. 0 0
34004 Execution mode %d is not a valid execution mode. 0 0
34010 %s '%s' already exists in the database. 0 0
34011 Specified value for property %s cannot be used with execution mode %d. 0 0
34012 Cannot delete %s referenced by a %s. 0 0
34013 %s '%s' is referenced by a '%s'. Cannot add another reference. 0 0
34014 Facet does not exist. 0 0
34015 Policy group %s does not exist. 0 0
34016 Invalid target filer: %s. Only filters that restrict the first level below the Server node are allowed. 0 0
34017 Automated policies cannot reference conditions that contain script. 0 0
34018 Target type "%s" is not a valid target type. 0 0
34019 Object "%s" is invalid. 0 0
34020 Configuration option "%s" is unknown. 0 0
34021 Invalid value type for configuration option "%s". Expecting "%s". 0 0
34022 Policy automation is turned off. 0 0
34050 %ls 0 0
34051 %ls 0 0
34052 %ls 0 0
34053 %ls 0 0
34054 Policy Management cannot be enabled on this edition of SQL Server. 0 0
34101 An error was encountered during object serialization operation. Examine the state to find out more details about this error. 0 0
34102 An object in serialized stream has version %u but maximum supported version of this class is %u. 0 0
34103 Error in formatter during serialize/deserialize. Required to process %d elements but processed only %d elements. 0 0
34104 An error was encountered during object serialization operation. The object that failed serialization is %hs. 0 0
2002 Cannot create a procedure for replication with group number greater than one. 0 0
2003 Procedures with a group number cannot have parameters of XML or CLR types. Parameter '%.*ls' of procedure '%.*ls' has type '%ls'. 0 0
2004 Procedure '%.*ls' has already been created with group number %d. Create procedure with an unused group number. 0 0
2007 The module '%.*ls' depends on the missing object '%.*ls'. The module will still be created; however, it cannot run successfully until the object exists. 0 0
2008 The object '%.*ls' is not a procedure so you cannot create another procedure under that group name. 0 0
2010 Cannot perform alter on '%.*ls' because it is an incompatible object type. 0 0
2011 Index hints cannot be specified within a schema-bound object. 0 0
2013 Warning: 'is_ms_shipped' property is turned off for %S_MSG '%.*ls' because you do not have permission to create or alter an object with this property. 0 0
2014 Remote access is not allowed from within a schema-bound object. 0 0
2020 The dependencies reported for entity "%.*ls" do not include references to columns. This is either because the entity references an object that does not exist or because of an error in one or more statements in the entity. Before rerunning the query, ensure that there are no errors in the entity and that all objects referenced by the entity exist. 0 0
2101 Cannot %S_MSG a server level %S_MSG for user '%.*ls' since there is no login corresponding to the user. 0 0
2102 Cannot %S_MSG %S_MSG '%.*ls' since there is no user for login '%.*ls' in database '%.*ls'. 0 0
2103 Cannot %S_MSG trigger '%.*s' because its schema is different from the schema of the target table or view. 0 0
2104 Cannot %S_MSG the %S_MSG '%.*ls', because you do not have permission. 0 0
2108 Cannot %S_MSG %S_MSG on '%.*ls' as the target is not in the current database. 0 0
2110 Cannot alter trigger '%.*ls' on '%.*ls' because this trigger does not belong to this object. Specify the correct trigger name or the correct target object name. 0 0
2111 Cannot %S_MSG trigger '%.*ls' on %S_MSG '%.*ls' because an INSTEAD OF %s trigger already exists on this object. 0 0
2112 Cannot create trigger '%.*ls' on view '%.*ls' because the view is defined with CHECK OPTION. 0 0
2113 Cannot %S_MSG INSTEAD OF DELETE or INSTEAD OF UPDATE TRIGGER '%.*ls' on table '%.*ls'. This is because the table has a FOREIGN KEY with cascading DELETE or UPDATE. 0 0
2114 Column '%.*ls' cannot be used in an IF UPDATE clause because it is a computed column. 0 0
2115 Server level event notifications are disabled as the database msdb does not exist. 0 0
2116 Cannot CREATE EVENT NOTIFICATION to database '%.*ls' because it is not a valid broker database. 0 0
2117 Cannot %S_MSG INSTEAD OF trigger '%.*ls' on %S_MSG '%.*ls' because the %S_MSG has a FILESTREAM column. 0 0
2201 %sDerivation from "anySimpleType" by restriction is not permitted, and derivation by restriction from a type derived from "anySimpleType" by extension is allowed only if no constraining facets are specified. 0 0
2202 %sAn error has occurred while compiling the query. To obtain more detailed information about the error, the query must be run by a user with EXECUTE permissions on the xml schema collection used in the query. 0 0
2203 %sOnly 'http://www.w3.org/2001/XMLSchema 0 0
2204 %sOnly 'http://www.w3.org/2001/XMLSchema 0 0
2205 %s"%ls" was expected. 0 0
2206 %sNamespace prefix 'xml' can only be associated with the URI 'http://www.w3.org/XML/1998/namespace' and this URI cannot be used with other prefixes. 0 0
2207 %sOnly non-document nodes can be inserted. Found "%ls". 0 0
2208 %sThe URI that starts with '%ls' is too long. Maximum allowed length is %d characters. 0 0
2209 %sSyntax error near '%ls' 0 0
2210 %sHeterogeneous sequences are not allowed: found '%ls' and '%ls' 0 0
2211 %sSingleton (or empty sequence) required, found operand of type '%ls' 0 0
2212 %sInvalid source character '%c' (0x%02x) found in an identifier near '%ls'. 0 0
2213 %sCannot atomize/apply data() on expression that contains type '%ls' within inferred type '%ls' 0 0
2214 %sThe type '%ls' is not an atomic type 0 0
2215 %sThe value of attribute '%ls' exceeds 4000 characters, the maximum permitted in XML schema documents 0 0
2216 %sInvalid XPath value in "%ls". 0 0
2217 %s'%ls' or '%ls' expected 0 0
2218 %sThere is no attribute named '@%ls' 0 0
2219 %sThere is no attribute named '@%ls' in the type '%ls'. 0 0
2220 %sThere is no attribute named '@%ls:%ls' 0 0
2221 %sThere is no attribute named '@%ls:%ls' in the type '%ls'. 0 0
2222 %sInvalid source character 0x%02x found in an identifier near '%ls'. 0 0
2223 %sSyntax error near '%ls', expected an identifier. 0 0
2225 %sA string literal was expected 0 0
2226 %sThe target of 'insert' must be a single node, found '%ls' 0 0
2227 %sThe variable '%ls' was not found in the scope in which it was referenced. 0 0
2228 %sThe variable '%ls:%ls' was not found in the scope in which it was referenced. 0 0
2229 %sThe name "%ls" does not denote a namespace. 0 0
2230 %sThe name "%ls" has already been defined. 0 0
2231 %sThe name "%ls" does not denote a defined type. 0 0
2232 %sThe name "%ls:%ls" does not denote a defined type. 0 0
2233 %sThe operand of "%ls" has an invalid type. 0 0
2234 %sThe operator "%ls" cannot be applied to "%ls" and "%ls" operands. 0 0
2235 %sAn argument list was applied to a non-function term. 0 0
2236 %sThere are not enough actual arguments in the call to function "%ls". 0 0
2237 %sDerivation from anyType by extension is not supported in this release. 0 0
2238 %sToo many arguments in call to function '%ls' 0 0
2240 %sThe target of 'insert into' must be an element/document node, found '%ls' 0 0
2241 %sVariable expected: '$name' 0 0
2242 %sType specification expected. 0 0
2243 %sRelative path expression used without any context 0 0
2247 %sThe value is of type "%ls", which is not a subtype of the expected type "%ls". 0 0
2248 %sSyntax error near '%ls', expected 'as', 'into', 'before' or 'after'. 0 0
2249 %sThe target of 'insert before/after' must be an element/PI/comment/text node, found '%ls' 0 0
2256 %sSyntax error near '%ls', expected a "node test". 0 0
2258 %sThe position may not be specified when inserting an attribute node, found '%ls' 0 0
2260 %sThere is no element named '%ls' 0 0
2261 %sThere is no element named '%ls' in the type '%ls'. 0 0
2262 %sThere is no element named '%ls:%ls' 0 0
2263 %sThere is no element named "%ls:%ls" in the type "%ls". 0 0
2264 %sOnly non-document nodes may be deleted, found '%ls' 0 0
2266 %sExpected end tag '%ls:%ls' 0 0
2267 %sExpected end tag '%ls' 0 0
2268 %sEnd tag '/%ls:%ls' has no matching begin tag 0 0
2269 %sEnd tag '/%ls' has no matching begin tag 0 0
2270 %sDuplicate attribute '%ls:%ls' 0 0
2271 %sDuplicate attribute '%ls' 0 0
2272 %s'?>' expected 0 0
2273 %sUnterminated CDATA section 0 0
2274 %sUnterminated string constant (started on line %u) 0 0
2275 %sUnterminated XML declaration 0 0
2276 %sDerivation from 'QName' by restriction is not supported in this release 0 0
2277 %sA tag name may not contain the character '%c' 0 0
2278 %sA tag name may not start with the character '%c' 0 0
2279 %sA name/token may not start with the character '%c' 0 0
2280 %s 0 0
2281 %sCannot construct DTDs in XQuery 0 0
2282 %sInvalid entity reference 0 0
2283 %sThe character '%c' may not be part of an entity reference 0 0
2284 %sThe namespace prefix '%ls' has not been defined 0 0
2285 %sInvalid numeric entity reference 0 0
2291 %sNo root element was found. 0 0
2292 %sWhen a type with simple content restricts a type with mixed content, it must have an embedded simple type definition. Location: '%ls'. 0 0
2293 %sChoice cannot be empty unless minOccurs is 0. Location: '%ls'. 0 0
2294 %s'xml' is not allowed as a processing instruction target. 0 0
2297 %sElement <%ls> is not valid at location '%ls'. 0 0
2298 %sAttribute '%ls' is not valid at location '%ls'. 0 0
2299 %sRequired attribute "%ls" of XSD element "%ls" is missing. 0 0
2300 %sRequired sub-element "%ls" of XSD element "%ls" is missing. 0 0
2301 %sThe element "%ls" has already been defined. 0 0
2302 %sThe name "%ls" has already been defined in this scope. 0 0
2305 %sElement or attribute type specified more than once. Location: '%ls'. 0 0
2306 %sThe qualified name "%ls" was found in a context where only NCName is allowed. 0 0
2307 %sReference to an undefined name '%ls' 0 0
2308 %sReference to an undefined name '%ls' within namespace '%ls' 0 0
2309 %sThe value of "%ls" is not a valid number. 0 0
2310 %sThe attribute "%ls" is declared more than once. 0 0
2311 %sThe attribute "%ls" is declared more than once within "%ls". 0 0
2312 %sThe value of attribute '%ls' does not conform to the type definition 'http://www.w3.org/2001/XMLSchema 0 0
2313 %sThe attribute "%ls" cannot have a value of "%ls". 0 0
2314 %sThe attribute "%ls" cannot have a negative value. 0 0
2315 %sThe attribute "%ls" should have a string value. 0 0
2316 %sThe required 'base' attribute is missing. Location: '%ls'. 0 0
2317 %sThe base type "%ls" defined on XSD element "%ls" is not a simple type. 0 0
2319 %sThis type may not have a '%ls' facet. Location: '%ls'. 0 0
2320 %sDuplicate facet '%ls' found at location '%ls'. 0 0
2321 %sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'. 0 0
2322 %sThe element type is not a subclass of the substitution group's head 0 0
2323 %sThe end tag '%ls' doesn't match opening tag '%ls' from line %u 0 0
2324 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls' from line %u 0 0
2325 %sThe end tag '%ls' doesn't match opening tag '%ls:%ls' from line %u 0 0
2326 %sThe end tag '%ls:%ls' doesn't match opening tag '%ls:%ls' from line %u 0 0
2327 %sThe content or definition of <%ls> is missing. 0 0
2328 %sSchema namespace '%ls' doesn't match directive's '%ls' 0 0
2329 %sThe string "%ls" is not a valid time duration value. 0 0
2331 %sRedefinition has to have itself as base type. Location: '%ls'. 0 0
2332 %s'%ls' may not be used with an 'empty' operand 0 0
2333 %sInvalid source character 0x%02x 0 0
2334 %sInvalid source character '%c' (0x%02x) 0 0
2335 %sNewline in character/string constant 0 0
2336 %s'%c' is not a valid octal digit (numbers starting with '0' are implicitly octal) 0 0
2337 %sThe target of 'replace' must be at most one node, found '%ls' 0 0
2338 %sThe second 'replace' operand must contain only nodes, found '%ls' 0 0
2339 %sEither a memberType attribute or a simpleType child must be present. Location: '%ls'. 0 0
2340 %sComment started on line %u has no end 0 0
2341 %sExpected hex character code following '\\x' 0 0
2342 %sInvalid numeric constant. 0 0
2343 %sUnterminated text section - missing ` 0 0
2348 %sA namespace URI should contain at least one non-whitespace character. 0 0
2349 %sAttempt to redefine namespace prefix '%ls' 0 0
2350 %sInvalid XML element content 0 0
2351 %sExpected 'first' or 'last' 0 0
2353 %s'to' or 'insert' or 'delete' expected 0 0
2354 %sInvalid source character encoding 0 0
2355 %s'else' expected 0 0
2356 %sThe target of 'replace value of' must be a non-metadata attribute or an element with simple typed content, found '%ls' 0 0
2357 %sA document node may only be replaced with another document node, found '%ls' 0 0
2358 %sDerivation with both a 'base' attribute and an embedded type definition is not supported in this release. Location: '%ls'. 0 0
2359 %sThe target of '%ls' may not be a constructed node 0 0
2360 %sCannot have both a 'name' and 'ref' attribute. Location: '%ls'. 0 0
2361 %sThe base type of an XSD extension or restriction type must be a simple type. 0 0
2362 %sXSD schema too complex 0 0
2363 %sXQuery too complex 0 0
2364 %sCannot implicitly convert from '%ls' to '%ls' 0 0
2365 %sCannot explicitly convert from '%ls' to '%ls' 0 0
2366 %s"%ls" has a circular definition. 0 0
2367 %sThe item type of an XSD list type must be a simple type. Location: '%ls'. 0 0
2368 %sCannot have element content in a complex type with simple content. Location: '%ls'. 0 0
2369 %sCannot have more than one group/sequence/choice/all within a restriction or extension. Location: '%ls'. 0 0
2370 %sNo more tokens expected at the end of the XQuery expression. Found '%ls'. 0 0
2371 %s'%ls' can only be used within a predicate or XPath selector 0 0
2372 %sMetadata attribute '@%ls:%ls' may not be used with '%ls' 0 0
2373 %s%ls is not supported with constructed XML 0 0
2374 %sA node or set of nodes is required for %ls 0 0
2375 %sAggregate function '%ls' expects a sequence argument 0 0
2376 %sOperand of a single numeric type expected 0 0
2377 %sResult of '%ls' expression is statically 'empty' 0 0
2378 %sExpected XML schema document 0 0
2379 %sThe name specified is not a valid XML name :'%ls' 0 0
2380 %sMixed content is not allowed at location '%ls'. 0 0
2382 %sInvalid combination of minOccurs and maxOccurs values, minOccurs has to be less than or equal to maxOccurs. Location: '%ls'. 0 0
2383 %sInvalid value '%ls' for the %ls attribute. The value has to be between 0 and %ld. 0 0
2384 %sInvalid element occurrence, element '%ls' was found multiple times in the context of element '%ls' 0 0
2385 Invalid target namespace specified 0 0
2386 %sThe value of '%ls' facet is outside of the allowed range 0 0
2387 %sCannot have both 'type' and 'ref' attributes. Location: '%ls'. 0 0
2388 %sInvalid element occurrence, element '%ls' has to appear first in the context of '%ls' 0 0
2389 %s'%ls' requires a singleton (or empty sequence), found operand of type '%ls' 0 0
2390 %sTop-level %s nodes are not supported 0 0
2391 %sRedefining XSD schemas is not supported 0 0
2392 %s'%ls::' is not a valid axis 0 0
2393 %sEither an itemType attribute or a simpleType child must be present. Location: '%ls'. 0 0
2394 %sThere is no function '%ls()' 0 0
2395 %sThere is no function '%ls:%ls()' 0 0
2396 %sAttribute may not appear outside of an element 0 0
2397 %sIdentifiers may not contain more than %u characters 0 0
2398 %sDuplicate id value found: '%ls' 0 0
2399 %sAn attribute cannot have a value of type '%ls', a simple type was expected 0 0
2501 Cannot find a table or object with the name "%.*ls". Check the system catalog. 0 0
2502 Memory object list dump failed due to temporary inconsistency in the memory object structure. Please try again. 0 0
2503 Successfully deleted the physical file '%ls'. 0 0
2504 Could not delete the physical file '%ls'. The DeleteFile system function returned error %ls. 0 0
2505 The device '%.*ls' does not exist. Use sys.backup_devices to show available devices. 0 0
2506 Could not find a table or object name '%.*ls' in database '%.*ls'. 0 0
2507 The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS. 0 0
2508 The %.*ls count for object "%.*ls", index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE. 0 0
2509 DBCC CHECKCONSTRAINTS failed due to an internal query error. 0 0
2510 DBCC %ls error: %ls. 0 0
2511 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d. 0 0
2512 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S_PGID slot %d. 0 0
2514 A DBCC PAGE error has occurred: %ls. 0 0
2515 The page %S_PGID, object ID %d, index ID %d, partition ID %I64d, allocation unit ID %I64d (type %.*ls) has been modified, but is not marked as modified in the differential backup bitmap. 0 0
2516 Repair has invalidated the differential bitmap for database %.*ls. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup. 0 0
2517 Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again. 0 0
2518 Object ID %ld (object "%.*ls"): Computed columns and CLR types cannot be checked for this object because the common language runtime (CLR) is disabled. 0 0
2519 Computed columns and CLR types cannot be checked for object ID %ld (object "%.*ls") because the internal expression evaluator could not be initialized. 0 0
2520 Could not find database '%.*ls'. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists by querying the sys.databases catalog view. 0 0
2521 Could not find database ID %d. The database ID either does not exist, or the database was dropped before a statement tried to use it. Verify if the database ID exists by querying the sys.databases catalog view. 0 0
2522 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid. 0 0
2523 Filegroup %.*ls is invalid. 0 0
2524 Cannot process object ID %ld (object "%.*ls") because it is a Service Broker queue. Try the operation again with the object ID of the corresponding internal table for the queue, found in sys.internal_tables. 0 0
2525 Database file %.*ls is offline. 0 0
2526 Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options. 0 0
2527 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline. 0 0
2528 DBCC execution completed. If DBCC printed error messages, contact your system administrator. 0 0
2529 Filegroup %.*ls is offline. 0 0
2530 The index "%.*ls" on table "%.*ls" is disabled. 0 0
2530 Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID. 0 0
2532 One or more WITH options specified are not valid for this command. 0 0
2533 Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. 0 0
2534 Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), is allocated by another object. 0 0
2536 DBCC results for '%.*ls'. 0 0
2537 Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%hs) failed. The values are %I64d and %I64d. 0 0
2538 File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d. 0 0
2539 The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database. 0 0
2540 The system cannot self repair this error. 0 0
2541 DBCC UPDATEUSAGE: Usage counts updated for table '%.*ls' (index '%.*ls', partition %ld): 0 0
2542 DATA pages %.*ls: changed from (%I64d) to (%I64d) pages. 0 0
2543 USED pages %.*ls: changed from (%I64d) to (%I64d) pages. 0 0
2544 RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages. 0 0
2545 ROWS count: changed from (%I64d) to (%I64d) rows. 0 0
2546 Index '%.*ls' on table '%.*ls' is marked as disabled. Rebuild the index to bring it online. 0 0
2547 Unable to process object ID %ld (object "%.*ls") because it is a synonym. If the object referenced by the synonym is a table or view, retry the operation using the base object that the synonym references. 0 0
2548 DBCC: Compaction phase of index '%.*ls' is %d%% complete. 0 0
2549 DBCC: Defrag phase of index '%.*ls' is %d%% complete. 0 0
2550 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because it is being reorganized by another process. 0 0
2551 The indexes on table "%.*ls" cannot be reorganized because there is already an online index build or rebuild in progress on the table. 0 0
2552 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because page level locking is disabled. 0 0
2553 Table '%.*ls' will not be available during reorganizing index '%.*ls'. This is because the index reorganization operation performs inside a user transaction and the entire table is exclusively locked. 0 0
2554 The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because the filegroup is read-only. 0 0
2555 Cannot move all contents of file "%.*ls" to other places to complete the emptyfile operation. 0 0
2556 There is insufficient space in the filegroup to complete the emptyfile operation. 0 0
2557 User '%.*ls' does not have permission to run DBCC %ls for object '%.*ls'. 0 0
2558 %I64d incorrect counts were detected in database '%.*ls'. 0 0
2559 The '%ls' and '%ls' options are not allowed on the same statement. 0 0
2560 Parameter %d is incorrect for this DBCC statement. 0 0
2561 Parameter %d is incorrect for this statement. 0 0
2562 Checking FILESTREAM filegroup "%.*ls" (ID %d) is not supported in DBCC CHECKFILEGROUP. Specify a filegroup containing user objects with FILESTREAM data instead. 0 0
2566 DBCC DBREINDEX cannot be used on system tables. 0 0
2567 DBCC INDEXDEFRAG cannot be used on system table indexes 0 0
2568 Page %S_PGID is out of range for this database or is in a log file. 0 0
2570 Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type "%.*ls"). Column "%.*ls" value is out of range for data type "%.*ls". Update column to a legal value. 0 0
2571 User '%.*ls' does not have permission to run DBCC %.*ls. 0 0
2572 DBCC cannot free DLL '%.*ls'. The DLL is in use. 0 0
2573 Could not find table or object ID %.*ls. Check system catalog. 0 0
2574 Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree. 0 0
2575 The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan. 0 0
2576 The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan. 0 0
2577 Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d. 0 0
2579 Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database. 0 0
2580 Table '%.*ls' is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table. 0 0
2581 DBCC cannot free the DLL "%.*ls". The DLL is not loaded. 0 0
2583 An incorrect number of parameters was given to the DBCC statement. 0 0
2585 Cannot find partition number %ld for table "%.*ls". 0 0
2586 Cannot find partition number %ld for index "%.*ls", table "%.*ls". 0 0
2587 The invalid partition number %ld was specified. 0 0
2588 Cannot find partition number %ld for index ID %d, object ID %d. 0 0
2589 Repair could not fix all errors on the first attempt. 0 0
2590 User "%.*ls" is modifying bytes %d to %d of page %S_PGID in database "%.*ls". 0 0
2591 Cannot find a row in the system catalog with the index ID %d for table "%.*ls". 0 0
2592 Repair: The %ls index successfully rebuilt for the object "%.*ls" in database "%.*ls". 0 0
2593 There are %I64d rows in %I64d pages for object "%.*ls". 0 0
2594 Cannot process rowset ID %I64d of object "%.*ls" (ID %d), index "%.*ls" (ID %d), because it resides on filegroup "%.*ls" (ID %d), which was not checked. 0 0
2596 The repair statement was not processed. The database cannot be in read-only mode. 0 0
2597 Ignoring trace flag %d. It is either an invalid trace flag or a trace flag that can only be specified during server startup. 0 0
2599 Cannot switch to in row text in table "%.*ls". 0 0
2601 Cannot insert duplicate key row in object '%.*ls' with unique index '%.*ls'. 0 0
2627 Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'. 0 0
2701 Database name '%.*ls' ignored, referencing object in tempdb. 0 0
2702 Database '%.*ls' does not exist. 0 0
2703 Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once. 0 0
2704 Invalid partition scheme '%.*ls' specified. 0 0
2705 Column names in each table must be unique. Column name '%.*ls' in table '%.*ls' is specified more than once. 0 0
2706 Table '%.*ls' does not exist. 0 0
2707 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it depends on a non-schemabound object. 0 0
2709 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it does user or system data access. 0 0
2710 You are not the owner specified for the object '%.*ls' in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT). 0 0
2711 The definition of object "%.*ls" in the resource database contains the non-ASCII character "%.*ls". 0 0
2712 Database '%.*ls' can not be configured as a distribution database because it has change tracking enabled. 0 0
2714 There is already an object named '%.*ls' in the database. 0 0
2715 Column, parameter, or variable 0 0
2716 Column, parameter, or variable 0 0
2717 The size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed (%d). 0 0
2719 Upgrade of database "%.*ls" failed because it contains a user named "sys" which is a reserved user or schema name in this version of SQL Server. 0 0
2720 Cannot schema bind %S_MSG '%.*ls' because it references system object '%.*ls'. 0 0
2722 Xml data type methods are not allowed in expressions in this context. 0 0
2724 Parameter or variable '%.*ls' has an invalid data type. 0 0
2725 An online operation cannot be performed for %S_MSG '%.*ls' because the index contains column '%.*ls' of data type text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml, or large CLR type. For a non-clustered index, the column could be an include column of the index. For a clustered index, the column could be any column of the table. If DROP_EXISTING is used, the column could be part of a new or old index. The operation must be performed offline. 0 0
2726 Partition function '%.*ls' uses %d columns which does not match with the number of partition columns used to partition the table or index. 0 0
2727 Cannot find index '%.*ls'. 0 0
2728 Cannot partition on more than %d columns. 0 0
2729 Column '%.*ls' in %S_MSG '%.*ls' cannot be used in an index or statistics or as a partition key because it is non-deterministic. 0 0
2730 Cannot create procedure '%.*ls' with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE '%.*ls';1 first. 0 0
2731 Column '%.*ls' has invalid width: %d. 0 0
2732 Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000. 0 0
2733 The %ls data type is invalid for return values. 0 0
2735 Cannot create primary xml or spatial index '%.*ls' on '%.*ls' because PRIMARY KEY constraint contains column(s) of type timestamp. 0 0
2738 A table can only have one timestamp column. Because table '%.*ls' already has one, the column '%.*ls' cannot be added. 0 0
2739 The text, ntext, and image data types are invalid for local variables. 0 0
2740 SET LANGUAGE failed because '%.*ls' is not an official language name or a language alias on this SQL Server. 0 0
2741 SET DATEFORMAT date order '%.*ls' is invalid. 0 0
2742 SET DATEFIRST %d is out of range. 0 0
2743 %ls statement requires %S_MSG parameter. 0 0
2744 Multiple identity columns specified for table '%.*ls'. Only one identity column per table is allowed. 0 0
2745 Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process. 0 0
2747 Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters. 0 0
2748 Cannot specify %ls data type (parameter %d) as a substitution parameter. 0 0
2749 Identity column '%.*ls' must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, and constrained to be nonnullable. 0 0
2750 Column or parameter 0 0
2751 Column or parameter 0 0
2752 Identity column '%.*ls' contains invalid SEED. 0 0
2753 Identity column '%.*ls' contains invalid INCREMENT. 0 0
2754 Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option. 0 0
2755 SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d ... %d] of type integer}. 0 0
2756 Invalid value %d for state. Valid range is from %d to %d. 0 0
2759 CREATE SCHEMA failed due to previous errors. 0 0
2760 The specified schema name "%.*ls" either does not exist or you do not have permission to use it. 0 0
2761 The ROWGUIDCOL property can only be specified on the uniqueidentifier data type. 0 0
2762 sp_setapprole was not invoked correctly. Refer to the documentation for more information. 0 0
2766 The definition for user-defined data type '%.*ls' has changed. 0 0
2767 Could not locate statistics '%.*ls' in the system catalogs. 0 0
2770 The SELECT INTO statement cannot have same source and destination tables. 0 0
2772 Cannot access temporary tables from within a function. 0 0
2773 The collation ID is corrupted because the sort order ID %d is not valid. 0 0
2774 Collation ID %d is invalid. 0 0
2775 The code page %d is not supported by the server. 0 0
2778 Only System Administrator can specify %s option for %s command. 0 0
2779 The %S_MSG '%.*ls' is an auto-drop system object. It cannot be used in queries or DDL. 0 0
2780 View '%.*ls' is not schemabound. 0 0
2782 Cannot create table "%.*ls": A table must have a clustered primary key in order to have XML data type columns. 0 0
2785 User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this context. 0 0
2786 The data type of substitution parameter %d does not match the expected type of the format specification. 0 0
2787 Invalid format specification: '%.*ls'. 0 0
2788 Synonyms are invalid in a schemabound object or a constraint expression. 0 0
2789 Must specify a two-part name for %S_MSG '%.*ls' in a schemabound object or a constraint expression. 0 0
2790 Cannot use a column of type TEXT, NTEXT, or IMAGE in a constraint expression. 0 0
2791 Could not resolve expression for Schema-bound object or constraint. 0 0
2792 Cannot specify a sql CLR type in a Schema-bound object or a constraint expression. 0 0
2793 Specified owner name '%.*ls' either does not exist or you do not have permission to act on its behalf. 0 0
2794 Message text expects more than the maximum number of arguments (%d). 0 0
2795 Could not %S_MSG %S_MSG because the new %S_MSG '%.*ls' does not match the FILESTREAM %S_MSG '%.*ls' of the table. 0 0
2796 Cannot specify database name with $partition in a Schema-bound object, computed column or constraint expression. 0 0
2797 The default schema does not exist. 0 0
2798 Cannot create index or statistics '%.*ls' on table '%.*ls' because SQL Server cannot verify that key column '%.*ls' is precise and deterministic. Consider removing column from index or statistics key, marking computed column persisted, or using non-CLR-derived column in key. 0 0
2799 Cannot create index or statistics '%.*ls' on table '%.*ls' because the computed column '%.*ls' is imprecise and not persisted. Consider removing column from index or statistics key or marking computed column persisted. 0 0
2801 The definition of object '%.*ls' has changed since it was compiled. 0 0
2802 SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to 'DBCC FREEPROCCACHE' or 'DBCC FREESYSTEMCACHE' operations. 0 0
2803 SQL Server has encountered %d occurrence(s) of cachestore flush for the '%s' cachestore (part of plan cache) due to some database maintenance or reconfigure operations. 0 0
2809 The request for %S_MSG '%.*ls' failed because '%.*ls' is a %S_MSG object. 0 0
2812 Could not find stored procedure '%.*ls'. 0 0
2813 %.*ls is not supported on this edition of SQL Server. 0 0
2814 A possible infinite recompile was detected for SQLHANDLE %hs, PlanHandle %hs, starting offset %d, ending offset %d. The last recompile reason was %d. 0 0
9001 The log for database '%.*ls' is not available. Check the event log for related error messages. Resolve any errors and restart the database. 0 0
9002 The transaction log for database '%.*ls' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases 0 0
9003 The log scan number %S_LSN passed to log scan in database '%.*ls' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. 0 0
9004 An error occurred while processing the log for database '%.*ls'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. 0 0
9005 Either start LSN or end LSN specified in OpenRowset(DBLog, ...) is invalid. 0 0
9006 Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d. 0 0
9007 Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file. 0 0
9008 Cannot shrink log file %d (%s) because the logical log file located at the end of the file is in use. 0 0
9009 Cannot shrink log file %d (%s) because of minimum log space required. 0 0
9010 User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission 0 0
9011 User does not have permission to query backup files with the virtual table DBLog. Only members of the sysadmin fixed server role has this permission 0 0
9012 There have been %d misaligned log IOs which required falling back to synchronous IO. The current IO is on file %ls. 0 0
9013 The tail of the log for database %ls is being rewritten to match the new sector size of %d bytes. %d bytes at offset %I64d in file %ls will be written. 0 0
9014 An error occurred while processing the log for database '%.*ls'. THe log block version is higher than this server allows. 0 0
9015 The log record at LSN %S_LSN is corrupted. 0 0
9016 An error occurred while processing the log for database '%.*ls'. The log block could not be decrypted. 0 0
9100 Possible index corruption detected. Run DBCC CHECKDB. 0 0
9101 auto statistics internal 0 0
9104 auto statistics internal 0 0
9105 The provided statistics stream is corrupt. 0 0
9106 Histogram support not allowed for input data type 0x%08x. 0 0
9201 %d active query notification subscription(s) in database '%.*ls' owned by security identification number '%.*ls' were dropped. 0 0
9202 The query notification subscription message is invalid. 0 0
9204 The query notification subscription timeout is invalid. The allowed range is 1 through 2147483647. 0 0
9205 User "%.*ls" does not have permission to request query notification subscriptions on database "%.*ls". 0 0
9206 The query notification subscription "%ld" cannot be deleted because it does not exist or it has already been fired. 0 0
9207 The query notification dialog on conversation handle '%.*ls' closed due to the following error: '%.*ls'. 0 0
9208 Query notification subscription could not get dialog endpoint. Could not open service broker dialog for service name '%.*ls' of broker instance '%.*ls'. 0 0
9209 Query notification subscription could not begin dialog with service name '%.*ls' of broker instance '%.*ls'. 0 0
9210 Query notification delivery could not send message on dialog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker: '%.*ls'. 0 0
9211 Failed to check for pending query notifications in database "%d" because of the following error when opening the database: '%.*ls'. 0 0
9213 Query notification subscription could not access database with id %d. Could not open broker dialog for service name '%.*ls' of broker instance '%.*ls'. 0 0
9214 The query notification delivery failed to decode the error message from the Service Broker. 0 0
9215 Query notification delivery failed to encode message. Delivery failed for notification '%.*ls'. 0 0
9216 Failed to delete the expired query notification subscription "%d". 0 0
9217 Failed to drop the unused internal query notification table "%d" in database "%d". 0 0
9218 Query notifications reached the internal limit of the maximum number of objects. 0 0
9219 The query notification subscriptions cleanup operation failed. See previous errors for details. 0 0
9220 Query notification dialog on conversation handle '%.*ls' closed due to an unknown service broker error. 0 0
9221 Query notification delivery could not get dialog endpoint for dialog '%.*ls'. Delivery failed for notification '%.*ls' because of the following error in service broker '%.*ls'. 0 0
9222 Internal query notification table has an outdated schema and the table has been dropped. Query notification cleanup has not been performed for this table. 0 0
9223 %d active query notification subscription(s) owned by security identification number '%.*ls' were dropped. 0 0
9224 Query notification delivery could not access database with id %d. Delivery failed for notification '%.*ls'. 0 0
9225 The notification options identifier string has %d characters. The maximum allowed length is %d characters. 0 0
9226 A string value within the notification options identifier is too long. String with prefix '%.*ls' must be %d characters or less. 0 0
9227 Unmatched quote in notification options identifier string. 0 0
9228 Name expected in notification options identifier option. 0 0
9229 Unknown option name '%.*ls' present in notification options identifier. The following are valid option names: 'Service', 'Broker Instance', 'Local Database'. Option names cannot be quoted. 0 0
9230 Option '%ls' was specified multiple times in the notification options identifier. 0 0
9231 An equal (=) character was expected after the option name. Found '%.*ls' instead. 0 0
9232 A semicolon (;) must be use to separate options in a notification options identifier. String '%.*ls' was found following an option. 0 0
9233 The option 'Service' must be specified in the notification options identifier. 0 0
9234 The options 'Broker Instance' and 'Local Database' were both specified in the notification options identifier. 0 0
9235 Value missing for option '%ls' in notification options identifier. 0 0
9236 Database %.*ls is not a valid local database. 0 0
9237 Database %.*ls is not a valid broker database. 0 0
9238 Query notification subscriptions are not allowed under an active application role context. Consider re-issuing the request without activating the application role. 0 0
9239 Internal query notifications error: The garbage collector corrected an inconsistency. 0 0
9240 Service broker dialog '%.*ls' could not be closed due to a broker error in database with id '%d' because of the following error in service broker: '%.*ls'. 0 0
9241 Service broker dialog '%.*ls' could not be closed because the database with id '%d' is not available. Consider closing the dialogs manually once the database is available again. 0 0
9242 Query notification delivery could not get dialog endpoint for dialog '%.*ls'. Query notification delivery failed because of the following error in service broker: '%.*ls'. See the error log for additional information. 0 0
9243 Query notification delivery could not send message on dialog '%.*ls'. Query notification delivery failed because of the following error in service broker: '%.*ls'. See the error log for additional information. 0 0
9244 Query notification cleanup could not access metadata for database "%d". Check whether the database is successfully restored and online. 0 0
9300 %sIn this version of the server, the 'fn:id()' function only accepts an argument of type 'IDREF *'. 0 0
9301 %sIn this version of the server, 'cast as %s' is not available. Please use the 'cast as ?' syntax. 0 0
9302 %sThe context item in which the 'fn:id()' function is used must be a node. 0 0
9303 %sSyntax error near '%ls', expected '%ls'. 0 0
9304 %sThis version of the server only supports XQuery version '1.0'. 0 0
9305 %sOnly type names followed by '?' are supported in the target of 'instance of'. 0 0
9306 %sThe target of 'replace value of' cannot be a union type, found '%ls'. 0 0
9308 %sThe argument of '%ls' must be of a single numeric primitive type or 'http://www.w3.org/2004/07/xpath-datatypes 0 0
9309 %sThe target of 'replace value of' cannot be 'http://www.w3.org/2001/XMLSchema 0 0
9310 %sThe 'with' clause of 'replace value of' cannot contain constructed XML. 0 0
9311 %sHeterogeneous sequences are not allowed in '%ls', found '%ls' and '%ls'. 0 0
9312 %s'%ls' is not supported on simple typed or 'http://www.w3.org/2001/XMLSchema 0 0
9313 %sThis version of the server does not support multiple expressions or expressions mixed with strings in an attribute constructor. 0 0
9314 %sCannot implicitly atomize or apply 'fn:data()' to complex content elements, found type '%ls' within inferred type '%ls'. 0 0
9315 %sOnly constant expressions are supported for the name expression of computed element and attribute constructors. 0 0
9316 %sCannot use 'xmlns' in the name expression of computed attribute constructor. 0 0
9317 %sSyntax error near '%ls', expected string literal. 0 0
9318 %sSyntax error at source character '0x%02x' near '%ls', expected string literal. 0 0
9319 %sStatic simple type validation: Invalid simple type value '%ls'. 0 0
9320 %sThe result of applying the 'parent' axis on the document node is statically 'empty'. 0 0
9321 %sThe result of applying 'parent::%ls' is statically 'empty'. 0 0
9322 %sTwo consecutive '-' can only appear in a comment constructor if they are used to close the comment ('-->'). 0 0
9323 %sUsing ':' in variable names is not supported in this version of the server. 0 0
9324 %sFound '}' without matching '{'. If you want to use the characters '{' or '}', you need to escape them as '{{' or '}}' respectively. 0 0
9325 %sComputed processing instruction constructors are not supported. 0 0
9326 %sComputed comment constructors are not supported. 0 0
9327 %sAll prolog entries need to end with ';', found '%ls'. 0 0
9328 %sType specification expected, found '%ls'. 0 0
9330 %sOnly comparable types are allowed in '%ls', found '%ls'. 0 0
9331 %sSyntax error near '%ls', expected '%ls' or '%ls'. 0 0
9332 %sSyntax error near '%ls', expected 'where', '(stable) order by' or 'return'. 0 0
9333 %s'//' followed by 'self', 'parent' or 'descendant-or-self' axes is not supported when it encounters simple typed or 'http://www.w3.org/2001/XMLSchema 0 0
9334 %sThe 'form' attribute cannot be specified on a local attribute or element definition that has the 'ref' attribute. Location: '%ls'. 0 0
9335 %sThe XQuery syntax '%ls' is not supported. 0 0
9336 %sThe XML Schema syntax '%ls' is not supported. 0 0
9337 %sThe XML Schema type 'NOTATION' is not supported. 0 0
9338 %sThe value of a namespace declaration attribute must be a string literal. It cannot contain expressions. 0 0
9339 %sThe 'form' attribute cannot be specified on a global attribute or element definition. Location: '%ls'. 0 0
9340 %sExplicit import of the current target namespace is invalid. References to items in the current target namespace that have already been loaded in the schema collection will be resolved implicitly. 0 0
9341 %sSyntax error near '%ls', expected a step expression. 0 0
9342 %sAn XML instance is only supported as the direct source of an insert using sql:column/sql:variable. 0 0
9343 %sThe XML instance referred to by sql:column() and sql:variable() must be either untyped XML or must be typed with the same XML schema collection as the context XML instance on which the XML method is being applied to. 0 0
9344 %sThe SQL type '%s' is not supported with sql:column() and sql:variable(). 0 0
9400 XML parsing: line %d, character %d, unexpected end of input 0 0
9401 XML parsing: line %d, character %d, unrecognized encoding 0 0
9402 XML parsing: line %d, character %d, unable to switch the encoding 0 0
9403 XML parsing: line %d, character %d, unrecognized input signature 0 0
9410 XML parsing: line %d, character %d, whitespace expected 0 0
9411 XML parsing: line %d, character %d, semicolon expected 0 0
9412 XML parsing: line %d, character %d, '>' expected 0 0
9413 XML parsing: line %d, character %d, A string literal was expected 0 0
9414 XML parsing: line %d, character %d, equal expected 0 0
9415 XML parsing: line %d, character %d, well formed check: no '<' in attribute value 0 0
9416 XML parsing: line %d, character %d, hexadecimal digit expected 0 0
9417 XML parsing: line %d, character %d, decimal digit expected 0 0
9418 XML parsing: line %d, character %d, '[' expected 0 0
9419 XML parsing: line %d, character %d, '(' expected 0 0
9420 XML parsing: line %d, character %d, illegal xml character 0 0
9421 XML parsing: line %d, character %d, illegal name character 0 0
9422 XML parsing: line %d, character %d, incorrect document syntax 0 0
9423 XML parsing: line %d, character %d, incorrect CDATA section syntax 0 0
9424 XML parsing: line %d, character %d, incorrect comment syntax 0 0
9425 XML parsing: line %d, character %d, incorrect conditional section syntax 0 0
9426 XML parsing: line %d, character %d, incorrect ATTLIST declaration syntax 0 0
9427 XML parsing: line %d, character %d, incorrect DOCTYPE declaration syntax 0 0
9428 XML parsing: line %d, character %d, incorrect ELEMENT declaration syntax 0 0
9429 XML parsing: line %d, character %d, incorrect ENTITY declaration syntax 0 0
9430 XML parsing: line %d, character %d, incorrect NOTATION declaration syntax 0 0
9431 XML parsing: line %d, character %d, NDATA expected 0 0
9432 XML parsing: line %d, character %d, PUBLIC expected 0 0
9433 XML parsing: line %d, character %d, SYSTEM expected 0 0
9434 XML parsing: line %d, character %d, name expected 0 0
9435 XML parsing: line %d, character %d, one root element 0 0
9436 XML parsing: line %d, character %d, end tag does not match start tag 0 0
9437 XML parsing: line %d, character %d, duplicate attribute 0 0
9438 XML parsing: line %d, character %d, text/xmldecl not at the beginning of input 0 0
9439 XML parsing: line %d, character %d, namespaces beginning with "xml" are reserved 0 0
9440 XML parsing: line %d, character %d, incorrect text declaration syntax 0 0
9441 XML parsing: line %d, character %d, incorrect xml declaration syntax 0 0
9442 XML parsing: line %d, character %d, incorrect encoding name syntax 0 0
9443 XML parsing: line %d, character %d, incorrect public identifier syntax 0 0
9444 XML parsing: line %d, character %d, well formed check: pes in internal subset 0 0
9445 XML parsing: line %d, character %d, well formed check: pes between declarations 0 0
9446 XML parsing: line %d, character %d, well formed check: no recursion 0 0
9447 XML parsing: line %d, character %d, entity content not well formed 0 0
9448 XML parsing: line %d, character %d, well formed check: undeclared entity 0 0
9449 XML parsing: line %d, character %d, well formed check: parsed entity 0 0
9450 XML parsing: line %d, character %d, well formed check: no external entity references 0 0
9451 XML parsing: line %d, character %d, incorrect processing instruction syntax 0 0
9452 XML parsing: line %d, character %d, incorrect system identifier syntax 0 0
9453 XML parsing: line %d, character %d, '?' expected 0 0
9454 XML parsing: line %d, character %d, no ']]>' in element content 0 0
9455 XML parsing: line %d, character %d, illegal qualified name character 0 0
9456 XML parsing: line %d, character %d, multiple colons in qualified name 0 0
9457 XML parsing: line %d, character %d, colon in name 0 0
9458 XML parsing: line %d, character %d, redeclared prefix 0 0
9459 XML parsing: line %d, character %d, undeclared prefix 0 0
9460 XML parsing: line %d, character %d, non default namespace with empty uri 0 0
9461 XML %ls starting with '%.*ls' is %d characters long, which exceeds the limit. Maximum allowed length is %d characters. 0 0
9462 XML parsing: line %d, character %d, not all chunks of value have been read 0 0
9463 XML parsing: line %d, character %d, xml:space has a non-legal value 0 0
9464 XML parsing: line %d, character %d, XML namespace prefix 'xml' can only be associated with the URI http://www.w3.org/XML/1998/namespace. This URI cannot be used with other prefixes. 0 0
9465 XML parsing: line %d, character %d, XML namespace prefix 'xmlns' is reserved for use by XML. 0 0
9466 XML parsing: line %d, character %d, XML namespace xml namespace URI (http://www.w3.org/XML/1998/namespace) must be assigned only to prefix 'xml'. 0 0
9467 XML parsing: line %d, character %d, xmlns namespace URI (http://www.w3.org/2000/xmlns/) is reserved and must not be used. 0 0
9480 XML parsing: line %d, character %d, unsupported xml 0 0
9500 The data type '%.*ls' used in the VALUE method is invalid. 0 0
9501 XQuery: Unable to resolve sql:variable('%.*ls'). The variable must be declared as a scalar TSQL variable. 0 0
9502 The string literal provided for the argument %d of the '%.*ls' method must not exceed %d bytes. 0 0
9503 Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls'. See previous error messages for more details. 0 0
9504 Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls', invoked on column '%.*ls', table '%.*ls'. See previous error messages for more details. 0 0
9506 The XMLDT method '%.*ls' can only be invoked on columns of type xml. 0 0
9507 The XML data type method on a remote column used in this query can not be executed either locally or remotely. Please rewrite your query. 0 0
9508 The reference parameter given to XMLDT method '%.*ls' was generated from a different XML instance than the one it is being applied to. 0 0
9509 XMLUNNEST method requires typed xml column with single global element 0 0
9510 Functionality not yet implemented: XMLNODEREFS cannot use references exposed by views. 0 0
9512 Xml data type is not supported as a parameter to remote calls. 0 0
9513 Error processing XML data type method '%.*ls'. The following SET options required by XML data type methods are not set: '%.*ls'. 0 0
9514 Xml data type is not supported in distributed queries. Remote object '%.*ls' has xml column(s). 0 0
9515 An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch. 0 0
9516 XQuery: The name or one of the parts of a multi-part name supplied to %S_MSG('%.*ls') is empty. Empty names cannot be used to identify objects, columns or variables in SQL. 0 0
9517 XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it is too long. Maximum length is %d, actual length is %d. 0 0
9518 XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it contains invalid characters. 0 0
9519 XQuery: The name supplied to sql:variable('%.*ls') is not a valid SQL variable name. Variable names must start with the '@' symbol followed by at least one character. 0 0
9520 XQuery: '%.*ls' referenced by sql:variable() is not a valid system function name. 0 0
9521 Error processing XML data type. The XML data type instance contains a negative xs:date or xs:dateTime value. 0 0
9522 The XQuery modify method is not allowed on sparse column sets. 0 0
9523 Cannot update the sparse column set '%.*ls' because the XML content supplied references the non-sparse column '%.*ls' which does not belong to this column set. The XML data used to update a sparse column set cannot reference columns that don't belong to the column set. 0 0
9524 The XML content provided does not conform to the required XML format for sparse column sets. 0 0
9525 The XML content that is supplied for the sparse column set '%.*ls' contains duplicate references to the column '%.*ls'. A column can only be referenced once in XML content supplied to a sparse column set. 0 0
9526 In the XML content that is supplied for the sparse column set '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is out of range. The valid range is from 1 to %d. 0 0
9527 In the XML content that is supplied for the column set '%.*ls', the sqltypes:scale attribute value on the element '%.*ls' is out of range. The valid range for the scale is from 0 to the specified precision. 0 0
9528 In the XML content that is supplied for the column set '%.*ls', the '%.*ls' attribute on the element '%.*ls' is not valid. The attribute is valid only for sparse columns of data type sql_variant. 0 0
9529 In the XML content that is supplied for the column set column '%.*ls', the sqlDBType:base64Encoded attribute on the element '%.*ls' is not valid. The base64Encoded attribute can only be used when the corresponding sparse column is of character data type (char, varchar, nchar, nvarchar), or if the sparse column is of data type sql_variant and the value of the xsi:type attribute is "Char", "VarChar", "NChar", or "NVarChar". 0 0
9530 In the XML content that is supplied for the column set column '%.*ls, the '%.*ls' attribute on the element '%.*ls' is not valid. Remove the attribute. 0 0
9531 In the XML content that is supplied for the column set column '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is not valid. 0 0
9532 In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the column '%.*ls'. 0 0
9533 In the XML that is supplied for the column set '%.*ls', the element '%.*ls' should reside in the global namespace. Remove the default namespace declaration or the prefix on the element. 0 0
9534 In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the column '%.*ls'. Please refer to the Books-on-line for more details on providing XML conversion methods for CLR types. 0 0
9601 Cannot relate to %S_MSG %.*ls because it is %S_MSG. 0 0
9605 Conversation Priorities analyzed: %d. 0 0
9606 The conversation priority with ID %d has been dropped. 0 0
9607 The conversation priority with ID %d is referencing the missing service with ID %d. 0 0
9608 The conversation priority with ID %d is referencing the missing service contract with ID %d. 0 0
9609 The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d. 0 0
9610 The service '%.*ls' in the FROM SERVICE clause must match the service '%.*ls' referenced by %s = '%.*ls'. 0 0
9611 Cannot find the specified user '%.*ls'. 0 0
9613 The queue '%.*ls' cannot be activated because the activation user is not specified. 0 0
9614 The queue '%.*ls' cannot be activated because the activation stored procedure is either not specified or is invalid. 0 0
9615 A message of type '%.*ls' failed XML validation on the target service. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
9616 A message of type '%.*ls' was received and failed XML validation. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
9617 The service queue "%.*ls" is currently disabled. 0 0
9618 The message cannot be sent because the service queue '%.*ls' associated with the dialog is currently disabled and retention is on. 0 0
9619 Failed to create remote service binding '%.*ls'. A remote service binding for service '%.*ls' already exists. 0 0
9620 The activation stored procedure '%.*ls' is invalid. Functions are not allowed. 0 0
9621 An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i. 0 0
9622 The crypto provider context is not initialized. 0 0
9623 The key passed in for this operation is in the wrong state. 0 0
9624 The key size is unacceptable for this key object. 0 0
9625 The key buffer size is inconsistent with the key modulus size. 0 0
9626 An internal Service Broker error occurred: an object is in the wrong state for this operation. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems. 0 0
9627 The hash buffer size is not correct for initializing the hash object. 0 0
9628 The encryption/decryption data buffer size is not 8 byte aligned. 0 0
9629 The decrypted signature size is wrong. 0 0
9630 The signature did not verify the internal hash. 0 0
9631 The salt size is unacceptable for this key object. 0 0
9632 The salt buffer size is too small. 0 0
9633 The passed in name is too long. 0 0
9634 Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem. 0 0
9635 The certificate is not valid at this point in time. 0 0
9636 The requested object was not found. 0 0
9637 The passed in serialized object is incorrectly encoded. 0 0
9638 The cer or pvk file size is too large. 0 0
9639 A password was supplied and the pvk file is not encrypted. 0 0
9640 The operation encountered an OS error. 0 0
9641 A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for further information. 0 0
9642 An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far endpoint address: '%.*hs') 0 0
9643 An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i. 0 0
9644 An error occurred in the service broker message dispatcher. Error: %i, State: %i. 0 0
9645 An error occurred in the service broker manager, Error: %i, State: %i. 0 0
9646 An error occurred in the timer event cache. Error %i, state %i. 0 0
9647 Received a malformed message from the network. Unable to retrieve a broker message attribute from a message destined for database ID %d. This may indicate a network problem or that another application connected to the Service Broker endpoint. 0 0
9648 The queue '%.*ls' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider increasing the number of MAX_QUEUE_READERS. 0 0
9649 A security (SSPI) error occurred when connecting to another service broker: '%.*ls'. Check the Windows Event Log for more information. 0 0
9650 A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '%ls'. 0 0
9651 The system call failed during a Service Broker or Database Mirroring operation. System error: '%ls'. 0 0
9652 Service Broker failed to retrieve the session key for encrypting a message. 0 0
9653 The signature of activation stored procedure '%.*ls' is invalid. Parameters are not allowed. 0 0
9654 Attempting to use database and it doesn't exist. 0 0
9655 The transmission queue table structure in database is inconsistent. Possible database corruption. 0 0
9657 The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware problems. Check the SQL Server error log and the Windows event logs for information on possible hardware problems. Restart SQL Server to rebuild tempdb. 0 0
9658 Cannot access the transmission queue table in database. 0 0
9659 The %s of route '%.*ls' cannot be empty. 0 0
9660 The %s of route '%.*ls' must be less than %d characters long. 0 0
9661 The SERVICE_NAME and BROKER_INSTANCE of route "%.*ls" must be specified when using mirroring. 0 0
9662 Cannot specify BROKER_INSTANCE without SERVICE_NAME in route "%.*ls". 0 0
9663 The system object cannot be modified. 0 0
9666 The %S_MSG protocol transport is disabled or not configured. 0 0
9667 Services analyzed: %d. 0 0
9668 Service Queues analyzed: %d. 0 0
9669 Conversation Endpoints analyzed: %d. 0 0
9670 Remote Service Bindings analyzed: %d. 0 0
9671 Messages with conversation ID '%ls' have been removed from the transmission queue. 0 0
9672 Messages with conversation handle '%ls' and conversation group '%ls' have been removed from the queue with ID %d. 0 0
9673 Activation has been disabled on the queue with ID %d. 0 0
9674 Conversation Groups analyzed: %d. 0 0
9675 Message Types analyzed: %d. 0 0
9676 Service Contracts analyzed: %d. 0 0
9677 The service contract with ID %d is referencing the missing message type with ID %d. 0 0
9678 The service with ID %d is referencing the missing service contract with ID %d. 0 0
9679 The service with ID %d is referencing the missing service queue with ID %d. 0 0
9680 The conversation endpoint '%ls' is referencing the missing conversation group '%ls'. 0 0
9681 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service contract with ID %d. 0 0
9682 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service with ID %d. 0 0
9683 The conversation group '%ls' is referencing the missing service with ID %d. 0 0
9684 The service with ID %d has been dropped. 0 0
9685 The service contract with ID %d has been dropped. 0 0
9686 The conversation endpoint with handle '%ls' has been dropped. 0 0
9687 The conversation group '%ls' has been dropped. 0 0
9688 Service Broker manager has started. 0 0
9689 Service Broker manager has shut down. 0 0
9690 The %S_MSG protocol transport is now listening for connections. 0 0
9691 The %S_MSG protocol transport has stopped listening for connections. 0 0
9692 The %S_MSG protocol transport cannot listen on port %d because it is in use by another process. 0 0
9693 The %S_MSG protocol transport could not listen for connections due to the following error: '%.*ls'. 0 0
9694 Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages. 0 0
9695 Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem. 0 0
9696 Cannot start the Service Broker primary event handler. This error is a symptom of another problem. Check the SQL Server error log for additional messages, and address this underlying problem. 0 0
9697 Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages. 0 0
9698 Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address the underlying problem. 0 0
9699 Could not allocate memory for extra Service Broker tasks while adding CPUs. 0 0
9701 Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem. 0 0
9704 This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target service. 0 0
9705 The messages in the queue with ID %d are referencing the invalid conversation handle '%ls'. 0 0
9706 The stored procedure with ID %d is invalid but is referenced by the queue with ID %d. 0 0
9707 The activation user with ID %d is invalid but is referenced by queue with ID %d. 0 0
9708 The messages in the queue with ID %d are referencing the invalid conversation group '%ls'. 0 0
9709 The messages in the queue with ID %d are referencing the invalid message type with ID %d. 0 0
9710 The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation group '%ls'. 0 0
9711 The transmission queue is referencing the invalid conversation ID '%ls'. 0 0
9712 The remote service binding with ID %d is referencing the invalid service contract with ID %d. 0 0
9713 The message type with ID %d is referencing the invalid XML schema collection ID %d. 0 0
9715 The conversation endpoint with conversation handle '%ls' is in an inconsistent state. Check the SQL Server error logs and the Windows event logs for information on possible hardware problems. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data. 0 0
9716 The conversation group '%ls' reports references to %d conversation handle(s), but actually references %d. 0 0
9717 Cannot enable stored procedure activation on queue '%.*ls'. Event notification for queue_activation is already configured on this queue. 0 0
9718 Cannot create event notification for queue_activation on queue "%.*ls". Stored procedure activation is already configured on this queue. 0 0
9719 The database for this conversation endpoint is attached or restored. 0 0
9720 The database for the remote conversation endpoint is attached or restored. 0 0
9721 Service broker failed to clean up conversation endpoints on database '%.*ls'. Another problem is preventing SQL Server from completing this operation. Check the SQL Server error log for additional messages. 0 0
9723 The database "%i" will not be started as the broker due to duplication in the broker instance ID. 0 0
9724 The activated proc '%ls' running on queue '%ls' output the following: '%.*ls' 0 0
9725 The invalid schema has been dropped from the message type with ID %d. 0 0
9726 The remote service binding with ID %d has been dropped. 0 0
9727 Dialog security is not available for this conversation because there is no remote service binding for the target service. Create a remote service binding, or specify ENCRYPTION = OFF in the BEGIN DIALOG statement. 0 0
9728 Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped after the conversation was created. 0 0
9730 Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security principal may have been dropped after the conversation was created. 0 0
9731 Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: %i). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation. 0 0
9733 There is no private key for the security certificate bound to database principal (Id: %i). The certificate may have been created or installed incorrectly. Reinstall the certificate, or create a new certificate. 0 0
9734 The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes. 0 0
9735 The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes. 0 0
9736 An error occurred in dialog transmission: Error: %i, State: %i. %.*ls 0 0
9737 The private key for the security certificate bound to the database principal (ID %i) is password protected. Password protected private keys are not supported for use with secure dialogs. 0 0
9738 Cannot create task for Service Broker message dispatcher. This message is a symptom of another problem that is preventing SQL Server from creating tasks. Please check the SQL Server error log and the Windows event log for additional messages. 0 0
9739 Message transmitter in service broker message dispatcher failed %d times 0 0
9740 Cannot start the Service Broker message dispatcher. This error is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address this underlying problem. 0 0
9741 The %S_MSG '%.*ls' was dropped on upgrade because it referenced a system contract that was dropped. 0 0
9742 The activation stored procedure '%.*ls' is invalid. Temporary procedures may not be configured for activation. 0 0
9743 The %s of route "%.*ls" must be an address when using mirroring. 0 0
9744 The %s of route "%.*ls" is not a valid address. 0 0
9745 The ADDRESS of route '%.*ls' cannot be 'TRANSPORT' when SERVICE_NAME is specified. 0 0
9746 The LIFETIME of route '%.*ls' must be in the range %d to %d. 0 0
9747 The ADDRESS and MIRROR_ADDRESS of route '%.*ls' cannot be the same. 0 0
9748 The %S_MSG protocol transport is not available. 0 0
9749 Target queue is busy; message(s) queued for delivery. 0 0
9750 No No route matches the destination service name for this conversation. Create a route to the destination service name for messages in this conversation to be delivered. 0 0
9751 Authentication failed with error: '%.*ls'. 0 0
9752 %S_MSG connection was refused. The user account of the remote server is not permitted to log in to this SQL Server: User account: '%.*ls', IP address: '%.*hs'. 0 0
9753 The target service broker is unreachable. 0 0
9754 Connection attempt failed with error: '%.*ls'. 0 0
9755 An error occurred while receiving data: '%.*ls'. 0 0
9756 An internal exception occurred while connecting to an adjacent broker: Error: %i, State: %i. %.*ls 0 0
9757 Service Broker/Database Mirroring network protocol error occurred. 0 0
9758 Login protocol negotiation error occurred. 0 0
9759 An error occurred while sending data: '%.*ls'. 0 0
9761 The Broker Configuration conversation on dialog handle '%s' closed due to an error. To troubleshoot this problem, investigate the error: '%.*ls'. 0 0
9762 An error occurred while looking up the public key certificate associated with this SQL Server instance: No certificate was found. 0 0
9763 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is not valid at the current time. 0 0
9764 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is too large. 0 0
9765 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found has no associated private key. 0 0
9766 An unknown internal error (%d) occurred while looking up the public key certificate associated with this SQL Server instance. 0 0
9767 The security certificate bound to database principal (Id: %i) has been disabled for use with BEGIN DIALOG. See the Books Online topics "Certificates and Service Broker" for an overview and "ALTER CERTIFICATE (Transact-SQL)" for syntax to make a certificate ACTIVE FOR BEGIN_DIALOG. 0 0
9768 A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER while conversations are being created. 0 0
9769 Insufficient memory prevented the Service Broker/Database Mirroring Transport Manager from starting. 0 0
9770 Locating routes and security information via the Broker Configuration Service. 0 0
9771 The service broker manager is disabled in single-user mode. 0 0
9772 The Service Broker in database "%.*ls" cannot be enabled because there is already an enabled Service Broker with the same ID. 0 0
9773 The Service Broker in database "%d" is disabled because there is already an enabled Service Broker with the same ID. 0 0
9774 Cannot create a new Service Broker in the attached read-only database "%.*ls". The Service Broker will be disabled. 0 0
9775 Cannot create a new Service Broker in read-only database "%.*ls". 0 0
9776 Cannot enable the Service Broker in database "%.*ls" because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s). 0 0
9777 The Service Broker in database "%.*ls" will be disabled because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s). 0 0
9778 Cannot create a new Service Broker in a mirrored database "%.*ls". 0 0
9779 Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation. 0 0
9780 The service broker manager is initializing. 0 0
9781 The service broker manager is shutting down. 0 0
9782 An internal exception occurred while dispatching a message: Error: %i, State: %i. %.*ls 0 0
9783 DNS lookup failed with error: '%.*ls'. 0 0
9784 Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation. 0 0
9785 Invalid address specified: '%.*ls'. 0 0
9786 Cannot retrieve user name from security context. Error: '%.*ls'. State: %hu. 0 0
9787 An error occurred while processing broker mirroring routes. Error: %i. State: %i. 0 0
9788 Unable to route the incoming message. The system database msdb containing routing information is not available. 0 0
9789 Unable to route the incoming message. The system database msdb containing routing information is not available. The broker is disabled in msdb. 0 0
9790 Unable to route the incoming message. The system database msdb containing routing information is in SINGLE USER mode. 0 0
9791 The broker is disabled in the sender's database. 0 0
9792 Could not forward the message because forwarding is disabled in this SQL Server instance. 0 0
9793 The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied. 0 0
9794 The broker mirroring manager has not fully initialized. 0 0
9795 Could not find the target broker in the local SQL Server instance. 0 0
9796 The target service name matched a LOCAL route, but there is no service by that name in the local SQL Server instance. 0 0
9797 Classification has been delayed because the routing information is currently being updated. 0 0
9798 The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure. 0 0
9801 Error converting %.*ls to %ls. The result would be truncated. 0 0
9802 The locale identifier (LCID) %d is not supported by SQL Server. 0 0
9803 Invalid data for type "%ls". 0 0
9804 Column or parameter 0 0
9805 Warning: converting %ls to %ls caused a loss of information. 0 0
9806 The datepart %.*ls is not supported by date function %.*ls. 0 0
9807 The input character string does not follow style %d, either change the input character string or use a different style. 0 0
9808 This session's YDM date format is not supported when converting from this character string format to date, time, datetime2 or datetimeoffset. Change the session's date format or provide a style to the explicit conversion. 0 0
9809 The style %d is not supported for conversions from %s to %s. 0 0
9810 The datepart %.*ls is not supported by date function %.*ls for data type %s. 0 0
9811 The system timezone information could not be retrieved. 0 0
9812 The timezone provided to builtin function %.*ls is invalid. 0 0
9813 The timezone provided to builtin function %.*ls would cause the datetimeoffset to overflow the range of valid date range in either UTC or local time. 0 0
9814 The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. (Julian calendar) or July 18th, 622 C.E (proleptic Gregorian calendar). 0 0
9815 Waitfor delay and waitfor time cannot be of type %s. 0 0
9816 The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set. 0 0
9817 The specified column set value causes the estimated row size to be at least %d bytes. This exceeds the maximum allowed row size of %d bytes. To reduce the row size, reduce the number of columns specified in the column set. 0 0
9901 Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on disk space. Pausing all populations in progress until more space becomes available. Reason code: %d. Error: %ls. To resume populations, free up disk space. 0 0
9902 Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on system resources. Any population in progress will be paused until more resources become available. Reason code: %d. Error: %ls. If this message occurs frequently, try to serialize full-text indexing for multiple catalogs. 0 0
9903 The full-text catalog health monitor reported a failure for full-text catalog '%ls' (%d) in database '%ls' (%d). Reason code: %d. Error: %ls. The system will restart any in-progress population from the previous checkpoint. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required. 0 0
9904 The full-text catalog '%ls' (%d) in database '%ls' (%d) will be remounted to recover from a failure. Reason code: %d. Error: %ls. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required. 0 0
9905 Informational: Full-text indexer requested status change for catalog '%ls' ('%d') in database '%ls' ('%d'). New Status: %ls, Reason: %ls (%ls). 0 0
9906 The full-text catalog monitor reported catalog '%ls' (%d) in database '%ls' (%d) in %ls state. This is an informational message only. No user action is required. 0 0
9907 Error: Total number of items in full-text catalog ID '%d' in database ID '%d' exceeds the supported limit. See Books Online for troubleshooting assistance. 0 0
9908 Changing the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). This is an informational message only. No user action is required. 0 0
9909 Warning: Failed to change the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). Error: %ls. 0 0
9910 Warning: Error occurred during full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %ls. 0 0
9911 Informational: Full-text %ls population initialized for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Population sub-tasks: %d. 0 0
9912 Error: Failed to initialize full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %d. 0 0
9913 Informational: Resuming full-text population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). Prior number of documents processed: %d, error encountered: %d. 0 0
9914 Error: Failed to resume full-text %ls population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: 0x%x. Repeat the operation that triggered the resume, or drop and re-create the index. 0 0
9915 Reinitialized full-text %ls population for table '%ls' (table ID '%d', database ID '%d') after a temporary failure. Number of documents processed prior to failure: %d, errors encountered: %d. This is an informational message only. No user action is required. 0 0
9916 Error: Failed to reinitialize full-text %ls population after a temporary failure for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d'). Error: %d. 0 0
9917 An internal error occurred in full-text docid mapper. 0 0
9918 Warning: Full-text catalog '%ls' uses FAT volume. Security and differential backup are not supported for the catalog. 0 0
9919 Fulltext DDL command failed because SQL Server was started in single user mode. 0 0
9920 Warning: Failed to get MSFTESQL indexer interface for full-text catalog '%ls' ('%d') in database '%ls' ('%d'). Error: %ls. 0 0
9921 During upgrade fatal error 0x%x encountered in CoCreateGuid. Failed to resolve full-text catalog file name for '%ls'. 0 0
9922 Warning: Full-text population for table or indexed view '%ls' failed to send batch of data to MSFTESQL service (table or indexed view ID '%d', catalog ID '%d', database ID '%d'). Error: %ls. 0 0
9923 Warning: Full-text population for table or indexed view '%ls' reported low resources while sending a batch of data to MSFTESQL service (table or indexed view ID '%d', catalog ID '%d', database ID '%d'). Error: %ls. 0 0
9924 Rebuild full-text catalog '%ls' failed: Catalog header file is read-only. 0 0
9925 Rebuild full-text catalog '%ls' failed: Full-text catalog is read-only. 0 0
9926 Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should. 0 0
9927 Informational: The full-text search condition contained noise word(s). 0 0
9928 Computed column '%.*ls' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column. 0 0
9929 Computed column '%.*ls' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column must be deterministic, precise or persisted, with a size less or equal than %d characters. 0 0
9930 Null document type provided. Row will not be full-text indexed. 0 0
9931 Document type exceeds the maximum permitted length. Row will not be full-text indexed. 0 0
9932 Document type value is malformed. Row will not be full-text indexed. 0 0
9933 Internal error: The row cannot be full-text indexed. The protocol handler was invoked out of sequence. This is an informational message only. No user action is required. 0 0
9934 Row was not found. It was deleted or updated while indexing was in progress. 0 0
9935 Warning: Wordbreaker, filter, or protocol handler used by catalog '%ls' does not exist on this instance. Use sp_help_fulltext_catalog_components and sp_help_fulltext_system_components check for mismatching components. Rebuild catalog is recommended. 0 0
9936 Informational: No full-text supported languages found. 0 0
9937 Too many full-text columns or the full-text query is too complex to be executed. 0 0
9938 Cannot find the specified user or role '%.*ls'. 0 0
9939 Current user or role '%.*ls' does not have the required permission to set the owner. 0 0
9940 Error: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is terminated due to the preceding error. 0 0
9941 Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is being suspended by the system as the database is unavailable. System will resume the population whenever the database is available 0 0
9942 Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') was cancelled by user. 0 0
9943 Informational: Full-text %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documents processed: %d. Number of documents failed: %d. Number of documents that will be retried: %d. 0 0
9944 Informational: Full-text retry pass of %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of retry documents processed: %d. Number of documents failed: %d. 0 0
9945 Error: All Full-text populations in progress, for catalog '%ls' ('%d') in database '%ls' ('%d') were terminated due to error. Error: 0x%x. 0 0
9947 Warning: Identity of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog cannot be attached. 0 0
9948 Warning: Full-text catalog path '%ls' is invalid. It exceeds the length limit, or it is a relative path, or it is a hidden directory. The full-text catalog cannot be attached. 0 0
9949 Warning: All Full-text populations in progress for full-text catalog '%ls' ('%d') in database '%ls' ('%d') are paused. Reason code: %d. Error: %ls. If this message occurs frequently, consult Books Online for indexing performance tuning assistance. 0 0
9950 Informational: Full-text catalog health monitor reported a failure for catalog '%ls' ('%d') in database '%ls' ('%d'). Reason code: %d. Error: %ls. The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch. 0 0
9951 Warning: Database %.*ls cannot be modified during detach because database is in read-only, standby, or shutdown state. Full-text catalog is not dropped, and '@keepfulltextindexfile = false' is ignored. 0 0
9952 Informational: Full-text auto change tracking is turned off for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') due to fatal crawl error. 0 0
9953 The path '%.*ls' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive. 0 0
9954 SQL Server failed to communicate with filter daemon launch service (Windows error: %ls). Full-Text filter daemon process failed to start. Full-text search functionality will not be available. 0 0
9955 SQL Server failed to create named pipe '%ls' to communicate with the full-text filter daemon (Windows error: %d). Either a named pipe already exists for a filter daemon host process, the system is low on resources, or the security identification number (SID) lookup for the filter daemon account group failed. To resolve this error, terminate any running full-text filter daemon processes, and if necessary reconfigure the full-text daemon launcher service account. 0 0
9959 Cannot perform requested task because full-text memory manager is not initialized. 0 0
9960 View '%.*ls' is not an indexed view. Full-text index is not allowed to be created on it. 0 0
9961 Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified. 0 0
9962 Failed to move full-text catalog from '%ls' to '%ls'. OS error '%ls'. 0 0
9963 Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset. 0 0
9964 Failed to finish full-text operation. Filegroup '%.*ls' is empty, read-only, or not online. 0 0
9965 NULL or Invalid type of value specified for '%ls' parameter. 0 0
9966 Cannot use full-text search in master, tempdb, or model database. 0 0
9967 A default full-text catalog does not exist in database '%.*ls' or user does not have permission to perform this action. 0 0
9968 Warning: No appropriate filter was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Some columns of the row were not indexed. 0 0
9969 Warning: No appropriate wordbreaker was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Neutral wordbreaker was used for some columns of the row. 0 0
9970 Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline. 0 0
9971 Warning: No appropriate filter for embedded object was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'), full-text key value '%ls'. Some embedded objects in the row could not be indexed. 0 0
9972 Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE. 0 0
9973 Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documents processed: %d. Number of documents failed: %d. 0 0
9974 Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue when your start the same type of crawl again. 0 0
9975 Warning: Only paused full population can be resumed. The command is ignored. 0 0
9977 Warning: Last population complete time of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog is attached and it may need to be repopulated. 0 0
9978 Warning: During upgrade full-text index on table '%ls' is disabled because at least one of full-text key column, full-text columns, or type columns is a non-deterministic or imprecise nonpersisted computed column. 0 0
9979 Warning: During upgrade full-text catalog '%ls' in database '%ls' is set as offline because it failed to be created at path '%ls'. Please fix the full-text catalog path and rebuild the full-text catalog after upgrade. 0 0
9980 Variable parameters can not be passed to fulltext predicates: contains, freetext and functions: containstable, freetexttable applied to remote table. 0 0
9982 Cannot use full-text search in user instance. 0 0
9983 The value '%ls' for the full-text component '%ls' is longer than the maximum permitted (%d characters). Please reduce the length of the value. 0 0
9984 Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). 0 0
9998 The column '%.*ls' cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a full-text index, add fewer columns. 0 0
9999 The column '%.*ls' in the table '%.*ls' cannot be used for full-text search because it is a sparse column set. 0 0
20001 There is no nickname for article '%s' in publication '%s'. 0 0
20002 The filter '%s' already exists for article '%s' in publication '%s'. 0 0
20003 Could not generate nickname for '%s'. 0 0
20004 Publication '%s' has the following property: '%s'. SQL Server subscribers below version '%s' will ignore this setting. 0 0
20005 %ls: Cannot convert parameter %ls: Resulting colv would have too many entries. 0 0
20006 Cannot make the change because the article might be in a publication that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 to acknowledge that such a subscription will be reinitialized. 0 0
20007 The system tables for merge replication could not be dropped successfully. 0 0
20008 The system tables for merge replication could not be created successfully. 0 0
20009 The article '%s' could not be added to the publication '%s'. 0 0
20010 The Snapshot Agent corresponding to the publication '%s' could not be dropped. 0 0
20011 Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property. 0 0
20012 The subscription type '%s' is not allowed on publication '%s'. 0 0
20013 The publication property '%s' cannot be changed when there are subscriptions on it. 0 0
20014 Invalid @schema_option value. 0 0
20015 Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. 0 0
20016 Invalid @subscription_type value. Valid values are 'pull' or 'anonymous'. 0 0
20017 The subscription on the Subscriber does not exist. 0 0
20018 The @optional_command_line is too long. Use an agent definition file. 0 0
20019 Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database. 0 0
20020 The article resolver supplied is either invalid or nonexistent. 0 0
20021 The subscription could not be found. 0 0
20022 This article has now settings to disable uploads and compensate_for_errors=true. However, local and anonymous subscribers will behave as if compensate_for_errors=false. 0 0
20023 Invalid @subscriber_type value. Valid options are 'local', 'global', or 'anonymous'. 0 0
20024 The alt_snapshot_folder cannot be the same as the working directory. 0 0
20025 The publication name must be unique. The specified publication name '%s' has already been used. 0 0
20026 The publication '%s' does not exist. 0 0
20027 The article '%s' does not exist. 0 0
20028 The Distributor has not been installed correctly. Could not enable database for publishing. 0 0
20029 The Distributor has not been installed correctly. Could not disable database for publishing. 0 0
20030 The article '%s' already exists on another publication with a different column tracking option. 0 0
20031 Could not delete the row because it does not exist. 0 0
20032 '%s' is not defined as a Subscriber for '%s'. 0 0
20033 Invalid publication type. 0 0
20034 Publication '%s' does not support '%s' subscriptions. 0 0
20036 The Distributor has not been installed correctly. 0 0
20037 The article '%s' already exists in another publication with a different article resolver. 0 0
20038 The article filter could not be added to the article '%s' in the publication '%s'. 0 0
20039 The article filter could not be dropped from the article '%s' in the publication '%s'. 0 0
20040 Could not drop the article(s) from the publication '%s'. 0 0
20041 Transaction rolled back. Could not execute trigger. Retry your transaction. 0 0
20043 Could not change the article '%s' because the publication has already been activated. 0 0
20044 The priority property is invalid for local subscribers. 0 0
20045 You must supply an article name. 0 0
20046 The article does not exist. 0 0
20047 You are not authorized to perform this operation. 0 0
20048 To modify the priority of a subscription, run sp_changemergesubscription at the Publisher instead of using sp_changemergepullsubscription at subscriber. This is for backward compatibility only. 0 0
20049 The priority value should not be larger than 100.0. 0 0
20050 The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999. 0 0
20051 The Subscriber is not registered. 0 0
20052 The @metatype parameter value must be null, 1, 2, 5, or 6. 0 0
20053 An article with a different %s value already exists for object '%s'. 0 0
20054 Current database is not enabled for publishing. 0 0
20055 Table '%s' cannot be published for merge replication because it has a timestamp column. 0 0
20056 Table '%s' cannot be republished. 0 0
20057 The profile name '%s' already exists for the specified agent type. 0 0
20058 The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge) 0 0
20059 The @profile_type must be 0 (System) or 1 (Custom) 0 0
20060 Compatibility level cannot be smaller than 60. 0 0
20061 The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing. 0 0
20062 Updating columns with the rowguidcol property is not allowed. 0 0
20063 Table '%s' into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process can perform these operations. 0 0
20064 Cannot drop profile. Either it is not defined or it is defined as the default profile. 0 0
20065 Cannot drop profile because it is in use. 0 0
20066 Profile not defined. 0 0
20067 The parameter name '%s' already exists for the specified profile. 0 0
20068 The article cannot be created on table '%s' because it has more than %d columns. 0 0
20069 Cannot validate a merge article that uses looping join filters. 0 0
20070 Cannot update subscription row. 0 0
20072 Cannot update Subscriber information row. 0 0
20073 Articles can be added or changed only at the Publisher. 0 0
20074 Only a table object can be published as a "table" article for merge replication. 0 0
20075 The 'status' parameter value must be either 'active' or 'unsynced'. 0 0
20076 The @sync_mode parameter value must be 'native' or 'character'. 0 0
20077 Problem encountered generating replica nickname. 0 0
20078 The @property parameter value must be one of the following: 'sync_type', 'priority', 'description', 'subscriber_security_mode', 'subscriber_login', 'subscriber_password', 'publisher_security_mode', 'publisher_login', 'publisher_password', 'merge_job_login', or 'merge_job_password'. 0 0
20079 Invalid @subscription_type parameter value. Valid options are 'push', 'pull', or 'both'. 0 0
20081 Publication property '%s' cannot be NULL. 0 0
20084 Publication '%s' cannot be subscribed to by Subscriber database '%s'. 0 0
20086 Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column. 0 0
20087 You cannot push an anonymous subscription. 0 0
20088 Only assign priorities that are greater than or equal to 0 and less than 100. 0 0
20089 Could not get license information correctly. 0 0
20090 Could not get version information correctly. 0 0
20091 sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions. 0 0
20092 Table '%s' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publisher data modifications are disallowed until the upgrade completes and snapshot has successfully run. On subscriber data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher. 0 0
20093 Merge replication upgrade is not complete until the snapshot agent is run for the publisher and the merge agent run for all the subscribers. 0 0
20100 Cannot drop Subscriber '%s'. There are existing subscriptions. 0 0
20500 The updatable Subscriber stored procedure '%s' does not exist. 0 0
20501 Could not insert into sysarticleupdates using sp_articlecolumn. 0 0
20502 Invalid '%s' value. Valid values are 'read only', 'sync tran', 'queued tran', or 'failover'. 0 0
20503 Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions. 0 0
20504 Immediate Updating Subscriptions: The xml values inserted/updated by Subscriber will be replicated as NULL to publisher. 0 0
20505 Could not drop synchronous update stored procedure '%s' in '%s'. 0 0
20506 Source table '%s' not found in '%s'. 0 0
20507 Table '%s' not found in '%s'. 0 0
20508 Updatable subscriptions: The text, ntext, or image values inserted at the Subscriber will be NULL. 0 0
20509 Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber. 0 0
20510 Updateable Subscriptions: Cannot update identity columns. 0 0
20511 Updateable Subscriptions: Cannot update timestamp columns. 0 0
20512 Updateable Subscriptions: Rolling back transaction. 0 0
20513 Database '%s' does not contain any replication metadata for a row whose ROWGUIDCOL matches the value specified for the @rowguid parameter of sp_showrowreplicainfo. Verify that the value specified for @rowguid parameter is correct. 0 0
20514 A rowcount validation request has been submitted to heterogeneous publisher %s for article %s of publication %s. Validation results will be posted to distribution history. 0 0
20515 Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber. 0 0
20516 Updateable Subscriptions: Replicated data is not updatable. 0 0
20518 Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column. 0 0
20519 Updateable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. 0 0
20520 Updateable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber. 0 0
20521 sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles. 0 0
20522 sp_MSmark_proc_norepl: invalid object name '%s'. 0 0
20523 Could not validate the article '%s'. It is not activated. 0 0
20524 Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast). 0 0
20525 Table '%s' might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s). 0 0
20526 Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast). 0 0
20527 Table '%s' passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns. 0 0
20528 Log Reader Agent startup message. 0 0
20529 Starting agent. 0 0
20530 Run agent. 0 0
20531 Detect nonlogged agent shutdown. 0 0
20532 Replication agent schedule. 0 0
20533 Replication agents checkup 0 0
20534 Detects replication agents that are not logging history actively. 0 0
20535 Removes replication agent history from the distribution database. 0 0
20536 Replication: agent failure 0 0
20537 Replication: agent retry 0 0
20538 Replication: expired subscription dropped 0 0
20539 Replication Warning: %s (Threshold: %s) 0 0
20540 Replication: agent success 0 0
20541 Removes replicated transactions from the distribution database. 0 0
20542 Detects and removes expired subscriptions from published databases. 0 0
20543 @rowcount_only parameter must be the value 0,1, or 2. 0=7.0 compatible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in version 8.0. 0 0
20545 Default agent profile 0 0
20546 Verbose history agent profile. 0 0
20547 Agent profile for detailed history logging. 0 0
20548 Slow link agent profile. 0 0
20549 Agent profile for low bandwidth connections. 0 0
20550 Windows Synchronization Manager profile 0 0
20551 Profile used by the Windows Synchronization Manager. 0 0
20552 Could not clean up the distribution transaction tables. 0 0
20553 Could not clean up the distribution history tables. 0 0
20554 The replication agent has not logged a progress message in %ld minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active. 0 0
20555 6.x publication. 0 0
20556 Heartbeats detected for all running replication agents. 0 0
20557 Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'. 0 0
20558 Table '%s' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically. 0 0
20559 Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used. 0 0
20560 An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested. 0 0
20561 Generated expected rowcount value of %s for %s. 0 0
20565 Replication: Subscriber has failed data validation 0 0
20566 Replication: Subscriber has passed data validation 0 0
20567 Agent history clean up: %s 0 0
20568 Distribution clean up: %s 0 0
20569 Expired subscription clean up 0 0
20570 Reinitialize subscriptions having data validation failures 0 0
20571 Reinitializes all subscriptions that have data validation failures. 0 0
20572 Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure. 0 0
20573 Replication: Subscription reinitialized after validation failure 0 0
20574 Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation. 0 0
20575 Subscriber '%s' subscription to article '%s' in publication '%s' passed data validation. 0 0
20576 Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure. 0 0
20577 No No entries were found in msdb..sysreplicationalerts. 0 0
20578 Replication: agent custom shutdown 0 0
20579 Generated expected rowcount value of %s and expected checksum value of %s for %s. 0 0
20580 Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'. 0 0
20581 Cannot drop server '%s' because it is used as a Distributor in replication. 0 0
20582 Cannot drop server '%s' because it is used as a Publisher in replication. 0 0
20583 Cannot drop server '%s' because it is used as a Subscriber in replication. 0 0
20584 Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication. 0 0
20585 Validation Failure. Object '%s' does not exist. 0 0
20586 (default destination) 0 0
20587 Invalid '%s' value for stored procedure '%s'. 0 0
20588 The subscription is not initialized. Run the Distribution Agent first. 0 0
20589 Agent profile for replicated queued transaction reader. 0 0
20590 The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data transformations. 0 0
20591 Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows data transformations. 0 0
20592 'dts horizontal partitions' and 'no dts horizontal partitions' are not valid 'status' values because the publication does not allow data transformations. 0 0
20593 Cannot modify publication '%s'. The sync_method cannot be changed to 'native', or 'concurrent' because the publication is enabled for heterogeneous subscribers. 0 0
20594 A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions. 0 0
20595 Skipping error signaled. 0 0
20596 Only '%s' or members of db_owner can drop the anonymous agent. 0 0
20597 Dropped %d anonymous subscription(s). 0 0
20598 The row was not found at the Subscriber when applying the replicated command. 0 0
20599 Continue on data consistency errors. 0 0
20600 Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers. 0 0
20601 Invalid value specified for agent parameter 'SkipErrors'. 0 0
20602 The value specified for agent parameter 'SkipErrors' is too long. 0 0
20603 The agent profile cannot be used by heterogeneous Subscribers. 0 0
20604 You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'. 0 0
20605 Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot. 0 0
20606 Reinitialized subscription(s). 0 0
20607 Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing snapshot. 0 0
20608 Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active subscriptions. 0 0
20609 Cannot attach subscription file '%s'. Make sure that it is a valid subscription copy file. 0 0
20610 Cannot run '%s' when the Log Reader Agent is replicating the database. 0 0
20611 Cannot add the article. Publications that allow transformable subscriptions with Data Transformation Services (DTS) can only include tables and indexed views that are published as tables. 0 0
20612 Checksum validation is not supported because the publication allows DTS. Use row count only validation. 0 0
20613 Validation is not supported for articles that are set up for DTS horizontal partitions. 0 0
20614 Validation is not supported for heterogeneous Subscribers. 0 0
20615 Unable to add a heterogeneous subscription to the publication. The publication is not enabled for heterogeneous subscriptions. 0 0
20616 High Volume Server-to-Server Profile 0 0
20617 Merge agent profile optimized for the high volume server-to-server synchronization scenario. 0 0
20618 You must have CREATE DATABASE permission to attach a subscription database. 0 0
20619 Server user '%s' is not a valid user in database '%s'. Add the user account or 'guest' user account into the database first. 0 0
20620 The security mode specified requires the server '%s' to be registered as a linked server. Use sp_addlinkedserver to add the server. 0 0
20621 Cannot copy a subscription database to an existing database. 0 0
20622 Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode. 0 0
20623 You cannot validate article '%s' unless you have 'SELECT ALL' permission on table '%s'. 0 0
20624 The value specified for the @login parameter is not valid. User '%s' is not a user in database '%s'. Add the user account to the database before attempting to execute the stored procedures sp_grant_publication_access or sp_revoke_publication_access. 0 0
20625 Cannot create the merge replication publication access list (PAL) database role for publication '%s'. This role is used by replication to control access to the publication. Verify that you have sufficient permissions to create roles in the publication database. 0 0
20626 Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter. 0 0
20627 Partition id has to be greater than or equal to 0. 0 0
20628 Failed to generate dynamic snapshot. 0 0
20629 Failed to get partition id information. 0 0
20630 Cannot create partitioned snapshot job. A job already exists for publication '%ls' that uses the values you specified for the @suser_sname and/or @host_name parameters of sp_adddynamicsnapshot_job. If the job that already exists is not working correctly, use sp_dropdynamicsnapshot_job to drop it and create a new one using sp_adddynamicsnapshot_job. 0 0
20631 Cannot find a location in which to generate a partitioned snapshot. Verify that the there is a valid snapshot folder specified for the publication. This can be the default folder associated with the Distributor or an alternate folder associated with the publication. 0 0
20632 Failed to create a dynamic snapshot job to generate the dynamic snapshot. 0 0
20633 Cannot start the partitioned snapshot job. Verify that SQL Server Agent is running on the Distributor. 0 0
20634 The root publication information could not be found on the republisher. 0 0
20635 A push subscription to '%ls' was found. Cannot add a pull subscription agent for a push subscription. 0 0
20636 Cannot generate merge replication stored procedures for article '%s'. Stored procedures are generated on the Publisher when the Snapshot Agent runs or when a data definition language action is performed; they are generated on the Subscriber when the snapshot is applied by the Merge Agent. Verify that the agents have the appropriate permissions to create procedures, and that the procedures do not already exist. 0 0
20637 The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign key relationships between published tables. Article '%s' references one or more articles that will be created after it is created. Change the processing_order property using sp_changemergearticle. 0 0
20638 Merge table articles do not support different values for the @source_object and @destination_object parameters of sp_addmergearticle. Either do not specify a value for @destination_object, or specify the same value for both parameters. 0 0
20639 Cannot enable the publication to support non-SQL Server subscriptions because the publication is enabled for updatable subscriptions. To support non-SQL Server subscriptions, drop the existing publication and create a new one with the properties allow_sync_tran and allow_queued_tran set to 'false'. 0 0
20640 Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication. 0 0
20641 Failed to check if the subset_filterclause has a dynamic function in it. 0 0
20642 Cannot add article '%s' with one or more dynamic functions in the subset_filterclause '%s' to publication '%s' because the publication could have active subscriptions. Set @force_reinit_subscription to 1 to add the article and reinitialize all active subscriptions. 0 0
20643 Cannot change the value of validate_subscriber_info for publication '%s' because the publication has active subscriptions. Set @force_reinit_subscription to 1 to change the value and reinitialize all active subscriptions. 0 0
20644 Invalid value "%s" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none". 0 0
20645 The property "%s" cannot be modified for publications that are enabled for non-SQL Server subscriptions. 0 0
20646 Peer-to-peer publications do not support %s. Change the value for parameter '%s'. 0 0
20647 Cannot modify property '%s'. The publication is used in a peer-to-peer topology, which does not allow this property to be modified after the publication is created. 0 0
20648 An article already exists for table "%s" with a different value for the @delete_tracking property. The value must be the same for all publications in which the table is published. Use the stored procedures sp_helpmergearticle and sp_changemergearticle to view and modify the property in the other article(s). 0 0
20649 Publications enabled for heterogeneous subscriptions do not support %s. Please change the '%s' parameter value. 0 0
20650 Cannot enable data definition language (DDL) replication (a value of "true" for the @replicate_ddl parameter) for publication "%s". This is because the compatibility level of the publication is lower than 90RTM. For new publications, in the stored procedure sp_addmergepublication, set the @publication_compatibility_level parameter to 90RTM; for existing publications, use sp_changemergepublication. 0 0
20651 Publication "%s" "%s". Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower, disable the feature and then call the stored procedure sp_changemergepublication to lower the compatibility level. 0 0
20652 Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again. 0 0
20653 Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL. 0 0
20654 Dynamic snapshots are only valid for merge publications. 0 0
20655 The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history table in the distribution database. Ensure that a standard snapshot is up-to-date and available. 0 0
20656 The @subset_filterclause parameter cannot reference a computed column. 0 0
20657 The value for the @pub_identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity column "%s" is %s. 0 0
20658 The value for the @identity_range parameter must be a multiple of the increment for the identity column. The increment for table "%s" and identity column "%s" is %s. 0 0
20659 The value of IDENT_CURRENT ("%s") is greater than the value in the max_used column of the MSmerge_identity_range system table. 0 0
20660 The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range. 0 0
20661 The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range. 0 0
20662 The republisher does not have a range of identity values from the root Publisher '%s' that it can assign to its Subscribers. Ensure that the republisher has a server subscription to the publication at the root Publisher, and then run the Merge Agent to synchronize with the root Publisher. 0 0
20663 The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @identityrangemanagementoption property is "auto". 0 0
20664 The Publisher cannot be assigned a new range of identity values, because the values for the identity column's data type have all been used. Change the data type in the identity column. 0 0
20665 The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run the Merge Agent to synchronize with the root Publisher. 0 0
20666 Cannot refresh the identity range and/or the check constraint on the Publisher. Ensure the following: that the value in the identity column has not reached the maximum for the data type in the identity column; and that the user who made the last insert has the privileges to drop and re-create the check constraint. 0 0
20667 Cannot allocate an identity range for article "%s". The article is not enabled for automatic identity range management. 0 0
20668 Not enough range available to allocate a new range for a subscriber. 0 0
20669 Object referenced by the given @article or @artid '%s' could not be found. 0 0
20670 Cannot add, drop, or alter the identity range check constraint for table %s. This constraint is used by replication for automatic identity range management. This error typically occurs if the user who made the last insert in the table does not have permission to make schema changes on the table. If this error occurs at the Publisher, run sp_adjustpublisheridentityrange; if it occurs at the Subscriber, run the Merge Agent. 0 0
20671 Cannot find the identity range allocation entry for the Subscriber in the MSmerge_identity_range table. Reinitialize the subscription. 0 0
20672 A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering. 0 0
20673 A value for the parameter @host_name was specified, but no articles in the publication use SUSER_SNAME() for parameterized filtering. 0 0
20674 The publication does not use dynamic filtering. 0 0
20675 The identity range values cannot be NULL. 0 0
20676 Cannot refresh the Publisher identity range for article "%s". Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity range. 0 0
20677 Cannot add article "%s" with automatic identity range management. The article is already published in a transactional publication with automatic identity range management. 0 0
20678 Could not find the regular snapshot job for the specified publication '%s'. 0 0
20679 Cannot execute the stored procedure sp_adjustpublisheridentityrange on the current database because the database is a republisher or a Subscriber. To adjust the identity range at a republisher or a Subscriber, synchronize with the root Publisher. 0 0
20680 Failed to get metadata for a batch of rows. 0 0
20681 Cannot specify a value of 1, 2, or 3 for the parameter @partition_options because publication "%s" has a compatibility level lower than 90RTM. Use the stored procedure sp_changemergepublication to set publication_compatibility_level to 90RTM. 0 0
20682 Failed deletion of rows in batched delete attempt on table %s. 0 0
20683 Failed batched deletion on download only article %s. 0 0
20684 Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent. 0 0
20685 Cannot drop the filter '%s' . The filter specified for the @filtername parameter cannot be found. 0 0
20686 Parameter '%s' cannot be NULL or empty when this procedure is run from a '%s' database. 0 0
20687 Parameter '%s' must be NULL when this procedure is not being run from a '%s' database. 0 0
20688 The tracer token ID (%d) could not be found for Publisher %s, database %s, publication %s. Use the stored procedure sp_helptracertokens to retrieve a list of valid tracer token IDs. 0 0
20689 The check for a Publisher needing a new identity range allocation failed on table %s. This check occurs every time the Merge Agent and Snapshot Agent run. Rerun the Merge Agent or Snapshot Agent. 0 0
20690 Cannot set up the Publisher identity range for table %s. Verify that appropriate ranges were specified when the article was created, and then rerun the Snapshot Agent. 0 0
20691 Merge replication upgrade of SQL Server 2005 metadata and triggers on the subscriber failed. 0 0
20692 One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_tombstone; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication. 0 0
20693 One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_contents; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication. 0 0
20694 One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch updates can improve the performance of merge replication. 0 0
20695 Only %ld out of %ld rows were updated in the batched update procedure for table %s; other rows could not be updated because they have been deleted. No action is required, but if this condition occurs frequently, determine if update-delete conflicts can be avoided. Batch updates can be helpful for performance. 0 0
20696 The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication. 0 0
20697 Cannot drop article %s from publication %s. In this publication, this is the only article that uses a parameterized filter. Dropping this article changes the publication to a static publication, which requires reinitialization of all Subscribers. To drop the article and reinitialize all active subscriptions, specify a value of 1 for the @force_reinit_subscription parameter of sp_dropmergepublication. 0 0
20698 A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering. 0 0
20699 A value for the parameter @suser_sname was not specified while publication uses SUSER_SNAME() for dynamic filtering. 0 0
20701 The dynamic snapshot job schedule could not be changed on the distributor. 0 0
20702 The dynamic snapshot job schedule could not be changed due to one or more errors. 0 0
20703 One or more rows inserted in table '%s' were out of partition while the table was published with 'partition_options' set to %d. 0 0
20704 The datatype of the identity column of table '%s' is tinyint. tinyint does not have enough numbers available for merge auto identity range. Change the identity column to have a larger datatype and add the merge article with merge auto identity range management. 0 0
20705 Cannot set @conflict_logging to 'both' because publication '%s' has a compatibility level lower than 90. Set @publication_compatibility_level to '90RTM' when creating the publication or use sp_changemergepublication to set publication_compatibility_level to '90RTM'. 0 0
20706 The max or min allowed identity numbers for the identity column could not be found for the given article. 0 0
20707 Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors. 0 0
20708 An article is not allowed to be part of a logical record when it has a custom business logic resolver. 0 0
20709 The merge process could not clean up the conflict table "%s" for publication "%s". 0 0
20710 Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for publisher '%s', publisher_db '%s', publication '%s' and article '%s'. 0 0
20711 The dynamic filters property for publication '%s' has been incorrectly set. Use sp_changemergepublication to reset the value to true if the publication uses parameterized filters and false if it does not. 0 0
20712 Unable to acquire the replication merge administrative application lock for database '%s'. This could be due an active snapshot running while the schema change (DDL) or the administrative proc change was attempted. 0 0
20713 Replication merge admin stored procedure '%s' failed for publication '%s'. This could be due an active snapshot running while the admin proc was called. 0 0
20714 Failed to prepare article '%s' in publication '%s' for merge replication. 0 0
20715 Failed to create merge replication triggers for object '%s'. 0 0
20716 Failed to create publication views for merge replication publication '%s'. 0 0
20717 sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings to change the settings or sp_dropmergelogsettings to remove the settings. 0 0
20718 Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. Use sp_addmergelogsettings to add the settings. 0 0
20719 sp_changemergelogsettings failed to update log settings. Check the parameter values. 0 0
20720 Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. 0 0
20721 sp_dropmergelogsettings failed to remove log settings. 0 0
20722 '%s' failed. The value for parameter '%s' is not valid. Valid values are @support_options [0 - 5], @log_severity [1 - 4], @log_file_size [2,000,000 - 999,000,000], @no_of_log_files [2 - 500], @upload_interval [0 - 40320], @delete_after_upload [0 - 1]. 0 0
20723 Computed column "%s" can only be added to publication after its depending object "%s" is added. 0 0
20724 Could not find a valid command line for the dynamic snapshot job with job_id '%s' for publication '%s'. 0 0
20725 Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id '%s' in publication '%s'. 0 0
20726 Failed to change the dynamic snapshot location in one or more dynamic snapshot jobs for the given publication. 0 0
20727 An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'. 0 0
20728 Failed to restore the max allocated identity value for article '%s' in publication '%s'. 0 0
20729 The max identity value allocation for article '%s' in publication '%s' could not be found on the distributor. 0 0
20730 Setting @upload_first to 'true' requires the publication to be at publication_compatibility_level of '80RTM' or higher. Use sp_changemergepublication to set publication_compatibility_level to '80RTM' or higher if you want to use this feature. 0 0
20731 This edition of SQL Server does not support publications. Dropping existing publications. 0 0
20732 Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead. 0 0
20733 One or more rows updated in table '%s' were out of partition while the table was published with 'partition_options' set to %d. 0 0
20734 One or more rows deleted in table '%s' were out of partition while the table was published with 'partition_options' set to %d. 0 0
20735 Cannot add article '%s' to publication '%s'. The publication already contains 256 articles, which is the maximum. 0 0
20736 Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead. 0 0
20737 Warning: To allow replication of FILESTREAM data to perform optimally and reduce memory utilization, the 'stream_blob_columns' property has been set to 'true'. To force FILESTREAM table articles to not use blob streaming, use sp_changemergearticle to set 'stream_blob_columns' to 'false'. 0 0
20738 Cannot add article '%s' with sparse column or column set to merge publication since merge replication does not support sparse columns and column set. 0 0
20739 The DDL operation is not supported for article '%s'. If the column in the DDL operation is enabled for FILESTREAM or is of type hierarchyid, geometry, geography, datetime2, date, time, or datetimeoffset, the publication compatibility level must be at least 100RTM. For DDL operations that involve FILESTREAM and hierarchyid columns, the snapshot mode must be native. Character mode, which is required for SQL Server Compact Subscribers, is not supported. 0 0
20800 Cannot reinitialize the article '%s' in subscription '%s:%s' to publication '%s'. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead. 0 0
20801 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. 0 0
20802 Cannot publish objects from the replication administrative user schema [%s]. This schema owns all replication procedures and metadata tables, but it cannot own published objects. Use a different schema for objects that will be published. 0 0
20803 Peer-To-Peer topologies require identical articles in publications at all nodes prior to synchronizing. Articles in publication [%s].[%s].[%s] do not match articles in [%s].[%s].[%s]. 0 0
20804 Articles can only be included in a single peer-to-peer publication. [%s].[%s] is already included in the peer-to-peer publication '%s'. 0 0
20805 Peer-to-peer topologies require identical publication names on each Publisher. You are attempting to republish object [%s].[%s] that is already being published in the peer-to-peer publication [%s].[%s].[%s]. 0 0
20806 An error occurred while executing a peer-to-peer forwarding command. Contact Customer Support Services. 0 0
20807 No No peers were found for %s:%s:%s. If you encounter this error when executing the stored procedure sp_requestpeerresponse, verify that subscriptions have been created before attempting to call the procedure again. If you encounter this error in other circumstances, contact Customer Support Services. 0 0
20808 The peer-to-peer publication '%s' does not exist. Execute sp_helppublication to view a list of publication names. 0 0
20809 Peer-To-Peer topologies require identical publication names on each publisher. The distribution agent for publication [%s].[%s].[%s] is attempting to synchronize articles that exist in publication [%s].[%s].[%s]. 0 0
20810 The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type article. 0 0
20811 Replication monitoring refresher for %s. 0 0
20812 The specified source object must be a synonym if it is published as a 'synonym schema only' type article. 0 0
20813 Only members of the sysadmin fixed server role can modify a %s that does not have a job with a proxy account defined. 0 0
20814 Distribution Profile for OLEDB streaming 0 0
20815 Distribution agent profile enabled for the processing LOB data using OLEDB streaming. 0 0
20816 Peer-To-Peer publishers are only supported on Enterprise class editions of SQL Server. This instance is %s. 0 0
20817 An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'. 0 0
1001 Line %d: Length or precision specification %d is invalid. 0 0
1002 Line %d: Specified scale %d is invalid. 0 0
1003 Line %d: %ls clause allowed only for %ls. 0 0
1004 Invalid column prefix '%.*ls': No table name specified 0 0
1005 Line %d: Invalid procedure number (%d). Must be between 1 and 32767. 0 0
1006 CREATE TRIGGER contains no statements. 0 0
1007 The %S_MSG '%.*ls' is out of the range for numeric representation (maximum precision 38). 0 0
1008 The SELECT item identified by the ORDER BY number %d contains a variable as part of the expression identifying a column position. Variables are only allowed when ordering by an expression referencing a column name. 0 0
1009 The keyword DEFAULT is not allowed in DBCC commands. 0 0
1010 Invalid escape character '%.*ls'. 0 0
1011 The correlation name '%.*ls' is specified multiple times in a FROM clause. 0 0
1012 The correlation name '%.*ls' has the same exposed name as table '%.*ls'. 0 0
1013 The objects "%.*ls" and "%.*ls" in the FROM clause have the same exposed names. Use correlation names to distinguish them. 0 0
1014 TOP clause contains an invalid value. 0 0
1015 An aggregate cannot appear in an ON clause unless it is in a subquery contained in a HAVING clause or select list, and the column being aggregated is an outer reference. 0 0
1016 Outer join operators cannot be specified in a query containing joined tables. 0 0
1018 Incorrect syntax near '%.*ls'. If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required. See SQL Server Books Online for proper syntax. 0 0
1019 Invalid column list after object name in GRANT/REVOKE statement. 0 0
1020 Sub-entity lists (such as column or security expressions) cannot be specified for entity-level permissions. 0 0
1021 FIPS Warning: Line %d has the non-ANSI statement '%ls'. 0 0
1022 FIPS Warning: Line %d has the non-ANSI clause '%ls'. 0 0
1023 Invalid parameter %d specified for %ls. 0 0
1024 FIPS Warning: Line %d has the non-ANSI function '%ls'. 0 0
1025 FIPS Warning: The length of identifier '%.*ls' exceeds 18. 0 0
1026 GOTO cannot be used to jump into a TRY or CATCH scope. 0 0
1028 The CUBE, ROLLUP, and GROUPING SETS constructs are not allowed in a GROUP BY ALL clause. 0 0
1029 Browse mode is invalid for subqueries and derived tables. 0 0
1030 Only constants are allowed here. Time literal is not permitted because it refers to the current date. 0 0
1031 Percent values must be between 0 and 100. 0 0
1032 Cannot use the column prefix '%.*ls'. This must match the object in the UPDATE clause '%.*ls'. 0 0
1033 The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified. 0 0
1034 Syntax error: Duplicate specification of the action "%.*s" in the trigger declaration. 0 0
1035 Incorrect syntax near '%.*ls', expected '%.*ls'. 0 0
1036 File option %hs is required in this CREATE/ALTER DATABASE statement. 0 0
1037 The CASCADE, WITH GRANT or AS options cannot be specified with statement permissions. 0 0
1038 An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name. 0 0
1039 Option '%.*ls' is specified more than once. 0 0
1041 Option %.*ls is not allowed for a LOG file. 0 0
1042 Conflicting %ls optimizer hints specified. 0 0
1043 '%hs' is not yet implemented. 0 0
1044 Cannot use an existing function name to specify a stored procedure name. 0 0
1045 Aggregates are not allowed in this context. Only scalar expressions are allowed. 0 0
1046 Subqueries are not allowed in this context. Only scalar expressions are allowed. 0 0
1047 Conflicting locking hints specified. 0 0
1048 Conflicting cursor options %ls and %ls. 0 0
1049 Mixing old and new syntax to specify cursor options is not allowed. 0 0
1050 This syntax is only allowed for parameterized queries. 0 0
1051 Cursor parameters in a stored procedure must be declared with OUTPUT and VARYING options, and they must be specified in the order CURSOR VARYING OUTPUT. 0 0
1052 Conflicting %ls options "%ls" and "%ls". 0 0
1053 For DROP STATISTICS, you must provide both the object (table or view) name and the statistics name, in the form "objectname.statisticsname". 0 0
1054 Syntax '%ls' is not allowed in schema-bound objects. 0 0
1055 '%.*ls' is an invalid name because it contains a NULL character or an invalid unicode character. 0 0
1056 The number of elements in the select list exceeds the maximum allowed number of %d elements. 0 0
1057 The IDENTITY function cannot be used with a SELECT INTO statement containing a UNION, INTERSECT or EXCEPT operator. 0 0
1058 Cannot specify both READ_ONLY and FOR READ ONLY on a cursor declaration. 0 0
1059 Cannot set or reset the 'parseonly' option within a procedure or function. 0 0
1060 The number of rows in the TOP clause must be an integer. 0 0
1061 The text/ntext/image constants are not yet implemented. 0 0
1062 The TOP N WITH TIES clause is not allowed without a corresponding ORDER BY clause. 0 0
1063 A filegroup cannot be added using ALTER DATABASE ADD FILE. Use ALTER DATABASE ADD FILEGROUP. 0 0
1064 A filegroup cannot be used with log files. 0 0
1065 The NOLOCK and READUNCOMMITTED lock hints are not allowed for target tables of INSERT, UPDATE, DELETE or MERGE statements. 0 0
1066 Warning. Line %d: The option '%ls' is obsolete and has no effect. 0 0
1067 The SET SHOWPLAN statements must be the only statements in the batch. 0 0
1068 Only one list of index hints per table is allowed. 0 0
1069 Index hints are only allowed in a FROM or OPTION clause. 0 0
1070 CREATE INDEX option '%.*ls' is no longer supported. 0 0
1071 Cannot specify a JOIN algorithm with a remote JOIN. 0 0
1072 A REMOTE hint can only be specified with an INNER JOIN clause. 0 0
1073 '%.*ls' is not a recognized cursor option for cursor %.*ls. 0 0
1074 Creation of temporary functions is not allowed. 0 0
1075 RETURN statements in scalar valued functions must include an argument. 0 0
1076 Function '%s' requires at least %d argument(s). 0 0
1077 INSERT into an identity column not allowed on table variables. 0 0
1078 '%.*ls %.*ls' is not a recognized option. 0 0
1079 A variable cannot be used to specify a search condition in a fulltext predicate when accessed through a cursor. 0 0
1080 The integer value %.*ls is out of range. 0 0
1081 %s does not allow specifying the database name as a prefix to the assembly name. 0 0
1082 %.*ls does not support synchronous trigger registration. 0 0
1083 OWNER is not a valid option for EXECUTE AS in the context of server and database level triggers. 0 0
1084 '%.*ls' is an invalid event type. 0 0
1085 '%.*ls' event type does not support event notifications. 0 0
1086 The FOR XML clause is invalid in views, inline functions, derived tables, and subqueries when they contain a set operator. To work around, wrap the SELECT containing a set operator using derived table syntax and apply FOR XML on top of it. 0 0
1087 Must declare the table variable "%.*ls". 0 0
1088 Cannot find the object "%.*ls" because it does not exist or you do not have permissions. 0 0
1089 The SET FMTONLY OFF statement must be the last statement in the batch. 0 0
1090 Invalid default for parameter %d. 0 0
1091 The option "%ls" is not valid for this function. 0 0
1092 In this context %d statistics name(s) cannot be specified for option '%ls'. 0 0
1093 %.*ls is not a valid broker name. 0 0
1094 Cannot specify a schema name as a prefix to the trigger name for database and server level triggers. 0 0
1095 %.*ls has already been specified as an event type. 0 0
1096 Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported. 0 0
1097 Cannot use If UPDATE within this CREATE TRIGGER statement. 0 0
1098 The specified event type(s) is/are not valid on the specified target object. 0 0
1099 The ON clause is not valid for this statement. 0 0
1101 Could not allocate a new page for database '%.*ls' because of insufficient disk space in filegroup '%.*ls'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 0 0
1105 Could not allocate space for object '%.*ls'%.*ls in database '%.*ls' because the '%.*ls' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 0 0
1119 Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to. 0 0
1121 Space allocator cannot allocate page in database %d. 0 0
1122 Table error: Page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned. 0 0
1123 Table error: Page %S_PGID. Unexpected page type %d. 0 0
1124 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid. 0 0
1125 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x. 0 0
1126 Table error: Page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row. 0 0
1127 Table error: Page %S_PGID. Test (%hs) failed. Values are %ld and %ld. 0 0
1128 Table error: Page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld. 0 0
1129 Could not cleanup deferred deallocations from filegroup '%.*ls'. 0 0
1130 Error while allocating extent for a worktable. Extent %S_PGID in TEMPDB may have been lost. 0 0
1131 Failed to truncate AppendOnlyStorageUnit 0x%p. Will retry next time. This is an informational message only. No user action is required. 0 0
1202 The database-principal '%.*ls' does not exist or user is not a member. 0 0
1203 Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator. 0 0
1204 The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. 0 0
1205 Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction. 0 0
1206 The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction. 0 0
1207 Can't allocate %u locks on startup, reverting to %u and turning on dynamic lock allocation. Maximum allowed memory usage at startup is %I64u KB. 0 0
1208 Could not allocate initial %u lock blocks during startup. Can not start the server. 0 0
1209 Could not allocate initial %u lock owner blocks during startup. Can not start the server. 0 0
1210 Unable to allocate lock owner block during lock migration. Server halted. 0 0
1212 Lock not logged: %-30ls Mode: %s 0 0
1213 Error spawning Lock Monitor thread: %ls 0 0
1214 Internal Error. There are too many parallel transactions. 0 0
1220 No No more lock classes available from transaction. 0 0
1221 The Database Engine is attempting to release a group of locks that are not currently held by the transaction. Retry the transaction. If the problem persists, contact your support provider. 0 0
1222 Lock request time out period exceeded. 0 0
1223 Cannot release the application lock (Database Principal: '%.*ls', Resource: '%.*ls') because it is not currently held. 0 0
1224 An invalid application lock resource was passed to %ls. 0 0
1225 An invalid application lock mode was passed to %ls. 0 0
1226 An invalid application lock owner was passed to %ls. 0 0
1227 An invalid application lock time-out was passed to %ls. 0 0
1228 An invalid parameter "%ls" was passed to the application lock function or procedure. 0 0
1230 An invalid database principal was passed to %ls. 0 0
1401 Startup of the database-mirroring master thread routine failed for the following reason: %ls. Correct the cause of this error, and restart the SQL Server service. 0 0
1402 Witness did not find an entry for database mirroring GUID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. A configuration mismatch exists. Retry the command, or reset the witness from one of the database mirroring partners. 0 0
1403 The witness for the mirroring session received error response %d (state %d) from server instance %.*ls for database %.*ls. For more information about the error, refer to the error log on this server instance and the partner server instance. 0 0
1404 The command failed because the database mirror is busy. Reissue the command later. 0 0
1405 The database "%.*ls" is already enabled for database mirroring. 0 0
1406 Unable to force service safely. Remove database mirroring and recover database "%.*ls" to gain access. 0 0
1407 The remote copy of database "%.*ls" is not related to the local copy of the database. 0 0
1408 The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring. 0 0
1409 Database mirroring cannot be enabled for the remote copy of database "%.*ls". Restore database logs to the remote copy. 0 0
1410 The remote copy of database "%.*ls" is already enabled for database mirroring. 0 0
1411 The remote copy of database "%.*ls" has not had enough log backups applied to roll forward all of its files to a common point in time. 0 0
1412 The remote copy of database "%.*ls" has not been rolled forward to a point in time that is encompassed in the local copy of the database log. 0 0
1413 Communications to the remote server instance '%.*ls' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started. 0 0
1414 The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed. 0 0
1415 The database mirroring operation for database "%.*ls" failed. The requested operation could not be performed. 0 0
1416 Database "%.*ls" is not configured for database mirroring. 0 0
1417 Database mirroring has been disabled by the administrator for database "%.*ls". 0 0
1418 The server network address "%.*ls" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. 0 0
1419 The remote copy of database "%.*ls" cannot be opened. Check the database name and ensure that it is in the restoring state, and then reissue the command. 0 0
1420 Database mirroring was unable to obtain the network hostname. Operating system error %ls encountered. Verify the network configuration. 0 0
1421 Communications to the remote server instance '%.*ls' failed to complete before its timeout. The ALTER DATABASE command may have not completed. Retry the command. 0 0
1422 The mirror server instance is not caught up to the recent changes to database "%.*ls". Unable to fail over. 0 0
1423 The property name is not supported. 0 0
1424 The remote server instance has a more recent value for the property '%.*ls'. Property value not changed. 0 0
1425 The property value is invalid for '%.*ls'. Property value not changed. 0 0
1426 To issue ALTER DATABASE SET WITNESS, all three server instances must be interconnected, and the mirror database must be caught up. When these conditions are met, reissue the command. 0 0
1427 The server instance '%.*ls' could not act as the witness. The ALTER DATABASE SET WITNESS command failed. 0 0
1428 The request is refused because the responding server instance is not in a state to service the request. 0 0
1429 The witness server instance name must be distinct from both of the server instances that manage the database. The ALTER DATABASE SET WITNESS command failed. 0 0
1430 Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery. 0 0
1431 Neither the partner nor the witness server instance for database "%.*ls" is available. Reissue the command when at least one of the instances becomes available. 0 0
1432 Database mirroring is attempting to repair physical page %S_PGID in database "%.*ls" by requesting a copy from the partner. 0 0
1433 All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness associated with the database. Verify the status and when necessary repeat the command. 0 0
1434 Invalid or unexpected database mirroring %ls message of type %d was received from server %ls, database %.*ls. 0 0
1435 %ls received unexpected database mirroring error response: status %u, severity %u, state %u, string %.*ls. 0 0
1436 The Service Broker ID for the remote copy of database "%.*ls" does not match the ID on the principal server. 0 0
1437 Could not post message '%ls' from server instance '%ls' because there is insufficient memory. Reduce non-essential memory load or increase system memory. 0 0
1438 The server instance %ls rejected configure request; read its error log file for more information. The reason %u, and state %u, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry. 0 0
1439 There is currently no witness associated with database "%.*ls". 0 0
1440 Database mirroring is active with database '%.*ls' as the principal copy. This is an informational message only. No user action is required. 0 0
1441 Database mirroring is active with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required. 0 0
1442 Database mirroring is inactive for database '%.*ls'. This is an informational message only. No user action is required. 0 0
1443 Database mirroring has been terminated for database '%.*ls'. This is an informational message only. No user action is required. 0 0
1444 Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required. 0 0
1445 Bypassing recovery for database '%ls' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change. 0 0
1446 The "%.*ls" server instance is already acting as the witness. 0 0
1447 ALTER DATABASE "%.*ls" command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command. 0 0
1448 The remote copy of database "%.*ls" does not exist. Check the database name and reissue the command. 0 0
1449 ALTER DATABASE command failed due to an invalid server connection string. 0 0
1450 The ALTER DATABASE command failed because the worker thread cannot be created. 0 0
1451 Database mirroring information was not found in the system table. 0 0
1452 The partner server instance name must be distinct from the server instance that manages the database. The ALTER DATABASE SET PARTNER command failed. 0 0
1453 '%.*ls', the remote mirroring partner for database '%.*ls', encountered error %d, status %d, severity %d. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. 0 0
1454 Database mirroring will be suspended. Server instance '%.*ls' encountered error %d, state %d, severity %d when it was acting as a mirroring partner for database '%.*ls'. The database mirroring partners might try to recover automatically from the error and resume the mirroring session. For more information, view the error log for additional error messages. 0 0
1455 The database mirroring service cannot be forced for database "%.*ls" because the database is not in the correct state to become the principal database. 0 0
1456 The ALTER DATABASE command could not be sent to the remote server instance '%.*ls'. The database mirroring configuration was not changed. Verify that the server is connected, and try again. 0 0
1457 Synchronization of the mirror database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The ALTER DATABASE command failed. Ensure that the principal database, if available, is back up and online, and then reconnect the mirror server instance and allow the mirror database to finish synchronizing. 0 0
1458 The principal copy of the '%.*ls' database encountered error %d, status %d, severity %d while sending page %S_PGID to the mirror. Database mirroring has been suspended. Try to resolve the error condition, and resume mirroring. 0 0
1459 An error occurred while accessing the database mirroring metadata. Drop mirroring (ALTER DATABASE database_name SET PARTNER OFF) and reconfigure it. 0 0
1460 The database "%.*ls" is already configured for database mirroring on the remote server. Drop database mirroring on the remote server to establish a new partner. 0 0
1461 Database mirroring successfully repaired physical page %S_PGID in database "%.*ls" by obtaining a copy from the partner. 0 0
1462 Database mirroring is disabled due to a failed redo operation. Unable to resume. 0 0
1463 Database mirroring is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions. 0 0
1464 Database mirroring cannot be enabled for the remote copy of database "%.*ls" because the database is not in a recovering state. The remote database must be restored using WITH NORECOVERY. 0 0
1465 Database mirroring cannot be enabled because the "%.*ls" database is not in full recovery mode on both partners. 0 0
1466 Database mirroring cannot be enabled because the "%.*ls" database is read-only on one of the partners. 0 0
1467 Database mirroring cannot be enabled because the "%.*ls" database is in emergency or suspect mode on one of the partners. 0 0
1468 The operation cannot be performed on database "%.*ls" because it is involved in a database mirroring session. 0 0
1469 Database mirroring cannot be enabled because the "%.*ls" database is an auto-close database on one of the partners. 0 0
1470 The alter database for this partner config values may only be initiated on the current principal server for database "%.*ls". 0 0
1471 The database mirroring connection terminated. Out of memory sending message for database "%.*ls". 0 0
1472 The database mirroring connection terminated. Communications error sending message for database "%.*ls". 0 0
1473 This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed. 0 0
1474 Database mirroring connection error %d '%.*ls' for '%.*ls'. 0 0
1475 Database mirroring cannot be enabled because the "%.*ls" database may have bulk logged changes that have not been backed up. The last log backup on the principal must be restored on the mirror. 0 0
1476 Database mirroring timeout value %d exceeds the maximum value 32767. 0 0
1477 The database mirroring safety level must be FULL to manually failover database "%.*ls". Set safety level to FULL and retry. 0 0
1478 The mirror database, "%.*ls", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database. 0 0
1479 The mirroring connection to "%.*ls" has timed out for database "%.*ls" after %d seconds without a response. Check the service and network connections. 0 0
1480 The mirrored database "%.*ls" is changing roles from "%ls" to "%ls" due to %S_MSG. 0 0
1481 Database mirroring could not repair physical page %S_PGID in database "%.*ls". The mirroring partner could not be contacted or did not provide a copy of the page. Possible reasons include a lack of network connectivity or that the copy of the page kept by the partner is also corrupted. To learn whether the partners are currently connected, view the mirroring_state_desc column of the sys.database_mirroring catalog view. If they are connected, for information about why the partner could not provide a copy of the page, examine its error log entries from around the time when this message was reported. Try to resolve the error and resume mirroring. 0 0
1485 Database mirroring has been enabled on this instance of SQL Server. 0 0
1486 Database Mirroring Transport is disabled in the endpoint configuration. 0 0
1487 Database mirroring is starting %d parallel redo thread(s) with database '%.*ls' as the mirror copy. This is an informational message only. No user action is required. 0 0
1488 Database mirroring cannot be enabled because the "%.*ls" database is in single user mode. 0 0
1489 Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information. 0 0
1499 Database mirroring error: status %u, severity %u, state %u, string %.*ls. 0 0
1501 Sort failure. Contact Technical Support. 0 0
1505 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name '%.*ls' and the index name '%.*ls'. The duplicate key value is %ls. 0 0
1509 Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support. 0 0
1510 Sort failed. Out of space or locks in database '%.*ls'. 0 0
1511 Sort cannot be reconciled with transaction log. 0 0
1522 Sort operation failed during an index build. The overwriting of the allocation page in database '%.*ls' was prevented by terminating the sort. Run DBCC CHECKDB to check for allocation and consistency errors. It may be necessary restore the database from backup. 0 0
1523 Sort failure. The incorrect extent could not be deallocated. Contact Technical Support. 0 0
1532 New sort run starting on page %S_PGID found an extent not marked as shared. Retry the transaction. If the problem persists, contact Technical Support. 0 0
1533 Cannot share extent %S_PGID. The correct extents could not be identified. Retry the transaction. 0 0
1534 Extent %S_PGID not found in shared extent directory. Retry the transaction. If the problem persists, contact Technical Support. 0 0
1535 Cannot share extent %S_PGID. Shared extent directory is full. Retry the transaction. If the problem persists, contact Technical Support. 0 0
1537 Cannot suspend a sort that is not in row input phase. 0 0
1538 Cannot insert a row into a sort when the sort is not in row input phase. 0 0
1540 Cannot sort a row of size %d, which is greater than the allowable maximum of %d. Consider resubmitting the query using the ROBUST PLAN hint. 0 0
1541 Sort failure. A defective CLR type comparison function is suspected. 0 0
1542 BobMgr::GetBuf: Sort Big Output Buffer write not complete after %d seconds. 0 0
1543 Operating system error '%ls' resulted from attempt to read the following: sort run page %S_PGID, in file '%ls', in database with ID %d. Sort is retrying the read. 0 0
1701 Creating or altering table '%.*ls' failed because the minimum row size would be %d, including %d bytes of internal overhead. This exceeds the maximum allowable table row size of %d bytes. 0 0
1702 CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns. 0 0
1706 The system table '%.*ls' can only be created or altered during an upgrade. 0 0
1707 Cannot specify TEXTIMAGE_ON filegroup for a partitioned table. 0 0
1708 Warning: The table "%.*ls" has been created, but its maximum row size exceeds the allowed maximum of %d bytes. INSERT or UPDATE to this table will fail if the resulting row exceeds the size limit. 0 0
1709 Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns. 0 0
1710 Cannot use alias type with rule or default bound to it as a column type in table variable or return table definition in table valued function. Type '%.*ls' has a %S_MSG bound to it. 0 0
1711 Cannot define PRIMARY KEY constraint on column '%.*ls' in table '%.*ls'. The computed column has to be persisted and not nullable. 0 0
1712 Online index operations can only be performed in Enterprise edition of SQL Server. 0 0
1713 Cannot execute %ls on/using table '%.*ls' since the table is the target table or part of cascading actions of a currently executing trigger. 0 0
1714 Alter table failed because unique column IDs have been exhausted for table '%.*ls'. 0 0
1715 Foreign key '%.*ls' creation failed. Only NO ACTION referential update action is allowed for referencing computed column '%.*ls'. 0 0
1716 FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, or add a FILESTREAM column to the table. 0 0
1717 FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause. 0 0
1718 Change tracking must be enabled on database '%.*ls' before it can be enabled on table '%.*ls'. 0 0
1719 FILESTREAM data cannot be placed on an empty filegroup. 0 0
1720 Cannot drop FILESTREAM filegroup or partition scheme since table '%.*ls' has FILESTREAM columns. 0 0
1721 Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes. 0 0
1722 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme is not specified for FILESTREAM data. 0 0
1723 Cannot %S_MSG %S_MSG '%.*ls' since a partition scheme was specified for FILESTREAM data but not for the table. 0 0
1724 Filegroup '%.*ls' is not a FILESTREAM filegroup or partition scheme of FILESTREAM filegroups. 0 0
1725 Cannot add FILESTREAM column to %S_MSG '%.*ls' because an INSTEAD OF trigger exists on the %S_MSG. 0 0
1726 Cannot add FILESTREAM filegroup or partition scheme since table '%.*ls' has a FILESTREAM filegroup or partition scheme already. 0 0
1727 Cannot create non-clustered index '%.*ls' on table '%.*ls' with the FILESTREAM_ON clause. 0 0
1728 Cannot create index '%.*ls' on table '%.*ls' because the computed column '%.*ls' uses a FILESTREAM column. 0 0
1729 Cannot create table '%.*ls' because the partitioning column '%.*ls' uses a FILESTREAM column. 0 0
1730 Creating or altering compressed table '%.*ls' failed because the uncompressed row size would be %d, including %d bytes of internal overhead. This exceeds the maximum allowable table row size of %d bytes. 0 0
1731 Cannot create the sparse column '%.*ls' in the table '%.*ls' because an option or data type specified is not valid. A sparse column must be nullable and cannot have the ROWGUIDCOL, IDENTITY, or FILESTREAM properties. A sparse column cannot be of the following data types: text, ntext, image, geometry, geography, or user-defined type. 0 0
1732 Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a table cannot have more than one sparse column set. Modify the statement so that only one column is specified as COLUMN_SET FOR ALL_SPARSE_COLUMNS. 0 0
1733 Cannot create the sparse column set '%.*ls' in the table '%.*ls' because a sparse column set must be a nullable xml column. Modify the column definition to allow null values. 0 0
1734 Cannot create the sparse column set '%.*ls' in the table '%.*ls' because the table already contains one or more sparse columns. A sparse column set cannot be added to a table if the table contains a sparse column. 0 0
1736 The column '%.*ls' in the table '%.*ls' cannot be referenced in a CHECK constraint or computed column definition because the column is a sparse column set. A sparse column set cannot be referenced in a a CHECK constraint or computed column definition. 0 0
1738 Cannot create table '%.*ls' with only a column set column and without any non-computed columns in the table. 0 0
1750 Could not create constraint. See previous errors. 0 0
1752 Column '%.*ls' in table '%.*ls' is invalid for creating a default constraint. 0 0
1753 Column '%.*ls.%.*ls' is not the same length or scale as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. Columns participating in a foreign key relationship must be defined with the same length and scale. 0 0
1754 Defaults cannot be created on columns with an IDENTITY attribute. Table '%.*ls', column '%.*ls'. 0 0
1755 Defaults cannot be created on columns of data type timestamp. Table '%.*ls', column '%.*ls'. 0 0
1756 Skipping FOREIGN KEY constraint '%.*ls' definition for temporary table. FOREIGN KEY constraints are not enforced on local or global temporary tables. 0 0
1757 Column '%.*ls.%.*ls' is not of same collation as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. 0 0
1758 Only a single constraint can be added or dropped online with no other operations in the same statement. 0 0
1759 Computed column '%.*ls' in table '%.*ls' is not allowed to be used in another computed-column definition. 0 0
1760 Constraints of type %ls cannot be created on columns of type %ls. 0 0
1761 Cannot create the foreign key "%.*ls" with the SET NULL referential action, because one or more referencing columns are not nullable. 0 0
1762 Cannot create the foreign key "%.*ls" with the SET DEFAULT referential action, because one or more referencing not-nullable columns lack a default constraint. 0 0
1763 Cross-database foreign key references are not supported. Foreign key '%.*ls'. 0 0
1764 Computed Column '%.*ls' in table '%.*ls' is invalid for use in '%ls' because it is not persisted. 0 0
1765 Foreign key '%.*ls' creation failed. Only NO ACTION and CASCADE referential delete actions are allowed for referencing computed column '%.*ls'. 0 0
1766 Foreign key references to temporary tables are not supported. Foreign key '%.*ls'. 0 0
1767 Foreign key '%.*ls' references invalid table '%.*ls'. 0 0
1768 Foreign key '%.*ls' references object '%.*ls' which is not a user table. 0 0
1769 Foreign key '%.*ls' references invalid column '%.*ls' in referencing table '%.*ls'. 0 0
1770 Foreign key '%.*ls' references invalid column '%.*ls' in referenced table '%.*ls'. 0 0
1771 Cannot create foreign key '%.*ls' because it references object '%.*ls' whose clustered index '%.*ls' is disabled. 0 0
1772 Foreign key '%.*ls' is not valid. A system table cannot be used in a foreign key definition. 0 0
1773 Foreign key '%.*ls' has implicit reference to object '%.*ls' which does not have a primary key defined on it. 0 0
1774 The number of columns in the referencing column list for foreign key '%.*ls' does not match those of the primary key in the referenced table '%.*ls'. 0 0
1775 Cannot create foreign key '%.*ls' because it references object '%.*ls' whose PRIMARY KEY index '%.*ls' is disabled. 0 0
1776 There are no primary or candidate keys in the referenced table '%.*ls' that match the referencing column list in the foreign key '%.*ls'. 0 0
1778 Column '%.*ls.%.*ls' is not the same data type as referencing column '%.*ls.%.*ls' in foreign key '%.*ls'. 0 0
1779 Table '%.*ls' already has a primary key defined on it. 0 0
1781 Column already has a DEFAULT bound to it. 0 0
1784 Cannot create the foreign key '%.*ls' because the referenced column '%.*ls.%.*ls' is a non-persisted computed column. 0 0
1785 Introducing FOREIGN KEY constraint '%.*ls' on table '%.*ls' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. 0 0
1786 Either column '%.*ls.%.*ls' or referencing column '%.*ls.%.*ls' in foreign key '%.*ls' is a timestamp column. This data type cannot be used with cascading referential integrity constraints. 0 0
1787 Cannot define foreign key constraint '%.*ls' with cascaded DELETE or UPDATE on table '%.*ls' because the table has an INSTEAD OF DELETE or UPDATE TRIGGER defined on it. 0 0
1788 Cascading foreign key '%.*ls' cannot be created where the referencing column '%.*ls.%.*ls' is an identity column. 0 0
1789 Cannot use CHECKSUM(*) in a computed column definition. 0 0
1790 The name of a user-defined table type cannot start with a number ( 0 0
1791 A DEFAULT constraint cannot be created on the column '%.*ls' in the table '%.*ls' because the column is a sparse column or sparse column set. Sparse columns or sparse column sets cannot have a DEFAULT constraint. 0 0
1801 Database '%.*ls' already exists. Choose a different database name. 0 0
1802 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 0 0
1803 The CREATE DATABASE statement failed. The primary file must be at least %d MB to accommodate a copy of the model database. 0 0
1806 CREATE DATABASE failed. The default collation of database '%.*ls' cannot be set to '%.*ls'. 0 0
1807 Could not obtain exclusive lock on database '%.*ls'. Retry the operation later. 0 0
1810 The model database must be updatable before a new database can be created. 0 0
1812 CREATE DATABASE failed. COLLATE clause cannot be used with the FOR ATTACH option. 0 0
1813 Could not open new database '%.*ls'. CREATE DATABASE is aborted. 0 0
1814 Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized. 0 0
1815 The %ls property cannot be used with database snapshot files. 0 0
1816 Database snapshot on the system database %.*ls is not allowed. 0 0
1817 Only the owner of database "%.*s" or the system administrator can create a database snapshot on it. 0 0
1818 Primary log file '%ls' is missing and the database was not cleanly shut down so it cannot be rebuilt. 0 0
1819 Could not create default log file because the name was too long. 0 0
1821 Cannot create a database snapshot on another database snapshot. 0 0
1822 The database must be online to have a database snapshot. 0 0
1823 A database snapshot cannot be created because it failed to start. 0 0
1824 Cannot attach a database that was being restored. 0 0
1825 Filegroups and collations cannot be specified for database snapshots. 0 0
1826 User-defined filegroups are not allowed on "%ls". 0 0
1827 CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of %I64d MB per %S_MSG. 0 0
1828 The logical file name "%.*ls" is already in use. Choose a different name. 0 0
1829 The FOR ATTACH option requires that at least the primary file be specified. 0 0
1830 The files '%.*ls' and '%.*ls' are both primary files. A database can only have one primary file. 0 0
1831 File ONLINE/OFFLINE syntax cannot be used with CREATE DATABASE. 0 0
1832 Cannot attach the file '%.*ls' as database '%.*ls'.%.*ls 0 0
1833 File '%ls' cannot be reused until after the next BACKUP LOG operation. 0 0
1834 The file '%ls' cannot be overwritten. It is being used by database '%.*ls'. 0 0
1835 Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d. 0 0
1836 Cannot create the default data files because the name that was supplied is too long. 0 0
1837 The file name "%ls" is too long to create an alternate stream name. 0 0
1838 Offline database file(s) have been overwritten while being reverted to online state from a database snapshot. The reverted file might contain invalid pages. Please run database consistency checks to assess the data integrity. 0 0
1839 Could not create default data files because the name '%ls' is a reserved device name. 0 0
1842 The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than 2147483647 in units of both page size and percentage. 0 0
1843 Reverting database '%ls' to the point in time of database snapshot '%ls' with split point LSN %.*ls (0x%ls). This is an informational message only. No user action is required. 0 0
1844 %ls is not supported on %ls. 0 0
1845 Cannot find SQL Volume Shadow Copy Service (VSS) Writer in writer metadata document provided by VSS while creating auto-recovered VSS snapshot for online DBCC check. 0 0
1846 Cannot find SQL Volume Shadow Copy (VSS) Writer component for database '%ls' while creating auto-recovered VSS snapshot for online DBCC check. 0 0
1847 The current version of the operating system doesn't support auto-recovered Volume Shadow Copy (VSS) snapshots. 0 0
1848 Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database '%ls' for online DBCC check. 0 0
1849 CREATE DATABASE failed because FILESTREAM filegroups were declared and ALLOW_SNAPSHOT_ISOLATION or READ_COMMITTED_SNAPSHOT is set to ON in the model database. Either set ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to OFF in the model database, or create the database without declaring any FILESTREAM filegroups, set ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT to OFF in the new database, and then use ALTER DATABSE to add FILESTREAM filegroups and files. 0 0
1901 Cannot create index or statistics '%.*ls' on view '%.*ls' because key column '%.*ls' is imprecise, computed and not persisted. Consider removing reference to column in view index or statistics key or changing column to be precise. If column is computed in base table consider marking it PERSISTED there. 0 0
1902 Cannot create more than one clustered index on %S_MSG '%.*ls'. Drop the existing clustered index '%.*ls' before creating another. 0 0
1904 The %S_MSG '%.*ls' on table '%.*ls' has %d column names in %S_MSG key list. The maximum limit for index or statistics key column list is %d. 0 0
1907 Cannot recreate index '%.*ls'. The new index definition does not match the constraint being enforced by the existing index. 0 0
1908 Column '%.*ls' is partitioning column of the index '%.*ls'. Partition columns for a unique index must be a subset of the index key. 0 0
1909 Cannot use duplicate column names in %S_MSG. Column name '%.*ls' listed more than once. 0 0
1910 Could not create %S_MSG '%.*ls' because it exceeds the maximum of %d allowed per table or view. 0 0
1911 Column name '%.*ls' does not exist in the target table or view. 0 0
1912 Could not proceed with index DDL operation on %S_MSG '%.*ls' because it conflicts with another concurrent operation that is already in progress on the object. The concurrent operation could be an online index operation on the same object or another concurrent operation that moves index pages like DBCC SHRINKFILE. 0 0
1913 The operation failed because an index or statistics with name '%.*ls' already exists on %S_MSG '%.*ls'. 0 0
1914 Index cannot be created on object '%.*ls' because the object is not a user table or view. 0 0
1915 Cannot alter a non-unique index with ignore_dup_key index option. Index '%.*ls' is non-unique. 0 0
1916 CREATE INDEX options %ls and %ls are mutually exclusive. 0 0
1917 Cannot create, rebuild or drop an index on a local temporary table online. Perform the index operation offline. 0 0
1919 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index. 0 0
1921 Invalid %S_MSG '%.*ls' specified. 0 0
1922 Filegroup '%.*ls' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. Use ALTER DATABASE to add one or more files to the filegroup. 0 0
1924 Filegroup '%.*ls' is read-only. 0 0
1925 Cannot convert a clustered index to a nonclustered index by using the DROP_EXISTING option. To change the index type from clustered to nonclustered, delete the clustered index, and then create a nonclustered index by using two separate statements. 0 0
1927 There are already statistics on table '%.*ls' named '%.*ls'. 0 0
1929 Statistics cannot be created on object '%.*ls' because the object is not a user table or view. 0 0
1930 Cannot convert a nonclustered index to a clustered index because a foreign key constraint references the index. Remove the foreign key constraint and then retry the operation. 0 0
1931 The SQL statement cannot be executed because filegroup '%.*ls' is offline. Use the sys.database_files or sys.master_files catalog view to determine the state of the files in this filegroup and then restore the offline file(s) from backup. 0 0
1934 %ls failed because the following SET options have incorrect settings: '%.*ls'. Verify that SET options are correct for use with %S_MSG. 0 0
1935 Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'. 0 0
1937 Cannot create %S_MSG on view '%.*ls' because it references another view '%.*ls'. Consider expanding referenced view's definition by hand in indexed view definition. 0 0
1938 Index cannot be created on view '%.*ls' because the underlying object '%.*ls' has a different owner. 0 0
1939 Cannot create %S_MSG on view '%.*ls' because the view is not schema bound. 0 0
1940 Cannot create %S_MSG on view '%.*ls'. It does not have a unique clustered index. 0 0
1941 Cannot create nonunique clustered index on view '%.*ls' because only unique clustered indexes are allowed. Consider creating unique clustered index instead. 0 0
1942 Cannot create %S_MSG on view '%.*ls'. It contains text, ntext, image, FILESTREAM or xml columns. 0 0
1944 Index '%.*ls' was not created. This index has a key length of at least %d bytes. The maximum permissible key length is %d bytes. 0 0
1945 Warning! The maximum key length is %d bytes. The index '%.*ls' has maximum length of %d bytes. For some combination of large values, the insert/update operation will fail. 0 0
1946 Operation failed. The index entry of length %d bytes for the index '%.*ls' exceeds the maximum length of %d bytes. 0 0
1947 Cannot create %S_MSG on view "%.*ls". The view contains a self join on "%.*ls". 0 0
1949 Cannot create %S_MSG on view '%.*ls'. The function '%s' yields nondeterministic results. Use a deterministic system function, or modify the user-defined function to return deterministic results. 0 0
1956 Cannot create %S_MSG on the '%.*ls' view because it uses the nondeterministic user-defined function '%.*ls'. Remove the reference to the function, or make it deterministic. 0 0
1957 Cannot create %S_MSG on view '%.*ls' because view uses imprecise user-defined function '%.*ls'. Consider removing reference to function or altering it to be precise. 0 0
1959 Cannot create an index on a view or computed column because the compatibility level of this database is less than 80. Use sp_dbcmptlevel to raise the compatibility level of the database. 0 0
1961 Cannot create %S_MSG on view '%.*ls'. The collation cast expression with collation name '%.*ls' is non-deterministic because it is dependent on the operating system. 0 0
1962 Cannot create %S_MSG on view '%.*ls' because column '%.*ls' that is referenced by the view in the WHERE or GROUP BY clause is imprecise. Consider eliminating the column from the view, or altering the column to be precise. 0 0
1963 Cannot create %S_MSG on view "%.*ls". The view contains a convert that is imprecise or non-deterministic. 0 0
1964 Cannot create %S_MSG on view "%.*ls". The view contains an imprecise constant. 0 0
1965 Cannot create %S_MSG on view "%.*ls". The view contains an imprecise arithmetic operator. 0 0
1966 Cannot create %S_MSG on view '%.*ls'. The view contains an imprecise aggregate operator. 0 0
1967 Cannot create a new clustered index on a view online. 0 0
1968 Cannot convert a nonclustered index to a clustered index online using DROP_EXISTING option. 0 0
1969 Default FILESTREAM filegroup is not available in database '%.*ls'. 0 0
1970 Warning: Online index operation on table '%.*ls' will proceed but concurrent access to the table may be limited due to residual lock on the table from a previous operation in the same transaction. 0 0
1971 Cannot disable index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that uses this index. 0 0
1972 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to alter the referencing view '%.*ls' while disabling its clustered index. 0 0
1973 Cannot perform the specified operation on disabled index '%.*ls' on %S_MSG '%.*ls'. 0 0
1974 Cannot perform the specified operation on %S_MSG '%.*ls' because its clustered index '%.*ls' is disabled. 0 0
1975 Index '%.*ls' row length exceeds the maximum permissible length of '%d' bytes. 0 0
1976 Cannot create index or statistics '%.*ls' on view '%.*ls' because cannot verify key column '%.*ls' is precise and deterministic. Consider removing column from index or statistics key, marking column persisted in base table if it is computed, or using non-CLR-derived column in key. 0 0
1977 Could not create %S_MSG '%.*ls' on table '%.*ls'. Only XML Index can be created on XML column '%.*ls'. 0 0
1978 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as a key column in an index or statistics. 0 0
1979 Cannot use index option ignore_dup_key to alter index '%.*ls' as it enforces a primary or unique constraint. 0 0
1980 Index cannot be created on computed column '%.*ls' of table '%.*ls' because the underlying object '%.*ls' has a different owner. 0 0
1981 Warning: The maximum length of the row exceeds the permissible limit of %d bytes. For some combination of large values, the insert/update operation will fail. 0 0
1982 Cannot create %S_MSG on view '%.*ls' because the view references non-deterministic or imprecise member function '%.*ls' on CLR type '%.*ls'. Consider removing reference to the function or altering the function to behave in a deterministic way. Do not declare a CLR function that behaves non-deterministically to have IsDeterministic=true, because that can lead to index corruption. See Books Online for details. 0 0
1983 Cannot create %S_MSG on view '%.*ls'. The function '%s' yields imprecise results. Use a precise system function, or modify the user-defined function to return precise results. 0 0
1984 Index '%.*ls' cannot be created or rebuilt. The specified row length for this index using the vardecimal storage format exceeds the maximum allowed length of '%d' bytes. 0 0
1985 Cannot create %S_MSG on view '%.*ls'. It contains one or more XML data type methods. 0 0
1986 Cannot replace non-hypothetical index '%.*ls' with a hypothetical index using the DROP_EXISTING option. 0 0
1987 Cannot %S_MSG %S_MSG '%.*ls' on %S_MSG '%.*ls' because its %S_MSG is disabled. 0 0
1988 Cannot rebuild clustered index '%.*ls' online because it is disabled. 0 0
1989 Cannot enable foreign key constraint '%.*ls' as index '%.*ls' on referenced key is disabled. 0 0
1990 Cannot define an index on a view with ignore_dup_key index option. Remove ignore_dup_key option and verify that view definition does not allow duplicates, or do not index view. 0 0
1991 Cannot disable clustered index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that references this table. 0 0
1992 Warning: Foreign key '%.*ls' on table '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'. 0 0
1993 Cannot partition an index on a table variable or return table definition in table valued function. 0 0
1994 Cannot create or update statistics on view "%.*ls" because both FULLSCAN and NORECOMPUTE options are required. 0 0
1995 Cannot rebuild hypothetical index '%.*ls' online. 0 0
1996 Could not create index enforcing primary key constraint '%.*ls' using DROP_EXISTING option because table has an XML or spatial index. Drop the XML or spatial index, create the primary key contstraint, and recreate the XML or spatial index. 0 0
1997 Could not convert the XML or spatial index '%.*ls' to a relational index by using the DROP_EXISTING option. Drop the XML or spatial index and create a relational index with the same name. 0 0
1998 Warning: Clustered index '%.*ls' on view '%.*ls' referencing table '%.*ls' was disabled as a result of disabling the index '%.*ls'. 0 0
1999 Column '%.*ls' in table '%.*ls' is of a type that is invalid for use as included column in an index. 0 0
11000 Unknown status code for this column. 0 0
11001 Non-NULL value successfully returned. 0 0
11001 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) (.Net SqlClient Data Provider 0 0
11002 Deferred accessor validation occurred. Invalid binding for this column. 0 0
11003 Could not convert the data value due to reasons other than sign mismatch or overflow. 0 0
11004 Successfully returned a NULL value. 0 0
11005 Successfully returned a truncated value. 0 0
11006 Could not convert the data type because of a sign mismatch. 0 0
11007 Conversion failed because the data value overflowed the data type used by the provider. 0 0
11008 The provider cannot allocate memory or open another storage object on this column. 0 0
11009 The provider cannot determine the value for this column. 0 0
11010 The user did not have permission to write to the column. 0 0
11011 The data value violated the integrity constraints for the column. 0 0
11012 The data value violated the schema for the column. 0 0
11013 The column had a bad status. 0 0
11014 The column used the default value. 0 0
11015 The column was skipped when setting data. 0 0
11031 The row was successfully deleted. 0 0
11032 The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. 0 0
11033 The row was released even though it had a pending change. 0 0
11034 Deletion of the row was canceled during notification. 0 0
11036 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized. 0 0
11037 The row has a pending delete or the deletion had been transmitted to the data source. 0 0
11038 The row is a pending insert row. 0 0
11039 DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source. 0 0
11040 Deleting the row violated the integrity constraints for the column or table. 0 0
11041 The row handle was invalid or was a row handle to which the current thread does not have access rights. 0 0
11042 Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS. 0 0
11043 The row has a storage object open. 0 0
11044 The provider ran out of memory and could not fetch the row. 0 0
11045 User did not have sufficient permission to delete the row. 0 0
11046 The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out. 0 0
11047 Updating did not meet the schema requirements. 0 0
11048 There was a recoverable, provider-specific error, such as an RPC failure. 0 0
11100 The provider indicates that conflicts occurred with other properties or requirements. 0 0
11101 Could not obtain an interface required for text, ntext, or image access. 0 0
11102 The provider could not support a required row lookup interface. 0 0
11103 The provider could not support an interface required for the UPDATE/DELETE/INSERT statements. 0 0
11104 The provider could not support insertion on this table. 0 0
11105 The provider could not support updates on this table. 0 0
11106 The provider could not support deletion on this table. 0 0
11107 The provider could not support a row lookup position. 0 0
11108 The provider could not support a required property. 0 0
11109 The provider does not support an index scan on this data source. 0 0
11201 This message could not be delivered because the FROM service name is missing. The message origin is: '%ls'. 0 0
11202 This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls". 0 0
11203 This message has been dropped because the FROM broker instance is missing. The message origin is '%ls'. 0 0
11204 This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: "%.*ls". Message origin: "%ls". 0 0
11205 This message has been dropped because the TO service name is missing. The message origin is "%ls". 0 0
11206 This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls". 0 0
11207 This message has been dropped because the service contract name is missing. The message origin is "%ls". 0 0
11208 This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name "%.*ls". Message origin: "%ls". 0 0
11209 This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: '%ls'. 0 0
11210 This message has been dropped because the TO service could not be found. Service name: "%.*ls". Message origin: "%ls". 0 0
11211 This message has been dropped because the user does not have permission to access the target database. Database ID: %d. Message origin: &quot;%ls&quot;. 0 0
11212 This message could not be delivered because the conversation endpoint has already been closed. 0 0
11213 This message could not be delivered because this is not the first message in the conversation. 0 0
11214 This message could not be delivered because the '%.*ls' contract could not be found or the service does not accept conversations for the contract. 0 0
11215 This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: '%.*ls'. 0 0
11216 This message could not be delivered because there is already another task processing this message. 0 0
11217 This message could not be delivered because it is out of sequence with respect to the conversation. Conversation receive sequence number: %I64d, Message sequence number: %I64d. 0 0
11218 This message could not be delivered because it is a duplicate. 0 0
11219 This message could not be delivered because the destination queue has been disabled. Queue ID: %d. 0 0
11220 This message could not be delivered because the TO broker instance is missing. 0 0
11221 This message could not be delivered because there is an inconsistency in the message header. 0 0
11222 This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Service Name: '%.*ls'. Conversation Endpoint TO Service Name: '%.*ls'. 0 0
11223 This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Message service contract name: '%.*ls'. Conversation endpoint service contract name: '%.*ls'. 0 0
11224 This message could not be delivered because another instance of this service program has already started conversing with this endpoint. 0 0
11225 This message could not be delivered because the message type name could not be found. Message type name: '%.*ls'. 0 0
11226 This message could not be delivered because the message type is not part of the service contract. Message type name: '%.*ls'. Service contract name: '%.*ls'. 0 0
11227 This message could not be delivered because the initiator service has sent a message with a message type that can only be sent by the target. Message type name: '%.*ls'. Service contract name: '%.*ls'. 0 0
11228 This message could not be delivered because the target service has sent a message with a message type that can only be sent by the initiator. Message type name: '%.*ls'. Service contract name: '%.*ls'. 0 0
11229 This message could not be delivered because the security context could not be retrieved. 0 0
11230 This message could not be delivered because the message could not be decrypted and validated. 0 0
11231 This message could not be delivered because the conversation endpoint is not secured, however the message is secured. 0 0
11232 This message could not be delivered because the conversation endpoint is secured, however the message is not secured. 0 0
11233 This message has been dropped because the session key of the conversation endpoint does not match that of the message. 0 0
11234 This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls. 0 0
11235 Received a malformed message. The binary message class (%d:%d) is not defined. This may indicate network problems or that another application is connected to the Service Broker endpoint. 0 0
11236 A corrupted message has been received. The binary header size of %d is expected, however the header size received was %d. 0 0
11237 A %S_MSG message could not be processed due to insufficient memory. The message was dropped. 0 0
11238 A corrupted message has been received. The private variable data segment is malformed. 0 0
11239 A corrupted message has been received. The private variable data segment extends beyond the length of the message. 0 0
11240 A corrupted message has been received. The binary message preamble is malformed. 0 0
11241 A corrupted message has been received. The conversation security version number is not %d.%d. 0 0
11242 A corrupted message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found: %d. 0 0
11243 A corrupted message has been received. The public variable data element (%d) has been duplicated in this message. 0 0
11244 A corrupted message has been received. The handshake validation header is malformed. 0 0
11245 A corrupted message has been received. The maximum number of private variable data elements (%d) has been exceeded. Private variable data elements found: %d. 0 0
11246 A corrupted message has been received. The private variable data element (%d) has been duplicated in this message. 0 0
11247 A corrupted message has been received. The login negotiate header is invalid. 0 0
11248 A corrupted message has been received. The SSPI login header is invalid. 0 0
11249 A corrupted message has been received. The pre-master-secret is invalid. 0 0
11250 A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11251 A corrupted message has been received. The service pair security header source certificate and the signature must both be present or both be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11252 A corrupted message has been received. The destination certificate serial number is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11253 A corrupted message has been received. The service pair security header destination certificate, the key exchange key, the key exchange key ID, and the session key must all be present or all be absent. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11254 A corrupted message has been received. The session key ID is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11255 A corrupted message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11256 A corrupted message has been received. The MIC is present, however the message body or encryption flag is missing. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11257 A corrupted message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11258 A corrupted message has been received. The MIC size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11259 A corrupted message has been received. The certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11260 A corrupted message has been received. The certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11261 A corrupted message has been received. The destination certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11262 A corrupted message has been received. The destination certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11263 A corrupted message has been received. The service pair security header size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11264 A corrupted message has been received. The key exchange key size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11265 A corrupted message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11266 A corrupted message has been received. The encrypted session key size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11267 A corrupted message has been received. The session key ID size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11268 A corrupted message has been received. The salt size is %d, however it must be %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11269 A corrupted message has been received. A UNICODE string is not two byte aligned within the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11270 A corrupted message has been received. A UNICODE string is greater than the maximum allowed size of %d bytes. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11271 A corrupted message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11272 A corrupted message has been received. The message ID must not be NULL. 0 0
11273 A corrupted message has been received. The message body is not properly padded for encryption. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11274 A corrupted message has been received. A sequence number is larger than allowed. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11275 A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11276 A corrupted message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11277 A corrupted message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11278 A corrupted message has been received. The message type is missing for this message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11279 A corrupted message has been received. The message type must not be set in this message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11280 A packet of size %lu bytes could not be processed because it exceeds the receive buffer count. 0 0
11281 A corrupted message has been received. The private portion of the message header is malformed. 0 0
11282 This message has been dropped due to licensing restrictions. See the documentation for further details. 0 0
11285 This forwarded message has been dropped because the hops remaining count has reached 0. 0 0
11286 Dropped this forwarded message because this SQL Server instance is out of memory. 0 0
11288 This forwarded message has been dropped because a duplicate message is already being forwarded. 0 0
11289 This forwarded message has been dropped because its memory usage would exceed the configured memory limit of %d bytes for forwarded messages. 0 0
11290 This forwarded message was dropped because the message could not be delivered within the message time to live. This may indicate that the forwarding route is incorrectly configured or that the destination is unavailable. 0 0
11291 This forwarded message has been dropped because the time consumed has exceeded the message's time to live of %u seconds (the message arrived with %u seconds consumed and used %u seconds in this broker). 0 0
11292 The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events for the error. 0 0
11293 This forwarded message has been dropped because a transport is shutdown. 0 0
11294 This forwarded message has been dropped because the destination route is not valid. 0 0
11295 Endpoint configuration change detected. Service Broker manager and transport will now restart. 0 0
11296 Certificate change detected. Service Broker manager and transport will now restart. 0 0
11297 A corrupted message has been received. The private variable data segment offset is incorrect. 0 0
11298 A corrupted message has been received. The public variable data segment offset is incorrect. 0 0
11299 A corrupted message has been received. An unsequenced message had a non-zero sequence number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
11300 Error wile committing a readonly or a TEMPDB XDES, Shutting down the server. 0 0
11301 Error while performing transaction notification for object %p event %d. 0 0
11302 Error during rollback. shutting down database (location: %d). 0 0
11303 Error releasing reserved log space: %ls space %I64d, code %d, state %d. 0 0
11304 Failed to record outcome of a local two-phase commit transaction. Taking database offline. 0 0
11400 ALTER TABLE SWITCH statement failed. Index '%.*ls' on indexed view '%.*ls' uses partition function '%.*ls', but table '%.*ls' uses non-equivalent partition function '%.*ls'. Index on indexed view '%.*ls' and table '%.*ls' must use an equivalent partition function. 0 0
11401 ALTER TABLE SWITCH statement failed. Table '%.*ls' is %S_MSG, but index '%.*ls' on indexed view '%.*ls' is %S_MSG. 0 0
11402 ALTER TABLE SWITCH statement failed. Target table '%.*ls' is referenced by %d indexed view(s), but source table '%.*ls' is only referenced by %d indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the source table. 0 0
11403 ALTER TABLE SWITCH statement failed. Indexed view '%.*ls' is not aligned with table '%.*ls'. The partitioning column '%.*ls' from the indexed view calculates its value from one or more columns or an expression, rather than directly selecting from the table partitioning column '%.*ls'. Change the indexed view definition, so that the partitioning column is directly selected from table partitioning column '%.*ls'. 0 0
11404 ALTER TABLE SWITCH statement failed. Target table '%.*ls' is referenced by %d indexed view(s), but source table '%.*ls' is only referenced by %d matching indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the source table. 0 0
11405 ALTER TABLE SWITCH statement failed. Table '%.*ls' is not aligned with the index '%.*ls' on indexed view '%.*ls'. The table is partitioned on column '%.*ls', but the index on the indexed view is partitioned on column '%.*ls', which is selected from a different column '%.*ls' in table '%.*ls'. Change the indexed view definition so that the partitioning column is the same as the table's partitioning column. 0 0
11406 ALTER TABLE SWITCH statement failed. Source and target partitions have different values for the DATA_COMPRESSION option. 0 0
11407 Vardecimal storage format can not be enabled for '%.*ls'. Only Enterprise edition of SQL Server supports vardecimal. 0 0
11408 Cannot modify the column '%.*ls' in the table '%.*ls' to add or remove the COLUMN_SET attribute. To change a COLUMN_SET attribute of a column, either modify the table to remove the column and then add the column again, or drop and re-create the table. 0 0
11409 Cannot remove the column set '%.*ls' in the table '%.*ls' because the table contains more than 1025 columns. Reduce the number of columns in the table to less than 1025. 0 0
11410 Cannot modify the column '%.*ls' in the table '%.*ls' to a sparse column because the column has a default or rule bound to it. Unbind the rule or default from the column before designating the column as sparse. 0 0
11411 Cannot add the sparse column '%.*ls' to the table '%.*ls' because the data type of the column has a default or rule bound to it. Unbind the rule or default from the data type before adding the sparse column to the table. 0 0
11412 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same sparse storage attribute in tables '%.*ls' and '%.*ls'. 0 0
11413 ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same column set property in tables '%.*ls' and '%.*ls'. 0 0
11414 Warning: Option %ls is not applicable to table %.*ls because it does not have a clustered index. This option will be applied only to the table's nonclustered indexes, if it has any. 0 0
11415 Object '%.*ls' cannot be disabled or enabled. This action applies only to foreign key and check constraints. 0 0
11418 Cannot %S_MSG table '%.*ls' because the table either contains sparse columns or a column set column which are incompatible with compression. 0 0
22101 The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask returned by the CHANGETABLE(CHANGES ...) function. 0 0
22102 The arguments supplied are not valid for the CHANGES option of the CHANGETABLE function. 0 0
22103 The arguments supplied are not valid for the VERSION option of the CHANGETABLE function. 0 0
22104 A table returned by the CHANGETABLE function must be aliased. 0 0
22105 Change tracking is not enabled on table '%.*ls'. 0 0
22106 The CHANGETABLE function does not support remote data sources. 0 0
22107 Object '%.*ls' is of a data type that is not supported by the CHANGETABLE function. The object must be a user-defined table. 0 0
22108 The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SELECT statement. 0 0
22109 The "context" argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128. 0 0
22110 The number of columns specified in the CHANGETABLE(VERSION ...) function does not match the number of primary key columns for table '%.*ls'. 0 0
22111 The column '%.*ls' specified in the CHANGETABLE(VERSION ...) function is not part of the primary key for table '%.*ls'. 0 0
22112 Each primary key column must be specified once in the CHANGETABLE(VERSION ...) function. The column '%.*ls' is specified more than once. 0 0
22113 %S_MSG is not allowed because the table is being tracked for change tracking. 0 0
22114 Change tracking options for ALTER DATABASE cannot be combined with other ALTER DATABASE options. 0 0
22115 Change tracking is enabled for one or more tables in database '%.*ls'. Disable change tracking on each table before disabling it for the database. Use the sys.change_tracking_tables catalog view to obtain a list of tables for which change tracking is enabled. 0 0
22116 Change tracking is not supported by this edition of SQL Server. 0 0
22500 Unexpected 0 0
22501 All articles in the publication passed data validation (rowcount and checksum). 0 0
22502 Not All articles in the publication passed data validation (rowcount only) 0 0
22503 Initializing. 0 0
22504 Applying the snapshot to the Subscriber. 0 0
22505 The merge completed with no data changes processed. 0 0
22506 No No data needed to be merged. 0 0
22507 Uploading data changes to the Publisher. 0 0
22508 Downloading data changes to the Subscriber. 0 0
22509 Retrieving subscription information. 0 0
22510 Retrieving publication information. 0 0
22511 The merge completed successfully. 0 0
22512 Cannot use partition groups with unfiltered publications. Set "use_partition_groups" to "false" using sp_changemergepublication. 0 0
22513 Cannot use partition groups because the join filter between the following articles contains one or more functions: "%s" and "%s". 0 0
22514 Cannot use partition groups because one or more filters reference the following view, which contains functions: "%s". 0 0
22515 The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist. 0 0
22516 The publication "%s" was defined as having dynamic filters, but it does not contain any dynamic filters. 0 0
22517 The publication was defined as having no dynamic filters, but contains one or more dynamic filters. 0 0
22518 Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: '%s'. 0 0
22519 Cannot add a logical record relationship between tables "%s" and "%s" because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause. 0 0
22520 A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details. 0 0
22521 Unable to synchronize the row because the row was updated by a different process outside of replication. 0 0
22522 Article '%s' cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot be included in multiple publications or subscriptions, and cannot be republished. To include the article in multiple publications, use sp_changemergearticle to specify a different value for the partition_options property of the existing article. 0 0
22523 An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article "%s". 0 0
22524 Article '%s' is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the existing article or change the existing article using sp_changemergearticle. 0 0
22525 The publication "%s" cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3. 0 0
22526 An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition). 0 0
22527 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'. 0 0
22528 Cannot use a retention period unit other than "days" for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM. 0 0
22529 Cannot change the retention period unit for publication "%s" because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM. 0 0
22530 Cannot update any column in article "%s" that is used in a logical record relationship clause. 0 0
22531 Initialization. 0 0
22532 Upload of Subscriber changes to the Publisher. 0 0
22533 Download of Publisher changes to the Subscriber. 0 0
22534 Character mode publication does not support partitioned tables. 0 0
22535 For heterogeneous publications, the %s parameters should be specified when calling "%s". 0 0
22536 The %s parameter value cannot be updated or changed for heterogeneous publications. 0 0
22537 The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher). 0 0
22538 Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures. 0 0
22539 Use of parameters %s is invalid when parameter %s is set to %s. 0 0
22540 Cannot change publication "%s" to use sync_mode of "character", because it contains one or more logical record relationships. 0 0
22541 Cannot add a logical record relationship in publication "%s" because it uses sync_mode of "character" and could have SQL Server Compact Edition subscribers. 0 0
22542 Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subscriber changes), and 3 (disable_outofpartition_subscriber_changes). 0 0
22543 When the publication property @allow_partition_realignment is set to "false", the article property @subscriber_upload_options for all articles in the publication must be set to disable uploads. 0 0
22544 Warning: The procedure sp_mergecleanupmetadata has been deprecated. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadataretentioncleanup every time it runs, so manual cleanup of metadata is not needed. Ignoring passed-in parameters and calling sp_mergemetadataretentioncleanup. 0 0
22545 Cannot add a logical record relationship in publication "%s" because it allows Web synchronization. 0 0
22546 Cannot change publication "%s" to allow Web synchronization because it contains one or more logical record relationships. 0 0
22547 A concurrent snapshot is not allowed for snapshot publications. 0 0
22548 Vertical partitioning is only allowed for log-based articles. 0 0
22549 A shared distribution agent (%s) already exists for this subscription. 0 0
22550 Cannot drop identity column "%s" from the vertical partition when identityrangemanagementoption is set to auto. 0 0
22551 The type "%s" is invalid. Valid types are "merge", "tran", and "both". 0 0
22552 A valid value for parameter "@resync_date_str" needs to be provided when "@resync_type" is set to 2. 0 0
22553 The parameter "@resync_type" is set to "%d" but this subscription has never been successfully validated. 0 0
22554 Cannot change publication "%s" to use the sync_mode of "character" because it uses a retention period unit other than "day". Use sp_changemergepublication to set the retention period unit to "day". 0 0
22555 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. 0 0
22556 Invalid value for the property "%s". Valid values are 1 and 0. 0 0
22557 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. 0 0
22558 The status of the schema change could not be updated. 0 0
22559 The status of the schema change must be "active" or "skipped". 0 0
22560 Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function "%s". 0 0
22561 The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication "%s" to 90RTM. 0 0
22562 Cannot change the compatibility level of a publication to a value lower than the existing value. 0 0
22563 contains one or more articles that do not upload changes 0 0
22564 uses ddl replication 0 0
22565 uses other than day as unit of retention period 0 0
22566 uses logical records 0 0
22567 contains one or more articles that use subscription-based or partition-based filtering 0 0
22568 contains one or more articles which will not compensate for errors 0 0
22569 contains one or more schema only articles 0 0
22570 contains one or more articles that use automatic identity range management 0 0
22571 contains one or more articles that use datatypes new in SQL Server 2000 0 0
22572 contains one or more articles with a timestamp column 0 0
22573 uses snapshot compression with snapshot_in_defaultfolder set to false 0 0
22574 contains one or more articles that use vertical partitioning 0 0
22575 When article property 'published_in_tran_pub' is set to 'true' then article property 'upload_options' has to be set to disable uploads. 0 0
22576 Invalid failover_mode value of %d was specified for [%s].[%s].[%s], setting to 0 [immediate]. 0 0
22577 Failed to add subscription because the allowed number of %s subscriptions for SQL Workgroup Edition Publisher '%s' would be exceeded. The maximum allowed number is %d. 0 0
22578 Cannot change publication "%s" to disallow use_partition_groups because it contains one or more logical record relationships. When using logical record relationships the publication must set the @use_partition_groups property to 'true'. 0 0
22579 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. 0 0
22580 Cannot publish database '%s' because it is marked as published on a different server. Before attempting to publish this database, execute sp_replicationdboption, specifying a value of FALSE for 'publish' and 'merge publish'. 0 0
22581 Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'sync_mode' of 1 (character mode). Specify a 'sync_mode' of 0 (native mode) for the publication by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated. 0 0
22582 Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for publications that have a 'publication_compatibility_level' of less than "90RTM" (SQL Server 2005). Specify a 'publication_compatibility_level' greater than or equal to "90RTM" by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated. 0 0
22583 Article '%s' cannot be added or modified in publication '%s'. The replication of FILESTREAM columns is not supported for articles that have a 'schema_option' set to 0x20000000. This converts large object data types to data types that are supported on earlier versions of Microsoft SQL Server. Remove this 'schema_option' setting by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated. 0 0
22584 Warning: Values of some of the flags specified in the 'schema_option' property are not compatible with the publication's compatibility level. The modified schema_option value of '%s' will be used instead. 0 0
22585 The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%s'. Enabling this option after the article is created can cause replication to fail when the data in a FILESTREAM column exceeds 2GB and there is a conflict during replication. If you want FILESTREAM data to be replicated, drop and re-create the article, and specify the appropriate schema option when you re-create the article. 0 0
22586 Column '%s' cannot be added or modified in article '%s' of publication '%s'. The DDL operatoin on hierarchyid and FILESTREAM columns is not supported for publications that have a 'sync_mode' of 1 (character mode) or with a lower than 90RTM backward compatibility level. 0 0
22801 Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view. 0 0
22802 Starting the Change Data Capture Cleanup Agent job using low watermark %s. 0 0
22803 Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view. 0 0
22804 Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %s but Distributor information cannot be retrieved to determine the state of the logreader agent. Make the Distributor database available, or disable distribution. 0 0
22805 For more information, query the sys.dm_cdc_errors dynamic management view. 0 0
22806 The originator ID '%s' is not valid. You must specify a non-zero ID that has never been used in the topology. 0 0
22807 The publication property '%s' cannot be modified because the peer-to-peer publication '%s' is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection. 0 0
22808 Cannot execute procedure '%s'. Publication '%s' must be enabled for peer-to-peer replication before you execute this procedure. To enable the publication for peer-to-peer replication, use sp_changepublication. 0 0
22809 The existing conflict table '%s' was dropped. 0 0
22810 The @action parameter value is not valid. Valid values are 'enable' and 'disable'. 0 0
22811 The roundtrip time-out must be greater than 0. 0 0
22812 The roundtrip '%s' finished with timeout: %d seconds. 0 0
22813 The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are SQL Server 2008 or later versions. 0 0
22814 The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology. 0 0
22815 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 0 0
22816 The qualified table name '%s' is too long to be enabled for peer-to-peer conflict detection. 0 0
22817 %s has %s. 0 0
22818 A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was skipped. 0 0
22819 A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming delete was skipped by peer %d. The conflict has to be resolved manually to guarantee data convergence between the peers. For steps on how to resolve the conflict refer to BOL. 0 0
22820 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. 0 0
22821 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. 0 0
22822 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. 0 0
22823 An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Check the priority of the destination peer and run data validation to ensure the delete conflict did not result in data non-convergence. 0 0
22824 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. 0 0
22825 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. 0 0
22827 Peer-to-peer conflict detection alert 0 0
22828 The publication '%s' was already %s for peer-to-peer conflict detection. 0 0
22829 The command %s failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d. 0 0
22830 Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22831 Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22832 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. 0 0
22833 Could not update the metadata that indicates table %s is not enabled for Change Data Capture. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22834 Could not modify the the verbose logging status for table %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22835 Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22836 Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22837 Could not delete table entries or drop objects associated with capture instance '%s'. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22838 All columns of a CDC unique index must be defined as NOT NULL. Index '%s' selected as the CDC unique index for source table '%s.%s' does not meet this requirement. Define all columns of the selected index as NOT NULL or select another unique index as the CDC index and resubmit the request. 0 0
22840 The application lock request '%s' needed to modify Change Data Capture metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 = canceled; -3 = deadlock victim; -999 validation or other call error. Examine the error cause and resbmit the request. 0 0
22841 Could not upgrade the metadata for database '%s' that is enabled for Change Data Capture. The failure occurred when executing the action '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22842 ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1. 0 0
22843 ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1. 0 0
22844 The '%s' option must be either 1 or 0. 0 0
22850 The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying the cleanup job, specify a positive threshold value. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the threshold value associated with the job to a non-negative value by using the sp_cdc_change_job stored procedure. 0 0
22851 Could not update cdc.change_tables to indicate a change in the low water mark for database %s. 0 0
22852 Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22853 Could not delete obsolete entries in the cdc.lsn_time_mapping table for database %s. The failure occurred when executing the command '%s'. The error returned was %d: '%s'. Use the action and error to determine the cause of the failure and resubmit the request. 0 0
22854 Can not enable Change Data Capture on table '%s' or add ColumnSet column to it because CDC does not support ColumnSet. 0 0
22855 Warning: The @allow_partition_switch parameter is set to 1. Change data capture will not track changes introduced in the table resulting from a partition switch which will cause data inconsistency when changes are consumed. Refer to books online for more information about partition switching behavior when using Change Data Capture. 0 0
22856 Warning: The @allow_partition_switch parameter is set to 0. ALTER TABLE ... SWITCH PARTITION statement will be disallowed on this partitioned table. Refer to books online for more information about partition switching behavior when using Change Data Capture. 0 0
22857 Warning: The @allow_partition_switch parameter must be 1 for tables that are not partitioned. The explicit setting of the parameter to 0 was ignored. Refer to books online for more information about partition switching behavior when using Change Data Capture. 0 0
22858 Unable to add entries to the Change Data Capture LSN time mapping table to reflect dml changes applied to the tracked tables. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22859 Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22860 Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22861 Unable to upgrade database '%s'. Error '%d' was raised: '%s'. Use the reported error to determine the cause of the failure and then execute sys.sp_cdc_vupgrade in the database context to rerun upgrade. 0 0
22862 The database snapshot '%s' does not exist. Correct the parameter value and resubmit the request. 0 0
22863 Failed to insert rows into Change Data Capture change tables. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22864 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. 0 0
22901 The database '%s' is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view. 0 0
22902 Caller is not authorized to initiate the requested action. Sysadmin privileges are required. 0 0
22903 Another connection is already running 'sp_replcmds' for Change Data Capture in the current database. 0 0
22904 Caller is not authorized to initiate the requested action. DBO privileges are required. 0 0
22905 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. 0 0
22906 The database '%s' cannot be enabled for Change Data Capture because a database user named 'cdc' or a schema named 'cdc' already exists in the current database. These objects are required exclusively by Change Data Capture. Drop or rename the user or schema and retry the operation. 0 0
22907 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. 0 0
22908 Could not create the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22909 Failed to cleanup the cdc.lsn_time_mapping table in database '%s' when the last database table enabled for Change Data Capture was disabled. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22910 The cleanup request for database '%s' failed. The database is not enabled for Change Data Capture. 0 0
22911 The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same database. When Change Data Capture and transactional replication are both enabled on a database, use the logreader agent to extract the log changes. 0 0
22913 Could not drop the Change Data Capture objects in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22914 Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation when Change Data Capture is enabled for a database. 0 0
22916 Could not grant SELECT permission for the change enumeration functions for capture instance '%s' and source table '%s.%s' for the specified role. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22918 One or more columns in the list of included columns was not a captured column of the change table %s. 0 0
22919 One or more columns in the list of columns needing update flags was not a captured column of the change table %s. 0 0
22920 The named capture instance %s does not exist for database %s. 0 0
22921 Unable to generate scripts for all capture instances that the caller is authorized to access. To generate all such scripts, the parameters @column_list and @update_flag_list must both be null or empty.' 0 0
22923 Could not compute the new low endpoint for database '%s' from retention %d. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22924 Could not clean up change tables for database '%s'. A failure occurred when attempting to clean up the database change tables based upon the current retention time. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22925 The number of columns captured by capture instance '%s' exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to specify a subset of the columns less than or equal to the maximum allowed and resubmit the request. 0 0
22926 Could not create a capture instance because the capture instance name '%s' already exists in the current database. Specify an explicit unique name for the parameter @capture_instance. 0 0
22927 Capture instance name '%s' exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint. 0 0
22928 Index name '%s' is not an index for table '%s.%s'. Specify a valid index name for the table. 0 0
22929 Index '%s' must be either a primary key or a unique index for table '%s.%s'. Specify an index that meets at least one of these requirements. 0 0
22930 Could not locate '%s' as a column of source table '%s.%s'. Specify a valid column name. 0 0
22931 Source table '%s.%s' does not exist in the current database. Ensure that the correct database context is set. Specify a valid schema and table name for the database. 0 0
22932 Capture instance name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules. 0 0
22938 Role name '%s' is invalid. Specify a valid name. See the topic 'Identifiers' in SQL Server Books Online for object name rules. 0 0
22939 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. 0 0
22940 Could not remove DDL history entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22941 Could not retrieve column information for index '%s' of source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22942 Columns specified in the captured column list could not be mapped to columns in source table '%s.%s'. Verify that the columns specified in the parameter @captured_column_list are delimited properly and match columns in the source table. 0 0
22943 Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key columns of the source table, or the columns defined for the index specified in the parameter @index_name to the list of captured columns and retry the operation. 0 0
22944 Could not create the specified database role '%s' for gating access to change table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22945 Could not add column information to the cdc.index_columns system table for the specified index for source table '%s.%s. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22946 Could not add column information to the cdc.captured_columns system table for source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22947 Could not create the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22948 Could not create the change enumeration functions for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22949 Could not update the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22950 Could not remove index column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22951 Could not remove captured column entries in the Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22952 Could not drop Change Data Capture objects created for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22953 Could not remove Change Data Capture metadata for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22954 Could not cleanup change tables for capture instance '%s' using low end point %s. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22955 Could not obtain the maximum LSN for the database from function 'sys.fn_cdc_get_max_lsn'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22956 Could not obtain the minimum LSN of the change table associated with capture instance '%s' from function 'sys.fn_cdc_get_min_lsn'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22957 LSN %s, specified as the new low end point for the change table associated with capture instance '%s', is not within the Change Data Capture timeline [%s, %s]. 0 0
22958 Could not create the function to query for all changes for capture instance '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22959 Could not create the function to query for net changes for capture instance '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22960 Change data capture instance '%s' has not been enabled for the source table '%s.%s'. Use sys.sp_cdc_help_change_data_capture to verify the capture instance name and retry the operation. 0 0
22961 Could not create a nonclustered index to support net change tracking for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22962 Two capture instances already exist for source table '%s.%s'. A table can have at most two capture instances. If the current tracking options are not appropriate, disable change tracking for the obsolete instance by using sys.sp_cdc_disable_table and retry the operation. 0 0
22963 Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation. 0 0
22964 LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping table. Choose an LSN value that satisfies this requirement. 0 0
22965 A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more information, see 'Delimited Identifiers' in Books Online. 0 0
22966 Could not create table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22967 Could not create a clustered index for table dbo.systranschemas in database '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22968 Could not create DDL trigger '%s' when enabling Change Data Capture for database '%s'. Additional messages in the SQL Server error log and system event log may provide more detail. 0 0
22970 The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0. 0 0
22971 Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual settings on the server and examine memory usage to see if another application is excessively consuming memory. 0 0
22972 When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other parameter must also be non-null and non-empty. 0 0
22973 The specified filegroup '%s' is not a valid filegroup for database '%s'. Specify a valid existing filegroup or create the named filegroup, and retry the operation. 0 0
22974 Tables contained in the cdc schema cannot be enabled for Change Data Capture. 0 0
22975 Source table '%s' contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and ensure that these columns are excluded from the list. 0 0
22976 Could not alter column '%s' of change table '%s' in response to a data type change in the corresponding column of the source table '%s'. The Change Data Capture meta data for source table '%s' no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22977 Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table '%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22978 Could not update the cdc.captured_columns entry for column '%s' of change table '%s' to reflect a data type change in the corresponding column of the source table '%s'. Change Data Capture column meta data for table '%s' no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22979 The unique index '%s' on table '%s' is used by Change Data Capture. The constraint using this index cannot be dropped or disabled. 0 0
22980 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. 0 0
22981 Object does not exist or access is denied. 0 0
22982 Could not create internal stored procedures used to populate the change table for capture instance '%s' and source table '%s.%s'. Refer to previous errors in the current session to identify the cause and correct any associated problems. 0 0
22983 The unique index '%s' on source table '%s' is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on the table. 0 0
22984 An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. Retry the operation. 0 0
22985 Change data capture has not been enabled for source table '%s.%s'. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in the sys.tables catalog view. 0 0
22986 Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory. 0 0
22987 Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory. 0 0
22988 This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, and Enterprise Evaluation editions. 0 0
22989 Could not enable Change Data Capture for database '%s'. Change data capture is not supported on system databases, or on a distribution database. 0 0
22990 The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds). 0 0
22991 The value specified for the parameter @maxtrans must be greater than 0. 0 0
22992 The specified @job_type, %s, is not supported. The value specified for the parameter @job_type must be N'capture' to indicate a capture job, or N'cleanup' to indicate a cleanup job. 0 0
22993 The Change Data Capture job table containing job information for database '%s' cannot be found in the msdb system database. Run the stored procedure 'sys.sp_cdc_add_job' to create the appropriate CDC capture or cleanup job. The stored procedure will create the required job table. 0 0
22994 The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the retention value associated with the job to a non-negative value less than 52594800 by using the sp_cdc_change_job stored procedure. 0 0
22995 A value for the parameter @retention cannot be specified when the job type is 'capture'. Specify NULL for the parameter, or omit the parameter from the statement. 0 0
22996 When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values. 0 0
22997 The Change Data Capture '%s' job does not exist in the system table 'msdb.dbo.cdc_jobs'. Use the stored procedure 'sys.sp_cdc_add_job' to add the Change Data Capture job. 0 0
22998 The value specified for the parameter @continuous must be 0 or 1. 0 0
22999 The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure 'sys.sp_cdc_scan' is not being run in continuous mode. 0 0
16901 %hs: This feature has not been implemented yet. 0 0
16902 %ls: The value of the parameter %ls is invalid. 0 0
16903 The "%ls" procedure was called with an incorrect number of parameters. 0 0
16904 sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE. 0 0
16905 The cursor is already open. 0 0
16906 Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more. 0 0
16907 %hs is not allowed in cursor statements. 0 0
16909 %ls: The cursor identifier value provided (%x) is not valid. 0 0
16910 The cursor %.*ls is currently used by another statement. 0 0
16911 %hs: The fetch type %hs cannot be used with forward only cursors. 0 0
16914 The "%ls" procedure was called with too many parameters. 0 0
16915 A cursor with the name '%.*ls' already exists. 0 0
16916 A cursor with the name '%.*ls' does not exist. 0 0
16917 Cursor is not open. 0 0
16922 Cursor Fetch: Implicit conversion from data type %s to %s is not allowed. 0 0
16924 Cursorfetch: The number of variables declared in the INTO list must match that of selected columns. 0 0
16925 The fetch type %hs cannot be used with dynamic cursors. 0 0
16926 sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column. 0 0
16927 Cannot fetch into text, ntext, and image variables. 0 0
16928 sp_cursor: Exec statement is not allowed as source for cursor insert. 0 0
16929 The cursor is READ ONLY. 0 0
16930 The requested row is not in the fetch buffer. 0 0
16931 There are no rows in the current fetch buffer. 0 0
16932 The cursor has a FOR UPDATE list and the requested column to be updated is not in this list. 0 0
16933 The cursor does not include the table being modified or the table is not updatable through the cursor. 0 0
16934 Optimistic concurrency check failed. The row was modified outside of this cursor. 0 0
16935 No No parameter values were specified for the sp_cursor-%hs statement. 0 0
16936 sp_cursor: One or more values parameters were invalid. 0 0
16937 A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor. 0 0
16938 sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments. 0 0
16941 Cursor updates are not allowed on tables opened with the NOLOCK option. 0 0
16942 Could not generate asynchronous keyset. The cursor has been deallocated. 0 0
16943 Could not complete cursor operation because the table schema changed after the cursor was declared. 0 0
16945 The cursor was not declared. 0 0
16946 Could not open the cursor because one or more of its tables have gone out of scope. 0 0
16947 No No rows were updated or deleted. 0 0
16948 The variable '%.*ls' is not a cursor variable, but it is used in a place where a cursor variable is expected. 0 0
16949 The variable '%.*ls' is a cursor variable, but it is used in a place where a cursor variable is not valid. 0 0
16950 The variable '%.*ls' does not currently have a cursor allocated to it. 0 0
16951 The variable '%.*ls' cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure. 0 0
16952 A cursor variable cannot be used as a parameter to a remote procedure call. 0 0
16953 Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor. 0 0
16954 Executing SQL directly; no cursor. 0 0
16955 Could not create an acceptable cursor. 0 0
16956 The created cursor is not of the requested type. 0 0
16957 FOR UPDATE cannot be specified on a READ ONLY cursor. 0 0
16958 Could not complete cursor operation because the set options have changed since the cursor was declared. 0 0
16959 Unique table computation failed. 0 0
16960 You have reached the maximum number of cursors allowed. 0 0
16961 One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query. 0 0
16962 The target object type is not updatable through a cursor. 0 0
16963 You cannot specify scroll locking on a cursor that contains a remote table. 0 0
16964 For the optimistic cursor, timestamp columns are required if the update or delete targets are remote. 0 0
16965 Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch. 0 0
16966 %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors. 0 0
16992 The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue. 0 0
16996 %ls cannot take output parameters. 0 0
16998 The asynchronous cursor worktable population thread spawn failed. 0 0
16999 Internal Cursor Error: The cursor is in an invalid state. 0 0
17000 Usage: sp_autostats [, {ON|OFF} [, ] ] 0 0
17001 Failure to send an event notification instance of type '%s' on conversation handle '%s'. Error Code = '%s'. 0 0
17002 Failed to post QUEUE_ACTIVATION event. Error code: '0x%s'. 0 0
17003 Closed event notification conversation endpoint with handle '%s', due to the following error: '%.*ls'. 0 0
17004 Event notification conversation on dialog handle '%s' closed without an error. 0 0
17005 Event notification '%ls' in database '%ls' dropped due to send time service broker errors. Check to ensure the conversation handle, service broker contract, and service specified in the event notification are active. 0 0
17049 Unable to cycle error log file from '%ls' to '%ls' due to OS error '%s'. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access." 0 0
17051 SQL Server evaluation period has expired. 0 0
17053 %ls: Operating system error %ls encountered. 0 0
17054 The current event was not reported to the Windows Events log. Operating system error = %s. You may need to clear the Windows Events log if it is full. 0 0
17056 The evaluation period for your edition of SQL Server expires in %d day(s). 0 0
17057 Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer to help diagnose the root cause. 0 0
17058 initerrlog: Could not open error log file '%s'. Operating system error = %s. 0 0
17060 %s 0 0
17061 Error: %d Severity: %d State: %d %s 0 0
17063 Error: %d Severity: %d State: %d %s 0 0
17065 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. 0 0
17066 SQL Server Assertion: File: <%s>, line=%d Failed Assertion = '%s'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 0 0
17067 SQL Server Assertion: File: <%s>, line = %d %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 0 0
17068 PrintStack Request 0 0
17069 %s 0 0
17070 Clustered instances are not supported on this edition of SQL Server. 0 0
17101 (c) 2005 Microsoft Corporation. 0 0
17102 Failed to initialize Distributed COM (CoInitializeEx returned %lx). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel. 0 0
17103 All rights reserved. 0 0
17104 Server process ID is %ld. 0 0
17105 Could not open master database in system task thread context. Terminating server. 0 0
17106 Common Criteria compliance mode is enabled. This is an informational message only; no user action is required. 0 0
17107 Perfmon counters for resource governor pools and groups failed to initialize and are disabled. 0 0
17108 Password policy update was successful. 0 0
17109 FallBack certificate was successfully created. 0 0
17110 Registry startup parameters: %.*ls 0 0
17111 Logging SQL Server messages in file '%s'. 0 0
17112 An invalid startup option %c was supplied, either from the registry or the command prompt. Correct or remove the option. 0 0
17113 Error %ls occurred while opening file '%ls' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary. 0 0
17114 Error %ls occurred while opening file '%ls' to obtain configuration information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary. 0 0
17115 Command Line Startup Parameters:%.*ls 0 0
17116 Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel. 0 0
17119 The number of concurrent user connections was reduced to %ld, because it exceeded the allowable limit for this edition of SQL Server. To avoid this message in the future, use sp_configure to permanently adjust the number of user connections within the licensed limit. 0 0
17120 SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. 0 0
17121 SQL Server is started with trace flag %d, this may cause user to see some error messages masked using '%ls'. 0 0
17123 Logging to event log is disabled. Startup option '-%c' is supplied, either from the registry or the command prompt. 0 0
17124 SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required. 0 0
17125 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. 0 0
17126 SQL Server is now ready for client connections. This is an informational message; no user action is required. 0 0
17127 initdata: No memory for kernel buffer hash table. 0 0
17128 initdata: No memory for kernel buffers. 0 0
17129 initconfig: Warning: affinity mask specified is not valid. Defaulting to no affinity. Use sp_configure 'affinity mask' or 'affinity64 mask' to configure the system to be compatible with the CPU mask on the system. You can also configure the system based on the number of licensed CPUs. 0 0
17130 Not enough memory for the configured number of locks. Attempting to start with a smaller lock hash table, which may impact performance. Contact the database administrator to configure more memory for this instance of the Database Engine. 0 0
17131 Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory. 0 0
17132 Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory. 0 0
17133 Launch of startup procedure '%s' failed. 0 0
17135 Launched startup procedure '%s'. 0 0
17136 Clearing tempdb database. 0 0
17137 Starting up database '%s'. 0 0
17138 Unable to allocate enough memory to start '%ls'. Reduce non-essential memory load or increase system memory. 0 0
17140 Could not dispatch SQL Server by Service Control Manager. Operating system error = %s. 0 0
17141 Could not register Service Control Handler. Operating system error = %s. 0 0
17142 SQL Server service has been paused. No new connections will be allowed. To resume the service, use SQL Computer Manager or the Services application in Control Panel. 0 0
17143 %s: Could not set Service Control Status. Operating system error = %s. 0 0
17144 SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, use SQL Computer Manager or the Services application in Control Panel. 0 0
17145 Service Control Handler received an invalid control code = %d. 0 0
17146 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. 0 0
17147 SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. 0 0
17148 SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 0 0
17149 Using the static lock allocation specified in the locks configuration option. Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required. 0 0
17150 Lock partitioning is enabled. This is an informational message only. No user action is required. 0 0
17152 Node configuration: node %ld: CPU mask: 0x%0*I64x Active CPU mask: 0x%0*I64x. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 0 0
17153 Processor affinity turned on: processor mask 0x%0*I64x. Threads will execute on CPUs per affinity mask/affinity64 mask config option. This is an informational message; no user action is required. 0 0
17155 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. 0 0
17156 initeventlog: Could not initiate the EventLog Service for the key '%s', last error code is %d. 0 0
17158 The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required. 0 0
17159 The server is idle. This is an informational message only. No user action is required. 0 0
17161 SQL Server could not use the NO_BUFFERING option during I/O, because the master file sector size, %d, is incorrect. Move the master file to a drive with a correct sector size. 0 0
17162 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 0 0
17163 SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required. 0 0
17164 Detected %d CPUs. This is an informational message; no user action is required. 0 0
17165 The RANU instance is terminating in response to its internal time out. This is an informational message only. No user action is required. 0 0
17166 Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 0 0
17167 Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required. 0 0
17169 Unable to locate kernel HTTP driver Httpapi.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support the kernel HTTP driver. 0 0
17170 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. 0 0
17171 SQL Server native HTTP support failed and will not be available. '%hs()' failed. Error 0x%lx. 0 0
17172 SNIInitialize() failed with error 0x%lx. 0 0
17173 Ignoring trace flag %d specified during startup. It is either an invalid trace flag or a trace flag that cannot be specified during server startup. 0 0
17174 Unable to initialize SQL Server native HTTP support due to insufficient resources. HTTP access to SQL Server will not be available. Error 0x%lx. This error typically indicates insufficient memory. Reduce non-essential memory load or increase system memory. 0 0
17175 The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx. 0 0
17176 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. 0 0
17177 This instance of SQL Server has been using a process ID of %s since %s (local) %s (UTC). This is an informational message only; no user action is required. 0 0
17178 Address Windowing Extensions is enabled. This is an informational message only; no user action is required. 0 0
17179 Could not use Address Windowing Extensions because the 'lock pages in memory' privilege was not granted. 0 0
17180 SQL Server is not configured to use all of the available system memory. To enable SQL Server to use more memory, set the awe enabled option to 1 by using the sp_configure stored procedure. 0 0
17181 SNIInitializeListener() failed with error 0x%lx. 0 0
17182 TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx. Reason: %S_MSG %.*ls 0 0
17183 Attempting to cycle error log. This is an informational message only; no user action is required. 0 0
17184 The error log has been reinitialized. See the previous log for older entries. 0 0
17185 Unable to update password policy. 0 0
17186 Failed to enqueue %s task. There may be insufficient memory. 0 0
17187 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 0 0
17188 SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls 0 0
17189 SQL Server failed with error code 0x%x to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.%.*ls 0 0
17190 FallBack certificate initialization failed with error code: %d. 0 0
17191 Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors.%.*ls 0 0
17192 Dedicated admin connection support was not started because of error 0x%lx, status code: 0x%lx. This error typically indicates a socket-based error, such as a port already in use. 0 0
17193 SQL Server native SOAP support is ready for client connections. This is an informational message only. No user action is required. 0 0
17194 The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message: %d %.*ls %.*ls 0 0
17195 The server was unable to complete its initialization sequence because the available network libraries do not support the required level of encryption. The server process has stopped. Before restarting the server, verify that SSL certificates have been installed. See Books Online topic "Configuring Client Protocols and Network Libraries". 0 0
17196 Preparing for eventual growth to %d GB with Hot Add Memory. 0 0
17197 Login failed due to timeout; the connection has been closed. This error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls 0 0
17198 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 0 0
17199 Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag %d. This is an informational message only. No user action is required. 0 0
17200 Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx. 0 0
17201 Dedicated admin connection support was established for listening locally on port %d. 0 0
17202 Dedicated admin connection support was established for listening remotely on port %d. 0 0
17203 SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to the System Requirements section in BOL for further information. 0 0
17204 %ls: Could not open file %ls for file number %d. OS error: %ls. 0 0
17207 %ls: Operating system error %ls occurred while creating or opening file '%ls'. Diagnose and correct the operating system error, and retry the operation. 0 0
17208 %s: File '%s' has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database from backup. 0 0
17253 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. 0 0
17255 Secondary TempDB file '%.*ls' resides on a removable drive and therefore will not be attached during startup. 0 0
17256 Secondary TempDB file '%.*ls' will not be attached during TempDB startup; Drive check failed with error '%ld'. 0 0
17257 System error while trying to initialize disk info; Error '%ld' 0 0
17258 No free space in the TempDB database 0 0
17300 SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes. 0 0
17303 The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services. 0 0
17308 %s: Process %d generated an access violation. SQL Server is terminating this process. 0 0
17310 A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory. 0 0
17311 SQL Server is terminating because of fatal exception %lx. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart). 0 0
17312 SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d). 0 0
17313 Unable to locate driver ntdll.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support this driver. 0 0
17401 Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required. 0 0
17403 Server resumed execution after being idle %d seconds. Reason: timer event. 0 0
17404 The server resumed execution after being idle for %d seconds. 0 0
17405 An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details. 0 0
17406 Server resumed execution after being idle %d seconds. Reason: resource pressure. 0 0
17550 DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required. 0 0
17551 DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required. 0 0
17557 DBCC DBRECOVER failed for database ID %d. Restore the database from a backup. 0 0
17558 Bypassing recovery for database ID %d. This is an informational message only. No user action is required. 0 0
17560 DBCC DBREPAIR: '%ls' index restored for '%ls.%ls'. 0 0
17561 %ls index restored for %ls.%ls. 0 0
17572 DBCC cannot free DLL '%ls'. SQL Server requires this DLL in order to function properly. 0 0
17573 CHECKDB for database '%ls' finished without errors on %ls (local time). This is an informational message only; no user action is required. 0 0
17657 Attempting to change default collation to %s. 0 0
17658 SQL Server started in single-user mode. This an informational message only. No user action is required. 0 0
17659 Warning: System table ID %d has been updated directly in database ID %d and cache coherence may not have been maintained. SQL Server should be restarted. 0 0
17660 Starting without recovery. This is an informational message only. No user action is required. 0 0
17661 Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required. 0 0
17663 Server name is '%s'. This is an informational message only. No user action is required. 0 0
17664 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. 0 0
17674 Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d. 0 0
17676 SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required. 0 0
17681 Loading default collation %s for this instance of SQL Server. 0 0
17750 Could not load the DLL %ls, or one of the DLLs it references. Reason: %ls. 0 0
17751 Could not find the function %ls in the library %ls. Reason: %ls. 0 0
17752 SQL Server has insufficient memory to run the extended stored procedure '%ls'. Release server memory resources by closing connections or ending transactions. 0 0
17753 %.*ls can only be executed in the master database. 0 0
17802 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 0 0
17803 There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls 0 0
17805 The value in the usertype field of the login record is invalid. The value 0x01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server.%.*ls 0 0
17806 SSPI handshake failed with error code 0x%x while establishing a connection with integrated security; the connection has been closed.%.*ls 0 0
17807 Event '%ld', which was received from the client, is not recognized by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent. 0 0
17809 Could not connect because the maximum number of '%ld' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.%.*ls 0 0
17810 Could not connect because the maximum number of '%ld' dedicated administrator connections already exists. Before a new connection can be made, the existing dedicated administrator connection must be dropped, either by logging off or ending the process.%.*ls 0 0
17812 Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required. 0 0
17813 The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls 0 0
17825 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. 0 0
17826 Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 0 0
17827 There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls 0 0
17828 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 0 0
17829 A network error occurred while establishing a connection; the connection has been closed.%.*ls 0 0
17830 Network error code 0x%x occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms, network writes %d ms, network reads %d ms, establishing SSL %d ms, negotiating SSPI %d ms, validating login %d ms, including user-defined login processing %d ms.%.*ls 0 0
17832 The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls 0 0
17835 Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library.%.*ls 0 0
17836 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 0 0
17881 '%ls' is an unsupported Open Data Services API. 0 0
17883 Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yielding on Scheduler %ld. Thread creation time: %I64d. Approx Thread CPU Used: kernel %I64d ms, user %I64d ms. Process Utilization %d%%. System Idle %d%%. Interval: %I64d ms. 0 0
17884 New queries assigned to process on Node %d have not been picked up by a worker thread in the last %d seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %d%%. System Idle: %d%%. 0 0
17885 An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure. 0 0
17886 The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor. 0 0
17887 IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d. 0 0
17888 All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%. 0 0
17889 A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls 0 0
17890 A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%. 0 0
17891 Resource Monitor (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Memory freed: %I64d KB. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d. 0 0
17892 Logon failed for login '%.*ls' due to trigger execution.%.*ls 0 0
17894 Dispatcher (0x%lx) from dispatcher pool '%.*ls' Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d. 0 0
26010 The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: % 0 0
26011 The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. 0 0
26012 The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support. 0 0
26013 The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption. 0 0
26014 Unable to load user-specified certificate [Cert Hash(sha1) "%hs"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. 0 0
26015 Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. 0 0
26017 Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 0 0
26018 A self-generated certificate was successfully loaded for encryption. 0 0
26022 Server is listening on [ %hs <%hs> %d]. 0 0
26023 Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp port is already in use. 0 0
26024 Server failed to listen on %hs <%hs> %d. Error: % 0 0
26025 HTTP authentication succeeded for user '%.*ls'.%.*ls 0 0
26026 HTTP authentication failed.%.*ls 0 0
26027 Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server. 0 0
26028 Server named pipe provider is ready to accept connection on [ %hs ]. 0 0
26029 Server named pipe provider failed to listen on [ %hs ]. Error: % 0 0
26030 Server shared memory provider is ready for clients to connect to [ %hs ]. 0 0
26031 Server shared memory provider failed to initialize. Error: % 0 0
26032 Server VIA provider is ready for clients to connect to [ %hs:%d ]. 0 0
26033 Server VIA provider failed to initialize. Error: % 0 0
26034 The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination. 0 0
26035 The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: % 0 0
26036 Server named pipe connections are restricted to local access only. This is an informational message only. No user action is required. 0 0
26037 The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: % 0 0
26038 The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: % 0 0
26039 The SQL Server Network Interface library was unable to load SPN related library. Error: % 0 0
26040 Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: % 0 0
26041 Server TCP provider has successfully reestablished listening on port [ %d ]. 0 0
26042 Server HTTP provider has stopped listening due to a failure. Error: % 0 0
26043 Server HTTP provider has successfully reestablished listening. 0 0
26044 Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: % 0 0
26045 Server named pipe provider has successfully reestablished listening on [ %hs ]. 0 0
26046 Server shared memory provider has stopped listening due to a failure. Error: % 0 0
26047 Server shared memory provider has successfully reestablished listening. 0 0
26048 Server local connection provider is ready to accept connection on [ %hs ]. 0 0
26049 Server local connection provider failed to listen on [ %hs ]. Error: % 0 0
26050 Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: % 0 0
26051 Server local connection provider has successfully re-established listening on [ %hs ]. 0 0
26052 SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is an informational message only. No user action is required. 0 0
26053 SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. There may be insufficient memory. Free up additional memory, then turn the node off and on again. If the failure persists repeat this multiple times or restart the SQL Server. 0 0
26054 Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: % 0 0
26055 The SQL Server failed to initialize VIA support library [%hs]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: % 0 0
26056 Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port through the SQL Server Browser Service. Error: % 0 0
26057 Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: % 0 0
26058 A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections. 0 0
26059 The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. 0 0
26060 The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. 0 0
26061 Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem with the network configuration of the computer. Error: % 0 0
26062 Invalid parameter detected while initializing TCP listening port. Error: % 0 0
12002 The requested %S_MSG index on column '%.*ls' of table '%.*ls' could not be created because the column type is not %S_MSG . Specify a column name that refers to a column with a %S_MSG data type. 0 0
12003 Could not find spatial tessellation scheme '%.*ls'. Specify a valid tessellation scheme name in your USING clause. 0 0
12004 Could not find the default spatial tessellation scheme for the column '%.*ls' on table '%.*ls'. Make sure that the column reference is correct, or specify the extension scheme in a USING clause. 0 0
12005 Incorrect parameters were passed to the CREATE %S_MSG statement near '%.*ls'. Validate the statement against the index-creation syntax. 0 0
12006 Duplicate parameters were passed to the create index statement. Validate the statement against the index-creation syntax. 0 0
12007 The CREATE %S_MSG statement is missing the required parameter '%.*ls'. Validate the statement against the index-creation syntax. 0 0
12008 Table '%.*ls' does not have a clustered primary key as required by the %S_MSG index. Make sure that the primary key column exists on the table before creating a %S_MSG index. 0 0
12009 Could not find the %S_MSG index '%.*ls' on table '%.*ls'. Either no %S_MSG index with this name exists, or a non-%S_MSG index might be using the same name. Fix the index name, avoiding duplicates. If a relational index has the same name, drop the regular relational index. 0 0
12010 Only one spatial index hint may appear per table, either as the first or the last hinted index. 0 0
12011 The value of parameter '%.*ls' of CREATE %S_MSG must be less than %d. 0 0
12012 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than %d. 0 0
12013 The value of parameter '%.*ls' of CREATE %S_MSG must be greater than the value of parameter '%.*ls'. 0 0
12014 The '%.*ls' parameter of CREATE %S_MSG is incompletely defined. If the parameter has more than one part, all the parts must be defined. 0 0
12015 The index option %.*ls in the CREATE %S_MSG statement has to appear before the general index options. 0 0
12016 Creating a %S_MSG index requires that the primary key in the base table satisfy the following restrictions. The maximum number of primary-key columns is %d. The maximum combined per-row size of the primary-key columns is %d bytes. The primary key on the base table '%.*ls' has %d columns, and contains %d bytes. Alter the base table to satisfy the primary-key restrictions imposed by the %S_MSG index. 0 0
12017 The spatial index is disabled or offline 0 0
12018 The spatial object is not defined in the scope of the predicate 0 0
12019 Spatial indexes do not support the comparand supplied in the predicate 0 0
12020 Spatial indexes do not support the comparator supplied in the predicate 0 0
12021 Spatial indexes do not support the method name supplied in the predicate 0 0
12022 The comparand references a column that is defined below the predicate 0 0
12023 The comparand in the comparison predicate is not deterministic 0 0
12024 The spatial parameter references a column that is defined below the predicate 0 0
12025 Could not find required binary spatial method in a condition 0 0
12026 Could not find required comparison predicate 0 0
12100 ALTER DATABASE failed because FILESTREAM filegroups cannot be added to a database that has either the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION option set to ON. To add FILESTREAM filegroups, you must set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF. 0 0
12980 Supply either %s or %s to identify the log entries. 0 0
12981 You must specify %s when creating a subplan. 0 0
12982 Supply either %s or %s to identify the plan or sub-plan to be run. 0 0
27001 Reserved error message. Should never be issued. 0 0
27002 A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection. 0 0
27003 Bad token encountered during tokenization. 0 0
27004 Unexpected token type encountered during tokenization. 0 0
27005 Error Tolerant Index is corrupt. 0 0
27006 Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt. 0 0
27007 Attempt to delete from empty ridlist. Error Tolerant Index is corrupt. 0 0
27008 rid to be deleted not found in rid-list. Error Tolerant Index is corrupt. 0 0
27009 Error Tolerant Index frequencies must be non-negative. Error Tolerant Index is corrupt. 0 0
27010 Attempt to insert row whose ID is already present. Error Tolerant Index is corrupt. 0 0
27011 No No ridlist provided for appending. Error Tolerant Index is corrupt. 0 0
27012 Cannot delete token. Error Tolerant Index is corrupt. 0 0
27013 Tokenizer object has no delimiter set. Error Tolerant Index is corrupt. 0 0
27014 Deletion failed because token does not occur in index. Error Tolerant Index is corrupt. 0 0
27015 Unexpected ridlist length. Error Tolerant Index is corrupt. 0 0
27016 Cannot connect to Error Tolerant Index. Bad or missing SqlCommand object. 0 0
27017 Failed to drop index on reference table copy. 0 0
27018 Could not retrieve metadata from Error Tolerant Index. The index is probably corrupt. 0 0
27019 Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt. 0 0
27022 An error specific to fuzzy lookup table maintenance has occurred. 0 0
27023 A system error occurred during execution of fuzzy lookup table maintenance. 0 0
27024 Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt. 0 0
27025 Argument is not a valid hex string. Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt. 0 0
27026 Negative count in Error Tolerant Index metadata. The index is probably corrupt. 0 0
27027 Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt. 0 0
27028 Invalid Error Tolerant Index metadata. The index is probably corrupt. 0 0
27029 Invalid Error Tolerant Index metadata version. 0 0
27030 Missing metadata. The Error Tolerant Index is probably corrupt. 0 0
27031 Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt. 0 0
27032 Error Tolerant Index Metadata string too long. Index is probably corrupt. 0 0
27033 Error Tolerant Index Metadata length limit exceeded. 0 0
27034 Unexpected end of Error Tolerant Index metadata. Index is probably corrupt. 0 0
27037 No No table name provided for Error Tolerant Index. The index is probably corrupt. 0 0
27038 No No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt. 0 0
27039 No No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt. 0 0
27040 No No Error Tolerant Index metadata string provided for initialization. Index is probably corrupt. 0 0
27041 No No Error Tolerant Index metadata provided for serialization. The index is probably corrupt. 0 0
27042 Could not lookup object_id. No object name provided. 0 0
27043 Could not lookup object_id. Null command object provided. 0 0
27044 Open connection required. Cannot query Error Tolerant Index. 0 0
27045 Cannot write to null output buffer. Could not update Error Tolerant Index. The index is probably corrupt. 0 0
27046 Output buffer provided is too small. Could not update Error Tolerant Index. The index is probably corrupt. 0 0
27047 The number of min-hash q-grams per token must be positive. 0 0
27048 Could not create index on reference table copy. 0 0
27049 Reference table (or internal copy) missing integer identity column. Error tolerant index is probably corrupt. 0 0
27050 The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps in sequence. 0 0
27051 Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted. 0 0
27052 Table maintenance insertion failed. 0 0
27053 A positive q-gram length is required for tokenization. 0 0
27054 Maintenance trigger already installed on this reference table. 0 0
27055 Missing extended property on maintenance trigger. 0 0
27056 Maintenance trigger name out of sync with Error Tolerant Index metadata. Index is probably corrupt. 0 0
27058 A SQL error occurred during execution of fuzzy lookup table maintenance. 0 0
27059 Could not lookup object_id. The reference table or maintenance trigger could not be found. 0 0
27060 The Error Tolerant Index table name provided is not a valid SQL identifier. 0 0
27061 The Error Tolerant Index table name provided refers to a missing table. Check sys.tables. 0 0
27062 An auxiliary Fuzzy Lookup table maintenance table is missing. 0 0
27063 An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed. 0 0
27064 The row deleted from the reference table could not be located in the reference table copy. 0 0
27065 Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt. 0 0
25002 The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is correct, and that the Publisher is enabled as a remote Publisher at the Distributor. 0 0
25003 Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database. 0 0
25005 It is invalid to drop the default constraint on the rowguid column that is used by merge replication. 0 0
25006 The new column cannot be added to article '%s' because it has more than %d replicated columns. 0 0
25007 Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the changes and synchronize the data. 0 0
25008 The merge replication views could not be regenerated after performing the data definition language (DDL) operation. 0 0
25009 Invalid value '%s' specified while executing sp_changemergearticle on article '%s' for the 'identityrangemanagementoption' property. 0 0
25010 The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle @publication, @article, "identityrangemanagementoption", "none" to disable merge identity management, which will also drop the constraint. 0 0
25012 Cannot add an identity column since the table is published for merge replication. 0 0
25013 Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than '90RTM'. Use sp_repladdcolumn or sp_repldropcolumn. 0 0
25014 sp_repladdcolumn does not allow adding columns of datatypes that are new to this release. 0 0
25015 Schema Changes and Bulk Inserts 0 0
25016 Prepare Dynamic Snapshot 0 0
25017 Failed to execute the command "%s" through xp_cmdshell. Detailed error information is returned in a result set. 0 0
25018 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. 0 0
25019 The logical record relationship between articles "%s" and "%s" cannot be added because at least one of the articles has a constraint with a CASCADE action defined. 0 0
25020 The article cannot be created on table '%s' because it has more than %d columns and column-level tracking is being used. Either reduce the number of columns in the table or change to row-level tracking. 0 0
25021 Replication stored procedure sp_MSupdategenhistory failed to update the generation '%s'. This generation will be retried in the next merge. 0 0
25022 The snapshot storage option (@snapshot_storage_option) must be 'file system', or 'database'. 0 0
25023 Stored procedures containing table-value parameters cannot be published as '[serializable] proc exec' articles. 0 0
25024 A snapshot storage option of 'database' is incompatible with the use of character mode bcp for snapshot generation. 0 0
25025 Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse columns. 0 0
25026 The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded. 0 0
25601 The extended event engine is out of memory. 0 0
25602 The %S_MSG, "%.*ls", encountered a configuration error during initialization. Object cannot be added to the event session. 0 0
25603 The %S_MSG, "%.*ls", could not be added. The maximum number of singleton targets has been reached. 0 0
25604 The extended event engine is disabled. 0 0
25605 The %S_MSG, "%.*ls", could not be added. The maximum number of packages has been reached. 0 0
25606 The extended event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information about possible related problems. 0 0
25607 The extended event engine has been disabled by startup options. Features that depend on extended events may fail to start. 0 0
25623 The %S_MSG name, "%.*ls", is invalid, or the object could not be found 0 0
25624 The constraints of %S_MSG name, "%.*ls", have been violated. The object does not support binding to actions or predicates. Event not added to event session. 0 0
25625 The %S_MSG, "%.*ls", already exists in the event session. Object cannot be added to the event session. 0 0
25629 For %S_MSG, "%.*ls", the customizable attribute, "%ls", does not exist. 0 0
25630 The predicate expression bound to %S_MSG ,"%.*ls", has mismatching types. 0 0
25631 The %S_MSG, "%.*ls", already exists. Choose a unique name for the event session. 0 0
25632 The specified buffer size is less than the minimum size. 0 0
25633 The buffer size specified exceeds the maximum size. 0 0
25634 The dispatch latency specified is below the minimum size. 0 0
25635 An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be added to a session, the session must have a maximum memory greater than 0. 0 0
25636 Source and comparator types of the predicate do not match. 0 0
25638 Event data exceeded allowed maximum. 0 0
25639 The %S_MSG, "%.*ls", exceeds the number of allowable bound actions. 0 0
25640 Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0. 0 0
25641 For %S_MSG, "%.*ls", the parameter "%ls" passed is invalid. %ls 0 0
25642 Mandatory customizable attributes are missing for %S_MSG, "%.*ls". 0 0
25643 The %S_MSG, "%.*ls", can not be added to an event session that specifies no event loss. 0 0
25644 The %S_MSG, "%.*ls", cannot be bound to the event session. 0 0
25646 The %S_MSG name, "%.*ls", is invalid. 0 0
25647 The %S_MSG, "%.*ls", could not be found. Ensure that the object exists and the name is spelled correctly. 0 0
25648 The %S_MSG, "%.*ls", could not be found. Ensure that the package exists and the name is spelled correctly. 0 0
25649 Two of the actions/predicates for %S_MSG, "%.*ls", can not coexist. Please remove one. 0 0
25650 For %S_MSG, "%.*ls" the customizable attribute, "%ls", was specified multiple times. 0 0
25651 For %S_MSG, "%.*ls", the value specified for customizable attribute, "%ls", did not match the expected type, "%ls". 0 0
25653 The %S_MSG, "%.*ls", does not exist in the event session. Object cannot be dropped from the event session. 0 0
25699 The extended event engine failed unexpectedly while performing an operation. 0 0
25701 Invalid event session name "%.*ls". Temporary event sessions are not allowed. 0 0
25702 The event session option, "%.*ls", is set more than once. Remove the duplicate session option and re-issue the statement. 0 0
25703 The event session option, "%.*ls", has an invalid value. Correct the value and re-issue the statement. 0 0
25704 The event session has already been stopped. 0 0
25705 The event session has already been started. 0 0
25706 The %S_MSG, "%.*ls", could not be found. 0 0
25707 Event session option "%.*ls" cannot be changed while the session is running. Stop the event session before changing this session option. 0 0
25708 The "%.*ls" specified exceeds the maximum allowed value. Specify a smaller configuration value. 0 0
25709 One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. 0 0
25710 Event session "%.*ls" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. 0 0
25711 Failed to parse an event predicate. 0 0
25712 An invalid comparison operator was specified for an event predicate. 0 0
25713 The value specified for %S_MSG, "%.*ls", %S_MSG, "%.*ls", is invalid. 0 0
25715 The predicate on event "%ls" is invalid. Operator '%ls' is not defined for type "%ls", %S_MSG: "%.*ls". 0 0
25716 The predicate on event, "%.*ls", exceeds the maximum length of %d characters. 0 0
25717 The operating system returned error %ls while reading from the file '%s'. 0 0
25718 The log file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it. 0 0
25719 Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query. 0 0
25720 'sys.fn_xe_file_target_read_file' is skipping records from "%.*ls" at offset %I64d. 0 0
25721 The metadata file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it. 0 0
25722 The offset %d is invalid for log file "%s". Specify an offset that exists in the log file and retry your query. 0 0
25723 An error occurred while obtaining metadata information from the file "%s". The file may be damaged. 0 0
25724 Predicate too large for display 0 0
25807 The %d KB buffer size specified is too low for the ETW target. Increase the size and retry your command. 0 0
25809 The log file path "%ls" to the ETW target is invalid. Verify that the path exists and that the SQL Server startup account has access to the log file. 0 0
25810 The session name specified exceeds the maximum length of %d characters. 0 0
25811 The operating system returned error 5 (ACCESS_DENIED) while creating an ETW tracing session. Ensure that the SQL Server startup account is a member of the 'Performance Log Users' group and then retry your command. 0 0
25812 The field '%ls' is invalid for the event '%ls'. Verify that the field exists and try your command again. 0 0
25813 The action "%ls" does not exist. Verify that the action exists and try your command again. 0 0
25814 The filtering event "%ls" does not exist. Verify that the event exists and try your command again. 0 0
25815 The source type, %d, is invalid. Valid types are 0 for event fields or 1 for actions. 0 0
25816 The slot count, %d, exceeds the maximum slot count size of %d. Reduce the slot count value and try your command again. 0 0
25817 The column or action name specified exceeds the maximum length of %d characters. 0 0
25818 The event "%ls" was not found. 0 0
25819 The column "%ls" was not found. 0 0
25820 The action "%ls" was not found. 0 0
25821 The number of begin and end columns must match. Specify the same number of columns for begin and end matching. 0 0
25822 The number of begin and end actions must match. Specify the same number of actions for begin and end matching. 0 0
25824 The begin and end columns at position %d are not of the same type. Specify matching columns that are the same type and try your command again. 0 0
25825 The begin and end action at postition %d are not of the same type. Specify matching actions that are the same type and try your command again. 0 0
25827 The operating system returned error %d while creating the file '%ls'. Verify that the path exists and that the SQL Server startup account has access to the location. 0 0
25833 Counter target could not add package "%ls" to the list of packages to count. Events from this package will not be counted. 0 0
25834 Ring Buffer target could not add package "%ls" to the package occurrence list. Events from this package will not be kept based on occurrence number. 0 0
18002 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. 0 0
18052 Error: %d, Severity: %d, State: %d. 0 0
18053 Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. 0 0
18054 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. 0 0
18055 Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support. 0 0
18056 The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. The failure ID is %d. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. 0 0
18057 Error: Failed to set up execution context. 0 0
18058 Failed to load format string for error %d, language id %d. Operating system error: %s. Check that the resource file matches SQL Server executable, and resource file in localized directory matches the file under English directory. Also check memory usage. 0 0
18059 The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online. 0 0
18060 Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the message. 0 0
18061 The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error message. 0 0
18100 Process ID %d was killed by hostname %.*ls, host process ID %d. 0 0
18113 SQL Server shutdown after verifying system indexes. 0 0
18124 The default collation was successfully changed. 0 0
18204 %s: Backup device '%s' failed to %s. Operating system error %s. 0 0
18210 %s: %s failure on backup device '%s'. Operating system error %s. 0 0
18225 Tape '%s' (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required 0 0
18226 Tape mount is being requested on drive '%s'. Expected volume has (Family ID %d, sequence %d). 0 0
18227 Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive '%s'. This is an informational message only. No user action required. 0 0
18228 Tape mount request on drive '%s' is cancelled. This is an informational message only. No user action is required. 0 0
18257 %s: Device or media does not support %s. To access this feature, use a different device or media. 0 0
18264 Database backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 0 0
18265 Log was backed up. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 0 0
18266 Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 0 0
18267 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. 0 0
18268 Log was restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 0 0
18269 Database file was restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 0 0
18270 Database differential changes were backed up. Database: %s, creation date(time): %s(%s), pages dumped: %I64d, first LSN: %s, last LSN: %s, full backup LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 0 0
18271 Database changes were restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 0 0
18272 During restore restart, an I/O error occurred on checkpoint file '%s' (operating system error %s). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file. 0 0
18273 Could not clear '%s' bitmap in database '%s' because of error %d. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the error occurred on a data backup, consider taking a data backup to create a new base for future differential backups. 0 0
18274 Tape '%s' was dismounted from drive '%s'. This is an informational message. No user action is required. 0 0
18275 Unnamed tape was dismounted from drive '%s'. This is an informational message. No user action is required. 0 0
18276 Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %I64d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required. 0 0
18277 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. 0 0
18300 Reason: Infrastructure error occurred. Check for previous errors. 0 0
18301 Reason: Could not find a login matching the name provided. 0 0
18302 Reason: Failed to unprotect memory containing sensitive information. 0 0
18303 Reason: Failed to unprotect memory containing sensitive information. 0 0
18304 Reason: Could not find a login matching the name provided. 0 0
18305 Reason: Attempting to use an NT account name with SQL Server Authentication. 0 0
18306 Reason: An error occurred while evaluating the password. 0 0
18307 Reason: Password did not match that for the login provided. 0 0
18308 Reason: Invalid password provided. 0 0
18309 Reason: Password validation failed with an infrastructure error. Check for previous errors. 0 0
18310 Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. 0 0
18311 Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. 0 0
18312 Reason: SQL Server service is paused. No new connections can be accepted at this time. 0 0
18313 Reason: Interface for login to SQL Server is not supported. 0 0
18314 Reason: Failed to open the specified database. 0 0
18315 Reason: Failed to open the database for this login. 0 0
18316 Reason: Unable to determine the initial language and date format. 0 0
18317 Reason: The user must change the password, but it cannot be changed with the current connection settings. 0 0
18318 Reason: Failed to unprotect memory containing sensitive information. 0 0
18319 Reason: Simulation of a failure while redoing login on the connection. 0 0
18320 Reason: SQL Server service is paused. Login could not be revalidated at this time. 0 0
18321 Reason: Reinitialization of security context failed while revalidating the login on the connection. 0 0
18322 Reason: Access to server validation failed while revalidating the login on the connection. 0 0
18323 Reason: Failed to open the specified database while revalidating the login on the connection. 0 0
18324 Reason: Failed to create the user instance while revalidating the login on the connection. 0 0
18325 Reason: Failed to attach the specified database while revalidating the login on the connection. 0 0
18326 Reason: Failed to open the database for this login while revalidating the login on the connection. 0 0
18327 Reason: Failed to determine the language and date format while revalidating the login on the connection. 0 0
18328 Reason: An exception was raised while revalidating the login on the connection. Check for previous errors. 0 0
18329 Reason: Simulation of a failure while reauthenticating login. 0 0
18330 Reason: SQL Server service is paused. Login cannot be reauthenticated at this time. 0 0
18331 Reason: Failed to reinitialize security context while reauthenticating login. 0 0
18332 Reason: Failed to access server for validation while reauthenticating login. 0 0
18333 Reason: Failed to open the specified database while reauthenticating login. 0 0
18334 Reason: An error occurred while reauthenticating login. Check for previous errors. 0 0
18335 Reason: Could not retrieve database name or map database to an item. 0 0
18336 Reason: Cannot connect with a login that does not specify a share. 0 0
18337 Reason: Failed to open the explicitly specified database. 0 0
18338 Reason: Unable to determine the database name from the specified file name. 0 0
18339 Reason: Failed to open the database specified in the login properties. 0 0
18340 Reason: Failed to store database name and collation. Check for previous errors. 0 0
18341 . Reason: Current collation did not match the database's collation during connection reset. 0 0
18342 Reason: Failed to send an environment change notification to a log shipping partner node. 0 0
18343 Reason: Failed to retrieve database name or map database to an item while revalidating the login on the connection. 0 0
18344 Reason: Connection with a login which does not specify a share is not allowed while revalidating the login on the connection. 0 0
18345 Reason: Failed to open the database configured in the login object while revalidating the login on the connection. 0 0
18346 Reason: Failed to determine database name from a given file name while revalidating the login on the connection. 0 0
18347 Reason: Failed to open the database specified in the login properties while revalidating the login on the connection. 0 0
18348 Reason: Failed to store database name and collation while revalidating the login on the connection. Check for previous errors. 0 0
18349 Reason: Current collation did not match the database's collation during connection reset. 0 0
18350 Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. 0 0
18351 Reason: Client impersonation failed. 0 0
18352 Reason: Failed to revert impersonation to self. 0 0
18353 Reason: Failed to get security token information. 0 0
18354 Reason: Failed to duplicate of security token. 0 0
18355 Reason: Failed attempted retry of a process token validation. 0 0
18356 Reason: An error occurred while attempting to change password. 0 0
18357 Reason: An attempt to login using SQL Server Authentication failed. Server is configured for Windows Authentication only. 0 0
18400 The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required. 0 0
18401 Login failed for user '%.*ls'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.%.*ls 0 0
18451 Login failed for user '%.*ls'. Only administrators may connect at this time.%.*ls 0 0
18452 Login failed. The login is from an untrusted domain and cannot be used with Windows Authentication.%.*ls 0 0
18453 Login succeeded for user '%.*ls'. Connection made using Windows Authentication.%.*ls 0 0
18454 Login succeeded for user '%.*ls'. Connection made using SQL Server Authentication.%.*ls 0 0
18455 Login succeeded for user '%.*ls'.%.*ls 0 0
18456 Login failed for user '%.*ls'.%.*ls%.*ls 0 0
18458 Login failed. The number of simultaneous users already equals the %d registered licenses for this server. To increase the maximum number of simultaneous users, obtain additional licenses and then register them through the Licensing item in Control Panel.%.*ls 0 0
18459 Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls 0 0
18460 Login failed. The number of simultaneous users has already reached the limit of %d licenses for this '%ls' server. Additional licenses should be obtained and installed or you should upgrade to a full version.%.*ls 0 0
18461 Login failed for user '%.*ls'. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls 0 0
18462 The login failed for user "%.*ls". The password change failed. The password for the user is too recent to change. %.*ls 0 0
18463 The login failed for user "%.*ls". The password change failed. The password cannot be used at this time. %.*ls 0 0
18464 Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is too short.%.*ls 0 0
18465 Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is too long.%.*ls 0 0
18466 Login failed for user '%.*ls'. Reason: Password change failed. The password does not meet Windows policy requirements because it is not complex enough.%.*ls 0 0
18467 The login failed for user "%.*ls". The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls 0 0
18468 The login failed for user "%.*ls". The password change failed. An unexpected error occurred during password validation. %.*ls 0 0
18469 [CLIENT: %.*hs] 0 0
18470 Login failed for user '%.*ls'. Reason: The account is disabled.%.*ls 0 0
18471 The login failed for user "%.*ls". The password change failed. The user does not have permission to change the password. %.*ls 0 0
18482 Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote server. Verify that you have specified the correct server name. %.*ls. 0 0
18483 Could not connect to server '%.*ls' because '%.*ls' is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls. 0 0
18485 Could not connect to server '%.*ls' because it is not configured to accept remote logins. Use the remote access configuration option to allow remote logins.%.*ls 0 0
18486 Login failed for user '%.*ls' because the account is currently locked out. The system administrator can unlock it. %.*ls 0 0
18487 Login failed for user '%.*ls'. Reason: The password of the account has expired.%.*ls 0 0
18488 Login failed for user '%.*ls'. Reason: The password of the account must be changed.%.*ls 0 0
18489 The dedicated administrator connection is in use by "%.*ls" on "%.*ls".%.*ls 0 0
18491 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. 0 0
18492 SQL Server cannot start because the license agreement for this '%ls' version of SQL Server is invalid. The server is exiting. To proceed, reinstall SQL Server with a valid license. 0 0
18493 The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls 0 0
18494 The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls 0 0
18495 The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls 0 0
18496 System Manufacturer: '%ls', System Model: '%ls'. 0 0
18596 %.*ls cannot start because your system is low on memory. 0 0
18597 Your %.*ls installation is either corrupt or has been tampered with (%hs). Please uninstall then re-run setup to correct this problem 0 0
18598 %.*ls could not find the default instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem. 0 0
18599 %.*ls could not find the specified named instance (%.*ls) - error %d. Please specify the name of an existing instance on the invocation of sqlservr.exe.\n\nIf you believe that your installation is corrupt or has been tampered with, uninstall then re-run setup to correct this problem. 0 0
18750 %ls: The parameter '%ls' is not valid. 0 0
18751 %ls procedure was called with the wrong number of parameters. 0 0
18752 Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure. 0 0
18755 Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations. 0 0
18756 Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent. 0 0
18757 Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication. 0 0
18760 Invalid %ls statement for article %d. Verify that the stored procedures that propagate changes to Subscribers use the appropriate call syntax, and then rerun the Log Reader Agent. Use sp_helparticle and sp_changearticle to view and change the call syntax. 0 0
18761 Commit record at {%08lx:%08lx:%04lx} has already been distributed. 0 0
18762 Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE. 0 0
18763 Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0). 0 0
18764 Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information. 0 0
18765 The "%s" log sequence number (LSN) that was specified for the replication log scan is invalid. 0 0
18766 The replbeginlsn field in the DBTABLE is invalid. 0 0
18767 The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}. 0 0
18768 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log {%08lx:%08lx:%04lx}. 0 0
18769 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record. 0 0
18770 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log. 0 0
18771 Invalid storage type %d specified writing variant of type %d. 0 0
18772 Invalid server data type (%d) specified in repl type lookup. 0 0
18773 Could not locate text information records for the column "%.*ls", ID %d during command construction. 0 0
18774 The stored procedure %s must be executed within a transaction. 0 0
18775 The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation. 0 0
18776 An error occurred while waiting on the article cache access event. 0 0
18777 %s: Error initializing MSMQ components 0 0
18778 %s: Error opening Microsoft Message Queue %s 0 0
18780 You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter. 0 0
18781 The value specified for the @backupdevicetype parameter is not valid. The value must be 'logical', 'disk', or 'tape'. 0 0
18782 Could not locate backup header information for database '%s' in the specified backup device. Specify a backup device that contains a backup of the Publisher database. 0 0
18783 The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to use a shorter path for this Publisher, and then retry the operation. 0 0
18784 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. 0 0
18786 The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, use sp_changepublication: set 'allow_initialize_from_backup' to 'true'. 0 0
18787 Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications. 0 0
18790 Cannot enable the option to initialize a subscription from a backup. This is not supported for non-SQL Server Publishers; it is only supported for transactional publications from SQL Server Publishers. 0 0
18795 The valid new types of a log based indexed view article are 'indexed view logbased', 'indexed view logbased manualfilter', 'indexed view logbased manualview', and 'indexed view logbased manualboth' only. 0 0
18796 The valid new types of a log based table article are 'logbased', 'logbased manualfilter', 'logbased manualview', and 'logbased manualboth' only. 0 0
18799 Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database. 0 0
18801 Unable to allocate memory for replication schema version node. 0 0
18802 Cannot insert a new schema change into the systranschemas system table. HRESULT = '0x%x'. If the problem persists, contact Customer Support Services. 0 0
18803 The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N'helptopics'. 0 0
18804 Peer-to-peer replication has been enabled, and the Log Reader Agent was unable to find an Extended-Originator-Record (EOR) for a transaction that did not originate at this server. Contact Customer Support Services. 0 0
18805 The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services. 0 0
18806 Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server. 0 0
18807 Cannot find an object ID for the replication system table '%s'. Verify that the system table exists and is accessible by querying it directly. If it does exist, stop and restart the Log Reader Agent; if it does not exist, drop and reconfigure replication. 0 0
18808 Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent. 0 0
18809 END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE. 0 0
18810 Cannot restart the scan on table '%s'. HRESULT = '0x%x'. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Services. 0 0
18811 Invalid %s log record. 0 0
18812 Can not lock the database object in article cache. 0 0
18815 Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services. 0 0
18817 Text information block not valid. Contact Customer Support Services. 0 0
18818 Failed to scan to log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 0 0
18819 Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 0 0
18821 The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services. 0 0
18823 Invalid value %d for %s. 0 0
18826 Failed to delete rows from the systranschemas table. HRESULT = '0x%x'. The rows will be deleted the next time replication executes the stored procedure sp_replcmds. 0 0
18827 The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %d transactions in the hash table, %d transactions processed, end of log LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services. 0 0
18828 Invalid filter procedure definition. 0 0
18829 Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 0 0
18830 A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, current BEGIN_UPDATE {%08lx:%08lx:%04lx}. Contact Customer Support Services. 0 0
18832 The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08lx:%08lx:%04lx}, current LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services. 0 0
18834 An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d). Contact Customer Support Services. 0 0
18835 Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d), text collection state %d. Contact product support. 0 0
18836 %s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %ld, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, offset %I64d, oldSize %I64d, newSize %I64d}. 0 0
18837 Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication. 0 0
18838 The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subscriptions to the publication. 0 0
18840 Cannot locate database information in the article cache. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, back up the publication database, and then contact Customer Support Services. 0 0
18842 Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication. 0 0
18843 Failed to allocate or reallocate buffer for replication command, old size %d, new size %d. 0 0
18844 Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication. 0 0
18845 Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication. 0 0
18846 Possible inconsistent state in the distribution database: dist_backup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute "sp_repldone NULL, NULL, 0, 0, 1", and then execute sp_replflush. Reinitialize all subscriptions to the publication. 0 0
18847 Cannot retrieve the peer-to-peer database information. Contact Customer Support Services. 0 0
18849 Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %d, rowsetId %I64d. Stop and restart the Log Reader Agent. If the problem persists, back up the publication database and then contact Customer Support Services. 0 0
18850 Unexpected %s log record encountered, last FILESTREAMInfo node processed : {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, {%08lx:%08lx:%04lx}} 0 0
18851 Failed to %s the replication context for TxF: {%I64d, %.*ls, %ld, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %I64d, %.*ls, {%08lx:%08lx:%04lx}}. If the problem persists, contact product support. 0 0
18852 Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%ld'. If the problem persists, contact Customer Support Services. 0 0
18853 Replication is skipping schema version logging because the systranschemas table is not present in database '%d'. This is an informational message only. No user action is required. 0 0
18854 One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error. 0 0
18855 Can not rename the database name because it is published or it is a distribution database used by replication. 0 0
18856 Agent '%s' is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details. 0 0
18857 The subscription to this publication is not active yet. No user action is required. 0 0
18896 Failed to compare delete and insert log record for column ID %ld with table ID %ld 0 0
15001 Object '%ls' does not exist or is not a valid object for this operation. 0 0
15002 The procedure '%s' cannot be executed within a transaction. 0 0
15003 Only members of the %s role can execute this stored procedure. 0 0
15004 Name cannot be NULL. 0 0
15005 Statistics for all tables have been updated. 0 0
15006 '%s' is not a valid name because it contains invalid characters. 0 0
15007 '%s' is not a valid login or you do not have permission. 0 0
15008 User '%s' does not exist in the current database. 0 0
15009 The object '%s' does not exist in database '%s' or is invalid for this operation. 0 0
15010 The database '%s' does not exist. Supply a valid database name. To see available databases, use sys.databases. 0 0
15011 Database option '%s' does not exist. Specify a valid database option. 0 0
15012 The device '%s' does not exist. Use sys.backup_devices to show available devices. 0 0
15013 Table '%s': No columns without statistics found. 0 0
15014 The role '%s' does not exist in the current database. 0 0
15015 The server '%s' does not exist. Use sp_helpserver to show available servers. 0 0
15016 The default '%s' does not exist. 0 0
15017 The rule '%s' does not exist. 0 0
15018 Table '%s': Creating statistics for the following columns: 0 0
15019 The extended stored procedure '%s' does not exist. 0 0
15020 Statistics have been created for the %d listed columns of the above tables. 0 0
15021 Invalid value given for parameter %s. Specify a valid parameter value. 0 0
15022 The specified user name is already aliased. 0 0
15023 User, group, or role '%s' already exists in the current database. 0 0
15025 The server principal '%s' already exists. 0 0
15026 Logical device '%s' already exists. 0 0
15028 The server '%s' already exists. 0 0
15032 The database '%s' already exists. Specify a unique database name. 0 0
15033 '%s' is not a valid official language name. 0 0
15034 The application role password must not be NULL. 0 0
15036 The data type '%s' does not exist or you do not have permission. 0 0
15040 User-defined error messages must have an ID greater than 50000. 0 0
15041 User-defined error messages must have a severity level between 1 and 25. 0 0
15042 The @with_log parameter is ignored for messages that are not us_english version. 0 0
15043 You must specify 'REPLACE' to overwrite an existing message. 0 0
15044 The type "%s" is an unknown backup device type. Use the type "disk" or "tape". 0 0
15045 The logical name cannot be NULL. 0 0
15046 The physical name cannot be NULL. 0 0
15048 Valid values of the database compatibility level are %d, %d, or %d. 0 0
15049 Cannot unbind from '%s'. Use ALTER TABLE DROP CONSTRAINT. 0 0
15050 Cannot bind default '%s'. The default must be created using the CREATE DEFAULT statement. 0 0
15051 Cannot rename the table because it is published for replication. 0 0
15053 Objects exist which are not owned by the database owner. 0 0
15054 The current compatibility level is %d. 0 0
15056 The suspect flag on the database "%s" is already reset. 0 0
15057 List of %s name contains spaces, which are not allowed. 0 0
15058 List of %s has too few names. 0 0
15059 List of %s has too many names. 0 0
15060 List of %s names contains name(s) which have '%s' non-alphabetic characters. 0 0
15061 The add device request was denied. A physical device named "%s" already exists. Only one backup device may refer to any physical device name. 0 0
15062 The guest user cannot be mapped to a login name. 0 0
15063 The login already has an account under a different user name. 0 0
15065 All user IDs have been assigned. 0 0
15066 A default-name mapping of a remote login from remote server '%s' already exists. 0 0
15068 A remote user '%s' already exists for remote server '%s'. 0 0
15069 One or more users are using the database. The requested operation cannot be completed. 0 0
15070 Object '%s' was successfully marked for recompilation. 0 0
15071 Usage: sp_addmessage ,, [, [,FALSE | TRUE [,REPLACE]]] 0 0
15072 Usage: sp_addremotelogin remoteserver [,loginname [,remotename]] 0 0
15074 Warning: You must recover this database prior to access. 0 0
15076 Default, table, and user data types must be in the current database. 0 0
15077 Rule, table, and user data type must be in the current database. 0 0
15078 The table or view must be in the current database. 0 0
15079 Queries processed: %d. 0 0
15080 Cannot use parameter %s for a Windows login. 0 0
15081 Membership of the public role cannot be changed. 0 0
15083 Physical data type '%s' does not accept a collation 0 0
15084 The column or user data type must be in the current database. 0 0
15085 Usage: sp_addtype name, 'data type' [,'NULL' | 'NOT NULL'] 0 0
15096 Could not find object '%ls' or you do not have required permission or the object is not valid for adding extended property. 0 0
15097 The size associated with an extended property cannot be more than 7,500 bytes. 0 0
15098 The name change cannot be performed because the SID of the new name does not match the old SID of the principal. 0 0
15099 The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is OFF. 0 0
15100 Usage: sp_bindefault defaultname, objectname [, 'futureonly'] 0 0
15101 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. 0 0
15102 Cannot bind a default to an identity column. 0 0
15103 Cannot bind a default to a column created with or altered to have a default value. 0 0
15104 You do not own a table named '%s' that has a column named '%s'. 0 0
15106 Usage: sp_bindrule rulename, objectname [, 'futureonly'] 0 0
15107 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. 0 0
15108 sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. Use CREATE TYPE for this purpose. 0 0
15109 Cannot change the owner of the master, model, tempdb or distribution database. 0 0
15110 The proposed new database owner is already a user or aliased in the database. 0 0
15112 The third parameter for table option 'text in row' is invalid. It should be 'on', 'off', '0', or a number from 24 through 7000. 0 0
15113 Too many failed login attempts. This account has been temporarily locked as a precaution against password guessing. A system administrator can unlock this login with the UNLOCK clause of ALTER LOGIN. 0 0
15114 Password validation failed. The password for the user is too recent to change. 0 0
15115 Password validation failed. The password cannot be used at this time. 0 0
15116 Password validation failed. The password does not meet Windows policy requirements because it is too short. 0 0
15117 Password validation failed. The password does not meet Windows policy requirements because it is too long. 0 0
15118 Password validation failed. The password does not meet Windows policy requirements because it is not complex enough. 0 0
15119 Password validation failed. The password does not meet the requirements of the password filter DLL. 0 0
15120 An unexpected error occurred during password validation. 0 0
15121 An error occurred during the execution of %ls. A call to '%ls' failed with error code: '%d'. 0 0
15122 The CHECK_EXPIRATION option cannot be used when CHECK_POLICY is OFF. 0 0
15123 The configuration option '%s' does not exist, or it may be an advanced option. 0 0
15124 The configuration option '%s' is not unique. 0 0
15125 Trigger '%s' is not a trigger for '%s'. 0 0
15127 Cannot set the default language to a language ID not defined in syslanguages. 0 0
15128 The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned OFF when MUST_CHANGE is ON. 0 0
15129 '%d' is not a valid value for configuration option '%s'. 0 0
15130 There already exists a '%s' trigger for '%s'. 0 0
15131 Usage: sp_dbremove [,dropdev] 0 0
15133 INSTEAD OF trigger '%s' cannot be associated with an order. 0 0
15134 No No alias exists for the specified user. 0 0
15135 Object is invalid. Extended properties are not permitted on '%s', or the object does not exist. 0 0
15136 The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped. 0 0
15137 An error occurred during the execution of sp_xp_cmdshell_proxy_account. Possible reasons: the provided account was invalid or the '%.*ls' credential could not be created. Error code: '%d'. 0 0
15138 The database principal owns a %S_MSG in the database, and cannot be dropped. 0 0
15141 The server principal owns one or more %S_MSG(s) and cannot be dropped. 0 0
15143 '%s' is not a valid option for the @updateusage parameter. Enter either 'true' or 'false'. 0 0
15144 The role has members. It must be empty before it can be dropped. 0 0
15145 An implicit %S_MSG creation has failed. Reason: The %S_MSG may have been dropped or its name may already be in use. 0 0
15146 An encryption password must be provided to encrypt the private key of this %S_MSG. 0 0
15147 No No decryption password should be provided because the private key of this %S_MSG is encrypted by a master key. 0 0
15148 The data type or table column '%s' does not exist or you do not have permission. 0 0
15149 Principal doesn't exist or doesn't have sufficient privileges. 0 0
15150 Cannot %S_MSG the %S_MSG '%.*ls'. 0 0
15151 Cannot %S_MSG the %S_MSG '%.*ls', because it does not exist or you do not have permission. 0 0
15152 Cannot update user instances. Reason: %ls. Error code: 0x%x. 0 0
15153 The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '%.*ls' credential exists and contains valid information. 0 0
15154 The database principal owns an %S_MSG and cannot be dropped. 0 0
15155 The server principal owns a %S_MSG and cannot be dropped. 0 0
15156 The password that you specified is too long. The password should have no more than %d characters. 0 0
15157 Setuser failed because of one of the following reasons: the database principal '%.*ls' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission. 0 0
15158 Cannot initialize security. 0 0
15159 Maximum impersonation nesting level exceeded (limit %d).. 0 0
15160 Cannot issue impersonation token from non-primary impersonation context or for non-Windows user. 0 0
15161 Cannot set application role '%.*ls' because it does not exist or the password is incorrect. 0 0
15162 Unexpected error while creating impersonation token. 0 0
15163 Invalid timeout value. Valid timeout is between 1 and 7200 sec. 0 0
15164 '%.*ls' is not a valid login or cannot be issued impersonation token. 0 0
15165 Could not find object '%ls' or you do not have permission. 0 0
15166 Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored. 0 0
15167 Cannot generate GUID. 0 0
15168 Cannot rename the view '%s' and its columns and indexes because it is a system generated view that was created for optimization purposes. 0 0
15169 The server option "%ls" is not available in this edition of SQL Server. 0 0
15170 This login is the owner of %ld job(s). You must delete or reassign these jobs before the login can be dropped. 0 0
15171 Cannot use the parameter "%s" for a certificate or asymmetric key login. 0 0
15172 FallBack certificate must be created or dropped in master database in single user mode. 0 0
15173 Login '%s' has granted one or more permission(s). Revoke the permission(s) before dropping the login. 0 0
15174 Login '%s' owns one or more database(s). Change the owner of the database(s) before dropping the login. 0 0
15175 Login '%s' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login. 0 0
15176 The only valid @parameter value is 'WITH_LOG'. 0 0
15177 Usage: sp_dropmessage [, | 'ALL'] 0 0
15178 Cannot drop or alter a message with an ID less than 50,000. 0 0
15179 The message number %u or specified language version does not exist. 0 0
15182 Cannot disable access to the guest user in master or tempdb. 0 0
15183 The database principal owns objects in the database and cannot be dropped. 0 0
15184 The database principal owns data types in the database and cannot be dropped. 0 0
15185 There is no remote user '%s' mapped to local user '%s' from the remote server '%s'. 0 0
15186 The server principal is set as the execution context of a trigger or event notification and cannot be dropped. 0 0
15187 The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s). 0 0
15188 Cannot create an index that does not include all security columns. 0 0
15189 Cannot have more than one security column for a table. 0 0
15190 There are still remote logins or linked logins for the server '%s'. 0 0
15192 Cannot alter or drop the security column of a table. 0 0
15195 The MUST_CHANGE option is not supported by this version of Microsoft Windows. 0 0
15196 The current security context is non-revertible. The "Revert" statement failed. 0 0
15197 There is no text for object '%s'. 0 0
15198 The name supplied (%s) is not a user, role, or aliased login. 0 0
15199 The current security context cannot be reverted. Please switch to the original database where '%ls' was called and try it again. 0 0
15200 There are no remote servers defined. 0 0
15201 There are no remote logins for the remote server '%s'. 0 0
15202 There are no remote logins defined. 0 0
15203 There are no remote logins for '%s'. 0 0
15204 There are no remote logins for '%s' on remote server '%s'. 0 0
15205 There are no servers defined. 0 0
15206 Invalid Remote Server Option: '%s'. 0 0
15207 The trusted option in remote login mapping is no longer supported. 0 0
15208 The certificate, asymmetric key, or private key file does not exist or has invalid format. 0 0
15209 An error occurred during encryption. 0 0
15212 Invalid certificate subject. The certificate subject must have between 1 and %d characters. 0 0
15213 Warning: The certificate you created has an invalid validity period; its expiration date precedes its start date. 0 0
15214 Warning: The certificate you created is expired. 0 0
15215 Warning: The certificate you created is not yet valid; its start date is in the future. 0 0
15216 '%s' is not a valid option for the @delfile parameter. 0 0
15217 Property cannot be updated or deleted. Property '%.*ls' does not exist for '%.*ls'. 0 0
15218 Object '%s' is not a table. 0 0
15219 Cannot change the owner of an indexed view. 0 0
15222 Remote login option '%s' is not unique. 0 0
15223 Error: The input parameter '%s' is not allowed to be null. 0 0
15224 Error: The value for the @newname parameter contains invalid characters or violates a basic restriction (%s). 0 0
15225 No No item by the name of '%s' could be found in the current database '%s', given that @itemtype was input as '%s'. 0 0
15226 Cannot create CLR types from an XML datatype. 0 0
15227 The database '%s' cannot be renamed. 0 0
15229 The argument specified for the "%.*ls" parameter of stored procedure sp_db_vardecimal_storage_format is not valid. Valid arguments are 'ON' or 'OFF'. 0 0
15230 Error starting user instance. Error code: %d. 0 0
15232 A certificate with name '%s' already exists or this certificate already has been added to the database. 0 0
15233 Property cannot be added. Property '%.*ls' already exists for '%.*ls'. 0 0
15234 Objects of this type have no space allocated. 0 0
15236 Column '%s' has no default. 0 0
15237 User data type '%s' has no default. 0 0
15238 Column '%s' has no rule. 0 0
15239 User data type '%s' has no rule. 0 0
15240 Cannot write into file '%s'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist. 0 0
15241 Usage: sp_dboption [dbname [,optname [,'true' | 'false']]] 0 0
15242 Database option '%s' is not unique. 0 0
15243 The option '%s' cannot be changed for the master database. 0 0
15244 Only members of the sysadmin role or the database owner may set database options. 0 0
15246 Cannot dump the private key of certificate '%s' because the private key cannot be found. 0 0
15247 User does not have permission to perform this action. 0 0
15248 Either the parameter @objname is ambiguous or the claimed @objtype (%s) is wrong. 0 0
15249 Error: Explicit @objtype '%s' is unrecognized. 0 0
15250 The database name component of the object qualifier must be the name of the current database. 0 0
15251 Invalid '%s' specified. It must be %s. 0 0
15252 The primary or foreign key table name must be given. 0 0
15253 Syntax error parsing SQL identifier '%s'. 0 0
15254 Users other than the database owner or guest exist in the database. Drop them before removing the database. 0 0
15255 '%s' is not a valid value for @autofix. The only valid value is 'auto'. 0 0
15256 Usage: sp_certify_removable [,'auto'] 0 0
15257 The database that you are attempting to certify cannot be in use at the same time. 0 0
15258 The database must be owned by a member of the sysadmin role before it can be removed. 0 0
15259 The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys. 0 0
15260 The format of the security descriptor string '%s' is invalid. 0 0
15261 Usage: sp_create_removable ,,,,,,,,, [,,,...,,] 0 0
15262 Invalid file size entered. All files must be at least 1 MB. 0 0
15263 A SID in the security descriptor string '%s' could not be found in an account lookup operation. 0 0
15264 Could not create the '%s' portion of the database. 0 0
15265 An unexpected error has occurred in the processing of the security descriptor string '%s'. 0 0
15266 Cannot make '%s' database removable. 0 0
15267 A security descriptor with name '%s' already exists. 0 0
15268 Authentication mode is %s. 0 0
15269 Logical data device '%s' not created. 0 0
15271 Invalid @with_log parameter value. Valid values are 'true' or 'false'. 0 0
15272 The %s '%.*s' is not trusted to execute. 0 0
15273 The decryption key is incorrect. 0 0
15274 Access to the remote server is denied because the current security context is not trusted. 0 0
15276 Cannot provision master key passwords for system databases. 0 0
15277 The only valid @parameter_value values are 'true' or 'false'. 0 0
15278 Login '%s' is already mapped to user '%s' in database '%s'. 0 0
15279 You must add the us_english version of this message before you can add the '%s' version. 0 0
15280 All localized versions of this message must be dropped before the us_english version can be dropped. 0 0
15281 SQL Server blocked access to %S_MSG '%ls' of component '%.*ls' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of '%.*ls' by using sp_configure. For more information about enabling '%.*ls', see "Surface Area Configuration" in SQL Server Books Online. 0 0
15282 A key with name '%.*ls' or user defined unique identifier already exists or you do not have permissions to create it. 0 0
15283 The name '%s' contains too many characters. 0 0
15284 The database principal has granted or denied permissions to objects in the database and cannot be dropped. 0 0
15285 The special word '%s' cannot be used for a logical device name. 0 0
15286 Terminating this procedure. The @action '%s' is unrecognized. Try 'REPORT', 'UPDATE_ONE', or 'AUTO_FIX'. 0 0
15287 Terminating this procedure. '%s' is a forbidden value for the login name parameter in this procedure. 0 0
15288 Please specify one decryptor to decrypt a key. 0 0
15289 Terminating this procedure. Cannot have an open transaction when this is run. 0 0
15291 Terminating this procedure. The %s name '%s' is absent or invalid. 0 0
15292 The row for user '%s' will be fixed by updating its login link to a login already in existence. 0 0
15293 Barring a conflict, the row for user '%s' will be fixed by updating its link to a new login. 0 0
15294 The number of orphaned users fixed by adding new logins and then updating users was %d. 0 0
15295 The number of orphaned users fixed by updating users was %d. 0 0
15296 General cryptographic failure. 0 0
15297 The certificate, asymmetric key, or private key data is invalid. 0 0
15299 The signature of the public key is invalid. 0 0
15300 No No recognized letter is contained in the parameter value for General Permission Type (%s). Valid letters are in this set: %s . 0 0
15301 Collation '%s' is supported for Unicode data types only and cannot be set at either the database or server level. 0 0
15302 Database_Name should not be used to qualify owner.object for the parameter into this procedure. 0 0
15303 The "user options" config value (%d) was rejected because it would set incompatible options. 0 0
15304 The severity level of the '%s' version of this message must be the same as the severity level (%ld) of the us_english version. 0 0
15305 The @TriggerType parameter value must be 'insert', 'update', or 'delete'. 0 0
15306 Cannot change the compatibility level of replicated or distributed databases. 0 0
15307 Could not change the merge publish option because the server is not set up for replication. 0 0
15309 Cannot alter the trustworthy state of the model or tempdb databases. 0 0
15310 Failed to configure user instance on startup. Error updating server metadata. 0 0
15311 The file named '%s' does not exist. 0 0
15312 The file named '%s' is a primary file and cannot be removed. 0 0
15313 The key is not encrypted using the specified decryptor. 0 0
15314 Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of Windows. 0 0
15315 The key '%.*ls' is not open. Please open the key before using it. 0 0
15316 Global temporary keys are not allowed. You can only use local temporary keys. 0 0
15317 The master key file does not exist or has invalid format. 0 0
15318 All fragments for database '%s' on device '%s' are now dedicated for log usage only. 0 0
15319 Error: DBCC DBREPAIR REMAP failed for database '%s' (device '%s'). 0 0
15320 An error occurred while decrypting %S_MSG '%.*ls' that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation, but data that cannot be decrypted by the old master key will become unavailable. 0 0
15321 There was some problem removing '%s' from sys.master_files. 0 0
15322 File '%s' was removed from tempdb, and will take effect upon server restart. 0 0
15323 The selected index does not exist on table '%s'. 0 0
15324 The option %s cannot be changed for the '%s' database. 0 0
15325 The current database does not contain a %s named '%ls'. 0 0
15326 No No extended stored procedures exist. 0 0
15327 The database is now offline. 0 0
15328 The database is offline already. 0 0
15329 The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session before performing this operation. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost. 0 0
15330 There are no matching rows on which to report. 0 0
15331 The user '%s' cannot take the action auto_fix due to duplicate SID. 0 0
15332 The private key is already set for this file. To change it you should drop and re-create the certificate. 0 0
15333 Error: The qualified @oldname references a database (%s) other than the current database. 0 0
15334 The %S_MSG has a private key that is protected by a user defined password. That password needs to be provided to enable the use of the private key. 0 0
15335 Error: The new name '%s' is already in use as a %s name and would cause a duplicate that is not permitted. 0 0
15336 Object '%s' cannot be renamed because the object participates in enforced dependencies. 0 0
15337 Caution: sys.sql_dependencies shows that other objects (views, procedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly. 0 0
15339 Creating '%s'. 0 0
15342 There is no private key provisioned for %S_MSG '%.*ls'. 0 0
15343 The username and/or password passed in is invalid or the current process does not have sufficient privileges. 0 0
15344 Ownership change for %S_MSG is not supported. 0 0
15345 An entity of type %S_MSG cannot be owned by a role, a group, or by principals mapped to certificates or asymmetric keys. 0 0
15346 Cannot change owner for an object that is owned by a parent object. Change the owner of the parent object instead. 0 0
15347 Cannot transfer an object that is owned by a parent object. 0 0
15348 Cannot transfer a schemabound object. 0 0
15349 Cannot transfer an MS Shipped object. 0 0
15350 An attempt to attach an auto-named database for file %.*ls failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. 0 0
15351 The CLR procedure/function/type being signed refers to an assembly that is not signed either by a strong name or an assembly. 0 0
15352 The %S_MSG cannot be dropped because one or more entities are either signed or encrypted using it. 0 0
15353 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. 0 0
15354 Usage: sp_detach_db , [TRUE|FALSE], [TRUE|FALSE] 0 0
15356 The current application role has been dropped. The current security context contains no valid database user context. 0 0
15357 The current security context was set by "%ls". It cannot be reverted by statement "%ls". 0 0
15358 User-defined filegroups should be made read-only. 0 0
15359 Cannot add functional unit '%.*ls' to component '%.*ls'. This unit has been already registered with the component. 0 0
15360 An error occurred while trying to load the xpstar dll to read the agent proxy account from LSA. 0 0
15361 An error occurred while trying to read the SQLAgent proxy account credentials from the LSA. 0 0
15362 An error occurred while trying to create the '%.*ls' credential. 0 0
15364 Failed to generate a user instance of SQL Server. Only an integrated connection can generate a user instance. The connection will be closed.%.*ls 0 0
15365 Failed to generate a user instance of SQL Server. Only members of Builtin\Users can generate a user instance. The connection will be closed.%.*ls 0 0
15366 Failed to generate a user instance of SQL Server due to low memory. The connection will be closed.%.*ls 0 0
15367 Failed to generate a user instance of SQL Server due to a failure in generating a unique user instance name. The connection will be closed.%.*ls 0 0
15368 Failed to generate a user instance of SQL Server due to a failure in reading registry keys. The connection will be closed.%.*ls 0 0
15369 Failed to generate a user instance of SQL Server due to a failure in impersonating the client. The connection will be closed.%.*ls 0 0
15370 Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.%.*ls 0 0
15371 Failed to generate a user instance of SQL Server due to a failure in creating user instance event. The connection will be closed.%.*ls 0 0
15372 Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.%.*ls 0 0
15373 Failed to generate a user instance of SQL Server due to a failure in obtaining the user instance's process information. The connection will be closed.%.*ls 0 0
15374 Failed to generate a user instance of SQL Server due to a failure in persisting the user instance information into system catalog. The connection will be closed.%.*ls 0 0
15375 Failed to generate a user instance of SQL Server due to a failure in making a connection to the user instance. The connection will be closed.%.*ls 0 0
15376 Failed to generate a user instance of SQL Server. Only the SQL Server Express version lets you generate a user instance. The connection will be closed.%.*ls 0 0
15377 Failed to configure user instance on startup. Error adding user to sysadmin role. 0 0
15378 Failed to configure user instance on startup. Error configuring system database entries in MASTER DB. 0 0
15380 Failed to configure user instance on startup. Error configuring system database paths in MASTER DB. 0 0
15381 Failed to generate a user instance of SQL Server due to a failure in updating security descriptor on the process of the user instance. 0 0
15382 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 0 0
15383 Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.%.*ls 0 0
15384 Failed to configure user instance on startup. Error updating Resource Manager ID. 0 0
15385 No No database principal is defined for sid '%.*ls'. 0 0
15386 Another batch in the session is changing security context, new batch is not allowed to start. 0 0
15387 If the qualified object name specifies a database, that database must be the current database. 0 0
15388 There is no user table matching the input name '%s' in the current database or you do not have permission to access the table. 0 0
15389 sp_indexoption is not supported for XML or spatial indexes. Use ALTER INDEX instead. 0 0
15390 Input name '%s' does not have a matching user table or indexed view in the current database. 0 0
15391 sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option for ALL the indexes. 0 0
15392 The specified option '%s' is not supported by this edition of SQL Server and cannot be changed using sp_configure. 0 0
15393 An error occurred while decrypting the password for linked login '%.*ls' that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost. 0 0
15394 Collation '%s' is not supported by the operating system 0 0
15395 The qualified old name could not be found for item type '%s'. 0 0
15396 An asymmetric key with name '%s' already exists or this asymmetric key already has been added to the database. 0 0
15397 The %S_MSG is not protected by a password. A decryption password cannot be used for this operation. 0 0
15398 Only objects in the master database owned by dbo can have the startup setting changed. 0 0
15399 Could not change startup option because this option is restricted to objects that have no parameters. 0 0
15401 Windows NT user or group '%s' not found. Check the name again. 0 0
15402 '%s' is not a fixed server role. 0 0
15403 The server principal "%.*ls" does not exist, does not have server access, or you do not have permission. 0 0
15404 Could not obtain information about Windows NT group/user '%ls', error code % 0 0
15405 Cannot use the special principal '%s'. 0 0
15406 Cannot execute as the server principal because the principal "%.*ls" does not exist, this type of principal cannot be impersonated, or you do not have permission. 0 0
15407 '%s' is not a valid Windows NT name. Give the complete name: . 0 0
15408 %ls cannot be called in this batch because a simultaneous batch has called it. 0 0
15409 '%s' is not a role. 0 0
15410 User or role '%s' does not exist in this database. 0 0
15411 Database principal or schema '%s' does not exist in this database. 0 0
15412 '%s' is not a known fixed role. 0 0
15413 Cannot make a role a member of itself. 0 0
15414 Cannot set compatibility level because database has a view or computed column that is indexed. These indexes require a SQL Server compatible database. 0 0
15416 Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]] 0 0
15418 Only members of the sysadmin role or the database owner may set the database compatibility level. 0 0
15419 Supplied parameter sid should be binary(16). 0 0
15420 The group '%s' does not exist in this database. 0 0
15421 The database principal owns a database role and cannot be dropped. 0 0
15422 Application roles can only be activated at the ad hoc level. 0 0
15425 No No server principal is defined for sid '%.*ls'. 0 0
15426 You must specify a provider name with this set of properties. 0 0
15427 You must specify a provider name for unknown product '%ls'. 0 0
15428 You cannot specify a provider or any properties for product '%ls'. 0 0
15429 '%ls' is an invalid product name. 0 0
15431 You must specify the @rolename parameter. 0 0
15432 Stored procedure '%s' can only be executed at the ad hoc level. 0 0
15433 Supplied parameter sid is in use. 0 0
15434 Could not drop login '%s' as the user is currently logged in. 0 0
15435 Database successfully published. 0 0
15436 Database successfully enabled for subscriptions. 0 0
15437 Database successfully published using merge replication. 0 0
15438 Database is already online. 0 0
15439 Database is now online. 0 0
15440 Database is no longer published. 0 0
15441 Database is no longer enabled for subscriptions. 0 0
15442 Database is no longer enabled for merge publications. 0 0
15443 Checkpointing database that was changed. 0 0
15448 Encryption by the machine key cannot be added to the service master key because the service master key cannot be decrypted or does not exist. 0 0
15450 New language inserted. 0 0
15451 Dropping an encryption from the service master key failed. No encryption by the machine key exists. 0 0
15452 No No alternate languages are available. 0 0
15453 us_english is always available, even though it is not in syslanguages. 0 0
15454 Language deleted. 0 0
15455 Adding an encryption to the service master key failed. An encryption by the machine key already exists. 0 0
15457 Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE statement to install. 0 0
15458 Database removed. 0 0
15459 In the current database, the specified object references the following: 0 0
15460 In the current database, the specified object is referenced by the following: 0 0
15461 Object does not reference any object, and no objects reference it. 0 0
15462 File '%s' closed. 0 0
15463 Device dropped. 0 0
15464 Unsupported private key format or key length. 0 0
15465 The private key password is invalid. 0 0
15466 An error occurred during decryption. 0 0
15468 An error occurred during the generation of the %S_MSG. 0 0
15469 No No constraints are defined on object '%ls', or you do not have permissions. 0 0
15470 No No foreign keys reference table '%ls', or you do not have permissions on referencing tables. 0 0
15471 The text for object '%ls' is encrypted. 0 0
15472 The object '%ls' does not have any indexes, or you do not have permissions. 0 0
15474 Invalid private key. The private key does not match the public key of the %S_MSG. 0 0
15475 The database is renamed and in single user mode. 0 0
15477 Caution: Changing any part of an object name could break scripts and stored procedures. 0 0
15482 Cannot change the owner of a table that has an indexed view. 0 0
15490 The dependent aliases were also dropped. 0 0
15497 Could not add login using sp_addlogin (user = %s). Terminating this procedure. 0 0
15499 The dependent aliases were mapped to the new database owner. 0 0
15500 The dependent aliases were dropped. 0 0
15502 Setting database owner to SA. 0 0
15503 Giving ownership of all objects to the database owner. 0 0
15504 Deleting users except guest and the database owner from the system catalog. 0 0
15505 Cannot change owner of object '%ls' or one of its child objects because the new owner '%ls' already has an object with the same name. 0 0
15506 An error occurred while signing. 0 0
15507 A key required by this operation appears to be corrupted. 0 0
15508 An error occurred while generating a key required by this operation. 0 0
15509 The password cannot be dropped because another database may be using it. 0 0
15510 Cannot enable a login that has an empty password. 0 0
15511 Default bound to column. 0 0
15512 Default bound to data type. 0 0
15513 The new default has been bound to columns(s) of the specified user data type. 0 0
15514 Rule bound to table column. 0 0
15515 Rule bound to data type. 0 0
15516 The new rule has been bound to column(s) of the specified user data type. 0 0
15517 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. 0 0
15518 Cannot execute as the Windows token. It is not valid, or you do not have permission. 0 0
15519 Default unbound from table column. 0 0
15520 Default unbound from data type. 0 0
15521 Columns of the specified user data type had their defaults unbound. 0 0
15522 Rule unbound from table column. 0 0
15523 Rule unbound from data type. 0 0
15524 Columns of the specified user data type had their rules unbound. 0 0
15525 sp_checknames is used to search for non 7-bit ASCII characters. 0 0
15526 in several important columns of system tables. The following 0 0
15527 columns are searched: 0 0
15528 In master: 0 0
15529 Cannot execute as the ticket. It is not valid, or you do not have permission. 0 0
15530 The %S_MSG with name "%.*ls" already exists. 0 0
15531 The security descriptor information is not valid. 0 0
15532 The security descriptor is invalid because it does not contain information about its owner or about its primary group. 0 0
15533 Invalid data type is supplied in the '%ls' statement. 0 0
15534 Cookie generation failed in the '%ls' statement. 0 0
15535 Cannot set a credential for principal '%.*ls'. 0 0
15536 In all databases: 0 0
15537 Login '%.*ls' does not have access to server. 0 0
15538 Login '%.*ls' does not have access to database. 0 0
15539 User '%s' cannot be dropped, it can only be disabled. The user is already disabled in the current database. 0 0
15540 The identity string is too long. The identity string should contain no more than %d characters. 0 0
15541 Cannot drop the credential '%.*ls' because it is used by a server principal. 0 0
15542 Cannot create a key without specifying an encryptor. 0 0
15556 Cannot decrypt or encrypt using the specified %S_MSG, either because it has no private key or because the password provided for the private key is incorrect. 0 0
15557 There is already a %S_MSG by %S_MSG '%.*ls'. 0 0
15558 Cannot drop %S_MSG by %S_MSG '%.*s'. 0 0
15559 Cannot drop %S_MSG '%.*ls' because there is a %S_MSG mapped to it. 0 0
15560 Cannot add or drop a signature on '%.*ls' because only modules can be signed. 0 0
15561 Signatures based on certificates or asymmetric keys are the only options supported in this version of the product. 0 0
15562 The module being executed is not trusted. Either the owner of the database of the module needs to be granted authenticate permission, or the module needs to be digitally signed. 0 0
15563 The %S_MSG has no private key set for it. 0 0
15574 This object does not have any statistics. 0 0
15575 This object does not have any statistics or indexes. 0 0
15576 You cannot set network name on server '%ls' because it is not a linked SQL Server. 0 0
15577 Warning: A linked server that refers to the originating server is not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias. 0 0
15578 There is already a master key in the database. Please drop it before performing this statement. 0 0
15579 Adding an encryption to the symmetric key failed. An encryption by the same %S_MSG '%.*s' may already exist. 0 0
15580 Cannot drop %S_MSG because %S_MSG '%.*s' is encrypted by it. 0 0
15581 Please create a master key in the database or open the master key in the session before performing this operation. 0 0
15583 The module being signed is marked to execute as owner. If the owner changes the signature will not be valid. 0 0
15584 An error occurred while decrypting %S_MSG '%.*ls' that was encrypted by the old master key. The error was ignored because the FORCE option was specified. 0 0
15585 The current master key cannot be decrypted. The error was ignored because the FORCE option was specified. 0 0
15586 Error in synchronizing system certificates between master and resource database. 0 0
15587 Cannot change owner of Assembly '%.*ls' since dependent assembly '%.*ls' is not owned by the new owner. 0 0
15588 The old and new master keys are identical. No data re-encryption is required. 0 0
15589 Cannot revert the current security context because the cookie is invalid. 0 0
15590 Can only use the 'No Revert' or 'Cookie' options with the 'Execute As' statement at the adhoc level. 0 0
15591 The current security context cannot be reverted using this statement. A cookie may or may not be needed with 'Revert' statement depending on how the context was set with 'Execute As' statement. 0 0
15592 Cannot unset application role because none was set or the cookie is invalid. 0 0
15593 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. 0 0
15594 The password is already provisioned for the database '%.*ls' 0 0
15595 The password cannot be dropped because it is not provisioned for the database '%.*ls' 0 0
15596 Warning: use of a UNIQUE index, PRIMARY KEY constraint, or UNIQUE constraint on a table with row-level security can allow information disclosure. 0 0
15597 Warning: use of an IDENTITY column on a table with row-level security can allow information disclosure. 0 0
15598 Warning: use of an indexed view on a table with row-level security can allow information disclosure. 0 0
15599 Warning: use of a FOREIGN KEY constraint on a table with row-level security enabled can allow information disclosure, modification, or deletion not authorized at the row level. 0 0
15600 An invalid parameter or option was specified for procedure '%s'. 0 0
15601 Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality to disable and enable full-text search for a database is deprecated. Please change your application. 0 0
15612 DBCC DBCONTROL error. Database was not made read-only. 0 0
15615 DBCC DBCONTROL error. Database was not made single user. 0 0
15622 No No permission to access database '%s'. 0 0
15625 Option '%ls' not recognized for '%ls' parameter. 0 0
15626 You attempted to acquire a transactional application lock without an active transaction. 0 0
15627 sp_dboption command failed. 0 0
15635 Cannot execute '%ls' because the database is in read-only access mode. 0 0
15645 Column '%ls' does not exist. 0 0
15646 Column '%ls' is not a computed column. 0 0
15647 No No views with schema binding reference table '%ls'. 0 0
15650 Updating %s 0 0
15651 %d index(es)/statistic(s) have been updated, %d did not require update. 0 0
15652 %s has been updated... 0 0
15653 %s, update is not necessary... 0 0
15654 Table %s: cannot perform the operation on the table because its clustered index is disabled. 0 0
15656 Cannot create user defined types from XML data type. 0 0
15657 Vardecimal storage format is not available in system database '%s'. 0 0
15658 Cannot run sp_resetstatus against a database snapshot. 0 0
15659 The schema '%ls' specified for parameter schema_name does not exist. 0 0
15660 Compressing XML index is not supported by the stored procedure sp_estimate_data_compression_savings. 0 0
15661 Compressing temporary tables is not supported by the stored procedure sp_estimate_data_compression_savings. 0 0
15662 Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings. 0 0
10000 Unknown provider error. 0 0
10001 The provider reported an unexpected catastrophic failure. 0 0
10002 The provider did not implement the functionality. 0 0
10003 The provider ran out of memory. 0 0
10004 One or more arguments were reported invalid by the provider. 0 0
10005 The provider did not support an interface. 0 0
10006 The provider indicated an invalid pointer was used. 0 0
10007 The provider indicated an invalid handle was used. 0 0
10008 The provider terminated the operation. 0 0
10009 The provider did not give any information about the error. 0 0
10010 The data necessary to complete this operation was not yet available to the provider. 0 0
10011 Access denied. 0 0
10021 Execution terminated by the provider because a resource limit was reached. 0 0
10022 The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned. 0 0
10023 The provider does not support the necessary method. 0 0
10024 The provider indicates that the user did not have the permission to perform the operation. 0 0
10025 Provider caused a server fault in an external process. 0 0
10026 No No command text was set. 0 0
10027 Command was not prepared. 0 0
10028 Authentication failed. 0 0
10032 Cannot return multiple result sets (not supported by the provider). 0 0
10033 The specified index does not exist or the provider does not support an index scan on this data source. 0 0
10034 The specified table or view does not exist or contains errors. 0 0
10035 No No value was given for one or more of the required parameters. 0 0
10042 Cannot set any properties while there is an open rowset. 0 0
10052 The insertion was canceled by the provider during notification. 0 0
10053 Could not convert the data value due to reasons other than sign mismatch or overflow. 0 0
10054 The data value for one or more columns overflowed the type used by the provider. 0 0
10055 The data violated the integrity constraints for one or more columns. 0 0
10056 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. 0 0
10057 Cannot create the row. Would exceed the total number of active rows supported by the rowset. 0 0
10058 The consumer cannot insert a new row before releasing previously-retrieved row handles. 0 0
10060 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060) 0 0
10061 An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061) 0 0
10062 The change was canceled by the provider during notification. 0 0
10063 The change was canceled by the provider during notification. 0 0
10064 Could not convert the data value due to reasons other than sign mismatch or overflow. 0 0
10065 The data value for one or more columns overflowed the type used by the provider. 0 0
10066 The data violated the integrity constraints for one or more columns. 0 0
10067 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property. 0 0
10068 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized. 0 0
10069 The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source. 0 0
10081 The consumer could not delete the row. The insertion has been transmitted to the data source. 0 0
10085 The rowset uses integrated indexes and there is no current index. 0 0
10086 RestartPosition on the table was canceled during notification. 0 0
10087 The table was built over a live data stream and the position cannot be restarted. 0 0
10088 The provider did not release some of the existing rows. 0 0
10100 The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed. 0 0
10101 Cannot create %S_MSG on view "%.*ls" because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG(*) to simulate DISTINCT on grouping columns. 0 0
10102 Cannot create %S_MSG on view "%.*ls" because it contains the TOP keyword. Consider removing TOP or not indexing the view. 0 0
10103 Cannot create %S_MSG on view "%.*ls" because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view. 0 0
10104 Cannot create %S_MSG on view "%.*ls" because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUERY, OPENROWSET, and OPENDATASOURCE. 0 0
10105 Cannot create %S_MSG on view "%.*ls" because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view. 0 0
10106 Cannot create %S_MSG on view "%.*ls" because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view. 0 0
10107 Cannot create %S_MSG on view "%.*ls" because it references an internal system rowset provider. Consider not indexing this view. 0 0
10108 Cannot create %S_MSG on view "%.*ls" because it uses table variable "%.*ls". Consider not indexing this view or removing the reference to the table variable. 0 0
10109 Cannot create %S_MSG on view "%.*ls" because it references a SQL Server internal table. 0 0
10110 Cannot create %S_MSG on view "%.*ls" because it references derived table "%.*ls" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view. 0 0
10111 Cannot create %S_MSG on view "%.*ls" because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY. 0 0
10112 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. 0 0
10113 Cannot create %S_MSG on view '%.*ls' because it contains an INNER join that specifies a join hint. Consider removing the join hint. 0 0
10114 Cannot create %S_MSG on view "%.*ls" because it uses a LEFT, RIGHT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Consider using an INNER join instead. 0 0
10115 Cannot create %S_MSG on view "%.*ls" because it uses the PIVOT operator. Consider not indexing this view. 0 0
10116 Cannot create %S_MSG on view "%.*ls" because it uses the UNPIVOT operator. Consider not indexing this view. 0 0
10117 Cannot create %S_MSG on view '%.*ls' because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view for each query that is an input to the UNION, INTERSECT, or EXCEPT operators of the original view. 0 0
10118 Cannot create %S_MSG on view "%.*ls" because the view uses the "*" operator to select columns. Consider referencing columns by name instead. 0 0
10119 Cannot create %S_MSG on view "%.*ls" because it contains a GROUP BY ALL. Consider using a GROUP BY instead. 0 0
10121 Cannot create %S_MSG on view "%.*ls" because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view. 0 0
10122 Cannot create %S_MSG on view "%.*ls" because it contains a HAVING clause. Consider removing the HAVING clause. 0 0
10123 Cannot create %S_MSG on view "%.*ls" because it contains a COMPUTE clause. Consider not indexing this view, or using a GROUP BY or aggregate view instead to replace the COMPUTE calculation of aggregate results. 0 0
10124 Cannot create %S_MSG on view "%.*ls" because it contains a join that uses deprecated Transact-SQL join syntax ( *= and =* ). Consider using = operator (non-outer-join) instead. 0 0
10125 Cannot create %S_MSG on view "%.*ls" because it references an internal SQL Server column. 0 0
10126 Cannot create %S_MSG on view "%.*ls" because it uses aggregate "%.*ls". Consider eliminating the aggregate, not indexing the view, or using alternate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUNT, substitute COUNT_BIG. 0 0
10127 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. 0 0
10128 Cannot create %S_MSG on view "%.*ls" because it contains one or more subqueries. Consider changing the view to use only joins instead of subqueries. Alternatively, consider not indexing this view. 0 0
10129 Cannot create %S_MSG on view "%.*ls" because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or not indexing the view. 0 0
10130 Cannot create %S_MSG on view "%.*ls" because it references the inline or multistatement table-valued function "%.*ls". Consider expanding the function definition by hand in the view definition, or not indexing the view. 0 0
10131 Cannot create %S_MSG on view "%.*ls" because it uses non-deterministic common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view or changing it to not use this function. 0 0
10132 Cannot create %S_MSG on view "%.*ls" because it references imprecise common language runtime (CLR) table-valued function "%.*ls". Consider not indexing the view. 0 0
10133 Cannot create %S_MSG on view "%.*ls" because it references table valued common language runtime (CLR) function "%.*ls". Consider removing reference to the function or not indexing the view. 0 0
10134 Cannot create %S_MSG on view "%.*ls" because function "%.*ls" referenced by the view performs user or system data access. 0 0
10136 Cannot create %S_MSG on view "%.*ls" because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY. 0 0
10137 Cannot create %S_MSG on view "%.*ls" because it uses the aggregate COUNT. Use COUNT_BIG instead. 0 0
10138 Cannot create %S_MSG on view "%.*ls" because it references common table expression "%.*ls". Views referencing common table expressions cannot be indexed. Consider not indexing the view, or removing the common table expression from the view definition. 0 0
10139 Cannot create %S_MSG on view '%.*ls' because its select list does not include a proper use of COUNT_BIG. Consider adding COUNT_BIG(*) to select list. 0 0
10140 Cannot create %S_MSG on view '%.*ls' because the view uses an implicit conversion from string to datetime or smalldatetime. Use an explicit CONVERT with a deterministic style value. 0 0
10141 Cannot create %S_MSG on view '%.*ls' because the view contains a table hint. Consider removing the hint. 0 0
10142 Cannot create %S_MSG on view '%.*ls' because it references CLR routine (function or method) '%.*ls' outside non-key columns of SELECT list. Recreate or alter view so it does not reference CLR routines except in non-key columns of SELECT list, and then create index. 0 0
10143 Cannot create %S_MSG on view "%.*ls" because it contains an APPLY. Consider not indexing the view, or removing APPLY. 0 0
10144 Cannot create %S_MSG on view "%.*ls" because it contains a ranking or aggregate window function. Remove the function from the view definition or, alternatively, do not index the view. 0 0
10145 Cannot create %S_MSG on view '%.*ls' because it uses the CHANGETABLE function. 0 0
10211 Cannot create %S_MSG on the view '%.*ls' because it references a sparse column set. Views that contain a sparse column set cannot be indexed. Consider removing the sparse column set from the view or not indexing the view. 0 0
10227 Cannot invoke mutator on a null CLR type value. 0 0
10240 Field "%.*ls" of type "%.*ls.%.*ls" cannot be updated because the field is "%.*ls". 0 0
10300 Could not find UdtExtensions.dll. Please check your installation. 0 0
10301 Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %S_MSG). Please load the referenced assembly into the current database and retry your request. 0 0
10302 Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %s). Please load the referenced assembly into the current database and retry your request. 0 0
10303 Could not get path for SQL Server: '%ls'. 0 0
10304 Could not create AppDomain manager: '%.*ls'. 0 0
10305 Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions. 0 0
10306 The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute. 0 0
10307 The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property. 0 0
10308 The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name. 0 0
10309 Warning: The Microsoft .NET Framework assembly '%.*ls' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details. 0 0
10310 Warning: The SQL Server client assembly '%.*ls' you are registering is not fully tested in SQL Server hosted environment. 0 0
10311 AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations. 0 0
10312 AppDomain %i (%.*ls) is marked for unload due to memory pressure. 0 0
10313 .NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token. 0 0
10314 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 0 0
10316 An error occurred in the Microsoft .NET Framework while trying to load assembly id %d. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: %.*ls 0 0
10317 The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found. 0 0
10318 An error occurred trying to get file version info for the file '%s'. 0 0
10319 '%.*ls' failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute. 0 0
10320 UserDefinedType method call failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute. 0 0
10321 Method name '%.*ls' is invalid for '%.*ls'. 0 0
10322 Method name '%.*ls' is invalid for UserDefinedType method call. 0 0
10323 Type %.*ls not found in database %.*ls 0 0
10324 Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls 0 0
10325 WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers. 0 0
10326 The server is shutting down due to stack overflow in user's unmanaged code. 0 0
10327 Two versions of assembly '%.*ls' cannot coexist in database '%.*ls'. Keep one version and drop the other. 0 0
10328 %ls ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is not authorized for PERMISSION_SET = %ls. The assembly is authorized when either of the following is true: the database owner (DBO) has %ls permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with %ls permission. 0 0
10329 There is not enough stack to create appdomain '%.*ls'. 0 0
10330 .Net Framework execution was aborted. %.*ls 0 0
10331 ALTER ASSEMBLY failed because serialization layout of type '%s' would change as a result of a change in type '%s' in the updated assembly. Persisted types are not allowed to change serialization layout. 0 0
10501 Type '%ls' in assembly '%.*ls' derives from a generic type which is not supported for a CLR Type. 0 0
10502 Cannot create plan guide '%.*ls' because type '%.*ls' provided is not allowed. 0 0
10503 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. 0 0
10504 Operation '%.*ls' is not allowed. 0 0
10505 Cannot create plan guide '%.*ls' because parameter @hints is incorrect. Use N'OPTION ( [ ,...n ] )'. 0 0
10506 Cannot create plan guide '%.*ls' because value '%.*ls' provided for @module_or_batch is not legal two-part name. Use 'schema_name.object_name'. 0 0
10507 Cannot create plan guide '%.*ls' because parameter @stmt has more than one statement. 0 0
10508 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. 0 0
10509 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. 0 0
10510 Cannot create plan guide '%.*ls' because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is ineligible for use in a plan guide. Provide a single valid Transact-SQL statement or a valid starting position of the statement within the batch. To obtain a valid starting position, query the 'statement_start_offset' column in the sys.dm_exec_query_stats dynamic management function. 0 0
10512 Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name. 0 0
10513 Cannot create plan guide '%.*ls' because object '@module_or_batch' is encrypted. Consider tuning query using other techniques such as indexes and statistics. 0 0
10515 Cannot %S_MSG %S_MSG '%.*ls' because it is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed. 0 0
10516 Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission. 0 0
10517 Cannot create plan guide '%.*ls' because @module_or_batch can not be compiled. 0 0
10518 Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required. 0 0
10519 Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide '%.*ls'. Alter permission on object referenced by plan guide, or alter database permission required. 0 0
10520 Cannot create plan guide '%.*ls' because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statement_start_offset. Verify that the hints can be applied to the statement. 0 0
10521 Cannot create plan guide '%.*ls' because @type was specified as '%ls' and a non-NULL value is specified for the parameter '%ls'. This type requires a NULL value for the parameter. Specify NULL for the parameter, or change the type to one that allows a non-NULL value for the parameter. 0 0
10522 Cannot create plan guide '%.*ls' because @type was specified as '%ls' and the parameter '%ls' is NULL. This type requires a non-NULL value for the parameter. Specify a non-NULL value for the parameter, or change the type to one that allows a NULL value for the parameter. 0 0
10523 Cannot create plan guide '%.*ls' because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) if @type is 'template'. 0 0
10524 Cannot generate query template because @querytext does not contain a valid single query. 0 0
10525 Cannot parameterize @querytext. 0 0
10526 Plan guide '%.*ls' matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains was ignored. RECOMPILE is not supported on automatically parameterized statements. Consider dropping this plan guide or removing RECOMPILE from it. 0 0
10527 Cannot drop %S_MSG '%.*ls' because its trigger '%.*ls' is referenced by plan guide '%.*ls'. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed. 0 0
10528 Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object. 0 0
10529 Cannot create plan guide '%.*ls' because its name is invalid. Plan guide name cannot begin with a ' 0 0
10530 Cannot create plan guide '%.*ls' because there is already a planguide '%.*ls' of @type 'template' on @stmt. 0 0
10531 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. 0 0
10532 Cannot create plan guide '%.*ls' from cache because the user does not have adequate permissions. Grant the VIEW SERVER STATE permission to the user creating the plan guide. 0 0
10533 Cannot create plan guide '%.*ls' because the batch or module specified by @plan_handle does not contain a statement that is eligible for a plan guide. Specify a different value for @plan_handle. 0 0
10534 Cannot create plan guide '%.*ls' because the plan guide name exceeds 124, the maximum number of characters allowed. Specify a name that contains fewer than 125 characters. 0 0
10535 Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form , or specify NULL. 0 0
10536 Cannot create plan guide '%.*ls' because a plan was not found in the plan cache that corresponds to the specified plan handle. Specify a cached plan handle. For a list of cached plan handles, query the sys.dm_exec_query_stats dynamic management view. 0 0
10537 Cannot create plan guide '%.*ls' because the batch or module corresponding to the specified @plan_handle contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a statement_start_offset value for each statement. 0 0
10538 Cannot enable plan guide '%.*ls' because the enabled plan guide '%.*ls' contains the same scope and starting offset value of the statement. Disable the existing plan guide before enabling the specified plan guide. 0 0
10539 Cannot find the plan guide either because the specified plan guide ID is NULL or invalid, or you do not have permission on the object referenced by the plan guide. Verify that the plan guide ID is valid, the current session is set to the correct database context, and you have ALTER permission on the object referenced by the plan guide or ALTER DATABASE permission. 0 0
10601 Cannot create plan guide '%.*ls' from cache because a query plan is not available for the statement with start offset %d.This problem can occur if the statement depends on database objects that have not yet been created. Make sure that all necessary database objects exist, and execute the statement before creating the plan guide. 0 0
10602 Cannot specify included columns for a clustered index. 0 0
10603 Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed. 0 0
10604 Cannot rebuild clustered index '%.*ls' on view '%.*ls' because the view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disabled. 0 0
10605 Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified. 0 0
10606 Cannot disable primary key index "%.*ls" on table "%.*ls" because the table is published for replication. 0 0
10607 Cannot disable the clustered index "%.*ls" on view "%.*ls" because the indexed view is published for replication. 0 0
10608 The clustered index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Disable change tracking on the table before disabling the clustered index. 0 0
10609 The index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Change tracking requires a primary key constraint on the table, and disabling the index will drop the constraint. Disable change tracking on the table before disabling the index. 0 0
10610 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is a computed column. Rewrite the filter expression so that it does not include this column. 0 0
10611 Filtered index '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered indexes are only supported on tables. If you are trying to create a filtered index on a view, consider creating an indexed view with the filter expression incorporated in the view definition. 0 0
10612 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant of higher data type precedence or of a different collation. Converting a column to the data type of a constant is not supported for filtered %S_MSG. To resolve this error, explicitly convert the constant to the same data type and collation as the column '%.*ls'. 0 0
10617 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant that cannot be converted to the data type of the column. Rewrite the filter expression so that it does not include this comparison. 0 0
10618 Index '%.*ls' could not be created or rebuilt. The key length for this index (%d bytes) exceeds the maximum allowed length of '%d' bytes when using the vardecimal storage format. 0 0
10619 Cannot %S_MSG filtered index '%.*ls' on table '%.*ls' because the statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it does not use the IGNORE_DUP_KEY option. 0 0
10620 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is of a CLR data type. Rewrite the filter expression so that it does not include this column. 0 0
10621 Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the filter expression contains a comparison with a literal NULL value. Rewrite the comparison to use the IS [NOT] NULL comparison operator to test for NULL values. 0 0
10622 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. 0 0
10623 Index '%.*ls' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set column. 0 0
10700 Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user tables. 0 0
10701 The table-valued parameter "%.*ls" is READONLY and cannot be modified. 0 0
10702 The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement. 0 0
10703 The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification. 0 0
10705 Too many grouping sets. The maximum number is %d. 0 0
10706 Subqueries are not allowed in the OUTPUT clause. 0 0
10707 Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied. 0 0
10708 The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 mode or higher. 0 0
10709 DEFAULT is not allowed on the right hand side of "%.*ls" 0 0
10710 The number of columns for each row in a table value constructor must be the same. 0 0
10711 An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement. 0 0
10712 An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement. 0 0
10713 Non-ANSI outer join operators ("*=" or "=*") are not allowed in a MERGE statement. Use the OUTER JOIN keywords instead. 0 0
10714 A MERGE statement must be terminated by a semi-colon (;). 0 0
10716 An action of type '%S_MSG' cannot appear more than once in a '%S_MSG' clause of a MERGE statement. 0 0
10717 A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause. 0 0
10718 The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
10719 Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements. 0 0
10720 Non-ANSI outer join operators ("*=" or "=*") are not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. Use the OUTER JOIN keywords instead. 0 0
10721 An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
10722 The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
10723 The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
10724 In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of the form 'SET @variable = column = expression' are not valid in the SET clause of an UPDATE action in a MERGE statement. Modify the SET clause to only specify assignments of the form 'SET @variable = column' or 'SET @variable = expression'. 0 0
10725 The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements. 0 0
10726 Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. 0 0
10727 User defined aggregates do not support default parameters. 0 0
10728 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator. 0 0
10729 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator. 0 0
10730 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statement. 0 0
10731 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement. 0 0
10732 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement. 0 0
10733 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator. 0 0
10734 A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement. 0 0
10735 Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator. 0 0
10736 Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.*ls'. 0 0
10737 A full-text stoplist statement must be terminated by a semi-colon (;). 0 0
10738 In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specified. The PARTITION=ALL clause is used to reinforce that all partitions of the table or index will be rebuilt, even if only a subset is specified in the DATA_COMPRESSION clause. 0 0
10739 The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values. 0 0
10900 The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead. 0 0
10901 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'). 0 0
10902 User does not have permission to alter the resource governor configuration. 0 0
10903 User-defined function '%s' does not exist in master database, or the user does not have permission to access it. 0 0
10904 The specified schema name '%.*ls' for classifier user-defined function either does not exist, or the user does not have permission to use it. 0 0
10905 Resource governor configuration failed. There are active sessions in workload groups being dropped or moved to different resource pools. Disconnect all active sessions in the affected workload groups and try again. 0 0
10906 Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicated administrator connection. 0 0
10907 The object '%.*ls'.'%.*ls' is not a valid resource governor classifier user-defined function. A valid classifier user-defined function must be schema-bound, return sysname, and have no parameters. 0 0
10908 Attribute '%.*ls' with value of %u is greater than attribute '%.*ls' with value of %u. 0 0
10909 Attribute '%.*ls' with value of %u is less than attribute '%.*ls' with value of %u. 0 0
10910 The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools. 0 0
10911 The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all resource pools to exceed 100 percent. Reduce the value or modify other resource pools so that the sum is less than 100. 0 0
10912 Requested operation cannot be performed because the resource pool '%.*ls' does not exist. 0 0
10913 The operation could not be completed. Dropping predefined %S_MSG is not allowed. 0 0
10914 Users are not allowed to %S_MSG the workload group '%.*ls' in the '%.*ls' resource pool. 0 0
10915 The name of the %S_MSG '%.*ls' cannot begin with 0 1
10916 The operation could not be completed. Altering '%.*ls' %S_MSG is not allowed. 0 0
10917 Cannot drop resource pool '%.*ls' because it contains workload group '%.*ls'. Drop or remove all workload groups using this resource pool before dropping it. 0 0
10918 ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified. 0 0
10919 Cannot create %S_MSG '%.*ls' because it already exists. 0 0
10920 An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system administrator. 0 0
10921 Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier. 0 0
10922 The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG. 0 0
10923 %ls failed. Rerun the statement. 0 0
10981 %ls failed. The resource governor is not available in this edition of SQL Server. You can manipulate resource governor metadata but you will not be able to apply resource governor configuration. Only Enterprise edition of SQL Server supports resource governor. 0 0
10982 Resource governor reconfiguration succeeded. 0 0
10983 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. 0 0
10984 Resource governor '%ls' operation was canceled by user. 0 0
6001 SHUTDOWN is waiting for %d process(es) to complete. 0 0
6004 User does not have permission to perform this action. 0 0
6005 SHUTDOWN is in progress. 0 0
6006 Server shut down by %.*ls from login %.*ls. 0 0
6007 The SHUTDOWN statement cannot be executed within a transaction or by a stored procedure. 0 0
6101 Process ID %d is not a valid process ID. Choose a number between 1 and %d. 0 0
6102 User does not have permission to use the KILL statement. 0 0
6104 Cannot use KILL to kill your own process. 0 0
6106 Process ID %d is not an active process ID. 0 0
6107 Only user processes can be killed. 0 0
6108 KILL SPID WITH COMMIT/ABORT is not supported by Microsoft SQL Server. Use KILL UOW WITH COMMIT/ABORT to resolve in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). 0 0
6109 SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%. Estimated time remaining: %d seconds. 0 0
6110 The distributed transaction with UOW %s does not exist. 0 0
6111 Another user has decided a different outcome for the distributed transaction associated with UOW %s. 0 0
6112 Distributed transaction with UOW %s is in prepared state. Only Microsoft Distributed Transaction Coordinator can resolve this transaction. KILL command failed. 0 0
6113 The distributed transaction associated with UOW %s is in PREPARE state. Use KILL UOW WITH COMMIT/ABORT syntax to kill the transaction instead. 0 0
6114 Distributed transaction with UOW %s is being used by another user. KILL command failed. 0 0
6115 KILL command cannot be used inside user transactions. 0 0
6117 There is a connection associated with the distributed transaction with UOW %s. First, kill the connection using KILL SPID syntax. 0 0
6118 The distributed transaction associated with UOW %s is not in PREPARED state. Use KILL UOW to kill the transaction instead. 0 0
6119 Distributed transaction with UOW %s is rolling back: estimated rollback completion: %d%%, estimated time left %d seconds. 0 0
6120 Status report cannot be obtained. Rollback operation for Process ID %d is not in progress. 0 0
6121 Status report cannot be obtained. Rollback operation for UOW %s is not in progress. 0 0
6200 Method "%ls" of type "%ls" in assembly "%.*ls" is marked as a mutator. Mutators cannot be used in the read-only portion of the query. 0 0
6201 Method "%ls" of type "%ls" in assembly "%.*ls" is not marked as a mutator. Only mutators can be used to update the value of a CLR type. 0 0
6202 Method "%ls" of type "%ls" in assembly "%.*ls" does not return a value. 0 0
6203 Method '%ls' of type '%ls' in assembly '%.*ls' cannot be marked as a mutator. A mutator method must be non-static, public, and returns void type. 0 0
6204 Trying to send a record with %d columns(s) in a result set with %d column(s). 0 0
6205 %s ASSEMBLY failed because assembly '%.*ls' was compiled with /UNSAFE option, but the assembly was not registered with the required PERMISSION_SET = UNSAFE option. 0 0
6206 Request submitted with too many parameters. The maximum number is %ld. 0 0
6207 Error converting %.*ls to fixed length binary type. The result would be padded and cannot be converted back. 0 0
6208 %s failed because the parameter count for the FillRow method should be one more than the SQL declaration for the table valued CLR function. 0 0
6209 Unsound ordering on CLR type "%.*ls": returning NULL on non-NULL inputs. 0 0
6210 CLR type '%.*ls' is not fully comparable. 0 0
6211 %s ASSEMBLY failed because type '%.*ls' in %.*ls assembly '%.*ls' has a static field '%.*ls'. Attributes of static fields in %.*ls assemblies must be marked readonly in Visual C 0 0
6212 %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %.*ls assembly '%.*ls' is storing to a static field. Storing to a static field is not allowed in %.*ls assemblies. 0 0
6213 %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in %.*ls assembly "%.*ls" has a synchronized attribute. Explicit synchronization is not allowed in %.*ls assemblies. 0 0
6214 %s ASSEMBLY failed because assembly "%.*ls" has an unmanaged entry point. 0 0
6215 %s ASSEMBLY failed because method '%.*ls' on type '%.*ls' in %.*ls assembly '%.*ls' has invalid attribute 0x%x. 0 0
6216 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a finalizer. Finalizers are not allowed in %.*ls assemblies. 0 0
6217 ALTER ASSEMBLY ADD FILE failed because the file, "%.*ls", being added is empty. 0 0
6218 %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' failed verification. Check if the referenced assemblies are up-to-date and trusted (for external_access or unsafe) to execute in the database. CLR Verifier error messages if any will follow this message%.*ls 0 0
6219 %s ASSEMBLY failed because assembly source parameter %d has an unmanaged entry point. 0 0
6220 SELECT INTO failed because CLR type "%.*ls" does not exist in the target database. 0 0
6221 The cursor operation generated more than one row of different column metadata. 0 0
6222 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is not valid for native serialization. 0 0
6223 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential". 0 0
6224 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is marked with "System.NonSerializedAttribute". Native serialization types cannot have fields marked with "System.NonSerializedAttribute". 0 0
6225 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls" which is a non-value type. Native serialization types can only have fields of blittable types. If you wish to have a field of any other type, consider using different kind of serialization format, such as User Defined Serialization. 0 0
6226 Type "%.*ls.%.*ls" is marked for user-defined serialization, but does not implement the "%.*ls.%.*ls" interface. 0 0
6227 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" is of type "%.*ls.%.*ls", which is not blittable, or type "%.*ls.%.*ls" has a recursive definition. 0 0
6228 Type "%.*ls.%.*ls" is marked for native serialization, but it contains non-blittable fields. 0 0
6229 Type "%.*ls.%.*ls" is marked for native serialization. It is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential". 0 0
6230 Type "%.*ls.%.*ls" is marked for native serialization, but field "%.*ls" of type "%.*ls.%.*ls" has field marshallers. Native serialization types cannot have field marshallers. 0 0
6231 Type "%.*ls.%.*ls" is marked for native serialization, but one of its base types "%.*ls.%.*ls" is not valid for native serialization. 0 0
6232 Type "%.*ls.%.*ls" is marked for native serialization, but base type "%.*ls.%.*ls" is not marked with "LayoutKind.Sequential". Native serialization requires the type to be marked with "LayoutKind.Sequential". 0 0
6233 In proc data access is not allowed in an impersonated state. 0 0
6234 Data truncation error. Length (%d) exceeds maximum length (%d) for type '%.*ls'. 0 0
6235 Data serialization error. Length (%d) is less than fixed length (%d) for type '%.*ls'. 0 0
6236 %s ASSEMBLY failed because filename '%.*ls' is too long. 0 0
6237 %s ASSEMBLY failed because method "%.*ls" on type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls". 0 0
6238 %s ASSEMBLY failed because field "%.*ls" in type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls". 0 0
6239 %s ASSEMBLY failed because type "%.*ls" in assembly "%.*ls" has an invalid custom attribute "%.*ls". 0 0
6240 ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the indexed view '%s'. 0 0
6241 Trying to send a record with type or name of column %d differing from the type or name of the corresponding column of the result set. 0 0
6242 CREATE ASSEMBLY failed because the user "%.*ls" specified in the authorization clause does not exist. 0 0
6243 '%.*ls.%.*ls' is marked for native serialization, and has the MaxByteSize property specified in the '%.*ls' attribute. Native serialization objects can not specify MaxByteSize property, it is calculated by SQL Server. 0 0
6244 The size (%d) for "%.*ls.%.*ls" is not in the valid range. Size must be -1 or a number between 1 and 8000. 0 0
6245 Invalid serialization format (%d) for type "%.*ls.%.*ls". 0 0
6246 Assembly "%.*ls" already exists in database "%.*ls". 0 0
6247 Cannot create type because '%.*ls.%.*ls' cannot have fixed length if it has MaxByteSize set to -1. 0 0
6248 %s failed because the type '%s' contains a method '%s' specified by SqlUserDefinedType.ValidateMethodName that does not conform to the required specification because it has an invalid signature. 0 0
6249 The associated file "%.*ls" already exists for assembly "%.*ls". 0 0
6250 Assembly "%.*ls" does not have an associated file "%.*ls". 0 0
6251 ALTER ASSEMBLY failed because the assembly file parameter %d is not a valid expression. 0 0
6252 ALTER ASSEMBLY failed because a file name was not specified for the inline assembly file parameter %d. 0 0
6253 Common language runtime (CLR) functionality initialized using CLR version %ls from %ls. 0 0
6254 Common language runtime (CLR) functionality initialized. 0 0
6255 %s failed because type "%s" does not conform to the %s specification: missing custom attribute "%.*ls". 0 0
6258 Function signature of "FillRow" method (as designated by SqlFunctionAttribute.FillRowMethodName) does not match SQL declaration for table valued CLR function'%.*ls' due to column %d. 0 0
6260 An error occurred while getting new row from user defined Table Valued Function : %.*ls. 0 0
6261 The CLR type referenced by column "%.*ls" of table variable "%.*ls" has been dropped during the execution of the batch. Run the batch again. 0 0
6262 Assembly was not found in current database or version did not match. 0 0
6263 Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option. 0 0
6264 Data access failed because the .NET Framework routine is not marked with "DataAccessKind.Read" or "SystemDataAccessKind.Read". 0 0
6265 %s ASSEMBLY failed because type "%.*ls" in %.*ls assembly "%.*ls" has a pinvokeimpl method. P/Invoke is not allowed in %.*ls assemblies. 0 0
6266 Warning: Assembly "%.*ls" was built using version %.*ls of the .NET Framework. SQL Server currently uses version %s. 0 0
6267 Assembly "%.*ls" does not exist, or the user does not have permission to reference it. 0 0
6269 ALTER ASSEMBLY failed because the user-defined aggregate "%s" does not exist or is not correctly defined in the updated assembly. 0 0
6270 ALTER ASSEMBLY failed because the required method "%s" in type "%s" was not found with the same signature in the updated assembly. 0 0
6271 ALTER ASSEMBLY failed because the required field "%s" in type "%s" was not found with the same signature in the updated assembly. 0 0
6272 ALTER ASSEMBLY failed because required property '%s' in type '%s' was not found with the same signature in the updated assembly. 0 0
6273 ALTER ASSEMBLY failed because required type '%s' does not exist or is not correctly defined in the updated assembly. 0 0
6274 ALTER ASSEMBLY failed because the serialization format of type '%s' would change in the updated assembly. Persisted types are not allowed to change serialization formats. 0 0
6275 ALTER ASSEMBLY failed because the IsByteOrdered attribute of type '%s' would change in the updated assembly. 0 0
6276 ALTER ASSEMBLY failed because serialization data of type '%s' would change in the updated assembly. Persisted types are not allowed to change serialization data. 0 0
6277 ALTER ASSEMBLY failed because the MaxLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change MaxLen attribute. 0 0
6278 ALTER ASSEMBLY failed because the IsFixedLen attribute of type '%s' would change in the updated assembly. Persisted types are not allowed to change IsFixedLen attribute. 0 0
6279 ALTER ASSEMBLY failed because the mutator attribute of method '%s' in type '%s' would change in the updated assembly, and the method is in use by the schema-bound function or view '%s'. 0 0
6280 ALTER ASSEMBLY failed because table, view or constraint '%s' depends on this assembly. Use WITH UNCHECKED DATA to skip checking for persisted data. 0 0
6281 ALTER ASSEMBLY failed because only members of the sysadmin role can use WITH UNCHECKED DATA. 0 0
6282 ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same. 0 0
6283 ALTER ASSEMBLY failed because only the assembly revision version number is allowed to change. 0 0
6284 ALTER ASSEMBLY failed because it is referenced by object '%.*ls'. Assemblies that are referenced by SQL objects cannot be made invisible. 0 0
6285 %s ASSEMBLY failed because the source assembly is, according to MVID, identical to an assembly that is already registered under the name "%.*ls". 0 0
6286 '%s' ASSEMBLY failed because a different version of assembly '%s', referenced by assembly '%s', is already in the database. 0 0
6287 ALTER ASSEMBLY failed because the function '%s' of type '%s' no longer satisfies indexability requirements, and is used for the persisted computed column '%s' of table '%s'. 0 0
6288 ALTER ASSEMBLY has marked data as unchecked in one or more objects in database "%.*ls". Refer to column "has_unchecked_assembly_data" from system views "sys.tables" and "sys.views" to locate all such objects. 0 0
6289 Failed to allocate memory for common language runtime (CLR) functionality. 0 0
6290 AppDomain %i (%.*ls) unloaded. 0 0
6291 AppDomain %i (%.*ls) failed to unload with error code 0x%x. 0 0
6292 The transaction that is associated with this operation has been committed or rolled back. Retry with a different transaction. 0 0
6293 %.*ls.%.*ls.%.*ls: SqlFacetAttribute is invalid on a non-public member. 0 0
6294 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute cannot be used in this context. 0 0
6295 %.*ls.%.*ls.%.*ls: %.*ls property of SqlFacetAttribute has an invalid value. 0 0
6296 %.*ls.%.*ls.%.*ls : SqlFacetAttribute cannot be applied to a property getter or a property setter. It should be applied to the property itself. 0 0
6297 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute property IsFixedLength cannot be set to true when MaxSize is set to -1. 0 0
6298 %.*ls.%.*ls.%.*ls: The SqlFacetAttribute properties Precision and Scale have to be used together. 0 0
6299 AppDomain %i (%.*ls) created. 0 0
6302 The argument of CREATE or ALTER XML SCHEMA COLLECTION statement must be a string expression. 0 0
6303 XML parsing: Document parsing required too much memory 0 0
6304 XML parsing: An unexpected error has occurred in the XML parser. 0 0
6305 XQuery data manipulation expression required in XML data type method. 0 0
6306 Invalid XQuery expression passed to XML data type method. 0 0
6307 XML well-formedness check: Attribute cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML. 0 0
6308 XML well-formedness check: Duplicate attribute '%.*ls'. Rewrite your XQuery so it returns well-formed XML. 0 0
6309 XML well-formedness check: the data for node '%.*ls' contains a character (0x%04X) which is not allowed in XML. 0 0
6310 Altering existing schema components is not allowed. There was an attempt to modify an existing XML Schema component, component namespace: '%.*ls' component name: '%.*ls' component kind:%.*ls 0 0
6311 An internal XMLDB schema processor error occurred. Contact Technical Support for assistance. 0 0
6312 Could not find schema components with target namespace '%.*ls' in collection '%.*ls'. 0 0
6314 Collection specified does not exist in metadata : '%.*ls' 0 0
6315 XQuery: Cannot update with value '%.*ls' as the canonical form of type '{%.*ls}%.*ls' violates the required pattern. It is recommended that you not use pattern facets on non-string types. 0 0
6316 Specified component '%s' can not be dropped because it is used by component:'%s' 0 0
6317 XQuery: Cannot update with value '%.*ls' because it failed validation against type '{%.*ls}%.*ls' 0 0
6318 XQuery: String conversion failed during UPDATE validation 0 0
6320 XQuery: Only nillable elements or text nodes can be updated with empty sequence 0 0
6321 xml:space attribute must have a value of 'preserve' or 'default'. '%.*ls' is not valid. 0 0
6322 XML Parser ran out of memory. This could be caused by too many attributes or namespace declarations. 0 0
6323 The xml schema collection for variable '%.*ls' has been altered while the batch was being executed. Remove all XML schema collection DDL operations it is dependent on from the batch, and re-run the batch. 0 0
6324 DROP XML INDEX does not support any options. 0 0
6325 XQuery: Replacing the value of a node with an empty sequence is allowed only if '()' is used as the new value expression. The new value expression evaluated to an empty sequence but it is not '()'. 0 0
6326 XML well-formedness check: XML namespace declaration cannot appear outside of element declaration. Rewrite your XQuery so it returns well-formed XML. 0 0
6327 The specified xml schema collection ID is not valid: %d 0 0
6328 Specified collection '%.*ls' cannot be dropped because it is used by %S_MSG '%ls'. 0 0
6329 Unsupported usage of a QName typed value in node '%.*ls' 0 0
6330 Column '%.*ls' on table '%.*ls' is not of type XML, which is required to create an XML index on it. 0 0
6331 Primary XML Index '%.*ls' already exists on column '%.*ls' on table '%.*ls', and multiple Primary XML Indexes per column are not allowed. 0 0
6332 Table '%.*ls' needs to have a clustered primary key with less than %d columns in it in order to create a primary XML index on it. 0 0
6333 Could not find%ls XML index named '%.*ls' on table '%.*ls' 0 0
6334 Could not create the XML or spatial index on object '%.*ls' because that object is not a table. Create the index on the base table column. 0 0
6335 XML datatype instance has too many levels of nested nodes. Maximum allowed depth is %d levels. 0 0
6336 Maximum size of primary index of table '%.*ls' is %d bytes. CREATE XML INDEX requires that such size should be limited to %d bytes 0 0
6337 '%.*ls' is not a valid XML Index name because it starts with '%c' character. XML Index name should not start with ' 0 0
6338 XML DTD has been stripped from one or more XML fragments. External subsets, if any, have been ignored. 0 0
6339 Specified collection '%.*ls' cannot be modified because it is SQL Server built-in XML Schema Collection. 0 0
6340 Xml schema collection '%.*ls' referenced by table variable '%.*ls' has been dropped or altered during the execution of the batch. Please re-run the batch. 0 0
6341 Xml schema collection referenced by column '%.*ls' of table variable '%.*ls' has been dropped or altered during the execution of the batch. Please re-run the batch. 0 0
6342 Cannot create primary xml or spatial index '%.*ls' on table '%.*ls', column '%.*ls', because the column is computed. 0 0
6343 Cannot create secondary xml index '%.*ls' without a USING XML INDEX clause. 0 0
6344 The primary xml index '%.*ls' does not exist on table '%.*ls' column '%.*ls'. 0 0
6345 The sparse column set '%.*ls' in the table '%.*ls' cannot be indexed by an XML index. 0 0
6346 Cannot convert a primary XML index to a secondary XML index using the DROP_EXISTING option. '%.*ls' is a primary XML index. 0 0
6347 Specified collection '%.*ls' cannot be altered because it does not exist or you do not have permission. 0 0
6348 Specified collection '%.*ls' cannot be created because it already exists or you do not have permission. 0 0
6350 The definition for xml schema collection '%.*ls' has changed. 0 0
6351 The xml schema collection for return parameter of module '%.*ls' has been altered while the batch was being executed. Please re-run the batch. 0 0
6352 Invalid parameter specified. XML Schema Collections can only be created from a string literal, or from a variable typed as a string or untyped XML. 0 0
6353 Serialization of built-in schemata is not supported. 0 0
6354 Target string size is too small to represent the XML instance 0 0
6355 Conversion of one or more characters from XML to target collation impossible 0 0
6356 Failed to load DLL. Make sure xmlrw.dll exists in the SQL Server installation. 0 0
6357 Internal error: cannot locate CreateInfoSetReaderEx in xmlrw.dll. You may have an incorrect version of xmlrw.dll. 0 0
6358 %d is not a valid style number when converting to XML. 0 0
6359 Parsing XML with internal subset DTDs not allowed. Use CONVERT with style option 2 to enable limited internal subset DTD support. 0 0
6360 %d is not a valid style number when converting from XML. 0 0
6361 Invalid null parameter specified. XML Schema Collections can only be created from a non-null value. 0 0
6362 Alter schema collection cannot be performed because the current schema has a lax wildcard or an element of type xs:anyType. 0 0
6363 ALTER SCHEMA COLLECTION failed. It cannot be performed on a schema collection that allows laxly validated content and is schema bound. Remove the schema binding before trying to alter the collection. 0 0
6364 ALTER SCHEMA COLLECTION failed. Revalidation of XML columns in table '%.*ls' did not succeed due to the following reason: '%.*ls'. Either the schema or the specified data should be altered so that validation does not find any mismatches. 0 0
6365 An XML operation resulted an XML data type exceeding 2GB in size. Operation aborted. 0 0
6401 Cannot roll back %.*ls. No transaction or savepoint of that name was found. 0 0
6500 %ls failed because method '%ls' of class '%ls' in assembly '%ls' returns %ls, but CLR Triggers must return void. 0 0
6501 %s ASSEMBLY failed because it could not open the physical file "%.*ls": %ls. 0 0
6502 %s ASSEMBLY failed because it could not read from the physical file '%.*ls': %ls. 0 0
6503 Assembly '%.*ls' was not found in the SQL catalog. 0 0
6504 The value returned from %.*ls.%.*ls is not allowed to be NULL. 0 0
6505 Could not find Type '%s' in assembly '%s'. 0 0
6506 Could not find method '%s' for type '%s' in assembly '%s' 0 0
6507 Failed to open malformed assembly '%ls' with HRESULT 0x%x. 0 0
6508 Could not find field '%s' for type '%s' in assembly '%s'. 0 0
6509 An error occurred while gathering metadata from assembly '%ls' with HRESULT 0x%x. 0 0
6510 Common Language Runtime (CLR) %ls not installed properly. The CLR is required to use SQL/CLR features. 0 0
6511 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You may fix the problem and try again later. 0 0
6512 Failed to initialize the Common Language Runtime (CLR) %ls with HRESULT 0x%x. You need to restart SQL Server to use CLR integration features. 0 0
6513 Failed to initialize the Common Language Runtime (CLR) %ls due to memory pressure. This is probably due to memory pressure in the MemToLeave region of memory. For more information, see the CLR integration documentation in SQL Server Books Online. 0 0
6514 Cannot use '%s' column in the result table of a streaming user-defined function (column '%.*ls'). 0 0
6515 Schema collection database '%.*ls' does not exist or you do not have permission. 0 0
6516 There is no collection '%.*ls' in metadata '%.*ls'. 0 0
6517 Failed to create AppDomain "%.*ls". %.*ls 0 0
6518 Could not open system assembly ''%.*ls'': %ls. 0 0
6519 Type '%.*ls' is not yet supported for CLR operations. 0 0
6520 A .NET Framework error occurred during statement execution. 0 0
6521 A .NET Framework error occurred during statement execution: %.*ls. 0 0
6522 A .NET Framework error occurred during execution of user-defined routine or aggregate "%.*ls": %ls. 0 0
6523 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is static. 0 0
6524 Cannot use computed column in the result table of a streaming user-defined function (column '%.*ls'). 0 0
6525 Cannot use '%s' constraint in the result table of a streaming user-defined function. 0 0
6526 Cannot use '%s' constraint in the result table of a streaming user-defined function (column '%.*ls'). 0 0
6527 .NET Framework runtime has been stopped. 0 0
6528 Assembly '%.*ls' was not found in the SQL catalog of database '%.*ls'. 0 0
6529 ALTER ASSEMBLY failed because the identity of referenced assembly '%.*ls' has changed. Make sure the version, name, and public key have not changed. 0 0
6530 Cannot perform alter on '%.*ls' because it is an incompatible object type. 0 0
6531 %ls failed because the function '%ls' of class '%ls' of assembly '%.*ls' takes one or more parameters but CLR Triggers do not accept parameters. 0 0
6532 .NET Framework execution was aborted by escalation policy because of out of memory. %.*ls 0 0
6533 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource. %.*ls 0 0
6534 AppDomain %.*ls was unloaded by escalation policy to ensure the consistency of your application. Application failed to release a managed lock. %.*ls 0 0
6535 .NET Framework execution was aborted. Another query caused the AppDomain %.*ls to be unloaded. %.*ls 0 0
6536 A fatal error occurred in the .NET Framework common language runtime. SQL Server is shutting down. If the error recurs after the server is restarted, contact Customer Support Services. 0 0
6537 The .NET Framework common language runtime was shut down by user code, such as in a user-defined function or CLR type. SQL Server is shutting down. Environment.Exit should not be used to exit the process. If the intent is to return an integer to indicate failure, use a scalar function or an output parameter instead. 0 0
6538 .NET Framework execution was aborted because of stack overflow. %.*ls 0 0
6539 Invalid serialization format (Format.Unknown) for type '%.*ls.%.*ls'. 0 0
6540 The assembly name '%.*ls' being registered has an illegal name that duplicates the name of a system assembly. 0 0
6541 ALTER ASSEMBLY failed because assembly '%.*ls' has more than one file associated with it. Use ALTER ASSEMBLY DROP FILE to remove extra files. 0 0
6542 Can not create object because %ls is a generic type. 0 0
6543 .NET Framework execution was aborted. The UDP/UDF/CLR type did not end thread affinity. 0 0
6544 %s ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is malformed or not a pure .NET assembly. %.*ls 0 0
6545 Enabling of execution statistics SET options is not allowed from within CLR procedure or function. 0 0
6546 Could not impersonate the execution context during the execution of '%.*ls'. 0 0
6547 An error occurred while getting method, property or field information for "%ls" of class "%ls" in assembly "%.*ls". 0 0
6548 CREATE ASSEMBLY failed because the assembly references assembly '%.*ls', which is owned by another user. 0 0
6549 A .NET Framework error occurred during execution of user defined routine or aggregate '%.*ls': %ls. User transaction, if any, will be rolled back. 0 0
6550 %s failed because parameter counts do not match. 0 0
6551 %s for "%.*ls" failed because T-SQL and CLR types for return value do not match. 0 0
6552 %s for "%.*ls" failed because T-SQL and CLR types for parameter "%.*ls" do not match. 0 0
6553 %s failed because of an invalid .NET Framework calling convention. Use the default .NET Framework calling convention. 0 0
6554 SQL assembly name '%.*ls', and .NET Framework assembly name '%.*ls' do not match. Assembly names must match. 0 0
6555 Assembly '%.*ls' already exists for owner '%.*ls' in database '%.*ls'. 0 0
6556 %s failed because it could not find type '%s' in assembly '%s'. 0 0
6557 %s failed because type '%s' does not conform to %s specification due to field '%s'. 0 0
6558 %s failed because type '%s' does not conform to %s specification due to method '%s'. 0 0
6559 Could not find type ID %d in database %.*ls. This is due to a schema inconsistency. 0 0
6560 Assembly "%.*ls" is a system assembly. This operation is permitted only with user assemblies. 0 0
6561 Could not find file '%s' in directory '%s%s'. 0 0
6562 Version mismatch between files '%s' (%d.%d.%d) and '%s' (%d.%d.%d). 0 0
6563 Method, property or field '%ls' in class '%ls' in assembly '%.*ls' has invalid return type. 0 0
6564 The method '%ls' in class '%ls' in assembly '%.*ls' has some invalid arguments. Value of type '%ls' is not valid for argument number %d. 0 0
6565 %s ASSEMBLY failed because the assembly source parameter %d is not a valid assembly. 0 0
6566 %s ASSEMBLY failed because the assembly source parameter %d is not a valid expression. 0 0
6567 %s failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, System.Nullable, void. 0 0
6568 A .NET Framework error occurred while getting information from class "%.*ls" in assembly "%.*ls": %ls. 0 0
6569 '%.*ls' failed because parameter %d is not allowed to be null. 0 0
6570 Method '%ls' of class '%ls' in assembly '%.*ls' is generic. Generic methods are not supported. 0 0
6571 Class '%ls' in assembly '%.*ls' is generic. Generic types are not supported. 0 0
6572 More than one method, property or field was found with name '%ls' in class '%ls' in assembly '%.*ls'. Overloaded methods, properties or fields are not supported. 0 0
6573 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not static. 0 0
6574 Method, property or field '%ls' of class '%ls' in assembly '%.*ls' is not public. 0 0
6575 Assembly names should be less than %d characters. Assembly name '%.*ls' is too long. 0 0
6576 Type '%ls' in assembly '%ls' is not public. 0 0
6577 CREATE TYPE failed because type '%s' does not conform to CLR type specification due to interface '%s'. 0 0
6578 Invalid attempt to continue operation after a severe error. 0 0
6579 Alter assembly from '%ls' to '%ls' is not a compatible upgrade. 0 0
6580 Declarations do not match for parameter %d. .NET Framework reference and T-SQL OUTPUT parameter declarations must match. 0 0
6581 Could not find assembly '%.*ls' in directory '%.*ls'. 0 0
6582 Assembly '%.*s' is not visible for creating SQL objects. Use ALTER ASSEMBLY to change the assembly visibility. 0 0
6583 Assembly '%.*s' cannot be used for creating SQL objects because it is a system assembly. 0 0
6584 Property or field '%ls' for type '%ls' in assembly '%ls' is not static 0 0
6585 Could not impersonate the client during assembly file operation. 0 0
6586 Assembly '%.*ls' could not be installed because existing policy would keep it from being used. 0 0
6587 Assembly reference '%ls' was redirected by external policy to '%ls' 0 0
6588 Assembly file operations are not allowed for Windows NT users activated by SETUSER. 0 0
6589 DROP ASSEMBLY failed because the specified assemblies are referenced by assembly '%ls'. 0 0
6590 DROP ASSEMBLY failed because '%ls' is referenced by object '%ls'. 0 0
6591 %s for "%.*ls" failed because first parameter of "%.*ls" method must be of type System.Object. 0 0
6592 Could not find property or field '%ls' for type '%ls' in assembly '%ls'. 0 0
6593 Property or field '%ls' for type '%ls' in assembly '%ls' is static. 0 0
6594 Could not read from property '%ls' for type '%ls' in assembly '%ls' because it does not have a get accessor. 0 0
6595 Could not assign to property '%ls' for type '%ls' in assembly '%ls' because it is read only. 0 0
6596 %s ASSEMBLY failed because assembly '%ls' is a system assembly. Consider creating a user assembly to wrap desired functionality. 0 0
6597 CREATE %s failed. 0 0
6598 DROP ASSEMBLY failed because '%ls' is referenced by CLR type '%ls'. 0 0
6599 Found an empty native serialization class '%.*ls'. Empty native serialization classes are not allowed. 0 0
6600 XML error: %.*ls 0 0
6601 The XML parse error 0x%x occurred on line number %d, near the XML text "%.*ls". 0 0
6602 The error description is '%.*ls'. 0 0
6603 XML parsing error: %.*ls 0 0
6605 %.*ls: Failed to obtain an IPersistStream interface on the XML text. 0 0
6607 %.*ls: The value supplied for parameter number %d is invalid. 0 0
6608 Failed to instantiate class "%ls". Verify that Msxmlsql.dll exists in the SQL Server installation. 0 0
6609 Invalid data type for the column "%ls". Allowed data types are CHAR/VARCHAR, NCHAR/NVARCHAR, TEXT/NTEXT, and XML. 0 0
6610 Failed to load Msxmlsql.dll. 0 0
6611 The XML data type is damaged. 0 0
6613 Specified value '%ls' already exists. 0 0
6621 XML encoding or decoding error occurred with object name '%.*ls'. 0 0
6622 Invalid data type for column "%ls". The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml. 0 0
6623 Column '%ls' contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar. 0 0
6624 XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents. 0 0
6625 Could not convert the value for OPENXML column '%ls' to sql_variant data type. The value is too long. Change the data type of this column to text, ntext or image. 0 0
6626 Unexpected end of data stream. 0 0
6627 The size of the data chunk that was requested from the stream exceeds the allowed limit. 0 0
6628 %.*ls can only process untyped XML. Cast the input value to XML or to a string type. 0 0
6629 The result of the column expression for column "%ls" is not compatible with the requested type "XML". The result must be an element, text node, comment node, processing instruction, or document node. 0 0
6630 Element-centric mapping must be used with OPENXML when one of the columns is of type XML. 0 0
6631 The requested OpenXML document is currently in use by another thread, and cannot be used. 0 0
6632 Invalid data type for the column "%ls". CLR types cannot be used in an OpenXML WITH clause. 0 0
6633 The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version "%d.%d.%d". Require version "%d.%d.%d". 0 0
6634 OpenXML cannot be used as the target of a DML or OUTPUT INTO operation. 0 0
6700 XQuery: The ' %ls' operation is not supported. 0 0
6701 The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index. 0 0
6716 XML Node ID is invalid. Re-build the database if the problem persists. 0 0
6717 XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy. 0 0
6718 XQuery: Invalid ordpath string: "%s" 0 0
6739 XQuery: SQL type '%s' is not supported in XQuery. 0 0
6743 XQuery: The maximum allowed depth in XML instances is %d levels. One of the paths in the query tries to access nodes at a lower level. 0 0
6744 XQuery: One of the paths specified in the query is too deep. The maximum allowed depth is %d levels. 0 0
6745 XQuery: Internal compiler error. 0 0
6800 FOR XML AUTO requires at least one table for generating XML tags. Use FOR XML RAW or add a FROM clause with a table name. 0 0
6801 FOR XML EXPLICIT requires at least three columns, including the tag column, the parent column, and at least one data column. 0 0
6802 FOR XML EXPLICIT query contains the invalid column name '%.*ls'. Use the TAGNAME!TAGID!ATTRIBUTENAME[!..] format where TAGID is a positive integer. 0 0
6803 FOR XML EXPLICIT requires the first column to hold positive integers that represent XML tag IDs. 0 0
6804 FOR XML EXPLICIT requires the second column to hold NULL or nonnegative integers that represent XML parent tag IDs. 0 0
6805 FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed. 0 0
6806 Undeclared tag ID %d is used in a FOR XML EXPLICIT query. 0 0
6807 Undeclared parent tag ID %d is used in a FOR XML EXPLICIT query. 0 0
6808 XML tag ID %d could not be added. The server memory resources may be low. 0 0
6809 Unnamed tables cannot be used as XML identifiers as well as unnamed columns cannot be used for attribute names. Name unnamed columns/tables using AS in the SELECT statement. 0 0
6810 Column name '%.*ls' is repeated. The same attribute cannot be generated more than once on the same XML tag. 0 0
6811 FOR XML is incompatible with COMPUTE expressions. Remove the COMPUTE expression. 0 0
6812 XML tag ID %d that was originally declared as '%.*ls' is being redeclared as '%.*ls'. 0 0
6813 FOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS, NMTOKEN, and/or NMTOKENS in column name '%.*ls'. 0 0
6814 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS require attribute names in '%.*ls'. 0 0
6815 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be hidden in '%.*ls'. 0 0
6816 In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in '%.*ls'. 0 0
6817 FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name '%.*ls'. 0 0
6819 The FOR XML clause is not allowed in a %ls statement. 0 0
6820 FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'. 0 0
6821 GROUP BY and aggregate functions are currently not supported with FOR XML AUTO. 0 0
6824 In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid. 0 0
6825 ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML. 0 0
6826 Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after the element to which they belong. 0 0
6827 FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column '%.*ls' declares another XMLTEXT column that is not permitted. 0 0
6828 XMLTEXT column '%.*ls' must be of a string data type or of type XML. 0 0
6829 FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column '%.*ls'. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax. 0 0
6830 FOR XML AUTO could not find the table owning the following column '%.*ls' to create a URL address for it. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the 'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax. 0 0
6831 FOR XML AUTO requires primary keys to create references for '%.*ls'. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form if no primary keys exist. 0 0
6832 FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary. 0 0
6833 Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requires parent tags to be opened first. Check the ordering of the result set. 0 0
6834 XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag and its attributes. 0 0
6835 FOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once. 0 0
6836 FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls' to precede element-centric IDREFS/NMTOKEN fields. 0 0
6838 Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either specify ELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive. 0 0
6839 FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that has IDREFS or NMTOKENS fields. 0 0
6840 Neither XMLDATA nor XMLSCHEMA supports namespace elements or attributes such as '%.*ls'. Run the SELECT FOR XML statement without it or remove the namespace prefix declaration. 0 0
6841 FOR XML could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data using FOR XML, convert it to binary, varbinary or image data type and use the BINARY BASE64 directive. 0 0
6842 Could not serialize the data for node '%.*ls' because it contains a character (0x%04X) which is not allowed in XML. To retrieve this data convert it to binary, varbinary or image data type 0 0
6843 FOR XML EXPLICIT: XML data types and CLR types cannot be processed as CDATA in column name '%.*ls'. Consider converting XML to a string type. Consider converting CLR types to XML and then to a string type. 0 0
6844 Two (or more) elements named '%.*ls' are of different types and not direct siblings in the same level. 0 0
6845 Two (or more) elements named '%.*ls' are optional in the same level. Consider making them direct siblings or map NULL to xsi:nil 0 0
6846 XML name space prefix '%.*ls' declaration is missing for FOR XML %.*ls name '%.*ls'. 0 0
6847 The column '%.*ls' is of type sql_variant, which is not supported in attribute-centric FOR XML, with XML Schema. 0 0
6848 XMLDATA does not support the mapping of the type of column '%.*ls' to an XDR type. Please use XMLSCHEMA instead for AUTO and RAW mode. 0 0
6849 FOR XML PATH error in column '%.*ls' - '//' and leading and trailing '/' are not allowed in simple path expressions. 0 0
6850 %.*ls name '%.*ls' contains an invalid XML identifier as required by FOR XML; '%c'(0x%04X) is the first character at fault. 0 0
6851 Column '%.*ls' has invalid data type for attribute-centric XML serialization in FOR XML PATH. 0 0
6852 Attribute-centric column '%.*ls' must not come after a non-attribute-centric sibling in XML hierarchy in FOR XML PATH. 0 0
6853 Column '%.*ls': the last step in the path can't be applied to XML data type or CLR type in FOR XML PATH. 0 0
6854 Invalid column alias '%.*ls' for formatting column as XML processing instruction in FOR XML PATH - it must be in 'processing-instruction(target)' format. 0 0
6855 Inline schema is not supported with FOR XML PATH. 0 0
6856 FOR XML row XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault. 0 0
6857 FOR XML root XML tag name contains an invalid XML identifier; '%c'(0x%04X) is the first character at fault. 0 0
6858 XML schema URI contains character '%c'(0x%04X) which is not allowed in XML. 0 0
6859 Row tag name is only allowed with RAW or PATH mode of FOR XML. 0 0
6860 FOR XML directive XMLDATA is not allowed with ROOT directive or row tag name specified. 0 0
6861 Empty root tag name can't be specified with FOR XML. 0 0
6862 Empty FOR XML target inline schema URI is not allowed. 0 0
6863 Row tag omission (empty row tag name) is not compatible with XMLSCHEMA FOR XML directive. 0 0
6864 Row tag omission (empty row tag name) cannot be used with attribute-centric FOR XML serialization. 0 0
6865 FOR XML does not support CLR types - cast CLR types explicitly into one of the supported types in FOR XML queries. 0 0
6866 Use of a system reserved XML schema URI is not allowed. 0 0
6867 'xmlns' is invalid in XML tag name in FOR XML PATH, or when WITH XMLNAMESPACES is used with FOR XML. 0 0
6868 The following FOR XML features are not supported with WITH XMLNAMESPACES list: EXPLICIT mode, XMLSCHEMA and XMLDATA directives. 0 0
6869 Attempt to redefine namespace prefix '%.*ls' 0 0
6870 Prefix '%.*ls' used in WITH XMLNAMESPACES clause contains an invalid XML identifier. '%c'(0x%04X) is the first character at fault. 0 0
6871 Prefix '%.*ls' used in WITH XMLNAMESPACES is reserved and cannot be used as a user-defined prefix. 0 0
6872 XML namespace prefix 'xml' can only be associated with the URI http://www.w3.org/XML/1998/namespace. This URI cannot be used with other prefixes. 0 0
6873 Redefinition of 'xsi' XML namespace prefix is not supported with ELEMENTS XSINIL option of FOR XML. 0 0
6874 Empty URI is not allowed in WITH XMLNAMESPACES clause. 0 0
6875 URI '%.*ls' used in WITH XMLNAMESPACES is invalid. '%c'(0x%04X) is the first character at fault. 0 0
6876 URI used in WITH XMLNAMESPACES is too long. The maximum length is %d characters. 0 0
6877 Empty namespace prefix is not allowed in WITH XMLNAMESPACES clause. 0 0
6878 FORXML XMLSCHEMA cannot be used with a typed XML column whose schema collection is empty. 0 0
6879 'xml' is an invalid XML processing instruction target. Possible attempt to construct XML declaration using XML processing instruction constructor. XML declaration construction with FOR XML is not supported. 0 0
6901 XML Validation: XML instance must be a document. 0 0
6902 XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support the use of the pattern or enumeration facet on lists of type QName. 0 0
6903 XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support inclusion of ID, QName, or list of QName among the member types of a union type. 0 0
6904 XML Validation: Found duplicate attribute '%s'. Location: %s 0 0
6905 XML Validation: Attribute '%s' is not permitted in this context. Location: %s 0 0
6906 XML Validation: Required attribute '%s' is missing. Location: %s 0 0
6907 Namespace URI too long: '%.*ls'. 0 0
6908 XML Validation: Invalid content. Expected element(s): %s. Location: %s 0 0
6909 XML Validation: Text node is not allowed at this location, the type was defined with element only content or with simple content. Location: %s 0 0
6910 XML Validation: Invalid definition for type '%ls'. SQL Server does not currently support restriction of union types. 0 0
6911 XML Validation: Found duplicate element '%s' in all content model. Location: %s 0 0
6912 XML Validation: Element '%s' found in text only content model. Location: %s 0 0
6913 XML Validation: Declaration not found for element '%s'. Location: %s 0 0
6914 XML Validation: Type definition for type '%s' was not found, type definition is required before use in a type cast. Location: %s 0 0
6915 Element or attribute name too long: '%.*ls'. 0 0
6916 XML Validation: The content model of type or model group '%s' is ambiguous and thus violates the unique particle attribution constraint. Consult SQL Server Books Online for more information. 0 0
6917 XML Validation: Element '%ls' may not have xsi:nil="true" because it was not defined as nillable or because it has a fixed value constraint. Location: %ls 0 0
6918 XML Validation: Element '%s' must not have character or element children, because xsi:nil was set to true. Location: %s 0 0
6919 XML Validation: The type of element '%s' is abstract. Instantiation requires the use of xsi:type to specify a non-abstract type. Location: %s 0 0
6920 Invalid definition for type '%ls'. Cannot specify use="prohibited" for attribute '%ls' because there is no corresponding attribute in the base type. 0 0
6921 XML Validation: Element or attribute '%s' was defined as fixed, the element value has to be equal to value of 'fixed' attribute specified in definition. Location: %s 0 0
6922 XML Validation: Not able to resolve namespace for prefix:'%.*ls' 0 0
6923 XML Validation: Unexpected element(s): %s. Location: %s 0 0
6924 XML Validation: Text '%.*ls' found in attribute-only content model. Location: %s 0 0
6925 Invalid definition for element '%ls'. SQL Server does not currently permit additions to existing substitution groups via ALTER XML SCHEMA COLLECTION. 0 0
6926 XML Validation: Invalid simple type value: '%s'. Location: %s 0 0
6927 XML Validation: Invalid simple type value: '%ls'. 0 0
6928 XML Validation: XML instances of the content model of type or model group '%ls' can be validated in multiple ways and are not supported. 0 0
6929 XML Validation: Invalid QName for xsi:type attribute '%.*ls'. 0 0
6930 XML Validation: ID constraint check failed. Found attribute named '%.*ls' with duplicate ID value '%.*ls'. Location: %s 0 0
6931 XML Validation: IDREF constraint check failed. Found attribute named '%.*ls' with reference to ID value '%.*ls', which does not exist 0 0
6932 Invalid definition for element or attribute '%s'. Value constraints on components of type ID are not allowed. 0 0
6933 XML Validation: Invalid simple type operation, inserting into simple type is not permitted. Location: %s 0 0
6934 XML Validation: Element '%s' requires substitution, because it was defined as abstract. Location: %s 0 0
6935 XML Validation: ID or IDREF attribute exceeded the allowed maximum length. Location: %s 0 0
6936 XML Validation: Invalid cast for element '%s' from type '%s' to type '%s'. Location: %s 0 0
6937 XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on non-string types or range restrictions or enumerations on floating-point types. Location: %ls 0 0
6938 XML Validation: The canonical form of the value '%ls' is not valid according to the specified type. This can result from the use of pattern facets on non-string types or range restrictions or enumerations on floating-point types. 0 0
6939 XML Validation: The element '%ls' is mixed content with a fixed value and therefore not allowed to have element content. Location: %ls 0 0
6940 Invalid component named '%s' found in global scope. Only elements, attributes, types and groups can be defined in global context 0 0
6941 Invalid type definition for type '%s', types with complex content can only be derived from base types which have complex content 0 0
6942 Invalid type definition for type '%s', types with simple content can only be derived from base types which have simple content 0 0
6943 Invalid type definition for type '%s', the derivation was illegal because 'final' attribute was specified on the base type 0 0
6944 Invalid type definition for type '%s', '%s' facet is not restricting the value space 0 0
6945 Invalid facet value for facet '%s' in type definition '%s' 0 0
6946 Invalid type definition for type '%s', 'minLength' can not be greater than 'maxLength' 0 0
6947 XML Validation: Multiple ID attributes found on a single element. Location: %s 0 0
6948 Invalid type definition for type '%s', 'minLength' can not be greater than 'Length' 0 0
6949 Invalid type definition for type '%s', 'Length' can not be greater than 'maxLength' 0 0
6950 Invalid type definition for type '%s', 'fractionDigits' can not be greater than 'totalDigits' 0 0
6951 Invalid type definition for type '%s', 'minInclusive' must be less than or equal to 'maxInclusive' and less than 'maxExclusive' 0 0
6952 Invalid type definition for type '%s', 'minExclusive' must be less than or equal to 'maxExclusive' and less than 'maxInclusive' 0 0
6953 Invalid type definition for type '%s', recursive type definitions are not allowed 0 0
6954 Invalid group definition for group '%s', recursive group definitions are not allowed 0 0
6955 Invalid attribute definition for attribute '%s', attributes type has to be simple type 0 0
6956 Invalid type definition for type '%s', fixed facet '%s' can not be redefined to a different value. 0 0
6957 Invalid element definition, element '%s' is not valid derivation of element '%s' 0 0
6958 Invalid definition for type '%s'. An 'all' group may not appear as the child or parent of any other model group, it must have minOccurs = maxOccurs = 1, its child elements must have maxOccurs = 1 0 0
6959 Invalid definition, top level group definitions can not have model groups as siblings 0 0
6960 Component '%s' is outside of allowed range. Maximum for 'fractionDigits' is 10 and maximum number of digits for non fractional part is 28 0 0
6961 The system limit on the number of XML types has been reached. Redesign your database to use fewer XML types. 0 0
6962 'default' and 'fixed' values are not allowed on element of this type: '%s' 0 0
6963 'Default' or 'Fixed' value is longer than allowed, maximum length allowed is 4000 characters : '%s' 0 0
6964 Facet value is longer than allowed, maximum length allowed is 4000 characters : '%s' 0 0
6965 XML Validation: Invalid content. Expected element(s): %s. Found: element '%s' instead. Location: %s. 0 0
6966 Warning: Type '%s' is restricted by a facet '%s' that may impede full round-tripping of instances of this type 0 0
6967 Invalid type definition for type '%s'. The base and derived types must have the same value for 'mixed' unless deriving by restriction, in which case 'false' is always permitted for the derived type. 0 0
6968 Invalid type definition for type '%s'. Complex types cannot restrict simple types 0 0
6969 ID/IDREF validation consumed too much memory. Try reducing the number of ID and IDREF attributes. Rearranging the file so that elements with IDREF attributes appear after the elements which they reference may also be helpful. 0 0
6970 Invalid type definition for type '%s'. No type may have more than one attribute of any type derived from ID. 0 0
6971 Invalid type definition for type '%s'. Type contains attribute '%s' which is not allowed in base type. 0 0
6972 Invalid redefinition of attribute '%s' in type '%s'. Must be of a type which is a valid restriction of the corresponding attribute in the base type. 0 0
6973 Invalid redefinition of attribute '%s' in type '%s'. Must be required in the derived type if it is required in the base type. 0 0
6974 Invalid redefinition of attribute '%s' in type '%s'. Must be prohibited in the derived type if it is prohibited in the base type. 0 0
6975 Invalid redefinition of attribute '%s' in type '%s'. Must be fixed to the same value as in the derived type. 0 0
6976 Invalid redefinition of attribute '%s' in type '%s'. Derivation by extension may not redefine attributes. 0 0
6977 Invalid member type '%s' in union type '%s'. Unions may not have complex member types. 0 0
6978 Invalid item type for list type '%s'. The item type of a list may not itself be a list, and types derived from ID may not be used as item types in this release. 0 0
6979 Invalid restriction for type '%s'. The element in the restricted type must have the same name as and a more restrictive type than the corresponding element in the base type. 0 0
6980 Invalid restriction for type '%s'. The particle in the restricted type may not have an occurrence range more permissive than that of the corresponding particle in the base type. 0 0
6981 Invalid restriction for type '%s'. The element in the restricted type may not be nillable if the corresponding element in the base type is not. 0 0
6982 Invalid restriction for type '%s'. The element in the restricted type must be fixed to the same value as the corresponding element in the derived type. 0 0
6983 Invalid restriction for type '%s'. The element in the restricted type may not have a 'block' value more permissive than the corresponding element in the base type. 0 0
6984 Invalid restriction for type '%s'. The element in the restricted type must be in one of the namespaces allowed by the base type's wildcard. 0 0
6985 Invalid restriction for type '%s'. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard in the base type, and the processContents may not be more permissive. 0 0
6986 Invalid restriction for type '%s'. The effective total range of the model group in the restricted type must be a valid restriction of the occurrence range of the wildcard in the base type. 0 0
6987 Invalid restriction for type '%s'. An 'all' particle may be restricted only by 'all', 'element', or 'sequence'. 0 0
6988 Invalid restriction for type '%s'. A 'choice' particle may be restricted only by 'element', 'choice', or 'sequence'. 0 0
6989 Invalid restriction for type '%s'. A 'sequence' particle may be restricted only by 'element' or 'sequence'. 0 0
6990 Invalid restriction for type '%s'. Invalid model group restriction. 0 0
6991 Invalid restriction for type '%s'. If the base type has empty content, then the derived type must as well, and if the derived type has empty content, then the base type must be emptiable. 0 0
6992 The content model of type '%s' contains two elements with the same name '%s' and different types, nullability, or value constraints. 0 0
6993 Value constraint on use of attribute '%s' must be consistent with value constraint on its declaration. 0 0
6994 Invalid restriction for type '%s'. The attribute wildcard in the restricted type must be a valid subset of the corresponding attribute wildcard in the base type, and the processContents may not be more permissive. 0 0
6995 Invalid definition for type or element '%s'. SQL Server does not permit the built-in XML Schema types 'ID' and 'IDREF' or types derived from them to be used as the type of an element or as the basis for derivation by extension. 0 0
6996 Invalid type definition for type '%s'. A type may not have both 'minInclusive' and 'minExclusive' or 'maxInclusive' and 'maxExclusive' facets. 0 0
6997 Invalid definition for element '%s'. An element which has a fixed value may not also be nillable. 0 0
6998 Invalid type definition: Type or content model '%s' is too complicated. It may be necessary to reduce the number of enumerations or the size of the content model. 0 0
6999 Invalid definition for element or attribute '%s'. Value constraints on components of type QName are not supported in this release. 0 0
28000 The decrypted session key has an unexpected size. 0 0
28001 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. 0 0
28002 Cannot start service broker manager. Operating system error: %ls. 0 0
28003 An internal service broker error occurred. Operating system error: %ls. 0 0
28004 This message could not be delivered because the '%S_MSG' action cannot be performed in the '%.*ls' state. 0 0
28005 An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls 0 0
28006 User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission. 0 0
28007 A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28008 The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}' is invalid. 0 0
28009 The crypto API has detected bad data while trying to perform a decryption operation. 0 0
28010 This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d. 0 0
28011 This message could not be delivered because its %S_MSG has expired or is invalid. 0 0
28012 The Service Broker in the target database is unavailable: '%S_MSG'. 0 0
28013 The service broker is administratively disabled. 0 0
28014 The database is in read-only mode. 0 0
28015 The database is in single-user mode. 0 0
28016 The message has been dropped because the service broker in the target database is unavailable: '%S_MSG'. 0 0
28017 The message has been dropped because the target service broker is unreachable. 0 0
28018 The database is a replica of a mirrored database. 0 0
28019 System error %d occurred while creating a new message element GUID for this forwarded message. 0 0
28020 Could not create user token for user %d in database %d. 0 0
28021 One or more messages could not be delivered to the local service targeted by this dialog. 0 0
28022 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid. 0 0
28023 An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired. 0 0
28024 The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid. 0 0
28025 The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal. 0 0
28026 Connection handshake failed. Not enough memory available. State %d. 0 0
28027 Connection handshake failed. There is no compatible %S_MSG. State %d. 0 0
28028 Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d. 0 0
28029 Connection handshake failed. Unexpected event (%d) for current context (%d). State %d. 0 0
28030 Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d. 0 0
28031 Connection handshake failed. An OS call failed: (%x) %ls. State %d. 0 0
28032 A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d. 0 0
28033 A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d. 0 0
28034 Connection handshake failed. The login '%.*ls' does not have CONNECT permission on the endpoint. State %d. 0 0
28035 Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d. 0 0
28036 Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d. 0 0
28037 Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d. 0 0
28038 Connection handshake failed. The handshake verification failed. State %d. 0 0
28039 Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d. 0 0
28040 A corrupted message has been received. The adjacent error message header is invalid. 0 0
28041 A corrupted message has been received. The encrypted payload offset is invalid (%d). 0 0
28042 A corrupted message has been received. The arbitration request header is invalid. 0 0
28043 A corrupted message has been received. The arbitration response header is invalid. 0 0
28044 A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28045 Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d. 0 0
28046 %S_MSG Login succeeded for user '%.*ls'. Authentication mode: %.*ls. %.*ls 0 0
28047 %S_MSG login attempt failed with error: '%.*ls'. %.*ls 0 0
28048 %S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls 0 0
28050 The session keys for this conversation could not be created or accessed. The database master key is required for this operation. 0 0
28051 Could not save a dialog session key. A master key is required in the database to save the session key. 0 0
28052 Cannot decrypt session key while regenerating master key with FORCE option. 0 0
28053 Service Broker could not upgrade conversation session keys in database '%.*ls' to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker. 0 0
28054 Service Broker needs to access the master key in the database '%.*ls'. Error code:%d. The master key has to exist and the service master key encryption is required. 0 0
28055 The certificate '%.*ls' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date. 0 0
28056 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'. 0 0
28057 Service Broker in database '%.*ls' has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete. 0 0
28058 Service Broker could not upgrade this conversation during a database upgrade operation. 0 0
28059 Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d. 0 0
28060 The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions. 0 0
28061 A corrupted message has been received. The adjacent message integrity check signature could not be validated. 0 0
28062 A corrupted message has been received. The signed dialog message header is invalid. 0 0
28063 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. 0 0
28064 A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28065 A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28066 A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28067 A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28068 A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d. 0 0
28069 Unexpected session key when encrypting a dialog message. 0 0
28070 Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d. 0 0
28072 A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds. 0 0
28073 An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds. 0 0
28074 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. 0 0
28075 The broker in the sender's database is in single user mode. Messages cannot be delivered while in single user mode. 0 0
28076 Could not query the FIPS compliance mode flag from registry. Error %ls. 0 0
28077 %S_MSG transport is running in FIPS compliance mode. This is an informational message only. No user action is required. 0 0
28078 The RC4 encryption algorithm is not supported when running in FIPS compliance mode. 0 0
28079 Connection handshake failed. The received SSPI packet is not of the expected direction. State %d. 0 0
28080 Connection handshake failed. The %S_MSG endpoint is not configured. State %d. 0 0
28081 Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d. 0 0
28082 Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d. 0 0
28083 The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys. 0 0
28084 An error occurred in Service Broker internal activation while trying to scan the user queue '%ls' for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required. 0 0
28085 The activated task was ended because the associated queue was dropped. 0 0
28086 The activated task was ended because either the queue or activation was disabled. 0 0
28087 The activated task was aborted because the invoked stored procedure '%ls' did not execute RECEIVE. 0 0
28088 The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possible output from the activation stored procedure. 0 0
28089 The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas. 0 0
28090 An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available. 0 0
28098 A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d. 0 0
28099 During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state. 0 0
28101 User '%.*ls\%.*ls' does not have permission to debug the requested client connection. 0 0
28102 Batch execution is terminated because of debugger request. 0 0
28201 SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found. 0 0
28102 Batch execution is terminated because of debugger request. 0 0
28201 SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found. 0 0
29001 To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO). 0 0
29003 Invalid parameter combinations. 0 0
29004 Unknown property specified: %s. 0 0