Application Deployment messages |
ADMA0001E: Validation error in task {0}
Listener port name is not specified for EJB {1} in module {2}.
Explanation:
There is message driven EJB in the application. The required listener port name for the message driven EJB does not have a value.
User Response:
Specify the listener port value for the message driven EJB in the task listed in the error message.
ADMA0002E: Validation error in task {0}
JNDI name is not specified for EJB {1} in module {2}.
Explanation:
There is non message driven EJB found in the application. The required JNDI name for the non message driven EJB does not have a value.
User Response:
Specify the JNDI name for the non message driven EJB in the task listed in the error message.
ADMA0003E: Validation error in task {0}
Isolation level is not specified for reference binding {1} in module {2}.
Explanation:
There is resource reference to an Oracle resource provider 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: Validation error in task {0}
JNDI name is not specified for module {1} with URI {2}. You have not specified the data source for each CMP bean belonging to this module. Either specify the data source for each CMP beans or specify the default data source for the entire module.
Explanation:
The application contains EJB 1.x. Data source JNDI name in both module and 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 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 CMP bean level.
ADMA0005E: Validation error in task {0}
Invalid resource authorization is specified for module {1} with URI {2}.
Explanation:
The application contains 2.x EJB that has resource authorization value for its data source. An incorrect value is specified for resource authorization. Correct value should be container or per connection factory.
User Response:
Specify the correct value for resource authorization in the module listed in the error message.
ADMA0006E: Validation error in task {0}
Invalidate protection value is specified for module {1} with URI {2}.
Explanation:
There is unprotected method in the applicaiton. Valid values for unprotected method for EJB 1.x module are leaving the entry as blank to keep the method as unprotected or deny all access. Valid values for unprotected method for EJB 2.x mothod is uncheck, exclude, or list of security role names.
User Response:
Specify the correct protection value in the module and task listed in the error message.
ADMA0007E: Validation error in task {0}
JNDI name is not specified for reference binding {1} in module {2}.
Explanation:
There is EJB and/or resource reference in the application. The required JNDI name field to bound the reference does not have a vallue.
User Response:
Specify the JNDI name for the reference in the task listed in the error message.
ADMA0008E: Validation error in task {0}
Hidden data to identify Oracle data source is not specified for reference binding {1} in module {2}.
Explanation:
There is resource reference in the application. The hidden required field to identify whether this resource reference to a Oracle provider does not have a value. This field is to be filled in by the client not by the user.
User Response:
If the problem persists, contain IBM support.
ADMA0010E: Validation error in task {0}
Virtual host is not specified for web module {1} with URI {2}.
Explanation:
The application contains 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 listed in the error message.
ADMA0012E: Unable to find task helper for task {0}
Explanation:
An error has occurred in setting up the tasks for the application.
User Response:
If the application install driver includes customerized tasks provided by the task provider, make sure the install task objects provided by the task provider are setup correctly.
ADMA0013E: Unable to find dependency helper for task {0}
Explanation:
An error has occurred in setting up the tasks for the application.
User Response:
If the application install driver includes customerized tasks provided by the task provider, make sure the install task objects provided by the task provider are setup correctly.
ADMA0014E: Validation failed.
{0}
Explanation:
An validation error has occurred in preparing the application. This message is followed by detailed error messages.
User Response:
Please see the detailed messages for details to correct the problem.
ADMA0015E: Incorrect task data format: incorrect length - {0}
Explanation:
An error has occurred in the task preparing the application.
User Response:
Re-enter the data in the task preparing the application. If the problem persists, contact IBM support.
ADMA0016E: Application name is null.
Explanation:
The application name passed in to the edit functions such as getApplicationInfo, getModuleInfo, exportApplication, extractDDL is null.
User Response:
If this error is thrown when you use wsadmin or UI then contact IBM support. If you are using these functions programmatically then make sure that the application name is not null.
ADMA0017E: Unable to obtain context for {0}
Explanation:
The application name supplied in edit functions such as getApplicationInfo, getModuleInfo, exportApplication, extractDDL is not an installed application name.
User Response:
If this error is thrown when you use wsadmin or UI then contact IBM support. If you are using these functions programmatically then make sure that the application with given name is installed.
ADMA0019E: Unable to get ear file for {0}
Explanation:
For listModules or extractDDL functio, the application management logic can not obtained the ear file stored in the WebSphere configuration.
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.
ADMA0020E: Error backing up the ear - {0}
Explanation:
Error copying the ear file to configuration repository.
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.
ADMA0021E: Error in compiling jsps - {0}
Explanation:
Error compiling jsps in a WAR file.
User Response:
Make sure that the jsps do not have any code that does not compile.
ADMA0024E: Incorrect dependency task {0}
Explanation:
An error has occurred in the Correct Oracle Isolation Level task while preparing the application.
User Response:
If the problem persists, validate your application using Application Assembly Tool.
ADMA0025E: Incorrect isolation level for resource ref {0} for module {1}
Explanation:
An error has occurred in preparing the application. The value to specify isolation level for 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 specified in the error message.
ADMA0026E: Isolation level not in number format - {0}
Explanation:
An error has occurred in preparing the application. The value to specify isolation level for 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: Incorrect task data format: missing JNDI name for data source for EJB {0} in module {1}
Explanation:
An error has occurred in preparing the application. Data source for a CMP bean is not specified.
User Response:
Specify the data source for the CMP bean specifed in the error message.
ADMA0028E: Incorrect task data format: missing user/passowrd data for EJB {0} in module {1}
Explanation:
An error has occurred in preparing the application. Data source for a 1.x CMP bean has incomplete data.
User Response:
If the problem persists, contact IBM support.
ADMA0029E: Incorrect task data value for resource authorization for EJB {0} in module {1}.
Correct value can be per connection factory or container.
Explanation:
An error has occurred in preparing the application. Resource authorization value for a CMP bean is not specified correctly. Correct values are per connection factory or container.
User Response:
Enter the correct value for the resource authorization in the CMP bean specified in the error message.
ADMA0030E: Incorrect task data format: missing resource authorization data for EJB {0} in module {1}
Explanation:
An error has occurred in preparing the application. Connection factory for a 2.x CMP bean has incomplete data.
User Response:
If the problem persists, contact IBM support.
ADMA0031E: Unable to find matching security role for role name {0}
Explanation:
An error has occurred in preparing the application. The security role name entered does not exist. You may have a typo in the role name specified.
User Response:
Specify an existing security role name.
ADMA0033E: Incorrect server string specified - {0}
Explanation:
An error has occurred in preparing the application. The server string specified has incorrect format. The correct format should be "WebSphere:cell=
User Response:
Specify the correct server string.
ADMA0034E: Error getting role assignment
Explanation:
An error has occurred in the Mapping Users to Roles task while preparing the application.
User Response:
If the problem persists, validate your application using Application Assembly Tool.
ADMA0035E: Null pointer exception when getting local methods for {0}
Explanation:
An error has 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 Assembly Tool.
ADMA0036E: Null pointer exception when getting home methods for {0}
Explanation:
An error has 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 Assembly Tool.
ADMA0037E: Null pointer exception when getting local home methods for {0}
Explanation:
An error has 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 Assembly Tool.
ADMA0038E: Null pointer exception when getting remote methods for {0}
Explanation:
An error has 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 Assembly Tool.
ADMA0041E: localEarPath can not be null for installApplication.
Explanation:
The ear file path supplied to the installApplication API for AppManagement MBean is null.
User Response:
Make sure that the ear path is not null if this API is called programmatically. If this error is shown by wsadmin or UI then contact IBM support.
ADMA0042E: properties can not be null for installApplication.
Explanation:
The properties table supplied to the installApplication API for AppManagement MBean is null.
User Response:
Make sure that the properties table is not null if this API is called programmatically. If this error is shown by wsadmin or UI then contact IBM support.
ADMA0043E: {0} does not exist for installation.
Explanation:
The ear file path provided to the installApplication API for AppManagement MBean does not contain a file.
User Response:
Make sure that the file exists at the specified location. If this error is shown by wsadmin or UI then contact IBM support.
ADMA0044E: Error scheduling install for {0}
Explanation:
Unexpected exception occured during installation.
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.
ADMA0045E: AppName can not be null.
Explanation:
The application name passed to the checkIfAppExists or uninstallApplication API of AppManagement MBean is null.
User Response:
If these APIs are called programmatically then make sure that the name is not null else contact IBM support.
ADMA0046E: Props can not be null for local mode.
Explanation:
The properties table passed to uninstallApplication API of AppManagement MBean can not be null
User Response:
If this API is called programmatically then make sure that the properties table is not null.
ADMA0047E: Error scheduling uninstall for {0}
Explanation:
Unexpected exception in uninstalling the application.
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.
ADMA0048E: Unknown module - {0}
Explanation:
The module parameter passed to getModuleInfo API of AppManagement MBean is invalid.
User Response:
Make sure that the module parameter is a String which has a value of moduleURI+ddURI. If this error is thrown by wsadmin or UI then contact IBM support.
ADMA0049E: Exception in getting module for deployment descriptor {0}
Explanation:
This exception is thrown when the unique module URI passed in to AppManagement MBean for getApplicationInfo or getModuleInfo APIs does not match a module in the EAR. The unique URI is moduleURI+ddURI
User Response:
If getApplicationInfo or getModuleInfo API on AppManagement MBean is called programmatically then make sure that the parameter passed in is correct. If this error is shown using wsadmin or admin client UI then contact IBM support.
ADMA0053E: Error closing ear {0}
Explanation:
This exception is thrown during application installation processing if the EAR file gets locked due to an unexpected error and hence can not be closed. Application installation is stopped when this exception is thrown.
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.
ADMA0054E: Exception in checking appication existence - {0}
Explanation:
Unexpected exception occured in checking the existence of the application during application uninstallation. The uninstallation will not proceed. This may also happen if the application to be uninstalled does not exist in the configuration.
User Response:
Make sure that the application name supplied to the uninstall action is correct.
ADMA0055E: Error getting task {0}
Explanation:
This exception is thrown when a task that is scheduled to perform one of the application installation activities can not be instantiated. Installation is halted as a result of this exception.
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.
ADMA0056E: Incorrect task data format: missing JNDI data in module {0}
Explanation:
An error has occurred in preparing the application. Default data source for a JAR file is not specified.
User Response:
Specify the default data source for the JAR file specifed in the error message.
ADMA0057E: Incorrect task data format: missing user/passowrd data in module {0}
Explanation:
An error has occurred in preparing the application. Default data source for a JAR file has incomplete data.
User Response:
If the problem persists, contact IBM support.
ADMA0058E: Incorrect task data value for resource authorization in module {0}.
Correct value can be per connection factory or container.
Explanation:
An error has occurred in preparing the application. Resource authorization value for a JAR file is not specified correctly. Correct values are per connection factory or container.
User Response:
Enter the correct value for the resource authorization in the JAR file specified in the error message.
ADMA0059E: Incorrect task data format: missing resource authorization data in module {0}
Explanation:
An error has occurred in preparing the application. Default connection factory for a JAR file has incomplete data.
User Response:
If the problem persists, contact IBM support.
ADMA0061E: Error deleting SI entry - {0}
Explanation:
Unexpected exception in deleteing the entry for deployedApplication from serverindex.xml file of the node in which application was installed. The application may not be uninstalled successfully.
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.
ADMA0062E: Unable to locate EJB deploy options.
Explanation:
This exception is thrown when the properties table passed to installApplication API of AppManagement MBean specifies that EJBDeploy should be executed as a part of install but does not specify options for EJBDeploy.
User Response:
If installApplication API is called programmatically then make sure that the hashtable for EJBDeploy options is passed in as one of the entries in the properties table. If this exception is thrown by wsadmin or admin client UI then contact IBM support.
ADMA0063E: Error in EJB deploy - {0}
Explanation:
Previous message from application installation should detail the error that happens during EJBDeploy.
User Response:
Make sure that the EJB Jar assembled with the application is a valid deployable JAR.
ADMA0064E: Error extracting ear file.
Explanation:
Unexpected exception thrown during ear expansion.
User Response:
Make sure that there is enough disk space for ear to be extracted completely and proper file permissions are set to the temp directory and the directory specified as install destination. If problem persists then contact IBM support.
ADMA0065E: Error getting partial archive in writeTasks - {0}
Explanation:
Unexpected exception in saving the information passed in during editing of an existing application.
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.
ADMA0066E: Error creating config documents in the repository.
Explanation:
Unexpected error in saving the configuration documents of the application to the WebSphere repository during application install. This message should be preceded by more detailed messages regarding the failure.
User Response:
Refer to previous messages in the log for failure description. If none appear then contact IBM support.
ADMA0067E: Validation error in task {0}
RunAs role, {1}, for EJB {2} in module {3} has different user name and password as that in task {4}.
Explanation:
The application contains runAs system identity which can optionally change to a RunAs role. You have 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 with the existing data in the Mapping Roles to User task.
User Response:
Make sure the RunAs role you are trying to switch to has the same user/password data as specified in the Mapping Roles to User task.
ADMA0068E: Validation error in task {0}
Error getting task {1} to validate existing RunAs roles.
Explanation:
The application contains runAs system identity which can optionally change to a RunAs role. An error has occurred when trying to get the RunAs role task.
User Response:
If the problem persists, contact IBM support.
ADMA0069E: Validation error in task {0}
RunAs role, {1}, for EJB {2} in module {3} has different user name and password combination.
Explanation:
The application contains RunAs system identity which can optionally change to a RunAs role. You have 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 the same user mapping data (user and password) is entered for the same RunAs role name.
ADMA0070W: Unable to perform security policy filtering:
error getting repository context for cell in workspace.
Explanation:
An error has occurred while searching for filter policy in the configuration. As a result, security filtering is not performed.
User Response:
None if there is no security concerned. Otherwise, validate your configuration.
ADMA0071W: Unable to perform security policy filtering:
unexpected exception caught: {0}
Explanation:
An error has occurred while performing security policy filtering. As a result, security filtering is not performed.
User Response:
None if there is no security concerned. Otherwise, validate your configuration.
ADMA0072E: Your application contains policy with permissions that are in the filter policy:
{0}.
Remove these permissions from your policy file before attempting to install your application again.
Explanation:
An error has occurred while performing security policy filtering. Your application contains policy with permissions that are in the filter policy.
User Response:
Remove the specified permission in the error message from your policy file.
ADMA0073W: Custom permissions found in policy file:
{0}
Explanation:
The application contains policy file which includes custom permissions.
User Response:
none
ADMA0074E: Validation error in task {0}
JNDI name and/or resource authorization is not specified for module {1} with URI {2}. You have not specified the data source for each CMP bean belonging to this module. Specify the default data source for the entire module or provide the complete data source for each CMP belonging to this module.
Explanation:
The application contains EJB 2.x. Data source JNDI name and/or resource authorization in both module and CMP bean level is not specified. You have to 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 wish 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/or resource authorization in either the module or CMP bean level.
ADMA0077W: Error removing the workspace: {0}
Explanation:
Unexpected exception thrown when saving the changes made during application installation, uninstallation, or editing. The changes may not be saved correctly. This exception is thrown only when application management functions are invoked programmatically and typically should not be seen while using wsadmin (except when -local option is used) or admin client UI.
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.
ADMA0078W: Unable to delete file: {0}
Explanation:
Error deleting a file or a directory.
User Response:
Make sure that the disk is not write-protected. If not then manually delete the file or directory mentioned in the error message.
ADMA0079W: Unable to find task info for: {0}
Explanation:
Unexpected exception thrown in getting the AppDeploymentTaskInfo object for a given AppDeploymentTask. If you see this message while testing an application installation extension then make sure that all the classes related to the extension appear in the classpath.
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.
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 located in the ${user.install.root}/config/cells/(yourCellName)/applications/(yourAppName).ear/deployments/(yourAppName)/META-INF directory after the application is installed. For syntax of was.policy, please refer to the Dynamic Policy section of documentation in Info Center.
Explanation:
A template policy file is included in your 1.2.x application.
User Response:
None if there is no security concerned. Otherwise, modify the was.policy in the location specified in the warning message to set up security permission.
ADMA0081W: The 1.2.x enterprise application does not contain any Java 2 Security policy. Your application may not be able to run after it is installed.
Explanation:
There is no policy file included in your 1.2.x application.
User Response:
None if there is no security. Otherwise, include a was.policy in your application before reinstalling the application.
ADMA0082E: Your application contains the following incompatible jar/war:
{0}
Correct the file(s) before trying again.
Explanation:
Typically this error is shown when a J2EE1.2 application EAR file contains a J2EE1.3 module.
User Response:
Make sure that the EAR is a J2EE compliant EAR file.
ADMA0083E: The file or directory {0} specified as ear file is not a valid ear.
Explanation:
The application specified is not a valid ear.
User Response:
Make sure the correct application file is entered. Otherwise, validate your application using Application Assembly Tool.
ADMA0084E: The archive {0} to be wrapped is not a module of type JAR or WAR. Wrong file type.
Explanation:
The application file specified is not a valid jar or war.
User Response:
Make sure the correct application file is entered.
ADMA0085E: Validation error in task {0}
Application name, {1}, is invalid. Application name cannot begin with a leading dot and cannot contain any of the following characters: / : * ? " < > | ; ,
Explanation:
The specified application name contains invalid character. Application name cannot begin with a leading dot and cannot contain any of the following characters: / : * ? " < > | ; ,
User Response:
Specify an application name that does not contain any of the invalid characters.
ADMA0086E: Error from EJBDeploy: {0} [severity {1}]
Explanation:
This message is written into the log file when a EJBDeploy error is encountered.
User Response:
Examine the error message and previous messages from EJBDeploy to determine the source of the problem.
ADMA0087W: Warning from EJBDeploy: {0} [severity {1}]
Explanation:
This message is written into the log file when a EJBDeploy warning is encountered.
User Response:
Examine the warning message and previous messages from EJBDeploy to determine whether any corrective action is necessary.
ADMA0088E: Invalid usage of {0}. Operation {0} can only be called in local mode of AppManagement.
Explanation:
Some of the application management functions can only be called if AppManagement runs in local mode i.e without connecting to a JMX process.
User Response:
If this API is called programmatically then make sure that AppManagementProxy object is created using getLocalProxy method.
ADMA0089E: AppManagement MBean not found.
Explanation:
If this is a node agent or application server then AppManagement MBean is not activated by default. If that is not the case then contact IBM support.
User Response:
Contact IBM support if this is a base WebSphere installation or a deployment manager process.
ADMA0090E: Invalid usage of {0}. Operation {0} can only be called in JMX mode of AppManagement.
Explanation:
Some of the application management functions can only be called if AppManagement runs in JMX mode i.e it must be connected to a server.
User Response:
If this API is called programmatically then make sure that AppManagementProxy object is created either using getJMXProxyForClient or getJMXProxyForServer methods.
ADMA0091E: Resource {0} defined in URI {1} for module {2} is invalid. It has a cross reference {3} that can not be resolved.
Explanation:
This typically happens when the bindings or extensions of an application or module has cross references to deployment descriptor artifacts and those cross referenced IDs are not present in the deployment descriptor. This is most common when bindings or extensions are hand edited.
User Response:
Edit the resource URI mentioned in the exception and fix the cross references.
ADMA0092E: Unexpected exception occurred while preparing task {0}. Please check server machine's FFDC for more information.
Explanation:
Unexpected exception occurred while preparing the specified task.
User Response:
Please see server machine's FFDC for more information. Please check the ear file if binding information is correct.
ADMA0093E: Unexpected exception occurred while completing task {0}. Please check server machine's FFDC for more information.
Explanation:
Unexpected exception occurred while completing the specified task.
User Response:
Please see server machine's FFDC for more information. Please check the ear file if binding information is correct.
ADMA0094E: Application Management operation {0} is not available in your WebSphere installation.
Explanation:
User applications cannot be installed or updated without a full WebSphere license.
User Response:
Do not call the application management APIs that update applications in this installation environment.
ADMA0095W: Current backend id({0}) specified in ibm-ejb-jar-bnd.xmi for ejb jar file ({1}) does not exist.
Explanation:
Current backend id specified in ibm-ejb-jar-bnd.xmi does not exist under META-INF/backends directory.
User Response:
Please check if the current backend id (currentBackendId) specified in ibm-ejb-jar-bnd.xmi is correct. Look for a correct id under META-INF/backends directory of the specified jar.
ADMA0096I: The Application Management version key was found but is not valid.
Explanation:
A full WebSphere product installation is not available or has become corrupted.
User Response:
No action is needed if this is an embedded WebSphere installation.
ADMA0097I: Application Management is being initialized without a full product install. All application management functions will not be available.
Explanation:
A full WebSphere product installation is not available to perform all application managment functions.
User Response:
No action is needed if this is an embedded WebSphere installation.
ADMA0098E: Current Backend id {0} does not exist in BackendId list: {1} under META-INF/backends directory.
Explanation:
The Current Backend Id specified in ibm-ejb-jar-bnd.xmi does not exist under META-INF/backends directory.
User Response:
Specify the correct CurrentBackendId in ibm-ejb-jar-bnd.xmi.
ADMA4001I: usage syntax:
EARExpander
-ear
Explanation:
NONE
User Response:
NONE
ADMA4002E: EARExpander: Missing required argument: {0}
Explanation:
When calling EARExpander, one of the required arguments is missing. The required arguments are ear, operationDir, and operation.
User Response:
Rerun EARExpander with the missing argument and its value.
ADMA4003E: EARExpander: Invalid ear file specified: {0}
Explanation:
The ear file specified is invalid. If you are performing an expand operation, the file does not exist, does not have read permission, or is not in correct ear format. If you are performing a collapse operation, the file specified is an existing file.
User Response:
Rerun EARExpander with the correct ear file specified.
ADMA4004E: EARExpander: Invalid operation directory specified: {0}
Explanation:
The operation directory specified is invalid. If you are performing a collapse operation, the directory specified does not exist, is not a directory, or the files in it is not in correct ear format. If you are performing an expand operation, the directory specified is an existing file.
User Response:
Rerun EARExpander with the correct operation directory specified.
ADMA4005E: EARExpander: Invalid operation specified: {0}
Explanation:
Check the command line arguments to EARExpander.
User Response:
Type EARExpander without any parameters to see command line help.
ADMA4006I: Expanding {0} into {1}
Explanation:
Informational message when running EARExpander to expand an ear file
User Response:
none
ADMA4007I: Collapsing {0} into {1}
Explanation:
Informational message when running EARExpander to collapse a directory to an ear
User Response:
none
ADMA4008E: EARExpander: Missing value for required argument "{0}"
Explanation:
A value is not specified for the required argument for EARExpander
User Response:
Rerun EARExpander with a value specified for the required argument
ADMA4009W: Invalid expansion flag specified: {0}. Ignorning this incorrect value. Using default value "All".
Explanation:
The expansion flag value specified is invalid. The default value "All" is used instead.
User Response:
None if your intension is to expand the entire ear. Otherwise, rerun EARExpander specifying "war" as the expansion flag.
ADMA5001I: Application binaries saved in {0}
Explanation:
NONE
User Response:
NONE
ADMA5002E: Application binaries could not be saved in {0}: {1}
Explanation:
As a part of application installation application ear file is saved in the WebSphere configuration repository. This error message is shown during installation if ear file can not be saved.
User Response:
Make sure there is enough disk space to save the ear file and check file permissions. If problem persists then contact IBM support.
ADMA5003I: Jsps in wars {0} compiled successfully
Explanation:
NONE
User Response:
NONE
ADMA5004E: Jsps in war {0} could not be compiled, check logs for more errors.: {1}
Explanation:
JSPs in the WAR modules of the ear have compilation errors.
User Response:
Use AAT to compile jsps and check compilation errors.
ADMA5005I: Application {0} configured in WebSphere repository
Explanation:
NONE
User Response:
NONE
ADMA5006E: Error in configuring {0} in WebSphere repository: {1}
Explanation:
Messages before this should detail cause of the failure. Typically the error conditions include wrong server, node name specified as module targets during installation.
User Response:
Read the error messages and rectify the problem.
ADMA5007I: EJBDeploy completed on {0}
Explanation:
NONE
User Response:
NONE
ADMA5008E: EJBDeploy failed on {0}: {1}
Explanation:
This message indicates that EJBDeploy has failed during application installation. Messages before this one should detail the cause of failure.
User Response:
Use AAT to run EJBDeploy on the EAR file before installing it and remove the causes of EJBDeploy failures.
ADMA5009I: Application archive extracted at {0}
Explanation:
NONE
User Response:
NONE
ADMA5010E: Error extracting application at {0}: {1}
Explanation:
The disk may be full or may be write protected.
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.
ADMA5011I: Cleanup of temp dir for app {0} done.
Explanation:
NONE
User Response:
NONE
ADMA5012I: Installed cleanup failed for {0}: {1}
Explanation:
NONE
User Response:
NONE
ADMA5013I: Application {0} installed successfully.
Explanation:
NONE
User Response:
NONE
ADMA5014E: Installation of application {0} failed.
Explanation:
Messages before this one should detail the cause of failure.
User Response:
Read the message before this and rectify the problem.
ADMA5015E: App {0} can not be installed since it already exists in WebSphere configuration.
Explanation:
The application name must be unique in the WebSphere configuration.
User Response:
Install the application under different name.
ADMA5016I: Installation of {0} started.
Explanation:
NONE
User Response:
NONE
ADMA5017I: Uninstallation of {0} started.
Explanation:
NONE
User Response:
NONE
ADMA5018I: Starting EJBDeploy on ear {0}..
Explanation:
NONE
User Response:
NONE
ADMA5019E: Invalid application name {0}. Application name cannot begin with a leading dot and cannot contain any of the following characters: / : * ? " < > | ; ,
Explanation:
The specified application name contains invalid character. Application name cannot begin with a leading dot and cannot contain any of the following characters: / : * ? " < > | ; ,
User Response:
Specify an application name that does not contain any of the invalid characters.
ADMA5020E: The target server {0} on node {1} specified for module {2} does not exist.
Explanation:
An invalid target is specified for a module during application installation.
User Response:
Check if the server specified as the target exists.
ADMA5022E: The target cluster {0} specified for module {1} does not exist.
Explanation:
An invalid target is specified for a module during appliction installation.
User Response:
Check if the cluster specified as the target exists.
ADMA5023E: Ambiguous specification for object {0}. There are multiple objects with this name, at least one each under parents {1} and {2}. Please specify parent {3}.
Explanation:
Typically this happens 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 it is treated as an ambiguous definition.
User Response:
Specify the parent name (e.g. 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 is an invalid configuration.
Explanation:
An application module can not 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: ObjectName format is incorrect for {0}.
Explanation:
The javax.management.ObjectName instance has domain:key=value format. The domain name for application management function in WebSphere 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 specified for a module in 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 typos.
ADMA5027E: Cluster {0} not found in the repository.
Explanation:
Cluster with the given name does not exist.
User Response:
Correct the cluster name. Check for typos.
ADMA5028E: Server {0} on Node {1} not found in the repository.
Explanation:
The server with a given name does not exist under the given node.
User Response:
Correct server name. Look for typos.
ADMA5029E: Cluster member {0} defined in cluster configuration for {1} can not be found as a server.
Explanation:
The cluster.xml for the cluster lists a cluster member and the member does not exist. The cluster configuration may be invalid.
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.
ADMA5030E: No deployment object found in the deployment document for {0}
Explanation:
The deployment.xml for the given deployment is empty or invalid.
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.
ADMA5031E: Could not load {0} document for object at {1}.
Explanation:
The document is corrupt or empty.
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.
ADMA5032W: The target {0} is specified more than once in {1}. Ignoring {2}
Explanation:
Same target specified multiple times for the same module are 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 the cluster {1} is not specified in the list of targets.
Explanation:
A module can not 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 copy.sessiommgr.servername options for install does not exist in the configuration.
Explanation:
Invalid server name.
User Response:
Make sure that the server with a given name exists.
ADMA5035E: The copy operation on session manager of {0} failed as the copy is {1}.
Explanation:
The copy made of SessionManager settings is not of type SessionManager.
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.
ADMA5036E: Exception {0} thrown while copying session manager settings from server {1}
Explanation:
Previous message should detail the cause of the problem.
User Response:
Read previous message to understand the probable cause.
ADMA5037I: Starting backup of app at {0}
Explanation:
NONE
User Response:
NONE
ADMA5038I: Completed backup of app at {0}
Explanation:
NONE
User Response:
NONE
ADMA5039E: The node name can not be null.
Explanation:
The node name passed in as a parameter to removeAllAppsFromNode can not be null.
User Response:
If removeAllAppsFromNode API on AppManagement MBean is called programmatically then make sure that the node name passed in is not null. If addNode utility throws this exception then contact IBM support.
ADMA5040E: The node name {0} does not exist in the configuration.
Explanation:
Invalid node name.
User Response:
Specify the correct node name.
ADMA5041E: The application {0} listed in the server index entry for node {1} can not be found.
Explanation:
The serverindex.xml file for the given node is incorrect.
User Response:
Note the steps to recreate the problem and contact IBM support.
ADMA5042E: Targets {0} are not found in the repository. So server index entries for these targets will not be updated.
Explanation:
The application has module deployed on the servers or clusters that do not seem to exist. The application is uninstalled but if the targets do really exist then the serverindex.xml file for the nodes of these targets are not updated.
User Response:
If the targets specified in the message do exist in the WebSphere configuration then contact IBM support.
ADMA5043I: Module {0} bound to server {1}
Explanation:
NONE
User Response:
NONE
ADMA5044I: Application {0} bound to node {1}
Explanation:
NONE
User Response:
NONE
ADMA5045E: The application name {0} can not be found under any cell in the repository.
Explanation:
Application does not exist.
User Response:
Check application name. Look for typos.
ADMA5046E: No cell name specified anywhere in the parameters passed to install API. The cell name is looked for in the Module to Server relation and then in the AppConstants.APPDEPL_CELLNAME.
Explanation:
If the application does not have any module and the cell name is not passed as a parameter to the installApplication API of AppManagement MBean.
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.
ADMA5047E: The cell name {0} does not exist in the configuration.
Explanation:
Invalid cell name
User Response:
Check cell name. Look for typos.
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 then make sure that cell name is passed in via properties table (key= AppConstants.APPDEPL_CELLNAME).
ADMA5049E: The binary data for ear of application {0} could not 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 WebSphere configuration. This error message is shown when the ear file can not be located under WAS_HOME/config/cells/cellName/applications/appName.ear/ directory.
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.
ADMA5050E: Invalid number format for reload interval. The specified value {0} is not a valid long.
Explanation:
The value for reload interval must be a long value.
User Response:
Make sure that the reload interval specified is a numeric long value.
ADMA5051W: Invalid value {0} for class loader policy. Default MULTIPLE will be used.
Explanation:
The value for class loader policy must be specified using constants defined in AppConstants class.
User Response:
Make sure that the class loader policy has one of the predefined values.
ADMA5052W: Invalid value {0} for class loading mode. Default PARENT_FIRST will be used.
Explanation:
The value for class loading mode must be specified using constants defined in AppConstants class.
User Response:
Make sure that the class loading mode has one of the predefined values.
ADMA5102I: Deletion of config data for {0} from config repository completed successfully.
Explanation:
NONE
User Response:
NONE
ADMA5103E: Deletion of config data for {0} from config repository failed.
Explanation:
The uninstall procedure failed to delete the application configuration data successfully. The application will be still uninstalled.
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.
ADMA5104I: Server index entry for {0} was updated successfully.
Explanation:
NONE
User Response:
NONE
ADMA5105E: Updates to server index entry failed for the last node in {0}
Explanation:
The application is listed in serverindex.xml for each node that every module is deployed on. This message indicates that an unexpected error happened while deleting the application entry from serverindex.xml during application uninstallation.
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.
ADMA5106I: Application {0} uninstalled successfully.
Explanation:
NONE
User Response:
NONE
ADMA5107E: Application {0} could not be uninstalled.
Explanation:
Unexpected exception occured during installation.
User Response:
Read previous error messages for further details.
ADMA5108E: App {0} can not be uninstalled since it does not exist in WebSphere configuration.
Explanation:
An application name does not exist.
User Response:
Make sure that the application name is correct.
ADMA6001I: Begin App Preparation -
Explanation:
NONE
User Response:
NONE
ADMA6002I: The options used are:
Explanation:
NONE
User Response:
NONE
ADMA6003I: Reading local ear file ... please wait ..
Explanation:
NONE
User Response:
NONE
ADMA6004I: Preferences for default bindings:
Explanation:
NONE
User Response:
NONE
ADMA6005I: Checking filter.policy on server ..
Explanation:
NONE
User Response:
NONE
ADMA6006I: ...... Saving the local EAR file ...
Explanation:
NONE
User Response:
NONE
ADMA6007I: Proceeding with local install..
Explanation:
NONE
User Response:
NONE
ADMA6008I: Install Event received:
Explanation:
NONE
User Response:
NONE
ADMA6009I: Processing complete.
Explanation:
NONE
User Response:
NONE
ADMA6010I: The tasks are {0}
Explanation:
NONE
User Response:
NONE
ADMA6011I: Deleting directory tree {0}
Explanation:
NONE
User Response:
NONE
ADMA6012I: Exception in run {0}
Explanation:
NONE
User Response:
NONE
ADMA6013I: Extract application binaries at {0}
Explanation:
NONE
User Response:
NONE
ADMA6014I: The cell name is {0}
Explanation:
NONE
User Response:
NONE
ADMA6015I: Module {0} is to be installed on {1}
Explanation:
NONE
User Response:
NONE
ADMA6016I: Add to workspace {0}
Explanation:
NONE
User Response:
NONE
ADMA6017I: Saved document {0}
Explanation:
NONE
User Response:
NONE
ADMA6018I: Node-server relation for this app is {0}
Explanation:
NONE
User Response:
NONE
ADMA6019I: Node-serverIndex document relation for this app {0}
Explanation:
NONE
User Response:
NONE
ADMA6020I: Adding serverindex entry for {0} for server {1} on node {2}
Explanation:
NONE
User Response:
NONE
ADMA6021I: Removing serverindex entry for {0} for server {1} on node {2} and return code is {3}
Explanation:
NONE
User Response:
NONE
ADMA6051I: Begin App uninstall -
Explanation:
NONE
User Response:
NONE
ADMA6052I: Proceeding with local uninstall ..
Explanation:
NONE
User Response:
NONE
ADMA6053I: Uninstall Event received:
Explanation:
NONE
User Response:
NONE
ADMA7000W: Unexpected exception in onChangeStart processing: {0}
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.
ADMA7001W: Unexpected exception in checking if {0} is an application ear file: {1}. 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.
ADMA7002E: Unexpected exception {0} in building cache for app sync from serverindex.xml. The app sync logic will not work for deletions or modifictions of binaries in this case.
Explanation:
The exception message may detail probable cause.
User Response:
If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear.
ADMA7003E: Malformed server indexn entry {0}. The entry should be of the form appName.ear/deployments/appName. The application binary corresponding to this entry may not be deleted/updated upon completion of the task.
Explanation:
The entry for deployedApplication in serverindex.xml is bad.
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.
ADMA7004E: Unexpected exception while building cache entry for {0} and {1}. Exception is: {2}. All the related binaries may not be deleted/updated.
Explanation:
The exception message may detail probable cause.
User Response:
If an application ear file is not expanded to the destination specified during installation then use EARExpander tool to expand the ear.
ADMA7005E: Unexpected exception loading resource {0} from the repository. This will cause further problems in using this resource for app sync logic.
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.
ADMA7006E: Unexpected exception in onChangeCompletion processing: {0}
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.
ADMA7007E: Unexpected exception in postProcess processing id={1}: {0}
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.
ADMA7008E: Unexpected exception in expandEar. The ear file {0} will not be extracted in following paths {1}. Exception: {2}
Explanation:
The disk may be full or the directory may not have write permission.
User Response:
Use EARExpander tool to extract the ear file.
ADMA7009E: Exception {0} in deleting dir {1}
Explanation:
The exception message may detail probable cause.
User Response:
Delete the directory manually.