I am want to use VC's Remote Execute to run a batch file that runs on a 64 Bit server. The VC server is 32 bit.

I am attempting to use Visual Cron as occasionally the job hangs, which stops further executions using Windows Task Sheduler.
I was hoping VC would be able to monitor the run time using the timeout options, including setting the "Consider Timeout as an Error" Check box.

I have upgraded to version 4.48.4

The Batch file normally runs in 2 to 2.5 minutes.

I have set the following options in the job (not task) for testing purposes.

Use timeout - checked

set to 1 minute

Consider Timeout as an Error - checked

Notifications on the Job are set on start and on error. Because I've set an unrealistic timeout of one minute, this should error. (I'm running all of this in the test environment ;0) )

The job fires off every two minutes, but completely ignores the "Do not run job if it's running" option, it just fires again.

I am guessing this is because it is a remote exec command. Do I need to install VC on the 64 bit server and run an execute task locally itself to make this work?

Dave

Main problem is that the WMI api (that Windows provide for this) does only gives us information about start result and nothing more. So we are not able to track remote executes. They are finished the moment they have been launched.

---

I have installed locally and it looks like it has noticed that the task took longer than 2 mins. I'm now waiting to see if it will finish successfully. This is good as I want it to tell me if it has been running for 10 mins, which should never happen....

Dave

How did it go?

---

Henrik, It was OK but appears to have crashed with an out of memory exception over the weekend. This caused me to reboot the server :(

I've sent a mail to support, is that you too?

Dave

We'll examine your error and get back to you as scheduled before.

---