LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"The VI is not executable."

I have an executable that runs on my development system and after installation on the target system gives the attached "This VI is not executable." message.  This executable runs on other PCs of similar type.

Per other postings, I have updated the .NET framework of the target to match my development system and I have unchecked the "Remove unused polymorphic VI instances" checkbox.

I still get the same "maddeningly unhelpful" message.

 

This is a very simple VI that just checks the operator input against a log file to prevent duplicate serial numbers being entered, and then launches another program via the command line.

 

Any ideas?

 

Thanks,

Dennis 

0 Kudos
Message 1 of 21
(4,996 Views)

Sorry, I don't have a solution, I just wanted to point out that you probably broke some record here:

 

Your image has about 100bytes of useful information, but your attachment is ~1.5MB, or about 15000x too big. 😮

Message 2 of 21
(4,970 Views)

Does your development machine have multiple version of .Net on it? If so, NI will automatically use the latest version. We have run into this in the past when multiple version of .Net were installed. You can force which verson to use by including a file named "<application name>.exe.config". The contents would be the following:

 

<?xml version ="1.0"?>
<configuration>
   <startup useLegacyV2RuntimeActivationPolicy="true">
      <supportedRuntime version="v4.0.30319"/>
   </startup>
</configuration>

 

Simply make sure that the version corresponds to the correct version of .Net you want to use.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 3 of 21
(4,962 Views)

Yeah, I should have typed in the message rather than attaching the picture.

 

"This VI is not executable.  The full development version of LabVIEW is required to fix the errors."

 

0 Kudos
Message 4 of 21
(4,936 Views)

No, I only have .NET 4.0 on my system and I installed 4.0 on the target system.

0 Kudos
Message 5 of 21
(4,935 Views)

Is the Run-Time engine installed?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 21
(4,928 Views)

Oh yes, as part of the installer, the Run-Time Engine is installed. 

LabVIEW 2012f3 by the way.

0 Kudos
Message 7 of 21
(4,923 Views)

I should mention that the VI runs on other PCs, but not on this target.

I thought it was a memory issue since the target system only had 512MB of RAM installed and the other PCs have 1GB of RAM.  However, installing 1GB did not help.

0 Kudos
Message 8 of 21
(4,922 Views)

Does the target system have other versions of .Net installed? We would see this error fairly often until we started to include the config file with our installs.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 9 of 21
(4,906 Views)

@hartzde wrote:

Oh yes, as part of the installer, the Run-Time Engine is installed. 

LabVIEW 2012f3 by the way.


Bitness?  (developed in 64 deployed to 32?)  1/2 G RAM on the target begs me to question the OS's of both the development and target machines and the LabVIEW RTE / IDE (x64/x32) versions


"Should be" isn't "Is" -Jay
0 Kudos
Message 10 of 21
(4,893 Views)