SQL Server Errors or Failures from Error: 22806 to Error: 22825

SQLServerF1

 

Error: 22806, Severity: 16, The originator ID ‘%s’ is not valid. You must specify a non-zero ID that has never been used in the topology.
Error: 22807, Severity: 16, The publication property ‘%s’ cannot be modified because the peer-to-peer publication ‘%s’ is not enabled for conflict detection. To enable the publication for conflict detection, use sp_configure_peerconflictdetection.
Error: 22808, Severity: 16, Cannot execute procedure ‘%s’. Publication ‘%s’ must be enabled for peer-to-peer replication before you execute this procedure. To enable the publication for peer-to-peer replication, use sp_changepublication.

Error: 22809, Severity: 10, The existing conflict table ‘%s’ was dropped.
Error: 22810, Severity: 16, The @action parameter value is not valid. Valid values are ‘enable’ and ‘disable’.
Error: 22811, Severity: 16, The roundtrip time-out must be greater than 0.
Error: 22812, Severity: 10, The roundtrip ‘%s’ finished with timeout: %d seconds.
Error: 22813, Severity: 10, The topology contains peer node versions that do not support conflict detection. To use conflict detection, ensure that all nodes in the topology are SQL Server 2008 or later versions.

Error: 22814, Severity: 10, The topology contains a duplicate originator ID. To use conflict detection, the originator ID must be unique across the topology.
Error: 22815, Severity: 10, A conflict of type ‘%s’ was detected at peer %d between peer %d (incoming), transaction id %s and peer %d (on disk), transaction id %s
Error: 22816, Severity: 16, The qualified table name ‘%s’ is too long to be enabled for peer-to-peer conflict detection.
Error: 22817, Severity: 10, %s has %s.
Error: 22818, Severity: 10, A delete-delete conflict was detected and resolved. The row could not be deleted from the peer since the row does not exist. The incoming delete was skipped.
Error: 22819, Severity: 10, A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and could not be resolved automatically. The incoming delete was skipped by peer %d. The conflict has to be resolved manually to guarantee data convergence between the
Error: 22820, Severity: 10, A delete-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming delete was applied to peer %d.
Error: 22821, Severity: 10, An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was skipped by peer %d.
Error: 22822, Severity: 10, An update-update conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming update was applied to peer %d.
Error: 22823, Severity: 10, An update-delete conflict was detected and unresolved. The row could not be updated since the row does not exist. The incoming update was skipped. Check the priority of the destination peer and run data validation to ensure the delete conflict did not re
Error: 22824, Severity: 10, An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was skipped by peer %d.
Error: 22825, Severity: 10, An insert-insert conflict between peer %d (incoming) and peer %d (on disk) was detected and resolved. The incoming insert was applied to peer %d.

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.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *