shaileshmonani
asked on
PULL REPLICATION OS ERROR 53
Hi,
We are unable to overcome the error below which occurs during Pull Replication while reading the snapshot files at the publisher.
2013-03-11 10:48:09.122 Initializing
2013-03-11 10:48:30.603 The process could not read file '\\AAA-BBB\repldata\unc\AA A-BBB$SQL2 008__DB_PU B_MASTERS\ 2013031116 1741\Produ ctMaster_5 .pre' due to OS error 53.
2013-03-11 10:48:30.978 Category:OS
Source:
Number: 53
Message: The network path was not found.
The setup is as under -
Two Servers running Windows 2008
Both having SQL 2008 R2 standard edition
Connected through internet having Static IP address for Server A and Dynamic Ip Address for Server B
Server A acts as Publisher
Server B acts as Subscriber - with pull subscription
\\\AAA-BBB\Repldata folder has been shared - granted rights to everyone for Full Control and also given NTFS security rights to everyone user
Subscriber Security options -
Distribution Agent - Runs Under SQL Server Agent Service Account
Connect to Distributor - Impersonate Process Account
Connect to Subscriber - Impersonate Process Account
We have also tried by creating a local user named PullReplication (having administrator access) on both the servers and assigning them as SQL Server Agent Service Startup Account.
Thanks.
We are unable to overcome the error below which occurs during Pull Replication while reading the snapshot files at the publisher.
2013-03-11 10:48:09.122 Initializing
2013-03-11 10:48:30.603 The process could not read file '\\AAA-BBB\repldata\unc\AA
2013-03-11 10:48:30.978 Category:OS
Source:
Number: 53
Message: The network path was not found.
The setup is as under -
Two Servers running Windows 2008
Both having SQL 2008 R2 standard edition
Connected through internet having Static IP address for Server A and Dynamic Ip Address for Server B
Server A acts as Publisher
Server B acts as Subscriber - with pull subscription
\\\AAA-BBB\Repldata folder has been shared - granted rights to everyone for Full Control and also given NTFS security rights to everyone user
Subscriber Security options -
Distribution Agent - Runs Under SQL Server Agent Service Account
Connect to Distributor - Impersonate Process Account
Connect to Subscriber - Impersonate Process Account
We have also tried by creating a local user named PullReplication (having administrator access) on both the servers and assigning them as SQL Server Agent Service Startup Account.
Thanks.
ASKER
BTW the Publisher and Subscriber servers are behind a firewall (Managed by a Router).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1. Created UserA on both the computers (having same username and password) using Manage - Local users and Groups. Made this user part of administrator group.
2. Then assigned this user to Sql service agent service. Username was set as ".\UserA"
3. Added this user to SQL Server security.
4. On Publisher Computer - assigned this user rights on the share and in NTFS as full control
5. Restarted SQL Server agent on pub and sub both.
6. Recreated the subscription on Subscriber computer. Distributor Agent settings - Impersonate Process Account, Connect to Publisher impersonate Process Account and Connect to Subscriber also Impersonate Process account.
Same error still occurs.