This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

LabVIEW Report Generation Toolkit VIs Broken

Updated Jun 12, 2019

Reported In

Software

  • LabVIEW Report Generation Toolkit
  • LabVIEW

Other

  • Microsoft Office 365 verison 1609 and above

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. How can I fix this?
  •  I am building an executable which 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

Small differences between versions of Microsoft Office can cause Report Generation Toolkit VIs to break as well as incompatible versions of Microsoft Office. In order to resolve this issue, take the following steps. While 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 verison of Microsoft Office 32bit

  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.
Note: Change <version number> to the specific version of LabVIEW you want to repair. Using a 64-bit version of LabVIEW, the top folder is typically C:\Program Files\, without "(x86)".
 
  1. Once this VI has been opened, click the broken run arrow, select the invoke node error message, and click Show Error.
  
 
  1. This takes you to the invoke node inside the nested case structures.
  1. Once you found the invoke node, perform a right-click anywhere on it, and select Relink Invoke Node:
  
 
  1. If the Relink Invoke Node selection does not appear, you may need to fix the VI by replacing the invoke node.
  • Select the invoke Node (in the picture above it is the tan block that says Range).
  • Copy and paste it on your block diagram.
  • Delete the old invoke node, and replace it to the new invoke node by rewiring the missing terminals. It is a good idea to save a previous copy or take a screenshot of the old VI before deleting the node so that you know where the connections should be made.  
  1. 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:
 
  1. 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.
  1. 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.
  1. 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

Another VI that gets typically broken by changes in Microsoft Office 365 is C:\Program Files (x86)\National Instruments\LabVIEW <version>\vi.lib\addons\_office\_exclsub.llb\Excel_Save_Workbook.vi. For specific information on how to fix that VI please follow the steps in this article: VI Is Broken When Using Excel_Save_Workbook.vi.

WAS THIS ARTICLE HELPFUL?

Not Helpful