Exe build error involvving internal.llb

[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

[J POWER]

HI Dan,

Thank you for your post, I have been investigating into your issue and the error code 1003 means:

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.

 By any chance are you using Microsoft word, Excel, RT, or the report generation toolkit?  

 If so you need to include more files to make it work as an .exe.

Also it may help if you:

Enter the ‘my advanced properties’

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 

If these can’t help could you please send a screenshot of the error message and section of code.

I have also noticed that you have posted this on another forum page please could you reframe from double posting in future.

http://forums.ni.com/ni/board/message?board.id=170&message.id=357791

Regards,  

Message Edited by J POWER on 10-06-2008 05:35 AM

[Dan R]

Hi Jordan,

Thanks for the advice.  I will give it a go.  I realise that I have posted this twice, but I thought I wasn't getting any replies because I basically repled to my own thread!  I wanted to include all the sub-vi's in the post as they may be the source of the error.  However, I found I was limited to 3 attachments per post, so posted 2 replies with the sub-vi's making my post appear answered!  Surely it would be better to limit the combined size of attachments.  Mine weren't particularly large.

Anyway, I thought I might delete the old one, but I don't think that's possible is it?

I will try to avoid these multiple posts in future.

Thanks again for the advice.  I'll let you know how I get on.

Dan

[J POWER]

Hi Dan,

I just had a look at one of your VI’s and you are using excel, another thing to check would be versions of excel on the development machine and the target user, as if they are different the functions won’t run properly as the commands differ.

Here is another link that may help with the report generation toolkit:

http://zone.ni.com/reference/en-XX/help/372120A-01/lvrgthelp/rgt_stand_alone_apps/

This explains some of the files needed to make the toolkit work in application.

Regards,

[Dan R · Accepted solution]

Hi Jordan,

i couldn't see anything wrong with the individual sub-vi's and tried your suggestions.  It turned out in the end to be a problem with opening the excel file with a password.  There was no security on the excel fiile, but the vi was programmed to use one.  If I removed the password from the vi it wouldn't open so I added a password to the excel file and - hey presto! - it all works and builds into an exe!

I haven't tried it on the machine yet, but I am optimisic that it will work.

I think it's microsofts fault!

Thanks for your suggestions; you narrowed it down to the excel link.

Cheers,

Dan