Jump to content

Ashish

JKI Team
  • Content Count

    289
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. Steven, I will recommend you to contact TortoiseSVN Support (http://tortoisesvn.net/support.html). This forum is primarily for JKI Products (jki.net/products).
  2. Please try to mass compile the source before building the package. Let me know how it goes.
  3. Please try to uninstall the package, restart PC and install the package again. The fact that you installed LabVIEW 2010 and 2012 after the installation might be the cause of this issue.
  4. No worries. Thanks for providing all your observations.
  5. I was not able to reproduce the behavior. Attached is the screenshot of all the versions as stated in the package i.e for LabVIEW 2009 to LabVIEW 2013 Not sure why is the issue? Try with "Run as administrator" option that you get from right mouse click.
  6. 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 Let me know how it goes.
  7. Thomas, Ok. So, you are concerned about the top level VI searching for VIs after package installation and you are thinking that it will possibly link to wrong VIs. Typically VIPM should mass compile after package installation in order to ensure that the newly installed package is linked correctly. Do you see "mass compiling" in the VIPM status bar at the bottom during package installation?
  8. What I understand is: after installation, the Top Level VI links to the newly installed VIs under vilib and provides warning about the new linkage. Is that correct? Also, it seems that building 2 packages is also linking correctly to the installed VIs under "..\..\..\..\..\..\MyProject.." Can you help clarify the issue?
  9. Try to open VIPM from LabVIEW(Under Tools from menu bar and select VI Package Manager) and again follow the steps to make VIPM communicate with LabVIEW. Let me know how it goes.
  10. Chris, You can do this by adding your packages as "Dependencies" while building the package. You can simply drag drop the packages as dependencies in VI Package Builder. More information is available in Help menu.
  11. Bob, Sorry for the delay in getting back to you. Please try following methods: Try to turn OFF your Antivirus and Firewall? Try to run VIPM from home network to see if it launches. There is possibility that if you are behind a firewall, VIPM fails to launch. Please try to launch VIPM using IT administrator login to see if that helps. Send the crash log: http://support.jki.net/entries/20634136-How-to-submit-VIPM-Troubleshooting-Logs 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.
  12. Jürgen, Have you found a solution yet? I can see from the screenshot that you are using LabVIEW 2014. Is it a 32 bit or 64 bit? Also what is the OS type and bitness? Anything special about this PC that you would like to share with us to help resolve the issue?
  13. Hi, Thanks for summarizing your experience. You can see how to configure the firewall and add VIPM to the exception list. Let me know how it goes.
  14. Can you try to install with "Run As Administrator" privileges (right mouse click option)?
  15. Did you select the correct OS bit version while building the package? https://di0skkm50b972.cloudfront.net/files/54112a85b1fa09d470000001/1c64e7ec8a8f3a625208342f47fae2b2ac79af06-e40e8e634e82fcec551598ed164aae3b7d75cd0e/vipb.png
  16. Philip, What version of VIPM are you using? Also, see of this article helps: http://support.jki.net/entries/21234937-VIPM-installation-error-on-Mac-OSX-10-7-
  17. The information provided in the article has always worked for the users experiencing the issue with VIPM not connecting to LabVIEW. Not sure whys is it not working for you.
  18. Hi, Have you tried to "Run As Administrator" using right mouse click option?
  19. Peter, Thanks for documenting your observations and the fix. I will pass on the information to the team for consideration.
  20. Jürgen, Have you referred to this article: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  21. 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?
  22. Thanks for the updates and recording the details of your observations. It will help us and others experiencing similar behavior.
×
×
  • Create New...

Important Information

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