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 (
I'd appreciate any help on this issue.

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.

Similar Messages

  • VISA Write differs between TS Development System and LV Run-Time Engine

    Hi all
    I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
    Everything works fine using just LabVIEW.
    Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
    Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
    The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
    The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
    Any solutions for this?
    Thanks in advance
    Go to Solution.

    you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
    So i am pondering: Does this refer to TS at all?
    Please check the following:
    Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
    If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
    Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
    What about loading/unloading options of the modules?
    How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
    Could you provide a simple example sequence+modules showing this behavior?
    What versions of LV and TS are you using?
    hope this helps,
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Install labview 6.1 (or compatible) run-time engine with labview 2011

    I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new  equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
    Go to Solution.

    Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
    So I guess my question there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

  • Has NI plans to develop CVI for WinCE run time engine?

    Has NI  plans to develop  CVI  for WinCE run time engine?

    At this point, LabWindows/CVI does not have plans to support Windows CE. There are many reasons we do not have plans for support, but two main reasons are:
    Windows CE uses a different kernel from other Windows operatings systems.
    Windows CE does not support the full WinAPI.
    National Instruments
    Product Support Engineer

  • Calling a VI which uses "system" with LabVIEW run-time engine as adapter

    My TestStand sequence calls a VI which includes a call to "system". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system" in a VI which is called in TestStand with LabVIEW run-time ?
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

  • When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

    I've created an application installer using LabVIEW's application builder and use it to install NI MAX.  However, after running the installer, the VISA interactive control is disabled in NI MAX.
    The installer installs the following NI components:  NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
    If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX.  But, the installer created with the application builder does not seem to install the necessary components.
    What needs to be added to the installer to enable  the VISA interactive control (VISAIC)?
    Go to Solution.

    From Pedro Munoz, Applications Engineer, National Instruments
    Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
    I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
    The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
    Here is the download link:
    And in here you can find instructions on how to get started with it:
    Let me know if you have any question.
    Pedro Munoz
    Applications Engineer
    National Instruments

  • Access denied error message when switching from one Mac to another Mac

    I use LR on a laptop and a desktop, both Macs running Yosemite. I use the same external drive to store my LR photo catalogs and move it back and forth between computers. If I import pictures on one computer I get a "file access denied" when in the Develop mode on the other computer. In other words, I can only use the Develop mode on the computer where the original download from my camera occurred. I cannot find a solution and would appreciate any help. I am running the latest versions of LR and OS X. Thanks.

    Jim ~ These Apple docs may help:
    _iWeb: Modifying your site from another computer_
    iWeb: Publish to your MobileMe account from more than one computer
    And this article:

  • Distribute application without labview run-time engine

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

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

  • 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\' 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\[Error Code: -17600, Failed to load a required step's associated module. ]
    I have attached the teststand sequence if this helps.
    QuantumDigitalBd.seq ‏13 KB

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

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

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

  • References​: Appearance different in Developmen​t System and in Run Time System

    I noticed a difference the references appearance in Development System and in Run Time System.  It seems to have no effect in the executable version but, per curiosity, someone have an explanation?
    Development System
    Run Time System
    LV2009 and LV2013
    Free PDF Report with iTextSharp
    Go to Solution.

    tst wrote:
    When LabVIEW builds an executable, it removes the parts which are not needed from the VIs (like BDs, or FPs of VIs which will not be opened). I'm assuming this is an extension of that where the icon is not copied over. Another option is that the RTE is simply missing the code necessary to display this specific this.
    In any case, I would say it's a bug, albeit a minor one.
    I don't think this is a bug, the references refere to a given CTL file, which is not present in the RTE, I think LabVIEW disconnects the reference form the typedef and only saves the properties needed.
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • System Error 998 While loading the Labview Run-Time Engine

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

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

    I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
    But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
    Go to Solution.

    Hi Rajshekar.
    > Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
          - The version of Labview on the win7 64bit PC is also lv8.6 full development system.
    > Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
          - the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
    I have listed the environments in which application ran and how the application was put in to the PC.
    I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
    1. Use the installer to install the application.
    2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
    3. The PCs might either be a blank one with no history of LV installed in them
    4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
    All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.

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

Maybe you are looking for

  • After downloading itunes get an error message saying itunes was not installed

    I am so frustrated because I had itunes on my laptop and after an update it wouldnt work. I have uninstalled itunes and downloaded the newest version but keep getting this message on screen 'Itunes was not installed correctly. Please re-install itune

  • Is there some sort of BC textbook?

    I found one on Amazon but it's a couple of years old and is getting bad reviews for being outdated.  I love BC, but it sucks having to look everything you need to know up individually on different websites or googling or youtubing.  I'd be nice to ha

  • Forms 6i - Oracle Net8 Easy Config Problem in Pentium4 Machine

    Hello to All: I've installed the software successfully, but I couldn't open the Oracle Net8 Easy Config in Win. 2000 and Pentium 4 machine. It gave an error message "jre.exe has generated errors and will be closed by window. You will need to restart

  • Refreshing ALV contents

    Hi all.. I have a few input fields and a button....based on the input provided i display the data in an ALV table. Now i navigate the next view and create a new entry and save it. until i click on the button again im not able to see that new entry in

  • Call settings

    I completed find call settings or call log settings Missing in BlackBerry 10 Does any one in BlackBerry 10 Os have call settings for received, Dialled and missed call? K G Desai