Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. We have recorded the issue as Case 15502 for consideration to be fixed in future release of VIPM.
  2. 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.
  3. I will recommend to submit your ideas to us. http://ideas.jki.net/
  4. It will be great if you can share the package source. Send it to support@jki.net.
  5. You can automate VIPM tasks using VIPM API functions. Here is the reference link: http://support.jki.net/entries/21395113-VIPM-API
  6. 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.
  7. Refer this article that discusses permissions to be set for VIPM installation on Mac: http://support.jki.net/entries/21234937-VIPM-installation-error-on-Mac-OSX-10-7-
  8. Scott, Thanks for the information. Please send an email to "support@jki,net" with the details from your previous post. We will diagnose the issue and will be able to provide dedicated support.
  9. Scott, Please see if this article helps you: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  10. sth, The ports entry in the settings.ini is not corrupt. That is the way VIPM manages port information for multiple LabVIEW versions on the same PC. After recreating the settings file, you wmight have to reconnect VIPM to all the installed LabVIEW versions. But, did that resolve the original issue? If not, please try to run the VIPM with "Run As Administrator" option from right mouse click.
  11. heel, Sorry for the delay in getting back to you. Also, thanks a lot for compiling the information to reproduce the behavior. I was able to reproduce the behavior described by you. We have recorded the issue as Case 15317 for us to be able to address in future release of VIPM. We will notify you when it gets fixed.
  12. Ok. Have you tried to click "No" when you get the dialog. For some reason, windows task scheduler did not get set properly. If you want, you can download the latest version of VIPM from www.jki.net/vipm/download
  13. lolo, The task is only to allow checking for VIPM updates. The VIPM should launch and function successfully after installation.
  14. Did you had a chance to look at this article: http://support.jki.net/entries/21395113-VIPM-API
  15. One of the customer experiencing similar issue figured that the possible reason might be related to the firewall blocking the source website from where the requested package is to be downloaded. In his case, it was the OpenG package that was being downloaded from Sourceforge and the firewall was blocking it. Certainly, the message on VIPM dialog is not accurate and we have logged it as a item to e fixed in future release of VIPM.
  16. DukeGriffin, The best thing for you will be to get VIPM Pro. Are you aware of Cybermonday 2013 sale going on for VIPM Pro? The deal expires this Friday. http://blog.jki.net/news/cyber-monday-2013-get-50-off-vipm-pro/
  17. Make sure that VIPM is connected to LabVIEW. Refer this article: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  18. Refer this link to make sure the settings are correct: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  19. cmal, I was able to recreate the issue and have logged it as Case 15065 for consideration in future VIPM release. Thanks for reporting the issue.
  20. I tried to recreate the behavior with a dummy package. The package built and install successfully as expected. http://screencast.com/t/f2iPblbIvw Is that what you get as well?
  21. John, You will have to install LabVIEW 2010 in order to be able to build VI Package. Once you install LabVIEW 2010, it will show up in VIPM list as well. Her is link to the VIPM Guide: http://support.jki.net/entries/20639971-VI-Package-Building-Guide
  22. Moritz, Please refer to the article again. I have added link to the VIPM Labs that contains newest VIPM builds which solved the issue. Let me know how it goes.
  23. Moritz, Refer this article: http://support.jki.net/entries/21430776-VIPM-fails-to-launch-after-splash-screen-on-Windows
  • Create New...

Important Information

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