Explanation | The exception message might detail the probable cause. |
Action | Check with the JSR-88 compliant tool vendor. |
Explanation | The exception message might detail the probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The port value is a numeric value. A valid URI is of the format "deployer:WebSphere:<host>:<port>" |
Action | Provide a valid URI. |
Explanation | A valid URI is of the format "deployer:WebSphere:<host>:<port>" |
Action | Provide a valid URI. |
Explanation | A connection cannot be established to the deployment server. Either the server is not running or the user ID and password are incorrect. |
Action | Verify that the server is running and that your user ID and password are correct. |
Explanation | A connection cannot be established to the deployment server. Either the server is not running or the user ID and password are incorrect. |
Action | Verify that the server is running and that your user ID and password are correct. |
Explanation | The configuration cannot be read for the server and cluster target information. |
Action |
Explanation | Stop is not supported on the J2EE deployment manager progress object. |
Action | Do not issue the stop operation. |
Explanation | Cancel is not supported on the J2EE deployment manager progress object. |
Action | Do not issue the cancel operation. |
Explanation | Redeploy is not supported on the J2EE deployment manager progress object. |
Action | Do not issue the DeploymentManager.redeploy operation. |
Explanation | At least one of the defined targets on an operation is not valid. |
Action | Verify that the target servers are configured correctly. |
Explanation | This operation cannot run in disconnected mode. |
Action | Get a connected J2EE deployment manager. |
Explanation | Data passed to this API is not correct. |
Action | Correct your program. |
Explanation | The deployment operation is successful. |
Action | No user action is required. |
Explanation | The deployment operation is not successful on any module. |
Action | Look at the error logs to determine why the operation failed. |
Explanation | The deployment operation is partially successful. |
Action | Look at the error logs to determine why the operation failed. |
Explanation | The exception message might detail the probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The exception message might detail the probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The exception message might detail probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The server is probably not started. |
Action | Start the target server to run commands on that server. |
Explanation | An application start is successful. |
Action | No user action is required. |
Explanation | An application stop request is successful. |
Action | No user action is required. |
Explanation | The deplopyment tool listening for ProgressEvents is throwing an exception. |
Action | Correct the handleProgressEvent code causing the error. |
Explanation | An operation is requested on a child module, which is not allowed. |
Action | Use root level modules for start, stop, and undeploy operations. |
Explanation | An incorrect path is specified for the file to deploy. |
Action | Correct the path to the file to deploy. |
Explanation | The exception message might detail the probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The exception message might detail the probable cause. |
Action | Consult the WebSphere Application Server support page: at http://www-306.ibm.com/software/webservers/appserv/was/support/. If problem persists turn on tracing for com.ibm.ws.management.application.*=all=enabled |
Explanation | The node agent must be running if you are deploying in a Network Deployment environment. |
Action | Start the node agent. |
Explanation | At least one of the defined targets on an operation is not valid. |
Action | Verify that the target servers are configured correctly. |
Explanation | The TargetModuleID[] input array is empty. |
Action | Verify that the correct input is provided to this command. |
Explanation | A cluster is not a valid target for stand-alone RAR file distribution. |
Action | Correct your program. |
Explanation | After application deploy or undeploy in the networked environment, the node requires synchronization. The node agent is not running at the target node. |
Action | Start the node agent at the affected node and synchronize the node. |
Explanation | An unexpected error occurred while processing a node synchronization. |
Action | Manually synchronize the affected node. |
Explanation | The Target[] input array is empty. |
Action | Verify that the correct input is provided to this command. |