Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/12/2019 in Posts

  1. 2 points
    Got same error from time to time. Have to restart LabVIEW. LabVIEW 2019 32bit Windows 7 Pro.
  2. 1 point
    I'm in no rush to move project to NXG, but I am curious, I saw on GitHub that JKI is has worked on a JKI State Machine for NXG and I was wondering if there was any similar project for EasyXML. I'm assuming the transition of this toolkit is not going to be a huge problem, am I right? I'm also assuming some NXG early birds have already tried the transition of EasyXML, anyone?
  3. 1 point
    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 "Run VIPM as Administrator", which (are you surprised?) fixes this "new" error. You'd think I would have learned my lesson, but I can at least pass on this warning. Bob Schor
  4. 1 point
    I missed the part where you are using a VM for this. Are you accesing from a remote X session? If so, the root user will require some additoinal authorization to run GUI based applications in remote sessions.
  5. 1 point
    One of my colleages found a sulution: I had to check the security checkbox under the general properties of the VIPM installer file. After that, the installation was successfull.
×
×
  • Create New...

Important Information

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