Dear all,

my remote Execute task does not stop.
I can see, that the executed Command was running on the remote server ( a small .bat file scanning a directory and saving it on the remote server --> dir rpm*.* /a-d /b > dir.txt ), but in VisualCron the job is still running and running .... and of course starts not the next task.
I am new to visualcron. So I think, the problem is before the screen 😕 😢
Have you got any ideas?
Thanks
Axel

I have to add :

2 hours 50 minutes later the task ended with <<Process with Id: 3736 was completed successfully >>
This means, that the result of the task ( creating the file dir.txt ) took about 5 seconds and it took 2h50 until visualCron realized, that the job is finished.
Anybody an idea, why this takes so long? and how to handle? Workaround? Perhaps with Timeout settings?
We run with 7.1.3

Axel

Was the 'dir.txt' last modified date 2 hours and 50 minutes prior to when the job got marked as finished? Just curious if something else hung and it didn't write the file until right before quitting.

Was the remote system disconnected, rebooted, etc.... around the time the job completed? I ask because it likely came back as successful because the remote task finally ended whether that be due to someone killing a process, rebooting, etc...

Screenshots of your remote execute task and maybe the contents of the batch file you're running would be helpful to try and reproduce.

Brian

the script to be executed is just:

dir rpm*.* /a-d /b > dir.txt

the timestamp of dir.txt is 13:51
i have added the log of the job, so you can see, that the file was created imediatly after start.

There was no problems with the remote server.
i had the same problems yesterday.
This is the first time, i work with remote execute. So, perhaps i configured sth wrong?

I am just proofing visualcron because our old tool ( Opalis ) run out of support.

There are many limitations in Remote execute and the property "Wait for completion" as there are bugs in the API that we use (WMI). It just works on some systems and other systems hang. To work around this you either have to uncheck that property or use the normal Execute Task in remote mode (Execution context setting) - that gives you more features but requires you to install VC on remote computer.

---

Hi Henrik,
thanks for your reply and the workaround.
by the way:

I have added a timeout and tested the job again.
first time the timeout stopped the task, the second ( and third ...) time the task ended successfully after one second 😢

so i think about the workaround
Axel