LabVIEW Executable or Installer Not Functioning on One Deployment Machine

Updated Jul 5, 2018

Reported In

Software

  • LabVIEW
  • LabVIEW Application Builder Module
  • Measurement & Automation Explorer (MAX)

Driver

  • NI-DAQmx

Issue Details

I have a built LabVIEW executable or installer that works properly on my development machine and a deployment machine. However, it does not function on a different deployment machine. How can I fix this?

Solution

This behavior can be caused by several reasons, so there are a couple of questions to consider for troubleshooting:
  • Are the target/deployment computers the same? Is the Operating System the same? Is the hardware the same? 
  • If this is an executable, are the same drivers and run-time versions installed on the deployment machines? The software installed in each computer can be compared as obtained in the MAX technical report
  • Does the application launch at all? Does the error occur when trying to perform an specific action?
  • You could consider using Remote debugging to troubleshoot the program. 
  • Are there different versions of the executable/installer?
  • If the application is stuck in a certain state, could certain logic be preventing it from preceding? (i.e. reliant on some DAQ input that is not triggering the next event)
If the application interacts with hardware:
  • Test to make sure the hardware is functioning.
  • Verify that the reference for the device is the same in both the building computer and the deployment computer (for example that the device is not called dev1 in one computer and dev2 in the other one). This can be determined in the Measurement and Automation Explorer, under devices and interfaces.

WAS THIS ARTICLE HELPFUL?

Not Helpful