Merge pull request #7955 from paulcociuba/patch-2

AB#3250: Docs 2024 review: Update troubleshoot-arr-using-frt-rules.md

Author: sevend2

support/developer/webapps/iis/health-diagnostic-performance/media/troubleshoot-arr-using-frt-rules/add-frt-rule-select-status-code.png

@@ -1,17 +1,17 @@
 ---
 title: Using Failed Request Tracing rules to troubleshoot Application Request Routing
 description: Describes the steps to enable Failed Request Tracing rules to debug failures and trace steps in Application Request Routing.
-ms.date: 07/02/2008
+ms.date: 01/03/2025
 ms.author: haiyingyu
 author: HaiyingYu
 ms.reviewer: johnhart, riande
 ms.custom: sap:Health, Diagnostic, and Performance Features\Failed Request Tracing
 ---
 # Using Failed Request Tracing rules to troubleshoot Application Request Routing
 
-_Applies to:_   Internet Information Services 7.0 and later versions
+_Applies to:_   Internet Information Services on Windows Server 2016 and later operating system versions
 
-Failed Request Tracing is a powerful tool for troubleshooting request-processing failures in IIS 7.0 and later versions. This article provides steps to enable Failed Request Tracing rules to debug failures and trace steps in Application Request Routing. For more information about Failed Request Tracing rules, see [Troubleshoot failed requests using tracing in IIS 8.5](troubleshoot-failed-requests-using-tracing-in-iis-85.md).
+Failed Request Tracing is a powerful tool for troubleshooting request-processing failures in the Internet Information Services (IIS) web server that ships with Windows Server 2016 or later versions. This article provides steps to enable Failed Request Tracing rules to debug failures and trace steps in Application Request Routing. For more information about Failed Request Tracing rules, see [Troubleshoot failed requests using tracing in IIS](troubleshoot-failed-requests-using-tracing-in-iis-85.md).
 
 ## Goal
 
@@ -21,7 +21,7 @@ To configure Failed Request Tracing rules and to understand what to look for whe
 
 This walkthrough requires the following prerequisites:
 
-- IIS 7.0 or above on Windows 2008 (any SKU) or newer with Tracing role service installed for IIS.
+- IIS on Windows Sever 2016 (any SKU) or newer with Tracing role service installed for IIS.
 - Microsoft Application Request Routing and dependent modules.
 - Minimum of two application servers with working sites and applications.
 
@@ -36,24 +36,38 @@ Configure the Failed Request Tracing rules for Application Request Routing using
 ### How to configure Failed Request Tracing rules using the UI
 
 1. Launch Internet Information Services (IIS) Manager (inetmgr).
-1. Select **Default Web Site**.  
+1. Select **Default Web Site**.
+
     :::image type="content" source="media/troubleshoot-arr-using-frt-rules/site-list-expanded.png" alt-text="Screenshot showing the Sites list expanded. Default Web Site is highlighted.":::
-1. In the **Actions** pane, under **Configure**, select **Failed Request Tracing…**.  
+
+1. In the **Actions** pane, under **Configure**, select **Failed Request Tracing…**.
+
     :::image type="content" source="media/troubleshoot-arr-using-frt-rules/failed-request-tracing-in-action-pane.png" alt-text="Screenshot focused on Failed Request Tracing in the Actions pane.":::
-1. In the **Edit Web Site Failed Request Tracing Settings** dialog box, select the **Enable** checkbox.  
+
+1. In the **Edit Web Site Failed Request Tracing Settings** dialog box, select the **Enable** checkbox.
+
     :::image type="content" source="media/troubleshoot-arr-using-frt-rules/edit-web-site-frt-settings-dialog.png" alt-text="Screenshot of the Edit Web Site Failed Request Tracing Settings dialog.":::
+
 1. Select **OK** to save changes.  
 1. Select **Default Web Site**.
 1. Double-click **Failed Request Tracing Rules**.
-1. In the **Actions** pane, select **Add…**.  
-    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/add-frt-rule-window.png" alt-text="Screenshot of the Add Failed Request Tracing Rule window. All content is selected.":::  
+1. In the **Actions** pane, select **Add…**.
+
+    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/add-frt-rule-window.png" alt-text="Screenshot of the Add Failed Request Tracing Rule window. All content is selected.":::
+
     Select **All content (\*)**, and then select **Next**.
-1. Select **Status code(s):** and enter _200-399_.  
-    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/add-frt-rule-select-status-code.png" alt-text="Screenshot of the Add Failed Request Tracing Rule. Status code is checked.":::  
+1. Select **Status code(s):** and enter _200-399_.
+
+    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/add-frt-rule-select-status-code.png" alt-text="Screenshot of the Add Failed Request Tracing Rule. Status code is checked.":::
+
     Select **Next**. The above configuration has created a Failed Request Tracing rule that writes traces when the status code falls between 200 and 399.
-1. Deselect **ASP**,**ASPNET**, and **ISAPI Extension**. After selecting **WWW Server**, deselect everything under **Areas:**, except for **Rewrite** and **RequestRouting**. Because Application Request Routing relies on the URL Rewrite Module to inspect incoming requests, it's recommended that you enable the traces for both Application Request Routing (**RequestRouting**) and URL Rewrite Module (**Rewrite**).  
-    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/edit-frt-rule-window.png" alt-text="Screenshot of the Edit Failed Request Tracing Rule window. W W W server is selected in the Providers section.":::  
-    For additional information about URL Rewrite Module traces, see [Using Failed Request Tracing to Trace Rewrite Rules](/iis/extensions/url-rewrite-module/using-failed-request-tracing-to-trace-rewrite-rules) .
+
+1. Deselect **ASP**,**ASPNET**, and **ISAPI Extension**. After selecting **WWW Server**, deselect everything under **Areas:**, except for **Rewrite** and **RequestRouting**. Because Application Request Routing relies on the URL Rewrite Module to inspect incoming requests, it's recommended that you enable the traces for both Application Request Routing (**RequestRouting**) and URL Rewrite Module (**Rewrite**).
+
+    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/edit-frt-rule-window.png" alt-text="Screenshot of the Edit Failed Request Tracing Rule window. W W W server is selected in the Providers section.":::
+
+    For additional information about URL Rewrite Module traces, see [Using Failed Request Tracing to Trace Rewrite Rules](/iis/extensions/url-rewrite-module/using-failed-request-tracing-to-trace-rewrite-rules).
+
 1. Select **Finish**.
 
 ### How to configure Failed Request Tracing rules using the command-line
@@ -96,8 +110,10 @@ In this step, you'll send requests to Application Request Routing and analyze Fa
 
 1. Send a request to Application Request Routing. If Application Request Routing is functioning correctly, it results in a 200 response, which falls within the 200 to 399 range that is specified in [Step 1](#step-1-configure-failed-request-tracing-rules). Therefore, the logs are written to the location above.  
 1. List the files in the directory to confirm that new XML files are written.
-1. Open the XML file. Select **Request Details**. Select **Complete Request Trace**, and then Select **Expand All**. The following image is an example of a Failed Request Tracing log for Application Request Routing:  
-    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/request-diagnostics-for-sample.png" alt-text="Screenshot of a browser window showing the Request Diagnostics for the example website in a tab.":::
+1. Open the XML file. Select **Request Details**. Select **Complete Request Trace**, and then Select **Expand All**. The following image is an example of a Failed Request Tracing log for Application Request Routing:
+
+    :::image type="content" source="media/troubleshoot-arr-using-frt-rules/request-diagnostics-for-sample.png" alt-text="Screenshot of a browser window showing the Request Diagnostics for the example website in a tab." lightbox="media/troubleshoot-arr-using-frt-rules/request-diagnostics-for-sample.png":::
+
 1. Pay closer attention to the following sections:
 
     - **GENERAL\_REQUEST\_HEADERS:**