LabVIEW Report Generation Toolkit VIs Broken

Issue Details

• I have a LabVIEW program that uses the LabVIEW Report Generation Toolkit. Recently, I started receiving an error that one VI, Excel Save Workbook.vi, and all its dependencies are broken. The issue details indicate the following. How can I fix this?:

 

• When I try to print an Excel Report using the Report Generation Toolkit in LabVIEW, I get the following error:

 

• Using Excel_Save_Workbook.vi from the LabVIEW Report Generation Toolkit  leads to a broken caller VI and LabVIEW reporting a block diagram error for an Invoke Node:

Invoke Node: Contains unwired or bad terminal
 

 

• I am building an executable that includes LabVIEW Report Generation Toolkit VIs and get the following error message upon building:

A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build. Report this error to National Instruments technical support.
 

  

Solution

There are some issues when using incompatible versions of LabVIEW and Microsoft Office.  These issues could cause Report Generation Toolkit VIs to break as well as Microsoft Office. In order to resolve this issue, take the following steps. While some of these steps use Excel Sort Data.vi as an example, the repair steps for fixing other VIs are analogous.

1. Make sure you are using a compatible version of Microsoft Office.

2. Open the broken VI, e.g. C:\Program Files (x86)\National Instruments\LabVIEW <version number>\vi.lib\addons\_office\excel.llb\Excel Sort Data.vi. 

3. Once this VI has been opened, click the broken run arrow, select the invoke node error message, and click Show Error.

4. This takes you to the invoke node inside the nested case structures.

5. Once you found the invoke node, perform a right-click anywhere on it, and select Relink Invoke Node:

 

6. If the Relink Invoke Node selection does not appear, you may need to fix the VI by replacing it with the invoke node.

7. This should cause another input node to appear at the bottom of the list, e.g. named SubField1 in the VI used as example here:

8. Once this is done, the run arrow should no longer be broken. Save Excel Sort Data.vi and try running your main VI once more.

9. If you get an error message "The VI already exists and you do not have permission to replace it." when saving the VI, please go through this article suggestions. 

10. If this does not fix the issue, mass-compile the folder that Excel Sort Data.vi is found in. This can be done by clicking menu Tools»Advanced»Mass Compile from in LabVIEW. Then navigate to the folder in which Excel Sort Data.vi is found and select Current Folder.
11. If the issue still persists, perform a reinstall of the Microsoft Office software. This will resolve the behavior in cases where corruption during installation has occurred.

Additional Information

It isn't possible to edit these VI's in Evaluation Mode. If you haven't purchased access to LabVIEW visit our website and Select Your LabVIEW Edition.