This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Upgrade to 2020.2.5 failed with Container storage is not initialized on Additonal Web Server

Upgrade to 2020.2.5 failed with Container storage is not initialized on Additonal Web Server.

I went from 2020.2.4 to 2020.2.5, everything else worked, just the Additonal Web Server failed.

Re-ran it a couple of times, with a reboot before the last attempt, it fails with the message;

Services configuration failed:
• Connection to SolarWinds® Information Service did not succeed.
Last error: RunQuery failed, check fault information.
Container storage is not initialized. Reason: InvalidOperationException:Not yet initialized

Parents
  • I tried bumping SWIS timeouts with no success

  • This is what I got from support, Solution 2 worked for me

    Solution 1:

    1. Stop all the Solarwinds services.

    2. Browse to the Orion installation path. By default,
    C:\Program Files (x86)\SolarWinds\Orion\

    3. Make a copy of ConfigurationWizard.exe.config and save it on another location.(Outside of the Orion installation path).

    4. Edit the file ConfigurationWizard.exe.config in notepad.
     

    1. Look for <add key="SWISMaxWaitingTime" value="00:01:30"/> 
         Change its value to 3 minutes: <add key="SWISMaxWaitingTime" value="00:03:00"/> 
       
    2. Save the config file and re-run the Configuration wizard.


    Solution 2.

    1. Follow same steps 1 to 4 from Solution 1.

    2. Edit SWIS container query retry wait and retries, e.g.
    <add key="SWISContainerQueryRetryWait" value="00:00:20"/>
    <add key="SWISContainerQueryRetries" value="10"/>
    <add key="SWISContainerQueryTimeout" value="00:00:20"/>


    Also, make sure SWIS maximum waiting time still stays at
    <add key="SWISMaxWaitingTime" value="00:03:00"/>
     

    3. Save the config file and re-run the Configuration wizard.

  • Jonathan, just wanted you to know that worked.

    I had changed the Container timeout values to 3 minutes, and was unsuccessful.
    Setting the values exactly as you listed worked like a charm.

Reply Children
No Data