Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin launcher has been invoked with the "-c" option. This option requires that a string be supplied to be interpreted as a wsadmin command. |
Action | Reissue the wsadmin command with a command string following the -c option. |
Explanation | The wsadmin launcher has been invoked with an option that requires the name of a file, but no such argument was found. These options are -f, -p, and -profile. |
Action | Reissue the wsadmin command with a file name following the option. |
Explanation | The wsadmin launcher has been invoked with the -host option, but no host name argument was found. |
Action | Specify a host name for the -host option and reissue the wsadmin command. |
Explanation | The wsadmin launcher has been invoked with the -port option, but no port number argument was found. |
Action | Specify a port number for the -port option and reissue the wsadmin command. |
Explanation | The wsadmin launcher has been invoked with the -lang option, but no language argument was found. |
Action | Specify a supported scripting language for the -lang option and reissue the wsadmin command. |
Explanation | The wsadmin launcher has been invoked with the -conntype option, but no connection type argument was found. |
Action | Specify a connection type for the -conntype option and reissue the wsadmin command. For example, the SOAP, RMI, or NONE connection types are valid values for the -conntype option. |
Explanation | The wsadmin launcher has been invoked with the -port option, but the string following -port is not an integer. |
Action | Specify an integer port argument for the -port option and reissue the wsadmin command. |
Explanation | The wsadmin launcher cannot determine what port number should be used when a connector is created. |
Action | Specify a -port option on the wsadmin command line or a com.ws.scripting.port property in the wsadmin.properties file. |
Explanation | The connection type was supplied on the command line -conntype option or in the com.ws.scripting.connectionType property in the wsadmin.properties file is not valid. |
Action | Correct the connection type on the command line or properties file. Specify "SOAP," "RMI," or "NONE." |
Explanation | The wsadmin launcher has been invoked with an option that requires the name of a file, but the file cannot be found. |
Action | Correct the name of the file specified by the -p, -f, or -profile option, or in a wsadmin.properties file. |
Explanation | During wsadmin initialization, a properties file could not be loaded. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | The wsadmin tool cannot determine which scripting language to use for the specified file. |
Action | Specify a value for the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | The wsadmin tool cannot determine which scripting language to use for an interactive session. |
Action | Specify a value for the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | The wsadmin tool cannot run interactive mode for the specified command. |
Action | Examine the accompanying exception information to determine the appropriate action. |
Explanation | An IO exception occurred while reading a script or profile. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system, and that there are no file permission problems. |
Explanation | The script or profile cannot run. The wsadmin tool created an exception. |
Action | Examine the wsadmin.traceout log file to determine the problem. |
Explanation | An unsupported scripting language was specified. |
Action | Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option. |
Explanation | The wsadmin tool requires connection type information. Specify the connection type with the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties. |
Action | Specify a valid connection type with the -conntype command line option or the com.ibm.ws.scripting.connectionType property in wsadmin.properties. |
Explanation | A host must be specified for the connection type. |
Action | Specify a valid host with the -host command line option or the com.ibm.ws.scripting.host property in wsadmin.properties. |
Explanation | The wsadmin tool cannot determine which scripting language to use with the -c option. |
Action | Specify a supported scripting language with the -lang option on the wsadmin command line, or com.ibm.ws.scripting.defaultLang property in the wsadmin.properties file. |
Explanation | The wsadmin tool created an exception when executing the command. |
Action | Examine the exception information provided in the message to determine the appropriate user action. |
Explanation | The connector did not establish a connection to the host. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. |
Explanation | The connector did not establish a connection to the host. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. |
Explanation | The wsadmin tool did not create the ObjectName object because a string was incorrectly formatted. |
Action | Verify that the string is not empty and that it is correctly formatted for an ObjectName string. |
Explanation | The AdminControl getConfigId or completeObjectName command cannot run because the ObjectName template that has been specified matches two or more running MBeans. This informational message indicates that the first matching MBean will be used. |
Action | Verify that first matching MBean is correct. Otherwise, specify the desired MBean and reissue the command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The connector did not establish a connection to the server. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server might not be running. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminConfig command did not start because the wsadmin process is not connected to a server with a running config service. |
Action | Specify a server with a running configuration services and reissue the wsadmin command. |
Explanation | The wsadmin tool is initialized but cannot connect to a server. |
Action | Reissue the wsadmin command to create a server connection. |
Explanation | The AdminControl reconnect command did not reconnect to the server. |
Action | Examine the accompanying exception information and the information in the wsadmin.traceout file to determine the cause of the error. The server might not be running. |
Explanation | The AdminControl reconnect command completed successfully. |
Action | No action is required. |
Explanation | The wsadmin tool did not recognize the configuration ID that has been specified for an AdminConfig command. No closing parenthesis was found. |
Action | Specify a valid configuration ID using one of two forms: name(uri) or (uri). |
Explanation | The wsadmin tool did not recognize the configuration ID that has been specified for an AdminConfig command. No opening parenthesis was found. |
Action | Specify a valid configuration ID using one of two forms: name(uri) or (uri). |
Explanation | The wsadmin tool cannot process an attribute that has been specified on an AdminConfig command. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | An attribute name that has been specified for the given type is not valid. |
Action | Specify a valid attribute name. Run the AdminConfig attributes command for a list of valid attribute names. |
Explanation | The wsadmin tool could not initialize an enum attribute. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | When an object is created with AdminConfig, wsadmin determines what attribute name to use for the new object in the parent. In certain cases, the wsadmin tool cannot determine this information if the parent object contains more than one attribute of the type being created. |
Action | Use the AdminConfig create command that uses four parameters. As a fourth parameter, supply one of the attribute names supplied in this message. |
Explanation | The wsadmin tool cannot find the configuration object specified by an AdminConfig command. |
Action | Specify a valid configuration object. |
Explanation | No help is available for the argument that has been specified with the help <argument> command. |
Action | Verify that the argument is a valid argument for help. Reissue the "help" command without the argument for a list of valid options. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool could not run an AdminConfig parents command. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The value specified for an AdminConfig create or modify command attribute of some ENUM type is not a valid value. |
Action | Specify one of the valid values for the ENUM attribute. See the WASX7087E error message for the possible values. |
Explanation | An attribute specified by an AdminConfig create or modify command requires a numeric data type. |
Action | Specify a numeric value for the attribute. |
Explanation | This is an informational message logging that this command was invoked. |
Action | No action is required. |
Explanation | This is an informational message logging that this script was invoked. |
Action | No action is required. |
Explanation | This informational message is logged instead of WASX7090I if the command appears to contain a password. |
Action | No action is required. |
Explanation | This informational message is logged when the subject message is displayed to the user. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool displays this informational message in response to an AdminApp options command. |
Action | No action is required. |
Explanation | An AdminApp command is invoked in the local mode, but wsadmin cannot determine the installation root for WebSphere. |
Action | The wsadmin.bat or wsadmin.sh launcher should set the server.root property. If you modified this launcher, correct the changes. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | One or more options that were specified for an AdminApp or AdminConfig command is not valid. |
Action | Check the spelling of the options; correct or remove any incorrect options and reissue the command. |
Explanation | The data is not valid for an AdminApp install command for the specified task. |
Action | Examine the errors reported for this task and correct the install command. |
Explanation | The data is not complete for an AdminApp install command for the specified task. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | The data is not valid for an AdminApp install command for the specified task. The task consists of some number of items, but a different number has been supplied. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | =The data is not valid for an AdminApp install command for the specified task. The task consists of some number of items, some of which cannot be changed. The unchangeable items are a key for the data must exactly match the information included in an install command for this task. |
Action | Invoke the AdminApp taskInfo command for this file and task name to determine what information is needed for the task. |
Explanation | This informational message displays in response to an AdminApp options command. |
Action | No action is required. |
Explanation | The task name is not valid for the AdminApp taskInfo command that has been invoked. |
Action | Specify a valid task name as described in the WAS7113E message output. |
Explanation | The wsadmin tool cannot copy the ear file to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system, and that there are no file permission problems. |
Explanation | The wsadmin tool cannot read the ear file when preparing to copy it to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that the file path is correct and that there are no file permission problems. |
Explanation | The wsadmin tool cannot copy the ear file to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | The user requested to terminate an interactive scripting session, but configuration changes have not yet been saved. Commit the unsaved changes. |
Action | To exit the scripting session without saving your changes, respond with "quit" or "exit." Any other response keeps the session active. Use the AdminConfig save command to commit any unsaved changes. |
Explanation | The mode that has been specified with the AdminConfig setSaveMode command is not valid. |
Action | Specify a valid save mode. The valid options are "overwriteOnConflict" and "rollbackOnConflict". |
Explanation | The wsadmin tool created an exception. |
Action | Examine the exception information in the log file to determine the source of the problem. |
Explanation | The wsadmin tool found the specified string when '{' was expected in the input stream. |
Action | Correct and reissue the command. |
Explanation | The wsadmin tool did not find the specified string in the expected location in the input stream. |
Action | Correct and reissue the command. |
Explanation | The wsadmin tool found the specified character in an unexpected location in the input stream. |
Action | Correct and reissue the command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The parent that has been specified with the AdminConfig create command is not valid. |
Action | Specify a valid parent object for the object to create and reissue the command. |
Explanation | The wsadmin tool created an UnsupportedOperationException exception from an MBean. This exception might result from an AdminControl invoke command. |
Action | Check the spelling of the operation. |
Explanation | The wsadmin tool created a RuntimeMBeanException exception from an MBean. |
Action | Examine the exception information and modify the command. |
Explanation | An AdminApp install command did not run. |
Action | See previous messages for details. |
Explanation | An AdminApp uninstall command did not run. |
Action | See previous messages for details. |
Explanation | The -contextroot option must be specified for the AdminApp install command for invoking a war file. |
Action | Specify a valid value for the -contextroot option. |
Explanation | No operation was defined for the AdminControl invoke command that has been issued for an MBean operation. The MBean accepts the same number of parameters specified in the AdminControl invoke command. |
Action | Specify the correct number of parameters and reissue the invoke command. Use the "operations" command for the Help object to learn more about the signatures available for this operation. |
Explanation | A different number of parameters and signature elements have been specified for an AdminControl invoke command. There must be exactly one signature element for every parameter. |
Action | Specify exactly one signature element for every parameter and reissue the invoke command. Alternatively, reissue the command with no signature elements. |
Explanation | The trace string that has been specified for an AdminControl trace command is not valid. |
Action | Verify that the trace string is spelled correctly. |
Explanation | The wsadmin tool did not process the AdminConfig command because a configuration ID that has been specified does not correspond to an existing configuration object. |
Action | Verify that the id is spelled correctly. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool displays this informational message in response to the AdminConfig queryChanges command. The command lists the files that have been updated by the scripting client since the last save or reset command. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A value that has been specified for an AdminConfig command is not valid. |
Action | Specify a valid value for the AdminConfig command. |
Explanation | An informational message issued in response to invoking the AdminConfig setCrossDocumentValidationEnabled. |
Action | No action is required. |
Explanation | An informational message issued in response to invoking the AdminConfig setValidationLevel. |
Action | No action is required. |
Explanation | The wsadmin tool writes this informational message to the validation output file each time validation is requested. |
Action | No action is required. |
Explanation | Validation is complete. |
Action | Optional- Examine the messages logged in the specified file to see if corrective action is needed. |
Explanation | This message provides a summary of messages generated during configuration validation. |
Action | No action is required. |
Explanation | The user requested validation. By default, the name of the file is wsadmin.valout, located in the logs directory. |
Action | Fix any configuration problems noted by the previous message. |
Explanation | The wsadmin tool cannot open an output file for validation results. The file exists on your system, but the wsadmin tool cannot write to it. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | The wsadmin tool cannot open an output file for validation results. The wsadmin tool cannot create this file. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | No connection was obtained to the configuration service. |
Action | Restart the wsadmin tool to obtain a server connection. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | No connection was obtained to the application management service. |
Action | Restart the wsadmin tool to obtain a server connection, or use "-conntype NONE" option to run the local mode. |
Explanation | The wsadmin tool is initialized or validation settings have been changed. |
Action | No action is required. |
Explanation | The wsadmin tool has connected to a server during initialization. |
Action | No action is required. |
Explanation | The wsadmin tool cannot determine the type of server to which it is connected. |
Action | Examine the wsadmin.traceout file for additional information. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool could not connect to a server using the options supplied on the command line and contained in wsadmin.properties files. |
Action | If a connection is not needed, no action is necessary. Specify the "-conntype NONE" option to indicate that no connection is desired. This option suppresses the WASX7213I message. If a connection is needed, restart the wsadmin tool with connection information that will allow it to connect to a running server. Alternatively, verify that the host and port information is correct. |
Explanation | 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/ . |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The wsadmin tool needs the DataSourceCfgHelper MBean to perform the testConnection function. The MBean should be running in a server. |
Action | Verify that the wsadmin process is connected to a server and the server is running. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The AdminControl testConnection command was successfully run. The database adapter code reported no errors or warnings. |
Action | No action is required. |
Explanation | There is a constraint on the specified attribute. |
Action | Specify the missing attribute. |
Explanation | The "-local" option is not permitted for AdminApp functions when the scripting client is connected to a server. |
Action | Remove the "-local" option, or use the "-conntype NONE" option to avoid connecting to a server. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool cannot run the profile that has been specified is not in the same scripting language as the scripting session. |
Action | Remove the profile from the wsadmin.properties file or the wsadmin command line options. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminControl setAttribute command contains an attribute type that is not supported by the setAttribute command. |
Action | Use the setAttribute_jmx command to set this attribute. |
Explanation | The wsadmin tool did not invoke the AdminConfig modify or create command. |
Action | Examine the wsadmin.traceout log for more information. |
Explanation | If a scripting session begins with unsaved changes in the workspace, the workspace resets and the unsaved changes are lost. |
Action | No action is required. |
Explanation | No changes were made to the configuration by this scripting process since the last "save" or "reset" AdminConfig command. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool did not connect to a server process because it could not authenticate to the server. |
Action | Verify that user and password are correct on the command line or in a properties file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin launcher has been invoked with the -user option, but no user name argument was found. |
Action | Specify a user name for the -user option and reissue the wsadmin command. |
Explanation | The wsadmin launcher has been invoked with the -password option, but no password argument was found. |
Action | Specify a password for the -password option and reissue the wsadmin command. |
Explanation | The AdminControl stopServer command did not run because a running server of the specified name was not found. |
Action | Verify that the server name is spelled correctly. |
Explanation | The wsadmin tool is connected to the wrong type of process. |
Action | Verify that the wsadmin tool is connected to the correct process. |
Explanation | The AdminControl startServer command did not run because the server that has been specified does not exist. |
Action | Verify that the server name is spelled correctly. |
Explanation | The AdminControl startServer invocation did not run because the wsadmin tool cannot locate the NodeSync object on the specified node. |
Action | Examine the logs on the node if the NodeSync object is not running. |
Explanation | The AdminControl startServer command did not run because the NodeAgent on the server's node is not running. |
Action | Start the NodeAgent on the appropriate machine. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The specified server is started on the specified node. |
Action | No action is required. |
Explanation | The specified server process cannot start. The request has timed out. |
Action | Verify that the server is started. |
Explanation | The specified server is stopped on the specified node. |
Action | No action is required. |
Explanation | The specified server process cannot stop. The request has timed out. |
Action | Verify that the server is stopped. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The installInteractive or editInteractive AdminApp commands returns the previous string that can be modified and copied into a script for use with the install or edit commands. |
Action | If needed, use the command string in a script. |
Explanation | The AdminApp install command did not run because the specified application name already exists. |
Action | Use the -appname option to specify a different application name. |
Explanation | The AdminApp command did not run because the specified application does not exist. |
Action | Verify that the application name is spelled correctly. |
Explanation | The AdminApp command did not run because specified file cannot be used. |
Action | Verify that this file exists and is readable. |
Explanation | The AdminApp edit or editInteractive command did not run because specified application has no valid tasks to edit. |
Action | No action is required. |
Explanation | An AdminConfig command did not run because a required object must be a specific type. |
Action | Specify an object of the correct type and reinvoke the command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminConfig extract command did not run because the specified filename describes an existing file system entity that is not a file. |
Action | Verify that the specified name is not a directory name. Specify a valid file name and reissue the command. |
Explanation | The AdminConfig extract command did not write document data to the specified file. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | The AdminConfig command requires a connection to a deployment manager server. |
Action | Connect to a deployment manager server or do not invoke this AdminConfig command. |
Explanation | The wsadmin launcher has been invoked with the -wsadmin_class path option, but no class path argument was found. |
Action | Specify a class path for the -wsadmin_classpath option and reissue the wsadmin command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminApp taskInfo command did not obtain task information from the specified ear file. |
Action | Verify that the file exists and is readable, and that the task name is spelled correctly. |
Explanation | The AdminApp options command did not obtain task options from the specified ear file. |
Action | Verify that this file exists and is readable. |
Explanation | The wsadmin tool did not recognize some arguments as command line parameters. The wsadmin tool stores these arguments in the argv variable and are available to the script. The argc variable contains the number of arguments available in the argv variable. |
Action | Verify that the unrecognized arguments are arguments for scripts or commands to use. Correct or delete unrecognized options if necessary. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool cannot synchronize the configuration before startup because a node agent process is starting. |
Action | No action is required. |
Explanation | The wsadmin tool cannot determine the node for the specified DataSource that was specified by the AdminControl testConnection command. |
Action | Verify that the DataSource is correctly configured. |
Explanation | The AdminConfig create command cannot create this type of object. |
Action | Modify the create command. |
Explanation | The changes invoked by a script concluded were not saved. No configuration changes were saved. |
Action | Verify that the script uses the AdminConfig save command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool is initializing the dynamic scripting objects. |
Action | No action is required. |
Explanation | The wsadmin tool initialized the dynamic scripting objects. |
Action | No action is required. |
Explanation | A dynamic scripting object did not initialize. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The dynamic scripting objects did not initialize. |
Action | Use the AdminControl invoke and get/setAttribute(s) commands to interact with MBeans instead of dynamic scripting support. |
Explanation | An error has occurred during the initialization of the objects used by wsadmin. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | The wsadmin tool is using the startServer command to start a server. The configuration used by the starting server may not be the most recent configuration because the configuration has not be synchronized for this node. |
Action | If the configuration is incorrect, stop the server and invoke a configuration synchronization for this node. |
Explanation | The AdminControl startServer command did not run because the server is already started. |
Action | Verify that the correct server name is specified. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool cannot create a temporary directory for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | The wsadmin tool cannot copy an expanded ear directory to a temporary location for AdminApp processing. |
Action | Examine the wsadmin.traceout log file to determine the problem. Verify that there is enough space in the file system and that there are no file permission problems. |
Explanation | During the initialization of a scripting process, several properties files might load. Use this message to determine which properties files that are in use. |
Action | No action is required. |
Explanation | The list displays the was.policy security policy file associated with this application. |
Action | No action is required. |
Explanation | The AdminConfig showAttribute command only displays the value of a single attribute, but multiple attribute names were supplied. |
Action | Specify a single attribute name. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool created an exception because it could not determine if configuration changes have been made during the session. The connection to the server process might have broken before the scripting session was stopped. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A required option is missing for the AdminApp install command. |
Action | Specify each required option and reinvoke the command. |
Explanation | A request has been made to stop the specified server process. The scripting process will wait until the stop is complete or the action times out. In the first case, WASX7264I should be issued; in the second case, WASX7265W should be issued. |
Action | No action is required. |
Explanation | The AdminControl stopServer command did not run. |
Action | Examine the wsadmin.traceout file and the server log files to determine the source of the problem. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An interactive scripting session concluded without saving configuration changes. No configuration changes were saved. |
Action | Invoke the AdminConfig "save" command to save your configuration changes. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool cannot run the AdminControl startServer command because the node name that has been specified is not the same as the node name that is currently connected to by the node agent. |
Action | Verify that the node name is spelled correctly. |
Explanation | The wsadmin tool cannot run the AdminControl startServer command because the node name is not specified. |
Action | Specify the node name to locate the server in the startServer command. |
Explanation | The wsadmin tool cannot run the AdminControl startServer command because there is no node of the specified name in the configuration. |
Action | Verify that the node name is spelled correctly. |
Explanation | The wsadmin tool cannot run the AdminControl stopServer command because the node agent for the specified server is not located in the configuration. |
Action | Verify that the client is connected to the appropriate process type. |
Explanation | The specified option requires an accompanying argument. For example, if you specify the "-node" option, you must follow the "-node" option with the name of a node such as "-node mynode." |
Action | Specify an argument for the indicated option, or remove the option from the command. |
Explanation | The previous information results from an AdminApp taskInfo command and details the task information requested. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The value for the resource authorization field was not specified. |
Action | Enter "container" or "per connection factory" as the value of resource authorization. |
Explanation | The parents command does not support the specified object type. |
Action | No action is required. |
Explanation | The number of arguments supplied for the given command is not correct. |
Action | Review the help information and reissue the command with the correct number of arguments. |
Explanation | Specify attribute values that are collections of objects as a list of name-value pairs. An example of a collection consisting of two objects is: {{{attr1 val1a} {attr2 val2a}} {attr1 val1b} {attr2 val2b}}}. |
Action | Correct the syntax of the command to note the attribute as a collection. |
Explanation | Specify attribute values that are embedded objects as a list of name-value pairs. An example of an embedded object consisting of three attributes is: {{attr1 val1a} {attr2 val2a}}. |
Action | Correct the syntax of the command so that the embedded object is formatted as a list of name-value pairs. |
Explanation | The value supplied for the attribute is not valid. |
Action | Correct the syntax and reissue the command. |
Explanation | The argument passed to the startServer command is not valid. |
Action | Reissue the command with the correct value for the argument. |
Explanation | The wsadmin tool is not connected to a server process. A request was made with "-conntype NONE" option from the command line or specified in com.ws.scripting.connectionType property with NONE as the value in wsadmin.properties. |
Action | No action is required. |
Explanation | The wsadmin tool found one or more options that are not valid. |
Action | Check the spelling of the options. Correct or remove any incorrect options and reissue the command. |
Explanation | The value specified for the -reloadInterval option is not an integer. |
Action | Specify an integer argument for the -reloadInterval option and reissue the AdminApp command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | No required attributes were found for the specified type. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The Help message command cannot locate any message information for the specified message id. |
Action | Verify that the specified message id is correct. |
Explanation | The directory containing the help information does not exist. |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The system cannot register the bean provider specified in the extension xml file with the BSF. |
Action | Examine the exception in the trace log and correct the problem accordingly. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The system cannot find the implementation class provided in the extension xml file. |
Action | Verify that the implementation class in the extension xml file is correct and that the class is in the class path. |
Explanation | The system cannot instantiate the implementation class provided in the extension xml file. |
Action | Examine the exception in the trace log and correct the problem accordingly. Verify that the class provides a constructor with no argument. |
Explanation | The same implementation class is included in the extension xml file more than once. |
Action | Remove the duplicate implementation class from the extension xml file. |
Explanation | The extension xml file contains an element type reported in this warning message with required element type missing. |
Action | Add the missing element type reported in this message to the extension xml file. |
Explanation | The same element type is used more than once in the extension xml file. |
Action | Remove the extra element type in the extension xml file. |
Explanation | The reported element tag in the extension xml file is not supported. |
Action | Remove the unsupported element tag in the extension xml file. |
Explanation | A type handler registerd to handle the same type class is included in the extension xml more than once. |
Action | Remove the duplicate type handler in the extension xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An unsupported scripting language was specified. |
Action | Specify a supported scripting language with the -lang option or com.ibm.ws.scripting.defaultLang option. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A parser exception occured when getting the scripting extension. |
Action | Examine the exception in the trace log and correct the problem accordingly. |
Explanation | Version 5.1 and later supports the testConnection command. |
Action | Use the testConnectionToDataSource method in DataSourceCfgHelper MBean to test the connection of a DataSource that resides in a 5.0 server. |
Explanation | An error occured during invoking test connection to the provided data source. |
Action | Examine the exception in the trace log and correct the problem accordingly. |
Explanation | The wsadmin tool does not support this command. |
Action | Do not use this command. |
Explanation | The wsadmin tool does not support this command. |
Action | Do not use this command. |
Explanation | The application server attempts to prevent applications from performing security-sensitive operations such as: calling the System.exit() method, replacing the java 2 Security manager, and replacing the java 2 Security policy. If the application is granted the all permission (java.security.AllPermission), the java 2 Security permission checks are disabled. This compromises the integrity of the system. |
Action | Review the application policy that is located in the EAR/META-INF/was.policy file. Remove the security-sensitive permissions and grant the application only the permissions that are required. |
Explanation | The application server attempts to prevent applications from performing security-sensitive operations such as: calling the System.exit() method, replacing the java 2 Security manager, and replacing the java 2 Security policy. If the application is granted the all permission (java.security.AllPermission), the java 2 Security permission checks are disabled. This compromises the integrity of the system. |
Action | Review the application policy that is located in the EAR/META-INF/was.policy file. Remove the security-sensitive permissions and grant the application only the permissions that are required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The -lang and -internalLang options are specified. However, the values for the two options are not the same. |
Action | Specify either the -lang or -internalLang option. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Applications currently use the resource adapter specified in the uninstallResourceAdapter command. |
Action | Uninstall the applications listed in this error message before uninstalling the resource adapter. To force this uninstall action without uninstalling applications first, specify the -force option with uninstallResourceAdapter command. |
Explanation | J2CResourceAdapter objects currently use the resource adapter specified in the uninstallResourceAdapter command. |
Action | Uninstall the resource adapters listed in this error message before attempting to uninstall the specified resource adapter. To force this uninstall action without uninstalling the other resource adapters first, use the -force option with uninstallResourceAdapter command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | When security policy is set to use only FIPS approved cryptographic algorithms, no SSL configuration can use FIPS approved JSSE provider. |
Action | Examine the exception in the trace log and correct the problem accordingly. |
Explanation | You cannot use FIPS approved cryptographic algorithms if SSL provider is not IBMJSSEFIPS. |
Action | Examine the exception in the trace log and correct the problem accordingly. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminApp view command did not run because the application has no valid tasks to view. |
Action | This application is not editable. |
Explanation | The AdminApp view command did not run because the application viewable tasks are not valid. |
Action | Specify the correct task with the correct spelling. To list the valid task names, use the -tasknames option. |
Explanation | Removal of the node from the configuration will corrupt your configuration. |
Action | If you did not commit the change, run the AdminConfig reset command to restore the configuration to its initial state. |
Explanation | Removal of the node from the configuration requires some manual steps. This operation is not recommended. Alternatively, use the removeNode utility script. |
Action | If you did not commit the change, run the AdminConfig reset command to restore the configuration to its initial state. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool cannot recognize some options specified in the AdminApp command. |
Action | Verify that options provided in the message are correct. Reissue the AdminApp command if necessary. Otherwise, no action is required. |
Explanation | The value for the content type parameter is not valid. Valid values for this parameter are add, addupdate, delete, and update. |
Action | Reissue the update command with the correct content type value. |
Explanation | The value for the operation option is not valid. Valid values for this parameter are app, file, modulefile, and partialapp. |
Action | Reissue the update command with the correct operation value. |
Explanation | The option specified in this message is not required if the specified content type is provided in the update command. |
Action | No action is required. |
Explanation | The option specified in the message is not required if the specified operation is provided in the update command. |
Action | No action is required. |
Explanation | The missing option is required when the specified content type is provided in the update command. |
Action | Specify the missing option and reissue the update command. |
Explanation | The missing option is a required option if the specified content type and operation are provided in the update command. |
Action | Specify the missing option and reissue the update command. |
Explanation | The wsadmin tool did not run the AdminApp update command. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Use the contextroot option with the update command, the modulefile content type, and the update or addupdate operation. |
Action | For an update operation with a modulefile content type, the wsadmin tool ignores the contextroot option. For the addupdate operation with a modulefile the content type, the wsadmin tool ignores the contextroot option if the module exists. This message is for the informational purposes only. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Searching for JNDI references may take longer depending on how many applications installed on your system. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The options listed in this message are deprecated for the AdminApp command. The support for these options will be removed in a future release. |
Action | Determine if there is replacement option for the deprecated option. If so, use the replacement option. If there is no replacement option, you can exclude the deprecated option. |
Explanation | A string value representing a boolean is not entered as true or false. |
Action | Verify that the string value is correct and reissue the command. |
Explanation | To use any default binding option, specify the usedefaultbindings option. |
Action | Specify the usedefaultbindings option in the option string with the AdminApp install, installInteractive, update, or updateInteractive command. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool is connected to local mode. |
Action | Verify that the scripting client is connected to a server and that the server is running. |
Explanation | Use the terminate flag only to stop servers of the managed process type. |
Action | Verify that the server to stop is a managed process. |
Explanation | Specify the node name as one of the arguments. |
Action | Include the node name for the server in your arguments. |
Explanation | The wsadmin tool issued a request to stop the specified server process. The scripting process will not wait until the request succeeds. |
Action | Verify that the server stopped before continuing. |
Explanation | A parameter value is not valid. Do not specify parameter values as null or empty strings. |
Action | Reissue the AdminConfig command with the correct parameter value. |
Explanation | The wsadmin launcher did not run because no jobid argument was found for the -jobid option. |
Action | Specify a value for the -jobid option and reissue the wsadmin command. |
Explanation | The wsadmin launcher did not run because no logfile argument was found for the -tracefile option. |
Action | Specify a file path for the -tracefile option and reissue the wsadmin command. |
Explanation | The wsadmin launcher did not run because no argument was found for the -appendtrace option. |
Action | Specify a string value for the -appendtrace option and reissue the wsadmin command. |
Explanation | The wsadmin launcher did not run because the location that has been specified is not writable. |
Action | Specify a different location for the -tracefile option and reissue the wsadmin command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The parameter value for file permission is not valid. |
Action | Specify a file permission value with a valid string. |
Explanation | The AdminConfig object was specified, but the wsadmin process is not connected to a server with a running configuration service. |
Action | If the node agent of the target node is not running, start it and reissue the wsadmin command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Scripting client is connected admin subsystem and try to stop the admiagent server which is not supported. |
Action | If you want to stop adminagent server you need to do it from adminagent bin directory or if you are trying to stop admin subsystem you need to connect to adminagent server directly and use AdminAgent mbean to invoke stopProfile operation. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The AdminControl testConnection command was successfully run. The database adapter code reported no errors or warnings. |
Action | No action is required. |
Explanation | The AdminControl testConnection command was failed. See exception message and wsadmin.traceout file to find what is the problem |
Action | Find the problem from the log and try to resolve the problem and reissue the command. |
Explanation | The attribute will be reset is not specified. |
Action | Supply the attribute to be reset. |
Explanation | The attribute name will be unset is not specified. |
Action | Supply the attribute name to be unset. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A file, which has the same name as the specified output file name in exportFile command, exists in the local directory. |
Action | Rerun the exportFile command and specify a non-existent output file name. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purpose only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The wsadmin tool found the specified string when '[' was expected in the input stream. |
Action | Correct and reissue the command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The command name is not a valid administrative command. |
Action | Verify that the command name is correct. |
Explanation | The wsadmin tool cannot run the AdminTask help command. |
Action | Verify that the number of arguments, command name, or command group name is correct. Use the AdminTask help command to view a list of valid commands for the help option. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The command does not contain any step. |
Action | Verify that step name is spelled correctly or use help command to view detailed help for the command. |
Explanation | The command does not contain the specified parameter. |
Action | Verify that parameter name is spelled correctly or use help command to view detailed help for the command. |
Explanation | The specified language is not supported. |
Action | Specify a supported scripting language. |
Explanation | The wsadmin tool cannot connect to a server. |
Action | Reissue the wsadmin command to create a server connection. |
Explanation | The wsadmin tool cannot modify the data in the specified step. It is not enabled for the task. |
Action | Reissue the AdminTask command without the step option indicated in this error message. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | More than one set of data values was specified for the step and is not a table. |
Action | Provide one set of data values to the step indicated in this error message and reissue the AdminTask command. |
Explanation | Option value provided to the specified step is not valid. |
Action | Reissue the AdminTask command with the correct option value for step. |
Explanation | The AdminTask command contains an internal error. |
Action | Retry with scripting trace on and take a look wsadmin.traceout. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The AdminTask command contains an internal error. |
Action | Retry with scripting trace on and take a look wsadmin.traceout. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The option values for the specified step do not match the existing data. |
Action | Specify the correct option values for the step and reissue the AdminTask command. |
Explanation | The option values provided to the specified step are not complete. |
Action | Specify the correct number of key fields for the step and reissue the AdminTask command. |
Explanation | The specified parameter requires an accompanying argument. For example, if you specify "-node" you need to follow "-node" with the name of a node: "-node mynode." |
Action | Supply an argument for the indicated parameter. |
Explanation | The wsadmin tool is connecting to an incompatible version of the server or deployment manager node. |
Action | Verify that the server or deployment manager node has same or higher version as the wsadmin tool. Connect to a compatible server or deployment manager node. |
Explanation | The wsadmin tool is connecting to an incompatible server or deployment manager node. |
Action | Ensure that the wsadmin tool connect to the same or higher version of the server or deployment manager node. |
Explanation | The file is not uploaded for installation. |
Action | Ensure that this file exists and is readable. |
Explanation | The command pattern specified is not found, try different pattern. |
Action | Ensure that the searching pattern correctly. |
Explanation | The AdminConfig command cannot be run because the configuration service is not available. |
Action | Specify a server with a running configuration service and reissue the wsadmin command. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |
Explanation | There is a syntax error in a string provided in an attribute list |
Action | Correct the attribute list syntax. |