SQL Server Error Messages 19001 to 25000

In this post, we’ll list out the SQL Server Error Messages from the error codes 19001 to 25000 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 19001 to 25000

ErrorCodeSeverityErrorMessage
1903010SQL Trace ID %d was started by login “%s”.
1903110SQL Trace stopped. Trace ID = ‘%d’. Login Name = ‘%s’.
1903210SQL Trace was stopped due to server shutdown. Trace ID = ‘%d’. This is an informational message only; no user action is required.
1903310Server started with ‘-f’ option. Auditing will not be started. This is an informational message only; no user action is required.
1903421Cannot start C2 audit trace. SQL Server is shutting down.  Error = %ls
1903516OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured.
1903610The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.
1904916File ‘%.*ls’ either does not exist or there was an error opening the file. Error = ‘%ls’.
1905016Trace file name ‘%.*ls’ is invalid.
1905116Unknown error occurred in the trace.
1905216The active trace must be stopped before modification.
1905316The trace event ID is not valid.
1905416The trace column ID is not valid.
1905516Filters with the same event column ID must be grouped together.
1905616The comparison operator in the filter is not valid.
1905716The boolean operator in the filter is not valid.
1905816The trace status is not valid.
1905916Could not find the requested trace.
1906016The trace option is not valid.
1906116Cannot remove SPID trace column.
1906216Could not create a trace file.
1906316Not enough memory was available for trace.
1906416The requested trace stop time has been already passed.
1906516The parameter is not valid.
1906616Cannot modify a restricted trace.
1906716Cannot create a new trace because the trace file path is found in the existing traces.
1906816The trace file path is not valid or not supported.
1906916The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover option is enabled.
1907016The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
1907116Stopping the trace because the current trace file is full and the rollover option is not specified.
1909616Fail to delete an old trace file ‘%ls’. Error = ‘%ls’.
1909710Operating system error occurred while running %s. Error = %s.
1909816An error occurred starting the default trace. Cause: %ls  Use sp_configure to turn off and then turn on the ‘default trace enabled’ advanced server configuration option.
1909916Trace ID ‘%d’ was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.
1910010Initialization succeeded.
1910110Initialization failed with an infrastructure error. Check for previous errors.
1910210Unable to create a node listener object. Check for memory-related errors.
1910310An error occurred while starting shared memory support.
1910410All protocols are disabled.
1910510Unable to create a node listener object for a special instance. Check for memory-related errors.
1910610Unable to trim spaces in an IP address. Check TCP/IP protocol settings.
1910710‘TcpKeepAlive’ registry setting is the wrong type. Check TCP/IP protocol settings.
1910810Unable to retrieve ‘TcpKeepAlive’ registry setting. Check TCP/IP protocol settings.
1910910Unable to configure MDAC-compatibility TCP/IP port in registry.
1911010Unable to initialize the TCP/IP listener.
1911110Unable to open TCP/IP protocol configuration key in registry.
1911210Unable to retrieve TCP/IP protocol ‘Enabled’ registry setting.
1911310Unable to retrieve ‘ListenOnAllIPs’ TCP/IP registry setting.
1911410Unable to open TCP/IP protocol’s ‘IPAll’ configuration key in registry.
1911510Unable to retrieve registry settings from TCP/IP protocol’s ‘IPAll’ configuration key.
1911610Unable to obtain list size for IP addresses configured for listening in registry.
1911710Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors.
1911810Unable to obtain list of IP addresses configured for listening in registry.
1911910Unable to open TCP/IP protocol’s registry key for a specific IP address.
1912010Unable to retrieve ‘Enabled’ setting for a specific IP address.
1912110Unable to retrieve ‘Active’ setting for a specific IP address.
1912210Unable to retrieve ‘IpAddress’ value for a specific IP address.
1912310‘IpAddress’ registry value is the wrong type.
1912410Unable to retrieve registry settings for a specific IP address.
1912510Unable to deallocate structures representing registry key for a specific IP address.
1912610Unable to retrieve registry settings for cluster environment.
1912710Server is configured to listen on a specific IP address in a cluster environment.
1912810The SQL Server Network Interface cannot check for a duplicate IP address in the SQL Server TCP listening settings.
1912910The SQL Server Network Interface found a duplicate IP address in the SQL Server TCP listening settings.  Remove the duplicate IP address by using SQL Server Configuration Manager.
1913010Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings.
1913110Unable to open Dedicated Administrator Connection configuration key in registry.
1913210Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry.
1913310Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection.
1913410No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings.
1913510Error starting Named Pipes support. Check protocol settings.
1913710Failed to allocate memory for SSL listening structures. Check for memory-related errors.
1913810An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager.
1913910Unable to add listener endpoints. Check for memory-related errors.
1914010Unable to initialize the communication listeners.
1914110Unable to retrieve SQL Server Network Interface library settings for a special instance.
1914210Unable to retrieve SQL Server Network Interface library settings; the instance name is too long.
1914310Unable to initialize the Shared Memory listener.
1914410Unable to initialize the Named Pipes listener.
1914510Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry.
1914710Unable to initialize the HTTP listener.
1914810Unable to initialize SSL support.
1914910Unable to configure MDAC-compatibility protocol list in registry.
1915010Unable to open SQL Server Network Interface library configuration key in registry.
1915110An error occurred while obtaining the Extended Protection setting. Check Network Configuration settings in SQL Server Configuration Manager.
1915210The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
1915310An error occurred while obtaining the Accepted SPNs list for Extended Protection. Check Network Configuration settings in SQL Server Configuration Manager.
1915410The configured value for the Accepted SPNs list is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
1915510TDSSNIClient failed to allocate memory while loading Extended Protection configuration settings. Check for memory-related errors.
1915610Failed to allocate memory for SSPI listening structures. Check for memory-related errors.
1915710Unable to initialize the SSPI listener.
1915810Unable to create connectivity Ring Buffer. Check for memory-related errors.
1915910Unable to open ‘Named Pipes’ configuration key for Dedicated Administrator Connection in registry.
1916010Unable to retrieve ‘Enabled’ registry settings for Named-Pipe Dedicated Administrator Connection.
1916110No protocol is enabled for the Dedicated Administrator Connection.
1916210Unable to retrieve ‘PipeName’ registry settings for Named-Pipe Dedicated Administrator Connection.
1916310Error starting Named Pipes support for Dedicated Administrator Connection.
1916410Unable to retrieve ‘GroupName’ registry settings for Named-Pipe Dedicated Administrator Connection.
1916510Error starting Named Pipes support for Dedicated Administrator Connection.
1920010Authentication succeeded.
1920110The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream.
1920210An error occurred while calling CompleteAuthToken for this security context. The operating system error code indicates the cause of failure.
1920310The CompleteAuthToken API is not defined for the current Security Support Provider.
1920410AcceptSecurityContext failed. The operating system error code indicates the cause of failure.
1920510The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
1920610The Channel Bindings from this client do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider might need to be upgraded to support Extended Protection. Closing the connection.
1920710The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider or client operating system might need to be upgraded to support Extended Protection. Closing the connection.
1920810The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
1920910QueryContextAttributes could not retrieve Service Bindings. The operating system error code indicates the cause of failure.
1921010The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this client must support Extended Protection. You might have to install an operating system service pack that allows for Service Binding and Channel Binding.
1921110The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this client must support Extended Protection. You might have to update the SQL Server driver on the client.
1921210The Service Class element of the received Service Principal Name (SPN) is not valid.
1921310The IP Address element of the received Service Principal Name (SPN) is not valid.
1921410The Host element of the received Service Principal Name (SPN) is not valid.
1921510A memory allocation failed while validating the received Service Principal Name (SPN).
1921610QueryContextAttributes succeeded but did not retrieve the received Service Principal Name (SPN).
1921710WSAStringToAddress was unable to convert the IP Address element of the received Service Principal Name (SPN) to an address structure. The operating system error code indicates the cause of failure.
1921810Could not wait on an event signaling IO completion for a cryptographic handshake.
1921910A task to process a cryptographic handshake could not be enqueued.
1922010An attempt to read a buffer from the network failed during a cryptographic handshake.
1922110The connection was closed while attempting to process a read buffer during a cryptographic handshake.
1922210The connection was closed while attempting to process a write buffer during a cryptographic handshake.
1922310An attempt to write a buffer to the network failed during a cryptographic handshake.
1922410AcquireCredentialsHandle failed. The operating system error code indicates the cause of the failure.
1922510InitializeSecurityContext failed. The operating system error code indicates the cause of the failure.
1922610QueryContextAttributes could not retrieve stream sizes. The operating system error code indicates the cause of the failure.
1922710An attempt to resize a buffer failed.
1922810An unexpected error occurred during a cryptographic handshake.
1922910An invalid token was received during a cryptographic handshake.
1923010Failed to allocate a packet for a network write during a cryptographic handshake.
1923110Failed to allocate an object to perform a cryptographic handshake.
1923210Failed to initialize an object to perform a cryptographic handshake.
1923310A token from a cryptographic handshake was larger than allowed by SSPI.
1923410The connection was closed while waiting for network IO during a cryptographic handshake.
1923510An unexpected exception was thrown while processing a cryptographic handshake.
1923610Negotiated security context is missing an integrity flag.
1923810Negotiated security context is missing a confidentiality flag.
1923910Negotiated security context has confidentiality flag present.
1924010Negotiated security context is missing a sequence detection flag.
1924110Negotiated security context is missing a replay detection flag.
1924210Global credentials handle required for inbound connections.
1924310SSPI structures too large for encryption.
1924410SSPI structures too large for signature.
1924510Empty output token is returned by SSPI during security context negotiation. Check for network packet corruption or other networking issues.
1924610Incomplete message error is returned from SSPI but failed to proceed.
1940116The READ_ONLY_ROUTING_URL ‘%.*ls’ specified for availability replica ‘%.*ls’ is not valid. It does not follow the required format of ‘TCP://system-address:port’. For information about the correct routing URL format, see the CREATE AVAILABILITY GROUP documentation in SQL Server Books Online.
1940216A duplicate availability replica ‘%.*ls’ was specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’. Inspect the replica list that you specified in your command, and remove the duplicate replica name or names from the list. Then retry the command.
1940316The availability replica ‘%.*ls’ specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’ does not exist. Only availability replicas that belong to the specified availability group ‘%.*ls’ can be added to this list. To get the names of availability replicas in a given availability group, select replica_server_name from sys.availability_replicas and name from sys.availability_groups. For more information, see SQL Server Books Online.
1940416An availability replica ‘%.*ls’ that is specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’ does not have a value set for READ_ONLY_ROUTING_URL. Ensure a READ_ONLY_ROUTING_URL is set for each availability replica in the availability group. Specify a valid READ_ONLY_ROUTING_URL for each replica that you want to added to the READ_ONLY_ROUTING_LIST. If you are altering availability replicas of an existing availability group, you can get the names of availability replicas in a given availability group, select replica_server_name from sys.availability_replicas and name from sys.availability_groups. For more information, see SQL Server Books Online.
1940516Failed to create, join or add replica to availability group ‘%.*ls’, because node ‘%.*ls’ is a possible owner for both replica ‘%.*ls’ and ‘%.*ls’. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try again.
1940610The state of the local availability replica in availability group ‘%.*ls’ has changed from ‘%ls’ to ‘%ls’.  %ls.  For more information, see the SQL Server error log or cluster log.  If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console.
1940716The lease between availability group ‘%.*ls’ and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
1940810The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the remote WSFC cluster, ‘%.*ls’. An ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = ‘remote_wsfc_cluster_name’ command switched the cluster context from the local WSFC cluster to this remote WSFC cluster. This is an informational message only. No user action is required.
1940910The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the local WSFC cluster. An ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command switched the cluster context from the remote WSFC cluster, ‘%.*ls’, to the local WSFC cluster. On this local WSFC cluster, availability databases no longer belong to any availability group, and they are transitioning to the RESTORING state. This is an informational message only. No user action is required.
1941016An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to a remote WSFC cluster failed. This is because one or more availability replicas hosted by the local instance of SQL Server are currently joined to an availability group on the local WSFC cluster. Remove each of the joined replicas from its respective availability group. Then retry your ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = ‘%.*ls’ command.
1941116The specified Windows Server Failover Clustering (WSFC) cluster, ‘%.*ls’, is not ready to become the cluster context of Always On Availability Groups (Windows error code: %d). The possible reason could be that the specified WSFC cluster is not up or that a security permissions issue was encountered. Fix the cause of the failure, and retry your ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = ‘remote_wsfc_cluster_name’ command.
1941216The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = ‘%.*ls’ command failed. The current Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups is already under a remote WSFC cluster. When Always On Availability Groups is running under a remote cluster context, switching to another remote WSFC cluster is not allowed. You can only switch to the local WSFC cluster.
1941316An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context failed. This attempt failed because switching the cluster context back to the local cluster at this time might cause data loss because one or more secondary databases on synchronous-commit replicas are not in the SYNCHRONIZED state. Wait until all synchronous-commit secondary databases are synchronized, and then retry the ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command.
1941416An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to the specified WSFC cluster , ‘%ls’, failed. The cluster context has been switched back to the local WSFC cluster. Check the SQL Server error log for more information. Correct the cause of the error, and repeat the steps for setting up the secondary replicas on the remote WSFC cluster from the beginning.
1941516Failed to process the registry key value ‘%.*ls’ (Windows error code: %d), which holds the name of the remote Windows Server Failover Clustering (WSFC) cluster. For more information about this error code, see “System Error Codes” in the Windows Development documentation. Correct the cause of this error, and repeat the steps for setting up the secondary replicas on the remote WSFC cluster from the beginning.
1941616One or more databases in availability group ‘%.*ls’ are not synchronized. On a synchronous-commit availability replica, ALTER AVAILABILITY GROUP <group_name> OFFLINE is not allowed when one or more databases are not synchronized. Wait for all databases to reach the SYNCHRONIZED state, and retry the command.
1941716An attempt to fail over or create an availability group failed. This operation is not supported when Always On Availability Groups is running under a remote Windows Server Failover Clustering (WSFC) cluster context. Under a remote cluster context, failing over or creating availability groups are not supported.
1941816The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = ‘%.*ls’ command failed because the local Windows Server Failover Clustering (WSFC) cluster name,’%.*ls’, was specified. Retry the command, specifying the name of a remote WSFC cluster.
1941916Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group ‘%.*ls’ within the lease timeout period.
1942010The availability group ‘%.*ls’ is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required.
1942116SQL Server hosting availability group ‘%.*ls’ did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period.
1942216The renewal of the lease between availability group ‘%.*ls’ and the Windows Server Failover Cluster failed because SQL Server encountered Windows error with error code (‘%d’).
1942316The lease of availability group ‘%.*ls’ lease is no longer valid to start the lease renewal process.
1942410The lease worker of availability group ‘%.*ls’ is now sleeping the excess lease time (%u ms) supplied during online. This is an informational message only. No user action is required.
1943116Always On Availability Groups transport for availability database “%.*ls” has hit flow control boundary with log block whose LSN is %S_LSN. This error happens when secondary replica doesn’t have buffer to receive a new message from primary. This is an informational message only. No user action is required.
1943216Always On Availability Groups transport has detected a missing log block for availability database “%.*ls”. LSN of last applied log block is %S_LSN. Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.
1943316Always On: AG integrity check failed to find AG name to ID map entry with matching group ID for AG ‘%.*ls’ (expected: ‘%.*ls’; found ‘%.*ls’).
1943416Always On: AG integrity check failed to find AG name to ID map entry with matching resource ID for AG ‘%.*ls’ (expected: ‘%.*ls’; found ‘%.*ls’).
1943516Always On: AG integrity check failed for AG ‘%.*ls’ with error %d, severity %d, state %d.
1943616Always On: A failure [%d] was encountered while waiting for LSN %S_LSN to be hardened on the Commit Manager [%d] for database ID [%d] on partner ID [%s].
1945016Failed to open a cluster network interface object: ‘%ls’. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1945116‘%.*ls’ and ‘%.*ls’ belong to the same subnet. Only one IPv4 and/or one IPv6 address from each subnet is allowed. For an advanced configuration, see the Windows Server Failover Clustering (WSFC) administrator to create a customized configuration through the Cluster Manager.
1945216The availability group listener (network name) with Windows Server Failover Clustering resource ID ‘%s’, DNS name ‘%s’, port %hu failed to start with a permanent error: %u. Verify port numbers, DNS names and other related network configuration, then retry the operation.
1945316The availability group listener (network name) with resource ID ‘%s’, DNS name ‘%s’, port %hu failed to start with this error: %u. Verify network and cluster configuration and logs.
1945416The availability group listener (network name) with resource ID ‘%s’, DNS name ‘%s’, port %hu failed to stop with this error: %u. Verify network and cluster configuration and logs.
1945516The WSFC cluster does not have a public cluster network with an IPv4 subnet. This is a requirement to create an availability group DHCP listener. Configure a public network for the cluster with an IPv4 subnet, and try to create the listener.
1945616None of the IP addresses configured for the availability group listener can be hosted by the server ‘%.*ls’. Either configure a public cluster network on which one of the specified IP addresses can be hosted, or add another listener IP address which can be hosted on a public cluster network for this server.
1945716The specified IP Address ‘%.*ls’ is not valid in the cluster-allowed IP range. Check with the network administrator to select values that are appropriate for the cluster-allowed IP range.
1945816The WSFC nodes that host the primary and secondary replicas belong to different subnets. DHCP across multiple subnets is not supported for availability replicas. Use the static IP option to configure the availability group listener.
1945916The listener with DNS name ‘%.*ls’ does not conform to SQL Server listener guidelines, and cannot be configured through SQL Server. Reconfigure the listener through the WSFC Cluster Manager.
1946016The availability group listener with DNS name ‘%.*ls’ is configured to use DHCP. For listeners with this configuration, IP addresses cannot be added through SQL Server. To add IP addresses to the listener, drop the DHCP listener and create it again configured to use static IP addresses.
1946116The WSFC node that hosts the primary replica belongs to multiple subnets. To use the DHCP option in a multi-subnet environment, supply an IPv4 IP address and subnet mask of the subnet for the listener.
1946216Failed to obtain the WSFC node enumeration handle. The error code is %d.  The WSFC service may not be running or may be inaccessible in its current state, or the specified cluster resource handle is invalid.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1946316The WSFC cluster network interface control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1946416The WSFC cluster network control API returned an invalid IP address. The WSFC service might have invalid data in its database or it is a not supported version.
1946516The WSFC management API returned an unrecognizable dependency expression: ‘%.*ls’. The WSFC service might have invalid data in its database or it is a not supported version.
1946616Failed to obtain the WSFC resource dependency expression for cluster resource with name or ID ‘%ls’ The error code is %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1946716Failed to remove the resource dependency in which resource ‘%.*ls’ is depending on resource ‘%.*ls’ in the WSFC cluster. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1946816The listener with DNS name ‘%.*ls’ for the availability group ‘%.*ls’ is already listening on the TCP port %u. Please choose a different TCP port for the listener. If there is a problem with the listener, try restarting the listener to correct the problem.
1946916The specified listener with DNS name, ‘%.*ls’, does not exist for the Availability Group ‘%.*ls’. Use an existing listener, or create a new listener.
1947016Failed to delete a resource in the WSFC cluster because the resource ‘%.*ls’ is not offline. Delete the resource using the Failover Cluster Management tool (cluadmin.msc).
1947116The WSFC cluster could not bring the Network Name resource with DNS name ‘%ls’ online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
1947216Failed to delete the WSFC cluster resource ‘%.*ls’. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1947316Failed to add a resource dependency, making resource ‘%.*ls’ depend on resource ‘%.*ls’, in the WSFC cluster. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1947416Failed to set the resource dependency expression ‘%ls’ for the WSFC resource ‘%.*ls’. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1947516Cannot take the WSFC resource with ID ‘%.*ls’ offline. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1947616The attempt to create the network name and IP address for the listener failed. If this is a WSFC availability group, the WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. Otherwise, contact your primary support provider.
1947716The availability group ‘%.*ls’ already has a listener with DNS name ‘%.*ls’.  Availability groups can have only one listener. Use the existing listener, or drop the existing listener and create a new one.
1947816Failed to find a multi-string property (property name ‘%ls’) of the WSFC resource with name or ID ‘%.*ls’. The system error code is %d.  The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see “System Error Codes” in the Windows Development documentation.
1947916The WSFC cluster network control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1948016Failed to open a cluster network object: ‘%ls’. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1948116Failed to obtain the WSFC resource state for cluster resource with name or ID ‘%.*ls’. The WSFC resource state API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state.  For information about this error code, see “System Error Codes” in the Windows Development documentation.
1948216The port number, %u, that is specified is invalid. Valid port numbers range from 1 to 65535, inclusive. Select a port number in this range. If a port number is not provided, the default number 1433 is used.
1948316The format for the IP address, ‘%.*ls’, is invalid. Please use a valid value for the IP address.
1948416The specified IP Address, ‘%.*ls’, is duplicated in the IP address list. Each IP address included in the listener configuration must be unique. Change the statement to remove or replace the duplicated values.
1948516The specified DNS name, ‘%.*ls’, is invalid. The length of the DNS name needs to be between 1 and 63 characters, inclusive. Change the value of the DNS name to meet this requirement.
1948616The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port [%.*ls:%d]. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For information about altering an availability group listener, see the “ALTER AVAILABILITY GROUP (Transact-SQL)” topic in SQL Server Books Online.
1948716Listener configuration changes were completed but listening status of the corresponding TCP provider could not be determined because of the error code: %u. Check the system error log to determine if the TCP provider is listening or a listener restart is needed.
1948816The attempt to create the network name and IP address for the listener failed, and the attempt to roll back the resources for the Network Name and IP Address resources has also failed. If this is a WSFC availability group, the WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. Ensure that no Network Name or IP Address resource from this operation still exists in the cluster. Otherwise, contact your primary support provider.
1948916The attempt to create FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
1949016The attempt to delete FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
1949110Always On: The Windows Server Failover Clustering (WSFC) service was started using /forcequorum. This is an informational message only. No user action is required.
1949216The availability database %ls in availailability group %ls is in an invalid state to perform an internal operation. Refer to the error code for more details. If this condition persists, contact the system administrator.
1949316Corrupt secondary replica %ls causing start scan to fail for database with ID %d. Refer to the SQL Server error log for information about the errors that were encountered.  If this condition persists, contact the system administrator.
1949410Automatic seeding of availability database ‘%ls’ in availability group ‘%.*ls’ failed with a transient error. The operation will be retried.
1949510Automatic seeding of availability database ‘%ls’ in availability group ‘%.*ls’ failed with an unrecoverable error. Correct the problem, then issue an ALTER AVAILABILITY GROUP command to set SEEDING_MODE = AUTOMATIC on the replica to restart seeding.
1949610Automatic seeding of availability database ‘%.*ls’ in availability group ‘%.*ls’ failed.
1949716Conflicting option spec provided. DISTRIBUTED option cannot be combined with any other availability group options.
1949816To create a distributed availability group, please specify the DISTRIBUTED option.
1949916The specified listener URL ‘%.*ls’ is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online.
1950116None of the specified availability groups exist locally. Please check your DDL and make sure there is one availability group exist locally.
1950216Cannot create a distributed availability replica for availability group ‘%.*ls’.  An availability replica of the specified availability group already exists on this instance of SQL Server.  Verify that the specified availability group name is correct and unique, then retry the operation.  To remove the existing availability replica, run DROP AVAILABILITY GROUP command.
1950316Cannot create a distributed availability replica for availability group ‘%.*ls’.  Local availability group is participating in a distributed availability group as secondary.
1950416Cannot failover a distributed availability replica for availability group ‘%.*ls’. Only force failover is supported in this version of SQL Server.
1950510Cannot initiate a target seeding operation on a non-secondary/forwarder replica for availability group ‘%.*ls’. Replica state may have changed since we submit the build task.
1950616Local availability replica for availability group ‘%.*ls’ has not been granted permission to create databases, but has a SEEDING_MODE of AUTOMATIC. Use the ALTER AVAILABILITY GROUP … GRANT CREATE ANY DATABASE command to allow the creation of databases seeded by the primary availability replica.
1950716Cannot create a distributed availability replica for availability group ‘%.*ls’. There is an already existing distributed availability group on top of the same replicas.
1950816‘ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP’ command failed. Participant availability replica ‘%.*ls’ not found in the distributed availability group ‘%.*ls’.
1950916Cannot create a distributed availability group ‘%.*ls’. An availability group with the same name already exists.
1951016Distributed availability group ‘%.*ls’ not found. Rerun the command with an existing distributed availbility group.
1951116Cannot join distributed availability group ‘%.*ls’. The local availability group ‘%.*ls’ contains one or more databases. Remove all the databases or create an empty availability group to join a distributed availability group.
1951216The requested operation only applies to distributed availability group, and is not supported on the specified availability group ‘%.*ls’. Please make sure you are specifying the correct availability group name.
1951316Cannot create a distributed availability replica for availability group ‘%.*ls’. Distributed availability group cannot be built on top of basic local availability group. Please make sure you are specifying the correct local availability group name.
1951410Failed to wait for primary partner’s transport up while starting up secondary remote replica.
1951516Database partner is missing during database restart.
2000110There is no nickname for article ‘%s’ in publication ‘%s’.
2000210The filter ‘%s’ already exists for article ‘%s’ in publication ‘%s’.
2000310Could not generate nickname for ‘%s’.
2000410Publication ‘%s’ has the following property: ‘%s’. SQL Server subscribers below version ‘%s’ will ignore this setting.
2000518%ls: Cannot convert parameter %ls: Resulting colv would have too many entries.
2000616Cannot make the change because the article might be in a publication that has anonymous or client subscriptions. Set @force_reinit_subscription to 1 to acknowledge that such a subscription will be reinitialized.
2000716The system tables for merge replication could not be dropped successfully.
2000816The system tables for merge replication could not be created successfully.
2000916The article ‘%s’ could not be added to the publication ‘%s’.
2001016The Snapshot Agent corresponding to the publication ‘%s’ could not be dropped.
2001116Cannot set incompatible publication properties. The ‘allow_anonymous’ property of a publication depends on the ‘immediate_sync’ property.
2001216The subscription type ‘%s’ is not allowed on publication ‘%s’.
2001316The publication property ‘%s’ cannot be changed when there are subscriptions on it.
2001416Invalid @schema_option value.
2001516Could not remove directory ‘%ls’. Check the security context of xp_cmdshell and close other processes that may be accessing the directory.
2001616Invalid @subscription_type value. Valid values are ‘pull’ or ‘anonymous’.
2001716The subscription on the Subscriber does not exist.
2001816The @optional_command_line is too long. Use an agent definition file.
2001916Replication database option ‘%s’ cannot be set unless the database is a publishing database or a distribution database.
2002016The article resolver supplied is either invalid or nonexistent.
2002116The subscription could not be found.
2002216This article has now settings to disable uploads and compensate_for_errors=true. However, local and anonymous subscribers will behave as if compensate_for_errors=false.
2002316Invalid @subscriber_type value. Valid options are ‘local’, ‘global’, or ‘anonymous’.
2002416The alt_snapshot_folder cannot be the same as the working directory.
2002516The publication name must be unique. The specified publication name ‘%s’ has already been used.
2002616The publication ‘%s’ does not exist.
2002716The article ‘%s’ does not exist.
2002816The Distributor has not been installed correctly. Could not enable database for publishing.
2002916The Distributor has not been installed correctly. Could not disable database for publishing.
2003016The article ‘%s’ already exists on another publication with a different column tracking option.
2003116Could not delete the row because it does not exist.
2003216‘%s’ is not defined as a Subscriber for ‘%s’.
2003316Invalid publication type.
2003416Publication ‘%s’ does not support ‘%s’ subscriptions.
2003616The Distributor has not been installed correctly.
2003716The article ‘%s’ already exists in another publication with a different article resolver.
2003816The article filter could not be added to the article ‘%s’ in the publication ‘%s’.
2003916The article filter could not be dropped from the article ‘%s’ in the publication ‘%s’.
2004016Could not drop the article(s) from the publication ‘%s’.
2004116Transaction rolled back. Could not execute trigger. Retry your transaction.
2004316Could not change the article ‘%s’ because the publication has already been activated.
2004416The priority property is invalid for local subscribers.
2004516You must supply an article name.
2004616The article does not exist.
2004716You are not authorized to perform this operation.
2004816To modify the priority of a subscription, run sp_changemergesubscription at the Publisher instead of using sp_changemergepullsubscription at subscriber. This is for backward compatibility only.
2004916The priority value should not be larger than 100.0.
2005016The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999.
2005116The Subscriber is not registered.
2005216The @metatype parameter value must be null, 1, 2, 5, or 6.
2005316An article with a different %s value already exists for object ‘%s’.
2005416Current database is not enabled for publishing.
2005516Table ‘%s’ cannot be published for merge replication because it has a timestamp column.
2005616Table ‘%s’ cannot be republished.
2005716The profile name ‘%s’ already exists for the specified agent type.
2005816The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge)
2005916The @profile_type must be 0 (System) or 1 (Custom)
2006016Compatibility level cannot be smaller than 60.
2006116The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.
2006216Updating columns with the rowguidcol property is not allowed.
2006316Table ‘%s’ into which you are trying to insert, update, or delete data has been marked as read-only. Only the merge process can perform these operations.
2006416Cannot drop profile. Either it is not defined or it is defined as the default profile.
2006516Cannot drop profile because it is in use.
2006616Profile not defined.
2006716The parameter name ‘%s’ already exists for the specified profile.
2006816The article cannot be created on table ‘%s’ because it has more than %d columns.
2006916Cannot validate a merge article that uses looping join filters.
2007016Cannot update subscription row.
2007216Cannot update Subscriber information row.
2007316Articles can be added or changed only at the Publisher.
2007416Only a table object can be published as a “table” article for merge replication.
2007516The ‘status’ parameter value must be either ‘active’ or ‘unsynced’.
2007616The @sync_mode parameter value must be ‘native’ or ‘character’.
2007716Problem encountered generating replica nickname.
2007816The @property parameter value must be one of the following: ‘sync_type’, ‘priority’, ‘description’, ‘subscriber_security_mode’, ‘subscriber_login’, ‘subscriber_password’, ‘publisher_security_mode’, ‘publisher_login’, ‘publisher_password’, ‘merge_job_login’, or ‘merge_job_password’.
2007916Invalid @subscription_type parameter value. Valid options are ‘push’, ‘pull’, or ‘both’.
2008116Publication property ‘%s’ cannot be NULL.
2008416Publication ‘%s’ cannot be subscribed to by Subscriber database ‘%s’.
2008616Publication ‘%s’ does not support the nosync type because it contains a table that does not have a rowguidcol column.
2008716You cannot push an anonymous subscription.
2008816Only assign priorities that are greater than or equal to 0 and less than 100.
2008916Could not get license information correctly.
2009016Could not get version information correctly.
2009116sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions.
2009216Table ‘%s’ into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publisher data modifications are disallowed until the upgrade completes and snapshot has successfully run. On subscriber data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher.
2009316Merge replication upgrade is not complete until the snapshot agent is run for the publisher and the merge agent run for all the subscribers.
2009410Profile parameter ‘%s’ is dynamically reloadable and the change will be applied to running agents within configured period of time.
2009510For agent profile ‘%s’, parameters marked as is_reloadable in msdb.dbo.MSagentparameterlist table will be applied to running agents within configured period of time.
2010016Cannot drop Subscriber ‘%s’. There are existing subscriptions.
2050016The updatable Subscriber stored procedure ‘%s’ does not exist.
2050116Could not insert into sysarticleupdates using sp_articlecolumn.
2050216Invalid ‘%s’ value. Valid values are ‘read only’, ‘sync tran’, ‘queued tran’, or ‘failover’.
2050316Invalid ‘%s’ value in ‘%s’. The publication is not enabled for ‘%s’ updatable subscriptions.
2050416Immediate Updating Subscriptions: The xml values inserted/updated by Subscriber will be replicated as NULL to publisher.
2050516Could not drop synchronous update stored procedure ‘%s’ in ‘%s’.
2050616Source table ‘%s’ not found in ‘%s’.
2050716Table ‘%s’ not found in ‘%s’.
2050811Updatable subscriptions: The text, ntext, or image values inserted at the Subscriber will be NULL.
2050916Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber.
2051016Updateable Subscriptions: Cannot update identity columns.
2051116Updateable Subscriptions: Cannot update timestamp columns.
2051216Updateable Subscriptions: Rolling back transaction.
2051316Database ‘%s’ does not contain any replication metadata for a row whose ROWGUIDCOL matches the value specified for the @rowguid parameter of sp_showrowreplicainfo. Verify that the value specified for @rowguid parameter is correct.
2051410A rowcount validation request has been submitted to heterogeneous publisher %s for article %s of publication %s.  Validation results will be posted to distribution history.
2051516Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber.
2051616Updateable Subscriptions: Replicated data is not updatable.
2051816Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column.
2051916Updateable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
2052016Updateable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
2052116sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles.
2052216sp_MSmark_proc_norepl: invalid object name ‘%s’.
2052316Could not validate the article ‘%s’. It is not activated.
2052410Table ‘%s’ may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast).
2052510Table ‘%s’ might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s).
2052610Table ‘%s’ passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast).
2052710Table ‘%s’ passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns.
2052810Log Reader Agent startup message.
2052910Starting agent.
2053010Run agent.
2053110Detect nonlogged agent shutdown.
2053210Replication agent schedule.
2053310Replication agents checkup
2053410Detects replication agents that are not logging history actively.
2053510Removes replication agent history from the distribution database.
2053610Replication: agent failure
2053710Replication: agent retry
2053810Replication: expired subscription dropped
2053910Replication Warning: %s (Threshold: %s)
2054010Replication: agent success
2054110Removes replicated transactions from the distribution database.
2054210Detects and removes expired subscriptions from published databases or distribution databases.
2054310@rowcount_only parameter must be the value 0,1, or 2. 0=7.0 compatible checksum. 1=only check rowcounts. 2=new checksum functionality introduced in version 8.0.
2054510Default agent profile
2054610Verbose history agent profile.
2054710Agent profile for detailed history logging.
2054810Slow link agent profile.
2054910Agent profile for low bandwidth connections.
2055010Windows Synchronization Manager profile
2055110Profile used by the Windows Synchronization Manager.
2055210Could not clean up the distribution transaction tables.
2055310Could not clean up the distribution history tables.
2055410The replication agent has not logged a progress message in %ld minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.
20555106.x publication.
2055610Heartbeats detected for all running replication agents.
2055710Agent shutdown. For more information, see the SQL Server Agent job history for job ‘%s’.
2055810Table ‘%s’ passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically.
2055910Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used.
2056010An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested.
2056110Generated expected rowcount value of %s for %s.
2056510Replication: Subscriber has failed data validation
2056610Replication: Subscriber has passed data validation
2056710Agent history clean up: %s
2056810Distribution clean up: %s
2056910Expired subscription clean up
2057010Reinitialize subscriptions having data validation failures
2057110Reinitializes all subscriptions that have data validation failures.
2057210Subscriber ‘%s’ subscription to article ‘%s’ in publication ‘%s’ has been reinitialized after a validation failure.
2057310Replication: Subscription reinitialized after validation failure
2057410Subscriber ‘%s’ subscription to article ‘%s’ in publication ‘%s’ failed data validation.
2057510Subscriber ‘%s’ subscription to article ‘%s’ in publication ‘%s’ passed data validation.
2057610Subscriber ‘%s’ subscription to article ‘%s’ in publication ‘%s’ has been reinitialized after a synchronization failure.
2057710No entries were found in msdb..sysreplicationalerts.
2057810Replication: agent custom shutdown
2057910Generated expected rowcount value of %s and expected checksum value of %s for %s.
2058010Heartbeats not detected for some replication agents. The status of these agents have been changed to ‘Failed’.
2058110Cannot drop server ‘%s’ because it is used as a Distributor in replication.
2058210Cannot drop server ‘%s’ because it is used as a Publisher in replication.
2058310Cannot drop server ‘%s’ because it is used as a Subscriber in replication.
2058410Cannot drop server ‘%s’ because it is used as a Subscriber to remote Publisher ‘%s’ in replication.
2058516Validation Failure. Object ‘%s’ does not exist.
2058616(default destination)
2058716Invalid ‘%s’ value for stored procedure ‘%s’.
2058816The subscription is not initialized. Run the Distribution Agent first.
2058910Agent profile for replicated queued transaction reader.
2059016The article property ‘status’ cannot include bit 64, ‘DTS horizontal partitions’ because the publication does not allow data transformations.
2059116Only ‘DTS horizontal partitions’ and ‘no DTS horizontal partitions’ are valid ‘status’ values because the publication allows data transformations.
2059216‘dts horizontal partitions’ and ‘no dts horizontal partitions’ are not valid ‘status’ values because the publication does not allow data transformations.
2059316Cannot modify publication ‘%s’.  The sync_method cannot be changed to ‘native’, or ‘concurrent’ because the publication is enabled for heterogeneous subscribers.
2059416A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions.
2059516Skipping error signaled.
2059616Only ‘%s’ or members of db_owner can drop the anonymous agent.
2059710Dropped %d anonymous subscription(s).
2059816The row was not found at the Subscriber when applying the replicated %S_MSG command for Table ‘%s’ with Primary Key(s): %s
2059916Continue on data consistency errors.
2060010Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers.
2060110Invalid value specified for agent parameter ‘SkipErrors’.
2060210The value specified for agent parameter ‘SkipErrors’ is too long.
2060310The agent profile cannot be used by heterogeneous Subscribers.
2060410You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter ‘SubscriptionType’.
2060510Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot.
2060610Reinitialized subscription(s).
2060710Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing snapshot.
2060810Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active subscriptions.
2060916Cannot attach subscription file ‘%s’. Make sure that it is a valid subscription copy file.
2061016Cannot run ‘%s’ when the Log Reader Agent is replicating the database.
2061116Cannot add the article. Publications that allow transformable subscriptions with Data Transformation Services (DTS) can only include tables and indexed views that are published as tables.
2061216Checksum validation is not supported because the publication allows DTS. Use row count only validation.
2061316Validation is not supported for articles that are set up for DTS horizontal partitions.
2061416Validation is not supported for heterogeneous Subscribers.
2061516Unable to add a heterogeneous subscription to the publication.  The publication is not enabled for heterogeneous subscriptions.
2061610High Volume Server-to-Server Profile
2061710Merge agent profile optimized for the high volume server-to-server synchronization scenario.
2061816You must have CREATE DATABASE permission to attach a subscription database.
2061916Server user ‘%s’ is not a valid user in database ‘%s’. Add the user account or ‘guest’ user account into the database first.
2062011The security mode specified requires the server ‘%s’ to be registered as a linked server. Use sp_addlinkedserver to add the server.
2062111Cannot copy a subscription database to an existing database.
2062211Replication database option ‘sync with backup’ cannot be set on the publishing database because the database is in Simple Recovery mode.
2062311You cannot validate article ‘%s’ unless you have ‘SELECT ALL’ permission on table ‘%s’.
2062416The value specified for the @login parameter is not valid. User ‘%s’ is not a user in database ‘%s’. Add the user account to the database before attempting to execute the stored procedures sp_grant_publication_access or sp_revoke_publication_access.
2062516Cannot create the merge replication publication access list (PAL) database role for publication ‘%s’. This role is used by replication to control access to the publication. Verify that you have sufficient permissions to create roles in the publication database.
2062616Filter ‘%s’ already exists in publication ‘%s’. Specify a unique name for the @filtername parameter of sp_addmergefilter.
2062716Partition id has to be greater than or equal to 0.
2062816Failed to generate dynamic snapshot.
2062916Failed to get partition id information.
2063016Cannot create partitioned snapshot job. A job already exists for publication ‘%ls’ that uses the values you specified for the @suser_sname and/or @host_name parameters of sp_adddynamicsnapshot_job. If the job that already exists is not working correctly, use sp_dropdynamicsnapshot_job to drop it and create a new one using sp_adddynamicsnapshot_job.
2063116Cannot find a location in which to generate a partitioned snapshot. Verify that the there is a valid snapshot folder specified for the publication. This can be the default folder associated with the Distributor or an alternate folder associated with the publication.
2063216Failed to create a dynamic snapshot job to generate the dynamic snapshot.
2063316Cannot start the partitioned snapshot job. Verify that SQL Server Agent is running on the Distributor.
2063416The root publication information could not be found on the republisher.
2063516A push subscription to ‘%ls’ was found. Cannot add a pull subscription agent for a push subscription.
2063616Cannot generate merge replication stored procedures for article ‘%s’. Stored procedures are generated on the Publisher when the Snapshot Agent runs or when a data definition language action is performed; they are generated on the Subscriber when the snapshot is applied by the Merge Agent. Verify that the agents have the appropriate permissions to create procedures, and that the procedures do not already exist.
2063710The article order specified in the @processing_order parameter of sp_addmergearticle does not reflect the primary key-foreign key relationships between published tables. Article ‘%s’ references one or more articles that will be created after it is created. Change the processing_order property using sp_changemergearticle.
2063810Merge table articles do not support different values for the @source_object and @destination_object parameters of sp_addmergearticle. Either do not specify a value for @destination_object, or specify the same value for both parameters.
2063916Cannot enable the publication to support non-SQL Server subscriptions because the publication is enabled for updatable subscriptions. To support non-SQL Server subscriptions, drop the existing publication and create a new one with the properties allow_sync_tran and allow_queued_tran set to ‘false’.
2064016Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.
2064116Failed to check if the subset_filterclause has a dynamic function in it.
2064216Cannot add article ‘%s’ with one or more dynamic functions in the subset_filterclause ‘%s’ to publication ‘%s’ because the publication could have active subscriptions. Set @force_reinit_subscription to 1 to add the article and reinitialize all active subscriptions.
2064316Cannot change the value of validate_subscriber_info for publication ‘%s’ because the publication has active subscriptions. Set @force_reinit_subscription to 1 to change the value and reinitialize all active subscriptions.
2064416Invalid value “%s” specified for the parameter @identityrangemangementoption. Valid values are “auto”, “manual”, or “none”.
2064516The property “%s” cannot be modified for publications that are enabled for non-SQL Server subscriptions.
2064616Peer-to-peer publications do not support %s. Change the value for parameter ‘%s’.
2064716Cannot modify property ‘%s’. The publication is used in a peer-to-peer topology, which does not allow this property to be modified after the publication is created.
2064816An article already exists for table “%s” with a different value for the @delete_tracking property. The value must be the same for all publications in which the table is published. Use the stored procedures sp_helpmergearticle and sp_changemergearticle to view and modify the property in the other article(s).
2064916Publications enabled for heterogeneous subscriptions do not support %s. Please change the ‘%s’ parameter value.
2065016Cannot enable data definition language (DDL) replication (a value of “true” for the @replicate_ddl parameter) for publication “%s”. This is because the compatibility level of the publication is lower than 90RTM. For new publications, in the stored procedure sp_addmergepublication, set the @publication_compatibility_level parameter to 90RTM; for existing publications, use sp_changemergepublication.
2065116Publication “%s” “%s”. Therefore the compatibility level of the publication cannot be set to lower than %d. To set the compatibility level lower, disable the feature and then call the stored procedure sp_changemergepublication to lower the compatibility level.
2065216Required metadata for publication ‘%s’ could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.
2065316Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.
2065416Dynamic snapshots are only valid for merge publications.
2065516The partitioned snapshot process cannot complete. Cannot retrieve the maximum timestamp information from the MSsnapshot_history table in the distribution database. Ensure that a standard snapshot is up-to-date and available.
2065616The @subset_filterclause parameter cannot reference a computed column.
2065716The value for the @pub_identity_range parameter must be a multiple of the increment for the identity column. The increment for table “%s” and identity column “%s” is %s.
2065816The value for the @identity_range parameter must be a multiple of the increment for the identity column. The increment for table “%s” and identity column “%s” is %s.
2065911The value of IDENT_CURRENT (“%s”) is greater than the value in the max_used column of the  MSmerge_identity_range system table.
2066016The republisher’s republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range.
2066116The republisher’s republishing range obtained from its publisher is not large enough to allocate the specified @identity_range.
2066216The republisher does not have a range of identity values from the root Publisher ‘%s’ that it can assign to its Subscribers. Ensure that the republisher has a server subscription to the publication at the root Publisher, and then run the Merge Agent to synchronize with the root Publisher.
2066316The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @identityrangemanagementoption property is “auto”.
2066416The Publisher cannot be assigned a new range of identity values, because the values for the identity column’s data type have all been used. Change the data type in the identity column.
2066516The republisher does not have a range of identity values from the root Publisher that it can assign to its Subscribers. Run the Merge Agent to synchronize with the root Publisher.
2066616Cannot refresh the identity range and/or the check constraint on the Publisher. Ensure the following: that the value in the identity column has not reached the maximum for the data type in the identity column; and that the user who made the last insert has the privileges to drop and re-create the check constraint.
2066716Cannot allocate an identity range for article “%s”. The article is not enabled for automatic identity range management.
2066816Not enough range available to allocate a new range for a subscriber.
2066916Object referenced by the given @article or @artid ‘%s’ could not be found.
2067016Cannot add, drop, or alter the identity range check constraint for table %s. This constraint is used by replication for automatic identity range management. This error typically occurs if the user who made the last insert in the table does not have permission to make schema changes on the table. If this error occurs at the Publisher, run sp_adjustpublisheridentityrange; if it occurs at the Subscriber, run the Merge Agent.
2067116Cannot find the identity range allocation entry for the Subscriber in the MSmerge_identity_range table. Reinitialize the subscription.
2067216A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering.
2067316A value for the parameter @host_name was specified, but no articles in the publication use SUSER_SNAME() for parameterized filtering.
2067416The publication does not use dynamic filtering.
2067516The identity range values cannot be NULL.
2067611Cannot refresh the Publisher identity range for article “%s”. Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity range.
2067711Cannot add article “%s” with automatic identity range management. The article is already published in a transactional publication with automatic identity range management.
2067811Could not find the regular snapshot job for the specified publication ‘%s’.
2067911Cannot execute the stored procedure sp_adjustpublisheridentityrange on the current database because the database is a republisher or a Subscriber. To adjust the identity range at a republisher or a Subscriber, synchronize with the root Publisher.
2068016Failed to get metadata for a batch of rows.
2068110Cannot specify a value of 1, 2, or 3 for the parameter @partition_options because publication “%s” has a compatibility level lower than 90RTM. Use the stored procedure sp_changemergepublication to set publication_compatibility_level to 90RTM.
2068210Failed deletion of rows in batched delete attempt on table %s.
2068316Failed batched deletion on download only article %s.
2068416Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent.
2068516Cannot drop the filter ‘%s’ . The filter specified for the @filtername parameter cannot be found.
2068616Parameter ‘%s’ cannot be NULL or empty when this procedure is run from a ‘%s’ database.
2068716Parameter ‘%s’ must be NULL when this procedure is not being run from a ‘%s’ database.
2068816The tracer token ID (%d) could not be found for Publisher %s, database %s, publication %s. Use the stored procedure sp_helptracertokens to retrieve a list of valid tracer token IDs.
2068916The check for a Publisher needing a new identity range allocation failed on table %s. This check occurs every time the Merge Agent and Snapshot Agent run. Rerun the Merge Agent or Snapshot Agent.
2069016Cannot set up the Publisher identity range for table %s. Verify that appropriate ranges were specified when the article was created, and then rerun the Snapshot Agent.
2069116Merge replication upgrade of SQL Server 2005 metadata and triggers on the subscriber failed.
2069216One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_tombstone; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication.
2069316One or more rows to be inserted in the batch insert procedure for table %s were present in MSmerge_contents; merge replication cannot use batch insert. This typically occurs when rows move from one partition to another. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch insert can improve the performance of merge replication.
2069416One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch updates can improve the performance of merge replication.
2069516Only %ld out of %ld rows were updated in the batched update procedure for table %s; other rows could not be updated because they have been deleted. No action is required, but if this condition occurs frequently, determine if update-delete conflicts can be avoided. Batch updates can be helpful for performance.
2069616The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication.
2069716Cannot drop article %s from publication %s. In this publication, this is the only article that uses a parameterized filter. Dropping this article changes the publication to a static publication, which requires reinitialization of all Subscribers. To drop the article and reinitialize all active subscriptions, specify a value of 1 for the  @force_reinit_subscription parameter of sp_dropmergepublication.
2069816A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering.
2069916A value for the parameter @suser_sname was not specified while publication uses SUSER_SNAME() for dynamic filtering.
2070116The dynamic snapshot job schedule could not be changed on the distributor.
2070216The dynamic snapshot job schedule could not be changed due to one or more errors.
2070316One or more rows inserted in table ‘%s’ were out of partition while the table was published with ‘partition_options’ set to %d.
2070416The datatype of the identity column of table ‘%s’ is tinyint. tinyint does not have enough numbers available for merge auto identity range. Change the identity column to have a larger datatype and add the merge article with merge auto identity range management.
2070510Cannot set @conflict_logging to ‘both’ because publication ‘%s’ has a compatibility level lower than 90. Set @publication_compatibility_level to ’90RTM’ when creating the publication or use sp_changemergepublication to set publication_compatibility_level to ’90RTM’.
2070610The max or min allowed identity numbers for the identity column could not be found for the given article.
2070710Failed to publish the article with identityrangemanagementoption set to ‘auto’ due to one or more errors.
2070810An article is not allowed to be part of a logical record when it has a custom business logic resolver.
2070910The merge process could not clean up the conflict table “%s” for publication “%s”.
2071016Incorrect identity range allocation was detected when logging identity range allocation information on the distributor for publisher ‘%s’, publisher_db ‘%s’, publication ‘%s’ and article ‘%s’.
2071116The dynamic filters property for publication ‘%s’ has been incorrectly set. Use sp_changemergepublication to reset the value to true if the publication uses parameterized filters and false if it does not.
2071216Unable to acquire the replication merge administrative application lock for database ‘%s’. This could be due an active snapshot running while the schema change (DDL) or the administrative proc change was attempted.
2071316Replication merge admin stored procedure ‘%s’ failed for publication ‘%s’. This could be due an active snapshot running while the admin proc was called.
2071416Failed to prepare article ‘%s’ in publication ‘%s’ for merge replication.
2071516Failed to create merge replication triggers for object ‘%s’.
2071616Failed to create publication views for merge replication publication ‘%s’.
2071716sp_addmergelogsettings failed to add log settings. If log settings already exist for this subscription then use sp_changemergelogsettings to change the settings or sp_dropmergelogsettings to remove the settings.
2071816Log settings do not exist for subscriber server ‘%s’, subscriber db ‘%s’, webserver ‘%s’. Use sp_addmergelogsettings to add the settings.
2071916sp_changemergelogsettings failed to update log settings. Check the parameter values.
2072016Log settings do not exist for subscriber server ‘%s’, subscriber db ‘%s’, webserver ‘%s’.
2072116sp_dropmergelogsettings failed to remove log settings.
2072216‘%s’ failed. The value for parameter ‘%s’ is not valid. Valid values are @support_options [0 – 5], @log_severity [1 – 4], @log_file_size [2,000,000 – 999,000,000], @no_of_log_files [2 – 500], @upload_interval [0 – 40320], @delete_after_upload [0 – 1].
2072316Computed column “%s” can only be added to publication after its depending object “%s” is added.
2072416Could not find a valid command line for the dynamic snapshot job with job_id ‘%s’ for publication ‘%s’.
2072516Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id ‘%s’ in publication ‘%s’.
2072616Failed to change the dynamic snapshot location in one or more dynamic snapshot jobs for the given publication.
2072716An invalid value was specified for parameter @subscription_type. Valid values are ‘push’, ‘pull’, ‘both’, ‘anonymous’ or ‘all’.
2072816Failed to restore the max allocated identity value for article ‘%s’ in publication ‘%s’.
2072916The max identity value allocation for article ‘%s’ in publication ‘%s’ could not be found on the distributor.
2073016Setting @upload_first to ‘true’ requires the publication to be at publication_compatibility_level of ’80RTM’ or higher. Use sp_changemergepublication to set publication_compatibility_level to ’80RTM’ or higher if you want to use this feature.
2073116This edition of SQL Server does not support publications. Dropping existing publications.
2073210Warning: Values of some of the flags specified in the ‘schema_option’ property are not compatible with the publication’s compatibility level. The modified schema_option value of ‘%s’ will be used instead.
2073316One or more rows updated in table ‘%s’ were out of partition while the table was published with ‘partition_options’ set to %d.
2073416One or more rows deleted in table ‘%s’ were out of partition while the table was published with ‘partition_options’ set to %d.
2073516Cannot add article ‘%s’ to publication ‘%s’. The publication already contains 256 articles, which is the maximum.
2073610Warning: Values of some of the flags specified in the ‘schema_option’ property are not compatible with the publication’s compatibility level. The modified schema_option value of ‘%s’ will be used instead.
2073710Warning: To allow replication of FILESTREAM data to perform optimally and reduce memory utilization, the ‘stream_blob_columns’ property has been set to ‘true’.  To force FILESTREAM table articles to not use blob streaming, use sp_changemergearticle to set ‘stream_blob_columns’ to ‘false’.
2073811Cannot add article ‘%s’ with sparse column or column set to merge publication since merge replication does not support sparse columns and column set.
2073916The DDL operation is not supported for article ‘%s’. If the column in the DDL operation is enabled for FILESTREAM or is of type hierarchyid, geometry, geography, datetime2, date, time, or datetimeoffset, the publication compatibility level must be at least 100RTM. For DDL operations that involve FILESTREAM and hierarchyid columns, the snapshot mode must be native. Character mode, which is required for SQL Server Compact Subscribers, is not supported.
2080016Cannot reinitialize the article ‘%s’ in subscription ‘%s:%s’ to publication ‘%s’. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead.
2080116Cannot reinitialize the subscription. The publication is enabled for peer-to-peer transactional replication, which does not allow subscriptions to be reinitialized with a snapshot. Drop and re-create the subscription instead.
2080216Cannot publish objects from the replication administrative user schema [%s]. This schema owns all replication procedures and metadata tables, but it cannot own published objects. Use a different schema for objects that will be published.
2080316Peer-To-Peer topologies require identical articles in publications at all nodes prior to synchronizing. Articles in publication [%s].[%s].[%s] do not match articles in [%s].[%s].[%s].
2080416Articles can only be included in a single peer-to-peer publication. [%s].[%s] is already included in the peer-to-peer publication ‘%s’.
2080516Peer-to-peer topologies require identical publication names on each Publisher. You are attempting to republish object [%s].[%s] that is already being published in the peer-to-peer publication [%s].[%s].[%s].
2080616An error occurred while executing a peer-to-peer forwarding command. Contact Customer Support Services.
2080716No peers were found for %s:%s:%s. If you encounter this error when executing the stored procedure sp_requestpeerresponse, verify that subscriptions have been created before attempting to call the procedure again. If you encounter this error in other circumstances, contact Customer Support Services.
2080816The peer-to-peer publication ‘%s’ does not exist. Execute sp_helppublication to view a list of publication names.
2080916Peer-To-Peer topologies require identical publication names on each publisher. The distribution agent for publication [%s].[%s].[%s] is attempting to synchronize articles that exist in publication [%s].[%s].[%s].
2081016The specified source object must be a user-defined aggregate object if it is published as an ‘aggregate schema only’ type article.
2081116Replication monitoring refresher for %s.
2081216The specified source object must be a synonym if it is published as a ‘synonym schema only’ type article.
2081316Only members of the sysadmin fixed server role can modify a %s that does not have a job with a proxy account defined.
2081410Distribution Profile for OLEDB streaming
2081510Distribution agent profile enabled for the processing LOB data using OLEDB streaming.
2081610Peer-To-Peer publishers are only supported on Enterprise class editions of SQL Server.  This instance is %s.
2081716An error occurred during the execution of ‘%ls’. A call to ‘%ls’ failed with error code: ‘%ld’, return code: ‘%d’.
2100016Cannot subscribe to an inactive publication.
2100116Cannot add a Distribution Agent at the Subscriber for a push subscription.
2100216The Distribution Agent for this subscription already exists (%s).
2100316Changing publication names is no longer supported.
2100416Cannot publish the database object ‘%s’ because it is encrypted.
2100510For backward compatibility, sp_addpublisher can be used to add a Publisher for this Distributor. However, sp_adddistpublisher is more flexible.
2100616Cannot use sp_addpublisher to add a Publisher. Use sp_adddistpublisher.
2100716Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor.
2100816Cannot uninstall the Distributor because there are Subscribers defined.
2100916The specified filter procedure is already associated with a table.
2101016Removed %ld replicated transactions consisting of %ld statements in %ld milliseconds (%ld rows/millisec).
2101116Deactivated subscriptions.
2101216Cannot change the ‘allow_push’ property of the publication to “false”. There are push subscriptions on the publication.
2101316Cannot change the ‘allow_pull’ property of the publication to “false”. There are pull subscriptions on the publication.
2101416The @optname parameter value must be ‘transactional’ or ‘merge’.
2101516The replication option ‘%s’ has been set to TRUE already.
2101616The replication option ‘%s’ has been set to FALSE already.
2101716Cannot perform SQL Server 7.0 compatible checksum operation on a merge article that has a vertical or horizontal partition. Rowcount validation and SQL Server 2000 compatible binary checksum operation can be performed on this article.
2101816There are too many consecutive snapshot transactions in the distribution database.  Run the Log Reader Agent again or clean up the distribution database.
2101910Distribution agent for subscription added.
2102010no comment specified.
2102116Drop the Distributor before you uninstall replication.
2102216If set ‘immediate_sync’ property of a publication to true then must also set ‘independent_agent’ property to true.
2102316‘%s’ is no longer supported.
2102416The stored procedure ‘%s’ is already published as an incompatible type.
2102516The string being encrypted cannot have null characters.
2102616Cannot have an anonymous subscription on a publication that does not have an independent agent.
2102716‘%s’ replication stored procedures are not installed. You must reinstall SQL Server with Replication.
2102816Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication.
2102916Cannot drop a push subscription entry at the Subscriber unless @drop_push is ‘true’.
2103016Names of SQL Server replication agents cannot be changed.
2103116‘post_script’ is not supported for stored procedure articles.
2103216Could not subscribe because non-SQL Server Subscriber ‘%s’ does not support ‘sync tran’ update mode.
2103316Cannot drop server ‘%s’ as Distribution Publisher because there are databases enabled for replication on that server.
2103416Rows inserted or updated at the Subscriber cannot be outside the article partition.
2103516You have updated the Publisher property ‘%s’ successfully.
2103616Another %s agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent.
2103716Invalid working directory ‘%s’.
2103816Integrated Authentication is not supported by the server.
2103916The article ‘%s’ contains the destination owner ‘%s’. Non-SQL Server Subscribers require articles to have the destination owner of NULL.
2104016Publication ‘%s’ does not exist.
2104116A remote distribution Publisher is not allowed on this server version.
2104216The distribution Publisher property, ‘distributor_password’, has no usage and is not supported for a Distributor running on Windows NT 4.0.
2104316The Distributor is not installed.
2104416Cannot ignore the remote Distributor (@ignore_remote_distributor cannot be 1) when enabling the database for publishing or merge publishing.
2104516Cannot uninstall the Distributor because there are databases enabled for publishing or merge publishing.
2104616Cannot change distribution Publisher property ‘distribution_db’ because the Publisher is using the current distribution database.
2104716Cannot drop the local distribution Publisher because there are Subscribers defined.
2104816Cannot add login ‘%s’ to the publication access list because it does not have access to the distribution server ‘%s’.
2104916The login ‘%s’ does not have access permission on publication ‘%s’ because it is not in the publication access list.
2105016Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation.
2105116Could not subscribe because non-SQL Server Subscriber ‘%s’ does not support custom stored procedures.
2105216Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator is running, and that the subscription is active and initialized. If the subscription uses Microsoft Message Queueing, ensure the proper permissions are set on the queue.
2105316Input property parameter is not valid. See SQL Server Books Online for a list of valid parameters for sp_changemergepublication.
2105416The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers with updating subscriptions). Ensure sp_link_publication has been used to configure the linked server properly, and ensure that the login used to connect to the Publisher is in the publication access list.
2105515Invalid value for parameter %s specified for %s.
2105616The subscription to publication ‘%s’ has expired or does not exist.
2105716Anonymous Subscribers cannot have updatable subscriptions.
2105816An updatable subscription to publication ‘%s’ on Subscriber ‘%s’ already exists.
2105916Cannot reinitialize subscriptions of non-immediate_sync publications.
2106016Could not subscribe because non-SQL Server Subscriber ‘%s’ does not support parameterized statements.
2106116Invalid article status %d specified when adding article ‘%s’.
2106216The row size of table ‘%s’ exceeds the replication limit of 6,000 bytes.
2106316Table ‘%s’ cannot participate in updatable subscriptions because it is published for merge replication.
2106416The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Queue Reader Agent for subscription initialization. Try again after the (re)initialization completes.
2107016This subscription does not support automatic reinitialization (subscribed with the ‘no sync’ option). To reinitialize this subscription, you must drop and re-create the subscription.
2107110Cannot reinitialize article ‘%s’ in subscription ‘%s:%s’ to publication ‘%s’ (subscribed with the ‘no sync’ option).
2107216The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subscription to receive data.
2107316The publication specified does not exist.
2107416The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.
2107510The initial snapshot for publication ‘%s’ is not yet available.
2107610The initial snapshot for article ‘%s’ is not yet available.
2107710Deactivated initial snapshot for anonymous publication(s). New subscriptions must wait for the next scheduled snapshot.
2107816Table ‘%s’ does not exist in the Subscriber database.
2107916The RPC security information for the Publisher is missing or invalid. Use sp_link_publication to specify it.
2108016The ‘msrepl_tran_version’ column must be in the vertical partition of the article that is enabled for updatable subscriptions; it cannot be dropped.
2108116Server setting ‘Allow triggers to be fired which fire other triggers (nested triggers)’ must exist on updatable Subscribers.
2108216Database property ‘IsRecursiveTriggersEnabled’ has to be false for subscription databases at Subscribers that allow updatable subscriptions.
2108316Database compatibility level at immediate updating Subscribers cannot be less than 70.
2108416Publication ‘%s’ does not allow anonymous subscriptions.
2108516The retention period must be less than the retention period for the distribution database.
2108616The retention period for the distribution database must be greater than the retention period of any existing non-merge publications.
2108716Client subscriptions and anonymous subscriptions cannot republish data. To republish data from this database, the subscription to the root Publisher must be a server subscription with a priority greater than 0. Drop the current subscription and create a server subscription.
2108810The initial snapshot for the publication is not yet available.
2108916Only members of the sysadmin fixed server role can perform this operation.
2109016Cannot upgrade merge replication metadata. Attempt the upgrade again by running the Merge Agent for the Subscriber or by running the Snapshot Agent for the Publisher.
2109116Global subscribers with priority 0 are not allowed to create merge publications.
2109210The Change Tracking manual cleanup procedure for database %s has been executed
2110110The custom command name %s specified for parameter %s will be ignored. A system generated name will be used instead. The publication allows %s and command names need not be specified.
2110516This edition of SQL Server cannot act as a Publisher or Distributor for replication.
2110616This edition of SQL Server does not support publications.
2110716‘%ls’ is not a table or view.
2110816This edition of SQL Server does not support transactional publications.
2110916The parameters @xact_seqno_start and @xact_seqno_end must be identical if @command_id is specified.
2111016@xact_seqno_start and @publisher_database_id must be specified if @command_id is specified.
2111116‘%s’ is not a valid parameter for the Snapshot Agent.
2111216‘%s’ is not a valid parameter for the Log Reader Agent.
2111316‘%s’ is not a valid parameter for the Distribution Agent.
2111416‘%s’ is not a valid parameter for the Merge Agent.
2111516%d is not a valid value for the ‘%s’ parameter. The value must be a positive integer.
2111616‘%s’ is not a valid value for the ‘%s’ parameter. The value must be 1, 2, or 3.
2111716‘%s’ is not a valid value for the ‘%s’ parameter. The value must be 0, 1, or 2.
2111816‘%s’ is not a valid value for the ‘%s’ parameter. The value must be greater than or equal to 0 and less than or equal to 10,000.
2111916%s is not a valid value for the ‘%s’ parameter. The value must be a non-negative integer.
2112016Only members of the sysadmin fixed server role or db_owner fixed database role, or the owner of the subscription can drop subscription ‘%s’ to publication ‘%s’.
2112116Only members of the sysadmin fixed server role and ‘%s’ can drop the pull subscription to the publication ‘%s’.
2112216Cannot drop the distribution database ‘%s’ because it is currently in use.
2112316The agent profile ‘%s’ could not be found at the Distributor.
2112416Cannot find the table name or the table owner corresponding to the alternative table ID(nickname) ‘%d’ in sysmergearticles.
2112516A table used in merge replication must have at least one non-computed column.
2112616Pull subscriptions cannot be created in the same database as the publication.
2112716Only global merge subscriptions can be added to database ‘%s’.
2112816Terminating immediate updating or queued updating INSERT trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger ‘%s’ to first.
2112916Terminating immediate updating or queued updating UPDATE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger ‘%s’ to first.
2113016Terminating immediate updating or queued updating DELETE trigger because it is not the first trigger to fire. Use sp_settriggerorder procedure to set the firing order for trigger ‘%s’ to first.
2113116There are existing subscriptions to heterogeneous publication ‘%s’. To add new articles, first drop the existing subscriptions to the publication.
2113216Cannot create transactional subscription to merge publication ‘%s’. The publication type should be either transactional(0) or snapshot(1) for this operation.
2113316Publication ‘%s’ is not enabled to use an independent agent.
2113416The specified job ID must identify a Distribution Agent or a Merge Agent job.
2113516Detected inconsistencies in the replication agent table. The specified job ID does not correspond to an entry in ‘%ls’.
2113616Detected inconsistencies in the replication agent table. The specified job ID corresponds to multiple entries in ‘%ls’.
2113716This procedure supports only remote execution of push subscription agents.
2113816The ‘offload_server’ property cannot be the same as the Distributor name.
2113916Could not determine the Subscriber name for distributed agent execution.
2114016Agent execution cannot be distributed to a Subscriber that resides on the same server as the Distributor.
2114116The @change_active flag may not be specified for articles with manual filters or views.
2114216The SQL Server ‘%s’ could not obtain Windows group membership information for login ‘%s’. Verify that the Windows account has access to the domain of the login.
2114316The custom stored procedure schema option is invalid for a snapshot publication article.
2114416Cannot subscribe to publication of sync_type ‘dump database’ because the Subscriber has subscriptions to other publications.
2114516Cannot subscribe to publication %s because the Subscriber has a subscription to a publication of sync_type ‘dump database’.
2114616@use_ftp cannot be ‘true’ while @alt_snapshot_folder is neither NULL nor empty.
2114716The ‘%s’ database is not published for merge replication.
2114816Both @subscriber and @subscriberdb must be specified with non-null values simultaneously, or both must be left unspecified.
2114916The ‘%s’ database is not published for transactional or snapshot replication.
2115016Unable to determine the snapshot folder for the specified subscription because the specified Subscriber is not known to the Distributor.
2115116Pre- and post-snapshot commands are not supported for a publication that may support non-SQL Server Subscribers by using the character-mode bcp as the synchronization method.
2115216Cannot create a subscription of sync_type ‘none’ to a publication using the ‘concurrent’ or ‘concurrent_c’ synchronization method.
2115316Cannot create article ‘%s’. All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber.
2115416Cannot change article ‘%s’.  All articles that are part of a concurrent synchronization publication must use stored procedures to apply changes to the Subscriber.
2115516Cannot change article ‘%s’.  articles that are part of a concurrent synchronization publication can not have ins_cmd/del_cmd which exceeds %d characters .
2115616The @status parameter value must be ‘initiated’ or ‘active’.
2115716The snapshot compression option can be enabled only for a publication having an alternate snapshot generation folder defined.
2115816For a publication to be enabled for the Internet, the ‘ftp_address’ property must not be null.
2115916If a publication is enabled for the Internet, the ‘alt_snapshot_folder’ property must be non-empty.
2116016The ‘ftp_port’ property must be a non-negative integer < 65536.
2116116Could not change the Publisher because the subscription has been dropped. Use sp_subscription_cleanup to clean up the triggers.
2116216It is invalid to exclude the rowguid column for the table from the partition.
2116316It is not possible to add column ‘%s’ to article ‘%s’ because the snapshot for publication ‘%s’ has been run.
2116416Column ‘%s’ cannot be included in a vertical partition because it is neither nullable nor defined with a default value.
2116516Column ‘%s’ cannot be excluded from a vertical partition because it is neither nullable nor defined with a default value.
2116616Column ‘%s’ does not exist.
2116716The specified job ID does not represent a %s agent job for any push subscription in this database.
2116816Only members of the sysadmin fixed server role, members of the db_owner fixed database role, and owners of subscriptions served by the specified replication agent job can modify the agent offload settings.
2116916Could not identify the Publisher ‘%s’ at the Distributor ‘%s’. Make sure that the server ‘%s’ is registered at the Distributor.
2117016The specified Subscriber cannot use transformable subscriptions using Data Transformation Services. Only SQL Server 2000, SQL Server 2005, and OLE DB Subscribers can use transformable subscriptions.
2117116Could not find package ‘%s’ in msdb at server ‘%s’.
2117216The publication has to be in ‘character’, ‘concurrent_c’, or ‘database snapshot character’  bcp mode to allow DTS.
2117316The publication has to be ‘independent_agent type’ to allow DTS.
2117416Because this publication allows transformable subscriptions using DTS, it requires autogenerated stored procedures and parameterized commands, which are set using default value for the @status.
2117516You cannot change the ins_cmd, upd_cmd, or del_cmd article properties because the publication allows Data Transformation Services or updatable subscriptions.
2117616Only members of the sysadmin fixed server role, db_owner fixed database role, or the creator of the subscription can change the subscription properties.
2117716Could not create column list because it is too long. Create the list manually.
2117816Data Transformation Services (DTS) properties cannot be set because the publication does not allow transformable subscriptions using DTS. To allow transformable subscriptions, you must drop the publication and then and re-create it, specifying that transformable subscriptions are allowed.
2117916Invalid @dts_package_location parameter value. Valid options are ‘Distributor’ or ‘Subscriber’.
2118016A publication that allows DTS cannot be enabled for updatable subscriptions.
2118116@dts_package_name can be set for push subscriptions only.
2118216The @agent_type parameter must be one of ‘distribution’, ‘merge’, or NULL.
2118316Invalid property name ‘%s’.
2118416%s parameter is incorrect: it should be ‘%s’, ‘%s’ or ‘%s’.
2118516The subscription is not initialized or not created for failover mode operations.
2118616Subscription for Publisher ‘%s’ does not have a valid queue_id.
2118716The current mode is the same as the requested mode.
2118810Changed update mode from [%s] to [%s].
2118916The queue for this subscription with queue_id = ‘%s’ is not empty. Run the Queue Reader Agent to make sure the queue is empty before setting mode from [queued] to [immediate].
2119010Overriding queue check for setting mode from [%s] to [%s].
2119216MSrepl_tran_version column is a predefined column used for replication and can be only of data type uniqueidentifier
2119316@identity_range, @pub_identity_range, or @threshold cannot be NULL when @identityrangemanagementoption is set to AUTO.
2119416Cannot support identity range management because this table does not have an identity column.
2119516A valid identity range is not available. Check the data type of the identity column.
2119616Identity automation failed.
2119716Failed to allocate new identity range.
2119816Schema replication failed.
2119916This change cannot take effect until you run the snapshot again.
2120016Publication ‘%s’ does not exist.
2120116Dropping a column that is being used by a merge filter clause is not allowed.
2120216It is not possible to drop column ‘%s’ to article ‘%s’ because the snapshot for publication ‘%s’ has already been run.
2120310Duplicate rows found in %s. Unique index not created.
2120416The publication ‘%s’ does not allow subscription copy or its subscription has not been synchronized.
2120516The subscription cannot be attached because the publication does not allow subscription copies to synchronize changes.
2120616Cannot resolve load hint for object %d because the object is not a user table.
2120716Cannot find source object ID information for article %d.
2120816This step failed because column ‘%s’ exists in the vertical partition.
2120916This step failed because column ‘%s’ does not exist in the vertical partition.
2121016The publication must be immediate_sync type to allow subscription copy.
2121116The database is attached from a subscription copy file without using sp_attach_subscription. Drop the database and reattach it using sp_attach_subscription.
2121216Cannot copy subscription. Only single file subscription databases are supported for this operation.
2121316Subscribers cannot subscribe to publications that allow DTS without using a DTS package.
2121416Cannot create file ‘%s’ because it already exists.
2121516An alternate synchronization partner can be configured only at the Publisher.
2121616Publisher ‘%s’, publisher database ‘%s’, and publication ‘%s’ are not valid synchronization partners.
2121710Publication of ‘%s’ data from Publisher ‘%s’.
2121816The creation_script property cannot be NULL if a schema option of 0x0000000000000000 is specified for the article.
2121916The specified source object must be a stored procedure object if it is published as a ‘proc schema only’ type article.
2122016Unable to add the article ‘%s’ because a snapshot has been generated for the publication ‘%s’.
2122116The specified source object must be a view object if it is going to be as a ‘view schema only’ type article.
2122216The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, 0x00001000, 0x00002000, 0x00400000, 0x02000000, 0x08000000, 0x10000000, 0x20000000, 0x40000000, and 0x80000000.
2122316The @pre_creation_command parameter for a schema only article must be either ‘none’ or ‘drop’.
2122416‘%s’ is not a valid property for a schema only article.
2122516The ‘offload_server’ property cannot be NULL or empty if the pull subscription agent is to be enabled for remote activation.
2122616The database ‘%s’ does not have a pull subscription to the specified publication.
2122716The ‘offload_server’ property cannot be the same as the Subscriber server name.
2122816The specified source object must be a user-defined function object if it is going to be published as a ‘func schema only’ type article.
2122916The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, 0x00002000, 0x00040000, 0x00100000, 0x00200000, 0x00400000, 0x00800000, 0x01000000, 0x08000000, 0x40000000, and 0x80000000.
2123016Do not call this stored procedure for schema change because the current database is not enabled for replication.
2123116Automatic identity range support is useful only for publications that allow updating subscribers.
2123216Identity range values must be positive integers that are greater than 1.
2123316Threshold value must be from 1 through 100.
2123416Cannot use the INSERT command because the table has an identity column. The insert custom stored procedure must be used to set ‘identity_insert’ settings at the Subscriber.
2123516Article property ‘%s’ can be set only when the article uses automatic identity range management.
2123616The subscription(s) to Publisher ‘%s’ does not allow subscription copy or it has not been synchronized.
2123716There is a push subscription to Publisher ‘%s’. Only pull and anonymous subscriptions can be copied.
2123816This database either is a publisher, or there is a push subscription to publication ‘%s’. Only pull and anonymous subscriptions can be copied.
2123916Cannot copy subscriptions because there is no synchronized subscription found in the database.
2124016The table ‘%s’ is already published as another article with a different automatic identity support option.
2124116The threshold value should be from 1 through 100.
2124216Conflict table for article ‘%s’ could not be created successfully.
2124316Publisher ‘%s’, publication database ‘%s’, and publication ‘%s’ could not be added to the list of synchronization partners.
2124416Character mode publication does not support vertical filtering when the base table does not support column-level tracking.
2124516Table ‘%s’ is not part of publication ‘%s’.
2124616This step failed because table ‘%s’ is not part of any publication.
2124716Cannot create file at ‘%s’. Ensure the file path is valid.
2124816Cannot attach subscription file ‘%s’. Ensure the file path is valid and the file is updatable.
2124916OLE DB or ODBC Subscribers cannot subscribe to article ‘%s’ in publication ‘%s’ because the article has a timestamp column and the publication is ‘allow_queued_tran’ (allows queued updating subscriptions).
2125016Primary key column ‘%s’ cannot be excluded from a vertical partition.
2125116Publisher ‘%s’, publisher database ‘%s’, publication ‘%s’ could not be removed from the list of synchronization partners.
2125216It is invalid to remove the default Publisher ‘%s’, publication database ‘%s’, and publication ‘%s’ from the list of synchronization partners
2125316Parameter ‘@add_to_active_directory’ cannot be set to TRUE because Active Directory client package is not installed properly on the machine where SQL Server is running.
2125416The Active Directory operation on publication ‘%s’ could not be completed because Active Directory client package is not installed properly on the machine where SQL Server is running.
2125516Column ‘%s’ already exists in table ‘%s’.
2125616A column used in filter clause ‘%s’ either does not exist in the table ‘%s’ or cannot be excluded from the current partition.
2125716Invalid property ‘%s’ for article ‘%s’.
2125816You must first drop all existing merge publications to add an anonymous or local subscription to database ‘%s’.
2125916Invalid property value ‘%s’. See SQL Server Books Online for a list of valid parameters for sp_changemergearticle.
2126016Schema replication failed because database ‘%s’ on server ‘%s’ is not the original Publisher of table ‘%s’.
2126116The offload server must be specified if the agent for this subscription is to be offloaded for remote execution.
2126216Failed to drop column ‘%s’ from the partition because a computed column is accessing it.
2126316Parameter ‘%s’ cannot be NULL or an empty string.
2126416Column ‘%s’ cannot be dropped from table ‘%s’ because it is a primary key column.
2126516Column ‘%s’ cannot be dropped from table ‘%s’ because there is a unique index accessing this column.
2126616Cannot publish table ‘%s’ for both a merge publication and a publication with the updatable subscribers option.
2126710Invalid value for queue type was specified. Valid values = (%s).
2126810Cannot change the parameter %s while there are subscriptions to the publication.
2126916Cannot add a computed column or a timestamp column to a vertical partition for a character mode publication.
2127010Queued snapshot publication property ‘%s’ cannot have the value ‘%s’.
2127216Cannot clean up the meta data for publication ‘%s’ because other publications are using one or more articles in this publication.
2127316You must upgrade the Subscriber to SQL Server 2000 to create updatable subscriptions when the Publisher is SQL Server 2000 or higher.
2127416Invalid publication name ‘%s’.
2127516Cannot publish the schema-bound view ‘%ls’. The value specified for the @type parameter must be “indexed view schema only” (for snapshot or transactional replication) or “indexed view logbased” (for transactional replication only).
2127616The type must be ‘table’ or ‘( view | indexed view | proc | func ) schema only’.
2127716Cannot publish the source object ‘%ls’. The value specified for the @type parameter (“indexed view schema only” or “indexed view logbased”) can be used only for indexed views. Either specify a value of “view schema only” for the @type parameter, or modify the view to be schema bound with a unique clustered index.
2127816Cannot publish the source object ‘%ls’. The value specified for the @type parameter (“indexed view logbased”) requires that the view be schema bound with a unique clustered index. Either specify a value of “view schema only” for the @type parameter, or modify the view to be schema bound with a unique clustered index.
2127916The ‘schema_option’ property for a merge article cannot be changed after a snapshot is generated for the publication. To change the ‘schema_option’ property of this article the corresponding merge publication must be dropped and re-created.
2128016Publication ‘%s’ cannot be subscribed to by Subscriber database ‘%s’ because it contains one or more articles that have been subscribed to by the same Subscriber database at transaction level.
2128116Publication ‘%s’ cannot be subscribed to by Subscriber database ‘%s’ because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level.
2128216@identity_range, @pub_identity_range, and @threshold must be NULL when @identityrangemanagementoption is set to ‘none’ or ‘manual’.
2128316Column ‘%s’ of table ‘%s’ cannot be excluded from a vertical partition because there is a computed column that depends on it.
2128416Failed to drop column ‘%s’ from table ‘%s’.
2128516Failed to add column ‘%s’ to table ‘%s’.
2128616Conflict table ‘%s’ does not exist.
2128716The specified @destination_folder is not a valid path of an existing folder.
2128816Could not create the snapshot directory structure in the specified @destination_folder.
2128916Either the snapshot files have not been generated or they have been cleaned up.
2129016The identity range value provided has exceeded the maximum value allowed.
2129116The specified automatic identity support parameters conflict with the settings in another article.
2129216Object ‘%s’ cannot be published twice in the same publication.
2129310Warning: adding updatable subscription for article ‘%s’ may cause data inconsistency as the source table is already subscribed to ‘%s’
2129416Either @publisher (and @publisher_db) or @subscriber (and @subscriber_db) must be specified, but both cannot be specified.
2129516Publication ‘%s’ does not contain any article that uses automatic identity range management.
2129616Parameter @resync_type must be either 0, 1, 2.
2129716Invalid resync type. No validation has been performed for this subscription.
2129816Failed to resynchronize this subscription.
2129916Invalid Subscriber partition validation expression ‘%s’.
2130010The resolver information was specified without specifying the resolver to be used for article ‘%s’. The default resolver will be used.
2130116The resolver information should be specified while using the ‘%s’ resolver.
2130216The resolver information should specify a column with data type, datetime, or smalldatetime while using the ‘%s’ resolver.
2130316The article ‘%s’ should enable column tracking to use the ‘%s’ resolver. The default resolver will be used to resolve conflicts on this article.
2130416The merge triggers could not be created on the table ‘%s’.
2130516The schema change information could not be updated at the subscription database.
2130616The copy of the subscription could not be made because the subscription to publication ‘%s’ has expired.
2130716The subscription could not be attached because the subscription to publication ‘%s’ has expired.
2130810Rowcount validation profile.
2130910Profile used by the Merge Agent to perform rowcount validation.
2131010Rowcount and checksum validation profile.
2131110Profile used by the Merge Agent to perform rowcount and checksum validation.
2131210Cannot change this publication property because there are active subscriptions to this publication.
2131310Subscriber partition validation expression must be NULL for static publications.
2131410There must be one and only one of ‘%s’ and ‘%s’ that is not NULL.
2131510Failed to adjust Publisher identity range for table ‘%s’.
2131610Failed to adjust Publisher identity range for publication ‘%s’.
2131710A push subscription to the publication ‘%s’ already exists. Use sp_mergesubscription_cleanup to drop defunct push subscriptions.
2131810Table ‘%s’ must have at least one column that is included in the vertical partition.
2131916Could not find the Snapshot Agent command line for the specified publication. Check that a valid regular snapshot job exists on the distributor.
2132016The version of the Distributor cannot be lower than the version of the Publisher.
2132116The parameter @dynamic_snapshot_location cannot be an empty string.
2132216This publication logs conflicts on both replicas. Pre-SQL Server 2005 subscribers will not honor this setting.
2132316A dynamic snapshot job can be scheduled only for a publication with dynamic filtering enabled.
2132416A Snapshot Agent must be added for the specified publication before a dynamic snapshot job can be scheduled.
2132516Could not find the Snapshot Agent ID for the specified publication.
2132616Could not find the dynamic snapshot job with a ‘%ls’ of ‘%ls’ for the specified publication.
2132716‘%ls’ is not a valid dynamic snapshot job name.
2132816The specified dynamic snapshot job name ‘%ls’ is already in use. Try the operation again with a different job name.
2132916Only one of the parameters, @dynamic_snapshot_jobid or @dynamic_snapshot_jobname, can be specified with a nondefault value.
2133016Cannot create a sub-directory under the snapshot folder (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to create a sub-directory under the snapshot folder.
2133116Cannot copy user script file to the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available, and that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories.
2133216Failed to retrieve information about the publication : %ls. Check the name again.
2133316A generation that was expected to be in %s.dbo.MSmerge_genhistory could not be found. If this error occurred in a subscription database, reinitialize the subscription. If this error occurred in a publication database, restore the database from a backup.
2133416Cannot initialize Message Queuing-based subscription because the platform is not Message Queuing %s compliant
2133516Warning: column ‘%s’ already exists in the vertical partition.
2133616Warning: column ‘%s’ does not exist in the vertical partition.
2133716Invalid @subscriber_type value. Valid options are ‘local’ and ‘global’.
2133816Cannot execute sp_dropmergearticle if the publication has a Subscriber that is running on a version of SQL Server 2000 or earlier. Drop and re-create the publication without the article ‘%s’ or set the publication compatibility level of publication ‘%s’ to ’90RTM’ before calling sp_dropmergearticle.
2133910Warning: the publication uses a feature that is only supported only by subscribers running ‘%s’ or higher.
2134016On Demand user script cannot be applied to the snapshot publication.
2134116@dynamic_snapshot_location cannot be a non-empty string while @alt_snapshot_folder is neither empty nor null.
2134216@dynamic_snapshot_location cannot be a non-empty string while @use_ftp is ‘true’.
2134316Could not find stored procedure ‘%s’.
2134416Invalid value specified for %ls parameter.
2134516Excluding the last column in the partition is not allowed.
2134616Failed to change the owner of ‘%s’ to ‘%s’.
2134716Column ‘%s’ cannot be excluded from the vertical partitioning because there is a unique index accessing this column.
2134816Invalid property name ‘%s’.
2134910Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication ‘%s’ because decentralized conflict logging is designated.
2135010Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because a compressed snapshot is used.
2135110Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because vertical filters are being used.
2135210Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because schema replication is performed.
2135310Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication ‘%s’ because publication wide reinitialization is performed.
2135410Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because publication wide reinitialization is performed.
2135510Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication ‘%s’ because merge metadata cleanup task is performed.
2135610Warning: only Subscribers running SQL Server 7.0 Service Pack 2 or later can synchronize with publication ‘%s’ because publication wide validation task is performed.
2135710Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because data types new in SQL Server 2000 exist in one of its articles.
2135810Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because at least one timestamp column exists in one of its articles.
2135910Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because automatic identity ranges are being used.
2136010Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because a new article has been added to the publication after its snapshot has been generated.
2136116The specified @agent_jobid is not a valid job id for a ‘%s’ agent job.
2136216Merge filter ‘%s’ does not exist.
2136316Failed to add publication ‘%s’ to Active Directory. %s
2136416Could not add article ‘%s’ because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
2136516Could not add article ‘%s’ because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions.
2136616Could not add filter ‘%s’ because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
2136716Could not add filter ‘%s’ because there are active subscriptions. Set @force_reinit_subscription to 1 to force this and reinitialize the active subscriptions.
2136816The specified offload server name contains the invalid character ‘%s’.
2136916Could not remove publication ‘%s’ from Active Directory.
2137016The resync date specified ‘%s’ is not a valid date.
2137110Could not propagate the change on publication ‘%s’ to Active Directory.
2137216Cannot drop filter ‘%s’ from publication ‘%s’ because its snapshot has been run and this publication could have active subscriptions. Set @force_reinit_subscription to 1 to reinitialize all subscriptions and drop the filter.
2137311Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available.
2137410Upgrading distribution settings and system objects in database %s.
2137510Upgrading publication settings and system objects in database %s.
2137611Could not open database %s. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the database is available.
2137710Upgrading subscription settings and system objects in database %s.
2137816Could not open distribution database %s because it is offline or being recovered. Replication settings and system objects could not be upgraded. Be sure this database is available and run sp_vupgrade_replication again.
2137916Cannot drop article ‘%s’ from publication ‘%s’ because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
2138016Cannot add timestamp column without forcing reinitialization. Set @force_reinit_subscription to 1 to force reinitialization.
2138116Cannot add (drop) column to table ‘%s’ because the table belongs to publication(s) with an active updatable subscription. Set @force_reinit_subscription to 1 to force reinitialization.
2138216Cannot drop filter ‘%s’ because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force this and invalidate the existing snapshot.
2138316Cannot enable a merge publication on this server because the working directory of its Distributors is not using a UNC path.
2138416The specified subscription does not exist or has not been synchronized yet.
2138516Snapshot failed to process publication ‘%s’. Possibly due to active schema change activity or new articles being added.
2138616Schema change failed on object ‘%s’. Possibly due to active snapshot or other schema change activity.
2138716The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider using the default mechanism instead of the dynamic snapshot for initializing the specified subscription.
2138810The concurrent snapshot for publication ‘%s’ is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication must be restarted until a complete snapshot is generated.
2138910Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because column-level collation is scripted out with the article schema creation script.
2139010Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because extended properties are scripted out with the article schema creation script.
2139110Warning: only Subscribers running SQL Server 2000 or later can synchronize with publication ‘%s’ because it contains schema-only articles.
2139216Row filter(%s) is invalid for column partition(%s) for article ‘%s’ in publication ‘%s’.
2139316Dropping row filter(%s) for article ‘%s’ in ‘%s’. Reissue sp_articlefilter and sp_articleview to create a row filter.
2139416Invalid schema option specified for publication that allows updating subscribers. Need to set the schema option to include DRI constraints.
2139510This column cannot be included in a transactional publication because the column ID is greater than 255.
2139616The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Server Books Online for a list of valid values.
2139716The transactions required for synchronizing the nosync subscription created from the specified backup are unavailable at the Distributor. Retry the operation again with a more up-to-date log, differential, or full database backup.
2139816Could not complete setting up the no-sync subscription at the Distributor while the distribution cleanup agent is running. The operation has a greater chance of success if the distribution cleanup agent is temporarily disabled.
2139916The transactions required for synchronizing the subscription with the specified log sequence number (LSN) are unavailable at the Distributor. Specify a higher LSN.
2140016Article property must be changed at the original Publisher of article ‘%s’.
2140116Article name cannot be ‘all’.
2140216Incorrect value for parameter ‘%s’.
2140310The ‘max_concurrent_dynamic_snapshots’ publication property must be greater than or equal to zero.
2140410‘%s’ is not a valid value for the ‘%s’ parameter. The value must be a positive integer greater than 300 or 0.
2140510‘%s’ is not a valid value for the ‘%s’ parameter. The value must be an integer greater than or equal to %d.
2140610‘%s’ is not a valid value for the ‘%s’ parameter. The value must be 0 or 1.
2140716Cannot create the subscription. If you specify a value of “initialize with backup” for the @sync_type parameter, you must subscribe to all articles in the publication by specifying a value of “all” for the @article parameter.
2140816Cannot create the subscription. You must specify a value of “Active” or “Subscribed” for the @status parameter. This is because the value specified for the @sync_type parameter is “initialize with backup” or “replication support only”.
2140916Only one of parameters %s and %s can be set.
2141016Snapshot Agent startup message.
2141116Distribution Agent startup message.
2141216Merge Agent startup message.
2141316Failed to acquire the application lock indicating the front of the queue.
2141410Unexpected failure acquiring an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available.
2141510Unexpected failure releasing an application lock. Ensure that the account under which the Merge Agent runs is a member of the publication access list. If there is a lot of activity on the server, run the Merge Agent when there are more server resources available.
2141610Property ‘%s’ of article ‘%s’ cannot be changed.
2141710Having a queue timeout value of over 12 hours is not allowed.
2141910Filter ‘%s’ of article ‘%s’ cannot be changed.
2142010Subscription property ‘%s’ cannot be changed.
2142110Article ‘%s’ cannot be dropped because there are other articles using it as a join article.
2142216Queue Reader Agent startup message.
2142316Either the publication ‘%s’ does not exist or you do not have sufficient permissions to access it. Ensure that the publication exists and that the account under which the Merge Agent connects to the Publisher is included in the publication access list (PAL).
2142416The @publisher parameter must be NULL for SQL Server publishers.
2142516The @publisher parameter may not be NULL for heterogeneous publishers.
2142616No shared agent subscription exists for publication ‘%s’ and the subscriber/subscriber database pair ‘%s’/’%s’.
2142816‘memory_optimized’ property can be enabled only for SQL Server Subscriber.
2142916Changing from sql subscriber to a non-sql subscriber is not allowed when the memory-optimized property is enabled.
2143016The use of P2P Replication is not supported for subscription with memory-optimized tables.
2145016The replication %s could not be upgraded for %s databases. Ensure that %s is upgraded and execute %s again.
2145116The %s %s (%s) login (%s) password has been changed.
2145210Warning: The %s agent job has been implicitly created and will run under the SQL Server Agent Service Account.
2145416The internal procedure sp_MStran_is_snapshot_required must be executed at the Distributor if the @run_at_distributor parameter has a value of 1. If the problem persists, contact Microsoft Customer Support Services.
2145616Value provided for parameter %s is not valid.
2146016The primary key for source table “%s” includes the timestamp column “%s”. Cannot create the article for the specified publication because it allows updating Subscribers.
2148116Cannot create replication subscription(s) in the master database. Choose another database for creating subscriptions.
2148216%s can only be executed in the “%s” database.
2148416Article validation was requested for snapshot publication “%s”. Article validation is only valid for transactional publications.
2148516Tracer tokens cannot be posted for a snapshot publication.
2148616An error occurred while logging the tracer token history information. The tracer token could not be posted.
2148716An error occurred while inserting the tracer token to the log. The tracer token could not be posted.
2148816No active subscriptions were found. The publication must have active subscriptions in order to post a tracer token.
2148916A database ‘%s’ already exists. If you intend this to be your distribution database set @existing_db = 1.
2149016The value specified for the %s parameter of sp_mergearticlecolumn must be ‘%s’. A value of ‘true’ is allowed only when this procedure is called by another replication procedure. Either set the value of the @schema_replication parameter to ‘false’ or do not specify a value.
2149916The procedure %s failed to %s the resource %s. Server error = %d.
2150010Invalid subscription type is specified. A subscription to publication ‘%s’ already exists in the database with a different subscription type.
2150110The supplied resolver information does not specify a valid column name to be used for conflict resolution by ‘%s’.
2150210The publication ‘%s’ does not allow the subscription to synchronize to an alternate synchronization partner.
2150310Cleanup of merge meta data cannot be performed while merge processes are running. Retry this operation after the merge processes have completed.
2150410Cleanup of merge meta data at republisher ‘%s’.’%s’ could not be performed because merge processes are propagating changes to the republisher. All subscriptions to this republisher must be reinitialized.
2150510Changes to publication ‘%s’ cannot be merged because it has been marked inactive.
2150610sp_mergecompletecleanup cannot be executed before sp_mergepreparecleanup is executed. Use sp_mergepreparecleanup to initiate the first phase of merge meta data cleanup.
2150710All prerequisites for cleaning up merge meta data have been completed. Execute sp_mergecompletecleanup to initiate the final phase of merge meta data cleanup.
2150810Cleanup of merge meta data cannot be performed while merge processes are running. Cleanup will proceed after the merge processes have completed.
2150910Cleanup of merge meta data cannot be performed because some republishers have not quiesced their changes. Cleanup will proceed after all republishers have quiesced their changes.
2151010Data changes are not allowed while cleanup of merge meta data is in progress.
2151110Neither MSmerge_contents nor MSmerge_tombstone contain meta data for this row.
2151218%ls: The %ls parameter is shorter than the minimum required size.
2151416Cannot complete the requested operation in the subscription database because a snapshot is currently being delivered to the database. Perform the operation again at a later time. To stop the delivery of the snapshot, stop the Distribution Agent or Merge Agent associated with the subscription.
2151518Replication custom procedures will not be scripted because the specified publication ‘%s’ is a snapshot publication.
2151610Transactional replication custom procedures for publication ‘%s’ from database ‘%s’:
2151710Replication custom procedures will not be scripted for article ‘%s’ because the auto-generate custom procedures schema option is not enabled.
2151810Replication custom procedures for article ‘%s’:
2151910Custom procedures will not be scripted for article update commands based on direct INSERT, UPDATE, or DELETE statements.
2152010Custom procedure will not be scripted because ‘%s’ is not a recognized article update command syntax.
2152116Some generation values are above the upper limit of %d used in SQL Server 2000. Change the publication_compatibility_level of the publication to 90 to make this work.
2152216This article cannot use the ‘%s’ feature because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication ‘%s’ to ’90RTM’.
2152316Adding column ‘%s’ to table ‘%s’ failed. Articles can have at most %d columns, including columns that have been filtered.
2152516A lightweight replica must be anonymous.
2152616Article ‘%s’ already belongs to a subscription with a different value for the @lightweight property.
2152716Publication ‘%s’ cannot be added to database ‘%s’, because a publication with a lower compatibility level already exists. All merge publications in a database must have the same compatibility level.
2152816Publication ‘%s’ cannot be added to database ‘%s’, because a publication with a higher compatibility level already exists. All merge publications in a database must have the same compatibiliy level.
2153010The schema change failed during execution of an internal replication procedure. For corrective action, see the other error messages that accompany this error message.
2153110The data definition language (DDL) command cannot be executed at the Subscriber. DDL commands can only be executed at the Publisher. In a republishing hierarchy, DDL commands can only be executed at the root Publisher, not at any of the republishing Subscribers.
2153210Cannot add a data definition language trigger for replicating ‘%.*ls’ events.
2153310Cannot insert information into the schema change tracking table sysmergeschemachange.
2153516The article ‘%s’ is already published in another publication, and is set to use nonoverlapping partitions with multiple subscribers per partition (@partition_options = 2). This setting does not permit the article to be included in more than one publication.
2153716The column ‘%s’ in table ‘%s’ is involved in a foreign key relationship with a column in table ‘%s’, but this column was not found in the specified join clause. A logical record relationship between these tables should include this column.
2153816Table ‘%s’ cannot have table ‘%s’ as a parent in a logical record relationship because it already has a different parent table. A logical record relationship allows only one parent table for a given child table.
2153916A logical record relationship, specified by the @filter_type parameter, requires a one-to-one or a one-to-many join from the parent table to the child table. Either change the value of the @filter_type parameter, or set the @join_unique_key parameter to 1.
2154016You cannot drop a column defined as data type uniqueidentifier with the rowguidcol property because merge replication uses this column for tracking. To drop the column, you must first drop the table from all publications and subscriptions.
2154116Cannot complete ALTER TABLE command. Do not execute the command ‘ALTER TABLE table_name DISABLE TRIGGER ALL’ on a published table. Reissue multiple ‘ALTER TABLE table_name DISABLE TRIGGER trigger_name’ statements to disable each trigger individually on the given table.
2154216Encountered server error %d while executing <%s>.
2154316The schema for the article %s was either not generated properly or was not applied properly during initial synchronization. This may be due to permissions issues. Verify whether the object exists, and whether the necessary permissions are granted.
2154410Value specified for the publication property replicate_ddl is not valid. The value must be 1 or 0.
2154516You cannot disable a trigger used by merge replication on a published table. To drop the trigger, drop the table from the publication.
2154616Cannot replicate the ALTER TABLE command. It contains multiple DROP commands, including a DROP command for a column that is not included in all subscriptions to this article. Use a single DROP command in each ALTER TABLE command.
2154716Encountered server error %d while restoring the log for database %s.
2154816Cannot execute sp_change_subscription_properties. This stored procedure can only be used for publications that have at least one pull subscription.
2154916Cannot add the computed column ‘%s’ to the publication. You must first add all columns on which this column depends; you cannot filter any of these colunmns from the article.
2155016Before you drop the column from the publication, all computed columns that depend on column ‘%s’ must be dropped.
2155116Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation.
2155216Merge data definition language (DDL) error: Dropping a column used in a row filter or a join filter is not allowed. To drop a column used in a row filter, first change the row filter using sp_changemergearticle. To drop a column used in a join filter, first drop the join filter using sp_dropmergefilter.
2156116The value specified for parameter %s = %d is not valid.
2156416The table %s contains the column msrepl_tran_version, which is used by replication. The column is set to NULL, but it must be set to NOT NULL. Replication failed to alter this column, so you must drop the column and then add the table as an article again using sp_addarticle. Replication will then add the column to the table.
2156716The call format VCALL cannot be used for the specified article. VCALL format can be used only for articles in publications that allow updating subscriptions. If you do not require updating subscriptions, specify a different call format. If you do require updating subscriptions, you must drop the publication and re-create it to specify that updating subscriptions are allowed.
2156916The article %s in the publication %s does not have a valid conflict table entry in the system table sysarticleupdates. This entry is required for publications that allow queued updating subscriptions. Check for errors in the last run of the Snapshot Agent.
2157016Cannot create the logical record relationship. Table ‘%s’ does not have a foreign key referencing table ‘%s’. A logical record relationship requires a foreign key relationship between the parent and child tables.
2157116Cannot create the logical record relationship in publication ‘%s’. The use_partition_groups option for the publication must be set to “true” in order to use logical records. Use sp_changemergepublication to set the option to “true”.
2157216Cannot add a logical record relationship because the foreign key constraint ‘%s’ on table ‘%s’ is disabled. To create the logical record relationship, first enable the foreign key constraint.
2157316Cannot add a logical record relationship because the foreign key constraint ‘%s’ on table ‘%s’ is defined with the NOT FOR REPLICATION option. To add the logical record relationship, first drop the foreign key constraint, and then re-create it without the NOT FOR REPLICATION option.
2157416Cannot add a logical record relationship because the article ‘%s’ is published in publication ‘%s’, which has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM.
2157516The value specified for the property filter_type is not valid. Valid values are 1 (join filter only), 2 (logical record relation only), and 3 (join filter and logical record relation).
2157616Cannot add a logical record relationship between tables ‘%s’ and ‘%s’ because the foreign key column ‘%s’ in table ‘%s’ allows NULL values. Alter the column to disallow NULL values.
2157816In order to use partition_options of 2 (non overlapping partitions with multiple subscriptions per partition) or 3 (non overlapping partitions one subscription per partition) the publication ‘%s’ must be enabled to use partition groups functionality. Use sp_changemergepublication to set ‘use_partition_groups’ to ‘true’.
2157916Article “%s” in publication “%s” does not qualify for the partition option that you specified. You cannot specify a value of  2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in multiple join filters. Either select a value of 0 or 1 for the @partition_options parameter, or drop all but one of the join filters by using sp_dropmergefilter.
2158016Article “%s” in publication “%s” does not qualify for the partition option that you specified. You cannot specify a value of  2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article is involved in both a row filter and a join filter. Either select a value of 0 or 1 for the @partition_options parameter; drop the join filter by using sp_dropmergefilter; or change the row filter by using sp_changemergepublication.
2158116Article “%s” in publication “%s” does not qualify for the partition option that you specified. You cannot specify a value of  2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a join filter with a join_unique_key value of 0. Either select a value of 0 or 1 for the @partition_options parameter, or use sp_changemergefilter to specify a value of 1 for join_unique_key.
2158216Article “%s” in publication “%s” does not qualify for the partition option that you specified. You cannot specify a value of  2 or 3 (nonoverlapping partitions) for the @partition_options parameter because the article has a direct or indirect join filter relationship with parent article “%s”. The parent article does not use the same value for partition_options. Use sp_changemergepublication to change the value for one of the articles.
2158316Cannot update the column in article ‘%s’. The article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property, and the column is involved in a row filter and/or a join filter. In this situation, the column cannot be updated at a Subscriber or republisher; it must be updated at the top-level Publisher.
2158416Cannot insert the row for article ‘%s’. The row does not belong to the Subscriber’s partition, and the article has a value of 2 or 3 (nonoverlapping partitions) for the partition_options property. Nonoverlapping partitions do not allow out-of-partition inserts.
2158516Cannot specify custom article ordering in publication ‘%s’ because the publication has a compatibility level lower than 90RTM. Use sp_changemergepublication to set the publication_compatibility_level to 90RTM.
2159716The article includes only the rowguidcol column. You must publish at least one other column.
2159816Modifying DDL triggers created by replication is disallowed since these are required to track DDL changes.
2159916The parameters @article and @join_articlename cannot have the same value. Specify different articles for the two parameters; self-joins are not permitted.
2160016Non-SQL Server Publisher [%s] cannot be found. Execute sp_helpdistpublishers to view a list of available Publishers.
2160116The value of the parameter @type must be ‘logbased’ for Oracle publications.
2160316The refresh of Oracle publisher ‘%s’ by sp_refresh_heterogeneous_publisher was not successful. The Oracle publisher meta data has been retained in its failed state to help in diagnosing the cause of the failure. When the problem has been diagnosed and resolved, rerun sp_refresh_heterogeneous_publisher to complete the refresh.
2160416The non-SQL Server Publisher vendor is not valid. Attempt to add the Publisher again. If the problem persists, contact Microsoft Customer Support Services.
2160516Non-SQL Server Publishers must be configured in the context of the distribution database. Execute sp_adddistpublisher in the context of the distribution database.
2160616Parameter “%s” is for non-SQL Server Publishers only. The value of this parameter must be “%s” for a SQL Server Publisher.
2160716sp_refresh_heterogeneous_publisher was unable to obtain publisher information for Oracle publisher ‘%s’. sp_refresh_heterogeneous_publisher may only be called to refresh Oracle publishers currently defined at the distributor.
2160816Cannot use a value of TRUE for the parameter @ignore_distributor. The value must be FALSE for a non-SQL Server Publisher.
2160916Non-SQL Server publications do not support updatable subscriptions. The properties allow_sync_tran and allow_queued_tran must be “false”.
2161016The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher ‘%s’ did not alter any meta data at the Oracle publisher. Make certain that the correct Oracle publisher has been identified and that the requirements for refreshing the Oracle publisher have been met.
2161116Cannot drop the distribution Publisher “%s” because it has publications defined. Drop the publications first.
2161216For non-SQL Server Publishers, the value of the @sync_method parameter must be “character” or “concurrent_c”.
2161316Constraint column ‘%s’ not found in table ‘%s’.
2161416Index column ‘%s’ not found in table ‘%s’,
2161516Unable to find table information for article %s. Local distributor cache may be corrupt.
2161616Cannot find column [%s] in the article. Verify that the column exists in the underlying table, and that it is included in the article.
2161716Unable to run SQL*PLUS. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21617 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2161816The Publisher ‘%s’ does not exist. To view a list of Publishers, use the stored procedure sp_helpdistpublisher.
2161916Must provide both @SelectColumnList and @InsColumnList.
2162016The version of SQL*PLUS that is accessible through the system Path variable is not current enough to support Oracle publishing. Make certain that a current version of the Oracle client code is installed at the distributor. For addition information, see SQL Server Error 21620 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2162116Unable to create the public synonym %s. Verify that the replication administrative user has been granted the CREATE SYNONYM permission.
2162216Unable to grant SELECT permission on the public synonym %s. Verify that the replication administrative user has sufficient permissions.
2162316Unable to update the public synonym ‘MSSQLSERVERDISTRIBUTOR’ to mark Oracle instance ‘%s’ as a SQL Server publisher.
2162416Unable to locate the registered Oracle OLEDB provider, OraOLEDB.Oracle, at distributor ‘%s’. Make certain that a current version of the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21624 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2162516Unable to update the publisher table HREPL_PUBLISHER at the Oracle instance ‘%s’.
2162616Unable to connect to Oracle database server ‘%s’ using the Oracle OLEDB provider OraOLEDB.Oracle. For addition information, see SQL Server Error 21626 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2162716Unable to connect to Oracle database server ‘%s’ using the Microsoft OLEDB provider MSDAORA. For addition information, see SQL Server Error 21627 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2162816Unable to update the registry of distributor ‘%s’ to allow Oracle OLEDB provider OraOLEDB.Oracle to run in process with SQL Server. Make certain that current login is authorized to modify SQL Server owned registry keys. For addition information, see SQL Server Error 21628 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2162916The CLSID registry key indicating that the Oracle OLEDB Provider for Oracle, OraOLEDB.Oracle, has been registered is not present at the distributor. Make certain that the Oracle OLEDB provider is installed and registered at the distributor. For addition information, see SQL Server Error 21629 in Troubleshooting Oracle Publishers in SQL Server Books Online.
2163016Unable to determine whether the table ‘%s’ is still being published. Contact Customer Support Services.
2163116Cannot unpublish table ‘%s’; the remote call to the Oracle Publisher failed. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect but the problem persists, drop and reconfigure Oracle publishing.
2163216The parameter %s is not supported for non-SQL Server  publications. The value specified for this parameter must be %s.
2163316The publication ‘%s’ could not be added because non-SQL Server Publishers only support the @sync_method parameter values “character” or “concurrent_c”.
2163416The parameter %s does not support the value ‘%s’ when using non-SQL Server publications. The value must be %s.
2163516An unsupported schema option combination was specified. Non-SQL Server publications only support the following schema options: 0x01, 0x02, 0x10, 0x40, 0x80, 0x4000, and 0x8000.
2163716%s is required for heterogeneous publications.
2163816You have specified a value of ‘%s’ for the @repl_freq parameter of sp_addpublication. For non-SQL Server publications, this requires one of the following values for the @sync_method parameter: %s.
2163916Heterogeneous publishers can not use trusted connections, set @trusted to false.
2164016Non-SQL Server Publishers do not support a value of 1 for the parameter @thirdparty_flag. When executing the stored procedure sp_adddistpublisher, specify a value of 0 for the parameter.
2164116The “%s” parameter is for non-SQL Server Publishers only. It must be NULL for SQL Server Publishers.
2164216Heterogeneous publishers require a linked server.  A linked server named ‘%s’ already exists.  Please remove linked server or choose a different publisher name.
2164316The value specified for the parameter ‘%s’ must be MSSQLSERVER, ORACLE, or ORACLE GATEWAY.
2164416%s value of ‘%s’ is not supported for heterogeneous subscribers, must be %s.
2164516The value ‘%s’ is not a valid non-SQL Server Publisher type. For SQL Server 2005, the value must be ORACLE or ORACLE GATEWAY.
2164616The Oracle server [%s] is already defined as the Publisher [%s] on the Distributor [%s].[%s]. Drop the Publisher or drop the public synonym [%s].
2164716The Oracle Publisher support package could not be loaded. Drop the replication administrative user schema and re-create it; ensure it is granted the documented permissions.
2164916Cannot change the property ‘%s’. Non-SQL Server Publishers do not support this property.
2165016The value specified for @rowcount_only for the article ‘%s’ is not 1. For an article in a publication from a non-SQL Server Publisher, 1 is the only valid setting for this parameter.
2165116Failed to execute the HREPL.%s request to Oracle Publisher ‘%s’. Verify that the Oracle package code exists on the Publisher, and that the replication administrative user account has sufficient permissions.
2165316The database management system (DBMS) %s %s does not exist. Verify the supported DBMS and versions by querying msdb.dbo.MSdbms.
2165416The data type %s does not exist. Verify the supported data types and mappings by querying msdb.dbo.sysdatatypemappings.
2165516The data type %s already exists.
2165616The data type mapping for %s does not exist. Verify the list of available mappings by querying msdb.dbo.sysdatatypemappings.
2165716The data type mapping for %s already exists.
2165816The data type mapping does not exist. Verify the list of mappings by querying msdb.dbo.sysdatatypemappings.
2165916Cannot execute this procedure for a SQL Server Publisher. The Publisher must be a non-SQL Server Publisher.
2166016The value specified for the parameter @full_or_fast for article ‘%s’ must be 0, 1, or 2.
2166116The value specified for the @shutdown_agent parameter for article ‘%s’ must be 0 or 1.
2166216The source object [%s].[%s] on the non-SQL Server Publisher was either not found or is not supported. If the object exists, verify that it meets the requirements for being published.
2166316Cannot find a valid primary key for the source table [%s].[%s]. A valid primary key is required to publish the table. Add or correct the primary key definition on the source table.
2166416Index [%s] contains unique nullable column.
2166516Key [%s] contains unique nullable column.
2166616Cannot specify more than %d column names for the index or primary key because this exceeds the maximum number of columns supported by SQL Server. %d columns were specified.
2166716The index “%s” was not created. The index has a key length of at least %d bytes. The maximum key length supported by SQL Server is %d bytes.
2166816The constraint “%s” was not created because one or more columns in the constraint is not published. Either include all columns in the published article, or alter the constraint to remove columns that are not published.
2166916Column [%s] cannot be published because it uses an unsupported data type [%s]. View supported data types by querying msdb.dbo.sysdatatypemappings.
2167016Connection to server [%s] failed.
2167116Cannot execute the procedure. Administration of a non-SQL Server Publisher must be performed at the associated SQL Server Distributor. Execute the procedure at the Distributor.
2167216The login ‘%s’ has insufficient authorization to execute this command.
2167316Test connection to publisher [%s] failed.  Verify authentication information.
2167416Unable to update the linked server [%s] for the login [%s].
2167516Cannot specify more than %d indexes for a single table.  %d indexes specified.  Excess indexes have been ignored.
2167616Heterogeneous subscriber ‘%s’ could not add a subscription for heterogeneous publication ‘%s’ because publication sync method is not ‘character’, ‘concurrent_c’, or ‘database snapshot character’.
2167716Heterogeneous publisher ‘%s’ cannot be defined as a subscriber.
2167816The parameter “%s” can be set to “%s” only when “%s” is set to “%s”.
2167916Peer-to-peer publications only support a ‘%s’ parameter value of %s.
2168016The Distribution Agent was unable to update the cached log sequence numbers (LSNs) for Originator %s, OriginatorDB %s, OriginatorDBVersion %d, OriginatorPublicationID %d. Stop and restart the Distribution Agent. If the problem persists, contact Customer Support Services.
2168116The current user ‘%s’ does not have a valid linked server login mapping for non-SQL Server Publisher [%s].  Replication connects to the Publisher through a linked server; use the stored procedure sp_addlinkedsrvlogin to map the user’s login to this linked server.
2168216Cannot publish table [%s].[%s]. The replication administraive user requires an explicit SELECT grant, or a SELECT grant through PUBLIC, in order to publish this table. A role-based SELECT grant, if one exists, is not sufficient.
2168316Cannot verify administrator login privileges for Oracle Publisher %s. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS.
2168416The replication administrative user for Oracle Publisher “%s” has insufficient permissions. Refer to the script /MSSQL/Install/oracleadmin.sql for the required permissions.
2168516Request ‘%s’ for Oracle schema filter for Oracle publisher ‘%s’ failed.
2168616The operation “%s” is not valid. Valid operations are “add”, “drop”, and “help”.
2168716Schema filters are supported only for Oracle Publishers. The Publisher “%s” is a “%s” Publisher.
2168816The current login ‘%s’ is not in the publication access list (PAL) of any publication at Publisher ‘%s’. Use a login that is in the PAL, or add this login to the PAL.
2168916A NULL @schema value is invalid for add and drop schema filter operations.
2169010The subscriber db cannot be the same as the publisher db when the subscriber is the same as the publisher
2169110sp_mergesubscription_cleanup should be called on the subscription database
2169216Failed to script the subscriber stored procedures for article ‘%s’ in publication ‘%s’
2169416%s cannot be null or empty when %s is set to 0 (SQL Server Authentication). Specify a login or set security mode to 1 (Integrated Authentication).
2169510The replication agent job ‘%s’ was not removed because it has a non-standard name; manually remove the job when it is no longer in use.
2169616The stored procedure only applies to Oracle Publishers. The Publisher ‘%s’ is a %s Publisher.
2169816The parameter ‘%s’ is no longer supported.
2169910Unable to reuse view ‘%s’ because it was not found. Re-creating all system table views. This is an informational message only. No user action is required.
2170116Microsoft SQL Server Additive Conflict Resolver
2170216Microsoft SQL Server Averaging Conflict Resolver
2170316Microsoft SQL Server DATETIME (Earlier Wins) Conflict Resolver
2170416Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver
2170516Microsoft SQL Server Download Only Conflict Resolver
2170616Microsoft SQL Server Maximum Conflict Resolver
2170716Microsoft SQL Server Merge Text Columns Conflict Resolver
2170816Microsoft SQL Server Minimum Conflict Resolver
2170916Microsoft SQL Server Priority Column Resolver
2171016Microsoft SQL Server Subscriber Always Wins Conflict Resolver
2171116Microsoft SQL Server Upload Only Conflict Resolver
2171216Microsoft SQLServer Stored Procedure Resolver
2171516Cannot register the article resolver %s. This can occur if the account under which SQL Server is running does not have access to the distribution database. Add the class ID and the custom resolver name manually to the MSmerge_articleresolver table in the distribution database.
2171716The article resolver name cannot be an empty string or NULL. Specify a valid value for the @article_resolver parameter.
2171816For a COM resolver, the @resolver_clsid cannot be an empty string or NULL. Specify a valid value for @resolver_clsid.
2171910The Subscriber ‘%s’:’%s’ was not marked for reinitialization at the Publisher because the subscription is either anonymous or not valid. Verify that valid values were specified for the @subscriber and @subscriber_db parameters of sp_reinitmergesubscription.
2172016Cannot find a job that matches the ID or name specified in the parameters @dynamic_snapshot_jobid or @dynamic_snapshot_jobname. Verify the values specified for those parameters.
2172110UserScripts
2172216Failed to add an extended trigger for replicating the ‘%.*ls’ event.
2172316The value specified for the @pubid parameter of procedure ‘%s’ is not valid or is NULL. Verify that the Merge Agent is running correctly. Reinitalize the subscription if the problem persists.
2172410Cannot add the foreign key %s with the CASCADE option because table %s is published. Add the NOT FOR REPLICATION clause to the foreign key definition.
2172516Cannot alter the view. An indexed view replicated as a table cannot be altered to a nonindexed view. Drop the view from the publication before attempting to alter it.
2172714Cannot complete the replication operation. The security check for the current user is failing. Only members of the sysadmin fixed server role, or db_owner or db_ddladmin fixed database roles can perform this operation.
2172816The article can support logical record level conflict detection only if it uses logical record conflict resolution.
2172916The @keep_partition_changes property cannot be set to “true.” This is because the @publication_compatibility_level property is set to 90RTM or higher and the @use_partition_groups property is set to “true.” Set a lower compatibility level or set the @use_partition_groups property to “false.”
2173016Table ‘%s’ can not be replicated because it contains imprecise Primary Key column, please recreate table without ‘persisted’ clause and try again.
2173116Cannot add a constraint or default without an explicit name, because the table is included in a publication that replicates DDL events. Specify a unique name for the constraint and then reissue the DDL statement.
2173216Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parameter ‘%s’.
2173316Cannot open database %s. The upgrade of replication %s could not be performed. Run %s again from the %s database when the %s is accessible.
2173416Peer-to-peer publications do not support replicating timestamp columns as varbinary(8). You cannot add an article with this option, nor add or alter a table to include a timestamp column as varbinary(8).
2173516Source object [%s].[%s] is a temporary object and cannot be published.
2173616Unable to relocate the article log table to a different tablespace. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect, but the problem persists, it might be caused by insufficient permissions or insufficient space in the tablespace; check for any Oracle error messages.
2173716The property ‘%s’ is not valid for ‘%s’ Publishers.
2173816The property ‘%s’ is not valid for %s publications.
2173916Cannot alter property ‘%s’. You must first call the stored procedure sp_articleview to initialize the article; the property can then be altered.
2174016Oracle subscriber ‘%s’ not found.  Loopback support cannot be checked.
2174116Unable to retrieve distributor information from Oracle publisher ‘%s’. Bi-directional publishing requires Oracle publisher to exist before the Oracle subscriber.
2174216The Oracle Publisher name is ‘%s’ and the Oracle Subscriber name is ‘%s’. Bidirectional Oracle publishing requires the Oracle Publisher and Subscriber names to be the same.
2174316Unable to retrieve the originator information for the Oracle subscriber ‘%s’.
2174416Oracle bidirectional publishing requires parameter ‘%s’ to have a value of ‘%s’.
2174516Cannot generate a filter view or procedure. Verify that the value specified for the @filter_clause parameter of sp_addarticle can be added to the WHERE clause of a SELECT statement to produce a valid query.
2174616The ‘%s’ character length must not exceed %d.
2174716Cannot establish a connection to the Oracle Publisher ‘%s’. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS.
2174816The article was dropped at the Distributor, but information at the Publisher ‘%s’ was not dropped. No action is required; the information is cleaned up if the Publisher is dropped.
2174916The Publisher was dropped at the Distributor, but information on the Publisher ‘%s’ was not dropped. Connect to the Oracle Publisher with SQL*PLUS and drop the replication administrative user.
2175016The table %s does not have a primary key, which is required for transactional replication. Create a primary key on the table.
2175116Cannot publish view %s as a table because it does not have a unique clustered index. Publish the view as a view, or add a unique clustered index.
2175216The current user %s does not have SELECT permission on the table %s. The user must have SELECT permission to retrieve rows at the Subscriber that have updates pending in the queue.
2175316The table %s, which is specified in the @tablename parameter of sp_getqueuedrows, is not part of any active initialized queued subscription. Ensure your queued subscriptions are properly initialized by running the Snapshot Agent, Distribution Agent, and Queue Reader Agent.
2175416Processing has been terminated. The resultset for sp_getqueuedrows is larger than 16,000, the maximum size that the procedure can return. Run the Queue Reader Agent to flush the queue at the Subscriber before executing this procedure again.
2175516Failed to mark ‘%s’ as a system object.
2175616Based on article settings, table %s should have an identity column, but it does not have one. Verify article settings with sp_helparticle and change them if necessary with sp_changearticle.
2175716The subscription is read-only. The publication that this subscription synchronizes with allows updates at the Subscriber, but a value of ‘read-only’ was specified for the @update_mode parameter of sp_addsubscription. To allow updates, you must drop and then re-create the subscription, specifying a different value for @update_mode.
2175816Cannot find a valid Queue Reader Agent ID for the subscription to Publisher %s, database %s, publication %s. The specified subscription to an updating Subscriber publication is not initialized. Run the Snapshot Agent, Distribution Agent, and Queue Reader Agent to initialize the subscription.
2175916Cannot add the column ‘%s’ to the table ‘%s’. The table already contains the maximum number of columns allowed for an article in a merge publication (246 columns).
2176011Cannot execute the replication script in the ‘master’ database; the current session will be terminated. The script must be executed in the distribution database, and the master database cannot serve as the distribution database.
2176120Cannot execute the replication script; the current session will be terminated. Check for any errors returned by SQL Server during execution of the script.
2176210The distribution database ‘%s’ has a compatibility level of %d, which is different from that of the master database. The two compatibility levels must be the same, so the distribution database level is being changed to %d. This is an informational message only. No user action is required.
2176316Message Queuing Service is not running. Start this service and retry the operation.
2176416Cannot create the publication. Specifying a value of ‘msmq’ for the parameter @queue_type is supported only on Microsoft Windows NT platforms. Specify a value of ‘sql’ for this parameter.
2176510The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow NULLs for updating subscribers.
2176616Table %s contains an identity column that is marked as Not For Replication, but the @identitymanagementoption parameter of sp_addarticle is set to ‘none’. To support immediate updating subscriptions, specify a value of ‘manual’ or ‘auto’  for @identitymanagementoption.
2176710Warning: The parameter ‘%s’ is obsolete and is available only for backwards compatibility. It will not be available in future releases. Instead of this parameter, use the parameter ‘%s’.
2176816When executing sp_adddistributor for a remote Distributor, you must use a password. The password specified for the @password parameter must be the same when the procedure is executed at the Publisher and at the Distributor.
2176910Custom data type mappings are not supported. You must validate the correctness of the mapping. If mappings are not compatible, errors will likely occur when moving data from the Publisher to the Subscriber.
2177010Data type mapping from ‘%s’ to ‘%s’ does not exist.  Review source and destination data type, length, precision, scale, and nullability. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings.
2177116%s is not within the supported range of %d and %d.
2177216Property “%s” requires the parameters @force_invalidate_snapshot and @force_reinit_subscription to be set to “true”.
2177310The distribution database ‘%s’ cannot be opened due to inaccessible files. The database will be dropped, but distribution database cleanup tasks will not occur. Check the database and server error logs for more information about why the database files cannot be accessed.
2177416This procedure is supported only for non-SQL Server Publishers. The Publisher ‘%s’, on which you are executing the procedure, is a SQL Server Publisher.
2177516Failed to generate column bitmap for article ‘%s’.
2177616Failed to generate published column bitmap for article ‘%s’.
2177716Failed to generate article view name for article ‘%s’.
2177816Cannot add Publisher objects to the Oracle Publisher for article ‘%s’. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
2177910Cannot use the specified data type mapping. The matching destination data type for source type %s cannot be found. Query the system table msdb.dbo.sysdatatypemappings for a list of supported mappings. Verify that the length, precision, scale, and nullability of the source type are correct.
2178016The non-SQL Server Publisher is missing one or more %s objects. Drop and re-create the Publisher and the replication administrative user schema.
2178116Unable to retrieve heterogeneous metadata.  Verify connection information
2178216Cannot add primary key column ‘%s’ to article ‘%s’. If the Publisher is a non-SQL Server Publisher, the primary key could have violated SQL Server limits for number and length of columns. For more information, see errors returned by sp_addarticle.
2178316Cannot add the Publisher triggers and the article log table to the Oracle Publisher for the article ‘%s’. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
2178416You must specify a non-NULL value for the @rowfilter parameter.
2178516Failure to query Oracle XactSet Job attributes for publisher ‘%s’.
2178616Failure to refresh Oracle XactSet Job for publisher ‘%s’.
2178716Failure to query Oracle Xact batching enabled flag for publisher ‘%s’.
2178816Invalid parameter passed to sp_IHSetXactBatching.  The bit flag to enable/disable Xact batching must be 0 or 1.
2178916Failure to set the Oracle Xact batching enabled flag for publisher ‘%s’.
2179016Cannot publish the table ‘%s.%s’ from the Publisher ‘%s’. Verify connection information and ensure that you can connect to the Publisher through a tool like SQL*PLUS. Ensure that the replication administrative user schema has the required permissions.
2179116The table ‘%s.%s’ already appears in a transactional publication on Oracle Gateway Publisher ‘%s’. When using the Oracle Gateway option, a table published using transactional replication can only be included in one publication. To publish this table in more than one publication, you must reconfigure the Oracle Publisher to use the Oracle Complete option.
2179216The table ‘%s.%s’ already appears in the transactional publication ‘%s’ on Publisher ‘%s’. The Oracle Gateway publishing option (the default) allows a table to be included as an article in any number of snapshot publications, but only in one transactional publication. To publish a table in more than one transactional publication, use the Oracle Complete publishing option. To change publishing options, you must drop and reconfigure the Publisher.
2179316Non-SQL Server Publishers are supported only in the Enterprise and Developer editions of SQL Server. The edition of this instance is %s.
2179416The value specified for the @propertyname parameter is not valid. Use one of the following values: %s.
2179516The value specified for property %s is not valid. Use one of the following values: %s.
2179616The property “xactsetjobinterval” must be assigned a value greater than or equal to 0.
2179716Cannot create the agent job. ‘%s’ must be a valid Windows login in the form : ‘MACHINE\Login’ or ‘DOMAIN\Login’. See the documentation for ‘%s’.
2179816Cannot execute the replication administrative procedure. The ‘%s’ agent job must be added through ‘%s’ before continuing. See the documentation for ‘%s’.
2179916The %s agent for Publisher (%s), database (%s), publication (%s) cannnot be found. Create the agent with the appropriate procedure: sp_addpublication_snapshot, sp_addlogreader_agent, or sp_addqreader_agent.
2180016The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up.
2180116The stored procedure sp_createagentparameter failed to add one or more parameters to the system table msdb.dbo.MSagentparameterlist. Check for any errors returned by sp_createagentparameter and errors returned by SQL Server during execution of sp_createagentparameter.
2180216The agent profile creation process cannot validate the specified agent parameter value. ‘%s’ is not a valid value for the ‘%s’ parameter. The value must be an integer less than or equal to ‘%d’. Verify that replication is installed properly.
2180316Cannot update agent parameter metadata. Replication could not insert parameter ‘%s’ into table ‘%s’. Verify that replication is properly installed. Check errors returned by SQL Server during execution of sp_createagentparameter.
2180416The value ‘%d’ specified for the @agent_type parameter of sp_getagentparameterlist is not valid. Specify a valid value of 1, 2, 3, 4, or 9.
2180516The agent profile creation process cannot validate the specified agent parameter value. ‘%s’ is not a valid value for the ‘%s’ parameter. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value.
2180616The agent profile creation process cannot validate the specified agent parameter value: the profile_id %d does not exist or it does not support the parameter %s. The value must be an integer. Verify that replication is installed properly and that sp_add_agent_parameter is invoked with a valid value.
2180716For a .NET Assembly Business Logic Handler, the @resolver_clsid must be specified as NULL.
2180816For a .NET Assembly Business Logic Handler, the @resolver_info must contain the class name in ‘%s’ that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface.
2180910DDL replication is not enabled for database ‘%ls’ because its compatibility level is less than 80.
2181016Identity column can only be added to a published table with ‘Not For Replication’ clause
2181116Cannot drop the column ‘%s’ because it is used by replication: it is referenced in a filter or view by article ‘%s’. To drop the column, you must first remove the filter from the article.
2181216Cannot perform “Disable Trigger All” on table %s because it belongs to a publication that supports updatable subscriptions (replication adds triggers to tables for these types of publications). You may, however, disable user triggers individually. Specify an individual user trigger name to disable.
2181316Can not disable trigger %s on table %s because it is required by updatable publication.
2181416DDL replication failed to refresh custom procedures, please run “exec sp_register_custom_scripting ‘CUSTOM_SCRIPT’, your_script, ‘%s’, ‘%s’ “and try again
2181516Can not alter replicated object ‘%s’ to ‘with encrypted’.
2181616An invalid value was specified for parameter ‘%s’. The value must be ‘%s’ when changing this property.
2181716The property ‘%s’ is only valid for push subscriptions.
2181810The parameters for security, batch size, and scheduling have been deprecated and should no longer be used. For more information, see the “sp_addsubscriber” documentation.
2181916Cannot change the property ‘%s’ . This property is only valid for subscriptions that allow updating at the Subscriber. The subscription against which the procedure was called does not allow updates at the Subscriber.
2182016Cannot write to the script file in the snapshot folder at the Distributor (%ls). Ensure that there is enough disk space available. Also ensure that the account under which the Snapshot Agent runs has permissions to write to the snapshot folder and its subdirectories.
2182116Specify one and only one of the parameters – %s or %s.
2182216Cannot perform %s on %s as entry already exists.
2182316Cannot perform %s on %s as entry does not exist.
2182416Can not add constraints to multiple columns because table %s is published but column %s is not in all active partitions, please use separate DDL statement.
2182516Can not drop constraints in the same DDL statement which drops columns from table %s because the table is published, please use separate DDL statement.
2182616The property ‘%s’ is valid only for %s subscriptions. Use ‘%s’ for %s subscriptions.
2182716The %s parameters have been deprecated and should no longer be used. For more information, see the ‘%s’ documentation.
2182816The proxy account for jobstep_uid (%s) could not be found.
2183016You cannot specify schema_option 0x4 (script identity as identity rather than the base data type) for article ‘%s’. The value specified for the parameter @identityrangemanagementoption is NONE. To replicate identity as identity, the value must be MANUAL or AUTO for publications that do not support queued updating subscriptions.
2183116The %s already exists. Use ‘%s’ to change any settings/properties.
2183216Only members of the sysadmin fixed server role can perform this operation without specifying %s.
2183316An error occurred when creating a trace event at Oracle publisher ‘%s’. The trace event could not be posted.
2183416The primary key for ‘%s.%s’ has %d columns. SQL Server supports a maximum of %d columns. Redefine the primary key so that it has no more than the maximum number of columns.
2183516The index for the primary key ‘%s.%s’ is at least %d bytes. SQL Server supports a maximum key length of %d bytes. Reduce the number of columns in the primary key or redefine the columns to use smaller data types.
2183616The distribution agent must be run in single subscription stream mode prior to resetting the subscription xact_seqno.
2183716A replication agent job (%s) for this subscription already exists.
2183816The %s parameter(s) have been deprecated from this procedure. The value(s) should now be specified when calling ‘%s’.
2183916Article ‘%s’ can not support schema_option 0x20 or 0x2000000000 because it contains computed column, check/default constraint or primary key which is based on CLR type column, change @schema_option setting and try again.
2184016Can not add CLR type based computed column or check constraint to table ‘%s’ because article ‘%s’ supports schema_option 0x20.
2184110DDL replication is forcing reinitialization because either publication’%s’ uses character mode bcp, or timestamp/identity column is being replicated as base type only for article ‘%s’.
2184216%s can only be specified/changed for heterogeneous publications when %s is set to %s.
2184316Article ‘%s’ can not be added, an indexed view published as ‘indexed view logbased’ and a stored procedure in either form of ‘proc exec’ can not be published if their common base table is also published.
2184416Can not alter XML, CLR type or MAX type column because table is published and article ‘%s’ supports the schema option to map this to a base column type.
2184516Can not alter procedure ‘%s’ to depend on an indexed view published as ‘indexed view logbased’ or a base table because the indexed view depends on this table as well.
2184616Cannot find a distribution agent job for the specified transactional or snapshot push subscription.
2184716Cannot find a merge agent job for the specified merge push subscription.
2184816The specified pull subscription is not configured with a synchronization agent job.
2185016The property “%s” cannot be changed to “%s” after the value has already been set to “%s”.
2185116Peer-to-peer publications only support a “%s” value of %s. Article “%s” currently has a “%s” value of %s. This value must be changed to continue.
2185216Peer-to-peer publications do not support %s. Article “%s” currently has %s. This must be changed to continue.
2185310Warning: The “%s” property for %s “%s” has been changed to “%s” because it is required by %s.
2185410Could not add new article to publication ‘%s’ because of active schema change activities or a snapshot is being generated.
2185516The login %s provided in sp_link_publication is not mapped to any user in publishing database %s.
2185616For a .NET Assembly Business Logic Handler, the .NET Assembly name should be the name of a valid assembly in ‘%s’ that contains the class that implements the Microsoft.SqlServer.Replication.BusinessLogicSupport.BusinessLogicModule interface. Check the registration of the business logic handler to make sure the .NET Assembly name was specified correctly.
2185710Forcing re-initialization for article ‘%s’ in publication ‘%s’, the clustered index on indexed view ‘%s’ may have been dropped by upgrade or restore process, please re-create the index and re-sync your data.
2185816Snapshot can not process article ‘%s’ in publication ‘%s’, the clustered index on indexed view ‘%s’ may have been dropped by upgrade or restore process, please re-create the index and re-run snapshot.
2185916Cannot change subscription property ‘%s’ because there is no entry for this subscription in the MSsubscription_properties table. Call sp_addmergepullsubscription_agent before changing this property.
2186010Table ‘%s’ in database ‘%s’ is subscribing to transactional queued publication and published for merge for uploading changes, this may cause non-convergence between transactional publisher and subscriber.
2186116The current operation was aborted because it would deactivate an article in a publication for which a snapshot was being generated.
2186216FILESTREAM columns cannot be published in a publication by using a synchronization method of either ‘database snapshot’ or ‘database snapshot character’.
2186316Cannot add the SPARSE property to a column for the article ‘%s’ because merge replication does not support sparse columns.
2186416Cannot publish the article ‘%s’ or add the COLUMN_SET attribute set to its base table ‘%s’ because replication does not support column sets.
2186516The ‘%s’ publication property must be either ‘true’ or ‘false’.
2186616The publication property ‘%s’ can only be set to ‘%s’ when the publication property ‘%s’ is set to ‘%s’.
2186716ALTER TABLE SWITCH statement failed. The table ‘%s’ belongs to a publication which does not allow switching of partitions
2186816ALTER TABLE SWITCH statement failed. The statement is not allowed because one or more of the tables in this statement is an article with a different destination table or owner.
2186916Cannot add filter between proposed parent article ‘%s’ and proposed child article ‘%s’ since this would introduce a cycle in the filter relationships.  The proposed parent is already being filtered by the child.
2187016Distribution agent encountered a deadlock while applying commands in SubscriptionStreams mode.  Spid %u waiting on lock (type ‘%s’, mode ‘%s’) for index ‘%s’ of table ‘%s’.
2187116Publisher %s of database %s has not been redirected.
2187216The availability group associated with Virtual Network Name ‘%s’ has no replicas.
2187316You are not authorized to run the stored procedure %s.
2187416The stored procedure %s must be run from a distirbution database. The current database %s is not a distribution database.
2187516The parameters @original_publisher and @publisher_db to stored procedure ‘%s’ may not be NULL.
2187616The distributor ‘%s’ is not the distributor for original publisher ‘%s’ and publisher database ‘%s’.
2187716The original publisher ‘%s’ for database ‘%s’ is not a remote server for the distributor.
2187816Unable to create a linked server to use in contacting the remote publisher for original publisher ‘%s’, publisher database ‘%s’, and redirected publisher ‘%s’. The command ‘%s’ failed with Error ‘%d’, Error Message ‘%s’.
2187916Unable to query the redirected server ‘%s’ for original publisher ‘%s’ and publisher database ‘%s’ to determine the name of the remote server; Error %d, Error message ‘%s’.
2188016The virtual network name ‘%s’ has been used to identify the redirected publisher for original publisher ‘%s’ and database ‘%s’. The availability group associated with this virtual network name, however, does not include the publisher database.
2188116The database ‘%s’ at the redirected publisher ‘%s’ for original publisher ‘%s’ and database ‘%s’ is either not synchronized or is not active.
2188216The database ‘%s’ at the redirected publisher ‘%s’ for original publisher ‘%s’ and database ‘%s’ belongs to a HADRon availability group and must be redirected to its associated HADRon Virtual Network Name.
2188316The query at the redirected publisher ‘%s’ to determine whether the publisher database ‘%s’ belonged to an availability group failed with error ‘%d’, error message ‘%s’.
2188416The query at the redirected publisher ‘%s’ to determine the health of the availability group associated with publisher database ‘%s’ failed with error ‘%d’, error message ‘%s’.
2188516The return code of the failed call was ‘%d’.
2188616The remote server name returned was null.
2188716The query at the redirected publisher ‘%s’ to determine whether the publisher database ‘%s’ belonged to an availability group failed with error ‘%d’, error message ‘%s’.
2188816The SQL Server instance ‘%s’ is not configured to support replication. To enable the SQL Server instance to serve as a replication publisher, configure the instance for replication.
2188916The SQL Server instance ‘%s’ is not a replication publisher. Run sp_adddistributor on SQL Server instance ‘%s’ with distributor ‘%s’ in order to enable the instance to host the publishing database ‘%s’. Make certain to specify the same login and password as that used for the original publisher.
2189016The SQL Server instance ‘%s’ with distributor ‘%s’ and distribution database ‘%s’ cannot be used with publisher database ‘%s’. Reconfigure the publisher to make use of distributor ‘%s’ and distribution database ‘%s.
2189116The publisher ‘%s’ with distributor ‘%s’ is not known as a publisher at distributor ‘%s’. Run sp_adddistpublisher at distributor ‘%s’ to enable the remote server to host the publishing database ‘%s’.
2189216Unable to query sys.availability_replicas at the availability group primary associated with virtual network name ‘%s’ for the server names of the member replicas: error = %d, error message = %s.’,
2189316The subscribers ( %s ) of original publisher ‘%s’ do not appear as remote servers at redirected publisher ‘%s’. Run sp_addlinkedserver at the redirected publisher to add these subscribers as remote servers.
2189416Unable to configure a linked server to query replica host server ‘%s’: return code = %d.
2189516One or more publisher validation errors were encountered for replica host ‘%s’.
2189616The query at the redirected publisher ‘%s’ to determine whether the SQL Server instance is a replication publisher failed with error ‘%d’, error message ‘%s’.
2189716The query to determine whether the local distributor ‘%s’ is the distributor for remote publisher ‘%s’ failed with error ‘%d’, error message ‘%s’.
2189816The publisher ‘%s’ uses distribution database ‘%s’ and not ‘%s’ which is required in order to host the publishing database ‘%s’. Run sp_changedistpublisher at distributor ‘%s’ to change the distribution database used by the publisher to ‘%s’.
2189916The query at the redirected publisher ‘%s’ to determine whether there were sysserver entries for the subscribers of the original publisher ‘%s’ failed with error ‘%d’, error message ‘%s’.
2200116FreeStaleVersionSpace failed for page %S_PGID for database id ‘%d’. It will be retired in the next iteration of the version cleaner.
2200316Stale/aborted version cleanup was aborted for database id ‘%d’ due to database shutdown.
2200410[%d]. System transaction with xdes id %S_XID was aborted due to failure injection while moving rows from one page to another.
2200510ADR cleanup failed for database id ‘%d’.
2200616Version cleanup was aborted for database id ‘%d’ due to database exclusive waiter.
2200716Version cleanup was aborted for database id ‘%d’ due to planned failover.
2200816Aborted versions belonging to this filegroup could not be cleaned up.
2201016Cannot change the READONLY property of the filegroup containing Persistent Version Store which is required for Accelerated Database Recovery.
2210116The value supplied for the change_columns argument of CHANGE_TRACKING_IS_COLUMN_IN_MASK function is not valid. The value must be a bitmask returned by the CHANGETABLE(CHANGES …) function.
2210216The arguments supplied are not valid for the CHANGES option of the CHANGETABLE function.
2210316The arguments supplied are not valid for the VERSION option of the CHANGETABLE function.
2210416A table returned by the CHANGETABLE function must be aliased.
2210516Change tracking is not enabled on table ‘%.*ls’.
2210616The CHANGETABLE function does not support remote data sources.
2210716Object ‘%.*ls’ is of a data type that is not supported by the CHANGETABLE function. The object must be a user-defined table.
2210816The CHANGE_TRACKING_CONTEXT WITH clause cannot be used with a SELECT statement.
2210916The “context” argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128.
2211016The number of columns specified in the CHANGETABLE(VERSION …) function does not match the number of primary key columns for table ‘%.*ls’.
2211116The column ‘%.*ls’ specified in the CHANGETABLE(VERSION …) function is not part of the primary key for table ‘%.*ls’.
2211216Each primary key column must be specified once in the CHANGETABLE(VERSION …) function. The column ‘%.*ls’ is specified more than once.
2211316%S_MSG is not allowed because the table is being tracked for change tracking.
2211416Change tracking options for ALTER DATABASE cannot be combined with other ALTER DATABASE options.
2211516Change tracking is enabled for one or more tables in database ‘%.*ls’. Disable change tracking on each table before disabling it for the database. Use the sys.change_tracking_tables catalog view to obtain a list of tables for which change tracking is enabled.
2211616Change tracking is not supported by this edition of SQL Server.
2211716For databases that are members of a secondary availability replica, change tracking is not supported. Run change tracking queries on the databases in the primary availability replica.
2211816Cannot enable change tracking on table ‘%.*ls’. Change tracking is not supported when the primary key contains encrypted columns.
2211916Cannot enable change tracking on table ‘%.*ls’. Change tracking requires a primary key constraint on the table to be enabled. Enable the primary key constraint on the table before enabling change tracking.
2212016Invalid value for cleanup batch size.
2212116Deleted %ld row(s) per millisecond from %s
2212216Change Tracking autocleanup failed on side table of “%s”.  If the failure persists, use sp_flush_CT_internal_table_on_demand to clean up expired records from its side table.
2212316Change Tracking autocleanup is blocked on side table of “%s”. If the failure persists, check if the table “%s” is blocked by any process .
2212416Change Tracking manual cleanup is blocked on side table of “%s”. If the failure persists, check if the table “%s” is blocked by any process .
2220116Internal error. Unable to acquire the latch holding buffers for DW Tiered Storage ColumnStore Scan.
2220216Internal error. Unable to run the remote cs garbage collector. Error Code 22202.
2220316Internal error. Unable to update the blobs table in the catalogDB. Error Code 22203.
2220416Internal error. Unable to refresh catalog db information for service uri [%ls].
2220516Internal error. Unable to get catalog information via the catalog helper.
2220616Internal error. Unable to get lock for protected shared buffer
2220716Internal error. Unable to get a valid dbtable. Error Code 22207.
2220816Access to  DW Tiered Storage ColumnStore blob failed. See earlier errors for cause.
2220916Internal error. Unable to populate instance member list.
2221016Internal error. Unable to get instance member.
2221116Internal error. Invalid instance member state.
2221221An error occurred while reading remote column store segment HoBt 0x%I64X, Object %d, Column %d, Type %d in database %d. The segement could not be decrypted.
2221316Internal error. Unable to get catalog information via the sp.
2221416Internal error. Unable to initialise XODBC Connection Manager.
2221516Internal error. Unable to get catalog information.
2221616Internal error. Protected buffer failure.
2221716Internal error. Persist lru cost info failure.
2221816Internal error. Catalog Communication Failure.
2221916Internal error. Internal table base failure.
2222010Beginning database migration scan for database “%s”.
2222110Database migration scan for database “%s” is complete.
2222210Database migration scan for database ‘%.*ls’ was aborted. Internal error. Migration scan was aborted.
2222316Internal error. Unable to refresh migration type from fabric property.
2222416Internal error. ADW Optimized for Compute storage detected. Unable to retrieve blob.
2222516An internal error (%d, %d) occured. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Support.
2222616An internal error (%d, %d) occured. Please retry the operation again. If the problem persists contact Microsoft Azure Customer Support.
2222710TIERED Storage Scanner encountered an error message “%ls” in “%ls”.
2222822The columnstore remote lob header is invalid.
2222922Remote storage columnstore data checksum mismatch. Expected checksum from blob is %lu, actual check sum from read buffers is %lu.
2230116DW FIDO mode is not enabled.
2230216DW FIDO transaction context not found.
2230316Updates are not allowed from a FIDO Scan transaction.
2230416Reading or Writing to database files is not supported in FIDO DBs.
2230516A NULL or unexpected value was retured by a FIDO ODBC call.
2230616Only CCI tables are allowed in Fido mode.
2230716Alter statements are only allowed from a FIDO Alter transaction.
2230816Fido thread failed to acquire a lock.
2230916Fido Cache DB not found.
2231016Failed to create Fido DB with key: [%.*ls].
2231116Generic Fido out of bounds error.
2231216Failed to remap rowset with Id ‘%I64d’ on a Fido DB.
2231316Failed to find Fido columns in rowset with Id ‘%I64d’.
2231416Fido invalid ODBC connection.
2231516Invalid Fido Transaction type %d.
2231616Failed to acquire CSI Cache lock.
2231716Fido invalid ODBC column.
2231816Fido ODBC transaction failed a commit.
2231916An invalid access to a Fido DB Rowset (DbId ‘%lu’, RowsetId ‘%I64d’) was performed.
2232016Fido DB (DbId:’%lu’, Name: ‘%.*ls’) can only be used under a Fido session context.
2232116Fido DB (DbId:’%lu’, Name: ‘%.*ls’) cannot be used in current session. Only DbId: ‘%lu’ is allowed.
2232216Fido session context invalid. Min cell Id cannot greater than Max cell Id
2232316DW FIDO GLM server is not initialized.
2232416DW FIDO GLM Client is not initialized.
2232516The Key column Id (%d) for Rowset (%I64d) is out of range.
2232616Updates are not allowed from a Scan only FIDO Rowset.
2232716Invalid Rowset Id (%I64d) was provided to a Fido Rowset remapping sys RowsetId (%I64d).
2232816Alters are only allowed on the GLMServer instance.
2232916Open of Rowset (%I64d) in DB (%d) failed.
2233016RowsetColumn Id (%d) missing in Rowset (%I64d).
2233116Provided Accessor Mode is not supported in Fido GLM Rowset.
2233216Data unsupported by Fido GLM Rowset.
2250016Unexpected
2250116All articles in the publication passed data validation (rowcount and checksum).
2250216Not All articles in the publication passed data validation (rowcount only)
2250316Initializing.
2250416Applying the snapshot to the Subscriber.
2250516The merge completed with no data changes processed.
2250616No data needed to be merged.
2250716Uploading data changes to the Publisher.
2250816Downloading data changes to the Subscriber.
2250916Retrieving subscription information.
2251016Retrieving publication information.
2251116The merge completed successfully.
2251216Cannot use partition groups with unfiltered publications. Set “use_partition_groups” to “false” using sp_changemergepublication.
2251316Cannot use partition groups because the join filter between the following articles contains one or more functions: “%s” and “%s”.
2251416Cannot use partition groups because one or more filters reference the following view, which contains functions: “%s”.
2251516The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
2251616The publication “%s” was defined as having dynamic filters, but it does not contain any dynamic filters.
2251716The publication was defined as having no dynamic filters, but contains one or more dynamic filters.
2251816Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: ‘%s’.
2251916Cannot add a logical record relationship between tables “%s” and “%s” because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
2252010A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
2252110Unable to synchronize the row because the row was updated by a different process outside of replication.
2252216Article ‘%s’ cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot be included in multiple publications or subscriptions, and cannot be republished. To include the article in multiple publications, use sp_changemergearticle to specify a different value for the partition_options property of the existing article.
2252316An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article “%s”.
2252416Article ‘%s’ is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the existing article or change the existing article using sp_changemergearticle.
2252516The publication “%s” cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
2252616An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
2252716Invalid value specified for %s. Valid values are ‘day’, ‘days’, ‘dd’, ‘year’, ‘years’, ‘yy’, ‘yyyy’, ‘month’, ‘months’, ‘mm’, ‘week’, ‘weeks’, ‘wk’, ‘hour’, ‘hours’, ‘hh’, ‘minute’, ‘minutes’, ‘mi’.
2252816Cannot use a retention period unit other than “days” for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
2252916Cannot change the retention period unit for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
2253016Cannot update any column in article “%s” that is used in a logical record relationship clause.
2253110Initialization.
2253210Upload of Subscriber changes to the Publisher.
2253310Download of Publisher changes to the Subscriber.
2253416Character mode publication does not support partitioned tables.
2253516For heterogeneous publications, the %s parameters should be specified when calling “%s”.
2253616The %s parameter value cannot be updated or changed for heterogeneous publications.
2253716The job_login provided must match the Publisher login specified when adding the distribution Publisher (sp_adddistpublisher).
2253816Only replication jobs or job schedules can be added, modified, dropped or viewed through replication stored procedures.
2253916Use of parameters %s is invalid when parameter %s is set to %s.
2254016Cannot change publication “%s” to use sync_mode of “character”, because it contains one or more logical record relationships.
2254116Cannot add a logical record relationship in publication “%s” because it uses sync_mode of “character” and could have SQL Server Compact Edition subscribers.
2254216Invalid value for property @subscriber_upload_options. Valid values are 0 (allow uploads), 1 (disable uploads), 2 (disable uploads prohibit subscriber changes), and 3 (disable_outofpartition_subscriber_changes).
2254316When the publication property @allow_partition_realignment is set to “false”, the article property @subscriber_upload_options for all articles in the publication must be set to disable uploads.
2254410Warning: The procedure sp_mergecleanupmetadata has been deprecated. In SQL Server 2000 SP1 and later, the merge agent calls sp_mergemetadataretentioncleanup every time it runs, so manual cleanup of metadata is not needed. Ignoring passed-in parameters and calling sp_mergemetadataretentioncleanup.
2254516Cannot add a logical record relationship in publication “%s” because it allows Web synchronization.
2254616Cannot change publication “%s” to allow Web synchronization because it contains one or more logical record relationships.
2254716A concurrent snapshot is not allowed for snapshot publications.
2254816Vertical partitioning is only allowed for log-based articles.
2254916A shared distribution agent (%s) already exists for this subscription.
2255016Cannot drop identity column “%s” from the vertical partition when identityrangemanagementoption is set to auto.
2255116The type “%s” is invalid. Valid types are “merge”, “tran”, and “both”.
2255216A valid value for parameter “@resync_date_str” needs to be provided when “@resync_type” is set to 2.
2255316The parameter “@resync_type” is set to “%d” but this subscription has never been successfully validated.
2255416Cannot change publication “%s” to use the sync_mode of “character” because it uses a retention period unit other than “day”. Use sp_changemergepublication to set the retention period unit to “day”.
2255516Cannot set the retention period unit to a value other than “day” for publication “%s” because it uses the sync_mode of “character” and may have SQL Server Compact Edition subscribers.
2255616Invalid value for the property “%s”. Valid values are 1 and 0.
2255716The status of the schema change could not be updated because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication “%s” to 90RTM.
2255816The status of the schema change could not be updated.
2255916The status of the schema change must be “active” or “skipped”.
2256016Merge replication does not allow filters that reference dynamic functions that take one or more parameters. Check the function “%s”.
2256116The requested operation failed because the publication compatibility level is less than 90. Use sp_changemergepublication to set the publication_compatibility_level of publication “%s” to 90RTM.
2256216Cannot change the compatibility level of a publication to a value lower than the existing value.
2256316contains one or more articles that do not upload changes
2256416uses ddl replication
2256516uses other than day as unit of retention period
2256616uses logical records
2256716contains one or more articles that use subscription-based or partition-based filtering
2256816contains one or more articles which will not compensate for errors
2256916contains one or more schema only articles
2257016contains one or more articles that use automatic identity range management
2257116contains one or more articles that use datatypes new in SQL Server 2000
2257216contains one or more articles with a timestamp column
2257316uses snapshot compression with snapshot_in_defaultfolder set to false
2257416contains one or more articles that use vertical partitioning
2257516When article property ‘published_in_tran_pub’ is set to ‘true’ then article property ‘upload_options’ has to be set to disable uploads.
2257610Invalid failover_mode value of %d was specified for [%s].[%s].[%s], setting to 0 [immediate].
2257816Cannot change publication “%s” to disallow use_partition_groups because it contains one or more logical record relationships. When using logical record relationships the publication must set the @use_partition_groups property to ‘true’.
2257916The subscription to publication ‘%s’ was not found but a shared agent does exist. To specify a subscription to a publication that is replicated via a shared agent specify ‘%s’ for the publication name.
2258016Cannot publish database ‘%s’ because it is marked as published on a different server. Before attempting to publish this database, execute sp_replicationdboption, specifying a value of FALSE for ‘publish’ and ‘merge publish’.
2258116Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for publications that have a ‘sync_mode’ of 1 (character mode). Specify a ‘sync_mode’ of 0 (native mode) for the publication by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
2258216Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for publications that have a ‘publication_compatibility_level’ of less than “90RTM” (SQL Server 2005). Specify a ‘publication_compatibility_level’ greater than or equal to “90RTM” by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
2258316Article ‘%s’ cannot be added or modified in publication ‘%s’. The replication of FILESTREAM columns is not supported for articles that have a ‘schema_option’ set to 0x20000000. This converts large object data types to data types that are supported on earlier versions of Microsoft SQL Server. Remove this ‘schema_option’ setting by using sp_addmergepublication or sp_changemergepublication, or partition the article vertically so that the FILESTREAM column is not replicated.
2258410Warning: Values of some of the flags specified in the ‘schema_option’ property are not compatible with the publication’s compatibility level. The modified schema_option value of ‘%s’ will be used instead.
2258510The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article ‘%s’. Enabling this option after the article is created can cause replication to fail when the data in a FILESTREAM column exceeds 2GB and there is a conflict during replication. If you want FILESTREAM data to be replicated, drop and re-create the article, and specify the appropriate schema option when you re-create the article.
2258616Column ‘%s’ cannot be added or modified in article ‘%s’ of publication ‘%s’. The DDL operatoin on hierarchyid and FILESTREAM columns is not supported for publications that have a ‘sync_mode’ of 1 (character mode) or with a lower than 90RTM backward compatibility level.
2258716Non-SQL Server Publishers and Subscribers are supported only on Windows. The platform detected is %s.
2280116Starting the Change Data Capture Collection Agent job. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
2280216Starting the Change Data Capture Cleanup Agent job using low watermark %s.
2280316Change Data Capture has scanned the log from LSN{%s} to LSN{%s}, %d transactions with %d commands have been extracted. To report on the progress of the operation, query the sys.dm_cdc_log_scan_sessions dynamic management view.
2280416Change Data Capture cannot proceed with the job-related action because transactional replication is enabled on database %s but Distributor information cannot be retrieved to determine the state of the logreader agent. Make the Distributor database available, or disable distribution.
2280510For more information, query the sys.dm_cdc_errors dynamic management view.
2280616The originator ID ‘%s’ is not valid. You must specify a non-zero ID that has never been used in the topology.
2280716The publication property ‘%s’ cannot be modified because the peer-to-peer publication ‘%s’ is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection.
2280816Cannot execute procedure ‘%s’. Publication ‘%s’ must be enabled for peer-to-peer replication before you execute this procedure. To enable the publication for peer-to-peer replication, use sp_changepublication.
2280910The existing conflict table ‘%s’ was dropped.
2281016The @action parameter value is not valid. Valid values are ‘enable’ and ‘disable’.
2281116The roundtrip time-out must be greater than 0.
2281210The roundtrip ‘%s’ finished with timeout:  %d seconds.
2281310The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are SQL Server 2008 or later versions.
2281410The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology.
2281510A conflict of type ‘%s’ was detected at peer %d between peer %d (incoming), transaction id %s  and peer %d (on disk), transaction id %s for Table ‘%s’ with Primary Key(s): %s Current Version ‘%s’, Pre-Version ‘%s’ and Post-Version ‘%s’
2281616The qualified table name ‘%s’ is too long to be enabled for peer-to-peer conflict detection.
2281710%s has %s.
2281810A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was skipped.
2281910A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically.  The incoming delete was skipped by peer %d. The conflict has to be resolved manually to guarantee data convergence between the peers. For steps on how to resolve the conflict refer to BOL.
2282010A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d.
2282110An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d.
2282210An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d.
2282310 An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Check the priority of the destination peer and run data validation to ensure the delete conflict did not result in data non-convergence.
2282410An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d.
2282510An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d.
2282716Peer-to-peer conflict detection alert
2282816The publication ‘%s’ was already %s for peer-to-peer conflict detection.
2282916The command %s failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name %s within the size limit %d.
2283016Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283116Could not update the metadata that indicates database %s is not enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283216Could not update the metadata that indicates table %s is enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283316Could not update the metadata that indicates table %s is not enabled for Change Data Capture. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283416Could not modify the the verbose logging status for table %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283516Could not update the metadata for database %s to indicate that a Change Data Capture job has been dropped. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283616Could not update the metadata for database %s to indicate that a Change Data Capture job has been added. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283716Could not delete table entries or drop objects associated with capture instance ‘%s’. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2283816All columns of a CDC unique index must be defined as NOT NULL. Index ‘%s’ selected as the CDC unique index for source table ‘%s.%s’ does not meet this requirement. Define all columns of the selected index as NOT NULL or select another unique index as the CDC index and resubmit the request.
2284016The application lock request ‘%s’ needed to modify Change Data Capture metadata was not granted. The value returned from the request was %d: -1 = timeout; -2 = canceled; -3 = deadlock victim; -999 validation or other call error. Examine the error cause and resbmit the request.
2284116Could not upgrade the metadata for database ‘%s’ that is enabled for Change Data Capture. The failure occurred when executing the action ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2284216ALTER TABLE SWITCH statement failed because the partitioned destination table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
2284316ALTER TABLE SWITCH statement failed because the partitioned source table is enabled for Change Data Capture and does not have @allow_partition_switch set to 1.
2284416The ‘%s’ option must be either 1 or 0.
2284516Cannot enable change data capture in this edition of SQL Server.
2285016The threshold value specified for the Change Data Capture cleanup process must be greater than 0. When creating or modifying the cleanup job, specify a positive threshold value. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the threshold value associated with the job to a non-negative value by using the sp_cdc_change_job stored procedure.
2285116Could not update cdc.change_tables to indicate a change in the low water mark for database %s.
2285210Could not delete change table entries made obsolete by a change in one or more low water marks for capture instances of database %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2285310Could not delete obsolete entries in the cdc.lsn_time_mapping table for database %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.
2285416Can not enable Change Data Capture on table ‘%s’ or add ColumnSet column to it because CDC does not support ColumnSet.
2285510Warning: The @allow_partition_switch parameter is set to 1. Change data capture will not track changes introduced in the table resulting from a partition switch which will cause data inconsistency when changes are consumed. Refer to books online for more information about partition switching behavior when using Change Data Capture.
2285610Warning: The @allow_partition_switch parameter is set to 0. ALTER TABLE … SWITCH PARTITION statement will be disallowed on this partitioned table. Refer to books online for more information about partition switching behavior when using Change Data Capture.
2285710Warning: The @allow_partition_switch parameter must be 1 for tables that are not partitioned. The explicit setting of the parameter to 0 was ignored. Refer to books online for more information about partition switching behavior when using Change Data Capture.
2285816Unable to add entries to the Change Data Capture LSN time mapping table to reflect dml changes applied to the tracked tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2285916Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2286016Log scan process failed in processing a ddl log record. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2286110Unable to upgrade database ‘%s’. Error ‘%d’ was raised: ‘%s’. Use the reported error to determine the cause of the failure and then execute sys.sp_cdc_vupgrade in the database context to rerun upgrade.
2286216The database snapshot ‘%s’ does not exist. Correct the parameter value and resubmit the request.
2286316Failed to insert rows into Change Data Capture change tables. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2286416The call to sp_MScdc_capture_job by the Capture Job for database ‘%s’ failed. Look at previous errors for the cause of the failure.
2286516The number of columns in the index ‘%s’, used as the unique row identifier to support net changes for table ‘%s’.’%s’, exceeds the limit of 14 columns. Set the parameter @supports_net_changes to 0 or use the @index_name parameter to identify a unique index with fewer than 15 columns as the unique row identifier and resubmit the request.
2286610The value returned by %S_MSG is %I64d.
2286710Total rows deleted: %I64u.
2286810Cleanup Watermark = %I64u
2286910Internal Change Tracking table name : %s
2287010Deleted %I64u rows from %s
2290116The database ‘%s’ is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.
2290216Caller is not authorized to initiate the requested action. Sysadmin privileges are required.
2290316Another connection is already running ‘sp_replcmds’ for Change Data Capture in the current database.
2290416Caller is not authorized to initiate the requested action. DBO privileges are required.
2290510Database ‘%s’ is already enabled for Change Data Capture. Ensure that the correct database context is set, and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.
2290616The database ‘%s’ cannot be enabled for Change Data Capture because a database user named ‘cdc’ or a schema named ‘cdc’ already exists in the current database. These objects are required exclusively by Change Data Capture. Drop or rename the user or schema and retry the operation.
2290716Parameter @role_name cannot be empty. Specify a value for @role_name and retry the operation. Supply null as the value if no role is to be used to gate access to captured change data.
2290816Could not create the Change Data Capture objects in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2290916Failed to cleanup the cdc.lsn_time_mapping table in database ‘%s’ when the last database table enabled for Change Data Capture was disabled. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2291016The cleanup request for database ‘%s’ failed.  The database is not enabled for Change Data Capture.
2291116The capture job cannot be used by Change Data Capture to extract changes from the log when transactional replication is also enabled on the same database. When Change Data Capture and transactional replication are both enabled on a database, use the logreader agent to extract the log changes.
2291316Could not drop the Change Data Capture objects in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2291416Only members of the sysadmin or db_owner or db_ddladmin roles can perform this operation when Change Data Capture is enabled for a database.
2291616Could not grant SELECT permission for the change enumeration functions for capture instance ‘%s’ and source table ‘%s.%s’ for the specified role. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2291816One or more columns in the list of included columns was not a captured column of the change table %s.
2291916One or more columns in the list of columns needing update flags was not a captured column of the change table %s.
2292016The named capture instance %s does not exist for database %s.
2292116Unable to generate scripts for all capture instances that the caller is authorized to access. To generate all such scripts, the parameters @column_list and @update_flag_list must both be null or empty.’
2292316Could not compute the new low endpoint for database ‘%s’ from retention %d. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2292416Could not clean up change tables for database ‘%s’. A failure occurred when attempting to clean up the database change tables based upon the current retention time. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2292516The number of columns captured by capture instance ‘%s’ exceeds the maximum allowed number: %d. Use the @captured_columns_list parameter to specify a subset of the columns less than or equal to the maximum allowed and resubmit the request.
2292616Could not create a capture instance because the capture instance name ‘%s’ already exists in the current database. Specify an explicit unique name for the parameter @capture_instance.
2292716Capture instance name ‘%s’ exceeds the length limit of 100 characters. Specify a name that satisfies the length constraint.
2292816Index name ‘%s’ is not an index for table ‘%s.%s’. Specify a valid index name for the table.
2292916Index ‘%s’ must be either a primary key or a unique index for table ‘%s.%s’. Specify an index that meets at least one of these requirements.
2293016Could not locate ‘%s’ as a column of source table ‘%s.%s’. Specify a valid column name.
2293116Source table ‘%s.%s’ does not exist in the current database. Ensure that the correct database context is set. Specify a valid schema and table name for the database.
2293216Capture instance name ‘%s’ is invalid. Specify a valid name. See the topic ‘Identifiers’ in SQL Server Books Online for object name rules.
2293816Role name ‘%s’ is invalid. Specify a valid name. See the topic ‘Identifiers’ in SQL Server Books Online for object name rules.
2293916The parameter @supports_net_changes is set to 1, but the source table does not have a primary key defined and no alternate unique index has been specified.
2294016Could not remove DDL history entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294116Could not retrieve column information for index ‘%s’ of source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294216Columns specified in the captured column list could not be mapped to columns in source table ‘%s.%s’. Verify that the columns specified in the parameter @captured_column_list are delimited properly and match columns in the source table.
2294316Columns used to uniquely identify a row for net change tracking must be included in the list of captured columns. Add either the primary key columns of the source table, or the columns defined for the index specified in the parameter @index_name to the list of captured columns and retry the operation.
2294416Could not create the specified database role ‘%s’ for gating access to change table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294516Could not add column information to the cdc.index_columns system table for the specified index for source table ‘%s.%s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294616Could not add column information to the cdc.captured_columns system table for source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294716Could not create the change table for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294816Could not create the change enumeration functions for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2294916Could not update the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295016Could not remove index column entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295116Could not remove captured column entries in the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295216Could not drop Change Data Capture objects created for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295316Could not remove Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295416Could not cleanup change tables for capture instance ‘%s’ using low end point %s. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295516Could not obtain the maximum LSN for the database from function ‘sys.fn_cdc_get_max_lsn’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295616Could not obtain the minimum LSN of the change table associated with capture instance ‘%s’ from function ‘sys.fn_cdc_get_min_lsn’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295716LSN %s, specified as the new low end point for the change table associated with capture instance ‘%s’, is not within the Change Data Capture timeline [%s, %s].
2295816Could not create the function to query for all changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2295916Could not create the function to query for net changes for capture instance ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2296016Change data capture instance ‘%s’ has not been enabled for the source table ‘%s.%s’. Use sys.sp_cdc_help_change_data_capture to verify the capture instance name and retry the operation.
2296116Could not create a nonclustered index to support net change tracking for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2296216Two capture instances already exist for source table ‘%s.%s’. A table can have at most two capture instances. If the current tracking options are not appropriate, disable change tracking for the obsolete instance by using sys.sp_cdc_disable_table and retry the operation.
2296316Parameter ‘%s’ cannot be null or empty. Specify a value for the named parameter and retry the operation.
2296416LSN %s, specified as the new low end point for change table cleanup must represent the start_lsn value of a current entry in the cdc.lsn_time_mapping table. Choose an LSN value that satisfies this requirement.
2296516A quoted column in the column list is not properly terminated. Verify that columns are correctly delimited and retry the operation. For more information, see ‘Delimited Identifiers’ in Books Online.
2296616Could not create table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2296716Could not create a clustered index for table dbo.systranschemas in database ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2296816Could not create DDL trigger ‘%s’ when enabling Change Data Capture for database ‘%s’. Additional messages in the SQL Server error log and operating system error log may provide more detail.
2297016The value for parameter @maxscans specified for the Change Data Capture job must be greater than 0.
2297116Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual settings on the server and examine memory usage to see if another application is excessively consuming memory.
2297216When calling stored procedure [sys].sp_cdc_help_change_data capture, if either @source_schema or @source_name is non-null and non-empty, the other parameter must also be non-null and non-empty.
2297316The specified filegroup ‘%s’ is not a valid filegroup for database ‘%s’. Specify a valid existing filegroup or create the named filegroup, and retry the operation.
2297416Tables contained in the cdc schema cannot be enabled for Change Data Capture.
2297516Source table ‘%s’ contains one of the following reserved column names: __$start_lsn, __$end_lsn, __$seqval, __$operation, and __$update_mask. To enable Change Data Capture for this table, specify a captured column list and ensure that these columns are excluded from the list.
2297616Could not alter column ‘%s’ of change table ‘%s’ in response to a data type change in the corresponding column of the source table ‘%s’. The Change Data Capture meta data for source table ‘%s’ no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2297716Unable to update DDL history information to reflect columns changes applied to the tracked table associated with change table ‘%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2297816Could not update the cdc.captured_columns entry for column ‘%s’ of change table ‘%s’ to reflect a data type change in the corresponding column of the source table ‘%s’. Change Data Capture column meta data for table ‘%s’ no longer accurately reflects the source table. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2297916The unique index ‘%s’ on table ‘%s’ is used by Change Data Capture. The constraint using this index cannot be dropped or disabled.
2298016The unique index ‘%s’ on table ‘%s.%s’ is disabled and cannot be used as a unique index by Change Data Capture. Enable the index.
2298116Object does not exist or access is denied.
2298216Could not create internal stored procedures used to populate the change table for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.
2298316The unique index ‘%s’ on source table ‘%s’ is used by Change Data Capture. To alter or drop the index, you must first disable Change Data Capture on the table.
2298416An error occurred while waiting on the log reader history cache event. This error is reported by the internal task scheduling and might be transient. Retry the operation.
2298516Change data capture has not been enabled for source table ‘%s.%s’. Specify the name of a table enabled for Change Data Capture. To report on the tables enabled for Change Data Capture, query the is_tracked_by_cdc column in the sys.tables catalog view.
2298616Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory.
2298716Change Data Capture population failed writing blob data for one or more large object columns. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory.
2298816This instance of SQL Server is the %s. Change data capture is only available in the Enterprise, Developer, Enterprise Evaluation, and Standard editions.
2298916Could not enable Change Data Capture for database ‘%s’. Change data capture is not supported on system databases, or on a distribution database.
2299016The value specified for the parameter @pollinginterval cannot exceed 24 hours or be less than 0. Specify a polling interval (in seconds) that is less than or equal to 24 hours (86,400 seconds).
2299116The value specified for the parameter @maxtrans must be greater than 0.
2299216The specified @job_type, %s, is not supported. The value specified for the parameter @job_type must be N’capture’ to indicate a capture job, or N’cleanup’ to indicate a cleanup job.
2299316The Change Data Capture job table containing job information for database ‘%s’ cannot be found in the msdb system database. Run the stored procedure ‘sys.sp_cdc_add_job’ to create the appropriate CDC capture or cleanup job. The stored procedure will create the required job table.
2299416The retention value specified for the Change Data Capture cleanup process must be greater than 0 and less than or equal to 52594800. When creating or modifying the cleanup job, specify a retention value (in minutes) that is within that range. If this error is encountered when executing the sys.sp_cdc_cleanup_change_table stored procedure, reset the retention value associated with the job to a non-negative value less than 52594800 by using the sp_cdc_change_job stored procedure.
2299516A value for the parameter @retention cannot be specified when the job type is ‘capture’. Specify NULL for the parameter, or omit the parameter from the statement.
2299616When adding or modifying the CDC cleanup job, @pollinginterval, @maxtrans, @maxscans, and @continuous may not be assigned non-null values.
2299716The Change Data Capture ‘%s’ job does not exist in the system table ‘msdb.dbo.cdc_jobs’. Use the stored procedure ‘sys.sp_cdc_add_job’ to add the Change Data Capture job.
2299816The value specified for the parameter @continuous must be 0 or 1.
2299916The value specified for the parameter @pollinginterval must be null or 0 when the stored procedure ‘sys.sp_cdc_scan’ is not being run in continuous mode.
2300317The WinFS share permissions have become corrupted {Error: %ld}. Please try setting the share permissions again.
2310016Invalid input parameter(s).
2310116Access is denied.
2310216Item does not exist {ItemId: %ls}.
2310316Folder already exists {ItemId: %ls}.
2310416Folder does not exist {ItemId: %ls}.
2310516Operation violates hierarchical namespace uniqueness.
2310616Container is not empty {ItemId: %ls}.
2310716Item cannot be copied onto itself.
2310816Scoping path does not exist or is invalid.
2310916Container does not exist.
2311016No more items to enumerate.
2311116Item does not exist in the given scope {ItemId: %ls, Scope: %ls}.
2311216Transaction not in active state.
2311316Item either does not exist or it is not a file-backed one.
2311416Sharing violation.
2311516Transaction bindtoken must be null when called within the context of a transaction.
2311616Inconsistent StreamSize and/or AllocationSize data {ItemId: %ls}.
2311716File-backed item does not exist {ItemId: %ls}.
2320016ItemId of folder ‘%ls’ not found.
2320116Share ‘%ls’ does not exist in Catalog.
2320216Could not delete Share ‘%ls’ in Catalog.
2320316Store item not found in Catalog.
2320416Could not delete Store item in Catalog.
2320516Store database name not found in Catalog.
2320616Could not create share to the ItemPath ‘%ls’.
2320716Could not add Share item for ‘%ls’ in Catalog.
2320816ItemPath ‘%ls’ does not exist in Store.
2320916Could not update Store state in Catalog.
2321016Itempath ‘%ls’ is a file-backed item or within its sub-tree.
2321116Could not start Store Manager. Please look in WinFS UT Log for details.
2321216Itempath ‘%ls’ is a compound item.
2350016Item container does not exist.
2350116Owning Item does not exist.
2350216NamespaceName is empty or exceeds the maximum length.
2350316Invalid Source endpoint type
2350416Invalid Target endpoint type
2350516A File-backed item must be a compound item type.
2350616A File Backed Item may not contain other Items.
2350916Source Item does not exist.
2351016Item with name already exists in container.
2351116New container cannot be a sub-container of item.
2351316Item does not exist.
2351516Item can not be deleted if it has children
2351916Target Item does not exist.
2352516Invalid Namespace Name.
2353016Operation can not be called inside a un-committable transaction
2353616Win32 file handle is open for item
2357316Cannot change ContainerId when replacing item.
2357916This procedure is reserved and cannot be called.
2358716File stream cannot be null.
2358816Container ids must be the same.
2399616The request could not be performed because of an device I/O error.
2399716System error occurred {ErrorCode: %d}.
2399816Not enough memory available in the system to process the request.
2399916Unspecified error(s) occurred.