Merge pull request #8352 from MicrosoftDocs/main

Auto push to live 2025-03-02 18:00:02

Author: Deland-Han

support/azure/azure-kubernetes/create-upgrade-delete/aks-increased-memory-usage-cgroup-v2.md

@@ -1,8 +1,8 @@
 ---
 title: Increased memory usage reported in Kubernetes 1.25 or later versions
 description: Resolve an increase in memory usage that's reported after you upgrade an Azure Kubernetes Service (AKS) cluster to Kubernetes 1.25.x.
-ms.date: 07/13/2023
-editor: v-jsitser
+ms.date: 03/03/2025
+editor: momajed
 ms.reviewer: aritraghosh, cssakscic, v-leedennis
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -23,23 +23,49 @@ You experience one or more of the following symptoms:
 
 ## Cause
 
-This increase is caused by a change in memory accounting within version 2 of the Linux control group (cgroup) API. [Cgroup v2](https://kubernetes.io/docs/concepts/architecture/cgroups/) is now the default cgroup version for Kubernetes 1.25 on AKS.
+This increase is caused by a change in memory accounting within version 2 of the Linux control group (`cgroup`) API. [Cgroup v2](https://kubernetes.io/docs/concepts/architecture/cgroups/) is now the default `cgroup` version for Kubernetes 1.25 on AKS.
 
 > [!NOTE]  
-> This issue is distinct from the memory saturation in nodes that's caused by applications or frameworks that aren't aware of cgroup v2. For more information, see [Memory saturation occurs in pods after cluster upgrade to Kubernetes 1.25](./aks-memory-saturation-after-upgrade.md).
+> This issue is distinct from the memory saturation in nodes that's caused by applications or frameworks that aren't aware of `cgroup` v2. For more information, see [Memory saturation occurs in pods after cluster upgrade to Kubernetes 1.25](./aks-memory-saturation-after-upgrade.md).
 
 ## Solution
 
 - If you observe frequent memory pressure on the nodes, upgrade your subscription to increase the amount of memory that's available to your virtual machines (VMs).
 
 - If you see a higher eviction rate on the pods, [use higher limits and requests for pods](/azure/aks/developer-best-practices-resource-management#define-pod-resource-requests-and-limits).
 
+- `cgroup` v2 uses a different API than `cgroup` v1. If there are any applications that directly access the `cgroup` file system, update them to later versions that support `cgroup` v2. For example:
+
+  - **Third-party monitoring and security agents**:
+
+     Some monitoring and security agents depend on the `cgroup` file system. Update these agents to versions that support `cgroup` v2.
+
+  - **Java applications**:
+
+     Use versions that fully support `cgroup` v2:
+    - OpenJDK/HotSpot: `jdk8u372`, `11.0.16`, `15`, and later versions.
+    - IBM Semeru Runtimes: `8.0.382.0`, `11.0.20.0`, `17.0.8.0`, and later versions.
+    - IBM Java: `8.0.8.6` and later versions.
+
+  - **uber-go/automaxprocs**:  
+    If you're using the `uber-go/automaxprocs` package, ensure the version is `v1.5.1` or later.
+
+- An alternative temporary solution is to revert the `cgroup` version on your nodes by using the DaemonSet. For more information, see [Revert to cgroup v1 DaemonSet](https://github.com/Azure/AKS/blob/master/examples/cgroups/revert-cgroup-v1.yaml).
+
+> [!IMPORTANT]
+> - Use the DaemonSet cautiously. Test it in a lower environment before applying to production to ensure compatibility and prevent disruptions.
+> - By default, the DaemonSet applies to all nodes in the cluster and reboots them to implement the `cgroup` change.  
+> - To control how the DaemonSet is applied, configure a `nodeSelector` to target specific nodes.
+
+
 > [!NOTE]  
 > If you experience only an increase in memory use without any of the other symptoms that are mentioned in the "Symptoms" section, you don't have to take any action.
 
 ## Status
 
-We're actively working with the Kubernetes community to fix the underlying issue, and we'll keep you updated on our progress. We also plan to change the eviction thresholds or [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
+We're actively working with the Kubernetes community to resolve the underlying issue. Progress on this effort can be tracked at [Azure/AKS Issue #3443](https://github.com/kubernetes/kubernetes/issues/118916). 
+
+As part of the resolution, we plan to adjust the eviction thresholds or update [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
 
 ## Reference
 

support/power-platform/power-automate/desktop-flows/browser-automation/machine-runtime-msix-errors.md

@@ -0,0 +1,36 @@
+---
+title: Web Automation Fails When Machine Runtime and MSIX Versions Are Different
+description: Solves a web automation error that occurs when the machine runtime application and the Power Automate for desktop store installation (MSIX) versions are different.
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.reviewer: amitrou
+ms.author: nimoutzo
+author: NikosMoutzourakis
+ms.date: 03/03/2025
+---
+# Web automation action fails when the machine runtime and Microsoft Store (MSIX) versions are different
+
+This article provides a workaround for the "Negotiation failed" error that occurs when a web automation action fails to run in Power Automate for desktop.
+
+## Symptoms
+
+Consider the following scenario:
+
+- You installed [Power Automate for desktop from Microsoft Store (MSIX)](/power-automate/desktop-flows/install#install-power-automate-from-microsoft-store).
+- You installed the machine runtime using an older version of the [MSI installer](/power-automate/desktop-flows/install#install-power-automate-using-the-msi-installer).
+- You created a flow in Power Automate for desktop to automate a web page with an [extension-based browser](/power-automate/desktop-flows/install-browser-extensions) and ran the flow from the cloud.
+
+In this scenario, the web automation action fails with the following error:
+
+> Negotiation failed
+
+This issue applies when running any web automation action under the [Browser Automation group](/power-automate/desktop-flows/automation-web) in unattended or attended mode.
+
+## Cause
+
+When the Power Automate for desktop MSIX installation is a different version than the machine runtime application, the Message Host (from the MSIX installation) running from the browser is a different version than the machine runtime expects. This discrepancy causes the flow to fail with a "Negotiation failed" error.
+
+## Workaround
+
+We don't recommend having both the MSI and MSIX versions of Power Automate on the same machine. If you do this, uninstall one version or ensure that the machine runtime application and the MSIX installation versions are the same.
+
+For more information on Power Automate for desktop versions, see [Released versions for Power Automate for desktop](/power-platform/released-versions/power-automate-desktop).

support/power-platform/power-automate/desktop-flows/office-automation/excel/launch-excel-action-failures.md

@@ -0,0 +1,91 @@
+---
+title: Launch Excel Action Failures
+description: Solves errors related to the Launch Excel action in Power Automate for desktop.
+ms.reviewer: amitrou
+ms.author: nimoutzo
+author: NikosMoutzourakis
+ms.custom: sap:Desktop flows\Office automation
+ms.date: 03/03/2025
+---
+# Error occurs when opening an Excel file in Power Automate for desktop
+
+This article helps solve errors that occur when you try to open a blank or existing Excel file in Power Automate for desktop.
+
+## "Exception from HRESULT: 0x800xxxxx" error
+
+> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800xxxxx
+
+### Cause
+
+This error can occur if:
+
+- Office apps (or just Excel) aren't properly installed.
+- Power Automate for desktop isn't properly installed.
+- The Excel file is synchronized with OneDrive.
+
+### Resolution
+
+- Manually [uninstall](/power-automate/desktop-flows/install#uninstall-power-automate) and [reinstall](/power-automate/desktop-flows/install) Power Automate for desktop. If it doesn't work, ensure you have Excel properly installed.
+- To work around the error caused by the synchronization with OneDrive, see [Using Excel files synchronized through OneDrive or SharePoint](/power-automate/desktop-flows/actions-reference/excel#using-excel-files-synchronized-through-onedrive-or-sharepoint).
+
+## "Could not load file or assembly or one of its dependencies" error
+
+> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Office.Interop.Excel' or one of its dependencies. The system cannot find the file specified.
+
+### Cause
+
+The Excel application isn't installed on the machine.
+
+### Resolution
+
+Ensure you have Excel installed on the machine.
+
+## "Access to the path 'C:\YourPath\YourFile.xlsx' is denied" error
+
+> System.UnauthorizedAccessException: Access to the path 'C:\YourPath\YourFile.xlsx' is denied.
+
+### Cause
+
+The document is located in a restricted file path, or Power Automate for desktop doesn't have permission to open and access the document.
+
+### Resolution
+
+Move the file to a directory where Power Automate for desktop has access.
+
+## "The process cannot access the file 'C:\YourPath\YourFile.xlsx'" error
+
+> System.IO.IOException: The process cannot access the file 'C:\YourPath\YourFile.xlsx' because it is being used by another process.
+
+### Cause
+
+The Excel application is locked, and no other process can access it.
+
+### Resolution
+
+Terminate all opened Excel processes and restart Power Automate for desktop.
+
+## "80040154 Class not registered" error
+
+> System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {*ID*} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
+
+### Cause
+
+This issue can occur if you're using an older version of Excel, such as Excel 2013 or earlier.
+
+### Resolution
+
+Ensure you have Excel 2013 or a later version installed on your machine.
+
+## "System.OutOfMemoryException: Out of memory" error
+
+### Cause
+
+The Excel application crashes due to insufficient memory or high memory utilization caused by a specific extension running on Excel.
+
+### Resolution
+
+Terminate all opened Excel applications and try again.
+
+## More information
+
+[Excel actions in Power Automate](/power-automate/desktop-flows/actions-reference/excel)

support/power-platform/power-automate/desktop-flows/office-automation/outlook/media/retrieve-emails-filtering/loop-emails-filter.png

@@ -0,0 +1,47 @@
+---
+title: Retrieve Email Messages from Outlook Doesn't Work
+description: Solves an issue related to the Retrieve email messages from Outlook action in Microsoft Power Automate.
+ms.custom: sap:Desktop flows\Office automation
+ms.reviewer: amitrou
+ms.author: nimoutzo
+author: NikosMoutzourakis
+ms.date: 03/03/2025
+---
+# The "Retrieve email messages from Outlook" action doesn't work as expected
+
+This article solves an issue where the [Retrieve email messages from Outlook](/power-automate/desktop-flows/actions-reference/outlook) action doesn't return any results in Microsoft Power Automate.
+
+## Symptoms
+
+When you use the **From contains** filter in the **Retrieve email messages from Outlook** action in Power Automate, no results are returned.
+
+## Cause
+
+In some cases, the email addresses of Exchange users are in an X500 format (for example, /o\=<organization-name\>/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=\<mailbox\>) instead of the standard mail format (`[email protected]`). When you use the **Retrieve email messages from Outlook** action in Power Automate, the **From contains** filter might not work if the filtering is performed with the X500 format email.
+
+If that's the case, use the X500 format email in the **From contains** filter.
+
+You can retrieve the X500 format email using the Exchange PowerShell cmdlet:
+
+```powershell
+Get-Mailbox -Identity username | ft legacyExchangeDN.
+```
+
+Alternatively, you can look in `%LocalAppData%\Microsoft\Outlook` for an XML file that contains a section called **LegacyDn**.
+
+## Workaround
+
+To work around this issue:
+
+- Use other actions for email operations, such as:
+
+  - [Exchange Server actions](/power-automate/desktop-flows/actions-reference/exchange).
+  - [Microsoft 365 Outlook actions](/connectors/office365/#get-emails-(v3)).
+  
+- Perform the filtering by using a **For each** loop to iterate through the returned messages. For example:
+
+  :::image type="content" source="media/retrieve-emails-filtering/loop-emails-filter.png" alt-text="Screenshot of an example of retrieving emails using a For each loop." lightbox="media/retrieve-emails-filtering/loop-emails-filter.png":::
+
+## More information
+
+[Outlook actions](/power-automate/desktop-flows/actions-reference/outlook)

support/power-platform/power-automate/desktop-flows/office-automation/outlook/retrieve-emails-filtering.md

@@ -0,0 +1,32 @@
+---
+title: The Server Threw an Exception When Opening SAP
+description: Solves an error that occurs when a user tries to open the SAP application automated by Power Automate for desktop.
+ms.reviewer: amitrou
+ms.author: nimoutzo
+author: NikosMoutzourakis
+ms.custom: sap:Desktop flows\SAP automation
+ms.date: 03/03/2025
+---
+# The server threw an exception when opening SAP
+
+This article helps you resolve an error that occurs when a user tries to open the SAP application automated by Power Automate for desktop.
+
+## Symptoms
+
+When a user tries to open the SAP application, they receive the following error message:
+
+> The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)): Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Action failed. ---> System.Runtime.InteropServices.COMException: The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
+
+## Cause
+
+This issue can occur if the user doesn't have scripting permissions to use the SAP actions.
+
+## Resolution
+
+To solve the issue, [check and enable the SAP scripting](/power-automate/guidance/rpa-sap-playbook/prerequisites#sap-gui-scripting-configuration) for the user who needs to use the SAP actions.
+
+## More information
+
+[Introduction to SAP GUI–based RPA in Power Automate Desktop](/power-automate/guidance/rpa-sap-playbook/introduction)
+
+[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

support/power-platform/power-automate/desktop-flows/sap-automation/scripting-permissions-launch-sap.md

@@ -0,0 +1,75 @@
+---
+title: No Element Highlighted or Error When Hovering over UI or Web Element
+description: Solves an issue that occurs when you hover the mouse cursor over a UI or web element of an application or webpage in Power Automate for desktop.
+ms.reviewer: amitrou
+ms.author: nimoutzo
+author: NikosMoutzourakis
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.date: 03/03/2025
+---
+# UI element isn't highlighted or an error occurs when hovering over a UI or web element
+
+This article helps you resolve issues you might encounter when using the UI element picker in virtual desktops, such as Citrix or Remote Desktop Protocol (RDP) environments.
+
+## Symptoms
+
+When you hover the mouse cursor over a UI or web element of an application or webpage inside a Citrix or RDP window with the [UI element picker](/power-automate/desktop-flows/ui-elements#ui-elements-types) enabled, you might see:
+
+1. The element isn't highlighted.
+2. An error message about enabling the [Power Automate agent for virtual desktops](/power-automate/desktop-flows/virtual-desktops#install-the-power-automate-agent-for-virtual-desktops).
+
+   > Enable UI automation in virtual desktop  
+   > To automate using UI elements on virtual desktops, ensure the Power Automate agent for virtual desktops is installed and running on the remote machine.
+
+   :::image type="content" source="media/rdp-no-highlight/agent-not-running.png" alt-text="Screenshot of the Enable UI automation in virtual desktop error.":::
+
+## Cause
+
+The communication with the remote agent components doesn't work.
+
+## Resolution
+
+1. Ensure the Power Automate Citrix or RDP plugin is registered.
+
+   1. While the virtual desktop platform (Citrix Desktop, Citrix Virtual Apps, Remote Desktop app, or a remote desktop with Windows RDP communication) is active, run the [troubleshooter](/power-automate/desktop-flows/troubleshooter) by navigating to **Help** > **Troubleshooter** in Power Automate.
+
+      > [!TIP]
+      > The troubleshooter can be manually opened via the console and the flow designer, through the dedicated menu under **Help** > **Troubleshooter**. It can also be opened via the process file **PAD.Troubleshooter.exe**, which can be found in the installation folder of Power Automate for desktop.
+
+   1. Run **Troubleshoot UI/Web automation issues** to view the diagnostics for the communication. If an error appears in the Citrix or RDP section, expand it for more details and solutions.
+
+2. If the troubleshooter indicates that the remote agent isn't running, check if the agent is running in the Citrix or RDP session.
+
+   Check the tray icon for the agent icon when the virtual desktop platform is active. If the icon exists, hover over it to confirm it's still running. If it is, right-click the tray icon to open the menu and select **Status**. The agent's status and the reason for the error will be displayed.
+
+   :::image type="content" source="media/rdp-no-highlight/agent-disconnected-icon.png" alt-text="Screenshot of the agent icon showing the Power Automate agent for virtual desktops is disconnected.":::
+
+3. If the agent is confirmed not running and Citrix is in use, ensure that the agent is installed on every Citrix server.
+
+4. If the agent is running, check the following conditions based on the agent's tray icon status:
+
+   - **A device on the system is not functioning**: The Citrix plugin isn't loaded on the host system.
+
+     To troubleshoot the issue, run the [troubleshooter](/power-automate/desktop-flows/troubleshooter) while the virtual desktop platform is active and check for errors in the **UI Automation** section.
+
+   - **Citrix Virtual Channel policy enabled**: The **Virtual channel allow list** policy on Citrix is set to **Enabled** or **Default**.
+
+     The default setting for this policy is **Enabled** or **Default**. However, if this policy isn't disabled, the Power Automate agent can't communicate with Power Automate for desktop. To resolve communication issues, work with your Citrix administrator to set the policy to **Disabled** and ensure Citrix machines are restarted after applying the policy.
+
+   - **Citrix VDA version < 2407**: The **Virtual channel allow list** policy on Citrix is set to **Enabled** or **Default**.
+
+     The default setting for this policy is **Enabled** or **Default**. However, if this policy isn't disabled, the Power Automate agent can't communicate with Power Automate for desktop. To resolve communication issues, work with your Citrix administrator to set the policy to **Disabled** and ensure Citrix machines are restarted after applying the policy.
+
+   - **Citrix VDA Version >= 2407**: The older **Virtual channel allow list** policy can remain at **Default**, but a different policy must be set.
+
+     Set the **Virtual channel allow list for DVC** policy with the following values:
+
+      - `C:\Program Files (x86)\Power Automate agent for virtual desktops\PAD.RDP.ControlAgent.exe,Microsoft.Flow.RPA.Desktop.UIAutomation.RDP.DVC.Plugin,PAD\CONTROL`
+  
+      - `C:\Users\*\AppData\Local\Microsoft\Power Automate Desktop\RDP Automation Agents\*\PAD.RDP.AutomationAgent.exe,Microsoft.Flow.RPA.Desktop.UIAutomation.RDP.DVC.Plugin,PAD\UIA`
+
+      Ensure Citrix machines are restarted after applying the policy.
+
+## More information
+
+[Automate on virtual desktops](/power-automate/desktop-flows/virtual-desktops)