Runtime Engine installer spawns from unrelated software

Hello all,
When I run a completely unrelated app (Quickbooks timer, in case you're wondering), Windows Installer launches and attempts to install LabVIEW 7.1 runtime engine. Has anyone else encountered this, and why would it occur? Is there an easy solution besides installing the runtime engine?
Thanks

Hello CT_JIM,
We are probably seeing this behavior because your application (Quickbooks Timer) is querying Windows to confirm that all MSI installers are installed properly. In this case some part of the LabVIEW RTE must not have been installed completely and Windows is trying to correct it.
This can typically be resolved by reinstalling or repairing the RTE to fix the install.
Please let me know if you have any questions.
Regards,
Matt F
LabVIEW Run-time Engine Version 7.1 for Windows 2000/NT/XP
Keep up to date on the latest PXI news at twitter.com/pxi

Similar Messages

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

Labview Runtime Engine installation problem with OSX

I tried to load the LabView Runtime 7.0 Engine for Mac OSX Says it's installing in my Applications folder and seems to be downloading the files. However, nothing is in the Application folder (and nowhere else on the HD). If I try to run a vi, it can't locate the program. If I try to reinstall, it says the files are already there. Can someone please help me with this problem?

> I tried to load the LabView Runtime 7.0 Engine for Mac OSX Says it's
> installing in my Applications folder and seems to be downloading the
> files. However, nothing is in the Application folder (and nowhere
> else on the HD). If I try to run a vi, it can't locate the program.
> If I try to reinstall, it says the files are already there. Can
> someone please help me with this problem?
I suspect the runtime is in a folder called National Instruments. You
might just do a Finder Search for that folder or for LabVIEW and see
what shows up. If you logged out and back in again between installation
and execution, it could be a permission problem.
Greg McKaskle

Multiple installs of runtime engine?

Are there any problems with multiple installs of LabVIEW 7.0 runtime engine.
That is, if I create an executable application with the runtime engine installer present and distribute it to a person who already has the 7.0 runtime engine installed, does this present any problems? Will the runtime engine actually be installed the second time? Will there be multiple entries in the Windows add/remove list?

The installer is designed to work that way. Multiple installs of the same version of the runtime engine should only increment the reference count on the files. When you install your built application you will not see an entry for the runtime engine in the Add/Remove Programs (ARP) list.
If you are familiar with MSI terminology, this behaviour is because the LV RTE that is included in your installer is just the merge module not the MSI. When you install the LV development environment, the RTE is installed from a separate MSI. Because your built app installer will use the merge module, the only way to uninstall the RTE will be by uninstalling your app.
Naren

Cannot Install LV Runtime Engine 7.1

HI,
Some of our users are having unusual installatiion problems while
installing the LV runtime Engine 7.1.1 on win2k. Our users have
installed another application recently and in that process the LV
runtime engine was removed from their computer. So, they tried to
install the runtime engine(downloaded it from NI website) again but couldn't becuase they keep getting
the message that they are not logged in as administrator. We logged in
as admnistrator and tried installing the runtime engine again,
but the error keeps occuring and is not allowing us to install. I
searched the NI discussion forums and the Knowledge base to find
answers but did not see any that match our problem. From some of the
posts I suspect it has got something to do with Microsoft hotfixes and
windows upgrades etc.
If anyone else had seen this kind of behavior and has found a fix,
please share it with us. Any help will be greatly appreciated.
Thanks Ahead
Deepak K

Hello!
This is an unusual problem. I would first go through the add/remove
programs through control panel. Loate the "National Instruments
Software" item and select "change". See if any LabVIEW
components are there and slect to remove them. This will completely remove the
LabVIEW components. Then attempt a reinstall of the runtime engine.
If this still causes problems, you may have deleted the old LabVIEW runtime
engine in an unusual way which is interfering with later installs. If this
is the case, there are some other methods that we might be able to use to
uninstall fragments of NI software. Removing the software does not fix
the problem post back and let us know!
-thanks-
Travis M
LabVIEW R&D
National Instruments

Runtime Engine Distribution Licensing (Legal) Issues?

Hi Everyone,
I need an official word from National Instruments on this one.
I've written a program using LabVIEW that I would like to distribute to the public. It runs in conjunction with a C#-based executable and is installed using the C# program's installer. Is there any legal/licensing problem with including the LabVIEW Runtime Engine installer with the C# program's installer?
Thanks!
-Yohan
Solved!
Go to Solution.

Hi Yohan,
Thanks for your post and I hope your well.
You can distribute LabVIEW executables freely. There is no need of a license to run executables that only require the Runtime Engine. Other modules such as Real Time do require a Run-Time License. Please see this link for more details: Which Software Requires a Run-Time License?
Can I ask more about your application - why do you require to distrubte these together?
Hope this helps,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

What is minimum runtime engine size when installed on XP embedded OS

I hope to build move an existing Labview 8.6 application to a Windows XP embedded machine and would like to know if their are any tools available to help minimize the hard disk memory requirement, specifically can the runtime engine installation be micro managed so that absolutely nothing that is not required by the application is installed?
If not, is their some way to install the runtime engine and then remove unused items, for instance one .dll file at a time?
I would appreciate any guidance.
Thanks,
Bernie

I believe NI does not officially support running LV apps on XPe, but if you search, you should find some references to it. In any case, I doubt you will find anything relating to the size of the RTE. You can probably safely remove some of the support files (e.g. language files, which take up some space), but I've never done it and it isn't necessarily safe.
In older versions, you could simply use all the files from the RTE folder if you didn't require any drivers, but I believe that doesn't work since ~8.0.
Try to take over the world!

NI VISA 14.0 runtime engine

Hello Everyone,
I started with LabView full development system 2011 and updated to 2014 recently. Now I was trying to build my vi. When i was trying to create runtime engine when I select NI VISA 14.0 it is giving error saying " NI visa 14.0 media path not found". So i just tried to install runtime engine by downloading from ni.com, downloading was successful, but not able to install it. Am I doing anything wrong?
Thanking you,
Sushmith

sushmith_ks wrote: When i was trying to create runtime engine when I select NI VISA 14.0 it is giving error saying " NI visa 14.0 media path not found".
The installer build spec just needs a copy of the VISA 14.0 installer in order to add it to the installer for your application. You do not need to reinstall it. It should ask you where the distribution is.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Runtime engine installatiion aborted

HI,
I am trying to install LV runtime engine 7.1 on a user's machine and
see the error "Installation aborted, A higher version of this product
is already installed". I checked the registry, C:\Program Files and
Control Panle --> Add remove programs for any traces of already
installed versions but couldn't find any. To the best of my knowledge,
I can say that this machine does not have any other versions of LV. I
attached a picture with the error messages. I am using windows 2000 and
was logged in as administrator, when this problem occured.
My question is does anyone know if the runtime engine installation
checks any particular registry settings for information about
previously installed versions and hence does not allow the user to
proceed with the installation.
Deepak

The Run-Time Engine installer shouldn't check to see if any previous or future versions have been installed. The reason is that multiple versions of the RTE can be installed on a given computer. This is actually necessary in many cases, since applications built with a certain version of LabVIEW require that version of the RTE to run.
I haven't heard of this specific error occurring. I would recommend downloading the following site and downloading a utility called msiblast.exe. This should detect any hidden installers for NI software on your machine. Remove any that you find. You might also check out this Microsoft knowledge base on the msicuu.exe utility that helps clean up installers. This utility could help clean up configuration settings for any Windows installers as well as registry information that might be left behind.
Let me know if either of these utilities helps out.
Jarrod S.
National Instruments

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 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

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

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

I'm installing windows 8 64 from iso dvd-I did the partition wiht BCamp 5 and I did the usb with compatibility software-once installation start from dvd, it ask me for some disk, usb or dvd drivers to continue. How I can continue the instalation?

I'm installing windows 8 64 from iso dvd-I did the partition wiht BCamp 5.
I did the usb drive with the compatibility software-once installation start from the dvd, it ask me for some disk, usb or dvd drivers to continue.
How I can continue the instalation? How I can provide those driver to the instalation process?
Thanks
Manuel

You can't get there with GUID/GPT.
There are tips on making a USB flash device that is bootable.
You can set aside a small 6GB partition somewhere and put Windows 7 installer there and run it WHILE IN Windows.
Windows Vista can be upgraded in place to 7 RC.
You'll need NTFS (30-50GB).
Windows doesn't support FW for booting.
You can create a drive that has Master Boot Record.

Installation of mysap PLM integration for Autodesk from Cideon Software

Where to download
Installation of mysap PLM integration - For AutoDesk / Auto CAD from Cideon Software
(SAP AutoCAD integration using CAD Desktop)
Is it comes along with SAP Inst or
do we need to get licence to use from Cideon Software.

Hi,
for clarification:
The AutoCAD-SAP Integration is a SAP product, developed by CIDEON Software together with SAP.
So it is an SAP pricelist product, it has to be purchased from SAP. Consulting services are typically done by CIDEON.

Runtime Engine installer spawns from unrelated software

Similar Messages

Maybe you are looking for