Installer build wants wrong runtime engine

LabVIEW 8.6
Windows XP Pro
When I build the installer for my application, it wants me to have available the install disk from November 2007.
Expanding the list for that disk, I find that it wants the runtime engine for version 7.1.1.
If I remove NI-DMM 2.9 from the 'National Instruments Installers to Include' list in the Installer Properties, the error goes away.  The description for that installer indicates it comes from the August 2008 device drivers disk.
At one time I had other versions of LV on the computer.  I have removed all other versions, including the directories in c:\Program Files.
My application uses the DMM device driver, so I assume that I need to check the box for the additional installer.  I've looked for more documentation on when and why I should select different items in the list, but couldn't find anything useful.  Would it be possible for the installer to automatically select those items required and perhaps let me direct it otherwise by choosing fewer or more items?
Bottom line, do I need to select the DMM driver to ensure that my application will run on a computer that doesn't have LV installed?
 - les

Hello all,
I couldn't really understand what was doing on in the above questions and answers but from the forum topic I believe I am in right place. I have an issue similar to those desscribed above. I have LabView 8.6.0 installed on my computer but when I run LabView it starts asking for 'NI LabView Runtime 7.1.1'. I tried feeding in the labview 8.6.0 but it doesn't accept it and keeps asking for 7.1.1.
The program used to run fine couple of months back and I then didn't use it for a while and I had other prgrams installed durig this time. And when this month I tried to use LabView it started giving me this trouble. I don't know what went wrong. I installed some ftdi chip drivers also. So, I am thinking if that kind of messed things up.
Also, I have this windows installer message come up sometimes which is not when I open LabView but some other programs. I don't know if this windows installer has to do anything with it.
Whatever the case it is could someone please help me figure out how I can get the right runtime work for my LabView 8.6 and if also possible how i can get rid of this windows installer message. I don't remember the error code right now because it comes up randomly. Next time I see it I am going to save that number. But in the meantime if anyone can help me with LabView 8.6. runtime engine problem.
Thanks,
Lovepreet

Similar Messages

  • USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

    Hello all,
    I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
    What has happened  is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
    On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
    I've installed on different computers (without previous labview installs) with the installer. They all worked.
    The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
    They say the COM ports aren't even showing up when they run the installed application.
    So, I'm not sure where to start. Is this a driver issue?  Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
    I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
    Thank you in advance,
    cayenne

    The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
    Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Labview 8 Application Builder and VISA Runtime Engine

    Hi,
    I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
    What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
    Is this possible?
    Ken

    Hi,
      this How-To explains about making those selections and including the different drivers :
    http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
    and this tutorial covers the screenshots a little more step by step.
    http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
    Hope that helps
    Sacha Emery
    National Instruments (UK)
    // it takes almost no time to rate an answer

  • Installer build wants Sound and Vibration Distribution but my vi dont need any

    My vi contains some ordinary serial inputs, and an ordinary DAQ to read some 4-20mA, refer attached.
    So I save a new project and build a exe with the vi, no problem, refer project files attached.
    Then I start to build the installer by clicking on the below libraries to install. I think I click the right library right?
    But lo! NI say i need Sound and Vibration Distribution, now where did that come from? My vi doesn't have sound and vibrations functions...
    I click no, Labview don't build the installer.
    I click yes, Labview kept on asking me where is the Sound and vibration library. 
    I bought a NI Developer suite, that expensive stuff costing around US$4000+. My software vendor told me I dont have the license for Sound and Vibration Distribution.
    So what should I do? Did I click some wrong settings during installer build? Is there someway to bypass this problem? Advance thanks!
    Solved!
    Go to Solution.
    Attachments:
    all-instrumentasst 4aug.vi ‏177 KB
    gmail.vi ‏16 KB
    project config.zip ‏5 KB

    pallen a écrit:
    So if I understand the KB correctly; What may have happened with the OP is that a newer version of Max (or another dependency of DAQmx) was installed along with the Sound and Vibration Suite.   So that now the "source" of those dependencies is indicated as residing within that Suite even though the software itself was not licensed/activated on that machine. 
    Something like that?  
    Hi,
    Yes, but as the note said,you can solve this problem depending on the LV version you use. In LabVIEW versions 8.6 and later, the Installer Source Location field is not editable.
    In order to update this property, you must uninstall the associated
    software and reinstall with the installers in the desired location as Christan said.
    For previous version, you have to copy the
    entire contents of the Device Driver
    CDs to your hard drive. Then next time you build your installer, change
    the Installer Source Location in the Advanced Installers dialog box to the location where you copied the contents of the Device Driver CD.
    Regards, 
    Steve M.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Vidéo-t'chats de l'été : présentations techniques et ingénieurs pour répondre à vos questions

  • Labview 8.5 installer build *.exe wrong date code

    In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today.  It will not update even after deleting it.  Is this a known bug?  SS

    Hi SS,
    The Date Modified property of setup.exe shows the date the MetaInstaller was built.  This was true in earlier versions of LabVIEW as well.  It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior.  The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi.  Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed. 
    Jennifer R.
    National Instruments
    Applications Engineer

  • Silent Installation For Crystal Reports Runtime Engine

    Hi
    I am now using vs2010 and I had created a setup package for my project.
    I had added the merged module CRRuntime_13_0_1.msn into the setup project.
    After building the setup package, I got the following items:
    Project.msi
    setup.exe
    So, by executing the setup.exe, the program will check all the prerequisite. If those are not existed, the setup program will try to install.
    Everything is fine. The program can detect the workstation missing the CR Runtime and installing it accordingly
    Now, we want to deploy it to the whole company. We had decided to execute the setup package using a batch file.
    So, we want to install the program silently. However, every time we call the setup.exe, it mentioned that we are required to accept the EULA from the SAP. The user is required to click the accept button on the screen and it is no longer a silent installation.
    I had tried a number of method to suppress it but no luck. Is there a way to suppress the EULA?
    Thank You!

    Hi Tare,
    CR for VS still uses the same installer as CR 2008 uses so see if this PDF for CR 2008 Silent Install works for you.
    http://help.sap.com/businessobject/product_guides/cr2008V1/en/xi3-1_cr_install_en.pdf
    No Keycode required for CR for VS. And note you do need to change any paths specified or required.
    I'll have to ping DEV to see if we support this, won't hear back from them until tomorrow...
    Don

  • Labview runtime engine plugin problem in Mac OS X

    Hi:
    We have just recently acquired a macBook Pro and am trying to test some instrumentation modules we have previously developed online for Circuit Theory courses on the MAc platform.
    These VI's are installed on lab view server and we have no difficulty accessing them in Windows XP or Vista from a browser either Firefox or IE. Of course the latest version of runtime engine is installed on the pc prior to accessing the vi using remote panel and secondly we have to disable any virus protection software.
    I have also installed the 8.5 version of LV runtime engine on the macbook with Leopard 10.5.x OS. I can see the LV plugin with the proper version in the Installed plug in check for the Safari browser. But every time the Remote panel is accessed I get a missing plugin message.
    Here is the message:
    Safari cannot find the Internet plug-in.
    The page “Blackboard Academic Suite” has content of MIME type “application/x-labviewrpvi82”, but you don’t have a plug-in installed for this MIME type. A plug-in should be available on this page:
    http://digital.ni.com/express.nsf/express?openagent&code=exck2m&
    Do you want to open the page?
    The page it suggests is the NI site for the plugin download?
    I am really in a corner and donot know what I am doing is wrong? Any help will be appreciated?
    Vishnu

    I'm not a Mac expert, but it sounds like you are missing the LabVIEW Browser Plugin which is necessary to view remote front panels.  That plugin installs with the LabVIEW runtime engine which you can find here.  I don't think Safari requires any extra configuration to work with the plugin but it might... let us know if installing the runtime engine doesn't resolve the problem.
    Travis M
    LabVIEW R&D
    National Instruments

  • Customizable Runtime Engine

    Hi,
    I am using LabVIEW 8.6 and I am interested to understand how to customize the LabVIEWRun time engine. Basically to shrink its size.
    I just create a sample program and installer with and without Runtime Engine.
    The VI and the projec is attached.
    The Sizes are,
    VI                                               ->      6.9 KB ( Just a UI with a loop)
    EXE                                            ->  151.0 KB 
    Installer without Runtime Engine    ->   10.4  MB  
    Installer with Runtime Engine         ->   74.7  MB
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Thanks,
    Pandiarajan R
    Certified LabVIEW Architect
    Attachments:
    RTE.zip ‏122 KB

    Pandiarajan wrote:
    I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
    Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
    Besides the options then you create the installer no. I think NI could have done it, but they do not dare. If the installer was more modular it would have resulted in a lot of extra support work for NI. As people hate to read read documentation. It is much more convenient to phone NI support and yell at them. So NI has taken the all or nothing approach. As a self defense. And I can not blame them. But I have to admit a modular RT setup would have been nice.
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Installer Build Error using LV Runtime Engine 2010

    I had an executable and installer working that were built in LV2009.  Since then I modified my source code and saved as LV version 2010.  I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed.  So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer.  However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
    Thanks in advance.
    Solved!
    Go to Solution.
    Attachments:
    Installer Build Error Message.docx ‏13 KB

    Hello,
    I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error 
    ------------------ERROR MESSAGE-----------------------------------
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
    *** Error: Windows SDK function returned an error. (Error code -12)
    The system cannot find the path specified.
    *** Error Details:
    Error in MDF API function: _MDFDistCopyList_CopyItem
    Windows function FindFirstFile returned an error. Error code: 3
    *** End Error Report
    Done building deployment
    CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
    Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\ ***************** Error: Windows SDK function returned an error. (Error code -12)The system cannot find the path specified.
    ***************** Error Details:Error in MDF API function: _MDFDistCopyList_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
    --------------------MESSAGE END------------------
    In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
    Attachments:
    Additional.jpg ‏174 KB

  • Several question s about runtime Engine, application builder and labview player

    I am a little confused by all the options to distribute a program.
    Please help bij answering (one of) the following questions:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    3. What is the advantage of the labview player above the runtime Engine?
    All questions refer to the latest software versions of NI software
    Thanks in advance,
    Regards,
    Ferry

    ferry1979 wrote:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
    If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
    The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
    (In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
    (Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    No. See above.
    3. What is the advantage of the labview player above the runtime Engine?
    The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
    Message Edited by altenbach on 08-21-2005 10:05 AM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    runtime.png ‏24 KB

  • Installer Builder - Install applicatio​n installer error, NI Variable Engine 2.6.0

    Dear All,
    Good Day!
    Im Shahril.
    My PC have 2 version of LV, 2012 and 2013.
    The application required NI Variable Engine to be installed.
    When i build the installer, nothing got wrong. AKA completed.
    But when tested it by install the application installer, the error occurred as attached.
    I do many times reinstalling the labview 2013. Still got the same problem.
    And i did run the NI Update Service. Update everthing in urgent needs to update.
    Please help me.
    TQ.
    Attachments:
    Error NI Variable.png ‏36 KB

    David,
    I can’t say for certain what’s going on here but I do have a few suggestions before you “recreate the installer for legacy code reasons.” First, I would delete everything from the Build Directory. This may be where the recursive issues are coming from. Lastly, in the My Installer Properties window, I would look at the Source Files and make sure everything is there and check for any broke links.
    Charlie M. CLD

  • Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

    *Hi
    I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
    I would like to include run time engine and the drivers of  my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
    How can I do that
    thank you in advance
    Olivier

    Olivier,
    What version of LabVIEW are you using to build your application?  On a remote computer you should only need the drivers you are using and the Run-Time Engine.  You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties.  This will allow you to attach a EXE to the installer which you can run.  Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on.  LabVIEW 7.0 is the last version that can be installed on Windows 98. 
    Please let me know if you have any further questions and please include the version of LabVIEW you are using.  Thanks!
    Andy F.
    National Instruments

  • Runtime Error building Installer with NI-VISA Runtime

    Greetings,  I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
    Everything builds fine when I check only the Runtime Engine.  Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
    Any help you could provide would be very much appreciated.
    Regards,
    JD

    Hi JD,
    This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
    LabVIEW has the
    ability to create a very detailed log of the events that occur when
    building an application or installer. To enable this feature, open up
    the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
    of the file. Save the changes and close the ini file. The LabVIEW.ini
    file is usually located in C:\Program Files\National
    Instruments\LabVIEW X.X
    Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
    To
    find out where this temp directory is located, go to Start>>Run.
    Type in "cmd". Then type "set". This will return all of your computer's
    variable names.
    Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
    Navigate to this directory using Windows Explorer.
    You
    should see a file named "Name.log" where "name" is the name of your
    build specification. For example, you might see "My Installer.log" if
    the name of your build specification is "My Installer".
    This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
    Michael K.
    | Michael K | Project Manager | LabVIEW R&D | National Instruments |

  • Distribute CVI runtime engine without the installer ?

    Customer wants to distribute CVI runtime engine with their application in VB.net.
    They don't want 2 installer (one for VB.net, one for CVI).  They want to extract the files out of CVI installer, and included in VB installer.
    Any one did this before?
    For CVI 2013.
    TIA.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

    I use CVI and deliver CVI dll to customer.
    I don't create installer.
    Customer don't want installer.
    They use VB.net, they create their own installer.
    And they don't want to call CVI Run Time Engine installer.  That's the problem.
    George Zou
    http://webspace.webring.com/people/og/gtoolbox

  • Can visa runtime engine be included in application build?

    I just installed my program on a new machine and it wouldn't work. Turned
    out I needed to also install the visa runtime engine. Is there any way to
    automatically include that in the application build?

    I've seen that you can tick of under the "additional installers" that Visa runtime is included, however, this will look for the installer files on the CD's. Is there a way to update this ? (I have 4.0 on the disc, and would like to included 4.2 in my build for installation/deployment.
    The file I download from NI is a .exe, but the linking to the build configurator is some strange windows code (see attached screenshot)
    /Brian
    Attachments:
    screenshot 13-08-2007 17.57.JPG ‏95 KB

Maybe you are looking for