错误码目录 / Microsoft SQL Server
Microsoft SQL Server 错误码目录 · 第 16 / 18 页
本页收录 Microsoft SQL Server 的 17,993 条错误码知识条目,每条均可打开独立详情页,包含错误说明、编号信息、官方文档与公开资料。
- 39124 — '%.*ls' platform information doesn't exist for the language '%.*ls'.
- 39125 — ALTER EXTERNAL LANGUAGE statement failed because of duplicate file specification. Only one file specification per platform is allowed.
- 39126 — ALTER EXTERNAL LANGUAGE REMOVE PLATFORM statement failed because an external language requires at least one file specification to be defined.
- 39127 — External script execution for '%.*s' script ran out of resources. External script request id is: %s.
- 39128 — External language runtime for '%s' could not be provisioned. Error code 0x%08x.
- 39129 — Cannot drop external language '%.*ls' because it is being referenced by external library '%.*ls'.
- 39130 — %.*ls statement failed. Language '%s' already exists.
- 39131 — %.*ls statement failed. System language '%s' can't be altered or removed.
- 39132 — The parameter '@r_rowsPerRead' is invalid. Parameter '@r_rowsPerRead' must be a positive integer.
- 39133 — CREATE/ALTER EXTERNAL LANGUAGE statement failed. The environment variables string is invalid.
- 39134 — The procedure '%s' cannot be executed because it is not supported in Azure SQL Edge.
- 39135 — Service environment '%s' is not ready.
- 39136 — Error sending a message to the service.
- 39137 — Error initialization external services framework.
- 39138 — Request to drop streaming job '%s' failed because the job is currently running. Stop the job before dropping.
- 39139 — Request to stop streaming job '%s' failed because the job is not currently running.
- 39140 — Request to create streaming job '%s' failed. The Streaming job query cannot be null or empty.
- 39141 — External data source '%s' with location prefix '%s' is not supported as input for streaming.
- 39142 — External data source '%s' with location prefix '%s' is not supported as output for streaming.
- 39143 — External data source '%s' with location prefix '%s' is not supported for streaming.
- 39144 — External data source '%s' has an invalid location for streaming.
- 39145 — External stream '%s' has an invalid location.
- 39146 — External stream '%s' has invalid properties.
- 39147 — Kafka datasource '%s' should specify a value for PARTITIONS in the properties field.
- 39148 — External file format '%s' type is not supported for streaming.
- 39149 — External file format '%s' encoding is not supported for streaming.
- 39150 — Error while processing streaming job: '%s'.
- 39151 — Transient error communicating with the streaming runtime. Please retry the operation.
- 39152 — Transient error communicating with the streaming runtime due to unfinished stop streaming job operation. Please retry the operation.
- 39153 — Error while launching mssql-flight-server with HRESULT 0x%x
- 39154 — Error while stopping mssql-flight-server with HRESULT 0x%x
- 39155 — The maximum acceptable number of columns is %d while %ld number of columns are in the schema.
- 39156 — External libraries are not permitted for language '%.*ls'.
- 39157 — Cannot modify or drop system-defined external language '%.*ls'.
- 39158 — First-party extensibility features are not enabled on this instance of SQL Server. Contact your system administrator.
- 39159 — %ls requires at least %d parameters.
- 39160 — Parameter '%ls' must not be NULL for stored procedure %ls.
- 39161 — Stored procedure %ls is not enabled on this instance of SQL Server.
- 39162 — Parameter '%ls' must not exceed %u characters.
- 39163 — Parameter '%ls' must be an inline (non-LOB) Unicode string.
- 39164 — '%.*ls' is not a recognized first-party language for stored procedure %ls.
- 39165 — The value supplied for parameter '%ls' of stored procedure %ls is not valid JSON.
- 39166 — The JSON supplied to stored procedure %ls is not valid: %ls.
- 39167 — '%ls' is not a supported data type in the JSON supplied to stored procedure %ls.
- 39168 — The JSON supplied to stored procedure %ls specifies too many parameters; the maximum is %d but %ld were supplied.
- 39169 — The JSON supplied to stored procedure %ls specifies too many columns; the maximum is %d but %ld were supplied.
- 39170 — Parameter '%ls' of stored procedure %ls must be declared with the OUTPUT keyword.
- 39171 — Parameter '%ls' must be a Unicode (nvarchar or nvarchar(max)) string.
- 39172 — An extension request for '%.*s' failed with HRESULT 0x%x. Request ID is %ls.
- 39173 — Stored procedure %ls returned a result set with an invalid schema.
- 40000 — Replicated tables support only local (non-DTC) two-phase commit involving the master database.
- 40001 — Secondary kill was initiated during commit.
- 40002 — Replicated row is not found.
- 40003 — Unexpected operation in replicated message.
- 40004 — Column count does not match.
- 40005 — Duplicated transaction id.
- 40006 — Unknown transaction id.
- 40007 — Invalid nesting level.
- 40008 — Replication target database is not found.
- 40009 — Transaction state locally does not match the expected state.
- 40010 — Replicated transactions across databases are not allowed.
- 40011 — Replicated target table %ld is not found.
- 40012 — Replicated target index %ld on table %ld is not found.
- 40013 — Replicated target schema %.*ls is not found.
- 40014 — Multiple databases can not be used in the same transaction.
- 40015 — This functionality is not supported on replicated tables.
- 40016 — The partitioning key column '%.*ls' must be one of the keys of '%.*ls.%.*ls.%.*ls' index.
- 40017 — Partition key can not be changed.
- 40018 — Partition key value is outside of the valid partition key range.
- 40019 — The partition key column '%.*ls' of table '%.*ls.%.*ls' is nullable or does not match the partition key type defined in the table group.
- 40020 — The database is in transition and transactions are being terminated.
- 40021 — The low and high keys specified for the partition are invalid. Low must be less than high.
- 40022 — A partition with overlapping key ranges already exists.
- 40023 — The name %s is too long.
- 40024 — The last committed CSN (%d, %I64d) was not found in the log. The last seen CSN was (%d, %I64d).
- 40025 — The transaction was aborted during commit due to a database state transition.
- 40028 — The tablegroup name '%.*ls.%.*ls' is not valid.
- 40029 — Replicated tables can have at most %d columns.
- 40030 — Can not perform replica operation because the replica does not exist in local partition map.
- 40031 — The partition key column for table '%.*ls.%.*ls' is undefined.
- 40032 — Unsupported use of LOB in online index build.
- 40033 — Attempted CSN epoch switch is not allowed. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40034 — CSN being added must be equal last CSN+1. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40035 — CSN being added must be equal or greater than the last CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40036 — Can not perform replica operation because this node is not the secondary for this partition.
- 40037 — The epoch being started must not have been used. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40038 — Can not get ack to rollback replication message.
- 40039 — Can not get ack to commit replication message.
- 40040 — Failed to initiate VDI Client for physical seeding.
- 40041 — Corrupted column status.
- 40042 — Corrupted column length.
- 40043 — Corrupted variable data. Actual remaining bytes is %d, expected %d bytes.
- 40044 — Corrupted fixed size data. Actual remaining bytes %d, expected %d bytes.
- 40045 — Message version mismatch. Actual version is %d and the expected is %d.
- 40046 — The minimum required message version %d for message type %d is unsupported.
- 40047 — Invalid use of parent transaction.
- 40048 — Corrupted fragmented row flow sequence.
- 40049 — Corrupted fragmented row.
- 40050 — Corrupted LOB row.
- 40051 — Use of UPDATETEXT on replicated tables is not supported.
- 40052 — Parallel queries are not supported on replicated tables.
- 40053 — Attempt to replicate a non-replicated system table %ld.
- 40054 — Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again.
- 40056 — Master, tempdb, model and mssqlsystemresource databases can not be replicated.
- 40057 — Table is not enabled for replication.
- 40058 — Unsupported replicated table usage option. Refer to the state to identify the cause.
- 40060 — Attempt to replicate out of partition already locked for internal use.
- 40061 — Unknown rowset id.
- 40062 — Incorrect replica role transition.
- 40063 — Replica is not found.
- 40064 — Attempt to add a CSN to an invalid CSN vector. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40065 — CSN vector can be reinitialized only with initial or invalid CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40066 — Transport destination is not found.
- 40067 — Corrupted row sequence.
- 40068 — Idempotent mode has been used on an unknown transaction.
- 40069 — Could not obtain rowset interface.
- 40070 — CSN mismatch detected. The local CSN is (%d,%I64d), the remote CSN is (%d,%I64d).
- 40071 — This partition does not have enough valid secondaries to start a DML transaction. The needed count is %ld, the current counts are %ld (main quorum) an…
- 40072 — Corrupted rowset metadata sequence.
- 40073 — Partitioned tables are not supported.
- 40074 — Partition key is not found is the target rowset or is nullable or not part of index keys.
- 40075 — Column schema mismatch for rowset %ls.%ls.%ls column %ld.
- 40076 — Too few columns from remote rowset %ls.%ls.%ls.
- 40077 — Remote rowset %ls.%ls.%ls column %ld is not found locally.
- 40078 — The persisted queue logging has failed.
- 40079 — A non-null variable length value is received for a column that is shorter locally.
- 40080 — Corrupted (too long) packed row.
- 40081 — Cardinality of index should not be less then zero.
- 40082 — Induced exception for testing purposes.
- 40083 — Corrupted CSN vector.
- 40084 — Multiple modifications to CSN vector in the same transaction are not supported.
- 40085 — The primary partition has lost the quorum. New transactions can not start.
- 40086 — Primary hit an error with this secondary.
- 40087 — Replica with the specified version is not found.
- 40088 — CSN being set is outside the CSN epoch range. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40089 — The index configuration for table %ld index %ld does not match the source.
- 40090 — The primary partition is in transition and the transaction can not commit.
- 40091 — Truncation CSN is mismatched. The truncation CSN is (%d,%I64d), the current CSN is (%d,%I64d).
- 40092 — This index %ld state for table %ld does not match the source.
- 40093 — Replication background task hit a lock timeout. User transactions will be killed and the operation will be retried.
- 40094 — Incompatible key metadata change. The scan can not be resumed.
- 40095 — Replication transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. The operati…
- 40096 — Critical replication task could not start. State is %d.
- 40097 — The begin transaction message was not found when scanning persisted replication queue.
- 40098 — Mismatched partition id found in the transaction log.
- 40099 — Invalid nested transaction count found in the transaction log.
- 40101 — The partition does not have persisted queues enabled.
- 40102 — The partition can not have persisted queues modified in this state.
- 40103 — The partition can not be changed inside a persisted object.
- 40104 — Only sysadmin can execute this stored procedure '%.*ls'.
- 40105 — The local partition map for database %.*ls is starting up in reduced functionality mode because of log full. Pending partition deletes will not be pro…
- 40106 — The schema scope set in the session is not the current schema scope for the current partition. Please rerun your query.
- 40108 — The filtered replica is not a subset of the primary replica. This is only possible for table groups without a partition key.
- 40109 — Number of parameters specified for procedure or function %.*ls is incorrect.
- 40110 — Cannot scope database %s for sp_cloud_scope_database spec proc because it is already set up as a partition database.
- 40111 — Unable to delete partition DB id %d.
- 40126 — The partition database was not found during pending schema scope cleanup, deleting partition metadata only (%d, %s).
- 40127 — %S_MSG database '%.*ls' link up with the %S_MSG database %d encountered the error: %S_MSG.
- 40128 — Cannot pair database '%.*ls' with fabric because it is not a partition host.
- 40129 — %S_MSG database link up with the %S_MSG database '%.*ls' encountered the error: %ls.
- 40130 — Replication quorum parameter is %d. It should be >= 1 and <= 32.
- 40131 — Partition key type '%.*ls' is not supported. Only BIGINT, UNIQUEIDENTIFIER, and VARBINARY(n) (0<n<=512) datatypes are supported currently.
- 40132 — Before dropping a table group, you have to delete all the partitions.
- 40133 — This operation is not supported in this version of SQL Server.
- 40134 — get_new_rowversion() can only be used in an active transaction.
- 40135 — This system metadata view is not supported.
- 40136 — Could not disable versioning because the database is not in single user mode.
- 40137 — Could not refresh options for all scoped databases.
- 40138 — Query references entities from multiple partitions.
- 40139 — The data node does not host a replica of the requested partition.
- 40140 — Set partition failed since a different partition already was set in the current transaction. Cross partition operations within a node are not reliable…
- 40141 — Partition has to be set using sp_set_partition before executing this query.
- 40142 — Accessing a different partition in the same transaction is not allowed.
- 40143 — The replica that the data node hosts for the requested partition is not primary.
- 40144 — Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
- 40145 — Database is not found.
- 40146 — Table group object is not found.
- 40147 — Stored procedure '%.*ls' is only for CloudDB.
- 40148 — The existing persisted queue snapshot CSN (%d, %I64d) at %S_LSN is greater than the requested snapshot CSN (%d, %I64d) at %S_LSN.
- 40149 — The database does not host any partitions.
- 40150 — Downgrading the severity of error %d, severity %d, state %d because it would cause the server to be shutdown on a non-critical error.
- 40151 — Partition is in transactionally inconsistent state.
- 40152 — Partition delete expects no context transaction.
- 40153 — The current database has been shutdown. The current database has been switched to master.
- 40154 — Cannot use sp_cloud_add_partition or sp_cloud_delete_partition within a transaction when Partition DB are enabled.
- 40155 — Invalid arguments provided to sp_cloud_add_partition spec proc (%s).
- 40156 — Drop is not allowed on the %S_MSG database '%.*ls' as it contains partitions. Drop the partition before the operation.
- 40157 — Too many secondaries. At most 32 are currently supported.
- 40158 — Could not change database collation for database id %d.
- 40159 — Database scoping cannot be run inside a transaction.
- 40160 — Heartbeat message version mismatch. Actual version is %d and the expected is %d.
- 40161 — Invalid partition type. Only 1 or 2 is supported.
- 40162 — The replica that the data node hosts for the requested partition is not transactionally consistent.
- 40163 — Become nothing expects no context transaction.
- 40164 — Idempotent flush expects no context transaction.
- 40165 — Prepare for full commit expects no context transaction.
- 40166 — A CloudDB reconfiguration is going on and all new user transactions are aborted.
- 40167 — A paired CloudDB fabric node failed and database %d must be shutdown.
- 40168 — SILO_TO_PDB: Partition copy is disabled in M1.
- 40169 — Waiting for database copy sync with %s.%s has failed. Please make sure the database is in the CATCH_UP state and try again later.
- 40170 — Catchup of secondary at %s:%s:%s:%d has failed.
- 40171 — Table group name (single part name) should not be longer than nvarchar(64).
- 40172 — The partition is not in a state that allows deletion.
- 40173 — This requested operation can not performed as this partition is in delete process.
- 40174 — The partition is in transition and transactions are being terminated.
- 40175 — Add a secondary with wait can not be used in a transaction.
- 40176 — Rename a partition can not be used in a transaction.
- 40177 — The new table group does not match the existing table group for the renaming partition.
- 40178 — A partition with same name already exists.
- 40179 — Fabric-database ('%.*ls') cannot be paired, the server is not ready to pair.
- 40180 — Fabric-database ('%.*ls') cannot be paired, the database is already paired.
- 40181 — Fabric-database ('%.*ls') cannot be paired, the supplied mutex ('%.*ls') could not be opened. Error code: %d
- 40182 — The schema scope %ld being created is not empty.
- 40183 — Could not create database side pairing mutex for database ('%.*ls'). Error code: %d
- 40184 — Login failed. A system operation is in progress, and the database is not accepting user connections.
- 40185 — Secondary failure report expects no context transaction.
- 40186 — The data node does not host a replica of the requested partition with the requested version.
- 40187 — The metadata record for the partition does not exist.
- 40188 — Failed to update database "%.*ls" because it is switched to read-only to enforce disaster recovery RPO.
- 40189 — The resource quota for the current database has been exceeded and this request has been aborted. Please rerun your request in the next quota window. %…
- 40190 — A context transaction is required.
- 40191 — Cannot create partition DB (%s).
- 40192 — Catchup of secondary at %s:%s:%s:%d has been cancelled.
- 40193 — The maximum allowed number of database is already paired.
- 40194 — Table %s has a partition key already. Explicitly specifying a new partition key is not allowed. Please use "Alter table".
- 40195 — %ls FOR SID command is not supported in this version of SQL Server.
- 40196 — A varbinary can not be longer than max length specified.
- 40197 — The service has encountered an error processing your request. Please try again. Error code %d.
- 40198 — Only a primary replica can be configured as a forwarder.
- 40199 — There should be no context transaction when entering the forwarder pending state.
- 40201 — Destination server name is too long.
- 40202 — Corrupted composite message.
- 40203 — Could not register AsyncTransport endpoint.
- 40204 — Dispatch sequence number maintenance failure
- 40205 — Maximum transport queue size reached.
- 40206 — Heartbeat lease time is less than the heartbeat worker interval.
- 40207 — Async transport test failed.
- 40208 — Corrupted received message format.
- 40209 — Duplicate destination id.
- 40210 — Cluster name has not been set.
- 40301 — Invalid lock mode or resource received in lock request.
- 40302 — Invalid identity value.
- 40303 — Enter idempotent sequence.
- 40304 — Target object %ld is not found.
- 40305 — The current object is not a relation.
- 40306 — Cannot create an index %ld on object %ld.
- 40307 — Cannot find index %ld on object %ld.
- 40308 — Metadata replication protocol error.
- 40309 — Partition %ld is not found
- 40310 — Converting a clustered index into a heap is not supported.
- 40311 — Switching out partitions not supported.
- 40312 — Inconsistent index build state.
- 40313 — Not all rowsets could be deleted.
- 40314 — Identity column not found on object %ld.
- 40401 — Requires AAD login for managing T-SQL streaming jobs.
- 40402 — Error creating the streaming job request with service auth issue.
- 40403 — Error creating the streaming job request.
- 40404 — Error sending the streaming job request.
- 40405 — T-SQL streaming is not supported.
- 40406 — The sysadmin role is required for operations on T-SQL streaming jobs.
- 40407 — The database scoped credential '%.*ls' has a secret with more than 200 characters. Long secret value is not supported in Synapse T-SQL Streaming.
- 40408 — '%.*ls' is not a supported Azure region for Synapse T-SQL streaming.
- 40409 — Request to update streaming job '%s' failed. The query statement cannot be updated when the job is running.
- 40410 — Request to update streaming job '%s' failed. Query statement update and online scaling cannot be done at the same time or both not set.
- 40411 — Request to scale streaming job '%s' failed. The job cannot be scaled when not running.
- 40412 — Request to stop streaming job '%s' failed. The job is in Created state and not running.
- 40501 — The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d
- 40502 — Duplicate group id settings specified.
- 40503 — Database field %ls contains invalid value '%.*ls'. Expected data type %ls.
- 40504 — Switching Databases is not supported. Use a new connection to connect to a different Database.
- 40505 — Incorrect user credentials.
- 40506 — Specified SID is invalid for this version of SQL Server.
- 40507 — '%.*ls' cannot be invoked with parameters in this version of SQL Server.
- 40508 — USE statement is not supported to switch between databases. Use a new connection to connect to a different database.
- 40509 — Upgrade of SAWA v1 database fails. Check the metadata of the database before re-running the upgrade.
- 40510 — Statement '%.*ls' is not supported in this version of SQL Server.
- 40511 — Built-in function '%.*ls' is not supported in this version of SQL Server.
- 40512 — Deprecated feature '%ls' is not supported in this version of SQL Server.
- 40513 — Server variable '%.*ls' is not supported in this version of SQL Server.
- 40514 — '%ls' is not supported in this version of SQL Server.
- 40515 — Reference to database and/or server name in '%.*ls' is not supported in this version of SQL Server.
- 40516 — Global temp objects are not supported in this version of SQL Server.
- 40517 — Keyword or statement option '%.*ls' is not supported in this version of SQL Server.
- 40518 — DBCC command '%.*ls' is not supported in this version of SQL Server.
- 40519 — Invalid value '%.*ls' of login field in gateway magic syntax.
- 40520 — Securable class '%S_MSG' not supported in this version of SQL Server.
- 40521 — Securable class '%S_MSG' not supported in the server scope in this version of SQL Server.
- 40522 — Database principal '%.*ls' type is not supported in this version of SQL Server.
- 40523 — Implicit user '%.*ls' creation is not supported in this version of SQL Server. Explicitly create the user before using it.
- 40524 — Data type '%.*ls' is not supported in this version of SQL Server.
- 40525 — 'WITH %ls' is not supported in this version of SQL Server.
- 40526 — '%.*ls' rowset provider not supported in this version of SQL Server.
- 40527 — Linked servers are not supported in this version of SQL Server.
- 40528 — Users cannot be mapped to Windows logins in this version of SQL Server.
- 40529 — Built-in function '%.*ls' in impersonation context is not supported in this version of SQL Server.
- 40530 — The %.*ls statement must be the only statement in the batch.
- 40531 — Server name cannot be determined. It must appear as the first segment of the server's dns name (servername.%.*ls). Some libraries do not send the serv…
- 40532 — Cannot open server "%.*ls" requested by the login. The login failed.
- 40533 — Server '%.*ls' already exists.
- 40534 — A valid SID is already associated with the database owner.
- 40535 — Properties for schema scope '%.*ls' already exist.
- 40536 — '%ls' is not supported in this service tier of the database. See Books Online for more details on feature support in different service tiers of Window…
- 40537 — User '%.*ls' not found in the database.
- 40538 — A valid URL beginning with 'https://' is required as value for any filepath specified.
- 40539 — Windows Azure Storage credential '%.*ls' was not found.
- 40540 — Transaction was aborted as database is moved to read-only mode. This is a temporary situation and please retry the operation.
- 40541 — Procedure cannot be called from inside a partition.
- 40542 — Incorrect number of parameters specified for procedure.
- 40543 — Invalid %S_MSG name specified. Length should be between 1 and %d.
- 40544 — The database '%.*ls' has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
- 40545 — The service is experiencing a problem that is currently under investigation. Incident ID: %ls. Code: %d
- 40546 — Cannot create UCS task pool
- 40548 — Granting CONNECT permission to the guest user in database '%.*ls' is not permitted.
- 40549 — Session is terminated because you have a long running transaction. Try shortening your transaction.
- 40550 — The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction.
- 40551 — The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce temporary table space usage.
- 40552 — The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.
- 40553 — The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows.
- 40554 — Exiting because of XEvent %ls.
- 40555 — '%ls' is not supported for this database. See Books Online for more details on feature support in different service tiers of Windows Azure SQL Databas…
- 40558 — Error - cannot perform checkpoint on a partition database before loading partition information.
- 40559 — File based statement options are not supported in this version of SQL Server.
- 40560 — Specified invalid LSN: '%.*ls' for database '%.*ls' while publishing external actor LSN progress.
- 40561 — Database copy failed. Either the source or target database does not exist.
- 40562 — Database copy failed. The source database has been dropped.
- 40563 — Database copy failed. The target database has been dropped.
- 40564 — Database copy failed. Database copy failed due to an internal error. Please drop target database and try again.</value>
- 40565 — Database copy failed. No more than 1 concurrent database copy from the same source is allowed. Please drop target database and try again later.
- 40566 — Database copy failed due to an internal error. Please drop target database and try again.
- 40567 — Database copy failed due to an internal error. Please drop target database and try again.
- 40568 — Database copy failed. Either the source or the target database has become unavailable. Please drop target database and try again.
- 40569 — Database copy failed. Target database has become unavailable. Please drop target database and try again.
- 40570 — Database copy failed due to an internal error. Please drop target database and try again later.
- 40571 — Database copy failed due to an internal error. Please drop target database and try again later.
- 40572 — Cannot obtain primary partition lock for CloudDB auto partition upgrade.
- 40573 — Cannot upgrade CloudDB auto partitions in database '%.*ls' because the physical database is read only.
- 40574 — Permissions for system stored procedures, server scoped catalog views, and extended stored procedures cannot be changed in this version of SQL Server.
- 40575 — Data type '%.*ls' is not supported in a federated database.
- 40576 — Table DDL on non-temporary tables is not supported in a filtered connection.
- 40577 — The constraint '%ls' is not supported in a federated database.
- 40578 — Statement '%.*ls' is not supported in a filtered connection.
- 40579 — DML statements are not supported on non-federated tables in a filtered connection.
- 40580 — Statement '%.*ls' is not supported in a federated database.
- 40581 — Logically filtered secondaries are only supported if the secondary is a forwarder.
- 40582 — Federation member metadata for a database cannot be changed when there are logically filtered secondaries attached (split is running).
- 40583 — Federation member does not exist for the given member id and federation root
- 40584 — Value '%.*ls' for option '%.*ls' is not supported in this version of SQL Server.
- 40585 — Can not perform replica operation because this node is not the forwarder for this partition.
- 40586 — Replicas with deferred commit enabled cannot be a member of a quorum.
- 40587 — Deferred commit is only supported with forwarder replicas.
- 40588 — Cannot create partition worker pool
- 40589 — Replicas that are not enabled for deferred commit cannot specify RPO.
- 40590 — The Gpm is in rebuild and cannot be accessed as it is not yet consistent.
- 40591 — Extended event configuration could not be initialized. The error is %ls.
- 40592 — Extended event session '%ls' could not be created or altered. XE Error %d.%d state:%d.
- 40593 — Extended event session '%ls' returned error '%ls'.
- 40594 — Extended event session '%ls' has been started.
- 40595 — Extended event session '%ls' has been altered.
- 40596 — Extended event session '%ls' has been stopped.
- 40597 — A federation root database cannot be read only.
- 40598 — A federation member cannot be read only.
- 40599 — This type of KILL is not supported in Windows Azure SQL Database; Only 'KILL session ID [WITH STATUSONLY]' and 'KILL UOW' are supported.
- 40601 — Server Admin user already exists.
- 40602 — Could not create login. Please try again later.
- 40603 — Cannot execute procedure because current user is not Gateway.
- 40604 — Could not %.*ls because it would exceed the quota of the server.
- 40605 — There is no route from the source cluster '%ls' to the target cluster '%ls'.
- 40606 — Databases cannot be attached in this version of SQL Server.
- 40607 — Windows logins are not supported in this version of SQL Server.
- 40608 — This session has been assigned a tracing ID of '%.*ls'. Provide this tracing ID to customer support when you need assistance.
- 40609 — '%.*ls' is not a valid IPv4 address.
- 40610 — The IP address that starts with '%.*ls' is too long. Maximum length is %d.
- 40611 — Windows Azure SQL Database supports a maximum of 128 firewall rules.
- 40612 — Spec proc was executed against a silo that cannot be upgraded to include firewall objects.
- 40613 — Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, a…
- 40614 — Start IP address of firewall rule cannot exceed End IP address.
- 40615 — Cannot open server '%.*ls' requested by the login. Client with IP address '%.*ls' is not allowed to access the server. To enable access, use the Windo…
- 40616 — '%.*ls' is not a valid login name in this version of SQL Server.
- 40617 — The firewall rule name that starts with '%.*ls' is too long. Maximum length is %d.
- 40618 — The firewall rule name cannot be empty.
- 40619 — The edition '%.*ls' does not support the database data max size '%.*ls'.
- 40620 — The login failed for user "%.*ls". The password change failed. Password change during login is not supported in this version of SQL Server.
- 40621 — metric type
- 40622 — metric data
- 40623 — Reauthentication failed for login "%.*ls". Within the past reauthentification interval, the login has become invalid due to a password change, a dropp…
- 40624 — Operation is not allowed because server '%.*ls' is disabled.
- 40625 — Provisioning (creating, altering, or dropping) Windows Azure SQL Database servers and databases is currently disabled. This most frequently occurs for…
- 40626 — The ALTER DATABASE command is in process. Please wait at least five minutes before logging into database '%.*ls', in order for the command to complete…
- 40627 — Operation on server '%.*ls' and database '%.*ls' is in progress. Please wait a few minutes before trying again.
- 40628 — Failed to update database '%.*ls' because the database is read-only. Please contact your Windows Azure service owner. There may be billing related iss…
- 40629 — An edition could not be determined from maxsize '%.*ls'. Specify a valid maxsize value.
- 40630 — Password validation failed. The password does not meet policy requirements because it is too short.
- 40631 — The password that you specified is too long. The password should have no more than %d characters.
- 40632 — Password validation failed. The password does not meet policy requirements because it is not complex enough.
- 40633 — '%.*ls' is not a valid database edition in this version of SQL Server.
- 40634 — This stored procedure can only be executed in the master database.
- 40635 — Client with IP address "%.*ls" is temporarily blocked.
- 40636 — Cannot use reserved database name '%.*ls' in this operation.
- 40637 — Database copy is currently disabled.
- 40638 — Invalid subscription id '%.*ls'. Subscription does not exist.
- 40639 — Request does not conform to schema: %.*ls.
- 40640 — The server encountered an unexpected exception.
- 40641 — Location '%.*ls' cannot be found.
- 40642 — The server is currently too busy. Please try again later.
- 40643 — The specified x-ms-version header value is invalid.
- 40644 — Failed to authorize access to the specified subscription.
- 40645 — Servername "%.*ls" cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen may not le…
- 40646 — Subscription ID cannot be empty.
- 40647 — Subscription '%.*ls' does not have the server '%.*ls'.
- 40648 — Too many requests have been performed. Please retry later.
- 40649 — Invalid content-type is specified. Only application/xml is supported.
- 40650 — Subscription '%.*ls' is not ready for the operation because another operation is currently in progress. Please wait a few minutes and then try the ope…
- 40651 — Failed to create server because the subscription '%.*ls' is disabled.
- 40652 — Cannot move or create server. Subscription '%.*ls' will exceed server quota.
- 40653 — Could not find database '%.*ls' at time '%.*ls' that can be restored.
- 40654 — Specified subregion '%.*ls' is invalid.
- 40655 — Database 'master' cannot be restored.
- 40656 — Quota for maximum number of concurrent restores has been exceeded.
- 40657 — Restore is not enabled on the server.
- 40658 — Quota for number of restores has been exceeded.
- 40659 — Could not successfully restore database because the maximum duration for processing a restore has elapsed.
- 40660 — Could not successfully restore database. This request has been assigned a tracing ID of '%.*ls'. Provide this tracing ID to customer support when you …
- 40661 — Restore has been cancelled by a system administrator.
- 40662 — An internal error was encountered when processing the restore request. This request has been assigned a tracing ID of '%.*ls'. Provide this tracing ID…
- 40663 — Database '%.*ls' is currently being restored and cannot be dropped. Please wait for restore to complete.
- 40664 — Database 'master' cannot be copied.
- 40665 — '%.*ls' is not a supported collation.
- 40666 — '%.*ls' is a unicode-only collation and cannot be a default collation for a database.
- 40667 — Specifying a LOGIN is not allowed in a federation member.
- 40668 — '%.*ls' is not a valid user name or you do not have permission.
- 40669 — Location '%.*ls' is not accepting creation of new Windows Azure SQL Database servers at this time.
- 40670 — The http header 'ocp-resourceprovider-registered-uri' is missing from the request or is invalid. To continue, provide a valid value for the header.
- 40671 — Unable to '%.*ls' '%.*ls' on server '%.*ls'. Please retry the connection later.
- 40672 — The service objective assignment for a database cannot be changed more than once per %d hour(s). Please retry the operation %d hour(s) after the last …
- 40673 — The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the server name, database name and…
- 40674 — Service objective creation or assignment is not permitted for this subscription.
- 40675 — The service is currently too busy. Please try again later.
- 40676 — System databases cannot be %ls.
- 40677 — The operation for the request uri '%.*ls' was not found. To continue, please provide a valid request uri.
- 40678 — Invalid value for header '%.*ls'. The header must contain a single valid GUID.
- 40679 — The operation cannot be performed since the database '%ls' is not in a replication relationship.
- 40680 — The operation cannot be performed since the database '%ls' is in a replication relationship.
- 40681 — The operation cannot be performed since the database '%ls' is a replication target.
- 40682 — Failed to update database '%.*ls' because the database is a replication target.
- 40683 — The operation cannot be performed since the database '%ls' is not a replication target.
- 40684 — A seeding operation is already in progress for database '%ls'.
- 40685 — A terminate operation is already in progress for database '%ls'.
- 40686 — The operation is currently not supported.
- 40687 — The operation cannot be performed on the database '%ls' in its current state.
- 40688 — The databases '%ls' in server '%ls' and '%ls' in server '%ls' are already in a replication relation.
- 40689 — Replication limit reached. The database '%ls' cannot have more than %d replication relationships.
- 40690 — The operation cannot be performed since the replication source and target databases have different names. The source and target databases must have th…
- 40691 — Replication target cannot be created in the same server as source.
- 40692 — The alter database '%ls' failed to initiate because there are operations pending on the database. After the pending operations are complete, try again…
- 40693 — The current operation cannot be initiated while a replication operation is in progress. You can rename the database only after the replication operati…
- 40694 — The seeding operation cannot be initiated on a replication target database.
- 40695 — The operation cannot be performed since the database is currently a Federation root or member database.
- 40696 — sp_wait_for_database_copy_sync failed because the current database is not the primary database involved in a replication relationship with the specifi…
- 40697 — Login failed for user '%.*ls'.
- 40698 — '%.*ls' cannot be performed on a free database.
- 40699 — You cannot create a user with password in this version of SQL Server
- 40700 — Hardware generation '%.*ls' is currently unavailable in Azure SQL Database. Please create a SQL Database support request to resolve.
- 40701 — XML format used for specifying rules is invalid. %.*ls.
- 40702 — Failed to parse XML rules.
- 40703 — Invalid attribute name '%.*ls' in %.*ls.
- 40704 — Invalid element name '%.*ls' in %.*ls.
- 40705 — Invalid Feature type '%.*ls' in %.*ls.
- 40706 — Feature name '%.*ls' does not exist.
- 40707 — Invalid index value '%.*ls' in %.*ls.
- 40708 — Invalid param count '%.*ls' in %.*ls.
- 40709 — operator attribute is missing in %.*ls.
- 40711 — Rule name '%.*ls' does not exist.
- 40712 — Invalid usage of %.*ls.
- 40713 — Invalid values supplied for <parameter> element in %.*ls.
- 40714 — Out of memory.
- 40715 — Invalid operator type %.*ls in %.*ls.
- 40716 — Invalid input type %.*ls in %.*ls.
- 40717 — index attribute is missing in %.*ls.
- 40718 — one of inputtype, isnull and format attributes is required in %.*ls.
- 40719 — Failed to get %s lock on %s rules.
- 40720 — Rule name '%.*ls' already exists.
- 40721 — Only one of inputtype, isnull and format attributes is required in %.*ls.
- 40722 — Failed to clear proc cache.
- 40723 — Rule name cannot exceed more than %d characters.
- 40724 — Unexpected Operator attribute in %.*ls.
- 40801 — Operation ALTER USER WITH LOGIN failed. User provided login does not match the login in the federation root database for the user provided username.
- 40802 — A service objective assignment on server '%.*ls' and database '%.*ls' is already in progress. Please wait until the service objective assignment state…
- 40803 — The server '%.*ls' has reached its quota of (%d) premium databases.
- 40804 — The specified service objective '%.*ls' is invalid.
- 40805 — The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the activity ID.
- 40806 — The request to retrieve subscription information has timed out. Please try again later.
- 40807 — Could not retrieve subscription information for subscription id: %.*ls, after %d attempts. Please try again later.
- 40808 — The edition '%.*ls' does not support the service objective '%.*ls'.
- 40809 — No rows found in sys.dm_operation_status table for database '%.*ls' and operation '%.*ls'.
- 40810 — More than one row found in sys.dm_operation_status table for database '%.*ls' and operation '%.*ls'.
- 40811 — Operation '%.*ls' for database '%.*ls' cannot be cancelled as it has already completed.
- 40812 — Database '%.*ls' cannot be dropped as create operation is in progress. The create operation will be cancelled.
- 40813 — Could not set database as writable because the database is Premium (suspended).
- 40814 — Could not change database edition to or from Premium for a Federation root.
- 40815 — Could not change database edition to or from Premium for a Federation member.
- 40816 — Could not change database edition to Premium for a database in a replication relationship.
- 40817 — Could not change database edition from Premium for a database in a replication relationship.
- 40818 — The replication operation on database '%ls' failed because there are alter operations pending on the database. Try again after the pending operations …
- 40820 — The server has reached its quota of (%d) premium databases.
- 40821 — Federations are not supported on a Premium database.
- 40822 — This feature is not available for the selected database's edition (%ls).
- 40823 — Invalid proxy override option supplied.
- 40824 — ProxyOverrideSupport feature switch is not turned ON.
- 40825 — Unable to complete request now. Please try again later.
- 40826 — %ls is not available for %ls service tier.
- 40827 — The operation is not supported for your subscription offer type.
- 40838 — Replication relationship limit reached. The database '%ls' cannot have more than one non-readable secondary.
- 40839 — Connection to a non-readable secondary database is not allowed. See ' http://go.microsoft.com/fwlink/?LinkID=402429&clcid=0x409 ' for more information…
- 40840 — Target region '%ls' is not a DR paired Azure region. See ' http://go.microsoft.com/fwlink/?LinkID=402430&clcid=0x409 ' for more information.
- 40841 — Friendly termination of a non-readable replication relationship is not supported.
- 40842 — Termination of the non-readable replication relationship for database '%ls' is currently not allowed. See ' http://go.microsoft.com/fwlink/?LinkID=402…
- 40843 — Non-readable secondary is not supported for database copy.
- 40844 — Database '%ls' on Server '%ls' is a '%ls' edition database in an elastic pool and cannot have a replication relationship.
- 40845 — Server DNS Alias name '%.*ls' may only contain a single '@' when used to denote a SQL Server alias.
- 40846 — DNS alias '%.*ls' cannot be moved between DNS zones. Target server '%.*ls' is in a DNS zone ('%.*ls') that is different from the current server's '%.*…
- 40847 — Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of %d.
- 40848 — The source database '%ls'.'%ls' cannot have higher performance level than the target database '%ls'.'%ls'. Upgrade the performance level on the target…
- 40849 — The target database '%ls'.'%ls' cannot have lower performance level than the source database '%ls'.'%ls'. Downgrade the performance level on the sourc…
- 40850 — Could not change database edition from '%ls' to Standard for database '%ls' in a replication relationship.
- 40851 — Could not change database edition from '%ls' to Basic for database '%ls' in a replication relationship.
- 40852 — Cannot open database '%.*ls' on server '%.*ls' requested by the login. Access to the database is only allowed using a security-enabled connection stri…
- 40853 — A recovery request for a database that is currently in an elastic pool must include either a target elastic pool name or a target service objective.
- 40854 — Partner server '%ls' is not compatible with server '%ls.'
- 40855 — The operation cannot be performed since the database '%ls' is not in '%ls' state on the replication relationship.
- 40856 — Could not change database edition for database '%ls' in a replication relationship.
- 40857 — Elastic pool not found for server: '%ls', elastic pool name: '%ls'.
- 40858 — Elastic pool '%ls' already exists in server: '%ls'
- 40859 — Elastic pool does not support database edition '%ls'.
- 40860 — Elastic pool '%ls' and service level objective '%ls' combination is invalid.
- 40861 — The database edition '%ls' cannot be different than the elastic pool service tier which is '%ls'.
- 40862 — Elastic pool name must be specified if the elastic pool service objective is specified.
- 40863 — Connections to this database are no longer allowed.
- 40864 — The DTUs for the elastic pool must be at least (%d) DTUs for service tier '%.*ls'.
- 40865 — The DTUs for the elastic pool cannot exceed (%d) DTUs for service tier '%.*ls'.
- 40866 — Max size (%d) is not valid. Please specify a valid max size.
- 40867 — The DTU max per database must be at least (%d) for service tier '%.*ls'.
- 40868 — The DTU max per database cannot exceed (%d) for service tier '%.*ls'.
- 40869 — The DTU max per database (%d) for the elastic pool does not belong to the specified values for service tier '%.*ls'.
- 40870 — The DTU min per database cannot exceed (%d) for service tier '%.*ls'.
- 40871 — The DTU min per database (%d) for the elastic pool does not belong to the allowed values for service tier '%.*ls'.
- 40872 — DTU value (%d) is not valid. Please specify a valid dtu value.
- 40873 — The number of databases (%d) and DTU min per database (%d) cannot exceed the DTUs of the elastic pool (%d).
- 40874 — The DTUs (%d) for the elastic pool does not belong to the specified values for service tier '%.*ls'.
- 40875 — The elastic pool storage limit in gigabytes cannot exceed (%d) in service tier '%.*ls'.
- 40876 — Elastic pools are not available in this region.
- 40877 — The elastic pool is not empty.
- 40878 — The elastic pool storage limit in gigabytes must be at least (%d) for service tier '%.*ls'.
- 40879 — The elastic pool storage limit in gigabytes (%d) does not belong to the allowed values for service tier '%.*ls'.
- 40880 — The DTUs (%d) for the elastic pool and the storage limit in gigabytes (%d) are inconsistent for service tier '%.*ls'.
- 40881 — The elastic pool '%.*ls' has reached its database count limit. The database count for the elastic pool cannot exceed (%d) for service tier '%.*ls'.
- 40882 — Can not change SLO from DataWarehouse edition to other SQL DB editions and vice versa.
- 40883 — The service level objective '%.*ls' specified is invalid. It must be a slo supported by DataWarehouse edition.
- 40884 — New service level objective '%.*ls' has (%d) physical databases and it is not compatible with current service level objective which has (%d) physical …
- 40885 — Failed to deactivate database.
- 40886 — Failed to change service level objective for database.
- 40887 — Failed to activate database.
- 40888 — Update service level objective for database feature is disabled.
- 40889 — The DTUs or storage limit for the elastic pool '%.*ls' cannot be decreased since that would not provide sufficient storage space for its databases.
- 40890 — The elastic pool is busy with another operation.
- 40891 — The DTU min per database (%d) cannot exceed the DTU max per database (%d).
- 40892 — Cannot connect to database when it is paused.
- 40893 — The database copy link from '%s.%s' to '%s.%s' was not successfully created or was deleted before the data copy link operation completed.
- 40894 — The database copy link from '%s.%s' to '%s.%s' is not in the catchup state after the data copy link operation completed.
- 40895 — The database copy link from '%s.%s' to '%s.%s' was not successfully deleted before completion of copy.
- 40896 — The database copy link from '%s.%s' to ID %s was not successfully dropped.
- 40897 — The elastic pool storage limit in megabytes must be at least (%d) for service tier '%.*ls'.
- 40898 — The elastic pool storage limit in megabytes (%d) does not belong to the allowed values for service tier '%.*ls'.
- 40899 — The DTUs (%d) for the elastic pool and the storage limit in megabytes (%d) are inconsistent for service tier '%.*ls'.
- 40900 — The service tier for an elastic pool cannot be changed.
- 40901 — The elastic pool storage limit in megabytes cannot exceed (%d) in service tier '%.*ls'.
- 40902 — Amount of pool storage cannot be specified when creating a Premium elastic pool.
- 40903 — The server '%.*ls' is currently busy. Please wait a few minutes before trying again.
- 40904 — Could not perform the operation because server would exceed the allowed Database Edition %s quota of %d.
- 40905 — Location '%.*ls' is not accepting creation of new Azure SQL Database Servers of version '%.*ls' at this time. This location only supports the followin…
- 40906 — A service objective change cannot start for database %s on server %s while it is also running for database %s on server %s.
- 40907 — Servers involved in a Disaster Recovery Configuration cannot reside in the same location
- 40908 — A Disaster Recovery Configuration already exists for '%.*ls' and '%.*ls'
- 40909 — A Disaster Recovery Configuration does not exist for '%.*ls' and '%.*ls'
- 40910 — A Disaster Recovery Configuration does not exist for server '%.*ls' and virtual endpoint '%.*ls'
- 40911 — Server '%.*ls' is not the secondary in the Disaster Recovery Configuration and cannot initiate a failover
- 40912 — The value for custom backup retention in days must be between %d and %d
- 40913 — Windows Azure SQL Database supports a maximum of %d Virtual Network firewall rules.
- 40914 — Cannot open server '%.*ls' requested by the login. Client from a Virtual Network with Service Tunneling is not allowed to access the server.
- 40915 — Secondary server specified in a Failover Group cannot reside in the same region
- 40916 — The Failover Group '%.*ls' already exists on server '%.*ls'
- 40917 — The Failover Group '%.*ls' does not exist on server '%.*ls'
- 40918 — The Failover Group '%.*ls' is busy with another operation and cannot perform '%.*ls' operation. Please try again later
- 40919 — The server '%.*ls' is currently the primary server in the Failover Group and cannot initate failover
- 40920 — The database '%.*ls' is already included in another Failover Group
- 40921 — The operation to add database '%.*ls' to Failover Group is in progress, please wait for this operation to finish
- 40922 — The operation to remove database '%.*ls' from Failover Group is in progress, please wait for this operation to finish
- 40923 — The database '%.*ls' is a secondary in an existing geo-replication relationship and cannot be added to the Failover Group
- 40924 — The operation cannot be performed due to multiple errors: '%.*ls'
- 40925 — Can not connect to the database in its current state.
- 40926 — The operation cannot be performed because the geo-replication link is part of a Failover Group. You must remove the database from the group in order t…
- 40927 — The endpoint '%.*ls' is already in use. Use a different Failover Group name.
- 40928 — Create or update Failover Group operation successfully completed; however, some of the databases could not be added to or removed from Failover Group:…
- 40929 — The source database '%ls.%ls' cannot have higher edition than the target database '%ls.%ls'. Upgrade the edition on the target before upgrading source…
- 40930 — The target database '%ls.%ls' cannot have lower edition than the source database '%ls.%ls'. Downgrade the edition on the source before downgrading tar…
- 40931 — Failover Group name '%.*ls' cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen m…
- 40932 — The elastic pool cannot change its service tier since one or more of its databases use memory-optimized objects.
- 40933 — The edition '%.*ls' does not support the database tempdb max size '%.*ls'.
- 40934 — Server DNS Alias name '%.*ls' cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen…
- 40935 — The endpoint '%.*ls' is already in use. Use a different Server DNS Alias name.
- 40936 — The Server DNS Alias '%.*ls' already exists for the server '%.*ls'.
- 40937 — The Server DNS Alias '%.*ls' does not exist for the server '%.*ls'.
- 40938 — The Server DNS Alias '%.*ls' is busy with another operation and cannot perform the '%.*ls' operation. Please try again later.
- 40939 — The scale operation from service level objective '%.*ls' to new service level objective '%.*ls' is not supported. Please file a support ticket.
- 40940 — The elastic pool '%.*ls' cannot be updated because one of its databases is performing a copy or geo-replication failover operation.
- 40941 — Copy operation for the database '%.*ls' on the server '%.*ls' cannot be started because the elastic pool '%.*ls' is currently being updated.
- 40942 — A service objective assignment operation cannot be performed because copy or failover operation for the database '%.*ls' on the server '%.*ls' is in p…
- 40943 — A Failover Group cannot be created on the server '%.*ls' because the Table Auditing feature is enabled for this server.
- 40944 — The database '%.*ls' on the server '%.*ls' cannot be added to a Failover Group because the Table Auditing or Security Enabled Access feature is turned…
- 40945 — The Table Auditing feature cannot be turned on for a server that contains Failover Groups. Please try Blob Auditing instead.
- 40946 — The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is part of a Failover Group.
- 40947 — The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is located on a server with a Server DNS Alias.
- 40948 — A Server DNS Alias cannot be created for the server '%.*ls' because the Table Auditing feature is enabled for this server.
- 40949 — A Server DNS Alias cannot be created for the server '%.*ls' because the database '%.*ls' has the Table Auditing or Security Enabled Access feature ena…
- 40950 — The Dns Alias '%.*ls' already exists for the elastic pool '%.*ls' on server '%.*ls'.
- 40951 — The Dns Alias '%.*ls' does not exist for the elastic pool '%.*ls' on server '%.*ls'.
- 40952 — A Server DNS Alias cannot be created because server '%.*ls' would exceed the allowed Server DNS Aliases quota of %d.
- 40953 — A Failover Group cannot be created because server '%.*ls' would exceed the allowed Failover Groups quota of %d.
- 40954 — The Table Auditing feature cannot be turned on for a server that contains Server Dns Aliases. Please try Blob Auditing instead.
- 40955 — The operation cannot be performed due to insufficient file space in the elastic pool. The operation requires (%d) MBs file space and there are (%d) MB…
- 40956 — The Server Disaster Recovery Configuration feature is deprecated. Please use Failover Group instead.
- 40957 — The DTU min per database must be at least (%d) for service tier '%.*ls'.
- 40958 — The VCore max per database must be at least (%d) for service tier '%.*ls'.
- 40959 — The VCore max per database cannot exceed (%d) for service tier '%.*ls'.
- 40960 — The VCore max per database (%d) for the elastic pool does not belong to the specified values for service tier '%.*ls'.
- 40961 — The VCore min per database cannot exceed (%d) for service tier '%.*ls'.
- 40962 — The VCore min per database must be at least (%d) for service tier '%.*ls'.
- 40963 — The VCore min per database (%d) for the elastic pool does not belong to the allowed values for service tier '%.*ls'.
- 40964 — The VCore min per database (%d) cannot exceed the VCore max per database (%d).
- 40965 — The service level objective '%.*ls' does not support the license type '%.*ls'.
- 40966 — No service objective was found for capacity '%d' in edition '%.*ls'
- 40967 — More than one service objective was found for capacity '%d' in edition '%.*ls'
- 40968 — Operation results in exceeding quota limits of %d. Maximum allowed: %d.
- 40969 — Cannot open server '%.*ls' requested by the login. Client is not allowed to access the server.
- 40970 — Can not change from '%.*ls' edition to '%.*ls' edition.
- 40971 — Cannot open Failover Group "%.*ls" requested by the login. The login failed.
- 40972 — Database copy limit per database reached. The database '%ls' cannot have more than %d concurrent database copies.
- 40973 — Can not drop database because a failover operation is in progress on the failover group.
- 40974 — Partner region specified does not match region of partner managed instance.
- 40975 — Partner managed instance's DNS Zone does not match the DNS Zone of the source managed instance.
- 40976 — Instance Failover Group cannot be created because partner managed server "%.*ls" is not empty or does not have secondaries for all databases in the pr…
- 40977 — '%.*ls' is not a supported timezone.
- 40978 — Instance failover group cannot be created because the reserved storage size on the secondary instance is different from the reserved storage size on t…
- 40979 — Database is unavailable because it is paused. Server '%.*ls', Database '%.*ls'. Please resume before trying to access the database again.
- 40980 — Partner managed server's managed server/failover group has been dropped.
- 40981 — Database '%.*ls' is not accessible due to Azure Key Vault critical error.
- 40982 — Instance failover group cannot be created because the secondary instance has user databases.
- 40983 — Replication to the partner managed instance could not be established. Verify that connectivity between the Virtual Networks of the primary and seconda…
- 40984 — Restore and GeoRestore target cannot be free database.
- 40985 — Restore and GeoRestore are not supported for free database.
- 40986 — Source database '%s' dropped on '%s' does not exist on server '%s' within the supported recovery period.
- 40987 — Source database '%s' does not exist on server '%s' within the supported recovery period. If restoring a dropped database, please specify its deletion …
- 40988 — The Hyperscale edition recovery requires both source and target databases to use VLDB service level objective.
- 40989 — he Hyperscale edition Point-In-Time restore requires both source and target databases to use VLDB service level objective.
- 40990 — Specifying an elastic pool and/or changing the service level objective or edition is not supported for '%s' edition.
- 40991 — Changing geo-backup policy is not supported for %s tier of SQL Data Warehouse.
- 40992 — Cannot perform this operation when the database is paused.
- 40993 — Enabling long-term retention (LTR) for a serverless database is not supported if auto-pause is enabled.
- 40994 — Enabling auto-pause for a serverless database is not supported if long-term retention (LTR) is enabled.
- 40995 — Enabling geo-replication for a serverless database is not supported if auto-pause is enabled.
- 40996 — Enabling auto-pause for a serverless database is not supported if geo-replication is enabled.
- 40997 — Elastic pool '%ls' does not exist in server '%ls'. Please make sure that the elastic pool name is entered correctly. Please contact Microsoft support …
- 40998 — The edition '%.*ls' does not support '%.*ls' bytes as the database data max size. For more details, see <>.
- 40999 — '%ls' is not a valid service level objective for elastic pool '%ls'.
- 41000 — Failed to obtain the local Windows Server Failover Clustering (WSFC) handle (Error code %d). If this is a WSFC availability group, the WSFC service ma…
- 41001 — Failed to obtain local computer name (Error code %d). The supplied buffer may be too small, or there is a system error. For information about this err…
- 41002 — Failed to obtain the local Windows Server Failover Clustering (WSFC) node handle (Error code %d). If this is a WSFC availability group, the WSFC servi…
- 41003 — Failed to obtain the local Windows Server Failover Clustering (WSFC) node ID (Error code %d). If this is a WSFC availability group, the WSFC service m…
- 41004 — Failed to obtain the Windows Server Failover Clustering (WSFC) group handle for cluster group with name or ID '%s' (Error code %d). If this is a WSFC …
- 41005 — Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID '%s' (Error code %d). If this is a…
- 41006 — Failed to create the Windows Server Failover Clustering (WSFC) group with name '%s' (Error code %d). If this is a WSFC availability group, the WSFC se…
- 41007 — The Windows Server Failover Clustering (WSFC) group control API returned error code %d. If this is a WSFC availability group, the WSFC service may not…
- 41008 — Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%s' and type '%s' (Error code %d). If this is a WSFC availability g…
- 41009 — The Windows Server Failover Clustering (WSFC) resource control API returned error code %d. If this is a WSFC availability group, the WSFC service may …
- 41010 — Failed to bring the Windows Server Failover Clustering (WSFC) group online (Error code %d). If this is a WSFC availability group, the WSFC service may…
- 41011 — Failed to take the Windows Server Failover Clustering (WSFC) group offline (Error code %d). If this is a WSFC availability group, the WSFC service may…
- 41012 — The Windows Server Failover Clustering (WSFC) node control API returned error code %d. If this is a WSFC availability group, the WSFC service may not …
- 41013 — Failed to obtain the Windows Server Failover Clustering (WSFC) resource enumeration handle (Error code %d). If this is a WSFC availability group, the …
- 41014 — Failed to enumerate the Windows Server Failover Clustering (WSFC) resources (Error code %d). If this is a WSFC availability group, the WSFC service ma…
- 41015 — Failed to obtain the Windows Server Failover Clustering (WSFC) node handle (Error code %d) for node '%.*ls'. If this is a WSFC availability group, the…
- 41016 — Failed to remove a node from the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code %d). If this is a WSFC availa…
- 41017 — Failed to add a node to the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code %d). If this is a WSFC availabilit…
- 41018 — Failed to move a Windows Server Failover Clustering (WSFC) group to the local node (Error code %d). If this is a WSFC availability group, the WSFC ser…
- 41019 — Failed to drop a Windows Server Failover Clustering (WSFC) group with name or ID '%.*ls' (Error code %d). If this is a WSFC availability group, the WS…
- 41020 — Failed to find a String property (property name '%s') of the Windows Server Failover Clustering (WSFC) resource with name or ID '%.*ls' (Error code %d…
- 41021 — Failed to find a DWORD property (property name '%s') of the Windows Server Failover Clustering (WSFC) resource with ID '%.*ls' (Error code %d). If thi…
- 41022 — Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter %d and notification key %d (Error code %d). If…
- 41023 — The Windows Server Failover Clustering (WSFC) change handle is invalid because a WSFC notification port has not been created or has been closed. Creat…
- 41024 — Failed to register additional Windows Server Failover Clustering (WSFC) change notifications with notification filter %d and notification key %d (Erro…
- 41025 — Failed to receive Windows Server Failover Clustering (WSFC) change notifications (Error code %d). If this is a WSFC availability group, the WSFC servi…
- 41026 — Failed to create the Windows Server Failover Clustering (WSFC) group with name '%ls'. The WSFC group with the specified name already exists. Retry the…
- 41027 — Failed to start the Windows Server Failover Clustering (WSFC) change listener (SQLOS error code %d). SQL Server may not have sufficient resources to s…
- 41028 — Failed to open Windows Server Failover Clustering (WSFC) registry root key (Error code %d). If this is a WSFC availability group, the WSFC service may…
- 41029 — Failed to open the Windows Server Failover Clustering (WSFC) resource registry key '%.*ls' (Error code %d). If this is a WSFC availability group, the …
- 41030 — Failed to open the Windows Server Failover Clustering registry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root key. If this is a …
- 41031 — Failed to create the Windows Server Failover Clustering (WSFC) registry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root key. If t…
- 41032 — Failed to delete the Windows Server Failover Clustering (WSFC) registry subkey '%.*ls' (Error code %d). The parent key is %sthe cluster root key. If t…
- 41033 — Failed to retrieve the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%.*ls' (Error code %d). If this is a WSFC avail…
- 41034 — Failed to set the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%.*ls' (Error code %d). If this is a WSFC availabili…
- 41035 — Failed to enumerate Windows Server Failover Clustering (WSFC) registry value (Error code %d). If this is a WSFC availability group, the WSFC service m…
- 41036 — Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%.*ls' (Error code %d). If this is a WSFC availab…
- 41037 — Failed to obtain a Windows Server Failover Clustering (WSFC) object enumeration handle for objects of type %d (Error code %d). If this is a WSFC avail…
- 41038 — Failed to enumerate Windows Server Failover Clustering (WSFC) objects (Error code %d). If this is a WSFC availability group, the WSFC service may not …
- 41039 — An availability group replica already exists on the node '%.*ls'. Each node can contain only one replica of an availability group. Please choose anoth…
- 41040 — Failed to remove the availability group replica '%.*ls' from availability group '%.*ls'. The availability group does not contain a replica with the sp…
- 41041 — SQL Server instance to cluster node map entry cannot be found for the SQL Server instance '%.*ls' and group ID '%.*ls'. The specified SQL Server insta…
- 41042 — The availability group '%.*ls' already exists. This error could be caused by a previous failed CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP op…
- 41043 — For availability group '%.*ls', the value of the name-to-ID map entry is invalid. The binary value should contain a resource ID, a group ID, and their…
- 41044 — Availability group name to ID map entry for availability group '%.*ls' cannot be found. The availability group name may be incorrect. If this is a WSF…
- 41045 — Cannot add database '%.*ls' to the availability group '%.*ls', because there is already a database with the same name in the availability group. Pleas…
- 41046 — Cannot add replica '%.*ls' to the availability group '%.*ls', because there is already a replica with the same name in the availability group. Please …
- 41047 — Failed to obtain the Windows Server Failover Clustering (WSFC) node state for the local WSFC node (Error code %d). If this is a WSFC availability grou…
- 41048 — Always On Availability Groups: Local Windows Server Failover Clustering service has become unavailable. This is an informational message only. No user…
- 41049 — Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user actio…
- 41050 — Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user a…
- 41051 — Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is requ…
- 41052 — Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user acti…
- 41053 — Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is require…
- 41054 — Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No use…
- 41055 — Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is requi…
- 41056 — Availability replica '%.*ls' of availability group '%.*ls' cannot be brought online on this SQL Server instance. Another replica of the same availabil…
- 41057 — Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%ls'. The WSFC resource with the specified name already exists. Ret…
- 41058 — Always On: The local replica of availability group '%.*ls' is starting. This is an informational message only. No user action is required.
- 41059 — Always On: Availability group '%.*ls' was removed while the availability replica on this instance of SQL Server was offline. The local replica will be…
- 41060 — The Cyclic Redundancy Check (CRC) value generated for the retrieved availability group configuration data does not match that stored with the data for…
- 41061 — Always On: The local replica of availability group '%.*ls' is stopping. This is an informational message only. No user action is required.
- 41062 — The ID of availability group '%.*ls' in local data store is inconsistent with that in the Windows Server Failover Clustering (WSFC) data store. The av…
- 41063 — Windows Server Failover Clustering (WSFC) detected that the availability group resource with ID '%.*ls' was online when the availability group was not…
- 41064 — Failed to set local node as sole preferred owner for the Windows Server Failover Clustering (WSFC) group with ID '%.*ls' (Error code: %d). The WSFC gr…
- 41065 — Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID: '%.*ls') online at this time. The WSFC resource is not in a state that can ac…
- 41066 — Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID '%.*ls') online (Error code %d). If this is a WSFC availability group, the WSF…
- 41067 — Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name '%.*ls') at this time. The WSFC group is not in a state that could accept …
- 41068 — Failed to enumerate the Windows Server Failover Clustering (WSFC) registry key (Error code %d). If this is a WSFC availability group, the WSFC service…
- 41069 — The existence of availability group data for the availability group '%.*ls' in the Windows Server Failover Clustering (WSFC) store could not be determ…
- 41070 — Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID '%.*ls' is not found in the WSFC data store. …
- 41071 — Cannot read the persisted configuration of Always On availability group with corresponding resource ID '%.*ls'. The persisted configuration is written…
- 41072 — The ID of availability group '%.*ls' in local data store does not exist in the Windows Server Failover Clustering (WSFC) data store. The availability …
- 41073 — The database '%.*ls' cannot be removed from availability group '%.*ls'. This database does not belong to the availability group.
- 41074 — Always On: The local replica of availability group '%.*ls' is preparing to transition to the primary role. This is an informational message only. No u…
- 41075 — Always On: The local replica of availability group '%.*ls' is preparing to transition to the resolving role. This is an informational message only. No…
- 41076 — Always On: Availability group '%.*ls' is going offline because it is being removed. This is an informational message only. No user action is required.
- 41077 — Cannot bring the Windows Server Failover Clustering (WSFC) group (ID '%.*ls') online at this time. The WSFC group is not in a state that could accept …
- 41078 — Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%.*ls', because a registry entry with the specifi…
- 41079 — Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name '%.*ls'), because the WSFC group does not exist. Specify a valid WSFC grou…
- 41080 — Failed to delete SQL Server instance name to Windows Server Failover Clustering node name map entry for the local availability replica of availability…
- 41081 — Failed to destroy the Windows Server Failover Clustering group corresponding to availability group '%.*ls'. The operation encountered SQL Server error…
- 41082 — Failed to obtain the name of local Windows Server Failover Cluster (Error code %d). If this is a WSFC availability group, the WSFC service may not be …
- 41083 — Failed to obtain the cluster quorum resource (Error code %d). If this is a WSFC availability group, the WSFC service may not be running or may not be …
- 41084 — The Windows Server Failover Clustering (WSFC) cluster control API returned error code %d. If this is a WSFC availability group, the WSFC service may n…
- 41085 — Failed to find a DWORD property (property name '%s') of the Windows Server Failover Clustering (WSFC) (Error code %d). If this is a WSFC availability …
- 41086 — Failed to retrieve the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whe…
- 41087 — Error in parsing the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify wheth…
- 41088 — Failed to determine if the Windows Server Failover Clustering (WSFC) service is in Force Quorum state. The prerequisite hotfix, KB 2494036, might not …
- 41089 — Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user action i…
- 41090 — Failed to update Replica status due to exception %d.
- 41091 — Always On: The local replica of availability group '%.*ls' is going offline because either the lease expired or lease renewal failed. This is an infor…
- 41092 — Always On: The availability replica manager is going offline because %ls. This is an informational message only. No user action is required.
- 41093 — Always On: The local replica of availability group '%.*ls' is going offline because the corresponding resource in the Windows Server Failover Clusteri…
- 41094 — Always On: The local replica of availability group '%.*ls' is restarting because the existing primary replica restarted or the availability group fail…
- 41095 — Always On: Explicitly transitioning the state of the Windows Server Failover Clustering (WSFC) resource that corresponds to availability group '%.*ls'…
- 41096 — Always On: The local replica of availability group '%.*ls' is being removed. The instance of SQL Server failed to validate the integrity of the availa…
- 41097 — Always On: The local replica of availability group '%.*ls' is going offline. This replica failed to read the persisted configuration because of a vers…
- 41098 — Always On: The local replica of availability group '%.*ls' is restarting, because it failed to read the persisted configuration. This is an informatio…
- 41099 — Always On: The local replica of availability group '%.*ls' is going offline. This replica failed to read the persisted configuration, and it has exhau…
- 41100 — The availability group '%.*ls' and/or its local availability replica does not exist. Verify that the specified availability group name is correct, and…
- 41101 — The availability group with Windows Server Failover Clustering resource ID '%.*ls' and/or its local availability replica does not exist. Verify that t…
- 41102 — Failed to persist configuration data of availability group '%.*ls'. The local availability replica either is not the primary replica or is shutting do…
- 41103 — Startup of the Always On Availability Replica Manager has been terminated, because the 'FixQuorum' property of Windows Server Failover Clustering (WSF…
- 41104 — Failover of the availability group '%.*ls' to the local replica failed because the availability group resource did not come online due to a previous e…
- 41105 — Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%s' and type '%s'. The resource type is not registered in the WSFC …
- 41106 — Cannot create an availability replica for availability group '%.*ls'. An availability replica of the specified availability group already exists on th…
- 41107 — Availability group '%.*ls' failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%d) when obtaining handles for…
- 41108 — An error occurred while removing availability group '%.*ls'. The DROP AVAILABILITY GROUP command removed the availability group configuration from the…
- 41109 — Could not enqueue a task (SQL OS error: 0x%x) for process actions for the availability group '%.*ls'. Most likely, the instance of SQL Server is low o…
- 41110 — Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
- 41111 — Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message on…
- 41112 — A Windows Server Failover Clustering (WSFC) API required by availability groups has not been loaded. Always On Availability Groups replica manager is …
- 41113 — Cannot failover availability group '%.*ls' to this instance of SQL Server because a failover command is already pending on the local replica of this a…
- 41114 — Cannot create an availability group named '%.*ls' because it already exists in a system table.
- 41115 — Cannot create the availability group named '%.*ls' because its availability group ID (ID: '%.*ls') already exists in a system table.
- 41116 — Cannot create an availability group named '%.*ls' with replica ID '%.*ls' because this ID already exists in a system table.
- 41117 — Cannot map local database ID %d to the availability database ID '%.*ls' within availability group '%.*ls'. This database is already mapped to an avail…
- 41118 — Cannot map database ID %d to the availability database ID '%.*ls' within availability group '%.*ls'. Another local database, (ID %d). is already mappe…
- 41119 — Could not find the availability group ID %d in the system table.
- 41120 — Failed to start task to process a down notification for the local Windows Server Failover Clustering (WSFC) node (SQL OS error: %d). Possible causes a…
- 41121 — The local availability replica of availability group '%.*ls' cannot accept signal '%s' in its current replica role, '%s', and state (configuration is …
- 41122 — Cannot failover availability group '%.*ls' to this instance of SQL Server. The local availability replica is already the primary replica of the availa…
- 41123 — Cannot bring the Windows Server Failover Clustering (WSFC) group (ID '%.*ls') online at this time. The WSFC group is moving to another node. Please wa…
- 41124 — The availability replica for availability group '%.*ls' on this instance of SQL Server cannot become the primary replica because the availability grou…
- 41125 — The availability replica for availability group '%.*ls' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was …
- 41126 — Operation on the local availability replica of availability group '%.*ls' failed. The local copy of the availability group configuration does not exis…
- 41127 — Attempt to set database mapping state where the local database id %d is not mapped to any availability group.
- 41128 — Failed to perform database operation '%s' on database '%.*ls' (ID %d) in availability group '%.*ls'. The database might be in an incorrect state for t…
- 41129 — Failed to schedule or execute database operation '%s' on database '%.*ls' (Database ID: %d) in availability group '%.*ls' (SQL OS error: %d). The inst…
- 41130 — Operation '%s' on a database '%.*ls' (Database ID: %d) in availability group '%.*ls' failed with SQL Server error %d (Error details: "%.*ls"). The ope…
- 41131 — Failed to bring availability group '%.*ls' online. The operation timed out. If this is a Windows Server Failover Clustering (WSFC) availability group,…
- 41132 — Cannot join database '%.*ls' to availability group '%.*ls'. The specified database does not belong to the availability group. Verify the names of the …
- 41133 — Cannot remove database '%.*ls' from availability group '%.*ls'. Either the database does not belong to the availability group, or the database has not…
- 41134 — Cannot bring the availability group '%.*ls' online. The local instance was not the previous primary replica when the availability group went offline, …
- 41135 — Startup of Always On Availability Groups replica manager failed due to SQL Server error %d. To determine the cause of this error, check the SQL Server…
- 41136 — Failed to join the availability replica to availability group '%.*ls' because the group is not online. Either bring the availability group online, or …
- 41137 — Abandoning a database operation '%ls' on availability database '%.*ls' of availability group '%.*ls'. The sequence number of local availability replic…
- 41138 — Cannot accept Always On Availability Groups operation operation on database '%.*ls' of availability group '%.*ls'. The database is currently processin…
- 41139 — Failed to set database information for availability group %.*ls. The local availability replica is not the primary replica, or it is shutting down. Th…
- 41140 — Availability group '%.*ls' cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is not the primary replica. Con…
- 41141 — Failed to set availability group database information for availability group %.*ls. The local availability replica is not the primary, or is shutting …
- 41142 — The availability replica for availability group '%.*ls' on this instance of SQL Server cannot become the primary replica. One or more databases are no…
- 41143 — Cannot process the operation. The local replica of availability Group '%.*ls' is in a failed state. A previous operation to read or update persisted c…
- 41144 — The local availability replica of availability group '%.*ls' is in a failed state. The replica failed to read or update the persisted configuration da…
- 41145 — Cannot join database '%.*ls' to availability group '%.*ls'. The database has already joined the availability group. This is an informational message. …
- 41146 — Failed to bring Availability Group '%.*ls' online. If this is a WSFC availability group, the Windows Server Failover Clustering (WSFC) service may not…
- 41147 — Always On Availability Groups was not started because %ls. This is an informational message. No user action is required.
- 41148 — Cannot add or join database '%.*ls' to availability group '%.*ls'. The database does not exist on this instance of SQL Server. Verify the database nam…
- 41149 — Operation on the availability group '%.*ls' has been cancelled or terminated, either because of a connection timeout or cancellation by user. This is …
- 41150 — Failed to take availability group '%.*ls' offline. If this is a WSFC availability group, the Windows Server Failover Clustering (WSFC) service may not…
- 41151 — Error accessing the Availability Groups manager. The local Availability Groups manager has not been initialized. Wait until the Availability Groups ma…
- 41152 — Failed to create availability group '%.*ls'. The operation encountered SQL Server error %d and has been rolled back. Check the SQL Server error log fo…
- 41153 — Failed to create availability group '%.*ls'. The operation encountered SQL Server error %d. An attempt to roll back the operation failed. Check the SQ…
- 41154 — Cannot failover availability group '%.*ls' to this SQL Server instance. The availability group is still being created. Verify that the specified avail…
- 41155 — Cannot failover availability group '%.*ls' to this instance of SQL Server. The availability group is being dropped. Verify that the specified availabi…
- 41156 — Cannot drop availability group '%.*ls' from this instance of SQL Server. The availability group is either being dropped, or the local availability rep…
- 41157 — Cannot remove the local availability replica from availability group '%.*ls' from this instance of SQL Server. The availability group is either being …
- 41158 — Failed to join local availability replica to availability group '%.*ls'. The operation encountered SQL Server error %d and has been rolled back. Check…
- 41159 — Failed to join local availability replica to availability group '%.*ls'. The operation encountered SQL Server error %d. An attempt to rollback the ope…
- 41160 — Failed to designate the local availability replica of availability group '%.*ls' as the primary replica. The operation encountered SQL Server error %d…
- 41161 — Failed to validate the Cyclic Redundancy Check (CRC) of the configuration of availability group '%.*ls'. The operation encountered SQL Server error %d…
- 41162 — Failed to validate sequence number of the configuration of availability group '%.*ls'. The in-memory sequence number does not match the persisted sequ…
- 41163 — An error occurred while waiting for the local availability replica of availability group '%.*ls' to transition to the primary role. The operation enco…
- 41164 — An error occurred while waiting for the local availability replica of availability group '%.*ls' to transition to the resolving role. The operation en…
- 41165 — A timeout error occurred while waiting to access the local availability replica of availability group '%.*ls'. The availability replica is currently b…
- 41166 — An error occurred while waiting to access the local availability replica of availability group '%.*ls'. The operation encountered SQL OS error %d, and…
- 41167 — An error occurred while attempting to access availability replica '%.*ls' in availability group '%.*ls'. The availability replica is not found in the …
- 41168 — An error occurred while attempting to access availability replica with ID '%.*ls' in availability group '%.*ls'. The availability replica is not found…
- 41169 — An error occurred while attempting to access the availability group database with ID '%.*ls' in availability group '%.*ls'. The availability database …
- 41170 — Post-online processing for availability group '%.*ls' has been terminated. Either post-online processing has already completed, the local availability…
- 41171 — Failed to create availability group '%.*ls', because a Windows Server Failover Cluster (WSFC) group with the specified name already exists. The operat…
- 41172 — An error occurred while dropping availability group '%.*ls'. The operation encountered SQL OS error %d, and has been terminated. Verify that the speci…
- 41173 — An error occurred while removing the local availability replica from availability group '%.*ls'. The operation encountered SQL OS error %d, and has be…
- 41174 — Failed to start the task of the Windows Server Failover Clustering (WSFC) event notification worker (SQL OS error: %d). If the problem persists, you m…
- 41175 — Failed to stop the task of WSFC event notification worker (SQL OS error: %d). If the problem persists, you might need to restart the instance of SQL S…
- 41176 — Failed to acquire exclusive access to local availability group configuration data (SQL OS error: %d). If the problem persists, you might need to resta…
- 41177 — The availability replica of the specified availability group '%.*ls' is being dropped. Wait for the completion of the drop command and retry the opera…
- 41178 — Cannot drop availability group '%.*ls' from this SQL Server instance. The availability group is currently being created. Verify that the specified ava…
- 41179 — Cannot remove the local availability replica from availability group '%.*ls' from this instance of SQL Server. The availability group is currently bei…
- 41180 — Attempt to access non-existent or uninitialized availability group with ID '%.*ls'. This is usually an internal condition, such as the availability gr…
- 41181 — The local availability replica of availability group '%.*ls' did not become primary. A concurrent operation may have changed the state of the availabi…
- 41182 — Failed to set the local availability replica of availability group '%.*ls' as joined in Windows Server Failover Clustering (WSFC) database. Either the…
- 41183 — Failed to modify availability replica options for availability group '%.*ls'. Before the availability group configuration could be updated, the operat…
- 41184 — Failed to modify availability replica options for availability group '%.*ls'. The availability group configuration has been updated. However, the oper…
- 41185 — Replica option specified in ALTER AVAILABILITY GROUP '%.*ls' MODIFY DDL is same is cached availability group configuration.
- 41186 — Availability group '%.*ls' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is still being created. Verify that…
- 41187 — Availability group '%.*ls' cannot process an ALTER AVAILABILITY GROUP command at this time. The availability group is being dropped. Verify that the s…
- 41188 — Availability group '%.*ls' failed to process %s-%s command. The operation encountered SQL Server error %d before the availability group configuration …
- 41189 — Availability group '%.*ls' failed to process the %s-%s command. The availability group configuration has been updated. However, the operation encounte…
- 41190 — Availability group '%.*ls' failed to process %s-%s command. The local availability replica is not in a state that could process the command. Verify th…
- 41191 — The local availability replica of availability group '%.*ls' cannot become the primary replica. The last-known primary availability replica is of a hi…
- 41192 — Creating and scheduling a worker task for Always On Availability Groups failed due to lack of resources (SQL OS error %d). Processing of new actions m…
- 41193 — Cannot join database '%.*ls' to availability group '%.*ls'. The database is in the process of being removed from the availability group. When the remo…
- 41194 — An error occurred while waiting for the local availability replica for availability group '%.*ls' to complete post-online work. The operation encounte…
- 41195 — Availability group '%.*ls' failed to process the WSFC lease-renewal command. The local availability replica lease is no longer valid to process the le…
- 41196 — Failed to create availability group '%.*ls', because a Windows Server Failover Cluster (WSFC) group with the specified name already exists. An attempt…
- 41197 — The FAILOVER_MODE option has not been specified for the replica '%.*ls'. Reenter the command, specifying a failover mode for the replica.
- 41198 — The AVAILABILITY_MODE option has not been specified for the replica '%.*ls'. Reenter the command, specifying an availability mode for the replica.
- 41199 — The specified command is invalid because the Always On Availability Groups %ls feature is not supported by this edition of SQL Server. For information…
- 41201 — The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support remote data sources.
- 41202 — The source table '%.*ls' specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function doesn't have a fu…
- 41203 — The column '%.*ls' specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function is not full-text indexe…
- 41204 — The source_key parameter is required in the SEMANTICSIMILARITYTABLE function.
- 41205 — Error %d occurred during semantic index population for table or indexed view '%.*ls' (table or indexed view ID %d, database ID %d, document ID %d)
- 41206 — An ALTER FULLTEXT INDEX statement cannot remove the 'STATISTICAL_SEMANTICS' option from the last column in the index that has the option set when a "W…
- 41207 — A locale ID that is not supported was specified for a column with 'STATISTICAL_SEMANTICS'. Please verify that the locale ID is correct and that the co…
- 41208 — Warning: The population for table or indexed view '%ls' (table or indexed view ID '%d', database ID '%d') encountered a document with full-text key va…
- 41209 — A semantic language statistics database is not registered. Full-text indexes using 'STATISTICAL_SEMANTICS' cannot be created or populated.
- 41210 — The semantic language statistics database is not accessible or not valid. Full-text indexes using 'STATISTICAL_SEMANTICS' cannot be created or populat…
- 41211 — A semantic language statistics database is already registered.
- 41212 — No semantic language statistics database is registered.
- 41213 — The database '%.*ls' does not exist or the database format is not valid. Provide a valid semantic language statistics database name.
- 41214 — An error occurred while trying to register the semantic language statistics database.
- 41215 — The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support update or insert.
- 41216 — The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support common table expressions.
- 41300 — The current transaction cannot be committed and cannot support read or write operations. Roll back the transaction.
- 41301 — A transaction dependency failure occurred, and the current transaction can no longer commit. Please retry the transaction.
- 41302 — The current transaction attempted to update a record that has been updated since this transaction started. The transaction was aborted.
- 41303 — The bucket count for a hash index must be a positive integer not exceeding %d.
- 41304 — The current value of option '%.*ls' for table '%.*ls', index '%.*ls' is %d.
- 41305 — The current transaction failed to commit due to a repeatable read validation failure.
- 41306 — The nesting limit of %d for conditional blocks and exception blocks, for natively compiled modules, has been exceeded. Please simplify the module.
- 41307 — Warning: The row size limit of %d bytes for memory optimized tables has been exceeded and will not work on subscribers running SQL Server 2014 or earl…
- 41308 — The database ID %d already exists.
- 41309 — Unable to load the compiled DLL for database ID %d.
- 41310 — A file with an invalid format was detected. Check the SQL Server error log for more details.
- 41311 — File error during C code generation. The error code was %d.
- 41312 — Unable to call into the C compiler. GetLastError = %d.
- 41313 — The C compiler encountered a failure. The exit code was %d.
- 41314 — Conversion of default value for parameter '%.*ls' failed. Unable to create stored procedure '%.*ls'.
- 41315 — Checkpoint operation failed in database '%.*ls'.
- 41316 — Restore operation failed for database '%.*ls' with internal error code '0x%08lx'.
- 41317 — A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases model and…
- 41318 — Memory optimized tables and natively compiled modules cannot be accessed from within SQLCLR stored procedures.
- 41319 — A maximum of %d predicates are allowed in the WHERE clauses of queries in natively compiled modules.
- 41320 — EXECUTE AS clause is required, and EXECUTE AS CALLER is not supported, with natively compiled modules.
- 41321 — The memory optimized table '%.*ls' with DURABILITY=SCHEMA_AND_DATA must have a primary key.
- 41322 — MAT/PIT export/import encountered a failure for memory optimized table or natively compiled module with object ID %d in database ID %d. The error code…
- 41323 — The table type '%ls' is not a memory optimized table type and cannot be used in a natively compiled module.
- 41324 — The memory optimized table variable '%.*ls' cannot be used in a batch with a 'USE' statement.
- 41325 — The current transaction failed to commit due to a serializable validation failure.
- 41326 — Memory optimized tables cannot be created in system databases.
- 41327 — The memory optimized table '%.*ls' must have at least one index or a primary key.
- 41328 — A floating point operation has overflowed.
- 41329 — Unsupported operation following a transaction dependency failure. Parameters and variables cannot be accessed in the CATCH block and the CATCH block m…
- 41330 — Create database operation failed for database '%.*ls'.
- 41331 — The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. Roll back the transaction…
- 41332 — Memory optimized tables and natively compiled modules cannot be accessed or created when the session TRANSACTION ISOLATION LEVEL is set to SNAPSHOT.
- 41333 — The following transactions must access memory optimized tables and natively compiled modules under snapshot isolation: RepeatableRead transactions, Se…
- 41334 — The code generation directory cannot be created or set up correctly.
- 41335 — Modifying the collation of a database is not allowed when the database contains memory optimized tables or natively compiled modules.
- 41336 — Unable to clean up all files that are needed for compilation.
- 41337 — Cannot create %S_MSG. To create %S_MSG, the database must have a MEMORY_OPTIMIZED_FILEGROUP that is online and has at least one container.
- 41338 — An invalid version of a data file was detected. Check the SQL Server error log for more details.
- 41339 — The table '%.*ls' has been created or altered after the start of the current transaction. The transaction was aborted. Please retry the transaction.
- 41340 — The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated.
- 41341 — Table '%.*ls' is not yet available on the secondary replica.
- 41342 — The model of the processor on the system does not support creating %.*ls. This error typically occurs with older processors. See SQL Server Books Onli…
- 41343 — In-Memory OLTP hot switch to primary replica for database '%.*ls' failed.
- 41344 — RESTORE DATABASE WITH PARTIAL requires the MEMORY_OPTIMIZED_DATA filegroup if the backup contains a MEMORY_OPTIMIZED_DATA filegroup.
- 41345 — The key size limit of %d bytes for nonclustered indexes on memory optimized tables has been exceeded. Please simplify the index definition.
- 41346 — CREATE and UPDATE STATISTICS for memory optimized tables do not support the WHERE clause.
- 41347 — A BACKUP or RESTORE DATABASE statement that includes the primary filegroup must include the MEMORY_OPTIMIZED_DATA filegroup, and vice versa.
- 41348 — MEMORY_OPTIMIZED_DATA filegroups cannot be used with the FILESTREAM_ON clause. Specify a FILESTREAM filegroup.
- 41349 — Warning: Encryption was enabled for a database that contains one or more memory optimized tables with durability SCHEMA_AND_DATA. The data in these me…
- 41350 — Warning: A memory optimized table with durability SCHEMA_AND_DATA was created in a database that is enabled for encryption. The data in the memory opt…
- 41351 — An error occurred while processing the log. The log version is unsupported.
- 41352 — The operation on database ID %d cannot complete because the database is in use.
- 41353 — The operation on database ID %d cannot complete because the database is being dropped or being taken offline.
- 41354 — The XTP background checkpoint thread encountered an unrecoverable error ('%ls') for database '%.*ls'. The checkpoint process is terminating so that th…
- 41355 — An XTP checkpoint operation encountered an error ('%ls') while processing log record ID %S_LSN for database '%.*ls'. Checkpoint processing has termina…
- 41356 — Filegroups with MEMORY_OPTIMIZED_DATA can only be created in 64-bit installations of SQL Server.
- 41357 — Tables with MEMORY_OPTIMIZED=ON can only be created in 64-bit installations of SQL Server.
- 41358 — Stored procedures with NATIVE_COMPILATION can only be created in 64-bit installations of SQL Server.
- 41359 — A query that accesses memory optimized tables using the READ COMMITTED isolation level, cannot access disk based tables when the database option READ_…
- 41360 — Default MEMORY_OPTIMIZED_DATA filegroup is not available in database '%.*ls'.
- 41361 — The READ_ONLY property of a MEMORY_OPTIMIZED_DATA filegroup cannot be modified.
- 41362 — FILESTREAM container '%.*ls' cannot be added. Either the server is out of memory or the container path is too long.
- 41363 — Only the owner of database '%.*ls' or users with valid permission can execute the stored procedure '%.*ls'.
- 41364 — Stored procedure '%.*ls' can only be executed on a database that has an online MEMORY_OPTIMIZED_DATA filegroup.
- 41365 — Merge request for transaction range [%ld, %ld] on database '%.*ls' was not scheduled. The checkpoint files represented by the range either cannot be m…
- 41366 — Merge operation failed because the requested transaction id range is invalid.
- 41367 — Failed to complete merge operation for transaction range [%ld, %ld] for database '%.*ls'. Error was 0x%08x.
- 41368 — Accessing memory optimized tables using the READ COMMITTED isolation level is supported only for autocommit transactions. It is not supported for expl…
- 41369 — Merge operations cannot be requested on a secondary replica.
- 41370 — Resource pool '%.*ls' does not exist or resource governor has not been reconfigured.
- 41371 — Binding to a resource pool is not supported for system database '%.*ls'. This operation can only be performed on a user database.
- 41372 — Database '%.*ls' is currently bound to a resource pool. A database must be unbound before creating a new binding.
- 41373 — Database '%.*ls' cannot be explicitly bound to the resource pool '%.*ls'. A database can only be bound to a user resource pool.
- 41374 — Database '%.*ls' does not have a binding to a resource pool.
- 41375 — A binding has been created. Take database '%.*ls' offline and then bring it back online to begin using resource pool '%.*ls'.
- 41376 — Only members of the fixed sysadmin role can execute the stored procedure '%ls'.
- 41377 — The natively compiled module with database ID %ld and object ID %ld has not been executed. Query execution statistics collection can only be enabled i…
- 41378 — Both @database_id and @xtp_object_id should be specified to enable or retrieve status of query level statistics collection for a procedure.
- 41379 — Restore operation failed for database '%.*ls' due to insufficient memory in the resource pool '%ls'. Close other applications to increase the availabl…
- 41380 — Databases with a MEMORY_OPTIMIZED_DATA filegroup are only supported in 64-bit editions of SQL Server.
- 41381 — The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details …
- 41382 — Failure adding a container to a MEMORY_OPTIMIZED_DATA filegroup. Possible causes include the server being out of memory and the container path being t…
- 41383 — An internal error occurred while running the DMV query. This was likely caused by concurrent DDL operations. Please retry the query.
- 41384 — Database '%.*ls' has exceeded the maximum number of XTP checkpoint files, and can no longer support write operations in durable memory-optimized table…
- 41385 — A memory-optimized table cannot be enabled for Change Data Capture (CDC).
- 41386 — Filegroups with MEMORY_OPTIMIZED_DATA, memory-optimized tables and natively compiled modules are not supported when lightweight pooling is enabled. Di…
- 41387 — Disallowing page allocations for database '%.*ls' due to insufficient memory in the resource pool '%ls'. See ' http://go.microsoft.com/fwlink/?LinkId=…
- 41388 — An upgrade operation failed for database '%.*ls'. Check the error log for additional details.
- 41389 — Failed to create a backup file collection snapshot necessary for backup of database '%.*ls'. Check the error log for additional details.
- 41390 — Failed to get checkpoint file information necessary for backup of database '%.*ls'. Check the error log for additional details.
- 41391 — Backup of database '%.*ls' detected a missing MEMORY_OPTIMIZED_DATA file with ID '%.*ls'.
- 41392 — Cannot ALTER a natively compiled module into a non-native module. Include WITH NATIVE_COMPILATION or drop and recreate the module.
- 41393 — Cannot ALTER a non-native module into a natively compiled module. Omit WITH NATIVE_COMPILATION or drop and recreate the module.
- 41394 — TEXTSIZE must be a number between -1 and 2147483647.
- 41395 — Rebuilding the log file is not supported for databases containing memory-optimized tables.
- 41396 — The sort operation exceeded the buffer limit. The stored procedure execution was aborted. Consult SQL Server Books Online for more information.
- 41397 — The TOP operator can return a maximum of %d sorted rows. %d was requested. Reduce the number of rows selected or simplify the query.
- 41398 — The TOP operator can return a maximum of %d rows; %d was requested.
- 41399 — The sort operation is too complex. Consult SQL Server Books Online for more information.
- 41401 — WSFC cluster service is offline.
- 41402 — The WSFC cluster is offline, and this availability group is not available. This issue can be caused by a cluster service issue or by the loss of quoru…
- 41403 — Availability group is offline.
- 41404 — The availability group is offline, and is unavailable. This issue can be caused by a failure in the server instance that hosts the primary replica or …
- 41405 — Availability group is not ready for automatic failover.
- 41406 — The availability group is not ready for automatic failover. The primary replica and a secondary replica are configured for automatic failover, however…
- 41407 — Some availability replicas are not synchronizing data.
- 41408 — In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the primary re…
- 41409 — Some synchronous replicas are not synchronized.
- 41410 — In this availability group, at least one synchronous replica is not currently synchronized. The replica synchronization state could be either SYNCHONI…
- 41411 — Some availability replicas do not have a healthy role.