November 14, 2002 at 12:02 pm
Environment:
SQL 2000 Server - Publisher (local domain)
SQL 2000 Server - Distributor (local domain)
SQL 2000 Server - Subscriber (remote domain)
As much as possible, the client wants the distibutor to offload work to
the distributor.
Directory for the snapshot is on the distributor. We set up the shared
directory and verified that all three servers can read and write to it.
Verified that all three servers have both the SQL and SQL Agent services
running.
Three issues:
1) After creating the initial snapshot without error, the subscriber
failed to load the snapshot. Any idea why?
2) After trying some things to resolve issue #1, we decided to remove
the replication via EM and start over. The following ewrror message was
displayed:
"Could not remove \\Dist-Server\E$\Microsoft SQL
Server\MSSQL\ReplData\unc\Pub-Server_MyDB_MyDB. Check the security
context of xp_cmdshell and close other processes that may be accessing
the directory."
Any idea why??
3) The Publication has been deleted but the orphaned Subcription can't
be removed. A new subscription can't be created since one already
exists. How can I remove the orphan.
Any help or suggestions is appreciated...
TIA
Steve Hendricks
MCSD, MCDBA
AFS Consulting Group
(949) 588-9800 x15
Steve Hendricks
MCSD, MCDBA
Data Matrix
shendricks@afsconsulting.com
(949) 588-9800 x15
November 14, 2002 at 4:07 pm
For #1 (and #2), I'd guess the subscriber didnt have access to the share where the snapshot was created and/or something went wrong with the process, ie it got hung up.
I rarely use merge, will have to look, there are a couple clean up procs you can run.
Andy
November 14, 2002 at 5:49 pm
We generally remove replication and go through setting it up all over again, making sure to get rid of the distribution database. Its a pain. There is somewhere in the distribution tables that when that happens, don't have the correct information for the procs to remove the subscriber. If you open the replication procs, you can find the exact tables involved and whats missing. I tracked it down once a couple years ago, but I also remember that it didn't do me any good to have tracked it down. seems like there was something I didn't know how to populate to make it all right again.
Make sure that everything is perfect before trying it again or you'll be back in the same boat. Much as I hate to say it, I went through it four times in a row once, over network rights which the network admins assurred me were correct, yet failed over and over....
I'm very interested in your solution. May be I won't have to remove and replace anymore.....
Edited by - Scorpion_66 on 11/14/2002 5:53:26 PM
December 6, 2002 at 12:24 pm
I found out that there is a system sproc that can clean things up on either the publisher or the subscriber end of the configuration.
sp_removedbreplication 'DBName'
This resolved my immediate issue... on to the next one!
Steve Hendricks
MCSD, MCDBA
AFS Consulting Group
(949) 588-9800 x15
Steve Hendricks
MCSD, MCDBA
Data Matrix
shendricks@afsconsulting.com
(949) 588-9800 x15
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply