Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-05-14 : 10:45:01
|
| Travis writes "Well, I did my homework... and I am still having troubles. I am trying to test out replication to see if it will do what I am needing (and to just get some experience with it).Here is the scenario...SQL-PROD: SQL Server 2000 Enterprise Ed, outside of org domainSQL-DEV: SQL Server 2000 Personal Ed (MSDE?), inside org domain(both are Win2K)SQL-PROD = Distributor & PublisherSQL-DEV = SubscriberI can go through the Replication wizard, and setup the Subscription on SQL-DEV (I am trying SnapShot based right now), and its set to a manual subscription.If I try to "Start Synchronizing", I end up seeing the following..."The process could not read file '\\sql-prod\e$\Working\TJ's\REPLICATION\unc\SQL-PROD_STAGING_STAGING-TJS_TEST\20030509145002\TMP_TJ_REPL_TEST_TBL_1.sch' due to OS error 5."...with the additional information of, "Access is denied."Now, I came across the following here...http://www.databasejournal.com/features/mssql/article.php/1438201(which I found on your site, thanks!)"The Localsystem account has no access to shares on the network as it isn't an authenticated network account. So if you want to setting up replication you must change the account the MSSQLServer and SQLServerAgent services runs under to a account with the Windows NT administrator's rights."Now, I dont think this is the issue, as I am saving the Replication data to the same system, right?Any ideas whats going on?Regards,Tj" |
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2003-05-14 : 12:20:19
|
| I was getting that same OS error when I initially tried to get replication set up. Our environment is the same as yours - SQL2000 as the publisher/distributor and MSDE as the subscriber. Though...our MSDE subscribers are not in the same domain...and we are using ftp with anonymous pull subscriptions. Anyway..the problem did turn out to be an issue with the account (on the publisher) that did not have access to the folder where we wanted to create/write the replication files. So, we created a new windows account, specifically for replication duties, and gave it access to that folder and then everything worked. |
 |
|
|
|
|
|
|
|
Replication issues