2012 missing runtime engine in newly created build

in 2012, when i complete a build, it creates an .exe file. when i run the .exe on a new computer, it says " runtime engine is missing". what option / button do i select to add the runtime engine to the build so everything is in one .exe, which makes it easier for our customer support team when dealing with customers that replaced their laptop?

Additional Installers >> NI LabVIEW (xxx) Run Time Engine
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E

Similar Messages

Front panel class objects are missing their icons in the runtime engine

I have this project that contain some class objects. When run in the developer environment, the icons appear fine.
However when I build as an executable and run it in the runtime engine, the icons are missing.
These missing icons are purely cosmetic and the underlying logic works without a problem. Is there anyway to get these icons to display when built as an executable?

Known issue, see http://lavag.org/topic/12980-class-control-icon-not-shown-in-run-time/
EDIT: have you considered just making that control invisible? Takes a bit of manipulation of property nodes and references but you can do it as shown:

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

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

Newly created photoshop images/icons missing in finder in Snow Leopard

Ever since installing Snow Leopard, whenever I create a new image in Photoshop and save it to a file, and then I go into that file to look for it, it is missing. The only way I can find the file is if I enter the name of the image in the finder window and do a search - then it says that the image is in the image folder - where I put it - but when I go there, it isn't there. So the only way to find and then open that newly created image, is to remember what I called it, and then enter it's name in the finder serach window. Crazy, Huh? What could be causing that, and how can I fix that?
The other problem that I notice with Snow Leopard is that the newly created icon images in finder are all blurry. The blurriness seems to be random. Some are, some are not. I did a search for that in the forum and it seems that just about everyone is experiencing this problem. You would think after a year of complaints that Apple would do something about this, but they have not. They are completly ignoring the problem.

What version of CS? what Mac even is this?
CS4 or later (CS5.x probably to be current).
http://help.adobe.com/en_US/Photoshop/11.0/WS9EF019E3-76FE-416a-853A-0F338265DB0 4a.html
http://help.adobe.com/en_US/photoshop/cs/using/WS9EF019E3-76FE-416a-853A-0F33826 5DB04a.html
http://www.bing.com/search?q=Adobe+photoshop+file+save+location

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

Can I use Solution Builder on newly created Client?

Dear Experts,
I have an existing SAP system and I created new client via SCC4 without doing any client copy (means it's blank).
Can I logon to the newly created client via SAP* (since there's no other user id) and run Solution Builder to activate those SAP best practices Building Block? Will that affect other existing client (what I mean, will there be a cross-client customizing?
regards,
Abraham

Hi Abraham,
Can I logon to the newly created client via SAP* (since there's no other user id) and run Solution Builder to activate those SAP best practices Building Block? Will that affect other existing client (what I mean, will there be a cross-client customizing?
Yes, You can login to newly created client via SAP*. However, running or activation on empty client is not advisable.
Please copy the Newly created client from 000 or 001 and start the activation.
Refer to below link for SAP best practices Activation.
http://help.sap.com/saap/sap_bp/HCM_ERP605_US/html/installation_page_EN_US.htm
IMPLEMENT - Solution Builder Simplified path to activate SAP Best Practices.
Graphical scenario selection; Standard scope templates
http://help.sap.com/bp_dm603/BBlibrary/General/SAP_Best_Practices_overview_EN.ppt
Regards,
Sravanthi

Can I extract the orginal VI's from an executable created by Runtime Engine?

I have an executable program created using the Labview Runtime engine and need to edit the subVI's contained within. Unfortunately, I don't have the original VI's the program was created with.
Is there any way I can extract those VI's?
Thanks,
Mike C.

First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

2LIS_11_VAKON missing newly created sales orders

Hi All,
Our Sales Order Condition - 2LIS_11_VAKON extractor is missing newly created SD's since 2 days and Sales Order Hearder & Item extractors brings correctly into BW.
Any inputs on this?

Hi Prasanna,
only the delta relevant fields of 2LIS_11_VAKON occurs a Delta in the Outbound Queue (LBWQ) and finally as a result in the Delta Queue (RSA7) for the relevant DataSource 2LIS_11_VAKON.
Please check the delta relevant fields in LBWE for the relevant DataSource. On the left side You see the Delta relevant fields, on the right side the possible fields which you can Append and make Delta relevant.
Is the LIS Job for Application 11 active to bring the Data from outbound Queue (LBWQ) to Delta Queue(RSA7)?
Please make a Delta test in ECC and change the relevant Field. After the change in LBWQ the Counter for Application 11 should increase by 1.
by the Way, in RSA3 you see only the Data from the Last Application Setup (e.g. OLI7BW for LIS11 DataSources), Delta records are only visible in RSA7 after the LIS Job (LBWE) was run.
hope it helps.
regards,
MIchael

How do I build an executable w/o installing the runtime engine in the OS?

Hello everyone
I have developped an application with LabView 8.01 and build an executable for a customer, this works great, if I have administrator rights. But my customer don't have full administrator rights and they are not able to install the software (Runtime Engine). In LabView 6.0.1, to solve this problem we added the lvrt.dll and some support files directly to the application builder as support files and it worked without to install the runtime engine in the operating system.
How can this be done in LabView 8.0.1 and which files are needed?
I am thankfull for any advice.

hi,
you always need admin rights to install software.
I think it's not possible in labVIEW 8.01 to install the runtime without admin rights.
The costumer only has to the runtime one time, so he should try to contact his system administrator.
I've found no workaround for it.
Best regards.
Christoph Strasser
AE/NIG

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

Is there a .sld file for LabView runtime engine when creating Embedded XP image

I'm looking for a .sld file to aid inclusion of LabView runtime engine in my embedded XP image. Has anyone already written one?

Hi,
unfortunately, National Instruments doesn't have any sld files for embedded OS'es, however, please checkout the links from the Lookout discussion forum, where someone was trying to do something similar.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000AD5C0000&ECategory=Lookout
Although there's no definitive resolution to this thread, the person who answered has said he could be contacted.
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Runtime Engine 8 & Application deployment

Can anyone direct me to a kbase article on the correct way to deploy applications using the latest runtime engine?
My first application said it was missing one of the libraries used to create the VI - why wouldn't the build include any VI's in the program etc?
I could use a good tutorial or article explaining the correct steps etc.
thanks!'
m

Found solution to my own problem
Best practices:
http://zone.ni.com/devzone/conceptd.nsf/webmain/BBE67528EBCA22B7862570700077EBB9#9
Using application builder:
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1

2012 missing runtime engine in newly created build

Similar Messages

Maybe you are looking for