Skip to main content
Solved

CenterlineReplacer - Error Not Installed

  • November 18, 2024
  • 3 replies
  • 108 views

tiztrain
Contributor
Forum|alt.badge.img+6

Hey all,

So I upgraded FME Desktop to 2024.1 (through ArcGIS Pro installation) and opened up an exisitng workspace I had created in a previous version. When it opens I get the message stating:

Transformers are used that are not installed: 'CenterlineReplacer (version 6)'

https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Transformers/Transformers/centerlinereplacer.htm

Why is this happening? I have no option to upgrade the existing transformer and it disappears from my workbench and when I try to search to add another ‘CenterlineReplace’ transformer, it is missing from the list.

I have ran a repair on the installation but it is still missing.

Best answer by tiztrain

Esri have confirmed it is a bug and will be addressed in a future release.

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.

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+62

Not sure what the issue you have is, but when I open a fresh workspace in 2024.1 (build 24612 to be exact) I can insert a new CenterlineReplacer so it is not deprecated.


tiztrain
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • November 19, 2024

Not sure what the issue you have is, but when I open a fresh workspace in 2024.1 (build 24612 to be exact) I can insert a new CenterlineReplacer so it is not deprecated.

Damn. Tried uninstalling and reinstalling the application too and still same issue. Will contact Esri support to see if it is an issue with their Data Interoperability Extension


tiztrain
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • Best Answer
  • November 25, 2024

Esri have confirmed it is a bug and will be addressed in a future release.