LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error in exe file

Solved!
Go to solution

Hello every one

 

When running exe file in my clint pc i got error "This vi is not executable .the full development version of labveiw is req to fix the errors"

 

I am using labview professional 2012 Version

 

In my clint pc i runned a exe file it is running perfectly but after including a vi which reads hard disk serial no. the above error is coming in my clint pc please see the attached vi

 

0 Kudos
Message 1 of 15
(4,338 Views)

Did you create an installer and installed in the client PC after including the new VI?

-----

The best solution is the one you find it by yourself
0 Kudos
Message 2 of 15
(4,333 Views)

yes sir 

 

I have created installer and installed

0 Kudos
Message 3 of 15
(4,327 Views)

Where do you have the vi that you added later? I believe some files associated with the added vi is missing.

-----

The best solution is the one you find it by yourself
0 Kudos
Message 4 of 15
(4,321 Views)

please see the attached vi

0 Kudos
Message 5 of 15
(4,318 Views)

Please attach the vi in 2011 version.

-----

The best solution is the one you find it by yourself
0 Kudos
Message 6 of 15
(4,313 Views)

see this vi in 11 version

0 Kudos
Message 7 of 15
(4,310 Views)

Are the correct version of DotNET installed on your client PC? If not you will see this error.



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 8 of 15
(4,296 Views)
Solution
Accepted by topic author Nagaa

@Nagaa wrote:

see this vi in 11 version


".NET, configuration files"  you'll want to go to that index in the LabVIEW help file

 

You will need to include a "MyApp.exe.config" file with this text

 

<?xml version ="1.0"?>
<configuration>
   <startup
useLegacyV2RuntimeActivationPolicy="true">
      <supportedRuntime
version="v4.0.30319"/>Or whatever version of the CLR you are using
   </startup>
</configuration>

 

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 9 of 15
(4,288 Views)

0 Kudos
Message 10 of 15
(4,264 Views)