LV 2009 SP1 Build Error NI

While trying to make a build on LV 2009 SP1, I get this error:
The build was unsuccessful.
An error occured while saving the following file: Sample.VI
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 1 occurred at 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_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s): LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Note I do not use any GPIB. Also when I build the project on VL 2009 (no SP1) on a different machine, I get no errors. Any ideas?
Solved!
Go to Solution.

Ugh. I've seen this in 2009 as well as quite a few others here. There seems to be no real explanation or consistent solution to this error. 1st thing to try is to remove all boolean constant-driven case selectors. For some reason the compiler gets confused with those - sometimes. See how that goes. Eventually this problem seems to resolve itself after a few days of development. That's been my experience. Sorry I can't be of more help.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

Similar Messages

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** 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] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
Thank You
Attachments:
Broken VI.gif ‏8 KB

Scott,
Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
I would recommend starting with these steps. Let me know if any of these solutions work for you.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

2009 sp1 slow build

Trying to build my application after I just upgraded to sp1 on LabVIEw 2009.
It seems to take a long time, while using a lot of cpu power.
Progress is very slow. Hard drive is not being used intensly.
Running the same on the 2009 f2 version. Building from the same sources.
Very slow as well.
I'm new to the performance of the build feature in 2009. Coming from version 7.1.1
And I'm very surprised on the difference. Why does the build take sooooo looooonnnnggg on the 2009 version(s)??
We build smaller apps before on 2009, and did not seem a big deal. But this bigger application.
And then after about 15 minutes, I get an error message:
Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
So this is running with the 2009 f2 version on XP pro with 1Gb of ram. And for the 2009 sp1 version on windows 7, with 8Gb of ram....
So do not expect any memory issues with the SP1. Could this be a windows 7 x64 issue?
Anyone any experience with building larger applications?

Hello Everyone,
We have observed that building executables in LabVIEW 2009 is slower than in 8.6. In most cases it was about 10 to 20%. However, in some larger builds we have seen almost a 3x or 4x slow down. This large slow down has been reported to R&D for further investigation (CAR 205343). In the case that was reported to us the build was about 8000 VIs and took 2GB of memory to complete.
There wasn't a difference between LabVIEW 2009 and 2009 SP1. The slow down occurred between 8.6.1 and 2009. Does your slow down occur between 2009 and 2009 SP1?
Message Edited by Jon S. on 03-09-2010 08:42 AM
Regards,
Jon S.
National Instruments
LabVIEW R&D

LV 2009 SP1 EXE Builder issue

Hi Guys:
I found that the exe file built from LV 2009 SP1 can be easily extracted by WinRAR , i can see all the main or sub vi , is this a bug? or a settings risk? I haven't found the same problem in LV 8.6 ,
thanks
Solved!
Go to Solution.

I do not think you should think to much about it. One of the first discussions about it is here http://forums.ni.com/t5/LabVIEW/decompiling-2009-executable/td-p/991662. It is correct that they will be able to extract the VIs But they will not be able to see any more than you show in your program.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

Build Error While importing standard application into NWDS

Hi all,
I am trying to Import T&E Standard Applications into NWDS.
Two components (tra & tra/tre) have to be synched to the studio. These two are interdependent..
One Component I am able synch and create project perfectly but when i try to do the second one, i am getting Generation BUILD Error...
Help me in this regard..
Thanks
Malla
Edited by: challa mallareddy on May 7, 2009 12:34 PM

Hi,
As per your error, I think you have already created a project with name NewParProject. Give a different name and then check.
Also check if your par file is not corrupt. Download it again and follow below steps in NWDS :
Go to File>Import > Select par file >
>Browse and select the par file>
>Give a project name i.e. ParProjectTest > Finish.
This should work.
Regards
Deepak

[SOLVED] Xsane Build Errors

xsane: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
Prompted me to rebuild sane-backends-1.0.20 against libjpeg 7-1 (no problems there) and xsane (with build errors):
--disable-gimp --disable-nls --disable-sanetest --disable-gimptest --disable-gtktest --prefix=/usr/local
xsane-back-gtk.c: In function 'xsane_back_gtk_range_display_value_right_callback':
xsane-back-gtk.c:1966: warning: cast from pointer to integer of different size
xsane-back-gtk.c: In function 'xsane_back_gtk_range_new':
xsane-back-gtk.c:2016: warning: cast to pointer from integer of different size
xsane-back-gtk.c: In function 'xsane_back_gtk_set_sensitivity':
xsane-back-gtk.c:2615: error: 'SANE_CAP_ALWAYS_SETTABLE' undeclared (first use in this function)
xsane-back-gtk.c:2615: error: (Each undeclared identifier is reported only once
xsane-back-gtk.c:2615: error: for each function it appears in.)
make[1]: *** [xsane-back-gtk.o] Error 1
Is there a known resolution/workaround for this?
Last edited by adamlau (2009-07-15 18:38:39)

Just noticed the MissingCapsFlag.patch, build went without a hitch, xsane works as expected...
Last edited by adamlau (2009-07-15 19:18:39)

LabVIEW Run-time 2009 SP1

When I try to install LabVIEW Run-time Engine 2009 SP1 on a Windows 2000 machine I get an error message that states "Windows XP SP2 or greater required"
The compatability chart http://www.ni.com/labview/os-support/f/ states that LV 2009 is supported on Windows 2000. What gives?

Do you have administrator privileges? Also, do you have any security programs installed on your computer that could hinder the installation?
Applications Engineer
National Instruments

2009 SP1 Debug Deployment Only

I've install LabVIEW 2009 SP1 and it works fine but it indicates "Licensed for Debug Deployment only" on the opening screen. We use the Volume License Manager and it correctly checks out a Development License which is correct for me.
Is this something I should be concerned about? It doesn't seem to be constrained in any way, i.e. I can build executables.

Here they are. I'm "DC10020"
Attachments:
VLM_Screenshot.jpg ‏511 KB
NILM_Screenshot.jpg ‏227 KB

C++ build error with LabVIEW DLL

Hi, I'm a student at UC Irvine learning to use LabVIEW. I am working on a practice project for which I have to use a PID system to control the temperature of an object. Things are starting to get a little messy with nested control statements, loops, etc., so I figured I'd export a LabVIEW DLL with all the hard to code stuff, such as interfacing with my instruments, and plotting data or whatever, and do the number crunching and keeping track of stuff in C++.
The DLL file I made in LabVIEW went off without a hitch as far as I can tell, but when linking it to my C++ test program (which at this point is just including the LabVIEW's .h file for the DLL and an empty main() function), I get a lot of build errors. I am using Dev-C++ which uses g++ to compile the code.
Here is a pic of my build errors:
Solved!
Go to Solution.
Attachments:
LabVIEW_compile_error.JPG ‏184 KB

Normal windows apps are not as forgiving about where you can put your DLL as LabVIEW. You have to have a DLL either in the direcotry where the executable file itself resides (that would be your build directory, not the source directory), the windows or system directory, or any directory that is set in the PATH environment variable. Anythin else will most likely not work, or at least not reliably.
No need to add the cintools directory into your include file paths nor the library file paths. you would only need that if you decided to let the DLL export native LabVIEW data types in which case you would need the LabVIEW manager functions to prepare the correct data buffers.
Rolf Kalbermatter
Message Edited by rolfk on 07-30-2009 07:49 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

[svn:osmf:] 11241: 10.1 related build error.

Revision: 11241
Author:   [email protected]
Date:     2009-10-28 13:08:09 -0700 (Wed, 28 Oct 2009)
Log Message:
10.1 related build error.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/video/VideoElement.as

Thanks for reporting this. It is a known bug (3985036) in that double-clicking on the column will still shuttle the column over. Since this is invalid behaviour the FK is not getting updated.
Regards,
Lisa
JDev QA

Installer Build Error using LV Runtime Engine 2010

I had an executable and installer working that were built in LV2009. Since then I modified my source code and saved as LV version 2010. I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed. So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer. However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
Thanks in advance.
Solved!
Go to Solution.
Attachments:
Installer Build Error Message.docx ‏13 KB

Hello,
I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error
------------------ERROR MESSAGE-----------------------------------
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ to: C:\ProgramData\National Instruments\MDF\ProductCache\ ***************** Error: Windows SDK function returned an error. (Error code -12)The system cannot find the path specified.
***************** Error Details:Error in MDF API function: _MDFDistCopyList_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
--------------------MESSAGE END------------------
In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
Attachments:
Additional.jpg ‏174 KB

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...

I'm trying to read some XML data from temperature logger over my network. I'm using LabView version 2009 sp1. I'm using the URL Get Document Vi. It works fine when using Internet sites like google or foxnews etc...
When I use it with my temperature logger most of the time I get an Error 66...but some times it does work and actually retrieves the document.
I can use the same address "http://172.22.21.68/XMLfeed.rb" (Internet Explorer or Google Chrome) in my browser and get a response every time. When accessing from my browser the server in the temperature logger does take around 6 seconds to respond, but it does respond every time.
Is the URL Get Document Vi exceeding a timeout? If so, where can I set it to wait longer?
Attachments:
Error 66.jpg ‏183 KB

It looks like the TCP Buffered Read has a 2.5 sec timeout, I believe that is where I had trouble as well. Try creating your own URL Get HTTP Doc vi in which you call URL Get Document in normal mode, with an appropriate number of characters to fetch (enough characters so that you capture all the important data in the XML file).
Attachments:
ex1.PNG ‏33 KB

TDMS File Corrupts on Close in LV 2009 SP1

I have an application that logs data to a TDMS 2.0 file, LV 2009 SP1, Windows 7 x32.
Initially, I set it up so that the app opens one R/W reference to the file. The state machine program writes data to the file in one step, then reads back the last 1000 points in another. The logging is slow, roughly 1Hz. There is no possibility of concurrent Reads and Writes.
When the program closes, I call the TDMS CLOSE method.
When I restart and try to read the data, I get error -2511/0xFFFFF631 "LabVIEW: The specified TDMS file is corrupt." Every time.
When I try and open the file in the TDMS viewer, the viewer shows the wrong number of samples in the properties, then shows no data at all (I assume it's eating the error, since it does not present it to me).
I have tried:
1) commenting out the code that reads. No good.
2) Opening a separate reference each time I wish to make a read. Nope.
3) Buffer On/Off
4) Flushing
5) Deleting the index and trying again.
6) Removing the CLOSE function
7) Killing the app instead of gracefully closing
8) Changing the filename/path
9) Writing to an SSD disk
10) Writing to a SATA disk.
None of that works. Essentially, the TDMS file is fine until it is closed. Then it is corrupt.
Any ideas?

Hi Jed,
I have a couple of questions:
Have you tried with the latest TDMS component? It's free to download, and here it is: http://zone.ni.com/devzone/cda/tut/p/id/9995
Is that possible or convenient for you to post your reproducible VI here, it would be great helpful for us to look into?
I have made a very simple VI for recovery corrupted TDMS files, attached in this post, maybe you can have a try, but please backup your file before trying.
Attachments:
RecoveryTDMSFile.vi ‏17 KB

LV 2009 SP1 Build Error NI

Similar Messages

Maybe you are looking for