New work PC, wondered why a script (that i use regularly) was completing without opening the excel file at the end.
Seems the Data.ExportExcel node is giving a rather helpfully vague error message.
Same message seen here using the sample “Export Data to Excel” script.
The machine is a brand new item, fresh install of current windows 10 and office365 (both x64)
all works fine on other machines in the office.
(my script uses a combination of bumblebee write to excel nodes and the ExportExcel nodes - as I like the fact the ExportExcel opens the file for me afterwards)