03-19-2008 09:06 AM
03-20-2008 07:59 AM
03-20-2008 10:22 AM
03-20-2008 11:07 AM
03-25-2008 11:31 AM
03-31-2008 02:05 AM
03-31-2008 05:30 AM
03-31-2008 05:43 AM
08-21-2009 01:22 PM
I just had the same problem. I am using LV 8.6 and OOP classes. Everything worked fine in the development system, but the executable came up with several VIs missing from the general error handler and the same final error message.
I decided to force LabVIEW to recompile all the VIs using shift-ctrl-run arrow. After saving all the files and building a new executable, the executable appears to work fine. It must have relinked whatever was missing.
Bruce
03-03-2010 03:14 PM
I am having a similar problem, but it did not go away when I recompiled everything.
Development machine:
Win XP Pro; LV 8.5.1f4 Pro; DAQmx 9.0.2
source in LV runs fine, custom built app runs fine.
Up to yesterday, I could copy the program to a target with a Zipped EXE file and run it.
Target machine:
Win 7; Custom LV Application; DAQmx 8.9.5
At this point, the built application fails to load and reports:
"VI has error type 4A438"
Tech support suggests that LabVIEW 8.5 and Windows 7 don't play nice. I am not using OOP's but I have been experimenting with XControls in a separate LVProject. I also added a feature to create a custom DAQmx scale.