06-13-2017 04:17 AM
Hi,
I have a broken LabVIEW 2014 install, when I try to open the NI example finder from the LabVIEW IDE menu system.
I have had this problem a few years ago when installing lots of different version nof LabVIEW and playing with Beta's. In the past this was easy to solve by doing a Repair on the installation as shown in the Knowledge based article below.
http://digital.ni.com/public.nsf/allkb/2A853C9ECC0AA98286257560007D57AB
However, trying this now I have 2017 installed and the NI Package Manager there no longer seems to be a Repair option.
Any suggestions please, I really really do NOT want to do a complete uninstall and reinstall as I am in the middle of a important project.
regards
Danny
06-14-2017 05:33 AM
Hi Danny,
Unfortunately here is no way to repair products in NI Package Manager.This is a known issue (#644626 at NI Package Manager Known Issues).
The best way to 'repair' is to uninstall and reinstall.
If this really isn't a possibility you can first uninstall all the 2017 and NXG products through Package Manager, and at the end Package Manager itself. (Package Manager also has its own entry next to the National Instruments Software in Add/Remove Programs window.) This will allow the Add/Remove Programs functionality for NI Software to go back to what it used to be.
I hope this helps,
Rebecca
06-14-2017 02:14 PM
Danny,
In addition to Rebecca's suggestion, there is another way that leverages the older uninstaller system, though it has a limitation. Here are the steps:
This will not repair everything, but should repair LabVIEW 2014 itself.
Regards,
- Wes
06-15-2017 06:09 AM
Thank you both for your replies.
I must say i think that this "know issue" is rather a major one to be honest and no workaround. Is this something that is going to be fixed at some time going forward ?
I did try you solution Wes, but it did not fix the problem for me, but thanks for the suggestion. Looks like I will have to live with the problem for now
cheers
Danny
09-11-2017 09:29 AM
I've just run into this problem. This is amateurish, NI. Fix it.
09-18-2017 05:15 AM
Me too - I missed installing R-series card drivers and after installing, can't get the FPGA VIs to show support for the cards. Having to uninstall/reinstall a bunch of components to try and resolve because the repair option is greyed out.
11-07-2017 01:13 PM
There is still a repair option if you just run the installer directly.
I wanted to repair MAX 17.0. So I put in the DAQmx 17.0 DVD, browsed the folders in products to MAX and ran the MSI file there. It let me choose a repair option.
TIL
01-10-2022 01:32 AM
I have just run into this problem
Following this worked
VI Package Manager Runtime Engine - Installation Media Required for Repair – VIPM
01-10-2022 07:37 AM
@DavidJCrawford wrote:
I have just run into this problem
Following this worked
VI Package Manager Runtime Engine - Installation Media Required for Repair – VIPM
Hi, David:
NIPM and VIPM are different applications. It took me probably a year to not get confused between the two.
01-10-2022 07:40 AM
Before 2017, which saw the introduction of NIPM, I often had 3-5 versions of LabVIEW installed on my PC. On multiple occasions, I would "mess up" one of the older ones, and need to do a "repair". I quickly (well, it took me about three experiences to "learn the lesson") realized that the "Repair" option was (a) extremely slow, (b) required a lot of CD shuffling, and (c) frequently didn't work, which forced me to do a "Remove/Reinstall Everything" option. After the third time, I realized "Remove/Reinstall" was actually much faster, and almost always worked (don't ask about LabVIEW 2011 ...).
Moving into the NIPM Era, that is still my "Best Practice" (I just did it recently with a system that had both LabVIEW 2019 and 2020, not quite working, and I wanted a pure 2019 system -- remove/reinstall, though NIPM Installation "gotchas" meant I had to try three times before I got the sequence of which packages to install in what order right ...).
Bob Schor