Skip to main content
Question

TempPathNameCreator missing rights to create temp folder

  • July 16, 2026
  • 3 replies
  • 99 views
koenterralytics
Supporter
Forum|alt.badge.img+11

Since a few days two of my FME hub transformers return the error below. I think it mentions that it is not possible to create a folder any more using the TempPathnameCreator. This might be resolved by updating the transformer to the latest version, but this also means that the transformers on FME hub cannot be used on old(er) versions any more. 

In another recent ticket in contact with Safe, I experienced something similar. Because of the security-changes for Flow several workspaces do not work any more. So I'm pretty sure many people will have similar issues. How can this be fixed without having to update all transformers to the latest version (and making it impossible to use them with older versions)?

2026-07-15 13:08:16|   0.0|  0.0|ERROR |@Tcl2 -- failed to evaluate expression `set sampleTempFile [FME_TempFilename]; set ourTempDir {}; append ourTempDir $sampleTempFile {_d}; file mkdir $ourTempDir; set env(InlineGeoJSON_TempPathnameCreator_6e0c2906_d797_4636_928a_fa984000ecc45_dir) $ourTempDir; set env(InlineGeoJSON_TempPathnameCreator_6e0c2906_d797_4636_928a_fa984000ecc45_file) $sampleTempFile; set gNumTempFilesHandedOut 0;' -- not allowed to invoke subcommand mkdir of file

The transformers I'm talking about:

https://hub.safe.com/publishers/terralytics/transformers/inlinegeojson

https://hub.safe.com/publishers/terralytics/transformers/leafletvectormap

    3 replies

    siennaatsafe
    Safer
    Forum|alt.badge.img+12

    Hi ​@koenterralytics,
     

    Thanks for the detailed write-up and for contributing the Hub and the community. This matches what we've seen elsewhere too.
     

    We did some security hardening, which is why TempPathnameCreator started failing on workspaces that were previously working fine. Updating the transformer to the latest version is indeed the only fix for this.

    With versioning on the Hub, if you are using a linked transformer, you can create a new version that works in 2026.2+, while the older versions will continue to work for those without the security hardening.

    I can see that your custom transformer are embedded so I understand, this is not helpful for you at the moment, but I did want to raise it as an option for the future. At least with the embedded version, the user can easily edit the transformer themselves. We will be releasing an article shortly that will walk through the steps of editing a custom transformer to help users if they do encounter issues with custom transformers due this security hardening. 
     

    I'd like to apologize for the issues this has caused you. I understand that breaking changes cause real pain for our users, who rely on our product to keep their critical processes running. We do our best to avoid this, but in this case it was decided that breaking older versions of a transformer was worth it to improve security.

    koenterralytics
    Supporter
    Forum|alt.badge.img+11

    Hi ​@siennaatsafe. Thanks for your answer. Is is an option to also add versioning for embedded transformers? I always try to avoid linked transformers since they have quite some disadvantages.

    siennaatsafe
    Safer
    Forum|alt.badge.img+12

    Hi ​@koenterralytics, 

    Since the transformer is embedded, it can’t be versioned the same way a linked transformer can. This discussion gets more into the details: 

     

    Community Stats

    32,749
    Posts
    124,194
    Replies
    41,251
    Members
    Terms & ConditionsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.