Problem with scheduled Script

Wolfgang Bach · Post by **Wolfgang Bach** » Wed May 06, 2009 3:24 am

Hello KS-Soft,

i have a problem with a script (HMS-File which imports new Tests) that doesn't run as a scheduled daily job (Options / Schedule) as a "Execute HMS script" at the "Execute action profile". I have no problem with the script when i run it manually at "File / Execute" Script. What can be wrong?

Thanks for your help

Regards

KS-Soft Europe · Post by **KS-Soft Europe** » Wed May 06, 2009 3:34 am

Please, ensure "on the shcedule" option is selected in "Action Properties" window for the "Execute HMS Script" action. Quote from the manual:
http://www.ks-soft.net/hostmon.eng/mfra ... uledaction
===============================
on the schedule
Unlike standard and advanced actions that are triggered by events related only to the tests, scheduled actions are conformable to the schedule. They also may be triggered by some "global" events (e.g. HostMonitor can start "scheduled" actions when user stops monitoring). There are several places where you can use scheduled actions:

* The Scheduler itself - a tab in the Options dialog allows you to execute up to 5 alert profiles by a schedule. E.g. HostMonitor may execute one profile every 1 hour and execute another profile every Monday at 21:00;
* Reports page in the Options dialog: now HostMonitor can execute alert profile after reports were generated;
* Reports page in the Folder Properties dialog;
* Statistics page in the Folder Properties dialog: HostMonitor can execute alert profile before resetting the statistics;
* Pause dialog: HostMonitor can execute alert profiles every time user starts or stops monitoring or when the user enables/disables alerts.

It is a good idea to create separate action profiles for standard/advanced actions and for scheduled actions.
===============================

Regards,
Max

Wolfgang Bach · Post by **Wolfgang Bach** » Wed May 06, 2009 3:47 am

Condition to start is on the schedule

KS-Soft Europe · Post by **KS-Soft Europe** » Wed May 06, 2009 4:29 am

In this case, I would suggest you to select another slot in "Options" -> "Scheduler" tab. If you schedule some profile to be fired once a day, it will be fired only once, even if you change time afterwards. So, just try another slot.

Regards,
Max

Wolfgang Bach · Post by **Wolfgang Bach** » Thu May 07, 2009 5:30 am

Thats the trick. Its working perfectly now. Thx.

infuseweb · Post by **infuseweb** » Fri Jun 12, 2009 11:55 am

Regarding scheduled tests, how do you use "Test Performer" with it? It always defaults to "HostMonitor".

For example, I want to use one action profile to restart a service on a schedule on all my RMA machines. So, the service restart needs to occur on the same machine as the main profile it's tied to.

In the instructions above it states "it's a good idea to use a separate profile for each...". Do I really have to create a separate action profile, then, for each individual RMA machine?

KS-Soft · Post by **KS-Soft** » Fri Jun 12, 2009 12:06 pm

Regarding scheduled tests, how do you use "Test Performer" with it? It always defaults to "HostMonitor".

Are we talking about tests? or actions?

For example, I want to use one action profile to restart a service on a schedule on all my RMA machines. So, the service restart needs to occur on the same machine as the main profile it's tied to.

Well, if you need to start "scheduled" action using several different agents, you should add several actions in the profile.
Not sure I understand what is "main profile"...

In the instructions above it states "it's a good idea to use a separate profile for each...". Do I really have to create a separate action profile, then, for each individual RMA machine?

Are you asking about this sentence "It is a good idea to create separate action profiles for standard/advanced actions and for scheduled actions"?
It has nothing to do with HostMonitor/RMA separation. It tells you about "standard" and "scheduled" actions. You can use the same profile but its nice to setup different profiles because you cannot start "standard" actions using built-in Scheduler and there is no sense to assign "scheduled" action to some test items.