Skip to main content

Hi,

I need to set log file path as a parameter. So I ‘ve added User parameter LogFile and linked it to log file in

Navigator-Workspace Parameters-Logging

I’m running my workflow as follows:

"C:\Program Files\FME2\fme.exe" C:\FME\mz\WybranaSiecPomDgn2k.fmw --LogFile "c:\Folder1\File.log"

The problem is, that “c:\Folder1” folder does not exists, and the following error appears:

“Unable to open log file `c:\Folder\File.log'. The preceding error has occurred during FME logfile setup
Program Terminating”

I was trying to create “c:\Folder1” folder using Scripting-Startup Python Script, but it doesn’t help, probably because FME tries to create log file before Python script execution.

There is an open improvement suggestion for this

Didn’t realise it was 8 years old! Surely this can’t be that hard to implement…..

@siennaatsafe can we grease the wheels on this? 😅


Hi ​@hkingsbury,

I’ve raised this suggestion with our product management team, and I can confirm that it’s on their radar. While it’s not currently scheduled for development in the next three months, it remains under consideration as we plan future updates.


Hi ​@hkingsbury,

I’ve raised this suggestion with our product management team, and I can confirm that it’s on their radar. While it’s not currently scheduled for development in the next three months, it remains under consideration as we plan future updates.

Thank you!! 🤗


Is there any workaround for this issue? I mean, how to tell FME, where log file should be stored?


Is there any workaround for this issue? I mean, how to tell FME, where log file should be stored?

As long as the folder where the logs should be written to exists you can simply specify it in the Navigator as shown in the top post. If I understand it correctly, their problem was that that folder didn’t exist yet when FME tried to create the logfile.


Reply