Jump to content


JKI Team
  • Content count

  • Joined

  • Last visited

  • Days Won


Ashish last won the day on July 8 2014

Ashish had the most liked content!

Community Reputation

4 Neutral

About Ashish

Profile Information

  • Gender
  1. 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.
  2. VIPM IDNet import tool failing...

    Ricardo, Sorry for such a late response. How did you manage to solve the issue? It appears that the toolkit provider should be able to help you.
  3. Apologies for extremely late response. I think this problem is solved for VIPM 2017 We tried with the code provided by you: https://www.screencast.com/t/Rq61BsNRG
  4. We had some other VIPM user having similar issue and here is what was discovered in this package source and the fix that solved the problem: ........ discovered a bad class library ownership relationship. Although one of my classes was directly placed within a lvlib, the class itself believed it was within a different lvlib, one that didn't even exist anymore. Despite this corruption, LabVIEW wasn't showing any errors, broken VIs or problems. I only discovered this when I started investigating one of the least well travelled routes with my code and saw some very odd behaviour with a DVR and an in-place structure on the class in question. .........resolving this class ownership issue appears to have resolved the problem in VIPM. I can only presume that the ownership corruption caused VIPM to get confused about which libraries to copy, open and close etc., or perhaps caused LabVIEW itself to fail to handle the libraries properly when closing the classes. Let me know if this helps or you have a different scenario.
  5. 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.
  6. Error 7 Installing Vi Probes

    James, Glad to know that you got it resolved and thanks for the details that helped you resolve the issue.
  7. Bob, Glad to know that "Run As Administrator" worked for you and you are now feeling better. Our apologies for the delay in getting back to you. Here is link to several support articles on VIPM: http://support.jki.net/forums
  8. VIPM - Any Future Updates?

    Hi, VIPM subscription renewal offers free upgrades along with dedicated support to ensure that you make the best of your purchase. VIPM Pro 2016 will be releasing soon. Stay tuned!!
  9. RDR, Was there any change in the OS, admin privileges, API version and operating environment? Also, for testing purpose, can we get access to repositories that you are using? Tools Network and another working repo?
  10. SubVIs In Pre/Post Install VIs

    > I have a dependency that says package A depends on package B. > does the order of an uninstall occur so that package A will be uninstalled before package B Yes, I believe that this is the intended/designed behavior.
  11. No. That should be fine. You need just the Run Time Engine for LabVIEW 2013 and not the full development software.
  12. VIPM 2014 needs LabVIEW 2013 Run Time Engine. You can download and install the LabVIEW 2013 Run Time Engine separately from NI website.
  13. Can you think of launching an executable post package install "Custom Action" that will take care of remaining activities (including re-launching LabVIEW, putting file at desired locations etc).
  14. Not sure if it is related but yes....VIPM connects to LabVIEW via VI Server. I wonder if LabVIEW reinstall/repair will help. Keep me posted on what solution NI provides for Desktop Execution Trace Toolkit.
  15. Hmm....thats odd. 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.

Important Information

By using this site, you agree to our Terms of Use.