Re: Annon Merge over VPN: WSM Insanity
From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 02/23/05
- Next message: Paul Ibison: "Re: Trans Replication with all types of objects published"
- Previous message: Hilary Cotter: "Re: The process could not create file 'C:\Program Files\Microsoft SQL Server\MSSQL\ReplDat\unc'."
- In reply to: richerwin_at_ubs-europe.org: "Annon Merge over VPN: WSM Insanity"
- Next in thread: richerwin_at_ubs-europe.org: "Re: Annon Merge over VPN: WSM Insanity"
- Reply: richerwin_at_ubs-europe.org: "Re: Annon Merge over VPN: WSM Insanity"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 13:54:45 -0500
answers in line.
-- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com <richerwin@ubs-europe.org> wrote in message news:1109180376.620053.87490@o13g2000cwo.googlegroups.com... > I have my replication "working", though I would like to script as much > of the client installation as possible, and running into mega > headaches. > > Here's the setup: > Client - MSDE > connects to Publisher/Distributor via VPN > annonymous pull subscription > > I can install my MSDE, create the db, logins, etc. > > 1) Through EM, I can create the subscription through wizard. (selecting > "Available to Synch Manager", "Start immediately"). It works. > Syncronization Manager (type in passwords) synch works. I take it you are using SQL Authentication in WSM. If so your user will have to enter the password each time WSM runs. You might want to use intergrated authentication and enter the user account in the pal on the publisher. > > 2) I script the subscription created in 1). Delete subscription and run > script with osql (doesn't run Merge Agent job automatically. Why not? I > even put in an extra line: EXEC sp_start_job @job_name = > 'MERGE_AGENT_JOBNAME'). Go back to EM, right click on subsrciption - > Start Synchronizing. It works. WSM (type in passwords) synch works. The merge agent doesn't start automatically because you have defined it to start on demand. > > 3). Delete subcription and recreate with same script as above. Go > straight to WSM. The subscription is in the list. Synch (type in > passwords). DOES NOT WORK!!! I get the error "the schema script <blah > blah blah> could not be propagated to the subscriber." This means that the subscriber does not have rights to read the snapshot share. You will have to craft a new snapshot share which does not use the administrative share (ie \\servername\c$\Program Files\Microsoft SQL Server\MSSQL\ReplData\UNC). Make sure this new snapshot share has read permission for the accounts or a group which the merge users are in, and that this group or user has rights to read the underlying files and folders. > > Why should I have to run the subscription once through EM before it > will work with WSM? I guess it has something to do with that Merge > Agent job and it needs to be fired off first? This does sound odd. Perhaps it is a rights issue. > > Obviously EM will not be distributed to my end users in far off lands. > I want them to be able to run a script and then synch through WSM. What > is the best way to achieve this? > > Much Thanks >
- Next message: Paul Ibison: "Re: Trans Replication with all types of objects published"
- Previous message: Hilary Cotter: "Re: The process could not create file 'C:\Program Files\Microsoft SQL Server\MSSQL\ReplDat\unc'."
- In reply to: richerwin_at_ubs-europe.org: "Annon Merge over VPN: WSM Insanity"
- Next in thread: richerwin_at_ubs-europe.org: "Re: Annon Merge over VPN: WSM Insanity"
- Reply: richerwin_at_ubs-europe.org: "Re: Annon Merge over VPN: WSM Insanity"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading