LabVIEW Run-Time Crash (2009) lvrt.dll

Hello,
I am currently experiencing a problem with an application built with LabVIEW 2009.  At random periods (often not more than once or twice a week when using the application regularly) I get a Windows error referencing lvrt.dll as the culprit.  I am having a hard time troubleshooting because of the scarcity of the problem, as well as the random nature (appearing in completely separate parts of the application, does not seem to be associated with any particular module of the code).
A little background- I have inherited the application maintenance, which has gone through many different versions of LabVIEW.  I implemented the code into LabVIEW 2009 from 8.6, which is when the error began to appear.  At that time no change was made to the source code itself, just merely built using 2009 rather than 8.6.
I apologize for the somewhat vague information; unfortunately this is all I have after working on this issue for weeks.  If anyone has any suggestions or similar experience your advice would be greatly appreciated!
Thanks

Hello Again Sean, thanks for your help.
I am running 2009 SP1.
There are other DLLs called throughout the code, but not any specific calls seem to cause the crash.  Likewise, as the crash will occur randomly throughout all of the software I suspect it is not in the code itself (i.e. this application consists of nearly 1000 VIs.  The crash has occurred while running various parts of the software, so it can't be traced to any particular party of the code via debug mode, highlight execution, etc).
I have attached a screen shot of the error message I receive.  Any other thoughts would be greatly appreciated.
Attachments:
error2.JPG ‏52 KB
error1.JPG ‏26 KB

Similar Messages

  • LabView Run-Time Engine 2009 installation failure

    Hi,
    I have problem to install Labview Run-Time Engine 2009.
    This error occur:
    Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
    Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
    Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
    Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
    (The installation of NI is VC2008MSMs x86 failed due to the following error.
    The Windows Installer Service could not be accessed. That can occur when you run
    Windows in Safe mode or Windows Installer is not installed correctly.
    Contact your support personnel for assistance.)
    I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
    I've installed Microsoft Visual C++ 2008 Redistributable x86.
    Im runing Windows XP Service Pack 3
    (Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
    I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
    So my question is:
    How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
    Best regards
    Simon
    Solved!
    Go to Solution.

    Hi,
    I have already looked at that forum issue.
    So I have already tried to delete all keys in regedit.
    The problem is, if I continue with my installation, about 10 other new issues will appear.
    And my installation will not complete, it will fail.
    The installer does not install, it will tell me that the installation failed, and it will only install a few things.
    Not all the things that I need to run my program.
    See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
    So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
    So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
    Best regards Simon
    Attachments:
    Pictures.zip ‏414 KB

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Error 1335 during installati​on of NI LABVIEW Run Time Engine 2009

    Hi,
    While installing Labview 2009, I am getting the following error.
    Error 1335 : The cabinet file 'mib100.cab' required for installation is corrupt and cannot be used. This could indicate a network error, error reading from CD -ROM, or a problem with this package.
    I tried installing the software using 2 different CD-ROMs and also from the hard-drive. I also uninstalled previous NI software and tried installing Labview again.
    Attached is the screenshot of error during installation from hard drive.
    Thanks in advance,
    Sayali D
    Solved!
    Go to Solution.
    Attachments:
    LV_Error.doc ‏153 KB

    The installation was successful after replacing the DVD drive.
    Thank you!
    Sayali

  • LabVIEW Run-Time Installer

    Hi,
    Does anyone know if it is possible to run the LabVIEW Run-Time Installer
    in silent mode?
    Best regards
    Magnus Nilsen

    "Magnus Nilsen" wrote in message
    news:[email protected]..
    >
    > Hi,
    >
    > Does anyone know if it is possible to run the LabVIEW Run-Time Installer
    > in silent mode?
    >
    > Best regards
    > Magnus Nilsen
    It is simple!
    Place in folder
    C:\Program Files\National Instruments\shared\LabVIEW Run-Time\5.1\
    lvrt.dll and ole_lv5container.dll
    Do not install RT 5.1.1 because of bug in
    Edit->Preferences: Tab [Front Panel]->Check box 1,2,3 or 4 -> Crash!!!

  • System Error 998 While loading the Labview Run-Time Engine

    Hello.
    I have a DLL made with LV 7.1 I run the dll using a C compiler and works great in WINXP, but cannot run in Win2K. Error is:
    "System error 998 while loading the Labview Run-Time Engin(c:\program
    files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
    READVOLTAGE requires a version 7.1 (or compatible) Labview Runtime
    Engine. Please contact the vendor of READVOLTAGE to correct this
    problem"
    READVOLTAGE is my function inside the dll. The runtime is already
    installed. I tried it in another WINXP running machine and works fine.

    This is actually a Microsoft bug with statically loaded DLLs. There are a couple of workarounds for it, and I have included two links below to posts that address this issue:
    Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC
    I get error 998 when calling a LabVIEW buildt DLL from MSVC++
    Kind Regards,
    E. Sulzer
    Applications Engineer
    National Instruments

  • System error 999 while loading the Labview Run-Time Engin

    Bonjour à tous,
    J’ai un PC avec un Runtime LV71.1 qui me retourne l’erreur suivante. Je ne trouve pas d’info sur cette erreur. Une Idée sur la cause ?
    System error 999 while loading the Labview Run-Time Engin(c:\program files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW
    Résolu !
    Accéder à la solution.

    Bonjour Maxime, merci pour ta réponse qui est très intéressante. Le soft est en LV7.1.1 est fonctionne depuis plusieurs années. Le PC est chez un client, dans un pays très « hostile », je n’ai donc pas accès à ce dernier. Un superviseur local m’a fait le retour qu’après redémarrage du PC ce dernier indiquait un problème, avec photo pour descriptif. Je n’ai pas plus d’info pour le moment. Je viens donc de demander un CHKDSK c: /F
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

  • System Error 31 while loading the LabVIEW Run-Time Engine

    I'm getting the following error message.  I've attached a screen shot of it as well. 
    System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
    I'm trying to update an instrument running Windows95.  What is system error 31?  I can't find anything on it using Google or the forum's search function.
    The instrument is a Romulus-IIIA from Quad Group.  I'm pursuing assistance from them as well.
    Solved!
    Go to Solution.
    Attachments:
    Winzeta Error LabVIEW.JPG ‏17 KB

    Howdy Szandstra,
    Check out this KnowledgeBase article describing what you are seeing.  Follow the steps there to correct the problem.  Have a great day, and let me know if that solution doesn't work for you!
    Sincerely,
    Chris G in AE

  • What is "LabVIEW Run Time Engine"?

    I'm trying to find the differences between two computers that I'm troubleshooting.  One of them is my development system which has the whole Development Suite installed, and the other is a test station which has LabVIEW 8.0 Evaluation Version installed.  When I was looking through the list of programs in my development system (in Add/Remove Programs), I found a program named "LabVIEW Run Time Engine" and the size is 0.11 MB that is not in my test station.  I thought all the NI components are installed under "National Instruments Software" including the Run Time Engine...
    Does anyone knows what this is?
    See-Ming

    The Run Time Engine is a library of routines that a compiled Labview program needs to run on a system that doesn't have the development environment.  It is similar to Visual Basic's vbrun.dll, which compiled VB programs need to run.
    As far as I know, the run time engine gets installed whenever you install any Labview development environment.  This engine is usually only necessary when running a Labview program compiled to an exe format.  Both the exe and the run time engine can be installed on another computer so that the program can run without having to buy another development package for that computer.
    The runtime engine is called LVRT.DLL.  Search for it.  For version 7.1, the run time engine is in C:\Program Files\National Instruments\shared\LabVIEW Run-Time\7.1\lvrt.dll
    - tbob
    Inventor of the WORM Global

  • LabVIEW Run-time 2009 SP1

    When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required" 
    The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

    Do you have administrator privileges?  Also, do you have any security programs installed on your computer that could hinder the installation?
    Applications Engineer
    National Instruments

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Attachments:
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • Include LabVIEW Run-Time Engine in C# Project Distribution

    I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
    I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
    Info:
    Development OS = Windows 2000
    Target OS = Windows XP
    C# Development Environment = Microsoft Visual Studio 2005 V8.0
    LabVIEW Version = 8.5
    Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
    Thanks for any help.
    CAS

    Hi CAS,
    One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
    With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
    I hope this helps!
    Best regards,
    Tom
    Applications Engineering, NI UK

  • Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

    I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
    ErrorCode: -17600,
    Failed to load a required step's associated module.
    LabVIEW Run-Time Engine version 9.0.1f3.
    When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
    My TestStand Engine Version is 2012 f1 (5.0.0.262).
    I'd appreciate any help on this issue.
    Roman

    Hi Roman,
    There are a couple of things you can try:
    1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
    Check if the simple VI is loadable and runs without errors in TestStand.
    If the step generates the same error, you should try a re-install of the LabVIEW development system.
    If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
    1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
    Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
    Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
    2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
        Right-click "Build Specifications" and choose "New->Application(EXE)".
        In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
        Save the properties.
        Right-click on the newly created build specification and choose Build.
    Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
    You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
    Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
    If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
    Regards,
    TRJ

  • Executable not working - Looking for LabVIEW Run-Time Engine

    This has been one of those days.
    I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
    I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
    Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
    Amateur programmer for over 10 years!

    Hi.
    Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
    There are basically 2 ways to get the run-time engine installed on a computer:
    1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
    http://digital.ni.com/softlib.nsf/websearch/369618​104E25B08E86256F54006A4E2F?opendocument&node=13205​0_US
    for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
    2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
    Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
    Good luck.
    Alejandro

  • Teststand error states that a vi failed to load in the Labview Run-Time Engine

    I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
    If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
    How do I get this VI to run on this system when it is called by test Stand?
    Thank you

    The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
    I do not have labview loaded on this system, only the run time engines from running my deployment.
    When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
    Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
    I have attached the teststand sequence if this helps.
    Thanks
    Attachments:
    QuantumDigitalBd.seq ‏13 KB

Maybe you are looking for

  • Loading of classes causing 1st time to be slow...

    Well, at least I think this is why. Here is my story: When the user clicks on a menu item, a dialog pops up. On this dialog, I have a JTree that has a TreeWillExpandListener hooked up to it. When the user clicks the JTree to expand the root node, a d

  • Multiple IDOCs

    Hi, I am Doing Multiple IDocs to File Scenario. MATMAS05 I am using as the IDOC for Both. I am sending some data from From MATMAS05 idoc1 and some other data from MATMAS05 idoc2. Both should be equated by material Number. I followed IDOCs (Multiple T

  • WorkFlow in Miscellaneous Transaction.

    I want to attach / embed a custom WorkFlow in Miscellaneous Transaction. Is it possible? Regards, Muhammad Hasan.

  • Failed to package book for print - now hundreds of links are broken

    Hi, I have a book document with 32 pages (newspaper) locally on my mac. As I always do after finishing my document, I chose to package the book for print, and save it to CC files server. The packaging process never finished, so after 30 minutes I had

  • My iPhoto '11 won't let me sort ALBUMS manually. How can I fix this?

    Recently my iPhoto just started bothering me by not letting me reorder and sort my albums manually, and this aggravates me so much because it's something I prefer, rather than sorting by daye, time, bla bla bla. Please help me with my problem