Jump to content


Photo

VIPM 14 Pro fails to load packages on new Windows 10 PC


  • Please log in to reply
7 replies to this topic

#1 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 02 February 2016 - 02:27 AM

Over the weekend, I installed Windows 10 (64-bit) on a new PC, and started installing software.  Late yesterday, I installed LabVIEW 2014 and LabVIEW 2015, and to my surprise, did not have any installation problems (I did a similar install two weeks ago on a Windows 7 system with multiple "Service not running" bugs, since fixed).

 

I just installed VIPM 14.0 and activated my Pro license.  I successfully connected to both LabVIEW versions, downloaded packages, and then tried to install.  I usually start with a single package, NI GXML, then do the OpenG Toolkit.

 

I got bizarre errors when doing this.  Nothing installed, on either 2014 or 2015.  I'm going to try to paste the error message I got when trying to install GXML on LV 2015:  [Oops -- can't figure out how to post a SnagIt snapshot, thought the Image menu button would work like the LabVIEW Forums and let me find the image on my disk, but it wants a URL ...]  So here (I hope) is a Copy/Paste of the text ...

 

Main Package Name: NI GXML v1.4.2.8
Package Name with Error: NI GXML v1.4.2.8
Error Message: VIPM could not install the package ni_lib_gxml-1.4.2.8 .
Error Code: 8
Error Source: Open/Create/Replace File in 23163E1A41169BF347A8CCAAC0675BD9->737916C70F04A06F7315252588CFE2EA->EDC783C0EDD9EFF57211A26F185B4235->3CEEB42FDB9E41319885C763266FF802->C3E21B565FCD6F248FD8C7F70DCA4E74->OGPM Class.lvlib:F1B7AB8155DFB5A57C76E744EBF6D846->OGPM Class.lvlib:8DA808F6EDC3F497E0970966EA075B32->151384EDD6F89B08F780714EAD830768->VIPM Main Window.vi<APPEND>
C:\ProgramData\JKI\VIPM\cache\ni_lib_gxml-1.4.2.8.spec
===============

 

I'm going to try a few more times, with reboots in between.  Never had VIPM flat out fail on me (I have had problems with I forgot to enable TCP/IP, but I haven't made that mistake in at least 5 years ...)

 

Bob Schor 


  • 0

#2 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 02 February 2016 - 02:44 AM

Followup on reboot -- same failure with LV 2015, NI GXML.  So I tried OpenG Toolkit.  Barely started when it stopped, red letters at the top of the Package Information page says "This package is not compatible with your operating system or any LabVIEW version installed on your computer.

 

As I noted before, last week I successfully installed LabVIEW 2014 and 2015 on a Windows 7 (x64) PC (not new) and had no trouble loading packages with VIPM.  Now I'm doing the same on a new PC built with Windows 10 (x64), same versions of LabVIEW (2014 and 2015), which seem to work fine.

 

Is it really true that VIPM is not compatible with "my operating system", i.e. Windows 10?  I find that hard to believe.  After posting this note, I'll go to the Web, download it again (I probably installed from the LabVIEW disks -- the version, I think, is 14.0.1 Build 1967.

 

Incidentally, when I clicked "submit" on the previous post, the "busy wheel" spun for perhaps 3 minutes or more ...

 

Bob Schor  (maybe it's the Iowa caucuses messing with the electrons running around inside my PC ...)


  • 0

#3 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 02 February 2016 - 03:18 AM

OK, problem solved!  Downloaded 14.0.2 Build 1976.  Two installs with LabVIEW 2015, Windows 10 were flawless, what I've come to expect.  I guess when I installed the Latest OS, the Latest LabVIEW, I somehow got the "almost-latest" VIPM ...

 

Bob Schor


  • 0

#4 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 02 February 2016 - 04:03 AM

Sigh.  When will I learn?  VIPM/LabVIEW 2015 (the first I tested when I (re-)installed Build 1976) worked fine, loading several packages.  However, a complete failure with LabVIEW 2014.

 

Ever since I started using VIPM, I've had multiple LabVIEW versions (typically at least 4 versions), and all of them were configured identically, all using TCP/IP port 3363 (if VIPM set up up as different, I set them all back to the same port, depending on the previous observation that if I was on a VIPM 2015 page, it would (only) try to connect to 2015.  Now, with VIPM 2014.0.2, build 1976, with Windows 10, LabVIEW 2014 (SP1), I've been able to install packages in 2015, but none yet in 2014.  Will keep trying, but it's never been so difficult ...

 

BS


  • 0

#5 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 02 February 2016 - 04:24 AM

Well, I don't get it.  There's something funny in the Windows 10 "water" (I've been using it only 3 days, still learning its idiosynchrasies).  So after seeing the (very) early returns from Iowa, I tried again with VIPM, LabVIEW 2014, both 2014 and 2015 ports set to 3363.

 

And (as it has in the past 4-5 years for me), VIPM installed packages without a hitch!  Not at all sure what the difference was a half hour ago (except I didn't know about the caucuses), but I'm going to leave Well Enough Alone.  I've now got my most important packages installed on the two (so far) versions of LabVIEW on my new Windows 10 PC.  Time to get some work done ...

 

BS


  • 0

#6 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 18 March 2016 - 04:42 AM

Well, it's a month later, and I'm still having problems with VIPM and Windows 10.  I should mention that I am using VIPM 14.0.2, and a check says "Your software is up to date".  I have several machines running Windows 7 (x64) and one running Windows 10 (x64).  All my machines have LabVIEW 2014 (32-bit) and LabVIEW 2015 (32-bit).

 

My VIPM problems are exclusively with the Windows 10 machine.  I have managed to install the OpenG Toolkit and one or two other Toolkits (I think I have the Biomedical Toolkit under LabVIEW 2014).  However, attempts to install the "Hidden Gems in VI.lib" on either LabVIEW 2014 or LabVIEW 2015 met with failures, and the following Error Message:

 

Main Package Name: Hidden Gems in vi.lib v1.0.0.8
Package Name with Error: Hidden Gems in vi.lib v1.0.0.8
Error Message: VIPM could not install the package national_instruments_lib_hidden_gems_in_vi_lib-1.0.0.8 .
Error Code: 8
Error Source: Open/Create/Replace File in 21C4387AAE161FADBB1B2CA3A9EA1E5B->32E4E917A65244952F75E76C7A772B37->9DD90B2ABCC05E64EEB423775FEE5AA4->0514BDAA838359D0AD33ACAFA20FBC99->F94B9712B58831359A5E0BC2B53B4AFD->OGPM Class.lvlib:AE5C17D32A658827574CE56AD11AA4E5->OGPM Class.lvlib:C43A876EE83195DB5AD53919EE545D96->04B61BB9511860B66C121A638B9449D9->VIPM Main Window.vi<APPEND>
C:\ProgramData\JKI\VIPM\cache\national_instruments_lib_hidden_gems_in_vi_lib-1.0.0.8.spec
===============
 
I would appreciate some clue as to how to proceed, as well as some understanding of the nature of the failure.
 
Bob Schor

  • 0

#7 Bob Schor

Bob Schor
  • Members
  • 63 posts

Posted 16 May 2016 - 07:14 PM

SOLVED.

 

After three months of silence, I followed up with phone calls and e-mails to JKI, and got a response.  The suggestion was to download VIPM 14.2.1976 (which I had done), and install it with "Run as Administrator".

 

On my Windows 10 (Enterprise) PC, I am in the Administrator Group (though I don't use the "defined Admin" account).  I tried it both ways, after a fresh reboot.  Installing without elevating my privilege gave the same Error Message.  Installing with Run As Administrator did, in fact, work.

 

Some Questions.

  1. Did JKI not know of this "requirement" with Windows 10?  Had they not tested it?
  2. If they did know, why were there no "fixes" or "warnings" built into the latest Software?
  3. Why is there no information either here in the JKI Forums or on the JKI VIPM main pages?
  4. Why did it take >3 months and my "yelling" to get a response?

Yes, now I do feel better.  I still think that JKI are a great group of people, and will continue to support them and their products.  And (best of all) I now have the Hidden Gems In VILib on my Windows 10 LabVIEW 2015 system!

 

Bob Schor


  • 0

#8 Ashish

Ashish
  • JKI Team
  • 252 posts
  • Gender:Male

Posted 17 May 2016 - 03:55 AM

Bob,

 

Glad to know that "Run As Administrator" worked for you and you are now feeling better. :)

 

Our apologies for the delay in getting back to you.

 

Here is link to several support articles on VIPM: http://support.jki.net/forums


  • 0
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI