LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Bui

Not sure how to set VIs to separate source code...

 

So I did the forced recompile. Labview now consistently fails compile when SSE2 Optimization is checked, and consistently succeeds the compile when it is unchecked again...tried it both ways six times. Even tried shutting down and restarting LV and then recompiling both ways again. Same thing. Seems to be directly related to SSE2 somehow...?

 

I'm on a brand new Dell Lattitude laptop running high-end hardware, on Windows 7 with all recent updates. Had this same issue a few months ago on a relatively high-end Dell desktop as well...so it doesn't seem to be computer specific...perhaps manufacturer specific. I have no way to try another manufacturers' computer since the company I work for only buys Dell...

0 Kudos
Message 11 of 14
(1,041 Views)
OK, consistency is progress, I guess...

There's a setting under VI properties on the general tab I think about separating the object code from the source. Each VI is set individually.

How about making a copy of the project and start removing things one at a time. The code doesn't need to work, it just can't be broken.

Personally, I'd start with the instrument drivers.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 12 of 14
(1,030 Views)

Mike,

 

Thanks for your help. I'll have to continue troubleshooting as you suggested after I get a few of my other tasks (that got pushed out due to this bug) completed. I'll post back here if / when I find a solution.

 

-Ryan

0 Kudos
Message 13 of 14
(1,022 Views)

I realize it has been over 14 years since the original post and almost 7 years since the most recent one, but as there is no "solution" posted I thought I would mention what I found.  

 

I had this problem building my applications in a VirtualBox Centos 7 VM, so after researching the right way to do this I decided to try brute force and that worked for me.  The problem had to do with file permissions, so I decided to start LabVIEW 2020 in administrative mode (sudo ./labview - see image below).  The problem was solved!

 

Bill_in_DetroitX_0-1648118474663.png

 

Bill_in_DetroitX_1-1648118623724.pngBill_in_DetroitX_2-1648118742779.png

 

regards,
Bill
0 Kudos
Message 14 of 14
(708 Views)