Execution Trace Will not work on an installed Remote Application

[TEST_GF]

I have followed every tutorial available and I cannot run execution trace on a remote application.

- I have tried Builds with different Port numbers from the default, as well as the default 3363. 

- I have verified that I am able to run the application remotely through my desktop with the debugger to prove that connection to the remote machine is possible.

- I close the source project on the machine where the app was created when preparing to use the Execution Trace Toolkit.

I have verified that I can run the Trace tool on the application when I execute the app on my own machine without issues. 

Source code machine is Win7 and the Target machine is XP.    Does this create any known issues?

Does the status of NI Max on either machine matter?  Is there something in NI max that requires setup?

The issue I am seeing is simply that it cannot see the target machine in the New Trace Connection Dialog box.

I am building the app in LV2011. 

[Joshua-B]

Hello TEST_GF,

Below is a link to an article that describes how to configure both the stand-alone application and Desktop Trace Execution Toolkit to debug stand-alone applications remotely.  If you haven't seen this before, I highly recommend following it step by step.  Please take notice of the note between the two sections of the article as well.  I hope this helps!

Debugging LabVIEW Stand-Alone Applications and Shared Library Files

http://zone.ni.com/reference/en-XX/help/372641A-01/lvdetthelp/debug_built_apps/ 

[TEST_GF]

I had seen that page before and I have performed all of those steps in the link you provided numerous times, to the letter.  Still no luck.

[Joshua-B]

Hello TEST_GF,

Are you using the machine name or the IP address when you are configuring VI Server in the project you are building into an executable?  Also, do you have any anti-virus software that you could turn off in case it is interfering with any of the ports you are trying to use?