Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a SQL Server 2000 Standard database with some tables being replicated (continuous transactional replication) to dozens of SQL Server 2005 Express and MSDE computers.

The step 2 of the replication agent job (Run agent) is configured by default to retry every 1 minute for 10 times if some problem ocurr. Because the client machines get shut down at night (they are POS machines), we changed the number of retries to 5760 (4 days), so replication would not be broken at night and would not need to be restarted manually.

But the problem is that every other day we have at least one machine with broken replication, with this error:

The process could not connect to Subscriber 'POS986'. NOTE: The step was retried the requested number of times (5760) without succeeding. The step failed.

It seems that SQL Server is not respecting the number of retries or the interval between retries as we configured.

PS: I have restarted the replication job after changing the number of retries from 10 to 5760.

share|improve this question

create a job which Check the status of the job and run if it fails periodically.

HTH Vinay

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.