I set up a pretty straight foward command task that calls a perl script like this:

Command: perl c:\localfolder\script.pl

The perl script loops simply iterates through 24 xml files outputs new formated xml files using 11 different xsl files. So this process should 264 new xml files.

About midway through the 7th file, I get an "Error in Argument" error message and the process stops and there are only about 80 files in the output folder.

If I run the exact same command perl (perl c:\localfolder\script.pl) from a command window, the process completes fully producing all 264 xml files.


This is a process that has been running for a year with no problem using windows task scheduler, that we are trying to move into visualCron. It is the first job we are moving from a windows task to visualcron so not having it work right off is a big concern.

Mike

Using the full path makes no difference, I've tried both ways (both in the command window and visualcron).

For security purposes, I can't send you the script and xml files. I thought about an error not being captured when processing in command window (although I see no evidence of this when I run it and look over the output).

So I:

1) Changed the script to only process the first 12 xml files. run task in VC. same error.

2) Then I looked to see how far along it had processed. removed the 7 already processed okay files from folder. run task in VC. Remaining 5 files processed with no errors.


I guess next I'll try and process each file one at a time and see if I can get an error.

It seems to me that if I can run a script from a command window, then I should see no difference running a command task in VS.