Troubleshooting an installation using the log files
This procedure describes how to troubleshoot an installation using log files.
Error and warning messages have [ messageType ] prefixes, for example, [ ERROR ] or [ WARNING ] that indicate the category of the message. Included with the prefix is a timestamp or called routine, if applicable. Installation step outlines have no prefixes.
To troubleshoot an installation
- Review the app_name.html summary log file for failures. Search for "Failed."
- If you find any errors, review the app_name_error.log file for details about the errors.
- If you find an indication of cascading failures, review the app_name.log file to obtain more complete information about the source of the errors.
- If you find any errors, review the arerror.log file and the database error logs to determine the source of installation errors.
- Send the .zip output file from the temp directory to Customer Support on request.
The path to the zipped log appears below the Zip Logs button.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*