Network Management

Configuration Wizard fails with error Verifying that SWIS container storage is available FAILED in the SolarWinds Platform

This article addresses an issue that causes the website configuration to fail in the Configuration Wizard with Connection to Solarwinds Information Service did not succeed. Last error: RunQuery failed, check fault information. EntityTypeResolver is not initialized

First published date

10/31/2019 7:36 AM

Last published date

2/21/2025 11:16 PM

Overview

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

Verifying that the SWIS container storage is available FAILED
Service configuration failed:

Connection to Solarwinds Information Service did not succeed. 
Last error: RunQuery failed, check fault information.
EntityTypeResolver is not initialized


Sample Image:

image.png

This can also be encountered while running an upgrade via Centralized Deployment:
image.png

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

ERROR ServiceHelper - Maximal waiting time for SWIS v2.0 was exceeded. Rethrowing the original exception.
ERROR TaskAdapter - Error running task Orion.EnsureSwisIsAvailable Verifying that the SWIS service is available
SolarWinds.ConfigurationWizard.Common.ConfigurationException: Connection to SolarWinds Information Service did not succeed.

OR 
Error 2:

ERROR TaskAdapter - Error running task Orion.EnsureSwisContainerStorageIsAvailable Verifying that the SWIS container storage is available
SolarWinds.ConfigurationWizard.Common.ConfigurationException: Connection to SolarWinds Information Service did not succeed.
Last error: RunQuery failed, check fault information.
EntityTypeResolver is not initialized ---> System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: 
RunQuery failed, check fault information.EntityTypeResolver is not initialized

OR
Error 3:

2021-12-25 01:59:30,236 [16] ERROR SubscriptionManager - An error occurred while creating the subscription 'NotificationMonitor.pdmc/mkQTKTXphEWsTriqM+R2RE=.Engine'.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://cossworion:17777/SolarWinds/InformationService/v3/Orion/Streamed/certificate that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Exception rethrown at [0]: 
   at SolarWinds.Orion.Core.Common.ChannelProxy`1.HandleException(Exception ex, Int32 currentRetryCount, ChannelProxyBehavior behavior, String methodName)

 

Product section

Orion Platform

Cause

SWISv2 taking so long to load.
  1. Broken pub/sub
  2. SWIS is broken completely

Resolution

Solution For Error 3:

1. Stop All SolarWinds Services on all server (excluding dependencies)
2. Clear Information Service Subscriptions - please contact us to work with support on this process
3. Re-run the SolarWinds Configuration Wizard


Solution 1 Error 1 & 2:

  1. Stop all of the SolarWinds services using SolarWinds Platform Service Manager.
  2. Browse to the SolarWinds Platform installation path, [drive:\Program Files (x86)\SolarWinds\Orion]
  3. Make a copy of the ConfigurationWizard.exe.config file and save it to another location. (Outside of the SolarWinds Platform installation path).
  4. Open Notepad as Administrator and edit the ConfigurationWizard.exe.config file.
  5.  Look for <add key="SWISMaxWaitingTime" value="00:01:30"/> and change the value to 3 minutes. 
 <add key="SWISMaxWaitingTime" value="00:03:00"/> 
  1. Save the ConfigurationWizard.exe.config file and run the Configuration Wizard.


Solution 1 Error 1 & 2:

  1. Follow the same steps 1 to 4 from Solution 1.
  2. Edit SWIS ContainerQuery line on the file,
<add key="SWISContainerQueryRetryWait" value="00:00:20"/>
<add key="SWISContainerQueryRetries" value="10"/>
<add key="SWISContainerQueryTimeout" value="00:00:20"/>

Also, make sure SWISMaximumWaitingTime still stays at 3 minutes.

<add key="SWISMaxWaitingTime" value="00:03:00"/>
  1. Save the ConfigurationWizard.exe.config file and run the Configuration Wizard.

 

Solution 3:

  1. Reboot the SolarWinds Server.
  2. Stop all the SolarWinds services via SolarWinds Platform Service Manager.
  3. Repair SolarWinds Platform via Control Panel.
  4. Run the Configuration Wizard.

 

Solution 4:

  1. Reboot the SolarWinds server.
  2. Stop all the SolarWinds Services.
  3. Uninstall and reinstall the SolarWinds Information Service.
  4. Run the Configuration Wizard.

Solution 5:

  1. Disable AV/Windows firewall

Solution 6:

  1. Run a repair on the SolarWinds Platform via the Control Panel.
  2. Complete the Configuration Wizard.
  3. Check Web Console Connectivity.