Help on Error 1502 when building application. How to find broken the VI?

[kraxx]

hello,

I have a problem compiling an application with AppBuilder in LV 8.2.1. If I compile it with debugging enabled, it works fine. If I compile it without debugging enabled, I get the following message:

Error 1502 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller

Possible reason(s):

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

Switching on debugging includes the block diagrams, so i can not leave debugging on (the classes inside the application would disclose to much knowledge, which should be protected...)

In the thread " Build error 1502 - but no broken VI" (http://forums.ni.com/ni/board/message?board.id=170&message.id=218967&query.id=175357#M218967)  lgk tracked down the "broken" vi (problem-causing vi) by DISASSEMBLING his whole code. I can not effort this in time (my application consists of ~800 VIs).

I need a tool, which identifies the problem-causing VIs (which are usually subVIs of the the VI stated by the error section). As an error can be generated/detected it should not be to difficult to provide a tool, which scans the code in the VIs to be ok....

Any other suggestions are welcome, too...

TIA
andreas

[mikeporter]

Try doing a search in the forum for "error 1502". This is a known problem.

Mike...

[BillMe]

I wrote a VI that will recurse through a folder hierarchy and find all "bad" VI's. Maybe someone else will find it useful. I'll post it on Monday.

[kraxx]

Thank you for the feedback.

Bill, it would be really of great help for me - and i guess also for others - when you could post such a vi. Thanks again.

[BruceMoyer]

I got bit by this bug when converting to LV2010 (from 8.5).  Took me a while to figure out the specific problem because it takes about 10 minutes to compile my exe and I had to try multiple times to get it plus trying other things such as building an exe with just the offending VI but with no success.

Turns out the problem went away when I changed the case selector with a constant connected to it into a diagram disable structure.

Bruce