ADMU

ADMU0001I: Begin federation of node {0} with Deployment Manager at {1}:{2}.
Explanation This is an informational message indicating that the addNode program has started.
Action None
ADMU0002E: Exception attempting to process server {0}: {1}
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.
ADMU0003I: Node {0} has been successfully federated.
Explanation This is an informational message indicating that the addNode program has successfully completed.
Action None
ADMU0004E: Exception attempting to get result from configuration synchronization {0}
Explanation An exception occurred during config synchronization while waiting for an asynchronous operation on the Deployment Manager.
Action Record the exception information from this message for further investigation.
ADMU0005E: Error synchronizing repositories {0}
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 sync with each other.
Action Examine the log files for additional problem determination information.
ADMU0006E: Exception creating Deployment Manager connection: {0}
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.
ADMU0007E: Error while copying {0}
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.
ADMU0008E: Error obtaining MBean by name {0}: {1}
Explanation A query to locate an MBean failed.
Action Record the exception information in this message for further investigation.
ADMU0009I: Successfully connected to Deployment Manager Server: {0}:{1}
Explanation This is an informational message indicating that the program has established communications with the Deployment Manager.
Action None
ADMU0010E: Error obtaining repository client {0}
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.
ADMU0011E: Error creating configuration in the cell repository {0}
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 still running and that the FileTransfer application is executing in the Deployment Manager. Record the exception information from this message for further problem determination. Ifthe JVM OutOfMemoryError is in the java stack trace in the addNode.log, the heapsize of addNode or the Deployment Manager may need be increased. For addNode, this is done by adding the -Xmx(size) parameter in the addNode script. For the Deployment Manager, the maximumHeapSize parameter in server.xml should be changed.
ADMU0012I: Creating Node Agent configuration for node: {0}
Explanation This is an informational message indicating that the addNode program is creating the configuration files related to the node agent for the new node.
Action None
ADMU0013I: A document already exists at the cell level: {0}
Explanation This is an informational message.
Action None
ADMU0014I: Adding node {0} configuration to cell: {1}
Explanation This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program.
Action None
ADMU0015I: Backing up the original cell repository.
Explanation This is an informational message indicating that the original configuration files are being saved before they are changed by the utility program.
Action None
ADMU0016I: Synchronizing configuration between node and cell.
Explanation This is an informational message indicating that a configuration synchronization is about to begin.
Action None
ADMU0017E: Error occurred closing an input/output stream {0}
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 -trace option.
ADMU0018I: Launching Node Agent process for node: {0}
Explanation This is an informational message indicating that the node agent process is about to be started.
Action None
ADMU0019E: Error occurred reading from an input stream {0}
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 -trace option.
ADMU0020I: Reading configuration for Node Agent process: {0}
Explanation This is an informational message.
Action None
ADMU0021E: Error occurred stopping server {0}
Explanation The status of the server is not STOPPED as expected.
Action Examine the log files for the server to see why the server is not stopped.
ADMU0022I: Node Agent launched. Waiting for initialization status.
Explanation This is an informational message.
Action None
ADMU0023E: Exception waiting for server initialization {0}
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.
ADMU0024I: Deleting the old backup directory.
Explanation This is an informational message indicating that the original configuration files are being saved before they are changed by the utility program.
Action None
ADMU0025E: Given host and port do not point to a Deployment Manager.
Explanation The connected process does not have a DeploymentManager MBean. The most common cause is that the host/port specified is not that for the Deployment Manager.
Action Verify that the host and port passed to the tool are correct.
ADMU0026I: An error occurred during federation; rolling back to original configuration.
Explanation If an error occurs during the addNode command process and it cannot complete, the original configuration is restored to the original state. before addNode was requested.
Action Review the associated messages in addNode.log to determine the specific problem and retry the addNode command.
ADMU0027E: An error occurred during federation {0}; rolling back to original configuration.
Explanation If an error occurs during the addNode command process and it cannot complete, the original configuration is restored to the original state. before addNode was requested.
Action Review the associated messages in addNode.log to determine the specific problem and retry the addNode command.
ADMU0028I: Log generated.
Explanation This is an informational message.
Action None
ADMU0029E: An error occurred during node removal: {0}
Explanation A problem occurred during node removal process.
Action Examine the exception to determine the specific problem and take corrective action.
ADMU0030I: Node Agent initialization completed successfully. Process id is: {0}
Explanation This is an informational message indicating that the node agent process started without errors.
Action None
ADMU0031E: Node Agent launched but failed initialization. Process id was: {0}
Explanation The node agent process returned an unsuccessful status value.
Action Examine the log files for the node agent to perform additional problem determination.
ADMU0032E: It is not valid to run addNode on the same node as the Deployment Manager: {0}
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.
ADMU0033E: The node {0} already has been added to the cell.
Explanation You cannot run addNode on a node that has already been added to a cell.
Action Do not attempt to run addNode twice on the same node.
ADMU0034E: The node/cell name of the node being federated with addNode must have a different name than the cell name of the ND manager node: {0}
Explanation The cell name of the ND manager node must be unique with the node.
Action Insure that the cell nameof the ND manager node is unique within the cell.
ADMU0035E: WebSphere Express nodes are not supported in a Network Deployment cell.
Explanation An attempt has been made to add a node that is a WebSphere Express node.
Action Do not attempt to add a WebSphere Express node. It is not a supported node for the Network Deployment environment.
ADMU0036E: The Deployment Manager cannot lookup by name host {0} at address {1}
Explanation The local host can lookup the Deployment Manager host, but the Deployment Manager cannot lookup the new node; often this occurs if DHCP does not interact with DNS.
Action You may need to use static IP if DHCP does not interact with DNS. If the hostname is not fully qualified, you may need to update the hostname using the AdminCommand $AdminTask changeHostName {-nodeName xxx -hostName xxx}
ADMU0037E: The node cannot lookup the Deployment Manager using host name {0}. The host name in the Deployment Manager configuration may need to be fully qualified.
Explanation There is a problem with the configuration of the Deployment Manager''s host name. The local node cannot lookup the Deployment Manager''s host name as it is specified in the Deployment Manager configuration.
Action Either the Deployment Manager''s host name needs to be added to DNS, the Deployment Manager''s host name needs to be fully qualified in the Deployment Manager''s server index configuration, or the domain''s DNS suffix needs to be added to the node''s TCP/IP configuration.
ADMU0038E: The Deployment Manager''s IP address resolves as 127.0.0.1, but the Deployment Manager is not on the local machine. The Deployment Manager''s host name configuration or DNS is configured incorrectly.
Explanation The Deployment Manager''s 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 search DNS before files.
ADMU0039E: There is already a node named {0} in the cell.
Explanation You cannot run addNode to add a node to a cell which already contains a node of the same name.
Action Do not attempt to run addNode to add a node to a cell already containing a node of the same name.
ADMU0040E: Exception on MBean invocation {0} {1} {2}
Explanation An MBean call failed.
Action Record and save the exception information from this message for further problem determination.
ADMU0041E: Another addNode or removeNode operation is currently in progress. Please attempt this operation later.
Explanation Concurrent addNode and removeNode operations are not allowed.
Action Wait until the first addNode or removeNode operation completes, and then retry this operation.
ADMU0042E: The addNode/removeNode operation lock could not be released at the Deployment Manager. You may need to invoke AdminOperations.forceNodeFederationOrRemovalTokenReset operation to manually complete this final step of addNode or removeNode.
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.
ADMU0044E: It is not valid to run syncNode on the same node as the Deployment Manager: {0}
Explanation The syncNode program only applies to app server nodes, not the ND deployment manager node itself.
Action Do not attempt to run syncNode on the Deployment Manager node itself.
ADMU0050E: Exception encountered while checking if node {1} can join node group {2}. {0}
Explanation The exception that was encountered during program execution follows the message text.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0051E: Exception occurred while converting node group {2} to sysplex node group for node {1}. {0}
Explanation The exception that was encountered during program execution follows the message text.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0052E: Exception occurred while adding node {1} to node group {2}. {0}
Explanation The exception that was encountered during program execution follows the message text.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0053E: Exception occurred while removing node {1} from all node groups. {0}
Explanation The exception that was encountered during program execution follows the message text.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0054W: {0} WARNING(S) occurred while checking if node {1} can join node group {2}. {3}
Explanation One or more warnings occurred while checking whether the node can join the node group.
Action None.
ADMU0055W: {0} WARNING(S) occurred while converting node group {2} to sysplex node group for node {1}. {3}
Explanation One or more warnings occurred while converting the node group to a sysplex node group.
Action None. ADMU0060W is issued for each warning message encountered.
ADMU0056W: {0} WARNING(S) occurred while adding node {1} to node group {2}. {3}
Explanation One or more warnings occurred while adding the node to the node group.
Action None.
ADMU0057W: {0} WARNING(S) occurred while removing node {1} from all node groups. {2}
Explanation One or more warnings occurred while removing the node from all node groups.
Action None.
ADMU0058I: Removing node {0} from all node groups.
Explanation This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program.
Action None
ADMU0059I: Adding node {0} to node group {1}.
Explanation This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program.
Action None
ADMU0060W: The -portprops option overrides the -startingport option.
Explanation The options are mutually exclusive.
Action Specify the correct option.
ADMU0061W: The -nodeagentshortname option is used in a z/OS environment only.
Explanation This option is ignored for a non-z/OS environment.
Action Use this option in a z/OS environment only.
ADMU0070W: Retrieving signer certificates from dmgr failed - this may cause node federation to fail.
Explanation The attempt to retrieve the signer certificates from the dmgr failed. The username and/or password specified may be incorrect.
Action Verify the username and password are correct or use the retrieveSigners script to download the signer certificates from the dmgr.
ADMU0071E: Exception occurred during security authentication.
Explanation An exception occurred during the password encryption/decryption.
Action Verify the user name and password are correct and retry the operation.
ADMU0088E: No Server MBean named {0} in this process {1}:{2}
Explanation The server name does not match the process attributes.
Action Check that the name is spelled correctly.
ADMU0089E: Exception caught during rollback of application binaries {0}
Explanation A problem was encountered during the rollback of application binaries..
Action Please consult the addNode.log file for additional information.
ADMU0111E: Program exiting with error: {0}
Explanation An exception occurred during program execution.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0112E: Exception writing serverindex.xml file: {0}
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.
ADMU0113E: Program exiting with error: {0}, resulting from: {1}
Explanation An exception occurred during program execution.
Action Record the exception information from this message and perform problem determination using that exception data.
ADMU0114E: Exception launching Node Agent process: {0}
Explanation The attempt to launch the node agent for the new node failed and issued an exception.
Action Record and save the exception information from this message and perform further problem determination to investigate why the process failed to launch.
ADMU0115I: Trace mode is on.
Explanation This is an informational message indicating that trace has been enabled
Action None
ADMU0116I: Tool information is being logged in file {0}
Explanation This is an informational message indicating the file in which logging data is being stored.
Action None
ADMU0117E: The application {0} on this node cannot be merged with the Cell. The application binaries URL conflicts with what is already in the Cell.
Explanation The application already exists in the cell configuration repository and uses a different URL for the location of its binaries. It cannot be merged with 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.
ADMU0118E: The log file cannot be written to location {0}; please specify a different location with -logfile
Explanation An error occurred attempting to write the logfile; this may be caused by a permissions or security problem
Action Use the -logfile option to specify a new location for the logfile
ADMU0119E: Unexpected exception {0} in rolling back application binaries.
Explanation An unexpected exception occured while attempting to expand the application ear files to appropriate locations after addNode command failed. Users will have to explicitly expand ear files for all the applications on this cell to their appropriate binariesURL locations.
Action Use EARExpander tool to expand the application ear files to their appropriate destination specified in the binariesURL attribute of the deployment.xml file in the repository.
ADMU0120I: {0} will not be uploaded since it already exists in the target repository.
Explanation None
Action None
ADMU0121E: Unexpected exception {0} while checking existence of {1} in the target repository. {1} will not be uploaded.
Explanation An exception occured while checking if the application already exists in the repository to which this node is being added to. Therefore this application will not be uploaded as a part of addNode even if -includeapps options is specified.
Action You can install this application after addNode is done either by using the admin UI or wsadmin.
ADMU0122E: Exception {0} copying application files from {1} to {2}.
Explanation Unexpected exception in file copy.
Action Manually copy files.
ADMU0123E: Could not find text for message ID {0}.
Explanation The specified message ID could not be found in the message file; contact IBM support.
Action This exception is unexpected. The cause is not immediately known.
ADMU0124I: The system clock of the new node ({0}) is not synchronized with that of the deployment manager ({1}).
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''s system clock to be the same as that of the deployment manager.
ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager.
Explanation Explanation of what to do if addNode fails because of the clock sync problem.
Action Follow the instructions in the message.
ADMU0126E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}); the node has not been added.
Explanation Deployment Manager version earlier than that of a node is an unsupported configuration.
Action Upgrade the Deployment Manager to the same or later version as that of the node.
ADMU0127E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}).
Explanation Deployment Manager version earlier than that of a node is an unsupported configuration.
Action Upgrade the Deployment Manager to the same or later version as that of the node.
ADMU0128I: Starting tool with the {0} profile
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.
ADMU0180E: Duplicate Entry Exception: An exception occured while checking existence of server short name {0}, node {1} in the Deployment Manager cell. The server short name already exists in the distributed cell.
Explanation The server short name already exists in the distributed cell to which this node is being added.
Action Make sure server short name is unique across all the servers in the distributed cell before running addNode. Change the server short name to be unique in the Deployment Manager cell, then run addNode
ADMU0181E: Duplicate Entry Exception: An exception occured while checking existence of cluster transition name {0}, node {1} in the Deployment Manager cell. The cluster transition name already exists in the distributed cell.
Explanation The cluster transition name already exists in the distributed cell to which this node is being added.
Action Make sure cluster transition name is unique across all the servers in the distributed cell before running addNode. Change the cluster transition name to be unique in the Deployment Manager cell, then run addNode
ADMU0182E: Duplicate Entry Exception: An exception occured while checking existence of node short name {0} in the Deployment Manager cell. The node short name already exists in the distributed cell.
Explanation The node short name already exists in the distributed cell to which this node is being added.
Action Make sure the node short name is unique across all the nodes in the distributed cell before running addNode. Change the node short name to be unique in the Deployment Manager cell then run addNode
ADMU0183E: Duplicate Entry Exception: An exception occured while checking existence of node agent short name {0} in the Deployment Manager cell. The node agent short name already exists in the distributed cell.
Explanation The node agent short name already exists in the distributed cell to which this node is being added.
Action Make sure the node agent short name is unique across all the nodes in the distributed cell before running addNode. Change the node agent short name to be unique in the Deployment Manager cell then run addNode
ADMU0211I: Error details may be seen in the file: {0}
Explanation This is an informational message indicating that additional information is available in the log file.
Action Look in the file for additional information.
ADMU0222I: Exception accessing the plugin-cfg.xml file.
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.
ADMU0250I: Node {0} has been successfully renamed to {1}.
Explanation This is an informational message indicating that the renameNode program has successfully completed.
Action None
ADMU0251I: Begin changing node name for {0}
Explanation This is an informational message indicating that rename node program has been started.
Action None
ADMU0254I: Update the node configuration for {0} on the Deployment Manager.
Explanation None
Action None
ADMU0300I: The node {0} was successfully added to the {1} cell.
Explanation None
Action None
ADMU0302I: Any cell-level documents from the standalone {0} configuration have not been migrated to the new cell.
Explanation None
Action None
ADMU0303I: Update the configuration on the {0} Deployment Manager with values from the old cell-level documents.
Explanation None
Action None
ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.
Explanation None
Action None
ADMU0305I: Install applications onto the {0} cell using wsadmin $AdminApp or the Administrative Console.
Explanation None
Action None
ADMU0306I: Note:
Explanation None
Action None
ADMU0307I: You might want to:
Explanation None
Action None
ADMU0308I: The node {0} and associated applications were successfully added to the {1} cell.
Explanation None
Action None
ADMU0401I: Begin syncNode operation for node {0} with Deployment Manager {1}: {2}
Explanation This is an informational message indicating that the syncNode program has started.
Action None
ADMU0402I: The configuration for node {0} has been synchronized with Deployment Manager {1}: {2}
Explanation This is an informational message indicating that the syncNode program has completed successfully.
Action None
ADMU0403E: The syncNode command may only be run when the node agent is stopped. Either stop the node agent or use the normal synchronization facility in the node agent.
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 syncNode.
Action Stop the node agent before running syncNode or use the normal synchronization facility via the admin console or the NodeSync MBean.
ADMU0500I: Retrieving server status for {0}
Explanation This is an informational message.
Action None
ADMU0501E: Server name not specified; must supply the name of a server or -all for all servers.
Explanation The serverStatus tool requires that a server name be provided or -all to list all servers.
Action Specify a server name or -all.
ADMU0503I: Retrieving server status for all servers
Explanation This is an informational message.
Action None
ADMU0505I: Servers found in configuration:
Explanation This is an informational message printed before a list of servers.
Action None
ADMU0506I: Server name: {0}
Explanation This is an informational message showing the name of a server.
Action None
ADMU0507I: No servers found in configuration under: {0}
Explanation The servers directory is empty in the configuration.
Action Check the integrity of the configuration files.
ADMU0508I: The {0} "{1}" is {2}
Explanation This is an informational message the shows the state of the server.
Action None
ADMU0509I: The {0} "{1}" cannot be reached. It appears to be stopped.
Explanation This is an informational message indicating that the server appears to be stopped.
Action None
ADMU0510I: Server {0} is now {1}
Explanation This is an informational message the shows the state of the server.
Action None
ADMU0512I: Server {0} cannot be reached. It appears to be stopped.
Explanation This is an informational message indicating that the server appears to be stopped.
Action None
ADMU0514E: Unsupported JMX Connector: {0}
Explanation A JMX connector type was requested that is not supported.
Action Request a connector type that is supported.
ADMU0521E:
No node named "{0}" is found in this cell.
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.
ADMU0522E: No server by this name in the configuration: {0}
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.
ADMU0523I: Creating Queue Manager for node {0} on server {1}
Explanation This is an informational message marking the progress of the program.
Action None
ADMU0524I: WebSphere Embedded Messaging support not installed; Queue Manager not created
Explanation This is an informational message explaining why a Queue Manager is not created.
Action None
ADMU0525I: Details of Queue Manager creation may be seen in the file: {0}
Explanation This is an informational message.
Action Look in the file for more information.
ADMU0526I: Deleting Queue Manager for node {0} on server {1}
Explanation This is an informational message marking the progress of the program.
Action None
ADMU0527I: WebSphere Embedded Messaging support not installed; Queue Manager not deleted from server {0}
Explanation This is an informational message marking the progress of the program.
Action None
ADMU0528I: Details of Queue Manager deletion may be seen in the file: {0}
Explanation This is an informational message.
Action Look in the file for more information.
ADMU0529E: Unexpected exception {0} thrown while restoring application binaries from the base configuration.
Explanation During removeNode processing, the applications from the original configuration are put back in place. Something caused this process to fail and manual recovery is necessary.
Action Use EARExpander tool to expand the application ear file to the appropriate location specified by binariesURL attribute in the corresponding deployment.xml config files.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
Explanation This is an informational message indicating that the -trace option is available to be used in order to gather additional trace information.
Action Consider using the -trace option on the command line.
ADMU1500W: Exception caught while registering node agent as Windows service - please check addNode.log for details
Explanation There was a problem found while registering node agent as Windows service.
Action Please check addNode.log for additional information.
ADMU1501W: Exception caught while de-registering node agent as Windows service - please check addNode.log for details
Explanation There was a problem found while de-registering node agent as Windows service.
Action Please check addNode.log for additional information.
ADMU1502E: If you specify "-serviceUserName" or "-servicePassword" then you must specify both of these as well as "-registerService".
Explanation You must specify "-serviceUserName" and "-servicePassword" together. You must also specify "-registerService"
Action Please obtain values for the above and resubmit request.
ADMU2001I: Begin removal of node: {0}
Explanation This is an informational message indicating that the removeNode program has started.
Action None
ADMU2003E: No setupCmdLine file found to modify: {0}
Explanation The file was not located.
Action Check that a setupCmdLine file exists in the installation.
ADMU2004E: An exception occurred
Explanation An exception occurred
Action Record the exception data and perform further problem determination.
ADMU2010I: Stopping all server processes for node {0}
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2012I: Backing up Network Deployment configuration.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2014I: Restoring original configuration.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2015I: This exception can be ignored by specifying -force.
Explanation This is an informational message explaining that the -force option can be used to eliminate the message.
Action None
ADMU2016E: Node {0} has not been removed from the Deployment Manager configuration.
Explanation The node configuration files remain in the cell configuration repository.
Action If the -force option is used, the cleanupNode utility will need to be run on the Deployment Manager to remove the config files for this node.
ADMU2017I: The local original configuration has been restored.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2018I: Node {0} has been removed from the Deployment Manager configuration.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2019I: Removing installed applications from node {0}.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2020E: Exception removing applications {0}
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.
ADMU2021I: Removing all servers on this node from all clusters in the cell.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2022I: Removing cluster member {0} from cluster {1}.
Explanation This is an informational message marking the progress of the program.
Action None
ADMU2023E: Exception removing servers from clusters {0}
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.
ADMU2024I: Removal of node {0} is complete.
Explanation This is an informational message indicating that removeNode has successfully completed.
Action None
ADMU2025W: Removal of node {0} is complete, but there were errors.
Explanation This node was removed from the cell, but problems occurred during the removal.
Action Examine the previous errors to determine what occurred. The cleanupNode utility may need to be run to remove this node from the Deployment Manager''s config.
ADMU2026E: Node {0} is not incorporated into any cell.
Explanation An attempt was made to remove a node that has never been added in the first place.
Action Run addNode before attempting to run removeNode.
ADMU2027E: Exception {0} caught in creating varmap for scope {1}, {2}, {3}
Explanation The variable map could not be created. This means applications may not be restored or deleted from their binaries URL.
Action Run EARExpander tool to expand the application ear files to their appropriate locations.
ADMU2028E: Exception {0} caught in expanding ear at {1} to {2}
Explanation EAR file could not be expanded to the destination.
Action Run EARExpander tool to expand the ear file to its appropriate locations.
ADMU2029E: Exception {0} caught in creating EAR Object from {1}
Explanation EAR file could not be obtained from the specified location. The ear will not be expanded to the specified destination.
Action Run EARExpander tool to expand the ear file to its appropriate locations.
ADMU2030E: Exception {0} caught in getting binariesURL from {1}
Explanation The specified deployment.xml could not be loaded to obtain binariesURL. The ear file will not be expanded or deleted from that location.
Action Run EARExpander tool to expand the ear file to its appropriate location if needed. Or delete the directory where ear was supposed to be deleted from.
ADMU2031I: Any applications that were uploaded to the {0} cell configuration during addNode using the -includeapps option are not uninstalled by removeNode.
Explanation None
Action None
ADMU2032I: Use wsadmin or the Administrative Console to uninstall any such applications from the Deployment Manager.
Explanation None
Action None
ADMU2033I: Any buses that were uploaded to the {0} cell configuration during addNode using the -includebuses option are not uninstalled by removeNode.
Explanation None
Action None
ADMU2034I: Use wsadmin or the Administrative Console to uninstall any such buses from the Deployment Manager.
Explanation None
Action None
ADMU2035W: WARNING! Node removal utility is unable to remove this node since it was created during Cell Profile creation. Your current node has not been modified.
Explanation Warning message informing user removeNode tool cannot complete when a node was created during Cell Profile creation.
Action Use manageprofiles utility to delete this node and run cleanupNode utility on Deployment Manager. See WAS Infocenter.
ADMU2036I: To continue removal of this node manually, you may use manageprofiles utility to delete the profile for this node and run cleanupNode utility on Deployment Manager.
Explanation Suggestion to clean up a node after running removeNode with possible warnings or errors.
Action See WAS Infocenter.
ADMU2091E: Exception {0} caught checking product extensions on the node or the Deployment Manager.
Explanation A problem occurred trying to determine which product extensions are installed.
Action Examine the exception to determine the specific problem.
ADMU2092E: The node and Deployment Manager must have the same product extensions, but they do not match. The node product extension is {0} and the Deployment Manager product extension is {1}.
Explanation The operation cannot be completed because the product extensions do not match.
Action Check the product extensions installed on both the node and the Deployment Manager. Additional product extensions may need to be installed.
ADMU2093E: Custom property {0} has no value.
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.
ADMU2094W: The node product extension is {0} which does not match the Deployment Manager product extension which is {1}. Some operations and configurations may not be valid on this node.
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.
ADMU3000I: Server {0} open for e-business; process id is {1}
Explanation This is an informational message indicating that the server has started.
Action None
ADMU3001I: Server {0} open for recovery; process id is {1}
Explanation This is an informational message indicating that the server is doing recovery.
Action None
ADMU3002E: Exception attempting to process server {0}
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.
ADMU3007E: Exception {0}
Explanation Some general exception condition has been discovered.
Action Combine this information with additional exception messages in order to perform additional problem determination.
ADMU3009E: Exception waiting for server initialization {0}
Explanation An exception occurred while the program was listening to the status socket for the server.
Action Record and save the exception information in this message for further problem determination.
ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under {0} should contain failure information.
Explanation The server process failed to start.
Action Examine the log files to see what failure messages were recorded there.
ADMU3012E: Exception attempting to get free port for status socket {0}
Explanation A free port was not able to be allocated for communicating server status.
Action Examine the log file for the utility to perform further problem determination. Attempt to execute the utility again.
ADMU3013I: Server recovery complete. Server stopped.
Explanation The server has completed recovery and has stopped.
Action This is an informational message.
ADMU3014W: Server recovery complete, problems occurred during recovery. Server log files should contain failure information.
Explanation The server had problems during recovery and has stopped.
Action Examine the log files to see what failure messages were recorded there.)
ADMU3019E: Exception waiting for server stop {0}
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.
ADMU3027E: An instance of the server may already be running: {0}
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.
ADMU3028I: Conflict detected on port {0}. Likely causes: a) An instance of the server {1} is already running b) some other process is using port {0}
Explanation A port required by this server is already in use by this or aother server.
Action Do not attempt use a port that is already in use.
ADMU3040E: Timed out waiting for server initialization: {0} seconds
Explanation The server initialization process has exceeded the timeout limit.
Action Perform problem determination on the server to check for possible errors.
ADMU3054E: No Server MBean named {0} in this process {1}:{2}
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.
ADMU3055E: Error obtaining MBean by name {0}: {1}
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.
ADMU3060E: Timed out waiting for server shutdown.
Explanation The amount of time taken for server shutdown exceeded the -timeout value requested.
Action Use a larger -timeout value or perform problem determination on the server to investigate possible errors.
ADMU3100I: Reading configuration for server: {0}
Explanation This is an informational message marking progress of the program.
Action None
ADMU3101I: Using explicit host and port {0}:{1} for server: {2}
Explanation This is an informational message indicating that explicit host or port options were used.
Action None
ADMU3111E: Server stop requested but failed to complete.
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.
ADMU3200I: Server launched. Waiting for initialization status.
Explanation This is an informational message marking progress of the program.
Action None
ADMU3201I: Server stop request issued. Waiting for stop status.
Explanation This is an informational message marking progress of the program.
Action None
ADMU3220I: Base server runtime initialized. Waiting for application initialization.
Explanation This is an informational message marking progress of the program.
Action None
ADMU3300I: Launch script for server created: {0}
Explanation This is an informational message indicating that the launch script has been successfully created.
Action None
ADMU3400I: Server launched. No initialization status. Process id is: {0}
Explanation The -nowait option was used for startServer, so no initialization status is available for the launched process.
Action None
ADMU3401I: Server stop request issued. No stop status requested.
Explanation This is an informational message.
Action None
ADMU3402E: Server name not specified; must supply the name of a server.
Explanation This tool requires that a server name be provided.
Action Specify a server name.
ADMU3522E: No server by this name in the configuration: {0}
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.
ADMU4000I: Server {0} stop completed.
Explanation This is an informational message indicating that the stopServer command succeeded.
Action None
ADMU4018E: "-script" option is not supported on zOS platform.
Explanation "-script" option is not supported on zOS platform.
Action Remove the "-script" option and rerun the command.
ADMU4111E: Program exiting with error: {0}
Explanation An error occurred during program execution.
Action Perform problem determination to investigate possible causes.
ADMU4112I: Error details may be seen in the file: {0}
Explanation This is an informational message indicating where to look for further information.
Action Look in the file for more information.
ADMU4113E: Verify that username and password information is correct. If running tool from the command line, pass in the correct -username and -password. Alternatively, update the <conntype>.client.props file.
Explanation The tool could not contact the remote server because of a credentials problem.
Action Pass in the correct username and password. If using command prompt, pass in -username & -password, or update the soap/sas.client.props file.
ADMU4122E: The specified server may not be running, or no appropriate username and password are provided if the specified server runs in secure mode
Explanation There is a problem establishing a connection to a process.
Action Make sure that the targeted process is really running and make sure that proper username and password are used when attempting to connect to the process running in secure mode.
ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port.
Explanation There is a problem establishing a connection to the Deployment Manager.
Action Make sure that the Deployment Manager is really running and make sure that proper hostname and port are used when attempting to connect to the process.
ADMU4211I: To obtain a full trace of the failure, use the -trace option.
Explanation This is an informational message telling the user about the -trace command line option.
Action None
ADMU5001I: Backing up config directory {0} to file {1}
Explanation This is an informational message saying the backup is beginning
Action None
ADMU5002I: {0} files successfully backed up
Explanation This is an informational message saying the number of files successfully backed up
Action None
ADMU5501E: The backup file specified {0} does not exist.
Explanation The file specified containing the backed-up config documents cannot be found.
Action Verify that the file given to restoreConfig exists and can be read.
ADMU5502I: The directory {0} already exists; renaming to {1}
Explanation This is an informational message saying the location to restore already exists and will be renamed
Action None
ADMU5503E: The restore location could not be renamed - another process may be using this subdirectory
Explanation A problem occurred attempting to rename the restore location
Action Use the -location option to specify a location which does not exist, or one which can be renamed
ADMU5504I: Restore location successfully renamed
Explanation This is an informational message saying the location specified has been renamed
Action None
ADMU5505I: Restoring file {0} to location {1}
Explanation This is an informational message saying the restore is beginning
Action None
ADMU5506I: {0} files successfully restored
Explanation This is an informational message saying the number of files successfully restored
Action None
ADMU6001I: Begin App Preparation -
Explanation NONE
Action NONE
ADMU6009I: Processing complete.
Explanation NONE
Action NONE
ADMU6012I: Exception in run {0}
Explanation NONE
Action NONE
ADMU7004E: Unexpected exception while building cache entry for {0} and {1}. Exception is: {2}. All the related binaries may not be deleted/updated.
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.
ADMU7005E: The cell name contained in the backup file is not the same as the current cell name of your configuration which is "{0}". You may ignore this condition by specifying "-force" as a command line option.
Explanation This backup file was created from a system with a different cell name.
Action Either user the "-force" option and manually correct the resulting problems or restore using a backup file that used the same cell name as current system.
ADMU7006W: The cell name contained in the backup file is not the same as the current cell name of your configuration which is "{0}". Since you specified the "-force" option, the backup file will be restored but you will need to manually correct the resulting problems.
Explanation This backup file was created from a system with a different cell name
Action After the restore operation has completed please correct any resulting problems and confirm proper system function before starting production applications.
ADMU7008E: Unexpected exception in expandEar. The ear file {0} will not be extracted in following paths {1}. Exception: {2}
Explanation The disk may be full or the directory may not have write permission.
Action Use EARExpander tool to extract the ear file.
ADMU7701I: Because {0} is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.
Explanation When a server is registered to run as a Windows Service, the Windows Service is used to start the server.
Action None
ADMU7702I: Because {0} is registered to run as a Windows Service, the request to stop this server will be completed by stopping the associated Windows Service.
Explanation When a server is registered to run as a Windows Service, the Windows Service is used to stop the server.
Action None
ADMU7703I: The Windows Service {0} associated with {1} is now being deregistered.
Explanation When a server is removed, the corresponding Windows Service is deregistered.
Action None
ADMU7704E: Failed while trying to start the Windows Service associated with server: {0};
probable error executing WASService.exe: {1}
Explanation The Windows Service associated with this server failed to start.
Action Check return code and correct the problem then retry the operation.
ADMU7705E: Failed while trying to stop the Windows Service associated with server: {0};
probable error executing WASService.exe: {1}
Explanation The Windows Service associated with this server failed to stop.
Action Check return code and correct the problem then retry the operation.
ADMU7706E: Failed while trying to deregister the Windows Service {0};
probable error executing WASService.exe: {1}
Explanation The Windows Service associated with this server failed to deregister.
Action Check return code and correct the problem then retry the operation.
ADMU7707E: Failed while trying to determine the Windows Service name for server: {0};
probable error executing WASService.exe: {1}
Explanation The Windows Service associated with this server could not be found.
Action Please verify that there is a valid Windows Service associated with this server.
ADMU7708E: Failed while trying to determine the Windows Service log file name for server: {0};
probable error executing WASService.exe: {1}
Explanation The log file for the Windows Service associated with this server could not be found.
Action Verify WebSphere installation. If nothing found, contact IBM support.
ADMU7709E: Unexpected exception while processing server: {0}; exception = {1}
Explanation An unexpected exception has been detected.
Action Verify WebSphere installation. If nothing found, contact IBM support.
ADMU7710E: Unexpected exit code {1} from WASService.exe while executing {0}
Explanation An unexpected exit code was returned from WASService.exe
Action Verify WebSphere installation and Windows environment; try running command manually; contact IBM support.
ADMU7711E: Unexpected exception associated with WASService.exe: {0} during processing of server with name: {1}
Explanation An unexpected exception has been detected.
Action Verify WebSphere installation. If nothing found, contact IBM support.
ADMU7712E: Failed while trying to determine the Windows Service status for service: {0};
probable error executing WASService.exe: {1}
Explanation The status for the Windows Service could not be obtained.
Action Verify WebSphere installation. If nothing found, contact IBM support.
ADMU7750E: The {0} command has failed because another process has temporarily requested exclusive access to {1}. Please wait a few minutes and try again.
Explanation Another command is running and might conflict with this one.
Action Wait a few minutes and try the command again.
ADMU7770I: Generic Server: {0} STARTED successfully.
Explanation Request to start generic server was successful.
Action None
ADMU7771E: Generic Server: {0} already running - use the "-forceGenericServerStart" to force server start!
Explanation User is trying 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.
ADMU7772I: Generic Server: {0} STOPPED successfully.
Explanation Request to stop generic server was successful.
Action None
ADMU7773E: Generic Server: {0} is not RUNNING
Explanation User is trying to stop a generic server that has not been started.
Action Be sure that generic server is RUNNING before attempting to stop it.
ADMU9990I:
Explanation None
Action None
ADMU9991E: Unknown option: {0}
Explanation The option specified is not a known option.
Action Examine the usage statement and specify a known option.
ADMU9992E: Parameter required for option: {0}
Explanation A parameter is required for the displayed option, and one was not provided.
Action Provide a parameter for this option.
ADMU9993E: Invalid parameter {0}
Explanation The parameter that is provided is not valid for the given option.
Action Provide a different parameter.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: May 16, 2012 4:38:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.nodeutils.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)