Replication Problem

Due to network failure (2 hours a day) replication fails between the servers. Normally when network is down for more than an hr, I am not able to restart the replication process by starting the agent. All RED cross marks Appears in the runing services.
Please tell me how do I manage this condition using some frontend deamon that check the replication status, if the replication is down due to network prob or any other reason, daemon tries to restart the replication process.
From http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Schedule your agents to restart every 5 minutes. If an agent fails it will
fail for a specific reason. The most common reasons are network
interruptions.
I would poll the msrepl_errors table on the distribution database and have
new errors sent to me via a page. I could then evaluate whether the
automatic scheduled restart will clear the error condition.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Madhur" <raj_max@.hotmail.com> wrote in message
news:6a88e5f5-42b0-4969-99cc-c41781493419@.developmentnow.com...
> Due to network failure (2 hours a day) replication fails between the
> servers. Normally when network is down for more than an hr, I am not able
> to restart the replication process by starting the agent. All RED cross
> marks Appears in the runing services.
> Please tell me how do I manage this condition using some frontend deamon
> that check the replication status, if the replication is down due to
> network prob or any other reason, daemon tries to restart the replication
> process.
> From
> http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com