Merge pull request #8068 from MicrosoftDocs/main

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

Author: Deland-Han

.openpublishing.redirection.developer.json

@@ -5842,6 +5842,10 @@
     {
       "source_path": "support/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md",
       "redirect_url": "/troubleshoot/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-native-memory-leak-iis-7x-application-pool.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-native-memory-leak-iis-7x-application-pool"
     }
   ]
 }

support/azure/automation/updates/find-azurermresource-fails.md

@@ -25,6 +25,6 @@ Starting in Microsoft AzureRM 6.0.0, the `Find-AzureRmResource` cmdlet functiona
 
 ## Resolution
 
-To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/powershell/module/azurerm.resources/get-azurermresource?view=azurermps-6.1.0&preserve-view=true).
+To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/previous-versions/powershell/module/azurerm.resources/get-azurermresource).
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/extensions/troubleshoot-failed-kubernetes-deployment-offer.md

@@ -132,7 +132,7 @@ You can use the Azure CLI commands that are described in the [Azure CLI legal te
 
 #### [PowerShell](#tab/PowerShell)
 
-To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/azurerm.marketplaceordering).
+To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/az.marketplaceordering).
 
 ---
 

support/azure/synapse-analytics/dedicated-sql/connectivity/dsql-conn-dropped-connections.md

@@ -38,7 +38,7 @@ The following PowerShell script downloads and runs the latest version of the Azu
 
 > [!NOTE]
 > - To run the tests in Linux, from computers that have no Internet access, or from a containerized environment, see [SQL connectivity checker on GitHub](https://github.com/Azure/SQL-Connectivity-Checker).
-> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/azurerm.sql#sql).
+> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/az.sql#sql).
 
 1. Open Windows PowerShell ISE (in **Administrator** mode if possible).
    > [!NOTE]

support/azure/virtual-machines/windows/extension-version-2.2-not-supported.md

@@ -26,7 +26,7 @@ To work around this problem, use one of the following methods.
 
 ### Method 1
 
-Revert to using the Microsoft Entra parameters in the syntax for [Set-AzureRmVmDiskEncryptionExtension](/powershell/module/azurerm.compute/set-azurermvmdiskencryptionextension?view=azurermps-6.2.0&preserve-view=true).
+Revert to using the Microsoft Entra parameters in the syntax for [Set-AzVMDiskEncryptionExtension](/powershell/module/az.compute/set-azvmdiskencryptionextension).
 
 The parameters are the following:
 
@@ -40,7 +40,7 @@ The parameters are the following:
 Opt in to the "UnifiedDiskEncryptionForVMs" feature for your subscription by running the following script before you try again to enable encryption:
 
 ```powershell
-Register-AzureRmProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureName "UnifiedDiskEncryptionForVMs" # Wait 10 minutes until state transitions to 'Registered' Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute
+Register-AzProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureName "UnifiedDiskEncryptionForVMs" # Wait 10 minutes until state transitions to 'Registered' Register-AzResourceProvider -ProviderNamespace Microsoft.Compute
 ```
 
 ## More Information
@@ -50,18 +50,18 @@ Register-AzureRmProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureN
 Run the following script:
 
 ```
-Set-AzureRmVMDiskEncryptionExtension -ResourceGroupName $resourceGroupName -VMName $vmName -DiskEncryptionKeyVaultUrl $diskEncryptionKeyVaultUrl -DiskEncryptionKeyVaultId $keyVaultResourceId -KeyEncryptionKeyUrl $keyEncryptionKeyUrl -KeyEncryptionKeyVaultId $keyVaultResourceId -VolumeType 'All';
+Set-AzVMDiskEncryptionExtension -ResourceGroupName $resourceGroupName -VMName $vmName -DiskEncryptionKeyVaultUrl $diskEncryptionKeyVaultUrl -DiskEncryptionKeyVaultId $keyVaultResourceId -KeyEncryptionKeyUrl $keyEncryptionKeyUrl -KeyEncryptionKeyVaultId $keyVaultResourceId -VolumeType 'All';
 DEBUG: 10:47:22 AM - SetAzureDiskEncryptionExtensionCommand end processing.
-Set-AzureRmVMDiskEncryptionExtension : Azure Disk Encryption extension version '2.2' is not supported.
+Set-AzVMDiskEncryptionExtension : Azure Disk Encryption extension version '2.2' is not supported.
 ErrorCode: NotSupported
 ErrorMessage: Azure Disk Encryption extension version '2.2' is not supported.
 StatusCode: 409
 ReasonPhrase: Conflict
 OperationID : 2cb4ac35-e2a5-4cd4-84d9-3174663e0a46
 At line:1 char:1
-+ Set-AzureRmVMDiskEncryptionExtension -ResourceGroupName $resourceGrou ...
++ Set-AzVMDiskEncryptionExtension -ResourceGroupName $resourceGrou ...
 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-    + CategoryInfo          : CloseError: (:) [Set-AzureRmVMDiskEncryptionExtension], ComputeCloudException
+    + CategoryInfo          : CloseError: (:) [Set-AzVMDiskEncryptionExtension], ComputeCloudException
 ```
 
 ## Status

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

@@ -43,8 +43,6 @@ items:
   href: troubleshoot-failed-requests-using-tracing-in-iis-85.md
 - name: Troubleshoot high CPU usage in an IIS app pool
   href: troubleshoot-high-cpu-in-iis-app-pool.md
-- name: Troubleshoot native memory leak in an IIS 7.x application pool
-  href: troubleshoot-native-memory-leak-iis-7x-application-pool.md
 - name: Troubleshoot PHP errors with Failed Request Tracing
   href: troubleshoot-php-with-failed-request-tracing.md
 - name: Troubleshoot IIS performance issues and application errors

support/developer/webapps/iis/site-behavior-performance/data-capture-managed-memory-leak.md

@@ -0,0 +1,81 @@
+---
+title: Data Capture for Managed Memory Leaks
+description: This article provides methods to capture data for managed memory leaks.
+ms.date: 01/17/2025
+ms.custom: sap:Site Behavior and Performance\High memory usage
+ms.reviewer: khgupta, v-sidong, mouradl, apkakh
+---
+
+# Data capture for managed memory leaks
+
+If your application is consuming high memory due to [managed memory leaks](high-memory-consumption-issues-overview.md#identify-whether-the-memory-leak-is-managed-or-native),
+collect memory dumps of the process during the high memory usage event. These dumps can help you analyze and diagnose the cause of these leaks.
+
+This article outlines the steps to capture memory dumps associated with managed memory leaks, both for consistently reproducible and intermittent cases.
+
+For more information on how to analyze memory dumps along with an example scenario, see [Troubleshooting example](high-memory-consumption-issues-overview.md#troubleshooting-example).
+
+## Memory leak issue is easily replicable
+
+If the memory leak issue can be consistently reproduced whenever needed, use one of the following methods to capture data.
+
+### Method 1: Using Procdump
+
+[!INCLUDE [Note when using Procdump](../../../../includes/note-using-procdump.md)]
+
+[!INCLUDE [Same steps when using Procdump](../../../../includes/same-steps-using-procdump.md)]  
+
+4. Run the command: `procdump.exe -s 30 -ma -n 3 <PID>`.
+
+   [!INCLUDE [How to get actual PID](../../../../includes/how-get-pid.md)]
+
+   - `-n`: This parameter is the number of memory dumps to collect.
+   - `-s`: This parameter is the interval (in seconds) between dumps.
+
+[!INCLUDE [Run command again with new PID](../../../../includes/run-command-new-pid-procdump.md)]
+
+### Method 2: Using DebugDiag
+
+1. Download and install [Debug Diagnostic Tool v2 Update 3.2](https://www.microsoft.com/download/details.aspx?id=103453).
+1. When a memory leak occurs, open **DebugDiag 2 Collection** from the **Start** menu:  
+   
+   :::image type="content" source="media/data-capture-managed-memory-leak/debugdiag-2-collection.png" alt-text="Screenshot of DebugDiag 2 Collection.":::
+
+   > [!NOTE]
+   > If you need to change the path where dumps are generated, select **Tools** > **Options And Settings** > **Manual Userdump Save Folder** to change it.
+1. Select the **Processes** tab.
+1. Locate the **w3wp** process with the **Process ID** column of the application in question.  
+   [!INCLUDE [How to get actual PID](../../../../includes/how-get-pid.md)]
+1. Right-click the **w3wp** process, select **Create Userdump Series**, and set the following options (adjust the numbers as needed). Don't select **Save & Close**.  
+   
+   :::image type="content" source="media/data-capture-managed-memory-leak/configure-userdump-series.png" alt-text="Screenshot of Configure UserDump Series.":::
+   
+1. Once the memory consumption of **w3wp.exe** reaches the limit as described in the [Memory limits for different scenarios](high-memory-consumption-issues-overview.md#memory-limits-for-different-scenarios), select **Save & Close**.
+
+   The dumps will start generating immediately.
+
+## Memory leak issue is intermittent
+
+If the memory leak issue is intermittent, you can automate the data capture process using the following steps:
+
+[!INCLUDE [Note when using Procdump](../../../../includes/note-using-procdump.md)]
+
+[!INCLUDE [Same steps when using Procdump](../../../../includes/same-steps-using-procdump.md)]  
+
+4. Run the command: `procdump.exe -s 30 -m <memoryConsumption> -ma -n 3 <PID>`.
+
+   [!INCLUDE [How to get actual PID](../../../../includes/how-get-pid.md)]
+
+   - `-n`: This parameter is the number of memory dumps to collect.  
+   - `-m`: This parameter is the memory commit threshold (in MB) for creating dumps.  
+   - `-s`: This parameter might have different meanings based on the other parameters in the `procdump` command.  
+
+   When you use `-m` in the command, `-s` indicates the number of consecutive seconds during which **w3wp.exe**'s memory consumption is >= the threshold specified by `-m`.  
+
+   For example, if the command is `procdump.exe -s 30 -m 5120 -ma -n 3 <PID>`, the process memory consumption must be >= 5,120 MB (5 GB) for at least 30 seconds to generate a dump. If the first dump is written but then memory drops to less than 5,120 MB, the second and third dumps won't be collected, and the memory must increase back to 5,120 MB or higher and remain so for 30 seconds for the second dump to be generated, and so on. So, `-s` here doesn't necessarily mean the interval between the dumps.
+
+[!INCLUDE [Run command again with new PID](../../../../includes/run-command-new-pid-procdump.md)]
+
+## More information
+
+[Overview of high memory consumption issues](high-memory-consumption-issues-overview.md)