The schema script 'snapshot.pre' could not be propagated to the subscriber.
-
I've always known you can do it, but now I get to learn how to make it do it.
I'm trying to do merge replication between 2 servers. "Yoda" is my publisher. "Traveler" is my subscriber. Both are 32bit machines running 2005 on Windows XP Pro. I figure on using "Pull" subscriptions.
Distributor on server Yoda:
yoda will act as its own distributor
snapshot folder is \\yoda\sql snapshots,
This is a shared folder on yoda.
Distribution database name: distribution
Folder for the database file: e:\program files\microsoft SQL server\..
Folder for database log: e:\program files\microsoft SQL server\...
The wizard finishes with 2 green check boxes.
Publisher on server Yoda:
Picked the database V60.
Merge Publication.
SQL Server 2005
Tables, Stored Procedures, Views, User Defined Functions.
No filters.
Create snapshot immediately and schedule snapshots.
Security Settings
Process Account yodaumbskull (and password)
Connect to the publisher using SQL login. (user and password)
Publication Name: Publish V60
Wizard finishes with 3 green checks.
I watch the Snapshot Agent Status and see it go to 100%.
Still watching the snapshot agent status. Ah, now it's 100% finished.
I now have lots of files under
C:\SQL Snapshots\unc\YODA_V60_PUBLISH V60\20070927163359
So, now I turn my attention to Traveler:
I created a database called W60 for no good reason.
New Subscription Wizard
Picked Publish V60 on Yoda
Run each agent at its subscriber
Subscriber Traveler, subscription database W60
Subscriber Security
Run under SQL Services Agent Account
By impersonating process account
By impersonating process account
On demand only
Initialize immediately
Subscription Type: Client
Wizard finished with 2 green checkmarks
Under Job Activity Monitor, it says the job Yoda-V60-Publish.... errored.
Yoda's replication monitor says it's not initialized.
I'm expecting to see it build the tables, views, stored procedures, function and insert the data...
Where am I going astray?
Willing to hire or kidnap somebody in the Chicago area to help me learn to do this.:hehe:
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font] -
you must ensure that the Subscriber SQL Agent Account has the necessary permissions on the Yoda Shared drive.
* Noel -
Hmm. Thought it might be a permissions thing.
Perhaps I should:
1. Create an account on Traveler.
2. Make sure while logged into that I can access the files in Yoda's snapshot folder.
3. Change the subscriber security to:
Run under the following windows account
Traveler\SomeLogin
(the password)
By impersonating process account
By impersonating process account
Hmm. That doesn't seem to have helped.....
There's got to be a way to get an error message a little more detailed than "You screwed this up." Wasn't I once seeing errors like "Error 5" or unable to open bla bla bla snapshot.pre?:crying:
(Usually I just make the programs and let someone else deal with logins and suchlike.)
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply