LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Strange Error in Built .exe

I've built this app many times; this is the first time for this error.

When I run it, I get this:

paul_cardinale_0-1678885841880.png

If I browse to that in in vi.lib, I get this:

paul_cardinale_1-1678885875427.png

I understand the 2nd error message, but not the first.  What could cause the dependency on "Get Type Information.vi" not to be included in the build?

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 1 of 5
(1,005 Views)

The first error is related to the this property of the VI:

 

petrz_1-1678886664855.png

 

this can happen when your executable is calling a VI, but it has removed the compiled code.

 

 

0 Kudos
Message 2 of 5
(993 Views)

@petrz wrote:

The first error is related to the this property of the VI:

 

petrz_1-1678886664855.png

 

this can happen when your executable is calling a VI, but it has removed the compiled code.

 

 


No, that's the 2nd error, not the first.

Furthermore, the VI with separated code is in vi.lib; it hasn't changed, and the build use to work.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 3 of 5
(976 Views)

I'm sure you've tried all sorts of things already but a few questions:

 

1- Have you cleared the compiled object cache? It could force the recompile.

 

2- Have you tried "cleaning" the build? (Right click -> Clean)

 

3- Could you delete and replace that function? Maybe one instance in one VI got corrupted somehow.

 

4- Any chance you're calling that VI dynamically, and the linking got weird somehow? (I only ask because dynamically calling a VI in vi.lib seems like something @paul_cardinale would do to accomplish something sneaky 😉)

0 Kudos
Message 4 of 5
(955 Views)

Sorry I misunderstand it, I tough you're referencing to a VI in our library, now I'm realize that it is VI from the vi.lib

 

Clearing the VI cache is good idea, but I think for the VIs in the vi.lib the cache is located in VIObjCache (e.g. C:\Program Files\National Instruments\LabVIEW 2018\VIObjCache) it has to be cleared manually.

Message 5 of 5
(913 Views)