Showing results for 
Search instead for 
Did you mean: 

NI Package Manager Ignores Dependency

Go to solution

I have created an application with LV 2016 that only depends on the run time engine. When I install the application through a package in NI Package Manager, it makes no attempt to install the RTE. I can then run my application and get the error that the run time engine needs to be installed. The dependencies tab for my package is shown below, does anyone have suggestions?


forum post nipm dependencies.PNG

0 Kudos
Message 1 of 18

Hello Gregory J,


Could you clarify, the NI Package Manager does not install the RTE?


As a work around, you can install the LabVIEW 2016 RTE directly from National Instruments' website. 


Let us know how if that solves the issue!



Michael Pahl

0 Kudos
Message 2 of 18

Correct, it does not install the runtime engine. 

Sure, there are half a dozen ways to install the runtime engine, what I want is for NIPM to install it when it sees it as a dependency.

0 Kudos
Message 3 of 18

Which version of NIPM  and operating system are you currently using?

0 Kudos
Message 4 of 18

I am using Windows 10 with NIPM 18.0.2 on both the development and target PCs. I created the package using LV 2016 with the package builder add on.

0 Kudos
Message 5 of 18

Shot in the dark, but is this computer connected to the network, where it has a feed that can supply the dependent package?  I remember hearing about a limitation with NIPM at one time where if a dependency couldn't be found.  Not sure if that is still the case.

0 Kudos
Message 6 of 18



Interesting, in the post you linked the application doesn't install, but in my case the application does install just not with the RTE so I can't run the application. The computer is connected to the internet and our network.


I can manually install the RTE in NIPM by going to Browse Products >> Programming Environments >> LabVIEW Run-Time Engine, but I don't know if that means it is in the "ni-package-manager-released" feed that comes registered with NIPM. 

0 Kudos
Message 7 of 18



It seems that in the other post, the issue was that the LabVIEW RT was not installed even though it was a dependency to another application that was installed. I would try posting in that discussion forum and see if the people who answered will be able to shed any more light on the issue.

0 Kudos
Message 8 of 18

Was the machine that you tested the installer on a fresh machine? Is it possible that the run-time engine is already installed? That's the only way I could see it installing without providing the installer. You should be able to see if the run-time engine is installed using the installed tab of NIPM.

Brandon Grey
Certified LabVIEW Architect

0 Kudos
Message 9 of 18

Hi Brandon,


The target machine did not have any NI software on it before I installed the package manager. The RTE is not installed, because when I try to run my installed application it throws an error message that it needs the RTE. If I manually install the RTE, then the application runs as expected, but of course I expect dependencies to be installed automatically as that is one of the greatest advantages of using a package manager.

Message 10 of 18