Build breaks because vi is broken ... but it's not :/

[Kyle97330]

---

@kutt wrote:

But on build I notice that:

What application instance does the VI show (lower left corner of the VI)?

What error do you see when you click on the broken run arrow?

---

Kutt,

You replied after this but skipped this VERY important question. Did you click it?

Since you are able to get to the block diagram of the built EXE, you should be able to explore it.  In the past when this has happened to me, I was able to click around and open subVIs until I found a broken subVI, then click through that one until I found a broken sub-sub-VI, until I finally came to a VI that was actually broken.  In my case it was a DLL call that had gone bad (the DLL was missing from the location it should have been moved to during the build).  If you can see the diagram, check every single subVI.  If one or more is also broken, go deeper.  If not, then you at least know the error is in your main VI.

[kutt]

I can't click the broken arrow, since the builder takes the focus when this happens ...

see here:

once it shifts to the error message the broken arrow turns back to  a normal (working) one ...

[kutt]

No, I don't have shift registers, that contain classes.

I got a **bleep** load of dll's, which can cause issues. But I moved them all into the root dir of the project, since I got a lot of problems with that in the past. 

It still runs like a charm, but still won't build an exe 😞 It sucks, that there is no useful error message. It just tells me that the vi is broken, which is not the case. Slowly this starts to look more like a bug in LabView to me.

This should be the latest version, at least the updater tells me that there are no updates available ...

Does NI have some kind of Bug Report System?

[daveTW]

Hello kutt,

perhaps there is a problem with your 64 bit LabVIEW and a 32 bit DLL. I don't know that, but perhaps the Application Builder checks that and complains, just to be sure.

[kutt]

Yea, I thought about this too ... but they are x64 like the LabView I use

PE32+ executable (DLL) (console) x86-64 Mono/.Net assembly, for MS Windows, 2 sections

I don't think that's the problem. If they were x86 DLL, then the vi would not run at all or just crash

[thols]

Have you looked at: Error 1003 Occurs When Trying to Create an Executable

If that does not help, I would also look at: Error 1502 When Building an Application in LabVIEW

[kutt]

All checked, even reinstalled LabView - still not building. Same Error every time: The vi is broken (but it's not).

PS: I did build an other project, so the builder itself seems to work. No idea why the f.. it won't work on this project.

The problem is, that i need an exe file, since our customer is not supposed to get the source files.

Maybe I try to ask out IT if we got someone kind of support contract with NI...

[thols]

So, if you have done everything we have proposed and what the links say, then you now have a clean mass-compile? Try a forced recompile and then mass-compile again and see if anything comes up (a tip Darren N mentioned sometime).

I still suspect its a simpler issue, but take a look at these tips. For example the checkbox roulette: LUDICROUS ways to Fix Broken LabVIEW Code with Darren Nattinger | GDevConNA 2022

I don't remember if it was suggested, but create a new project and build spec. There could be something wrong with the project file.

If that does not help, go back in SCC versions and go from a version that works, and find what version breaks it.

Another way is to build a smaller part of the application and add parts until it breaks.

[billko]

Have you tried including the dll explicitly?

[raphschru]

It reminds me of this bug on the Error Ring that did break my PPL build:

https://forums.ni.com/t5/LabVIEW/Error-Ring-Bug-with-Enum-Input/m-p/4299501

Did you use somewhere an Error Ring with an enum input?

Regards,

Raphaël.