Documentation.NET Profiler 4.5 HelpRunning applications with profilerLocal profiling troubleshooting

If the profiler cannot connect to a local application:

• Ensure that the application is started with the profiler and is running when you connect.

  If the application has started before you start the profiler and enable profiling, the profiler will not able to connect to the application, and the application should be restarted to profile it.

  If it didn't start or terminated by the moment, check the application's output, logs etc. for possible errors, or restart the application if it was intentionally shut down.

• If the application is up and running, ensure that the profiler agent port is not blocked by a firewall, an antivirus etc.

  The profiler agent port is not the same port as the ports which your profiled application normally uses, such as 8080 etc.

  The default profiler agent port range is 10001-10010. When an application starts with the profiler, the profiler first makes attempt to allocate a free port in this range. Profiled applications listening on ports in this range can be automatically detected when you connect.

  If all ports in the range are busy, an arbitrary port is chosen. In this case, you should explicitly specify the host and the port in the connect dialog as host:port You can find the port number in the profiler agent log file <user home directory>\.ynp\log\<PID>.log

• Due to some system settings such as security permissions, enabling profiling on the Welcome screen approach may not work for all .NET applications.

  In this case, the application will start, but no profiler agent log will be created (<user home directory>\.ynp\log\<PID>.log).

  As a workaround, try to enable profiling manually.

• If application to be profiled has started with the profiler, which is shown by the profiler agent log file which has been created (<user home directory>\.ynp\log\<PID>.log), but the Welcome screen does not show the application, please try "File | Connect to remote application...", specifying "localhost" as host name, and using the port which you should have seen in the profiler agent log.