The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.
How can I solve this problem?
Thanks.the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.
|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||How can i track it?
|||I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.
I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.
|||Do you know who is that writes in sysmergearticles?|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'
The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?
I think that it is so but...
For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170
and
The process could not deliver the snapshot to the Subscriber. -2147201001.
|||I drop all subscriptions of this publication. I drop my publication that give me error.
I do a new publication. I do my subscriptions with no initializate schema and data.
Now all go well.
No comments:
Post a Comment