Jump to content

Bob Schor

  • Content Count

  • Joined

  • Last visited

  • Days Won


Bob Schor last won the day on October 16 2019

Bob Schor had the most liked content!

Community Reputation

2 Neutral
  1. Son of a gun!  After posting "I can't install VIPM 2019", I tried once more, got the same error, clicked something (maybe "ignore"?, and the installation started up, despite the error.  It finished, and now it looks like it is working.  Weird.

    Bob "I believe in Miracles" Schor

  2. Recently installed LabVIEW 2017 (have other versions already installed), VIPM Pro 2019 fails to install Hidden Gems for LabVIEW 2017 (but installs OpenG just fine).  I also tried running VIPM as Admin, made no difference.  

    Oops, spoke too soon -- Got Error Code 7 with OpenG LabVIEW ZIP Library.  Had gotten Error Code 8 with Hidden Gems.  Did reboot on first seeing this error, and still error persists.

    One other Gripe -- I logged in to JKI Community, saw my old messages, but couldn't Post.  I was identified on the Forum as Bob Schor (Members), but it still insisted that I "Sign In" again to post.  I did, got back to the same place, and now I can post.  This is an annoying "Feature" of the site!

    Bob Schor

    1. Bob Schor

      Bob Schor

      OK.  Second Reboot, uninstalled then reinstalled OpenG Toolkit, on reinstallation, only the LabVIEW Zip Library seemed to be installed, without error.

      Hidden Gems in vi.lib (from the 2017 menu) still gives me the error, message attached below.

      This time, when I log in to the Forum, I get here without trouble (i.e. it not only takes me to my "page", but it lets me enter this message without needing to "Sign In" again).  Weird.

      Bob Schor

      VIPM Hidden Gems Bug.txt

  3. I've been using VIPM for years to access the LabVIEW Tools Network. Recently, one of my machines was set up with a User Account (where I do most of my work) and a separate Admin account. A while ago, I tried to install EasyXML and got a strange error (among other things, I was told the package was not compatible with my OS nor any version of LabVIEW installed on my computer). Turns out the "fix" was to run VIPM from my Admin account. But do I learn? No, months later, I try to install another package. Similar error. While browsing this Forum, I run across my previous note and see "Ru
  4. Running as Administrator did it! I was about to do a Follow-up Post saying I'd just "built" a second PC with LabVIEW (on a system where my normal account is NOT an Admin account, just like the PC where I had the problem), and over here (PC-2), EasyXML installed without problems. So back to PC-1 (where the problem occurred), did Steps 1-3, no go, but Step 4 worked. Who knows, some permission flag got "stuck", I guess ... Many thanks for the quick response. Bob Schor
  5. I've just (re-)installed LabVIEW 2016 (32-bit), 2018 SP1 (32-bit), and 2019 (32-bit) on a Windows 10 PC. I successfully installed the OpenG Toolkit in LabVIEW 2018 (so VIPM 2019 is clearly working). When I try to install EasyXML, I get an Error message: Main Package Name: EasyXML Toolkit for LabVIEW v3.0.0.170 Package Name with Error: EasyXML Toolkit for LabVIEW v3.0.0.170 Error Message: VIPM could not install the package jki_lib_easyxml- . Error Code: 8 Error Source: Open/Create/Replace File in C67C17A61D892A779727551BEF09A84E->43105161E3ECC5D5EE650DF274C1
  6. It is about four years later, I'm re-installing EasyXML, and this Example is still broken. The newly-installed Package still has the 4-year-old "wrong" Address, not the "corrected" one listed above. Why not put the "right" address in the Package? When I manually put the corrected address in and tried to run the example, I got "Error 1181 occurred at DataSocket Read in Read RSS Feed.vi. Possible reason: Protocol not recognized by LabVIEW. Can you please do the following: (1) Figure out how to make this example work! (2) Update your Package Repository to include the repair
  7. 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. Did JKI not know of this "requirement" with Windows 10? Ha
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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 tr
  13. 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 d
  14. I just tried the Read RSS Feed example for EasyXML 2.0, and failed the parse. I'm guessing that the rss cluster that "defines" the parse is very wrong. The feed is coming from http://forums.lavag.org/rss-8.html. The first few lines of the raw rss data are: <!DOCTYPE html> <html lang="en" xmlns:fb="http://www.facebook.com/2008/fbml"> <head> <meta charset="UTF-8" /> <title>LAVA</title> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <link rel="shortcut icon" href='https://lavag.org/favicon.ico'/> <link rel="image_src" href=
  15. OK, so a "simple install" (just click the downloaded installer) fails because "The product is already installed". Go to Control Panel, remove VIPM 2014, and try again. This time, it installs, and actually seems to run! Hooray. BS
  • Create New...

Important Information

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