Skip to main content
Question

FME Form 2025.1 crashing when I try to open AttributeRenamer properties

  • February 6, 2026
  • 4 replies
  • 32 views

alexmotta
Participant
Forum|alt.badge.img+4

Whenever I try to open the AttributeRenamer transform properties, FME Form crashes.

 

It doesnt matter if it is an existing workflow or if I start a new one woth nothing but only one AttributeRenamer.

 

Any thoughts, anyone?

 

The screenshot below if from FME Academy:

 

But it also happens on an otherwise empty workflow:
 

 

4 replies

david_r
Celebrity
  • February 6, 2026

That is a very strange issue. 

In the second screenshot you have a BulkAttributeRenamer rather than an AttributeRenamer. Does both cause this problem?

What about the AttributeManager, does that work? It can fully replace the AttributeRenamer, at least.

Which OS are you on? Is the OS updated with all the latest patches? It could be that the issue is with the graphics driver, make sure it’s updated.


alexmotta
Participant
Forum|alt.badge.img+4
  • Author
  • Participant
  • February 6, 2026

Yes, it happened to both renamers. If fact, it just crashed when I tried to add a new AttributeRenamer to the workflow above using the menu that opens when you type AttributeRenamer on the canvas.

 

 

 

And thank you!

 


alexmotta
Participant
Forum|alt.badge.img+4
  • Author
  • Participant
  • February 6, 2026

The crash just happened when I tried to open the AttributeCopier.

No clue why, but I guess it is not a unique transformer problem.


desiree_at_safe
Safer
Forum|alt.badge.img+18

Hi ​@alexmotta! In your Windows Event Viewer, would you be able to track down the Application crash details? It would be helpful (for the community too) to know what the faulting module DLL is!

I also, see you've already submitted a case with us which is perfect! If you haven't already, please send over the HTML report outlined in this General Troubleshooting | Gathering System Information Article. 

Since this report contains detailed system information, it's best to attach it directly to your existing support case rather than posting it here publicly. This will help us investigate further!😊

FYI for other users, you can submit a new case using this link: submit a ticket