Solution
There are various reasons you would not be able to find a remotely running debuggable executable from your development computer. See them below:
1. 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 explained in the Solution section of the
NI Example Finder Does Not Open.
2. 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. You can verify this by going to
http://localhost:3580/dumpinfo?, the version is indicated in the URL column e.g.
National Instruments/LabVIEW/Built Application/23.1/RemoteDebug/Application.exe. means that Run-Time Engine version 23 is used.
If the versions of the runtime and the development environment do not match, it can be that
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 under these conditions. If this option was deactivated during the build process, the RTE version corresponding to the build environment will be used.
Note: the entry for the Remote Debuggable Program in the
http://localhost:3580/dumpinfo? URL will only be displayed when the executable is running.
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
Default range - Windows Documentation. The port use can be found in the Service Locator page and is the number behind
mapping=.
6. Make sure that you are running LabVIEW with Administrator rights.
7. Try pinging the computer using the Windows Command Prompt.