f



LabVIEW 8.5.1 "The build was unsuccessful"

When attempting to build my executable in LabVIEW 8.5.1 I get the following dialog:
 
<img src="http://forums.ni.com/attachments/ni/170/338657/1/Build%20Errors.PNG"> 
&nbsp;
I've tried recreating my build specification, reinstalling LabVIEW, commenting out sections of my code and nothing seems to help.&nbsp; Has anyone encountered this before?&nbsp; Any ideas NI?Message Edited by FlamingYawn on 07-08-2008  11:24 AM


Build Errors.PNG:
http://forums.ni.com/attachments/ni/170/338657/1/Build Errors.PNG
0
x9561 (148439)
7/8/2008 4:40:07 PM
comp.lang.labview 35210 articles. 1 followers. vasusachin24 (1) is leader. Post Follow

12 Replies
1001 Views

Similar Articles

[PageSpeed] 40

Hi,
&nbsp;
Are you building a .exe application? In that case, please verify that all your startup and always included VIs exist in the same path and have been properly compiled. You can try Tolls&lt;VI Analyzer&lt; Mass Compile. Also are you using DSC or shared variables in your code?
&nbsp;
Ipshita C.
0
x9561 (148439)
7/9/2008 6:40:08 PM
Hi Ipshita,
&nbsp;
Thanks for responding.&nbsp; 
&nbsp;
Yes, this is "a .exe application."&nbsp; 
&nbsp;
My startup path is correct, and I tried building with all my "always included" VIs removed.&nbsp; Same error.
&nbsp;
I've mass compiled several times.
&nbsp;
I'm not using DSC or shared variables.
&nbsp;
I'm able to build the executable on another computer with the exact same project and code (we use source code control), so something must be different about my environment or setup.
&nbsp;
Thanks,
&nbsp;
Robert
0
x9561 (148439)
7/9/2008 7:10:05 PM
I have seen this error before, but when I was using 8.20 and the Touch Panel module (compliling a CE .exe).&nbsp; The build error tells you absolutely nothing about how to resolve it :smileymad:.&nbsp; However, after some trial and error I found the problem (in my case) was that labview was having trouble overwriting the .exe from a previous build.&nbsp; That is, the target destination for the build already had a .exe from a previous build and it would not replace it.
If you have any files in the target destination for the build, try deleting them and then run the build.&nbsp; Typically you don't have to do this.&nbsp; Usually can do a rebuild into the same directory and LV will replace the old build.&nbsp;Message Edited by StevenA on 07-09-2008  01:54 PM
0
x9561 (148439)
7/9/2008 8:10:12 PM
Thanks for responding, Steven.
&nbsp;
I've seen the problem you mention as well.&nbsp; Especially when dealing with source code control.&nbsp; However that's not the problem in this case.&nbsp; I cleaned out the destination directory to make sure that wasn't the problem.
&nbsp;
Thanks,
&nbsp;
Robert
0
x9561 (148439)
7/9/2008 8:40:08 PM
I wonder if it could still be related if for some reason LV cannot get the folder access rights it needs.&nbsp;
0
x9561 (148439)
7/9/2008 9:40:07 PM
When I diagram disable all of my code, the executable builds fine.&nbsp; So that would seem to rule out folder rights.
I uninstalled all NI software and drivers from my computer, reinstalled them, and I still get the error.
NI, what conditions cause the dialog to be blank as shown above?Message Edited by FlamingYawn on 07-09-2008  04:44 PM
0
x9561 (148439)
7/9/2008 10:10:05 PM
Figured it out.&nbsp; What's causing it, at least.&nbsp; Not why.
&nbsp;
I added 2 GB of RAM a little while back, upping my memory to 4 GB.
&nbsp;
I didn't know WIndows had a problem using the full 4 GB; it was only using 3 GB, but that's another issue.
&nbsp;
One of the fixes I read had me add "/PAE" (Physical Address Extension, or something like that) to c:\boot.ini.&nbsp; It didn't help, but I left it there.
&nbsp;
When I removed it, the build worked.
&nbsp;
Maybe NI can figure out why.
0
x9561 (148439)
7/9/2008 10:40:09 PM
That is really strange.&nbsp; I'm interested to see if NI can determine why.
0
x9561 (148439)
7/10/2008 5:10:08 PM
Removing /PAE isn't enough, now.&nbsp; I need to have /3GB in order to build.
0
x9561 (148439)
7/11/2008 5:40:08 PM
Hi Robert,
Please let me know the answers to the following questions:
1. The operating system that you are using--is it 64-bit or 32-bit?
2. The exact amount of physical memory that you have--please give me the number shown in System Information.
3. Any additional installers that you are using--NI-488.2, NI-DAQmx etc. 
If you are running a 32-bit installation OS on your computer but have 4GB of memory, that is indeed a reason for your build error. Labview being a 32-bit installation maxes out at 4GB and therefore, the threshold RAM is set to 3GB. You do not need to have PAE enabled as that is used only for 64-bit installations or for a 64-bit memory. Please have a look at <a href="http://digital.ni.com/public.nsf/allkb/49C3316C0FFC23C286256E4B006FB6A4?OpenDocument" target="_blank">this</a> knowledgebase article for more information. Enable PAE only if you have 64-bit memory addressing. Otherwise, the only workaround is to use 3GB of RAM. Hope this helps. 
Ipshita C.
0
x9561 (148439)
7/14/2008 8:40:08 PM
1.&nbsp; 32 bit
2.&nbsp; 3.00 GB (it displayed this before I took out my 4th 1 GB stick, as well)
3.&nbsp; DAQ, GPIB, VISA, CAN, Serial
I lowered my RAM to 3 GB and removed the '/PAE'.&nbsp; I was still getting the build error until I added '/3GB'
0
x9561 (148439)
7/14/2008 10:40:05 PM
Hi Robert,
Even after you removed your 1GB stick the boot.ini file does not update automatically. Also, are you using SP3? In that case, it is necessary to specify /3GB as a boot.ini switch. Hope that answers your question.
Ipshita C.
0
x9561 (148439)
7/15/2008 5:40:04 PM
Reply: