Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Monitored directory application deployment service did not start due to an error. |
Action | Check the log file containing this error and the FFDC log files for more detailed messages. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error occurred during a request to stop the monitored directory application deployment service. The service might have stopped already. |
Action | None if the associated error message indicates that the service was already stopped. Check the log file containing this error and the FFDC log files for more detailed messages. |
Explanation | A new monitored directory application deployment event was detected. This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A request might have been received to uninstall an application that is not currently installed. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This error might be due to a corrupted application file. |
Action | Check the log file containing this error and or FFDC log files for more detailed error messages. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The named application cannot be uninstalled. |
Action | Check the log file containing this error and the FFDC log files for more detailed messages. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This error typically occurs if required resources are missing or misconfigured. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The named application cannot be stopped. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages. |
Explanation | An error occurred when persisting configuration data associated with an install or uninstall operation. |
Action | Check the log file containing this error and or the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | A timeout was exceeded while waiting for the indicated operation on the indicated application. The status of the operation is unknown, and the monitored directory application deployment service will continue processing other operations. |
Action | Retry the operation. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The monitored directory application deployment operation was successful but an error occurred while cleaning up temporary resources. |
Action | No action is required. |
Explanation | A temporary workspace cannot be created. As a result, the monitored directory application deployment service was not started. The failure might be due to insufficient file permissions or an out of space error on the file system. |
Action | Check the log file containing this error and or the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to start an application on the indicated target was unsuccessful. |
Action | Check the log file containing this error and or the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to stop an application on the indicated target was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to start an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to stop an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to start an application on the indicated server was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to stop an application on the indicated server was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | An attempt to synchronize configuration change on the indicated node was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to synchronize configuration change on the indicated node was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error typically occurs if the node agent is not running. |
Action | Check the log file containing this error and or the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An attempt to start an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to stop an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to start an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | An attempt to stop an application on the indicated cluster was unsuccessful. |
Action | Check the log file containing this error and the FFDC log files for more detailed error messages to determine the cause for the failure. |
Explanation | This error occurred might because node agent is not running or application is not installed. |
Action | Check the log file containing this error or FFDC log files for more detailed error messages |
Explanation | No enterprise application archive file exists. |
Action | Check the enterprise application archive file named correctly in the property file. |
Explanation | The specified ResourceType is invalid. Only Application resource type is allowed. |
Action | Check the resource type specified correctly in the property file. |
Explanation | The specified ImplementingResourceType is invalid. Only application or module deployment implementing resource type is allowed. |
Action | Check the implementing resource type specified correctly in the property file. |
Explanation | This message is for informational purposes only. |
Action | No action is required . |
Explanation | This message is for informational purposes only. |
Action | No action is required . |
Explanation | This message is for informational purposes only. |
Action | No action is required . |
Explanation | This error might be due to a corrupted application file. |
Action | Check the report file containing this error for more detailed error messages. |
Explanation | This message is for informational purposes only. |
Action | No action is required . |
Explanation | An attempt to uninstall or update an application was unsuccessfully. |
Action | No action is required . |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The monitored directory application deployment service may be configured through a configuration panel or command. |
Action | No action is required. |
Explanation | An internal application server service, the config service was not initialized correctly. |
Action | Examine trace for earlier error messages related to the config service. |
Explanation | Servers that are cluster members may not be targeted for application install. |
Action | Install to the server in question my installing to its cluster. |
Explanation | The indicated server and node combination do not exist. |
Action | Check that the monitored directory application deployment folders are named correctly. |
Explanation | No servers exist of the given name. |
Action | Check that the monitored directory application deployment folders are named correctly. |
Explanation | No clusters exist of the given name. |
Action | Check that the monitored directory application deployment folders are named correctly. |
Explanation | A monitored directory application deployment event was detected to a server or cluster folder that did not correspond to any existing servers or clusters in the system. As a result, no action was taken. |
Action | No action is required. |
Explanation | The service failed to create a required directory. The monitored directory application deployment root may be set to a location that the service does not have write access to. |
Action | Check file permissions of the indicated file. |
Explanation | The monitored directory application deployment service queries the configuration service to determine what targets to act on. Most likely a configuration error was encountered. |
Action | Examine the associated exception for further information. |
Explanation | An exception occurred while examining a file in a monitored directory application deployment directory. |
Action | Examine associated exception for more information. |
Explanation | Monitored directory application deployment is only supported in network deployment and single server stand-alone topologies. |
Action | No action is required. |
Explanation | Monitored directory application deployment service requires a valid EAR file. |
Action | Examine associated exception for more information. |
Explanation | An attempt to start an application was unsuccessful because no target is specified. |
Action | Update the property file and specify the target (server or cluster or MapModulesToServers task) for the application. |