Explanation | The specified message ID could not be found in the message file; contact IBM support. |
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 | 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 connector you specified using openConnectors option is not one of the supported connectors. |
Action | Make sure you specified the connectors that is supported which are SOAP, RMI, JSR160RMI and IPC. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Node registration cannot continue because it failed to initialize the administrative subystem connectors. |
Action | Review the associated error in the administrative agent logs or turn on administrative agent trace to diagnose the problem. |
Explanation | The administrative agent cannot start the node subsystem because the set of products and versions on the node is not the same as the set of administrative agent products and versions. |
Action | Complete the following steps: 1. Unregister the node from the administrative agent. 2. Ensure that the set of products and versions on the node is the same as the set of administrative agent products and versions. 3. Re-register the node to the administrative agent. |
Explanation | The set of products and versions on the node must be the same as the set of administrative agent products and versions. |
Action | Before you attempt to register a node, ensure that the set of products and versions on the node and the set of products and versions of administrative agent versions are the same. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminAgent node cannot be registered to itself. |
Action | Verify that the node you are registering is not the AdminAgent node itself. |
Explanation | The node cannot be registered without first connecting to an AdminAgent server. |
Action | Verify that the connection you use to the AdminAgent server is correct and that the AdminAgent server is running. |
Explanation | The node is already registered. |
Action | Make sure you register a node that has not been registered. |
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 node cannot be unregistered because it is not registered. |
Action | No action is required. |
Explanation | The node cannot be destroyed because it started. |
Action | Stop the node first then attempt to destroy it. |
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 node cannot be started because it has not been initialized. |
Action | Initialize the node and then start it. |
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 generateProfileKey command failed because it is missing one of the required properties. |
Action | Make sure that you supply all of the required properties when you call the generateProfileKey command. |
Explanation | The specified connector type is not valid. The following connector type are valid: SOAP, RMI, JSR160RMI and IPC. |
Action | Try again using the correct connector type. |
Explanation | The ManagedNode name of the registered node has not been specified. |
Action | If you run the command to connect to an administrative agent, specify the ManagedNode name of the registered node. |
Explanation | Using the local mode, the command cannot be executed from the bin directory of the registered node. |
Action | Connect to an administrative agent when you run the command from the bin directory of the registered node. |
Explanation | An attempt was made to register a node in an unsupported environment. A node can be registered or deregistered only when it runs on the same machine as the administrative agent, which is the AminAgent MBean. |
Action | Register or deregister a node, using the registerNode or deregisterNode operation, when the node is located on the same machine as the administrative agent. The administrative agent is the AdminAgent MBean. |
Explanation | An attempt was made to register a node that has higher level then the administrative agent level. |
Action | Ensure that the node level you are trying to register is less then or equal to the administrative agent level. |
Explanation | The node you are trying to register is not a stand-alone server node. You can register only a stand-alone application server node to an administrative agent. |
Action | Ensure that the node you are trying to register to an administrative agent is a stand-alone application server node. |
Explanation | The node name being used to create a new managed node already exist. |
Action | The node name being used to create a new managed node already exist. You need to specify different name. |
Explanation | An error occured when trying to create managed node. |
Action | Review the associated error or turn on trace to diagnose the problem. |
Explanation | The node could not be registered because it has already been registered. |
Action | Ensure that the node has not been previously registered before attempting to register it. |
Explanation | A client connection for the Cell configuration repository could not be obtained. |
Action | Record the exception information from this message for further problem determination. |
Explanation | Failed to deregister the node, the node may have not been registered yet or the node may have been registered to different AdminAgent. |
Action | Check if the node you are trying to deregister was registered or make sure you try to deregister the node from the correct AdminAgent. |
Explanation | The registerNode command can only be invoked by a user with administrator role. |
Action | Supply administrator user id and password to the registerNode command. |
Explanation | The deregisterNode command can only be invoked by a user with administrator role. |
Action | Supply administrator user id and password to the deregisterNode command. |