Explanation | An IOException or SAXException error is created when the file is read. |
Action | Ensure that the file exists and that it is usable. |
Explanation | An IOException is created when ServiceIndexWriter class writes to the file. |
Action | Ensure that the hard disk is not full and you have the writable permission. |
Explanation | The application name cannot be found. |
Action | Provide the correct application name. |
Explanation | The module cannot be found in the service package. |
Action | Provide the correct module name for the service package. |
Explanation | The Web services cannot be found in the module. |
Action | Ensure that the module has a Web service and that the service name is correct. |
Explanation | The specified logical endpoint cannot be found in the serivce. |
Action | Provide a logical endpoint name. |
Explanation | Multiple services index files were found when only one service index file is expected. |
Action | This is an internal error, no user action is required. |
Explanation | The services index file has no entry for a Web service. The file might not be usable. |
Action | If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product. |
Explanation | The services index file has no entry for a logical endpoint. The file might not be usable. |
Action | If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product. |
Explanation | The services index file has no operation for the endpoint. The file might not be usable. |
Action | If the file was manually modified, uninstall and reinstall the service. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product. |
Explanation | The file name must not contain slashes, directory or path name. |
Action | Provide the correct file name without the slashes, directory or path name. |
Explanation | The specified file name cannot be located in the configuration repository. |
Action | Provide the correct file name that can be found in the repository. |
Explanation | The version of the Feature Pack for Web Services that is installed on the deployment manager node must be at the same level or higher than the version that is installed on the node. |
Action | Install the same version or a higher version of the Feature Pack for Web Services on the deployment manager node before running the addNode command. |
Explanation | The Feature Pack for Web Services is not installed on the deployment manager node but has been installed on the managed node. |
Action | Install the same level or a higher version of the Feature Pack for Web Services on the deployment manager node before attempting to add the managed node. |
Explanation | The module contains JAX-WS Web Services and requires the Feature Pack for Web Services. To map a Web module from an application that requires feature pack functionality even though the Web server does not have feature pack functionality, define the Web server on a node with feature pack augmentation. |
Action | Install the Feature Pack for Web Services on the target node. |
Explanation | The Feature Pack for Web Services is installed on the deployment manager node but the managed node is prior to the WebSphere 6.1 level. |
Action | Install the same level of the Feature Pack for Web Services on the managed node or upgrade it to the WebSphere 6.1 level before attempting to add the managed node. |
Explanation | The specified asset name cannot be found. |
Action | Provide the correct asset name. |
Explanation | The parameters for the administrative command or MBean operation contain one or more not valid property names. |
Action | Provide the correct parameters. |
Explanation | The command parameters contain one or multiple not valid property values. |
Action | Provide the correct command parameters. |
Explanation | No more than one asset type is allowed in the query properties. |
Action | Provide no more than one asset type. |
Explanation | The logical endpoint name is required in the parameter for the specific MBean operation. |
Action | Provide the logical endpoint name in the parameter. |
Explanation | The query parameter should not be null. |
Action | Provide queryProps parameter. |
Explanation | Application name is required in the parameter. |
Action | Provide the application name in the parameter. |
Explanation | Module name is required in the parameter. |
Action | Provide the module name in the parameter. |
Explanation | Service name is required in the parameter. |
Action | Provide the service name in the parameter. |
Explanation | The service or endpoint listener is already started on the specific server. |
Action | No action is needed since the service listener is already started on the specific server. |
Explanation | The service or endpoint listener is already stopped on the specific server. |
Action | No action is needed since the endpoint listener is already stopped on the specific server. |
Explanation | Cannot start the service listener on a pre-7.0 server. |
Action | Start the asset that contains the service. |
Explanation | Cannot stop the service listener on a pre-7.0 server. |
Action | Stop the asset that contains the service. |
Explanation | Cannot start the service listener if the containing asset is not started. |
Action | Start the asset that contains the service. |
Explanation | The specified application module does not contain any web service. |
Action | Provide the correct application, module, and service name. |
Explanation | Cannot start the service listener if the server is not started. |
Action | Start the server that is the target for the service. |
Explanation | Node name is required in the target parameter. |
Action | Provide the node name in the target parameter. |
Explanation | Either server or cluster name is required in the target parameter. |
Action | Provide the server name or the cluster name in the target parameter. |
Explanation | The application is not installed on the specified server target or cluster target. |
Action | Provide the correct node name and server name for the target. |
Explanation | The specified MBean operation requires the application is running on a 7.0 server. |
Action | Make sure the application is installed on a 7.0 server and is started before invoking the operation. |
Explanation | The module cannot be found in the service package. |
Action | Provide the correct module name for the service package. |
Explanation | The extended status report data fro ma downstream server should be of EndpointStatusReportExtendedData type. |
Action | This is an internal error. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | Prior messages detail the cause of this failure. Typically, the error conditions include wrong server and node names that are specified as module targets during installation. |
Action | Read the error messages and rectify the problem. |
Explanation | An unexpected error occurred when saving the configuration documents of the application to the WebSphere repository during application installation. This message is preceded by a more detailed message regarding the failure. |
Action | Refer to the previous messages in the log file for a failure description. If no messages are displayed, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The number of router modules defined for the update EJB jar are not as same as the number found on the deployed EJB jar. |
Action | Provide the correct EJB jar for update or correct the binding file. |
Explanation | No HTTP router module is found within the update EJB jar binding while there is a HTTP router module defined in deployed EJB binding. |
Action | Provide the correct EJB jar for update or correct the bindings. |
Explanation | The binding has a new HTTP router module name than the one on deployed binding. |
Action | Provide the correct ejb jar for update or correct the bindings. |
Explanation | The update EJB jar bindings has an extra HTTP router module than the deployed EJB binding. |
Action | Provide the correct ejb jar for update or correc the bindings. |
Explanation | No JMS router module is found within update EJB jar binding while there is a JMS router module defined in deployed EJB binding. |
Action | Provide the correct EJB jar for update or correct the bindings. |
Explanation | The binding has a new JMS router module name than the one on deployed binding. |
Action | Provide the correct ejb jar for update or correct the bindings. |
Explanation | The update EJB jar bindings has an extra HTTP router module than the deployed EJB jar binding. |
Action | Provide the correct ejb jar for update or correct the bindings. |
Explanation | The binding file is missing from the update EJB jar. |
Action | Provide the correct ejb jar for update or correct the bindings. |
Explanation | The hash table does not contains the EJB JAR information from application installation operation. Error may be caused by using incorrect application or inputs parameters. |
Action | Check with the installation inputs or scripts or provide a correct application. |
Explanation | The hash table does not contains the server string for a particular key. Error may be caused by using incorrect application or inputs parameters. |
Action | Check with the installation inputs or scripts or provide a correct application. |
Explanation | The hash table does not contains the router module information. Error may be caused by using incorrect application or inputs parameters. |
Action | Check with the installation inputs or scripts or provide a correct application. |
Explanation | The hash table does not contains the server string for a particular key. Error may be caused by using incorrect inputs parameters or application. |
Action | Check with the installation inputs or scripts or provide a correct application. |
Explanation | The destinations of EJB JAR and its HTTP router WAR module are not the same. |
Action | Check with the installation inputs and scripts or provide a correct application. Sometimes, you may need to provide explicit server information for installation. |
Explanation | The hash table does not contains the server string for a particular key. Error may be caused by using incorrect inputs parameters of application. |
Action | Check with the installation inputs or scripts or provide a correct application. If all correct, contact IBM support. |
Explanation | The destinations of EJB JAR and its JMS router JAR module are not the same. |
Action | Check with the installation inputs and scripts or provide a correct application. Sometimes, you may need to provide explicit server information for installation. |
Explanation | The hash table does not contains the EJB JAR information from application installation operation. Error may be caused by using incorrect application or inputs parameters. |
Action | Check with the installation inputs or scripts or provide a correct application. |
Explanation | There is not matched name application or module deployed on the server. |
Action | Provide the correct module for update or check with the deployment inputs or scripts. |
Explanation | The update module has server target which is different than the server target of deployed module. EJB and its related router modules cannot have different server targets. |
Action | Provide the correct module for update, check the deployment inputs or scripts, or make sure EJB and its related router modules have the same server targets. |
Explanation | This could be either an user error or IBM internal error. |
Action | Provide the correct module for update or check with the deployment inputs or scripts. |
Explanation | Cannot find map modules to servers information from user inputs. |
Action | Add map modules to servers option with the deployment inputs or scripts. |
Explanation | This could be an user error or IBM WebSphere internal error. |
Action | Provide the correct module for update or chekc with the deployment inputs or scripts. |
Explanation | The module contains JAXWS Web Services that is required for the WebSphere 7.0 and later. |
Action | Install or upgrade the target node to WebSphere 7.0 and later. |
Explanation | The router modules found within the update EJB binding do not exist or cannot be found on the deployment target. |
Action | Include a router module within the application and redo the deployment. |
Explanation | The specified service cannot be found in the module. |
Action | Ensure that the module has a service and that the service name is correct. |
Explanation | The specified logical endpoint cannot be found in the serivce. |
Action | Ensure that the logical endpoint name is correct. |
Explanation | There is an exception when invoking the EndpointManager MBean operation on a server. |
Action | Check the JMX connection to the server is working. If working, this is an internal error. If not working, fix the JMX connection problem. |
Explanation | The target parameter can contain either server name or cluster name but not both. |
Action | Pass either server name or cluster name. You can invoke the operation twice, one for the server and one for the cluster. |
Explanation | Web service enabled EJB module should be greater than or equal to EJB 3.0. |
Action | Change or update the EJB to a 3.0-style EJB. |
Explanation | The module with partial or single file update has server target different than the server target of deployed module. EJB and its relted router modules cannot have different server targets. |
Action | Provide the correct module for update, check the deployment inputs or scripts, or make sure EJB and its related router modules have the same server targets. |
Explanation | This could be either an user error or IBM internal error. |
Action | Provide the correct file or partial application for update or check with the deployment inputs or scripts. |
Explanation | This could be either an user error or IBM internal error. |
Action | Provide value to map modules to server property for the file or partial application update. |
Explanation | Cannot obtain RepositoryContext. |
Action | Contact IBM technical support. |
Explanation | No target is found for updated module. |
Action | Contact IBM technical support. |
Explanation | Cannot obtain server target from deployed router module. |
Action | Contact IBM technical support. |
Explanation | The current user role does not have access to the resource. |
Action | Retry the command with a higher level user. |
Explanation | The application specific binding, which is defined in the specified application, requires WebSphere Application Server Version 7.0 or later. |
Action | Target the module to a node that is at WebSphere Application Server Version 7.0 or later. |
Explanation | The operation requires the asset in the started status and cannot be performed if the asset is in other status such as unknown, unavailable, partial start, or partial stopped. |
Action | Start the containing asset in order to perform the operation. |
Explanation | The operation requires the asset in the started status and cannot be performed if the asset is in other status such as unknown, unavailable, partial start, or partial stopped. |
Action | Start the containing asset in order to perform the operation. |
Explanation | The input parameter may contain wrong or missing package name, so zero or multiple ServiceIndexManager extensions are found matching the input parameter. |
Action | Specify the correct asset package names for the input parameter. |
Explanation | The asset is not installed on the specified server target or cluster target. |
Action | Provide the correct server target or cluster target. |
Explanation | This service does not support the operational control at the service or endpoint level. |
Action | Start the asset that contains the service. |
Explanation | This service does not support the operational control at the service or endpoint level. |
Action | Stop the asset that contains the service. |
Explanation | This service does not support the operational control at the service or endpoint level. Therefore, the MBean operation is not supported. |
Action | Do not invoke the MBean operation for the specified service. |
Explanation | A sub-string in the input parameter is not in the format of name=value. |
Action | Provide the input parameter in the format of name value pairs such as name1=value1,name2=value2. |