I have this error in LV 8.6.1. The application has been running fine from within the development suite, but
building the application simply crashed LabVIEW - having the task manager to stop it. At this time the
builder says saving .... (see picture attached) which left me assuming a broken VI deep within NI's
libraries.
Note the DONE button is enabled and closes the window, but no application has been built. Usually if the done button is enabled, the build says somewhat like 'build located in...'
After 'enabling debugging' and uncheck 'Remove unused members of project libraries' in the build properties and having the main vi to build open during the build I got the 1502 error pointing to a unused VI within my application which has been broken due to a sub-vi's user interface change this is VI using.
Error 1502 occurred at
AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi ->
AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi ->
AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
possible reason(s):
LabVIEW: Cannot save a bad VI without its block diagram.
Note that if I tell the builder NOT to remove the unused (broken) members the build succeeds!
In between I've removed this bad VI's, and had been able to build without the 'enabling debugging' in the
build. But if I re-enable the 'Remove unused members of project libraries' LabVIEW again hangs at the end
of the build.
Keeping 'Remove unused members of project libraries' on is inacceptable as this increases the size of the
executeable from 3.2 to 29 MBytes (debugging on) and still 13 MBytes (debugging off)! And this is an elping application, not the main one. THis increased from 4.5 to 17 MBytes.
Any ideas? I'll try to cut down the example, but this will be a difficult process as I expect the Builders display is not pointing to the right VI (less frequently updated). And if, it's deep within NI's device drivers.
Regards,
Roland
