Skip to main content

Hi FME Community,

Has anyone run into this odd issue? FME Workbench 2022.2.1 (FME Python 3.10+).

I did have issues installing transformers from FME Hub within FME Workbench, though it now seems to have resolved itself.

 

(Note: removed sensitive but otherwise inconsequential information)

Initially FME would throw an error similar to: 

An error occurred while installing Python package with 'pip install --force-reinstall --no-deps --no-index --find-links C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python --target C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\python\safe.emailer --upgrade --no-compile fme-emailer' : Process crashed. An error occurred while installing package 'C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer'

Sadly FME isn't more descriptive than this. Feedback for FME Devs: could FME print out the Python traceback when transformer installation fails? This would be immensely helpful in troubleshooting.

 

I tried running the script directly in Command Prompt, which threw this:

C:\WINDOWS\system32>pip install --force-reinstall --no-deps --no-index --find-links C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python --target C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\python\safe.emailer --upgrade --no-compile fme-emailer
ERROR: Invalid requirement: 'Software\\FME\\Packages\\22776-win64\\PackageFiles\\safe.emailer\\python'
Hint: It looks like a path. File 'Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python' does not exist.

Trying to account for spaces in file paths, added "" around the path which threw this:

C:\WINDOWS\system32>pip install --force-reinstall --no-deps --no-index --find-links "C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python" --target "C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\python\safe.emailer" --upgrade --no-compile fme-emailer
Looking in links: c:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python
WARNING: Location 'C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer\python' is ignored: it is either a non-existing path or lacks a specific scheme.
ERROR: Could not find a version that satisfies the requirement fme-emailer (from versions: none)
ERROR: No matching distribution found for fme-emailer

However, I was able to install both these transformers directly through PowerShell. The workaround (ensure FME Workbench is not running):

(Credit to vijays 27/04/2021 here: https://hub.safe.com/publishers/safe/packages/emailer#comments)

PS C:\Program Files\FME> .\fme.exe PACKAGE INSTALL C:\Temp\safe.emailer-3.3.3.fpkg
                FME 2022.2.1.0 (20221202 - Build 22776 - WIN64)
                        FME Database Edition (floating)
                       Temporary License: 190 days left.
                         Machine host name is: <removed>
          Operating System: Microsoft Windows 10 64-bit  (Build 19044)
                 Copyright (c) 1994 - 2022, Safe Software Inc.
                               Safe Software Inc.
 
Installed package 'safe.emailer'
==========================================================================
 Name              : safe.emailer
 Version           : 3.3.3
 Minimum FME Build : 20000
 Author            : Safe Software
 Email             :
 Transformers      :  Emailer]
 Formats           :  ]
 Web Services      : ÂGoogle Gmail.xml, Microsoft Mail.xml]
 Web File Systems  : c]
 Python Packages   : =fme-emailer]
 Install Path      : C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.emailer
 Description       : Sends HTML or plaintext emails via Simple Mail Transfer Protocol (SMTP) or the Gmail API.
 
Translation was SUCCESSFUL
PS C:\Program Files\FME> .\fme.exe PACKAGE INSTALL C:\Temp\safe.geocoder-2.2.4.fpkg
                FME 2022.2.1.0 (20221202 - Build 22776 - WIN64)
                        FME Database Edition (floating)
                       Temporary License: 190 days left.
                         Machine host name is: <removed>
          Operating System: Microsoft Windows 10 64-bit  (Build 19044)
                 Copyright (c) 1994 - 2022, Safe Software Inc.
                               Safe Software Inc.
 
Installed package 'safe.geocoder'
==========================================================================
 Name              : safe.geocoder
 Version           : 2.2.4
 Minimum FME Build : 21746
 Author            : Safe Software
 Email             :
 Transformers      :  Geocoder]
 Formats           :  ]
 Web Services      : r]
 Web File Systems  :  ]
 Python Packages   : ifme-geocoder]
 Install Path      : C:\Users\<user>\AppData\Roaming\Safe Software\FME\Packages\22776-win64\PackageFiles\safe.geocoder
 Description       : Convert addresses to coordinates, or vice versa.
 
Translation was SUCCESSFUL

I can't seem to reproduce the bug now as FME Workbench will install transformers from FME Hub without complaint.

 

Has anyone run into this?

Hello @madeleine_rfs​ 

We have reports of the initial error ("Process crashed") occurring when antivirus or other protection software blocks the installation of FME packages. This may be logged within the antivirus software reported as a "Lockdown exploit". Is there anti-virus software installed on the machine you're using?


Hi @debbiatsafe​!

On further investigation, this is what caused it. It didn't come to mind initially as our anti-virus software doesn't alert the user to actions that it has taken which is why it didn't occur to me to check this (and transformer installation was blocked even with administrative elevation). Our anti-virus software did say it blocked FME from installing the selection in its logs, but didn't flag at the time this action was taken.

 

The workaround above, using PowerShell to install a downloaded transformer, didn't trigger our anti-virus though, so that may help others who are facing this issue. It would also be an option for those in locked down environments where a user with administrative privileges can install a transformer on behalf of an unprivileged user.

 

Many thanks!


Reply