Installing LabVIEW 8.2.1 On Top of LabVIEW 8.2 Causes Broken VIs and Libraries
Primary Software: LabVIEW Development Systems>>Professional Development System
Primary Software Version: 8.2.1
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>Full Development System, LabVIEW Development Systems>>Base Package
Problem: When upgrading LabVIEW 8.2 to 8.2.1 by installing LabVIEW 8.2.1 without first uninstalling LabVIEW 8.2, you will encounter the problems mentioned below. The root cause of these problems is that the subVIs and typedefs for ODE Solver.vi in the NI_Gmath.lvlib library are not properly installed in this scenario. This causes ODE Solver.vi and the NI_Gmath.lvlib library to break.
Note: This is only a problem when installing LabVIEW 8.2.1 on top of LabVIEW 8.2. If you first uninstall LabVIEW 8.2 and then install LabVIEW 8.2.1, you will not encounter this problem.
All users who installed LabVIEW 8.2.1 on top of LabVIEW 8.2 should repair their installation as described in the solution section at the end of this document.
Below are common situations in which you may be affected by this problem.
- Any VI that directly uses ODE Solver.vi
Since ODE Solver.vi becomes a broken VI, any VI that contains ODE Solver.vi in its hierarchy will also be broken.
- Building a source distribution that includes any VI in the Advanced Analysis or G Math Libraries (NI_AALPro.lvlib, NI_AALBase.lvlib, or NI_Gmath.lvlib)
Breaking any VI within a project library causes the entire library to break and NI_Gmath.lvlib is a dependency of NI_AALPro.lvlib and NI_AALBase.lvlib. By default, source distributions include all members (even those unreferenced) of a project library if the project library is a dependency of the build.
In this situation, you will receive an error indicating that "The build was unsuccessful." Possible Reasons will include "An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them (Ctrl-Shift Click the run arrow), and save them to update their dependencies." Details of the error will reveal error 7, indicating "The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File»Open and verify that it is runnable."
- Building an executable that includes any VI in the Advanced Analysis or G Math Libraries (NI_AALPro.lvlib, NI_AALBase.lvlib, or NI_Gmath.lvlib) while at the same time specifying in the build specification "Do not disconnect type definitions or remove unreferenced members" on the Additional Exclusions page.
Breaking any VI within a project library causes the entire library to break and NI_Gmath.lvlib is a dependency of NI_AALPro.lvlib and NI_AALBase.lvlib.
In this situation, you will receive an error indicating "The build was unsuccessful." Possible Reasons will include "The VI is broken. Open the VI in LabVIEW and fix the errors." Details of the error will reveal error 1003, indicating "The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable."
- Deploying VIs with TestStand
When deploying VIs that contain in the hierarchy ODE Solver.vi or any VI in the Advanced Analysis or G Math Libraries (NI_AALPro.lvlib, NI_AALBase.lvlib, or NI_Gmath.lvlib) will cause the Deployment Utility to generate:
"Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version. The missing file path is: [VIpath] while Processing VIs..."
- Using LabVIEW Control Design and Simulation products
Many of our control design and simulation tools rely on VIs and controls missing as a result of this problem. When using the control design and simulation tools, if you are affected by this problem, many VIs will be missing components.
Solution: To correct this problem, you need to repair the simulation.msi component either manually or programmatically.
To repair the simulation.msi component manually:
- First, shut down LabVIEW.
- Locate and run simulation.msi from the installation distribution (i.e. the CD you used to install LabVIEW). You can find simulation.msi in
\Products\LabVIEW_Simulation_Core_Shared\simulation.msi.
- Choose to Repair and proceed through repairing this component.
- Restart LabVIEW and the problem should be corrected.
To repair the simulation.msi component programmatically:
- First, shut down LabVIEW.
- Download and run LabVIEW 8.2.1 Repair_Simulation_MSI.exe (attached below). This executable contains and repairs the simulation.msi component so you will not need to locate your installation distribution.
- Restart LabVIEW and the problem should be corrected.
Related Links:
Attachments: 
Report Date: 04/04/2007
Last Updated: 01/16/2008
Document ID: 47CDMI00
