April 7, 2010 at 8:37 am
Hello,
We are also running in to the same issue. We are moving our production merge replication database to a new test environment which is still on our production domain (to allow outside consultants access to the server to help). We need a different name than the production server. So we restored the databases (master, msdb, and the replicated DB) to the new box. Run @@servername and see the old server. Set to single user mode by adding -m to the command line for SQL svc and restored the master, back to multi mode, restore msdb, and the main db. When we restored we selected the option to preserve replication. Used the following TSQL:
Use _insert dbname_
Exec sp_removedbreplication '_dbname_'
GO
Use master
Exec sp_dropdistpublisher '_old servername_'
Exec sp_dropdistributiondb 'distribution'
Exec sp_dropdistributor
GO
Next we change the name of the server in the master db
USE MASTER
EXEC SP_DROPSERVER 'OLD SERVER NAME', 'DROPLOGINS'
GO
EXEC SP_ADDSERVER 'NEW SERVER NAME','LOCAL'
GO
If you run "select @@servername you should get your new server name
Next we generate scripts from the old server for the publisher to create the new publisher on the new server. We had to modify some of the entries; job_frequency for example was set to 0 when it needed to be at least 1 to create the job.
My problem now is that I am unable to get the initial snapshot to finish creating. We have a user in the agent that has permissions but when I look at the status it is waiting to prepare the merge process.
April 7, 2010 at 12:17 pm
My problem now is that I am unable to get the initial snapshot to finish creating. We have a user in the agent that has permissions but when I look at the status it is waiting to prepare the merge process.
>> So, you are finding that the snapshot is not getting created at all? did you check the folder under your \\repldata share? If the issue is suspected due to the job owner not having permission, then logon to the distributor box with an admin (or some powerful) user and start snapshot.exe from \90\COM folder from command prompt with the same parameter.
If the snapshot completes successfully fromthis command line, then the issue is definitely with the job owner not having enough rights to run other EXEs. Then you will need to think of configuring proxies or using a job owner with admin rights.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply