LabVIEW Remote Debugging Cannot Find the Application

Updated Nov 10, 2022

Reported In

Software

  • LabVIEW

Issue Details

I have built my executable to include debugging and I can debug it correctly when it is running on my development computer. However, when I try to debug the executable running on a remote machine or locally, I am not able to find any debuggable applications. I am able to ping the remote computer so I know the network is set up correctly. Why am I not able to connect to my remotely running debuggable executable?

When clicking on Operate >> Debug Application or Shared Library... a message similar to the one below is shown in the Connection Status panel: "No debuggable applications or runtime libraries found".
 
No debuggable applications.png

Solution

There are various reasons you would not be able to find a remotely running debuggable executable from your development computer.
  1. Make sure that the version of the LabVIEW Development Environment you are using for remote debugging is the same version as the Run-Time Engine (RTE) in which the deployed code is running. The used Run-Time Engine version is indicated in the URL column, e.g. National Instruments/LabVIEW/Built Application/22.0/RemoteDebug/Application.exe means that Run-Time Engine version 22 is used.
    Note: If the application was built with the option Allow future versions of the LabVIEW Runtime to run this application selected, the newest available bit-compatible version of the RTE will be used. If this option was deactivated during the build process, the RTE version corresponding to the build environment will be used.
  2. The NI Service Locator needs to be running on the remote computer to manage the dynamic port that the application will be using. Navigating to http://localhost:3580/dumpinfo? in a browser on the remote computer should show you the current status. If the browser returns “Page not Found”, the service locator may not be running. If this is the case, follow the instructions to start the NI Service Locator.
  3. Make sure the entire application folder is copied over to the remote computer.  When an application is built with debugging enabled, an INI file is created in this folder with a special line that enables the remote debugging server. This configuration (ini) file needs to be distributed with the shared library or application.
  4. The NI Service Locator requires that port 3580 is open for incoming communication. If you are using a firewall, you may need to ensure that this port is added as an exception.
  5. Make sure the executable running in the deployment machine is allowed to communicate through Windows® firewall. The application will dynamically choose a port from the Windows® default range. The port use can be found in the Service Locator page and is the number behind 'mapping='.