错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 14 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 28014 — The database is in read-only mode.
- 28015 — The database is in single-user mode.
- 28016 — The message has been dropped because the service broker in the target database is unavailable: '%S_MSG'.
- 28017 — The message has been dropped because the target service broker is unreachable.
- 28018 — The database is a replica of a mirrored database.
- 28019 — System error %d occurred while creating a new message element GUID for this forwarded message.
- 28020 — Could not create user token for user %d in database %d.
- 28021 — One or more messages could not be delivered to the local service targeted by this dialog.
- 28022 — An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.
- 28023 — An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.
- 28024 — The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certifica…
- 28025 — The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.
- 28026 — Connection handshake failed. Not enough memory available. State %d.
- 28027 — Connection handshake failed. There is no compatible %S_MSG. State %d.
- 28028 — Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.
- 28029 — Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.
- 28030 — Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.
- 28031 — Connection handshake failed. An OS call failed: (%x) %ls. State %d.
- 28032 — A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be clos…
- 28033 — A 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…
- 28034 — Connection handshake failed. The login '%.*ls' does not have CONNECT permission on the endpoint. State %d.
- 28035 — Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
- 28036 — Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata i…
- 28037 — Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the op…
- 28038 — Connection handshake failed. The handshake verification failed. State %d.
- 28039 — Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.
- 28040 — A corrupted message has been received. The adjacent error message header is invalid.
- 28041 — A corrupted message has been received. The encrypted payload offset is invalid (%d).
- 28042 — A corrupted message has been received. The arbitration request header is invalid.
- 28043 — A corrupted message has been received. The arbitration response header is invalid.
- 28044 — A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message …
- 28045 — Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State…
- 28046 — %S_MSG Login succeeded for user '%.*ls'. Authentication mode: %.*ls. %.*ls
- 28047 — %S_MSG login attempt failed with error: '%.*ls'. %.*ls
- 28048 — %S_MSG login attempt by user '%.*ls' failed with error: '%.*ls'. %.*ls
- 28049 — A corrupted message has been received. The proxy connect message header is invalid.
- 28050 — The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
- 28051 — Could not save a dialog session key. A master key is required in the database to save the session key.
- 28052 — Cannot decrypt session key while regenerating master key with FORCE option.
- 28053 — Service Broker could not upgrade conversation session keys in database '%.*ls' to encrypted format (Error: %d). The Service Broker in this database wa…
- 28054 — Service 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 encryptio…
- 28055 — The certificate '%.*ls' is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and c…
- 28056 — This 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: '%.*l…
- 28057 — Service Broker in database '%.*ls' has a pending conversation upgrade operation. A database master key in the database is required for this operation …
- 28058 — Service Broker could not upgrade this conversation during a database upgrade operation.
- 28059 — Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
- 28060 — The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
- 28061 — A corrupted message has been received. The adjacent message integrity check signature could not be validated.
- 28062 — A corrupted message has been received. The signed dialog message header is invalid.
- 28063 — A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID '%.*ls…
- 28064 — A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversat…
- 28065 — A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initi…
- 28066 — A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID '%.*ls', Initi…
- 28067 — A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message …
- 28068 — A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID '%.*ls', Ini…
- 28069 — Unexpected session key when encrypting a dialog message.
- 28070 — Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
- 28071 — The received message could not be forwarded onto another connection. State %d.
- 28072 — A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i second…
- 28073 — An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
- 28074 — Service Broker could not upgrade conversation with conversation_handle '%ls'. Use END CONVERSATION ... WITH CLEANUP to delete this conversation, then …
- 28075 — The broker in the sender's database is in single user mode. Messages cannot be delivered while in single user mode.
- 28076 — Could not query the FIPS compliance mode flag from registry. Error %ls.
- 28077 — %S_MSG endpoint is running in FIPS compliance mode. This is an informational message only. No user action is required.
- 28078 — The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
- 28079 — Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
- 28080 — Connection handshake failed. The %S_MSG endpoint is not configured. State %d.
- 28081 — Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
- 28082 — Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
- 28083 — The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associ…
- 28084 — An 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 …
- 28085 — The activated task was ended because the associated queue was dropped.
- 28086 — The activated task was ended because either the queue or activation was disabled.
- 28087 — The activated task was aborted because the invoked stored procedure '%ls' did not execute RECEIVE.
- 28088 — The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous "Broker:Activation" trace event for possible outp…
- 28089 — The database principal '%.*ls' cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward comp…
- 28090 — An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transm…
- 28091 — Starting endpoint for %S_MSG with no authentication is not supported.
- 28092 — Error updating proxy settings
- 28093 — Connection handshake failed due to internal failure. State %d.
- 28098 — A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the …
- 28099 — During the database upgrade process on database '%.*ls', a user object '%S_MSG' named '%.*ls' was found to already exist. That object is now reserved …
- 28101 — User '%.*ls%.*ls' does not have permission to debug the requested client connection.
- 28102 — Batch execution is terminated because of debugger request.
- 28200 — QUIC operation completed successfully.
- 28201 — QUIC configuration operation failed.
- 28202 — QUIC API operation failed.
- 28203 — QUIC listener operation failed.
- 28204 — QUIC connection operation failed.
- 28205 — QUIC stream operation failed.
- 28206 — Failed in starting XE Session for Sqlquic during sql startup
- 28207 — QUIC StartEndpoint result for endpoint type %d: reason=%d, status=0x%x.
- 28380 — Index with the specified Id (%d) in the clone address syntax cannot be found.
- 28381 — Lock hints other than READCOMMITTED and REPEATABLEREAD are not allowed when clone address syntax is used.
- 28382 — A correlation name must be specified for the clone address rowset function.
- 28383 — Clone address hint is missing on the tables '%.*ls'.
- 28389 — Target 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 inconsiste…
- 28390 — Invalid clone address syntax: IdxId %d, DbFragId %d, RowsetId 0x%016I64X.
- 28391 — The use of internal Clone Addressability syntax extensions is incompatible with the feature '%.*ls'.
- 28392 — The internal Clone Addressability syntax extensions is only allowed on user tables. The target (in the FROM claus) is '%.*ls'.
- 28393 — The index (id = %d) selected in the plan is inconsistent with the index specified in the clone address syntax (id = %d).
- 28394 — The query plan uses the feature '%.*ls' which is unexpected with clone address syntax.
- 28395 — Multiple conflicting Ids are given on '%.*ls': old value = %d, new value = %d.
- 28396 — Invalid clone address syntax: IdxId %d, DbFragId %d, RowsetId 0x%016I64X. (If you see this error, it implies there is a bug in the code.)
- 28397 — Unable to activate query fragment.
- 28401 — Feature or option '%ls' is not available. Please consult Books Online for more information on this feature or option.
- 28402 — Feature or option '%ls' is not yet implemented. Please consult Books Online for more information on this feature or option.
- 28403 — Starting SQL Server instance as a MatrixDB instance.
- 28404 — Exception in exception handling service thread.
- 28405 — During error handling, a second error was raised, causing an unrecoverable failure.
- 28406 — Error %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.
- 28407 — Entry fetch from brick %d failed to find entry in distributed cache %d on brick %d.
- 28408 — This 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 opt…
- 28410 — Warning: The lock_escalation option 'TABLE' is not available, and 'AUTO' option will be used instead. Please consult Books Online for more information…
- 28502 — The specified object Id is not valid.
- 28503 — The specified index Id is not valid.
- 28504 — The specified partition number is not valid.
- 28506 — Incorrect number of keys was specified. Must specify at least first %d key columns
- 28553 — Operation is not supported if all bricks are not online.
- 28554 — Data Virtualization Manager not found.
- 28555 — DVM failed to handle matrix reconfiguration. {error_code: %d, state: %d}
- 28601 — The Transaction Coordination Manager has encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, which ma…
- 28602 — The transaction is aborted because the transaction agent is shutting down.
- 28603 — Transaction agent is shutting down because shutdown request was received from the manager.
- 28604 — Transaction Coordination Manager is starting up. This is an informational message only. No user action is required.
- 28605 — Transaction Coordination Manager is inactive. This is an informational message only. No user action is required.
- 28606 — Transaction Coordination Manager is active with %016I64x as the starting AGE. This is an informational message only. No user action is required.
- 28607 — TCM %.*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-synchron…
- 28608 — Federated 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…
- 28609 — Matrix transaction operation is not allowed because the transaction doesn't allow forward progress, the transaction will be rolled back.
- 28610 — Matrix transaction couldn't commit because the task is aborted. The task is aborted either because of cancel instruction from client application, or b…
- 28611 — The request is aborted because the transaction has been aborted by Matrix Transaction Coordination Manager. This is mostly caused by one or more trans…
- 28612 — An error occurred while accessing Transaction Coordination Manager metadata. Could not persist AGE %016I64x.
- 28613 — Transaction Coordination Agent is active. This is an informational message only. No user action is required.
- 28614 — TCM manager has received a request for re-synchronization from brick id %d and will now restart. Typical causes where restart is necessary are tempora…
- 28615 — The request has performed an operation that is disallowed on a remote branch of a transaction
- 28701 — Request aborted due to communication errors: an attempt was made to use channel %d.%d.%I64u in the closed state.
- 28702 — Request aborted due to communication errors: incoming message format violation.
- 28703 — Request aborted due to communication errors: no enabled channel maps for component %d found.
- 28704 — Request aborted due to communication errors: unable to allocate new message for the brick %d. Error code %d.
- 28705 — Request aborted due to communication errors: unable to complete send operation for the pipeline %hs. Error code %d.
- 28706 — Next message reported have originated on brick %d.
- 28707 — Brick was unable to communicate with configuration manager and will be disconnected. See previous errors for the details.
- 28708 — Failure encountered due to Matrix configuration change: a brick was evicted.
- 28709 — Dispatcher was unable to create new thread.
- 28710 — Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent but there were no messages recei…
- 28711 — Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent at age %d (current age and bytes…
- 28712 — Unable to start expiration manager dispatch thread. Result code %d.
- 28713 — Communication subsystem failed to process user abort request. Error Number: %d; State: %d.
- 28714 — Request aborted due to communication errors: an attempt was made to communicate with Brick %d which is no longer online or have been reconfigured.
- 28715 — Execution of the request was aborted on remote brick.
- 28716 — Request aborted due to communication errors: too many concurrent operations.
- 28717 — Request aborted due to communication errors: communication subsystem is shutting down or initialization not complete yet.
- 28718 — Request aborted due to communication errors: pipeline %hs received message (classId %d, sequenceId %d) from the expired age %d (last acceptable age %d…
- 28719 — Request aborted due to Fabric errors: unable to enqueue a task for workspace 0x%I64x.
- 28720 — Mci subsystem failed to start with error %d.
- 28721 — Mci subsystem failed to start channel %d with error %d
- 28722 — Force close service was unable to communicate with configuration manager (brick %d) either due errors or timeout (%d milliseconds). Matrix is not func…
- 28723 — Brick was shutdown by administrator request
- 28724 — Channel close verification
- 28725 — Unable to process cancellation request due to resource availability. Retrying...
- 28726 — Unable to process activation data for a workspace.
- 28727 — Unable to process incoming message due to resource availability.
- 28728 — Request aborted due to communication errors: no channel maps of version %d for component %d found to create channel %I64u.
- 28729 — Request aborted due to communication errors: a message have arrived for non-activated channel %I64u.
- 28901 — Configuration manager agent has started enlistment protocol to join matrix
- 28902 — Cannot create configuration manager agent enlistment thread.
- 28903 — Configuration manager agent enlistment is retrying enlistment since brick <%d> eviction is pending.
- 28904 — Configuration manager agent enlistment is sending join request message to manager.
- 28905 — Configuration manager agent enlistment failed to receive reply from manager. See previous errors in error log.
- 28906 — Configuration manager agent enlistment completed with '%s'.
- 28907 — Configuration manager agent enlistment stopped.
- 28908 — Configuration manager agent enlistment failed due to different enlistment protocol versions between manager and agent. Version received from manager: …
- 28909 — Configuration manager agent enlistment failed due to receiving reply from invalid manager brick id <%d> .
- 28910 — Sequence number mismatch of enlistment messages. Sequence number received: <%d>, Sequence number expected <%d>.
- 28911 — Configuration manager agent enlistment succeeded. Manager accepted brick <%d> join request.
- 28912 — Brick <%d> enlistment with configuration manager failed due to '%s' mismatch. Brick will be taken down.
- 28913 — Configuration manager agent enlistment encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, that preve…
- 28914 — Configuration manager agent enlistment: Brick <%d>, state <%d>.
- 28915 — Configuration manager agent encountered error %d, state %d, severity %d while updating brick <%lu> incarnation to %I64u. Examine previous logged messa…
- 28916 — Configuration manager agent encountered error %d, state %d, severity %d while updating state information. Examine previous logged messages to determin…
- 28917 — Configuration manager agent enlistment received join reply message.
- 28918 — Brick cannot be started due to fatal error %d, state %d, severity %d during bootstrap. Examine previous logged messages to determine cause of this err…
- 28919 — Duplicate brick id <%d> detected in configuration file.
- 28920 — Configuration manager agent cannot send reported error to configuration manager due to error %d, state %d, severity %d.
- 28921 — No configuration file specified.
- 28922 — Configuration manager agent thread encountered fatal exception (error: %d severity: %d state: %d). This is a serious error and brick will be taken dow…
- 28923 — Configuration manager agent initialization failed. See previous errors in error log. This is a serious error condition and brick will be taken down.
- 28924 — Configuration manager agent activation failed.
- 28925 — Configuration manager agent quiesce failed.
- 28926 — Configuration manager agent release failed.
- 28927 — Configuration manager cannot create agent %d.
- 28929 — Configuration manager agent cannot commit new roster.
- 28931 — Configuration manager agent roster is corrupt.
- 28932 — Configuration manager agent did not receive a shutdown channel map.
- 28933 — Configuration manager agent could not perform brick down notification.
- 28934 — Configuration manager agent could not perform brick up notification.
- 28935 — Configuration manager agent is trying to start non-existing agent %d.
- 28936 — Configuration manager agent start failed (Loc: %d).
- 28937 — Configuration manager agent stop failed.
- 28938 — Configuration manager agent has started.
- 28939 — Configuration manager agent has shutdown.
- 28940 — Configuration manager agent could not delete stale MCI sessions.
- 28942 — Error reading configuration file. (Reason=%d).
- 28943 — Error reading configuration file. Column %s not defined.
- 28944 — Error reading configuration file. Host name or instance name cannot be empty (Reason: %d).
- 28945 — Error reading configuration file. Invalid contents. (Reason=%d).
- 28946 — Error reading matrix.xsd schema configuration file. (Reason=%d).
- 28947 — Error reading configuration file. (line:%d, column:%d, Reason=%s).
- 28948 — Error reading configuration file. Invalid placement brick id.
- 28949 — Error during configuration check (Function:%s, result: 0x%08lx).
- 28950 — Configuration manager agent cannot store metadata.
- 28951 — Cannot update roster, brick id %d not part of roster.
- 28952 — Configuration manager cannot initialize agent %d.
- 28953 — Matrix agent %d has the invalid state %d.
- 28955 — Cannot create roster memento.
- 28958 — Error copying configuration. (Reason=%s).
- 28959 — Cannot commit metadata change for brick id %d.
- 28960 — Error: Cannot read <%s> node of configuration file.
- 28961 — Error: invalid configuration file, no bricks defined.
- 28962 — Error: Invalid value for manager name %s specified.
- 28963 — Error: Invalid value for manager role %s specified.
- 28964 — Error: Cannot create dom object for writing of XML configuration file (Reason %d).
- 28968 — Starting communication infrastructure for communication between configuration manager and agent
- 28969 — Configuration manager agent shutting down...
- 28970 — Error: cannot update matrix metadata (Loc: %d).
- 28972 — Error: cannot determine host name.
- 28973 — Configuration manager agent cannot create notification publisher.
- 28974 — Configuration manager agent cannot create notification service.
- 28975 — Brick not configured correctly, corrupt configuration file.
- 28976 — Configuration manager agent is ignoring stale message from manager brick %d due to '%s' mismatch. Expected %I64u but received %I64u
- 28977 — Configuration manager agent is performing '%s' '%s' operation.
- 28978 — Configuration manager agent cannot '%s' '%s'. Examine previous logged messages to determine cause of this error. This is a fatal error affecting syste…
- 28979 — Configuration manager agent cannot '%s' '%s' due to invalid state '%s'. This is a fatal error affecting system functionality and brick will be taken d…
- 28980 — Error writing brick simulator state file. (Reason=%s).
- 29001 — To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
- 29003 — Invalid parameter combinations.
- 29004 — Unknown property specified: %s.
- 29101 — Fatal error in primary manager
- 29102 — Fatal error in backup manager
- 29103 — TCMA is shutting down since it encountered fatal error %d, state %d, severity %d
- 29104 — Failure in channel announce
- 29105 — Failure in channel enable
- 29201 — Configuration manager enlistment can not initialize communication service to receive enlistment requests
- 29202 — Configuration manager enlistment is ignoring message from brick <%d>. Enlistment protocol version mismatch. Agent version <%X>, manager version <%X>.
- 29203 — Configuration manager enlistment denied join of brick <%d>.
- 29204 — Configuration manager enlistment denied join of brick <%d>. Server default collation mismatch. Agent collation <%lu>, manager collation <%lu>.
- 29205 — Configuration manager enlistment denied join of brick <%d>. SQL version or build number mismatch. Agent version <%X>, manager version <%X>.
- 29206 — Configuration manager enlistment is ignoring messages from brick <%d> since message queue does not exist.
- 29207 — Configuration manager enlistment is ignoring stale message from brick %d due to '%s' mismatch. Expected %I64u but received %I64u
- 29208 — Cannot commit metadata change '%s' for brick id %d.
- 29209 — Configuration manager enlistment encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, which prevents f…
- 29210 — Configuration manager enlistment encountered error %d, state %d, severity %d while sending enlistment reply to brick <%lu>. Enlistment reply not sent!…
- 29211 — Configuration manager enlistment is ignoring request from invalid brick id <%d>.
- 29212 — Configuration manager enlistment encountered error %d, state %d, severity %d while updating brick <%lu> incarnation to %I64u. Enlistment request from …
- 29215 — Configuration manager enlistment acknowledges brick join request. Brick <%d> joined matrix.
- 29217 — Configuration manager enlistment received a new enlistment message.
- 29218 — Configuration manager enlistment state machine: Brick <%d>, state <%d>
- 29219 — Reserved brick <%d> is now marked active
- 29220 — Configuration manager enlistment started.
- 29221 — Configuration manager enlistment stopped.
- 29222 — Configuration manager enlistment did not receive enlistment messages
- 29223 — Configuration manager enlistment ran out of memory. Enlistment messages ignored.
- 29224 — Configuration manager enlistment sent reply to brick <%d>.
- 29225 — Configuration manager enlistment received join message from brick <%d>
- 29227 — Thread creation failed. (RC=%d).
- 29228 — Matrix transitioned from state %d to state %d.
- 29229 — Brick transitioned from state %d to state %d.
- 29230 — Manager transitioned from state %d to state %d.
- 29231 — Matrix transitioned from state %d to state %d.
- 29232 — Cannot create configuration manager enlistment thread.
- 29233 — Configuration manager thread encountered fatal exception (error: %d state: %d severity: %d). This is a serious error and brick will be taken down. Exa…
- 29234 — Configuration manager initialization failed. (Reason=%s).
- 29235 — Configuration manager cannot create channel distribution service.
- 29236 — Configuration manager cannot create force close service.
- 29237 — Configuration manager cannot create expiration service.
- 29239 — Configuration manager reconfiguration failed.
- 29241 — Configuration manager initialization failed.
- 29242 — Configuration manager activation failed.
- 29243 — Configuration manager quiesce operation failed.
- 29244 — Configuration manager release operation failed.
- 29245 — Configuration manager cannot quiesce the agents.
- 29246 — Configuration manager reconfiguration failed due to error %d, state %d, severity %d.
- 29247 — Configuration manager error handler initialization failed due to error %d, state %d, severity %d. This is a serious error and brick will be taken down…
- 29249 — Configuration manager broadcast channel shutdown crashed.
- 29250 — Configuration manager cannot perform action %d on other bricks in the matrix due to error %d, state %d, severity %d.
- 29251 — Configuration manager cannot create notification.
- 29252 — Configuration manager cannot create brick down event for unregistered brick <%d>
- 29253 — Configuration manager cannot perform channel distribution (Reason: %d, Loc: %d)
- 29254 — Configuration manager cannot activate the agents.
- 29255 — Configuration manager cannot send reconfig event.
- 29256 — Configuration manager cannot retire old channel maps (Loc: %d).
- 29257 — Configuration manager cannot shutdown old channel maps (Loc: %d).
- 29258 — Configuration manager cannot cannot deliver shutdown ack to leaving bricks.
- 29260 — Configuration manager cannot set matrix state.
- 29261 — Configuration manager detected an invalid matrix state.
- 29262 — Configuration manager can only evict bricks from the manager brick.
- 29263 — Configuration manager can only force close bricks from the manager brick.
- 29264 — Configuration manager brick down notification failed.
- 29265 — Configuration manager reconfig announce step failed.
- 29266 — Configuration manager reconfig enable step failed.
- 29267 — Configuration manager performed reconfig without membership change.
- 29268 — Configuration manager reconfig retire step failed.
- 29269 — Configuration manager cannot start non-registered manager %d.
- 29270 — Configuration manager has started accepting enlistment requests
- 29271 — Configuration manager has shutdown.
- 29272 — Configuration manager enlistment denied join of brick <%d>. Machine architecture mismatch. Agent machine architecture <%X>, manager machine architectu…
- 29273 — Error: cannot bump Configuration manager manager major version (Loc: %d).
- 29274 — Component %s reported that the component %s in brick %d is in a suspicious state because of the error: %d, severity: %d, state: %d, description: '%s'.…
- 29275 — Component %s from brick %d reported that the component %s in brick %d is in a suspicious state because of the error: %d, severity: %d, state: %d, desc…
- 29276 — Brick down message for brick %d enqueued due to fatal error reported for component %s by component %s in brick %d. Fatal error reported is error code:…
- 29277 — Configuration manager enlistment is queuing a failure request for brick <%d> due to receiving new enlistment request from this brick.
- 29278 — Configuration manager is evicting brick <%d> from which it did not receive expected reply during communication. This also includes brick not respondin…
- 29279 — Configuration manager could not read metadata necessary for its operation from the master database.
- 29280 — Configuration manager is performing '%s' '%s' operation on all online bricks.
- 29281 — Configuration manager is performing '%s' '%s' operation on brick <%lu>.
- 29282 — Configuration manager cannot '%s' '%s'. Examine previous logged messages to determine cause of this error. This is a fatal error affecting system func…
- 29283 — Configuration manager cannot initialize communication object. Examine previous logged messages to determine cause of this error.
- 29284 — Configuration manager could not write the WMI offline configuration file. (Reason=%s).
- 29285 — Configuration manager enlistment denied join of brick <%lu>. Supported number of bricks mismatch. Agent supported number of bricks <%lu>, manager supp…
- 29286 — Brick <%lu> will be allowed to join matrix once its previous brick down reconfiguration is completed.
- 29300 — The configuration file name %ls is invalid.
- 29301 — Failed to open configuration file %ls.
- 29302 — Configuration file %ls is empty.
- 29303 — The configuration file %ls is corrupt.
- 29304 — Cannot create brick configuration.
- 29305 — The configuration property %s is corrupt.
- 29306 — The configuration file name cannot be constructed. (Reason: %d).
- 29307 — Cannot set the roster property %s.
- 29308 — Local brick id <%d> does not match brick id <%d> in the resource database.
- 29309 — Brick id has not been set. (Resource instance name: %s)
- 29311 — An error occurred while trying to connect to a service control manager on machine %ls. Error returned: %d - %ls.
- 29312 — An error occurred while trying to perform a service operation on service %ls on machine %ls. Error returned: %d - %ls.
- 29314 — The service %ls on machine %ls failed to start in a timely fashion. Service specific error code %d.
- 29315 — OS user does not have the required privileges to start the remote service on brick %d.
- 29316 — The path name for the file matrix.xsd cannot be constructed. (Reason: %d).
- 29317 — Communication involving configuration manager and agent is ignoring stale message from brick <%lu> to brick <%lu> due to '%s' mismatch. Expected %I64u…
- 29318 — Communication involving configuration manager and agent is unable to send message from brick <%lu> to brick <%lu> due to error %d, state %d, severity …
- 29319 — Communication involving configuration manager and agent did not receive a valid reply from brick <%lu>
- 29320 — Communication involving configuration manager and agent cannot be initialized due to error %d, state %d, severity %d.
- 29321 — Communication involving configuration manager and agent received a failure response <0x%lx> from brick <%lu>.
- 29400 — Synchronous write task failed due to inconsistent prism state.
- 29401 — Prism operation failed due to error code %d.
- 29402 — Synchronous write task was aborted.
- 29501 — Data Virtualization Manager Agent not found.
- 29601 — SM force closing channel to recover after errors
- 29701 — GDMA LWFG buffer object pool initialization failed.
- 29702 — Failed to grow GDMA LWFG buffer LWFG vertex pool.
- 29703 — Failed to grow GDMA LWFG buffer LWFG edge pool.
- 29704 — Failed to release the specified vertex back to the vertex pool.
- 29705 — Failed to release the specified edge back to the edge pool.
- 29706 — GDMA LWFG buffer initialization failed.
- 29707 — Failed to publish LWFG to GDMA LWFG buffer.
- 29708 — GDMA request processing failed. See previous error for details.
- 29709 — TCMA API for mapping SOS_Task to federated transaction failed.
- 29711 — Failed to obtain brick-local active thread count for a federated transaction from local TCMA.
- 29801 — GDM request processing failed. See previous error for details.
- 29802 — GDM failed to allocate message via communication stack API.
- 29803 — Global Deadlock Monitor is inactive. This is an informational message only. No user action is required.
- 30003 — A fulltext system view or stvf cannot open database id %d.
- 30004 — A fulltext system view or stvf cannot open user table object id %d.
- 30005 — The name specified for full-text index fragment %.*ls is not valid.
- 30006 — A fulltext system view or stvf cannot open fulltext index for user table object id %d.
- 30007 — Parameters of dm_fts_index_keywords, dm_fts_index_keywords_by_document, dm_fts_index_keywords_by_property, and dm_fts_index_keywords_position_by_docum…
- 30008 — This is an internal error when invoking the TVF to access the full-text index. The level number specified for the TVF is not valid. Valid level number…
- 30009 — The argument data type '%ls' specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar.
- 30010 — An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service accou…
- 30011 — Full-text index version 1 is not supported by this instance configuration. Rebuild or recreate the index with database scoped configuration FULLTEXT_I…
- 30020 — The full-text query parameter for %S_MSG is not valid.
- 30022 — Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent…
- 30023 — The fulltext stoplist '%.*ls' does not exist or the current user does not have permission to perform this action. Verify that the correct stoplist nam…
- 30024 — The fulltext stoplist '%.*ls' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a uniq…
- 30025 — The search property list '%.*ls' does not exist or you do not have permission to perform this action. Verify that the correct search property list nam…
- 30026 — The search property list '%.*ls' already exists in the current database. Duplicate search property list names are not allowed. Rerun the statement and…
- 30027 — The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION …
- 30028 — Failed to get pipeline interface for '%ls', resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
- 30029 — The full-text host controller failed to start. Error: 0x%X.
- 30030 — The search property '%.*ls' does not exist, or you do not have permission to perform this action. Verify that the correct search property is specified…
- 30031 — A full-text master merge failed on full-text catalog '%ls' in database '%.*ls' with error 0x%08X.
- 30032 — The stoplist '%.*ls' does not contain fulltext stopword '%.*ls' with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transa…
- 30033 — The stoplist '%.*ls' already contains full-text stopword '%.*ls' with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Tran…
- 30034 — Full-text stoplist '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a st…
- 30035 — The search property '%.*ls' already exists in the search property list. Specify a search property name that is unique within the specified search prop…
- 30036 — Search property list '%.*ls' cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are us…
- 30037 — An argument passed to a fulltext function is not valid.
- 30038 — Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
- 30039 — Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing op…
- 30040 — During a full-text crawl of table or indexed view '%ls', an unregistered property, '%ls', was found in batch ID %d. This property will be indexed as p…
- 30041 — The master merge started at the end of the full crawl of table or indexed view '%ls' failed with HRESULT = '0x%08x'. Database ID is '%d', table id is …
- 30043 — Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
- 30044 — The user does not have permission to alter the current default stoplist '%.*ls'. To change the default stoplist of the database, ALTER permission is r…
- 30045 — Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
- 30046 — SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running…
- 30047 — The user does not have permission to %.*ls stoplist '%.*ls'.
- 30048 — Informational: Ignoring duplicate thesaurus rule '%ls' while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in eithe…
- 30049 — Fulltext thesaurus internal error (HRESULT = '0x%08x')
- 30050 — Both the thesaurus file for lcid '%d' and the global thesaurus could not be loaded.
- 30051 — Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: '%ls'.
- 30052 — The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs successfully…
- 30053 — An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service accou…
- 30055 — Full-text catalog import has started for full-text catalog '%ls' in database '%ls'.
- 30056 — Full-text catalog import has finished for full-text catalog '%ls' in database '%ls'. %d fragments and %d keywords were processed.
- 30057 — Upgrade option '%ls' is being used for full-text catalog '%ls' in database '%ls'.
- 30058 — Properties of zero length cannot be added to a search property list. Specify a search property name that contains at least one character and that is u…
- 30059 — A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); …
- 30060 — The import population for database %ls (id: %d), catalog %ls (id: %d) is being cancelled because of a fatal error ('%ls'). Fix the errors that are log…
- 30061 — The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account doe…
- 30062 — The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
- 30063 — Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid.
- 30064 — SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of document…
- 30065 — Filegroup '%ls' is offline, readonly, or no data file. Full-text population on table '%ls' is not resumed. Resume full-text population after fixing th…
- 30067 — Warning: The detach operation cannot delete a full-text index created on table '%ls' in database '%ls' because the index is on a read-only filegroup. …
- 30068 — During the database upgrade, the full-text filter component '%ls' that is used by catalog '%ls' was successfully verified. Component version is '%ls';…
- 30069 — The full-text filter component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component version is …
- 30070 — During the database upgrade, the full-text word-breaker component '%ls' that is used by catalog '%ls' was successfully verified. Component version is …
- 30071 — The full-text word-breaker component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component versi…
- 30072 — During the database upgrade, the full-text protocol handler component '%ls' that is used by catalog '%ls' was successfully verified. Component version…
- 30073 — The full-text protocol handler component '%ls' used to populate catalog '%ls' in a previous SQL Server release is not the current version (component v…
- 30074 — The master merge of full-text catalog '%ls' in database '%.*ls' was cancelled.
- 30075 — Full-text crawls for database ID: %d, table ID: %d, catalog ID: %d will be stopped since the clustered index on the table has been altered or dropped.…
- 30076 — Full-text crawl forward progress information for database ID: %d, table ID: %d, catalog ID: %d has been reset due to the modification of the clustered…
- 30077 — The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values for full-text queries tha…
- 30078 — The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type of full-text logical opera…
- 30079 — The full text query ignored UNKNOWN in the OPTIMIZE FOR hint.
- 30080 — The full-text population on table '%ls' cannot be started because the full-text catalog is importing data from existing catalogs. After the import ope…
- 30081 — A cached plan was compiled using trace flags that are incompatible with the current values. Consider recompiling the query with the new trace flag set…
- 30082 — Full-text predicates cannot appear in an aggregate expression. Place the aggregate expression in a subquery.
- 30083 — Full-text predicates cannot appear in the GROUP BY clause. Place a GROUP BY clause expression in a subquery.
- 30084 — The full-text index cannot be created because filegroup '%.*ls' does not exist or the filegroup name is incorrectly specified. Specify a valid filegro…
- 30085 — A stoplist cache cannot be generated while processing a full-text query or performing full-text indexing. There is not enough memory to load the stopl…
- 30086 — The system ran out of memory while building a full-text index. The batch for the full-text indexing operation will automatically be retried using a sm…
- 30087 — Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing op…
- 30088 — The full-text filter daemon host process has stopped normally. The process will be automatically restarted if necessary.
- 30089 — The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic comp…
- 30090 — A new instance of the full-text filter daemon host process has been successfully started.
- 30091 — A request to start a full-text index population on table or indexed view '%.*ls' is ignored because a population is currently paused. Either resume or…
- 30092 — Full-text stoplist ID '%d' does not exist.
- 30093 — The SQL Server word-breaking client failed to initialize. This might be because a filter daemon host process is not in a valid state. This can prevent…
- 30094 — The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to allocate memory or create t…
- 30095 — The version of the language components used by full-text catalog '%ls' in database '%ls' is different from the version of the language components incl…
- 30096 — A full-text retry pass of %ls population started for table or indexed view '%ls'. Table or indexed view ID is '%d'. Database ID is '%d'.
- 30097 — The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs for the catalog ID %d i…
- 30098 — An internal query to load data for a crawl on database '%.*ls' and table '%.*ls' failed with error code %d. Check the sql error code for more informat…
- 30099 — Fulltext internal error
- 30101 — The parameter '%s' is mandatory in stored procedure '%s'.
- 30103 — Invalid CM instance name.
- 30104 — Invalid matrix name.
- 30105 — Invalid TCP port number: %s.
- 30106 — Invalid network security level.
- 30107 — Invalid network isolation level.
- 30108 — Invalid matrix guid.
- 30109 — Invalid or duplicated brick ID was used: %s
- 30110 — Invalid parameter.
- 30111 — Matrix setup stored procedure '%s' failed with HRESULT 0x%x.
- 30112 — Insert brick into metadata operation failed during execution of stored procedure '%s'.
- 30113 — Insert manager into metadata operation failed during execution of stored procedure '%s'.
- 30114 — Insert parameter into metadata operation failed during execution of stored procedure '%s'.
- 30115 — No more bricks can be reserved. The maximum amount of %lu bricks is reached.
- 30118 — Invalid server name provided to configure a matrix brick.
- 30119 — Invalid CM brick GUID.
- 30120 — Invalid brick GUID.
- 30121 — '%s' in only allowed in standalone (non matrix) mode.
- 30122 — '%s' in only allowed in single user (-m) mode.
- 30123 — Drop existing matrix configuration failed during execution of stored procedure '%s'.
- 30124 — An error occurred while updating the CM metadata to remove a brick.
- 30125 — Configuration manager could not write the WMI offline configuration file during the execution of stored procedure '%s'.
- 30126 — Could not complete the last operation with the brick_id %u due a metadata failure
- 30127 — Attempt to cancel the reservation of a brick that is not reserved: %u
- 30128 — The stored procedure '%s' failed with the error code %d
- 30129 — '%s' in only allowed in matrix mode.
- 30130 — The brick with server name '%s' already exists in the configuration.
- 31001 — The session '%s' already exists. Use a different session name.
- 31002 — This operation can be performed only by the owner of the session.
- 31003 — User does not have enough permissions to tune one or more of the databases specified.
- 31004 — Could not create DTA directory for saving tuning option file when invoking DTA for auto indexing.
- 31005 — Could not create DTA tuning option file when invoking DTA for auto indexing.
- 31006 — Could not write DTA tuning option to file when invoking DTA for auto indexing.
- 31007 — Could not create a DTA job when invoking DTA for auto indexing.
- 31008 — Could not retrieve limit and job state information from DTA job object when invoking DTA for auto indexing.
- 31009 — Could not set limits on DTA job object when invoking DTA for auto indexing.
- 31010 — Could not create a DTA process when invoking DTA for auto indexing.
- 31011 — Could not terminate DTA process after it fails to be assigned to DTA job object when invoking DTA for auto indexing.
- 31012 — Could not resume DTA process to start tuning when invoking DTA for auto indexing.
- 31013 — Invalid tuning option specified for auto indexing.
- 31014 — Could not terminate DTA job when cancelling DTA tuning for auto indexing.
- 31015 — Could not delete DTA tuning options file when cancelling DTA tuning for auto indexing.
- 31016 — Could not cleanup hypothetical indexes and statistics when cancelling DTA tuning for auto indexing.
- 31017 — DTA tuning for auto indexing is only supported on Azure DB.
- 31018 — Could not get winfab temp directory when performing DTA tuning related task.
- 31019 — Could not create GUID when performing DTA tuning related task.
- 31020 — String operation failed.
- 31021 — Could not get winfab log directory when performing DTA tuning related task.
- 31022 — Could not get winfab data package directory when performing DTA tuning related task.
- 31201 — Property-scoped full-text queries cannot be specified on the specified table because its full-text index is not configured for property searching. To …
- 31202 — Reconfiguring the search property list of the full-text index has truncated the existing data in the index. Until the full-text index has been fully r…
- 31203 — Warning Master Merge operation was not done for dbid %d, objid %d, so querying index will be slow. Please run alter fulltext catalog reorganize.
- 31204 — Operation %ls is not supported on the %ls platform.
- 31205 — The import population for database %ls (id: %d), catalog id: %d is being cancelled because of a fatal error ('%ls'). Fix the errors that are logged in…
- 31206 — Failed to schedule asynchronous resume fulltext crawl task for database id %d with error %d.
- 31207 — Invalid value for Full-Text index version is specified. Valid values are 1 or 2.
- 31208 — A fulltext fragment table is missing.
- 31209 — Cannot create a full-text index on table or indexed view '%.*ls.%.*ls' because a previous full-text index drop is still being cleaned up. Try again la…
- 31210 — Cannot execute ALTER FULLTEXT INDEX on table or indexed view '%.*ls' because an online full-text index rebuild is in progress. Wait for the rebuild to…
- 31601 — The size of the provided %ls is %u bytes, which exceeds the maximum allowed size of %u bytes.
- 31602 — Received param '%.*ls' successfully.
- 31603 — Received param '%d' successfully.
- 31604 — The value '%d' is not within range for the '%.*ls' parameter.
- 31605 — The specified method '%.*ls' is not supported.
- 31606 — Serializing payload value failed
- 31607 — Outbound connection not allowed for the specified external endpoint.
- 31608 — An error occurred, failed to communicate with the external rest endpoint. HRESULT: 0x%x.
- 31609 — An error occurred, failed to parse url. HRESULT: 0x%x.
- 31610 — Accessing the external endpoint is only allowed via HTTPS.
- 31611 — The response's headers size exceeds the maximum allowed size of %u bytes.
- 31612 — Connections to the domain %ls are not allowed.
- 31613 — The length of the provided %ls after percent-encoding exceeds the maximum allowed length of %u bytes.
- 31614 — Only alphanumeric characters, hyphens, underscores, and dots are allowed in the hostname or in the fully qualified domain name.
- 31615 — The %ls cannot contain nested structures. Please check the formatting of the JSON and try again with a flat structure.
- 31616 — Warning: header '%ls' was overwritten by a system-defined value.
- 31617 — The %ls contains invalid characters. Only printable US ASCII characters are allowed.
- 31618 — The %ls contains an empty key.
- 31619 — The %ls could not be parsed. jsonError = %d.
- 31620 — The %ls is not a json object datatype.
- 31621 — One of the %ls values could not be parsed.
- 31622 — An unexpected error occurred while validating that the connection to the hostname is allowed. For more information, see https://go.microsoft.com/fwlin…
- 31624 — Connection to the external endpoint IP is not allowed. URL contains a hostname that is resolved to a blocked IP. For more information, see https://go.…
- 31625 — DNS resolution of the hostname has failed with windows sockets error %d.
- 31627 — An out of memory exception has occurred during external endpoint invocation.
- 31628 — The database scoped credential '%.*ls' has an invalid identity '%.*ls' for use with an external rest endpoint.
- 31629 — The external rest endpoint execution exceeded the timeout value.
- 31630 — The database scoped credential '%.*ls' cannot be used to invoke an external rest endpoint.
- 31631 — An error has occurred while waiting for the external rest endpoint result: %d.
- 31632 — The request's headers size exceeds the maximum allowed size of %u bytes.
- 31633 — The length of the provided %ls exceeds the maximum allowed length of %u bytes.
- 31634 — The %ls must contain a '%ls' for use with managed identity.
- 31635 — The %ls's '%ls' value must be a %ls for use with managed identity.
- 31636 — Error retrieving the managed identity access token for the resource id '%ls'
- 31637 — Connections to the domain %ls are not allowed using a credential object with the identity 'SHARED ACCESS SIGNATURE'.
- 31638 — The specified '%.*ls' value is not supported in the @headers parameter.
- 31639 — The specified '%ls' value is not supported in the @credential secret.
- 31640 — The %.*ls XML string could not be parsed. %.*ls.
- 31641 — The charset value of the response's Content-Type header is not supported.
- 31642 — The value of one of the key-value pairs in the %ls is empty.
- 31643 — '%ls' is disabled on this instance of SQL Server. Use sp_configure 'external rest endpoint enabled' to enable it.
- 31644 — Server Managed Identity is disabled for this instance of SQL Server. Use sp_configure 'allow server scoped db credentials' to enable it. For more info…
- 31701 — Parameter '%ls' must be specified. This parameter cannot be NULL.
- 31703 — Missing JSON key %ls
- 31704 — Unable to parse JSON
- 31705 — Failed to run AI function with error %d %ls
- 31706 — Requested entities count does not match response: sent %d, received %d
- 31707 — Failed to generate a request ID with HRESULT %d
- 31708 — Failed to write to a blob handle with HRESULT %d
- 31709 — Failed to read from a blob handle with HRESULT %d
- 31710 — Failed to lock bytes of a blob handle
- 31711 — AI service response is inconsistent
- 31712 — Request failed with retriable error
- 31713 — Bad URL argument %ls
- 31714 — AI function returned following error: %s
- 31715 — JSON value type ID is %d but %d expected
- 31716 — The model parameter '%.*ls' is required for invocation.
- 31717 — Extensibility function is not allowed in system database.
- 31718 — An internal error has occurred. Please retry the operation. If the issue persists, contact support for assistance.
- 31719 — The API_FORMAT '%.*ls' is not supported. For more information, see https://go.microsoft.com/fwlink/?linkid=2325940 .
- 31720 — Fabric functions service response is inconsistent.
- 31721 — Failed to run Fabric function with error %d %ls.
- 31723 — Failed to fetch service endpoint.
- 31724 — Type %ls is not supported by Fabric functions.
- 31725 — Failed to run Fabric function with error %d %ls.
- 31726 — Invalid Fabric function '%ls' argument count: '%d' given vs '%d' expected.
- 31727 — Fabric function '%ls' is not found in '%ls' function set.
- 31728 — Function '%ls' is not found.
- 31729 — Type '%ls' is does not convert to '%ls' for argument '%ls' of function '%ls'.
- 31730 — The Fabric Function argument type '%ls' is not supported.
- 31731 — The provided JSON parameters (e.g., '%.*ls') are not allowed.
- 31732 — '%.*ls' must be a valid JSON object.
- 31733 — The '%ls' with Local ONNX provider is not enabled.
- 31734 — The value '%I64d' is not within range for the %ls parameter.
- 31735 — The JSON value for the JSON key '%ls' must be '%.*ls' type.
- 31736 — An error occurred during the execution of the function.
- 31737 — The size of the provided %ls would be at least %u bytes after converting to UTF-8, which exceeds the maximum allowed size of %u bytes.
- 31738 — Initialization of the '%ls' process with session ID '%ls' failed with HRESULT 0x%08x.
- 31739 — Generating embeddings from '%ls' process with session ID '%ls' failed with HRESULT 0x%08x.
- 31740 — An internal error has occurred in AI runtime with session ID '%ls'. Retry the operation, if the issue persists, contact support for assistance.
- 31741 — SQL type '%ls' is implicitly converted to Fabric function's type '%ls' for argument '%ls'.
- 31742 — Unrecoverable HTTP error %d %ls occured.
- 31743 — Language '%ls' is not supported.
- 31744 — The JSON path for embeddings could not be found in the response.
- 31745 — The HTTP response does not contain valid JSON.
- 31746 — Label '%.*ls' is empty, which is not allowed.
- 31747 — Label '%.*ls' exceeds the maximum allowed length of %d bytes.
- 31748 — The (CREATE | CREATE OR ALTER | ALTER) FUNCTION statement cannot reference external functions whose parameters or return types are of type None.
- 31749 — Function set is not found.
- 31750 — Incorrect value '%ls' provided for type '%ls'.
- 31751 — The AI function '%ls' failed to process the input text '%.*ls'. Error %d: %ls.
- 31752 — The AI function '%ls' failed to process an input row after multiple retry attempts. Error %d: %ls.
- 31753 — The AI function '%ls' failed to process an input row. Error %d: %ls.
- 31754 — Fabric Function '%.*ls' does not have batch mode value defined, the invocation will be serialized.
- 31755 — '%ls' requires an external model of type '%ls'.
- 31756 — The '%ls' function with Local ONNX provider is not supported in batch mode.
- 31757 — The '%ls' function with RETURNING JSON is not supported in batch mode.
- 31758 — sp_ai_request returned an invalid result: %.*ls
- 31759 — An empty key was found in the JSON object for '%.*ls'.
- 31760 — The function set is not ready for the use. Please, validate that last publising completed successfully.
- 31761 — The function set is being deployed. Please, wait for the deployment to complete before using the function set.
- 31762 — Cannot use function set because its' deployment failed with error: '%.*ls'
- 31763 — The function set runtime is unsupported.
- 31764 — The function set has unpublished package: '%.*ls'
- 31765 — Fabric function '%.*ls' is not available for use as its' state is not 'OK'. Validate that the function can be invoked in User Data Functions.
- 31766 — The Fabric function metadata contains more than the maximum supported number of %d parameters.
- 31767 — The Fabric function metadata contains invalid parameter metadata at parameter %d. Parameter names must be unique, contain between 1 and %d characters,…
- 31768 — The Fabric function batch size must be an integer from 0 through %d.
- 31769 — The Fabric function catalog metadata contains invalid parameter information. Recreate the function.
- 31770 — The principal must have write permissions to execute external functions.
- 31771 — The AI functions configuration is not a valid JSON object.
- 31772 — '%.*ls' is not a recognized AI functions configuration setting.
- 31773 — The AI functions configuration setting '%.*ls' requires a value of type %.*ls.
- 31774 — The AI functions configuration setting '%.*ls' exceeds its maximum length of %d characters.
- 31775 — The AI functions configuration setting '%.*ls' value is out of bounds.
- 31776 — The AI functions configuration JSON document exceeds the maximum allowed length of %d characters.
- 31777 — The session context key '%.*ls' is reserved for the AI functions configuration and cannot be set directly.
- 31778 — The AI functions configuration setting '%.*ls' cannot be an empty string.
- 31779 — The AI service rejected the AI functions configuration of this session with error %d: %ls Review the settings applied with sp_aifunc_default_conf.
- 31780 — Failure occurred during authorization: %.*ls %.*ls (RootActivityId: %.*ls)
- 31801 — Incorrect JSON
- 31802 — JSON value casted to incorrect type
- 31803 — Missing JSON key '%ls'
- 32001 — Log shipping backup log job for %s.
- 32002 — Log shipping copy job for %s:%s.
- 32003 — Log shipping restore log job for %s:%s.
- 32004 — Log shipping backup log job step.
- 32005 — Log shipping copy job step.
- 32006 — Log shipping restore log job step.
- 32007 — Database %s is not ONLINE.
- 32008 — Database %s is not ONLINE. The backup job will not be performed until this database is brought online.
- 32009 — A log shipping primary entry already exists for database %s.
- 32010 — Database %s does not exist as log shipping primary.
- 32011 — Primary Database %s has active log shipping secondary database(s). Drop the secondary database(s) first.
- 32012 — Secondary %s.%s already exists for primary %s.
- 32013 — A log shipping entry already exists for secondary database %s.
- 32014 — Database %s does not exist as log shipping secondary.
- 32015 — The primary database %s cannot have SIMPLE recovery for log shipping to work properly.
- 32016 — The specified agent_id %s or agent_type %d do not form a valid pair for log shipping monitoring processing.
- 32017 — Log shipping is supported on Enterprise, Developer and Standard editions of SQL Server. This instance has %s and is not supported.
- 32018 — Log shipping is not installed on this instance.
- 32019 — Log shipping alert job.
- 32020 — Log shipping alert job step.
- 32021 — Log shipping alert job schedule.
- 32022 — Cannot add a log shipping job with name %s. A job with same name already exists in the system and this job does not belong to log shipping category.
- 32023 — An entry for primary server %s, primary database %s does not exist on this secondary. Register the primary first.
- 32024 — An entry for primary server %s, primary database %s already exists.
- 32025 — Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first.
- 32026 — Log shipping Primary Server Alert.
- 32027 — Log shipping Secondary Server Alert.
- 32028 — Invalid value = %d for parameter @threshold_alert was specified.
- 32029 — Log shipping backup agent [%s] has verified log backup file '%s.wrk' and renamed it as '%s.trn'. This is an informational message only. No user action…
- 32030 — Could not query monitor information for log shipping primary %s.%s from monitor server %s.
- 32031 — Could not query monitor information for log shipping secondary %s.%s from monitor server %s.
- 32032 — Invalid value '%d' for update period. Update period should be between 1 and 120 minutes.
- 32033 — The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring
- 32034 — An internal error occurred when setting up the database mirroring monitoring job.
- 32035 — An internal error occurred when modifying the database mirroring monitoring job.
- 32036 — Parameter(s) out of range.
- 32037 — The units for the update period for the database mirroring monitor job have been changed.
- 32038 — An internal error has occurred in the database mirroring monitor.
- 32039 — The database '%s' is not being mirrored. No update of the base table was done.
- 32040 — The alert for 'oldest unsent transaction' has been raised. The current value of '%d' surpasses the threshold '%d'.
- 32041 — The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them.
- 32042 — The alert for 'unsent log' has been raised. The current value of '%d' surpasses the threshold '%d'.
- 32043 — The alert for 'unrestored log' has been raised. The current value of '%d' surpasses the threshold '%d'.
- 32044 — The alert for 'mirror commit overhead' has been raised. The current value of '%d' surpasses the threshold '%d'.
- 32045 — '%s' must be executed in msdb.
- 32046 — Only members of the sysadmin fixed server role or the 'dbm_monitor' role in msdb can perform this operation.
- 32047 — Database Mirroring Monitor Job
- 32048 — Database Mirroring Monitor Schedule
- 32049 — The database mirroring monitoring job does not exist. Run sp_dbmmonitoraddmonitoring to setup the job.
- 32050 — Alerts cannot be created on the system databases, master, msdb, model or tempdb.
- 32051 — System administrator privilege is required to update the base table. The base table was not updated.
- 32052 — Parameter '%s' cannot be null or empty. Specify a value for the named parameter and retry the operation.
- 32053 — The server name, given by '@@servername', is currently null.
- 32054 — There was an error establishing a link to the remote monitor server.
- 32055 — There was an error configuring the remote monitor server.
- 32056 — The SQL Server failed to create full-text FTData directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does no…
- 32057 — There was an error configuring the log shipping backup server. The primary_server_with_port_override is set to '%s'. It is only valid on a contained a…
- 33001 — Cannot drop the option because the option is not specified on %S_MSG.
- 33002 — Access to %ls %ls is blocked because the signature is not valid.
- 33003 — DDL statement is not allowed.
- 33004 — The password of login '%.*ls' is invalid. A new password should be set for this login without specifying the old password.
- 33005 — Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x.
- 33006 — WITH SIGNATURE option cannot be specified on database.
- 33007 — Cannot encrypt symmetric key with itself.
- 33008 — Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG.
- 33009 — The database owner SID recorded in the master database differs from the database owner SID recorded in database '%.*ls'. You should correct this situa…
- 33010 — The MUST_CHANGE option cannot be specified together with the HASHED option.
- 33011 — The %S_MSG private key cannot be dropped because one or more entities are encrypted by it.
- 33012 — Cannot %S_MSG signature %S_MSG %S_MSG '%.*ls'. Signature already exists or cannot be added.
- 33013 — A %S_MSG by %S_MSG '%.*s' does not exist.
- 33014 — Cannot countersign '%.*s'. Only modules can be countersigned.
- 33015 — The database principal is referenced by a %S_MSG in the database, and cannot be dropped.
- 33016 — The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins.
- 33017 — Cannot remap a user of one type to a login of a different type. For example, a SQL user must be mapped to a SQL login; it cannot be remapped to a Wind…
- 33018 — Cannot remap user to login '%.*s', because the login is already mapped to a user in the database.
- 33019 — Cannot create implicit user for the special login '%.*s'.
- 33020 — A HASHED password cannot be set for a login that has CHECK_POLICY turned on.
- 33021 — Failed to generate a user instance of SQL Server. Only local user accounts, interactive users accounts, service accounts, or batch accounts can genera…
- 33022 — Cannot obtain cryptographic provider properties. Provider error code: %d.
- 33023 — The %S_MSG is too long. Maximum allowed length is %d bytes.
- 33024 — Cryptographic provider %S_MSG '%ls' in dll is different from the guid recorded in system catalog for provider with id %d.
- 33025 — Invalid cryptograpihic provider property: %S_MSG.
- 33026 — Cryptographic provider with guid '%ls' already exists.
- 33027 — Cannot load library '%.*ls'. See errorlog for more information.
- 33028 — Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%S_MSG)
- 33029 — Cannot initialize cryptographic provider. Provider error code: %d. (%S_MSG)
- 33030 — Cryptographic provider is not available.
- 33031 — Cryptographic provider '%.*ls' is in disabled.
- 33032 — SQL Crypto API version '%02d.%02d' implemented by provider is not supported. Supported version is '%02d.%02d'.
- 33033 — Specified key type or option '%S_MSG' is not supported by the provider.
- 33034 — Cannot specify algorithm for existing key.
- 33035 — Cannot create key '%.*ls' in the provider. Provider error code: %d. (%S_MSG)
- 33036 — Cannot drop the key with thumbprint '%.*ls' in the provider.
- 33037 — Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG)
- 33038 — Operation is not supported by cryptographic provider key.
- 33039 — Invalid algorithm '%.*ls'. Provider error code: %d. (%S_MSG)
- 33040 — Cryptographic provider key cannot be encrypted by password or other key.
- 33041 — Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Se…
- 33042 — Cannot add %S_MSG because it is already mapped to a login.
- 33043 — Cannot add %S_MSG '%.*ls' because there is already %S_MSG specified for the login.
- 33044 — Cannot drop %S_MSG because there is %S_MSG referencing this provider.
- 33045 — Cannot drop %S_MSG because it is not mapped to this login.
- 33046 — Server principal '%.*ls' has no credential associated with %S_MSG '%.*ls'.
- 33047 — Fail to obtain or decrypt secret for %S_MSG '%.*ls'.
- 33048 — Cannot use %S_MSG under non-primary security context.
- 33049 — Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG)
- 33050 — Cannot create key '%.*ls' in the provider. Provider does not allow specifying key names.
- 33051 — Invalid algorithm id: %d. Provider error code: %d. (%S_MSG)
- 33052 — Cryptographic provider key cannot be a temporary key.
- 33053 — Extensible Key Management is disabled or not supported on this edition of SQL Server. Use sp_configure 'EKM provider enabled' to enable it.
- 33054 — Extensible key management is not supported in this edition of SQL Server.
- 33055 — Exception happened when calling cryptographic provider '%.*ls' in the API '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exceptio…
- 33056 — Cannnot impersonate login '%.*ls' to access %S_MSG '%.*ls'.
- 33057 — Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still use it. Restart the server to…
- 33058 — Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the server to …
- 33059 — An error occurred while trying to flush all running audit sessions. Some events may be lost.
- 33060 — The format of supplied parameter sid is invalid. The sid might be incorrect or the sid might describe the wrong type of user.
- 33061 — The specified RETENTION_DAYS value is greater than the maximum value allowed. The retenton days value must be less than %d days.
- 33062 — Password validation failed. The password does not meet SQL Server password policy requirements because it is too short. The password must be at least …
- 33063 — Password validation failed. The password does not meet SQL Server password policy requirements because it is too long. The password must be at most %d…
- 33064 — Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be …
- 33065 — An error occurred while configuring the password policy: HRESULT 0x%x, state %d. To skip configuring the password policy, use trace flag -T4634 during…
- 33066 — An error occurred while configuring the password policy: NTSTATUS 0x%x, state %d. To skip configuring the password policy, use trace flag -T4634 durin…
- 33067 — Secret provided can not contain more than 120 characters. Please provide a valid credential.
- 33068 — Cannot load cryptographic provider '%.*ls' because another EKM provider is already loaded in this process. Only one third-party EKM provider or one Az…
- 33069 — CREATE CERTIFICATE statement cannot mix file and binary modes. Rewrite the statement using only the FILE or the BINARY keyword.
- 33070 — The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must be at least 2 MB.
- 33071 — This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command.
- 33072 — The audit log file path is invalid.
- 33073 — Cannot find %S_MSG '%.*ls' or you do not have the required permissions.
- 33074 — Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database.
- 33075 — Granular auditing is not available in this edition of SQL Server. For more information about feature support in the editions of SQL Server, see SQL Se…
- 33076 — The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB.
- 33077 — RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE.
- 33078 — The containment setting in the master database does not match the property of the database files. Use ALTER DATABASE to reset the containment property…
- 33079 — Cannot bind a default or rule to the CLR type '%s' because an existing sparse column uses this data type. Modify the data type of the sparse column or…
- 33080 — Cryptographic provider library '%.*ls' loaded into memory. This is an informational message only. No user action is required.
- 33081 — Failed to verify Authenticode signature on DLL '%.*ls'.
- 33082 — Cannot find Cryptographic provider library with guid '%ls'.
- 33083 — Cannot create %S_MSG for %S_MSG '%ls' because it is not supported by the extensible key management provider '%ls'.
- 33084 — The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. Symmetric keys created fro…
- 33085 — One or more methods cannot be found in cryptographic provider library '%.*ls'.
- 33086 — SQL Server Audit failed to record %ls action.
- 33087 — %S_MSG property of the key returned by EKM provider doesn't match the expected value
- 33088 — The algorithm: %.*ls is not supported for EKM operations by SQL Server
- 33089 — Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG)
- 33090 — Attempting to load library '%.*ls' into memory. This is an informational message only. No user action is required.
- 33091 — Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and th…
- 33092 — Failed to verify the Authenticode signature of '%.*ls'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are si…
- 33093 — The Windows user or group '%s' is local or built-in. Use a Windows domain user or domain group.
- 33094 — An error occurred during Service Master Key %S_MSG
- 33095 — Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
- 33096 — A generic failure occurred during Service Master Key encryption or decryption.
- 33097 — Processing BrickId: %d with MasterDb.PrimaryPru.FragId %d
- 33098 — Initializing SMK for brickId: %d
- 33099 — You cannot add server-scoped catalog views, system stored procedures, or extended stored procedures to a database audit specification in a user databa…
- 33101 — Cannot use %S_MSG '%.*ls', because its private key is not present or it is not protected by the database master key. SQL Server requires the ability t…
- 33102 — Cannot encrypt a system database. Database encryption operations cannot be performed for 'master', 'model', 'tempdb', 'msdb', or 'resource' databases.
- 33103 — A database encryption key already exists for this database.
- 33104 — A database encryption key does not exist for this database.
- 33105 — Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the database enc…
- 33106 — Cannot change database encryption state because no database encryption key is set.
- 33107 — Cannot enable database encryption because it is already enabled.
- 33108 — Cannot disable database encryption because it is already disabled.
- 33109 — Cannot %S_MSG database encryption while an encryption, decryption, or key change scan is in progress.
- 33110 — Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
- 33111 — Cannot find server %S_MSG with thumbprint '%.*ls'.
- 33112 — Beginning database encryption scan for database '%.*ls'.
- 33113 — Database encryption scan for database '%.*ls' is complete.
- 33114 — Database encryption scan for database '%.*ls' was aborted. Reissue ALTER DB to resume the scan.
- 33115 — CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
- 33116 — CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%.*ls'. Try again later.
- 33117 — Transparent Data Encryption is not available in the edition of this SQL Server instance. See books online for more details on feature support in diffe…
- 33118 — Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
- 33119 — Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.
- 33120 — In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
- 33121 — The %S_MSG '%ls' does not have a login associated with it. Create a login and credential for this key to automatically access the extensible key manag…
- 33122 — This command requires a database encryption scan on database '%.*ls'. However, the database has changes from previous encryption scans that are pendin…
- 33123 — Cannot drop or alter the database encryption key since it is currently in use on a mirror or secondary availability replica. Retry the command after a…
- 33124 — Database encryption scan for database '%.*ls' cannot complete since one or more files are offline. Bring the files online to run the scan to completio…
- 33125 — Can not create login token because there are too many secondary principals. The maximum number of allowed secondary principals allowed is %lu. To fix …
- 33126 — Database encryption key is corrupted and cannot be read.
- 33127 — The %S_MSG cannot be dropped because it is used by one or more databases to encrypt a Database Encryption Key.
- 33128 — Encryption failed. Key uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use this ke…
- 33129 — Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission instead.
- 33130 — Principal '%ls' could not be found or this principal type is not supported.
- 33131 — Principal '%ls' was not unique.
- 33132 — This principal type is not supported in Windows Azure SQL Database.
- 33133 — Your subscription is not enabled for Integrated Authentication.
- 33134 — Principal '%ls' could not be found at this time. Please try again later.
- 33135 — Altering the name of a Windows principal is not supported through this form of execution. For more information about this, see SQL Server Books Online…
- 33136 — The operation could not be completed at this time. Please try again later.
- 33137 — The tenant '%.*ls' cannot be found.
- 33138 — ALTER DATABASE on a federation member is not supported for Windows users or groups.
- 33139 — This subscription does not support Integrated Authentication.
- 33140 — The login '%.*ls' could not be created because a login is already associated with certificate '%.*ls'.
- 33141 — The credential created might not be able to decrypt the database master key. Please ensure a database master key exists for this database and is encry…
- 33142 — Updating the tenantId for Azure SQL Server was not successful.
- 33143 — The account admin of the subscription does not belong to this tenant.
- 33144 — Cannot change the schema of a temporary object.
- 33145 — Cannot update database encryption key protector while protector change is already in progress.
- 33146 — The database '%.*ls' is offline. The credential was created but SQL Server is unable to determine if the credential can decrypt the database master ke…
- 33147 — Federated Authentication Feature data used in login record to open a connection is structurally or semantically invalid; the connection has been close…
- 33148 — The user name for a windows login has to be identical to the login name.
- 33149 — Dropping a credential '%.*ls' which could still be used by Managed Backup.
- 33150 — Warning: Can not check whether the credential '%.*ls' is used by managed backup, because %ls. Please check whether the credential is used by managed b…
- 33151 — The user name for a user with password cannot be identical to the name of the server admin or the dbo of the database.
- 33152 — Valid values of the database compatibility level are %d or %d.
- 33153 — Valid values of the database compatibility level are %d, %d, or %d.
- 33154 — Client sent an invalid token when server was expecting federated authentication token. And it was not a disconnect event.
- 33155 — A disconnect event was raised when server is waiting for Federated Authentication token. This could be due to client close or server timeout expired.
- 33156 — A Federated Authentication token was sent by the client when the server is not expecting it. So server will close the connection due to TDS non-confor…
- 33157 — Crypthographic providers are not supported on database credentials.
- 33158 — Database credentials are not supported in master database.
- 33159 — Principal '%ls' could not be created. Only connections established with Active Directory accounts can create other Active Directory users.
- 33160 — Unable to verify Authenticode signatures due to error code %d. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server…
- 33161 — Database master keys without password are not supported in this version of SQL Server.
- 33162 — TYPE and SID options have to be used along with each other, in this version of SQL Server.
- 33163 — The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) and X (EXTERNAL_GROUP)
- 33164 — Cannot drop the credential '%.*ls' because it is used by an external data source.
- 33165 — Cannot drop the external %ls '%.*ls' because it is used by an external table.
- 33166 — dbManager permission check failed.
- 33167 — This command is not supported for Azure AD users. Execute this command as a SQL Authenticated user.
- 33168 — TYPE option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version …
- 33169 — User name cannot have backslash character, when using the TYPE option.
- 33170 — SID option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version o…
- 33171 — Only active directory users can impersonate other active directory users.
- 33172 — Encrypting Secret for Database '%.*ls' and Credential '%.*ls' failed.
- 33173 — Assigning value for output parameter @credentialSecret failed because the parameter size is less than the required size %u. Please provide a larger si…
- 33174 — Cannot get credential '%.*ls' because it is not referenced by any external data source.
- 33175 — Encryption operation failed. Key used for encryption has deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If …
- 33176 — Signing operation failed. Key uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use …
- 33177 — Hash operation failed. Hash Function uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need …
- 33178 — Encryption key length is over the currently supported maximum length of %d.
- 33179 — Searching for '%.*ls' only searches "'%.*ls'" for SQL Server authentication logins.
- 33180 — Searching for "'%.*ls'" only searches for Azure Active Directory users. To search for a SQL Server authentication login, add the server name at the en…
- 33181 — The new owner cannot be Azure Active Directory group.
- 33182 — The command must be executed on the target database '%.*ls'.
- 33183 — The Azure Key Vault client encountered an error with message '%s'.
- 33184 — An error occurred while obtaining information for the Azure Key Vault client with message '%s'.
- 33185 — An error ocurred while attempting to copy the encrypted DEK from the DBTable.
- 33186 — Cannot alter the credential '%.*ls' because it is being used by an active audit session ('%.*ls').
- 33187 — Internal enclave error. Enclave failed to decrypt a column value or parameter - invalid authentication tag. For more information, contact Customer Sup…
- 33189 — Internal enclave error: Enclave is out of session resources. For more information, contact Customer Support Services.
- 33190 — Internal enclave error. Enclave attestation information requested for an unsupported enclave type. For more information, contact Customer Support Serv…
- 33191 — Enclave host encountered a runtime error: out of priority queue space.
- 33192 — Internal enclave error. Enclave raised an exception (major = %d, minor = %d). See error log for more information. For more information, contact Custom…
- 33194 — Internal enclave error. The enclave bcrypt method %hs failed with status 0x%x. For more information, contact Customer Support Services.
- 33195 — Internal enclave error. Enclave was provided with an invalid session handle. For more information, contact Customer Support Services.
- 33196 — VBS enclave attestation failed due to an error in Windows Management Instrumentation (WMI). API: '%ls', Return code: '0x%08x'. Check the AzureAttestSe…
- 33197 — The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) and X (EXTERNAL_GROUP).
- 33198 — TYPE and SID options have to be used along with each other, in this version of SQL Server.
- 33199 — Only Active Directory logins can impersonate other Active Directory logins.
- 33201 — An error occurred in reading from the audit file or file-pattern: '%s'. The SQL service account may not have Read permission on the files, or the patt…
- 33202 — SQL Server Audit could not write to file '%s'.
- 33203 — SQL Server Audit could not write to the event log.
- 33204 — SQL Server Audit could not write to the security log.
- 33205 — Audit event: %s.
- 33206 — SQL Server Audit failed to create the audit file '%s'. Make sure that the disk is not full and that the SQL Server service account has the required pe…
- 33207 — SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log.
- 33208 — SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
- 33209 — Audit '%.*ls' has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server was started with the -m …
- 33210 — SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-ge…
- 33211 — A list of subentities, such as columns, cannot be specified for entity-level audits.
- 33212 — There is an invalid column list after the object name in the AUDIT SPECIFICATION statement.
- 33213 — All actions in an audit specification statement must be at the same scope.
- 33214 — The operation cannot be performed because SQL Server Audit has not been started.
- 33215 — One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with each err…
- 33216 — SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
- 33217 — SQL Server Audit is starting the audits. This is an informational message. No user action is required.
- 33218 — SQL Server Audit has started the audits. This is an informational message. No user action is required.
- 33219 — The server was stopped because SQL Server Audit '%.*ls' is configured to shut down on failure. To troubleshoot this issue, use the -m flag (Single Use…
- 33220 — Audit actions at the server scope can only be granted when the current database is master.
- 33221 — You can only create audit actions on objects in the current database.
- 33222 — Audit '%.*ls' failed to %S_MSG . For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_type …
- 33223 — ALTER SERVER AUDIT requires the STATE option to be specified without using any other options.
- 33224 — The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command.
- 33225 — The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file set. Verify the file name a…
- 33226 — The fn_get_audit_file function is skipping records from '%.*ls' at offset %I64d.
- 33227 — The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher.
- 33228 — You cannot configure SQL Server Audit to shutdown the server because you do not have the permission to shut down the server. Contact your system admin…
- 33229 — Changes to an audit specification must be done while the audit specification is disabled.
- 33230 — An audit specification for audit '%.*ls' already exists.
- 33231 — You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements.
- 33232 — You may not add a role to Sysadmin.
- 33233 — You can only create a user with a password in a contained database.
- 33234 — The parameter %s cannot be provided for users that cannot authenticate in a database.
- 33235 — The parameter %s cannot be provided for users that cannot authenticate in a database. Remove the WITHOUT LOGIN or PASSWORD clause.
- 33236 — The default language parameter can only be provided for users in a contained database.
- 33237 — Cannot use parameter %s for Windows users or groups.
- 33238 — MAX_FILES and MAX_ROLLOVER_FILES options cannot be specified toghether.
- 33239 — An error occurred while auditing this operation. Fix the error in the audit and then retry this operation.
- 33240 — A failure occurred during initializing of an Audit. See the errorlog for details.
- 33241 — Failed to configure user instance on startup. Error updating the idle timeout.
- 33242 — When providing a sid, the user must be a user without login or a user with password.
- 33243 — Failed to generate a user instance of SQL Server due to a failure in setting access control list on the user instance's process. The connection will b…
- 33244 — SQL Server Audit failed to create an audit file related to the audit '%s' in the directory '%s'. Make sure that the disk is not full and that the SQL …
- 33245 — SQL Server Audit failed to write to an audit file related to the audit '%s' in the directory '%s'. Make sure that the disk is not full and that the SQ…
- 33246 — SQL Server Audit failed to access the MDS file log. Make sure that the disk is not full and that the SQL Server service account has the required permi…
- 33247 — SQL Server Audit could not write to the MDS local file (Error Code: %d).
- 33248 — The specified value for QUEUE_DELAY is not valid for MDS log target. Specify value higher than 0.
- 33249 — Cannot drop the credential '%.*ls' because it is being used.
- 33250 — Failed to allocate memory for caching credential '%.*ls' which is used by a database file.
- 33251 — A credential conflicting with '%.*ls' already exists in credential cache in memory. Use alter step to change the secret. Drop and re-create to change …
- 33252 — This CREATE AUDIT request exceeds the maximum number of audits that can be created per database.
- 33253 — Failed to modify the identity field of the credential '%.*ls' because the credential is used by an active database file.
- 33254 — This operation cannot be performed in the master database.
- 33255 — Audit specification '%.*ls' can only be bound to a %S_MSG audit.
- 33256 — The audit store location or the audit store URL has been configured for this database audit.
- 33257 — Cannot drop an audit store URL that is not configured for this database audit.
- 33258 — Invalid value for procedure "%.*ls", parameter "%.*ls".
- 33259 — Invalid security policy name '%.*ls'.
- 33260 — The predicate was not added to the security policy '%.*ls' because there are no available predicate IDs. Drop and recreate the security policy.
- 33261 — The security policy '%.*ls' does not contain a predicate on table '%.*ls'.
- 33262 — A %S_MSG predicate for the same operation has already been defined on table '%.*ls' in the security policy '%.*ls'.
- 33263 — Security predicates can only be added to user tables and schema bound views. '%.*ls' is not a user table or a schema bound view.
- 33264 — The security policy '%.*ls' cannot be enabled with a predicate on table '%.*ls'. Table '%.*ls' is already referenced by the enabled security policy '%…
- 33265 — The security policy '%.*ls' cannot have a predicate on table '%.*ls' because this table is referenced by the indexed view '%.*ls'.
- 33266 — The index on the view '%.*ls' cannot be created because the view is referencing table '%.*ls' that is referenced by a security policy.
- 33267 — Security predicates cannot reference memory optimized tables. Table '%.*ls' is memory optimized.
- 33268 — Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
- 33269 — Security predicates are not allowed on temporary objects. Object names that begin with '#' denote temporary objects.
- 33270 — Cannot find the object "%.*ls" or this object is not an inline table-valued function.
- 33271 — Cannot alter '%.*ls' because it is not a security policy.
- 33272 — Unable to load the security predicate for table "%.*ls".
- 33273 — Security predicates cannot be added on FileTables. '%.*ls' is a FileTable.
- 33274 — The version was not created for the key '%.*ls' because there are no available version IDs. Drop and recreate the key.
- 33275 — The encrypted value for this column encryption key cannot be dropped. Each column encryption key must have at least one encrypted value.
- 33277 — Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line '%d' expec…
- 33278 — Cannot assign the same encryption scheme to two expressions at line '%d'. The encryption scheme of the first expression is %ls and the encryption sche…
- 33279 — Cannot remove the credential '%.*ls/%.*ls' because it is being used.
- 33280 — Cannot create encrypted column '%.*ls' because type '%ls' is not supported for encryption.
- 33281 — Column '%.*ls.%.*ls' has a different encryption scheme than referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
- 33282 — Column '%.*ls.%.*ls' is encrypted using a randomized encryption type and is therefore not valid for use as a key column in a constraint, index, or sta…
- 33283 — '%S_MSG' clause is unsupported for encrypted columns.
- 33284 — The encrypted column '%.*ls.%.*ls' cannot be used as a partition key column.
- 33285 — Cannot set default constraint on encrypted column '%.*ls.%.*ls'. Default constraints are unsupported on encrypted columns.
- 33286 — Cannot encrypt column '%.*ls', because it is of a user-defined type.
- 33287 — Cannot drop column encryption key '%.*ls' because the key is referenced by column '%.*ls.%.*ls'.
- 33288 — The encrypted value for the column encryption key cannot be added. There can be no more than two encrypted values for each column encryption key. Drop…
- 33289 — Cannot create encrypted column '%.*ls', character strings that do not use a *_BIN2 collation cannot be encrypted.
- 33290 — There is no column encryption key value associated with the column master key '%.*ls'.
- 33291 — There is already a column encryption key value associated with the column master key '%.*ls'.
- 33292 — The encryption algorithm '%.*ls' is not supported. Please specify a valid encryption algorithm.
- 33293 — Cannot find the %S_MSG "%.*ls" because it does not exist or you do not have permissions.
- 33294 — Some parameters or columns of the batch require to be encrypted, but the corresponding column encryption key cannot be found. Use sp_refresh_parameter…
- 33296 — Cannot create table '%.*ls' since it references a column encryption key from a different database.
- 33297 — Cannot create %S_MSG. The %S_MSG cannot be empty.
- 33298 — Internal Query Processor Error: The encryption scheme of certain parameters was incorrectly analyzed. For more information, contact Customer Support S…
- 33299 — Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line '%d' expec…
- 33301 — The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and %d characters long.
- 33302 — The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and 10.
- 33303 — A conversation priority already exists in the database with either the name '%.*ls' or the properties %ls='%ls', %ls='%ls', and %ls='%.*ls'. Either us…
- 33304 — The transmission queue row with conversation handle '%ls' and message sequence number %d references a missing multicast message body row with referenc…
- 33305 — The multicast message body row with reference %d should have reference count value of %d.
- 33306 — The unreferenced message with reference %d has been deleted from the message body table.
- 33307 — The message with reference %d has been updated to a reference count of %d in the message body table.
- 33308 — The queue %d in database %d has activation enabled and contains unlocked messages but no RECEIVE has been executed for %u seconds.
- 33309 — Cannot start cluster endpoint because the default %S_MSG endpoint configuration has not been loaded yet.
- 33310 — Local cluster name can be set only once.
- 33311 — The wait for connect request completion failed.
- 33312 — The wait for querying proxy routes failed or was aborted.
- 33313 — An out of memory condition has occurred in the Service Broker transport layer. A service broker connection is closed due to this condition.
- 33314 — The supplied whitelist is invalid.
- 33315 — The redirected endpointurl is Invalid
- 33316 — Failed to reset encryption while performing redirection.
- 33317 — The redirect response contains invalid redirect string
- 33318 — The redirect request contains invalid string or redirect handler failed to handle the request
- 33319 — The redirector returned lookup failure
- 33320 — Tried to send redirect request but the redirect string is empty
- 33321 — The other end does not support redirection
- 33322 — The redirect message is corrupted
- 33323 — The endpoint is closing because the connection was redirected
- 33324 — Failed to parse the redirect info string