Skip to main content
Solved

Wrong FME version opens when running FME from command line

  • November 22, 2022
  • 2 replies
  • 62 views
james_c_452
Enthusiast
Forum|alt.badge.img+8

Hi,

 

I'm trying to run an FME process from the command line like I have many times before (fme example.fmw)

 

However, it is opening the wrong version for the workspace. The workspace is in 2022 but the command line is opening 2018 (which is also installed on my computer). Is there a flag or something I could add to my code to ensure it opens 2022? My workspace has newer transformers than 2018 so it crashes everytime I open it

 

I have tried adding it to the system path variable, but this doesn't do anything, unless I'm doing it wrong

 

Thanks

Best answer by virtualcitymatt

Yeah, adding the folder of the fme.exe to the Path Environment is want you want to do - you will also need to make sure the old version is removed from the path too.

Also, after updating the environment variables you'll need to close and open your terminal for the change to take effect.

Alternatively, instead of calling 'fme', you can put the full path to the correct fme.exe version when calling

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.

2 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47
  • virtualcitymattCelebrity
  • Celebrity
  • 2000 replies
  • Best Answer
  • November 22, 2022

Yeah, adding the folder of the fme.exe to the Path Environment is want you want to do - you will also need to make sure the old version is removed from the path too.

Also, after updating the environment variables you'll need to close and open your terminal for the change to take effect.

Alternatively, instead of calling 'fme', you can put the full path to the correct fme.exe version when calling

james_c_452
Enthusiast
Forum|alt.badge.img+8
  • james_c_452Enthusiast
  • Author
  • Enthusiast
  • 63 replies
  • November 24, 2022

Thanks @virtualcitymatt​ ! Looks like I was just setting the path attribute slightly wrong in the windows environment variables

Community Stats

32,066
Posts
121,744
Replies
39,692
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.