Error 1003 when building executable

[ericdj]

Hi, I'm using Labview 2010 on Windows 7 and I'm getting an error when I try to build an executable:

Error 1003 occurred at Open VI Reference in AB_Engine_EXE_Call_Write_Icons.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Create_Build_Application.vi->EBUIP_Global_OnCommand.vi->EBUIP_Global_OnCommand.vi.ProxyCaller

Possible reason(s):

LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.

VI Path: C:\Program Files\National Instruments\LabVIEW 2010\vi.lib\Platform\icon.llb\Read Icons from ICO File.vi

This happens even when I try to build a simple vi, like a random number generator.

[TiTou]

Happens to me sometimes, I close LabVIEW and re-open it then it works...

That's not much help, I know...

[brunsli]

Same problem here. Error 1003 and error 8 I encoutered often.

For error 8 during build process, I needed to save the executable on a higher level in the file hierarchy.

For error 1003, I did not find a solution. Restarting LabView does not help. Sometimes (but not always) restarting the computer helps. Sometimes I need to reinstall the labview system.

More details: I have a first vi, starting the actual vi with a hidden front panel (second vi). This vi can also be started directly. Sometimes, the build process runs smoothly then  when I include the second vi as main vi to start the program.

The program runs fine when the build process succeeds, and it runs fine in LabView.

[ericdj]

NI solved this for me.  It turns out I had corrupted files way down in the icon.llb.  The VIs in that llb had broken arrows. Although they did not result in a broken arrow in the VI I was trying turn into an executable, they prevented a successful build.  They sent me an uncorrupted file and the build worked.

[brunsli]

Thanks for your answer.

I relinked a library, now it is compiling. The new library is identical with the old one, but located at a different place in the file system. I do not see the reasons it did not work previously....

How did "Ni" find this error? I performed a mass compile, without any obvious errors....

brauni

[ericdj]

Again, this llb was not a subVI of my program, but still prevented it from building an executable.  So it makes sense that you could do a mass compile.