Express (Distributed operating systems), v8.0 > Reference > Messages
ADMU
ADMU0001I: Begin federation of node {0} with Deployment Manager at {1}:{2}.
Explanation Informational message indicating that the addNode program has started. Action No user action is required.
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 Informational message indicating that the addNode program has successfully completed. Action No user action is required.
ADMU0004E: Exception attempting to get result from configuration synchronization {0}
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.
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 synchronization 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 Informational message indicating that the program has established communications with the Deployment Manager. Action No user action is required.
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 dmgr for creation in the cell repository. Action Ensure that the dmgr is running and that the FileTransfer application is running in the dmgr. 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 dmgr might need to be increased. For the addNode command, add the -Xmx(size) parameter to the addNode command.
ADMU0012I: Creating Node Agent configuration for node: {0}
Explanation The addNode command created the configuration files for the node agent for the new node. Action No user action is required.
ADMU0013I: A document already exists at the cell level: {0}
Explanation The specified document exists at the cell level. Action No user action is required.
ADMU0014I: Adding node {0} configuration to cell: {1}
Explanation Configuration files from the node are being uploaded to the cell repository that the dmgr manages. Action No user action is required.
ADMU0015I: Backing up the original cell repository.
Explanation The original configuration files are saved before the utility program changes them. Action No user action is required.
ADMU0016I: Synchronizing configuration between node and cell.
Explanation Configuration synchronization is occurring between a node and a cell. Action No user action is required.
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 the -trace option.
ADMU0018I: Launching Node Agent process for node: {0}
Explanation The node agent process is starting. Action No user action is required.
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 the -trace option.
ADMU0020I: Reading configuration for Node Agent process: {0}
Explanation The configuration for the specified node agent process is being read. Action No user action is required.
ADMU0021E: Error occurred stopping server {0}
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.
ADMU0022I: Node Agent launched. Waiting for initialization status.
Explanation The node agent launched and is waiting for initialization status. Action No user action is required.
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 The original configuration files are saved before they the utility program changes them. Action No user action is required.
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 specified host or port is not for the dmgr. 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 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.
ADMU0027E: An error occurred during federation {0}; rolling back to original configuration.
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.
ADMU0028I: Log generated.
Explanation A log was generated. Action No user action is required.
ADMU0029E: An error occurred during node removal: {0}
Explanation The node could not be removed. Action Examine the exception to determine the specific problem and take corrective action.
ADMU0030I: Node Agent initialization completed successfully. Process id is: {0}
Explanation Informational message indicating that the node agent process started without errors. Action No user action is required.
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 Network Deployment dmgr 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 We 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.
ADMU0034E: The node/cell name of the node being federated with addNode must have a different name than the cell name of the Network Deployment manager node: {0}
Explanation The cell name of the Network Deployment manager node must be unique within the cell. Action Ensure that the cell name of the dmgr is unique within the cell.
ADMU0035E: WebSphere Express nodes are not supported in a Network Deployment 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.
ADMU0036E: The Deployment Manager cannot lookup by name host {0} at address {1}
Explanation The local host can look up the dmgr host, but the dmgr 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.
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 The local node cannot look up the dmgr host name specified in the dmgr configuration. Action Do one of the following actions: - Add the dmgr host name to the DNS. - Fully qualify the deployment manger host name in the dmgr server index configuration. -Add the DNS of the domain to the TCP/IP configuration of the node.
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 dmgr host name is not resolving correctly. Action Verify that the host name is configured properly at the dmgr. For Linux systems, modify either the /etc/hosts file or the /etc/nsswitch.conf file to search the domain name server (DNS) before files.
ADMU0039E: There is already a node named {0} in the cell.
Explanation We 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.
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.
ADMU0043E: Error trying to federate a node that is still registered to an AdminAgent.
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.
ADMU0050E: Exception encountered while checking if node {1} can join node group {2}. {0}
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.
ADMU0051E: Exception occurred while converting node group {2} to sysplex node group for node {1}. {0}
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.
ADMU0052E: Exception occurred while adding node {1} to node group {2}. {0}
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.
ADMU0053E: Exception occurred while removing node {1} from all node groups. {0}
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.
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 No user action is required..
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 No user action is required.. 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 No user action is required..
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 the node groups. Action No user action is required..
ADMU0058I: Removing node {0} from all node groups.
Explanation The configuration files for the node are being uploaded to the cell repository that the dmgr manages because the specified node is being removed from all the node groups. Action No user action is required.
ADMU0059I: Adding node {0} to node group {1}.
Explanation The configuration files for the node are being uploaded to the cell repository that the dmgr manages because the specified node is being added to the specified node group. Action No user action is required.
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 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.
ADMU0062E: The -asExistingNode option cannot be used with any of the following options: {0}
Explanation The -asExistingNode option is incompatible with these options. Action Retry the command and omit either the -asExistingNode option or all of the incompatible options.
ADMU0063E: The {0} node does not exist in the cell so the -asExistingNode option cannot be used.
Explanation We cannot use the -asExistingNode option unless the node already exists in the cell. Action Use the command with a node that already exists in the cell or do not use the -asExistingNode option.
ADMU0070W: Retrieving signer certificates from dmgr failed - this may cause node federation to fail.
Explanation The signer certificates could not be retrieved from the dmgr. 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 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 The rollback of the application binaries failed. Action Consult the addNode.log file for additional information.
ADMU0111E: Program exiting with error: {0}
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.
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 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.
ADMU0114E: Exception launching Node Agent process: {0}
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.
ADMU0115I: Trace mode is on.
Explanation Trace has been enabled. Action No user action is required.
ADMU0116I: Tool information is being logged in file {0}
Explanation Tool information is being logged to the specified file. Action No user action is required.
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. The application cannot be merged with the cell configuration and will be ignored. Action Install the application on the dmgr 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 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.
ADMU0119E: Unexpected exception {0} in rolling back application binaries.
Explanation Expansion of the application 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.
ADMU0120I: {0} will not be uploaded since it already exists in the target repository.
Explanation File already exists. Action No user action is required.
ADMU0121E: Unexpected exception {0} while checking existence of {1} in the target repository. {1} will not be uploaded.
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 wsadmin.sh.
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. Action More info at:
ADMU0124I: The system clock of the new node ({0}) is not synchronized with that of the dmgr ({1}).
Explanation To add a node, the system clock of the node to be added must be fairly close to that of the dmgr. Action Change the new node system clock to be the same as that of the dmgr.
ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the dmgr.
Explanation The addNode command failed because the clock of the new node is out of synchronization with the dmgr. Action Change the clock of the new node to be within the specified minutes of the clock of the dmgr.
ADMU0126E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}); the node has not been added.
Explanation The dmgr version is earlier than that of the specified node. The product requires that the dmgr 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 dmgr to the same version as the node, or a later version than the node.
ADMU0127E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}).
Explanation The dmgr version is earlier than that of the specified node. The product requires that the dmgr version be at the same version as the node, or at a later version. Action Upgrade the dmgr to the same version as the node, or a later version than 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.
ADMU0129E: The dmgr is of an older version or has less feature packs installed than this node; the node has not been added
Explanation The dmgr version is earlier than that of the node. The product requires that the dmgr version be at the same version as the node, or at a later version. Action Upgrade the dmgr to the same version as the node, or a later version than the node.
ADMU0180E: Duplicate Entry Exception: An exception occurred 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 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 dmgr cell unique. Then run the addNode command.
ADMU0181E: Duplicate Entry Exception: An exception occurred 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 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 dmgr cell. Then run the addNode command.
ADMU0182E: Duplicate Entry Exception: An exception occurred 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 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 dmgr cell. Then run the addNode command.
ADMU0183E: Duplicate Entry Exception: An exception occurred 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 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 dmgr cell. Then run the addNode command.
ADMU0211I: Error details may be seen in the file: {0}
Explanation 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 The specified node has been successfully renamed. Action No user action is required.
ADMU0251I: Begin changing node name for {0}
Explanation The process of renaming the node has started. Action No user action is required.
ADMU0254I: Update the node configuration for {0} on the Deployment Manager.
Explanation The particular node configuration is updated. Action No user action is required.
ADMU0300I: The node {0} was successfully added to the {1} cell.
Explanation The specified node was successfully added to the specified cell. Action No user action is required.
ADMU0302I: Any cell-level documents from the standalone {0} configuration have not been migrated to the new cell.
Explanation None Action No user action is required.
ADMU0303I: Update the configuration on the {0} Deployment Manager with values from the old cell-level documents.
Explanation The configuration on the specified dmgr was updated. Action No user action is required.
ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.
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.
ADMU0305I: Install applications onto the {0} cell using wsadmin $AdminApp or the Administrative Console.
Explanation None Action No user action is required.
ADMU0306I: Note:
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.
ADMU0307I: You might want to:
Explanation This message suggests that you do the actions associated with the messages that immediately follow this message. Action No user action is required.
ADMU0308I: The node {0} and associated applications were successfully added to the {1} cell.
Explanation The specified node and its associated applications were successfully added to the specified cell. Action No user action is required.
ADMU0401I: Begin syncNode operation for node {0} with Deployment Manager {1}: {2}
Explanation The specified node is being synchronized with the dmgr. Action No user action is required.
ADMU0402I: The configuration for node {0} has been synchronized with Deployment Manager {1}: {2}
Explanation The specified node was successfully synchronized with the dmgr. Action No user action is required.
ADMU0403E: The syncNode command may only be run when the node agent is stopped. Either stop the node agent or use the administrative console or wsadmin to synchronize the node.
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.
ADMU0500I: Retrieving server status for {0}
Explanation The status of the specified service is being retrieved. Action No user action is required.
ADMU0501E: Server name not specified; must supply the name of a server or -all for all servers.
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.
ADMU0503I: Retrieving server status for all servers
Explanation The server status is being retrieved for all servers. Action No user action is required.
ADMU0505I: Servers found in configuration:
Explanation Informational message printed before a list of servers. Action No user action is required.
ADMU0506I: Server name: {0}
Explanation The server name is displayed. Action No user action is required.
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 The state of the specified server is given. Action No user action is required.
ADMU0509I: The {0} "{1}" cannot be reached. It appears to be stopped.
Explanation The server cannot be reached and seems to be stopped. Action No user action is required.
ADMU0510I: Server {0} is now {1}
Explanation The state of the specified server is given. Action No user action is required.
ADMU0512I: Server {0} cannot be reached. It appears to be stopped.
Explanation The server cannot be reached and seems to be stopped. Action No user action is required.
ADMU0514E: Unsupported JMX Connector: {0}
Explanation A Java Management Extensions (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 The queue manager is being created for the specified node on the specified server. Action No user action is required.
ADMU0524I: WebSphere Embedded Messaging support not installed; Queue Manager not created
Explanation Embedded messaging was not installed. The queue manager was not created. Action No user action is required.
ADMU0525I: Details of Queue Manager creation may be seen in the file: {0}
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.
ADMU0526I: Deleting Queue Manager for node {0} on server {1}
Explanation The queue manager is being deleted on the specified node and the specified server. Action No user action is required.
ADMU0527I: WebSphere Embedded Messaging support not installed; Queue Manager not deleted from server {0}
Explanation Embedded messaging support is not installed. The queue manager cannot be deleted from the specified server. Action No user action is required.
ADMU0528I: Details of Queue Manager deletion may be seen in the file: {0}
Explanation We can see the details of the deletion of the queue manager in the specified file. Action Look in the file for more information.
ADMU0529E: Unexpected exception {0} thrown while restoring application binaries from the base configuration.
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 EAR file to the location specified on the binariesURL attribute. The attribute is in the corresponding deployment.xml configuration file.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
Explanation We can use the trace option to gather additional 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 The node agent could not be registered as a Windows service. Action Check the addNode.log file 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 Check addNode.log for additional information.
ADMU1502E: If you specify "-serviceUserName" or "-servicePassword" then specify both of these as well as "-registerService".
Explanation We must specify "-serviceUserName" and "-servicePassword" together. We must also specify "-registerService" Action Obtain values for the above and resubmit request.
ADMU2001I: Begin removal of node: {0}
Explanation Removal of the node has started. Action No user action is required.
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 All server processes are being stopped for the specified node. Action No user action is required.
ADMU2012I: Backing up Network Deployment configuration.
Explanation The product configuration is being backed up. Action No user action is required.
ADMU2014I: Restoring original configuration.
Explanation The original product configuration is being restored. Action No user action is required.
ADMU2015I: This exception can be ignored by specifying -force.
Explanation Informational message explaining that the -force option can be used to eliminate the message. Action No user action is required.
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, run the cleanupNode utility on the dmgr to remove the configuration files for this node.
ADMU2017I: The local original configuration has been restored.
Explanation The local configuration file has been restored. Action No user action is required.
ADMU2018I: Node {0} has been removed from the Deployment Manager configuration.
Explanation The specified node has been removed from the dmgr configuration. Action No user action is required.
ADMU2019I: Removing installed applications from node {0}.
Explanation The installed applications are being removed from the specified node. Action No user action is required.
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 Informational message marking the progress of the program. Action No user action is required.
ADMU2022I: Removing cluster member {0} from cluster {1}.
Explanation The specified cluster member is being removed from the specified cluster. Action No user action is required.
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 The specified node has been successfully removed. Action No user action is required.
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. You might need to run the cleanupNode utility to remove this node from the dmgr configuration.
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 the addNode command before attempting to run the removeNode command.
ADMU2027E: Exception {0} caught in creating varmap for scope {1}, {2}, {3}
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 EAR files to their appropriate locations.
ADMU2028E: Exception {0} caught in expanding ear at {1} to {2}
Explanation The EAR file could not be expanded to the destination. Action Run the EARExpander tool to expand the EAR file to its appropriate locations.
ADMU2029E: Exception {0} caught in creating EAR Object from {1}
Explanation The 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.
ADMU2030E: Exception {0} caught in getting binariesURL from {1}
Explanation The specified deployment.xml file could not be loaded to obtain the value of the binariesURL attribute. The 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.
ADMU2031I: Any applications that were uploaded to the {0} cell configuration during addNode using the -includeapps option are not uninstalled by removeNode.
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.
ADMU2032I: Use wsadmin or the Administrative Console to uninstall any such applications from the Deployment Manager.
Explanation We can use wsadmin.sh or the administrative console to uninstall applications from the dmgr. Action No user action is required.
ADMU2033I: Any buses that were uploaded to the {0} cell configuration during addNode using the -includebuses option are not uninstalled by removeNode.
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.
ADMU2034I: Use wsadmin or the Administrative Console to uninstall any such buses from the Deployment Manager.
Explanation We can use wsadmin.sh or the administrative console to uninstall any buses from the dmgr. Action No user action is required.
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 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 dmgr.
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 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 dmgr.
ADMU2037W: The {0} node host name that the product is federating does not match the {1} dmgr host name. The local operating system registry is usually only supported when the cell is configured on a single machine.
Explanation The host names for the dmgr 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.
ADMU2091E: Exception {0} caught checking product extensions on the node or the Deployment Manager.
Explanation The product extensions installed on the node or the dmgr could not be determined. 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 between the node and the dmgr. Action Check the product extensions installed on both the node and the dmgr. Additional product extensions might 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.
ADMU2095I: Any security domains that were uploaded to the {0} cell configuration during addNode are not removed by removeNode.
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.
ADMU2096I: Any security domains that are no longer required can be removed using the deleteSecurityDomain task using the force option. They can also be manually removed.
Explanation We can use the deleteSecurityDomain task with the force option to remove any unused security domains. We can also manually delete the security domains that are not required any more. Action No user action is required.
ADMU3000I: Server {0} open for e-business; process id is {1}
Explanation The specified server has started. The process id indicates the PID for Distributed platforms while on z/OS it represents the Server token(stoken). Action No user action is required.
ADMU3001I: Server {0} open for recovery; process id is {1}
Explanation The specified server is recovering. Action No user action is required.
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. The server process failed to start. Action Record and save the exception information in this message for further problem determination.
ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, 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 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.
ADMU3013I: Server recovery complete. Server stopped.
Explanation The server has completed recovery and has stopped. Action No user action is required.
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 another 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 value for the -timeout option or perform problem determination on the server to investigate possible errors.
ADMU3100I: Reading configuration for server: {0}
Explanation The server configuration is being read. Action No user action is required.
ADMU3101I: Using explicit host and port {0}:{1} for server: {2}
Explanation The specified hot and the specified port were used. Action No user action is required.
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 The server process launched. The product is waiting for initialization status. Action No user action is required.
ADMU3201I: Server stop request issued. Waiting for stop status.
Explanation A request to stop the server was made. The product is waiting for server status. Action No user action is required.
ADMU3220I: Base server runtime initialized. Waiting for application initialization.
Explanation The server initialized. The product is waiting for application initialization. Action No user action is required.
ADMU3300I: Launch script for server created: {0}
Explanation The server launch script has been successfully created. Action No user action is required.
ADMU3400I: Server launched. No initialization status. Process id is: {0}
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.
ADMU3401I: Server stop request issued. No stop status requested.
Explanation A stop server request was issued without a stop status request. Action No user action is required.
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 The stopServer command completed successfully. Action No user action is required.
ADMU4018E: "-script" option is not supported on zOS platform.
Explanation An error occurred when the program ran. 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 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 user name and password. If you are using a command, 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 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.
ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port.
Explanation A connection could not be made to the dmgr. Action Ensure that the dmgr is running. Ensure that the proper host name 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 The trace option can be used to obtain a full trace of the failure. Action No user action is required.
ADMU5001I: Backing up config directory {0} to file {1}
Explanation The specified configuration directory is being backed up to the specified file. Action No user action is required.
ADMU5002I: {0} files successfully backed up
Explanation The specified number of files were backed up. Action No user action is required.
ADMU5501E: The backup file specified {0} does not exist.
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.
ADMU5502I: The directory {0} already exists; renaming to {1}
Explanation The specified directory for the restored configuration already exists and is being renamed to the specified directory. Action No user action is required.
ADMU5503E: The restore location could not be renamed - another process may be using this subdirectory
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.
ADMU5504I: Restore location successfully renamed
Explanation The specified location has been renamed. Action No user action is required.
ADMU5505I: Restoring file {0} to location {1}
Explanation The specified file is being restored to the specified location. Action No user action is required.
ADMU5506I: {0} files successfully restored
Explanation The specified number of files were successfully restored. Action No user action is required.
ADMU6001I: Begin App Preparation -
Explanation Preparation of applications has begun. Action No user action is required.
ADMU6002I: Begin Asset Preparation -
Explanation Preparation of assets has begun. Action No user action is required.
ADMU6009I: Processing complete.
Explanation Processing complete. Action No user action is required.
ADMU6012I: Exception in run {0}
Explanation NONE Action No user action is required.
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 the 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 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.
ADMU7006W: The cell name contained in the backup file is not the same as the current cell name of the 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, 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 might be full, or the directory might not have write permission. Action Use EARExpander command to extract the EAR file.
ADMU7009E: There is an unexpected exception in expandArchive. The archive file {0} will not be extracted in following paths {1}. Exception: {2}
Explanation The disk might be full, or the directory might not have write permission. Action Use EARExpander command to extract the archive 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 No user action is required.
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 No user action is required.
ADMU7703I: The Windows Service {0} associated with {1} is now being deregistered.
Explanation When a server is removed, the corresponding Windows service is removed from the registry. Action No user action is required.
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 the 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 could not be removed from the registry. Action Examine the error message and make correction accordingly.
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 Verify that a Windows service associated with the specified server exists.
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 that the product installation is correct.
ADMU7709E: Unexpected exception while processing server: {0}; exception = {1}
Explanation An unexpected exception has been detected. Action Verify that the product installation is correct.
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 that the product installation is correct.
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 that the product installation is correct.
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 The generic server started successfully. Action No user action is required.
ADMU7771E: Generic Server: {0} already running - use the "-forceGenericServerStart" to force server start!
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.
ADMU7772I: Generic Server: {0} STOPPED successfully.
Explanation The generic server successfully stopped. Action No user action is required.
ADMU7773E: Generic Server: {0} is not RUNNING
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.
ADMU8001E: An error occurred during node registration; rolling back to original configuration.
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.
ADMU8002I: Exchanging signers between adminagent and node with path {0}.
Explanation Exchanging signers between adminagent and node to be registered. Action No user action is required.
ADMU8003E: An error occurred when calling registerNode command; rolling back to original configuration.
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.
ADMU8004I: Backing up the original config directory of the node to be registered.
Explanation The original configuration files are being saved before the utility program changes them. Action No user action is required.
ADMU8005I: Admin preferred authorization mechanism is set to {0}.
Explanation Security admin preferred authorization mechanism is set to RSAToken. Action No user action is required.
ADMU8006E: An error occurred when calling deregisterNode command.
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.
ADMU8007I: Exchanged signers successfully.
Explanation Exchanged security signers successfully. Action No user action is required.
ADMU8008I: Restoring all original pre-registered files of the profile after deregistration.
Explanation The original configuration files are being restored after the profile was removed from the registry. Action No user action is required.
ADMU8009I: Begin deregistration of Application Server with path {0}.
Explanation The node will be deregistered with an adminagent. Action No user action is required.
ADMU8010I: Begin registration of Application Server with path {0}
Explanation Registration of the profile has begun. Action No user action is required.
ADMU8012I: Application Server with path {0} has been successfully registered.
Explanation Registration of the specified profile successfully completed. Action No user action is required.
ADMU8013I: Application Server with path {0} has been successfully deregistered.
Explanation The node was successfully deregistered with an adminagent. Action No user action is required.
ADMU8014I: The administrative subsystem for the registered node has been successfully initialized.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8015I: The administrative subsystem for the registered node has been successfully started.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8016I: The administrative subsystem for the deregistered node has been successfully stopped.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8017I: The administrative subsystem for deregistered node has been successfully destroyed.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8018E: Error running registerNode on non supported environment.
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 admin 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 admin agent. The admin agent is the AdminAgent MBean.
ADMU8019E: Error trying to register a non supported profile.
Explanation The node you are trying to register is not a stand-alone server node. We can only register a stand-alone application server node. Action Ensure that the node you are trying to register to an admin agent is a stand-alone application server node.
ADMU8020E: Error running registerNode on non supported environment.
Explanation The node could not be registered using the registerNode because no connection was made to the admin agent during node registration. The admin agent is the AdminAgent MBean. Action Ensure that a connection is made to the correct port of the admin agent.
ADMU8021I: Backing up the original config directory of the profile to be deregistered.
Explanation The original configuration files for the profile are being saved before they are removed from the registry. Action No user action is required.
ADMU8022E: An error occurred when calling registerWithAdminAgent command; rolling back to original configuration.
Explanation Failed running registerWithAdminAgent command of the profile to be registered. Action Review the associated error in registerNode.log or turn on trace to diagnose the problem and look for trace information in the trace log.
ADMU8023E: An error occurred when invoking initializeProfile operation on AdminAgent mbean; rolling back to original configuration.
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.
ADMU8024E: An error occurred when invoking startProfile operation on AdminAgent mbean; rolling back to original configuration.
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.
ADMU8025E: An error occurred when calling deregisterWithAdminAgent command; rolling back to original configuration.
Explanation Failed running deregisterWithAdminAgent command. Action Review the associated error in deregisterNode.log or turn on trace to diagnose the problem.
ADMU8026E: An error occurred when invoking stopProfile operation on AdminAgent mbean; rolling back to original configuration.
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.
ADMU8027E: An error occurred when invoking destroyProfile operation on AdminAgent mbean; rolling back to original configuration.
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.
ADMU8028E: An error occurred during node deregistration; rolling back to original configuration.
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.
ADMU8029E: Error running deregisterNode on non supported environment.
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 admin agent. The admin agent is the AdminAgent MBean. Action Remove a node from the registry when the node is located on the same machine as the admin agent.
ADMU8030E: Failed finding backup files so unregister node cannot continue.
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 the environment.
ADMU8031E: Failed getting AdminAgent mbean, registerNode cannot continue.
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.
ADMU8032E: Failed getting AdminAgent mbean, deregisterNode cannot continue.
Explanation The AdminAgent MBean, which is the admin 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.
ADMU8033E: Error trying to register a node that has been registered already.
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.
ADMU8034E: The profile path {0} does not exist locally on the Administrative Agent system.
Explanation Make sure the profile path you specify is correct and the profile path exists locally on the Administrative Agent system. Action Review the associated error to diagnose the problem.
ADMU8035E: Ensure that the AdminAgent is running on the specified port.
Explanation A connection cannot be made to the admin agent. The admin agent is the AdminAgent MBean. Action Ensure that the admin agent is running. Ensure that the proper port is used when attempting to connect to the process.
ADMU8036I: Registering the node with an AdminAgent.
Explanation The node is being registered with an adminagent. Action No user action is required.
ADMU8037I: Backing up the original wsadmin.properties file of the node to be registered.
Explanation The wsadmin.properties file is being saved before it is changed. Action No user action is required.
ADMU8038I: Deregistering the node with an adminagent.
Explanation The node will be deregistered with an adminagent. Action No user action is required.
ADMU8039E: Required option type is expected if you try to register a WebSphere plug-in type.
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.
ADMU8040I: The admin agent is initializing the administrative subsystem for the registered node.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8041I: The admin agent is starting the administrative subsystem for the registered node.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8042I: Node has been successfully registered.
Explanation The node has been registered with an adminagent. Action No user action is required.
ADMU8043I: The admin agent is stopping the administrative subsystem for the deregistered node.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8044I: The admin agent is destroying the administrative subsystem for the deregistered node.
Explanation This message is for informational purposes only. Action No user action is required.
ADMU8045I: Node has been successfully deregistered.
Explanation The node has been deregistered from an adminagent. Action No user action is required.
ADMU8046E: The admin agent port number specified for {0} connector is invalid, registerNode cannot continue.
Explanation Failed to register the node because the port number specified is invalid. Action Check your admin agent serverindex.xml and find the correct port number of the connector.
ADMU8047E: An error occurred when invoking listProfiles operation on AdminAgent mbean; rolling back to original configuration.
Explanation Failed invoking listProfiles operation on AdminAgent mbean. Action Review the associated error in registerNode.log or turn on trace to diagnose the problem.
ADMU8048E: Error trying to unregister node that has not been registered.
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.
ADMU8049E: An error occurred when adminagent tried to exchange signers with the node.
Explanation An error occurred 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.
ADMU8050E: An error occurred during signers removal.
Explanation An error occurred when adminagent tried to remove signers that were exchanged during node registration. Action Review the associated error in deregsiterNode.log or turn on trace to diagnose the problem.
ADMU8051I: Removed signers successfully.
Explanation Removed security signers that were exchanged during node registration successfully. Action No user action is required.
ADMU8052I: Removing signers exchanged during node registration.
Explanation Removing security signers that were exchanged during node registration. Action No user action is required.
ADMU8053I: Successfully connected to AdminAgent Server: {0}:{1}
Explanation Informational message indicating that the program has established communications with the AdminAgent. Action No user action is required.
ADMU8054E: Failed to create managed node with name {0}.
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.
ADMU8055E: An error occurred when trying to create the managed node.
Explanation An error occurred when trying to create managed node. Action Review the associated error in registerNode.log or turn on trace to diagnose the problem.
ADMU8056E: Error removing the managed node from an adminagent.
Explanation An error occurred during managed node removal from an adminagent. Action Review the associated error or turn on trace to diagnose the problem.
ADMU8057E: An error occurred during node deregistration; rolling back to original configuration.
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.
ADMU8058E: An error occurred when trying to set the admin preferred authorization mechanism to {0}
Explanation An error occurred 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.
ADMU8059E: An error occurred when trying to get the managed node name.
Explanation An error occurred when trying to get the managed node name. Action Review the associated error in registerNode.log or turn on trace to diagnose the problem.
ADMU8060E: An error occurred when trying to get the profile key.
Explanation An error occurred when trying to get the profile key. Action Review the associated error in registerNode.log or turn on trace to diagnose the problem.
ADMU8061E: If you specify the user name, also specify the password.
Explanation We 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.
ADMU8062E: If you specify the password, also specify the user name.
Explanation We 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.
ADMU8063E: If you specify the nodeusername, also specify the nodepassword.
Explanation We 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.
ADMU8064E: If you specify the nodepassword, also specify the nodeusername.
Explanation We 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.
ADMU8065E: You did not specify all required parameters.
Required parameters you did not specify are {0}
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.
ADMU8066E: You specified a non supported parameter {0}
Explanation We cannot use non supported parameters. Action Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem.
ADMU8067E: Parameter {0} was specified twice.
Explanation We cannot specify the same parameter more than once. Action Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem.
ADMU8068E: If you specify the port, also specify the conntype.
Explanation We must specify conntype option if you specified port option. Action Review the associated error to diagnose the problem.
ADMU8069E: If you specify the conntype, also specify the port.
Explanation We must specify port option if you specified conntype option. Action Review the associated error to diagnose the problem.
ADMU8070I: All Application Server nodes have been successfully registered.
Explanation Registration of all specified nodes successfully completed. Action No user action is required.
ADMU8071I: All Application Server nodes have been successfully deregistered.
Explanation Deregistration of all specified nodes successfully completed. Action No user action is required.
ADMU8072E: Application Server nodes with profilePath {0} failed to register with the admin agent.
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.
ADMU8073E: Application Server nodes with profilePath {0} failed to deregister from the admin agent.
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.
ADMU8074E: The admin agent port number specified for {0} connector is invalid, deregisterNode cannot continue.
Explanation Failed to deregister the node because the port number specified is invalid. Action Check your admin agent serverindex.xml and find the correct port number of the connector.
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, but one was not provided. Action Provide a parameter for this option.
ADMU9993E: Invalid parameter {0}
Explanation The parameter provided is not valid for the given option. Action Provide a different parameter.
ADMU9994W: Options username or password is not needed to start a server and it will be ignored.
Explanation The given option is not needed to start a server and it is ignored. Action No user action is required.