LabVIEW 2009 Build Path Problem

[Cross Posted to LAVA]
I had some code that worked fine on my home PC, when I moved it to work, the exe would not build due to errors.
The errors coming back weren't that good at explaining the problem
Until I got this one:
Look at the path in the error:
C:\Users\Developer2\Desktop\User Group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build executable file paths\dist\application 9.0\my application.exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb
That path is referring to a VI inside my executable!
This may be a bigger issue that I first thought
So my question is:
If a have a path inside my build that would be relative to the executable and LabVIEW needs to resolve it, could that process fail depending on where the exe sits in a folder hierarchy?
I guess this could have happened before? but it would be more likely now due longer paths!
Message Edited by jg-code on 08-26-2009 05:20 AM
Certified LabVIEW Architect * LabVIEW Champion
Solved!
Go to Solution.

Solution in cross post
Certified LabVIEW Architect * LabVIEW Champion

Similar Messages

LabVIEW 2009 build memory usage exceeds Windows limit

We have a large application that builds without problems using 8.6.1, but failed to build using LabVIEW 2009 with the error "Not enough memory to build this application".
We solved the problem by adding the parameter /3GB to the Windows XP boot.ini file. This increases the available memory for a Windows XP application from 2Gb to 3Gb.
It appears that LabVIEW 2009 uses more memory during the build process and, in our case, this took it over the 2Gb limit.

We are also facing the same problem...
can National Instruments help us ??????
Following error is occuring while creating exe.
"Build was unsuccessful
An error occurred while saving the following file:
D:\BIS_Main_2009_V3.XY\branches\BIS_Main_2009_V3.61_Trans\User Interface Panels\Inspection.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.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_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>"
Please suggest!!!

Tip: How to Avoid some tough LV 2009 Build & Run Problems

Hello,
I posted some tips I think may be useful to my fellow LabView 2009 programmers on the MathScript forum here:
http://forums.ni.com/t5/LabVIEW-MathScript-RT-Module/Avoid-MathScipt-Comments-in-EXE-Build-amp-Run-P...
Allthough some of the problems are MathScript related, the post contains information on how to avoid some other LabView 2009 problems as well. I thought this info would be interesting to other than "MathScript programmers":
The post contains information on how to circumvent the following problems:
* "The VI is not Executable. The full development version of LabView is required to fix the errors"
* Avoid that MathScript Comments are included in the EXE !
* Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE
* DSC Reference Problem in LabView 2010 DS1 release
* TagSrv Error "TagSrv.exe: This application has requested the runtime to terminate in an unusual way"
Geir Ove

Hello,
I posted some tips I think may be useful to my fellow LabView 2009 programmers on the MathScript forum here:
http://forums.ni.com/t5/LabVIEW-MathScript-RT-Module/Avoid-MathScipt-Comments-in-EXE-Build-amp-Run-P...
Allthough some of the problems are MathScript related, the post contains information on how to avoid some other LabView 2009 problems as well. I thought this info would be interesting to other than "MathScript programmers":
The post contains information on how to circumvent the following problems:
* "The VI is not Executable. The full development version of LabView is required to fix the errors"
* Avoid that MathScript Comments are included in the EXE !
* Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE
* DSC Reference Problem in LabView 2010 DS1 release
* TagSrv Error "TagSrv.exe: This application has requested the runtime to terminate in an unusual way"
Geir Ove

LabView 2009 tagsrv.exe problem

Hello!
I installed LV 2009 on windows XP machine. On startup of computer the error in tagsrv.exe is reported. On Distributed system manager is not possible to see shared variable on network computers. Firewall is disabled. Do you have any idea how to solved this?
Thanks!
Solved!
Go to Solution.
Attachments:
lv_err.JPG ‏19 KB

Hello!
I have done all proposed action:
1. Disabled tagsrv.exe at startup of computer and later manually start. The result is the same. After startup the service system still reported same error.
2. Uninstall all NI software and install again LV 2009. At startup of tagsrv.exe is again error reported.
3. I can managed the shared variable on both PC (LV 9.0 and LV8.6), deploy is done without error, but later reading in the program the error -1950679027 is reported. All firewalls are disabled.
Attachments:
lv_err.JPG ‏19 KB
Distributed system manager.JPG ‏81 KB
Share variable in LV program.JPG ‏152 KB

Build Specifications gone with LabVIEW 2009

I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
Is this a known issue and is there a fix for it?

Hello,
this might be a corrupt project file. Does this only happen with this project?
If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
Regards,
Joseph Tagg

Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_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 permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
Any suggestions?
Thanks

For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine. On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
This may not be a complete fix to the problem but at least in this one case it worked.

Run-time engine problem in Labview 2009 and Labview 2010

I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation related to Labview is not permitted and the same error came up every time. it is very annoying.
So, What is the deal?
I attached the error here. Any comments or advice are welcomed and appreciated.
Attachments:
error.docx ‏2305 KB

By chance is this machine's language set to any non-English locale? You would check the locale setting by:
Opening Control Panel.
Opening "Regional and Language Options".
Looking Under "Regional Options" >> "Standards and Formats"
If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
Regards,
- WesW

Can i build an application with Labview 2009 for Windows 7?

Hello
i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
Solved!
Go to Solution.

Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application. After installation I had to move the files from 1 location to the other to make it work.

Signed applet : problem signing jar files that are in build path

Hello,
I have a problem while trying to create an ftp applet.
I use org.apache.commons.net.ftp and i build path for commons-net-1.1.4.jar and then i build my classes.
When i create a jar file with my classes and after signing it, it works under eclipse but not on a web page.
I had signed commons-net-1.1.4.jar before to build the path in eclipse but commons-net-1.1.4.jar is not in my jar file.
What is the way to sign applet correctly even if some jar ressources are in eclipse build path.
Thank you

You were right!!!
I'm not sure what to write down in the formsweb.cfg (configuration file) , following the instructions on the on-line help of Developer Forms 10g , in step 9..
The step 9 says...
Because in this release the JACOB code is in an external Jar file and not incorporated into frmwebutil.jar, it needs to be downloaded. To do this, change the WebUtilArchive setting to read: webUtilArchive=/forms/webutil/frmwebutil.jar,/forms/webutil/jacob.jar
The doudt is pointed to the fact that the frmwebutil.jar isn't in the ORACLE_HOME\forms\webutil path but it is ORACLE_HOME\forms\java path.
Also , these paths referenced in webUtilArchive are physical paths in a Unix system or they are logical paths in a url?
Simon

Issues about labview 2009 application builder

first of all, sorry for my poor English ~~~i am not quite sure about whether i could make myself clear for you guys.here it is:
SFX-ZIP archive is choosed as the file format for built-exe in labview 2009.when building any project into exe in labview 2009, you can always turn the suffix of the application file into zip. then use any compress-decompress software to open that file.shocked? right? yes, all the vis that used in your project are there. of course, you can decompress all the vis from the archive.although the block digram is removed during the building process, they still can be dragged into any vi and work perfectly.
this is so insecure both for the application and the source code.how about you?
Message Edited by hunt978 on 05-10-2010 04:16 AM

Double post

LabVIEW 2009 x64 and application builder

Hi
My organisation has just got a site licence for LabVIEW so I have just installed 2009 x64.
My question is this:
If I build applications written using LabVIEW 2009 x64, will they only run on 64 bit computers? I would test this but both my computers are 64 bit machines. I have had a brief look through the build specs but there doesn't seem to be anything about 32/64 bit compatibility.
thanks.
J
Solved!
Go to Solution.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

Problem about Mac Os X 10.6.3 V.S Labview 2009

hi,labview~
i have some problem about Labview 2009.i saw the website of NI wrote the Labview 2009 is not support for Mac OSX 10.6.3,but i have already installed it (English system) in my computer successfully.
anyway,i cant open the programs which are wrote by labview 8.5(Japanese system) .My labmate who use Labview 2009(Mac OSX 10.5) can open those programs.
can anyone tell me the possible reason i cant open the programs?
Thanks a lot!
PS i have already tried Labview 8.5 and 8.6(English system),but the problem cant be solved....

Hi mofi, my name is Taiki from National Instruments Japan.
I assume that the link you referred to is the one below, but as you stated, LabVIEW 2009 is not supported in Mac OS X 10.6 so even though you were able to install it successfully, NI cannot assure that it will fully function on your Mac.
LabVIEW Support for Mac OS 10.6 (Snow Leopard) and 10.5 (Leopard)
http://digital.ni.com/public.nsf/allkb/70F17A30DE7B865E8625737F006377F8?OpenDocument
Since you mentioned that the VI files were able to be opened on LabVIEW 2009, Mac OS X 10.5, the actual VI files should not be the issue which leaves us with the possibility of the software environment.
You also noted that the issue could not be solved on LabVIEW 8.5 and 8.6 but was this on Mac OS X 10.6 as well?
If so, there is a good chance that this issue is due to the fact that LabVIEW is running on an supported OS and I would suggest trying opening the files on another different Mac OS X 10.5 system.
Unfortunately, currently Mac OS X 10.6 is an unsupported OS for any version of LabVIEW so I can only suggest trying on a Mac OS X 10.5.
Kind regards.
Taiki Hoshi
Applications Engineer
National Instruments Japan

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

Avoid MathScipt Comments in EXE, Build & Run Problems - NI Please Fix these Bugs!

Hello,
After 4 days of intensive work, I have finally found the solution for two major MathScript Problems:
1) Mathscript Comments are included in your EXE File !!
    - Yes, if you do not watch your steps, the EXE will include all your % Mathscript Comments!
2) Problems building, but even worse: An app that builds with NO Error and NO Warnings will not RUN and creates the following misleading Erro Message:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    With absolutely NO hint to what VI have the problem.
I have made myself an internal note how to avoid this problem. I am using LabView 2009, 2010 DS1 Release (I think this is 9.01) under WInXP SP2.
Rather than retyping everything, I will post the full text of my Notes below. I also mention several other LV BUG in this note, so pleae read carefully.
One is the TagSrv Error that occurs in LabView 2009 if I programatically deploy Shared Variables under the WinXP Development Environment. After this problem has occured, it will occur every time I restart XP, and in essense I have to restore to before I did this (thanks Nortong Ghost !!!).
Below you can find the full unabridged version of my Build, Run and Bug Notes for LV 2009 / 2010 DS1 (9.01). Hope they can be helpful to my fellow LabView programmers!
2010-07-03:
Building under LabView 2009 / 2010 DS1 Release (version 9.01)
Follow the steps below:
a) To successfully build an EXE that also runs
b) Avoid that MathScript Comments are included in the EXE !!!!!!!!!!!!!!!!
Before Building:
I) Recompile All by pressing Ctrl+Shift and pressing the RUN button on the Application_References.vi
   Then Save All (about 1200 Vis are saved)
II) Make Sure that NO User Defined Mathscript (and Mathscript Nodes?) define Empty Functions:
    This seemed to cause the following problem with the built EXE: The main VI will be broken, and a dialog reports:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    MathScitp BUG: Empty Functions causes no Build Errorm but RUN Error:
    The following User Defined MathScript .m files are candidates:
    log_write() and log_clear() whith do_log_write() and do_log_clear() commented out, these functions are empty.
    When calls to log_write() and log_clear() where removed, the problem above vanished !
Building the EXE:
1) Additional Exclusions:
-"Disconnect type definitions": YES
- "Remove unused polymorphic VI instantces": YES
- "Remove unused members of project libraries": NO (do not know if this is important)
2) Advanced:
- Enable Debugging: "NO"
3) Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE if you use the New Build File Layout:
   IMPORTANT !!!!!!!!!!!!!
   Advanced:
   "Use LabView 8.x file layout": YES !!!!!!!
   Using the new layout, causes ALL COMMENTS FROM USER DEFINED MATHSCRIPT .M FILES TO BE INCLUDED IN THE .EXE !!!!!!!
4) BUG: DSC Reference Problem in LabView 2010 DS1 release:
   In VI Deploy_Shared_Variables.vi we deploy alle Shared Variables using the "Deploy Libraries.vi" which is a part of the DSC option.
   As long as only deploying of Variables is used, using this VI should NOT require any DSC Runtime license.
   We have used this before with no compilation problems.
   However, starting with LV 2009 SP1 (or was it the DS1 2010 upgrade) LV will start nagging us to resolve references to tens of VIs
   in the DSC lib file ! Solution: Used press "Stop" on the dialog, and the Build will succeed and the EXE will work !
   Optionally, we could use the following Invoke node for the deployment:
   (see: http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6). Excerpt from this description:
<<Right-click the block diagram to bring up the programming palette and go to Programming»Application Control and place the
    Invoke Node on the block diagram. Using the hand tool, click Method and select Library»Deploy Library>>
5) LabView BUG: Do NOT RUn the Application under the WIn XP SP2 Development Environment if the APP Deploys Shared Vars:
   This will cause the Dreaded TagSrv Error: "TagSrv.exe: This application has requested the runtime to terminate in an unusual way".
   After this Error has occured, it will reoccur each time WinXP SP2 is restarted, and (Network) Shared Variables will NOT work any more!
Geir Ove
Attachments:
LabView_Tagsrv_Error.jpg ‏26 KB

Hello Geir,
I have tried to reproduce the behavior you are seeing where .m file comments appear in the final built executable. However, I am unable to do so using LabVIEW 2009 SP1. I have a caller VI with a MathScript node that calls the adder function in adder.m. The contents of adder.m are as follows:
% ADDER This function adds 3 to its input variable
%   y = adder(x)
%   INPUT: x
%   OUTPUT: y, equal to x + 3
function y = adder(x)
y = x + 3;
I have configured the build specification as you mention in steps (1) and (2):
Additional Exclusions
- "Disconnect type definitions" Yes
- "Remove unused polymorphic VI instances" Yes
- "Remove unused members of project libraries" No
Advanced
- "Enable Debugging" No
At first, I did not include the adder.m file in the project. I built the application and was not able to find the text "adder" anywhere in the EXE. Then, I added the .m file to the project and put it in the "Always Included" section in "Source Files." Again, I was not able to find the search text in the built EXE. In step 3, you mention
geirove wrote:
   "Use LabView 8.x file layout": YES !!!!!!!
but in the 5th post in this thread, you state
geirove wrote:
Compile using the new compile method ( Use LabView 8.x file layout": NO),
I have tried both settings in the Advanced section, but again, I am not able to find any comments in the EXE. I even added a call to the "path" function in adder.m. This puts a warning glyph on the caller MathScript node and generates different code. The EXE will return an unknown symbol error for adder (any VI with a warning glyph will not work in a built app), but I am not able to find any comments in the EXE. This project is attached below.
As for your other item with a broken EXE if you call empty functions, I am unable to reproduce this as well. I have taken the last attachment to your third post in this thread (the log_write function) and called it from the caller VI as well. The EXE runs just fine and I do not find any comments in this EXE either.
Unfortunately, there was a rather serious issue in the LabVIEW 2009 MathScript RT Module, where some internal MathScript VIs could become corrupted when building executables. Have you tried running the "Find Bad Instantiations" tool from this Knowledge Base article? Simply installing the SP1 version on top may not have corrected any VIs that may be corrupted.
Due to our difficulty in reproducing the issues you mention, could you modify the attached project or else attach a new project, appropriately configured, that builds an EXE with .m comments embedded in it? This way, we can uncover any minute details that we're overlooking.
Grant M.
Senior Software Engineer | LabVIEW MathScript | National Instruments
Attachments:
MComments.zip ‏186 KB

LabVIEW 2009 - Executable w/ Remote Panels

Just hit a wall.
I'm want to make an installer that sets up the remote panel webserver and document for me. My goal is to not have to tweak or move setting files, or my html files around to get this to work. I can get it to work, but only with a little bit of tweaking.
Here is the krux of the problem (and I will get to the details of my setup after that):
I can't place my document.html that contains my web page with the remote panel in the appropriate folder automatically using the "Source Files" tree in my installer. See the attached image.
Within the niwebserver.conf file that my application creates (because my custom .ini file has WebServer.Enabled=True) there is a variable $LVSERVER_ROOT.
This variable points to:
$LVSERVER_ROOT = "C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\2009\webserver"
The default documentroot (where the .html files go) is:
DocumentRoot "$LVSERVER_ROOT/../../www"
Which resolves to:
"C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\www"
Seems somewhat trivial.
1. Make a custom .ini file for my compiled program that has the WebServer.Enabled=True, add it to my project and set it as the .ini file for my build specifications.
2. Make a .html file using the Web Publishing Tool, and add it to my project.
3. Have my .html file placed in "C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\www"
The closest alias for this is [LV90RTEDIR] which resolves to C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\LabVIEW 2009\. But I can't seem to figure out a way to select the directory above. I suppose I could make the file path in the [ProgramFilesFolder], but what if the user decided to place the run-time in some other folder (can they even do that?).
How should I resolve this? Should I just hard-code the path from the [ProgramFilesFolder] directive onward?
Thanks!
-nic
Attachments:
My Installer Properties.jpg ‏69 KB

Hi mishkin,
I will have a read through your linked article. However, I was able to get the installer to setup everything for my target computer w/o me messing with config files as desired. The steps I followed were:
1. Code a desired VI and place it in a Project
2. Create a custom .ini file with the line "WebServer.Enabled=True". Add the .ini file to your project.
3. Create a Build of the VI, with the custom LabVIEW .ini
4. Use the web publishing tool to generate a .html file for the VI. The .html file will be placed in the root of your LabVIEW web server folder (see options dialog). For me this was C:\Program Files\National Instruments\LabVIEW 2009\www. If you study the .html file, you will see that it would not be difficult to make your own .html file.
5. Add the .html file to your project. (As a pre-step, I like to copy the .html file out of my web server root and into my project directory).
6. Build your application
7. Create an Installer. Add the application build of your VI to your desired directory. Place the .html file in [ProgramFilesFolder]\National Instruments\Shared\LabVIEW Run-Time\www
8. Build your installer
9. Install on target machine
So long as your target machine doesn't have another web server running on port 80 (which would require the need of an additional config file to be included to put the web server on another port), and the target machine's local group policies and firewall allow it, a user should be able to open their browser and point it to http://<targetmachine>/<targetvi>.html and be connected to that front panel.
NI has come a long way in making this feature very accessable. My only complaint is the lack of documentation. Although v8.5 and 8.6 were well documented, the steps in v2009 have changed and I had to figure them out through trial and error.
Now I need to add to my code that will allow my user to turn on and off the web server.

LabVIEW 2009 Build Path Problem

Similar Messages

Maybe you are looking for