SQL Server Error Messages 25001 to 30000

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

ErrorCodeSeverityErrorMessage
2500216The 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.
2500316Upgrade of the distribution database MSmerge_subscriptions table failed. Rerun the upgrade procedure in order to upgrade the distribution database.
2500516It is invalid to drop the default constraint on the rowguid column that is used by merge replication.
2500616The new column cannot be added to article ‘%s’ because it has more than %d replicated columns.
2500716Cannot 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.
2500816The merge replication views could not be regenerated after performing the data definition language (DDL) operation.
2500916Invalid value ‘%s’ specified while executing sp_changemergearticle on article ‘%s’ for the ‘identityrangemanagementoption’ property.
2501016The 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.
2501216Cannot add an identity column since the table is published for merge replication.
2501316Cannot 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.
2501416sp_repladdcolumn does not allow adding columns of datatypes that are new to this release.
2501510Schema Changes and Bulk Inserts
2501610Prepare Dynamic Snapshot
2501716Failed to execute the command “%s” through xp_cmdshell. Detailed error information is returned in a result set.
2501816Precomputed 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.
2501916The 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.
2502016The 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.
2502116Replication stored procedure sp_MSupdategenhistory failed to update the generation ‘%s’. This generation will be retried in the next merge.
2502216The snapshot storage option (@snapshot_storage_option) must be ‘file system’, or ‘database’.
2502316Stored procedures containing table-value parameters cannot be published as ‘[serializable] proc exec’ articles.
2502416A snapshot storage option of ‘database’ is incompatible with the use of character mode bcp for snapshot generation.
2502516Cannot add a sparse column or a sparse column set because the table is published for merge replication. Merge replication does not support sparse columns.
2502616The 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.
2502716Cannot 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.
2502816Cannot specify ‘database_name’ when ‘all’ is set to 1.
2502916Replication distribution database ‘%s’ is not in the primary replica of its availability group.
2503016Replication distribution database ‘%s’ is not in an availability group.
2503110Monitor and sync replication agent jobs
2503210Sync replication agent jobs and their enabled states.
2503316The distribution database is part of an availability group without a listener. Add a listener to the availability group before adding publication, subscription or distribution.
2503416Distribution database in availability group is only supported for publisher_type as MSSQLSERVER.
2503516When distribution database is part of availability group, then distributor and publisher server cannot be same.
2503616Distribution database needs to be in readable state on secondary replica, when distribution database is part of availability group.
2503716The @subscriber parameter must be either @@SERVERNAME or listener name of the availability group that the subscriber database is part of.
2503816User needs to have VIEW SERVER STATE permission to assign @subscriber as the listener name of the availability group.
2503916Assigning listener name for @subscriber parameter is not a supported scenario for Managed Instance.
2504016Assigning the default value to “%ls”: %ls.
2560117The Extended Event engine is out of memory.
2560217The %S_MSG, “%.*ls”, encountered a configuration error during initialization. Object cannot be added to the event session. %ls
2560317The %S_MSG, “%.*ls”, could not be added.  The maximum number of singleton targets has been reached.
2560417The Extended Event engine is disabled.
2560517The %S_MSG, “%.*ls”, could not be added. The maximum number of packages has been reached.
2560617The 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.
2560717The Extended Event engine has been disabled by startup options.  Features that depend on Extended Events may fail to start.
2560817The Extended Event engine could not allocate record for local thread/fiber.
2562316The %S_MSG name, “%.*ls”, is invalid, or the object could not be found
2562416The 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.
2562516The %S_MSG, “%.*ls”, already exists in the event session. Object cannot be added to the event session.
2562616The %S_MSG, “%.*ls”, was specified multiple times.
2562916For %S_MSG, “%.*ls”, the customizable attribute, “%ls”, does not exist.
2563016The predicate expression bound to %S_MSG ,”%.*ls”, has mismatching types.
2563116The %S_MSG, “%.*ls”, already exists.  Choose a unique name for the event session.
2563216The specified buffer size is less than the minimum size. The minimum allowed size is %d bytes.
2563316The buffer size specified exceeds the maximum size.
2563416The dispatch latency specified is below the minimum size.
2563516An 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.
2563616Source and comparator types of the predicate do not match.
2563916The %S_MSG, “%.*ls”, exceeds the number of allowable bound actions.
2564016Maximum event size is smaller than configured event session memory. Specify a larger value for maximum event size, or specify 0.
2564116For %S_MSG, “%.*ls”, the parameter “%ls” passed is invalid. %ls
2564216Mandatory customizable attributes are missing for %S_MSG, “%.*ls”.
2564316The %S_MSG, “%.*ls”, can not be added to an event session that specifies no event loss.
2564416The %S_MSG, “%.*ls”, cannot be bound to the event session.
2564616The %S_MSG name, “%.*ls”, is invalid.
2564716The %S_MSG, “%.*ls”, could not be found. Ensure that the object exists and the name is spelled correctly.
2564816The %S_MSG, “%.*ls”, could not be found. Ensure that the package exists and the name is spelled correctly.
2564916Two of the actions/predicates for %S_MSG, “%.*ls”, can not coexist.  Please remove one.
2565016For %S_MSG, “%.*ls” the customizable attribute, “%ls”, was specified multiple times.
2565116For %S_MSG, “%.*ls”, the value specified for customizable attribute, “%ls”, did not match the expected type, “%ls”.
2565316The %S_MSG, “%.*ls”, does not exist in the event session. Object cannot be dropped from the event session.
2565416Insuficient buffer space to copy error message.
2565516Internal Extended Event error: invalid message code.
2565616Error validating action. %ls
2565716Error validating predicate. %ls
2565816The %S_MSG name “%.*ls” is not unique.
2565917The %S_MSG, “%.*ls”, encountered a configuration error during initialization. The customizable attribute %ls is used internally only.
2566416Internal Extended Event error: invalid package ID.
2569917The Extended Event engine failed unexpectedly while performing an operation.
2570115Invalid event session name “%.*ls”. Temporary event sessions are not allowed.
2570216The event session option, “%.*ls”, is set more than once. Remove the duplicate session option and re-issue the statement.
2570316The event session option, “%.*ls”, has an invalid value. Correct the value and re-issue the statement.
2570416The event session has already been stopped.
2570516The event session has already been started.
2570616The %S_MSG, “%.*ls”, could not be found.
2570716Event session option “%.*ls” cannot be changed while the session is running. Stop the event session before changing this session option.
2570816The “%.*ls” specified exceeds the maximum allowed value. Specify a smaller configuration value.
2570916One or more event sessions failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
2571016Event session “%.*ls” failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
2571116Failed to parse an event predicate.
2571216An invalid comparison operator was specified for an event predicate.
2571316The value specified for %S_MSG, “%.*ls”, %S_MSG, “%.*ls”, is invalid.
2571516The predicate on event “%ls” is invalid.  Operator ‘%ls’ is not defined for type “%ls”, %S_MSG: “%.*ls”.
2571616The predicate on event, “%.*ls”, exceeds the maximum length of %d characters.
2571716The operating system returned error %ls while reading from the file ‘%s’.
2571816The log file name “%s” is invalid.  Verify that the file exists and that the SQL Server service account has access to it.
2571916Initial file name and initial offset must be specified as a pair. Please correct the parameters and retry your query.
2572010‘sys.fn_xe_file_target_read_file’ is skipping records from “%.*ls” at offset %I64d.
2572116The metadata file name “%s” is invalid. Verify that the file exists and that the SQL Server service account has access to it.
2572216The offset %I64d is invalid for log file “%s”.  Specify an offset that exists in the log file and retry your query.
2572316An error occurred while obtaining metadata information from the file “%s”. The file may be damaged.
2572416Predicate too large for display.
2572516An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
2572617The 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.
2572716The Extended Events session named “%.*ls” has either been stopped or dropped and can no longer be accessed.
2572816The Extended Events session named “%.*ls” could not be found. Make sure the session exists and is started.
2572917The event data stream was disconnected due to an internal error.
2573010The 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.
2573116Execution 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.
2573216One 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.
2573316Event 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.
2573416The file pattern “%s” represents a full path.  Use only relative paths with no drive letters.
2573516The source option %d is invalid.
2573616A damaged buffer was found in file “%s” at offset %I64d, no further events will be read from the file.
2573716Database scoped extended event sessions are not available in server scope or system databases in Azure DB.
2573816Event session ‘%.*ls’ could not be started because system is currently busy. Please try again later.
2573916Failed to start event session ‘%.*ls’ because required credential for writing session output to Azure blob is missing.
2574016Unable to start event session ‘%.*ls’ because system is busy. Please try again later.
2574116The URL specified for %S_MSG “%.*ls”, %S_MSG “%.*ls” is invalid. URL must begin with ‘https://’ .
2574216Target ‘%.*ls’ is not available for Azure SQL Database.
2574316The event ‘%.*ls’ is not available for Azure SQL Database.
2574416The action ‘%.*ls’ is not available for Azure SQL Database.
2574516Unable to retrieve Azure SQL Database telemetry data.
2574616Operation 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.
2574716Operation 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.
2574816The file “%s” contains audit logs. Audit logs can only be accessed by using the fn_get_audit_file function.
2601010The 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.
2601116The 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.
2601216The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support.
2601310The certificate [Cert Hash(sha1) “%hs”] was successfully loaded for encryption.
2601416Unable 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.
2601516Unable 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.
2601710Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2601810A self-generated certificate was successfully loaded for encryption.
2602210Server is listening on [ %s <%s> %d].
2602316Server TCP provider failed to listen on [ %s <%s> %d]. Tcp port is already in use.
2602416Server failed to listen on %s <%s> %d. Error: %#x. To proceed, notify your system administrator.
2602510HTTP authentication succeeded for user ‘%.*ls’.%.*ls
2602614HTTP authentication failed.%.*ls
2602810Server named pipe provider is ready to accept connection on [ %s ].
2602916Server named pipe provider failed to listen on [ %s ]. Error: %#x
2603410The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections.  It will proceed with immediate termination.
2603516The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x.
2603710The 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.
2603810The 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.
2603916The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.
2604017Server 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.
2604110Server TCP provider has successfully reestablished listening on port [ %d ].
2604217Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
2604310Server HTTP provider has successfully reestablished listening.
2604417Server named pipe provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
2604510Server named pipe provider has successfully reestablished listening on [ %s ].
2604810Server local connection provider is ready to accept connection on [ %s ].
2604916Server local connection provider failed to listen on [ %s ]. Error: %#x
2605017Server 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.
2605110Server local connection provider has successfully re-established listening on [ %s ].
2605210SQL 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.
2605316SQL 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.
2605416Could 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.
2605610Failed 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.
2605716Failed 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.
2605816A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.
2605910The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
2606010The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
2606110Failed 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.
2606216Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.
2606410SQL 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.
2606516Extended 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.
2606616An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Integrated Authentication might fail. Error: %d.
2606710The 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.
2606810The 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.
2606910Started listening on virtual network name ‘%ls’. No user action is required.
2607010Stopped listening on virtual network name ‘%ls’. No user action is required.
2607116Failed to load the Cluster Resource Libraries: clusapi.dll and resutils.dll. SQL Server will be unable to accept TCP connections on clustered listeners.
2607210Found 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.
2607316Failed to clean up event associated with TCP connection, this is most likely because the server was under heavy load. Operating system return code: %#x
2607516Failed to start a listener for virtual network name ‘%ls’. Error: %d.
2607610SQL 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.
2607720An asynchronous read has timed out
2607820Client disconnected during login
2607917Server 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.
2700116Reserved error message.  Should never be issued.
2700216A null or invalid SqlCommand object was supplied to Fuzzy Lookup Table Maintenance by SQLCLR. Reset the connection.
2700316Bad token encountered during tokenization.
2700416Unexpected token type encountered during tokenization.
2700516Error Tolerant Index is corrupt.
2700616Deleted more than one rid from ridlist during delete operation.  Error Tolerant Index is corrupt.
2700716Attempt to delete from empty ridlist.  Error Tolerant Index is corrupt.
2700816rid to be deleted not found in rid-list.  Error Tolerant Index is corrupt.
2700916Error Tolerant Index frequencies must be non-negative.  Error Tolerant Index is corrupt.
2701016Attempt to insert row whose ID is already present.  Error Tolerant Index is corrupt.
2701116No ridlist provided for appending.  Error Tolerant Index is corrupt.
2701216Cannot delete token.  Error Tolerant Index is corrupt.
2701316Tokenizer object has no delimiter set.  Error Tolerant Index is corrupt.
2701416Deletion failed because token does not occur in index.  Error Tolerant Index is corrupt.
2701516Unexpected ridlist length.  Error Tolerant Index is corrupt.
2701616Cannot connect to Error Tolerant Index.  Bad or missing SqlCommand object.
2701716Failed to drop index on reference table copy.
2701816Could not retrieve metadata from Error Tolerant Index.  The index is probably corrupt.
2701916Could not initialize from metadata contained in Error Tolerant Index.  The index is probably corrupt.
2702216An error specific to fuzzy lookup table maintenance has occurred.
2702316A system error occurred during execution of fuzzy lookup table maintenance.
2702416Cannot write at negative index position.  Could not update Error Tolerant Index.  The index is probably corrupt.
2702516Argument is not a valid hex string.  Could not initialize from metadata contained in Error Tolerant Index.  The index is probably corrupt.
2702616Negative count in Error Tolerant Index metadata.  The index is probably corrupt.
2702716Error tolerant index metadata contains unsupported normalization flags.  The index is probably corrupt.
2702816Invalid Error Tolerant Index metadata.  The index is probably corrupt.
2702916Invalid Error Tolerant Index metadata version.
2703016Missing metadata.  The Error Tolerant Index is probably corrupt.
2703116Unable to parse token counts in Error Tolerant Index metadata.  The index is probably corrupt.
2703216Error Tolerant Index Metadata string too long.  Index is probably corrupt.
2703316Error Tolerant Index Metadata length limit exceeded.
2703416Unexpected end of Error Tolerant Index metadata.  Index is probably corrupt.
2703716No table name provided for Error Tolerant Index.  The index is probably corrupt.
2703816No input provided for decoding in Error Tolerant Index metadata.  Index is probably corrupt.
2703916No input provided for encoding in Error Tolerant Index metadata.  Index is probably corrupt.
2704016No Error Tolerant Index metadata string provided for initialization.  Index is probably corrupt.
2704116No Error Tolerant Index metadata provided for serialization.  The index is probably corrupt.
2704216Could not lookup object_id.  No object name provided.
2704316Could not lookup object_id.  Null command object provided.
2704416Open connection required.  Cannot query Error Tolerant Index.
2704516Cannot write to null output buffer.  Could not update Error Tolerant Index.  The index is probably corrupt.
2704616Output buffer provided is too small.  Could not update Error Tolerant Index.  The index is probably corrupt.
2704716The number of min-hash q-grams per token must be positive.
2704816Could not create index on reference table copy.
2704916Reference table (or internal copy) missing integer identity column.  Error tolerant index is probably corrupt.
2705016The maximum allow integer identity value has been reached.  Consider re-building the error tolerant index to use any gaps in sequence.
2705116Could not read rid from data provided (missing column name, null reader object, or corrupted data).  The index is probably corrupted.
2705216Table maintenance insertion failed.
2705316A positive q-gram length is required for tokenization.
2705416Maintenance trigger already installed on this reference table.
2705516Missing extended property on maintenance trigger.
2705616Maintenance trigger name out of sync with Error Tolerant Index metadata.  Index is probably corrupt.
2705816A SQL error occurred during execution of fuzzy lookup table maintenance.
2705916Could not lookup object_id.  The reference table or maintenance trigger could not be found.
2706016The Error Tolerant Index table name provided is not a valid SQL identifier.
2706116The Error Tolerant Index table name provided refers to a missing table.  Check sys.tables.
2706216An auxiliary Fuzzy Lookup table maintenance table is missing.
2706316An auxiliary Fuzzy Lookup table maintenance table name is null.  Maintenance cannot proceed.
2706416The row deleted from the reference table could not be located in the reference table copy.
2706516Fuzzy Lookup Table Maintenance is not installed or the Error Tolerant Index is corrupt.
2710016The input parameter, ‘%ls’, cannot be null. Provide a valid value for this parameter.
2710116The value specified for the input parameter, ‘%ls’, is not valid. Provide a valid value for this parameter.
2710216The input parameter, ‘%ls’, cannot be empty. Provide a valid value for this parameter.
2710316Cannot find the execution instance ‘%I64d’ because it does not exist or you do not have sufficient permissions.
2710416Cannot find the folder ‘%ls’ because it does not exist or you do not have sufficient permissions.
2710516Cannot find the operation ‘%I64d’ because it does not exist or you do not have sufficient permissions.
2710616Cannot find the parameter ‘%ls’ because it does not exist.
2710716The specified %ls already exists.
2710816The path for ‘%ls’ cannot be found. The operation will now exit.
2710916Cannot find the project ‘%ls’ because it does not exist or you do not have sufficient permissions.
2711016Default permissions for the project cannot be granted to the user. Make sure that the user can be assigned these permissions.
2711116Cannot find the reference ‘%I64d’ because it is not part of the project or you do not have sufficient permissions.
2711216Unable to update the row in the table, ‘%ls’. Make sure that this row exists.
2711316Unable to delete one or more rows in the table, ‘%ls’. Make sure that these rows exist.
2711416Cannot find the reference ‘%I64d’ because it does not exist or you do not have sufficient permissions.
2711516Cannot find the target folder ‘%ls’ because it does not exist or you do not have sufficient permissions.
2711616Conversion failed while performing encryption.
2711716Failed to decrypt the project. The symmetric key that was used to encrypt it may have been deleted. Delete the project and deploy it again.
2711816Failed to deploy the project. Try again later.
2711916Failed to encrypt the project named ‘%ls’. The symmetric key may have been deleted. Delete the project and deploy it again.
2712016Failed to grant permission ‘%ls’.
2712116The project is currently running or has completed. An instance of execution can only be started once.
2712216Unable 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.
2712316The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Integrated Authentication.
2712416Integration Services server cannot stop the operation. The specified operation with ID ‘%I64d’ is not valid or is not running.
2712516Integration Services server cannot stop the operation. The specified operation is not in a consistent state and cannot be stopped.
2712616Integration Services server cannot stop the operation. The specified operation is already in Stopping state.
2712716The Integration Services catalog ‘%ls’ does not exists.
2712816The name ‘%ls’ is not valid. It consists of characters that are not allowed.
2712916The folder ‘%ls’ already exists or you have not been granted the appropriate permissions to change it.
2713016Integration Services server was unable to impersonate the caller. Operating system returned error code: %ls.
2713116Integration Services server was unable to start the process, ‘%ls’. Operating system returned error code: %ls.
2713216Integration Services server was unable to create process component, ‘%ls’. Operating system returned error code: %ls.
2713316Integration Services server was unable to wait for process, ‘%ls’, to finish. Operating system returned error code: %ls.
2713516The database, ‘%ls’, already exists. Rename or remove the existing database, and then run SQL Server Setup again.
2713616The required components for the 32-bit edition of Integration Services cannot be found.  Run SQL Server Setup to add the required components.
2713716The registry key for the system setting ‘%ls’ could not be found. The operation will now exit.
2713816The input parameter cannot be null. Provide a valid value for the parameter.
2713916Integration 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.
2714016The 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.
2714116Integration Services server cannot be configured because there are execution logs. Please cleanup all execution logs, and then try to configure the server again.
2714216‘%ls’ is not a valid environment name. It consists of characters that are not allowed.
2714316Cannot access the operation with ID, ‘%I64d’. Verify that the user has appropriate permissions.
2714516‘%ls’ is not a valid project name. It consists of characters that are not allowed.
2714616Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it.
2714716The data type of the input value is not compatible with the data type of the ‘%ls’.
2714816The data type of the parameter does not match the data type of the environment variable.
2714916Integration 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.
2715016The version of the project has changed since the instance of the execution has been created. Create a new execution instance and try again.
2715110The restore operation for project ‘%ls’ from version ‘%I64d’ has started.
2715210The restore operation for project ‘%ls’ to version ‘%I64d’ has completed.
2715316Default permissions for the operation cannot be granted to the user. Make sure that the user can be assigned these permissions.
2715416The @sensitive parameter is missing. This parameter is used to indicate if the parameter contains a sensitive value.
2715516Project restore has failed. You cannot restore a project having an object_version_lsn that is the same as the current project.
2715616The Integration Services server property, ‘%ls’, cannot be found. Check the name of the property and try again.
2715716The environment ‘%ls’ already exists or you have not been granted the appropriate permissions to create it.
2715816Error 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.
2715916Data type of the input value is not supported.
2716016The 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.
2716110Warning: the requested permission has already been granted to the user. The duplicate request will be ignored.
2716216The 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.
2716316The 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.
2716510Warning: 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.
2716616The 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.
2716716Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the environment variables with the ‘%ls’ algorithm.
2716816Failed to change the encryption algorithm to ‘%ls’. An error occurred while encrypting the parameter values using the ‘%ls’ algorithm.
2716916Failed to create a log entry for the requested operation.
2717016Failed to retrieve the project named ‘%ls’.
2717116The value specified is not valid. A value of data type ‘%ls’ is required.
2717216The certificate and symmetric key used to encrypt project ‘%ls’ does not exist or you do not have sufficient permissions.
2717316The environment variable ‘%ls’ already exists.
2717516The execution has already completed.
2717616The parameter ‘%ls’ does not exist or you do not have sufficient permissions.
2717716Environment names must be unique. There is already an environment named ‘%ls’.
2717816Unable to execute the project named ‘%ls’. You do not have sufficient permissions.
2717916The object version does not match the project id or you do not have sufficient permissions.
2718016%ls is not a valid environment variable name. It consists of characters that are not allowed.
2718116The project ‘%ls’ already exists or you have not been granted the appropriate permissions to access it.
2718216The environment ‘%s’ does not exist or you have not been granted the appropriate permissions to access it.
2718316The environment variable ‘%ls’ does not exist or you have not been granted the appropriate permissions to access it.
2718416In order to execute this package, you need to specify values for the required parameters.
2718516The validation record for ID ‘%I64d’ does not exist or you have not been granted the appropriate permissions to access it.
2718616One or more environment variables could not be found in the referenced environment.
2718716The project does not exist or you have not been granted the appropriate permissions to access it.
2718816Only members of the ssis_admin or sysadmin server roles can create, delete, or rename a catalog folder.
2718916Catalog folder name cannot be NULL or an empty string.
2719016The folder ‘%ls’ already exists or you have not been granted the appropriate permissions to create it.
2719116The ‘%d’ permission is not applicable to objects of type ‘%d’. Grant, deny, or revoke of this permission is not allowed.
2719216The caller has not been granted the MANAGEPERMISSION permission for the specified object.
2719316SQL Server %ls is required to install Integration Services. It cannot be installed on this version of SQL Server.
2719416Cannot find the project because it does not exist or you do not have sufficient permissions.
2719516The operation failed because the execution timed out.
2719616Failed to delete the folder ‘%ls’ because it is not empty. Only empty folders can be deleted.
2719716The specified %ls %ld does not exist.
2719816Failed to locate records for the specified operation (ID %I64d).
2719916%ls is not a valid folder name. It consists of characters that are not allowed.
2720016The project is missing the specified environment reference.
2720116Values are missing for required parameters in this package. Specify values in order to start the validation.
2720216This project is missing one or more environment references. In order to use environment variables, specify the corresponding environment reference identifier.
2720316Failed to deploy project. For more information, query the operation_messages view for the operation identifier ‘%I64d’.
2720416Failed to create environment reference. This project already has an reference to the specified environment.
2720516Some of the property values for this parameter are missing.
2720616Failed to deploy project to the folder ‘%ls’. You do not have sufficient permissions to deploy this project.
2720716Failed to locate one or more variables in the environment ‘%ls’.
2720816The environment reference ‘%I64d’ is not associated with the project.
2720916Failed to create environment to the folder ‘%ls’. You do not have sufficient permissions to create this environment.
2721016Conversion failed when converting the %ls to data type %ls.
2721216Data tap can only be added or removed when the execution status is created.
2721316The 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.
2721416The 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.
2721516The data tap ‘%I64d’ does not exist, or you do not have sufficient permissions to remove it. Provide a valid data tap ID.
2721616The number of rows must be a non-negative value. Specify a valid value.
2721716The logging level ‘%d’ is undefined. Provide one of the following logging levels: 0 (None), 1 (Basic), 2 (Performance), 3 (Verbose), 4 (RuntimeLineage), 100 (Customized).
2721816The Integration Services Server cannot find the running process for execution ID %I64d. Provide a valid execution ID.
2721916Caller does not have permissions to execute the stored procedure.
2722016SSISDB database does not exist. Create the SSISDB database.
2722116Unable 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.
2722216The required components for the 64-bit edition of Integration Services cannot be found.  Run SQL Server Setup to install the required components.
2722316Cannot move the project to folder ‘%ls’ due to insufficient permissions.
2722416The parameter value cannot be changed after the execution has been started.
2722516The property cannot be overridden after the execution has been started.
2722616The database principal has granted or denied permissions to catalog objects in the database and cannot be dropped.
2722716The server ‘%ls’ already exists.
2722816The server ‘%ls’ does not exists.
2722916Cannot find the SQL login ‘%ls’.
2723016Failed to deploy the packages. Try again later.
2723116Failed to deploy packages. For more information, query the operation_messages view for the operation identifier ‘%I64d’.
2723216Failed to create customized logging level ‘%ls’. You do not have sufficient permissions to create customized logging level.
2723316Customized logging level name cannot be NULL or an empty string.
2723416‘%ls’ is not a valid customized logging level name. It consists of characters that are not allowed.
2723516The customized logging level ‘%ls’ already exists.
2723616Failed to delete customized logging level ‘%ls’. You do not have sufficient permissions to delete customized logging level.
2723716The customized logging level ‘%ls’ does not exist.
2723816Failed to rename customized logging level ‘%ls’ with ‘%ls’. You do not have sufficient permissions to rename customized logging level.
2723916Failed to update customized logging level ‘%ls’. You do not have sufficient permissions to update customized logging level.
2724016The value can not be less than zero.
2724116Failed 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’.
2724216Cannot find the cluster execution job instance ‘%ls’ because it does not exist or you do not have sufficient permissions.
2724316Cannot find the cluster worker agent ‘%ls’ because it does not exist or you do not have sufficient permissions.
2724616Cannot find the cluster execution task instance ‘%ls’ because it does not exist or you do not have sufficient permissions.
2725116Cannot add a worker agent to execute the cluster job instance ‘%ls’ because the job is specified for all worker agents.
2725216The Integration Services cluster worker agent ‘%ls’ is disabled.
2725516The job id of the execution is null. Create a job for the execution first and try again.
2725616The event message does not exist.
2725716There is no active worker agent.
2725916Failed to enable worker agent because current SQL Server edition only support limited number of worker agents.
2726016Only members of sysadmin server roles can perform this action.
2726116There is no Scale Out Master installed.
2730316An 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.
2730816SegmentID %d from the archive does not match the segmentID %d from the specified filename on brick %d.
2780110Successfully initialize HPC environment from provider ‘%ld’, device type ‘%ld’ DLL version %ld, and find %ld device(s), %ld of them are used.
2780216Failed to initialize HPC environment.
2780310Message reported from (%.*s) device on device Id (%I64d), code : %d, message : %.*s .
2780416Query failed on HPC device Id (%I64d), with error code %d .
2800016The decrypted session key has an unexpected size.
2800116A 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.
2800216Cannot start service broker manager. Operating system error: %ls.
2800316An internal service broker error occurred. Operating system error: %ls.
2800416This message could not be delivered because the ‘%S_MSG’ action cannot be performed in the ‘%.*ls’ state.
2800516An exception occurred while enqueueing a message in the target queue. Error: %d, State: %d. %.*ls
2800614User 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.
2800716A 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.
2800816The conversation handle ‘{%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}’ is invalid.
2800916The crypto API has detected bad data while trying to perform a decryption operation.
2801016This 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.
2801116This message could not be delivered because its %S_MSG has expired or is invalid.
2801216The Service Broker in the target database is unavailable: ‘%S_MSG’.
2801316The service broker is administratively disabled.
2801416The database is in read-only mode.
2801516The database is in single-user mode.
2801616The message has been dropped because the service broker in the target database is unavailable: ‘%S_MSG’.
2801716The message has been dropped because the target service broker is unreachable.
2801816The database is a replica of a mirrored database.
2801916System error %d occurred while creating a new message element GUID for this forwarded message.
2802016Could not create user token for user %d in database %d.
2802116One or more messages could not be delivered to the local service targeted by this dialog.
2802210An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate is not yet valid.
2802310An error occurred while looking up the public key certificate associated with this SQL Server instance: The certificate has expired.
2802416The 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.
2802516The security certificate bound to database principal (Id: %i) has expired. Create or install a new certificate for the database principal.
2802610Connection handshake failed. Not enough memory available. State %d.
2802710Connection handshake failed. There is no compatible %S_MSG. State %d.
2802810Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State %d.
2802910Connection handshake failed. Unexpected event (%d) for current context (%d). State %d.
2803010Connection handshake failed. A call to the SQL Server Network Interface failed: (%x) %ls. State %d.
2803110Connection handshake failed. An OS call failed: (%x) %ls. State %d.
2803210A 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.
2803310A 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.
2803410Connection handshake failed. The login ‘%.*ls’ does not have CONNECT permission on the endpoint. State %d.
2803510Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
2803610Connection 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.
2803710Connection 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.
2803810Connection handshake failed. The handshake verification failed. State %d.
2803910Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.
2804010A corrupted message has been received. The adjacent error message header is invalid.
2804116A corrupted message has been received. The encrypted payload offset is invalid (%d).
2804216A corrupted message has been received. The arbitration request header is invalid.
2804316A corrupted message has been received. The arbitration response header is invalid.
2804416A 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.
2804510Connection 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.
2804610%S_MSG Login succeeded for user ‘%.*ls’. Authentication mode: %.*ls. %.*ls
2804710%S_MSG login attempt failed with error: ‘%.*ls’. %.*ls
2804810%S_MSG login attempt by user ‘%.*ls’ failed with error: ‘%.*ls’. %.*ls
2804916A corrupted message has been received. The proxy connect message header is invalid.
2805010The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
2805110Could not save a dialog session key. A master key is required in the database to save the session key.
2805216Cannot decrypt session key while regenerating master key with FORCE option.
2805316Service 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.
2805416Service 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.
2805516The 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.
2805616This 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’.
2805710Service Broker in database ‘%.*ls’ has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.
2805816Service Broker could not upgrade this conversation during a database upgrade operation.
2805916Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
2806016The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
2806116A corrupted message has been received. The adjacent message integrity check signature could not be validated.
2806216A corrupted message has been received. The signed dialog message header is invalid.
2806316A 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.
2806416A 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.
2806516A 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.
2806616A 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.
2806716A 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.
2806816A 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.
2806916Unexpected session key when encrypting a dialog message.
2807010Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
2807110The received message could not be forwarded onto another connection. State %d.
2807216A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.
2807316An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
2807416Service 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.
2807510The broker in the sender’s database is in single user mode. Messages cannot be delivered while in single user mode.
2807610Could not query the FIPS compliance mode flag from registry. Error %ls.
2807710%S_MSG endpoint is running in FIPS compliance mode. This is an informational message only. No user action is required.
2807810The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
2807910Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
2808010Connection handshake failed. The %S_MSG endpoint is not configured. State %d.
2808110Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
2808210Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
2808316The 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.
2808410An 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.
2808516The activated task was ended because the associated queue was dropped.
2808616The activated task was ended because either the queue or activation was disabled.
2808716The activated task was aborted because the invoked stored procedure ‘%ls’ did not execute RECEIVE.
2808816The 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.
2808916The 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.
2809016An 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.
2809110 Starting endpoint for %S_MSG with no authentication is not supported.
2809210Error updating proxy settings
2809810A 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.
2809910During 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.
2810116User ‘%.*ls\%.*ls’ does not have permission to debug the requested client connection.
2810216Batch execution is terminated because of debugger request.
2840116Feature or option ‘%ls’ is not available. Please consult Books Online for more information on this feature or option.
2840517During error handling, a second error was raised, causing an unrecoverable failure.
2850211The specified object Id is not valid.
2850311The specified index Id is not valid.
2850411The specified partition number is not valid.
2850611Incorrect number of keys was specified. Must specify at least first %d key columns
2855416Data Virtualization Manager not found.
2855510DVM failed to handle matrix reconfiguration. {error_code: %d, state: %d}
2860116The 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.
2860216The transaction is aborted because the transaction agent is shutting down.
2860310Transaction agent is shutting down because shutdown request was received from the manager.
2860410Transaction Coordination Manager is starting up. This is an informational message only. No user action is required.
2860510Transaction Coordination Manager is inactive. This is an informational message only. No user action is required.
2860610Transaction Coordination Manager is active with %016I64x as the starting AGE. This is an informational message only. No user action is required.
2860716TCM %.*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.
2860816Federated 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.
2860916Matrix transaction operation is not allowed because the transaction doesn’t allow forward progress, the transaction will be rolled back.
2861016Matrix 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.
2861220An error occurred while accessing Transaction Coordination Manager metadata. Could not persist AGE %016I64x.
2861310Transaction Coordination Agent is active. This is an informational message only. No user action is required.
2861416TCM 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.
2861520The request has performed an operation that is disallowed on a remote branch of a transaction
2870116Request aborted due to communication errors: an attempt was made to use channel %d.%d.%I64u in the closed state.
2870216Request aborted due to communication errors: incoming message format violation.
2870316Request aborted due to communication errors: no enabled channel maps for component %d found.
2870416Request aborted due to communication errors: unable to allocate new message for the brick %d. Error code %d.
2870516Request aborted due to communication errors: unable to complete send operation for the pipeline %hs. Error code %d.
2870610Next message reported have originated on brick %d.
2870720Brick was unable to communicate with configuration manager and will be disconnected. See previous errors for the details.
2870816Failure encountered due to Matrix configuration change: a brick was evicted.
2870916Dispatcher was unable to create new thread.
2871016Request aborted due to communication errors: pipeline %hs inconsistency detected: send side reported %I64d bytes sent but there were no messages received on other side.
2871116Request 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.
2871216Unable to start expiration manager dispatch thread. Result code %d.
2871316Communication subsystem failed to process user abort request. Error Number: %d; State: %d.
2871416Request aborted due to communication errors: an attempt was made to communicate with Brick %d which is no longer online or have been reconfigured.
2871510Execution of the request was aborted on remote brick.
2871616Request aborted due to communication errors: too many concurrent operations.
2871716Request aborted due to communication errors: communication subsystem is shutting down or initialization not complete yet.
2871816Request aborted due to communication errors: pipeline %hs received message (classId %d, sequenceId %d) from the expired age %d (last acceptable age %d).
2871916Request aborted due to Fabric errors: unable to enqueue a task for workspace 0x%I64x.
2872016Mci subsystem failed to start with error %d.
2872116Mci subsystem failed to start channel %d with error %d
2872220Force 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.
2872316Brick was shutdown by administrator request
2872416Channel close verification
2872520Unable to process cancellation request due to resource availability. Retrying…
2872620Unable to process activation data for a workspace.
2872720Unable to process incoming message due to resource availability.
2872816Request aborted due to communication errors: no channel maps of version %d for component %d found to create channel %I64u.
2872916Request aborted due to communication errors: a message have arrived for non-activated channel %I64u.
2890316Configuration manager agent enlistment is retrying enlistment since brick <%d> eviction is pending.
2890416Configuration manager agent enlistment is sending join request message to manager.
2890516Configuration manager agent enlistment failed to receive reply from manager. See previous errors in error log.
2890616Configuration manager agent enlistment completed with ‘%s’.
2890716Configuration manager agent enlistment stopped.
2890816Configuration manager agent enlistment failed due to different enlistment protocol versions between manager and agent. Version received from manager: <%d>, Version expected: <%d>.
2890916Configuration manager agent enlistment failed due to receiving reply from invalid manager brick id <%d> .
2891110Configuration manager agent enlistment succeeded. Manager accepted brick <%d> join request.
2891216Brick <%d> enlistment with configuration manager failed due to ‘%s’ mismatch. Brick will be taken down.
2891316Configuration 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.
2891410Configuration manager agent enlistment: Brick <%d>, state <%d>.
2891516Configuration 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.
2891616Configuration manager agent encountered error %d, state %d, severity %d while updating state information. Examine previous logged messages to determine cause of this error.
2891710Configuration manager agent enlistment received join reply message.
2891916Duplicate brick id <%d> detected in configuration file.
2892016Configuration manager agent cannot send reported error to configuration manager due to error %d, state %d, severity %d.
2892116No configuration file specified.
2892216Configuration 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.
2892316Configuration manager agent initialization failed. See previous errors in error log. This is a serious error condition and brick will be taken down.
2892416Configuration manager agent activation failed.
2892916Configuration manager agent cannot commit new roster.
2893116Configuration manager agent roster is corrupt.
2893216Configuration manager agent did not receive a shutdown channel map.
2893316Configuration manager agent could not perform brick down notification.
2893416Configuration manager agent could not perform brick up notification.
2893516Configuration manager agent is trying to start non-existing agent %d.
2893616Configuration manager agent start failed (Loc: %d).
2893716Configuration manager agent stop failed.
2893810Configuration manager agent has started.
2893910Configuration manager agent has shutdown.
2894016Configuration manager agent could not delete stale MCI sessions.
2894216Error reading configuration file. (Reason=%d).
2894316Error reading configuration file. Column %s not defined.
2894416Error reading configuration file. Host name or instance name cannot be empty (Reason: %d).
2894516Error reading configuration file. Invalid contents. (Reason=%d).
2894616Error reading matrix.xsd schema configuration file. (Reason=%d).
2894716Error reading configuration file. (line:%d, column:%d, Reason=%s).
2894816Error reading configuration file. Invalid placement brick id.
2894916Error during configuration check (Function:%s, result: 0x%08lx).
2895016Configuration manager agent cannot store metadata.
2895116Cannot update roster, brick id %d not part of roster.
2895216Configuration manager cannot initialize agent %d.
2895316Matrix agent %d has the invalid state %d.
2895516Cannot create roster memento.
2895816Error copying configuration. (Reason=%s).
2895916Cannot commit metadata change for brick id %d.
2896016Error: Cannot read <%s> node of configuration file.
2896116Error: invalid configuration file, no bricks defined.
2896216Error: Invalid value for manager name %s specified.
2896316Error: Invalid value for manager role %s specified.
2896416Error: Cannot create dom object for writing of XML configuration file (Reason %d).
2896810Starting communication infrastructure for communication between configuration manager and agent
2896910Configuration manager agent shutting down…
2897016Error: cannot update matrix metadata (Loc: %d).
2897216Error: cannot determine host name.
2897316Configuration manager agent cannot create notification publisher.
2897416Configuration manager agent cannot create notification service.
2897516Brick not configured correctly, corrupt configuration file.
2897616Configuration manager agent is ignoring stale message from manager brick %d due to ‘%s’ mismatch. Expected %I64u but received %I64u
2897716Configuration manager agent is performing ‘%s’ ‘%s’ operation.
2897816Configuration 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.
2897916Configuration manager agent cannot ‘%s’ ‘%s’ due to invalid state ‘%s’. This is a fatal error affecting system functionality and brick will be taken down.
2898016Error writing brick simulator state file. (Reason=%s).
2900116To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
2900316Invalid parameter combinations.
2900416Unknown property specified: %s.
2910316TCMA is shutting down since it encountered fatal error %d, state %d, severity %d
2910416Failure in channel announce
2910516Failure in channel enable
2920117Configuration manager enlistment can not initialize communication service to receive enlistment requests
2920216Configuration manager enlistment is ignoring message from brick <%d>. Enlistment protocol version mismatch. Agent version <%X>, manager version <%X>.
2920316Configuration manager enlistment denied join of brick <%d>.
2920416Configuration manager enlistment denied join of brick <%d>. Server default collation mismatch. Agent collation <%lu>, manager collation <%lu>.
2920516Configuration manager enlistment denied join of brick <%d>. SQL version or build number mismatch. Agent version <%X>, manager version <%X>.
2920616Configuration manager enlistment is ignoring messages from brick <%d> since message queue does not exist.
2920716Configuration manager enlistment is ignoring stale message from brick %d due to ‘%s’ mismatch. Expected %I64u but received %I64u
2920816Cannot commit metadata change ‘%s’ for brick id %d.
2920916Configuration 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.
2921016Configuration 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.
2921116Configuration manager enlistment is ignoring request from invalid brick id <%d>.
2921216Configuration 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.
2921510Configuration manager enlistment acknowledges brick join request. Brick <%d> joined matrix.
2921710Configuration manager enlistment received a new enlistment message.
2921810Configuration manager enlistment state machine: Brick <%d>, state <%d>
2921910Reserved brick <%d> is now marked active
2922010Configuration manager enlistment started.
2922110Configuration manager enlistment stopped.
2922216Configuration manager enlistment did not receive enlistment messages
2922317Configuration manager enlistment ran out of memory. Enlistment messages ignored.
2922410Configuration manager enlistment sent reply to brick <%d>.
2922510Configuration manager enlistment received join message from brick <%d>
2922717Thread creation failed. (RC=%d).
2922810Matrix transitioned from state %d to state %d.
2922910Brick transitioned from state %d to state %d.
2923010Manager transitioned from state %d to state %d.
2923110Matrix transitioned from state %d to state %d.
2923216Cannot create configuration manager enlistment thread.
2923316Configuration 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.
2923416Configuration manager initialization failed. (Reason=%s).
2923516Configuration manager cannot create channel distribution service.
2923616Configuration manager cannot create force close service.
2923716Configuration manager cannot create expiration service.
2923916Configuration manager reconfiguration failed.
2924116Configuration manager initialization failed.
2924216Configuration manager activation failed.
2924316Configuration manager quiesce operation failed.
2924416Configuration manager release operation failed.
2924516Configuration manager cannot quiesce the agents.
2924616Configuration manager reconfiguration failed due to error %d, state %d, severity %d.
2924716Configuration 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.
2924916Configuration manager broadcast channel shutdown crashed.
2925016Configuration manager cannot perform action %d on other bricks in the matrix due to error %d, state %d, severity %d.
2925116Configuration manager cannot create notification.
2925216Configuration manager cannot create brick down event for unregistered brick <%d>
2925316Configuration manager cannot perform channel distribution (Reason: %d, Loc: %d)
2925416Configuration manager cannot activate the agents.
2925516Configuration manager cannot send reconfig event.
2925616Configuration manager cannot retire old channel maps (Loc: %d).
2925716Configuration manager cannot shutdown old channel maps (Loc: %d).
2925816Configuration manager cannot cannot deliver shutdown ack to leaving bricks.
2926016Configuration manager cannot set matrix state.
2926116Configuration manager detected an invalid matrix state.
2926216Configuration manager can only evict bricks from the manager brick.
2926316Configuration manager can only force close bricks from the manager brick.
2926416Configuration manager brick down notification failed.
2926516Configuration manager reconfig announce step failed.
2926616Configuration manager reconfig enable step failed.
2926716Configuration manager performed reconfig without membership change.
2926816Configuration manager reconfig retire step failed.
2926916Configuration manager cannot start non-registered manager %d.
2927010Configuration manager has started accepting enlistment requests
2927110Configuration manager has shutdown.
2927216Configuration manager enlistment denied join of brick <%d>. Machine architecture mismatch. Agent machine architecture <%X>, manager machine architecture <%X>.
2927316Error: cannot bump Configuration manager manager major version (Loc: %d).
2927416Component %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.
2927516Component %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’.
2927616Brick 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’.
2927716Configuration manager enlistment is queuing a failure request for brick <%d> due to receiving new enlistment request from this brick.
2927816Configuration manager is evicting brick <%d> from which it did not receive expected reply during communication. This also includes brick not responding within timeout.
2927916Configuration manager could not read metadata necessary for its operation from the master database.
2928016Configuration manager is performing ‘%s’ ‘%s’ operation on all online bricks.
2928116Configuration manager is performing ‘%s’ ‘%s’ operation on brick <%lu>.
2928216Configuration 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.
2928316Configuration manager cannot initialize communication object. Examine previous logged messages to determine cause of this error.
2928416Configuration manager could not write the WMI offline configuration file. (Reason=%s).
2928516Configuration manager enlistment denied join of brick <%lu>. Supported number of bricks mismatch. Agent supported number of bricks <%lu>, manager supported number of bricks <%lu>.
2928610Brick <%lu> will be allowed to join matrix once its previous brick down reconfiguration is completed.
2930016The configuration file name %ls is invalid.
2930116Failed to open configuration file %ls.
2930216Configuration file %ls is empty.
2930316The configuration file %ls is corrupt.
2930416Cannot create brick configuration.
2930516The configuration property %s is corrupt.
2930616The configuration file name cannot be constructed. (Reason: %d).
2930716Cannot set the roster property %s.
2930816Local brick id <%d> does not match brick id <%d> in the resource database.
2930916Brick id has not been set. (Resource instance name: %s)
2931116An error occurred while trying to connect to a service control manager on machine %ls.  Error returned: %d – %ls.
2931216An error occurred while trying to perform a service operation on service %ls on machine %ls.  Error returned: %d – %ls.
2931416The service %ls on machine %ls failed to start in a timely fashion. Service specific error code %d.
2931516OS user does not have the required privileges to start the remote service on brick %d.
2931616The path name for the file matrix.xsd cannot be constructed. (Reason: %d).
2931716Communication involving configuration manager and agent is ignoring stale message from brick <%lu> to brick <%lu> due to ‘%s’ mismatch. Expected %I64u but received %I64u.
2931816Communication involving configuration manager and agent is unable to send message from brick <%lu> to brick <%lu> due to error %d, state %d, severity %d.
2931916Communication involving configuration manager and agent did not receive a valid reply from brick <%lu>
2932016Communication involving configuration manager and agent cannot be initialized due to error %d, state %d, severity %d.
2932116Communication involving configuration manager and agent received a failure response <0x%lx> from brick <%lu>.
2940016Synchronous write task failed due to inconsistent prism state.
2940116Prism operation failed due to error code %d.
2940216Synchronous write task was aborted.
2950116Data Virtualization Manager Agent not found.
2960116SM force closing channel to recover after errors