executable errors

[Live_Wire]

I have built an VI that runs as a VI but when I try to build it into a standalone application i get the following error:

C:\program files\national instruments\labiview 8.2\vi.lib\gmath\NumericalOptimization\cgderivative fletcher.vi.

The VI became broken during the build process.  Open the Build Specification and enable debugging to include front panel and block diagrams. 

(*I don't want to show block diagrams.)

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 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_Rule_Editor.vi -> EBUIP_Item_OnDoProperties.vi -> EBUIP_Item_OnDoProperties.vi.ProxyCaller

Possible reason(s):

LabVIEW:  Cannot save bad vi

I have found similar posting on this subject but none of them have Error 1502. I've tried all the fixes from the similar postings but none have worked.  Any help would be aprreciated.   

[reggier]

Hello,

I have seen issues like this before where the type def disconnections are causing the error.  Can you rebuild the executable and in the advanced exclusions tab choose "Do not disconnect type defs"?  I think this will help you out.

Thanks and good luck!
reggier

[Live_Wire]

I've tried that but it doesn't work.  I think the computer is running out of memory while the build is in process. Would that be why i'm getting an error?  I've haven't seen any documentation regarding this issue. 

[reggier]

Here are a couple more things to try/check.

1) Can you check the task manager during the build to see if the memory is spiking?  LabVIEW does require that its applications be open during the build process, so it would be beneficial to see how much memory is being used.

2) Can you build/run a smaller application that doesn't require this specific vi?  If yes, can you build/run a smaller application that does include this vi?  If yes, keep adding things into the program until the build/run is unsuccessful.  This will give us a better understanding of where the error is coming from.

reggier