Long Filenames

[bradysvbc]

I've been able to track down an issue with long files names not being picked up by workflows.

It my instance, it was filenames longer than 40 characters. File names shorter will pass in the same folder.. Just longer names would not be picked up by the watch processor. Did some testing..

I changed the workflow to use drive mappings. IE: W:\Input_Folder name.

This still did not work. Longer files would not be processed.

I then changed the workflow back to the full UNC path, but I launched the FFAStrans executable using a drive map instead of the UNC path.. IE: S:\FFAStrans\

It worked!

Looking though the logs, I can see the json files being appended in really long names in the UNC paths.. Is this part of the problem?

Machines tested on were Windows Server 2019 with the GPO enabled to allow long filenames and registry set to allow as well, and rebooted the machines to make sure it would take effect.

Again, thanks for this great software. Just wanted to bring attention to this if there was a way to shorten things in the backend or if this helps someone else!

[admin]

Hi bradysvbc, thank you for using FFAStrans and welcome to the forum!

FFAStrans has been very well tested with picking up very long names, UNC and mapped drives. Basically, if you can access the file in explorer, FFAStrans should be able to pick it up. But usually the FFAStrans installation itself resides on a much shorter path and is not tested as extensively when the installation itself resides on a long path. So that might probably be a bug. I will take a look at that.
Thanks for reporting!

-steinar