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 |
|
acm
Starting Member
4 Posts |
 Posted - 2002-06-12 : 08:26:10
|
| The following is the architecture:Server_origin (Publisher + Distributor)Server_dest (Subscriber)Replication Agent connects to Publisher through 'sa' accountAgent connects to Subscriber with 'sa' password.Both servers are on the same domain but different networks. The snapshot files get created. However, the 'Push' process never happens. The following is the message I receive:"The process could not connect to Subscriber 'Server_dest' "When I choose to set the transactional replication between two servers on the same network the replication process works as expected.Any suggestion would be greatly appreciated?Thanks,ACM |
|
|
M.E.
Aged Yak Warrior
539 Posts |
Posted - 2002-06-14 : 12:50:52
|
| SA Login is your problem here. SA has full rights on your the SQL servers but not on the network. quite simply, SA is being denied access across networks. I'd try to move to using windows logins for this and drop the SQL server 'SA' account. Then just create a login account that allows sql agent access across the networks and admin in the SQL servers.key thing here is permissions on the SA account-----------------------Take my advice, I dare ya |
 |
|
|
acm
Starting Member
4 Posts |
Posted - 2002-06-17 : 09:11:51
|
| Thank you for your time, but we actually set initially the SQL Server Agents on both sides to log in through Domain Administrator account with no success. It was then when I thought that sa could help but we got the same result. |
|
|
|
|
|
|
Transactional Replication: connecting to subscribe