In this post, we’ll list out the SQL Server Error Messages from the error codes 25001 to 30000 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 25001 to 30000
ErrorCode | Severity | ErrorMessage |
25002 | 16 | The specified Publisher is not enabled as a remote Publisher at this Distributor. Ensure the value specified for the parameter @publisher is correct, and that the Publisher is enabled as a remote Publisher at the Distributor. |
25003 | 16 | Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database. |
25005 | 16 | It is invalid to drop the default constraint on the rowguid column that is used by merge replication. |
25006 | 16 | The new column cannot be added to article ‘%s’ because it has more than %d replicated columns. |
25007 | 16 | Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the changes and synchronize the data. |
25008 | 16 | The merge replication views could not be regenerated after performing the data definition language (DDL) operation. |
25009 | 16 | Invalid value ‘%s’ specified while executing sp_changemergearticle on article ‘%s’ for the ‘identityrangemanagementoption’ property. |
25010 | 16 | The constraint is used by merge replication for identity management and cannot be dropped directly. Execute sp_changemergearticle @publication, @article, “identityrangemanagementoption”, “none” to disable merge identity management, which will also drop the constraint. |
25012 | 16 | Cannot add an identity column since the table is published for merge replication. |
25013 | 16 | Cannot perform alter table because the table is published in one or more publications with a publication_compatibility_level of lower than ’90RTM’. Use sp_repladdcolumn or sp_repldropcolumn. |
25014 | 16 | sp_repladdcolumn does not allow adding columns of datatypes that are new to this release. |
25015 | 10 | Schema Changes and Bulk Inserts |
25016 | 10 | Prepare Dynamic Snapshot |
25017 | 16 | Failed to execute the command “%s” through xp_cmdshell. Detailed error information is returned in a result set. |
25018 | 16 | Precomputed partitions cannot be used because articles “%s” and “%s” are part of a join filter and at least one of them has a constraint with a CASCADE action defined. |
25019 | 16 | The logical record relationship between articles “%s” and “%s” cannot be added because at least one of the articles has a constraint with a CASCADE action defined. |
25020 | 16 | The article cannot be created on table ‘%s’ because it has more than %d columns and column-level tracking is being used. Either reduce the number of columns in the table or change to row-level tracking. |
25021 | 16 | Replication stored procedure sp_MSupdategenhistory failed to update the generation ‘%s’. This generation will be retried in the next merge. |
25022 | 16 | The snapshot storage option (@snapshot_storage_option) must be ‘file system’, or ‘database’. |
25023 | 16 | Stored procedures containing table-value parameters cannot be published as ‘[serializable] proc exec’ articles. |
25024 | 16 | A snapshot storage option of ‘database’ is incompatible with the use of character mode bcp for snapshot generation. |
25025 | 16 | Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse columns. |
25026 | 16 | The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded. |
25027 | 16 | Cannot find a credential for Windows login ‘%s’. Replication agent job sync needs a credential to be pre-created in all availability group replicas for each required Windows logins. |
25028 | 16 | Cannot specify ‘database_name’ when ‘all’ is set to 1. |
25029 | 16 | Replication distribution database ‘%s’ is not in the primary replica of its availability group. |
25030 | 16 | Replication distribution database ‘%s’ is not in an availability group. |
25031 | 10 | Monitor and sync replication agent jobs |
25032 | 10 | Sync replication agent jobs and their enabled states. |
25033 | 16 | The distribution database is part of an availability group without a listener. Add a listener to the availability group before adding publication, subscription or distribution. |
25034 | 16 | Distribution database in availability group is only supported for publisher_type as MSSQLSERVER. |
25035 | 16 | When distribution database is part of availability group, then distributor and publisher server cannot be same. |
25036 | 16 | Distribution database needs to be in readable state on secondary replica, when distribution database is part of availability group. |
25037 | 16 | The @subscriber parameter must be either @@SERVERNAME or listener name of the availability group that the subscriber database is part of. |
25038 | 16 | User needs to have VIEW SERVER STATE permission to assign @subscriber as the listener name of the availability group. |
25039 | 16 | Assigning listener name for @subscriber parameter is not a supported scenario for Managed Instance. |
25040 | 16 | Assigning the default value to “%ls”: %ls. |
25601 | 17 | The Extended Event engine is out of memory. |
25602 | 17 | The %S_MSG, “%.*ls”, encountered a configuration error during initialization. Object cannot be added to the event session. %ls |
25603 | 17 | The %S_MSG, “%.*ls”, could not be added. The maximum number of singleton targets has been reached. |
25604 | 17 | The Extended Event engine is disabled. |
25605 | 17 | The %S_MSG, “%.*ls”, could not be added. The maximum number of packages has been reached. |
25606 | 17 | The Extended Event engine could not be initialized. Check the SQL Server error log and the operating system error log for information about possible related problems. |
25607 | 17 | The Extended Event engine has been disabled by startup options. Features that depend on Extended Events may fail to start. |
25608 | 17 | The Extended Event engine could not allocate record for local thread/fiber. |
25623 | 16 | The %S_MSG name, “%.*ls”, is invalid, or the object could not be found |
25624 | 16 | The constraints of %S_MSG name, “%.*ls”, have been violated. The object does not support binding to actions or predicates. Event not added to event session. |
25625 | 16 | The %S_MSG, “%.*ls”, already exists in the event session. Object cannot be added to the event session. |
25626 | 16 | The %S_MSG, “%.*ls”, was specified multiple times. |
25629 | 16 | For %S_MSG, “%.*ls”, the customizable attribute, “%ls”, does not exist. |
25630 | 16 | The predicate expression bound to %S_MSG ,”%.*ls”, has mismatching types. |
25631 | 16 | The %S_MSG, “%.*ls”, already exists. Choose a unique name for the event session. |
25632 | 16 | The specified buffer size is less than the minimum size. The minimum allowed size is %d bytes. |
25633 | 16 | The buffer size specified exceeds the maximum size. |
25634 | 16 | The dispatch latency specified is below the minimum size. |
25635 | 16 | An attempt was made to add an asynchronous target to a session with a maximum memory of 0. For asynchronous targets to be added to a session, the session must have a maximum memory greater than 0. |
25636 | 16 | Source and comparator types of the predicate do not match. |
25639 | 16 | The %S_MSG, “%.*ls”, exceeds the number of allowable bound actions. |
25640 | 16 | Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0. |
25641 | 16 | For %S_MSG, “%.*ls”, the parameter “%ls” passed is invalid. %ls |
25642 | 16 | Mandatory customizable attributes are missing for %S_MSG, “%.*ls”. |
25643 | 16 | The %S_MSG, “%.*ls”, can not be added to an event session that specifies no event loss. |
25644 | 16 | The %S_MSG, “%.*ls”, cannot be bound to the event session. |
25646 | 16 | The %S_MSG name, “%.*ls”, is invalid. |
25647 | 16 | The %S_MSG, “%.*ls”, could not be found. Ensure that the object exists and the name is spelled correctly. |
25648 | 16 | The %S_MSG, “%.*ls”, could not be found. Ensure that the package exists and the name is spelled correctly. |
25649 | 16 | Two of the actions/predicates for %S_MSG, “%.*ls”, can not coexist. Please remove one. |
25650 | 16 | For %S_MSG, “%.*ls” the customizable attribute, “%ls”, was specified multiple times. |
25651 | 16 | For %S_MSG, “%.*ls”, the value specified for customizable attribute, “%ls”, did not match the expected type, “%ls”. |
25653 | 16 | The %S_MSG, “%.*ls”, does not exist in the event session. Object cannot be dropped from the event session. |
25654 | 16 | Insuficient buffer space to copy error message. |
25655 | 16 | Internal Extended Event error: invalid message code. |
25656 | 16 | Error validating action. %ls |
25657 | 16 | Error validating predicate. %ls |
25658 | 16 | The %S_MSG name “%.*ls” is not unique. |
25659 | 17 | The %S_MSG, “%.*ls”, encountered a configuration error during initialization. The customizable attribute %ls is used internally only. |
25664 | 16 | Internal Extended Event error: invalid package ID. |
25699 | 17 | The Extended Event engine failed unexpectedly while performing an operation. |
25701 | 15 | Invalid event session name “%.*ls”. Temporary event sessions are not allowed. |
25702 | 16 | The event session option, “%.*ls”, is set more than once. Remove the duplicate session option and re-issue the statement. |
25703 | 16 | The event session option, “%.*ls”, has an invalid value. Correct the value and re-issue the statement. |
25704 | 16 | The event session has already been stopped. |
25705 | 16 | The event session has already been started. |
25706 | 16 | The %S_MSG, “%.*ls”, could not be found. |
25707 | 16 | Event session option “%.*ls” cannot be changed while the session is running. Stop the event session before changing this session option. |
25708 | 16 | The “%.*ls” specified exceeds the maximum allowed value. Specify a smaller configuration value. |
25709 | 16 | One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. |
25710 | 16 | Event session “%.*ls” failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems. |
25711 | 16 | Failed to parse an event predicate. |
25712 | 16 | An invalid comparison operator was specified for an event predicate. |
25713 | 16 | The value specified for %S_MSG, “%.*ls”, %S_MSG, “%.*ls”, is invalid. |
25715 | 16 | The predicate on event “%ls” is invalid. Operator ‘%ls’ is not defined for type “%ls”, %S_MSG: “%.*ls”. |
25716 | 16 | The predicate on event, “%.*ls”, exceeds the maximum length of %d characters. |
25717 | 16 | The operating system returned error %ls while reading from the file ‘%s’. |
25718 | 16 | The log file name “%s” is invalid. Verify that the file exists and that the SQL Server service account has access to it. |
25719 | 16 | Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query. |
25720 | 10 | ‘sys.fn_xe_file_target_read_file’ is skipping records from “%.*ls” at offset %I64d. |
25721 | 16 | The metadata file name “%s” is invalid. Verify that the file exists and that the SQL Server service account has access to it. |
25722 | 16 | The offset %I64d is invalid for log file “%s”. Specify an offset that exists in the log file and retry your query. |
25723 | 16 | An error occurred while obtaining metadata information from the file “%s”. The file may be damaged. |
25724 | 16 | Predicate too large for display. |
25725 | 16 | An error occurred while trying to flush all running Extended Event sessions. Some events may be lost. |
25726 | 17 | The event data stream was disconnected because there were too many outstanding events. To avoid this error either remove events or actions from your session or add a more restrictive predicate filter to your session. |
25727 | 16 | The Extended Events session named “%.*ls” has either been stopped or dropped and can no longer be accessed. |
25728 | 16 | The Extended Events session named “%.*ls” could not be found. Make sure the session exists and is started. |
25729 | 17 | The event data stream was disconnected due to an internal error. |
25730 | 10 | The Extended Events session named “%.*ls” was modified during the upgrade and one of the bucketizer targets was excluded from the Extended Events session. Only one bucketizer target is supported for each Extended Events session. |
25731 | 16 | Execution of event session state change request failed on remote brick. Event session name: “%.*ls”. Refer to previous errors to identify the cause, and correct any associated problems. |
25732 | 16 | One or more event sessions failed to reconcile their runtime states. Refer to previous errors in the current session to identify the cause, and correct any associated problems. |
25733 | 16 | Event session “%.*ls” failed to reconcile its runtime state. Refer to previous errors in the current session to identify the cause, and correct any associated problems. |
25734 | 16 | The file pattern “%s” represents a full path. Use only relative paths with no drive letters. |
25735 | 16 | The source option %d is invalid. |
25736 | 16 | A damaged buffer was found in file “%s” at offset %I64d, no further events will be read from the file. |
25737 | 16 | Database scoped extended event sessions are not available in server scope or system databases in Azure DB. |
25738 | 16 | Event session ‘%.*ls’ could not be started because system is currently busy. Please try again later. |
25739 | 16 | Failed to start event session ‘%.*ls’ because required credential for writing session output to Azure blob is missing. |
25740 | 16 | Unable to start event session ‘%.*ls’ because system is busy. Please try again later. |
25741 | 16 | The URL specified for %S_MSG “%.*ls”, %S_MSG “%.*ls” is invalid. URL must begin with ‘https://’ . |
25742 | 16 | Target ‘%.*ls’ is not available for Azure SQL Database. |
25743 | 16 | The event ‘%.*ls’ is not available for Azure SQL Database. |
25744 | 16 | The action ‘%.*ls’ is not available for Azure SQL Database. |
25745 | 16 | Unable to retrieve Azure SQL Database telemetry data. |
25746 | 16 | Operation failed. Operation will cause database %S_MSG memory to exceed allowed limit. Event session memory may be released by stopping active sessions or altering session memory options. Check sys.dm_xe_database_sessions for active sessions that can be stopped or altered. |
25747 | 16 | Operation failed. Operation will cause database %S_MSG memory to exceed allowed limit. Event session memory may be released by stopping active sessions or altering session memory options. Check sys.dm_xe_database_sessions for active sessions that can be stopped or altered. If no sessions are active on this database, please check sessions running on other databases under the same logical server. |
25748 | 16 | The file “%s” contains audit logs. Audit logs can only be accessed by using the fn_get_audit_file function. |
26010 | 10 | The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %#x. Check certificates to make sure they are valid. |
26011 | 16 | The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. |
26012 | 16 | The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support. |
26013 | 10 | The certificate [Cert Hash(sha1) “%hs”] was successfully loaded for encryption. |
26014 | 16 | Unable to load user-specified certificate [Cert Hash(sha1) “%hs”]. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online. |
26015 | 16 | Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online. |
26017 | 10 | Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. |
26018 | 10 | A self-generated certificate was successfully loaded for encryption. |
26022 | 10 | Server is listening on [ %s <%s> %d]. |
26023 | 16 | Server TCP provider failed to listen on [ %s <%s> %d]. Tcp port is already in use. |
26024 | 16 | Server failed to listen on %s <%s> %d. Error: %#x. To proceed, notify your system administrator. |
26025 | 10 | HTTP authentication succeeded for user ‘%.*ls’.%.*ls |
26026 | 14 | HTTP authentication failed.%.*ls |
26028 | 10 | Server named pipe provider is ready to accept connection on [ %s ]. |
26029 | 16 | Server named pipe provider failed to listen on [ %s ]. Error: %#x |
26034 | 10 | The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination. |
26035 | 16 | The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x. |
26037 | 10 | The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: %#x, state: %d. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. |
26038 | 10 | The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors. |
26039 | 16 | The SQL Server Network Interface library was unable to load SPN related library. Error: %#x. |
26040 | 17 | Server TCP provider has stopped listening on port [ %d ] due to an AcceptEx failure. Socket error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
26041 | 10 | Server TCP provider has successfully reestablished listening on port [ %d ]. |
26042 | 17 | Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
26043 | 10 | Server HTTP provider has successfully reestablished listening. |
26044 | 17 | Server named pipe provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
26045 | 10 | Server named pipe provider has successfully reestablished listening on [ %s ]. |
26048 | 10 | Server local connection provider is ready to accept connection on [ %s ]. |
26049 | 16 | Server local connection provider failed to listen on [ %s ]. Error: %#x |
26050 | 17 | Server local connection provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening. |
26051 | 10 | Server local connection provider has successfully re-established listening on [ %s ]. |
26052 | 10 | SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is an informational message only. No user action is required. |
26053 | 16 | SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. There may be insufficient memory. Free up additional memory, then turn the node off and on again. If the failure persists repeat this multiple times or restart the SQL Server. |
26054 | 16 | Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: %#x. |
26056 | 10 | Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port through the SQL Server Browser Service. Error: %#x. |
26057 | 16 | Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: %#x. |
26058 | 16 | A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections. |
26059 | 10 | The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. |
26060 | 10 | The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. |
26061 | 10 | Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem with the network configuration of the computer. Error: %#x. |
26062 | 16 | Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support. |
26064 | 10 | SQL Server could not listen on IP address [%s] because the cluster resource ‘%s’ is not online (state = %d). This is an informational message and may indicate that resource ‘%s’ has OR type of dependency on several IP addresses some of which are currently offline or in a failed state. Further action is only required if it is generally possible to bind the IP address of the cluster resource ‘%s’ to a network segment on the current hosting node. |
26065 | 16 | Extended Protection for the SQL Server Database Engine is enabled, but the operating system does not support Extended Protection. Connection attempts using Windows Authentication might fail. Check for an operating system service pack to allow for Extended Protection through Service Binding and Channel Binding, or disable Extended Protection for the Database Engine. |
26066 | 16 | An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Integrated Authentication might fail. Error: %d. |
26067 | 10 | The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Windows return code: %#x, state: %d. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. |
26068 | 10 | The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors. |
26069 | 10 | Started listening on virtual network name ‘%ls’. No user action is required. |
26070 | 10 | Stopped listening on virtual network name ‘%ls’. No user action is required. |
26071 | 16 | Failed to load the Cluster Resource Libraries: clusapi.dll and resutils.dll. SQL Server will be unable to accept TCP connections on clustered listeners. |
26072 | 10 | Found multiple dependent virtual network names for the Windows Failover Cluster Resource ‘%ls’. SQL Server will only listen on the first virtual network name resource: ‘%ls’. This may indicate that there is an incorrect configuration of the Windows Failover Cluster Resources for SQL Server. |
26073 | 16 | Failed to clean up event associated with TCP connection, this is most likely because the server was under heavy load. Operating system return code: %#x |
26075 | 16 | Failed to start a listener for virtual network name ‘%ls’. Error: %d. |
26076 | 10 | SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. |
26077 | 20 | An asynchronous read has timed out |
26078 | 20 | Client disconnected during login |
26079 | 17 | Server TCP provider has stopped listening on port [ %d ] due to a CreateSocket failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
27001 | 16 | Reserved error message. Should never be issued. |
27002 | 16 | A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection. |
27003 | 16 | Bad token encountered during tokenization. |
27004 | 16 | Unexpected token type encountered during tokenization. |
27005 | 16 | Error Tolerant Index is corrupt. |
27006 | 16 | Deleted more than one rid from ridlist during delete operation. Error Tolerant Index is corrupt. |
27007 | 16 | Attempt to delete from empty ridlist. Error Tolerant Index is corrupt. |
27008 | 16 | rid to be deleted not found in rid-list. Error Tolerant Index is corrupt. |
27009 | 16 | Error Tolerant Index frequencies must be non-negative. Error Tolerant Index is corrupt. |
27010 | 16 | Attempt to insert row whose ID is already present. Error Tolerant Index is corrupt. |
27011 | 16 | No ridlist provided for appending. Error Tolerant Index is corrupt. |
27012 | 16 | Cannot delete token. Error Tolerant Index is corrupt. |
27013 | 16 | Tokenizer object has no delimiter set. Error Tolerant Index is corrupt. |
27014 | 16 | Deletion failed because token does not occur in index. Error Tolerant Index is corrupt. |
27015 | 16 | Unexpected ridlist length. Error Tolerant Index is corrupt. |
27016 | 16 | Cannot connect to Error Tolerant Index. Bad or missing SqlCommand object. |
27017 | 16 | Failed to drop index on reference table copy. |
27018 | 16 | Could not retrieve metadata from Error Tolerant Index. The index is probably corrupt. |
27019 | 16 | Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt. |
27022 | 16 | An error specific to fuzzy lookup table maintenance has occurred. |
27023 | 16 | A system error occurred during execution of fuzzy lookup table maintenance. |
27024 | 16 | Cannot write at negative index position. Could not update Error Tolerant Index. The index is probably corrupt. |
27025 | 16 | Argument is not a valid hex string. Could not initialize from metadata contained in Error Tolerant Index. The index is probably corrupt. |
27026 | 16 | Negative count in Error Tolerant Index metadata. The index is probably corrupt. |
27027 | 16 | Error tolerant index metadata contains unsupported normalization flags. The index is probably corrupt. |
27028 | 16 | Invalid Error Tolerant Index metadata. The index is probably corrupt. |
27029 | 16 | Invalid Error Tolerant Index metadata version. |
27030 | 16 | Missing metadata. The Error Tolerant Index is probably corrupt. |
27031 | 16 | Unable to parse token counts in Error Tolerant Index metadata. The index is probably corrupt. |
27032 | 16 | Error Tolerant Index Metadata string too long. Index is probably corrupt. |
27033 | 16 | Error Tolerant Index Metadata length limit exceeded. |
27034 | 16 | Unexpected end of Error Tolerant Index metadata. Index is probably corrupt. |
27037 | 16 | No table name provided for Error Tolerant Index. The index is probably corrupt. |
27038 | 16 | No input provided for decoding in Error Tolerant Index metadata. Index is probably corrupt. |
27039 | 16 | No input provided for encoding in Error Tolerant Index metadata. Index is probably corrupt. |
27040 | 16 | No Error Tolerant Index metadata string provided for initialization. Index is probably corrupt. |
27041 | 16 | No Error Tolerant Index metadata provided for serialization. The index is probably corrupt. |
27042 | 16 | Could not lookup object_id. No object name provided. |
27043 | 16 | Could not lookup object_id. Null command object provided. |
27044 | 16 | Open connection required. Cannot query Error Tolerant Index. |
27045 | 16 | Cannot write to null output buffer. Could not update Error Tolerant Index. The index is probably corrupt. |
27046 | 16 | Output buffer provided is too small. Could not update Error Tolerant Index. The index is probably corrupt. |
27047 | 16 | The number of min-hash q-grams per token must be positive. |
27048 | 16 | Could not create index on reference table copy. |
27049 | 16 | Reference table (or internal copy) missing integer identity column. Error tolerant index is probably corrupt. |
27050 | 16 | The maximum allow integer identity value has been reached. Consider re-building the error tolerant index to use any gaps in sequence. |
27051 | 16 | Could not read rid from data provided (missing column name, null reader object, or corrupted data). The index is probably corrupted. |
27052 | 16 | Table maintenance insertion failed. |
27053 | 16 | A positive q-gram length is required for tokenization. |
27054 | 16 | Maintenance trigger already installed on this reference table. |
27055 | 16 | Missing extended property on maintenance trigger. |
27056 | 16 | Maintenance trigger name out of sync with Error Tolerant Index metadata. Index is probably corrupt. |
27058 | 16 | A SQL error occurred during execution of fuzzy lookup table maintenance. |
27059 | 16 | Could not lookup object_id. The reference table or maintenance trigger could not be found. |
27060 | 16 | The Error Tolerant Index table name provided is not a valid SQL identifier. |
27061 | 16 | The Error Tolerant Index table name provided refers to a missing table. Check sys.tables. |
27062 | 16 | An auxiliary Fuzzy Lookup table maintenance table is missing. |
27063 | 16 | An auxiliary Fuzzy Lookup table maintenance table name is null. Maintenance cannot proceed. |
27064 | 16 | The row deleted from the reference table could not be located in the reference table copy. |
27065 | 16 | Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt. |
27100 | 16 | The input parameter, ‘%ls’, cannot be null. Provide a valid value for this parameter. |
27101 | 16 | The value specified for the input parameter, ‘%ls’, is not valid. Provide a valid value for this parameter. |
27102 | 16 | The input parameter, ‘%ls’, cannot be empty. Provide a valid value for this parameter. |
27103 | 16 | Cannot find the execution instance ‘%I64d’ because it does not exist or you do not have sufficient permissions. |
27104 | 16 | Cannot find the folder ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27105 | 16 | Cannot find the operation ‘%I64d’ because it does not exist or you do not have sufficient permissions. |
27106 | 16 | Cannot find the parameter ‘%ls’ because it does not exist. |
27107 | 16 | The specified %ls already exists. |
27108 | 16 | The path for ‘%ls’ cannot be found. The operation will now exit. |
27109 | 16 | Cannot find the project ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27110 | 16 | Default permissions for the project cannot be granted to the user. Make sure that the user can be assigned these permissions. |
27111 | 16 | Cannot find the reference ‘%I64d’ because it is not part of the project or you do not have sufficient permissions. |
27112 | 16 | Unable to update the row in the table, ‘%ls’. Make sure that this row exists. |
27113 | 16 | Unable to delete one or more rows in the table, ‘%ls’. Make sure that these rows exist. |
27114 | 16 | Cannot find the reference ‘%I64d’ because it does not exist or you do not have sufficient permissions. |
27115 | 16 | Cannot find the target folder ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27116 | 16 | Conversion failed while performing encryption. |
27117 | 16 | Failed to decrypt the project. The symmetric key that was used to encrypt it may have been deleted. Delete the project and deploy it again. |
27118 | 16 | Failed to deploy the project. Try again later. |
27119 | 16 | Failed to encrypt the project named ‘%ls’. The symmetric key may have been deleted. Delete the project and deploy it again. |
27120 | 16 | Failed to grant permission ‘%ls’. |
27121 | 16 | The project is currently running or has completed. An instance of execution can only be started once. |
27122 | 16 | Unable to perform impact analysis and lineage. The package data or configuration data might not be valid. To validate package data, open the package in Business Intelligence Development Studio. To validate configuration data, open the configuration XML file in an XML editor. |
27123 | 16 | The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Integrated Authentication. |
27124 | 16 | Integration Services server cannot stop the operation. The specified operation with ID ‘%I64d’ is not valid or is not running. |
27125 | 16 | Integration Services server cannot stop the operation. The specified operation is not in a consistent state and cannot be stopped. |
27126 | 16 | Integration Services server cannot stop the operation. The specified operation is already in Stopping state. |
27127 | 16 | The Integration Services catalog ‘%ls’ does not exists. |
27128 | 16 | The name ‘%ls’ is not valid. It consists of characters that are not allowed. |
27129 | 16 | The folder ‘%ls’ already exists or you have not been granted the appropriate permissions to change it. |
27130 | 16 | Integration Services server was unable to impersonate the caller. Operating system returned error code: %ls. |
27131 | 16 | Integration Services server was unable to start the process, ‘%ls’. Operating system returned error code: %ls. |
27132 | 16 | Integration Services server was unable to create process component, ‘%ls’. Operating system returned error code: %ls. |
27133 | 16 | Integration Services server was unable to wait for process, ‘%ls’, to finish. Operating system returned error code: %ls. |
27135 | 16 | The database, ‘%ls’, already exists. Rename or remove the existing database, and then run SQL Server Setup again. |
27136 | 16 | The required components for the 32-bit edition of Integration Services cannot be found. Run SQL Server Setup to add the required components. |
27137 | 16 | The registry key for the system setting ‘%ls’ could not be found. The operation will now exit. |
27138 | 16 | The input parameter cannot be null. Provide a valid value for the parameter. |
27139 | 16 | Integration Services server cannot be configured because there are active operations. Wait until there are no active operations, and then try to configure the server again. |
27140 | 16 | The operation cannot be started because the user is not a member of the database role, ‘%ls’, or the server role, ‘%ls’. Log in as a member of one of these roles, and then try to start the operation again. |
27141 | 16 | Integration Services server cannot be configured because there are execution logs. Please cleanup all execution logs, and then try to configure the server again. |
27142 | 16 | ‘%ls’ is not a valid environment name. It consists of characters that are not allowed. |
27143 | 16 | Cannot access the operation with ID, ‘%I64d’. Verify that the user has appropriate permissions. |
27145 | 16 | ‘%ls’ is not a valid project name. It consists of characters that are not allowed. |
27146 | 16 | Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it. |
27147 | 16 | The data type of the input value is not compatible with the data type of the ‘%ls’. |
27148 | 16 | The data type of the parameter does not match the data type of the environment variable. |
27149 | 16 | Integration Services server cannot perform the requested operation on the specified package now, because the package is in pending state. Wait until the package is not in pending state, and try to perform the operation again. |
27150 | 16 | The version of the project has changed since the instance of the execution has been created. Create a new execution instance and try again. |
27151 | 10 | The restore operation for project ‘%ls’ from version ‘%I64d’ has started. |
27152 | 10 | The restore operation for project ‘%ls’ to version ‘%I64d’ has completed. |
27153 | 16 | Default permissions for the operation cannot be granted to the user. Make sure that the user can be assigned these permissions. |
27154 | 16 | The @sensitive parameter is missing. This parameter is used to indicate if the parameter contains a sensitive value. |
27155 | 16 | Project restore has failed. You cannot restore a project having an object_version_lsn that is the same as the current project. |
27156 | 16 | The Integration Services server property, ‘%ls’, cannot be found. Check the name of the property and try again. |
27157 | 16 | The environment ‘%ls’ already exists or you have not been granted the appropriate permissions to create it. |
27158 | 16 | Error number, %d, occurred in the procedure, ‘%ls’, at line number, %d. The error message was: ‘%ls’ The error level was %d and the state was %d. |
27159 | 16 | Data type of the input value is not supported. |
27160 | 16 | The Stored Procedure, ‘%ls’, failed to run because the Integration Services database (SSISDB) is not in single-user mode. In SQL Server Management Studio, launch Database Properties dialog box for SSISDB, switch to the Options tab, and set the Restrict Access property to single-user mode (SINGLE_USER). Then, try to run the stored procedure again. |
27161 | 10 | Warning: the requested permission has already been granted to the user. The duplicate request will be ignored. |
27162 | 16 | The property, ‘%ls’, cannot be changed because the Integration Services database is not in single-user mode. In Management Studio, in the Database Properties dialog box, set the Restrict Access property to single-user mode. Then, try to change the value of the property again. |
27163 | 16 | The value for the Integration Services server property, ‘%ls’, is not valid. In Management Studio, in the Integration Services Properties dialog box, enter a valid value for this property. |
27165 | 10 | Warning: During startup, the Integration Services server marked operation %I64d (type %d, status %d) as terminated. Please check the operating system error logs for operation details. |
27166 | 16 | The installed version of SQL Server does not support the installation of the Integration Services server. Update SQL Server, and then try installing the Integration Services server again. |
27167 | 16 | Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the environment variables with the ‘%ls’ algorithm. |
27168 | 16 | Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the parameter values using the ‘%ls’ algorithm. |
27169 | 16 | Failed to create a log entry for the requested operation. |
27170 | 16 | Failed to retrieve the project named ‘%ls’. |
27171 | 16 | The value specified is not valid. A value of data type ‘%ls’ is required. |
27172 | 16 | The certificate and symmetric key used to encrypt project ‘%ls’ does not exist or you do not have sufficient permissions. |
27173 | 16 | The environment variable ‘%ls’ already exists. |
27175 | 16 | The execution has already completed. |
27176 | 16 | The parameter ‘%ls’ does not exist or you do not have sufficient permissions. |
27177 | 16 | Environment names must be unique. There is already an environment named ‘%ls’. |
27178 | 16 | Unable to execute the project named ‘%ls’. You do not have sufficient permissions. |
27179 | 16 | The object version does not match the project id or you do not have sufficient permissions. |
27180 | 16 | %ls is not a valid environment variable name. It consists of characters that are not allowed. |
27181 | 16 | The project ‘%ls’ already exists or you have not been granted the appropriate permissions to access it. |
27182 | 16 | The environment ‘%s’ does not exist or you have not been granted the appropriate permissions to access it. |
27183 | 16 | The environment variable ‘%ls’ does not exist or you have not been granted the appropriate permissions to access it. |
27184 | 16 | In order to execute this package, you need to specify values for the required parameters. |
27185 | 16 | The validation record for ID ‘%I64d’ does not exist or you have not been granted the appropriate permissions to access it. |
27186 | 16 | One or more environment variables could not be found in the referenced environment. |
27187 | 16 | The project does not exist or you have not been granted the appropriate permissions to access it. |
27188 | 16 | Only members of the ssis_admin or sysadmin server roles can create, delete, or rename a catalog folder. |
27189 | 16 | Catalog folder name cannot be NULL or an empty string. |
27190 | 16 | The folder ‘%ls’ already exists or you have not been granted the appropriate permissions to create it. |
27191 | 16 | The ‘%d’ permission is not applicable to objects of type ‘%d’. Grant, deny, or revoke of this permission is not allowed. |
27192 | 16 | The caller has not been granted the MANAGEPERMISSION permission for the specified object. |
27193 | 16 | SQL Server %ls is required to install Integration Services. It cannot be installed on this version of SQL Server. |
27194 | 16 | Cannot find the project because it does not exist or you do not have sufficient permissions. |
27195 | 16 | The operation failed because the execution timed out. |
27196 | 16 | Failed to delete the folder ‘%ls’ because it is not empty. Only empty folders can be deleted. |
27197 | 16 | The specified %ls %ld does not exist. |
27198 | 16 | Failed to locate records for the specified operation (ID %I64d). |
27199 | 16 | %ls is not a valid folder name. It consists of characters that are not allowed. |
27200 | 16 | The project is missing the specified environment reference. |
27201 | 16 | Values are missing for required parameters in this package. Specify values in order to start the validation. |
27202 | 16 | This project is missing one or more environment references. In order to use environment variables, specify the corresponding environment reference identifier. |
27203 | 16 | Failed to deploy project. For more information, query the operation_messages view for the operation identifier ‘%I64d’. |
27204 | 16 | Failed to create environment reference. This project already has an reference to the specified environment. |
27205 | 16 | Some of the property values for this parameter are missing. |
27206 | 16 | Failed to deploy project to the folder ‘%ls’. You do not have sufficient permissions to deploy this project. |
27207 | 16 | Failed to locate one or more variables in the environment ‘%ls’. |
27208 | 16 | The environment reference ‘%I64d’ is not associated with the project. |
27209 | 16 | Failed to create environment to the folder ‘%ls’. You do not have sufficient permissions to create this environment. |
27210 | 16 | Conversion failed when converting the %ls to data type %ls. |
27212 | 16 | Data tap can only be added or removed when the execution status is created. |
27213 | 16 | The package path and data flow path ID strings already exist for the execution ID %I64d. Provide package path and data flow path ID strings that are not in the catalog.execution_data_taps view. |
27214 | 16 | The data flow task GUID ‘%ls’ and the data flow path ID string already exist for the execution ID %I64d. Provide a data flow task GUID and a data flow path ID string that are not in the catalog.execution_data_taps view. |
27215 | 16 | The data tap ‘%I64d’ does not exist, or you do not have sufficient permissions to remove it. Provide a valid data tap ID. |
27216 | 16 | The number of rows must be a non-negative value. Specify a valid value. |
27217 | 16 | The logging level ‘%d’ is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), 3 (Verbose), 4 (RuntimeLineage), 100 (Customized). |
27218 | 16 | The Integration Services Server cannot find the running process for execution ID %I64d. Provide a valid execution ID. |
27219 | 16 | Caller does not have permissions to execute the stored procedure. |
27220 | 16 | SSISDB database does not exist. Create the SSISDB database. |
27221 | 16 | Unable to map an environment variable with the sensitive property set to True, to a parameter with the sensitive property set to False. Ensure that the property settings match. |
27222 | 16 | The required components for the 64-bit edition of Integration Services cannot be found. Run SQL Server Setup to install the required components. |
27223 | 16 | Cannot move the project to folder ‘%ls’ due to insufficient permissions. |
27224 | 16 | The parameter value cannot be changed after the execution has been started. |
27225 | 16 | The property cannot be overridden after the execution has been started. |
27226 | 16 | The database principal has granted or denied permissions to catalog objects in the database and cannot be dropped. |
27227 | 16 | The server ‘%ls’ already exists. |
27228 | 16 | The server ‘%ls’ does not exists. |
27229 | 16 | Cannot find the SQL login ‘%ls’. |
27230 | 16 | Failed to deploy the packages. Try again later. |
27231 | 16 | Failed to deploy packages. For more information, query the operation_messages view for the operation identifier ‘%I64d’. |
27232 | 16 | Failed to create customized logging level ‘%ls’. You do not have sufficient permissions to create customized logging level. |
27233 | 16 | Customized logging level name cannot be NULL or an empty string. |
27234 | 16 | ‘%ls’ is not a valid customized logging level name. It consists of characters that are not allowed. |
27235 | 16 | The customized logging level ‘%ls’ already exists. |
27236 | 16 | Failed to delete customized logging level ‘%ls’. You do not have sufficient permissions to delete customized logging level. |
27237 | 16 | The customized logging level ‘%ls’ does not exist. |
27238 | 16 | Failed to rename customized logging level ‘%ls’ with ‘%ls’. You do not have sufficient permissions to rename customized logging level. |
27239 | 16 | Failed to update customized logging level ‘%ls’. You do not have sufficient permissions to update customized logging level. |
27240 | 16 | The value can not be less than zero. |
27241 | 16 | Failed to update logging level ‘%d’. Provide the value for SERVER_CUSTOMIZED_LOGGING_LEVEL property, as it can not be null or empty for logging level ‘%d’. |
27242 | 16 | Cannot find the cluster execution job instance ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27243 | 16 | Cannot find the cluster worker agent ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27246 | 16 | Cannot find the cluster execution task instance ‘%ls’ because it does not exist or you do not have sufficient permissions. |
27251 | 16 | Cannot add a worker agent to execute the cluster job instance ‘%ls’ because the job is specified for all worker agents. |
27252 | 16 | The Integration Services cluster worker agent ‘%ls’ is disabled. |
27255 | 16 | The job id of the execution is null. Create a job for the execution first and try again. |
27256 | 16 | The event message does not exist. |
27257 | 16 | There is no active worker agent. |
27259 | 16 | Failed to enable worker agent because current SQL Server edition only support limited number of worker agents. |
27260 | 16 | Only members of sysadmin server roles can perform this action. |
27261 | 16 | There is no Scale Out Master installed. |
27303 | 16 | An unexpected error with HRESULT 0x%x occurred while processing backup files. Refer to the SQL Server error log for information about any related errors that were encountered. Address those errors if necessary, and retry the operation. |
27308 | 16 | SegmentID %d from the archive does not match the segmentID %d from the specified filename on brick %d. |
27801 | 10 | Successfully initialize HPC environment from provider ‘%ld’, device type ‘%ld’ DLL version %ld, and find %ld device(s), %ld of them are used. |
27802 | 16 | Failed to initialize HPC environment. |
27803 | 10 | Message reported from (%.*s) device on device Id (%I64d), code : %d, message : %.*s . |
27804 | 16 | Query failed on HPC device Id (%I64d), with error code %d . |
28000 | 16 | The decrypted session key has an unexpected size. |
28001 | 16 | A corrupted message has been received. It contains invalid flags. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28002 | 16 | Cannot start service broker manager. Operating system error: %ls. |
28003 | 16 | An internal service broker error occurred. Operating system error: %ls. |
28004 | 16 | This message could not be delivered because the ‘%S_MSG’ action cannot be performed in the ‘%.*ls’ state. |
28005 | 16 | An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls |
28006 | 14 | User does not have permission to %S_MSG the conversation ‘%.*ls’ in state ‘%.*ls’. Only members of the sysadmin fixed server role and the db_owner fixed database role have this permission. |
28007 | 16 | A corrupted message has been received. The highest seen message number must be greater than the acknowledged message number. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28008 | 16 | The conversation handle ‘{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}’ is invalid. |
28009 | 16 | The crypto API has detected bad data while trying to perform a decryption operation. |
28010 | 16 | This message could not be delivered because it contains an invalid acknowledged message number. Highest expected message number: %I64d. Acknowledged message number: %I64d, fragment number: %d. |
28011 | 16 | This message could not be delivered because its %S_MSG has expired or is invalid. |
28012 | 16 | The Service Broker in the target database is unavailable: ‘%S_MSG’. |
28013 | 16 | The service broker is administratively disabled. |
28014 | 16 | The database is in read-only mode. |
28015 | 16 | The database is in single-user mode. |
28016 | 16 | The message has been dropped because the service broker in the target database is unavailable: ‘%S_MSG’. |
28017 | 16 | The message has been dropped because the target service broker is unreachable. |
28018 | 16 | The database is a replica of a mirrored database. |
28019 | 16 | System error %d occurred while creating a new message element GUID for this forwarded message. |
28020 | 16 | Could not create user token for user %d in database %d. |
28021 | 16 | One or more messages could not be delivered to the local service targeted by this dialog. |
28022 | 10 | An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid. |
28023 | 10 | An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired. |
28024 | 16 | The security certificate bound to database principal (Id: %i) is not yet valid. Either wait for the certificate to become valid or install a certificate that is currently valid. |
28025 | 16 | The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal. |
28026 | 10 | Connection handshake failed. Not enough memory available. State %d. |
28027 | 10 | Connection handshake failed. There is no compatible %S_MSG. State %d. |
28028 | 10 | Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d. |
28029 | 10 | Connection handshake failed. Unexpected event (%d) for current context (%d). State %d. |
28030 | 10 | Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d. |
28031 | 10 | Connection handshake failed. An OS call failed: (%x) %ls. State %d. |
28032 | 10 | A previously existing connection with the same peer was detected during connection handshake. This connection lost the arbitration and it will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d. |
28033 | 10 | A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d. |
28034 | 10 | Connection handshake failed. The login ‘%.*ls’ does not have CONNECT permission on the endpoint. State %d. |
28035 | 10 | Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d. |
28036 | 10 | Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d. |
28037 | 10 | Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the operating system error log may contain entries related to this error. State %d. |
28038 | 10 | Connection handshake failed. The handshake verification failed. State %d. |
28039 | 10 | Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d. |
28040 | 10 | A corrupted message has been received. The adjacent error message header is invalid. |
28041 | 16 | A corrupted message has been received. The encrypted payload offset is invalid (%d). |
28042 | 16 | A corrupted message has been received. The arbitration request header is invalid. |
28043 | 16 | A corrupted message has been received. The arbitration response header is invalid. |
28044 | 16 | A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28045 | 10 | Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d. |
28046 | 10 | %S_MSG Login succeeded for user ‘%.*ls’. Authentication mode: %.*ls. %.*ls |
28047 | 10 | %S_MSG login attempt failed with error: ‘%.*ls’. %.*ls |
28048 | 10 | %S_MSG login attempt by user ‘%.*ls’ failed with error: ‘%.*ls’. %.*ls |
28049 | 16 | A corrupted message has been received. The proxy connect message header is invalid. |
28050 | 10 | The session keys for this conversation could not be created or accessed. The database master key is required for this operation. |
28051 | 10 | Could not save a dialog session key. A master key is required in the database to save the session key. |
28052 | 16 | Cannot decrypt session key while regenerating master key with FORCE option. |
28053 | 16 | Service Broker could not upgrade conversation session keys in database ‘%.*ls’ to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker. |
28054 | 16 | Service Broker needs to access the master key in the database ‘%.*ls’. Error code:%d. The master key has to exist and the service master key encryption is required. |
28055 | 16 | The certificate ‘%.*ls’ is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date. |
28056 | 16 | This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: ‘%.*ls’. |
28057 | 10 | Service Broker in database ‘%.*ls’ has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete. |
28058 | 16 | Service Broker could not upgrade this conversation during a database upgrade operation. |
28059 | 16 | Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d. |
28060 | 16 | The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions. |
28061 | 16 | A corrupted message has been received. The adjacent message integrity check signature could not be validated. |
28062 | 16 | A corrupted message has been received. The signed dialog message header is invalid. |
28063 | 16 | A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28064 | 16 | A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28065 | 16 | A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28066 | 16 | A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28067 | 16 | A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28068 | 16 | A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d. |
28069 | 16 | Unexpected session key when encrypting a dialog message. |
28070 | 10 | Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d. |
28071 | 10 | The received message could not be forwarded onto another connection. State %d. |
28072 | 16 | A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds. |
28073 | 16 | An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds. |
28074 | 16 | Service Broker could not upgrade conversation with conversation_handle ‘%ls’. Use END CONVERSATION … WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE … SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE … SET NEW_BROKER to delete all conversations in this database. |
28075 | 10 | The broker in the sender’s database is in single user mode. Messages cannot be delivered while in single user mode. |
28076 | 10 | Could not query the FIPS compliance mode flag from registry. Error %ls. |
28077 | 10 | %S_MSG endpoint is running in FIPS compliance mode. This is an informational message only. No user action is required. |
28078 | 10 | The RC4 encryption algorithm is not supported when running in FIPS compliance mode. |
28079 | 10 | Connection handshake failed. The received SSPI packet is not of the expected direction. State %d. |
28080 | 10 | Connection handshake failed. The %S_MSG endpoint is not configured. State %d. |
28081 | 10 | Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d. |
28082 | 10 | Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d. |
28083 | 16 | The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys. |
28084 | 10 | An error occurred in Service Broker internal activation while trying to scan the user queue ‘%ls’ for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required. |
28085 | 16 | The activated task was ended because the associated queue was dropped. |
28086 | 16 | The activated task was ended because either the queue or activation was disabled. |
28087 | 16 | The activated task was aborted because the invoked stored procedure ‘%ls’ did not execute RECEIVE. |
28088 | 16 | The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous “Broker:Activation” trace event for possible output from the activation stored procedure. |
28089 | 16 | The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas. |
28090 | 16 | An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available. |
28091 | 10 | Starting endpoint for %S_MSG with no authentication is not supported. |
28092 | 10 | Error updating proxy settings |
28098 | 10 | A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State %d. |
28099 | 10 | During the database upgrade process on database ‘%.*ls’, a user object ‘%S_MSG’ named ‘%.*ls’ was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade process is unable to install the object. Remove or rename the user object from the original (pre-upgraded) database on an older version of SQL Server and then retry the database upgrade process by using CREATE DATABASE FOR ATTACH. Functionality that relies on the reserved object may not function correctly if you continue to use the database in the current state. |
28101 | 16 | User ‘%.*ls\%.*ls’ does not have permission to debug the requested client connection. |
28102 | 16 | Batch execution is terminated because of debugger request. |
28401 | 16 | Feature or option ‘%ls’ is not available. Please consult Books Online for more information on this feature or option. |
28405 | 17 | During error handling, a second error was raised, causing an unrecoverable failure. |
28502 | 11 | The specified object Id is not valid. |
28503 | 11 | The specified index Id is not valid. |
28504 | 11 | The specified partition number is not valid. |
28506 | 11 | Incorrect number of keys was specified. Must specify at least first %d key columns |
28554 | 16 | Data Virtualization Manager not found. |
28555 | 10 | DVM failed to handle matrix reconfiguration. {error_code: %d, state: %d} |
28601 | 16 | The Transaction Coordination Manager has encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, which may prevent further transaction processing. Examine previously logged messages to figure out the cause for this unexpected failure. Depending on the failure condition, the Transaction Coordination Manager might be restarted automatically. |
28602 | 16 | The transaction is aborted because the transaction agent is shutting down. |
28603 | 10 | Transaction agent is shutting down because shutdown request was received from the manager. |
28604 | 10 | Transaction Coordination Manager is starting up. This is an informational message only. No user action is required. |
28605 | 10 | Transaction Coordination Manager is inactive. This is an informational message only. No user action is required. |
28606 | 10 | Transaction Coordination Manager is active with %016I64x as the starting AGE. This is an informational message only. No user action is required. |
28607 | 16 | TCM %.*ls has received an out of order message from brick id %d and has to be stopped. Based on the state of the system it may restart and re-synchronize automatically. Typical causes for missed messages are temporary network errors or out of memory conditions. Look for earlier messages in the log which should contain additional information. |
28608 | 16 | Federated transaction could not be started at this time because the TCM Agent is not in a state, which allows new transactions to begin. The TCM Agent is currently in state: %d. The most common reason for this is that the system is being shutdown. Previous messages in the log should contain additional information. |
28609 | 16 | Matrix transaction operation is not allowed because the transaction doesn’t allow forward progress, the transaction will be rolled back. |
28610 | 16 | Matrix transaction couldn’t commit because the task is aborted. The task is aborted either because of cancel instruction from client application, or because one or more transaction paritipant went offline. |
28612 | 20 | An error occurred while accessing Transaction Coordination Manager metadata. Could not persist AGE %016I64x. |
28613 | 10 | Transaction Coordination Agent is active. This is an informational message only. No user action is required. |
28614 | 16 | TCM manager has received a request for re-synchronization from brick id %d and will now restart. Typical causes where restart is necessary are temporary network errors or out of memory conditions. Look for earlier messages in the log on the offending brick for more information. |
28615 | 20 | The request has performed an operation that is disallowed on a remote branch of a transaction |
28701 | 16 | Request aborted due to communication errors: an attempt was made to use channel %d.%d.%I64u in the closed state. |
28702 | 16 | Request aborted due to communication errors: incoming message format violation. |
28703 | 16 | Request aborted due to communication errors: no enabled channel maps for component %d found. |
28704 | 16 | Request aborted due to communication errors: unable to allocate new message for the brick %d. Error code %d. |
28705 | 16 | Request aborted due to communication errors: unable to complete send operation for the pipeline %hs. Error code %d. |
28706 | 10 | Next message reported have originated on brick %d. |
28707 | 20 | Brick was unable to communicate with configuration manager and will be disconnected. See previous errors for the details. |
28708 | 16 | Failure encountered due to Matrix configuration change: a brick was evicted. |
28709 | 16 | Dispatcher was unable to create new thread. |
28710 | 16 | Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent but there were no messages received on other side. |
28711 | 16 | Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent at age %d (current age and bytes sent are %I64d and %I64d) but receive side has processed only %I64d at age %d. |
28712 | 16 | Unable to start expiration manager dispatch thread. Result code %d. |
28713 | 16 | Communication subsystem failed to process user abort request. Error Number: %d; State: %d. |
28714 | 16 | Request aborted due to communication errors: an attempt was made to communicate with Brick %d which is no longer online or have been reconfigured. |
28715 | 10 | Execution of the request was aborted on remote brick. |
28716 | 16 | Request aborted due to communication errors: too many concurrent operations. |
28717 | 16 | Request aborted due to communication errors: communication subsystem is shutting down or initialization not complete yet. |
28718 | 16 | Request aborted due to communication errors: pipeline %hs received message (classId %d, sequenceId %d) from the expired age %d (last acceptable age %d). |
28719 | 16 | Request aborted due to Fabric errors: unable to enqueue a task for workspace 0x%I64x. |
28720 | 16 | Mci subsystem failed to start with error %d. |
28721 | 16 | Mci subsystem failed to start channel %d with error %d |
28722 | 20 | Force close service was unable to communicate with configuration manager (brick %d) either due errors or timeout (%d milliseconds). Matrix is not functioning properly. Investigation is prudent. |
28723 | 16 | Brick was shutdown by administrator request |
28724 | 16 | Channel close verification |
28725 | 20 | Unable to process cancellation request due to resource availability. Retrying… |
28726 | 20 | Unable to process activation data for a workspace. |
28727 | 20 | Unable to process incoming message due to resource availability. |
28728 | 16 | Request aborted due to communication errors: no channel maps of version %d for component %d found to create channel %I64u. |
28729 | 16 | Request aborted due to communication errors: a message have arrived for non-activated channel %I64u. |
28903 | 16 | Configuration manager agent enlistment is retrying enlistment since brick <%d> eviction is pending. |
28904 | 16 | Configuration manager agent enlistment is sending join request message to manager. |
28905 | 16 | Configuration manager agent enlistment failed to receive reply from manager. See previous errors in error log. |
28906 | 16 | Configuration manager agent enlistment completed with ‘%s’. |
28907 | 16 | Configuration manager agent enlistment stopped. |
28908 | 16 | Configuration manager agent enlistment failed due to different enlistment protocol versions between manager and agent. Version received from manager: <%d>, Version expected: <%d>. |
28909 | 16 | Configuration manager agent enlistment failed due to receiving reply from invalid manager brick id <%d> . |
28911 | 10 | Configuration manager agent enlistment succeeded. Manager accepted brick <%d> join request. |
28912 | 16 | Brick <%d> enlistment with configuration manager failed due to ‘%s’ mismatch. Brick will be taken down. |
28913 | 16 | Configuration manager agent enlistment encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, that prevents the brick from joining the matrix. Brick will be taken down. |
28914 | 10 | Configuration manager agent enlistment: Brick <%d>, state <%d>. |
28915 | 16 | Configuration manager agent encountered error %d, state %d, severity %d while updating brick <%lu> incarnation to %I64u. Examine previous logged messages to determine cause of this error. |
28916 | 16 | Configuration manager agent encountered error %d, state %d, severity %d while updating state information. Examine previous logged messages to determine cause of this error. |
28917 | 10 | Configuration manager agent enlistment received join reply message. |
28919 | 16 | Duplicate brick id <%d> detected in configuration file. |
28920 | 16 | Configuration manager agent cannot send reported error to configuration manager due to error %d, state %d, severity %d. |
28921 | 16 | No configuration file specified. |
28922 | 16 | Configuration manager agent thread encountered fatal exception (error: %d severity: %d state: %d). This is a serious error and brick will be taken down. Examine previously logged messages to figure out the cause for this fatal failure. |
28923 | 16 | Configuration manager agent initialization failed. See previous errors in error log. This is a serious error condition and brick will be taken down. |
28924 | 16 | Configuration manager agent activation failed. |
28929 | 16 | Configuration manager agent cannot commit new roster. |
28931 | 16 | Configuration manager agent roster is corrupt. |
28932 | 16 | Configuration manager agent did not receive a shutdown channel map. |
28933 | 16 | Configuration manager agent could not perform brick down notification. |
28934 | 16 | Configuration manager agent could not perform brick up notification. |
28935 | 16 | Configuration manager agent is trying to start non-existing agent %d. |
28936 | 16 | Configuration manager agent start failed (Loc: %d). |
28937 | 16 | Configuration manager agent stop failed. |
28938 | 10 | Configuration manager agent has started. |
28939 | 10 | Configuration manager agent has shutdown. |
28940 | 16 | Configuration manager agent could not delete stale MCI sessions. |
28942 | 16 | Error reading configuration file. (Reason=%d). |
28943 | 16 | Error reading configuration file. Column %s not defined. |
28944 | 16 | Error reading configuration file. Host name or instance name cannot be empty (Reason: %d). |
28945 | 16 | Error reading configuration file. Invalid contents. (Reason=%d). |
28946 | 16 | Error reading matrix.xsd schema configuration file. (Reason=%d). |
28947 | 16 | Error reading configuration file. (line:%d, column:%d, Reason=%s). |
28948 | 16 | Error reading configuration file. Invalid placement brick id. |
28949 | 16 | Error during configuration check (Function:%s, result: 0x%08lx). |
28950 | 16 | Configuration manager agent cannot store metadata. |
28951 | 16 | Cannot update roster, brick id %d not part of roster. |
28952 | 16 | Configuration manager cannot initialize agent %d. |
28953 | 16 | Matrix agent %d has the invalid state %d. |
28955 | 16 | Cannot create roster memento. |
28958 | 16 | Error copying configuration. (Reason=%s). |
28959 | 16 | Cannot commit metadata change for brick id %d. |
28960 | 16 | Error: Cannot read <%s> node of configuration file. |
28961 | 16 | Error: invalid configuration file, no bricks defined. |
28962 | 16 | Error: Invalid value for manager name %s specified. |
28963 | 16 | Error: Invalid value for manager role %s specified. |
28964 | 16 | Error: Cannot create dom object for writing of XML configuration file (Reason %d). |
28968 | 10 | Starting communication infrastructure for communication between configuration manager and agent |
28969 | 10 | Configuration manager agent shutting down… |
28970 | 16 | Error: cannot update matrix metadata (Loc: %d). |
28972 | 16 | Error: cannot determine host name. |
28973 | 16 | Configuration manager agent cannot create notification publisher. |
28974 | 16 | Configuration manager agent cannot create notification service. |
28975 | 16 | Brick not configured correctly, corrupt configuration file. |
28976 | 16 | Configuration manager agent is ignoring stale message from manager brick %d due to ‘%s’ mismatch. Expected %I64u but received %I64u |
28977 | 16 | Configuration manager agent is performing ‘%s’ ‘%s’ operation. |
28978 | 16 | Configuration manager agent cannot ‘%s’ ‘%s’. Examine previous logged messages to determine cause of this error. This is a fatal error affecting system functionality and brick will be taken down. |
28979 | 16 | Configuration manager agent cannot ‘%s’ ‘%s’ due to invalid state ‘%s’. This is a fatal error affecting system functionality and brick will be taken down. |
28980 | 16 | Error writing brick simulator state file. (Reason=%s). |
29001 | 16 | To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO). |
29003 | 16 | Invalid parameter combinations. |
29004 | 16 | Unknown property specified: %s. |
29103 | 16 | TCMA is shutting down since it encountered fatal error %d, state %d, severity %d |
29104 | 16 | Failure in channel announce |
29105 | 16 | Failure in channel enable |
29201 | 17 | Configuration manager enlistment can not initialize communication service to receive enlistment requests |
29202 | 16 | Configuration manager enlistment is ignoring message from brick <%d>. Enlistment protocol version mismatch. Agent version <%X>, manager version <%X>. |
29203 | 16 | Configuration manager enlistment denied join of brick <%d>. |
29204 | 16 | Configuration manager enlistment denied join of brick <%d>. Server default collation mismatch. Agent collation <%lu>, manager collation <%lu>. |
29205 | 16 | Configuration manager enlistment denied join of brick <%d>. SQL version or build number mismatch. Agent version <%X>, manager version <%X>. |
29206 | 16 | Configuration manager enlistment is ignoring messages from brick <%d> since message queue does not exist. |
29207 | 16 | Configuration manager enlistment is ignoring stale message from brick %d due to ‘%s’ mismatch. Expected %I64u but received %I64u |
29208 | 16 | Cannot commit metadata change ‘%s’ for brick id %d. |
29209 | 16 | Configuration manager enlistment encountered error %d, state %d, severity %d and is shutting down. This is a serious error condition, which prevents further enlistment and bricks joining matrix. Brick will be restarted. |
29210 | 16 | Configuration manager enlistment encountered error %d, state %d, severity %d while sending enlistment reply to brick <%lu>. Enlistment reply not sent! Examine previous logged messages to determine cause of this error. |
29211 | 16 | Configuration manager enlistment is ignoring request from invalid brick id <%d>. |
29212 | 16 | Configuration manager enlistment encountered error %d, state %d, severity %d while updating brick <%lu> incarnation to %I64u. Enlistment request from brick is not processed. Examine previous logged messages to determine cause of this error. |
29215 | 10 | Configuration manager enlistment acknowledges brick join request. Brick <%d> joined matrix. |
29217 | 10 | Configuration manager enlistment received a new enlistment message. |
29218 | 10 | Configuration manager enlistment state machine: Brick <%d>, state <%d> |
29219 | 10 | Reserved brick <%d> is now marked active |
29220 | 10 | Configuration manager enlistment started. |
29221 | 10 | Configuration manager enlistment stopped. |
29222 | 16 | Configuration manager enlistment did not receive enlistment messages |
29223 | 17 | Configuration manager enlistment ran out of memory. Enlistment messages ignored. |
29224 | 10 | Configuration manager enlistment sent reply to brick <%d>. |
29225 | 10 | Configuration manager enlistment received join message from brick <%d> |
29227 | 17 | Thread creation failed. (RC=%d). |
29228 | 10 | Matrix transitioned from state %d to state %d. |
29229 | 10 | Brick transitioned from state %d to state %d. |
29230 | 10 | Manager transitioned from state %d to state %d. |
29231 | 10 | Matrix transitioned from state %d to state %d. |
29232 | 16 | Cannot create configuration manager enlistment thread. |
29233 | 16 | Configuration manager thread encountered fatal exception (error: %d state: %d severity: %d). This is a serious error and brick will be taken down. Examine previously logged messages to figure out the cause for this fatal failure. |
29234 | 16 | Configuration manager initialization failed. (Reason=%s). |
29235 | 16 | Configuration manager cannot create channel distribution service. |
29236 | 16 | Configuration manager cannot create force close service. |
29237 | 16 | Configuration manager cannot create expiration service. |
29239 | 16 | Configuration manager reconfiguration failed. |
29241 | 16 | Configuration manager initialization failed. |
29242 | 16 | Configuration manager activation failed. |
29243 | 16 | Configuration manager quiesce operation failed. |
29244 | 16 | Configuration manager release operation failed. |
29245 | 16 | Configuration manager cannot quiesce the agents. |
29246 | 16 | Configuration manager reconfiguration failed due to error %d, state %d, severity %d. |
29247 | 16 | Configuration manager error handler initialization failed due to error %d, state %d, severity %d. This is a serious error and brick will be taken down. Examine previously logged messages to figure out the cause for this fatal failure. |
29249 | 16 | Configuration manager broadcast channel shutdown crashed. |
29250 | 16 | Configuration manager cannot perform action %d on other bricks in the matrix due to error %d, state %d, severity %d. |
29251 | 16 | Configuration manager cannot create notification. |
29252 | 16 | Configuration manager cannot create brick down event for unregistered brick <%d> |
29253 | 16 | Configuration manager cannot perform channel distribution (Reason: %d, Loc: %d) |
29254 | 16 | Configuration manager cannot activate the agents. |
29255 | 16 | Configuration manager cannot send reconfig event. |
29256 | 16 | Configuration manager cannot retire old channel maps (Loc: %d). |
29257 | 16 | Configuration manager cannot shutdown old channel maps (Loc: %d). |
29258 | 16 | Configuration manager cannot cannot deliver shutdown ack to leaving bricks. |
29260 | 16 | Configuration manager cannot set matrix state. |
29261 | 16 | Configuration manager detected an invalid matrix state. |
29262 | 16 | Configuration manager can only evict bricks from the manager brick. |
29263 | 16 | Configuration manager can only force close bricks from the manager brick. |
29264 | 16 | Configuration manager brick down notification failed. |
29265 | 16 | Configuration manager reconfig announce step failed. |
29266 | 16 | Configuration manager reconfig enable step failed. |
29267 | 16 | Configuration manager performed reconfig without membership change. |
29268 | 16 | Configuration manager reconfig retire step failed. |
29269 | 16 | Configuration manager cannot start non-registered manager %d. |
29270 | 10 | Configuration manager has started accepting enlistment requests |
29271 | 10 | Configuration manager has shutdown. |
29272 | 16 | Configuration manager enlistment denied join of brick <%d>. Machine architecture mismatch. Agent machine architecture <%X>, manager machine architecture <%X>. |
29273 | 16 | Error: cannot bump Configuration manager manager major version (Loc: %d). |
29274 | 16 | Component %s reported that the component %s in brick %d is in a suspicious state because of the error: %d, severity: %d, state: %d, description: ‘%s’. Additional description provided was: ‘%s’. This report will be sent to the configuration manager known to be on brick %d. |
29275 | 16 | Component %s from brick %d reported that the component %s in brick %d is in a suspicious state because of the error: %d, severity: %d, state: %d, description: ‘%s’. Additional description provided was: ‘%s’. |
29276 | 16 | Brick down message for brick %d enqueued due to fatal error reported for component %s by component %s in brick %d. Fatal error reported is error code: %d, severity: %d, state: %d, description: ‘%s’. Additional description provided was: ‘%s’. |
29277 | 16 | Configuration manager enlistment is queuing a failure request for brick <%d> due to receiving new enlistment request from this brick. |
29278 | 16 | Configuration manager is evicting brick <%d> from which it did not receive expected reply during communication. This also includes brick not responding within timeout. |
29279 | 16 | Configuration manager could not read metadata necessary for its operation from the master database. |
29280 | 16 | Configuration manager is performing ‘%s’ ‘%s’ operation on all online bricks. |
29281 | 16 | Configuration manager is performing ‘%s’ ‘%s’ operation on brick <%lu>. |
29282 | 16 | Configuration manager cannot ‘%s’ ‘%s’. Examine previous logged messages to determine cause of this error. This is a fatal error affecting system functionality and brick <%lu> will be evicted. |
29283 | 16 | Configuration manager cannot initialize communication object. Examine previous logged messages to determine cause of this error. |
29284 | 16 | Configuration manager could not write the WMI offline configuration file. (Reason=%s). |
29285 | 16 | Configuration manager enlistment denied join of brick <%lu>. Supported number of bricks mismatch. Agent supported number of bricks <%lu>, manager supported number of bricks <%lu>. |
29286 | 10 | Brick <%lu> will be allowed to join matrix once its previous brick down reconfiguration is completed. |
29300 | 16 | The configuration file name %ls is invalid. |
29301 | 16 | Failed to open configuration file %ls. |
29302 | 16 | Configuration file %ls is empty. |
29303 | 16 | The configuration file %ls is corrupt. |
29304 | 16 | Cannot create brick configuration. |
29305 | 16 | The configuration property %s is corrupt. |
29306 | 16 | The configuration file name cannot be constructed. (Reason: %d). |
29307 | 16 | Cannot set the roster property %s. |
29308 | 16 | Local brick id <%d> does not match brick id <%d> in the resource database. |
29309 | 16 | Brick id has not been set. (Resource instance name: %s) |
29311 | 16 | An error occurred while trying to connect to a service control manager on machine %ls. Error returned: %d – %ls. |
29312 | 16 | An error occurred while trying to perform a service operation on service %ls on machine %ls. Error returned: %d – %ls. |
29314 | 16 | The service %ls on machine %ls failed to start in a timely fashion. Service specific error code %d. |
29315 | 16 | OS user does not have the required privileges to start the remote service on brick %d. |
29316 | 16 | The path name for the file matrix.xsd cannot be constructed. (Reason: %d). |
29317 | 16 | Communication involving configuration manager and agent is ignoring stale message from brick <%lu> to brick <%lu> due to ‘%s’ mismatch. Expected %I64u but received %I64u. |
29318 | 16 | Communication involving configuration manager and agent is unable to send message from brick <%lu> to brick <%lu> due to error %d, state %d, severity %d. |
29319 | 16 | Communication involving configuration manager and agent did not receive a valid reply from brick <%lu> |
29320 | 16 | Communication involving configuration manager and agent cannot be initialized due to error %d, state %d, severity %d. |
29321 | 16 | Communication involving configuration manager and agent received a failure response <0x%lx> from brick <%lu>. |
29400 | 16 | Synchronous write task failed due to inconsistent prism state. |
29401 | 16 | Prism operation failed due to error code %d. |
29402 | 16 | Synchronous write task was aborted. |
29501 | 16 | Data Virtualization Manager Agent not found. |
29601 | 16 | SM force closing channel to recover after errors |