Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


hepworthd
2012-09-07T16:29:44Z
I have an ftp job that does the following:
- Touches a heartbeat file
- Does an FTP pull
- Logs the Pull session to a file
- Loops through downloaded data files and renames them.

When I added a new task to read an XML file right after completing the FTP pull, with, or without data, the loop rename process fails. I am using the loop to go file by file, full path, and am getting this error:
- '9/7/2012 12:01:28 PM Err Exception in Task: Illegal characters in path.'

Upon removing the XML read, the process works with no issue.

thanks
Sponsor
Forum information
Support
2012-09-10T07:41:05Z
So, the error is very specific to the XML Task. Could be that the file is located on a network drive and you need Credentials?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hepworthd
2012-09-10T13:52:07Z
I'm not sure if it is actually only associated with an XML task or not, just how I found the issue. The data resides on the local disk, if I put the same XML process as the first step, no issue's with the job.
Support
2012-09-10T14:01:56Z
Originally Posted by: hepworthd 

I'm not sure if it is actually only associated with an XML task or not, just how I found the issue. The data resides on the local disk, if I put the same XML process as the first step, no issue's with the job.



So, then it is something about the Variable that you use? Which do you use and if you create a file write Task before this XML task (and just write the Variable value) - what does it contain?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hepworthd
2012-09-10T14:03:27Z
The XML task all it does is read's a node, and gathers the information found in the node, that's it. I placed another task in the same location, a write to file task, and it did the same thing, very strange, since I have a write to file task already there and works fine, as long as I do not put another task in line.
hepworthd
2012-09-10T14:08:01Z
Another note, if I deactivate the original write file task, and activate the new task, the job runs successfully.
Support
2012-09-10T14:17:42Z
Originally Posted by: hepworthd 

Another note, if I deactivate the original write file task, and activate the new task, the job runs successfully.



Right, I understand this. But the error itself is natural if there is something with not finding the file so I suspect there is something about the path.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hepworthd
2012-09-10T14:19:25Z
Sorry to keep posting what I find in seperate replies, but another thing I found. If I move the original write file task further down my process, and keep the new write file task in place, the job runs successfully. But when I put a condition on the new write file task, to check if the previous task ran successfully, the Loop fails again, this new write file task basically writes out a failure notification if the previous task fails, so since my previous task was successful, this write task was skipped, and cause the loop issue.
hepworthd
2012-09-10T14:21:23Z
The path is fine, and always will be fine, running a control test that will ensure it will run successfully everytime. The issue seems to be in the loop rename task, I am using '{PATH(GetDirectoryName|{LOOP(CurrentValueX)})}' as my path, and '{PATH(GetFileName|{LOOP(CurrentValueX)})}', these are not evaluating correctly during my modifications, only if I keep one task between the job, and the loop.
Support
2012-09-10T14:24:54Z
Ok, please create a sample Job (where you can reproduce this) with as few dependencies as possible (and as few Tasks as possible). Then export the Job and post here. Please also tell us if any files are needed and where. When working with files for the test job then please assume that they are existing in c:/ root. This will simplify testing a lot. Thanks.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hepworthd
2012-09-10T15:02:28Z
Currently, with the task 'Get Error Level' in this Order, we see a failure, if you move the task 'Get Error Level' to Order number 1, the job successfully completed.

thanks
File Attachment(s):
LoopTest.zip (7kb) downloaded 35 time(s).
hepworthd
2012-09-12T14:54:16Z
Has there been any update/investigation on this yet?

thanks
Support
2012-09-12T14:59:32Z
Sorry for the delay, we will come back with a result tomorrow as early as possible.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2012-09-13T08:08:32Z
We tested the Job, as is, and it worked without returning any error. Do you really get an error with the exact same setup as you sent?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hepworthd
2012-09-21T13:36:59Z
Yes I do. Also running version 6.1.0, so not sure if maybe that's the issue?

thanks
Support
2012-09-21T13:50:18Z
I cannot say exactly if/when this has been fixed. But I tested with version 6.1.3 and it worked there.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top