Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Virtualization Manager (VMAN) > SolarWinds Virtualization Manager 7.1 HotFix 2

SolarWinds Virtualization Manager 7.1 HotFix 2

 

Updated: September 8, 2017

Fixed issues

This hotfix addresses the following issues:

  • Test connection fails for a previously added cloud account (AWS IAM account)
    • Clicking on Test Connection on the AWS account edit page fails with the error "Credential Test Failed".
    • There is also an error message in CloudMonitoring.Jobs.log similar to the following:
      SolarWinds.CloudMonitoring.Jobs.TestAwsConnection - Credential test for region 'us-east-1' failed with code Unauthorized and message: AWS was not able to validate the provided access credentials
    • You may receive this error after installing VIM 7.1.
  • Polling of Hyper-V via Agent does not work
    • Polling of Hyper-V servers using Agent fails with the following error:
      SolarWinds.JobEngine.WorkerProcess.JobExecutionException: System.IO.FileNotFoundException: Could not load file or assembly 'SolarWinds.CloudMonitoring.Shared, Version=1.0.0.134, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
    • You may receive this error after installing VIM 7.1.
  • Terminated AWS instances are not removed from the Cloud Summary resource
    • AWS instances that no longer exist in Amazon cloud are still visible on Cloud Summary resource and have a status of "Unknown".
    • You may receive this error after installing VIM 7.1.
  • "Out of memory" errors in VIM BusinessLayer
    • The VIM BusinessLayer crashes because it runs out of available memory.
    • You may receive this error after installing VIM 7.1.

Environment

  • VIM 7.1

Notes

  • This hotfix requires SolarWinds Orion Core 2017.1 MSP2 or newer and VIM 7.1.
  • This hotfix must be installed on the main poller, and on any additional pollers.
  • This hotfix addresses the described issues for VIM 7.1.
  • After installation, "SolarWinds Orion Module Engine" service must be restarted to enforce reconnection of all agents. The agents will then receive the updated plugin.
  • This hotfix is cumulative and replaces VIM 7.1 Hotfix 1.

Installation instructions

Install this standalone hotfix on the main poller, on any additional pollers, and on web servers.

  1. Log in to the server hosting your SolarWinds Orion installation as an administrator.  
  2. Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
  3. Run the standalone hotfix SolarWinds-VIM-v7.1-Hotfix2.exe, and follow the instructions in the installation wizard.

After applying the hotfix, the issues outlined above do not occur.

Install the hotfix with SolarWinds HA

Use these instructions to install the hotfix with SolarWinds HA. 

Important: The HA pool must be disabled to begin installation. If you install prior to disabling, the pool is automatically disabled.

  1. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  2. Select the pool you want to disable.
  3. Toggle High Availability to Off.
  4. Install the hotfix/buddy drop on the primary server in the pool.
  5. Install the hotfix/buddy drop on the secondary server in the pool.
  6. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  7. Select the pool you want to enable and toggle High Availability to On.

The Orion Web Console verifies all SolarWinds product versions match across the HA pair before enabling. If you receive errors, check your product versions.
You may need to recreate the HA pool. For details, see Set up an HA pool.

Uninstall the hotfix 

  1. Log in to the server hosting your SolarWinds Orion installation as an administrator.
  2. Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
  3. Navigate to Control Panel > Programs > Programs and Features > View installed updates.
  4. Select "Update for Virtual Infrastructure Monitor v7.1.0 (Hotfix2)", click Uninstall, and complete the uninstallation wizard.

 

For more information, contact Technical Support at https://support.solarwinds.com/Succe...g_With_Support

Last modified

Tags

Classifications

Public