tomlawton67

Same problem here, with the message "This package is not compatible with your operating system" - even though LabVIEW and OS are within acceptable range. Other packages are installing OK, so I believe permissions are good. I have a feeling the machine I'm on- which is now Windows 10 Pro- started life on Windows XP. I wonder if VIPM is detecting an old vestige of XP, and reporting the machine as such...? I can't see anything in System Information that's different from a "good" machine... Maybe it's <shudder>... in the Registry...? Any ideas?

Hi- late to the party here, but finally got around to updating. I'm probably pushing the envelope a bit, being on MacOS Sonoma, 14.4.1. Getting Error 8 "LabVIEW: File permission error. You do not have the correct permissions for the file." on startup... Have enabled Full Disk Access for VIPM, and recursively added the admin group RW for the National Instruments/LabVIEW folder (as this has traditionally been required..) I'd guess VIPM is trying to read or write a startup preferences file; and if I could for the life of me remember where it kept the file, I could delete or chmod it as necessary! Any clues? Cheers, Tom

Ahhh... yep... Not sure which was important- perhaps both- but install went OK after I granted LabVIEW and VIPM "Full Disk Access" ("Files and Folders" may have been sufficient, but I took the nuclear option..!) Thanks for the nudge

Hi- trying to install for LV2022, and the installation fails with: Main Package Name: JSONtext v1.7.0.118 Package Name with Error: JSONtext v1.7.0.118 Error Message: VIPM could not install the package jdp_science_jsontext-1.7.0.118 . Error Code: 1059 Error Source: Open VI Reference in BF32001BE83DE5E0CE0778B652B69156->0899928E468768EC9D6A07D840B896CD->AD4791BDA0231EB30EBF129C1A98AB7B->OGPM Class.lvlib:1D42A1CCBC79EB157F4B29421C6C7648->OGPM Class.lvlib:68DD1F408D6154AB6D8715845077EEA9->FB296AD1654D68D63B7041E1F06FA55C->VIPM Main Window.vi<APPEND> VI Path: /private/var/folders/ct/7_4f8zf08vldl700r6_w_1vh0000gq/T/TemporaryItems/PostInstall.vi =============== For 2021, I had a similar error, and IIRC I beat it by writing a VI to watch the TemporaryItems directory, and copy the PostInstall VI when it appeared, so I could run it at my leisure; it seems it was being deleted before it could be run. The same trick isn't working for LV2022; any ideas?! Guessing it's just a Mac problem...