SQL Server Errors or Failures from Error: 21049 to Error: 21073

 

Error: 21049, Severity: 16, The login ‘%s’ does not have access permission on publication ‘%s’ because it is not in the publication access list.
Error: 21050, Severity: 16, Only members of the sysadmin fixed server role or db_owner fixed database role can perform this operation. Contact an administrator with sufficient permissions to perform this operation.
Error: 21051, Severity: 16, Could not subscribe because non-SQL Server Subscriber ‘%s’ does not support custom stored procedures.
Error: 21052, Severity: 16, Cannot write to the message queue for the queued updating subscription. Ensure that Microsoft Distributed Transaction Coordinator is running, and that the subscription is active and initialized. If the subscription uses Microsoft Message Queueing, ensure

Error: 21053, Severity: 16, Input property parameter is not valid. See SQL Server Books Online for a list of valid parameters for sp_changemergepublication.
Error: 21054, Severity: 16, The trigger at the Subscriber could not execute commands at the Publisher over the linked server connection (triggers are used for Subscribers with updating subscriptions). Ensure sp_link_publication has been used to configure the linked server properly,
Error: 21055, Severity: 15, Invalid value for parameter %s specified for %s.
Error: 21056, Severity: 16, The subscription to publication ‘%s’ has expired or does not exist.
Error: 21057, Severity: 16, Anonymous Subscribers cannot have updatable subscriptions.

Error: 21058, Severity: 16, An updatable subscription to publication ‘%s’ on Subscriber ‘%s’ already exists.
Error: 21059, Severity: 16, Cannot reinitialize subscriptions of non-immediate_sync publications.
Error: 21060, Severity: 16, Could not subscribe because non-SQL Server Subscriber ‘%s’ does not support parameterized statements.
Error: 21061, Severity: 16, Invalid article status %d specified when adding article ‘%s’.
Error: 21062, Severity: 16, The row size of table ‘%s’ exceeds the replication limit of 6,000 bytes.
Error: 21063, Severity: 16, Table ‘%s’ cannot participate in updatable subscriptions because it is published for merge replication.
Error: 21064, Severity: 16, The subscription is uninitialized or unavailable for immediate updating as it is marked for reinitialization. If using queued failover option, run Queue Reader Agent for subscription initialization. Try again after the (re)initialization completes.
Error: 21070, Severity: 16, This subscription does not support automatic reinitialization (subscribed with the ‘no sync’ option). To reinitialize this subscription, you must drop and re-create the subscription.
Error: 21071, Severity: 10, Cannot reinitialize article ‘%s’ in subscription ‘%s:%s’ to publication ‘%s’ (subscribed with the ‘no sync’ option).
Error: 21072, Severity: 16, The subscription has not been synchronized within the maximum retention period or it has been dropped at the Publisher. You must reinitialize the subscription to receive data.
Error: 21073, Severity: 16, The publication specified does not exist.

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.