Report Generation Toolkit dependency broken after installing LabVIEW 2026 Q1

[EnthusiasticTester]

Hi

Today I installed LabVIEW 2026 Q1. After installation I opened a project in LabVIEW 2024 Q1 that had a dependency to the report generation toolkit. Specifically the excel functions.

They were all missing. The folder was even removed from the LabVIEW 2024\vi.lib directory.

When i checked NI Package Manager it showed a LabVIEW 2026 Q1 Report Generation Toolkit was installed and I could not install the LabVIEW 2024 Q1 version because a newer version exists.

Is it correctly understood that installing LabVIEW 2026 Q1 breaks this dependency? Did i miss something? Is this a bug associated with bleeding-edge SW?

Thanks for reading 🙂

[santo_13 · Accepted solution]

My best guess is that they moved the RGT to version agnostic LVAddons directory with a configuration to support only 2026+, someone else also reported a similar issue for the Database toolkit

[santo_13]

Here is the other issue https://forums.ni.com/t5/LabVIEW/LabVIEW-2026-and-the-Database-connectivity-toolkit/m-p/4468806#M132...

[EnthusiasticTester]

That would explain it.

It does mean that everyone on the team would have to install LabVIEW 2026 Q1 or risk a tedious search for dependencies every time they open the project after I have submitted changes. I have uninstalled LabVIEW 2026 Q1 and re-installed the RGT for LabVIEW 2024 Q1 and that worked.

[IanLloyd]

I had the problem with the database toolkit.
Now I have a problem with the RGT.

I have a application written in 2024 that use the RGT, it works OK in the development environment but when I build it as an executable it fails to open the excel file that it should.

I have tried the same with a 2026 application it does the same. At least this gives me an error message.

The full text of the error is

Possible reason(s):

LabVIEW: (Hex 0x464) VI is not loadable.

In a built application, this error might occur because the VI being loaded was last compiled for a different OS or with CPU features, such as SSE, that this target does not support. In this case you must rebuild the application for the target OS and make sure SSE compiler settings in the build specifications match the target platform. This error also might occur if the VI is a polymorphic VI, which cannot be loaded in the LabVIEW Run-Time Engine. You must load an instance of the polymorphic VI instead of the polymorphic VI itself.

Complete call chain:
Get LV Class Default Value.vi
NI_report.lvclass:Create Report.vi
RDS_Populate_Sensor_Readings_at_Temperature.vi
RDS_Temperature_Test.vi

LabVIEW attempted to load the class at this path:
C:\Projects\R_and_D_Software version 7.0\Builds\RDS_Ver1.exe\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass

Has anybody seen a message like this before?

[EnthusiasticTester]

Hi Ian

I haven't seen that error message, but considering the text, and that it works in the development environment, I would try a mass-compile of all the VIs in the call-chain.

[ConnerP]

Always wait for the first patch release.

[IanLloyd]

The message says it is trying to load Create Report.vi from this path

LabVIEW attempted to load the class at this path:
C:\Projects\R_and_D_Software version 7.0\Builds\RDS_Ver1.exe\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass

This path doesn't exist on my PC

It is

C:\Program Files\National Instruments\LabVIEW 2026\vi.lib\Utility\NIReport.llb\Create Report.vi

And I don't understand how this relates to an EXE

I've read elsewhere about having to have the excel class in the always include but I didn't need to do that previously for this application.

[IanLloyd]

"Always wait for the first patch release."

and if everyone did that who would find the errors.

Thanks for your help

[EnthusiasticTester]

It is possible that this is an exe issue. Paths used in VIs are not always the same as paths in exe files.

I found this one that might help: Solved: Understanding File Path inside a EXE - NI Community

I haven't built a lot of exe files, but I have experience with PPLs. When all my dependencies in a project are from basic labview or other PPLs then the path inside the PPL is the same as in my library. However, if I reference a vi that is not part of the basic LabVIEW then the ppl adds an extra layer in the paths to differentiate between VIs in the library and VIs from outside the library.

Can you check your dependencies?