Skip to main content
Solved

WorkspaceRunner woes: "BadNews"

  • August 1, 2017
  • 5 replies
  • 74 views
lifalin2016
Supporter
Forum|alt.badge.img+39

Hi,

I'm using FME to check the log files of previous runs, testing for errors.

I'm now getting notifications of errors in a set of log files, that has been generated by running a workspace via "WorkspaceRunner". The error is bogus, however, so it messes up my overview by cluttering it with false positives.

The dependent workspace is called with two parameters: the path of the (xml) file to check, and a path to the desired log file. This log file path contains a dash, so I get this error:

BADNEWS: String value `WorkspaceRunner_DanDas: Running FME Workspace xxxxx.fmw with command line:' contains invalid characters and could not be converted into an integer (stfutil.cpp:802)

A typical log file name may be: CONTROL ARWOS XML - TV-Inspektioner.log

How can I avoid having FME attempt to do a bogus subtraction in my string value ??

Cheers

Best answer by erik_jan

Hi @lifalin2016,

I have been running into the same issues.

So, I posted this idea:

clean-up-the-badnews-messaging

It seems some old BADNEWS messages are still around, even though they have no meaning anymore.

-- Cheers, Lars I.
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.

5 replies

lifalin2016
Supporter
Forum|alt.badge.img+39
  • lifalin2016Supporter
  • Author
  • Supporter
  • August 1, 2017
I forgot to state, that it seems to work none-the-less, but the log file is littered with these "errors".

 

 

-- Cheers, Lars I.
erik_jan
Contributor
Forum|alt.badge.img+23
  • erik_janContributor
  • Contributor
  • Best Answer
  • August 1, 2017

Hi @lifalin2016,

I have been running into the same issues.

So, I posted this idea:

clean-up-the-badnews-messaging

It seems some old BADNEWS messages are still around, even though they have no meaning anymore.

fmelizard
Safer
Forum|alt.badge.img+21
  • fmelizardSafer
  • Safer
  • August 1, 2017

Hi @lifalin2016, normally we recommend keeping BADNEWS turned off. Please check out our article on it: The Badnews Function. However, should you want them to be changed/cleaned up, please up-vote @erik_jan's idea.

runneals
Supporter
Forum|alt.badge.img+29
  • runnealsSupporter
  • Supporter
  • August 1, 2017

Hi @lifalin2016, normally we recommend keeping BADNEWS turned off. Please check out our article on it: The Badnews Function. However, should you want them to be changed/cleaned up, please up-vote @erik_jan's idea.

How do you do this on FME server?

 

 

lifalin2016
Supporter
Forum|alt.badge.img+39
  • lifalin2016Supporter
  • Author
  • Supporter
  • August 2, 2017

Hi @lifalin2016, normally we recommend keeping BADNEWS turned off. Please check out our article on it: The Badnews Function. However, should you want them to be changed/cleaned up, please up-vote @erik_jan's idea.

Hi Tia,

 

 

I think you're missing the point here. Debugging information should never be marked as "ERROR" (which it is in this case), but rather "DEBUG" or similar. Yes, I can turn it off, but then I might miss something, since the same option is used in _all_ runs (because it's set in the overall options dialog), not just for the ones being developed (i.e. in the workspace). Or am I missing something here ?

 

 

Besides, this particular error seems to be caused by a wrong assumption on FME's part. Why else would it complain about not being able to do an integer subtraction in a path name ??

 

 

Cheers.

 

 

And Ps. I'm not running an FME Server, just FME Desktop.

 

-- Cheers, Lars I.

Community Stats

32,154
Posts
122,047
Replies
39,812
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.