Row not found at Subscriber

This is a srange error because I found the row its looking
for at the subscriber..
The row was not found at the Subscriber when applying the
replicated command.
Any ideas? This one is a big one.
niv
Niv,
please can you post up the full error message, and explain what type of
replication you are using.
If it is transactional, the row being looked for will be based on OK, while
if merge it'll be based on guid.
If it is transactional, use sp_browsereplcmds to get the command and try to
run it yourself in QA if it is an update and let's see what tat returns.
HTH,
Paul Ibison
|||Enable replication logging as outlined in the kb article. It will tell you exactly which row it is failing on.
http://support.microsoft.com/default...&Product=sql2k
Then you can either select the agent profile to continue on data consistency errors or you can manually fill in the data by hand.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" wrote:

> Niv,
> please can you post up the full error message, and explain what type of
> replication you are using.
> If it is transactional, the row being looked for will be based on OK, while
> if merge it'll be based on guid.
> If it is transactional, use sp_browsereplcmds to get the command and try to
> run it yourself in QA if it is an update and let's see what tat returns.
> HTH,
> Paul Ibison
>
>
|||Sorry for typo - should be PK not OK.
Further trhinking - I suspect that you don't have updatable subscribers and
someone has removed the row. If this is the case then you can readd the row
or skip the error, as Hilary points out.
Regards,
Paul Ibison
|||The strange this is, I searched for the row that could not
be found by the replication agent and found it.
This is why I dont understand why the agent seems to think
the row does not exist.
niv
>--Original Message--
>Enable replication logging as outlined in the kb article.
It will tell you exactly which row it is failing on.
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;312292&Product=sql2k
>Then you can either select the agent profile to continue
on data consistency errors or you can manually fill in the
data by hand.[vbcol=seagreen]
>--
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>
>"Paul Ibison" wrote:
explain what type of[vbcol=seagreen]
be based on OK, while[vbcol=seagreen]
the command and try to[vbcol=seagreen]
what tat returns.
>.
>
|||Niv,
can you try my original suggestion - get hold of the error
causing command and run it yourself in QA. This statement
should call an update stored procedure and the SP will
refer to the row by PK value. Investigating this way
should point out what the issue is.
Regards,
Paul Ibison
sql