Missing Replication Stored procedure

We have had many SQL Server merge replications up and running for several
years now. Then we started having an major issue where information started
disappearing from the database.
We found the data still there but it was all in the conflict viewer. The
error that was given was "The row was updated at '(name of the 1st
subscriber)' but could not be updated at '(name of the 1st subscriber)'.
Could not find stored procedure 'ap_upd_E62019530D9D42907AC976C5A3134364'.
we recreated the subscriptions thinking that would be the end of it but a
few days later we had the same issue but with a different stored procedure
name.
The stored procedure that says is missing at the subscriber is always there
on the publisher. Also, the number of these "ap_" procedures seems to be
growing and sometimes is goes to "bp_". Meaning that in one database we now
have "sp_upd_E62019530D9D42907AC976C5A3134364",
"ap_upd_E62019530D9D42907AC976C5A3134364", and
"bp_upd_E62019530D9D42907AC976C5A3134364" and all of these stored procedures
are identical in there SQL
Does anybody have any knowledge of this issue or know where to look? This
problem is starting to accelerate and we are having real trouble finding a
solution
I've run into this problem myself. I ran into it when I deployed waves of
filtered subscriptions. You can grab the procs from the publisher and script
them out and put them in place on the subscriber. The problem is next
subscriber you deploy you might encounter this problem again.
I did raise a support incident with Microsoft on this one, but its over 3
years old now. The engineer was a Rand Boyd if that helps you to track it
down. I don't believe it was solved by a service pack as we were unable to
reproduce it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ken Hundley" <KenHundley@.discussions.microsoft.com> wrote in message
news:D5F05DF7-3449-4D8C-B8BA-531132792723@.microsoft.com...
> We have had many SQL Server merge replications up and running for several
> years now. Then we started having an major issue where information
> started
> disappearing from the database.
> We found the data still there but it was all in the conflict viewer. The
> error that was given was "The row was updated at '(name of the 1st
> subscriber)' but could not be updated at '(name of the 1st subscriber)'.
> Could not find stored procedure 'ap_upd_E62019530D9D42907AC976C5A3134364'.
> we recreated the subscriptions thinking that would be the end of it but a
> few days later we had the same issue but with a different stored procedure
> name.
> The stored procedure that says is missing at the subscriber is always
> there
> on the publisher. Also, the number of these "ap_" procedures seems to be
> growing and sometimes is goes to "bp_". Meaning that in one database we
> now
> have "sp_upd_E62019530D9D42907AC976C5A3134364",
> "ap_upd_E62019530D9D42907AC976C5A3134364", and
> "bp_upd_E62019530D9D42907AC976C5A3134364" and all of these stored
> procedures
> are identical in there SQL
> Does anybody have any knowledge of this issue or know where to look? This
> problem is starting to accelerate and we are having real trouble finding a
> solution
|||That is what I have done...
I re-created all the missing sp on the subscriber computer, but after
several days there seems to be more that appear.
Maybe I will just open a ticket with MS and see if they can figure out what
is happening.
Thanks
"Hilary Cotter" wrote:

> I've run into this problem myself. I ran into it when I deployed waves of
> filtered subscriptions. You can grab the procs from the publisher and script
> them out and put them in place on the subscriber. The problem is next
> subscriber you deploy you might encounter this problem again.
> I did raise a support incident with Microsoft on this one, but its over 3
> years old now. The engineer was a Rand Boyd if that helps you to track it
> down. I don't believe it was solved by a service pack as we were unable to
> reproduce it.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Ken Hundley" <KenHundley@.discussions.microsoft.com> wrote in message
> news:D5F05DF7-3449-4D8C-B8BA-531132792723@.microsoft.com...
>
>