To localize the problem, we need to find out whether the problem is with the profiled application itself (agent is actually "not listening" for some reason) or with the remote connection to the agent port.
Please try opening the URL <the remote host>:10001 in a web browser on your local machine where you run the profiler UI. If there is a remote connection to the agent port, it is expected to see a page with text "Invalid magic number" among some unprintable characters (the agent uses a binary protocol). Is it what you see?
.Net core profile activation "not an attachable process"
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am