Skip to content

Commit d9f9221

Browse files
author
Simonx Xu
authored
Merge pull request #9379 from MicrosoftDocs/main
Auto push to live 2025-07-21 10:02:09
2 parents f2e83a9 + cd66f61 commit d9f9221

5 files changed

Lines changed: 57 additions & 115 deletions

File tree

.openpublishing.redirection.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13761,6 +13761,10 @@
1376113761
{
1376213762
"source_path": "support/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting.md",
1376313763
"redirect_url": "/troubleshoot/windows-client/performance/stop-code-error-troubleshooting"
13764+
},
13765+
{
13766+
"source_path": "support/power-platform/power-automate/desktop-flows/office-automation/excel/launch-excel-action-failures.md",
13767+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
1376413768
}
1376513769
]
1376613770
}

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

Lines changed: 14 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues that you might encounter with Azure File
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 07/16/2025
7+
ms.date: 07/21/2025
88
ms.author: kendownie
99
ms.custom: sap:File Sync
1010
---
@@ -113,30 +113,35 @@ After installing or upgrading the Azure File Sync agent (v18 or later), you migh
113113
These issues occur because the Azure File Sync agent has a dependency on a Windows security feature and updates for this security feature aren't installed.
114114

115115
To resolve this issue, verify your Windows Server has the following updates installed:
116+
116117
- Windows Server 2016 [Microsoft Update Catalog](https://catalog.update.microsoft.com/Search.aspx?q=cumulative%20windows%20server%202016) (latest cumulative update)
117118
- Windows Server 2019 [Microsoft Update Catalog](https://catalog.update.microsoft.com/Search.aspx?q=cumulative%20windows%20server%202019) (latest cumulative update)
118-
- Cumulative updates are released monthly. To deploy the latest update, users can either use Windows Update or manually download it from the [Microsoft Update Catalog](https://catalog.update.microsoft.com). If installing manually, users should review the associated KB article to ensure all prerequisites are met.​ ​​If the Windows Updates aren't installed prior to installing the Azure File Sync agent, the Storage Sync Agent service (FileSyncSvc) will fail to start.
119-
120-
## Auto Update not upgrading ‘to be expired’ or expired Azure File Sync Agent
119+
120+
Cumulative updates are released monthly. To deploy the latest update, you can use Windows Update or download it from the [Microsoft Update Catalog](https://catalog.update.microsoft.com). Before manual installation, review the associated Knowledge Base (KB) article to ensure all prerequisites are met.​ ​​If Windows updates aren't installed before installing the Azure File Sync agent, the Storage Sync Agent service (FileSyncSvc) will fail to start.
121+
122+
## Auto Update can't upgrade a "to be expired" or expired Azure File Sync agent
121123

122-
If Auto Update isn't upgrading your ‘to be expired’ or expired Azure File Sync agent, check if the agent expiration information is properly applied to the server. The expiration metadata is required for Auto Update to function as expected.
124+
If Auto Update fails to upgrade your Azure File Sync agent that is about to expire or has expired, verify that the agent expiration information is properly applied to the server. The expiration metadata is required for Auto Update to function as expected.
123125

124-
To verify whether the `AgentExpirationDate` is set, run the following command from an elevated PowerShell session:
126+
To verify whether the `AgentExpirationDate` metadata is set, run the following command from an elevated PowerShell session:
125127

126128
```powershell
127129
Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
128130
Get-StorageSyncServer
129131
```
130-
If the `AgentExpirationDate` value isn't set or is empty, there might be a networking issue preventing the server from receiving expiration data. To test network connectivity, run the following command:
132+
133+
If the `AgentExpirationDate` metadata isn't set or its value is empty, there might be a networking issue that prevents the server from receiving the expiration data. To test network connectivity, run the following command:
131134

132135
```powershell
133136
Import-Module "C:\Program Files\Azure\StorageSyncAgent\StorageSync.Management.ServerCmdlets.dll"
134137
Test-StorageSyncNetworkConnectivity
135138
```
139+
136140
If network connectivity issues are reported, you can manually update the agent by downloading it from the [Microsoft Update Catalog](https://catalog.update.microsoft.com/Search.aspx?q=azure%20file%20sync).
137-
After downloading the appropriate agent version, refer to the specific **Knowledge Base** article listed in the catalog for step-by-step installation instructions.
138141

139-
If connectivity issues aren't found and the `AgentExpirationDate` is still not set, contact Azure File Sync support for further assistance.
142+
After downloading the appropriate agent version, refer to the specific KB article in the catalog for step-by-step installation instructions.
143+
144+
If there are no connectivity issues and the `AgentExpirationDate` metadata is still not set, contact Azure File Sync support for further assistance.
140145

141146
## High memory usage on the server
142147

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

Lines changed: 0 additions & 91 deletions
This file was deleted.

support/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors.md

Lines changed: 39 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,33 +3,59 @@ title: Errors when running desktop flows including Excel actions
33
description: Provides mitigation steps for errors generated by Excel actions in desktop flows.
44
ms.author: iomavrid
55
author: yiannismavridis
6-
ms.date: 05/08/2023
6+
ms.date: 07/21/2025
77
ms.custom: sap:Desktop flows\Office automation
88
---
99
# Errors when running desktop flows, including Excel actions
1010

11-
This article provides mitigation steps for errors generated by Excel actions in desktop flows. Most errors occur in the context of multiple Excel actions, and there's no strict mapping between them.
11+
This article provides mitigation steps for errors generated by [Excel actions](/power-automate/desktop-flows/actions-reference/excel) in desktop flows. Most errors occur in the context of multiple Excel actions, and there's no strict mapping between them.
1212

1313
## More information
1414

15-
|Exception in error details|Mitigation steps|
15+
|Exception|Mitigation steps|
1616
|---|---|
17-
|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.|
18-
|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.|
19-
|System.Runtime.InteropServices.COMException: Open method of Workbooks class failed|The Excel file path shouldn't contain more than 255 characters.|
17+
|System.ArgumentNullException: Value cannot be null.</br> Parameter name: type|When Excel fails to open with this error, ensure that Excel is installed, licensed, and properly configured on the computer. If Excel is already installed, you can try to repair your Office installation.|
18+
|System.IO.FileNotFoundException: documentPathSafe|Ensure that the Excel file exists and its name and path are spelled correctly. Also ensure that the file path doesn't contain more than 255 characters.|
19+
|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.|Ensure that you have Excel installed on the computer.|
20+
|System.IO.IOException: The process cannot access the file 'C:\YourPath\YourFile.xlsx' because it is being used by another process.|Ensure that the Excel application isn't being used or locked by another process. Try terminating all open Excel processes and restart Power Automate for desktop.|
21+
|System.UnauthorizedAccessException: Access to the path 'C:\YourPath\YourFile.xlsx' is denied.| Ensure that access to the path and file isn't restricted, and Power Automate can access the file.|
22+
|Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Excel document '<Excel_file_name>' not found.|Ensure that the Excel file is open and its name or path is spelled correctly.|
23+
|System.OutOfMemoryException: Out of memory|Close all open Excel applications and unnecessary programs to free up memory, and then try again.|
24+
|System.Runtime.InteropServices.COMException: Open method of Workbooks class failed|Ensure that the Excel file path doesn't contain more than 255 characters.|
2025
|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.|
21-
|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.|
22-
|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.|
23-
|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.|
26+
|System.Runtime.InteropServices.COMException: Unknown name. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME))|Ensure that the target Excel file is open in Protected View.|
27+
|System.Runtime.InteropServices.COMException: Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))|Ensure that the target Excel file isn't being 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.|
2428
|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.|
25-
|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.|
29+
|System.Runtime.InteropServices.COMException: The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))|Keep the Excel instance open and active until all Excel actions are complete. Don't close the file manually or through the "Close Excel" action.|
30+
|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)).|Ensure that you have Excel 2013 or a later version installed on your computer.|
2631

27-
The following exceptions come with embedded mitigation steps in their text.
32+
### Exceptions with embedded mitigation steps
2833

29-
|Exception in error details|
34+
Some exceptions include mitigation steps in their error messages:
35+
36+
|Exception|
3037
|---|
3138
|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.|
32-
|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.|
3339
|System.Runtime.InteropServices.COMException: The file name is too long. Rename the file with fewer than 207 characters.|
3440
|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.|
3541
|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.|
42+
|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.|
43+
44+
## Troubleshooting generic COMException (HRESULT: 0x800xxxxx) errors
45+
46+
When you try to open a blank or existing Excel file in Power Automate for desktop, you might receive an error similar to:
47+
48+
> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x800xxxxx
49+
50+
### Cause
51+
52+
This error might occur due to one or more of the following reasons:
53+
54+
- Office apps (or just Excel) aren't properly installed.
55+
- Power Automate for desktop isn't properly installed.
56+
- The Excel file is synchronized with OneDrive.
57+
58+
### Resolution
59+
60+
- 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.
61+
- 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).

support/power-platform/power-automate/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,6 @@
7676
items:
7777
- name: Errors when running desktop flows including Excel actions
7878
href: desktop-flows/office-automation/excel/troubleshoot-excel-errors.md
79-
- name: Launch Excel action errors
80-
href: desktop-flows/office-automation/excel/launch-excel-action-failures.md
8179
- name: Outlook
8280
items:
8381
- name: Retrieve email messages from Outlook doesn't work as expected

0 commit comments

Comments
 (0)