ADMU

ADMU0001I: Begin federation of node {0} with Deployment Manager at {1}:{2}.
ADMU0002E: Exception attempting to process server {0}: {1}
ADMU0003I: Node {0} has been successfully federated.
ADMU0004E: Exception attempting to get result from configuration synchronization {0}
ADMU0005E: Error synchronizing repositories {0}
ADMU0006E: Exception creating Deployment Manager connection: {0}
ADMU0007E: Error while copying {0}
ADMU0008E: Error obtaining MBean by name {0}: {1}
ADMU0009I: Successfully connected to Deployment Manager Server: {0}:{1}
ADMU0010E: Error obtaining repository client {0}
ADMU0011E: Error creating configuration in the cell repository {0}
ADMU0012I: Creating Node Agent configuration for node: {0}
ADMU0013I: A document already exists at the cell level: {0}
ADMU0014I: Adding node {0} configuration to cell: {1}
ADMU0015I: Backing up the original cell repository.
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0017E: Error occurred closing an input/output stream {0}
ADMU0018I: Launching Node Agent process for node: {0}
ADMU0019E: Error occurred reading from an input stream {0}
ADMU0020I: Reading configuration for Node Agent process: {0}
ADMU0021E: Error occurred stopping server {0}
ADMU0022I: Node Agent launched. Waiting for initialization status.
ADMU0023E: Exception waiting for server initialization {0}
ADMU0024I: Deleting the old backup directory.
ADMU0025E: Given host and port do not point to a Deployment Manager.
ADMU0026I: An error occurred during federation; rolling back to original configuration.
ADMU0027E: An error occurred during federation {0}; rolling back to original configuration.
ADMU0028I: Log generated.
ADMU0029E: An error occurred during node removal: {0}
ADMU0030I: Node Agent initialization completed successfully. Process id is: {0}
ADMU0031E: Node Agent launched but failed initialization. Process id was: {0}
ADMU0032E: It is not valid to run addNode on the same node as the Deployment Manager: {0}
ADMU0033E: The node {0} already has been added to the cell.
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}
ADMU0035E: WebSphere Express nodes are not supported in a Network Deployment cell.
ADMU0036E: The Deployment Manager cannot lookup by name host {0} at address {1}
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.
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.
ADMU0039E: There is already a node named {0} in the cell.
ADMU0040E: Exception on MBean invocation {0} {1} {2}
ADMU0041E: Another addNode or removeNode operation is currently in progress. Please attempt this operation later.
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.
ADMU0043E: Error trying to federate a node that is still registered to an AdminAgent.
ADMU0044E: It is not valid to run syncNode on the same node as the Deployment Manager: {0}
ADMU0050E: Exception encountered while checking if node {1} can join node group {2}. {0}
ADMU0051E: Exception occurred while converting node group {2} to sysplex node group for node {1}. {0}
ADMU0052E: Exception occurred while adding node {1} to node group {2}. {0}
ADMU0053E: Exception occurred while removing node {1} from all node groups. {0}
ADMU0054W: {0} WARNING(S) occurred while checking if node {1} can join node group {2}. {3}
ADMU0055W: {0} WARNING(S) occurred while converting node group {2} to sysplex node group for node {1}. {3}
ADMU0056W: {0} WARNING(S) occurred while adding node {1} to node group {2}. {3}
ADMU0057W: {0} WARNING(S) occurred while removing node {1} from all node groups. {2}
ADMU0058I: Removing node {0} from all node groups.
ADMU0059I: Adding node {0} to node group {1}.
ADMU0060W: The -portprops option overrides the -startingport option.
ADMU0061W: The -nodeagentshortname option is used in a z/OS environment only.
ADMU0062E: The -asExistingNode option cannot be used with any of the following options: {0}
ADMU0063E: The {0} node does not exist in the cell so the -asExistingNode option cannot be used.
ADMU0064E: addNode can only be run from a base (application server) profile
ADMU0070W: Retrieving signer certificates from dmgr failed - this may cause node federation to fail.
ADMU0071E: Exception occurred during security authentication.
ADMU0088E: No Server MBean named {0} in this process {1}:{2}
ADMU0089E: Exception caught during rollback of application binaries {0}
ADMU0111E: Program exiting with error: {0}
ADMU0112E: Exception writing serverindex.xml file: {0}
ADMU0113E: Program exiting with error: {0}, resulting from: {1}
ADMU0114E: Exception launching Node Agent process: {0}
ADMU0115I: Trace mode is on.
ADMU0116I: Tool information is being logged in file {0}
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.
ADMU0118E: The log file cannot be written to location {0}; please specify a different location with -logfile
ADMU0119E: Unexpected exception {0} in rolling back application binaries.
ADMU0120I: {0} will not be uploaded since it already exists in the target repository.
ADMU0121E: Unexpected exception {0} while checking existence of {1} in the target repository. {1} will not be uploaded.
ADMU0122E: Exception {0} copying application files from {1} to {2}.
ADMU0123E: Could not find text for message ID {0}.
ADMU0124I: The system clock of the new node ({0}) is not synchronized with that of the deployment manager ({1}).
ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager.
ADMU0126E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}); the node has not been added.
ADMU0127E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}).
ADMU0128I: Starting tool with the {0} profile
ADMU0129E: The deployment manager is of an older version or has less feature packs installed than this node; the node has not been added
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.
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.
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.
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.
ADMU0211I: Error details may be seen in the file: {0}
ADMU0222I: Exception accessing the plugin-cfg.xml file.
ADMU0250I: Node {0} has been successfully renamed to {1}.
ADMU0251I: Begin changing node name for {0}
ADMU0254I: Update the node configuration for {0} on the Deployment Manager.
ADMU0300I: The node {0} was successfully added to the {1} cell.
ADMU0302I: Any cell-level documents from the standalone {0} configuration have not been migrated to the new cell.
ADMU0303I: Update the configuration on the {0} Deployment Manager with values from the old cell-level documents.
ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell.
ADMU0305I: Install applications onto the {0} cell using wsadmin $AdminApp or the Administrative Console.
ADMU0306I: Note:
ADMU0307I: You might want to:
ADMU0308I: The node {0} and associated applications were successfully added to the {1} cell.
ADMU0401I: Begin syncNode operation for node {0} with Deployment Manager {1}: {2}
ADMU0402I: The configuration for node {0} has been synchronized with Deployment Manager {1}: {2}
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.
ADMU0500I: Retrieving server status for {0}
ADMU0501E: Server name not specified; must supply the name of a server or -all for all servers.
ADMU0503I: Retrieving server status for all servers
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: {0}
ADMU0507I: No servers found in configuration under: {0}
ADMU0508I: The {0} "{1}" is {2}
ADMU0509I: The {0} "{1}" cannot be reached. It appears to be stopped.
ADMU0510I: Server {0} is now {1}
ADMU0512I: Server {0} cannot be reached. It appears to be stopped.
ADMU0514E: Unsupported JMX Connector: {0}
ADMU0521E:
No node named "{0}" is found in this cell.
ADMU0522E: No server by this name in the configuration: {0}
ADMU0523I: Creating Queue Manager for node {0} on server {1}
ADMU0524I: WebSphere Embedded Messaging support not installed; Queue Manager not created
ADMU0525I: Details of Queue Manager creation may be seen in the file: {0}
ADMU0526I: Deleting Queue Manager for node {0} on server {1}
ADMU0527I: WebSphere Embedded Messaging support not installed; Queue Manager not deleted from server {0}
ADMU0528I: Details of Queue Manager deletion may be seen in the file: {0}
ADMU0529E: Unexpected exception {0} thrown while restoring application binaries from the base configuration.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU1500W: Exception caught while registering node agent as Windows service - please check addNode.log for details
ADMU1501W: Exception caught while de-registering node agent as Windows service - please check addNode.log for details
ADMU1502E: If you specify "-serviceUserName" or "-servicePassword" then you must specify both of these as well as "-registerService".
ADMU2001I: Begin removal of node: {0}
ADMU2003E: No setupCmdLine file found to modify: {0}
ADMU2004E: An exception occurred
ADMU2010I: Stopping all server processes for node {0}
ADMU2012I: Backing up Network Deployment configuration.
ADMU2014I: Restoring original configuration.
ADMU2015I: This exception can be ignored by specifying -force.
ADMU2016E: Node {0} has not been removed from the Deployment Manager configuration.
ADMU2017I: The local original configuration has been restored.
ADMU2018I: Node {0} has been removed from the Deployment Manager configuration.
ADMU2019I: Removing installed applications from node {0}.
ADMU2020E: Exception removing applications {0}
ADMU2021I: Removing all servers on this node from all clusters in the cell.
ADMU2022I: Removing cluster member {0} from cluster {1}.
ADMU2023E: Exception removing servers from clusters {0}
ADMU2024I: Removal of node {0} is complete.
ADMU2025W: Removal of node {0} is complete, but there were errors.
ADMU2026E: Node {0} is not incorporated into any cell.
ADMU2027E: Exception {0} caught in creating varmap for scope {1}, {2}, {3}
ADMU2028E: Exception {0} caught in expanding ear at {1} to {2}
ADMU2029E: Exception {0} caught in creating EAR Object from {1}
ADMU2030E: Exception {0} caught in getting binariesURL from {1}
ADMU2031I: Any applications that were uploaded to the {0} cell configuration during addNode using the -includeapps option are not uninstalled by removeNode.
ADMU2032I: Use wsadmin or the Administrative Console to uninstall any such applications from the Deployment Manager.
ADMU2033I: Any buses that were uploaded to the {0} cell configuration during addNode using the -includebuses option are not uninstalled by removeNode.
ADMU2034I: Use wsadmin or the Administrative Console to uninstall any such buses from the Deployment Manager.
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.
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.
ADMU2037W: The {0} node host name that the product is federating does not match the {1} deployment manager host name. The local operating system registry is usually only supported when the cell is configured on a single machine.
ADMU2091E: Exception {0} caught checking product extensions on the node or the Deployment Manager.
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}.
ADMU2093E: Custom property {0} has no value.
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.
ADMU2095I: Any security domains that were uploaded to the {0} cell configuration during addNode are not removed by removeNode.
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.
ADMU3000I: Server {0} open for e-business; process id is {1}
ADMU3001I: Server {0} open for recovery; process id is {1}
ADMU3002E: Exception attempting to process server {0}
ADMU3007E: Exception {0}
ADMU3009E: Exception waiting for server initialization {0}
ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under {0} should contain failure information.
ADMU3012E: Exception attempting to get free port for status socket {0}
ADMU3013I: Server recovery complete. Server stopped.
ADMU3014W: Server recovery complete, problems occurred during recovery. Server log files should contain failure information.
ADMU3019E: Exception waiting for server stop {0}
ADMU3027E: An instance of the server may already be running: {0}
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}
ADMU3029I: Conflict detected on port {0} for endpoint {2} of the server {1}
ADMU3040E: Timed out waiting for server initialization: {0} seconds
ADMU3054E: No Server MBean named {0} in this process {1}:{2}
ADMU3055E: Error obtaining MBean by name {0}: {1}
ADMU3060E: Timed out waiting for server shutdown.
ADMU3100I: Reading configuration for server: {0}
ADMU3101I: Using explicit host and port {0}:{1} for server: {2}
ADMU3111E: Server stop requested but failed to complete.
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU3220I: Base server runtime initialized. Waiting for application initialization.
ADMU3300I: Launch script for server created: {0}
ADMU3400I: Server launched. No initialization status. Process id is: {0}
ADMU3401I: Server stop request issued. No stop status requested.
ADMU3402E: Server name not specified; must supply the name of a server.
ADMU3522E: No server by this name in the configuration: {0}
ADMU4000I: Server {0} stop completed.
ADMU4018E: "-script" option is not supported on zOS platform.
ADMU4111E: Program exiting with error: {0}
ADMU4112I: Error details may be seen in the file: {0}
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.
ADMU4122E: The specified server may not be running, or no appropriate username and password are provided if the specified server runs in secure mode
ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port. Also ensure that the security configuration in ssl.client.props on the node is compatible with the Deployment Manager.
ADMU4211I: To obtain a full trace of the failure, use the -trace option.
ADMU5001I: Backing up config directory {0} to file {1}
ADMU5002I: {0} files successfully backed up
ADMU5501E: The backup file specified {0} does not exist.
ADMU5502I: The directory {0} already exists; renaming to {1}
ADMU5503E: The restore location could not be renamed - another process may be using this subdirectory
ADMU5504I: Restore location successfully renamed
ADMU5505I: Restoring file {0} to location {1}
ADMU5506I: {0} files successfully restored
ADMU6001I: Begin App Preparation -
ADMU6002I: Begin Asset Preparation -
ADMU6009I: Processing complete.
ADMU6012I: Exception in run {0}
ADMU7004E: Unexpected exception while building cache entry for {0} and {1}. Exception is: {2}. All the related binaries may not be deleted/updated.
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.
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.
ADMU7008E: Unexpected exception in expandEar. The ear file {0} will not be extracted in following paths {1}. Exception: {2}
ADMU7009E: There is an unexpected exception in expandArchive. The archive file {0} will not be extracted in following paths {1}. Exception: {2}
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.
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.
ADMU7703I: The Windows Service {0} associated with {1} is now being deregistered.
ADMU7704E: Failed while trying to start the Windows Service associated with server: {0};
probable error executing WASService.exe: {1}
ADMU7705E: Failed while trying to stop the Windows Service associated with server: {0};
probable error executing WASService.exe: {1}
ADMU7706E: Failed while trying to deregister the Windows Service {0};
probable error executing WASService.exe: {1}
ADMU7707E: Failed while trying to determine the Windows Service name for server: {0};
probable error executing WASService.exe: {1}
ADMU7708E: Failed while trying to determine the Windows Service log file name for server: {0};
probable error executing WASService.exe: {1}
ADMU7709E: Unexpected exception while processing server: {0}; exception = {1}
ADMU7710E: Unexpected exit code {1} from WASService.exe while executing {0}
ADMU7711E: Unexpected exception associated with WASService.exe: {0} during processing of server with name: {1}
ADMU7712E: Failed while trying to determine the Windows Service status for service: {0};
probable error executing WASService.exe: {1}
ADMU7713E: WASService command for server {0} failed. Unexpected exit code {1} from running {2}.
ADMU7714I: WASService command for server {0} completed successfully.
ADMU7750E: The {0} command has failed because another process has temporarily requested exclusive access to {1}. Please wait a few minutes and try again.
ADMU7770I: Generic Server: {0} STARTED successfully.
ADMU7771E: Generic Server: {0} already running - use the "-forceGenericServerStart" to force server start!
ADMU7772I: Generic Server: {0} STOPPED successfully.
ADMU7773E: Generic Server: {0} is not RUNNING
ADMU8001E: An error occurred during node registration; rolling back to original configuration.
ADMU8002I: Exchanging signers between adminagent and node with path {0}.
ADMU8003E: An error occurred when calling registerNode command; rolling back to original configuration.
ADMU8004I: Backing up the original config directory of the node to be registered.
ADMU8005I: Admin preferred authorization mechanism is set to {0}.
ADMU8006E: An error occurred when calling deregisterNode command.
ADMU8007I: Exchanged signers successfully.
ADMU8008I: Restoring all original pre-registered files of the profile after deregistration.
ADMU8009I: Begin deregistration of Application Server with path {0}.
ADMU8010I: Begin registration of Application Server with path {0}
ADMU8012I: Application Server with path {0} has been successfully registered.
ADMU8013I: Application Server with path {0} has been successfully deregistered.
ADMU8014I: The administrative subsystem for the registered node has been successfully initialized.
ADMU8015I: The administrative subsystem for the registered node has been successfully started.
ADMU8016I: The administrative subsystem for the deregistered node has been successfully stopped.
ADMU8017I: The administrative subsystem for deregistered node has been successfully destroyed.
ADMU8018E: Error running registerNode on non supported environment.
ADMU8019E: Error trying to register an unsupported profile. You can only register a stand-alone application server node with an administrative agent.
ADMU8020E: Error running registerNode on non supported environment.
ADMU8021I: Backing up the original config directory of the profile to be deregistered.
ADMU8022E: An error occurred when calling registerWithAdminAgent command; rolling back to original configuration.
ADMU8023E: An error occurred when invoking initializeProfile operation on AdminAgent mbean; rolling back to original configuration.
ADMU8024E: An error occurred when invoking startProfile operation on AdminAgent mbean; rolling back to original configuration.
ADMU8025E: An error occurred when calling deregisterWithAdminAgent command; rolling back to original configuration.
ADMU8026E: An error occurred when invoking stopProfile operation on AdminAgent mbean; rolling back to original configuration.
ADMU8027E: An error occurred when invoking destroyProfile operation on AdminAgent mbean; rolling back to original configuration.
ADMU8028E: An error occurred during node deregistration; rolling back to original configuration.
ADMU8029E: Error running deregisterNode on non supported environment.
ADMU8030E: Failed finding backup files so unregister node cannot continue.
ADMU8031E: Failed getting AdminAgent mbean, registerNode cannot continue.
ADMU8032E: Failed getting AdminAgent mbean, deregisterNode cannot continue.
ADMU8033E: Error trying to register a node that has been registered already.
ADMU8034E: The profile path {0} does not exist locally on the Administrative Agent system.
ADMU8035E: Ensure that the AdminAgent is running on the specified port.
ADMU8036I: Registering the node with an AdminAgent.
ADMU8037I: Backing up the original wsadmin.properties file of the node to be registered.
ADMU8038I: Deregistering the node with an adminagent.
ADMU8039E: Required option type is expected if you try to register a WebSphere plug-in type.
ADMU8040I: The administrative agent is initializing the administrative subsystem for the registered node.
ADMU8041I: The administrative agent is starting the administrative subsystem for the registered node.
ADMU8042I: Node has been successfully registered.
ADMU8043I: The administrative agent is stopping the administrative subsystem for the deregistered node.
ADMU8044I: The administrative agent is destroying the administrative subsystem for the deregistered node.
ADMU8045I: Node has been successfully deregistered.
ADMU8046E: The administrative agent port number specified for {0} connector is invalid, registerNode cannot continue.
ADMU8047E: An error occurred when invoking listProfiles operation on AdminAgent mbean; rolling back to original configuration.
ADMU8048E: Error trying to unregister node that has not been registered.
ADMU8049E: An error occurred when adminagent tried to exchange signers with the node.
ADMU8050E: An error occurred during signers removal.
ADMU8051I: Removed signers successfully.
ADMU8052I: Removing signers exchanged during node registration.
ADMU8053I: Successfully connected to AdminAgent Server: {0}:{1}
ADMU8054E: Failed to create managed node with name {0}.
ADMU8055E: An error occurred when trying to create the managed node.
ADMU8056E: Error removing the managed node from an adminagent.
ADMU8057E: An error occurred during node deregistration; rolling back to original configuration.
ADMU8058E: An error occurred when trying to set the admin preferred authorization mechanism to {0}
ADMU8059E: An error occurred when trying to get the managed node name.
ADMU8060E: An error occurred when trying to get the profile key.
ADMU8061E: If you specify the user name, you must also specify the password.
ADMU8062E: If you specify the password, you must also specify the user name.
ADMU8063E: If you specify the nodeusername, you must also specify the nodepassword.
ADMU8064E: If you specify the nodepassword, you must also specify the nodeusername.
ADMU8065E: You did not specify all required parameters. Required parameters you did not specify are {0}
ADMU8066E: You specified a non supported parameter {0}
ADMU8067E: Parameter {0} was specified twice.
ADMU8068E: If you specify the port, you must also specify the conntype.
ADMU8069E: If you specify the conntype, you must also specify the port.
ADMU8070I: All Application Server nodes have been successfully registered.
ADMU8071I: All Application Server nodes have been successfully deregistered.
ADMU8072E: Application Server nodes with profilePath {0} failed to register with the administrative agent.
ADMU8073E: Application Server nodes with profilePath {0} failed to deregister from the administrative agent.
ADMU8074E: The administrative agent port number specified for {0} connector is invalid, deregisterNode cannot continue.
ADMU8075W: Application {0} is not imported because conflicting object {1} already exists.
ADMU8076E: The node was not removed from the cell configuration because the node has a different product version than the local node
ADMU9990I:
ADMU9991E: Unknown option: {0}
ADMU9992E: Parameter required for option: {0}
ADMU9993E: Invalid parameter {0}
ADMU9994W: Options username or password is not needed to start a server and it will be ignored.