SQL Server Errors or Failures from Error: 20029 to Error: 20050

SQLServerF1

 

Error: 20029, Severity: 16, The Distributor has not been installed correctly. Could not disable database for publishing.
Error: 20030, Severity: 16, The article ‘%s’ already exists on another publication with a different column tracking option.
Error: 20031, Severity: 16, Could not delete the row because it does not exist.
Error: 20032, Severity: 16, ‘%s’ is not defined as a Subscriber for ‘%s’.
Error: 20033, Severity: 16, Invalid publication type.
Error: 20034, Severity: 16, Publication ‘%s’ does not support ‘%s’ subscriptions.

Error: 20036, Severity: 16, The Distributor has not been installed correctly.
Error: 20037, Severity: 16, The article ‘%s’ already exists in another publication with a different article resolver.
Error: 20038, Severity: 16, The article filter could not be added to the article ‘%s’ in the publication ‘%s’.
Error: 20039, Severity: 16, The article filter could not be dropped from the article ‘%s’ in the publication ‘%s’.

Error: 20040, Severity: 16, Could not drop the article(s) from the publication ‘%s’.
Error: 20041, Severity: 16, Transaction rolled back. Could not execute trigger. Retry your transaction.
Error: 20043, Severity: 16, Could not change the article ‘%s’ because the publication has already been activated.
Error: 20044, Severity: 16, The priority property is invalid for local subscribers.
Error: 20045, Severity: 16, You must supply an article name.
Error: 20046, Severity: 16, The article does not exist.
Error: 20047, Severity: 16, You are not authorized to perform this operation.
Error: 20048, Severity: 16, To modify the priority of a subscription, run sp_changemergesubscription at the Publisher instead of using sp_changemergepullsubscription at subscriber. This is for backward compatibility only.
Error: 20049, Severity: 16, The priority value should not be larger than 100.0.
Error: 20050, Severity: 16, The retention period must be greater than or equal to 0, and it must not extend past December 31, 9999.

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 *