Our instance of 24x7 seems to crash at various times, and causes a backup in the next days schedule. I have tried creating a vb script to kill the app on schedule, and start it back up, and even tried windows schduled tasks.

The 24x7 server is killed properly, but only starts back up i i kick of the scripts manually. if the scripts are run on schedule, 24x7 is only a job in the task manager, but its not actually running.

Is there some reason 24x7 scheduler can't be kicked off on schedule ?

There is no reason, you just don't do it right.

See http://www.softtreetech.com/cgi_bin/config.cgi?review=6327 for details

You can schedule this job from 24x7 or your can schedule it "outside" To run it from outside use 24x7.exe /JOB job_id_here

: Our instance of 24x7 seems to crash at various times, and causes a backup in
: the next days schedule. I have tried creating a vb script to kill the app
: on schedule, and start it back up, and even tried windows schduled tasks.

: The 24x7 server is killed properly, but only starts back up i i kick of the
: scripts manually. if the scripts are run on schedule, 24x7 is only a job
: in the task manager, but its not actually running.

: Is there some reason 24x7 scheduler can't be kicked off on schedule ?

Eric,

I have an untested idea.

Write a 24x7 job to call a .bat file to start the 24x7 scheduler. Then schedule that job like the SysOp suggests (24x7.exe /JOB job_id_here).

I hope that helps.

: There is no reason, you just don't do it right.

: See http://www.softtreetech.com/cgi_bin/config.cgi?review=6327 for details

: You can schedule this job from 24x7 or your can schedule it
: "outside" To run it from outside use 24x7.exe /JOB job_id_here

Sorry I pasted wrong link, the correct link is following

http://www.softtreetech.com/cgi_bin/config.cgi?read=3872

: There is no reason, you just don't do it right.

: See http://www.softtreetech.com/cgi_bin/config.cgi?review=6327 for details

: You can schedule this job from 24x7 or your can schedule it
: "outside" To run it from outside use 24x7.exe /JOB job_id_here

An alternative solution is to use ProcessKill utility from 24x7 Tips and Scripts archive. It can be used with a batch file

KillProcess /T 5 24X7.EXE

The advantage of this method is that it can terminate multiple instances of 24x7.exe at once; it attempts to close processes gratefully before terminating them forcibly; and does not need to run 24x7 job.

: Eric,

: I have an untested idea.

: Write a 24x7 job to call a .bat file to start the 24x7 scheduler. Then
: schedule that job like the SysOp suggests (24x7.exe /JOB job_id_here).

: I hope that helps.

Well... i am in fact using a vbscript file to kill / open 24x7 .. even using windows scheduled tasks to run the 24x7 server, it will not open the actuall application.

I am hesitant to use 24x7 itself to restart 24x7... the whole point of starting 24x7 remotely is to fix it when it crashes. 24x7 can't restart itself when crashed, and other servers can't connect to an agent that is no longer responding.

KillProcess is actually a command line utillity. Give it a try.

On the other hand if time allows it might be rather better to find and fix the the root cause of the problems. If you need my help with that please describe in detail what you are running and how you do it. Look in the job log and NT event log for any patterns, errors, warning leading to the crash.

: Well... i am in fact using a vbscript file to kill / open 24x7 .. even using
: windows scheduled tasks to run the 24x7 server, it will not open the
: actuall application.

: I am hesitant to use 24x7 itself to restart 24x7... the whole point of
: starting 24x7 remotely is to fix it when it crashes. 24x7 can't restart
: itself when crashed, and other servers can't connect to an agent that is
: no longer responding.