Explanation | This is an informational message indicating that the addNode program has started. |
Action | No user action is required. |
Explanation | An exception occurred while attempting to attach to the server and obtain its state. |
Action | Record the exception information from this message for further investigation. |
Explanation | This is an informational message indicating that the addNode program has successfully completed. |
Action | No user action is required. |
Explanation | An exception occurred during configuration synchronization while waiting for an asynchronous operation on the Deployment Manager. |
Action | Record the exception information from this message for further investigation. |
Explanation | An error occurred during configuration synchronization. If the error was encountered during addNode, the configuration will be rolled back to the base configuration. If this error was encountered during syncNode, node and cell repositories may be out of synchronization with each other. |
Action | Examine the log files for additional problem determination information. |
Explanation | The client utility program was not able to establish a connection to the Deployment Manager using the information provided. |
Action | Check that the Deployment Manager host and port are reachable from the system on which the utility is being executed. One method to check connectivity is to use the TCP/IP "ping" command. If security is enabled, ensure the user and password are specified correctly. |
Explanation | The program was not able to copy a file. There may not be enough disk space or there may be a problem reading the file. |
Action | Check the available disk space on the system. Check that the file does exist and is readable. |
Explanation | A query to locate an MBean failed. |
Action | Record the exception information in this message for further investigation. |
Explanation | This is an informational message indicating that the program has established communications with the Deployment Manager. |
Action | No user action is required. |
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 | Configuration files for the new node could not be uploaded to the deployment manager for creation in the cell repository. |
Action | Ensure that the deployment manager is running and that the FileTransfer application is running in the deployment manager. Record the exception information from this message for further problem determination. If the Java(TM) virtual machine (JVM) OutOfMemoryError error is in the stack trace in the addNode.log file, the heap size for the addNode command or the deployment manager might need to be increased. For the addNode command, add the -Xmx(size) parameter to the addNode command. |
Explanation | The addNode command created the configuration files for the node agent for the new node. |
Action | No user action is required. |
Explanation | The specified document exists at the cell level. |
Action | No user action is required. |
Explanation | Configuration files from the node are being uploaded to the cell repository that the deployment manager manages. |
Action | No user action is required. |
Explanation | The original configuration files are saved before the utility program changes them. |
Action | No user action is required. |
Explanation | Configuration synchronization is occurring between a node and a cell. |
Action | No user action is required. |
Explanation | The close method of an I/O stream object issued an exception. This probably is a secondary exception that came after an earlier I/O failure. |
Action | Record and save the exception information in this message for further problem determination. Examine the log file for the utility and rerun the program with the -trace option. |
Explanation | The node agent process is starting. |
Action | No user action is required. |
Explanation | The read method of an I/O stream issued an exception. |
Action | Record and save the exception information in this message for further problem determination. Examine the log file for the utility and rerun the program with the -trace option. |
Explanation | The configuration for the specified node agent process is being read. |
Action | No user action is required. |
Explanation | An attempt was made to stop the specified server, but the server did not stop. |
Action | Examine the log files for the server to see why the server is not stopped. |
Explanation | The node agent launched and is waiting for initialization status. |
Action | No user action is required. |
Explanation | An IOException was issued while the program was waiting for input on the server status port. |
Action | Record and save the exception information from this message for further problem determination. Examine the log file for the utility and rerun the program with the -trace option. |
Explanation | The original configuration files are saved before they the utility program changes them. |
Action | No user action is required. |
Explanation | The connected process does not have a DeploymentManager MBean. The most common cause is that the specified host or port is not for the deployment manager. |
Action | Verify that the host and port passed to the tool are correct. |
Explanation | If the addNode process cannot complete, an attempt is made to restore the configuration to its original state. However, the restoration might also fail to complete. |
Action | Review the associated messages in the addNode.log file to determine the specific problem, and retry the addNode command. You might need to run the cleanupNode command before retrying the addNode command, if the rollback did not complete as expected. |
Explanation | If the addNode process cannot complete, an attempt is made to restore the configuration to its original state. However, the restoration might also fail to complete. |
Action | Review the associated messages in the addNode.log file to determine the specific problem, and retry the addNode command. You might need to run the cleanupNode command before retrying the addNode command, if the rollback did not complete as expected. |
Explanation | A log was generated. |
Action | No user action is required. |
Explanation | The node could not be removed. |
Action | Examine the exception to determine the specific problem and take corrective action. |
Explanation | This is an informational message indicating that the node agent process started without errors. |
Action | No user action is required. |
Explanation | The node agent process returned an unsuccessful status value. |
Action | Examine the log files for the node agent to perform additional problem determination. |
Explanation | The addNode program only applies to base app server nodes, not the ND deployment manager node itself. |
Action | Do not attempt to run addNode on the Deployment Manager node itself. |
Explanation | You cannot run the addNode command on a node that has already been added to a cell. |
Action | Do not attempt to run addNode twice on the same node. |
Explanation | The cell name of the ND manager node must be unique within the cell. |
Action | Ensure that the cell name of the deployment manager is unique within the cell. |
Explanation | The Express node could not be added to a Network Deployment cell because an Express node is not supported in a Network Deployment environment. |
Action | Do not attempt to add the node. |
Explanation | The local host can look up the deployment manager host, but the deployment manager cannot look up the new node. The situation can occur if the Dynamic Host Configuration Protocol (DHCP) does not interact with domain name servers (DNS). |
Action | Try using a static IP address if the DHCP does not interact with the DNS. If the host name is not fully qualified,try updating the host name. To update the host name, specify the -nodeName parameter and the -hostName parameter on the changeHostName command of the AdminTask object. |
Explanation | The local node cannot look up the deployment manager host name that is specified in the deployment manager configuration. |
Action | Do one of the following actions: - Add the deployment manager host name to the DNS. - Fully qualify the deployment manger host name in the deployment manager server index configuration. -Add the DNS of the domain to the TCP/IP configuration of the node. |
Explanation | The deployment manager host name is not resolving correctly. |
Action | Verify that the host name is configured properly at the deployment manager. For Linux systems, modify either the /etc/hosts file or the /etc/nsswitch.conf file to search the domain name server (DNS) before files. |
Explanation | You cannot run the addNode command to add a node to a cell which already contains a node of the same name. |
Action | Do not attempt to run the addNode command to add a node to a cell already containing a node of the same name. |
Explanation | An MBean call failed. |
Action | Record and save the exception information from this message for further problem determination. |
Explanation | Concurrent addNode and removeNode operations are not allowed. |
Action | Wait until the first addNode or removeNode operation completes, and then retry this operation. |
Explanation | The lock used to prevent concurrent addNode and removeNode operations could not be reset. |
Action | If you can not run an addNode or removeNode operation after receiving this message, you can clear the lock by invoking the AdminOperations.forceNodeFederationOrRemovalTokenReset operation. |
Explanation | The node you are trying to federate still registered to an AdminAgent. |
Action | You need to unregister the node from an AdminAgent before being able to federate to DeploymentManager. |
Explanation | Whether the specified node could join the specified node group could not be determined. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The specified node group could not be converted to a sysplex node group for the specified node. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The specified node could not be added to the specified node group. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | Removal of the specified node from all node groups failed. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | One or more warnings occurred while checking whether the node can join the node group. |
Action | No user action is required.. |
Explanation | One or more warnings occurred while converting the node group to a sysplex node group. |
Action | No user action is required.. ADMU0060W is issued for each warning message encountered. |
Explanation | One or more warnings occurred while adding the node to the node group. |
Action | No user action is required.. |
Explanation | One or more warnings occurred while removing the node from all the node groups. |
Action | No user action is required.. |
Explanation | The configuration files for the node are being uploaded to the cell repository that the deployment manager manages because the specified node is being removed from all the node groups. |
Action | No user action is required. |
Explanation | The configuration files for the node are being uploaded to the cell repository that the deployment manager manages because the specified node is being added to the specified node group. |
Action | No user action is required. |
Explanation | The options are mutually exclusive. |
Action | Specify the correct option. |
Explanation | The -nodeagentshortname option is ignored on operating systems other than the z/OS operating system. |
Action | Use the option on the z/OS operating system only. |
Explanation | The signer certificates could not be retrieved from the deployment manager. The user name, password, or both might be incorrect. |
Action | Verify that the user name and password are correct. Alternatively, use the retrieveSigners script to download the signer certificates from the deployment manager. |
Explanation | The server name does not match the process attributes. |
Action | Check that the name is spelled correctly. |
Explanation | The rollback of the application binaries failed. |
Action | Consult the addNode.log file for additional information. |
Explanation | The program did not finish because of the specified error. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The code that attempts to update the serverindex.xml configuration file failed and issued an exception. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be written to. |
Explanation | The program did not finish because of the specified error. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The node agent process for the new node failed to launch. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the process failed to launch. |
Explanation | Trace has been enabled. |
Action | No user action is required. |
Explanation | Tool information is being logged to the specified file. |
Action | No user action is required. |
Explanation | The application already exists in the cell configuration repository and uses a different URL for the location of its binaries. The application cannot be merged with the cell configuration and will be ignored. |
Action | Install the application on the deployment manager if it is to be used in servers for this cell. |
Explanation | The log file could not be written to the specified location. Permissions or a security issue might be a cause of the problem. |
Action | Use the -logfile option to specify a new location for the logfile. |
Explanation | Expansion of the application enterprise archive (EAR) files to appropriate locations failed because the addNode command failed. |
Action | Use the EARExpander tool to expand the application EAR files to their appropriate destination. The destination is specified in the binariesURL attribute of the deployment.xml file in the repository. |
Explanation | File already exists. |
Action | No user action is required. |
Explanation | The check, to determine if the application already exists in the repository to which the node is being added, failed. The application will not be uploaded as a part of the addNode command even if the -includeapps option is specified. |
Action | After the addNode command finishes, install the application using either the administrative console or the wsadmin tool. |
Explanation | Unexpected exception in file copy. |
Action | Manually copy files. |
Explanation | The specified message ID could not be found in the message file. |
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 | To add a node, the system clock of the node to be added must be fairly close to that of the deployment manager. |
Action | Change the new node system clock to be the same as that of the deployment manager. |
Explanation | The addNode command failed because the clock of the new node is out of synchronization with the deployment manager. |
Action | Change the clock of the new node to be within the specified minutes of the clock of the deployment manager. |
Explanation | The deployment manager version is earlier than that of the specified node. The product requires that the deployment manager version be at the same version as the node, or at a later version. The node has not been added to the cell. |
Action | Upgrade the deployment manager to the same version as the node, or a later version than the node. |
Explanation | The deployment manager version is earlier than that of the specified node. The product requires that the deployment manager version be at the same version as the node, or at a later version. |
Action | Upgrade the deployment manager to the same version as the node, or a later version than the node. |
Explanation | If -profileName is passed, that specified profile will be used. If run from a profile''s bin directory, that profile will be used. Otherwise the default profile is used. This message just clarifies the profile used. |
Action | You may want to verify that the profile listed in this message is the desired profile. |
Explanation | The deployment manager version is earlier than that of the node. The product requires that the deployment manager version be at the same version as the node, or at a later version. |
Action | Upgrade the deployment manager to the same version as the node, or a later version than the node. |
Explanation | The server short name already exists in the distributed cell to which this node is being added. |
Action | Ensure that the short name is unique across all the servers in the distributed cell before running the addNode command. Make the server short name in the deployment manager cell unique. Then run the addNode command. |
Explanation | The cluster transition name already exists in the distributed cell to which this node is being added. |
Action | Ensure that the cluster transition name is unique across all the servers in the distributed cell before running the addNode command. Make the cluster transition name unique in the deployment manager cell. Then run the addNode command. |
Explanation | The node short name already exists in the distributed cell to which this node is being added. |
Action | Ensure that the node short name is unique across all the nodes in the distributed cell before running the addNode command. Make the node short name unique in the deployment manager cell. Then run the addNode command. |
Explanation | The node agent short name already exists in the distributed cell to which this node is being added. |
Action | Ensure that the node agent short name is unique across all the nodes in the distributed cell before running the addNode command. Make the node agent short name unique in the deployment manager cell. Then run the addNode command. |
Explanation | This is an informational message indicating that additional information is available in the log file. |
Action | Look in the file for additional information. |
Explanation | The code that attempts to upload the plugin-cfg.xml configuration file failed and issued an exception. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be accessed. |
Explanation | The specified node has been successfully renamed. |
Action | No user action is required. |
Explanation | The process of renaming the node has started. |
Action | No user action is required. |
Explanation | The paricular node configuration is updated. |
Action | No user action is required. |
Explanation | The specified node was successfully added to the specified cell. |
Action | No user action is required. |
Explanation | None |
Action | No user action is required. |
Explanation | The configuration on the specified deployment manager was updated. |
Action | No user action is required. |
Explanation | Because the -includeapps option of the addNode command was not specified, applications installed on the stand-alone node were not installed on the new cell. |
Action | No user action is required. |
Explanation | None |
Action | No user action is required. |
Explanation | This message indicates that at least one message immediately follows this message and that you should read any messages that immediately follow this one. |
Action | No user action is required. |
Explanation | This message suggests that you do the actions associated with the messsages that immediately follow this message. |
Action | No user action is required. |
Explanation | The specified node and its associated applications were successfully added to the specified cell. |
Action | No user action is required. |
Explanation | The specified node is being synchronized with the deployment manager. |
Action | No user action is required. |
Explanation | The specified node was successfully synchronized with the deployment manager. |
Action | No user action is required. |
Explanation | The syncNode command is a recovery tool that performs an offline synchronization operation. To avoid interference, the node agent must be stopped prior to running the syncNode command. |
Action | Stop the node agent before running the syncNode command, or use the normal synchronization facility in the administrative console or the NodeSync MBean in wsadmin. |
Explanation | The status of the specified service is being retrieved. |
Action | No user action is required. |
Explanation | Neither the server name nor the -all argument was specified on the serverStatus command. |
Action | Either specify the server name or the -all argument on the serverStatus command. |
Explanation | The server status is being retrieved for all servers. |
Action | No user action is required. |
Explanation | This is an informational message printed before a list of servers. |
Action | No user action is required. |
Explanation | The server name is displayed. |
Action | No user action is required. |
Explanation | The servers directory is empty in the configuration. |
Action | Check the integrity of the configuration files. |
Explanation | The state of the specified server is given. |
Action | No user action is required. |
Explanation | The server cannot be reached and seems to be stopped. |
Action | No user action is required. |
Explanation | The state of the specified server is given. |
Action | No user action is required. |
Explanation | The server cannot be reached and seems to be stopped. |
Action | No user action is required. |
Explanation | A Java Management Extensions (JMX) connector type was requested that is not supported. |
Action | Request a connector type that is supported. |
Explanation | No node was located in the configuration repository with the specified name. |
Action | Check the spelling of the node name. Check the integrity of the configuration files. |
Explanation | No server was located in the configuration repository by the specified name. |
Action | Check the spelling of the server name. Check the integrity of the configuration files. |
Explanation | The queue manager is being created for the specified node on the specified server. |
Action | No user action is required. |
Explanation | Embedded messaging was not installed. The queue manager was not created. |
Action | No user action is required. |
Explanation | The details of the queue manager creation cannot be seen in the specified file. |
Action | Look in the file for more information on the queue manager creation. |
Explanation | The queue manager is being deleted on the specified node and the specified server. |
Action | No user action is required. |
Explanation | Embedded messaging support is not installed. The queue manager cannot be deleted from the specified server. |
Action | No user action is required. |
Explanation | You can see the details of the deletion of the queue manager in the specified file. |
Action | Look in the file for more information. |
Explanation | When the removeNode command runs, the applications from the original configuration are put back in place. Something caused the command to fail. Manual recovery is necessary. |
Action | Use the EARExpander command to expand the application enterprise archive (EAR) file to the location specified on the binariesURL attribute. The attribute is in the corresponding deployment.xml configuration file. |
Explanation | You can use the trace option to gather additional information. |
Action | Consider using the -trace option on the command line. |
Explanation | The node agent could not be registered as a Windows service. |
Action | Check the addNode.log file for additional information. |
Explanation | There was a problem found while de-registering node agent as Windows service. |
Action | Check addNode.log for additional information. |
Explanation | You must specify "-serviceUserName" and "-servicePassword" together. You must also specify "-registerService" |
Action | Obtain values for the above and resubmit request. |
Explanation | Removal of the node has started. |
Action | No user action is required. |
Explanation | The file was not located. |
Action | Check that a setupCmdLine file exists in the installation. |
Explanation | An exception occurred. |
Action | Record the exception data and perform further problem determination. |
Explanation | All server processes are being stopped for the specified node. |
Action | No user action is required. |
Explanation | The product configuration is being backed up. |
Action | No user action is required. |
Explanation | The original product configuration is being restored. |
Action | No user action is required. |
Explanation | This is an informational message explaining that the -force option can be used to eliminate the message. |
Action | No user action is required. |
Explanation | The node configuration files remain in the cell configuration repository. |
Action | If the -force option is used, run the cleanupNode utility on the deployment manager to remove the configuration files for this node. |
Explanation | The local configuration file has been restored. |
Action | No user action is required. |
Explanation | The specified node has been removed from the deployment manager configuration. |
Action | No user action is required. |
Explanation | The installed applications are being removed from the specified node. |
Action | No user action is required. |
Explanation | A problem occurred attempting to remove the applications from this node. |
Action | Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. |
Explanation | This is an informational message marking the progress of the program. |
Action | No user action is required. |
Explanation | The specified cluster member is being removed from the specified cluster. |
Action | No user action is required. |
Explanation | A problem occurred attempting to remove the servers from the clusters. |
Action | Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. |
Explanation | The specified node has been successfully removed. |
Action | No user action is required. |
Explanation | This node was removed from the cell, but problems occurred during the removal. |
Action | Examine the previous errors to determine what occurred. You might need to run the cleanupNode utility to remove this node from the deployment manager configuration. |
Explanation | An attempt was made to remove a node that has never been added in the first place. |
Action | Run the addNode command before attempting to run the removeNode command. |
Explanation | The variable map could not be created. Applications might not be restored or deleted from their binary Web address. |
Action | Run the EARExpander tool to expand the application enterprise archive (EAR) files to their appropriate locations. |
Explanation | The enterprise archive (EAR) file could not be expanded to the destination. |
Action | Run the EARExpander tool to expand the EAR file to its appropriate locations. |
Explanation | The enterprise archive (EAR) file could not be obtained from the specified location. The EAR file will not be expanded to the specified destination. |
Action | Run the EARExpander tool to expand the EAR file to its appropriate locations. |
Explanation | The specified deployment.xml file could not be loaded to obtain the value of the binariesURL attribute. The enterprise archive (EAR) file will not be expanded or deleted from that location. |
Action | Run the EARExpander tool to expand the EAR file to its appropriate location. Alternatively, delete the directory of the EAR file that was supposed to be deleted. |
Explanation | If the addNode command, with the -includeapps option specified, previously uploaded any applications to the specified cell, the removeNode command did not uninstall any of those applications. |
Action | No user action is required. |
Explanation | You can use the wsadmin tool or the administrative console to uninstall applications from the deployment manager. |
Action | No user action is required. |
Explanation | If the addNode command, with the -includebuses option specified, previously uploaded any buses to the specified cell, the removeNode command did not uninstall any of those buses. |
Action | No user action is required. |
Explanation | You can use the wsadmin tool or the administrative console to uninstall any buses from the deployment manager. |
Action | No user action is required. |
Explanation | The removeNode tool could not remove the node because the node was created during cell profile creation. |
Action | Use the manageprofiles command to delete the node. Run the cleanupNode command on the deployment manager. |
Explanation | The node can be removed manually if error messages or warning messages resulted from running the removeNode command. |
Action | Use the manageprofiles command to delete the profile for this node. Run the cleanupNode command on the deployment manager. |
Explanation | The host names for the deployment manager and for the node being federated do not match. This mismatch might be an indication of an unsupported configuration. The local operating system registry will not work across multiple machines, except in special cases. These special cases include having a cell reside exclusively on the z/OS operating system, or be part of a Microsoft Windows domain controller. |
Action | Verify that the node being federated is the intended node, and that the active user registry is supported. For more information, refer to the information center documentation on the supported configurations that can be used with the local operating system registry. If the registry is not supported, change the active user registry to a registry that is supported either through the administrative console or scripting. |
Explanation | The product extensions installed on the node or the deployment manager could not be determined. |
Action | Examine the exception to determine the specific problem. |
Explanation | The operation cannot be completed because the product extensions do not match between the node and the deployment manager. |
Action | Check the product extensions installed on both the node and the deployment manager. Additional product extensions might need to be installed. |
Explanation | The specified custom property was found, but has no value. |
Action | Examine the configuration to be certain a value is specified for the custom property. |
Explanation | The operation will continue even though the product extensions do not match. |
Action | Ensure the necessary product extensions are installed on the node to support any subsequent operations and configurations applied to it. Additional product extensions may need to be installed. |
Explanation | If the addNode command uploaded any security domains to the specified cell, the removeNode command did not remove these security domains. |
Action | No user action is required. |
Explanation | You can use the deleteSecurityDomain task with the force option to remove any unused security domains. You can also manually delete the security domains that are not required any more. |
Action | No user action is required. |
Explanation | The specified server has started. |
Action | No user action is required. |
Explanation | The specified server is recovering. |
Action | No user action is required. |
Explanation | A more detailed exception has occurred while attempting to start or stop the named server. This message is always paired with a second message that displays the detailed exception. |
Action | Record and save the exception information in the follow-on message for further problem determination. |
Explanation | Some general exception condition has been discovered. |
Action | Combine this information with additional exception messages in order to perform additional problem determination. |
Explanation | An exception occurred while the program was listening to the status socket for the server. The server process failed to start. |
Action | Record and save the exception information in this message for further problem determination. |
Explanation | The server process failed to start. |
Action | Examine the log files to see what failure messages were recorded there. |
Explanation | A free port could not be allocated to communicate server status. |
Action | Examine the log file for the utility to perform further problem determination. Attempt to run the utility again. |
Explanation | The server has completed recovery and has stopped. |
Action | No user action is required. |
Explanation | The server had problems during recovery and has stopped. |
Action | Examine the log files to see what failure messages were recorded there. |
Explanation | An exception was issued while the server was in the process of stopping. |
Action | Examine the log files for the server to see why the stop function issued an exception. |
Explanation | An attempt has been made to start a server that is already running. |
Action | Do not attempt to start a server that is already running. |
Explanation | A port required by this server is already in use by this or another server. |
Action | Do not attempt use a port that is already in use. |
Explanation | The server initialization process has exceeded the timeout limit. |
Action | Perform problem determination on the server to check for possible errors. |
Explanation | The MBean of type Server appears to be missing from the process. |
Action | Check that the named server is actually running on the host and port specified. |
Explanation | A query to locate an MBean failed. |
Action | Check that the server process is still running. Examine the log files for the program to perform further problem determination. |
Explanation | The amount of time taken for server shutdown exceeded the -timeout value requested. |
Action | Use a larger value for the -timeout option or perform problem determination on the server to investigate possible errors. |
Explanation | The server configuration is being read. |
Action | No user action is required. |
Explanation | The specified hot and the specified port were used. |
Action | No user action is required. |
Explanation | The stop request failed. Additional information is supplied in other messages. |
Action | Record the failure information from the other messages and perform problem determination on the server to investigate why it failed to stop. |
Explanation | The server process launched. The product is waiting for initialization status. |
Action | No user action is required. |
Explanation | A request to stop the server was made. The product is waiting for server status. |
Action | No user action is required. |
Explanation | The server initialized. The product is waiting for application initialization. |
Action | No user action is required. |
Explanation | The server launch script has been successfully created. |
Action | No user action is required. |
Explanation | The -nowait option was used for the startServer command, so no initialization status is available for the launched process. |
Action | No user action is required. |
Explanation | A stop server request was issued without a stop status request. |
Action | No user action is required. |
Explanation | This tool requires that a server name be provided. |
Action | Specify a server name. |
Explanation | The specified server name cannot be located within the configuration for this node. |
Action | Check that the specified name is spelled correctly and that a directory by that name does exist under the servers directory in the configuration. |
Explanation | The stopServer command completed successfully. |
Action | No user action is required. |
Explanation | An error occured when the program ran. |
Action | Remove the "-script" option and rerun the command. |
Explanation | An error occurred during program execution. |
Action | Perform problem determination to investigate possible causes. |
Explanation | This is an informational message indicating where to look for further information. |
Action | Look in the file for more information. |
Explanation | The tool could not contact the remote server because of a credentials problem. |
Action | Pass in the correct user name and password. If you are using a command, pass in -username & -password, or update the soap/sas.client.props file. |
Explanation | A connection to the server could not be established. |
Action | Ensure that the targeted process is running. Ensure that the proper user name and password are used when attempting to connect to the process in secure mode. |
Explanation | A connection could not be made to the deployment manager. |
Action | Ensure that the deployment manager is running. Ensure that the proper host name and port are used when attempting to connect to the process. |
Explanation | The trace option can be used to obtain a full trace of the failure. |
Action | No user action is required. |
Explanation | The specified configuration directory is being backed up to the specified file. |
Action | No user action is required. |
Explanation | The specified number of files were backed up. |
Action | No user action is required. |
Explanation | The file specified containing the backed up configuration documents cannot be found. |
Action | Verify that the file given to the restoreConfig command exists and can be read. |
Explanation | The specified directory for the restored configuration already exists and is being renamed to the specified directory. |
Action | No user action is required. |
Explanation | The location of the restored configuration could not be renamed. |
Action | Use the -location option on the restoreConfig command to specify a location which does not exist, or which can be renamed. |
Explanation | The specified locatino has been renamed. |
Action | No user action is required. |
Explanation | The specified file is being restored to the specified location. |
Action | No user action is required. |
Explanation | The specified number of files were successfully restored. |
Action | No user action is required. |
Explanation | Preparation of applications has begun. |
Action | No user action is required. |
Explanation | Preparation of assets has begun. |
Action | No user action is required. |
Explanation | Processing complete. |
Action | No user action is required. |
Explanation | NONE |
Action | No user action is required. |
Explanation | The exception message may detail probable cause. |
Action | If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear. |
Explanation | This backup file was created from a system with a different cell name. |
Action | Either use the "-force" option on the restoreConfig command and manually correct the problems, or restore the cell using a backup file that used the same cell name as the current system. |
Explanation | This backup file was created from a system with a different cell name. |
Action | After the restore operation has completed, correct any resulting problems and confirm proper system function before starting production applications. |
Explanation | The disk might be full, or the directory might not have write permission. |
Action | Use EARExpander command to extract the enterprise archive (EAR) file. |
Explanation | The disk might be full, or the directory might not have write permission. |
Action | Use EARExpander command to extract the archive file. |
Explanation | When a server is registered to run as a Windows Service, the Windows Service is used to start the server. |
Action | No user action is required. |
Explanation | When a server is registered to run as a Windows Service, the Windows Service is used to stop the server. |
Action | No user action is required. |
Explanation | When a server is removed, the corresponding Windows service is removed from the registry. |
Action | No user action is required. |
Explanation | The Windows service associated with this server failed to start. |
Action | Check the return code and correct the problem. Then retry the operation. |
Explanation | The Windows Service associated with this server failed to stop. |
Action | Check return code and correct the problem then retry the operation. |
Explanation | The Windows service associated with this server could not be removed from the registry. |
Action | Examine the error message and make correction accordingly. |
Explanation | The Windows service associated with this server could not be found. |
Action | Verify that a Windows service associated with the specified server exists. |
Explanation | The log file for the Windows service associated with this server could not be found. |
Action | Verify that the product installation is correct. |
Explanation | An unexpected exception has been detected. |
Action | Verify that the product installation is correct. |
Explanation | An unexpected exit code was returned from WASService.exe |
Action | Verify WebSphere installation and Windows environment; try running command manually; contact IBM support. |
Explanation | An unexpected exception has been detected. |
Action | Verify that the product installation is correct. |
Explanation | The status for the Windows service could not be obtained. |
Action | Verify that the product installation is correct. |
Explanation | Another command is running and might conflict with this one. |
Action | Wait a few minutes and try the command again. |
Explanation | The generic server started successfully. |
Action | No user action is required. |
Explanation | An attempt was made to start a generic server that has already been started. |
Action | Use "stopServer.(bat|sh)" to stop the generic server, then retry the startServer command or use the "-forceGenericServerStart" option to try to force the start of the generic server. |
Explanation | The generic server successfully stopped. |
Action | No user action is required. |
Explanation | An attempt was made to stop a generic server that is not running. |
Action | Ensure that the generic server is running before attempting to stop it. |
Explanation | If an error occurs during the registerNode command process and it cannot complete, an attempt is made to restore the configuration to its original state, though this might also fail to complete. |
Action | Review the associated messages in the registerNode.log file to determine the specific problem. Retry the registerNode command. |
Explanation | Exchanging signers between adminagent and node will be registered. |
Action | No user action is required. |
Explanation | The registerNode command failed. The configuration is being rolled back to the original configuration. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | The original configuration files are being saved before the utility program changes them. |
Action | No user action is required. |
Explanation | Security admin preferred authorization mechanism is set to RSAToken. |
Action | No user action is required. |
Explanation | The profile could not be removed from the registry. |
Action | Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. |
Explanation | Exchanged security signers successfully. |
Action | No user action is required. |
Explanation | The original configuration files are being restored after the profile was removed from the registry. |
Action | No user action is required. |
Explanation | The node will be deregistered with an adminagent. |
Action | No user action is required. |
Explanation | Registration of the profile has begun. |
Action | No user action is required. |
Explanation | Registration of the specified profile successfully completed. |
Action | No user action is required. |
Explanation | The node was successfully deregistered with an adminagent. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | An attempt was made to register a node in an unsupported environment. A node can be registered only when it runs on the same machine as the administrative agent, which is the AminAgent MBean. |
Action | Register a node, using the registerNode operation, when the node is located on the same machine as the administrative agent. The administrative agent is the AdminAgent MBean. |
Explanation | The node you are trying to register is not a stand-alone server node. You can only register a stand-alone application server node. |
Action | Ensure that the node you are trying to register to an administrative agent is a stand-alone application server node. |
Explanation | The node could not be registered using the registerNode because no connection was made to the administrative agent during node registration. The administrative agent is the AdminAgent MBean. |
Action | Ensure that a connection is made to the correct port of the administrative agent. |
Explanation | The original configuration files for the profile are being saved before they are removed from the registry. |
Action | No user action is required. |
Explanation | Failed running registerWithAdminAgent command of the profile will be registered. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem and look for trace information in trace.log. |
Explanation | The profile failed to initialize. The initializeProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. |
Action | Review the associated error in registerProfile.log or turn on trace to diagnose the problem. |
Explanation | The profile failed to start. The startProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. |
Action | Review the associated error in registerProfile.log or turn on trace to diagnose the problem. |
Explanation | Failed running deregistereWithAdminAgent command of the node will be deregistered. |
Action | Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. |
Explanation | The profile could not be stopped. The stopProfile operation on AdminAgent MBean failed. The configuration is rolled back to the original configuration. |
Action | Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. |
Explanation | The profile could not be deleted. The destroyProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. |
Action | Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. |
Explanation | The node could not be removed from the registry. The configuration is rolled back to the original configuration. |
Action | Review the associated messages in deregisterNode.log to determine the specific problem and retry the deregisterNode command. |
Explanation | An attempt was made, using the deregisterNode operation, to remove a profile from the registry in an unsupported environment. A node can be deregistered only when it runs on the same machine as the administrative agent. The administrative agent is the AdminAgent MBean. |
Action | Remove a node from the registry when the node is located on the same machine as the administrative agent. |
Explanation | Before removing the node from the registry, the configuration must be backed up. However, the configuration files to back up could not be found. |
Action | Ensure that the node was previously registered, and that the backup files exist in your environment. |
Explanation | The node could not be registered because the AdminAgent MBean could not be gotten. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | The AdminAgent MBean, which is the administrative agent, could not be gotten during the removal of the node from the registry. The node removal was attempted using the deregisterNode operation. |
Action | Review the associated error in deregisterNode.log 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 | Make sure the profile path you specify is correct or the profile path exist locally on the Administrative Agent system. |
Action | Review the associated error to diagnose the problem. |
Explanation | A connection cannot be made to the administrative agent. The administrative agent is the AdminAgent MBean. |
Action | Ensure that the administrative agent is running. Ensure that the proper port is used when attempting to connect to the process. |
Explanation | The node is being registered with an adminagent. |
Action | No user action is required. |
Explanation | The wsadmin.properties file is being saved before it is changed. |
Action | No user action is required. |
Explanation | The node will be deregistered with an adminagent. |
Action | No user action is required. |
Explanation | The node could not be registered because the node is not a stand-alone node. |
Action | Specify the node type and the plug-in type to register the plug-in type. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The node has been registered with an adminagent. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | The node has been deregistered with an adminagent. |
Action | No user action is required. |
Explanation | Failed to register the node because the port number specified is invalid. |
Action | Check your administrative agent serverindex.xml and find the correct port number of the connector. |
Explanation | Failed invoking listProfiles operation on AdminAgent mbean. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | Failed to unregister 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 unregister was registered or make sure you try to unregister the node from the correct AdminAgent. |
Explanation | An error occured when adminagent tried to exchange signers with the node that you tried to register. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | An error occured when adminagent try to removed signers that was exchanged during node registration. |
Action | Review the associated error in deregsiterNode.log or turn on trace to diagnose the problem. |
Explanation | Removed security signers that was exchanged during node registration successfully. |
Action | No user action is required. |
Explanation | Removing security signers that was exchanged during node registration. |
Action | No user action is required. |
Explanation | This is an informational message indicating that the program has established communications with the AdminAgent. |
Action | No user action is required. |
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. Specify different name. |
Explanation | An error occured when trying to create managed node. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | An error occured during managed node removal from an adminagent. |
Action | Review the associated error or turn on trace to diagnose the problem. |
Explanation | If an error occurs during the deregisterNode command process and it cannot complete, an attempt is made to restore the configuration to its original state, though this might also fail to complete. |
Action | Review the associated messages in the deregisterNode.log file to determine the specific problem. Retry the deregisterNode. |
Explanation | An error occured when trying to set the admin preferred authorization mechanism |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | An error occured when trying to get the managed node name. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | An error occured when trying to get the profile key. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | You must specify the password when you specify the user name. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You must specify the user name when you specify the password. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You must specify the nodepassword when you specify the nodeusername. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You must specify the nodeusername when you specify the nodepassword. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You need to specify all required parameters. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You cannot use non supporting parameters. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You cannot specify the same parameter more then once. |
Action | Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. |
Explanation | You must specify conntype option if you specified port option. |
Action | Review the associated error to diagnose the problem. |
Explanation | You must specify port option if you specified conntype option. |
Action | Review the associated error to diagnose the problem. |
Explanation | Registration of all specified nodes successfully completed. |
Action | No user action is required. |
Explanation | Deregistration of all specified nodes successfully completed. |
Action | No user action is required. |
Explanation | One or more Application Server nodes failed to register. |
Action | Review the associated error in registerNode.log or turn on trace to diagnose the problem. |
Explanation | One or more Application Server nodes failed to deregister. |
Action | Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. |
Explanation | Failed to deregister the node because the port number specified is invalid. |
Action | Check your administrative agent serverindex.xml and find the correct port number of the connector. |
Explanation | None |
Action | No user action is required. |
Explanation | The option specified is not a known option. |
Action | Examine the usage statement and specify a known option. |
Explanation | A parameter is required for the displayed option, but one was not provided. |
Action | Provide a parameter for this option. |
Explanation | The parameter that is provided is not valid for the given option. |
Action | Provide a different parameter. |