05-08-2018 08:51 PM
is it on a network drive, the Excel spreadsheet? What happens, when you open it, does it say something about being protected? Open the spreadsheet yourself, see, if you can edit it, maybe it throws a warning.
Alternatively, can you save as .csv?
How about Open Office?
Some programs I cannot save to my desktop, only into my documents.
Another HD partition an option?
Excel not installed as Admin?
There is a software called "take ownership". maybe do that on the folder where you want to save into.
Recently I tried to get rid of Windows 10 on a laptop, what a pain that was.....
05-09-2018 05:12 AM
one more thing, is it Excel 2016? With all that 360 stuff, it takes forever to open the 1st time after PC reboot. Logging in to check, if its still licensed. Maybe run excel first, close, and then try again
05-09-2018 07:33 AM
Looks like we are all on the same track.
The dev machine is networked running Windows 7 Enterprise 64Bit, Office 2010
The target machine (that won't work) is a network pc running Windows 10 and Office 2016
05-09-2018 08:38 AM
I read in one of our documents: "Microsoft Excel spreadsheets [...] increased these limits to 16,384 columns and 1 million rows. If these limits are exceeded and there is an attempt to access a row or column outside the allowed range, this error will occur: Error -2146827284 from the Excel_Get_Range VI." - Error 2146827284 Occurs When Writing to Excel Report Using Report Generation Toolkit VIs
Another document states that this can be caused because of the file not being accessible: Error-2146827284: File Does Not Exist When Opening Excel in LabVIEW
Not sure if this could be the problem you are seeing (since it is the same ActiveX error code), but might be worth double checking if the Excel application is being initialized as Minimized, that the amount of samples being written to it is not too large, and that the file or destination can be accessed correctly.
05-09-2018 12:15 PM
BINGO!
Kudos to whomever suggested to make sure to NOT select Minimized.
Suggestion to the good folks at NI. Perhaps add this to the help file.