错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 6 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 9239 — Internal query notifications error: The garbage collector corrected an inconsistency.
- 9240 — Service broker dialog '%.*ls' could not be closed due to a broker error in database with id '%d' because of the following error in service broker: '%.…
- 9241 — Service broker dialog '%.*ls' could not be closed because the database with id '%d' is not available. Consider closing the dialogs manually once the d…
- 9242 — Query notification delivery could not get dialog endpoint for dialog '%.*ls'. Query notification delivery failed because of the following error in ser…
- 9243 — Query notification delivery could not send message on dialog '%.*ls'. Query notification delivery failed because of the following error in service bro…
- 9244 — Query notification cleanup could not access metadata for database "%d". Check whether the database is successfully restored and online.
- 9245 — During the last time interval %d query notification errors were suppressed.
- 9246 — Distributed Exchange moved %I64u rows and %I64u bytes.
- 9300 — %sIn this version of the server, the 'fn:id()' function only accepts an argument of type 'IDREF *'.
- 9301 — %sIn this version of the server, 'cast as <type>%s' is not available. Please use the 'cast as <type> ?' syntax.
- 9302 — %sThe context item in which the 'fn:id()' function is used must be a node.
- 9303 — %sSyntax error near '%ls', expected '%ls'.
- 9304 — %sThis version of the server only supports XQuery version '1.0'.
- 9305 — %sOnly type names followed by '?' are supported in the target of 'instance of'.
- 9306 — %sThe target of 'replace value of' cannot be a union type, found '%ls'.
- 9308 — %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 typ…
- 9309 — %sThe target of 'replace value of' cannot be 'http://www.w3.org/2001/XMLSchema#anySimpleType', found '%ls'.
- 9310 — %sThe 'with' clause of 'replace value of' cannot contain constructed XML.
- 9311 — %sHeterogeneous sequences are not allowed in '%ls', found '%ls' and '%ls'.
- 9312 — %s'%ls' is not supported on simple typed or 'http://www.w3.org/2001/XMLSchema#anyType' elements, found '%ls'.
- 9313 — %sThis version of the server does not support multiple expressions or expressions mixed with strings in an attribute constructor.
- 9314 — %sCannot implicitly atomize or apply 'fn:data()' to complex content elements, found type '%ls' within inferred type '%ls'.
- 9315 — %sOnly constant expressions are supported for the name expression of computed element and attribute constructors.
- 9316 — %sCannot use 'xmlns' in the name expression of computed attribute constructor.
- 9317 — %sSyntax error near '%ls', expected string literal.
- 9318 — %sSyntax error at source character '0x%02x' near '%ls', expected string literal.
- 9319 — %sStatic simple type validation: Invalid simple type value '%ls'.
- 9320 — %sThe result of applying the 'parent' axis on the document node is statically 'empty'.
- 9321 — %sThe result of applying 'parent::%ls' is statically 'empty'.
- 9322 — %sTwo consecutive '-' can only appear in a comment constructor if they are used to close the comment ('-->').
- 9323 — %sUsing ':' in variable names is not supported in this version of the server.
- 9324 — %sFound '}' without matching '{'. If you want to use the characters '{' or '}', you need to escape them as '{{' or '}}' respectively.
- 9325 — %sComputed processing instruction constructors are not supported.
- 9326 — %sComputed comment constructors are not supported.
- 9327 — %sAll prolog entries need to end with ';', found '%ls'.
- 9328 — %sType specification expected, found '%ls'.
- 9330 — %sOnly comparable types are allowed in '%ls', found '%ls'.
- 9331 — %sSyntax error near '%ls', expected '%ls' or '%ls'.
- 9332 — %sSyntax error near '%ls', expected 'where', '(stable) order by' or 'return'.
- 9333 — %s'//' followed by 'self', 'parent' or 'descendant-or-self' axes is not supported when it encounters simple typed or 'http://www.w3.org/2001/XMLSchema…
- 9334 — %sThe 'form' attribute cannot be specified on a local attribute or element definition that has the 'ref' attribute. Location: '%ls'.
- 9335 — %sThe XQuery syntax '%ls' is not supported.
- 9336 — %sThe XML Schema syntax '%ls' is not supported.
- 9337 — %sThe XML Schema type 'NOTATION' is not supported.
- 9338 — %sThe value of a namespace declaration attribute must be a string literal. It cannot contain expressions.
- 9339 — %sThe 'form' attribute cannot be specified on a global attribute or element definition. Location: '%ls'.
- 9340 — %sExplicit import of the current target namespace is invalid. References to items in the current target namespace that have already been loaded in the…
- 9341 — %sSyntax error near '%ls', expected a step expression.
- 9342 — %sAn XML instance is only supported as the direct source of an insert using sql:column/sql:variable.
- 9343 — %sThe XML instance referred to by sql:column() and sql:variable() must be either untyped XML or must be typed with the same XML schema collection as t…
- 9344 — %sThe SQL type '%s' is not supported with sql:column() and sql:variable().
- 9400 — XML parsing: line %d, character %d, unexpected end of input
- 9401 — XML parsing: line %d, character %d, unrecognized encoding
- 9402 — XML parsing: line %d, character %d, unable to switch the encoding
- 9403 — XML parsing: line %d, character %d, unrecognized input signature
- 9410 — XML parsing: line %d, character %d, whitespace expected
- 9411 — XML parsing: line %d, character %d, semicolon expected
- 9412 — XML parsing: line %d, character %d, '>' expected
- 9413 — XML parsing: line %d, character %d, A string literal was expected
- 9414 — XML parsing: line %d, character %d, equal expected
- 9415 — XML parsing: line %d, character %d, well formed check: no '<' in attribute value
- 9416 — XML parsing: line %d, character %d, hexadecimal digit expected
- 9417 — XML parsing: line %d, character %d, decimal digit expected
- 9418 — XML parsing: line %d, character %d, '[' expected
- 9419 — XML parsing: line %d, character %d, '(' expected
- 9420 — XML parsing: line %d, character %d, illegal xml character
- 9421 — XML parsing: line %d, character %d, illegal name character
- 9422 — XML parsing: line %d, character %d, incorrect document syntax
- 9423 — XML parsing: line %d, character %d, incorrect CDATA section syntax
- 9424 — XML parsing: line %d, character %d, incorrect comment syntax
- 9425 — XML parsing: line %d, character %d, incorrect conditional section syntax
- 9426 — XML parsing: line %d, character %d, incorrect ATTLIST declaration syntax
- 9427 — XML parsing: line %d, character %d, incorrect DOCTYPE declaration syntax
- 9428 — XML parsing: line %d, character %d, incorrect ELEMENT declaration syntax
- 9429 — XML parsing: line %d, character %d, incorrect ENTITY declaration syntax
- 9430 — XML parsing: line %d, character %d, incorrect NOTATION declaration syntax
- 9431 — XML parsing: line %d, character %d, NDATA expected
- 9432 — XML parsing: line %d, character %d, PUBLIC expected
- 9433 — XML parsing: line %d, character %d, SYSTEM expected
- 9434 — XML parsing: line %d, character %d, name expected
- 9435 — XML parsing: line %d, character %d, one root element
- 9436 — XML parsing: line %d, character %d, end tag does not match start tag
- 9437 — XML parsing: line %d, character %d, duplicate attribute
- 9438 — XML parsing: line %d, character %d, text/xmldecl not at the beginning of input
- 9439 — XML parsing: line %d, character %d, namespaces beginning with "xml" are reserved
- 9440 — XML parsing: line %d, character %d, incorrect text declaration syntax
- 9441 — XML parsing: line %d, character %d, incorrect xml declaration syntax
- 9442 — XML parsing: line %d, character %d, incorrect encoding name syntax
- 9443 — XML parsing: line %d, character %d, incorrect public identifier syntax
- 9444 — XML parsing: line %d, character %d, well formed check: pes in internal subset
- 9445 — XML parsing: line %d, character %d, well formed check: pes between declarations
- 9446 — XML parsing: line %d, character %d, well formed check: no recursion
- 9447 — XML parsing: line %d, character %d, entity content not well formed
- 9448 — XML parsing: line %d, character %d, well formed check: undeclared entity
- 9449 — XML parsing: line %d, character %d, well formed check: parsed entity
- 9450 — XML parsing: line %d, character %d, well formed check: no external entity references
- 9451 — XML parsing: line %d, character %d, incorrect processing instruction syntax
- 9452 — XML parsing: line %d, character %d, incorrect system identifier syntax
- 9453 — XML parsing: line %d, character %d, '?' expected
- 9454 — XML parsing: line %d, character %d, no ']]>' in element content
- 9455 — XML parsing: line %d, character %d, illegal qualified name character
- 9456 — XML parsing: line %d, character %d, multiple colons in qualified name
- 9457 — XML parsing: line %d, character %d, colon in name
- 9458 — XML parsing: line %d, character %d, redeclared prefix
- 9459 — XML parsing: line %d, character %d, undeclared prefix
- 9460 — XML parsing: line %d, character %d, non default namespace with empty uri
- 9461 — XML %ls starting with '%.*ls' is %d characters long, which exceeds the limit. Maximum allowed length is %d characters.
- 9462 — XML parsing: line %d, character %d, not all chunks of value have been read
- 9463 — XML parsing: line %d, character %d, xml:space has a non-legal value
- 9464 — XML parsing: line %d, character %d, XML namespace prefix 'xml' can only be associated with the URI http://www.w3.org/XML/1998/namespace . This URI can…
- 9465 — XML parsing: line %d, character %d, XML namespace prefix 'xmlns' is reserved for use by XML.
- 9466 — XML parsing: line %d, character %d, XML namespace xml namespace URI ( http://www.w3.org/XML/1998/namespace ) must be assigned only to prefix 'xml'.
- 9467 — XML parsing: line %d, character %d, xmlns namespace URI ( http://www.w3.org/2000/xmlns/ ) is reserved and must not be used.
- 9480 — XML parsing: line %d, character %d, unsupported xml
- 9500 — The data type '%.*ls' used in the VALUE method is invalid.
- 9501 — XQuery: Unable to resolve sql:variable('%.*ls'). The variable must be declared as a scalar TSQL variable.
- 9502 — The string literal provided for the argument %d of the '%.*ls' method must not exceed %d bytes.
- 9503 — Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls'. See previous error messages for more details.
- 9504 — Errors and/or warnings occurred when processing the XQuery statement for XML data type method '%.*ls', invoked on column '%.*ls', table '%.*ls'. See p…
- 9506 — The XMLDT method '%.*ls' can only be invoked on columns of type xml.
- 9507 — The XML data type method on a remote column used in this query can not be executed either locally or remotely. Please rewrite your query.
- 9508 — The reference parameter given to XMLDT method '%.*ls' was generated from a different XML instance than the one it is being applied to.
- 9509 — XMLUNNEST method requires typed xml column with single global element
- 9510 — Functionality not yet implemented: XMLNODEREFS cannot use references exposed by views.
- 9512 — Xml data type is not supported as a parameter to remote calls.
- 9513 — Error processing XML data type method '%.*ls'. The following SET options required by XML data type methods are not set: '%.*ls'.
- 9514 — Xml data type is not supported in distributed queries. Remote object '%.*ls' has xml column(s).
- 9515 — An XML schema has been altered or dropped, and the query plan is no longer valid. Please rerun the query batch.
- 9516 — XQuery: The name or one of the parts of a multi-part name supplied to %S_MSG('%.*ls') is empty. Empty names cannot be used to identify objects, column…
- 9517 — XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it is too long…
- 9518 — XQuery: The name or one of the parts of a multi-part name that starts with '%.*ls' supplied to %S_MSG() is not a valid SQL identifier - it contains in…
- 9519 — XQuery: The name supplied to sql:variable('%.*ls') is not a valid SQL variable name. Variable names must start with the '@' symbol followed by at leas…
- 9520 — XQuery: '%.*ls' referenced by sql:variable() is not a valid system function name.
- 9521 — Error processing XML data type. The XML data type instance contains a negative xs:date or xs:dateTime value.
- 9522 — The XQuery modify method is not allowed on sparse column sets.
- 9523 — Cannot update the sparse column set '%.*ls' because the XML content supplied references the non-sparse column '%.*ls' which does not belong to this co…
- 9524 — The XML content provided does not conform to the required XML format for sparse column sets.
- 9525 — The XML content that is supplied for the sparse column set '%.*ls' contains duplicate references to the column '%.*ls'. A column can only be reference…
- 9526 — In the XML content that is supplied for the sparse column set '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is out of range. The valid r…
- 9527 — In the XML content that is supplied for the column set '%.*ls', the sqltypes:scale attribute value on the element '%.*ls' is out of range. The valid r…
- 9528 — In the XML content that is supplied for the column set '%.*ls', the '%.*ls' attribute on the element '%.*ls' is not valid. The attribute is valid only…
- 9529 — In the XML content that is supplied for the column set column '%.*ls', the sqlDBType:base64Encoded attribute on the element '%.*ls' is not valid. The …
- 9530 — In the XML content that is supplied for the column set column '%.*ls, the '%.*ls' attribute on the element '%.*ls' is not valid. Remove the attribute.
- 9531 — In the XML content that is supplied for the column set column '%.*ls', the '%.*ls' attribute value on the element '%.*ls' is not valid.
- 9532 — In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the col…
- 9533 — In the XML that is supplied for the column set '%.*ls', the element '%.*ls' should reside in the global namespace. Remove the default namespace declar…
- 9534 — In the query/DML operation involving column set '%.*ls', conversion failed when converting from the data type '%ls' to the data type '%ls' for the col…
- 9535 — For untyped XML it is not allowed to specify MAXLENGTH or SINGLETON option if XSD type is not already specified for path '%.*ls' of selective XML inde…
- 9536 — It is not allowed to specify REMOVE '%.*ls' more than once for the same pathname in alter statement for selective XML index '%.*ls'.
- 9537 — Two paths indexed with selective XML index '%.*ls' on table '%.*ls' would have same path name with new collation.
- 9538 — Paths with same path expression indexed with selective XML index '%.*ls' should have SINGLETON option either specified for all of them or for none of …
- 9539 — Selective XML Index feature is not supported for the current database version
- 9601 — Cannot relate to %S_MSG %.*ls because it is %S_MSG.
- 9602 — Failed to start a system task with error code %d, state %d.
- 9605 — Conversation Priorities analyzed: %d.
- 9606 — The conversation priority with ID %d has been dropped.
- 9607 — The conversation priority with ID %d is referencing the missing service with ID %d.
- 9608 — The conversation priority with ID %d is referencing the missing service contract with ID %d.
- 9609 — The %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.
- 9610 — The service '%.*ls' in the FROM SERVICE clause must match the service '%.*ls' referenced by %s = '%.*ls'.
- 9611 — Cannot find the specified user '%.*ls'.
- 9613 — The queue '%.*ls' cannot be activated because the activation user is not specified.
- 9614 — The queue '%.*ls' cannot be activated because the activation stored procedure is either not specified or is invalid.
- 9615 — A message of type '%.*ls' failed XML validation on the target service. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d,…
- 9616 — A message of type '%.*ls' was received and failed XML validation. %.*ls This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and …
- 9617 — The service queue "%.*ls" is currently disabled.
- 9618 — The message cannot be sent because the service queue '%.*ls' associated with the dialog is currently disabled and retention is on.
- 9619 — Failed to create remote service binding '%.*ls'. A remote service binding for service '%.*ls' already exists.
- 9620 — The activation stored procedure '%.*ls' is invalid. Functions are not allowed.
- 9621 — An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i.
- 9622 — The crypto provider context is not initialized.
- 9623 — The key passed in for this operation is in the wrong state.
- 9624 — The key size is unacceptable for this key object.
- 9625 — The key buffer size is inconsistent with the key modulus size.
- 9626 — An internal Service Broker error occurred: an object is in the wrong state for this operation. This error indicates a serious problem with SQL Server.…
- 9627 — The hash buffer size is not correct for initializing the hash object.
- 9628 — The encryption/decryption data buffer size is not 8 byte aligned.
- 9629 — The decrypted signature size is wrong.
- 9630 — The signature did not verify the internal hash.
- 9631 — The salt size is unacceptable for this key object.
- 9632 — The salt buffer size is too small.
- 9633 — The passed in name is too long.
- 9634 — Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem. Check the SQL Server error lo…
- 9635 — The certificate is not valid at this point in time.
- 9636 — The requested object was not found.
- 9637 — The passed in serialized object is incorrectly encoded.
- 9638 — The cer or pvk file size is too large.
- 9639 — A password was supplied and the pvk file is not encrypted.
- 9640 — The operation encountered an OS error.
- 9641 — A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the operating system erro…
- 9642 — An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far endpoin…
- 9643 — An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i.
- 9644 — An error occurred in the service broker message dispatcher. Error: %i, State: %i.
- 9645 — An error occurred in the service broker manager, Error: %i, State: %i.
- 9646 — An error occurred in the timer event cache. Error %i, state %i.
- 9647 — Received a malformed message from the network. Unable to retrieve a broker message attribute from a message destined for database ID %d. This may indi…
- 9648 — The queue '%.*ls' has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider increasing the number …
- 9649 — A security (SSPI) error occurred when connecting to another service broker: '%.*ls'. Check the operating system error log for more information.
- 9650 — A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error '%ls'.
- 9651 — The system call failed during a Service Broker or Database Mirroring operation. System error: '%ls'.
- 9652 — Service Broker failed to retrieve the session key for encrypting a message.
- 9653 — The signature of activation stored procedure '%.*ls' is invalid. Parameters are not allowed.
- 9654 — Attempting to use database and it doesn't exist.
- 9655 — The transmission queue table structure in database is inconsistent. Possible database corruption.
- 9656 — An error occurred in the service broker multicast manager, Error: %i, State: %i.
- 9657 — The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware…
- 9658 — Cannot access the transmission queue table in database.
- 9659 — The %s of route '%.*ls' cannot be empty.
- 9660 — The %s of route '%.*ls' must be less than %d characters long.
- 9661 — The SERVICE_NAME and BROKER_INSTANCE of route "%.*ls" must be specified when using mirroring.
- 9662 — Cannot specify BROKER_INSTANCE without SERVICE_NAME in route "%.*ls".
- 9663 — The system object cannot be modified.
- 9666 — The %S_MSG endpoint is in disabled or stopped state.
- 9667 — Services analyzed: %d.
- 9668 — Service Queues analyzed: %d.
- 9669 — Conversation Endpoints analyzed: %d.
- 9670 — Remote Service Bindings analyzed: %d.
- 9671 — Messages with conversation ID '%ls' have been removed from the transmission queue.
- 9672 — Messages with conversation handle '%ls' and conversation group '%ls' have been removed from the queue with ID %d.
- 9673 — Activation has been disabled on the queue with ID %d.
- 9674 — Conversation Groups analyzed: %d.
- 9675 — Message Types analyzed: %d.
- 9676 — Service Contracts analyzed: %d.
- 9677 — The service contract with ID %d is referencing the missing message type with ID %d.
- 9678 — The service with ID %d is referencing the missing service contract with ID %d.
- 9679 — The service with ID %d is referencing the missing service queue with ID %d.
- 9680 — The conversation endpoint '%ls' is referencing the missing conversation group '%ls'.
- 9681 — The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service contract with ID %d.
- 9682 — The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the missing service with ID %d.
- 9683 — The conversation group '%ls' is referencing the missing service with ID %d.
- 9684 — The service with ID %d has been dropped.
- 9685 — The service contract with ID %d has been dropped.
- 9686 — The conversation endpoint with handle '%ls' has been dropped.
- 9687 — The conversation group '%ls' has been dropped.
- 9688 — Service Broker manager has started.
- 9689 — Service Broker manager has shut down.
- 9690 — The %S_MSG endpoint is now listening for connections.
- 9691 — The %S_MSG endpoint has stopped listening for connections.
- 9692 — The %S_MSG endpoint cannot listen on port %d because it is in use by another process.
- 9693 — The %S_MSG endpoint cannot listen for connections due to the following error: '%.*ls'.
- 9694 — Could not start Service Broker manager. Check the SQL Server error log and the operating system error log for additional error messages.
- 9695 — Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. Check the SQL Server error lo…
- 9696 — Cannot start the Service Broker primary event handler. This error is a symptom of another problem. Check the SQL Server error log for additional messa…
- 9697 — Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log fo…
- 9698 — Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the operating system er…
- 9699 — Could not allocate memory for extra Service Broker tasks while adding CPUs.
- 9701 — Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the operating system …
- 9704 — This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target servic…
- 9705 — The messages in the queue with ID %d are referencing the invalid conversation handle '%ls'.
- 9706 — The stored procedure with ID %d is invalid but is referenced by the queue with ID %d.
- 9707 — The activation user with ID %d is invalid but is referenced by queue with ID %d.
- 9708 — The messages in the queue with ID %d are referencing the invalid conversation group '%ls'.
- 9709 — The messages in the queue with ID %d are referencing the invalid message type with ID %d.
- 9710 — The conversation endpoint with ID '%ls' and is_initiator: %d is referencing the invalid conversation group '%ls'.
- 9711 — The transmission queue is referencing the invalid conversation ID '%ls'.
- 9712 — The remote service binding with ID %d is referencing the invalid service contract with ID %d.
- 9713 — The message type with ID %d is referencing the invalid XML schema collection ID %d.
- 9715 — The conversation endpoint with conversation handle '%ls' is in an inconsistent state. Check the SQL Server error logs and the operating system error l…
- 9716 — The conversation group '%ls' reports references to %d conversation handle(s), but actually references %d.
- 9717 — Cannot enable stored procedure activation on queue '%.*ls'. Event notification for queue_activation is already configured on this queue.
- 9718 — Cannot create event notification for queue_activation on queue "%.*ls". Stored procedure activation is already configured on this queue.
- 9719 — The database for this conversation endpoint is attached or restored.
- 9720 — The database for the remote conversation endpoint is attached or restored.
- 9721 — Service broker failed to clean up conversation endpoints on database '%.*ls'. Another problem is preventing SQL Server from completing this operation.…
- 9722 — Connection attempt to destination '%.*ls' failed. %.*ls
- 9723 — The database "%i" will not be started as the broker due to duplication in the broker instance ID.
- 9724 — The activated proc '%ls' running on queue '%ls' output the following: '%.*ls'
- 9725 — The invalid schema has been dropped from the message type with ID %d.
- 9726 — The remote service binding with ID %d has been dropped.
- 9727 — Dialog security is not available for this conversation because there is no remote service binding for the target service. Create a remote service bind…
- 9728 — Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped after th…
- 9729 — There is no cluster proxy route for the URI '%.*ls'.
- 9730 — Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security principal …
- 9731 — Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: %i). Either create …
- 9732 — Error during startup, shutdown or update of cluster proxy route manager.
- 9733 — There is no private key for the security certificate bound to database principal (Id: %i). The certificate may have been created or installed incorrec…
- 9734 — The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the operating system cryptographi…
- 9735 — The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the operating system cryptographic…
- 9736 — An error occurred in dialog transmission: Error: %i, State: %i. %.*ls
- 9737 — The private key for the security certificate bound to the database principal (ID %i) is password protected. Password protected private keys are not su…
- 9738 — Cannot create task for Service Broker message dispatcher. This message is a symptom of another problem that is preventing SQL Server from creating tas…
- 9739 — Message transmitter in service broker message dispatcher failed %d times
- 9740 — Cannot start the Service Broker message dispatcher. This error is a symptom of another problem. Check the SQL Server error log and the operating syste…
- 9741 — The %S_MSG '%.*ls' was dropped on upgrade because it referenced a system contract that was dropped.
- 9742 — The activation stored procedure '%.*ls' is invalid. Temporary procedures may not be configured for activation.
- 9743 — The %s of route "%.*ls" must be an address when using mirroring.
- 9744 — The %s of route "%.*ls" is not a valid address.
- 9745 — The ADDRESS of route '%.*ls' cannot be 'TRANSPORT' when SERVICE_NAME is specified.
- 9746 — The LIFETIME of route '%.*ls' must be in the range %d to %d.
- 9747 — The ADDRESS and MIRROR_ADDRESS of route '%.*ls' cannot be the same.
- 9748 — The %S_MSG protocol transport is not available.
- 9749 — Target queue is busy; message(s) queued for delivery.
- 9750 — No route matches the destination service name for this conversation. Create a route to the destination service name for messages in this conversation …
- 9751 — Authentication failed with error: '%.*ls'.
- 9752 — %S_MSG connection was refused. The user account of the remote server is not permitted to log in to this SQL Server: User account: '%.*ls', IP address:…
- 9753 — The target service broker is unreachable.
- 9754 — Connection attempt failed with error: '%.*ls'.
- 9755 — An error occurred while receiving data: '%.*ls'.
- 9756 — An internal exception occurred while connecting to an adjacent broker: Error: %i, State: %i. %.*ls
- 9757 — Service Broker/Database Mirroring network protocol error occurred.
- 9758 — Login protocol negotiation error occurred.
- 9759 — An error occurred while sending data: '%.*ls'.
- 9760 — The connection has been idle for over %d seconds.
- 9761 — The Broker Configuration conversation on dialog handle '%s' closed due to an error. To troubleshoot this problem, investigate the error: '%.*ls'.
- 9762 — An error occurred while looking up the public key certificate associated with this SQL Server instance: No certificate was found.
- 9763 — An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is not valid at the curr…
- 9764 — An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found is too large.
- 9765 — An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate found has no associated privat…
- 9766 — An unknown internal error (%d) occurred while looking up the public key certificate associated with this SQL Server instance.
- 9767 — The security certificate bound to database principal (Id: %i) has been disabled for use with BEGIN DIALOG. See the Books Online topics "Certificates a…
- 9768 — A database user associated with the secure conversation was dropped before credentials had been exchanged with the far endpoint. Avoid using DROP USER…
- 9769 — Insufficient memory prevented the Service Broker/Database Mirroring Transport Manager from starting.
- 9770 — Locating routes and security information via the Broker Configuration Service.
- 9771 — The service broker manager is disabled in single-user mode.
- 9772 — The Service Broker in database "%.*ls" cannot be enabled because there is already an enabled Service Broker with the same ID.
- 9773 — The Service Broker in database "%d" is disabled because there is already an enabled Service Broker with the same ID.
- 9774 — Cannot create a new Service Broker in the attached read-only database "%.*ls". The Service Broker will be disabled.
- 9775 — Cannot create a new Service Broker in read-only database "%.*ls".
- 9776 — Cannot enable the Service Broker in database "%.*ls" because the Service Broker GUID in the database (%s) does not match the one in sys.databases (%s)…
- 9777 — The Service Broker in database "%.*ls" will be disabled because the Service Broker GUID in the database (%s) does not match the one in sys.databases (…
- 9778 — Cannot create a new Service Broker in a mirrored database "%.*ls".
- 9779 — Service Broker received an END CONVERSATION message on this conversation. Service Broker will not transmit the message; it will be held until the appl…
- 9780 — The service broker manager is initializing.
- 9781 — The service broker manager is shutting down.
- 9782 — An internal exception occurred while dispatching a message: Error: %i, State: %i. %.*ls
- 9783 — DNS lookup failed with error: '%.*ls'.
- 9784 — Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held until the application end…
- 9785 — Invalid address specified: '%.*ls'.
- 9786 — Cannot retrieve user name from security context. Error: '%.*ls'. State: %hu.
- 9787 — An error occurred while processing broker mirroring routes. Error: %i. State: %i.
- 9788 — Unable to route the incoming message. The system database msdb containing routing information is not available.
- 9789 — Unable to route the incoming message. The system database msdb containing routing information is not available. The broker is disabled in msdb.
- 9790 — Unable to route the incoming message. The system database msdb containing routing information is in SINGLE USER mode.
- 9791 — The broker is disabled in the sender's database.
- 9792 — Could not forward the message because forwarding is disabled in this SQL Server instance.
- 9793 — The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied.
- 9794 — The broker mirroring manager has not fully initialized.
- 9795 — Could not find the target broker in the local SQL Server instance.
- 9796 — The target service name matched a LOCAL route, but there is no service by that name in the local SQL Server instance.
- 9797 — Classification has been delayed because the routing information is currently being updated.
- 9798 — The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
- 9799 — The connection was closed by the remote end, or an error occurred while receiving data: '%.*ls'
- 9801 — Error converting %.*ls to %ls. The result would be truncated.
- 9802 — The locale identifier (LCID) %d is not supported by SQL Server.
- 9803 — Invalid data for type "%ls".
- 9804 — Column or parameter #%d: Invalid fractional second precision %d specified for %ls data type. The maximum fractional second precision is %d.
- 9805 — Warning: converting %ls to %ls caused a loss of information.
- 9806 — The datepart %.*ls is not supported by date function %.*ls.
- 9807 — The input character string does not follow style %d, either change the input character string or use a different style.
- 9808 — This session's YDM date format is not supported when converting from this character string format to date, time, datetime2 or datetimeoffset. Change t…
- 9809 — The style %d is not supported for conversions from %s to %s.
- 9810 — The datepart %.*ls is not supported by date function %.*ls for data type %s.
- 9811 — The system timezone information could not be retrieved.
- 9812 — The timezone provided to builtin function %.*ls is invalid.
- 9813 — The timezone provided to builtin function %.*ls would cause the datetimeoffset to overflow the range of valid date range in either UTC or local time.
- 9814 — The date provided is before the start of the Hijri calendar which in Microsoft's 'Kuwaiti Algorithm' is July 15th, 622 C.E. (Julian calendar) or July …
- 9815 — Waitfor delay and waitfor time cannot be of type %s.
- 9816 — The number of columns in the column set exceeds 2048. Reduce the number of columns that are referenced in the column set.
- 9817 — The specified column set value causes the estimated row size to be at least %d bytes. This exceeds the maximum allowed row size of %d bytes. To reduce…
- 9818 — The culture parameter '%.*ls' provided in the function call is not supported.
- 9819 — Error converting string value '%.*ls' into data type %ls using culture '%.*ls'.
- 9820 — The time zone parameter '%.*ls' provided to AT TIME ZONE clause is invalid.
- 9821 — Internal error occurred during time zone conversion.
- 9822 — Internal error occurred during time zone data access.
- 9823 — COMPRESS builtin failed.
- 9824 — Not enough memory for COMPRESS builtin to execute.
- 9825 — DECOMPRESS builtin failed.
- 9826 — Uncompressed or corrupted data passed as argument to DECOMPRESS builtin.
- 9827 — Not enough memory for DECOMPRESS builtin to execute.
- 9828 — The second and third arguments of the TRANSLATE built-in function must contain an equal number of characters.
- 9829 — STRING_AGG aggregation result exceeded the limit of 8000 bytes. Use LOB types to avoid result truncation.
- 9830 — %ls cannot be less than zero.\nParameter name: %ls.
- 9831 — %ls cannot be larger than length of string.\nParameter name: %ls.
- 9832 — Index and length must refer to a location within the string.\nParameter name: %ls.
- 9833 — Invalid data for %ls-encoded characters
- 9834 — Invalid bucket width value passed to date_bucket function. Only positive values are allowed.
- 9835 — Calculating date bucket for '%ls' column caused an overflow.
- 9836 — The query processor encountered an unexpected error during processing an APPROX_PERCENTILE function. Please contact support.
- 9837 — An invalid %ls value was encountered: The date value is less than the minimum date value allowed for the data type.
- 9838 — Parameter %d in function '%ls' is out of range 0 to %d.
- 9839 — Parameter 3 in function 'set_bit' must be 0 or 1.
- 9840 — The statement failed because the number of rows passed to APPROX_PERCENTILE function exceeded an internal limit. Consider adding a GROUP BY expression…
- 9841 — An invalid Unicode escape sequence was specified in the input. Unicode escape sequences should be specified as <UESCAPE character>XXXX or <UESCAPE cha…
- 9842 — Invalid Unicode escape character was provided. The <UESCAPE character> cannot be <plus sign> <single quote> <double quotes> <space> <hexit>.
- 9843 — Unicode escape character '%.*ls' is invalid. Unicode escape character should be of 1 character length and a code point ranging from U+0020 up to U+007…
- 9844 — The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.
- 9845 — The fuzzy string matching function failed to convert string to sort weights for collation-aware comparison.
- 9846 — String similarity function cannot process input text larger than 8 KB.
- 9847 — The fuzzy string matching function does not support SQL_* collations. Use a Windows collation instead.
- 9901 — Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on disk space. Pausing all populations in progress until more space becomes available. …
- 9902 — Full-text catalog '%ls' ('%d') in database '%ls' ('%d') is low on system resources. Any population in progress will be paused until more resources bec…
- 9903 — The full-text catalog health monitor reported a failure for full-text catalog '%ls' (%d) in database '%ls' (%d). Reason code: %d. Error: %ls. The syst…
- 9904 — The full-text catalog '%ls' (%d) in database '%ls' (%d) will be remounted to recover from a failure. Reason code: %d. Error: %ls. If this message occu…
- 9905 — Informational: Full-text indexer requested status change for catalog '%ls' ('%d') in database '%ls' ('%d'). New Status: %ls, Reason: %ls (%ls).
- 9906 — The full-text catalog monitor reported catalog '%ls' (%d) in database '%ls' (%d) in %ls state. This is an informational message only. No user action i…
- 9907 — Error: Total number of items in full-text catalog ID '%d' in database ID '%d' exceeds the supported limit. See Books Online for troubleshooting assist…
- 9908 — Changing the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). This is an informational message only. No user action is required.
- 9909 — Warning: Failed to change the status to %ls for full-text catalog '%ls' (%d) in database '%ls' (%d). Error: %ls.
- 9910 — Warning: Error occurred during full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%…
- 9911 — Informational: Full-text %ls population initialized for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Population sub-…
- 9912 — Error: Failed to initialize full-text %ls population for table or indexed view '%ls', database '%ls' (table or indexed view ID '%d', database ID '%d')…
- 9913 — Informational: Resuming full-text population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). Prio…
- 9914 — Error: Failed to resume full-text %ls population for table or indexed view '%ls' in database '%ls' (table or indexed view ID '%d', database ID '%d'). …
- 9915 — Reinitialized full-text %ls population for table '%ls' (table ID '%d', database ID '%d') after a temporary failure. Number of documents processed prio…
- 9916 — Error: Failed to reinitialize full-text %ls population after a temporary failure for table or indexed view '%ls', database '%ls' (table or indexed vie…
- 9917 — An internal error occurred in full-text docid mapper.
- 9918 — Warning: Full-text catalog '%ls' uses FAT volume. Security and differential backup are not supported for the catalog.
- 9919 — Fulltext DDL command failed because SQL Server was started in single user mode.
- 9920 — Warning: Failed to get MSFTESQL indexer interface for full-text catalog '%ls' ('%d') in database '%ls' ('%d'). Error: %ls.
- 9921 — During upgrade fatal error 0x%x encountered in CoCreateGuid. Failed to resolve full-text catalog file name for '%ls'.
- 9922 — Warning: Full-text population for table or indexed view '%ls' failed to send batch of data to MSFTESQL service (table or indexed view ID '%d', catalog…
- 9923 — Warning: Full-text population for table or indexed view '%ls' reported low resources while sending a batch of data to MSFTESQL service (table or index…
- 9924 — Rebuild full-text catalog '%ls' failed: Catalog header file is read-only.
- 9925 — Rebuild full-text catalog '%ls' failed: Full-text catalog is read-only.
- 9926 — Informational: MS Search stop limit reached. The full-text query may have returned fewer rows than it should.
- 9927 — Informational: The full-text search condition contained noise word(s).
- 9928 — Computed column '%.*ls' cannot be used for full-text search because it is nondeterministic or imprecise nonpersisted computed column.
- 9929 — Computed column '%.*ls' cannot be used as full-text type column for image or varbinary(MAX) column. This computed column must be deterministic, precis…
- 9930 — Null document type provided. Row will not be full-text indexed.
- 9931 — Document type exceeds the maximum permitted length. Row will not be full-text indexed.
- 9932 — Document type value is malformed. Row will not be full-text indexed.
- 9933 — Internal error: The row cannot be full-text indexed. The protocol handler was invoked out of sequence. This is an informational message only. No user …
- 9934 — Row was not found. It was deleted or updated while indexing was in progress.
- 9935 — Warning: Wordbreaker, filter, or protocol handler used by catalog '%ls' does not exist on this instance. Use sp_help_fulltext_catalog_components and s…
- 9936 — Informational: No full-text supported languages found.
- 9937 — Too many full-text columns or the full-text query is too complex to be executed.
- 9938 — Cannot find the specified user or role '%.*ls'.
- 9939 — Current user or role '%.*ls' does not have the required permission to set the owner.
- 9940 — Error: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is terminated due to the preceding e…
- 9941 — Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') is being suspended by the sy…
- 9942 — Informational: Full-text %ls population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') was cancelled by user.
- 9943 — Informational: Full-text %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documen…
- 9944 — Informational: Full-text retry pass of %ls population completed for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Num…
- 9945 — Error: All Full-text populations in progress, for catalog '%ls' ('%d') in database '%ls' ('%d') were terminated due to error. Error: 0x%x.
- 9946 — Warning: Failed to mount full-text catalog '%ls' in directory '%ls'. The full-text catalog cannot be attached.
- 9947 — Warning: Identity of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog cannot be attached.
- 9948 — Warning: Full-text catalog path '%ls' is invalid. It exceeds the length limit, or it is a relative path, or it is a hidden directory, or it is a UNC P…
- 9949 — Warning: All Full-text populations in progress for full-text catalog '%ls' ('%d') in database '%ls' ('%d') are paused. Reason code: %d. Error: %ls. If…
- 9950 — Informational: Full-text catalog health monitor reported a failure for catalog '%ls' ('%d') in database '%ls' ('%d'). Reason code: %d. Error: %ls. The…
- 9951 — Warning: Database %.*ls cannot be modified during detach because database is in read-only, standby, or shutdown state. Full-text catalog is not droppe…
- 9952 — Informational: Full-text auto change tracking is turned off for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') due to f…
- 9953 — The path '%.*ls' has invalid attributes. It needs to be a directory. It must not be hidden, read-only, or on a removable drive.
- 9954 — SQL Server failed to communicate with filter daemon launch service (OS error: %ls). Full-Text filter daemon process failed to start. Full-text search …
- 9955 — SQL Server failed to create named pipe '%ls' to communicate with the full-text filter daemon (OS error: %d). Either a named pipe already exists for a …
- 9956 — SQL Server failed to logon the Full-Text filter daemon account '%ls' (Windows error code %d). The filter daemon process will not be started and full-t…
- 9957 — Full-text operation failed due to full-text catalog %ls is corrupted. Use rebuild catalog to correct the problem.
- 9959 — Cannot perform requested task because full-text memory manager is not initialized.
- 9960 — View '%.*ls' is not an indexed view. Full-text index is not allowed to be created on it.
- 9961 — Logical name, size, maxsize, filegrowth, and offline properties of full-text catalog cannot be modified.
- 9962 — Failed to move full-text catalog from '%ls' to '%ls'. OS error '%ls'.
- 9963 — Inconsistent accent sensitivity of full-text catalog is detected. Full-text catalog for catalog ID '%d', database ID '%d' is reset.
- 9964 — Failed to finish full-text operation. Filegroup '%.*ls' is empty, read-only, or not online.
- 9965 — NULL or Invalid type of value specified for '%ls' parameter.
- 9966 — Cannot use full-text search in master, tempdb, or model database.
- 9967 — A default full-text catalog does not exist in database '%.*ls' or user does not have permission to perform this action.
- 9968 — Warning: No appropriate filter was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', database ID…
- 9969 — Warning: No appropriate wordbreaker was found during full-text index population for table or indexed view '%ls' (table or indexed view ID '%d', databa…
- 9970 — Couldn't complete full-text operation because full-text key for table or indexed view '%.*ls' is offline.
- 9971 — Warning: No appropriate filter for embedded object was found during full-text index population for table or indexed view '%ls' (table or indexed view …
- 9972 — Database is not fully started up or it is not in an ONLINE state. Try the full-text DDL command again after database is started up and becomes ONLINE.
- 9973 — Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d'). Number of documents …
- 9974 — Warning: Only running full population can be paused. The command is ignored. Other type of population can just be stopped and it will continue when yo…
- 9975 — Warning: Only paused full population can be resumed. The command is ignored.
- 9976 — The Microsoft SQL Server Service (mssqlserver%ls%ls) is shutting down. The system administrator must start this service.
- 9977 — Warning: Last population complete time of full-text catalog in directory '%ls' does not match database '%.*ls'. The full-text catalog is attached and …
- 9978 — Warning: During upgrade full-text index on table '%ls' is disabled because at least one of full-text key column, full-text columns, or type columns is…
- 9979 — Warning: During upgrade full-text catalog '%ls' in database '%ls' is set as offline because it failed to be created at path '%ls'. Please fix the full…
- 9980 — Variable parameters can not be passed to fulltext predicates: contains, freetext and functions: containstable, freetexttable applied to remote table.
- 9982 — Cannot use full-text search in user instance.
- 9983 — The value '%ls' for the full-text component '%ls' is longer than the maximum permitted (%d characters). Please reduce the length of the value.
- 9984 — Informational: Full-text %ls population paused for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d').
- 9985 — There is not enough memory to generate a search property list cache. Rerun your full-text indexing statement when more resources are available.
- 9986 — A search property list cache cannot be generated during full-text indexing. Attempting to query the registered search properties caused an internal er…
- 9987 — The max gap argument in NEAR clause must be either the word MAX or an integer greater than or equal to 0.
- 9988 — The number of query terms in NEAR clause must be less than or equal to 64.
- 9989 — Cannot use full-text search in this instance.
- 9990 — Failed to retrieve full-text batch size configuration. A batch size of %d will be used instead.
- 9991 — Failed to retrieve max full-text crawl range configuration. A crawl range of %d will be used instead.
- 9992 — Failed to retrieve full-text drop batch size configuration. A drop batch size of %d will be used instead.
- 9993 — Informational: Failed to create Fulltext index internal table to track failed DocId on table '%.*ls'.
- 9994 — Informational: Failed to insert failed Doc Id '%d' from table '%ls' into the internal table, error: %d.
- 9995 — Internal table access error: failed to access the Fulltext failed DocId internal table with HRESULT: 0x%x.
- 9996 — Failed to create DML AFTER trigger to track DML operations on failed Doc Id for table '%ls'.
- 9998 — The column '%.*ls' cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a full-text index, add fewer c…
- 9999 — The column '%.*ls' in the table '%.*ls' cannot be used for full-text search because it is a sparse column set.
- 10000 — Unknown provider error.
- 10001 — The provider reported an unexpected catastrophic failure.
- 10002 — The provider did not implement the functionality.
- 10003 — The provider ran out of memory.
- 10004 — One or more arguments were reported invalid by the provider.
- 10005 — The provider did not support an interface.
- 10006 — The provider indicated an invalid pointer was used.
- 10007 — The provider indicated an invalid handle was used.
- 10008 — The provider terminated the operation.
- 10009 — The provider did not give any information about the error.
- 10010 — The data necessary to complete this operation was not yet available to the provider.
- 10011 — Access denied.
- 10021 — Execution terminated by the provider because a resource limit was reached.
- 10022 — The provider called a method from IRowsetNotify in the consumer, and the method has not yet returned.
- 10023 — The provider does not support the necessary method.
- 10024 — The provider indicates that the user did not have the permission to perform the operation.
- 10025 — Provider caused a server fault in an external process.
- 10026 — No command text was set.
- 10027 — Command was not prepared.
- 10028 — Authentication failed.
- 10032 — Cannot return multiple result sets (not supported by the provider).
- 10033 — The specified index does not exist or the provider does not support an index scan on this data source.
- 10034 — The specified table or view does not exist or contains errors.
- 10035 — No value was given for one or more of the required parameters.
- 10042 — Cannot set any properties while there is an open rowset.
- 10052 — The insertion was canceled by the provider during notification.
- 10053 — Could not convert the data value due to reasons other than sign mismatch or overflow.
- 10054 — The data value for one or more columns overflowed the type used by the provider.
- 10055 — The data violated the integrity constraints for one or more columns.
- 10056 — The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
- 10057 — Cannot create the row. Would exceed the total number of active rows supported by the rowset.
- 10058 — The consumer cannot insert a new row before releasing previously-retrieved row handles.
- 10062 — The change was canceled by the provider during notification.
- 10063 — Could not convert the data value due to reasons other than sign mismatch or overflow.
- 10064 — The data value for one or more columns overflowed the type used by the provider.
- 10065 — The data violated the integrity constraints for one or more columns.
- 10066 — The number of rows that have pending changes has exceeded the limit specified by the DBPROP_MAXPENDINGROWS property.
- 10067 — 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 — The consumer could not delete the row. A deletion is pending or has already been transmitted to the data source.
- 10069 — The consumer could not delete the row. The insertion has been transmitted to the data source.
- 10081 — The rowset uses integrated indexes and there is no current index.
- 10085 — RestartPosition on the table was canceled during notification.
- 10086 — The table was built over a live data stream and the position cannot be restarted.
- 10087 — The provider did not release some of the existing rows.
- 10088 — 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 fet…
- 10100 — Cannot create %S_MSG on view "%.*ls" because it contains the DISTINCT keyword. Consider removing DISTINCT from the view or not indexing the view. Alte…
- 10101 — Cannot create %S_MSG on view "%.*ls" because it contains the TOP or OFFSET keyword. Consider removing the TOP or OFFSET or not indexing the view.
- 10102 — Cannot create %S_MSG on view "%.*ls" because it contains the TABLESAMPLE clause. Consider removing TABLESAMPLE or not indexing the view.
- 10103 — Cannot create %S_MSG on view "%.*ls" because it uses OPENROWSET, OPENQUERY, or OPENDATASOURCE. Consider not indexing the view, or eliminating OPENQUER…
- 10104 — Cannot create %S_MSG on view "%.*ls" because it references a table using a CONTAINSTABLE or FREETEXTTABLE full-text function. Consider removing use of…
- 10105 — Cannot create %S_MSG on view "%.*ls" because it uses the OPENXML rowset provider. Consider removing OPENXML or not indexing the view.
- 10106 — Cannot create %S_MSG on view "%.*ls" because it references an internal system rowset provider. Consider not indexing this view.
- 10107 — 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 va…
- 10108 — Cannot create %S_MSG on view "%.*ls" because it references a SQL Server internal table.
- 10109 — Cannot create %S_MSG on view "%.*ls" because it references derived table "%.*ls" (defined by SELECT statement in FROM clause). Consider removing the r…
- 10110 — Cannot create %S_MSG on view "%.*ls" because it contains an OUTER APPLY. Consider not indexing the view, or removing OUTER APPLY.
- 10111 — 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 — Cannot create %S_MSG on view '%.*ls' because it contains an INNER join that specifies a join hint. Consider removing the join hint.
- 10113 — 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 usin…
- 10114 — Cannot create %S_MSG on view "%.*ls" because it uses the PIVOT operator. Consider not indexing this view.
- 10115 — Cannot create %S_MSG on view "%.*ls" because it uses the UNPIVOT operator. Consider not indexing this view.
- 10116 — Cannot create %S_MSG on view '%.*ls' because it contains one or more UNION, INTERSECT, or EXCEPT operators. Consider creating a separate indexed view …
- 10117 — Cannot create %S_MSG on view "%.*ls" because the view uses the "*" operator to select columns. Consider referencing columns by name instead.
- 10118 — Cannot create %S_MSG on view "%.*ls" because it contains a GROUP BY ALL. Consider using a GROUP BY instead.
- 10119 — Cannot create %S_MSG on view "%.*ls" because it contains a CUBE, ROLLUP, or GROUPING SETS operator. Consider not indexing this view.
- 10120 — Cannot create %S_MSG on view "%.*ls" because it contains the ROLLUP operator. Consider not indexing this view.
- 10121 — Cannot create %S_MSG on view "%.*ls" because it contains a HAVING clause. Consider removing the HAVING clause.
- 10122 — 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 inst…
- 10124 — Cannot create %S_MSG on view "%.*ls" because it references an internal SQL Server column.
- 10125 — Cannot create %S_MSG on view "%.*ls" because it uses aggregate "%.*ls". Consider eliminating the aggregate, not indexing the view, or using alternate …
- 10126 — Cannot create %S_MSG on view "%.*ls" because it uses aggregate "%.*ls" with the DISTINCT keyword. Consider not indexing this view or eliminating DISTI…
- 10127 — 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. A…
- 10128 — Cannot create %S_MSG on view "%.*ls" because it uses a CONTAINS or FREETEXT full-text predicate. Consider eliminating CONTAINS or FREETEXT, or not ind…
- 10129 — Cannot create %S_MSG on view "%.*ls" because it references the inline or multistatement table-valued function "%.*ls". Consider expanding the function…
- 10130 — Cannot create %S_MSG on view "%.*ls" because it uses non-deterministic common language runtime (CLR) table-valued function "%.*ls". Consider not index…
- 10131 — Cannot create %S_MSG on view "%.*ls" because it references imprecise common language runtime (CLR) table-valued function "%.*ls". Consider not indexin…
- 10132 — Cannot create %S_MSG on view "%.*ls" because it references table valued common language runtime (CLR) function "%.*ls". Consider removing reference to…
- 10133 — Cannot create %S_MSG on view "%.*ls" because function "%.*ls" referenced by the view performs user or system data access.
- 10134 — Cannot create %S_MSG on view "%.*ls" because it contains more than one APPLY. Consider not indexing the view, or using only one APPLY.
- 10136 — Cannot create %S_MSG on view "%.*ls" because it uses the aggregate COUNT. Use COUNT_BIG instead.
- 10137 — Cannot create %S_MSG on view "%.*ls" because it references common table expression "%.*ls". Views referencing common table expressions cannot be index…
- 10138 — 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 — Cannot create %S_MSG on view '%.*ls' because the view uses an implicit conversion from string to datetime or smalldatetime. Use an explicit CONVERT wi…
- 10140 — Cannot create %S_MSG on view '%.*ls' because the view contains a table hint. Consider removing the hint.
- 10141 — Cannot create %S_MSG on view '%.*ls' because it references CLR routine (function or method) '%.*ls' outside non-key columns of SELECT list. Recreate o…
- 10142 — Cannot create %S_MSG on view "%.*ls" because it contains an APPLY. Consider not indexing the view, or removing APPLY.
- 10143 — Cannot create %S_MSG on view "%.*ls" because it contains a ranking or aggregate window function. Remove the function from the view definition or, alte…
- 10144 — Cannot create %S_MSG on view '%.*ls' because it uses the CHANGETABLE function.
- 10145 — Cannot create %S_MSG on the view '%.*ls' because it references a sparse column set. Views that contain a sparse column set cannot be indexed. Consider…
- 10146 — Cannot create %S_MSG on the view '%.*ls' because it uses the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE functio…
- 10147 — Cannot create %S_MSG on the view '%.*ls' because it uses temporal FOR SYSTEM_TIME clause.
- 10148 — Cannot create %S_MSG on the view '%.*ls' because it uses OPENJSON.
- 10149 — Index that has SNAPSHOT_MATERIALIZATION cannot be created on view '%.*ls' because view definition contains memory-optimized table(s).
- 10150 — Cannot create %S_MSG on the view '%.*ls' because it references a scalar UDF that is inlineable.
- 10151 — Cannot create %S_MSG on view "%.*ls" because it uses a ANTISEMI or SEMI join, and no SEMI joins are allowed in indexed views. Consider using an INNER …
- 10211 — Cannot invoke mutator on a null CLR type value.
- 10227 — Field "%.*ls" of type "%.*ls.%.*ls" cannot be updated because the field is "%.*ls".
- 10240 — Could not find UdtExtensions.dll. Please check your installation.
- 10300 — Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the …
- 10301 — Assembly '%.*ls' references assembly '%.*ls', which is not present in the current database. SQL Server attempted to locate and automatically load the …
- 10302 — Could not get path for SQL Server: '%ls'.
- 10303 — Could not create AppDomain manager: '%.*ls'.
- 10304 — Failed to enter Common Language Runtime (CLR) with HRESULT 0x%x. This may due to low resource conditions.
- 10305 — The Init method for a CLR table-valued function must be annotated with SqlFunctionAttribute.
- 10306 — The SqlFunctionAttribute of the Init method for a CLR table-valued function must set the FillRowMethodName property.
- 10307 — The FillRowMethodName property of SqlFunctionAttribute does not contain a valid method name.
- 10308 — Warning: The Microsoft .NET Framework assembly '%.*ls' you are registering is not fully tested in the SQL Server hosted environment and is not support…
- 10309 — Warning: The SQL Server client assembly '%.*ls' you are registering is not fully tested in SQL Server hosted environment.
- 10310 — AppDomain %i (%.*ls) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
- 10311 — AppDomain %i (%.*ls) is marked for unload due to memory pressure.
- 10312 — .NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token.
- 10313 — 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 proble…
- 10314 — 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…
- 10316 — The app domain with specified version id (%d) was unloaded due to memory pressure and could not be found.
- 10317 — An error occurred trying to get file version info for the file '%s'.
- 10318 — '%.*ls' failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAttribute.
- 10319 — UserDefinedType method call failed because parameter %d of method '%.*ls' of type '%.*ls' is annotated with unsupported attribute System.ParamArrayAtt…
- 10320 — Method name '%.*ls' is invalid for '%.*ls'.
- 10321 — Method name '%.*ls' is invalid for UserDefinedType method call.
- 10322 — Type %.*ls not found in database %.*ls
- 10323 — Invalid user code has been identified by .Net Framework Managed Debug Assistant %.*ls
- 10324 — WITH ENCRYPTION option of CREATE TRIGGER is only applicable to T-SQL triggers and not to CLR triggers.
- 10325 — The server is shutting down due to stack overflow in user's unmanaged code.
- 10326 — Two versions of assembly '%.*ls' cannot coexist in database '%.*ls'. Keep one version and drop the other.
- 10327 — %ls ASSEMBLY for assembly '%.*ls' failed because assembly '%.*ls' is not trusted. The assembly is trusted when either of the following is true: the as…
- 10328 — There is not enough stack to create appdomain '%.*ls'.
- 10329 — .Net Framework execution was aborted. %.*ls
- 10330 — ALTER ASSEMBLY failed because serialization layout of type '%s' would change as a result of a change in type '%s' in the updated assembly. Persisted t…
- 10331 — Type '%ls' in assembly '%.*ls' derives from a generic type which is not supported for a CLR Type.
- 10332 — Assembly "%.*ls" was built using version %.*ls of the .NET Framework. SQL Server currently uses version %s.
- 10333 — Failed to obtain ICLRAppDomainResourceMonitor interface from CLR. The error code from CLR was: 0x%x. As a result, resource monitoring won't work for A…
- 10334 — Changing the database compatibility level has caused data to be marked as unchecked in one or more objects in database %s. Refer to the column has_unc…
- 10335 — The Common Language Runtime (CLR) was loaded in an unsupported manner. This can occur if an extended stored procedure or OLE Automation object running…
- 10336 — Failed to enque task to start CLR during SQL server startup. Error code: %u. CLR will be started in an on-demand fashion.
- 10337 — An internal error occurred.
- 10338 — Verification of assembly failed. Could not open the physical file '%.*ls': %ls.
- 10339 — Verification of assembly failed. Could not read from the physical file "%.*ls": %ls.
- 10340 — DROP ASSEMBLY failed. Error code: 0x%x.
- 10341 — Assembly '%.*ls' cannot be loaded because Azure SQL Database does not support user-defined assemblies. Contact Azure Technical Support if you have que…
- 10342 — Assembly '%.*ls' cannot be loaded because this edition of SQL Server only supports SAFE assemblies.
- 10343 — CREATE or ALTER ASSEMBLY for assembly '%.*ls' with the SAFE or EXTERNAL_ACCESS option failed because the 'clr strict security' option of sp_configure …
- 10344 — Internal table access error: failed to access the Trusted Assemblies internal table with HRESULT: 0x%x. Contact Customer Support Services.
- 10345 — The assembly hash '0x%.*ls' is already trusted.
- 10346 — The assembly hash '0x%.*ls' is not currently trusted. No action was taken.
- 10347 — Common Language Runtime(CLR) is not enabled on this instance.
- 10501 — Cannot create plan guide '%.*ls' because type '%.*ls' provided is not allowed.
- 10502 — Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch , or by @plan_handle and @statement_start_offset , matc…
- 10503 — Operation '%.*ls' is not allowed.
- 10504 — Cannot create plan guide '%.*ls' because parameter @hints is incorrect. Use N'OPTION ( <query_hint> [ ,...n ] )'.
- 10505 — 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 — Cannot create plan guide '%.*ls' because parameter @stmt has more than one statement.
- 10507 — Cannot create plan guide '%.*ls' because the statement specified by @stmt and @module_or_batch , or by @plan_handle and @statement_start_offset , does…
- 10508 — 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 t…
- 10509 — Cannot create plan guide '%.*ls' because the statement specified by @stmt or @statement_start_offset either contains a syntax error or is ineligible f…
- 10510 — Cannot create plan guide '%.*ls' because there is already a plan guide with that name in the database. Use a unique name.
- 10511 — Cannot create plan guide '%.*ls' because @params is not NULL. @params must be NULL if @type is 'object'.
- 10512 — Cannot create plan guide '%.*ls' because object '@module_or_batch' is encrypted. Consider tuning query using other techniques such as indexes and stat…
- 10513 — 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 g…
- 10514 — Cannot create plan guide '%.*ls' because @module_or_batch can not be large object when @type is object.
- 10515 — Cannot create plan guide '%.*ls' because the module '%.*ls' does not exist or you do not have needed permission.
- 10516 — Cannot create plan guide '%.*ls' because @module_or_batch can not be compiled.
- 10517 — Cannot create plan guide '%.*ls' because you do not have needed permission. Alter database permission required.
- 10518 — Cannot execute sp_control_plan_guide because of insufficient permissions to control plan guide '%.*ls'. Alter permission on object referenced by plan …
- 10519 — Cannot create plan guide '%.*ls' because the hints specified in @hints cannot be applied to the statement specified by either @stmt or @statement_star…
- 10520 — Cannot create plan guide '%.*ls' because @type was specified as '%ls' and a non-NULL value is specified for the parameter '%ls'. This type requires a …
- 10521 — Cannot create plan guide '%.*ls' because @type was specified as '%ls' and the parameter '%ls' is NULL. This type requires a non-NULL value for the par…
- 10522 — Cannot create plan guide '%.*ls' because @hints has illegal value. @hints must be OPTION(PARAMETERIZATION FORCED) or OPTION(PARAMETERIZATION SIMPLE) i…
- 10523 — Cannot generate query template because @querytext does not contain a valid single query.
- 10524 — Cannot parameterize @querytext .
- 10525 — Plan guide '%.*ls' matched statement after it was parameterized automatically by FORCED or SIMPLE parameterization, but the RECOMPILE hint it contains…
- 10526 — 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. Re…
- 10527 — Cannot create plan guide '%.*ls' because the object '%.*ls' is a temporary object.
- 10528 — Cannot create plan guide '%.*ls' because its name is invalid. Plan guide name cannot begin with a '#' character.
- 10529 — Cannot create plan guide '%.*ls' because there is already a planguide '%.*ls' of @type 'template' on @stmt .
- 10530 — Cannot create plan guide '%.*ls' because the statement specified by @statement_start_offset does not match any statement in specified module or batch.…
- 10531 — Cannot create plan guide '%.*ls' from cache because the user does not have adequate permissions. Grant the VIEW SERVER STATE permission to the user cr…
- 10532 — Cannot create plan guide '%.*ls' because the batch or module specified by @plan_handle does not contain a statement that is eligible for a plan guide.…
- 10533 — Cannot create plan guide '%.*ls' because the plan guide name exceeds 124, the maximum number of characters allowed. Specify a name that contains fewer…
- 10534 — Cannot create plan guide '%.*ls' because the value specified for @params is invalid. Specify the value in the form <parameter_name> <parameter_type>, …
- 10535 — Cannot create plan guide '%.*ls' because a plan was not found in the plan cache that corresponds to the specified plan handle. Specify a cached plan h…
- 10536 — Cannot create plan guide '%.*ls' because the batch or module corresponding to the specified @plan_handle contains more than 1000 eligible statements. …
- 10537 — Cannot enable plan guide '%.*ls' because the enabled plan guide '%.*ls' contains the same scope and starting offset value of the statement. Disable th…
- 10538 — Cannot find the plan guide either because the specified plan guide ID is NULL or invalid, or you do not have permission on the object referenced by th…
- 10539 — Cannot create plan guide '%.*ls' from cache because a query plan is not available for the statement with start offset %d.This problem can occur if the…
- 10601 — Cannot specify included columns for a clustered index.
- 10602 — Mixing old and new syntax in CREATE/ALTER/DROP INDEX statement is not allowed.
- 10603 — Cannot rebuild clustered index '%.*ls' on view '%.*ls' because the view is dependent on base table '%.*ls' whose clustered index '%.*ls' is disabled.
- 10604 — Cannot convert a statistic to an index using DROP_EXISTING index option when ONLINE index option is also specified.
- 10605 — Cannot disable primary key index "%.*ls" on table "%.*ls" because the table is published for replication.
- 10606 — Cannot disable the clustered index "%.*ls" on view "%.*ls" because the indexed view is published for replication.
- 10607 — The clustered index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Disable change tracking on the table be…
- 10608 — The index '%.*ls' on table '%.*ls' cannot be disabled because the table has change tracking enabled. Change tracking requires a primary key constraint…
- 10609 — Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is a computed column. Rewrite the filte…
- 10610 — Filtered index '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered indexes are only supported on tables. If you are t…
- 10611 — Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant of higher d…
- 10612 — Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is compared with a constant that cannot…
- 10617 — Index '%.*ls' could not be created or rebuilt. The key length for this index (%d bytes) exceeds the maximum allowed length of '%d' bytes when using th…
- 10618 — Cannot %S_MSG filtered index '%.*ls' on table '%.*ls' because the statement sets the IGNORE_DUP_KEY option to ON. Rewrite the statement so that it doe…
- 10619 — Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the column '%.*ls' in the filter expression is of a CLR data type. Rewrite the filt…
- 10620 — Filtered %S_MSG '%.*ls' cannot be created on table '%.*ls' because the filter expression contains a comparison with a literal NULL value. Rewrite the …
- 10621 — The index '%.*ls' on table '%.*ls' could not be created because the column '%.*ls' in the filter expression of the index is a column set.
- 10622 — The %S_MSG '%.*ls' could not be created or rebuilt. A compressed index is not supported on table that contains sparse columns or a column set column.
- 10623 — Filtered statistics '%.*ls' cannot be created on object '%.*ls' because it is not a user table. Filtered statistics are only supported on user tables.
- 10624 — The CREATE INDEX or REBUILD INDEX statement failed for index '%.*ls' on table '%.*ls' because a distribution policy cannot be specified for system dat…
- 10625 — A distribution key cannot be created containing more than %d columns.
- 10626 — Column name '%.*ls' appears more than one time in the list of columns in the distribution key.
- 10627 — Column '%.*ls' cannot be part of the distribution key of the index '%.*ls' because the column is not part of the unique index key. Distribution key co…
- 10628 — Index '%.*ls' on table '%.*ls' is a hypothetical index that was created to hold column-level statistics. A distribution policy is not allowed for hypo…
- 10629 — The data type specified for column '%.*ls' in table '%.*ls' cannot be used as a column in the distribution key of an index.
- 10630 — The index distribution policy is invalid. The policy must be set to HASH, NONE, or REPLICATE. Distribution columns cannot be specified when the distri…
- 10631 — Index '%.*ls' could not be created or rebuilt. A unique or clustered index on a federated table must contain the federated column.
- 10632 — Index '%.*ls' could not be created. Views cannot be indexed in a federated database.
- 10633 — Invalid online index creation operation
- 10634 — An '%.*ls' statement was executed on object '%.*ls' by hostname '%.*ls', host process ID %d using the WAIT_AT_LOW_PRIORITY options with MAX_DURATION =…
- 10635 — An online operation cannot be performed for '%.*ls' because the index contains column of large object type, and in the same transaction there are upda…
- 10636 — Ignore in Optimization cannot be set for '%.*ls' on '%.*ls.%.*ls' because it is only applicable to non-clustered B-tree or columnstore indexes.
- 10637 — Cannot perform this operation on '%.*ls' with ID %I64d as one or more indexes are currently in resumable index rebuild state. Please refer to sys.inde…
- 10638 — ALTER INDEX '%S_MSG' failed. There is no pending resumable index operation for the index '%.*ls' on '%.*ls'.
- 10639 — Resumable index operation for %S_MSG '%.*ls' failed because the index contains column '%.*ls' of type timestamp as a key column.
- 10640 — Ignore in Optimization cannot be set for an index on '%.*ls.%.*ls' because it is only applicable to indexes on user defined disk-based tables.
- 10641 — ALTER INDEX PAUSE failed. There is no actively running resumable index operation for the index '%.*ls' on '%.*ls'.
- 10642 — SNAPSHOT_MATERIALIZATION cannot be set for index '%.*ls' on '%.*ls' because it is only applicable to indexes on views.
- 10643 — SNAPSHOT_MATERIALIZATION cannot be set for '%.*ls' on '%.*ls' because it is only applicable to clustered indexes on views.
- 10644 — Resumable index operation for %S_MSG '%.*ls' failed because the index contains the computed column '%.*ls' as a key or partitioning column. If this is…
- 10645 — Warning: An existing resumable operation with the same options was identified for the same index on '%.*ls'. The existing operation will be resumed in…
- 10646 — Index '%.*ls' on view '%.*ls' that has SNAPSHOT_MATERIALIZATION cannot be dropped using the DROP_EXISTING option.
- 10647 — Index '%.*ls' on '%.*ls' that has SNAPSHOT_MATERIALIZATION cannot be altered.
- 10648 — SNAPSHOT_MATERIALIZATION cannot be set for partitioned index '%.*ls' on '%.*ls'.
- 10649 — Nonclustered index '%.*ls' cannot be created on '%.*ls' that has clustered index '%.*ls' with SNAPSHOT_MATERIALIZATION.
- 10650 — Refresh of snapshot view(s) requires snapshot isolation to be enabled on the database.
- 10651 — Refresh of snapshot view failed because view '%.*ls.%.*ls' does not exist.
- 10652 — Refresh of snapshot view failed because '%.*ls.%.*ls' is not a snapshot view.
- 10653 — Refresh of snapshot view failed.
- 10654 — Refresh of snapshot view failed because lock could not be obtained on the database.
- 10655 — Refresh of snapshot view failed because view is not specified in two-part name format.
- 10656 — The resumable index operation for index '%.*ls' on object '%.*ls' was paused.
- 10657 — The resumable index '%.*ls' on object '%.*ls' has been paused for '%.2f' hours.
- 10658 — Stored procedure '%ls' is currently disabled.
- 10659 — An ALTER INDEX '%S_MSG' was executed for index '%.*ls' on object '%.*ls' by hostname '%.*ls'.
- 10660 — The online index build operation was chosen as a deadlock victim over 500 times while attempting to process a single row. Resolve the blocking concurr…
- 10661 — The refresh operation for all snapshot views failed because there was another refresh operation (either for all or a single snapshot view) in progress…
- 10662 — The refresh operation for snapshot view '%.*ls' failed because another refresh operation for the same snapshot view was already in progress.
- 10663 — The refresh operation for snapshot view '%.*ls' failed because refresh operation for all snapshot views was already in progress.
- 10664 — Cannot specify included columns for indexes on memory optimized tables.
- 10665 — '%.*ls' with DROP_EXISTING option is not supported with %S_MSG option.
- 10666 — Cannot resume index build as required DOP %d (DOP operation was started with) is not available. Please ensure sufficient DOP is available or abort exi…
- 10667 — Warning: Create Index was started with MAXDOP %d. The operation will resume with MAXDOP value %d.
- 10668 — The %S_MSG option is not supported for creating an index on a heap.
- 10669 — The %S_MSG option is not supported for creating a nonclustered index on clustered columnstore index.
- 10670 — Resumable index creation for %S_MSG '%.*ls' failed because the index includes a large object column '%.*ls'.
- 10671 — The %S_MSG option is not supported for creating a filtered index.
- 10672 — The %S_MSG option is not supported for creating a clustered index on a relation that has a filtered index.
- 10673 — Cannot resume index creation due to incorrect persisted state found. Please ABORT the operation and try again.
- 10674 — The %S_MSG option is not supported for creating a clustered index on a table containing nonclustered columnstore index.
- 10675 — Internal Query Processor Error: The query processor could not produce a query plan. The RESUMABLE option is not supported for this index build. Remove…
- 10676 — The resumable index '%.*ls' on object '%.*ls' is being auto aborted because it has remained paused for more than %d minutes. Refer to the PAUSED_RESUM…
- 10677 — The index '%.*ls' on object '%.*ls' was rebuilt with valid data rows but null stats were found.
- 10678 — Could not create columnstore index '%.*ls' on table '%.*ls' since column '%.*ls' is computed column which is not supported in the ORDER list.
- 10679 — Online columnstore index is not supported with ORDER clause.
- 10680 — ALTER INDEX ALL '%S_MSG' failed. There is no pending resumable index operation on '%.*ls'.
- 10681 — Cannot create a row of size %d which is greater than the allowable maximum row size of %d. Abort and retry the operation by specifying the RESUMABLE =…
- 10682 — Cannot convert the %S_MSG '%.*ls' to a relational index by using the DROP_EXISTING option.
- 10683 — Cannot create %S_MSG because %S_MSG already exists on the table.
- 10700 — The table-valued parameter "%.*ls" is READONLY and cannot be modified.
- 10701 — The READONLY option cannot be used in an EXECUTE or CREATE AGGREGATE statement.
- 10702 — The WITH CUBE and WITH ROLLUP options are not permitted with a ROLLUP, CUBE, or GROUPING SETS specification.
- 10703 — Too many grouping sets. The maximum number is %d.
- 10704 — To rethrow an error, a THROW statement must be used inside a CATCH block. Insert the THROW statement inside a CATCH block, or add error parameters to …
- 10705 — Subqueries are not allowed in the OUTPUT clause.
- 10706 — Too many expressions are specified in the GROUP BY clause. The maximum number is %d when grouping sets are supplied.
- 10707 — The CUBE() and ROLLUP() grouping constructs are not allowed in the current compatibility mode. They are only allowed in 100 mode or higher.
- 10708 — DEFAULT is not allowed on the right hand side of "%.*ls"
- 10709 — The number of columns for each row in a table value constructor must be the same.
- 10710 — An action of type '%S_MSG' is not allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement.
- 10711 — An action of type 'INSERT' is not allowed in the '%S_MSG' clause of a MERGE statement.
- 10712 — The pseudocolumn '%.*ls' cannot be part of an index.
- 10713 — A MERGE statement must be terminated by a semi-colon (;).
- 10714 — An action of type '%S_MSG' cannot appear more than once in a '%S_MSG' clause of a MERGE statement.
- 10715 — '%.*ls' is not a valid hint.
- 10716 — A nested INSERT, UPDATE, DELETE, or MERGE statement must have an OUTPUT clause.
- 10717 — The %S_MSG clause is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
- 10718 — Query hints are not allowed in nested INSERT, UPDATE, DELETE, or MERGE statements.
- 10719 — Foreign key relationships from a memory optimized table with DURABILITY set to SCHEMA_AND_DATA to a memory optimized table with DURABILITY set to SCHE…
- 10720 — An OUTPUT INTO clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
- 10721 — The WHERE CURRENT OF clause is not allowed in a nested INSERT, UPDATE, DELETE, or MERGE statement.
- 10722 — The DISTINCT keyword is not allowed when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
- 10723 — In a MERGE statement, a variable cannot be set to a column and expression in the same assignment in the SET clause of an UPDATE action. Assignments of…
- 10724 — The FORCESEEK hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
- 10725 — Cannot use the VARYING option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.
- 10726 — User defined aggregates do not support default parameters.
- 10727 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a JOIN or APPLY operator.
- 10728 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed as the table source of a PIVOT or UNPIVOT operator.
- 10729 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in a SELECT statement that is not the immediate source of rows for an INSERT statem…
- 10730 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.
- 10731 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed inside another nested INSERT, UPDATE, DELETE, or MERGE statement.
- 10732 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed on either side of a UNION, INTERSECT, or EXCEPT operator.
- 10733 — A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the USING clause of a MERGE statement.
- 10734 — Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator.
- 10735 — Incorrect WHERE clause for filtered %S_MSG '%.*ls' on table '%.*ls'.
- 10736 — A full-text stoplist statement must be terminated by a semi-colon (;).
- 10737 — In an ALTER TABLE REBUILD or ALTER INDEX REBUILD statement, when a partition is specified in a DATA_COMPRESSION clause, PARTITION=ALL must be specifie…
- 10738 — The number of row value expressions in the INSERT statement exceeds the maximum allowed number of %d row values.
- 10739 — The insert column list used in the MERGE statement cannot contain multi-part identifiers. Use single part identifiers instead.
- 10740 — A search property list statement must end with a semicolon (;).
- 10741 — A TOP can not be used in the same query or sub-query as a OFFSET.
- 10742 — The offset specified in a OFFSET clause may not be negative.
- 10743 — The number of rows provided for a OFFSET clause must be an integer.
- 10744 — The number of rows provided for a FETCH clause must be greater then zero.
- 10745 — The FORCESCAN hint is not allowed for target tables of INSERT, UPDATE, or DELETE statements.
- 10746 — The FORCESCAN hint is specified simultaneously with the FORCESEEK hint. Remove one of the hints and resubmit the query.
- 10747 — The parameterized FORCESEEK hint cannot be simultaneously used with INDEX hints or a non-parameterized FORCESEEK hint on the same object. Use either I…
- 10748 — There are multiple FORCESEEK hints specified on the same table or view. Remove the extra FORCESEEK hints and resubmit the query.
- 10749 — The FORCESEEK hint cannot be used with index 0. Correct the index provided to the FORCESEEK hint and resubmit the query.
- 10750 — The FORCESCAN hint cannot be used with more than one INDEX hint. Remove the extra INDEX hints and resubmit the query.
- 10751 — The ORDER BY in WITHIN GROUP clause of '%.*ls' function must have exactly one expression.
- 10752 — The function '%.*ls' may not have a window frame.
- 10753 — The function '%.*ls' must have an OVER clause.
- 10754 — The function '%.*ls' must have a WITHIN GROUP clause.
- 10755 — The function '%.*ls' takes between %d and %d arguments.
- 10756 — Window frame with ROWS or RANGE must have an ORDER BY clause.
- 10757 — The function '%.*ls' may not have a WITHIN GROUP clause.
- 10758 — The function '%.*ls' may not have ORDER BY in OVER clause.
- 10759 — Use of DISTINCT is not allowed with the OVER clause.
- 10760 — Scale argument is not valid. Valid expressions for data type %ls scale argument are integer constants and integer constant expressions.
- 10761 — Invalid data type %.*ls in function %.*ls.
- 10762 — The %.*ls function is not allowed in the current compatibility mode. It is only allowed in 110 mode or higher.
- 10763 — GROUP BY clause can only contain one query hint. Remove the extra hints and re-run the query.
- 10764 — Number of grouping columns in the query exceeded maximum number allowed. SQL Server allows 64k grouping columns. Reduce number of grouping columns and…
- 10765 — DISTRIBUTED_AGG and CENTRAL_AGG hints cannot be used with a CUBE or ROLLUP clause. Modify the query and re-run it.
- 10766 — CENTRAL_AGG must be specified after all columns in the GROUP BY clause. Modify the query and re-run it.
- 10767 — DISTRIBUTED_AGG hint cannot be used when the GROUP BY clause contains the same column more than once. Modify the query and re-run it.
- 10768 — LABEL hint can only be used one time in the query. Modify the query and re-run it.
- 10769 — SET options are not supported inside ATOMIC blocks.
- 10770 — The SERVER option and one of CREDENTIAL or FEDERATED_SERVICE_ACCOUNT = ON options are required for setting REMOTE_DATA_ARCHIVE on a database.
- 10771 — The CREDENTIAL option cannot be used with the FEDERATED_SERVICE_ACCOUNT = ON option.
- 10772 — There are multiple REMOTE_DATA_ARCHIVE_OVERRIDE hints specified on the same table or view reference. Remove the extra REMOTE_DATA_ARCHIVE_OVERRIDE hin…
- 10773 — The REMOTE_DATA_ARCHIVE_OVERRIDE hint is not applicable to object '%.*ls' because it is not a table with REMOTE_DATA_ARCHIVE enabled. Remove the REMOT…
- 10774 — Incorrect WHERE clause for filtered index.
- 10775 — Object '%.*ls' is not a memory optimized table or a natively compiled inline table-valued function and cannot be accessed from a natively compiled mod…
- 10776 — Triggers on non-memory optimized tables cannot use WITH NATIVE_COMPILATION.
- 10777 — Triggers on memory-optimized tables must use WITH NATIVE_COMPILATION.
- 10778 — Foreign key relationships between memory optimized tables and non-memory optimized tables are not supported.
- 10779 — The durability option 'schema_only' is supported only with memory optimized tables.
- 10780 — There is no primary key in the referenced table '%.*ls' that matches the referencing column list in the foreign key '%.*ls'. Foreign keys in memory-op…
- 10781 — Querytraceon %d and optimizer hint '%.*ls' specify conflicting behaviors. Remove one of them and rerun the query.
- 10782 — BEGIN ATOMIC is supported only in natively compiled modules.
- 10783 — The body of a natively compiled module must be an ATOMIC block.
- 10784 — The WITH clause of BEGIN ATOMIC statement must specify a value for the option '%ls'.
- 10785 — The %S_MSG '%ls' is supported only with %S_MSG.
- 10786 — The ALTER AVAILABILITY GROUP command failed because it contained multiple MODIFY REPLICA options: %ls. Enter a separate ALTER AVAILABILITY GROUP ... M…
- 10787 — The REPEATABLEREAD and SERIALIZABLE hints are not permitted on Hekaton tables with columnstore indexes.
- 10788 — The option '%ls' is not supported with table types.
- 10789 — The option '%ls' must be specified for index '%.*ls' on table '%.*ls'. It is required for hash indexes.
- 10790 — The option '%ls' can be specified only for hash indexes.
- 10791 — Hash indexes are permitted only in memory optimized tables.
- 10792 — When used in a natively compiled module, the function '%.*ls' cannot appear outside of a catch block.
- 10793 — Both an index and a PRIMARY KEY constraint have been defined inline, with the definition of column '%.*ls', table '%.*ls'. Defining both an index and …
- 10794 — The %S_MSG '%ls' is not supported with %S_MSG.
- 10795 — The variable '%.*ls' was declared as not null, and must be declared with an initial value.
- 10796 — The SCHEMABINDING option is supported only for natively compiled modules, and is required for those modules.
- 10797 — Only one MEMORY_OPTIMIZED_DATA filegroup is allowed per database.
- 10798 — This is not a valid data compression setting for this object. It can only be used with columnstore indexes. Please choose NONE, PAGE, or ROW compressi…
- 10799 — This is not a valid data compression setting for a columnstore index. Please choose COLUMNSTORE or COLUMNSTORE_ARCHIVE compression.
- 10800 — The listener for the WSFC resource '%.*ls' failed to start, and returned error code %d, '%.*ls'. For more information about this error code, see "Syst…
- 10801 — Failed to stop the listener for Windows Failover Cluster resource '%.*ls'. Error: %d. %.*ls
- 10802 — Failed to enqueue a task to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a S…
- 10900 — Failed to configure resource governor during startup. Check SQL Server error log for specific error messages or check the consistency of master databa…
- 10901 — User does not have permission to alter the resource governor configuration.
- 10902 — User-defined function '%s' does not exist in master database, or the user does not have permission to access it.
- 10903 — The specified schema name '%.*ls' for classifier user-defined function either does not exist, or the user does not have permission to use it.
- 10904 — Resource governor configuration failed. There are active sessions in workload groups being dropped or moved to different resource pools. Disconnect al…
- 10905 — Could not complete resource governor configuration because there is not enough memory. Reduce the server load or try the operation on a dedicated admi…
- 10906 — The object '%.*ls'.'%.*ls' is not a valid resource governor classifier user-defined function. A valid classifier user-defined function must be schema-…
- 10907 — Attribute '%.*ls' with value of %u is greater than attribute '%.*ls' with value of %u.
- 10908 — Attribute '%.*ls' with value of %u is less than attribute '%.*ls' with value of %u.
- 10909 — The resource pool cannot be created. The maximum number of resource pools cannot exceed current limit of %u including predefined resource pools.
- 10910 — The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all resource pools on scheduler %u to exceed 100 …
- 10911 — Requested operation cannot be performed because the resource pool '%.*ls' does not exist.
- 10912 — The operation could not be completed. Dropping predefined %S_MSG is not allowed.
- 10913 — Users are not allowed to %S_MSG the workload group '%.*ls' in the '%.*ls' resource pool.
- 10914 — The name of the %S_MSG '%.*ls' cannot begin with # of ##.
- 10915 — The operation could not be completed. Altering '%.*ls' %S_MSG is not allowed.
- 10916 — Cannot drop resource pool '%.*ls' because it contains workload group '%.*ls'. Drop or remove all workload groups using this resource pool before dropp…
- 10917 — ALTER WORKLOAD GROUP failed. Either a 'WITH' or 'USING' clause must be specified.
- 10918 — Cannot create %S_MSG '%.*ls' because it already exists.
- 10919 — An error occurred while reading the resource governor configuration from master database. Check the integrity of master database or contact the system…
- 10920 — Cannot %S_MSG user-defined function '%.*ls'. It is being used as a resource governor classifier.
- 10921 — The '%.*ls' %S_MSG cannot be moved out of '%.*ls' %S_MSG.
- 10922 — %ls failed. Rerun the statement.
- 10923 — %ls failed. The resource governor is not available in this edition of SQL Server. You can manipulate resource governor metadata but you will not be ab…
- 10924 — The pool affinity range is invalid. The lower bound %d must be less than the upper bound %d.
- 10925 — A %S_MSG value was specified more than one time in the pool affinity range list.
- 10926 — The %S_MSG range that specifies %S_MSG %d includes at least one %S_MSG that is not available to the current instance. The maximum %S_MSG number that i…
- 10927 — The operation could not be completed. The specified '%.*ls' value, %u, causes the sum of minimums on all workload groups using resource pool '%.*ls' t…
- 10928 — Resource ID : %d. The %ls limit for the database is %d and has been reached. See ' http://go.microsoft.com/fwlink/?LinkId=267637 ' for assistance.
- 10929 — Resource ID : %d. The %ls minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently …
- 10930 — The service is currently too busy. Please try again later.
- 10931 — Cannot drop resource pool '%.*ls' because it is bound to a database. Remove all bindings to this resource pool before dropping it.
- 10932 — Resource governor configuration failed, because there is an active database in the resource pool being dropped. Take the database offline and try agai…
- 10933 — A %S_MSG with id %d does not exist on this system. Use sys.dm_os_schedulers to locate valid %S_MSGs for this system.
- 10934 — Requested operation cannot be performed because the external resource pool '%.*ls' does not exist.
- 10935 — External resource pool does not allow more than one processor group.
- 10936 — Resource ID : %d. The %ls limit for the elastic pool is %d and has been reached. See ' http://go.microsoft.com/fwlink/?LinkId=267637 ' for assistance.
- 10937 — Default workload group does not allow to alter attribute '%.*ls'.
- 10938 — Contained Availability Group connections do not support Resource Governor DDL. Please retry using the instance connection.
- 10939 — The maximum number of user created workload groups is %d and has already been reached for this database.
- 10940 — Execute ALTER WORKLOAD GROUP [%.*ls] ON DATABASE ... before creating the first database-scoped workload group.
- 10941 — The name '%.*ls' is invalid because it starts with a reserved prefix '%.*ls'.
- 10942 — Request failed because it reached the MAX_WORKERS_PERCENT limit (%d workers) for the workload group '%.*ls' in database '%.*ls'.
- 10943 — Request failed because it reached the MAX_SESSIONS limit (%d sessions) for the workload group '%.*ls' in database '%.*ls'.
- 10944 — ALTER WORKLOAD GROUP failed. The 'WITH' clause must be specified.
- 10945 — Resource governor reconfiguration failed because database resource configuration is not ready. This is a transient condition that can occur during dat…
- 10946 — Cannot disable resource governor because database resource configuration is not ready. This is a transient condition that can occur during database st…
- 10947 — The resource governor is not supported for databases using the DTU purchasing model.
- 10961 — The request has been aborted because its CPU usage exceeds the maximum configured limit for the workload group.
- 10981 — Resource governor reconfiguration succeeded.
- 10982 — Failed to run resource governor classifier user-defined function '%.*ls'. Last error %u, state %u. See previous errors in SQL Server error log from se…
- 10983 — Resource governor '%ls' operation was canceled by user.
- 10984 — Resource governor reconfiguration failed.
- 10985 — Resource governor reconfiguration encountered an issue (HRESULT code : 0x%lx, reason: %ls), while sending active external resource pool ids to launchp…
- 10986 — Load resource governor configuration from replicated master failed to complete.
- 10987 — Load resource governor configuration from replicated master failed to start. Unable to submit async task.
- 10988 — The %ls limit for the workspace is %d and has been reached.
- 10989 — %ls_MAX_TEMPDB_DATA_PERCENT is not in effect because tempdb configuration requirements aren't met. For more information, see https://go.microsoft.com/…
- 10990 — The current tempdb space consumption by workload group '%s' exceeds the new configured limit. Increase the configured limit or reduce tempdb space con…
- 10991 — The specified MAX_IOPS_PERCENT value %d percent would reduce the IOPS limit below the supported minimum of %d IOPS. Resource governor set the effectiv…
- 10992 — Successfully disabled resource governor.
- 10993 — Failed to disable resource governor.
- 10994 — The specified MAX_WORKERS_PERCENT value would reduce the worker limit below the supported minimum of %d workers. Resource governor set the effective w…
- 11000 — Unknown status code for this column.
- 11001 — Non-NULL value successfully returned.
- 11002 — Deferred accessor validation occurred. Invalid binding for this column.
- 11003 — Could not convert the data value due to reasons other than sign mismatch or overflow.
- 11004 — Successfully returned a NULL value.
- 11005 — Successfully returned a truncated value.
- 11006 — Could not convert the data type because of a sign mismatch.
- 11007 — Conversion failed because the data value overflowed the data type used by the provider.
- 11008 — The provider cannot allocate memory or open another storage object on this column.
- 11009 — The provider cannot determine the value for this column.
- 11010 — The user did not have permission to write to the column.
- 11011 — The data value violated the integrity constraints for the column.
- 11012 — The data value violated the schema for the column.
- 11013 — The column had a bad status.
- 11014 — The column used the default value.
- 11015 — The column was skipped when setting data.
- 11031 — The row was successfully deleted.
- 11032 — The table was in immediate-update mode, and deleting a single row caused more than one row to be deleted in the data source.
- 11033 — The row was released even though it had a pending change.
- 11034 — Deletion of the row was canceled during notification.
- 11036 — The rowset was using optimistic concurrency and the value of a column has been changed after the containing row was last fetched or resynchronized.
- 11037 — The row has a pending delete or the deletion had been transmitted to the data source.
- 11038 — The row is a pending insert row.
- 11039 — DBPROP_CHANGEINSERTEDROWS was VARIANT_FALSE and the insertion for the row has been transmitted to the data source.
- 11040 — Deleting the row violated the integrity constraints for the column or table.
- 11041 — The row handle was invalid or was a row handle to which the current thread does not have access rights.
- 11042 — Deleting the row would exceed the limit for pending changes specified by the rowset property DBPROP_MAXPENDINGROWS.
- 11043 — The row has a storage object open.
- 11044 — The provider ran out of memory and could not fetch the row.
- 11045 — User did not have sufficient permission to delete the row.
- 11046 — The table was in immediate-update mode and the row was not deleted due to reaching a limit on the server, such as query execution timing out.
- 11047 — Updating did not meet the schema requirements.
- 11048 — There was a recoverable, provider-specific error, such as an RPC failure.
- 11100 — The provider indicates that conflicts occurred with other properties or requirements.
- 11101 — Could not obtain an interface required for text, ntext, or image access.
- 11102 — The provider could not support a required row lookup interface.
- 11103 — The provider could not support an interface required for the UPDATE/DELETE/INSERT statements.
- 11104 — The provider could not support insertion on this table.
- 11105 — The provider could not support updates on this table.
- 11106 — The provider could not support deletion on this table.
- 11107 — The provider could not support a row lookup position.
- 11108 — The provider could not support a required property.
- 11109 — The provider does not support an index scan on this data source.
- 11201 — This message could not be delivered because the FROM service name is missing. The message origin is: '%ls'.
- 11202 — This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
- 11203 — This message has been dropped because the FROM broker instance is missing. The message origin is '%ls'.
- 11204 — This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: "%.*ls". Message origin: "%ls".
- 11205 — This message has been dropped because the TO service name is missing. The message origin is "%ls".
- 11206 — This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: "%.*ls". Message origin: "%ls".
- 11207 — This message has been dropped because the service contract name is missing. The message origin is "%ls".
- 11208 — This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name "%.*ls". Message origin: "%ls".
- 11209 — This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: '%ls'.
- 11210 — This message has been dropped because the TO service could not be found. Service name: "%.*ls". Message origin: "%ls".
- 11211 — This message has been dropped because the user does not have permission to access the target database. Database ID: %d. Message origin: "%ls"…
- 11212 — This message could not be delivered because the conversation endpoint has already been closed.
- 11213 — This message could not be delivered because this is not the first message in the conversation.
- 11214 — This message could not be delivered because the '%.*ls' contract could not be found or the service does not accept conversations for the contract.
- 11215 — This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: '%.*l…
- 11216 — This message could not be delivered because there is already another task processing this message.
- 11217 — This message could not be delivered because it is out of sequence with respect to the conversation. Conversation receive sequence number: %I64d, Messa…
- 11218 — This message could not be delivered because it is a duplicate.
- 11219 — This message could not be delivered because the destination queue has been disabled. Queue ID: %d.
- 11220 — This message could not be delivered because the TO broker instance is missing.
- 11221 — This message could not be delivered because there is an inconsistency in the message header.
- 11222 — This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Servic…
- 11223 — This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Message ser…
- 11224 — This message could not be delivered because another instance of this service program has already started conversing with this endpoint.
- 11225 — This message could not be delivered because the message type name could not be found. Message type name: '%.*ls'.
- 11226 — This message could not be delivered because the message type is not part of the service contract. Message type name: '%.*ls'. Service contract name: '…
- 11227 — This message could not be delivered because the initiator service has sent a message with a message type that can only be sent by the target. Message …
- 11228 — This message could not be delivered because the target service has sent a message with a message type that can only be sent by the initiator. Message …
- 11229 — This message could not be delivered because the security context could not be retrieved.
- 11230 — This message could not be delivered because the message could not be decrypted and validated.
- 11231 — This message could not be delivered because the conversation endpoint is not secured, however the message is secured.
- 11232 — This message could not be delivered because the conversation endpoint is secured, however the message is not secured.
- 11233 — This message has been dropped because the session key of the conversation endpoint does not match that of the message.
- 11234 — This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls.
- 11235 — Received a malformed message. The binary message class (%d:%d) is not defined. This may indicate network problems or that another application is conne…
- 11236 — A corrupted message has been received. The binary header size of %d is expected, however the header size received was %d.
- 11237 — A %S_MSG message could not be processed due to insufficient memory. The message was dropped.
- 11238 — A corrupted message has been received. The private variable data segment is malformed.
- 11239 — A corrupted message has been received. The private variable data segment extends beyond the length of the message.
- 11240 — A corrupted message has been received. The binary message preamble is malformed.
- 11241 — A corrupted message has been received. The conversation security version number is not %d.%d.
- 11242 — A corrupted message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found…
- 11243 — A corrupted message has been received. The public variable data element (%d) has been duplicated in this message.