October 2024 - File transfer tool from Limagito

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:
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!
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 max path, max_path, maxpath, too long
20 Oct
How to verify the pgp signature during decryption
How to verify the pgp signature during decryption
Q: I use PGP decryption in some rules and I need to activate the signature checking. Can you tell me if this is available and how to do it ?
A: We added this option in v2024.10.19.0
PGP Decryption, Added Verify Signature option (v2024.10.19.0) [+]
We added some screenshots in this blog article to get you started.
We used a Windows Folder as Destination:
We enabled ‘Enable Encrypt – Decrypt’ and selected ‘Decrypt Files’. As Encryption Algorithm we chose ‘PGP (Pretty Good Privacy)’.
Under the PGP tab we:
Added our Private Key file (and password) to decrypt the received files. The files we received were encrypted by a third party using our corresponding public key.
Added the Public Key file we received, from this third party, to check the signature. The files we received were signed by the third party using their private key file.
Enabled the ‘Verify Signature (Decryption)’ option.
Important: When ‘Verify Signature’ is enabled then all files must have a valid signature. Also files without a signature will not be allowed (error).
RunTime log example of files with an invalid signature:
If you need any help with this “verify the pgp signature” question, please let us know.
Best Regards,
Limagito Team
#pgp #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team PGP
18 Oct
How to send files to Azure using limagito file mover
How to send files to Azure using limagito file mover
Q: We are trying to send files to Azure. This is the first time we are connecting to Azure and need help. We have page blobs selected and are getting the error messages below, when hitting the “Connect” button in the setup.
10/17/2024 9:48:55 AM Container Exists Exception Error: Connection failed due to error 96260
10/17/2024 9:50:31 AM Connect AZURE, ContainerName Exception: Connection failed due to error 96260
10/17/2024 9:50:46 AM Container Exists Exception Error: Connection failed due to error 96260
A: We had a remote meeting with the customer and agreed that we would send him the working setup of our test system.
Destination setup, AZURE as Destination
We asked the customer to check the AccountName he was using (it looked a bit strange to us), only the first part is needed without core.windows.net
We used a container named “pageblob”:
Default File and Directory setup:
Default Common setup:
In case your account is not allowed to check if a container exists then enable “Do not check is Container exists”.
If you need more logging information, enable “Add Control Information to Log”.
RunTime Log result:
Feedback customer:
Thanks for your help today. I believe we have all the settings correctly in place on Limagito. We determine I didn’t truncate our account name correctly. Once I fixed that, it started to work.
If you need any help with this “send files to Azure” question, please let us know.
Best Regards,
Limagito Team
#azure #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Azure send files to azure