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 initialize.vi.  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. 
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

Similar Messages

  • 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

  • Can I use the labview run-time engine 2010 with my LV 2012 program?

    Hi all,
    I will receive the new Labview Developer Suite 2012 DS2 in a few days and
    I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
    Stay Hungry, Stay Foolish
    Solved!
    Go to Solution.

    Hi Benjamin,
    You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications.  Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
    The following links direct you to our download pages for the run-time engine:
    The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
    Hope this helps.
    Marshall B
    Applications Engineer
    National Instruments UK & Ireland

  • Getting "the procedure entry point CGImageRelease could not be located in the dynamic link library CoreGraphics.dll" error when starting Itunes. Haved reloaded many times and still the error.

    Getting "the procedure entry point CGImageRelease could not be located in the dynamic link library CoreGraphics.dll" error when starting Itunes. Haved reloaded many times and still the error.

    Taken at face value, you're having trouble with an Apple Application Support program file there. (Apple Application Support is where single copies of program files used by multiple different Apple programs are kept.)
    Let's try something relatively simple first. Restart the PC. Now head into your Uninstall a program control panel, select "Apple Application Support" and then click "Repair".
    Does iTunes launch properly now?
    If no joy after that, try the more rigorous uninstall/reinstall procedure from the following post:
    Re: I recently updated to vista service pack 2 and I updated to itunes

  • "Could not complete scan" error when using Windows Fax and Scan

    "Could not complete scan" error when using Windows Fax and Scan with a HP OfficeJet Pro 8600 Plus All-In-One network printer.
    Printing is fine.
    When using the HP Scan application, get the error "Scanner communication cannot be established".
    When scanning from the printer itself it fails with the same message. In addition the printer panel displays the error:
    "The scan could not be completed due to one or more of the following issues:
    Connection to the computer is lost
    The scanner is in use
    OCR application is not installed"
    My PC is a HP Compaq Pro 6300 SFF 64bit, with ethernet cable to the router and ethernet cable to the printer
    Originally ran Windows 8.0; recently upgraded to Windows 8.1.
    Older separate Netgear router and modem was replaced with a newer Netgear Router/Modem, but both experienced the same problem.
    There was no problem with the original Windows 8.0 configuration and only after upgrading to 8.1 did the problem emerge.
    On my home netowrk I have an HP ProBook 6550b running Windows 7 sp1 that uses wireless to get to the Router, and it has no problem with scanning.
    I have followed the recommendations of a number of articles relating to this issue (including: http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&​lc=en&docname=c02915410&product=4323659#N94), but there has been no change in behaviour.
    The printer has a static IP address;
    Power settings have been adjusted to Never for Turn off Hard Disk; Sleep and Hybrid Sleep.
    Scanning has been tested with all firewalls and antivirus turned off and in Selective Startup.
    The printer has been plugged directly into the power socket.
    With all these settings the Windows 8.1 cannot scan while the Windows 7 laptop with wireless to the router has no problems.
    Appreciate any insights into this problem.
    I can only surmise that the problem is a compatibility problem between the 8600 Printer and Windows 8.1.
    Any ideas?
    regards,
    Motorbike

    You can determine if there is compatiblity between the printer and PC by checking the Windows 8.1 hardware compatibility list. I have done that and it is shown to be fully compatible.  If the driver you installed before was only the basic driver,it would explain the lack of scan and copy functionality.
    Download and install the Windows 8.1 full feature driver and software on the HP Compaq Pro 6300 SFF 64bit PC . 
    http://h10025.www1.hp.com/ewfrf/wc/softwareDownloa​dIndex?softwareitem=bi-108858-4&cc=us&dlc=en&lc=en​...
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • 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 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

    Hi to all,
    I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
    The Problem is that I get the following error, saying that my VIs cannot be executed:
    -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
    All my VIs were masscompiled with LabVIEW 7.1.1
    How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
    Thanks for you help,
    - Caribe -
    PS: I configured the adapter to use the  LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

    Hi Caribe,
    Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
    I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
    If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
     Thank you,
    Sasi

  • 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

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

  • 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

  • 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

  • How to load dynamically String into a VI using LabVIEW Run-time Engine Version 7.0?

    I would like to be able to traduce string into my application using import string method. I create an program with my VI to translate. When I use the import method, I get this error: the VI is locked. WHY ? because it works well in the edit mode but not using LabVIEW Run-time Engine Version 7.0 .

    Hello loup,
    If you call dynamically a VI in your LabVIEW application you must add this VI when you build the .exe file.
    To add this VI, go to the Tab "Source Files" when you build application and click on "Add Dynamic VI..." then chose the VI you call.
    It should solve your problem.
    In the attached file you can found an example of LV program that translate front panel.
    Try to build exe file and add "Languages.vi" as dynamic VI and .txt files as "Support files".
    I test it, it works.
    I hope that this will help you.
    Best Regards,
    Sanaa T
    National Instruments
    Attachments:
    Translation.zip ‏69 KB

  • System Error 31 while loading the LabVIEW Run-Time Engine

    I'm getting the following error message.  I've attached a screen shot of it as well. 
    System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
    I'm trying to update an instrument running Windows95.  What is system error 31?  I can't find anything on it using Google or the forum's search function.
    The instrument is a Romulus-IIIA from Quad Group.  I'm pursuing assistance from them as well.
    Solved!
    Go to Solution.
    Attachments:
    Winzeta Error LabVIEW.JPG ‏17 KB

    Howdy Szandstra,
    Check out this KnowledgeBase article describing what you are seeing.  Follow the steps there to correct the problem.  Have a great day, and let me know if that solution doesn't work for you!
    Sincerely,
    Chris G in AE

  • 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

Maybe you are looking for