"application error" in LV8 when building an .exe .

Hi All
I am trying to build an .exe using LabView 8. I can generate a preview, fine, I can see all my files and where they will be, however
I click the build button to star building the application and the application starts build fine. I get messages like:
First "Initializing build"
Then "Preparing File", "Loading items to build", "updating libraries" and "Processing .............vi"
Suddenly just crash with the following error message pop up window:
"dwwin.exe - Application Error
The application failed to initialize properly(0X=0000142). Click on "OK" to terminate the application"
Does anyone knows what 's wrong??
Thank You Very Much in advanse

Togos,
Well at least you got it to build once. So even with the exact same settings you were unable to rebuild the EXE? That is certainly odd. Since you are able to build the example, we know that it is probably the VI that is being built that is causing the problem. I have a couple of suggestions for you at this point. The first is to try to create a new Build Specification and just use the default options to try to get the EXE to compile. Since you probably have already tried this, there is a more involved suggestion. This sounds like a very large VI, so I might suggest trying to whittle down the problem by deleting code and attempting to rebuild the EXE. Once you have deleted enough code, you will probably get down to a point where the VI will compile (hopefully before you reach an empty block diagram). At this point we can test to see if the recently deleted past of the VI will compile by itself to see if it is a specific code snippet that is causing this problem. As mentioned this is a lengthy and involved process, so before I tried this I might treat this as a VI corruption error, and try to copy and paste the Block Diagram from the problematic VI to a blank one to see if that makes any difference.
Let me know if any of that helps or if you have any other questions!
Andy F.
National Instruments

Similar Messages

Error 7 occurred when building Exe in LabVIEW2010 SP1

Hi All,
I wanted to build an Exe for my Application. When I created an Exe and give Generate Preview, I got the following warning.
Further, I tried to delete most of the code and give generate preview
I didnt get any warning but I dont know, What is that empty file under data folder? Please explain if any one know the reason
Then I build the Exe, the following error is popped up.
Error copying files.
Source: D:\Test Exe\SC\SubVIs\
Destination: D:\Test Exe\Exe\data\
source does not exist
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 7 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.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: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface."
Herewith I have attached the LabVIEW code (LV 2010 SP1) which I extracted from my Project.
I browsed our ni forum and the answers posted couldnt sort my problem.
Thanks for your reply in advance
Thanks,
Charu Praba
Attachments:
Test Exe.zip ‏9 KB

Hi Rob,
For some reason there's an issue with the link to the lvdaq.dll in your
application. The lvdaq.dll is used by the DAQ VIs from the palette -
are you by any reason calling the DLL directly from a Call Library
Function Node?
Can you please explain what changes you made to the VI that caused the
issue. It would also be a help if you submit the VIs that you are
trying to build into an executable, thanks.
- Philip Courtois, Thinkbot Solutions

Error of heads when build the .dll by visual studio 2003

I am trying to call the dll function in labVIEW which build by visual studio 2003.
while I compile the basic program in visual studio 2003,the dll will be built successfully,but if I include heads like or in my program, etc.Compiling has the error of ,so the dll can not be built.
I have trued to look for the solution in NI Discussion Forums,but havent seen the related article about the error of including .
If someone can answer this for me,that will be a great help,and I'll be so appreciate if anyone get me out
of the trouble.
Sean

I'm a little unclear about your question. What is the exact error that you are receiving and at what point are you receiving it? Is the error occurring when calling the DLL in LabVIEW or is it occurring when building the DLL in Visual Studio? Further clarification about exactly what the problem is and where it is occurring would be a big help!
Regards,
E. Sulzer
Applications Engineer
National Instruments

Labview crashing when building application (exe)

Hi,
I am trying to build an application from a simple labview (2011) vi. All the vi does is sets (boolean = TRUE) a line on the digital output card (NI 9472) when I start running the vi. The program works fine after I have coded it. But when I try to build an exe file (application) of that project, then labview crashes in the build process. Is this a known issue? please help. I am attaching my vi alongwith this email
Thanks
Solved!
Go to Solution.
Attachments:
relayProject.lvproj ‏34 KB
relay.vi ‏21 KB

I'm sorry to hear that gascars. I have downloaded your project and VI and have succesfully built an executable in both LabVIEW 2011 and LabVIEW 2012. Can you please send me a screenshot of the error you are receiving? Also, can you make a simple VI that just adds two numbers and see if that can be made into an .exe.
Thanks
Chris
Chris
National Instruments
Applications Engineer

Getting the message "Error generating preview" when building the installer.

I'm getting this error when attempting to expand the application in the installer. However, I am able to preview the built application without errors. Please see the attached screen shots. I have built this application several times before without incident. I made some modifications to the application and now I'm getting this error. What does it mean? I'm using Win XP and LV8.5.
Dave
Attachments:
App Builder Error.pdf ‏55 KB

If I understand this correctly, you are able to build the executable--it's just that you are not able to see the preview in the Application Builder. Is that right?
I searched some of our internal documentation. I found a record of a customer who also experienced the "unable to generate preview" error when upgrading to a new version. He was able to solve it by making sure that all of the VIs ini the build were saved in the current version of LabVIEW. This may be helpful for you.
Also, I would like to recommend that you create a new forum thread rather than posting on a very old thread like this one. You will generate more discussion from the other ni.com users. It also helps our R&D department to automatically keep track of how often these issues are reported.
Jeremy P.
Applications Engineer
National Instruments

Heap size full Error message displayed when build par file in Eclispe.

We are getting below error message.
[plugin-assemble] Java returned: 1
[plugin-assemble] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:107)
[plugin-assemble] at com.mslv.oms.j2ee.deploytool.automation.c.a(Unknown Source)
[plugin-assemble] at com.mslv.oms.deploytool.api.d.a(Unknown Source)
[plugin-assemble] at com.mslv.oms.deploytool.anttasks.OMSPluginAssemble.execute(Unknown Source)
[plugin-assemble] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[plugin-assemble] at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
[plugin-assemble] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[plugin-assemble] at java.lang.reflect.Method.invoke(Method.java:597)
[plugin-assemble] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[plugin-assemble] at org.apache.tools.ant.Task.perform(Task.java:348)
[plugin-assemble] at org.apache.tools.ant.Target.execute(Target.java:357)
[plugin-assemble] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[plugin-assemble] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[plugin-assemble] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[plugin-assemble] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[plugin-assemble] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
[plugin-assemble] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[plugin-assemble] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
[plugin-assemble] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
we tried various option to change Xmx & XXMaxPermSize in eclispe ini file.
-showsplash
org.eclipse.platform
-launcher.XXMaxPermSize
2048M
-framework
plugins\org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms64m
-Xmx1024m
Your help is highly appreciated.

I have a couple of recommendations, hopefully they will help:
1. In the Design Studio installation it mentions that you have to append: -vmargs -Dsun.lang.ClassLoader.allowArraySyntax=true to the shortcut created to launch it. Eclipse won't take both: the configuration on your eclipse.ini and the arguments in the shortcut, I recommend to just use the eclipse.ini
Make sure that your configuration is what you have specified by going to:
- In Design Studio open menu: Help ->About Eclipse Platform ->Configuration Details …
2. When you are using Ant to build, deploy a project you may run into Java Heap problem. You may need to increase the amount of memory Ant is allowed to use for your project, to do that:
- In Design Studio open menu: Run->External Tools->Open External Tools Dialog…
- Select the build script you want to change on the left view.
- Select the JRE tab on the right
- Set the following as VM arguments: -Xms768m -Xmx1024m -XX:MaxPermSize=512m (this is just an example, adjust the values to your computer specifications)

Error code -13 when building installer

Hello,
I need some help! I am trying to create an installer for my application; which was created with no problems; but I keep getting a message about an error code -13. I'm adding an image of the message since it is a long one. I really don't understand what the error means or how to repair it. Any help I could get is appreciated!

Hello rd.mcdt,
The following link has information about a similar problem, could you try to follow the process described on the link? Please look for error code 13 instead error code 30 and let us know if this helps.
Error 30 Occurred at CDK_CreateNewWizard_Invoke.vi.ProxyCaller When Trying To Build a LabVIEW Installer:
http://digital.ni.com/public.nsf/allkb/8E5E6C58C625B88A8625786A005B21E0
Best Regards
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

Error 8 occurred when building an executable due to file permission error?

I received this error on executable builds from two different .vis. Other .vis in the project build without incident and the message below doesn't seem to indicate the file that is causing the problem, unless it is the SPT-errors.txt file listed at the end of the 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 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.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: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files\National Instruments\LabVIEW 8.5\project\errors\Japanese\SPT-errors.txt

Hi DanielAllis,
Like mentioned earlier, there is most likely an application on the internet that you can find and use where you can see what processes are calling specific files or folders to see if that specific file is being used by anything else. It doesn't sound like this is the root of your problem, but it couldn't hurt to check. Also, I have seen a similar problem to this with someone who was using the software Subversion and Tortoise with their application. I am not familiar with this software in particular, but I have attached a link below that goes through the steps that this other person took to try and fix the same error when having this software on their computer. Let me know if any of this helps!
http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537
Regards
Noah R
Applications Engineering
National Instruments

Getting "Error 10 occurred" when building exe

I am getting the following error when trying to build an executable: "Error 10 occurred at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\Daq\lvdaq.dll"
Listed under possible reasons were:
LabVIEW: Duplicate path.
NI-488: New I/O attempted with old I/O in progress.
I made some changes and added a .vi to my program, but get no errors if I run the program from the top level .vi.
Any ideas?

Hi Rob,
For some reason there's an issue with the link to the lvdaq.dll in your
application. The lvdaq.dll is used by the DAQ VIs from the palette -
are you by any reason calling the DLL directly from a Call Library
Function Node?
Can you please explain what changes you made to the VI that caused the
issue. It would also be a help if you submit the VIs that you are
trying to build into an executable, thanks.
- Philip Courtois, Thinkbot Solutions

Labview: resource not found error code 24 when building executable using 8.20 and dsc module

I am trying to build an executable and I keep getting and error and cannot seem to figure out what is wring. The whole error is "LabVIEW: resource not found. An error occured loading "interface 3.vi" Labview load error code 24: this vi cannot be loaded because it is broken and has no block diagram."
I am using LV 8.20 and DSC 8.2. I am trying to create an executable that has the web server running for using remote panels, i have netowrk published shared variables, connecting to a fieldpoint unit, and I am using the NI system tray icon vis to load the program to the system tray.
I have my shared variable library added as a support file, as well as the lvdsc.ini, and the tray icon files. I have sleected "Enable Enhacned DSC run time support" in the app builder, did not remove any type def,etc.
I cannot get the .exe to run on my development machine or another machine, I get the same error. I tried creating an installer that installed the 8.2 runtime, dsc,fieldpoint, variable engine and manager and MAX.
I could not find anything in the help files on the dsc, maybe someone else has some hints. thanks
Kenny

Hi Kenny,
I hope you are doing well today! What is interface 3.vi? Is it possible for you to post your project over here? Also, I would recommend creating a simple DSC application; and would like you to build it. Do you still get errors?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

When building an exe I get 'Error 1051' due to not copying Labview...\IMAQ GetPalette

I am trying to build using Labview 8.5 rather than 8.6 for compatibility reasons. However, since installing 8.6 and porting my code over to that as well I am finding that now I reset up a build script for 8.5 it no longer functions. The build fails with :
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Vision\Display.llb\IMAQ GetPalette
Destination: C:\Work folder\Programs\builds\Acoustic\SamWare Application_8-5\internal.llb\IMAQ GetPalette
Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>
The file exists but gives the same error if I include 'IMAQ GetPalette' in the build explicitly having copied it to the application directory.
Any suggestions?

Hello blown_leaf,
I have been looking at the error message you have been receiving, and would like to help you. If I understand your post correctly, you have been able to prepare a Build task in Project Explorer in LabVIEW 8.6 and execute it without any problems. However, you now require a program compatible with LabVIEW 8.5, so you are building the same Build task in LabVIEW 8.5. Is this correct?
If this is the case, have you individually saved each VI for version 8.5? I also see that you are using IMAQ as part of your VI. Does your VI have multiple instances of IMAQ GetPalette within it?
Regards,
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

Best way to add inst. drivers when building an .exe?

Hello,
I am finally at the stage of building an executable out of my project. I'm using a HAL and as a consequence the build script doesn't include everything in my project. I figured out how to get the classes into the build, but I can't seem to add some instrument drivers that are in the LabVIEW inst directory (C:\Program Files (x86)\National Instruments\LabVIEW 2014\instr.lib\General SNMP Driver\snmp communication.llb). They are listed in the project dependencies:
But dependencies aren't listed in the source files section of the build script:
And I see dependencies in the source files settings section, but it isn't obvious what I need to do to include them:
I'm using LV2014 32-bit. I'm sure I could just copy the files into the project, but surely duplicating code isn't the optimal solution. Can someone tell me the proper procedure?
Thanks,
Simon
Solved!
Go to Solution.

SimonGoodson wrote:
I'm using LV2014 32-bit. I'm sure I could just copy the files into the project, but surely duplicating code isn't the optimal solution. Can someone tell me the proper procedure?
Copy? No. You just create a virtural folder that can point to the library that is sitting in instr.lib. You can then force them to be in the executable.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Why are unwanted vi files produced when building executable?

I'm using LabVIEW 9, and when I build an executable, it creates 3 unwanted folders containing a number of .vi files that I don't want to have. The 3 unwanted folders that are automatically created are:
NI_HTML, NI_report, and NI_Standard Report
Why are these folders with numerous .vi files created automatically, and where is the option to exclude these when building the .exe? Ok thanks
Solved!
Go to Solution.

I assume this is a executable build description is created in LabVIEW 8.6 (or earlier), look in your LabVIEW 2009 build settings, there should be an option 'Use LabVIEW 8.x build layout' (or something similar), this is probably checked, please uncheck.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

LabView 2010 Application Builder for EXE Always Included files are not Included

In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
Why does the Application Builder ignore these files specifications?

Dennis Knutson wrote:
The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
The Build Directory.jpg file shows the file in the Build directory that were built.
The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
Attachments:
Build Source Files.jpg ‏151 KB
Build Directory.jpg ‏125 KB
Data Directory.jpg ‏131 KB

Error 10 when building app with Report Generation _wordsub.llb in the project.

Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
This is the error I get when a set up _wordsub.llb to use of report generation in a build project.

Dave,
thanks for providing me with this information. I didn't hear about this error in the past, but I found a KB, that possibly can help you debugging the application: http://digital.ni.com/public.nsf/websearch/AF12BB5FAC27FE2186256F9400619C84?OpenDocument
Let me know, if it helped you out
Stefan
Impossible is nothing - nothing is impossible

"applicati​on error" in LV8 when building an .exe .

Similar Messages

Maybe you are looking for

"application error" in LV8 when building an .exe .