I Can't Find My Debuggable Application While Remote Debugging

Updated Aug 14, 2018

Reported In

Software

  • LabVIEW Full
  • LabVIEW Base
  • LabVIEW Professional

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, 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?

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 LabVIEW  you are remote debugging from is the same version in which the application was developed. 
  2. 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.
  3. 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.
  4. The NI Service Locator requires that port 3580 be open for communication. If you are using a firewall, you may need to ensure that this port is added as an exception.

WAS THIS ARTICLE HELPFUL?

Not Helpful