Problem while executing action 'SaveAs'. Failed to save Excel document

[jogden]

All of the sudden I have had two flows start throwing this error. I have other flows that run and save to the same locations without any  issues. 

This has happened now to two different flows which pull data from SQL then create an xlsx doc, and saves it to one-drive. The first one I was able to just recreate the save as step and it fixed it, the second one that is not working. 

Same box and same one drive are being used to run other flows in the same manor without issues. 

Full error below 

Problem while executing action 'SaveAs'. Failed to save Excel document '*One-Drive Location*'.
Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Failed to save Excel document '*One-Drive Location*'. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: SaveAs method of Workbook class failed
--- End of inner exception stack trace ---
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.InvokeMethod(Object o, String methodName, Object[] methodArgs)
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.SaveExcelInstance(Object activeWorkbook, String workbookName, FileVariant documentPathSafe, SaveExcelEnum saveSafe, ExcelSaveAsFormatEnum saveAsFormatSafe, String xmlMapName)
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.SaveExcel(Variant excelInstance, Variant documentPath, Int32 save, Int32 saveAsFormat, String xmlMapName)
--- End of inner exception stack trace ---
at Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.SaveExcel.Execute(ActionContext context)
at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

[jogden]

I have a different box I was able to run it on, the only difference is the path to the one drive on the box that failed is a direct sync were as the box it is working on is a mapped drive to the OneDrive. (The mapped drive is much slower) 

[jogden]

Bump, anyone have any ideas? it is popping up again on the flow that was fixed but on only 1 of the 5 files. 

[jogden]

Bump

[jogden]

Bump

[jogden]

After some thought my theory is that "TargetInvocationException" points to some connectivity issued with the one drive. 

I created a temp space on the host to save the files and use the move files function to then move the files to the one drive it adds 20-30 seconds to the flow, so far it is working when I manually kick off the flow. Still need to test the cloud schedule flow tomorrow. 

[msharmes]

I have the same problem, also with an excel file located in my company OneDrive. And it worked before (must have been some weeks ago). Maybe this is some kind of malware protection from Microsoft?

My error message (partly German):

Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Speichern des Excel-Dokuments „Forms.xlsx“ fehlgeschlagen. ---> System.Exception: „Forms.xlsx“ kann nicht gespeichert werden, da die Datei schreibgeschützt ist.
bei Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.SaveExcelInstance(Object activeWorkbook, String workbookName, FileVariant documentPathSafe, SaveExcelEnum saveSafe, ExcelSaveAsFormatEnum saveAsFormatSafe, String xmlMapName)
bei Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.ExcelActions.CloseExcel(Variant excelInstance, Variant documentPath, Int32 save, Int32 saveAsFormat, String xmlMapName)
--- Ende der internen Ausnahmestapelüberwachung ---
bei Microsoft.Flow.RPA.Desktop.Modules.Excel.Actions.CloseExcel.Execute(ActionContext context)
bei Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

[msharmes]

Small update here: I managed to solve the problem: In my flow I open the excel as "read-only". When closing it "save document" was pre-selected. This was accepted in older versions of Power Automate Desktop but throws now this error message. I changed the Close Excel step to "do not save document" and it works now.

[jogden]

Are you adding data to the file? I am creating a new file in my flow so I am not sure the read only would solve for me. I do have the close step set to not save as I have a step for saving already. 

[msharmes]

At first I open the file read-only. Later I open the same file again for read-write and change it.

If you have already a save step, maybe you can try "do not save document" in the close step.

[Zap174]

@jogden @msharmes 

I am having this issue as well. I tried to recreate the steps that @msharmes listed in their comment above but was unable to. Could either of you share in detail what your fix was?

[jogden]

I solved mine by first saving it to a temporary folder on the local system then moving it to my One drive. 

[cdkincaid]

I had the same problem. Changing the Close Excel step to "do not save document" worked for me. Thanks!

[Crack-1703]

I have a similar scenario. but it has only become an issue in since the 17th April,
In order to identify the problem I built a very simple flow.
Launch Excel, Wait(3), Close Excel save document).
I created a Excel document Test.xlsm with a macro in ThisWorkbook,  - Workbook Open
The macro code is just msgbox("&%^$%^&)

In Excel I can Open and Close with no problem.
Then I run the flow above - with no problem,
If I then open Test.xlsm it opens the message is displayed but with no sheets.

Any Ideas?

[HaBi_CHB]

Hi,

I've the same problem here. I solved the problem by changing / deactivate the option in the start excel-dialog from (in german version of power automate) "Unter einem neuen Excel-Prozess verschachteln" (more-option).

This helps.