Error while building an executable from vi

[saurabhsay]

Hello,

I am trying to make a .exe file from the VI which includes Vision Aquisition Software also and while building it I get a error message--

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_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Create_Build_Application.vi -> EBUIP_Global_OnCommand.vi -> EBUIP_Global_OnCommand.vi.ProxyCaller

Possible reason(s):

LabVIEW: Cannot save a bad VI without its block diagram.

Can anyone tell me how to solve this problem ?

Thanks in advance.

[mikeporter]

Have you tried any of the suggestions that all the other people who have had this problem tried?

Mike...

[Xenox]

Hi,

which LabVIEW version do you have?

With LabVIEW 2009 f2 patch they fixed this bug:

http://digital.ni.com/public.nsf/allkb/6CE99D0518D392E98625768E00543744

Can you execute all your SubVIs?

Did you try to create a new build specification?

Xenox

[stevevalwa]

"Have you tried any of the suggestions that all the other people who have had this problem tried?"

I can't find any suggestions. I'm using Labview 2011, I've built my application hundreds of times in the past sucessfully, I created a new sub-vi, it executes as a standalone fine, and it executes within the top level vi fine, but when I try to build my application with it, I get this same error. The block diagram is there, and obviously no errors. I've even re-coded it from scratch with the same results.

[richard.koo]

I have the same problem with LabVIEW 2010 sp12f.  Remove unused members of project libraries had always been checked.  I have been building this project for 2 years, adding features along the way, and never had this problem.  Today, suddenly I got it. 

Desperately needing a solution.

[stevevalwa]

I was able to get rid of the error by deleting the executable build definition and re-creating it from scratch... Clearly there is some bug in the application builder that corrupts the definition. In my case, all I did was create a new (perfectly working, simple, with no errors, and block diagram) vi, insert it into my project, use it in the top level VI, and then try to build the application from the existing definition and I got that error.

[richard.koo]

I had done that and did not work.  I did not get rid of the old build defination, but started a brand new one via Tools>Build Application (EXE) from VI...  I got the same error 1502.  Inspecting the offending VI did not yield any obvious problem with the block diagram. 

Upon searching for error 1502, I found this Know Issue link:

http://www.ni.com/white-paper/11869/en.  Issue ID 255617 stated:

Error 1502 can occur if dependencies are placed in non executing case structures
In previous versions of LabVIEW you could place VIs in a case structure with a constant wired the the case selector. This would load the VIs at runtime. If you have this pattern and attempt to build an executable you could receive error 1502

Workaround: Don't use unreachable code

So the issue is I have an case structure with hard coded boolean, so the other case is unreachable.

[vgravel]

Hello,

I'm having the same problem and I'm not using unreachable code... Looked many times. I'm using LabVIEW 2011 (11.0).

Anybody knows if SP1 would help?

Thanks!

Vincent

[sfrosty]

I get the same 1503 error. I've made the VI in question a separte project and in creating EXE I get the same error. 

Using LabVIEW 2011 SP1

[sfrosty]

I found that I can eliminate the 1502 errror and generate a successful build if I check the Enable debugging under the Advanced catagory.