Explanation: | Could not obtain the TCP/IP address of the remote FTP remote host using the remote host name specified in the FTP connection. |
User Response: | Verify that the FTP host name provided in the FTP connection is correct. Contact the FTP system administrator. |
Explanation: | The Integration Service could not create the socket due to insufficient resources such as file descriptors, memory, or permissions on the FTP server. |
User Response: | Contact the FTP system administrator. |
Explanation: | Internal error. |
User Response: | Contact the Informatica Global Customer Support. |
Explanation: | The Integration Service could not connect to the FTP server, possibly because the network is down. |
User Response: | Contact the network administrator. |
Explanation: | The FTP server is not properly configured on the remote machine. |
User Response: | Contact the FTP system administrator. |
Explanation: | The network connection went down after the Integration Service connected to the FTP server. |
User Response: | Contact the network administrator, the FTP system administrator, and the Informatica system administrator. |
Explanation: | The Integration Service does not recognize the FTP protocol. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service lost connection with the FTP server. |
User Response: | Contact the FTP administrator. |
Explanation: | The user name in the FTP connection object is incorrect. |
User Response: | Verify the FTP user name in the Workflow Manager. |
Explanation: | The password in the FTP connection object is incorrect. |
User Response: | Verify the FTP password in the connection object. |
Explanation: | The FTP server denied connection from the Integration Service. |
User Response: | Contact the FTP system administrator. |
Explanation: | The FTP user in the FTP connection object does not have read permissions. |
User Response: | For Windows, verify that the FTP user accessing the file has standard read permissions on the directory of the staged file. For UNIX, prepare the staging directory so that the FTP user who accesses the file also owns the directory. Run the following UNIX command from the directory where you want to generate the file: % chmod g+s |
Explanation: | This is an informational message. The Integration Service checks the existence of a file when you run a file persist session. The first time you run a file persist session, the file does not exist. When the Integration Service does not find the file, it writes this message to the session log. |
User Response: | None. |
Explanation: | The Integration Service could not open the local staging file you specified in the session properties. |
User Response: | Check the session log for further messages. |
Explanation: | The target file was written to the target staging location, but the Integration Service encountered an error while reading the file when transferring it to the target machine. |
User Response: | Check the session log for further messages. |
Explanation: | The Integration Service encountered an error when writing to the source staging file location. |
User Response: | Confirm the staging directory specified in the session properties. |
Explanation: | The FTP user does not have permission to delete the staging file. |
User Response: | Delete the file manually, and contact the administrator of the FTP system to get permission to delete FTP files for future sessions. |
Explanation: | You entered an FTP host name in the wrong format in the Host Name field in the FTP Connection Editor dialog box. |
User Response: | Edit the FTP connection in the Workflow Manager. Specify the host name format as <hostname> or <hostname:port>. |
Explanation: | The Integration Service tried to accessed a file source on an FTP server, but the FTP server did not send any data before the Integration Service timed out. By default, the Integration Service waits 600 seconds before timing out. |
User Response: | Verify the FTP server is still running. If you need to increase the amount of time the Integration Service waits before timing out, contact Informatica Global Customer Support. |
Explanation: | The connection to the FTP server failed. The Integration Service could not reconnect to the FTP server within the retry period for the FTP connection object. |
User Response: | Check the status of the FTP server and run the session again. If the session is enabled for recovery, recover the session. |
Explanation: | The connection to the FTP server for the session failed and the Integration Service reconnected to the FTP server. However, the source file for the session changed since the last time the Integration Service read from the file, and the session failed. |
User Response: | Run the session again. If the session is enabled for recovery, recover the session. |
Explanation: | The connection to the FTP server failed. The Integration Service reconnected to the FTP server and attempted to restart the file transfer. However, the FTP server does not support the REST, MDTM, or SIZE FTP commands, which are necessary to restart the file transfer. As a result, the session failed. |
User Response: | For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP commands. |
Explanation: | The connection to the FTP server failed. The Integration Service reconnected to the FTP server and attempted to restart the file transfer. However, the FTP server does not support the REST, MDTM, or SIZE FTP commands, which are necessary to restart the file transfer. As a result, the session failed. |
User Response: | For a resilient FTP connection, the FTP server must support the REST, MDTM, or SIZE FTP commands. |
Explanation: | The Integration Service transferred some target data to the remote FTP server and the connection failed. Some of the target data was not written to the remote file by the FTP server, and target data no longer exists in the buffer for the DTM process. As a result, data was lost and the Integration Service cannot restart file transfer after reconnecting to the FTP server. |
User Response: | Run the session again. |
Explanation: | The Integration Service encountered an error for the socket. As a result, the session failed. |
User Response: | Correct the error and run the session again. |
Explanation: | The retry period is configured in the FTP connection object, but you do not have the high availability option. The retry period is ignored. |
User Response: | None. |
Explanation: | Could not obtain the TCP/IP address of the remote SFTP remote host using the remote host name specified in the SFTP connection. |
User Response: | Verify that the SFTP host name provided in the SFTP connection is correct. Contact the SFTP system administrator. |
Explanation: | The Integration Service could not create the socket due to insufficient resources such as file descriptors, memory, or permissions on the SFTP server. |
User Response: | Contact the SFTP system administrator. |
Explanation: | The Integration Service could not connect to the SFTP server, possibly because the network is down. |
User Response: | Contact the network administrator. |
Explanation: | The SFTP server is not properly configured on the remote machine. |
User Response: | Contact the SFTP system administrator. |
Explanation: | The host name specified in the FTP connection is not in the format that the Integration Service expects. |
User Response: | Edit the FTP connection in the Workflow Monitor. Specify the host name format as <host name> or <host name:port>. |
Explanation: | The Integration Service could not open the local staging file specified in the session properties. |
User Response: | Check the session log for further messages. |
Explanation: | The target file was written to the target staging location, but the Integration Service encountered an error reading from a local staging file. |
User Response: | Check the session log for further messages. |
Explanation: | The Integration Service encountered an error when writing to the source staging file location |
User Response: | Confirm the staging directory specified in the session properties. |
Explanation: | The SFTP user does not have permission to delete the staging file. |
User Response: | Delete the file manually, and contact the administrator of the SFTP system to get permission to delete SFTP files for future sessions. |
Explanation: | The SSH library that the Integration Service uses is not compatible with the library files on the SFTP server. |
User Response: | Verify that the SFTP server supports the SSH version that the Integration Service uses. |
Explanation: | The Integration Service encountered a socket error. As a result, the session failed. |
User Response: | Review the error message, correct the error, and run the session again. |
Explanation: | The authentication failed. |
User Response: | Verify that the authentication information provided in the FTP connection is valid for the authentication method the SFTP server expects. |
Explanation: | Error related to external library. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The file does not exist or you do not have the permissions to open the file. |
User Response: | Verify the file name and file permissions. |
Explanation: | The public key and private key file names were not provided in the FTP connection. |
User Response: | Specify the public key and private key file name in the FTP connection. |
Explanation: | The Integration Service could not connect to the SFTP server, possibly because the network is down. |
User Response: | Contact the network administrator. |
Explanation: | The SFTP server is not properly configured on the remote machine. |
User Response: | Contact the SFTP system administrator. |
Explanation: | The remote file name in the FTP connection object was not specified. |
User Response: | Specify the remote file name in the FTP connection object. |
Explanation: | The public key or private key file was not specified correctly. |
User Response: | Verify that the correct file name and file path is specified in the FTP connection object. |