Explanation | This is an informational message indicating that the addNode program has started. |
Action | None |
Explanation | An exception occurred while attempting to attach to the server and obtain its state. |
Action | Record the exception information from this message for further investigation. |
Explanation | This is an informational message indicating that the addNode program has successfully completed. |
Action | None |
Explanation | An exception occurred during config synchronization while waiting for an asynchronous operation on the Deployment Manager. |
Action | Record the exception information from this message for further investigation. |
Explanation | An error occurred during configuration synchronization. If the error was encountered during addNode, the configuration will be rolled back to the base configuration. If this error was encountered during syncNode, node and cell repositories may be out of sync with each other. |
Action | Examine the log files for additional problem determination information. |
Explanation | The client utility program was not able to establish a connection to the Deployment Manager using the information provided. |
Action | Check that the Deployment Manager host and port are reachable from the system on which the utility is being executed. One method to check connectivity is to use the TCP/IP "ping" command. If security is enabled, ensure the user and password are specified correctly. |
Explanation | The program was not able to copy a file. There may not be enough disk space or there may be a problem reading the file. |
Action | Check the available disk space on the system. Check that the file does exist and is readable. |
Explanation | A query to locate an MBean failed. |
Action | Record the exception information in this message for further investigation. |
Explanation | This is an informational message indicating that the program has established communications with the Deployment Manager. |
Action | None |
Explanation | A client connection for the Cell configuration repository could not be obtained. |
Action | Record the exception information from this message for further problem determination. |
Explanation | Configuration files for the new node could not be uploaded to the Deployment Manager for creation in the cell repository. |
Action | Ensure that the Deployment Manager is still running and that the FileTransfer application is executing in the Deployment Manager. Record the exception information from this message for further problem determination. Ifthe JVM OutOfMemoryError is in the java stack trace in the addNode.log, the heapsize of addNode or the Deployment Manager may need be increased. For addNode, this is done by adding the -Xmx(size) parameter in the addNode script. For the Deployment Manager, the maximumHeapSize parameter in server.xml should be changed. |
Explanation | This is an informational message indicating that the addNode program is creating the configuration files related to the node agent for the new node. |
Action | None |
Explanation | This is an informational message. |
Action | None |
Explanation | This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program. |
Action | None |
Explanation | This is an informational message indicating that the original configuration files are being saved before they are changed by the utility program. |
Action | None |
Explanation | This is an informational message indicating that a configuration synchronization is about to begin. |
Action | None |
Explanation | The close method of an I/O stream object issued an exception. This probably is a secondary exception that came after an earlier I/O failure. |
Action | Record and save the exception information in this message for further problem determination. Examine the log file for the utility and rerun the program with -trace option. |
Explanation | This is an informational message indicating that the node agent process is about to be started. |
Action | None |
Explanation | The read method of an I/O stream issued an exception. |
Action | Record and save the exception information in this message for further problem determination. Examine the log file for the utility and rerun the program with -trace option. |
Explanation | This is an informational message. |
Action | None |
Explanation | The status of the server is not STOPPED as expected. |
Action | Examine the log files for the server to see why the server is not stopped. |
Explanation | This is an informational message. |
Action | None |
Explanation | An IOException was issued while the program was waiting for input on the server status port. |
Action | Record and save the exception information from this message for further problem determination. Examine the log file for the utility and rerun the program with the -trace option. |
Explanation | This is an informational message indicating that the original configuration files are being saved before they are changed by the utility program. |
Action | None |
Explanation | The connected process does not have a DeploymentManager MBean. The most common cause is that the host/port specified is not that for the Deployment Manager. |
Action | Verify that the host and port passed to the tool are correct. |
Explanation | If an error occurs during the addNode command process and it cannot complete, the original configuration is restored to the original state. before addNode was requested. |
Action | Review the associated messages in addNode.log to determine the specific problem and retry the addNode command. |
Explanation | If an error occurs during the addNode command process and it cannot complete, the original configuration is restored to the original state. before addNode was requested. |
Action | Review the associated messages in addNode.log to determine the specific problem and retry the addNode command. |
Explanation | This is an informational message. |
Action | None |
Explanation | A problem occurred during node removal process. |
Action | Examine the exception to determine the specific problem and take corrective action. |
Explanation | This is an informational message indicating that the node agent process started without errors. |
Action | None |
Explanation | The node agent process returned an unsuccessful status value. |
Action | Examine the log files for the node agent to perform additional problem determination. |
Explanation | The addNode program only applies to base app server nodes, not the ND deployment manager node itself. |
Action | Do not attempt to run addNode on the Deployment Manager node itself. |
Explanation | You cannot run addNode on a node that has already been added to a cell. |
Action | Do not attempt to run addNode twice on the same node. |
Explanation | The cell name of the ND manager node must be unique with the node. |
Action | Insure that the cell nameof the ND manager node is unique within the cell. |
Explanation | An attempt has been made to add a node that is a WebSphere Express node. |
Action | Do not attempt to add a WebSphere Express node. It is not a supported node for the Network Deployment environment. |
Explanation | The local host can lookup the Deployment Manager host, but the Deployment Manager cannot lookup the new node; often this occurs if DHCP does not interact with DNS. |
Action | You may need to use static IP if DHCP does not interact with DNS. If the hostname is not fully qualified, you may need to update the hostname using the AdminCommand $AdminTask changeHostName {-nodeName xxx -hostName xxx} |
Explanation | There is a problem with the configuration of the Deployment Manager's host name. The local node cannot lookup the Deployment Manager's host name as it is specified in the Deployment Manager configuration. |
Action | Either the Deployment Manager's host name needs to be added to DNS, the Deployment Manager's host name needs to be fully qualified in the Deployment Manager's server index configuration, or the domain's DNS suffix needs to be added to the node's TCP/IP configuration. |
Explanation | The Deployment Manager's host name is not resolving correctly. |
Action | Verify that the host name is configured properly at the Deployment Manager. For Linux systems, modify either the /etc/hosts file or the /etc/nsswitch.conf file search DNS before files. |
Explanation | You cannot run addNode to add a node to a cell which already contains a node of the same name. |
Action | Do not attempt to run addNode to add a node to a cell already containing a node of the same name. |
Explanation | An MBean call failed. |
Action | Record and save the exception information from this message for further problem determination. |
Explanation | Concurrent addNode and removeNode operations are not allowed. |
Action | Wait until the first addNode or removeNode operation completes, and then retry this operation. |
Explanation | The lock used to prevent concurrent addNode and removeNode operations could not be reset. |
Action | If you can not run an addNode or removeNode operation after receiving this message, you can clear the lock by invoking the AdminOperations.forceNodeFederationOrRemovalTokenReset operation. |
Explanation | The exception that was encountered during program execution follows the message text. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The exception that was encountered during program execution follows the message text. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The exception that was encountered during program execution follows the message text. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The exception that was encountered during program execution follows the message text. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | One or more warnings occurred while checking whether the node can join the node group. |
Action | None. |
Explanation | One or more warnings occurred while converting the node group to a sysplex node group. |
Action | None. ADMU0060W is issued for each warning message encountered. |
Explanation | One or more warnings occurred while adding the node to the node group. |
Action | None. |
Explanation | One or more warnings occurred while removing the node from all node groups. |
Action | None. |
Explanation | This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program. |
Action | None |
Explanation | This is an informational message indicating that configuration files from the node are about to be uploaded to the cell repository managed by the Deployment Manager program. |
Action | None |
Explanation | The options are mutually exclusive. |
Action | Specify the correct option. |
Explanation | This option is ignored for a non-z/OS environment. |
Action | Use this option in a z/OS environment only. |
Explanation | The attempt to retrieve the signer certificates from the dmgr failed. The username and/or password specified may be incorrect. |
Action | Verify the username and password are correct or use the retrieveSigners script to download the signer certificates from the dmgr. |
Explanation | The server name does not match the process attributes. |
Action | Check that the name is spelled correctly. |
Explanation | A problem was encountered during the rollback of application binaries.. |
Action | Please consult the addNode.log file for additional information. |
Explanation | An exception occurred during program execution. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The code that attempts to update the serverindex.xml configuration file failed and issued an exception. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be written to. |
Explanation | An exception occurred during program execution. |
Action | Record the exception information from this message and perform problem determination using that exception data. |
Explanation | The attempt to launch the node agent for the new node failed and issued an exception. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the process failed to launch. |
Explanation | This is an informational message indicating that trace has been enabled |
Action | None |
Explanation | This is an informational message indicating the file in which logging data is being stored. |
Action | None |
Explanation | The application already exists in the cell configuration repository and uses a different URL for the location of its binaries. It cannot be merged with cell configuration and will be ignored. |
Action | Install the application on the Deployment Manager if it is to be used in servers for this cell. |
Explanation | An error occurred attempting to write the logfile; this may be caused by a permissions or security problem |
Action | Use the -logfile option to specify a new location for the logfile |
Explanation | An unexpected exception occured while attempting to expand the application ear files to appropriate locations after addNode command failed. Users will have to explicitly expand ear files for all the applications on this cell to their appropriate binariesURL locations. |
Action | Use EARExpander tool to expand the application ear files to their appropriate destination specified in the binariesURL attribute of the deployment.xml file in the repository. |
Explanation | None |
Action | None |
Explanation | An exception occured while checking if the application already exists in the repository to which this node is being added to. Therefore this application will not be uploaded as a part of addNode even if -includeapps options is specified. |
Action | You can install this application after addNode is done either by using the admin UI or wsadmin. |
Explanation | Unexpected exception in file copy. |
Action | Manually copy files. |
Explanation | The specified message ID could not be found in the message file; contact IBM support. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | To add a node, the system clock of the node to be added must be fairly close to that of the deployment manager. |
Action | Change the new node's system clock to be the same as that of the deployment manager. |
Explanation | Explanation of what to do if addNode fails because of the clock sync problem. |
Action | Follow the instructions in the message. |
Explanation | Deployment Manager version earlier than that of a node is an unsupported configuration. |
Action | Upgrade the Deployment Manager to the same or later version as that of the node. |
Explanation | Deployment Manager version earlier than that of a node is an unsupported configuration. |
Action | Upgrade the Deployment Manager to the same or later version as that of the node. |
Explanation | If -profileName is passed, that specified profile will be used. If run from a profile's bin directory, that profile will be used. Otherwise the default profile is used. This message just clarifies the profile used. |
Action | You may want to verify that the profile listed in this message is the desired profile. |
Explanation | The server short name already exists in the distributed cell to which this node is being added. |
Action | Make sure server short name is unique across all the servers in the distributed cell before running addNode. Change the server short name to be unique in the Deployment Manager cell, then run addNode |
Explanation | The cluster transition name already exists in the distributed cell to which this node is being added. |
Action | Make sure cluster transition name is unique across all the servers in the distributed cell before running addNode. Change the cluster transition name to be unique in the Deployment Manager cell, then run addNode |
Explanation | The node short name already exists in the distributed cell to which this node is being added. |
Action | Make sure the node short name is unique across all the nodes in the distributed cell before running addNode. Change the node short name to be unique in the Deployment Manager cell then run addNode |
Explanation | The node agent short name already exists in the distributed cell to which this node is being added. |
Action | Make sure the node agent short name is unique across all the nodes in the distributed cell before running addNode. Change the node agent short name to be unique in the Deployment Manager cell then run addNode |
Explanation | This is an informational message indicating that additional information is available in the log file. |
Action | Look in the file for additional information. |
Explanation | The code that attempts to upload the plugin-cfg.xml configuration file failed and issued an exception. |
Action | Record and save the exception information from this message and perform further problem determination to investigate why the file cannot be accessed. |
Explanation | This is an informational message indicating that the renameNode program has successfully completed. |
Action | None |
Explanation | This is an informational message indicating that rename node program has been started. |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | This is an informational message indicating that the syncNode program has started. |
Action | None |
Explanation | This is an informational message indicating that the syncNode program has completed successfully. |
Action | None |
Explanation | The syncNode command is a recovery tool that performs an offline synchronization operation. To avoid interference the node agent must be stopped prior to running syncNode. |
Action | Stop the node agent before running syncNode or use the normal synchronization facility via the admin console or the NodeSync MBean. |
Explanation | This is an informational message. |
Action | None |
Explanation | The serverStatus tool requires that a server name be provided or -all to list all servers. |
Action | Specify a server name or -all. |
Explanation | This is an informational message. |
Action | None |
Explanation | This is an informational message printed before a list of servers. |
Action | None |
Explanation | This is an informational message showing the name of a server. |
Action | None |
Explanation | The servers directory is empty in the configuration. |
Action | Check the integrity of the configuration files. |
Explanation | This is an informational message the shows the state of the server. |
Action | None |
Explanation | This is an informational message indicating that the server appears to be stopped. |
Action | None |
Explanation | This is an informational message the shows the state of the server. |
Action | None |
Explanation | This is an informational message indicating that the server appears to be stopped. |
Action | None |
Explanation | A JMX connector type was requested that is not supported. |
Action | Request a connector type that is supported. |
Explanation | No node was located in the configuration repository with the specified name. |
Action | Check the spelling of the node name. Check the integrity of the configuration files. |
Explanation | No server was located in the configuration repository by the specified name. |
Action | Check the spelling of the server name. Check the integrity of the configuration files. |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message explaining why a Queue Manager is not created. |
Action | None |
Explanation | This is an informational message. |
Action | Look in the file for more information. |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message. |
Action | Look in the file for more information. |
Explanation | During removeNode processing, the applications from the original configuration are put back in place. Something caused this process to fail and manual recovery is necessary. |
Action | Use EARExpander tool to expand the application ear file to the appropriate location specified by binariesURL attribute in the corresponding deployment.xml config files. |
Explanation | This is an informational message indicating that the -trace option is available to be used in order to gather additional trace information. |
Action | Consider using the -trace option on the command line. |
Explanation | There was a problem found while registering node agent as Windows service. |
Action | Please check addNode.log for additional information. |
Explanation | There was a problem found while de-registering node agent as Windows service. |
Action | Please check addNode.log for additional information. |
Explanation | You must specify "-serviceUserName" and "-servicePassword" together. You must also specify "-registerService" |
Action | Please obtain values for the above and resubmit request. |
Explanation | This is an informational message indicating that the removeNode program has started. |
Action | None |
Explanation | The file was not located. |
Action | Check that a setupCmdLine file exists in the installation. |
Explanation | An exception occurred |
Action | Record the exception data and perform further problem determination. |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message explaining that the -force option can be used to eliminate the message. |
Action | None |
Explanation | The node configuration files remain in the cell configuration repository. |
Action | If the -force option is used, the cleanupNode utility will need to be run on the Deployment Manager to remove the config files for this node. |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | A problem occurred attempting to remove the applications from this node. |
Action | Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | This is an informational message marking the progress of the program. |
Action | None |
Explanation | A problem occurred attempting to remove the servers from the clusters. |
Action | Examine the exception to determine the specific problem. To force the node to be removed, specify the -force option. |
Explanation | This is an informational message indicating that removeNode has successfully completed. |
Action | None |
Explanation | This node was removed from the cell, but problems occurred during the removal. |
Action | Examine the previous errors to determine what occurred. The cleanupNode utility may need to be run to remove this node from the Deployment Manager's config. |
Explanation | An attempt was made to remove a node that has never been added in the first place. |
Action | Run addNode before attempting to run removeNode. |
Explanation | The variable map could not be created. This means applications may not be restored or deleted from their binaries URL. |
Action | Run EARExpander tool to expand the application ear files to their appropriate locations. |
Explanation | EAR file could not be expanded to the destination. |
Action | Run EARExpander tool to expand the ear file to its appropriate locations. |
Explanation | EAR file could not be obtained from the specified location. The ear will not be expanded to the specified destination. |
Action | Run EARExpander tool to expand the ear file to its appropriate locations. |
Explanation | The specified deployment.xml could not be loaded to obtain binariesURL. The ear file will not be expanded or deleted from that location. |
Action | Run EARExpander tool to expand the ear file to its appropriate location if needed. Or delete the directory where ear was supposed to be deleted from. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | Warning message informing user removeNode tool cannot complete when a node was created during Cell Profile creation. |
Action | Use manageprofiles utility to delete this node and run cleanupNode utility on Deployment Manager. See WAS Infocenter. |
Explanation | Suggestion to clean up a node after running removeNode with possible warnings or errors. |
Action | See WAS Infocenter. |
Explanation | A problem occurred trying to determine which product extensions are installed. |
Action | Examine the exception to determine the specific problem. |
Explanation | The operation cannot be completed because the product extensions do not match. |
Action | Check the product extensions installed on both the node and the Deployment Manager. Additional product extensions may need to be installed. |
Explanation | The specified custom property was found, but has no value. |
Action | Examine the configuration to be certain a value is specified for the custom property. |
Explanation | The operation will continue even though the product extensions do not match. |
Action | Ensure the necessary product extensions are installed on the node to support any subsequent operations and configurations applied to it. Additional product extensions may need to be installed. |
Explanation | This is an informational message indicating that the server has started. |
Action | None |
Explanation | This is an informational message indicating that the server is doing recovery. |
Action | None |
Explanation | A more detailed exception has occurred while attempting to start or stop the named server. This message is always paired with a second message that displays the detailed exception. |
Action | Record and save the exception information in the follow-on message for further problem determination. |
Explanation | Some general exception condition has been discovered. |
Action | Combine this information with additional exception messages in order to perform additional problem determination. |
Explanation | An exception occurred while the program was listening to the status socket for the server. |
Action | Record and save the exception information in this message for further problem determination. |
Explanation | The server process failed to start. |
Action | Examine the log files to see what failure messages were recorded there. |
Explanation | A free port was not able to be allocated for communicating server status. |
Action | Examine the log file for the utility to perform further problem determination. Attempt to execute the utility again. |
Explanation | The server has completed recovery and has stopped. |
Action | This is an informational message. |
Explanation | The server had problems during recovery and has stopped. |
Action | Examine the log files to see what failure messages were recorded there.) |
Explanation | An exception was issued while the server was in the process of stopping. |
Action | Examine the log files for the server to see why the stop function issued an exception. |
Explanation | An attempt has been made to start a server that is already running. |
Action | Do not attempt to start a server that is already running. |
Explanation | A port required by this server is already in use by this or aother server. |
Action | Do not attempt use a port that is already in use. |
Explanation | The server initialization process has exceeded the timeout limit. |
Action | Perform problem determination on the server to check for possible errors. |
Explanation | The MBean of type Server appears to be missing from the process. |
Action | Check that the named server is actually running on the host and port specified. |
Explanation | A query to locate an MBean failed. |
Action | Check that the server process is still running. Examine the log files for the program to perform further problem determination. |
Explanation | The amount of time taken for server shutdown exceeded the -timeout value requested. |
Action | Use a larger -timeout value or perform problem determination on the server to investigate possible errors. |
Explanation | This is an informational message marking progress of the program. |
Action | None |
Explanation | This is an informational message indicating that explicit host or port options were used. |
Action | None |
Explanation | The stop request failed. Additional information is supplied in other messages. |
Action | Record the failure information from the other messages and perform problem determination on the server to investigate why it failed to stop. |
Explanation | This is an informational message marking progress of the program. |
Action | None |
Explanation | This is an informational message marking progress of the program. |
Action | None |
Explanation | This is an informational message marking progress of the program. |
Action | None |
Explanation | This is an informational message indicating that the launch script has been successfully created. |
Action | None |
Explanation | The -nowait option was used for startServer, so no initialization status is available for the launched process. |
Action | None |
Explanation | This is an informational message. |
Action | None |
Explanation | This tool requires that a server name be provided. |
Action | Specify a server name. |
Explanation | The specified server name cannot be located within the configuration for this node. |
Action | Check that the specified name is spelled correctly and that a directory by that name does exist under the servers directory in the configuration. |
Explanation | This is an informational message indicating that the stopServer command succeeded. |
Action | None |
Explanation | "-script" option is not supported on zOS platform. |
Action | Remove the "-script" option and rerun the command. |
Explanation | An error occurred during program execution. |
Action | Perform problem determination to investigate possible causes. |
Explanation | This is an informational message indicating where to look for further information. |
Action | Look in the file for more information. |
Explanation | The tool could not contact the remote server because of a credentials problem. |
Action | Pass in the correct username and password. If using command prompt, pass in -username & -password, or update the soap/sas.client.props file. |
Explanation | There is a problem establishing a connection to a process. |
Action | Make sure that the targeted process is really running and make sure that proper username and password are used when attempting to connect to the process running in secure mode. |
Explanation | There is a problem establishing a connection to the Deployment Manager. |
Action | Make sure that the Deployment Manager is really running and make sure that proper hostname and port are used when attempting to connect to the process. |
Explanation | This is an informational message telling the user about the -trace command line option. |
Action | None |
Explanation | This is an informational message saying the backup is beginning |
Action | None |
Explanation | This is an informational message saying the number of files successfully backed up |
Action | None |
Explanation | The file specified containing the backed-up config documents cannot be found. |
Action | Verify that the file given to restoreConfig exists and can be read. |
Explanation | This is an informational message saying the location to restore already exists and will be renamed |
Action | None |
Explanation | A problem occurred attempting to rename the restore location |
Action | Use the -location option to specify a location which does not exist, or one which can be renamed |
Explanation | This is an informational message saying the location specified has been renamed |
Action | None |
Explanation | This is an informational message saying the restore is beginning |
Action | None |
Explanation | This is an informational message saying the number of files successfully restored |
Action | None |
Explanation | NONE |
Action | NONE |
Explanation | NONE |
Action | NONE |
Explanation | NONE |
Action | NONE |
Explanation | The exception message may detail probable cause. |
Action | If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear. |
Explanation | This backup file was created from a system with a different cell name. |
Action | Either user the "-force" option and manually correct the resulting problems or restore using a backup file that used the same cell name as current system. |
Explanation | This backup file was created from a system with a different cell name |
Action | After the restore operation has completed please correct any resulting problems and confirm proper system function before starting production applications. |
Explanation | The disk may be full or the directory may not have write permission. |
Action | Use EARExpander tool to extract the ear file. |
Explanation | When a server is registered to run as a Windows Service, the Windows Service is used to start the server. |
Action | None |
Explanation | When a server is registered to run as a Windows Service, the Windows Service is used to stop the server. |
Action | None |
Explanation | When a server is removed, the corresponding Windows Service is deregistered. |
Action | None |
Explanation | The Windows Service associated with this server failed to start. |
Action | Check return code and correct the problem then retry the operation. |
Explanation | The Windows Service associated with this server failed to stop. |
Action | Check return code and correct the problem then retry the operation. |
Explanation | The Windows Service associated with this server failed to deregister. |
Action | Check return code and correct the problem then retry the operation. |
Explanation | The Windows Service associated with this server could not be found. |
Action | Please verify that there is a valid Windows Service associated with this server. |
Explanation | The log file for the Windows Service associated with this server could not be found. |
Action | Verify WebSphere installation. If nothing found, contact IBM support. |
Explanation | An unexpected exception has been detected. |
Action | Verify WebSphere installation. If nothing found, contact IBM support. |
Explanation | An unexpected exit code was returned from WASService.exe |
Action | Verify WebSphere installation and Windows environment; try running command manually; contact IBM support. |
Explanation | An unexpected exception has been detected. |
Action | Verify WebSphere installation. If nothing found, contact IBM support. |
Explanation | The status for the Windows Service could not be obtained. |
Action | Verify WebSphere installation. If nothing found, contact IBM support. |
Explanation | Another command is running and might conflict with this one. |
Action | Wait a few minutes and try the command again. |
Explanation | Request to start generic server was successful. |
Action | None |
Explanation | User is trying to start a generic server that has already been started. |
Action | Use "stopServer.(bat|sh)" to stop the generic server, then retry the startServer command or use the "-forceGenericServerStart" option to try to force the start of the generic server. |
Explanation | Request to stop generic server was successful. |
Action | None |
Explanation | User is trying to stop a generic server that has not been started. |
Action | Be sure that generic server is RUNNING before attempting to stop it. |
Explanation | None |
Action | None |
Explanation | The option specified is not a known option. |
Action | Examine the usage statement and specify a known option. |
Explanation | A parameter is required for the displayed option, and one was not provided. |
Action | Provide a parameter for this option. |
Explanation | The parameter that is provided is not valid for the given option. |
Action | Provide a different parameter. |