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