Merge branch 'main' of https://github.com/microsoftdocs/SupportArticles-docs-pr into main4493

genlin · genlin · commit 52bced12c046 · 2025-03-20T10:22:14.000+08:00
diff --git a/support/azure/.openpublishing.redirection.azure.json b/support/azure/.openpublishing.redirection.azure.json
@@ -6299,6 +6299,10 @@
       {
         "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
         "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"
       }
   ]
 }
diff --git a/support/azure/azure-kubernetes/connectivity/error-from-server-error-dialing-backend-dial-tcp.md b/support/azure/azure-kubernetes/connectivity/error-from-server-error-dialing-backend-dial-tcp.md
@@ -1,8 +1,8 @@
 ---
 title: 'Error from server: error dialing backend: dial tcp'
 description: 'Troubleshoot the error dialing backend: dial tcp error that blocks you from using kubectl commands or other tools when you connect to the API server.'
-ms.date: 10/21/2024
-ms.reviewer: chiragpa, nickoman, v-leedennis, pihe
+ms.date: 03/05/2025
+ms.reviewer: chiragpa, nickoman, v-leedennis, pihe, mariusbutuc
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the "Error from server: error dialing backend: dial tcp" error so that I can connect to the API server or use the `kubectl logs` command to get logs.
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverconnfailvmextensionerror.md b/support/azure/azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverconnfailvmextensionerror.md
@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the K8SAPIServerConnFailVMExtensionError error code (51)
 description: Learn how to troubleshoot the K8SAPIServerConnFailVMExtensionError error (51) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 01/24/2024
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir
+ms.date: 03/12/2025
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the K8SAPIServerConnFailVMExtensionError error code (or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully start or create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -50,4 +50,4 @@ In rare cases, the firewall's outbound IP address can be blocked if you've autho
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md b/support/azure/azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/quota-exceeded-during-creation-upgrade.md b/support/azure/azure-kubernetes/create-upgrade-delete/quota-exceeded-during-creation-upgrade.md
@@ -1,8 +1,8 @@
 ---
 title: QuotaExceeded or InsufficientVCPUQuota error during creation or upgrade
 description: Resolves a QuotaExceeded or InsufficientVCPUQuota error during a creation or upgrade operation in an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/25/2024
-ms.reviewer: chiragpa, nickoman, v-weizhu
+ms.date: 03/07/2025
+ms.reviewer: chiragpa, nickoman, v-weizhu, mariusbutuc
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to avoid the "QuotaExceeded" or "InsufficientVCPUQuota" error for virtual CPU (vCPU) usage so that I can create or upgrade an AKS cluster successfully.
diff --git a/support/azure/azure-kubernetes/error-codes/vmextensionerror-k8sapiserverdnslookupfail.md b/support/azure/azure-kubernetes/error-codes/vmextensionerror-k8sapiserverdnslookupfail.md
@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code 
 description: Learn how to troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail (52) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
-ms.date: 01/24/2024
-ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir
+ms.date: 03/12/2025
+ms.reviewer: rissing, chiragpa, erbookbi, v-leedennis, jovieir, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code (or error code ERR_K8S_API_SERVER_DNS_LOOKUP_FAIL, error number 52) so that I can successfully start or create and deploy an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
diff --git a/support/azure/azure-kubernetes/storage/create-file-share-failed-storage-account.md b/support/azure/azure-kubernetes/storage/create-file-share-failed-storage-account.md
@@ -1,8 +1,8 @@
 ---
 title: Failed to create file share on storage account
 description: Troubleshoot why you can't create a file share on a storage account for an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/20/2024
-ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis
+ms.date: 03/14/2025
+ms.reviewer: chiragpa, nickoman, wonkilee, v-leedennis, mariusbutuc
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot why I can't create a file share on a storage account so that I can do dynamic provisioning on my Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Storage
diff --git a/support/azure/azure-kubernetes/toc.yml b/support/azure/azure-kubernetes/toc.yml
@@ -109,8 +109,6 @@
       href: create-upgrade-delete/error-code-subnetisfull.md
     - name: Cluster upgrading and scaling errors
       href: create-upgrade-delete/upgrading-or-scaling-does-not-succeed.md
-    - name: Errors using features that require virtual machine scale sets
-      href: create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md
     - name: Node count isn't in autoscaler min and max range
       href: create-upgrade-delete/node-count-is-not-in-autoscaler-min-max-range.md
   - name: Start operations
diff --git a/support/power-platform/dataverse/toc.yml b/support/power-platform/dataverse/toc.yml
@@ -206,8 +206,12 @@
       href: working-with-solutions/error-when-uninstalling-portals-solutions.md
     - name: Duplicate security roles after solution import
       href: working-with-solutions/duplicate-security-roles.md
+    - name: Environment schema type mismatch warning during solution import
+      href: working-with-solutions/schemaType-mismatch-on-solution-import.md  
     - name: Error 8004F042 when importing solution patch
       href: working-with-solutions/error-code-8004f042-occurs.md
+    - name: Environment version mismatch warning during solution import
+      href: working-with-solutions/version-mismatch-on-solution-import.md
     - name: Failure when multiple publishers have shared components
       href: working-with-solutions/multiple-publisher-shared-component-failure.md
     - name: Form doesn't appear in target environment after import
@@ -226,10 +230,10 @@
       href: working-with-solutions/newly-added-components-dont-appear.md
     - name: Permission error 80040220 when importing or deleting solution
       href: working-with-solutions/error-when-you-import-delete-solution.md
+    - name: Resources to help troubleshoot solution import errors
+      href: working-with-solutions/troubleshoot-solution-import-errors-in-dynamics-365.md
     - name: Solution checker enforcement in Managed Environments blocks or warns on import
       href: working-with-solutions/solution-checker-enforcement-import-issues.md
-    - name: Solution import errors
-      href: working-with-solutions/troubleshoot-solution-import-errors-in-dynamics-365.md
     - name: Solution import or app installation fails due to missing privileges
       href: working-with-solutions/install-failure-priviledge-not-assigned.md
     - name: Solution upgrade fails due to a pending upgrade
diff --git a/support/power-platform/dataverse/working-with-solutions/assembly-version-error-importing-dynamics-365-solution.md b/support/power-platform/dataverse/working-with-solutions/assembly-version-error-importing-dynamics-365-solution.md
@@ -1,36 +1,48 @@
 ---
 title: Assembly version error when importing solution
-description: You may receive an assembly version error when importing a Microsoft Dynamics 365 solution. Provides a resolution.
-ms.reviewer: 
-ms.topic: troubleshooting
-ms.date: 03/31/2021
+description: Solves an assembly version error that might occur when importing a Microsoft Dynamics 365 solution.
+ms.date: 03/20/2025
 ms.custom: sap:Working with Solutions
 ---
-# Assembly version error when importing a Microsoft Dynamics 365 solution
+# Assembly version error when importing a Dynamics 365 solution
 
-This article provides a resolution for the assembly version error that occurs when you import a solution in Microsoft Dynamics 365 (online).
+This article provides a resolution for an assembly version error that might occur when you import a solution in Microsoft Dynamics 365.
 
 _Applies to:_ &nbsp; Microsoft Dynamics 365  
 _Original KB number:_ &nbsp; 4345239
 
 ## Symptoms
 
-When you attempt to import a solution in Microsoft Dynamics 365 (online), the import fails with the following message:
+When you try to import a solution in Dynamics 365, the import might fail with the following error message:
 
 > The import of solution: [solution name] failed
 
-If you select **Download Log File**, you see details similar to the following message:
+If you select **Download Log File**, you might see a message like this:
 
-> An error occurred while importing a Solution. : Microsoft.Crm.CrmException: This plugin assembly uses version {0} of the .NET Framework. At this time Microsoft Dynamics 365 requires version {1} of the .NET Framework for plugin assemblies. Rebuild this assembly using .NET Framework version {1} and try again.    at  Microsoft.Crm.ObjectModel.TargetFrameworkVersionValidator.ValidateInternal()    at Microsoft.Crm.ObjectModel.PluginValidatorBase.Validate()    at  Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal\`1.ValidateAssemblyMetadata(ExecutionContext context, IBusinessEntity pluginAssembly, CrmPluginAssemblyMetadata assemblyMetadata)    at  Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal\`1.VerifyRegistrationAbility(IBusinessEntity pluginAssembly, Boolean createCall, ExecutionContext context, CrmPluginAssemblyMetadata assemblyMetadata)    at  Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal\`1.ValidateOperation(String operationName, IBusinessEntity entity, ExecutionContext context)    at  Microsoft.Crm.ObjectModel.SdkEntityServiceBase.CreateInternal(IBusinessEntity entity, ExecutionContext context, Boolean verifyAction)    at  Microsoft.Crm.Tools.ImportExportPublish.ImportPluginAssemblyHandler.CreateOrGetExistingPluginAssembly(PluginAssembly pluginAssembly, String fileContent, BusinessProcessObject bpoService, Boolean skipValidation, BusinessEntityCollection& existingPluginAssemblies)    at  Microsoft.Crm.Tools.ImportExportPublish.ImportPluginAssemblyHandler.ImportItem()
+```output
+An error occurred while importing a Solution. : Microsoft.Crm.CrmException: 
+This plugin assembly uses version {0} of the .NET Framework. 
+At this time Microsoft Dynamics 365 requires version {1} of the .NET Framework for plugin assemblies. Rebuild this assembly using .NET Framework version {1} and try again.    at  
+Microsoft.Crm.ObjectModel.TargetFrameworkVersionValidator.ValidateInternal()    at Microsoft.Crm.ObjectModel.PluginValidatorBase.Validate()    at  
+Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.ValidateAssemblyMetadata(ExecutionContext context, IBusinessEntity pluginAssembly, CrmPluginAssemblyMetadata assemblyMetadata)    at  
+Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.VerifyRegistrationAbility(IBusinessEntity pluginAssembly, Boolean createCall, ExecutionContext context, CrmPluginAssemblyMetadata assemblyMetadata)    at  
+Microsoft.Crm.ObjectModel.PluginAssemblyServiceInternal`1.ValidateOperation(String operationName, IBusinessEntity entity, ExecutionContext context)    at  
+Microsoft.Crm.ObjectModel.SdkEntityServiceBase.CreateInternal(IBusinessEntity entity, ExecutionContext context, Boolean verifyAction)    at  
+Microsoft.Crm.Tools.ImportExportPublish.ImportPluginAssemblyHandler.CreateOrGetExistingPluginAssembly(PluginAssembly pluginAssembly, String fileContent, BusinessProcessObject bpoService, Boolean skipValidation, BusinessEntityCollection& existingPluginAssemblies)    at  
+Microsoft.Crm.Tools.ImportExportPublish.ImportPluginAssemblyHandler.ImportItem()
+```
 
-In the example provided above, {0} is a version that is too high and {1} is the currently supported version. You may also see a reference to error code **8004420B**, **8004418B**, or **-2147204725**.
+In the preceding log, `{0}` represents the .NET Framework version used in the plug-in assembly, which is incompatible, and `{1}` represents the .NET Framework version required by Dynamics 365. Additionally, you might receive error codes such as **8004420B**, **8004418B**, or **-2147204725**.
 
 ## Cause
 
-This error can occur if you are trying to import a solution that includes a plugin assembly compiled on a version of the .NET Framework that is not currently supported by Microsoft Dynamics 365 (online).
+This error occurs when the imported solution includes a plug-in assembly compiled using a version of the .NET Framework that's not currently supported by Dynamics 365.
 
 ## Resolution
 
-Recompile the assembly using the mentioned version of the .NET Framework.
+To solve this issue, recompile the plug-in assembly using the specified version of the .NET Framework, and then reimport the solution.
 
-For information about the .NET Framework version currently supported by Microsoft Dynamics 365 (online), see [Supported extensions for Microsoft Dynamics 365](/previous-versions/dynamicscrm-2016/developers-guide/gg328350(v=crm.8)).
+## More information
+
+- For information about the .NET Framework versions currently supported by Dynamics 365, see [Support for .NET Framework versions](/power-apps/developer/data-platform/supported-customizations#support-for-net-framework-versions).
+- For guidelines on configuring and building assemblies for Microsoft Dataverse plug-ins, see [Build and package plug-in code](/power-apps/developer/data-platform/build-and-package).
diff --git a/support/power-platform/dataverse/working-with-solutions/schemaType-mismatch-on-solution-import.md b/support/power-platform/dataverse/working-with-solutions/schemaType-mismatch-on-solution-import.md
@@ -0,0 +1,35 @@
+---
+title: Environment Schema Type Mismatch During Solution Import in Power Apps
+description: Works around a warning about environment schema type mismatch that occurs when you import a solution in the target environment in Microsoft Power Apps.
+ms.reviewer: matp
+ms.date: 03/20/2025
+author: swatimadhukargit
+ms.author: swatim
+ms.custom: sap:Working with Solutions\Environment schema type mistamch during solution import
+---
+# Environment schema type mismatch warning during solution import
+
+This article provides a workaround for the warning that might occur when the source environment's [schema type](/power-apps/developer/data-platform/webapi/reference/organizationdetail#remarks) is higher than the target environment's schema type. This issue occurs when you [import a solution](/powerapps/maker/data-platform/import-update-export-solutions) in Microsoft Power Platform. Although you can still proceed with the solution import if there are no other errors, this warning helps guide you to avoid missing components due to schema type mismatch for future imports.
+
+_Applies to:_ &nbsp; Power Platform, Solutions
+
+## Symptoms
+
+When you try to import a solution in [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), you might receive the following warning:
+
+> This solution was exported from a [source environment schema type] environment, which has more components than the current [target environment schema type] environment. When you import, some components might be missing.
+
+## Cause
+
+This issue might occur when the source environment, from which the solution is exported, has a higher schema type than the target environment. The higher schema type might include more components than the lower schema type of the target environment. Consequently, the solution might depend on components available in the source environment but absent in the target environment, leading to missing dependencies.
+
+For example, a `Full` schema type has more components than a `Standard` schema type, and a `Standard` schema type has more components than a `Core` schema type.
+
+This warning ensures that you understand the drawbacks of having source and development environments with different schema types.
+
+## Workaround
+
+To work around this issue, ensure the schema type of the source environment is either the same or lower than that of the target environment. If the source environment's schema type is higher, consider adjusting it to match the target environment's schema type.
+
+> [!NOTE]
+> The warning doesn't necessarily mean there are missing dependencies during solution import. Instead, this warning serves as a best practice guideline to properly configure source and target environments, reducing the risk of future missing dependencies.
diff --git a/support/power-platform/dataverse/working-with-solutions/troubleshoot-solution-import-errors-in-dynamics-365.md b/support/power-platform/dataverse/working-with-solutions/troubleshoot-solution-import-errors-in-dynamics-365.md
diff --git a/support/power-platform/dataverse/working-with-solutions/version-mismatch-on-solution-import.md b/support/power-platform/dataverse/working-with-solutions/version-mismatch-on-solution-import.md
diff --git a/support/sql/releases/sqlserver-2017/cumulativeupdate30.md b/support/sql/releases/sqlserver-2017/cumulativeupdate30.md

Original file line number	Diff line number	Diff line change
`@@ -6299,6 +6299,10 @@`
`6299`	`6299`	`{`
`6300`	`6300`	`"source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",`
`6301`	`6301`	`"redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"`
	`6302`	`+ },`
	`6303`	`+ {`
	`6304`	`+ "source_path": "azure-kubernetes/create-upgrade-delete/error-using-feature-requiring-virtual-machine-scale-set.md",`
	`6305`	`+ "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes"`
`6302`	`6306`	`}`
`6303`	`6307`	`]`
`6304`	`6308`	`}`