Hi,
The file path was working fine on Workbench but it's giving me this error when I put the FME script in Task Scheduler (or Command Line).
Question
CSV: failed to open error
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+10- Contributor
@fpakzat Would need to see more of the error and/or your syntax for the script. It can fail for many reasons.
+21- Safer
Hi @fpakzat The system user might not have access to that file path. See https://knowledge.safe.com/questions/3881/fme-workbench-on-windows-scheduler.html and https://knowledge.safe.com/questions/67628/fme-batch-file-works-but-not-via-windows-task-sche.html for ideas of how to work around the Windows Task Scheduler.
+10- Contributor
@fpakzat drop another line here of those links from danstasafe don't help. I use task scheduler, flat files and call fmw with .bat scripts on a regular basis. Maybe i can help.
+3- Contributor
I think I found the reason. I got away with this problem by using the path follows UNC standard. I didn't realize the previous path that I used contains a Mapped Drive.
\\servername\path