Mads Toppe Posted January 25, 2021 Report Share Posted January 25, 2021 Trying to repair NI RIO on my machine NIPM keeps asking for the location of the VI Package Manager RunTime Engine: And the location it shows is of cours enot accepted (nor can I find one that it does accept). The funny thing though is that this happens even after I have uninstalled all parts of VIPM(!). Reinstalling VIPM does not resolve the issue either...Any ideas? 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 25, 2021 Report Share Posted January 25, 2021 Thanks for reporting this. I haven’t heard of this one before, and it seems like something for which we need to loop in NI, since it appears to be something NIPM is looking for and I don’t know about the internals of that. Let me reach out to NI and see what I can find. Quote Link to comment Share on other sites More sharing options...
kosist Posted January 26, 2021 Report Share Posted January 26, 2021 I've seen similar behavior during building of LabVIEW application installer. We've installed LabVIEW 2019 some time ago, and then cleared NI Packages cache. Then later on we had to build executable and installer. Executable was built without issues, but with installers were problems - LabVIEW "asked" to provide installation media for various distributions/drivers, including VIPM Run-Time Engine (which had nothing to do with our application). Reinstalling VIPM didn't help. In our case, the solution was to repair LabVIEW completely, using installation media. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 26, 2021 Report Share Posted January 26, 2021 14 hours ago, Mads Toppe said: Trying to repair NI RIO on my machine NIPM keeps asking for the location of the VI Package Manager RunTime Engine: And the location it shows is of course not accepted (nor can I find one that it does accept). The funny thing though is that this happens even after I have uninstalled all parts of VIPM(!). Reinstalling VIPM does not resolve the issue either...Any ideas? Hi @Mads Toppe. What version of NI RIO is on your machine that you're trying to repair? A comment I got back from an NI support person is that the "dialog looks like a “metaInstaller” which would be pre-2019, in which case it’s an OS thing from the MSI installer. " I'm not sure if that's helpful or not. I'm hoping to hear more back from NI. I'll keep you posted. Quote Link to comment Share on other sites More sharing options...
Mads Toppe Posted January 26, 2021 Author Report Share Posted January 26, 2021 (edited) I suspect that the issue was that after installing VIPM as part of the LabVIEW installation I had applied an update to VIPM. NIPM offered me to uninstall VIPM, but I noticed that after uninstalling in NIPM (and NIPM reported that no VIPM was installed) I could still find VIPM under Programs and Features. Once I uninstalled it from there as well I was able to run the repair from NIPM. If this is the case the issue could perhaps reappear though, due to the VIPM update function....If NIPM is not directly involved it loses track of what is installed and from where...? Edited January 26, 2021 by Mads Toppe 1 Quote Link to comment Share on other sites More sharing options...
Mads Toppe Posted January 26, 2021 Author Report Share Posted January 26, 2021 12 hours ago, Jim Kring said: What version of NI RIO is on your machine that you're trying to repair? This was on a machine with only one version of LabVIEW/RIO ever installed on it - 2020. 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 26, 2021 Report Share Posted January 26, 2021 Hi @Mads Toppe, So that I can get NI support into the loop on this, can you please submit a bug report with NI and then respond back to me with the link to that ticket (you can send it to me off-line if you prefer). When you submit the ticket to NI, please list the steps you took to get into the situation (if you can) and also provide the screenshots you posted here in the forum. I can then work to get the ticket escalated and reproduced internally by NI so their dev team can figure out what happened. Thanks! Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 26, 2021 Report Share Posted January 26, 2021 Hi @Mads Toppe, Can you try this? Download this zipped up version of the VIPM Runtime Engine installer and point the "Select Distribution" dialog to where you extracted it? vipm-runtime-engine-19.1.3-windows.zip I'm hoping that will help you get past this step. The longer story is that it seems there's some deadlock happening due to the way NIPM and NI's older driver installers work. Hopefully, we'll get you going again. Please let me know if this works for you. Quote Link to comment Share on other sites More sharing options...
Mads Toppe Posted January 27, 2021 Author Report Share Posted January 27, 2021 Hi @Jim Kring 11 hours ago, Jim Kring said: Hi @Mads Toppe, Can you try this? Download this zipped up version of the VIPM Runtime Engine installer and point the "Select Distribution" dialog to where you extracted it? vipm-runtime-engine-19.1.3-windows.zip I'm hoping that will help you get past this step. The longer story is that it seems there's some deadlock happening due to the way NIPM and NI's older driver installers work. Hopefully, we'll get you going again. Please let me know if this works for you. That worked😃. I had already gotten around the issue by uninstalling VIPM from Programs and Featuresafter having uninstalled it from NIPM.But then as soon as VIPM was reinstalled and updated again from its automatic update feature the issue in NIPM was back. As I suspected...The folder you sent was accepted as a source though so with that it is possible to do a repair without everything halting on the VIPM error. PS. NIPM is really terrible (compared to VIPM e.g.); From NIPM you cannot even repair VIPM without having to repair almost every component there is of LabVIEW ☹️ 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 27, 2021 Report Share Posted January 27, 2021 Hi @Mads Toppe, Thats fantastic news. I’m really glad that worked for you. Thanks for sharing all the details about the problem and how you fixed it. We will create a knowledge base entry about all this to hopefully help anyone else who may get stuck in a similar situation. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted February 1, 2021 Report Share Posted February 1, 2021 @Mads Toppe, Thanks again. We've created an official knowledge-base entry for this issue: Knowledge Base: VI Package Manager Runtime Engine - Installation Media Required for Repair Quote Link to comment Share on other sites More sharing options...
Sam Sharp Posted August 11, 2021 Report Share Posted August 11, 2021 (edited) Hi Jim, I have also now run into a similar issue, I tried the steps in your workaround (with VIPM 2020.3) and it is looking for installer media here: The folder is empty. If I try the workaround and select the downloaded 19.1.3 runtime folder I get this message: I also tried: - Pointing it at the LabVIEW 2017 SP1 Runtime (since that's what I'm building) - Repairing LabVIEW from NIPM - Repairing VI Package Manager This is what's in my installer build spec: And the only thing it's complaining about is the "VI Package Manager Runtime Engine": Edited August 11, 2021 by Sam Sharp Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted August 11, 2021 Report Share Posted August 11, 2021 38 minutes ago, Sam Sharp said: Hi Jim, I have also now run into a similar issue, I tried the steps in your workaround (with VIPM 2020.3) and it is looking for installer media here: Hi Sam. I'm sorry for the trouble. This is really a pain... Can you try using this copy of the "VI Package Manager Runtime Engine" installer? >> vipm-2020.3.2540-windows-prerequisites.zip << This is a copy of the actual temp folder (containing the VIPM runtime engine) extracted during the VIPM 2020.3.2540 installation. C:\Users\%USERNAME%\AppData\Roaming\JKI\VI Package Manager 2020.3\prerequisites If that doesn't work, we could try the one from the 2020.3.2532 installer. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.