Hello,

I am looking at the documentation on how to setup Remote VisualCron Server Execution Context. The docs just mention the feature but doesn't seem to help much when you run into trouble. So I will explain my situation in hopes to help others while finding advise.

I have VisualCron (VC) installed on a main server and a remote server (2 running instances of VC server). I have a job setup on the main server with an execute task. The task references runmytask.bat file on c:\MyTasks\ of the remote server. Credentials are setup for a user using {domain}\{username} type login and the execute task references those credentials in the Execute tab. On main settings tab, I have selected "Remote VisualCron Server" under the execution context section using a background execution. I am using a VisualCron type of connection for that connection using a local user for the username and password on that remote server. I have verified that user can log into the remote server using the client tools on my machine.

Having set this up I am unable to get the task to execute. It fails with exit code 2 (cannot find the specified file) and no error output. I am assuming the path to the bat located on the remote VC server cannot be referenced in the same way. How should this be setup for the best success. We have tried remote execution tasks but we hit a fail point when the bat references a copy command to another remote server by saying success on the task but the file copy from within the bat did not execute because files were left. We have tested it works when running directly on the remote server. We are in a position supporting old .bat files inherited but no power to re-engineer them to work better for VC. We just need VC to execute the tasks.

Best Regards!!!

Hi,

if you use the Execute Task with Remote Execution Context the Job does not have to exist on the remote server but the executable must exist at the specified path. If you verify that you have the correct path please add some screenshots of settings.

---

Are you saying the executable has to reside at a path relevant from the remote server perspective or the main server prospective? The job is being setup on the main server not the remote server.

Attached are:
execute context settings:


execute tab of edit task:

Yes, the script needs to reside on the server it should run on.

---

Ok so the script resides in a path relevant to the remote vc server. And the path is valid. What can I do to troubleshoot further since this does not work?

Ok so the script resides in a path relevant to the remote vc server. And the path is valid. What can I do to troubleshoot further since this does not work?

I think we could start with something simple. Like creating a script at server level that just have a batch file that echo. Just to see if it is a general problem or not.

---

Ok thanks. I have created a bat on the remote VC server (the one set as the remote vc server in the execution context of the task). The file includes a simple echo and a piping of the console to a log file using arguments on the execution. It fails status code 2. The only way I see this working is if I UNC to the file on the remote server. The path is relevant to the local server holding the job for the remote execution.

Might be a misunderstanding. The path, and the script, should be respresenting remote server. Because the script is not sent in anyway to the remote server.

---

Can you provide an example setup? Sorry I am very visual and literal.

Let say you have Server A and Server B. Server B is where you want to run execute a command. Server A hold the Job that calls the remote Server B. Then, in the Execute Task (located on Server A) you need to specify a local path on Server B - to the script you want to run. Hope this is more clear. Not sure how I could visualize this here.

---

This doesn't appear to work the same way you describe or I am misunderstanding. Can we get a quick 15 minute call stood up in order to have you walk me through the setup? I have followed your instructions but still getting the same error.

Please send an email to support@visualcron.com with your time zone and suggested day for next week. I think we need a screen sharing session for this to make it clear as we cannot fully confirm on phone only.

---