Merge pull request #8827 from MicrosoftDocs/main

Auto push to live 2025-04-29 02:31:47

Author: Deland-Han

.openpublishing.redirection.json

@@ -13683,6 +13683,10 @@
     {
       "source_path": "support/windows-server/active-directory/dcs-cannot-be-located-high-rate-outbound-sessions.md",
       "redirect_url": "/troubleshoot/windows-server/user-profiles-and-logon/dcs-cannot-be-located-high-rate-outbound-sessions"
-    }
+    },
+    {
+    "source_path": "support/power-platform/power-automate/desktop-flows/troubleshoot-excel-errors.md",
+    "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
+  }
   ]
 }

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-installation.md

@@ -175,6 +175,38 @@ When registering a server using *ServerRegistration.exe*, some resource groups a
 
 This issue occurs due to a known issue that has been fixed in File Sync Agent v19.1. To resolve this issue, install the latest version of the agent.
 
+
+
+**Server Registration displays the following message: "System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=..."**
+
+This error occurs when the required version of the .NET Framework is missing on the server. Azure File Sync's server registration requires **.NET Framework 4.7.2. or higher** to function properly. 
+
+To resolve the issue:
+1. Downland and install .NET Framework 4.7.2. or higher.
+2. Restart the server after installation.
+3. Retry the server registration using the Server Registration UI or PowerShell.
+
+
+
+**Server registration fails with error: operation returned an invalid status code 'Unauthorized'**
+
+During server registration, if you encounter the following error:
+`Operation returned an invalid status code 'Unauthorized'`
+
+This issue occurs when authentication with Azure fails during the registration process. To resolve this issue: 
+
+Manually register the server using PowerShell:
+
+```powershell
+Connect-AzAccount -Subscription "<your-subscription-guid>" -Tenant "<your-tenant-guid>"
+Register-AzStorageSyncServer -ResourceGroupName "<your-resource-group-name>" -StorageSyncServiceName "<your-storage-sync-service-name>"
+```
+
+Replace the placeholder values with your subscription ID, tenant ID, resource group name, and Storage Sync Service name.
+
+After completing the manual registration, verify that the server appears under Registered servers in the Azure portal.
+
+
 <a id="server-already-registered"></a>**Server Registration displays the following message: "This server is already registered"**
 
 :::image type="content" source="media/file-sync-troubleshoot-installation/server-already-registered-error.png" alt-text="Screenshot that shows the Server Registration dialog box with the 'server is already registered' error message.":::

support/power-platform/power-automate/desktop-flows/cannot-connect-to-ibm-personal-communications.md

@@ -0,0 +1,43 @@
+---
+title: Unable to Connect to IBM Personal Communications Session
+description: Solves an issue where you can't connect to an IBM Personal Communications session using the Open terminal session action with the HLLAPI provider.
+ms.custom: sap:Desktop flows
+ms.date: 04/29/2025
+ms.author: nimoutzo 
+author: NikosMoutzourakis
+---
+# Can't connect to an IBM Personal Communications session
+
+This article provides a resolution for an issue where you can't connect to an IBM Personal Communications session using the [Open terminal session](/power-automate/desktop-flows/actions-reference/terminalemulation) action with the HLLAPI provider in Power Automate for desktop.
+
+_Applies to:_   Power Automate for desktop
+
+## Symptoms
+
+When you try to use the **Open terminal session** action with the HLLAPI provider to connect to the IBM Personal Communications terminal emulator, you might receive the following error message:
+
+```output
+Exception of type 'Microsoft.Flow.RPA.Desktop.Modules.TerminalEmulation.Common.TerminalEmulationActionException' was thrown.: Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Error communicating with the emulator ---> Microsoft.Flow.RPA.Desktop.Modules.TerminalEmulation.Common.TerminalEmulationActionException: Exception of type 'Microsoft.Flow.RPA.Desktop.Modules.TerminalEmulation.Common.TerminalEmulationActionException' was thrown.
+   at Microsoft.Flow.RPA.Desktop.BridgeToHLLAPI.HLLAPIActionsImpl.<>c__DisplayClass16_0.<Open>b__0()
+   --- End of inner exception stack trace ---
+   at Microsoft.Flow.RPA.Desktop.Modules.TerminalEmulation.Actions.OpenTerminalSession.Execute(ActionContext context)
+   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)
+```
+
+This issue can occur in the following desktop flow modes:
+
+- Unattended
+- Attended
+- Console/Designer
+
+## Cause
+
+The IBM Personal Communications terminal emulator requires access to HLLAPI DLLs for proper operation. However, the HLLAPI implementation in IBM Personal Communications version 14 (32-bit) might result in the error.
+
+## Resolution
+
+To resolve this issue, download and install the [64-bit version of IBM Personal Communications](https://www.ibm.com/docs/personal-communications) that includes the required HLLAPI DLLs. Ensure that you select the appropriate DLL file in the **Open terminal session** action.
+
+For more information, see [Terminal emulation actions](/power-automate/desktop-flows/actions-reference/terminalemulation).
+
+[!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]

…sktop-flows/troubleshoot-excel-errors.md …ation/excel/troubleshoot-excel-errors.mdsupport/power-platform/power-automate/desktop-flows/troubleshoot-excel-errors.md renamed to support/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors.md support/power-platform/power-automate/desktop-flows/troubleshoot-excel-errors.md renamed to support/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors.md

@@ -4,7 +4,7 @@ description: Provides mitigation steps for errors generated by Excel actions in
 ms.author: iomavrid
 author: yiannismavridis
 ms.date: 05/08/2023
-ms.custom: sap:Desktop flows\Power Automate for desktop errors
+ms.custom: sap:Desktop flows\Office automation
 ---
 # Errors when running desktop flows, including Excel actions
 
@@ -17,11 +17,11 @@ This article provides mitigation steps for errors generated by Excel actions in
 |System.ArgumentNullException: Value cannot be null.</br>Parameter name: type|When Excel fails to open with this error, make sure that Excel is installed, licensed, and properly configured on the computer. You can also try to repair your Office installation.|
 |System.IO.FileNotFoundException: documentPathSafe|The Excel file doesn't exist, or its name or path isn't spelled correctly. Also, the file path shouldn't contain more than 255 characters.|
 |System.Runtime.InteropServices.COMException: Open method of Workbooks class failed|The Excel file path shouldn't contain more than 255 characters.|
-|System.Runtime.InteropServices.COMException: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)|When an Excel file fails to open with this error, try to enable the **Nest under a New Excel process** option under the **Advanced** group of parameters. The existing Excel process might have been terminated before opening this Excel file.|
-|Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Excel document '<Excel_file_name>' not found.|Make sure that the Excel file has been opened and its name or path has been spelled correctly.|
-|System.Runtime.InteropServices.COMException: Unknown name. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME))|Make sure that the target Excel file hasn't been opened in Protected View.|
+|System.Runtime.InteropServices.COMException: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)|When an Excel file fails to open with this error, try to enable the **Nest under a New Excel process** option under the **Advanced** group of parameters. The existing Excel process might be terminated before opening this Excel file.|
+|Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Excel document '<Excel_file_name>' not found.|Make sure that the Excel file is opened and its name or path is spelled correctly.|
+|System.Runtime.InteropServices.COMException: Unknown name. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME))|Make sure that the target Excel file is opened in Protected View.|
 |System.Runtime.InteropServices.COMException: Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))|The target Excel file shouldn't be edited (for example, a cell is actively being edited at the time of the action run) or blocked by a pop-up dialog when the corresponding Excel action runs.|
-|System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800A03EC|When using an Excel action where a column, a row, or both need to be specified, the column index should be greater than zero and less than 16,385, or the column letter should belong to the range between A and XFD. Furthermore, the row index should be greater than zero and less than 1,048,577.|
+|System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800A03EC|When you use an Excel action where a column, a row, or both need to be specified, the column index should be greater than zero and less than 16,385, or the column letter should belong to the range between A and XFD. Furthermore, the row index should be greater than zero and less than 1,048,577.|
 |System.Runtime.InteropServices.COMException: The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))|The Excel instance should be open and active, so the Excel file shouldn't be closed manually or through the "Close Excel" action before the rest of the Excel actions take place.|
 
 The following exceptions come with embedded mitigation steps in their text.
@@ -30,6 +30,6 @@ The following exceptions come with embedded mitigation steps in their text.
 |---|
 |System.Runtime.InteropServices.COMException: The cell or chart you're trying to change is on a protected sheet. To make a change, unprotect the sheet. You might be requested to enter a password.|
 |System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.</br>Parameter name: The column number must be greater than one or less than 16384.|
-|System.Runtime.InteropServices.COMException: The file name is too long. Rename the file with less than 207 characters.|
+|System.Runtime.InteropServices.COMException: The file name is too long. Rename the file with fewer than 207 characters.|
 |System.Runtime.InteropServices.COMException: The password you supplied isn't correct. Verify that the <kbd>Caps Lock</kbd> key is off and be sure to use the correct capitalization.|
 |System.Runtime.InteropServices.COMException: Excel cannot open the file '<Excel_file_name>' because the file format or file extension is not valid. Verify that the file hasn't been corrupted and that the file extension matches the format of the file.|

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md

@@ -0,0 +1,62 @@
+---
+title: The Remote Desktop Wasn't Found Error
+description: Solves an error that occurs when you use Remote Desktop Protocol (RDP) or Citrix automation in Microsoft Power Automate.
+ms.reviewer: amitrou
+ms.author: iopanag
+author: iopanag
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.date: 04/29/2025
+---
+# A desktop flow fails with the "The remote desktop wasn't found" error
+
+This article helps you resolve an issue where a flow fails with the "The remote desktop wasn't found" error when using Microsoft Remote Desktop Protocol (RDP) or Citrix automation in Microsoft Power Automate.
+
+## Symptoms
+
+A flow using [Remote Desktop Protocol (RDP) or Citrix automation](/power-automate/desktop-flows/virtual-desktops) that previously ran successfully might start failing with the following error:
+
+> The remote desktop wasn't found.
+
+This issue is more common in Citrix Virtual Apps.
+
+## Cause 1
+
+The names of the RDP window, Citrix Desktop, or Citrix Virtual Apps might have changed since the original [UI elements](/power-automate/desktop-flows/virtual-desktops#distinguish-ui-elements-captured-on-virtual-desktops) were captured. Tracking these elements with the old name can fail.
+
+### Resolution
+
+To solve this issue:
+
+1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
+2. Locate the desktop element causing the issue in the [UI elements](/power-automate/desktop-flows/ui-elements#ui-elements) pane in the flow designer. Double-click it to open the selector editor.
+
+   :::image type="content" source="media/error-remote-desktop-not-found/control-repo-desktop.png" alt-text="Screenshot of the Power Automate elements section with a Citrix desktop element highlighted.":::
+
+3. Select the **Repair** button and capture the new desktop or app. Review the suggested changes and accept them. For more information, see [Repair a selector](/power-automate/desktop-flows/repair-selector).
+
+   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-repair.png" alt-text="Screenshot of the Power Automate selector builder window with the Repair button highlighted.":::
+
+4. After accepting the changes, select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).
+
+5. (Optional) Use the **New** button to add more fallback selectors for the desktop.
+
+## Cause 2
+
+When you use Citrix Virtual Apps with certain applications, especially when interacting with combo box lists, an incorrect target desktop selector might be created using an ordinal value (for example, **eq**) instead of a more robust selection method.
+
+### Resolution
+
+To solve this issue:
+
+1. Ensure the affected RDP window, Citrix Desktop, or Citrix Virtual Apps is active.
+2. Locate the desktop element causing the issue in the [UI elements](/power-automate/desktop-flows/ui-elements#ui-elements) pane in the flow designer. Double-click it to open the selector editor.
+
+   :::image type="content" source="media/error-remote-desktop-not-found/control-repo-desktop.png" alt-text="Screenshot of the Power Automate elements section with a Citrix app element highlighted.":::
+
+3. Check if the selector is using an ordinal value (the **eq** is selected.) If it is, clear the value and save the change.
+
+   :::image type="content" source="media/error-remote-desktop-not-found/rdp-selector-builder-ordinal.png" alt-text="Screenshot of the Power Automate selector builder window with an ordinal attribute checkbox cleared.":::
+
+4. Select **Test** to verify the new selector. For more information, see [Test a selector](/power-automate/desktop-flows/test-selectors).
+
+[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/interactions-with-rdp-citrix-takes-long-and-fails.md

@@ -0,0 +1,53 @@
+---
+title: Operation Takes a Long Time and Fails During Runtime
+description: Solves an issue where interactions with Remote Desktop Protocol (RDP) or Citrix applications take a long time and fail during runtime in Power Automate.
+ms.reviewer: amitrou
+ms.author: iopanag
+author: iopanag
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.date: 04/29/2025
+---
+# Interactions with RDP or Citrix applications take a long time and fail
+
+This article provides guidance to resolve issues where operations take a long time to run and eventually time out. It describes the settings that can be modified to accommodate longer timeout periods.
+
+## Symptoms
+
+When you try to highlight, capture, test a [UI element](/power-automate/desktop-flows/ui-elements), or interact with UI elements during runtime in Power Automate, the operation might take a significant amount of time and ultimately fail. This issue occurs when interacting with Microsoft Remote Desktop Protocol (RDP) or Citrix applications.
+
+## Cause
+
+The default time-out settings in Power Automate might be insufficient. The time-outs might need to be adjusted to accommodate the increased time required for communication between the local and remote environments.
+
+## Resolution
+
+To resolve the issue, modify the following keys as needed. For more information about configuring the values, see [time-out configuration for UI and browser automation](/power-automate/desktop-flows/how-to/ui-automation-change-timeout-cofiguration).
+
+- **Java.Bridge.Client.ReadWriteTimeout**
+
+  - Use this setting if the target application is Java-based.
+  - This time-out increases the waiting time for responses from Java applications.
+  - For remote Java applications (for example, on RDP or Citrix), configure this time-out on the remote machine.
+
+- **BrowserNativeMessageHost.MessageTimeout** and **WebExtensionsMessageProxy.SendTimeout**
+  - Use these settings if web automation is used.
+  - These time-outs increase the maximum waiting time for webpages to respond.
+  - For webpages in remote environments (for example, RDP or Citrix), configure these time-outs on the remote machine.
+
+- **RDP.Client.CallTimeOut**
+  - Use this setting when interacting with applications or webpages on a remote machine via RDP or Citrix.
+  - This time-out increases the maximum waiting time for responses from remote applications or webpages.
+
+## Other time-out settings
+
+Depending on whether the issue occurs during design time or runtime, the following time-out settings might need to be configured:
+
+- For design-time issues (for example, failing to capture an element from the designer), adjust the following setting:
+
+  - **AutomationServerEndpoint.DesignTime.CallTimeout**: This setting increases the time the Power Automate Designer waits for a response.
+
+- For runtime issues (for example, failing during the execution of a flow), adjust the following setting:
+
+  - **AutomationServerEndpoint.Runtime.CallTimeout**: This setting increases the maximum waiting time during runtime for an action to be executed.
+
+[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]