Unanswered

Error opening Excel workbook from SharePoint document library

(0) Share

Report

Posted on by Ipsifendus

I have a desktop flow that uses the "Launch Excel" action to open a workbook that's kept in a SharePoint document library. The flow was working just fine, and then I changed the setting for "Make instance visible" to "Off". Shortly after making this change, the package started failing when the "Launch Excel" option fires. The error message is...unhelpful (I'll paste it below), but I speculated that the problem was that the workbook was still open in a running (but invisible) instance of Excel. So, I've used Task Manager to kill all Excel sessions, but still get the error. Turned off OneDrive, still get the error. Did a repair on my Office installation (as suggested when other people have reported the same error)...no good, still get the error.
Anybody have any ideas? Error text as follows:

Correlation Id: afbe2ae6-d6dc-4faf-b4a4-8667eb90f592

Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED)): Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Failed to open Excel document [URL REDACTED] (Active workbook retrieval error). ---> System.Runtime.InteropServices.COMException: Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture)
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.GetProperty(Object o, String propertyName)
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.LaunchExcel(Variant documentPath, Variant readPassword, Variant writePassword, Variant& excelInstance, Int32 launchMode, Boolean visible, Boolean loadAddInsAndMacros, Boolean needsAuthentication, Boolean readOnly, Boolean launchInNewInstance, String& version)
--- End of inner exception stack trace ---
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.LaunchExcel(Variant documentPath, Variant readPassword, Variant writePassword, Variant& excelInstance, Int32 launchMode, Boolean visible, Boolean loadAddInsAndMacros, Boolean needsAuthentication, Boolean readOnly, Boolean launchInNewInstance, String& version)
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.LaunchExcel.Execute(ActionContext context)
at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

Categories:

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (0)

Sort by

WillSG 352 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @Ipsifendus I hope you are doing well.

I see, based on my experience it’s really interesting that it’s not working just because you disable the option, however, take this into consideration:
Check the document specified in the URL provided and ensure that it is accessible and not corrupted.
Verify the permissions and authentication required to access the document.
Validate if a macro was added or modified recently, Macros with the set up to refresh once opening generate issues with PAD.
Finally, have you tested again with the make the instance visible enable, is it working?

Please let me know if it works, happy automation!

If I have addressed your inquiry successfully, kindly consider marking my response as the preferred solution. If you found my assistance helpful, a 'Thumbs Up' would be greatly appreciated.

Additionally, I offer specialized consultancy and development services leveraging PAD. If you're interested in exploring these services further, feel free to DM me, and we can initiate a discussion.

Finally, here is my LinkedIn Profile if you want to follow or connect with me.

Kind regards,

Will SG
Managing Director & Automation Lead
RAMS CR (Recruitment & Automation)

Was this reply helpful? Yes No
Ipsifendus 43 on at

Like
a
(0)

Report
Copy link

Link copied!

Yep, the file in question is available and uncorrupted. I can open it in Excel manually either using the web-based or desktop versions of Excel. The user that the flow signs on with has permissions to open the file. No changes have been to the file since testing commenced, and the flow was working for several days until the invisibility flag was set.
I have attempted setting the flag off again, but the package continues on failing with the same error message.
Currently as a workaround I've pointed the flow at a different file, identical in content. It works fine with that file. So I get the feeling that some element of the Microsoft product ecology thinks that the file is open for editing somewhere, or popping up a modal message box, or something. I don't know if that element is Windows, Office, OneDrive, Power Automate, or SharePoint, or other. But it's been a full 18 hours and the file is still inaccessible to the flow.

Was this reply helpful? Yes No
davykouakou 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, I have exactly the same issue. Did you ever get a proper solution? tks

Was this reply helpful? Yes No
Ipsifendus 43 on at

Like
a
(0)

Report
Copy link

Link copied!

I never did, sorry. I haven't been able to find any solution other than renaming a copy of the file and using that instead.

Was this reply helpful? Yes No