04-23-2019 03:21 PM - edited 04-23-2019 03:24 PM
I'm having a strange issue with the Report Generation Toolkit in LabVIEW 2018 (32 bit) that I've traced to the "Excel_Save_Workbook.vi" found inside the "Save Report to File.vi". I've spent most of the day chasing error code 97:
A null or previously deleted refnum was passed in as an input
Thankfully it seems like I'm not the only person who has had this problem; however, after looking at the various references linked below, I have tried the following to no avail:
Lastly, I came upon a recommendation to delete and replace the "_Workbook" Invoke Node in the affected VI (see below):
In attempting to do so, I noticed a few things...
FWIW, I've taken a look at the parent VI (Save Report to File.vi) where the "Excel._Workbook" is extracted via an Unbundle by Name. It would seem that for some reason my Report Generation Toolkit is damaged and some or all of my Excel LV classes are missing their constituent Methods.
If anyone can provide advice on how to repair or replace these missing / damaged components, I would be incredibly appreciative.
References:
Edit: Formatting
04-23-2019 04:28 PM
Sorry, you've (probably) gotten bad advice. The problem is that Microsoft made a change in some of its functions and forgot to tell NI. You are correct about the source of the problem, but you do not want to replace NI's code. You want to start with a good installation (that doesn't work because Excel_Save_Workbook is "broken"). Here's how to fix it:
Open it up and expand the Case Statement so that you can see the Invoke Node. It is probably broken, and doesn't look like the one in the picture, below (it is missing the last entry). I think you can right-click the Invoke node and ask it to "repair" itself, which should (a) change it to look like the one shown here, and (b) make the Broken Arrow go away. That will fix it (until you reinstall LabVIEW, but you'll just do the fix again).
Bob Schor
04-24-2019 07:17 AM
Thank you for the reply, Bob! The trouble is, I don't have the usual "broken" arrow. The VI will run...it's just wrong. I don't even have the option to re-link / repair the Invoke Node. is it fair to assume that my only option at this point is to reinstall LabVIEW?
04-24-2019 11:28 AM
@JRiggles wrote:
Thank you for the reply, Bob! The trouble is, I don't have the usual "broken" arrow. The VI will run...it's just wrong. I don't even have the option to re-link / repair the Invoke Node. is it fair to assume that my only option at this point is to reinstall LabVIEW?
That's strange ... Before you go through the process of an Uninstall/Reinstall, which might (or might not!) fix the problem, can you create a bundle of Program and Data that illustrates the problem and let us test it and confirm (a bug) or explain (an error or misunderstanding)?
Bob Schor
Bob Schor