09-20-2011 10:21 PM
Hi All,
Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.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.
This error i am getting when i am trying to builg the EXE.
Help me.
Thanks and Regards,
Rams
09-22-2011 02:42 AM
Hi Rams ,
Can you please upload a snapshot of the error. so that I can better understand
Regards
09-22-2011 02:44 AM
http://forums.ni.com/t5/LabVIEW/Error-while-creatiing-executable-Error-1502/td-p/669757
The above thread might be useful
10-11-2011 08:19 AM
I had the same error in a VI that used to compile without any problems. But after changing this VI's code error 1502 error popped up. I tried some of the suggestions in the thread you proposed except enabling debugging but it did not help. The changes I made to the code included a case structure with a Boolean constant wired to the selector input. By doing this one of the cases would never execute and this was my way to save some old unused code code for the moment in the TRUE-case and putting some new code in the FALSE-case. Apparently the LabView compiler does not like this because removing the case structure and leaving only the new code made the compiler build my application without errors.
12-13-2012 10:31 AM
Also see here:
http://forums.ni.com/t5/LabVIEW/bleep-you-error-1502-shakes-fist/m-p/2252430
12-13-2012 10:44 AM
You forgot to see the date
12-13-2012 10:59 AM
@Stig junge wrote:
I had the same error in a VI that used to compile without any problems. But after changing this VI's code error 1502 error popped up. I tried some of the suggestions in the thread you proposed except enabling debugging but it did not help. The changes I made to the code included a case structure with a Boolean constant wired to the selector input. By doing this one of the cases would never execute and this was my way to save some old unused code code for the moment in the TRUE-case and putting some new code in the FALSE-case. Apparently the LabView compiler does not like this because removing the case structure and leaving only the new code made the compiler build my application without errors.
No the 2012 compiler does not like dead code. use a disable structure to disable code