LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

installing problem

Solved!
Go to solution

I was terminating the NIOfflineHelpViewer.exe process through Task Manager. Terminating it through the mentioned solution (command prompt) did the trick. Thanks.

0 Kudos
Message 21 of 28
(501 Views)

NI requests your log files to help diagnose the issue with the offline help viewer installation. They are located at C:\Users\<username>\AppData\Roaming\ni-offline-help-viewer\logs

 

We are currently tracking this issue with Bug 2090695.


Christina Rogers
Principal Product Owner, LabVIEW R&D
Message 22 of 28
(396 Views)

Same here, I just installed on a user PC in our company (I'm the IT) it got stuck the first time and now nothing works (even the License Manager says that there is the license but LabView says no).

Now the installation is broken and won't go past the first step (offline help viewer), if I try to kill the process this error come out.

 

The user already have 2022 version but we never had any issue with older version being installed (we had a pc with 2018, 2022 and 2024 installed all working fine).

 

Now I need to reinstall both on user PC starting from scratch (= uninstall and fully removing folders and registry keys that are left).

0 Kudos
Message 23 of 28
(279 Views)

@Baboo85 wrote:

Now I need to reinstall both on user PC starting from scratch (= uninstall and fully removing folders and registry keys that are left).


Do not do that!  Use NIPM to remove all installed LabVIEW software (be sure that the "Products Only" is not checked).  Once only NIPM is left, go ahead and delete that, as well.

 

DO NOT TOUCH THE REGISTRY!  I've done this (twice!), and ended up reformatting the C: drive, reinstalling Windows, Apps, and (fortunately) my backed-up Profile.  Deleting Folders can be done safely, but is probably not necessary, as you'll "overwrite" the contents of those folders when you re-install.

 

Bob Schor

Message 24 of 28
(266 Views)

Always did and will do, never had any problem. Did this also for Adobe that we had a strange error during a failed update and the solution was delete everything after the uninstallation. Folders and key registry.

 

You need to check what you're deleting obviously. One of our internal solution I found during a failed LabView 2022 installation ("Unable to load MIFSystemUtility DLL") is to just delete 2 registry keys then install again, and works like a charm ("HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\MIF" and "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\Common\Installer\MIF")

 

I use the windows registry since 1995 when I had my first Windows, never had a problem.

 

If you want to reinstall from scratch as if you didn't ever installed anything, you need to do this. If you're unsure on what you're doing, use a "install sniffer" that trace every modification (file and folders created, new registry keys) done on the PC. Discard the ones that don't relate to the software you're installing and voila'.

 

If you still not sure or you had problem like you said, just don't do it. It's better avoid to do something you're not sure to.
Or use a Virtual Machine to do some tests before doing it (I'm doing that too, don't think I'll go directly with experiments to user PC, I try first on mine and on VM if I'm doing it the first time).

In fact I'll use one VM now to test the installation of both 2022 and 2025 to check if maybe the procedure we're using have some flaw (I don't think so, we just select 4 plugin and that's it, but anything could be), the complete uninstall (with folders and reg key deletion of course) and reinstall.

0 Kudos
Message 25 of 28
(253 Views)

@Christina_R wrote:

NI requests your log files to help diagnose the issue with the offline help viewer installation. They are located at C:\Users\<username>\AppData\Roaming\ni-offline-help-viewer\logs

 

We are currently tracking this issue with Bug 2090695.


We're now tracking the issue where the NI Offline Help Viewer hangs the LabVIEW installer with Bug 3140514.

 

The problem seems to be with the offline.sqlite file, and a possible workaround is to delete it before running the installer. The file is located in C:\ProgramData\National Instruments\Offline Help Viewer\database-orm


Christina Rogers
Principal Product Owner, LabVIEW R&D
0 Kudos
Message 26 of 28
(239 Views)

@Bob_Schor  a écrit :

I have been installing LabVIEW (for myself, my colleagues and students, and generally several times for every version of LabVIEW) and it has become more and more difficult.  I had procedures that included "Install only a few features at a time, going through at least three "installation Loops", with Drivers always last, to "Do it all at once".  I find that after LabVIEW 2016, installation took a big jump in difficulty (coinciding with the introduction of NIPM), with another jump in difficulty with LabVIEW 2020, and culminating with LabVIEW 2022 (and the confusing "version-less" morass we now find ourselves with "continuous versioning".

 

Is there a compelling reason to install the "latest" version of LabVIEW?  If not, I will say that I've successfully installed "minimal" LabVIEW 2021 systems (by "minimal", I mean only the toolkits, modules, drivers, and "Additional Features" that I am certain I need).

 

Bob Schor


Genuinely so hard, IT has given up with installing Labview when needed, that I'm the one doing it because it's faster anyway (compared to giving them the list of drivers and add-ons and so on and in the end they just enter the admin password while I do the rest)

0 Kudos
Message 27 of 28
(215 Views)

I had an ongoing installation where I had killed the task SO many times.  Once I deleted the file in C:\ProgramData\National Instruments\Offline Help Viewer\database-orm the installer continued even when the process relaunched and I did not kill it anymore. eventually the installer finished with the offline help and moved on to other modules in the install list.

 

-> Deleting that offline.sqlite seems to fix it for me, much better than constantly killing tasks that the installer keeps spawning!

Message 28 of 28
(82 Views)