Database Engine events and errors (19000 to 20999)

This article contains error message numbers (between the range 19000 and 20999) and their description, which is the text of the error message from the sys.messages catalog view. Where applicable, the error number is a link to further information.

For the full range of error numbers, see the list on Database Engine events and errors.

You can query the Database Engine to see a full list of all errors, by running the following query against the sys.messages catalog view:

SELECT message_id AS Error,
    severity AS Severity,
    [Event Logged] = CASE is_event_logged
        WHEN 0 THEN 'No' ELSE 'Yes'
        END,
    [text] AS [Description]
FROM sys.messages
WHERE language_id = 1040 /* replace 1040 with the desired language ID, such as 1033 for US English */
ORDER BY message_id;

SQL Server version

This article shows events and errors (between the range 19000 and 20999) for SQL Server 2022 (16.x). If you want to view events and errors for other versions of SQL Server, see:

• SQL Server 2019
• SQL Server 2017
• SQL Server 2016

Errors and events (19000 to 20999)

Error	Severity	Event logged	Description
19030	10	Yes	SQL Trace ID %d was started by login "%s".
19031	10	Yes	SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'.
19032	10	Yes	SQL Trace was stopped due to server shutdown. Trace ID = '%d'. This is an informational message only; no user action is required.
19033	10	Yes	Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
19034	21	Yes	Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls
19035	16	Yes	OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured.
19036	10	Yes	The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.
19049	16	No	File '%.*ls' either does not exist or there was an error opening the file. Error = '%ls'.
19050	16	No	Trace file name '%.*ls' is invalid.
19051	16	No	Unknown error occurred in the trace.
19052	16	No	The active trace must be stopped before modification.
19053	16	No	The trace event ID is not valid.
19054	16	No	The trace column ID is not valid.
19055	16	No	Filters with the same event column ID must be grouped together.
19056	16	No	The comparison operator in the filter is not valid.
19057	16	No	The boolean operator in the filter is not valid.
19058	16	No	The trace status is not valid.
19059	16	No	Could not find the requested trace.
19060	16	No	The trace option is not valid.
19061	16	No	Cannot remove SPID trace column.
19062	16	No	Could not create a trace file.
19063	16	No	Not enough memory was available for trace.
19064	16	No	The requested trace stop time has been already passed.
19065	16	No	The parameter is not valid.
19066	16	No	Cannot modify a restricted trace.
19067	16	No	Cannot create a new trace because the trace file path is found in the existing traces.
19068	16	No	The trace file path is not valid or not supported.
19069	16	No	The 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.
19070	16	No	The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
19071	16	No	Stopping the trace because the current trace file is full and the rollover option is not specified.
19096	16	No	Fail to delete an old trace file '%ls'. Error = '%ls'.
19097	10	No	Operating system error occurred while running %s. Error = %s.
19098	16	Yes	An 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.
19099	16	Yes	Trace ID '%d' was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.
19100	10	No	Initialization succeeded.
19101	10	No	Initialization failed with an infrastructure error. Check for previous errors.
19102	10	No	Unable to create a node listener object. Check for memory-related errors.
19103	10	No	An error occurred while starting shared memory support.
19104	10	No	All protocols are disabled.
19105	10	No	Unable to create a node listener object for a special instance. Check for memory-related errors.
19106	10	No	Unable to trim spaces in an IP address. Check TCP/IP protocol settings.
19107	10	No	'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings.
19108	10	No	Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings.
19109	10	No	Unable to configure MDAC-compatibility TCP/IP port in registry.
19110	10	No	Unable to initialize the TCP/IP listener.
19111	10	No	Unable to open TCP/IP protocol configuration key in registry.
19112	10	No	Unable to retrieve TCP/IP protocol 'Enabled' registry setting.
19113	10	No	Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting.
19114	10	No	Unable to open TCP/IP protocol's 'IPAll' configuration key in registry.
19115	10	No	Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key.
19116	10	No	Unable to obtain list size for IP addresses configured for listening in registry.
19117	10	No	Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors.
19118	10	No	Unable to obtain list of IP addresses configured for listening in registry.
19119	10	No	Unable to open TCP/IP protocol's registry key for a specific IP address.
19120	10	No	Unable to retrieve 'Enabled' setting for a specific IP address.
19121	10	No	Unable to retrieve 'Active' setting for a specific IP address.
19122	10	No	Unable to retrieve 'IpAddress' value for a specific IP address.
19123	10	No	'IpAddress' registry value is the wrong type.
19124	10	No	Unable to retrieve registry settings for a specific IP address.
19125	10	No	Unable to deallocate structures representing registry key for a specific IP address.
19126	10	No	Unable to retrieve registry settings for cluster environment.
19127	10	No	Server is configured to listen on a specific IP address in a cluster environment.
19128	10	No	The SQL Server Network Interface cannot check for a duplicate IP address in the SQL Server TCP listening settings.
19129	10	No	The 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.
19130	10	No	Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings.
19131	10	No	Unable to open Dedicated Administrator Connection configuration key in registry.
19132	10	No	Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry.
19133	10	No	Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection.
19134	10	No	No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings.
19135	10	No	Error starting Named Pipes support. Check protocol settings.
19136	10	No	An error occurred starting VIA support. Check protocol settings.
19137	10	No	Failed to allocate memory for SSL listening structures. Check for memory-related errors.
19138	10	No	An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager.
19139	10	No	Unable to add listener endpoints. Check for memory-related errors.
19140	10	No	Unable to initialize the communication listeners.
19141	10	No	Unable to retrieve SQL Server Network Interface library settings for a special instance.
19142	10	No	Unable to retrieve SQL Server Network Interface library settings; the instance name is too long.
19143	10	No	Unable to initialize the Shared Memory listener.
19144	10	No	Unable to initialize the Named Pipes listener.
19145	10	No	Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry.
19146	10	No	Unable to initialize the VIA listener.
19147	10	No	Unable to initialize the HTTP listener.
19148	10	No	Unable to initialize SSL support.
19149	10	No	Unable to configure MDAC-compatibility protocol list in registry.
19150	10	No	Unable to open SQL Server Network Interface library configuration key in registry.
19151	10	No	An error occurred while obtaining the Extended Protection setting. Check Network Configuration settings in SQL Server Configuration Manager.
19152	10	No	The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
19153	10	No	An error occurred while obtaining the Accepted SPNs list for Extended Protection. Check Network Configuration settings in SQL Server Configuration Manager.
19154	10	No	The configured value for the Accepted SPNs list is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
19155	10	No	TDSSNIClient failed to allocate memory while loading Extended Protection configuration settings. Check for memory-related errors.
19156	10	No	Failed to allocate memory for SSPI listening structures. Check for memory-related errors.
19157	10	No	Unable to initialize the SSPI listener.
19158	10	No	Unable to create connectivity Ring Buffer. Check for memory-related errors.
19159	10	No	Unable to open 'Named Pipes' configuration key for Dedicated Administrator Connection in registry.
19160	10	No	Unable to retrieve 'Enabled' registry settings for Named-Pipe Dedicated Administrator Connection.
19161	10	No	No protocol is enabled for the Dedicated Administrator Connection.
19162	10	No	Unable to retrieve 'PipeName' registry settings for Named-Pipe Dedicated Administrator Connection.
19163	10	No	Error starting Named Pipes support for Dedicated Administrator Connection.
19164	10	No	Unable to retrieve 'GroupName' registry settings for Named-Pipe Dedicated Administrator Connection.
19165	10	No	Error starting Named Pipes support for Dedicated Administrator Connection.
19200	10	No	Authentication succeeded.
19201	10	No	The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream.
19202	10	No	An error occurred while calling CompleteAuthToken for this security context. The operating system error code indicates the cause of failure.
19203	10	No	The CompleteAuthToken API is not defined for the current Security Support Provider.
19204	10	No	AcceptSecurityContext failed. The operating system error code indicates the cause of failure.
19205	10	No	The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
19206	10	No	The 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.
19207	10	No	The 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.
19208	10	No	The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
19209	10	No	QueryContextAttributes could not retrieve Service Bindings. The operating system error code indicates the cause of failure.
19210	10	No	The 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.
19211	10	No	The 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.
19212	10	No	The Service Class element of the received Service Principal Name (SPN) is not valid.
19213	10	No	The IP Address element of the received Service Principal Name (SPN) is not valid.
19214	10	No	The Host element of the received Service Principal Name (SPN) is not valid.
19215	10	No	A memory allocation failed while validating the received Service Principal Name (SPN).
19216	10	No	QueryContextAttributes succeeded but did not retrieve the received Service Principal Name (SPN).
19217	10	No	WSAStringToAddress 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.
19218	10	No	Could not wait on an event signaling IO completion for a cryptographic handshake.
19219	10	No	A task to process a cryptographic handshake could not be enqueued.
19220	10	No	An attempt to read a buffer from the network failed during a cryptographic handshake.
19221	10	No	The connection was closed while attempting to process a read buffer during a cryptographic handshake.
19222	10	No	The connection was closed while attempting to process a write buffer during a cryptographic handshake.
19223	10	No	An attempt to write a buffer to the network failed during a cryptographic handshake.
19224	10	No	AcquireCredentialsHandle failed. The operating system error code indicates the cause of the failure.
19225	10	No	InitializeSecurityContext failed. The operating system error code indicates the cause of the failure.
19226	10	No	QueryContextAttributes could not retrieve stream sizes. The operating system error code indicates the cause of the failure.
19227	10	No	An attempt to resize a buffer failed.
19228	10	No	An unexpected error occurred during a cryptographic handshake.
19229	10	No	An invalid token was received during a cryptographic handshake.
19230	10	No	Failed to allocate a packet for a network write during a cryptographic handshake.
19231	10	No	Failed to allocate an object to perform a cryptographic handshake.
19232	10	No	Failed to initialize an object to perform a cryptographic handshake.
19233	10	No	A token from a cryptographic handshake was larger than allowed by SSPI.
19234	10	No	The connection was closed while waiting for network IO during a cryptographic handshake.
19235	10	No	An unexpected exception was thrown while processing a cryptographic handshake.
19236	10	No	Negotiated security context is missing an integrity flag.
19238	10	No	Negotiated security context is missing a confidentiality flag.
19239	10	No	Negotiated security context has confidentiality flag present.
19240	10	No	Negotiated security context is missing a sequence detection flag.
19241	10	No	Negotiated security context is missing a replay detection flag.
19242	10	No	Global credentials handle required for inbound connections.
19243	10	No	SSPI structures too large for encryption.
19244	10	No	SSPI structures too large for signature.
19245	10	No	Empty output token is returned by SSPI during security context negotiation. Check for network packet corruption or other networking issues.
19246	10	No	Incomplete message error is returned from SSPI but failed to proceed.
19401	16	No	The 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.
19402	16	No	A 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.
19403	16	No	The 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.
19404	16	No	An 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.
19405	16	No	Failed 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.
19406	10	No	The 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.
19407	16	No	The 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.
19408	10	No	The 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.
19409	10	No	The 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.
19410	16	No	An 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.
19411	16	No	The 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.
19412	16	No	The 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.
19413	16	No	An 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.
19414	16	No	An 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.
19415	16	No	Failed 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.
19416	16	No	One 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.
19417	16	No	An 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.
19418	16	No	The 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.
19419	16	No	Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group '%.*ls' within the lease timeout period.
19420	10	No	The 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.
19421	16	No	SQL Server hosting availability group '%.*ls' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period.
19422	16	No	The 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').
19423	16	No	The lease of availability group '%.*ls' lease is no longer valid to start the lease renewal process.
19424	10	No	The 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.
19431	16	No	Always 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.
19432	16	No	Always 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.
19433	16	No	Always On: AG integrity check failed to find AG name to ID map entry with matching group ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
19434	16	No	Always On: AG integrity check failed to find AG name to ID map entry with matching resource ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
19435	16	No	Always On: AG integrity check failed for AG '%.*ls' with error %d, severity %d, state %d.
19436	16	No	Always 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].
19450	16	No	Failed 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.
19451	16	No	'%.*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.
19452	16	No	The 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.
19453	16	No	The 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.
19454	16	No	The 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.
19455	16	No	The 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.
19456	16	No	None 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.
19457	16	No	The 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.
19458	16	No	The 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.
19459	16	No	The 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.
19460	16	No	The 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.
19461	16	No	The 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.
19462	16	No	Failed 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.
19463	16	No	The 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.
19464	16	No	The 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.
19465	16	No	The 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.
19466	16	No	Failed 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.
19467	16	No	Failed 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.
19468	16	No	The 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.
19469	16	No	The specified listener with DNS name, '%.*ls', does not exist for the Availability Group '%.*ls'. Use an existing listener, or create a new listener.
19470	16	No	Failed 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).
19471	16	No	The 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.
19472	16	No	Failed 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.
19473	16	No	Failed 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.
19474	16	No	Failed 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.
19475	16	No	Cannot 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.
19476	16	No	The 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.
19477	16	No	The 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.
19478	16	No	Failed 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.
19479	16	No	The 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.
19480	16	No	Failed 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.
19481	16	No	Failed 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.
19482	16	No	The 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.
19483	16	No	The format for the IP address, '%.*ls', is invalid. Please use a valid value for the IP address.
19484	16	No	The 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.
19485	16	No	The 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.
19486	16	No	The 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.
19487	16	No	Listener 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.
19488	16	No	The 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.
19489	16	No	The attempt to create FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
19490	16	No	The attempt to delete FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
19491	10	No	Always On: The Windows Server Failover Clustering (WSFC) service was started using /forcequorum. This is an informational message only. No user action is required.
19492	16	No	The availability database %ls in availability 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.
19493	16	No	Corrupt 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.
19494	10	No	Automatic seeding of availability database '%ls' in availability group '%.*ls' failed with a transient error. The operation will be retried.
19495	10	No	Automatic 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.
19496	10	No	Automatic seeding of availability database '%.*ls' in availability group '%.*ls' failed.
19497	16	No	Conflicting option spec provided. DISTRIBUTED option cannot be combined with any other availability group options.
19498	16	No	To create a distributed availability group, please specify the DISTRIBUTED option.
19499	16	No	The 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.
19501	16	No	None of the specified availability groups exist locally. Please check your DDL and make sure there is one availability group exist locally.
19502	16	No	Cannot 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.
19503	16	No	Cannot create a distributed availability replica for availability group '%.*ls'. Local availability group is participating in a distributed availability group as secondary.
19504	16	No	Cannot failover a distributed availability replica for availability group '%.*ls'. Only force failover is supported in this version of SQL Server.
19505	10	No	Cannot 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.
19506	16	No	Local 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.
19507	16	No	Cannot create a distributed availability replica for availability group '%.*ls'. There is an already existing distributed availability group on top of the same replicas.
19508	16	No	'ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Participant availability replica '%.*ls' not found in the distributed availability group '%.*ls'.
19509	16	No	Cannot create a distributed availability group '%.*ls'. An availability group with the same name already exists.
19510	16	No	Distributed availability group '%.*ls' not found. Rerun the command with an existing distributed availbility group.
19511	16	No	Cannot 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.
19512	16	No	The 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.
19513	16	No	Cannot 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.
19514	10	No	Failed to wait for primary partner's transport up while starting up secondary remote replica.
19515	16	No	Database partner is missing during database restart.
19516	16	No	Creating Availability Group Listener '%.*ls' in Availability Group '%.*ls' with DISTRIBUTED_NETWORK_NAME option is not supported in non WSFC cluster.
19517	16	No	The specified listener with DNS name, '%.*ls' in Availability Group '%.*ls' is a DISTRIBUTED_NETWORK_NAME listener. Cannot add IP to a DISTRIBUTED_NETWORK_NAME listener.
19518	16	No	The listener port '%.*ls' is in conflict with other Availability Group listeners. Retry the operation with a unique port.
19519	16	No	Failed to set the WSFC cluster resource name to '%.*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.
19520	16	No	The DISTRIBUTED_NETWORK_NAME resource name '%.*ls' should match the listener port number but is invalid now. Modify the resource name back to the port number.
19521	16	No	The attempt to create the distributed network name for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the listener port number may be in conflict. Check the state of the WSFC cluster and validate the listener port number with the network administrator. Otherwise, contact your primary support provider.
19522	16	No	The attempt to retrieve local physical addresses from WSFC failed. Check the state of the WSFC cluster with the network administrator. Otherwise, contact your primary support provider.
19523	16	No	The specified '%.*ls' of Availability Group must be less than 256 characters long.
19524	16	No	Failed to create a database backup on a secondary replica for database "%.*ls.". Required information could not be committed on the primary replica. Check the health of the database in the SQL Server error log on the current primary replica. If the database is healthy, try the operation again.
19525	16	No	Failed to create a database backup on a secondary replica for database "%.*ls.". The differential bitmaps could not be cleared and the checkpoint could not be run on the primary replica. Check the health of the database in the SQL Server error log on the current primary replica. If the database is healthy, try the operation again.
19526	16	No	Failed to create a full backup on the secondary replica for database "%.*ls.". The primary database lock could not be acquired on the primary replica. Check the health of the database in the SQL Server error log on the current primary replica. If the database is healthy, try the operation again.
19527	16	No	Failed to initialize a full backup on the secondary replica for database "%.*ls.". Verify that the database is a member of the availability group, and then try again.
19528	16	No	Failed to create a full backup on secondary replica for database "%.*ls.". The checkpoint could not be run on the primary replica. Check the health of the database in the SQL Server error log on the current primary replica. If the database is healthy, try the operation again.
19529	16	No	Failed to create a database backup on secondary replica for database "%ls". The checkpoint LSN from primary replica could not be redone. Check the health of the database in the SQL Server error log on both primary and secondary replica. If the database is healthy, try the operation again.
19530	16	No	The %ls operation is not allowed by the current availability group configuration. The required_synchronized_secondaries_to_commit needs to be 0 when changing availability mode to ASYNCHRONOUS_COMMIT. Change required_synchronized_secondaries_to_commit to 0 and retry the operation.
19601	16	No	System error.
19602	16	No	System error.
19603	16	No	System error.
19604	16	No	System error.
19605	16	No	System error.
19606	16	No	System error.
19607	16	No	System error.
19608	16	No	System error.
19609	16	No	System error.
19610	16	No	System error.
19611	16	No	System error: "%ls".
19612	16	No	System error: '%.*ls', '%.*ls'.
19613	16	No	System error: '%.*ls'.
19614	16	No	System error: '%.*ls'.
19615	10	No	System error: '%s'.
19616	10	No	System error: '%s'.
19617	16	No	System error.
19618	16	No	System error.
19619	16	No	System error: %s.
19620	16	No	System error: %ld.
19621	16	No	System error: %s.
19701	10	No	1 row was rejected during query execution.
19702	10	No	%ld rows were rejected during query execution.
19703	16	No	Table manifest generation error.
19704	16	No	Missing %ls in ROWSET_OPTIONS. It is required when %ls is set.
19705	16	No	Failed to create a new database due to system error.
19706	16	No	Database edition was not properly set or is missing in the DDL statement.
19707	16	No	Failed to create a credential to access the data root container.
19708	16	No	Artifact ID was not properly set or is missing in the DDL statement.
19709	10	No	The specified bulk option '%ls' is not supported for file format '%ls'. Review the documentation for supported options.
19710	10	No	Master key for database '%.*ls' was automatically created because it did not exist.
19711	16	No	Failed to alter database due to system error.
19712	16	No	The Create External Table as Select operation is not supported for the connector specified by external data source '%.*ls'.
19713	16	No	Statistics on virtual column are not available.
19714	16	No	Number of columns in PARTITION clause does not match number of partition columns in Delta schema.
20001	10	No	There is no nickname for article '%s' in publication '%s'.
20002	10	No	The filter '%s' already exists for article '%s' in publication '%s'.
20003	10	No	Could not generate nickname for '%s'.
20004	10	No	Publication '%s' has the following property: '%s'. SQL Server subscribers below version '%s' will ignore this setting.
20005	18	No	%ls: Cannot convert parameter %ls: Resulting colv would have too many entries.
20006	16	No	Cannot 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.
20007	16	No	The system tables for merge replication could not be dropped successfully.
20008	16	No	The system tables for merge replication could not be created successfully.
20009	16	No	The article '%s' could not be added to the publication '%s'.
20010	16	No	The Snapshot Agent corresponding to the publication '%s' could not be dropped.
20011	16	No	Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property.
20012	16	No	The subscription type '%s' is not allowed on publication '%s'.
20013	16	No	The publication property '%s' cannot be changed when there are subscriptions on it.
20014	16	No	Invalid @schema_option value.
20015	16	No	Could not remove directory '%ls'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory.
20016	16	No	Invalid @subscription_type value. Valid values are 'pull' or 'anonymous'.
20017	16	No	The subscription on the Subscriber does not exist.
20018	16	No	The @optional_command_line is too long. Use an agent definition file.
20019	16	No	Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database.
20020	16	No	The article resolver supplied is either invalid or nonexistent.
20021	16	No	The subscription could not be found.
20022	16	No	This 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.
20023	16	No	Invalid @subscriber_type value. Valid options are 'local', 'global', or 'anonymous'.
20024	16	No	The alt_snapshot_folder cannot be the same as the working directory.
20025	16	No	The publication name must be unique. The specified publication name '%s' has already been used.
20026	16	No	The publication '%s' does not exist.
20027	16	No	The article '%s' does not exist.
20028	16	No	The Distributor has not been installed correctly. Could not enable database for publishing.
20029	16	No	The Distributor has not been installed correctly. Could not disable database for publishing.
20030	16	No	The article '%s' already exists on another publication with a different column tracking option.
20031	16	No	Could not delete the row because it does not exist.
20032	16	No	'%s' is not defined as a Subscriber for '%s'.
20033	16	No	Invalid publication type.
20034	16	No	Publication '%s' does not support '%s' subscriptions.
20036	16	No	The Distributor has not been installed correctly.
20037	16	No	The article '%s' already exists in another publication with a different article resolver.
20038	16	No	The article filter could not be added to the article '%s' in the publication '%s'.
20039	16	No	The article filter could not be dropped from the article '%s' in the publication '%s'.
20040	16	No	Could not drop the article(s) from the publication '%s'.
20041	16	No	Transaction rolled back. Could not execute trigger. Retry your transaction.
20043	16	No	Could not change the article '%s' because the publication has already been activated.
20044	16	No	The priority property is invalid for local subscribers.
20045	16	No	You must supply an article name.
20046	16	No	The article does not exist.
20047	16	No	You are not authorized to perform this operation.
20048	16	No	To 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.
20049	16	No	The priority value should not be larger than 100.0.
20050	16	No	The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999.
20051	16	No	The Subscriber is not registered.
20052	16	No	The @metatype parameter value must be null, 1, 2, 5, or 6.
20053	16	No	An article with a different %s value already exists for object '%s'.
20054	16	No	Current database is not enabled for publishing.
20055	16	No	Table '%s' cannot be published for merge replication because it has a timestamp column.
20056	16	No	Table '%s' cannot be republished.
20057	16	No	The profile name '%s' already exists for the specified agent type.
20058	16	No	The @agent_type must be 1 (Snapshot), 2 (Logreader), 3 (Distribution), or 4 (Merge)
20059	16	No	The @profile_type must be 0 (System) or 1 (Custom)
20060	16	No	Compatibility level cannot be smaller than 60.
20061	16	No	The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.
20062	16	No	Updating columns with the rowguidcol property is not allowed.
20063	16	No	Table '%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.
20064	16	No	Cannot drop profile. Either it is not defined or it is defined as the default profile.
20065	16	No	Cannot drop profile because it is in use.
20066	16	No	Profile not defined.
20067	16	No	The parameter name '%s' already exists for the specified profile.
20068	16	No	The article cannot be created on table '%s' because it has more than %d columns.
20069	16	No	Cannot validate a merge article that uses looping join filters.
20070	16	No	Cannot update subscription row.
20072	16	No	Cannot update Subscriber information row.
20073	16	No	Articles can be added or changed only at the Publisher.
20074	16	No	Only a table object can be published as a "table" article for merge replication.
20075	16	No	The 'status' parameter value must be either 'active' or 'unsynced'.
20076	16	No	The @sync_mode parameter value must be 'native' or 'character'.
20077	16	No	Problem encountered generating replica nickname.
20078	16	No	The @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'.
20079	16	No	Invalid @subscription_type parameter value. Valid options are 'push', 'pull', or 'both'.
20081	16	No	Publication property '%s' cannot be NULL.
20084	16	No	Publication '%s' cannot be subscribed to by Subscriber database '%s'.
20086	16	No	Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column.
20087	16	No	You cannot push an anonymous subscription.
20088	16	No	Only assign priorities that are greater than or equal to 0 and less than 100.
20089	16	No	Could not get license information correctly.
20090	16	No	Could not get version information correctly.
20091	16	No	sp_mergesubscription_cleanup is used to clean up push subscriptions. Use sp_dropmergepullsubscription to clean up pull or anonymous subscriptions.
20092	16	No	Table '%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.
20093	16	No	Merge replication upgrade is not complete until the snapshot agent is run for the publisher and the merge agent run for all the subscribers.
20094	10	No	Profile parameter '%s' is dynamically reloadable and the change will be applied to running agents within configured period of time.
20095	10	No	For agent profile '%s', parameters marked as is_reloadable in msdb.dbo.MSagentparameterlist table will be applied to running agents within configured period of time.
20100	16	No	Cannot drop Subscriber '%s'. There are existing subscriptions.
20500	16	No	The updatable Subscriber stored procedure '%s' does not exist.
20501	16	No	Could not insert into sysarticleupdates using sp_articlecolumn.
20502	16	No	Invalid '%s' value. Valid values are 'read only', 'sync tran', 'queued tran', or 'failover'.
20503	16	No	Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions.
20504	16	No	Immediate Updating Subscriptions: The xml values inserted/updated by Subscriber will be replicated as NULL to publisher.
20505	16	No	Could not drop synchronous update stored procedure '%s' in '%s'.
20506	16	No	Source table '%s' not found in '%s'.
20507	16	No	Table '%s' not found in '%s'.
20508	11	No	Updatable subscriptions: The text, ntext, or image values inserted at the Subscriber will be NULL.
20509	16	No	Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber.
20510	16	No	Updateable Subscriptions: Cannot update identity columns.
20511	16	No	Updateable Subscriptions: Cannot update timestamp columns.
20512	16	No	Updateable Subscriptions: Rolling back transaction.
20513	16	No	Database '%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.
20514	10	No	A rowcount validation request has been submitted to heterogeneous publisher %s for article %s of publication %s. Validation results will be posted to distribution history.
20515	16	No	Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber.
20516	16	No	Updateable Subscriptions: Replicated data is not updatable.
20518	16	No	Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column.
20519	16	No	Updateable Subscriptions: INSERT operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
20520	16	No	Updateable Subscriptions: UPDATE operations on tables with identity or timestamp columns are not allowed unless a primary key is defined at the Subscriber.
20521	16	No	sp_MSmark_proc_norepl: must be a member of the db_owner or sysadmin roles.
20522	16	No	sp_MSmark_proc_norepl: invalid object name '%s'.
20523	16	No	Could not validate the article '%s'. It is not activated.
20524	10	No	Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast).
20525	10	No	Table '%s' might be out of synchronization. Rowcounts (actual: %s, expected %s). Checksum values (actual: %s, expected: %s).
20526	10	No	Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast).
20527	10	No	Table '%s' passed rowcount (%s) and checksum validation. Checksum is not compared for any text or image columns.
20528	10	No	Log Reader Agent startup message.
20529	10	No	Starting agent.
20530	10	No	Run agent.
20531	10	No	Detect nonlogged agent shutdown.
20532	10	No	Replication agent schedule.
20533	10	No	Replication agents checkup
20534	10	No	Detects replication agents that are not logging history actively.
20535	10	No	Removes replication agent history from the distribution database.
20536	10	No	Replication: agent failure
20537	10	No	Replication: agent retry
20538	10	No	Replication: expired subscription dropped
20539	10	No	Replication Warning: %s (Threshold: %s)
20540	10	No	Replication: agent success
20541	10	No	Removes replicated transactions from the distribution database.
20542	10	No	Detects and removes expired subscriptions from published databases or distribution databases.
20543	10	No	@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.
20545	10	No	Default agent profile
20546	10	No	Verbose history agent profile.
20547	10	No	Agent profile for detailed history logging.
20548	10	No	Slow link agent profile.
20549	10	No	Agent profile for low bandwidth connections.
20550	10	No	Windows Synchronization Manager profile
20551	10	No	Profile used by the Windows Synchronization Manager.
20552	10	No	Could not clean up the distribution transaction tables.
20553	10	No	Could not clean up the distribution history tables.
20554	10	No	The 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.
20555	10	No	6.x publication.
20556	10	No	Heartbeats detected for all running replication agents.
20557	10	Yes	Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'.
20558	10	No	Table '%s' passed full rowcount validation after failing the fast check. DBCC UPDATEUSAGE will be initiated automatically.
20559	10	No	Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used.
20560	10	No	An expected checksum value was passed, but checksums will not be compared because rowcount-only checking was requested.
20561	10	No	Generated expected rowcount value of %s for %s.
20565	10	No	Replication: Subscriber has failed data validation
20566	10	No	Replication: Subscriber has passed data validation
20567	10	No	Agent history clean up: %s
20568	10	No	Distribution clean up: %s
20569	10	No	Expired subscription clean up
20570	10	No	Reinitialize subscriptions having data validation failures
20571	10	No	Reinitializes all subscriptions that have data validation failures.
20572	10	Yes	Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure.
20573	10	No	Replication: Subscription reinitialized after validation failure
20574	10	Yes	Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation.
20575	10	No	Subscriber '%s' subscription to article '%s' in publication '%s' passed data validation.
20576	10	No	Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure.
20577	10	No	No entries were found in msdb..sysreplicationalerts.
20578	10	No	Replication: agent custom shutdown
20579	10	No	Generated expected rowcount value of %s and expected checksum value of %s for %s.
20580	10	No	Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'.
20581	10	No	Cannot drop server '%s' because it is used as a Distributor in replication.
20582	10	No	Cannot drop server '%s' because it is used as a Publisher in replication.
20583	10	No	Cannot drop server '%s' because it is used as a Subscriber in replication.
20584	10	No	Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication.
20585	16	No	Validation Failure. Object '%s' does not exist.
20586	16	No	(default destination)
20587	16	No	Invalid '%s' value for stored procedure '%s'.
20588	16	No	The subscription is not initialized. Run the Distribution Agent first.
20589	10	No	Agent profile for replicated queued transaction reader.
20590	16	No	The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow data transformations.
20591	16	No	Only 'DTS horizontal partitions' and 'no DTS horizontal partitions' are valid 'status' values because the publication allows data transformations.
20592	16	No	'dts horizontal partitions' and 'no dts horizontal partitions' are not valid 'status' values because the publication does not allow data transformations.
20593	16	No	Cannot modify publication '%s'. The sync_method cannot be changed to 'native', or 'concurrent' because the publication is enabled for heterogeneous subscribers.
20594	16	No	A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions.
20595	16	No	Skipping error signaled.
20596	16	No	Only '%s' or members of db_owner can drop the anonymous agent.
20597	10	No	Dropped %d anonymous subscription(s).
20598	16	No	The row was not found at the Subscriber when applying the replicated %S_MSG command for Table '%s' with Primary Key(s): %s
20599	16	No	Continue on data consistency errors.
20600	10	No	Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers.
20601	10	No	Invalid value specified for agent parameter 'SkipErrors'.
20602	10	No	The value specified for agent parameter 'SkipErrors' is too long.
20603	10	No	The agent profile cannot be used by heterogeneous Subscribers.
20604	10	No	You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'.
20605	10	No	Invalidated the existing snapshot of the publication. Run the Snapshot Agent again to generate a new snapshot.
20606	10	No	Reinitialized subscription(s).
20607	10	No	Cannot make the change because a snapshot is already generated. Set @force_invalidate_snapshot to 1 to force the change and invalidate the existing snapshot.
20608	10	No	Cannot make the change because there are active subscriptions. Set @force_reinit_subscription to 1 to force the change and reinitialize the active subscriptions.
20609	16	No	Cannot attach subscription file '%s'. Make sure that it is a valid subscription copy file.
20610	16	No	Cannot run '%s' when the Log Reader Agent is replicating the database.
20611	16	No	Cannot 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.
20612	16	No	Checksum validation is not supported because the publication allows DTS. Use row count only validation.
20613	16	No	Validation is not supported for articles that are set up for DTS horizontal partitions.
20614	16	No	Validation is not supported for heterogeneous Subscribers.
20615	16	No	Unable to add a heterogeneous subscription to the publication. The publication is not enabled for heterogeneous subscriptions.
20616	10	No	High Volume Server-to-Server Profile
20617	10	No	Merge agent profile optimized for the high volume server-to-server synchronization scenario.
20618	16	No	You must have CREATE DATABASE permission to attach a subscription database.
20619	16	No	Server user '%s' is not a valid user in database '%s'. Add the user account or 'guest' user account into the database first.
20620	11	No	The security mode specified requires the server '%s' to be registered as a linked server. Use sp_addlinkedserver to add the server.
20621	11	No	Cannot copy a subscription database to an existing database.
20622	11	No	Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode.
20623	11	No	You cannot validate article '%s' unless you have 'SELECT ALL' permission on table '%s'.
20624	16	No	The 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.
20625	16	No	Cannot 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.
20626	16	No	Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter.
20627	16	No	Partition id has to be greater than or equal to 0.
20628	16	No	Failed to generate dynamic snapshot.
20629	16	No	Failed to get partition id information.
20630	16	No	Cannot 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.
20631	16	No	Cannot 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.
20632	16	No	Failed to create a dynamic snapshot job to generate the dynamic snapshot.
20633	16	No	Cannot start the partitioned snapshot job. Verify that SQL Server Agent is running on the Distributor.
20634	16	No	The root publication information could not be found on the republisher.
20635	16	No	A push subscription to '%ls' was found. Cannot add a pull subscription agent for a push subscription.
20636	16	No	Cannot 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.
20637	10	No	The 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.
20638	10	No	Merge 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.
20639	16	No	Cannot 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'.
20640	16	No	Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.
20641	16	No	Failed to check if the subset_filterclause has a dynamic function in it.
20642	16	No	Cannot 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.
20643	16	No	Cannot 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.
20644	16	No	Invalid value "%s" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none".
20645	16	No	The property "%s" cannot be modified for publications that are enabled for non-SQL Server subscriptions.
20646	16	No	Peer-to-peer publications do not support %s. Change the value for parameter '%s'.
20647	16	No	Cannot 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.
20648	16	No	An 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).
20649	16	No	Publications enabled for heterogeneous subscriptions do not support %s. Please change the '%s' parameter value.
20650	16	No	Cannot 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.
20651	16	No	Publication "%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.
20652	16	No	Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.
20653	16	No	Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.
20654	16	No	Dynamic snapshots are only valid for merge publications.
20655	16	No	The 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.
20656	16	No	The @subset_filterclause parameter cannot reference a computed column.
20657	16	No	The 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.
20658	16	No	The 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.
20659	11	No	The value of IDENT_CURRENT ("%s") is greater than the value in the max_used column of the MSmerge_identity_range system table.
20660	16	No	The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range.
20661	16	No	The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @identity_range.
20662	16	No	The 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.
20663	16	No	The 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".
20664	16	No	The 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.
20665	16	No	The 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.
20666	16	No	Cannot 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.
20667	16	No	Cannot allocate an identity range for article "%s". The article is not enabled for automatic identity range management.
20668	16	No	Not enough range available to allocate a new range for a subscriber.
20669	16	No	Object referenced by the given @article or @artid '%s' could not be found.
20670	16	No	Cannot 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.
20671	16	No	Cannot find the identity range allocation entry for the Subscriber in the MSmerge_identity_range table. Reinitialize the subscription.
20672	16	No	A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering.
20673	16	No	A value for the parameter @host_name was specified, but no articles in the publication use SUSER_SNAME() for parameterized filtering.
20674	16	No	The publication does not use dynamic filtering.
20675	16	No	The identity range values cannot be NULL.
20676	11	No	Cannot refresh the Publisher identity range for article "%s". Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity range.
20677	11	No	Cannot add article "%s" with automatic identity range management. The article is already published in a transactional publication with automatic identity range management.
20678	11	No	Could not find the regular snapshot job for the specified publication '%s'.
20679	11	No	Cannot 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.
20680	16	No	Failed to get metadata for a batch of rows.
20681	10	No	Cannot 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.
20682	10	No	Failed deletion of rows in batched delete attempt on table %s.
20683	16	No	Failed batched deletion on download only article %s.
20684	16	No	Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent.
20685	16	No	Cannot drop the filter '%s' . The filter specified for the @filtername parameter cannot be found.
20686	16	No	Parameter '%s' cannot be NULL or empty when this procedure is run from a '%s' database.
20687	16	No	Parameter '%s' must be NULL when this procedure is not being run from a '%s' database.
20688	16	No	The 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.
20689	16	No	The 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.
20690	16	No	Cannot 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.
20691	16	No	Merge replication upgrade of SQL Server 2005 metadata and triggers on the subscriber failed.
20692	16	No	One 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.
20693	16	No	One 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.
20694	16	No	One 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.
20695	16	No	Only %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.
20696	16	No	The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication.
20697	16	No	Cannot 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.
20698	16	No	A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering.
20699	16	No	A value for the parameter @suser_sname was not specified while publication uses SUSER_SNAME() for dynamic filtering.
20701	16	No	The dynamic snapshot job schedule could not be changed on the distributor.
20702	16	No	The dynamic snapshot job schedule could not be changed due to one or more errors.
20703	16	No	One or more rows inserted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20704	16	No	The 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.
20705	10	No	Cannot 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'.
20706	10	No	The max or min allowed identity numbers for the identity column could not be found for the given article.
20707	10	No	Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors.
20708	10	No	An article is not allowed to be part of a logical record when it has a custom business logic resolver.
20709	10	No	The merge process could not clean up the conflict table "%s" for publication "%s".
20710	16	No	Incorrect 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'.
20711	16	No	The 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.
20712	16	No	Unable 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.
20713	16	No	Replication merge admin stored procedure '%s' failed for publication '%s'. This could be due an active snapshot running while the admin proc was called.
20714	16	No	Failed to prepare article '%s' in publication '%s' for merge replication.
20715	16	No	Failed to create merge replication triggers for object '%s'.
20716	16	No	Failed to create publication views for merge replication publication '%s'.
20717	16	No	sp_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.
20718	16	No	Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'. Use sp_addmergelogsettings to add the settings.
20719	16	No	sp_changemergelogsettings failed to update log settings. Check the parameter values.
20720	16	No	Log settings do not exist for subscriber server '%s', subscriber db '%s', webserver '%s'.
20721	16	No	sp_dropmergelogsettings failed to remove log settings.
20722	16	No	'%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].
20723	16	No	Computed column "%s" can only be added to publication after its depending object "%s" is added.
20724	16	No	Could not find a valid command line for the dynamic snapshot job with job_id '%s' for publication '%s'.
20725	16	No	Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id '%s' in publication '%s'.
20726	16	No	Failed to change the dynamic snapshot location in one or more dynamic snapshot jobs for the given publication.
20727	16	No	An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'.
20728	16	No	Failed to restore the max allocated identity value for article '%s' in publication '%s'.
20729	16	No	The max identity value allocation for article '%s' in publication '%s' could not be found on the distributor.
20730	16	No	Setting @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.
20731	16	No	This edition of SQL Server does not support publications. Dropping existing publications.
20732	10	No	Warning: 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.
20733	16	No	One or more rows updated in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20734	16	No	One or more rows deleted in table '%s' were out of partition while the table was published with 'partition_options' set to %d.
20735	16	No	Cannot add article '%s' to publication '%s'. The publication already contains 256 articles, which is the maximum.
20736	10	No	Warning: 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.
20737	10	No	Warning: 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'.
20738	11	No	Cannot add article '%s' with sparse column or column set to merge publication since merge replication does not support sparse columns and column set.
20739	16	No	The 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.
20800	16	No	Cannot 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.
20801	16	No	Cannot 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.
20802	16	No	Cannot 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.
20803	16	No	Peer-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].
20804	16	No	Articles can only be included in a single peer-to-peer publication. [%s].[%s] is already included in the peer-to-peer publication '%s'.
20805	16	No	Peer-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].
20806	16	No	An error occurred while executing a peer-to-peer forwarding command. Contact Customer Support Services.
20807	16	No	No 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.
20808	16	No	The peer-to-peer publication '%s' does not exist. Execute sp_helppublication to view a list of publication names.
20809	16	No	Peer-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].
20810	16	No	The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type article.
20811	16	No	Replication monitoring refresher for %s.
20812	16	No	The specified source object must be a synonym if it is published as a 'synonym schema only' type article.
20813	16	No	Only members of the sysadmin fixed server role can modify a %s that does not have a job with a proxy account defined.
20814	10	No	Distribution Profile for OLEDB streaming
20815	10	No	Distribution agent profile enabled for the processing LOB data using OLEDB streaming.
20816	10	No	Peer-To-Peer publishers are only supported on Enterprise class editions of SQL Server. This instance is %s.
20817	16	No	An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'.

Related content

• Database Engine events and errors
• Understanding Database Engine Errors
• Cause and Resolution of Database Engine Errors