Skip to main content
Archived

Clean up the BADNEWS messaging

Related products:FME Form
  • Jun 19, 2017 12:00 AM UTC
  • 8 replies
  • 99 views

erik_jan
Contributor
Forum|alt.badge.img+26

With the DEBUG option in FME Desktop on, the log file will contain a number of additional information lines.

That can be very helpful in solving issues.

But it will also contain some additional errors that can cause customers to panic.

I spend almost a day explaining to a customer (who had the debug option on) that this could be ignored if the workspace does not fail:

BADNEWS: File D:FMEDesktopmetafileMULTI_WRITER.fmf could not be opened (tabrdr.cpp:161)

It would be great if the messaging could be cleaned up, so unneeded messages do not appear.

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.

8 replies

runneals
Enthusiast
Forum|alt.badge.img+32
  • Enthusiast
  • Jun 20, 2017 8:24 PM UTC

If they do keep it, don't make it red text. Make it yellow or black.


mark2atsafe
Safer
Forum|alt.badge.img+59
Yes, for sure tell users not to use that option unless you already have a problem that you need to investigate further.

 

 


erik_jan
Contributor
Forum|alt.badge.img+26
  • Author
  • Contributor
  • Jun 21, 2017 8:39 PM UTC
@Mark2AtSafeTrue, but after turning it off, the mode can still be available in the FMW file:

 

https://knowledge.safe.com/idea/46396/show-debug-logging-mode-as-workspace-property.html

 


mark2atsafe
Safer
Forum|alt.badge.img+59
You're right. I couldn't believe it at first, but I checked the file contents and it is saved as part of the mapping file:

 

FME_DEBUG MAPPING_FILE BADNEWS FME_STACK_TRACE UNGROUPED UNCORRELATED DUMP_SCHEMA XSD_VERBOSE HTTP_DEBUG FTP_DEBUG

 

I'm going to file that as a 'bug' because it seems to me that anything that is an option should not affect a workspace like that.

 

You can fix it by turning off the setting and saving the workspace.

 

But it's even more reason to not use that option unless you have to.

 


lifalin2016
Influencer
Forum|alt.badge.img+42
  • Influencer
  • Aug 2, 2017 6:36 AM UTC
Or maybe just tag all debugging information with "DEBUG" instead of - say - "ERROR" ?

 

 


Forum|alt.badge.img
  • Feb 14, 2018 8:42 PM UTC

Hi All, I am getting this error as well, even with debug option checked off. One observation that FME 2017 (64 bit) installation doesn't include this file, may be this is the reason for the error. I am curious if there is workaround for this issue. Appreciate any feedback.

BADNEWS: File C:\\Program Files\\FME64\\metafile\\MULTI_WRITER.fmf could not be opened (tabrdr.cpp:161)


Forum|alt.badge.img
  • Feb 14, 2018 8:55 PM UTC

I also wanted to add that running the workspace from FME IDE doesnt have this problem. It ONLY happens when calling the workspace from a batch file.


Forum|alt.badge.img
  • Feb 14, 2018 8:57 PM UTC

I also wanted to add that running the workspace from FME IDE doesnt have this problem. It ONLY happens when calling the workspace from a batch file.

 

testbat3.txt