Express (Distributed operating systems), v8.0 > Reference > Messages
ADFS
ADFS0100E: An error occurred creating the "{0}" MBean.
Explanation The dmgr or node agent could not initialize one of the file service MBeans. Action More info at:
ADFS0101E: An error occurred deactivating the "{0}" MBean. Exception: {1}
Explanation When the dmgr or node agent was stopped, the file service MBean could not be deactivated. Action More info at:
ADFS0102E: An error occurred initializing the File Service component. Exception: {0}
Explanation File services might be unavailable. Unavailability of file services could cause problems with file synchronization, file browsing, or other administrative functions. Action More info at:
ADFS0103E: The directory "{0}" could not be created.
Explanation During an administrative operation an attempt was made to create the directory named in the error message. Action Verify that the access rights are set correctly for the directory in error.
ADFS0104E: An error occurred accessing the file system. {0}
Explanation The file service had problems getting properties of a requested property file. Action Verify that file permissions are set properly. See the first failure data capture (FFDC) log in the ${LOG_ROOT}/ffdc directory for additional information.
ADFS0105E: The file transfer plug-in can not be loaded. {0}
Explanation While initializing File Transfer, an exception occurred possibly due to problems loading a class. Action Verify that the file transfer application installed correctly by checking ${LOG_ROOT}/installFiletransfer.log. If necessary, reinstall the file transfer application.
ADFS0106E: An error occurred writing the transferred file "{0}". {1}
Explanation During a file upload from the node to the dmgr a problem occurred either writing the file or communicating with the node. Action 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.
ADFS0107E: The file to download "{0}" does not exist.
Explanation The file requested for download was not found at the dmgr. The path for the file being downloaded might not be correct, or a service could be experiencing a problem. Action Verify that the path is correct for the file being downloaded. Determine whether a service is having the problem.
ADFS0108E: An error occurred creating the transferred file "{0}"
Explanation The file being transferred could not be written to the file system. Action Verify that sufficient file system space exists to create the file.
ADFS0109E: FileTransferClient failed to get server configuration information: {0}
Explanation Either a communication problem or other internal error occurred when the node agent tried to contact the dmgr for file transfer configuration information. Action Verify the dmgr is running correctly with no errors by looking at dmgr server logs.
ADFS0111E: Unable to find ObjectName for FileTransferServer: {0}
Explanation The file transfer client was unable to resolve the MBean object name of the file transfer service. Action Verify that the dmgr is running with no errors by looking at dmgr server logs.
ADFS0112E: File transfer has failed with the following message: {0}
Explanation File download failed. Action Verify that file permissions are set properly and sufficient file system space exists.
ADFS0113E: A problem occurred trying to create a connection to the dmgr. {0}
Explanation A connection could not be made to the dployment manager. Action Verify that the dmgr is running with no errors by looking at dmgr server logs.
ADFS0114W: A port was not configured for the dmgr''s administrative functions. File transfer will try to use the default port number "{0}".
Explanation A problem exists in configured HTTP transports for the dmgr. Action Verify that the dmgr transports are correct and match the ports defined in the admin_host virtualhost configuration by looking at serverindex.xml and virtualhosts.xml files.
ADFS0119E: An unexpected exception occurred: {0}
Explanation File download/upload maybe fail. Action Verify that file permission are set properly and sufficient file system space exists. Verify that the dmgr is running with no error by looking at dmgr server logs.
ADFS0120E: Can not resolve the MBean reference ObjectName for {0}.
Explanation The node agent is not running at the remote node. Action Verify that the node agent is running looking at the nodeagent logs in ${LOG_ROOT}/nodeagent directory.
ADFS0121E: An error occurred trying to resolve the MBean reference ObjectName for {0}. Exception: {1}
Explanation The file transfer server could not resolve the file transfer client's MBean at a specific node. Action Verify that the node is running and there were no errors initializing the node agent.
ADFS0122E: The ObjectName "{0}" is not valid. Exception: {1}
Explanation The file transfer server had an internal error trying to resolve an object name. Action More info at:
ADFS0123E: An error occurred trying to contact the node agent "{0}". Exception: {1}
Explanation The file transfer server could not contact the file transfer client at the node agent. Action Verify that the node is running and that no errors initializing the nodeagent. Look at nodeagent logs in the ${LOG_ROOT}/nodeagent directory.
ADFS0124E: An exception occurred uploading a file {0}. Exception: {1}
Explanation A file could not be uploaded from the node to the dmgr. Action If the exception information contains a Web address, verify that the IP address is correct for the dmgr. If the IP address is 127.0.0.1, the dmgr domain name server (DNS) is not configured correctly.
ADFS0125E: An exception occurred downloading a file {0}. Exception: {1}
Explanation The dmgr could not download a file to the nodeagent. Action If the exception information contains a Web address, verify that the IP address is correct for the dmgr. If the IP address is 127.0.0.1, the dmgr domain name server (DNS) is not configured correctly.
ADFS0126W: A configured port for file transfer service was not found. Default port {0} is being used.
Explanation The configured port information for the dmgr Web container was not found in the configuration. Action Verify that the dmgr server configuration includes the proper HTTP transports looking at serverindex.xml and virtualhosts.xml files.
ADFS0128E: The IBM JSSE package could not be loaded. It is needed to run file transfer in a secure environment. {0}
Explanation File transfer could not be set up with security enabled. Action Ensure that the ibmjsse.jar is in the class path. Verify that the SSL port is configured for dmgr server.
ADFS0129E: Errors occurred trying to read the SAS client configuration file. {0} {1}
Explanation The sas.client.props file cannot be opened. Action 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.
ADFS0130E: Errors decrypting the password: {0}
Explanation The password in the sas.client.props file could not be decoded. Action Verify that the sas.client.props file is not corrupted and the contents for password is correct.
ADFS0131W: The host address of the dmgr is 127.0.0.1. This is not valid for a configuration with more than one machine.
Explanation 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 dmgr, file transfer cannot occur between the node and the dmgr. Action 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.
ADFS0132W: The host address of the dmgr could not be determined. A default of "localhost" is being used. This is not valid for a configuration with more than one machine.
Explanation 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 dmgr, file transfer cannot occur between the node and the dmgr. Action Verify that the host address and domain name server (DNS) configurations are set correctly.
ADFS0133E: An error occurred trying to connect to the file transfer server running in the dmgr. Exception: {0}
Explanation The file transfer service running at the node agent cannot communicate with the file transfer service at the dmgr. Action Verify that the network connection is good. Verify that the ports for dmgr Web container are configured correctly in the dmgr server configuration and in the virtual host configuration.
ADFS0134I: File transfer is configured with host="{0}", server="{3}", port="{1}", securityEnabled="{2}".
Explanation The information indicates how file transfer client is configured to communicate with the file transfer server. Action No user action is required.
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.
Explanation A problem exists in the configured HTTP transports for the server. Action Verify that the server transports are correct and match the port numbers, which are defined in the admin_host virtual host configuration.
ADFS0140E: The file transfer server cannot download the {0} file. The server returned HTTP error code {1}.
Explanation 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. Action Use the status code to determine and resolve the problem, and then retry the operation.
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.
Explanation 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. Action Retry the operation with a valid path.
ADFS0142E: The {0} file path cannot be downloaded because it does not exist on the server, or the path specified is a directory.
Explanation The path specified does not exist on the server, or you specified a directory path rather than a file path. Action Specify a file that exists on the server, and retry the operation.
ADFS0143E: The byte range for the download of the {0} file is not valid.
Explanation 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. Action Specify a valid byte range, and retry the operation.
ADFS0160I: An upload was made to the non-standard path {0}
Explanation 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. Action This message may be helpful when tracking unusual or unexpected file transfers.
ADFS0161I: A download was made from the non-standard path {0}
Explanation 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. Action This message may be helpful when tracking unusual or unexpected file transfers.