Build was unsuccessful

[Echoman]

I am trying to build EXE and I keep getting message "A VI broke during the build process from being saved without block diagram.  C:\Program Files\National Instruments\Labview 2017\vi.lib\addons\_office\excel.llb\Excel Find and Replace (num).vi. 

I enable debugging when creating a build and it will create the exe and run.  How can I create a build without enabling debug in the build?  How do I include the block diagram of this vi?

[cbutcher]

I suspect that VI might be under your Dependencies section.

If you drag it into the project directly (from Dependencies) then you can give it special settings for its BD inclusion under the Source Files options.

Here you can see if I unchecked the "Use default save settings" box and removed check marks from other boxes I could change the behaviour.

[Echoman · Accepted solution]

I found my problem.  I opened the vi C:\Program Files\National Instruments\LabVIEW 2017\vi.lib\addons\_office\Excel Find and Replace (num).vi and it was broken.  It said the Invoke Node had missing connections but everything was connected.  I right clicked on the Invoke Node and selected something like Reconnect and it fixed the broke VI.  I built the application again without the "Enable debugging" and it built the exe with no problems.

Thanks you for your input.

[nfajsf]

I got the same problem.

Thank for your solution.

[aeastet]

You should make your

---

@Echoman wrote:

I found my problem.  I opened the vi C:\Program Files\National Instruments\LabVIEW 2017\vi.lib\addons\_office\Excel Find and Replace (num).vi and it was broken.  It said the Invoke Node had missing connections but everything was connected.  I right clicked on the Invoke Node and selected something like Reconnect and it fixed the broke VI.  I built the application again without the "Enable debugging" and it built the exe with no problems.

Thanks you for your input.

---

answer as the solution.

[djb]

Thanks for sharing this!

I ran into the same problem using Labview 2022.  Using the 'relink' trick and saving the file in library solved my problem as well