| Explanation | This is an unexpected exception. The cause cannot be immediately determined. |
| Action | For more information about resolving this error, consult the IBM WebSphere Application Server Support: https://ibm.biz/BdztgV. The website provides searchable databases of technotes, solutions, and e-fixes. |
| Explanation | The Liberty migration scan requires a binary scanner JAR file to create the migration report. This file is not accessible because the environment might be corrupted or the correct file permissions do not exist. |
| Action | Verify that the JAR file exists, and check the file system permissions for this file. For more information about resolving this error, see the IBM WebSphere Application Server Support website: https://ibm.biz/BdztgV. The website provides searchable databases of technotes, solutions, and e-fixes. |
| Explanation | The Liberty migration report for the application was not deleted because the report may be deleted already, the application name may be misspelled, or the environment might be corrupted. |
| Action | Verify that the application name is correct and that the report exists. |
| Explanation | The application binary files for the specified application name were not accessible at the expected location. The files either do not exist or do not allow read access. |
| Action | Check the spelling of the application name and the read permissions of the specified application file. |
| Explanation | The Liberty migration report was not written to the output directory because the correct file permissions do not exist. |
| Action | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
| Explanation | The Liberty migration report is still in progress. |
| Action | Wait for the Liberty migration report to complete. |
| Explanation | The Liberty migration report was submitted. The report is available when the scan completes. |
| Action | No action is required. |
| Explanation | The command cannot be successfully run. |
| Action | See the trace output for more details about the origin of the problem. |
| Explanation | User does not have the correct authority to run the command. |
| Action | Make sure that the user has the correct authority or security role to perform the command. |
| Explanation | The value of the maxHeap parameter must not be larger than the maximum size of an integer. |
| Action | Specify a value for the maxHeap parameter that is less than the maximum size of an integer. Values for maxHeap can be in bytes, KB, MB, or GB. |
| Explanation | Applications installed using the zeroEarCopy parameter do not store their archive in the default <USER_INSTALL_ROOT>/config/cell/<CELL_NAME>/application/<APP_NAME> location and therefore cannot be automatically scanned. |
| Action | Run the binary scanner installed in the <WAS_INSTALL_ROOT>\bin\migration\wamt directory against the application archive and specify the --configLocation=<USER_INSTALL_ROOT> parameter. |
| Explanation | The Transformation Advisor data collection requires a binary scanner JAR file to create the data collection. This file is not accessible because the environment might be corrupted or the correct file permissions do not exist. |
| Action | Verify that the JAR file exists and check the file system permissions for this file. |
| Explanation | The Transformation Advisor data collection is still in progress. |
| Action | Wait for the Transformation Advisor data collection to complete before you attempt to delete it. |
| Explanation | The specified file or files are not accessible at the expected location. The files either do not exist or do not allow read access. |
| Action | Check the spelling of each profile name and the read permissions of the specified profile files. |
| Explanation | The Transformation Advisor data collection cannot be written to the output directory because the correct file permissions do not exist. |
| Action | Check that storage space exists and that the product has the necessary permissions to create the directory. |
| Explanation | The Transformation Advisor data collection was submitted. The data collection is available when the scan completes. |
| Action | No action is required. |
| Explanation | The target profile is not accessible at the expected location. The files either do not exist or do not allow read access. |
| Action | Check the profile registry and the read permissions for the target profile. |
| Explanation | A Transformation Advisor data collection is already running. The Transformation Advisor data collection cannot be submitted again. |
| Action | Wait until the current collection is complete before you start a new Transformation Advisor data collection. |