Are you the developer of the service? Why not add the wait or retry in the service code?
--Tigran On Tue, Apr 13, 2010 at 1:14 PM, Bonner, John <[email protected]> wrote: > Hello Admins, > > I know this may be a simple questions for you guys but I'm a developer so my > knowledge is not as robust. > > Our web server has a service that relies on communication with SQL server. If > it doesn't see the SQL box Sitescope alarms as the service is not started. > Now this is fine and dandy except during maintenance windows when the servers > get rebooted and the web server comes up before the SQL box does. I know I > could have Sitescope attempt to start the service but I was wanting to be > more proactive and have Sitescope be the backup. So I was hoping there might > be a configuration / dependancy I could specify on that service to not > ATTEMPT it's first start until a check verifies SQL is up. Since I know this > is not a new problem I figured there must be a tried and true method for > handling this scenario? > > Thank You Very Much > JB > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
