Skip to main content
Question

Optional Reader: Failed to read the specified file(s) in the folder '.\\'

  • Jul 20, 2016 9:15 AM UTC
  • 4 replies
  • 88 views

gpt_geoinfo
Contributor
Forum|alt.badge.img+3

Hi FME'ler,

I have a CSV-Reader which is optional

When starting the workbench and leaving this reader blank it fails:

Does anyone know about that issue?

Thanks in advance,

 

Maria

FME Desktop: 2016.1.0.1 (20160516 - Build 16494 - WIN32)

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.

4 replies

david_r
Celebrity
  • Jul 20, 2016 9:59 AM UTC

That option is only relevant to the published parameter value, not to the reader itself.

Have you tried setting "Ignore failed readers" to Yes in the workspace parameters?


gpt_geoinfo
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • Jul 22, 2016 1:51 PM UTC

Thanks @david_r, that helped. Didn't know about that parameter.

But now - when starting the workspace in batch - no features are written. When starting the workbench everything works fine. Is that problem linked to that parameter?! Or is there anything different wrong...?!


david_r
Celebrity
  • Jul 22, 2016 2:31 PM UTC

Thanks @david_r, that helped. Didn't know about that parameter.

But now - when starting the workspace in batch - no features are written. When starting the workbench everything works fine. Is that problem linked to that parameter?! Or is there anything different wrong...?!

What does the log file say?


gpt_geoinfo
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • Jul 25, 2016 8:26 AM UTC

Thanks @david_r, that helped. Didn't know about that parameter.

But now - when starting the workspace in batch - no features are written. When starting the workbench everything works fine. Is that problem linked to that parameter?! Or is there anything different wrong...?!

I looked closer to the log and the batch file. It turned out it was a typing error. -.-