Replication Error - The row was not found at Subscriber... 1

[Catadmin]

Came across an unusual one and I'm not sure how to interpret the error. Tried Googling it and it only made me more confused. Has anyone run across this one before?

Distributor Agent fails with multiple articles in one publication. Error history reads as:

[b]LastCommand:[/b] {CALL sp_MSupd_GroupInfo (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,2005-03-18 00:00:00.000,2005-04-17 00:00:00.000,2005-03-18 00:00:00,NULL,NULL,'A01',0,NULL,NULL,NULL,NULL,695,0x00007002)} 
Transaction sequence number and command ID of last execution batch are 0x00000FDA000000BC000400000000 and 1.

[b]Error Details:[/b] The row was not found at the Subscriber when applying the replicated command.
(Source: CONSTRUCTACON2\WEBENREPORTS (Data source); Error number: 20598)

[b]Error Message:[/b] Error at parameter 196 during datastream processing of parameterized command.

The posts I've read have mentioned something about deleted values or duplicate records or something. I'm trying to verify what could cause this error. I know what table I need to look into - GroupInfo. I just need to figure out what it is I'm looking for.

BTW, GroupInfo has a column filter and a row filter on it. The row filter has "SELECT <published_columns> FROM <<TABLE>> WHERE id in
(select group_ID from participant where customer_ID = 1)".

The Participant table is also being replicated in this publication. It also has row and column filters on it. The row filter for it is: "SELECT <published_columns> FROM <<TABLE>> WHERE
customer_ID = 1 and TransactionDate >= '01/01/2005'".


Any thoughts?

Thanks!



Catadmin - MCDBA, MCSA
Beware the error of pre-emptive poultry inventory!

 

[clapag22]

This usually occurs during transactional replication when the Primary Key value of the row being updated does not exist in the subscriber. So the upd SP can't find anything to update.

 

[Catadmin]

Aha. Well that makes sense. Especially as the replicated tables don't contain the same row counts as my views (pulling on the replicated tables horizontal filters) do.

Truncating the tables, re-initializing the subscriptions and re-starting the agents did the trick. I've watched the DB all day and it looks like the pull subscription ran without problem this time around.

Thank you very much for your assistance.



Catadmin - MCDBA, MCSA
Beware the error of pre-emptive poultry inventory!