ADMU0514E=ADMU0514E: Unsupported JMX Connector: {0} A Java Management Extensions (JMX) connector type was requested that is not supported. Request a connector type that is supported. ADMU3200I=ADMU3200I: Server launched. Waiting for initialization status. The server process launched. The product is waiting for initialization status. No user action is required. ADMU0124I=ADMU0124I: The system clock of the new node ({0}) is not synchronized with that of the deployment manager ({1}). To add a node, the system clock of the node to be added must be fairly close to that of the deployment manager. Change the new node system clock to be the same as that of the deployment manager. ADMU7770I=ADMU7770I: Generic Server: {0} STARTED successfully. The generic server started successfully. No user action is required. ADMU3019E=ADMU3019E: Exception waiting for server stop {0} An exception was issued while the server was in the process of stopping. Examine the log files for the server to see why the stop function issued an exception. ADMU0015I=ADMU0015I: Backing up the original cell repository. The original configuration files are saved before the utility program changes them. No user action is required. ADMU8044I=ADMU8044I: The administrative agent is destroying the administrative subsystem for the deregistered node. This message is for informational purposes only. No user action is required. ADMU1502E=ADMU1502E: If you specify "-serviceUserName" or "-servicePassword" then you must specify both of these as well as "-registerService". You must specify "-serviceUserName" and "-servicePassword" together. You must also specify "-registerService" Obtain values for the above and resubmit request. ADMU0123E=ADMU0123E: Could not find text for message ID {0}. The specified message ID could not be found in the message file. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ADMU2029E=ADMU2029E: Exception {0} caught in creating EAR Object from {1} The enterprise archive (EAR) file could not be obtained from the specified location. The EAR file will not be expanded to the specified destination. Run the EARExpander tool to expand the EAR file to its appropriate locations. ADMU1501W=ADMU1501W: Exception caught while de-registering node agent as Windows service - please check addNode.log for details There was a problem found while de-registering node agent as Windows service. Check addNode.log for additional information. ADMU0014I=ADMU0014I: Adding node {0} configuration to cell: {1} Configuration files from the node are being uploaded to the cell repository that the deployment manager manages. No user action is required. ADMU0512I=ADMU0512I: Server {0} cannot be reached. It appears to be stopped. The server cannot be reached and seems to be stopped. No user action is required. ADMU8043I=ADMU8043I: The administrative agent is stopping the administrative subsystem for the deregistered node. This message is for informational purposes only. No user action is required. ADMU0122E=ADMU0122E: Exception {0} copying application files from {1} to {2}. Unexpected exception in file copy. Manually copy files. ADMU2028E=ADMU2028E: Exception {0} caught in expanding ear at {1} to {2} The enterprise archive (EAR) file could not be expanded to the destination. Run the EARExpander tool to expand the EAR file to its appropriate locations. ADMU1500W=ADMU1500W: Exception caught while registering node agent as Windows service - please check addNode.log for details The node agent could not be registered as a Windows service. Check the addNode.log file for additional information. ADMU0403E=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. 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. 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. ADMU0013I=ADMU0013I: A document already exists at the cell level: {0} The specified document exists at the cell level. No user action is required. ADMU8042I=ADMU8042I: Node has been successfully registered. The node has been registered with an adminagent. No user action is required. ADMU3060E=ADMU3060E: Timed out waiting for server shutdown. The amount of time taken for server shutdown exceeded the -timeout value requested. Use a larger value for the -timeout option or perform problem determination on the server to investigate possible errors. ADMU0121E=ADMU0121E: Unexpected exception {0} while checking existence of {1} in the target repository. {1} will not be uploaded. 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. After the addNode command finishes, install the application using either the administrative console or the wsadmin tool. ADMU7009E=ADMU7009E: There is an unexpected exception in expandArchive. The archive file {0} will not be extracted in following paths {1}. Exception: {2} The disk might be full, or the directory might not have write permission. Use EARExpander command to extract the archive file. ADMU2027E=ADMU2027E: Exception {0} caught in creating varmap for scope {1}, {2}, {3} The variable map could not be created. Applications might not be restored or deleted from their binary Web address. Run the EARExpander tool to expand the application enterprise archive (EAR) files to their appropriate locations. ADMU0402I=ADMU0402I: The configuration for node {0} has been synchronized with Deployment Manager {1}: {2} The specified node was successfully synchronized with the deployment manager. No user action is required. ADMU0012I=ADMU0012I: Creating Node Agent configuration for node: {0} The addNode command created the configuration files for the node agent for the new node. No user action is required. ADMU0510I=ADMU0510I: Server {0} is now {1} The state of the specified server is given. No user action is required. ADMU8041I=ADMU8041I: The administrative agent is starting the administrative subsystem for the registered node. This message is for informational purposes only. No user action is required. ADMU4113E=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. The tool could not contact the remote server because of a credentials problem. 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. ADMU0120I=ADMU0120I: {0} will not be uploaded since it already exists in the target repository. File already exists. No user action is required. ADMU7008E=ADMU7008E: Unexpected exception in expandEar. The ear file {0} will not be extracted in following paths {1}. Exception: {2} The disk might be full, or the directory might not have write permission. Use EARExpander command to extract the enterprise archive (EAR) file. ADMU2026E=ADMU2026E: Node {0} is not incorporated into any cell. An attempt was made to remove a node that has never been added in the first place. Run the addNode command before attempting to run the removeNode command. ADMU0401I=ADMU0401I: Begin syncNode operation for node {0} with Deployment Manager {1}: {2} The specified node is being synchronized with the deployment manager. No user action is required. ADMU2025W=ADMU2025W: Removal of node {0} is complete, but there were errors. This node was removed from the cell, but problems occurred during the removal. Examine the previous errors to determine what occurred. You might need to run the cleanupNode utility to remove this node from the deployment manager configuration. ADMU0011E=ADMU0011E: Error creating configuration in the cell repository {0} Configuration files for the new node could not be uploaded to the deployment manager for creation in the cell repository. Ensure that the deployment manager is running and that the FileTransfer application is running in the deployment manager. Record the exception information from this message for further problem determination. If the Java(TM) virtual machine (JVM) OutOfMemoryError error is in the stack trace in the addNode.log file, the heap size for the addNode command or the deployment manager might need to be increased. For the addNode command, add the -Xmx(size) parameter to the addNode command. ADMU4112I=ADMU4112I: Error details may be seen in the file: {0} This is an informational message indicating where to look for further information. Look in the file for more information. ADMU8040I=ADMU8040I: The administrative agent is initializing the administrative subsystem for the registered node. This message is for informational purposes only. No user action is required. ADMU3014W=ADMU3014W: Server recovery complete, problems occurred during recovery. Server log files should contain failure information. The server had problems during recovery and has stopped. Examine the log files to see what failure messages were recorded there. ADMU8076E=ADMU8076E: The node was not removed from the cell configuration because the node has a different product version than the local node The difference in node product versions likely resulted from attempting to remove an old node that was migrated to a higher product level, while the migrated deployment manager is running. Stop the migrated deployment manager and try removing the node again ADMU8075W=ADMU8075W: Application {0} is not imported because conflicting object {1} already exists. Cannot import application because business-level application or composition unit already exists. No user action is required. ADMU7006W=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. This backup file was created from a system with a different cell name. After the restore operation has completed, correct any resulting problems and confirm proper system function before starting production applications. ADMU0010E=ADMU0010E: Error obtaining repository client {0} A client connection for the Cell configuration repository could not be obtained. Record the exception information from this message for further problem determination. ADMU4111E=ADMU4111E: Program exiting with error: {0} An error occurred during program execution. Perform problem determination to investigate possible causes. ADMU2024I=ADMU2024I: Removal of node {0} is complete. The specified node has been successfully removed. No user action is required. ADMU3013I=ADMU3013I: Server recovery complete. Server stopped. The server has completed recovery and has stopped. No user action is required. ADMU8074E=ADMU8074E: The administrative agent port number specified for {0} connector is invalid, deregisterNode cannot continue. Failed to deregister the node because the port number specified is invalid. Check your administrative agent serverindex.xml and find the correct port number of the connector. ADMU3402E=ADMU3402E: Server name not specified; must supply the name of a server. This tool requires that a server name be provided. Specify a server name. ADMU7005E=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. This backup file was created from a system with a different cell name. 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. ADMU2023E=ADMU2023E: Exception removing servers from clusters {0} A problem occurred attempting to remove the servers from the clusters. Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. ADMU3012E=ADMU3012E: Exception attempting to get free port for status socket {0} A free port could not be allocated to communicate server status. Examine the log file for the utility to perform further problem determination. Attempt to run the utility again. ADMU0044E=ADMU0044E: It is not valid to run syncNode on the same node as the Deployment Manager: {0} The syncNode program only applies to app server nodes, not the ND deployment manager node itself. Do not attempt to run syncNode on the Deployment Manager node itself. ADMU8073E=ADMU8073E: Application Server nodes with profilePath {0} failed to deregister from the administrative agent. One or more Application Server nodes failed to deregister. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU3401I=ADMU3401I: Server stop request issued. No stop status requested. A stop server request was issued without a stop status request. No user action is required. ADMU2022I=ADMU2022I: Removing cluster member {0} from cluster {1}. The specified cluster member is being removed from the specified cluster. No user action is required. ADMU7004E=ADMU7004E: Unexpected exception while building cache entry for {0} and {1}. Exception is: {2}. All the related binaries may not be deleted/updated. The exception message may detail probable cause. If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear. ADMU3011E=ADMU3011E: Server launched but failed initialization. Server logs, startServer.log, and other log files under {0} should contain failure information. The server process failed to start. Examine the log files to see what failure messages were recorded there. ADMU8029E=ADMU8029E: Error running deregisterNode on non supported environment. An attempt was made, using the deregisterNode operation, to remove a profile from the registry in an unsupported environment. A node can be deregistered only when it runs on the same machine as the administrative agent. The administrative agent is the AdminAgent MBean. Remove a node from the registry when the node is located on the same machine as the administrative agent. ADMU4000I=ADMU4000I: Server {0} stop completed. The stopServer command completed successfully. No user action is required. ADMU0043E=ADMU0043E: Error trying to federate a node that is still registered to an AdminAgent. The node you are trying to federate still registered to an AdminAgent. You need to unregister the node from an AdminAgent before being able to federate to DeploymentManager. ADMU8072E=ADMU8072E: Application Server nodes with profilePath {0} failed to register with the administrative agent. One or more Application Server nodes failed to register. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU3400I=ADMU3400I: Server launched. No initialization status. Process id is: {0} The -nowait option was used for the startServer command, so no initialization status is available for the launched process. No user action is required. ADMU2021I=ADMU2021I: Removing all servers on this node from all clusters in the cell. This is an informational message marking the progress of the program. No user action is required. ADMU8028E=ADMU8028E: An error occurred during node deregistration; rolling back to original configuration. The node could not be removed from the registry. The configuration is rolled back to the original configuration. Review the associated messages in deregisterNode.log to determine the specific problem and retry the deregisterNode command. ADMU0042E=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. The lock used to prevent concurrent addNode and removeNode operations could not be reset. 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. ADMU8071I=ADMU8071I: All Application Server nodes have been successfully deregistered. Deregistration of all specified nodes successfully completed. No user action is required. ADMU2020E=ADMU2020E: Exception removing applications {0} A problem occurred attempting to remove the applications from this node. Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. ADMU7709E=ADMU7709E: Unexpected exception while processing server: {0}; exception = {1} An unexpected exception has been detected. Verify that the product installation is correct. ADMU8027E=ADMU8027E: An error occurred when invoking destroyProfile operation on AdminAgent mbean; rolling back to original configuration. The profile could not be deleted. The destroyProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU0041E=ADMU0041E: Another addNode or removeNode operation is currently in progress. Please attempt this operation later. Concurrent addNode and removeNode operations are not allowed. Wait until the first addNode or removeNode operation completes, and then retry this operation. ADMU8070I=ADMU8070I: All Application Server nodes have been successfully registered. Registration of all specified nodes successfully completed. No user action is required. ADMU6012I=ADMU6012I: Exception in run {0} NONE No user action is required. ADMU7708E=ADMU7708E: Failed while trying to determine the Windows Service log file name for server: {0}; probable error executing WASService.exe: {1} The log file for the Windows service associated with this server could not be found. Verify that the product installation is correct. ADMU8026E=ADMU8026E: An error occurred when invoking stopProfile operation on AdminAgent mbean; rolling back to original configuration. The profile could not be stopped. The stopProfile operation on AdminAgent MBean failed. The configuration is rolled back to the original configuration. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU0040E=ADMU0040E: Exception on MBean invocation {0} {1} {2} An MBean call failed. Record and save the exception information from this message for further problem determination. ADMU7707E=ADMU7707E: Failed while trying to determine the Windows Service name for server: {0}; probable error executing WASService.exe: {1} The Windows service associated with this server could not be found. Verify that a Windows service associated with the specified server exists. ADMU8025E=ADMU8025E: An error occurred when calling deregisterWithAdminAgent command; rolling back to original configuration. Failed running deregisterWithAdminAgent command. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU7750E=ADMU7750E: The {0} command has failed because another process has temporarily requested exclusive access to {1}. Please wait a few minutes and try again. Another command is running and might conflict with this one. Wait a few minutes and try the command again. ADMU0183E=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. The node agent short name already exists in the distributed cell to which this node is being added. Ensure that the node agent short name is unique across all the nodes in the distributed cell before running the addNode command. Make the node agent short name unique in the deployment manager cell. Then run the addNode command. ADMU0529E=ADMU0529E: Unexpected exception {0} thrown while restoring application binaries from the base configuration. 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. Use the EARExpander command to expand the application enterprise archive (EAR) file to the location specified on the binariesURL attribute. The attribute is in the corresponding deployment.xml configuration file. ADMU7706E=ADMU7706E: Failed while trying to deregister the Windows Service {0}; probable error executing WASService.exe: {1} The Windows service associated with this server could not be removed from the registry. Examine the error message and make correction accordingly. ADMU8024E=ADMU8024E: An error occurred when invoking startProfile operation on AdminAgent mbean; rolling back to original configuration. The profile failed to start. The startProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. Review the associated error in registerProfile.log or turn on trace to diagnose the problem. ADMU0211I=ADMU0211I: Error details may be seen in the file: {0} This is an informational message indicating that additional information is available in the log file. Look in the file for additional information. ADMU0182E=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. The node short name already exists in the distributed cell to which this node is being added. Ensure that the node short name is unique across all the nodes in the distributed cell before running the addNode command. Make the node short name unique in the deployment manager cell. Then run the addNode command. ADMU0528I=ADMU0528I: Details of Queue Manager deletion may be seen in the file: {0} You can see the details of the deletion of the queue manager in the specified file. Look in the file for more information. ADMU7705E=ADMU7705E: Failed while trying to stop the Windows Service associated with server: {0}; probable error executing WASService.exe: {1} The Windows Service associated with this server failed to stop. Check return code and correct the problem then retry the operation. ADMU8023E=ADMU8023E: An error occurred when invoking initializeProfile operation on AdminAgent mbean; rolling back to original configuration. The profile failed to initialize. The initializeProfile operation on the AdminAgent MBean failed. The configuration is rolled back to the original configuration. Review the associated error in registerProfile.log or turn on trace to diagnose the problem. ADMU8059E=ADMU8059E: An error occurred when trying to get the managed node name. An error occurred when trying to get the managed node name. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU0181E=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. The cluster transition name already exists in the distributed cell to which this node is being added. Ensure that the cluster transition name is unique across all the servers in the distributed cell before running the addNode command. Make the cluster transition name unique in the deployment manager cell. Then run the addNode command. ADMU0527I=ADMU0527I: WebSphere Embedded Messaging support not installed; Queue Manager not deleted from server {0} Embedded messaging support is not installed. The queue manager cannot be deleted from the specified server. No user action is required. ADMU0029E=ADMU0029E: An error occurred during node removal: {0} The node could not be removed. Examine the exception to determine the specific problem and take corrective action. ADMU7704E=ADMU7704E: Failed while trying to start the Windows Service associated with server: {0}; probable error executing WASService.exe: {1} The Windows service associated with this server failed to start. Check the return code and correct the problem. Then retry the operation. ADMU8022E=ADMU8022E: An error occurred when calling registerWithAdminAgent command; rolling back to original configuration. Failed running registerWithAdminAgent command of the profile to be registered. Review the associated error in registerNode.log or turn on trace to diagnose the problem and look for trace information in the trace log. ADMU3040E=ADMU3040E: Timed out waiting for server initialization: {0} seconds The server initialization process has exceeded the timeout limit. Perform problem determination on the server to check for possible errors. ADMU8058E=ADMU8058E: An error occurred when trying to set the admin preferred authorization mechanism to {0} An error occurred when trying to set the admin preferred authorization mechanism Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU0180E=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. The server short name already exists in the distributed cell to which this node is being added. Ensure that the short name is unique across all the servers in the distributed cell before running the addNode command. Make the server short name in the deployment manager cell unique. Then run the addNode command. ADMU0028I=ADMU0028I: Log generated. A log was generated. No user action is required. ADMU0526I=ADMU0526I: Deleting Queue Manager for node {0} on server {1} The queue manager is being deleted on the specified node and the specified server. No user action is required. ADMU7703I=ADMU7703I: The Windows Service {0} associated with {1} is now being deregistered. When a server is removed, the corresponding Windows service is removed from the registry. No user action is required. ADMU8021I=ADMU8021I: Backing up the original config directory of the profile to be deregistered. The original configuration files for the profile are being saved before they are removed from the registry. No user action is required. ADMU8057E=ADMU8057E: An error occurred during node deregistration; rolling back to original configuration. 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. Review the associated messages in the deregisterNode.log file to determine the specific problem. Retry the deregisterNode. ADMU0071E=ADMU0071E: Exception occurred during security authentication. An exception occurred during the password encryption/decryption. Verify the user name and password are correct and retry the operation. ADMU0525I=ADMU0525I: Details of Queue Manager creation may be seen in the file: {0} The details of the queue manager creation cannot be seen in the specified file. Look in the file for more information on the queue manager creation. ADMU7702I=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. When a server is registered to run as a Windows Service, the Windows Service is used to stop the server. No user action is required. ADMU0070W=ADMU0070W: Retrieving signer certificates from dmgr failed - this may cause node federation to fail. The signer certificates could not be retrieved from the deployment manager. The user name, password, or both might be incorrect. Verify that the user name and password are correct. Alternatively, use the retrieveSigners script to download the signer certificates from the deployment manager. ADMU0027E=ADMU0027E: An error occurred during federation {0}; rolling back to original configuration. 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. 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. ADMU8020E=ADMU8020E: Error running registerNode on non supported environment. The node could not be registered using the registerNode because no connection was made to the administrative agent during node registration. The administrative agent is the AdminAgent MBean. Ensure that a connection is made to the correct port of the administrative agent. ADMU8056E=ADMU8056E: Error removing the managed node from an adminagent. An error occurred during managed node removal from an adminagent. Review the associated error or turn on trace to diagnose the problem. ADMU0308I=ADMU0308I: The node {0} and associated applications were successfully added to the {1} cell. The specified node and its associated applications were successfully added to the specified cell. No user action is required. ADMU0026I=ADMU0026I: An error occurred during federation; rolling back to original configuration. 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. 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. ADMU5506I=ADMU5506I: {0} files successfully restored The specified number of files were successfully restored. No user action is required. ADMU0524I=ADMU0524I: WebSphere Embedded Messaging support not installed; Queue Manager not created Embedded messaging was not installed. The queue manager was not created. No user action is required. ADMU7701I=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. When a server is registered to run as a Windows Service, the Windows Service is used to start the server. No user action is required. ADMU8055E=ADMU8055E: An error occurred when trying to create the managed node. An error occurred when trying to create managed node. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU0307I=ADMU0307I: You might want to: This message suggests that you do the actions associated with the messages that immediately follow this message. No user action is required. ADMU2004E=ADMU2004E: An exception occurred An exception occurred. Record the exception data and perform further problem determination. ADMU3029I=ADMU3029I: Conflict detected on port {0} for endpoint {2} of the server {1} The port for the specified endpoint of this server is already in use by this or another server. Do not attempt to use a port that is already in use. ADMU3101I=ADMU3101I: Using explicit host and port {0}:{1} for server: {2} The specified hot and the specified port were used. No user action is required. ADMU4018E=ADMU4018E: "-script" option is not supported on zOS platform. An error occurred when the program ran. Remove the "-script" option and rerun the command. ADMU5505I=ADMU5505I: Restoring file {0} to location {1} The specified file is being restored to the specified location. No user action is required. ADMU0523I=ADMU0523I: Creating Queue Manager for node {0} on server {1} The queue manager is being created for the specified node on the specified server. No user action is required. ADMU0025E=ADMU0025E: Given host and port do not point to a Deployment Manager. The connected process does not have a DeploymentManager MBean. The most common cause is that the specified host or port is not for the deployment manager. Verify that the host and port passed to the tool are correct. ADMU8054E=ADMU8054E: Failed to create managed node with name {0}. The node name being used to create a new managed node already exist. The node name being used to create a new managed node already exist. Specify different name. ADMU0306I=ADMU0306I: Note: This message indicates that at least one message immediately follows this message and that you should read any messages that immediately follow this one. No user action is required. ADMU2003E=ADMU2003E: No setupCmdLine file found to modify: {0} The file was not located. Check that a setupCmdLine file exists in the installation. ADMU3028I=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} A port required by this server is already in use by this or another server. Do not attempt use a port that is already in use. ADMU3100I=ADMU3100I: Reading configuration for server: {0} The server configuration is being read. No user action is required. ADMU0024I=ADMU0024I: Deleting the old backup directory. The original configuration files are saved before they the utility program changes them. No user action is required. ADMU5504I=ADMU5504I: Restore location successfully renamed The specified location has been renamed. No user action is required. ADMU8053I=ADMU8053I: Successfully connected to AdminAgent Server: {0}:{1} This is an informational message indicating that the program has established communications with the AdminAgent. No user action is required. ADMU0522E=ADMU0522E: No server by this name in the configuration: {0} No server was located in the configuration repository by the specified name. Check the spelling of the server name. Check the integrity of the configuration files. ADMU0305I=ADMU0305I: Install applications onto the {0} cell using wsadmin $AdminApp or the Administrative Console. None No user action is required. ADMU8009I=ADMU8009I: Begin deregistration of Application Server with path {0}. The node will be deregistered with an adminagent. No user action is required. ADMU3027E=ADMU3027E: An instance of the server may already be running: {0} An attempt has been made to start a server that is already running. Do not attempt to start a server that is already running. ADMU2037W=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. The host names for the deployment manager and for the node being federated do not match. This mismatch might be an indication of an unsupported configuration. The local operating system registry will not work across multiple machines, except in special cases. These special cases include having a cell reside exclusively on the z/OS operating system, or be part of a Microsoft Windows domain controller. 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. ADMU0059I=ADMU0059I: Adding node {0} to node group {1}. The configuration files for the node are being uploaded to the cell repository that the deployment manager manages because the specified node is being added to the specified node group. No user action is required. ADMU0023E=ADMU0023E: Exception waiting for server initialization {0} An IOException was issued while the program was waiting for input on the server status port. 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. ADMU8052I=ADMU8052I: Removing signers exchanged during node registration. Removing security signers that were exchanged during node registration. No user action is required. ADMU5503E=ADMU5503E: The restore location could not be renamed - another process may be using this subdirectory The location of the restored configuration could not be renamed. Use the -location option on the restoreConfig command to specify a location which does not exist, or which can be renamed. ADMU0521E=ADMU0521E: No node named "{0}" is found in this cell. No node was located in the configuration repository with the specified name. Check the spelling of the node name. Check the integrity of the configuration files. ADMU2001I=ADMU2001I: Begin removal of node: {0} Removal of the node has started. No user action is required. ADMU0304I=ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell. 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. No user action is required. ADMU8008I=ADMU8008I: Restoring all original pre-registered files of the profile after deregistration. The original configuration files are being restored after the profile was removed from the registry. No user action is required. ADMU0022I=ADMU0022I: Node Agent launched. Waiting for initialization status. The node agent launched and is waiting for initialization status. No user action is required. ADMU0058I=ADMU0058I: Removing node {0} from all node groups. The configuration files for the node are being uploaded to the cell repository that the deployment manager manages because the specified node is being removed from all the node groups. No user action is required. ADMU5502I=ADMU5502I: The directory {0} already exists; renaming to {1} The specified directory for the restored configuration already exists and is being renamed to the specified directory. No user action is required. ADMU8051I=ADMU8051I: Removed signers successfully. Removed security signers that were exchanged during node registration successfully. No user action is required. ADMU4123E=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. A connection could not be made to the deployment manager. Ensure that the deployment manager is running. Ensure that the proper host name and port are used when attempting to connect to the process. Also ensure that the security configuration in ssl.client.props on the node is compatible with the Deployment Manager. ADMU2036I=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. The node can be removed manually if error messages or warning messages resulted from running the removeNode command. Use the manageprofiles command to delete the profile for this node. Run the cleanupNode command on the deployment manager. ADMU0303I=ADMU0303I: Update the configuration on the {0} Deployment Manager with values from the old cell-level documents. The configuration on the specified deployment manager was updated. No user action is required. ADMU0057W=ADMU0057W: {0} WARNING(S) occurred while removing node {1} from all node groups. {2} One or more warnings occurred while removing the node from all the node groups. No user action is required.. ADMU8007I=ADMU8007I: Exchanged signers successfully. Exchanged security signers successfully. No user action is required. ADMU2035W=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. The removeNode tool could not remove the node because the node was created during cell profile creation. Use the manageprofiles command to delete the node. Run the cleanupNode command on the deployment manager. ADMU0021E=ADMU0021E: Error occurred stopping server {0} An attempt was made to stop the specified server, but the server did not stop. Examine the log files for the server to see why the server is not stopped. ADMU5501E=ADMU5501E: The backup file specified {0} does not exist. The file specified containing the backed up configuration documents cannot be found. Verify that the file given to the restoreConfig command exists and can be read. ADMU4122E=ADMU4122E: The specified server may not be running, or no appropriate username and password are provided if the specified server runs in secure mode A connection to the server could not be established. 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. ADMU8050E=ADMU8050E: An error occurred during signers removal. An error occurred when adminagent tried to remove signers that were exchanged during node registration. Review the associated error in deregsiterNode.log or turn on trace to diagnose the problem. ADMU0302I=ADMU0302I: Any cell-level documents from the standalone {0} configuration have not been migrated to the new cell. None No user action is required. ADMU0056W=ADMU0056W: {0} WARNING(S) occurred while adding node {1} to node group {2}. {3} One or more warnings occurred while adding the node to the node group. No user action is required.. ADMU8006E=ADMU8006E: An error occurred when calling deregisterNode command. The profile could not be removed from the registry. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU3522E=ADMU3522E: No server by this name in the configuration: {0} The specified server name cannot be located within the configuration for this node. Check that the specified name is spelled correctly and that a directory by that name does exist under the servers directory in the configuration. ADMU5002I=ADMU5002I: {0} files successfully backed up The specified number of files were backed up. No user action is required. ADMU0020I=ADMU0020I: Reading configuration for Node Agent process: {0} The configuration for the specified node agent process is being read. No user action is required. ADMU2034I=ADMU2034I: Use wsadmin or the Administrative Console to uninstall any such buses from the Deployment Manager. You can use the wsadmin tool or the administrative console to uninstall any buses from the deployment manager. No user action is required. ADMU0055W=ADMU0055W: {0} WARNING(S) occurred while converting node group {2} to sysplex node group for node {1}. {3} One or more warnings occurred while converting the node group to a sysplex node group. No user action is required.. ADMU0060W is issued for each warning message encountered. ADMU8005I=ADMU8005I: Admin preferred authorization mechanism is set to {0}. Security admin preferred authorization mechanism is set to RSAToken. No user action is required. ADMU5001I=ADMU5001I: Backing up config directory {0} to file {1} The specified configuration directory is being backed up to the specified file. No user action is required. ADMU2033I=ADMU2033I: Any buses that were uploaded to the {0} cell configuration during addNode using the -includebuses option are not uninstalled by removeNode. 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. No user action is required. ADMU0300I=ADMU0300I: The node {0} was successfully added to the {1} cell. The specified node was successfully added to the specified cell. No user action is required. ADMU0509I=ADMU0509I: The {0} "{1}" cannot be reached. It appears to be stopped. The server cannot be reached and seems to be stopped. No user action is required. ADMU0054W=ADMU0054W: {0} WARNING(S) occurred while checking if node {1} can join node group {2}. {3} One or more warnings occurred while checking whether the node can join the node group. No user action is required.. ADMU8004I=ADMU8004I: Backing up the original config directory of the node to be registered. The original configuration files are being saved before the utility program changes them. No user action is required. ADMU0119E=ADMU0119E: Unexpected exception {0} in rolling back application binaries. Expansion of the application enterprise archive (EAR) files to appropriate locations failed because the addNode command failed. 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. ADMU2032I=ADMU2032I: Use wsadmin or the Administrative Console to uninstall any such applications from the Deployment Manager. You can use the wsadmin tool or the administrative console to uninstall applications from the deployment manager. No user action is required. ADMU0508I=ADMU0508I: The {0} "{1}" is {2} The state of the specified server is given. No user action is required. ADMU8003E=ADMU8003E: An error occurred when calling registerNode command; rolling back to original configuration. The registerNode command failed. The configuration is being rolled back to the original configuration. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU8039E=ADMU8039E: Required option type is expected if you try to register a WebSphere plug-in type. The node could not be registered because the node is not a stand-alone node. Specify the node type and the plug-in type to register the plug-in type. ADMU0118E=ADMU0118E: The log file cannot be written to location {0}; please specify a different location with -logfile The log file could not be written to the specified location. Permissions or a security issue might be a cause of the problem. Use the -logfile option to specify a new location for the logfile. ADMU0053E=ADMU0053E: Exception occurred while removing node {1} from all node groups. {0} Removal of the specified node from all node groups failed. Record the exception information from this message and perform problem determination using that exception data. ADMU0089E=ADMU0089E: Exception caught during rollback of application binaries {0} The rollback of the application binaries failed. Consult the addNode.log file for additional information. ADMU2031I=ADMU2031I: Any applications that were uploaded to the {0} cell configuration during addNode using the -includeapps option are not uninstalled by removeNode. 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. No user action is required. ADMU0009I=ADMU0009I: Successfully connected to Deployment Manager Server: {0}:{1} This is an informational message indicating that the program has established communications with the Deployment Manager. No user action is required. ADMU0507I=ADMU0507I: No servers found in configuration under: {0} The servers directory is empty in the configuration. Check the integrity of the configuration files. ADMU8002I=ADMU8002I: Exchanging signers between adminagent and node with path {0}. Exchanging signers between adminagent and node to be registered. No user action is required. ADMU8038I=ADMU8038I: Deregistering the node with an adminagent. The node will be deregistered with an adminagent. No user action is required. ADMU9994W=ADMU9994W: Options username or password is not needed to start a server and it will be ignored. The given option is not needed to start a server and it is ignored. No user action is required. ADMU0117E=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. 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. Install the application on the deployment manager if it is to be used in servers for this cell. ADMU0052E=ADMU0052E: Exception occurred while adding node {1} to node group {2}. {0} The specified node could not be added to the specified node group. Record the exception information from this message and perform problem determination using that exception data. ADMU0088E=ADMU0088E: No Server MBean named {0} in this process {1}:{2} The server name does not match the process attributes. Check that the name is spelled correctly. ADMU0506I=ADMU0506I: Server name: {0} The server name is displayed. No user action is required. ADMU2030E=ADMU2030E: Exception {0} caught in getting binariesURL from {1} The specified deployment.xml file could not be loaded to obtain the value of the binariesURL attribute. The enterprise archive (EAR) file will not be expanded or deleted from that location. 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. ADMU0008E=ADMU0008E: Error obtaining MBean by name {0}: {1} A query to locate an MBean failed. Record the exception information in this message for further investigation. ADMU8037I=ADMU8037I: Backing up the original wsadmin.properties file of the node to be registered. The wsadmin.properties file is being saved before it is changed. No user action is required. ADMU8001E=ADMU8001E: An error occurred during node registration; rolling back to original configuration. 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. Review the associated messages in the registerNode.log file to determine the specific problem. Retry the registerNode command. ADMU3055E=ADMU3055E: Error obtaining MBean by name {0}: {1} A query to locate an MBean failed. Check that the server process is still running. Examine the log files for the program to perform further problem determination. ADMU0116I=ADMU0116I: Tool information is being logged in file {0} Tool information is being logged to the specified file. No user action is required. ADMU3300I=ADMU3300I: Launch script for server created: {0} The server launch script has been successfully created. No user action is required. ADMU0051E=ADMU0051E: Exception occurred while converting node group {2} to sysplex node group for node {1}. {0} The specified node group could not be converted to a sysplex node group for the specified node. Record the exception information from this message and perform problem determination using that exception data. ADMU9993E=ADMU9993E: Invalid parameter {0} The parameter that is provided is not valid for the given option. Provide a different parameter. ADMU0505I=ADMU0505I: Servers found in configuration: This is an informational message printed before a list of servers. No user action is required. ADMU0007E=ADMU0007E: Error while copying {0} 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. Check the available disk space on the system. Check that the file does exist and is readable. ADMU8036I=ADMU8036I: Registering the node with an AdminAgent. The node is being registered with an adminagent. No user action is required. ADMU3054E=ADMU3054E: No Server MBean named {0} in this process {1}:{2} The MBean of type Server appears to be missing from the process. Check that the named server is actually running on the host and port specified. ADMU0115I=ADMU0115I: Trace mode is on. Trace has been enabled. No user action is required. ADMU0050E=ADMU0050E: Exception encountered while checking if node {1} can join node group {2}. {0} Whether the specified node could join the specified node group could not be determined. Record the exception information from this message and perform problem determination using that exception data. ADMU9992E=ADMU9992E: Parameter required for option: {0} A parameter is required for the displayed option, but one was not provided. Provide a parameter for this option. ADMU0006E=ADMU0006E: Exception creating Deployment Manager connection: {0} The client utility program was not able to establish a connection to the Deployment Manager using the information provided. 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. ADMU8035E=ADMU8035E: Ensure that the AdminAgent is running on the specified port. A connection cannot be made to the administrative agent. The administrative agent is the AdminAgent MBean. Ensure that the administrative agent is running. Ensure that the proper port is used when attempting to connect to the process. ADMU0114E=ADMU0114E: Exception launching Node Agent process: {0} The node agent process for the new node failed to launch. Record and save the exception information from this message and perform further problem determination to investigate why the process failed to launch. ADMU0222I=ADMU0222I: Exception accessing the plugin-cfg.xml file. The code that attempts to upload the plugin-cfg.xml configuration file failed and issued an exception. Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be accessed. ADMU3009E=ADMU3009E: Exception waiting for server initialization {0} An exception occurred while the program was listening to the status socket for the server. The server process failed to start. Record and save the exception information in this message for further problem determination. ADMU1211I=ADMU1211I: To obtain a full trace of the failure, use the -trace option. You can use the trace option to gather additional information. Consider using the -trace option on the command line. ADMU9991E=ADMU9991E: Unknown option: {0} The option specified is not a known option. Examine the usage statement and specify a known option. ADMU0503I=ADMU0503I: Retrieving server status for all servers The server status is being retrieved for all servers. No user action is required. ADMU0005E=ADMU0005E: Error synchronizing repositories {0} 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. Examine the log files for additional problem determination information. ADMU8034E=ADMU8034E: The profile path {0} does not exist locally on the Administrative Agent system. Make sure the profile path you specify is correct and the profile path exists locally on the Administrative Agent system. Review the associated error to diagnose the problem. ADMU2019I=ADMU2019I: Removing installed applications from node {0}. The installed applications are being removed from the specified node. No user action is required. ADMU0113E=ADMU0113E: Program exiting with error: {0}, resulting from: {1} The program did not finish because of the specified error. Record the exception information from this message and perform problem determination using that exception data. ADMU0004E=ADMU0004E: Exception attempting to get result from configuration synchronization {0} An exception occurred during configuration synchronization while waiting for an asynchronous operation on the Deployment Manager. Record the exception information from this message for further investigation. ADMU8033E=ADMU8033E: Error trying to register a node that has been registered already. The node could not be registered because it has already been registered. Ensure that the node has not been previously registered before attempting to register it. ADMU8069E=ADMU8069E: If you specify the conntype, you must also specify the port. You must specify port option if you specified conntype option. Review the associated error to diagnose the problem. ADMU2018I=ADMU2018I: Node {0} has been removed from the Deployment Manager configuration. The specified node has been removed from the deployment manager configuration. No user action is required. ADMU0112E=ADMU0112E: Exception writing serverindex.xml file: {0} The code that attempts to update the serverindex.xml configuration file failed and issued an exception. Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be written to. ADMU3007E=ADMU3007E: Exception {0} Some general exception condition has been discovered. Combine this information with additional exception messages in order to perform additional problem determination. ADMU0003I=ADMU0003I: Node {0} has been successfully federated. This is an informational message indicating that the addNode program has successfully completed. No user action is required. ADMU7714I=ADMU7714I: WASService command for server {0} completed successfully. The WASService command completed successfully. No user action is required. ADMU0039E=ADMU0039E: There is already a node named {0} in the cell. You cannot run the addNode command to add a node to a cell which already contains a node of the same name. Do not attempt to run the addNode command to add a node to a cell already containing a node of the same name. ADMU0501E=ADMU0501E: Server name not specified; must supply the name of a server or -all for all servers. Neither the server name nor the -all argument was specified on the serverStatus command. Either specify the server name or the -all argument on the serverStatus command. ADMU8032E=ADMU8032E: Failed getting AdminAgent mbean, deregisterNode cannot continue. The AdminAgent MBean, which is the administrative agent, could not be gotten during the removal of the node from the registry. The node removal was attempted using the deregisterNode operation. Review the associated error in deregisterNode.log or turn on trace to diagnose the problem. ADMU8068E=ADMU8068E: If you specify the port, you must also specify the conntype. You must specify conntype option if you specified port option. Review the associated error to diagnose the problem. ADMU2017I=ADMU2017I: The local original configuration has been restored. The local configuration file has been restored. No user action is required. ADMU0111E=ADMU0111E: Program exiting with error: {0} The program did not finish because of the specified error. If the program is in the current working directory, verify that the directory is on the PATH or prefix the command invocation with the current working directory. Otherwise, record the exception information from this message and perform problem determination using that exception data. ADMU2096I=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. You can use the deleteSecurityDomain task with the force option to remove any unused security domains. You can also manually delete the security domains that are not required any more. No user action is required. ADMU0500I=ADMU0500I: Retrieving server status for {0} The status of the specified service is being retrieved. No user action is required. ADMU0002E=ADMU0002E: Exception attempting to process server {0}: {1} An exception occurred while attempting to attach to the server and obtain its state. Record the exception information from this message for further investigation. ADMU0038E=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. The deployment manager host name is not resolving correctly. Verify that the host name is configured properly at the deployment manager. For Linux systems, modify either the /etc/hosts file or the /etc/nsswitch.conf file to search the domain name server (DNS) before files. ADMU6009I=ADMU6009I: Processing complete. Processing complete. No user action is required. ADMU7713E=ADMU7713E: WASService command for server {0} failed. Unexpected exit code {1} from running {2}. The WASService command returned a non-zero exit code. Verify that the product installation and environment configuration are correct. Then, run the WASService command manually. ADMU8031E=ADMU8031E: Failed getting AdminAgent mbean, registerNode cannot continue. The node could not be registered because the AdminAgent MBean could not be gotten. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU8067E=ADMU8067E: Parameter {0} was specified twice. You cannot specify the same parameter more than once. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU4211I=ADMU4211I: To obtain a full trace of the failure, use the -trace option. The trace option can be used to obtain a full trace of the failure. No user action is required. ADMU2016E=ADMU2016E: Node {0} has not been removed from the Deployment Manager configuration. The node configuration files remain in the cell configuration repository. If the -force option is used, run the cleanupNode utility on the deployment manager to remove the configuration files for this node. ADMU0254I=ADMU0254I: Update the node configuration for {0} on the Deployment Manager. The particular node configuration is updated. No user action is required. ADMU0001I=ADMU0001I: Begin federation of node {0} with Deployment Manager at {1}:{2}. This is an informational message indicating that the addNode program has started. No user action is required. ADMU2095I=ADMU2095I: Any security domains that were uploaded to the {0} cell configuration during addNode are not removed by removeNode. If the addNode command uploaded any security domains to the specified cell, the removeNode command did not remove these security domains. No user action is required. ADMU0037E=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. The local node cannot look up the deployment manager host name that is specified in the deployment manager configuration. Do one of the following actions: - Add the deployment manager host name to the DNS. - Fully qualify the deployment manger host name in the deployment manager server index configuration. -Add the DNS of the domain to the TCP/IP configuration of the node. ADMU7712E=ADMU7712E: Failed while trying to determine the Windows Service status for service: {0}; probable error executing WASService.exe: {1} The status for the Windows service could not be obtained. Verify that the product installation is correct. ADMU8030E=ADMU8030E: Failed finding backup files so unregister node cannot continue. Before removing the node from the registry, the configuration must be backed up. However, the configuration files to back up could not be found. Ensure that the node was previously registered, and that the backup files exist in your environment. ADMU8066E=ADMU8066E: You specified a non supported parameter {0} You cannot use non supported parameters. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU2015I=ADMU2015I: This exception can be ignored by specifying -force. This is an informational message explaining that the -force option can be used to eliminate the message. No user action is required. ADMU2094W=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. The operation will continue even though the product extensions do not match. 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. ADMU0036E=ADMU0036E: The Deployment Manager cannot lookup by name host {0} at address {1} The local host can look up the deployment manager host, but the deployment manager cannot look up the new node. The situation can occur if the Dynamic Host Configuration Protocol (DHCP) does not interact with domain name servers (DNS). 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. ADMU7711E=ADMU7711E: Unexpected exception associated with WASService.exe: {0} during processing of server with name: {1} An unexpected exception has been detected. Verify that the product installation is correct. ADMU3220I=ADMU3220I: Base server runtime initialized. Waiting for application initialization. The server initialized. The product is waiting for application initialization. No user action is required. ADMU8065E=ADMU8065E: You did not specify all required parameters. Required parameters you did not specify are {0} You need to specify all required parameters. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU2014I=ADMU2014I: Restoring original configuration. The original product configuration is being restored. No user action is required. ADMU3111E=ADMU3111E: Server stop requested but failed to complete. The stop request failed. Additional information is supplied in other messages. Record the failure information from the other messages and perform problem determination on the server to investigate why it failed to stop. ADMU2093E=ADMU2093E: Custom property {0} has no value. The specified custom property was found, but has no value. Examine the configuration to be certain a value is specified for the custom property. ADMU0035E=ADMU0035E: WebSphere Express nodes are not supported in a Network Deployment cell. The Express node could not be added to a Network Deployment cell because an Express node is not supported in a Network Deployment environment. Do not attempt to add the node. ADMU7710E=ADMU7710E: Unexpected exit code {1} from WASService.exe while executing {0} An unexpected exit code was returned from WASService.exe Verify WebSphere installation and Windows environment; try running command manually; contact IBM support. ADMU8064E=ADMU8064E: If you specify the nodepassword, you must also specify the nodeusername. You must specify the nodeusername when you specify the nodepassword. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU0251I=ADMU0251I: Begin changing node name for {0} The process of renaming the node has started. No user action is required. ADMU3002E=ADMU3002E: Exception attempting to process server {0} 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. Record and save the exception information in the follow-on message for further problem determination. ADMU2092E=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}. The operation cannot be completed because the product extensions do not match between the node and the deployment manager. Check the product extensions installed on both the node and the deployment manager. Additional product extensions might need to be installed. ADMU0034E=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} The cell name of the Network Deployment manager node must be unique within the cell. Ensure that the cell name of the deployment manager is unique within the cell. ADMU8063E=ADMU8063E: If you specify the nodeusername, you must also specify the nodepassword. You must specify the nodepassword when you specify the nodeusername. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU2012I=ADMU2012I: Backing up Network Deployment configuration. The product configuration is being backed up. No user action is required. ADMU3001I=ADMU3001I: Server {0} open for recovery; process id is {1} The specified server is recovering. No user action is required. ADMU0250I=ADMU0250I: Node {0} has been successfully renamed to {1}. The specified node has been successfully renamed. No user action is required. ADMU8019E=ADMU8019E: Error trying to register an unsupported profile. You can only register a stand-alone application server node with an administrative agent. The node you are trying to register is not a stand-alone server node. You can only register a stand-alone application server node. Ensure that the node you are trying to register to an administrative agent is a stand-alone application server node. ADMU2091E=ADMU2091E: Exception {0} caught checking product extensions on the node or the Deployment Manager. The product extensions installed on the node or the deployment manager could not be determined. Examine the exception to determine the specific problem. ADMU0033E=ADMU0033E: The node {0} already has been added to the cell. You cannot run the addNode command on a node that has already been added to a cell. Do not attempt to run addNode twice on the same node. ADMU8062E=ADMU8062E: If you specify the password, you must also specify the user name. You must specify the user name when you specify the password. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU3000I=ADMU3000I: Server {0} open for e-business; process id is {1} The specified server has started. The process id indicates the PID for Distributed platforms while on z/OS it represents the Server token(stoken). No user action is required. ADMU8018E=ADMU8018E: Error running registerNode on non supported environment. An attempt was made to register a node in an unsupported environment. A node can be registered only when it runs on the same machine as the administrative agent, which is the AminAgent MBean. Register a node, using the registerNode operation, when the node is located on the same machine as the administrative agent. The administrative agent is the AdminAgent MBean. ADMU0032E=ADMU0032E: It is not valid to run addNode on the same node as the Deployment Manager: {0} The addNode program only applies to base app server nodes, not the Network Deployment deployment manager node itself. Do not attempt to run addNode on the Deployment Manager node itself. ADMU8061E=ADMU8061E: If you specify the user name, you must also specify the password. You must specify the password when you specify the user name. Review the associated error in registerNode.log or turn on adminagent trace to diagnose the problem. ADMU2010I=ADMU2010I: Stopping all server processes for node {0} All server processes are being stopped for the specified node. No user action is required. ADMU8017I=ADMU8017I: The administrative subsystem for deregistered node has been successfully destroyed. This message is for informational purposes only. No user action is required. ADMU0031E=ADMU0031E: Node Agent launched but failed initialization. Process id was: {0} The node agent process returned an unsuccessful status value. Examine the log files for the node agent to perform additional problem determination. ADMU6002I=ADMU6002I: Begin Asset Preparation - Preparation of assets has begun. No user action is required. ADMU8060E=ADMU8060E: An error occurred when trying to get the profile key. An error occurred when trying to get the profile key. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU8016I=ADMU8016I: The administrative subsystem for the deregistered node has been successfully stopped. This message is for informational purposes only. No user action is required. ADMU0030I=ADMU0030I: Node Agent initialization completed successfully. Process id is: {0} This is an informational message indicating that the node agent process started without errors. No user action is required. ADMU6001I=ADMU6001I: Begin App Preparation - Preparation of applications has begun. No user action is required. ADMU8015I=ADMU8015I: The administrative subsystem for the registered node has been successfully started. This message is for informational purposes only. No user action is required. ADMU8014I=ADMU8014I: The administrative subsystem for the registered node has been successfully initialized. This message is for informational purposes only. No user action is required. ADMU0129E=ADMU0129E: The deployment manager is of an older version or has less feature packs installed than this node; the node has not been added The deployment manager version is earlier than that of the node. The product requires that the deployment manager version be at the same version as the node, or at a later version. Upgrade the deployment manager to the same version as the node, or a later version than the node. ADMU0064E=ADMU0064E: addNode can only be run from a base (application server) profile The addNode command did not run because the profile from which it was begun is not a base (application server) profile. Run the command from a base (application server) profile, such as AppSrv01. ADMU8013I=ADMU8013I: Application Server with path {0} has been successfully deregistered. The node was successfully deregistered with an adminagent. No user action is required. ADMU8049E=ADMU8049E: An error occurred when adminagent tried to exchange signers with the node. An error occurred when adminagent tried to exchange signers with the node that you tried to register. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU0128I=ADMU0128I: Starting tool with the {0} profile 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. You may want to verify that the profile listed in this message is the desired profile. ADMU0063E=ADMU0063E: The {0} node does not exist in the cell so the -asExistingNode option cannot be used. You cannot use the -asExistingNode option unless the node already exists in the cell. Use the command with a node that already exists in the cell or do not use the -asExistingNode option. ADMU8012I=ADMU8012I: Application Server with path {0} has been successfully registered. Registration of the specified profile successfully completed. No user action is required. ADMU0019E=ADMU0019E: Error occurred reading from an input stream {0} The read method of an I/O stream issued an exception. 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. ADMU8048E=ADMU8048E: Error trying to unregister node that has not been registered. Failed to unregister the node, the node may have not been registered yet or the node may have been registered to different AdminAgent. Check if the node you are trying to unregister was registered or make sure you try to unregister the node from the correct AdminAgent. ADMU0127E=ADMU0127E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}). The deployment manager version is earlier than that of the specified node. The product requires that the deployment manager version be at the same version as the node, or at a later version. Upgrade the deployment manager to the same version as the node, or a later version than the node. ADMU0062E=ADMU0062E: The -asExistingNode option cannot be used with any of the following options: {0} The -asExistingNode option is incompatible with these options. Retry the command and omit either the -asExistingNode option or all of the incompatible options. ADMU7773E=ADMU7773E: Generic Server: {0} is not RUNNING An attempt was made to stop a generic server that is not running. Ensure that the generic server is running before attempting to stop it. ADMU0018I=ADMU0018I: Launching Node Agent process for node: {0} The node agent process is starting. No user action is required. ADMU0061W=ADMU0061W: The -nodeagentshortname option is used in a z/OS environment only. The -nodeagentshortname option is ignored on operating systems other than the z/OS operating system. Use the option on the z/OS operating system only. ADMU8047E=ADMU8047E: An error occurred when invoking listProfiles operation on AdminAgent mbean; rolling back to original configuration. Failed invoking listProfiles operation on AdminAgent mbean. Review the associated error in registerNode.log or turn on trace to diagnose the problem. ADMU0126E=ADMU0126E: The version of the Deployment Manager ({0}) is earlier than that of this node ({1}); the node has not been added. The deployment manager version is earlier than that of the specified node. The product requires that the deployment manager version be at the same version as the node, or at a later version. The node has not been added to the cell. Upgrade the deployment manager to the same version as the node, or a later version than the node. ADMU7772I=ADMU7772I: Generic Server: {0} STOPPED successfully. The generic server successfully stopped. No user action is required. ADMU0060W=ADMU0060W: The -portprops option overrides the -startingport option. The options are mutually exclusive. Specify the correct option. ADMU8010I=ADMU8010I: Begin registration of Application Server with path {0} Registration of the profile has begun. No user action is required. ADMU0017E=ADMU0017E: Error occurred closing an input/output stream {0} 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. 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. ADMU3201I=ADMU3201I: Server stop request issued. Waiting for stop status. A request to stop the server was made. The product is waiting for server status. No user action is required. ADMU8046E=ADMU8046E: The administrative agent port number specified for {0} connector is invalid, registerNode cannot continue. Failed to register the node because the port number specified is invalid. Check your administrative agent serverindex.xml and find the correct port number of the connector. ADMU0125E=ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager. The addNode command failed because the clock of the new node is out of synchronization with the deployment manager. Change the clock of the new node to be within the specified minutes of the clock of the deployment manager. ADMU7771E=ADMU7771E: Generic Server: {0} already running - use the "-forceGenericServerStart" to force server start! An attempt was made to start a generic server that has already been started. 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. ADMU0016I=ADMU0016I: Synchronizing configuration between node and cell. Configuration synchronization is occurring between a node and a cell. No user action is required. ADMU8045I=ADMU8045I: Node has been successfully deregistered. The node has been deregistered from an adminagent. No user action is required.