Skip to main content
Archived

Clean up the BADNEWS messaging

Related products:FME Form
rylanatsafe
siennaatsafe
erik_jan
lifalin2016
stalknecht
+7
  • rylanatsafe
    rylanatsafe
  • siennaatsafe
    siennaatsafe
  • erik_jan
    erik_jan
  • lifalin2016
    lifalin2016
  • stalknecht
    stalknecht
  • courtney_m
    courtney_m
  • T
    tara
  • cwarren
    cwarren
  • jvanravenswaaij
    jvanravenswaaij
  • tino
    tino
  • C
    conterraclara
  • J
    jaygis
erik_jan
Contributor

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 a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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
Contributor
Forum|alt.badge.img+19
  • runnealsContributor
  • Contributor
  • June 20, 2017

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

mark2atsafe
Safer
Forum|alt.badge.img+43
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+17
  • erik_janContributor
  • Author
  • Contributor
  • June 21, 2017
@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+43
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
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Contributor
  • August 2, 2017
Or maybe just tag all debugging information with "DEBUG" instead of - say - "ERROR" ?

 

 

-- Cheers, Lars I.
J
Forum|alt.badge.img
  • jaygis
  • February 14, 2018

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)

J
Forum|alt.badge.img
  • jaygis
  • February 14, 2018

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.

J
Forum|alt.badge.img
  • jaygis
  • February 14, 2018

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

Helpful Members This Week

Community Stats

30,990
Posts
117,465
Replies
38,773
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
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.