FME Version
Summary Table | |
---|---|
Known Issue ID |
FMESERVER-15940 |
Discovered |
2020.2 Build 20787 |
Resolved | 2020.2 Build 20809 |
Symptom
In earlier versions of FME Server 2020.2, workspaces with linked custom transformers will fail if the custom transformer is in the repository or workspace folder. This was fixed in FME Server 2020.2 build 20809.
Cause
The issue occurs because when a transformer is uploaded it’s placed in the following folder:
<REPOSITORY_HOME>\<repository>\fmeresources\Transformers\<TransformerName>\<TransformerName>.fmx
>However, in FME Server 2020.2, it is searching for the custom transformer in this folder instead: <REPOSITORY_HOME>\<repository>\fmeresources\Transformers
<REPOSITORY_HOME> should be C:\ProgramData\Safe Software\FME Server\repositories unless otherwise specified.
Resolution
Recommended Workaround
Upload the custom transformer to a shared resource folder. All resources published with the workspace will be available to all other workspaces run from FME Server, from any repository. Transformers should be uploaded to Resources > Engines > Transformers
Alternative Workaround
If you cannot upgrade and don’t want to use the recommended workaround, you can copy the .fmx file to these folders in each repository <REPOSITORY_HOME>\<repository>\fmeresources\Transformers
If you do decide to use this workaround there are a few things to consider:
-
When you do upgrade your FME Server it will start looking in those subfolders again so you should make sure a copy is still saved in the subfolder.
-
If you are updating your custom transformers, make sure that you do the normal upload process using workbench and then copy that version to this path: <REPOSITORY_HOME>\<repository>\fmeresources\Transformers. If you don't do this when you upgrade you could be running the wrong version of the transformer
Once you do upgrade, we recommend deleting all custom transformers in that base Transformers folder i.e.<REPOSITORY_HOME>\<repository>\fmeresources\Transformers to avoid any confusion.
Comments
0 comments
Please sign in to leave a comment.