2024 - Page 2 of 19 - File transfer tool from Limagito

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
18 Oct
The x-amz-content-sha256 header does not match what was computed
The provided x-amz-content-sha256 header does not match what was computed
Q: I was able to setup a non aws s3 (wasabi) as source but I’m not able to do so as destination. Is it possible to have some help?
A: The customer was using an older version so we first asked him to update his version. We created a new build with extra logging information for AWS as Destination (v2024.10.14.0 or higher).
<Error><Code>XAmzContentSHA256Mismatch</Code><Message>The provided 'x-amz-content-sha256' header does not match what was computed.</Message><ClientComputedContentSHA256>8AFBD736EC2917807F5FF5D8A9018846AA9D6B25EC839506DACE0D588DE491C5</ClientComputedContentSHA256><S3ComputedContentSHA256>8afbd736ec2917807f5ff5d8a9018846aa9d6b25ec839506dace0d588de491c5</S3ComputedContentSHA256><RequestId>1CF8F37CAA85D906:A</RequestId><HostId>KKwBla460dUwWRytyBUsvPQBw/z9QNkAg8mFuYQtBNOUHDXQhPG1vYAHfC5djS/fwa0VH2J0qIHx</HostId><CMReferenceId>MTcyODkyMjIzMDgxOCAxMzAuMTE3LjE4NS4xMDIgQ29uSUQ6ODA5NDI1OTAwL0VuZ2luZUNvbklEOjc5MDkwODgvQ29yZTo0Ng==</CMReferenceId></Error>
We found out that Wasabi was expecting the lowercase of the sha256 hash. This was adjusted in version v2024.10.17.0 and since this version we are using the lowercase of the sha256 hash.
If you need any help with this question, please let us know.
Best Regards,
Limagito Team
#awss3 #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team AWS S3 wasabi, x-amz-content-sha256
12 Oct
Excel as destination losing some rows of data when converting from csv
Excel as destination losing some rows of data when converting from csv
Q: We are running LimagitoX File Mover v2024.1.20.0 and noticed an issue with the Excel destination. It appears to be losing some rows of data starting after line 45. You can replicate this issue by creating a simple rule that uses the attached test_file.txt file as the source and set the destination as Excel with the options in the images below. Note that the text input file has 101 rows, and the Excel output file only has 57. We are still seeing this issue with version 2024.8.26.0. Didn’t want it to fall off your radar.
A: We added the following Pascal Script which will convert your source Ansi csv file to Unicode.
Open our Pascal Script option:
Enable and Add the following ‘On Destination’ Pascal Script:
Begin psExitCode:= 1; // ... add your code here psChangeTxtEncoding(psFilePath + psFileName, psFilePath + psFileName, 2); End.
This will adjust the source txt file so if you don’t want this, add an extra Rule where you use a copy of the original file.
Feedback Customer: That fixed it. Thank you!
If you need any help with this ‘send an email when a file is successfully transferred’ request, please let us know.
Best Regards,
Limagito Team
#xls #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team XLS/CSV excel, losing rows, xls