Skip to main content
Question

Transformer requires build XXX


dbryantgeo
Contributor
Forum|alt.badge.img+7

I am attempted to add the FMEServerEmailGenerator to a workbench on build number 17291, however I receive an error stating that I must upgrade to 177725 to use the transformer.

I know this sounds pretty obvious, but another workbench on the same build number (17291) does not prompt me to upgrade.

What might be causing this conflict?

4 replies

redgeographics
Celebrity
Forum|alt.badge.img+50
So for clarification: you're also trying to add the FMEServerEmailGenerator in the 2nd workspace?

 

 


dbryantgeo
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • July 12, 2018
redgeographics wrote:
So for clarification: you're also trying to add the FMEServerEmailGenerator in the 2nd workspace?

 

 

Yes, attempting to add the generator to both workspaces, one successfully and the other not so.

 

 


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • July 12, 2018
What happens if you copy the FMEServerEmailGenerator from the workspace that works to the one that doesn't, rather than accessing ti directly from the hub?

 

 


rylanatsafe
Safer
Forum|alt.badge.img+13

Hi @dbryantgeo – you might try clearing the location where FME Hub/Store downloaded items appear, and reopening FME Workbench. The FMEServerEmailGenerator is a custom transformer and perhaps there is some sort of conflict.

 

macOS: ~/Library/Caches/Safe Software/FME/FME Store/

 

Windows: ~\\AppData\\Roaming\\Safe Software\\FME\\FME Store\\

 

 

If that does not work – try removing all instances of the FMEServerEmailGenerator from the workspace (after making a backup of it!) and then re-add it. When you have an embedded custom transformer in the workspace, FME will load that version of it – could be some odd corruption.

Hope that helps! The suggestions in the comments directly under your post might be helpful too.


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