Yann 3 Posted January 27 Report Share Posted January 27 Hello, I was using VIPM 2019 and Labview 2019 without issue. After update to Labview 2020 and VIPM installed directly with NIPM, VIPM has error when launch. If I downgrade to VIPM 2019, it works but I can't link with Labview 2020. I tried to install VIPM 2020.1 and 2020.2, 2020.3 with NIPM or directly but still the same issue. There is no error in C:\ProgramData\JKI\VIPM\error Thanks Quote Link to post Share on other sites
Jim Kring 143 Posted January 27 Report Share Posted January 27 Hi There. Sorry for the trouble. You said you tried installing VIPM that you download from JKI, here, right? vipm.io/desktop Yes, something seems broken. What do you see if you click on the broken run arrow? Quote Link to post Share on other sites
Yann 3 Posted January 27 Author Report Share Posted January 27 Hello, Yes, exactly. I download from this point. If i click on broken arrow, I got "VI is not executable. The complete development of LabVIEW is necessary to solve errors". and that's all. Thanks Quote Link to post Share on other sites
Jim Kring 143 Posted January 27 Report Share Posted January 27 Would you be able to check which versions of .NET you have installed? That's the only thing I can think of that would cause the code to open but be in a broken state. Quote Link to post Share on other sites
Yann 3 Posted January 27 Author Report Share Posted January 27 .NET 3.0, 3.5, 4.0 and 4.8 are installed Quote Link to post Share on other sites
Yann 3 Posted January 28 Author Report Share Posted January 28 The trouble has been solved by IT. it was due to antivirus "cybereason" which was blocking .net for VIPM 2020. Thanks for your advices. 1 Quote Link to post Share on other sites
Jim Kring 143 Posted January 28 Report Share Posted January 28 Ah, that's good to hear that IT was able to figure it out. Glad it's working for you now. 1 Quote Link to post Share on other sites
Yann 3 Posted February 2 Author Report Share Posted February 2 Hello, I have been too much optimistic. Finally IT can't disable the antivirus on my computer for a long time. They whitelisted the C:/program files(X86)/JKI folder without effects. Do you know if there is some dependency or some others folders we could try to whitelist? thanks. Quote Link to post Share on other sites
Jim Kring 143 Posted February 2 Report Share Posted February 2 There are the ones that come to mind: C:\Program Files (x86)\JKI C:\ProgramData\JKI C:\Program Files (x86)\National Instruments C:\Program Files\National Instruments Quote Link to post Share on other sites
Sam Grayson 1 Posted February 23 Report Share Posted February 23 Did whitelisting those folders fix the issue? If not, did you find a fix? I'm running into the exact same issue, and I've confirmed that disabling Cybereason fixes it. Would love to have a fix that I could take to IT to implement. Quote Link to post Share on other sites
Jim Kring 143 Posted February 23 Report Share Posted February 23 Hi @Sam Grayson and @Yann -- I'm also curious to learn more about how to configure Cybereason so that VIPM will work OK for you. Please let me know if your IT departments are willing to share more information. Quote Link to post Share on other sites
Yann 3 Posted February 24 Author Report Share Posted February 24 Hello @Sam Grayson and @Jim Kring, the IT departement tried to whitelist any folders but it didn't work finally. it was working few time if VIPM start before Cyberreason. Anyway IT solved the issue with puting my computer in a special group to only use antivirus of cyberreason. Now it works correctly. I try to get more information from IT departement and let you know when I have news. 1 Quote Link to post Share on other sites
Yann 3 Posted February 24 Author Report Share Posted February 24 Here was last answer from IT which solved my problem : Maybe our problem is not AV itself but something else… I just put this machine xx.xx.xx.xx under a policy that has only AV enabled. 1 Quote Link to post Share on other sites
Jim Kring 143 Posted February 24 Report Share Posted February 24 Hi @Yann. Thank you for sharing how IT resolved the issue for you. That's really helpful to know. Quote Link to post Share on other sites
Sam Grayson 1 Posted March 2 Report Share Posted March 2 @Jim Kring @Yann Report from my adventures with IT. Short term solution: We found that it was the Cybereason ActiveProbe service that caused the run error. If that service was disabled, VIPM can launched without issue. Long term solution: IT assigned a policy to my machine that disabled some Cybereason monitoring for .NET (they were vague). I was then able to use VIPM while ActiveProbe was running. That's as specific as they were willing to get. Hope this helps! 1 Quote Link to post Share on other sites
Jim Kring 143 Posted March 2 Report Share Posted March 2 Ah, OK. Thanks @Sam Grayson. It's helpful to know that the issue may have something to do with .NET. Quote Link to post Share on other sites
Andrew Casalenuovo 0 Posted March 31 Report Share Posted March 31 We are also having issues with VIPM not running on our development computers due to Cybereason ActiveProbe. But it's even worse for us... We have LabVIEW 2019 Runtime in our Software Center, which allows anyone in the company to install it without admin rights. This has been done so we can give small executables to people to use, ones that don't need VISA, DAQmx, etc. Runtimes. Well, everything was fine a couple weeks ago but now ALL of those small programs load up with the same message, "The VI is not executable..." Since VIPM 2020 uses LV19 Runtime, this makes sense. But wow is it a pain. We're also in talks with IT as to what the core issue is and what course of action to take. Quote Link to post Share on other sites
Jim Kring 143 Posted March 31 Report Share Posted March 31 Oh no! I’m sorry to hear the installers and security challenges are such a pain. I wonder if there’s a way to have a VIPM installer that does not include the runtime engine stuff — can you install VIPM and the skip over the runtime installer part, I wonder. Quote Link to post Share on other sites
Waclaw 0 Posted April 14 Report Share Posted April 14 I have the same issue. New computer and fresh installation of the Windows OS. After installing LabVIEW 2020 and restarting the computer, the same information (VIPM service with dashed arrow) as at the beginning of this post appears . I did try also earlier versions of VIPM. It works well up to v. 2019. Problems started after upgrade to 2020.1 ol later versions. BTW. I have Cybereason installed too. Quote Link to post Share on other sites
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.