Scribd
Upload
217 views2 pages

LabVIEW Remote Debugging Cannot Find The Application - National Instruments

The document discusses troubleshooting issues with remotely debugging a LabVIEW executable from a development computer. It provides potential reasons why the remotely running executable may not be found, including having different LabVIEW versions, not running the NI Service Locator on the remote machine, or having a firewall block the required port. It recommends checking that the LabVIEW versions match, starting the NI Service Locator, and ensuring the debug port is open on the remote firewall.

Uploaded by

jun li
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
217 views2 pages

LabVIEW Remote Debugging Cannot Find The Application - National Instruments

The document discusses troubleshooting issues with remotely debugging a LabVIEW executable from a development computer. It provides potential reasons why the remotely running executable may not be found, including having different LabVIEW versions, not running the NI Service Locator on the remote machine, or having a firewall block the required port. It recommends checking that the LabVIEW versions match, starting the NI Service Locator, and ensuring the debug port is open on the remote firewall.

Uploaded by

jun li
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

LabVIEW Remote Debugging Cannot Find the Application

Updated Jan 6, 2021

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, 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. If the target computer has a newer version of LabVIEW Runtime Engine installed, the newer
version of the development environment will be required for remote debugging. To avoid this,
remove permission for future Runtime versions to run the executable during its build.
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.
4. 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.
5. 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.
Related Links
Remotely Debugging Executables in LabVIEW

What Is The NI Service Locator and How Do I Troubleshoot?

Other Support Options


Ask the NI Community
Collaborate with other users in our discussion forums
Search the NI Community for a solution

Request Support from an Engineer


A valid service agreement may be required, and support options vary by country.
Open a service request Purchase or renew support services

WAS THIS INFORMATION HELPFUL?

Helpful Not Helpful

 

You might also like