Errors 20000 - 20999

20001

10

No

There is no nickname for article '%s' in publication '%s'.

20003

10

No

Could not generate nickname for '%s'.

20005

18

No

%ls: Cannot convert parameter %ls: Resulting colv would have too many entries.

20007

16

No

The system tables for merge replication could not be dropped successfully.

20009

16

No

The article '%s' could not be added to the publication '%s'.

20011

16

No

Cannot set incompatible publication properties. The 'allow_anonymous' property of a publication depends on the 'immediate_sync' property.

20013

16

No

The publication property '%s' cannot be changed when there are subscriptions on it.

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.

20017

16

No

The subscription on the Subscriber does not exist.

20019

16

No

Replication database option '%s' cannot be set unless the database is a publishing database or a distribution database.

20021

16

No

The subscription could not be found.

20023

16

No

Invalid @subscriber_type value. Valid options are 'local', 'global', or 'anonymous'.

20025

16

No

The publication name must be unique. The specified publication name '%s' has already been used.

20027

16

No

The article '%s' does not exist.

20029

16

No

The Distributor has not been installed correctly. Could not disable database for publishing.

20031

16

No

Could not delete the row because it does not exist.

20033

16

No

Invalid publication type.

20036

16

No

The Distributor has not been installed correctly.

20038

16

No

The article filter could not be added to the article '%s' in the publication '%s'.

20040

16

No

Could not drop the article(s) from the publication '%s'.

20043

16

No

Could not change the article '%s' because the publication has already been activated.

20045

16

No

You must supply an article name.

20047

16

No

You are not authorized to perform this operation.

20049

16

No

The priority value should not be larger than 100.0.

20051

16

No

The Subscriber is not registered.

20053

16

No

An article with a different %s value already exists for object '%s'.

20055

16

No

Table '%s' cannot be published for merge replication because it has a timestamp column.

20057

16

No

The profile name '%s' already exists for the specified agent type.

20059

16

No

The @profile_type must be 0 (System) or 1 (Custom)

20061

16

No

The compatibility level of this database must be set to 70 or higher to be enabled for merge publishing.

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.

20065

16

No

Cannot drop profile because it is in use.

20067

16

No

The parameter name '%s' already exists for the specified profile.

20069

16

No

Cannot validate a merge article that uses looping join filters.

20072

16

No

Cannot update Subscriber information row.

20074

16

No

Only a table object can be published as a "table" article for merge replication.

20076

16

No

The @sync_mode parameter value must be 'native' or 'character'.

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'.

20081

16

No

Publication property '%s' cannot be NULL.

20086

16

No

Publication '%s' does not support the nosync type because it contains a table that does not have a rowguidcol column.

20088

16

No

Only assign priorities that are greater than or equal to 0 and less than 100.

20090

16

No

Could not get version information correctly.

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.

20100

16

No

Cannot drop Subscriber '%s'. There are existing subscriptions.

20501

16

No

Could not insert into sysarticleupdates using sp_articlecolumn.

20503

16

No

Invalid '%s' value in '%s'. The publication is not enabled for '%s' updatable subscriptions.

20505

16

No

Could not drop synchronous update stored procedure '%s' in '%s'.

20507

16

No

Table '%s' not found in '%s'.

20509

16

No

Updatable subscriptions: The text, ntext, or image values cannot be updated at the Subscriber.

20511

16

No

Updateable Subscriptions: Cannot update timestamp columns.

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.

20515

16

No

Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber.

20518

16

No

Updateable Subscriptions: INSERT and DELETE operations are not supported unless published table has a timestamp column.

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.

20522

16

No

sp_MSmark_proc_norepl: invalid object name '%s'.

20524

10

No

Table '%s' may be out of synchronization. Rowcounts (actual: %s, expected: %s). Rowcount method %d used (0 = Full, 1 = Fast).

20526

10

No

Table '%s' passed rowcount (%s) validation. Rowcount method %d used (0 = Full, 1 = Fast).

20528

10

No

Log Reader Agent startup message.

20530

10

No

Run agent.

20532

10

No

Replication agent schedule.

20534

10

No

Detects replication agents that are not logging history actively.

20536

10

No

Replication: agent failure

20538

10

No

Replication: expired subscription dropped

20540

10

No

Replication: agent success

20542

10

No

Detects and removes expired subscriptions from published databases.

20545

10

No

Default agent profile

20547

10

No

Agent profile for detailed history logging.

20549

10

No

Agent profile for low bandwidth connections.

20551

10

No

Profile used by the Windows Synchronization Manager.

20553

10

No

Could not clean up the distribution history tables.

20555

10

No

6.x publication.

20557

10

Yes

Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'.

20559

10

No

Conditional Fast Rowcount method requested without specifying an expected count. Fast method will be used.

20561

10

No

Generated expected rowcount value of %s for %s.

20566

10

No

Replication: Subscriber has passed data validation

20568

10

No

Distribution clean up: %s

20570

10

No

Reinitialize subscriptions having data validation failures

20572

10

Yes

Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a validation failure.

20574

10

Yes

Subscriber '%s' subscription to article '%s' in publication '%s' failed data validation.

20576

10

No

Subscriber '%s' subscription to article '%s' in publication '%s' has been reinitialized after a synchronization failure.

20578

10

No

Replication: agent custom shutdown

20580

10

No

Heartbeats not detected for some replication agents. The status of these agents have been changed to 'Failed'.

20582

10

No

Cannot drop server '%s' because it is used as a Publisher in replication.

20584

10

No

Cannot drop server '%s' because it is used as a Subscriber to remote Publisher '%s' in replication.

20586

16

No

(default destination)

20588

16

No

The subscription is not initialized. Run the Distribution Agent first.

20590

16

No

The article property 'status' cannot include bit 64, 'DTS horizontal partitions' because the publication does not allow 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.

20594

16

No

A push subscription to the publication exists. Use sp_subscription_cleanup to drop defunct push subscriptions.

20596

16

No

Only '%s' or members of db_owner can drop the anonymous agent.

20598

16

No

The row was not found at the Subscriber when applying the replicated command.

20600

10

No

Agent profile for skipping data consistency errors. It can be used only by SQL Server Subscribers.

20602

10

No

The value specified for agent parameter 'SkipErrors' is too long.

20604

10

No

You do not have permissions to run agents for push subscriptions. Make sure that you specify the agent parameter 'SubscriptionType'.

20606

10

No

Reinitialized subscription(s).

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.

20610

16

No

Cannot run '%s' when the Log Reader Agent is replicating the database.

20612

16

No

Checksum validation is not supported because the publication allows DTS. Use row count only validation.

20614

16

No

Validation is not supported for heterogeneous Subscribers.

20616

10

No

High Volume Server-to-Server Profile

20618

16

No

You must have CREATE DATABASE permission to attach a subscription database.

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.

20622

11

No

Replication database option 'sync with backup' cannot be set on the publishing database because the database is in Simple Recovery mode.

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.

20626

16

No

Filter '%s' already exists in publication '%s'. Specify a unique name for the @filtername parameter of sp_addmergefilter.

20628

16

No

Failed to generate dynamic snapshot.

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.

20632

16

No

Failed to create a dynamic snapshot job to generate the dynamic snapshot.

20634

16

No

The root publication information could not be found on the republisher.

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.

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.

20640

16

No

Cannot change enabled for heterogeneous subscriptions property while there are subscriptions to the publication.

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.

20644

16

No

Invalid value "%s" specified for the parameter @identityrangemangementoption. Valid values are "auto", "manual", or "none".

20646

16

No

Peer-to-peer publications do not support %s. Change the value for parameter '%s'.

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).

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.

20652

16

No

Required metadata for publication '%s' could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.

20654

16

No

Dynamic snapshots are only valid for merge publications.

20656

16

No

The @subset_filterclause parameter cannot reference a computed column.

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.

20660

16

No

The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_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.

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.

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.

20668

16

No

Not enough range available to allocate a new range for a subscriber.

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.

20672

16

No

A value for the parameter @host_name was specified, but no articles in the publication use HOST_NAME() for parameterized filtering.

20674

16

No

The publication does not use dynamic filtering.

20676

11

No

Cannot refresh the Publisher identity range for article "%s". Execute the stored procedure sp_adjustpublisheridentityrange to refresh the identity range.

20678

11

No

Could not find the regular snapshot job for the specified publication '%s'.

20680

16

No

Failed to get metadata for a batch of rows.

20682

10

No

Failed deletion of rows in batched delete attempt on table %s.

20684

16

No

Deleted more rows than expected in the batched delete attempt on table %s. Stop and restart the Merge Agent.

20686

16

No

Parameter '%s' cannot be NULL or empty when this procedure is 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.

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.

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.

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.

20696

16

No

The object %s is marked as shipped by Microsoft (ms_shipped). It cannot be added as an article for merge replication.

20698

16

No

A value for the parameter @host_name was not specified while publication uses HOST_NAME() for dynamic filtering.

20701

16

No

The dynamic snapshot job schedule could not be changed on the distributor.

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.

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'.

20707

10

No

Failed to publish the article with identityrangemanagementoption set to 'auto' due to one or more errors.

20709

10

No

The merge process could not clean up the conflict table "%s" for publication "%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.

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.

20715

16

No

Failed to create merge replication triggers for object '%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.

20719

16

No

sp_changemergelogsettings failed to update log settings. Check the parameter values.

20721

16

No

sp_dropmergelogsettings failed to remove log settings.

20723

16

No

Computed column "%s" can only be added to publication after its depending object "%s" is added.

20725

16

No

Unable to update the dynamic snapshot location for the dynamic snapshot job with job_id '%s' in publication '%s'.

20727

16

No

An invalid value was specified for parameter @subscription_type. Valid values are 'push', 'pull', 'both', 'anonymous' or 'all'.

20729

16

No

The max identity value allocation for article '%s' in publication '%s' could not be found on the distributor.

20731

16

No

This edition of SQL Server does not support publications. Dropping existing publications.

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.

20735

16

No

Cannot add article '%s' to publication '%s'. The publication already contains 256 articles, which is the maximum.

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'.

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.

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.

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].

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].

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.

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].

20811

16

No

Replication monitoring refresher for %s.

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.

20815

10

No

Distribution agent profile enabled for the processing LOB data using OLEDB streaming.

20817

16

No

An error occurred during the execution of '%ls'. A call to '%ls' failed with error code: '%ld', return code: '%d'.