Jump to content

Ashish

JKI Team
  • Content Count

    292
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. It might be related to the permissions to the installer for deleting temp file. See what happens if you run the installer as Administrator (right mouse click and select "Run As Administrator". Let me know how it goes.
  2. Thanks for recording your observations. Yes, it will be a real value to get more inputs on how to reproduce it. It will only help us to speed up the investigation and resolution in future build of VIPM. Take some screenshots if you feel necessary to convey the information.
  3. gad_z00ks, Sure. I see your thought process. VIPM is a mechanism to distribute packages. I will recommend you to contact package developer company. The information should be available in VIPM.
  4. Peter, You can use the "Format Date/Time String" function to build the desired UTC format string and then use EasyXML to generate the XML string. See attached snippet for reference. Here is the time format string I created: %Y-%m-%dT%H:%M:%S%3uZ
  5. gad_z00ks, The JKI Discussion Forum is primarily for JKI Products (www.jki.net/products). I will recommend you to ask for help on NI Discussion Forum or LAVA (http://lavausergroup.org/)
  6. Peter, You can easily convert the timestamp in UTC xml string by using "Easy Write XML File" function. Just wire the timestamp and destination file path to it.
  7. Priyadarshini, I will recommend you to reinstall VIPM and see if that helps.
  8. I tried to recreate the behavior and I think I know the issue. On this specific PC, the VIPC file are associated with LVTN and not "VIPM File Handler.exe". Hence, trying to open VIPC launches LVTN. Try this: - Right click VIPC File - Go to Properties - Click "Change" - Click on "Browse" button at the bottom right corner - Go to: C:\Program Files\JKI\VI Package Manager\support and select "VIPM File Handler.exe" - Click "Open" - Click "OK" - Click "OK" on the Properties dialog to apply and close the dialog Now try to double click on VIPM file and check to make sure it opens correctly.
  9. Priyadarshini, Can you send the attachments?
  10. Priyadarsini, We have never experience this before. So, what happens when you double click VIPM shortcut on the PC? Does it open VIPM or LVTN?
  11. shruthibs, Try the attached control for your XML file. Control 1.ctl
  12. Mike, We have recorded the issue as Case 15964 for consideration to be fixed in future release of VIPM. In the mean time, please use the workaround mentioned. We will certainly notify you when we have the fix ready.
  13. Mike, I was unable to recreate the behavior described by you using my test package. Can you share the packages source? If not, can you create the test package that recreates the behavior and share with us? You can send that info to us on "support@jki.net" to continue this discussion.
  14. Please contact us at support@jki.net for further assistance on this issue.
  15. It is indeed as simple as it sounds. Refer this article: http://support.jki.net/entries/20625761-How-do-I-transfer-packages-with-VIPM-to-a-non-networked-computer-
  16. We had some users experience similar issues with some special processors. I am wondering if your CPU is one of that kind.
  17. What kind of processor do you have on your PC? Also, please provide the PC, OS, LabVIEW specs (along with the bitness info 32bit/64bit).
  18. Please send us an email on "support@jki.net" for more dedicated help in solving this issue.
  19. Try running VIPM with "Run As Administrator" privileges as described in this link: http://support.jki.net/entries/21430776-VIPM-fails-to-launch-after-splash-screen-on-Windows
  20. Please try the following. 1. Click Start in windows. Type: "allow a program through windows firewall" then select it. 2. See attached image. Make sure LabVIEW 2012 and VIPM are added to this list and are allowed to communicate through the windows firewall. 3. Try the connection to LabVIEW from VIPM to see if this works.
  21. Can you send screenshot of "VIPM port list configuration"? Also, disable your firewall, antivirus and try again.
  22. Hi, Please refer this article and see if you missed anything: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW
  23. Bob, Glad to know that you got it resolved. Also, apologies for not getting back to you sooner. Also, thanks for the information. It will be great if you share more details of the things you tweaked. Other Surface users will be benefited from your experience.
  24. We have recorded the issue as Case 15502 for consideration to be fixed in future release of VIPM.
×
×
  • Create New...

Important Information

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