WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


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 This exception is unexpected. The cause is not immediately known.
ADFS0101E: An error occurred deactivating the "{0}" MBean. Exception: {1}
Explanation When the deployment manager or node agent was stopped an error occurred deactivating a File Service MBean.
Action This exception is unexpected. The cause is not immediately known.
ADFS0102E: An error occurred initializing the File Service component. Exception: {0}
Explanation While initializing File Services, an error occurred which may cause their function to be unavailable. This could cause problems with file synchronization, file browsing, or other administrative functions.
Action This exception is unexpected. The cause is not immediately known.
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 If it is a valid user action to create this folder, verify that the access rights are set correctly for the directory in error.
ADFS0104E: An error occurred accessing the file system. {0}
Explanation While getting properties of a requested file, File Service encountered an error.
Action Depending on the specific error, verify that file permissions are set properly. Also the FFDC log may contain 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 for additional information regarding this error. Depending on the log information, verify there is a good connection and there is disk space available. Verify that the remote host and port look correct for file transfer.
ADFS0107E: The file to download "{0}" does not exist.
Explanation The file requested for download was not found at the deployment manager.
Action Verify that the path is correct for the file being downloaded. If a service such as configuration synchronization is encountering this problem, contact IBM technical support.
ADFS0108E: An error occurred creating the transferred file "{0}"
Explanation An error occurred writing the transferred file to disk.
Action Verify that there is sufficient disk space to allow the creation of 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.
ADFS0111E: Unable to find ObjectName for FileTransferServer: {0}
Explanation The file transfer client was unable to resolve the file transfer server's MBean object name.
Action Verify that the deployment manager is running with no errors.
ADFS0112E: File transfer has failed with the following message: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADFS0113E: A problem occurred trying to create a connection to the deployment manager. {0}
Explanation When trying to create a client to the deployment manager an error occurred.
Action Verify that the deployment manager is running with no errors.
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 There is a problem in the deployment manager's configured HTTP transports.
Action Verify that the deployment manager's transport ports are correct and match the ports defined in the virtualhost, admin_host configuration.
ADFS0119E: An unexpected exception occurred: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
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 This exception is unexpected. The cause is not immediately known.
ADFS0123E: An error occurred trying to contact the node agent "{0}". Exception: {1}
Explanation File transfer server could not contact file transfer client at the node agent.
Action Verify that the node is running and there were no errors initializing the node agent.
ADFS0124E: An exception occurred uploading a file {0}. Exception: {1}
Explanation An error occurred uploading a file from the node to the deployment manager.
Action If the exception information contains URL information, verify that the IP address looks correct for the deployment manager. If the IP address is 127.0.0.1, the deployment manager's DNS is not configured correctly.
ADFS0125E: An exception occurred downloading a file {0}. Exception: {1}
Explanation An error occurred download a file from the deployment manager to the node agent.
Action If the exception information contains URL information, verify that the IP address looks correct for the deployment manager. If the IP address is 127.0.0.1, the deployment manager's DNS is not configured correctly.
ADFS0126W: A configured port for file transfer service was not found. Default port {0} is being used.
Explanation Configured port information for the deployment manager's web container was not found in the configuration.
Action Verify that the deployment manager's server configuration includes the proper HTTP transports.
ADFS0128E: The IBM JSSE package could not be loaded. It is needed to run file transfer in a secure environment. {0}
Explanation An error occurred setting up file transfer to run with security enabled.
Action Ensure that the ibmjsse.jar is in the classpath. Also verify that the SSL port is configured for deployment manager's application server.
ADFS0129E: Errors occurred trying to read the SAS client configuration file. {0} {1}
Explanation The sas.client.props file can not be opened.
Action Verify that the sas.client.props file is in the correct configured location based on the ${WAS_PROPS_DIR} variable and that it can be opened.
ADFS0130E: Errors decrypting the password: {0}
Explanation An error occurred trying to decode the password in sas.client.props.
Action Verify that the sas.client.props file contents are 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 does not appear correct for this type of server. If a node is configured at a machine different that the deployment manager, file transfer will be unable to communicate with the deployment manager.
Action Verify that the host address and DNS configurations are set correctly. For Linux configurations, configure the /etc/nsswitch.conf file to search 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 does not appear correct for this type of server. If a node is configured at a machine different that the deployment manager, file transfer will be unable to communicate with the deployment manager.
Action Verify that the host address and 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 can not 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's web container is configured correctly in the deployment manager's 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 will communicate with the filetransfer server.
Action No user action is required.
Reference topic    

Terms of Use | Feedback

Last updated: Jul 22, 2008 7:04:22 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.fileservice.html

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