Error 1502

[JorgeSau]

I'm having the same issue as appears on this thread. The vi's and directory where found are:

Close_Reference.vi.....AB_Source_VI.lvclass

Save.vi.....AB_Build.lvclass

I found the vi's in the vi.lib folder, but they are password protected, so can't try any of the suggestions regarding the cases and constants. I also tried enabling "Enable dubugging" in the Advanced mention of the exe builder and set "Disconnect type definitions" under the Additional Exclusions tab. Thanks.

Running LV2013, SP1, patch f2, Windows 7, 64-bit 

[JorgeSau]

Forgot to mention that the two file I listed are the files the app builder calls out with Error 1502.

Also, when i tried enabling the two options in the exe builder properties, the exe does build, but gives the error that the vi is broken and requires a development version of LV to fix. This is the same issue mentioned a few messages above. Thanks.

[warEagle12]

Hello,

Thank you for the infromation! Here is a KnowledgeBase Article that discusses the 1502 error and presents a few additional steps to configure to see if this error can be remidied: 

http://digital.ni.com/public.nsf/allkb/8683D4C66F5CA50E86257341007CF34D?OpenDocument

This problem can occur when there is a dynamic call that is not included in the build specification. VIs that are dynamically called must be placed in the always include section of the build properties window.  Another possible way to get rid of this error is by going to the Additional Exclusions section of your build specification window and selecting Do not disconnect type definitions or removed unreferenced members.While this may make your execution larger, in most cases it will fix the error.  Another possible workaround could be building an installer instead of an executable. 

Thanks!

[JorgeSau]

Stephanie,

The unchecking of the "Remove unused members of project libraries" fixed the issue. Thanks.

-Jorge

[warEagle12]

Great! I am glad to hear that this was helpful. Best of luck with your application!