A Collector is reporting as faulty in the Blueprint Administrator. The Test Results indicate the following error:
"The WCF HTTP Server Communication test failed. The request channel timed out attempting to send after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."
- Blueprint Administrator reports one or more Collectors as faulty with WCF communication errors.
- Blueprint Collector passes self checks when using the Blueprint Server Configuration utility but shortly afterward generates a popup error stating that health status reporting to the Analyst has failed.
Microsoft.NET - the managed code library around which much of the Blueprint software is developed - is attempting proxy communication using Web Proxy Autodiscovery Protocol (WPAD). This behavior causes the Blueprint services (namely, the Pharos Systems Taskmaster service) to also attempt communication via WPAD, resulting in a timeout. WCF HTTP communication subsequently fails.
Edit the failing Analyst's and / or Collector's .NET library machine.config file to explicitly disable automatic proxy discovery.
The machine.config file can be found within the
Add the following text within the <Configuration> section.
<!-- Disable Autoproxy-->
An edited machine.config file can be found below as a reference.
Make sure to retain a copy of the original machine.config file as a backup.
After making the edit and saving the file, the Pharos services will need to be restarted. Use the Blueprint Server Configuration utility to test functionality on the Collector. Likewise, open the Blueprint Administrator on the Analyst, select the previously failing Collector and click the Update Status button to retest connectivity.