SQL Server Error Messages


General Error Message (Volume 3)

The below information can be seen from sys.messages table.

This helps to understand the error falls under which severity.

Msg_Id Severity Message

7999 16 Could not find any index named ‘%.*ls’ for table ‘%.*ls’. 8001 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid for the Sql Variant parameter.
8002 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (XML) has an invalid database or schema specified.
8003 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is %d.
8004 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. The RPC name is invalid. 8005 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter name is invalid.
8006 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d: The parameter status flags are invalid.
8007 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The chunking format is incorrect for a large object parameter of type 0x%02X. 8008 16 The number of params passed to sp_execute is not equal to the number of params used when the handle was prepared (%d). 8009 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X is unknown.
8010 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The RPC is marked with the metadata unchanged flag, but data type 0x%02X is different from the one sent last time.
8011 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (sql_variant) has an invalid length for type-specific metadata. 8012 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (sql_variant) has an invalid precision or scale for type-specific metadata. 8013 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (sql_variant) has an invalid instance length.
8014 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (sql_variant) has an invalid type for type-specific metadata. 8015 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X is an untyped NULL but is marked as an output parameter.
8016 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X has an invalid data length or metadata length.
8017 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X has an invalid precision or scale.
8018 16 Invalid parameter %d (‘%.*ls’): Data type 0x%02X is a deprecated large object, or LOB, but is marked as output parameter. Deprecated types are not supported as output parameters. Use current large object types instead.
8019 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type “0x%02X” (user-defined type) has an invalid user type specified. 8020 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type “0x%02X” (user-defined type) has an invalid length for serialization metadata.
8021 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type “0x%02X” (user-defined type) has an invalid database specified. 8022 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The supplied value is NULL and data type %.*ls cannot be NULL. Check the source data for invalid values.
8023 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The supplied value is not a valid instance of data type %.*ls. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater than precision.
8024 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type 0x%02X (sql_variant) has an invalid collation for type-specific metadata. 8025 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has a maximum length different from the one sent last time.
8026 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): The RPC is marked with the metadata unchanged flag, but data type 0x%02X has an actual length different from the one sent last time.
8027 16 The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %d (“%.*ls”): Data type “0x%02X” (user-defined type) has an invalid schema specified. 8028 16 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.
8101 16 An explicit value for the identity column in table ‘%.*ls’ can only be specified when a column list is used and IDENTITY_INSERT is ON. 8102 16 Cannot update identity column ‘%.*ls’.
8105 16 ‘%.*ls’ is not a user table. Cannot perform SET operation. 8106 16 Table ‘%.*ls’ does not have the identity property. Cannot perform SET operation.
8107 16 IDENTITY_INSERT is already ON for table ‘%.*ls.%.*ls.%.*ls’. Cannot perform SET operation for table ‘%.*ls’.
8108 16 Cannot add identity column, using the SELECT INTO statement, to table ‘%.*ls’, which already has column ‘%.*ls’ that inherits the identity property.
8109 16 Attempting to add multiple identity columns to table ‘%.*ls’ using the SELECT INTO statement.
8110 16 Cannot add multiple PRIMARY KEY constraints to table ‘%.*ls’.
8111 16 Cannot define PRIMARY KEY constraint on nullable column in table ‘%.*ls’.
8112 16 Cannot add more than one clustered index for constraints on table ‘%.*ls’.
8113 16 Incorrect use of the xml data type method ‘%.*ls’. A mutator method is expected in this context.
8114 16 Error converting data type %ls to %ls.
8115 16 Arithmetic overflow error converting %ls to data type %ls. 8116 16 Argument data type %ls is invalid for argument %d of %ls function.
8117 16 Operand data type %ls is invalid for %ls operator.
8118 16 Column ‘%.*ls.%.*ls’ is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause.
8119 16 Column ‘%.*ls.%.*ls’ is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause.
8120 16 Column ‘%.*ls.%.*ls’ is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. 8121 16 Column ‘%.*ls.%.*ls’ is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause. 8123 16 A correlated expression is invalid because it is not in a GROUP BY clause.
8124 16 Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression.
8125 16 An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated. 8126 16 Column “%.*ls.%.*ls” is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause.
8127 16 Column “%.*ls.%.*ls” is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause.
8128 10 Using ‘%s’ version ‘%s’ to execute extended stored procedure ‘%s’. This is an informational message only; no user action is required. 8129 16 The new disk size must be greater than %d. Consider using DBCC SHRINKDB.
8131 10 Extended stored procedure DLL ‘%s’ does not export
__GetXpVersion(). Refer to the topic “Backward Compatibility Details (Level 1) – Open Data Services” in the documentation for more information. 8132 10 Extended stored procedure DLL ‘%s’ reports its version is %d.%d. The expected version is %d.%d.
8133 16 None of the result expressions in a CASE specification can be NULL.
8134 16 Divide by zero error encountered.
8135 16 Table level constraint does not specify column list, table ‘%.*ls’.
8136 16 Duplicate columns specified in %ls constraint key list, table ‘%.*ls’.
8137 16 Incorrect use of the xml data type method ‘%.*ls’. A non-mutator method is expected in this context.
8138 16 More than 16 columns specified in foreign key column list, table ‘%.*ls’.
8139 16 Number of referencing columns in foreign key differs from number of referenced columns, table ‘%.*ls’.
8140 16 More than one key specified in column level %ls constraint, table ‘%.*ls’.
8141 16 Column %ls constraint for column ‘%.*ls’ references another column, table ‘%.*ls’.
8143 16 Parameter ‘%.*ls’ was supplied multiple times.
8144 16 Procedure or function %.*ls has too many arguments
specified.
8145 16 %.*ls is not a parameter for procedure %.*ls.
8146 16 Procedure %.*ls has no parameters and arguments were supplied.
8147 16 Could not create IDENTITY attribute on nullable column ‘%.*ls’, table ‘%.*ls’.
8148 16 More than one column %ls constraint specified for column ‘%.*ls’, table ‘%.*ls’.
8149 16 OLE Automation objects are not supported in fiber mode. 8150 16 Multiple NULL constraints were specified for column ‘%.*ls’, table ‘%.*ls’.
8151 16 Both a PRIMARY KEY and UNIQUE constraint have been defined for column ‘%.*ls’, table ‘%.*ls’. Only one is allowed.
8152 16 String or binary data would be truncated.
8153 10 Warning: Null value is eliminated by an aggregate or other SET operation.
8154 15 The table ‘%.*ls’ is ambiguous.
8155 15 No column was specified for column %d of ‘%.*ls’.
8156 15 The column ‘%.*ls’ was specified multiple times for ‘%.*ls’. 8158 15 ‘%.*ls’ has more columns than were specified in the column list.
8159 15 ‘%.*ls’ has fewer columns than were specified in the column list.
8160 15 A grouping function can only be specified when either CUBE or ROLLUP is specified in the GROUP BY clause.
8161 15 A grouping function argument does not match any of the expressions in the GROUP BY clause.
8162 16 The formal parameter “%.*ls” was not declared as an OUTPUT parameter, but the actual parameter passed in requested output. 8164 16 An INSERT EXEC statement cannot be nested.
8165 16 Invalid subcommand value %d. Legal range from %d to %d. 8166 16 Constraint name ‘%.*ls’ not permitted. Constraint names cannot begin with a number sign (#).
8167 16 The type of column “%.*ls” conflicts with the type of other columns specified in the UNPIVOT list.
8168 16 Cannot create two constraints named ‘%.*ls’. Duplicate constraint names are not allowed.
8169 16 Conversion failed when converting from a character string to uniqueidentifier.
8170 16 Insufficient result space to convert uniqueidentifier value to char.
8171 16 Hint ‘%ls’ on object ‘%.*ls’ is invalid.
8172 16 The argument %d of the xml data type method “%.*ls” must be a string literal.
8173 15 Incorrect syntax was used to invoke the xml data type method ‘%.*ls’.
8174 16 Schema lock with handle %d not found.
8175 10 Could not find table %.*ls. Will try to resolve this table name later.
8176 16 Resync procedure expects value of key ‘%.*ls’, which was not supplied.
8177 16 Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause.
8178 16 The parameterized query ‘%.*ls’ expects the parameter ‘%.*ls’, which was not supplied.
8179 16 Could not find prepared statement with handle %d.
8180 16 Statement(s) could not be prepared.
8181 16 Text for ‘%.*ls’ is missing from syscomments. The object must be dropped and re-created before it can be used.
8183 16 Only UNIQUE or PRIMARY KEY constraints can be created on computed columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that computed columns be persisted.
8184 16 Error in binarychecksum. There are no comparable columns in the binarychecksum input.
8185 16 Error expanding “*”: An incomparable column has been found in an underlying table or view.
8186 16 Function ‘%.*ls’ can be used only on user and system tables. 8187 16 The prepared handle %d is currently being used by another command (error state: %d).
8188 16 There is already a user-defined type for assembly type “%.*ls” on assembly “%.*ls”. Only one SQL type can be mapped to a given assembly type. CREATE TYPE fails.
8189 16 You do not have permission to run ‘%ls’.
8190 16 Cannot compile replication filter procedure without defining table being filtered.
8191 16 Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements.
8192 16 Replication filter procedures cannot have parameters. 8193 16 Cannot execute a procedure marked FOR REPLICATION.
8195 16 Cannot create “%.*ls” on “%.*ls”. Insert, Update, and Delete triggers can only be created on user tables and views.
8196 16 Duplicate column specified as ROWGUIDCOL.
8197 16 The object ‘%.*ls’ does not exist or is invalid for this operation.
8199 16 In EXECUTE , procname can only be a literal or variable of type char, varchar, nchar, or nvarchar.
8302 10 CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new development work, and plan to modify applications that currently use them. Use check constraints instead, which are created using the CHECK keyword of CREATE TABLE or ALTER TABLE.
8303 10 CREATE DEFAULT and DROP DEFAULT will be removed in a future version of SQL Server. Avoid using CREATE DEFAULT and DROP DEFAULT in new development work, and plan to modify applications that currently use them. Instead, use default definitions created using the DEFAULT keyword of ALTER TABLE or CREATE TABLE.
8304 10 INDEXKEY_PROPERTY will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use sys.index_columns instead. 8305 10 The TEXT IN ROW feature will be removed in a future version of SQL Server. Avoid using sp_tableoption for TEXT IN ROW option in new development work, and plan to modify applications that currently use the text in row option. The preferred method of storing large data is through use of the varchar(max), nvarchar(max) and varbinary(max) data types. 8306 10 Use of level0type with value ‘TYPE’ in procedure
sp_addextendedproperty, sp_updateextendedproperty and
sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server. Types are now schema scoped and hence use level0type with value ‘SCHEMA’ and level1type with value ‘TYPE’ for extended properties on TYPE. 8307 10 FILE_ID will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use the feature. Use FILE_IDEX instead. 8308 10 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.
8309 16 BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
8310 16 Cannot create (or open) named file mapping object ‘%ls’. SQL Server performance counters are disabled.
8311 16 Unable to map view of file mapping object ‘%ls’ into SQL Server process address space. SQL Server performance counters are disabled. 8312 16 Cannot create (or open) named mutex ‘%ls’. SQL Server performance counters are disabled.
8313 16 Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
8314 16 SQL Server performance object ‘%ls’ not found in registry. SQL Server performance counters are disabled.
8315 16 SQL Server performance counter ‘%ls’ not found in registry. SQL Server performance counters are disabled.
8316 16 Cannot open registry key ‘HKLM%ls’. SQL Server performance counters are disabled.
8317 16 Cannot query value ‘%ls’ associated with registry key ‘HKLM%ls’. SQL Server performance counters are disabled.
8318 16 There was a virtual memory allocation failure during performance counters initialization. SQL Server performance counters are disabled.
8319 16 Windows kernel object ‘%ls’ already exists. It’s not owned by the SQL Server service account. SQL Server performance counters are disabled.
8350 10 Use of NOLOCK or READUNCOMMITTED hints in the FROM clause of an UPDATE or DELETE statement on the target table of the statement (‘%.*ls’) is deprecated. These hints have no effect in this location. Microsoft recommends that you remove these hints from this statement. Support for these hints in this location will be removed in a future version of SQL Server.
8351 16 A trace control request could not be processed because invalid parameters were specified when events were registered. Confirm that the parameters are within valid ranges.
8352 16 Cannot find the requested trace template: id = %ls.
8353 16 Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server.
8354 16 Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls.
8355 16 Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.
8356 16 Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future.
8357 16 Event Tracing for Windows (ETW) failed to send event. This may be due to low resource conditions. The same send failure may not be reported in the future.
8358 16 Event Tracing for Windows (ETW) failed to send event. Event message size exceeds limit. The same send failure may not be reported in the future.
8359 16 SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported in the future. 8360 16 SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future.
8379 10 Old style RAISERROR (Format: RAISERROR integer string) will be removed in a future version of SQL Server. Avoid using this in new development work, and plan to modify applications that currently use it to use new style RAISERROR.
8380 10 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server ‘%.*ls’.
8381 10 SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) for ad hoc connection to SQL Server. 8382 10 Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version.
8383 10 Specifying HOLDLOCK as a table hint without parenthesis is a deprecated feature and will be removed in a future version.
8384 10 Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints.
8385 10 The select list of an aggregate indexed view must contain count_big(*) in 90 compatibility mode and higher.
8386 10 Use of hint “%.*ls” on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove the use of this hint. 8387 10 The indirect application of table hints to an invocation of a multi-statement table-valued function (TVF) through a view will be removed in a future version of SQL Server. Remove hints on references to view “%.*ls” because it references a multi-statement TVF.
8388 10 The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 8389 10 The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work and plan to modify applications that currently use it.
8390 10 The ‘::’ function calling syntax will be removed in a future version of SQL Server. Replace it with “sys.”.
8391 10 The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX <1p-name> ON {<3p-table-name> | <3p-view-name> } 8392 10 TEXTIMAGE_ON will be removed in a future version of SQL Server. Avoid using this syntax in new development work, and plan to modify applications that currently use it. The preferred method of storing large data is through the use of the varchar(max), nvarchar(max), and varbinary(max) data types.
8393 10 A future version of SQL Server may modify the behavior of the Transact-SQL timestamp data type to align it with the behavior defined in the standard. At that time, the current timestamp data type will be replaced with a rowversion data type.
8394 10 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. 8395 10 %ls; This Open Data Services function will be removed in a future version of SQL Server. Avoid using it in new development work, and plan to modify applications that currently use it.
8396 10 %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use %ls instead.
8397 10 The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types instead.
8398 10 The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. 8399 10 %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
8401 16 This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue ‘%.*ls’.
8402 16 The data type of the ‘%S_MSG’ in the ‘%S_MSG’ statement must be %s. The %s data type is not allowed.
8403 16 The message type ‘%.*ls’ is specified more than once. Remove the duplicate message type.
8404 16 The service contract ‘%.*ls’ is specified more than once. Remove the duplicate service contract.
8405 16 An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.
8407 16 Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.
8408 16 Target service ‘%.*ls’ does not support contract ‘%.*ls’. 8409 16 This message could not be delivered because the targeted service does not support the service contract. Targeted service: ‘%.*ls’, service contract: ‘%.*ls’.
8410 16 The conversation timer cannot be set beyond the
conversation’s lifetime.
8412 16 The service name ‘%.*ls’ is invalid. The name must not be longer than 256 characters, and must not be blank.
8417 16 The service contract name is NULL. Specify a service contract name.
8418 16 The conversation handle is missing. Specify a conversation handle.
8419 16 Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL.
8420 16 The conversation group is missing. Specify a conversation group.
8421 16 The service name is missing. Specify a service name. 8422 16 The error description is missing. Specify a description of the error.
8423 16 The service “%.*ls” is not found.
8424 16 The error code and error description are missing. Specify both the error code and description of the error.
8425 16 The service contract ‘%.*ls’ is not found.
8426 16 The conversation handle “%.*ls” is not found.
8427 16 The conversation endpoint is not in a valid state for END CONVERSATION. The current endpoint state is ‘%ls’.
8428 16 The message type “%.*ls” is not found.
8429 16 The conversation endpoint is not in a valid state for SEND. The current endpoint state is ‘%ls’.
8430 16 The message body failed the configured validation.
8431 16 The message type ‘%.*ls’ is not part of the service
contract.
8432 16 The message cannot be sent because the message type ‘%.*ls’ is marked SENT BY TARGET in the contract, however this service is an Initiator.
8433 16 The message body may not be NULL. A zero-length UNICODE or binary string is allowed.
8434 16 The message cannot be sent because the message type ‘%.*ls’ is marked SENT BY INTITIATOR in the contract, however this service is a Target.
8436 16 The conversation group “%.*ls” is not found.
8437 16 The message received was sent by a Target service, but the message type ‘%.*ls’ is marked SENT BY INITIATOR in the contract. 8438 16 The conversation endpoint is not in a valid state for MOVE CONVERSATION. The current endpoint state is ‘%ls’.
8439 16 The destination conversation group ‘%.*ls’ is invalid. 8440 23 The conversation group exists, but no queue exists.
Possible database corruption. Run DBCC CHECKDB.
8442 16 There is no Service Broker active in the database. Change to a database context that contains a Service Broker.
8443 23 The conversation with ID ‘%.*ls’ and initiator: %d
references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database.
8444 23 The service queue structure is inconsistent. Possible database corruption. Run DBCC CHECKDB.
8445 16 The conversation handle ‘%ls’ is referencing an invalid conversation ID ‘%ls’, initiator: %d.
8447 16 A RECEIVE statement that assigns a value to a variable must not be combined with data retrieval operations.
8450 16 Assignments in the RECEIVE projection are not allowed in conjunction with the INTO clause.
8457 16 The message received was sent by the initiator of the conversation, but the message type ‘%.*ls’ is marked SENT BY TARGET in the contract.
8458 16 The conversation endpoint is not in a valid state for BEGIN CONVERSATION TIMER. The current endpoint state is ‘%ls’.
8459 16 The message size, including header information, exceeds the maximum allowed of %d.
8460 16 The conversation endpoint with ID ‘%ls’ and is_initiator: %d is referencing the invalid conversation handle ‘%ls’.
8461 23 An internal service broker error detected. Possible database corruption. Run DBCC CHECKDB.
8462 16 The remote conversation endpoint is either in a state where no more messages can be exchanged, or it has been dropped.
8463 16 Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem. If the problem persists, the database may be damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database.
8468 16 Underlying service has been altered.
8469 16 Remote service has been altered.
8470 16 Remote service has been dropped.
8471 16 An SNI call failed during a Service Broker/Database
Mirroring transport operation. SNI error ‘%ls’.
8472 16 The remote service has sent a message that contains invalid header fields.
8475 16 The conversation endpoint with ID ‘%ls’ and is_initiator: %d has been dropped.
8477 16 An internal Service Broker error occurred (error = 0x%08x). This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems. The database may have been damaged. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data to repair the database.
8479 16 Used by test in failpoint simulation.
8487 16 The remote service contract has been dropped.
8489 16 The dialog has exceeded the specified LIFETIME.
8490 16 Cannot find the remote service ‘%.*ls’ because it does not exist.
8492 16 The service contract ‘%.*ls’ must have at least one message SENT BY INITIATOR or ANY.
8493 16 The alter of service ‘%.*ls’ must change the queue or at least one contract.
8494 16 You do not have permission to access the service ‘%.*ls’. 8495 16 The conversation has already been acknowledged by another instance of this service.
8498 16 The remote service has sent a message of type ‘%.*ls’ that is not part of the local contract.
8499 16 The remote service has sent a message body of type ‘%.*ls’ that does not match the message body encoding format. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
8501 16 MSDTC on server ‘%.*ls’ is unavailable.
8502 20 Unknown token ‘0x%x’ received from Microsoft Distributed Transaction Coordinator (MS DTC) .
8504 20 The import buffer for this transaction is not valid. 8506 20 Cannot change transaction state from %hs to %hs. The change requested is not valid.
8508 10 QueryInterface failed for “%ls”: %ls.
8509 20 Import of Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed: %ls.
8510 20 Enlist operation failed: %ls. SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.
8511 16 Unknown isolation level 0x%x requested from Microsoft Distributed Transaction Coordinator (MS DTC).
8512 20 Microsoft Distributed Transaction Coordinator (MS DTC) commit transaction acknowledgement failed: %hs.
8513 20 Microsoft Distributed Transaction Coordinator (MS DTC) end transaction acknowledgement failed: %hs.
8514 20 Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE acknowledgement failed: %hs.
8515 20 Microsoft Distributed Transaction Coordinator (MS DTC) global state is not valid.
8517 20 Failed to get Microsoft Distributed Transaction Coordinator (MS DTC) PREPARE information: %ls.
8518 16 Microsoft Distributed Transaction Coordinator (MS DTC) BEGIN TRANSACTION failed: %ls.
8519 16 Current Microsoft Distributed Transaction Coordinator (MS DTC) transaction must be committed by remote client.
8520 16 Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: %ls.
8521 20 This awakening state is not valid: slept in %hs; awoke in %hs.
8522 20 Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
8523 15 PREPARE TRAN statement not allowed on MSDTC transaction. 8524 16 The current transaction could not be exported to the remote provider. It has been rolled back.
8525 16 Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
8526 16 Cannot go remote while the session is enlisted in a
distributed transaction that has an active savepoint.
8527 16 An attempt to create a distributed transaction export token failed with this error: %ls. Contact your Microsoft Distributed Transaction Coordinator (MS DTC) system administrator.
8528 16 The commit of the Kernel Transaction Manager (KTM)
transaction failed: %d.
8529 16 Unable to extract the Kernel Transaction Manager (KTM) transaction handle from the Microsoft Distributed Transaction Coordinator (MS DTC) transaction: 0x%x.
8530 16 The Windows kernel transaction manager creation failed: 0x%x.
8531 16 The Windows kernel transaction manager failed to create the enlistment: 0x%08x.
8532 20 Error while reading resource manager notification from Kernel Transaction Manager (KTM): %d.
8533 20 Error while waiting for communication from Kernel
Transaction Manager (KTM): %d.
8534 21 The KTM RM for this database, %ls, failed to start: %d. 8535 16 A savepoint operation in the Windows transactional file system failed: 0x%x.
8536 16 Only single DB updates are allowed with FILESTREAM
operations.
8537 16 This transaction was aborted by Kernel Transaction Manager (KTM).
8538 16 The current isolation level is unsupported by the FileStream 0x%x.
8539 10 The distributed transaction with UOW %ls was forced to commit. MS DTC became temporarily unavailable and forced heuristic resolution of the transaction. This is an informational message only. No user action is required.
8540 10 The distributed transaction with UOW %ls was forced to rollback.
8541 10 System process ID %d tried to terminate the distributed transaction with Unit of Work ID %ls. This message occurs when the client executes a KILL statement on the distributed transaction.
8542 10 Spid %d tried to commit the distributed transaction with UOW %ls.
8543 10 Unable to commit a prepared transaction from the Microsoft Distributed Transaction Coordinator (MS DTC). Shutting down server to initiate resource manager (RM) recovery. When the RM recovers, it will query the transaction manager about the outcome of the in-doubt transaction, and commit or roll back accordingly.
8544 10 Unknown status of commit of a two-phase commit transaction. Shutting down server. Restart server to complete recovery.
8545 10 Unknown status ‘%d’ from Reenlist call in rm_resolve. 8546 10 Unable to load Microsoft Distributed Transaction Coordinator (MS DTC) library. This error indicates that MS DTC is not installed. Install MS DTC to proceed.
8547 10 Resource Manager Creation Failed: %ls
8548 10 DTC not initialized because it’s unavailable
8549 10 GetWhereaboutsSize call failed: %ls
8550 10 MS DTC initialization failed because the transaction manager address is invalid. The protocol element used to carry address information may be too large. A network protocol analyzer may provide additional information about the cause. Contact your application support provider or Microsoft Product Support Services.
8551 16 CoCreateGuid failed: %ls.
8552 20 RegOpenKeyEx of “%ls” failed: %ls.
8553 20 RegQueryValueEx of “%hs” failed: %ls.
8554 20 IIDFromString failed for %hs, (%ls).
8555 10 RegCloseKey failed: %ls
8556 10 Microsoft Distributed Transaction Coordinator (MS DTC) initialization failed due to insufficient memory. It may be necessary to change some server configuration options to make more memory available. 8557 10 The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
8558 20 RegDeleteValue of “%hs” failed: %ls.
8560 10 Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
8561 10 Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required. 8562 10 The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required.
8563 10 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.
8564 10 An attempt to connect to Microsoft Distributed Transaction Coordinator (MS DTC) will be skipped because the RPCSS service doesn’t appear to be started. Another attempt to connect to MS DTC will be made later. This is an informational message only. No user action is required. 8601 17 Internal Query Processor Error: The query processor could not obtain access to a required interface.
8602 16 Indexes used in hints must be explicitly included by the index tuning wizard.
8603 16 Invalid syntax for internal DBCC REPAIR statement.
8604 16 ALTER TABLE SWITCH statement failed. Table ‘%.*ls’ has a column level check constraint ‘%.*ls’ on column ‘%.*ls’ that is not loadable for semantic validation.
8605 10 Index creation operation will use %ld KB of memory specified in the advanced sp_configure option “min memory per query (KB)” instead of %lu KB specified in “index create memory (KB)” option because the former has to be smaller than the latter.
8606 17 This index operation requires %I64d KB of memory per DOP. The total requirement of %I64d KB for DOP of %lu is greater than the sp_configure value of %lu KB set for the advanced server configuration option “index create memory (KB)”. Increase this setting or reduce DOP and rerun the query.
8607 16 The table ‘%.*ls’ cannot be modified because one or more non-clustered indexes reside in a filegroup which is not online. 8616 10 The index hints for table ‘%.*ls’ were ignored because the table was considered a fact table in the star join.
8617 17 Invalid Query: CUBE and ROLLUP cannot compute distinct aggregates.
8618 16 The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. If the query has a GROUP BY or ORDER BY clause, consider reducing the number and/or size of the fields in the clause. Consider using prefix (LEFT()) or hash (CHECKSUM()) of fields for grouping or prefix for ordering. Note however that this will change the behavior of the query.
8619 16 The query processor could not produce a query plan because a worktable is required, and its minimum row size exceeds the maximum allowable of %d bytes. A typical reason why a worktable is required is a GROUP BY or ORDER BY clause in the query. Resubmit your query without the ROBUST PLAN hint.
8621 16 The query processor ran out of stack space during query optimization. Please simplify the query.
8622 16 Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
8623 16 The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
8624 16 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
8625 10 Warning: The join order has been enforced because a local join hint is used.
8628 17 A time out occurred while waiting to optimize the query. Rerun the query.
8630 17 Internal Query Processor Error: The query processor
encountered an unexpected error during execution.
8631 17 Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it. 8632 17 Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
8642 17 The query processor could not start the necessary thread resources for parallel query execution.
8644 16 Internal Query Processor Error: The plan selected for execution does not support the invoked given execution routine. 8645 17 A time out occurred while waiting for memory resources to execute the query. Rerun the query.
8646 21 Unable to find index entry in index ID %d, of table %d, in database ‘%.*ls’. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.
8648 20 Could not insert a row larger than the page size into a hash table. Resubmit the query using the ROBUST PLAN optimization hint. 8649 17 The query has been canceled because the estimated cost of this query (%d) exceeds the configured threshold of %d. Contact the system administrator.
8651 17 Could not perform the requested operation because the minimum query memory is not available. Decrease the configured value for the ‘min memory per query’ server configuration option.
8653 16 The query processor is unable to produce a plan for the table or view ‘%.*ls’ because the table resides in a filegroup which is not online.
8655 16 The query processor is unable to produce a plan because the index ‘%.*ls’ on table or view ‘%.*ls’ is disabled.
8660 16 Cannot create the clustered index “%.*ls” on view “%.*ls” because the select list of the view definition does not include all columns in the GROUP BY clause. Consider adding these columns to the select list. 8661 16 Cannot create the clustered index “%.*ls” on view “%.*ls” because the index key includes columns that are not in the GROUP BY clause. Consider eliminating columns that are not in the GROUP BY clause from the index key.
8662 16 Cannot create the clustered index “%.*ls” on view “%.*ls” because the view references an unknown value (SUM aggregate of nullable expression). Consider referencing only non-nullable values in SUM. ISNULL() may be useful for this.
8663 16 Cannot create the clustered index “%.*ls” on view “%.*ls” because its select list does not include COUNT_BIG(*). Consider adding COUNT_BIG(*) to the select list.
8665 16 Cannot create the clustered index “%.*ls” on view “%.*ls” because no row can satisfy the view definition. Consider eliminating contradictions from the view definition.
8668 16 Cannot create the clustered index ‘%.*ls’ on view ‘%.*ls’ because the select list of the view contains an expression on result of aggregate function or grouping column. Consider removing expression on result of aggregate function or grouping column from select list. 8669 16 The attempt to maintain the indexed view “%.*ls” failed because it contains an expression on aggregate results, or because it contains a ranking or aggregate window function. Consider dropping the clustered index on the view, or changing the view definition. 8670 16 Query optimizer reached the internal limit of the maximum number of views that can be used during optimization.
8671 16 The attempt to maintain the indexed view “%.*ls” failed because of the ignore_dup_key option on index “%.*ls”. Drop the index or re-create it without the ignore_dup_key index option.
8680 17 Internal Query Processor Error: The query processor
encountered an unexpected error during the processing of a remote query phase.
8682 16 SELECT via cursor failed because in XML plan provided to USE PLAN hint, neither Populate nor Fetch plans are provided, and at least one must be present. For best likelihood of successful plan forcing, use an XML cursor plan captured from SQL Server without modification.
8683 16 Could not force query plan because XML showplan provided in USE PLAN hint contains invalid Star Join specification. Consider specifying a USE PLAN hint that contains an unmodified XML showplan produced by SQL Server. This may allow you to force the plan.
8684 16 A query plan could not be found because optimizer exceeded number of allowed operations while searching for plan specified in USE PLAN hint. First consider removing USE PLAN hint. Then if necessary consider (1) updating statistics, (2) using other hints such as join hints, index hints, or the OPTIMIZE FOR hint, (3) rewriting query or breaking it down into two or more separate queries.
8685 16 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.
8686 16 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.
8687 16 Cursor plan failed because it is not possible to force the plan for a cursor of type other than FAST_FORWARD or STATIC with a USE PLAN hint. Consider removing USE PLAN hint and updating statistics or using different hints to influence query plan choice.
8688 16 Cursor plan forcing failed because in XML plan provided to USE PLAN, required element %ls is missing under element. Consider using an XML cursor plan captured from SQL Server without modification.
8689 16 Database ‘%.*ls’ specified in the use plan hint does not exist.
8690 16 Query cannot be compiled because USE PLAN hint conflicts with hint %ls. Consider removing hint %ls.
8691 16 Query cannot be compiled because USE PLAN hint conflicts with SET %ls ON. Consider setting %ls OFF.
8692 16 %ls statement could not be executed because USE PLAN hint not supported for %ls. USE PLAN is only supported for SELECT. 8693 16 Cannot compile query because combination of LogicalOp = ‘%ls’, PhysicalOp = ‘%ls’, and sub_element = ‘%ls’ under RelOp element in XML plan in USE PLAN hint is not valid. Use a recognized combination instead. Consider using an automatically generated XML plan without modification.
8694 16 Cannot execute query because USE PLAN hint conflicts with use of distributed query or full-text operations. Consider removing USE PLAN hint.
8695 16 Cannot execute query because of incorrectly formed XML plan in USE PLAN hint. Verify that XML plan is a legal plan suitable for plan forcing. See Books Online for additional details.
8696 16 Cannot run query because of improperly formed Spool element with parent RelOp with NodeId %d in XML plan in USE PLAN hint. Verify that each Spool element’s parent RelOp has unique NodeId attribute, and each Spool element has either a single RelOp sub-element, or a PrimaryNodeId attribute, but not both. PrimaryNodeId of Spool must reference NodeId of an existing RelOp with a Spool sub-element. Consider using unmodified XML showplan as USE PLAN hint.
8697 16 Cannot run query because in XML plan provided to USE PLAN, element %ls must have %d %ls nodes as children, but has %d.
8698 16 Query processor could not produce query plan because USE PLAN hint contains plan that could not be verified to be legal for query. Remove or replace USE PLAN hint. For best likelihood of successful plan forcing, verify that the plan provided in the USE PLAN hint is one generated automatically by SQL Server for the same query.
8699 16 Cannot run query because it contains more than one USE PLAN hint. Use at most one USE PLAN hint.
8901 16 Table error: Object ID %d has inconsistent metadata. This error cannot be repaired and prevents further processing of this object. 8902 17 Memory allocation error during DBCC processing.
8903 16 Extent %S_PGID in database ID %d is allocated in both GAM %S_PGID and SGAM %S_PGID.
8904 16 Extent %S_PGID in database ID %d is allocated by more than one allocation object.
8905 16 Extent %S_PGID in database ID %d is marked allocated in the GAM, but no SGAM or IAM has allocated it.
8906 16 Page %S_PGID in database ID %d is allocated in the SGAM %S_PGID and PFS %S_PGID, but was not allocated in any IAM. PFS flags ‘%hs’. 8907 16 Indexed view ‘%.*ls’ (object ID %d) contains rows not produced by the view definition. Refer to Books Online for more information on this error. This does not necessarily represent an integrity issue with the data in this database.
8908 16 Indexed view ‘%.*ls’ (object ID %d) does not contain all rows that the view definition produces. Refer to Books Online for more information on this error. This does not necessarily represent an integrity issue with the data in this database.
8909 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID. 8910 16 Page %S_PGID in database ID %d is allocated to both object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), and object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
8911 10 The error has been repaired.
8912 10 %.*ls fixed %d allocation errors and %d consistency errors in database ‘%ls’.
8913 16 Extent %S_PGID is allocated to ‘%ls’ and at least one other object.
8914 10 Incorrect PFS free space information for page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Expected value %hs, actual value %hs.
8915 10 File %d (number of mixed extents = %I64d, mixed pages = %I64d).
8916 10 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), data extents %I64d, pages %I64d, mixed extent pages %I64d.
8917 10 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), index extents %I64d, pages %I64d, mixed extent pages %I64d.
8918 10 (number of mixed extents = %I64d, mixed pages = %I64d) in this database.
8919 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The record count in the header (%d) does not match the number of records (%d) found on page %S_PGID.
8920 16 Cannot perform a %ls operation inside a user transaction. Terminate the transaction and reissue the statement.
8921 16 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
8922 10 Could not repair this error.
8923 10 The repair level on the DBCC statement caused this repair to be bypassed.
8924 10 Repairing this error requires other errors to be corrected first.
8925 16 Table error: Cross object linkage: Page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), refers to page %S_PGID, slot %d, in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls).
8926 16 Table error: Cross object linkage: Parent page %S_PGID, slot %d in object %d, index %d, partition %I64d, AU %I64d (%.*ls), and page %S_PGID->next in object %d, index %d, partition %I64d, AU %I64d (%.*ls), refer to page %S_PGID but are not in the same object.
8927 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): The ghosted record count in the header (%d) does not match the number of ghosted records (%d) found on page %S_PGID. 8928 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Page %S_PGID could not be processed. See other errors for details.
8929 16 Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): Errors found in off-row data with ID %I64d owned by %ls record identified by %.*ls
8930 16 Database error: Database %d has inconsistent metadata. This error cannot be repaired and prevents further DBCC processing. Please restore from a backup.
8931 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from parent %S_PGID.
8932 16 Could not find filegroup ID %d in sys.filegroups for database ‘%ls’.
8933 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The low key value on page %S_PGID (level %d) is not %ls the key value in the parent %S_PGID slot %d.
8934 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The high key value on page %S_PGID (level %d) is not less than the low key value in the parent %S_PGID, slot %d of the next page %S_PGID.
8935 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.
8936 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID.
8937 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.
8938 16 Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
8939 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Values are %ld and %ld.
8940 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Address 0x%x is not aligned.
8941 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x is invalid.
8942 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, offset 0x%x overlaps with the prior row.
8943 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%hs) failed. Slot %d, row extends into free space at 0x%x.
8944 14 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. Test (%hs) failed. Values are %ld and %ld.
8945 16 Table error: Object ID %d, index ID %d will be rebuilt. 8946 16 Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page.
8947 16 Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.
8948 16 Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
8949 10 %.*ls fixed %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
8950 16 %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
8951 16 Table error: table ‘%ls’ (ID %d). Data row does not have a matching index row in the index ‘%ls’ (ID %d). Possible missing or invalid keys for the index row matching:
8952 16 Table error: table ‘%ls’ (ID %d). Index row in index ‘%ls’ (ID %d) does not match any data row. Possible extra or invalid keys for: 8953 10 Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
8954 10 %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
8955 16 Data row (%d:%d:%d) identified by (%ls) with index values ‘%ls’.
8956 16 Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
8957 10 %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. 8958 10 %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
8959 16 Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.
8960 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column.
8961 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.
8962 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d.
8963 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.
8964 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced.
8965 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.
8966 22 Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
8967 16 An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
8968 16 Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database.
8969 16 Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.
8970 16 Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column ‘%.*ls’ was created NOT NULL, but is NULL in the row.
8971 16 Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d
8972 16 Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d.
8973 16 CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice. Possible internal error or allocation fault.
8974 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d.
8975 10 Indexed view check failed for indexed view ‘%.*ls’ (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error. This does not necessarily represent an integrity issue with the data in this database. However, this view will not be processed further.
8976 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
8977 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.
8978 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
8979 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
8980 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
8981 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.
8982 16 Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index.
8983 10 File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
8984 16 Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
8985 16 Could not locate file ‘%.*ls’ for database ‘%.*ls’ in sys.database_files. The file either does not exist, or was dropped. 8986 16 Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using “WITH ALL_ERRORMSGS”. 8987 16 No help available for DBCC statement ‘%.*ls’.
8988 16 Row (%d:%d:%d) identified by (%ls).
8989 10 %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.
8990 10 %.*ls found %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
8991 16 0x%p to 0x%p is not a valid address range.
8992 16 Check Catalog Msg %d, State %d: %.*ls
8993 16 Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
8994 16 Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.
8995 16 System table ‘%.*ls’ (object ID %d, index ID %d) is in filegroup %d. All system tables must be in filegroup %d.
8996 16 IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) controls pages in filegroup %d, that should be in filegroup %d.
8997 16 Service Broker Msg %d, State %d: %.*ls
8998 16 Page errors on the GAM, SGAM, or PFS pages prevent
allocation integrity checks in database ID %d pages from %S_PGID to %S_PGID. See other errors for cause.
8999 10 Database tempdb allocation errors prevent further %ls processing.
9001 10 The log for database ‘%.*ls’ is not available. Check the event log for related error messages. Resolve any errors and restart the database.
9002 17 The transaction log for database ‘%.*ls’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
9003 20 The log scan number %S_LSN passed to log scan in database ‘%.*ls’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
9004 21 An error occurred while processing the log for database ‘%.*ls’. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
9005 16 Either start LSN or end LSN specified in OpenRowset(DBLog, …) is invalid.
9006 10 Cannot shrink log file %d (%s) because total number of logical log files cannot be fewer than %d.
9007 10 Cannot shrink log file %d (%s) because requested size (%dKB) is larger than the start of the last logical log file.
9008 10 Cannot shrink log file %d (%s) because all logical log files are in use.
9009 10 Cannot shrink log file %d (%s) because of minimum log space required.
9010 14 User does not have permission to query the virtual table, DBLog. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission
9100 23 Possible index corruption detected. Run DBCC CHECKDB. 9101 16 auto statistics internal
9104 16 auto statistics internal
9105 16 The provided statistics stream is corrupt.
9106 16 Histogram support not allowed for input data type 0x%08x. 9201 10 %d active query notification subscription(s) in database ‘%.*ls’ owned by security identification number ‘%.*ls’ were dropped. 9202 16 The query notification subscription message is invalid. 9204 16 The query notification subscription timeout is invalid. The allowed range is 1 through 2147483647.
9205 16 User “%.*ls” does not have permission to request query notification subscriptions on database “%.*ls”.
9206 16 The query notification subscription “%ld” cannot be deleted because it does not exist or it has already been fired.
9207 10 The query notification dialog on conversation handle ‘%.*ls’ closed due to the following error: ‘%.*ls’.
9208 16 Query notification subscription could not get dialog endpoint. Could not open service broker dialog for service name ‘%.*ls’ of broker instance ‘%.*ls’.
9209 16 Query notification subscription could not begin dialog with service name ‘%.*ls’ of broker instance ‘%.*ls’.
9210 10 Query notification delivery could not send message on dialog ‘%.*ls’. Delivery failed for notification ‘%.*ls’ because of the following error in service broker: ‘%.*ls’.
9211 10 Failed to check for pending query notifications in database “%d” because of the following error when opening the database: ‘%.*ls’. 9213 10 Query notification subscription could not access database with id %d. Could not open broker dialog for service name ‘%.*ls’ of broker instance ‘%.*ls’.
9214 16 The query notification delivery failed to decode the error message from the Service Broker.
9215 16 Query notification delivery failed to encode message. Delivery failed for notification ‘%.*ls’.
9216 10 Failed to delete the expired query notification subscription “%d”.
9217 10 Failed to drop the unused internal query notification table “%d” in database “%d”.
9218 16 Query notifications reached the internal limit of the maximum number of objects.
9219 16 The query notification subscriptions cleanup operation failed. See previous errors for details.
9220 10 Query notification dialog on conversation handle ‘%.*ls’ closed due to an unknown service broker error.
9221 10 Query notification delivery could not get dialog endpoint for dialog ‘%.*ls’. Delivery failed for notification ‘%.*ls’ because of the following error in service broker ‘%.*ls’.
9222 16 Internal query notification table has an outdated schema and the table has been dropped. Query notification cleanup has not been performed for this table.
9223 10 %d active query notification subscription(s) owned by security identification number ‘%.*ls’ were dropped.
9224 10 Query notification delivery could not access database with id %d. Delivery failed for notification ‘%.*ls’.
9225 16 The notification options identifier string has %d
characters. The maximum allowed length is %d characters.
9226 16 A string value within the notification options identifier is too long. String with prefix ‘%.*ls’ must be %d characters or less. 9227 16 Unmatched quote in notification options identifier string. 9228 16 Name expected in notification options identifier option. 9229 16 Unknown option name ‘%.*ls’ present in notification options identifier. The following are valid option names: ‘Service’, ‘Broker Instance’, ‘Local Database’. Option names cannot be quoted.
9230 16 Option ‘%ls’ was specified multiple times in the
notification options identifier.
9231 16 An equal (=) character was expected after the option name. Found ‘%.*ls’ instead.
9232 16 A semicolon (;) must be use to separate options in a notification options identifier. String ‘%.*ls’ was found following an option.
9233 16 The option ‘Service’ must be specified in the notification options identifier.
9234 16 The options ‘Broker Instance’ and ‘Local Database’ were both specified in the notification options identifier.
9235 16 Value missing for option ‘%ls’ in notification options identifier.
9236 16 Database %.*ls is not a valid local database.
9237 16 Database %.*ls is not a valid broker database.
9238 16 Query notification subscriptions are not allowed under an active application role context. Consider re-issuing the request without activating the application role.
9239 16 Internal query notifications error: The garbage collector corrected an inconsistency.
9240 10 Service broker dialog ‘%.*ls’ could not be closed due to a broker error in database with id ‘%d’ because of the following error in service broker: ‘%.*ls’.
9241 16 Serice broker dialog ‘%.*ls’ could not be closed because the database with id ‘%d’ is not available. Consider closing the dialogs manually once the database is available again.
9242 10 Query notification delivery could not get dialog endpoint for dialog ‘%.*ls’. Query notification delivery failed because of the following error in service broker: ‘%.*ls’. See the error log for additional information.
9243 10 Query notification delivery could not send message on dialog ‘%.*ls’. Query notification delivery failed because of the following error in service broker: ‘%.*ls’. See the error log for additional information. 9244 16 Query notification cleanup could not access metadata for database “%d”. Check whether the database is successfully restored and online.
9300 16 %sIn this version of the server, the ‘fn:id()’ function only accepts an argument of type ‘IDREF *’.
9301 16 %sIn this version of the server, ‘cast as %s’ is not available. Please use the ‘cast as ?’ syntax.
9302 16 %sThe context item in which the ‘fn:id()’ function is used must be a node.
9303 16 %sSyntax error near ‘%ls’, expected ‘%ls’.
9304 16 %sThis version of the server only supports XQuery version ‘1.0’.
9305 16 %sOnly type names followed by ‘?’ are supported in the target of ‘instance of’.
9306 16 %sThe target of ‘replace value of’ cannot be a union type, found ‘%ls’.
9308 16 %sThe argument of ‘%ls’ must be of a single numeric
primitive type or ‘http://www.w3.org/2004/07/xpath-datatypes#untypedAtomic‘. Found argument of type ‘%ls’.
9309 16 %sThe target of ‘replace value of’ cannot be
http://www.w3.org/2001/XMLSchema#anySimpleType‘, found ‘%ls’. 9310 16 %sThe ‘with’ clause of ‘replace value of’ cannot contain constructed XML.
9311 16 %sHeterogeneous sequences are not allowed in ‘%ls’, found ‘%ls’ and ‘%ls’.
9312 16 %s’%ls’ is not supported on simple typed or
http://www.w3.org/2001/XMLSchema#anyType‘ elements, found ‘%ls’. 9313 16 %sThis version of the server does not support multiple expressions or expressions mixed with strings in an attribute constructor. 9314 16 %sCannot implicitly atomize or apply ‘fn:data()’ to complex content elements, found type ‘%ls’ within inferred type ‘%ls’. 9315 16 %sOnly constant expressions are supported for the name expression of computed element and attribute constructors.
9316 16 %sCannot use ‘xmlns’ in the name expression of computed attribute constructor.
9317 16 %sSyntax error near ‘%ls’, expected string literal.
9318 16 %sSyntax error at source character ‘0x%02x’ near ‘%ls’, expected string literal.
9319 16 %sStatic simple type validation: Invalid simple type value ‘%ls’.
9320 16 %sThe result of applying the ‘parent’ axis on the document node is statically ’empty’.
9321 16 %sThe result of applying ‘parent::%ls’ is statically ’empty’.
9322 16 %sTwo consecutive ‘-‘ can only appear in a comment
constructor if they are used to close the comment (‘–>’).
9323 16 %sUsing ‘:’ in variable names is not supported in this version of the server.
9324 16 %sFound ‘}’ without matching ‘{‘. If you want to use the characters ‘{‘ or ‘}’, you need to escape them as ‘{{‘ or ‘}}’ respectively. 9325 16 %sComputed processing instruction constructors are not supported.
9326 16 %sComputed comment constructors are not supported.
9327 16 %sAll prolog entries need to end with ‘;’, found ‘%ls’. 9328 16 %sType specification expected, found ‘%ls’.
9329 16 %sThe sequence type ‘document-node()’ is only supported without a content type.
9330 16 %sOnly comparable types are allowed in ‘%ls’, found ‘%ls’. 9331 16 %sSyntax error near ‘%ls’, expected ‘%ls’ or ‘%ls’.
9332 16 %sSyntax error near ‘%ls’, expected ‘where’, ‘(stable) order by’ or ‘return’.
9333 16 %s’//’ followed by ‘self’, ‘parent’ or ‘descendant-or-self’ axes is not supported when it encounters simple typed or
http://www.w3.org/2001/XMLSchema#anyType‘ elements, found ‘%ls’. 9334 16 %sThe ‘form’ attribute cannot be specified on a local attribute or element definition that has the ‘ref’ attribute. 9335 16 %sThe XQuery syntax ‘%ls’ is not supported.
9336 16 %sThe XML Schema syntax ‘%ls’ is not supported.
9337 16 %sThe XML Schema type ‘NOTATION’ is not supported.
9338 16 %sThe value of a namespace declaration attribute must be a string literal. It cannot contain expressions.
9339 16 %sThe ‘form’ attribute cannot be specified on a global attribute or element definition.
9340 16 %sExplicit import of the current target namespace is invalid. References to items in the current target namespace that have already been loaded in the schema collection will be resolved implicitly. 9400 16 XML parsing: line %d, character %d, unexpected end of input 9401 16 XML parsing: line %d, character %d, unrecognized encoding 9402 16 XML parsing: line %d, character %d, unable to switch the encoding
9403 16 XML parsing: line %d, character %d, unrecognized input signature
9410 16 XML parsing: line %d, character %d, whitespace expected 9411 16 XML parsing: line %d, character %d, semicolon expected 9412 16 XML parsing: line %d, character %d, ‘>’ expected
9413 16 XML parsing: line %d, character %d, A string literal was expected
9414 16 XML parsing: line %d, character %d, equal expected
9415 16 XML parsing: line %d, character %d, well formed check: no ‘<‘ in attribute value
9416 16 XML parsing: line %d, character %d, hexadecimal digit expected
9417 16 XML parsing: line %d, character %d, decimal digit expected 9418 16 XML parsing: line %d, character %d, ‘[‘ expected
9419 16 XML parsing: line %d, character %d, ‘(‘ expected
9420 16 XML parsing: line %d, character %d, illegal xml character 9421 16 XML parsing: line %d, character %d, illegal name character 9422 16 XML parsing: line %d, character %d, incorrect document syntax
9423 16 XML parsing: line %d, character %d, incorrect CDATA section syntax
9424 16 XML parsing: line %d, character %d, incorrect comment syntax 9425 16 XML parsing: line %d, character %d, incorrect conditional section syntax
9426 16 XML parsing: line %d, character %d, incorrect ATTLIST declaration syntax
9427 16 XML parsing: line %d, character %d, incorrect DOCTYPE declaration syntax
9428 16 XML parsing: line %d, character %d, incorrect ELEMENT declaration syntax
9429 16 XML parsing: line %d, character %d, incorrect ENTITY declaration syntax
9430 16 XML parsing: line %d, character %d, incorrect NOTATION declaration syntax
9431 16 XML parsing: line %d, character %d, NDATA expected
9432 16 XML parsing: line %d, character %d, PUBLIC expected
9433 16 XML parsing: line %d, character %d, SYSTEM expected
9434 16 XML parsing: line %d, character %d, name expected
9435 16 XML parsing: line %d, character %d, one root element 9436 16 XML parsing: line %d, character %d, end tag does not match start tag
9437 16 XML parsing: line %d, character %d, duplicate attribute 9438 16 XML parsing: line %d, character %d, text/xmldecl not at the beginning of input
9439 16 XML parsing: line %d, character %d, namespaces beginning with “xml” are reserved
9440 16 XML parsing: line %d, character %d, incorrect text
declaration syntax
9441 16 XML parsing: line %d, character %d, incorrect xml
declaration syntax
9442 16 XML parsing: line %d, character %d, incorrect encoding name syntax
9443 16 XML parsing: line %d, character %d, incorrect public identifier syntax
9444 16 XML parsing: line %d, character %d, well formed check: pes in internal subset
9445 16 XML parsing: line %d, character %d, well formed check: pes between declarations
9446 16 XML parsing: line %d, character %d, well formed check: no recursion
9447 16 XML parsing: line %d, character %d, entity content not well formed
9448 16 XML parsing: line %d, character %d, well formed check: undeclared entity
9449 16 XML parsing: line %d, character %d, well formed check: parsed entity
9450 16 XML parsing: line %d, character %d, well formed check: no external entity references
9451 16 XML parsing: line %d, character %d, incorrect processing instruction syntax
9452 16 XML parsing: line %d, character %d, incorrect system identifier syntax
9453 16 XML parsing: line %d, character %d, ‘?’ expected
9454 16 XML parsing: line %d, character %d, no ‘]]>’ in element content
9455 16 XML parsing: line %d, character %d, illegal qualified name character
9456 16 XML parsing: line %d, character %d, multiple colons in qualified name
9457 16 XML parsing: line %d, character %d, colon in name
9458 16 XML parsing: line %d, character %d, redeclared prefix 9459 16 XML parsing: line %d, character %d, undeclared prefix 9460 16 XML parsing: line %d, character %d, non default namespace with empty uri
9461 16 XML %ls starting with ‘%.*ls’ is %d characters long, which exceeds the limit. Maximum allowed length is %d characters.
9462 16 XML parsing: line %d, character %d, not all chunks of value have been read
9463 16 XML parsing: line %d, character %d, xml:space has a
non-legal value
9480 16 XML parsing: line %d, character %d, unsupported xml
9500 16 The data type ‘%.*ls’ used in the VALUE method is invalid. 9501 16 XQuery: Unable to resolve sql:variable(‘%.*ls’). The variable must be declared as a scalar TSQL variable.
9502 16 The string literal provided for the argument %d of the ‘%.*ls’ method must not exceed %d bytes.
9503 16 Errors and/or warnings occurred when processing the XQuery statement for xml data type method ‘%.*ls’. See previous error messages for more details.
9504 16 Errors and/or warnings occurred when processing the XQuery statement for xml data type method ‘%.*ls’, invoked on column ‘%.*ls’, table ‘%.*ls’. See previous error messages for more details.
9506 16 The XMLDT method ‘%.*ls’ can only be invoked on columns of type xml.
9507 16 The XML data type method on a remote column used in this query can not be executed either locally or remotely. Please rewrite your query.
9508 16 The reference parameter given to XMLDT method ‘%.*ls’ was generated from a different XML instance than the one it is being applied to. 9509 16 XMLUNNEST method requires typed xml column with single global element
9510 16 Functionality not yet implemented: XMLNODEREFS cannot use references exposed by views.
9512 16 Xml data type is not supported as a parameter to remote calls.
9513 16 Error processing xml data type method ‘%.*ls’. The following SET options required by xml data type methods are not set: ‘%.*ls’. 9514 16 Xml data type is not supported in distributed queries. Remote object ‘%.*ls’ has xml column(s).
9515 16 An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch.
9516 16 XQuery: The name or one of the parts of a multi-part name supplied to %S_MSG(‘%.*ls’) is empty. Empty names cannot be used to identify objects, columns or variables in SQL.
9517 16 XQuery: The name or one of the parts of a multi-part name that starts with ‘%.*ls’ supplied to %S_MSG() is not a valid SQL identifier – it is too long. Maximum length is %d, actual length is %d. 9518 16 XQuery: The name or one of the parts of a multi-part name that starts with ‘%.*ls’ supplied to %S_MSG() is not a valid SQL identifier – it contains invalid characters.
9519 16 XQuery: The name supplied to sql:variable(‘%.*ls’) is not a valid SQL variable name. Variable names must start with the ‘@’ symbol followed by at least one character.
9520 16 XQuery: ‘%.*ls’ referenced by sql:variable() is not a valid system function name.
9601 16 Cannot relate to %S_MSG %.*ls because it is %S_MSG.
9609 16 The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d.
9610 16 The service ‘%.*ls’ in the FROM SERVICE clause must match the service ‘%.*ls’ referenced by %s = ‘%.*ls’.
9611 16 Cannot find the specified user ‘%.*ls’.
9613 16 The queue ‘%.*ls’ cannot be activated because the activation user is not specified.
9614 16 The queue ‘%.*ls’ cannot be activated because the activation stored procedure is either not specified or is invalid.
9615 16 A message of type ‘%.*ls’ failed XML validation on the target service. %.*ls This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
9616 16 A message of type ‘%.*ls’ was received and failed XML validation. %.*ls This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
9617 16 The service queue “%.*ls” is currently disabled.
9618 16 The message cannot be sent because the service queue ‘%.*ls’ associated with the dialog is currently disabled and retention is on. 9619 16 Failed to create remote service binding ‘%.*ls’. A remote service binding for service ‘%.*ls’ already exists.
9620 16 The activation stored procedure ‘%.*ls’ is invalid.
Functions are not allowed.
9621 16 An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i. 9622 16 The crypto provider context is not initialized.
9623 16 The key passed in for this operation is in the wrong state. 9624 16 The key size is unacceptable for this key object.
9625 16 The key buffer size is inconsistent with the key modulus size.
9626 16 An internal Service Broker error occurred: an object is in the wrong state for this operation. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware problems.
9627 16 The hash buffer size is not correct for initializing the hash object.
9628 16 The encryption/decryption data buffer size is not 8 byte aligned.
9629 16 The decrypted signature size is wrong.
9630 16 The signature did not verify the internal hash.
9631 16 The salt size is unacceptable for this key object.
9632 16 The salt buffer size is too small.
9633 16 The passed in name is too long.
9634 16 Service Broker was unable to allocate memory for
cryptographic operations. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.
9635 16 The certificate is not valid at this point in time.
9636 16 The requested object was not found.
9637 16 The passed in serialized object is incorrectly encoded. 9638 16 The cer or pvk file size is too large.
9639 16 A password was supplied and the pvk file is not encrypted. 9640 16 The operation encountered an OS error.
9641 16 A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for further information.
9642 16 An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far endpoint address: ‘%.*hs’)
9643 16 An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i.
9644 16 An error occurred in the service broker message dispatcher. Error: %i, State: %i.
9645 16 An error occurred in the service broker manager, Error: %i, State: %i.
9646 16 An error occurred in the timer event cache. Error %i, state %i.
9647 16 Received a malformed message from the network. Unable to retrieve a broker message attribute from a message destined for database ID %d. This may indicate a network problem or that another application connected to the Service Broker endpoint.
9649 16 A security (SSPI) error occurred when connecting to another service broker: ‘%.*ls’. Check the Windows Event Log for more information. 9650 16 A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error ‘%ls’.
9651 16 The system call failed during a Service Broker or Database Mirroring operation. System error: ‘%ls’.
9652 16 Service Broker failed to retrieve the session key for encrypting a message.
9653 16 The activation stored procedure ‘%.*ls’ is invalid.
Activation stored procedures cannot require parameters.
9654 16 Attempting to use database and it doesn’t exist.
9655 23 The transmission queue table structure in database is inconsistent. Possible database corruption.
9656 16 The pvk file is encrypted and no password was supplied. 9657 23 The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware problems. Check the SQL Server error log and the Windows event logs for information on possible hardware problems. Restart SQL Server to rebuild tempdb.
9658 16 Cannot access the transmission queue table in database. 9659 16 The %s of route ‘%.*ls’ cannot be empty.
9660 16 The %s of route ‘%.*ls’ must be less than %d characters long.
9661 16 The SERVICE_NAME and BROKER_INSTANCE of route “%.*ls” must be specified when using mirroring.
9662 16 Cannot specify BROKER_INSTANCE without SERVICE_NAME in route “%.*ls”.
9663 16 The system object cannot be modified.
9666 10 The %S_MSG protocol transport is disabled or not configured. 9667 10 Services analyzed: %d.
9668 10 Service Queues analyzed: %d.
9669 10 Conversation Endpoints analyzed: %d.
9670 10 Remote Service Bindings analyzed: %d.
9671 16 Messages with conversation ID ‘%ls’ have been removed from the transmission queue.
9672 16 Messages with conversation handle ‘%ls’ and conversation group ‘%ls’ have been removed from the queue with ID %d.
9673 16 Activation has been disabled on the queue with ID %d. 9674 10 Conversation Groups analyzed: %d.
9675 10 Message Types analyzed: %d.
9676 10 Service Contracts analyzed: %d.
9677 16 The service contract with ID %d is referencing the missing message type with ID %d.
9678 16 The service with ID %d is referencing the missing service contract with ID %d.
9679 16 The service with ID %d is referencing the missing service queue with ID %d.
9680 16 The conversation endpoint ‘%ls’ is referencing the missing conversation group ‘%ls’.
9681 16 The conversation endpoint with ID ‘%ls’ and is_initiator: %d is referencing the missing service contract with ID %d.
9682 16 The conversation endpoint with ID ‘%ls’ and is_initiator: %d is referencing the missing service with ID %d.
9683 16 The conversation group ‘%ls’ is referencing the missing service with ID %d.
9684 16 The service with ID %d has been dropped.
9685 16 The service contract with ID %d has been dropped.
9686 16 The conversation endpoint with handle ‘%ls’ has been dropped.
9687 16 The conversation group ‘%ls’ has been dropped.
9688 10 Service Broker manager has started.
9689 10 Service Broker manager has shut down.
9690 10 The %S_MSG protocol transport is now listening for
connections.
9691 10 The %S_MSG protocol transport has stopped listening for connections.
9692 16 The %S_MSG protocol transport cannot listen on port %d because it is in use by another process.
9693 16 The %S_MSG protocol transport could not listen for
connections due to the following error: ‘%.*ls’.
9694 16 Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages. 9695 16 Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.
9696 16 Cannot start the Service Broker primary event handler. This error is a symptom of another problem. Check the SQL Server error log for additional messages, and address this underlying problem.
9697 10 Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
9698 16 Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address the underlying problem.
9701 16 Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem.
9704 16 This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target service.
9705 16 The messages in the queue with ID %d are referencing the invalid conversation handle ‘%ls’.
9706 16 The stored procedure with ID %d is invalid but is referenced by the queue with ID %d.
9707 16 The activation user with ID %d is invalid but is referenced by queue with ID %d.
9708 16 The messages in the queue with ID %d are referencing the invalid conversation group ‘%ls’.
9709 16 The messages in the queue with ID %d are referencing the invalid message type with ID %d.
9710 16 The conversation endpoint with ID ‘%ls’ and is_initiator: %d is referencing the invalid conversation group ‘%ls’.
9711 16 The transmission queue is referencing the invalid
conversation ID ‘%ls’.
9712 16 The remote service binding with ID %d is referencing the invalid service contract with ID %d.
9713 16 The message type with ID %d is referencing the invalid XML schema collection ID %d.
9715 16 The conversation endpoint with conversation handle ‘%ls’ is in an inconsistent state. Check the SQL Server error logs and the Windows event logs for information on possible hardware problems. To recover the database, restore the database from a clean backup. If no clean backup is available, consider running DBCC CHECKDB. Note that DBCC CHECKDB may remove data.
9716 16 The conversation group ‘%ls’ reports references to %d conversation handle(s), but actually references %d.
9717 16 Cannot enable stored procedure activation on queue ‘%.*ls’. Event notification for queue_activation is already configured on this queue. 9718 16 Cannot create event notification for queue_activation on queue “%.*ls”. Stored procedure activation is already configured on this queue.
9719 16 The database for this conversation endpoint is attached or restored.
9720 16 The database for the remote conversation endpoint is attached or restored.
9721 10 Service broker failed to clean up conversation endpoints on database ‘%.*ls’. Another problem is preventing SQL Server from completing this operation. Check the SQL Server error log for additional messages. 9722 16 The Service Broker is not ready on database “%.*ls”. 9723 10 The database “%i” will not be started as the broker due to duplication in the broker instance ID.
9724 10 The activated proc %ls running on queue %ls output the following: ‘%.*ls’
9725 16 The invalid schema has been dropped from the message type with ID %d.
9726 16 The remote service binding with ID %d has been dropped. 9727 16 Dialog security is not available for this conversation because there is no remote service binding for the target service. Create a remote service binding, or specify ENCRYPTION = OFF in the BEGIN DIALOG statement.
9728 16 Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped after the conversation was created.
9730 16 Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security principal may have been dropped after the conversation was created. 9731 16 Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: %i). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation.
9733 16 There is no private key for the security certificate bound to database principal (Id: %i). The certificate may have been created or installed incorrectly. Reinstall the certificate, or create a new certificate.
9734 16 The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.
9735 16 The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.
9736 16 An error occurred in dialog transmission: Error: %i, State: %i. %.*ls
9737 16 The private key for the security certificate bound to the database principal (ID %i) is password protected. Password protected private keys are not supported for use with secure dialogs.
9738 16 Cannot create task for Service Broker message dispatcher. This message is a symptom of another problem that is preventing SQL Server from creating tasks. Please check the SQL Server error log and the Windows event log for additional messages.
9739 16 Message transmitter in service broker message dispatcher failed %d times
9740 16 Cannot start the Service Broker message dispatcher. This error is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address this underlying problem.
9741 10 The %S_MSG ‘%.*ls’ was dropped on upgrade because it referenced a system contract that was dropped.
9742 16 The activation stored procedure ‘%.*ls’ is invalid.
Temporary procedures may not be configured for activation.
9743 16 The %s of route “%.*ls” must be an address when using mirroring.
9744 16 The %s of route “%.*ls” is not a valid address.
9745 16 The ADDRESS of route ‘%.*ls’ cannot be ‘TRANSPORT’ when SERVICE_NAME is specified.
9746 16 The LIFETIME of route ‘%.*ls’ must be in the range %d to %d. 9747 16 The ADDRESS and MIRROR_ADDRESS of route ‘%.*ls’ cannot be the same.
9748 10 The %S_MSG protocol transport is not available.
9749 10 Target queue is busy; message(s) queued for delivery. 9750 10 No route matches the destination service name for this conversation. Create a route to the destination service name for messages in this conversation to be delivered.
9751 10 Authentication failed with error: ‘%.*ls’.
9752 10 %S_MSG connection was refused. The user account of the remote server is not permitted to log in to this SQL Server: User account: ‘%.*ls’, IP address: ‘%.*hs’.
9753 10 The target service broker is unreachable.
9754 10 Connection attempt failed with error: ‘%.*ls’.
9755 10 An error occurred while receiving data: ‘%.*ls’.
9756 10 An internal exception occurred while connecting to an adjacent broker: Error: %i, State: %i. %.*ls
9757 10 Service Broker/Database Mirroring network protocol error occurred.
9758 10 Login protocol negotiation error occurred.
9759 10 An error occurred while sending data: ‘%.*ls’.
9761 16 The Broker Configuration conversation on dialog handle ‘%s’ closed due to an error. To troubleshoot this problem, investigate the error: ‘%.*ls’.
9762 10 An error occurred while looking up the public key
certificate associated with this SQL Server instance: No certificate was found.
9763 10 An error occurred while looking up the public key
certificate associated with this SQL Server instance: The certificate found is not valid at the current time.
9764 10 An error occurred while looking up the public key
certificate associated with this SQL Server instance: The certificate found is too large.
9765 10 An error occurred while looking up the public key
certificate associated with this SQL Server instance: The certificate found has no associated private key.
9766 10 An unknown internal error (%d) occurred while looking up the public key certificate associated with this SQL Server instance. 9767 16 The security certificate bound to database principal (Id: %i) has been disabled for use with BEGIN DIALOG. See the Books Online topics “Certificates and Service Broker” for an overview and “ALTER CERTIFICATE (Transact-SQL)” for syntax to make a certificate ACTIVE FOR BEGIN_DIALOG. 9768 16 A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER while conversations are being created.
9769 10 Insufficient memory prevented the Service Broker/Database Mirroring Transport Manager from starting.
9770 10 Locating routes and security information via the Broker Configuration Service.
9771 10 The service broker manager is disabled in single-user mode. 9772 16 The Service Broker in database “%.*ls” cannot be enabled because there is already an enabled Service Broker with the same ID. 9773 10 The Service Broker in database “%d” is disabled because there is already an enabled Service Broker with the same ID. 9774 10 Cannot create a new Service Broker in the attached read-only database “%.*ls”. The Service Broker will be disabled.
9775 16 Cannot create a new Service Broker in read-only database “%.*ls”.
9776 16 Cannot enable the Service Broker in database “%.*ls” because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s).
9777 10 The Service Broker in database “%.*ls” will be disabled because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s).
9778 16 Cannot create a new Service Broker in a mirrored database “%.*ls”.
9779 10 Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.
9780 10 The service broker manager is initializing.
9781 10 The service broker manager is shutting down.
9782 10 An internal exception occurred while dispatching a message: Error: %i, State: %i. %.*ls
9783 10 DNS lookup failed with error: ‘%.*ls’.
9784 10 Service Broker received an error message on this
conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.
9785 10 Invalid address specified: ‘%.*ls’.
9786 10 Cannot retrieve user name from security context. Error: ‘%.*ls’. State: %hu.
9787 10 An error occurred while processing broker mirroring routes. Error: %i. State: %i.
9788 10 Unable to route the incoming message. The system database MSDB containing routing information is not available.
9789 10 Unable to route the incoming message. The system database MSDB containing routing information is not available. The broker is disabled in MSDB.
9790 10 Unable to route the incoming message. The system database MSDB containing routing information is in SINGLE USER mode.
9791 10 The broker is disabled in the sender’s database.
9792 10 Could not forward the message because forwarding is disabled in this SQL Server instance.
9793 10 The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied.
9794 10 The broker mirroring manager has not fully initialized. 9795 10 Could not find the target broker in the local SQL Server instance.
9796 10 The target service name matched a LOCAL route, but there is no service by that name in the local SQL Server instance.
9797 10 Classification has been delayed because the routing
information is currently being updated.
9798 16 The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
9801 16 Error converting %.*ls to %ls. The result would be
truncated.
9802 16 The locale identifier (LCID) %d is not supported by SQL Server.
9803 16 Invalid data for type “%ls”.
9901 16 Full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) is low on disk space. Pausing all populations in progress until more space becomes available. Reason code: %d. Error: %ls. To resume populations, free up disk space.
9902 10 Full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) is low on system resources. Any population in progress will be paused until more resources become available. Reason code: %d. Error: %ls. If this message occurs frequently, try to serialize full-text indexing for multiple catalogs.
9903 10 The full-text catalog health monitor reported a failure for full-text catalog “%ls” (%d) in database “%ls” (%d). Reason code: %d. Error: %ls. The system will restart any in-progress population from the previous checkpoint. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required.
9904 10 The full-text catalog “%ls” (%d) in database “%ls” (%d) will be remounted to recover from a failure. Reason code: %d. Error: %ls. If this message occurs frequently, consult SQL Server Books Online for troubleshooting assistance. This is an informational message only. No user action is required.
9905 10 Informational: Full-text indexer requested status change for catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’). New Status: %ls, Reason: %ls (%ls).
9906 10 The full-text catalog monitor reported catalog “%ls” (%d) in database “%ls” (%d) in %ls state. This is an informational message only. No user action is required.
9907 10 Error: Total number of items in full-text catalog ID ‘%d’ in database ID ‘%d’ exceeds the supported limit. See Books Online for troubleshooting assistance.
9908 10 Changing the status to %ls for full-text catalog “%ls” (%d) in database “%ls” (%d). This is an informational message only. No user action is required.
9909 10 Warning: Failed to change the status to %ls for full-text catalog “%ls” (%d) in database “%ls” (%d). Error: %ls.
9910 10 Warning: Error occurred during full-text %ls population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %ls.
9911 10 Informational: Full-text %ls population initialized for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Population sub-tasks: %d.
9912 10 Error: Failed to initialize full-text %ls population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %d.
9913 10 Informational: Resuming full-text population for table or indexed view ‘%ls’ in database %ls (table or indexed view ID ‘%d’, database ID ‘%d’). Prior number of documents processed: %d, error encountered: %d. 9914 16 Error: Failed to resume full-text %ls population for table or indexed view ‘%ls’ in database %ls (table or indexed view ID ‘%d’, database ID ‘%d’). Error: 0x%x. Repeat the operation that triggered the resume, or drop and re-create the index.
9915 10 Reinitialized full-text %ls population for table ‘%ls’ (table ID ‘%d’, database ID ‘%d’) after a temporary failure. Number of documents processed prior to failure: %d, errors encountered: %d. This is an informational message only. No user action is required.
9916 10 Error: Failed to reinitialize full-text %ls population after a temporary failure for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %d.
9917 17 An internal error occurred in full-text docid mapper. 9918 10 Warning: Full-text catalog ‘%ls’ uses FAT volume. Security and differential backup are not supported for the catalog.
9919 16 Fulltext DDL command failed because SQL Server was started in single user mode.
9920 10 Warning: Failed to get MSFTESQL indexer interface for full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’). Error: %ls. 9921 16 During upgrade fatal error 0x%x encountered in CoCreateGuid. Failed to resolve full-text catalog file name for ‘%ls’.
9922 10 Warning: Full-text population for table or indexed view ‘%ls’ failed to send batch of data to MSFTESQL service (table or indexed view ID ‘%d’, catalog ID ‘%d’, database ID ‘%d’). Error: %ls. 9923 10 Warning: Full-text population for table or indexed view ‘%ls’ reported low resources while sending a batch of data to MSFTESQL service (table or indexed view ID ‘%d’, catalog ID ‘%d’, database ID ‘%d’). Error: %ls.
9924 16 Rebuild full-text catalog ‘%ls’ failed: Catalog header file is read-only.
9925 16 Rebuild full-text catalog ‘%ls’ failed: Full-text catalog is read-only.
9926 10 Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should.
9927 10 Informational: The full-text search condition contained noise word(s).
9928 16 Computed column ‘%.*ls’ cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column. 9929 16 Computed column ‘%.*ls’ cannot be used as full-text type column for image or varbinary(MAX) column. This computed column must be deterministic, precise or persisted, with a size less or equal than %d characters.
9930 10 Null document type provided. Row will not be full-text indexed.
9931 10 Document type exceeds the maximum permitted length. Row will not be full-text indexed.
9932 10 Document type value is malformed. Row will not be full-text indexed.
9933 10 Internal error: The row cannot be full-text indexed. The protocol handler was invoked out of sequence. This is an informational message only. No user action is required.
9934 10 Row was not found. It was deleted or updated while indexing was in progress.
9935 10 Warning: Wordbreaker, filter, or protocol handler used by catalog ‘%ls’ does not exist on this instance. Use
sp_help_fulltext_catalog_components and sp_help_fulltext_system_components check for mismatching components. Rebuild catalog is recommended. 9936 10 Informational: No full-text supported languages found. 9937 16 Too many full-text columns or the full-text query is too complex to be executed.
9938 16 Cannot find the specified user or role ‘%.*ls’.
9939 16 Current user or role ‘%.*ls’ does not have the required permission to set the owner.
9940 10 Error: Full-text %ls population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) is terminated due to the preceding error.
9941 10 Informational: Full-text %ls population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) is being suspended by the system as the database is unavailable. System will resume the population whenever the database is available
9942 10 Informational: Full-text %ls population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) was cancelled by user.
9943 10 Informational: Full-text %ls population completed for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Number of documents processed: %d. Number of documents failed: %d. Number of documents need retry: %d.
9944 10 Informational: Full-text retry pass of %ls population completed for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Number of retry documents processed: %d. Number of documents failed: %d.
9945 10 Error: All Full-text populations in progress, for catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) were terminated due to error. Error: 0x%x.
9946 10 Warning: Failed to mount full-text catalog ‘%ls’ in
directory ‘%ls’. The full-text catalog cannot be attached.
9947 10 Warning: Identity or last population complete time of full-text catalog in directory ‘%ls’ does not match database ‘%.*ls’. The full-text catalog cannot be attached.
9948 10 Warning: Full-text catalog path ‘%ls’ is invalid. It exceeds the length limit, or it is a relative path, or it is a hidden directory. The full-text catalog cannot be attached.
9949 10 Warning: All Full-text populations in progress for full-text catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’) are paused. Reason code: %d. Error: %ls. If this message occurs frequently, consult Books Online for indexing performance tuning assistance.

9950 10 Informational: Full-text catalog health monitor reported a failure for catalog ‘%ls’ (‘%d’) in database ‘%ls’ (‘%d’). Reason code: %d. Error: %ls. The catalog is corrupted and all in-progress populations will be stopped. Use rebuild catalog to recover the failure and start population from scratch.
9951 10 Warning: Database %.*ls cannot be modified during detach. Drop full-text catalog request will be ignored. Full-text catalog will be dismounted instead.
9952 10 Informational: Full-text auto change tracking is turned off for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) due to fatal crawl error.
9953 16 The path ‘%.*ls’ has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive. 9954 16 The Full-Text Service (msftesql%ls%ls) is disabled. The system administrator must enable this service.
9955 16 SQL server failed to communicate with Full-Text Service (msftesql%ls%ls). The system administrator must make sure that same service account is used for both services and the service account has the permission to auto start the full-text service.
9956 16 The Full-Text Service (msftesql%ls%ls) failed to logon. The system administrator must use a valid service account and password for the service.
9957 16 Full-text operation failed due to full-text catalog %ls is corrupted. Use rebuild rebuild catalog to correct the problem. 9958 16 Full-text catalog with ID %d doesn’t exist.
9959 16 Cannot perform requested task because full-text memory manager is not initialized.
9960 16 View ‘%.*ls’ is not an indexed view. Full-text index is not allowed to be created on it.
9961 16 Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified.
9962 16 Failed to move full-text catalog from ‘%ls’ to ‘%ls’. OS error ‘%ls’.
9963 10 Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID ‘%d’, database ID ‘%d’ is reset. 9964 16 Failed to finish full-text operation. Filegroup ‘%.*ls’ is empty, read-only, or not online.
9965 16 NULL or Invalid type of value specified for ‘%ls’ parameter. 9966 16 Cannot use full-text search in master, tempdb, or model database.
9967 10 A default full-text catalog does not exist in database ‘%.*ls’ or user does not have permission to perform this action. 9968 10 Warning: No appropriate filter was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value 0x%ls. Some columns of the row were not indexed.
9969 10 Warning: No appropriate wordbreaker was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value 0x%ls. Neutral wordbreaker was used for some columns of the row.

9970 16 Couldn’t complete full-text operation because full-text key for table or indexed view ‘%.*ls’ is offline.
9971 10 Warning: No appropriate filter for embedded object was found during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value 0x%ls. Some embedded objects in the row could not be indexed.
9972 16 Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE.
9973 10 Informational: Full-text %ls population paused for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Number of documents processed: %d. Number of documents failed: %d. Number of documents need retry: %d.
9974 10 Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue when your start the same type of crawl again.
9975 10 Warning: Only paused full population can be resumed. The command is ignored.
9976 16 The Microsoft SQL Server Service (mssqlserver%ls%ls) is shutting down. The system administrator must start this service. 9977 10 Warning: Last population complete time of full-text catalog in directory ‘%ls’ does not match database ‘%.*ls’. The full-text catalog is attached and it may need to be repopulated.
9978 10 Warning: During upgrade full-text index on table ‘%ls’ is disabled because at least one of full-text key column, full-text columns, or type columns is a non-deterministic or imprecise nonpersisted computed column.
9979 10 Warning: During upgrade full-text catalog ‘%ls’ in database ‘%ls’ is set as offline because it failed to be created at path ‘%ls’. Please fix the full-text catalog path and rebuild the full-text catalog after upgrade.
9980 16 Variable parameters can not be passed to fulltext
predicates: contains, freetext and functions: containstable, freetexttable applied to remote table.
9981 16 Remote scan is not supported on fulltext queries.
9982 16 Cannot use full-text search in user instance.
9983 10 Warning: Full-text catalog ‘%ls’ in database ‘%ls’ is set as offline because a valid full-text catalog cannot be found at path ‘%ls’. Please fix the full-text catalog path and rebuild the full-text catalog to bring it online.
9984 10 Warning: Full-text catalog ‘%ls’ in database ‘%ls’ is set as offline because database is set to full-text disabled. Please enable full-text in the database to bring full-text catalog online. 9985 10 Warning: Full-text catalog ‘%ls’ in database ‘%ls’ is set as offline because operation failed with error ‘%ls’. Fix the problem and rebuild the catalog to bring it online.
9986 10 Warning: Full-text catalog ‘%ls’ in database ‘%ls’ is set as offline during attach database. Please fix full-text catalog path and rebuild to bring full-text catalog online, or reattach the database with correct catalog path.
9987 16 The backup of full-text catalog ‘%ls’ is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online. Or BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data.
10000 16 Unknown provider error.
10001 16 The provider reported an unexpected catastrophic failure. 10002 16 The provider did not implement the functionality.
10003 16 The provider ran out of memory.
10004 16 One or more arguments were reported invalid by the provider. 10005 16 The provider did not support an interface.
10006 16 The provider indicated an invalid pointer was used. 10007 16 The provider indicated an invalid handle was used.
10008 16 The provider terminated the operation.
10009 16 The provider did not give any information about the error. 10010 16 The data necessary to complete this operation was not yet available to the provider.
10011 16 Access denied.
10021 16 Execution terminated by the provider because a resource limit was reached.
10022 16 The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
10023 16 The provider does not support the necessary method. 10024 16 The provider indicates that the user did not have the permission to perform the operation.
10025 16 Provider caused a server fault in an external process. 10026 16 No command text was set.
10027 16 Command was not prepared.
10028 16 Authentication failed.
10032 16 Cannot return multiple result sets (not supported by the provider).
10033 16 The specified index does not exist or the provider does not support an index scan on this data source.
10034 16 The specified table or view does not exist or contains errors.
10035 16 No value was given for one or more of the required
parameters.
10042 16 Cannot set any properties while there is an open rowset. 10052 16 The insertion was canceled by the provider during
notification.
10053 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
10054 16 The data value for one or more columns overflowed the type used by the provider.
10055 16 The data violated the integrity constraints for one or more columns.
10056 16 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10057 16 Cannot create the row. Would exceed the total number of active rows supported by the rowset.
10058 16 The consumer cannot insert a new row before releasing previously-retrieved row handles.
10062 16 The change was canceled by the provider during notification. 10063 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
10064 16 The data value for one or more columns overflowed the type used by the provider.
10065 16 The data violated the integrity constraints for one or more columns.
10066 16 The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
10067 16 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
10068 16 The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
10069 16 The consumer could not delete the row. The insertion has been transmitted to the data source.
10081 16 The rowset uses integrated indexes and there is no current index.
10085 16 RestartPosition on the table was canceled during
notification.
10086 16 The table was built over a live data stream and the position cannot be restarted.
10087 16 The provider did not release some of the existing rows. 10088 16 The order of the columns was not specified in the object that created the rowset. The provider had to reexecute the command to reposition the next fetch position to its initial position, and the order of the columns changed.
10100 16 Cannot create %S_MSG on view “%.*ls” because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alternatively, consider replacing DISTINCT with GROUP BY or COUNT_BIG(*) to simulate DISTINCT on grouping columns.
10101 16 Cannot create %S_MSG on view “%.*ls” because it contains the TOP keyword. Consider removing TOP or not indexing the view. 10102 16 Cannot create %S_MSG on view “%.*ls” because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view. 10103 16 Cannot create %S_MSG on view “%.*ls” because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUERY, OPENROWSET, and OPENDATASOURCE.
10104 16 Cannot create %S_MSG on view “%.*ls” because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of these functions or not indexing the view.
10105 16 Cannot create %S_MSG on view “%.*ls” because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view. 10106 16 Cannot create %S_MSG on view “%.*ls” because it references an internal system rowset provider. Consider not indexing this view. 10107 16 Cannot create %S_MSG on view “%.*ls” because it uses table variable “%.*ls”. Consider not indexing this view or removing the reference to the table variable.
10108 16 Cannot create %S_MSG on view “%.*ls” because it references a SQL Server internal table.
10109 16 Cannot create %S_MSG on view “%.*ls” because it references derived table “%.*ls” (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view. 10110 16 Cannot create %S_MSG on view “%.*ls” because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY. 10111 16 Cannot create %S_MSG on view “%.*ls” because it contains a join using an ODBC standard escape syntax. Consider using an ANSI join syntax instead.
10112 16 Cannot create %S_MSG on view ‘%.*ls’ because it contains an INNER join that specifies a join hint. Consider removing the join hint. 10113 16 Cannot create %S_MSG on view “%.*ls” because it uses a LEFT, RIGHT, or FULL OUTER join, and no OUTER joins are allowed in indexed views. Consider using an INNER join instead.
10114 16 Cannot create %S_MSG on view “%.*ls” because it uses the PIVOT operator. Consider not indexing this view.
10115 16 Cannot create %S_MSG on view “%.*ls” because it uses the UNPIVOT operator. Consider not indexing this view.
10116 16 Cannot create %S_MSG on view ‘%.*ls’ because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view for each query that is an input to the UNION, INTERSECT, or EXCEPT operators of the original view.
10117 16 Cannot create %S_MSG on view “%.*ls” because the select list of the view uses the “*” operator to select columns. Consider referencing columns by name instead.
10118 16 Cannot create %S_MSG on view “%.*ls” because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
10119 16 Cannot create %S_MSG on view “%.*ls” because it contains the CUBE operator. Consider not indexing this view.
10120 16 Cannot create %S_MSG on view “%.*ls” because it contains the ROLLUP operator. Consider not indexing this view.
10121 16 Cannot create %S_MSG on view “%.*ls” because it contains a HAVING clause. Consider removing the HAVING clause.
10122 16 Cannot create %S_MSG on view “%.*ls” because it contains a COMPUTE clause. Consider not indexing this view, or using a GROUP BY or aggregate view instead to replace the COMPUTE calculation of aggregate results.
10123 16 Cannot create %S_MSG on view “%.*ls” because it contains a join that uses deprecated Transact-SQL join syntax ( *= and =* ). Consider using = operator (non-outer-join) instead.
10124 16 Cannot create %S_MSG on view “%.*ls” because it references an internal SQL Server column.
10125 16 Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls”. Consider eliminating the aggregate, not indexing the view, or using alternate aggregates. For example, for AVG substitute SUM and COUNT_BIG, or for COUNT, substitute COUNT_BIG.
10126 16 Cannot create %S_MSG on view “%.*ls” because it uses aggregate “%.*ls” with the DISTINCT keyword. Consider not indexing this view or eliminating DISTINCT. Consider use of a GROUP BY or COUNT_BIG(*) view to simulate DISTINCT on grouping columns.
10127 16 Cannot create %S_MSG on view “%.*ls” because it contains one or more subqueries. Consider changing the view to use only joins instead of subqueries. Alternatively, consider not indexing this view.
10128 16 Cannot create %S_MSG on view “%.*ls” because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or not indexing the view.
10129 16 Cannot create %S_MSG on view “%.*ls” because it references the inline or multistatement table-valued function “%.*ls”. Consider expanding the function definition by hand in the view definition, or not indexing the view.
10130 16 Cannot create %S_MSG on view “%.*ls” because it uses non-deterministic common language runtime (CLR) table-valued function “%.*ls”. Consider not indexing the view or changing it to not use this function.
10131 16 Cannot create %S_MSG on view “%.*ls” because it references imprecise common language runtime (CLR) table-valued function “%.*ls”. Consider not indexing the view.
10132 16 Cannot create %S_MSG on view “%.*ls” because it references table valued common language runtime (CLR) function “%.*ls”. Consider removing reference to the function or not indexing the view. 10133 16 Cannot create %S_MSG on view “%.*ls” because function “%.*ls” referenced by the view performs user or system data access. 10134 16 Cannot create %S_MSG on view “%.*ls” because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY.
10135 16 Cannot create %S_MSG on view “%.*ls” because it contains an UNNEST. Consider not indexing the view, or removing UNNEST.
10136 16 Cannot create %S_MSG on view “%.*ls” because it uses the aggregate COUNT. Use COUNT_BIG instead.
10137 16 Cannot create %S_MSG on view “%.*ls” because it references common table expression “%.*ls”. Views referencing common table expressions cannot be indexed. Consider not indexing the view, or removing the common table expression from the view definition.
10138 16 Cannot create %S_MSG on view ‘%.*ls’ because its select list does not include a proper use of COUNT_BIG. Consider adding COUNT_BIG(*) to select list.
10139 16 Cannot create %S_MSG on view ‘%.*ls’ because the view uses an implicit conversion from string to datetime or smalldatetime. Use an explicit CONVERT with a deterministic style value.
10140 16 Cannot create %S_MSG on view ‘%.*ls’ because the view contains a table hint. Consider removing the hint.
10141 16 Cannot create %S_MSG on view ‘%.*ls’ because it references CLR routine (function or method) ‘%.*ls’ outside non-key columns of SELECT list. Recreate or alter view so it does not reference CLR routines except in non-key columns of SELECT list, and then create index.
10142 16 Cannot create %S_MSG on view “%.*ls” because it contains an APPLY. Consider not indexing the view, or removing APPLY.
10143 16 Cannot create %S_MSG on view “%.*ls” because it contains a ranking or aggregate window function. Remove the function from the view definition or, alternatively, do not index the view.
10208 16 Cannot create parameter, column or declare variable of multiset built-in system type.
10211 16 Cannot invoke mutator on a null user-defined type value. 10227 16 Field “%.*ls” of type “%.*ls.%.*ls” cannot be updated because the field is “%.*ls”.
10240 16 Could not find UdtExtensions.dll. Please check your installation.
10300 16 Assembly ‘%.*ls’ references assembly ‘%.*ls’, which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %S_MSG). Please load the referenced assembly into the current database and retry your request.
10301 16 Assembly ‘%.*ls’ references assembly ‘%.*ls’, which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: %s). Please load the referenced assembly into the current database and retry your request.
10302 16 Could not get path for SQL server: ‘%ls’.
10303 16 Could not create AppDomain manager: ‘%.*ls’.
10304 16 Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions.
10305 16 The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.
10306 16 The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property. 10307 16 The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name.
10308 10 Warning: The Microsoft .Net frameworks assembly ‘%.*ls’ you are registering is not fully tested in SQL Server hosted environment. 10309 10 Warning: The SQL Server client assembly ‘%.*ls’ you are registering is not fully tested in SQL Server hosted environment. 10310 10 AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
10311 10 AppDomain %i (%.*ls) is marked for unload due to memory pressure.
10312 16 .NET Framework execution was aborted. The UDP/UDF/UDT did not revert thread token.
10313 16 An error occurred while using the .NET Framework during %S_MSG. The server may be running out of resources. Try running the query again. If the problem persist, contact a support professional. %.*ls 10314 16 An error occurred in the Microsoft .NET Framework while trying to load assembly id %d. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: %.*ls 10316 16 The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found.
10317 16 An error occurred trying to get file version info for the file ‘%s’.
10318 16 ‘%.*ls’ failed because parameter %d of method ‘%.*ls’ of type ‘%.*ls’ is annotated with unsupported attribute
System.ParamArrayAttribute.
10319 16 UserDefinedType method call failed because parameter %d of method ‘%.*ls’ of type ‘%.*ls’ is annotated with unsupported attribute System.ParamArrayAttribute.
10320 16 Method name ‘%.*ls’ is invalid for ‘%.*ls’.
10321 16 Method name ‘%.*ls’ is invalid for UserDefinedType method call.
10322 16 Type %.*ls not found in database %.*ls
10323 16 Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls
10324 16 WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers.
10325 16 The server is shutting down due to stack overflow in user’s unmanaged code.
10326 16 Two versions of assembly ‘%.*ls’ cannot coexist in database ‘%.*ls’. Keep one version and drop the other.
10327 14 %ls ASSEMBLY for assembly ‘%.*ls’ failed because assembly ‘%.*ls’ is not authorized for PERMISSION_SET = %ls. The assembly is authorized when either of the following is true: the database owner (DBO) has %ls permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with %ls permission. If you have restored or attached this database, make sure the database owner is mapped to the correct login on this server. If not, use sp_changedbowner to fix the problem.
10501 16 Cannot create plan guide ‘%.*ls’ because type ‘%.*ls’ provided is not allowed.
10502 16 Cannot create plan guide ‘%.*ls’ because @stmt and
@module_or_batch match an existing plan guide ‘%.*ls’ in the database. 10503 16 Operation ‘%.*ls’ is not allowed.
10504 16 Cannot create plan guide ‘%.*ls’ because parameter @hints is incorrect. Use N’OPTION ( [ ,…n ] )’.
10505 16 Cannot create plan guide ‘%.*ls’ because value ‘%.*ls’ provided for @module_or_batch is not legal two-part name. Use ‘schema_name.object_name’.
10506 16 Cannot create plan guide ‘%.*ls’ because parameter @stmt has more than one statement.
10507 16 Cannot create plan guide ‘%.*ls’ because @stmt does not match any statement in specified module or batch. Consider modifying @stmt to match a statement in module or batch.
10508 16 Cannot ‘%ls’ plan guide ‘%.*ls’ because it does not exist or you do not have permission. Verify plan guide name and database of current session, and that you have needed permission.
10509 16 Cannot create plan guide ‘%.*ls’ because statement @stmt contains a syntax error or is not eligible for plan guide. Provide a single legal statement.
10510 16 Cannot create plan guide ‘%.*ls’ because there is already a plan guide with that name in the database. Use a unique name. 10511 16 Cannot create plan guide ‘%.*ls’ because @params is not NULL. @params must be NULL if @type is ‘object’.
10512 16 Cannot create plan guide ‘%.*ls’ because object
‘@module_or_batch’ is encrypted. Consider tuning query using other techniques such as indexes and statistics.
10513 16 Cannot %S_MSG %S_MSG ‘%.*ls’ because it is referenced by plan guide ‘%.*ls’. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.
10514 16 Cannot create plan guide ‘%.*ls’ because @module_or_batch can not be large object when @type is object.
10515 16 Cannot create plan guide ‘%.*ls’ because the module ‘%.*ls’ does not exist or you do not have needed permission.
10516 16 Cannot create plan guide ‘%.*ls’ because @module_or_batch can not be compiled.
10517 16 Cannot create plan guide ‘%.*ls’ because you do not have needed permission. Alter database permission required.
10518 16 Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide ‘%.*ls’. Alter permission on object referenced by plan guide, or alter database permission required. 10519 16 Cannot create plan guide ‘%.*ls’ because @hints can not be applied to @stmt.
10520 16 Cannot create plan guide ‘%.*ls’ because @type was specified as ‘template’ and @module_or_batch was specified.
10521 16 Cannot create plan guide ‘%.*ls’ because @params is NULL. @params must be non NULL if @type is ‘template’.
10522 16 Cannot create plan guide ‘%.*ls’ because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or
OPTION(PARAMETERIZATION SIMPLE) if @type is ‘template’.
10523 16 Cannot generate query template because @querytext does not contain a valid single query.
10524 16 Cannot parameterize @querytext.
10525 10 Plan guide ‘%.*ls’ matched statement after it was
parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains was ignored. RECOMPILE is not supported on automatically parameterized statements. Consider dropping this plan guide or removing RECOMPILE from it.
10526 16 Cannot drop %S_MSG ‘%.*ls’ because its trigger ‘%.*ls’ is referenced by plan guide ‘%.*ls’. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed. 10527 16 Cannot create plan guide ‘%.*ls’ because the object ‘%.*ls’ is a temporary object.
10528 16 Cannot create plan guide ‘%.*ls’ because its name is invalid. Plan guide name cannot begin with a ‘#’ character.
10529 16 Cannot create plan guide ‘%.*ls’ because there is already a planguide ‘%.*ls’ of @type ‘template’ on @stmt.
10601 16 Cannot specify included columns for a clustered index. 10602 16 Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
10603 16 Cannot rebuild clustered index ‘%.*ls’ on view ‘%.*ls’ because the view is dependent on base table ‘%.*ls’ whose clustered index ‘%.*ls’ is disabled.
10604 16 Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
10605 16 Cannot disable primary key index “%.*ls” on table “%.*ls” because the table is published for replication.
10606 16 Cannot disable the clustered index “%.*ls” on view “%.*ls” because the indexed view is published for replication.
10607 16 Merged or concatenated indexes cannot be created on temporary objects. The object ‘%.*ls’ is temporary.
10608 16 Cannot merge or concatenate more than %d indexes together. 10609 16 MERGE and CONCATENATE operations are mutually exclusive and cannot be specified together during index creation.
10610 16 MERGE and CONCATENATE operations can only be performed on objects in the same database. The object ‘%.*ls’ and ‘%.*ls’ are in different databases.
10611 16 MERGE and CONCATENATE operations can not merge objects of different types. The object ‘%.*ls’ and ‘%.*ls’ have types %S_MSG and %S_MSG respectively.
10612 16 If partition scheme is mentioned for one index it should be mentioned for all the indexes present in the CREATE INDEX statement. Partition scheme is not mentioned for index ‘%.*ls’.
10613 16 All partition schemes and filegroups specified for
individual indexes in a merged index should be identical. ‘%.*ls’ and ‘%.*ls’ are not identical.
10614 16 An index name cannot be specified for the same object multiple times. Index name ‘%.*ls’ is specified for object ‘%.*ls’ more than once.
10615 16 Only one clustered index can be mentioned for a table or view. Index ‘%.*ls’ and ‘%.*ls’ are both specified as clustered Index for object ‘%.*ls’.
10616 10 Warning: Leading index column of index ‘%.*ls’ and ‘%.*ls’ are not of the same type. The merge index operation will result in index concatenation.
10617 16 : Index ‘%.*ls’ could not be created or rebuilt. This index has a maximum key length of %d bytes with vardecimal storage format. This length exceeds the maximum allowed key length of %d bytes.
10705 15 Subqueries are not allowed in the OUTPUT clause.
11000 16 Unknown status code for this column.
11001 16 Non-NULL value successfully returned.
11002 16 Deferred accessor validation occurred. Invalid binding for this column.
11003 16 Could not convert the data value due to reasons other than sign mismatch or overflow.
11004 16 Successfully returned a NULL value.
11005 16 Successfully returned a truncated value.
11006 16 Could not convert the data type because of a sign mismatch. 11007 16 Conversion failed because the data value overflowed the data type used by the provider.
11008 16 The provider cannot allocate memory or open another storage object on this column.
11009 16 The provider cannot determine the value for this column. 11010 16 The user did not have permission to write to the column. 11011 16 The data value violated the integrity constraints for the column.
11012 16 The data value violated the schema for the column.
11013 16 The column had a bad status.
11014 16 The column used the default value.
11015 16 The column was skipped when setting data.
11031 16 The row was successfully deleted.
11032 16 The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source. 11033 16 The row was released even though it had a pending change. 11034 16 Deletion of the row was canceled during notification. 11036 16 The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
11037 16 The row has a pending delete or the deletion had been transmitted to the data source.
11038 16 The row is a pending insert row.
11039 16 DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source. 11040 16 Deleting the row violated the integrity constraints for the column or table.
11041 16 The row handle was invalid or was a row handle to which the current thread does not have access rights.
11042 16 Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.
11043 16 The row has a storage object open.
11044 16 The provider ran out of memory and could not fetch the row. 11045 16 User did not have sufficient permission to delete the row. 11046 16 The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.
11047 16 Updating did not meet the schema requirements.
11048 16 There was a recoverable, provider-specific error, such as an RPC failure.
11100 16 The provider indicates that conflicts occurred with other properties or requirements.
11101 16 Could not obtain an interface required for text, ntext, or image access.
11102 16 The provider could not support a required row lookup interface.
11103 16 The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.
11104 16 The provider could not support insertion on this table. 11105 16 The provider could not support updates on this table. 11106 16 The provider could not support deletion on this table. 11107 16 The provider could not support a row lookup position. 11108 16 The provider could not support a required property. 11109 16 The provider does not support an index scan on this data source.
11201 16 This message could not be delivered because the FROM service name is missing. The message origin is: ‘%ls’.
11202 16 This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: “%.*ls”. Message origin: “%ls”.
11203 16 This message has been dropped because the FROM broker instance is missing. The message origin is ‘%ls’.
11204 16 This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: “%.*ls”. Message origin: “%ls”.
11205 16 This message has been dropped because the TO service name is missing. The message origin is “%ls”.
11206 16 This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: “%.*ls”. Message origin: “%ls”.
11207 16 This message has been dropped because the service contract name is missing. The message origin is “%ls”.
11208 16 This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name “%.*ls”. Message origin: “%ls”.
11209 16 This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: ‘%ls’.
11210 16 This message has been dropped because the TO service could not be found. Service name: “%.*ls”. Message origin: “%ls”.
11211 16 This message has been dropped because the user does not have permission to access the target database. Database ID: %d. Message origin: &quot;%ls&quot;.
11212 16 This message could not be delivered because the conversation endpoint has already been closed.
11213 16 This message could not be delivered because this is not the first message in the conversation.
11214 16 This message could not be delivered because the ‘%.*ls’ contract could not be found or the service does not accept conversations for the contract.
11215 16 This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: ‘%.*ls’.
11216 16 This message could not be delivered because there is already another task processing this message.
11217 16 This message could not be delivered because it is out of sequence with respect to the conversation. Conversation receive sequence number: %I64d, Message sequence number: %I64d.
11218 16 This message could not be delivered because it is a duplicate.
11219 16 This message could not be delivered because the destination queue has been disabled. Queue ID: %d.
11220 16 This message could not be delivered because the TO broker instance is missing.
11221 16 This message could not be delivered because there is an inconsistency in the message header.
11222 16 This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Service Name: ‘%.*ls’. Conversation Endpoint TO Service Name: ‘%.*ls’.
11223 16 This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Message service contract name: ‘%.*ls’. Conversation endpoint service contract name: ‘%.*ls’.
11224 16 This message could not be delivered because another instance of this service program has already started conversing with this endpoint. 11225 16 This message could not be delivered because the message type name could not be found. Message type name: ‘%.*ls’.
11226 16 This message could not be delivered because the message type is not part of the service contract. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’.
11227 16 This message could not be delivered because the initiator service has sent a message with a message type that can only be sent by the target. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’. 11228 16 This message could not be delivered because the target service has sent a message with a message type that can only be sent by the initiator. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’. 11229 16 This message could not be delivered because the security context could not be retrieved.
11230 16 This message could not be delivered because the message could not be decrypted and validated.
11231 16 This message could not be delivered because the conversation endpoint is not secured, however the message is secured.
11232 16 This message could not be delivered because the conversation endpoint is secured, however the message is not secured.
11233 16 This message has been dropped because the session key of the conversation endpoint does not match that of the message.
11234 16 This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls. 11235 16 Received a malformed message. The binary message class (%d:%d) is not defined. This may indicate network problems or that another application is connected to the Service Broker endpoint.
11236 16 A corrupt message has been received. The binary header size of %d is expected, however the header size received was %d.
11237 16 A %S_MSG message could not be processed due to insufficient memory. The message was dropped.
11238 16 A corrupt message has been received. The private variable data segment is malformed.
11239 16 A corrupt message has been received. The private variable data segment extends beyond the length of the message.
11240 16 A corrupt message has been received. The binary message preamble is malformed.
11241 16 A corrupt message has been received. The conversation security version number is not %d.%d.
11242 16 A corrupt message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found: %d.
11243 16 A corrupt message has been received. The public variable data element (%d) has been duplicated in this message.
11244 16 A corrupt message has been received. The handshake
validation header is malformed.
11245 16 A corrupt message has been received. The maximum number of private variable data elements (%d) has been exceeded. Private variable data elements found: %d.
11246 16 A corrupt message has been received. The private variable data element (%d) has been duplicated in this message.
11247 16 A corrupt message has been received. The login negotiate header is invalid.
11248 16 A corrupt message has been received. The SSPI login header is invalid.
11249 16 A corrupt message has been received. The pre-master-secret is invalid.
11250 16 A corrupt message has been received. The security
certificate key fields must both be present or both be absent. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11251 16 A corrupt message has been received. The service pair security header source certificate and the signature must both be present or both be absent. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11252 16 A corrupt message has been received. The destination certificate serial number is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11253 16 A corrupt message has been received. The service pair security header destination certificate, the key exchange key, the key exchange key ID, and the session key must all be present or all be absent. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11254 16 A corrupt message has been received. The session key ID is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11255 16 A corrupt message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11256 16 A corrupt message has been received. The MIC is present, however the message body or encryption flag is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11257 16 A corrupt message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11258 16 A corrupt message has been received. The MIC size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11259 16 A corrupt message has been received. The certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11260 16 A corrupt message has been received. The certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11261 16 A corrupt message has been received. The destination certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11262 16 A corrupt message has been received. The destination certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11263 16 A corrupt message has been received. The service pair security header size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11264 16 A corrupt message has been received. The key exchange key size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11265 16 A corrupt message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11266 16 A corrupt message has been received. The encrypted session key size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11267 16 A corrupt message has been received. The session key ID size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11268 16 A corrupt message has been received. The salt size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11269 16 A corrupt message has been received. A UNICODE string is not two byte aligned within the message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11270 16 A corrupt message has been received. A UNICODE string is greater than the maximum allowed size of %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11271 16 A corrupt message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11272 16 A corrupt message has been received. The message ID must not be NULL.
11273 16 A corrupt message has been received. The message body is not properly padded for encryption. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11274 16 A corrupt message has been received. A sequence number is larger than allowed. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11275 16 A corrupt message has been received. The End of Conversation and Error flags are both set. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11276 16 A corrupt message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11277 16 A corrupt message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11278 16 A corrupt message has been received. The message type is missing for this message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
11279 16 A corrupt message has been received. The message type must not be set in this message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11280 16 A packet of size %lu bytes could not be processed because it exceeds the receive buffer count.
11281 16 A corrupt message has been received. The private portion of the message header is malformed.
11282 16 This message has been dropped due to licensing restrictions. See the documentation for further details.
11285 16 This forwarded message has been dropped because the hops remaining count has reached 0.
11286 16 Dropped this forwarded message because this SQL Server instance is out of memory.
11288 16 This forwarded message has been dropped because a duplicate message is already being forwarded.
11289 16 This forwarded message has been dropped because its memory usage would exceed the configured memory limit of %d MB for forwarded messages.
11290 16 This forwarded message was dropped because the message could not be delivered within the message time to live. This may indicate that the forwarding route is incorrectly configured or that the destination is unavailable.
11291 16 This forwarded message has been dropped because the time consumed has exceeded the message’s time to live of %u seconds (the message arrived with %u seconds consumed and used %u seconds in this broker). 11292 16 The forwarded message has been dropped because a transport send error occurred when sending the message. Check previous events for the error.
11293 16 This forwarded message has been dropped because a transport is shutdown.
11294 16 This forwarded message has been dropped because the destination route is not valid.
11295 10 Endpoint configuration change detected. Service Broker manager and transport will now restart.
11296 10 Certificate change detected. Service Broker manager and transport will now restart.
11297 16 A corrupt message has been received. The private variable data segment offset is incorrect.
11298 16 A corrupt message has been received. The public variable data segment offset is incorrect.
11299 10 A corrupt message has been received. An unsequenced message had a non-zero sequence number. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. 11300 10 Error wile committing a readonly or a TEMPDB XDES, Shutting down the server.
11301 10 Error while performing transaction notification for object %p event %d.
11302 10 Error during rollback. shutting down database (location: %d).
11303 10 Error releasing reserved log space: %ls space %I64d, code %d, state %d.
11304 10 Failed to record outcome of a local two-phase commit transaction. Taking database offline.
11501 10 Guardian is checkpointing database ‘%.*ls’ (%d)
12980 16 Supply either %s or %s to identify the log entries. 12981 16 You must specify %s when creating a subplan.
12982 16 Supply either %s or %s to identify the plan or sub-plan to be run.
13001 0 data page
13002 0 index page
13003 0 leaf page
13004 0 last
13005 0 root
13006 0 read from
13007 0 send to
13008 0 receive
13009 0 send
13010 0 read
13011 0 wait
13012 0 a USE database statement
13013 0 a procedure, function or trigger
13014 0 a DISTINCT clause
13015 0 a view
13016 0 an INTO clause
13017 0 an ORDER BY clause
13018 0 a COMPUTE clause
13019 0 a SELECT INTO statement
13020 0 option
13021 0 offset option
13022 0 statistics option
13023 0 parameter option
13024 0 function name
13025 0 varbinary (128) NOT NULL
13026 0 parameter
13027 0 convert specification
13028 0 index
13029 0 table
13030 0 database
13031 0 procedure
13032 0 trigger
13033 0 view
13034 0 default
13035 0 rule
13036 0 system table
13037 0 unknown type
13038 0 SET option
13039 0 column
13040 0 type
13041 0 character string
13042 0 integer
13043 0 identifier
13044 0 number
13045 0 integer value
13046 0 floating point value
13047 0 object
13048 0 column heading
13049 0 built-in function name
13050 0 aggregate function
13051 0 XML INDEX
13052 0 user defined type
13053 0 xml schema collection
13057 0 a planguide batch
13076 0 an assignment
13077 0 a cursor declaration
13078 0 replication filter
13079 0 variable assignment
13080 0 statistics
13081 0 file
13082 0 filegroup
13083 0 server
13084 0 write
13085 0 function
13086 0 database collation
13087 0 drop
13088 0 alter
13089 0 message type
13090 0 contract
13092 0 service
13093 0 queue
13094 0 table valued function
13095 0 event notification
13096 0 synonym
13097 0 lock
13098 0 thread
13099 0 communication buffer
13100 0 Common Language Runtime critical section
13101 0 partition scheme
13102 10 DETACH
13103 0 HASH
13104 0 RANGE
13105 0 create
13106 0 route
13107 0 remote service binding
13108 0 Initiator
13109 0 Target
13110 0 host synchronization object
13111 0 generic waitable object
13112 0 application role
13113 0 schema
13114 0 user
13115 0 login
13116 0 certificate
13117 0 role
13118 0 find
13119 0 endpoint
13120 0 sql:variable
13121 0 sql:column
13122 0 XML namespace
13123 0 assembly
13124 0 fulltext catalog
13125 16 execute as
13126 16 symmetric key
13127 16 principal
13128 16 security descriptor
13129 16 hypothetical index
13130 16 nonclustered index
13131 16 credential
13132 0 transfer
13133 0 Cumulative wait time (ms) per second
13134 0 Waits started per second
13135 0 Waits in progress
13136 0 Average wait time (ms)
13137 0 Cumulative execution time (ms) per second
13138 0 Execs started per second
13139 0 Execs in progress
13140 0 Average execution time (ms)
13141 16 asymmetric key
13142 0 an INSERT SELECT statement
13143 16 partition function
13144 16 partition scheme
13145 16 encryption
13146 16 signature
13147 16 password
13148 16 rename
13149 16 end dialog
13150 16 END CONVERSATION WITH ERROR
13151 16 MOVE CONVERSATION
13152 16 receive sequenced message
13153 16 receive end conversation
13154 16 receive end conversation with error
13155 16 receive broker error
13156 16 receive message acknowledgement
13157 16 terminate conversation
13158 16 broker error
13160 16 BEGIN CONVERSATION TIMER
13161 16 fire conversation timer
13162 16 END CONVERSATION WITH CLEANUP
13163 16 BEGIN DIALOG CONVERSATION
13164 16 SEND
13165 16 conversation
13166 16 conversation group
13167 16 system
13168 16 Service Broker
13169 16 Database Mirroring
13170 0 table or indexed view
13171 16 conversation handle
13172 16 GET CONVERSATION GROUP
13173 16 master key
13174 16 another assembly with same SQL name is already present in the current database
13175 16 version, culture or public key mismatch
13176 0 component
13177 16 IL compilation
13178 16 Inproc data access
13179 16 DDL operations
13180 16 execution cache cleanup
13181 16 unspecified operation
13182 16 dialog
13183 10 The certificate’s private key cannot be found
13184 10 The certificate’s private key size is incompatible with the crypto provider
13185 10 The certificate’s public key size is incompatible with the crypto provider
13186 10 The certificate’s private key size is incompatible with the encrypted key exchange key
13187 10 The certificate’s public key size is incompatible with the security header’s signature
13188 10 The certificate’s private key is password protected 13189 10 The key exchange key has an invalid size after being decrypted with the certificate private key
13190 10 The database principal used to lookup the cert is invalid 13191 10 The database principal has no mapping to a server principal 13192 10 The certificate is disabled for BEGIN DIALOG
13193 16 encryption algorithm
13194 16 authentication protocol
13195 10 Certificate not found
13196 10 Certificate not yet valid
13197 10 Certificate expired
13198 10 Certificate is larger than maximum allowed size
13199 10 message timestamp
13202 10 TO BROKER INSTANCE
13203 10 TO SERVICE
13204 10 FROM BROKER INSTANCE
13205 10 FROM SERVICE
13206 10 SERVICE CONTRACT
13207 10 MESSAGE TYPE
13208 10 MESSAGE INTEGRITY CHECK
13209 10 KEY SALT
13210 10 SESSION KEY
13211 10 KEY EXCHANGE KEY
13212 10 SOURCE CERTIFICATE ISSUER NAME
13213 10 SOURCE CERTIFICATE SERIAL NUMBER
13214 10 DESTINATION CERTIFICATE ISSUER NAME
13215 10 DESTINATION CERTIFICATE SERIAL NUMBER
13216 10 SECURITY HEADER SIGNATURE
13217 10 MESSAGE BODY
13218 10 STATEMENT
13219 10 clustered index
13220 10 primary xml index
13221 10 Failover
13222 10 Auto Failover
13223 10 Failover from partner
13224 10 Role Syncronization
13225 10 Force_Service_Allow_Data_Loss
13229 10 enable
13230 10 disable
13231 10 remap
14002 16 Could not find the ‘Sync’ subsystem with the task ID %ld. 14003 16 You must supply a publication name.
14004 16 %s must be in the current database.
14005 16 Cannot drop the publication because at least one
subscription exists for this publication. Drop all subscriptions to the publication before attempting to drop the publication. If the problem persists, replication metadata might be incorrect; consult Books Online for troubleshooting information.
14006 16 Could not drop the publication.
14008 11 There are no publications.
14009 11 There are no articles for publication ‘%s’.
14010 16 The remote server ‘%s’ is not defined as a subscription server. Ensure you specify the server name rather than a network alias. 14011 16 Unable to mark sysservers entry ‘%s’ as a non SQL Server subscriber.
14012 16 The @status parameter value must be either ‘active’ or ‘inactive’.
14013 16 This database is not enabled for publication.
14014 16 The synchronization method (@sync_method) must be ‘[bcp] native’, ‘[bcp] character’, ‘concurrent’, ‘concurrent_c’, ‘database snapshot’, or ‘database snapshot character’.
14015 16 The replication frequency (@repl_freq) must be either ‘continuous’ or ‘snapshot’.
14016 16 The publication ‘%s’ already exists.
14017 16 Invalid @restricted parameter value. Valid options are ‘true’ or ‘false’.
14018 16 Could not create the publication.
14019 16 The @operation parameter value must be either add, drop, or alter.
14020 16 Could not obtain the column ID for the specified column. Schema replication failed.
14021 16 The column was not added correctly to the article.
14022 16 The @property parameter value must be either ‘description’, ‘sync_object’, ‘type’, ‘ins_cmd’, ‘del_cmd’, ‘upd_cmd’, ‘filter’, ‘dest_table’, ‘dest_object’, ‘creation_script’, ‘pre_creation_cmd’, ‘status’, ‘schema_option’, or ‘destination_owner’.
14023 16 The type must be ‘[indexed view ]logbased[
(manualview|manualfilter|manualboth)]’, ‘[serializable ]proc exec’, or ‘(view|indexed view|proc|func|aggregate|synonym) schema only’. 14024 16 The value of property ‘subscriber_provider’ cannot be NULL. 14025 10 Article update successful.
14026 16 The value of property ‘subscriber_type is not a supported heterogeneous subscriber type. The value must be 1 (ODBC subscriber), or 3 (OLEDB subscriber).
14027 11 %s does not exist in the current database.
14028 16 Only user tables, materialized views, and stored procedures can be published as ‘logbased’ articles.
14029 16 The vertical partition switch must be either ‘true’ or ‘false’.
14030 16 The article ‘%s’ exists in publication ‘%s’.
14031 16 User tables and views are the only valid synchronization objects.
14032 16 The value of parameter %s cannot be ‘all’. It is reserved by replication stored procedures.
14033 16 Could not change replication frequency because there are active subscriptions on the publication.
14034 16 The publication name (@publication) cannot be the keyword ‘all’.
14035 16 The replication option ‘%s’ of database ‘%s’ has already been set to true.
14036 16 Could not enable database for publishing.
14037 16 The replication option ‘%s’ of database ‘%s’ has been set to false.
14038 16 Could not disable database for publishing.
14039 16 Could not construct column clause for article view. Reduce the number of columns or create the view manually.
14040 16 The server ‘%s’ is already a Subscriber.
14041 16 The ‘%s’ property can only be changed if the publication is enabled for heterogeneous subscriptions. The publication is not enabled. 14042 16 Could not create Subscriber.
14043 16 The parameter %s passed to stored procedure %s cannot be NULL.
14044 16 Unable to clear subscriber status from sysservers entry. 14045 16 Unable to update subscriber_type in MSdistribution_agents table.
14046 16 Could not drop article. A subscription exists on it. 14047 16 Could not drop %s.
14048 16 The server ‘%s’ is not a Subscriber.
14049 16 Stored procedures for replication are the only objects that can be used as a filter.
14050 11 No subscription is on this publication or article.
14051 16 The parameter value must be ‘sync_type’ or ‘dest_db’. 14052 16 The @sync_type parameter value must be “automatic”, “none”, “replication support only”, “initialize with backup”, or “initialize from lsn”.
14053 16 The subscription could not be updated at this time. 14054 10 The subscription was updated successfully.
14055 10 The subscription does not exist.
14056 16 The subscription could not be dropped at this time. 14057 16 The subscription could not be created.
14058 16 Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.
14059 16 Materialized view articles cannot be created for
publications with the properties allow_sync_tran, allow_queued_tran, or allow_dts.
14060 16 Subscriber parameters specifying provider properties must be NULL for SQL Server subscribers.
14061 16 The @pre_creation_cmd parameter value must be ‘none’, ‘drop’, ‘delete’, or ‘truncate’.
14062 10 The Subscriber was dropped.
14063 11 The remote server does not exist or has not been designated as a valid Subscriber.
14065 16 The @status parameter value must be ‘initiated’, ‘active’, ‘inactive’, or ‘subscribed’.
14066 16 The previous status must be ‘active’, ‘inactive’, or ‘subscribed’.
14067 16 The status value is the same as the previous status value. 14068 16 Could not update sysobjects. The subscription status could not be changed.
14069 16 Could not update sysarticles. The subscription status could not be changed.
14070 16 Could not update the distribution database subscription table. The subscription status could not be changed.
14071 16 Could not find the Distributor or the distribution database for the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor. 14074 16 The server ‘%s’ is already listed as a Publisher.
14075 16 The Publisher could not be created at this time.
14076 16 Could not grant replication login permission to ‘%s’. 14077 10 The publication was updated successfully.
14078 16 The parameter must be ‘description’, ‘taskid’,
‘sync_method’, ‘status’, ‘repl_freq’, ‘restricted’, ‘retention’, ‘immediate_sync’, ‘enabled_for_internet’, ‘allow_push’, ‘allow_pull’, ‘allow_anonymous’, or ‘retention’.
14080 16 The remote server “%s” does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers.
14085 16 The Subscriber information could not be obtained from the Distributor.
14088 16 The table ‘%s’ must have a primary key to be published using the transaction-based method.
14089 16 The clustered index on materialized view ‘%s’ may not contain nullable columns if it is to be published using the
transaction-based method.
14090 16 Error evaluating article synchronization object after column drop. The filter clause for article ‘%s’ must not reference the dropped column.
14091 16 The @type parameter passed to sp_helpreplicationdb must be either ‘pub’ or ‘sub’.
14092 16 Could not change article because there is an existing subscription to the article.
14093 16 Cannot grant or revoke access directly on publication ‘%s’ because it uses the default publication access list.
14094 16 Could not subscribe to article ‘%s’ because heterogeneous Subscriber ‘%s’ does not support the @pre_creation_cmd parameter value ‘truncate’.
14095 16 The value for the @sync_method parameter is not valid. Could not subscribe to publication ‘%s’ because non-SQL Server Subscriber ‘%s’ only supports values of ‘character’, ‘bcp character’, ‘concurrent_c’, and ‘database snapshot character’ for the @sync_method parameter. 14096 16 The path and name of the table creation script must be specified if the @pre_creation_cmd parameter value is ‘drop’. 14097 16 The ‘status’ value must be ‘no column names’, ‘include column names’, ‘string literals’, ‘parameters’, ‘DTS horizontal partitions’ or ‘no DTS horizontal partitions’.
14098 16 Cannot drop Distribution Publisher ‘%s’. The remote Publisher is using ‘%s’ as Distributor. Disable publishing at the Publisher before attempting to drop this relationship.
14099 16 The server ‘%s’ is already defined as a Distributor. To reconfigure the server as a Distributor, you must first uninstall the exisiting Distributor. Use the stored procedure sp_dropdistributor, or use the Disable Publishing and Distribution Wizard.
14100 16 Specify all articles when subscribing to a publication using concurrent snapshot processing.
14101 16 The publication ‘%s’ already has a Snapshot Agent defined. 14102 16 Specify all articles when unsubscribing from a publication using concurrent snapshot processing.
14103 16 Invalid “%s” value. Valid values are “publisher”,
“subscriber”, or “both”.
14105 10 You have updated the distribution database property ‘%s’ successfully.
14106 16 Distribution retention periods must be greater than or equal to 0.
14107 10 The @max_distretention value must be larger than the @min_distretention value.
14108 10 Removed %ld history records from %s.
14109 10 The @security_mode parameter value must be 0 (SQL Server Authentication) or 1 (Windows Authentication).
14110 16 For stored procedure articles, the @property parameter value must be ‘description’, ‘dest_table’, ‘dest_object’, ‘creation_script’, ‘pre_creation_cmd’, ‘schema_option’, or ‘destination_owner’. 14111 16 The @pre_creation_cmd parameter value must be ‘none’ or ‘drop’.
14112 16 This procedure can be executed only against table-based articles.
14113 16 Could not execute ‘%s’. Check ‘%s’ in the install directory. 14114 16 The server ‘%s’ is not configured as a Distributor. 14115 16 The property parameter value must be %s.
14117 16 ‘%s’ is not configured as a distribution database.
14118 16 A stored procedure can be published only as a ‘serializable proc exec’ article, a ‘proc exec’ article, or a ‘proc schema only’ article. 14119 16 Could not add the distribution database ‘%s’. This
distribution database already exists.
14120 16 Could not drop the distribution database ‘%s’. This distributor database is associated with a Publisher.
14121 16 Could not drop the Distributor ‘%s’. This Distributor has associated distribution databases.
14122 16 The @article parameter value must be ‘all’ for
immediate_sync publications.
14123 16 The subscription @sync_type parameter value ‘manual’ is no longer supported.
14124 16 A publication must have at least one article before a subscription to it can be created.
14126 16 You do not have the required permissions to complete the operation.
14128 16 Invalid @subscription_type parameter value. Valid options are ‘push’ or ‘pull’.
14129 16 The @status parameter value must be NULL for ‘automatic’ sync_type when you add subscriptions to an immediate_sync publication. 14135 16 There is no subscription on Publisher ‘%s’, publisher database ‘%s’, publication ‘%s’.
14136 16 The keyword ‘all’ is reserved by replication stored procedures.
14137 16 The @value parameter value must be either ‘true’ or ‘false’. 14138 16 Invalid option name ‘%s’.
14139 16 The replication system table ‘%s’ already exists.
14143 16 Cannot drop Distributor Publisher ‘%s’. There are
Subscribers associated with it in the distribution database ‘%s’. 14144 16 Cannot drop Subscriber ‘%s’. There are subscriptions for it in the publication database ‘%s’.
14146 16 The article parameter ‘@schema_option’ cannot be NULL. 14147 16 Restricted publications are no longer supported.
14148 16 Invalid ‘%s’ value. Valid values are ‘true’ or ‘false’. 14149 10 Removed %ld replication history records in %s seconds (%ld row/secs).
14150 10 Replication-%s: agent %s succeeded. %s
14151 18 Replication-%s: agent %s failed. %s
14152 10 Replication-%s: agent %s scheduled for retry. %s
14153 10 Replication-%s: agent %s warning. %s
14154 16 The Distributor parameter must be ‘@heartbeat_interval’. 14155 16 Invalid article ID specified for procedure script
generation.
14156 16 The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format. 14157 10 The subscription created by Subscriber ‘%s’ to publication ‘%s’ has expired and has been dropped.
14158 10 Replication-%s: agent %s: %s.
14159 16 Could not change property ‘%s’ for article ‘%s’ because there is an existing subscription to the article.
14160 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and change the expiration threshold value if necessary. 14161 10 The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latency requirement.
14162 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14163 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14164 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14165 10 One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
14166 10 Disable publishing ignored error msg %d, severity %d, state %d: %s.
14167 10 Subscription expiration
14168 10 Transactional replication latency
14169 10 Long merge over dialup connection
14170 10 Long merge over LAN connection
14171 10 Slow merge over LAN connection
14172 10 Slow merge over dialup connection
14173 16 Failed to set publication parameter %s because it is not supported in Workgroup sku.
14196 10 The agent has never been run.
14197 10 Value of %s parameter should be in the set %s
14198 10 The value of the %s parameter should be in the range %s. Verify that the specified parameter value is correct.
14199 10 The specified job ‘%s’ is not created for maintenance plans. Verify that the job has at least one step calling xp_sqlmaint. 14200 16 The specified ‘%s’ is invalid.
14201 10 0 (all steps) ..
14202 10 before or after @active_start_time
14203 10 sp_helplogins [excluding Windows NT groups]
14204 10 0 (non-idle), 1 (executing), 2 (waiting for thread), 3 (between retries), 4 (idle), 5 (suspended), 7 (performing completion actions)
14205 10 (unknown)
14206 10 0..n seconds
14207 10 -1 [no maximum], 0..n
14208 10 1..7 [1 = E-mail, 2 = Pager, 4 = NetSend]
14209 10 0..127 [1 = Sunday .. 64 = Saturday]
14210 10 notification
14211 10 server
14212 10 (all jobs)
14213 10 Core Job Details:
14214 10 Job Steps:
14215 10 Job Schedules:
14216 10 Job Target Servers:
14217 10 SQL Server Warning: ‘%s’ has performed a forced defection of TSX server ‘%s’. Run sp_delete_targetserver at the MSX in order to complete the defection.
14218 10 hour
14219 10 minute
14220 10 second
14221 16 This job has one or more notifications to operators other than ‘%s’. The job cannot be targeted at remote servers as currently defined.
14222 16 Cannot rename the ‘%s’ operator.
14223 16 Cannot modify or delete operator ‘%s’ while this server is a %s.
14224 10 Warning: The server name given is not the current MSX server (‘%s’).
14225 16 Warning: Could not determine local machine name. This prevents MSX operations from being posted.
14226 10 %ld history entries purged.
14227 10 Server defected from MSX ‘%s’. %ld job(s) deleted.
14228 10 Server MSX enlistment changed from ‘%s’ to ‘%s’.
14229 10 Server enlisted into MSX ‘%s’.
14230 10 SP_POST_MSX_OPERATION: %ld %s download instruction(s) posted.
14231 10 SP_POST_MSX_OPERATION Warning: The specified %s (‘%s’) is not involved in a multiserver job.
14232 16 Specify either a job_name, job_id, or an originating_server. 14233 16 Specify a valid job_id (or 0x00 for all jobs).
14234 16 The specified ‘%s’ is invalid (valid values are returned by %s).
14235 16 The specified ‘%s’ is invalid (valid values are greater than 0 but excluding %ld).
14236 10 Warning: Non-existent step referenced by %s.
14237 16 When an action of ‘REASSIGN’ is specified, the New Login parameter must also be supplied.
14238 10 %ld jobs deleted.
14239 10 %ld jobs reassigned to %s.
14240 10 Job applied to %ld new servers.
14241 10 Job removed from %ld servers.
14242 16 Only a system administrator can reassign ownership of a job. 14243 10 Job ‘%s’ started successfully.
14245 16 Specify either the @name, @id, or @loginname of the task(s) to be deleted.
14250 16 The specified %s is too long. It must contain no more than %ld characters.
14251 16 Cannot specify ‘%s’ as the operator to be notified. 14252 16 Cannot perform this action on a job you do not own. 14253 10 %ld (of %ld) job(s) stopped successfully.
14254 10 Job ‘%s’ stopped successfully.
14255 16 The owner (‘%s’) of this job is either an invalid login, or is not a valid user of database ‘%s’.
14256 16 Cannot start the job “%s” (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
14257 16 Cannot stop the job “%s” (ID %s) because it does not have any job server or servers defined. Associate the job with a job server by calling sp_add_jobserver.
14258 16 Cannot perform this operation while SQLServerAgent is starting. Try again later.
14260 16 You do not have sufficient permission to run this command. Contact your system administrator.
14261 16 The specified %s (‘%s’) already exists.
14262 16 The specified %s (‘%s’) does not exist.
14263 16 Target server ‘%s’ is already a member of group ‘%s’. 14264 16 Target server ‘%s’ is not a member of group ‘%s’.
14265 24 The MSSQLServer service terminated unexpectedly. Check the SQL Server error log and Windows System and Application event logs for possible causes.
14266 16 The specified ‘%s’ is invalid (valid values are: %s). 14267 16 Cannot add a job to the ‘%s’ job category.
14268 16 There are no jobs at this server that originated from server ‘%s’.
14269 16 Job ‘%s’ is already targeted at server ‘%s’.
14270 16 Job ‘%s’ is not currently targeted at server ‘%s’.
14271 16 A target server cannot be named ‘%s’.
14272 16 Object-type and object-name must be supplied as a pair. 14273 16 You must provide either @job_id or @job_name (and,
optionally, @schedule_name), or @schedule_id.
14274 16 Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server.
14275 16 The originating server must be either local server or MSX server.
14276 16 ‘%s’ is a permanent %s category and cannot be deleted. 14277 16 The command script does not destroy all the objects that it creates. Revise the command script.
14278 16 The schedule for this job is invalid (reason: %s).
14279 16 Supply either @job_name, @job_id or @originating_server. 14280 16 Supply either a job name (and job aspect), or one or more job filter parameters.
14281 10 Warning: The @new_owner_login_name parameter is not necessary when specifying a ‘DELETE’ action.
14282 16 Supply either a date (created or last modified) and a data comparator, or no date parameters at all.
14283 16 Supply @target_server_groups or @target_servers, or both. 14284 16 Cannot specify a job ID for a new job. An ID will be assigned by the procedure.
14285 16 Cannot add a local job to a multiserver job category. 14286 16 Cannot add a multiserver job to a local job category. 14287 16 The ‘%s’ supplied has an invalid %s.
14288 16 %s cannot be before %s.
14289 16 %s cannot contain ‘%s’ characters.
14290 16 This job is currently targeted at the local server so cannot also be targeted at a remote server.
14291 16 This job is currently targeted at a remote server so cannot also be targeted at the local server.
14292 16 There are two or more tasks named ‘%s’. Specify %s instead of %s to uniquely identify the task.
14293 16 There are two or more jobs named ‘%s’. Specify %s instead of %s to uniquely identify the job.
14294 16 Supply either %s or %s to identify the job.
14295 16 Frequency Type 0x2 (OnDemand) is no longer supported. 14296 16 This server is already enlisted into MSX ‘%s’.
14297 16 Cannot enlist into the local machine.
14298 16 This server is not currently enlisted into an MSX.
14299 16 Server ‘%s’ is an MSX. Cannot enlist one MSX into another MSX.
14301 16 Logins other than the current user can only be seen by members of the sysadmin role.
14303 16 Stored procedure ‘%s’ failed to access registry key. 14304 16 Stored procedure ‘%s’ can run only on Windows 2000 servers. 14305 16 Column ‘%.*ls’ does not exist in table ‘%.*ls’.
14306 16 The target server (TSX) version is not compatible with the master server (MSX) version (%ld.%ld.%ld).
14307 16 Access to Integration Services package ‘%s’ is denied. 14350 16 Cannot initialize COM library because CoInitialize failed. 14351 16 Cannot complete this operation because an unexpected error occurred.
14352 16 Cannot find Active Directory information in the registry for this SQL Server instance. Run sp_ActiveDirectory_SCP again.
14353 16 Cannot determine the service account for this SQL Server instance.
14354 16 Cannot start the MSSQLServerADHelper service. Verify that the service account for this SQL Server instance has the necessary permissions to start the MSSQLServerADHelper service.
14355 16 The MSSQLServerADHelper service is busy. Retry this operation later.
14356 16 The Windows Active Directory client is not installed properly on the computer where this SQL Server instance is running. LoadLibrary failed to load ACTIVEDS.DLL.
14357 16 Cannot list ‘%s’ in Active Directory because the name is too long. Active Directory common names cannot exceed 64 characters. 14359 16 Active Directory directory service is not enabled on the network, or it is not supported by the operating system.
14360 16 %s is already configured as TSX machine
14362 16 The MSX server must be running the Standard or Enterprise edition of SQL Server
14363 16 The MSX server is not prepared for enlistments [there must be an operator named ‘MSXOperator’ defined at the MSX]
14364 16 The TSX server is not currently enlisted
14365 16 Specify a valid schedule_uid.
14366 16 Only members of sysadmin role can modify the owner of a schedule.
14367 16 One or more schedules were not deleted because they are being used by at least one other job. Use “sp_detach_schedule” to remove schedules from a job.
14368 16 Schedule “%s” was not deleted because it is being used by at least one other job. Use “sp_detach_schedule” to remove schedules from a job.
14369 16 The schedule ID “%s” is used by more than one job. Specify the job_id.
14370 16 The @originating_server must be either the local server name or the master server (MSX) name for MSX jobs on a target server (TSX). 14371 16 There are two or more schedules named “%s”. Specify %s instead of %s to uniquely identify the schedule.
14372 16 The schedule was not deleted because it is being used by one or more jobs.
14373 16 Supply either %s or %s to identify the schedule.
14374 16 The specified schedule name “%s” is not associated with the job “%s”.
14375 16 More than one schedule named “%s” is attached to job “%s”. Use “sp_update_schedule” to update schedules.
14376 16 More than one schedule named “%s” is attached to job “%s”. Use “sp_detach_schedule” to remove schedules from a job.
14377 16 The schedule was not attached to the specified job. The schedule owner and the job owner must be the same or the operation must be performed by a sysadmin.
14378 16 @sysadmin_only flag is no longer supported by SQLAgent and kept here only for backwards compatibility
14379 16 Table ‘%s’ foreign key ‘originating_server_id’ does not have a matching value in the referenced view ‘dbo.sysoriginatingservers_view’. 14380 16 Field ‘originating_server_id’ in table sysoriginatingservers is being referenced by either sysjobs or sysschedules.
14390 16 Only members of role sysadmin can specify the %s parameter. 14391 16 Only owner of a job or members of sysadmin role can detach a schedule.
14392 16 Only owner of a job or members of role sysadmin or
SQLAgentOperatorRole can purge history of the job.
14393 16 Only owner of a job or members of role sysadmin or
SQLAgentOperatorRole can start and stop the job.
14394 16 Only owner of a job schedule or members of sysadmin role can modify or delete the job schedule.
14395 16 ‘%s’ is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy.
14396 16 Only members of sysadmin server role can modify multi-server jobs
14397 16 Only members of sysadmin server role can start/stop multi-server jobs
14398 16 Only members of sysadmin server role can create multi-server jobs
14410 16 You must supply either a plan_name or a plan_id.
14411 16 Cannot delete this plan. The plan contains enlisted databases.
14412 16 The destination database is already part of a log shipping plan.
14413 16 This database is already log shipping.
14414 16 A log shipping monitor is already defined.
14415 16 The user name cannot be null when using SQL Server
authentication.
14416 16 This stored procedure must be run in msdb.
14417 16 Cannot delete the monitor server while databases are participating in log shipping.
14418 16 The specified @backup_file_name was not created from database ‘%s’.
14419 16 The specified @backup_file_name is not a database backup. 14420 16 The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.
14421 16 The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.
14422 16 Supply either @plan_id or @plan_name.
14423 16 Other databases are enlisted on this plan and must be removed before the plan can be deleted.
14424 16 The database ‘%s’ is already involved in log shipping. 14425 16 The database ‘%s’ does not seem to be involved in log shipping.
14426 16 A log shipping monitor is already defined. Call
sp_define_log_shipping_monitor with @delete_existing = 1.
14427 16 A user name is necessary for SQL Server security.
14428 16 Could not remove the monitor as there are still databases involved in log shipping.
14429 16 There are still secondary servers attached to this primary. 14430 16 Destination path %s is not valid. Unable to list directory contents. Specify a valid destination path.
14440 16 Could not set single user mode.
14441 16 Role change succeeded.
14442 16 Role change failed.
14450 16 The specified @backup_file_name was not taken from database ‘%s’.
14451 16 The specified @backup_file_name is not a database backup. 14500 16 Supply either a non-zero message ID, non-zero severity, non-null performance condition, or non-null WMI namespace and query. 14501 16 An alert (‘%s’) has already been defined on this condition. 14502 16 The @target_name parameter must be supplied when specifying an @enum_type of ‘TARGET’.
14503 16 The @target_name parameter should not be supplied when specifying an @enum_type of ‘ALL’ or ‘ACTUAL’.
14504 16 ‘%s’ is the fail-safe operator. You must make another operator the fail-safe operator before ‘%s’ can be dropped.
14505 16 Specify a null %s when supplying a performance condition. 14506 16 Cannot set alerts on message ID %ld.
14507 16 A performance condition must be formatted as:
‘object_name|counter_name|instance_name|comparator(> or < or =)|numeric value’.
14508 16 Specify both @wmi_namespace and @wmi_query.
14509 16 Specify a valid %s when supplying a @wmi_namespace. 14510 16 Specify a null %s when supplying a @wmi_namespace.
14511 16 The @wmi_query could not be executed in the @wmi_namespace provided. Verify that an event class selected in the query exists in the namespace and that the query has the correct syntax.
14512 16 Specify a valid %s when supplying a @wmi_query.
14513 10 Analysis query subsystem
14514 10 Analysis command subsystem
14515 16 Only a member of the sysadmin server role can add a job for a different owner with @owner_login_name.
14516 16 Proxy (%d) is not allowed for subsystem “%s” and user “%s”. Grant permission by calling sp_grant_proxy_to_subsystem or
sp_grant_login_to_proxy.
14517 16 A proxy account is not allowed for a Transact-SQL subsystem. 14518 16 Cannot delete proxy (%d). It is used by at least one jobstep. Change this proxy for all jobsteps first.
14519 16 Only one of @login_name, @fixed_server_role, or @msdb_role should be specified.
14520 16 “%s” is not a valid SQL Server standard login, Windows NT user, Windows NT group, or MSDB database role.
14521 16 “%s” is not a valid SQL Server fixed server role, Windows NT user, or Windows NT group.
14522 16 ‘”%s” is not a valid role of an MSDB database, Windows NT user, or Windows NT group.
14523 16 “%s” has not been granted permission to use proxy “%s”. 14524 16 Supply either %s or %s.
14525 16 Only members of sysadmin role are allowed to update or delete jobs owned by a different login.
14526 16 The specified category “%s” does not exist for category class “%s”.
14527 16 Job “%s” cannot be used by an alert. It should first be associated with a server by calling sp_add_jobserver.
14528 16 Job “%s” has no steps defined.
14529 16 Proxy “%s” is not a valid Windows user.
14530 16 The Transact-SQL subsystem cannot be executed under the context of a proxy account.
14531 16 Permission to access proxy already granted. Verify current permissions assignments.
14532 16 Supply both %s and %s, or none of them.
14533 16 Use either a proxy or user_domain, user_name, or
user_password parameter.
14534 16 All user_domain, user_name, and user_password parameters should be defined.
14535 16 The user_domain, user_name, and user_password parameters can be specified only for replication subsystems.
14536 16 Only members of the sysadmin role can specify a “%s” parameter.
14537 16 Execution in the context of disabled proxy (proxy_id = %d) is not allowed. Contact your system administrator.
14538 10 SSIS package execution subsystem
14539 16 Only a Standard or Enterprise edition of SQL Server can be enlisted into an MSX.
14540 16 Only a SQL Server running on Microsoft Windows NT can be enlisted into an MSX.
14541 16 The version of the MSX (%s) is not recent enough to support this TSX. Version %s or later is required at the MSX.
14542 16 It is invalid for any TSQL step of a multiserver job to have a non-null %s value.
14543 16 Login ‘%s’ owns one or more multiserver jobs. Ownership of these jobs can only be assigned to members of the %s role.
14544 16 This job is owned by ‘%s’. Only a job owned by a member of the %s role can be a multiserver job.
14545 16 The %s parameter is not valid for a job step of type ‘%s’. 14546 16 The %s parameter is not supported on Windows 95/98
platforms.
14547 10 Warning: This change will not be downloaded by the target server(s) until an %s for the job is posted using %s.
14548 10 Target server ‘%s’ does not have any jobs assigned to it. 14549 10 (Description not requested.)
14550 10 Command-Line Subsystem
14551 10 Replication Snapshot Subsystem
14552 10 Replication Transaction-Log Reader Subsystem
14553 10 Replication Distribution Subsystem
14554 10 Replication Merge Subsystem
14555 10 Active Scripting Subsystem
14556 10 Transact-SQL Subsystem
14557 10 [Internal]
14558 10 (encrypted command)
14559 10 (append output file)
14560 10 (include results in history)
14561 10 (normal)
14562 10 (quit with success)
14563 10 (quit with failure)
14564 10 (goto next step)
14565 10 (goto step)
14566 10 (idle)
14567 10 (below normal)
14568 10 (above normal)
14569 10 (time critical)
14570 10 (Job outcome)
14571 10 No description available.
14572 10 @freq_interval must be at least 1 for a daily job.
14573 10 @freq_interval must be a valid day of the week bitmask [Sunday = 1 .. Saturday = 64] for a weekly job.
14574 10 @freq_interval must be between 1 and 31 for a monthly job. 14575 10 @freq_relative_interval must be one of 1st (0x1), 2nd (0x2), 3rd [0x4], 4th (0x8) or Last (0x10).
14576 10 @freq_interval must be between 1 and 10 (1 = Sunday .. 7 = Saturday, 8 = Day, 9 = Weekday, 10 = Weekend-day) for a monthly-relative job.
14577 10 @freq_recurrence_factor must be at least 1.
14578 10 Starts whenever the CPU usage has remained below %ld percent for %ld seconds.
14579 10 Automatically starts when SQLServerAgent starts.
14580 10 job
14581 10 Replication Transaction Queue Reader Subsystem
14582 16 Only a sysadmin can specify ‘@output_file_name’ parameter for a jobstep.
14583 16 Only a sysadmin can specify ‘@database_user_name’ parameter. 14585 16 Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may reassign its ownership.
14586 16 Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may create new versions of it.
14587 16 Only the owner of DTS Package ‘%s’ or a member of the sysadmin role may drop it or any of its versions.
14588 10 ID.VersionID =
14589 10 [not specified]
14590 16 DTS Package ‘%s’ already exists with a different ID in this category.
14591 16 SSIS folder ‘%s’ already exists in the specified parent folder.
14592 16 DTS Category ‘%s’ was found in multiple parent categories. You must uniquely specify the category to be dropped.
14593 16 SSIS folder ‘%s’ contains packages and/or other folders. You must drop these first.
14594 10 DTS Package
14595 16 DTS Package ‘%s’ exists in different categories. You must uniquely specify the package.
14596 16 DTS Package ‘%s’ exists in another category.
14597 16 DTS Package ID ‘%s’ already exists with a different name. 14598 16 Cannot drop the Local, Repository, or LocalDefault DTS categories.
14599 10 Name
14600 16 Proxy “%s” has not been granted permission to use subsystem “%s”.
14601 16 Operator “%s” is not enabled and therefore cannot receive notifications.
14602 16 Operator “%s” does not have an e-mail address specified. 14603 16 Database Mail is not properly configured.
14604 16 Both %s parameters (id and name) cannot be NULL
14605 16 Both %s parameters (id and name) do not point to the same object
14606 16 %s id is not valid
14607 16 %s name is not valid
14608 16 Either %s or %s parameter needs to be supplied
14609 16 Mail database to user database association does not exist and therefore cannot be updated
14610 16 Either @profile_name or @description parameter needs to be specified for update
14611 16 Account sequence number must be supplied for update 14612 16 Each principal should have at least one default profile 14614 16 %s is not a valid mailserver_type
14615 16 The @username parameter needs to be supplied if the @password is supplied.
14616 16 Unable to retrieve the newly created credential [%s] from the credential store.
14617 16 Mail host database specified is invalid
14618 16 Parameter ‘%s’ must be specified. This parameter cannot be NULL.
14619 16 Received an error on the Service Broker conversation with Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for information. 14620 16 The Service Broker conversation to Database Mail ended without a response from Database Mail. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information.
14621 16 Parameter @attachmentencoding does not support the value “%s”. The attachment encoding must be “MIME”.
14622 16 Parameter @importance does not support the value “%s”. Mail importance must be one of LOW, NORMAL, or HIGH.
14623 16 Parameter @sensitivity does not support the value “%s”. Mail sensitivity must be one of NORMAL, PERSONAL, PRIVATE, or CONFIDENTIAL. 14624 16 At least one of the following parameters must be specified. “%s”.
14625 16 Parameter @attach_query_result_as_file cannot be 1 (true) when no value is specified for parameter @query. A query must be specified to attach the results of the query.
14626 16 Parameter @mailformat does not support the value “%s”. The mail format must be TEXT or HTML.
14627 16 Received error %d while sending a message as part of the %s operation. Database Mail may not be available, or may have encountered an error. Check the Database Mail error log for more information. 14628 16 The format of the parameter @attachments is incorrect. The file names must be separated by a semicolon “;”.
14629 16 There is no configuration parameter named “%s”, or the value provided is not of the correct data type.
14630 16 Database Mail is not permitted to send files with the file extension %s.
14631 16 The current user (‘%s’) either does not have permission to access the database specified in the parameter @execute_query_database or cannot impersonate the user specified in the parameter @execute_query_as. Only members of the sysadmin fixed server role and members of the db_owner fixed database role can impersonate another user.
14632 16 The user name %s specified in @execute_query_as is invalid. There is no user by that name.
14633 16 The database name “%s” specified in @execute_query_database is invalid. There is no database by that name.
14634 10 Warning: %s’
14635 10 Mail queued.
14636 16 No global profile is configured. Specify a profile name in the @profile_name parameter.
14637 10 Activation failure.
14638 10 Activation successful.
14639 10 The mail queue was started by login “%s”.
14640 10 The mail queue stopped by login “%s”.
14641 16 Mail not queued. Database Mail is stopped. Use
sysmail_start_sp to start Database Mail.
14642 10 Default attachment encoding
14643 10 Default dialog lifetime
14644 10 Default maximum file size
14645 10 Extensions not allowed in outgoing mails
14646 10 Number of retry attempts for a mail server
14647 10 Delay between each retry attempt to mail server
14648 10 Minimum process lifetime in seconds
14649 16 Unable to test profile. Database Mail is stopped. Use sysmail_start_sp to start Database Mail.
14650 16 Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
14651 16 Unable to test profile. Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker message delivery.
14652 16 Invalid message received on the ExternalMailQueue.
conversation_handle: %s. message_type_name: %s. message body: %s. 14653 16 Invalid %s value received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 14654 10 Unexpected message received on the ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s. 14655 16 Invalid XML message format received on the
ExternalMailQueue. conversation_handle: %s. message_type_name: %s. message body: %s.
14657 16 Mail not queued. Maximum number of mails per day (%ld) for login %s has been exceeded.
14658 16 Failed to retrieve SQLPath for syssubsystems population. 14659 16 Failed to retrieve VerSpecificRootDir for syssubsystems population.
14660 16 Database Compatibility Level is too low. Compatibility Level must be Version80 or higher.
14661 16 Query execution failed: %s
14662 10 mailitem_id on conversation %s was not found in the sysmail_send_retries table. This mail item will not be sent. 14663 10 Mail Id %d has exceeded the retry count. This mail item will not be sent.
14664 16 Database Mail logging level: normal – 1, extended – 2 (default), verbose – 3
14665 10 Mail items deletion is initiated by user “%s”. %d items deleted.
14666 16 User name cannot be supplied when using default credentials 14667 16 Mail Id %d has been deleted from sysmail_mailitems table. This mail will not be sent.
14668 16 Deleting profile % failed because there are some unsent emails associated with this profile, use force_delete option to force the deletion of the profile.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: