Archived:Report Generation Toolkit Version 1.1.x VIs Break After Updating LabVIEW

Updated Oct 27, 2020

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Reported In


  • LabVIEW
  • LabVIEW Report Generation Toolkit 1.1.1
  • LabVIEW Report Generation Toolkit 1.1.2
  • LabVIEW Report Generation Toolkit 1.1.3
  • LabVIEW Report Generation Toolkit 1.1.4

Issue Details

I am using the LabVIEW Report Generation Toolkit for Microsoft Office version 1.1.x with LabVIEW 8.x or 2009. After installing the LabVIEW update, my Report Generation VIs no longer work properly. Why is that, and how can I fix this?


Installing the Report Generation Toolkit replaces core LabVIEW files with toolkit versions of the files; however, the LabVIEW update replaces some of these same files. This results in a mix of toolkit VIs and LabVIEW VIs, which ultimately results in broken toolkit VIs. You may also find that your Word Specific and Excel Specific palettes are missing.

To resolve this problem, uninstall and reinstall the Report Generation Toolkit.
  1. Open the Windows Control Panel (Start»Control Panel) 
  1. Open Add or Remove Programs
  1. Find National Instruments Software and select Change
  1. Find NI Report Generation Toolkit for Microsoft Office and select Remove
  1. After the removal is complete, restart your computer
  2. Reinstall the toolkit from your disk
  3. Open LabVIEW and confirm the Toolkit's VIs are intact and operable

Additional Information

After building into an executable, you may also find that VIs that work fine in the development environment are not being found by the built application. The search may even be looking in the proper folder for the resource files and not finding them.

If repairing the Report Generation toolkit as detailed above does not resolve the issue, check the location of the build. Failure to locate the Report Generation VIs has been observed when building into the user.lib or other directories in the LabVIEW folder. This practice is not generally encouraged as it entangles user files with the LabVIEW source files, and building outside the directory seems to solve the problem in these cases.