LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot build executable file. Error 1003. No Vi Error listed.

Dear NI,

 

  I'm using LabView 8.5, I can't build my application after massived change the the code. I try follow the instruction on the Error 1003, but didnot work out. Below is my mass compile result:

 

 #### Starting Mass Compile: Fri, Jul 31, 2009 2:08:51 PM
  Directory: "D:\Generic Controller"
Search failed to find "semaphor.lsb" previously from ""
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
Search failed to find "RESISTANCE AND VOLTAGE DISPLAY.vi" previously from "D:\Generic Controller\Instrument Classes\Temperature Reader\,DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi\RESISTANCE AND VOLTAGE DISPLAY.vi"
Search failed to find "RESISTANCE AND VOLTAGE INITIATE.vi" previously from "D:\Generic Controller\Instrument Classes\Temperature Reader\,DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi\RESISTANCE AND VOLTAGE INITIATE.vi"
Search failed to find "Temperature Read.vi" previously from "D:\Generic Controller\Instrument Classes\Temperature Reader\,DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi\Temperature Read.vi"
Search failed to find "RESISTANCE AND VOLTAGE CONFIG.vi" previously from "D:\Generic Controller\Instrument Classes\Temperature Reader\,DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi\RESISTANCE AND VOLTAGE CONFIG.vi"
  ### Bad VI:    ",DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi"    Path="D:\Generic Controller\Instrument Classes\Temperature Reader\,DanaInfo=owa.draper.com,SSL+RESISTANCE AND VOLTAGE MAIN.vi"
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
        #Reload LVSBs: CIN (semaphor) was loaded from inside VI (C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Platform\synch.llb\Semaphore Core.vi)
#### Finished Mass Compile: Fri, Jul 31, 2009 2:09:05 PM

 

 NOTE: The RESISTANCE.vi is not a part of my applycation.

 

And below are my build error message:

 Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 1003 occurred at AB_Application.lvclass:Open_Top_Level_VIs.vi -> AB_Build.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.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.  Open the VI in LabVIEW using File>>Open and verify that it is runnable.

 

0 Kudos
Message 1 of 13
(4,568 Views)

That's telling me that "RESISTANCE AND VOLTAGE MAIN.vi" is a dependency of your application but it can't find it in order to resolve it during the build.

 

Look in the Dependency folder in your project...is this VI listed there?

 

Can you run your application in development mode with no problems?

0 Kudos
Message 2 of 13
(4,551 Views)
In the depency list aren't containt RESISTANCE*.vi. It is run under development eviroment without any trouble.
0 Kudos
Message 3 of 13
(4,533 Views)

I might suggest opening your top level VI and choosing View >> VI Hierarchy in order to look at all dependencies within your VI. Then see if you can locate any of the RESISTANCE*.vi  VIs. If you do, you can right-click on them and choose Properties... which will bring up the General VI Properties of the VI which should give the location of that VI on disk. Make sure it is added to your project.

 

Also, are you using an existing build specification when building the application, or did you create a new one for the largely changed application? I would suggest creating a fresh build specification.

Will
CLA, CLED, CTD, CPI
LabVIEW Champion
Choose Movement Consulting
choose-mc.com
0 Kudos
Message 4 of 13
(4,513 Views)

Ok, I when through my code and remove some, and try rebuild. I found that the ThisApp class's pirvate cluster containt an Strict Type RefNum of ThisApp class. When I remove this RefNum, LabView seem to let me bulid the application.

 

After work around on this problem, I found that "Preview" in the Build process show no more error. But when I try to Build the application, the Status Dialog show me that the Build when through a lot of the VI file without error until the end of the build it gave me following error:

 

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 Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller

Possible reason(s):

LabVIEW:  Cannot save a bad VI without its block diagram.

Method Name: Save:Target Instrument

0 Kudos
Message 5 of 13
(4,506 Views)
I'm now able to build my application just by checking the Enable Debug Check box in the build properties. Now I got another problem is that when I run the Application, the run button show error icon on my application Panel. But there is not error when I run my Application under Development Enviroment what is the problem now?
0 Kudos
Message 6 of 13
(4,441 Views)

Is this issue local to this particular project, or does it occur even if you attempt to build a small application?

Do you get any warnings when you build your executable?

Can you only build it with debug selected?

Will
CLA, CLED, CTD, CPI
LabVIEW Champion
Choose Movement Consulting
choose-mc.com
0 Kudos
Message 7 of 13
(4,425 Views)

1. Yes, only happen on this perticular project. I can build a small application and run at normal.

2. Did not get any warning during build or Preview.

3. Preview allway tell me it good to go. But if I don't enable the debug option, the build process will complaint at the end of the build. 

0 Kudos
Message 8 of 13
(4,422 Views)
So does the application always build successfully, but then just does not run? What do you mean by the build process complains at the end of the build? Do you get the same error as you listed before? A different error?

I may suggest building the pieces of your project individually until you can locate the specific section that causes the build error. This can help isolate the cause of the issue.
Will
CLA, CLED, CTD, CPI
LabVIEW Champion
Choose Movement Consulting
choose-mc.com
0 Kudos
Message 9 of 13
(4,367 Views)

Hi guys,

   I think I found "one" of the problem that make my application can't be executable event Labview 8.5 let me build executable file successfully. Bellow is the simple project that containt 1 Abstract class and its 2 childrens class. I try to build the source distribution (but it would introduce the same problem).

   I divide children classes in to differecenc virtual folder to allow me rename the vi to solve the VI name conflict. However this is the main thing that cause the problem. But since I working on Object Oreiante, therefor I have no other solution for it right now. In my conclusion that, I can't not have multiple children class inherit to one parent class that dynamic link to function call. If you have any work around in this, please let me know.

0 Kudos
Message 10 of 13
(4,336 Views)