- CWYFT0001F: An error occurred while configuring the splitting mechanism for inbound operation, SplittingFunctionClassName={0} ,SplitCriteria={1} ,FileContentEncoding={2}, error message={3}.
- Explanation: SplittingFunctionClassName should be a fully qualified class name that is used for splitting the event files based on SplitCriteria and encoding of the file content.
- User Action: Check the configuration properties for SplittingFunctionClassName, SplitCriteria and FileContentEncoding, try again.
- CWYFT0002E: An error occurred while parsing the time stamp from the event ID during recovery: event id= {0} , timestamp= {1} , error message={2}.
- Explanation: The time stamp present in the eventID should be in the following format: yyyy_MM_dd_HH_mm_ss_SSS Otherwise a parsing time stamp error will occur when the time is obtained from the the event ID.
- User Action: Ensure that the eventid and time stamp are valid.
- CWYFT0003E: An error occurred while getting the business object content as a byte[] from the event file present in LocalEventDirectory for the event ID {0}.
- Explanation: An error occurred while getting the business object content from the event file when parsing the file based on the SplitCriteria.
- User Action: This is a runtime error. Check to see that the file exists in the LocalEventDirectory and try again. If you still receive an error message, the file might be corrupt.
- CWYFT0004E: An error occurred while archiving: delivery type is ordered, event file name: {0}, current business object: {1}, total business objects: {2}, current business object status: {3}.
- Explanation: A error occurred while archiving each business object available in the event file.
- User Action: Ensure that the event file exists in the LocalEventDirectory and that it is not corrupt.
- CWYFT0005E: An error occurred while archiving: The delivery type is unordered, event file name: {0}, current business object: {1}, total business objects: {2}, current business object status: {3}.
- Explanation: An error occurred while archiving each business object available in the event file.
- User Action: Ensure that the event file exists in the LocalEventDirectory and that it is not corrupt.
- CWYFT0006E: An error occurred while validating the poll period, because it is less than zero. PollPeriod={0}
- Explanation: PollPeriod cannnot be negative. It is the rate (in milliseconds) at which to poll the FTP server EventDirectory for new events files.
- User Action: Ensure that the poll period is greater than or equal to zero and try again.
- CWYFT0007E: An error occurred while validating the poll quantity; it is less than 1. PollQuantity={0}
- Explanation: The poll quantity should be greater than or equal to one. It determines the number of events(business objects) to be delivered to each endpoint per poll cycle.
- User Action: Ensure that the poll quantity is greater than or equal to one and try again.
- CWYFT0008E: An error occurred while validating the delivery type, which should take either ORDERED or UNORDERED values. The value given for the delivery type is {0}.
- Explanation: The delivery type should be either ORDERED or UNORDERED. This value determines the order in which the events will be published, either one at a time (ORDERED) or all at once (UNORDERED).
- User Action: Ensure that the delivery type is correct and that it takes a valid value.
- CWYFT0009E: An error occurred while validating the file mask. The value is invalid. File mask={0}
- Explanation: The file mask is not valid. It should not contain any special characters that file systems will not consider as valid characters in a file name.
- User Action: Ensure that the file mask is correct and try again.
- CWYFT0010E: An error occurred while validating the event file sorting order format. It takes any of the following values: "Filename" , "Timestamp" and "", The value given for SortEventFiles={0}.
- Explanation: SortEventFiles has an invalid value. It takes "Filename", "Timestamp" and "". It determines how the event files are sorted, based on their Filename or Timestamp. If no value is specified, the files are not sorted.
- User Action: Ensure that the sorting order format is correct, and try again.
- CWYFT0011E: An error occurred while validating FTPGetQuantity. It should be an integer greater than zero. FTPGetQuantity={0}
- Explanation: FTPGetQuantity determines the number of files to be downloaded to local event directory from the remote FTP URL with each remote poll. It should have a positive integer.
- User Action: Ensure that the value for FTPGetQuantity has a valid positive integer, and try again.
- CWYFT0012E: An error occurred while validating the FTPPollFrequency. FTPPollFrequency={0}
- Explanation: The FTPPollFrequency is invalid because it is less than zero. The FTPPollFrequency determines how frequently the resource adapter polls the FTP server, and is measured in the number of standard poll cycles.
- User Action: Ensure that the FTPPollFrequency has a valid integer greater than or equal to zero.
- CWYFT0013E: An error occurred while validating the CustomParserClassName, because it is not valid. The given value is {0}.
- Explanation: An error occurred while validating CustomParserClassName, because it takes a fully qualified class name of the custom parser that is used to parse the ls -l output.
- User Action: Ensure that the value is a fully-qualified Java class name.
- CWYFT0014E: An error occurred while validating SplittingFunctionClassName, because is not valid. The given value is {0}.
- Explanation: The SplittingFunctionClassName could not be validated. It takes a fully qualified class name of the class to be used in order to split the event file.
- User Action: Ensure that the SplittingFunctionClassName is a valid value. It should be a fully-qualified class name.
- CWYFT0015E: An error occurred while validating SplitCriteria, because it is not valid for the selected SplittingFunctionClassName: {0}. SplitCriteria is {1}.
- Explanation: Failed to validate SplitCriteria. It takes a valid value based on the SplittingFunctionClassName used.
- User Action: Ensure that the SplitCriteria has a valid value, and try again.
- CWYFT0016E: An error occurred while validating the {0}. The file does not exist in the directory. Filename = {1}
- Explanation: The FTP script file could not be validated. It represents the absolute path of the script file in the adapter machine and the file should exist in that directory.
- User Action: Ensure that the FTP script file exists in the directory, and try again.
- CWYFT0017E: Error: {0} is invalid for the inbound operation, because it is either NULL or an empty string. Directory={1}
- Explanation: The directory could not be validated. It should not be null and it should have a valid value.
- User Action: Ensure that the directory name is correct and that it exists in the FTP server.
- CWYFT0018E: An error occurred while validating the user name for the FTP server; the user name is invalid.
- Explanation: The user name of the FTP server could not be validated. Either the user name should be part of the FTP URL, or the Username property of the ActivationSpec should have a valid value.
- User Action: Ensure that the user name is not NULL and that it is correct.
- CWYFT0019E: An error occurred while validating the password for the FTP server; the password is invalid.
- Explanation: The password of the FTP server could not be validated. It should be part of the FTP URL or Password property of the ActivationSpec and should have a valid value.
- User Action: Ensure that the password is not NULL and that it is correct.
- CWYFT0020E: An error occurred while validating the FTP URL and event directory, {0}; the value for EventDirectory is {1}.
- Explanation: The EventDirectory could not be validated. It should have the following format: "ftp://[UserId:password@]FTPserver[:port][RemoteEventDirectory]"
- User Action: Ensure that the value for EventDirectory is correct.
- CWYFT0021E: The specified {0} does not exist in the FTP server. Directory name: {1}
- Explanation: The directory for the inbound operation could not be validated because it does not exist.
- User Action: Ensure that the directory name is correct, and try again.
- CWYFT0022E: The {0} in the FTP server does not have the necessary permissions. Directory name: {1}
- Explanation: The directory for the inbound operation could not be validated because it does not have the necessary permissions.
- User Action: Ensure that the directory has necessary permissions for the inbound operation.
- CWYFT0023E: An error occurred while validating the {0} directory, directory name={1} and error message ={2}.
- Explanation: The directory could not be validated. The directory (with sufficient required permissions) should be a valid name, and it should exist in the FTP server.
- User Action: Ensure that the directory is correct, and try again.
- CWYFT0024E: An error occurred while validating the {0} path present in the local adapter machine, because it is either NULL or is an empty string. Directory name = {1}
- Explanation: The directory path present in the workstation where the adapter is running could not be validated. The directory should not be null or an empty string.
- User Action: Ensure that the directory path is not NULL and that it is correct.
- CWYFT0025E: An error occurred while validating the {0} path present in the workstation where the adapter is running; the directory does not exist. Directory name={1}
- Explanation: The directory could not be validated. It must exist on the workstation where the adapter is installed.
- User Action: Ensure that the directory name is correct, and that it exists in the workstation where the adapter is running.
- CWYFT0026E: The {0} does not have the required {1} permission. Directory name={2}
- Explanation: The directory does not have the necessary read or write permissions.
- User Action: Ensure that the directory has the necessary permissions.
- CWYFT0027E: An error occurred while validating {0}; it should be a valid encoding supported by Java. Its value is {1}.
- Explanation: The encoding value is not correct as it is not a java supported encoding.
- User Action: Ensure that the value is a valid encoding supported by Java, and try again.
- CWYFT0028E: An error occurred while connecting to the FTP server {0}.
- Explanation: A connection could not be made to the FTP server.
- User Action: Ensure that the connection information is correct, and try again.
- CWYFT0029E: An error occurred while selecting the files with the specified file mask, file mask={0}, file name={1}, error message={2}.
- Explanation: The adapter failed to select the files with the specified file mask.
- User Action: Ensure that the file mask is correct and that it is valid.
- CWYFT0030E: An error occurred while downloading the event file to LocalEventDirectory and archiving it on the FTP server. Error message: {0}
- Explanation: The adapter failed while downloading the files from FTPServer.
- User Action: Ensure that the FTP server is running and that network connections are properly configured, and try again.
- CWYFT0031I: Setting the EisEncoding value (if it is not set) of the ActivationSpec with the value of resource adapter EisEncoding(if this has a value).
- Explanation: If EisEncoding of the ActivationSpec is not set, then EisEncoding will take the EisEncoding value (if it has a value) available at the resource adapter level.
- User Action: No action is required.
- CWYFT0032I: The FTP server data connection mode is not set, and will therefore default to the active data connection mode.
- Explanation: If the DataConnectionMode of the ActivationSpec is not set, then DataConnectionMode is set to 'active' by default.
- User Action: No action is required.
- CWYFT0033I: The file transfer type is set incorrectly and will be defaulted to the binary transfer type.
- Explanation: If FileTransferType of the ActivationSpec is not set, the FileTransferType is set to 'binary' by default.
- User Action: No action is required.
- CWYFT0034I: SplittingFunctionClassName is being set to com.ibm.j2ca.utils.filesplit.SplitBySize.
- Explanation: If SplittingFunctionClassName of the ActivationSpec is not set, it is set to 'com.ibm.j2ca.utils.filesplit.SplitBySize' by default.
- User Action: No action is required.
- CWYFT0035I: Setting SplitCriteria to 0 (no chunking of the event file) because the given SplitCriteria is not valid for the given SplittingFunctionClassName(com.ibm.j2ca.utils.filesplit.SplitBySize)
- Explanation: If SplittingFunctionClassName is com.ibm.j2ca.utils.filesplit.SplitBySize, and SplitCriteria is not a valid number, then SplitCriteria is set to 0.
- User Action: No action is required.
- CWYFT0036I: EventContentType is not set. The inbound scenario is a pass through where data transformation will not take place.
- Explanation: If EventContentType is not set, the inbound scenario is a pass through where data transformation does not take place and the unparsed content is sent to the endpoint.
- User Action: No action is required.
- CWYFT0037I: The FTP data connection mode is being set to {0} connection mode.
- Explanation: If you are using secure FTP, the data connection mode to be used is passive, otherwise use either active or passive data connectionmodes as per user configuration.
- User Action: No action is required.
- CWYFT0038I: DefaultObjectName is being set to {0}.
- Explanation: If DefaultObjectName or EventContentType is not set, the DefaultObjectName is set to the FTPFileBG.
- User Action: No action is required.
- CWYFT0039E: An error occurred while validating the DefaultObjectName. DefaultObjectName = {0}
- Explanation: The DefaultObjectName appears to be invalid.
- User Action: Ensure that the DefaultObjectName is correct and that the required XSDs are present in the deployed application, and try again.
- CWYFT0040E: An error occurred while validating the BONamespace because it is invalid. BONamespace = {0}
- Explanation: Failed to validate the BONamespace.
- User Action: Ensure that the BONamespace value is correct, and try again.
- CWYFT0041E: An error occurred while instantiating the file object.
- Explanation: Either the file does not exist or it is locked
- User Action: The file path and name is incorrect.Ensure that the path is valid and that the file exists in the specified path.
- CWYFT0042E: An error occurred while retrieving the business object content.
- Explanation: Check the contents of the event file.
- User Action: The event file might be empty.
- CWYFT0043E: An error occurred while fetching the total number of business objects in the file.
- Explanation: The total number of business objects could not be obtained due to invalid event file or delimiter.
- User Action: Verify that the event file and delimiter are correct.
- CWYFT0044E: EndBODelimiter is set to an invalid value.
- Explanation: Delimiter is set to an unsupported format.
- User Action: Set a valid value for the EndBODelimiter.
- CWYFT0045E: The specified delimiter does not exist in the event file.
- Explanation: A delimiter value could not be found in the event file.Ensure that the specified delimiter exists in the event file.
- User Action: Configure a delimiter that exists in the event file.
- CWYFT0046E: The file exists in the specified location, but is not accessible.
- Explanation: File might be locked by an external application or might not have sufficient access permissions.
- User Action: Ensure that the file has the required permissions and no external application has a lock on the file.
- CWYFT0047E: The configured encoding is not supported.
- Explanation: The encoding specified may not be a valid value.
- User Action: Specify a valid encoding.
- CWYFT0101E: The InteractionSpec specified is invalid. It is null or not a valid instance of FTPFileInteractionSpec.
- Explanation: The specified InteractionSpec is either null or invalid.
- User Action: Specify a valid InteractionSpec argument. The InteractionSpec passed as an argument to the execute method of the interaction should not be null and should be a valid instance of FTPFileInteractionSpec.
- CWYFT0102E: An error occurred while validating the function name: {0}. It is not a valid value.
- Explanation: None of the valid function names (Create, Append, Overwrite, Delete, Exists, Retrieve, List, ExecuteFTPScript, and ServerToServerFileTransfer) have been specified in the Interaction specification.
- User Action: Ensure that the function name is correct and one of the supported function names: Create, Append, Overwrite, Delete, Exists, Retrieve, List, ExecuteFTPScript, and ServerToServerFileTransfer.
- CWYFT0103E: The specified input record is invalid.
- Explanation: The input record passed as an argument to the execute method of the interaction should not be null and should be an instance of FTPFileUnstructuredRecord.
- User Action: Specify a valid input record(FTPFileUnstructuredRecord) argument.
- CWYFT0104E: Error: The {0} for the {1} operation is invalid; it is either NULL or an empty string.
- Explanation: The directory path is invalid.
- User Action: Ensure that the directory path is correct.
- CWYFT0105F: An error occurred while connecting to the enterprise information system (EIS). FtpUrl:{0}, UserName:{1} and Password:{2}
- Explanation: Failed to get a connection to the EIS.
- User Action: Ensure that the connection information(FTPURL, userName and password) is correct, and try again.
- CWYFT0106E: An error occurred while creating the ManagedConnection object; the FTP connection information is invalid in ConnectionSpec or ManagedConnectionFactory.
- Explanation: Failed to create ManagedConnection object.
- User Action: Ensure that the connection information is correct, and try again.
- CWYFT0107E: An error occurred while validating the FtpUrl in ManagedConnectionfactory, it is invalid.
- Explanation: An error occurred while validating the FtpUrl in ManagedConnectionFactory.
- User Action: Ensure that the FtpUrl is correct, and try again.
- CWYFT0108E: An error occurred while validating the user name for the FTP server.
- Explanation: The user name of the FTP server could not be validated. Either the user name should be part of the FTP URL, or the Username property of the ManagedConnectionFactory must have a valid value.
- User Action: Ensure that the user name is not NULL and is correct.
- CWYFT0109E: An error occurred while validating the password for the FTP server.
- Explanation: The password of the FTP server could not be validated. Either the password should be part of the FTP URL, or the Username property of the MCF should have a valid value.
- User Action: Ensure that the password is not NULL and is correct.
- CWYFT0110E: An error occurred while validating the FtpUrl, URL={0}, error message: {1}.
- Explanation: The FtpUrl could not be validated. To be valid, it must take the form of ftp://[username:password@]hostname[:portNumber]
- User Action: Ensure that the FtpUrl is correct, and try again.
- CWYFT0111I: The EisEncoding value (if it is not set) of the ManagedConnectionFactory is set with the value of resource adapter EisEncoding (if this property has a value).
- Explanation: If the value for EisEncoding of the ManagedConnectionFactory is not set, then the adapter will take the EisEncoding value (if it has value) available at the resource adapter level.
- User Action: No action is required.
- CWYFT0112E: An error occurred while validating {0}; it should be a valid encoding supported by Java. The specified value is {1}.
- Explanation: Failed to validate the encoding.
- User Action: Ensure that the value is a valid encoding supported by Java and try again.
- CWYFT0113E: An error occurred while validating CustomParserClassName. The specified value for the parser is {0}.
- Explanation: An error occurred while validating CustomParserClassName. The fully qualified class name of the custom parser is used to parse the ls -l output.
- User Action: Ensure that the value is a valid, fully qualified Java class name.
- CWYFT0114E: The Port Number for SocksProxyPort is invalid.
- Explanation: The adapter failed to validate the SocksProxyPort. It should be a valid port used by the FTP proxy server.
- User Action: Ensure that the SocksProxyPort is correct, and try again.
- CWYFT0115E: An error occurred while checking the {0} for {1} operation, because the directory does not exist. The specified directory path is {2}
- Explanation: The adapter failed while validating the directory during the outbound scenario.
- User Action: Ensure that the directory path is correct and try again.
- CWYFT0116E: The {0} does not have the necessary permissions for outbound {1} operation. Directory path: {2}
- Explanation: The adapter failed to validate the directory because the directory does not have the necessary permission.
- User Action: Ensure that the directory has valid permissions.
- CWYFT0117E: An error occurred while changing to the {0} for the operation: {1}. The specified directory path is {2}
- Explanation: The adapter failed to move to the directory for the outbound operation.
- User Action: Ensure that directory is valid, and try again.
- CWYFT0118E: File {0} already exists in the specified directory {1} for the outbound {2} operation.
- Explanation: An error occurred during the create operation because the file already exists. The file with same name should not be available in the directory.
- User Action: Ensure that the file does not exist in the specified directory, and try again.
- CWYFT0119E: {0} operation failed. The content(bytes attribute in the input record) to {0} the file is NULL.
- Explanation: The adapter failed during the outbound operation, because the attribute for input bytes is NULL.
- User Action: Ensure that the file content bytes[] is populated, and try again.
- CWYFT0120E: An error occurred during local archiving: {0}. File name: {1}
- Explanation: The adapter failed during local archiving for the outbound create operation.
- User Action: Ensure that the local archive directory is correct.
- CWYFT0121E: File {0} is either invalid or it does not exist in the specified directory {1} for the outbound operation {2}
- Explanation: An error occurred while checking for the existence of the file.
- User Action: Ensure that the file exists in the specified directory, and try again.
- CWYFT0122E: The second server connection details are invalid.
- Explanation: The ServerToServerFileTransfer operation failed because the second server connection information in the ManagedConnectionFactory or wrapper business object properties is invalid.
- User Action: Correct the second server connection details and try again.
- CWYFT0123I: The FTP data connection mode is not set; it will be set to an active data connection mode.
- Explanation: The adapter failed to validate the data connection mode; DataConnectionMode will be defaulted to active mode.
- User Action: Ensure that the required data connection mode is set.
- CWYFT0124I: The file transfer type is not valid; it will be defaulted to binary transfer mode.
- Explanation: The adapter failed to validate the file transfer type and is therefore defaulting to binary mode.
- User Action: Ensure that the required file transfer type is selected.
- CWYFT0125E: {0} is invalid for the {1} operation, directory path {2}
- Explanation: The adapter failed to validate the LocalDirectoryPath. The directory is not existing or the value is wrong.
- User Action: Specify a valid value for the LocalDirectoryPath and try again.
- CWYFT0126E: The file does not exist in the {0} given by {1} for the {2} operation.
- Explanation: The specified directory does not exist.
- User Action: Ensure that the directory name, file name, and other configurations are correct.
- CWYFT0127E: {0} does not have write permission for the {1} operation, {0} = {2}.
- Explanation: The directory does not have the required write permission.
- User Action: Ensure that the directory has the required write permission.
- CWYFT0128E: {0} does not have read permission for the {1} operation, {0} = {2}.
- Explanation: The directory does not have the required read permission
- User Action: Ensure that the directory has the required read permission.
- CWYFT0129E: An error occurred while reading the file from the adapter workstation for a create operation. The local directory name is {0} and the file name is {1}
- Explanation: The local directory and file name from which the content for the create operation will be picked are not valid. The file should exist in the adapter workstation.
- User Action: Ensure that the directory name and file name are correct and try again.
- CWYFT0130E: An error occurred while reading the byte content from the unstructured record, error message: {0}
- Explanation: Error occurred while reading the byte content from unstructured record.
- User Action: Check the encoding of the content, and use the same encoding to configure the adapter FileContentEncoding.
- CWYFT0131E: An error occurred while instantiating the data object, which is returned as part of the {0} operation. Error message: {1}
- Explanation: Error while instantiating the data object.
- User Action: Ensure that the XSDs are available and are valid.
- CWYFT0132E: The files to be retrieved for the Retrieve operation are either not specified or is invalid.
- Explanation: The adapter failed to validate the file names for the Retrieve operation.
- User Action: Provide a valid file names list, with each file name separated by a comma, if more than one file is to be retrieved.
- CWYFT0133E: The ServerToServerFileTransfer operation failed. Error message: {0}
- Explanation: An error occurred during the ServerToServerFileTransfer operation.
- User Action: Check the configuration(SecondServerDirectory, SecondServerUsername, SecondServerpassword) related to the ServerToServerFileTransfer operation and try again.
- CWYFT0134E: The value set for FileContentEncoding is not supported. FileContentEncoding={0}
- Explanation: The encoding value for the FileContentEncoding property is not supported.
- User Action: Specify a valid encoding supported by Java, and try again.
- CWYFT0201F: : The adapter cannot instantiate the FTPClient wrapper for FTP related operations. Audit for directory: {0}, control encoding (EisEncoding): {1} , custom parser class name: {2}, error message: {3}
- Explanation: The adapter failed to instantiate the FTPClient wrapper for FTP related operations.
- User Action: Check the connection details in the ManagedConnectionFactory and try again.
- CWYFT0202E: An error occurred while appending the content to the file in the FTP server, directory name: {0}, file name: {1}, FTP reply code: {2} and FTP reply String: {3}; error message: {4}
- Explanation: The adapter failed to append the content to the file in the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct and try again.
- CWYFT0203E: The FTP server prematurely closed the connection as a result of the client being idle, directory name: {0}, file name: {1}, FTP reply code: {2}, FTP reply String: {3}, and error string: {4}
- Explanation: If the FTP connection is not used to connect to the FTP server for the timeout period, the connection times out and you must reconnect it.
- User Action: Set the timeout property of the FTP server based on the time between each request to the FTP server so that the FTP connection will not time out.
- CWYFT0204F: An error occurred while establishing a connection with the FTP server, hostname: {0}, port number: {1}, FTP reply code: {2}, FTP reply string: {3}, and error message: {4}
- Explanation: Check the connection details in ManagedConnectionFactory and also the network connections.
- User Action: Ensure that the host name and port number are correct. Also check the network connections with the FTP server to be sure that they are fine.
- CWYFT0205E: An error occurred while creating the file in the FTP server, directory name: {0}, file name: {1}, FTP reply code: {2}, and FTP reply String: {3}; error message: {4}
- Explanation: The adapter failed to create the file in the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0206E: An error occurred while deleting the file from the FTP server, directory name: {0}, file name: {1}, FTP reply code: {2}, and FTP reply String: {3}; error message: {4}
- Explanation: Failed to delete the file in the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0207E: An error occurred while closing the FTP connection. FTP reply code: {0} and FTP reply String: {1}; error message: {2}
- Explanation: Failed to close the connection to the FTP server.
- User Action: Ensure that the network connections are properly configured.
- CWYFT0208E: An error occurred while checking for the existence of the file in the FTP server, directory name: {0}, file name: {1}, FTP reply code: {2}, and FTP reply String: {3}; error message: {4}
- Explanation: Error while checking if the file exists.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0209E: An error occurred while checking to ensure that the directory exists in the FTP server, directory name: {0}, FTP reply code: {1}, and FTP reply String: {2}; error message: {3}
- Explanation: Error while checking if the file exists.
- User Action: Ensure that the directory name and other configurations are correct, and try again.
- CWYFT0210E: An error occurred while retrieving the timestamp of the file, directory name: {0}, file name: {1}, FTP reply code: {2}, and FTP reply String: {3}; error message: {4}
- Explanation: Error while retrieving the timestamp of the file.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0211E: An error occurred while getting the list of file names from the current directory of the FTP server, directory name: {0}, FTP reply code: {1}, and FTP reply String: {2}; error message: {3}
- Explanation: An error occurred while getting the list of file names from the current directory of the FTP server.
- User Action: Ensure that the directory name and other configurations are correct, and try again.
- CWYFT0212E: An error occurred while logging into the FTP server, user name: {0}, password: {1}, account info: {2}, FTP reply code: {3}, and FTP reply String: {4}; error message: {5}
- Explanation: Error while logging into the FTP server.
- User Action: Ensure that the user name, password, account name, and other configurations are correct, and try again.
- CWYFT0213E: An error occurred while logging out of the FTP server. FTP reply code: {0} and FTP reply String: {1}; error message: {2}
- Explanation: Failed to close the connection to the FTP server.
- User Action: Ensure that the network connections are properly configured.
- CWYFT0214E: A file with the same name already exists in the directory. New directory: {0} and file name: {1}
- Explanation: A file with same name already exists in the new directory while moving the file.
- User Action: A file already exists with same name in the new directory. Ensure that the file names are unique, and try again.
- CWYFT0215E: An error occurred while moving and renaming the file. Current directory: {0}, new directory: {1}, current filename: {2}, new filename: {3}, FTP reply code: {4} and FTP reply String: {5}; error message: {6}
- Explanation: An error occurred while moving and renaming the file.
- User Action: Check the configuration and try again.
- CWYFT0216E: An error occurred while moving the file. Current directory: {0}, new directory: {1}, file name: {2}, FTP reply code: {3} and FTP reply String: {4}; error message: {5}
- Explanation: Error while moving the file.
- User Action: Ensure that the adapter is correctly configured, and try again.
- CWYFT0217E: An error occurred while overwriting the file in the FTP server, directory name: {0}, file name: {1}, FTP reply code: {2} and FTP reply String: {3}; error message: {4}
- Explanation: The adapter failed to overwrite the file in the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct and try again.
- CWYFT0218E: An error occurred while renaming the file in the FTP server, directory name: {0}, old file name: {1}, new file name: {2}, FTP reply code: {3}, and FTP reply String: {4}; error message: {5}
- Explanation: The adapter failed to rename the file in the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0219E: An error occurred while downloading the file. A file already exists with the same name in the local directory. Directory: {0} and file name: {1}
- Explanation: The adapter failed to retrieve (download) the file from the FTP server to the adapter workstation.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0220E: An error while retrieving the file from the FTP server, remote directory: {0}, remote filename: {1}, local directory name: {2}, local file name: {3}, FTP reply code: {4} and FTP reply String: {5}; error message: {6}
- Explanation: Failed to retrieve(download) the file from the FTP server to the adapter machine.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0221E: An error occurred while retrieving the file content as a byte[] from the FTP server, remote directory: {0}, remote filename: {1}, FTP reply code: {2} and FTP reply String: {3}; error message: {4}
- Explanation: Failed to retrieve (download) the file as a byte[] from the FTP server.
- User Action: Ensure that the directory name, file name, and other configurations are correct, and try again.
- CWYFT0222E: An error occurred while setting the file transfer mode, file transfer mode: {0}, FTP reply code: {1} and FTP reply String: {2}; error message: {3}
- Explanation: An error while setting the file transfer mode, STREAM_TRANSFER_MODE=10.
- User Action: Ensure that the file transfer mode is set correctly.
- CWYFT0223E: An error occurred while setting the file type, file type: {0}, FTP reply code: {1} and FTP reply String: {2}; error message: {3}
- Explanation: An error occurred while setting the file type, ASCII_FILE_TYPE=0 and BINARY_FILE_TYPE=2.
- User Action: Ensure that the file type is set correctly.
- CWYFT0224E: An error occurred while changing the directory, directory name: {0}, FTP reply code: {1} and FTP reply String: {2}; error message: {3}
- Explanation: Error while changing the directory.
- User Action: Ensure that the directory name is correct, and try again.
- CWYFT0225E: An error occurred while getting the current working directory, FTP reply code: {0} and FTP reply String: {1}; error message: {2}
- Explanation: The adapter failed while getting the current working directory of the FTP server.
- User Action: Ensure that the network connection is proper, and try again.
- CWYFT0226E: An error occurred while listing only files (not directories) from the given directory, directory name: {0}, FTP reply code: {1} and FTP reply String: {2}; error message: {3}
- Explanation: An error occurred while listing only files (not directories) from the given directory.
- User Action: Ensure that the directory name is correct, and try again.
- CWYFT0227E: An error occurred while checking the permissions for a directory, directory name: {0}, FTP reply code: {1} and FTP reply String: {2}; error message: {3}
- Explanation: An error occurred while checking the permissions for a directory.
- User Action: Ensure that the directory name is correct, and try again.
- CWYFT0228E: The adapter failed in the send noop command, FTP URL:{0}, FTP reply code: {1}, and FTP reply String: {2}; error message: {3}
- Explanation: Error while sending a noop command. Server might be down or problem with the network.
- User Action: Check to see if the FTP server is down. Also check the network connections to be sure they are properly configured
- CWYFT0229E: An error occurred during a ServerToServerFileTransferOperation, file name to be transferred: {0}, FTP reply code: {1}, and FTP reply String: {2}; error message: {3}
- Explanation: Error during a ServerToServerFileTransferOperation.
- User Action: Ensure that the two server connection details are valid. Also check the directory and file name to be transferred if they are valid or not.
- CWYFT0230I: The FTP connection timed out, and the connection was closed. The adapter is reconnecting.
- Explanation: The timeout period of the FTP server should be configured so that it will not time out between each FTP server interaction.
- User Action: No action is required.
- CWYFT1001E: An error occurred while setting the tool context and instantiating the logging and tracing object. Error message:{0}
- Explanation: An error occurred while starting the enterprise service discovery tool.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1002E: An error occurred in the createServiceDescription call in MetaDataDiscoveryImpl for {0}. Error message:{1}
- Explanation: An error occurred while creating the service descriptions.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1003E: An error occurred in the getMetadataTree call in MetaDataDiscoveryImpl. Error message :{0}
- Explanation: An error occurred in the getMetadataTree used to set the operations.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1004E: An error occurred in getAdapterTypeSummaries call in MetaDataDiscoveryImpl. Error message :{0}
- Explanation: An error occurred in the getAdapterTypeSummaries used to instantiate the inbound and outbound connection types.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1005E: An error occurred in setFunctionDescriptions call in Service Description class for {0}. Error message:{1}
- Explanation: An error occurred in the setFunctionDescriptions call.
- User Action: Check the logs and take necessary steps to resolve the problem
- CWYFT1006E: An error occurred while creating {0} connection configuration. Error message:{1}
- Explanation: An error occurred in the setFunctionDescriptions call.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1007E: An error occurred while creating the ManagedConnectionFactory properties for the {0} scenario. Error message:{1}
- Explanation: The adapter failed to create Managed Connection Factory properties.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1008E: An error occurred while creating the resource adapter properties for the {0} scenario. Error message:{1}
- Explanation: The adapter failed to create the resource adapter properties.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1009E: An error occurred while creating the Unified properties for the {0} scenario. Error message :{1}
- Explanation: The adapter failed to create the Unified properties.
- User Action: Check the logs and take the necessary steps to resolve the problem.
- CWYFT1010E: An error occurred while creating the ActivationSpec properties for the inbound scenario. Error message :{0}
- Explanation: The adapter failed to create the Activation Spec properties.
- User Action: Check the logs and take the necessary steps to resolve the problem.