Bob Schor Posted September 16, 2019 Report Share Posted September 16, 2019 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 3.0.0.170, 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-3.0.0.170 . Error Code: 8 Error Source: Open/Create/Replace File in C67C17A61D892A779727551BEF09A84E->43105161E3ECC5D5EE650DF274C1CB11->0ED5338B9A29C49A512F6049C2CCAE99->1DBEABF39FB76470575E756F0E9DB3AC->87355405EFC0DDB6ACE0A96175E31D86->OGPM Class.lvlib:89AC7BADF759B8183E200C1F7AFA7855->OGPM Class.lvlib:3617A98EB64CF6012064A2A881466B07->579BE417495B7ADCD1FF111EE165D832->VIPM Main Window.vi<APPEND> C:\ProgramData\JKI\VIPM\cache\jki_lib_easyxml-3.0.0.170.spec =============== Please advise how to proceed. Bob Schor Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted September 16, 2019 Report Share Posted September 16, 2019 Hi Bob. Error 8 is a file permission error. Please try this: 1) shut down LabVIEW 2) Go into VIPM and install EasyXML 3) Wait for VIPM to start LabVIEW, and then see if EasyXML installed OK If that doesn't work, retry the above steps, but launch VIPM as Administrator -- try it first with VIPM launched normally. Please let me know how that works for you. Quote Link to comment Share on other sites More sharing options...
Bob Schor Posted September 16, 2019 Author Report Share Posted September 16, 2019 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 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.