Since upgrading from 6.0.3 to 6.0.9 my remote execution tasks, although still executing, all return errors for no exit code:

Output: No Output
stderr: Exception in Task: Not found
Exit code: 77777
Result: VisualCron specific error

Log shows:
Exception in Task: Not found
Exception in Task: Non zero exit code

I've tried every combination of credential on earth.

I'm executing .bat scripts, and it works fine when I do a local execution. I've simplified it down to this for testing:

@echo off
mkdir test
EXIT /B 0

Any ideas?

Could you please test this with this version:

http://www.visualcron.co....aspx?g=posts&t=2370 

---

The upgrade did not resolve this issue for me.

1. do you use a Credential?
2. have you edited the Credential and check "Login user" and "Load profile"?

---

1. Yes
2. Every possible combination x 10

Something notable, "Wait for completion" option. If I uncheck this VC shows a Output = "Process with Id: #### was started successfully" & Exit Code = "80000"(still an error).

There is a bug fix in this in version 6.1.0. Could you try this version first?

---

FYI.. I'm on ver 6.1.1 and this is still a problem.

In order to prevent erroneous errors I need to uncheck "wait for completion" and uncheck errors for "non zero error codes".

FYI.. I'm on ver 6.1.1 and this is still a problem.

In order to prevent erroneous errors I need to uncheck "wait for completion" and uncheck errors for "non zero error codes".

What operative system and service pack do you get this on (both VisualCron machine and remote machine)?

---

I have several, but I will narrow it down to one setup...

-I am using Windows Server 2003 R2 SP2(32bit) on the VisualCron Server
-The remote server(s) run Windows Server 2003 R2 SP2(64bit)

The .bats are executing, but Visualcron times out waiting for the Exit code.


Is this proper syntax for an exit code?

EXIT /B 0

Yes, it is proper syntax. But I wonder if it execute at all? What if you uncheck the "Wait for completion" - does it start and run without error?

---

Yes, everything executes properly in all cases. But the whole point of using something like VisualCron is for workflow management and error reporting (beyond what I can do with Windows Task Scheduler).

Unchecking "Wait for completion" prevents VisualCron from timing out, but I get an error for "non-zero exit code" of 80000.

Are you sure that the process has exited? What we do is to start a watcher for that newly started process id. The timeout values control how long time we wait for it to complete.

What we have added for next version is some debugging on which process id we are watching. Then you can log on to remote machine and verify.

---

Yes, process is definitely exiting.

This process would be "cmd.exe", since we are executing a .bat file.