October 15, 2008 at 10:32 am
First, I suspect my problem is lack of experience with replication. I have never set this up before.
Here is my scenario:
1. My publisher and distributor is a SQL Server 2000 SP4 instance on a Windows 2003 Server.
2. My subscriber will be a SQL Server 2005 SP1 instance on a different Windows 2003 Server.
3. I set the snapshot folder to be a file share.
4. I checked the Publication Access List and it by default added in all logins with the sysadmin role, which according Books Online is the expected behavior. I picked one of those logins, gave it the db_owner role on the database I want to publish articles from. This account is a windows account.
5. I gave that windows account that is both a sysadmin and a db_owner on the publication database, full control on the file share.
Is there anything I am misunderstanding or have done incorrectly. The error message I get is quite simple:
"The process could not create file '\\myFileShare\replsnap\unc'"
I noticed in the Replication Monitor that the Log Reader Agent is running and has been for over 45 minutes now. I have no idea what that is or what it is doing. Does that need to finish before the Snapshot Agent can run to create the first snapshot?
I want to create an initial snapshot and then every 24 hours, use a pull subscription on the subscriber to update all of the articles.
I greatly appreciate any help anyone can provide.
October 16, 2008 at 10:32 am
I got it working. Disregard above post.
The problem was actually DNS. I was using a file share but for some reason DNS wasn't resolving for the server the file share is on. I substituted the name for the ip address (which is static anyway) and all is good. The error message doesn't reflect the problem, which always makes debugging these things a lot more fun.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy