Skip to main content
Solved

Quick Translator Log window not displaying detail

  • February 13, 2018
  • 7 replies
  • 26 views

johnt
Contributor
Forum|alt.badge.img+11
  • Contributor

Hi,

 

I have two password protected workbenches (one to run, that runs another through workspace runner). People can use the Quick Translator to run them. After some development work, the Quick Translator no longer displays logging info (sometimes it does). Instead, It says "Reading file" for the duration, and then either doesn't finish properly (no output file) with window entry of "Translation finished", or finished successfully with the same entry, and sometimes with "Translation Successful", in between (the actual logs are collecting info though). Before the development work, it provided all the usual logging info all the time (except for another time when I had this is issue, but it went away).

Hope I'm missing something simple. But is there an explanation for this?

Thanks, John

Best answer by fmelizard

Hi @johnt Please try FME 2017 or even 2018.0 beta. If the problem still exists then please send details to www.safe.com/support Thanks!

View original
Did this help you find an answer to your question?

7 replies

johnt
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • February 13, 2018
Should add that this with FME 2015.1.1.0 32 bit on Windows Server 2008 R2 Enterprise

 

 


johnt
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • February 13, 2018

 

Ok, further development. Investigation of the worker workbench log reveals it sometimes fails when writing the excel report (larger data only) at the end and is the result of a "child killed: segmentation violation" ??? Sounds serious. I changed to csv and no more of that (the reason for it failing occassionally - see above). Still runs with no log info most times though in the quick translator window, so that is not resolved.

fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • Best Answer
  • February 16, 2018

Hi @johnt Please try FME 2017 or even 2018.0 beta. If the problem still exists then please send details to www.safe.com/support Thanks!


johnt
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • February 16, 2018
fmelizard wrote:

Hi @johnt Please try FME 2017 or even 2018.0 beta. If the problem still exists then please send details to www.safe.com/support Thanks!

 

Hi @DanAtSafe, thanks for the response. I am tempted to try this and revise the workbenches for 2017, just need to find the time. But I'll report back once I've had the opportunity. I guess this isn't a known 2015 issue then.

 


johnt
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • April 16, 2018
fmelizard wrote:

Hi @johnt Please try FME 2017 or even 2018.0 beta. If the problem still exists then please send details to www.safe.com/support Thanks!

Hi @DanAtSafe, so I moved the workspace to 2017.0.1.1 and now the log is displayed all the time. I wonder though, as it is password protected, should it be displaying all the transformers that are being used etc. I would expect it to either run as above with no information, or basic info to cover the running of the process? Cheers

 

 


fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • April 16, 2018
johnt wrote:
Hi @DanAtSafe, so I moved the workspace to 2017.0.1.1 and now the log is displayed all the time. I wonder though, as it is password protected, should it be displaying all the transformers that are being used etc. I would expect it to either run as above with no information, or basic info to cover the running of the process? Cheers

 

 

Hi @johnt You can't edit or view a workspace that's password protected but it can still be run from the command line or Quick Translator which will always produce a log file. The log file shouldn't display any passwords set within the workspace.

johnt
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • April 16, 2018

Hi @DanAtSafe, thanks for the clarity.


Reply


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