Skip to main content
Solved

Translation was SUCCESSFUL despite of ERROR in Logfile??

  • February 22, 2016
  • 3 replies
  • 33 views
vki
Contributor
Forum|alt.badge.img+7

We have to run various workbenches (and other scripts) automatically and repeatedly with different timeperiods in between, so I wrote some python scripts to run them.

In those scripts I check the returncode of FME and if it's <> 0 (Translation was successful) then my scripts throw an error.

But obviously FME sometimes returns 0 (Translation was successful), even though there is an ERROR in the Logfile and the translation was NOT successful.

How come? Isn't this a bug?

Thanks in advance

Vera

...

2016-02-22 04:40:44| 221.4| 0.0|INFORM|XLSX Reader: Opening dataset '\\\\ktsz003\\groups$\\AVG\\Geoinformation\\Produkte\\GDI\\Themen\\A018 AV\\data\\a018_Domain_EOB.xlsx'...

 

2016-02-22 04:40:44| 221.4| 0.0|ERROR |XLSX Reader: Failed to open the dataset '\\\\ktsz003\\groups$\\AVG\\Geoinformation\\Produkte\\GDI\\Themen\\A018 AV\\data\\a018_Domain_EOB.xlsx'. Error message was 'can't open file for reading'

 

2016-02-22 04:40:44| 221.4| 0.0|ERROR |A fatal error has occurred. Check the logfile above for details

 

2016-02-22 04:40:44| 221.4| 0.0|INFORM|XLSX Reader: Closing dataset '\\\\ktsz003\\groups$\\AVG\\Geoinformation\\Produkte\\GDI\\Themen\\A018 AV\\data\\a018_Domain_EOB.xlsx'...

 

2016-02-22 04:40:44| 221.4| 0.0|ERROR |Error occured while reading feature from table `Joiner_5:Domain' : `A fatal error has occurred. Check the logfile above for details'

 

2016-02-22 04:40:44| 221.4| 0.0|ERROR |A fatal error has occurred. Check the logfile above for details

 

2016-02-22 04:40:49| 221.6| 0.2|ERROR |... Last line repeated 459 times ...

....

2016-02-22 04:53:23| 269.2| 0.0|STATS |=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

2016-02-22 04:53:23| 269.2| 0.0|STATS | Features Written Summary

 

2016-02-22 04:53:23| 269.2| 0.0|STATS |=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

2016-02-22 04:53:23| 269.2| 0.0|STATS |==============================================================================

 

2016-02-22 04:53:23| 269.2| 0.0|STATS |Total Features Written 0

 

2016-02-22 04:53:23| 269.2| 0.0|STATS |=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

2016-02-22 04:53:23| 269.2| 0.0|INFORM|Translation was SUCCESSFUL with 2 warning(s) (0 feature(s) output)

 

2

Best answer by mark2atsafe

Yes, I do find that sometimes we don't stop a translation when we should or that we stop when we shouldn't. Can I suggest you file a case with our support team (safe.com/support) or your local reseller support.

Either we should change this to a WARNing, or - if it stays as an ERROR - we should halt the translation. But we'll probably need a copy of your workspace and source data to be able to replicate the problem

Oh! I'll also mention that there is a parameter in the Navigator window (Workspace Parameters > Advanced > Ignore Failed Readers) that could legitimately cause an error to be ignored. So first check that is not set to Yes before filing a case.

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

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.

3 replies

mark2atsafe
Safer
Forum|alt.badge.img+59
  • mark2atsafeSafer
  • Safer
  • Best Answer
  • February 22, 2016

Yes, I do find that sometimes we don't stop a translation when we should or that we stop when we shouldn't. Can I suggest you file a case with our support team (safe.com/support) or your local reseller support.

Either we should change this to a WARNing, or - if it stays as an ERROR - we should halt the translation. But we'll probably need a copy of your workspace and source data to be able to replicate the problem

Oh! I'll also mention that there is a parameter in the Navigator window (Workspace Parameters > Advanced > Ignore Failed Readers) that could legitimately cause an error to be ignored. So first check that is not set to Yes before filing a case.

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

FME Evangelist to the Rich and Famous!!
J
Forum|alt.badge.img+5
  • julien
  • February 22, 2016

This is a security issue... Error message was 'can't open file for reading'

FME doesn't have an access to read your File. You can ignore your Failed Reader but it's not a good option in batch process.

vki
Contributor
Forum|alt.badge.img+7
  • vkiContributor
  • Author
  • Contributor
  • February 23, 2016

Yes, I do find that sometimes we don't stop a translation when we should or that we stop when we shouldn't. Can I suggest you file a case with our support team (safe.com/support) or your local reseller support.

Either we should change this to a WARNing, or - if it stays as an ERROR - we should halt the translation. But we'll probably need a copy of your workspace and source data to be able to replicate the problem

Oh! I'll also mention that there is a parameter in the Navigator window (Workspace Parameters > Advanced > Ignore Failed Readers) that could legitimately cause an error to be ignored. So first check that is not set to Yes before filing a case.

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

The parameter "ignore failed reader" ist set to No. (The error lies in a Joiner-Transformer that tries to open an Excel-File that doesn't exist)

I'll send the the workbench to the support.

Community Stats

32,154
Posts
122,046
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.