I'm testing a Winbatch script I created. The VC ExecuteScript function does not seem to recognize that type of script. (.wbt extender)
What are the types of scripts that VC will recognize to execute?
Or, do I need to launch Winbatch in the background somehow in order to execute this script?

VisualCron can execute any type of script but it may not be clear which executable that is actually processing the script. In the case of WinBatch you need to use the WinBatch.exe path in the command and the path to your script in the argument textbox.

---

I'm not sure I understand what you are saying.

I have the path specified in the "execute script" tab as:

C:\Program Files (x86)\WinBatch\System\Consolidate Route Files_TEST.wbt

The executable for WinBatch (Winbatch.exe) resides in the "System" directory which is in this path. The script does not run, in fact, I get a message stating "no process is associated" which I interpret it to mean that either VC doesn't know where to find the .exe file, or the script in the current .wbt extender can't be executed.

How do I insert Winbatch.exe in the command? It does not allow me to select anything other than Task Type "execute script".

As this is a background operation the SYSTEM account may not know which executable that is able to run *.wbt files. That is why you need to specify the full local path (on the remote server) in the command line and the full local path to the script (on the remote server).

---

***NOTE For WinBatch scripting users***

If you are going to use WinBatch to build and run your scripts, you need to follow a specific convention in setting up the task in the VisualCron product. At the guidance of Henrik, I used "Execute" instead of "Execute Script".

However, using both the command and argument was confusing to VC and resulted in the script appearing to run, but it really did not.

We resolved this by using a direct path statement like this:

C:\Program Files (x86)\WinBatch\System\Consolidate Route Files_TEST.wbt

in the Command line of "Execute" and running it using the "shell" option. An argument was not needed. Credentials were not necessary.

If you have Popmenu.exe running the background for Winbatch scripting, the command will find it and run fine.

Make sure you have adequate authority to the directories that you are writing/reading from with the user that you are running the script under.

Many thanks to Henrik for excellent support!

hi..
Can I run *.vbs with parameter/arguments on Task Type: Execute script?
if I used type: Execute to run *.vbs,it can run but can't send error description to Task result when I got error. task just display success but in fact got error/error description display on StdErr
Can I custom Task Result value using *.vbs?

VisualCron raises an error if a different exit code than 0 is raised. This done by default when a normal application fails but in vbscript you have to raise this your self.

Try adding something like this:

Err.Raise 155, 'My error message'

Replace error message and 155 with your error code.

---

thanks for your reply
with add script "Err.Raise 155, 'My error message'".
if run with task type:EXECUTE SCRIPT: task can display error result suitable with my raise but
if I run with task type: EXECUTE, task can't display error result suitable with my raise.
(command: cscript.exe, arguments: /nologo c:\test.vbs)
how can I display error result suitable with my raise when run task with type: EXECUTE not EXECUTE SCRIPT
thanx

Try using this method instead:

wscript.quit(1)

---