This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

This VI Is Not Executable Error When Trying to Run an Executable

Updated Jul 24, 2020

Reported In

Software

  • LabVIEW
  • LabVIEW Runtime

Issue Details

When trying to run my LabVIEW executable, I receive this error: 

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

I have installed the correct version of LabVIEW Run-Time Engine and all necessary drivers. What is the cause of this error?

Solution

  • The cause of this is often a missing version of the .NET Framework on the non-development computer.  To resolve the issue, you should install the .NET Framework that the application uses in the development machine:
  1. You can download the missing version of .NET Framework from Microsoft's website. Check Additional Information for information on determining what versions of .NET you have installed.
  2. Make sure all NI and third party drivers being used by the executable are installed on the computer trying to run the executable.
  3. If installing the .NET Framework that the application uses does not solve the error:
  • Try debugging the executable remotely to identify where the error is occurring. This will give you more information on what might be the cause of the error.
  • If you are using XControls you can try checking the Disconnect Type Definition option in the Build Specifications and add the XControls to the Always Included section.
  • Try the same steps outlined in this article (especially if you have previously encountered Error 1502 at any point while building the executable).

Additional Information

You can check the versions of .NET installed on Windows by following the steps below:
  1. Click Start » Run (Alternatively press Windows Key + R)
  2. Type regedit in the Run dialog box.
  3. In the Registry Editor navigate to HKEY_LOCAL_MACHINE » SOFTWARE » Microsoft » NET Framework Setup » NDP to view all versions of .NET Framework.

When mass compiling, LabVIEW opens and closes VIs automatically. This does the following:
  • Ensures that all subVIs exist and relinks them to the main VI. It decreases loading time since LabVIEW will not need to search for the VIs.
  • Updates the VIs to the current LabVIEW version.
  • Reports corrupted VIs which can prevent them from loading correctly.
Some applications that were developed with older OS than Windows 10 use .NET Framework 2.0 and 3.5. Windows 10 does not come with .NET Framework 2.0 and 3.5 by default, so installing these frameworks would be necessary to fix the issue.