why does this error happen?"42000 The row was not found at the Subscriber when applying the replicated command.20598"

All Replies

• Friday, December 28, 2012 1:31 PM

  Moderator

   

   
  

  1
  You will get this error for several reasons - the most likely one is because you did a no-sync subscription, or someone has deleted data from the subscription database. If you get many of these error messages you are best to reinitialize your subscription, or use the continue on data consistency error profile.
  

  ---

  looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Marked As Answer by Allen Li - MSFTModerator Friday, January 04, 2013 2:23 AM
  •  
  • Reply
  • Quote

   
• Tuesday, January 01, 2013 2:54 PM

   

   
  

  0

  Hi Archer,

  Last week I was also faced the same issue as per our requirement, changed those articles properties like "do not replicate INSERT/UPDATE/DELETE".

  Shrinking database will not effect replication, as far my knowledge becoz shrinking will delete the free space.

  Please refer the following links for knowing root casue of deletions, might be helpful

  http://sameproblemmorecode.blogspot.in/2011/02/row-was-not-found-at-subscriber-when.html

  http://sqlserverreplicationtroubleshooting.blogspot.in/2011/04/how-to-fix-missing-rows-error.html

  http://www.sqlservergeeks.com/articles/sql-server-bi/97/somebody-has-manually-performed-a-dml-operation-on-the-subscriber-what-to-do-next

  Thanks,

  ---

  Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

  • Reply
  • Quote