Jump to content

Mads Toppe

Members
  • Posts

    14
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Mads Toppe

  1. I had not RTFM so I tried adding multiple search terms by separating them with comma, semicolon or logical AND/OR operators but since none of that worked I just assumed multiple keywords were not supported. The manual however says that you can separate the terms by space....This does not work as expected though (so perhaps I did try space-separation earlier, but thought it did not work) as the default then is to require *all* terms, not one or more. Why would i like to search for any of the terms? Well, often I just need to quickly install a few known package sets and I know their names. Instead of hunting through the entire list of packages I could then just write the keywords to get a shortened list of the ones I probably want, and select from that.
  2. If VIPM says I have a package installed, but the package is corrupted or missing anyhow it would be nice to be able to select a bunch of packages and choose to reinstall them. Currently I have to remove or downgrade them and then reinstall them, when all I want to do really is to repair the installation of the current version.
  3. FYI: I had 4.2b installed and ran into a couple of issues with the upgrade to 5.0: 1) The package fails to download. I manually downloaded it through the web browser instead and that worked though. 2) When first installing it says that it failed to upgrade. Running the same operation again produces the informational dilaog where you have to scroll down to the end to OK it, and only then, this second time, did it install OK. Unistalling the previous version first did not seem to change the need for a second run to get the dialog.
  4. Trying to install the same packages on a couple of new machines as on my main development machine I exported a configuration and open it on the new machines. On these new machines though several of the packages will pop up in the license agreement dialog during this, and for some reason this always seem to end up with the dialog in a dead state. I click to agree and all the packages disappear from the agreement list, but nothing happens after that. The window stays open but does not react to anything. Looking at the error log I can see an entry for what is probably the first package (here Variant_Probe-2.4.3-0) that it runs into an issue with (there are several packages that cause the same issue): =========== START of VIPM 2024.1 f1 (build 2637) Error Message =========== An internal VIPM 2024.1 f1 (build 2637) Error has occured on: Friday February 09, 2024 at 12:43:05 PM = Automated Message Start = Error 1 occurred at (No Package Info found for "Variant_Probe-2.4.3-0") B73B39751ECBFB0AAAB62D0FC81D35BC in OGPM Class.lvlib:058D7D5CE34F15D58C5A800E04C162FC->VIPM Package License Dialog.vi->VIPM Main Window.vi Possible reason(s): LabVIEW: (Hex 0x1) An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. = Automated Message End = = User Defined Message Start = Log Error in Main Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi = Error Handler Call Chain End = =========== END of VIPM 2024.1 f1 (build 2637) Error Message =========== Is there a way to get around this other than to remove all the pacakages it has issues with (fix anything in the package)? Perhaps VIPM should be rewrittens lightly to handle this in a way that lets you move on to the othe rpackages it doe snot have an issue with, or ignore the issue and still install the affecte dpackages if possible?
  5. The "Send to configuration" way of getting the same collection of packages onto another machine is a bit unintuitive (both in naming, not being selectable without selecting packages first, and its file menu locations) and cumbersome if all you want to do is to select the same pacakage names in the VIPM list on another machine and install them. (The save/apply configuration function also seems to fail frequently; complaining about not being applied to the same version of LabVIEW, failing to include packages (even if you have set it to not include them(!), AND refusing to apply what it can when there is an issue with just some of the package sin the configuration...) Why not also have a way to just copy a selection, then paste to get the same packages selected on another machine? Ctrl+C is already a Copy Package Names option, but there is no Paste Package Names...
  6. Hi @Jim Kring 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 ☹️
  7. This was on a machine with only one version of LabVIEW/RIO ever installed on it - 2020.
  8. 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...?
  9. 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?
  10. 4.2.0b1 is a beta that was put on lavag.org, it has support for Linux RT targets that the previous one did not, unfortunately there is no official release with that functionality yet.The package had a slightly different name as well, which confuses VIPM a bit when trying to uninstall. See the discussion here: https://lavag.org/topic/21142-openg-zip-42/page/2/
  11. The error log shows an authentication issue for the server, so probably a certificate that needs to be updated or something? By temporarily accepting this in our firewall we got through...Should definitely be fixed on the server side though, with all LabVIEW 2020 users trying to use it and most of them probably having firewalls blocking the process. =========== START of VIPM 2020.0.0 (build 2302) Error Message =========== An internal VIPM 2020.0.0 (build 2302) Error has occured on: tirsdag juni 23, 2020 at 03:50:11 p.m. = Automated Message Start = Error 363507 occurred at 487489412C8DC88F1BC985B0C2BD11EC:600004 Possible reason(s): LabVIEW: (Hex 0x58BF3) LabVIEW could not verify the authenticity of the server. Complete call chain: 487489412C8DC88F1BC985B0C2BD11EC:600004 JKI_API.lvclass:LogIn_Parse_API.vi MainUI.vi 3DDDEADAB56AD7591191154923B491E0 VIPM Main Window.vi = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 3DDDEADAB56AD7591191154923B491E0-> MainUI.vi = Error Handler Call Chain End = =========== END of VIPM 2020.0.0 (build 2302) Error Message ===========
  12. I have the same problem now, irritating as hell. Having paying customers is of course the optimal for JKI, but it still seems silly to chase everyone over to alternative solutions. It is the adoption rate after all that makes the platform interesting for package publishers. And now that we are all forced to register to download even the open source projects proper logon functionality has become critical. Please support every user, and fix the connection issues.
  13. Regarding the issue of the not-working account I guess the reason was that VIPM does not accept accounts created here in the discussion forum, nor during previous VIPM free-installs(!?)? When trying to reset the password I did not get any feedback that the e-mail was not recognised, but no password reset response arrived.
  14. There seems to be an issue using VIPM without a sign-in. Starting VIPM 2020 after installing LabVIEW 2020 I chose the free edition and opted not to sign in (as I could not get my user account password, even though I tried with an e-mail address that I verified as used by JKI earlier...a side-issue?) - after doing so VIPM would show the splash screen, close that, but then just sit dead in the background not displaying anything... I tried this repeatedly, eventually manually removing the programdata folder (note that the software happened to be running at the time without me knowing it, and then did not handle the fact that it had files missing there - ending up in an infinite file error loop) and uninstalling-reinstalling it with no effect. The only fix I found was to remove it (and the programdata) again, to get back to the version-selection dialog, and then sign-in with a new account.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.