Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

The runnable tool object was invalid (default)

 

The runnable tool object was invalid (default)

Anyone see this issue?

Trying to run any task and I get an error:

The runnable tool object was invalid (default)

-----------------------------
Server configuration for HP SIM CMS as follows:
Windows 2003 Server Enterprise,
8GB of RAM
SQL 2000 SP4 Enterprise
ProLiant DL585 G1
Quad AMD Opteron 2.4 GHz CPU
HPSIM 5.1 SP1 with hot fix's
4 REPLIES
Change_happens
Honored Contributor

Re: The runnable tool object was invalid (default)

It depends on which u r trying to run that task. If u r running task on a logical node/iLO and it requires server then it becomes Invalid.
So question is on which system/s u r running the task and whats this about?
Lawrance Lee_1
Frequent Advisor

Re: The runnable tool object was invalid (default)


I am also seeing this problem.

I am going through the steps to "Creating a task to delete disk thresholds on a monthly basis" in the SIM 5.1 user guide, page 320.

I follow the steps *exactly* as the manual suggests and when I run the scheduled task, I get this error as well.

I'll be happy if someone gan provide some information on why this error message pops up on a dialogue box. :(
Lawrance Lee_1
Frequent Advisor

Re: The runnable tool object was invalid (default)


I should also state my Central Management Server configuration:

Windows 2003 Server Enterprise, SP1
16GB of RAM
SQL 2000 SP4 Enterprise Edition
ProLiant BL25PG1
Dual AMD Opteron single core 2.6 GHz CPUs
HPSIM 5.1 SP1 with hot fix's

I only get the problem if I click on "Run Now", but if I just let it auto start on the scheduled time, the SIM server actually executes the scheduled task.

So perhaps my suggestion to you, Mariano, is simply to schedule the tasks that you want to start at a certain time.

Re: The runnable tool object was invalid (default)

You may also notice that although you get the popup the task does run. Have a call with HP and will provide an update if we get anywhere on this.