(Source: MSSQLServer, Error number: 20598)

Question

(Source: MSSQLServer, Error number: 20598)

johnebonin

SSC Veteran

Points: 270
More actions
August 28, 2008 at 6:03 pm

#211907

Hello i am having and issue with replication i am receiving the following
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/20598
I 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 the issue.
Any help would be great.
Thanks

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

john_jakob Mr or Mrs. 500 Points: 587 More actions · Answer 1

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

johnebonin SSC Veteran Points: 270 More actions · Answer 2

johnebonin

SSC Veteran

Points: 270

September 2, 2008 at 1:22 pm

#866165

Thanks That has seem to resolve the issue.

john_jakob Mr or Mrs. 500 Points: 587 More actions · Answer 3

john_jakob

Mr or Mrs. 500

Points: 587

September 3, 2008 at 8:31 am

#866510

Cool. Glad it helped.

Abhilash Melethil Old Hand Points: 303 More actions · Answer 4

Abhilash Melethil

Old Hand

Points: 303

August 26, 2010 at 12:17 am

#1212085

Thanks a ton for the solution!

Kendal Van Dyke SSCertifiable Points: 5972 More actions · Answer 5

john_jakob (8/29/2008)
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

There's a much more precise way to solve this. If you don't care about data consistency at the subscriber then simply change the distribution agent profile to ignore data consistency errors, restart the agent, and move on.

If you want to know the command that's failing then start by looking at the error in Replication Monitor or by executing sp_helpsubscriptionerrors (in the distribution database on the distributor). Syntax, including required parameters, can be found here: http://technet.microsoft.com/en-us/library/ms173427.aspx... that'll get you the xact_seqno and command_id.

You also need the publisher database id which you can get by runing this query on the distributor (substitute values in quotes for your situation):

SELECT DISTINCT

subscriptions.publisher_database_id

FROM sys.servers AS [publishers]

INNER JOIN distribution.dbo.MSpublications AS [publications] ON publishers.server_id = publications.publisher_id

INNER JOIN distribution.dbo.MSarticles AS [articles] ON publications.publication_id = articles.publication_id

INNER JOIN distribution.dbo.MSsubscriptions AS [subscriptions] ON articles.article_id = subscriptions.article_id

AND articles.publication_id = subscriptions.publication_id

AND articles.publisher_db = subscriptions.publisher_db

AND articles.publisher_id = subscriptions.publisher_id

INNER JOIN sys.servers AS [subscribers] ON subscriptions.subscriber_id = subscribers.server_id

WHERE publishers.name = 'MyPublisher'

AND publications.publication = 'MyPublication'

AND subscribers.name = 'MySubscriber'

Now plug the xact_seqno, xact_seqno, and publisher_database_id into this query (again substituting the values with the ones you've gotten from the queries above):

EXECUTE distribution.dbo.sp_browsereplcmds

@xact_seqno_start = '0x0000001900001926000800000000',

@xact_seqno_end = '0x0000001900001926000800000000',

@publisher_database_id = 29,

@command_id = 1

Once you know what command is failing you can figure out what you need to change at the subscriber for replication to get past the error.

Kendal Van Dyke
http://kendalvandyke.blogspot.com/[/url]