File location surprizes when building .exe

Hi,
I'm working on a project which I'm saving to my "D:\Documents and Settings\My Name\My Documents\Customer\Project" folder.  The project contains VIs located in "\Project" and a couple of DLLs located in a '\Project\api' subfolder.  When I build an installer using Application Builder which installs the project to "C:\Program Files\Project", the resulting .exe file that I launch looks for the DLLs in "D:\Documents and Settings\My Name\My Documents\Customer\Project\api" and prompts me to find the files.  I configured Application Builder to install the DLLs in "C:\Program Files\Project\lib" folder during installation of the project. 
I don't want the .exe to look for the DLLs in the "\Projects\api" folder.  I want the .exe to automatically find the DLLs in the "C:\Program Files\Project\lib" folder without asking me.  How can I do this? 
Is this an Application Builder problem or a LabVIEW problem?
Thanks.

I guess you forgot to include the DLLs in the EXE. Please post back if my assumption is wrong.

Similar Messages

  • Error 7 occurred when building Exe in LabVIEW2010 SP1

    Hi All,
    I wanted to build an Exe for my Application. When I created an Exe and give Generate Preview, I got the following warning.
    Further, I tried to delete most of the code and give generate preview
    I didnt get any warning but I dont know, What is that empty file under data folder? Please explain if any one know the reason
    Then I build the Exe, the following error is popped up.
    Error copying files.
    Source: D:\Test Exe\SC\SubVIs\
    Destination: D:\Test Exe\Exe\data\
    source does not exist
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 7 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488: Nonexistent GPIB interface."
    Herewith I have attached the LabVIEW code (LV 2010 SP1) which I extracted from my Project.
    I browsed our ni forum and the answers posted couldnt sort my problem.
    Thanks for your reply in advance
    Thanks,
    Charu Praba
    Attachments:
    Test Exe.zip ‏9 KB

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • Labview crashes when building exe

    Hi all,
    I have created a Project and have a main vi which works fine in the development environment. When I try to build exe for the same, LabVIEW crashes. I dont get it why. If anyone could help on this, you are welcome.
    LabVIEW version:2013, 64 bit
    Thanks,
    Prabhu
    Solved!
    Go to Solution.

    Hi Prabhu,
    either provide full error descriptions - or your complete project so somebody else can try to build your EXE…
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Can't find files when building EXE unless the WHOLE codebase is in an auto-populating folder

    I have a project with FPGA (specifically a couple cRIO targets).
    I have a build spec for a PC target, then a target that's set up for Scan Mode, then a couple targets set up for FPGA mode.
    When I try and build the FPGA or Scan Mode targets, I NEED to have the entire code folder (and sub-folders) in an auto-populating folder.
    What's strange is that I manually added the same folder, and then pulled the Top-level VI out so that it was easier to see within the project.  When I did that, I got errors that files were broken and missing.  I then removed that folder and added the same folder as auto-populating and all is well.
    Yes, I was able to make the build work by including debugging, not removing TypeDefs, etc.  This also cause the build to go from 2MB and 30 secodns build time to 50MB + 10 min build time.
    Why si this?  I would like to remove the files for other targets from the Source of each of the targets.  If I do this, I can't build (these are other top-level VIs that are not appropriate on a per target basis).
    Any ideas?

    Hey Jed,
    It sounds like the problem you are having is coming from a file path issue.  When you manually add folders as "Snapshot" the file paths are set and will generate errors if the files are moved.  The autopopulating folder updates file path locations so you don't have those same issues.  Debug mode allows for the file paths to be reassociated, but at the expense of time, and in some cases resources.  Enabling debugging will cause the compilation to take longer.
    You wrote:
    So what I am trying to say is that ALL I did when I removed the auto-populate was to click "Stop Auto Populate" and moved the Top-level VI up one folder level within the project.  This causes it to fail compile (unless debugging is checked).
    This makes complete sense.  By moving ANY VI in a project and not having the folder set to auto-populate or having debugging enabled will cause an error because that VI that you moved isn't where it is supposed to be.  This is the way that projects and the compilation of programs was designed.
    To avoid this, don't move files around after they have been added to the project unless you have folders set to autopopulate, or have debug mode enabled.  When you start shuffling file paths, associations get broken and compilations will fail.
    Ben N.
    Applications Engineering
    Certified LabVIEW Developer

  • Error 1003 when building exe

    Hi all,
    I saw a couple of thread of other people here having the same "1003 error" when trying to build an exe with LV 7.1.1
    The exact text error is :
    Error
    1003 occurred at Open VI Reference in Dist Copy Non-VI
    Files.vi->Dist Build LLB Image.vi->Dist Build App
    Image.vi->Build Application.viPossible reason(s):LabVIEW: The VI is not executable.
    This is all the more surprising because this error will only happen on my computer !!!
    I borrowed a collegue's computer and the build went OK...
    After further investigations I noticed only one difference between my collegue's computer and mine : mine has VIPM installed.
    Could VIPM possibly be the source of this issue ??
    PS : recompling the code (ctrl+shift+run) on my CPU didn't make any change.
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

    Hi TiTou,
          You've probably solved this by now, but if not...
    A few months ago I was trying to distribute two EXEs - both of which made dynamic calls - and this error (among others) was giving me "fits".  I think it can happen if the caller has loaded a VI (.ctl or .vi) that also appears in the callee hierarchy - and the version loaded by the caller is incompatable with the callee's diagram(s.)  When the callee runs, it has to use same-named VIs already in memory.  If you see different behaviour on two different machines, are there two different versions of the caller?
    No matter what the problem really is (was,)  the attached VI will try to open all the broken VIs in a hierarchy - which can be a huge help in narrowing the problem.  Oh yeah, with the (broken) FP open, click on the broken-arrow to see an error-list that can (but-usually-doesn't) display helpful diagnostic info!  Compile this into your EXE (caller) so it runs if there's a problem running the callee.
    Cheers.
    Message Edited by tbd on 01-15-2007 10:58 PM
    Message Edited by tbd on 01-15-2007 11:00 PM
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    Util.VI.OpenBroken.vi ‏62 KB

  • Error 10 occurred at New VI Library.vi when building .exe

    This is driving me crazy!  What is causing this.  The program worked fine in 8.5.1 and before.  The only thing that has changed is that I had to create directories for each class in the Microsoft Report Generation Toolkit which was a huge pain itself.  See Building an EXE in LabVIEW 8.6 using the Report Generation Toolkit application note for more information.  Anyway, any suggestions would be much appreciated.

    After a lot more testing I think I have identified the problem.  Our executable uses the Microsoft Report Generation toolkit.  Due to how LabVIEW 8.6 has implemented the toolkit, it creates directories for each class of the toolkit to prevent name collisions.  Maybe LabVIEW should start using namespaces.  Anyway, we did not want the code to be visible to out customers.  We wanted it to be in a single executable.  So I found a knowledge base article that addresses the issue.  It's called "Managing the Resulting Files from a Build Containing LabVIEW Classes" and it's document id is 4OKDCDES.  Anyway this article says to add .llb destinations into the build so that instead of 5 directories with exposed VIs, you get 5 .llb.  This worked ok with no build issues, but then the article said to rename the .llb to .dll so the extra directories would appear to look like dlls.  The first time you build this it works, but if you build it again, it fails and you get error code 10.  You can then build it again and it will work.  So the problem has to do with renaming the extra .llb to .dll. 

  • Removing file location path when converting to PDF?

    Is there a setting somewhere that I can alter so that when I convert a TXT or HTML file to PDF the location path doesn't show on the bottom of each PDF page? Currently when converting I get something along these lines of file:///F|/Folder/254126.txt[06-Aug-11 20:34:02] on the bottom in a smaller font than the rest of the page.
    Is there a way to disable this or is it just something I have to live with?
    I am using Adobe Acrobat X Pro.

    Settings for converting text and HTML pages aren't in the preferences panel, they're buried in the web capture widget:
    Open the Tools Pane > Pages > More Insert Options > Create PDF from Web Page.
    Click "Settings"
    Uncheck "Place headers....", click OK then Cancel to close the capture dialog.

  • Getting "Error 10 occurred" when building exe

    I am getting the following error when trying to build an executable: "Error 10 occurred at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\Daq\lvdaq.dll"
    Listed under possible reasons were:
    LabVIEW: Duplicate path.
    NI-488: New I/O attempted with old I/O in progress.
    I made some changes and added a .vi to my program, but get no errors if I run the program from the top level .vi.
    Any ideas?

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • Error: "not enough memory to complete this operation" when building EXE + LLB in LabVIEW 2009

    Just upgraded to LabVIEW 2009 last week and can't build anymore.
    I am building and EXE with support files in LLB.
    PC Specs:
    -P4 3GHz
      -4GB RAM
    -Windows XP PRO SP2 
    - Windows is already enabled to use up to 3GB of virtual memory for applications. 
    - Performed a mass compile on all vi's.
    Not sure what else to try and will appreciate any suggestions.
    Thanks,
    Tavi. 

    This issue as well as a few others have been fixed in the LabVIEW 2009 f2 patch that was released today.  For more information, check out the following Knowledgebase for the list of resolved issues as well as download instructions.
    David_L | Certified LabVIEW Architect
    LabVIEW Tools Network | LabVIEW Tools Network Developer Center

  • Wifi related files not found when building cyanogenmod 7.2

    Hi all,
    I try to build cyanogenmod 7.2 for my Neo following the "build for hallon" wiki.
    Before building the system together, I'm supposed to extract Sony proprietary blobs from the phone using ./extract-files.sh.
    My Neo is rooted and the bootloader is unlocked.
    I'm running Sony ROM 4.0.2.A.0.62.
    When retrieving the files, I get the following messages for three of them :
    remote object '/system/etc/wifi/tiwlan.ini' does not exist
    remote object '/system/etc/wifi/tiwlan_firmware.bin' does not exist
    remote object '/system/etc/wifi/softap/tiwlan_firmware_ap.bin' does not exist
    Could somebody tell me whether it's a problem and what to do ?
    Are those files needed (for 2.3.x) ? If yes, how can I get them ?
    Regards,
    Laurent

    This is not my area of expertise but i recommend that you check the following thread for advise if you haven't done so already: http://forum.xda-developers.com/showthread.php?t=1205141.
    I'm also moving your thread to Android development.
     - Official Sony Xperia Support Staff
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

  • Error when building exe

    Building an application with database connectivity toolset v 1.0.1.
    aplication builder crashes and gives error resource.cpp

    Usually when you get this kind of error it includes a line number. This can be helpful to find other reports of this error. Also we need to know what version Of labVIEW and your OS. Can you build any application at all?

  • Build EXE error in excel dispose report

    I have seen much discussion about path-relative-to-current vi problems when building EXE apps.
    I am compiling an EXE which happens largely successfully, but when it encounters the Excel Dispose Report vi at the end of my Excel report creation section, it stops with 'error 7 at open vi reference in Dispose report  ...excel quit vi   ... file not found'.  It works without a problem in the un-compiled version. I am just using the standard Excel Dispose Report vi out of the report generation library.
    Can anyone enlighten me about how to clear this problem?
    Fred

    Fred,
    Did you include the dynamic VIs?  See: http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
    More confirmation it is dynamic VI issue: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

  • Build exe for DSC security tools

    Hi All,
    I am developing an application in LV7.0 which has Visa read/write functions, alongwith that i want to implement some security features using Dsc module's vi present in function palette. My requirement is wen Login button is clicked a login dialog box gets popped up, this i have done by using NI SEC Invoke login dialog. vi. I have also used other security tools like NI SEC User account info.vi, programmatic logout.vi etc.........Vi is working perfectly fine but after making exe, and running it on same pc, login dialog box doesn't gets popped on login button clicked.
    So my doubt is do i need to add some security library files while building exe and creating installer???
    Your reply will be valuable to me
    Thanks & Regards,
    Ratna 

    Hi Sahil,
    Thanks for ur reply. wanted to inform u that i m using only security tools of DSC module, apart from that no other DSC tools. Even though i add all supporting files which was listed in the document named Support Files to Include when Building a LabVIEW DSC Module Application (available on http://zone.ni.com/devzone/cda/tut/p/id/4189) link. In addition to this i also add .rtm file for viewing tool bar while running application and security.llb (available at development machine directory:LabVIEW7.0\Vi.lib\lvdsc>. But still the problem remains as it is. So my question is do i need to add any other supporting files related to DSC security tools, which can solve my problem???????
    If u have any clue, kindly recommend me.
    Regards,
    Ratna 

  • Labview fail to build exe for a perfect VI?

    I build a small example VI,which simply uses a T/F constant to control a case structure. The false case passes through the data, the true case does a filter on the data. This VI runs fine for when the constant is set to either True or False.
    However, if I set the constant to False, and try to build the VI into exe file, Labview fails to build exe and give out this error:
    An error occurred while saving the following file:
    C:\testfilter\Main.vi
    Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
    <APPEND>
    Method Name: <b>Save:Target Instrument</b>
    If I set the constant to true, then the VI builds fine. That makes no sense, since whatever the constant value is, it should not affect the building process.Anyone knows why Labview is making this error?
    Please see the attached sample project, I build it in Labview 8.6.1.   Set the constant to false, and the build fails.  BTW, the code does not do any real "meaningful" thing, it's just an abstraction of a complex program.
    Attachments:
    testfilter.zip ‏10 KB

    I knew this would solve the problem, because I believe the problem is that there is a case that "seems" will never be executed, so the blocks inside the case does not get included (dumped by "smart" compiler) but somehow later needs to be referenced in the build process. If you put it outside the case structure, a copy of that block will be included anyway so later it can be referenced.  I have seen similiar problems in languages like Java.   Good to hear it probabily has been solved in lv 2009, so another reason to fork a few dollars to NI for upgrades...
    Dennis Knutson wrote:
    I got the same error. I then deleted the code in the true case, selected the low pass filter function that you had outside the case structure, and dragged a copy inside. The build was then successfull. I can't explain what was corrupt and the error message is pointing to functions you did not have.

  • Adobe Acrobat 9 Updater Preference File Location

    What is the default Adobe Acrobat 9 Updater Preference File Location setting when you click on Help > Check for Updates?

    Windows XP
    C:\Documents and Settings\<current user>\Local Settings\Application Data\Adobe\Updater6\
    Windows Vista
    \\Users\<current user>[AppData]\Local\Adobe\Updater6\
    Windows 7
    C:\Users\<current user>[AppData]\Local\Adobe\Updater6\
    Mac
    "/Users/<current user>/Library/Application Support/Adobe/Updater6/"
    AdobeUpdaterPrefs.dat

Maybe you are looking for