Ashish

Hi, Can you try to install VIPM with "Run As Administrator" option. Here is an article that explains how to do it for launching VIPM. But, you can use same process while installing VIPM. But, before that, make sure you remove all files related to VIPM from Program Files(x86) and Program Data folder.

Ian, Certainly a useful feature for some user. But, it possibly did not make it to the list of improvements during VIPM updates. I will suggest to add your opinion on the Idea Exchange for making it visible to the responsible folks.

Ruslan, I will suggest to leverage VIPM's capability. Refer this link: https://support.jki.net/hc/en-us/articles/214135803-How-do-I-transfer-packages-with-VIPM-to-a-non-networked-computer-

Hi, Sorry for the delay in getting back to you. I was struggling on why VIPM was opening LabVIEW 2016 when I had selected LabVIEW 2014 in VI Package Builder. I later figured that the VIs are compiled in LabVIEW 2016. No wonder, VIPM was trying to do its best to build the package. Can you confirm the LabVIEW and VIPM version to test?

@Nik and @Parth I would like you to install VIPM with administrator permissions as mentioned in this article: https://support.jki.net/hc/en-us/articles/214135583-VIPM-installation-error-on-Mac-OSX-10-7- Although the article is not related to this specific issue, it explains how to set permissions during VIPM installation. Let me know how it goes.

Great! It was indeed one of the fixes implemented in VIPM 2017 SP1. Thanks for confirmation and glad to know that you were able to build the package successfully.

Hi !! Apologies for missing out on these. We were able to reproduce the behaviour and have recorded as Case 17570 for VIPM team to take a look at. I will get back to you when there are more updates on this.

aputman, Thanks for summarizing your observations and the solution that helped leverage JKI State Machine architecture to meet your needs. As drjdpowell pointed out, there are certain tradeoffs as well. So, it all depends on the use case. Certainly, your suggestions will be useful for many JKI State Machine users in similar situation.

dbrown78, Please try VIPM reinstall.

Jed, That is great news and good information for us for reference.

Jed, Openg is downloaded from sourceforge, whereas the ni server used for the other packages. NI server is commonly not blocked. But, chances are that sourceforge is blocked. Please check with your IT department to unblock Sourceforge.

Jed, We have experienced this issue when the source location of the package is blocked on your network. Please check if you can identify the source of the package and get it unblocked by the network admin.

Mike, We want you to try to re-install VIPM. To do this you will have to uninstall VIPM using the VIPM uninstall and then delete the following folders manually: C:\ProgramData\JKI\VIPM C:\Program Files (x86)\JKI\VI Package Manager Then re-install VIPM. If that does not fix the problem, try re-installing LV2009 32bit (Full) Run Time Engine: http://forums.jki.net/topic/1430-where-do-i-get-the-labview-2009-run-time-engine/ Let me know what happens. - Ashish