Express (Distributed operating systems), v8.0 > Reference > Messages
ADMA
ADMA0001E: A validation error occurred in task {0}. The listener port name is not specified for the enterprise bean {1} in module {2}.
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.
ADMA0002E: A validation error occurred in task {0}. The JNDI name is not specified for enterprise bean {1} in module {2}.
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.
ADMA0003E: A validation error occurred in task {0}. The isolation level is not specified for resource reference {1} in module {2}.
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.
ADMA0004E: A validation error occurred in task {0}. The JNDI name is not specified for module {1} with URI {2}. The data source must be specified for each container-managed persistence (CMP) bean that belongs to this module.
Explanation The application contains an 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 to overwrite the one set in the module level. If you do not specify the data source JNDI name in the module level, then we 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.
ADMA0005E: A validation error occurred in task {0}. An inappropriate resource authorization is specified for module {1} with URI {2}.
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.
ADMA0006E: A validation error occurred in task {0}. An inappropriate protection value is specified for module {1} with URI {2}.
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.
ADMA0007E: A validation error occurred in task {0}. The JNDI name is not specified for resource reference {1} in module {2} with EJB name {3}.
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.
ADMA0008E: A validation error occurred in task {0}. The data in a hidden field used to identify an Oracle data source is not specified for resource reference {1} in module {2} with EJB name {3}.
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 More info at:
ADMA0009E: Validation error in task {0}.
User info is not specified for role {1}.
Explanation No user information was specified for the security role. Action Specify a valid user for the listed task in the error message.
ADMA0010E: Validation error in task {0}. A virtual host is not specified for web module {1} with URI {2}.
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.
ADMA0011E: Error saving workspace to configuration repository.
Explanation An unexpected exception occurred when saving the changes made during an application management operation to the configuration repository. Action More info at:
ADMA0012E: The task helper for task {0} cannot be located.
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.
ADMA0013E: The dependency helper for task {0} cannot be located.
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.
ADMA0014E: Validation failed. {0}
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.
ADMA0015E: An incorrect task data format is encountered: incorrect length - {0}
Explanation An error occurred in the task preparing the application. Action Enter the data again in the task preparing the application.
ADMA0016E: The application name is null.
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.
ADMA0017E: The context for {0} cannot be obtained. The application does not appear to be installed.
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.
ADMA0018W: The database vendor type of "{0}" is not supported. Supported values are {1}.
Explanation The specified database vendor type is not supported. Action Specify a supported database vendor type.
ADMA0019E: An attempt to get the EAR file for {0} failed.
Explanation For the listModules or extractDDL functions, the application management logic cannot obtain the EAR file stored in the Application Server configuration. Action More info at:
ADMA0020E: An error occurred backing up the EAR file - {0}
Explanation An error occurred while copying the EAR file to the configuration repository. Action More info at:
ADMA0021E: An error occurred in compiling JSP files - {0}
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.
ADMA0024E: An incorrect dependency task {0} is encountered.
Explanation An error occurred in the Correct Oracle Isolation Level task while preparing the application. Action Validate the application using the Application Server Toolkit.
ADMA0025E: An incorrect isolation level is detected for resource reference {0} for module {1}.
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 specified in the error message.
ADMA0026E: An isolation level is not in number format - {0}
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.
ADMA0027E: An incorrect task data format is detected: The JNDI name for the data source for enterprise bean {0} in module {1} is missing.
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 specified in the error message.
ADMA0028E: An incorrect task data format is detected: User and password data for enterprise bean {0} in module {1} is missing.
Explanation An error occurred in preparing the application. The data source for a 1.x container-managed persistence (CMP) bean has incomplete data. Action More info at:
ADMA0029E: An incorrect task data value is detected for resource authorization of enterprise bean {0} in module {1}.
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 specified in the error message.
ADMA0030E: An incorrect task data format is detected: Resource authorization data for enterprise bean {0} in module {1} is missing.
Explanation An error occurred in preparing the application. The connection factory for a 2.x CMP bean has incomplete data. Action More info at:
ADMA0031E: A matching security role for role name {0} cannot be found.
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.
ADMA0032W: The database access type of "{0}" is not supported. Supported values are {1}.
Explanation The specified database access type is not supported. Action Specify a supported database access type.
ADMA0033E: An incorrect server string is specified - {0}
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.
ADMA0034E: An error occurred getting a role assignment.
Explanation An error occurred in the Mapping users to roles task, while preparing the application. Action If the problem persists, validate the application using the Application Server Toolkit.
ADMA0035E: A null pointer exception occurred when getting local methods for {0}
Explanation An error occurred in the Selecting method protections for unprotected methods task, while preparing the application. Action If the problem persists, validate the application using Application Server Toolkit.
ADMA0036E: A null pointer exception occurred when getting home methods for {0}
Explanation An error occurred in the Selecting method protections for unprotected methods task, while preparing the application. Action If the problem persists, validate the application using the Application Server Toolkit.
ADMA0037E: A null pointer exception occurred when getting local home methods for {0}
Explanation An error occurred in the Selecting method protections for unprotected methods task while preparing the application. Action If the problem persists, validate the application using the Application Server Toolkit.
ADMA0038E: A null pointer exception occurred when getting remote methods for {0}
Explanation An error occurred in the Selecting method protections for unprotected methods task while preparing the application. Action If the problem persists, validate the application using the Application Server Toolkit.
ADMA0039W: The JDK compliance level of "{0}" is not supported. Supported values are {1}.
Explanation The specified JDK compliance level is not supported. Action Specify a supported JDK compliance level.
ADMA0040E: Could not find an EAR, EJB JAR, or WAR (with EJBs) to process.
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.
ADMA0041E: The local EAR file path cannot be null for the installApplication API.
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.
ADMA0042E: The properties cannot be null for the installApplication API.
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.
ADMA0043E: {0} does not exist for installation.
Explanation The EAR file path provided to the installApplication API for the AppManagement MBean does not contain a file. Action Verify that the file exists at the specified location.
ADMA0044E: An error occurred scheduling the installation for {0}
Explanation An unexpected exception occurred during installation. Action More info at:
ADMA0045E: The application name cannot be null.
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.
ADMA0046E: Properties cannot be null for local mode.
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.
ADMA0047E: An error occurred when scheduling the uninstallation for {0}
Explanation An unexpected exception occurred when uninstalling the application. Action More info at:
ADMA0048E: An unknown module is encountered- {0}
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.
ADMA0049E: An exception occurred when getting a module for deployment descriptor {0}
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 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.
ADMA0050W: Role name is empty for security role {0}.
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.
ADMA0053E: An error occurred closing the EAR file {0}
Explanation This exception occurs during application installation processing if the EAR file gets locked because of an unexpected error, and cannot be closed. Application installation is stopped when this error occurs. Action More info at:
ADMA0054E: An exception occurred checking application existence - {0}
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.
ADMA0055E: An error occurred getting task {0}
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 More info at:
ADMA0056E: An incorrect task data format is detected; the JNDI data is missing in module {0}
Explanation An error occurred in preparing the application. The default data source for a JAR file is not specified. Action Specify the default data source for the JAR file specified in the error message.
ADMA0057E: An incorrect task data format is detected: the user and password data is missing in module {0}
Explanation An error occurred in preparing the application. The default data source for a JAR file has incomplete data. Action More info at:
ADMA0058E: An incorrect task data value for resource authorization exists in module {0}.
Explanation An error occurred in preparing the application. The resource authorization value for a 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 specified in the error message.
ADMA0059E: An incorrect task data format is detected. The resource authorization data is missing in module {0}
Explanation An error occurred in preparing the application. The default connection factory for a JAR file contains incomplete data. Action More info at:
ADMA0060E: The "filename" parameter value is not valid. It must be a non-empty string.
Explanation The "filename" parameter passed to the exportApplication function must be a valid file path name. Action Specify a non-empty file path name.
ADMA0061E: An error occurred deleting SI entry - {0}
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 More info at:
ADMA0062E: The EJBDeploy program issued the following error messages: {0}
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.
ADMA0063E: An error occurred during EJB deployment. Exception: {0}
Explanation An unexpected exception occurred during EJB deployment. Action More info at:
ADMA0064E: An error occurred when extracting the EAR file.
Explanation An unexpected exception occurred during EAR file expansion. Action Verify that enough disk space is available for the EAR file to extract completely and that the proper file permissions are set to both the temp directory and the directory specified as the installation destination.
ADMA0065E: An error occurred getting a partial archive in the writeTasks method- {0}
Explanation An unexpected exception occurred saving the information that passed in during the editing of an existing application. Action More info at:
ADMA0066E: An error occurred creating the configuration documents in the repository.
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.
ADMA0067E: A validation error occurred in task {0}. The RunAs role, {1}, for enterprise bean {2} in module {3} has a user name and a password that are different from those in task {4}.
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.
ADMA0068E: A validation error occurred in task {0}. An error occurred getting task {1} to validate existing RunAs roles.
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 More info at:
ADMA0069E: A validation error occurred in task {0}. The RunAs role, {1}, for enterprise bean {2} in module {3} has a different user name and password combination.
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.
ADMA0070W: Security policy filtering cannot be performed: An error occurred getting the repository context for a cell in the workspace.
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 the configuration.
ADMA0071W: An attempt to perform security policy filtering failed. An unexpected exception occurred {0}
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 the configuration.
ADMA0072E: Your application contains policy permissions that are in the filter.policy. These permissions are security sensitive and can compromise the integrity of the system. Remove these permissions from your policy file before attempting to install the application again.
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.
ADMA0073W: Custom permissions are found in the {0} policy file. Custom permissions can compromise the integrity of Java 2 Security.
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.
ADMA0074E: A validation error occurred in task {0}. The JNDI name and resource authorization are not specified for module {1} with URI {2}. The data source for each container-managed persistence (CMP) bean belonging to this module is not specified. Specify the default data source for the entire module or provide the complete data source for each CMP bean belonging to this module.
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. We 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 to overwrite the one set in the module level. If you do not specify the data source data in the module level, then we 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.
ADMA0077W: An error occurred removing the workspace. Exception: {0}
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 wsadmin.sh (except when the -local option is used) or the administration client UI. Action More info at:
ADMA0078W: The file: {0} cannot be deleted.
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.
ADMA0079W: The task information for: {0} cannot be found.
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 More info at:
ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application. We can modify the Java 2 Security policy for the enterprise application by editing the was.policy file that is located in the ${user.install.root}/config/cells/(yourCellName)/applications/(yourAppName).ear/deployments/(yourAppName)/META-INF directory after the application is installed.
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 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.
ADMA0081W: The 1.2.x enterprise application does not contain a Java 2 Security policy. Your application might not run after it is installed.
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 the application before reinstalling the application.
ADMA0082E: Your application contains the following incompatible JAR or Web application archive (WAR) file:{0}. Correct the file before trying the operation again.
Explanation Typically, this error is displayed when a J2EE 1.2 application EAR file contains a J2EE 1.3 module. Action Verify that the EAR file is a J2EE-compliant EAR file.
ADMA0083E: The file or directory {0} specified as an EAR file is not valid.
Explanation The application specified is not a valid EAR file. Action Verify that the correct application file is entered. Otherwise, validate the application using the Application Server Toolkit.
ADMA0084E: The archive {0} to wrap is not a module of type JAR or WAR.
Explanation The specified application file is not a valid JAR or WAR file. Action Verify that the correct application file is entered.
ADMA0085E: A validation error occurred in task {0}. Application name, {1}, is not valid. An application name cannot begin with a dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ''
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.
ADMA0086E: [EJBDeploy] {0}
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.
ADMA0087W: [EJBDeploy] {0}
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.
ADMA0088E: An unacceptable usage of {0} has occurred. Operation {0} can be called only in the local mode of the AppManagement MBean.
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.
ADMA0089E: The AppManagement MBean is not found.
Explanation If the AppManagement MBean is a node agent or application server, then the AppManagement MBean is not activated by default. Action More info at:
ADMA0090E: The system detected a use of {0} that is not valid. Operation {0} can be called in the Java Management Extentions (JMX) mode of the AppManagement MBean only.
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.
ADMA0091W: The resource {0} that is defined in URI {1} for module {2} is not valid. The resource has a cross reference {3} that cannot be resolved.
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.
ADMA0092E: An unexpected exception occurred while preparing task {0}. Exception: {1}
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 EAR file is correct.
ADMA0093E: An unexpected exception occurred while completing task {0}. Exception: {1}
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 EAR file is correct.
ADMA0094E: An application management operation {0} is not available in your WAS installation.
Explanation The user applications cannot be installed or updated without a full WAS license. Action Do not call the application management APIs that update applications in this installation environment.
ADMA0095W: The current backend ID ({0}) specified in the ibm-ejb-jar-bnd.xmi file for enterprise bean JAR file ({1}) does not exist.
Explanation The current backend ID 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) 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 JAR file.
ADMA0096I: The application management version key is found, but is not valid.
Explanation A full WAS product installation is not available, or is corrupted. Action No user action is required if we have an embedded WAS installation.
ADMA0097I: Application management is being initialized without a full product installation. All application management functions are not available.
Explanation A full WAS product installation is not available to perform all of the application management functions. Action No user action is required if we have an embedded WAS installation.
ADMA0098E: The current backend ID {0} does not exist in the BackendId list: {1} under the META-INF/backends directory.
Explanation The current backend ID 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.
ADMA0099E: A validation error occurred in task {0}. The listener port name or JNDI name is not specified for enterprise bean {1} in module {2}.
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.
ADMA0100E: A validation error occurred in task {0}. The JNDI name is not specified for connector {1} in module {2}.
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.
ADMA0101E: A validation error occurred in task {0}. The reload interval, {1}, is not valid. The reload interval must be an integer from 0 to {2}.
Explanation The exception message might contain the reason for this problem. Action Specify an integer within the valid range.
ADMA0102E: {0} is not defined in the ra.xml file.
Explanation The specified entry is not found in the ra.xml file. Action Add the specified entry to the ra.xml file.
ADMA0103E: A duplicate {0} entry is found in 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.
ADMA0104W: An unexpected exception occurred while getting the workspace. {0}
Explanation Review the exception information to determine the cause of the error. Action No user action is required.
ADMA0105E: An error occurred creating the libraryRef object for the installedOptionalPackage task.
Explanation A previous message from the application installation program contains more detail about this error. Action Make sure that the shared library JAR file contains the libraryName object.
ADMA0106E: A workspace cannot be obtained. The workspace ID is {0}.
Explanation An attempt to get a workspace failed. Action Verify what is passed in as a workspace ID.
ADMA0107E: Application has J2EE/Deployment features of version {0} but they are not supported on nodes {1}
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.
ADMA0108E: The application contains connector modules or resource adapter archives (RAR) of version {0}, which is not supported in the application version {1}
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.
ADMA0109W: The validate install input value: {0} is not valid. Specify either off, warn, or fail as the value.
Explanation An unexpected exception occurred. Review the exception information. Action No user action is required.
ADMA0110E: This type of J2EE application {0} is not supported on nodes {1} of version {2}
Explanation This type of application is not supported on the nodes. Action Verify that the J2EE application type is correct for the deployment target.
ADMA0111E: The following J2EE and deployment options {0} are selected, but are not supported while installing an application on nodes {1} of version {2}
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.
ADMA0112E: Validation error in task {0}.
The required column {1} is not specified.
Explanation The required column does not have a value. Action Specify the required column in the task that is listed in the error message.
ADMA0113I: [EJBDeploy] {0}
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.
ADMA0114W: Resource assignment with JNDI name {0} is not found within scope of module {1} with URI {2} deployed to target {3}.
Explanation The resource is not found on the deployment target. Action Make sure that the resource JNDI name is correct for the resource.
ADMA0115W: Resource assignment of name {0} and type {1}, with JNDI name {2} is not found within scope of module {3} with URI {4} deployed to target {5}.
Explanation The resource is not found on the deployment target. Action Make sure that the resource JNDI name is correct for the resource.
ADMA0116W: Unable to start: {0} using: {1} exception is: {2}
Explanation An unexpected exception occurred. Action No user action is required.
ADMA0117W: Unable to stop: {0} using: {1} exception is: {2}
Explanation An unexpected exception occurred. Action No user action is required.
ADMA0118W: The {0} operation on application {1}, node {2}, server {3}, failed because the ApplicationManager MBean for that target server could not be found.
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.
ADMA0119E: An unexpected exception occurred while getting the node objects in the cell {0}. Exception is {1}.
Explanation An unexpected error occurred while getting the node objects in the cell. Action Review and investigate the original exception.
ADMA0120E: An unexpected exception occurred while getting the servers in the node {0}. Exception is {1}.
Explanation An unexpected error occurred while getting the servers in the specified node. Action Review and investigate the original exception.
ADMA0121E: An unexpected exception occurred while getting the clusters in the cell {0}. Exception is {1}.
Explanation An unexpected error occurred while getting the clusters in the specified cell. Action Review and investigate the original exception.
ADMA0122E: An unexpected exception occurred while getting the application {0}. Exception is {1}.
Explanation An unexpected error occurred while getting the specified application scopes. Action Review and investigate the original exception.
ADMA0123W: An unexpected exception occurred while getting the attribute {0} of object {1}. Exception is {2}.
Explanation An unexpected error occurred while getting the attribute of the specified object. Action Review and investigate the original exception.
ADMA0124E: An unexpected exception occurred while getting the Library object from the deployment.xml file of the application {0}. Exception is {1}.
Explanation An unexpected error occurred while getting the Library object from the specified application deplyment.xml file. Action Review and investigate the original exception.
ADMA0125E: The cell name cannot be null for installing or uninstalling system application {0}.
Explanation System application installation and uninstallation needs a cell, node, and server name. Action Pass cell.name in the hashtable to the AppManagement API.
ADMA0126E: The node name cannot be null for installing or uninstalling system application {0}.
Explanation System application installation and uninstallation needs a cell, node, and server name. Action Pass node.name in the hashtable to the AppManagement API.
ADMA0127E: The server name cannot be null for installing or uninstalling system application {0}.
Explanation System application installation and uninstallation needs a cell,node, and server name. Action Pass server.name in the hashtable to the AppManagement API.
ADMA0128E: Invalid cell name {1} was passed to the installApplication API for installing application {0}
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.
ADMA0129W: Unable to get the deployment.xml file.
Explanation The deployment.xml file cannot be retrieved. Action Verify the deployment.xml file can be reached.
ADMA0130E: The content type {0} specified for updating {1} is not valid.
Explanation The content type can be file, module, partialapp or app. Action Change the content type that passes to the updateApplication API.
ADMA0131E: The path to content must be specified when the contenttype value is partialapp for updating an application.
Explanation The content path is null in the updateApplication API. Action Specify the pathToContents value in the updateApplication API.
ADMA0132E: The operation {0} that is specfied for updating application {1} is not valid.
Explanation The operation type is not valid in the updateApplication API. Action Specify a valid operation type: add, addupdate, update, or delete.
ADMA0133E: Both the content URI and the path to content values must be specified for file or modulefile updates.
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.
ADMA0134E: Content does not exist at path {0} specified for the file and modulefile update of {1}
Explanation The content does not exist at the specified path. Action Verify that the content path is correct.
ADMA0135E: The content URI must be specified for file or modulefile delete.
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.
ADMA0136E: Content type {0} and operation {1} is not valid. Because {1} is installed using zero binary copy mode only, you can use the modulefile as content type and specify add or delete as operation.
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.
ADMA0137E: JNDI resource element {2} in module {0} with URI {1} does not have a type.
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.
ADMA0138W: The resource assignment with JNDI name {0} is found within scope of module {1} with URI {2} deployed to target {3}, but of wrong resource type {4}. The expected resource type is {5}.
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.
ADMA0139W: The resource assignment of name {0} and type {1}, with JNDI name {2} is found within scope of module {3} with URI {4} deployed to target {5}, but of wrong resource type {6}. The expected resource type is {7}.
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.
ADMA0140E: A validation error occurred in task {0}. Application edition, {1}, is not valid. An application edition cannot have leading or trailing spaces and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % '' [ ]
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.
ADMA0141E: Application {0} cannot be uninstalled because it is active on deployment targets {1}.
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.
ADMA0142W: Trying to close the archive that is already closed.
Explanation The archive file is already closed. Action No user action is required.
ADMA0143W: Unexpected exception: {0} checking if the EAR file is deployed.
Explanation An unexpected exception occurred while checking if the enterprise bean JAR file deployed. Action No user action is required.
ADMA0144E: Application {0} is installed with the zero binary copy option. Applications are installed using this option in a Rational unit test environment or using AppManagement MBean API. When an application is installed using this option it is not possible to perform any operation on this application using wsadmin or administrative console that involves accessing the application metadata or EAR file. Such operations include view/edit application information, export, export DDL etc. The only possible operations using wsadmin or admin console are start, stop and uninstall. If this application is installed using WSAD unit test environment then use WSAD to view/edit application information.
Explanation This application cannot be exported, edited, or updated. Action This operation is not accepted.
ADMA0145E: The application {0} is installed with the zero binary copy option. It is not possible to perform any operation on this application that involves accessing the application metadata or enterprise archivve (EAR) file.
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.
ADMA0146E: The application {0} is installed with the zero ear copy option. It is not possible to perform edit operations with useMetaDataFromBinaries flag true.
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.
ADMA0147E: The application {0} 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.
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.
ADMA0148E: This type of Java Platform, Enterprise Edition application {0} is not allowed on nodes {1} of version {2} when autolink is enabled
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.
ADMA0149E: This type of Java Platform, Enterprise Edition application {0} is not allowed on nodes {1} of version {2} when client module is deployed.
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.
ADMA0150E: An error occurred during the deployment extension step - {0}
Explanation An error occurred while running the deployment step. Action Check any error logs that are specific to the step.
ADMA0151I: The system successfully ran the deployment extension step - {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA0152E: The system failed to run the deployment extension step - {0}: {1}
Explanation This deployment step is not successful. Action Check any error logs that are specfic to the step.
ADMA0153I: The system is starting the deployment extension step - {0}
Explanation This informational message indicates the program status. Action No user action is required
ADMA0154I: A non-J2EE artifact is detected for installation. The system searches for available EAR wrapper extensions to wrap the non-J2EE artifact to an EAR file for application deployment.
Explanation This informational message indicates the program status. Action No user action is required
ADMA0155I: The system successfully made an EAR wrapper extension. New earFilePath: - {0}
Explanation The EAR wrapper extension is successful. Action No user action is required
ADMA0156I: The EAR wrapper extension class - {0} is found and ran successfully.
Explanation An EAR wrapper extension was found to wrap the module to the EAR file. Action No user action is required
ADMA0157E: The system cannot find any valid EAR wrapper extensions or an extension did not run successfully to set a new EAR file path.
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 More info at:
ADMA0158I: [EJBDeploy] {0}
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.
ADMA0159W: Duplicate root context({0}) was found on the same node {1} and same host {2}
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.
ADMA0160E: The target scope that is passed to the listApplications has incorrect format {0}.
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.
ADMA0161W: The resource assignment with name {0} is not found within scope of module {1} with URI {2} that is deployed to target {3}.
Explanation The resource is not found on the deployment target. Action Verify that the resource JNDI name is correct for the resource.
ADMA0162W: The resource assignment with name {0} is found within scope of module {1} with URI {2} deployed to target {3}, but of wrong resource type {4}. The expected resource type is {5}.
Explanation The resource is not found on the deployment target. Action Make sure that the resource JNDI name is correct for the resource.
ADMA0163E: Resource validation is not initialized.
Explanation The call to initialize the resource validation is not performed. Action More info at:
ADMA0164W: Failed to load the systemapps.xml file on cell {0}, node {1}.
Explanation The systemapps.xml file did not load. Action Verify that the cell name and node name are correct.
ADMA0165E: Content does not exist at the path specified {0} for a partialapp update.
Explanation The specified content does not exist. Action Verify that the content path is correct.
ADMA0166E: Duplicate file {0} for {1} operation.
Explanation The file 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.
ADMA0167E: File {0} does not exist for {1} operation.
Explanation The file 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.
ADMA0168E: Attempt to remove last module {0}.
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.
ADMA0169E: Parameter validation failure for {0}:
Explanation Parameter validation failed. Action Review the original exception and confirm that the passed parameter is correct.
ADMA0170E: Authorization failure. The user does not have permission to access application {0}.
Explanation The user does not have proper role assigned to manage the specified application. Action Confirm that the user has the proper administrative role.
ADMA0171E: Authorization failure. The user does not have permission to manage the target {0} : {1}.
Explanation The user does not have proper role assigned to manage the specified target. Action Confirm that the user has the proper administrative role.
ADMA0172E: Authorization failure. The user does not have permission to perform {0} role on the resource {1}.
Explanation The user does not have proper role assigned to manage the specified resource. Action Confirm that the user has the proper administrative role.
ADMA0173E: The EAR file for application {0} is not managed by WebSphere. Therefore, any operation such as {1} that involves changing the EAR file is not allowed.
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.
ADMA0174E: The filepermission argument contains an invalid format or contains an invalid regular expression pattern: {0}. Correct format is file_pattern=permission. Multiple filepermissions are separated by a ''#'' (Example: .*\.jsp=644#.*\.xml=744).
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.
ADMA0175E: The AsyncRequestDispatchType is not valid.
Explanation User provided incorrect AysncRequestDispatchType, valid types are DISABLED, SERVER_SIDE, or CLIENT_SIDE. Action Provide a valid AsyncRequestDispatchType.
ADMA0176E: Application installation of {0} failed with PrivilegedActionException. Ear file path is {1}.
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.
ADMA0177E: Application installation of {0} failed with unknown exception. Ear file path is {1}. Exception is {2}.
Explanation Application installation had failed with unknown exception. Action Investigate the exception.
ADMA0178E: Checking of the existence of Application {0} failed with PrivilegedActionException.
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.
ADMA0179E: Checking of the existence of Application {0} failed with unknown exception. Exception is {1}.
Explanation Checking of the existence of Application had failed with unknown exception. Action Investigate the exception.
ADMA0180E: Comparing security policy failed with PrivilegedActionException.
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.
ADMA0181E: Comparing security policy failed with unknown exception. Exception is {0}.
Explanation Comparing security policy had failed with unknown exception. Action Investigate the exception.
ADMA0182W: The JNDI name {0} specified for the message destination reference {1} does not match the JNDI name {2} of the message destination.
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.
ADMA0183E: Cannot delete a deployment descriptor file: {0}
Explanation The file requested to be deleted is a deployment descriptor file which cannot be deleted. Action Check that we 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.
ADMA0184E: {0} is not a valid target.
Explanation The specified target server does not exist. Action Verify that the target name is valid. Look for typographical errors.
ADMA0185W: An update application operation failed and the configuration session could not be restored to its state before the operation was initiated. The configuration session is in an inconsistent state, and changes made in the session should be discarded.
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.
ADMA0186W: An uninstall application operation failed and the configuration session could not be restored to its state before the operation was initiated. The configuration session is in an inconsistent state, and changes made in the session should be discarded.
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.
ADMA0187E: Authorization failure. The user does not have permission to install application {0}. The user must have deployer role or configurator role for the cell or for the targets to install/redeploy the application.
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.
ADMA0188E: Authorization failure. The user does not have permission to uninstall application {0}. The user must have deployer role or configurator role for the cell or for the target, or deployer role for the application to uninstall it.
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.
ADMA0189E: Authorization failure. The user does not have permission to update application {0}. The user must have deployer role or configurator role for the cell or for the target, or deployer role for the application.
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.
ADMA0190E: Authorization failure. The user does not have permission to access application {0}. The user must have monitor role.
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.
ADMA0191E: Authorization failure. The user does not have permission to access the resource {0}. The user must have monitor role for the cell, target node or the application.
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.
ADMA0192E: Authorization failure. The user does not have permission to access the resource {0}. The user must have {1} role to access {2}.
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.
ADMA0193E: Authorization failure. The user does not have permission to update the application {0}. The user must have deployer role or configurator role for the cell or deployer role of the application.
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.
ADMA0194E: Authorization failure. The user does not have permission to start/stop application {0}. The user must have operator role of the applocation.
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.
ADMA0195W: Environment entry {1} in module {0} does not have a type.
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.
ADMA0196W: Environment entry {1} in module {0} does not have a value.
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.
ADMA0197E: The application cannot be updated with the {0} file because the application server cannot expand the {1} URI as an archive file. Either the URI does not resolve to an archive file or the archive file is corrupted.
Explanation An archive file in a deployed application cannot be opened. The file URI 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.
ADMA0199E: The system cannot complete the operation with autolink enabled. All modules must share one common target to enable autolink support.
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.
ADMA0200E: The application cannot be installed as the installation logic failed to determine the runtime components that this application depends on. The error is - {0}
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.
ADMA0201E: Application validation failed as node {0} of version {1} cannot support use of asset and composition unit shared library.
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.
ADMA0202E: A validation error occurred in task {0}. The type of EJB reference is not specified or is not valid for EJB resource reference {1} in module {2} with EJB name {3}.
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.
ADMA0203E: A validation error occurred in task {0}. The type is not specified for the resource reference {1} in module {2} with EJB name {3}.
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.
ADMA0204E: The application {0} cannot be installed to server type {1} since it is not a system 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.
ADMA0205E: A validation error occurred in task {0}. JNDI names for the bean and its local/remote home are both specified for enterprise bean {1} in module {2}. We can provide either JNDI name for the bean or JNDI names for its local/remote home. But you cannot provide both.
Explanation A non-message-driven bean is in the application. We 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.
ADMA0206E: A validation error occurred. JNDI names for the bean in task "{0}" and its business interface "{1}" in task "{2}" are both specified for enterprise bean {3} in module {4}. We can provide either JNDI name for the bean or JNDI names for its business interface(s). But you cannot provide both.
Explanation A non-message-driven bean is in the application. We 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.
ADMA0207E: Module {0} contains an unsupported xmi format bindings or extensions file.
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 EJB 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.
ADMA0208E: The Enterprise Archive (EAR) contains an unsupported xmi format bindings or extensions file.
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.
ADMA0209E: EJB module {0} contains the following container-managed persistence (CMP) or bean-managed persistence (BMP) Entity beans: {1}.
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.
ADMA0210E: A validation error occurred in task {0}. The extended data source properties {1} specified for resource reference {2} in module {3} with EJB name {4} is not valid.
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.
ADMA0211E: This is a EAR file which is a system application. The system application should always be installed from an expanded directory.
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.
ADMA0212E: The Enterprise Archive (EAR) contains both xmi and xml bindings or extensions files at the application level.
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.
ADMA0213W: The "deploy enterprise beans" option was specified, but no enterprise beans were deployed.
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.
ADMA0214W: The "precompile JSP files" option was specified, but no JSP were compiled.
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 JSP files option.
ADMA0215I: The JSP compile task completed.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA0216E: The JSP compile task failed.
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.
ADMA0217E: Validation error in task "{0}". The JSP reload interval "{3}" for web module {1} (URI: {2}) is not valid.
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.
ADMA0218E: Environment entry {2} for EJB {1} in module {0} does not have a type.
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.
ADMA0219E: A validation error occurred in task "{0}". The value for environment entry {3} for EJB {2} in module {1} is missing.
Explanation A value for the indicated environment entry must be specified. Action Specify a value for the indicated environment entry.
ADMA0220E: A validation error occurred in task "{0}". The value "{5}" for environment entry {3} (type: {4}) for EJB {2} in module {1} is not valid. Exception: {6}
Explanation The value specified for the indicated environment entry is not valid. Action Specify a valid value for the indicated environment entry.
ADMA0221E: Environment entry {1} in module {0} does not have a type.
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.
ADMA0222E: A validation error occurred in task "{0}". The value for environment entry {2} in module {1} is missing.
Explanation A value for the indicated environment entry must be specified. Action Specify a value for the indicated environment entry.
ADMA0223E: A validation error occurred in task "{0}". The value "{4}" for environment entry {2} (type: {3}) in module {1} is not valid. Exception: {5}
Explanation The value specified for the indicated environment entry is not valid. Action Specify a valid value for the indicated environment entry.
ADMA0224E: The applyConfigProperties command failed. Result: {0}
Explanation The property-based configuration applyConfigProperties command failed with the indicated result. Action More info at:
ADMA0225E: The property-based configuration task failed.
Explanation An unexpected error occurred while applying the property-based configuration file (META-INF/ibm-was-config.props) to the application. Action More info at:
ADMA0226E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires EJB specification level {2}, which this node does not support
Explanation The deployed applications for this cluster require an 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.
ADMA0227E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires Servlet specification level {2}, which this node does not support
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.
ADMA0228W: EJB {0} in module {1} has no binding for its datasource.
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.
ADMA0229W: An unexpected error occurred when querying for applications running on node {0}, server {1}.
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.
ADMA0230I: Will retry to expand the application {0}, which previously failed to expand.
Explanation Found a marker file that indicates a binary expansion failure and expansion needs to be retried. Action No action is required.
ADMA0231E: Failed to set file permissions on the file {0}.
Explanation For some reason there was a problem setting the file permissions for the file. Action Check the FFDC logs for the error.
ADMA0232E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires Connector specification level {2}, which this node does not support
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.
ADMA0233E: Node {0} cannot be added to cluster {1} because an application currently deployed on the cluster requires at least Servlet specification level {2} that contains EJB content, which this node does not support
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.
ADMA0234E: A validation error occurred in task {0}. An environment entry value {3} and lookup name {4} are specified for environment entry {2} in module {1}.
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.
ADMA0235E: A validation error occurred in task {0}. A lookup name {3} and EJB link {4} are specified for EJB reference {2} in module {1}.
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.
ADMA0236E: File {0} is a non-J2EE type artifact. Operation delete on modulefile content type cannot be performed on a non-J2EE type artifact.
Explanation The file 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.
ADMA0237I: EJBDeploy does not apply to EJBs contained in WAR files. EJBs in WAR file {0} are being skipped.
Explanation The deploy EJB task does not execute on EJBs in WAR files. Action No action is required.
ADMA0238I: No EJB JAR files were found for EJBDeploy to process.
Explanation The deploy EJB task could not find an EJB JAR file to process. Action No action is required.
ADMA0239W: The application contains EJB content in web module {0}. This module can not be targeted for web server {1}.
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.
ADMA0240E: The application contains EJB content in web module {0}. This module can not be targeted for web server {1}.
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.
ADMA0241W: EJB {0} has a dependency on EJB {1} in another module, which conflicts with the option to initialize the modules in the order they are listed in the application deployment descriptor.
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. 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.
ADMA0242E: A validation error occurred in task {0}. There is a conflict in the target JNDI name for the same reference {1} in module {2}.
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.
ADMA0243I: The file {0} has been removed, from {1} application during the open of the packaged archive.
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.
ADMA0244E: The client mode input value: {0} is not valid. Specify either isolated, federated, or server_deployed as the value.
Explanation An invalid value is specified for client mode option. Action Provide a correct value for client mode option.
ADMA0245W: EJBDeploy feature is not installed. Cannot execute "deploy enterprise beans" 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.
ADMA0246E: Environment entry {0} in application level does not have a type.
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.
ADMA0247E: A validation error occurred in task "{0}". The value for environment entry {1} is missing.
Explanation A value for the indicated environment entry must be specified. Action Specify a value for the indicated environment entry.
ADMA0248E: A validation error occurred in task "{0}". The value "{1}" for environment entry {2} (type: {3}) is not valid. Exception: {4}
Explanation The value specified for the indicated environment entry is not valid. Action Specify a valid value for the indicated environment entry.
ADMA0249W: Extended datasource property is not supported for module {0} in task {1}
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.
ADMA0500E: Unexpected exception occurred in application management command: {0}
Explanation An unexpected exception occurred during application management command processing. Action Examine the exception cause message, if one is displayed, for additional information.
ADMA0501E: The EAR file was not found for the application: {0}
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.
ADMA0502E: An exception occurred while updating the EAR file in the workspace. The SQLJ customization results were not stored, however, if SQLJ binding was performed, then packages in the database have been modified. The application name is: {0} The workspace EAR file is: {1}
Explanation An exception occurred while storing the results of SQLJ processing to the 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.
ADMA0503E: An exception occurred while accessing an input file. The file name is: {0}
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.
ADMA0504W: A duplicate profile name was found. The short profile name is: {0}. The input profile name is: {1}.
Explanation During SQLJ processing a duplicate profile name was found. Action Check the input list of profile names for duplicate names.
ADMA0505E: An exception occurred while accessing a temporary output file. The file name is: {0}
Explanation An exception occurred while opening or writing a temporary output file. Action Examine the linked exception for the cause.
ADMA0506I: The SQLJ operation on application {0} did not complete successfully. Exit code: {1}
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.
ADMA0507I: The SQLJ operation on application {0} completed successfully. Exit code: {1}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA0508I: The pureQuery bind operation on application {0} did not complete successfully. Exit code: {1}
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.
ADMA0509I: The pureQuery bind operation on application {0} completed successfully. Exit code: {1}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA0510I: Results from pureQuery bind processing for {0}. Return code: {1} Exception: {2}
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.
ADMA0511E: Application {0} failed to start. There is no module target specified for the application.
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.
ADMA2000E: An unexpected error occurred.
Explanation An unexpected error occurred. Action More info at:
ADMA2001E: Unsupported object type {0} specified for source of deployable object.
Explanation The object type passed to the createDeployableObject method must to a Scheduler or an Archive. Action More info at:
ADMA2002E: The setContentPath method is not supported for the scheduler being used.
Explanation The setContentPath method is not supported for either an edit or uninstall scheduler. Action More info at:
ADMA2003E: Internal error; unexpected scheduler type {0}.
Explanation The scheduler type indicated in the message is not valid. Action More info at:
ADMA2004E: Extension provider {0} encountered an error.
Explanation Examine the exception for a possible root cause. Action More info at:
ADMA3000E: Unable to get the extension registry.
Explanation The extension registry was not found. Action More info at:
ADMA3001E: Unable to get the extension point {0}.
Explanation The extension registry does not contain information about the indicated extension point id. Action More info at:
ADMA4001I: Usage: EARExpander -ear <file-name>
-operation {expand|collapse}
-directory <directory> | -operationDir <directory>
[-expansionFlags {all | war}]
[-verbose]
Explanation Usage information for the EARExpander command. Action No user action is required.
ADMA4002E: The option {0} is required.
Explanation The indicated option is required and must be specified. Action Rerun the EARExpander command with the missing required option.
ADMA4003E: The EAR file {0} is not valid.
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.
ADMA4004E: The operation directory {0} is not valid.
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.
ADMA4005E: The operation {0} is not valid.
Explanation The indicated operation is not valid. Valid operations are "expand" and "collapse". Action Rerun the EARExpander command with a valid operation.
ADMA4006I: Expanding EAR file {0} to directory {1}.
Explanation The EARExpander command is expanding an EAR file to the indicated directory. Action No user action is required.
ADMA4007I: Collapsing the contents of directory {0} to EAR file {1}.
Explanation The EARExpander command is collapsing the contents of the directory to the indicated EAR file. Action No user action is required.
ADMA4008E: The value for option {0} is missing.
Explanation The value for the indicated option is missing. Action Rerun the EARExpander command with a value for the indicated option.
ADMA4009W: The value {0} for the expansion flag option is not valid.
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 EAR file. Otherwise, rerun the EARExpander command and specify war, as the expansion flag.
ADMA4010W: Both the listener port and the JNDI name are specified for the enterprise bean: {0} in module {1}. Specify only one value, either the listener port or the JNDI name, for the enterprise bean.
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.
ADMA4011E: A validation error occurred in task {0}. The JNDI name is not specified for message destination object {1} in module {2}.
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.
ADMA4012E: A validation error occurred in task {0}.
The JNDI name is not specified for the enterprise bean: {1} in module: {2}. Specify a JNDI name for the enterprise bean.
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.
ADMA4013E: An unexpected exception occurred while attempting to expand the EAR file {0} to directory {1}. Exception: {2}
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.
ADMA4014E: An unexpected exception occurred while attempting to collapse the contents of directory {0} to EAR file {1}. Exception: {2}
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.
ADMA4015E: The argument {0} is not recognized.
Explanation The indicated argument is not recognized. Action Rerun the EARExpander command without the indicated argument.
ADMA5001I: The application binaries are saved in {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5002E: Application binaries cannot be saved in {0}: {1}
Explanation As part of the application installation, the application EAR file is saved in the Application Server configuration repository. This error message is displayed during installation if the EAR file cannot be saved. Action Verify that enough disk space is available to save the EAR file, and check the file permissions.
ADMA5003I: The JSP files in the Web Archive (WAR) {0} compiled successfully.
Explanation This informational message indicates that the JSP files in the specified WAR compiled without errors. Action No user action is required.
ADMA5004W: The JSP files in the Web Archive (WAR) {0} failed to compile; check the log for more information.
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.
ADMA5005I: The application {0} is configured in the WAS repository.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5006E: An error occurred configuring {0} in WAS repository: {1}
Explanation Prior messages detail the cause of this failure. Typically, the error conditions include wrong server and node names specified as module targets during installation. Action Read the error messages and rectify the problem.
ADMA5007I: The EJBDeploy program completed on file {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5008E: The EJBDeploy program failed on file {0}. Exception: {1}
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 EAR file before installing it, and remove the causes of the EJBDeploy failures.
ADMA5009I: Extracting application archive to {0}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5010E: An error occurred extracting the application archive to {0}. Exception: {1}
Explanation The disk might be full or might be write-protected. Action More info at:
ADMA5011I: The cleanup of the temp directory for application {0} is complete.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5012I: The installed cleanup failed for {0}: {1}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5013I: Application {0} installed successfully.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5014E: The installation of application {0} failed.
Explanation Prior messages detail the cause of this failure. Action Read the previous message to rectify the problem.
ADMA5015E: Application {0} cannot be installed because it already exists in the WAS configuration.
Explanation The application name must be unique in the Application Server configuration. Action Install the application with a different name.
ADMA5016I: Installation of {0} started.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5017I: Uninstallation of {0} started.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5018I: The EJBDeploy program is running on file {0}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5019E: The application name {0} is not valid. The application name cannot begin with a dot, cannot have leading or trailing spaces, cannot contain "]]>", and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ''
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.
ADMA5020E: The target server {0} on node {1} specified for module {2} does not exist.
Explanation A target specified for a module during application installation is not valid. Action Verify that the specified target server exists.
ADMA5022E: The target cluster {0} specified for module {1} does not exist.
Explanation A target specified for a module during application installation is not valid. Action Verify that the specified target cluster exists.
ADMA5023E: Ambiguous specification for object {0}. Multiple objects exist with this name, at least one each under parents {1} and {2}. Specify parent {3}.
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.
ADMA5024E: The cluster member {0} is specified as a target for module {1}, but the cluster {2} that {0} belongs to is not specified in the list of targets. This configuration is not valid.
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.
ADMA5025E: The ObjectName format is incorrect for {0}.
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.
ADMA5026E: No valid target is specified in ObjectName {0} for module {1}.
Explanation The target server or cluster 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.
ADMA5027E: Cluster {0} is not found in the repository.
Explanation The cluster with the given name does not exist. Action Correct the cluster name. Check for typographical errors.
ADMA5028E: Server {0} on node {1} is not found in the repository.
Explanation The server with the given name does not exist under the given node. Action Correct the server name. Look for typographical errors.
ADMA5029E: Cluster member {0} that is defined in the cluster configuration for {1} cannot be found as a server.
Explanation The cluster.xml file for the cluster lists a cluster member that does not exist. The cluster configuration might not be valid. Action More info at:
ADMA5030E: No deployment object is found in the deployment document for {0}.
Explanation The deployment.xml file for the given deployment is empty or not valid. Action More info at:
ADMA5031E: The system cannot load {0} document for the object at {1}.
Explanation The document is corrupted or empty. Action More info at:
ADMA5032W: The target {0} is specified more than once in {1}. Ignoring {2}
Explanation The same target specified multiple times for the same module is treated as a single target. Action Remove the duplicates from the target name.
ADMA5033E: The target server {0} specified for {2} is a part of cluster {1}, but cluster {1} is not specified in the list of targets.
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.
ADMA5034W: The server {0} mentioned in the copy.sessionmgr.servername options for installation does not exist in the configuration.
Explanation The server name is not valid. Action Make sure that the server exists.
ADMA5035E: The copy operation on the session manager of {0} failed, as the copy is {1}.
Explanation The copy made of the session manager settings is not of type SessionManager. Action More info at:
ADMA5036E: An exception {0} occurred while copying session manager settings from server {1}.
Explanation The previous message details the cause of this problem. Action Read the previous message to understand the probable cause.
ADMA5037I: The system is starting to back up the application at {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5038I: The system Completed the backup of the application at {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5039E: The node name cannot be null.
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.
ADMA5040E: The node name {0} does not exist in the configuration.
Explanation The node name is not valid. Action Specify the correct node name.
ADMA5041E: The application {0} that is listed in the server index entry for node {1} cannot be found.
Explanation The serverindex.xml file for the given node is incorrect. Action More info at:
ADMA5042E: Targets {0} are not found in the repository. Server index entries for these targets are not updated.
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 More info at:
ADMA5043I: Module {0} is bound to server {1}.
Explanation This informational message describes the program status. Action No user action is required.
ADMA5044I: Application {0} is bound to node {1}.
Explanation This informational message describes the program status. Action No user action is required.
ADMA5045E: The application name {0} cannot be found under any cell in the repository.
Explanation The application does not exist. Action Check the application name. Look for typographical errors.
ADMA5046E: No cell name is specified in the options table that is passed as a parameter to the intallApplication API. The cell name is looked for in the module to server mapping specified using the AppConstants.APPDEPL_MODULE_TO_SERVER key in the options table and then in the value that corresponds to the AppConstants.APPDEPL_CELL key in the options table.
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 More info at:
ADMA5047E: The cell name {0} does not exist in the configuration.
Explanation The cell name is not valid. Action Check the cell name. Look for typographical errors.
ADMA5048E: No cell name is specified in the input parameters.
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).
ADMA5049E: The binary data for the EAR file of application {0} cannot be located either in the repository at context {1} or on the disk at {2}.
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...
WAS_HOME/config/cells/cellName/applications/appName.ear/Action More info at:
ADMA5050E: An unacceptable number format for the reload interval is detected. The specified value {0} is not a valid long value.
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.
ADMA5051W: An unacceptable value {0} for the class loader policy is detected. The default MULTIPLE is used.
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.
ADMA5052W: A value that is not valid {0} is detected for the class loading mode. The default, PARENT_FIRST, is used.
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.
ADMA5053I: The library references for the installed optional package are created.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5054E: The InstalledOptionalPackage deployment task failed on {0}: {1}
Explanation This message indicates that the InstalledOptionalPackage installation task failed during application installation. Prior messages detail the cause of this failure. Action More info at:
ADMA5055E: Errors in validating application target association for {0} - {1}
Explanation Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. Action More info at:
ADMA5056E: Error in installing application {0}
Explanation Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. Action More info at:
ADMA5057E: Application validation failed with an unexpected exception while checking module to server relationship: {0}
Explanation Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. Action More info at:
ADMA5058I: Application and module versions are validated with versions of deployment targets.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5059E: Errors in validating resource usage for application {0} - {1}
Explanation Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. Action More info at:
ADMA5060E: Resource validation for application {0} failed due to unexpected exception {1}
Explanation Messages before this error detail the cause of the failure. Typically the error conditions include wrong application type or wrong module targets. Action More info at:
ADMA5061W: The resource JNDI table is not created yet; call gatherJNDINames first.
Explanation No resource JNDI table is created. Need to call gatherJNDINames first. Action Make sure that the gatherJNDINames is called first.
ADMA5062W: An error occurred while reusing the existing deployment.xml file. The original deployment settings are not reused."
Explanation A problem occurred getting the existing deployment resource. Action Edit the application to restore any previous deployment settings.
ADMA5063W: Wrong input for recycle behavior. {0} is specified as recycle option, but modules to recycle are not supplied using key {0}.
Explanation Recycle option does not match input. Action More info at:
ADMA5064I: FileMergeTask completed successfully for {0}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5065E: Exception in FileMergeTask {0}.
Explanation See the exception for causes of the error. Action More info at:
ADMA5066E: Error validate application {0} : {1}.
Explanation See messages for cause of error. Action More info at:
ADMA5067I: Resource validation for application {0} completed successfully.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5068I: The resource validation for application {0} completed successfully, but warnings occurred during validation.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5069E: The installation of application {0} failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WAS configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.
Explanation Prior messages detail the cause of this failure. Action Read the previous message to rectify the problem.
ADMA5070E: The serverindex.xml for node {0} is empty. The operation cannot be completed. Save the log files and report this problem.
Explanation See message for the cause of the error. Action Save the log files and report the problem.
ADMA5071I: Distribution status check started for application {0}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5072I: Distribution status check completed for application {0}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5073E: An incorrect shared library string is specified - {0}
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.
ADMA5074W: The application {0} has web modules with a version 2.5 deployment descriptor and EJB content. The product treats these modules as version 3.0 web modules. Deploy them only to version 8 or later nodes. The modules are: {1}.
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 We must target each of the specified modules to a node at version 8 or later.
ADMA5075I: Editing of application {0} started.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5076I: Application {0} edited successfully. The application or its web modules may require a restart when a save is performed.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5077E: Editing of application {0} failed.
Explanation Prior messages detail the cause of this failure. Action Read the previous message to rectify the problem.
ADMA5078I: Update of {0} has started.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5079I: Update of {0} has ended. The application or its web modules may require a restart when a save is performed.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5080E: Update of {0} has ended. The update failed.
Explanation Prior messages detail the cause of this failure. Action Read the previous message to rectify the problem.
ADMA5081I: The bootstrap address for client module is configured in the WAS repository.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5082E: Error configuring the bootstrap address for application {0} - {1}
Explanation See the exception for causes of the error. Action More info at:
ADMA5083E: Unexpected exception while looking for application client extension.
Explanation While attempting to look for application client for module update, the indicate expcetion occurred. Action More info at:
ADMA5102I: The configuration data for {0} from the configuration repository is deleted successfully.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5103E: The deletion of the configuration data for {0} from the configuration repository failed.
Explanation The uninstall procedure failed to delete the application configuration data successfully. The application is still uninstalled. Action More info at:
ADMA5104I: The server index entry for {0} is updated successfully.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5105E: Updates to the server index entry failed for the last node in {0}
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 More info at:
ADMA5106I: Application {0} uninstalled successfully.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA5107E: The application {0} cannot be uninstalled.
Explanation An unexpected exception occurred during installation. Action Read the previous error messages for details.
ADMA5108E: Application {0} cannot be uninstalled because it does not exist in the WAS configuration.
Explanation An application name does not exist. Action Make sure that the application name is correct.
ADMA5109E: Unexpected exception {0} deleting edition configuration properties for {1}
Explanation While attempting to delete edition properties for the specified application, the indicate exception occurred. Action More info at:
ADMA5110I: The application {0} is installed as a hidden application and will not be exposed via administrative interfaces such as GUI client, wsadmin or MBean Java API. In order to perform management operations on this application, the application name must be known.
Explanation This information message indicates the program status. Action No user action is required.
ADMA5111E: The deployment.xml file could not be found in the expanded application directory while installing as a system application
Explanation Deployment.xml file does not exist Action Make sure the deployment.xml file exists
ADMA5112E: An error occurred creating an activation plan for the application - {0}
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.
ADMA5113I: Activation plan created successfully.
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.
ADMA5114I: Property-based configuration file successfully applied.
Explanation The property-based configuration file (META-INF/ibm-was-config.props) has been applied to the application. Action No user action is required.
ADMA5115E: An unexpected exception occurred while applying the property-based configuration file. Exception: {0}
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.
ADMA6001I: Begin the application preparation -
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6002I: The options used are:
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6003I: Reading the local EAR file ...
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6004I: The preferences for default bindings:
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6005I: Checking the filter.policy file on server ...
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6006I: ...... Saving the local EAR file ...
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6007I: Proceeding with local installation.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6008I: Installation event received:
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6009I: Processing is complete.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6010I: The tasks are {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6011I: Deleting directory tree {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6012I: Exception in run {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6013I: Extract application binaries at {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6014I: The cell name is {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6015I: Module {0} is being installed on {1}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6016I: Add to workspace {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6017I: The document {0} is saved.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6018I: The node-server relationship for this application is {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6019I: The node-serverIndex document relationship for this application is {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6020I: The system is adding the serverindex entry for {0} for server {1} on node {2}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6021I: Removing the serverindex entry for {0} for server {1} on node {2}, and the return code is {3}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6022E: Uri {0} conflicts with existing uri {1} in the application"
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.
ADMA6051I: Begin the application uninstall.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6052I: Proceeding with the local uninstall ...
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6053I: Uninstall event received:
Explanation This informational message indicates the program status. Action No user action is required.
ADMA6054I: Application installation deployment targets exist in different node groups {0}
Explanation This informational message indicates the program status. Action No user action is required.
ADMA7000W: An unexpected exception occurred during onChangeStart processing: {0}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7001W: An unexpected exception occurred in checking if {0} is an application EAR file: {1}. This file might not be synchronized properly, that is the application binaries might not get placed correctly.
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7002E: An unexpected exception {0} occurred in building the cache for application synchronization from the serverindex.xml file. The application synchronization logic does not work for deletions or modifictions of binaries in this case.
Explanation The exception message might detail a probable cause. Action If an application EAR file is not expanded to the destination specified during installation, use the EARExpander tool to expand the EAR file.
ADMA7003E: A malformed server index entry {0} exists. The correct form for the entry is appName.ear/deployments/appName. The application binary corresponding to this entry might not be changed upon completion of the task.
Explanation The entry for deployedApplication in the serverindex.xml file is bad. Action More info at:
ADMA7004E: An unexpected exception occurred while building the cache entry for {0} and {1}. The exception is: {2}. All the related binaries might not be changed.
Explanation The exception message might detail a probable cause. Action If an application EAR file is not expanded to the destination specified during installation, use the EARExpander tool to expand the EAR file.
ADMA7005E: An unexpected exception occurred while loading resource {0} from the repository. This error causes problems in using this resource for application synchronization logic.
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7006E: An unexpected exception occurred in onChangeCompletion processing: {0}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7007E: An unexpected exception occurred in postProcess processing ID={1}: {0}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7008E: An unexpected exception occurred for the expandEar command. The EAR file {0} is not extracted in the following paths {1}. Exception: {2}
Explanation The disk might be full, or the directory might not have write permission. Action Use the EARExpander tool to extract the EAR file.
ADMA7009E: An exception {0} occurred when deleting directory {1}
Explanation The exception message might detail a probable cause. Action Delete the directory manually.
ADMA7010E: An unexpected exception occurred when calling an external security provider at application installation time {0}. The exception is {1}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7011E: An unexpected exception occurred when calling an external security provider at application uninstallation time {0}. The exception is {1}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7012E: An unexpected exception occurred when calling an external security provider at application uninstallation time. The exception is {0}
Explanation The exception message might detail a probable cause. Action More info at:
ADMA7013W: Enabling the Cluster ripple option requires that you also enable the Distribute binaries option.
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.
ADMA7014E: The Cluster ripple option cannot be specified when the target cluster is on node: {0} which has auto-sync enabled.
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.
ADMA7015W: Unexpected exception {0} in {1} for fileURI {2}. This file might not be synchronized properly and the application binaries might not get placed correctly.
Explanation The exception message might detail the probable cause. Action More info at:
ADMA7016W: Unexpected exception {0} in {1} to build VariableMap. This file might not be synchronized properly and the application binaries might not get placed correctly.
Explanation The exception message may detail probable cause. Action More info at:
ADMA7017W: The event type: {0} is not valid.
Explanation Received an unexpected repository event type. Action No user action is required.
ADMA7018W: Malformed file list in {0}. No <file> tag found under <files>.
Explanation The delta.xml file is malformed. Action More info at:
ADMA7019E: ERROR: {0} value in AppDataMgr for application {1} is not meaningful. AppData creation might fail, application binary may not be placed correctly.
Explanation Missing data in the application binary synchronization process. Action If an application EAR file is not expanded to the destination specified during installation, then use the EARExpander tool to expand the EAR file.
ADMA7020E: Error processing delta files {0}.
Explanation Application update changes might not be sychronized, recycle behavior might be unexpected. Action More info at:
ADMA7021I: Distribution of application {0} completed successfully.
Explanation This informational message indicates the distribution status of the application. Action No user action is required.
ADMA7022E: Distribution of application {0} failed with exception {1}.
Explanation An unexpected failure occurred during application distribution. Application distribution tasks will not be executed. Action See FFDC for more information.
ADMA7023E: Distribution of application {0} failed. Task {1} failed.
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.
ADMA7024E: Distribution of application {0} failed. Task {1} failed with exception {2}.
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.
ADMA7030E: Unable to obtain NotificationService MBean in {0} process to emit application distribution notifications.
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.
ADMA7100E: A validation error occurred in task {0}. The reload interval, {1}, is not valid. A reload interval must be an integer from 0 to 2147483647.
Explanation The exception message might detail a probable cause. Action Specify an integer within the valid range.
ADMA7101E: An unexpected error occurred for the EAR expansion process. The EAR file {0} is not extracted in the following paths {1}. On node: {2}
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.
ADMA7102E: Resource conflict detected for resources with the name {0} between application resources in {1} and {2}.
Explanation JNDI strings must be unique within a given scope. Action Modify the JNDI strings to be unique for each application resource.
ADMA7103W: Resource conflict detected. Applications {0} and {1} define conflicting resources with the name {2}. The problem must be resolved before the session is saved.
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.
ADMA7104E: Resource conflict detected. Applications {0} and {1} define conflicting resources with the name {2}. The application configuration cannot be saved.
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.
ADMA8000I: Application ripple of application {0} is successful.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8001E: Application ripple of application {0} failed.
Explanation An unexpected exception occurred during cluster update. Action Read previous error messages for further details.
ADMA8002I: Application ripple of application {0} started.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8003I: Stopping server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8004I: Stopped server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8005I: Synchronizing node {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8006I: Synchronized node {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8007I: Starting server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8008I: Started server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8009I: Server {0} is not responding. It will not be started during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8010I: Server {0} failed to start during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8011I: Synchronization of node {0} failed during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8012I: Cluster update of node {0} failed during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8013I: Application ripple of applications {0} is complete.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8014I: Application ripple of applications {0} failed.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8015I: Application ripple of applications {0} failed. The exception is {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8016I: Application ripple might not be complete. Targets {0} are not found in the repository.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8017W: Cluster ripple does not function without Synchronize changes with nodes selected.
Explanation The Cluster ripple option requires that Synchronize changes with Nodes be selected. Action To use the Cluster ripple option, select Synchronize changes with nodes.
ADMA8018W: Resources that are assigned to the application are beyond deployment target scope.
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, or continue to move on.
ADMA8019E: The resources that are assigned to the application are beyond the deployment target scope. Resources are within the deployment target scope if they are defined at the cell, node, server, or application level when the deployment target is a server, or at the cell, cluster, or application level when the deployment target is a cluster. Assign resources that are within the deployment target scope of the application or confirm that these resources assignments are correct as specified.
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.
ADMA8020I: Applications {1} failed to start during application ripple on server {0}.
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.
ADMA8021I: No target server found for application {1}.
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.
ADMA8022I: Pausing server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8023I: Paused server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8024I: Resuming server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8025I: Resumed server {0} to perform application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8026I: Server {0} failed to pause. This server will not be resumed during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8027I: Server {0} failed to resume during application ripple of application {1}.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA8028I: The {0} application has been successfully expanded on the {1} node.
Explanation This message is for informational purposes only. Action No action is required.
ADMA8029E: The expansion of the {0} application has failed on the {1} node.
Explanation The application failed to expand to the destination for the installed 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.
ADMA8030W: The {0} application did not expand on the {1} node within the expected amount of time.
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 dmgr. For more information on this property, see the product documentation..
ADMA8031I: The application expansion will occur as a background process on the {0} node.
Explanation If the servers are not intend to start, the application expansion process will occur as a background process. Action No action is required.
ADMA8032E: Unable to get the {0} application expansion status on {1} node.
Explanation If the servers are not intend to start, the application expansion process will occur as a background process. Action No action is required.
ADMA8033I: The node {0} is already synchronized.
Explanation The node is already synchronized. Application ripple will skip node synchronization. Action No action is required.
ADMA9000E: We cannot install an application across multiple security domains. Make sure that all the deployment targets belong to the same security domain.
Explanation Application cannot be installed accross multiple security domains. Action Verify that user is not installing this application accorss multiple security domains.
ADMA9001E: Installation of system application < {0} > failed because there is already a system application with that name.
Explanation This informational message indicates the program status. Action No user action is required.
ADMA9002E: Installation of application failed because LightweightLocal is set in {0} and target node is prior to 6.1
Explanation This informational message indicates the program status. Action No user action is required.
ADMA9003E: The {0} destination directory cannot be found in the EAR file.
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.
ADMA9004E: The {0} external binding file cannot be found.
Explanation The external binding file cannot be found. Action Verify that the binding file is available on the file system.
ADMA9005E: Cannot associate Access Ids {0} with mapped user/group {1} because of incompatible length.
Explanation Access ids should have one to one mapping to the user/group. Action Validate the entries and retry.
ADMA9006E: The application failed to install. The {0} application is not licensed to be installed in this server under the {1} product.
Explanation The application is not licensed to be installed on this server. Action Verify that the application is licensed.
ADMA9007I: The application server is running in a restricted mode under the {0} product.
Explanation The product name is registered. Action No action is required.
ADMA9008E: The application server is running in a restricted mode. The {0} application management operation is not available in the application server installation.
Explanation The application cannot be installed or updated without a full application server license. Action Do not call the API for application management that update applications in this installation environment.
ADMA9010E: Installation failed due to missing required parameters for properties based configuration.
Explanation We 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.
ADMA9011E: Runtime provisioning component(s) {0} are malformed.
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.
ADMA9012E: {0} is not a valid operation parameter for a full application update.
Explanation A full application update only takes "update" as a parameter to the operation option. Action Specify the correct parameter for the operation option.
ADMA9013E: Runtime provisioning component(s) {0} cannot be specified as patterns or contain multiple key-property values.
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.
ADMA9014E: Runtime provisioning component(s) {0} must have a domain of "WebSphere".
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.
ADMA9015E: Runtime provisioning component(s) {0} must have a key of "specname".
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.
ADMA9016E: A validation error occurred in task {0}. No valid value was specified for properties file variable {1}.
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.
ADMA9998W: Unable to delete {0}.
Explanation The indicated file or directory could not be deleted. Action Manually delete the indicated file or directory.
ADMA9999W: Unable to delete {0}. Exception: {1}
Explanation An unexpected exception occurred deleting the indicated file or directory. Action Manually delete the indicated file or directory.