LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview: (Hex 0x464) VI is not loadable.

Solved!
Go to solution

I have an LabVIEW 2018 executable built on a Win7 pc. It runs fine. I ran it on another Win7 pc and a Win10 pc and it runs fine. However, another Win7 and Win10 machine have the following errors. The PCs that fail do not have the LabVIEW 2018 Development installed, only the 2018 Runtime Engine. The app has the following dll dependencies, Advapi32.dll, kernal32.dll, lvanlys.dll. Any suggestions how to fix this? 

 

 

 

qq.jpg

0 Kudos
Message 1 of 7
(5,373 Views)

At the first - try to remove the checkmark from the "Enable SSE2 optimization" checkbox in the buld spec (if enabled).

 

0 Kudos
Message 2 of 7
(5,357 Views)

@Andrey_Dmitriev wrote:

At the first - try to remove the checkmark from the "Enable SSE2 optimization" checkbox in the buld spec (if enabled).

 


Are there any x86 processors out there that don't use that?  I feel it is a symptom and not the problem.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 7
(5,348 Views)

I have LabVIEW 2018 32 bit installed. I do not see the Enable SSE2 Optimization option.

 

qq1.jpg

0 Kudos
Message 4 of 7
(5,337 Views)
Solution
Accepted by topic author davidhi

Looks like the issue was with the LabVIEW 2018. I just updated with 2018 f2patch and the app is now working.

0 Kudos
Message 5 of 7
(5,314 Views)

@davidhi wrote:

Looks like the issue was with the LabVIEW 2018. I just updated with 2018 f2patch and the app is now working.


Don't forget to mark your post as the solution.  It will definitely help others!

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 7
(5,311 Views)

Experienced the same problem. Runs fine on development computer. Popup this error on computer only with LV18 runtime.  One compiled app initially runs fine, then after disabling an indicator also started this error. Everything fixed after installing f2 patch through NI update service. 

0 Kudos
Message 7 of 7
(4,225 Views)