LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"build was unsuccessful" does not provide an explanation

I get a message saying "build was unsuccessful" but no details of why it did not build.  Win7 & LV10SP1.  The "Possible reasons" window is empty (see image below).

 

It built last night.  It won't build this morning.  Nothing in the code has changed.  Using the same PC.

I will reboot the PC and see if I can blame it on windoze..  😉

 

 

 

0 Kudos
Message 1 of 23
(4,434 Views)

Rebooted the PC, restored the last version of the code and it builds.

Don't know what happened.  The only change I had made on the VI was with decorations and moving the controls a little bit.

 

No explanation...

 

0 Kudos
Message 2 of 23
(4,404 Views)

I've run across that too- (I think LV11f2 fixed it)  It seems like you need to exit and re-open the project before re-building IF you run the build from the project.  Sometimes cleaning the build worked too.  Twas very annoyingSmiley Sad


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 23
(4,398 Views)

I occasionally get builds that fail, with little (but some nonetheless) information returned. If I simply retry the build it often then succeeds!

Sounds like a cleanup issue.

Thoric (CLA, CLED, CTD and LabVIEW Champion)


0 Kudos
Message 4 of 23
(4,392 Views)

I don't know about the cleanup issue, but this is the first time (day) that I've encountered that behavior.

It's doing it again...  😠

 

Closing the project didn't work...  Closing LabVIEW didn't work either.

 

Time for reboot!

0 Kudos
Message 5 of 23
(4,383 Views)

Hi Ray,

 

This error is most likely related to one of the CAR (Corrective Action Requests) that were filed for LabVIEW 2010. As Jeff suggested uprading to LabVIEW 2011 and appliying f2 patch can help solve this issue.

Sev K.
Senior Systems R&D Engineer | Wireless | CLA
National Instruments
0 Kudos
Message 6 of 23
(4,346 Views)

Unfortunately, the client has not yet upgraded to LV2011, so I'm stuck at LV2010.

It's a shame that bug fixes are only with the latest version.  I know this is bringing up an old discussion.  Not all clients go to the latest & greatest version.  There are some clients still at LV8.2.  And one at 7.1...

0 Kudos
Message 7 of 23
(4,327 Views)

Hi Ray,

 

How often does the "build was unsuccessful" error appear?

Have you tried deleting the files created by the builder and then building again?

Have you tried building the project programmatically in LabVIEW. (Refer to the Build Targets Programmatically VI in the examples\project\programmatically build directory for an example of building an application programmatically.)

Sev K.
Senior Systems R&D Engineer | Wireless | CLA
National Instruments
0 Kudos
Message 8 of 23
(4,300 Views)

@Sev K wrote:

Hi Ray,

 

How often does the "build was unsuccessful" error appear?

When it occurred, it was consistently repeatable, during two different attempts to build.  Maybe three...  I can't remember.

 

Have you tried deleting the files created by the builder and then building again?

Of course..  😉   But that did not help / change the situation.

 

Have you tried building the project programmatically in LabVIEW. (Refer to the Build Targets Programmatically VI in the examples\project\programmatically build directory for an example of building an application programmatically.)

No, this was a simple build, manually carried out by right click on build spcification and selecting "Build ".  The build and project themselves are very simple.  Nothing fancy with the code.  No LVOOP.  Subsequent builds went fine.


 

0 Kudos
Message 9 of 23
(4,295 Views)

Just started having the same problem with LabVIEW 2011.  Worked recently with 2011.  During the build, I get this screen pop:

 

Norton error associated with Empty LV build error.png

 

To try to fix this, I just installed the 2011 f2 patch and restarted.  The problem persists.  I've tried removing the application files and building into an empty directory (problem persists).  This worked recently.  Recent change:  I removed a path control from the main VI panel and the corresponding diagram "Current VI's Path" primitive.  I *have* been running the EXE from the project by right clicking the build specification and clicking "Run".  Maybe that got me.

 

The application is small.  Actually it's just my starting architecture which does not talk to any hardware.  NI - please open attached LVPROJ and try to build the application and let me know if it's just my machine.  Thanks!


Certified LabVIEW Architect
TestScript: Free Python/LabVIEW Connector

One global to rule them all,
One double-click to find them,
One interface to bring them all
and in the panel bind them.
0 Kudos
Message 10 of 23
(4,257 Views)