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/ . |
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/ . |
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/ . |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | File download failed. |
Action | Verify that file permissions are set properly and sufficient file system space exists. |
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. |
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. |
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. |
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. |
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. |
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/ . |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | The information indicates how file transfer client is configured to communicate with the file transfer server. |
Action | No user action is required. |
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. |