Run time engine, Error of type 1002208

Hi,
I want to build an exe using LV 8.6 development (project builder). When I finished the project in LV8.6 development, it works ok. But When I copy the project (include the exe file) to the computer installed only run-time engine (standard) and Measurement & Automation Explorer, V4.0.0.3010, The screen indicates " VI has an error of type 1002208, The full development version of LV is required to fix the errors." Is there anything wrong when I build the application? Thank you.
Hsien
Solved!
Go to Solution.

Hi Dennis,
When i built the application, I didn't build an installer into the project. I pretty much followed the HELP in LV 8.6 example: Build a stand-alone application.
The vi is mainly to read the TC signal and voltage signal from the computer connected to a scxi-1000 chassis and modules (scxi-1102 etc.) Yes, the vi called the sub vi (like DAQmx Created Channel [AI Temperature-Thermocouple].vi; DAQmx read.vi etc.). When I built the exe file, I have placed these vis into "always included" under "source file" category. Thank you.
Regards,
Hsien

Similar Messages

LV2011 run time engine error

Somebody knows why I hit a run time engine error when I select runtime adapter in teststand? If I choose dev environment, there is no error and the vi executes.
Attachments:
RunTimeError.png ‏194 KB

Hello JoVMo,
I think the reason and solution for the issue can be found in this KB:
http://digital.ni.com/public.nsf/allkb/24A8C9552C01D7368625735600768095?OpenDocument
Please let me know if it resolves the issue.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Run-Time Engine error

I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
Thanks
Chirs
Solved!
Go to Solution.

Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

LV 6.1, 3D Surface Graph sometimes collapses (doesn't work stably); plus blocks use of remotely controlled panel by LV run-time engine (error #26:"window.cpp", line 11518

1) "3D Surface Graph" does not work stably; sometimes it changes its properties (e.g. plot style) without me doing anything prior to that; a couple of times it lost a complete sense so that I had to delete the graph and install it again
2) I tried to remotely run a VI which contains a 3D Surface Graph in it. It turns out, the use of the "3D Surface Graph" somehow blocks the remote control over the panel. As a result of that, I got the following error message: Error #26: "window.cpp", line 11518 (with LabVIEW version 6.1).
3) Is it possible to plug into the 3D Surface Graph a few plots at
the same time since there is a built-in control "plot number" (somehow by bundling them up or putting into an array - I tried both but didn't work) or it can be done merely by use of 'case' structure preceding the Graph, where case structure decides which plot to pass into the 3D graph?
Attachments:
3D_Graph_ver_1.bmp ‏214 KB

Hello mjoler,
Thank you for contacting National Instruments.
The following example will show you how to plot multiple 3D plots on a single 3D graph. Modeling your VI after the example may also alleviate the instability that you have been experiencing.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B123AE0CBA19111EE034080020E74861&p_node=DZ52038
As far as the error you are receiving, it's difficult to say what could be causing this. ActiveX controls embedded on a front panel sometimes do not display on a remote client because they draw and operate almost completely independent of LabVIEW. If possible, try remotely controlling your VI with a client computer that has a complete installation of LabVIEW. The error could also be a bu
g. Try downloading the evaluation version of LabVIEW 7.0 from http://www.ni.com/labview. By doing this, we can determine if it is a bug in the older version that has been fixed in the latest version.
Let me know how this goes.
Matthew C
Applications Engineer
National Instruments

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

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

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

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

System Error 998 While loading the Labview Run-Time Engine

Hello.
I have a DLL made with LV 7.1 I run the dll using a C compiler and works great in WINXP, but cannot run in Win2K. Error is:
"System error 998 while loading the Labview Run-Time Engin(c:\program
files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
READVOLTAGE requires a version 7.1 (or compatible) Labview Runtime
Engine. Please contact the vendor of READVOLTAGE to correct this
problem"
READVOLTAGE is my function inside the dll. The runtime is already
installed. I tried it in another WINXP running machine and works fine.

This is actually a Microsoft bug with statically loaded DLLs. There are a couple of workarounds for it, and I have included two links below to posts that address this issue:
Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC
I get error 998 when calling a LabVIEW buildt DLL from MSVC++
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

MAX giving error - Unable to locate Labview run-time engine

I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
I installed some support software for a LabJack interface, which required LV version 6.1 run-time, so I let it install that.
I now get the error whenever I run MAX:
"Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

Dear CDancer
Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
C:\Program Files\National Instruments\Shared\LabVIEW Broker
Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
Many thanks for using the NI forums and I look forward to your reply.
Kind regards
David
Applications Engineer
National Instruments UK
Attachments:
LV Broker Directory View.JPG ‏57 KB
LV Broker.zip ‏413 KB

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Error -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL. TS 4.2.1 / LV 2010

When I try to run a VI that is reentrant in parallel execution, I receive this error. The details of the error is: LabVIEW: The property or method is not supported in this version of LabVIEW.
This is run under the Simple Operator Interface in LV 2010. The TestStand engine is version 4.2.1 using LV 2010 run-time engine adapter.
If I save for previous version to LV 2009 SP1 and set the TS adapter to 9.0.1 (2009 SP1), this works.
Can anyone reproduce this error (bug?) ?
Solved!
Go to Solution.

have you got the latest updates for TestStand using LabVIEW 2010?
http://digital.ni.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument
Regards
Ray Farmer

Error 1722 when uninstalling Labview run-time engine 7.1.1

I have been trying to uninstall all NI software so I can start off with a clean slate. I have been going to the control panel under add/remove programs to remove the NI stuff. Everything is gone except the Labview run-time engine 7.1.1. Everytime i try to remove it, i get teh 1722 error followed by the 1603 error. I've tried repairing it but I still get the same results when i try to remove it agian. I've also tried removing it with MSI Blast. This did not work either. I've gone through the registry and manually deleted anything related to NI and that still didn't work. Is there anything else I could try?
Thanks,
Nick

Hey Steve,
I have tried repairing it through the control panel.
I tried reinstalling just the run-time engine and it said it was already installed. So I reinstalled Labview 7.1 and repaired the 7.1.1 run-time engine through the control panel. Then I uninstalled everything. Thanks for all your help
Thanks again,
Nick
Message Edited by Nick_C on 03-12-2007 03:57 PM

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"

Run time engine, Error of type 1002208

Similar Messages

Maybe you are looking for