Dear all

Trying to remote execute a batch file from our visual cron (5.7.4) server Server 1 (2008 R2), to Server2 (2008 R2). When I start the batch file manually or by task scheduler from the Server2 it works fine.

When the task is run either scheduled or manually from VC it reports success and gives alwas a PID, but it doesn't actually run on the remote server.

Configuration of the remote execution:

Account: serviceAccount@domain
Hostname: Server2 <-- the server name
Command: D:\Application Batches\Test.bat

I created another batch file with an easy command, this doesn't work neither. However I see in the event viewer of Server2 that the process was created, but nothing happens.

The service account is a domain account & local admin on Server2.

Where is here the problem?

Thanks
Matthias

Hi,

the reasons could be many. One important difference is that Remote execution uses WMI (Windows Management Instrumentation). This has some limits and context of execution is a bit different. For example, if you are trying to access mapped drives they may not be accessible in remote execution mode unless you mount them there.

Later versions like version 6.1.3 gives you the correct exit code. Previous versions only tell if process started ok.

Also, finally, to really now the reason why it fails we recommend that you add debugging and write to a file on each line. This way you will see exactly which line it fails on - then it will be a lot easier to tell the real reason and solve the problem.

---

Hi Henrik

Actually I don't access to a mapped drive.

Account: serviceAccount@domain
Hostname: Server2 <-- the server name
Command: D:\Application Batches\Test.bat <-- direct link into file system of Server2

Debugging the batch file seems to be difficult because when I start the VC job on Server1 I can see on Server2's task manager two new processes (conhost.exe and cmd.exe) but it does not execute the batch file (tested with echo and > log.txt)

Installing a new VC version would be fine, just not the next days:-)

What else can I try?

Regards
Matthias

Instead of just using echo > log.txt specify a full path like

echo > c:/log.txt

I guess your previous log.txt ended up in system or temp folder or something else.

---

The logfile is in the same folder and it works when it is executed manually. Anyway I tried it with an absolute path, still the same problem: the processes are created but nothing happens...

When executed manually it probably has another working directory. If not even a log file can be created I find it hard to debug this issue.

---

In this case it is easier to handle it with a scheduled windows task. Maybe next try with a new VC relase with the better exit code.

Thanks for support!

I have a very similar problem. In my case, the task runs on the remote server, but not always retrieves the VC Exit Code, which ends up causing failure "Incorrect function.Exception in Task: Non zero exit code." I'm like the last line in the bat file command "EXIT / B 0." This problem is bothering me a lot because the task was performed, and the VC notified as an error. (sorry for bad english)

I have a very similar problem. In my case, the task runs on the remote server, but not always retrieves the VC Exit Code, which ends up causing failure "Incorrect function.Exception in Task: Non zero exit code." I'm like the last line in the bat file command "EXIT / B 0." This problem is bothering me a lot because the task was performed, and the VC notified as an error. (sorry for bad english)

I think you need to debug log to file. It probably exits with error before your "nice" exit.

---

I already do this for each command line in BATCH, with the command >> LOG.TXT (no problems)

I already do this for each command line in BATCH, with the command >> LOG.TXT (no problems)

Sounds really strange. I see no way we could return that unless it fails earlier. Can you reproduce this? And what is the reason for using the exit command? Because, if it fails earlier it will exit with other exit code anyway. Unless you jump in code.

---