Skip to main content
Solved

FME Form 2024.2 - Command Line Execution - Log File

jbradfor
Contributor
Forum|alt.badge.img+7

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.

 

Best answer by jbradfor

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

View original
    This post is closed to further activity.
    It may be a question with a best answer, an implemented idea, or just a post needing no comment.
    If you have a follow-up or related question, 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

    DanAtSafe
    Safer
    Forum|alt.badge.img+16
    • DanAtSafeSafer
    • Safer
    • January 31, 2025

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

    jbradfor
    Contributor
    Forum|alt.badge.img+7
    • jbradforContributor
    • Author
    • Contributor
    • February 3, 2025

    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.

    jbradfor
    Contributor
    Forum|alt.badge.img+7
    • jbradforContributor
    • Author
    • Contributor
    • Best Answer
    • February 5, 2025

    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

    Most helpful members this week

    Community Stats

    30,846
    Posts
    116,937
    Replies
    38,670
    Members
    Terms & ConditionsCookie settings

    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
    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.