Network Management

Configuration Wizard fails with error Verifying that SWIS service is available FAILED

This article addresses an issue that causes the website configuration to fail in the Configuration Wizard. Verifying that the SWIS service is available FAILED Service configuration failed: Connection to SolarWinds Information Service did not succeed. Last error: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00.

First published date

11/23/2021 2:51 PM

Last published date

4/5/2022 5:41 AM

Overview

When you run the Configuration Wizard, the wizard fails with the following error:

Error Message:

Service configuration failed:
Connection to SolarWinds Information Service did not succeed.
Last error: The socket connection was aborted. This could be caused by an error 
processing your message or a receive timeout being exceeded by the remote host, or an 
underlying network resource issue. Local socket timeout was '00:01:00. 


Sample Image:
 

2.PNG

 

From the ConfigurationWizard.log (C:\ProgramData\SolarWinds\Logs\Orion), you will see the following error message:

2021-11-22 01:38:58,718 [9] ERROR SolarWinds.Common.Utility.ScheduledTask - (null)  
CheckEvaluationExpiration threw an exception.
System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoService
FaultContract]: RunQuery failed, check fault information.
The License Store is inaccessible. Restore connectivity to Main Poller. (Fault Detail is 
equal to InfoServiceFaultContract [ 
SolarWinds.Orion.Licensing.Client.CircuitBreakerException: The License Store is 
inaccessible. Restore connectivity to Main Poller. ---> 
System.ServiceModel.CommunicationException: The socket connection was aborted. This 
could be caused by an error processing your message or a receive timeout being exceeded 
by the remote host, or an underlying network resource issue. Local socket timeout was 
'00:01:00'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly 
closed by the remote host
   at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
   --- End of inner exception stack trace ---



 

Product section

Network Performance Monitor

Cause

TLS is not enabled.

Resolution

image.png
  • Run IIS Crypto on Orion Server.
image.png
  • Click Best Practices.
  • Check Reboot.
  • Click Apply.
  • After rebooting the Orion Server, run Configuration Wizard.