FFAStrans forum

Hi emcodem
Thanks for your explanation.
Let me inform you that since the configuration change (hostname instead of fqdn) all monitors are picking up the files normally.

Hi emcodem
What do you mean by “cannot reproduce”?
Does it mean, that you are able to process mons JSONs with UNC longer than 260 chars in your enviroment?
Does autoit support long paths?

Yes I have used hostname instead of FQDN which saved 22 chars.
If I may I would recommend trimm of the source filename when constructing the mons json filename

Hi admin I have finally identified the root cause ... the problem is not the actual length of the filename, but the length of the unc path of the json file created by the monitor node, exceeding 259 chars. Example: file dropped to watchfolder: 12345678901234567890123456789012345678901234567890123456...

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

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?

@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...

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

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 reaso...