My general network errors are back!
Very often (once a day) my transactional replication fails after losing communication with the subscriber usually mid update and then it cannot reconnect and eventually gives up trying. As far as I am aware there is no corresponding general network failure that anyone else has noticed and as its an always on leased line there should not be any dropouts.
When I look at the agent history it tells me that there are problems with the ODBC connection, these are either connection timed out, communication link failure, then I get a report that the subscriber sql server does not exist or access denied, then lots of timeout messages again then after the 10 retry attempts it stops;
1. Why is it using ODBC
2. Why is it timing out
3. Is there somewhere I can alter the timeout properties.
As an aside is there a recommended process for completely erasing all replication history, SPs, etc etc from both the subscriber and publisher and starting again on a clean replication slate..?
Thanks for any help you can give
Rolf