Merge pull request #7932 from MicrosoftDocs/main

Auto push to live 2024-12-24 02:00:02

Author: Deland-Han

.openpublishing.redirection.json

@@ -11147,7 +11147,7 @@
     },
     {
       "source_path": "support/windows-server/active-directory/lingering-objects-remain.md",
-      "redirect_url": "/previous-versions/troubleshoot/windows-server/lingering-objects-remain",
+      "redirect_url": "/troubleshoot/windows-server/active-directory/manually-remove-lingering-objects",
       "redirect_document_id": false
     },
     {

support/azure/azure-kubernetes/create-upgrade-delete/error-code-outboundconnfailvmextensionerror.md

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the OutboundConnFailVMExtensionError error code (50)
 description: Learn how to troubleshoot the OutboundConnFailVMExtensionError error (50) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 01/24/2024
-ms.reviewer: rissing, chiragpa, v-leedennis, jovieir
+ms.date: 12/23/2024
+ms.reviewer: rissing, chiragpa, jaewonpark, v-leedennis, jovieir, v-weizhu
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 ---
@@ -114,8 +114,7 @@ There are many reasons why the traffic might be blocked. In any of these situati
 The following table lists specific reasons why traffic might be blocked, and the corresponding solution for each reason.
 | Issue | Solution |
 | ----- | -------- |
-| Traffic is blocked by firewall rules or a proxy server | In this scenario, a firewall or a proxy server does egress filtering. To verify that all required domains and ports are allowed, see [Control egress traffic for cluster nodes in Azure Kubernetes Service (AKS)](/azure/aks/limit-egress-traffic). |
-| Traffic is blocked by a cluster network security group (NSG) | On any NSGs that are attached to your cluster, verify that there's no blocking on port 443, port 53, or any other port that might have to be used to connect to the endpoint. For more information, see [Control egress traffic for cluster nodes in Azure Kubernetes Service (AKS)](/azure/aks/limit-egress-traffic). |
+| Traffic is blocked by firewall rules, a proxy server or Network Security Group (NSG) | This issue occurs when the AKS required ports or Fully Qualified Domain Names (FQDNs) are blocked by a firewall, proxy server, or NSG. Ensure these ports and FQDNs are allowed. To determine what's blocked, check the connectivity provided in the preceeding [Cause](#cause) section. For more information about AKS required ports and FQDNs, see [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress).|
 | The AAAA (IPv6) record is blocked on the firewall | On your firewall, verify that nothing exists that would block the endpoint from resolving in Azure DNS. |
 | Private cluster can't resolve internal Azure resources | In private clusters, the Azure DNS IP address (`168.63.129.16`) must be added as an upstream DNS server if custom DNS is used. Verify that the address is set on your DNS servers. For more information, see [Create a private AKS cluster](/azure/aks/private-clusters) and [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16) |
 

support/azure/azure-monitor/app-insights/telemetry/troubleshoot-webpages-issues.md

@@ -9,11 +9,22 @@ ms.reviewer: mmcc, toddfous, aaronmax, v-weizhu
 ---
 # Troubleshoot Application Insights JavaScript SDK for webpages
 
-The article explains certain issues involving [Application Insights JavaScript SDK for webpages](/azure/azure-monitor/app/javascript) and offers strategies to help fix these issues.
+The article explains certain issues that involve [Application Insights JavaScript SDK for webpages](/azure/azure-monitor/app/javascript) and offers strategies to help fix these issues.
 
-## I'm getting an error message of "Failed to get Request-Context correlation header as it may be not included in the response or not accessible"
+## I'm seeing a "0" value recorded for page views in Application Insights
 
-The `correlationHeaderExcludedDomains` configuration property is an exclude list that disables correlation headers for specific domains. This option is useful if you include headers that cause the request to fail or not to be sent because of third-party server configuration. This property supports wildcards. Therefore, you can specify a value such as `*.queue.core.windows.net`. Avoid adding the application domain to this property because this stops the SDK from including the required distributed tracing `Request-Id`, `Request-Context`, and `traceparent` headers as part of the request.
+This is by design when instrumenting Single Page Applications (SPA). See the following [GitHub issue](https://github.com/microsoft/ApplicationInsights-JS/issues/1139). 
+
+Use any of the following workarounds, as appropriate: 
+
+- Manually calculate the duration between different route changes in the app, and feed that duration value into the trackPageView() method. See details [here](https://github.com/microsoft/ApplicationInsights-JS/issues/1139#issuecomment-566169033).
+- Use the startTrackPageView() and stopTrackPageView() methods as timers to calculate page load durations. See details [here](https://microsoft.github.io/ApplicationInsights-JS/webSdk/applicationinsights-web/classes/ApplicationInsights.html#startTrackPage).
+- Use sample app duration measuring for the SPA app. See details [here](https://github.com/microsoft/applicationinsights-react-js?tab=readme-ov-file#example-of-measuring-page-duration-in-an-spa).
+- Manually set an overridePageViewDuration value. See details [here](https://github.com/microsoft/ApplicationInsights-JS#:~:text=overridePageViewDuration).
+
+## I'm getting the following error message: "Failed to get Request-Context correlation header as it may be not included in the response or not accessible"
+
+The `correlationHeaderExcludedDomains` configuration property is an exclude list that disables correlation headers for specific domains. This option is useful if you include headers that cause the request to fail or not to be sent because of a third-party server configuration. This property supports wildcards. Therefore, you can specify a value such as `*.queue.core.windows.net`. Avoid adding the application domain to this property because doing this stops the SDK from including the required distributed tracing headers, `Request-Id`, `Request-Context`, and `traceparent`, as part of the request.
 
 ## I'm not sure how to update my third-party server configuration
 
@@ -23,10 +34,12 @@ The server side must be able to accept connections that have certain headers. De
 
 ## I'm receiving duplicate telemetry data from the Application Insights JavaScript SDK
 
-If the SDK reports correlation recursively, enable the configuration setting of `excludeRequestFromAutoTrackingPatterns` to exclude the duplicate data. This scenario can occur if you use connection strings. The syntax for the configuration setting is `excludeRequestFromAutoTrackingPatterns: [<endpointUrl>]`.
+If the SDK reports correlation recursively, enable the configuration setting of `excludeRequestFromAutoTrackingPatterns` to exclude the duplicate data. This scenario might occur if you use connection strings. The syntax for the configuration setting is `excludeRequestFromAutoTrackingPatterns: [<endpointUrl>]`.
 
-## Connectivity issues occur between your application host and the ingestion service
+## I'm experiencing connectivity issues between my application host and the ingestion service
 
 Application Insights SDKs and agents send telemetry to get ingested as REST calls to our ingestion endpoints. To test connectivity from your web server or application host device to the ingestion service endpoints, use raw REST clients from PowerShell or [curl](https://curl.se/docs/manpage.html) commands. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
 
+[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-contact-disclaimer.md)]
+
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/virtual-machines/linux/leapp-upgrade-rhel-8dotx-to-9dotx-saphana-sapapps.md

@@ -2,7 +2,7 @@
 title: Leapp upgrade from RHEL 8.x to RHEL 9.x on SAP-HANA and SAP-APPS pay-as-you-go VMs
 description: Provides steps to help you upgrade SAP-HANA and SAP-APPS pay-as-you-go virtual machines from RHEL 8.x to RHEL 9.x by using the Leapp tool.
 ms.reviewer: divargas, msaenzbo, v-weizhu
-ms.date: 09/14/2024
+ms.date: 12/24/2024
 ms.service: azure-virtual-machines
 ms.topic: how-to
 ms.custom: sap:VM Admin - Linux (Guest OS), linux-related-content
@@ -45,9 +45,6 @@ According to the [Upgrading SAP environments from RHEL 8 to RHEL 9 - Supported u
 
 SAP validates SAP NetWeaver for each major RHEL version. The supported in-place upgrade paths for an SAP NetWeaver system are the two latest Extended Update Support (EUS)/Update Services for SAP Solutions (E4S) releases that the Leapp tool supports for non-HANA systems. For more information, see [Upgrading from RHEL 8 to RHEL 9 - Supported upgrade paths](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/upgrading_from_rhel_8_to_rhel_9). Certain deviations from the default upgrade procedure are described in [Upgrading an SAP NetWeaver system](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_for_sap_solutions/9/html/upgrading_sap_environments_from_rhel_8_to_rhel_9/asmb_upgrading_netweaver_asmb_upgrading-hana-system). For systems where both SAP HANA and SAP NetWeaver are installed, the SAP HANA restrictions apply.
 
-> [!IMPORTANT]  
-> When you upgrade a RHEL VM for SAP HANA or SAP Applications from 8.10 to 9.4, there is a known issue due to the RHUI client RPM name difference in 8.10 compared to earlier versions. As a result, the upgrade is currently not possible, and no workaround is available. However, the upgrade from 8.8 to 9.2 is unaffected by this issue. This article will be updated once the issue is resolved. Then, you can follow the steps in this article to perform the upgrade from 8.10 to 9.4.
-
 ### [RHEL 8.8 to RHEL 9.2 - SAP-HANA PAYG VMs](#tab/rhel92saphana)
 
 This section outlines the necessary steps before performing an in-place upgrade from RHEL 8.8 to RHEL 9.2 using the Leapp utility on SAP-HANA PAYG VMs.