ADFS0114=ADFS0114W: A port was not configured for the deployment manager''s administrative functions. File transfer will try to use the default port number "{0}". A problem exists in configured HTTP transports for the deployment manager. Verify that the deployment manager transports are correct and match the ports defined in the admin_host virtualhost configuration by looking at serverindex.xml and virtualhosts.xml files. ADFS0113=ADFS0113E: A problem occurred trying to create a connection to the deployment manager. {0} A connection could not be made to the dployment manager. Verify that the deployment manager is running with no errors by looking at deployment manager server logs. ADFS0112=ADFS0112E: File transfer has failed with the following message: {0} File download failed. Verify that file permissions are set properly and sufficient file system space exists. ADFS0111=ADFS0111E: Unable to find ObjectName for FileTransferServer: {0} The file transfer client was unable to resolve the MBean object name of the file transfer service. Verify that the deployment manager is running with no errors by looking at deployment manager server logs. ADFS0109=ADFS0109E: FileTransferClient failed to get server configuration information: {0} Either a communication problem or other internal error occurred when the node agent tried to contact the deployment manager for file transfer configuration information. Verify the deployment manager is running correctly with no errors by looking at deployment manager server logs. ADFS0108=ADFS0108E: An error occurred creating the transferred file "{0}" The file being transferred could not be written to the file system. Verify that sufficient file system space exists to create the file. ADFS0107=ADFS0107E: The file to download "{0}" does not exist. The file requested for download was not found at the deployment manager. The path for the file being downloaded might not be correct, or a service could be experiencing a problem. Verify that the path is correct for the file being downloaded. Determine whether a service is having the problem. ADFS0106=ADFS0106E: An error occurred writing the transferred file "{0}". {1} During a file upload from the node to the deployment manager a problem occurred either writing the file or communicating with the node. Check the logs files in the ${LOG_ROOT} directory for additional information regarding this error. Verify that the remote host and remote port are correct for file transfer and there is disk space available. ADFS0105=ADFS0105E: The file transfer plug-in can not be loaded. {0} While initializing File Transfer, an exception occurred possibly due to problems loading a class. Verify that the file transfer application installed correctly by checking ${LOG_ROOT}/installFiletransfer.log. If necessary, reinstall the file transfer application. ADFS0104=ADFS0104E: An error occurred accessing the file system. {0} The file service had problems getting properties of a requested property file. Verify that file permissions are set properly. See the first failure data capture (FFDC) log in the ${LOG_ROOT}/ffdc directory for additional information. ADFS0103=ADFS0103E: The directory "{0}" could not be created. During an administrative operation an attempt was made to create the directory named in the error message. Verify that the access rights are set correctly for the directory in error. ADFS0102=ADFS0102E: An error occurred initializing the File Service component. Exception: {0} File services might be unavailable. Unavailability of file services could cause problems with file synchronization, file browsing, or other administrative functions. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ADFS0101=ADFS0101E: An error occurred deactivating the "{0}" MBean. Exception: {1} When the deployment manager or node agent was stopped, the file service MBean could not be deactivated. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ADFS0100=ADFS0100E: An error occurred creating the "{0}" MBean. The deployment manager or node agent could not initialize one of the file service MBeans. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ADFS0161=ADFS0161I: A download was made from the non-standard path {0} A file transfer download was made from an non-standard path. Downloads are typically requested from the download or JobManager subdirectory of the configuration repository temporary directory. This message may be helpful when tracking unusual or unexpected file transfers. ADFS0160=ADFS0160I: An upload was made to the non-standard path {0} A file transfer upload was made to a non-standard path. Uploads are typically made to the upload or JobManager subdirectory of the configuration repository temporary directory. This message may be helpful when tracking unusual or unexpected file transfers. ADFS0143=ADFS0143E: The byte range for the download of the {0} file is not valid. A request was made to download a portion of the file, but the byte range is not valid. The starting index cannot be less than 0, greater than the ending index, or greater than the length of the file. Specify a valid byte range, and retry the operation. ADFS0142=ADFS0142E: The {0} file path cannot be downloaded because it does not exist on the server, or the path that you specified is a directory. The path that you specified does not exist on the server, or you specified a directory path rather than a file path. This error also might result from inconsistent port definitions for the administrative host in the deployment manager virtualhosts.xml and serverindex.xml files. Specify a file that exists on the server, and try the operation again. Ensure that the ports defined for admin_host in virtualhosts.xml match those for WC_adminhost and WC_adminhost_secure in the deployment manager serverindex.xml. ADFS0141=ADFS0141E: The {0} file path cannot be downloaded because it is a location or file type that is not allowed, or the path is not valid. Downloading a file from this path is not allowed for one of the following reasons: downloading from this particular subdirectory is not allowed, files with this extension cannot be downloaded, the path contains a .. directory, or the path ends with an invalid character. The trace log on the target server might provide more information. Retry the operation with a valid path. ADFS0140=ADFS0140E: The file transfer server cannot download the {0} file. The server returned HTTP error code {1}. An unanticipated HTTP error code was returned while attempting to download a file. More information might be available in your trace logs or in the trace logs of the server running the file transfer application. Use the status code to determine and resolve the problem, and then retry the operation. ADFS0136=ADFS0136W: The server cannot locate a port configuration for the administrative functions. Thus, the file transfer service will attempt to use the {0} default port number. A problem exists in the configured HTTP transports for the server. Verify that the server transports are correct and match the port numbers, which are defined in the admin_host virtual host configuration. ADFS0134=ADFS0134I: File transfer is configured with host="{0}", server="{3}", port="{1}", securityEnabled="{2}". The information indicates how file transfer client is configured to communicate with the file transfer server. No user action is required. ADFS0133=ADFS0133E: An error occurred trying to connect to the file transfer server running in the deployment manager. Exception: {0} The file transfer service running at the node agent cannot communicate with the file transfer service at the deployment manager. Verify that the network connection is good. Verify that the ports for deployment manager Web container are configured correctly in the deployment manager server configuration and in the virtual host configuration. ADFS0132=ADFS0132W: The host address of the deployment manager could not be determined. A default of "localhost" is being used. This is not valid for a configuration with more than one machine. The TCP/IP configuration is not correct for the server since more then one machine exists for the configuration. If a node is configured at a machine different that the deployment manager, file transfer cannot occur between the node and the deployment manager. Verify that the host address and domain name server (DNS) configurations are set correctly. ADFS0131=ADFS0131W: The host address of the deployment manager is 127.0.0.1. This is not valid for a configuration with more than one machine. The TCP/IP configuration is not correct for the server since more then one machine exists for the configuration. If a node is configured at a machine different from the deployment manager, file transfer cannot occur between the node and the deployment manager. Verify that the host address and domain name server (DNS) configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search the DNS before the /etc/hosts file. ADFS0130=ADFS0130E: Errors decrypting the password: {0} The password in the sas.client.props file could not be decoded. Verify that the sas.client.props file is not corrupted and the contents for password is correct. ADFS0129=ADFS0129E: Errors occurred trying to read the SAS client configuration file. {0} {1} The sas.client.props file cannot be opened. Verify that the sas.client.props file is in the correct configured location based on the ${WAS_PROPS_DIR} variable. Verify that the file can be opened by checking the file permission. ADFS0128=ADFS0128E: The IBM JSSE package could not be loaded. It is needed to run file transfer in a secure environment. {0} File transfer could not be set up with security enabled. Ensure that the ibmjsse.jar is in the class path. Verify that the SSL port is configured for deployment manager server. ADFS0126=ADFS0126W: A configured port for file transfer service was not found. Default port {0} is being used. The configured port information for the deployment manager Web container was not found in the configuration. Verify that the deployment manager server configuration includes the proper HTTP transports looking at serverindex.xml and virtualhosts.xml files. ADFS0125=ADFS0125E: An exception occurred downloading a file {0}. Exception: {1} The deployment manager could not download a file to the nodeagent. If the exception information contains a Web address, verify that the IP address is correct for the deployment manager. If the IP address is 127.0.0.1, the deployment manager domain name server (DNS) is not configured correctly. ADFS0124=ADFS0124E: An exception occurred uploading a file {0}. Exception: {1} A file could not be uploaded from the node to the deployment manager. If the exception information contains a Web address, verify that the IP address is correct for the deployment manager. If the IP address is 127.0.0.1, the deployment manager domain name server (DNS) is not configured correctly. ADFS0123=ADFS0123E: An error occurred trying to contact the node agent "{0}". Exception: {1} The file transfer server could not contact the file transfer client at the node agent. Verify that the node is running and that no errors initializing the nodeagent. Look at nodeagent logs in the ${LOG_ROOT}/nodeagent directory. ADFS0122=ADFS0122E: The ObjectName "{0}" is not valid. Exception: {1} The file transfer server had an internal error trying to resolve an object name. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ADFS0121=ADFS0121E: An error occurred trying to resolve the MBean reference ObjectName for {0}. Exception: {1} The file transfer server could not resolve the file transfer client's MBean at a specific node. Verify that the node is running and there were no errors initializing the node agent. ADFS0120=ADFS0120E: Can not resolve the MBean reference ObjectName for {0}. The node agent is not running at the remote node. Verify that the node agent is running looking at the nodeagent logs in ${LOG_ROOT}/nodeagent directory. ADFS0119=ADFS0119E: An unexpected exception occurred: {0} File download/upload maybe fail. Verify that file permission are set properly and sufficient file system space exists. Verify that the deployment manager is running with no error by looking at deployment manager server logs.