"Missing external function lvanlys.dll" when running EXE

Windows 7 x32, LV2009SP1 / LVRuntime 2009
I am trying to build an EXE from a customer's code.  They use the analysis library (NI_AALBase.lvlib).
It runs fine on my dev machine.  When I build the EXE and pass it to a target machine with LVRuntime on it, I get the error:
Missing external function lvanlys.dll: Mean_head:C NI_AALBase.lvlib:Mean.vi.
I explicitly added the lvanlys library to the project.  I added the library as a source file in the build.  Finally I added the DLL itself to the project and as a source for the build.
Always the same error.  The DLL is located in the data folder after the build.  I tried to move it into the same folder as the EXE, and into the system32 folder.  Nope.
I just changed the DLL's extension to dllx and tried again, and I get the same error, so it looks like it can't find it.
Do I need to register this DLL or something?  Does it need a support file?
Solved!
Go to Solution.

Runawaycode wrote:
As the application was launched, a pop up window suggested to download the Labview run time engine, and an internet address was suggested.
I am not aware that there is a download link suggestion. Can you show us a picture of the popup window? Does the link really point to the minimum run time engine? That would be hard to believe.....
Runawaycode wrote:
National Instruments should warn the users that there are more download versions or possibly suggest the complete version if something goes wrong. 
The download page for the run time engine is very specific about the various versions. It is a matter of actually reading it.
It is even more clear in the newer versions, where the minimum run time version has been renamed into web browser plugin. The description is:
This is the download page for the LabVIEW 2012 (32-bit) Remote Front Panel Web Browser Plug-in (formerly known as the Minimum Run-Time Engine). The Web Browser Plug-in is a smaller download intended for viewing VIs embedded in a web page.  It does not contain the full run-time engine and is not recommended for running executables.
Compare with the standard run time engine where the description is:
"This Run-Time Engine must be installed on any 32-bit or 64-bit Windows system where you plan to run executables that you build with the Application Builder in LabVIEW 2012 or 2012 SP1 (32-bit). Executables built with LabVIEW 2012 or 2012 SP1 (64-bit) require the LabVIEW 2012 (64-bit) Run-Time Engine.
Additionally, the Run-Time Engine allows your browser to display VIs embedded in Web pages."
I am not sure how much clearer it could be made. Do you have a suggestion?
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • Report generation toolkit VI error when running EXE

    A VI inside the Report Generation Toolkit (version 1.1.2), Excel Find Application Directory.vi, will not function correctly when running an EXE.  The "Current VI's path" block will return the path of the currently running EXE rather than the path of the Excel Find Application Directory VI.  (The same would be true for Word Find Application Directory.vi.)
    -Joel
    Solved!
    Go to Solution.

    Have you had a look at this knowledgebase article? The error is caused due to the exclusion of any dynamic VI.
    Ipshita C.
    National Instruments
    Applications Engineer

  • Cs6 pro prem install from dload exe and 7z on usb both in same folder. when run exe it gives error archive file needed

    new install cs6 production premium  .downloaded exe to a usb thet the vendor provided with the 7z file cos i dont have lots of data.  .With both in the same folder on the usb running exe rsults in error message asking for an archive file.  There are only 2 files in the download . what does it want?

    same error message from desktop looking for archive file
    files
    ProductionPremium CS6.7z  6,109,190  KB
    ProductionPremium_CS6_LS7      1,020  KB
    running win 8.1 on ssd and z97 mobo 4790 cpu gtx780

  • Why does it report missing *.dll when running standalone programs on a separate PC without LabVIEW?

    I wrote a LabVIEW code to control GPIB, DAQ and Serial port. Then I built an installer including runtime engine. Everything works fine at the PC with the LabVIEW. I copy this installer folder to another computer without LabVIEW. I had no problem to install the program. But after I run the program, it started to ask for nilvaiu.dll. After I copied it under C\Windows\System32\, it started to ask for nimdbgu.dll, then niorbu.dll. Then it reported "The procedure entry point_pkgModulePackageEventLog@20 could not be located in the dynamic link library NIPALU.dll"
    I guess it missed some drivers. So I installed NI-488.2 for Windows on the PC. But it did not solve the issue.

    hi there
    i recommend to update to DAQ 7.4. the performance is much better.
    best regards
    chris
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

  • Cannot find 'MFPlat.dll' when running ColorBasics-D2D.exe

    I don't know why there is an error message.

    Are you running a full version of Windows 8.1 not the N or KN version. If you have the N/KN versions you need to install the media pack.
    https://www.microsoft.com/en-us/download/details.aspx?id=30685
    Carmine Sirignano - MSFT

  • Report Generation Toolkit error when running exe not vi

    Unknown System Error in Get Report Settings.vi->Get Current Font.vi->Excel Easy Table (str).vi->insert table and save file.vi->80x test suite.vi
    1. The above is an error I get from my exe
    2. I do not get this error when just running the vi.
    3. On several report gen functions cohersion dots are on my refnum input.  Is this the cause of my problem with the exe? 
    I guess there is an another learning curve when dealing with the app builder. 
    Any suggestions would be appreciated.
    Thanks
    Brian
    CLAD
    Brian

    forget what i wrote. it was my vi. 
    funny, most of the time it aint LabVIEW causing the problem but the program itself.
    Brian

  • Error 1003 when running .exe

    I am having a problem with error 1003 when I run a built application.  I have searched the forums and found many others with this problem, but they encounter the problem while building the application, not while running the built .exe.
    I have a top level VI (AutoRun.vi) that calls 3 VIs in sequence.  All three are called in the same manner.  The first two work fine, but I get this error with the third sub vi.  This is how I call the subvi:
    Use App.kind, check for "Run Time System" (strip app path twice), or "Development System" (strip app path once)
    Build path to combine stripped path and file name of subvi to open
    open vi reference
    Invokee Node - Open FP
             Activated - T
             State - Standard
    Invoke Node - Run VI
              Wait until done - T
              Dispose ReF - F
    Invoke Node - Close FP
    Close VI Reference
    The error I get is:
    Error 1003 occurred at Invoke Node in AutoRun.vi
    Possible reasons:
    LabView: the VI is not executable
    I do not get this error while running in the development environment.  Only when I run it as a .exe.  Also I have had no problems with this code in the past.  I just made a small change and now I have this problem.  I have gone back to the old code and have the problem with it too. 
    I build the app by starting the app builder, selecting the top level VI, adding dynamic VIs and select all 3 subvis.  The front panel of the second VI is not visible while running.  I have to go in and manualy change the "Remove Panel" in the build settings for this VI from the default yes to no.  If I do not do this I get an error while trying to run the built application.  I have no idea why this happens either, but making this change fixes the problem.  After this I select build.
    BTW, I have LabView 7.0

    Hello,
    Not sure what happened on your end, but if the problem comes back repost and we'll explore it!
    Best Regards,
    JLS
    Best,
    JLS
    Sixclear

  • Word_print.vi 1015 error when running exe

    I created a vi that generates report in word and prints to default printer. The vi works fine in three different computers with office 2000, 2003 & 2007. But when I create an exe, there is an error: 1015 Word_Print.vi in Print Report.vi. The error is only in system running office 2000. The application was built using LV 8.2 & office 2007. The exe is created with dynamic word vis in support files. I also tried addind Word_print.vi in the support files.
    Could you please let me know what I else I could do?
    Thanks
    U

    Ah, understood.  Which version of the Report Generation Toolkit do you have installed?  All versions, except maybe 1.1, have a folder on the package CD called Compatibility.  Within this folder are directories such as Office 97, Office 2000, [Office XP], [Office 2003], and [Office 2007] (toolkit version determines if you have the items in brackets).  If you dig into these directories, you'll eventually discover the file _wordsub.llb.  This library contains the appropriate _Word Dynamic VIs.vi that you'll want to include in the "support files" section of the application builder.  Refer to the Office.txt document found within C:\Program Files\National Instruments\LabVIEW 8.X\vi.lib\addons\_office directory to confirm what I said.  Thus, to create an executable that will print from your Office 2000 test machine, include the _Word Dynamic VIs.vi from the Compatibility\Office 2000\vi.lib\addons\_office\_wordsub.llb library on your Report Generation Toolkit CD.
    Peter K.
    National Instruments

  • Error when running EXE but not from editor. How do I find it?

    When I run my app from the editor, the program works fine. But when I try to run the EXE, I get an "index out of range" error. (???)
    I examined my code extensively but I can't figure out for the life of me where the error's coming from.
    Any advice on how to track it down? Thanks.

    Find out what is using indexes then correct whichever code is using indexes. Apparently you have not examined your code extensively enough.
    Can't you see details of the error and find what line the error occured on?
    La vida loca
    Monkeyboy brings an interesting point.
    Try wrapping all of your code in a try-catch block and msgboxing the stacktrace, that way you can find the line.
    “If you want something you've never had, you need to do something you've never done.”
    Don't forget to mark
    helpful posts and answers
    ! Answer an interesting question? Write a
    new article
    about it! My Articles
    *This post does not reflect the opinion of Microsoft, or its employees.

  • ImaqDisplayImage hangs when running .exe and the window can't be moved when in Debug mode

    I am running a multi threaded application with multiple windows, two of which display images but only one is open all the time.  The window displaying the image (using imaqDisplayImage(myImage, 1, TRUE)) can not be moved or resized, the image continually updates though, when I run the app in debug mode.
    If I run an executable, either debug or release the following happens:
    Everything looks good right when the app starts, all windows are displayed and the live image window is continually updated.
    If I click on any window in my program or not in my program, the imaqDisplayImage window freezes and will not udate its image, it will allow me to move it though, and it has (Not Responding) in the title bar.  The main window of my program does not freeze and behaves normally. 
    I know that an acquisition is still taking place because I have a button on my main window that copies the last grabbed image that should be displayed in the imaqDisplayImage window and displayes it on a canvas (using imaqImageToArray etc . . .) and this image changes everytime I click the button.
    Anyone have any tips with dealing with imaqDisplayImage windows??  Thanks!

    At this point we want to pinpoint exactly where in your code this behavior is originating from. Try running the included examples which can be found here:
    C:\Program Files\National Instruments\MeasurementStudio\CVI\samples\IMAQ\Display
    C:\Program Files\National Instruments\MeasurementStudio\CVI\samples\Vision\1.GettingStarted
    and see if you experience the same behavior. If we still experience this, then we know that it is a setting within the functions that we need to change. If not, we know that it is somewhere else in the code of the bigger project which is the culprit. 
    Daniel G.
    Applications Engineer
    National Instruments

  • Unable to load gpib-32.dll when running the visual basic 2008 program

    I installed NI-488.2 into my PC, window 7 64 bit OS.
    In the program >> project> add reference>.NET, I successfully add the NI.4882  into my visual basic  program.
    By the way, this program worked well in another window 7 32 bit PC.
    But when I run the program at ildev(BDINDEX,.........), error comes up as "unable load DLL gpib-32.dll".
    So when I looked at c:\windows\system32, I can not fine gpib-32.dll.
    Doesn't  NI-488.2 driver install gpib-32.dll?
    How can I install gpib-32.dll?

    SeongCho wrote:
    Nyc, thank you for your reply.
    By the way, I think I did all the link explained.
    So I have no problem in  adding  NI488.2 to my program's reference using "add reference".
    The problem is GPIB statement like ildev() looks for "gpib-32.dll".
    But there was no gpib-32.dll installed in "c:\windows\system32" so error comes up with "unable to load gpib-32.dll".
    I did the same procedure in my another PC(window 7 32 bit OS,my current PC is window 7 64 bit OS), and in that PC I can see the gpib-32.dll in that directory and program run without problem.
    I do not know how gpib-32.dll was installed in my previous PC.
    Thanks
    Seong
    Have you looked at the example programs for .NET that install with NI-488.2?
    You need to start thinking in terms of .NET 

  • Missing external function ni.can

    Hi guys,
    i built an exe and when i tried to load it to my second PC i got the error below.
    I have to mention that when i run the exe in my PC where i build the vi it works properly.  Also i have build also another VI with analogue data acquisition that runs perfect in both PCs.
    Looking forward to hearing from you
    Elias

  • Missing external function nivissvc

    Hello,
    Could you help me to solve this error message?
    This error occures when I launch my application. The exe and the installer is created with LV and the LV RTE + Vision RTE are also attached to the installer.
    +++ In God we believe, in Trance we Trust +++
    [Hungary]
    Solved!
    Go to Solution.

    Sorry for duplicate,
    I have tried to search my previous post but did not find it...
    The problem is solved,
    Platform: Win764Bit,
    All updates must be installed to the OS, and the error gone!
    +++ In God we believe, in Trance we Trust +++
    [Hungary]

  • External Monitor not recognized when running XP (MDP to HDMI)

    Hi,
    I also posted this in the "Windows Compatibility" forum.
    I have a new Macbook Pro (unibody, 15.4", 2.53 ghz) and I am trying to make it work with my Samsung T260HD HDTV/Monitor. I am hooking this up via a Mini displayport to HDMI adapter, Yeah! I have NO problems when using the computer in OS 10.5.6, but when I boot up into windows XP (SP3) via bootcamp, the monitor gets no signal. I know that it is NOT the adapter, Apple hardware, or monitor, because, like I said, it works fine in OS X. I am assuming that this is a windows driver thing. Anyone have any thoughts or suggestions to get this to work? Thanks.
    -Dan

    boot windows xp in safe mode with vga drivers to use standard 800x600 display drivers so you can see, then install teh drivers for your monitor.

  • External Monitor not recognized when running XP

    Hi,
    I have a new Macbook Pro (unibody, 15.4", 2.53 ghz) and I am trying to make it work with my Samsung T260HD HDTV/Monitor. I am hooking this up via a Mini displayport to HDMI adapter, Yeah! I have NO problems when using the computer in OS 10.5.6, but when I boot up into windows XP (SP3) via bootcamp, the monitor gets no signal. I know that it is NOT the adapter, Apple hardware, or monitor, because, like I said, it works fine in OS X. I am assuming that this is a windows driver thing. Anyone have any thoughts or suggestions to get this to work? Thanks.
    -Dan

    boot windows xp in safe mode with vga drivers to use standard 800x600 display drivers so you can see, then install teh drivers for your monitor.

Maybe you are looking for