Skip to main content
Question

ERROR |BADNEWS ??

  • September 12, 2013
  • 4 replies
  • 520 views
farfar
Contributor
Forum|alt.badge.img+12
Hi all,

 

if i launch a workbench, it executes no problem but i see this error into log file when i checked "Log Debugging information" from Tools==> FME Options==> Runtime=>Log file Default".

 

ERROR |BADNEWS: File C:\\Program Files\\FME\\metafile\\MULTI_WRITER.fmf could not be opened (tabrdr.cpp:997)

 

 

ERROR |BADNEWS: File C:\\Program Files\\FME\\metafile\\PythonFactory.fmf could not be opened (tabrdr.cpp:997)

 

 

ERROR |BADNEWS: File C:\\Program Files\\FME\\metafile\\QueryFactory.fmf could not be opened (tabrdr.cpp:997)

 

 

What that means this error?

 

 

Thanks an advance. 

 

 

FarFar
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
  • david_rCelebrity
  • September 12, 2013
Hi,

 

 

if your workspace executes correctly, I would not pay any attention to these messages. Safe also recommends that you do not turn on this option unless you're working on a specific issue with them.

 

 

David
farfar
Contributor
Forum|alt.badge.img+12
  • farfarContributor
  • Author
  • Contributor
  • September 12, 2013
Hi,

 

Ok. Thanks.

 

FarFar

 

 

R
  • royce
  • March 20, 2014
But surely if::

 

C:\\Program Files\\FME\\metafile\\MULTI_WRITER.fmf 

 

is not on my hard drive this would be somewhat of an issue?

 

 

I get this eror later on in my log:

 

BADNEWS: No MULTI_WRITER dataset name was specified (couldn't find a value for `MULTI_WRITER_DATASET') (writrimp.cpp:549)

 

 

Any ideas?

 

I have been going around in circles for a week with this.

 

 

thanks

 

Russ

 

 

 

D
Go to tools FME Options then on Runtime untick Log debugging information

 

 

You only need this if you're working on a specific issue with Safe.

 

 

Darren

Community Stats

32,408
Posts
122,908
Replies
40,127
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.