Error while creatiing executable - Error 1502

[aghouse]

I have taken TestSatnd default Operator Interface and customized as per our requirement. When I tried to build the exectable of the new code the application buidles shows the following error.,

"

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_EXE.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

Is anyone know how to fix this?

Thx

Abdulla

[Kameralina]

Hello,

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.

Please let me know whether this works for you. 
Which version of LabVIEW are you using?

[DarkLordOfG]

I was able to get around this error by having the VI open when I did the build.  Doesn't make any sense but it worked.

John

[jdchu]

I had the same problem.  Does enabling debugging slow down performance?

[Kameralina]

Hello,

Enable Debugging includes the block diagram in the executable, and having the VI open probably prevented the error for the same reason.

The option should not affect performance, but it may make the exe larger.

Hope that this helps!

[travispape]

---

FieldKam wrote:
Hello,

Do not... remove unreferenced members.

---

 If anyone is getting Error 1502 when building after upgrading to LV 8.6....

I installed LV 8.6 on a machine to see how much work it would it would take to get my main application that was written in 8.5.1 to build on 8.6.  I was getting the Error 1502 message and after playing around with it for a while I found that there were at least a couple of different VIs in the project that would cause the problem.  It was odd that either of the VIs would work fine as a top-level VI in a debug .exe build, but as sub-VIs they caused the error.

Anyway, the above tip is what finally made my application build troubles go away.

[gmart]

Enabling debugging works because we keep the block diagrams of VIs. Since the block diagrams are around, the error doesn't apply. In a sense the problem is being masked. What needs to happen is to figure out why not having the block diagram causes the error. Is the code simple enough to be sent to support for evaluation?

[travispape]

Actually, I did not enable debugging, I just unchecked the setting for "Remove unused membersof project libraries", which is checked by default.  Do you still want code for evaluation?

Travis

[gmart]

Thank you for the clarification and glad to hear you are up and running. I would open a service request and send your files (if they are able to be loaded without drivers, custom code, etc) to support for evaluation.

[Michelle_N]

If you post the code here I can take a look at it and see if I can reproduce the error.