Ashish

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.

Please contact us at support@jki.net for further assistance on this issue.

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-

We had some users experience similar issues with some special processors. I am wondering if your CPU is one of that kind.

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).

Please send us an email on "support@jki.net" for more dedicated help in solving this issue.

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

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.

Can you send screenshot of "VIPM port list configuration"? Also, disable your firewall, antivirus and try again.

Hi, Please refer this article and see if you missed anything: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW

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.

We have recorded the issue as Case 15502 for consideration to be fixed in future release of VIPM.

Jed, That is great news and good information for us for reference.

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.

I will recommend to submit your ideas to us. http://ideas.jki.net/

It will be great if you can share the package source. Send it to support@jki.net.

You can automate VIPM tasks using VIPM API functions. Here is the reference link: http://support.jki.net/entries/21395113-VIPM-API

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.

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-

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.

Scott, Please see if this article helps you: http://support.jki.net/entries/21447601-Resolving-issues-with-VIPM-connecting-to-LabVIEW

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.

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.

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

lolo, The task is only to allow checking for VIPM updates. The VIPM should launch and function successfully after installation.