March 19, 2003 at 2:48 pm
I am troubleshooting replication issue which after few minutes we get error 20598
I look at sp_MSupd_tblname procedure, which says
if @@microsoftversion>0x07320000
exec sp_MSreplraiserror 20598
Our value 1s 134218488
Can somebody tell me what is the meaning?
of @@microsoftversion>0x07320000 is ?
What is it verifying
March 20, 2003 at 3:04 am
To be honest I don't know exactly what your problem is because I can't find either the error number 20598 nor the stored procedure you name. Which version are you running? What type of replication?
Anyway the message seems to point in the direction of a version mismatch. This can happen if you have a higher version or SP on the subscriber than you have on the publisher. In that case the initial snapshot will fail.
Hope this helps
M
[font="Verdana"]Markus Bohse[/font]
March 20, 2003 at 7:37 am
It isn't about the version of the sp. It is in every replication store procedure. Usually the error number 20598 fires when no rows are affected by the insert, delete or update. This can be for example because the update stored procedure coudn't find the row to be updated. If you can, post the rror message too.
March 20, 2003 at 1:21 pm
Thanks for help and comments I have rec
The error message is "The row was not found at the Subscriber when applying the replicated command"
I can find the record in replicated table and values seems to be correct.
I am going to use Xcall instead of Mcall to see if makes any diff, any pointer?
March 21, 2003 at 9:18 am
If you have the row that needs to be updated then maybe you should check the code of the stored procedure. Check that is has the correct number of variables (@c1, @c3, @c4, etc) and that the pkeys are also correct (@pkc1, etc). If everything is correct inside the sp, run it manually and pass as many variables as it is needed. You can find a call to the sp in the error message with EM.
But double check that the record that needs to be updated really exists, because that is problably the error.
May 17, 2007 at 1:08 pm
Have you checked the table relationships to make sure that they are not set to be enforced for replication on both publisher and subscriber? Other setings that can cause this error to come up:
February 5, 2008 at 12:10 pm
here's a link to for this issue from microsoft..
http://technet.microsoft.com/en-us/library/ms151174.aspx
I had the same issue..but since my server was the test svr..what i did was set the parameter
-skiperrors 20598 for the distribution agent
September 10, 2010 at 2:04 pm
Hi All,
Please help me out as i am also getting the same error quite frequently and when i reinitialize it's working fine for one or two days and again i am getting the same issue repeadly.
i am posting the error message here.:
Command attempted:
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x0000059A00009B4D005000000000, Command ID: 101)
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
The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)
Get help: http://help/20598
Please help me out from this as it is a very important to resolve for me in no time.
Regards,
August 29, 2011 at 11:55 pm
mismatch of columns the columns in publication wont be available in subscription
"Use Distribution
sp_helpsubscriptionerrors @publisher='ramcobl352',@publisher_db='AVNAPPDB_NEW',@publication='AVN_PUB',@subscriber='ramcobl353',
@subscriber_db='AVNAPPDB_NEW' THE XACT_SEQNO PUT IT IN AT SUSCRIBER DB use avnappdb_new sp_setsubscriptionxactseqno @publisher = 'ramcobl352'
, @publisher_db = 'AVNAPPDB_NEW'
, @publication = 'AVN_PUB'
, @xact_seqno = 0x0004CCCB00009551000C00000000 "
run this will solve the problem
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply