I have also encountered the same error as you.
Since I am not the author of the the replication procedure (but I need
to fix the problem), I am not sure which stored procedure should I drop
from the db and identify and retain the ones made by the snapshot agent.

Thanks.

Hello Jana

This is the script i used for the sp cleanup...

declare @pubid uniqueidentifier
declare @pubidstr varchar(16)
declare @pubname varchar(50)

set @pubname = '????' -- type the name of the publication that's causing
the problem

select @pubid = pubid from sysmergepublications where name = @pubname

exec dbo.sp_MSguidtostr @pubid, @pubidstr out

create table #tempSP(sp sysname)
insert into #tempSP(sp)
select ins_conflict_proc as sp from sysmergearticles where ins_conflict_proc
is not null
union all
select insert_proc as sp from sysmergearticles where insert_proc is not null
union all
select update_proc as sp from sysmergearticles where update_proc is not null
union all
select select_proc as sp from sysmergearticles where select_proc is not null
union all
select view_sel_proc as sp from sysmergearticles where view_sel_proc is not
null

select identity(int,1,1) as temp_id, name
into #tempNames
from sysobjects
where type = 'P'
and name not in (select sp from #tempSP)
and name not like 'dt_%'
and name like '%' + @pubidstr
and status < 0
order by name

declare @total int, @i int
declare @tmp_procname nvarchar(260)

select @total = count(*) from #tempNames
set @i = 1

while @i <= @total
begin
select @tmp_procname = name
from #tempNames
where temp_id = @i

print ('drop proc ' + @tmp_procname) --exec
set @i = @i + 1
end

drop table #tempSP
drop table #tempNames

I chose to print the drop commands because they were a lot, I copied the
text from the messages tab of query analizer, paste it into a new query, and
run as many lines as i wanted to, but if you want to save your energy just
replace the "print" command for an "exec".

Regards...


[quoted text, click to view]