Explanation | Unable to locate the required extension point to process a job. |
Action | Contact IBM Support. |
Explanation | Unable to locate the required Java handler class for the extension point. |
Action | Contact IBM Support. |
Explanation | Payload properties are passed from the job manager to the job agent in a JobContext object during the execution of a distribution job. Payload distribution job cannot proceed without these properties. |
Action | Contact IBM Support. |
Explanation | Job execution can not proceed without the required job parameter. |
Action | Resubmit job with the required parameter. |
Explanation | A payload distribution provider is required to process a payload distribution job. The provider may be specified as part of the payload's properties, as part of the job agent's default payload distribution provider configuration, or as a parameter during job submission. |
Action | Ensure the payload distribution provider is available before submitting a payload distribution job. |
Explanation | The payload distribution provider is the name of the extension point that is used to transfer payload between the job manager and job agent, or between the job manager and a remote machine. The name of the provider may be specified as part of the payload's properties in the Payload Registry, as part of the job agent's default payload distribution provider configuration, or as a parameter during job submission. |
Action | Ensure the name of the payload distribution provider is spelled correctly. |
Explanation | An exception was encountered while processing a job. |
Action | Examine the exception message and take corrective action as appropriate. |
Explanation | A managed node with the given UUID already exists. |
Action | Choose a different UUID for the managed node. |
Explanation | Unable to locate a managed node with the specified UUID. |
Action | Specify the UUID of an existing managed node. |
Explanation | The UUID of a managed node may not be changed. |
Action | Do not change UUID of a managed node. |
Explanation | The system is unable to run the job because there is no registered extension that implements the job. |
Action | Verify that the job name is entered correctly. |
Explanation | Internal problem during the execution of the job. |
Action | Check the error message to diagnose the problem. |
Explanation | Server name parameter is required. |
Action | Resubmit the job with a server name parameter. |
Explanation | Application name parameter is required. |
Action | Resubmit the job with an application name parameter |
Explanation | Unable to find the file specificed by the path. |
Action | Check to see if the Properties file is located at the path specified. If correct file is located at desired path, then double check the supplied path parameter. |
Explanation | Clusters are not supported in a base Application Server environment. |
Action | Resubmit the job without a cluster name parameter. |
Explanation | The application could not be located on the managed node. The application needs to be installed. |
Action | Install the application on the managed node before resubmitting the job. |
Explanation | The server could not be located on the managed node. The server may not exist, or you may not have permission to access the server. |
Action | Ensure you have permission to the server, or create the server before resubmitting the job. |
Explanation | Properties file path is a required parameter |
Action | Resubmit the job with a correct Properties file path parameter. |
Explanation | Delete parameter has to be either true, false, or not provided. |
Action | Resubmit the job with a valid delete parameter. |
Explanation | The incorrect parameter is not needed for the job. |
Action | Validate the parameters and resubmit the job. |
Explanation | This informational message indicates that the application was installed. |
Action | No user action required. |
Explanation | This informational message indicates that the application was uninstalled. |
Action | No user action required. |
Explanation | This informational message indicates that the application was updated. |
Action | No user action required. |
Explanation | The application has already been installed. |
Action | Do not install an application that is already installed. Try updating the application, or uninstall the application first. |
Explanation | This informational message indicates that the application was started. |
Action | No user action required. |
Explanation | This informational message indicates that the application was stoppped. |
Action | No user action required. |
Explanation | This informational message indicates that the application cannot be found. |
Action | No user action required. |
Explanation | This informational message indicates that the application does not exist. |
Action | No user action required. |
Explanation | This informational message indicates that the application server already exists on the specified node. |
Action | No user action required. |
Explanation | This informational message indicates that the application server does not exist on the specified node. |
Action | No user action required. |
Explanation | This informational message indicates that the server with configured with a properties file. |
Action | No user action required. |
Explanation | This informational message indicates that the application server was created on the specifed node. |
Action | No user action required. |
Explanation | This informational message indicates that the application server was deleted from the specified node. |
Action | No user action required. |
Explanation | This informational message indicates that the proxy server already exists. |
Action | No user action required. |
Explanation | This informational message indicates that the proxy server does not exist. |
Action | No user action required. |
Explanation | This informational message indicates that the proxy server was created. |
Action | No user action required. |
Explanation | This informational message indicates that the proxy server was deleted. |
Action | No user action required. |
Explanation | This informational message indicates that the selected job is not available in the current profile. |
Action | No user action required. |
Explanation | This informational message indicates that the server was started on the specified node. |
Action | No user action required. |
Explanation | This informational message indicates that the server is already running on the specified node. |
Action | No user action required. |
Explanation | This informational message indicates that the server was stopped on the specified node. |
Action | No user action required. |
Explanation | The server was already stopped on the specified node. |
Action | No user action required. |
Explanation | Server was not started in the allotted time. The server start operation will continue, but may not succeed. |
Action | Check server status to determine whether it has been started. |
Explanation | Node agent MBean required to process the job can not be located. |
Action | Ensure that the node agent is running. |
Explanation | Server MBean required to process the job can not be located. |
Action | Check that the server is running, and reachable from either deployment manager or admin agent. |
Explanation | Unable to process the job due to exceptions. |
Action | Check the exception message. |
Explanation | Unable to process the job due to exceptions. |
Action | Check the exception message. |
Explanation | The cluster returned an unknown state. |
Action | Check the status of the cluster again. |
Explanation | The cluster has not started. |
Action | Check the status of the cluster again. |
Explanation | The cluster has not stopped. |
Action | Check the status of the cluster again. |
Explanation | Not all the members in the cluster have started. |
Action | Check the status of the cluster again. |
Explanation | Not all the members in the cluster have stopped |
Action | Check the status of the cluster again. |
Explanation | Not all the targets have started the application. |
Action | Check the status of the application again. |
Explanation | Not all the targets have stopped the application. |
Action | Check the status of the application again. |
Explanation | The ID is not known to this system. |
Action | Check if the ID has typos or other errors in it. |
Explanation | This is not a valid job manager ID with which any of the managed nodes is registered. |
Action | Check if the ID has typos or other errors in it. |
Explanation | JMX connection could not be established with the job manager. Possible causes include job manager not started; connector data supplied is not correct; authentication failed. |
Action | Ensure the server is running and the connection data are correct. |
Explanation | The cause may be revealed by the embedded job manager exception. |
Action | Analyze the job manager exception and enable job manager trace for further investigation. |
Explanation | The cause may be revealed by the embedded job manager exception. |
Action | Analyze the job manager exception and enable job manager trace for further investigation. |
Explanation | The managed node to register is not in the list returned by command listRegisteredNodes, and this agent can only use registered managed nodes. |
Action | Register the managed node first. |
Explanation | Registration call to the job manager returned empty result. |
Action | Enable trace in the job manager and analyze the output. |
Explanation | Unregistration call to the job manager returned empty result. |
Action | Enable trace in the job manager and analyze the output. |
Explanation | Call to command listRegisteredNodes failed. |
Action | Analyze admin agent trace to see why the call failed. |
Explanation | The managed node is not registered through this agent. |
Action | Ensure the managed node UUID supplied is correct. |
Explanation | System property user.install.root is not defined. |
Action | No user action required. |
Explanation | A directory cannot be created, probably due to a system constraint. |
Action | Find the cause and correct it. |
Explanation | The file for the persistent store is corrupted. |
Action | Find out why the file is corrupted and correct the condition, so in the future the managed nodes can be persisted. |
Explanation | The ID used to retrieve the data is probably wrong. |
Action | Ensure correct ID is used. |
Explanation | This is probably due a system failure. |
Action | Find the cause and correct it. |
Explanation | It can be a connection issue or job manager malfunction. |
Action | Ensure the job manager is working normally, and the connection link is sound. |
Explanation | It can be a connection issue or job manager malfunction. |
Action | Ensure the job manager is working normally, and the conection link is sound. |
Explanation | Could not restore a registered managed node due to unexpected error. |
Action | Find the cause of the error and correct it. |
Explanation | The unregistration will continue, but it might not be cleanly done. |
Action | Find the cause of the error and correct it. |
Explanation | The unregistration will continue, but it might not be cleanly done. |
Action | Find the cause of the error and correct it. |
Explanation | A managed node with the given UUID does not exist in the system configuration, or its configuration file has been corrupted. |
Action | Check system configuration for the managed node. |
Explanation | Unexpected error occurred. |
Action | Report to IBM tech support. |
Explanation | There is not a managed node with the given name in the configuration. |
Action | Check if wrong name was entered. |
Explanation | The managed node does not have the UUID property defined. |
Action | Examine the managed node configuration and ensure it has the UUID property defined. |
Explanation | User-entered job manager URL host name, port number, or managed node name may not be valid. |
Action | Reenter the correct data |
Explanation | An error occurred when trying to create the managed node configuration for the deployment manager. |
Action | See the wrapped exception for the cause of the error. |
Explanation | A connection cannot be established with the job manager. This connection problem most often occurs because the job manager is not running. Job manager polling will continue and any pending information will be exchanged after communication is re-established. |
Action | Ensure that the job manager server is running and the connection information is correct. |
Explanation | A node cannot communicate with a job manager that is at an earlier version. Polling with this job manager is stopped. |
Action | Upgrade the job manager to be the same level or higher than the node. After upgrading the job manager, use the startPollingJobManager command from the deployment manager or admin agent to restart job polling. |
Explanation | Internal error occurred during job processing. |
Action | Make sure that the deployment manager's federated nodes are running. |
Explanation | The job could not be completed due to the parameter. |
Action | Try the command again with valid parameters. |
Explanation | The job could not be completed due to the missing required parameter. |
Action | Try the command again with the required parameter. |
Explanation | The job can only be executed at a Deployment Manager in a WebSphere Network Deployment environment. |
Action | Try the job on a Deployment Manager target. |
Explanation | Internal error occurred during job execution. |
Action | Verify that the job parameters have the correct content and type. |
Explanation | The job could not be completed because the cluster could not be found. |
Action | Verify that the cluster name is correct. |
Explanation | The submitted job was successfully executed. |
Action | Read the message and explanation. |
Explanation | The submitted job was not successfully executed. |
Action | Read the message and explanation. |
Explanation | The submitted job was successfully executed. |
Action | Read the message and explanation. |
Explanation | The submitted job was successfully executed. |
Action | Read the message and explanation. |
Explanation | The submitted job had a parameter with a value that is not valid. |
Action | Provide a correct value for the job parameter. |
Explanation | The job failed because there was an error in the script execution. |
Action | Inspect the SystemOut for errors. |
Explanation | The script to run could not be located. |
Action | Provide the correct script file path. |
Explanation | The cluster member can not be found. |
Action | Ensure you have permission to the cluster, or that the cluster member exists. |
Explanation | Cluster can not be found. Either the cluster does not exist, or you do not have permission to access the cluster. |
Action | Ensure the cluster exists, and that you have permission to the cluster. |
Explanation | The job succeeded. |
Action | Inspect the log file for output from script execution. |
Explanation | The job succeeded. |
Action | Inspect the log file for output from script execution. |
Explanation | The job was received from the job manager and waiting in a queue to be dispatched to the target. |
Action | No user action required. |
Explanation | The job started running on the target. |
Action | No user action required. |
Explanation | The job completed running on the target. |
Action | No user action required. |
Explanation | The user must be assigned the given role either at the cell level, or in at least one authorization group. |
Action | Assign the user the required role for the cell, or in at least one authorization group. |
Explanation | The job failed due to insufficient permission to access a file. |
Action | Assign the user the required permission. |
Explanation | Cannot find the MBean for Application Manager on the server. |
Action | Restart the server and make sure the Application Manager MBean starts. |
Explanation | The job manager stopped after the job was dispatched,but before the job completed. Because the job manager can no longer track the current job status, the job is marked as failed. |
Action | Check the accurate status of the job on the remote host to which the job was dispatched. |