Failed to execute HTTP request

4ahmadali

Dear Valued Community,

We stopped receiving SMS alerts, which are configured using "Send a GET or POST request to a web server". I tried to simulate the action and I am getting "Failed to execute HTTP request" error. In the Alerting.Service.V2 log files I am getting bellow errors.

2018-07-23 09:49:11,879 [78] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - Error closing exception.

System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

2018-07-23 09:51:39,683 [AlertingService.OnStart] WARN  SolarWinds.Orion.Core.Common.InformationServiceConnectionProvider - Connection via certificate could not be created.

System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:17777/SolarWinds/InformationService/v3/Orion/certificate. The connection attempt lasted for a time span of 00:00:02.0468738. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:17777.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:17777

Please inform what is the underlying issue causing this problem.

Kind Thanks

dan_jagnow

If you have Web Companion by Lavasoft installed (possibly from installing FileZilla), then this support article may apply to your situation:

Website will not load: Orion module engine unable to talk to swis v2 after installing Web Companion by Lavasoft - SolarW…

There is also some useful information about testing connections to the SolarWinds Information Service (SWIS) on this thread:

Solarwinds Information Service - Enable for External API Access

In particular, note the comment about running the netstat command to verify that SWIS is listening on port 17777 on the server.  The "No connection could be made because the target machine actively refused" message typically means that no service is listening on that port (which you can verify with netstat) or that some firewall is blocking access to that port.  See .net - No connection could be made because the target machine actively refused it? - Stack Overflow for more details.