Unrecognized FaultException when Connecting to RemoteAgent

How can I troubleshoot the following error message in the dotTrace Profiler Configuration dialog?

Unrecognized FaultException: code Receiver, prefix Server was 
unable to process request. ---> Unable to open f

I have a RemoteAgent configured and running on a server, firewall port 9000 open.
Attempting to connect to it, I specify the IP address, port, and endpoint and I get the message above. That is it...it ends with the letter "f" and I'm not sure what it is referring to. I checked the logs, unfortunately, this is all I'm getting:

12:51:09 PM.060: Thread:1: [ConfigRemove] #13 HostParameters:
<?xml version="1.0" encoding="utf-8"?>
<HostParameters type="RemoteHostParameters">
    <Domain IsNull="False">
    </Domain>
    <Password IsNull="False">
    </Password>
    <Url>http://192.168.1.177:9000/RemoteAgent/AgentService.asmx</Url>
    <UserName IsNull="False">
    </UserName>
</HostParameters>
12:51:09 PM.060: Thread:1: [ConfigRemove] #13 Make selection empty
12:51:09 PM.590: Thread:1: [ConfigActivate] #14 HostParameters:
<?xml version="1.0" encoding="utf-8"?>
<HostParameters type="RemoteHostParameters">
    <Domain IsNull="False">
    </Domain>
    <Password IsNull="False">
    </Password>
    <Url>http://192.168.1.177:9000/RemoteAgent/AgentService.asmx</Url>
    <UserName IsNull="False">
    </UserName>
</HostParameters>
12:51:09 PM.590: Thread:1: [ConfigActivate] #14 Set selection
12:51:09 PM.876: Thread:1: [ConfigActivate] #14 Start processing
12:51:09 PM.877: Thread:40: [ConfigActivate] #14 Connecting
12:51:09 PM.880: Thread:40: Local SysTools v5.5.4.160 loaded
12:51:10 PM.674: Thread:40: [ConfigActivate] #14 Failed
12:51:10 PM.674: Thread:40: [ConfigActivate] #14 Stored
12:51:10 PM.674: Thread:40: [ConfigActivate] #14 Set selection

There doesn't seem to be any information on the server either. All I see in the event log is the following, which is logged on startup of RemoteAgent but makes sense as it likely doesn't want itself to be profiled:

The profiler has requested that the CLR instance not load 
the profiler into this process.

There are no other log files or artifacts that I can find.
Other info:

  • I'm on Windows 8.1
  • dotTrace version is 5.5.4
  • Server is 2012
  • All apps run with admin privileges

I have been able to connect to other RemoteAgents on other servers. Don't know what the missing piece is here.

5 comments

James,

There are also RemoteAgent logs, located in the %TEMP%\JetLogs folder on remote machine. They could be more helpful.

From what I can guess so far, it is likely failed to access the binaries cache directory, located at %ProgramData%\JetBrains\Profiler\RemoteAgent\SysToolsCache.

Could you, please, check log files and the cache path above.

0

Thanks Ilya,

The %TEMP%\JetLogs logfile seems to just have the startup output from the console, but thanks for the location.  Just a thought...perhaps pump that path out to the console on startup?

As far as the cache is concerned, it seems to be able to access that path on the server as well (permissions support it and the correct version is in that folder).

Side note, I can access the webservice from a browser, so I know I'm making a connection. Running Fiddler, there is a series of about 5 exchanges, ending in a 500 with the following error:
  Server was unable to process request. ---&gt; Exception has been thrown by the target of an invocation. ---&gt; Could not load file or assembly 'file:///C:\ProgramData\JetBrains\Profiler\RemoteAgent\SysToolsCache\5.5.4.160\JetBrains.Profiler.dotTrace.Agent.SysTools.dll' or one of its dependencies. The system cannot find the file specified.

The log files have this appended on the server:
8:46:12 AM.328: Thread:6: Remote Agent WebService loaded, auth required = False
8:46:14 AM.465: Thread:6: Loading SysTools v5.5.4.160 into new AppDomain

...and nothing further.

So, it seems your hunch on the cache access is correct, but I'm not sure how to address it. The 5.5.4.160 folder is there. Interestingly, systools.dll is not there (though systools.base and systools.core are there). I can't find this binary in any of my install paths either, but I'm not sure if that's a red herring or what.

Any ideas?

Cheers,
-James

0

Okay, an update here.

The cache dir pointed me in the right direction. I took a closer look at the RemoteAgent as it was starting up, and it turns out that it was on version 5.3.1 (not 5.5.4). I cleared the cache directories, copied the current version of the RemoteAgent to the target server and was able to connect.

Thanks again Ilya.

Best,
-jc

0

Ok, glad that you resolved it. And thanks for pointing out to the problem - we shall at least think how to make it easier to recognize.

0

Let me do a pull request and I'd be happy to help. ;)

0

Please sign in to leave a comment.