Explanation | Before the application is started, the application file is copied to a new location. The file copy operation did not succeed, so the application was not started. |
Action | Examine the source and destination file locations to see if the problem can be resolved. |
Explanation | The server could not start the application, because the ear file could not be extracted. |
Action | Read the exception message for information. Additional details might be available in the exception log. |
Explanation | The server could not start the application, because the ear file could not be extracted. |
Action | Examine the ear file to ensure it is a valid archive. |
Explanation | Before the application is started, a directory is created. The directory create operation did not succeed, so the application was not started. |
Action | Examine the directory location to see if the problem can be resolved. |
Explanation | The server could not start the application. This might be an internal error. |
Action | Examine the message and exception logs for related errors. |
Explanation | An earlier error prevented the application from being installed. |
Action | Check the location in the application configuration. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error occurred when accessing the contents of the library. That library will not available for use. |
Action | Review the contents of the application to ensure that an archive is present for the library. |
Explanation | An error occurred while listing application libraries. The list of application libraries will be incomplete. |
Action | See the exception information for additional details. |
Explanation | An error occurred while parsing the application descriptor. No modules will be available for the application. |
Action | See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data. |
Explanation | An internal error occurred when accessing the contents of the module. The module will not be made available for use. |
Action | See the exception information for additional details. |
Explanation | An internal error occurred when accessing the contents of a module. The application may be missing an archive for the module. The module will not be made available for use. |
Action | Review the contents of the application to ensure that an archive is present for the module. |
Explanation | An internal error occurred while finishing creation of a module. The module will not be made available for use. |
Action | See the exception information for additional details. |
Explanation | No archive is available for a module listed in the application descriptor. The module will not be made available for use. |
Action | See the exception information for additional details. Review the contents of the application to ensure that an archive is present for the module. |
Explanation | An error occurred while parsing the module deployment descriptor. The module will not be made available for use. |
Action | See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data. |
Explanation | An internal error occurred while attempting to scan a JAR file for EJB annotations. The JAR will not be available as an EJB JAR. |
Action | See the exception information for additional details. |
Explanation | An internal error occurred while attempting to scan a JAR file for EJB annotations. The JAR will not be available as an EJB JAR. |
Action | See the exception information for additional details. |
Explanation | Multiple modules point to the same archive. Only one module will be made available for use. |
Action | Review the contents of the application descriptor to ensure that each module points to a unique archive. |
Explanation | While trying to determine if the module is an EJB or an application client module, an error occurred trying to read the META-INF/MANIFEST.MF file. This module will not be treated as an application client module. |
Action | See the exception information for additional details. Review the contents of the application to ensure that the META-INF/MANIFEST.MF path is a file and not a directory, and ensure that the MANIFEST.MF file is valid. |