Build Exe

Sorry i have posted the question in other forums
Good Morning
I have Main vi,from which I will run many vis in parallel(Open Reference).
This program works fine, but when i created an executable for the main vi and tried to open the parallel vis it gives the error message "Missing subvi write to spreadsheet file".
Pls give me suggestions
Thanks

Hi
When i add the files, i am getting a conflict for a subvi(becuase this subvi is used in the main vi and all the other vis which will be called from main vi).
What happens is when i add a file to my computer in the project explorer,the subvi gets added to the dependencies and while i am adding the other vis to my computer in project explorer the subvi getting added again and it gives conflicts in dependencies.
Pls let me know ,I can post the error i am getting.
Thanks

Similar Messages

Build EXE error in excel dispose report

I have seen much discussion about path-relative-to-current vi problems when building EXE apps.
I am compiling an EXE which happens largely successfully, but when it encounters the Excel Dispose Report vi at the end of my Excel report creation section, it stops with 'error 7 at open vi reference in Dispose report ...excel quit vi ... file not found'. It works without a problem in the un-compiled version. I am just using the standard Excel Dispose Report vi out of the report generation library.
Can anyone enlighten me about how to clear this problem?
Fred

Fred,
Did you include the dynamic VIs? See: http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
More confirmation it is dynamic VI issue: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

First Chance exception in build.exe(NTDLL.DLL);0xC0000008:Invalid Handle

Hi Michael,
                           I am using WINDOWS XP with SP2 ; I am facing a problem after installing Sp6 for VC++
             First Chance exception in build.exe(NTDLL.DLL);0xC0000008:Invalid Handle
     Please Help me out for this Michael.
Thanks & Regards,
Rakesh
Rakesh

Howdy Rakesh,
I'm not sure who Michael is, but you might want to try the MSDN or the MSDN forum for general VC++ help.
Warm regards,
pBerg

Labview crashes when building exe

Hi all,
I have created a Project and have a main vi which works fine in the development environment. When I try to build exe for the same, LabVIEW crashes. I dont get it why. If anyone could help on this, you are welcome.
LabVIEW version:2013, 64 bit
Thanks,
Prabhu
Solved!
Go to Solution.

Hi Prabhu,
either provide full error descriptions - or your complete project so somebody else can try to build your EXE…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Labview 8.5 installer build *.exe wrong date code

In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today. It will not update even after deleting it. Is this a known bug? SS

Hi SS,
The Date Modified property of setup.exe shows the date the MetaInstaller was built. This was true in earlier versions of LabVIEW as well. It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior. The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi. Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed.
Jennifer R.
National Instruments
Applications Engineer

Labview shuttin down while trying to Build EXE

Hello,
I am trying to develop a program using LabVIEW 8.0 and when I am trying to build exe the Entire LabVIEW software is getting closed. There hadn't been any such problem till now and I had even made EXE files of the same program many times earlier.. Can anyone help me in finding out a solution for this.
Regards,
Nitzy

hello,
Does the CPU goes to a 100% while you build the installer? Also doe isclose abruptly (may it says not responsding)
Why dont you try calling your local NI representative and explain the situation ?
GUru
Regards
Guru (CLA)

Slow update of shared variables on RT (cRIO) after building exe

Hi,
I've been struggling with this for the past few days. I am having a problem with slow updating of shared variables on my RT project....but only after building the application into exe's.
The application consists of an RT target (cRIO 9073) sampling inputs at a rate of 1sec. I have a host PC running the front panel that updates with the new acquired values from the cRIO. These values are communicated via shared variables.
Once the cRIO samples the inputs, it writes the values to the shared variables, and then flags the data as 'ready to be read' using a boolean shared variable flag. The hostPC polls this boolean shared variable and updates the indicators on the front panel accordingly.
Now, this worked fine during development, but as soon as I built the RT exe and host exe's, it stopped working properly and the shared variables ended up being updated very slowly, roughly 2-3sec update time.
To give you some more background:
I am running the Labview 2010 v10.0.
I am deploying the shared variable library on the RT device (as the system must work even without the hostPC). I have checked that its deploying using Distributed System Manager, as well as deploying it into the support directory on the cRIO and not the exe itself.
I have also disabled all firewalls and my antivirus, plus made sure that the IP's and subnets are correct and its DNS Server address is set to 0.0.0.0.
There are 25 shared variables all in all, but over half of those are config values only used once or twice at startup. Some are arrays, plus I dont have any buffering and none of them are configured as RT FIFO's either.
The available memory on the cRIO is about 15MB minimum.
What strikes me is that it works fine before building exe's and its not like the cRIO code is processor intensive, its idleing 95% of the time.

Thats exactly what I'm saying, it takes 2-3seconds to update the values.
I have tried taking out the polling on the PC side, and registered an event on the changing of that shared variable and that doesn't do anything to change the slow update time. Even if I stop the PC, and just monitor the shared variables in DSM it updates slowly.
I also tried utilising the "flush shared variables" vi to try to force the update....that does nothing.
I wire all the error nodes religously. Still no luck.
Its very strange, I'm not too sure whats happening here. These things should be able to update in 10ms.

Can't find the Workflow builder exe - how to start it?

Can anyone tell me where the workflow builder exe resides. Is it a java applet, OCX or EXE. How does one start it? OUI shows the client is installed and I can verify the WF server is functioning since I can run one of the demo apps and look at a process through the browser. From the doc however, the WF builder appears to be a Windows based app.
Any help is appreciated.
TIA
Paul Valdetaro

Hi
The workflow Builder is an application, that came with Oracle Client Cd4s.
Try installing the option in the Oracle Cd4s e the application is inside START/ORACLE***/Application Development.
I hope this will help you

Build exe for DSC security tools

Hi All,
I am developing an application in LV7.0 which has Visa read/write functions, alongwith that i want to implement some security features using Dsc module's vi present in function palette. My requirement is wen Login button is clicked a login dialog box gets popped up, this i have done by using NI SEC Invoke login dialog. vi. I have also used other security tools like NI SEC User account info.vi, programmatic logout.vi etc.........Vi is working perfectly fine but after making exe, and running it on same pc, login dialog box doesn't gets popped on login button clicked.
So my doubt is do i need to add some security library files while building exe and creating installer???
Your reply will be valuable to me
Thanks & Regards,
Ratna

Hi Sahil,
Thanks for ur reply. wanted to inform u that i m using only security tools of DSC module, apart from that no other DSC tools. Even though i add all supporting files which was listed in the document named Support Files to Include when Building a LabVIEW DSC Module Application (available on http://zone.ni.com/devzone/cda/tut/p/id/4189) link. In addition to this i also add .rtm file for viewing tool bar while running application and security.llb (available at development machine directory:LabVIEW7.0\Vi.lib\lvdsc>. But still the problem remains as it is. So my question is do i need to add any other supporting files related to DSC security tools, which can solve my problem???????
If u have any clue, kindly recommend me.
Regards,
Ratna

Labview fail to build exe for a perfect VI?

I build a small example VI,which simply uses a T/F constant to control a case structure. The false case passes through the data, the true case does a filter on the data. This VI runs fine for when the constant is set to either True or False.
However, if I set the constant to False, and try to build the VI into exe file, Labview fails to build exe and give out this error:
An error occurred while saving the following file:
C:\testfilter\Main.vi
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
<APPEND>
Method Name: <b>Save:Target Instrument</b>
If I set the constant to true, then the VI builds fine. That makes no sense, since whatever the constant value is, it should not affect the building process.Anyone knows why Labview is making this error?
Please see the attached sample project, I build it in Labview 8.6.1. Set the constant to false, and the build fails. BTW, the code does not do any real "meaningful" thing, it's just an abstraction of a complex program.
Attachments:
testfilter.zip ‏10 KB

I knew this would solve the problem, because I believe the problem is that there is a case that "seems" will never be executed, so the blocks inside the case does not get included (dumped by "smart" compiler) but somehow later needs to be referenced in the build process. If you put it outside the case structure, a copy of that block will be included anyway so later it can be referenced. I have seen similiar problems in languages like Java. Good to hear it probabily has been solved in lv 2009, so another reason to fork a few dollars to NI for upgrades...
Dennis Knutson wrote:
I got the same error. I then deleted the code in the true case, selected the low pass filter function that you had outside the case structure, and dragged a copy inside. The build was then successfull. I can't explain what was corrupt and the error message is pointing to functions you did not have.

After build exe file . the config.ini file change the path

i have config.ini in my proj
after build exe file i get that error
Error 7 occurred at Open VI Reference in Open Config.vi->Start Main.vi.
VI Path: C:\IRP Burn SW\Labview Proj\EXE Build\SWDL.exe\IRP Burn SW\Labview Proj\configuration.vi
in my proj configuration file locat in : C:\IRP Burn SW\Labview Proj\Config File\config.ini
how can i solved this problem ?

http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

Error 10 occurred at New VI Library.vi when building .exe

This is driving me crazy! What is causing this. The program worked fine in 8.5.1 and before. The only thing that has changed is that I had to create directories for each class in the Microsoft Report Generation Toolkit which was a huge pain itself. See Building an EXE in LabVIEW 8.6 using the Report Generation Toolkit application note for more information. Anyway, any suggestions would be much appreciated.

After a lot more testing I think I have identified the problem. Our executable uses the Microsoft Report Generation toolkit. Due to how LabVIEW 8.6 has implemented the toolkit, it creates directories for each class of the toolkit to prevent name collisions. Maybe LabVIEW should start using namespaces. Anyway, we did not want the code to be visible to out customers. We wanted it to be in a single executable. So I found a knowledge base article that addresses the issue. It's called "Managing the Resulting Files from a Build Containing LabVIEW Classes" and it's document id is 4OKDCDES. Anyway this article says to add .llb destinations into the build so that instead of 5 directories with exposed VIs, you get 5 .llb. This worked ok with no build issues, but then the article said to rename the .llb to .dll so the extra directories would appear to look like dlls. The first time you build this it works, but if you build it again, it fails and you get error code 10. You can then build it again and it will work. So the problem has to do with renaming the extra .llb to .dll.

Error 1003 when building exe

Hi all,
I saw a couple of thread of other people here having the same "1003 error" when trying to build an exe with LV 7.1.1
The exact text error is :
Error
1003 occurred at Open VI Reference in Dist Copy Non-VI
Files.vi->Dist Build LLB Image.vi->Dist Build App
Image.vi->Build Application.viPossible reason(s):LabVIEW: The VI is not executable.
This is all the more surprising because this error will only happen on my computer !!!
I borrowed a collegue's computer and the build went OK...
After further investigations I noticed only one difference between my collegue's computer and mine : mine has VIPM installed.
Could VIPM possibly be the source of this issue ??
PS : recompling the code (ctrl+shift+run) on my CPU didn't make any change.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Hi TiTou,
You've probably solved this by now, but if not...
A few months ago I was trying to distribute two EXEs - both of which made dynamic calls - and this error (among others) was giving me "fits". I think it can happen if the caller has loaded a VI (.ctl or .vi) that also appears in the callee hierarchy - and the version loaded by the caller is incompatable with the callee's diagram(s.) When the callee runs, it has to use same-named VIs already in memory. If you see different behaviour on two different machines, are there two different versions of the caller?
No matter what the problem really is (was,) the attached VI will try to open all the broken VIs in a hierarchy - which can be a huge help in narrowing the problem. Oh yeah, with the (broken) FP open, click on the broken-arrow to see an error-list that can (but-usually-doesn't) display helpful diagnostic info! Compile this into your EXE (caller) so it runs if there's a problem running the callee.
Cheers.
Message Edited by tbd on 01-15-2007 10:58 PM
Message Edited by tbd on 01-15-2007 11:00 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
Util.VI.OpenBroken.vi ‏62 KB

Build exe is working but the program is not

i have build an exe, everything went fine. I opened the exe and want to start the program via "Übernehmen". Then I get the attached error message. It's an old Labview Version (2009) which I converted in 2014. Do I miss sth I should add to get a successfull program via exe?
Solved!
Go to Solution.
Attachments:
items.png ‏28 KB
items.png ‏28 KB
buildexe.png ‏74 KB

Sam_Sharp wrote:
Does the application run fine in the development environment?
Does the old version of the application work on the same PC?
What happens when you run the .exe - does anything come up on the screen? Do you get any error messages?
I don't speak german so I don't understand the message that appears - but it seems to be saying something related to the 'program not installed'? Was there previously an installer that did custom actions (e.g. running other installers or putting files/registry keys in certain locations)?
1. yes, it is running fine in the development environment. There are no errors when I start the main.vi. I can open the program and work with it etc.
2. yes, the old version is working. It's 2009, I installed 2009 Runtime and I can open the .exe and work with it.
3. concerning 2009 .exe see my answer at 2. When I start .exe which is converted AND build in 2014, the first screen is working. Then I press the "Übernehmen" Button and I got the attached error. Yes, it says "the program is not working".
I don't know if there were custom actions. I got this project from a former colleague... :/

Application builder exe does not load excel

I have used application property node and invoke node to cerate a set of VIs that read and write data to an Excel sperad sheet. This works fine in when running in LabVIEW, however when I run myApp.exe as build from application builder, the data does not get logged to Excel. The file dialog appears to open the XL Spreadsheet but not data gets logged nor is any error reported?
What is going on? All the VI are in the same project folder? Is there some additional addon run-time the must be installed on the target machine? I am uisng LabVIEW 2012 on the development station with Win7 Pro and Office 2010 on both the devleopment station and the target system. Is there one document that describes using Application Builder? It was not clear that I needed both LabVIEW and VISA run-time engines to get my application.exe to run on the target. Is there something simialr I must do to get Office to work as well?

I was finally able to track this back through by starting from scratch and received an error code, which led me to this post:
https://forums.ni.com/t5/LabVIEW/Error-2147319779-Excel-ActiveX-and-Broken-LabVIEW-Icon/td-p/2354776
Deleting the "1.7" items solved the problem.

Call library node in builded exe - path problem

Hi!
I have builded an EXE with the App. Builder. In my application I use the Call Library Node, and call functions from a DLL.
I give the path of the dll with the "Current VI path", than strip the path, and add the DLL-s name. So in the CallLibNode I check the "specify path on diagram" option.
It works when I run my application on a PC that has the LV 8.5 installed.
But when I install my app on a PC that does not have it, just my setup installs the Runtime Engine onto it, it does not work, and I get errors.
Which is the proper way to give the DLL-s path, if I want my app run on any PC that does not have LV installed?
Thanks:
Waszil

Does the executable run correctly on the development machine? If not I would imagine it is a problem with how you are referencing the dll.
Have you installed all necessary support libraries you may be using throughout the program on the target machine? Are you able to confirm that the error messages are referencing to the dll not being found?
It sounds like you are referencing the dll correctly. When compiled, the dll is put into the 'data' directory within the root directory, so make sure that is there on the target pc
Message Edited by yenknip on 08-04-2008 10:42 AM
- Cheers, Ed

Build Exe

Similar Messages

Maybe you are looking for