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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | No user information was specified for the security role. |
Action | Specify a valid user for the listed task in the error message. |
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 unexpected exception occurred when saving the changes made during an application management operation to the configuration repository. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | The application name passed in to the edit functions such as getApplicationInfo, getModuleInfo, exportApplication, and extractDDL is null. |
Action | If you are using these functions programmatically, make sure that the application name is not null. |
Explanation | The application name that is supplied in start or stop function is not an installed application name. |
Action | If you are using these functions programmatically, make sure that the application with the given name is installed. |
Explanation | The specified database vendor type is not supported. |
Action | Specify a supported database vendor type. |
Explanation | For the listModules or extractDDL functions, the application management logic cannot obtain the EAR file that is stored in the Application Server configuration. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred while copying the EAR file to the configuration repository. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred while compiling JSP files in a Web 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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | The specified database access type is not supported. |
Action | Specify a supported database access type. |
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 specified JDK compliance level is not supported. |
Action | Specify a supported JDK compliance level. |
Explanation | The deploy EJB task could not find an EAR, EJB JAR, or WAR (with EJBs) file to process. |
Action | Verify the options specified for the deploy EJB task. |
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. |
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. |
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. |
Explanation | An unexpected exception occurred during installation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | The RunAsBinding element in the applications bindings file (ibm-application-bnd.xmi or ibm-application-bnd.xml file for EE5) 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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected exception occurred 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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The "filename" parameter passed to the exportApplication function must be a valid file path name. |
Action | Specify a non-empty file path name. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A previous message from the application installation details the error that occurred during the EJBDeploy program. |
Action | Verify that the EJB archive file that is assembled with the application is a valid and deployable JAR file. |
Explanation | An unexpected exception occurred during EJB deployment. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | An unexpected exception occurred saving the information that passed in during the editing of an existing application. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | 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 policy file META-INF/was.policy included with the application contains custom permissions listed in the warning message. The implementation of custom permissions can weaken the integrity of the Java 2 Security permission check. |
Action | Verify that the custom permissions listed in the message are intended and update the file META-INF/was.policy in the application, if necessary. |
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 | 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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: backward slash (\), slash (/), comma (,), number sign (#), dollar ($), at sign (@), colon (:), semicolon (;), quotation mark ("), asterisk (*), question mark (?), greater than sign (>), less than sign (<), pipe (|), equal sign (=), plus (+), ampersand (&), percent (%), or single quotation mark ('). |
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 this message and any 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 this message and any 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 the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 warning 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 | Check the server's First Failure Data Capture (FFDC) tool for more information. Verify that the binding information for the enterprise archive (EAR) file is correct. |
Explanation | An unexpected exception occurred while completing the specified task. |
Action | Check the server's First Failure Data Capture (FFDC) tool for more information. Verify that the binding information for the enterprise archive (EAR) file 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 | This message is written into the log file when an EJBDeploy informational message is encountered. |
Action | Examine this message and any previous messages from the EJBDeploy program, to determine whether any corrective action is necessary. |
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 occurred. |
Action | No user action is required. |
Explanation | The ApplicationManager MBean for the specified server could not be found. The target server probably is not running. |
Action | If you are trying to start an application, start the specified server and reissue the start command. If you are trying to stop an application, the application is probably already stopped on specified server because that server is not running. No further action is required to process the stop operation. |
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 | The deployment.xml file cannot be retrieved. |
Action | Verify the deployment.xml file can be reached. |
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 | For this operation to complete successfully, you will need to specify both the content URI and the path to content. |
Action | Specify the content URI and path to content in the updateApplication API. |
Explanation | The content does not exist at the specified path. |
Action | Verify that the content path is correct. |
Explanation | For this operation to complete successfully, the content URI must be specified for file or modulefile delete. |
Action | Verify that the content URI is specified. |
Explanation | When updating an application, use modulefile as the content type and add or delete as the operation. |
Action | Use modulefile as the content type for updating an application and use add or delete as the operation. |
Explanation | The indicated JNDI resource element does not specify a type. A type is required when no injection targets are specified. |
Action | Specify a type or injection targets for the indicated JNDI resource element. |
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 (/), comma (,), number sign (#), dollar ($), at sign (@), colon (:), semicolon (;), quotation mark ("), asterisk (*), question mark (?), greater than sign (>), less than sign (<), pipe (|), equal sign (=), plus (+), ampersand (&), percent (%), single quotation mark ('), or 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 | This type of application is not supported on the nodes when autolink is enabled. |
Action | Verify that the Java Platform, Enterprise Edition application type is correct for the deployment target. |
Explanation | To deploy a client module, the deployment target must be version 8.0 or above. |
Action | Verify that the deployment target is version 8.0 or above. |
Explanation | An error occurred 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This message is written into the log file when the 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. 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 | Confirm that the user has the proper administrative role. |
Explanation | The user does not have proper role assigned to manage the specified target. |
Action | Confirm that the user has the proper administrative role. |
Explanation | The user does not have proper role assigned to manage the specified resource. |
Action | Confirm that the user has the proper administrative role. |
Explanation | If the application is installed using zero binary copy or zero EAR copy (with use binary configuration) then EAR file of the application is not in WebSphere repository. Therefore, such an EAR cannot be modified. |
Action | Install the application without zero binary or zero ear copy. |
Explanation | User provided incorrect format or a regular expression pattern that is not valid for filepermission. |
Action | Check filepermission and pattern again for valid format or valid regular expression pattern. |
Explanation | User provided incorrect AysncRequestDispatchType, valid types are DISABLED, SERVER_SIDE, or CLIENT_SIDE. |
Action | Provide a valid AsyncRequestDispatchType. |
Explanation | Some of the actions to install the application could not be performed due to a lack of privilege. |
Action | Confirm that there is enough privilege to perform the installation of the application. |
Explanation | Application installation had failed with unknown exception. |
Action | Investigate the exception. |
Explanation | Some of the action to check the existence of the application could not be performed because of the lack of privilege. |
Action | Confirm that the user has the correct privileges to perform the checking of the existence of the application. |
Explanation | Checking of the existence of Application had failed with unknown exception. |
Action | Investigate the exception. |
Explanation | Some of the action to compare the security policy could not be performed because of the lack of privilege. |
Action | Confirm that there is enough privilege to perform the compare the security policy. |
Explanation | Comparing security policy had failed with unknown exception. |
Action | Investigate the exception. |
Explanation | The JNDI name of the indicated message destination reference does not match the JNDI name that is linked by the message destination. |
Action | Confirm that the JNDI names are 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 | Confirm that the user has the proper administrative role described in the message. |
Explanation | The user does not have a proper role assigned to uninstall the specified target. |
Action | Confirm that the user has the proper administrative role as described in the message. |
Explanation | The user does not have a proper role assigned to update the specified target. |
Action | Confirm that the user has the proper administrative role as described in the message. |
Explanation | The user does not have a proper role assigned to access the specified application. |
Action | Confirm that the user has the proper administrative role described in the message. |
Explanation | The user does not have a proper role assigned to access the specified resource. |
Action | Confirm that the user has the proper administrative role described in the message. |
Explanation | The user does not a have proper role assigned to access the specified resource. |
Action | Confirm that the user has the proper administrative role described in the error message. |
Explanation | The user does not have a proper role assigned to manage the specified target. |
Action | Confirm that the user has the proper administrative role described in the message. |
Explanation | The user does not have a proper role assigned to operate the specified application. |
Action | Confirm that the user has the proper administrative role described in the message. |
Explanation | The indicated environment entry does not specify a type. A type is required when no injection targets are specified. |
Action | Specify a type or injection targets for the indicated environment entry. |
Explanation | The indicated environment entry does not have a value. A value is required when no injection targets are specified. Environment entries without a value will be ignored (with a warning) during runtime. |
Action | Specify a value or injection targets for the indicated environment entry. |
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 | 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 | Activation Plan defines dependencies of Java Platform, Enterprise Edition application modules on WebSphere runtime components. An unexpected error occurred while deducing this dependency. |
Action | No user action is needed. |
Explanation | To use asset and composition unit shared libraries in Java Platform, Enterprise Edition applications, the target node must be at least a 7.0 version. |
Action | Rerun the operation and either do not specify shared library from the asset and composition unit shared library task or choose a target of at least 7.0 version to deploy each module. |
Explanation | Unresolved enterprise bean references exist in the application. The type field that is required to bind the reference must have a value of either local or remote. |
Action | Specify either local or remote as the value for the EJB reference type in the task that is listed in the error message. |
Explanation | Unresolved resource references exist in the application. The type field that is required to bind the reference resource does not have a value. |
Action | Specify the type for the indicated resource reference in the application. |
Explanation | Non system applications are not allowed to install on Admin Agent or JobManager server type. |
Action | Specify application server type for deployment targets. |
Explanation | A non-message-driven bean is in the application. You cannot specify JNDI names for both the bean and its local/remote home. If JNDI for the bean is specified, you cannot specify JNDI for its local/remote home and its local/remote business interface(s). |
Action | Specify either the JNDI name for the non-message-driven bean or JNDI name for its local/remote home in the task that is listed in the error message. |
Explanation | A non-message-driven bean is in the application. You cannot specify JNDI names for both the bean and its business interface. If JNDI for the bean is specified, you cannot specify JNDI for its local/remote home and its local/remote business interface(s). |
Action | Specify either the JNDI name for the non-message-driven bean or JNDI name for its business interface in the tasks that are listed in the error message. |
Explanation | This error occurs when a module has a version that is associated with Java Enterprise Edition (Java EE) 5 or later and the module has IBM bindings and extensions files in an older XMI format. Module versions that are specific to Java EE 5 are 2.5 for Web archive (WAR) files and 3.0 for Enterprise JavaBeans (EJB) Java archive (JAR) files. When a module has a Java EE 5 or later specific version, the bindings and extensions files of that module must not use the old XMI format. Instead, the bindings and extensions files of the module must use the new XML format. IBM bindings and extensions files in the older XMI format have a .xmi file extension. IBM bindings and extensions files in the new XML format have a .xml file extension. |
Action | Either revert the module version to a pre-Java EE 5 value or remove the bindings and extensions files from the module. Important: Do not rename the bindings and extensions files to change the file extension from .xmi to .xml. Note: The error is specific to individual modules. When you fix this problem, only update the specific modules that are exhibiting the problem. If you remove the bindings and extensions files, the files can be regenerated using the application deployment process. Also, you can regenerate the bindings and extensions files using application development tools. |
Explanation | This error occurs when an EAR has a version that is associated with Java Enterprise Edition (Java EE) 5 or later and the EAR has IBM bindings and extensions files in an older XMI format. When an EAR has a Java EE 5 or later specific version, the bindings and extensions files must not use the old XMI format. Instead, the bindings and extensions files must use the new XML format. IBM bindings and extensions files in the older XMI format have a .xmi file extension. IBM bindings and extensions files in the new XML format have a .xml file extension. |
Action | Either revert the application version to a pre-Java EE 5 value or remove the bindings and extensions files. Important: Do not rename the bindings and extensions files to change the file extension from .xmi to .xml. If you remove the bindings and extensions files, the files can be regenerated using the application deployment process. Also, you can regenerate the bindings and extensions files using application development tools. |
Explanation | CMP and BMP Entity beans are not supported in EJB 3.0 or later EJB modules. |
Action | Package all CMP and BMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application. |
Explanation | The extended data source properties must be specified as one or more name=value pairs separated by a "+". |
Action | Correct the extended data source property listed in the error message. |
Explanation | System application EAR files must be expanded into a directory for installation. The EAR file itself cannot be used for installation. |
Action | Expand the system application EAR file before you install it. |
Explanation | The presence of both xmi and xml format bindings or extensions files at the application level is not supported. |
Action | Provide either an xmi or an xml format bindings or extensions file at the application level in the EAR. |
Explanation | EJB deployment was not performed because either the application does not contain any EJB modules or no EJB deploy options were specified. |
Action | If this message is unexpected, verify the contents of the application or check the options specified; otherwise, remove the deploy enterprise bean option. |
Explanation | JSP compiliation was not performed because the application does not contain any WAR modules. |
Action | If this message is unexpected, verify the contents of the application; otherwise, remove the precompile JavaServer Pages files option. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | One or more JSP files did not compile due to complication errors. |
Action | Use the Application Server Toolkit to compile the JSP files and check for compilation errors. |
Explanation | The JSP reload interval for the indicated web module is not valid. The JSP reload interval must be a positive integer. |
Action | Specify a valid value for the JSP reload interval. |
Explanation | The indicated environment entry does not specify a type. A type is required when no injection targets are specified. |
Action | Specify a type or injection targets for the indicated environment entry. |
Explanation | A value for the indicated environment entry must be specified. |
Action | Specify a value for the indicated environment entry. |
Explanation | The value specified for the indicated environment entry is not valid. |
Action | Specify a valid value for the indicated environment entry. |
Explanation | The indicated environment entry does not specify a type. A type is required when no injection targets are specified. |
Action | Specify a type or injection targets for the indicated environment entry. |
Explanation | A value for the indicated environment entry must be specified. |
Action | Specify a value for the indicated environment entry. |
Explanation | The value specified for the indicated environment entry is not valid. |
Action | Specify a valid value for the indicated environment entry. |
Explanation | The property-based configuration applyConfigProperties command failed with the indicated result. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while applying the property-based configuration file (META-INF/ibm-was-config.props) to the application. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The deployed applications for this cluster require an Enterprise JavaBeans (EJB) specification level that this node does not support. |
Action | Verify that the node supports the Java EE application type required by the applications currently deployed on this cluster. |
Explanation | The deployed applications for this cluster require a Servlet specification level that this node does not support. |
Action | Verify that the node supports the Java EE application type required by the applications currently deployed on this cluster. |
Explanation | Binding data for the EJB does not exist. |
Action | Fix the binding for the EJB in the tool that was used to create it or edit the application. |
Explanation | There was an error that occurred when querying for the running applications on the server and node specified. |
Action | Check the FFDC logs for the error. |
Explanation | Found a marker file that indicates a binary expansion failure and expansion needs to be retried. |
Action | No action is required. |
Explanation | For some reason there was a problem setting the file permissions for the file. |
Action | Check the FFDC logs for the error. |
Explanation | The deployed applications for this cluster require a Connector specification level that this node does not support. |
Action | Verify that the node supports the Java EE application type required by the applications currently deployed on this cluster. |
Explanation | The deployed applications for this cluster require a Servlet specification level that this node does not support. |
Action | Verify that the node supports the Java EE application type required by the applications currently deployed on this cluster. |
Explanation | It is an error for an environment entry value and lookup name to be specified for a given environment entry element. |
Action | Specify either an environment entry value or lookup name but not both for the indicated environment entry. |
Explanation | It is an error for a lookup name and EJB link to be specified for a given EJB reference element. |
Action | Specify either a look up name or EJB link but not both for the indicated EJB reference. |
Explanation | The file that is specified by the URL is not a valid J2EE type artifact. The specified operation cannot be performed. |
Action | Verify that the specified URL is correct or that the content type is correct. |
Explanation | The deploy EJB task does not execute on EJBs in WAR files. |
Action | No action is required. |
Explanation | The deploy EJB task could not find an EJB JAR file to process. |
Action | No action is required. |
Explanation | EJB content within a web module is not recognized on an HTTP server. |
Action | Target the web module to at least 1 application server and remove targeting of this module to any web server. |
Explanation | EJB content within a web module is not recognized on an HTTP server. |
Action | Target the web module to at least 1 application server and remove targeting of this module to any web server. |
Explanation | The <initialize-in-order> option specified in the application deployment descriptor was set to true but the order of the modules listed in the application deployment descriptor conflicts with the order of the dependencies between EJB's in the application. In order to use the <initialize-in-order> option, a module cannot be dependent on a module that is positioned after it in the module list in the application deployment descriptor. |
Action | To use the <initialize-in-order> option, the order of the EJB dependencies between the modules must be consistent with the order of the modules listed in the application deployment descriptor. |
Explanation | If a web module contains EJB and the same reference is used in both the web module and the EJB, the JNDI name specified must be the same for both references. |
Action | Specify identical target JNDI name for identical reference to resolve the conflict. |
Explanation | If an EE5 or newer application is found to have both an xmi and xml bindings and/or both xmi and xml extensions file, the xmi file will be removed from the application when it is opened. |
Action | None. |
Explanation | An invalid value is specified for client mode option. |
Action | Provide a correct value for client mode option. |
Explanation | EJB deployment cannot be executed because the EJBDeploy feature is not installed in the environment. |
Action | If this message is unexpected, verify the contents of the application includes ejb class files or check the options specified; otherwise, remove the deploy enterprise bean option. |
Explanation | The indicated environment entry does not specify a type. A type is required when no injection targets are specified. |
Action | Specify a type or injection targets for the indicated environment entry. |
Explanation | A value for the indicated environment entry must be specified. |
Action | Specify a value for the indicated environment entry. |
Explanation | The value specified for the indicated environment entry is not valid. |
Action | Specify a valid value for the indicated environment entry. |
Explanation | Extended datasource property is specified, but the property is ignored as there is no extended datasource property support in the specified module. |
Action | No action is required. |
Explanation | An unexpected exception occurred during application management command processing. |
Action | Examine the exception cause message, if one is displayed, for additional information. |
Explanation | The application management command was not able to locate the EAR file for the specified application. |
Action | Verify that the application deployment contains a proper EAR file. Make sure that the deployed application archive is not corrupted. |
Explanation | An exception occurred while storing the results of SQLJ processing to the enterprise archive (EAR) file in the workspace. The EAR file modifications were not saved. The SQLJ processing may have created or changed corresponding packages in the database. |
Action | Retry the application management command. |
Explanation | An exception occurred while opening or reading an input file. |
Action | If the file was not found, verify that the file name is correct. |
Explanation | During SQLJ processing a duplicate profile name was found. |
Action | Check the input list of profile names for duplicate names. |
Explanation | An exception occurred while opening or writing a temporary output file. |
Action | Examine the linked exception for the cause. |
Explanation | The SQLJ operation encountered a problem. This informational message indicates the program status. Prior messages in the command output give details of the problem. |
Action | Check the command output for the cause of the problem. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | The pureQuery bind operation encountered a problem. This informational message indicates the program status. Prior messages in the command output give details of the problem. |
Action | Check the command output for the cause of the problem. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | This is a summary of the results from bind processing for the file. |
Action | No user action is required when the result is what you expected. If you suspect a problem, examine the command output for the cause of the problem. |
Explanation | The specified application is not deployed to any target such as an application server or cluster of application servers. |
Action | Edit the application to provide targets for its modules. |
Explanation | An unexpected error occurred. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The object type passed to the createDeployableObject method must to a Scheduler or an Archive. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The setContentPath method is not supported for either an edit or uninstall scheduler. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The scheduler type indicated in the message is not valid. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Examine the exception for a possible root cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The extension registry was not found. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The extension registry does not contain information about the indicated extension point id. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Usage information for the EARExpander command. |
Action | No user action is required. |
Explanation | The indicated option is required and must be specified. |
Action | Rerun the EARExpander command with the missing required option. |
Explanation | The indicated file is not valid. If you are performing an expand operation, the file does not exist, does not have read permission, or is not a valid EAR. If you are performing a collapse operation, the specified file is an existing file. |
Action | Rerun the EARExpander command with a valid EAR file. |
Explanation | The indicated operation directory is not valid. If you are performing an expand operation, the specified directory is an existing file. 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. |
Action | Rerun the EARExpander command with a valid operation directory. |
Explanation | The indicated operation is not valid. Valid operations are "expand" and "collapse". |
Action | Rerun the EARExpander command with a valid operation. |
Explanation | The EARExpander command is expanding an enterprise archive (EAR) file to the indicated directory. |
Action | No user action is required. |
Explanation | The EARExpander command is collapsing the contents of the directory to the indicated EAR file. |
Action | No user action is required. |
Explanation | The value for the indicated option is missing. |
Action | Rerun the EARExpander command with a value for the indicated option. |
Explanation | The specified value for the expansion flag option is not valid. The default value, all, will be 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 | Rerun the EARExpander command with the -verbose option 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 | Rerun the EARExpander command with the -verbose option to get a stack trace for the exception. |
Explanation | The indicated argument is not recognized. |
Action | Rerun the EARExpander command without the indicated argument. |
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 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. |
Explanation | This informational message indicates that the JSP files in the specified WAR compiled without errors. |
Action | No user action is required. |
Explanation | The JSP files in the specified WAR did not compile due to complication 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 program failed during application installation. Prior messages detail the cause of this failure. |
Action | Use the Application Server Toolkit to run the EJBDeploy program 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 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 dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: backward slash (\), slash (/), comma (,), number sign (#), dollar ($), at sign (@), colon (:), semicolon (;), quotation mark ("), asterisk (*), question mark (?), greater than sign (>), less than sign (<), pipe (|), equal sign (=), plus (+), ampersand (&), percent (%), or single quotation mark ('). |
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 the 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The deployment.xml file for the given deployment is empty or not valid. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The document is corrupted or empty. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, make sure that the node name that is passed in is not null. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | No resource JNDI table is created. Need to call gatherJNDINames first. |
Action | Make sure that the gatherJNDINames is called first. |
Explanation | A problem occurred getting the existing deployment resource. |
Action | Edit the application to restore any previous deployment settings. |
Explanation | Recycle option does not match input. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | See messages for cause of error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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: stand-alone library name or "WebSphere:name=<LibraryName>,isSharedClassloader=<true/false>". Use "+" to specify multiple library names. |
Action | Specify the correct shared library string. |
Explanation | The application has version 2.5 web modules with EJB content. Those modules are supported by the product only on version 8 or later. The web modules must be targeted to nodes at version 8 or later. |
Action | You must target each of the specified modules to a node at version 8 or later. |
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 | 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 | 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | While attempting to look for application client for module update, the indicate expcetion occurred. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | An unexpected exception occurred 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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | An activation plan defines dependency of Java Platform, Enterprise Edition application modules on WebSphere runtime components. An unexpected error occurred while deducing this dependency. |
Action | No user action is required. |
Explanation | An activation plan defines dependency of Java Platform, Enterprise Edition application modules on WebSphere runtime components. An activation plan has been successfully created for this application. |
Action | No user action is required. |
Explanation | The property-based configuration file (META-INF/ibm-was-config.props) has been applied to the application. |
Action | No user action is required. |
Explanation | An unexpected error occurred while applying the property-based configuration file (META-INF/ibm-was-config.props) to the application. |
Action | Examine the exception cause message, if one is displayed, for additional information. |
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 | A file or archive with the same name already exist in the application with a different case. |
Action | Rename the file or archive. If the conflicting file or archive was removed from the applicaiton in the same session Save the session and then add the new file or archive. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message might detail a probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 automatic synchronization 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The exception message may detail probable cause. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | Application update changes might not be sychronized, recycle behavior might be unexpected. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | Application distribution status events are emitted through the NotificationService MBean. Because a reference to the NotificationService MBean cannot be obtained, some application distribution notifications cannot be sent. Any listeners for those events will not receive them. |
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 | JNDI strings must be unique within a given scope. |
Action | Modify the JNDI strings to be unique for each application resource. |
Explanation | Multiple applications define resources that have the same name and do not match. |
Action | If the conflicting resources are of the same type, they must be configured identically. If the conflicting resources cannot be configured identically, the conflicting applications cannot coexist in the configuration. |
Explanation | Multiple applications define resources that have the same name and do not match. |
Action | If the conflicting resources are of the same type, they must be configured identically. If the conflicting resources cannot be configured identically, the conflicting applications cannot coexist in the configuration. |
Explanation | This informational message indicates the program status. |
Action | No user action is required. |
Explanation | An unexpected exception occurred 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 installation 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 | If the servers are not intend to start, the application expansion process will occur as a background process. |
Action | No action is required. |
Explanation | The node is already synchronized. Application ripple will skip node synchronization. |
Action | No action is required. |
Explanation | Application cannot be installed accross multiple security domains. |
Action | Verify that user is not installing this application accorss multiple security domains. |
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 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. |
Explanation | Access ids should have one to one mapping to the user/group. |
Action | Validate the entries and retry. |
Explanation | The application is not licensed to be installed on this server. |
Action | Verify that the application is licensed. |
Explanation | The product name is registered. |
Action | No action is required. |
Explanation | The application cannot be installed or updated without a full application server license. |
Action | Do not call the application programming interfaces (API) for application management that update applications in this installation environment. |
Explanation | You cannot install an application without providing required values for variables used in embedded property based configuration file. |
Action | Verify that user provides all required parameters for properties based configuration task. |
Explanation | Runtime provisioning components must be specified as WebSphere:specname=COMP_NAME with multiple components separated by +. |
Action | Verify that the user specified the runtime provisioning components to add or remove in the correct format. |
Explanation | A full application update only takes "update" as a parameter to the operation option. |
Action | Specify the correct parameter for the operation option. |
Explanation | Runtime provisioning components must be specified as WebSphere:specname=COMP_NAME with multiple components separated by +. |
Action | Verify that the user specified the runtime provisioning components to add or remove in the correct format. |
Explanation | Runtime provisioning components must be specified as WebSphere:specname=COMP_NAME with multiple components separated by +. |
Action | Verify that the user specified the runtime provisioning components to add or remove in the correct format. |
Explanation | Runtime provisioning components must be specified as WebSphere:specname=COMP_NAME with multiple components separated by +. |
Action | Verify that the user specified the runtime provisioning components to add or remove in the correct format. |
Explanation | The application contains an ibm-was-config.props file. One is required to specify the values for variables declared in the file. |
Action | Specify the value for the variable. |
Explanation | The indicated file or directory could not be deleted. |
Action | Manually delete the indicated file or directory. |
Explanation | An unexpected exception occurred deleting the indicated file or directory. |
Action | Manually delete the indicated file or directory. |