LabVIEW 2009 sp1 not responding / crash

Hi, 
    I seem to have developed an issue with LabVIEW whereby it freezes at a random point during execution. It is not a case of a VI freezing, rather the LabVIEW application itself ceases to work and needs to closed by task manager. What I have running at the time is a host VI that sends and receives data over a TCP connection to a real-time target on a PXI. The real-time application keeps running after the crash. The host system is also running 3D picture control showing some basic graphics. The whole system is controlled at a top level by a program written in C#  over a TCP connection but can run stand alone. When running stand alone the problem does not occur.
   The communication between the C# and LabVIEW works fine, yet at a random point during operation, LabVIEW freezes while the C# continues to work. This doesn't seem to correspond to a particular action by the C# program. I guess my question is, is there any likely culprit by which LabVIEW can be crashed by an exernal program where the only communication is via TCP that seems to work fine and where there doesn't appear to be excessive memory or CPU usage?
Cheers. 
Solved!
Go to Solution.

Having further investigated it appears to only occur as TCP exchange is taking place and the full LabVIEW application doesn't appear to have crashed, but several VIs hang and can't be closed. There are three total TCP connections running, one that links to the PXI unit, one to the C# application and one from the C# to the visual display VI that is idle when this event occurs. Does anyone know of any reason why a TCP connection can cause LabVIEW to hang? The same connection has worked numerous times before the error occurs. Appears to only happen when the 3D picture control is running.

Similar Messages

  • Simple Math VI crashes LabVIEW 2009 SP1

    Hi,
    We previously filed a related issue, (ref #: 7302858). The last problem was resolved by 
    Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
    However, the interesting crash happens again.
    I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
    1. Add the "Word bits" as a connector on the diagram
    2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
    Before the change, the VI was functioning all right.
    Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
    Thanks,
    Tian
    Attachments:
    Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
    Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

    Tian,
    Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it. 
    I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted. 
    <Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 
    Attachments:
    Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
    Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

  • Labview 2009 SP1 - Create exe option does not appear

    Hello everyone,
    I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other  computer with the appropiate labview run time engine).
    I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
    Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
    Thanks for advance!
    Much thanks for your time and dedication!

    I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
    The best solution is the one you find it by yourself

  • LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

    Hi,
    Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
    1) Is there a limit on the size of the exe which can be run on it?
    2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
    3) If a list of what it does or does not support is available, it would be extremely helpful.
    Thanks In advance.
    Regards,
    Vijay

    Anand, 
    I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
    http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
    It does not contain the full run-time engine, but will allow some executables to run.
    1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
    2) Can someone from NI reply to this and shed more knowledge?
    Regards,
    Vijay 

  • LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

    In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
    One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
    I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
    In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
    One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.
    Attachments:
    Connector pane.PNG ‏4 KB

    Troy K wrote:
    I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
    So you must be using crazy non-standard connector panes, or you would not have discovered this bug.  Right?   Actuall this is a good catch for it to go unnoticed for this long.
    - tbob
    Inventor of the WORM Global

  • After updating to Firefox5.1, Nvidia kernal mode driver frequently "not responding & crashed then recovered", along with crashing of the Firefox browser.

    After updating to Firefox5.1, Nvidia kernal mode driver frequently "not responding & crashed then recovered", along with crashing of the Firefox browser.

    I have the same problem. I just upgraded to Win 7, no problems. Then I upgraded to FF 4.0, and I kept getting Nvidia Video Card crashes. I always undo my last computer change/install when something like this happens, so I immediately uninstalled 4.0, and went back to my older version of Firefox. No problems ever since.

  • Labview 2009 SP1 crashes when moving large selection with arrow key

    If I select a lot (10 or 15) of Block Diagram components and try to move them some distance with the arrow key, I will frequently get a program crash.  Since a smaller number of components seems to crash after a longer travel distance, it looks like some kind of buffer overflow error.  I do not see this problem when using the mouse to move selections.
    I have checked to be sure I have the latest video driver for my NVIDIA Quatro FX570.  I have also tried working with no hardware acceleration and no combined writes.  This is happening on Windows XP SP3 with all the current updates.
    It has become so bad that I have to do a Save As every fifteen minutes to keep from losing data.
    Why don't I use my mouse for all movements?  Because it is not as accurate and not so easy to restrict to one dimension of movement.   My hand is not as steady as it once was.
    I hoping someone will have a suggestion that will clear up this problem.
    Solved!
    Go to Solution.

    As I indicated, I had the same problem with 8.5 and just DID a new installation of Labview 2009.
    Since it is possible my three-monitor setup, which obviously requires more video memory, may be at the root of the problem, I am satisfied with the workaround of dragging the objects near their final destination and then using the arrow keys.  
    Three monitors are ideal for front panel, block diagram and Help/Internet/Probe Window.  When I had to work in the field with only one monitor, I felt severely handicapped.
    You may consider the matter closed.
    Thanks for attempting to duplicate the failure.

  • Labview 2009 SP1 Installer build help needed

    Hello,
    First time posting here.  I have a rather large project that I recently converted from Labview 7.0 to 9.0.  I am able to build an executable and it starts up Ok but I don't know for sure if it works.  Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1.  The executable then complains that it needs the full development version to work.  I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
    Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer.  Here's the Build Errors from the pop-up dialog:
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    *** Error: An internal tool or library returned an error. (Error code -21)
    *** End Error Report
    *** Error: Windows SDK function returned an error. (Error code -12)
    *** End Error Report
    The build log file has slightly more info:
        [LOG ON]  Mon May 31 20:55:07 2010
    <<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
    <<<MDFConfig_SetDistributionLanguage>>> Language id: 9
    <<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
    <<<MDFConfig_SetBuildMode>>> Build mode: 1
        [NMDK BEGIN]  Mon May 31 20:55:07 2010
         Building developer part
    > Adding files to installer
    <<<MDFBuildDevPart_SetFileNames>>>
    <<<MDFBuildDevPart_SetDefaultInstallDir>>>
    <<<MDFBuildDevPart_SetUpgradeInfo>>>
    <<<MDFBuildDevPart_SetOtherProperties>>>
    > 
    > **************
    > *** Error: An internal tool or library returned an error. (Error code -21)
    Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
    nmdkSetInformationalProperties returned error code 26024
    > *** End Error Report
    > **************
    > 
    Adding product dependencies to developer part
    > 
    > **************
    > *** Error: Windows SDK function returned an error. (Error code -12)
    Closing dist kit
    ***** About to begin MAXImportConfig:oMAXPartModifications...
    No MAX import files specified - nothing to do - returning.
    Error in MDF API function: _MDFBuildDevPart_Close
    Error in MDF::BuildDeveloperPart::Close.
    ERROR: Caught MSI Exception:
    <Unable to format error record.>
    MSI error code: 6
    > *** End Error Report
    > **************
    > 
        [LOG OFF]  Mon May 31 20:55:07 2010
        [MDF END]  Mon May 31 20:55:07 2010
         Closing MDF.
    I realize that I should post my project file but I can't do that until tomorrow.  From those 2 errors, can you tell me what the installer builder is looking for?  I have gone through all my dependencies and they look Ok at the moment.
    Thanks for you time.

    Hi Celeb,
    I had to help out on another project and finally only getting back to looking at this issue yesterday.  As you suggested, I went ahead and created a new project and created new build specifications (exe and installer).  I was able to properly build both items but won't be able to check out the executable til later this week.
    I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View.  I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder.  Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly.  This might have been the cause of my inability to build an installer with the converted project/build specs.
    I hope NI could add in more details into the build error messages.  As it is, it's really difficult to know why a build failed because there's no details in those messages.
    Thanks again,
    T.

  • Labview 2009 .exe not working with windows 2000

    I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    Serial Number Reset Cell 2.vi ‏15 KB

    There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
    George M
    National Instruments

  • Image ROI ID number in LabVIEW 2009 SP1?

    In LV 8.5 (Vision), multiple ROIs had ID numbers displayed next to them:
    Apparently not so anymore in 2009 SP1:
    The only difference between the two VIs is that I was using a classic image object and I am now using the modern version;and the image tools window is replaced by the image tools palette associated with the image. There is no image property that I can find to turn the ROI "legends" on or off.
    How is the user supposed to know which ROI is which?
    Solved!
    Go to Solution.

    Ooops...: Indeed. I checked my LV 8.5 code (in fact written in LV 6 or whenever the first Image control was released) and I did overlay the ROI numbers myself at that time! 
    Since I had meanwhile used overlay to get ROI numbers, I just reinvented the wheel...twice.
    I still think that would make sense to have this feature by default in the Vision toolkit.
    X.

  • BSOD with labview 2009 sp1 on windows xp on dual core intel computer stop code F4

    I have 14 test stations with the Labview runtime engine installed.   These stations run 24 hours a day, or are supposed to,   Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4.  It seems fairly random which computer it is.
    Some other details:
    Labview version 2009 sp1, and visa 5.02 installed
    The computers are brand new Intel D510MO computers, with wester digital solid state hard drives. (Fanless)
    XP service pack 3.
    The computers aren't overheating, The ram is good, to power is stable and filtered.
    The computers seem to run fine without ni software installed.
    The only other thing installed is a serial port driver for a usb serial port converted.
    We've caught one blue screen with no Labview executable running.
    I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
    I've been working this problem for months.  Any ideas?

    John@ge wrote:
    I have 14 test stations with the Labview runtime engine installed.   These stations run 24 hours a day, or are supposed to,   Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4.  It seems fairly random which computer it is.
    Some other details:
    We've caught one blue screen with no Labview executable running.
    I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
    I've been working this problem for months.  Any ideas?
    If I am reading this correctly you have ruled out your LabVIEW program as the cause and you think it is one of the non-essential services. Which ones are still running?
    Have you looked in the Windows error logs?
    Edit: I forgot to add the link I was going to give you.
    =====================
    LabVIEW 2012

  • How to activate labview 2009 sp1 after reinstall window?

    hi
    my camputer was installed labview 2009 and it was activated by the academic license. Currently, i reinstalled the window and i cannot activate the labview 2009. So how can i activate it?

    Hi,
    In the license manager (Start » National Instruments » License Manager) you should set the correct parameters concerning your license server.
    Regards,
    Da Helmut

  • Labview 2009 would not close properly

    Hi everyone!
    I have been having problems with our recent upgrade from LabView 7.1 to 9. I have removed 7.1 completely and have installed everything that came with the installation DVD's in LabView 9. When I went to my old VI's and continued to work on them, after I have saved the VI and exited LabView, Labview would still linger in the background and do nothing. This prevents me from opening LabView again. I then would have to go to Task Manager to terminate the process. As soon as I do this and re-open LabView, I would get the pop-up window asking to investigate the recent crash.
    I am currently in contact with [email protected] as well, but they have not solved the issue so far. This is why I am seeking help with the rest of the community. I am hoping that somebody out there knows anything about this issue. I am attaching the most recent lvfailurelog I have encountered. 
    I have currently installed the most recent patch to LabView 9 and the only thing it's done is to illiminate the logging of the failure because it's no longer asking me to investigate after terminating the application from Task Manager.
    Marcos
    March 25, 2009
    Update: The problem has retuned and I have attached the most recent logfile.  Please help.
    Attachments:
    lvlog2010-03-25-13-35-08.txt ‏190 KB

    I don't know about old VIs specifically, but quite often, when I exit LV 2009 (and I think 8.6 did this as well) it takes a long time until the process dies and during that time the memory consumption of the process rises considerably. Eventually it does quit, but it just takes a while before it does (roughly two or three minutes).
    Try to take over the world!

  • I-Cal Not Responding / Crashing

    I keep on opening my i-cal & each time I try to edit one of the entries in one of my calendars or delete a calendar or a to-do then it crashes & I have to force quit. I sync my calendar regularly with my phone & I noticed some of the to-do's were corrupted today on there also.
    In addition, about 20 new calendars have appeared on my i-cal this evening with no title or information in them & if I try to delete them then it crashes after deleting about 4. I am not sure what to do to fix this problem & I need my calendar as I use it everyday.
    Help!
    IBook G4   Mac OS X (10.4.7)   i-Cal Version 2.0.3

    Visit the folllowing links to help resolve this issue:
    http://discussions.apple.com/message.jspa?messageID=3723952#3723952
    http://discussions.apple.com/thread.jspa?threadID=316681&tstart=15
    http://discussions.apple.com/thread.jspa?threadID=696740&tstart=15
    http://www.info.apple.com/kbnum/n301270

  • Not responding / crash while using proxy calendar

    Hi
    On one station the GroupWise Client crashes often while using proxy calendars. The user opens a calender trough proxy access and klick on somme entries (days). The error is not reproducable - restarting the client and do the same klicks won't crash again.
    Most of the crashes report this File: C:\PROGRA~2\Novell\GROUPW~1\gwclu.ocx
    Any help would be nice.
    grpwise.exe 11/16/2014 09:53:31 12.0.3.28451
    - GroupWise Unhandled Exception Report -
    - Generated on 4/1/2015 at 16:50:41 -
    Exception code: C0000005 EXCEPTION_ACCESS_VIOLATION
    Fault Address: 54BF63A8 01:000153A8
    File: C:\PROGRA~2\Novell\GROUPW~1\gwclu.ocx
    File TimeStamp: 11/16/14 09:54:20
    --------------Network----------------------
    Computer Name: PC-75
    User Name: gau
    --------------Hardware---------------------
    Number of Processors: 8
    Processor Type: Intel64 Family 6 Model 30 Stepping 5
    --------------Operating System-------------
    Platform: Windows NT
    Version: 6.1
    Build Number: 7601
    Other Information: S

    In article <[email protected]>, Interbit wrote:
    > Yes, one user, one machine. The machine was completely new installed,
    > still 2-3 isues per Week.
    So this rather points to the user. So the next question is what
    regular preventative maintenance do you have running?
    What I typically set of customers is
    http://www.konecnyad.ca/andyk/gwmnt5x.htm
    If you are already running the contents checks, then look at section of
    the resulting logs for that user to see what errors are showing there.
    Especially of note would be errors that are identical each time as they
    indicate there is something that needs a bit of direct effort.
    Also are there any error showing in the POA logs that coinside with
    these crashes?
    Is it always the same calendar? Are others proxying into the same
    calendar?
    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

Maybe you are looking for