David,
can you have a look at the list of processes and see if
the snapshot.exe is listed, then kill it if it is.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
No - definitely no snapshot.exe.
"Paul Ibison" wrote:
> David,
> can you have a look at the list of processes and see if
> the snapshot.exe is listed, then kill it if it is.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||David,
have a look at sp_removedbreplication, which should
remove any lingering system table traces. Have a look for
any orphaned jobs which are running the snapshot agent.
Also, consider restarting the sql server service.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||An update on this issue:
I disabled replication and distribution on the publisher and distributor
(respectivley) started again.
I was able to start the snapshot agent.
I then received a different error from the snapshot agent:
Invalid object name: syspublications.
Still stuck on this error though.
"Paul Ibison" wrote:
> David,
> have a look at sp_removedbreplication, which should
> remove any lingering system table traces. Have a look for
> any orphaned jobs which are running the snapshot agent.
> Also, consider restarting the sql server service.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment