LabVIEW 2010 unstable on Windows 7

I am finding that LabVIEW 2010 is fairly unstable on Windows 7 Ultimate system.
LV stopped working several times, LV tells me that it stopped working, looks for a solution and then shuts down. Like just a few minutes ago, shortly after system power up.
Several times it just closes all of the Windows and terminates without any message or error displayed.  Didn't even say goodbye.
I have even had one BSOD (which is hard to do on Win 7) almost immediately after an application was built and run. Didn't happen again when app was run again and built again.
I have only observed these problems with LV. All other applications have been running fine over the last month without unusual errors or misbehaver.
The system is only 1 month old. It is fairly clean with minimal software installed.
I don't know how much data on these problems that NI is capturing automatically. I haven't seen my system request permission to send problem reports to NI.
Has anyone else seen similar behavior with LV and Win 7 Ultimate?

I too am extremely (that's a total understatement) displeased with the behavior of Labview 2010 under Windows 7.
I get frequent crashes, some with recovery/log/.error message, some where Labview just exits. One minute I'm editing my code with 7 windows up; the next I'm staring at an empty desktop.
I too have started saving my work every few seconds. It's a royal pain in the ass.
I have turned in NUMEROUS bug reports, including samples of code that cause Labview to crash. MANY of them are related to typedefs. I just found another one and will be turning in that bug report within minutes. In this case I have a typedef (NOT strict) that contains only a combo listbox. If I right-click on the combo listbox, Labview silently exits and does no recovery or logging when started back up.
I have lost SOOOOOO much time trying to create code while fighting numerous Labview 2010 issues. The most egregious (to me) is that I have a control (I *want* it to be a strict typdef) that when I drop it on the Labview block diagram, Labview crashes. Yes this has been reported. I had to change the control from 'strict typedef' to 'control' to use it. The result is that every time I have to modify it (it's a work in progress) I heve to go thru my code and change over 60 occurrences of that control. By hand. If it was a typedef, I would change it ONCE.
I have a customer I'm developing Labview code for; I find it both personally and professionally embarassing to be missing deadlines for delivery, and blaming Labview instead of myself. But I have 3 pages of bug reports online with NI; each one cost me between an hour and 3-4 days of time. Many of them required me to redesign code I'd alrady written to avoid using constructs in Labview that simply don't work.
I'm glad to know I'm not alone - but absolutely dismayed that the code base for Labview 2010 is so buggy under Windows 7; it may be buggy on every platform, but that's all I'm using.
NI tech support has been helpful; but only to a point. They routinely generate correction requests based on my bug reports; not one has resulted in a patch from engineering to date.
I've been a software engineer for over 35 years. This is probably the 2nd worst experience with an IDE that I've had. The first was with a Sun product that was supposed to generate user interfaces; it simply was crap. Labview is dismayingly similar. If I'd elected to write this application in C I'd not only be finished, but it would have taken 6 months less on the calendar. Some of that is due simply to the way you have to construct and enter code in Labview; but in my case, most is due to failures of Labview to work as documentd, or to failures in the Labview documentation to explain what Labview is really doing (yes, I've turned those in too).
Here's an example of a Labview crash: open this VI and right-click on the listbox on the front panel. Make sure you do NOT have any other Labview code open at the time...!
Gary Sloane
SB/US Engineering Inc.

Similar Messages

  • Is it possible to build a project with Labview 2010 on a Windows XP system, that is useful for a system with windows 7 on it?

    Hi there,
    I am planning to use Labview 2010 in a short time.
    But before I'm going to use it I have some questions.
    I know it is possible to run Labview 2010 in an XP environment. But is it also possible to, when running Labview 2010 on a XP system, to build a project to a version that is useful in a Windows 7 environment?
    Or do I have to run Labview 2010, when I want to build a project that is useful on a Windows 7 system, on a system with Windows 7?
    Please give me some information.
    I hope to hear from one of you soon.
    Go to Solution.

    Is it possible to build a project with Labview 2009 on a Windows XP system, that is useful for a system with windows 7 on it?
    Philippe B.
    Certified Associate Developer / Dépt Moyens d'essais

  • Labview 2010 crashes XP while looking for webserver

    I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable.  I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
    I've gone into the Windows Event Viewer and there is an event that says "Labview information:  Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL     ."
    I'm attaching a jpg of the Event in case I typed it incorrectly.  There is another post that mentions this error but there is no resolution and the discussion went in a different direction:
    Neither my Win 7 development laptop or my target Win XP system have this www folder.
    Has anyone seen this before or know the cause?  Thanks.
    Event Viewer small.jpg ‏69 KB

    Thanks for the quick reply.
    Yes, the time stamp of this error coincides with the crash.  I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer.  Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
    This only happened on time and I have not been able to reproduce it again.
    I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again.  Do you have any suggestions?  Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.

  • Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version and exception code c0000005

    I build an application exe and then its installer along with run time environment.
    The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash. 
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: AGMS.exe
    Application Version:
    Application Timestamp: 4c24e8f5
    Fault Module Name: lvrt.dll
    Fault Module Version:
    Fault Module Timestamp: 4c9273f4
    Exception Code: c0000005
    Exception Offset: 00005310
    OS Version: 6.1.7601.
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    If the online privacy statement is not available, please read our privacy statement offline:
    I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
    Language: English (Regional Setting: English)
    System Manufacturer: Dell Inc.
    System Model: Dell System XPS L502X
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
    Memory: 8192MB RAM
    Available OS Memory: 8106MB RAM
    Page File: 3457MB used, 12753MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: LENOVO
    System Model: HuronRiver Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
    Memory: 4096MB RAM
    Available OS Memory: 4010MB RAM
    Page File: 1359MB used, 6658MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
    This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
    Now as I see it, it could be a Run-time environment mis-match error.
    For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
    I checked DEP, for all 3 PCs and it was set to the following
    Turn on DEP for essential Windows programs and services only (first option).
    I am confused. I can not find a solution for this and it is really frustrating.

    But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
    Since from the picture you can see its including the support installers from '\Program Files (x86)\'
    The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
    I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
    Yes I did reboot every time after I ran the installation.
    Still getting the same error.

  • Conexión tarjeta ni6008 a pc con windows 8 y labview 2010

    Hola. Soy nuevo en labview, y estoy intentando conectar una tarjeta de adquisición de datos NI 6008 a un pc con windows 8 y labview 2010, le he instalado los drivers, y todo ok, pero cuando intento hacer una prueba con Measurement & automation, me aparece que no hay ningún dispositivo conectado... no se donde puede estar el fallo, o si hay que hacer algo más... Gracias de antemano

    hola goku, 
    intenta revisando esta ayuda, para descartar problemas con las versiones del driver NI-DAQmx:
    Por qué no Puedo Ver mi USB-6008/6009/6501 en MAX Después de Instalar NI-DAQmx 7.5 o Posterior?
    Espero que te ayude. Saludos !
    Patricio Cortes
    Ingeniero de Aplicaciones | National Instruments Cono Sur

  • Labview 2010 randomly restarts computer - windows event viewer points to nap agent

    When running my current VI that I am working on, the computer will ranomly reboot. There is no freeze, or blue screen, just a reboot. When examining the windows event viewer after the reboot, the following warning is listed immediately preceding the reboot:
    Event ID 39
    The Network Access Protection Agent was unable to determine which HRAs to request a health certificate from.
    A network change or if GP is configured, a configuration change will prompt further attempts to acquire a health certificate. Otherwise no further attempts will be made.
    Contact the HRA administrator for more information.
    Previous to getting this warning before a reboot, I was getting the following error:
    Event ID 10016
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18).  This security permission can be modified using the Component Services administrative tool.
    This is a DCOM service eror and the CLSID is referring to NAPAGENT. So I configured DCOM to allow the NAPAGENT to start and now I get the Event ID 39 warning and still get the reboot.
    I am not sure why labview is even asking for DCOM or NAPAGENT to start at all. My VI is simply reading information from two serial instruments.
    This reboot behavior does not occur when the computer is not running labview.
    I am attaching a copy of the main VI, if it will be helpful I can post the sub VI's as well.
    Thanks in advance for your help.
    -Justin Lee
    Attachments: ‏179 KB

    Hi Joe,
    Thanks for the reply.
    I am running windows XP pro service pack 3.
    I am running a standard instal of labview 2010 with the latest VISA drivers, no other modules or options installed.
    I am only reading and writing to the serial ports (com) in my code. I don't believe that virus/spyware/malware is to blame for several reasons.
    1. This only occurs when running this VI in labview.
    2. I have replicated this problem on another computer.
    3. I am behind a government (DOE) firewall and virus scans and checks are performed constantly.
    4. If I take out the serial portion of my code via a T/F case structure, it will not crash.
    The code will run fine for sevetral hours sometimes and then crash, other times it will crash after only a few minutes.
    Please let me know what other information you require.
    Justin Lee

  • Using LabVIEW 7.1 and LabVIEW 2010 on the same PC (Windows XP)

    I have LabVIEW 7.1 on a Windows XP 32-bit PC and we plan to upgrade to LabVIEW 2010 soon. A lot of our software is using Traditional DAQ, DAQmx and DeviceNet. We need to use both versions of LabVIEW for some time on the same PC. Is this possible at all?
    I installed an evaluation 2010 version and now I don't have DAQ and DeviceNet in LabVIEW 7.1. Any suggestions will be very helpful.
    Thanks, Nick
    Go to Solution.

    For what it is worth, I tried having multiple versions of LabVIEW on the same PC.  If you are (very) careful, it is possible to do so, as long as you are only doing development work, i.e. you don't try and install LabVIEW drivers.  However, as I've discovered to my great sorrow (which involved installing and removing various versions of LabVIEW on the same machine probably 5-8 times, eventually leading to wiping the machine and installing WinXP all over again, then only one version of LabVIEW), if you want to actually run your code, particularly if it does anything with hardware, you need to stick to one version!
    There's another "gotcha" for those of us working with "older" versions (namely before 2009, though one can "trick" 8.6 if you're careful) -- Windows 7 doesn't "play well" with the older software!
    So my development machine runs Windows 7.  I have a VM of Windows XP in which I installed LabVIEW 7, which I use for my "legacy" work -- I use the Win 7 machine for LabVIEW 8.6, 2009, and 2010 development (and only development, see above).
    The machine that got "rebuilt", where I wanted to run LabVIEW code for various hardware and potentially various LabVIEW versions, I did a really nutty thing -- I created a quadruple-boot PC!  (It really is a triple-booter, as the Windows 7 system, which is the key step, is "hidden").  To make this work properly, I needed three hard drives in the machine (one for each OS -- I might have figured out how to put two XPs on a single drive, but since I already had the disks, one-OS-per-disk seemed easier).  I'm using Windows 7's Boot Loader to give me the startup choice of which system to use (the message says something like "System for Hardware A", "System for Hardware B", "Test System").  True, you need to do a Restart, but since you're going to be collecting data, it's not such a bad idea to start with a "fresh machine".
    [I did think about doing this with Virtual Machines, which would have been much simpler, but I didn't have "virtual drivers" for the hardware!  One piece was actually a USB device, but the other was a proprietary device that plugged into my PC ...]

  • Labview 2010 crash at startup windows 7

    Labview crashes on startup. I get this message: "Labview 10.0 Development System has stopped working." I don't get any further than this.
    I have 95 computers running Windows 7 64-bit Enterprise. To install Labview on these I use the automated installer with these options: "/q /acceptlicenses yes /r:n /applyspecfile k:\zfdmsi\Labview2010\yellow1\".
    This was working on Windows XP. I have tried to install Labview manually on one of the windows 7 computers and it works fine.. But I cant do that on 95 computers...
    Any ideas why it's crashing?
    Thanks in advance.
    Go to Solution.

    Yes, m: is a network drive. We have a local policy on all workstations redirecting My Documents to the M: drive.
    I got the issue resolved by installing Labview 2010 SP1

  • Tftp on Labview 2010 and windows 7

    I am having difficulty running tftp on my Labview 2010 on windows 7 using the system exec vi. I already enabled tftp client on windows 7. What is interesting is that tftp runs when I execute it directly from the command prompt but gives an error when I try using the system exec vi. The error says tftp is not recognized as an internal or external command, operable program or batch file . Please help. I have attached the vi I used
    Attachments: ‏8 KB

    If you use system exec, you either have to specify the entire path to the executable or if it is a system utility, launch the Windows Command Shell utility first with "cmd /c" and prepend the rest of your command after that. System Exec is NOT the Windows command shell but simply a way to spawn a new process. As such it has no notion of "Windows", "System32" and what else directories to search for unqualified command utilities. The only paths it probably will recognize for such unqualified commands is the "current directory path" and possibly the directories in the PATH environment variable. It won't look for directory paths that are specified for the Windows Shell in the registry.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Wdapi900.dll error on windows 7 while running labview 2010 executible

    Hello All,
    I am trying to run a "1.exe" on a windows 7 PC created from a Labview 2010 version.
    It gives me a following error
    "The Program cant start because WDAPI900.DLL is missing from your computer"
    However the previous version of labview 2009 "2.exe" file works absolutely fine on the same Windows 7.
    I tried running the Labview 2010 "1.exe" file on Windows Vista and it runs absolutely fine.
    Any ideas?

    I created another .exe file from LV 2010 and ran it on win7 PC.
    It ran perfectly fine.
    The difference between this file was, i was just using a serial port for communication.
    On the other program i was using a winI2c interface along with options to choose from NI 8451 and serial interface.
    The error messages i am getting are as attched.
    Error 1 is the 1st message i get as soon as u open the program.
    After pressing OK, i get a bunch of other error messages as shown in Error2. 
    I have already installed latest Win-I2CUSB on win 7 machine.
    error.jpg ‏30 KB
    error2.jpg ‏14 KB

  • Printing LabView 2010 in Windows 7

    I recently upgraded to LabView 2010 and Windows 7 and now I cannot print my anything from within LabView, I have to pdf the page and then print the pdf.  All other applications print fine.  When I print from LabView I get the following on my printer:
    PCL XL error
    Subsystem: KERNEL
    Error: Illegal Tag
    Operator: PassThrough
    Position: 15

    Are you using 64-bit or 32-bit LabVIEW and are you using 32-bit or 64-bit windows?  
    You mention you get that error text on your printer, is that on a display screen on the printer or does it actually print that?  
    How are you exporting it to a PDF?
    Have you tried printing to any other printer other than HP?  I remember last year someone had a really strange printer issue that only affected HP printers on LabVIEW 2009 32-bit in Vista 64-bit.  I was able to reproduce it with pretty much any HP printer, but other printers worked fine.  Maybe this is somehow related.  
    David_L | Certified LabVIEW Architect
    LabVIEW Tools Network | LabVIEW Tools Network Developer Center

  • LabView 2010 application runs twice as slow in Windows 7

    When our company mandated the replacement of Windows XP PC's, my LabView test application that was compiled in LabView 2010 runs over twice as slow on a Fujitsu Esprimo E710E86+ machine. The application uses a GPIB USB - HS adapter to control an HP 4285 Impedance analyzer whose signals are switched to it using two (2) SCXI chassis that contains five (5) SCXI-1193 switch modules. This chassis uses the USB-1359 communicator.
    On the Windows XP machine that is being replaced (a Dell Optiplex 960), a typical set of measurements takes around 40 seconds to complete. The new Windows 7 machine takes about 100 seconds to do the same set of measurements. Has anyone noted this increase in test time???
    Thank you.
    Rod Johnson
    Test Engineering
    FujiFilm SonoSite Inc.

    Hello Rod,
    Before updating to LV 2013 I'd recommend isolating what components are causing the slowdown or at least trying to eliminate some of the variables - right now there's a new PC, new OS, new physical connections, and perhaps even new hardware, so figuring out which of these is causing the slowdown should be the first order of business.  I've seen issues simlar because USB devices were switched around to different (built-in) ports on the same machine.
    A few things to check:
    -What does this application do?  Are you doing any intensive data manipulation or is this mostly a call-and-response type application?
    -What does your system resource utilization look like on the two machines?  In either case, are you using more or less RAM on one machine or railing one or more CPUs?
    -Do you see the same sort of performance hit on a Windows 7 installation on an Optiplex or similar machine?
    -Did you change drivers when you upgraded to Windows 7? 
    -What NI driver version(s) are/were you using?
    -Does this application log data data to disk or perform any network operations?
    -Have you attempted recompiling the 2010 executable on "new" hardware?  The LabVIEW compiler will optimize for the platform it is being built on and it seems highly likely that the Dell and Fujitsu machines have different processors.  As a note I've never seen recompiling in this fashion result in a 100%+ speedup.
    -Have you taken a look at the machine's I/O traces to see how long the acquisition itself takes?
    -Have you tried moving the USB connections to different ports?  Most desktop PCs nowadays have one hub on the front and one on the back of the machine, although I'm not familiar with Fujitsu desktops.  If the adapters you are using or anything else on the machine is forcing a USB 2.0/3.0 port to 1.0 or something this could be a factor.
    Tom L.

  • Running the latest Labview 2010 on new computers (Windows 7) but have the older/olde​st NI ELVIS hardware

    We are running the latest Labview 2010 on new computers (Windows 7) but have the older/oldest NI ELVIS hardware (NI ELVIS I?).
    Labview works great and the device drivers are installed.
    Which NI ELVIS software do we install?
    The latest version states that it is for the ELVIS II and III hardware,
    Go to Solution.

    The ELVIS software installed fine and the ELVISmx Instrument Launcher runs fine.
    However, when I try to run an instrument, we get the following error (See Attachment):
    Error -200220 occurred at ALVISmx_DAQmx
    Create Channel (AI-Voltage-basic).vic4
    It seems that the software can't find the DAQ card which is directly hooked up to the ELVIS unit via a cable
    We aren't using USB. 
    I noticed that the newer ELVIS units use USB only.
    Is there a setup to make it recognize the card?   There used run with the older ELVIS software when you clicked on Continue in the error box.
    The PCI-6251 card checks out fine with MAX.
    Doc1.docx ‏1399 KB

  • LV runtime error in file C:\Program Files\National Instruments\LabVIEW 2010\CCodeGen\libsrc\os\rtx\LVThreads_rtx.c

    I tried to run my application on LM3S8962.
    The build succeeded. All LEDs are green,
    but the application doesn't run.
    The error message appears in the status window:
    [17:06:21] Status: Build Succeeded.
    LV runtime error in file C:\Program Files\National Instruments\LabVIEW 2010\CCodeGen\libsrc\os\rtx\LVThreads_rtx.c at line 141: 2 19
    This message isn't really enlightening to me.
    Doesn't anyone know how to solve the problem?

    Hi Peter,
    i tried to modify the code to isolate the problem.
    With the attached code the new error message appears:
    LV runtime error in file C:\Program Files\National Instruments\LabVIEW 2010\CCodeGen\libsrc\blockdiagram\CCGClusterSupport.c at line 141: 2 13
    What are the limits of clusters in LV ARM?
    My Toolchain:
    Tool Version Numbers:
    Toolchain:        RealView MDK-ARM  Version: 4.11
    Toolchain Path:    BIN40\
    C Compiler:         Armcc.Exe       V4.0.0.728
    Assembler:          Armasm.Exe       V4.0.0.728
    Linker/Locator:     ArmLink.Exe       V4.0.0.728
    Librarian:             ArmAr.Exe       V4.0.0.728
    Hex Converter:      FromElf.Exe       V4.0.0.728
    CPU DLL:               SARMCM3.DLL       V4.11
    Dialog DLL:         DLM.DLL       V1.19a
    Target DLL:             BIN\UL2CM3.DLL       V1.63
    Dialog DLL:         TLM.DLL       V1.19a
    Attachments: ‏463 KB

  • Labview 2010 run-time engine silent install

    I am having trouble with installing the run-time engine for LabVIEW 2010 with the silent option.
    I am using the minimum version of the run-time engine.
    Before I used the LV7 run-time engine. Then I could install it silently using LVRunTimeEng.exe /qb!
    In LabVIEW 2010 the run-time engine is no longer a single file but a directory that contains the installation files. There are two files that can be used to launch the installer Setup.exe and LV2010runtime.msi.
    Setup.exe does not seem to accept any command-line arguments. LV2010runtime.msi however accepts the command-line arguments and can be installed silently.
    Now my problem is that I am building a windows installer using a third party application and it is only possible to launch exe files after the installation completes. Before I could launch the LVRunTimeEng.exe /qb! to install the labview 7 run-time engine but now when I have upgraded to labview 2010 I cannot do the same for Setup.exe.
    My question is if it is possible to use the Setup.exe file to install the Labview 2010 run-time engine (minumum) silently?

    Setup.exe runs a number of other .exe files during its execution.  This article looks like it will allow you to run setup.exe silently by supressing all messages and windows:

Maybe you are looking for