Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Goku25, Try launching VIPM with "Run As Administrator" settings that you get by RightMouseClick or Shift+RightMouseClick.
  2. Had you worked with earlier version of VIPM successfully or is this the very first time?
  3. @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.
  4. Walter, If ain't broken, don't fix it. :) But if you face the problem in future, try adding machine name and ip address.
  5. Please refer this article and let us know if it helps: https://support.jki.net/hc/en-us/articles/214135683-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  6. Johan, It sounds like some permissions issue. Try reinstalling VIPM with "Run As Administrator" settings that you get by RightMouseClick or Shift+RightMouseClick while launching VIPM Installer.
  7. Thanks for providing the error message. It appears to be a permissions issue. I will suggest to uninstall VIPM and Reinstall. But, this time while reinstalling, I want you to RightMouseClick or Shift+RightMouseClick on VIPM Installer and select "Run As Administrator" option. Let me know how it goes.
  8. @Waleed El-Badry I will suggest you to look at examples that ship with EasyXML Toolkit. Especially, the one called "Write and Read XML File.vi". You can access examples from VIPM by opening the EasyXML Toolkit Package Information and clicking on "Show Examples" button as shown below:
  9. Location of Error file ==> C:\ProgramData\JKI\VIPM\error The ProgramData folder may be hidden. Watch this video which shows how to make this folder visible:
  10. @Thoric We have recorded this issue as Case 17869 in our internal bug tracking tool.
  11. Have you referred to this article that shows how to Install and Run VIPM with Run As Administrator Mode: https://support.jki.net/hc/en-us/articles/214135663-VIPM-fails-to-launch-after-splash-screen-on-Windows Also, if problem persists, refer this article to check the VIPM Troubleshooting logs: https://support.jki.net/hc/en-us/articles/214135523-How-to-submit-VIPM-Troubleshooting-Logs
  12. I believe that you are referring to this article already to Transfer Packages to Non-Network Computer Here are the options Get VIPM on the network PC with help from IT folks OR Get temporary internet connection to the non-network PC OR Download in personal PC and then transfer to non-network PC
  13. 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.
  14. 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.
  15. 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
  16. 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.
  17. 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.
  18. James, Glad to know that you got it resolved and thanks for the details that helped you resolve the issue.
  19. 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
  20. 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!!
  21. 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?
  22. > 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.
  23. No. That should be fine. You need just the Run Time Engine for LabVIEW 2013 and not the full development software.
  24. VIPM 2014 needs LabVIEW 2013 Run Time Engine. You can download and install the LabVIEW 2013 Run Time Engine separately from NI website.
  25. 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).
  • Create New...

Important Information

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