SQL Server Error Messages 35001 to 40000

In this post, we’ll list out the SQL Server Error Messages from the error codes 35001 to 40000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 35001 to 40000

ErrorCodeSeverityErrorMessage
3500116Parent Server Group does not exist.
3500216Server type and parent Server Group type are not the same
3500316Cannot move node to one of its children
3500416Could not find server group
3500516An invalid value NULL was passed in for @server_group_id.
3500616An invalid value NULL was passed in for @server_id.
3500716Could not find shared registered server.
3500816Cannot delete system shared server groups.
3500916An invalid value NULL was passed in for @server_type.
3501016An invalid value %d was passed in for parameter @server_type.
3501116The @server_name parameter cannot be a relative name.
3501216You cannot add a shared registered server with the same name as the Configuration Server.
3510016Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647.
3510116One of the SET options FMTONLY or NOEXEC was changes from ON to OFF in a TRY…CATCH block.
3520016Failed to add database ‘%.*ls’ to availability group ‘%.*ls’. The specified availability group is created with basic functionality and supports %d database.
3520110A connection timeout has occurred while attempting to establish a connection to availability replica ‘%ls’ with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
3520210A connection for availability group ‘%ls’ from availability replica ‘%ls’ with id  [%ls] to ‘%ls’ with id [%ls] has been successfully established.  This is an informational message only. No user action is required.
3520316Unable to establish a connection between instance ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] due to a transport version mismatch.
3520410The connection between server instances ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] has been disabled because the database mirroring endpoint was either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT Transact-SQL statement with STATE = STARTED.
3520516Could not start the Always On Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL Server error log and the Windows error log for additional error messages. If a low memory condition exists, investigate and correct its cause.
3520610A connection timeout has occurred on a previously established connection to availability replica ‘%ls’ with id [%ls].  Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
3520716Connection attempt on availability group id ‘%ls’ from replica id ‘%ls’ to replica id ‘%ls’ failed because of error %d, severity %d, state %d.
3520816Availability-group DDL operations are permitted only when you are using the master database.  Run the USE MASTER command, and retry your availability-group DDL command.
3520916The %ls operation failed for availability replica ‘%.*ls’, because the backup priority value is outside the valid range. The valid range is between %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation.
3521016Failed to modify options for availability replica ‘%.*ls’ in availability group ‘%.*ls’. The specified availability group does not contain an availability replica with specified name. Verify that availability group name and availability replica name are correct, then retry the operation.
3521116The %ls operation is not allowed.  The operation attempted to change the configuration of availability replica ‘%.*ls’ to the asynchronous-commit availability mode with automatic failover, which is an invalid configuration.  Either change the failover mode to manual or the availability mode to synchronous commit, and retry the operation.
3521216The %ls operation is not allowed by the current availability-group configuration.  This operation would exceed the maximum number of %d synchronous-commit availability replicas in availability group ‘%.*ls’.  Change one of the existing synchronous-commit replicas to the asynchronous-commit availability mode, and retry the operation.
3521316The %ls operation is not allowed by the current availability-group configuration.  This operation would exceed the maximum number of %d automatic failover targets in availability group ‘%.*ls’.  Change one of the existing synchronous-commit replicas to the manual failover mode, and retry the operation.
3521416The %ls operation failed for availability replica ‘%.*ls’.  The minimum value for session timeout is %d.  Retry the operation specifying a valid session-timeout value.
3521516The %ls operation is not allowed on availability replica ‘%.*ls’, because automatic failover mode is an invalid configuration on a SQL Server Failover Cluster Instance.  Retry the operation by specifying manual failover mode.
3521616An error occurred while adding or removing a log truncation holdup to build secondary replica from primary availability database ‘%.*ls’.  Primary database is temporarily offline due to restart or other transient condition.  Retry the operation.
3521716 The thread pool for Always On Availability Groups was unable to start a new worker thread because there are not enough available worker threads.  This may degrade Always On Availability Groups performance.  Use the “max worker threads” configuration option to increase number of allowable threads.
3521816An error occurred while trying to set the initial Backup LSN of database ‘%.*ls’.  Primary database is temporarily offline due to restart or other transient condition.  Retry the operation.
3522016Could not process the operation. Always On Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster node is not online. If the computer is a cluster node, wait for it to join the cluster. If the computer is not a cluster node, add the computer to a WSFC cluster. Then, retry the operation.
3522116Could not process the operation. Always On Availability Groups replica manager is disabled on this instance of SQL Server. Enable Always On Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.
3522216Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.
3522316Cannot add %d availability replica(s) to availability group ‘%.*ls’.  The availability group already contains %d replica(s), and the maximum number of replicas supported in an availability group is %d.
3522416Could not process the operation.  Always On Availability Groups failed to load the required Windows Server Failover Clustering (WSFC) library. Verify that the computer is a node in a WSFC cluster.  You will need to restart the SQL Server instance to reload the required library functions.
3522516Could not process the operation. The  instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support Always On Availability Groups.  Reinstall SQL Server in the native 64-bit edition, and re-enable Always On Availability Groups. Then, restart the SQL Server service, and retry the operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.
3522616Could not process the operation.  Always On Availability Groups has not started because the instance of SQL Server is not running as a service. Restart the server instance as a service, and retry the operation.
3522816The attempt to set the failure condition level for availability group ‘%.*ls’ failed. The specified level value is out of the valid range [%u, %u]. Reenter the command specifying a valid failure condition level value.
3522916The attempt to set the health check timeout value for availability group ‘%.*ls’ failed. The specified timeout value is less than %u milliseconds. Reenter the command specifying a valid health check timeout value.
3523016The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name.
3523116The specified server instance name, ‘%ls’, is invalid. Reenter the command specifying a valid instance name.
3523216The specified endpoint URL ‘%.*ls’ is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online.
3523316Cannot create an availability group containing %d availability replica(s). The maximum number of availability replicas in an availability group %ls is %d.  Reenter your CREATE AVAILABILITY GROUP command specifying fewer availability replicas.
3523416Database name ‘%ls’ was specified more than once. Reenter the command, specifying each database name only once.
3523516The system name ‘%ls’ was specified more than once in the REPLICA ON clause of this command. Reenter the command, specifying a different instance of SQL Server for each replica.
3523615The endpoint URL was not specified for the availability replica hosted by server instance ‘%.*ls’.  Reenter the command, specifying the endpoint URL of this instance of SQL Server.
3523716None of the specified replicas for availability group %.*ls maps to the instance of SQL Server to which you are connected. Reenter the command, specifying this server instance to host one of the replicas. This replica will be the initial primary replica.
3523816Database ‘%.*ls’ cannot be added to availability group ‘%.*ls’.  The database does not exist on this SQL Server instance.  Verify that the database name is correct, then retry the operation.
3523916The ALTER DATABASE <database-name> SET HADR SUSPEND (or SET HADR RESUME) statement failed on database ‘%.*ls’ of availability group ‘%.*ls”. Either the availability group does not contain the specified database, or the database has not joined the availability group, or the database has not yet started. Reenter the command after the database is online and has joined the availability group.
3524016Database ‘%.*ls’ cannot be joined to or unjoined from availability group ‘%.*ls’. This operation is not supported on the primary replica of the availability group.
3524216Cannot complete this ALTER DATABASE <database-name> SET HADR operation on database ‘%.*ls’. The database is not joined to an availability group. After the database has joined the availability group, retry the command.
3524316Failed to set resource property ‘%.*ls’ for availability group ‘%.*ls’.  The operation encountered SQL Server error %d.  When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP command later.
3524416Database ‘%.*ls’ cannot be added to availability group ‘%.*ls’.  The database is currently joined to another availability group.  Verify that the database name is correct and that the database is not joined to an availability group, then retry the operation.
3524616Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file ‘%ls’ could not be located (Windows System Error %d). Verify that the specified server instance exists. If it exists, the DLL file might be missing from the server instance.
3524716Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library (DLL) file ‘%ls’ could not be loaded (Windows System Error %d).
3524816The %ls operation is not allowed by the current availability-group configuration.  The required_synchronized_secondaries_to_commit %d is greater than the %d possible secondary synchronous-commit availability replicas in availability group ‘%.*ls’.  Change one of the existing asynchronous-commit replicas to the synchronous-commit availability mode, and retry the operation.
3524916An attempt to add or join a system database, ‘%.*ls’, to an availability group failed. Specify only user databases for this operation.
3525016The connection to the primary replica is not active.  The command cannot be processed.
3525116This command can be run only on the primary replica. Connect to the primary replica, and retry the command.
3525216The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command.
3525316Database “%.*ls” is not in the correct state to become the primary database.  The log must be restored from the previous primary replica to bring the database out of the reinitializing state.
3525416An error occurred while accessing the availability group metadata. Remove this database or replica from the availability group, and reconfigure the availability group to add the database or replica again. For more information, see the ALTER AVAILABILITY GROUP Transact-SQL statement in SQL Server Books Online.
3525516An attempt to start database ‘%.*ls’ failed because the database is already started and online.
3525616The session timeout value was exceeded while waiting for a response from the other availability replica in the session. That replica or the network might be down, or the command might be misconfigured. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters.
3525716 Always On Availability Groups Send Error (Error code 0x%X, “NOT OK”) was returned when sending a message for database ID %d. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters.
3525816 Error in the hadron simulator.
3525916 Database ‘%.*ls’ is already participating in a different availability group.
3526016 During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group database ID %ls.  Recovery was terminated. The most likely cause of this error is that the availability group manager is not running, but the cause could be a metadata error. Ensure that the availability group manager and the WSFC cluster are started, and retry the recovery operation.
3526116 Attempt to perform an Always On Availability Groups operation on a system database, ‘%ls’, failed. System databases are not supported by Always On Availability Groups.
3526210Skipping the default startup of database ‘%.*ls’ because the database belongs to an availability group (Group ID:  %d). The database will be started by the availability group. This is an informational message only. No user action is required.
3526316During the undo phase, a function call (%ls) to the primary replica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Server error log for the primary replica. If an error occurred on the primary database, you might need to suspend the secondary database, fix the issue on the primary database, and then resume the database.
3526410Always On Availability Groups data movement for database ‘%.*ls’ has been suspended for the following reason: “%S_MSG” (Source ID %d; Source string: ‘%.*ls’). To resume data movement on the database, you will need to resume the database manually. For information about how to resume an availability database, see SQL Server Books Online.
3526510Always On Availability Groups data movement for database ‘%.*ls’ has been resumed. This is an informational message only. No user action is required.
3526610Always On Availability Groups connection with %S_MSG database established for %S_MSG database ‘%.*ls’ on the availability replica ‘%.*ls’ with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required.
3526710Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database ‘%.*ls’ on the availability replica ‘%.*ls’ with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required.
3526816Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORING state. To complete recovery and bring the database online, use current log backups from the primary database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups.
3526921Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will be marked SUSPECT. To return the database to a consistent state, restore it from a clean database backup followed by all subsequent log backups.
3527010Received a corrupt FileStream transport message. The ‘%ls’ message section is invalid.
3527116The availability database %ls in availailability group %ls failed to complete a reconfiguration. Refer to the error code for more details. If this condition persists, contact the system administrator.
3527216Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure.
3527310Bypassing recovery for database ‘%ls’ because it is marked as an inaccessible availability database. The session with the primary replica was interrupted while reverting the database to the common recovery point. Either the WSFC node lacks quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, you need to determine what has changed in the session configuration and undo the change.
3527410Recovery for availability database ‘%ls’ is pending until the secondary replica receives additional transaction log from the primary before it complete and come online. Ensure that the server instance that hosts the primary replica is running.
3527516A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the ‘%.*ls’ database in a potentially damaged state. The database cannot be joined while in this state. Restore the database, and retry the join operation.
3527617Failed to allocate and schedule an Always On Availability Groups task for database ‘%ls’. Manual intervention may be required to resume synchronization of the database. If the problem persists, you might need to restart the local instance of SQL Server.
3527716Automatic failover is not supported for distributed availability group replica.
3527816Availability database ‘%.*ls’, which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required.
3527916The attempt to join database ‘%.*ls’ to the availability group was rejected by the primary database with error ‘%d’. For more information, see the SQL Server error log for the primary replica.
3528016Database ‘%.*ls’ cannot be added to availability group ‘%.*ls’.  The database is already joined to the specified availability group.  Verify that the database name is correct and that the database is not joined to an availability group, then retry the operation.
3528116Database ‘%.*ls’ cannot be removed from availability group ‘%.*ls’.  The database is not joined to the specified availability group.  Verify that the database name and the availability group name are correct, then retry the operation.
3528216Availability replica ‘%.*ls’ cannot be added to availability group ‘%.*ls’.  The availability group already contains an availability replica with the specified name.  Verify that the availability replica name and the availability group name are correct, then retry the operation.
3528316Availability replica ‘%.*ls’ cannot be removed from availability group ‘%.*ls’.  The availability group does not contain an availability replica with the specified name.  Verify that the availability replica name is correct, then retry the operation.
3528416Availability replica ‘%.*ls’ cannot be removed from availability group ‘%.*ls’, because this replica is on the local instance of SQL Server.  If the local availability replica is a secondary replica, connect to the server instance that is currently hosting the primary replica, and re-run the command.
3528510The recovery LSN %S_LSN was identified for the database with ID %d. This is an informational message only. No user action is required.
3528616Using the recovery LSN %S_LSN stored in the metadata for the database with ID %d. This is an informational message only. No user action is required.
3528716Always On Availability Groups transport for availability database “%.*ls” failed to decompress the log block whose LSN is %S_LSN.  This error can be caused by a corrupt network packet or a compression version mismatch.  The database replica has been put into the SUSPENDED state.  Resume the availability database.  If the error keeps reoccurring, investigate the root cause.
3528816Always On Availability Groups log apply for availability database “%.*ls” has received an out-of-order log block.  The expected LSN was %S_LSN.  The received LSN was %S_LSN.  The database replica has been put into the SUSPENDED state.  Resume the availability database.  If the error reoccurs, contact Customer Support Services.
3528916Failed to send request for file ‘%.*ls’ to the ‘%.*ls’ primary database for the local secondary database. Resuming the database will be retried automatically.
3529016Failed to wait for completion of file requests from the ‘%.*ls’ primary database for the local secondary database. Resuming the database will be retried automatically.
3529110Failed to acquire exclusive access to the extended recovery fork stack (error %d). If the problem persists, you might need to restart the instance of SQL Server.
3529216An internal error occurred when performing an operation on extended recovery forks. This is an informational message only. No user action is required.
3529316Error in retrieving extended recovery forks from the primary replica. The extended-recovery-fork stack changed while being retrieved by the secondary replica. Retry the operation.
3529416Log backup for database “%.*ls” on a secondary replica failed because a synchronization point could not be established on the primary database. Either locks could not be acquired on the primary database or the database is not operating as part of the availability replica. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation.
3529516Log backup for database “%.*ls” on a secondary replica failed because the last backup LSN (0x%ls) from the primary database is greater than the current local redo LSN (0x%ls). No log records need to be backed up at this time. Retry the log-backup operation later.
3529616 Log backup for database “%.*ls” on secondary replica failed because the new backup information could not be committed on primary database. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation.
3529710Log backup for database “%.*ls” on secondary replica created backup files successfully but could not ensure that a backup point has been committed on the primary.  This is an informational message only.  Preserve this log backup along with the other log backups of this database.
3529810The backup on the secondary database “%.*ls” was terminated, but a terminate backup message could not be sent to the primary replica. This is an informational message only. The primary replica should detect this error and clean up its backup history accordingly.
3529910Nonqualified transactions are being rolled back in database %.*ls for an Always On Availability Groups state change. Estimated rollback completion: %d%%. This is an informational message only. No user action is required.
3530115The statement failed because a columnstore index cannot be unique. Create the columnstore index without the UNIQUE keyword or create a unique index without the COLUMNSTORE keyword.
3530215The statement failed because specifying sort order (ASC or DESC) is not allowed when creating a columnstore index. Create the columnstore index without specifying a sort order.
3530315The statement failed because a nonclustered index cannot be created on a table that has a clustered columnstore index. Consider replacing the clustered columnstore index with a nonclustered columnstore index.
3530415The statement failed because a clustered columnstore index cannot be created on a table that has a nonclustered index. Consider dropping all nonclustered indexes and trying again.
3530515The statement failed because a clustered columnstore index cannot be created on a view. Consider creating a nonclustered columnstore index on the view, creating a clustered columnstore index on the base table or creating an index without the COLUMNSTORE keyword on the view.
3530615The statement failed because a columnstore index cannot be specified using INDEX specification at the column level.
3530715The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column. Columnstore index cannot include a computed column implicitly or explicitly.
3530815The statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without the predicate filter.
3530915The statement failed because a columnstore index cannot be created on a sparse column. Consider creating a nonclustered columnstore index on a subset of columns that does not include any sparse columns.
3531015The statement failed because columnstore indexes are not allowed on table types and table variables. Remove the column store index specification from the table type or table variable declaration.
3531115The statement failed because a columnstore index cannot have included columns.   Create the columnstore index on the desired columns without specifying any included columns.
3531215The statement failed because a columnstore index cannot be created on a column with filestream data. Consider creating a nonclustered columnstore index on a subset of columns that does not include any columns with filestream data.
3531315The statement failed because specifying FILESTREAM_ON is not allowed when creating a columnstore index. Consider creating a columnstore index on columns without filestream data and omit the FILESTREAM_ON specification.
3531415The statement failed because a columnstore index cannot be created on a column set. Consider creating a nonclustered columnstore index on a subset of columns in the table that does not contain a column set or any sparse columns.
3531515The statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
3531615The statement failed because a columnstore index must be partition-aligned with the base table. Create the columnstore index using the same partition function and same (or equivalent) partition scheme as the base table. If the base table is not partitioned, create a nonpartitioned columnstore index.
3531715The statement failed because specifying %S_MSG is not allowed when creating a columnstore index. Consider creating a columnstore index without specifying %S_MSG.
3531815The statement failed because the %S_MSG option is not allowed when creating a columnstore index. Create the columnstore index without specifying the %S_MSG option.
3531915The table option DATA_COMPRESSION is not allowed when a table specifies a clustered column store index.
3532015Column store indexes are not allowed on tables for which the durability option SCHEMA_ONLY is specified.
3532116Table ‘%.*ls’ uses a clustered columnstore index. Columnstore indexes are not supported in this service tier of the database. See Books Online for more details on feature support in different service tiers of Windows Azure SQL Database.
3532216The statement failed because a nonclustered index and the underlying clustered columnstore index must be partition-aligned. Consider creating the nonclustered index using the same partition function and same (or equivalent) partition scheme as the clustered columnstore index.
3532316The statement failed because adding multiple generated value type columns (such as identity and uniqueidentifier types) at once is not supported for columnstore index. Consider adding the generated columns seperately.
3532415The statement failed because specifying SORT_IN_TEMPDB is not allowed when creating a columnstore index without ORDER. Consider creating a columnstore index without specifying SORT_IN_TEMPDB, or use it with ORDER clause.
3532515The statement failed because the definition of a column belonging to clustered columnstore index cannot be changed. Consider dropping the columnstore index, altering the column, then creating a new columnstore index.
3532615The statement failed because a nonclustered columnstore index cannot be reorganized. Reorganization of a nonclustered columnstore index is not necessary.
3532715ALTER INDEX REBUILD statement failed because specifying %S_MSG is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying %S_MSG.
3532815ALTER INDEX REBUILD statement failed because the %S_MSG option is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying the %S_MSG option.
3532915The statement failed because specifying ORDER is not allowed when creating the rowstore index ‘%.*ls’ on table ‘%.*ls’. Consider creating the rowstore index without specifying ORDER.
3533016%S_MSG statement failed because data cannot be updated in a table that has a nonclustered columnstore index. Consider disabling the columnstore index before issuing the %S_MSG statement, and then rebuilding the columnstore index after %S_MSG has completed.
3533116Cannot use duplicate column names in the ORDER column list. Column name ‘%.*ls’ appears more than once.
3533216Cannot ORDER on more than %d columns.
3533415DBCC DBREINDEX failed because specifying FILLFACTOR is not allowed when creating or rebuilding a columnstore index. Rebuild the columnstore index without specifying FILLFACTOR.
3533515The statement failed because specifying a key list is not allowed when creating a clustered columnstore index. Create the clustered columnstore index without specifying a key list.
3533615The statement failed because specifying key list is missing when creating an index. Create the index with specifying key list .
3533716UPDATE STATISTICS failed because statistics cannot be updated on a columnstore index.  UPDATE STATISTICS is valid only when used with the STATS_STREAM option.
3533816Clustered columnstore index is not supported.
3533916Multiple columnstore indexes are not supported.
3534016LOB columns are disabled in columnstore.
3534116The statement failed. A columnstore index cannot include a decimal or numeric data type with a precision greater than 18. Reduce the precision or omit column ‘%.*ls’.
3534215The statement failed because specifying ORDER is not a valid option for creating the non-clustered columnstore index ‘%.*ls’ on table ‘%.*ls’. Consider creating the non-clustered columnstore index without specifying ORDER, or create a clustered columnstore index.
3534315The statement failed. Column ‘%.*ls’ has a data type that cannot participate in a columnstore index.
3534416MERGE clause of ALTER PARTITION statement failed because two nonempty partitions containing a columnstore index cannot be merged. Consider an ALTER TABLE SWITCH operation from one of the nonempty partitions on the source table to a temporary staging table and then re-attempt the ALTER PARTITION MERGE operation. Once completed, use ALTER TABLE SWITCH to move the staging table partition back to the original source table.
3534516MERGE clause of ALTER PARTITION statement failed because two partitions on different filegroups cannot be merged if either partition contains columnstore index data. Consider dropping the columnstore index before issuing the ALTER PARTITION statement, then rebuilding the columnstore index after ALTER PARTITION is complete.
3534616SPLIT clause of ALTER PARTITION statement failed because the partition is not empty.  Only empty partitions can be split in when a columnstore index exists on the table. Consider an ALTER TABLE SWITCH operation from one of the nonempty partitions on the source table to a temporary staging table and then re-attempt the ALTER PARTITION SPLIT operation. Once completed, use ALTER TABLE SWITCH to move the staging table partition back to the original source table.
3534716The stored procedure ‘sp_tableoption’ failed because a table with a columnstore index cannot be altered to use vardecimal storage format. Consider dropping the columnstore index.
3534816The statement failed because table ‘%.*ls’ uses vardecimal storage format. A columnstore index cannot be created on a table using vardecimal storage. Consider rebuilding the table without vardecimal storage.
3534916TRUNCATE TABLE statement failed because table ‘%.*ls’ has a columnstore index on it. A table with a columnstore index cannot be truncated. Consider dropping the columnstore index then truncating the table.
3535016The statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table. Consider dropping the columnstore index before creating a new clustered index.
3535116DROP INDEX statement failed because a columnstore index on a partitioned table must be partition-aligned with the base table (heap). Consider dropping the columnstore index before dropping a clustered index.
3535216%S_MSG statement failed because the operation cannot be performed online on a table with a columnstore index. Perform the operation without specifying the ONLINE option or drop (or disable) the columnstore index before performing the operation using the ONLINE option.
3535316%s cannot be enabled on a table with a clustered columnstore index.  Consider dropping clustered columnstore index ‘%s’ on table ‘%s’.
3535416The statement failed because a clustered columnstore index cannot be created on a table enabled for %S_MSG. Consider disabling %S_MSG and then creating the clustered columnstore index.
3535516The statement failed. Column ‘%.*ls’ is either a primary key or a partitioning key that must be included, but a columnstore index cannot include a decimal or numeric data type with a precision greater than 18. Consider reducing the precision to 18.
3535616This operation is not supported on nonclustered columnstore indexes built in earlier versions of SQL Server. Consider rebuilding the index.
3535716The statement failed because a secondary dictionary reached the maximum size limit. Consider dropping the columnstore index, altering the column, then creating a new columnstore index.
3535816CREATE TRIGGER on table ‘%.*ls’ failed because you cannot create a trigger on a table with a clustered columnstore index. Consider enforcing the logic of the trigger in some other way, or if you must use a trigger, use a heap or B-tree index instead.
3535916The statement failed because a table with a clustered columnstore index cannot have triggers. Consider removing all triggers from the table and then creating the clustered columnstore index.
3536016Referential constraint ‘%.*ls’ cannot be created because the %S_MSG table ‘%.*ls’ has a clustered columnstore index.
3536116The statement failed. A clustered columnstore index cannot be created over referencing column ‘%.*ls’ on table ‘%.*ls’.
3536316The statement failed because clustered columnstore indexes are not supported in system databases.
3536416ALTER INDEX statement option COMPRESSION_DELAY can only be used with columnstore indexes.
3536522The compression block header at offset %ld is invalid.
3536622The columnstore blob Xpress header is invalid.
3536722The columnstore blob Xpress object header is invalid.
3536817Internal DDL Operation Error: The DDL encountered an unexpected error %d during execution (HRESULT = 0x%x).
3536916GETCHECKSUM can not be used for a table which has a clustered columnstore index.
3537016Cursors are not supported on a table which has a clustered columnstore index.
3537116SNAPSHOT isolation level is not supported on a table which has a clustered columnstore index.
3537216You cannot create more than one clustered index on %S_MSG ‘%.*ls’. Consider creating a new clustered index using ‘with (drop_existing = on)’ option.
3537316ALTER INDEX REORGANIZE statement failed on a clustered columnstore index with error %d. See previous error messages for more details.
3537416Columnstore archive decompression failed with error %d.
3537516ALTER INDEX REORGANIZE statement option COMPRESS_ALL_ROW_GROUPS can only be used with clustered columnstore indexes.
3537616Tuple mover stvf got passed invalid arguments
3537816Row groups stvf got passed invalid arguments
3537916Internal error occurred while flushing delete buffer database id %d, table id %d, index id %d, partition number %d. Additional messages in the SQL Server error log may provide more details.
3538016The non-clustered columnstore index ‘%.*ls’ on table ‘%.*ls’ cannot be reorganized due to an active snapshot transaction.
3538122The columnstore blob dictionary header is invalid.
3538216The specified COMPRESSION_DELAY option value %d is invalid. The valid range for disk-based table is between (0, 10080) minutes and for memory-optimized table is 0 or between (60, 10080) minutes.
3538316The use of user-defined functions is not allowed in default constraints when adding columns to a columnstore index.
3538416The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a lob column. Non clustered index with lob column as included column cannot co-exist with clustered columnstore index.
3538617Unable to allocate %I64d KB for columnstore compression because it exceeds the remaining memory from total allocated for current resource class and DWU. Please rerun query at a higher resource class, and also consider increasing DWU. See ‘https://aka.ms/sqldw_columnstore_memory’ for assistance.
3538717TEMPDB ran out of space during spilling. Verify that data is evenly distributed and/or rewrite the query to consume fewer rows. If the issue still persists, consider upgrading to a higher service level objective.
3538815The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a persisted computed column. Adding persisted computed columns to an existing clustered columnstore index is not supported.
3538915The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column of a LOB type. Columnstore indexes cannot include computed columns of LOB types.
3539016Computed columns in columnstore indexes are temporarily disabled. Please rewrite your query to exclude computed columns.
3539116Could not build or rebuild clustered columnstore index ‘%.*ls’ online, because the the table has secondary indexes. Please perform the operation offline, or remove the secondary indexes and try again.
3539215The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column. Nonclustered index with computed column as key or included column cannot be created on a table that has a clustered columnstore index.
3539316Columnstore tuple mover unit tests can’t be run under master database.
3539416Transaction %d reached %I64u log used bytes and %I64d reserved log bytes. In order to minimize log usage %d suboptimal rowgroups were created, which is not allowed since it compromises index quality. Please re-run query at a higher resource class, and also consider increasing DWU. See ‘https://aka.ms/sqldw_columnstore_memory’ for assistance.
3539516Transaction %d reached %I64u log used bytes and %I64d reserved log bytes. In order to minimize log usage, %d suboptimal rowgroups were created, which is not allowed since it compromises index quality. Please re-run the query with more memory (change your Resource Governor settings or upgrade to a higher SLO) or target fewer partitions in the load if your target table is partitioned.
3539617Effective DOP of %u is too high for columnstore compression on table id %d because each thread only has %I64d KB for compression. Please retry using the MAXDOP hint to use a lower DOP.
3539716%S_MSG statement failed because the operation cannot be performed resumably on a table with a columnstore index. Perform the operation without specifying the RESUMABLE option or drop (or disable) the columnstore index before performing the operation using the RESUMABLE option.
3539816Columnstore index operation failed. Please contact Microsoft customer support.
3540110ONLINE
3540210ALLOW_ROW_LOCKS
3540310ALLOW_PAGE_LOCKS
3540416sequence
3540510decryption
3540610creation
3540910Replication
3541010Change Tracking
3541110Change Data Capture
3541216CloudDB Async Transport
3541316CloudDB Async Transport Forwarder
3541510mirrored
3541710primary
3541810secondary
3541916feature
3542016operation
3542116statement
3542216index option
3542316table option
3542416operator
3542516value
3542616system column
3542716set option
3542816query hint
3542916transaction isolation level
3543016in-memory index
3543110SCHEDULER
3543210NUMANODE
3543316federation
3543416federation distribution
3543516system database
3543616federation member database
3543716non federation member database
3543816federation root database
3543910it is a system database.
3544010it acts as a distribution database
3544110an internal error occurred
3544210it is involved in a mirroring session. Turn off the mirroring session and try again
3544310it is not in SIMPLE recovery mode. Change the recovery model to SIMPLE and try again
3544410it is a database snapshot
3544510it is a not currently enabled
3544616clause
3544710Cluster Proxy
3544810partition
3544916signing algorithm
3545016table
3545116join hint
3545210Database unavailable
3545310it is a system database. Make sure to target a user database. If you want temporary clustered columnstore tables, consider creating a regular user database for them
3545410a transaction is currently active. Execute sp_db_enable_clustered_columnstores by itself
3545510an internal error occurred
3545610it is involved in a mirroring pair. Consider disabling mirroring, changing the setting, then re-establishing mirroring
3545710it is a database snapshot
3545810it is part of an Always On availability group. Consider removing the database from the availability group, changing the setting, and then adding the database back to the availability group
3545910it is a replication distribution database. Make sure to target a regular user database
3546010it is not using the SIMPLE recovery model. Consider temporarily changing to the simple recovery model, then downgrading, then switching back
3546110it contains one or more clustered columnstore indexes. Consider dropping these indexes or creating clustered B-tree indexes instead, and trying again
3546210referencing
3546310referenced
3546410columnstore indexes are not supported in the current SQL Server edition. See SQL Server Books Online for supported editions
3546517Unable to allocate the recovery thread
3546616Exception in the recovery thread
3546716Already linked to a partition host
3546816Partition DB marked as suspect
3546916Failed to get Partition DB attributes
3547016Partition Host
3547110Partition metadata not found
3547215memory optimized tables
3547315natively compiled modules
3547415indexes on memory optimized tables
3547515hash indexes
3547615transactions that access memory optimized tables or natively compiled modules
3547715databases that have a MEMORY_OPTIMIZED_DATA filegroup
3547816truncate
3547916start
3548016stop
3548115memory optimized table types
3548216clustered
3548316nonclustered
3548416BUCKET_COUNT
3548516security policy
3548615memory optimized tables that have a column store index
3548710Global Transactions
3548815natively compiled triggers
3548916Upgrade of Hekaton database
3549016memory optimized tables that have max length columns
3549116max length columns in natively compiled modules
3549216column definition
3549316enabled
3549416disabled
3549515memory optimized table
3549615natively compiled module
3549715module
3549816external data source
3549916OUTPUT clauses in natively compiled modules
3550115schemas that contain natively compiled modules
3550215change_tracking_hardened_cleanup_version()
3550315safe_cleanup_version()
3550416server encryption protector
3550515RESUMABLE
3550615MAX_DURATION
3550710Storage
3550810RESUME
3550910PAUSE
3551010ABORT
3551110ABORT
3551210allow_enclave_computations
3551310compute
3551410local computer
3551510current user
3551610query_capture_policy
3551710execution_count
3551810total_compile_cpu_time_ms
3551910total_execution_cpu_time_ms
3552010OPTIMIZE_FOR_SEQUENTIAL_KEY
3552110stale_capture_policy_threshold
3552210day
3600116%s ‘%s’ already exists in the database.
3600216instance_id already exists in the database.
3600316%s ‘%s’ already exists for the given DAC instance.
3600416DacInstance with the specified instance_id does not exist.
3600516Dac root – database %s does not exist.
3600616Dac Policy with the specified policy id already exists in the parts table.
3600716Dac Part the policy refers to, does not exist.
3600816Dac Policy refers to a non-existent Policy.
3600916%s ‘%s’ already exists in the Dac Parts.
3601016The caller must be a member of the dbcreator fixed server role to perform this action.
3601116The caller must be sysadmin or the creator of the history entry being updated.
3601210Unable to execute T-SQL within procedure due to SQL Server limitation.\nPlease execute following T-SQL in database ‘%s’ context after this procedure finishes:\n%s
3610116Process ID %d is not an active process ID.
3700116This operation is not allowed since there are dependent objects pending installation.
3700216Cannot find the database ‘%s’, because it does not exist or you do not have permission to access it.
3700316This operation is not allowed because a utility control point already exists on this instance of SQL Server.
3700416The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL Server ‘%s’.
3700516The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL Server ‘%s’.
3700616Cannot perform the operation because the specified instance of SQL Server is not enrolled in a SQL Server utility.
3700716An error occurred during upload to the SQL Server utility control point.
3700816The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role.
3700916The operation cannot continue. The specified instance of SQL Server is not a SQL Server utility control point.
3701016The operation cannot continue. The SQL Server utility control point has managed instances of SQL Server enrolled.
3710116Server ‘%.*ls’ does not contain elastic job account: ‘%.*ls’.
3710216Elastic job account ‘%.*ls’ does not contain the resource of type ‘%.*ls’ named ‘%.*ls’.
3710316Internal job account error occurred : ‘%.*ls’.
3710416A job account already exists for subscription ‘%.*ls’ for the selected region.
3710516The job account ‘%.*ls’ on server ‘%.*ls’ already exists.
3710616The database ‘%.*ls’ on server ‘%.*ls’ is in use by job account ‘%.*ls’. The database cannot be deleted or renamed while associated with a job account.
3710716The database ‘%.*ls’ on server ‘%.*ls’ has service level objective ‘%.*ls’ which is not supported for use as a job account database.
3710816A job account could not be linked to database ‘%.*ls’ on server ‘%.*ls’ because it is a geo-secondary database.
3710916Database ‘%ls’ on server ‘%ls’ is already linked to another job account.
3720116An instance pool could not be found with name ‘%.*ls’.
3720216An instance pool with name ‘%.*ls’ is busy with another ongoing operation.

37203 16 An instance pool with name ‘%.*ls’ is not empty.

37204 16 An instance pool with name ‘%.*ls’ does not have enough vCore capacity for given request.

37301 16 Internal enclave error. The enclave symcrypt method %ls failed with status 0x%08x. For more information, contact Customer Support Services.

37302 16 SGX error encountered during enclave attestation. The SGX enclave attestation method %ls failed with status 0x%08x.

37303 16 Internal error occurred while obtaining an authentication token for an attestation service. Authentication method: %ls, status: 0x%08x.

37304 16 Cannot initialize %ls enclave for column encryption – the operating system does not support the enclave type.

37305 16 Invalid enclave configuration: %ls.

37306 16 Internal enclave error: Cannot initialize the %ls enclave. Error: 0x%08x. For more information, contact Customer Support Services.

37307 16 Internal enclave error: Cannot initialize the %ls enclave. Load method: %s. For more information, contact Customer Support Services.

37308 16 Loaded %ls enclave for always encrypted.

37309 16 Enclave attestation failed due to an error in Intel Data Center Attestation Primitives (DCAP) SGX API: ‘%ls’. Return code: ‘0x%08x’. For more information, contact Customer Support Services.

37310 16 Enclave attestation failed due to an error while parsing the attestation URL provided by the client. URL: ‘%ls’. Return code: ‘0x%08x’.

37311 16 Enclave attestation failed. The attestation URL provided by the client has an invalid scheme name. URL: ‘%ls’. The supported schemes are: ‘%ls’.

37312 16 Enclave attestation failed. The attestation URL specified by the client is not reachable. URL: ‘%ls’. Return code: ‘0x%08x’. Check your networking configuration.

37313 16 Enclave attestation failed. The attestation service returned an empty response. Attestation URL: ‘%ls’. Verify the attestation policy. If the policy is correct, contact Customer Support Services.

37314 16 VBS enclave attestation failed due to an error in Windows Management Instrumentation (WMI). API: ‘%ls’, Return code: ‘0x%08x’. Check the Host Gurdian Service is running. For more information, contact Customer Support Services.

37315 16 Credential object named ‘0x%08x’, configured for external authentication, does not exist.

37316 16 Authentication bearer service failed to return a valid challenge. Verify URL ‘%ls’ is correct. Return code: ‘0x%08x’.

37317 16 Failed to look up ‘%ls’ for ‘%ls’.

37318 16 Unable to acquire an authentication token for resource_id ‘%ls’ with URL ‘%ls’. Return code: ‘0x%08x’. For more information, contact Customer Support Services.

37319 16 Failed to obtain an authentication token for URL ‘%ls’. Return code: ‘0x%08x’.

37320 16 Authentication for URL ‘%ls’ failed due to an invalid client id or an invalid secret. Return code: ‘0x%08x’.

37321 16 Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Return code: ‘0x%08x’.

37322 16 Failed to acquire a token using a managed service identity. Make sure managed identities are enabled on the machine hosting SQL Server. Error code: ‘%ls’. Error message: ‘%ls’. Return code: ‘0x%08x’.

37323 16 Authentication bearer service failed to return a valid challenge. Verify URL ‘%ls’ is correct. Error code: ‘%ls’. Error message: ‘%ls’. Return code: ‘0x%08x’.

37324 16 Enclave attestation failed. Attestation service returned Error code: ‘%ls’. Error message: ‘%ls’. Attestation URL: ‘%ls’. Return code: ‘0x%08x’. Verify the attestation policy. If the policy is correct, contact Customer Support Services.

37325 16 Enclave attestation failed due to an error in Azure Data Center Attestation Primitives (DCAP) Client. Validate Azure DCAP Client is installed and configured properly. Return code: ‘0x%08x’. For more information, contact Customer Support Services.

37326 16 Enclave attestation failed due an authorization failure. Verify the identity of SQL Server instance has the required permissions to access an attestation service at URL ‘%ls’.

38001 16 Cannot find the file id %d in the database ‘%s’.

38002 16 Only users having %s permission can execute this stored procedure.

39001 16 Only SELECT statement is supported for input data query to ‘sp_execute_external_script’ stored procedure.

39002 16 SQL failed to boot extensibility for error code 0x%lx.

39003 10 SQL successfully boots extensibility.

39004 16 A ‘%.*s’ script error occurred during execution of ‘sp_execute_external_script’ with HRESULT 0x%x.

39005 10 STDOUT message(s) from external script: %.*ls%.*ls

39006 10 External script execution status: %.*ls.

39007 16 The specified language ‘%.*ls’ does not exist or you do not have permission.

39008 16 Invlid Parameter name ‘%ls’ specified for Procedure. This clashes with internal parameters.

39009 16 Output parameter in external script execution is not yet supported.

39010 16 External script execution for ‘%.*s’ script encountered an unexpected error (HRESULT = 0x%x) for request id: %ls.

39011 16 SQL Server was unable to communicate with the LaunchPad service for request id: %ls. Please verify the configuration of the service.

39012 16 Unable to communicate with the runtime for ‘%.*s’ script for request id: %ls. Please check the requirements of ‘%.*s’ runtime.

39013 16 SQL Server encountered error 0x%x while communicating with the ‘%.*s’ runtime for request id: %ls. Please check the configuration of the ‘%.*s’ runtime.

39014 16 Parallelism in external script execution is not yet supported.

39015 16 SELECT INTO statement is not supported for input data query to ‘sp_execute_external_script’ stored procedure.

39016 16 The parameterized external script expects the parameter ‘%.*ls’, which was not supplied.

39017 16 Input data query returns column #%d of type ‘%ls’ which is not supported by the runtime for ‘%.*s’ script. Unsupported types are binary, varbinary, timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type. External script request id is %ls.

39018 16 Parameter ‘%.*ls’ uses a data type that is not supported by the runtime for ‘%.*s’ script. Unsupported types are timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type. External script request id is %ls.

39019 10 An external script error occurred: %.*ls%.*ls

39020 16 Feature ‘Advanced Analytics Extensions’ is not installed. Please consult Books Online for more information on this feature.

39021 16 Unable to launch runtime for ‘%.*s’ script for request id: %ls. Please check the configuration of the ‘%.*s’ runtime.

39022 10 STDERR message(s) from external script: %.*ls%.*ls

39023 16 ‘sp_execute_external_script’ is disabled on this instance of SQL Server. Use sp_configure ‘external scripts enabled’ to enable it.

39024 16 Parallel execution of ‘sp_execute_external_script’ failed. Specify WITH RESULT SETS clause with output schema.

39025 16 External script execution failed as extensibility environment is not ready yet. Retry the operation when the server is fully started.

39026 16 The parameter name ‘r_rowsPerRead’ is specified multiple times in ‘sp_execute_external_script’ call. The name ‘r_rowsPerRead’ is reserved for specifying streaming behavior only. External script request id is %ls.

39027 16 Parameter ‘%.*ls’ was specified multiple times to sp_execute_external_script stored procedure.

39031 16 Cannot parse the output schema of the builtin function ‘PREDICT’.

39032 16 The function PREDICT expects parameters in the form of ‘name = value’.

39033 16 The parameter name ‘%.*ls’ has already been declared. Parameter names must be unique in a PREDICT function call.

39034 16 The parameter ‘PARAMETERS’ in PREDICT function contains a definition that doesn’t match the supplied arguments.

39035 16 The function PREDICT has too many arguments supplied.

39036 16 The function PREDICT expects parameter ‘%.*ls’ which was not supplied.

39037 16 The function PREDICT contains a parameter ‘%.*ls’ that has an invalid type.

39038 16 The function PREDICT expects parameter ‘PARAMETERS’ of type ntext/nchar/nvarchar.

39039 16 Error converting the parameter value for ‘%.*ls’ to ‘%.*ls’.

39040 16 The function ‘PREDICT’ does not support SQL identifier or variable for ‘PARAMETERS’.

39041 16 The parameter ‘PARAMETERS’ has an invalid definition.

39042 16 %s EXTERNAL LIBRARY failed because the library source parameter %d is not a valid expression.

39043 16 %s EXTERNAL LIBRARY failed because filename ‘%.*ls’ is too long.

39044 16 %s EXTERNAL LIBRARY failed because it could not open the physical file ‘%.*ls’: %ls.

39045 16 %s EXTERNAL LIBRARY failed because it could not read from the physical file ‘%.*ls’: %ls.

39046 16 CREATE EXTERNAL LIBRARY failed because the user %.*ls” specified in the authorization clause does not exist.
3904716External library ‘%.*ls’ already exists for owner ‘%.*ls’ in database ‘%.*ls’.
3904816Failed to %s external library ‘%ls’: %ls.
3904910Message(s) from ‘PREDICT’ engine: %.*ls%.*ls
3905016Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Out of memory.
3905116Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Model is corrupt or invalid.
3905216Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Model type is unsupported.
3909216Initialization of native scoring libraries failed with HRESULT 0x%x.
3909316‘PREDICT’ function does not take parameters of varchar(max), nvarchar(max) or varbinary(max) type except for ‘MODEL’ parameter.
3909416‘PREDICT’ function only supports models smaller than  100 MB.
3909616Execution failed because its WITH clause specified different output columns from what ‘PREDICT’ function tries to return. The schema returned by ‘PREDICT’ function is ‘%ls’.
3909716Input data column #%d is of type ‘%ls’ which is not supported by ‘PREDICT’ function. Unsupported types are binary, varbinary, timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type.
3909816Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x.
3909916Feature or option ‘PREDICT’ is not yet implemented. Please consult Books Online for more information on this feature or option.
3910116‘%.*ls’ failed because it is not supported in the edition of this SQL Server instance.
3910216Duplicate column names are not allowed in ‘%.*ls’. Column name ‘%.*ls’ is a duplicate.
3910316Parameter ‘@input_data_1_order_by_columns’ is not allowed without parameter ‘@input_data_1_partition_by_columns’.
3910416Column ‘%.*ls’ in ‘%.*ls’ is not defined in the SELECT clause of ‘@input_data_1’ parameter.
3910516Invalid syntax for parameter ‘@input_data_1_partition_by_columns’. Specify a list of comma separated columns.
3910616Invalid syntax for parameter ‘@input_data_1_order_by_columns’. Specify a list of comma separated columns and an optional argument for sorting order <ASC|DESC>.
3910716Columns in parameters ‘@input_data_1_partition_by_columns’ and ‘@input_data_1_order_by_columns’ must be unique. Column name ‘%.*ls’ appears in both parameters.
3910816Maximum number of concurrent external script users has been reached. Limit is %d. Please retry the operation. External script request id is %ls.
3910916The combined total number of columns given in parameters ‘@input_data_1_partition_by_columns’ and ‘@input_data_1_order_by_columns’ exceeds the maximum %d.
3911016Maximum number of concurrent external script queries for this user has been reached. Limit is %d. Please retry the operation. External script request id is %ls.
3911116The SQL Server Machine Learning Services End-User License Agreement (EULA) has not been accepted.
3911215Duplicate file specification supplied for platform ‘%.*ls’.
3911315Number of file specifications exceeds the maximum of %d.
3911415CREATE EXTERNAL LIBRARY statement failed because of duplicate file specification. Only one file specification per platform is allowed in a CREATE EXTERNAL LIBRARY statement.
3911516ALTER EXTERNAL LIBRARY statement failed because the content for platform ‘%.*ls’ does not exist or is not correctly defined in the external library.
3911616ALTER EXTERNAL LIBRARY REMOVE PLATFORM statement failed because an external library requires at least one file specification to be defined.
3911716%.*ls EXTERNAL LANGUAGE statement failed because the parameter ‘%s’ is not a valid expression.
3911816%s EXTERNAL LANGUAGE statement failed because the specified file path ‘%.*ls’ is too long. Maximum length of file path is %d characters.
3911916%s EXTERNAL LANGUAGE failed because it could not open the physical file ‘%.*ls’: %ls.
3912016%s EXTERNAL LANGUAGE statement failed because it could not read from the physical file ‘%.*ls’: %ls.
3912116CREATE EXTERNAL LANGUAGE statement failed because the user “%.*ls” specified in the authorization clause does not exist or have permission.
3912216CREATE statement failed. External language ‘%.*ls’ already exists.
3912316%.*ls EXTERNAL LANGUAGE statement failed because the parameter ‘%s’ is not specified.
3912416‘%.*ls’ platform information doesn’t exist for the language ‘%.*ls’.
3912516ALTER EXTERNAL LANGUAGE statement failed because of duplicate file specification. Only one file specification per platform is allowed.
3912616ALTER EXTERNAL LANGUAGE REMOVE PLATFORM statement failed because an external language requires at least one file specification to be defined.
3912716External script execution for ‘%.*s’ script ran out of resources. External script request id is: %s.
3912816External language runtime for ‘%s’ could not be provisioned. Error code 0x%08x.
3912916Cannot drop external language ‘%.*ls’ because it is being referenced by external library ‘%.*ls’.
3913016%.*ls statement failed. Language ‘%s’ already exists.
3913116%.*ls statement failed. System language ‘%s’ can’t be altered or removed.
3913216The parameter ‘@r_rowsPerRead’ is invalid. Parameter ‘@r_rowsPerRead’ must be a positive integer.
3913316CREATE/ALTER EXTERNAL LANGUAGE statement failed. The environment variables string is invalid.
4000016Replicated tables support only local (non-DTC) two-phase commit involving the master database.
4000116Secondary kill was initiated during commit.
4000216Replicated row is not found.
4000316Unexpected operation in replicated message.
4000416Column count does not match.
4000516Duplicated transaction id.
4000616Unknown transaction id.
4000716Invalid nesting level.
4000816Replication target database is not found.
4000916Transaction state locally does not match the expected state.
4001016Replicated transactions across databases are not allowed.
4001116Replicated target table %ld is not found.
4001216Replicated target index %ld on table %ld is not found.
4001316Replicated target schema %.*ls is not found.
4001416Multiple databases can not be used in the same transaction.
4001516This functionality is not supported on replicated tables.
4001616The partitioning key column ‘%.*ls’ must be one of the keys of ‘%.*ls.%.*ls.%.*ls’ index.
4001716Partition key can not be changed.
4001816Partition key value is outside of the valid partition key range.
4001916The partition key column ‘%.*ls’ of table ‘%.*ls.%.*ls’ is nullable or does not match the partition key type defined in the table group.
4002016The database is in transition and transactions are being terminated.
4002116The low and high keys specified for the partition are invalid.  Low must be less than high.
4002216A partition with overlapping key ranges already exists.
4002316The name %s is too long.
4002416The last committed CSN (%d, %I64d) was not found in the log. The last seen CSN was (%d, %I64d).
4002516The transaction was aborted during commit due to a database state transition.
4002816The tablegroup name ‘%.*ls.%.*ls’ is not valid.
4002916Replicated tables can have at most %d columns.
4003016Can not perform replica operation because the replica does not exist in local partition map.
4003116The partition key column for table ‘%.*ls.%.*ls’ is undefined.
4003216Unsupported use of LOB in online index build.
4003316Attempted CSN epoch switch is not allowed. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4003416CSN being added must be equal last CSN+1. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4003516CSN being added must be equal or greater than the last CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4003616Can not perform replica operation because this node is not the secondary for this partition.
4003716The epoch being started must not have been used. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4003816Can not get ack to rollback replication message.
4003916Can not get ack to commit replication message.
4004016Failed to initiate VDI Client for physical seeding.
4004116Corrupted column status.
4004216Corrupted column length.
4004316Corrupted variable data. Actual remaining bytes is %d, expected %d bytes.
4004416Corrupted fixed size data. Actual remaining bytes %d, expected %d bytes.
4004516Message version mismatch. Actual version is %d and the expected is %d.
4004616The minimum required message version %d for message type %d is unsupported.
4004716Invalid use of parent transaction.
4004816Corrupted fragmented row flow sequence.
4004916Corrupted fragmented row.
4005016Corrupted LOB row.
4005116Use of UPDATETEXT on replicated tables is not supported.
4005216Parallel queries are not supported on replicated tables.
4005316Attempt to replicate a non-replicated system table %ld.
4005416Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again.
4005616Master, tempdb, model and mssqlsystemresource databases can not be replicated.
4005716Table is not enabled for replication.
4005816Unsupported replicated table usage option. Refer to the state to identify the cause.
4006016Attempt to replicate out of partition already locked for internal use.
4006116Unknown rowset id.
4006216Incorrect replica role transition.
4006316Replica is not found.
4006416Attempt to add a CSN to an invalid CSN vector. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4006516CSN vector can be reinitialized only with initial or invalid CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4006616Transport destination is not found.
4006716Corrupted row sequence.
4006816Idempotent mode has been used on an unknown transaction.
4006916Could not obtain rowset interface.
4007016CSN mismatch detected. The local CSN is (%d,%I64d), the remote CSN is (%d,%I64d).
4007116This partition does not have enough valid secondaries to start a DML transaction. The needed count is %ld, the current counts are %ld (main quorum) and %ld (transient quorum).
4007216Corrupted rowset metadata sequence.
4007316Partitioned tables are not supported.
4007416Partition key is not found is the target rowset or is nullable or not part of index keys.
4007516Column schema mismatch for rowset %ls.%ls.%ls column %ld.
4007616Too few columns from remote rowset %ls.%ls.%ls.
4007716Remote rowset %ls.%ls.%ls column %ld is not found locally.
4007816The persisted queue logging has failed.
4007916A non-null variable length value is received for a column that is shorter locally.
4008016Corrupted (too long) packed row.
4008116Cardinality of index should not be less then zero.
4008216Induced exception for testing purposes.
4008316Corrupted CSN vector.
4008416Multiple modifications to CSN vector in the same transaction are not supported.
4008516The primary partition has lost the quorum. New transactions can not start.
4008616Primary hit an error with this secondary.
4008716Replica with the specified version is not found.
4008816CSN being set is outside the CSN epoch range. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4008916The index configuration for table %ld index %ld does not match the source.
4009016The primary partition is in transition and the transaction can not commit.
4009116Truncation CSN is mismatched. The truncation CSN is (%d,%I64d), the current CSN is (%d,%I64d).
4009216This index %ld state for table %ld does not match the source.
4009316Replication background task hit a lock timeout. User transactions will be killed and the operation will be retried.
4009416Incompatible key metadata change. The scan can not be resumed.
4009513Replication transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. The operation will be retried.
4009616Critical replication task could not start. State is %d.
4009716The begin transaction message was not found when scanning persisted replication queue.
4009816Mismatched partition id found in the transaction log.
4009916Invalid nested transaction count found in the transaction log.
4010116The partition does not have persisted queues enabled.
4010216The partition can not have persisted queues modified in this state.
4010316The partition can not be changed inside a persisted object.
4010416Only sysadmin can execute this stored procedure ‘%.*ls’.
4010516The local partition map for database %.*ls is starting up in reduced functionality mode because of log full. Pending partition deletes will not be processed until the log is truncated.
4010616The schema scope set in the session is not the current schema scope for the current partition. Please rerun your query.
4010816The filtered replica is not a subset of the primary replica. This is only possible for table groups without a partition key.
4010916Number of parameters specified for procedure or function %.*ls is incorrect.
4011016Cannot scope database %s for sp_cloud_scope_database spec proc because it is already set up as a partition database.
4011116Unable to delete partition DB id %d.
4012616The partition database was not found during pending schema scope cleanup, deleting partition metadata only (%d, %s).
4012716%S_MSG database ‘%.*ls’ link up with the %S_MSG database %d encountered the error: %S_MSG.
4012816Cannot pair database ‘%.*ls’ with fabric because it is not a partition host.
4012916%S_MSG database link up with the %S_MSG database ‘%.*ls’ encountered the error: %ls.
4013016Replication quorum parameter is %d. It should be >= 1 and <= 32.
4013116Partition key type ‘%.*ls’ is not supported. Only BIGINT, UNIQUEIDENTIFIER, and VARBINARY(n) (0<n<=512) datatypes are supported currently.
4013216Before dropping a table group, you have to delete all the partitions.
4013315This operation is not supported in this version of SQL Server.
4013416get_new_rowversion() can only be used in an active transaction.
4013515This system metadata view is not supported.
4013615Could not disable versioning because the database is not in single user mode.
4013715Could not refresh options for all scoped databases.
4013816Query references entities from multiple partitions.
4013916The data node does not host a replica of the requested partition.
4014016Set partition failed since a different partition already was set in the current transaction. Cross partition operations within a node are not reliable or supported.
4014116Partition has to be set using sp_set_partition before executing this query.
4014216Accessing a different partition in the same transaction is not allowed.
4014316The replica that the data node hosts for the requested partition is not primary.
4014416Cannot find the object “%.*ls” because it does not exist or you do not have permissions.
4014516Database is not found.
4014616Table group object is not found.
4014716Stored procedure ‘%.*ls’ is only for CloudDB.
4014816The existing persisted queue snapshot CSN (%d, %I64d) at %S_LSN is greater than the requested snapshot CSN (%d, %I64d) at %S_LSN.
4014916The database does not host any partitions.
4015016Downgrading the severity of error %d, severity %d, state %d because it would cause the server to be shutdown on a non-critical error.
4015116Partition is in transactionally inconsistent state.
4015216Partition delete expects no context transaction.
4015316The current database has been shutdown. The current database has been switched to master.
4015416Cannot use sp_cloud_add_partition or sp_cloud_delete_partition within a transaction when Partition DB are enabled.
4015516Invalid arguments provided to sp_cloud_add_partition spec proc (%s).
4015616Drop is not allowed on the %S_MSG database ‘%.*ls’ as it contains partitions. Drop the partition before the operation.
4015716Too many secondaries. At most 32 are currently supported.
4015816Could not change database collation for database id %d.
4015916Database scoping cannot be run inside a transaction.
4016016Heartbeat message version mismatch. Actual version is %d and the expected is %d.
4016116Invalid partition type. Only 1 or 2 is supported.
4016216The replica that the data node hosts for the requested partition is not transactionally consistent.
4016316Become nothing expects no context transaction.
4016416Idempotent flush expects no context transaction.
4016516Prepare for full commit expects no context transaction.
4016616A CloudDB reconfiguration is going on and all new user transactions are aborted.
4016721A paired CloudDB fabric node failed and database %d must be shutdown.
4016816SILO_TO_PDB: Partition copy is disabled in M1.
4016916Waiting for database copy sync with %s.%s has failed. Please make sure the database is in the CATCH_UP state and try again later.
4017016Catchup of secondary at %s:%s:%s:%d has failed.
4017116Table group name (single part name) should not be longer than nvarchar(64).
4017216The partition is not in a state that allows deletion.
4017316This requested operation can not performed as this partition is in delete process.
4017416The partition is in transition and transactions are being terminated.
4017516Add a secondary with wait can not be used in a transaction.
4017616Rename a partition can not be used in a transaction.
4017716The new table group does not match the existing table group for the renaming partition.
4017816A partition with same name already exists.
4017916Fabric-database (‘%.*ls’) cannot be paired, the server is not ready to pair.
4018016Fabric-database (‘%.*ls’) cannot be paired, the database is already paired.
4018116Fabric-database (‘%.*ls’) cannot be paired, the supplied mutex (‘%.*ls’) could not be opened. Error code: %d
4018216The schema scope %ld being created is not empty.
4018316Could not create database side pairing mutex for database (‘%.*ls’). Error code: %d
4018416Login failed. A system operation is in progress, and the database is not accepting user connections.
4018516Secondary failure report expects no context transaction.
4018616The data node does not host a replica of the requested partition with the requested version.
4018716The metadata record for the partition does not exist.
4018816Failed to update database “%.*ls” because it is switched to read-only to enforce disaster recovery RPO.
4018916The resource quota for the current database has been exceeded and this request has been aborted. Please rerun your request in the next quota window. %s
4019016A context transaction is required.
4019116Cannot create partition DB (%s).
4019216Catchup of secondary at %s:%s:%s:%d has been cancelled.
4019316The maximum allowed number of database is already paired.
4019416Table %s has a partition key already. Explicitly specifying a new partition key is not allowed. Please use “Alter table”.
4019516%ls FOR SID command is not supported in this version of SQL Server.
4019616A varbinary can not be longer than max length specified.
4019716The service has encountered an error processing your request. Please try again. Error code %d.
4019816Only a primary replica can be configured as a forwarder.
4019916There should be no context transaction when entering the forwarder pending state.
4020116Destination server name is too long.
4020216Corrupted composite message.
4020316Could not register AsyncTransport endpoint.
4020416Dispatch sequence number maintenance failure
4020516Maximum transport queue size reached.
4020616Heartbeat lease time is less than the heartbeat worker interval.
4020716Async transport test failed.
4020816Corrupted received message format.
4020917Duplicate destination id.
4021016Cluster name has not been set.
4030116Invalid lock mode or resource received in lock request.
4030216Invalid identity value.
4030316Enter idempotent sequence.
4030416Target object %ld is not found.
4030516The current object is not a relation.
4030616Cannot create an index %ld on object %ld.
4030716Cannot find index %ld on object %ld.
4030816Metadata replication protocol error.
4030916Partition %ld is not found
4031016Converting a clustered index into a heap is not supported.
4031116Switching out partitions not supported.
4031216Inconsistent index build state.
4031316Not all rowsets could be deleted.
4031416Identity column not found on object %ld.
4050120The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d
4050216Duplicate group id settings specified.
4050316Database field %ls contains invalid value ‘%.*ls’.  Expected data type %ls.
4050416Switching Databases is not supported.  Use a new connection to connect to a different Database.
4050516Incorrect user credentials.
4050616Specified SID is invalid for this version of SQL Server.
4050716‘%.*ls’ cannot be invoked with parameters in this version of SQL Server.
4050816USE statement is not supported to switch between databases. Use a new connection to connect to a different database.
4050916Upgrade of SAWA v1 database fails. Check the metadata of the database before re-running the upgrade.
4051016Statement ‘%.*ls’ is not supported in this version of SQL Server.
4051116Built-in function ‘%.*ls’ is not supported in this version of SQL Server.
4051216Deprecated feature ‘%ls’ is not supported in this version of SQL Server.
4051316Server variable ‘%.*ls’ is not supported in this version of SQL Server.
4051416‘%ls’ is not supported in this version of SQL Server.
4051516Reference to database and/or server name in ‘%.*ls’ is not supported in this version of SQL Server.
4051616Global temp objects are not supported in this version of SQL Server.
4051716Keyword or statement option ‘%.*ls’ is not supported in this version of SQL Server.
4051816DBCC command ‘%.*ls’ is not supported in this version of SQL Server.
4051916Invalid value ‘%.*ls’ of login field in gateway magic syntax.
4052016Securable class ‘%S_MSG’ not supported in this version of SQL Server.
4052116Securable class ‘%S_MSG’ not supported in the server scope in this version of SQL Server.
4052216Database principal ‘%.*ls’ type is not supported in this version of SQL Server.
4052316Implicit user ‘%.*ls’ creation is not supported in this version of SQL Server. Explicitly create the user before using it.
4052416Data type ‘%.*ls’ is not supported in this version of SQL Server.
4052516‘WITH %ls’ is not supported in this version of SQL Server.
4052616‘%.*ls’ rowset provider not supported in this version of SQL Server.
4052716Linked servers are not supported in this version of SQL Server.
4052816Users cannot be mapped to Windows logins in this version of SQL Server.
4052916Built-in function ‘%.*ls’ in impersonation context is not supported in this version of SQL Server.
4053016The %.*ls statement must be the only statement in the batch.
4053111Server 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 server name, in which case the server name must be included as part of the user name ([email protected]).  In addition, if both formats are used, the server names must match.
4053211Cannot open server “%.*ls” requested by the login.  The login failed.
4053316Server ‘%.*ls’ already exists.
4053416A valid SID is already associated with the database owner.
4053516Properties for schema scope ‘%.*ls’ already exist.
4053616‘%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 Windows Azure SQL Database.
4053716User ‘%.*ls’ not found in the database.
4053816A valid URL beginning with ‘https://’ is required as value for any filepath specified.
4053916Windows Azure Storage credential ‘%.*ls’ was not found.
4054016Transaction was aborted as database is moved to read-only mode. This is a temporary situation and please retry the operation.
4054116Procedure cannot be called from inside a partition.
4054216Incorrect number of parameters specified for procedure.
4054316Invalid %S_MSG name specified. Length should be between 1 and %d.
4054420The database ‘%.*ls’ has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
4054520The service is experiencing a problem that is currently under investigation. Incident ID: %ls. Code: %d
4054616Cannot create UCS task pool
4054816Granting CONNECT permission to the guest user in database ‘%.*ls’ is not permitted.
4054916Session is terminated because you have a long running transaction. Try shortening your transaction.
4055016The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction.
4055116The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce temporary table space usage.
4055216The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction.
4055316The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows.
4055410Exiting because of XEvent %ls.
4055516‘%ls’ is not supported for this database. See Books Online for more details on feature support in different service tiers of Windows Azure SQL Database.
4055816Error – cannot perform checkpoint on a partition database before loading partition information.
4055916File based statement options are not supported in this version of SQL Server.
4056116Database copy failed. Either the source or target database does not exist.
4056216Database copy failed. The source database has been dropped.
4056316Database copy failed. The target database has been dropped.
4056416Database copy failed. Database copy failed due to an internal error. Please drop target database and try again.</value>
4056516Database copy failed. No more than 1 concurrent database copy from the same source is allowed. Please drop target database and try again later.
4056616Database copy failed due to an internal error. Please drop target database and try again.
4056716Database copy failed due to an internal error. Please drop target database and try again.
4056816Database copy failed. Either the source or the target database has become unavailable. Please drop target database and try again.
4056916Database copy failed. Target database has become unavailable. Please drop target database and try again.
4057016Database copy failed due to an internal error. Please drop target database and try again later.
4057116Database copy failed due to an internal error.  Please drop target database and try again later.
4057216Cannot obtain primary partition lock for CloudDB auto partition upgrade.
4057316Cannot upgrade CloudDB auto partitions in database ‘%.*ls’ because the physical database is read only.
4057416Permissions for system stored procedures, server scoped catalog views, and extended stored procedures cannot be changed in this version of SQL Server.
4057516Data type ‘%.*ls’ is not supported in a federated database.
4057616Table DDL on non-temporary tables is not supported in a filtered connection.
4057716The constraint ‘%ls’ is not supported in a federated database.
4057816Statement ‘%.*ls’ is not supported in a filtered connection.
4057916DML statements are not supported on non-federated tables in a filtered connection.
4058016Statement ‘%.*ls’ is not supported in a federated database.
4058116Logically filtered secondaries are only supported if the secondary is a forwarder.
4058216Federation member metadata for a database cannot be changed when there are logically filtered secondaries attached (split is running).
4058316Federation member does not exist for the given member id and federation root
4058416Value ‘%.*ls’ for option ‘%.*ls’ is not supported in this version of SQL Server.
4058516Can not perform replica operation because this node is not the forwarder for this partition.
4058616Replicas with deferred commit enabled cannot be a member of a quorum.
4058716Deferred commit is only supported with forwarder replicas.
4058816Cannot create partition worker pool
4058916Replicas that are not enabled for deferred commit cannot specify RPO.
4059016The Gpm is in rebuild and cannot be accessed as it is not yet consistent.
4059116Extended event configuration could not be initialized. The error is %ls.
4059216Extended event session ‘%ls’ could not be created or altered. XE Error %d.%d state:%d.
4059316Extended event session ‘%ls’ returned error ‘%ls’.
4059416Extended event session ‘%ls’ has been started.
4059516Extended event session ‘%ls’ has been altered.
4059616Extended event session ‘%ls’ has been stopped.
4059716A federation root database cannot be read only.
4059816A federation member cannot be read only.
4059916This type of KILL is not supported in Windows Azure SQL Database; Only ‘KILL session ID [WITH STATUSONLY]’ and ‘KILL UOW’ are supported.
4060116Server Admin user already exists.
4060216Could not create login. Please try again later.
4060316Cannot execute procedure because current user is not Gateway.
4060416Could not %.*ls because it would exceed the quota of the server.
4060516There is no route from the source cluster ‘%ls’ to the target cluster ‘%ls’.
4060616Databases cannot be attached in this version of SQL Server.
4060716Windows logins are not supported in this version of SQL Server.
4060810This session has been assigned a tracing ID of ‘%.*ls’.  Provide this tracing ID to customer support when you need assistance.
4060916‘%.*ls’ is not a valid IPv4 address.
4061016The IP address that starts with ‘%.*ls’ is too long. Maximum length is %d.
4061116Windows Azure SQL Database supports a maximum of 128 firewall rules.
4061216Spec proc was executed against a silo that cannot be upgraded to include firewall objects.
4061317Database ‘%.*ls’ on server ‘%.*ls’ is not currently available.  Please retry the connection later.  If the problem persists, contact customer support, and provide them the session tracing ID of ‘%.*ls’.
4061416Start IP address of firewall rule cannot exceed End IP address.
4061516Cannot open server ‘%.*ls’ requested by the login. Client with IP address ‘%.*ls’ is not allowed to access the server.  To enable access, use the Windows Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
4061616‘%.*ls’ is not a valid login name in this version of SQL Server.
4061716The firewall rule name that starts with ‘%.*ls’ is too long. Maximum length is %d.
4061816The firewall rule name cannot be empty.
4061916The edition ‘%.*ls’ does not support the database data max size ‘%.*ls’.
4062016The login failed for user “%.*ls”. The password change failed. Password change during login is not supported in this version of SQL Server.
4062116metric type
4062216metric data
4062320Reauthentication failed for login “%.*ls”. Within the past reauthentification interval, the login has become invalid due to a password change, a dropped login, or other cause.  Please retry login.
4062416Operation is not allowed because server ‘%.*ls’ is disabled.
4062517Provisioning (creating, altering, or dropping) Windows Azure SQL Database servers and databases is currently disabled.  This most frequently occurs for brief periods during system maintenance.
4062620The ALTER DATABASE command is in process.  Please wait at least five minutes before logging into database ‘%.*ls’, in order for the command to complete.  Some system catalogs may be out of date until the command completes.  If you have altered the database name, use the NEW database name for future activity.
4062720Operation on server ‘%.*ls’ and database ‘%.*ls’ is in progress.  Please wait a few minutes before trying again.
4062816Failed to update database ‘%.*ls’ because the database is read-only. Please contact your Windows Azure service owner. There may be billing related issues with your Windows Azure account.
4062916An edition could not be determined from maxsize ‘%.*ls’.  Specify a valid maxsize value.
4063016Password validation failed. The password does not meet policy requirements because it is too short.
4063116The password that you specified is too long. The password should have no more than %d characters.
4063216Password validation failed. The password does not meet policy requirements because it is not complex enough.
4063316‘%.*ls’ is not a valid database edition in this version of SQL Server.
4063416This stored procedure can only be executed in the master database.
4063516Client with IP address “%.*ls” is temporarily blocked.
4063616Cannot use reserved database name ‘%.*ls’ in this operation.
4063717Database copy is currently disabled.
4063816Invalid subscription id ‘%.*ls’.  Subscription does not exist.
4063916Request does not conform to schema: %.*ls.
4064020The server encountered an unexpected exception.
4064116Location ‘%.*ls’ cannot be found.
4064217The server is currently too busy.  Please try again later.
4064316The specified x-ms-version header value is invalid.
4064414Failed to authorize access to the specified subscription.
4064516Servername “%.*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 lead or trail in the name.
4064616Subscription ID cannot be empty.
4064716Subscription ‘%.*ls’ does not have the server ‘%.*ls’.
4064817Too many requests have been performed.  Please retry later.
4064916Invalid content-type is specified.  Only application/xml is supported.
4065016Subscription ‘%.*ls’ is not ready for the operation because another operation is currently in progress. Please wait a few minutes and then try the operation again.
4065116Failed to create server because the subscription ‘%.*ls’ is disabled.
4065216Cannot move or create server. Subscription ‘%.*ls’ will exceed server quota.
4065316Could not find database ‘%.*ls’ at time ‘%.*ls’ that can be restored.
4065416Specified subregion ‘%.*ls’ is invalid.
4065516Database ‘master’ cannot be restored.
4065616Quota for maximum number of concurrent restores has been exceeded.
4065716Restore is not enabled on the server.
4065816Quota for number of restores has been exceeded.
4065916Could not successfully restore database because the maximum duration for processing a restore has elapsed.
4066016Could not successfully restore database. This request has been assigned a tracing ID of ‘%.*ls’.  Provide this tracing ID to customer support when you need assistance.
4066116Restore has been cancelled by a system administrator.
4066216An internal error was encountered when processing the restore request. This request has been assigned a tracing ID of ‘%.*ls’.  Provide this tracing ID to customer support when you need assistance.
4066316Database ‘%.*ls’ is currently being restored and cannot be dropped. Please wait for restore to complete.
4066416Database ‘master’ cannot be copied.
4066516‘%.*ls’ is not a supported collation.
4066616‘%.*ls’ is a unicode-only collation and cannot be a default collation for a database.
4066715Specifying a LOGIN is not allowed in a federation member.
4066816‘%.*ls’ is not a valid user name or you do not have permission.
4066917Location ‘%.*ls’ is not accepting creation of new Windows Azure SQL Database servers at this time.
4067016The http header ‘ocp-resourceprovider-registered-uri’ is missing from the request or is invalid. To continue, provide a valid value for the header.
4067117Unable to ‘%.*ls’ ‘%.*ls’ on server ‘%.*ls’. Please retry the connection later.
4067216The 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 service objective assignment completed for this database.
4067316The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the server name, database name and activity ID.
4067416Service objective creation or assignment is not permitted for this subscription.
4067516The service is currently too busy.  Please try again later.
4067716The operation for the request uri ‘%.*ls’ was not found. To continue, please provide a valid request uri.
4067816Invalid value for header ‘%.*ls’. The header must contain a single valid GUID.
4067916The operation cannot be performed since the database ‘%ls’ is not in a replication relationship.
4068016The operation cannot be performed since the database ‘%ls’ is in a replication relationship.
4068116The operation cannot be performed since the database ‘%ls’ is a replication target.
4068216Failed to update database ‘%.*ls’ because the database is a replication target.
4068316The operation cannot be performed since the database ‘%ls’ is not a replication target.
4068416A seeding operation is already in progress for database ‘%ls’.
4068516A terminate operation is already in progress for database ‘%ls’.
4068616The operation is currently not supported.
4068716The operation cannot be performed on the database ‘%.*ls’ in its current state.
4068816The databases ‘%ls’ in server ‘%ls’ and ‘%ls’ in server ‘%ls’ are already in a replication relation.
4068916Replication limit reached. The database ‘%ls’ cannot have more than %d replication relationships.
4069016The operation cannot be performed since the replication source and target databases have different names. The source and target databases must have the same name.
4069116Replication target cannot be created in the same server as source.
4069216The alter database ‘%ls’ failed to initiate because there are operations pending on the database. After the pending operations are complete, try again.
4069316The current operation cannot be initiated while a replication operation is in progress. You can rename the database only after the replication operation has stopped.
4069416The seeding operation cannot be initiated on a replication target database.
4069516The operation cannot be performed since the database is currently a Federation root or member database.
4069616sp_wait_for_database_copy_sync failed because the current database is not the primary database involved in a replication relationship with the specified target server ‘%s’ and database ‘%s’.
4069716Login failed for user ‘%.*ls’.
4069816‘%.*ls’ cannot be performed on a free database.
4069916You cannot create a user with password in this version of SQL Server
4070116XML format used for specifying rules is invalid. %.*ls.
4070216Failed to parse XML rules.
4070316Invalid attribute name ‘%.*ls’ in %.*ls.
4070416Invalid element name ‘%.*ls’ in %.*ls.
4070516Invalid Feature type ‘%.*ls’ in %.*ls.
4070616Feature name ‘%.*ls’ does not exist.
4070716Invalid index value ‘%.*ls’ in %.*ls.
4070816Invalid param count ‘%.*ls’ in %.*ls.
4070916operator attribute is missing in %.*ls.
4071116Rule name ‘%.*ls’ does not exist.
4071216Invalid usage of %.*ls.
4071316Invalid values supplied for <parameter> element in %.*ls.
4071416Out of memory.
4071516Invalid operator type %.*ls in %.*ls.
4071616Invalid input type %.*ls in %.*ls.
4071716index attribute is missing in %.*ls.
4071816one of inputtype, isnull and format attributes is required in %.*ls.
4071916Failed to get %s lock on %s rules.
4072016Rule name ‘%.*ls’ already exists.
4072116Only one of inputtype, isnull and format attributes is required in %.*ls.
4072216Failed to clear proc cache.
4072316Rule name cannot exceed more than %d characters.
4072416Unexpected Operator attribute in %.*ls.
4080116Operation ALTER USER WITH LOGIN failed. User provided login does not match the login in the federation root database for the user provided username.
4080216A service objective assignment on server ‘%.*ls’ and database ‘%.*ls’ is already in progress. Please wait until the service objective assignment state for the database is marked as ‘Completed’.
4080316The server ‘%.*ls’ has reached its quota of (%d) premium databases.
4080416The specified service objective ‘%.*ls’ is invalid.
4080516The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the activity ID.
4080616The request to retrieve subscription information has timed out. Please try again later.
4080716Could not retrieve subscription information for subscription id: %.*ls, after %d attempts. Please try again later.
4080816The edition ‘%.*ls’ does not support the service objective ‘%.*ls’.
4080916No rows found in sys.dm_operation_status table for database ‘%.*ls’ and operation ‘%.*ls’.
4081016More than one row found in sys.dm_operation_status table for database ‘%.*ls’ and operation ‘%.*ls’.
4081116Operation ‘%.*ls’ for database ‘%.*ls’ cannot be cancelled as it has already completed.
4081216Database ‘%.*ls’ cannot be dropped as create operation is in progress. The create operation will be cancelled.
4081316Could not set database as writable because the database is Premium (suspended).
4081416Could not change database edition to or from Premium for a Federation root.
4081516Could not change database edition to or from Premium for a Federation member.
4081616Could not change database edition to Premium for a database in a replication relationship.
4081716Could not change database edition from Premium for a database in a replication relationship.
4081816The replication operation on database ‘%ls’ failed because there are alter operations pending on the database. Try again after the pending operations have completed.
4082016The server has reached its quota of (%d) premium databases.
4082116Federations are not supported on a Premium database.
4082216This feature is not available for the selected database’s edition (%ls).
4082316Invalid proxy override option supplied.
4082416ProxyOverrideSupport feature switch is not turned ON.
4082516Unable to complete request now. Please try again later.
4082716The operation is not supported for your subscription offer type.
4083816Replication relationship limit reached. The database ‘%ls’ cannot have more than one non-readable secondary.
4083916Connection to a non-readable secondary database is not allowed. See ‘http://go.microsoft.com/fwlink/?LinkID=402429&clcid=0x409’ for more information.
4084016Target region ‘%ls’ is not a DR paired Azure region. See ‘http://go.microsoft.com/fwlink/?LinkID=402430&clcid=0x409’ for more information.
4084116Friendly termination of a non-readable replication relationship is not supported.
4084216Termination of the non-readable replication relationship for database ‘%ls’ is currently not allowed. See ‘http://go.microsoft.com/fwlink/?LinkID=402431&clcid=0x409’ for more information
4084316Non-readable secondary is not supported for database copy.
4084416Database ‘%ls’ on Server ‘%ls’ is a ‘%ls’ edition database in an elastic pool and cannot have a replication relationship.
4084716Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of %d.
4084816The source database ‘%ls’.’%ls’ cannot have higher performance level than the target database ‘%ls’.’%ls’. Upgrade the performance level on the target before upgrading source.
4084916The target database ‘%ls’.’%ls’ cannot have lower performance level than the source database ‘%ls’.’%ls’. Downgrade the performance level on the source before downgrading target.
4085016Could not change database edition from ‘%ls’ to Standard for database ‘%ls’ in a replication relationship.
4085116Could not change database edition from ‘%ls’ to Basic for database ‘%ls’ in a replication relationship.
4085216Cannot open database ‘%.*ls’ on server ‘%.*ls’ requested by the login. Access to the database is only allowed using a security-enabled connection string.
4085416Partner server ‘%ls’ is not compatible with server ‘%ls.’
4085516The operation cannot be performed since the database ‘%ls’ is not in ‘%ls’ state on the replication relationship.
4085616Could not change database edition for database ‘%ls’ in a replication relationship.
4085716Elastic pool not found for server: ‘%ls’, elastic pool name: ‘%ls’.
4085816Elastic pool ‘%ls’ already exists in server: ‘%ls’
4085916Elastic pool does not support database edition ‘%ls’.
4086016Elastic pool ‘%ls’ and service level objective ‘%ls’ combination is invalid.
4086116The database edition ‘%ls’ cannot be different than the elastic pool service tier which is ‘%ls’.
4086216Elastic pool name must be specified if the elastic pool service objective is specified.
4086316Connections to this database are no longer allowed.
4086416The DTUs for the elastic pool must be at least (%d) DTUs for service tier ‘%.*ls’.
4086516The DTUs for the elastic pool cannot exceed (%d) DTUs for service tier ‘%.*ls’.
4086616Max size (%d) is not valid. Please specify a valid max size.
4086716The DTU max per database must be at least (%d) for service tier ‘%.*ls’.
4086816The DTU max per database cannot exceed (%d) for service tier ‘%.*ls’.
4086916The DTU max per database (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’.
4087016The DTU min per database cannot exceed (%d) for service tier ‘%.*ls’.
4087116The DTU min per database (%d) for the elastic pool does not belong to the allowed values for service tier ‘%.*ls’.
4087216DTU value (%d) is not valid. Please specify a valid dtu value.
4087316The number of databases (%d) and DTU min per database (%d) cannot exceed the DTUs of the elastic pool (%d).
4087416The DTUs (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’.
4087516The elastic pool storage limit in gigabytes cannot exceed (%d) in service tier ‘%.*ls’.
4087616Elastic pools are not available in this region.
4087716The elastic pool is not empty.
4087816The elastic pool storage limit in gigabytes must be at least (%d) for service tier ‘%.*ls’.
4087916The elastic pool storage limit in gigabytes (%d) does not belong to the allowed values for service tier ‘%.*ls’.
4088016The DTUs (%d) for the elastic pool and the storage limit in gigabytes (%d) are inconsistent for service tier ‘%.*ls’.
4088116The elastic pool ‘%.*ls’ has reached its database count limit. The database count for the elastic pool cannot exceed (%d) for service tier ‘%.*ls’.
4088216Can not change SLO from DataWarehouse edition to other SQL DB editions and vice versa.
4088316The service level objective ‘%.*ls’ specified is invalid. It must be a slo supported by DataWarehouse edition.
4088416New service level objective ‘%.*ls’ has (%d) physical databases and it is not compatible with current service level objective which has (%d) physical databases.
4088516Failed to deactivate database.
4088616Failed to change service level objective for database.
4088716Failed to activate database.
4088816Update service level objective for database feature is disabled.
4088916The DTUs or storage limit for the elastic pool ‘%.*ls’ cannot be decreased since that would not provide sufficient storage space for its databases.
4089016The elastic pool is busy with another operation.
4089116The DTU min per database (%d) cannot exceed the DTU max per database (%d).
4089216Cannot connect to database when it is paused.
4089316The database copy link from ‘%s.%s’ to ‘%s.%s’ was not successfully created or was deleted before the data copy link operation completed.
4089416The database copy link from ‘%s.%s’ to ‘%s.%s’ is not in the catchup state after the data copy link operation completed.
4089516The database copy link from ‘%s.%s’ to ‘%s.%s’ was not successfully deleted before completion of copy.
4089616The database copy link from ‘%s.%s’ to ID %s was not successfully dropped.
4089716The elastic pool storage limit in megabytes must be at least (%d) for service tier ‘%.*ls’.
4089816The elastic pool storage limit in megabytes (%d) does not belong to the allowed values for service tier ‘%.*ls’.
4089916The DTUs (%d) for the elastic pool and the storage limit in megabytes (%d) are inconsistent for service tier ‘%.*ls’.
4090016The service tier for an elastic pool cannot be changed.
4090116The elastic pool storage limit in megabytes cannot exceed (%d) in service tier ‘%.*ls’.
4090216Amount of pool storage cannot be specified when creating a Premium elastic pool.
4090320The server ‘%.*ls’ is currently busy.  Please wait a few minutes before trying again.
4090416Could not perform the operation because server would exceed the allowed Database Edition %s quota of %d.
4090516Location ‘%.*ls’ is not accepting creation of new Azure SQL Database Servers of version ‘%.*ls’ at this time. This location only supports the following server versions: ‘%.*ls’. Please retry using a supported server version.
4090616A service objective change cannot start for database %s on server %s while it is also running for database %s on server %s.
4090716Servers involved in a Disaster Recovery Configuration cannot reside in the same location
4090816A Disaster Recovery Configuration already exists for ‘%.*ls’ and ‘%.*ls’
4090916A Disaster Recovery Configuration does not exist for ‘%.*ls’ and ‘%.*ls’
4091016A Disaster Recovery Configuration does not exist for server ‘%.*ls’ and virtual endpoint ‘%.*ls’
4091116Server ‘%.*ls’ is not the secondary in the Disaster Recovery Configuration and cannot initiate a failover
4091216The value for custom backup retention in days must be between %d and %d
4091316Windows Azure SQL Database supports a maximum of %d Virtual Network firewall rules.
4091416Cannot open server ‘%.*ls’ requested by the login. Client is not allowed to access the server.
4091516Secondary server specified in a Failover Group cannot reside in the same region
4091616The Failover Group ‘%.*ls’ already exists on server ‘%.*ls’
4091716The Failover Group ‘%.*ls’ does not exist on server ‘%.*ls’
4091816The Failover Group ‘%.*ls’ is busy with another operation and cannot perform the ‘%.*ls’ operation. Please try again later
4091916The server ‘%.*ls’ is currently the primary server in the Failover Group and cannot initate failover
4092016The database ‘%.*ls’ is already included in another Failover Group
4092116The operation to add database ‘%.*ls’ to Failover Group is in progress, please wait for this operation to finish
4092216The operation to remove database ‘%.*ls’ from Failover Group is in progress, please wait for this operation to finish
4092316The database ‘%.*ls’ is a secondary in an existing geo-replication relationship and cannot be added to the Failover Group
4092416The operation cannot be performed due to multiple errors: ‘%.*ls’
4092516Can not connect to the database in its current state.
4092616The 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 to individually terminate or failover.
4092716The endpoint ‘%.*ls’ is already in use. Use a different Failover Group name.
4092816Create or update Failover Group operation successfully completed; however, some of the databases could not be added to or removed from Failover Group: ‘%.*ls’
4092916The source database ‘%ls.%ls’ cannot have higher edition than the target database ‘%ls.%ls’. Upgrade the edition on the target before upgrading source.
4093016The target database ‘%ls.%ls’ cannot have lower edition than the source database ‘%ls.%ls’. Downgrade the edition on the source before downgrading target.
4093116Failover 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 may not lead or trail in the name.
4093216The elastic pool cannot change its service tier since one or more of its databases use memory-optimized objects.
4093316The edition ‘%.*ls’ does not support the database tempdb max size ‘%.*ls’.
4093416Server 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 may not lead or trail in the name.
4093516The endpoint ‘%.*ls’ is already in use. Use a different Server DNS Alias name.
4093616The Server DNS Alias ‘%.*ls’ already exists for the server ‘%.*ls’.
4093716The Server DNS Alias ‘%.*ls’ does not exist for the server ‘%.*ls’.
4093816The Server DNS Alias ‘%.*ls’ is busy with another operation and cannot perform the ‘%.*ls’ operation. Please try again later.
4093916 The scale operation from service level objective ‘%.*ls’ to new service level objective ‘%.*ls’ is not supported. Please file a support ticket.
4094016The elastic pool ‘%.*ls’ cannot be updated because one of its databases is performing a copy or geo-replication failover operation.
4094116Copy operation for the database ‘%.*ls’ on the server ‘%.*ls’ cannot be started because the elastic pool ‘%.*ls’ is currently being updated.
4094216A service objective assignment operation cannot be performed because copy or failover operation for the database ‘%.*ls’ on the server ‘%.*ls’ is in progress.
4094316A Failover Group cannot be created on the server ‘%.*ls’ because the Table Auditing feature is enabled for this server.
4094416The database ‘%.*ls’ on the server ‘%.*ls’ cannot be added to a Failover Group because the Table Auditing or Security Enabled Access feature is turned on for this database.
4094516The Table Auditing feature cannot be turned on for a server that contains Failover Groups. Please try Blob Auditing instead.
4094616The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is part of a Failover Group.
4094716The 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.
4094816A Server DNS Alias cannot be created for the server ‘%.*ls’ because the Table Auditing feature is enabled for this server.
4094916A Server DNS Alias cannot be created for the server ‘%.*ls’ because the database ‘%.*ls’ has the Table Auditing or Security Enabled Access feature enabled.
4095016The Dns Alias ‘%.*ls’ already exists for the elastic pool ‘%.*ls’ on server ‘%.*ls’.
4095116The Dns Alias ‘%.*ls’ does not exist for the elastic pool ‘%.*ls’ on server ‘%.*ls’.
4095216A Server DNS Alias cannot be created because server ‘%.*ls’ would exceed the allowed Server DNS Aliases quota of %d.
4095316A Failover Group cannot be created because server ‘%.*ls’ would exceed the allowed Failover Groups quota of %d.
4095416The Table Auditing feature cannot be turned on for a server that contains Server Dns Aliases. Please try Blob Auditing instead.
4095516The operation cannot be performed due to insufficient file space in the elastic pool. The operation requires (%d) MBs file space and there are (%d) MBs file space available. Unused file space must be reclaimed before retrying the operation.  Please refer to the following article for details on reclaiming unused file space: https://go.microsoft.com/fwlink/?linkid=864775.
4095616The Server Disaster Recovery Configuration feature is deprecated. Please use Failover Group instead.
4095716The DTU min per database must be at least (%d) for service tier ‘%.*ls’.
4095816The VCore max per database must be at least (%d) for service tier ‘%.*ls’.
4095916The VCore max per database cannot exceed (%d) for service tier ‘%.*ls’.
4096016The VCore max per database (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’.
4096116The VCore min per database cannot exceed (%d) for service tier ‘%.*ls’.
4096216The VCore min per database must be at least (%d) for service tier ‘%.*ls’.
4096316The VCore min per database (%d) for the elastic pool does not belong to the allowed values for service tier ‘%.*ls’.
4096416The VCore min per database (%d) cannot exceed the VCore max per database (%d).
4096516The service level objective ‘%.*ls’ does not support the license type ‘%.*ls’.
4096616No service objective was found for capacity ‘%d’ in edition ‘%.*ls’
4096716More than one service objective was found for capacity ‘%d’ in edition ‘%.*ls’
4096816Operation results in exceeding quota limits of %d. Maximum allowed: %d.
4096916Cannot open server ‘%.*ls’ requested by the login. Client is not allowed to access the server.
4097016Can not change from ‘%.*ls’ edition to ‘%.*ls’ edition.
4097116Cannot open Failover Group “%.*ls” requested by the login. The login failed.
4097216Database copy limit per database reached. The database ‘%ls’ cannot have more than %d concurrent database copies.
4097316Can not drop database because a failover operation is in progress on the failover group.
4097416Partner region specified does not match region of partner managed instance.
4097516Partner managed instance’s DNS Zone does not match the DNS Zone of the source managed instance.
4097616Instance Failover Group cannot be created because partner managed server “%.*ls” is not empty or does not have secondaries for all databases in the primary instance  “%.*ls” .
4097716‘%.*ls’ is not a supported timezone.
4097816Instance failover group cannot be created because the reserved storage size on the secondary instance is different from the reserved storage size on the primary instance.
4097916Database is unavailable because it is paused. Server ‘%.*ls’, Database ‘%.*ls’. Please resume before trying to access the database again.
4098016Partner managed server’s managed server/failover group has been dropped.
4098116Database ‘%.*ls’ is not accessible due to Azure Key Vault critical error.
4098216Instance failover group cannot be created because the secondary instance has user databases.
4098316Replication to the partner managed instance could not be established. Verify that connectivity between the Virtual Networks of the primary and secondary managed servers has been established correctly according to guidelines in https://aka.ms/instanceFailoverGroups.
4098416Restore and GeoRestore target cannot be free database.
4098516Restore and GeoRestore are not supported for free database.
4098616Source database ‘%s’ dropped on ‘%s’ does not exist on server ‘%s’ within the supported recovery period.
4098716Source database ‘%s’ does not exist on server ‘%s’ within the supported recovery period. If restoring a dropped database, please specify its deletion date.
4098816The Hyperscale edition recovery requires both source and target databases to use VLDB service level objective.
4098916he Hyperscale edition Point-In-Time restore requires both source and target databases to use VLDB service level objective.
4099016Specifying an elastic pool and/or changing the service level objective or edition is not supported for ‘%s’ edition.
4100016Failed to obtain the local Windows Server Failover Clustering (WSFC) handle (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100116Failed 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 error code, see “System Error Codes” in the operating system documentation.
4100216Failed to obtain the local Windows Server Failover Clustering (WSFC) node handle (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100316Failed to obtain the local Windows Server Failover Clustering (WSFC) node ID (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100416Failed 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 availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name or ID is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100516Failed 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 WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource name or ID is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100616Failed to create the Windows Server Failover Clustering (WSFC) group with name ‘%s’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100716The Windows Server Failover Clustering (WSFC) group control API returned error code %d.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100816Failed to create the Windows Server Failover Clustering (WSFC) resource with name ‘%s’ and type ‘%s’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource name or type is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4100916The Windows Server Failover Clustering (WSFC) resource control API returned error code %d.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101016Failed to bring the Windows Server Failover Clustering (WSFC) group online (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101116Failed to take the Windows Server Failover Clustering (WSFC) group offline (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101216The Windows Server Failover Clustering (WSFC) node control API returned error code %d.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101316Failed to obtain the Windows Server Failover Clustering (WSFC) resource enumeration handle (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101416Failed to enumerate the Windows Server Failover Clustering (WSFC) resources (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource enumeration handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101516Failed to obtain the Windows Server Failover Clustering (WSFC) node handle (Error code %d) for node ‘%.*ls’.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster node name is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101616Failed 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 availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource or node handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101716Failed 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 availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource or node handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101816Failed 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 service may not be running or may not be accessible in its current state, or the specified cluster group or node handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4101916Failed 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 WSFC service may not be running or may not be accessible in its current state, or the specified cluster group name or ID is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102016Failed to find a String property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) resource with name or ID ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102116Failed to find a DWORD property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) resource with ID ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102216Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter %d and notification key %d (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102316The Windows Server Failover Clustering (WSFC) change handle is invalid because a WSFC notification port has not been created or has been closed.  Create a new WSFC notification port and retry the operation.
4102416Failed to register additional Windows Server Failover Clustering (WSFC) change notifications with notification filter %d and notification key %d (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102516Failed to receive Windows Server Failover Clustering (WSFC) change notifications (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102610Failed to create the Windows Server Failover Clustering (WSFC) group with name ‘%ls’.  The WSFC group with the specified name already exists.  Retry the operation with a group name that is unique in the cluster.
4102716Failed to start the Windows Server Failover Clustering (WSFC) change listener (SQLOS error code %d).  SQL Server may not have sufficient resources to start the WSFC change listener.  If the condition persists, the SQL Server instance may need to be restarted.
4102816Failed to open Windows Server Failover Clustering (WSFC) registry root key (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4102916Failed to open the Windows Server Failover Clustering (WSFC) resource registry key ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103016Failed 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 WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  If the corresponding availability group has been dropped, this error is expected.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103116Failed to create the Windows Server Failover Clustering (WSFC) registry subkey ‘%.*ls’ (Error code %d).  The parent key is %sthe cluster root key.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103216Failed to delete the Windows Server Failover Clustering (WSFC) registry subkey ‘%.*ls’ (Error code %d).  The parent key is %sthe cluster root key.  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103316Failed to retrieve the Windows Server Failover Clustering (WSFC) registry value corresponding to name ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103416Failed to set the Windows Server Failover Clustering (WSFC) registry value corresponding to name ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103516Failed to enumerate Windows Server Failover Clustering (WSFC) registry value (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103616Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name ‘%.*ls’ (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103716Failed to obtain a Windows Server Failover Clustering (WSFC) object enumeration handle for objects of type %d (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103816Failed to enumerate Windows Server Failover Clustering (WSFC) objects (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified cluster object enumeration handle is invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4103916An availability group replica already exists on the node ‘%.*ls’.  Each node can contain only one replica of an availability group.  Please choose another node to host the new replica.
4104016Failed to remove the availability group replica ‘%.*ls’ from availability group ‘%.*ls’.  The availability group does not contain a replica with the specified name.  Verify the availability group and replica names and then retry the operation.
4104116SQL Server instance to cluster node map entry cannot be found for the SQL Server instance ‘%.*ls’ and group ID ‘%.*ls’.  The specified SQL Server instance name is invalid, or the corresponding registry entry does not exist.  Verify the SQL Server instance name and retry the operation.
4104216The availability group ‘%.*ls’ already exists.  This error could be caused by a previous failed CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation.  If the availability group name you specified is correct, try dropping the availability group and then retry CREATE AVAILABILITY GROUP operation.
4104316For 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 corresponding lengths in characters.  The availability group name may be incorrect, or the availability group configuration data may be corrupt.  If this error persists, you may need to drop and recreate the availability group.
4104416Availability group name to ID map entry for availability group ‘%.*ls’ cannot be found.  The availability group name may be incorrect.  If this is a WSFC availability group, the availability group may not exist in this Windows Server Failover Cluster.  Verify the availability group exists and that the availability group name is correct and then retry the operation.
4104516Cannot add database ‘%.*ls’ to the availability group ‘%.*ls’, because there is already a database with the same name in the availability group.  Please verify that the database and availability group names specified are correct.
4104616Cannot add replica ‘%.*ls’ to the availability group ‘%.*ls’, because there is already a replica with the same name in the availability group.  Please verify the replica and availability group names specified are correct.
4104716Failed to obtain the Windows Server Failover Clustering (WSFC) node state for the local WSFC node (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4104810Always On Availability Groups: Local Windows Server Failover Clustering service has become unavailable. This is an informational message only. No user action is required.
4104910Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user action is required.
4105010Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required.
4105110Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
4105210Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required.
4105310Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
4105410Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required.
4105510Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
4105616Availability replica ‘%.*ls’ of availability group ‘%.*ls’ cannot be brought online on this SQL Server instance.  Another replica of the same availability group is already online on the node.  Each node can host only one replica of an availability group, regardless of the number of SQL Server instances on the node.  Use the ALTER AVAILABILITY GROUP command to correct the availability group configuration.  Then, if the other replica is no longer being hosted on this node, restart this instance of SQL Server to bring the local replica of the availability group online.
4105716Failed to create the Windows Server Failover Clustering (WSFC) resource with name ‘%ls’.  The WSFC resource with the specified name already exists.  Retry the operation with a resource name that is unique in the cluster.
4105810Always On: The local replica of availability group ‘%.*ls’ is starting. This is an informational message only. No user action is required.
4105910Always On: Availability group ‘%.*ls’ was removed while the availability replica on this instance of SQL Server was offline.  The local replica will be removed now. This is an informational message only. No user action is required.
4106016The Cyclic Redundancy Check (CRC) value generated for the retrieved availability group configuration data does not match that stored with the data for the availability group with ID ‘%.*ls’.  If this is a WSFC availability group, the availability group data in the WSFC store may have been modified outside SQL Server, or the data is corrupt.  If the error persists, you may need to drop and recreate the availability group.
4106110Always On: The local replica of availability group ‘%.*ls’ is stopping. This is an informational message only. No user action is required.
4106216The ID of availability group ‘%.*ls’ in local data store is inconsistent with that in the Windows Server Failover Clustering (WSFC) data store.  The availability group may have been dropped and recreated while the SQL Server instance was offline, or while the WSFC node was down.  To resolve this error, drop the availability group and then recreate it.
4106316Windows Server Failover Clustering (WSFC) detected that the availability group resource with ID ‘%.*ls’ was online when the availability group was not actually online.  The attempt to synchronize the WSFC resource state with the availability group state failed (Error code: %d).  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4106416Failed to set local node as sole preferred owner for the Windows Server Failover Clustering (WSFC) group with ID ‘%.*ls’ (Error code: %d).  The WSFC group might be in state that cannot accept the request.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4106516Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID: ‘%.*ls’) online at this time.  The WSFC resource is not in a state that can accept the request.  Wait for the WSFC resource to enter a terminal state, and retry the operation.  For information about this error, see error code 5023 in “System Error Codes” in the Windows Development documentation.
4106616Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID ‘%.*ls’) online (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the WSFC resource may not be in a state that could accept the request.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4106716Cannot 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 the request.  Please wait for the WSFC group to enter a terminal state and then retry the operation.  For information about this error, see error code 5023 in “System Error Codes” in the Windows Development documentation.
4106816Failed to enumerate the Windows Server Failover Clustering (WSFC) registry key (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4106916The existence of availability group data for the availability group ‘%.*ls’ in the Windows Server Failover Clustering (WSFC) store could not be determined.  The local WSFC node may be down, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation has failed.  Please use DROP AVAILABILITY GROUP command to clean up previously failed operations.  Verify that the local WSFC node is up before retrying the operation.
4107016Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID ‘%.*ls’ is not found in the WSFC data store.  The availability group may have been dropped, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation has failed.  Please use DROP AVAILABILITY GROUP command to clean up previously failed operations before retrying the current operation.
4107116Cannot read the persisted configuration of Always On availability group with corresponding resource ID ‘%.*ls’.  The persisted configuration is written by a higher-version SQL Server that hosts the primary availability replica.  Upgrade the local SQL Server instance to allow the local availability replica to become a secondary replica.
4107216The ID of availability group ‘%.*ls’ in local data store does not exist in the Windows Server Failover Clustering (WSFC) data store.  The availability group may have been dropped but the current WSFC node was not notified.  To resolve this error, try to recreate the availability group.
4107316The database ‘%.*ls’ cannot be removed from availability group ‘%.*ls’.  This database does not belong to the availability group.
4107410Always On: The local replica of availability group ‘%.*ls’ is preparing to transition to the primary role. This is an informational message only. No user action is required.
4107510Always On: The local replica of availability group ‘%.*ls’ is preparing to transition to the resolving role. This is an informational message only. No user action is required.
4107610Always On: Availability group ‘%.*ls’ is going offline because it is being removed. This is an informational message only. No user action is required.
4107716Cannot 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 the request.  Please wait for the WSFC group to enter a terminal state and then retry the operation.  For information about this error, see error code 5023 in “System Error Codes” in the Windows Development documentation.
4107816Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name ‘%.*ls’, because a registry entry with the specified name does not exist.  Check that the registry value name is correct, and retry the operation.
4107916Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name ‘%.*ls’), because the WSFC group does not exist.  Specify a valid WSFC group ID or name and retry the operation.  For information about this error, see error code 5013 in “System Error Codes” in the Windows Development documentation.
4108016Failed to delete SQL Server instance name to Windows Server Failover Clustering node name map entry for the local availability replica of availability group ‘%.*ls’.  The operation encountered SQL Server error %d and has been terminated.  Refer to the SQL Server error log for details about this SQL Server error and corrective actions.
4108116Failed to destroy the Windows Server Failover Clustering group corresponding to availability group ‘%.*ls’.  The operation encountered SQL Server error %d and has been terminated.  Refer to the SQL Server error log for details about this SQL Server error and corrective actions.
4108216Failed 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 running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4108316Failed 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 accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4108416The Windows Server Failover Clustering (WSFC) cluster control API returned error code %d. If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4108516Failed to find a DWORD property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) (Error code %d).  If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid.  Otherwise, contact your primary support provider.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
4108616Failed to retrieve the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whether the ‘HKLM\Cluster\PaxosTag’ registry value exists in the WSFC registry hive.
4108716Error in parsing the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whether the ‘HKLM\Cluster\PaxosTag’ is in the format outlined in the Microsoft Knowledge Base article KB 947713 (“The implications of using the /forcequorum switch to start the Cluster service in Windows Server 2008”).
4108816Failed to determine if the Windows Server Failover Clustering (WSFC) service is in Force Quorum state. The prerequisite hotfix, KB 2494036, might not yet be installed on your Windows Server 2008/Windows Server 2008 R2 systems. For more information, see Microsoft Knowledge Base article KB 2494036 (“A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2”).
4108910Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user action is required.
4109010Failed to update Replica status due to exception %d.
4109110Always On: The local replica of availability group ‘%.*ls’ is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
4109210Always On: The availability replica manager is going offline because %ls. This is an informational message only. No user action is required.
4109310Always On: The local replica of availability group ‘%.*ls’ is going offline because the corresponding resource in the Windows Server Failover Clustering (WSFC) cluster is no longer online. This is an informational message only. No user action is required.
4109410Always On: The local replica of availability group ‘%.*ls’ is restarting because the existing primary replica restarted or the availability group failed over to a new primary replica. This is an informational message only. No user action is required.
4109510Always On: Explicitly transitioning the state of the Windows Server Failover Clustering (WSFC) resource that corresponds to availability group ‘%.*ls’ to Failed. The resource state is not consistent with the availability group state in the instance of SQL Server.  The WSFC resource state indicates that the local availability replica is the primary replica, but the local replica is not in the primary role. This is an informational message only. No user action is required.
4109610Always On: The local replica of availability group ‘%.*ls’ is being removed. The instance of SQL Server failed to validate the integrity of the availability group configuration in the Windows Server Failover Clustering (WSFC) store.  This is expected if the availability group has been removed from another instance of SQL Server. This is an informational message only. No user action is required.
4109710Always On: The local replica of availability group ‘%.*ls’ is going offline. This replica failed to read the persisted configuration because of a version mismatch. This is an informational message only. No user action is required.
4109810Always On: The local replica of availability group ‘%.*ls’ is restarting, because it failed to read the persisted configuration. This is an informational message only. No user action is required.
4109910Always On: The local replica of availability group ‘%.*ls’ is going offline. This replica failed to read the persisted configuration, and it has exhausted the maximum for restart attempts. This is an informational message only. No user action is required.
4110016The availability group ‘%.*ls’ and/or its local availability replica does not exist.  Verify that the specified availability group name is correct, and that the local availability replica has joined the availability group, then retry the operation.
4110116The availability group with Windows Server Failover Clustering resource ID ‘%.*ls’ and/or its local availability replica does not exist.  Verify that the specified availability resource ID is correct, and that the local availability replica has joined the availability group, then retry the operation.
4110210Failed to persist configuration data of availability group ‘%.*ls’.  The local availability replica either is not the primary replica or is shutting down.
4110310Startup of the Always On Availability Replica Manager has been terminated, because the ‘FixQuorum’ property of Windows Server Failover Clustering (WSFC) is not present. The prerequisite Hotfix, KB 2494036, might not yet be installed on your Windows Server 2008/Windows Server 2008 R2 systems. For more information, see Microsoft Knowledge Base article KB 2494036 (“A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2”).
4110416Failover of the availability group ‘%.*ls’ to the local replica failed because the availability group resource did not come online due to a previous error. To identify that error, check the SQL Server error log, cluster logs and system event logs. For information about how to view events and logs for a Windows Server Failover Clustering (WSFC) cluster, see Windows Server documentation.
4110516Failed to create the Windows Server Failover Clustering (WSFC) resource with name ‘%s’ and type ‘%s’.  The resource type is not registered in the WSFC cluster.  The WSFC cluster many have been destroyed and created again.  To register the resource type in the WSFC cluster, disable and then enable Always On in the SQL Server Configuration Manager.
4110616Cannot create an availability replica for availability group ‘%.*ls’.  An availability replica of the specified availability group already exists on this instance of SQL Server.  Verify that the specified availability group name is correct and unique, then retry the operation.  To remove the existing availability replica, run DROP AVAILABILITY GROUP command.
4110716Availability group ‘%.*ls’ failed to create necessary events for the WSFC Lease mechanism. Windows returned error code (%d) when obtaining handles for Lease events. Resolve the windows error and retry the availability group operation.
4110816An error occurred while removing availability group ‘%.*ls’. The DROP AVAILABILITY GROUP command removed the availability group configuration from the local metadata. However, the attempt to remove this configuration from the Windows Server Failover Clustering (WSFC) cluster failed because the Always On Availability Groups manager is not online (SQL Server error: %d). To remove the availability group configuration from the WSFC cluster, re-enter the command.
4110917Could 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 on resources. Check the SQL Server error log to determine the cause of the failure. Retry the operation later, and if this condition persists, contact your database administrator.
4111010Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
4111110Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
4111216A Windows Server Failover Clustering (WSFC) API required by availability groups has not been loaded. Always On Availability Groups replica manager is not enabled on the local instance SQL Server. If the server instance is running an edition of SQL Server that supports Always On Availability Groups, you can enable the it by using the SQL Server Configuration Manager.
4111316Cannot failover availability group ‘%.*ls’ to this instance of SQL Server because a failover command is already pending on the local replica of this availability group.  Wait for the pending failover command to complete before issuing another command on the local replica of this availability group.
4111416Cannot create an availability group named ‘%.*ls’ because it already exists in a system table.
4111516Cannot create the availability group named ‘%.*ls’ because its availability group ID (ID: ‘%.*ls’) already exists in a system table.
4111616Cannot create an availability group named ‘%.*ls’ with replica ID ‘%.*ls’ because this ID already exists in a system table.
4111716Cannot map local database ID %d to the availability database ID ‘%.*ls’ within availability group ‘%.*ls’. This database is already mapped to an availability group.
4111816Cannot map database ID %d to the availability database ID ‘%.*ls’ within availability group ‘%.*ls’. Another local database, (ID %d). is already mapped to this availability database.
4111916Could not find the availability group ID %d in the system table.
4112016Failed to start task to process a down notification for the local Windows Server Failover Clustering (WSFC) node (SQL OS error: %d). Possible causes are no worker threads are available or there is insufficient memory. Check the state of the local WSFC node. If this problem persists, you might need to restart the instance of SQL Server.
4112110The local availability replica of availability group ‘%.*ls’ cannot accept signal ‘%s’ in its current replica role, ‘%s’, and state (configuration is %s in Windows Server Failover Clustering store, local availability replica has %s joined).  The availability replica signal is invalid given the current replica role.  When the signal is permitted based on the current role of the local availability replica, retry the operation.
4112216Cannot failover availability group ‘%.*ls’ to this instance of SQL Server.  The local availability replica is already the primary replica of the availability group.  To failover this availability group to another instance of SQL Server, run the failover command on that instance of SQL Server.  If local instance of SQL Server is intended to host the primary replica of the availability group, then no action is required.
4112316Cannot bring the Windows Server Failover Clustering (WSFC) group (ID ‘%.*ls’) online at this time.  The WSFC group is moving to another node.  Please wait for the WSFC group to complete the move operation and then retry the command.  For information about this error, see error code 5908 in “System Error Codes” in the Windows Development documentation.
4112416The availability replica for availability group ‘%.*ls’ on this instance of SQL Server cannot become the primary replica because the availability group is being dropped.
4112516The availability replica for availability group ‘%.*ls’ on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).
4112616Operation on the local availability replica of availability group ‘%.*ls’ failed.  The local copy of the availability group configuration does not exist or has not been initialized.  Verify that the availability group exists and that the local copy of the configuration is initialized, and retry the operation.
4112716Attempt to set database mapping state where the local database id %d is not mapped to any availability group.
4112816Failed to perform database operation ‘%s’ on database ‘%.*ls’ (ID %d) in availability group ‘%.*ls’.  The database might be in an incorrect state for the operation.  If the problem persists, you may need to restart the SQL Server instance.
4112916Failed to schedule or execute database operation ‘%s’ on database ‘%.*ls’ (Database ID: %d) in availability group ‘%.*ls’ (SQL OS error: %d).  The instance of SQL Server may have insufficient resources to carry out the database operation. If the problem persists, you might need to restart the server instance.
4113016Operation ‘%s’ on a database ‘%.*ls’ (Database ID: %d) in availability group ‘%.*ls’ failed with SQL Server error %d (Error details: “%.*ls”).  The operation has been rolled back.  See previous error messages in the SQL Server error log for more details. If the problem persists, you might need to restart the instance of SQL Server.
4113110Failed to bring availability group ‘%.*ls’ online.  The operation timed out. If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online. Then verify that the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.
4113216Cannot join database ‘%.*ls’ to availability group ‘%.*ls’.  The specified database does not belong to the availability group.  Verify the names of the database and the availability group, and retry the command specifying the correct names.
4113310Cannot remove database ‘%.*ls’ from availability group ‘%.*ls’.  Either the database does not belong to the availability group, or the database has not joined the group. Verify the database and availability group names, and retry the command.
4113416Cannot bring the availability group ‘%.*ls’ online.  The local instance was not the previous primary replica when the availability group went offline, not all databases are synchronized, and no force failover command was issued on the local availability replica.  To designate the local availability replica as the primary replica of the availability group, run the force failover command on this instance of SQL Server.
4113510Startup 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 error log for the preceding error.
4113616Failed to join the availability replica to availability group ‘%.*ls’ because the group is not online.  Either bring the availability group online, or drop and recreate it. Then retry the join operation.
4113710Abandoning a database operation ‘%ls’ on availability database ‘%.*ls’ of availability group ‘%.*ls’.  The sequence number of local availability replica has changed (Previous sequence number: %u, current sequence number: %u).  This is an informational message only. No user action is required.
4113817Cannot accept Always On Availability Groups operation operation on database ‘%.*ls’ of availability group ‘%.*ls’.  The database is currently processing another operation that might change the database state. Retry the operation later. If the condition persists, contact the database administrator.
4113910Failed to set database information for availability group %.*ls.  The local availability replica is not the primary replica, or it is shutting down.  This is an informational message only. No user action is required.
4114016Availability group ‘%.*ls’ cannot process the ALTER AVAILABILITY GROUP command, because the local availability replica is not the primary replica.  Connect to the server instance that is currently hosting the primary replica of this availability group, and rerun the command.
4114116Failed to set availability group database information for availability group %.*ls.  The local availability replica is not the primary, or is shutting down.  This is an informational message only. No user action is required.
4114216The availability replica for availability group ‘%.*ls’ on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group. If the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss). For more information, see SQL Server Books Online.
4114316Cannot process the operation.  The local replica of availability Group ‘%.*ls’ is in a failed state.  A previous operation to read or update persisted configuration data for the availability group has failed.  To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
4114416The local availability replica of availability group ‘%.*ls’ is in a failed state.  The replica failed to read or update the persisted configuration data (SQL Server error: %d).  To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
4114510Cannot join database ‘%.*ls’ to availability group ‘%.*ls’.  The database has already joined the availability group.  This is an informational message.  No user action is required.
4114616Failed to bring Availability Group ‘%.*ls’ online.  If this is a WSFC availability group, the Windows Server Failover Clustering (WSFC) service may not be running, or it may not be accessible in its current state.  Please verify the local WSFC node is up and then retry the operation.  Otherwise, contact your primary source provider.
4114710Always On Availability Groups was not started because %ls.  This is an informational message.  No user action is required.
4114816Cannot add or join database ‘%.*ls’ to availability group ‘%.*ls’.  The database does not exist on this instance of SQL Server.  Verify the database name and that the database exists on the server instance.  Then retry the operation, specifying the correct database name.
4114916Operation on the availability group ‘%.*ls’ has been cancelled or terminated, either because of a connection timeout or cancellation by user.  This is an informational message.  No user action is required.
4115016Failed to take availability group ‘%.*ls’ offline.  If this is a WSFC availability group, the Windows Server Failover Clustering (WSFC) service may not be running, or it may not be accessible in its current state.  Verify the local WSFC node is up and then retry the operation.  Otherwise, contact your primary support provider.
4115116Error accessing the Availability Groups manager.  The local Availability Groups manager has not been initialized.  Wait until the Availability Groups manager is in a state that allows access, and retry the operation.
4115216Failed to create availability group ‘%.*ls’.  The operation encountered SQL Server error %d and has been rolled back.  Check the SQL Server error log for more details.  When the cause of the error has been resolved, retry CREATE AVAILABILITY GROUP command.
4115316Failed to create availability group ‘%.*ls’.  The operation encountered SQL Server error %d.  An attempt to roll back the operation failed.  Check the SQL Server error log for more details.  Then execute the DROP AVAILABILITY GROUP command to clean up any metadata that might remain from the failed attempt to create the availability group.
4115416Cannot failover availability group ‘%.*ls’ to this SQL Server instance.  The availability group is still being created.  Verify that the specified availability group name is correct.  Wait for CREATE AVAILABILITY GROUP command to finish, then retry the operation.
4115516Cannot failover availability group ‘%.*ls’ to this instance of SQL Server.  The availability group is being dropped.  Verify that the specified availability group name is correct.  The availability group may need to be recreated if the drop operation was unintentional.
4115616Cannot drop availability group ‘%.*ls’ from this instance of SQL Server.  The availability group is either being dropped, or the local availability replica is being removed from the availability group.  Verify that the specified availability group name is correct.  Wait for the current operation to complete, then retry the command if necessary.
4115716Cannot remove the local availability replica from availability group ‘%.*ls’ from this instance of SQL Server.  The availability group is either being dropped, or the local availability replica is being disjoined.  Verify that the specified availability group name is correct.  Wait for the current operation to complete, then retry the command if necessary.
4115816Failed to join local availability replica to availability group ‘%.*ls’.  The operation encountered SQL Server error %d and has been rolled back.  Check the SQL Server error log for more details.  When the cause of the error has been resolved, retry the ALTER AVAILABILITY GROUP JOIN command.
4115916Failed to join local availability replica to availability group ‘%.*ls’.  The operation encountered SQL Server error %d.  An attempt to rollback the operation failed.  Check SQL Server error log for more details.  Run DROP AVAILABILITY GROUP command to clean up any metadata that might remain from the availability group.
4116016Failed to designate the local availability replica of availability group ‘%.*ls’ as the primary replica.  The operation encountered SQL Server error %d and has been terminated.  Check the preceding error and the SQL Server error log for more details about the error and corrective actions.
4116116Failed to validate the Cyclic Redundancy Check (CRC) of the configuration of availability group ‘%.*ls’.  The operation encountered SQL Server error %d, and the availability group has been taken offline to protect its configuration and the consistency of its joined databases.  Check the SQL Server error log for more details.  If configuration data corruption occurred, the availability group might need to be dropped and recreated.
4116216Failed to validate sequence number of the configuration of availability group ‘%.*ls’.  The in-memory sequence number does not match the persisted sequence number.  The availability group and/or the local availability replica will be restarted automatically.  No user action is required at this time.
4116316An error occurred while waiting for the local availability replica of availability group ‘%.*ls’ to transition to the primary role.  The operation encountered SQL OS error %d and has been terminated.  Verify that the availability group is in the correct state for the command.  If this is a Windows Server Failover Clustering (WSFC) availability group, also verify that the WSFC cluster is in the correct state for the command.  Then retry the command.
4116416An error occurred while waiting for the local availability replica of availability group ‘%.*ls’ to transition to the resolving role.  The operation encountered SQL OS error %d and has been terminated.  Verify that the availability group is in the correct state for the command.  If this is a Windows Server Failover Clustering (WSFC) availability group, also verify that the WSFC cluster is in the correct state for the command.  Then retry the command.
4116516A timeout error occurred while waiting to access the local availability replica of availability group ‘%.*ls’.  The availability replica is currently being accessed by another operation.  Wait for the in-progress operation to complete, and then retry the command.
4116616An error occurred while waiting to access the local availability replica of availability group ‘%.*ls’.  The operation encountered SQL OS error %d, and has been terminated.  Verify that the local availability replica is in the correct state, and then retry the command.
4116716An error occurred while attempting to access availability replica ‘%.*ls’ in availability group ‘%.*ls’.  The availability replica is not found in the availability group configuration.  Verify that the availability group and availability replica names are correct, then retry the command.
4116816An error occurred while attempting to access availability replica with ID ‘%.*ls’ in availability group ‘%.*ls’.  The availability replica is not found in the availability group configuration.  Verify that the availability group name and availability replica ID are correct, then retry the command.
4116916An error occurred while attempting to access the availability group database with ID ‘%.*ls’ in availability group ‘%.*ls’.  The availability database is not found in the availability group configuration.  Verify that the availability group name and availability database ID are correct, then retry the command.
4117010Post-online processing for availability group ‘%.*ls’ has been terminated.  Either post-online processing has already completed, the local availability replica is no longer the primary replica, or the availability group is being dropped.  This is an informational message.  No user action is required.
4117116Failed to create availability group ‘%.*ls’, because a Windows Server Failover Cluster (WSFC) group with the specified name already exists.  The operation has been rolled back successfully.  To retry creating an availability group, either remove or rename the existing WSFC group, or retry the operation specifying a different availability group name.
4117216An error occurred while dropping availability group ‘%.*ls’.  The operation encountered SQL OS error %d, and has been terminated.  Verify that the specified availability group name is correct, and then retry the command.
4117316An error occurred while removing the local availability replica from availability group ‘%.*ls’.  The operation encountered SQL OS error %d, and has been terminated.  Verify that the specified availability group name is correct, and then retry the command.
4117410Failed to start the task of the Windows Server Failover Clustering (WSFC) event notification worker (SQL OS error: %d).  If the problem persists, you might need to restart the instance of SQL Server.
4117510Failed 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 Server.
4117610Failed to acquire exclusive access to local availability group configuration data (SQL OS error: %d).  If the problem persists, you might need to restart the instance of SQL Server.
4117716The availability replica of the specified availability group ‘%.*ls’ is being dropped.  Wait for the completion of the drop command and retry the operation later.
4117816Cannot drop availability group ‘%.*ls’ from this SQL Server instance.  The availability group is currently being created.  Verify that the specified availability group name is correct.  Wait for the current operation to complete, then retry the command if necessary.
4117916Cannot remove the local availability replica from availability group ‘%.*ls’ from this instance of SQL Server.  The availability group is currently being created.  Verify that the specified availability group name is correct.  Wait for the current operation to complete, and then retry the command if necessary.
4118016Attempt to access non-existent or uninitialized availability group with ID ‘%.*ls’.  This is usually an internal condition, such as the availability group is being dropped or the local WSFC node has lost quorum. In such cases, and no user action is required.
4118116The local availability replica of availability group ‘%.*ls’ did not become primary.  A concurrent operation may have changed the state of the availability group in Windows Server Failover Cluster.  Verify that the availability group state in Windows Server Failover Cluster is correct, then retry the operation.
4118216Failed to set the local availability replica of availability group ‘%.*ls’ as joined in Windows Server Failover Clustering (WSFC) database.  Either the local availability replica is no longer the primary, or the WSFC service is not accessible.  Verify that the local WSFC node is online, and that the local availability replica is the primary replica.  Then retry the operation.
4118316Failed to modify availability replica options for availability group ‘%.*ls’.  Before the availability group configuration could be updated, the operation encountered SQL Server error %d.  The operation has been rolled back.  Refer to the SQL Server error log for more information.  If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online, and retry the command.  Otherwise, contact your primary support provider.
4118416Failed to modify availability replica options for availability group ‘%.*ls’.  The availability group configuration has been updated.  However, the operation encountered SQL Server error %d while applying the new configuration to the local availability replica.  The operation has been terminated.  Refer to the SQL Server error log for more information.  If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online.  Use the ALTER AVAILABILITY GROUP command to undo the changes made to the availability group configuration.
4118510Replica option specified in ALTER AVAILABILITY GROUP ‘%.*ls’ MODIFY DDL is same is cached availability group configuration.
4118616Availability group ‘%.*ls’ cannot process an ALTER AVAILABILITY GROUP command at this time.  The availability group is still being created.  Verify that the specified availability group name is correct.  Wait for CREATE AVAILABILITY GROUP command to finish, and then retry the operation.
4118716Availability group ‘%.*ls’ cannot process an ALTER AVAILABILITY GROUP command at this time.  The availability group is being dropped.  Verify that the specified availability group name is correct.  The availability group may need to be recreated if it was dropped unintentionally.
4118816Availability group ‘%.*ls’ failed to process %s-%s command.  The operation encountered SQL Server error %d before the availability group configuration could be updated, and has been rolled back.  Refer to the SQL Server error log for details.  If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online, and then retry the command.  Otherwise, contact your primary support provider.
4118916Availability group ‘%.*ls’ failed to process the %s-%s command.  The availability group configuration has been updated.  However, the operation encountered SQL Server error %d while applying the new configuration to the local availability replica, and has been terminated.  Refer to the SQL Server error log for details .  If this is a Windows Server Failover Clustering (WSFC) availability group, verify that the local WSFC node is online.  Use an ALTER AVAILABILITY GROUP command to undo the changes to the availability group configuration.
4119016Availability group ‘%.*ls’ failed to process %s-%s command.  The local availability replica is not in a state that could process the command.  Verify that the availability group is online and that the local availability replica is the primary replica, then retry the command.
4119116The local availability replica of availability group ‘%.*ls’ cannot become the primary replica.  The last-known primary availability replica is of a higher version than the local availability replica.  Upgrade the local instance of SQL Server to the same or later version as the server instance that is hosting the current primary availability replica, and then retry the command.
4119217Creating and scheduling a worker task for Always On Availability Groups failed due to lack of resources (SQL OS error %d).   Processing of new actions might be delayed or stalled until the resource limits are resolved. Reduce the memory or thread count on the instance of SQL Server to allow new threads to get scheduled.  If new tasks are scheduled the problem might resolve itself. However, if the problem persists, you might need to restart the local instance of SQL Server.
4119310Cannot join database ‘%.*ls’ to availability group ‘%.*ls’.  The database is in the process of being removed from the availability group.  When the remove-database operation completes, the database will no longer be joined to the availability group.  Then retry the join-database command.
4119416An error occurred while waiting for the local availability replica for availability group ‘%.*ls’ to complete post-online work.  The operation encountered SQL OS error %d and has been terminated.  Verify that the availability group is in the correct state for the command.  If this is a Windows Server Failover Clustering (WSFC) availability group, also verify that the WSFC cluster is in the correct states for the command.  Then retry the command.
4119516Availability group ‘%.*ls’ failed to process the WSFC lease-renewal command. The local availability replica lease is no longer valid to process the lease renewal command. Availability replica lease expired. This is an informational message only. No user action is required.
4119616Failed to create availability group ‘%.*ls’, because a Windows Server Failover Cluster (WSFC) group with the specified name already exists.  An attempt to rollback the operation failed.  Check the SQL Server error log for more details.  To manually clean up the partially created availability group, run the DROP AVAILABILITY GROUP command.  Reenter your CREATE AVAILABILITY GROUP command specifying a unique availability group name.
4119715The FAILOVER_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying a failover mode for the replica.
4119815The AVAILABILITY_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying an availability mode for the replica.
4119916The specified command is invalid because the Always On Availability Groups %ls feature is not supported by this edition of SQL Server. For information about features supported by the editions of SQL Server, see SQL Server Books Online.
4120116The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support remote data sources.
4120216The source table ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function doesn’t have a full-text index that uses the STATISTICAL_SEMANTICS option.  A full-text index using the STATISTICAL_SEMANTICS option is required to use this function.
4120316The column ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function is not full-text indexed with the STATISTICAL_SEMANTICS option.  The column must be full-text indexed using the STATISTICAL_SEMANTICS option to be used in this function.
4120416The source_key parameter is required in the SEMANTICSIMILARITYTABLE function.
4120510Error %d occurred during semantic index population for table or indexed view ‘%.*ls’ (table or indexed view ID %d, database ID %d, document ID %d)
4120610An ALTER FULLTEXT INDEX statement cannot remove the ‘STATISTICAL_SEMANTICS’ option from the last column in the index that has the option set when a “WITH NO POPULATION” clause is specified. Remove the “WITH NO POPULATION” clause.
4120710A 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 corresponding language statistics has been installed.
4120810Warning: The population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) encountered a document with full-text key value ‘%ls’ that specifies a language not supported for semantic indexing. Some columns of the row will not be part of the semantic index.
4120910A semantic language statistics database is not registered. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
4121010The semantic language statistics database is not accessible or not valid. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
4121116A semantic language statistics database is already registered.
4121216No semantic language statistics database is registered.
4121316The database ‘%.*ls’ does not exist or the database format is not valid. Provide a valid semantic language statistics database name.
4121416An error occurred while trying to register the semantic language statistics database.
4121516The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support update or insert.
4121616The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support common table expressions.
4130016The current transaction cannot be committed and cannot support read or write operations. Roll back the transaction.
4130117A transaction dependency failure occurred, and the current transaction can no longer commit. Please retry the transaction.
4130216The current transaction attempted to update a record that has been updated since this transaction started. The transaction was aborted.
4130316The bucket count for a hash index must be a positive integer not exceeding %d.
4130410The current value of option ‘%.*ls’ for table ‘%.*ls’, index ‘%.*ls’ is %d.
4130517The current transaction failed to commit due to a repeatable read validation failure.
4130616The nesting limit of %d for conditional blocks and exception blocks, for natively compiled modules, has been exceeded. Please simplify the module.
4130710Warning: 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 earlier. Please simplify the table definition.
4130821The database ID %d already exists.
4130916Unable to load the compiled DLL for database ID %d.
4131016A file with an invalid format was detected. Check the SQL Server error log for more details.
4131116File error during C code generation. The error code was %d.
4131216Unable to call into the C compiler. GetLastError = %d.
4131316The C compiler encountered a failure. The exit code was %d.
4131416Conversion of default value for parameter ‘%.*ls’ failed. Unable to create stored procedure ‘%.*ls’.
4131516Checkpoint operation failed in database ‘%.*ls’.
4131616Restore operation failed for database ‘%.*ls’ with internal error code ‘0x%08lx’.
4131716A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases model and msdb, and it cannot write to master.
4131816Memory optimized tables and natively compiled modules cannot be accessed from within SQLCLR stored procedures.
4131916A maximum of %d predicates are allowed in the WHERE clauses of queries in natively compiled modules.
4132016EXECUTE AS clause is required, and EXECUTE AS CALLER is not supported, with natively compiled modules.
4132116The memory optimized table ‘%.*ls’ with DURABILITY=SCHEMA_AND_DATA must have a primary key.
4132216MAT/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 was 0x%x.
4132316The table type ‘%ls’ is not a memory optimized table type and cannot be used in a natively compiled module.
4132416The memory optimized table variable ‘%.*ls’ cannot be used in a batch with a ‘USE’ statement.
4132517The current transaction failed to commit due to a serializable validation failure.
4132616Memory optimized tables cannot be created in system databases.
4132716The memory optimized table ‘%.*ls’ must have at least one index or a primary key.
4132816A floating point operation has overflowed.
4132916Unsupported operation following a transaction dependency failure. Parameters and variables cannot be accessed in the CATCH block and the CATCH block must raise an exception following a dependency failure.
4133016Create database operation failed for database ‘%.*ls’.
4133117The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. Roll back the transaction.
4133216Memory optimized tables and natively compiled modules cannot be accessed or created when the session TRANSACTION ISOLATION LEVEL is set to SNAPSHOT.
4133316The following transactions must access memory optimized tables and natively compiled modules under snapshot isolation: RepeatableRead transactions, Serializable transactions, and transactions that access tables that are not memory optimized in RepeatableRead or Serializable isolation.
4133416The code generation directory cannot be created or set up correctly.
4133516Modifying the collation of a database is not allowed when the database contains memory optimized tables or natively compiled modules.
4133716Cannot create %S_MSG. To create %S_MSG, the database must have a MEMORY_OPTIMIZED_FILEGROUP that is online and has at least one container.
4133816An invalid version of a data file was detected. Check the SQL Server error log for more details.
4133916The table ‘%.*ls’ has been created or altered after the start of the current transaction. The transaction was aborted. Please retry the transaction.
4134016The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated.
4134116Table ‘%.*ls’ is not yet available on the secondary replica.
4134216The model of the processor on the system does not support creating %.*ls. This error typically occurs with older processors. See SQL Server Books Online for information on supported models.
4134316In-Memory OLTP hot switch to primary replica for database ‘%.*ls’ failed.
4134416RESTORE DATABASE WITH PARTIAL requires the MEMORY_OPTIMIZED_DATA filegroup if the backup contains a MEMORY_OPTIMIZED_DATA filegroup.
4134516The key size limit of %d bytes for nonclustered indexes on memory optimized tables has been exceeded. Please simplify the index definition.
4134616CREATE and UPDATE STATISTICS for memory optimized tables do not support the WHERE clause.
4134716A BACKUP or RESTORE DATABASE statement that includes the primary filegroup must include the MEMORY_OPTIMIZED_DATA filegroup, and vice versa.
4134816MEMORY_OPTIMIZED_DATA filegroups cannot be used with the FILESTREAM_ON clause. Specify a FILESTREAM filegroup.
4134910Warning: Encryption was enabled for a database that contains one or more memory optimized tables with durability SCHEMA_AND_DATA. The data in these memory optimized tables will not be encrypted.
4135010Warning: A memory optimized table with durability SCHEMA_AND_DATA was created in a database that is enabled for encryption. The data in the memory optimized table will not be encrypted.
4135116An error occurred while processing the log. The log version is unsupported.
4135216The operation on database ID %d cannot complete because the database is in use.
4135316The operation on database ID %d cannot complete because the database is being dropped or being taken offline.
4135421The XTP background checkpoint thread encountered an unrecoverable error (‘%ls’) for database ‘%.*ls’. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.
4135521An XTP checkpoint operation encountered an error (‘%ls’) while processing log record ID %S_LSN for database ‘%.*ls’. Checkpoint processing has terminated.
4135616Filegroups with MEMORY_OPTIMIZED_DATA can only be created in 64-bit installations of SQL Server.
4135716Tables with MEMORY_OPTIMIZED=ON can only be created in 64-bit installations of SQL Server.
4135816Stored procedures with NATIVE_COMPILATION can only be created in 64-bit installations of SQL Server.
4135916A query that accesses memory optimized tables using the READ COMMITTED isolation level, cannot access disk based tables when the database option READ_COMMITTED_SNAPSHOT is set to ON. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).
4136016Default MEMORY_OPTIMIZED_DATA filegroup is not available in database ‘%.*ls’.
4136116The READ_ONLY property of a MEMORY_OPTIMIZED_DATA filegroup cannot be modified.
4136216FILESTREAM container ‘%.*ls’ cannot be added. Either the server is out of memory or the container path is too long.
4136316Only the owner of database ‘%.*ls’ or users with valid permission can execute the stored procedure ‘%.*ls’.
4136416Stored procedure ‘%.*ls’ can only be executed on a database that has an online MEMORY_OPTIMIZED_DATA filegroup.
4136516Merge request for transaction range [%ld, %ld] on database ‘%.*ls’ was not scheduled. The checkpoint files represented by the range either cannot be merged, or the checkpoint files are already part of an existing merge operation.
4136616Merge operation failed because the requested transaction id range is invalid.
4136716Failed to complete merge operation for transaction range [%ld, %ld] for database ‘%.*ls’.  Error was 0x%08x.
4136816Accessing memory optimized tables using the READ COMMITTED isolation level is supported only for autocommit transactions. It is not supported for explicit or implicit transactions. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).
4136916Merge operations cannot be requested on a secondary replica.
4137016Resource pool ‘%.*ls’ does not exist or resource governor has not been reconfigured.
4137116Binding to a resource pool is not supported for system database ‘%.*ls’. This operation can only be performed on a user database.
4137216Database ‘%.*ls’ is currently bound to a resource pool. A database must be unbound before creating a new binding.
4137316Database ‘%.*ls’ cannot be explicitly bound to the resource pool ‘%.*ls’. A database can only be bound to a user resource pool.
4137416Database ‘%.*ls’ does not have a binding to a resource pool.
4137516A binding has been created. Take database ‘%.*ls’ offline and then bring it back online to begin using resource pool ‘%.*ls’.
4137616Only members of the fixed sysadmin role can execute the stored procedure ‘%ls’.
4137716The natively compiled module with database ID %ld and object ID %ld has not been executed. Query execution statistics collection can only be enabled if the module has been executed at least once since creation or last database restart.
4137816Both @database_id and @xtp_object_id should be specified to enable or retrieve status of query level statistics collection for a procedure.
4137916Restore operation failed for database ‘%.*ls’ due to insufficient memory in the resource pool ‘%ls’. Close other applications to increase the available memory, ensure that both SQL Server memory configuration and resource pool memory limits are correct and try again. See ‘http://go.microsoft.com/fwlink/?LinkID=507574’ for more information.
4138021Databases with a MEMORY_OPTIMIZED_DATA filegroup are only supported in 64-bit editions of SQL Server.
4138121The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions.
4138216Failure adding a container to a MEMORY_OPTIMIZED_DATA filegroup. Possible causes  include the server being out of memory and the container path being too long.
4138316An internal error occurred while running the DMV query. This was likely caused by concurrent DDL operations. Please retry the query.
4138416Database ‘%.*ls’ has exceeded the maximum number of XTP checkpoint files, and can no longer support write operations in durable memory-optimized tables. For more information, contact Customer Support Services.
4138516A memory-optimized table cannot be enabled for Change Data Capture (CDC).
4138616Filegroups with MEMORY_OPTIMIZED_DATA, memory-optimized tables and natively compiled modules are not supported when lightweight pooling is enabled. Disable lightweight pooling in order to use memory-optimized features.
4138710Disallowing page allocations for database ‘%.*ls’ due to insufficient memory in the resource pool ‘%ls’. See ‘http://go.microsoft.com/fwlink/?LinkId=510837’ for more information.
4138816An upgrade operation failed for database ‘%.*ls’. Check the error log for additional details.
4138916Failed to create a backup file collection snapshot necessary for backup of database ‘%.*ls’. Check the error log for additional details.
4139016Failed to get checkpoint file information necessary for backup of database ‘%.*ls’. Check the error log for additional details.
4139123Backup of database ‘%.*ls’ detected a missing MEMORY_OPTIMIZED_DATA file with ID ‘%.*ls’.
4139216Cannot ALTER a natively compiled module into a non-native module. Include WITH NATIVE_COMPILATION or drop and recreate the module.
4139316Cannot ALTER a non-native module into a natively compiled module. Omit WITH NATIVE_COMPILATION or drop and recreate the module.
4139416TEXTSIZE must be a number between -1 and 2147483647.
4139510Rebuilding the log file is not supported for databases containing memory-optimized tables.
4139616The sort operation exceeded the buffer limit. The stored procedure execution was aborted. Consult SQL Server Books Online for more information.
4139716The TOP operator can return a maximum of %d sorted rows. %d was requested. Reduce the number of rows selected or simplify the query.
4139816The TOP operator can return a maximum of %d rows; %d was requested.
4139916The sort operation is too complex. Consult SQL Server Books Online for more information.
4140116WSFC cluster service is offline.
4140216The 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 quorum in the cluster.
4140316Availability group is offline.
4140416The 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 by the WSFC availability group resource going offline.
4140516Availability group is not ready for automatic failover.
4140616The availability group is not ready for automatic failover. The primary replica and a secondary replica are configured for automatic failover, however, the secondary replica is not ready for an automatic failover. Possibly the secondary replica is unavailable, or its data synchronization state is currently not in the SYNCHRONIZED synchronization state.
4140716Some availability replicas are not synchronizing data.
4140816In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the primary replica.
4140916Some synchronous replicas are not synchronized.
4141016In this availability group, at least one synchronous replica is not currently synchronized. The replica synchronization state could be either SYNCHONIZING or NOT SYNCHRONIZING.
4141116Some availability replicas do not have a healthy role.
4141216In this availability group, at least one availability replica does not currently have the primary or secondary role.
4141316Some availability replicas are disconnected.
4141416In this availability group, at least one secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
4141516Availability replica does not have a healthy role.
4141616The role of this availability replica is unhealthy. The replica does not have either the primary or secondary role.
4141716Availability replica is disconnected.
4141816This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
4141916Data synchronization state of some availability database is not healthy.
4142016At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-commit availability replica, all availability databases should be in the SYNCHRONIZED state.
4142116Availability database is suspended.
4142216Either a database administrator or the system has suspended data synchronization on this availability database.
4142316Secondary database is not joined.
4142416This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete. For information about how to join a secondary database to an availability group, see SQL Server Books Online.
4142516Data synchronization state of availability database is not healthy.
4142616The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database should be in the SYNCHRONIZED state.
4142716Availability replica is not joined.
4142816This secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the join state must be Joined Standalone Instance (1) or Joined Failover Cluster (2). For information about how-to join a secondary replica to an availability group, see SQL Server Books Online.
4150010An error (0x%08x) occurred when asynchronous operations administrator attempted to notify the client (ID %ls) of the completion of an operation.  This is an information message only.  No user action is required.
4150116Failed to register client (ID %ls) with asynchronous operations administrator.  A client with this ID has already been registered.  Check that the specified client ID is correct, then retry the operation.  To re-register a client, the client must first be deregistered.
4150216Failed to deregister client (ID %ls) from asynchronous operations administrator.  The client has not registered with the administrator.  Check that the specified client ID is correct, then retry the operation.
4150316Client (ID %ls) failed to submit work to asynchronous operations administrator.  The client has not registered with the administrator.  Check that the specified client ID is correct, then retry the operation.
4150416Asynchronous operations administrator failed to allocate a work item for the work submitted by client (ID %ls).  The administrator may have exhausted all available resources.  If this condition persists, contact the system administrator.
4150516Asynchronous operations administrator failed to queue a work item for the work submitted by client (ID %ls) (internal error %d).  The administrator may have exhausted all available resources.  If this condition persists, contact the system administrator.
4160016An error has occurred while executing an asynchronous operation for a database replica (Windows Fabric partition ID %ls, operation %d, error 0x%08x).  Refer to the error code for more details.  If this condition persists, contact the system administrator.
4160116Valid state transition is not found for local replica with partition ID %ls (current state %ls, trigger %ls, current epoch [%I64d,%I64d], triggering epoch [%I64d,%I64d]).  The replica is not in the correct state to accept the Windows Fabric command.  If this condition persists, contact the system administrator.
4160216An error has occurred while attempting to access replica publisher’s subscriber list (partition ID %ls, SQL OS error code 0x%08x).  Refer to the error code for more details.  If this condition persists, contact the system administrator.
4160316The transport subscriber failed to process the build secondary replica event (partition ID %ls).  If this condition persists, contact the system administrator.
4160416The transport subscriber failed to process the configuration change replica event (partition ID %ls).  If this condition persists, contact the system administrator.
4160516Cannot associate replica (Windows Fabric replica ID 0x%08X) with the specified Windows Fabric partition (ID %ls).  The replica is already associated with a Windows Fabric partition (ID %ls).  If this condition persists, contact the system administrator.
4160616Replica (Windows Fabric replica ID 0x%08X, current state ‘%ls’) cannot process configuration-update command for Windows Fabric partition (ID %ls).  Configuration updates can be process by the primary replica only.  If this condition persists, contact the system administrator.
4160716Operation timed out while waiting for %ls access to the cached information in the replica controller (Windows Fabric replica ID 0x%08X, partition ID %ls).  If this condition persists, contact the system administrator.
4160816Failed to obtain %ls access to the cached information in the replica controller (Windows Fabric replica ID 0x%08X, partition ID %ls, SQL OS error %d).  The operation may have been aborted.  Refer to the SQL OS error number for details.  If this condition persists, contact the system administrator.
4160916Operation timed out while waiting for %ls access to the list of replica controller objects.  If this condition persists, contact the system administrator.
4161016Failed to obtain %ls access to the list of replica controller objects (SQL OS error %d).  The operation may have been aborted.  Refer to the SQL OS error number for details.  If this condition persists, contact the system administrator.
4161116Replica controller for the local replica (Availability Group ID %ls) cannot be found.  Make sure the specified Availability Group ID is correct, then retry the operation.  If this condition persists, contact the system administrator.
4161216An error has occurred while %ls %ls database (SQL Error Code: %d).  Refer to the SQL error code for more details.  If this condition persists, contact the system administrator.
4161317Fabric Service ‘%ls’ failed to perform database operation ‘%ls’ on ‘%ls’ database (ID %d).  The database might be in an incorrect state for the operation.  If this condition persists, contact the system administrator.
4161410Fabric Service ‘%ls’ encountered a transient error while performing Windows Fabric operation on ‘%ls’ database (ID %d).  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4161510Fabric Service ‘%ls’ encountered a permanent error while performing a Windows Fabric operation on ‘%ls’ database (ID %d).  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4161616SQL Server cannot find the configuration of the replica with ID %ls (Windows Fabric partition ID %ls).  Make sure the specified Windows Fabric partition ID and replica ID are correct, then retry the operation.  If this condition persists, contact the system administrator.
4161710Fabric Service ‘%ls’ is unable to find out start of log and end of log LSN for ‘%ls’ database.  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4161816Attempt to access non-existent or uninitialized Windows Fabric partition ‘%ls’.  This is usually an internal condition, such as the Windows Fabric service is getting initialized or it is getting destroyed.
4161916Windows Fabric ‘%ls’ (partition ID ‘%ls’)encountered transient error %d while waiting for build replica operation on database ‘%ls’ (ID %d).  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4162010Build replica operation on database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) has been cancelled by Windows Fabric.  Windows Fabric cancelled build replica operation.  This is an informational message only.  No user action is required.
4162110Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) encountered error ‘%ls’ and is reporting ‘%ls’ failure to Windows Fabric.  Refer to the SQL Server error log for information about the errors that were encountered..  If this condition persists, contact the system administrator.
4162216Windows Fabric service ‘%ls’ (partition ID ‘%ls’) is trying to update primary replica information for local replica %ls which is neither ACTIVE_SECONDARY nor IDLE_SECONDARY (current role %ls).  SQL Server cannot update primary replica information in invalid state.  This is an informational message only.  No user action is required.
4162320The Database Mirroring endpoint port is unavailable.  Verify that the DBM endpoint is created.
4162416Drop database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) has failed. SQL Server has failed to drop the database. If this condition persists, contact the system administrator.
4162520The internal buffer for the replication URL is insufficient.
4162610Failed to retrieve service desription from Windows Fabric for partition ‘%ls’ (Windows Fabric error 0x%08x).  If this condition persists, contact the system administrator.
4162710An error has occurred while Dropping %ls database (SQL Error Code: %d).  Refer to the SQL error code for more details.  If this condition persists, contact the system administrator.
4162810Drop database Timer task encountered an error (SQL Error Code: %d).  Refer to the SQL error code for more details.  If this condition persists, contact the system administrator.
4162910Fabric replica publisher encountered an error (SQL Error Code: %d, State: %d) while publishing event ‘%ls’ to subscriber of type ‘%ls’ on Fabric partition ‘%ls’ (partition ID: ‘%ls’).  Refer to the SQL error code for more details.  If this condition persists, contact the system administrator.
4163010Failed to update primary replica information for partition ‘%ls’ (Windows Fabric error 0x%08x).  This is an informational message only.  No user action is required.
4163116Fabric service ‘%ls’ failed to retrieve a known hardware sku while performing a build replica operation on ‘%ls’ database (ID %d).  Refer to the cluster manifest to ensure a valid SKU is defined for this node type.  If this condition persists, contact the system administrator.
4163210The system encountered SQL Error %d (severity: %d, state: %d), which has no corresponding error text.  Refer to the SQL Error number for more information regarding the cause and corrective action.
4163316Fabric Service ‘%ls’ (partition ID ‘%ls’) is unable to allocate a work item for the database restart of ‘%ls’ database (ID %d). The administrator may have exhausted all available resources.  If this condition persists, contact the system administrator.
4163410Open replica operation on database ‘%ls’ (ID %d) of Windows Fabric partition ID ‘%ls’ has been cancelled.  This is an informational message only.  No user action is required.
4163510Open replica operation on database ‘%ls’ (ID %d) of Windows Fabric partition ID ‘%ls’ failed.  For more information, see the SQL Server error log.  This is an informational message only.  No user action is required.
4163616Fabric Service ‘%ls’ (partition ID ‘%ls’) is unable to enqueue a work item for the database restart of ‘%ls’ database (ID %d). The administrator may have exhausted all available resources.  If this condition persists, contact the system administrator.
4163716The database ‘%ls’ (URI: ‘%ls’, partition ID ‘%ls’) is not currently participating in a GeoDR relationship.
4163816Could not retrieve remote replica storage configuration for database ‘%ls’ (URI: ‘%ls’).
4163916Could not retrieve remote replica configuration for database ‘%ls’ (URI: ‘%ls’).
4164010Database ‘%ls’ encountered a transient error (error code: 0x%08X) while performing task ‘%ls’.  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4164116Could not send global cluster action ‘%ls’ request 0x%x.
4164210Undo of redo is run in Active Secondary role on database ‘%ls’ (ID %d). Recovery lsn: ‘%S_LSN’, Hardened lsn: ‘%S_LSN’.  If this condition persists, contact the system administrator.
4164316Could not retrieve the Distributed AG Configuration  for database ‘%ls’ (URI: ‘%ls’, partition ID ‘%ls’) . Encountered error (error code: 0x%08X).
4164417Fabric Service ‘%ls’ failed to perform database operation ‘%ls’ on database ‘%ls’.  The database might be in an incorrect state for the operation.  If this condition persists, contact the system administrator.
4164516Fabric Service ‘%ls’ (partition ID ‘%ls’) encountered error (error code: 0x%08X) while querying for Fabric property ‘%ls’.
4164616Invalid Fabric property ‘%ls’ received for partition ‘%ls’.
4164717Failed to start the report fault thread during replica manager startup.
4164810Get current progress was called on ‘%ls’ database (ID %d) which had undo of redo pending. Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4164910Could not submit Change Role completion tasks for  %ls’ (URI: ‘%ls’, partition ID ‘%ls’) . Encountered error (error code: 0x%08X).
4165010Waiting for replica catchup for AGID ‘%ls’ and ReplicaID ‘%ls’ Failed.
4165116Invalid partition id in replica manager
4165217The replica manager is unavailable or not ready.
4165321Database ‘%.*ls’ encountered an error (error type: %d ‘%.*ls’) causing failure of the availability group ‘%.*ls’.  Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
4165417Failed to start the clean up nonexistant DBs thread during replica manager startup.
4165510Could not submit logical reseeding task for ‘%ls’ (URI: ‘%ls’, partition id: ‘%ls’) . Encountered error (error code: 0x%08X).
4165617Failed to start the windows fabric load balancer reporting thread during replica manager startup.
4165716Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) failed the call to UseDB.
4165816Failed to automatically enable Query Store in Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) .
4165916Checkpoint for Database ‘%ls’ (ID %d) failed. Encountered error (error code: 0x%08X).
4166016Windows Fabric service ‘%ls’ (partition ID ‘%ls’) received a primary replica information message from remote replica ‘%ls’ with an epoch [%I64d,%I64d] which is less than the local epoch [%I64d,%I64d].  SQL Server cannot update primary replica information from a replica with a smaller epoch.  This is an informational message only.  No user action is required.
4166116There are no waiters on the DataLossEvent for Fabric Service ‘%ls’ (partition ID ‘%ls’).
4166216Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) hit exception while running async tasks in Generic Subscriber.
4166310Failed to parse datawarehouse columnar cache settings during replica manager startup.
4166410Failed to refresh remote replica configuration for fabric service ‘%ls’.
4166510Failed to resolve DW logical node id for physical database ‘%ls’, which is hosted by compute service: ‘%ls’.
4166616Waiting for replica catchup before GeoDR role change failed for with error %d for database ‘%ls’, DBID %d, AGID ‘%ls’, and ReplicaID ‘%ls’.
4166716Fabric Service ‘%ls’ (partition ID ‘%ls’) encountered error (error code: 0x%08X) while setting Fabric property ‘%ls’.
4166816Failed to transition to forwarder role for physical database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’).
4166916Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) hit exception while running async tasks in RbIo Subscriber.
4167016Cannot retrieve tempdb remote file lease order id.
4170016System views related to Windows Fabric partitions and replicas are not available at this time, because replica manager has not yet started.  Wait for replica manager to start, then retry the system view query.
4170120The Activation Context is unavailable at this time.  The Windows Fabric Runtime is unavailable at this time, retry later.  Wait for the activation context to become available, then retry.
4170220The requested Configuration Package is unavailable at this time.  The Configuration Package is not a part of the Activation Context.  Verify that the requested Configuration Package name exists and is properly formatted.
4170320The requested Service Endpoint is unavailable at this time.  The Service Endpoint is not a part of the Activation Context.  Verify that the requested Service Endpoint name exists and is properly formatted.
4170420The datasource name is not correctly formatted.  The datasource name exceeds the maximum path length or does not adhere to defined format.  Verify that the datasource is name is fewer than MAX_PATH characters in length is properly formatted.
4170520The computer name is unavailable.  The computer name was not returned.
4170620Unable to get Fabric NodeContext.
4180116Failed to drop the memory optimized container ‘%.*ls’.
4180216Cannot drop the last memory-optimized container ‘%.*ls’.
4180316An In-Memory OLTP physical database was restarted while processing log record ID %S_LSN for database ‘%.*ls’. No further action is necessary.
4180416Internal error for database ‘%.*ls’ (lookup for HkTruncationLsn failed). The operation will be retried. No user action is required. If the problem persists, contact customer support.
4180516There is insufficient memory in the resource pool ‘%ls’ to run this operation on memory-optimized tables. See ‘http://go.microsoft.com/fwlink/?LinkID=614951’ for more information.
4180616Parameter “%ls” specified for procedure or function “%ls” is not valid.
4180716A MARS batch failed due to a unique constraint violation on a memory optimized table.
4180816The current MARS batch attempted to update a record that has been updated by another batch within the same transaction.
4180916Natively compiled triggers do not support statements that output a result set.
4181016Stored procedures called from natively compiled triggers do not support statements that output a result set.
4181116XTP physical database was stopped while processing log record ID %S_LSN for database ‘%.*ls’. No further action is necessary.
4181216ALTER TABLE on memory-optimized tables is not supported with concurrent MARS transactions.
4181316XTP database ‘%.*ls’ was undeployed. No further action is necessary.
4181416The procedure ‘%.*ls’ cannot be called from a user transaction.
4181516Data migration on table id %d cannot be performed because the table is already in the process of migration.
4181616The parameter ‘%.*ls’ for procedure ‘%.*ls’ cannot be NULL.
4181716Invalid object id %d provided as input for procedure ‘%.*ls’.  The object id must refer to a memory-optimized table with a column store index.
4181823An upgrade operation failed for database ‘%.*ls’ attempting to upgrade the XTP component from version %u.%u to version %u.%u. Check the error log for further details.
4181916A MARS batch failed due to a validation failure for a foreign key constraint on memory optimized table ‘%.*ls’. Another interleaved MARS batch deleted or updated a row that was referenced by a foreign key row inserted by the failed batch.
4182016A MARS batch failed due to a validation failure for a foreign key constraint on memory optimized table ‘%.*ls’. Another interleaved MARS batch inserted a row that references the row that was deleted by the failed batch.
4182217There is insufficient disk space to generate checkpoint files and as a result the database is in delete-only mode. In this mode, only deletes and drops are allowed.
4182316Could not perform the operation because the database has reached its quota for in-memory tables. This error may be transient. Please retry the operation. See ‘http://go.microsoft.com/fwlink/?LinkID=623028’ for more information.
4182416The transaction was killed by a concurrent ALTER operation or by a write-write conflict.
4182516Stored procedure ‘%.*ls’ cannot be used to increase the user memory limit on the database.
4182616Stored procedure ‘%.*ls’ tried to set a lower limit to the user memory quota. The operation failed because the user memory consumption is larger than the specified target, delete some user data and try the operation again.
4182716Upgrade of XTP physical database ‘%.*ls’ requires restart of XTP engine.
4182816Creation of memory-optimized tables is temporarily disabled. Please try again later.
4182916The database cannot proceed with pricing-tier update as it has memory-optimized objects. Please drop such objects and try again.
4183016Upgrade of XTP physical database ‘%.*ls’ restarted XTP engine.
4183116Data migration on table id %d failed either fully or partially.  See errorlog for details.
4183216Index ‘%.*ls’ cannot be created on table ‘%.*ls’, because at least one key column is stored off-row. Index key columns memory-optimized tables must fit within the %d byte limit for in-row data. Simplify the index key or reduce the size of the columns to fit within %d bytes.
4183316Columnstore index ‘%.*ls’ cannot be created, because table ‘%.*ls’ has columns stored off-row. Columnstore indexes can only be created on memory-optimized table if the columns fit within the %d byte limit for in-row data. Reduce the size of the columns to fit within %d bytes.
4183416ALTER TABLE has failed for ‘%.*ls’ with error code %d.
4183521An error (error code: 0x%08lx) occurred while adding encryption keys to XTP database ‘%.*ls’.
4183616Rebuilding log is not supported for databases containing files belonging to MEMORY_OPTIMIZED_DATA filegroup.
4183716Boot-page adjustment of XTP database ‘%.*ls’ requires restart of XTP engine.
4183816Failed to retrieve size for this file due to an internal error. Please try again later.
4183916Transaction exceeded the maximum number of commit dependencies and the last statement was aborted. Retry the statement.
4184016Could not perform the operation because the elastic pool has reached its quota for in-memory tables. This error may be transient. Please retry the operation. See ‘http://go.microsoft.com/fwlink/?LinkID=623028’ for more information.
4184123Found inconsistent boot-page for database ‘%.*ls’.
4184216Too many rows inserted or updated in this transaction. You can insert or update at most 4,294,967,294 rows in memory-optimized tables in a single transaction.
4184316Unable to construct segment for segment table.
4184415Clustered columnstore indexes are not supported on memory optimized tables with computed columns.
4184516Checksum verification failed for memory optimized checkpoint file %.*ls.
4184616Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have unique recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%I64d:%hu).
4184716Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not point to a transaction segment definition record.
4184916Memory optimized segment table consistency error detected. Segments are not contiguous in logical space. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
4185016Memory optimized segment table consistency error detected. Segments are not well formed for Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
4185116Memory optimized segment table consistency error detected. Segment definition ordering does not match the (strict) logical ordering. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
4185216Memory optimized segment table consistency error detected. Segment has a NullHkLsn. CkptId = %I64d, Segment LsnInfo = (%I64d:%hu)
4185316Memory optimized segment table consistency error detected. Current segment goes backward further than the definition record of the N-2 segment. Older Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. Newer Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d.
4185416Memory optimized file consistency error detected. An in use file with FileId %.*ls is referenced by the Checkpoint File Table but is not accounted for in the Storage Interface.
4185516Memory optimized file consistency error detected. Could not find a file with FileId %.*ls in the File Watermark Table visible by checkpoint ID %u.
4185616Memory optimized file consistency error detected. A file with FileId %.*ls of size %I64d bytes is smaller than expected %I64d bytes.
4186116Memory optimized large rows table consistency error detected. File Id is %.*ls. Corresponding LSN range is not ascending. Begin Lsn is (%I64d:%hu), End Lsn is (%I64d:%hu).
4186216Memory optimized large rows table consistency error detected. Corresponding File %.*ls not found in File Table. Begin Lsn is (%I64d:%hu), End Lsn is (%I64d:%hu).
4186316Checkpoint %I64d points to a root file %.*ls which was in use by a more recent checkpoint.
4186416Checkpoint %I64d has a file %.*ls which has a watermark (%I64d) larger than the more recent checkpoints watermark (%I64d).
4186516File %.*ls does not have a pair file %.*ls
4186616Unprocessed File %.*ls does not have a pair file which is also unprocessed. Processed pair file is %.*ls.
4186716Consistency errors detected in the MEMORY_OPTIMIZED_DATA filegroup. See preceding error messages for details. Consult https://go.microsoft.com/fwlink/?linkid=845604 for details on how to recover from the errors.
4186816Memory optimized filegroup checks could not be completed because of system errors. See errorlog for more details.
4186921In-memory OLTP version %u.%u is not supported on this platform.
4187010Dropped %d Orphan Internal Table(s).
4187116Failed to recreate XTP non-durable tables during recovery of the database ‘%.*ls’.
4187210Warning: Articles with varchar(max), nvarchar(max) and varbinary(max) data type columns are not supported with memory optimized tables on subscribers running SQL Server 2014 or earlier.
4190116One or more of the options (%ls) are not supported for this statement in SQL Database Managed Instance. Review the documentation for supported options.
4190216Unsupported device type. SQL Database Managed Instance supports database restore from URI backup device only.
4190316FILENAME option is not allowed in SQL Database Managed Instance.
4190416BACKUP DATABASE failed. SQL Database Managed Instance supports only COPY_ONLY full database backups which are initiated by user.
4190516Stored procedure %ls is not supported in SQL Database Managed Instance.
4190616Statement ‘%.*ls’ is not supported in SQL Database Managed Instance.
4190716Unsupported file type during restore on SQL Database Managed Instance.
4190816Only ‘local’ routes are supported in SQL Database Managed Instance.
4190916Modifying logical file name is not supported in SQL Database Managed Instance.
4191016Add/remove/modify of log files is not supported in SQL Database Managed Instance.
4191116Adding or removing XTP file or filegroup is not allowed in SQL Database Managed Instance.
4191216Maximum number of databases for SQL Database Managed Instance reached.
4191316Multiple filestream files are not supported in SQL Database Managed Instance.
4191416SQL Server Agent feature %ls is not supported in SQL Database Managed Instance. Review the documentation for supported options.
4191516Memory-optimized filegroup must be empty in order to be restored on the current tier of SQL Database Managed Instance.
4191616Maximum number of %u files for SQL Database Managed Instance reached.
4191716Dropping local instance via sp_dropserver is not allowed in SQL Database Managed Instance.
4191816Specifying files and filegroups in CREATE DATABASE statement is not supported on SQL Database Managed Instance.
4191916Multiple backup sets in a single backup file are not supported in SQL Database Managed Instance.
4192016This feature is not supported through T-SQL on SQL Database Managed Instance.
4192116Restoring from a backup that contains multiple log files is not supported in SQL Database Managed Instance.
4192216The backup operation for a database with service-managed transparent data encryption is not supported on SQL Database Managed Instance.
4192316Cannot find server certificate with thumbprint ‘%.*ls’. Please use PowerShell Cmdlet ‘Add-AzureRmSqlManagedInstanceTransparentDataEncryptionCertificate’ to create the certificate.
4192416All files need to be smaller or equal to %d MB in this edition of Managed Instance. File id: %ld. Size: %I64d bytes.
4192516If DB has multiple data files, all files need to have max size larger than %d MB in this edition of Managed Instance. File id: %ld. Size: %I64d bytes.
4192616Secondary filegroup is not supported in this edition of Managed Instance. File id: %ld.
4192716The file name ‘XTP’ is reserved for the files containing In-Memory OLTP data.
4192816The filegroup name ‘XTP’ is reserved for the filegroup containing In-Memory OLTP data.
4192916One or more files are not in online state after the restore.
4193016Modifying number of files and max size for TempDb is not yet supported in SQL Database Managed Instance.
4193110Warning:  New name of managed database ‘%.*ls’ is same as the old one.
4193216Cannot rename managed database ‘%.*ls’ because it’s currently in use.
4193321Failed to initialize detours and local time for Managed Instance. %ls
4193416Statement ‘%.*ls’ is not supported in the current version of the server.
4193516Managed Instance has reached the total capacity of underlying Azure storage account. Azure Premium Storage account is limited to 35TB of allocated space.
4193616This feature is not supported in the Hyperscale edition of SQL Database Managed Instance.
4200116Failed to parse XML configuration. The operating system returned error %ls.
4200216Failed to parse XML configuration. The parser returned error %.*ls
4200316Failed to parse XML configuration. A required attribute ‘%ls’ is missing.
4200416Failed to parse XML configuration. A required element ‘%ls’ is missing.
4200516Failed to parse XML configuration. Invalid value for attribute ‘%ls’.
4200616The default tempdb directory (‘%ls’) in XDB is not a valid path.
4200716The default tempdb directory (‘%ls’) in XDB is not a local path.
4200816ODBC error: State: %ls: Error: %d Message:’%ls’.
4200916Instance certificate ‘%ls’ cannot be found.
4201016Cannot initiate cross instance connection.
4201116ODBC initialization error: : %d.
4201216XodbcWrapper Enforced Retry For Testing.
4201316HTTP initialization error: : %d.
4201416Cannot retrieve server admin credential configuration.
4201520Error occurred while attempting to authenticate user remotely. Error %d, State %d.
4201616Error occurred in the DosGuard.
4201716Error occurred in the Redirector’s proxy while parsing a packet. Expected: %d, Actual: %d.
4201816Remote transaction has been doomed and cannot commit.
4201916%ls operation failed. %ls
4202016Updating name to ‘%.*ls’ failed.
4202116Initialization of http session handle for fetching federation metadata failed during AzureActiveDirectory initialization.
4202216Initialization of http connect handle for fetching federation metadata failed during AzureActiveDirectory initialization.
4202316Updating userdb properties on copy termination failed.
4202416Switching to logical master database failed.
4202516The extended recovery fork stack in the metadata of FCB is either corrupted or in an unexpected format.
4202616Loading the Active Directory Library failed.
4202716Initialization of the Active Directory Function pointers failed.
4202816The database ‘%.*ls’ has been detached as it was marked as a shared disk instance and was not started. This is an informational message; no user action is required.
4202916An internal error happened while generating a new DBTS for database “%.*ls”. Please retry the operation.
4203016Updating logical master’s sys.databases on seeding completion failed.
4203116This functionality is not supported for A/B test isolated instances.
4203216XODBC Get Authentication Cache failed, state %d
4203316Updating Distributed AG Configuration failed.
4203416Boot of federation host failed with error 0x%08X.
4300116‘%.*ls’ is not a valid login name.
4300216The storage size of %d MB exceeds the maximum allowed storage of %d MB.
4300316More than one firewall rules have the same name ‘%.*ls’.
4300416‘%.*ls’ is not a valid firewall rule name because it contains invalid characters.
4300516‘%.*ls’ is not a valid database name because it contains invalid characters.
4300616Database name ‘%.*ls’ is too long.
4300716‘%.*ls’ is not a valid database charset.
4300816‘%.*ls’ is not a valid database collation.
4300916The storage size of %d MB does not meet the minimum required storage of %d MB.
4301016‘%.*ls’ cannot be updated.
4301116‘%.*ls’ is not a valid version.
4301216The configuration name cannot be empty.
4301316The value for configuration ‘%.*ls’ cannot be empty.
4301416The same configuration ‘%.*ls’ cannot be updated more than once.
4301516The configuration ‘%.*ls’ does not exist for %.*ls server version %.*ls.
4301616The value ‘%.*ls’ for configuration ‘%.*ls’ is not valid. The allowed values are ‘%.*ls’.
4301716The configuration names you defined are not consistent.
4301816The value ‘%.*ls’ for configuration ‘%.*ls’ is not consistent with default value ‘%.*ls’.
4301916The source ‘%.*ls’ for configuration ‘%.*ls’ is not valid.
4302016The storage size of %d MB is not a valid configuration. Valid storage sizes range from minimum of %d MB and additional increments of %d MB up to maximum of %d MB.
4302116The point in time %S_DATE is not valid. Valid point in time range from %d days early to now and not before source server creation time.
4302216The edition %.*ls is not a valid edition. Edition cannot be changed by restoring.
4302316The storage size of %d MB is lower than the source storage size.
4302416The version %.*ls is not a valid version. Version cannot be changed by restoring.
4302516Input parameter is incorrect. Please double check the input.
4302616Cannot drop system database ‘%.*ls’, skipping.
4302716Geo Restore is not supported.
4302816The replication feature is not supported.
4302916Edition %.*ls must be the same as the primary server when creating a replica server.
4303016Version %.*ls must be the same as the primary server when creating a replica server.
4303116The storage size of %d MB is lower than the primary server’s storage size.
4303216No available primary server %.*ls is found when creating a replica server.
4303316The primary server %.*ls already has the maximum of replica servers.
4303416The replica server is not in ready state when promoting.
4303516‘%.*ls’ and ‘%.*ls’ cannot be updated together.
4303616Input parameter is incorrect when creating a replica server. Please double check the input.
4303716An internal error was encountered when processing the restore request. This request has been assigned a tracing ID of ‘%.*ls’. Message is ‘%.*ls’, and details are ‘%.*ls’. Provide this tracing ID/Message/Details to customer support when you need assistance.
4500116%ls operation failed. Specified federation name does not exist.
4500216%ls operation failed. Specified federation distribution name %.*ls is not valid.
4500316%ls operation failed. Specified data type is not supported as a federation distribution.
4500416%ls operation failed. Specified value is not valid for federation distribution %.*ls and federation %.*ls.
4500516Filter value cannot be set or was already set for this session.
4500616The federation key value is out of bounds for this member.
4500716%ls cannot be run while another federation operation is in progress on federation %.*ls and member with id %d.
4500816A partition in a table group that has a partition key defined is not allowed to be a federation member.
4501416%ls is not supported on %S_MSG.
4501516Specified federation operation id is already in use.
4501616Specified federation %.*ls does not exist.
4501716%ls operation failed. Specified federation name %.*ls is not valid.
4501816Specified federation operation id is invalid for %ls operation.
4501916%ls operation failed. Federation is in invalid state.
4502016%ls operation failed. %d is not a valid federation id.
4502116%ls operation failed. %d is not a valid federation member id.
4502216A column insert or update conflicts with a federation member range. The statement was terminated. The conflict occurred in database ‘%.*ls’, table ‘%.*ls’, column ‘%.*ls’.
4502316%ls cannot be called on %S_MSG.
4502416ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %.*ls and federation %.*ls.
4502516%ls operation failed. Specified boundary value is not valid for federation distribution %.*ls and federation %.*ls.
4502616%ls operation failed. Specified boundary value does not exist for federation distribution %.*ls and federation %.*ls.
4502716%ls operation failed. Specified type information is not valid for federation distribution.
4502816%ls operation failed. Specified boundary value is not valid for current federation member.
4502916%ls operation failed. The federation distribution scheme size cannot exceed 900 bytes.
4503015The USE FEDERATION statement is missing the required %.*ls option.  Provide the option in the WITH clause of the statement.
4503116The USE FEDERATION statement is not supported on a connection which has multiple active result sets (MARS) enabled.
4503216The USE FEDERATION statement is not allowed under non-revertible impersonated security context.
4503316Federation member %d is not available.  Another command is creating or dropping it.
4503416Federation member database cannot be dropped using DROP DATABASE.
4503516Federation member database cannot be renamed using ALTER DATABASE.
4503616ALTER FEDERATION SPLIT operation has been aborted. The %.*ls federation was dropped while the split was still in progress.
4503716ALTER FEDERATION SPLIT operation failed due to an internal error.  This request has been assigned a tracing ID of ‘%.*ls’.  Provide this tracing ID to customer support when you need assistance.
4503816CREATE DATABASE AS COPY OF %S_MSG is not supported.
4503916Federation member database cannot be restored.
4504016Service objective for federation member database cannot be changed using ALTER DATABASE.
4504116Federation member database options cannot be changed.
4504216Federation root database options cannot be changed.
4504316ALTER FEDERATION SWITCH %ls is not supported on %ls members.
4504416ALTER FEDERATION SWITCH IN failed. %.*ls is not a valid database that can be switched in.
4504516ALTER FEDERATION SWITCH IN failed. %ls of the federation key in %.*ls doesn’t match with the correponding property of federation %.*ls.
4504616%ls operation failed. The specified value for federation %.*ls does not correspond to a present member.
4510116Parameter “%ls” should contain all configurable dimension properties.
4510216Parameter “%ls” should contain settings for all dimensions.
4510316Cannot reset the last setting for a dimension to non-default.
4510416The default setting cannot be deleted for a dimension.
4510516Cannot assign a deprecated setting as successor.
4510616Cannot create new item. The max provision count has been reached.
4510716Cannot reset service objective to draft from enabled or disabled state.
4510816Default service objective cannot be disabled.
4510916Parameter “%ls” contains conflicting dimension setting selections.
4511016Parameter %s value cannot be applied to service objective in non-draft mode.
4511116Cannot reset the last service objective to non-default.
4511216Cannot delete the default service objective.
4511316Cannot set the service objective as default in draft mode.
4511416Cannot edit setting marked as deprecated.
4511516Cannot assign a disabled service objective to a database.
4511616Cannot delete a setting without a successor assigned for deprecation.
4511716Cannot delete a system service objective.
4511816Cannot assign a system service objective to user database.
4511916Property selections contain conflicting values.
4512016The name ‘%ls’ already exists. Choose a different name.
4512116Server ‘%ls’ does not support memory-optimized data. Make sure both source and target servers are enabled for memory-optimized data.
4512216‘%ls’
4512316Updating max size is not supported for database ‘%ls’. Database size will grow automatically as more data is inserted.
4512516Parameter “%ls” cannot be empty or null.
4512616Parameter “%ls” is invalid.
4512716Parameter “%ls” is invalid.
4512816Parameter “%ls” is invalid.
4512916Parameter “%ls” is invalid.
4513016Parameter “%ls” is invalid.
4513116Parameter “%ls” is invalid.
4513216Every database must be assigned a service objective.
4513317A connection failed while the operation was still in progress, and the outcome of the operation is unknown. Query sys.dm_operation_status in the master database for current job status.
4513416The remote partner server name ‘%ls’ could not be resolved.
4513516Only continuous database copies can be updated.
4513616Only continuous database copies can be terminated.
4513716 Insufficient permission to create a database copy on server ‘%ls’.
4513816The destination database name ‘%ls’ already exists on the server ‘%ls’.
4513916The source server name should be the server of the current connection.
4514016Maximum lag does not support the specified value. Maximum lag must be between ‘%ls’ and ‘%ls’.
4514116Database copies can only be initiated on the source server.
4514216IsForcedTerminate cannot be set while creating a database copy.  This can only be updated on the source server after it is created.
4514316The source database ‘%ls’ does not exist.
4514416Continuous copy cannot be initiated on source database ‘%ls’ because it is a federation root member.
4514516Only continuous database copies can be created.
4514616Database copy property ‘%ls’ is required.
4514716Database copy property ‘%ls’ cannot be changed.
4514816 ‘%ls’ is not supported for entity ‘%ls’.
4514916 Continuous copy is not supported on ‘master’ database.
4515016 Feature is disabled.
4515116 Changing value(s) ‘%ls’ for entity ‘%ls’ not supported.
4515216 Termination of a database copy cannot be performed because the destination server ‘%ls’ is unavailable or the database copy does not exist on the destination server. Try forced termination instead.
4515316 Management Service is not currently available.  Please retry the operation later.  If the problem persists, contact customer support, and provide them the session tracing ID of ‘%ls’.
4515416A free database already exists for subscription ‘%ld’ for the selected region. Subscription can have only one free database per region. To provision another free database in same subscription, choose a different region. To provision another free database in same region, use different subscription.
4515516A free database operation is already in progress for subscription ‘%ld’. Subscription can have only one free database per region. To provision another free database in same subscription, choose a different region. To provision another free database in same region, use different subscription.
4515616Subscription ‘%.*ls’ is busy with another operation. Please try your operation later.
4515716Server ‘%.*ls’ is busy with another operation. Please try your operation later.
4515816Cannot move server ‘%.*ls’ from source subscription ‘%ls’ to target subscription ‘%ls’. You can have only one free database per subscription. To continue the move operation, drop one of the free databases, or use a different subscription.
4515916Cannot move servers from source subscription ‘%ls’ to target subscription ‘%ls’ since both subscriptions have free databases. You can have only one free database per subscription. To continue the move operation, drop one of the free databases, or use a different subscription.
4516016Subscription ‘%ls’ doesn’t have any servers to move.
4516116Managed instance ‘%.*ls’ is busy with another operation. Please try your operation later.
4516216Operation failed because subscription ‘%ls’ is disabled.
4516316Create Server request must either specify SQL login with password or denote admin login is a federated user by setting ‘IsFederatedAdminLogin’ property to ‘True’.
4516416 Invalid number of database copies: ‘%d’.  Only one database copy is currently allowed to be created along with the database creation.
4516516Continuous copy is not supported on the free database ‘%.*ls’.
4516616Database ‘%.*ls’ was %.*ls successfully, but some properties could not be displayed.
4516716An invalid state transition was attempted.
4516816The server ‘%.*ls’ has too many active connections.  Try again later.
4516916The subscription ‘%.*ls’ has too many active connections.  Try again later.
4517016A trusted certificate was not found for this request.
4517116Secondary database must be created in the same server as primary database unless ‘IsContinuous’ is specified.
4517216The ‘MaximumLag’ parameter requires that ‘IsContinuous’ is specified.
4517316Source server not found for subscription: %ls, resource group: %ls, server name: %ls.
4517416Unable to queue server %ls for migration.  There is a pending migration request for the server.
4517516Unable to queue server %ls for migration.  A migration is already in progress.
4517616Unable to queue server %ls for migration.  The server is using feature %ls that prevents it from being migrated.
4517716Unable to queue server %ls for migration.  Failed to find a target cluster for migration.
4517816Database create mode ‘%ls’ is not supported.
4517916The operation timed out and automatically rolled back. Please retry the operation.
4518016Resource with the name ‘%ls’ already exists. To continue, specify a different resource name.
4518116Resource with the name ‘%ls’ does not exist. To continue, specify a valid resource name.
4518216Database ‘%ls’ is busy with another operation. Please try your operation later.
4518316There is an import or export operation in progress on the database ‘%ls’.
4518416Operation Id ‘%ls’ was not found.
4518516The change role completion notification for logical server ‘%.*ls’, ag id ‘%ls’, local database id ‘%ls’ was ignored as freshness number did not match. Expected ‘%d’.
4518616Database create mode ‘%ls’ is not supported in state ‘%ls’.
4518716The replication mode updated notification for logical server ‘%.*ls’, ag id ‘%ls’, local database id ‘%ls’, partner database id ‘%ls’ was ignored as current replication mode did not match expected value ‘%ls’.
4518816The operation has been cancelled by user.
4518916 Insufficient permission to add secondary on server ‘%ls’.
4519016 ‘%ls’ is an invalid name because it contains one or more unsupported unicode characters.
4519116The operation could not be completed because it would result in data loss on secondary database ‘%ls’ on server ‘%ls.’ Set the ‘replace’ parameter to proceed anyway.
4519216The value specified for ‘allow_connections’ does not match the value for the existing replication relation for database ‘%ls’ on server ‘%ls.’
4519316Database ‘%ls’ on server ‘%ls’ is already the target in another replication relationship.
4519416The operation could not be completed because it would result in target database ‘%ls’ on server ‘%ls’ having a lower service objective than source database ‘%ls’ on server ‘%ls.’
4519516The operation could not be completed because database ‘%ls’ on server ‘%ls’ is the source in another replication relationship.
4519616The operation on the resource could not be completed because it was interrupted by another operation on the same resource.
4519717A system maintenance operation is in progress on server ‘%.*ls’ and database ‘%.*ls.’ Please wait a few minutes before trying again.
4519816MODIFY LOG FILE failed. Size is greater than MAXSIZE.
4519916This command requires a database encryption scan on database ‘%.*ls’. However, the database has changes from previous encryption scans that are pending log backup. Please wait several minutes for the log backup to complete and retry the command.
4520016The server ‘%ls’ are not associated with the tenant ‘%ls’.
4520116SQL Server Agent service is not running.
4520216Timed out after %ld seconds waiting for Smart Admin job to complete. Please run the stored procedure again.
4520316The parameter @state cannot be NULL, and should be 1 or 0. Specify 1 to start SQL Server Managed Backup to Windows Azure, or 0 to pause.
4520416The parameter %ls cannot be NULL or empty. Provide a valid %ls.
4520516No backup setting is supplied. Please specify at least one backup setting to be configured.
4520616The value specified for parameter @type is invalid. The @type parameter value should either be ‘Database’ or ‘Log’.
4520716%ls
4520816SQL Server Managed Backup to Windows Azure master switch is not turned on.
4520916The parameter value for notification email is not specified or is NULL. Please specify a valid email to enable notifications for Smart Admin.
4521016Database Mail is not enabled for SQL Agent to use for Notifications. Enable Database Mail as the mail system for alerts.
4521116Database mail profile is not setup for SQL Agent notifications.
4521216The value specified for parameter %ls is invalid. Provide a valid %ls.
4521316@full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must be specified if @scheduling_option is set to ‘Custom’
4521416@days_of_week must be specified if @full_backup_freq_type is set to ‘Weekly’
4521516Local caching is not yet supported.
4521616@full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must not be specified if @scheduling_option is set to ‘System’
4521716@encryptor_type, and @encryptor_name must not be specified if @encryption_algorithm is set to ‘NO_ENCRYPTION’
4521816@encryptor_type, and @encryptor_name must be specified if @encryption_algorithm is not set to ‘NO_ENCRYPTION’
4521916@days_of_week must not be specified if @full_backup_freq_type is set to ‘Daily’
4522010An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
4522110An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d.
4530117The resource has been moved to another location
4530217SLO ‘%ls’ operation cannot succeed as the memory usage of ‘%ls’ exceeds the quota.
4530317Attempt to cancel activation or rollback activation automatically because of operation timeout, but this is not supported in current state. Please check database status after operation is finished.
4530416Elastic pool estimate ‘%.*ls’ was not found for server ‘%.*ls’
4530516Request could not be processed because of conflict in the request: ‘%.*ls’
4530616The external admin cannot be set because the user or group already exists in the ‘master’ database.
4530716Advisor ‘%.*ls’ was not found for requested resource
4530816Recommended action ‘%.*ls’ was not found for advisor ‘%.*ls’
4530916The operation could not be completed because database ‘%ls’ on server ‘%ls’ is recovering from a geo-replication role change and is not currently eligible to become a primary or standalone database. Wait until the relationship leaves the ‘SUSPENDED’ replication state and try again.
4531016Unable to return metrics. Request would return too much data.
4531116The server key ‘%.*ls’ already exists. Please choose a different server key name.
4531216The server key URI ‘%.*ls’ already exists as another server key.
4531316The server key ‘%.*ls’ cannot be deleted because it is currently in use by ‘%.*ls’.
4531416Server key ‘%.*ls’ does not exist. Make sure that the server key name is entered correctly.
4531516The operation could not be completed because a service objective assignment is in progress for database ‘%.*ls’ on server ‘%.*ls.’ Wait for the service objective assignment to complete and try again.
4531616MODIFY FILE failed. Size is greater than MAXSIZE. Please query sys.database_files and use DBCC SHRINKFILE to reduce the file size first.
4531716Server ‘%.*ls’ does not exist in resource group ‘%.*ls’ in subscription ‘%.*ls’.
4531816 Service Fabric Application Version is not available.
4531916The service objective assignment for database ‘%.*ls’ on server ‘%.*ls’ could not be completed as the database is too busy. Reduce the workload before initiating another service objective update.
4532016The operation could not be completed on server ‘%.*ls’ because the Azure Key Vault key ‘%.*ls’ is disabled.
4532116The operation could not be completed on server ‘%.*ls’ because attempts to connect to Azure Key Vault ‘%.*ls’ have failed
4532216The operation could not be completed because the Azure Key Vault key ‘%.*ls’ expiration date is invalid. The Azure Key Vault key can not have an expiration date.
4532316Unable to start a copy because the source database ‘%ls’ is being updated.
4532416The operation could not be completed because the Azure Key Vault Uri is null or empty.
4532516The operation could not be completed because the Azure Key Vault Key name is null or empty.
4532616The operation could not be completed because the Azure Key Vault Key name ‘%ls’ does not exist.
4532716The operation could not be completed because the Azure Key Vault Key name ‘%ls’ is currently set as server encryption protector.
4532816The server identity is not correctly configured on server ‘%ls’. (https://aka.ms/sqltdebyoksetup)
4532916An invalid response from Azure Key Vault. Please use a valid Azure Key Vault URI.
4533016The server ‘%ls’ requires the following Azure Key Vault permissions: ‘%ls’. Please grant the missing permissions to the service principal with ID ‘%ls’. (https://aka.ms/sqltdebyoksetup)
4533116The operation could not be completed because the read scale value specified is not supported for a ‘%ls’ database.
4533216The operation could not be completed because the read scale value specified is invalid.
4533316The service request timed out.  %ls.
4533416Server edition ‘%ls’ is invalid.
4533516Server type ‘%ls’ is invalid.
4533616The operation could not be completed because ‘%ls’ is an invalid Server Key name. Please provide a key name in the format of ‘vault_key_version’. For example, if the keyId is https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion, then the Server Key Name should be formatted as: YourVaultName_YourKeyName_YourKeyVersion.
4533716The planned failover operation has rolled back because database ‘%ls’ could not be synchronized with its remote partner. This may be due to a service outage, or to a high volume of write traffic. Consider using forced failover.
4533816The planned failover operation has rolled back because the remote server ‘%ls’ could not be reached. This may be due to a service outage. Consider using forced failover.
4533916The max size update on the geo-secondary database ‘%ls’ on server ‘%ls’ failed with reason ‘%ls’.
4534016The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is ‘%ls’.
4534116The operation could not be completed because an error was encountered when attempting to retrieve Key Vault information for ‘%ls’ from server ‘%ls’. The encountered error message is ‘%ls’.
4534216The operation could not be completed because an Azure Active Directory error was encountered. Please ensure the server ‘%ls’ and key vault ‘%ls’ belong to the same tenant. The error message from Active Directory Authentication library is ‘%ls’.
4534316The provided Key Vault uri ‘%ls’ is not valid. Please ensure the uri contains the vault, key, and key version information. An example valid uri looks like ‘https://YourVaultName.vault.azure.net/keys/YourKeyName/YourKeyVersion’. Please ensure the vault belongs to an endpoint from the list of supported endpoints available at ‘%ls’.
4534416Catalog DB creation failed.
4534516Cannot cancel database management operation ‘%ls’ in the current state.
4534616Subnet resource ID ‘%ls’ is invalid. Please provide a correct resource Id for the target subnet.
4534716LongTermRetentionBackup is enabled for server ‘%ls’. Move server cross subscription is not allowed.
4534816LongTermRetentionBackup is enabled for server ‘%ls’. Move server cross resource group is not allowed.
4534916The operation could not be completed because certificate rotation is in progress for server ‘%ls’.
4535016MODIFY MAXSIZE failed. To reduce the database size, the database first needs to reclaim unused space by running DBCC SHRINKDATABASE. Note that this operation can impact performance while it is running and may take several hours to complete. Refer to the following article for details of using T-SQL to run DBCC SHRINKDATABASE: ‘https://go.microsoft.com/fwlink/?linkid=852312’
4535116MODIFY MAXSIZE failed. The requested database size is smaller than the amount of data storage used.
4535216Create Managed Instance failed. Provided virtual network subnet is located in %ls, which is a different region than the one you are provisioning Managed Instance in (%ls). To create a VNET-joined Managed Instance, the instance and the virtual network have to be located in the same region.
4535316This private cluster is associated with TR %ls. You specified TR %ls as a parameter.
4535416Tenant ring %d already has positive placement weight set(%d) and can’t be used for private cluster for subscription %ls. Please ensure that the ring is actually not used, reset weight back to 0 or -1 and re-run the SignalPrivateTenantRingReady CAS.
4535516The storage account %ls is not valid or does not exist.
4535616The storage account credentials are not valid.
4535716Auditing cannot be configured on secondary databases.
4535816Server auditing settings are being updated for server ‘%ls’. Please wait for the existing operation to complete.
4535916Database name validation failed. The database name is not allowed because it contains trailing whitespace characters.
4536016The operation could not be completed because app config deployment is in progress for the app ‘%ls’.
4536116Invalid subnet address range (%ls). Address range has to be in CIDR format (IP/MASK) where IP is a valid IPv4 address and MASK is a number between 0 and 28.
4536216The operation could not be completed because the Azure Key Vault principal certificate has expired. The error message from Active Directory Authentication library (ADAL) is ‘%ls’.
4536316Server automatic tuning settings from previous request have not propagated to all databases yet. Please try again in few minutes.
4536416The operation could not be completed because database ‘%ls’ on server ‘%ls’ is currently unavailable. Try again later. If the problem persists, contact customer support.
4536516vCore value (%d) is not valid. Please specify a valid vCore value.
4536616The retention days of %d is not a valid configuration. Valid backup retention in days must be between %d and %d.
4536716Invalid virtual network configuration. This is not allowed: %ls.
4536816The given rule ID: %s is invalid. You can find valid rule ids in scan results file.
4536916No baseline is set for rule ID: %d. You should first set a baseline for this rule.
4537016Vulnerability Assessment scan on the resource ‘%ls’ is in progress. Please wait for the existing operation to complete.
4537116Cannot cancel management operation ‘%ls’ in the current state.%ls
4537216Automatic tuning option ‘%.*ls’ was not found for requested resource.
4537316Automatic tuning is not supported for SQL Data Warehouse.
4537416HardwareGeneration ‘%ls’ is not valid. Please specify a valid HardwareGeneration value.
4537516vCore value (%d) and HardwareGeneration ‘%ls’ is not a valid combination. Please specify a valid vCore and HardwareGeneration value.
4537616Managed Instance cannot be joined to a classic virtual network. Please provide a Resource Manager vnet to join.
4537716The provided Key Vault uri ‘%ls’ is not valid. Please ensure the key vault has been configured with soft-delete and purge protection. (https://aka.ms/sqltdebyoksoftdelete)
4537816geo-redundant-backup not supported for the current edition.
4537916geo-redundant-backup value is not allowed to update
4538016The edition %.*ls is not a valid edition. Edition cannot be changed by update.
4538116SKU Name ‘%ls’ is not valid. Please specify a valid SKU Name.
4538216Read or write operaions are not allowed on the storage account ‘%ls’.
4538316The storage account ‘%ls’ is disabled.
4538416The encryption protectors for all servers linked by GeoDR must be in the same region as their respective servers.  Please upload key ‘%ls’ to a Key Vault in the region ‘%ls’ as server ‘%ls’. (https://aka.ms/sqltdebyokgeodr)
4538516Unexpected Key Vault region found in the response for Key Vault ‘%ls’ associated with server ‘%ls’. Expected region: ‘%ls’, Region receieved in response: ‘%ls’. (https://aka.ms/sqltdebyokgeodr)
4538616The key vault provided ‘%ls’ on  server ‘%ls’ uses unsupported RSA Key Size or Key Type. The supported RSA Key Size is 2048 and Key Type is RSA and  RSA-HSM.
4538716Invalid hardware generation. It isn’t allowed to have both Gen4 and Gen5.
4538816Target subnet has associated Network Security Group (NSG). Remove %ls. (https://go.microsoft.com/fwlink/?linkid=871071)
4538916Target subnet has no associated Route Table. Associate Route Table with single User Defined Route (UDR): Name: default, Address prefix: 0.0.0.0/0, Next hop type: Internet. (https://go.microsoft.com/fwlink/?linkid=871071)
4539016Target subnet has associated Route Table with invalid configuration %ls. Associate Route Table with single User Defined Route (UDR): Name: default, Address prefix: 0.0.0.0/0, Next hop type: Internet. (https://go.microsoft.com/fwlink/?linkid=871071)
4539116Invalid virtual network configuration %ls. Add Azure recursive resolver virtual IP address 168.63.129.16 at the end of your custom DNS list: %ls. (https://go.microsoft.com/fwlink/?linkid=871071)
4539216SQL service endpoint is currently not allowed on Managed Instance. Remove SQL service endpoint from %ls. (https://go.microsoft.com/fwlink/?linkid=871071)
4539316Target subnet is not empty. Remove all resources from %ls or use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071)
4539416Virtual network for the target subnet is locked. Remove the lock from %ls. (https://go.microsoft.com/fwlink/?linkid=871071)
4539516Gateway subnet cannot be used for deploying managed instance. Use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071)
4539616Target subnet %ls does not exist. Use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071)
4539716Managed Instance deployment failed due to conflict with the following network requirements: %ls. Information about the network requirements and how to set them could be found at (https://go.microsoft.com/fwlink/?linkid=871071). You can find more details about this error in the virtual network Activity log.
4539816The specified edition %ls is not consistent with the specified SKU %ls.
4539916The specified license type %ls is not valid.
4540016Invalid storage size: %ls GB. Storage size must be specified between %ls and %ls gigabytes, in increments of %ls GB.
4540116Ring buildout ‘%ls’ has no support for small VM roles, role: ‘%ls’.
4540216Ring buildout ‘%ls’ does not support multiple DB roles.
4540316The operation could not be completed because a service tier change is in progress for managed instance ‘%.*ls.’ Please wait for the operation in progress to complete and try again.
4540416The operation failed because update SLO safety checks could not be completed. Details: ‘%ls’.
4540516The operation failed because a long running transaction was found on the SQL instance. Please wait for the transaction to finish execution and try again.
4540616Provisioning of zone redundant database/pool is not supported for your current request.
4540716The operation timed out and failed: ‘%ls’
4540816Resource not found: ‘%ls’.
4540916Network resource provider returned following error: ‘%ls’.
4541016Network resource provider denied access: ‘%ls’.
4541116Virtual network firewall rules are not currently supported on servers with failover groups configured with automatic failover policy. Please configure the failover groups on the server with manual failover policy.
4541216Failover Groups configured with an automatic failover policy are currently not supported on servers configured with virtual network firewall rules. Please configure the failover group with manual failover policy.
4541316Only one Interface endpoint profile is allowed.
4541416The instance collation cannot be changed on Managed Instance.
4541516Creating secondary of secondary (a process known as chaining) is not supported when enabling Transparent Data Encryption using Azure Key Vault (BYOK).
4541616Cannot create a Managed Instance with collation ‘%.*ls’. Please use collation ‘SQL_Latin1_General_CP1_CI_AS’ instead.
4541716Vulnerability Assessment storage container path must be supplied
4541816The operation failed because the SQL instance had high CPU usage of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try again.
4541916The operation failed because the SQL instance had high log write rate of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try again.
4542016The operation failed because update elastic pool safety checks could not be completed. Details: ‘%ls’.
4542116The operation failed because a long running transaction was found on the elastic pool. Please wait for the transaction to finish execution and try again.
4542216The operation failed because the elastic pool had high CPU usage of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try again.
4542316The operation failed because the elastic pool had high log write rate of %.*f%%. The current threshold is %.*f%%. Please wait for it to go down and try again.
4542416The operation could not be completed because %ls operation is in progress. Please wait for the operation in progress to complete and try again.
4542516The operation could not be completed because total allocated storage size for General Purpose instance would exceed %ls. Please reduce the number of database files and retry operation.
4542616The operation could not be completed because instance has configured geo replicated secondary instance.
4542716Hardware generation of the source is ‘%.*ls’ while that of the PITR target is ‘%.*ls’.
4542816The operation has failed because you are attempting to deploy managed instance as a geo-replication secondary to the subnet ‘%.*ls’ in which there already exists a managed instance. Deploying managed instance as a geo-replication secondary is supported only in cases when managed instance is the first instance deployed in a subnet. Consider deploying managed instance as a geo-replication secondary to a different subnet in which there are no existing managed instances, or if deploying to a subnet with existing managed instance disable the geo-replication option.
4542916The operation failed because it was issued on a custom maintenance window database. This is prohibited by default. Please try again with a switch to disable this check if the instance needs to be updated.
4543016The operation failed because it was issued on a custom maintenance window database outside of its maintenance window. Please try again within the next maintenance window (%ls – %ls).
4543116The operation failed because it was issued on a database during the default business hours in the region (%ls – %ls). Please try again once they end.
4543216Invalid storage size: Storage size limit (%ls GB) is less that current storage used (%ls GB). Please specify higher storage size limit.
4543316The specified family %ls is not consistent with the specified SKU %ls.
4543416The point in time ‘%.*ls’ for restoration can’t be later than now.
4543516The operation could not be completed. The requested sku update would cause the master server to have a larger max_connections value than its replica(s).
4543616The operation could not be completed. The requested storage update would cause the master server to have a larger storage size than its replica(s).
4543716The operation could not be completed. Replication is not enabled for the server.
4543816The timezone cannot be changed on Managed Instance.
4543916Cannot create a Managed Instance with timezone ‘%.*ls’. Please use timezone ‘UTC’ instead.
4544016Cannot create a Managed Instance as there are not enough available ip addresses in the selected subnet.
4544116Elastic server restore verification is not supported.
4544216The operation failed because the requested update mode ‘%ls’ did not match the chosen one ‘%ls’. Please try again later or use a different update mode specification.
4544316Storage Auto Grow is not supported .
4544416Provisioning of Zone Redundant server is not supported .
4544516Storage Auto Grow is not supported for Primary and Replica Servers.
4544616Geo Reduntant Backup not supported for Zone Redundant Server.
4544716Database cannot be paused because it is not supported on a ‘%ls’ database.
4544816Database with ‘%ls’ feature cannot be paused. Operation failed for Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4544916The database is already paused. Server ‘%.*ls’, Database ‘%.*ls’, Paused Time ‘%.*ls’.
4545016The database is already resumed. Server ‘%.*ls’, Database ‘%.*ls’.
4545116Database operation failed because database is paused. Server ‘%.*ls’, Database ‘%.*ls’
4545216Database operation failed because database is paused. Server ‘%.*ls’, Database ‘%.*ls’
4545310The operation failed due to throttling. Server ‘%.*ls’, Database ‘%.*ls’
4545416The operation failed because it is not supported on disabled database. Server ‘%.*ls’, Database ‘%.*ls’
4545516The operation failed because it is not supported on geo replicated databases. Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4545616The request failed because there is an ongoing ‘%.*ls’ operation. Server ‘%.*ls’, Database ‘%.*ls’.
4545716The request failed because there is an ongoing migration on server ‘%.*ls’, database ‘%.*ls’.
4545816Choosen subnet is delegated and cannot be used for deploying managed instance. Remove delegation from subnet.
4650115External table references ‘%S_MSG’ that does not exist.
4650215Type with name ‘%.*ls’ already exists.
4650315Invalid format for option ‘%S_MSG’.
4650415External option ‘%S_MSG’ is not valid.  Ensure that the length and range are appropriate.
4650515Missing required external DDL option ‘%S_MSG’.
4650615Invalid set of options specified for ‘%S_MSG’.
4650715Cannot perform DML on external tables.
4650815Incorrect syntax on external DDL option ‘%S_MSG’.
4650915FILE_FORMAT must be specified for HADOOP data source.
4651015FILE_FORMAT cannot be specified for RDBMS data source.
4651115EXTERNAL %S_MSG with id %d cannot be found.
4651215%S_MSG cannot be used with %S_MSG data source.
4651315A sharding column name must be provided when using SHARDED distribution.
4651415DISTRIBUTION must be specified when using a SHARD_MAP_MANGER data source.
4651515The specified sharding column name does not match any column in the external table definition.
4651615The specified credential cannot be found or the user does not have permission to perform this action.
4651717XML Parse error when de-serializing PDW Metadata.
4651815The %S_MSG ‘%ls’ is not supported with %S_MSG.
4651915%ls are not supported with %S_MSG.
4652015The external DDL statement contained an unrecognized option.
4652115Queries over external tables are not supported with the current service tier or performance level of this database. Consider upgrading the service tier or performance level of the database.
4652210Failed to update ‘%S_MSG’.
4652315A SCHEMA_NAME must be specified when using OBJECT_NAME.
4652415An OBJECT_NAME must be specified when using SCHEMA_NAME.
4652515External tables are not supported with the %S_MSG data source type.
4652615The %S_MSG operation is not supported with %S_MSG data source type.
4652715Altering the ‘%S_MSG’ property is not permitted for an external data source of type %ls.
4652815SHARDED DISTRIBUTION is allowed for SHARD_MAP_MANGER data source only.
4652915Allowed integer values for FIRST_ROW are between and including 1-101
4653015External data sources are not supported with type %S_MSG.
4653115Support for external data sources of type HADOOP is not enabled. To enable, set ‘hadoop connectivity’ to desired value.
4653215Sp_rename is not supported for data pool external table.
4653315Internal error occurred during distributed operation.
4653415A maximum of three NULL_VALUES are allowed in the list.
4653515Unable to retrieve secret [%s] from the secret store.
4653615Unable to process secret [%s] from the secret store.
4653716An unexpected internal error, failed to communicate with controller service, HRESULT 0x%x.
4653816An unexpected internal error received from controller service error code [%i].
4653915‘%S_MSG’ statement failed. At least one partitioning column is required when distribution type is ‘%S_MSG’.
4654015‘%S_MSG’ statement failed. Partitioning columns can be specified only if distribution type is ‘%S_MSG’.
4654115‘%S_MSG’ statement failed. The column name ‘%.*ls’ specified in the ‘%S_MSG’ option does not match any columns specified in the external table definition.
4654215%S_MSG statement failed. One or more errors occurred while executing the statement. %s
4654315%S_MSG statement failed. Invalid URI provided.
4654515Creating external data source over data pools is not supported in a system database.
4660116REJECT_TYPE
4660216FILE_FORMAT
4660316REJECT_VALUE
4660416REJECT_SAMPLE_VALUE
4660516LOCATION
4660616DATA_SOURCE
4660716PERCENTAGE
4660816ROW_TERMINATOR
4660916DATA_COMPRESSION
4661016SERDE_METHOD
4661116ENCODING
4661216STRING_DELIMITER
4661316DATE_FORMAT
4661416FIELD_TERMINATOR
4661516FORMAT_TYPE
4661616JOB_TRACKER_LOCATION
4661716EXTERNAL TABLE
4661816HADOOP
4661916RDBMS
4662016SHARD_MAP_MANGER
4662116SHARDING_COLUMN_NAME
4662216DISTRIBUTION
4662316DATABASE_NAME
4662416SHARD_MAP_NAME
4662516CREDENTIAL
4662616REMOTE_SCHEMA_NAME
4662716REMOTE_OBJECT_NAME
4662816SHARED_MEMORY
4662916EXTRACTOR
4664316external tables
4664416external tables for sharded data
4664516Remote Data Archive
4664616provided
4664716seconds
4664816minutes
4664916hours
4665016days
4665116weeks
4665216months
4665316years
4665416database scoped credential
4665516rejected rows location
4665616CONNECTION_OPTIONS
4665716PUSHDOWN
4665816GENERIC
4665916BLOB_STORAGE
4666016GENERIC
4666116CREATE EXTERNAL TABLE
4666216HASH
4666316PARTITION
4666416DROP EXTERNAL TABLE
4666516TRUNCATE EXTERNAL TABLE
4666616ALTER DATABASE
4666716DROP DATABASE
4670116Query notifications is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4670216Remote RPC requests are not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4670316Conversion error while attempting conversion between IPC blob parameter.
4670416Large object column support in SQL Server Parallel DataWarehouse server is limited to only nvarchar(max) data type.
4670516Unsupported parameter type found while parsing RPC request. The request has been terminated.
4670616Cursor support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4670716The given IPC request with code %d is not supported for SQL Server Parallel DataWarehousing TDS endpoint.
4670916Default parameter support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4671016Unsupported transaction manager request %d encountered. SQL Server Parallel DataWarehousing TDS endpoint only supports local transaction request for ‘begin/commit/rollback’.
4671116Unsupported TDS request packet of type %d encountered on SQL Server Parallel DataWarehousing TDS endpoint. Only batch, rpc and transaction requests are supported.
4671216Unexpected error encountered during request processing. Connection will be terminated.
4671316Integrated authentication is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4671616Attach Database File is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint.
4671716Login as Replication or Remote user is not supported by SQL Server Parallel DataWarehousing TDS endpoint.
4671816Only ‘us_english’ or ‘English’ language is supported by SQL Server Parallel DataWarehousing TDS endpoint.
4671916Attempt to reset connection with ‘Keep Transaction’ failed because the incoming request was not a commit/rollback request. This error can occur if more than one SqlConnection is used within the scope of a System.Transactions.Transaction.
4672016Parallel query execution on the same connection is not supported.
4672116Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication.
4672216Client driver version is not supported.
4672316Large object column in Global Query is not supported for types other than Nvarchar(MAX), Varchar(MAX), Varbinary(MAX) and Image.
4672416Communication error during bulk copy operation.
4680116GlobalQuery operations
4680216Failed to load module for global query.
4680316Failed to locate entry point for global query module.
4680416Failed to initialize the global query module.
4680516Conversion error while constructing the GlobalQuery request.
4680616An error occurred while executing GlobalQuery operation: %.*ls
4680716An access violation occurred while performing GlobalQuery operation. Execution has been aborted.
4680816An entry corresponding to given Global Query request could not be located. Execution has been aborted.
4680916An error occurred while attempting to execute the Global Query request. Error Code: %d, Severity: %d, State: %d.
4681016An unhandled exception occurred while performing GlobalQuery operation. Execution has been aborted.
4681116An unexpected error with code 0x%x occurred while executing GlobalQuery operation.
4681216%.*ls
4681316%.*ls
4681416%.*ls
4681516%.*ls
4681616%.*ls
4681716%.*ls
4681816%.*ls
4681916%.*ls
4682016%.*ls
4682116%.*ls
4682216%.*ls
4682316%.*ls
4682416%.*ls
4682516%.*ls
4682616Output parameters are not supported with %.*ls.
4682716The option ‘%ls’ must be turned ON to execute queries referencing external tables.
4682816The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint.
4682916The proc %.*ls is only supported for external data sources of type SHARD_MAP_MANAGER or RDBMS.
4683016Internal column references are not supported for external tables.
4683116Provided argument exceeds the current size limit of %u bytes for procedure %.*ls.
4690110Stored procedure finished successfully. Polybase engine service is disabled. Please restart Polybase DMS service.
4690210Stored procedure finished successfully. Polybase engine service is enabled. Please restart Polybase engine and DMS services.
4690310This stored procedure is not available because Polybase feature is not enabled.
4690416Failed to get the computer name. This might indicate a problem with the network configuration of the computer. Error: %ls.
4690510Head node cannot be removed from a Polybase computational group.
4690616Unable to retrieve registry value ‘%ls’ from Windows registry key ‘%ls’: %ls.
4690716Unable to delete registry value ‘%ls’ from Windows registry key ‘%ls’: %ls.
4690816Unable to update registry value ‘%ls’ in Windows registry key ‘%ls’: %ls.
4690916Unable to open registry key ‘%ls’: %ls.
4691016Incorrect number of parameters specified for procedure.
4691116Procedure expects parameter ‘%ls’ of type ‘%ls’.
4691216The option ‘%ls’ must be turned ON to execute requests referencing external tables.
4691316The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint.
4691416INSERT into external table is disabled. Turn on the configuration option ‘allow polybase export’ to enable.
4691516Table hints are not supported on queries that reference external tables.
4691616Queries that reference external tables are not supported by the legacy cardinality estimation framework. Ensure that trace flag 9481 is not enabled, the database compatibility level is at least 120 and the legacy cardinality estimator is not explicitly enabled through a database scoped configuration setting.
4691716An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
4691816An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
4691916An internal error occured while attempting to retrieve the encrypted database-scoped credential secret.
4692010Polybase feature disabled.
4692116The EXECUTE AT DATA_SOURCE command is not supported for this external data source type.
4692221PolyBase provisioning script performing on master database failed. This is a serious error which might prevent the SQL Server instance from starting. Examine the errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the steps run to completion.
4692316PolyBase feature is not installed. Please consult Books Online for more information on this feature.
4692416SQL failed to start PolyBase for error code 0x%lx.
4692516SQL failed to start PolyBase request for error code 0x%lx.
4692616Failed to get polybase service account due to error ‘%ls’.
4700010Reason: FedAuth RPS Initialization failed when fetching CLSID of RPS ProgID.
4700110Reason: FedAuth RPS Initialization failed when creating instance of Passport.RPS COM Object.
4700210Reason: FedAuth RPS Initialization failed when initializing the RPS COM object.
4700310Reason: FedAuth RPS Authentication failed when getting IRPSAuth object.
4700410Reason: FedAuth RPS Authentication failed when getting IRPSPropBag object.
4700510Reason: FedAuth RPS Authentication failed during IRPS::Authenticate.
4700610Reason: FedAuth RPS Authentication failed when getting IRPSValidatedPropertyBag object.
4700710Reason: FedAuth RPS Authentication failed during SetAuthPolicy.
4700810Reason: FedAuth RPS Authentication failed during ValidateTicketWithAuthPolicy.
4700910Reason: FedAuth RPS Authentication failed when fetching Session Key.
4701010Reason: FedAuth RPS Authentication failed when initializing HMAC Hash object.
4701110Reason: FedAuth RPS Authentication failed when computing HMAC Hash Signature.
4701210Reason: FedAuth RPS Authentication failed when comparing HMAC Hash Signature with the one sent by the client.
4701310Reason: FedAuth RPS Authentication failed when fetching MemberId Low.
4701410Reason: FedAuth RPS Authentication failed when fetching MemberId High.
4701510Reason: FedAuth RPS Authentication failed when fetching MemberName.
4701610Reason: FedAuth AzureActiveDirectoryService Initialization failed when opening Certificate Store.
4701710Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to find ceritificate in store.
4701810Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to initialize Error object for service proxy.
4701910Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to create service proxy.
4702010Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to open service proxy.
4702110Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Heap object.
4702210Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Error object.
4702310Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during Group Membership Lookup.
4702410Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during validation of federated context.
4702510Reason: FedAuth AzureActiveDirectoryService Group Expansion failed due to unknown reason.
4702610Reason: Failure occurred when trying to fetch the HMAC signature of prelogin client nonce to set FeatureExtAck
4702710Reason: This was a non-Microsoft domain login attempt in a Non-SDS session.
4702810Reason: This FedAuth library is not supported by the security layer for authentication.
4702910Reason: This FedAuth Ticket type is not supported by the security layer for authentication.
4703010Reason: The Feature Switch for this FedAuth protocol is OFF.
4703110Reason: There was a failure in acquiring the max heap memory limit from config during AAD group expansion.
4703210Reason: There is a user error in FedAuth token parsing. There should be a seperate XEvent called ‘fedauth_web_token_failure’ which indicate the actual error code
4703310Reason: There is a System error in FedAuth token parsing. There should be a seperate XEvent called ‘fedauth_web_token_failure’ which indicate the actual error code
4703410Reason: Authentication was successful, but database is in Recovering state.
4703510Reason: Login failed because it was attempting to use integrated authentication, which we do not support.
4703610Reason: Login failed because USE db failed while checking firewall rules.
4703710Reason: Login failed because Deny External Connections flags is on.
4703810Reason: Login failed because client disconnected when fedauth specific processing was going on during login.
4703910Reason: Login failed because the client is attempting to use certificate authentication without correct permissions.
4704010Reason: Login failed because database is not found.
4704110Reason: Login failed because login token feature extension is not present.
4704210Reason: Login failed because login token feature extension is malformed.
4704310 Reason: Token-based server access validation failed with an infrastructure error. Login is disabled.
4704410 Reason: Login-based server access validation failed with an infrastructure error. Login is disabled.
4704510 Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission.
4704610 Reason: Login-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission.
4704710 Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission.
4704810 Reason: Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission.
4704910 Reason: VNET Firewall Rule has rejected the login.
4705010 Reason: Unexpected error while copying the VNET IPv6 address.
4705110 Reason: Unexpected error while parsing the VNET IPv6.
4705210 Reason: Unexpected error while extracting VNET metadata info from the IPv6 (VNET parsing).
4705310 Reason: Unexpected error on VNET firewall rule table lookup.
4705410 Reason: Unexpected error on VNET firewall rule table COUNT lookup.
4705510 Reason: VNET Firewall rejected the login due to a the source of a login being outside a VNET
4705610 Reason: Firewall rejected the login attempt because VNET firewall rules are not database-level, only server-level.
4705710 Reason: Firewall rejected the login because an IPv6 attempt was received when not expected
4705810 Reason: Unexpected error on VNET firewall rule table lookup while looking up the IPv4 Allow All rule.
4705910 Reason: Unexpected error while swapping the session peer address with the VNET CA.
4706010 Reason: Unexpected error on TDS readhandler, payload length > sni packet buf size
4706110 Reason: Replicated Master is not ready at this point and user connections are disallowed.
4706210 Reason: lock timeout expired while looking up interface endpoints list
4706310 Reason: lock timeout expired while looking up interface endpoints list
4706410 Reason: The incoming login VNET metadata was not found in the list of interface endpoints configured
4706510 Reason: Unexpected error on Interface Endpoints access lockdown check
4706610 Reason: Allow All Azure rule can’t be evaluated at DB level Firewall Rule for Interface Endpoints connections
4706710 Reason: Internal error. Unexpected frontend connection to Vldb page server.
4706810fulltext stoplist
4710016The cluster type of availability group ‘%.*ls’ doesn’t match its primary configuration.  Verify that the specified availability group cluster type is correct, then retry the operation.
4710116The cluster type of availability group ‘%.*ls’ only supports MANUAL failover mode.  Verify that the specified availability group cluster type is correct, then retry the operation.
4710216The cluster type of availability group ‘%.*ls’ only supports EXTERNAL failover mode.  Verify that the specified availability group cluster type is correct, then retry the operation.
4710316The cluster type of availability group ‘%.*ls’ only supports AUTOMATIC and MANUAL failover modes.  Verify that the specified availability group cluster type is correct, then retry the operation.
4710416This operation cannot be performed on the availability group ‘%.*ls’ because it has EXTERNAL cluster type. Use the cluster management tools to perform the operation.
4710516The Always On Availability Groups feature must be enabled for this server instance before you can perform availability group operations. Please enable the feature, then retry the operation.
4710616Cannot join availability group ‘%.*ls’. Download configuration timeout. Please check primary configuration, network connectivity and firewall setup, then retry the operation.
4710716The %ls operation is not allowed by the current availability group configuration. The availability group ‘%.*ls’ only supports one relica which has configuration-only availability mode. Verify that the specified availability group availability mode is correct, then retry the operation.
4710816The %ls operation is not allowed by the current availability group configuration. The availability group ‘%.*ls’ only supports two synchronous mode replicas and required_syncrhonized_secondaries_to_commit is zero when configuration-only mode replica is specified. Verify that the specified availability group availability mode is correct, then retry the operation.
4710916Availability group ‘%.*ls’ cannot failover to this replica. Configuration-only replica cannot become primary. An attempt to fail over an availability group failed. The replica is a configuration-only and cannot become a primary.
4711015The ‘%.*ls’ option is not valid for the ‘%.*ls’ replica as it is a configuration-only. Remove this option, then retry the operation
4711116Local availability replica for availability group ‘%.*ls’ cannot be granted permission to create databases. The replica is a configuration-only and cannot host databases inside the availability group.
4711216Only the SESSION_TIMEOUT property can be modified for a configuration-only replica.
4711316The ‘%.*ls’ option is not valid for the ‘%.*ls’ replica for modification. Remove this option, then retry the operation.
4711416Availability replica ‘%.*ls’ cannot be added to availability group ‘%.*ls’. Configuration-only replicas can only be added to availability groups with CLUSTER_TYPE = EXTERNAL.  Verify that the AVAILABILITY_MODE setting of the replica spec, then retry the operation.
4711516The ‘%ls’ option is not valid for WSFC availability group ‘%.*ls’. Remove the option or set the ‘CLUSTER_TYPE’ option to a different value, then retry the operation.
4711616The external lease cannot be set on availability group ‘%.*ls’. External Lease updates are not enabled for this availability group.
4711716The ‘%ls’ option must be specified with a valid time value when updating the Availability Group’s external write lease status on availability group ‘%.*ls’.
4711816The ‘%ls’ option must be specified with a valid value when updating the external lease status on availability group ‘%.*ls’.
4711916The current write lease of the availability group ‘%.*ls’ is still valid. The lease expiration time cannot be set to an earlier time than its current value.
4712016The READ_WRITE_ROUTING_URL ‘%.*ls’ specified for availability replica ‘%.*ls’ is not valid. It does not follow the required format of ‘TCP://system-address:port’. For information about the correct routing URL format, see the CREATE AVAILABILITY GROUP documentation in SQL Server Books Online.
4712116The replica spec for the local replica ‘%.*ls’ has an invalid availability mode. Valid values are SYNCHRONOUS_COMMIT and ASYNCHRONOUS_COMMIT.
4712216Cannot failover an availability replica for availability group ‘%.*ls’ since it has CLUSTER_TYPE = NONE. Only force failover is supported in this version of SQL Server.
4712316Creating contained availability group ‘%.*ls’ failed. No other availability groups can exist before creating contained availability group. Verify specified availability group availability options are correct, then retry the operation.
4712416Creation of contained availability group master database failed. Only contained availability group can create contained availability group master database. Verify availability group availability options are correct, then retry the operation.
4712516Joining contained availability group ‘%.*ls’ has failed. Verify there is no other availability group existed, then retry the operation.
4712616Joining contained availability group ‘%.*ls’ failed. Verify that user databases are not present, then retry the operation.
4712716Joining or creating contained availability group ‘%.*ls’ failed. The SQL Server instance is not enabled to create or join contained availability group.
4712916Creating Distributed availability group ‘%.*ls’ has failed. Cannot create Distributed Availability Group on top of Contained Availability Group. Verify Availability Group’s name, then retry the operation.
4713016Creating contained availability group ‘%.*ls’ failed. When creating contained availability group, both master database and msdb database must be included in contained availability group. Include master and msdb in CREATE AVAILABILITY GROUP statement and retry the operation.
4713116Creating or joining availability group ‘%.*ls’ failed because there is a contained availability group. Remove contained availability group, then retry the operation.
4713216Joining availability group ‘%.*ls’ with rebuilding contained system DB has failed because rebuilding contained MSDB has failed. This is caused by contained MSDB is still used. Retry the operation later.
4713316Joining availability group ‘%.*ls’ with rebuilding contained system databases has failed because rebuilding contained availability group master database has failed. This is caused by contained availability group master database still being used. Reconnect to master database at SQL Server instance level and retry the operation later.
4713416Joining availability group ‘%.*ls’ with ‘REBUILD_SYSTEM_DATABASES’ has failed. ‘REBUILD_SYSTEM_DATABASES’ is only valid for joining contained availability group. Remove the option and retry the operation.
4713516Contained availability group system database ‘%.*ls’ cannot be removed from contained availability group ‘%.*ls’.
4713616Cannot add database ‘%.*ls’ to contained availability group ‘%.*ls’ because it is in the exclusion list. Remove the excluded database from the database list and retry the operation.
4713716Cannot create contained system databases in contained availability group ‘%.*ls’ It might be caused by temporary condition. Retry the operation.
4713816Joining contained availability group ‘%.*ls’ without rebuilding contained system DB has failed because availability group master ‘%.*ls’ had incorrect db id ‘%ld’. Please use rebuild_system_databases option or remove availability group contained master manually, then retry the operation again.
4713916Join contained availability group ‘%.*ls’ failed to create group master ‘%.*ls’ Database ID. Please retry the operation again.
4714016Starting contained availability group ‘%.*ls’ failed. Contained availabiity group system database ‘%.*ls’ (id = %d) failed to load during startup.
4714116Starting contained availability group ‘%.*ls’ failed. One of constained system databases (masterdbid = %d, msdbid = %d) failed to load during startup.
4714216Creating contained availability group ‘%.*ls’ failed. One of contained system database ‘%.*ls’ already exists. Remove it or add ‘reuse_system_databases’ option, then retry the operation again.
4714316Option ‘reuse_system_databases’ is invalid for creating availability group ‘%.*ls’. Option ‘reuse_system_databases’ can only be used with contained availability group. Correct the option and retry the operation.
4714516Failed to obtain the resource handle for cluster resource with name or ID ‘%.*ls’. Cluster service may not be running or may not be accessible in its current state, or the specified cluster resource name or ID is invalid.  Otherwise, contact your primary support provider.
4720116Procedure expects ‘%u’ parameters.
4720216Procedure expects ‘%u’ parameters and ‘%u’ for _ex version.
4720316Procedure expects at least ‘%u’ parameters and ‘%u’ max.
4940116Database backup not supported on this database as it has foreign files attached.
4940216Failed to initialize the covering resilient buffer pool extension for foreign file ‘%.*ls’ with HRESULT 0x%x.
4940317Database ‘%.*ls’ does not allow autostart operations. An explicit ONLINE database operation is required.
4940416Value ‘%.*ls’ for option ‘%.*ls’ is not supported in this version of SQL Server.
4940517Skipping the default startup of vldb database ‘%.*ls’. The database will be started by the fabric. This is an informational message only. No user action is required.
4940616Recovery modes other than full are not supported in this version of SQL Server.
4940716Error: %ls.
4940816Error: %ls. Error code: %d.
4940916Special procedure is not available on the current SQL instance.
4941016Change tracking is currently not supported in this version of SQL Server.
4941116Couldn’t register the database in the page server database map.
4950116DBCC SHRINKFILE for %.*ls is aborted. Sbs flat files are not supported
4950210%.*ls: Page %d:%d could not be moved because it is an sbs flat file page or the destination is an sbs flat file page.
4950310%.*ls: Page %d:%d could not be moved because it is an off-row persistent version store page. Page holdup reason: %ls. Page holdup timestamp: %I64d.
4950410Error updating failover proc.
4950516Registering extended stored procedure failed because it is not valid to use UNC path for DLL name. Use local path for DLL name instead.
4950616The DBCC operation failed because it is not supported in an explicit transaction when Accelerated Database Recovery is enabled on the database. Commit or rollback the current transaction and run the operation again.
4950716Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row is aborted.
4950816DBCC SHRINKFILE for data files is not supported in this version of SQL Server.
4950916DBCC SHRINKFILE for PMM files is not supported in this version of SQL Server.
4951016Managed instance is busy with another operation. Please try your operation later.
4951110Unable to set one or more trace flags. Unsupported trace flag(s): %ls%ls%ls.
4951210Session level trace flags are not supported on managed instance.
4951310%lsDBCC %ls for databese id %d terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds.  %.*ls
4951410%lsDBCC %ls for databese id %d found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds.  %.*ls
4960022SQL tiered storage table schema is corrupt.
4960216Failure waiting for %ls latch in ‘%ls’.
4960316CREATE FILE encountered operating system error %ls while attempting to copy the physical file ‘%.*ls’.
4970110Server override on the category is not supported yet (Server: ‘%.*ls’, Category: ‘%.*ls’).
4970210The category name is either invalid or not supported yet. Server: ‘%.*ls’. CategoryName: ‘%.*ls’.
4970310Failed to parse server override on server ‘%.*ls’. The category name is: ‘%.*ls’ and the override string is: ‘%.*ls’.
4970410Failed to apply server override on category ‘%.*ls’, because physical db or instance ‘%.*ls’ in server ‘%.*ls’ is currently not in ‘Ready’ or ‘Deactivated’ state.
4970510Failed to merge server override into property bag on physical db or instance ‘%.*ls’ of server ‘%.*ls’. The override string is: ‘%.*ls’.
4971610Database override on the category is not supported yet (Server: ‘%.*ls’, Database: ‘%.*ls’, Category: ‘%.*ls’).
4971710Failed to apply database override on category ‘%.*ls’, because physical db or instance ‘%.*ls’ in server ‘%.*ls’ is currently not in ‘Ready’ or ‘Deactivated’ state.
4971810The category name is either invalid or not supported yet. Server: ‘%.*ls’. Database: ‘%.*ls’. CategoryName: ‘%.*ls’.
4980110Dynamic Deactivation Timer task encountered an error (SQL Error Code: %d).  Refer to the xel for more details.
4980210Database is unavailable at the moment, please retry connection at later time.
4980310Resource Pool Data Space Usage Timer task encountered an error (SQL Error Code: %d).
4980410Database cannot be deactivated: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4980510DynamicActivation feature switch is off for Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4980610DynamicActivation feature switch is not enabled for all remote storage DB: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4980710DynamicActivation is only supported for remote storage DB: Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4980810Deactivated database cannot be deactivated again: Server ‘%.*ls’, Database ‘%.*ls’
4980910Database Operation failed for Server ‘%.*ls’, Database ‘%.*ls’ due to unexpected delay. Please try again.
4981010Workflow failed due to throttling: Server ‘%.*ls’, Database ‘%.*ls’
4981110Deactivation is not supported on Disabled database: Server ‘%.*ls’, Database ‘%.*ls’
4981210EnableForceNoBackupDeactivation is not enabled: Server ‘%.*ls’, Database ‘%.*ls’
4981310Deactivation is not supported on databases part of servers in global transaction partnership: Server ‘%.*ls’, Database ‘%.*ls’
4981410DynamicActivation is not supported for GeoDR DB: Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4981510Database cannot be deactivated: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’
4981610Server ‘%.*ls’, Database ‘%.*ls’ cannot be online as BlockingMode is set
4981710Failed to query CMS for thottling on database ‘%.*ls’, ‘%.*ls’ due to the exception: ‘%.*ls’
4981810Cannot deactivate a database when it is already getting deactivated, Server ‘%.*ls’, Database ‘%.*ls’
4981910Deflation Monitor Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details.
4982010Managed Server Resource Stats Timer task encountered an error (SQL Error Code: %d).
4982110Rg Metrics Reporting Timer task encountered an error (SQL Error Code: %d).
4982210Move Cost Calculation and Reporting Timer task encountered an error (SQL Error Code: %d).
4990110The number of max worker threads that is configured %u is less than the minimum allowed on this computer. The default number of %u will be used instead. To change the number of max worker threads, use sp_configure ‘max worker threads’.
4990210There are not enough worker threads available for the number of CPUs. This is because one or more CPUs were added. To increase the number of worker threads, use sp_configure ‘max worker threads’.
4990310Detected %I64d MB of RAM. This is an informational message; no user action is required.
4990410The service account is ‘%.*ls’. This is an informational message; no user action is required.
4990510Error %u occurred while opening parameters file ‘%s’. Verify that the file exists, and if it exists, verify that it is a valid parameters file.
4990610Error %u occurred while processing parameters from either the registry or the command prompt. Verify your parameters.
4990710Ignored deprecated SQL Server startup parameters from the registry: %.*ls
4990810The following SQL Server startup parameters are either deprecated or incorrectly specified: %.*ls
4990910Multiple instances of SQL server are installed on this computer. Renter the command, specifying the -s parameter with the name of the instance that you want to start.
4991010Software Usage Metrics is disabled.
4991110Software Usage Metrics failed to start.
4991210Software Usage Metrics is enabled.
4991310The server could not load DCOM. Software Usage Metrics cannot be started without DCOM.
4991410%ls Trace: %ls
4991510Invalid, incomplete, or deprecated parameters were found in the command line or in the registry. Normally those would be ignored but the ‘%s’ parameter was specified which cause SQL Server to exit. Remove the offending parameters. Check the error log for further details.
4991610UTC adjustment: %d:%02u
4991710Default collation: %ls (%ls %u)
4991816Cannot process request. Not enough resources to process request. Please retry your request later.
4991916Cannot process create or update request. Too many create or update operations in progress for subscription “%ld”. Query sys.dm_operation_status for pending operations. Wait till pending create/update requests are complete or delete one of your pending create/update requests and retry your request later.
4992016Cannot process request. Too many operations in progress for subscription “%ld”. Query sys.dm_operation_status for pending operations and wait till the operation is complete or delete one of the pending requests and retry later.
4992110Total Log Writer threads: %ld. This is an informational message; no user action is required.
4992216Unable to process ‘%s’ notification for subscription ‘%ld’ because it contains ‘%d’ child resources
4992416Subscription ‘%ld’ does not support creating a database with selected service level objective ‘%ls’. Try creating a database with different service level objective.
4992516Databases cannot be updated to free service level objective.
4992610Server setup is starting
4992710An error occurred while setting the server administrator (SA) password: error %d, severity %d, state %d.
4992810An error occurred during server setup. See previous errors for more information.
4992910Server setup completed successfully.
4993010Parallel redo is %ls for database ‘%.*ls’ with worker pool size [%d].
4993110An error occurred while configuring engine telemetry: error %d, severity %d, state %d.
4993210An error occurred while initializing security. %ls.
4993310ERROR: The MSSQL_SA_PASSWORD environment variable must be set when using the –reset-sa-password option.
4993410Error %u occurred while reading the RbIo configuration parameters. Verify that the sqlservr.ini or registry entries exist.
4993510Enclave of type %d initialized successfully.
4993610ERROR: The provided PID [%s] is invalid.  The PID must be in the form #####-#####-#####-#####-##### where ‘#’ is a number or letter.
4993710ERROR: A failure occurred in the licensing subsystem. Error [%d].
4993810The licensing PID was successfully processed. The new edition is [%s].
4993916Unable to initialize user-specified certificate configuration. The server is being shut down. Verify that the certificate is correctly configured. Error[%d]. State[%d].
4994016Unable to open one or more of the user-specified certificate file(s). Verify that the certificate file(s) exist with read permissions for the user and group running SQL Server.
4994116Unable to load one or more of the user-specified certificate file(s). Verify that the certificate file(s) are of a supported format.
4994216Internal error occurred initializing user-specified certificate configuration. Error code [%08X].
4994310The certificate [Certificate File:’%hs’, Private Key File:’%hs’] was successfully loaded for encryption.
4994416The allowed TLS protocol version list [‘%hs’] is invalid. Verify that the supplied TLS version numbers are supported by SQL Server and separated by spaces in the configuration.
4994516The allowed TLS cipher list [‘%hs’] is invalid. See docs.microsoft.com for more information on creating a cipher list.
4994616Internal error occurred initializing the TLS configuration. Error code [%d].
4994716Unable to initialize the TLS configuration. The server is being shut down. Verify that the allowed TLS protocol and cipher lists are configured correctly. Error state [%d].
4994810Successfully initialized the TLS configuration. Allowed TLS protocol versions are [‘%hs’]. Allowed TLS ciphers are [‘%hs’].
4994910ERROR: Unable to set system administrator password: %s.
4995010The SQL Server End-User License Agreement (EULA) must be accepted before SQL
4995110Server can start. The license terms for this product can be downloaded from
4995210http://go.microsoft.com/fwlink/?LinkId=746388.
4995310You can accept the EULA by specifying the –accept-eula command line option,
4995410setting the ACCEPT_EULA environment variable, or using the mssql-conf tool.
4995510Environment Variable Startup Parameters:%.*ls
4995610The default language (LCID %d) has been set for engine and full-text services.
4995710The default language (LCID %d) failed to be set for engine and full-text services.
4995821The server collation cannot be changed with user databases attached. Please detach user databases before changing server collation.
4995910ERROR: The environment variable MSSQL_COLLATION contains an invalid collation ‘%.*ls’.
4996010Did not find an existing master data file %s, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
4996110Setup step is %scopying system data file ‘%s’ to ‘%s’.
4996210ERROR: Setup FAILED copying system data file ‘%s’ to ‘%s’:  %s
4996310ERROR: ‘%s’ is a directory. Cannot continue.
4996410ERROR: Setup failed to create the system data directory ‘%s’: %s
4996510Unable to load cluster root CA certificate due to OSError:’%s’.
4997216Cannot add tempdb remote file to local tempdb filegroup in transition to primary.
4997316Cannot remove tempdb remote file to local tempdb filegroup in transition to primary.
4997510Unable to load controller client certificate due to OSError:’%s’.