Can't drop procedure ... Snapshot won't run... Help!

Hi,
I have a server set up for Merge replication. It is the publisher and the
distributer. Has been working fine.
It has two publications.
I wanted the subscribers to get a new copy of the data next time they
replicate, so I went to the first publication, which is stored procs and
view, went to Status tab of the publication properties, and clicked the run
agent now. When it was done, I right clicked on the publication and selected
reinitialize subscriptions.
Then I went to the publication for tables. Right clicked and selected
Re-initialize subscritions. Then I went to the status tab and selected run
agent now. When it came back with a timestamp, red x's appeared on the
replication monitor on the snap shot agents.
The error message it give is :
Cannot drop the procedure 'dbo.sp_sel_B4AC8FE9123F47EDB952DCE5249B4F84_pal'
because it is being used for replication.
As a last resort, I tried to delete the publication, I was going to re do
it. When I try to delete it
it gives me the same error message as above, but with a different sp_sel_
name.
What should I do, or what did I do. I really need it back to working today.
.. .
Any help,
Thanks,
Steve
Well, here is what I did.
I kept trying to delete the publication that I could not get the snapshot
agent to run on, and kept getting the error above. So I delete the stored
proc publication, it went OK. Then I deleted the table publication, and this
time it let me. Then I went to each of the clients, deleted both
subscriptions, and re-created them. Ran fine then, and am able to do manual
pull replications from the subscriber boxes now.
If any one can help me understand what happened, please do. How did I get
in that mess, and what would have been a good way to get out. I was lucky
that I could get to all subscriber boxes and re-create the subscriptions.
Thanks,
Steve
"SteveInBeloit" wrote:

> Hi,
> I have a server set up for Merge replication. It is the publisher and the
> distributer. Has been working fine.
> It has two publications.
> I wanted the subscribers to get a new copy of the data next time they
> replicate, so I went to the first publication, which is stored procs and
> view, went to Status tab of the publication properties, and clicked the run
> agent now. When it was done, I right clicked on the publication and selected
> reinitialize subscriptions.
> Then I went to the publication for tables. Right clicked and selected
> Re-initialize subscritions. Then I went to the status tab and selected run
> agent now. When it came back with a timestamp, red x's appeared on the
> replication monitor on the snap shot agents.
> The error message it give is :
> Cannot drop the procedure 'dbo.sp_sel_B4AC8FE9123F47EDB952DCE5249B4F84_pal'
> because it is being used for replication.
> As a last resort, I tried to delete the publication, I was going to re do
> it. When I try to delete it
> it gives me the same error message as above, but with a different sp_sel_
> name.
> What should I do, or what did I do. I really need it back to working today.
> . .
> Any help,
> Thanks,
> Steve
>
sql

Can't drop a table

I have a table that used to be in a merge replication. How ever it is not
being replicated any more, I can't drop it because it thinks it is been
replicated. How can I drop it?
Thanks a lot, Lina
If you don't replicate anything else from your database run the
sp_removedbreplication procedure. It'll remove all traces of replication.
Then you'll be able to drop the table.
If the first option is not available then you need to reset the replication
status bit in sysobjects for your table. Although you need to know that
manual updating of the sysobjects table is not recommend.
Yury
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:52C9D2D2-61D0-4D7B-9D5A-1950AFA1E8E5@.microsoft.com...
>I have a table that used to be in a merge replication. How ever it is not
> being replicated any more, I can't drop it because it thinks it is been
> replicated. How can I drop it?
> Thanks a lot, Lina
|||issue the following
EXEC sp_configure 'allow',1
go
reconfigure with override
go
use DataBaseName
go
update sysobjects set replinfo = 0 where name = 'TableName'
go
EXEC sp_configure 'allow',0
go
reconfigure with override
go
sp_MSunmarkreplinfo 'TableName'
go
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
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:52C9D2D2-61D0-4D7B-9D5A-1950AFA1E8E5@.microsoft.com...
> I have a table that used to be in a merge replication. How ever it is not
> being replicated any more, I can't drop it because it thinks it is been
> replicated. How can I drop it?
> Thanks a lot, Lina

Can't Disable, getting Server Cannot obtain LOCK

Internet merge replication. Need to detach to move to a new box. Deleted
all the publication, now when I try to disable it as the publisher. I tried
to run sp_removedbreplication 'db_name' and get the same message.
Any thoughts?
Thanks
After lots more reading and searching, I found low memory could cause this.
I added another 512 to the box, and it worked.
"SteveInBeloit" wrote:

> Internet merge replication. Need to detach to move to a new box. Deleted
> all the publication, now when I try to disable it as the publisher. I tried
> to run sp_removedbreplication 'db_name' and get the same message.
> Any thoughts?
> Thanks
|||I would have bounced the server and then tried this - this is abnormal.
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:17E5CBD0-5D2A-444A-97BD-4629B2AE3559@.microsoft.com...[vbcol=seagreen]
> After lots more reading and searching, I found low memory could cause
> this.
> I added another 512 to the box, and it worked.
>
> "SteveInBeloit" wrote:

Can't delete database that has been part of replication

I had a publication (merge) setup for a database. Deleted the publication and tried to delete the database. Sql server says it can't be deleted because it's has replication setup. Bug?

Found the answer. I had to run a stored procedure to get all replication objects removed from my db.

sp_removedbreplication @.dbname = 'dbname', @.type = 'merge'

/Magnus

Can't create Merge Publication

I have been trying for some time to create a Merge publication in SQL Server. I'm running SQL Server 2000 Standard Edition with the latest service pack on a Win2k3 Server. It doesn't seem to matter what replication-enabled database or which table I select
, I always get the same error at the end of the create publication wizard in Enterprise Mgr: "Error 2758 RAISERROR could not locate entry for error 21423 in sysmessages. Object 'pubs' (note: or whatever db I select) does not exist or is not a valid object
for this operation."
Any ideas here?
Corey - possibly this is an incomplete service pack install as some messages
in sysmessages are missing. You could have a look at sqlsp.log file from the
c:\windows directory which might shed some light on any failed actions
during the sp installation. Even if there isn't anything enlightening there
I'd reapply the sp3a.
HTH,
Paul Ibison
|||Thanks, Paul, but so far no luck. I dug through the log and didn't find anything all that revealing. I also re-applied SP3a, but that didn't help either. Still searching...
"Paul Ibison" wrote:

> Corey - possibly this is an incomplete service pack install as some messages
> in sysmessages are missing. You could have a look at sqlsp.log file from the
> c:\windows directory which might shed some light on any failed actions
> during the sp installation. Even if there isn't anything enlightening there
> I'd reapply the sp3a.
> HTH,
> Paul Ibison
>
>
|||Corey,
in htis case you could rebuild the master database or alternatively just add
the missing messages. To do the latter you'll need to create a linked server
to another server that has a complete master database and join to that table
(left outer join) to find the missing messages in sysmessages.
HTH,
Paul Ibison