LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

An error occurred while upgrading from package 'ni-ssp-notifier (19.0.0.49152-0+f0)' to 'ni-ssp-notifier (20.6.0.49152-0+f0)'.

 

Hi,

 

I've been receiving this error while trying to install the "Academic Volume" version of Labview 2021.

There are other similar and related posts for this issue. Following the proposed troubleshooting steps,

I have checked that full-access is given to the "temp" folder in "%appdata%".

I have completely uninstalled, then reinstalled LabView and NI programs.

I have tried to install with the offline package.

 

One user said that the problem could only be fixed with a clean install of Win10. I'd prefer to avoid that if possible...


I've discovered that a similar error is thrown up if I attempt to remove "NI license manager" through the "NI package manager" app. There seems to be some issue with 'ni-ssp-notifier'. As a bypass, is it possible that this particular package can be manually updated to the correct version?

 

I've had Labview on this computer before. And, it has installed fine without issues. I ended up removing NI programs later when I discovered that it seemed to interfere and turn off my wireless adapter occasionally. My adapter is an Intel(R) Dual Band Wireless-AC 8265. And, the issue would appear after the computer was awakened from sleep-mode. The adapter would be turned off with no way to turn it back on again without restarting. After the removal of NI programs, this issue went away entirely.

 

So, I'm wondering if there's some interference due to this not being my first installation of LabView and NI programs on this computer... I'd like to be able to have LabView on this computer because it's a laptop and portable. And, for the purposes of interfacing with laboratory-hardware, I can easily move it where needed.

 

Kind regards,

Allison

 

 

 

Screenshot of the error:

Allisonh_0-1666807739362.png

 

Screenshot of the version of Labview:

Allisonh_1-1666807819819.png

 

Error message:

An error occurred while upgrading from package 'ni-ssp-notifier (19.0.0.49152-0+f0)' to 'ni-ssp-notifier (20.6.0.49152-0+f0)'.

Additional error information:
An error occurred while running the custom execute queue 'pre'.

 

 

0 Kudos
Message 1 of 10
(1,968 Views)

Hello 我也遇到了同样的问题,请问你解决了没有?

0 Kudos
Message 2 of 10
(1,872 Views)

Installing LabVIEW can be difficult, particularly if more than one Version of LabVIEW is involved.  Removing (or uninstalling) LabVIEW can be simple, but attempts to "force" an uninstall, particularly trying to do anything with the Windows Registry, will probably require that you re-install Windows 10 (and all of your other programs and data).  I've encountered such "forced uninstalls", and have not been able to "repair" the damage except by "starting over" and reinstalling Windows.

 

Bob Schor

0 Kudos
Message 3 of 10
(1,853 Views)

have you found the solution besides doing a full reinstall? This whole situation is horrible and I can find no helpful solution aid or guide from the NI forums, they all seem like dead ends. 

0 Kudos
Message 4 of 10
(385 Views)

@hectorramzla wrote:

have you found the solution besides doing a full reinstall? This whole situation is horrible and I can find no helpful solution aid or guide from the NI forums, they all seem like dead ends. 


I see such errors more and more often, the overall complexity of the software continuously increases, and something is "out if control" by NI.

For example, last week in attempt to install LabVIEW 2025 Q1 got this one:

Screenshot 2025-02-03 12.12.23.png

It is not exactly the same error like yours, but very similar.

 

What I do usually is one following attempt (sometimes this trick works, sometimes not).

First, on the install DVD locate this package. In your case it will be something like ni-ssp-notifier_20.6.0.49152-0+f0_windows_all.nipkg.

This is ZIP file in general. Just copy it to the PC, then rename to *.zip, then unpack.

You will see some *tar.gz archives, unpack these as well (I would like to recommend 7zip software), the goal is to extract *.msi installer.

Once *.msi extracted, then install it as usually, in my case looks like this:

Screenshot 2025-02-03 12.17.57.png

et voilà:

Screenshot 2025-02-03 12.19.24.png

After that next install attempt usually OK. If not, then full reinstall will help. Sometimes installation directly from Package Manager instead of DVD is also helpful.

0 Kudos
Message 5 of 10
(376 Views)

I dont have a DVD sadly, we only got a code for our lab

0 Kudos
Message 6 of 10
(364 Views)

@hectorramzla wrote:

I dont have a DVD sadly, we only got a code for our lab


But you have *.iso image mounted as DVD or self-made installer, generated from LabVIEW project, this file should be somewhere on the installation media you have in your hands.

0 Kudos
Message 7 of 10
(341 Views)

im not sure what you are tlaking about, I installed it through the NI 2025 q3 package manager, do you know where it puts this iso image? note that in my issue, due to this ssp error I was never able to actually install lab view on my computer. 

0 Kudos
Message 8 of 10
(335 Views)

@hectorramzla wrote:

im not sure what you are tlaking about, I installed it through the NI 2025 q3 package manager, do you know where it puts this iso image? note that in my issue, due to this ssp error I was never able to actually install lab view on my computer. 


Sorry, sorry, sorry, if you installing this with Package Manager already, then it is not applicable, of course. You can try in theory download iso image from LabVIEW Downloads and try described workaround.

0 Kudos
Message 9 of 10
(329 Views)

I ended up having to do a windows reset. There's an option to reset while keeping personal and documents and files. After that, LabView installed without issue.

 

I've had this computer since 2018. LabView is the one program in particular that gives me some trouble. It actually turns off my wireless adapter card (unless I disable a very specific LV driver) and seems to break compatibility with some my other programs.

 

So, I tend to just install it on the lab desktops and use those computers specifically for hardware interface.

0 Kudos
Message 10 of 10
(315 Views)