错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 13 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 23203 — Store item not found in Catalog.
- 23204 — Could not delete Store item in Catalog.
- 23205 — Store database name not found in Catalog.
- 23206 — Could not create share to the ItemPath '%ls'.
- 23207 — Could not add Share item for '%ls' in Catalog.
- 23208 — ItemPath '%ls' does not exist in Store.
- 23209 — Could not update Store state in Catalog.
- 23210 — Itempath '%ls' is a file-backed item or within it's sub-tree.
- 23211 — Could not start Store Manager. Please look in WinFS UT Log for details.
- 23212 — Itempath '%ls' is a compound item.
- 23500 — Item container does not exist.
- 23501 — Owning Item does not exist.
- 23502 — NamespaceName is empty or exceeds the maximum length.
- 23503 — Invalid Source endpoint type
- 23504 — Invalid Target endpoint type
- 23505 — A File-backed item must be a compound item type.
- 23506 — A File Backed Item may not contain other Items.
- 23509 — Source Item does not exist.
- 23510 — Item with name already exists in container.
- 23511 — New container cannot be a sub-container of item.
- 23513 — Item does not exist.
- 23515 — Item can not be deleted if it has children
- 23519 — Target Item does not exist.
- 23525 — Invalid Namespace Name.
- 23530 — Operation can not be called inside a un-committable transaction
- 23536 — Win32 file handle is open for item
- 23573 — Cannot change ContainerId when replacing item.
- 23579 — This procedure is reserved and cannot be called.
- 23587 — File stream cannot be null.
- 23588 — Container ids must be the same.
- 23601 — Change Event Streaming
- 23602 — Creation of the AMQP link on the session failed.
- 23603 — AMQP link target descriptor creation failed.
- 23604 — AMQP link source descriptor creation failed.
- 23605 — AMQP Session flow control configuration failed.
- 23606 — Creation of the AMQP session on the broker connection failed.
- 23607 — Creation of the AMQP connection to the broker failed.
- 23608 — Initialization of the AMQP client library failed.
- 23609 — Broker acknowledgment timed out.
- 23610 — The message could not be delivered to the broker.
- 23611 — Failed to establish an AMQP connection to the broker.
- 23612 — Failed to acquire a token using a managed service identity. Make sure that managed identity is configured correctly. Return code: '0x%08x'.
- 23613 — The identity type specified in the database scoped credential is not supported. For more information about supported identity types, see Change Event …
- 23614 — Could not allocate memory for Change Event Streaming operation. Verify that sufficient memory is available for all operations. Check the memory settin…
- 23615 — The argument '%ls' must not be null.
- 23616 — The value provided for the argument '@partition_key_column_name' is invalid. This argument must be null unless the argument '@partition_key_scheme' is…
- 23617 — The argument '@partition_key_column_name' must not be null or empty when using 'Column' partition key scheme.
- 23618 — The value provided for the argument '%ls' is invalid. Allowed values: %ls.
- 23619 — The value provided for the argument '%ls' is invalid. Stream group with the provided name already exists.
- 23620 — The value provided for the argument '%ls' is invalid. %ls with the provided name does not exist.
- 23621 — The argument '%ls' must not be null or empty.
- 23622 — Change Streams requires Change feed to be enabled.
- 23623 — The feature switch enabling support for using Event Hub with change streams is disabled. // ErrorCause: Change Streams has not enabled support for Eve…
- 23624 — The caller does not have permission to use '%s'.
- 23625 — The argument '%s' failed validation.
- 23626 — An error occured. The error/state returned was %d/%d: '%s'.
- 23627 — An error occured when configuring change feed.
- 23628 — The argument '%s' failed validation. Expects: 'schemaName.objectName'
- 23629 — The configuration already exists in '%s'.
- 23630 — Change Streams could not create the object configuration.
- 23631 — The configuration does not exists in '%s'.
- 23632 — Change Streams could not remove the object configuration.
- 23633 — Change Streams could not drop the object configuration from the group.
- 23634 — Change Event Streaming is not supported for this database.
- 23635 — Adding partition key to the AMQP message failed.
- 23636 — Change Event Streaming is not enabled on database '%ls'.
- 23637 — Change Event Streaming is not supported in the free offer databases, single databases using the Basic, S0, S1, or S2 service objectives, and in elasti…
- 23638 — Change Event Streaming encountered an Avro exception.
- 23639 — LOB data could not be read while extracting column values for change event. HRESULT: '0x%08x'.
- 23640 — Change Event Streaming serializer not initialized.
- 23641 — The value in provided argument '@include_old_lob_values' is incompatible with value '0' provided in argument '@include_old_values'. To use '@include_o…
- 23642 — Destination location parameter is not in the expected format. Expected format is [Event Hubs Namespace Host name]/[Event Hubs Instance] or [Event Hubs…
- 23643 — Change Event Streaming for '%ls' is already enabled for stream group '%ls'.
- 23644 — Table name supplied in the argument '%ls' is either not configured for Change Event Streaming or it does not exist for the supplied stream group.
- 23645 — The value provided for the 'Port number' in the destination location parameter is invalid. It must be a numeric value between 0 and 65535.
- 23646 — Change Event Streaming message exceeds the configured message size limit.
- 23647 — Tables contained in the changefeed schema cannot be enabled for Change Streams.
- 23648 — Could not enable Change Event Streaming for database '%ls'. Change Event Streaming is not supported on system databases, or on a distribution database…
- 23649 — Change Event Streaming is not supported in contained databases. Change Event Streaming cannot be enabled on the contained database '%ls'.
- 23650 — Could not enable Change Event Streaming for database '%ls'. Change Event Streaming cannot be enabled on a database configured for Change Data Capture.
- 23651 — Could not enable Change Event Streaming for database '%ls'. Change Event Streaming cannot be enabled on a database with forced or allowed DELAYED_DURA…
- 23652 — Could not enable Change Event Streaming for database '%ls'. Change Event Streaming cannot be enabled on a database configured for Database Mirroring i…
- 23653 — Could not enable Change Event Streaming for database '%ls' as it is already enabled.
- 23654 — The application lock request '%ls' needed to modify Change Event Streaming metadata was not granted. The value returned by sp_getapplock was %d. Exami…
- 23655 — Allowed number of Change Event Streaming stream groups is exceeded. The limit is %d stream groups per database.
- 23656 — Enabling Change Event Streaming for table '%ls' failed because '%ls' table type is not supported.
- 23657 — The number of tables enabled for a Change Event Streaming stream group cannot exceed %d. Current number of tables enabled: %d.
- 23658 — Change Event Streaming encountered a SQL exception.
- 23659 — Schema changes on table '%.*ls' are not supported because the table is enabled for Change Event Streaming.
- 23660 — The switch partition operation is not supported for table '%.*ls' because it is enabled for Change Event Streaming.
- 23661 — Cannot rename the table because it is enabled for Change Event Streaming.
- 23662 — Cannot drop the table '%.*ls' because it is enabled for Change Event Streaming.
- 23663 — Cannot truncate the table '%.*ls' because it is enabled for Change Event Streaming.
- 23664 — Adding primary key constraint failed for table '%.*ls'. Once tables are enabled for Change Event Streaming, their primary keys cannot be added or modi…
- 23665 — Dropping primary key constraint failed for table '%.*ls'. Once tables are enabled for Change Event Streaming, their primary keys cannot be dropped or …
- 23666 — The expected value for argument '%ls' is between '%d' and '%d' KB, inclusive.
- 23667 — Change Event Streaming event delivery error: '%ls'.
- 23668 — User table '%ls' has reached the maximum number of Change Event Streaming destinations.
- 23669 — PREVIEW_FEATURES must be enabled on the database to use Microsoft Fabric Mirroring on Linux.
- 23670 — No primary system assigned managed identity found.
- 23671 — Microsoft Fabric Mirroring is not supported on Azure VM.
- 23672 — Microsoft Fabric Mirroring is not supported with Arc user assigned managed identity. Please use Arc system assigned managed identity.
- 23673 — Communication with Change Event Streaming destination blocked by outbound firewall rules.
- 23674 — Communication with Change Event Streaming destination blocked by Network Security Perimeter rules.
- 23675 — Enabling Change Event Streaming for table '%ls' that has a column_set column is not supported.
- 23676 — Adding a column_set column to table '%.*ls' that is enabled for Change Event Streaming is not supported.
- 23677 — Change Event Streaming encountered a Kafka exception.
- 23678 — Failed to send a message to Kafka endpoint.
- 23679 — Unable to reach the configured destination.
- 23680 — The specified destination instance could not be found. Verify the destination_location parameter in the stream group configuration.
- 23681 — Could not connect to the destination due to an authentication error.
- 23682 — Could not connect to the Kafka endpoint due to throttling happening on the destination.
- 23683 — Failed to send a message to AMQP endpoint.
- 23684 — The specified destination instance could not be found. Verify the destination_location parameter in the stream group configuration.
- 23685 — The message could not be sent because its size exceeds an AMQP broker limit.
- 23686 — Could not connect to the AMQP endpoint due to throttling happening on the destination.
- 23687 — Failed to verify access to the destination. Verify that SAS token is valid.
- 23688 — Could not connect to the destination due to an authentication error.
- 23689 — The request to the AMQP endpoint was not authorized. Verify that your credentials or access policy include the required permissions.
- 23690 — The request to the Kafka endpoint was not authorized. Verify that your credentials or access policy include the required permissions.
- 23691 — Failed to send a message to the requested topic. The SAS token provided when creating the credential is invalid.
- 23692 — Delivery of the message failed due to a timeout. Check if the broker is available and accessible over the network.
- 23693 — Request to the broker failed due to a timeout. Check if the broker is available and accessible over the network.
- 23694 — Unable to establish a secure connection to the broker.
- 23695 — The requested AMQP entity does not exist on the broker.
- 23696 — The AMQP resource was removed or disabled after a connection to the resource was established.
- 23697 — Failed to create Change Event Streaming stream group object. Destination location is not in the expected format. Expected format is [Event Hubs Namesp…
- 23698 — Aborting Change Event Streaming Publish task for partition %ld timed out. Change Event Streaming is not disabled. Retry this operation later.
- 23699 — Invalid table state encountered while processing Change Event Streaming table.
- 23701 — Database '%ls' went to suspect state. Backup cannot be performed on a database that is in suspect state.
- 23702 — Backup on participant is not allowed in SDA failover.
- 23801 — Change Event Streaming encountered an invalid UTF-8 encoding sequence.
- 23802 — Change Event Streaming credential not found.
- 23803 — Cannot drop the database scoped credential '%.*ls' because it is being used by a Change Event Streaming group.
- 23804 — Failed to check if credential is in use by a Change Event Streaming group.
- 23805 — %s is deprecated and will be removed in a future release. Use %s instead.
- 23806 — Could not find stream group or table with the provided stream_group_id and table_id, or source_schema and source_name.
- 23807 — Invalid parameter combination. When @table_id is provided, @stream_group_id must also be provided.
- 23808 — Cannot enable Change Event Streaming on database '%ls' because Data Recovery is enabled on this server. Combining Change Event Streaming with Data Rec…
- 23809 — Change Event Streaming Avro encoding failed.
- 23810 — Change Event Streaming encountered an invalid UTF-8 encoding sequence for column index %d.
- 23811 — Change Event Streaming structured Avro payload is enabled but table column metadata was not provided for schema generation.
- 23812 — Change Event Streaming operations history becomes available only after Change Event Streaming is enabled for the first time.
- 23813 — The loaded external Kafka library does not implement a function required by Change Event Streaming.
- 23814 — Change Event Streaming could not prepare the Microsoft Entra credential for destination authentication.
- 23815 — Warning: The @destination_type value '%ls' is deprecated and will be removed in a future update. Use 'AzureEventHubs' instead. The 'AzureEventHubs' de…
- 23996 — The request could not be performed because of an device I/O error.
- 23997 — System error occurred {ErrorCode: %d}.
- 23998 — Not enough memory available in the system to process the request.
- 23999 — Unspecified error(s) occurred.
- 24501 — Internal error when retrieving lock information. Please try the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 24502 — Failed to get db lock with error %d during redo operation.
- 24503 — Could not get clone tx ctx. Please try the operation again. If the problem persists contact Microsoft Azure Customer Support.
- 24504 — Alter of System table Columns are not allowed.
- 24505 — Table '%.*ls' already exists. Choose a different table name or rename the existing table.
- 24506 — Failed to find a TSRBRowGroupObject from the in-memory list
- 24507 — Index quality generation was aborted due to server shutdown.
- 24508 — The DB Version upgrade cannot modify user created data and metadata.
- 24509 — The DB Version upgrade cannot modify user created data and metadata. Index [%.*ls].[%.*ls] row with Key %ls was created by transactions '%I64d'.
- 24510 — Index maintenance operation complete: %d actions completed successfully in %d iterations with %d non-retriable errors and %d retriable errors encounte…
- 24511 — Cache db version too low
- 24512 — The requested SLO (%ls) for this pool exceeds the maximum allowed SLO (%ls).
- 24513 — You have already reached the limit of %ld SQL pools in this workspace.
- 24514 — You have already reached the limit of %ld SQL pools in this subscription.
- 24515 — Sum of SLOs for all pools in this workspace (%ls) plus the requested SLO for the new pool (%ls) exceeds the limit (%ls).
- 24516 — Sum of SLOs for all pools in this subscription (%ls) plus the requested SLO for the new pool (%ls) exceeds the limit (%ls).
- 24517 — The user provided a disallowed value for %ls for Auto-Pause. The value provided is %ld. The value must be between [%ld, %ld] or 0 (zero).
- 24519 — Internal error when resolving the DW temp table name during statement execution. Please try the operation again. If the problem persists contact Micro…
- 24520 — The metadata log for the database '%.*ls' is corrupted at Block '%I64d' RecordId '%I64d'.
- 24521 — The metadata log Block '%I64d' for the database '%.*ls' is not valid.
- 24522 — Read of the metadata log Block '%I64d' for the database '%.*ls' failed. Check errorlog for more info.
- 24523 — The metadata log Block was flushed to disk but the trnasaction aborted.
- 24524 — Failed to read or write the Max ASN data (HRESULT = 0x%x).
- 24525 — Internal error. Unable to gain access to the manifest file table. Result [%x]
- 24526 — Internal error. Unable to insert record to the manifest file table. Result [%x]
- 24527 — Internal error. Encounter unexpected error while writing manifest file
- 24528 — Attempt to commit the block list for a manifest file blob failed. Blob Prefix is "%ls", Blob name is "%ls". Storage Errorcode %ld.
- 24529 — There is not enough capacity to resize pool '%ls' to %ld backend instances.
- 24530 — Tenant ring selection failed while creating or activating a pool.
- 24531 — Internal error. Unable to gain access to the reference table. Result [%x]
- 24532 — Attempt to flush a manifest file blob failed. Blob Path is "%ls".
- 24533 — USE statement does not support switching to '%ls' database.
- 24534 — USE statement does not support switching to '%ls' database. Use a new connection to connect to '%ls' database.
- 24535 — Transactional data stored in physical metadata doesn't align with database transactional data.
- 24536 — Data insertion into Parquet-backed table failed.
- 24537 — Three-part names are not supported from '%ls' database to '%ls' database.
- 24538 — Internal error. Unable to gain access to the table-level write/write conflict table. Result [%x]
- 24539 — Failed to update physical metadata because of a file table transaction error.
- 24540 — Failed to update physical metadata because we could not read data from the temp table %d.
- 24541 — Failed to update physical metadata because of invalid file path present in row %d of temp table %d.
- 24542 — Failed to update physical metadata because of an unexpected file action present in row %d of temp table %d.
- 24543 — Cannot begin a transaction with the given isolation level. Please specify the snapshot isolation level when explicitly beginning the transaction.
- 24544 — The current isolation level isn't supported. Please change the transaction isolation level for this session to snapshot then re-run the operation.
- 24545 — An unexpected error occurred during Transcoder scan.
- 24546 — An unexpected error occurred during execution.
- 24547 — There was an error updating runtime physical metadata information needed to execute the statement.
- 24548 — A conversion error occurred during Transcoder scan.
- 24549 — Encountered internal error %d (of category '%ls') while attempting to process physical metadata.
- 24550 — Encountered operating system error %ls while attempting to write physical metadata.
- 24551 — Encountered operating system error %ls while attempting to read physical metadata.
- 24552 — Delete operation failed.
- 24553 — Invalid number of target backend instances for pool resize.
- 24554 — Pool is not in a valid state for resize.
- 24555 — Keep list for pool resize legth/content is invalid.
- 24556 — Snapshot isolation transaction aborted due to update conflict. Using snapshot isolation to access table '%.*ls' directly or indirectly in database '%.…
- 24557 — Internal error. Encountered an unexpected error while working with an internal table. Result [%x].
- 24558 — Failed physical metadata notification action '%ls' with result %lu for row %lu data from the temp table %ld.
- 24559 — Data Manipulation Language (DML) statements are not supported for this table type in this version of SQL Server.
- 24560 — Internal error. Encountered an issue removing physical metadata.
- 24561 — Internal error. Invalid physical metadata for CREATE TABLE operation.
- 24562 — Input not provided. Could not create vdw service principal. Please provide mandatory parameters to create service principal.
- 24563 — Invalid input. Could not create vdw service principal. The number of provided values does not match the mandatory parameters for the environment.
- 24564 — sp_get_min_xdes is unable to get and validate min xdes
- 24565 — sp_get_delta_lake_storage_properties is unable to return
- 24566 — Failed to update physical metadata with result %lu because of invalid partition values present in row %lu of temp table %ld.
- 24567 — Failed to parse '%ls' from physical metadata with result %lu for row %lu of temp table %ld.
- 24568 — Internal DW transaction error.
- 24570 — CREATE TABLE executed for the database %s without workspace on Trident instance. Normal for Witness databases
- 24571 — Failed to process extended property '%ls' for DB %ld table %ld. More details: %ls.
- 24572 — Commits up to '%ld' have already been applied for DB %ld table %ld. Skipped %lu/%lu row(s) of temp table %ld.
- 24573 — Invalid row group metadata for row group id "%ls".
- 24574 — The %ls '%ls' is not supported in this edition of SQL Server.
- 24575 — Manifest for DB %ld table %ld is not available, commit is not possible.
- 24576 — Table name cannot contain '%.*ls'.
- 24577 — Invalid column chunk metadata for column "%ls". Wrong parameter: %ls. Underlying data description: %ls.
- 24580 — Invalid value %d was provided for the DML config parameter %ls.
- 24581 — Global temporary tables and transient user tables in TEMPDB are not supported in this edition of SQL Server.
- 24583 — Enforced constraints are not supported. To create an unenforced constraint you must include the NOT ENFORCED syntax as part of your statement.
- 24584 — The %ls keyword is not supported in the %ls statement in this edition of SQL Server.
- 24585 — The specified ALTER TABLE statement is not supported in this edition of SQL Server.
- 24586 — Distributed transactions are not supported in this edition of SQL Server.
- 24590 — Encountered incompatible delete format.
- 24591 — An invalid value is present in the data.
- 24592 — Invalid metadata present in the file.
- 24593 — Internal error. Unable to Serialize Usage Data.
- 24594 — Internal error. Buffer is full.
- 24595 — SQL internal tasks encountered failure.
- 24596 — Failed to complete the command because the underlying location does not exist. Underlying data description: %ls.
- 24597 — An integer precision value between 0 and 6 must be specified.
- 24598 — Distributed temp tables are not supported in the master database. Switch to a user-created warehouse with USE <warehouse_name> and retry.
- 24599 — Failed to ingest data since a BE connection instead of FE connection was used.
- 24601 — A Native Shuffle storage provider for the URL '%ls' could not be found.
- 24602 — Error 0x%X - Could not allocate space while transferring data from one distribution to another.
- 24603 — Error 0x%X occurred when sending data over the network to another distribution. Please try to run the query again. If the error persists, please conta…
- 24604 — Error occurred when distribution %d wrote metadata for distribution %d. Please try to run the query again. If the error persists, please contact suppo…
- 24605 — The storage entity does not exist when transferring data from one distribution to another. If the error persists, please contact support.
- 24606 — The storage entity already exists when transferring data from one distribution to another. If the error persists, please contact support.
- 24607 — Error occurred when setting the owner for the storage location '%ls'. If the error persists, please contact support.
- 24608 — Storage location for transfering data to another distribution is not defined. If the error persists, please contact support.
- 24609 — Error 0x%X occurred while trying to access data exceeding the permitted limit. If the error persists, please contact support.
- 24610 — Unsupported data movement functionality was used. If the error persists, please contact support.
- 24611 — Data movement temporary table metadata is invalid. If the error persists, please contact support.
- 24612 — Data movement location is invalid. If the error persists, please contact support.
- 24613 — Data movement content validation failed. Rows Expected: %d Actual %d; Bytes Expected: %d Actual %d.
- 24614 — Error 0x%X occurred while reading metadata from storage for source distribution %d and target distribution %d. Please try to run the query again. If t…
- 24615 — Data movement content validation failed. Rows Expected: %I64u Actual %I64u.
- 24701 — The query failed because the access is denied on %ls.
- 24702 — The query failed because the following location is changed during the query execution: %ls.
- 24703 — The query failed because an unexpected error occurred in distributed query processing phase. File a support ticket and provide the error code and stat…
- 24704 — The query processor ran out of internal resources. Underlying data description: %ls.
- 24705 — Error when converting partition column value '%ls' to '%ls' column type.
- 24706 — Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table '%.*ls' directly or indirectly in dat…
- 24707 — There was an error reading runtime physical metadata information needed to execute the statement.
- 24708 — '%ls' is an unsupported partition column type.
- 24709 — There are null values present in the column which was specified as 'not null'.
- 24710 — There is insufficient system memory to read the data: %ls.
- 24711 — The query failed because parquet file is corrupted and cannot be deserialized while attempting to read it from the location: %ls.
- 24712 — The query failed because parquet file is corrupted and cannot be deserialized while attempting to read it from the location: %ls.
- 24713 — Oredered index is not supported.
- 24714 — Unexpected Error in DW FrontEnd Stress Testing.
- 24715 — The specified ordered column count %d is greater than the maximum ordered column count %d.
- 24716 — sp_get_managed_delta_table_log_files_metadata is unable to generate the output xml.
- 24717 — sp_check_file_cleanup_eligibility is unable to generate the output resultset.
- 24718 — Lakehouse tables cannot be renamed from the SQL Endpoint. Please use the Lakehouse to rename tables.
- 24719 — sp_trigger_expired_files_cleanup is unable to trigger the system event for expired files cleanup.
- 24720 — Internal error. Unable to interact with an internal metadata table. Please try the operation again and contact Customer Support Services if this persi…
- 24721 — The operation could not be completed due to I/O error. This error can occur when the file size defined in the metadata (or delta log) is larger than t…
- 24722 — The remote storage service is not active or available at this time (HTTP 500). This could be a temporary issue. Please try the operation one more time…
- 24723 — The operation has timed out (HTTP 503) due to a lack of response from the remote storage service. This could be a temporary issue. Please try the oper…
- 24724 — Cannot bulk load because of an error writing file. Underlying data description: %ls.
- 24725 — Data Compaction is only supported for warehouse databases.
- 24726 — Service is currently experiencing high demand and is unable to process your request at this time. Please try again later, as retrying may help.
- 24727 — Table name cannot end with '.'.
- 24728 — Schema name cannot contain '%.*ls'.
- 24729 — Schema name cannot end with '.'.
- 24730 — The operation encountered an HTTP error while trying to read data. This could be a temporary issue. Please try the operation one more time. Underlying…
- 24731 — The specified clustering column count %d is greater than the maximum clustering column count %d.
- 24732 — CLUSTER BY is not supported.
- 24733 — An unexpected error occurred during execution.
- 24734 — There was an error during stored procedure execution.
- 24735 — Only nullable columns can be added to an existing table.
- 24736 — There are multiple empty string indexes present in the dictionary. Column name: '%ls'.
- 24737 — Data Lake Log publishing is supported only for warehouse databases.
- 24738 — There was an error reading runtime ingestion information needed to execute the statement.
- 24739 — No statistics exist for clustering column at ordinal %lu.
- 24740 — VORDER is supported only for warehouse databases.
- 24741 — Identity column '%.*ls' must be of data type BIGINT.
- 24742 — Identity column '%.*ls' does not support specifying SEED or INCREMENT.
- 24743 — An error occurred while attempting to update discovered table properties.
- 24744 — StringCchCopyNW failed with HRESULT = 0x%x.
- 24745 — Found column mapping properties, but no column mapping values.
- 24746 — The MaxColumnId value %u is less than the number of column mappings %lu.
- 24747 — The MaxColumnId %u is less than column with field ID value %u.
- 24748 — The 'MaxColumnId' value %u is out of bounds.
- 24749 — The column mapping 'Id' value %u is out of bounds.
- 24750 — Found %lu column mapping values, but did not find the required column mapping properties.
- 24751 — Found duplicate column mapping id = %lu.
- 24752 — Found duplicate column mapping logical name = '%ls'.
- 24753 — Found duplicate column mapping physical name = '%ls'.
- 24754 — An internal error occurred when truncating table '%.*ls'.
- 24755 — An internal error occurred when truncating user table.
- 24756 — The query failed because handling end of file happened before whole IO buffer was populated: %ls.
- 24757 — Could not create table '%.*ls' because the type (collation) of the column '%.*ls' is not supported in a table with Data Clustering.
- 24758 — sp_cleanup_dropped_table_metadata is unable to clean up internal metadata for the trident DW table.
- 24759 — Data insertion into Parquet-backed table failed (%d,%ls).
- 24760 — The file is temporarily unavailable due to a high number of requests in the lake. This is a transient issue. Please try again shortly. Underlying data…
- 24761 — There are null values present in the partition column '%ls' which was specified as 'not null'.
- 24762 — Error converting values NaN or Infinity to type '%ls' in the column '%ls'. NaN and Infinity are not supported. Underlying data description: %ls.
- 24763 — There was an error reading column mapping information for column: '%ls'.
- 24764 — No histogram steps exist for clustering column at ordinal %lu. Please check the content of the table.
- 24765 — %ld rows processed for compaction did NOT match %ld rows from the source.
- 24766 — TIMESTAMP can only be set for snapshot databases.
- 24767 — CREATE DATABASE AS SNAPSHOT OF supported only for DataWarehouse.
- 24768 — TIMESTAMP is invalid or missing in the DDL statement.
- 24769 — Internal error with lock serialization logic during DW pre-commit transactional metadata handling.
- 24770 — Identity %.*ls value %I64d is out of range. Value must be between 0 and (2^%d - 1). Retry may not help. Please contact Microsoft support.
- 24771 — The %.*ls JSON parameter %.*ls is missing or incorrectly formatted. Please check the formatting of the JSON.
- 24772 — Failed to initialize TempDB.
- 24773 — The query failed because the file is too small. Underlying data description: %ls.
- 24774 — Internal error occurred during DW table metrics retrieval.
- 24775 — Internal system error (%ls) when attempting to open or create remotely stored delta log file. This error is usually intermittent. Please try the opera…
- 24776 — The current version of data being accessed in [%s] is as of timestamp '%s'.
- 24777 — TIMESTAMP must not be before the source database was created. Creation timestamp: '%s', specified timestamp: '%s'.
- 24778 — Internal error occurred during Trident DW mix-mode query execution.
- 24779 — The specified ALTER TABLE statement is not supported in this edition of SQL Server. Columns that are part of a data clustered index may not be dropped…
- 24780 — Columns in this type of table cannot be renamed.
- 24781 — Desired column data type: '%ls' is not supported, please retry column creation with a supported data type.
- 24782 — Internal error occurred during Trident DW DDL Operations.
- 24783 — Invalid column mapping metadata.
- 24784 — An error occurred while communicating with an external component. Underlying data description: %ls.
- 24785 — Internal error occurred when attempting to read physical metadata.
- 24786 — Unable to process insertion into table '%ls' with identity column. Please wait for other active transactions to abort or commit, then retry.
- 24787 — Internal error occurred during execution of the command.
- 24788 — Error occurred while attempting to read a deletion vector.
- 24789 — Insertion of timestamp for column '%ls' failed. The allowed SQL range is from '0001-01-01' to '9999-12-31', but the provided date is '%ls'. Underlying…
- 24790 — Insertion of timestamp for column '%ls' failed. The allowed SQL range for hundreds of nanoseconds from midnight is from '0' to '863999999999', but the…
- 24791 — An unexpected error occurred during the execution of the distributed temp table operation.
- 24792 — Table '%ls' with classification '%ls' is not eligible for maintenance operation.
- 24793 — Refresh is only available for external tables.
- 24794 — Type mismatch between table schema and physical metadata.
- 24795 — Unexpected physical metadata file name %ls.
- 24796 — Refresh cannot be called inside an existing transaction.
- 24797 — Table in database '%d' with object ID '%d' and classification '%ls' is not a valid DML target.
- 24798 — Internal error. Unable to interact with an internal metadata table. Please try the operation again and contact Customer Support Services if this persi…
- 24799 — Cloning an external table is not supported.
- 24801 — Internal error. Unable to interact with the internal metadata of an external table due to the following reason: %ls
- 24802 — Table snapshot generation failure during file elimination using file-level statistics. NaN and Infinity are not supported.
- 24803 — Encountered failure during database upgrade of internal tables.
- 24804 — This stored procedure supports only one-part or two-part names. Please use either [table] or [schema].[table].
- 24805 — Column '%s' of type '%s' could not be validated with the underlying table. Reason: %s.
- 24806 — Unexpected JSON data during parsing attempt in column type inference. Underlying data description: '%ls'
- 24807 — Cannot parse unquoted JSON value in the property '%ls'. Valid unquoted values can be true, false, null, and numbers. Underlying data description: '%ls…
- 24808 — Cannot convert a string value found in the JSON text to binary value because it is not Base64 encoded.
- 24809 — One or more log or checkpoint files have been deleted or overwritten. No operations can be performed on the external table. Please recreate the extern…
- 24810 — Updating source database is not supported.
- 24811 — SOURCE_DATABASE can only be altered only for warehouse snapshots in LIVE mode.
- 24812 — Setting SOURCE_DATABASE failed.
- 24813 — Specifying an explicit value for the identity column '%.*ls' in table '%.*ls' is not supported.
- 24814 — Retrieving table storage path failed.
- 24815 — Ingestion failed because the total LOB size (%I64u) bytes of the current row exceeds the defined limit (%I64u) bytes.
- 24816 — An unexpected error related to collations occurred.
- 24817 — Unsupported collation version.
- 24818 — Columns %ls and %ls in the delta log are incompatible for the given catalog collation.
- 24819 — Data compaction aborted because of a concurrent user update, delete, or merge operation on the target table.
- 24820 — Can't access column '%s' right now because it does not exist in the underlying table.
- 24821 — Internal error occurred during DW table row change summary retrieval.
- 24822 — Operation failed because the destination '%ls' is not permitted. It must be in the allowed list or within the workspace. Please contact your workspace…
- 24823 — The maximum delta log version allowed is 9,223,372,036,854,775,807.
- 24824 — Unknown or incorrectly formatted field '%.*ls' in JSON parameter '%.*ls'. Check the formatting and values of the JSON.
- 24825 — Scan failed because the total LOB size (%I64u) bytes of the current row exceeds the defined limit (%I64u) bytes.
- 24826 — Can't query column '%s' because data type '%s' isn't supported.
- 24827 — Can't access column '%ls' right now because the column's type in the underlying table doesn't match.
- 24828 — Identity column '%.*ls' cannot be designated as a clustering column on a clustered table.
- 24829 — Collated string '%.*ls' contains an invalid UTF-8 codepoint.
- 24830 — Configuration setting operation failed because '%.*ls' (package='%.*ls', section='%.*ls', setting='%.*ls').
- 24831 — Can't access the table because the metadata contains absolute file paths. Create the table again using relative file paths.
- 24832 — The table metadata contains an unsupported deletion vector type.
- 24833 — The length of the partition column string exceeds the maximum allowed length of %d characters.
- 24834 — The length of the partition column name that starts with '%.*ls' exceeds the maximum allowed length of %d characters.
- 24835 — The specified table location is invalid or not accessible.
- 24836 — Partition columns must remain the same. Column changed: %ls. Partition column existed at table creation: %d. Partition column found in delta log: %d.
- 24837 — Column segment has overflown as a result of wrong row group metadata (num_rows) which was read from the file. Expected row count: %ls. Actual row coun…
- 24838 — Error encountered while parsing JSON data: '%ls'. Underlying data description: %ls.
- 24839 — sp_get_clone_island_table_metadata is unable to generate output metadata.
- 24840 — Duplicate entry in the list of scanned files for file: '%ls'. Check delta log for duplicate entries.
- 24841 — The specified ALTER COLUMN operation is not supported in this edition of SQL Server. %ls.
- 24842 — There was an internal fatal error when processing identity column values.
- 24843 — There are missing column segments in the column which was specified as 'not null'.
- 24844 — Action cannot be completed because you cannot ALTER a non distributed temp table in an explicit user transaction. Use a distributed temporary table fo…
- 24845 — The specified ALTER COLUMN operation requires data validation or rewrite, so it is currently not supported in this edition of SQL Server.
- 24846 — Could not access column '%s', because it utilizes unsupported feature '%s'.
- 24847 — Clustered constraints are not supported. To create a nonclustered constraint you must include the NONCLUSTERED clause as part of your statement.
- 24848 — The table schema does not match the underlying data source.
- 24849 — Service Fabric Property with name %ls does not exist.
- 24850 — Reading of Service fabric property is not allowed under test mode (property='%ls')
- 24851 — Invalid num_rows present in row group metadata. %ls. Underlying data description: %ls.
- 24852 — Can't access the table as the latest checkpoint is a V2 checkpoint that isn't supported.
- 24853 — The table is blocked and cannot be interacted with.
- 24854 — Explicit value must be specified for identity column in table '%.*ls' when IDENTITY_INSERT is set to ON.
- 24855 — A wrong number of tables were provided to the refresh operation.
- 24856 — The element in position %d of the JSON array does not have the expected type '%ls'.
- 24857 — DBCC CHECKIDENT is not supported in Fabric DW.
- 24858 — DBCC CHECKIDENT RESEED with reseed value is not supported in Fabric DW.
- 24859 — DBCC CHECKIDENT with NORESEED option is not supported in Fabric DW.
- 24860 — The table contains a deletion vector, but the corresponding add-file action is missing a valid 'numRecords' entry in 'stats'.
- 24861 — Table snapshot for '%s' contains duplicate data parquet file path with different deletion vector descriptors. Does not comply with Delta protocol.
- 24862 — No delta log or checkpoint found at the specified table location.
- 24863 — The operation failed because the table has too many delta logs since the last checkpoint. Create a new checkpoint and retry the operation.
- 24864 — DBCC CHECKIDENT RESEED for table '%ls' failed. Please try the operation again and contact Customer Support Services if the problem persists.
- 24865 — Can't access the table as one or more delta log files have been deleted.
- 24866 — Internal error occurred during table data distribution metrics retrieval.
- 24867 — Error encountered while validating '%ls' fabric property refresh implementation.
- 24868 — The operation failed because the table has too many files in the delta log folder after _last_checkpoint, or _last_checkpoint does not exist. Create a…
- 24869 — The JSON manifest file size exceeds the maximum allowed limit. The file size must not exceed %I64u bytes.
- 24870 — The table schema does not include all the columns supported and defined in the underlying data source.
- 24871 — Internal stand alone SI transaction failed.
- 24872 — Internal error. Redirection for proxy database failed.
- 24873 — No active distributed query found for the specified distributed_statement_id '%ls'. The query may have completed or is not a distributed query.
- 24874 — We couldn't access the underlying data source because you don't have sufficient permissions. Make sure you have access and then try again.
- 24875 — We couldn't access the underlying data source. Check your permission to the data source. If you have the right permission then try again later.
- 24876 — This stored procedure is part of a feature that is not yet available in your environment. If this is unexpected, please contact support.
- 24877 — MDSync provided an invalid commit id. Discovered table id: %d. Temp table id: %d.
- 24878 — Internal error occurred during DW table checksum creation. '%ls'
- 24879 — Internal error occurred during sp_dw_create_table_checksum execution.
- 24880 — The TIMESTAMP in the query (%ls) is before the earliest data was available.
- 24881 — DBCC CHECKIDENT for table '%ls' failed due to Sch-M table lock in current transaction and conflict with concurrent transaction.
- 24882 — No histogram steps exist for clustering column at ordinal %lu because the target table is empty.
- 24883 — Internal error occurred while processing the Trident identity insert sentinel value.
- 24884 — DBCC CHECKIDENT is not supported on a database snapshot in Fabric DW.
- 24885 — Cannot access the external table because a shortcut transform is still in progress. Please wait for the transform to complete and try again.
- 24886 — Cannot access the external table because the shortcut transform failed. Please recreate the external table.
- 24887 — Internal Trident DW test failpoint. The error state identifies the specific failpoint site.
- 24888 — Bulk copy into a temporary table '%.*ls' is not supported in Fabric DW. Bulk copy into a regular (non-temporary) table instead.
- 24889 — Failed to open or create the remotely stored delta log file. %ls
- 24890 — The table schema could not be upgraded to the latest delta log version. Check sys.dm_db_external_tables_log_status for more information.
- 24891 — The LOCATION value is not a valid JSON shortcut definition. Reason: %ls.
- 24892 — Failed to create the shortcut. Error code: '%ls'. Error message: '%ls'.
- 24893 — Failed to drop the shortcut. Error code: '%ls'. Error message: '%ls'.
- 24894 — Schema reconciliation could not be completed. %.*ls Remove the dependency and run sp_dw_refresh_ext_table again.
- 24895 — Fabric Catalog is not enabled on this workspace.
- 24896 — The Fabric Catalog %.*ls parameter must not be empty.
- 24897 — The Fabric Catalog %.*ls parameter exceeds the maximum identifier length of %d characters.
- 24898 — Procedure %ls requires all arguments to be passed by name.
- 24899 — The @transaction_id and @fencing_token parameters must both be supplied together or both omitted.
- 24901 — Fabric DW BCP failed due to an internal error.
- 24902 — An internal error occurred while creating a table checkpoint. Retry the operation and contact support if the problem persists.
- 24903 — Fabric Catalog operations are only valid against unified user tables.
- 24904 — An internal error occurred while processing row-level security information.
- 25002 — The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is correct, …
- 25003 — Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database.
- 25005 — It is invalid to drop the default constraint on the rowguid column that is used by merge replication.
- 25006 — The new column cannot be added to article '%s' because it has more than %d replicated columns.
- 25007 — Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending sch…
- 25008 — The merge replication views could not be regenerated after performing the data definition language (DDL) operation.
- 25009 — Invalid value '%s' specified while executing sp_changemergearticle on article '%s' for the 'identityrangemanagementoption' property.
- 25010 — The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle @publication , @arti…
- 25012 — Cannot add an identity column since the table is published for merge replication.
- 25013 — Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than '90RTM'. Us…
- 25014 — sp_repladdcolumn does not allow adding columns of datatypes that are new to this release.
- 25015 — Schema Changes and Bulk Inserts
- 25016 — Prepare Dynamic Snapshot
- 25017 — Failed to execute the command "%s" through xp_cmdshell. Detailed error information is returned in a result set.
- 25018 — Precomputed partitions cannot be used because articles "%s" and "%s" are part of a join filter and at least one of them has a constraint with a CASCAD…
- 25019 — The logical record relationship between articles "%s" and "%s" cannot be added because at least one of the articles has a constraint with a CASCADE ac…
- 25020 — The article cannot be created on table '%s' because it has more than %d columns and column-level tracking is being used. Either reduce the number of c…
- 25021 — Replication stored procedure sp_MSupdategenhistory failed to update the generation '%s'. This generation will be retried in the next merge.
- 25022 — The snapshot storage option (@snapshot_storage_option) must be 'file system', or 'database'.
- 25023 — Stored procedures containing table-value parameters cannot be published as '[serializable] proc exec' articles.
- 25024 — A snapshot storage option of 'database' is incompatible with the use of character mode bcp for snapshot generation.
- 25025 — Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse colu…
- 25026 — The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is n…
- 25027 — Cannot find a credential for Windows login '%s'. Replication agent job sync needs a credential to be pre-created in all availability group replicas fo…
- 25028 — Cannot specify 'database_name' when 'all' is set to 1.
- 25029 — Replication distribution database '%s' is not in the primary replica of its availability group.
- 25030 — Replication distribution database '%s' is not in an availability group.
- 25031 — Monitor and sync replication agent jobs
- 25032 — Sync replication agent jobs and their enabled states.
- 25033 — The distribution database is part of an availability group without a listener. Add a listener to the availability group before adding publication, sub…
- 25034 — Distribution database in availability group is only supported for publisher_type as MSSQLSERVER.
- 25035 — When distribution database is part of availability group, then distributor and publisher server cannot be same.
- 25036 — Distribution database needs to be in readable state on secondary replica, when distribution database is part of availability group.
- 25037 — The @subscriber parameter must be either @@SERVERNAME or listener name of the availability group that the subscriber database is part of.
- 25038 — User needs to have VIEW SERVER STATE permission to assign @subscriber as the listener name of the availability group.
- 25039 — Assigning listener name for @subscriber parameter is not a supported scenario for Managed Instance.
- 25040 — Assigning the default value to "%ls": %ls.
- 25100 — Storage is unavailable.
- 25101 — Provided lease is broken.
- 25102 — Lease was already released.
- 25103 — Incompatible lease mode.
- 25104 — Invalid parameter.
- 25105 — Error occurred when writing data to another distribution. Please try to run the query again. If the error persists, please contact support.
- 25106 — An internal error occurred when writing data to another distribution. Please try to run the query again. If the error persists, please contact support…
- 25107 — Error occurred when reading data from another distribution. Please try to run the query again. If the error persists, please contact support.
- 25108 — Insufficient storage capacity when processing data moved between distributions. Please try to run the query again. If the error persists, please conta…
- 25109 — The invoked functionality has not been implemented.
- 25110 — Error occurred when deleting transferred data. Please try to run the query again. If the error persists, please contact support.
- 25111 — An internal error occurred while accessing a TLS key. Please try to run the query again. If the error persists, please contact support.
- 25112 — An internal error occurred when writing data to another distribution. Please try to run the query again. If the error persists, please contact support…
- 25113 — Insufficient storage capacity when processing data moved between distributions. Please try to run the query again. If the error persists, please conta…
- 25114 — Error occurred when reading data from another distribution. Please try to run the query again. If the error persists, please contact support.
- 25115 — Error occurred when reading data from another distribution. Please try to run the query again. If the error persists, please contact support.
- 25507 — Invalid number of arguments passed to unit test '%ls'.
- 25601 — The Extended Event engine is out of memory.
- 25602 — The %S_MSG, "%.*ls", encountered a configuration error during initialization. Object cannot be added to the event session. %ls
- 25603 — The %S_MSG, "%.*ls", could not be added. The maximum number of singleton targets has been reached.
- 25604 — The Extended Event engine is disabled.
- 25605 — The %S_MSG, "%.*ls", could not be added. The maximum number of packages has been reached.
- 25606 — The Extended Event engine could not be initialized. Check the SQL Server error log and the operating system error log for information about possible r…
- 25607 — The Extended Event engine has been disabled by startup options. Features that depend on Extended Events may fail to start.
- 25608 — The Extended Event engine could not allocate record for local thread/fiber.
- 25623 — The %S_MSG name, "%.*ls", is invalid, or the object could not be found
- 25624 — The constraints of %S_MSG name, "%.*ls", have been violated. The object does not support binding to actions or predicates. Event not added to event se…
- 25625 — The %S_MSG, "%.*ls", already exists in the event session. Object cannot be added to the event session.
- 25626 — The %S_MSG, "%.*ls", was specified multiple times.
- 25629 — For %S_MSG, "%.*ls", the customizable attribute, "%ls", does not exist.
- 25630 — The predicate expression bound to %S_MSG ,"%.*ls", has mismatching types.
- 25631 — The %S_MSG, "%.*ls", already exists. Choose a unique name for the event session.
- 25632 — The specified buffer size is less than the minimum size. The minimum allowed size is %d bytes.
- 25633 — The buffer size specified exceeds the maximum size.
- 25634 — The dispatch latency specified is below the minimum size.
- 25635 — An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be added to a session, the sess…
- 25636 — Source and comparator types of the predicate do not match.
- 25639 — The %S_MSG, "%.*ls", exceeds the number of allowable bound actions.
- 25640 — Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0.
- 25641 — For %S_MSG, "%.*ls", the parameter "%ls" passed is invalid. %ls
- 25642 — Mandatory customizable attributes are missing for %S_MSG, "%.*ls".
- 25643 — The %S_MSG, "%.*ls", can not be added to an event session that specifies no event loss.
- 25644 — The %S_MSG, "%.*ls", cannot be bound to the event session.
- 25646 — The %S_MSG name, "%.*ls", is invalid.
- 25647 — The %S_MSG, "%.*ls", could not be found. Ensure that the object exists and the name is spelled correctly.
- 25648 — The %S_MSG, "%.*ls", could not be found. Ensure that the package exists and the name is spelled correctly.
- 25649 — Two of the actions/predicates for %S_MSG, "%.*ls", can not coexist. Please remove one.
- 25650 — For %S_MSG, "%.*ls" the customizable attribute, "%ls", was specified multiple times.
- 25651 — For %S_MSG, "%.*ls", the value specified for customizable attribute, "%ls", did not match the expected type, "%ls".
- 25653 — The %S_MSG, "%.*ls", does not exist in the event session. Object cannot be dropped from the event session.
- 25654 — Insuficient buffer space to copy error message.
- 25655 — Internal Extended Event error: invalid message code.
- 25656 — Error validating action. %ls
- 25657 — Error validating predicate. %ls
- 25658 — The %S_MSG name "%.*ls" is not unique.
- 25659 — The %S_MSG, "%.*ls", encountered a configuration error during initialization. The customizable attribute %ls is used internally only.
- 25664 — Internal Extended Event error: invalid package ID.
- 25665 — This target does not support the NO_EVENT_LOSS event retention mode. The ALLOW_SINGLE_EVENT_LOSS retention mode is used instead.
- 25666 — The %S_MSG "%.*ls" exceeds the maximum number of target parameters or event customizable attributes.
- 25699 — The Extended Event engine failed unexpectedly while performing an operation.
- 25701 — Invalid event session name "%.*ls". Temporary event sessions are not allowed.
- 25702 — The event session option, "%.*ls", is set more than once. Remove the duplicate session option and re-issue the statement.
- 25703 — The event session option, "%.*ls", has an invalid value. Correct the value and re-issue the statement.
- 25704 — The event session has already been stopped.
- 25705 — The event session has already been started.
- 25706 — The %S_MSG, "%.*ls", could not be found.
- 25707 — Event session option "%.*ls" cannot be changed while the session is running. Stop the event session before changing this session option.
- 25708 — The "%.*ls" specified exceeds the maximum allowed value. Specify a smaller configuration value.
- 25709 — One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems…
- 25710 — Event session "%.*ls" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
- 25711 — Failed to parse an event predicate.
- 25712 — An invalid comparison operator was specified for an event predicate.
- 25713 — The value specified for %S_MSG, "%.*ls", %S_MSG, "%.*ls", is invalid.
- 25715 — The predicate on event "%ls" is invalid. Operator '%ls' is not defined for type "%ls", %S_MSG: "%.*ls".
- 25716 — The predicate on event, "%.*ls", exceeds the maximum length of %d characters.
- 25717 — The operating system returned error %ls while reading from the file '%s'.
- 25718 — The log file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it.
- 25719 — Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query.
- 25720 — 'sys.fn_xe_file_target_read_file' is skipping records from "%.*ls" at offset %I64d.
- 25721 — The metadata file name "%s" is invalid. Verify that the file exists and that the SQL Server service account has access to it.
- 25722 — The offset %I64d is invalid for log file "%s". Specify an offset that exists in the log file and retry your query.
- 25723 — An error occurred while obtaining metadata information from the file "%s". The file may be damaged.
- 25724 — Predicate too large for display.
- 25725 — An error occurred while trying to flush all running Extended Event sessions. Some events may be lost.
- 25726 — The event data stream was disconnected because there were too many outstanding events. To avoid this error either remove events or actions from your s…
- 25727 — The Extended Events session named "%.*ls" has either been stopped or dropped and can no longer be accessed.
- 25728 — The Extended Events session named "%.*ls" could not be found. Make sure the session exists and is started.
- 25729 — The event data stream was disconnected due to an internal error.
- 25730 — The Extended Events session named "%.*ls" was modified during the upgrade and one of the bucketizer targets was excluded from the Extended Events sess…
- 25731 — Execution of event session state change request failed on remote brick. Event session name: "%.*ls". Refer to previous errors to identify the cause, a…
- 25732 — One or more event sessions failed to reconcile their runtime states. Refer to previous errors in the current session to identify the cause, and correc…
- 25733 — Event session "%.*ls" failed to reconcile its runtime state. Refer to previous errors in the current session to identify the cause, and correct any as…
- 25734 — The file pattern "%s" represents a full path. Use only relative paths with no drive letters.
- 25735 — The source option %d is invalid.
- 25736 — A damaged buffer was found in file "%s" at offset %I64d, no further events will be read from the file.
- 25737 — Database scoped extended event sessions are not available in server scope or system databases in Azure DB.
- 25738 — Event session '%.*ls' could not be started because system is currently busy. Please try again later.
- 25739 — Failed to start event session '%.*ls' because required credential for writing session output to Azure blob is missing.
- 25740 — Unable to start event session '%.*ls' because system is busy. Please try again later.
- 25741 — The URL specified for %S_MSG "%.*ls", %S_MSG "%.*ls" is invalid. URL must begin with 'https://' .
- 25742 — Target '%.*ls' is not available for Azure SQL Database.
- 25743 — The event '%.*ls' is not available for Azure SQL Database.
- 25744 — The action '%.*ls' is not available for Azure SQL Database.
- 25745 — Unable to retrieve Azure SQL Database telemetry data.
- 25746 — Operation failed. Operation will cause database %S_MSG memory to exceed allowed limit. Event session memory may be released by stopping active session…
- 25747 — Operation failed. Operation will cause database %S_MSG memory to exceed allowed limit. Event session memory may be released by stopping active session…
- 25748 — The file "%s" contains audit logs. Audit logs can only be accessed by using the fn_get_audit_file function.
- 25749 — Target '%.*ls' is not available on SQL Database Managed Instance.
- 25750 — Event '%.*ls' is not available on SQL Database Managed Instance.
- 25751 — Action '%.*ls' is not available on SQL Database Managed Instance.
- 25752 — Auto start XE sessions are disabled.
- 25753 — XE session '%s' started.
- 25754 — XE session '%s' stopping.
- 25755 — Could not create live session target because live session targets are disabled.
- 25756 — Could not create stream XEL file because that functionality is disabled.
- 25757 — Could not stop orphan session (session which is running but has no definition in metadata) with name '%s'
- 25758 — The ALTER EVENT SESSION FOR SECONDARY command can only be executed on the primary replica. Connect to the primary replica of this database, and try ag…
- 25759 — Network Security Perimeter (NSP) blocked outbound access to the storage URL '%s'. The NSP configuration does not allow reading from the specified loca…
- 26010 — The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %#x. Check certificates to make sur…
- 26011 — The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security…
- 26012 — The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technica…
- 26013 — The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption.
- 26014 — Unable to load user-specified certificate [Cert Hash(sha1) "%hs"]. The server will not accept a connection. You should verify that the certificate is …
- 26015 — Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You shoul…
- 26017 — Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
- 26018 — A self-generated certificate was successfully loaded for encryption.
- 26022 — Server is listening on [ %s <%s> %d].
- 26023 — Server TCP provider failed to listen on [ %s <%s> %d]. Tcp port is already in use.
- 26024 — Server failed to listen on %s <%s> %d. Error: %#x. To proceed, notify your system administrator.
- 26025 — HTTP authentication succeeded for user '%.*ls'.%.*ls
- 26026 — HTTP authentication failed.%.*ls
- 26027 — Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.
- 26028 — Server named pipe provider is ready to accept connection on [ %s ].
- 26029 — Server named pipe provider failed to listen on [ %s ]. Error: %#x
- 26032 — Server VIA provider is ready for clients to connect to [ %hs:%d ].
- 26033 — Server VIA provider failed to initialize. Error: %#x
- 26034 — The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termi…
- 26035 — The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x…
- 26037 — The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: %#x, sta…
- 26038 — The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Admi…
- 26039 — The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.
- 26040 — Server TCP provider has stopped listening on port [ %d ] due to an AcceptEx failure. Socket error: %#x, state: %d. The server will automatically attem…
- 26041 — Server TCP provider has successfully reestablished listening on port [ %d ].
- 26042 — Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
- 26043 — Server HTTP provider has successfully reestablished listening.
- 26044 — Server named pipe provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestabli…
- 26045 — Server named pipe provider has successfully reestablished listening on [ %s ].
- 26048 — Server local connection provider is ready to accept connection on [ %s ].
- 26049 — Server local connection provider failed to listen on [ %s ]. Error: %#x
- 26050 — Server local connection provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-…
- 26051 — Server local connection provider has successfully re-established listening on [ %s ].
- 26052 — SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is…
- 26053 — SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x…
- 26054 — Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relations…
- 26055 — The SQL Server failed to initialize VIA support library [%hs]. This normally indicates the VIA support library does not exist or is corrupted. Please …
- 26056 — Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port th…
- 26057 — Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network con…
- 26058 — A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.
- 26059 — The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
- 26060 — The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
- 26061 — Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem wi…
- 26062 — Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.
- 26063 — Warning: Support for the VIA protocol is deprecated and will be removed in a future version of Microsoft SQL Server. If possible, use a different netw…
- 26064 — SQL Server could not listen on IP address [%s] because the cluster resource '%s' is not online (state = %d). This is an informational message and may …
- 26065 — Extended Protection for the SQL Server Database Engine is enabled, but the operating system does not support Extended Protection. Connection attempts …
- 26066 — An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Integrated Authentication might fa…
- 26067 — The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Windows return code: …
- 26068 — The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Error: %#x, state: …
- 26069 — Started listening on virtual network name '%ls'. No user action is required.
- 26070 — Stopped listening on virtual network name '%ls'. No user action is required.
- 26071 — Failed to load the Cluster Resource Libraries: clusapi.dll and resutils.dll. SQL Server will be unable to accept TCP connections on clustered listener…
- 26072 — Found multiple dependent virtual network names for the Windows Failover Cluster Resource '%ls'. SQL Server will only listen on the first virtual netwo…
- 26073 — Failed to clean up event associated with TCP connection, this is most likely because the server was under heavy load. Operating system return code: %#…
- 26075 — Failed to start a listener for virtual network name '%ls'. Error: %d.
- 26076 — SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a S…
- 26077 — An asynchronous read has timed out
- 26078 — Client disconnected during login
- 26079 — Server TCP provider has stopped listening on port [ %d ] due to a CreateSocket failure. Error: %#x, state: %d. The server will automatically attempt t…
- 26080 — DISTRIBUTED_NETWORK_NAME is defined for FCI, listen to all IP addresses. No user action is required.
- 26081 — DISTRIBUTED_NETWORK_NAME is NOT defined for FCI, listen to VNN IP address. No user action is required.
- 26082 — DISTRIBUTED_NETWORK_NAME probing failed for cluster group [ %ls ] with error code %#x.
- 26083 — DISTRIBUTED_NETWORK_NAME probing failed with error code %#x.
- 26084 — Started listening on listener network name '%ls' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required.
- 26085 — Stopped listening on listener network name '%ls' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required.
- 26086 — A dead session is detected and closed, the connect id is '%ls'. No user action is required.
- 26087 — A Attn token is received, the session id is '%d', No user action is required.
- 26088 — SSL/TLS certificate info - state: %d.
- 26089 — %ls operation failed for [%ls] with status 0x%x.
- 27001 — Reserved error message. Should never be issued.
- 27002 — A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection.
- 27003 — Bad token encountered during tokenization.
- 27004 — Unexpected token type encountered during tokenization.
- 27005 — Error Tolerant Index is corrupt.
- 27006 — Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt.
- 27007 — Attempt to delete from empty ridlist. Error Tolerant Index is corrupt.
- 27008 — rid to be deleted not found in rid-list. Error Tolerant Index is corrupt.
- 27009 — Error Tolerant Index frequencies must be non-negative. Error Tolerant Index is corrupt.
- 27010 — Attempt to insert row whose ID is already present. Error Tolerant Index is corrupt.
- 27011 — No ridlist provided for appending. Error Tolerant Index is corrupt.
- 27012 — Cannot delete token. Error Tolerant Index is corrupt.
- 27013 — Tokenizer object has no delimiter set. Error Tolerant Index is corrupt.
- 27014 — Deletion failed because token does not occur in index. Error Tolerant Index is corrupt.
- 27015 — Unexpected ridlist length. Error Tolerant Index is corrupt.
- 27016 — Cannot connect to Error Tolerant Index. Bad or missing SqlCommand object.
- 27017 — Failed to drop index on reference table copy.
- 27018 — Could not retrieve metadata from Error Tolerant Index. The index is probably corrupt.
- 27019 — Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
- 27022 — An error specific to fuzzy lookup table maintenance has occurred.
- 27023 — A system error occurred during execution of fuzzy lookup table maintenance.
- 27024 — Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt.
- 27025 — Argument is not a valid hex string. Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt.
- 27026 — Negative count in Error Tolerant Index metadata. The index is probably corrupt.
- 27027 — Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt.
- 27028 — Invalid Error Tolerant Index metadata. The index is probably corrupt.
- 27029 — Invalid Error Tolerant Index metadata version.
- 27030 — Missing metadata. The Error Tolerant Index is probably corrupt.
- 27031 — Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt.
- 27032 — Error Tolerant Index Metadata string too long. Index is probably corrupt.
- 27033 — Error Tolerant Index Metadata length limit exceeded.
- 27034 — Unexpected end of Error Tolerant Index metadata. Index is probably corrupt.
- 27037 — No table name provided for Error Tolerant Index. The index is probably corrupt.
- 27038 — No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt.
- 27039 — No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt.
- 27040 — No Error Tolerant Index metadata string provided for initialization. Index is probably corrupt.
- 27041 — No Error Tolerant Index metadata provided for serialization. The index is probably corrupt.
- 27042 — Could not lookup object_id. No object name provided.
- 27043 — Could not lookup object_id. Null command object provided.
- 27044 — Open connection required. Cannot query Error Tolerant Index.
- 27045 — Cannot write to null output buffer. Could not update Error Tolerant Index. The index is probably corrupt.
- 27046 — Output buffer provided is too small. Could not update Error Tolerant Index. The index is probably corrupt.
- 27047 — The number of min-hash q-grams per token must be positive.
- 27048 — Could not create index on reference table copy.
- 27049 — Reference table (or internal copy) missing integer identity column. Error tolerant index is probably corrupt.
- 27050 — The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps in sequence.
- 27051 — Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted.
- 27052 — Table maintenance insertion failed.
- 27053 — A positive q-gram length is required for tokenization.
- 27054 — Maintenance trigger already installed on this reference table.
- 27055 — Missing extended property on maintenance trigger.
- 27056 — Maintenance trigger name out of sync with Error Tolerant Index metadata. Index is probably corrupt.
- 27058 — A SQL error occurred during execution of fuzzy lookup table maintenance.
- 27059 — Could not lookup object_id. The reference table or maintenance trigger could not be found.
- 27060 — The Error Tolerant Index table name provided is not a valid SQL identifier.
- 27061 — The Error Tolerant Index table name provided refers to a missing table. Check sys.tables.
- 27062 — An auxiliary Fuzzy Lookup table maintenance table is missing.
- 27063 — An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed.
- 27064 — The row deleted from the reference table could not be located in the reference table copy.
- 27065 — Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt.
- 27100 — The input parameter, '%ls', cannot be null. Provide a valid value for this parameter.
- 27101 — The value specified for the input parameter, '%ls', is not valid. Provide a valid value for this parameter.
- 27102 — The input parameter, '%ls', cannot be empty. Provide a valid value for this parameter.
- 27103 — Cannot find the execution instance '%I64d' because it does not exist or you do not have sufficient permissions.
- 27104 — Cannot find the folder '%ls' because it does not exist or you do not have sufficient permissions.
- 27105 — Cannot find the operation '%I64d' because it does not exist or you do not have sufficient permissions.
- 27106 — Cannot find the parameter '%ls' because it does not exist.
- 27107 — The specified %ls already exists.
- 27108 — The path for '%ls' cannot be found. The operation will now exit.
- 27109 — Cannot find the project '%ls' because it does not exist or you do not have sufficient permissions.
- 27110 — Default permissions for the project cannot be granted to the user. Make sure that the user can be assigned these permissions.
- 27111 — Cannot find the reference '%I64d' because it is not part of the project or you do not have sufficient permissions.
- 27112 — Unable to update the row in the table, '%ls'. Make sure that this row exists.
- 27113 — Unable to delete one or more rows in the table, '%ls'. Make sure that these rows exist.
- 27114 — Cannot find the reference '%I64d' because it does not exist or you do not have sufficient permissions.
- 27115 — Cannot find the target folder '%ls' because it does not exist or you do not have sufficient permissions.
- 27116 — Conversion failed while performing encryption.
- 27117 — Failed to decrypt the project. The symmetric key that was used to encrypt it may have been deleted. Delete the project and deploy it again.
- 27118 — Failed to deploy the project. Try again later.
- 27119 — Failed to encrypt the project named '%ls'. The symmetric key may have been deleted. Delete the project and deploy it again.
- 27120 — Failed to grant permission '%ls'.
- 27121 — The project is currently running or has completed. An instance of execution can only be started once.
- 27122 — Unable to perform impact analysis and lineage. The package data or configuration data might not be valid. To validate package data, open the package i…
- 27123 — The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Integrated Authentica…
- 27124 — Integration Services server cannot stop the operation. The specified operation with ID '%I64d' is not valid or is not running.
- 27125 — Integration Services server cannot stop the operation. The specified operation is not in a consistent state and cannot be stopped.
- 27126 — Integration Services server cannot stop the operation. The specified operation is already in Stopping state.
- 27127 — The Integration Services catalog '%ls' does not exists.
- 27128 — The name '%ls' is not valid. It consists of characters that are not allowed.
- 27129 — The folder '%ls' already exists or you have not been granted the appropriate permissions to change it.
- 27130 — Integration Services server was unable to impersonate the caller. Operating system returned error code: %ls.
- 27131 — Integration Services server was unable to start the process, '%ls'. Operating system returned error code: %ls.
- 27132 — Integration Services server was unable to create process component, '%ls'. Operating system returned error code: %ls.
- 27133 — Integration Services server was unable to wait for process, '%ls', to finish. Operating system returned error code: %ls.
- 27135 — The database, '%ls', already exists. Rename or remove the existing database, and then run SQL Server Setup again.
- 27136 — The required components for the 32-bit edition of Integration Services cannot be found. Run SQL Server Setup to add the required components.
- 27137 — The registry key for the system setting '%ls' could not be found. The operation will now exit.
- 27138 — The input parameter cannot be null. Provide a valid value for the parameter.
- 27139 — Integration Services server cannot be configured because there are active operations. Wait until there are no active operations, and then try to confi…
- 27140 — The operation cannot be started because the user is not a member of the database role, '%ls', or the server role, '%ls'. Log in as a member of one of …
- 27141 — Integration Services server cannot be configured because there are execution logs. Please cleanup all execution logs, and then try to configure the se…
- 27142 — '%ls' is not a valid environment name. It consists of characters that are not allowed.
- 27143 — Cannot access the operation with ID, '%I64d'. Verify that the user has appropriate permissions.
- 27145 — '%ls' is not a valid project name. It consists of characters that are not allowed.
- 27146 — Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it.
- 27147 — The data type of the input value is not compatible with the data type of the '%ls'.
- 27148 — The data type of the parameter does not match the data type of the environment variable.
- 27149 — Integration Services server cannot perform the requested operation on the specified package now, because the package is in pending state. Wait until t…
- 27150 — The version of the project has changed since the instance of the execution has been created. Create a new execution instance and try again.
- 27151 — The restore operation for project '%ls' from version '%I64d' has started.
- 27152 — The restore operation for project '%ls' to version '%I64d' has completed.
- 27153 — Default permissions for the operation cannot be granted to the user. Make sure that the user can be assigned these permissions.
- 27154 — The @sensitive parameter is missing. This parameter is used to indicate if the parameter contains a sensitive value.
- 27155 — Project restore has failed. You cannot restore a project having an object_version_lsn that is the same as the current project.
- 27156 — The Integration Services server property, '%ls', cannot be found. Check the name of the property and try again.
- 27157 — The environment '%ls' already exists or you have not been granted the appropriate permissions to create it.
- 27158 — Error number, %d, occurred in the procedure, '%ls', at line number, %d. The error message was: '%ls' The error level was %d and the state was %d.
- 27159 — Data type of the input value is not supported.
- 27160 — The Stored Procedure, '%ls', failed to run because the Integration Services database (SSISDB) is not in single-user mode. In SQL Server Management Stu…
- 27161 — Warning: the requested permission has already been granted to the user. The duplicate request will be ignored.
- 27162 — The property, '%ls', cannot be changed because the Integration Services database is not in single-user mode. In Management Studio, in the Database Pro…
- 27163 — The value for the Integration Services server property, '%ls', is not valid. In Management Studio, in the Integration Services Properties dialog box, …
- 27165 — Warning: During startup, the Integration Services server marked operation %I64d (type %d, status %d) as terminated. Please check the operating system …
- 27166 — The installed version of SQL Server does not support the installation of the Integration Services server. Update SQL Server, and then try installing t…
- 27167 — Failed to change the encryption algorithm to '%ls'. An error occurred while encrypting the environment variables with the '%ls' algorithm.
- 27168 — Failed to change the encryption algorithm to '%ls'. An error occurred while encrypting the parameter values using the '%ls' algorithm.
- 27169 — Failed to create a log entry for the requested operation.
- 27170 — Failed to retrieve the project named '%ls'.
- 27171 — The value specified is not valid. A value of data type '%ls' is required.
- 27172 — The certificate and symmetric key used to encrypt project '%ls' does not exist or you do not have sufficient permissions.
- 27173 — The environment variable '%ls' already exists.
- 27175 — The execution has already completed.
- 27176 — The parameter '%ls' does not exist or you do not have sufficient permissions.
- 27177 — Environment names must be unique. There is already an environment named '%ls'.
- 27178 — Unable to execute the project named '%ls'. You do not have sufficient permissions.
- 27179 — The object version does not match the project id or you do not have sufficient permissions.
- 27180 — %ls is not a valid environment variable name. It consists of characters that are not allowed.
- 27181 — The project '%ls' already exists or you have not been granted the appropriate permissions to access it.
- 27182 — The environment '%s' does not exist or you have not been granted the appropriate permissions to access it.
- 27183 — The environment variable '%ls' does not exist or you have not been granted the appropriate permissions to access it.
- 27184 — In order to execute this package, you need to specify values for the required parameters.
- 27185 — The validation record for ID '%I64d' does not exist or you have not been granted the appropriate permissions to access it.
- 27186 — One or more environment variables could not be found in the referenced environment.
- 27187 — The project does not exist or you have not been granted the appropriate permissions to access it.
- 27188 — Only members of the ssis_admin or sysadmin server roles can create, delete, or rename a catalog folder.
- 27189 — Catalog folder name cannot be NULL or an empty string.
- 27190 — The folder '%ls' already exists or you have not been granted the appropriate permissions to create it.
- 27191 — The '%d' permission is not applicable to objects of type '%d'. Grant, deny, or revoke of this permission is not allowed.
- 27192 — The caller has not been granted the MANAGEPERMISSION permission for the specified object.
- 27193 — SQL Server %ls is required to install Integration Services. It cannot be installed on this version of SQL Server.
- 27194 — Cannot find the project because it does not exist or you do not have sufficient permissions.
- 27195 — The operation failed because the execution timed out.
- 27196 — Failed to delete the folder '%ls' because it is not empty. Only empty folders can be deleted.
- 27197 — The specified %ls %ld does not exist.
- 27198 — Failed to locate records for the specified operation (ID %I64d).
- 27199 — %ls is not a valid folder name. It consists of characters that are not allowed.
- 27200 — The project is missing the specified environment reference.
- 27201 — Values are missing for required parameters in this package. Specify values in order to start the validation.
- 27202 — This project is missing one or more environment references. In order to use environment variables, specify the corresponding environment reference ide…
- 27203 — Failed to deploy project. For more information, query the operation_messages view for the operation identifier '%I64d'.
- 27204 — Failed to create environment reference. This project already has an reference to the specified environment.
- 27205 — Some of the property values for this parameter are missing.
- 27206 — Failed to deploy project to the folder '%ls'. You do not have sufficient permissions to deploy this project.
- 27207 — Failed to locate one or more variables in the environment '%ls'.
- 27208 — The environment reference '%I64d' is not associated with the project.
- 27209 — Failed to create environment to the folder '%ls'. You do not have sufficient permissions to create this environment.
- 27210 — Conversion failed when converting the %ls to data type %ls.
- 27212 — Data tap can only be added or removed when the execution status is created.
- 27213 — The package path and data flow path ID strings already exist for the execution ID %I64d. Provide package path and data flow path ID strings that are n…
- 27214 — The data flow task GUID '%ls' and the data flow path ID string already exist for the execution ID %I64d. Provide a data flow task GUID and a data flow…
- 27215 — The data tap '%I64d' does not exist, or you do not have sufficient permissions to remove it. Provide a valid data tap ID.
- 27216 — The number of rows must be a non-negative value. Specify a valid value.
- 27217 — The logging level '%d' is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), 3 (Verbose), 4 (RuntimeLineage…
- 27218 — The Integration Services Server cannot find the running process for execution ID %I64d. Provide a valid execution ID.
- 27219 — Caller does not have permissions to execute the stored procedure.
- 27220 — SSISDB database does not exist. Create the SSISDB database.
- 27221 — Unable to map an environment variable with the sensitive property set to True, to a parameter with the sensitive property set to False. Ensure that th…
- 27222 — The required components for the 64-bit edition of Integration Services cannot be found. Run SQL Server Setup to install the required components.
- 27223 — Cannot move the project to folder '%ls' due to insufficient permissions.
- 27224 — The parameter value cannot be changed after the execution has been started.
- 27225 — The property cannot be overridden after the execution has been started.
- 27226 — The database principal has granted or denied permissions to catalog objects in the database and cannot be dropped.
- 27227 — The server '%ls' already exists.
- 27228 — The server '%ls' does not exists.
- 27229 — Cannot find the SQL login '%ls'.
- 27230 — Failed to deploy the packages. Try again later.
- 27231 — Failed to deploy packages. For more information, query the operation_messages view for the operation identifier '%I64d'.
- 27232 — Failed to create customized logging level '%ls'. You do not have sufficient permissions to create customized logging level.
- 27233 — Customized logging level name cannot be NULL or an empty string.
- 27234 — '%ls' is not a valid customized logging level name. It consists of characters that are not allowed.
- 27235 — The customized logging level '%ls' already exists.
- 27236 — Failed to delete customized logging level '%ls'. You do not have sufficient permissions to delete customized logging level.
- 27237 — The customized logging level '%ls' does not exist.
- 27238 — Failed to rename customized logging level '%ls' with '%ls'. You do not have sufficient permissions to rename customized logging level.
- 27239 — Failed to update customized logging level '%ls'. You do not have sufficient permissions to update customized logging level.
- 27240 — The value can not be less than zero.
- 27241 — Failed to update logging level '%d'. Provide the value for SERVER_CUSTOMIZED_LOGGING_LEVEL property, as it can not be null or empty for logging level …
- 27242 — Cannot find the cluster execution job instance '%ls' because it does not exist or you do not have sufficient permissions.
- 27243 — Cannot find the cluster worker agent '%ls' because it does not exist or you do not have sufficient permissions.
- 27246 — Cannot find the cluster execution task instance '%ls' because it does not exist or you do not have sufficient permissions.
- 27251 — Cannot add a worker agent to execute the cluster job instance '%ls' because the job is specified for all worker agents.
- 27252 — The Integration Services cluster worker agent '%ls' is disabled.
- 27255 — The job id of the execution is null. Create a job for the execution first and try again.
- 27256 — The event message does not exist.
- 27257 — There is no active worker agent.
- 27259 — Failed to enable worker agent because current SQL Server edition only support limited number of worker agents.
- 27260 — Only members of sysadmin server roles can perform this action.
- 27261 — There is no Scale Out Master installed.
- 27301 — Operation is not supported unless all bricks are online. Bring the offline bricks back online, and retry the operation.
- 27302 — An internal communication error occurred. Retry the operation.
- 27303 — An unexpected error with HRESULT 0x%x occurred while processing backup files. Refer to the SQL Server error log for information about any related erro…
- 27304 — The number of matching backup files (%d) is less than the required number (%d). Copy all the right backup files to the proper backup location, and ret…
- 27305 — The number of backup files (%d) is greater than the available number of bricks (%d). You must restore backup files on to at least as many bricks as pr…
- 27306 — No matching backup files were found by any of the bricks. Copy the backup files to the correct backup location, and retry the operation. If the backup…
- 27307 — Brick ID %d has no backup files available. Copy the backup file for the segment to this brick, and retry the operation.
- 27308 — SegmentID %d from the archive does not match the segmentID %d from the specified filename on brick %d.
- 27309 — Restore recovery failed because a problem was detected with data in a temporary file that is needed for recovery. This error can be caused because of …
- 27310 — Restore failed because all the backup files did not come from the same backup operation. Retry the restore operation using the backup files from a sin…
- 27311 — Restore failed because of an internal communications error. Retry the restore operation after addressing any network issues.
- 27312 — Device name '%ls' is not valid in a Matrix Backup/Restore command. The device name contains illegal characters or file name is empty. Retry the comman…
- 27313 — Restore command is not valid as both Standalone and Matrix archives were found while disambiguating the device name(s). Retry the command after making…
- 27314 — Restore failed because the brick count of %ld is different from the BACKUP GROUP COUNT %ld from the backup file. Make sure that all Matrix backup file…
- 27315 — An unexpected error occurred while executing a Backup/Restore command. Refer to the SQL Server error log for information about any related errors that…
- 27316 — Device name '%.*ls' is not a valid MOVE target of a Matrix Restore command. Retry the command using a valid relative path name.
- 27317 — The backup files of the RESTORE command do not match with the segments of the existing database. Copy the backup files to the correct backup location,…
- 27318 — The backup files of the FULL RESTORE command do not match with the segments of the existing database. Copy the correct backup files to the backup loca…
- 27319 — The backup type of all the archive segments is not the same. Copy the correct backup files to the backup location, and retry the restore operation.
- 27400 — An invalid synctoken was used for a reference fetch during attribute synchronization with an external governance engine.
- 27401 — A database was found with the wrong state during an external governance operation.
- 27402 — A database was not found during an external governance operation.
- 27403 — A schema was not found during an external governance operation.
- 27404 — A relation was not found during an external governance operation.
- 27405 — A column was not found during an external governance operation.
- 27406 — The database registration was not found during an external governance operation.
- 27407 — The database registration attributes could not be obtained during an external governance operation.
- 27408 — An external governance operation was attempted on a database that differs from the current one.
- 27409 — The sensitivity classification DDL commands are disabled when a database is under external governance.
- 27410 — The references to the attribute synchronization data blobs must be in JSON format.
- 27411 — The references to the attribute synchronization data blobs must be in a JSON array.
- 27412 — A reference to the attribute synchronization data blobs must be a JSON object.
- 27413 — A reference to the attribute synchronization data blobs does not have the proper JSON format.
- 27414 — Malformed resource path.
- 27415 — Invalid JSON for attribute synchronization data.
- 27416 — Cannot create attribute because it is missing information.
- 27417 — Invalid JSON format for classification attribute.
- 27418 — Unsupported attribute synchronization event.
- 27419 — Unsupported kind of synchronization attribute .
- 27420 — Cannot update synchronization attribute because version is older.
- 27421 — Cannot create HTTP client for attribute synchronization.
- 27422 — Invalid JSON format for reference fetch response.
- 27423 — Could not execute a reference fetch because the AAD token could not be created.
- 27424 — An object was not found during an external governance operation.
- 27425 — No more attribute events for the specified token.
- 27426 — External governance synchronization task failed to acquire lock while trying to synchronize attributes.
- 27427 — External governance synchronization task failed to initialize attribute synchronization manager.
- 27428 — '%ls' is not a valid option for the @scope parameter. Enter 'access_policies', 'attributes' or 'full'.
- 27429 — Fatal error: Unable to synchronize attributes to database '%ls' for %d consecutive attempts.
- 27500 — An HTTP error occurred.
- 27501 — An unsupported connection type HTTP error occurred.
- 27502 — An open session HTTP error occurred.
- 27503 — A connect session HTTP error occurred.
- 27504 — An attempt connect HTTP error occurred.
- 27505 — An open request HTTP error occurred.
- 27506 — An add request header HTTP error occurred.
- 27507 — A send request HTTP error occurred.
- 27508 — A get response code HTTP error occurred.
- 27509 — A response code unauthrozied HTTP error occurred.
- 27510 — A response code throttled HTTP error occurred.
- 27511 — A response code client error HTTP error occurred.
- 27512 — A response code server error HTTP error occurred.
- 27513 — A not found HTTP error occurred.
- 27514 — A forbidden HTTP error occurred.
- 27515 — A query header HTTP error occurred.
- 27516 — A query header out of memory (copy header) HTTP error occurred.
- 27517 — A query header out of memory (realloc buffer) HTTP error occurred.
- 27518 — A query header not found HTTP error occurred.
- 27519 — A query header update buffer length HTTP error occurred.
- 27520 — A read data HTTP error occurred.
- 27521 — A get response out of memory (create temp buffer) HTTP error occurred.
- 27522 — A get response out of memory (get result string) HTTP error occurred.
- 27523 — A get response out of memory (append response) HTTP error occurred.
- 27524 — A set client certificate context HTTP error occurred.
- 27525 — A get security flags HTTP error occurred.
- 27526 — A set security flags HTTP error occurred.
- 27527 — A receive response HTTP error occurred.
- 27528 — A 'NotModified' response HTTP error occurred.
- 27600 — The response was in a bad format while obtaining label information from Microsoft Purview Information Protection.
- 27601 — Internal error occurred while obtaining Microsoft Purview Information Protection label information from API endpoint. Substate: '%ls', status: 0x%08x.
- 27602 — An internal error occurred while assigning an Microsoft Purview Information Protection Label. Try the assignment again.
- 27603 — The response was in a bad format while obtaining information from Microsoft Purview Information Protection API.
- 27604 — Your organization Microsoft Purview Information Protection label publishing policy requires a justification when the label assigned to the column is b…
- 27605 — The label with ID '%.*ls' is not a valid label in Microsoft Purview Information Protection. Provide a valid label ID. For more information, see https:…
- 27606 — Microsoft Purview Information Protection label can only be assigned or changed by Microsoft Entra user. Use a valid Microsoft Entra user to execute th…
- 27607 — Microsoft Purview Information Protection labels cannot be assigned when the database has existing labels assigned via the SQL Data Discovery and Class…
- 27608 — Labels via the SQL Data Discovery and Classification feature cannot be assigned when the database has existing Microsoft Purview Information Protectio…
- 27609 — Internal error occurred while running billing background task. Major error code: %d, Minor error code: %d, State: %d.
- 27610 — Unable to access Microsoft Purview Information Protection on your behalf because your session has expired. Reconnect to SQL database and try again.
- 27611 — No valid Microsoft Purview Information Protection labels exist for the user in the tenant.
- 27801 — Successfully initialize HPC environment from provider '%ld', device type '%ld' DLL version %ld, and find %ld device(s), %ld of them are used.
- 27802 — Failed to initialize HPC environment.
- 27803 — Message reported from (%.*s) device on device Id (%I64d), code : %d, message : %.*s .
- 27804 — Query failed on HPC device Id (%I64d), with error code %d .
- 27805 — Failed to generate substrait for query.
- 28000 — The decrypted session key has an unexpected size.
- 28001 — A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID '%.*ls', Initiator: %d, and Messag…
- 28002 — Cannot start service broker manager. Operating system error: %ls.
- 28003 — An internal service broker error occurred. Operating system error: %ls.
- 28004 — This message could not be delivered because the '%S_MSG' action cannot be performed in the '%.*ls' state.
- 28005 — An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls
- 28006 — User does not have permission to %S_MSG the conversation '%.*ls' in state '%.*ls'. Only members of the sysadmin fixed server role and the db_owner fix…
- 28007 — A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the mess…
- 28008 — The conversation handle '{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}' is invalid.
- 28009 — The crypto API has detected bad data while trying to perform a decryption operation.
- 28010 — This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged m…
- 28011 — This message could not be delivered because its %S_MSG has expired or is invalid.
- 28012 — The Service Broker in the target database is unavailable: '%S_MSG'.
- 28013 — The service broker is administratively disabled.