Another Snap shot for publication is running ?

i was doing replication on SQL 7, both my pulisher and subscriber was SQL 7
and the replicatoin was happening without any problem.Then i upgraded it to
SQL 2000 and restore the backup which was taken on SQL7.
After that when i am starting my agent then it is giving thie error "ANOTHER
SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
Please let me know hot to fix this problem as my complete setup is down.
Thanks & Regards
Asif
There are some reports that this was caused by an incomplete application of
a SQL 7 SP.
With this in mind, perhaps the best option is to script out your
publication(s), and subscriber(s), and then drop them, disable replication,
reenable it, and rerun your publication and subscription scripts.
"Asif" <Asif@.discussions.microsoft.com> wrote in message
news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
> i was doing replication on SQL 7, both my pulisher and subscriber was SQL
7
> and the replicatoin was happening without any problem.Then i upgraded it
to
> SQL 2000 and restore the backup which was taken on SQL7.
> After that when i am starting my agent then it is giving thie error
"ANOTHER
> SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
> Please let me know hot to fix this problem as my complete setup is down.
> Thanks & Regards
> Asif
|||Thanks for the reply.
Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
In fact, I eventually was able to reproduce it. The tricky option is on the
Snapshot tab on publication properties - If you check "Do not lock tables
during snapshot generation...", that's when it happened. Without check the
option, you get a normal sp_MSins.
But I still couldn't figure out what exactly this has helped not to block
the table.
Richard
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> There are some reports that this was caused by an incomplete application
of
> a SQL 7 SP.
> With this in mind, perhaps the best option is to script out your
> publication(s), and subscriber(s), and then drop them, disable
replication,[vbcol=seagreen]
> reenable it, and rerun your publication and subscription scripts.
>
> "Asif" <Asif@.discussions.microsoft.com> wrote in message
> news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
SQL
> 7
> to
> "ANOTHER
>
|||It still locks the tables with that box checked. You can see the lock
requests if you watch.
"Richard Ding" wrote:

> Thanks for the reply.
> Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
> In fact, I eventually was able to reproduce it. The tricky option is on the
> Snapshot tab on publication properties - If you check "Do not lock tables
> during snapshot generation...", that's when it happened. Without check the
> option, you get a normal sp_MSins.
> But I still couldn't figure out what exactly this has helped not to block
> the table.
>
> Richard
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> of
> replication,
> SQL
>
>