Application Deployment messages

ADMA0001E: A Validation error occurred in task {0}. The listener port name is not specified for the enterprise bean {1} in module {2}.
Explanation: There is message-driven enterprise bean in the application. The required listener port name for the message-driven enterprise bean does not have a value.
User Response: Specify the listener port value for the message-driven bean in the task listed in the error message.

ADMA0002E: A Validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean {1} in module {2}.
Explanation: There is a non-message-driven bean found in the application. The required JNDI name for the non-message-driven bean does not have a value.
User Response: Specify the JNDI name for the non-message-driven bean in the task listed in the error message.

ADMA0003E: A Validation error occurred in task {0}. The isolation level is not specified for reference binding {1} in module {2}.
Explanation: A resource reference to an Oracle resource provider is in the applicaiton. The required isolation level for Oracle does not have a value.
User Response: Specify the isolation level for the resource reference in the task listed in the error message.

ADMA0004E: A Validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for module {1} with URI {2}. The data source must be specified for each container-managed persistence (CMP) bean belonging to this module.
Explanation: The application contains an Enterprise JavaBean (EJB) 1.x. The data source JNDI name in both the module and the CMP bean level is not specified. You have to specify the JNDI name in at least one level. If you specify the data source JNDI name in the module level, then you do not have to specify the data source JNDI name for each CMP bean in that module unless you wish to overwrite the one set in the module level. If you do not specify the data source JNDI name in the module level, then you have to specify it for each CMP bean in that module.
User Response: 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".
User Response: Specify the correct value for resource authorization in the module 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 applicaiton. 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.
User Response: Specify the correct protection value in the module and task listed in the error message.

ADMA0007E: A Validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for reference binding {1} in module {2} with EJB name {3}.
Explanation: There is an EJB or resource reference (or both references) in the application. The JNDI name field required to bind the reference does not have a value.
User Response: Specify the JNDI name for the reference in the task 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 reference binding {1} in module {2}.
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.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0010E: A Validation error occurred 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.
User Response: Specify the virtual host for the Web module that is listed in the error message.

ADMA0012E: The task helper for task {0} cannot be located.
Explanation: An error has occurred in setting up the tasks for the application.
User Response: 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 has occurred in setting up the tasks for the application.
User Response: Verify that the installation task object, if provided by the task provider, are set up correctly.

ADMA0014E: Validation failed. {0}
Explanation: A validation error has occurred in preparing the application. This message is followed by a detailed error message.
User Response: 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.
User Response: Enter the data again in the task preparing the application. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: If this error occurs when you use the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. If you are using these functions programmatically, make sure that the application name is not null.

ADMA0017E: The context for {0} cannot be obtained.
Explanation: The application name supplied in edit functions such as getApplicationInfo, getModuleInfo, exportApplication, and extractDDL is not an installed application name.
User Response: If this error occurs when you use the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. If you are using these functions programmatically, make sure that the application with the given name is installed.

ADMA0019E: An attempt to get the enterprise archive (EAR) file for {0} failed.
Explanation: For the listModules or extractDDL functions, the application management logic cannot obtain the EAR file that is stored in the WebSphere Application Server configuration.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0020E: An error occurred backing up the enterprise archive (EAR) file - {0}
Explanation: An error occurred while copying the EAR file to the configuration repository.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0021E: An error occurred in compiling JavaServer Pages (JSP) files - {0}
Explanation: An error occurred while compiling JSP files in a Web application archive (WAR) file.
User Response: 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.
User Response: Validate your application using the Application Server Toolkit.

ADMA0025E: An incorrect isolation level was 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).
User Response: Enter the correct value for the isolation level field in the resource reference that is 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).
User Response: Enter the correct value for the isolation level field.

ADMA0027E: An incorrect task data format is detected: The Java Naming and Directory Interface (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.
User Response: Specify the data source for the CMP bean that is specifed 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.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: Enter the correct value for the resource authorization in the CMP bean that is 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.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: Specify an existing security role name.

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=,node=,server=" and "WebSphere:cell=,cluster=" for server and cluster respectively.
User Response: 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.
User Response: If the problem persists, validate your 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.
User Response: If the problem persists, validate your 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.
User Response: If the problem persists, validate your 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.
User Response: If the problem persists, validate your 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.
User Response: If the problem persists, validate your application using the Application Server Toolkit.

ADMA0041E: The local enterprise archive (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.
User Response: Verify that the EAR path is not null if this API is called programmatically. If this error is displayed by the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: Verify that the properties table is not null if this API is called programmatically. If this error is displayed by the wsadmin tool or the UI, then see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0043E: {0} does not exist for installation.
Explanation: The enterprise archive (EAR) file path that is provided to the installApplication API for the AppManagement MBean does not contain a file.
User Response: Verify that the file exists at the specified location. If this error is displayed by the wsadmin tool or the UI, then see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0044E: An error occurred scheduling the installation for {0}
Explanation: An unexpected exception occured during installation.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0045E: The application name cannot be null.
Explanation: The application name passed to the checkIfAppExists or the uninstallApplication APIs of the AppManagement MBean is null.
User Response: If these APIs are called programmatically, verify that the name is not null; otherwise, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0048E: An unknown module is encountered- {0}
Explanation: The module parameter that passes to the getModuleInfo API of the AppManagement MBean is not valid.
User Response: Make sure that the module parameter is a string that has a value of moduleURI+ddURI. If this error is displayed by the wsadmin tool or the UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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 enterprise archive (EAR) file. The unique URI is moduleURI+ddURI
User Response: If the getApplicationInfo or the getModuleInfo API on the AppManagement MBean is called programmatically, verify that the parameter passed in is correct. If this error is displayed using the wsadmin tool or the administration client UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0053E: An error occurred closing the enterprise archive (EAR) file {0}
Explanation: This exception occurs during application installation processing if the enterprise archive (EAR) file gets locked because of an unexpected error, and cannot be closed. Application installation is stopped when this error occurs.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0054E: An exception occurred checking appication existence - {0}
Explanation: An unexpected exception occured in checking the existence of the application during application uninstallation so the uninstallation is not proceeding. This problem can also occur if the application to be uninstalled does not exist in the configuration.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0056E: An incorrect task data format is detected; the Java Naming and Directory Interface (JNDI) data is missing in module {0}
Explanation: An error occurred in preparing the application. The default data source for a Java archive (JAR) file is not specified.
User Response: Specify the default data source for the JAR file that is specifed 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 Java archive (JAR) file has incomplete data.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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 Java archive (JAR) file is not specified correctly. The correct values are per application or container.
User Response: Enter the correct value for the resource authorization in the JAR file that is 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 Java archive (JAR) file contains incomplete data.
User Response: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0062E: The enterprise bean deployment options cannot be found.
Explanation: This exception occurs when the properties table that passes to the installApplication API of the AppManagement MBean specifies that the EJBDeploy program that runs as a part of an installation does not specify options for the EJBDeploy program.
User Response: If the installApplication API is called programmatically, verify that the hash table for EJBDeploy options is passed in as one of the entries in the properties table. If this exception is displayed by the wsadmin tool or the administration client UI, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0063E: An error occurred in EJB deployment - {0}
Explanation: A previous message from the application installation details the error that occurred during the EJBDeploy program.
User Response: Verify that the enterprise bean Java archive (JAR) file that is assembled with the application is a valid and deployable JAR file.

ADMA0064E: An error occurred when extracting the enterprise archive (EAR) file.
Explanation: An unexpected exception occurred during EAR file expansion.
User Response: Verify that enough disk space is available for the EAR file to extract completely, and that the proper file permissions are set to both the temp directory and the directory that is specified as the installation destination. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

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.
User Response: Refer to the previous messages in the log file for a failure description. If no messages are displayed, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: 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.
User Response: If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: 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.
User Response: No user action is required if no security concerns exist. Otherwise, validate your 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.
User Response: No user action is required if no security concerns exist. Otherwise, validate your 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 your application again.
Explanation: WebSphere Application Server attempts to prevent applications from performing security-sensitive operations, like calling the System.exit() method, replacing the Java 2 Security manager, and replacing the Java 2 Security policy. If the application is granted the all permissions (java.security.AllPermission), the Java 2 Security permission checks are effectively disabled, which can compromise the integrity of the system.
User Response: Review the application policy, which is located in the EAR/META-INF/was.policy file, remove the security-sensitive permissions and grant the application only the permissions that are required.

ADMA0073W: Custom permissions are found in the {0} policy file. Custom permissions can compromise the integrity of Java 2 Security.
Explanation: The implementation of custom permissions can weaken the integrity of the Java 2 Security permission check.
User Response: Review both the application policy, which is located in the EAR/META-INF/was.policy file, and the implementation of custom permissions.

ADMA0074E: A validation error occurred in task {0}. The Java Naming and Directory Interface (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. You must specify the data in at least one level. If you specify the data source data in the module level, then you do not have to specify it for each CMP bean in that module unless you want to overwrite the one set in the module level. If you do not specify the data source data in the module level, then you have to specify it for each CMP bean in that module.
User Response: 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: {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 the wsadmin tool (except when the -local option is used) or the administration client UI.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0078W: The file: {0} cannot be deleted.
Explanation: An error occurred when deleting a file or a directory.
User Response: Verify that the disk is not write-protected. If not, manually delete the file or directory 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 appear in the class path.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application. You 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.
User Response: No user action is required if no security concerns exist. Otherwise, modify the was.policy file in the location that is specified in the warning message about setting up a security permission. For syntax of the was.policy file, refer to the dynamic policy section of the information center.

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.
User Response: No user action is required if security is not enabled. Otherwise, include a was.policy file in your application before reinstalling the application.

ADMA0082E: Your application contains the following incompatible Java archive (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 enterprise archive (EAR) file contains a J2EE 1.3 module.
User Response: Verify that the EAR file is a J2EE-compliant EAR file.

ADMA0083E: The file or directory {0} that is specified as an enterprise archive (EAR) file is not valid.
Explanation: The application specified is not a valid EAR file.
User Response: Verify that the correct application file is entered. Otherwise, validate your 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.
User Response: 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 leading dot, can not have leading or trailing spaces and cannot contain any of the following characters: / , # $ @ : ; " * ? < > | = + & % ' ]]
Explanation: The specified application name contains an unacceptable character. An application name cannot begin with a leading dot, can not contain leading or trailing spaces and cannot contain any of the following characters: backward slash (\), slash (/), hash (#), dollar ($), at sign (@), $colon (:), asterisk (*), question mark (?), quotation marks ("), greater than sign (>), less than sign (<), pipe (|), semicolon (;), or comma (,), equal sign (=), plus (+), percent (%), ampersand (&), single quotation mark (') square brackets (]]).
User Response: Specify an application name that does not contain any of these unacceptable characters.

ADMA0086E: An error occurred from the EJBDeploy program: {0} [severity {1}]
Explanation: This message is written into the log file when an EJBDeploy error is encountered.
User Response: Examine the error message and the previous messages from the EJBDeploy program, to determine the source of the problem.

ADMA0087W: A warning is issued from the EJBDeploy program: {0} [severity {1}]
Explanation: This message is written into the log file when an EJBDeploy warning is encountered.
User Response: Examine the warning message and the 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 only be called in the local mode of the AppManagement MBean.
Explanation: Some of the application management functions can only be called if the AppManagement MBean runs in local mode, that is without connecting to a Java Management Extentions (JMX) process.
User Response: 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. If not, See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.
User Response: If this installation is a base WebSphere Application Server installation or a deployment manager process, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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 only be called if the AppManagement MBean runs in JMX mode; that is, the client must be connected to a server.
User Response: If this API is called programmatically, make sure that the AppManagementProxy object is created either using the getJMXProxyForClient or the getJMXProxyForServer method.

ADMA0091E: 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 error typically occurs when the bindings or extensions of an application or module have cross references to deployment descriptor artifacts, and those cross referenced IDs are not present in the deployment descriptor. This situation is most common when bindings or extensions are manually edited.
User Response: Edit the resource URI mentioned in the exception and fix the cross references.

ADMA0092E: An unexpected exception occurred while preparing task {0}. Check the server machine First Failure Data Capture tool (FFDC) for more information.
Explanation: An unexpected exception occurred while preparing the specified task.
User Response: See server machine FFDC for more information. Check the enterprise archive (EAR) file if the binding information is correct.

ADMA0093E: An unexpected exception occurred while completing task {0}. Check the server machine First Failure Data Capture tool (FFDC) for more information.
Explanation: An unexpected exception occurred while completing the specified task.
User Response: See server machine FFDC for more information. Check the enterprise archive (EAR) file if the binding information is correct.

ADMA0094E: An application management operation {0} is not available in your WebSphere installation.
Explanation: The user applications cannot be installed or updated without a full WebSphere Application Server license.
User Response: Do not call the application management APIs that update applications in this installation environment.

ADMA0095W: The current backend ID ({0}) that is specified in the ibm-ejb-jar-bnd.xmi file for enterprise bean Java archive (JAR) file ({1}) does not exist.
Explanation: The current backend ID that is specified in the ibm-ejb-jar-bnd.xmi file does not exist under the META-INF/backends directory.
User Response: Verify that the current backend ID (currentBackendId) that is specified in the ibm-ejb-jar-bnd.xmi file is correct. Look for a correct ID under the META-INF/backends directory of the specified Java archive (JAR) file.

ADMA0096I: The application management version key is found, but is not valid.
Explanation: A full WebSphere product installation is not available, or is corrupted.
User Response: No user action is required if you have an embedded WebSphere installation.

ADMA0097I: Application management is being initialized without a full product installation. All application management functions are not available.
Explanation: A full WebSphere product installation is not available to perform all of the application management functions.
User Response: No user action is required if you have an embedded WebSphere 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 that is specified in the ibm-ejb-jar-bnd.xmi file does not exist under the META-INF/backends directory.
User Response: 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 Java Naming and Directory Interface (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.
User Response: Specify the listener port or the JNDI name for the message-driven enterprise bean in the task listed in the error message.

ADMA0100E: A validation error occurred in task {0}. The Java Naming and Directory Interface (JNDI) name is not specified for connector {1} in module {2}.
Explanation: There is a connector module (resource archive, or RAR, file) embedded in the application. The required JNDI name for the connector does not have a value.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: Make sure that the shared library Java archive (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.
User Response: 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.
User Response: 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.
User Response: Verify that the connector modules or the RAR version is correct for the application.

ADMA0109W: The validate install input value: {0} is invalid. Please specify one of off/warn/fail value.
Explanation: Unexpected excetion occurred. Please take a look at the exception information.
User Response: This is a warning.

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.
User Response: 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.
User Response: 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.
User Response: Specify the required column in the task listed in the error message.

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.
User Response: 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.
User Response: Make sure that the resource JNDI name is correct for the resource.

ADMA0116W: Unable to start: {0} using: {1} exception is: {2}
Explanation: Unexpected exception occured.
User Response: This is a warning.

ADMA0117W: Unable to stop: {0} using: {1} exception is: {2}
Explanation: Unexpected exception occured.
User Response: This is a warning.

ADMA0118W: No MBean found for : {0}.
Explanation: Node MBean not found for application stop.
User Response: This is a warning.

ADMA0119E: Unexpected exception was thrown while getting the nodes objects in the cell {0}. Exception is {1}.
Explanation: Unexpected exception was thrown while getting the nodes objects in the cell.
User Response: Please investigate the original Exception.

ADMA0120E: Unexpected exception was thrown while getting the servers in the node {0}. Exception is {1}.
Explanation: Unexpected exception was thrown while getting the servers in the specified node.
User Response: Please investigate the original Exception.

ADMA0121E: Unexpected exception was thrown while getting the clusters in the cell {0}. Exception is {1}.
Explanation: Unexpected exception was thrown while getting the clusters in the specified cell.
User Response: Please investigate the original Exception.

ADMA0122E: Unexpected exception was thrown while getting the application {0}. Exception is {1}.
Explanation: Unexpected exception was thrown while getting the specified application scopes.
User Response: Please investigate the original Exception.

ADMA0123W: Unexpected exception was thrown while getting the attribute {0} of object {1}. Exception is {2}.
Explanation: Unexpected exception was thrown while getting the attribute of the specified object.
User Response: Please investigate the original Exception.

ADMA0124E: Unexpected exception was thrown while getting the Library object from the deployment.xml of the application {0}. Exception is {1}.
Explanation: Unexpected exception was thrown while getting the Library object from the specified application's deplyment.xml.
User Response: Please investigate the original Exception.

ADMA0125E: Cell name can not be null for installing or uninstalling system app {0}.
Explanation: System application installation/uninstallation needs a cell/node/server name.
User Response: Pass cell.name in the hashtable to AppManagement API

ADMA0126E: Node name can not be null for installing or uninstalling system app {0}.
Explanation: System application installation/uninstallation needs a cell/node/server name.
User Response: Pass node.name in the hashtable to AppManagement API

ADMA0127E: Server name can not be null for installing or uninstalling system app {0}.
Explanation: System application installation/uninstallation needs a cell/node/server name.
User Response: Pass server.name in the hashtable to AppManagement API

ADMA0128E: No cell name was passed to the installApplication API for installing {0}
Explanation: Cell name is picked up either from module to server mapping or from cell.name property.
User Response: Pass cell.name in the hashtable of properties to installApplication API.

ADMA0129W: Unable to get deployment.xml.
Explanation: MSG0001
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA0130E: Invalid content type {0} specified for updating {1}
Explanation: The content type can be file, module, partialapp or app.
User Response: Change the content type passed to updateApplication API.

ADMA0131E: Path to content must be specified when contenttype is partialapp for updating application.
Explanation: The content path is null in updateApplication API.
User Response: Specify pathToContents in updateApplication API.

ADMA0132E: Invalid operation {0} specfied for updating application {1}
Explanation: The operation type is invalid in updateApplication API.
User Response: Specify valid operation type - add, addupdate, update, delete.

ADMA0133E: Both Content URI and path to content must be specified for file or modulefile update.
Explanation: MSG0001
User Response: Specify content URI and path to content in updateApplication API.

ADMA0134E: Content does not exist at path {0} specified for file/modulefile update of {1}
Explanation: MSG0001
User Response: Make sure that the content path is correct.

ADMA0135E: Content URI must be specified for file or modulefile delete.
Explanation: MSG0001
User Response: Make sure that the content URI is specified.

ADMA0136E: Invalid content type {0} and/or operation {1}. Since {1} is installed using zero binary copy mode only modulefile can be used as content type and add or delete can be specified as operation.
Explanation: MSG0001
User Response: Use modulefile as content type for updating application and add or delete as operation.

ADMA0137E: Failed to load the resource-env-ref-type of {0}
Explanation: Failed to load of the specifiles name. There is a syntax error in ejb-jar.xml file.
User Response: Modify the syntax of of the specified name in ejb-jar.xml.

ADMA0138W: 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 wrong resource type.
User Response: Make sure that the resource type is correct for the resource.

ADMA0139W: 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 of wrong resource type.
User Response: Make sure that the resource type is correct for the resource.

ADMA4001I: Usage syntax: EARExpander -ear (name of the input EAR file for the expand operation or name of the output EAR file for the collapse operation) -operationDir (directory to which the EAR file is expanded or directory from which the EAR file is collapsed) -operation (expand | collapse) [-expansionFlags (all | war)]
Explanation: NONE
User Response: No user action is required.

ADMA4002E: The EARExpander command is missing a required argument: {0}
Explanation: One of the required arguments for the EARExpander command is missing. The required arguments are ear, operationDir, and operation.
User Response: Rerun the EARExpander command with the missing argument and its value.

ADMA4003E: EARExpander: The enterprise archive (EAR) file that is specified is not valid: {0}
Explanation: The specified EAR file is not valid. If you are performing an expand operation, the file does not exist, does not have read permission, or is not in the correct EAR format. If you are performing a collapse operation, the specified file is an existing file.
User Response: Rerun the EARExpander command with the correct EAR file specified.

ADMA4004E: EARExpander: The specified operation directory {0} is not valid.
Explanation: The specified operation directory is not valid. If you are performing a collapse operation, the specified directory does not exist, is not a directory, or the files in it are not in the correct EAR file format. If you are performing an expand operation, the specified directory is an existing file.
User Response: Rerun the EARExpander command with the correct operation directory specified.

ADMA4005E: EARExpander: The specified operation {0} is not valid.
Explanation: Check the command-line arguments to the EARExpander command.
User Response: Type EARExpander without any parameters to see command-line help.

ADMA4006I: Expanding {0} into {1}
Explanation: This informational message indicates that the EARExpander command is expanding an enterprise archive (EAR) file.
User Response: No user action is required.

ADMA4007I: Collapsing {0} into {1}
Explanation: This informational message indicates that the EARExpander command is collapsing a directory to an EAR file.
User Response: No user action is required.

ADMA4008E: EARExpander: Missing a value for the required argument "{0}"
Explanation: A value is not specified for the required argument of the EARExpander command.
User Response: Rerun the EARExpander command with a specified value for the required argument.

ADMA4009W: The expansion flag that is specified, {0}, is not valid. The program is ignoring this incorrect value and using a default value of "All".
Explanation: The expansion flag value that is specified is not valid. The default value "All" is used instead.
User Response: No user action is required if your intention is to expand the entire enterprise archive (EAR) file. Otherwise, rerun the EARExpander command and specify "war" as the expansion flag.

ADMA4010W: Both the listener port and the Java Naming and Directory Interface (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.
User Response: 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 Java Naming and Directory Interface (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.
User Response: 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 Java Naming and Directory Interface (JNDI) name is not specified for EJB: {1} in module: {2}. Please specify JNDI Name for the EJB.
Explanation: There is message driven EJB in the application, The required JNDI name for the message driven EJB does not have a value.
User Response: Specify the JNDI name for the message driven EJB in the task listed in the error message.

ADMA5001I: The application binaries are saved in {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA5002E: Application binaries cannot be saved in {0}: {1}
Explanation: As part of the application installation, the application enterprise archive (EAR) file is saved in the WebSphere Application Server configuration repository. This error message is displayed during installation if the EAR file cannot be saved.
User Response: Verify that enough disk space is available to save the EAR file, and check the file permissions. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5003I: The JavaServer Pages (JSP) files in the Web archive (WAR) files {0} compiled successfully.
Explanation: This information message indicates the program status.
User Response: No user action is required.

ADMA5004E: The JavaServer Pages (JSP) files in the Web archive (WAR) file {0} cannot be compiled; check the logs for more errors.: {1}
Explanation: The JavaServer Pages (JSP) files in the Web archive (WAR) modules of the enterprise archive (EAR) file have compilation errors.
User Response: Use the Application Server Toolkit to compile the JSP files and check for compilation errors.

ADMA5005I: The application {0} is configured in the WebSphere Application Server repository.
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA5006E: An error occurred configuring {0} in WebSphere Application Server repository: {1}
Explanation: Prior messages detail the cause of this failure. Typically, the error conditions include wrong server and node names that are specified as module targets during installation.
User Response: Read the error messages and rectify the problem.

ADMA5007I: The EJBDeploy command completed on {0}
Explanation: NONE
User Response: No user action is required.

ADMA5008E: EJBDeploy failed on {0}: {1}
Explanation: This message indicates that the EJBDeploy command has failed during application installation. Prior messages detail the cause of this failure.
User Response: Use the Application Server Toolkit to run the EJBDeploy command on the enterprise archive (EAR) file before installing it, and remove the causes of the EJBDeploy failures.

ADMA5009I: An application archive is extracted at {0}
Explanation: NONE
User Response: No user action is required.

ADMA5010E: An error occurred extracting the application at {0}: {1}
Explanation: The disk might be full or might be write-protected.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5011I: The cleanup of the temp directory for application {0} is complete.
Explanation: NONE
User Response: No user action is required.

ADMA5012I: The installed cleanup failed for {0}: {1}
Explanation: NONE
User Response: No user action is required.

ADMA5013I: Application {0} installed successfully.
Explanation: NONE
User Response: No user action is required.

ADMA5014E: The installation of application {0} failed.
Explanation: Prior messages detail the cause of this failure.
User Response: Read the previous message to rectify the problem.

ADMA5015E: Application {0} cannot be installed because it already exists in the WebSphere Application Server configuration.
Explanation: The application name must be unique in the WebSphere Application Server configuration.
User Response: Install the application with a different name.

ADMA5016I: Installation of {0} started.
Explanation: NONE
User Response: No user action is required.

ADMA5017I: Uninstallation of {0} started.
Explanation: NONE
User Response: No user action is required.

ADMA5018I: The EJBDeploy command is running on enterprise archive (EAR) file {0}.
Explanation: NONE
User Response: No user action is required.

ADMA5019E: The application name {0} is not valid. The application name cannot begin with a leading dot and cannot contain any of the following characters: / : * ? " < > | ; ,
Explanation: The specified application name contains an unacceptable character. An application name cannot begin with a leading dot and cannot contain any of the following characters: slash (/) (\), (:) colon, asterisk (*), question mark (?), quotation marks ", > (greater than sign), less than sign <, pipe |, semicolon (;), or comma (,).
User Response: Specify an application name that does not contain any of the unacceptable characters.

ADMA5020E: The target server {0} on node {1} that is specified for module {2} does not exist.
Explanation: An invalid target is specified for a module during application installation.
User Response: Verify that the specified target server exists.

ADMA5022E: The target cluster {0} specified for module {1} does not exist.
Explanation: An invalid target is specified for a module during application installation.
User Response: 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.
User Response: 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.
User Response: 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 WebSphere Application Server is WebSphere.
User Response: Correct the ObjectName format.

ADMA5026E: No valid target is specified in ObjectName {0} for module {1}.
Explanation: The target server or cluster that is specified for a module in the application installation does not exist. The target server name is specified as WebSphere:cell=cellName,node=nodeName,server=serverName. The target cluster name is specified as WebSphere:cell=cellName,cluster=clusterName.
User Response: Make sure 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.
User Response: 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.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5031E: The system cannot load {0} document for the object at {1}.
Explanation: The document is corrupt or empty.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5032W: The target {0} is specified more than once in {1}. Ignoring {2}
Explanation: The same target that is specified multiple times for the same module is treated as a single target.
User Response: 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.
User Response: 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.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5036E: An exception {0} occurred while copying session manager settings from server {1}.
Explanation: The previous message details the cause of this problem.
User Response: Read the previous message to understand the probable cause.

ADMA5037I: The system is starting to back up the application at {0}
Explanation: NONE
User Response: No user action is required.

ADMA5038I: The system Completed the backup of the application at {0}
Explanation: NONE
User Response: 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.
User Response: If the removeAllAppsFromNode API on the AppManagement MBean is called programmatically, then make sure that the node name passed in is not null. If the addNode utility displays this exception, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5040E: The node name {0} does not exist in the configuration.
Explanation: The node name is not valid.
User Response: Specify the correct node name.

ADMA5041E: The application {0} listed in the server index entry for node {1} cannot be found.
Explanation: The serverindex.xml file for the given node is incorrect.
User Response: Note the steps to recreate the problem and see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: If the targets that are specified in the message exist in the WebSphere Application Server configuration, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5043I: Module {0} is bound to server {1}.
Explanation: This informational message describes the program status.
User Response: No user action is required.

ADMA5044I: Application {0} is bound to node {1}.
Explanation: This informational message describes the program status.
User Response: 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.
User Response: Check the application name. Look for typographical errors.

ADMA5046E: No cell name is specified anywhere in the parameters passed to the installation API. The cell name is looked for in the module-to-server relation, and then in the AppConstants.APPDEPL_CELLNAME object.
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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5047E: The cell name {0} does not exist in the configuration.
Explanation: The cell name is not valid.
User Response: 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.
User Response: 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 enterprise archive (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 WebSphere Application Server configuration. This error message is displayed when the EAR file cannot be located in the WAS_HOME/config/cells/cellName/applications/appName.ear/ directory.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

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.
User Response: 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.
User Response: Verify that the class loader policy has one of the predefined values.

ADMA5052W: An invalid value {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.
User Response: 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: NONE
User Response: No user action is required.

ADMA5054E: The InstalledOptionalPackage deployment task failed on {0}: {1}
Explanation: This message indicates that the InstalledOptionalPackage installation task has failed during application installation. Prior messages detail the cause of this failure.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5055E: Errors in validating application target association for {0} - {1}
Explanation: Messages before this should detail cause of the failure. Typically the error conditions include wrong application type or wrong module targets.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5056E: Error in installing application {0}
Explanation: Messages before this should detail cause of the failure. Typically the error conditions include wrong application type or wrong module targets.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5057E: Application validation failed with unexpected exception while checking module to server relationship: {0}
Explanation: Messages before this should detail cause of the failure. Typically the error conditions include wrong application type or wrong module targets.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5058I: Application and module versions validated with versions of deployment targets.
Explanation: NONE
User Response: NONE

ADMA5059E: Errors in validating resource usage for application {0} - {1}
Explanation: Messages before this should detail cause of the failure. Typically the error conditions include wrong application type or wrong module targets.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5060E: Resource validation for application {0} failed due to unexpected exception {1}
Explanation: Messages before this should detail cause of the failure. Typically the error conditions include wrong application type or wrong module targets.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5061W: The Resource JNDI table has not created yet, please call gatherJNDINames first.
Explanation: No resource jndi table being created. Need to call gatherJNDINames first.
User Response: Make sure that the gatherJNDINames needs to be called first.

ADMA5062W: Error reusing existing deployment.xml. The original deployment settings will not be reused."
Explanation: Problem occured getting existing deployment resource.
User Response: Edit application to restore any previous deployment settings.

ADMA5063W: Wrong input for recycle behavior. {0} is specified as recycle option but modules to be recycled are not supplied using key {0}.
Explanation: Recycle option does not match input.
User Response: Read the error messages. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA5064I: FileMergeTask completed successfully for {0}.
Explanation: NONE
User Response: NONE

ADMA5065E: Exception in FileMergeTask {0}.
Explanation: See exception for cause of error.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA5066E: Error validate application {0} : {1}.
Explanation: See message for cause of error.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA5067I: Resource validation for application {0} completed successfully.
Explanation: NONE
User Response: NONE

ADMA5068I: The resource validation for application {0} completed successfully, but warnings occured during validation.
Explanation: None
User Response: No user action is required.

ADMA5069E: The installation of application {0} failed. This application was in the middle of a full update and therefore has been uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere configuration repository. The application has not been uninstalled from the WebSphere configuration repository. Until the current configuration session is discarded you will not see this application in the current session.
Explanation: Prior messages detail the cause of this failure.
User Response: Read the previous message to rectify the problem.

ADMA5070E: The serverindex.xml for node {0} is empty. The operation can not be completed. Please save log files and report this problem.
Explanation: See message for cause of error.
User Response: Please save log files and report the problem.

ADMA5071I: Distribution status check started for application {0}.
Explanation: NONE
User Response: NONE

ADMA5072I: Distribution status check completed for application {0}.
Explanation: NONE
User Response: NONE

ADMA5102I: The configuration data for {0} from the configuration repository is deleted successfully.
Explanation: This informational message indicates the program status.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5104I: The server index entry for {0} is updated successfully.
Explanation: This informational message indicates the program status.
User Response: 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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA5106I: Application {0} uninstalled successfully.
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA5107E: The application {0} cannot be uninstalled.
Explanation: An unexpected exception occured during installation.
User Response: Read the previous error messages for details.

ADMA5108E: Application {0} cannot be uninstalled because it does not exist in the WebSphere Application Server configuration.
Explanation: An application name does not exist.
User Response: Make sure that the application name is correct.

ADMA6001I: Begin the application preparation -
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6002I: The options used are:
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6003I: Reading the local enterprise archive (EAR) file ...
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6004I: The preferences for default bindings:
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6005I: Checking the filter.policy file on server ...
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6006I: ...... Saving the local enterprise archive (EAR) file ...
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6007I: Proceeding with local installation..
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6008I: Installation event received:
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6009I: Processing is complete.
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6010I: The tasks are {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6011I: Deleting directory tree {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6012I: Exception in run {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6013I: Extract application binaries at {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6014I: The cell name is {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6015I: Module {0} is being installed on {1}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6016I: Add to workspace {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6017I: The document {0} is saved.
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6018I: The node-server relationship for this application is {0}
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6019I: The node-serverIndex document relationship for this application is {0}
Explanation: This informational message indicates the program status.
User Response: 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.
User Response: 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.
User Response: No user action is required.

ADMA6051I: Begin the application uninstall -
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6052I: Proceeding with the local uninstall ...
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6053I: Uninstall event received:
Explanation: This informational message indicates the program status.
User Response: No user action is required.

ADMA6054I: Application installation deployment targets exists in different node groups {0}
Explanation: NONE
User Response: NONE

ADMA7000W: An unexpected exception occurred during onChangeStart processing: {0}
Explanation: The exception message might detail a probable cause.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA7001W: An unexpected exception occurred in checking if {0} is an application enterprise archive (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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

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.
User Response: If an application enterprise archive (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 serverindex.xml is bad.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

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.
User Response: If an application enterprise archive (EAR) file is not expanded to the destination that is specified during installation, use the EARExpander tool to expand the EAR file.

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.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA7006E: An unexpected exception occurred in onChangeCompletion processing: {0}
Explanation: The exception message might detail a probable cause.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA7007E: An unexpected exception occurred in postProcess processing ID={1}: {0}
Explanation: The exception message might detail a probable cause.
User Response: Consult the IBM WebSphere Application Server Support Web site at: http://www-3.ibm.com/software/webservers/appserv/support.html

ADMA7008E: An unexpected exception occurred for the expandEar command. The enterprise archive (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.
User Response: 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.
User Response: 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.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

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.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

ADMA7013W: Enabling the Cluster Ripple option requires that you also enable the Distribute Binaries option.
Explanation: To enable Cluster Ripple, Distribute Binaries must be enabled as well.
User Response: Enable Distribute Binaries if Cluster Ripple is required.

ADMA7014E: Cluster Ripple cannot be specified when target cluster is on node: {0} which has auto-sync enabled.
Explanation: Cluster Ripple cannot be specified when target cluster is on nodes that have auto-sync enabled.
User Response: Enable Distribute Binaries if Cluster Ripple is required.

ADMA7015W: Unexpected exception {0} in {1} for fileURI {2}. This file may not be synced up properly i.e. the application binaries may not get placed correctly.
Explanation: The exception message may detail probable cause.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA7016W: Unexpected exception {0} in {1} to build VariableMap. This file may not be synced up properly i.e. the application binaries may not get placed correctly.
Explanation: The exception message may detail probable cause.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA7017W: Invalid event type: {0}.
Explanation: Received unexpected repository event type.
User Response: NONE

ADMA7018W: Malformed file list in {0}. No tag found under .
Explanation: Malformed delta.xml file.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA7019E: ERROR: {0} value in AppDataMgr for app {1} is not meaningful. AppData creation may fail, application binary may not be placed correctly.
Explanation: Missing data in the application binary sync process.
User Response: If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMA7020E: Error processing delta files {0}.
Explanation: Application update changes may not be sychronized, recycle behavior may be unexpected.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

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.
User Response: Specify an integer within the valid range.

ADMA8000I: Application ripple of application {0} is successfull.
Explanation: NONE
User Response: NONE

ADMA8001E: Application ripple of application {0} has failed.
Explanation: Unexpected exception occured during cluster update.
User Response: Read previous error messages for further details.

ADMA8002I: Application ripple of application {0} has started.
Explanation: NONE
User Response: NONE

ADMA8003I: Stopping server {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8004I: Stopped server {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8005I: Synchronizing node {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8006I: Synchronized node {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8007I: Starting server {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8008I: Started server {0} to perform application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8009I: Server {0} is not responding, May be it is already stopped. This server will not be started during application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8010I: Server {0} failed to start during application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8011I: Synchronization of node {0} failed during application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8012I: Cluster update of node {0} failed during application ripple of application {1}.
Explanation: NONE
User Response: NONE

ADMA8013I: Application ripple of applications {0} has completed.
Explanation: NONE
User Response: NONE

ADMA8014I: Application ripple of applications {0} has failed.
Explanation: NONE
User Response: NONE

ADMA8015I: Application ripple of applications {0} has failed. The exception is {1}.
Explanation: NONE
User Response: NONE

ADMA8016I: Application ripple may not be complete. Targets {0} are not found in the repository.
Explanation: NONE
User Response: NONE

ADMA8017W: Cluster Ripple will not function without Synchronize changes with Nodes checked.
Explanation: Cluster Ripple requires that Synchronize changes with Nodes be checked.
User Response: If you want to use Cluster Ripple, check Synchronize changes with Nodes.

ADMA8018W: Resources assigned to application are beyond deployment target scope.
Explanation: Resources assigned to application are beyond deployment target scope.
User Response: 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 assigned to application are beyond deployment target scope.
User Response: Click cancel to return to the previous step and correct JNDI assignments, since Validate Install option FAIL was chosen, you will not be able to 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 displayed in the message.
User Response: Check the logs for reason of failure.

ADMA8021I: No target server found for application {1}.
Explanation: The applicaiton names supplied is not targetted on any servers.
User Response: The application name may be incorrect.