Jump to content


JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Ashish

  1. Another VIPM user has experienced that installting .NET Framework 4.0 solved the problem with VIPM crashing. (http://forums.jki.net/topic/2065-crash-on-startup/page__view__findpost__p__5078) Here is link to download .NET Framework 4.0: http://www.microsoft.com/en-us/download/details.aspx?id=17851 Let me know if that helps anyone.
  2. Steve, Thanks for the information. It will help in our investigation.
  3. flarn2006, What is your OS and other PC parameters? Was VIPM ever working for you before? Please provide some screenshots if possible.
  4. qbits, Glad to know that you are good to go. Also, thanks for the information. It will help us debug the issue.
  5. RocketHacker, We have recorded your observation as Case 13874 for consideration in our next release of VIPM.
  6. qbits, I am unable to recreate the behavior on my 64 bit Windows 7 virtual machine. I have LabVIEW 2012 (32 and 64 bit) and installed VIPM 2012.0.1 (build 1818). It launches successfully. Here is the screenshot: http://screencast.com/t/gCODbPuHBA VIPM launched successfully from no-admin account as well. While I am still investigating, let me know if you find anything that I can try.
  7. qbits, Thanks for your observations. We will try to reproduce it and let you know.
  8. One of the VIPM users got this problem fixed by reinstalling NI Device Drivers for LabVIEW 2012. If possible, please try that out and let us know if it helps you as well.
  9. Here is an article that is made for Mac users but is valid for anu other OS platform as well: http://support.jki.net/entries/21888011-connecting-vipm-mac-to-labview
  10. Nina, Better place for such questions is http://lavag.org/
  11. Becky, Using VIPM 2012.0.1 (build 1818), I was not able to recreate the behavior described by you. Here is how I tested it: 1. Build package. Do not publish. 2. Install the package 3. Update and build package. Publish the package. 4. Refresh repository to check for new packages. This shows that the new version of the installed package (in step 2) is available 5. Install the upgrade Any more details to recreate the behavior will be helpful.
  12. Bjarne, This capability is not yet available in VIPM.
  13. We have recorded this issue as Case 13848 for consideration in future release of VIPM. Thank you.
  14. TonP, Can you try "Remove all versions from library..." and try to install the package again? If that does not work, can you share the package so that I can give it a try on my PC? For some reason, I am not able to download the package from LAVA website. http://lavag.org/files/file/206-mercurial-provider/
  15. TonP, Thanks for your feedback. I have added Case 13823 (Item 1) and Case 13824 (Item 2) for consideration in future VIPM release.
  16. The error dialog does indicate that the virus scanner on your PC, Bitdefender, has blocked VIPM from accessing the internet So, you will have to make sure that VIPM gets access to internet. Here is an article to help you: http://support.jki.net/entries/20589198-solving-vipm-network-connection-issues
  17. Do you see LabVIEW 2011 in the "LabVIEW versions list" in VIPM 2012? If not, here is an article on how to fix it: http://support.jki.net/entries/20634111-fixing-your-available-labview-version-list
  18. If you scroll down in VI Server dialog, you will see settings to add localhost as shown in the screenshot at this link: http://screencast.com/t/rgNU6KdS
  19. I was able to successfully install the package on my Win 7 32 bit with LV2012. We have seen some customers getting "input parameter invalid" error message related with firewall blocking VIPM access to internet. Have you referred to this article: http://support.jki.net/entries/20589198-solving-vipm-network-connection-issues
  20. Please create a support ticket to get dedicated support. Here is the link: http://jki.net/contact
  21. Ton, I was able to recreate the issue and have filed the case (Case 13783) for internal review. Thanks for reporting your observations.
  22. Ton, Now I know what you mean. I was able to recreate the behavior described by you and have submitted the issue (Case 13780) for review by VIPM team. Thanks for recording your observations. I was curious about your non-standard LabVIEW folders for multiple LabVIEW versions. I have multiple LabVIEW versions on my PC as well and I did let it install the components in the default locations. Am I missing anything?
  23. Ton, I was not able to recreate the behavior you are describing. If possible, can you record the screen video and send me the link?
  24. Ton, I was able to configure the package and deploy it under the Glyphs folder. Here is the screenshot of my Destination configuration in VI Package Builder: http://screencast.com/t/ut6ZKWjsW Here is how the LabVIEW Icon Editor Glyphs interface looks after the package is deployed: http://screencast.com/t/Ae4p9IDDaK I hope this helps.
  • Create New...

Important Information

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