Merge pull request #8341 from MicrosoftDocs/main

Deland-Han · web-flow · commit b9cd76ada524 · 2025-02-28T10:00:07.000+08:00
Auto push to live 2025-02-27 18:00:02
diff --git a/support/azure/virtual-machines/windows/allocation-failure.md b/support/azure/virtual-machines/windows/allocation-failure.md
@@ -154,7 +154,7 @@ To work around this issue, use one of the following methods:
 
 ### Cause
 
-When the Azure Compute platform can't allocate a VM to meet the required constraints specified in the request, overconstrained allocation failures occur. These failures typically happen when specific requirements can’t be met within the available resources. They are often indicated by errors like `OverconstrainedZonalAllocationRequest` or `OverconstrainedAllocationRequest`.
+When the Azure Compute platform can't allocate a VM to meet the required constraints specified in the request, overconstrained allocation failures occur. These failures typically happen when specific requirements can't be met within the available resources. They are often indicated by errors like `OverconstrainedZonalAllocationRequest` or `OverconstrainedAllocationRequest`.
 
 These constraints usually (but not always) include the following items:
 
@@ -232,7 +232,7 @@ The servers in Azure datacenters are partitioned into clusters. Normally, an all
 
 ### Why allocation failures happen
 
-When an allocation has a large number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted (for example, when using proximity placement groups but the type of resource you requested isn’t supported by the set of clusters and nearby ones), your request fails even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the  proximity placement group don’t support the requested VM size, even though the clusters have free resources.
+When an allocation has a large number of restrictions, there's a higher chance of failing to find free resources since the available resource pool is smaller. Furthermore, if your allocation request is restricted (for example, when using proximity placement groups but the type of resource you requested isn't supported by the set of clusters and nearby ones), your request fails even if the cluster has free resources. The following Diagram 2 illustrates the case where an allocation fails because the candidate clusters associated with the proximity placement group don't have free resources. Diagram 3 illustrates the case where an allocation fails because the candidate clusters associated with the  proximity placement group don't support the requested VM size, even though the clusters have free resources.
 
 :::image type="content" source="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png" alt-text="Screenshot of Diagram 2 showing allocation failed with no free resource available and Diagram 3 showing allocation failed with size not supported." lightbox="media/virtual-machines-common-allocation-failure/allocation-failures-ppg.png":::
 
diff --git a/support/dynamics-365/supply-chain/asset-management/asset-id-not-editable-when-number-sequence-is-manual.md b/support/dynamics-365/supply-chain/asset-management/asset-id-not-editable-when-number-sequence-is-manual.md
@@ -0,0 +1,33 @@
+---
+title: Asset ID Isn't Editable When Number Sequence Is Set to Manual
+description: Provides a workaround for editing the Asset ID in Microsoft Dynamics 365 Supply Chain Management.
+author: sorenbacker2
+ms.author: sorenba
+ms.date: 02/28/2025
+ms.custom: sap:Asset management\Issues with asset management
+---
+# Asset ID isn't editable when the number sequence is set to Manual
+
+This article provides a workaround that allows the Asset ID to be edited in Microsoft Dynamics 365 Supply Chain Management.
+
+## Symptoms
+
+A user [creates a new asset](/dynamics365/supply-chain/asset-management/objects/create-objects-based-on-purchase-orders#select-asset-items) using the **Asset Management** page. The asset is created with an **Asset ID** value that the system generates based on the [number sequence](/dynamics365/supply-chain/asset-management/setup-for-objects/enterprise-asset-management-parameters#the-number-sequences-tab) selected on the **Asset management parameters** page. However, the **Asset ID** value can't be edited later, even though the related number sequence is set to **Manual** on the **Number sequences** details page.
+
+## Cause
+
+This behavior is by design. A user can't edit an existing **Asset ID** because the **Asset ID** is the natural key for the asset. Editing it can cause data corruption and unexpected behavior in case of integrations.
+
+## Workaround
+
+To allow a user to edit the **Asset ID** on an existing asset despite the risk of data corruption, a developer needs to extend the `EntAssetObjectTable` form and change the property of the field.
+
+1. Use Chain of Command (CoC) to change the control property by calling the `allowEdit()` method of the control and passing `false` as an argument.
+
+1. Create an extension class and extend the  `init()` form method to programmatically allow the field to be edited after the `next()` call.
+
+For a detailed explanation of the approach, see [Class extension - Method wrapping and Chain of Command](/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc).
+
+## More information
+
+[Set up number sequences on an individual basis](/dynamics365/fin-ops-core/fin-ops/organization-administration/tasks/set-up-number-sequences-individual-basis)
diff --git a/support/dynamics-365/supply-chain/toc.yml b/support/dynamics-365/supply-chain/toc.yml
@@ -2,6 +2,8 @@
   href: welcome-supply-chain.yml
 - name: Asset management
   items:
+    - name: Asset ID isn't editable when number sequence is set to Manual
+      href: asset-management/asset-id-not-editable-when-number-sequence-is-manual.md
     - name: Changing work order lifecycle state doesn't generate fault cause or fault remedy error
       href: asset-management/change-lifecycle-state-doesnt-create-fault.md
 - name: Inventory costing and closing
diff --git a/support/power-platform/dataverse/email-exchange-synchronization/emails-not-automatically-tracked-or-synchronized.md b/support/power-platform/dataverse/email-exchange-synchronization/emails-not-automatically-tracked-or-synchronized.md
@@ -36,11 +36,11 @@ To get troubleshooting information in the **Server-Side Synchronization Item Lev
 
 2. The **Sync Error** column contains information about why an item didn't synchronize. Selecting the link directs you to an article about the error, if available. For example:
 
-   - This screenshot shows a "Question about service" email that isn't automatically tracked due to an [IsvAborted](/troubleshoot/dynamics-365/sales/unknownincomingemailintegrationerror-2147220891) error that occurs during processing. This error indicates a failure within a plugin or workflow that needs to be addressed by the solution owner.
+   - This screenshot shows a "Question about service" email that isn't automatically tracked due to an [IsvAborted](unknownincomingemailintegrationerror-2147220891.md) error that occurs during processing. This error indicates a failure within a plugin or workflow that needs to be addressed by the solution owner.
 
      :::image type="content" source="media/emails-not-automatically-tracked-or-synchronized/question-about-service-email-example.png" alt-text="Screenshot that shows an IsvAborted error in a Question about service email.":::
 
-   - This screenshot shows a "Can we meet tomorrow?" email that isn't automatically tracked due to a [NoCorrelationMatch](/troubleshoot/dynamics-365/sales/email-fails-to-create-with-nocorrelationmatch-error) error. This error occurs because none of the resolved (known) Dataverse email recipients automatically accept the email based on their [personal option settings](/power-platform/admin/email-message-filtering-correlation).
+   - This screenshot shows a "Can we meet tomorrow?" email that isn't automatically tracked due to a [NoCorrelationMatch](email-fails-to-create-with-nocorrelationmatch-error.md) error. This error occurs because none of the resolved (known) Dataverse email recipients automatically accept the email based on their [personal option settings](/power-platform/admin/email-message-filtering-correlation).
 
      :::image type="content" source="media/emails-not-automatically-tracked-or-synchronized/can-we-meet-tomorrow-email-example.png" alt-text="Screenshot that shows a NoCorrelationMatch error in a Can we meet tomorrow email.":::
 
diff --git a/support/sql/releases/linux/release-history-2019.md b/support/sql/releases/linux/release-history-2019.md
@@ -67,6 +67,7 @@ The following table lists the release history for [!INCLUDE [sql-server-2019](..
 
 ## <a id="CU32"></a> CU 32 (February 2025)
 
+This is the Cumulative Update 31 (CU 31) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4420.2. For information about the fixes and improvements in this release, see the [Support article](../sqlserver-2019/cumulativeupdate31.md).
 This is the Cumulative Update 32 (CU 32) release of [!INCLUDE [sql-server-2019](../../includes/versions/sql-server-2019.md)]. The [!INCLUDE [sql-server-database-engine](../../includes/versions/sql-server-database-engine.md)] version for this release is 15.0.4430.1. For information about the fixes and improvements in this release, see the [Support article](/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate32).
 
 > [!IMPORTANT]  
diff --git a/support/windows/win32/toc.yml b/support/windows/win32/toc.yml
@@ -79,5 +79,7 @@
       href: addin-components-core-os-processes.md
     - name: GetTickCount resets to zero after approximately 776 days
       href: gettickcount-resets-zero-after-approximately-776-days.md
+    - name: The UMDH tool generates warnings
+      href: umdh-windows-11-sdk-not-work-fine.md
     - name: User32.dll or Kernel32.dll doesn't initialize
       href: user32-kernel32-not-initialize.md
diff --git a/support/windows/win32/umdh-windows-11-sdk-not-work-fine.md b/support/windows/win32/umdh-windows-11-sdk-not-work-fine.md
@@ -0,0 +1,30 @@
+---
+title: The UMDH Tool Generates Warnings
+description: Works around an issue where umdh.exe in the Windows SDK for Windows 11, the Windows Driver Kit for Windows 11, and the standalone toolsets doesn't work fine.
+ms.date: 02/28/2025
+ms.reviewer: hirotoh, v-sidong
+ms.custom: sap:System Services Development
+---
+# The UMDH tool generates warnings
+
+This article describes a known issue with the [User-Mode Dump Heap (UMDH)](/windows-hardware/drivers/debugger/umdh) tool that is installed with the [Debugging Tools for Windows](/windows-hardware/drivers/debugger/debugger-download-tools). The issue affects the UMDH tool included in the Windows SDK for Windows 11, the Windows Driver Kit for Windows 11, and the standalone toolsets.
+
+## Symptoms
+
+When the [UMDH](/windows-hardware/drivers/debugger/umdh) tool (also known as **umdh.exe**) executes, it displays the following messages and fails to capture memory allocations:
+
+```output
+Warning:
+Warning: UMDH didn't find any allocations that have stacks collected.
+Warning: Traces could not be collected because the Stack Trace Database is full.
+Warning: Increase the size of the Stack Trace Database using GFLAGS.
+Warning:
+```
+
+## Cause
+
+This is a bug in the UMDH tool included in the Windows SDK for Windows 11 and the Windows Driver Kit for Windows 11.
+
+## Workaround
+
+To work around the issue, install the [latest version of the Windows SDK for Windows 10](https://developer.microsoft.com/windows/downloads/sdk-archive/) or the [Windows Driver Kit for Windows 10](/windows-hardware/drivers/other-wdk-downloads) and use the UMDH tool in it.
