Hi,

I have a remote execute task that is returning an error code on completion: 77777(VisualCron specific error). The task also returns a couple of errors in Output(StdErr) - “Exception in Task: Not found” and “Exception in Task: Non zero exit code”. The VBScript appears to execute remotely when the task is triggered, but it returns the above mentioned errors on completion. I have tested the VBScript locally and it executes without errors, so I know the script is not at fault.

Reading other posts, I think this could be a permission related problem, but I have tried all possible combinations of credential config and nothing works.


VC version 6.2.2

Try using local path for engine and script without the UNC and without and hidden drives ($C), just something like this;

c:/engine.exe
c:/script.vb

---

nope, still no joy.

FYI - this is what the test script is doing (below).


'Test Script

strDir = "C:\VBS_Test"

Set objFS = CreateObject("Scripting.FileSystemObject")
Set objFolder = objFS.CreateFolder(strDir)
WScript.StdErr.Write "I created the folder " & strDir & " "

Could you try to uncheck "Wait for completion"?

---

Hi,

If I uncheck the ‘wait for completion’ box, the task does complete successfully. It doesn’t, however, return the StdOut or StdErr that I require. Also, the purpose of using VisualCron is to schedule several jobs that are dependent on their predecessors. As far as I can tell, the task is now completing successfully, regardless of the VBScript outcome.

The Remote Execute Task relies on Windows and cannot return output. If you want to return output you should use the normal Execute Task and alter Execution context so you execute on another computer. It requires that you install VisualCron on remote computer but gives you all features of Execute Task (like output).

---

OK, forget that I wanted the task to return output (I can live without that). I simply need the task to fail or complete (depending on the VBScript result).

OK, forget that I wanted the task to return output (I can live without that). I simply need the task to fail or complete (depending on the VBScript result).

On some systems the "Wait for complete" is not simply reliable. There seems to be a bug in the Windows API regarding this. We have not yet found any workaround but to use our own remote execution.

---