ADFS

ADFS0100E: An error occurred creating the "{0}" MBean.
Explanation The deployment manager or node agent could not initialize one of the file service MBeans.
Action 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/ .
ADFS0101E: An error occurred deactivating the "{0}" MBean. Exception: {1}
Explanation When the deployment manager or node agent was stopped, the file service MBean could not be deactivated.
Action 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/ .
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 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/ .
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 deployment manager 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 deployment manager. 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 deployment manager for file transfer configuration information.
Action Verify the deployment manager is running correctly with no errors by looking at deployment manager server SystemOut.log.
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 deployment manager is running with no errors by looking at deployment manager server SystemOut.log.
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 deployment manager. {0}
Explanation A connection could not be made to the dployment manager.
Action Verify that the deployment manager is running with no errors by looking at deployment manager server SystemOut.log.
ADFS0114W: A port was not configured for the deployment manager''s administrative functions. File transfer will try to use the default port number "{0}".
Explanation A problem exists in configured HTTP transports for the deployment manager.
Action 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.
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 deployment manager is running with no error by looking at deployment manager server SystemOut.log.
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 SystemOut.log 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 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/ .
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 SystemOut.log 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 deployment manager.
Action 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.
ADFS0125E: An exception occurred downloading a file {0}. Exception: {1}
Explanation The deployment manager 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 deployment manager. If the IP address is 127.0.0.1, the deployment manager 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 deployment manager Web container was not found in the configuration.
Action Verify that the deployment manager 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 deployment manager 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 deployment manager 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 deployment manager, file transfer cannot occur between the node and the deployment manager.
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 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.
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 deployment manager, file transfer cannot occur between the node and the deployment manager.
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 deployment manager. Exception: {0}
Explanation The file transfer service running at the node agent cannot communicate with the file transfer service at the deployment manager.
Action 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.
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.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Jun 13, 2012 7:39:43 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.fileservice.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)