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

Similar Messages

  • 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 Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

    I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs.  This happens near the beginning.  Is there a compatibility issue?  The window does not have any error messages.  It says: "Updating System, The features you selected are currently being installed."  The progress indicator blinks periodically, but does not move forward.  Please help.  Thanks!

    I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
    Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
    Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

  • LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

    I'm having a problem building an installer in LabVIEW 2011SP1.
    It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
    Now when I try to build the installer I get "The build was unsuccessful."
    Possible reasons: Error generating preview for My Application 3.1.7.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    *** Error: An internal error occurred for which the cause is unknown. (Error code -41)
    *** Error Details:
    Error in MDF API function: _MDFCommon_GetNextLogMessage
    Error in MDF::GetInstance - MDF static instance is not initialized!
    *** End Error Report
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
    Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
    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.

    I do have the LabVIEW 2013 discs but didn't install it.
    I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
    I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
    Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
    So now I need to distribute 2 runtimes with my application?!?!
    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

  • Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

    Hi,
    a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
    (window title)
    Microsoft Visual C++ Runtime library:
    (message box text)
    Runtime error!
    Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.
    http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
    I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
    Do you know this behavior and do you have any ideas how the problem can be solved?
    Thanks in advance.
    Best regards
    Manuel
    Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
    Solved!
    Go to Solution.

    Hi there
    log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error. 
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

  • Installer Error of LabView Run Time Engine 6.0.2 "premature"

    I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
    The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
    Does anyone know what to do is ?
    Thanks for Help

    It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
    J.R. Allen

  • Pdfcreator invokes LabVIEW run-time engine installer!

    Okay, so I'm a desktop tech, know little about LabView, but can at least install it.  We also use pdfcreator on our desktops.  For some reason, however, whenever pdfcreator is used (for ANYTHING, not just LabView stuff), a windows installer fires up, "please wait while windows configures NI LabVIEW Run-Time Engine 7.0."  The installer proceeds, then gets stuck while trying to find the msi.  Well I don't HAVE the proper MSI apparently, because my version is 7.1.1!  When I put in the 7.1.1 Run-Time CD (the only one I have) and point it to the msi it seems to be looking for, it still fails (apparently due to different versions).
    So first, why is pdfcreator invoking this installer in the first place (they seem to have nothing to do with each other!)
    Second, why is the installer looking for the Run-Time for 7.0, instead of 7.1.1?
    Help! 
    Thanks,
    Wiltony

    Well, I fixed it.  I eventually used the NI Software Add/Remove item, and chose "repair" for NI LabVIEW run-time 7.0, which called for the appropriate 7.1.1 device driver discs (strange).  After it completed, everything worked fine.
    Wiltony

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

  • 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

  • Unable to locate the LabVIEW Run-Time engine

    Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
    I can't go forward or backwards!
    Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
    In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
    At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
    What could be causing this problem, and how do I get past it??
    Thank you.

    One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
    The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
    I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
    Good luck.
    Dan

  • 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

  • Unable to locate labview run time engine (lab view 8.5)

    Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe  I have the following error message:
    Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
    What I'm missing??
    Thanks
    Maurizio

    are there one other reasons why it would not work.  I have asimilar problem.
    I intsalled version 8 of run time engine and acrtivated software.  Now I am trying to run compiled application provided to me by third party.
    When I click on application it says
    Unable to locate LV run time engine
    Test server requires a version 6.0 or compatible LV engine.
    How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • 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

Maybe you are looking for

  • Audio doesn't work on some programs after boot (sometimes)

    Check new message dated 30.06.2014 Hi, I'm having a weird problem. After booting my computer, the audio sometimes works perfectly, sometimes not at all, and sometimes it works on some programs but not on others. For example last night audio played wi

  • Can't access tables in PL/SQL package

    I'm trying to create my first package/stored procedure. Been to class, so I don't think the problem is with me. In a real environment now. My schema/user has access to tables in another schema, plus create procedure priviledges. I compiled the packag

  • Can't see imported Photoshop jpegs in iPhoot 6

    I have done some work with RAW images in Photoshop, saved them as jpegs with new alpha names and then attempted to import them into iPhoto, but cannot see them in the Library. When I try to re-import them, I get the message "Unreadable File - 1. The

  • Dropping internet when I get a call on my vonage telephone system

    Every time I get or make a call through my voip (vonage) I lose my wireless connection..I have a wrt150n router. I use a corless phone with my vonage system. Is there any way to stop this from happening?

  • Out put of subcontracting challan

    Hi Gurus I am facing a problem. I have configured diff output type for my two plant to print subcontracting challan & same i have assign in CIN setting subcontracting attributes. For J1IF it is working i am able to print subcontracting challan but i