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

2002 16 Cannot create a procedure for replication with group number greater than one.
2003 16 Procedures with a group number cannot have parameters of xml or sqlclr user defined types. Parameter ‘%.*ls’ of procedure ‘%.*ls’ has type ‘%ls’.
2004 16 Procedure ‘%.*ls’ has already been created with group number %d. Create procedure with an unused group number.
2007 10 Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table ‘%.*ls’. The stored procedure will still be created; however, it cannot be successfully executed until the table exists.
2008 16 The object ‘%.*ls’ is not a procedure so you cannot create another procedure under that group name.
2010 16 Cannot perform alter on ‘%.*ls’ because it is an
incompatible object type.
2011 16 Index hints cannot be specified within a schema-bound object.
2013 10 Warning: ‘is_ms_shipped’ property is turned off for %S_MSG ‘%.*ls’ because you do not have permission to create or alter an object with this property.
2014 16 Remote access is not allowed from within a schema-bound object.
2101 14 Cannot %S_MSG a server level %S_MSG for user ‘%.*ls’ since there is no login corresponding to the user.
2102 16 Cannot %S_MSG %S_MSG ‘%.*ls’ since there is no user for login ‘%.*ls’ in database ‘%.*ls’.
2103 15 Cannot %S_MSG trigger ‘%.*s’ because its schema is different from the schema of the target table or view.
2104 14 Cannot %S_MSG the %S_MSG ‘%.*ls’, because you do not have permission.
2108 15 Cannot %S_MSG %S_MSG on ‘%.*ls’ as the target is not in the current database.
2110 15 Cannot alter trigger ‘%.*ls’ on ‘%.*ls’ because this trigger does not belong to this object. Specify the correct trigger name or the correct target object name.
2111 16 Cannot %S_MSG trigger ‘%.*ls’ on %S_MSG ‘%.*ls’ because an INSTEAD OF %s trigger already exists on this object.
2112 16 Cannot create trigger ‘%.*ls’ on view ‘%.*ls’ because the view is defined with CHECK OPTION.
2113 16 Cannot %S_MSG INSTEAD OF DELETE or INSTEAD OF UPDATE TRIGGER ‘%.*ls’ on table ‘%.*ls’. This is because the table has a FOREIGN KEY with cascading DELETE or UPDATE.
2114 16 Column ‘%.*ls’ cannot be used in an IF UPDATE clause because it is a computed column.
2115 16 Server level event notifications are disabled as the database MSDB does not exist.
2116 16 Cannot CREATE EVENT NOTIFICATION to database ‘%.*ls’ because it is not a valid broker database.
2201 16 %sDerivation from “anySimpleType” by restriction is not permitted.
2202 16 %sAn error has occurred while compiling the query. To obtain more detailed information about the error, the query must be run by a user with EXECUTE permissions on the xml schema collection used in the query. 2203 16 %sOnly single (optional) numeric/boolean or node*
expressions allowed as predicates, found ‘%ls’
2204 16 %sOnly (boolean ?) or (node *) expressions are allowed in conditions and with logical operators. Found “%ls”.
2205 16 %s”%ls” was expected.
2206 16 %sNamespace prefix ‘xml’ can only be associated with the URI ‘http://www.w3.org/XML/1998/namespace‘ and this URI cannot be used with other prefixes.
2207 16 %sOnly non-document nodes can be inserted. Found “%ls”. 2209 16 %sSyntax error near ‘%ls’
2210 16 %sHeterogeneous sequences are not allowed: found ‘%ls’ and ‘%ls’
2211 16 %sSingleton (or empty sequence) required, found operand of type ‘%ls’
2212 16 %sInvalid source character ‘%c’ (0x%02x) found in an identifier near ‘%ls’.
2213 16 %sCannot atomize/apply data() on expression that contains type ‘%ls’ within inferred type ‘%ls’
2214 16 %sThe type ‘%ls’ is not an atomic type
2215 16 %sThe value of attribute ‘%ls’ exceeds 4000 characters, the maximum permitted in XML schema documents
2216 16 %sInvalid XPath value in “%ls”.
2217 16 %s’%ls’ or ‘%ls’ expected
2218 16 %sThere is no attribute named ‘@%ls’
2219 16 %sThere is no attribute named ‘@%ls’ in the type ‘%ls’. 2220 16 %sThere is no attribute named ‘@%ls:%ls’
2221 16 %sThere is no attribute named ‘@%ls:%ls’ in the type ‘%ls’. 2222 16 %sInvalid source character 0x%02x found in an identifier near ‘%ls’.
2223 16 %sSyntax error near ‘%ls’, expected an identifier.
2224 16 %sAn expression was expected
2225 16 %sA string literal was expected
2226 16 %sThe target of ‘insert’ must be a single node, found ‘%ls’ 2227 16 %sThe variable ‘%ls’ was not found in the scope in which it was referenced.
2228 16 %sThe variable ‘%ls:%ls’ was not found in the scope in which it was referenced.
2229 16 %sThe name “%ls” does not denote a namespace.
2230 16 %sThe name “%ls” has already been defined.
2231 16 %sThe name “%ls” does not denote a defined type.
2232 16 %sThe name “%ls:%ls” does not denote a defined type. 2233 16 %sThe operand of “%ls” has an invalid type.
2234 16 %sThe operator “%ls” cannot be applied to “%ls” and “%ls” operands.
2235 16 %sAn argument list was applied to a non-function term. 2236 16 %sThere are not enough actual arguments in the call to function “%ls”.
2237 16 %sDerivation from anyType by extension is not supported in this release.
2238 16 %sToo many arguments in call to function ‘%ls’
2240 16 %sThe target of ‘insert into’ must be an element/document node, found ‘%ls’
2241 16 %sVariable expected: ‘$name’
2242 16 %sType specification expected.
2243 16 %sRelative path expression used without any context
2247 16 %sThe value is of type “%ls”, which is not a subtype of the expected type “%ls”.
2248 16 %sSyntax error near ‘%ls’, expected ‘as’, ‘into’, ‘before’ or ‘after’.
2249 16 %sThe target of ‘insert before/after’ must be an
element/PI/comment/text node, found ‘%ls’
2256 16 %sSyntax error near ‘%ls’, expected a “node test”.
2257 16 %sSyntax error near ‘%ls’, expected a “name test”.
2258 16 %sThe position may not be specified when inserting an attribute/document node, found ‘%ls’
2260 16 %sThere is no element named ‘%ls’
2261 16 %sThere is no element named ‘%ls’ in the type ‘%ls’. 2262 16 %sThere is no element named ‘%ls:%ls’
2263 16 %sThere is no element named “%ls:%ls” in the type “%ls”. 2264 16 %sOnly non-document nodes may be deleted, found ‘%ls’ 2266 16 %sExpected end tag ‘%ls:%ls’
2267 16 %sExpected end tag ‘%ls’
2268 16 %sEnd tag ‘/%ls:%ls’ has no matching begin tag
2269 16 %sEnd tag ‘/%ls’ has no matching begin tag
2270 16 %sDuplicate attribute ‘%ls:%ls’
2271 16 %sDuplicate attribute ‘%ls’
2272 16 %s’>’ expected
2273 16 %sUnterminated CDATA section
2274 16 %sUnterminated string constant (started on line %u)
2275 16 %sUnterminated XML declaration
2276 16 %sDerivation from ‘QName’ by restriction is not supported in this release
2277 16 %sA tag name may not contain the character ‘%c’
2278 16 %sA tag name may not start with the character ‘%c’
2279 16 %sA name/token may not start with the character ‘%c’ 2280 16 %s directive’s ‘%ls’
2329 16 %sThe string “%ls” is not a valid time duration value. 2331 16 %sRedefinition has to have itself as base type
2332 16 %s’%ls’ may not be used with an ’empty’ operand
2333 16 %sInvalid source character 0x%02x
2334 16 %sInvalid source character ‘%c’ (0x%02x)
2335 16 %sNewline in character/string constant
2336 16 %s’%c’ is not a valid octal digit (numbers starting with ‘0’ are implicitly octal)
2337 16 %sThe target of ‘replace’ must be at most one node, found ‘%ls’
2338 16 %sThe second ‘replace’ operand must contain only nodes, found ‘%ls’
2339 16 %sEither a memberType attribute or a simpleType child must be present
2340 16 %sComment started on line %u has no end
2341 16 %sExpected hex character code following ‘\x’
2342 16 %sInvalid numeric constant.
2343 16 %sUnterminated text section – missing `
2348 16 %sA namespace URI should contain at least one non-whitespace character.
2349 16 %sAttempt to redefine namespace prefix ‘%ls’
2350 16 %sInvalid XML element content
2351 16 %sExpected ‘first’ or ‘last’
2352 16 %s’of’ expected
2353 16 %s’to’ or ‘insert’ or ‘delete’ expected
2354 16 %sInvalid source character encoding
2355 16 %s’else’ expected
2356 16 %sThe target of ‘replace value of’ must be a non-metadata attribute or an element with simple typed content, found ‘%ls’ 2357 16 %sA document node may only be replaced with another document node, found ‘%ls’
2358 16 %sDerivation with both a ‘base’ attribute and an embedded type definition is not supported in this release
2359 16 %sThe target of ‘%ls’ may not be a constructed node
2360 16 %sCannot have both a ‘name’ and ‘ref’ attribute
2361 16 %sThe base type of an XSD extension or restriction type must be a simple type.
2362 16 %sXSD schema too complex
2363 16 %sXQuery too complex
2364 16 %sCannot implicitly convert from ‘%ls’ to ‘%ls’
2365 16 %sCannot explicitly convert from ‘%ls’ to ‘%ls’
2366 16 %s”%ls” has a circular definition.
2367 16 %sThe item type of an XSD list type must be a simple type. 2368 16 %sCannot have element content in a complex type with simple content.
2369 16 %sCannot have more than one group/sequence/choice/all within an restriction/extension.
2370 16 %sNo more tokens expected at the end of the XQuery
expression. Found ‘%ls’.
2371 16 %s’%ls’ can only be used within a predicate or XPath selector
2372 16 %sMetadata attribute ‘@%ls:%ls’ may not be used with ‘%ls’ 2373 16 %s%ls is not supported with constructed XML
2374 16 %sA node or set of nodes is required for %ls
2375 16 %sAggregate function ‘%ls’ expects a sequence argument 2376 16 %sOperand of a single numeric type expected
2377 16 %sResult of ‘%ls’ expression is statically ’empty’
2378 16 %sExpected XML schema document
2379 16 %sThe name specified is not a valid XML name :’%ls’
2380 16 %sMixed content is not allowed in this schema context 2382 16 Invalid combination of minOccurs and maxOccurs values, minOccurs has to be less than or equal to maxOccurs
2383 16 %sInvalid value ‘%ls’ for the %ls attribute. The value has to be between 0 and %ld.
2384 16 %sInvalid element occurrence, element ‘%ls’ was found multiple times in the context of element ‘%ls’
2385 16 Invalid target namespace specified
2386 16 %sThe value of ‘%ls’ facet is outside of the allowed range 2387 16 Cannot have both ‘type’ and ‘ref’ attributes
2388 16 %sInvalid element occurrence, element ‘%ls’ has to appear first in the context of ‘%ls’
2389 16 %s’%ls’ requires a singleton (or empty sequence), found operand of type ‘%ls’
2390 16 %sTop-level %s nodes are not supported
2391 16 %sRedefining xsd schemas is not supported
2392 16 %s’%ls::’ is not a valid axis
2393 16 %sEither an itemType attribute or a simpleType child must be present
2394 16 %sThere is no function ‘%ls()’
2395 16 %sThere is no function ‘%ls:%ls()’
2396 16 %sAttribute may not appear outside of an element
2397 16 %sIdentifiers may not contain more than %u characters 2398 16 %sDuplicate id value found: ‘%ls’
2399 16 %sAn attribute cannot have a value of type ‘%ls’, a simple type was expected
2501 16 Cannot find a table or object with the name “%.*ls”. Check the system catalog.
2502 16 DBCC MEMOBJLIST failed due to temporary inconsistency in the PMO structure. Please try again.
2503 10 Successfully deleted the physical file ‘%ls’.
2504 16 Could not delete the physical file ‘%ls’. The DeleteFile system function returned error %ls.
2505 16 The device ‘%.*ls’ does not exist. Use sys.backup_devices to show available devices.
2506 16 Could not find a table or object name ‘%.*ls’ in database ‘%.*ls’.
2507 16 The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS.
2508 16 The %.*ls count for object “%.*ls”, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE.
2509 16 DBCC CHECKCONSTRAINTS failed due to an internal query error. 2510 16 DBCC %ls error: %ls.
2511 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d.
2512 16 Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S_PGID slot %d.
2514 16 A DBCC PAGE error has occurred: %ls.
2515 16 The page %S_PGID, object ID %d, index ID %d, partition ID %I64d, allocation unit ID %I64d (type %.*ls) has been modified, but is not marked as modified in the differential backup bitmap.
2516 16 Repair has invalidated the differential bitmap for database %.*ls. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup. 2517 16 Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again. 2518 10 Object ID %ld (object “%.*ls”): Computed columns and user-defined types cannot be checked for this object because the common language runtime (CLR) is disabled.
2519 10 Computed columns and user-defined types cannot be checked for object ID %ld (object “%.*ls”) because the internal expression evaluator could not be initialized.
2520 16 Could not find database ‘%.*ls’. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists by querying the sys.databases catalog view.
2521 16 Could not find database ID %d. The database ID either does not exist, or the database was dropped before a statement tried to use it. Verify if the database ID exists by querying the sys.databases catalog view. 2522 16 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid.
2523 16 Filegroup %.*ls is invalid.
2524 16 Cannot process object ID %ld (object “%.*ls”) because it is a Service Broker queue. Try the operation again with the object ID of the corresponding internal table for the queue, found in sys.internal_tables. 2525 16 Database file %.*ls is offline.
2526 16 Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.
2527 16 Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline.
2528 10 DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2529 16 Filegroup %.*ls is offline.
2530 16 The index “%.*ls” on table “%.*ls” is disabled.
2531 16 Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID.
2532 16 One or more WITH options specified are not valid for this command.
2533 16 Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
2534 16 Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), is allocated by another object.
2536 10 DBCC results for ‘%.*ls’.
2537 16 Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%hs) failed. The values are %ld and %ld.
2538 10 File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.
2539 10 The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.
2540 10 The system cannot self repair this error.
2541 10 DBCC UPDATEUSAGE: counts updated for table ‘%.*ls’ (index ‘%.*ls’, partition %ld):
2542 10 DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.
2543 10 USED pages %.*ls: changed from (%I64d) to (%I64d) pages.
2544 10 RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.
2545 10 ROWS count: Changed from (%I64d) to (%I64d) rows. 2546 10 Index ‘%.*ls’ on table ‘%.*ls’ is marked as disabled. Rebuild the index to bring it online.
2547 16 Unable to process object ID %ld (object “%.*ls”) because it is a synonym. If the object referenced by the synonym is a table or view, retry the operation using the base object that the synonym references. 2548 10 DBCC: Compaction phase of index ‘%.*ls’ is %d%% complete. 2549 10 DBCC: Defrag phase of index ‘%.*ls’ is %d%% complete. 2550 16 The index “%.*ls” (partition %ld) on table “%.*ls” cannot be reorganized because it is being reorganized by another process. 2551 16 The indexes on table “%.*ls” cannot be reorganized because there is already an online index build or rebuild in progress on the table. 2552 16 The index “%.*ls” (partition %ld) on table “%.*ls” cannot be reorganized because page level locking is disabled.
2553 10 Index ‘%.*ls’ (Partition %ld) on table ‘%.*ls’ will not be available during index reorganization. This is because page-level locking is disabled and the entire index is exclusively locked.
2554 16 The index “%.*ls” (partition %ld) on table “%.*ls” cannot be reorganized because the filegroup is read-only.
2555 16 Cannot move all contents of file “%.*ls” to other places to complete the emptyfile operation.
2556 16 There is insufficient space in the filegroup to complete the emptyfile operation.
2557 14 User ‘%.*ls’ does not have permission to run DBCC %ls for object ‘%.*ls’.
2558 16 %I64d incorrect counts were detected in database ‘%.*ls’. 2559 16 The ‘%ls’ and ‘%ls’ options are not allowed on the same statement.
2560 16 Parameter %d is incorrect for this DBCC statement.
2561 16 Parameter %d is incorrect for this statement.
2566 14 DBCC DBREINDEX cannot be used on system tables.
2567 14 DBCC INDEXDEFRAG cannot be used on system table indexes 2568 16 Page %S_PGID is out of range for this database or is in a log file.
2570 16 Page %S_PGID, slot %d in object ID %d, index ID %d,
partition ID %I64d, alloc unit ID %I64d (type “%.*ls”). Column “%.*ls” value is out of range for data type “%.*ls”. Update column to a legal value. 2571 14 User ‘%.*ls’ does not have permission to run DBCC %.*ls. 2572 16 DBCC cannot free DLL ‘%.*ls’. The DLL is in use.
2573 16 Could not find table or object ID %.*ls. Check system catalog.
2574 16 Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree.
2575 16 The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.
2576 16 The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.
2577 16 Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d.
2579 16 Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database.
2580 16 Table ‘%.*ls’ is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table. 2581 10 DBCC cannot free the DLL “%.*ls”. The DLL is not loaded. 2583 16 An incorrect number of parameters was given to the DBCC statement.
2585 16 Cannot find partition number %ld for table “%.*ls”.
2586 16 Cannot find partition number %ld for index “%.*ls”, table “%.*ls”.
2587 16 The invalid partition number %ld was specified.
2588 16 Cannot find partition number %ld for index ID %d, object ID %d.
2589 16 Repair could not fix all errors on the first attempt. 2590 10 User “%.*ls” is modifying bytes %d to %d of page %S_PGID in database “%.*ls”.
2591 16 Cannot find a row in the system catalog with the index ID %d for table “%.*ls”.
2592 10 Repair: The %ls index successfully rebuilt for the object “%.*ls” in database “%.*ls”.
2593 10 There are %I64d rows in %I64d pages for object “%.*ls”. 2594 10 Cannot process rowset ID %I64d of object “%.*ls” (ID %d), index “%.*ls” (ID %d), because it resides on filegroup “%.*ls” (ID %d), which was not checked.
2596 16 The repair statement was not processed. The database cannot be in read-only mode.
2599 16 Cannot switch to in row text in table “%.*ls”.
2601 14 Cannot insert duplicate key row in object ‘%.*ls’ with unique index ‘%.*ls’.
2627 14 Violation of %ls constraint ‘%.*ls’. Cannot insert duplicate key in object ‘%.*ls’.
2701 10 Database name ‘%.*ls’ ignored, referencing object in tempdb. 2702 16 Database ‘%.*ls’ does not exist.
2703 16 Cannot use duplicate column names in the partition columns list. Column name ‘%.*ls’ appears more than once.
2704 16 Invalid partition scheme ‘%.*ls’ specified.
2705 16 Column names in each table must be unique. Column name ‘%.*ls’ in table ‘%.*ls’ is specified more than once.
2706 11 Table ‘%.*ls’ does not exist.
2707 16 Column ‘%.*ls’ in %S_MSG ‘%.*ls’ cannot be used in an index or statistics or as a partition key because it depends on a non-schemabound object.
2709 16 Column ‘%.*ls’ in %S_MSG ‘%.*ls’ cannot be used in an index or statistics or as a partition key because it does user or system data access.
2710 16 You are not the owner specified for the object ‘%.*ls’ in this statement (CREATE, ALTER, TRUNCATE, UPDATE STATISTICS or BULK INSERT). 2711 16 The definition of object “%.*ls” in the resource database contains the non-ASCII character “%.*ls”.
2714 16 There is already an object named ‘%.*ls’ in the database. 2715 16 Column, parameter, or variable #%d: Cannot find data type %.*ls.
2716 16 Column, parameter, or variable #%d: Cannot specify a column width on data type %.*ls.
2717 15 The size (%d) given to the %S_MSG ‘%.*ls’ exceeds the maximum allowed (%d).
2719 16 Upgrade of database “%.*ls” failed because it contains a user named “sys” which is a reserved user or schema name in this version of SQL Server.
2720 16 Cannot schema bind %S_MSG ‘%.*ls’ because it references system object ‘%.*ls’.
2722 16 Xml data type methods are not allowed in expressions in this context.
2724 10 Parameter or variable ‘%.*ls’ has an invalid data type. 2725 16 Online index operation cannot be performed for index ‘%.*ls’ because the index contains column ‘%.*ls’ of data type text, ntext, image, varchar(max), nvarchar(max), varbinary(max) or xml. For non-clustered index the column could be an include column of the index, for clustered index it could be any column of the table. In case of drop_existing the column could be part of new or old index. The operation must be performed offline. 2726 16 Partition function ‘%.*ls’ uses %d columns which does not match with the number of partition columns used to partition the table or index.
2727 11 Cannot find index ‘%.*ls’.
2728 16 Cannot partition on more than %d columns.
2729 16 Column ‘%.*ls’ in %S_MSG ‘%.*ls’ cannot be used in an index or statistics or as a partition key because it is non-deterministic. 2730 11 Cannot create procedure ‘%.*ls’ with a group number of %d because a procedure with the same name and a group number of 1 does not currently exist in the database. Must execute CREATE PROCEDURE ‘%.*ls’;1 first.
2731 16 Column ‘%.*ls’ has invalid width: %d.
2732 16 Error number %ld is invalid. The number must be from %ld through %ld and it cannot be 50000.
2733 16 The %ls data type is invalid for return values.
2735 16 Cannot create primary xml index ‘%.*ls’ on ‘%.*ls’ because PRIMARY KEY constraint contains column(s) of type timestamp. 2738 16 A table can only have one timestamp column. Because table ‘%.*ls’ already has one, the column ‘%.*ls’ cannot be added. 2739 16 The text, ntext, and image data types are invalid for local variables.
2740 16 SET LANGUAGE failed because ‘%.*ls’ is not an official language name or a language alias on this SQL Server.
2741 16 SET DATEFORMAT date order ‘%.*ls’ is invalid.
2742 16 SET DATEFIRST %d is out of range.
2743 16 %ls statement requires %S_MSG parameter.
2744 16 Multiple identity columns specified for table ‘%.*ls’. Only one identity column per table is allowed.
2745 10 Process ID %d has raised user error %d, severity %d. SQL Server is terminating this process.
2747 16 Too many substitution parameters for RAISERROR. Cannot exceed %d substitution parameters.
2748 16 Cannot specify %ls data type (parameter %d) as a
substitution parameter.
2749 16 Identity column ‘%.*ls’ must be of data type int, bigint, smallint, tinyint, or decimal or numeric with a scale of 0, and constrained to be nonnullable.
2750 16 Column or parameter #%d: Specified column precision %d is greater than the maximum precision of %d.
2751 16 Column or parameter #%d: Specified column scale %d is greater than the specified precision of %d.
2752 16 Identity column ‘%.*ls’ contains invalid SEED.
2753 16 Identity column ‘%.*ls’ contains invalid INCREMENT.
2754 16 Error severity levels greater than %d can only be specified by members of the sysadmin role, using the WITH LOG option.
2755 16 SET DEADLOCK_PRIORITY option is invalid. Valid options are {HIGH | NORMAL | LOW | [%d … %d] of type integer}.
2756 16 Invalid value %d for state. Valid range is from %d to %d. 2759 16 CREATE SCHEMA failed due to previous errors.
2760 16 The specified schema name “%.*ls” either does not exist or you do not have permission to use it.
2761 16 The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.
2762 16 sp_setapprole was not invoked correctly. Refer to the documentation for more information.
2766 16 The definition for user-defined data type ‘%.*ls’ has changed.
2767 15 Could not locate statistics ‘%.*ls’ in the system catalogs. 2770 16 The SELECT INTO statement cannot have same source and destination tables.
2772 16 Cannot access temporary tables from within a function. 2773 16 The collation ID is corrupted because the sort order ID %d is not valid.
2774 16 Collation ID %d is invalid.
2775 16 The code page %d is not supported by the server.
2778 16 Only System Administrator can specify %s option for %s command.
2779 16 The %S_MSG ‘%.*ls’ is an auto-drop system object. It cannot be used in queries or DDL.
2780 16 View ‘%.*ls’ is not schemabound.
2782 16 Cannot create table “%.*ls”: A table must have a clustered primary key in order to have xml data type columns.
2785 16 User-defined functions are not allowed in expressions in this context.
2786 16 The data type of substitution parameter %d does not match the expected type of the format specification.
2787 16 Invalid format specification: ‘%.*ls’.
2788 16 Synonyms are invalid in a schemabound object or a constraint expression.
2789 16 Must specify a two-part name for %S_MSG ‘%.*ls’ in a schemabound object or a constraint expression.
2790 16 Cannot use a column of type TEXT, NTEXT, or IMAGE in a constraint expression.
2791 16 Could not resolve expression for schemabound object or constraint.
2792 16 Cannot specify a sql user defined type in a Schema-bound object or a constraint expression.
2793 16 Specified owner name ‘%.*ls’ either does not exist or you do not have permission to act on its behalf.
2794 16 Message text expects more than the maximum number of arguments (%d).
2795 16 Could not %S_MSG clustered index because the new %S_MSG ‘%.*ls’ does not match the filestream %S_MSG ‘%.*ls’ of the table. 2796 16 Cannot specify database name with $partition in a
Schema-bound object, computed column or constraint expression. 2797 16 The default schema does not exist.
2798 16 Cannot create index or statistics ‘%.*ls’ on table ‘%.*ls’ because SQL Server cannot verify that key column ‘%.*ls’ is precise and deterministic. Consider removing column from index or statistics key, marking computed column persisted, or using non-CLR-derived column in key. 2799 16 Cannot create index or statistics ‘%.*ls’ on table ‘%.*ls’ because the computed column ‘%.*ls’ is imprecise and not persisted. Consider removing column from index or statistics key or marking computed column persisted.
2801 16 The definition of object ‘%.*ls’ has changed since it was compiled.
2802 10 SQL Server has encountered %d occurrence(s) of cachestore flush for the ‘%s’ cachestore (part of plan cache) due to ‘DBCC FREEPROCCACHE’ or ‘DBCC FREESYSTEMCACHE’ operations.
2803 10 SQL Server has encountered %d occurrence(s) of cachestore flush for the ‘%s’ cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2809 18 The request for %S_MSG ‘%.*ls’ failed because ‘%.*ls’ is a %S_MSG object.
2812 16 Could not find stored procedure ‘%.*ls’.
2813 16 “%.*ls” is not supported on this edition of SQL Server. 2814 10 A possible infinite recompile was detected for SQLHANDLE %hs, PlanHandle %hs, starting offset %d, ending offset %d. The last recompile reason was %d.
3002 16 Cannot BACKUP or RESTORE a database snapshot.
3003 10 This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before attempting to restore this differential backup.
3004 16 The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
3005 10 The differential partial backup is including a read-only filegroup, ‘%ls’. This filegroup was read-write when the base partial backup was created, but was later changed to read-only access. We recommend that you create a separate file backup of the ‘%ls’ filegroup now, and then create a new partial backup to provide a new base for later differential partial backups.
3006 16 The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups are not allowed in the simple recovery model, and are never allowed for partial differential backups.
3007 16 The backup of the file or filegroup “%ls” is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. 3008 16 The specified device type is not supported for backup mirroring.
3009 16 Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
3010 16 Invalid backup mirror specification. All mirrors must have the same number of members.
3011 16 All backup devices must be of the same general class (for example, DISK and TAPE).
3012 17 VDI ran out of buffer when SQL server attempted to send differential information to SQL Writer.
3013 16 %hs is terminating abnormally.
3014 10 %hs successfully processed %d pages in %d.%03d seconds (%d.%03d MB/sec).
3015 10 %hs is not yet implemented.
3016 16 Backup of file ‘%ls’ is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taking the backup, or restrict the backup to exclude this file. 3017 16 The restart-checkpoint file ‘%ls’ could not be opened. Operating system error ‘%ls’. Correct the problem, or reissue the command without RESTART.
3018 10 The restart-checkpoint file ‘%ls’ was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
3019 16 The restart-checkpoint file ‘%ls’ is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The restart command must use the same syntax as the interrupted command, with the addition of the RESTART clause. Alternatively, reissue the current statement without the RESTART clause.
3021 16 Cannot perform a backup or restore operation within a transaction.
3022 10 This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate if you plan to set the filegroup to read-only followed by a differential file backup. Consult Books Online for more information on managing read-only data for the simple recovery model. In particular, consider how partial backups are used.
3023 16 Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed. 3024 16 You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
3025 16 Missing database name. Reissue the statement specifying a valid database name.
3027 16 The filegroup “%.*ls” is not part of database “%.*ls”. 3028 10 The restart-checkpoint file ‘%ls’ was corrupt and is being ignored. The RESTORE command will continue from the beginning as if RESTART had not been specified.
3031 16 Option ‘%ls’ conflicts with option(s) ‘%ls’. Remove the conflicting option and reissue the statement.
3032 16 One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options.
3033 16 BACKUP DATABASE cannot be used on a database opened in emergency mode.
3034 16 No files were selected to be processed. You may have selected one or more filegroups that have no members.
3035 16 Cannot perform a differential backup for database “%ls”, because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. 3036 16 The database “%ls” is in warm-standby state (set by
executing RESTORE WITH STANDBY) and cannot be backed up until the entire restore sequence is completed.
3038 16 The file name “%ls” is invalid as a backup device name. Reissue the BACKUP statement with a valid file name.
3039 16 Cannot perform a differential backup for file ‘%ls’ because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option.
3040 10 An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected.
3041 16 BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages.
3042 10 BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the errors that were encountered.
3043 16 BACKUP ‘%ls’ detected an error on page (%d:%d) in file ‘%ls’.
3044 16 Invalid zero-length device name. Reissue the BACKUP
statement with a valid device name.
3045 16 Differential BACKUP or RESTORE is not supported on the FAT file system. The path “%.*ls” is not usable.
3046 16 Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
3047 16 The BackupDirectory registry key is not configured
correctly. This key should specify the root path where disk backup files are stored when full path names are not provided. This path is also used to locate restart checkpoint files for RESTORE.
3048 16 BACKUP LOG WITH TRUNCATE_ONLY cannot operate on database ‘%ls’ because it is configured for database mirroring.
3049 16 BACKUP detected corruption in the database log. Check the errorlog for more information.
3050 16 SQL Server could not send the differential information for database file ‘%ls’ of database ‘%ls\%ls’ to the backup application because the differential information is too large to fit in memory, and an attempt to use a temporary file has failed.
3051 16 BACKUP LOG was unable to maintain mirroring consistency for database ‘%ls’. Database mirroring has been permanently suspended. To resume mirroring, the existing mirroring configuration must be dropped and then re-established.
3054 16 Differential file backups can include only read-only data for databases using the simple recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
3101 16 Exclusive access could not be obtained because the database is in use.
3102 16 %ls cannot process database ‘%ls’ because it is in use by this session. It is recommended that the master database be used when performing this operation.
3103 16 A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTORE statement and provide a backup set which includes a full copy of at least the primary data file. The WITH PARTIAL clause of the RESTORE statement may not be used for any other purpose.
3104 16 RESTORE cannot operate on database ‘%ls’ because it is configured for database mirroring. Use ALTER DATABASE to remove mirroring if you intend to restore the database.
3105 16 RESTORE cannot restore any more pages into file ‘%ls’ because the maximum number of pages (%d) are already being restored. Either complete the restore sequence for the existing pages, or use RESTORE FILE to restore all pages in the file.
3106 16 The filegroup “%ls” is ambiguous. The identity in the backup set does not match the filegroup that is currently defined in the online database. To force the use of the filegroup in the backup set, take the database offline and then reissue the RESTORE command.
3107 16 The file “%ls” is ambiguous. The identity in the backup set does not match the file that is currently defined in the online database. To force the use of the file in the backup set, take the database offline and then reissue the RESTORE command.
3108 16 To restore the master database, the server must be running in single-user mode. For information on starting in single-user mode, see “How to: Start an Instance of SQL Server (sqlservr.exe)” in Books Online. 3109 16 Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not supported.
3110 14 User does not have permission to RESTORE database ‘%.*ls’. 3111 16 Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored. 3112 16 Cannot restore any database other than master when the server is in single user mode.
3115 16 The database is using the simple recovery model. It is not possible to restore a subset of the read-write data.
3116 16 The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore. 3117 16 The log or differential backup cannot be restored because no files are ready to rollforward.
3118 16 The database “%ls” does not exist. RESTORE can only create a database when restoring either a full backup or a file backup of the primary file.
3119 16 Problems were identified while planning for the RESTORE statement. Previous messages provide details.
3120 16 This backup set will not be restored because all data has already been restored to a point beyond the time covered by this backup set. 3121 16 The file “%ls” is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue. 3122 16 File initialization failed. RESTORE cannot continue. 3123 16 Invalid database name ‘%.*ls’ specified for backup or restore operation.
3125 16 The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the database. Restoring more data is required before recovery is possible. Either restore a full file backup taken since the data was marked read-only, or restore the most recent base backup for the target data followed by a differential file backup.
3126 16 Point-in-time recovery is not supported by this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
3127 16 The file ‘%ls’ of restored database ‘%ls’ is being left in the defunct state because the database is using the simple recovery model and the file is marked for read-write access. Therefore, only read-only files can be recovered by piecemeal restore.
3128 16 File ‘%ls’ has an unsupported page size (%d).
3129 16 The contents of the file “%ls” are not consistent with a transition into the restore sequence. A restore from a backup set may be required.
3130 10 The filegroup “%ls” is selected. At the time of backup it was known by the name “%ls”‘. RESTORE will continue operating upon the renamed filegroup.
3131 10 The file “%ls” is selected. At the time of backup it was known by the name “%ls”. RESTORE will continue operating upon the renamed file.
3132 16 The media set has %d media families but only %d are
provided. All members must be provided.
3133 16 The volume on device “%ls” is sequence number %d of media family %d, but sequence number %d of media family %d is expected. Check that the device specifications and loaded media are correct.
3134 10 The differential base attribute for file ‘%ls’ of database ‘%ls’ has been reset because the file has been restored from a backup taken on a conflicting recovery path. The restore was allowed because the file was read-only and was consistent with the current status of the database. Any future differential backup of this file will require a new differential base.
3135 16 The backup set in file ‘%ls’ was created by %hs and cannot be used for this restore operation.
3136 16 This differential backup cannot be restored because the database has not been restored to the correct earlier state. 3137 16 Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files.
3138 16 The database cannot be reverted because FileStreams are present.
3139 16 Restore to snapshot is not allowed with the master database. 3140 16 Could not adjust the space allocation for file ‘%ls’. 3141 16 The database to be restored was named ‘%ls’. Reissue the statement using the WITH REPLACE option to overwrite the ‘%ls’ database. 3142 16 File “%ls” cannot be restored over the existing “%ls”. Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location.
3143 16 The data set on device ‘%ls’ is not a SQL Server backup set. 3144 16 File ‘%.*ls’ was not backed up in file %d on device ‘%ls’. The file cannot be restored from this backup set.
3145 16 The STOPAT option is not supported for databases that use the SIMPLE recovery model.
3147 16 Backup and restore operations are not allowed on database tempdb.
3148 16 This RESTORE statement is invalid in the current context. The ‘Recover Data Only’ option is only defined for secondary filegroups when the database is in an online state. When the database is in an offline state filegroups cannot be specified.
3149 16 The file or filegroup “%ls” is not in a valid state for the “Recover Data Only” option to be used. Only secondary files in the OFFLINE or RECOVERY_PENDING state can be processed.
3150 10 The master database has been successfully restored. Shutting down SQL Server.
3151 21 Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online. 3153 16 The database is already fully recovered.
3154 16 The backup set holds a backup of a database other than the existing ‘%ls’ database.
3155 16 The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created.
3156 16 File ‘%ls’ cannot be restored to ‘%ls’. Use WITH MOVE to identify a valid location for the file.
3159 16 The tail of the log for the database “%ls” has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log. 3161 16 The primary file is unavailable. It must be restored or otherwise made available.
3163 16 The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.
3165 16 Database ‘%ls’ was restored, however an error was
encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online. 3166 16 RESTORE DATABASE could not drop database ‘%ls’. Drop the database and then reissue the RESTORE DATABASE statement.
3167 16 RESTORE could not start database ‘%ls’.
3168 16 The backup of the system database on the device %ls cannot be restored because it was created by a different version of the server (%ls) than this server (%ls).
3169 16 The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
3170 16 The STANDBY filename is invalid.
3171 16 File %ls is defunct and cannot be restored into the online database.
3172 16 Filegroup %ls is defunct and cannot be restored into the online database.
3173 16 The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed up to reach the target point in time. The tail of the log for the database “%ls” has not been backed up. Use BACKUP LOG WITH NORECOVERY to back up the log, or use the WITH REPLACE clause in your RESTORE statement to overwrite the tail of the log.
3174 16 The file ‘%ls’ cannot be moved by this RESTORE operation. 3175 10 RESTORE FILEGROUP=”%ls” was specified, but not all of its files are present in the backup set. File “%ls” is missing. RESTORE will continue, but if you want all files to be restored, you must restore other backup sets.
3176 16 File ‘%ls’ is claimed by ‘%ls'(%d) and ‘%ls'(%d). The WITH MOVE clause can be used to relocate one or more files.
3178 16 File %ls is not in the correct state to have this
differential backup applied to it.
3179 16 The system database cannot be moved by RESTORE.
3180 16 This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY. 3181 10 Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.
3182 16 The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR.
3183 16 RESTORE detected an error on page (%d:%d) in database “%ls” as read from the backup set.
3184 10 RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible. 3185 16 RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage.
3186 16 The backup set has been damaged. RESTORE will not attempt to apply this backup set.
3187 16 RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
3188 10 The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.
3189 16 Damage to the backup set was detected.
3190 16 Filegroup ‘%ls’ cannot be restored because it does not exist in the backup set.
3191 16 Restore cannot continue because file ‘%ls’ cannot be written. Ensure that all files in the database are writable. 3192 10 Restore was successful but deferred transactions remain. These transactions can not be resolved because there are data that is unavailable. Either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
3194 16 Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored.
3195 16 Page %S_PGID cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first log or differential backup taken since the file was added to the database. 3196 16 RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file.
3197 10 I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup. 3198 10 I/O was resumed on database %ls. No user action is required. 3199 16 RESTORE requires MAXTRANSFERSIZE=%u but %u was specified. 3201 16 Cannot open backup device ‘%ls’. Operating system error %ls. 3202 16 Write on “%ls” failed: %ls
3203 16 Read on “%ls” failed: %ls
3204 16 The backup or restore was aborted.
3205 16 Too many backup devices specified for backup or restore; only %d are allowed.
3206 16 The backup device ‘%.*ls’ was not found in
sys.backup_devices. To add this backup device, you can use the sp_addumpdevice stored procedure.
3207 16 Backup or restore requires at least one backup device. Rerun your statement specifying a backup device.
3208 16 Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error log for more details.
3209 16 Operation is not supported on user instances.
3210 16 The mirror member in drive “%ls” is inconsistent with the mirror member in drive “%ls”.
3211 10 %d percent processed.
3212 16 The mirror device “%ls” and the mirror device “%ls” have different device specifications.
3213 16 Unable to unload one or more tapes. See the error log for details.
3214 16 Too many backup mirrors are specified. Only %d are allowed. 3215 16 Use WITH FORMAT to create a new mirrored backup set. 3216 16 RESTORE REWINDONLY is only applicable to tape devices. 3217 16 Invalid value specified for %ls parameter.
3218 16 Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
3219 16 The file or filegroup “%.*ls” cannot be selected for this operation.
3221 16 The ReadFileEx system function executed on file ‘%ls’ only read %d bytes, expected %d.
3222 16 The WriteFileEx system function executed on file ‘%ls’ only wrote %d bytes, expected %d.
3224 16 Cannot create worker thread.
3227 16 The backup media on “%ls” is part of media family %d which has already been processed on “%ls”. Ensure that backup devices are correctly specified. For tape devices, ensure that the correct volumes are loaded.
3229 16 Request for device ‘%ls’ timed out.
3230 16 Operation on device ‘%ls’ exceeded retry count.
3231 16 The media loaded on “%ls” is formatted to support %d media families, but %d media families are expected according to the backup device specification.
3232 16 The volume mounted on “%ls” does not have the expected backup set identity. The volume may be obsolete due to a more recent overwrite of this media family. In that case, locate the correct volume with sequence number %d of media family %d.
3234 16 Logical file ‘%.*ls’ is not part of database ‘%ls’. Use RESTORE FILELISTONLY to list the logical file names.
3235 16 The file “%.*ls” is not part of database “%ls”. You can only list files that are members of this database.
3239 16 The backup set on device ‘%ls’ uses a feature of the Microsoft Tape Format not supported by SQL Server.
3240 16 Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set. 3241 16 The media family on device ‘%ls’ is incorrectly formed. SQL Server cannot process this media family.
3242 16 The file on device ‘%ls’ is not a valid Microsoft Tape Format backup set.
3243 16 The media family on device ‘%ls’ was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d. 3244 16 Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation.
3245 16 Could not convert a string to or from Unicode, %ls.
3246 16 The media family on device ‘%ls’ is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media. 3247 16 The volume on device ‘%ls’ has the wrong media sequence number (%d). Remove it and insert volume %d.
3249 16 The volume on device ‘%ls’ is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set.
3250 16 The value ‘%d’ is not within range for the %ls parameter. 3251 10 The media family on device ‘%ls’ is complete. The device is now being reused for one of the remaining families.
3253 16 The block size parameter must supply a value that is a power of 2.
3254 16 The volume on device ‘%ls’ is empty.
3255 16 The data set on device ‘%ls’ is a SQL Server backup set not compatible with this version of SQL Server.
3256 16 The backup set on device ‘%ls’ was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally. 3257 16 There is insufficient free space on disk volume ‘%ls’ to create the database. The database requires %I64u additional free bytes, while only %I64u bytes are available.
3258 16 The volume on the device “%ls” is not part of the media set that is currently being processed. Ensure that the backup devices are loaded with the correct media.
3259 16 The volume on device ‘%ls’ is not part of a multiple family media set. BACKUP WITH FORMAT can be used to form a new media set. 3260 16 An internal buffer has become full.
3261 16 SQL Server cannot use the virtual device configuration. 3262 10 The backup set on file %d is valid.
3263 16 Cannot use the volume on device ‘%ls’ as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, or sequence number %d of family %d for the current set. 3264 16 The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
3265 16 The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. 3266 16 The backup data at the end of “%ls” is incorrectly
formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on the media, use RESTORE HEADERONLY. To determine the usability of the backup sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reformat the media using BACKUP WITH FORMAT, which destroys all the backup sets.
3267 16 Insufficient resources to create UMS scheduler.
3268 16 Cannot use the backup file ‘%ls’ because it was originally formatted with sector size %d and is now on a device with sector size %d. 3269 16 Cannot restore the file ‘%ls’ because it was originally written with sector size %d; ‘%ls’ is now on a device with sector size %d. 3270 16 An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance. 3271 16 A nonrecoverable I/O error occurred on file “%ls:” %ls. 3272 16 The ‘%ls’ device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement using a compatible block size.
3273 16 The BUFFERCOUNT parameter must supply a value that allows at least one buffer per backup device.
3276 16 WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.
3277 16 WITH SNAPSHOT must be used with only one virtual device. 3278 16 Failed to encrypt string %ls
3279 16 Access is denied due to a password failure
3280 16 Backups on raw devices are not supported. ‘%ls’ is a raw device.
3281 10 Released and initiated rewind on ‘%ls’.
3283 16 The file “%ls” failed to initialize correctly. Examine the error logs for more details.
3301 21 The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database.
3313 21 During redoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
3314 21 During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
3315 21 During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database ‘%.*ls’ under transaction %S_XID. Restore a backup of the database, or repair the database.
3316 21 During undo of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a full backup, or repair the database.
3401 10 Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery.
3402 10 The database ‘%ls’ is marked %ls and is in a state that does not allow recovery to be run.
3403 10 Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
3404 10 Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
3406 10 %d transactions rolled forward in database ‘%.*ls’ (%d). This is an informational message only. No user action is required. 3407 10 %d transactions rolled back in database ‘%.*ls’ (%d). This is an informational message only. No user action is required. 3408 10 Recovery is complete. This is an informational message only. No user action is required.
3409 16 Performance counter shared memory setup failed with error %d. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
3410 10 Data in filegroup %s is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup if you never intend to recover it. Log truncation cannot occur until this condition is resolved.
3411 21 Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall. 3412 10 Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
3413 21 Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems. 3414 10 An error occurred during recovery, preventing the database ‘%.*ls’ (database ID %d) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
3415 16 Database ‘%.*ls’ cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
3416 16 The server contains read-only files that must be made writable before the server can be recollated.
3417 21 Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
3418 10 Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain.
3419 16 Recovery for database ‘%.*ls’ is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence.
3420 21 Database snapshot ‘%ls’ has failed an IO operation and is marked suspect. It must be dropped and recreated.
3429 10 Recovery could not determine the outcome of a cross-database transaction %S_XID, named ‘%.*ls’, in database ‘%.*ls’ (database ID %d). The coordinating database (database ID %d) was unavailable. The transaction was assumed to be committed. If the transaction was not committed, you can retry recovery when the coordinating database is available.
3431 21 Could not recover database ‘%.*ls’ (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS DTC, restore from a full backup, or repair the database.
3434 20 Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation.
3437 21 An error occurred while recovering database ‘%.*ls’. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again.
3441 21 During startup of warm standby database ‘%.*ls’ (database ID %d), its standby file (‘%ls’) was inaccessible to the RESTORE statement. The operating system error was ‘%ls’. Diagnose the operating system error, correct the problem, and retry startup.
3442 21 Recovery of warm standby database ‘%.*ls’ (database ID %d) failed. There is insufficient room in the undo file. Increase the size of the undo file and retry recovery.
3443 21 Database ‘%.*ls’ (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.
3445 21 File ‘%ls’ is not a valid undo file for database ‘%.*ls (database ID %d). Verify the file path, and specify the correct file. 3446 16 Primary log file is not available for database ‘%.*ls’. The log cannot be backed up.
3447 16 Could not activate or scan all of the log files for database ‘%.*ls’.
3448 21 Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%.*ls’ (database ID %d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. Restore or repair the database.
3449 21 SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database. 3450 10 Recovery of database ‘%.*ls’ (%d) is %d%% complete
(approximately %d seconds remain). Phase %d of 3. This is an informational message only. No user action is required.
3452 10 Recovery of database ‘%.*ls’ (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT (‘%.*ls’). 3453 16 This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible. 3454 10 Recovery is writing a checkpoint in database ‘%.*ls’ (%d). This is an informational message only. No user action is required. 3455 10 Analysis of database ‘%.*ls’ (%d) is %d%% complete
(approximately %d seconds remain). This is an informational message only. No user action is required.
3456 21 Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%.*ls’ (database ID %d). Page: LSN = %S_LSN, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore from a backup of the database, or repair the database.
3457 21 Transactional file system resource manager ‘%.*ls’ failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.
3458 16 Recovery cannot scan database “%.*ls” for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up.
3505 14 Only the owner of database “%.*ls” or someone with relevant permissions can run the CHECKPOINT statement.
3604 10 Duplicate key was ignored.
3606 10 Arithmetic overflow occurred.
3607 10 Division by zero occurred.
3608 16 Cannot allocate a GUID for the token.
3609 16 The transaction ended in the trigger. The batch has been aborted.
3612 10 %hsSQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms.
3613 10 SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms.
3615 10 Table ‘%.*ls’. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob read-ahead reads %d.
3616 16 Transaction doomed in trigger. Batch has been aborted. 3619 10 Could not write a checkpoint record in database ID %d because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files. 3620 10 Automatic checkpointing is disabled in database ‘%.*ls’ because the log is out of space. Automatic checkpointing will be enabled when the database owner successfully checkpoints the database. Contact the database owner to either truncate the log file or add more disk space to the log. Then retry the CHECKPOINT statement.
3621 10 The statement has been terminated.
3622 10 Warning: A domain error occurred.
3623 16 A domain error occurred.
3624 20 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 3625 20 ‘%hs’ is not yet implemented.
3627 17 New parallel operation cannot be started due to too many parallel operations executing at this time. Use the “max worker threads” configuration option to increase the number of allowable threads, or reduce the number of parallel operations running on the system.
3628 24 The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator. 3633 16 The operating system returned the error ‘%ls’ while
attempting ‘%ls’ on ‘%ls’ at ‘%hs'(%d).
3634 16 The operating system returned the error ‘%ls’ while
attempting ‘%ls’ on ‘%ls’.
3635 16 An error occurred while processing ‘%ls’ metadata for database id %d, file id %d, and transaction=’%.*ls’. Additional Context=’%ls’. Location=’%hs'(%d). Retry the operation; if the problem persists, contact the database administrator to review locking and memory configurations. Review the application for possible deadlock conflicts. 3636 16 An error occurred while processing ‘%ls’ metadata for database id %d file id %d.
3637 16 A parallel operation cannot be started from a DAC
connection.
3701 11 Cannot %S_MSG the %S_MSG ‘%.*ls’, because it does not exist or you do not have permission.
3702 16 Cannot drop database “%.*ls” because it is currently in use. 3703 16 Cannot detach the %S_MSG ‘%.*ls’ because it is currently in use.
3705 16 Cannot use DROP %ls with ‘%.*ls’ because ‘%.*ls’ is a %S_MSG. Use DROP %ls.
3706 16 Cannot %S_MSG a database snapshot.
3707 16 Cannot detach a suspect database. It must be repaired or dropped.
3708 16 Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is a system %S_MSG.
3709 16 Cannot %S_MSG the database while the database snapshot “%.*ls” refers to it. Drop that database first.
3710 16 Cannot detach an opened database when the server is in minimally configured mode.
3716 16 The %S_MSG ‘%.*ls’ cannot be dropped because it is bound to one or more %S_MSG.
3717 16 Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.
3721 16 Type ‘%.*ls’ cannot be renamed because it is being
referenced by object ‘%.*ls’.
3723 16 An explicit DROP INDEX is not allowed on index ‘%.*ls’. It is being used for %ls constraint enforcement.
3724 16 Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is being used for replication.
3725 16 The constraint ‘%.*ls’ is being referenced by table ‘%.*ls’, foreign key constraint ‘%.*ls’.
3726 16 Could not drop object ‘%.*ls’ because it is referenced by a FOREIGN KEY constraint.
3727 10 Could not drop constraint. See previous errors.
3728 16 ‘%.*ls’ is not a constraint.
3729 16 Cannot %ls ‘%.*ls’ because it is being referenced by object ‘%.*ls’.
3730 16 Cannot drop the default constraint ‘%.*ls’ while it is being used by a foreign key as SET DEFAULT referential action.
3732 16 Cannot drop type ‘%.*ls’ because it is currently in use. 3733 16 Constraint ‘%.*ls’ does not belong to table ‘%.*ls’. 3734 16 Could not drop the primary key constraint ‘%.*ls’ because the table has an XML index.
3737 16 Could not delete file ‘%ls’. See the SQL Server error log for more information.
3738 10 Deleting database file ‘%ls’.
3739 11 Cannot %ls the index ‘%.*ls’ because it is not a statistics collection.
3740 16 Cannot drop the %S_MSG ‘%.*ls’ because at least part of the table resides on a read-only filegroup.
3741 16 Cannot drop the %S_MSG ‘%.*ls’ because at least part of the table resides on an offline filegroup.
3743 16 The database ‘%.*ls’ is enabled for database mirroring. Database mirroring must be removed before you drop the database. 3744 16 Only a single clause is allowed in a statement where an index is dropped online.
3745 16 Only a clustered index can be dropped online.
3746 16 Cannot drop the clustered index of view ‘%.*ls’ because the view is being used for replication.
3747 16 Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index ‘%.*ls’ is created on view ‘%.*ls’. 3748 16 Cannot drop non-clustered index ‘%.*ls’ using drop clustered index clause.
3749 16 Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead.
3750 10 Warning: Index ‘%.*ls’ on %S_MSG ‘%.*ls’ was disabled as a result of disabling the clustered index on the %S_MSG.
3751 16 Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with ‘%.*ls’ because ‘%.*ls’ is a %S_MSG. Use DROP %ls.
3801 10 Warning: The index “%.*ls” on “%.*ls”.”%.*ls” may be impacted by the collation upgrade. Run DBCC CHECKTABLE.
3802 10 Warning: The constraint “%.*ls” on “%.*ls”.”%.*ls” may be impacted by the collation upgrade. Disable and enable WITH CHECK. 3803 10 Warning: The index “%.*ls” on “%.*ls”.”%.*ls” is disabled because the implementation of the checksum function has changed. 3804 10 Warning: The check constraint “%.*ls” on table
“%.*ls”.”%.*ls” is disabled because the implementation of the checksum function has changed.
3805 10 Warning: Index “%.*ls” on table “%.*ls”.”%.*ls” might be corrupted because it references computed column “%.*ls” containing a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify index. Consider using explicit CONVERT with deterministic date style such as 121. Computed column indexes referencing non-deterministic expressions can’t be created in 90 compatibility mode. See Books Online topic “Creating Indexes on Computed Columns” for more information. 3806 10 Warning: Indexed view “%.*ls”.”%.*ls” might be corrupted because it contains a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify view. Consider using explicit CONVERT with deterministic date style such as 121. Indexed views referencing non-deterministic expressions can’t be created in 90 compatibility mode. See Books Online topic “Creating Indexed Views” for more information. 3807 17 Create failed because all available identifiers have been exhausted.
3808 10 Warning: The index “%.*ls” on “%.*ls”.”%.*ls” is disabled because the index is defined on a view with ignore_dup_key index option. Drop the index and, if possible, recreate it without ignore_dup_key option. You may need to change the logical structure of the view to ensure all rows are unique.
3809 16 Upgrade of database “%.*ls” failed because index “%.*ls” on object ID %d has the same name as that of another index on the same table. 3810 10 Event notification “%.*ls” on assembly is dropped.
3811 10 Event notification “%.*ls” on service queue is dropped as broker instance is not specified.
3812 10 Event notification “%.*ls” on object is dropped.
3813 16 Upgrade of login ‘%.*ls’ failed because its name or sid is a duplicate of another login or server role.
3816 16 Upgrade of login ‘%.*ls’ failed because its password hash is invalid. Update the login password before upgrade.
3851 10 An invalid row (%ls) was found in the system table
sys.%ls%ls.
3852 10 Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
3853 10 Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
3854 10 Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (%ls) in sys.%ls%ls that is invalid.
3855 10 Attribute (%ls) exists without a row (%ls) in sys.%ls%ls. 3856 10 Attribute (%ls) exists but should not for row (%ls) in sys.%ls%ls.
3857 10 The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls.
3858 10 The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid value.
3859 10 Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE.
3860 10 Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use.
3862 10 User defined type ‘%.*ls’.’%.*ls’ is disabled because the on disk format for this udt has been changed. Use DROP TYPE to remove this disabled type.
3864 23 Could not find an entry for index %d with object ID %d in database %d. Possible schema corruption. Run DBCC CHECKDB.
3901 16 The transaction name must be specified when it is used with the mark option.
3902 16 The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
3903 16 The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
3904 21 Cannot unsplit logical page %S_PGID in object ‘%.*ls’, in database ‘%.*ls’. Both pages together contain more data than will fit on one page.
3906 16 Failed to update database “%.*ls” because the database is read-only.
3908 16 Could not run BEGIN TRANSACTION in database ‘%.*ls’ because the database is in bypass recovery mode.
3909 16 Session binding token is invalid.
3910 16 Transaction context in use by another session.
3912 16 Cannot bind using an XP token while the server is not in an XP call.
3914 16 The data type “%s” is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max).
3915 16 Cannot use the ROLLBACK statement within an INSERT-EXEC statement.
3916 16 Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
3917 16 Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
3918 16 The statement or function must be executed in the context of a user transaction.
3919 16 Cannot enlist in the transaction because the transaction has already been committed or rolled back.
3920 10 The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
3921 16 Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started 3922 16 Cannot enlist in the transaction because the transaction does not exist.
3923 10 Cannot use transaction marks on database ‘%.*ls’ with bulk-logged operations that have not been backed up. The mark is ignored. 3924 10 The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction.
3925 16 Invalid transaction mark name. The ‘LSN:’ prefix is
reserved.
3926 10 The transaction active in this session has been committed or aborted by another session.
3927 10 The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction. 3928 16 The marked transaction ‘%.*ls’ failed. A Deadlock was encountered while attempting to place the mark in the log.
3929 16 No distributed or bound transaction is allowed in single user database.
3930 16 The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. 3931 16 The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction. 3932 16 The save point name “%.*ls” that was provided is too long. The maximum allowed length is %d characters.
3933 16 Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
3951 16 Transaction failed in database ‘%.*ls’ because the statement was run under snapshot isolation but the transaction did not start in snapshot isolation. You cannot change the isolation level of the transaction to snapshot after the transaction has started unless the transaction was originally started under snapshot isolation level.
3952 16 Snapshot isolation transaction failed accessing database ‘%.*ls’ because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation.
3953 16 Snapshot isolation transaction failed in database ‘%.*ls’ because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered. 3954 16 Snapshot isolation transaction failed to start in database ‘%.*ls’ because the ALTER DATABASE command that disallows snapshot isolation had started before this transaction began. The database is in transition to OFF state. You will either need to change the isolation level of the transaction or re-enable the snapshot isolation in the database. 3955 16 Snapshot isolation transaction failed in database ‘%.*ls’ because the recovery was skipped for this database. You must recover the database before you can run a transaction under snapshot isolation. 3956 16 Snapshot isolation transaction failed to start in database ‘%.*ls’ because the ALTER DATABASE command which enables snapshot isolation for this database has not finished yet. The database is in transition to pending ON state. You must wait until the ALTER DATABASE Command completes successfully.
3957 16 Snapshot isolation transaction failed in database ‘%.*ls’ because the database did not allow snapshot isolation when the current transaction started. It may help to retry the transaction.
3958 16 Transaction aborted when accessing versioned row in table ‘%.*ls’ in database ‘%.*ls’. Requested versioned row was not found. Your tempdb is probably out of space. Please refer to BOL on how to configure tempdb for versioning.
3959 10 Version store is full. New version(s) could not be added. A transaction that needs to access the version store may be rolled back. Please refer to BOL on how to configure tempdb for versioning. 3960 16 Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table ‘%.*ls’ directly or indirectly in database ‘%.*ls’ to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. 3961 16 Snapshot isolation transaction failed in database ‘%.*ls’ because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
3963 16 Transaction failed in database ‘%.*ls’ because distributed transactions are not supported under snapshot isolation.
3964 16 Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not versioned, a metadata change can lead to inconsistency if mixed within snapshot isolation.
3965 16 The PROMOTE TRANSACTION request failed because there is no local transaction active.
3966 17 Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient space in tempdb. This transaction was marked as a victim earlier because it may need the row version(s) that have already been removed to make space in tempdb. Retry the transaction
3967 17 Insufficient space in tempdb to hold row versions. Need to shrink the version store to free up some space in tempdb. Transaction (id=%I64d xsn=%I64d spid=%d elapsed_time=%d) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning. 3968 10 Snapshot isolation or read committed snapshot is not available in database ‘%.*ls’ because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
3970 16 This operation conflicts with another pending operation on this transaction. The operation failed.
3971 16 The server failed to resume the transaction. Desc:%I64x. 3972 20 Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d.
3973 16 The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed.
3974 16 The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed.
3975 16 The varchar(max) data type is not supported for
sp_getbindtoken. The batch has been aborted.
3976 16 The transaction name has the odd length %d. The batch has been aborted.
3977 16 The savepoint name cannot be NULL. The batch has been aborted.
3978 16 Beginning a new transaction after rollback to save point is not allowed.
3979 16 The TM request is longer than expected. The request is not processed.
3980 16 The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy.
3981 16 The transaction operation cannot be performed because there are pending requests working on this transaction.
3982 16 New transaction is not allowed to be started while DTC or bound transaction is active.
3983 16 The operation failed because the session is not single threaded.
3984 16 Cannot acquire a database lock during a transaction change. 3985 16 An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.
3986 19 The transaction timestamps ran out. Restart the server. 3987 10 SNAPSHOT ISOLATION is always enabled in this database. 3988 16 New transaction is not allowed because there are other threads running in the session.
3989 16 New request is not allowed to start because it should come with valid transaction descriptor.
3990 16 Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
3991 16 The context transaction which was active before entering user defined routine, trigger or aggregate “%.*ls” has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.
3992 16 Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate “%.*ls”. This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.
3993 16 The user transaction that has been started in user defined routine, trigger or aggregate “%.*ls” is not ended upon exiting from it. This is not allowed and the transaction will be rolled back. Change application logic to enforce strict transaction nesting.
3994 16 Transaction is not allowed to roll back inside a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
3995 16 Unknown transaction isolation level %d, valid value range is 0 to 5.
3996 16 Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction.
3997 16 A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back. 3998 16 Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.

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: