NI Vision Run-Time Engine 8.2 - Error user is now getting when attempting install of built software

I've built an installer for an application using LabVIEW 8.2 and Vision8.2.  I have sent this installer to someone for 6 months and they have had no problems completing the install. 
Now the last time that I sent the installer, the user is getting the attached error during install.
"NI Vision Run-Time Engine 8.2
Error: Another installer or uninstaller is running.
Finish that installer or uninstaller and try again."
When the user clicks OK to this error, the user is then told to restart or finish uninstall.  Since we do not know what uninstall is being asked for, the user restarted the computer and attempted running the software - to which he was prompted for LVWA.dll file and he did not know what to do from there.
I gave the installer to a second beta-tester - the same thing occurred.
The only thing 'of significance' that has changed in my software that I can think of that is Vision related is the inclusion in the software of the ability to read/write .TIF files.  I have no clue whether that might have anything to do with the error.
Any help is appreciated.  NI - I can post the installer ZIP to your ftp site if you want.
Sincerely,
Don
Attachments:
error.jpg ‏30 KB

Hello Don,
Have you tried uninstalling the previous Vision run-time
engine on the deployed computer before running the new installer?   You
might also want to try running the Vision RTE separately from the installer to
see if you are able to manually run it on the target.  Here is a document which explains the
procedure for both manually installing the RTE as well as how to include it in
the LabVIEW installer:How do I
Deploy LabVIEW 8.0 and 8.20 Applications with NI Vision 8.0 and 8.2?
  I also found
a Knowledge Base that may be helpful addressing the error you mention in your
first post.  I hope this helps.
How Do I
Correct the "Another Installer Is Already Running" Error Message?
Regards,
Vu D

Similar Messages

  • Programatically determine if Vision Run-Time Engine Activated

    I am working with an application that requires the Vision Run-Time Engine.  After installation, if the Vision Run-Time Engine is not activated I get a pop-up (Vision Evaluation notice) that is behind my main application window.  The pop-up is launched when I am running an analysis with the application (I assume the pop-up is invoked when I am calling a Vision Development VI).  It appears to the user as if the application hangs.  I can force the pop-up to be frontmost so the user will see the window.  However, I'd like to be able to programatically determine if the Vision Run-Time Engine has been activated.  This way I will not have to continue to poll for this window after it has been activated.  Is there a way to do this?
    Also, suggest that this pop-up window should be made front most so this work around isn't necessary.  Please take a look into this NI R&D.
    Thanks!
    Brooks

    Hi Brooks, 
    You should be able to probe the error wire and look at the error message to see if the RTE is activated or not. This is the standard way of programatically checking to see if a license exists. 
    -N
    National Instruments
    Applications Engineer

  • How to install Vision run-time engine to a desktop PC converted to real-time target

    Hi, all
    I don't know how can I install the vision run-time engine to a desktop PC which I converted to a real-time target.  The same problem applies to installing real-time run-time engine and labview run-time engine to the real-time target.  The only way to install software to real-time target is through "add/remove software" in MAX for remote system, but it is not for all types of run-time engine installation.  
    I am also confused about how to activate those run-time engines for the desktop PC as real-time target.
    Please help and great thanks.
    Wei 

    Hi turtle,
    Here is a link that explains how to set up a desktop PC as a real-time target.  The section for Formatting & Setup should help you the most.
    NI Developer Zone Tutorial: Requirements for Desktop PCs as LabVIEW Real-Time Targets
    Justin D.
    Applications Engineer
    National Instruments

  • Does Vision Development Module obviate the need for the Vision Run Time Engine?

    I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated.  In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons).  Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs.  I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers.  I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine).  Does this mean the engine is already installed and ready to run compiled applications?  Or do we need to pay for the engine on each computer?

    The Development module includes the RTE for that machine.
    For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
    http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • Licence NI VISION Run-Time Engine

    Bonjour,
    Je vous envoie cette question parce que malgré le nombre de doc que j'ai pu trouver en relation avec ma question, je n'ai pas eu de réponse clair à mon pb :
    Je possède une application qui a été développé avec LV 8.2.1 faisant appel à des fonctions issues de NI IMAQ 3.7. (Très brièvement le programme acquiert des images provenant d'une caméra, réalise des opérations simples sur les images et enregistre les resultats de ces opérations, donc d'autres images).
    J'aimerai savoir quels sont les licences que je dois acheter pour installer la version compilée de mon prog sur pc client (qui ne possède pas LV). (Je sais deja que je devrai acheter pour chaque PC client une licence IMAQ 3.7 mais concernant le traitement de ces images puis-je me contenter de NI VISION Run-Time Engine 8.2.1 qui me semble-t-il est gratuit de la même façon que NI LABVIEW Run Time Engine 8.2.1)
    Merci d'avance pour vos réponse qui je l'espère m'aideront à voir plus clair entre les IMAQ vision, vision run-time, VISA Run-time....
    Solved!
    Go to Solution.

    Bonjour fabrice91,
    Le NI-VISION Runtime est disponible au téléchargement et ce
    gratuitement, cependant lors de  l'installation
    il te faudra l'activer. Lorsque tu crée un exécutable LabVIEW n'intègre pas
    automatiquement de Run Time Engine, c'est pourquoi il te faut créer un
    installeur qui contiendra le RTE de LabVIEW et de NI-VISION. Si tu lance l'exécutable
    sur le poste de développement il est normal que ton application tourne car tu
    as tous les Runtime nécessaires sur ce poste. Par contre si tu essaye de lancer
    ton application sur une machine où il n'y a aucun logiciel NI ton exécutable ne
    devrai pas fonctionner et c'est là que vient ton installeur. Pour connaitre les
    programmes National Instruments installés sur un PC tu as plusieurs
    possibilités soit de passer par Measurement & Automation Explorer soit
    Démarrer >> Panneau de Configuration >> Ajouter/Supprimer des Programmes
    >> Logiciels National Instruments.  
    Benjamin R.
    R&D Software Development Manager
    http://www.fluigent.com/

  • LabVIEW Run-Time Engine 6.0 Error 1606

    I try to install LabVIEW Run-Time Engine 6.0 on a PC running Windows Me. As soon as the installer wizard apear, the message follows "can't find network location ..\. Error 1606

    Hello,
    There is an article in the NI KnowledgeBase describing this problem. I recommend you visit www.ni.com/support and search the KnowledgeBase for "1606".
    The KnowledgeBase is the best place to start when you have technical support questions like this. Good luck and have a nice day.
    Darren
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Does Labview run-time engine 6.0 application created by Windows NT/2000 can install & run on UNIX

    LabVIEW exe created in Windows and running in UNIX

    LabVIEW source code from one OS can be ported to another OS (except for OS specific things like ActiveX) but executables cannot. You would need the unix version of LabVIEW and it's app builder to create an new exe.

  • 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!"

  • Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE

    What's going on here?  I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer.  When I open VB6, I always get what looks like a Windows Installer error:
    First, it asked me for the location of "lvruntimeeng.msi", which I located for it.  The next progress-window says:
    NI LabVIEW Run-Time Engine 7.11
    Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
    Finally it fails with this error-message window:
    NI LabVIEW Run-Time Engine 7.11
    Error 1334.  The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'.  This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
    [OK]
    The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay.  What can I do to prevent this error?
    Message Edited by citizenDAK on 04-23-2008 01:34 PM

    Yes it occurrs every time I launch VB6.
    For a long time now, at least many months.  It's not every day that I need to open good old VB6.  I was hoping it'd just 'go away' but it hasn't.
    I don't know what changes lead up to it.  LOTS of things have been updated, security-patched, etc...  (It is XP.)  I've even un-installed the runtime, then re-installed it when I kept getting the same prompt.  Don't have any idea why, I was hoping you could tell me from the specific file named in the error.  (Google didn't find it for me, and neither did searching ni.com)
    p.s.,  Sorry I left out a decimal and copy/pasted it several times...  should've said "NI LabVIEW Run-Time Engine 7.1.1"

  • Uninstalling LabVIEW Run-Time Engine 6.1

    Hi, I get an error message during uninstalling NI LabVIEW
    Run-Time Engine 6.1:
    Error 2727 NETSCAPEPLAGINSDIR
    How can I fix this problem?

    Armen,
    Here is my guess as to what happened:
    1. You had Netscape installed on your machine.
    2. You installed the LabVIEW Run-time Engine which installed the remote panel plugin into Netscape.
    3. You uninstalled Netscape.
    4. You are trying to uninstall the LabVIEW Run-time Engine.
    If this is correct, then try installing Netscape again, uninstall the LabVIEW Run-time Engine, and finally uninstall Netscape again. If this does not work, then please submit a phone request at http://www.ni.com/ask to get help with MSIBlast.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Is it possible to choose the serial port if only the run time engine is installed

    I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
    the different ports. Any suggestions?

    Hi Daniel,
    Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
    To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
    Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
    l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
    If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
    I have attached a Small VI to Illustrate this.
    Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
    I hope this Answers your Q!
    Good Luck
    Mache
    Good Luck!
    Mache
    Attachments:
    Serial_Port_Select.vi ‏36 KB

  • Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

    A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
    The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • How to specify a different directory for the Run-Time Engine?

    With LV 7.1 it's become even more difficult to create installation sets in third-party tools without having to include the full run-time engine separately.
    If you use any of the advanced analysis VIs you have to install the run-time engine (no use in including files in the same directory as the built application) and if you do and you use the old serial VIs you get a problem because the application will load the run-time from the main run-time installation and then look for serpdrv in that directory, not in the application folder...
    So - being forced to use the installer builder in the application builder and include the run-time engine in the installation kit I wonder whether it is possible to specify where the run-time should be installed?
    By default it will go in a directory called National Instruments in the program files folder, however that is not ideal due to the fact that the users have no relation to the fact that our application needs something from NI...and may end up deleting the directory ("National Instruments? - what do I need that for...let me delete it...). We would like to be able to specify that the run-time is installed silently in a directory named with our company name instead.
    MTO

    When you create the stand alone, in options you can actually set the temp directory and default directory. You can change it there OR in goto options and check for libraries/directories. You can change it there too.
    Kudos always welcome for helpful posts

  • Distribute application without labview run-time engine

    I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
    Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
    Solved!
    Go to Solution.

    Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
    And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
    Attachments:
    NI software.jpg ‏98 KB
    Installer.jpg ‏216 KB

  • Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installati​on package for Run-Time Engine 7.0

    I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit).  The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading.  I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013.  Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0.  If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
    I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected).  How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0?  Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    Are you running your VI from a Project?  If so, you can look at Dependencies and get an idea what "dependent" VIs you might have.  There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
    If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it.  If all of your relevant VIs are in a single folder, add the entire folder.  Now look in Dependencies.
    BS
    Yes I am running the VI from within a LV Project.  After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
    1.  Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
    2.  Restart the PC
    3.  Open the project, close the project choosing to "save all"
    4.  Restart the PC
    5.  Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
    6.  Restart the PC
    7.  Open the project, close the project choosing to "save all"
    8.  Open the project and run the VI.  No more messages about LabVIEW trying to find Run-Time Engine 7.0.

Maybe you are looking for