Troubleshooting LabVIEW Stand-Alone Applications (Executables)

Updated Apr 26, 2018

Reported In

Software

  • LabVIEW

Issue Details

I built an executable in LabVIEW and I have deployed it on multiple machines. In some machines the application works fine but it fails in others.

Solution

When deploying a LabVIEW executable consider the following aspects:
  • You must install the same LabVIEW Run-Time Engine version used to develop the application on the deployment environment, as well as any driver such as NI-DAQmx, NI-VISA, NI-488.2, among others used by the application in the development environment. In the article Distributing Applications with the LabVIEW Application Builder, you will find information about deploying LabVIEW executables and the requirements for it to properly work.
  • If after verifying that the proper software is already installed in deployment environment the application does not work as expected, you can re-build the executable in the LabVIEW Application Builder and check the Enable debugging option in the Advanced menu. This option will allow you to remotely debug the application deployed on the target from the developer machine using the debugging tools. For information about how to configure the LabVIEW executable with debugging enabled and how to remotely access the application follow the steps in Remotely Debugging Executables in LabVIEW.

Additional Information

Some modules require a specific Run-Time Engine to be installed in the deployment machine to work as in the development environment, such as the Vision Deployment Module which requires the Vision Run-Time Engine to be installed and activated in the deployment machine.

WAS THIS ARTICLE HELPFUL?

Not Helpful