May 16, 2008 at 8:24 am
Hi all
I have 64-bit distribution server struggling to replicate to a 64-subscriber in a specific location.
Replicates fine (although alot of "cannot connect to subscriber errors) to a 32-bit subscriber in the same location.
If I replicate from the subscriber down to the distributor, zero errors or problems.
When setting up the subscriptions, the server connects to the subscriber and populates the database drop-down list. Yet, when it actually has to replicate, no joy or atleast takes ages to replicate 10 records
The process could not connect to subscriber
Unable to complete login process due to delay in opening server connection
Turned on agent logging and error file also had above in, and error 106 (haven't found much on that)
As extra tests, same distributor has replicated to other multiple locations (32/64 mix of subscribers) without any problems.
There are no firewall rules blocking sql and as mentioned, it does connect during setup. The odd publication has made it there of numerous attempts
Even configured a 32-bit distribution to same location and it fails outright, whether the subscriber is same 64-bit machine or 32-bit.
Our other locations replicate to "problem location" without any problems.
Network admin has emailed the location hosting companies to see if any filtering is occurring on our line as a last resort.
Ping times are 100ms average.
Am I missing something?
John Mac Pherson
Database Administrator
Optimal Information Systems Pty (Ltd)
jmacpherson@ois.co.za
May 23, 2008 at 9:39 am
SQL Server is impatient. 100 ms seems like a long time between endpoints for SS to wait. You may need to redesign your approach - load the xactions locally and then try to upload within the one machine.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply