Problems creating a executable

[festo]

I keep seeing error 1003 when trying to create an executable for my application. It informs me that one of the subVIs is not executable. However, when I remove it the build has a problem with another subVI. Looking at the subVI independently there is no problem. Doing a mass compile creates no errors. Any suggestions?

[Ben]

Are you using LV 7.0 and type def's?

The following was cut and pasted from a discussion on Info-LabVIEW a while back.

Part 1

"

-----Original Message-----
From: = Michael Aivaliotis = [mailto:michael@mmwis.com]
Sent: Tuesday, July 08, 2003 7:47 PM
To: 'Info-LabVIEW Mailing List'
Subject: RE: lv7 app builder problem - solved


Thanks to all who replied!

Unfortunatly the problem is due to a LV7 bug. I managed to work around it. I'm just waiting to see if NIsupport can confirm this (doesn't matter, it's reproducable). I was able to isolate it to using unnamed typedefs. The app builder chokes on the bundle by name. I replaced it with the standard bundle and my app compiled fine. However the problem runs deeper as some experimentation discovered the real culprit. For the benefit of others, i've documented the bug here:

http://www.lavausergroup.org/phpBB2/viewtopic.php?p=136

In any case my problem is solved but hey, I only wasted a day...and a half No, i won't rant.:-(

Michael Aivaliotis

> Ok, a follow-up to my problem. I decided to do the following to debug
> the problem. I added the bad vi as a dynamic vi. As expected the app
> builder crapped out. I then removed the bad vi and added all of the
> sub-vi's of the bad vi as dynamic vi's. The app builder executed
> without problem. How can this be possible? The only thing between the
> bad vi and the subvi's are wires (no strict-types). Again, remember
> all of this code executes fine, it's the app builder that chokes.
> Also, all of this is running inside an llb
> right now so I don't think it's an issue of duplicate names anymore. I
> renamed vi.lib and user.lib just to be sure...
>
> Michael Aivaliotis
>
> > I'm trying to build an app in LV7. I keep getting the following
> > error:
> >
> >
> > Error 1003, the vi is not executable.>


"
End of part 1.

Part 2

"

-----Original Message-----
From: Konstantin Shifershteyn [mailto:snow@fivt.krasn.ru]
Sent: Tuesday, July 08, 2003 10:09 PM
To: michael@mmwis.com
Cc: Info-LabVIEW
Subject: Re: lv7 app builder problem


Michael,

As far as I can see, you have problem similar to one I met during beta testing. I reported it to NI staff and got rather good clarification. By default, LV7 AppBuilder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. If some VI in your exe calls a VI outside (that was not planned by AppBuilder) and uses a type definition in order to pass parameters, you will meet such kind of problem for sure.

I was offered a few ways to solve the problem but I really like only one. There is undocumented ini setting that disables this new feature. Put the following line to your labview.ini file:

BldApp.RemovePolyVIsandTypedefs=False

Then restart LV and rebuild your application.

[ another ways assume explicit including of all VIs into a build project, but it is unapplicable if you need support plug-ins, for example ]

Hope this helps.

regards,

Konstantin Shifershteyn
snow@fivt.krasn.ru
kostya_sh@email.com



"

FYI
The Info-LabVIEW archieves can be searched at

http://www.searchview.net/

If the above does not help, then are you using the SD Editor?

Disconnecting the diagram helps if this is the case.

Ben

[Ben]

And yet another posting from Info-LabVIEW

"
-----Original Message-----
From: Charles Lasnier [mailto:Lasnier@fusion.gat.com]
Sent: Tuesday, December 17, 2002 7:18 PM
To: Info-LabVIEW Mailing List
Subject: Re: error during application build


This is a post of a fix to a problem I posted previously, in which an application exhibited a 1003 error during the build. By building applications from the sub-vi's, I was eventually able to narrow the problem to an IMAQ property node which used the IMAQ Sleep property.
The property had become invalid, evidently when the driver was upgraded.
The solution was a new up-to-date copy of the imaqrc file, which is a resource file that goes in the LabVIEW 6\resource folder to replace the existing imaqrc
file. The new file was supplied by NI support.
IMAQ sleep is used to free up cpu cycles while an IMAQ card is waiting for a trigger/acquisition.

Here is the link to an example, sent me by Russell Blake of NI.
The imaqrc file is included in the download link from this web page.

http://zone.ni.com/devzone/explprog.nsf/6c163603265406328625682a006ed37d/4de0487ca4fb118086256ab80072afdc?OpenDocument

-Charles Lasnier


>Date: Tue, 19 Nov 2002 10:33:57 -0800
>To: "Info-LabVIEW Mailing List"
>From: Charles Lasnier
>Subject: error during application build
>Cc:
>Bcc:
>X-Attachments:
>
> I am getting an error 1003 "VI is not executable" error at the end
>of building an application. Like the previous posts, the VI runs fine
>under LabVIEW, so I assume there is some file missing from the build
>configuration. This is an application which built OK before, and the
>significant change seems to be that NI-IM
AQ was uninstalled and
>re-installed. I don't recall using any dynamically loaded VI's.
>Any suggestions?
>
>Thanks,
>Charles Lasnier
"

Ben