Skip to main content
  • EN

We have hundreds of mappings we execute via command line.  We have implemented standards regarding the use of source, destination, and logging user parms.

We started our 2024 migration and found a bug while trying to pass in our --LOG_FILE parm from the cmnd line (fme ...fmw --LOG_FILE xxx).

The workspace will not execute and throws this error:

ERROR : Unable to open log file `X:\...\FME\X_\...\Log\mapping_name.log'
ERROR : The preceding error has occurred during FME logfile setup

For some reason, in 2024 it is always prefixing the log location with the location of the fme workspace.

The only workaround I found to get the log file to write in our desired location was to eliminate the --LOG_FILE parm and use LOG_FILENAME instead.

I have opened a ticket with Safe and have not heard anything back.  Having to modify hundreds of workspace executions is a show stopper.

 

Hi ​@jbradfor This problem was likely fixed via FMEFORM-32544 in the latest FME 2024.2.2

fme xxx.fmw --DestDataset xxx --LOG_FILE xxx\Log\xxx.log
                FME 2024.2.2.0 (20250114 - Build 24820 - WIN64)
                              FME Form (floating)
 

ERROR : Unable to open log file `workspacelocation\D_\xxx\Log\xxx.log'
ERROR : The preceding error has occurred during FME logfile setup

After updating to the latest build, we are still seeing the error.

Dan instructed to open each workspace again using the latest Build 24820, make a minor change and save.

Reran from the cmnd line.  They are all now accepting the --LOG_FILE user param and logging in the correct spot.

Thanks

Community Stats

31,931
Posts
121,282
Replies
39,553
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.