ADML0064I=ADML0064I: Restarting an unreachable server "{0}". This information message indicates the program status. No user action is required. ADML0115I=ADML0115I: The trace mode is on. The trace output is directed to: {0} The trace data is stored in a file. No user action is required. ADML0005I=ADML0005I: The ${USER_INSTALL_ROOT} variable is missing; the tool is using ${WAS_INSTALL_ROOT} as a default. The ${USER_INSTALL_ROOT} variable is not set in the configuration files. Edit the configuration and provide a ${USER_INSTALL_ROOT} variable. ADML3001W=ADML3001W: The {0} property is missing from the systemlaunch.properties file. A required property cannot be located in the system.properties file. Edit the file and add the required property, along with a value for that property. ADML0063W=ADML0063W: The tool cannot contact server "{0}". Force stop this server if it is still running. The nodeagent failed to contact the given server. The server might be malfunctioning. The specified server can be restarted if the"autoRestart" attribute is set to "true" in the server monitoring policy, which is defined in the server.xml file. For restarting the server, the nodeagent must try to stop the server by calling the stop method on the process. If the stop does not complete, the nodeagent may also call the terminate method on the process. Check the logs and trace for this server. Normally, the logs show why the server cannot respond to the nodeagent. If the "autoRestart" attribute is set to true, check to see whether the nodeagent restarted the server. ADML0004E=ADML0004E: An exception occurred when attempting to expand variable {0} {1}. The variable in the configuration data cannot be resolved. The variable may not exist or it may have the wrong value. Check variable.xml file in your WebSphere configuration to see make sure the variable exist and has the correct value. Edit the configuration and change the value of the property to use a variable that can be resolved. ADML0059E=ADML0059E: An error occurred restarting the nodeagent: {0} The nodeagent failed to restart itself. Stop and start the nodeagent by using the startNode or stopNode command-line utilities scripts. ADML0062W=ADML0062W: The tool cannot load the server.xml file for server {0}. The nodeagent failed to load the server.xml file to read the monitoring policy for a given server. Open the problem server.xml file to check for XML syntax errors. ADML3000E=ADML3000E: The tool is unable to locate the systemlaunch.properties file: {0} The systemlaunch.properties file contains default settings for important system properties. This file is required for server launching. Verify that the file is available and can be read. ADML0029E=ADML0029E: No configuration is defined for server: {0} An attempt was made to start a server that has no configuration. Verify that the server name is correct. ADML0068I=ADML0068I: Attempt {0} to restart an unreachable server "{1}" returned with the following status indicating whether the server was restarted successfully: {2} Multiple attempts are made to restart an unreachable server. This message indicates the resulting status for one of these attempts. No user action is required. ADML0019E=ADML0019E: An exception occurred waiting for the server stop {0}. The server could not be stopped. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0003E=ADML0003E: A configuration error occurred in the ProcessDef Umask property {0}. The value of the Umask property is not in a valid integer format. The valid format is string containing the integer representation. Edit the configuration and change the value of the process Umask property. ADML0009E=ADML0009E: An exception occurred waiting for server initialization {0}. An error occurred while waiting for the server to get initialized. The server socket may have been timeout. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0058E=ADML0058E: An error occurred while stopping the node. The nodeagent failed to stop the local application servers or itself. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0523E=ADML0523E: An error occurred trying to get the object name of server {0}.: {1} The Server MBean could not be queried. The server name might be misspelled or the Server MBean might not run. Check the spelling of the server name. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0008W=ADML0008W: An unsupported platform type is encountered: {0} {1} The program is starting on an operating system platform that is not supported. Do not attempt to run the program on this platform. ADML0012E=ADML0012E: An exception occurred when attempting to get a free port for status socket {0}. The server status could not be obtained because the attempt to bind to a socket failed. The socket might be in use. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. If the problem caused by socket in use, check with your network administrator how to solve this problem. ADML0061E=ADML0061E: An error occurred during synchronization. Set the synchOnServerStartup value to false, if you want to proceed without synchronization. The nodeagent tried to do file synchronization before launching the process, but the synchronization failed. Check to see the nodeagent is started without error by looking at nodeagent logs. Or set the synchOnServerStartup value to false if you want to proceed without synchronization. ADML0018I=ADML0018I: The log is generated. The program log was generated. No user action is required. ADML0067I=ADML0067I: The initial heap size of {0} MB is larger than the maximum heap size of {1} MB. The server will use a maximum heap size that is the same value as the initial heap size. The server will fail to start with an initial heap size that is greater than the maximum heap size. No action is necessary. ADML0057E=ADML0057E: An error occurred while running file synchronization. The nodeagent failed to run the file synchronization. Check the logs and trace to see the detailed error. ADML0060W=ADML0060W: The tool cannot contact server "{0}". The server will not be restarted since Automatic Restart is false. The node agent failed to contact the server. The server might be malfunctioning. The specified server restarts if the "autoRestart" attribute is set to "true" in the server monitoring policy, which is defined in the server.xml file. For this server, the "autoRestart" attribute is set to false. Check the logs and trace for this server. Usually, the logs show why the given server cannot respond to the node agent. ADML0031E=ADML0031E: The value specified in the ExecutableTargetKind property {0} is not valid. The value of the ExecutableTargetKind property is not valid. Select a valid ExecutableTargetKind such as Java class or jar. You may want to examine the exception in this message for problem determination. You could also check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0011E=ADML0011E: The server launched, but failed initialization. See the server log files for failure information. The server failed to run. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0066I=ADML0066I: The stop did not complete. The node agent is trying to end processing of server "{0}". The node agent tried unsuccessfully to stop an application server. The node agent is trying the terminate method to force the server to end processing. Check the logs and trace for this server. Usually, the logs show why the server cannot respond to the node agent. See whether the node agent was able to terminate the process and restart the server. ADML0111E=ADML0111E: A request to stop the server stop failed to complete. The server did not return a status indicating that it completed shutdown in response to a stop request. Examine the server logs and trace to see if an exception occurred during the stop logic that might have prevented a successful shutdown. ADML0056E=ADML0056E: The tool is unable to initiate monitoring for process {0} with PID {1} because of exception: {2} The nodeagent failed to establish a connection to the launched process. Check to make sure nodeagent is running, look at nodeagent logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0040E=ADML0040E: The process timed out waiting for server "{0}" initialization: {1} seconds The server initialization process exceeded the timeout limit. Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. ADML0065W=ADML0065W: A sync operation prior to starting an application server failed. The node agent started the application server, but could not first synchronize the configuration data of the node with the master copy of configuration data at the deployment manager. The deployment manager might not be running or might be unavailable. If you require synchronization for the server configuration, ensure that the deployment manager is running before another synchronization occurs. ADML0220I=ADML0220I: The base server run time initialized; the tool is waiting for application initialization. This informational message indicates the progress of the program. No user action is required. ADML0000I=ADML0000I: The server initialization is complete. The process ID is: {0}, server name is: {1} The server process started successfully. No user action is required. ADML0006E=ADML0006E: The ${WAS_INSTALL_ROOT} variable is missing. The variable setting for ${WAS_INSTALL_ROOT} value is missing. This variable is required. Edit the configuration and provide a ${WAS_INSTALL_ROOT} variable.