Error 1502 when building RT Exe in LV8.5

[Jeff_Long]

Hi.

I'm getting the dreaded error 1502 when I'm building my application for my LVRT target (cRIO).

The following information appears in the "Build Errors" dialog:

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 1502 occurred at Invoke Node in 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_RTEXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller

Possible reason(s):

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

Method Name: Save:Target Instrument

None of the problematic VIs are mine.  As far as I know, all of my software versions are up to date.  Any ideas?

[Riconquistiamola]

Jeff,

Thank you for your post. The "dreaded" 1502 error can reference more than one type of build issue, but there are general workarounds if you believe your code is not at fault.

You can get rid of this error if in the Additional Exclusions section of your build specification window select Do not disconnect type definitions or remove unreferenced members. While this may make your execution larger, in most cases it will fix the error. Another option is to enable debugging. This can be done by navigating to the Advanced section of the build specification, and check Enable debugging.

If you are successful with this workaround we would be interested in seeing exactly what has caused the 1502 error. If you can please create a service request (referencing this discussion forum) we can further investigate your problem to make LabVIEW a better product.

Cheers.

[Stephen_Moore]

I have also just had a similar problem.  It turned out that I had changed the input of a case structure to a constant. 
Labview then cam up with the errors when attempting a build.  Adding some logic between the constant and the case structure solved the problem.
This may not be your problem.
Cheers
Stephen

[Riconquistiamola]

Stephen,

R&D would be interested in investigating this behaviour. If possible, could you post a reproducing case or contact your local Applications Engineering Department and provide them the example?

Cheers.