Limagito File Mover Software Blog and Filemover News

06 Jun
SFTP Connection errors 10054 (0x2746)
Q: SFTP Connection errors 10054 (0x2746). Is there something we can look at in regards to this error? What causes it and if we can resolve? We’ve encountered a situation twice now where a vast amount of rules appear to stop processing to 1 particular server. The rules in web remote all turn green and stay green as if they are currently being triggered, but there is no output on the runtime log and no transfers take place. To resolve the issue we’ve restarted the Limagito server, and rule processing occurs normally again. Are we able to provide you with some logs that might help shed light on what’s occurred?
We have 173 rules, and of the failures they seem to be with this 1 SFTP server, destination and source rules. Is there a preference in which one we use? We scan the rules every 70 seconds.
With our SFTP Source Code Vendor 1 (SB) the error message looks like:
6/3/2022 9:12:57 AM SFTP Connected Error
6/3/2022 9:12:57 AM Connect attempt 1 Exception: Connection lost due to error 10054
6/3/2022 9:12:57 AM Connecting SFTP Server..
6/3/2022 9:12:57 AM Cyclus [SFTPGET]
6/3/2022 9:12:57 AM Start Source Thread
With our SFTP Source Code Vendor 2 (CK) the error message looks like:
A: With 70 seconds scan time we would certainly enable the ‘Stay connected’ option (Common Tab of SFTP setup). We guess this SFTP server is no longer accepting new connections (after x time). Please also check the ‘Hint’ in the feedback when using our SFTP Source Code Vendor 2 (CK). If you trigger the rules often then some SFTP servers will find this (connects/disconnects) suspicious and will no longer allow new connections for a certain time.
SFTP Setup (Source or Destination), enable ‘Stay Connected’.
#SFTP #Filetransfer #Filemanagement
If you need any info about this ‘ SFTP Connection errors’ question, please let us know.
Best regards,
Limagito Team
By Limagito-Team Error SFTP Sftp connection
06 Jun
Verify FTP download using existing hash file at source
Q: I am downloading a file, plus the sha256.hash that was created at the file source via FTP. How can I verify FTP download with an already existing hash file? If the feature exists, I don’t seem to be able to find it. An example file name for my application is 12345.dmp – and the hash file is 12345.dmp.hash
A: In our latest version v2022.6.6.0 we added an option to achieve your request.
Please open your FTP as Source Setup:
Select the Verify Tab:
Enable ‘Use Checksum file at source to verify download’ option
Select the ‘Algorithm’ you used to create the hash file on the FTP server
Select the ‘Encoding’ you used to create the hash file on the FTP server
Set Checksum Filename. Default is %SFN (= Source File Name) + .hash
We will look for that file at the FTP source to verify the download
Select if you want to keep the the checksum file download (move to Destination)
File Filter Setup. In our example we are downloading and checking .pdf files so we added the *.pdf extension to the Filename Include Filter option. Please do not include the hash file extension, this is all handled by the ‘Use Checksum file at source to verify download’ option itself.
RunTime Log Result:
#FTP #Filetransfer #Filemanagement
If you need any info about this ‘ Verify FTP download’ request, please let us know.
Best regards,
Limagito Team
By Limagito-Team FTP checksum, CRC, Verify FTP, Verify FTP download
04 Jun
Execute Command, continuing on error
Q: Execute Command, continuing on error. I have a rule which moves a file from one win folder to another win folder and then runs a CMD against it. If the CMD errors out it keeps retrying the file. How do I move the failed file to another folder on the error and NOT retry it with the command line?
My current setup is:
WIN as Source
Destinations:
WIN
CMD (Execute Command)
A: In our latest version v2022.6.2.0 we added a new ‘Redirect ExitCode to PS Integer Var A (%VIA)’ option. Please check the ‘Advanced Tab’ of the CMD (Command) as Destination. Enable this option to transfer the ExitCode to our Pascal Script Integer Var psVIA. We’ll use the psVIA var to move the source file in case the Command returns a value <> 0 (which normally is an errorcode).
We will need a third ‘Pascal Script’ as Destination.
1) WIN as Destination
2) CMD as Destination
Now please add a third ‘Pascal Script’ Destination. This must be in the last position. Do not forget to adjust the Const ctErrorPath value. This Pascal Script will move the source file to an error path if the ExitCode of the CMD (command) <> 0.
Const ctErrorPath = 'C:\3ProcessError\'; // must end with a / Begin psExitCode:= 1; // ... add your code here If psVIA <> 0 Then Begin psMoveFile(psFilePath + psFileName, ctErrorPath + psFileName); psLogwrite(1, '', 'CMD ExitCode Error, psVIA: ' + IntToStr(psVIA)); End; End.
#Filetransfer #Filemanagement
If you need any info about this ‘continuing on error’ request, please let us know.
Best regards,
Limagito Team
By Limagito-Team Command Pascal Script continuing on error, execute command