Application Builder Error "Browse to LabVIEW.exe"

LabVIEW gurus...
I am currently building a standalone app from my project.  When I run the application (which builds successfully), LabVIEW prompts me to browse to the LabVIEW.exe file.  However, I want this app to run on a computer that will not have LabVIEW installed, and so browsing to this file isn't an option.
I know that the reason for this problem is that I'm using 2 call library functions named StrLen and MoveBlock within the LabVIEW.exe library (to access data from a pointer to a pointer).
LabVIEW.exe shows up as one of the dependencies in my project, but I can't figure out how to add it to my build specifications.  I tried to build an installer and include the LabVIEW runtime environment, but this doesn't seem to work either.
Any suggestions would be greatly appreciated!
I'm using LabVIEW 8.6.
Go to Solution.

In the dll call simply type LabVIEW without any path. This should work (I used it on 7.1)to automagicallylink it.
The functions are also located in the lvrt.dll which is the main part of the runtime engine.
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Similar Messages

  • Application builder error 1055

    ed. cross-post:
    Hello everyone
    I have a big problem with building applications lately. The build is running fine until the end, when it throws:
    Error 1055 occurred at Property Node in>>>>>>>>>>
    Possible reason(s):
    LabVIEW: Object reference is invalid.
    Has anyone seen this error in app builder? Does anyone have any idea how can I resolve this problem?

    Lennard, Valko
    I'm using LV 2013 f2. Let me give you some more details and... The story how I fixed it:
    The project is pretty big (~1500 VIs) and highly object-oriented (~300 classes). It has RT (PXI) and PC part. Some of the classes are shared between PC and RT. The problem with build was present only on PC - build for RT was ok.
    I had DSC module installed, but it was not used in this project at all. Despite that, when I found information from Lennards link, I've tried to build it using "Enable Enhanced DSC Run-Time support". It didn't help. I started to wonder if the sharing of classes between RT and PC has something to do with the problem. So I refactored the project, splitted it into two projects (one for PC, one for PXI) and reduced number of shared classes (especially some specific classes, which implement "threads"). Afterwards, the build could be done just fine, but only in those refactored projects.
    Now for the plot twist: before refactoring, I've tried to build the project on another computer. It was build without any problems! So I started to look for the differences. First of all, just before the build I've updated one of our internal libraries in VIPM and changed its name - so it was my main suspect (I needed to update dependencies in project as the change of VIPM package name changed it folder in vi.lib). This + disconnecting code from VIs and I though that I've just found another way of destroying LV compiler completely. Still, I couldn't fix it in any way...
    As per Valko suggestion I've uninstalled DSC module completely. Once again - my project does not explicitly use this module at all! Removing the module didn't broke anything in the project. And guess what? The build was done without problems! I've even tried to do this build again on the code revision before refactoring, and the build was done!



    No it's not but it is a free upgrade last time I checked. Go here and click on the Upgrade Advisor link. You will need the serial number of your current app builder.
    p.s. LabVIEW 7.1 was released today so you might want to skip 7 and go straight to the latest.

  • Application builder error.llb

    Hi all,
    I'm using application builder to compile an executable of my VI. Compile runs without a hitch.
    However, when I try to launch the .exe three subvis from error.llb are missing : Not Found, Details Display and Set String
    The compiled .exe seems to be looking for these VIs in instr.lib, which is nowhere to be found in the compile folder.
    This happens even on my developpment machine, on which, of course, the VI runs fine from within LabView.
    Did I miss something during the compiler setup ?
    Thanks in advance for your help !
    Go to Solution.

    I've had this before, and it was reported by NI as being a bug that comes from loading up a project that was built in an older version of LabVIEW and creating an application from it. For me it was loading a LV8.5 project into 8.6.
    The only workaround was to add the three missing vi's to the project, and ensure they are added to the Always Included list within the application builder.
    You will find these vi's in Program Files\National Instruments\LabVIEW 8.x\vi.lib\Utility\error.llb. Simply add them to your project somewhere, then in application builder made sure you select them as Always Included in the Source Files section, then rebuild your application.
    Message Edited by Thoric on 03-13-2009 03:52 PM
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Occasional error message saying "Labview.exe has stopped working"

    I am using Labview 8.0 on a Windows Vista operating system to communicate with lab instruments through GPIB. Occasionally, when one of my programs finishes running, an error message appears saying "Labview.exe has stopped working". The error window gives me the option to close the program or debug. After clicking debug, Windows cannot find the source of the error and the all labview applications get closed. Any ideas? Thanks.

    The code that I have been having an issue with is attached. The main program is called "Frequency Sweep Real Time2". The other two attachments are subVI's used within the main program. I am a young programmer and I have never had any official training with Labview so sorry if my Labview programming is unconventional or just plain bad. Thanks to whoever looks this over.
    Frequency Sweep Real ‏443 KB
    Read multiple ‏26 KB ‏22 KB

  • Application Builde Error

    When I build my application in Labview 6.1(Win 2000), the error is "Error 1 occurred at Snd Gen Error Call Chain.Vi\., possible reason:
    Labview: An input parameter is invalid", What sould I solve this problem?

    Typically, this occurs when vi's have duplicate names. Find all instances of Snd and rename the dupes.
    See the handy dandy ni doc strangely titled "What Do I Do When I am Building An Application and I Get Error 1: "Error saving file"?" at:
    or the Application Builder Troubleshooter at:
    2006 Ultimate LabVIEW G-eek.

  • Application Build Error

    When I try to build my application I get the following error: Error 26096 occurred at>>>>>>>> C:\Program Files\National Instruments\LabVIEW 6.1\applibs\distkit\redist\Modules\ActiveXContainer.Msm
    Possible Reasons:

    This behaviour can happen when installing Visual Studio .Net or ORCA because they install a newer mergemod.dll which isn't compatible with the older version that LV 6.1 uses in the Application Builder installer.
    This steps should help:
    1. Open a command prompt.
    2. Change to the "\Program Files\Common Files\Microsoft Shared\MSI Tools" directory.
    3. Execute the following command: "regsvr32 /u mergemod.dll". This should report that the unregister was successful.
    4. Change to the "\Program Files\National Instruments\shared\Installer" directory.
    5. Execute the following command: "regsvr32 mergemod.dll". This should report that the register was successful.
    Hope this helps

  • Does a Latest Application builder supports older Version LabVIEW 8.5 or 6.2?

    Currently I'm using LabVIEW Full Development System version 8.5 I want
    to install Application Builder, the current version of which is 8.5. If
    I purchase Application Builder now, will I be forced to upgrade the
    LabView Installation too? How to find out the version number of the
    application builder which i have? I am aware that it is a serial number
    that i will be recieving for application builder and i have to just
    activate in license manager. Does it works this simple? or a latest
    version application builder wont support my older version LabVIEW.

    For such a specific question you should contact your local NI sales rep. They should know there way around in the various licensing schemes NI has.
    But I think this should be doable.
    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!

  • Blueprint Application Builder Error.

    Dear Gurus,
      I went to CRMC_BLUEPRINT transaction code and selected the BluePrint Application Builder. BAB got launched in Internet Explorer. When I select the Application as "Leads" and View as "Lead Manager" and click on "Load Application" I get a java script message saying "SAP data could not be maintained in the customer system". I get this message for any selection of Application and View. Can you pls advice me.

    Vivek, get me your email address and will forward you the CRM PC-UI 4.0 Cookbook and I would recommend you to go through the examples and the end of the documentation to get a feel of the concept and how to tackle your questions. Also read the conceptual piece of the blueprint tables and their possibilities. If you have any questions just let us here now and help you gladly. Tiest.
    By the way also have a look at my weblog: <a href="/people/tiest.vangool/blog/2005/07/24/pc-ui-and-easy-enhancement-workbench-eew-integration and Easy Enhancement Workbench (EEW) Integration</a> which describes the generic process on how to extend transactions and make them available in PC-UI.
    Message was edited by: Tiest van Gool

  • Application Builder error in LabVIEW 7.0

    I am maintaining some legacy code in LabVIEW 7.0.  I have recently (perhaps within the last month or so) been getting Error 1003 in Dist Copy Non-VI (part of App Builder) when building my code.  I've done some testing, including trying to build much simpler VIs, and get the same error.  Curiously, this occurs on multiple (Windows XP SP3) machines, both "real" and "virtual", including on two of three installations on a single PC (so it is not hardware-dependent).
    I have a strong suspicion that the problem is neither my code nor LabVIEW itself, based on the following logic:  1) This problem arose on multiple PCs at about the same time (i.e. I don't recall seeing this a few months ago, now I see it on almost all of my PCs).  2) There are two PCs where I do not see this error -- when I check the LabVIEW installation files between a PC that "works" and one that doesn't, the differences seem (to me) to be small, more related to "what did I do most recently" or "how much of MAX did I install, which drivers".  (3) Using or not using OpenG in my code mades no difference, nor does turning off Anti-Virus scans.
    I tried two other things.  First, I have a VM that I recently build (which I think is significant) that has both LabVIEW 7.0 and LabVIEW 7.1.  The build fails with LabVIEW 7.0, but succeeds with LabVIEW 7.1.  In addition, I found a VM, built a year ago and "sitting idle", with LabVIEW 7.0 on it.  I fired it up, did not allow Microsoft Update to update anything, and tried the build with LabVIEW 7.0 -- it worked!
    My current working hypothesis is that some "patch" installed by Microsoft (.NET? ActiveX?) has clobbered something in the LabVIEW 7.0 Build Application.  Unfortunately, the VIs that make up this application are password-protected, so I can't see "inside" to discover what file or other condition is responsible for the error message.
    Does anyone have any ideas or suggestions?  [Don't suggest "Upgrade to 7.1" -- I'm the only "maintainer" of multiple PCs and multiple applications, some of which run on systems "belonging" to other people.  I am in the process of rewriting the code in "modern LabVIEW" (2011) and will port it widely, but until then, it's not practical (or "politically correct") to make the 7.0 -> 7.1 shift ...  Besides, my curiousity is piqued!]
    Bob Schor
    Go to Solution.

    Good point.  The reason for my "laser beams" is several fold.  First, I follow a written protocol (I wrote it!) whenever I install or re-install LabVIEW 7.0, so I'm pretty sure that all of the installations "should be consistent" (if not identical).  Second, I compared two NI folders in Program Files between a version that worked and one that didn't, and while there were differences, it seemed "not likely" to be an explanation.  Third, I'm 99% sure that at least one of the systems that now cannot build (of the eight installs, all by me, that I've checked, only three worked, and one was on a PC that hadn't been turned on in over a year, hence was certainly not updated) was able to build previously (i.e. I don't recall seeing this problem until about a week ago, when I started re-building an update to my legacy application).  It is possible that this problem was always present on these systems, but doesn't seem likely.
    Nevertheless, before the beginning of next week, I plan to take one of my "failing" systems, uninstall LabVIEW (but not change the OS in any way), reinstall it, and see if I can build.  If this still fails, I'll take the "old" system I mentioned above and start bringing it "up to speed" until I "break" the App Builder.  Note that it is possible that MicroSoft is not to blame -- I have other software (such as editors, utilities like WinZip, etc.) that have also been updated, and one of them might have clobbered the Builder.
    Will let you all know what I find.
    Bob Schor

  • Application builder Error: Windows SDK function returned an error. (Error code -12) *** End Error Report

     try to create an installer in Labview 8.6.  The build fail and I got this message. >> >> 
    >> >> >> >>
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Loading product deployment information
    Adding files to installer
    Done adding files
    Preparing to build deployment
    Copying products from distributions
    Copying distribution 'NI LabVIEW 8.6.1 Datalogging and Supervisory Control Module' from: 
    D:\software\application\LabView\NI.LABVIEW\NI-Labview 8.6.1 DSC Module\ to: C:\Documents and Settings\Lidaoling\桌面
    \Builds\generate waveform\My Installer\
    Building deployment
    Copying setup files
    Setting merged database information
    Setting product information
    Setting developer part information
    Starting final build
    Copying files...
    Updating files...
    Creating merged database...
    *** Error: Windows SDK function returned an error. (Error code -12)
    *** End Error Report
    Done building deployment 


  • Installer build error code-21 Labview 8.6.1

    While attempting to build an installer I get an error code -21. What is the error and how do I correct it?

    I also have this problem.  The executable build itself works correctly, but the installer fails to build.  There are a number of DLL dependencies, but they are all included and present in the build and in the installer Source Files.  I put CDK.EnableLog=True in my LabVIEW.ini and logged the error from the installer build process.  Here is an excerpt from the relevant section:
        [LOG ON]  Fri Apr 30 13:46:02 2010
    <<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
    <<<MDFConfig_SetDistributionLanguage>>> Language id: 9
    <<<MDFConfig_SetBuildDir>>> Build directory: C:\MyPrograms\MyApp_Working\Install
    <<<MDFConfig_SetBuildMode>>> Build mode: 1
        [NMDK BEGIN]  Fri Apr 30 13:46:02 2010
         Building developer part
    > Adding files to installer
    > **************
    > *** Error: An internal tool or library returned an error. (Error code -21)
    Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
    nmdkSetInformationalProperties returned error code 26024
    > *** End Error Report
    > **************
    Adding product dependencies to developer part
    > **************
    > *** Error: Windows SDK function returned an error. (Error code -12)
    Closing dist kit
    ***** About to begin MAXImportConfig:oMAXPartModifications...
    No MAX import files specified - nothing to do - returning.
    Error in MDF API function: _MDFBuildDevPart_Close
    Error in MDF::BuildDeveloperPart::Close.
    ERROR: Caught MSI Exception:
    <Unable to format error record.>
    MSI error code: 6
    > *** End Error Report
    > **************
        [LOG OFF]  Fri Apr 30 13:46:02 2010
        [MDF END]  Fri Apr 30 13:46:02 2010
         Closing MDF.
     I've also tried the same with a simple test application and it build/installs correctly, so I know it is my project somehow.  One notable difference is that I previously had namespace conflicts in the executable build that were resolved by the following these instructions:​167DB862574AC006A258B?OpenDocument
    I hope someone can help.  I need to deploy this application soon.
    - Ray

  • Application builder error

    Has anyone seen this error
    I get this error after I build an installer and try to run the setup
    Message Edited by James R on 05-14-2009 01:24 PM
    - James
    Using LV 2012 on Windows 7 64 bit
    builder_error.jpg ‏48 KB

    Hi James,
    Did you make sure to include the LV 8.5.1 Run-Time Engine in the installer?  The error is saying that dependencies are missing and the product code is for the LabvIEW Run-Time Engine v8.5.1 (I was able to look that up for you).  When you say the executables work by themselves, is that on the target machine or development machine?  Have you ever been able to build an installer?
    Kristen H.
    Message Edited by Kristen H. on 05-15-2009 11:18 AM

  • Opening Excel2000 Labview.exe generated errors

    I am trying to generate an Excel speadsheet to report test results with LabVIEW 6 and Excel 2000 on a Windows 2000 machine. The LV 6 Excel library distributed by NI has an "excel" which causes LabVIEW to crash. The error message is "Labview.exe has generated errors and will be closed by Windows. Error log is being created." Is this because of WIN2K or Excel 2K? What do I need to do to use Excel?
    Attachments: ‏929 KB

    I have the same configuration as you do in my computer with everything working fine, except for one thing, I have the update of LabVIEW 6.0.2, so I will recommend you three things in order to fix this issue:
    1. Get the update for LabVIEW ( >> Software Downloads >> Drivers and Updates >> Current Software Versions >> LabVIEW >> Select the update for your system, please follow all the instructions for installation. Reboot the computer after installation and try the example again.
    2. Try the examples that I'm sending to you as attachment and also try the example for writing data to Excel which is located in the Help >> Examples... >> Communications >> ActiveX >> Write Table to Excel
    3. Try reinstalling Excel or re-assigning the automation refn
    If you still found issues concerning this VI you may want to try to contact us directly and have a copy of the VI that is failing in order to test, you may find the information to reach us at
    Good luck!
    Nestor Sanchez
    Applications Engineer
    National Instruments
    National Instruments
    Attachments: ‏76 KB ‏129 KB

  • Application builder timeout

    Everytime i try to make a change in the application builder the browser timesout.
    Does anybody know why this might be happening?
    Thanks in advance

    How do you access APEX? Apache with mod_plsql/EPG/APEX Listener?
    If you use Apache with mod_plsql, have a look at your error.log file it might contain additional information why your submit fails.
    My Blog:
    APEX 4.0 Plug-Ins:

Maybe you are looking for