LabVIEW Executable Runs on Development Computer but Not Deployment Computer

Updated Feb 22, 2019

Reported In

Software

  • LabVIEW
  • LabVIEW Application Builder Module
  • LabVIEW Run-Time Engine

Issue Details

  • I have created an executable of my LabVIEW application using the Application Builder and it works fine on my PC but doesn't work on my colleague's PC. Should I create an installer instead? 
  • I sent an LabVIEW executable to a customer but my customer is unable to run it on his computer. Dialog box pops up with "LabVIEW: Resource not found." How can my customer run my executable?
  • I have downloaded the LabVIEW Run-Time Engine compatible with my system and executable, but the program still will not run on my target machine.

Solution

  1. A PC must have all the required toolkits, drivers, and run-time engines installed that were used to develop the LabVIEW application. When interfacing with hardware, the correct hardware drivers must also be installed on the computer (DAQmx, 488.2, etc). These can manually be installed or included in an installer along with the executable. Learn more about building an installer in Distributing Applications with LabVIEW Application Builder .
  2. Check to make sure the LabVIEW Run-Time Engine installed is compatible with the LabVIEW version the executable was developed in. Also ensure that you have the standard LabVIEW Run-Time Engine, and not the LabVIEW Run-Time Engine Web-Based Plug-in (formerly known as the LabVIEW Minimum Run-Time Engine). The Web-Based Plug-in is intended for viewing VIs embedded in a web page, and not for running executables.
  3. Check to make sure your application is running on the same operating system version as the one it was developed in. Executables are platform-dependent and should be built on the same version of the same operating system as the target computer.

Additional Information

Two deliverables the Application Builder can create are Stand-alone Applications and Installers. The two have unique use cases and it is important to understand when to use one versus the other.

Stand-alone Applications

  • Use stand-alone applications to provide other users with executable versions of VIs. (Windows) Applications have a .exe extension. (Mac OS) Applications have .app extension. 
  • Stand-alone applications only contain the LabVIEW VIs and do not contain any other resources needed to run. For the executable to run, the PC must have the necessary run-time engines, drivers, etc. 

Installers 

  • (Windows) You can create an installer to distribute stand-alone applications, shared libraries, and source distributions that you can create with Application Builder. 
  • Installers can include drivers and libraries to ensure the user's PC has all the resources the .exe is dependent on.
  • Installers can also include custom installer graphics to customize the installation experience. 

WAS THIS ARTICLE HELPFUL?

Not Helpful