maxpath

  • 20 Oct

    Problem copying a file due to a folder tree that is too long

    Problem copying a file due to a folder tree that is too long

    Q: I’m contacting you because we’re experiencing a problem when retrieving and copying a file stored on AWS (bucket) via LimagitoX v2023.5.12.0 (screenshot attached). The problem seems to be linked to the length of the folder tree containing the file. In fact, when we test with a shorter tree path, the file is copied successfully. Unfortunately, according to AWS, it is not possible to modify the path length of the tree structure.

    To give you more information on the problem, I’ve attached two log files:

    • Log_OK_SrvLimagitoX.Ruleld : short tree path with which the copy works.
    • Log_KO_SrvLimagitoX.Ruleld: tree path imposed by AWS that generates the error (which doesn’t work).

    A: We found some renaming errors in the log file.

    2024-04-26 15:26:18 AMS_BI_AMAZON_TEST_S3_VGO [AWSS3GET] Rename Exception Error: Rename C:\Users\Admin_Limagito\AppData\Local\Temp\LimagitoX\LimagitoX.740\aps-download-publisher-11111111-5ce6-49d8-8037-111111111\versionId=c36c10e4-d59c-4f20-82f4-111111111111\executionDate=20240426\part-00000-111111111111111111111111111111111111.c000.csv.tmpdwnld To C:\Users\Admin_Limagito\AppData\Local\Temp\LimagitoX\LimagitoX.740\aps-download-publisher-11111111-5ce6-49d8-8037-111111111111\versionId=c36c10e4-d59c-4f20-82f4-111111111111\executionDate=20240426\part-00000-111111111111111111111111111111111111.c000.csv Error

    When downloading files from AWSS3, we first store the stream of data we are downloading locally on the system. The same counts for all non-Windows folders as source, like AZURE, SFTP, FTP, … . During the download, the file has a temporary extension (.tmpdwnld). After a successful download, the file will be renamed to its original extension. The problem here is that Windows doesn’t like very long path + filenames, please check: link.

    Solution: Please update to the latest build first (v2024.10.17.0 or higher)
    • Could you please open the Advanced option of this AWSS3 Rule:

    limagito filemover advanced rule options

    • Please add  \\%\  as prefix to your ‘Temporary Directory’ setup. Please, always keep the temporary folder on the local system where the file mover is installed!

    limagito file mover folder tree that is too long

    If you need any help with this “folder tree that is too long” question, please let us know.

    Best Regards,

    Limagito Team

    #managedfiletransfer #filetransfer #filemanagement

    By Limagito-Team Error , , ,
  • 25 Apr

    Q&A 22: Can I use filenames longer than 256 characters

    We received the following information from Joe, a new Limagito vXI user.

    Your program copies from sources longer than 256 characters, and destinations longer than 256 characters.

    Just have to put \\?\ at the beginning of the path for local drives and \\?\UNC\ for network drives.

     

    Some examples:

    • Local Drive folder
      • C:\PathThatIsVeryLong\ => \\?\C:\PathThatIsVeryLong\
    • Network Drive Folder:
      • \\ServerName\PathThatIsVeryLong\ => \\?\UNC\ServerName\PathThatIsVeryLong\
      • For a share folder (\\ServerName\PathThatIsVeryLong\), we could use \\?\UNC\ServerName\PathThatIsVeryLong\ where “ServerName” is the name of the computer and “PathThatIsVeryLong” is the name of the shared folder.

    More information: msdn.microsoft.com

    For more recent OS versions we found the following:
    How to make windows accept file paths over 260 characters

    Regards,

    Limagito Team

SEARCH