Web.QHMIT.com

SQL Server System Errors: 28000 - 28999

List of error messages between 28000 and 28999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text
28000160The decrypted session key has an unexpected size.
28001160A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28002160Cannot start service broker manager. Operating system error: %ls.
28003160An internal service broker error occurred. Operating system error: %ls.
28004160This message could not be delivered because the '%S_MSG' action cannot be performed in the '%.*ls' state.
28005160An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls
28006140User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission.
28007160A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28008160The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}' is invalid.
28009160The crypto API has detected bad data while trying to perform a decryption operation.
28010160This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d.
28011160This message could not be delivered because its %S_MSG has expired or is invalid.
28012160The Service Broker in the target database is unavailable: '%S_MSG'.
28013160The service broker is administratively disabled.
28014160The database is in read-only mode.
28015160The database is in single-user mode.
28016160The message has been dropped because the service broker in the target database is unavailable: '%S_MSG'.
28017160The message has been dropped because the target service broker is unreachable.
28018160The database is a replica of a mirrored database.
28019160System error %d occurred while creating a new message element GUID for this forwarded message.
28020160Could not create user token for user %d in database %d.
28021160One or more messages could not be delivered to the local service targeted by this dialog.
28022100An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.
28023100An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.
28024161The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid.
28025161The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.
28026100Connection handshake failed. Not enough memory available. State %d.
28027100Connection handshake failed. There is no compatible %S_MSG. State %d.
28028100Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.
28029100Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.
28030100Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.
28031100Connection handshake failed. An OS call failed: (%x) %ls. State %d.
28032100A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.
28033100A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d.
28034100Connection handshake failed. The login '%.*ls' does not have CONNECT permission on the endpoint. State %d.
28035100Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
28036100Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d.
28037100Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the operating system error log may contain entries related to this error. State %d.
28038100Connection handshake failed. The handshake verification failed. State %d.
28039100Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.
28040100A corrupted message has been received. The adjacent error message header is invalid.
28041160A corrupted message has been received. The encrypted payload offset is invalid (%d).
28042160A corrupted message has been received. The arbitration request header is invalid.
28043160A corrupted message has been received. The arbitration response header is invalid.
28044160A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28045100Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d.
28046101%S_MSG Login succeeded for user '%.*ls'. Authentication mode: %.*ls. %.*ls
28047101%S_MSG login attempt failed with error: '%.*ls'. %.*ls
28048101%S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls
28049160A corrupted message has been received. The proxy connect message header is invalid.
28050100The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
28051100Could not save a dialog session key. A master key is required in the database to save the session key.
28052160Cannot decrypt session key while regenerating master key with FORCE option.
28053160Service Broker could not upgrade conversation session keys in database '%.*ls' to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker.
28054160Service Broker needs to access the master key in the database '%.*ls'. Error code:%d. The master key has to exist and the service master key encryption is required.
28055160The certificate '%.*ls' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
28056160This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: '%.*ls'.
28057100Service Broker in database '%.*ls' has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.
28058160Service Broker could not upgrade this conversation during a database upgrade operation.
28059160Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
28060160The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
28061160A corrupted message has been received. The adjacent message integrity check signature could not be validated.
28062160A corrupted message has been received. The signed dialog message header is invalid.
28063160A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28064160A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28065160A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28066160A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28067160A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28068160A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Message sequence number: %I64d.
28069161Unexpected session key when encrypting a dialog message.
28070100Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
28071100The received message could not be forwarded onto another connection. State %d.
28072160A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.
28073160An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
28074160Service Broker could not upgrade conversation with conversation_handle '%ls'. Use END CONVERSATION ... WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE ... SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE ... SET NEW_BROKER to delete all conversations in this database.
28075100The broker in the sender's database is in single user mode. Messages cannot be delivered while in single user mode.
28076100Could not query the FIPS compliance mode flag from registry. Error %ls.
28077100%S_MSG endpoint is running in FIPS compliance mode. This is an informational message only. No user action is required.
28078100The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
28079100Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
28080100Connection handshake failed. The %S_MSG endpoint is not configured. State %d.
28081100Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
28082100Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
28083160The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys.
28084100An error occurred in Service Broker internal activation while trying to scan the user queue '%ls' for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required.
28085160The activated task was ended because the associated queue was dropped.
28086160The activated task was ended because either the queue or activation was disabled.
28087160The activated task was aborted because the invoked stored procedure '%ls' did not execute RECEIVE.
28088160The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possible output from the activation stored procedure.
28089160The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas.
28090160An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available.
28091100 Starting endpoint for %S_MSG with no authentication is not supported.
28092100Error updating proxy settings
28098100A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d.
28099100During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state.
28101160User '%.*ls%.*ls' does not have permission to debug the requested client connection.
28102160Batch execution is terminated because of debugger request.
28380160Index with the specified Id (%d) in the clone address syntax cannot be found.
28381150Lock hints other than READCOMMITTED and REPEATABLEREAD are not allowed when clone address syntax is used.
28382160A correlation name must be specified for the clone address rowset function.
28383160Clone address hint is missing on the tables '%.*ls'.
28389160Target with the clone address: IdxId %d, DbFragId %d, RowsetId 0x%016I64X is not found at brick %d. Possibly caused by invalid IDs or by an inconsistency between the IDs and the fragmentation function.
28390160Invalid clone address syntax: IdxId %d, DbFragId %d, RowsetId 0x%016I64X.
28391160The use of internal Clone Addressability syntax extensions is incompatible with the feature '%.*ls'.
28392160The internal Clone Addressability syntax extensions is only allowed on user tables. The target (in the FROM claus) is '%.*ls'.
28393160The index (id = %d) selected in the plan is inconsistent with the index specified in the clone address syntax (id = %d).
28394160The query plan uses the feature '%.*ls' which is unexpected with clone address syntax.
28395160Multiple conflicting Ids are given on '%.*ls': old value = %d, new value = %d.
28396160Invalid clone address syntax: IdxId %d, DbFragId %d, RowsetId 0x%016I64X. (If you see this error, it implies there is a bug in the code.)
28397160Unable to activate query fragment.
28401160Feature or option '%ls' is not available. Please consult Books Online for more information on this feature or option.
28402160Feature or option '%ls' is not yet implemented. Please consult Books Online for more information on this feature or option.
28403101Starting SQL Server instance as a MatrixDB instance.
28404101Exception in exception handling service thread.
28405171During error handling, a second error was raised, causing an unrecoverable failure.
28406101Error %d, Severity %d, State %d was raised on a subtask before it was registered, therefore the exception could not be relayed to the main thread.
28407160Entry fetch from brick %d failed to find entry in distributed cache %d on brick %d.
28408160This feature or option %ls is available only when an instance of SQL Server is installed as a MatrixDB. For more information about this feature or option, see SQL Server Books Online.
28410100Warning: The lock_escalation option 'TABLE' is not available, and 'AUTO' option will be used instead. Please consult Books Online for more information on this feature or option.
28502110The specified object Id is not valid.
28503110The specified index Id is not valid.
28504110The specified partition number is not valid.
28506110Incorrect number of keys was specified. Must specify at least first %d key columns
28553161Operation is not supported if all bricks are not online.
28554161Data Virtualization Manager not found.
28555101DVM failed to handle matrix reconfiguration. {error_code: %d, state: %d}
28601160The Transaction Coordination Manager has encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, which may prevent further transaction processing. Examine previously logged messages to figure out the cause for this unexpected failure. Depending on the failure condition, the Transaction Coordination Manager might be restarted automatically.
28602160The transaction is aborted because the transaction agent is shutting down.
28603101Transaction agent is shutting down because shutdown request was received from the manager.
28604101Transaction Coordination Manager is starting up. This is an informational message only. No user action is required.
28605101Transaction Coordination Manager is inactive. This is an informational message only. No user action is required.
28606101Transaction Coordination Manager is active with %016I64x as the starting AGE. This is an informational message only. No user action is required.
28607160TCM %.*ls has received an out of order message from brick id %d and has to be stopped. Based on the state of the system it may restart and re-synchronize automatically. Typical causes for missed messages are temporary network errors or out of memory conditions. Look for earlier messages in the log which should contain additional information.
28608160Federated transaction could not be started at this time because the TCM Agent is not in a state, which allows new transactions to begin. The TCM Agent is currently in state: %d. The most common reason for this is that the system is being shutdown. Previous messages in the log should contain additional information.
28609160Matrix transaction operation is not allowed because the transaction doesn't allow forward progress, the transaction will be rolled back.
28610160Matrix transaction couldn't commit because the task is aborted. The task is aborted either because of cancel instruction from client application, or because one or more transaction paritipant went offline.
28611180The request is aborted because the transaction has been aborted by Matrix Transaction Coordination Manager. This is mostly caused by one or more transaction particpant brick went offline.
28612200An error occurred while accessing Transaction Coordination Manager metadata. Could not persist AGE %016I64x.
28613101Transaction Coordination Agent is active. This is an informational message only. No user action is required.
28614160TCM manager has received a request for re-synchronization from brick id %d and will now restart. Typical causes where restart is necessary are temporary network errors or out of memory conditions. Look for earlier messages in the log on the offending brick for more information.
28615200The request has performed an operation that is disallowed on a remote branch of a transaction
28701160Request aborted due to communication errors: an attempt was made to use channel %d.%d.%I64u in the closed state.
28702160Request aborted due to communication errors: incoming message format violation.
28703160Request aborted due to communication errors: no enabled channel maps for component %d found.
28704160Request aborted due to communication errors: unable to allocate new message for the brick %d. Error code %d.
28705160Request aborted due to communication errors: unable to complete send operation for the pipeline %hs. Error code %d.
28706100Next message reported have originated on brick %d.
28707200Brick was unable to communicate with configuration manager and will be disconnected. See previous errors for the details.
28708160Failure encountered due to Matrix configuration change: a brick was evicted.
28709160Dispatcher was unable to create new thread.
28710160Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent but there were no messages received on other side.
28711160Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent at age %d (current age and bytes sent are %I64d and %I64d) but receive side has processed only %I64d at age %d.
28712160Unable to start expiration manager dispatch thread. Result code %d.
28713160Communication subsystem failed to process user abort request. Error Number: %d; State: %d.
28714160Request aborted due to communication errors: an attempt was made to communicate with Brick %d which is no longer online or have been reconfigured.
28715100Execution of the request was aborted on remote brick.
28716160Request aborted due to communication errors: too many concurrent operations.
28717160Request aborted due to communication errors: communication subsystem is shutting down or initialization not complete yet.
28718160Request aborted due to communication errors: pipeline %hs received message (classId %d, sequenceId %d) from the expired age %d (last acceptable age %d).
28719160Request aborted due to Fabric errors: unable to enqueue a task for workspace 0x%I64x.
28720160Mci subsystem failed to start with error %d.
28721160Mci subsystem failed to start channel %d with error %d
28722200Force close service was unable to communicate with configuration manager (brick %d) either due errors or timeout (%d milliseconds). Matrix is not functioning properly. Investigation is prudent.
28723160Brick was shutdown by administrator request
28724160Channel close verification
28725200Unable to process cancellation request due to resource availability. Retrying...
28726200Unable to process activation data for a workspace.
28727200Unable to process incoming message due to resource availability.
28728160Request aborted due to communication errors: no channel maps of version %d for component %d found to create channel %I64u.
28729160Request aborted due to communication errors: a message have arrived for non-activated channel %I64u.
28901101Configuration manager agent has started enlistment protocol to join matrix
28902161Cannot create configuration manager agent enlistment thread.
28903161Configuration manager agent enlistment is retrying enlistment since brick <%d> eviction is pending.
28904161Configuration manager agent enlistment is sending join request message to manager.
28905161Configuration manager agent enlistment failed to receive reply from manager. See previous errors in error log.
28906161Configuration manager agent enlistment completed with '%s'.
28907161Configuration manager agent enlistment stopped.
28908161Configuration manager agent enlistment failed due to different enlistment protocol versions between manager and agent. Version received from manager: <%d>, Version expected: <%d>.
28909161Configuration manager agent enlistment failed due to receiving reply from invalid manager brick id <%d> .
28910161Sequence number mismatch of enlistment messages. Sequence number received: <%d>, Sequence number expected <%d>.
28911101Configuration manager agent enlistment succeeded. Manager accepted brick <%d> join request.
28912161Brick <%d> enlistment with configuration manager failed due to '%s' mismatch. Brick will be taken down.
28913161Configuration manager agent enlistment encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, that prevents the brick from joining the matrix. Brick will be taken down.
28914101Configuration manager agent enlistment: Brick <%d>, state <%d>.
28915161Configuration manager agent encountered error %d, state %d, severity %d while updating brick <%lu> incarnation to %I64u. Examine previous logged messages to determine cause of this error.
28916161Configuration manager agent encountered error %d, state %d, severity %d while updating state information. Examine previous logged messages to determine cause of this error.
28917101Configuration manager agent enlistment received join reply message.
28918161Brick cannot be started due to fatal error %d, state %d, severity %d during bootstrap. Examine previous logged messages to determine cause of this error.
28919161Duplicate brick id <%d> detected in configuration file.
28920161Configuration manager agent cannot send reported error to configuration manager due to error %d, state %d, severity %d.
28921161No configuration file specified.
28922161Configuration manager agent thread encountered fatal exception (error: %d severity: %d state: %d). This is a serious error and brick will be taken down. Examine previously logged messages to figure out the cause for this fatal failure.
28923161Configuration manager agent initialization failed. See previous errors in error log. This is a serious error condition and brick will be taken down.
28924161Configuration manager agent activation failed.
28925161Configuration manager agent quiesce failed.
28926161Configuration manager agent release failed.
28927161Configuration manager cannot create agent %d.
28929161Configuration manager agent cannot commit new roster.
28931161Configuration manager agent roster is corrupt.
28932161Configuration manager agent did not receive a shutdown channel map.
28933161Configuration manager agent could not perform brick down notification.
28934161Configuration manager agent could not perform brick up notification.
28935161Configuration manager agent is trying to start non-existing agent %d.
28936161Configuration manager agent start failed (Loc: %d).
28937161Configuration manager agent stop failed.
28938101Configuration manager agent has started.
28939101Configuration manager agent has shutdown.
28940161Configuration manager agent could not delete stale MCI sessions.
28942161Error reading configuration file. (Reason=%d).
28943161Error reading configuration file. Column %s not defined.
28944161Error reading configuration file. Host name or instance name cannot be empty (Reason: %d).
28945161Error reading configuration file. Invalid contents. (Reason=%d).
28946161Error reading matrix.xsd schema configuration file. (Reason=%d).
28947160Error reading configuration file. (line:%d, column:%d, Reason=%s).
28948161Error reading configuration file. Invalid placement brick id.
28949161Error during configuration check (Function:%s, result: 0x%08lx).
28950161Configuration manager agent cannot store metadata.
28951161Cannot update roster, brick id %d not part of roster.
28952161Configuration manager cannot initialize agent %d.
28953161Matrix agent %d has the invalid state %d.
28955161Cannot create roster memento.
28958161Error copying configuration. (Reason=%s).
28959161Cannot commit metadata change for brick id %d.
28960161Error: Cannot read <%s> node of configuration file.
28961161Error: invalid configuration file, no bricks defined.
28962161Error: Invalid value for manager name %s specified.
28963161Error: Invalid value for manager role %s specified.
28964161Error: Cannot create dom object for writing of XML configuration file (Reason %d).
28968101Starting communication infrastructure for communication between configuration manager and agent
28969101Configuration manager agent shutting down...
28970161Error: cannot update matrix metadata (Loc: %d).
28972161Error: cannot determine host name.
28973161Configuration manager agent cannot create notification publisher.
28974161Configuration manager agent cannot create notification service.
28975161Brick not configured correctly, corrupt configuration file.
28976161Configuration manager agent is ignoring stale message from manager brick %d due to '%s' mismatch. Expected %I64u but received %I64u
28977161Configuration manager agent is performing '%s' '%s' operation.
28978161Configuration manager agent cannot '%s' '%s'. Examine previous logged messages to determine cause of this error. This is a fatal error affecting system functionality and brick will be taken down.
28979161Configuration manager agent cannot '%s' '%s' due to invalid state '%s'. This is a fatal error affecting system functionality and brick will be taken down.
28980161Error writing brick simulator state file. (Reason=%s).