Whenever I run a workbench I encounter following error
ERROR |BADNEWS: File C:\\apps\\FME\\metafile\\geodatabaseDefline_.fmi could not be opened (tabrdr_classic.cpp:2756 - tabrdr::ClassicTableReader::TableReaderSource::open) - (tabrdr_classic.cpp:1743 - tabrdr::ClassicTableReader::getRow) - (tabrdr_classic.cpp:1743 - tabrdr::ClassicTableReader::getRow)
I am using FME Desktop 2018.1
+11Hi @harshal.gharat, Thanks for your question.
Are you by any chance running the workspace with debug logging turned on? You can check this in Tools>Fme Options>Translation>Log Message Filter, see if Log Debug is checked.
Most "BADNEWS" logs are debug logs, which are meant to help developers to use. Often the translation will be successful, even with these types of errors logs. Is your translation producing expected results?
Hi @harshal.gharat, Thanks for your question.
Are you by any chance running the workspace with debug logging turned on? You can check this in Tools>Fme Options>Translation>Log Message Filter, see if Log Debug is checked.
Most "BADNEWS" logs are debug logs, which are meant to help developers to use. Often the translation will be successful, even with these types of errors logs. Is your translation producing expected results?
Hi @xiaomengatsafe Yes, I have Log Debug is checked and my translation is also successful however at the end I get a message as Error running translation
+11Hi @xiaomengatsafe Yes, I have Log Debug is checked and my translation is also successful however at the end I get a message as Error running translation
What if you run the workspace again (as long as it won't produce undesired results), with Log Debug turned off? Would that still give you the "Error running translation" at the end?
If you can verify the output of your translation is as you'd expected, it's safe to ignore the error in this particular case.
+22I had similar issues before and posted an idea about this:
