Labview 2018 - Error 1124 with Std Deviation and Variance.vi

[PerMartinHejHopp]

I have just been struggling with exactly the same issue so this is definingly a LabVIEW bug.

I upgraded my entire project from LV16 (32) to LV18 (32) and the builds works on some computers and not on others. I have not yet been able to see what causes the difference between the different computers.

“I think I will try compiling with the option for removing unused polymorphic VIs turned off (so the unused ones are included).  Maybe this will help...”   --> This did not help for me!

National Instruments, please fix this! It has cost our company several hours of extra work and a lot of headache.

[Ross36]

+1 for me to - just ran into this program this morning and it was a massive hassle as the systems were being used overseas. Surely this is an easy fix. It only seems to occur for me when I open code from earlier LV versions into Labview 2018 and build an executable. The workaround "works" but sucks as it should be an easy fix. 

[natasftw]

---

@PerMartinHejHopp wrote:

I have just been struggling with exactly the same issue so this is definingly a LabVIEW bug.

National Instruments, please fix this! It has cost our company several hours of extra work and a lot of headache.

---

http://www.ni.com/product-documentation/54795/en/

Seeing as the post before yours was a NI Employee calling it a bug, sounds like they'd agree.  Are you running the patch from the notes I linked?  It'd appear the 2018 f2 patch has a fix for the VIs referenced in this thread.

[DP2018]

Is there a better resolution to this yet?

I did an initial installer for a new program and it ran fine at first. I needed to make some changes so I updated (ran installer with no additional installer packages) and now its throwing up the "Labview: (Hex 0x464) VI is not loadable."

An error occured loading VI "NI_AALBase.lvlib:Std Deviation and Variance.vi"

I'm running LV2018 18.0f2

[EBlasberg]

I have not found a better solution to this given the version of LabVIEW.  Perhaps LabVIEW 2019 fixes this?

[DP2018]

I can confirm that right-click and select "Replace with SubVI Contents" fixes the issue and luckily for me I only had one instance of the subVI that was in a relatively convenient spot to break it out into its individual components.

Still frustrating, but at least it was documented in this thread and an easy fix.

[EBlasberg]

Agreed: frustrating and stupid.  And yes, at least there is a fix.  Hopefully it is (or will be) fixed in a future version...