Error Number 20598
Contents |
360 games PC games error number 20598 replication Windows games Windows phone games Entertainment All Entertainment
Transactional Replication Error 20598
Movies & TV Music Business & Education Business Students & educators the row was not found at the subscriber when applying the replicated command. the step failed Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet instruct the distribution agent to skip this error Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Exec Sp_browsereplcmds
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Related Tips: More > Replication Problem From time to time you may see replication error 20598 for DELETEs. This a pain to fix manually instruct the distribution agent to skip this error and continue to replicate the rest of the changes and we often do not want to resort to having to redo sql server 20598 the snapshot or skip the error. In this tip I show how you can deal with this error. Solution
Sql Server Replication Skip Error
In transactional replication, error 20598 is due to a missing row on the subscriber and there are two scenarios that can cause this error: An UPDATE command cannot be replicated, https://support.microsoft.com/en-us/kb/3066750 because there is no record that matches the update condition on the subscriber. A DELETE command cannot be replicated, because there is no record that matches the delete condition on the subscriber. I have addressed the UPDATE scenario in part 1. In this tip, I will address the delete scenario. The traditional way to fix this error for a DELETE is similar https://www.mssqltips.com/sqlservertip/3366/auto-fix-sql-server-transactional-replication-error-20598-for-deletes/ to what I discussed in part 1, so I will bypass the common steps and only mention the steps unique to the delete scenario. There are actually two ways to fix this issue: On the subscriber, insert a dummy record with the exact primary key value of the deleted row. This PK value can be retrieved using sp_browsereplcmds. The other option is to modify the sp_MSDel_
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server http://www.sqlservercentral.com/Forums/Topic560915-291-1.aspx 2005 » SS2K5 Replication » (Source: MSSQLServer, Error number: 20598) (Source: MSSQLServer, Error number: 20598) Rate Topic Display Mode Topic Options Author Message johneboninjohnebonin Posted Thursday, August 28, 2008 6:03 PM Forum Newbie Group: General Forum Members Last Login: Saturday, September 14, 2013 7:42 AM Points: 4, Visits: 102 Hello i am having and issue with replication i am receiving the following error number Command attempted:if @@trancount > 0 rollback tran(Transaction sequence number: 0x000004850000013C000600000000, Command ID: 1)Error messages:The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)Get help: http://help/20598I have tried applying 953752 Cumulative update package 9 for SQL Server 2005 Service Pack 2 to resolve this issue but so far to date this has not resolved error number 20598 the issue.Any help would be great.Thanks Post #560915 john_jakobjohn_jakob Posted Friday, August 29, 2008 3:44 PM Grasshopper Group: General Forum Members Last Login: Thursday, February 21, 2013 11:46 AM Points: 19, Visits: 100 I ran into this problem several times with SQL 2000 replication -- 2005 might be similar. First try deleting all rows in the table in question at the subscriber, and start the replication going again--see if that works.If that doesn't work, you might have to reinitialize the publication from scratch. Not a pleasant thing from anyone's perspective.- j Post #561553 johneboninjohnebonin Posted Tuesday, September 2, 2008 1:22 PM Forum Newbie Group: General Forum Members Last Login: Saturday, September 14, 2013 7:42 AM Points: 4, Visits: 102 Thanks That has seem to resolve the issue. Post #562613 john_jakobjohn_jakob Posted Wednesday, September 3, 2008 8:31 AM Grasshopper Group: General Forum Members Last Login: Thursday, February 21, 2013 11:46 AM Points: 19, Visits: 100 Cool. Glad it helped. Post #563037 Abhilash MelethilAbhilash Melethil Posted Thursday, August 26, 2010 12:17 AM Grasshopper Group: General Forum Members Last Login: Tuesday, August 18, 2015 6:09 P