Skip to main content
Solved

Wrong FME version opens when running FME from command line

  • November 22, 2022
  • 2 replies
  • 52 views

james_c_452
Supporter
Forum|alt.badge.img+7

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

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

2 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+39
  • Celebrity
  • 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
Supporter
Forum|alt.badge.img+7
  • Author
  • Supporter
  • November 24, 2022

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


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