Remote Profile WCF running on IIS 7 accepting TCP Connections

I have a single IIS Web application with several WCF services running under IIS that I wish to profile due to intermittent performance issues. I have a website with is a client of the WCF services using TCP to communuicate with them.

Using DotTrace, I am able to setup the connection from my work PC to the remote client without problem. When attempting to run the profile, it appears to deploy / configure the remote agent, but at which point I can no longer 

1) I have the Remote Agent running on the server as an Administrator

2) using net.tcp:// address, i can establish a connection with the RemoteAgent from dotTrace installed PC

3) It appears to some installation / registration of software

4) Website can no longer communicate with the WCF on IIS host. Reports; "

No connection could be made because the target machine actively refused it XXX.XXX.XXX.XXX:808"

 5) Close the Remote Agent application and restarting the NET.TCP Listener service fixes the issue.

Really need to know a solution for this, as the Tool was bought specifically to monitor these WCF Services on our Release environment to diagnose some intermittent performance issues.

Any advice appreciated.

Cheers

Darcy

0
3 comments

Darcy,

 

I have answered you in the corresponding support ticket.

0
Avatar
Permanently deleted user

I face the same issue.  What was the answer in the support ticket?

0

Hi Wayne,

There are few possible causes of the problem:

  1. When you start profiling of IIS Server, dotTrace stops and then starts IIS service, so there could be some issues with slow start of the WCF services.
  2. dotTrace Remote Agent uses 9100 port by default, could you please check that this port is not used by some other application? Could you please change the port number and check if the issue persists? ("RemoteAgent.exe /nt=new_port_number")
  3. Also you can try to enable listening HTTP connections for Remote Agent, disable listening net.tcp connections and then connect to the agent via HTTP protocol: "RemoteAgent.exe /nt- /wh+". Full help for Remote Agent is available by "RemoteAgent.exe /?" command.
0

Please sign in to leave a comment.