Some network issues require an administrator to turn on WCF tracing in order to figure out what issue is occurring. The steps are as follows:
- First read this KB article to Find the installation location of Intelligence Agent.
- Edit the Hubstream.Intelligence.Agent.exe.config file in Notepad
- Scroll down to the system.diagnostics section, and remove the <!-- and --> comments from the source element as follows:
<sources> <source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"> <listeners> <add name="traceListener" type="System.Diagnostics.XmlWriterTraceListener" initializeData="c:\temp\TracesClienthttps.svclog" /> </listeners> </source> </sources> </system.diagnostics>
- Note the highlight path above, this is where the WCF trace files will be created
- Exit Agent (Actions/Exit) and restart
- Repeat the process that is failing, for example choosing Download
- Exit Agent
After completing the above steps, send the resulting file to Hubstream support for further analysis.
Alternatively, the file can be used for local troubleshooting using Microsoft's Service Trace Viewer tool (SvcTraceViewer.exe) which is part of the Windows SDK. Gateway error messages are often the root cause of issues, for example where a local proxy/gateway is blocking certain types of traffic.