FFAStrans forum

Hi @emcodem and @admin
I'm facing similar or maybe identical issue. I've found out, that it is related to filename or complete UNC path length:
- if the filename is too long, the json created by monitor node, contains CR LF and such file is not processed by following nodes
- if the filename is reasonable short, the json created by monitor node, does not contain CR LF and such file is processed normally
See sample files attached

Hey @Silicon

not sure if these issues are connected. I tried to reproduce yours but using 1.4.1 all seems to work normally.
Looking at the code, it seems that we write the formatted json (with \r\n\) only in the phase when the file has not been processed yet, so it makes sense what you see but it does not deliver hints about why the file has not been processed.

Currently i have no feeling about whats happening to you, where did you find the jsons, in the /i subfolder or directly, is it always reproduceable with "long" (its actually not really long is it) filenames?

Hi @emcodem

I have found the json files in mons\guid folder not in .\i subfolder.

I'm afraid it can be (once again) related to the regional settings of Windows Server 2022

@Silicon
i did set up a VM with the OS and settings you provided but still not able to reproduce it unfortunately. Worked with the current release version 1.4.1 as downloaded from ffastrans.com...
There must be more about it than just the filenames. Are you able to reproduce the issue when you place a 0kb file with specified "bad" name in the watch? Whats your exact monitor settings? Does it also happen when you use e.g. \\localhost\c$\temp\longfoldername\longfilename ?

@emcodem
I've got answers to few of your questions:
1) by dropping 0kb file with "long" filename 4636472_68c72bd169774e9a86cb0d697ba6cfd0_74c5be04b0504613928112ab531bc5ee.mp4 the result is identical ... file is ignored
2) as for monitor setting see the screenshot (I can PM to you the whole workflow if you want ... it is processing the MP4 files from AP agency) 3) it happens also when using \\localhost\c$\

Thanks @Silicon can you please post the exact ffastrans version you have?

HI dev team.
I'mm still facing the issue reported earlier - FFAStrans is not abke to process the files with filenames "too long", when too long means longer then 55. chars (without file ext).
Any advice? Anyone?

Worth to mention, that it is working normally on Windows 10

Hi Silicon,

In general FFAStrans should not have a problem with long file paths. It's many years ago we added support for dealing with long paths and filenames. However, it might be you have something in your flow that provoke some edge case bug in ffastrans.
If you make a new workflow and just add a Monitor node with just your path with long file name, will it pick up the files? If not, you need to provide som details about your file structure so we can see if there are some other not yet taken care of edge case. And of course, if your workflow fails with long file names we need job logs.

-steinar