Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


e.wijnstra
2012-12-11T13:35:39Z
I’m having difficulty using REMOTE EXECUTE in VisualCron. We are using v5.4.7, but are testing v6.1.5 as well. We see the same problem in both versions.

When I run this task (01.png) via VisualCron remote execute, I see “scd.exe” starting as well as the process-tree. After 2-3 seconds the jobs fail (red) and disappear. No errors seen/logged (02.png).

When I run the task from the command prompt on the remote server, I can see the process-tree build and the batch job is processing (03.png).

When I run the task with a more basic parameter, it works via VisualCron remote execute (0.4.png, 05.png).

I suspect that passing arguments with the ‘=’ sign might not work properly. Unfortunately it’s the way the .exe works I want to remotely execute.

Can you help?
Thanks in advance!

e.wijnstra attached the following image(s):
Sponsor
Forum information
Support
2012-12-11T15:37:57Z
We did some tests and the = sign is not the problem. We created a small app which needs to be placed in c:\test folder.

The exe takes any argument and write whatever argument it gets to a file in the same folder "out.txt". You can then verify that anything can be used as output.

The file can be downloaded here:

http://neteject.com/download/VisualCron/ArgOut.zip 

So, your problem seems to be related to your specific exe and a combination of factors. Remote execute is executed through WMI which has some limitations and restrictions. It is not entirely sure that your application can run that way, at least not by default. The restrictions could be:

- user limitations in that environment
- access to resources in that environment
- general WMI environment restrictions

You should take a look at security settings in WMI in Computer management. Maybe something there.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
e.wijnstra
2012-12-14T15:18:49Z
Hello Henrik,

Thanks for your earlier answer and providing the .exe

I’ve tried this on both VC versions and also locally. The passing of the parameters (regardless of what signs/symbols are used) appear to be passed on just fine. This appears to rule out VisualCron as a possible suspect.

Hope you have any hints/tricks up your sleeve though on making this one work.


Ebbele Wijnstra
Scroll to Top