deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Replace HTML lists with Markdown

Browse Source
This commit is contained in:
Gary Moore 2021-12-02 18:35:31 -08:00
parent f61940c8aa
commit 998a8209bb
1 changed files with 39 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

73
windows/deployment/upgrade/log-files.md
View File

@ -49,15 +49,15 @@ The following table describes some log files and how to use them for troubleshoo
A setupact.log or setuperr.log entry (files are located at C:\Windows) includes the following elements: A setupact.log or setuperr.log entry (files are located at C:\Windows) includes the following elements:
<ol> 1. **The date and time** - 2016-09-08 09:20:05.
<LI><B>The date and time</B> - 2016-09-08 09:20:05.
<LI><B>The log level</B> - Info, Warning, Error, Fatal Error. 2. **The log level** - Info, Warning, Error, Fatal Error.
<LI><B>The logging component</B> - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
<UL> 3. **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
<LI>The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors.
</UL> The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors.
<LI><B>The message</B> - Operation completed successfully.
</OL> 4. **The message** - Operation completed successfully.
See the following example: See the following example:
@ -70,32 +70,37 @@ See the following example:
The following instructions are meant for IT professionals. Also see the [Upgrade error codes](upgrade-error-codes.md) section in this guide to familiarize yourself with [result codes](upgrade-error-codes.md#result-codes) and [extend codes](upgrade-error-codes.md#extend-codes). The following instructions are meant for IT professionals. Also see the [Upgrade error codes](upgrade-error-codes.md) section in this guide to familiarize yourself with [result codes](upgrade-error-codes.md#result-codes) and [extend codes](upgrade-error-codes.md#extend-codes).
<br>To analyze Windows Setup log files: To analyze Windows Setup log files:
<ol> 1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process.
<LI>Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process.
<LI>Based on the <a href="upgrade-error-codes.md#extend-codes" data-raw-source="[extend code](upgrade-error-codes.md#extend-codes)">extend code</a> portion of the error code, determine the type and location of a <a href="#log-files" data-raw-source="[log files](#log-files)">log files</a> to investigate. 2. Based on the [extend code](upgrade-error-codes.md#extend-codes) portion of the error code, determine the type and location of a [log files](#log-files) to investigate.
<LI>Open the log file in a text editor, such as notepad.
<LI>Using the <a href="upgrade-error-codes.md#result-codes" data-raw-source="[result code](upgrade-error-codes.md#result-codes)">result code</a> portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the &quot;abort&quot; and abandoning&quot; text strings described in step 7 below. 3. Open the log file in a text editor, such as notepad.
<LI>To find the last occurrence of the result code:
<OL type="a"> 4. Using the [result code](upgrade-error-codes.md#result-codes) portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below.
<LI>Scroll to the bottom of the file and click after the last character.
<LI>Click <B>Edit</B>. 5. To find the last occurrence of the result code:
<LI>Click <B>Find</B>.
<LI>Type the result code. 1. Scroll to the bottom of the file and click after the last character.
<LI>Under <B>Direction</B> select <b>Up</b>. 2. Click **Edit**.
<LI>Click <b>Find Next</b>. 3. Click **Find**.
</OL> 4. Type the result code.
<LI> When you have located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed just prior to generating the result code. 5. Under **Direction** select **Up**.
<LI> Search for the following important text strings: 6. Click **Find Next**.
<UL>
<LI><B>Shell application requested abort</B> 6. When you have located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed just prior to generating the result code.
<LI><B>Abandoning apply due to error for object</B>
</UL> 7. Search for the following important text strings:
<LI> Decode Win32 errors that appear in this section.
<LI> Write down the timestamp for the observed errors in this section. * **Shell application requested abort**
<LI> Search other log files for additional information matching these timestamps or errors. * **Abandoning apply due to error for object**
</OL>
8. Decode Win32 errors that appear in this section.
9. Write down the timestamp for the observed errors in this section.
10. Search other log files for additional information matching these timestamps or errors.
For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file: For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file: