Error building .exe (internal.llb error)

[Dan R]

Hi all,

I have built many exe's, but for some reason this one is being difficult!  I get an error which states:

Error 1003 occurred at \\Rochester\mtp\Test Rigs\NC4\NC4 Air Cap\Code Development\Air cap v2.0\exe\internal.llb\Air Cap inspection Rig v2.1.vi

I have reviewed many forum posts which suggest that one of the sub vi's is not executable.  The main vi and all of the sub-vi's will execute in the labview environment.  I have tried a forced compile and even a mass compile.  All to no avail.  This problem occurs on two different PC's and other similar vi's build fine, so I assume it is not a problem with the builder.

I am using LabVIEW 7.1, Vision 8.0 and IMAQ 3.5.1: see attached report for good measure.

Can you help?

If you need the sub vi's let me know.

Dan

Message Edited by Dan R on 09-25-2008 11:55 AM

[Dan R]

You'll probably need these sub vi's.

[Dan R]

I'm not sure if the main vi will have the sub-vi's in it, but I can only add three at a time - Grrr!

Anyway, these are the last two!

Message Edited by Dan R on 09-25-2008 12:02 PM

[Daniel_Thomas_NIUK]

Hi Dan,

I have reviewed you forum post and have come up with the following information which should hopefully assist you with your application.With regards to the error code 1003:

1003	The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File»Open And verify that it is runnable.

 This may occur because one of your variables is spelt slightly different to what the code is expecting, or because one of your enum typedefs has an empty element.  If you are using Microsoft word, Excel, RT, or the report generation toolkit, you need to include more files to make it work as an .exe.  

After taking the selection of vi’s that you posted I set up a system to the specification which you had described. I found I could produce executable files in LabVIEW 7.1 but it did require the application builder toolkit. 

When running your main vi it requested the locations of a number of sub vi’s that you hadn’t posted. If the methods recommended in this post do not solve your issue then it may be worth you posting your remaining vi’s.  

It may also help if you: 

Check the Enable debugging option in the Advanced category of the application executable properties.

Uncheck the Disconnect type definitions and remove unused polymorphic VI instances.

Here are some links that may help you:

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

http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02 

Regards,

Message Edited by DThomas on 10-06-2008 08:18 AM

Message Edited by DThomas on 10-06-2008 08:19 AM

[Dan R · Accepted solution]

See solution here: http://forums.ni.com/ni/board/message?board.id=170&message.id=360001#M360001