Jump to content

Ashish

JKI Team
  • Content Count

    292
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. Gavin, Thanks for this piece of information. We had one user having issues after he began using SSD. He was using "Directory Junction". Are you?
  2. Thanks for the updates and recording the details of your observations. It will help us and others experiencing similar behavior.
  3. You can try that. For dedicated support, I will recommend to send email to support@jki.net.
  4. You might want to try to exclude the dependencies from compiling in VI Package Builder. http://screencast.com/t/ea0cGFVZEk
  5. Nelson, 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 help, please send the screenshot of the error message. What OS, LabVIEW and VIPM version are you using? Please try using Administrator privileges.
  6. sshiraishi, Can you send a sample XML file and your VI that can reproduce the behavior? You can send it on "support@jki.net".
  7. Priyadarshini, So, essentially you want to "update" the existing VIPC file instead of creating a new one from scratch. As per this article, the "Update VIPC" function is not yet available. http://support.jki.net/entries/21395113-VIPM-API
  8. Brian, Thanks for recording your observations. It will indeed help us and others.
  9. Scott, Thanks for detailed description of the problem. We have recorded the issue as Case 16350 for internal tracking and debugging to identify and fix the problem.
  10. James, Glad to know that you figured it out.
  11. Gavin, Your problem description is really never experienced by us. Especially when you mention that several attempts are needed installing a package. Have you experienced this on same PC? Have you tried using VIPM on other PC?
  12. I was not able to reproduce the error. I tried to create a simple Post Build VI that launches a dialog. I tried with VIPM 2014 Build 1944. Here is link to the latest VIPM Labs build that you can try: http://support.jki.net/entries/24071293-VIPM-Labs
  13. Priyadarshini, I was not able to reproduce the behavior. Are you running latest and greatest VIPM? If not, please try the latest VIPM (jki.net/vipm).
  14. Olivier, Yes. Please send us an email at support@jki.net to debug this.
  15. Olivier, I think you are talking about two different topics. 1. Older packages not installing in VIPM 2014 - How old are those packages? - VIPM 2014 does allow you to install packages built using older VIPM versions. Try mass compiling the source before building the package using VIPM 2014. - If that does not work, there might be some corner cases. Hence, I would like you to share the package source (send to support@jki.net) 2. Packages built with VIPM 2014 cannot be installed with older versions of VIPM - Yes. This is a known behavior. http://forums.jki.net/topic/2367-vipm-2014-migration-issue/ - Contact us on support@jki.net to understand the case and provide a solution
  16. Thanks for updating the response. It will be good resource for reference.
  17. Do you have a project containing all the source files in it?
  18. It might be due to the internet unavailability to VIPM. Have you installed any other available packages before? Try from another network.
  19. Did you try mass compile of the source before building the package?
  20. We have recorded the issue as Case 16100 and will be fixed in the future release of VIPM API. For the time being, you can rename the VIPB file as ".vipb" (remove the file name) and VIPM API should work as expected. Let me know how it goes.
  21. Beutlich, Please refer this article: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW See if this article helps: http://support.jki.net/entries/20634111-Fixing-your-available-LabVIEW-version-list
  22. TonP, We were not able to reproduce the exact issue but do see some discrepancy which is not allowing us to install the package. We are investigating this and will get back to you soon.
  23. Priyadarsini, Thanks for reporting your observations. I was able to reproduce the behavior and have recorded it as Case 16076 for consideration in future release of VIPM.
×
×
  • Create New...

Important Information

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