05-12-2021 11:14 AM
So, I'm trying to install VIPM through NIPM and get the stupid message mentioned in the subject. After two days of trying to figure it out, I finally believe I know the cause: I already have that version installed, but it was installed directly when I got a popup to update VIPM to 2020 and finally said "yes".
I guess this installed VIPM 2020 without telling NIPM what I did. That's fine, but why couldn't NIPM tell me that the install failed because the same version (or newer) was installed??? It's not some obscure error that they never thought would happen; I'd rather think that this would be one of the most common errors that could occur. Instead, I get the stupid generic error.
NI, could you please put a little more effort into this critical piece of software?
05-13-2021 07:28 AM
Yeah the error is a red herring. It says things like the checksum doesn't match, or that the download is bad. But as demonstrated multiple times this error is just a catch all for "I couldn't install it". I've seen that error when a stick of RAM was bad in the PC, and as you mentioned here, when a version of VIPM is newer, or the same as it is trying to install. Quite frustrating. The fix is easy and that is to uninstall VIPM, then install the NIPM package of VIPM. Of course figuring that out takes time.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
05-13-2021 08:08 AM
@Hooovahh wrote:
Yeah the error is a red herring. It says things like the checksum doesn't match, or that the download is bad. But as demonstrated multiple times this error is just a catch all for "I couldn't install it". I've seen that error when a stick of RAM was bad in the PC, and as you mentioned here, when a version of VIPM is newer, or the same as it is trying to install. Quite frustrating. The fix is easy and that is to uninstall VIPM, then install the NIPM package of VIPM. Of course figuring that out takes time.
Yes, it is frustrating. I just wish they would put a little more effort into such a critical piece of software. I mean, if you want to get nitty-gritty, I don't even think that "internet connections" are responsible for most install issues, so they didn't even choose a reasonable default message. I guess their ego is too big to admit "we don't know what happened". 😄
05-20-2021 05:43 AM
@billko wrote:
I guess their ego is too big to admit "we don't know what happened". 😄
They should go with a funny message, like google's monkey error message, that way the sting of failure would at least make you feel better.
07-16-2021 01:29 PM
To follow up on the generic error message mentioned above, NI Package Manager 21.0 just released and will display a lower-level error message to a user when available instead of the generic suggestion to "please check your internet connection". We have left the "Try Again" button in case the user want to do that. Hopefully this will help when debugging errors returned when installing a package.
Ref: See bug number 148740 in NI Package Manager 21.0 Bugs Fixed.