Application builder adds files additional select instr.lib

Similar Questions

• the application builder exe file does not work

  Hi all

  I have a usb data acquisition module, it is USB 2408-2AO of MC. I order the module with a VI and it works very well. I used the Application Builder to create an exe of the VI. The exe works great too, but only on my own computer and not on other computers.

  I already made the other screws's exe files and never had any problems to run the exe on other machines. I also tried to do an installation of the VI program and not just a stand-alone application, but once again the final application does not work. The application runs without problem on the target computer, no errors are displayed, but it just does not control the USB module as it should. I think the problem is that the builder Application does not include al screws required in the installation program, particularly MC devices to control the USB device. I tried to manually choose the screws, but it seems that everything is included... I am sure that the problem is the USB device, as I did other exe files and they all work very well (but they do not control the USB device) on other machines. Someone has any idea how to solve the problem?

  
  

• application builder error.llb

  Hi all

  I use the application builder to compile an executable from my VI. Compilation works without a hitch.

  However, when I try to launch the .exe subvis are missing three of error.llb: not found Dialog.vi, Dialog.vi to view details and the value string Value.vi

  The compiled .exe seems to be looking for these screws in instr.lib, which is not found in the compilation folder.

  This occurs even on my machine for development, on which, of course, the VI works well since in LabView.

  I missed something during the configuration of the compiler?

  Thank you in advance for your help!

  Nico

  I had this before, and it was reported by OR as a bug that just load a project that was built in an old version of LabVIEW and creating an application thereof. For me it was to load a project LV8.5 in 8.6.

  The only solution was to add the three missing from vi to the project and make sure that they are added to the list always included in the application builder.

  You will find these vi NIUninstaller Instruments\LabVIEW 8.x\vi.lib\Utility\error.llb program. Simply add them to your project, somewhere, and then in the application Builder makes sure that select you them as always included in the source files section, and then rebuild your application.

• missing application builder files

  Hi all

  I'm new to LabView and I'm trying to deploy an application as an executable file. I'm under LabView 2009 on Win XP Pro. I have the application builder and ran the application Builder tutorial. The tutorial has worked, but do the same steps on my project which called screws of several different libraries did not work. I'm not trying to build an installer again, just a stand alone executable running on a machine with the LabView run already installed calendar. I don't ask anything by reference, all Sub screws are called explicitly.

  The VI I'm deploying thin works running in LabView. Application successfully Builder generates an executable file. When the executable is run, it appears a dialog looking for a bunch of sub box face. I have attached a copy of the executable invites me for a sub - VI contained in the vi.lib

  First, is there a user manual or something like that for Application Builder? LabView help describes how to create a stand-alone executable, but not described all the settings in detail. I probably just one of the wrong settings.

  Any ideas or suggestions on what to try next?

  Thanks in advance for your help.

  Turns out you can't build project applications in the instr.lib folder. I moved the project to the folder instr.lib and the builder application worked well.

• How to include a .wav file with vi the use of the application builder?

  Hello

  I am developing an application that uses a .wav file. I want to compress this file along with the vi in an executable so that the end user has a single file to run it.  Is it possible to add the .wav file to the executable using Application Builder? Moreover, to do this, can we configure the path to the .wav file in vi to always search for the file in the installation folder (for example: C:\Program Files\E2C\MSK or according to the user installs the executable folder in)?

  Thank you

  Anvy

  Anvy,

  It is not possible to compile a wav file in an executable file using LabVIEW. You can include the wav file in the project and include it in "still included" in your build script that will copy the file in the folder wav data from your executable file. So it is quite easy to distribute the wav with your exe file, even if the wav is not in the exe file.

  hope this helps,

  Norbert

• Application Builder Question: How to get several .exe files in one version?

  I am trying to release a LV 2010 application composed of a high level VI (Main.vi), and a number of dynamically called live contacting one using functional global variables (and a few classic global variables).

  One of the dynamic subVIs (Second.vi) can in fact be used independently of Main.vi (and often will). I wish it were available as a .exe, but I would like to be able to communicate with Main.exe if is started after Second.exe. Is - it somehow possible?

  It seems to me that I must write two screws as independent applications (and release them as such, but in the same folder of the application) and find another way to enable the exchange of data between the two (which, I have no idea). Is there an easier way, I'm missing? The two screws as high level screws in the Build specification will do almost what I want, but not quite, since it in order to open the two screws little important if I want to run only the Main.vi or Second.vi only (and of course only show the single .exe file in the application folder).

  You could do this by using the arguments passed to the exe.  This document gives an example "past of Arguments to a LabVIEW executable".  I just think, you can create shortcuts in the Application Builder, but you will need to generate them buy a post running installation tool.

  Jason

• 1 error in writing on a text - installer with Application Builder file

  I wrote an installer using the Application Builder to install the runtime engine that allows any computer without LabVIEW to run an .exe program. Setup runs and installs engine race and then as a .exe VI. When it is done installing, the .exe VI opens automatically.

  An error appears when the .exe opens and says "1 error in writing to a text file". If the user clicks on the error that it can run the program without problem, it converts file formats in a file .lvm. Automatically, it generates a new file name and saves the file in the same directory, but with a different name.

  Why did it only happen when opening first upward? The program tries to run when it automatically opens? Is there a file path residual left in the program that trys to run first, before that the user put his own file path in the program?

  I am semi new to labVIEW (a few months) and that nothing shows that would create this error at the beginning of the program.

  Thank you

  Hi Scott,.

  Well, you could model a little VI and turn on debugging highlighted to test your idea!

  THINK THE STREAM!

  How a Boolean entry should WAIT for the action of the user? It should be read according to the stream!

  What this small pseudo-code:

  REPEAT
  
    Wait (50ms)
  
  Until the button

  Or how about an event in the user queue structure?

• LV Application Builder: fixed error "the system cannot find the file specified."?

  Hi all

  I don't mind banging my head out of something that feels complex, but it's still frustrating to be baffled by something that seems simple... I have LabVIEW 2014 and Application Builder. I've built a program that works perfectly as a VI, and then compiles and runs without fault as a .exe. But I can't get the installer to work. I get the following error:

  

  The suggestions in this thread and this KB article, I created a new specification to build installer, then a new application build spec, then a new project with all my screws in, build and test setup at each stage. None of this seems to make a difference.

  I ran the installer as an administrator, I created the Advanced installation directories (in which case it does not have the privileges to create folders) and built an installer without the performance in. None of this worked either. Finally, I played a bit with put all my subVIs in a library.

  So I guess it's a quirk in my program from the tutorial worked. Does anyone have any experience or advice on what specific aspects of a piece of Nice program with AB installers? It is a primary VI, less than a dozen, some Type Defs and no material integration subVIs. Seems to be a program fairly simple and straightforward, but maybe something in it is persona non grata with Application Builder?

  Are you running in deep subfolders with long folder names and file names? Perhaps some of the paths are getting too much time managing?

• * ERROR *: file d:/build/ob/bora-127388/bora/vim/lib/gvmomiMOMgr. c: lin

  Hi friends:

  I m automation ESX 4.0 with vix api 1.6.2... When I connect to the server I get this error:

  ERROR*: file d:/build/ob/bora-127388/bora/vim/lib/gvmomiMOMgr. line c: 212: failed assertion: (priv-> updatesListener == NULL) abandonment...

  I read in other threads and disconnect me properly the host, I have reinstall the server, etc... but I have can´t ignore this error... What can I do?

  Thank you!!

  What you write it in? C++, C#? If you're not do whatever it is threaded, then you should be able to get it to some stable level by closing all handles and logout (you think you are, but you are not), so it's a bug in your code. If you do this on multiple threads to several virtual machines, it will not work with 1.6.2 due to known bugs. If you write it in c#, use VMWareTasks and save yourself to treat the headaches with handles - all that needs to be closed is IDisposable.

• Application has permissions to add/file server-side streams

  I installed the FMS on Linux.  I'm trying to record video from webcam to a flex application and save them server side, to a possible posting to YouTube.

  I installed the 'live' application in the path "record".  In my flex code, I do:

  NC. Connect ("rtmp://ipaddr.us-west-1.compute.amazonaws.com/live/record");

  It connects very well, so I have:

  NS. Publish ("camtest", "record");

  It fails with NetStream.Record.NoAccess.  Server side, he said

  Accepts a connection from IP:xx.xx.xx.xx, sponsor:, pageurl:
  Application does not have permissions to add/file server-side streams; access denied to the camtest stream.

  I have LIVE_DIR in my conf/fms.ini file in/mnt/live.  This directory exists and is writable, so I'm not sure what's going on.  Are there any other permission that I'm missing?  Is it just the wrong application?  That you used for registration of netstream?

  Thank you

  -jsd-

  Hello

  Since you are using the developer version, you should be able to record. Just check the permission of the directory of the application that you created. Make sure you have permission to write to it.

  Thank you

  Abhishek

• Application builder bands DLL

  Hello

  I have a project that controls a piezo stage. This is done via a DLL from the manufacturer, and I used the wizard 'Import-> Shared Library' to make a library lvlib in the user.lib folder. The lvlib folder contains a bunch of screws and two DLLs (a manufacturer and I think come from LabView: wdapi1120.dll).

  The screws of this project are now being used in another project which brings together several projects material control. The lvlib file appear correctly under this meta-project dependencies.

  I then tried to build a stand-alone executable, but the manufacturer request stripped away of the two DLLs from the lvlib: wdapi1120.dll. This leads to two error messages (see images). The workaround I found is to uncheck "additional Exclusions-> Remove unused members of the libraries in the project" so it works now.

  But I wonder, why the application builder strips way a DLL file that was placed there by before LabView? I guess he's checking the references. So if there is no reference, why must she then?

  My feeling is that I'm missing something here if all clearification would be great.

  This DLL is not a LabVIEW DLL but your first DLL dependency. And this DLL was only placed by LabVIEW in the lvlib if there is any explicitedly VI accessing it. Otherwise, it has been added in there by which it is created the driver and LabVIEW interface.

  Given that your project does not call any VI that refers to this the application builder DLL determines that it is not used and deletes if you check the option according to. Cannot be generic for LabVIEW determine that your DLL must this second other than reimpleminting all Windows executable DLL loader in LabVIEW, which is certainly beyond the scope of what LabVIEW should never try.

• Application builder appears complete but does not create executable not

  I'm working on a major project (~ 5000 screws, LV2011 SP1, Win7 32 bit) and have recently from problems with the Application Builder. This is after 3-4 years of success is based on this project...

  When I try to build my application of following higher level occurs:

  1. "build status' window opens as usual and starts the processing of my file:

  

  2. Subsequently, the progress bar reaches about halfway and the message becomes "Compilation."... » :

  

  3. then the progress bar jumps sharply at the end and the message becomes "Save...". ». In addition, the 'Done' button becomes active, as if the build is completed. The window remains like this for always. Notes on this dialog box:

  • The 'Explorer' and 'Help' buttons work normally in this State.
  • If I press the 'Done' button (or close the window with the Red 'X') then the window closes but Labview is suspended. The only way out of here is to kill the process in Task Manager.

  

  4. If I sail in my generation folder so I see temporary build files are still sitting here, i.e. the manufacturer failed to create my exe...

  

  When I turn on logging, I see that all the files seem to be treated successfully (in comparison with a previous successful build log), but the paper stops before writing the article ' [output file Version]]... ".

  Anyway - I'm trying to restore a large number of small changes to see if I can isolate that my changes of code causing the problem.

  Someone out there knows what could cause request the manufacturer to get as much as he does, thinking it's done (even if this isn't the case)?

  Thanks for all the ideas...

  Well - I finally managed to isolate the problem... Corrupted code is attached!

  
  

  The attached code is a version of a dialog box that is used in my project. The question turned out to be associated with the order by radio inside the tab control:

  • If you open the library and then try to REMOVE the two controls private library (simultaneously), then you are greeted with the accident below report. NOTE: Remove the private items one-at-a-time does not cause the accident. (weird...)
  • The same happens if you try to rename the library

  

  The solution:

  • The inclusion of this library in my project was originally my application build will fail every time.
  • Given that the report mentions "RadioClust.cpp", I made the amazing jump that the question has been connected with the radio control... so I just unplugged all instances of this control their typedef. That seems to have fixed!

  ASIDE: I have not checked if including this library in a different application will cause his generation to not too... Something to try out a rainy day!

• Application builder does not

  Hi people.

  I can't build this application. When I try and open it I get the following error (also attached).

  Exception: Access to EIP Violation (0xC0000005) = 0x772D8E19

  Version: 1.0.0.0

  When I run like a VI in labview, it works very well without any problems, but when I build it with the application builder I can not open the .exe file.

  The project is only 1 VI, which opens an executable file from the command line, implements a few keys to generate a QR code in the file called, then cropps it and saves it.

  Is this something to do with how I'm building the application. If it works in labview surely it should work when built.

  I've built other projects from the command line, use the .exe and they open very well, but I can't talk about it.

  Any help would be greatly appreciated.

  Select this option.

  Code too sequential sems with many duplicate ode and it uses 100% of CPU core when doing nothing. There should be a small wait in the case of fake of big business structure. Couldn't you mix together into a single table U8 once and use a single autoidenxing FOR loop? Code would take on a postcard! I would use also "build path" to create paths.

  In any case, why the UIBC use a relative path ("...) "" "\Windows\System32\user32.dll")? Try changing it to 'user32.dll' instead.

• ThinApp application search "Program Files."

  Hi all

  First, I must say that this is my first time with ThinApp. Use package with Citrix or M$!

  I thinapped an application on a Windows XP SP2 virtual machine to own address. When I install applications on Windows 7, applications is looking for a dll in "C:\Program Files\AppsFolder\xxx.dll" and does not start.

  I have looke everywhere I can't find this dll.

  If I take the specific dll that apps looking in the right place, it works... (normal!)

  So here are my questions:

  1. Where will the folder and files after installing a thinapped application?
     
  2. How can I tell the application to search this dll?
     
  3. What Miss me?
     

  Thanks for your help and sorry for my bad English!

  Patrick

  > If I take the specific dll that apps looking in the right place, it works... (normal!)

  You copy the dll to C:\Program Files\AppsFolder to make it work? If this is the case, copy the dll to the appropriate folder in the ThinApp project folder and rebuild the ThinApp running the build.bat file in the folder of the ThinApp project.

  By default, install a ThinApp using MSI will go to the C:\Program Files\AppName(VMware ThinApp) folder. Note that only the ThinApp executable (EXE) will be installed in this folder and copy all the files (dll) inside will not work. The best way to manage is to add/edit the changes required in the project folder ThinApp and rebuilding it will give you an updated EXE ThinApp.

• build the file

  Hello...
  
  How can I use a version of you my project ANT script? I already have the "build.xml" file, but I don't know how to use it in my project.
  
  I tried to do in looking at project-properties-builders. I created a new Builder by selecting the build.xml file in the location of the field and other values, that I have not changed. However, I have the following error:
  
  Errors during construction.
  Errors running builder "External tool Builder integrated" on the mon_project project
  Exception occurred in the run command line.
  CreateProcess: C:\workspace\my_project\flex\build.xml error 193
  
  I think I might do something wrong. Could you help me find my error?
  
  Thanks in advance

  Here is a working example of the ANT script to build the flex application. In case you it seems that you are missing the flex Ant jar specified in my script by:

  
  

  
  
  output="${APP_ROOT}/bin/no-debug/analysis.swf".
  optimize = 'true '.
  strict = "true".
  warning = "false" >

  
  

  
  
  

  
  

  ATTA