Problem | The deployment manager or node agent could not initialize one of the File Service MBeans. |
User response | This exception is unexpected. The cause is not immediately known. |
Problem | When the deployment manager or node agent was stopped an error occurred deactivating a File Service MBean. |
User response | This exception is unexpected. The cause is not immediately known. |
Problem | 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. |
User response | This exception is unexpected. The cause is not immediately known. |
Problem | During an administrative operation an attempt was made to create the directory named in the error message. |
User response | If it is a valid user action to create this folder, verify that the access rights are set correctly for the directory in error. |
Problem | While getting properties of a requested file, File Service encountered an error. |
User response | Depending on the specific error, verify that file permissions are set properly. Also the FFDC log may contain additional information. |
Problem | While initializing File Transfer, an exception occurred possibly due to problems loading a class. |
User response | Verify that the file transfer application installed correctly by checking ${"LOG_ROOT"}/installFiletransfer.log. If necessary, reinstall the file transfer application. |
Problem | During a file upload from the node to the deployment manager a problem occurred either writing the file or communicating with the node. |
User response | 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. |
Problem | The file requested for download was not found at the deployment manager. |
User response | 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. |
Problem | An error occurred writing the transferred file to disk. |
User response | Verify that there is sufficient disk space to allow the creation of the file. |
Problem | Either a communication problem or other internal error occurred when the node agent tried to contact the deployment manager for File Transfer configuration information. |
User response | Verify the deployment manager is running correctly with no errors. |
Problem | The file transfer client was unable to resolve the file transfer server's MBean object name. |
User response | Verify that the deployment manager is running with no errors. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | When trying to create a client to the deployment manager an error occurred. |
User response | Verify that the deployment manager is running with no errors. |
Problem | There is a problem in the deployment manager's configured HTTP transports. |
User response | Verify that the deployment manager's transport ports are correct and match the ports defined in the virtualhost, admin_host configuration. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | 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/. |
Problem | The node agent is not running at the remote node. |
User response | Verify that the node agent is running. |
Problem | The file transfer server could not resolve the file transfer client's MBean at a specific node. |
User response | Verify that the node is running and there were no errors initializing the node agent. |
Problem | The file transfer server had an internal error trying to resolve an object name. |
User response | This exception is unexpected. The cause is not immediately known. |
Problem | File transfer server could not contact file transfer client at the node agent. |
User response | Verify that the node is running and there were no errors initializing the node agent. |
Problem | An error occurred uploading a file from the node to the deployment manager. |
User response | 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. |
Problem | An error occurred download a file from the deployment manager to the node agent. |
User response | 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. |
Problem | Configured port information for the deployment manager's web container was not found in the configuration. |
User response | Verify that the deployment manager's server configuration includes the proper HTTP transports. |
Problem | An error occurred setting up file transfer to run with security enabled. |
User response | Ensure that the ibmjsse.jar is in the classpath. Also verify that the SSL port is configured for deployment manager's application server. |
Problem | The sas.client.props file can not be opened. |
User response | 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. |
Problem | An error occurred trying to decode the password in sas.client.props. |
User response | Verify that the sas.client.props file contents are correct. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Verify that the host address and DNS configurations are set correctly. |
Problem | The file transfer service running at the node agent can not communicate with the file transfer service at the deployment manager. |
User response | 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. |
Problem | The information indicates how file transfer client will communicate with the filetransfer server. |
User response | No user action is required. |
Problem | This unsecured version of the filetransfer application does not check for authorization when it uploads or downloads files. Thus, the application might pose a security threat to your environment. Use a secure version of the filetransfer application when administrative security is enabled. |
User response | Use the $WAS_HOME/bin/redeployFileTransfer.jacl script to switch to the secure filetransfer application. |