SQL Server Errors or Failures from Error: 21725 to Error: 21745
Error: 21725, Severity: 16, Cannot alter the view. An indexed view replicated as a table cannot be altered to a nonindexed view. Drop the view from the publication before attempting to alter it.
Error: 21727, Severity: 14, Cannot complete the replication operation. The security check for the current user is failing. Only members of the sysadmin fixed server role, or db_owner or db_ddladmin fixed database roles can perform this operation.
Error: 21728, Severity: 16, The article can support logical record level conflict detection only if it uses logical record conflict resolution.
Error: 21729, Severity: 16, The @keep_partition_changes property cannot be set to “true.”
This is because the @publication_compatibility_level property is set to 90RTM or higher and the @use_partition_groups property is set to “true.” Set a lower compatibility level or set the @use_
Error: 21730, Severity: 16, Table ‘%s’ can not be replicated because it contains imprecise Primary Key column, please recreate table without ‘persisted’ clause and try again.
Error: 21731, Severity: 16, Cannot add a constraint or default without an explicit name, because the table is included in a publication that replicates DDL events. Specify a unique name for the constraint and then reissue the DDL statement.
Error: 21732, Severity: 16, Using Data Transformation Services (DTS) packages in replication requires a password that is not NULL or empty. Specify a valid value for parameter ‘%s’.
Error: 21733, Severity: 16, Cannot open database %s. The upgrade of replication %s could not be performed. Run %s again from the %s database when the %s is accessible.
Error: 21734, Severity: 16, Peer-to-peer publications do not support replicating timestamp columns as varbinary(8). You cannot add an article with this option, nor add or alter a table to include a timestamp column as varbinary(8).
Error: 21735, Severity: 16, Source object [%s].[%s] is a temporary object and cannot be published.
Error: 21736, Severity: 16, Unable to relocate the article log table to a different tablespace. Verify that the replication administrative user login can connect to the Oracle Publisher using SQL*PLUS. If you can connect, but the problem persists, it might be caused by insufficient
Error: 21737, Severity: 16, The property ‘%s’ is not valid for ‘%s’ Publishers.
Error: 21738, Severity: 16, The property ‘%s’ is not valid for %s publications.
Error: 21739, Severity: 16, Cannot alter property ‘%s’. You must first call the stored procedure sp_articleview to initialize the article; the property can then be altered.
Error: 21740, Severity: 16, Oracle subscriber ‘%s’ not found. Loopback support cannot be checked.
Error: 21741, Severity: 16, Unable to retrieve distributor information from Oracle publisher ‘%s’. Bi-directional publishing requires Oracle publisher to exist before the Oracle subscriber.
Error: 21742, Severity: 16, The Oracle Publisher name is ‘%s’ and the Oracle Subscriber name is ‘%s’. Bidirectional Oracle publishing requires the Oracle Publisher and Subscriber names to be the same.
Error: 21743, Severity: 16, Unable to retrieve the originator information for the Oracle subscriber ‘%s’.
Error: 21744, Severity: 16, Oracle bidirectional publishing requires parameter ‘%s’ to have a value of ‘%s’.
Error: 21745, Severity: 16, Cannot generate a filter view or procedure. Verify that the value specified for the @filter_clause parameter of sp_addarticle can be added to the WHERE clause of a SELECT statement to produce a valid query.
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.