Filter:
Submit Search

Messages and limitations of the FTP connector

Message code list of FTP category

The following message codes correspond to errors that occur in FTP Connector.

 

FTP0000E

This message code is output when an undefined error occurs.

Cause

Solution

An undefined error occurred.

Check the error message or the help of the operation in which the error has occurred.

Corresponding error

  • None

 

FTP0001E

This message code is output when it can't connect to the specified host or HTTP proxy host.

Cause

Solution

Can't connect to the host of Host name or HTTP proxy host of the connection resource.

Check the settings of the connection resource.

Corresponding error

  • java.net.UnknownHostException

 

FTP0002E

This message code is output when the private key file format is invalid or the private key passphrase is incorrect.

Cause

Solution

Either the format of Private key specified in the connection resource or the entered Private key passphrase is invalid.

Check whether the Private key file with valid format is specified and Private key passphrase is valid.

Corresponding error

  • InvalidPrivateKeyException

 

FTP0003E

This message code is output when the client certificate format is invalid or the certificate passphrase is incorrect.

Cause

Solution

Either the format of Client certificate specified in the connection resource or the entered Certificate passphrase is invalid.

Check whether the Client certificate file with valid format (PEM format) is specified and Certificate passphrase is valid.

Corresponding error

  • InvalidCertificateException

 

FTP0004E

This message code is output when the client certificate has expired.

Cause

Solution

The client certificate specified in the connection resource has expired.

Specify a client certificate that is still valid.

Corresponding error

  • com.enterprisedt.net.puretls.SSLCaughtAlertException

 

FTP0005E

This message code is output when authenticity of the server certificate can't be verified.

Cause

Solution

This error might occur when FTP over SSL/TLS connection is specified in the connection resource, and Do not check server certificate isn't selected.

The cause is that authenticity of the server certificate couldn't be verified, because the server certificate registered in Java doesn't match with the one to perform SSL/TLS connection.

Check whether the server certificate to perform SSL/TLS connection is registered in Java.

When registered, check whether the destination server is the same as the one registered in Java and the server certificate of destination isn't expired.

Corresponding error

  • javax.net.ssl.SSLHandshakeException

 

FTP0006E

This message code is output when failed to connect with FTP over SSL/TLS.

Cause

Solution

This occurs when failed to connect with FTP over SSL/TLS.

Check whether the server connection information such as SSL/TLS connection type is configured correctly in the connection resource.

Corresponding error

  • com.enterprisedt.net.puretls.SSLPrematureCloseException

 

FTP0007E

This message code is output when the FTP server has returned some error.

Cause

Solution

This is an exception thrown when FTP server returns some error.

Check the contents of the message.

Corresponding error

  • FTPException

  • com.enterprisedt.net.ftp.FTPException

 

FTP0008E

This message code is output when a connection can't be made to the FTP server.

Cause

Solution

This is an exception thrown when a connection can't be made to the FTP server.

Check whether the port number is correct and the FTP server is running.

Corresponding error

  • java.net.ConnectException

 

FTP0009E

This message code is output when failed to parse remote file list.

Cause

Solution

Failed to parse the remote file list.

Check the settings such as Encoding selected in Destination and the settings of the FTP server.

Corresponding error

  • RemoteFileListParseException

 

FTP0010E

This message code is output when the path on FTP server doesn't start with "/".

Cause

Solution

The path on FTP server doesn't start with "/".

Enter the absolute path starting with "/" for path on FTP server.

Corresponding error

  • MalformedRemotePathException

 

Exception messages of FTP category

Exception name

Cause

Solution

com.enterprisedt.net.ftp.FTPException

This is an exception thrown when FTP server returns some error.

Check the contents of the message.

com.enterprisedt.net.puretls.SSLCaughtAlertException

Expired certificate at handshake state SSL_HT_FINISHED or SSL_HS_WAIT_FOR_CHANGE_CIPHER_SPECS

The client certificate has expired.

Specify a client certificate that is still valid.

com.enterprisedt.net.puretls.SSLPrematureCloseException

Short read

This occurs when failed to connect with FTP over SSL/TLS.

Check whether the server connection information such as SSL/TLS connection type is configured correctly.

FTPException

This is an exception thrown when FTP server returns some error.

Check the contents of the message.

InvalidCertificateException

Failed to load the client certificate. Check the file format or the passphrase.

Either the format of specified Client certificate or the entered Certificate passphrase is invalid.

Check whether the Client certificate file with valid format (PEM format) is specified and Certificate passphrase is valid.

InvalidPrivateKeyException

Private key file or private key pass phrase is invalid.

Either the format of the specified Private key or the entered Private key passphrase is invalid.

Check whether the Private key file with valid format is specified and Private key passphrase is valid.

InvalidPropertyConfigurationException

<Property name> is not entered.

<Property name> isn't specified.

Enter <property name>.

java.io.FileNotFoundException

The path specified in Local path doesn't exist.

Check Local path.

java.io.IOException

Proxy tunnel setup failed: <HTTP error message>

This error occurs if you select Use the HTTP proxy server when you perform SFTP connection.

Check whether Host name or Port number is configured correctly.

java.io.UnsupportedEncodingException

<encoding>

Unsupported encoding is entered in Encoding.

Select or enter an encoding that is supported in Java SE Runtime Environment 8.

= Remarks =

For details, refer to "Supported Encodings" (http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html).

java.net.ConnectException

This is an exception thrown when a connection can't be made to the FTP server.

Check whether the port number is correct and the FTP server is running.

java.net.UnknownHostException

The host "<host name>" is not found.

Unable to connect to Host name.

Check the settings.

java.net.UnknownHostException

This is an exception thrown when the specified FTP server isn't found.

Check the FTP server settings.

javax.net.ssl.SSLHandshakeException

The authenticity of server certificate cannot be verified.

This error occurs if Do not check server certificate isn't selected when you perform FTP over SSL/TLS connection.

Check whether the server certificate to perform SSL/TLS connection is registered in Java. When registered, check whether the destination server is the same as the one registered in Java and the server certificate of destination isn't expired.

MalformedRemotePathException

The path after renaming is invalid. Enter the path after renaming with an absolute path starting with "/".

After renaming doesn't start with "/".

Enter After renaming with an absolute path starting with "/".

MalformedRemotePathException

The path before renaming is invalid. Enter the path before renaming with an absolute path starting with "/".

Before renaming doesn't start with "/".

Enter Before renaming with an absolute path starting with "/".

RemoteFileListParseException

Failed to parse the remote file list. The encoding may be incorrect.

Failed to parse the remote file list.

Check the settings such as Encoding selected in Destination and the settings of the FTP server.

ResourceNotFoundException

Resource definition is not found. Name: []

Destination isn't specified.

Specify Destination.

ResourceNotFoundException

Resource definition is not found. Name: [<connection resource name>]

The resource definition selected in Destination isn't found.

Check the connection resource specified in Destination.

 

Limitations of FTP category

Operation environment

Notes

  • When connecting to an FTP server or an FTP over SSL/TLS server, this connector assumes that the server complies with RFC 1123.

    When connecting to a server that doesn't comply with RFC 1123, the operation might fail.

    • Note

    SSH version 1 isn't supported.

Connection resource properties

Notes

  • Destination FTP servers

    When connecting to an FTP server or an FTP over SSL/TLS server, FTP Connector assumes that the server complies with RFC 1123.

    When connecting to a server that doesn't comply with RFC 1123, the operation might fail.

Get List and Data

Specification limits

  • ACCOUNT(ACCT) isn't supported.

  • To get a text file containing character code other than ASCII code, you need to get it in BINARY.

  • Confirmation whether updated or not is judged by issuing the MDTM command and getting the updated date and time for files from FTP server.

    Depending on FTP server, this command might not be able to used. In that case, don't select Check for update when transferring file, or select Check for update when transferring file and select Exist in Criteria for updating.

    Also, when MDTM doesn't return GMT (Greenwich Mean Time), judging update might not work well.

  • Only when MDTM command can be used in FTP server and the command returns GMT (Greenwich Mean Time), Updated time of Check for update when transferring file can be used.

    Also, when there is a time difference between the FTP server and the host in which HULFT Square operates, this function can't be used.

  • In this connector, updated time can't be set arbitrarily for files in the HULFT Square Storage. Therefore, the time of OS in which HULFT Square operates is set to files gotten from FTP server.

    Consequently, when there is a time difference between the FTP server and the OS in which HULFT Square operates, judging update might not be work well.

  • To download files, you need to have permissions to read the files to be downloaded. Further, you need to have permissions to write to the path to be downloaded to.

  • The list of files output with FTP Connector depends on the result of LIST command issued to FTP server. Sorting by names or sorting by files and directories isn't performed.

  • Attributes of files that can be gotten are "directory", "file", and "symbolic link". For symbolic link, the data of the link target will be gotten. Block special files, character special files, named pipes, AF_UNIX family sockets, etc. can't be handled. Files with an attribute that can't be handled by a read operation will be ignored. In other words, it isn't downloaded nor included in the result.

Notes

  • All the file paths used in FTP Connector are absolute path. All the items to input or output a path or a file path are absolute path.

  • "/" is used for all the delimiters of file paths used in FTP Connector.

  • Characters that can't be used for file name

    • Character code that isn't supported by HULFT Square and custom characters or extended character code can't be used.

    • Characters that can't be used in the FTP server to be connected also can't be used. Strings that can't be used are as follows.

      Note

      The character code within the parentheses is the character code in Shift_JIS.

      • ―(0x815c)

      • ～(0x8160)

      • ∥(0x8161)

      • －(0x817c)

      • ￠(0x8191)

      • ￡(0x8192)

      • ￢(0x81CA)

  • When using wild cards in file path, it can't be specified in the middle of file path.

    • File paths with wild cards can be set as follows:

      • /home/user/getdata/*

      • /home/user/getdata/*.txt

    • File paths with wild cards can't be set as follows:

      • /home/user/*/sample.txt

      • /home/user/*data/*.txt

  • When an error other than network failure occurs during downloading files, the error details is output in the log with the log level "WARN" and the operation continues.

    In the output schema, "NG" is set in the status attribute of the file where the error occurred.

Read List

Specification limits

  • ACCOUNT(ACCT) isn't supported.

  • The list of files output with FTP Connector depends on the result of LIST command issued to FTP server. Sorting by names, files, or directories isn't performed.

  • Attributes of files that can be gotten are "directory", "file", and "symbolic link". For symbolic link, the data of the link target will be gotten. Block special files, character special files, named pipes, AF_UNIX family sockets, etc. can't be handled. Files with an attribute that can't be handled by a read operation will be ignored. In other words, it's not included in the result.

Notes

  • All the file paths used in FTP Connector are absolute path. All the items to input or output a path or a file path are absolute path.

  • "/" is used for all the delimiters of file paths used in FTP Connector.

  • Characters that can't be used for file name

    • Character code that isn't supported by HULFT Square and custom characters or extended character code can't be used.

    • Characters that can't be used in the FTP server to be connected also can't be used. Strings that can't be used are as follows.

      Note

      The character code within the parentheses is the character code in Shift_JIS.

      • ―(0x815c)

      • ～(0x8160)

      • ∥(0x8161)

      • －(0x817c)

      • ￠(0x8191)

      • ￡(0x8192)

      • ￢(0x81CA)

  • When using wild cards in file path, it can't be specified in the middle of file path.

    • File paths with wild cards can be set as follows:

      • /home/user/getdata/*

      • /home/user/getdata/*.txt

    • File paths with wild cards can't be set as follows:

      • /home/user/*/sample.txt

      • /home/user/*data/*.txt

Update

Specification limits

  • ACCOUNT(ACCT) isn't supported.

  • Confirmation whether updated or not is judged by issuing the MDTM command and getting the updated date and time for files from FTP server.

    Depending on FTP server, this command might not be able to used. In that case, don't select Check for update when transferring file, or select Check for update when transferring file and select Exist in Criteria for updating.

    Also, when MDTM doesn't return GMT (Greenwich Mean Time), judging update might not work well.

  • Only when MDTM command can be used in FTP server and the command returns GMT (Greenwich Mean Time), Updated time of Check for update when transferring file can be used.

    Also, when there is a time difference between the FTP server and the host in which HULFT Square operates, this function can't be used.

  • In this connector, updated time can't be set arbitrarily for files in the HULFT Square Storage. Therefore, the time of OS in which HULFT Square operates is set to files gotten from FTP server.

    Consequently, when there is a time difference between the FTP server and the OS in which HULFT Square operates, judging update might not be work well.

  • To upload files, you need to have permissions to read the files to be uploaded. Further, you need to have permissions to write to the FTP server path to be uploaded to.

Notes

  • All the file paths used in FTP Connector are absolute path. All the items to input or output a path or a file path are absolute path.

  • "/" is used for all the delimiters of file paths used in FTP Connector.

  • Characters that can't be used for file name

    • Character code that isn't supported by HULFT Square and custom characters or extended character code can't be used.

    • Characters that can't be used in the FTP server to be connected also can't be used. Strings that can't be used are as follows.

      Note

      The character code within the parentheses is the character code in Shift_JIS.

      • ―(0x815c)

      • ～(0x8160)

      • ∥(0x8161)

      • －(0x817c)

      • ￠(0x8191)

      • ￡(0x8192)

      • ￢(0x81CA)

  • When using wild cards in file path, it can't be specified in the middle of file path.

    • File paths with wild cards can be set as follows:

      • /home/user/getdata/*

      • /home/user/getdata/*.txt

    • File paths with wild cards can't be set as follows:

      • /home/user/*/sample.txt

      • /home/user/*data/*.txt

  • When an error other than network failure occurs during updating files, the error details is output in the log with the log level "WARN" and the operation continues.

    In the output schema, "NG" is set in the status attribute of the file where the error occurred.

Delete

Specification limits

  • ACCOUNT(ACCT) isn't supported.

  • In some of FTP server environments, even the file without permissions will be deleted if it corresponds with the path.

Notes

  • All the file paths used in FTP Connector are absolute path. All the items to input or output a path or a file path are absolute path.

  • "/" is used for all the delimiters of file paths used in FTP Connector.

  • Characters that can't be used for file name

    • Character code that isn't supported by HULFT Square and custom characters or extended character code can't be used.

    • Characters that can't be used in the FTP server to be connected also can't be used. Strings that can't be used are as follows.

      Note

      The character code within the parentheses is the character code in Shift_JIS.

      • ―(0x815c)

      • ～(0x8160)

      • ∥(0x8161)

      • －(0x817c)

      • ￠(0x8191)

      • ￡(0x8192)

      • ￢(0x81CA)

  • When using wild cards in file path, it can't be specified in the middle of file path.

    • File paths with wild cards can be set as follows:

      • /home/user/getdata/*

      • /home/user/getdata/*.txt

    • File paths with wild cards can't be set as follows:

      • /home/user/*/sample.txt

      • /home/user/*data/*.txt

  • When an error other than network failure occurs during deleting files, the error details is output in the log with the log level "WARN" and the operation continues.

    In the output schema, "NG" is set in the status attribute of the file where the error occurred.

Rename

Specification limits

  • ACCOUNT(ACCT) isn't supported.

Notes

  • All the file paths used in FTP Connector are absolute path. All the items to input or output a path or a file path are absolute path.

  • "/" is used for all the delimiters of file paths used in FTP Connector.

  • Characters that can't be used for file name

    • Character code that isn't supported by HULFT Square and custom characters or extended character code can't be used.

    • Characters that can't be used in the FTP server to be connected also can't be used. Strings that can't be used are as follows.

      Note

      The character code within the parentheses is the character code in Shift_JIS.

      • ―(0x815c)

      • ～(0x8160)

      • ∥(0x8161)

      • －(0x817c)

      • ￠(0x8191)

      • ￡(0x8192)

      • ￢(0x81CA)

  • When an error other than network failure occurs during renaming files, the error details is output in the log with the log level "WARN" and the operation continues.

    In the output schema, "NG" is set in the status attribute of the file where the error occurred.

Policies     (c) Saison Technology Co.,Ltd. 2021

TOP