Invisible Replications

Derek,
can you run sp_removedbreplication in the previously
published databases.
If this doesn't remove the rogue red x's in replication
monitor, try restarting the sql server service - when I
have investigated this before, there is a reference to a
temp table in tempdb, so restarting removed both the
table and the red icon.
Apparently sp_MSload_replication_status may clear this
error as well.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
removedbreplication didn't work. It appears the "new" "Database A" has no
knowledge of the replications. I'm not sure where replication monitor is
getting it's information from, but that is what needs clearing out.
sp_MSload_replication_status also didn't seem to help.
I can get the database rebooted over the weekend, but is there anything else
I can try or any reading I can do to help investigate.
Thanks
Derek
"Paul Ibison" wrote:

> Derek,
> can you run sp_removedbreplication in the previously
> published databases.
> If this doesn't remove the rogue red x's in replication
> monitor, try restarting the sql server service - when I
> have investigated this before, there is a reference to a
> temp table in tempdb, so restarting removed both the
> table and the red icon.
> Apparently sp_MSload_replication_status may clear this
> error as well.
> HTH,
> Paul Ibison
> (The ONLY sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>