Dear Users,
In build v2019.12.29.0 we migrated to another Fork of Pascal Script. The one we were using was giving some issues on x64. The latest bug we received from a user was a Service crash when Pascal Script was trying to do a ‘LoadFromFile(File)’ when the ‘File’ was locked by another application.
Regards,
Limagito Team
Dear users,
A while ago we received the folllowing support question:
“I am having problem transfering a big file. The file is 959MB. We get the following error: Exception Error Control channel transfer error 114690.”
We found out that error 11469 = No data is being transferred via control channel. We asked our FTP code supplier for advice.
“Looks like a timeout-related issue. Error 114690 (SB_FTPS_ERROR_CONTROL_CHANNEL_NO_DATA) is returned if no reply was received from the control channel where it was expected to come in. According to the log, the server does not perform any activity after the file is being sent. I believe there may be a delay between the file is sent to the server and the actual response the server is sending back. This delay may originate, for example, from the server copying the uploaded file from a temporary location to its final destination. The solution is quite straightforward – instead of uploading the file as a whole, upload it in pieces. Please start with splitting the file into 100MB chunks and see how it goes.”
And that is what we did in version ‘v2018.12.27.0’. The Multipart Upload option was added in the ‘File & Directory’ tab of the FTP destination.
So what does this mean. When a source filesize is 500 MiByte or higher then this file will be uploaded in parts (chunks) of 100 MiByte. So not as a whole but in parts. Each part will be appened at the FTP server side. We use the APPE (Append) FTP command to achieve this.
A second option to achieve a multipart upload is using the COMB command (‘Use COMB’ checkbox). Important, not so many FTP servers support the COMB command (non RFC). The source file is send in segments and afterwards the FTP server will combine them when it receives the COMB command. We tested this using the trial version of Titan FTP server.
Even better is when you combine this with the Retry option. So if one of the parts would fail during the FTP upload then it will retry to upload this part again (and not the whole file).
Feedback would be much appreciated,
Happy Holidays,
Limagito Team
https://www.secureblackbox.com/kb/help/ref_err_sslerrorcodes.html
| Copyright www.secureblackbox.com | Value | Possible reason and steps to take | |
| ERROR_SSL_CONNECTION_CANCELLED_BY_USER | 73729 (0x12001) | ||
| ERROR_SSL_TIMEOUT | 73730 (0x12002) | ||
| ERROR_SSL_UNSUPPORTED_MAC_ALGORITHM | 73731 (0x12003) | ||
| ERROR_SSL_UNEXPECTED_MESSAGE | 75777 (0x12801) |
| |
| ERROR_SSL_BAD_RECORD_MAC | 75778 (0x12802) | The peers failed to negotiate a shared key material. Try connecting with different cipher suites one-by-one and check if any of them helps. If neither does, try to use a different protocol version. | |
| ERROR_SSL_DECRYPTION_FAILED | 75779 (0x12803) | ||
| ERROR_SSL_DECODE_ERROR | 75792 (0x12810) | ||
| ERROR_SSL_DECRYPT_ERROR | 75793 (0x12811) | ||
| ERROR_SSL_RECORD_OVERFLOW | 75780 (0x12804) | Packet size too large. Try to decrease the maximal size of the packet by adjusting the MaxFragmentLength extension. | |
| ERROR_SSL_DECOMPRESSION_FAILURE | 75781 (0x12805) | Compression or decompression failure. Switch off compression (CompressionAlgorithms property). | |
| ERROR_SSL_HANDSHAKE_FAILURE | 75782 (0x12806) | Incompatible versions or cipher suite lists. Try to play with version and cipher suite sets. Check that the server certificate is provided and has an associated private key. | |
| ERROR_SSL_ILLEGAL_PARAMETER | 75789 (0x1280D) | ||
| ERROR_SSL_NO_CERTIFICATE | 75783 (0x12807) | The certificate provided by the peer is not valid. | |
| ERROR_SSL_BAD_CERTIFICATE | 75784 (0x12808) | ||
| ERROR_SSL_UNSUPPORTED_CERTIFICATE | 75785 (0x12809) | ||
| ERROR_SSL_CERTIFICATE_REVOKED | 75786 (0x1280A) | ||
| ERROR_SSL_CERTIFICATE_EXPIRED | 75787 (0x1280B) | ||
| ERROR_SSL_CERTIFICATE_UNKNOWN | 75788 (0x1280C) | ||
| ERROR_SSL_UNKNOWN_CA | 75790 (0x1280E) | ||
| ERROR_SSL_ACCESS_DENIED | 75791 (0x1280F) | The requested application-layer resource cannot be accessed by the requestor. Check with the administrator of the remote resource. | |
| ERROR_SSL_EXPORT_RESTRICTION | 75794 (0x12812) | The peer is only configured to use exportable cipher suites. Switch on support for “EXPORT” cipher suites. | |
| ERROR_SSL_PROTOCOL_VERSION | 75795 (0x12813) | The peers have not been able to negotiate a version to use (no shared protocol versions). | |
| ERROR_SSL_INSUFFICIENT_SECURITY | 75796 (0x12814) | The cipher suites mutually supported by the peers are too weak and do not provide an adequate level of security. | |
| ERROR_SSL_INTERNAL_ERROR | 75797 (0x12815) | Contact the vendor. | |
| ERROR_SSL_USER_CANCELED | 75798 (0x12816) | Application layer has shut down the connection. | |
| ERROR_SSL_NO_RENEGOTIATION | 75799 (0x12817) | One of the peers requested a renegotiation, which was refused by the other. Note that you will get this error (as a warning) if you return Allow = false from the OnRenegotiationStart event handler. | |
| ERROR_SSL_CLOSE_NOTIFY | 75800 (0x12818) | Does not indicate an error condition. The SSL connection was closed gracefully and can be restored or cloned in future. | |
| ERROR_SSL_UNKNOWN_PROTOCOL_ERROR | 75801 (0x12819) | ||
Limagito filemover is an automated file mover solution handling everything from moving, deleting to copying files.
Please don’t hesitate to contact us if you have any questions about our product and services.