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

Similar Messages

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 crashes when building 1d digital waveform

Hello,
I don't know if it is something about my machine or if I am missing something.... When I run the VI attached below with "# of digital lines=32" Labview hangs up and I have to kill the process using the Window Task manager. If I run it with 16 digital lines , everything is ok. If I run the application several times increasing the # of digital lines, I can get to 32 without Labview hanging up.
This seems otherwordly to me....
Can anyone help?
Thanks
Attachments:
create ADDRESS one.vi ‏19 KB

I'm not sure what the "# of digital lines=32" parameter is, but I ran the code as posted with execution highlighting and the loop executed 24 time without problems. The code hung when trying to exit the loop. Yes, very strange...
You didn't mention what version you were using, I'm on V8.6.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

LabView crash when intensity graph is in P6 of tab control

Any available fixes for LabView crash when intensity graph is put on page 6 of tab control and right-clicked??

Michael,
This has been fixed in LabVIEW 6.1.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.

Hello, LV 8.2.1 notes indicates the following bug fix:
43SAIR2A Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.
I am running this version, and still have this behavior. Is there anything I may be missing, and/or certain circumstances that may still be causing this?
thanks in advance,
Darren

Darren:
I looked at the CAR ID that you mentioned and the issue has been resolved in LabVIEW 8.2.1. To verify something similar, I ran the attached VI and things worked just fine. Please feel free to send me the steps to follow to reproduce the issue you are running into in 8.2.1.
Regards,
Rudi N.
Attachments:
MixedGraphs.vi ‏15 KB

Crashes when building previews

LR keeps crashing when I try to rebuild previews. I had an issue before where I didn't see any thumbnails in the "all photographs" view, and to fix that I created a new catalog. I was able to rebuild previews for several external discs, but one disc kept crashing LR. So I installed that disc internally in my Mac Pro. Still kept crashing on build previews. Then I transferred all the files to a brand new hard drive, still inside my Mac. Whenver I rebuild the previews, the scan completes, and then I get the spinning beach ball, and then crash.
I do have a bunch of crash reports if that helps.
I'm running LR 2.7 on a Mac Pro with OSX 10.6.3. 5GB memory. I've repaired disk permissions on startup disk, and ran DiskWarrior on startup disk as well as the discs that house my photos. I've also run Techtool. In the past I've had issues with LR crashing when building Web galleries.
I would really appreciate suggestions--I've been wresting with this for days and it's very frustrating. Thanks!

More trouble: there's a catalog I can't import. I keep getting an "unkown error." And when I start the import, I'm getting strange previews with backwards text (I'm pretty sure it's instructing me to take hallucinogenic drugs) see below.

LabVIEW Crashes when Opening Project

Hey Guys,
I'm running into an interesting issue where LabVIEW crashes when opening a project. This is the second time I've run into this issue, on the same project. To get around it the first time I simply deleted and re-made my project, but since it's happened again, I need to figure out how to debug it. The symptom is that LabVIEW will crash when opening the project (sometimes I can see the "vi loading" screen) without any indication that crash has occured. It doesn't even launch the error reporter, the process just dies. Anyone know how I can go about debugging this?
Solved!
Go to Solution.

xkenneth86,
What version of LabVIEW? Have you ever had previous versions of LabVIEW on your computer? Can you attach a screenshot of the crash?
David H.
National Instruments

Labview crashes when creating large image files

I have a problem with Labview 6.0.2( I've tested evaluation version 7.0 too).
I'm constructing a very large image, for example: 4500x4500 pixels. Labview crashes when converting the pixture to a pixmap. The image is fully constructed on my screen (in a picture control), but when converting it to a pixmap (for saving the image in a known format (bmp, jpg, tiff)), Labview crashes.
I did some testing and when the number of pixels exceeded the limit of 2^24(16777216), the file 'image.cpp' crashes on line 1570. The vi to convert it to a pixmap is: P'icture to pixmap.vi'
Does someone know a workaround for this problem? Or is there a fix for it?
Thank you!

I've tested the 6i version of my VI in Labview 7.0 evalutation version. It raised an error but not the same error:
d:\lvworm\src\lvsource\compatexport.cpp(37) : DAbort: Called a routine not in the compatibility LVRT table
$Id: //labview/branches/Wormhole/dev/lvsource/compatexport.cpp#11 $
0x004BD4CB - LabVIEW_Eval + 0
0x0EB710D9 - lvs248 + 0
0x094C87A0 - + 0
So i replaced the picture VI's with the 7.0 evalutation version VI's, and it worked. It is now possible for me to construct very large image files!
I see no attached VI to test. But i guess it is also solved in Labview 7.0
I used this file to convert the picture to image data:
C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib
\picture\pictutil.llb\Picture to Pixmap.vi
And this file to convert image data to bmp:
C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib\picture\bmp.llb\Write BMP File.vi
I guess i have to write a workaround for this problem:
divide the picture in blocks of 4096 x 4096 and then merge the image data arrays of the bloks together.

LabVIEW crashes when I save changes to a particular VI.

LabVIEW crashes when it tries to compile a particular VI. I have managed to get it to work a couple of times by changing a few things and making some subVIs, but the problem keeps returning.
Is there some way to fix this or clean the VI of whatever corruption keeps occurring?
Thank you,
David R. Asher

I can think of address/hardware conflicts or something that LabVIEW cannot provide an error message. I would go with hardware/address conflicts.
Try renaming the file and executing it stand-alone. also try making it as a subvi and run the toplevel code.
Kudos always welcome for helpful posts

Internet Explorer is crashing when opening application

Internet Explorer is crashing when opening application.
Internet Explorer 7.0.5730.11
Oracle JInitiator 1.3.1.22

I was having similar issues turned out to be a problem with the Jinitiator proxy setting. If you go into Win->control panel->Jinitiator Then Proxies and UNCHECKE the 'Use browser settings' option it may fix the problem.
My Setup: Winxp SP3, IE7.0.5730.11CO, Jinitiator 1.3.1.26
I was able to open Apps using Firefox3 fine, but IE was crashing everytime Jinitiator started. Turns out it's because of how the proxies in IE versus FF were setup, so it could open via the FF browser Proxy setting but not via the IE7 proxy settings. Telling Jinitiator to NOT use the browser setting enabled me to use both IE7 and FF3
Note: My company uses a automated proxy configuration script (proxy.pac) so if you have a similar setup to this it may help.
Message was edited by:
ben jones
Message was edited by:
ben jones

Why does LabView crash when unloading my DLL (reentrant calls)?

I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine. All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
OR
Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
OR
Your DLL is only called from one, non-reentrant VI
OR
Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
Hopefully this information can help you out in some way.
J.R. Allen

"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

Using external llb when building applications

I would like to be able to update the SubVI's that an executable uses, but am having problems editing them after installation of the build application.
I am using the option "Small target file with external file for SubVI's" in the application builder, but I don't seem to be able to open the VI's present in the external library ("data.llb") after installation. I get the error message "ressoruce not found", when trying to open the file in LabVIEW. Does anyone know what might be the problem.

Caveman wrote:
> I would like to be able to update the SubVI's that an executable uses,
> but am having problems editing them after installation of the build
> application.
>
> I am using the option "Small target file with external file for
> SubVI's" in the application builder, but I don't seem to be able to
> open the VI's present in the external library ("data.llb") after
> installation. I get the error message "ressoruce not found", when
> trying to open the file in LabVIEW. Does anyone know what might be the
> problem.
Those VIs get just as much stripped of their front panel and diagram
unless you specifiy not to do that in the VI settings in Application
Builder. Without front panel you can not load a VI in the LabVIEW
editor. It is only good for calling
by reference.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW crashing when running NI-DSP VI on Windows XP

I am in the process of upgrading a software application from LabVIEW 3.1 on Windows 3.11 to LabVIEW 7.0 on Windows XP with NI-DAQ 7.2. The hardware has been replaced, the relevant hardware change here is from the AT-DSP2200 to the NI-4551.
The source code uses the NI-DSP libraries to control the DSP2200. I can't find any equivalent in the new LabVIEW (and have assumed that there is none, this is all covered in the MAXX now). The source code has been convereted to LabVIEW 7.
When the source code is opened on the Windows XP machine LabVIEW crashes. I've traced to cause of this crash to the NI-DSP code. Whenever I try to open any VI that contains the DSP code it crashes LabVIEW. I think the problem is the CNI call
inside the DSP library. When I try opening the source code on a computer that doesn't have the NI-4551 installed there are no problems.
What is the upgrade from NI-DSP to? Is there a direct mapping of NI-DSP functions to equivalent NI-DAQ ones? How is it that having the hardware plugged in causes a crash even though it shouldn't be accesssed until I run the VI?
Any help would be appreciated.
Thanks.

Hello EborLance,
The NI-4551 can use either NI-DAQ or NI-DSA as the driver. If you only have NI-DAQ installed, any program that uses the NI-DSA functions may be crashing.
There is no direct mapping of NI-DAQ functions to NI-DSA functions but you can download and install the NI-DSA driver from the website. Current DSA Drivers
Once you have installed the NI-DSA driver, you should see the functionality you were previously used to and your program should run.
Thanks,
C. Flip
National Instruments

Labview crashing when building application (exe)

Similar Messages

Maybe you are looking for