LabVIEW 2019 Invalid App Kind

[JGar]

That is weird.  I'm using Windows 10 and get the "Development System" return.  I use this feature in a couple of different applications across multiple machines and haven't had an issue with LabVIEW 2019.

[RTSLVU]

I have not had an issue with any of my deployed applications because my VI also exits on "invalid".

I just noticed it because I am updating an application I wrote in LV2017, where it all worked fine. After I updated that system to LV2019. Then every time I ran my program it would exit the development system at the end of the program. I can open the same source code on LV2017 on the same machine and it works fine...

[Bob_Schor]

This is truly weird.  I just created the same 3-function code you mentioned in your first post, ran it on Windows 10 (x64) on a LabVIEW 2019 system (32-bit, 19.0f2).  Said "Development System".

Can you create a little VI that demonstrates the bug and post it?  It would be fascinating if it worked on (say) my system and failed on yours -- could suggest that there's a problem with installation on your system.  Hmm, is anyone having problems installing LabVIEW 2019?  [That's not supposed to be a joke ...].

Bob Schor

[ben64]

Is there something showing up if you probe the error wire out of the property node?

Ben64

[Darren]

Does the same problem happen if you drop a new property node on the block diagram and set the property? i.e. maybe something is corrupt with the property node from your old code?

Also, I'm curious to know the answer to the previous question of whether or not the node is returning an error.

[thols]

19.0.1 on Win10 here. I get "development system". But I have always wondered if and when "invalid app kind" can happen. are you getting a valid reference from the Open application reference node?

[rolfk]

You get invalid app kind when either error in indicated an error or the property node itself generated an error. Darrens suggestion to try to create a new node and see if that works is a good one.

I’ve seen property nodes go totally weird in software having been upgraded through multiple LabVIEW versions. Not frequent enough to make much hassle about it but definitely possible. Especially if the original was created in 8.x and before, this can occasionally happen. Recent versions have become a lot less “insane” but they seem not always able to detect corruptions that happened in earlier versions