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

Similar Messages

  • 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

  • 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

  • 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.

  • 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

  • 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

  • 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

  • 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

  • LabVIEW crashes when trying to use VISA controls

    When I try and place VISA controls onto the front panel or a constant into the block diagram LabVIEW crashes and says that LabVIEW.exe caused an error and that LabVIEW must be restarted. Is there some setup required in order to use VISA or is there something wrong with LabVIEW?

    I saw something that sounded exactly like this myself on two PC that where running some kind of "Eveidence Eleminator" software that got its hooks into everything.
    I never did get it running on those two machines.
    I saw something similar when trying to access a serial port that was hanging off of a USB gizmo.
    We downloaded the latest and greatest version of the driver for the USB to serail device
    and
    upadted NI-VISA to the latest and greatest.
    Then everything worked.
    It was just like you mentioned, LV looks fine right up until you drop a VISA control.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • LabView crashes when writting file

    Hello,
    I have a big problem with LabView. In my Vi I capture 6 waveforms from a
    DAQ Card with a SCC Module. When combining the 6 signals to an array and
    write them to an file there is no problem but there is also no time
    information. When merging the 6 signals and trying to write this to a
    file, Lab View crashes without any error code or something. Perhaps
    anybody knows a solution for this problem.
    Thanks
    Achim Kanert

    Hello,
    LabView crashes without any ErrorCode. A Popupwindows appears that says
    LabView.exe occured an error. And then the LabView process is killed
    automatically.
    Because of other problems with the same machine I decided to reinstall
    the hole system new (OS and LabView). So i hope it will be function
    after this.
    Otherwise I will try to send you a part of the vi, which causes the
    error. I only know that it dependce on the integrated Vi to write
    LabView Measerument Files, because when I take it out the System runs.
    Thank you for your answer and I will tell you if the reinstall of the
    system has solved the problems.
    Achim Kanert

  • Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

    I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
    Can you tell me why this occurs and what the solution is?

    Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

  • LabVIEW crash when saving from LV2012 to LV2011 with express VI and reopen in LV2012

    Hi all,
    Preconditions:
    Save the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" for a previous version of LabVIEW, in this case from LV2012 to LV2011
    Reopen the LV2011 VI in LV2012 according to the steps below.
    Steps to get it to crash:
    Unzip Crash.zip
    Open the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" and from there double-click (open) the "PulsedDerivative.vi" and from there double click the "Derivative dX/dt" express VI.
    LabVIEW crashes!!
    Alternatively when LabVIEW does not crash:
    Unzip Crash.zip
    Open "PulsedDerivative.vi"
    Inside the VI double click the "Derivative dX/dt" express VI.
    LabVIEW does not crash?
    Some compiler bug?
    Br,
    /Roger
    Solved!
    Go to Solution.
    Attachments:
    445b4df5-fd64-49a2-8302-f8ddf06af2d3.zip ‏62 KB
    Crash.zip ‏166 KB

    Hi Roger,
    Thank you for reporting this. I have filed CAR 390673 to our developers.
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

Maybe you are looking for