Merge pull request #7976 from MicrosoftDocs/main

Auto push to live 2025-01-03 02:00:02

Author: Deland-Han

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:**  

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

@@ -3,7 +3,7 @@ title: Invalid credentials error running desktop flows
 description: Provides a resolution for the invalid credentials error that might occur when you run a desktop flow in Power Automate.
 ms.reviewer: guco, johndund
 ms.custom: sap:Desktop flows\Cannot create desktop flow connection
-ms.date: 09/12/2024
+ms.date: 01/03/2025
 ---
 # Invalid credentials error when running desktop flows in Power Automate for desktop
 
@@ -50,6 +50,7 @@ To see an error message with specific details on what went wrong, ensure you hav
 |-1073741477|A user has requested a type of logon (for example, interactive or network) that has not been granted. An administrator has control over who can logon interactively and through the network.|The user account doesn't have logon rights on the machine, or the administrator changed the policies of the machine (check the [User Rights Assignment](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/user-rights-assignment) settings).|To solve this issue, see ["Logon type has not been granted" error when running a desktop flow or creating a connection](logon-type-has-not-been-granted.md).|
 |-1073445812|The user's UPN isn't in the expected format|The user signed in using `DOMAIN\user` but should use the `[email protected]` format instead (or vice versa).|Try to sign in using both the `[email protected]` and `DOMAIN\user` formats.|
 |-1073741062|Smart card logon is required and was not used| |Connections to machines that require smart card logons aren't supported. Use a machine without this requirement.|
+|-1073741715|Bad username or authentication information| The "executing account name" or the format of your username is incorrect. |Run the [dsregcmd /status](/entra/identity/devices/troubleshoot-device-dsregcmd) command in the context of the desktop flow connection account. Check the `Executing Account Name` section in the output and make sure it matches the username that was used. [Microsoft Entra joined](/entra/identity/devices/concept-directory-join) or hybrid devices always prefer the UPN  `[email protected]` format. If your machine is Microsoft Entra joined, use the `[email protected]` format for your username. You should only use the `DOMAIN\user` format if your device is domain-only joined.|
 
 If you don't have a more specific error associated with the problem, the easiest way to troubleshoot is to sign in to the machine with the exact credentials you entered in your connection. You can try this method by signing in to the machine locally or through a Remote Desktop connection. You should receive the same error message that Power Automate receives when trying to authenticate your credentials, which should help you troubleshoot the issue.
 

support/developer/webapps/iis/health-diagnostic-performance/media/troubleshoot-arr-using-frt-rules/edit-frt-rule-window.png

@@ -2,7 +2,7 @@
 title: Troubleshoot database consistency errors reported
 description: This article introduces how to troubleshoot errors reported by the DBCC CHECKDB command.
 ms.reviewer: jopilov, v-jayaramanp
-ms.date: 08/13/2024
+ms.date: 01/03/2025
 ms.custom: sap:File, Filegroup, Database Operations or Corruption
 ---
 
@@ -38,7 +38,7 @@ The cause of these problems can range from file system corruption, underlying ha
 
 ## Resolution
 
-1. Resolve any underlying hardware-related problems on the system before you proceed with restoring a backup or otherwise repairing the database. Apply any device driver, firmware, BIOS, and operating system updates that are relevant to the I/O path. Work with the administrator of the full I/O path (local machine, device drivers, storage NICs, SAN, backend storage, and cache) to isolate and resolve any problems. Examples include updating device drivers and checking configuration of the entire I/O path. For more information about checking the root cause, see [Investigate root cause](#investigate-root-cause-for-database-consistency-errors).
+1. Resolve any underlying hardware-related problems on the system before you proceed with restoring a backup or otherwise repairing the database. Apply any device driver, firmware, BIOS, and operating system updates that are relevant to the I/O path. Work with the administrator of the full I/O path (local machine, device drivers, storage NICs, SAN, backend storage, and cache) and memory (RAM) to isolate and resolve any problems. Examples include updating device drivers and checking the configuration of the entire I/O path. For details on how to investigate the root cause, see [Investigate root cause](#investigate-root-cause-for-database-consistency-errors).
 1. If `DBCC CHECKDB` reports permanent consistency errors, the best solution would be to restore data from a known good backup. For more information, see [Restore and Recovery](/sql/relational-databases/backup-restore/restore-and-recovery-overview-sql-server).
 1. Apply the latest SQL Server Cumulative Update or Service Pack to make sure you aren't running into any known issues. Check the [Cumulative Update or Service Pack documentation](../../releases/download-and-install-latest-updates.md) for any known issues fixed related to database corruption (consistency errors) and apply any relevant fixes. One central location where you can search for all fixes for a particular version if the [Detailed fix lists for SQL Server 2022, 2019, 2017](https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fdownload.microsoft.com%2Fdownload%2Fd%2F3%2Fe%2Fd3e28f3d-6a4f-47ce-aaa5-9d74c5590ed6%2FSQLServerBuilds.xlsx).
 1. If the `DBCC CHECKDB` errors are intermittent, that is if they appear on one run and disappear on the next one, you might be facing disk cache issues (either device driver or other I/O path issue). Work with the maintainers of the I/O path to isolate and resolve any problems. Examples include updating device drivers, checking configuration of the entire I/O path, and updating firmware and BIOS on the I/O path devices and system.
@@ -81,7 +81,7 @@ The cause of these problems can range from file system corruption, underlying ha
 To identify the root cause of database consistency errors, consider these methods:
 
 - Check the Windows System Event Log for any system level, driver, or disk-related errors and work with your hardware manufacturer to resolve them.
-- Run any diagnostics provided by your hardware manufacturers for the computer and/or disk system.
+- Run any diagnostics provided by your hardware manufacturers for the computer and/or disk system. Most systems provide BIOS/UEFI built-in diagnostics for storage (hard drives), memory, CPUs, system boards, RAID arrays, and multiple other components. 
 - Work with your hardware vendor or device manufacturer to make sure that:
   - The hardware devices and the configuration confirm to the [Microsoft SQL Server Database Engine Input/Output requirements](database-engine-input-output-requirements.md).
   - The device drivers and other supporting software components of all devices in the I/O path are updated.