SQL Server Errors or Failures from Error: 20646 to Error: 20665
Error: 20646, Severity: 16, Peer-to-peer publications do not support %s. Change the value for parameter ‘%s’.
Error: 20647, Severity: 16, 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.
Error: 20648, Severity: 16, 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
Error: 20649, Severity: 16, Publications enabled for heterogeneous subscriptions do not support %s. Please change the ‘%s’ parameter value.
Error: 20650, Severity: 16, 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 procedu
Error: 20651, Severity: 16, 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
Error: 20652, Severity: 16, Required metadata for publication ‘%s’ could not be found in the sysmergeschemachange system table. Run the Snapshot Agent again.
Error: 20653, Severity: 16, Cannot have a dynamic snapshot job with both dynamic_filter_login and dynamic_filter_hostname being NULL.
Error: 20654, Severity: 16, Dynamic snapshots are only valid for merge publications.
Error: 20655, Severity: 16, 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.
Error: 20656, Severity: 16, The @subset_filterclause parameter cannot reference a computed column.
Error: 20657, Severity: 16, 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.
Error: 20658, Severity: 16, 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.
Error: 20659, Severity: 11, The value of IDENT_CURRENT (“%s”) is greater than the value in the max_used column of the MSmerge_identity_range system table.
Error: 20660, Severity: 16, The republisher’s republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range.
Error: 20661, Severity: 16, The republisher’s republishing range obtained from its publisher is not large enough to allocate the specified @identity_range.
Error: 20662, Severity: 16, 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 sy
Error: 20663, Severity: 16, 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”.
Error: 20664, Severity: 16, 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.
Error: 20665, Severity: 16, 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.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.