SQL Server System Errors: 46000 - 49999
List of error messages between 46000 and 49999 in SQL Server 2017.
These error messages are all available by querying the sys.messages
catalog view on the master
database.
message_id | severity | is_event_logged | text |
---|---|---|---|
46501 | 15 | 0 | External table references '%S_MSG' that does not exist. |
46502 | 15 | 0 | Type with name '%.*ls' already exists. |
46503 | 15 | 0 | Invalid format for option '%S_MSG'. |
46504 | 15 | 0 | External option '%S_MSG' is not valid. Ensure that the length and range are appropriate. |
46505 | 15 | 0 | Missing required external DDL option '%S_MSG'. |
46506 | 15 | 0 | Invalid set of options specified for '%S_MSG'. |
46507 | 15 | 0 | Cannot perform DML on external tables. |
46508 | 15 | 0 | Incorrect syntax on external DDL option '%S_MSG'. |
46509 | 15 | 0 | FILE_FORMAT must be specified for HADOOP data source. |
46510 | 15 | 0 | FILE_FORMAT cannot be specified for RDBMS data source. |
46511 | 15 | 0 | EXTERNAL %S_MSG with id %d cannot be found. |
46512 | 15 | 0 | %S_MSG cannot be used with %S_MSG data source. |
46513 | 15 | 0 | A sharding column name must be provided when using SHARDED distribution. |
46514 | 15 | 0 | DISTRIBUTION must be specified when using a SHARD_MAP_MANGER data source. |
46515 | 15 | 0 | The specified sharding column name does not match any column in the external table definition. |
46516 | 15 | 0 | The specified credential cannot be found or the user does not have permission to perform this action. |
46517 | 17 | 0 | XML Parse error when de-serializing PDW Metadata. |
46518 | 15 | 0 | The %S_MSG '%ls' is not supported with %S_MSG. |
46519 | 15 | 0 | %ls are not supported with %S_MSG. |
46520 | 15 | 0 | The external DDL statement contained an unrecognized option. |
46521 | 15 | 0 | 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 | 0 | Failed to update '%S_MSG'. |
46523 | 15 | 0 | A SCHEMA_NAME must be specified when using OBJECT_NAME. |
46524 | 15 | 0 | An OBJECT_NAME must be specified when using SCHEMA_NAME. |
46525 | 15 | 0 | External tables are not supported with the %S_MSG data source type. |
46526 | 15 | 0 | The %S_MSG operation is not supported with %S_MSG data source type. |
46527 | 15 | 0 | Altering the '%S_MSG' property is not permitted for an external data source of type %ls. |
46601 | 16 | 0 | REJECT_TYPE |
46602 | 16 | 0 | FILE_FORMAT |
46603 | 16 | 0 | REJECT_VALUE |
46604 | 16 | 0 | REJECT_SAMPLE_VALUE |
46605 | 16 | 0 | LOCATION |
46606 | 16 | 0 | DATA_SOURCE |
46607 | 16 | 0 | PERCENTAGE |
46608 | 16 | 0 | ROW_TERMINATOR |
46609 | 16 | 0 | DATA_COMPRESSION |
46610 | 16 | 0 | SERDE_METHOD |
46611 | 16 | 0 | ENCODING |
46612 | 16 | 0 | STRING_DELIMITER |
46613 | 16 | 0 | DATE_FORMAT |
46614 | 16 | 0 | FIELD_TERMINATOR |
46615 | 16 | 0 | FORMAT_TYPE |
46616 | 16 | 0 | JOB_TRACKER_LOCATION |
46617 | 16 | 0 | EXTERNAL TABLE |
46618 | 16 | 0 | HADOOP |
46619 | 16 | 0 | RDBMS |
46620 | 16 | 0 | SHARD_MAP_MANGER |
46621 | 16 | 0 | SHARDING_COLUMN_NAME |
46622 | 16 | 0 | DISTRIBUTION |
46623 | 16 | 0 | DATABASE_NAME |
46624 | 16 | 0 | SHARD_MAP_NAME |
46625 | 16 | 0 | CREDENTIAL |
46626 | 16 | 0 | REMOTE_SCHEMA_NAME |
46627 | 16 | 0 | REMOTE_OBJECT_NAME |
46628 | 16 | 0 | SHARED_MEMORY |
46643 | 16 | 0 | external tables |
46644 | 16 | 0 | external tables for sharded data |
46645 | 16 | 0 | Remote Data Archive |
46646 | 16 | 0 | provided |
46647 | 16 | 0 | seconds |
46648 | 16 | 0 | minutes |
46649 | 16 | 0 | hours |
46650 | 16 | 0 | days |
46651 | 16 | 0 | weeks |
46652 | 16 | 0 | months |
46653 | 16 | 0 | years |
46654 | 16 | 0 | database scoped credential |
46701 | 16 | 0 | Query notifications is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46702 | 16 | 0 | Remote RPC requests are not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46703 | 16 | 0 | Conversion error while attempting conversion between IPC blob parameter. |
46704 | 16 | 0 | Large object column support in SQL Server Parallel DataWarehouse server is limited to only nvarchar(max) data type. |
46705 | 16 | 0 | Unsupported parameter type found while parsing RPC request. The request has been terminated. |
46706 | 16 | 0 | Cursor support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46707 | 16 | 0 | The given IPC request with code %d is not supported for SQL Server Parallel DataWarehousing TDS endpoint. |
46709 | 16 | 0 | Default parameter support is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46710 | 16 | 0 | Unsupported transaction manager request %d encountered. SQL Server Parallel DataWarehousing TDS endpoint only supports local transaction request for 'begin/commit/rollback'. |
46711 | 16 | 0 | 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 | 0 | Unexpected error encountered during request processing. Connection will be terminated. |
46713 | 16 | 0 | Integrated authentication is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46716 | 16 | 0 | Attach Database File is not an implemented feature for SQL Server Parallel DataWarehousing TDS endpoint. |
46717 | 16 | 0 | Login as Replication or Remote user is not supported by SQL Server Parallel DataWarehousing TDS endpoint. |
46718 | 16 | 0 | Only 'us_english' or 'English' language is supported by SQL Server Parallel DataWarehousing TDS endpoint. |
46719 | 16 | 0 | 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 | 0 | Parallel query execution on the same connection is not supported. |
46721 | 16 | 0 | Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. |
46722 | 16 | 0 | Client driver version is not supported. |
46723 | 16 | 0 | Large object column in Global Query is not supported for types other than Nvarchar(MAX), Varchar(MAX), Varbinary(MAX) and Image. |
46801 | 16 | 0 | GlobalQuery operations |
46802 | 16 | 0 | Failed to load module for global query. |
46803 | 16 | 0 | Failed to locate entry point for global query module. |
46804 | 16 | 0 | Failed to initialize the global query module. |
46805 | 16 | 0 | Conversion error while constructing the GlobalQuery request. |
46806 | 16 | 0 | An error occurred while executing GlobalQuery operation: %.*ls |
46807 | 16 | 0 | An access violation occurred while performing GlobalQuery operation. Execution has been aborted. |
46808 | 16 | 0 | An entry corresponding to given Global Query request could not be located. Execution has been aborted. |
46809 | 16 | 0 | An error occurred while attempting to execute the Global Query request. Error Code: %d, Severity: %d, State: %d. |
46810 | 16 | 0 | An unhandled exception occurred while performing GlobalQuery operation. Execution has been aborted. |
46811 | 16 | 0 | An unexpected error with code 0x%x occurred while executing GlobalQuery operation. |
46812 | 16 | 0 | %.*ls |
46813 | 16 | 0 | %.*ls |
46814 | 16 | 0 | %.*ls |
46815 | 16 | 0 | %.*ls |
46816 | 16 | 0 | %.*ls |
46817 | 16 | 0 | %.*ls |
46818 | 16 | 0 | %.*ls |
46819 | 16 | 0 | %.*ls |
46820 | 16 | 0 | %.*ls |
46821 | 16 | 0 | %.*ls |
46822 | 16 | 0 | %.*ls |
46823 | 16 | 0 | %.*ls |
46824 | 16 | 0 | %.*ls |
46825 | 16 | 0 | %.*ls |
46826 | 16 | 0 | Output parameters are not supported with %.*ls. |
46827 | 16 | 0 | The option '%ls' must be turned ON to execute queries referencing external tables. |
46828 | 16 | 0 | The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint. |
46829 | 16 | 0 | The proc %.*ls is only supported for external data sources of type SHARD_MAP_MANAGER or RDBMS. |
46830 | 16 | 0 | Internal column references are not supported for external tables. |
46901 | 10 | 0 | Stored procedure finished successfully. Polybase engine service is disabled. Please restart Polybase DMS service. |
46902 | 10 | 0 | Stored procedure finished successfully. Polybase engine service is enabled. Please restart Polybase engine and DMS services. |
46903 | 10 | 0 | This stored procedure is not available because Polybase feature is not enabled. |
46904 | 16 | 0 | Failed to get the computer name. This might indicate a problem with the network configuration of the computer. Error: %ls. |
46905 | 10 | 0 | Head node cannot be removed from a Polybase computational group. |
46906 | 16 | 0 | Unable to retrieve registry value '%ls' from Windows registry key '%ls': %ls. |
46907 | 16 | 0 | Unable to delete registry value '%ls' from Windows registry key '%ls': %ls. |
46908 | 16 | 0 | Unable to update registry value '%ls' in Windows registry key '%ls': %ls. |
46909 | 16 | 0 | Unable to open registry key '%ls': %ls. |
46910 | 16 | 0 | Incorrect number of parameters specified for procedure. |
46911 | 16 | 0 | Procedure expects parameter '%ls' of type '%ls'. |
46912 | 16 | 0 | The option '%ls' must be turned ON to execute requests referencing external tables. |
46913 | 16 | 0 | The USE PLAN hint is not supported for queries that reference external tables. Consider removing USE PLAN hint. |
46914 | 16 | 0 | INSERT into external table is disabled. Turn on the configuration option 'allow polybase export' to enable. |
46915 | 16 | 0 | Table hints are not supported on queries that reference external tables. |
46916 | 16 | 0 | 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 | 0 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46918 | 16 | 0 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46919 | 16 | 0 | An internal error occured while attempting to retrieve the encrypted database-scoped credential secret. |
46920 | 10 | 0 | Polybase feature disabled. |
47000 | 10 | 0 | Reason: FedAuth RPS Initialization failed when fetching CLSID of RPS ProgID. |
47001 | 10 | 0 | Reason: FedAuth RPS Initialization failed when creating instance of Passport.RPS COM Object. |
47002 | 10 | 0 | Reason: FedAuth RPS Initialization failed when initializing the RPS COM object. |
47003 | 10 | 0 | Reason: FedAuth RPS Authentication failed when getting IRPSAuth object. |
47004 | 10 | 0 | Reason: FedAuth RPS Authentication failed when getting IRPSPropBag object. |
47005 | 10 | 0 | Reason: FedAuth RPS Authentication failed during IRPS::Authenticate. |
47006 | 10 | 0 | Reason: FedAuth RPS Authentication failed when getting IRPSValidatedPropertyBag object. |
47007 | 10 | 0 | Reason: FedAuth RPS Authentication failed during SetAuthPolicy. |
47008 | 10 | 0 | Reason: FedAuth RPS Authentication failed during ValidateTicketWithAuthPolicy. |
47009 | 10 | 0 | Reason: FedAuth RPS Authentication failed when fetching Session Key. |
47010 | 10 | 0 | Reason: FedAuth RPS Authentication failed when initializing HMAC Hash object. |
47011 | 10 | 0 | Reason: FedAuth RPS Authentication failed when computing HMAC Hash Signature. |
47012 | 10 | 0 | Reason: FedAuth RPS Authentication failed when comparing HMAC Hash Signature with the one sent by the client. |
47013 | 10 | 0 | Reason: FedAuth RPS Authentication failed when fetching MemberId Low. |
47014 | 10 | 0 | Reason: FedAuth RPS Authentication failed when fetching MemberId High. |
47015 | 10 | 0 | Reason: FedAuth RPS Authentication failed when fetching MemberName. |
47016 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when opening Certificate Store. |
47017 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to find ceritificate in store. |
47018 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to initialize Error object for service proxy. |
47019 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to create service proxy. |
47020 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Initialization failed when trying to open service proxy. |
47021 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Heap object. |
47022 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed when trying to initialize Error object. |
47023 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during Group Membership Lookup. |
47024 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed during validation of federated context. |
47025 | 10 | 0 | Reason: FedAuth AzureActiveDirectoryService Group Expansion failed due to unknown reason. |
47026 | 10 | 0 | Reason: Failure occurred when trying to fetch the HMAC signature of prelogin client nonce to set FeatureExtAck |
47027 | 10 | 0 | Reason: This was a non-Microsoft domain login attempt in a Non-SDS session. |
47028 | 10 | 0 | Reason: This FedAuth library is not supported by the security layer for authentication. |
47029 | 10 | 0 | Reason: This FedAuth Ticket type is not supported by the security layer for authentication. |
47030 | 10 | 0 | Reason: The Feature Switch for this FedAuth protocol is OFF. |
47031 | 10 | 0 | Reason: There was a failure in acquiring the max heap memory limit from config during AAD group expansion. |
47032 | 10 | 0 | 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 eroor code |
47033 | 10 | 0 | 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 eroor code |
47034 | 10 | 0 | Reason: Authentication was successful, but database is in Recovering state. |
47035 | 10 | 0 | Reason: Login failed because it was attempting to use integrated authentication, which we do not support. |
47036 | 10 | 0 | Reason: Login failed because USE db failed while checking firewall rules. |
47037 | 10 | 0 | Reason: Login failed because Deny External Connections flags is on. |
47038 | 10 | 0 | Reason: Login failed because client disconnected when fedauth specific processing was going on during login. |
47039 | 10 | 0 | Reason: Login failed because the client is attempting to use certificate authentication without correct permissions. |
47040 | 10 | 0 | Reason: Login failed because database is not found. |
47041 | 10 | 0 | Reason: Login failed because login token feature extension is not present. |
47042 | 10 | 0 | Reason: Login failed because login token feature extension is malformed. |
47043 | 10 | 0 | Reason: Token-based server access validation failed with an infrastructure error. Login is disabled. |
47044 | 10 | 0 | Reason: Login-based server access validation failed with an infrastructure error. Login is disabled. |
47045 | 10 | 0 | Reason: Token-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. |
47046 | 10 | 0 | Reason: Login-based server access validation failed with an infrastructure error. Login lacks Connect SQL permission. |
47047 | 10 | 0 | Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. |
47048 | 10 | 0 | Reason: Login-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. |
47049 | 10 | 0 | Reason: VNET Firewall Rule has rejected the login. |
47050 | 10 | 0 | Reason: Unexpected error while copying the VNET IPv6 address. |
47051 | 10 | 0 | Reason: Unexpected error while parsing the VNET IPv6. |
47052 | 10 | 0 | Reason: Unexpected error while extracting VNET metadata info from the IPv6 (VNET parsing). |
47053 | 10 | 0 | Reason: Unexpected error on VNET firewall rule table lookup. |
47054 | 10 | 0 | Reason: Unexpected error on VNET firewall rule table COUNT lookup. |
47055 | 10 | 0 | Reason: VNET Firewall rejected the login due to a the source of a login being outside a VNET |
47056 | 10 | 0 | Reason: Firewall rejected the login attempt because VNET firewall rules are not database-level, only server-level. |
47057 | 10 | 0 | Reason: Firewall rejected the login because an IPv6 attempt was received when not expected |
47058 | 10 | 0 | Reason: Unexpected error on VNET firewall rule table lookup while looking up the IPv4 Allow All rule. |
47100 | 16 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | Cannot join availability group '%.*ls'. Download configuration timeout. Please check primary configuration, network connectivity and firewall setup, then retry the operation. |
47107 | 16 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | Configuration-only replica for availability group '%.*ls' cannot be modified. This replica is a configuration-only and only can be added or removed. |
47113 | 16 | 0 | The '%.*ls' option is not valid for the '%.*ls' replica for modification. Remove this option, then retry the operation. |
47114 | 16 | 0 | Availability replica '%.*ls' cannot be added to availability group '%.*ls'. Configuration-only Replica canot added into WSFC cluster type AG. Verify that the AVAILABILITY_MODE setting is correct, then retry the operation. |
49401 | 16 | 1 | Database backup not supported on this database as it has foreign files attached. |
49501 | 16 | 0 | DBCC SHRINKFILE for %.*ls is aborted. Sbs flat files are not supported |
49502 | 10 | 0 | %.*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. |
49600 | 22 | 0 | SQL tiered storage table schema is corrupt. |
49601 | 16 | 0 | SBS Flat File Access not fully initialized, when function '%ls' was called. |
49602 | 16 | 0 | Failure waiting for %ls latch in '%ls'. |
49701 | 10 | 0 | Server override on the category is not supported yet (Server: '%.*ls', Category: '%.*ls'). |
49702 | 10 | 0 | The category name is either invalid or not supported yet. Server: '%.*ls'. CategoryName: '%.*ls'. |
49703 | 10 | 0 | Failed to parse server override on server '%.*ls'. The category name is: '%.*ls' and the override string is: '%.*ls'. |
49704 | 10 | 0 | 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 | 0 | Failed to merge server override into property bag on physical db or instance '%.*ls' of server '%.*ls'. The override string is: '%.*ls'. |
49801 | 10 | 0 | Dynamic Deactivation Timer task encountered an error (SQL Error Code: %d). Refer to the xel for more details. |
49802 | 10 | 0 | Database is unavailable at the moment, please retry connection at later time. |
49803 | 10 | 0 | Resource Pool Data Space Usage Timer task encountered an error (SQL Error Code: %d). |
49804 | 10 | 0 | Database cannot be deactivated: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49805 | 10 | 0 | DynamicActivation feature switch is off for Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49806 | 10 | 0 | DynamicActivation feature switch is not enabled for all remote storage DB: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49807 | 10 | 0 | DynamicActivation is only supported for remote storage DB: Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49808 | 10 | 0 | Deactivated database cannot be deactivated again: Server '%.*ls', Database '%.*ls' |
49809 | 10 | 0 | Database Operation failed for Server '%.*ls', Database '%.*ls' due to unexpected delay. Please try again. |
49810 | 10 | 0 | Workflow failed due to throttling: Server '%.*ls', Database '%.*ls' |
49811 | 10 | 0 | Deactivation is not supported on Disabled database: Server '%.*ls', Database '%.*ls' |
49812 | 10 | 0 | EnableForceNoBackupDeactivation is not enabled: Server '%.*ls', Database '%.*ls' |
49813 | 10 | 0 | Deactivation is not supported on databases part of servers in global transaction partnership: Server '%.*ls', Database '%.*ls' |
49814 | 10 | 0 | DynamicActivation is not supported for GeoDR DB: Logical Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49815 | 10 | 0 | Database cannot be deactivated: Server '%.*ls', Database '%.*ls', ServiceLevelObjective '%.*ls' |
49816 | 10 | 0 | Server '%.*ls', Database '%.*ls' cannot be online as BlockingMode is set |
49817 | 10 | 0 | Failed to query CMS for thottling on database '%.*ls', '%.*ls' due to the exception: '%.*ls' |
49818 | 10 | 0 | Cannot deactivate a database when it is already getting deactivated, Server '%.*ls', Database '%.*ls' |
49819 | 10 | 0 | Deflation Monitor Timer task encountered an error (SQL Error Code: %d).tRefer to the xel for more details.t |
49901 | 10 | 0 | 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 | 0 | 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 | 1 | Detected %I64d MB of RAM. This is an informational message; no user action is required. |
49904 | 10 | 1 | The service account is '%.*ls'. This is an informational message; no user action is required. |
49905 | 10 | 1 | 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 | 1 | Error %u occurred while processing parameters from either the registry or the command prompt. Verify your parameters. |
49907 | 10 | 1 | Ignored deprecated SQL Server startup parameters from the registry: %.*ls |
49908 | 10 | 1 | The following SQL Server startup parameters are either deprecated or incorrectly specified: %.*ls |
49909 | 10 | 1 | 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 | 0 | Software Usage Metrics is disabled. |
49911 | 10 | 0 | Software Usage Metrics failed to start. |
49912 | 10 | 0 | Software Usage Metrics is enabled. |
49913 | 10 | 0 | The server could not load DCOM. Software Usage Metrics cannot be started without DCOM. |
49914 | 10 | 0 | %ls Trace: %ls |
49915 | 10 | 1 | 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 | 1 | UTC adjustment: %d:%02u |
49917 | 10 | 1 | Default collation: %ls (%ls %u) |
49918 | 16 | 0 | Cannot process request. Not enough resources to process request. Please retry you request later. |
49919 | 16 | 0 | 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 | 0 | 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. |
49922 | 16 | 0 | Unable to process '%s' notification for subscription '%ld' because it contains '%d' child resources |
49924 | 16 | 0 | 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 | 0 | Databases cannot be updated to free service level objective. |
49926 | 10 | 0 | Server setup is starting |
49927 | 10 | 0 | An error occurred while setting the server administrator (SA) password: error %d, severity %d, state %d. |
49928 | 10 | 0 | An error occurred during server setup. See previous errors for more information. |
49929 | 10 | 0 | Server setup completed successfully. |
49930 | 10 | 1 | Parallel redo is %ls for database '%.*ls' with worker pool size [%d]. |
49931 | 10 | 0 | An error occurred while configuring engine telemetry: error %d, severity %d, state %d. |
49932 | 10 | 0 | An error occurred while initializing security. %ls. |
49933 | 10 | 0 | ERROR: The MSSQL_SA_PASSWORD environment variable must be set when using the --reset-sa-password option. |
49934 | 10 | 1 | Error %u occurred while reading the RbIo configuration parameters. Verify that the sqlservr.ini or registry entries exist. |
49936 | 10 | 0 | ERROR: The provided PID [%s] is invalid. The PID must be in the form #####-#####-#####-#####-##### where '#' is a number or letter. |
49937 | 10 | 0 | ERROR: A failure occurred in the licensing subsystem. Error [%d]. |
49938 | 10 | 0 | The licensing PID was successfully processed. The new edition is [%s]. |
49939 | 16 | 0 | 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 | 0 | 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 | 0 | 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 | 0 | Internal error occurred initializing user-specified certificate configuration. Error code [%08X]. |
49943 | 10 | 0 | The certificate [Certificate File:'%hs', Private Key File:'%hs'] was successfully loaded for encryption. |
49944 | 16 | 0 | 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 | 0 | The allowed TLS cipher list ['%hs'] is invalid. See docs.microsoft.com for more information on creating a cipher list. |
49946 | 16 | 0 | Internal error occurred initializing the TLS configuration. Error code [%d]. |
49947 | 16 | 0 | 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 | 0 | Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['%hs']. Allowed TLS ciphers are ['%hs']. |
49949 | 10 | 0 | ERROR: Unable to set system administrator password: %s. |
49950 | 10 | 0 | The SQL Server End-User License Agreement (EULA) must be accepted before SQL |
49951 | 10 | 0 | Server can start. The license terms for this product can be downloaded from |
49952 | 10 | 0 | http://go.microsoft.com/fwlink/?LinkId=746388. |
49953 | 10 | 0 | You can accept the EULA by specifying the --accept-eula command line option, |
49954 | 10 | 0 | setting the ACCEPT_EULA environment variable, or using the mssql-conf tool. |
49955 | 10 | 0 | Environment Variable Startup Parameters:%.*ls |
49956 | 10 | 0 | The default language (LCID %d) has been set for engine and full-text services. |
49957 | 10 | 0 | The default language (LCID %d) failed to be set for engine and full-text services. |
49958 | 21 | 0 | The server collation cannot be changed with user databases attached. Please detach user databases before changing server collation. |
49959 | 10 | 0 | ERROR: The environment variable MSSQL_COLLATION contains an invalid collation '%.*ls'. |
49960 | 10 | 0 | 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 | 0 | Setup step is %scopying system data file '%s' to '%s'. |
49962 | 10 | 0 | ERROR: Setup FAILED copying system data file '%s' to '%s': %s |
49963 | 10 | 0 | ERROR: '%s' is a directory. Cannot continue. |
49964 | 10 | 0 | ERROR: Setup failed to create the system data directory '%s': %s |