Merge branch 'MicrosoftDocs:main' into patch-3

Author: sevend2

support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Azure Monitor Application Insights for Java
 description: This article presents troubleshooting information for the Java agent for Azure Monitor Application Insights.
 ms.topic: conceptual
-ms.date: 11/06/2024
+ms.date: 01/10/2025
 editor: v-jsitser
 ms.reviewer: aaronmax, jeanbisutti, trstalna, toddfous, heya, v-leedennis
 ms.service: azure-monitor
@@ -253,6 +253,32 @@ You can also try the [monitoring solutions for Java native](/azure/azure-monitor
 - With Spring Boot, the Microsoft distribution of the OpenTelemetry starter.
 - With Quarkus, the Quarkus Opentelemetry Exporter for Microsoft Azure.
 
+
+## Understand duplicated operation IDs
+
+Application logic can result in an operation ID being reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, use one of the following methods:
+
+* Enable the capture of the `traceparent` header in the **applicationinsigths.json** file as follows:
+
+    ```json
+      {
+        "preview": {
+          "captureHttpServerHeaders": {
+            "requestHeaders": [
+              "traceparent"
+            ]
+          }
+        }
+      }
+    ```
+* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and restart the application.
+
+    In the following log example, the operation ID comes from an incoming request, not Application Insights:
+
+    ```output
+    {"ver":1,"name":"Request",...,"ai.operation.id":"4e757357805f4eb18705abd24326b550)","ai.operation.parentId":"973487efc3db7d03"},"data":{"baseType":"RequestData","baseData":{...,"properties":{"http.request.header.traceparent":"00-4e757357805f4eb18705abd24326b550-973487efc3db7d03-01", ...}}}}
+    ```
+
 [!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]
 
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

@@ -103,6 +103,7 @@ If content doesn't exist for the error code, follow the general troubleshooting
 | 0x800703e3 | -2147023901 | ERROR_OPERATION_ABORTED | The file failed to tier because it was recalled at the same time. | No action required. The file will be tiered when the recall completes and the file is no longer in use. |
 | 0x80c80264 | -2134375836 | ECS_E_GHOSTING_FILE_NOT_SYNCED | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
 | 0x80070001 | -2147942401 | ERROR_INVALID_FUNCTION | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
+| 0x80c86041 | -2134351807 | ECS_E_AFS_FILTER_NOT_LOADED | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
 | 0x80070070 | -2147024784 | ERROR_DISK_FULL | The file failed to tier due to insufficient disk space on the volume where the server endpoint is located. | To resolve this issue, free at least 100 MiB of disk space on the volume where the server endpoint is located. |
 | 0x80070490 | -2147023728 | ERROR_NOT_FOUND | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
 | 0x80c80262 | -2134375838 | ECS_E_GHOSTING_UNSUPPORTED_RP | The file failed to tier because it's an unsupported reparse point. | If the file is a Data Deduplication reparse point, follow the steps in the [planning guide](/azure/storage/file-sync/file-sync-planning#data-deduplication) to enable Data Deduplication support. Files with reparse points other than Data Deduplication aren't supported and won't be tiered.  |

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-installation.md

@@ -67,6 +67,11 @@ MSI (s) (0C:C8) [12:23:40:994]: Note: 1: 2265 2:  3: -2147287035
 
 For this example, the agent installation failed with error code -2147287035 (ERROR_ACCESS_DENIED).
 
+<a id="agent-installation-gpo"></a>**Agent installation fails with error: ERROR_NO_SYSTEM_RESOURCES with Error Code 0x800705AA**
+
+The agent installation failed due to insufficient system resources. To resolve this issue, please free up memory on the server and retry installation.
+
+
 <a id="agent-installation-gpo"></a>**Agent installation fails with error: Storage Sync Agent Setup Wizard ended prematurely because of an error**
 
 In the agent installation log, the following error is logged:
@@ -174,7 +179,7 @@ This issue occurs due to a known issue that has been fixed in File Sync Agent v1
 
 :::image type="content" source="media/file-sync-troubleshoot-installation/server-already-registered-error.png" alt-text="Screenshot that shows the Server Registration dialog box with the 'server is already registered' error message.":::
 
-This message appears if the server was previously registered with a Storage Sync Service. To unregister the server from the current Storage Sync Service and then register with a new Storage Sync Service, complete the steps that are described in [Unregister a server with Azure File Sync](/azure/storage/file-sync/file-sync-server-registration#unregister-the-server-with-storage-sync-service).
+This message with error code 0x80C80064 appears if the server was previously registered with a Storage Sync Service.  To unregister the server from the current Storage Sync Service and then register with a new Storage Sync Service, complete the steps that are described in [Unregister a server with Azure File Sync](/azure/storage/file-sync/file-sync-server-registration#unregister-the-server-with-storage-sync-service).
 
 If the server isn't listed under **Registered servers** in the Storage Sync Service, on the server that you want to unregister, run the following PowerShell commands:
 

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -280,6 +280,13 @@ No action required. Azure File Sync has a scheduled task (VssSyncScheduledTask)
 | **Error string** | WININET_E_TIMEOUT |
 | **Remediation required** | Yes |
 
+| Error | Code |
+|-|-|
+| **HRESULT** | 0x80072EFE |
+| **HRESULT (decimal)** | -2147012866 |
+| **Error string** | WININET_E_CONNECTION_ABORTED |
+| **Remediation required** | Yes |
+
 This error can occur whenever the Azure File Sync service is inaccessible from the server. You can troubleshoot this error by working through the following steps:
 
 1. Verify the Windows service *FileSyncSvc.exe* is not blocked by your firewall.

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-group-management.md

@@ -100,7 +100,7 @@ This error occurs because Azure File Sync doesn't support server endpoints on vo
     compact /u /s
     ```
 
-<a id="-2134376345"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2134376345 or 0x80C80067)**
+<a id="-2134376345"></a>**Server endpoint creation fails, with this error message: "The server endpoints per server limit has been reached" (Error code: -2134376345 or 0x80C80067)**
 
 This error occurs if the limit of server endpoints per server is reached. Azure File Sync currently supports up to 30 server endpoints per server. For more information, see
 [Azure File Sync scale targets](/azure/storage/files/storage-files-scale-targets?toc=/azure/storage/filesync/toc.json#azure-file-sync-scale-targets).

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot.md

@@ -104,6 +104,11 @@ After installing or upgrading the Azure File Sync agent (v17.3 or later), you ma
   ```
 
 - ServerRegistration.exe or AfsUpdater.exe fails to open
+- Agent installation fails and installation log shows error code 0x80c84111 with message:
+
+  ```
+  Exception occurred while configuring MitigationRedirection policy. This could indicate that required windows updates not installed on the computer.
+  ```
 
 This issue occurs because the Azure File Sync agent has a dependency on a Windows security feature and updates for this security feature are not installed.
 

support/azure/virtual-machines/linux/serial-console-linux.md

@@ -12,7 +12,7 @@ ms.collection: linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 11/21/2024
+ms.date: 01/09/2025
 ms.author: mbifeld
 ---
 
@@ -116,7 +116,7 @@ Serial Console uses the storage account configured for boot diagnostics in its c
    | Australia | Australia Central, Australia Central 2, Australia East, Australia Southeast | 4.198.45.55, 4.200.251.224, 20.167.131.228, 20.53.52.250, 20.53.53.224, 20.53.55.174, 20.70.222.112, 20.70.222.113, 68.218.123.133 |
    | Brazil | Brazil South, Brazil Southeast | 20.206.0.192, 20.206.0.193, 20.206.0.194, 20.226.211.157, 108.140.5.172, 191.234.136.63, 191.238.77.232, 191.238.77.233 |
    | Canada | Canada Central, Canada East | 20.175.7.183, 20.48.201.78, 20.48.201.79, 20.220.7.246, 52.139.106.74, 52.139.106.75, 52.228.86.177, 52.242.40.90 |
-   | Canary (EUAP) | Canary | 20.45.242.18, 20.51.21.252 |
+   | Canary (EUAP) | US Central EUAP, US East 2 EUAP | 20.45.242.18, 20.45.242.19, 20.45.242.20, 20.47.232.186, 20.47.232.187, 20.51.21.252, 68.220.123.194, 168.61.232.59 |
    | China | China North 3, China East 3 | 163.228.102.122, 163.228.102.123, 52.131.192.182, 52.131.192.183, 159.27.255.76, 159.27.253.236, 163.228.102.122, 163.228.102.123, 52.131.192.182, 52.131.192.183 |
    | Europe | Europe North, Europe West | 4.210.131.60, 20.105.209.72, 20.105.209.73, 40.113.178.49, 52.146.137.65, 52.146.139.220, 52.146.139.221, 98.71.107.78 |
    | France | France Central, France South | 20.111.0.244, 40.80.103.247, 51.138.215.126, 51.138.215.127, 52.136.191.8, 52.136.191.9, 52.136.191.10, 98.66.128.35 |

support/azure/virtual-machines/windows/serial-console-windows.md

@@ -11,7 +11,7 @@ ms.collection: windows
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 11/22/2024
+ms.date: 01/10/2025
 ms.author: mbifeld
 ms.custom: sap:VM Admin - Windows (Guest OS)
 ---
@@ -170,7 +170,7 @@ Serial Console uses the storage account configured for boot diagnostics in its c
    | Australia | Australia Central, Australia Central 2, Australia East, Australia Southeast | 4.198.45.55, 4.200.251.224, 20.167.131.228, 20.53.52.250, 20.53.53.224, 20.53.55.174, 20.70.222.112, 20.70.222.113, 68.218.123.133 |
    | Brazil | Brazil South, Brazil Southeast | 20.206.0.192, 20.206.0.193, 20.206.0.194, 20.226.211.157, 108.140.5.172, 191.234.136.63, 191.238.77.232, 191.238.77.233 |
    | Canada | Canada Central, Canada East | 20.175.7.183, 20.48.201.78, 20.48.201.79, 20.220.7.246, 52.139.106.74, 52.139.106.75, 52.228.86.177, 52.242.40.90 |
-   | Canary (EUAP) | Canary | 20.45.242.18, 20.51.21.252 |
+   | Canary (EUAP) | US Central EUAP, US East 2 EUAP | 20.45.242.18, 20.45.242.19, 20.45.242.20, 20.47.232.186, 20.47.232.187, 20.51.21.252, 68.220.123.194, 168.61.232.59 |
    | China | China North 3, China East 3 | 163.228.102.122, 163.228.102.123, 52.131.192.182, 52.131.192.183, 159.27.255.76, 159.27.253.236, 163.228.102.122, 163.228.102.123, 52.131.192.182, 52.131.192.183 |
    | Europe | Europe North, Europe West | 4.210.131.60, 20.105.209.72, 20.105.209.73, 40.113.178.49, 52.146.137.65, 52.146.139.220, 52.146.139.221, 98.71.107.78 |
    | France | France Central, France South | 20.111.0.244, 40.80.103.247, 51.138.215.126, 51.138.215.127, 52.136.191.8, 52.136.191.9, 52.136.191.10, 98.66.128.35 |

support/developer/webapps/iis/health-diagnostic-performance/toc.yml

@@ -13,8 +13,6 @@ items:
   href: hidden-static-files-http-404-access-denied.md
 - name: HTTP error 400 in the CLM portal
   href: clm-http-bad-request.md
-- name: HTTP error 403.16
-  href: http-403-forbidden-access-website.md
 - name: HTTP error 403.7
   href: http-error-403-7-forbidden-web-app.md
 - name: HTTP error 404 file not found on a server

…nce/http-403-forbidden-access-website.md …nce/http-403-forbidden-access-website.mdsupport/developer/webapps/iis/health-diagnostic-performance/http-403-forbidden-access-website.md renamed to support/developer/webapps/iis/site-behavior-performance/http-403-forbidden-access-website.md support/developer/webapps/iis/health-diagnostic-performance/http-403-forbidden-access-website.md renamed to support/developer/webapps/iis/site-behavior-performance/http-403-forbidden-access-website.md

@@ -1,20 +1,20 @@
 ---
 title: HTTP Error 403.16 when you access a website
-description: This article describes the problem where an HTTP 403.16 error occurs when you try to access a website that's hosted by IIS 7.0.
-ms.date: 03/26/2020
+description: This article describes the problem where an HTTP 403.16 error occurs when you try to access a website that's hosted on IIS.
+ms.date: 01/09/2025
 ms.custom: sap:Site Behavior and Performance\Runtime errors and exceptions, including HTTP 400 and 50x errors
-ms.reviewer: mlaing
+ms.reviewer: mlaing, paulboc
 ---
-# HTTP Error 403.16 when you try to access a website that's hosted on IIS 7.0
+# HTTP Error 403.16 when you try to access a website that's hosted on IIS
 
-This article helps you resolve the **HTTP 403.16 - Forbidden** error that occurs when you access a website that's hosted on Internet Information Services (IIS) 7.0.
+This article helps you resolve the "HTTP 403.16 - Forbidden" error that occurs when you access a website that's hosted on Internet Information Services (IIS).
 
-_Original product version:_   Internet Information Services 7.0  
+_Original product version:_   Internet Information Services  
 _Original KB number:_   942061
 
 ## Symptoms
 
-You have a website that's hosted on IIS 7.0. When you try to access the site through a web browser, you receive an error message that resembles one of the following examples.
+You have a website hosted on the IIS web server that ships with Windows Server 2016 or later. When you try to access the site through a web browser, you receive an error message that resembles one of the following examples:
 
 - Error message 1
 
@@ -35,13 +35,9 @@ This problem occurs because the root certificate of the certification authority
 > [!NOTE]
 > The root certificate of the certification authority is used to issue the client certificate.
 
-## Cause 2: Non-self-signed certificates are in Trusted Root Certification Authorities Certificate store
-
-There are one or more non-self-signed certificates in the Trusted Root Certification Authorities Certificate store. A non-self-signed certificate is any certificate for which the `Issued To` and `Issued By` values aren't an exact match.
-
-## Resolution for cause 1
+### Resolution for cause 1
 
-1. On the IIS Web server, select **Start**, type *mmc.exe* in the **Start Search** box, right-click mmc.exe, and then select **Run as administrator**.
+1. On the IIS Web server, select **Start**, type *mmc.exe* in the **Start Search** box, right-click **mmc.exe**, and then select **Run as administrator**.
 
     > [!NOTE]
     > If you are prompted for an administrator password or for a confirmation, type the password, or select **Continue**.
@@ -51,12 +47,16 @@ There are one or more non-self-signed certificates in the Trusted Root Certifica
 4. Select **Computer account**, and then select **Next**.
 5. Select **Local computer**, select **Finish**, and then select **Close**.
 6. To exit the wizard, select **OK**.
-7. Expand **Certificates**, expand **Trusted Root Certification Authorities**, right-click **Certificates**, point to **All Tasks**, and then select **Import**.
+7. Expand **Certificates** > **Trusted Root Certification Authorities**, right-click **Certificates**, point to **All Tasks**, and then select **Import**.
 8. In the Certificate Import Wizard, select **Next**.
 9. In the **File name** box, type the location of the root certificate of the certification authority, and then select **Next**.
-10. Select **Next**, and then select **Finish**.
+10. Select **Next** > **Finish**.
+
+## Cause 2: Non-self-signed certificates are in Trusted Root Certification Authorities Certificate store
+
+There are one or more non-self-signed certificates in the Trusted Root Certification Authorities Certificate store. A non-self-signed certificate is any certificate for which the `Issued To` and `Issued By` values aren't an exact match.
 
-## Resolution for cause 2
+### Resolution for cause 2
 
 Move any non-self-signed certificated out of the Trusted Root Certification Authorities Certificate store and into the Intermediate Certification Authorities Certificate store.