Explanation | A message-driven enterprise bean is in the application. The required listener port name for the message-driven enterprise bean does not have a value. |
Action | Specify the listener port value for the message-driven bean in the task that is listed in the error message. |
Explanation | A non-message-driven bean is in the application. The required JNDI name for the non-message-driven bean does not have a value. |
Action | Specify the JNDI name for the non-message-driven bean in the task that is listed in the error message. |
Explanation | A resource reference to an Oracle resource provider is in the application. The required isolation level for Oracle does not have a value. |
Action | Specify the isolation level for the resource reference in the task that is listed in the error message. |
Explanation | The application contains an Enterprise JavaBeans (EJB) 1.x. The data source JNDI name in both the module and the CMP bean level is not specified. You have to specify the JNDI name in at least one level. If you specify the data source JNDI name in the module level, then you do not have to specify the data source JNDI name for each CMP bean in that module unless you want to overwrite the one set in the module level. If you do not specify the data source JNDI name in the module level, then you have to specify it for each CMP bean in that module. |
Action | Specify the data source JNDI name in either the module or the CMP bean level. |
Explanation | The application contains a 2.x enterprise bean that has a resource authorization value for its data source. An incorrect value is specified for resource authorization. The correct value is either container or per application. |
Action | Specify the correct value for resource authorization in the module that is listed in the error message. |
Explanation | An unprotected method exists in the application. Valid values for an unprotected method for an EJB 1.x module include leaving the entry blank to keep the method as unprotected, or denying all access. Valid values for an unprotected method for an EJB 2.x module include uncheck, exclude, or a list of security role names. |
Action | Specify the correct protection value in the module and task that are listed in the error message. |
Explanation | Enterprise bean or resource references exist in the application. The JNDI name field that is required to bind the reference does not have a value. |
Action | Specify the JNDI name for the reference in the task that is listed in the error message. |
Explanation | A resource reference exists in the application. The hidden field that identifies this resource as an Oracle provider does not have a value. This field is filled in by the client, not by the user. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The application contains a Web module. The required field to specify the virtual host to install the Web module does not have a value. |
Action | Specify the virtual host for the Web module that is listed in the error message. |
Explanation | An error occurred setting up the tasks for the application. |
Action | Verify that the installation task objects, if provided by the task provider, are set up correctly. |
Explanation | An error occurred setting up the tasks for the application. |
Action | Verify that the installation task object, if provided by the task provider, is set up correctly. |
Explanation | A validation error occurred in preparing the application. This message is followed by a detailed error message. |
Action | See the detailed messages for instructions on how to correct the problem. |
Explanation | An error occurred in the task preparing the application. |
Action | Enter the data again in the task preparing the application. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The application name passed in to the edit functions such as getApplicationInfo, getModuleInfo, exportApplication, and extractDDL is null. |
Action | If this error occurs when you use the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. If you are using these functions programmatically, make sure that the application name is not null. |
Explanation | The application name that is supplied in edit functions such as getApplicationInfo, getModuleInfo, exportApplication, and extractDDL is not an installed application name. |
Action | If this error occurs when you use the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. If you are using these functions programmatically, make sure that the application with the given name is installed. |
Explanation | For the listModules or extractDDL functions, the application management logic cannot obtain the EAR file that is stored in the WebSphere Application Server configuration. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while copying the EAR file to the configuration repository. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while compiling JSP files in a Web application archive (WAR) file. |
Action | Verify that the JSP files do not have any code that does not compile. |
Explanation | An error occurred in the Correct Oracle Isolation Level task while preparing the application. |
Action | Validate your application using the Application Server Toolkit. |
Explanation | An error occurred in preparing the application. The value to specify the isolation level for the Oracle resource provider is incorrect. Valid values are 2 (for transaction read committed) or 7 (for transaction serializable). |
Action | Enter the correct value for the isolation level field in the resource reference that is specified in the error message. |
Explanation | An error occurred in preparing the application. The value to specify the isolation level for the Oracle resource provider is incorrect. Valid values are 2 (for transaction read committed) or 7 (for transaction serializable). |
Action | Enter the correct value for the isolation level field. |
Explanation | An error occurred in preparing the application. The data source for a container-managed persistence (CMP) bean is not specified. |
Action | Specify the data source for the CMP bean that is specified in the error message. |
Explanation | An error occurred in preparing the application. The data source for a 1.x container-managed persistence (CMP) bean has incomplete data. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred in preparing the application. The resource authorization value for a container-managed persistence (CMP) bean is not specified correctly. The correct values include per application or container. |
Action | Enter the correct value for the resource authorization in the CMP bean that is specified in the error message. |
Explanation | An error occurred in preparing the application. The connection factory for a 2.x CMP bean has incomplete data. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred in preparing the application. The security role name that is entered does not exist. |
Action | Specify an existing security role name. |
Explanation | An error occurred in preparing the application. The specified server string has an incorrect format. The correct format is "WebSphere:cell=<cell>,node=<node>,server=<server>" and "WebSphere:cell=<cell>,cluster=<cluster>" for server and cluster respectively. |
Action | Specify the correct server string. |
Explanation | An error occurred in the Mapping users to roles task, while preparing the application. |
Action | If the problem persists, validate your application using the Application Server Toolkit. |
Explanation | An error occurred in the Selecting method protections for unprotected methods task, while preparing the application. |
Action | If the problem persists, validate your application using Application Server Toolkit. |
Explanation | An error occurred in the Selecting method protections for unprotected methods task, while preparing the application. |
Action | If the problem persists, validate your application using the Application Server Toolkit. |
Explanation | An error occurred in the Selecting method protections for unprotected methods task while preparing the application. |
Action | If the problem persists, validate your application using the Application Server Toolkit. |
Explanation | An error occurred in the Selecting method protections for unprotected methods task while preparing the application. |
Action | If the problem persists, validate your application using the Application Server Toolkit. |
Explanation | The EAR file path that is supplied to the installApplication API for the AppManagement MBean is null. |
Action | Verify that the EAR path is not null if this API is called programmatically. If this error is displayed by the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The properties table supplied to the installApplication API for the AppManagement MBean is null. |
Action | Verify that the properties table is not null if this API is called programmatically. If this error is displayed by the wsadmin tool or the UI, then see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The enterprise archive (EAR) file path that is provided to the installApplication API for the AppManagement MBean does not contain a file. |
Action | Verify that the file exists at the specified location. If this error is displayed by the wsadmin tool or the UI, then see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected exception occured during installation. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | The application name that passed to the checkIfAppExists or the uninstallApplication APIs of the AppManagement MBean is null. |
Action | If these APIs are called programmatically, verify that the name is not null; otherwise, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The properties table that passes to the uninstallApplication API of the AppManagement MBean cannot be null. |
Action | If this API is called programmatically, make sure that the properties table is not null. |
Explanation | An unexpected exception occurred when uninstalling the application. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | The module parameter that passes to the getModuleInfo API of the AppManagement MBean is not valid. |
Action | Make sure that the module parameter is a string that has a value of moduleURI+ddURI. If this error is displayed by the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception occurs when the unique module URI that passes into the AppManagement MBean for the getApplicationInfo or the getModuleInfo APIs does not match a module in the enterprise archive (EAR) file. The unique URI is moduleURI+ddURI |
Action | If the getApplicationInfo or the getModuleInfo API on the AppManagement MBean is called programmatically, verify that the parameter passed in is correct. If this error is displayed using the wsadmin tool or the administration client UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The RunAsBinding element in the applications bindings file (ibm-application-bnd.xmi) references a security role element in the application deployment descriptor (application.xml) that does not exist. |
Action | Verify that the security role exists in the application deployment descriptor file. |
Explanation | This exception occurs during application installation processing if the enterprise archive (EAR) file gets locked because of an unexpected error, and cannot be closed. Application installation is stopped when this error occurs. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | An unexpected exception occured in checking the existence of the application during application uninstallation so the uninstallation is not proceeding. This problem can also occur if the application to uninstall does not exist in the configuration. |
Action | Verify that the application name that is supplied to the uninstall action is correct. |
Explanation | This exception occurs when a task that is scheduled to perform one of the application installation activities cannot be instantiated. Installation is halted as a result of this exception. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | An error occurred in preparing the application. The default data source for a Java archive (JAR) file is not specified. |
Action | Specify the default data source for the JAR file that is specified in the error message. |
Explanation | An error occurred in preparing the application. The default data source for a Java archive (JAR) file has incomplete data. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred in preparing the application. The resource authorization value for a Java archive (JAR) file is not specified correctly. The correct values are per application or container. |
Action | Enter the correct value for the resource authorization in the JAR file that is specified in the error message. |
Explanation | An error occurred in preparing the application. The default connection factory for a Java archive (JAR) file contains incomplete data. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected exception occurred while deleting the entry for the deployed application from the serverindex.xml file of the node on which the application is installed. The application might not be uninstalled successfully. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | This exception occurs when the properties table that passes to the installApplication API of the AppManagement MBean specifies that the EJBDeploy program that runs as a part of an installation does not specify options for the EJBDeploy program. |
Action | If the installApplication API is called programmatically, verify that the hash table for EJBDeploy options is passed in as one of the entries in the properties table. If this exception is displayed by the wsadmin tool or the administration client UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A previous message from the application installation details the error that occurred during the EJBDeploy program. |
Action | Verify that the enterprise bean Java archive (JAR) file that is assembled with the application is a valid and deployable JAR file. |
Explanation | An unexpected exception occurred during EAR file expansion. |
Action | Verify that enough disk space is available for the EAR file to extract completely, and that the proper file permissions are set to both the temp directory and the directory that is specified as the installation destination. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An unexpected exception occurred saving the information that passed in during the editing of an existing application. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
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 WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The application contains a runAs system identity, which can optionally change to a RunAs role. You specified to change a RunAs system identity to an existing RunAs role. However, the specified user mapping data for the existing RunAs role does not match the existing data in the Mapping roles to user task. |
Action | Make sure that the RunAs role that you switch to has the same user ID and password data as specified in the Mapping roles to user task. |
Explanation | The application contains a runAs system identity that can optionally change to a RunAs role. An error occurred when trying to get the RunAs role task. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The application contains a RunAs system identity, which can optionally change to a RunAs role. You specified to change a RunAs system identity to a non-existing RunAs role. However, this non-existing RunAs role is used in more than one RunAs system identity, and does not have the matching user mapping data. |
Action | Make sure that the same user mapping data (user ID and password) is entered for the same RunAs role name. |
Explanation | An error occurred while searching for the filter policy in the configuration. Security filtering is not performed. |
Action | No user action is required if no security concerns exist. Otherwise, validate your configuration. |
Explanation | An error occurred while performing security policy filtering. Security filtering is not performed. |
Action | No user action is required if no security concerns exist. Otherwise, validate your configuration. |
Explanation | WebSphere Application Server attempts to prevent applications from performing security-sensitive operations, like 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 permissions (java.security.AllPermission), the Java 2 Security permission checks are effectively disabled, which can compromise the integrity of the system. |
Action | Review the application policy, which is located in the EAR/META-INF/was.policy file, remove the security-sensitive permissions and grant the application the permissions that are required only. |
Explanation | The implementation of custom permissions can weaken the integrity of the Java 2 Security permission check. |
Action | Review both the application policy, which is located in the EAR/META-INF/was.policy file, and the implementation of custom permissions. |
Explanation | The application contains a 2.x enterprise bean. The data source JNDI name and resource authorization in both the module and the container-managed persistence (CMP) bean level are not specified. You must specify the data in at least one level. If you specify the data source data in the module level, then you do not have to specify it for each CMP bean in that module unless you want to overwrite the one set in the module level. If you do not specify the data source data in the module level, then you have to specify it for each CMP bean in that module. |
Action | Specify the data source JNDI name and resource authorization in either the module or the CMP bean level. |
Explanation | Valid values for the com.ibm.websphere.management.application.client.jspReloadEnabled custom property include true or false. Any other value is not valid. When a value is not valid, the product uses the default behavior, which is to set the reloadEnabled JavaServer Pages (JSP) attribute value to true. |
Action | Edit the com.ibm.websphere.management.application.client.jspReloadEnabled custom property to have a value of true or false. |
Explanation | An unexpected exception occurred when saving the changes made during application installation, uninstallation, or editing. The changes might not be saved correctly. This exception is displayed only when application management functions are invoked programmatically. This error is not typically encountered during use of the wsadmin tool (except when the -local option is used) or the administration client UI. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | An error occurred when deleting a file or a directory. |
Action | Verify that the disk is not write-protected. If not, manually delete the file or directory that is mentioned in the error message. |
Explanation | An unexpected exception occurred in getting the AppDeploymentTaskInfo object for a given AppDeployment task. If you see this message while testing an application installation extension, make sure that all of the classes related to the extension display in the class path. |
Action | Consult the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | A template policy file is included in your 1.2.x application. |
Action | No user action is required if no security concerns exist. Otherwise, modify the was.policy file in the location that is specified in the warning message about setting up a security permission. For syntax of the was.policy file, refer to the dynamic policy section of the information center. |
Explanation | The policy file is missing from your 1.2.x application. |
Action | No user action is required if security is not enabled. Otherwise, include a was.policy file in your application before reinstalling the application. |
Explanation | Typically, this error is displayed when a J2EE 1.2 application enterprise archive (EAR) file contains a J2EE 1.3 module. |
Action | Verify that the EAR file is a J2EE-compliant EAR file. |
Explanation | The application specified is not a valid EAR file. |
Action | Verify that the correct application file is entered. Otherwise, validate your application using the Application Server Toolkit. |
Explanation | The specified application file is not a valid JAR or WAR file. |
Action | Verify that the correct application file is entered. |
Explanation | The specified application name contains an unacceptable character. An application name cannot begin with a leading dot, cannot contain leading or trailing spaces and cannot contain any of the following characters: backward slash (\), slash (/), number sign (#), dollar ($), at sign (@), $colon (:), asterisk (*), question mark (?), quotation marks ("), greater than sign (>), less than sign (<), pipe (|), semicolon (;), or comma (,), equal sign (=), plus (+), percent (%), ampersand (&), single quotation mark (') square brackets (]]). |
Action | Specify an application name that does not contain any of these unacceptable characters. |
Explanation | This message is written into the log file when an EJBDeploy error is encountered. |
Action | Examine the error message and the previous messages from the EJBDeploy program, to determine the source of the problem. |
Explanation | This message is written into the log file when an EJBDeploy warning is encountered. |
Action | Examine the warning message and the previous messages from the EJBDeploy program, to determine whether any corrective action is necessary. |
Explanation | Some of the application management functions can be called only if the AppManagement MBean runs in local mode, that is without connecting to a Java Management Extentions (JMX) process. |
Action | If this API is called programmatically, make sure that the AppManagementProxy object is created using the getLocalProxy method. |
Explanation | If the AppManagement MBean is a node agent or application server, then the AppManagement MBean is not activated by default. |
Action | If this installation is a base WebSphere Application Server installation or a deployment manager process, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Some of the application management functions can be called only if the AppManagement MBean runs in JMX mode; that is, the client must be connected to a server. |
Action | If this API is called programmatically, make sure that the AppManagementProxy object is created either using the getJMXProxyForClient or the getJMXProxyForServer method. |
Explanation | This error typically occurs when the bindings or extensions of an application or module have cross references to deployment descriptor artifacts, and those cross referenced IDs are not present in the deployment descriptor. This situation is most common when bindings or extensions are manually edited. |
Action | Edit the resource URI mentioned in the exception and fix the cross references. |
Explanation | An unexpected exception occurred while preparing the specified task. |
Action | See server machine FFDC for more information. Check the enterprise archive (EAR) file if the binding information is correct. |
Explanation | An unexpected exception occurred while completing the specified task. |
Action | See server machine FFDC for more information. Check the enterprise archive (EAR) file if the binding information is correct. |
Explanation | The user applications cannot be installed or updated without a full WebSphere Application Server license. |
Action | Do not call the application management APIs that update applications in this installation environment. |
Explanation | The current backend ID that is specified in the ibm-ejb-jar-bnd.xmi file does not exist under the META-INF/backends directory. |
Action | Verify that the current backend ID (currentBackendId) that is specified in the ibm-ejb-jar-bnd.xmi file is correct. Look for a correct ID under the META-INF/backends directory of the specified Java archive (JAR) file. |
Explanation | A full WebSphere Application Server product installation is not available, or is corrupted. |
Action | No user action is required if you have an embedded WebSphere Application Server installation. |
Explanation | A full WebSphere Application Server product installation is not available to perform all of the application management functions. |
Action | No user action is required if you have an embedded WebSphere Application Server installation. |
Explanation | The current backend ID that is specified in the ibm-ejb-jar-bnd.xmi file does not exist under the META-INF/backends directory. |
Action | Specify the correct CurrentBackendId value in the ibm-ejb-jar-bnd.xmi file. |
Explanation | A message-driven enterprise bean exists in the application. The required listener port name or the JNDI name for the message-driven enterprise bean does not have a value. |
Action | Specify the listener port or the JNDI name for the message-driven enterprise bean in the task that is listed in the error message. |
Explanation | A connector module (resource archive, or RAR, file) is embedded in the application. The required JNDI name for the connector does not have a value. |
Action | Specify the JNDI name for the connector in the task that is listed in the error message. |
Explanation | The exception message might contain the reason for this problem. |
Action | Specify an integer within the valid range. |
Explanation | The specified entry is not found in the ra.xml file. |
Action | Add the specified entry to the ra.xml file. |
Explanation | The specified entry must be unique in the ra.xml file. |
Action | Modify the ra.xml file so that the specified entry is used only once. |
Explanation | Review the exception information to determine the cause of the error. |
Action | No user action is required. |
Explanation | A previous message from the application installation program contains more detail about this error. |
Action | Make sure that the shared library Java archive (JAR) file contains the libraryName object. |
Explanation | An attempt to get a workspace failed. |
Action | Verify what is passed in as a workspace ID. |
Explanation | The type of J2EE application is not supported on the node. |
Action | Make sure that the J2EE application type is correct for the deployment target. |
Explanation | This type of J2EE application contains a later version of resource adapter archives that is not supported. |
Action | Verify that the connector modules or the RAR version is correct for the application. |
Explanation | An unexpected exception occurred. Review the exception information. |
Action | No user action is required. |
Explanation | This type of application is not supported on the nodes. |
Action | Verify that the J2EE application type is correct for the deployment target. |
Explanation | This type of application contains deployment options that are not supported on the nodes. |
Action | Verify that the J2EE application type is correct for the deployment target. |
Explanation | The required column does not have a value. |
Action | Specify the required column in the task that is listed in the error message. |
Explanation | The resource is not found on the deployment target. |
Action | Make sure that the resource JNDI name is correct for the resource. |
Explanation | The resource is not found on the deployment target. |
Action | Make sure that the resource JNDI name is correct for the resource. |
Explanation | An unexpected exception occurred. |
Action | No user action is required. |
Explanation | An unexpected exception occured. |
Action | No user action is required. |
Explanation | The node MBean is not found for application stop. |
Action | No user action is required. |
Explanation | An unexpected error occurred while getting the node objects in the cell. |
Action | Review and investigate the original exception. |
Explanation | An unexpected error occurred while getting the servers in the specified node. |
Action | Review and investigate the original exception. |
Explanation | An unexpected error occurred while getting the clusters in the specified cell. |
Action | Review and investigate the original exception. |
Explanation | An unexpected error occurred while getting the specified application scopes. |
Action | Review and investigate the original exception. |
Explanation | An unexpected error occurred while getting the attribute of the specified object. |
Action | Review and investigate the original exception. |
Explanation | An unexpected error occurred while getting the Library object from the specified application deplyment.xml file. |
Action | Review and investigate the original exception. |
Explanation | System application installation and uninstallation needs a cell, node, and server name. |
Action | Pass cell.name in the hashtable to the AppManagement API. |
Explanation | System application installation and uninstallation needs a cell, node, and server name. |
Action | Pass node.name in the hashtable to the AppManagement API. |
Explanation | System application installation and uninstallation needs a cell,node, and server name. |
Action | Pass server.name in the hashtable to the AppManagement API. |
Explanation | The cell name is picked up either from the module-to-server mapping or from the cell.name property. |
Action | Pass cell.name in the hashtable of properties to the installApplication API. |
Explanation | MSG0001 |
Action | 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 content type can be file, module, partialapp or app. |
Action | Change the content type that passes to the updateApplication API. |
Explanation | The content path is null in the updateApplication API. |
Action | Specify the pathToContents value in the updateApplication API. |
Explanation | The operation type is not valid in the updateApplication API. |
Action | Specify a valid operation type: add, addupdate, update, or delete. |
Explanation | MSG0001 |
Action | Specify the content URI and path to content in the updateApplication API. |
Explanation | MSG0001 |
Action | Verify that the content path is correct. |
Explanation | MSG0001 |
Action | Verify that the content URI is specified. |
Explanation | MSG0001 |
Action | Use modulefile as the content type for updating an application and use add or delete as the operation. |
Explanation | A syntax error exists in the ejb-jar.xml file. |
Action | Modify the syntax of <resource-env-ref-type> of the specified name in the ejb-jar.xml file. |
Explanation | The resource is found on the deployment target, but of the wrong resource type. |
Action | Verify that the resource type is correct for the resource. |
Explanation | The resource is found on the deployment target, but with the wrong resource type. |
Action | Verify that the resource type is correct for the resource. |
Explanation | The specified application edition contains an unacceptable character. An application edition cannot contain leading or trailing spaces and cannot contain any of the following characters: backward slash (\), slash (/), number sign (#), dollar ($), at sign (@), $colon (:), asterisk (*), question mark (?), quotation marks ("), greater than sign (>), less than sign (<), pipe (|), semicolon (;), or comma (,), equal sign (=), plus (+), percent (%), ampersand (&), single quotation mark (') square brackets (]]). |
Action | Specify an application edition that contains acceptable characters. |
Explanation | The specified application edition cannot be uninstalled because it is the active edition on the specified deployment targets. |
Action | Activate another edition of this application to deactivate the edition that you are trying to uninstall. |
Explanation | The archive file is already closed. |
Action | No user action is required. |
Explanation | An unexpected exception occurred while checking if the enterprise bean Java archive (JAR) file deployed. |
Action | No user action is required. |
Explanation | This application cannot be exported, edited, or updated. |
Action | This operation is not accepted. |
Explanation | Because the application was installed using the zero binary copy option, it is not possible to perform any operation on this application that involves accessing the application metadata or EAR file. The only possible operation is uninstall. |
Action | This operation is not accepted for the specified application. |
Explanation | Because the application was installed using the zero ear copy option, it is not possible to perform any operation on this application that involves accessing the EAR file. |
Action | This operation is not accepted for the specified application. |
Explanation | Because the application was installed using the zero ear copy option, it is not possible to perform any operation on this application that involves accessing the EAR file. |
Action | This operation is not accepted for the specified application. |
Explanation | An error occured while running the deployment step. |
Action | Check any error logs that are specific to the step. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This deployment step is not successful. |
Action | Check any error logs that are specfic to the step. |
Explanation | This informational message indicates the program status. |
Action | No user action is required |
Explanation | This informational message indicates the program status. |
Action | No user action is required |
Explanation | The EAR wrapper extension is successful. |
Action | No user action is required |
Explanation | An EAR wrapper extension was found to wrap the module to the EAR file. |
Action | No user action is required |
Explanation | This error occurs when a non-J2EE type artifact and extensions are installed to wrap the module to an EAR file before application deployment can be found or did not run successfully. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message is written into the log file when an DeployEJBTask is run. |
Action | Examine the informational message and the previous messages from the DeployEJBTask, to determine whether any corrective action is necessary. |
Explanation | More than one Web module is installed with the same root context, same node and same host. The same Web archive (WAR) module might be installed more than once. |
Action | Verify that you are not installing the same WAR file to the same host. |
Explanation | The target scope must be "WebSphere:cell=myCell,node=myNode", "WebSphere:cell=myCell,node=myNode,server=myServer" or "WebSphere:cell=myCell,cluster=myCluster". |
Action | Correct the syntax of the target. |
Explanation | The resource is not found on the deployment target. |
Action | Verify that the resource Java Naming and Directory Interface (JNDI) name is correct for the resource. |
Explanation | The resource is not found on the deployment target. |
Action | Make sure that the resource Java Naming and Directory Interface (JNDI) name is correct for the resource. |
Explanation | The call to initialize the resource validation is not performed. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The systemapps.xml file did not load. |
Action | Verify that the cell name and node name are correct. |
Explanation | The specified content does not exist. |
Action | Verify that the content path is correct. |
Explanation | The file that is specified by the URL already exists in the application. The specified operation cannot be performed. |
Action | Verify that the specified URL is correct or that the operation is correct. Use update instead of add. |
Explanation | The file that is specified by the URL does not exist in the application. The specified operation cannot be performed. |
Action | Verify that the specified URL is correct or that the operation is correct. |
Explanation | The specified module is the last module in the application. WebSphere Application Server cannot remove all of the modules from the application. |
Action | No user action is required. |
Explanation | Parameter validation failed. |
Action | Review the original exception and confirm that the passed parameter is correct. |
Explanation | The user does not have proper role assigned to manage the specified application. |
Action | Please confirm if the user has proper administratiove role. |
Explanation | The user does not have proper role assigned to manage the specified target. |
Action | Please confirm if the user has proper administratiove role. |
Explanation | The user does not have proper role assigned to manage the specified resource. |
Action | Please confirm if the user has proper administratiove role. |
Explanation | If the application is installed using zero binary copy or zero EAR copy (with use binary config) then EAR file of the application is not in WebSphere repository. Therefore, such EAR can not be modified. |
Action | Install the application without zero binary or zero ear copy. |
Explanation | User provided incorrect format or invalid regular expression pattern for filepermission |
Action | Check filepermission and pattern again for valid format or valid regular expression pattern. |
Explanation | Some of the action to install the application could not be performed because fo the lack of previlege. |
Action | Please confirm that there is enough priviledge to perform the installation of the application. |
Explanation | Application installation had failed with unknown exception. |
Action | Please investigate the exception. |
Explanation | Some of the action to checkthe existance of the application could not be performed because fo the lack of previlege. |
Action | Please confirm that there is enough priviledge to perform the checking of the existance of the application. |
Explanation | Checking of the existance of Application had failed with unknown exception. |
Action | Please investigate the exception. |
Explanation | Some of the action to compare the security policy could not be performed because fo the lack of previlege. |
Action | Please confirm that there is enough priviledge to perform the compare the security policy. |
Explanation | Comparing security policy had failed with unknown exception. |
Action | Please investigate the exception. |
Explanation | The specified jndi name of the message destination ref does not match withe the jndi name that is linked by the message destination. |
Action | This is an information. Please confirm the jndi name is correct. |
Explanation | The file requested to be deleted is a deployment descriptor file which cannot be deleted. |
Action | Check that you have specified the correct file to be deleted. If there is a mistake in the deleted file name, rerun the update with the correct file to be deleted. |
Explanation | The specified target server does not exist. |
Action | Verify that the target name is valid. Look for typographical errors. |
Explanation | An update application operation failed, and the configuration session state could not be restored. Saving the session might result in an inconsistent configuration. |
Action | Discard the configuration changes in the current session. |
Explanation | An uninstall application operation failed, and the configuration session state could not be restored. Saving the session might result in an inconsistent configuration. |
Action | Discard the configuration changes in the current session. |
Explanation | The user does not have proper role assigned to install or redeploy the the application to specified targets. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | The user does not have proper role assigned to uninstall the specified target. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | The user does not have proper role assigned to update the specified target. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | The user does not have proper role assigned to access the specified application. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | The user does not have proper role assigned to access the specified resource. |
Action | Please confirm if the user has proper administratiove role described in the error message. |
Explanation | The user does not have proper role assigned to access the specified resource. |
Action | Please confirm if the user has proper administratiove role described in the error message. |
Explanation | The user does not have proper role assigned to manage the specified target. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | The user does not have proper role assigned to operate the specified application. |
Action | Please confirm if the user has proper administratiove role described in the message. |
Explanation | Value for an Environment Entry is missing. Missing entries will be ignored during runtime, with a warning. |
Action | Deployer needs to provide the corresponding values to EAR, before deployment. |
Explanation | exception was trown while loading the specified deployment descriptor. |
Action | Please examine the specified Deployment descriptor. |
Explanation | An archive file in a deployed application cannot be opened. The file URI that is specified in the error message might resolve to a file that is not an archive file in the deployed application. The archive file also might be corrupted. |
Action | Verify that the contents of the files that are used to update the application are consistent with the application archive that is being updated. Also, make sure that the deployed application archive is not corrupted. |
Explanation | Autolink support is only available for applications that contain an EJB 3.0 module. |
Action | Disable autolink support and rerun the same operation. |
Explanation | To use autolink for an EJB reference, each module in the application must share at least one common target. |
Action | Specify a common target for each module or disable the autolink option. Then, rerun the same operation. |
Explanation | NONE |
Action | No user action is required. |
Explanation | One of the required arguments for the EARExpander command is missing. The required arguments are ear, operationDir, and operation. |
Action | Rerun the EARExpander command with the missing argument and its value. |
Explanation | The specified EAR file is not valid. If you are performing an expand operation, the file does not exist, does not have read permission, or is not in the correct EAR format. If you are performing a collapse operation, the specified file is an existing file. |
Action | Rerun the EARExpander command with the correct EAR file specified. |
Explanation | The specified operation directory is not valid. If you are performing a collapse operation, the specified directory does not exist, is not a directory, or the files in it are not in the correct EAR file format. If you are performing an expand operation, the specified directory is an existing file. |
Action | Rerun the EARExpander command with the correct operation directory specified. |
Explanation | Check the command-line arguments to the EARExpander command. |
Action | Type EARExpander without any parameters to see command-line help. |
Explanation | This informational message indicates that the EARExpander command is expanding an enterprise archive (EAR) file. |
Action | No user action is required. |
Explanation | This informational message indicates that the EARExpander command is collapsing a directory to an EAR file. |
Action | No user action is required. |
Explanation | A value is not specified for the required argument of the EARExpander command. |
Action | Rerun the EARExpander command with a specified value for the required argument. |
Explanation | The expansion flag value that is specified is not valid. The default value, All, is used instead. |
Action | No user action is required if your intention is to expand the entire enterprise archive (EAR) file. Otherwise, rerun the EARExpander command and specify war, as the expansion flag. |
Explanation | Specify either the listener port and the JNDI name for the message-driven enterprise bean, but not both of them. |
Action | Specify either the listener port or the JNDI name for the message-driven enterprise bean in the listed task. |
Explanation | A message destination reference exists in the application. The JNDI name field that is required to bind the reference does not have a value. |
Action | Specify the JNDI name for the reference in the task that is listed in the error message. |
Explanation | The JNDI name must have a value because an enterprise bean exists in the application. |
Action | Specify the JNDI name for the message-driven enterprise bean in the task that is listed in the error message. |
Explanation | The EAR file might contain files that are not valid or access has been denied to create or read the files. |
Action | Use the -verbose option with the EARExpander command to get a stack trace for the exception. |
Explanation | The EAR file might contain files that are not valid or access has been denied to create or read the files. |
Action | Use the -verbose option with the EARExpander command to get a stack trace for the exception. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | As part of the application installation, the application enterprise archive (EAR) file is saved in the WebSphere Application Server configuration repository. This error message is displayed during installation if the enterprise archive (EAR) file cannot be saved. |
Action | Verify that enough disk space is available to save the EAR file, and check the file permissions. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The JavaServer Pages (JSP) files in the Web archive (WAR) modules of the enterprise archive (EAR) file have compilation errors. |
Action | Use the Application Server Toolkit to compile the JSP files and check for compilation errors. |
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 | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This message indicates that the EJBDeploy command failed during application installation. Prior messages detail the cause of this failure. |
Action | Use the Application Server Toolkit to run the EJBDeploy command on the enterprise archive (EAR) file before installing it, and remove the causes of the EJBDeploy failures. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The disk might be full or might be write-protected. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | Prior messages detail the cause of this failure. |
Action | Read the previous message to rectify the problem. |
Explanation | The application name must be unique in the WebSphere Application Server configuration. |
Action | Install the application with a different name. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The specified application name contains an unacceptable character. An application name cannot begin with a leading dot and cannot contain any of the following characters: slash (/) (\), (:) colon, asterisk (*), question mark (?), quotation marks ", > (greater than sign), less than sign <, pipe |, semicolon (;), or comma (,). |
Action | Specify an application name that contains acceptable characters. |
Explanation | A target that is specified for a module during application installation is not valid. |
Action | Verify that the specified target server exists. |
Explanation | A target that is specified for a module during application installation is not valid. |
Action | Verify that the specified target cluster exists. |
Explanation | Typically this error occurs when a server name is specified as a target for the module of the application without specifying the node name. If multiple servers exist with the same name, then the value is treated as an ambiguous definition. |
Action | Specify the parent name, for example, a node name if a server is specified. |
Explanation | An application module cannot be installed on a server that is a member of a cluster, without specifying the cluster as a target. |
Action | Specify the cluster as a target. |
Explanation | The javax.management.ObjectName instance has domain:key=value format. The domain name for the application management function in WebSphere Application Server is WebSphere. |
Action | Correct the ObjectName format. |
Explanation | The target server or cluster that is specified for a module in the application installation does not exist. The target server name is specified as WebSphere:cell=cellName,node=nodeName,server=serverName. The target cluster name is specified as WebSphere:cell=cellName,cluster=clusterName. |
Action | Verify that the target name is valid. Look for typographical errors. |
Explanation | The cluster with the given name does not exist. |
Action | Correct the cluster name. Check for typographical errors. |
Explanation | The server with the given name does not exist under the given node. |
Action | Correct the server name. Look for typographical errors. |
Explanation | The cluster.xml file for the cluster lists a cluster member that does not exist. The cluster configuration might not be valid. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The deployment.xml file for the given deployment is empty or not valid. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The document is corrupt or empty. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The same target that is specified multiple times for the same module is treated as a single target. |
Action | Remove the duplicates from the target name. |
Explanation | A module cannot be installed on a cluster member without also specifying the cluster as a target. |
Action | Specify the cluster as a module target also. |
Explanation | The server name is not valid. |
Action | Make sure that the server exists. |
Explanation | The copy made of the session manager settings is not of type SessionManager. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The previous message details the cause of this problem. |
Action | Read the previous message to understand the probable cause. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The node name that passed in as a parameter to the removeAllAppsFromNode API cannot be null. |
Action | If the removeAllAppsFromNode API on the AppManagement MBean is called programmatically, then make sure that the node name that is passed in is not null. If the addNode utility displays this exception, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The node name is not valid. |
Action | Specify the correct node name. |
Explanation | The serverindex.xml file for the given node is incorrect. |
Action | Note the steps to recreate the problem and see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The application has a module that is deployed on the servers or clusters that do not exist. The application is uninstalled, but if the targets do exist, the serverindex.xml file for the nodes of these targets is not updated. |
Action | If the targets that are specified in the message exist in the WebSphere Application Server configuration, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message describes the program status. |
Action | No user action is required. |
Explanation | This informational message describes the program status. |
Action | No user action is required. |
Explanation | The application does not exist. |
Action | Check the application name. Look for typographical errors. |
Explanation | The application does not have a module, and the cell name is not passed as a parameter to the installApplication API of the AppManagement MBean. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The cell name is not valid. |
Action | Check the cell name. Look for typographical errors. |
Explanation | The cell name is needed to uniquely identify the application. |
Action | If this API is called programmatically, make sure that the cell name is passed in through the properties table (key= AppConstants.APPDEPL_CELLNAME). |
Explanation | After application installation, the EAR file is stored in the WebSphere Application Server configuration. This error message is displayed when the EAR file cannot be located in the WAS_HOME/config/cells/cellName/applications/appName.ear/ directory. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The value for the reload interval must be a long value. |
Action | Make sure that the specified reload interval is a numeric long value. |
Explanation | The value for the class loader policy must be specified using the constants that are defined in the AppConstants class. |
Action | Verify that the class loader policy has one of the predefined values. |
Explanation | The value for the class loading mode must be specified using the constants that are defined in the AppConstants class. |
Action | Make sure that the class loading mode has one of the predefined values. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This message indicates that the InstalledOptionalPackage installation task failed during application installation. Prior messages detail the cause of this failure. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | No resource JNDI table is created. Need to call gatherJNDINames first. |
Action | Make sure that the gatherJNDINames is called first. |
Explanation | A problem occured getting the existing deployment resource. |
Action | Edit the application to restore any previous deployment settings. |
Explanation | Recycle option does not match input. |
Action | Review and investigate the error messages. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | See the exception for causes of the error. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | See messages for cause of error. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | Prior messages detail the cause of this failure. |
Action | Read the previous message to rectify the problem. |
Explanation | See message for the cause of the error. |
Action | Save the log files and report the problem. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | An error occurred in preparing the application. The specified shared library string has an incorrect format. The correct format is: standalone library name or "WebSphere:name=<LibraryName>,isSharedClassloader=<true/false>". Use "+" to specify multiple library names. |
Action | Specify the correct shared library string. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The uninstall procedure failed to delete the application configuration data successfully. The application is still uninstalled. |
Action | See the problem determination information at the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The application is listed in the serverindex.xml file for each node on which every module is deployed. This message indicates that an unexpected error occurred while deleting the application entry from the serverindex.xml file during application uninstallation. |
Action | See the problem determination information at the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | An unexpected exception occured during installation. |
Action | Read the previous error messages for details. |
Explanation | An application name does not exist. |
Action | Make sure that the application name is correct. |
Explanation | While attempting to delete edition properties for the specified application, the indicate exception occurred. |
Action | See the problem determination information at the IBM WebSphere Application Server Support Web site at: http://www.ibm.com/software/webservers/appserv/support.html |
Explanation | This information message indicates the program status. |
Action | No user action is required. |
Explanation | Deployment.xml file does not exist |
Action | Make sure the deployment.xml file exists |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message might detail a probable cause. |
Action | If an application enterprise archive (EAR) file is not expanded to the destination that is specified during installation, use the EARExpander tool to expand the EAR file. |
Explanation | The entry for deployedApplication in the serverindex.xml file is bad. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message might detail a probable cause. |
Action | If an application enterprise archive (EAR) file is not expanded to the destination that is specified during installation, use the EARExpander tool to expand the EAR file. |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The disk might be full, or the directory might not have write permission. |
Action | Use the EARExpander tool to extract the EAR file. |
Explanation | The exception message might detail a probable cause. |
Action | Delete the directory manually. |
Explanation | The exception message might detail a probable cause. |
Action | 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 exception message might detail a probable cause. |
Action | 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 exception message might detail a probable cause. |
Action | 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 | To enable the Cluster ripple option, enable the Distribute binaries option as well. |
Action | Enable Distribute binaries if the Cluster ripple option is required. |
Explanation | The Cluster ripple option cannot be specified when target cluster is on nodes that have auto-sync enabled. |
Action | Enable the Distribute binaries option if the Cluster ripple option is required. |
Explanation | The exception message might detail the probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The exception message may detail probable cause. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Received an unexpected repository event type. |
Action | No user action is required. |
Explanation | The delta.xml file is malformed. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Missing data in the application binary synchronization process. |
Action | If an application EAR file is not expanded to the destination that is specified during installation, then use the EARExpander tool to expand the EAR file. Consult the IBM WebSphere Application Server Support website available at: http://www.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Explanation | Application update changes might not be sychronized, recycle behavior might be unexpected. |
Action | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This informational message indicates the distribution status of the application. |
Action | No user action is required. |
Explanation | An unexpected failure occurred during application distribution. Application distribution tasks will not be executed. |
Action | See FFDC for more information. |
Explanation | An unexpected failure occurred during the execution of an application distribution task. Subsequent application distribution tasks will not be executed. |
Action | See FFDC for more information. |
Explanation | An unexpected failure occurred during the execution of an application distribution task. Subsequent application distribution tasks will not be executed. |
Action | See FFDC for more information. |
Explanation | The exception message might detail a probable cause. |
Action | Specify an integer within the valid range. |
Explanation | The disk might be full, or the directory might not have write permission. |
Action | Correct the cause of the failure, and either resync the node or use the EARExpander tool to extract the EAR file. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | An unexpected exception occured during cluster update. |
Action | Read previous error messages for further details. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The Cluster ripple option requires that Synchronize changes with Nodes be selected. |
Action | If you want to use the Cluster ripple option, select Synchronize changes with nodes. |
Explanation | Resources that are assigned to application are beyond deployment target scope. |
Action | Click cancel to return to the previous step and correct Java Naming and Directory Interface (JNDI) assignments, or continue to move on. |
Explanation | Resources that are assigned to application are beyond deployment target scope. |
Action | Click Cancel to return to the previous step and correct JNDI assignments, because Validate install option FAIL is chosen, you cannot continue beyond this step. |
Explanation | One or more applications failed to start during application ripple on the server that is displayed in the message. |
Action | Check the logs for reason of failure. |
Explanation | The application names that are supplied are not targeted on any servers. The application name might be incorrect. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The application failed to expand to the destination for the installed enterprise archive (EAR) file. |
Action | For more information about the failure, see the node agent error log. The default path for the error log is profile_root/logs/nodeagent/SystemErr.log. |
Explanation | The application did not expand within the expected amount of time because the expansion process might be in-progress. |
Action | Consider increasing the wait time for application expansion. Use the com.ibm.websphere.management.application.updatesync.appExpansionTimeout system property to increase the wait time for the deployment manager. For more information on this property, see the product documentation.. |
Explanation | If the servers are not intend to start, the application expansion process will occur as a background process. |
Action | No action is required. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The destination directory for the external binding file must be part of the application. |
Action | Make sure that the destination directory for the binding file is specified in the EAR file. |
Explanation | The external binding file cannot be found. |
Action | Verify that the binding file is available on the file system. |