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
ErrorCode | Severity | ErrorMessage |
35001 | 16 | Parent Server Group does not exist. |
35002 | 16 | Server type and parent Server Group type are not the same |
35003 | 16 | Cannot move node to one of its children |
35004 | 16 | Could not find server group |
35005 | 16 | An invalid value NULL was passed in for @server_group_id. |
35006 | 16 | An invalid value NULL was passed in for @server_id. |
35007 | 16 | Could not find shared registered server. |
35008 | 16 | Cannot delete system shared server groups. |
35009 | 16 | An invalid value NULL was passed in for @server_type. |
35010 | 16 | An invalid value %d was passed in for parameter @server_type. |
35011 | 16 | The @server_name parameter cannot be a relative name. |
35012 | 16 | You cannot add a shared registered server with the same name as the Configuration Server. |
35100 | 16 | Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647. |
35101 | 16 | One of the SET options FMTONLY or NOEXEC was changes from ON to OFF in a TRY…CATCH block. |
35200 | 16 | Failed to add database ‘%.*ls’ to availability group ‘%.*ls’. The specified availability group is created with basic functionality and supports %d database. |
35201 | 10 | A 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. |
35202 | 10 | A 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. |
35203 | 16 | Unable to establish a connection between instance ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] due to a transport version mismatch. |
35204 | 10 | The 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. |
35205 | 16 | Could 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. |
35206 | 10 | A 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. |
35207 | 16 | Connection attempt on availability group id ‘%ls’ from replica id ‘%ls’ to replica id ‘%ls’ failed because of error %d, severity %d, state %d. |
35208 | 16 | Availability-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. |
35209 | 16 | The %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. |
35210 | 16 | Failed 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. |
35211 | 16 | The %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. |
35212 | 16 | The %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. |
35213 | 16 | The %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. |
35214 | 16 | The %ls operation failed for availability replica ‘%.*ls’. The minimum value for session timeout is %d. Retry the operation specifying a valid session-timeout value. |
35215 | 16 | The %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. |
35216 | 16 | An 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. |
35217 | 16 | 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. |
35218 | 16 | An 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. |
35220 | 16 | Could 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. |
35221 | 16 | Could 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. |
35222 | 16 | Could 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. |
35223 | 16 | Cannot 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. |
35224 | 16 | Could 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. |
35225 | 16 | Could 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. |
35226 | 16 | Could 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. |
35228 | 16 | The 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. |
35229 | 16 | The 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. |
35230 | 16 | The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name. |
35231 | 16 | The specified server instance name, ‘%ls’, is invalid. Reenter the command specifying a valid instance name. |
35232 | 16 | The 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. |
35233 | 16 | Cannot 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. |
35234 | 16 | Database name ‘%ls’ was specified more than once. Reenter the command, specifying each database name only once. |
35235 | 16 | The 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. |
35236 | 15 | The 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. |
35237 | 16 | None 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. |
35238 | 16 | Database ‘%.*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. |
35239 | 16 | The 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. |
35240 | 16 | Database ‘%.*ls’ cannot be joined to or unjoined from availability group ‘%.*ls’. This operation is not supported on the primary replica of the availability group. |
35242 | 16 | Cannot 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. |
35243 | 16 | Failed 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. |
35244 | 16 | Database ‘%.*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. |
35246 | 16 | Failed 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. |
35247 | 16 | Failed 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). |
35248 | 16 | The %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. |
35249 | 16 | An attempt to add or join a system database, ‘%.*ls’, to an availability group failed. Specify only user databases for this operation. |
35250 | 16 | The connection to the primary replica is not active. The command cannot be processed. |
35251 | 16 | This command can be run only on the primary replica. Connect to the primary replica, and retry the command. |
35252 | 16 | The command can only be run on a secondary database. Connect to the correct secondary replica, and retry the command. |
35253 | 16 | Database “%.*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. |
35254 | 16 | An 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. |
35255 | 16 | An attempt to start database ‘%.*ls’ failed because the database is already started and online. |
35256 | 16 | The 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. |
35257 | 16 | 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. |
35258 | 16 | Error in the hadron simulator. |
35259 | 16 | Database ‘%.*ls’ is already participating in a different availability group. |
35260 | 16 | 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. |
35261 | 16 | 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. |
35262 | 10 | Skipping 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. |
35263 | 16 | During 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. |
35264 | 10 | Always 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. |
35265 | 10 | Always On Availability Groups data movement for database ‘%.*ls’ has been resumed. This is an informational message only. No user action is required. |
35266 | 10 | Always 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. |
35267 | 10 | Always 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. |
35268 | 16 | Synchronization 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. |
35269 | 21 | Synchronization 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. |
35270 | 10 | Received a corrupt FileStream transport message. The ‘%ls’ message section is invalid. |
35271 | 16 | The 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. |
35272 | 16 | Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure. |
35273 | 10 | Bypassing 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. |
35274 | 10 | Recovery 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. |
35275 | 16 | A 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. |
35276 | 17 | Failed 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. |
35277 | 16 | Automatic failover is not supported for distributed availability group replica. |
35278 | 16 | Availability 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. |
35279 | 16 | The 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. |
35280 | 16 | Database ‘%.*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. |
35281 | 16 | Database ‘%.*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. |
35282 | 16 | Availability 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. |
35283 | 16 | Availability 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. |
35284 | 16 | Availability 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. |
35285 | 10 | The recovery LSN %S_LSN was identified for the database with ID %d. This is an informational message only. No user action is required. |
35286 | 16 | Using 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. |
35287 | 16 | Always 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. |
35288 | 16 | Always 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. |
35289 | 16 | Failed to send request for file ‘%.*ls’ to the ‘%.*ls’ primary database for the local secondary database. Resuming the database will be retried automatically. |
35290 | 16 | Failed to wait for completion of file requests from the ‘%.*ls’ primary database for the local secondary database. Resuming the database will be retried automatically. |
35291 | 10 | Failed 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. |
35292 | 16 | An internal error occurred when performing an operation on extended recovery forks. This is an informational message only. No user action is required. |
35293 | 16 | Error 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. |
35294 | 16 | Log 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. |
35295 | 16 | Log 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. |
35296 | 16 | 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. |
35297 | 10 | Log 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. |
35298 | 10 | The 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. |
35299 | 10 | Nonqualified 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. |
35301 | 15 | The 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. |
35302 | 15 | The 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. |
35303 | 15 | The 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. |
35304 | 15 | The 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. |
35305 | 15 | The 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. |
35306 | 15 | The statement failed because a columnstore index cannot be specified using INDEX specification at the column level. |
35307 | 15 | The statement failed because column ‘%.*ls’ on table ‘%.*ls’ is a computed column. Columnstore index cannot include a computed column implicitly or explicitly. |
35308 | 15 | The statement failed because a columnstore index cannot be a filtered index. Consider creating a columnstore index without the predicate filter. |
35309 | 15 | The 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. |
35310 | 15 | The 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. |
35311 | 15 | The statement failed because a columnstore index cannot have included columns. Create the columnstore index on the desired columns without specifying any included columns. |
35312 | 15 | The 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. |
35313 | 15 | The 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. |
35314 | 15 | The 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. |
35315 | 15 | The 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. |
35316 | 15 | The 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. |
35317 | 15 | The statement failed because specifying %S_MSG is not allowed when creating a columnstore index. Consider creating a columnstore index without specifying %S_MSG. |
35318 | 15 | The 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. |
35319 | 15 | The table option DATA_COMPRESSION is not allowed when a table specifies a clustered column store index. |
35320 | 15 | Column store indexes are not allowed on tables for which the durability option SCHEMA_ONLY is specified. |
35321 | 16 | Table ‘%.*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. |
35322 | 16 | The 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. |
35323 | 16 | The 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. |
35324 | 15 | The 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. |
35325 | 15 | The 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. |
35326 | 15 | The statement failed because a nonclustered columnstore index cannot be reorganized. Reorganization of a nonclustered columnstore index is not necessary. |
35327 | 15 | ALTER INDEX REBUILD statement failed because specifying %S_MSG is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying %S_MSG. |
35328 | 15 | ALTER 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. |
35329 | 15 | The 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. |
35330 | 16 | %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. |
35331 | 16 | Cannot use duplicate column names in the ORDER column list. Column name ‘%.*ls’ appears more than once. |
35332 | 16 | Cannot ORDER on more than %d columns. |
35334 | 15 | DBCC DBREINDEX failed because specifying FILLFACTOR is not allowed when creating or rebuilding a columnstore index. Rebuild the columnstore index without specifying FILLFACTOR. |
35335 | 15 | The 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. |
35336 | 15 | The statement failed because specifying key list is missing when creating an index. Create the index with specifying key list . |
35337 | 16 | UPDATE STATISTICS failed because statistics cannot be updated on a columnstore index. UPDATE STATISTICS is valid only when used with the STATS_STREAM option. |
35338 | 16 | Clustered columnstore index is not supported. |
35339 | 16 | Multiple columnstore indexes are not supported. |
35340 | 16 | LOB columns are disabled in columnstore. |
35341 | 16 | The 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’. |
35342 | 15 | The 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. |
35343 | 15 | The statement failed. Column ‘%.*ls’ has a data type that cannot participate in a columnstore index. |
35344 | 16 | MERGE 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. |
35345 | 16 | MERGE 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. |
35346 | 16 | SPLIT 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. |
35347 | 16 | The 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. |
35348 | 16 | The 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. |
35349 | 16 | TRUNCATE 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. |
35350 | 16 | The 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. |
35351 | 16 | DROP 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. |
35352 | 16 | %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. |
35353 | 16 | %s cannot be enabled on a table with a clustered columnstore index. Consider dropping clustered columnstore index ‘%s’ on table ‘%s’. |
35354 | 16 | The 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. |
35355 | 16 | The 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. |
35356 | 16 | This operation is not supported on nonclustered columnstore indexes built in earlier versions of SQL Server. Consider rebuilding the index. |
35357 | 16 | The 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. |
35358 | 16 | CREATE 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. |
35359 | 16 | The 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. |
35360 | 16 | Referential constraint ‘%.*ls’ cannot be created because the %S_MSG table ‘%.*ls’ has a clustered columnstore index. |
35361 | 16 | The statement failed. A clustered columnstore index cannot be created over referencing column ‘%.*ls’ on table ‘%.*ls’. |
35363 | 16 | The statement failed because clustered columnstore indexes are not supported in system databases. |
35364 | 16 | ALTER INDEX statement option COMPRESSION_DELAY can only be used with columnstore indexes. |
35365 | 22 | The compression block header at offset %ld is invalid. |
35366 | 22 | The columnstore blob Xpress header is invalid. |
35367 | 22 | The columnstore blob Xpress object header is invalid. |
35368 | 17 | Internal DDL Operation Error: The DDL encountered an unexpected error %d during execution (HRESULT = 0x%x). |
35369 | 16 | GETCHECKSUM can not be used for a table which has a clustered columnstore index. |
35370 | 16 | Cursors are not supported on a table which has a clustered columnstore index. |
35371 | 16 | SNAPSHOT isolation level is not supported on a table which has a clustered columnstore index. |
35372 | 16 | You cannot create more than one clustered index on %S_MSG ‘%.*ls’. Consider creating a new clustered index using ‘with (drop_existing = on)’ option. |
35373 | 16 | ALTER INDEX REORGANIZE statement failed on a clustered columnstore index with error %d. See previous error messages for more details. |
35374 | 16 | Columnstore archive decompression failed with error %d. |
35375 | 16 | ALTER INDEX REORGANIZE statement option COMPRESS_ALL_ROW_GROUPS can only be used with clustered columnstore indexes. |
35376 | 16 | Tuple mover stvf got passed invalid arguments |
35378 | 16 | Row groups stvf got passed invalid arguments |
35379 | 16 | Internal 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. |
35380 | 16 | The non-clustered columnstore index ‘%.*ls’ on table ‘%.*ls’ cannot be reorganized due to an active snapshot transaction. |
35381 | 22 | The columnstore blob dictionary header is invalid. |
35382 | 16 | The 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. |
35383 | 16 | The use of user-defined functions is not allowed in default constraints when adding columns to a columnstore index. |
35384 | 16 | The 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. |
35386 | 17 | Unable 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. |
35387 | 17 | TEMPDB 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. |
35388 | 15 | The 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. |
35389 | 15 | The 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. |
35390 | 16 | Computed columns in columnstore indexes are temporarily disabled. Please rewrite your query to exclude computed columns. |
35391 | 16 | Could 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. |
35392 | 15 | The 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. |
35393 | 16 | Columnstore tuple mover unit tests can’t be run under master database. |
35394 | 16 | Transaction %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. |
35395 | 16 | Transaction %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. |
35396 | 17 | Effective 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. |
35397 | 16 | %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. |
35398 | 16 | Columnstore index operation failed. Please contact Microsoft customer support. |
35401 | 10 | ONLINE |
35402 | 10 | ALLOW_ROW_LOCKS |
35403 | 10 | ALLOW_PAGE_LOCKS |
35404 | 16 | sequence |
35405 | 10 | decryption |
35406 | 10 | creation |
35409 | 10 | Replication |
35410 | 10 | Change Tracking |
35411 | 10 | Change Data Capture |
35412 | 16 | CloudDB Async Transport |
35413 | 16 | CloudDB Async Transport Forwarder |
35415 | 10 | mirrored |
35417 | 10 | primary |
35418 | 10 | secondary |
35419 | 16 | feature |
35420 | 16 | operation |
35421 | 16 | statement |
35422 | 16 | index option |
35423 | 16 | table option |
35424 | 16 | operator |
35425 | 16 | value |
35426 | 16 | system column |
35427 | 16 | set option |
35428 | 16 | query hint |
35429 | 16 | transaction isolation level |
35430 | 16 | in-memory index |
35431 | 10 | SCHEDULER |
35432 | 10 | NUMANODE |
35433 | 16 | federation |
35434 | 16 | federation distribution |
35435 | 16 | system database |
35436 | 16 | federation member database |
35437 | 16 | non federation member database |
35438 | 16 | federation root database |
35439 | 10 | it is a system database. |
35440 | 10 | it acts as a distribution database |
35441 | 10 | an internal error occurred |
35442 | 10 | it is involved in a mirroring session. Turn off the mirroring session and try again |
35443 | 10 | it is not in SIMPLE recovery mode. Change the recovery model to SIMPLE and try again |
35444 | 10 | it is a database snapshot |
35445 | 10 | it is a not currently enabled |
35446 | 16 | clause |
35447 | 10 | Cluster Proxy |
35448 | 10 | partition |
35449 | 16 | signing algorithm |
35450 | 16 | table |
35451 | 16 | join hint |
35452 | 10 | Database unavailable |
35453 | 10 | it 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 |
35454 | 10 | a transaction is currently active. Execute sp_db_enable_clustered_columnstores by itself |
35455 | 10 | an internal error occurred |
35456 | 10 | it is involved in a mirroring pair. Consider disabling mirroring, changing the setting, then re-establishing mirroring |
35457 | 10 | it is a database snapshot |
35458 | 10 | it 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 |
35459 | 10 | it is a replication distribution database. Make sure to target a regular user database |
35460 | 10 | it is not using the SIMPLE recovery model. Consider temporarily changing to the simple recovery model, then downgrading, then switching back |
35461 | 10 | it contains one or more clustered columnstore indexes. Consider dropping these indexes or creating clustered B-tree indexes instead, and trying again |
35462 | 10 | referencing |
35463 | 10 | referenced |
35464 | 10 | columnstore indexes are not supported in the current SQL Server edition. See SQL Server Books Online for supported editions |
35465 | 17 | Unable to allocate the recovery thread |
35466 | 16 | Exception in the recovery thread |
35467 | 16 | Already linked to a partition host |
35468 | 16 | Partition DB marked as suspect |
35469 | 16 | Failed to get Partition DB attributes |
35470 | 16 | Partition Host |
35471 | 10 | Partition metadata not found |
35472 | 15 | memory optimized tables |
35473 | 15 | natively compiled modules |
35474 | 15 | indexes on memory optimized tables |
35475 | 15 | hash indexes |
35476 | 15 | transactions that access memory optimized tables or natively compiled modules |
35477 | 15 | databases that have a MEMORY_OPTIMIZED_DATA filegroup |
35478 | 16 | truncate |
35479 | 16 | start |
35480 | 16 | stop |
35481 | 15 | memory optimized table types |
35482 | 16 | clustered |
35483 | 16 | nonclustered |
35484 | 16 | BUCKET_COUNT |
35485 | 16 | security policy |
35486 | 15 | memory optimized tables that have a column store index |
35487 | 10 | Global Transactions |
35488 | 15 | natively compiled triggers |
35489 | 16 | Upgrade of Hekaton database |
35490 | 16 | memory optimized tables that have max length columns |
35491 | 16 | max length columns in natively compiled modules |
35492 | 16 | column definition |
35493 | 16 | enabled |
35494 | 16 | disabled |
35495 | 15 | memory optimized table |
35496 | 15 | natively compiled module |
35497 | 15 | module |
35498 | 16 | external data source |
35499 | 16 | OUTPUT clauses in natively compiled modules |
35501 | 15 | schemas that contain natively compiled modules |
35502 | 15 | change_tracking_hardened_cleanup_version() |
35503 | 15 | safe_cleanup_version() |
35504 | 16 | server encryption protector |
35505 | 15 | RESUMABLE |
35506 | 15 | MAX_DURATION |
35507 | 10 | Storage |
35508 | 10 | RESUME |
35509 | 10 | PAUSE |
35510 | 10 | ABORT |
35511 | 10 | ABORT |
35512 | 10 | allow_enclave_computations |
35513 | 10 | compute |
35514 | 10 | local computer |
35515 | 10 | current user |
35516 | 10 | query_capture_policy |
35517 | 10 | execution_count |
35518 | 10 | total_compile_cpu_time_ms |
35519 | 10 | total_execution_cpu_time_ms |
35520 | 10 | OPTIMIZE_FOR_SEQUENTIAL_KEY |
35521 | 10 | stale_capture_policy_threshold |
35522 | 10 | day |
36001 | 16 | %s ‘%s’ already exists in the database. |
36002 | 16 | instance_id already exists in the database. |
36003 | 16 | %s ‘%s’ already exists for the given DAC instance. |
36004 | 16 | DacInstance with the specified instance_id does not exist. |
36005 | 16 | Dac root – database %s does not exist. |
36006 | 16 | Dac Policy with the specified policy id already exists in the parts table. |
36007 | 16 | Dac Part the policy refers to, does not exist. |
36008 | 16 | Dac Policy refers to a non-existent Policy. |
36009 | 16 | %s ‘%s’ already exists in the Dac Parts. |
36010 | 16 | The caller must be a member of the dbcreator fixed server role to perform this action. |
36011 | 16 | The caller must be sysadmin or the creator of the history entry being updated. |
36012 | 10 | Unable 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 |
36101 | 16 | Process ID %d is not an active process ID. |
37001 | 16 | This operation is not allowed since there are dependent objects pending installation. |
37002 | 16 | Cannot find the database ‘%s’, because it does not exist or you do not have permission to access it. |
37003 | 16 | This operation is not allowed because a utility control point already exists on this instance of SQL Server. |
37004 | 16 | The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL Server ‘%s’. |
37005 | 16 | The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL Server ‘%s’. |
37006 | 16 | Cannot perform the operation because the specified instance of SQL Server is not enrolled in a SQL Server utility. |
37007 | 16 | An error occurred during upload to the SQL Server utility control point. |
37008 | 16 | The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role. |
37009 | 16 | The operation cannot continue. The specified instance of SQL Server is not a SQL Server utility control point. |
37010 | 16 | The operation cannot continue. The SQL Server utility control point has managed instances of SQL Server enrolled. |
37101 | 16 | Server ‘%.*ls’ does not contain elastic job account: ‘%.*ls’. |
37102 | 16 | Elastic job account ‘%.*ls’ does not contain the resource of type ‘%.*ls’ named ‘%.*ls’. |
37103 | 16 | Internal job account error occurred : ‘%.*ls’. |
37104 | 16 | A job account already exists for subscription ‘%.*ls’ for the selected region. |
37105 | 16 | The job account ‘%.*ls’ on server ‘%.*ls’ already exists. |
37106 | 16 | The 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. |
37107 | 16 | The database ‘%.*ls’ on server ‘%.*ls’ has service level objective ‘%.*ls’ which is not supported for use as a job account database. |
37108 | 16 | A job account could not be linked to database ‘%.*ls’ on server ‘%.*ls’ because it is a geo-secondary database. |
37109 | 16 | Database ‘%ls’ on server ‘%ls’ is already linked to another job account. |
37201 | 16 | An instance pool could not be found with name ‘%.*ls’. |
37202 | 16 | An 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. |
39047 | 16 | External library ‘%.*ls’ already exists for owner ‘%.*ls’ in database ‘%.*ls’. |
39048 | 16 | Failed to %s external library ‘%ls’: %ls. |
39049 | 10 | Message(s) from ‘PREDICT’ engine: %.*ls%.*ls |
39050 | 16 | Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Out of memory. |
39051 | 16 | Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Model is corrupt or invalid. |
39052 | 16 | Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. Model type is unsupported. |
39092 | 16 | Initialization of native scoring libraries failed with HRESULT 0x%x. |
39093 | 16 | ‘PREDICT’ function does not take parameters of varchar(max), nvarchar(max) or varbinary(max) type except for ‘MODEL’ parameter. |
39094 | 16 | ‘PREDICT’ function only supports models smaller than 100 MB. |
39096 | 16 | Execution failed because its WITH clause specified different output columns from what ‘PREDICT’ function tries to return. The schema returned by ‘PREDICT’ function is ‘%ls’. |
39097 | 16 | Input 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. |
39098 | 16 | Error occurred during execution of the builtin function ‘PREDICT’ with HRESULT 0x%x. |
39099 | 16 | Feature or option ‘PREDICT’ is not yet implemented. Please consult Books Online for more information on this feature or option. |
39101 | 16 | ‘%.*ls’ failed because it is not supported in the edition of this SQL Server instance. |
39102 | 16 | Duplicate column names are not allowed in ‘%.*ls’. Column name ‘%.*ls’ is a duplicate. |
39103 | 16 | Parameter ‘@input_data_1_order_by_columns’ is not allowed without parameter ‘@input_data_1_partition_by_columns’. |
39104 | 16 | Column ‘%.*ls’ in ‘%.*ls’ is not defined in the SELECT clause of ‘@input_data_1’ parameter. |
39105 | 16 | Invalid syntax for parameter ‘@input_data_1_partition_by_columns’. Specify a list of comma separated columns. |
39106 | 16 | Invalid 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>. |
39107 | 16 | Columns 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. |
39108 | 16 | Maximum number of concurrent external script users has been reached. Limit is %d. Please retry the operation. External script request id is %ls. |
39109 | 16 | The 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. |
39110 | 16 | Maximum 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. |
39111 | 16 | The SQL Server Machine Learning Services End-User License Agreement (EULA) has not been accepted. |
39112 | 15 | Duplicate file specification supplied for platform ‘%.*ls’. |
39113 | 15 | Number of file specifications exceeds the maximum of %d. |
39114 | 15 | CREATE EXTERNAL LIBRARY statement failed because of duplicate file specification. Only one file specification per platform is allowed in a CREATE EXTERNAL LIBRARY statement. |
39115 | 16 | ALTER EXTERNAL LIBRARY statement failed because the content for platform ‘%.*ls’ does not exist or is not correctly defined in the external library. |
39116 | 16 | ALTER EXTERNAL LIBRARY REMOVE PLATFORM statement failed because an external library requires at least one file specification to be defined. |
39117 | 16 | %.*ls EXTERNAL LANGUAGE statement failed because the parameter ‘%s’ is not a valid expression. |
39118 | 16 | %s EXTERNAL LANGUAGE statement failed because the specified file path ‘%.*ls’ is too long. Maximum length of file path is %d characters. |
39119 | 16 | %s EXTERNAL LANGUAGE failed because it could not open the physical file ‘%.*ls’: %ls. |
39120 | 16 | %s EXTERNAL LANGUAGE statement failed because it could not read from the physical file ‘%.*ls’: %ls. |
39121 | 16 | CREATE EXTERNAL LANGUAGE statement failed because the user “%.*ls” specified in the authorization clause does not exist or have permission. |
39122 | 16 | CREATE statement failed. External language ‘%.*ls’ already exists. |
39123 | 16 | %.*ls EXTERNAL LANGUAGE statement failed because the parameter ‘%s’ is not specified. |
39124 | 16 | ‘%.*ls’ platform information doesn’t exist for the language ‘%.*ls’. |
39125 | 16 | ALTER EXTERNAL LANGUAGE statement failed because of duplicate file specification. Only one file specification per platform is allowed. |
39126 | 16 | ALTER EXTERNAL LANGUAGE REMOVE PLATFORM statement failed because an external language requires at least one file specification to be defined. |
39127 | 16 | External script execution for ‘%.*s’ script ran out of resources. External script request id is: %s. |
39128 | 16 | External language runtime for ‘%s’ could not be provisioned. Error code 0x%08x. |
39129 | 16 | Cannot drop external language ‘%.*ls’ because it is being referenced by external library ‘%.*ls’. |
39130 | 16 | %.*ls statement failed. Language ‘%s’ already exists. |
39131 | 16 | %.*ls statement failed. System language ‘%s’ can’t be altered or removed. |
39132 | 16 | The parameter ‘@r_rowsPerRead’ is invalid. Parameter ‘@r_rowsPerRead’ must be a positive integer. |
39133 | 16 | CREATE/ALTER EXTERNAL LANGUAGE statement failed. The environment variables string is invalid. |
40000 | 16 | Replicated tables support only local (non-DTC) two-phase commit involving the master database. |
40001 | 16 | Secondary kill was initiated during commit. |
40002 | 16 | Replicated row is not found. |
40003 | 16 | Unexpected operation in replicated message. |
40004 | 16 | Column count does not match. |
40005 | 16 | Duplicated transaction id. |
40006 | 16 | Unknown transaction id. |
40007 | 16 | Invalid nesting level. |
40008 | 16 | Replication target database is not found. |
40009 | 16 | Transaction state locally does not match the expected state. |
40010 | 16 | Replicated transactions across databases are not allowed. |
40011 | 16 | Replicated target table %ld is not found. |
40012 | 16 | Replicated target index %ld on table %ld is not found. |
40013 | 16 | Replicated target schema %.*ls is not found. |
40014 | 16 | Multiple databases can not be used in the same transaction. |
40015 | 16 | This functionality is not supported on replicated tables. |
40016 | 16 | The partitioning key column ‘%.*ls’ must be one of the keys of ‘%.*ls.%.*ls.%.*ls’ index. |
40017 | 16 | Partition key can not be changed. |
40018 | 16 | Partition key value is outside of the valid partition key range. |
40019 | 16 | The partition key column ‘%.*ls’ of table ‘%.*ls.%.*ls’ is nullable or does not match the partition key type defined in the table group. |
40020 | 16 | The database is in transition and transactions are being terminated. |
40021 | 16 | The low and high keys specified for the partition are invalid. Low must be less than high. |
40022 | 16 | A partition with overlapping key ranges already exists. |
40023 | 16 | The name %s is too long. |
40024 | 16 | The last committed CSN (%d, %I64d) was not found in the log. The last seen CSN was (%d, %I64d). |
40025 | 16 | The transaction was aborted during commit due to a database state transition. |
40028 | 16 | The tablegroup name ‘%.*ls.%.*ls’ is not valid. |
40029 | 16 | Replicated tables can have at most %d columns. |
40030 | 16 | Can not perform replica operation because the replica does not exist in local partition map. |
40031 | 16 | The partition key column for table ‘%.*ls.%.*ls’ is undefined. |
40032 | 16 | Unsupported use of LOB in online index build. |
40033 | 16 | Attempted CSN epoch switch is not allowed. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40034 | 16 | CSN being added must be equal last CSN+1. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40035 | 16 | CSN being added must be equal or greater than the last CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40036 | 16 | Can not perform replica operation because this node is not the secondary for this partition. |
40037 | 16 | The epoch being started must not have been used. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40038 | 16 | Can not get ack to rollback replication message. |
40039 | 16 | Can not get ack to commit replication message. |
40040 | 16 | Failed to initiate VDI Client for physical seeding. |
40041 | 16 | Corrupted column status. |
40042 | 16 | Corrupted column length. |
40043 | 16 | Corrupted variable data. Actual remaining bytes is %d, expected %d bytes. |
40044 | 16 | Corrupted fixed size data. Actual remaining bytes %d, expected %d bytes. |
40045 | 16 | Message version mismatch. Actual version is %d and the expected is %d. |
40046 | 16 | The minimum required message version %d for message type %d is unsupported. |
40047 | 16 | Invalid use of parent transaction. |
40048 | 16 | Corrupted fragmented row flow sequence. |
40049 | 16 | Corrupted fragmented row. |
40050 | 16 | Corrupted LOB row. |
40051 | 16 | Use of UPDATETEXT on replicated tables is not supported. |
40052 | 16 | Parallel queries are not supported on replicated tables. |
40053 | 16 | Attempt to replicate a non-replicated system table %ld. |
40054 | 16 | Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again. |
40056 | 16 | Master, tempdb, model and mssqlsystemresource databases can not be replicated. |
40057 | 16 | Table is not enabled for replication. |
40058 | 16 | Unsupported replicated table usage option. Refer to the state to identify the cause. |
40060 | 16 | Attempt to replicate out of partition already locked for internal use. |
40061 | 16 | Unknown rowset id. |
40062 | 16 | Incorrect replica role transition. |
40063 | 16 | Replica is not found. |
40064 | 16 | Attempt to add a CSN to an invalid CSN vector. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40065 | 16 | CSN vector can be reinitialized only with initial or invalid CSN. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40066 | 16 | Transport destination is not found. |
40067 | 16 | Corrupted row sequence. |
40068 | 16 | Idempotent mode has been used on an unknown transaction. |
40069 | 16 | Could not obtain rowset interface. |
40070 | 16 | CSN mismatch detected. The local CSN is (%d,%I64d), the remote CSN is (%d,%I64d). |
40071 | 16 | This partition does not have enough valid secondaries to start a DML transaction. The needed count is %ld, the current counts are %ld (main quorum) and %ld (transient quorum). |
40072 | 16 | Corrupted rowset metadata sequence. |
40073 | 16 | Partitioned tables are not supported. |
40074 | 16 | Partition key is not found is the target rowset or is nullable or not part of index keys. |
40075 | 16 | Column schema mismatch for rowset %ls.%ls.%ls column %ld. |
40076 | 16 | Too few columns from remote rowset %ls.%ls.%ls. |
40077 | 16 | Remote rowset %ls.%ls.%ls column %ld is not found locally. |
40078 | 16 | The persisted queue logging has failed. |
40079 | 16 | A non-null variable length value is received for a column that is shorter locally. |
40080 | 16 | Corrupted (too long) packed row. |
40081 | 16 | Cardinality of index should not be less then zero. |
40082 | 16 | Induced exception for testing purposes. |
40083 | 16 | Corrupted CSN vector. |
40084 | 16 | Multiple modifications to CSN vector in the same transaction are not supported. |
40085 | 16 | The primary partition has lost the quorum. New transactions can not start. |
40086 | 16 | Primary hit an error with this secondary. |
40087 | 16 | Replica with the specified version is not found. |
40088 | 16 | CSN being set is outside the CSN epoch range. The new CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40089 | 16 | The index configuration for table %ld index %ld does not match the source. |
40090 | 16 | The primary partition is in transition and the transaction can not commit. |
40091 | 16 | Truncation CSN is mismatched. The truncation CSN is (%d,%I64d), the current CSN is (%d,%I64d). |
40092 | 16 | This index %ld state for table %ld does not match the source. |
40093 | 16 | Replication background task hit a lock timeout. User transactions will be killed and the operation will be retried. |
40094 | 16 | Incompatible key metadata change. The scan can not be resumed. |
40095 | 13 | Replication 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. |
40096 | 16 | Critical replication task could not start. State is %d. |
40097 | 16 | The begin transaction message was not found when scanning persisted replication queue. |
40098 | 16 | Mismatched partition id found in the transaction log. |
40099 | 16 | Invalid nested transaction count found in the transaction log. |
40101 | 16 | The partition does not have persisted queues enabled. |
40102 | 16 | The partition can not have persisted queues modified in this state. |
40103 | 16 | The partition can not be changed inside a persisted object. |
40104 | 16 | Only sysadmin can execute this stored procedure ‘%.*ls’. |
40105 | 16 | The 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. |
40106 | 16 | The schema scope set in the session is not the current schema scope for the current partition. Please rerun your query. |
40108 | 16 | The filtered replica is not a subset of the primary replica. This is only possible for table groups without a partition key. |
40109 | 16 | Number of parameters specified for procedure or function %.*ls is incorrect. |
40110 | 16 | Cannot scope database %s for sp_cloud_scope_database spec proc because it is already set up as a partition database. |
40111 | 16 | Unable to delete partition DB id %d. |
40126 | 16 | The partition database was not found during pending schema scope cleanup, deleting partition metadata only (%d, %s). |
40127 | 16 | %S_MSG database ‘%.*ls’ link up with the %S_MSG database %d encountered the error: %S_MSG. |
40128 | 16 | Cannot pair database ‘%.*ls’ with fabric because it is not a partition host. |
40129 | 16 | %S_MSG database link up with the %S_MSG database ‘%.*ls’ encountered the error: %ls. |
40130 | 16 | Replication quorum parameter is %d. It should be >= 1 and <= 32. |
40131 | 16 | Partition key type ‘%.*ls’ is not supported. Only BIGINT, UNIQUEIDENTIFIER, and VARBINARY(n) (0<n<=512) datatypes are supported currently. |
40132 | 16 | Before dropping a table group, you have to delete all the partitions. |
40133 | 15 | This operation is not supported in this version of SQL Server. |
40134 | 16 | get_new_rowversion() can only be used in an active transaction. |
40135 | 15 | This system metadata view is not supported. |
40136 | 15 | Could not disable versioning because the database is not in single user mode. |
40137 | 15 | Could not refresh options for all scoped databases. |
40138 | 16 | Query references entities from multiple partitions. |
40139 | 16 | The data node does not host a replica of the requested partition. |
40140 | 16 | Set partition failed since a different partition already was set in the current transaction. Cross partition operations within a node are not reliable or supported. |
40141 | 16 | Partition has to be set using sp_set_partition before executing this query. |
40142 | 16 | Accessing a different partition in the same transaction is not allowed. |
40143 | 16 | The replica that the data node hosts for the requested partition is not primary. |
40144 | 16 | Cannot find the object “%.*ls” because it does not exist or you do not have permissions. |
40145 | 16 | Database is not found. |
40146 | 16 | Table group object is not found. |
40147 | 16 | Stored procedure ‘%.*ls’ is only for CloudDB. |
40148 | 16 | The existing persisted queue snapshot CSN (%d, %I64d) at %S_LSN is greater than the requested snapshot CSN (%d, %I64d) at %S_LSN. |
40149 | 16 | The database does not host any partitions. |
40150 | 16 | Downgrading the severity of error %d, severity %d, state %d because it would cause the server to be shutdown on a non-critical error. |
40151 | 16 | Partition is in transactionally inconsistent state. |
40152 | 16 | Partition delete expects no context transaction. |
40153 | 16 | The current database has been shutdown. The current database has been switched to master. |
40154 | 16 | Cannot use sp_cloud_add_partition or sp_cloud_delete_partition within a transaction when Partition DB are enabled. |
40155 | 16 | Invalid arguments provided to sp_cloud_add_partition spec proc (%s). |
40156 | 16 | Drop is not allowed on the %S_MSG database ‘%.*ls’ as it contains partitions. Drop the partition before the operation. |
40157 | 16 | Too many secondaries. At most 32 are currently supported. |
40158 | 16 | Could not change database collation for database id %d. |
40159 | 16 | Database scoping cannot be run inside a transaction. |
40160 | 16 | Heartbeat message version mismatch. Actual version is %d and the expected is %d. |
40161 | 16 | Invalid partition type. Only 1 or 2 is supported. |
40162 | 16 | The replica that the data node hosts for the requested partition is not transactionally consistent. |
40163 | 16 | Become nothing expects no context transaction. |
40164 | 16 | Idempotent flush expects no context transaction. |
40165 | 16 | Prepare for full commit expects no context transaction. |
40166 | 16 | A CloudDB reconfiguration is going on and all new user transactions are aborted. |
40167 | 21 | A paired CloudDB fabric node failed and database %d must be shutdown. |
40168 | 16 | SILO_TO_PDB: Partition copy is disabled in M1. |
40169 | 16 | Waiting for database copy sync with %s.%s has failed. Please make sure the database is in the CATCH_UP state and try again later. |
40170 | 16 | Catchup of secondary at %s:%s:%s:%d has failed. |
40171 | 16 | Table group name (single part name) should not be longer than nvarchar(64). |
40172 | 16 | The partition is not in a state that allows deletion. |
40173 | 16 | This requested operation can not performed as this partition is in delete process. |
40174 | 16 | The partition is in transition and transactions are being terminated. |
40175 | 16 | Add a secondary with wait can not be used in a transaction. |
40176 | 16 | Rename a partition can not be used in a transaction. |
40177 | 16 | The new table group does not match the existing table group for the renaming partition. |
40178 | 16 | A partition with same name already exists. |
40179 | 16 | Fabric-database (‘%.*ls’) cannot be paired, the server is not ready to pair. |
40180 | 16 | Fabric-database (‘%.*ls’) cannot be paired, the database is already paired. |
40181 | 16 | Fabric-database (‘%.*ls’) cannot be paired, the supplied mutex (‘%.*ls’) could not be opened. Error code: %d |
40182 | 16 | The schema scope %ld being created is not empty. |
40183 | 16 | Could not create database side pairing mutex for database (‘%.*ls’). Error code: %d |
40184 | 16 | Login failed. A system operation is in progress, and the database is not accepting user connections. |
40185 | 16 | Secondary failure report expects no context transaction. |
40186 | 16 | The data node does not host a replica of the requested partition with the requested version. |
40187 | 16 | The metadata record for the partition does not exist. |
40188 | 16 | Failed to update database “%.*ls” because it is switched to read-only to enforce disaster recovery RPO. |
40189 | 16 | The resource quota for the current database has been exceeded and this request has been aborted. Please rerun your request in the next quota window. %s |
40190 | 16 | A context transaction is required. |
40191 | 16 | Cannot create partition DB (%s). |
40192 | 16 | Catchup of secondary at %s:%s:%s:%d has been cancelled. |
40193 | 16 | The maximum allowed number of database is already paired. |
40194 | 16 | Table %s has a partition key already. Explicitly specifying a new partition key is not allowed. Please use “Alter table”. |
40195 | 16 | %ls FOR SID command is not supported in this version of SQL Server. |
40196 | 16 | A varbinary can not be longer than max length specified. |
40197 | 16 | The service has encountered an error processing your request. Please try again. Error code %d. |
40198 | 16 | Only a primary replica can be configured as a forwarder. |
40199 | 16 | There should be no context transaction when entering the forwarder pending state. |
40201 | 16 | Destination server name is too long. |
40202 | 16 | Corrupted composite message. |
40203 | 16 | Could not register AsyncTransport endpoint. |
40204 | 16 | Dispatch sequence number maintenance failure |
40205 | 16 | Maximum transport queue size reached. |
40206 | 16 | Heartbeat lease time is less than the heartbeat worker interval. |
40207 | 16 | Async transport test failed. |
40208 | 16 | Corrupted received message format. |
40209 | 17 | Duplicate destination id. |
40210 | 16 | Cluster name has not been set. |
40301 | 16 | Invalid lock mode or resource received in lock request. |
40302 | 16 | Invalid identity value. |
40303 | 16 | Enter idempotent sequence. |
40304 | 16 | Target object %ld is not found. |
40305 | 16 | The current object is not a relation. |
40306 | 16 | Cannot create an index %ld on object %ld. |
40307 | 16 | Cannot find index %ld on object %ld. |
40308 | 16 | Metadata replication protocol error. |
40309 | 16 | Partition %ld is not found |
40310 | 16 | Converting a clustered index into a heap is not supported. |
40311 | 16 | Switching out partitions not supported. |
40312 | 16 | Inconsistent index build state. |
40313 | 16 | Not all rowsets could be deleted. |
40314 | 16 | Identity column not found on object %ld. |
40501 | 20 | The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d |
40502 | 16 | Duplicate group id settings specified. |
40503 | 16 | Database field %ls contains invalid value ‘%.*ls’. Expected data type %ls. |
40504 | 16 | Switching Databases is not supported. Use a new connection to connect to a different Database. |
40505 | 16 | Incorrect user credentials. |
40506 | 16 | Specified SID is invalid for this version of SQL Server. |
40507 | 16 | ‘%.*ls’ cannot be invoked with parameters in this version of SQL Server. |
40508 | 16 | USE statement is not supported to switch between databases. Use a new connection to connect to a different database. |
40509 | 16 | Upgrade of SAWA v1 database fails. Check the metadata of the database before re-running the upgrade. |
40510 | 16 | Statement ‘%.*ls’ is not supported in this version of SQL Server. |
40511 | 16 | Built-in function ‘%.*ls’ is not supported in this version of SQL Server. |
40512 | 16 | Deprecated feature ‘%ls’ is not supported in this version of SQL Server. |
40513 | 16 | Server variable ‘%.*ls’ is not supported in this version of SQL Server. |
40514 | 16 | ‘%ls’ is not supported in this version of SQL Server. |
40515 | 16 | Reference to database and/or server name in ‘%.*ls’ is not supported in this version of SQL Server. |
40516 | 16 | Global temp objects are not supported in this version of SQL Server. |
40517 | 16 | Keyword or statement option ‘%.*ls’ is not supported in this version of SQL Server. |
40518 | 16 | DBCC command ‘%.*ls’ is not supported in this version of SQL Server. |
40519 | 16 | Invalid value ‘%.*ls’ of login field in gateway magic syntax. |
40520 | 16 | Securable class ‘%S_MSG’ not supported in this version of SQL Server. |
40521 | 16 | Securable class ‘%S_MSG’ not supported in the server scope in this version of SQL Server. |
40522 | 16 | Database principal ‘%.*ls’ type is not supported in this version of SQL Server. |
40523 | 16 | Implicit user ‘%.*ls’ creation is not supported in this version of SQL Server. Explicitly create the user before using it. |
40524 | 16 | Data type ‘%.*ls’ is not supported in this version of SQL Server. |
40525 | 16 | ‘WITH %ls’ is not supported in this version of SQL Server. |
40526 | 16 | ‘%.*ls’ rowset provider not supported in this version of SQL Server. |
40527 | 16 | Linked servers are not supported in this version of SQL Server. |
40528 | 16 | Users cannot be mapped to Windows logins in this version of SQL Server. |
40529 | 16 | Built-in function ‘%.*ls’ in impersonation context is not supported in this version of SQL Server. |
40530 | 16 | The %.*ls statement must be the only statement in the batch. |
40531 | 11 | Server name cannot be determined. It must appear as the first segment of the server’s dns name (servername.%.*ls). Some libraries do not send the server name, in which case the server name must be included as part of the user name (username@servername). In addition, if both formats are used, the server names must match. |
40532 | 11 | Cannot open server “%.*ls” requested by the login. The login failed. |
40533 | 16 | Server ‘%.*ls’ already exists. |
40534 | 16 | A valid SID is already associated with the database owner. |
40535 | 16 | Properties for schema scope ‘%.*ls’ already exist. |
40536 | 16 | ‘%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. |
40537 | 16 | User ‘%.*ls’ not found in the database. |
40538 | 16 | A valid URL beginning with ‘https://’ is required as value for any filepath specified. |
40539 | 16 | Windows Azure Storage credential ‘%.*ls’ was not found. |
40540 | 16 | Transaction was aborted as database is moved to read-only mode. This is a temporary situation and please retry the operation. |
40541 | 16 | Procedure cannot be called from inside a partition. |
40542 | 16 | Incorrect number of parameters specified for procedure. |
40543 | 16 | Invalid %S_MSG name specified. Length should be between 1 and %d. |
40544 | 20 | The database ‘%.*ls’ has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. |
40545 | 20 | The service is experiencing a problem that is currently under investigation. Incident ID: %ls. Code: %d |
40546 | 16 | Cannot create UCS task pool |
40548 | 16 | Granting CONNECT permission to the guest user in database ‘%.*ls’ is not permitted. |
40549 | 16 | Session is terminated because you have a long running transaction. Try shortening your transaction. |
40550 | 16 | The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction. |
40551 | 16 | The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce temporary table space usage. |
40552 | 16 | The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction. |
40553 | 16 | The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows. |
40554 | 10 | Exiting because of XEvent %ls. |
40555 | 16 | ‘%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. |
40558 | 16 | Error – cannot perform checkpoint on a partition database before loading partition information. |
40559 | 16 | File based statement options are not supported in this version of SQL Server. |
40561 | 16 | Database copy failed. Either the source or target database does not exist. |
40562 | 16 | Database copy failed. The source database has been dropped. |
40563 | 16 | Database copy failed. The target database has been dropped. |
40564 | 16 | Database copy failed. Database copy failed due to an internal error. Please drop target database and try again.</value> |
40565 | 16 | Database copy failed. No more than 1 concurrent database copy from the same source is allowed. Please drop target database and try again later. |
40566 | 16 | Database copy failed due to an internal error. Please drop target database and try again. |
40567 | 16 | Database copy failed due to an internal error. Please drop target database and try again. |
40568 | 16 | Database copy failed. Either the source or the target database has become unavailable. Please drop target database and try again. |
40569 | 16 | Database copy failed. Target database has become unavailable. Please drop target database and try again. |
40570 | 16 | Database copy failed due to an internal error. Please drop target database and try again later. |
40571 | 16 | Database copy failed due to an internal error. Please drop target database and try again later. |
40572 | 16 | Cannot obtain primary partition lock for CloudDB auto partition upgrade. |
40573 | 16 | Cannot upgrade CloudDB auto partitions in database ‘%.*ls’ because the physical database is read only. |
40574 | 16 | Permissions for system stored procedures, server scoped catalog views, and extended stored procedures cannot be changed in this version of SQL Server. |
40575 | 16 | Data type ‘%.*ls’ is not supported in a federated database. |
40576 | 16 | Table DDL on non-temporary tables is not supported in a filtered connection. |
40577 | 16 | The constraint ‘%ls’ is not supported in a federated database. |
40578 | 16 | Statement ‘%.*ls’ is not supported in a filtered connection. |
40579 | 16 | DML statements are not supported on non-federated tables in a filtered connection. |
40580 | 16 | Statement ‘%.*ls’ is not supported in a federated database. |
40581 | 16 | Logically filtered secondaries are only supported if the secondary is a forwarder. |
40582 | 16 | Federation member metadata for a database cannot be changed when there are logically filtered secondaries attached (split is running). |
40583 | 16 | Federation member does not exist for the given member id and federation root |
40584 | 16 | Value ‘%.*ls’ for option ‘%.*ls’ is not supported in this version of SQL Server. |
40585 | 16 | Can not perform replica operation because this node is not the forwarder for this partition. |
40586 | 16 | Replicas with deferred commit enabled cannot be a member of a quorum. |
40587 | 16 | Deferred commit is only supported with forwarder replicas. |
40588 | 16 | Cannot create partition worker pool |
40589 | 16 | Replicas that are not enabled for deferred commit cannot specify RPO. |
40590 | 16 | The Gpm is in rebuild and cannot be accessed as it is not yet consistent. |
40591 | 16 | Extended event configuration could not be initialized. The error is %ls. |
40592 | 16 | Extended event session ‘%ls’ could not be created or altered. XE Error %d.%d state:%d. |
40593 | 16 | Extended event session ‘%ls’ returned error ‘%ls’. |
40594 | 16 | Extended event session ‘%ls’ has been started. |
40595 | 16 | Extended event session ‘%ls’ has been altered. |
40596 | 16 | Extended event session ‘%ls’ has been stopped. |
40597 | 16 | A federation root database cannot be read only. |
40598 | 16 | A federation member cannot be read only. |
40599 | 16 | This type of KILL is not supported in Windows Azure SQL Database; Only ‘KILL session ID [WITH STATUSONLY]’ and ‘KILL UOW’ are supported. |
40601 | 16 | Server Admin user already exists. |
40602 | 16 | Could not create login. Please try again later. |
40603 | 16 | Cannot execute procedure because current user is not Gateway. |
40604 | 16 | Could not %.*ls because it would exceed the quota of the server. |
40605 | 16 | There is no route from the source cluster ‘%ls’ to the target cluster ‘%ls’. |
40606 | 16 | Databases cannot be attached in this version of SQL Server. |
40607 | 16 | Windows logins are not supported in this version of SQL Server. |
40608 | 10 | This session has been assigned a tracing ID of ‘%.*ls’. Provide this tracing ID to customer support when you need assistance. |
40609 | 16 | ‘%.*ls’ is not a valid IPv4 address. |
40610 | 16 | The IP address that starts with ‘%.*ls’ is too long. Maximum length is %d. |
40611 | 16 | Windows Azure SQL Database supports a maximum of 128 firewall rules. |
40612 | 16 | Spec proc was executed against a silo that cannot be upgraded to include firewall objects. |
40613 | 17 | Database ‘%.*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’. |
40614 | 16 | Start IP address of firewall rule cannot exceed End IP address. |
40615 | 16 | Cannot open server ‘%.*ls’ requested by the login. Client with IP address ‘%.*ls’ is not allowed to access the server. To enable access, use the 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. |
40616 | 16 | ‘%.*ls’ is not a valid login name in this version of SQL Server. |
40617 | 16 | The firewall rule name that starts with ‘%.*ls’ is too long. Maximum length is %d. |
40618 | 16 | The firewall rule name cannot be empty. |
40619 | 16 | The edition ‘%.*ls’ does not support the database data max size ‘%.*ls’. |
40620 | 16 | The login failed for user “%.*ls”. The password change failed. Password change during login is not supported in this version of SQL Server. |
40621 | 16 | metric type |
40622 | 16 | metric data |
40623 | 20 | Reauthentication 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. |
40624 | 16 | Operation is not allowed because server ‘%.*ls’ is disabled. |
40625 | 17 | Provisioning (creating, altering, or dropping) Windows Azure SQL Database servers and databases is currently disabled. This most frequently occurs for brief periods during system maintenance. |
40626 | 20 | The ALTER DATABASE command is in process. Please wait at least five minutes before logging into database ‘%.*ls’, in order for the command to complete. 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. |
40627 | 20 | Operation on server ‘%.*ls’ and database ‘%.*ls’ is in progress. Please wait a few minutes before trying again. |
40628 | 16 | Failed 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. |
40629 | 16 | An edition could not be determined from maxsize ‘%.*ls’. Specify a valid maxsize value. |
40630 | 16 | Password validation failed. The password does not meet policy requirements because it is too short. |
40631 | 16 | The password that you specified is too long. The password should have no more than %d characters. |
40632 | 16 | Password validation failed. The password does not meet policy requirements because it is not complex enough. |
40633 | 16 | ‘%.*ls’ is not a valid database edition in this version of SQL Server. |
40634 | 16 | This stored procedure can only be executed in the master database. |
40635 | 16 | Client with IP address “%.*ls” is temporarily blocked. |
40636 | 16 | Cannot use reserved database name ‘%.*ls’ in this operation. |
40637 | 17 | Database copy is currently disabled. |
40638 | 16 | Invalid subscription id ‘%.*ls’. Subscription does not exist. |
40639 | 16 | Request does not conform to schema: %.*ls. |
40640 | 20 | The server encountered an unexpected exception. |
40641 | 16 | Location ‘%.*ls’ cannot be found. |
40642 | 17 | The server is currently too busy. Please try again later. |
40643 | 16 | The specified x-ms-version header value is invalid. |
40644 | 14 | Failed to authorize access to the specified subscription. |
40645 | 16 | Servername “%.*ls” cannot be empty or null. It can only be made up of lowercase letters ‘a’-‘z’, the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name. |
40646 | 16 | Subscription ID cannot be empty. |
40647 | 16 | Subscription ‘%.*ls’ does not have the server ‘%.*ls’. |
40648 | 17 | Too many requests have been performed. Please retry later. |
40649 | 16 | Invalid content-type is specified. Only application/xml is supported. |
40650 | 16 | Subscription ‘%.*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. |
40651 | 16 | Failed to create server because the subscription ‘%.*ls’ is disabled. |
40652 | 16 | Cannot move or create server. Subscription ‘%.*ls’ will exceed server quota. |
40653 | 16 | Could not find database ‘%.*ls’ at time ‘%.*ls’ that can be restored. |
40654 | 16 | Specified subregion ‘%.*ls’ is invalid. |
40655 | 16 | Database ‘master’ cannot be restored. |
40656 | 16 | Quota for maximum number of concurrent restores has been exceeded. |
40657 | 16 | Restore is not enabled on the server. |
40658 | 16 | Quota for number of restores has been exceeded. |
40659 | 16 | Could not successfully restore database because the maximum duration for processing a restore has elapsed. |
40660 | 16 | Could 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. |
40661 | 16 | Restore has been cancelled by a system administrator. |
40662 | 16 | An 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. |
40663 | 16 | Database ‘%.*ls’ is currently being restored and cannot be dropped. Please wait for restore to complete. |
40664 | 16 | Database ‘master’ cannot be copied. |
40665 | 16 | ‘%.*ls’ is not a supported collation. |
40666 | 16 | ‘%.*ls’ is a unicode-only collation and cannot be a default collation for a database. |
40667 | 15 | Specifying a LOGIN is not allowed in a federation member. |
40668 | 16 | ‘%.*ls’ is not a valid user name or you do not have permission. |
40669 | 17 | Location ‘%.*ls’ is not accepting creation of new Windows Azure SQL Database servers at this time. |
40670 | 16 | The http header ‘ocp-resourceprovider-registered-uri’ is missing from the request or is invalid. To continue, provide a valid value for the header. |
40671 | 17 | Unable to ‘%.*ls’ ‘%.*ls’ on server ‘%.*ls’. Please retry the connection later. |
40672 | 16 | The service objective assignment for a database cannot be changed more than once per %d hour(s). Please retry the operation %d hour(s) after the last service objective assignment completed for this database. |
40673 | 16 | The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the server name, database name and activity ID. |
40674 | 16 | Service objective creation or assignment is not permitted for this subscription. |
40675 | 16 | The service is currently too busy. Please try again later. |
40677 | 16 | The operation for the request uri ‘%.*ls’ was not found. To continue, please provide a valid request uri. |
40678 | 16 | Invalid value for header ‘%.*ls’. The header must contain a single valid GUID. |
40679 | 16 | The operation cannot be performed since the database ‘%ls’ is not in a replication relationship. |
40680 | 16 | The operation cannot be performed since the database ‘%ls’ is in a replication relationship. |
40681 | 16 | The operation cannot be performed since the database ‘%ls’ is a replication target. |
40682 | 16 | Failed to update database ‘%.*ls’ because the database is a replication target. |
40683 | 16 | The operation cannot be performed since the database ‘%ls’ is not a replication target. |
40684 | 16 | A seeding operation is already in progress for database ‘%ls’. |
40685 | 16 | A terminate operation is already in progress for database ‘%ls’. |
40686 | 16 | The operation is currently not supported. |
40687 | 16 | The operation cannot be performed on the database ‘%.*ls’ in its current state. |
40688 | 16 | The databases ‘%ls’ in server ‘%ls’ and ‘%ls’ in server ‘%ls’ are already in a replication relation. |
40689 | 16 | Replication limit reached. The database ‘%ls’ cannot have more than %d replication relationships. |
40690 | 16 | The operation cannot be performed since the replication source and target databases have different names. The source and target databases must have the same name. |
40691 | 16 | Replication target cannot be created in the same server as source. |
40692 | 16 | The alter database ‘%ls’ failed to initiate because there are operations pending on the database. After the pending operations are complete, try again. |
40693 | 16 | The current operation cannot be initiated while a replication operation is in progress. You can rename the database only after the replication operation has stopped. |
40694 | 16 | The seeding operation cannot be initiated on a replication target database. |
40695 | 16 | The operation cannot be performed since the database is currently a Federation root or member database. |
40696 | 16 | sp_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’. |
40697 | 16 | Login failed for user ‘%.*ls’. |
40698 | 16 | ‘%.*ls’ cannot be performed on a free database. |
40699 | 16 | You cannot create a user with password in this version of SQL Server |
40701 | 16 | XML format used for specifying rules is invalid. %.*ls. |
40702 | 16 | Failed to parse XML rules. |
40703 | 16 | Invalid attribute name ‘%.*ls’ in %.*ls. |
40704 | 16 | Invalid element name ‘%.*ls’ in %.*ls. |
40705 | 16 | Invalid Feature type ‘%.*ls’ in %.*ls. |
40706 | 16 | Feature name ‘%.*ls’ does not exist. |
40707 | 16 | Invalid index value ‘%.*ls’ in %.*ls. |
40708 | 16 | Invalid param count ‘%.*ls’ in %.*ls. |
40709 | 16 | operator attribute is missing in %.*ls. |
40711 | 16 | Rule name ‘%.*ls’ does not exist. |
40712 | 16 | Invalid usage of %.*ls. |
40713 | 16 | Invalid values supplied for <parameter> element in %.*ls. |
40714 | 16 | Out of memory. |
40715 | 16 | Invalid operator type %.*ls in %.*ls. |
40716 | 16 | Invalid input type %.*ls in %.*ls. |
40717 | 16 | index attribute is missing in %.*ls. |
40718 | 16 | one of inputtype, isnull and format attributes is required in %.*ls. |
40719 | 16 | Failed to get %s lock on %s rules. |
40720 | 16 | Rule name ‘%.*ls’ already exists. |
40721 | 16 | Only one of inputtype, isnull and format attributes is required in %.*ls. |
40722 | 16 | Failed to clear proc cache. |
40723 | 16 | Rule name cannot exceed more than %d characters. |
40724 | 16 | Unexpected Operator attribute in %.*ls. |
40801 | 16 | Operation ALTER USER WITH LOGIN failed. User provided login does not match the login in the federation root database for the user provided username. |
40802 | 16 | A 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’. |
40803 | 16 | The server ‘%.*ls’ has reached its quota of (%d) premium databases. |
40804 | 16 | The specified service objective ‘%.*ls’ is invalid. |
40805 | 16 | The service objective assignment for the database has failed. Please contact Microsoft customer support and provide the activity ID. |
40806 | 16 | The request to retrieve subscription information has timed out. Please try again later. |
40807 | 16 | Could not retrieve subscription information for subscription id: %.*ls, after %d attempts. Please try again later. |
40808 | 16 | The edition ‘%.*ls’ does not support the service objective ‘%.*ls’. |
40809 | 16 | No rows found in sys.dm_operation_status table for database ‘%.*ls’ and operation ‘%.*ls’. |
40810 | 16 | More than one row found in sys.dm_operation_status table for database ‘%.*ls’ and operation ‘%.*ls’. |
40811 | 16 | Operation ‘%.*ls’ for database ‘%.*ls’ cannot be cancelled as it has already completed. |
40812 | 16 | Database ‘%.*ls’ cannot be dropped as create operation is in progress. The create operation will be cancelled. |
40813 | 16 | Could not set database as writable because the database is Premium (suspended). |
40814 | 16 | Could not change database edition to or from Premium for a Federation root. |
40815 | 16 | Could not change database edition to or from Premium for a Federation member. |
40816 | 16 | Could not change database edition to Premium for a database in a replication relationship. |
40817 | 16 | Could not change database edition from Premium for a database in a replication relationship. |
40818 | 16 | The replication operation on database ‘%ls’ failed because there are alter operations pending on the database. Try again after the pending operations have completed. |
40820 | 16 | The server has reached its quota of (%d) premium databases. |
40821 | 16 | Federations are not supported on a Premium database. |
40822 | 16 | This feature is not available for the selected database’s edition (%ls). |
40823 | 16 | Invalid proxy override option supplied. |
40824 | 16 | ProxyOverrideSupport feature switch is not turned ON. |
40825 | 16 | Unable to complete request now. Please try again later. |
40827 | 16 | The operation is not supported for your subscription offer type. |
40838 | 16 | Replication relationship limit reached. The database ‘%ls’ cannot have more than one non-readable secondary. |
40839 | 16 | Connection to a non-readable secondary database is not allowed. See ‘http://go.microsoft.com/fwlink/?LinkID=402429&clcid=0x409’ for more information. |
40840 | 16 | Target region ‘%ls’ is not a DR paired Azure region. See ‘http://go.microsoft.com/fwlink/?LinkID=402430&clcid=0x409’ for more information. |
40841 | 16 | Friendly termination of a non-readable replication relationship is not supported. |
40842 | 16 | Termination 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 |
40843 | 16 | Non-readable secondary is not supported for database copy. |
40844 | 16 | Database ‘%ls’ on Server ‘%ls’ is a ‘%ls’ edition database in an elastic pool and cannot have a replication relationship. |
40847 | 16 | Could not perform the operation because server would exceed the allowed Database Throughput Unit quota of %d. |
40848 | 16 | The 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. |
40849 | 16 | The 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. |
40850 | 16 | Could not change database edition from ‘%ls’ to Standard for database ‘%ls’ in a replication relationship. |
40851 | 16 | Could not change database edition from ‘%ls’ to Basic for database ‘%ls’ in a replication relationship. |
40852 | 16 | Cannot open database ‘%.*ls’ on server ‘%.*ls’ requested by the login. Access to the database is only allowed using a security-enabled connection string. |
40854 | 16 | Partner server ‘%ls’ is not compatible with server ‘%ls.’ |
40855 | 16 | The operation cannot be performed since the database ‘%ls’ is not in ‘%ls’ state on the replication relationship. |
40856 | 16 | Could not change database edition for database ‘%ls’ in a replication relationship. |
40857 | 16 | Elastic pool not found for server: ‘%ls’, elastic pool name: ‘%ls’. |
40858 | 16 | Elastic pool ‘%ls’ already exists in server: ‘%ls’ |
40859 | 16 | Elastic pool does not support database edition ‘%ls’. |
40860 | 16 | Elastic pool ‘%ls’ and service level objective ‘%ls’ combination is invalid. |
40861 | 16 | The database edition ‘%ls’ cannot be different than the elastic pool service tier which is ‘%ls’. |
40862 | 16 | Elastic pool name must be specified if the elastic pool service objective is specified. |
40863 | 16 | Connections to this database are no longer allowed. |
40864 | 16 | The DTUs for the elastic pool must be at least (%d) DTUs for service tier ‘%.*ls’. |
40865 | 16 | The DTUs for the elastic pool cannot exceed (%d) DTUs for service tier ‘%.*ls’. |
40866 | 16 | Max size (%d) is not valid. Please specify a valid max size. |
40867 | 16 | The DTU max per database must be at least (%d) for service tier ‘%.*ls’. |
40868 | 16 | The DTU max per database cannot exceed (%d) for service tier ‘%.*ls’. |
40869 | 16 | The DTU max per database (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’. |
40870 | 16 | The DTU min per database cannot exceed (%d) for service tier ‘%.*ls’. |
40871 | 16 | The DTU min per database (%d) for the elastic pool does not belong to the allowed values for service tier ‘%.*ls’. |
40872 | 16 | DTU value (%d) is not valid. Please specify a valid dtu value. |
40873 | 16 | The number of databases (%d) and DTU min per database (%d) cannot exceed the DTUs of the elastic pool (%d). |
40874 | 16 | The DTUs (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’. |
40875 | 16 | The elastic pool storage limit in gigabytes cannot exceed (%d) in service tier ‘%.*ls’. |
40876 | 16 | Elastic pools are not available in this region. |
40877 | 16 | The elastic pool is not empty. |
40878 | 16 | The elastic pool storage limit in gigabytes must be at least (%d) for service tier ‘%.*ls’. |
40879 | 16 | The elastic pool storage limit in gigabytes (%d) does not belong to the allowed values for service tier ‘%.*ls’. |
40880 | 16 | The DTUs (%d) for the elastic pool and the storage limit in gigabytes (%d) are inconsistent for service tier ‘%.*ls’. |
40881 | 16 | The elastic pool ‘%.*ls’ has reached its database count limit. The database count for the elastic pool cannot exceed (%d) for service tier ‘%.*ls’. |
40882 | 16 | Can not change SLO from DataWarehouse edition to other SQL DB editions and vice versa. |
40883 | 16 | The service level objective ‘%.*ls’ specified is invalid. It must be a slo supported by DataWarehouse edition. |
40884 | 16 | New service level objective ‘%.*ls’ has (%d) physical databases and it is not compatible with current service level objective which has (%d) physical databases. |
40885 | 16 | Failed to deactivate database. |
40886 | 16 | Failed to change service level objective for database. |
40887 | 16 | Failed to activate database. |
40888 | 16 | Update service level objective for database feature is disabled. |
40889 | 16 | The DTUs or storage limit for the elastic pool ‘%.*ls’ cannot be decreased since that would not provide sufficient storage space for its databases. |
40890 | 16 | The elastic pool is busy with another operation. |
40891 | 16 | The DTU min per database (%d) cannot exceed the DTU max per database (%d). |
40892 | 16 | Cannot connect to database when it is paused. |
40893 | 16 | The database copy link from ‘%s.%s’ to ‘%s.%s’ was not successfully created or was deleted before the data copy link operation completed. |
40894 | 16 | The database copy link from ‘%s.%s’ to ‘%s.%s’ is not in the catchup state after the data copy link operation completed. |
40895 | 16 | The database copy link from ‘%s.%s’ to ‘%s.%s’ was not successfully deleted before completion of copy. |
40896 | 16 | The database copy link from ‘%s.%s’ to ID %s was not successfully dropped. |
40897 | 16 | The elastic pool storage limit in megabytes must be at least (%d) for service tier ‘%.*ls’. |
40898 | 16 | The elastic pool storage limit in megabytes (%d) does not belong to the allowed values for service tier ‘%.*ls’. |
40899 | 16 | The DTUs (%d) for the elastic pool and the storage limit in megabytes (%d) are inconsistent for service tier ‘%.*ls’. |
40900 | 16 | The service tier for an elastic pool cannot be changed. |
40901 | 16 | The elastic pool storage limit in megabytes cannot exceed (%d) in service tier ‘%.*ls’. |
40902 | 16 | Amount of pool storage cannot be specified when creating a Premium elastic pool. |
40903 | 20 | The server ‘%.*ls’ is currently busy. Please wait a few minutes before trying again. |
40904 | 16 | Could not perform the operation because server would exceed the allowed Database Edition %s quota of %d. |
40905 | 16 | Location ‘%.*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. |
40906 | 16 | A service objective change cannot start for database %s on server %s while it is also running for database %s on server %s. |
40907 | 16 | Servers involved in a Disaster Recovery Configuration cannot reside in the same location |
40908 | 16 | A Disaster Recovery Configuration already exists for ‘%.*ls’ and ‘%.*ls’ |
40909 | 16 | A Disaster Recovery Configuration does not exist for ‘%.*ls’ and ‘%.*ls’ |
40910 | 16 | A Disaster Recovery Configuration does not exist for server ‘%.*ls’ and virtual endpoint ‘%.*ls’ |
40911 | 16 | Server ‘%.*ls’ is not the secondary in the Disaster Recovery Configuration and cannot initiate a failover |
40912 | 16 | The value for custom backup retention in days must be between %d and %d |
40913 | 16 | Windows Azure SQL Database supports a maximum of %d Virtual Network firewall rules. |
40914 | 16 | Cannot open server ‘%.*ls’ requested by the login. Client is not allowed to access the server. |
40915 | 16 | Secondary server specified in a Failover Group cannot reside in the same region |
40916 | 16 | The Failover Group ‘%.*ls’ already exists on server ‘%.*ls’ |
40917 | 16 | The Failover Group ‘%.*ls’ does not exist on server ‘%.*ls’ |
40918 | 16 | The Failover Group ‘%.*ls’ is busy with another operation and cannot perform the ‘%.*ls’ operation. Please try again later |
40919 | 16 | The server ‘%.*ls’ is currently the primary server in the Failover Group and cannot initate failover |
40920 | 16 | The database ‘%.*ls’ is already included in another Failover Group |
40921 | 16 | The operation to add database ‘%.*ls’ to Failover Group is in progress, please wait for this operation to finish |
40922 | 16 | The operation to remove database ‘%.*ls’ from Failover Group is in progress, please wait for this operation to finish |
40923 | 16 | The database ‘%.*ls’ is a secondary in an existing geo-replication relationship and cannot be added to the Failover Group |
40924 | 16 | The operation cannot be performed due to multiple errors: ‘%.*ls’ |
40925 | 16 | Can not connect to the database in its current state. |
40926 | 16 | The operation cannot be performed because the geo-replication link is part of a Failover Group. You must remove the database from the group in order to individually terminate or failover. |
40927 | 16 | The endpoint ‘%.*ls’ is already in use. Use a different Failover Group name. |
40928 | 16 | Create or update Failover Group operation successfully completed; however, some of the databases could not be added to or removed from Failover Group: ‘%.*ls’ |
40929 | 16 | The source database ‘%ls.%ls’ cannot have higher edition than the target database ‘%ls.%ls’. Upgrade the edition on the target before upgrading source. |
40930 | 16 | The target database ‘%ls.%ls’ cannot have lower edition than the source database ‘%ls.%ls’. Downgrade the edition on the source before downgrading target. |
40931 | 16 | Failover Group name ‘%.*ls’ cannot be empty or null. It can only be made up of lowercase letters ‘a’-‘z’, the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name. |
40932 | 16 | The elastic pool cannot change its service tier since one or more of its databases use memory-optimized objects. |
40933 | 16 | The edition ‘%.*ls’ does not support the database tempdb max size ‘%.*ls’. |
40934 | 16 | Server DNS Alias name ‘%.*ls’ cannot be empty or null. It can only be made up of lowercase letters ‘a’-‘z’, the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name. |
40935 | 16 | The endpoint ‘%.*ls’ is already in use. Use a different Server DNS Alias name. |
40936 | 16 | The Server DNS Alias ‘%.*ls’ already exists for the server ‘%.*ls’. |
40937 | 16 | The Server DNS Alias ‘%.*ls’ does not exist for the server ‘%.*ls’. |
40938 | 16 | The Server DNS Alias ‘%.*ls’ is busy with another operation and cannot perform the ‘%.*ls’ operation. Please try again later. |
40939 | 16 | The scale operation from service level objective ‘%.*ls’ to new service level objective ‘%.*ls’ is not supported. Please file a support ticket. |
40940 | 16 | The elastic pool ‘%.*ls’ cannot be updated because one of its databases is performing a copy or geo-replication failover operation. |
40941 | 16 | Copy operation for the database ‘%.*ls’ on the server ‘%.*ls’ cannot be started because the elastic pool ‘%.*ls’ is currently being updated. |
40942 | 16 | A service objective assignment operation cannot be performed because copy or failover operation for the database ‘%.*ls’ on the server ‘%.*ls’ is in progress. |
40943 | 16 | A Failover Group cannot be created on the server ‘%.*ls’ because the Table Auditing feature is enabled for this server. |
40944 | 16 | The database ‘%.*ls’ on the server ‘%.*ls’ cannot be added to a Failover Group because the Table Auditing or Security Enabled Access feature is turned on for this database. |
40945 | 16 | The Table Auditing feature cannot be turned on for a server that contains Failover Groups. Please try Blob Auditing instead. |
40946 | 16 | The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is part of a Failover Group. |
40947 | 16 | The Table Auditing or Security Enabled Access feature cannot be turned on for a database that is located on a server with a Server DNS Alias. |
40948 | 16 | A Server DNS Alias cannot be created for the server ‘%.*ls’ because the Table Auditing feature is enabled for this server. |
40949 | 16 | A Server DNS Alias cannot be created for the server ‘%.*ls’ because the database ‘%.*ls’ has the Table Auditing or Security Enabled Access feature enabled. |
40950 | 16 | The Dns Alias ‘%.*ls’ already exists for the elastic pool ‘%.*ls’ on server ‘%.*ls’. |
40951 | 16 | The Dns Alias ‘%.*ls’ does not exist for the elastic pool ‘%.*ls’ on server ‘%.*ls’. |
40952 | 16 | A Server DNS Alias cannot be created because server ‘%.*ls’ would exceed the allowed Server DNS Aliases quota of %d. |
40953 | 16 | A Failover Group cannot be created because server ‘%.*ls’ would exceed the allowed Failover Groups quota of %d. |
40954 | 16 | The Table Auditing feature cannot be turned on for a server that contains Server Dns Aliases. Please try Blob Auditing instead. |
40955 | 16 | The operation cannot be performed due to insufficient file space in the elastic pool. The operation requires (%d) MBs file space and there are (%d) 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. |
40956 | 16 | The Server Disaster Recovery Configuration feature is deprecated. Please use Failover Group instead. |
40957 | 16 | The DTU min per database must be at least (%d) for service tier ‘%.*ls’. |
40958 | 16 | The VCore max per database must be at least (%d) for service tier ‘%.*ls’. |
40959 | 16 | The VCore max per database cannot exceed (%d) for service tier ‘%.*ls’. |
40960 | 16 | The VCore max per database (%d) for the elastic pool does not belong to the specified values for service tier ‘%.*ls’. |
40961 | 16 | The VCore min per database cannot exceed (%d) for service tier ‘%.*ls’. |
40962 | 16 | The VCore min per database must be at least (%d) for service tier ‘%.*ls’. |
40963 | 16 | The VCore min per database (%d) for the elastic pool does not belong to the allowed values for service tier ‘%.*ls’. |
40964 | 16 | The VCore min per database (%d) cannot exceed the VCore max per database (%d). |
40965 | 16 | The service level objective ‘%.*ls’ does not support the license type ‘%.*ls’. |
40966 | 16 | No service objective was found for capacity ‘%d’ in edition ‘%.*ls’ |
40967 | 16 | More than one service objective was found for capacity ‘%d’ in edition ‘%.*ls’ |
40968 | 16 | Operation results in exceeding quota limits of %d. Maximum allowed: %d. |
40969 | 16 | Cannot open server ‘%.*ls’ requested by the login. Client is not allowed to access the server. |
40970 | 16 | Can not change from ‘%.*ls’ edition to ‘%.*ls’ edition. |
40971 | 16 | Cannot open Failover Group “%.*ls” requested by the login. The login failed. |
40972 | 16 | Database copy limit per database reached. The database ‘%ls’ cannot have more than %d concurrent database copies. |
40973 | 16 | Can not drop database because a failover operation is in progress on the failover group. |
40974 | 16 | Partner region specified does not match region of partner managed instance. |
40975 | 16 | Partner managed instance’s DNS Zone does not match the DNS Zone of the source managed instance. |
40976 | 16 | Instance 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” . |
40977 | 16 | ‘%.*ls’ is not a supported timezone. |
40978 | 16 | Instance 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. |
40979 | 16 | Database is unavailable because it is paused. Server ‘%.*ls’, Database ‘%.*ls’. Please resume before trying to access the database again. |
40980 | 16 | Partner managed server’s managed server/failover group has been dropped. |
40981 | 16 | Database ‘%.*ls’ is not accessible due to Azure Key Vault critical error. |
40982 | 16 | Instance failover group cannot be created because the secondary instance has user databases. |
40983 | 16 | Replication 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. |
40984 | 16 | Restore and GeoRestore target cannot be free database. |
40985 | 16 | Restore and GeoRestore are not supported for free database. |
40986 | 16 | Source database ‘%s’ dropped on ‘%s’ does not exist on server ‘%s’ within the supported recovery period. |
40987 | 16 | Source database ‘%s’ does not exist on server ‘%s’ within the supported recovery period. If restoring a dropped database, please specify its deletion date. |
40988 | 16 | The Hyperscale edition recovery requires both source and target databases to use VLDB service level objective. |
40989 | 16 | he Hyperscale edition Point-In-Time restore requires both source and target databases to use VLDB service level objective. |
40990 | 16 | Specifying an elastic pool and/or changing the service level objective or edition is not supported for ‘%s’ edition. |
41000 | 16 | Failed 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. |
41001 | 16 | Failed to obtain local computer name (Error code %d). The supplied buffer may be too small, or there is a system error. For information about this error code, see “System Error Codes” in the operating system documentation. |
41002 | 16 | Failed 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. |
41003 | 16 | Failed to obtain the local Windows Server Failover Clustering (WSFC) node ID (Error code %d). If this is a WSFC availability group, the WSFC service 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. |
41004 | 16 | Failed to obtain the Windows Server Failover Clustering (WSFC) group handle for cluster group with name or ID ‘%s’ (Error code %d). If this is a WSFC 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. |
41005 | 16 | Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID ‘%s’ (Error code %d). If this is a 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. |
41006 | 16 | Failed to create the Windows Server Failover Clustering (WSFC) group with name ‘%s’ (Error code %d). If this is a WSFC availability group, the WSFC 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. |
41007 | 16 | The Windows Server Failover Clustering (WSFC) group control API returned error code %d. If this is a WSFC availability group, the WSFC service may not 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. |
41008 | 16 | Failed to create the Windows Server Failover Clustering (WSFC) resource with name ‘%s’ and type ‘%s’ (Error code %d). If this is a WSFC availability 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. |
41009 | 16 | The 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. |
41010 | 16 | Failed to bring the Windows Server Failover Clustering (WSFC) group online (Error code %d). If this is a WSFC availability group, the WSFC service may 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. |
41011 | 16 | Failed to take the Windows Server Failover Clustering (WSFC) group offline (Error code %d). If this is a WSFC availability group, the WSFC service may 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. |
41012 | 16 | The Windows Server Failover Clustering (WSFC) node control API returned error code %d. If this is a WSFC availability group, the WSFC service may not 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. |
41013 | 16 | Failed 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. |
41014 | 16 | Failed 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. |
41015 | 16 | Failed to obtain the Windows Server Failover Clustering (WSFC) node handle (Error code %d) for node ‘%.*ls’. If this is a WSFC availability group, the 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. |
41016 | 16 | Failed to remove a node from the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code %d). If this is a WSFC 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. |
41017 | 16 | Failed to add a node to the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code %d). If this is a WSFC 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. |
41018 | 16 | Failed to move a Windows Server Failover Clustering (WSFC) group to the local node (Error code %d). If this is a WSFC availability group, the WSFC 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. |
41019 | 16 | Failed to drop a Windows Server Failover Clustering (WSFC) group with name or ID ‘%.*ls’ (Error code %d). If this is a WSFC availability group, the 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. |
41020 | 16 | Failed to find a String property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) resource with name or ID ‘%.*ls’ (Error code %d). 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. |
41021 | 16 | Failed 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. |
41022 | 16 | Failed 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. |
41023 | 16 | The 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. |
41024 | 16 | Failed 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. |
41025 | 16 | Failed 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. |
41026 | 10 | Failed 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. |
41027 | 16 | Failed 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. |
41028 | 16 | Failed to open Windows Server Failover Clustering (WSFC) registry root key (Error code %d). If this is a WSFC availability group, the WSFC service may 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. |
41029 | 16 | Failed 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. |
41030 | 16 | Failed to open the Windows Server Failover Clustering registry subkey ‘%.*ls’ (Error code %d). The parent key is %sthe cluster root key. If this is a 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. |
41031 | 16 | Failed 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. |
41032 | 16 | Failed 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. |
41033 | 16 | Failed 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. |
41034 | 16 | Failed 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. |
41035 | 16 | Failed 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. |
41036 | 16 | Failed 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. |
41037 | 16 | Failed to obtain a Windows Server Failover Clustering (WSFC) object enumeration handle for objects of type %d (Error code %d). If this is a WSFC 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. |
41038 | 16 | Failed 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. |
41039 | 16 | An 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. |
41040 | 16 | Failed 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. |
41041 | 16 | SQL Server instance to cluster node map entry cannot be found for the SQL Server instance ‘%.*ls’ and group ID ‘%.*ls’. The specified SQL Server instance name is invalid, or the corresponding registry entry does not exist. Verify the SQL Server instance name and retry the operation. |
41042 | 16 | The 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. |
41043 | 16 | For availability group ‘%.*ls’, the value of the name-to-ID map entry is invalid. The binary value should contain a resource ID, a group ID, and their 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. |
41044 | 16 | Availability group name to ID map entry for availability group ‘%.*ls’ cannot be found. The availability group name may be incorrect. If this is a 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. |
41045 | 16 | Cannot 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. |
41046 | 16 | Cannot 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. |
41047 | 16 | Failed to obtain the Windows Server Failover Clustering (WSFC) node state for the local WSFC node (Error code %d). If this is a WSFC availability 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. |
41048 | 10 | Always On Availability Groups: Local Windows Server Failover Clustering service has become unavailable. This is an informational message only. No user action is required. |
41049 | 10 | Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user action is required. |
41050 | 10 | Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required. |
41051 | 10 | Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required. |
41052 | 10 | Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required. |
41053 | 10 | Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required. |
41054 | 10 | Always 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. |
41055 | 10 | Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required. |
41056 | 16 | Availability 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. |
41057 | 16 | Failed 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. |
41058 | 10 | Always On: The local replica of availability group ‘%.*ls’ is starting. This is an informational message only. No user action is required. |
41059 | 10 | Always 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. |
41060 | 16 | The 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. |
41061 | 10 | Always On: The local replica of availability group ‘%.*ls’ is stopping. This is an informational message only. No user action is required. |
41062 | 16 | The 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. |
41063 | 16 | Windows 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. |
41064 | 16 | Failed to set local node as sole preferred owner for the Windows Server Failover Clustering (WSFC) group with ID ‘%.*ls’ (Error code: %d). The WSFC 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. |
41065 | 16 | Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID: ‘%.*ls’) online at this time. The WSFC resource is not in a state that can 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. |
41066 | 16 | Cannot 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. |
41067 | 16 | Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name ‘%.*ls’) at this time. The WSFC group is not in a state that could accept 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. |
41068 | 16 | Failed 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. |
41069 | 16 | The 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. |
41070 | 16 | Configuration 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. |
41071 | 16 | Cannot 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. |
41072 | 16 | The 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. |
41073 | 16 | The database ‘%.*ls’ cannot be removed from availability group ‘%.*ls’. This database does not belong to the availability group. |
41074 | 10 | Always 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. |
41075 | 10 | Always 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. |
41076 | 10 | Always On: Availability group ‘%.*ls’ is going offline because it is being removed. This is an informational message only. No user action is required. |
41077 | 16 | Cannot bring the Windows Server Failover Clustering (WSFC) group (ID ‘%.*ls’) online at this time. The WSFC group is not in a state that could accept 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. |
41078 | 16 | Failed 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. |
41079 | 16 | Cannot 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. |
41080 | 16 | Failed 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. |
41081 | 16 | Failed 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. |
41082 | 16 | Failed to obtain the name of local Windows Server Failover Cluster (Error code %d). If this is a WSFC availability group, the WSFC service may not be 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. |
41083 | 16 | Failed to obtain the cluster quorum resource (Error code %d). If this is a WSFC availability group, the WSFC service may not be running or may not be 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. |
41084 | 16 | The 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. |
41085 | 16 | Failed to find a DWORD property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) (Error code %d). If this is a WSFC availability 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. |
41086 | 16 | Failed 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. |
41087 | 16 | Error 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”). |
41088 | 16 | Failed 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”). |
41089 | 10 | Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user action is required. |
41090 | 10 | Failed to update Replica status due to exception %d. |
41091 | 10 | Always 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. |
41092 | 10 | Always On: The availability replica manager is going offline because %ls. This is an informational message only. No user action is required. |
41093 | 10 | Always 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. |
41094 | 10 | Always 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. |
41095 | 10 | Always 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. |
41096 | 10 | Always 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. |
41097 | 10 | Always 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. |
41098 | 10 | Always 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. |
41099 | 10 | Always 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. |
41100 | 16 | The 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. |
41101 | 16 | The 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. |
41102 | 10 | Failed to persist configuration data of availability group ‘%.*ls’. The local availability replica either is not the primary replica or is shutting down. |
41103 | 10 | Startup 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”). |
41104 | 16 | Failover 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. |
41105 | 16 | Failed to create the Windows Server Failover Clustering (WSFC) resource with name ‘%s’ and type ‘%s’. The resource type is not registered in the WSFC 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. |
41106 | 16 | Cannot 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. |
41107 | 16 | Availability 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. |
41108 | 16 | An 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. |
41109 | 17 | Could not enqueue a task (SQL OS error: 0x%x) for process actions for the availability group ‘%.*ls’. Most likely, the instance of SQL Server is low 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. |
41110 | 10 | Always On: The availability replica manager is starting. This is an informational message only. No user action is required. |
41111 | 10 | Always 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. |
41112 | 16 | A 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. |
41113 | 16 | Cannot 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. |
41114 | 16 | Cannot create an availability group named ‘%.*ls’ because it already exists in a system table. |
41115 | 16 | Cannot create the availability group named ‘%.*ls’ because its availability group ID (ID: ‘%.*ls’) already exists in a system table. |
41116 | 16 | Cannot create an availability group named ‘%.*ls’ with replica ID ‘%.*ls’ because this ID already exists in a system table. |
41117 | 16 | Cannot map local database ID %d to the availability database ID ‘%.*ls’ within availability group ‘%.*ls’. This database is already mapped to an availability group. |
41118 | 16 | Cannot 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. |
41119 | 16 | Could not find the availability group ID %d in the system table. |
41120 | 16 | Failed 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. |
41121 | 10 | The 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. |
41122 | 16 | Cannot 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. |
41123 | 16 | Cannot 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. |
41124 | 16 | The availability replica for availability group ‘%.*ls’ on this instance of SQL Server cannot become the primary replica because the availability group is being dropped. |
41125 | 16 | The 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). |
41126 | 16 | Operation 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. |
41127 | 16 | Attempt to set database mapping state where the local database id %d is not mapped to any availability group. |
41128 | 16 | Failed 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. |
41129 | 16 | Failed 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. |
41130 | 16 | Operation ‘%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. |
41131 | 10 | Failed 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. |
41132 | 16 | Cannot 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. |
41133 | 10 | Cannot 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. |
41134 | 16 | Cannot 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. |
41135 | 10 | Startup of Always On Availability Groups replica manager failed due to SQL Server error %d. To determine the cause of this error, check the SQL Server error log for the preceding error. |
41136 | 16 | Failed 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. |
41137 | 10 | Abandoning 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. |
41138 | 17 | Cannot 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. |
41139 | 10 | Failed 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. |
41140 | 16 | Availability 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. |
41141 | 16 | Failed 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. |
41142 | 16 | The 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. |
41143 | 16 | Cannot 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. |
41144 | 16 | The 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. |
41145 | 10 | Cannot 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. |
41146 | 16 | Failed 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. |
41147 | 10 | Always On Availability Groups was not started because %ls. This is an informational message. No user action is required. |
41148 | 16 | Cannot 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. |
41149 | 16 | Operation 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. |
41150 | 16 | Failed 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. |
41151 | 16 | Error 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. |
41152 | 16 | Failed 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. |
41153 | 16 | Failed 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. |
41154 | 16 | Cannot 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. |
41155 | 16 | Cannot 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. |
41156 | 16 | Cannot 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. |
41157 | 16 | Cannot 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. |
41158 | 16 | Failed 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. |
41159 | 16 | Failed 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. |
41160 | 16 | Failed 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. |
41161 | 16 | Failed 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. |
41162 | 16 | Failed 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. |
41163 | 16 | An 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. |
41164 | 16 | An 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. |
41165 | 16 | A 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. |
41166 | 16 | An 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. |
41167 | 16 | An 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. |
41168 | 16 | An 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. |
41169 | 16 | An 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. |
41170 | 10 | Post-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. |
41171 | 16 | Failed 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. |
41172 | 16 | An 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. |
41173 | 16 | An 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. |
41174 | 10 | Failed 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. |
41175 | 10 | Failed to stop the task of WSFC event notification worker (SQL OS error: %d). If the problem persists, you might need to restart the instance of SQL Server. |
41176 | 10 | Failed 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. |
41177 | 16 | The availability replica of the specified availability group ‘%.*ls’ is being dropped. Wait for the completion of the drop command and retry the operation later. |
41178 | 16 | Cannot 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. |
41179 | 16 | Cannot 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. |
41180 | 16 | Attempt 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. |
41181 | 16 | The 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. |
41182 | 16 | Failed 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. |
41183 | 16 | Failed 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. |
41184 | 16 | Failed 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. |
41185 | 10 | Replica option specified in ALTER AVAILABILITY GROUP ‘%.*ls’ MODIFY DDL is same is cached availability group configuration. |
41186 | 16 | Availability 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. |
41187 | 16 | Availability 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. |
41188 | 16 | Availability 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. |
41189 | 16 | Availability 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. |
41190 | 16 | Availability 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. |
41191 | 16 | The 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. |
41192 | 17 | Creating and scheduling a worker task for Always On Availability Groups failed due to lack of resources (SQL OS error %d). Processing of new actions 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. |
41193 | 10 | Cannot 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. |
41194 | 16 | An 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. |
41195 | 16 | Availability 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. |
41196 | 16 | Failed 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. |
41197 | 15 | The FAILOVER_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying a failover mode for the replica. |
41198 | 15 | The AVAILABILITY_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying an availability mode for the replica. |
41199 | 16 | The 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. |
41201 | 16 | The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support remote data sources. |
41202 | 16 | The 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. |
41203 | 16 | The 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. |
41204 | 16 | The source_key parameter is required in the SEMANTICSIMILARITYTABLE function. |
41205 | 10 | Error %d occurred during semantic index population for table or indexed view ‘%.*ls’ (table or indexed view ID %d, database ID %d, document ID %d) |
41206 | 10 | An ALTER FULLTEXT INDEX statement cannot remove the ‘STATISTICAL_SEMANTICS’ option from the last column in the index that has the option set when a “WITH NO POPULATION” clause is specified. Remove the “WITH NO POPULATION” clause. |
41207 | 10 | A locale ID that is not supported was specified for a column with ‘STATISTICAL_SEMANTICS’. Please verify that the locale ID is correct and that the corresponding language statistics has been installed. |
41208 | 10 | Warning: The population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) encountered a document with full-text key value ‘%ls’ that specifies a language not supported for semantic indexing. Some columns of the row will not be part of the semantic index. |
41209 | 10 | A semantic language statistics database is not registered. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated. |
41210 | 10 | The semantic language statistics database is not accessible or not valid. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated. |
41211 | 16 | A semantic language statistics database is already registered. |
41212 | 16 | No semantic language statistics database is registered. |
41213 | 16 | The database ‘%.*ls’ does not exist or the database format is not valid. Provide a valid semantic language statistics database name. |
41214 | 16 | An error occurred while trying to register the semantic language statistics database. |
41215 | 16 | The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support update or insert. |
41216 | 16 | The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support common table expressions. |
41300 | 16 | The current transaction cannot be committed and cannot support read or write operations. Roll back the transaction. |
41301 | 17 | A transaction dependency failure occurred, and the current transaction can no longer commit. Please retry the transaction. |
41302 | 16 | The current transaction attempted to update a record that has been updated since this transaction started. The transaction was aborted. |
41303 | 16 | The bucket count for a hash index must be a positive integer not exceeding %d. |
41304 | 10 | The current value of option ‘%.*ls’ for table ‘%.*ls’, index ‘%.*ls’ is %d. |
41305 | 17 | The current transaction failed to commit due to a repeatable read validation failure. |
41306 | 16 | The nesting limit of %d for conditional blocks and exception blocks, for natively compiled modules, has been exceeded. Please simplify the module. |
41307 | 10 | Warning: The row size limit of %d bytes for memory optimized tables has been exceeded and will not work on subscribers running SQL Server 2014 or earlier. Please simplify the table definition. |
41308 | 21 | The database ID %d already exists. |
41309 | 16 | Unable to load the compiled DLL for database ID %d. |
41310 | 16 | A file with an invalid format was detected. Check the SQL Server error log for more details. |
41311 | 16 | File error during C code generation. The error code was %d. |
41312 | 16 | Unable to call into the C compiler. GetLastError = %d. |
41313 | 16 | The C compiler encountered a failure. The exit code was %d. |
41314 | 16 | Conversion of default value for parameter ‘%.*ls’ failed. Unable to create stored procedure ‘%.*ls’. |
41315 | 16 | Checkpoint operation failed in database ‘%.*ls’. |
41316 | 16 | Restore operation failed for database ‘%.*ls’ with internal error code ‘0x%08lx’. |
41317 | 16 | A 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. |
41318 | 16 | Memory optimized tables and natively compiled modules cannot be accessed from within SQLCLR stored procedures. |
41319 | 16 | A maximum of %d predicates are allowed in the WHERE clauses of queries in natively compiled modules. |
41320 | 16 | EXECUTE AS clause is required, and EXECUTE AS CALLER is not supported, with natively compiled modules. |
41321 | 16 | The memory optimized table ‘%.*ls’ with DURABILITY=SCHEMA_AND_DATA must have a primary key. |
41322 | 16 | MAT/PIT export/import encountered a failure for memory optimized table or natively compiled module with object ID %d in database ID %d. The error code was 0x%x. |
41323 | 16 | The table type ‘%ls’ is not a memory optimized table type and cannot be used in a natively compiled module. |
41324 | 16 | The memory optimized table variable ‘%.*ls’ cannot be used in a batch with a ‘USE’ statement. |
41325 | 17 | The current transaction failed to commit due to a serializable validation failure. |
41326 | 16 | Memory optimized tables cannot be created in system databases. |
41327 | 16 | The memory optimized table ‘%.*ls’ must have at least one index or a primary key. |
41328 | 16 | A floating point operation has overflowed. |
41329 | 16 | Unsupported 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. |
41330 | 16 | Create database operation failed for database ‘%.*ls’. |
41331 | 17 | The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. Roll back the transaction. |
41332 | 16 | Memory optimized tables and natively compiled modules cannot be accessed or created when the session TRANSACTION ISOLATION LEVEL is set to SNAPSHOT. |
41333 | 16 | The 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. |
41334 | 16 | The code generation directory cannot be created or set up correctly. |
41335 | 16 | Modifying the collation of a database is not allowed when the database contains memory optimized tables or natively compiled modules. |
41337 | 16 | Cannot create %S_MSG. To create %S_MSG, the database must have a MEMORY_OPTIMIZED_FILEGROUP that is online and has at least one container. |
41338 | 16 | An invalid version of a data file was detected. Check the SQL Server error log for more details. |
41339 | 16 | The table ‘%.*ls’ has been created or altered after the start of the current transaction. The transaction was aborted. Please retry the transaction. |
41340 | 16 | The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated. |
41341 | 16 | Table ‘%.*ls’ is not yet available on the secondary replica. |
41342 | 16 | The 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. |
41343 | 16 | In-Memory OLTP hot switch to primary replica for database ‘%.*ls’ failed. |
41344 | 16 | RESTORE DATABASE WITH PARTIAL requires the MEMORY_OPTIMIZED_DATA filegroup if the backup contains a MEMORY_OPTIMIZED_DATA filegroup. |
41345 | 16 | The key size limit of %d bytes for nonclustered indexes on memory optimized tables has been exceeded. Please simplify the index definition. |
41346 | 16 | CREATE and UPDATE STATISTICS for memory optimized tables do not support the WHERE clause. |
41347 | 16 | A BACKUP or RESTORE DATABASE statement that includes the primary filegroup must include the MEMORY_OPTIMIZED_DATA filegroup, and vice versa. |
41348 | 16 | MEMORY_OPTIMIZED_DATA filegroups cannot be used with the FILESTREAM_ON clause. Specify a FILESTREAM filegroup. |
41349 | 10 | Warning: 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. |
41350 | 10 | Warning: A memory optimized table with durability SCHEMA_AND_DATA was created in a database that is enabled for encryption. The data in the memory optimized table will not be encrypted. |
41351 | 16 | An error occurred while processing the log. The log version is unsupported. |
41352 | 16 | The operation on database ID %d cannot complete because the database is in use. |
41353 | 16 | The operation on database ID %d cannot complete because the database is being dropped or being taken offline. |
41354 | 21 | The 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. |
41355 | 21 | An XTP checkpoint operation encountered an error (‘%ls’) while processing log record ID %S_LSN for database ‘%.*ls’. Checkpoint processing has terminated. |
41356 | 16 | Filegroups with MEMORY_OPTIMIZED_DATA can only be created in 64-bit installations of SQL Server. |
41357 | 16 | Tables with MEMORY_OPTIMIZED=ON can only be created in 64-bit installations of SQL Server. |
41358 | 16 | Stored procedures with NATIVE_COMPILATION can only be created in 64-bit installations of SQL Server. |
41359 | 16 | A 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). |
41360 | 16 | Default MEMORY_OPTIMIZED_DATA filegroup is not available in database ‘%.*ls’. |
41361 | 16 | The READ_ONLY property of a MEMORY_OPTIMIZED_DATA filegroup cannot be modified. |
41362 | 16 | FILESTREAM container ‘%.*ls’ cannot be added. Either the server is out of memory or the container path is too long. |
41363 | 16 | Only the owner of database ‘%.*ls’ or users with valid permission can execute the stored procedure ‘%.*ls’. |
41364 | 16 | Stored procedure ‘%.*ls’ can only be executed on a database that has an online MEMORY_OPTIMIZED_DATA filegroup. |
41365 | 16 | Merge 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. |
41366 | 16 | Merge operation failed because the requested transaction id range is invalid. |
41367 | 16 | Failed to complete merge operation for transaction range [%ld, %ld] for database ‘%.*ls’. Error was 0x%08x. |
41368 | 16 | Accessing 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). |
41369 | 16 | Merge operations cannot be requested on a secondary replica. |
41370 | 16 | Resource pool ‘%.*ls’ does not exist or resource governor has not been reconfigured. |
41371 | 16 | Binding to a resource pool is not supported for system database ‘%.*ls’. This operation can only be performed on a user database. |
41372 | 16 | Database ‘%.*ls’ is currently bound to a resource pool. A database must be unbound before creating a new binding. |
41373 | 16 | Database ‘%.*ls’ cannot be explicitly bound to the resource pool ‘%.*ls’. A database can only be bound to a user resource pool. |
41374 | 16 | Database ‘%.*ls’ does not have a binding to a resource pool. |
41375 | 16 | A binding has been created. Take database ‘%.*ls’ offline and then bring it back online to begin using resource pool ‘%.*ls’. |
41376 | 16 | Only members of the fixed sysadmin role can execute the stored procedure ‘%ls’. |
41377 | 16 | The 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. |
41378 | 16 | Both @database_id and @xtp_object_id should be specified to enable or retrieve status of query level statistics collection for a procedure. |
41379 | 16 | Restore 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. |
41380 | 21 | Databases with a MEMORY_OPTIMIZED_DATA filegroup are only supported in 64-bit editions of SQL Server. |
41381 | 21 | The database cannot be started in this edition of SQL Server because it contains a MEMORY_OPTIMIZED_DATA filegroup. See Books Online for more details on feature support in different SQL Server editions. |
41382 | 16 | Failure 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. |
41383 | 16 | An internal error occurred while running the DMV query. This was likely caused by concurrent DDL operations. Please retry the query. |
41384 | 16 | Database ‘%.*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. |
41385 | 16 | A memory-optimized table cannot be enabled for Change Data Capture (CDC). |
41386 | 16 | Filegroups 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. |
41387 | 10 | Disallowing 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. |
41388 | 16 | An upgrade operation failed for database ‘%.*ls’. Check the error log for additional details. |
41389 | 16 | Failed to create a backup file collection snapshot necessary for backup of database ‘%.*ls’. Check the error log for additional details. |
41390 | 16 | Failed to get checkpoint file information necessary for backup of database ‘%.*ls’. Check the error log for additional details. |
41391 | 23 | Backup of database ‘%.*ls’ detected a missing MEMORY_OPTIMIZED_DATA file with ID ‘%.*ls’. |
41392 | 16 | Cannot ALTER a natively compiled module into a non-native module. Include WITH NATIVE_COMPILATION or drop and recreate the module. |
41393 | 16 | Cannot ALTER a non-native module into a natively compiled module. Omit WITH NATIVE_COMPILATION or drop and recreate the module. |
41394 | 16 | TEXTSIZE must be a number between -1 and 2147483647. |
41395 | 10 | Rebuilding the log file is not supported for databases containing memory-optimized tables. |
41396 | 16 | The sort operation exceeded the buffer limit. The stored procedure execution was aborted. Consult SQL Server Books Online for more information. |
41397 | 16 | The TOP operator can return a maximum of %d sorted rows. %d was requested. Reduce the number of rows selected or simplify the query. |
41398 | 16 | The TOP operator can return a maximum of %d rows; %d was requested. |
41399 | 16 | The sort operation is too complex. Consult SQL Server Books Online for more information. |
41401 | 16 | WSFC cluster service is offline. |
41402 | 16 | The WSFC cluster is offline, and this availability group is not available. This issue can be caused by a cluster service issue or by the loss of quorum in the cluster. |
41403 | 16 | Availability group is offline. |
41404 | 16 | The availability group is offline, and is unavailable. This issue can be caused by a failure in the server instance that hosts the primary replica or by the WSFC availability group resource going offline. |
41405 | 16 | Availability group is not ready for automatic failover. |
41406 | 16 | The 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. |
41407 | 16 | Some availability replicas are not synchronizing data. |
41408 | 16 | In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the primary replica. |
41409 | 16 | Some synchronous replicas are not synchronized. |
41410 | 16 | In this availability group, at least one synchronous replica is not currently synchronized. The replica synchronization state could be either SYNCHONIZING or NOT SYNCHRONIZING. |
41411 | 16 | Some availability replicas do not have a healthy role. |
41412 | 16 | In this availability group, at least one availability replica does not currently have the primary or secondary role. |
41413 | 16 | Some availability replicas are disconnected. |
41414 | 16 | In this availability group, at least one secondary replica is not connected to the primary replica. The connected state is DISCONNECTED. |
41415 | 16 | Availability replica does not have a healthy role. |
41416 | 16 | The role of this availability replica is unhealthy. The replica does not have either the primary or secondary role. |
41417 | 16 | Availability replica is disconnected. |
41418 | 16 | This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED. |
41419 | 16 | Data synchronization state of some availability database is not healthy. |
41420 | 16 | At 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. |
41421 | 16 | Availability database is suspended. |
41422 | 16 | Either a database administrator or the system has suspended data synchronization on this availability database. |
41423 | 16 | Secondary database is not joined. |
41424 | 16 | This 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. |
41425 | 16 | Data synchronization state of availability database is not healthy. |
41426 | 16 | The 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. |
41427 | 16 | Availability replica is not joined. |
41428 | 16 | This 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. |
41500 | 10 | An 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. |
41501 | 16 | Failed 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. |
41502 | 16 | Failed 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. |
41503 | 16 | Client (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. |
41504 | 16 | Asynchronous 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. |
41505 | 16 | Asynchronous 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. |
41600 | 16 | An 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. |
41601 | 16 | Valid 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. |
41602 | 16 | An 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. |
41603 | 16 | The transport subscriber failed to process the build secondary replica event (partition ID %ls). If this condition persists, contact the system administrator. |
41604 | 16 | The transport subscriber failed to process the configuration change replica event (partition ID %ls). If this condition persists, contact the system administrator. |
41605 | 16 | Cannot 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. |
41606 | 16 | Replica (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. |
41607 | 16 | Operation 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. |
41608 | 16 | Failed 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. |
41609 | 16 | Operation timed out while waiting for %ls access to the list of replica controller objects. If this condition persists, contact the system administrator. |
41610 | 16 | Failed 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. |
41611 | 16 | Replica 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. |
41612 | 16 | An 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. |
41613 | 17 | Fabric 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. |
41614 | 10 | Fabric 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. |
41615 | 10 | Fabric 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. |
41616 | 16 | SQL 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. |
41617 | 10 | Fabric 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. |
41618 | 16 | Attempt 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. |
41619 | 16 | Windows 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. |
41620 | 10 | Build 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. |
41621 | 10 | Windows 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. |
41622 | 16 | Windows 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. |
41623 | 20 | The Database Mirroring endpoint port is unavailable. Verify that the DBM endpoint is created. |
41624 | 16 | Drop 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. |
41625 | 20 | The internal buffer for the replication URL is insufficient. |
41626 | 10 | Failed to retrieve service desription from Windows Fabric for partition ‘%ls’ (Windows Fabric error 0x%08x). If this condition persists, contact the system administrator. |
41627 | 10 | An 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. |
41628 | 10 | Drop 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. |
41629 | 10 | Fabric 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. |
41630 | 10 | Failed to update primary replica information for partition ‘%ls’ (Windows Fabric error 0x%08x). This is an informational message only. No user action is required. |
41631 | 16 | Fabric 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. |
41632 | 10 | The 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. |
41633 | 16 | Fabric 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. |
41634 | 10 | Open 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. |
41635 | 10 | Open 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. |
41636 | 16 | Fabric 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. |
41637 | 16 | The database ‘%ls’ (URI: ‘%ls’, partition ID ‘%ls’) is not currently participating in a GeoDR relationship. |
41638 | 16 | Could not retrieve remote replica storage configuration for database ‘%ls’ (URI: ‘%ls’). |
41639 | 16 | Could not retrieve remote replica configuration for database ‘%ls’ (URI: ‘%ls’). |
41640 | 10 | Database ‘%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. |
41641 | 16 | Could not send global cluster action ‘%ls’ request 0x%x. |
41642 | 10 | Undo 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. |
41643 | 16 | Could not retrieve the Distributed AG Configuration for database ‘%ls’ (URI: ‘%ls’, partition ID ‘%ls’) . Encountered error (error code: 0x%08X). |
41644 | 17 | Fabric 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. |
41645 | 16 | Fabric Service ‘%ls’ (partition ID ‘%ls’) encountered error (error code: 0x%08X) while querying for Fabric property ‘%ls’. |
41646 | 16 | Invalid Fabric property ‘%ls’ received for partition ‘%ls’. |
41647 | 17 | Failed to start the report fault thread during replica manager startup. |
41648 | 10 | Get 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. |
41649 | 10 | Could not submit Change Role completion tasks for %ls’ (URI: ‘%ls’, partition ID ‘%ls’) . Encountered error (error code: 0x%08X). |
41650 | 10 | Waiting for replica catchup for AGID ‘%ls’ and ReplicaID ‘%ls’ Failed. |
41651 | 16 | Invalid partition id in replica manager |
41652 | 17 | The replica manager is unavailable or not ready. |
41653 | 21 | Database ‘%.*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. |
41654 | 17 | Failed to start the clean up nonexistant DBs thread during replica manager startup. |
41655 | 10 | Could not submit logical reseeding task for ‘%ls’ (URI: ‘%ls’, partition id: ‘%ls’) . Encountered error (error code: 0x%08X). |
41656 | 17 | Failed to start the windows fabric load balancer reporting thread during replica manager startup. |
41657 | 16 | Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) failed the call to UseDB. |
41658 | 16 | Failed to automatically enable Query Store in Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) . |
41659 | 16 | Checkpoint for Database ‘%ls’ (ID %d) failed. Encountered error (error code: 0x%08X). |
41660 | 16 | Windows 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. |
41661 | 16 | There are no waiters on the DataLossEvent for Fabric Service ‘%ls’ (partition ID ‘%ls’). |
41662 | 16 | Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) hit exception while running async tasks in Generic Subscriber. |
41663 | 10 | Failed to parse datawarehouse columnar cache settings during replica manager startup. |
41664 | 10 | Failed to refresh remote replica configuration for fabric service ‘%ls’. |
41665 | 10 | Failed to resolve DW logical node id for physical database ‘%ls’, which is hosted by compute service: ‘%ls’. |
41666 | 16 | Waiting for replica catchup before GeoDR role change failed for with error %d for database ‘%ls’, DBID %d, AGID ‘%ls’, and ReplicaID ‘%ls’. |
41667 | 16 | Fabric Service ‘%ls’ (partition ID ‘%ls’) encountered error (error code: 0x%08X) while setting Fabric property ‘%ls’. |
41668 | 16 | Failed to transition to forwarder role for physical database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’). |
41669 | 16 | Database ‘%ls’ (ID %d) of Windows Fabric partition ‘%ls’ (partition ID ‘%ls’) hit exception while running async tasks in RbIo Subscriber. |
41670 | 16 | Cannot retrieve tempdb remote file lease order id. |
41700 | 16 | System 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. |
41701 | 20 | The 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. |
41702 | 20 | The 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. |
41703 | 20 | The 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. |
41704 | 20 | The 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. |
41705 | 20 | The computer name is unavailable. The computer name was not returned. |
41706 | 20 | Unable to get Fabric NodeContext. |
41801 | 16 | Failed to drop the memory optimized container ‘%.*ls’. |
41802 | 16 | Cannot drop the last memory-optimized container ‘%.*ls’. |
41803 | 16 | An In-Memory OLTP physical database was restarted while processing log record ID %S_LSN for database ‘%.*ls’. No further action is necessary. |
41804 | 16 | Internal 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. |
41805 | 16 | There 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. |
41806 | 16 | Parameter “%ls” specified for procedure or function “%ls” is not valid. |
41807 | 16 | A MARS batch failed due to a unique constraint violation on a memory optimized table. |
41808 | 16 | The current MARS batch attempted to update a record that has been updated by another batch within the same transaction. |
41809 | 16 | Natively compiled triggers do not support statements that output a result set. |
41810 | 16 | Stored procedures called from natively compiled triggers do not support statements that output a result set. |
41811 | 16 | XTP physical database was stopped while processing log record ID %S_LSN for database ‘%.*ls’. No further action is necessary. |
41812 | 16 | ALTER TABLE on memory-optimized tables is not supported with concurrent MARS transactions. |
41813 | 16 | XTP database ‘%.*ls’ was undeployed. No further action is necessary. |
41814 | 16 | The procedure ‘%.*ls’ cannot be called from a user transaction. |
41815 | 16 | Data migration on table id %d cannot be performed because the table is already in the process of migration. |
41816 | 16 | The parameter ‘%.*ls’ for procedure ‘%.*ls’ cannot be NULL. |
41817 | 16 | Invalid object id %d provided as input for procedure ‘%.*ls’. The object id must refer to a memory-optimized table with a column store index. |
41818 | 23 | An 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. |
41819 | 16 | A 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. |
41820 | 16 | A 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. |
41822 | 17 | There 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. |
41823 | 16 | Could 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. |
41824 | 16 | The transaction was killed by a concurrent ALTER operation or by a write-write conflict. |
41825 | 16 | Stored procedure ‘%.*ls’ cannot be used to increase the user memory limit on the database. |
41826 | 16 | Stored 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. |
41827 | 16 | Upgrade of XTP physical database ‘%.*ls’ requires restart of XTP engine. |
41828 | 16 | Creation of memory-optimized tables is temporarily disabled. Please try again later. |
41829 | 16 | The database cannot proceed with pricing-tier update as it has memory-optimized objects. Please drop such objects and try again. |
41830 | 16 | Upgrade of XTP physical database ‘%.*ls’ restarted XTP engine. |
41831 | 16 | Data migration on table id %d failed either fully or partially. See errorlog for details. |
41832 | 16 | Index ‘%.*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. |
41833 | 16 | Columnstore 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. |
41834 | 16 | ALTER TABLE has failed for ‘%.*ls’ with error code %d. |
41835 | 21 | An error (error code: 0x%08lx) occurred while adding encryption keys to XTP database ‘%.*ls’. |
41836 | 16 | Rebuilding log is not supported for databases containing files belonging to MEMORY_OPTIMIZED_DATA filegroup. |
41837 | 16 | Boot-page adjustment of XTP database ‘%.*ls’ requires restart of XTP engine. |
41838 | 16 | Failed to retrieve size for this file due to an internal error. Please try again later. |
41839 | 16 | Transaction exceeded the maximum number of commit dependencies and the last statement was aborted. Retry the statement. |
41840 | 16 | Could 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. |
41841 | 23 | Found inconsistent boot-page for database ‘%.*ls’. |
41842 | 16 | Too 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. |
41843 | 16 | Unable to construct segment for segment table. |
41844 | 15 | Clustered columnstore indexes are not supported on memory optimized tables with computed columns. |
41845 | 16 | Checksum verification failed for memory optimized checkpoint file %.*ls. |
41846 | 16 | Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not have unique recoverLsn. PrevLSN = (%I64d:%hu), CurrLSN = (%I64d:%hu). |
41847 | 16 | Memory optimized checkpoint table consistency error detected. Checkpoint %I64d does not point to a transaction segment definition record. |
41849 | 16 | Memory 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. |
41850 | 16 | Memory optimized segment table consistency error detected. Segments are not well formed for Segment CkptId = %I64d, LsnInfo = (%I64d:%hu), TxBegin = %I64d, TxEnd = %I64d. |
41851 | 16 | Memory 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. |
41852 | 16 | Memory optimized segment table consistency error detected. Segment has a NullHkLsn. CkptId = %I64d, Segment LsnInfo = (%I64d:%hu) |
41853 | 16 | Memory 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. |
41854 | 16 | Memory 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. |
41855 | 16 | Memory optimized file consistency error detected. Could not find a file with FileId %.*ls in the File Watermark Table visible by checkpoint ID %u. |
41856 | 16 | Memory optimized file consistency error detected. A file with FileId %.*ls of size %I64d bytes is smaller than expected %I64d bytes. |
41861 | 16 | Memory 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). |
41862 | 16 | Memory 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). |
41863 | 16 | Checkpoint %I64d points to a root file %.*ls which was in use by a more recent checkpoint. |
41864 | 16 | Checkpoint %I64d has a file %.*ls which has a watermark (%I64d) larger than the more recent checkpoints watermark (%I64d). |
41865 | 16 | File %.*ls does not have a pair file %.*ls |
41866 | 16 | Unprocessed File %.*ls does not have a pair file which is also unprocessed. Processed pair file is %.*ls. |
41867 | 16 | Consistency 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. |
41868 | 16 | Memory optimized filegroup checks could not be completed because of system errors. See errorlog for more details. |
41869 | 21 | In-memory OLTP version %u.%u is not supported on this platform. |
41870 | 10 | Dropped %d Orphan Internal Table(s). |
41871 | 16 | Failed to recreate XTP non-durable tables during recovery of the database ‘%.*ls’. |
41872 | 10 | Warning: 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. |
41901 | 16 | One or more of the options (%ls) are not supported for this statement in SQL Database Managed Instance. Review the documentation for supported options. |
41902 | 16 | Unsupported device type. SQL Database Managed Instance supports database restore from URI backup device only. |
41903 | 16 | FILENAME option is not allowed in SQL Database Managed Instance. |
41904 | 16 | BACKUP DATABASE failed. SQL Database Managed Instance supports only COPY_ONLY full database backups which are initiated by user. |
41905 | 16 | Stored procedure %ls is not supported in SQL Database Managed Instance. |
41906 | 16 | Statement ‘%.*ls’ is not supported in SQL Database Managed Instance. |
41907 | 16 | Unsupported file type during restore on SQL Database Managed Instance. |
41908 | 16 | Only ‘local’ routes are supported in SQL Database Managed Instance. |
41909 | 16 | Modifying logical file name is not supported in SQL Database Managed Instance. |
41910 | 16 | Add/remove/modify of log files is not supported in SQL Database Managed Instance. |
41911 | 16 | Adding or removing XTP file or filegroup is not allowed in SQL Database Managed Instance. |
41912 | 16 | Maximum number of databases for SQL Database Managed Instance reached. |
41913 | 16 | Multiple filestream files are not supported in SQL Database Managed Instance. |
41914 | 16 | SQL Server Agent feature %ls is not supported in SQL Database Managed Instance. Review the documentation for supported options. |
41915 | 16 | Memory-optimized filegroup must be empty in order to be restored on the current tier of SQL Database Managed Instance. |
41916 | 16 | Maximum number of %u files for SQL Database Managed Instance reached. |
41917 | 16 | Dropping local instance via sp_dropserver is not allowed in SQL Database Managed Instance. |
41918 | 16 | Specifying files and filegroups in CREATE DATABASE statement is not supported on SQL Database Managed Instance. |
41919 | 16 | Multiple backup sets in a single backup file are not supported in SQL Database Managed Instance. |
41920 | 16 | This feature is not supported through T-SQL on SQL Database Managed Instance. |
41921 | 16 | Restoring from a backup that contains multiple log files is not supported in SQL Database Managed Instance. |
41922 | 16 | The backup operation for a database with service-managed transparent data encryption is not supported on SQL Database Managed Instance. |
41923 | 16 | Cannot find server certificate with thumbprint ‘%.*ls’. Please use PowerShell Cmdlet ‘Add-AzureRmSqlManagedInstanceTransparentDataEncryptionCertificate’ to create the certificate. |
41924 | 16 | All files need to be smaller or equal to %d MB in this edition of Managed Instance. File id: %ld. Size: %I64d bytes. |
41925 | 16 | If 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. |
41926 | 16 | Secondary filegroup is not supported in this edition of Managed Instance. File id: %ld. |
41927 | 16 | The file name ‘XTP’ is reserved for the files containing In-Memory OLTP data. |
41928 | 16 | The filegroup name ‘XTP’ is reserved for the filegroup containing In-Memory OLTP data. |
41929 | 16 | One or more files are not in online state after the restore. |
41930 | 16 | Modifying number of files and max size for TempDb is not yet supported in SQL Database Managed Instance. |
41931 | 10 | Warning: New name of managed database ‘%.*ls’ is same as the old one. |
41932 | 16 | Cannot rename managed database ‘%.*ls’ because it’s currently in use. |
41933 | 21 | Failed to initialize detours and local time for Managed Instance. %ls |
41934 | 16 | Statement ‘%.*ls’ is not supported in the current version of the server. |
41935 | 16 | Managed Instance has reached the total capacity of underlying Azure storage account. Azure Premium Storage account is limited to 35TB of allocated space. |
41936 | 16 | This feature is not supported in the Hyperscale edition of SQL Database Managed Instance. |
42001 | 16 | Failed to parse XML configuration. The operating system returned error %ls. |
42002 | 16 | Failed to parse XML configuration. The parser returned error %.*ls |
42003 | 16 | Failed to parse XML configuration. A required attribute ‘%ls’ is missing. |
42004 | 16 | Failed to parse XML configuration. A required element ‘%ls’ is missing. |
42005 | 16 | Failed to parse XML configuration. Invalid value for attribute ‘%ls’. |
42006 | 16 | The default tempdb directory (‘%ls’) in XDB is not a valid path. |
42007 | 16 | The default tempdb directory (‘%ls’) in XDB is not a local path. |
42008 | 16 | ODBC error: State: %ls: Error: %d Message:’%ls’. |
42009 | 16 | Instance certificate ‘%ls’ cannot be found. |
42010 | 16 | Cannot initiate cross instance connection. |
42011 | 16 | ODBC initialization error: : %d. |
42012 | 16 | XodbcWrapper Enforced Retry For Testing. |
42013 | 16 | HTTP initialization error: : %d. |
42014 | 16 | Cannot retrieve server admin credential configuration. |
42015 | 20 | Error occurred while attempting to authenticate user remotely. Error %d, State %d. |
42016 | 16 | Error occurred in the DosGuard. |
42017 | 16 | Error occurred in the Redirector’s proxy while parsing a packet. Expected: %d, Actual: %d. |
42018 | 16 | Remote transaction has been doomed and cannot commit. |
42019 | 16 | %ls operation failed. %ls |
42020 | 16 | Updating name to ‘%.*ls’ failed. |
42021 | 16 | Initialization of http session handle for fetching federation metadata failed during AzureActiveDirectory initialization. |
42022 | 16 | Initialization of http connect handle for fetching federation metadata failed during AzureActiveDirectory initialization. |
42023 | 16 | Updating userdb properties on copy termination failed. |
42024 | 16 | Switching to logical master database failed. |
42025 | 16 | The extended recovery fork stack in the metadata of FCB is either corrupted or in an unexpected format. |
42026 | 16 | Loading the Active Directory Library failed. |
42027 | 16 | Initialization of the Active Directory Function pointers failed. |
42028 | 16 | The 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. |
42029 | 16 | An internal error happened while generating a new DBTS for database “%.*ls”. Please retry the operation. |
42030 | 16 | Updating logical master’s sys.databases on seeding completion failed. |
42031 | 16 | This functionality is not supported for A/B test isolated instances. |
42032 | 16 | XODBC Get Authentication Cache failed, state %d |
42033 | 16 | Updating Distributed AG Configuration failed. |
42034 | 16 | Boot of federation host failed with error 0x%08X. |
43001 | 16 | ‘%.*ls’ is not a valid login name. |
43002 | 16 | The storage size of %d MB exceeds the maximum allowed storage of %d MB. |
43003 | 16 | More than one firewall rules have the same name ‘%.*ls’. |
43004 | 16 | ‘%.*ls’ is not a valid firewall rule name because it contains invalid characters. |
43005 | 16 | ‘%.*ls’ is not a valid database name because it contains invalid characters. |
43006 | 16 | Database name ‘%.*ls’ is too long. |
43007 | 16 | ‘%.*ls’ is not a valid database charset. |
43008 | 16 | ‘%.*ls’ is not a valid database collation. |
43009 | 16 | The storage size of %d MB does not meet the minimum required storage of %d MB. |
43010 | 16 | ‘%.*ls’ cannot be updated. |
43011 | 16 | ‘%.*ls’ is not a valid version. |
43012 | 16 | The configuration name cannot be empty. |
43013 | 16 | The value for configuration ‘%.*ls’ cannot be empty. |
43014 | 16 | The same configuration ‘%.*ls’ cannot be updated more than once. |
43015 | 16 | The configuration ‘%.*ls’ does not exist for %.*ls server version %.*ls. |
43016 | 16 | The value ‘%.*ls’ for configuration ‘%.*ls’ is not valid. The allowed values are ‘%.*ls’. |
43017 | 16 | The configuration names you defined are not consistent. |
43018 | 16 | The value ‘%.*ls’ for configuration ‘%.*ls’ is not consistent with default value ‘%.*ls’. |
43019 | 16 | The source ‘%.*ls’ for configuration ‘%.*ls’ is not valid. |
43020 | 16 | The 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. |
43021 | 16 | The 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. |
43022 | 16 | The edition %.*ls is not a valid edition. Edition cannot be changed by restoring. |
43023 | 16 | The storage size of %d MB is lower than the source storage size. |
43024 | 16 | The version %.*ls is not a valid version. Version cannot be changed by restoring. |
43025 | 16 | Input parameter is incorrect. Please double check the input. |
43026 | 16 | Cannot drop system database ‘%.*ls’, skipping. |
43027 | 16 | Geo Restore is not supported. |
43028 | 16 | The replication feature is not supported. |
43029 | 16 | Edition %.*ls must be the same as the primary server when creating a replica server. |
43030 | 16 | Version %.*ls must be the same as the primary server when creating a replica server. |
43031 | 16 | The storage size of %d MB is lower than the primary server’s storage size. |
43032 | 16 | No available primary server %.*ls is found when creating a replica server. |
43033 | 16 | The primary server %.*ls already has the maximum of replica servers. |
43034 | 16 | The replica server is not in ready state when promoting. |
43035 | 16 | ‘%.*ls’ and ‘%.*ls’ cannot be updated together. |
43036 | 16 | Input parameter is incorrect when creating a replica server. Please double check the input. |
43037 | 16 | An 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. |
45001 | 16 | %ls operation failed. Specified federation name does not exist. |
45002 | 16 | %ls operation failed. Specified federation distribution name %.*ls is not valid. |
45003 | 16 | %ls operation failed. Specified data type is not supported as a federation distribution. |
45004 | 16 | %ls operation failed. Specified value is not valid for federation distribution %.*ls and federation %.*ls. |
45005 | 16 | Filter value cannot be set or was already set for this session. |
45006 | 16 | The federation key value is out of bounds for this member. |
45007 | 16 | %ls cannot be run while another federation operation is in progress on federation %.*ls and member with id %d. |
45008 | 16 | A partition in a table group that has a partition key defined is not allowed to be a federation member. |
45014 | 16 | %ls is not supported on %S_MSG. |
45015 | 16 | Specified federation operation id is already in use. |
45016 | 16 | Specified federation %.*ls does not exist. |
45017 | 16 | %ls operation failed. Specified federation name %.*ls is not valid. |
45018 | 16 | Specified federation operation id is invalid for %ls operation. |
45019 | 16 | %ls operation failed. Federation is in invalid state. |
45020 | 16 | %ls operation failed. %d is not a valid federation id. |
45021 | 16 | %ls operation failed. %d is not a valid federation member id. |
45022 | 16 | A column insert or update conflicts with a federation member range. The statement was terminated. The conflict occurred in database ‘%.*ls’, table ‘%.*ls’, column ‘%.*ls’. |
45023 | 16 | %ls cannot be called on %S_MSG. |
45024 | 16 | ALTER FEDERATION SPLIT operation failed. Specified boundary value already exists for federation distribution %.*ls and federation %.*ls. |
45025 | 16 | %ls operation failed. Specified boundary value is not valid for federation distribution %.*ls and federation %.*ls. |
45026 | 16 | %ls operation failed. Specified boundary value does not exist for federation distribution %.*ls and federation %.*ls. |
45027 | 16 | %ls operation failed. Specified type information is not valid for federation distribution. |
45028 | 16 | %ls operation failed. Specified boundary value is not valid for current federation member. |
45029 | 16 | %ls operation failed. The federation distribution scheme size cannot exceed 900 bytes. |
45030 | 15 | The USE FEDERATION statement is missing the required %.*ls option. Provide the option in the WITH clause of the statement. |
45031 | 16 | The USE FEDERATION statement is not supported on a connection which has multiple active result sets (MARS) enabled. |
45032 | 16 | The USE FEDERATION statement is not allowed under non-revertible impersonated security context. |
45033 | 16 | Federation member %d is not available. Another command is creating or dropping it. |
45034 | 16 | Federation member database cannot be dropped using DROP DATABASE. |
45035 | 16 | Federation member database cannot be renamed using ALTER DATABASE. |
45036 | 16 | ALTER FEDERATION SPLIT operation has been aborted. The %.*ls federation was dropped while the split was still in progress. |
45037 | 16 | ALTER 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. |
45038 | 16 | CREATE DATABASE AS COPY OF %S_MSG is not supported. |
45039 | 16 | Federation member database cannot be restored. |
45040 | 16 | Service objective for federation member database cannot be changed using ALTER DATABASE. |
45041 | 16 | Federation member database options cannot be changed. |
45042 | 16 | Federation root database options cannot be changed. |
45043 | 16 | ALTER FEDERATION SWITCH %ls is not supported on %ls members. |
45044 | 16 | ALTER FEDERATION SWITCH IN failed. %.*ls is not a valid database that can be switched in. |
45045 | 16 | ALTER FEDERATION SWITCH IN failed. %ls of the federation key in %.*ls doesn’t match with the correponding property of federation %.*ls. |
45046 | 16 | %ls operation failed. The specified value for federation %.*ls does not correspond to a present member. |
45101 | 16 | Parameter “%ls” should contain all configurable dimension properties. |
45102 | 16 | Parameter “%ls” should contain settings for all dimensions. |
45103 | 16 | Cannot reset the last setting for a dimension to non-default. |
45104 | 16 | The default setting cannot be deleted for a dimension. |
45105 | 16 | Cannot assign a deprecated setting as successor. |
45106 | 16 | Cannot create new item. The max provision count has been reached. |
45107 | 16 | Cannot reset service objective to draft from enabled or disabled state. |
45108 | 16 | Default service objective cannot be disabled. |
45109 | 16 | Parameter “%ls” contains conflicting dimension setting selections. |
45110 | 16 | Parameter %s value cannot be applied to service objective in non-draft mode. |
45111 | 16 | Cannot reset the last service objective to non-default. |
45112 | 16 | Cannot delete the default service objective. |
45113 | 16 | Cannot set the service objective as default in draft mode. |
45114 | 16 | Cannot edit setting marked as deprecated. |
45115 | 16 | Cannot assign a disabled service objective to a database. |
45116 | 16 | Cannot delete a setting without a successor assigned for deprecation. |
45117 | 16 | Cannot delete a system service objective. |
45118 | 16 | Cannot assign a system service objective to user database. |
45119 | 16 | Property selections contain conflicting values. |
45120 | 16 | The name ‘%ls’ already exists. Choose a different name. |
45121 | 16 | Server ‘%ls’ does not support memory-optimized data. Make sure both source and target servers are enabled for memory-optimized data. |
45122 | 16 | ‘%ls’ |
45123 | 16 | Updating max size is not supported for database ‘%ls’. Database size will grow automatically as more data is inserted. |
45125 | 16 | Parameter “%ls” cannot be empty or null. |
45126 | 16 | Parameter “%ls” is invalid. |
45127 | 16 | Parameter “%ls” is invalid. |
45128 | 16 | Parameter “%ls” is invalid. |
45129 | 16 | Parameter “%ls” is invalid. |
45130 | 16 | Parameter “%ls” is invalid. |
45131 | 16 | Parameter “%ls” is invalid. |
45132 | 16 | Every database must be assigned a service objective. |
45133 | 17 | A 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. |
45134 | 16 | The remote partner server name ‘%ls’ could not be resolved. |
45135 | 16 | Only continuous database copies can be updated. |
45136 | 16 | Only continuous database copies can be terminated. |
45137 | 16 | Insufficient permission to create a database copy on server ‘%ls’. |
45138 | 16 | The destination database name ‘%ls’ already exists on the server ‘%ls’. |
45139 | 16 | The source server name should be the server of the current connection. |
45140 | 16 | Maximum lag does not support the specified value. Maximum lag must be between ‘%ls’ and ‘%ls’. |
45141 | 16 | Database copies can only be initiated on the source server. |
45142 | 16 | IsForcedTerminate cannot be set while creating a database copy. This can only be updated on the source server after it is created. |
45143 | 16 | The source database ‘%ls’ does not exist. |
45144 | 16 | Continuous copy cannot be initiated on source database ‘%ls’ because it is a federation root member. |
45145 | 16 | Only continuous database copies can be created. |
45146 | 16 | Database copy property ‘%ls’ is required. |
45147 | 16 | Database copy property ‘%ls’ cannot be changed. |
45148 | 16 | ‘%ls’ is not supported for entity ‘%ls’. |
45149 | 16 | Continuous copy is not supported on ‘master’ database. |
45150 | 16 | Feature is disabled. |
45151 | 16 | Changing value(s) ‘%ls’ for entity ‘%ls’ not supported. |
45152 | 16 | 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. |
45153 | 16 | 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’. |
45154 | 16 | A 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. |
45155 | 16 | A 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. |
45156 | 16 | Subscription ‘%.*ls’ is busy with another operation. Please try your operation later. |
45157 | 16 | Server ‘%.*ls’ is busy with another operation. Please try your operation later. |
45158 | 16 | Cannot 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. |
45159 | 16 | Cannot 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. |
45160 | 16 | Subscription ‘%ls’ doesn’t have any servers to move. |
45161 | 16 | Managed instance ‘%.*ls’ is busy with another operation. Please try your operation later. |
45162 | 16 | Operation failed because subscription ‘%ls’ is disabled. |
45163 | 16 | Create Server request must either specify SQL login with password or denote admin login is a federated user by setting ‘IsFederatedAdminLogin’ property to ‘True’. |
45164 | 16 | Invalid number of database copies: ‘%d’. Only one database copy is currently allowed to be created along with the database creation. |
45165 | 16 | Continuous copy is not supported on the free database ‘%.*ls’. |
45166 | 16 | Database ‘%.*ls’ was %.*ls successfully, but some properties could not be displayed. |
45167 | 16 | An invalid state transition was attempted. |
45168 | 16 | The server ‘%.*ls’ has too many active connections. Try again later. |
45169 | 16 | The subscription ‘%.*ls’ has too many active connections. Try again later. |
45170 | 16 | A trusted certificate was not found for this request. |
45171 | 16 | Secondary database must be created in the same server as primary database unless ‘IsContinuous’ is specified. |
45172 | 16 | The ‘MaximumLag’ parameter requires that ‘IsContinuous’ is specified. |
45173 | 16 | Source server not found for subscription: %ls, resource group: %ls, server name: %ls. |
45174 | 16 | Unable to queue server %ls for migration. There is a pending migration request for the server. |
45175 | 16 | Unable to queue server %ls for migration. A migration is already in progress. |
45176 | 16 | Unable to queue server %ls for migration. The server is using feature %ls that prevents it from being migrated. |
45177 | 16 | Unable to queue server %ls for migration. Failed to find a target cluster for migration. |
45178 | 16 | Database create mode ‘%ls’ is not supported. |
45179 | 16 | The operation timed out and automatically rolled back. Please retry the operation. |
45180 | 16 | Resource with the name ‘%ls’ already exists. To continue, specify a different resource name. |
45181 | 16 | Resource with the name ‘%ls’ does not exist. To continue, specify a valid resource name. |
45182 | 16 | Database ‘%ls’ is busy with another operation. Please try your operation later. |
45183 | 16 | There is an import or export operation in progress on the database ‘%ls’. |
45184 | 16 | Operation Id ‘%ls’ was not found. |
45185 | 16 | The 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’. |
45186 | 16 | Database create mode ‘%ls’ is not supported in state ‘%ls’. |
45187 | 16 | The 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’. |
45188 | 16 | The operation has been cancelled by user. |
45189 | 16 | Insufficient permission to add secondary on server ‘%ls’. |
45190 | 16 | ‘%ls’ is an invalid name because it contains one or more unsupported unicode characters. |
45191 | 16 | The 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. |
45192 | 16 | The value specified for ‘allow_connections’ does not match the value for the existing replication relation for database ‘%ls’ on server ‘%ls.’ |
45193 | 16 | Database ‘%ls’ on server ‘%ls’ is already the target in another replication relationship. |
45194 | 16 | The 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.’ |
45195 | 16 | The operation could not be completed because database ‘%ls’ on server ‘%ls’ is the source in another replication relationship. |
45196 | 16 | The operation on the resource could not be completed because it was interrupted by another operation on the same resource. |
45197 | 17 | A system maintenance operation is in progress on server ‘%.*ls’ and database ‘%.*ls.’ Please wait a few minutes before trying again. |
45198 | 16 | MODIFY LOG FILE failed. Size is greater than MAXSIZE. |
45199 | 16 | This 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. |
45200 | 16 | The server ‘%ls’ are not associated with the tenant ‘%ls’. |
45201 | 16 | SQL Server Agent service is not running. |
45202 | 16 | Timed out after %ld seconds waiting for Smart Admin job to complete. Please run the stored procedure again. |
45203 | 16 | The 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. |
45204 | 16 | The parameter %ls cannot be NULL or empty. Provide a valid %ls. |
45205 | 16 | No backup setting is supplied. Please specify at least one backup setting to be configured. |
45206 | 16 | The value specified for parameter @type is invalid. The @type parameter value should either be ‘Database’ or ‘Log’. |
45207 | 16 | %ls |
45208 | 16 | SQL Server Managed Backup to Windows Azure master switch is not turned on. |
45209 | 16 | The parameter value for notification email is not specified or is NULL. Please specify a valid email to enable notifications for Smart Admin. |
45210 | 16 | Database Mail is not enabled for SQL Agent to use for Notifications. Enable Database Mail as the mail system for alerts. |
45211 | 16 | Database mail profile is not setup for SQL Agent notifications. |
45212 | 16 | The value specified for parameter %ls is invalid. Provide a valid %ls. |
45213 | 16 | @full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must be specified if @scheduling_option is set to ‘Custom’ |
45214 | 16 | @days_of_week must be specified if @full_backup_freq_type is set to ‘Weekly’ |
45215 | 16 | Local caching is not yet supported. |
45216 | 16 | @full_backup_freq_type, @backup_begin_time, @backup_duration, and @log_backup_freq must not be specified if @scheduling_option is set to ‘System’ |
45217 | 16 | @encryptor_type, and @encryptor_name must not be specified if @encryption_algorithm is set to ‘NO_ENCRYPTION’ |
45218 | 16 | @encryptor_type, and @encryptor_name must be specified if @encryption_algorithm is not set to ‘NO_ENCRYPTION’ |
45219 | 16 | @days_of_week must not be specified if @full_backup_freq_type is set to ‘Daily’ |
45220 | 10 | An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d. |
45221 | 10 | An error occurred while configuring for the SQL Agent: error %d, severity %d, state %d. |
45301 | 17 | The resource has been moved to another location |
45302 | 17 | SLO ‘%ls’ operation cannot succeed as the memory usage of ‘%ls’ exceeds the quota. |
45303 | 17 | Attempt 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. |
45304 | 16 | Elastic pool estimate ‘%.*ls’ was not found for server ‘%.*ls’ |
45305 | 16 | Request could not be processed because of conflict in the request: ‘%.*ls’ |
45306 | 16 | The external admin cannot be set because the user or group already exists in the ‘master’ database. |
45307 | 16 | Advisor ‘%.*ls’ was not found for requested resource |
45308 | 16 | Recommended action ‘%.*ls’ was not found for advisor ‘%.*ls’ |
45309 | 16 | The 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. |
45310 | 16 | Unable to return metrics. Request would return too much data. |
45311 | 16 | The server key ‘%.*ls’ already exists. Please choose a different server key name. |
45312 | 16 | The server key URI ‘%.*ls’ already exists as another server key. |
45313 | 16 | The server key ‘%.*ls’ cannot be deleted because it is currently in use by ‘%.*ls’. |
45314 | 16 | Server key ‘%.*ls’ does not exist. Make sure that the server key name is entered correctly. |
45315 | 16 | The 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. |
45316 | 16 | MODIFY FILE failed. Size is greater than MAXSIZE. Please query sys.database_files and use DBCC SHRINKFILE to reduce the file size first. |
45317 | 16 | Server ‘%.*ls’ does not exist in resource group ‘%.*ls’ in subscription ‘%.*ls’. |
45318 | 16 | Service Fabric Application Version is not available. |
45319 | 16 | The 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. |
45320 | 16 | The operation could not be completed on server ‘%.*ls’ because the Azure Key Vault key ‘%.*ls’ is disabled. |
45321 | 16 | The operation could not be completed on server ‘%.*ls’ because attempts to connect to Azure Key Vault ‘%.*ls’ have failed |
45322 | 16 | The 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. |
45323 | 16 | Unable to start a copy because the source database ‘%ls’ is being updated. |
45324 | 16 | The operation could not be completed because the Azure Key Vault Uri is null or empty. |
45325 | 16 | The operation could not be completed because the Azure Key Vault Key name is null or empty. |
45326 | 16 | The operation could not be completed because the Azure Key Vault Key name ‘%ls’ does not exist. |
45327 | 16 | The operation could not be completed because the Azure Key Vault Key name ‘%ls’ is currently set as server encryption protector. |
45328 | 16 | The server identity is not correctly configured on server ‘%ls’. (https://aka.ms/sqltdebyoksetup) |
45329 | 16 | An invalid response from Azure Key Vault. Please use a valid Azure Key Vault URI. |
45330 | 16 | The 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) |
45331 | 16 | The operation could not be completed because the read scale value specified is not supported for a ‘%ls’ database. |
45332 | 16 | The operation could not be completed because the read scale value specified is invalid. |
45333 | 16 | The service request timed out. %ls. |
45334 | 16 | Server edition ‘%ls’ is invalid. |
45335 | 16 | Server type ‘%ls’ is invalid. |
45336 | 16 | The 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. |
45337 | 16 | The 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. |
45338 | 16 | The 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. |
45339 | 16 | The max size update on the geo-secondary database ‘%ls’ on server ‘%ls’ failed with reason ‘%ls’. |
45340 | 16 | The operation could not be completed because an Azure Active Directory error was encountered. The error message from Active Directory Authentication library (ADAL) is ‘%ls’. |
45341 | 16 | The 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’. |
45342 | 16 | The 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’. |
45343 | 16 | The 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’. |
45344 | 16 | Catalog DB creation failed. |
45345 | 16 | Cannot cancel database management operation ‘%ls’ in the current state. |
45346 | 16 | Subnet resource ID ‘%ls’ is invalid. Please provide a correct resource Id for the target subnet. |
45347 | 16 | LongTermRetentionBackup is enabled for server ‘%ls’. Move server cross subscription is not allowed. |
45348 | 16 | LongTermRetentionBackup is enabled for server ‘%ls’. Move server cross resource group is not allowed. |
45349 | 16 | The operation could not be completed because certificate rotation is in progress for server ‘%ls’. |
45350 | 16 | MODIFY 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’ |
45351 | 16 | MODIFY MAXSIZE failed. The requested database size is smaller than the amount of data storage used. |
45352 | 16 | Create 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. |
45353 | 16 | This private cluster is associated with TR %ls. You specified TR %ls as a parameter. |
45354 | 16 | Tenant 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. |
45355 | 16 | The storage account %ls is not valid or does not exist. |
45356 | 16 | The storage account credentials are not valid. |
45357 | 16 | Auditing cannot be configured on secondary databases. |
45358 | 16 | Server auditing settings are being updated for server ‘%ls’. Please wait for the existing operation to complete. |
45359 | 16 | Database name validation failed. The database name is not allowed because it contains trailing whitespace characters. |
45360 | 16 | The operation could not be completed because app config deployment is in progress for the app ‘%ls’. |
45361 | 16 | Invalid 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. |
45362 | 16 | The 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’. |
45363 | 16 | Server automatic tuning settings from previous request have not propagated to all databases yet. Please try again in few minutes. |
45364 | 16 | The operation could not be completed because database ‘%ls’ on server ‘%ls’ is currently unavailable. Try again later. If the problem persists, contact customer support. |
45365 | 16 | vCore value (%d) is not valid. Please specify a valid vCore value. |
45366 | 16 | The retention days of %d is not a valid configuration. Valid backup retention in days must be between %d and %d. |
45367 | 16 | Invalid virtual network configuration. This is not allowed: %ls. |
45368 | 16 | The given rule ID: %s is invalid. You can find valid rule ids in scan results file. |
45369 | 16 | No baseline is set for rule ID: %d. You should first set a baseline for this rule. |
45370 | 16 | Vulnerability Assessment scan on the resource ‘%ls’ is in progress. Please wait for the existing operation to complete. |
45371 | 16 | Cannot cancel management operation ‘%ls’ in the current state.%ls |
45372 | 16 | Automatic tuning option ‘%.*ls’ was not found for requested resource. |
45373 | 16 | Automatic tuning is not supported for SQL Data Warehouse. |
45374 | 16 | HardwareGeneration ‘%ls’ is not valid. Please specify a valid HardwareGeneration value. |
45375 | 16 | vCore value (%d) and HardwareGeneration ‘%ls’ is not a valid combination. Please specify a valid vCore and HardwareGeneration value. |
45376 | 16 | Managed Instance cannot be joined to a classic virtual network. Please provide a Resource Manager vnet to join. |
45377 | 16 | The 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) |
45378 | 16 | geo-redundant-backup not supported for the current edition. |
45379 | 16 | geo-redundant-backup value is not allowed to update |
45380 | 16 | The edition %.*ls is not a valid edition. Edition cannot be changed by update. |
45381 | 16 | SKU Name ‘%ls’ is not valid. Please specify a valid SKU Name. |
45382 | 16 | Read or write operaions are not allowed on the storage account ‘%ls’. |
45383 | 16 | The storage account ‘%ls’ is disabled. |
45384 | 16 | The 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) |
45385 | 16 | Unexpected 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) |
45386 | 16 | The 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. |
45387 | 16 | Invalid hardware generation. It isn’t allowed to have both Gen4 and Gen5. |
45388 | 16 | Target subnet has associated Network Security Group (NSG). Remove %ls. (https://go.microsoft.com/fwlink/?linkid=871071) |
45389 | 16 | Target 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) |
45390 | 16 | Target 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) |
45391 | 16 | Invalid 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) |
45392 | 16 | SQL service endpoint is currently not allowed on Managed Instance. Remove SQL service endpoint from %ls. (https://go.microsoft.com/fwlink/?linkid=871071) |
45393 | 16 | Target subnet is not empty. Remove all resources from %ls or use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071) |
45394 | 16 | Virtual network for the target subnet is locked. Remove the lock from %ls. (https://go.microsoft.com/fwlink/?linkid=871071) |
45395 | 16 | Gateway subnet cannot be used for deploying managed instance. Use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071) |
45396 | 16 | Target subnet %ls does not exist. Use a different empty subnet. (https://go.microsoft.com/fwlink/?linkid=871071) |
45397 | 16 | Managed 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. |
45398 | 16 | The specified edition %ls is not consistent with the specified SKU %ls. |
45399 | 16 | The specified license type %ls is not valid. |
45400 | 16 | Invalid storage size: %ls GB. Storage size must be specified between %ls and %ls gigabytes, in increments of %ls GB. |
45401 | 16 | Ring buildout ‘%ls’ has no support for small VM roles, role: ‘%ls’. |
45402 | 16 | Ring buildout ‘%ls’ does not support multiple DB roles. |
45403 | 16 | The 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. |
45404 | 16 | The operation failed because update SLO safety checks could not be completed. Details: ‘%ls’. |
45405 | 16 | The operation failed because a long running transaction was found on the SQL instance. Please wait for the transaction to finish execution and try again. |
45406 | 16 | Provisioning of zone redundant database/pool is not supported for your current request. |
45407 | 16 | The operation timed out and failed: ‘%ls’ |
45408 | 16 | Resource not found: ‘%ls’. |
45409 | 16 | Network resource provider returned following error: ‘%ls’. |
45410 | 16 | Network resource provider denied access: ‘%ls’. |
45411 | 16 | Virtual 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. |
45412 | 16 | Failover 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. |
45413 | 16 | Only one Interface endpoint profile is allowed. |
45414 | 16 | The instance collation cannot be changed on Managed Instance. |
45415 | 16 | Creating secondary of secondary (a process known as chaining) is not supported when enabling Transparent Data Encryption using Azure Key Vault (BYOK). |
45416 | 16 | Cannot create a Managed Instance with collation ‘%.*ls’. Please use collation ‘SQL_Latin1_General_CP1_CI_AS’ instead. |
45417 | 16 | Vulnerability Assessment storage container path must be supplied |
45418 | 16 | The 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. |
45419 | 16 | The 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. |
45420 | 16 | The operation failed because update elastic pool safety checks could not be completed. Details: ‘%ls’. |
45421 | 16 | The operation failed because a long running transaction was found on the elastic pool. Please wait for the transaction to finish execution and try again. |
45422 | 16 | The 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. |
45423 | 16 | The 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. |
45424 | 16 | The operation could not be completed because %ls operation is in progress. Please wait for the operation in progress to complete and try again. |
45425 | 16 | The 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. |
45426 | 16 | The operation could not be completed because instance has configured geo replicated secondary instance. |
45427 | 16 | Hardware generation of the source is ‘%.*ls’ while that of the PITR target is ‘%.*ls’. |
45428 | 16 | The 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. |
45429 | 16 | The 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. |
45430 | 16 | The 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). |
45431 | 16 | The 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. |
45432 | 16 | Invalid storage size: Storage size limit (%ls GB) is less that current storage used (%ls GB). Please specify higher storage size limit. |
45433 | 16 | The specified family %ls is not consistent with the specified SKU %ls. |
45434 | 16 | The point in time ‘%.*ls’ for restoration can’t be later than now. |
45435 | 16 | The 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). |
45436 | 16 | The operation could not be completed. The requested storage update would cause the master server to have a larger storage size than its replica(s). |
45437 | 16 | The operation could not be completed. Replication is not enabled for the server. |
45438 | 16 | The timezone cannot be changed on Managed Instance. |
45439 | 16 | Cannot create a Managed Instance with timezone ‘%.*ls’. Please use timezone ‘UTC’ instead. |
45440 | 16 | Cannot create a Managed Instance as there are not enough available ip addresses in the selected subnet. |
45441 | 16 | Elastic server restore verification is not supported. |
45442 | 16 | The 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. |
45443 | 16 | Storage Auto Grow is not supported . |
45444 | 16 | Provisioning of Zone Redundant server is not supported . |
45445 | 16 | Storage Auto Grow is not supported for Primary and Replica Servers. |
45446 | 16 | Geo Reduntant Backup not supported for Zone Redundant Server. |
45447 | 16 | Database cannot be paused because it is not supported on a ‘%ls’ database. |
45448 | 16 | Database with ‘%ls’ feature cannot be paused. Operation failed for Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
45449 | 16 | The database is already paused. Server ‘%.*ls’, Database ‘%.*ls’, Paused Time ‘%.*ls’. |
45450 | 16 | The database is already resumed. Server ‘%.*ls’, Database ‘%.*ls’. |
45451 | 16 | Database operation failed because database is paused. Server ‘%.*ls’, Database ‘%.*ls’ |
45452 | 16 | Database operation failed because database is paused. Server ‘%.*ls’, Database ‘%.*ls’ |
45453 | 10 | The operation failed due to throttling. Server ‘%.*ls’, Database ‘%.*ls’ |
45454 | 16 | The operation failed because it is not supported on disabled database. Server ‘%.*ls’, Database ‘%.*ls’ |
45455 | 16 | The operation failed because it is not supported on geo replicated databases. Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
45456 | 16 | The request failed because there is an ongoing ‘%.*ls’ operation. Server ‘%.*ls’, Database ‘%.*ls’. |
45457 | 16 | The request failed because there is an ongoing migration on server ‘%.*ls’, database ‘%.*ls’. |
45458 | 16 | Choosen subnet is delegated and cannot be used for deploying managed instance. Remove delegation from subnet. |
46501 | 15 | External table references ‘%S_MSG’ that does not exist. |
46502 | 15 | Type with name ‘%.*ls’ already exists. |
46503 | 15 | Invalid format for option ‘%S_MSG’. |
46504 | 15 | External option ‘%S_MSG’ is not valid. Ensure that the length and range are appropriate. |
46505 | 15 | Missing required external DDL option ‘%S_MSG’. |
46506 | 15 | Invalid set of options specified for ‘%S_MSG’. |
46507 | 15 | Cannot perform DML on external tables. |
46508 | 15 | Incorrect syntax on external DDL option ‘%S_MSG’. |
46509 | 15 | FILE_FORMAT must be specified for HADOOP data source. |
46510 | 15 | FILE_FORMAT cannot be specified for RDBMS data source. |
46511 | 15 | EXTERNAL %S_MSG with id %d cannot be found. |
46512 | 15 | %S_MSG cannot be used with %S_MSG data source. |
46513 | 15 | A sharding column name must be provided when using SHARDED distribution. |
46514 | 15 | DISTRIBUTION must be specified when using a SHARD_MAP_MANGER data source. |
46515 | 15 | The specified sharding column name does not match any column in the external table definition. |
46516 | 15 | The specified credential cannot be found or the user does not have permission to perform this action. |
46517 | 17 | XML Parse error when de-serializing PDW Metadata. |
46518 | 15 | The %S_MSG ‘%ls’ is not supported with %S_MSG. |
46519 | 15 | %ls are not supported with %S_MSG. |
46520 | 15 | The external DDL statement contained an unrecognized option. |
46521 | 15 | Queries 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. |
46522 | 10 | Failed to update ‘%S_MSG’. |
46523 | 15 | A SCHEMA_NAME must be specified when using OBJECT_NAME. |
46524 | 15 | An OBJECT_NAME must be specified when using SCHEMA_NAME. |
46525 | 15 | External tables are not supported with the %S_MSG data source type. |
46526 | 15 | The %S_MSG operation is not supported with %S_MSG data source type. |
46527 | 15 | Altering the ‘%S_MSG’ property is not permitted for an external data source of type %ls. |
46528 | 15 | SHARDED DISTRIBUTION is allowed for SHARD_MAP_MANGER data source only. |
46529 | 15 | Allowed integer values for FIRST_ROW are between and including 1-101 |
46530 | 15 | External data sources are not supported with type %S_MSG. |
46531 | 15 | Support for external data sources of type HADOOP is not enabled. To enable, set ‘hadoop connectivity’ to desired value. |
46532 | 15 | Sp_rename is not supported for data pool external table. |
46533 | 15 | Internal error occurred during distributed operation. |
46534 | 15 | A maximum of three NULL_VALUES are allowed in the list. |
46535 | 15 | Unable to retrieve secret [%s] from the secret store. |
46536 | 15 | Unable to process secret [%s] from the secret store. |
46537 | 16 | An unexpected internal error, failed to communicate with controller service, HRESULT 0x%x. |
46538 | 16 | An unexpected internal error received from controller service error code [%i]. |
46539 | 15 | ‘%S_MSG’ statement failed. At least one partitioning column is required when distribution type is ‘%S_MSG’. |
46540 | 15 | ‘%S_MSG’ statement failed. Partitioning columns can be specified only if distribution type is ‘%S_MSG’. |
46541 | 15 | ‘%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. |
46542 | 15 | %S_MSG statement failed. One or more errors occurred while executing the statement. %s |
46543 | 15 | %S_MSG statement failed. Invalid URI provided. |
46545 | 15 | Creating external data source over data pools is not supported in a system database. |
46601 | 16 | REJECT_TYPE |
46602 | 16 | FILE_FORMAT |
46603 | 16 | REJECT_VALUE |
46604 | 16 | REJECT_SAMPLE_VALUE |
46605 | 16 | LOCATION |
46606 | 16 | DATA_SOURCE |
46607 | 16 | PERCENTAGE |
46608 | 16 | ROW_TERMINATOR |
46609 | 16 | DATA_COMPRESSION |
46610 | 16 | SERDE_METHOD |
46611 | 16 | ENCODING |
46612 | 16 | STRING_DELIMITER |
46613 | 16 | DATE_FORMAT |
46614 | 16 | FIELD_TERMINATOR |
46615 | 16 | FORMAT_TYPE |
46616 | 16 | JOB_TRACKER_LOCATION |
46617 | 16 | EXTERNAL TABLE |
46618 | 16 | HADOOP |
46619 | 16 | RDBMS |
46620 | 16 | SHARD_MAP_MANGER |
46621 | 16 | SHARDING_COLUMN_NAME |
46622 | 16 | DISTRIBUTION |
46623 | 16 | DATABASE_NAME |
46624 | 16 | SHARD_MAP_NAME |
46625 | 16 | CREDENTIAL |
46626 | 16 | REMOTE_SCHEMA_NAME |
46627 | 16 | REMOTE_OBJECT_NAME |
46628 | 16 | SHARED_MEMORY |
46629 | 16 | EXTRACTOR |
46643 | 16 | external tables |
46644 | 16 | external tables for sharded data |
46645 | 16 | Remote Data Archive |
46646 | 16 | provided |
46647 | 16 | seconds |
46648 | 16 | minutes |
46649 | 16 | hours |
46650 | 16 | days |
46651 | 16 | weeks |
46652 | 16 | months |
46653 | 16 | years |
46654 | 16 | database scoped credential |
46655 | 16 | rejected rows location |
46656 | 16 | CONNECTION_OPTIONS |
46657 | 16 | PUSHDOWN |
46658 | 16 | GENERIC |
46659 | 16 | BLOB_STORAGE |
46660 | 16 | GENERIC |
46661 | 16 | CREATE EXTERNAL TABLE |
46662 | 16 | HASH |
46663 | 16 | PARTITION |
46664 | 16 | DROP EXTERNAL TABLE |
46665 | 16 | TRUNCATE EXTERNAL TABLE |
46666 | 16 | ALTER DATABASE |
46667 | 16 | DROP DATABASE |
46701 | 16 | Query notifications is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46702 | 16 | Remote RPC requests are not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46703 | 16 | Conversion error while attempting conversion between IPC blob parameter. |
46704 | 16 | Large object column support in SQL Server Parallel DataWarehouse server is limited to only nvarchar(max) data type. |
46705 | 16 | Unsupported parameter type found while parsing RPC request. The request has been terminated. |
46706 | 16 | Cursor support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46707 | 16 | The given IPC request with code %d is not supported for SQL Server Parallel DataWarehousing TDS endpoint. |
46709 | 16 | Default parameter support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46710 | 16 | Unsupported transaction manager request %d encountered. SQL Server Parallel DataWarehousing TDS endpoint only supports local transaction request for ‘begin/commit/rollback’. |
46711 | 16 | Unsupported TDS request packet of type %d encountered on SQL Server Parallel DataWarehousing TDS endpoint. Only batch, rpc and transaction requests are supported. |
46712 | 16 | Unexpected error encountered during request processing. Connection will be terminated. |
46713 | 16 | Integrated authentication is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46716 | 16 | Attach Database File is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46717 | 16 | Login as Replication or Remote user is not supported by SQL Server Parallel DataWarehousing TDS endpoint. |
46718 | 16 | Only ‘us_english’ or ‘English’ language is supported by SQL Server Parallel DataWarehousing TDS endpoint. |
46719 | 16 | Attempt 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. |
46720 | 16 | Parallel query execution on the same connection is not supported. |
46721 | 16 | Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. |
46722 | 16 | Client driver version is not supported. |
46723 | 16 | Large object column in Global Query is not supported for types other than Nvarchar(MAX), Varchar(MAX), Varbinary(MAX) and Image. |
46724 | 16 | Communication error during bulk copy operation. |
46801 | 16 | GlobalQuery operations |
46802 | 16 | Failed to load module for global query. |
46803 | 16 | Failed to locate entry point for global query module. |
46804 | 16 | Failed to initialize the global query module. |
46805 | 16 | Conversion error while constructing the GlobalQuery request. |
46806 | 16 | An error occurred while executing GlobalQuery operation: %.*ls |
46807 | 16 | An access violation occurred while performing GlobalQuery operation. Execution has been aborted. |
46808 | 16 | An entry corresponding to given Global Query request could not be located. Execution has been aborted. |
46809 | 16 | An error occurred while attempting to execute the Global Query request. Error Code: %d, Severity: %d, State: %d. |
46810 | 16 | An unhandled exception occurred while performing GlobalQuery operation. Execution has been aborted. |
46811 | 16 | An unexpected error with code 0x%x occurred while executing GlobalQuery operation. |
46812 | 16 | %.*ls |
46813 | 16 | %.*ls |
46814 | 16 | %.*ls |
46815 | 16 | %.*ls |
46816 | 16 | %.*ls |
46817 | 16 | %.*ls |
46818 | 16 | %.*ls |
46819 | 16 | %.*ls |
46820 | 16 | %.*ls |
46821 | 16 | %.*ls |
46822 | 16 | %.*ls |
46823 | 16 | %.*ls |
46824 | 16 | %.*ls |
46825 | 16 | %.*ls |
46826 | 16 | Output parameters are not supported with %.*ls. |
46827 | 16 | The option ‘%ls’ must be turned ON to execute queries referencing external tables. |
46828 | 16 | The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint. |
46829 | 16 | The proc %.*ls is only supported for external data sources of type SHARD_MAP_MANAGER or RDBMS. |
46830 | 16 | Internal column references are not supported for external tables. |
46831 | 16 | Provided argument exceeds the current size limit of %u bytes for procedure %.*ls. |
46901 | 10 | Stored procedure finished successfully. Polybase engine service is disabled. Please restart Polybase DMS service. |
46902 | 10 | Stored procedure finished successfully. Polybase engine service is enabled. Please restart Polybase engine and DMS services. |
46903 | 10 | This stored procedure is not available because Polybase feature is not enabled. |
46904 | 16 | Failed to get the computer name. This might indicate a problem with the network configuration of the computer. Error: %ls. |
46905 | 10 | Head node cannot be removed from a Polybase computational group. |
46906 | 16 | Unable to retrieve registry value ‘%ls’ from Windows registry key ‘%ls’: %ls. |
46907 | 16 | Unable to delete registry value ‘%ls’ from Windows registry key ‘%ls’: %ls. |
46908 | 16 | Unable to update registry value ‘%ls’ in Windows registry key ‘%ls’: %ls. |
46909 | 16 | Unable to open registry key ‘%ls’: %ls. |
46910 | 16 | Incorrect number of parameters specified for procedure. |
46911 | 16 | Procedure expects parameter ‘%ls’ of type ‘%ls’. |
46912 | 16 | The option ‘%ls’ must be turned ON to execute requests referencing external tables. |
46913 | 16 | The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint. |
46914 | 16 | INSERT into external table is disabled. Turn on the configuration option ‘allow polybase export’ to enable. |
46915 | 16 | Table hints are not supported on queries that reference external tables. |
46916 | 16 | Queries 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. |
46917 | 16 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46918 | 16 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46919 | 16 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46920 | 10 | Polybase feature disabled. |
46921 | 16 | The EXECUTE AT DATA_SOURCE command is not supported for this external data source type. |
46922 | 21 | PolyBase 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. |
46923 | 16 | PolyBase feature is not installed. Please consult Books Online for more information on this feature. |
46924 | 16 | SQL failed to start PolyBase for error code 0x%lx. |
46925 | 16 | SQL failed to start PolyBase request for error code 0x%lx. |
46926 | 16 | Failed to get polybase service account due to error ‘%ls’. |
47000 | 10 | Reason: FedAuth RPS Initialization failed when fetching CLSID of RPS ProgID. |
47001 | 10 | Reason: FedAuth RPS Initialization failed when creating instance of Passport.RPS COM Object. |
47002 | 10 | Reason: FedAuth RPS Initialization failed when initializing the RPS COM object. |
47003 | 10 | Reason: FedAuth RPS Authentication failed when getting IRPSAuth object. |
47004 | 10 | Reason: FedAuth RPS Authentication failed when getting IRPSPropBag object. |
47005 | 10 | Reason: FedAuth RPS Authentication failed during IRPS::Authenticate. |
47006 | 10 | Reason: FedAuth RPS Authentication failed when getting IRPSValidatedPropertyBag object. |
47007 | 10 | Reason: FedAuth RPS Authentication failed during SetAuthPolicy. |
47008 | 10 | Reason: FedAuth RPS Authentication failed during ValidateTicketWithAuthPolicy. |
47009 | 10 | Reason: FedAuth RPS Authentication failed when fetching Session Key. |
47010 | 10 | Reason: FedAuth RPS Authentication failed when initializing HMAC Hash object. |
47011 | 10 | Reason: FedAuth RPS Authentication failed when computing HMAC Hash Signature. |
47012 | 10 | Reason: FedAuth RPS Authentication failed when comparing HMAC Hash Signature with the one sent by the client. |
47013 | 10 | Reason: FedAuth RPS Authentication failed when fetching MemberId Low. |
47014 | 10 | Reason: FedAuth RPS Authentication failed when fetching MemberId High. |
47015 | 10 | Reason: FedAuth RPS Authentication failed when fetching MemberName. |
47016 | 10 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when opening Certificate Store. |
47017 | 10 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to find ceritificate in store. |
47018 | 10 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to initialize Error object for service proxy. |
47019 | 10 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to create service proxy. |
47020 | 10 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to open service proxy. |
47021 | 10 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Heap object. |
47022 | 10 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Error object. |
47023 | 10 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during Group Membership Lookup. |
47024 | 10 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during validation of federated context. |
47025 | 10 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed due to unknown reason. |
47026 | 10 | Reason: Failure occurred when trying to fetch the HMAC signature of prelogin client nonce to set FeatureExtAck |
47027 | 10 | Reason: This was a non-Microsoft domain login attempt in a Non-SDS session. |
47028 | 10 | Reason: This FedAuth library is not supported by the security layer for authentication. |
47029 | 10 | Reason: This FedAuth Ticket type is not supported by the security layer for authentication. |
47030 | 10 | Reason: The Feature Switch for this FedAuth protocol is OFF. |
47031 | 10 | Reason: There was a failure in acquiring the max heap memory limit from config during AAD group expansion. |
47032 | 10 | Reason: 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 |
47033 | 10 | Reason: 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 |
47034 | 10 | Reason: Authentication was successful, but database is in Recovering state. |
47035 | 10 | Reason: Login failed because it was attempting to use integrated authentication, which we do not support. |
47036 | 10 | Reason: Login failed because USE db failed while checking firewall rules. |
47037 | 10 | Reason: Login failed because Deny External Connections flags is on. |
47038 | 10 | Reason: Login failed because client disconnected when fedauth specific processing was going on during login. |
47039 | 10 | Reason: Login failed because the client is attempting to use certificate authentication without correct permissions. |
47040 | 10 | Reason: Login failed because database is not found. |
47041 | 10 | Reason: Login failed because login token feature extension is not present. |
47042 | 10 | Reason: Login failed because login token feature extension is malformed. |
47043 | 10 | Reason: Token-based server access validation failed with an infrastructure error. Login is disabled. |
47044 | 10 | Reason: Login-based server access validation failed with an infrastructure error. Login is disabled. |
47045 | 10 | Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. |
47046 | 10 | Reason: Login-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. |
47047 | 10 | Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. |
47048 | 10 | Reason: Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. |
47049 | 10 | Reason: VNET Firewall Rule has rejected the login. |
47050 | 10 | Reason: Unexpected error while copying the VNET IPv6 address. |
47051 | 10 | Reason: Unexpected error while parsing the VNET IPv6. |
47052 | 10 | Reason: Unexpected error while extracting VNET metadata info from the IPv6 (VNET parsing). |
47053 | 10 | Reason: Unexpected error on VNET firewall rule table lookup. |
47054 | 10 | Reason: Unexpected error on VNET firewall rule table COUNT lookup. |
47055 | 10 | Reason: VNET Firewall rejected the login due to a the source of a login being outside a VNET |
47056 | 10 | Reason: Firewall rejected the login attempt because VNET firewall rules are not database-level, only server-level. |
47057 | 10 | Reason: Firewall rejected the login because an IPv6 attempt was received when not expected |
47058 | 10 | Reason: Unexpected error on VNET firewall rule table lookup while looking up the IPv4 Allow All rule. |
47059 | 10 | Reason: Unexpected error while swapping the session peer address with the VNET CA. |
47060 | 10 | Reason: Unexpected error on TDS readhandler, payload length > sni packet buf size |
47061 | 10 | Reason: Replicated Master is not ready at this point and user connections are disallowed. |
47062 | 10 | Reason: lock timeout expired while looking up interface endpoints list |
47063 | 10 | Reason: lock timeout expired while looking up interface endpoints list |
47064 | 10 | Reason: The incoming login VNET metadata was not found in the list of interface endpoints configured |
47065 | 10 | Reason: Unexpected error on Interface Endpoints access lockdown check |
47066 | 10 | Reason: Allow All Azure rule can’t be evaluated at DB level Firewall Rule for Interface Endpoints connections |
47067 | 10 | Reason: Internal error. Unexpected frontend connection to Vldb page server. |
47068 | 10 | fulltext stoplist |
47100 | 16 | The 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. |
47101 | 16 | The 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. |
47102 | 16 | The 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. |
47103 | 16 | The 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. |
47104 | 16 | This operation cannot be performed on the availability group ‘%.*ls’ because it has EXTERNAL cluster type. Use the cluster management tools to perform the operation. |
47105 | 16 | The 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. |
47106 | 16 | Cannot join availability group ‘%.*ls’. Download configuration timeout. Please check primary configuration, network connectivity and firewall setup, then retry the operation. |
47107 | 16 | The %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. |
47108 | 16 | The %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. |
47109 | 16 | Availability 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. |
47110 | 15 | The ‘%.*ls’ option is not valid for the ‘%.*ls’ replica as it is a configuration-only. Remove this option, then retry the operation |
47111 | 16 | Local 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. |
47112 | 16 | Only the SESSION_TIMEOUT property can be modified for a configuration-only replica. |
47113 | 16 | The ‘%.*ls’ option is not valid for the ‘%.*ls’ replica for modification. Remove this option, then retry the operation. |
47114 | 16 | Availability 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. |
47115 | 16 | The ‘%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. |
47116 | 16 | The external lease cannot be set on availability group ‘%.*ls’. External Lease updates are not enabled for this availability group. |
47117 | 16 | The ‘%ls’ option must be specified with a valid time value when updating the Availability Group’s external write lease status on availability group ‘%.*ls’. |
47118 | 16 | The ‘%ls’ option must be specified with a valid value when updating the external lease status on availability group ‘%.*ls’. |
47119 | 16 | The 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. |
47120 | 16 | The 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. |
47121 | 16 | The replica spec for the local replica ‘%.*ls’ has an invalid availability mode. Valid values are SYNCHRONOUS_COMMIT and ASYNCHRONOUS_COMMIT. |
47122 | 16 | Cannot 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. |
47123 | 16 | Creating 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. |
47124 | 16 | Creation 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. |
47125 | 16 | Joining contained availability group ‘%.*ls’ has failed. Verify there is no other availability group existed, then retry the operation. |
47126 | 16 | Joining contained availability group ‘%.*ls’ failed. Verify that user databases are not present, then retry the operation. |
47127 | 16 | Joining or creating contained availability group ‘%.*ls’ failed. The SQL Server instance is not enabled to create or join contained availability group. |
47129 | 16 | Creating 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. |
47130 | 16 | Creating 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. |
47131 | 16 | Creating or joining availability group ‘%.*ls’ failed because there is a contained availability group. Remove contained availability group, then retry the operation. |
47132 | 16 | Joining 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. |
47133 | 16 | Joining 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. |
47134 | 16 | Joining 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. |
47135 | 16 | Contained availability group system database ‘%.*ls’ cannot be removed from contained availability group ‘%.*ls’. |
47136 | 16 | Cannot 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. |
47137 | 16 | Cannot create contained system databases in contained availability group ‘%.*ls’ It might be caused by temporary condition. Retry the operation. |
47138 | 16 | Joining 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. |
47139 | 16 | Join contained availability group ‘%.*ls’ failed to create group master ‘%.*ls’ Database ID. Please retry the operation again. |
47140 | 16 | Starting contained availability group ‘%.*ls’ failed. Contained availabiity group system database ‘%.*ls’ (id = %d) failed to load during startup. |
47141 | 16 | Starting contained availability group ‘%.*ls’ failed. One of constained system databases (masterdbid = %d, msdbid = %d) failed to load during startup. |
47142 | 16 | Creating 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. |
47143 | 16 | Option ‘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. |
47145 | 16 | Failed 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. |
47201 | 16 | Procedure expects ‘%u’ parameters. |
47202 | 16 | Procedure expects ‘%u’ parameters and ‘%u’ for _ex version. |
47203 | 16 | Procedure expects at least ‘%u’ parameters and ‘%u’ max. |
49401 | 16 | Database backup not supported on this database as it has foreign files attached. |
49402 | 16 | Failed to initialize the covering resilient buffer pool extension for foreign file ‘%.*ls’ with HRESULT 0x%x. |
49403 | 17 | Database ‘%.*ls’ does not allow autostart operations. An explicit ONLINE database operation is required. |
49404 | 16 | Value ‘%.*ls’ for option ‘%.*ls’ is not supported in this version of SQL Server. |
49405 | 17 | Skipping 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. |
49406 | 16 | Recovery modes other than full are not supported in this version of SQL Server. |
49407 | 16 | Error: %ls. |
49408 | 16 | Error: %ls. Error code: %d. |
49409 | 16 | Special procedure is not available on the current SQL instance. |
49410 | 16 | Change tracking is currently not supported in this version of SQL Server. |
49411 | 16 | Couldn’t register the database in the page server database map. |
49501 | 16 | DBCC SHRINKFILE for %.*ls is aborted. Sbs flat files are not supported |
49502 | 10 | %.*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. |
49503 | 10 | %.*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. |
49504 | 10 | Error updating failover proc. |
49505 | 16 | Registering extended stored procedure failed because it is not valid to use UNC path for DLL name. Use local path for DLL name instead. |
49506 | 16 | The 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. |
49507 | 16 | Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row is aborted. |
49508 | 16 | DBCC SHRINKFILE for data files is not supported in this version of SQL Server. |
49509 | 16 | DBCC SHRINKFILE for PMM files is not supported in this version of SQL Server. |
49510 | 16 | Managed instance is busy with another operation. Please try your operation later. |
49511 | 10 | Unable to set one or more trace flags. Unsupported trace flag(s): %ls%ls%ls. |
49512 | 10 | Session level trace flags are not supported on managed instance. |
49513 | 10 | %lsDBCC %ls for databese id %d terminated abnormally due to error state %d. Elapsed time: %d hours %d minutes %d seconds. %.*ls |
49514 | 10 | %lsDBCC %ls for databese id %d found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls |
49600 | 22 | SQL tiered storage table schema is corrupt. |
49602 | 16 | Failure waiting for %ls latch in ‘%ls’. |
49603 | 16 | CREATE FILE encountered operating system error %ls while attempting to copy the physical file ‘%.*ls’. |
49701 | 10 | Server override on the category is not supported yet (Server: ‘%.*ls’, Category: ‘%.*ls’). |
49702 | 10 | The category name is either invalid or not supported yet. Server: ‘%.*ls’. CategoryName: ‘%.*ls’. |
49703 | 10 | Failed to parse server override on server ‘%.*ls’. The category name is: ‘%.*ls’ and the override string is: ‘%.*ls’. |
49704 | 10 | Failed to apply server override on category ‘%.*ls’, because physical db or instance ‘%.*ls’ in server ‘%.*ls’ is currently not in ‘Ready’ or ‘Deactivated’ state. |
49705 | 10 | Failed to merge server override into property bag on physical db or instance ‘%.*ls’ of server ‘%.*ls’. The override string is: ‘%.*ls’. |
49716 | 10 | Database override on the category is not supported yet (Server: ‘%.*ls’, Database: ‘%.*ls’, Category: ‘%.*ls’). |
49717 | 10 | Failed to apply database override on category ‘%.*ls’, because physical db or instance ‘%.*ls’ in server ‘%.*ls’ is currently not in ‘Ready’ or ‘Deactivated’ state. |
49718 | 10 | The category name is either invalid or not supported yet. Server: ‘%.*ls’. Database: ‘%.*ls’. CategoryName: ‘%.*ls’. |
49801 | 10 | Dynamic Deactivation Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details. |
49802 | 10 | Database is unavailable at the moment, please retry connection at later time. |
49803 | 10 | Resource Pool Data Space Usage Timer task encountered an error (SQL Error Code: %d). |
49804 | 10 | Database cannot be deactivated: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49805 | 10 | DynamicActivation feature switch is off for Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49806 | 10 | DynamicActivation feature switch is not enabled for all remote storage DB: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49807 | 10 | DynamicActivation is only supported for remote storage DB: Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49808 | 10 | Deactivated database cannot be deactivated again: Server ‘%.*ls’, Database ‘%.*ls’ |
49809 | 10 | Database Operation failed for Server ‘%.*ls’, Database ‘%.*ls’ due to unexpected delay. Please try again. |
49810 | 10 | Workflow failed due to throttling: Server ‘%.*ls’, Database ‘%.*ls’ |
49811 | 10 | Deactivation is not supported on Disabled database: Server ‘%.*ls’, Database ‘%.*ls’ |
49812 | 10 | EnableForceNoBackupDeactivation is not enabled: Server ‘%.*ls’, Database ‘%.*ls’ |
49813 | 10 | Deactivation is not supported on databases part of servers in global transaction partnership: Server ‘%.*ls’, Database ‘%.*ls’ |
49814 | 10 | DynamicActivation is not supported for GeoDR DB: Logical Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49815 | 10 | Database cannot be deactivated: Server ‘%.*ls’, Database ‘%.*ls’, ServiceLevelObjective ‘%.*ls’ |
49816 | 10 | Server ‘%.*ls’, Database ‘%.*ls’ cannot be online as BlockingMode is set |
49817 | 10 | Failed to query CMS for thottling on database ‘%.*ls’, ‘%.*ls’ due to the exception: ‘%.*ls’ |
49818 | 10 | Cannot deactivate a database when it is already getting deactivated, Server ‘%.*ls’, Database ‘%.*ls’ |
49819 | 10 | Deflation Monitor Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details. |
49820 | 10 | Managed Server Resource Stats Timer task encountered an error (SQL Error Code: %d). |
49821 | 10 | Rg Metrics Reporting Timer task encountered an error (SQL Error Code: %d). |
49822 | 10 | Move Cost Calculation and Reporting Timer task encountered an error (SQL Error Code: %d). |
49901 | 10 | The 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’. |
49902 | 10 | There 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’. |
49903 | 10 | Detected %I64d MB of RAM. This is an informational message; no user action is required. |
49904 | 10 | The service account is ‘%.*ls’. This is an informational message; no user action is required. |
49905 | 10 | Error %u occurred while opening parameters file ‘%s’. Verify that the file exists, and if it exists, verify that it is a valid parameters file. |
49906 | 10 | Error %u occurred while processing parameters from either the registry or the command prompt. Verify your parameters. |
49907 | 10 | Ignored deprecated SQL Server startup parameters from the registry: %.*ls |
49908 | 10 | The following SQL Server startup parameters are either deprecated or incorrectly specified: %.*ls |
49909 | 10 | Multiple 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. |
49910 | 10 | Software Usage Metrics is disabled. |
49911 | 10 | Software Usage Metrics failed to start. |
49912 | 10 | Software Usage Metrics is enabled. |
49913 | 10 | The server could not load DCOM. Software Usage Metrics cannot be started without DCOM. |
49914 | 10 | %ls Trace: %ls |
49915 | 10 | Invalid, 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. |
49916 | 10 | UTC adjustment: %d:%02u |
49917 | 10 | Default collation: %ls (%ls %u) |
49918 | 16 | Cannot process request. Not enough resources to process request. Please retry your request later. |
49919 | 16 | Cannot 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. |
49920 | 16 | Cannot 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. |
49921 | 10 | Total Log Writer threads: %ld. This is an informational message; no user action is required. |
49922 | 16 | Unable to process ‘%s’ notification for subscription ‘%ld’ because it contains ‘%d’ child resources |
49924 | 16 | Subscription ‘%ld’ does not support creating a database with selected service level objective ‘%ls’. Try creating a database with different service level objective. |
49925 | 16 | Databases cannot be updated to free service level objective. |
49926 | 10 | Server setup is starting |
49927 | 10 | An error occurred while setting the server administrator (SA) password: error %d, severity %d, state %d. |
49928 | 10 | An error occurred during server setup. See previous errors for more information. |
49929 | 10 | Server setup completed successfully. |
49930 | 10 | Parallel redo is %ls for database ‘%.*ls’ with worker pool size [%d]. |
49931 | 10 | An error occurred while configuring engine telemetry: error %d, severity %d, state %d. |
49932 | 10 | An error occurred while initializing security. %ls. |
49933 | 10 | ERROR: The MSSQL_SA_PASSWORD environment variable must be set when using the –reset-sa-password option. |
49934 | 10 | Error %u occurred while reading the RbIo configuration parameters. Verify that the sqlservr.ini or registry entries exist. |
49935 | 10 | Enclave of type %d initialized successfully. |
49936 | 10 | ERROR: The provided PID [%s] is invalid. The PID must be in the form #####-#####-#####-#####-##### where ‘#’ is a number or letter. |
49937 | 10 | ERROR: A failure occurred in the licensing subsystem. Error [%d]. |
49938 | 10 | The licensing PID was successfully processed. The new edition is [%s]. |
49939 | 16 | Unable to initialize user-specified certificate configuration. The server is being shut down. Verify that the certificate is correctly configured. Error[%d]. State[%d]. |
49940 | 16 | Unable 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. |
49941 | 16 | Unable to load one or more of the user-specified certificate file(s). Verify that the certificate file(s) are of a supported format. |
49942 | 16 | Internal error occurred initializing user-specified certificate configuration. Error code [%08X]. |
49943 | 10 | The certificate [Certificate File:’%hs’, Private Key File:’%hs’] was successfully loaded for encryption. |
49944 | 16 | The 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. |
49945 | 16 | The allowed TLS cipher list [‘%hs’] is invalid. See docs.microsoft.com for more information on creating a cipher list. |
49946 | 16 | Internal error occurred initializing the TLS configuration. Error code [%d]. |
49947 | 16 | Unable 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]. |
49948 | 10 | Successfully initialized the TLS configuration. Allowed TLS protocol versions are [‘%hs’]. Allowed TLS ciphers are [‘%hs’]. |
49949 | 10 | ERROR: Unable to set system administrator password: %s. |
49950 | 10 | The SQL Server End-User License Agreement (EULA) must be accepted before SQL |
49951 | 10 | Server can start. The license terms for this product can be downloaded from |
49952 | 10 | http://go.microsoft.com/fwlink/?LinkId=746388. |
49953 | 10 | You can accept the EULA by specifying the –accept-eula command line option, |
49954 | 10 | setting the ACCEPT_EULA environment variable, or using the mssql-conf tool. |
49955 | 10 | Environment Variable Startup Parameters:%.*ls |
49956 | 10 | The default language (LCID %d) has been set for engine and full-text services. |
49957 | 10 | The default language (LCID %d) failed to be set for engine and full-text services. |
49958 | 21 | The server collation cannot be changed with user databases attached. Please detach user databases before changing server collation. |
49959 | 10 | ERROR: The environment variable MSSQL_COLLATION contains an invalid collation ‘%.*ls’. |
49960 | 10 | Did 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. |
49961 | 10 | Setup step is %scopying system data file ‘%s’ to ‘%s’. |
49962 | 10 | ERROR: Setup FAILED copying system data file ‘%s’ to ‘%s’: %s |
49963 | 10 | ERROR: ‘%s’ is a directory. Cannot continue. |
49964 | 10 | ERROR: Setup failed to create the system data directory ‘%s’: %s |
49965 | 10 | Unable to load cluster root CA certificate due to OSError:’%s’. |
49972 | 16 | Cannot add tempdb remote file to local tempdb filegroup in transition to primary. |
49973 | 16 | Cannot remove tempdb remote file to local tempdb filegroup in transition to primary. |
49975 | 10 | Unable to load controller client certificate due to OSError:’%s’. |