Specify all articles when subscribing to a publication using concurrent snapshot processing.

Chris Skorlinski [MSFT] Troubleshooting April 4, 2012

I recently encountered this error when setting up Transactional Replication via SQL scripts. Msg 14100, Level 16, State 1, Procedure sp_MSrepl_addsubscription, Line 533 Specify all articles when subscribing to a publication using concurrent snapshot processing. Looking at my create Publication script I see the default @sync_method = N’concurrent’ being set in sp_addpublication. Nothing I want
Read More »

SQL Replication Agent will RETRY for 4085 Years

Chris Skorlinski [MSFT] ReplTalk Blog August 25, 2010

Have you noticed the SQL Server Agent Job RETRY is set to 2147? Well it is not, the dialog window just cuts off the rest of the digits. Actually the Replication Agent are set by default to retry 2147483647 times, once every minute. That is over 4000 years! 2147483647 = 35791394 Hours = 1491308 Days
Read More »

ReplTip – Publishing 1 Article into 2 Publications bloats Distribution DB

Chris Skorlinski [MSFT] Troubleshooting November 24, 2015

Chris Skorlinski – Microsoft SQL Server Escalation Services While visiting a customer site, we discussed consequences of publishing common article\tables into multiple Publications. For this customer, each Publication contains same set of core or common tables used by all subscribers, but then some subscribers had tables unique to just that subscriber. For example, all Publications
Read More »

Replication Agent fails with “An error occurred during decryption.”

ReplTalk Troubleshooting March 2, 2011

While helping a customer on a Replication issue, we encountered an very unusual error message. An error occurred during decryption. There is no remote user 'distributor_admin' mapped to local user '(null)' from the remote server 'repl_distributor'. Changed database context to 'master'. (Microsoft SQL Server, Error: 15466) There are some key words in this error (‘distributor_admin’,
Read More »

Reinitialization MS SQL Replication Subscirber may cause data loss

Chris Skorlinski [MSFT] Troubleshooting February 23, 2010

In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber. In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »