Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Integration between VMAN and the Orion server stops working after upgrading to version 6.2 and 6.3

Integration between VMAN and the Orion server stops working after upgrading to version 6.2 and 6.3

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,484 Votes: 1 Revisions: 13

Overview

The integration between Virtualization Manager and the Orion server stops working after Virtualization Manager is upgraded to 6.2.0 and 6.3. 

Environment

  • All NPM versions
  • All VMAN versions

Cause

The issue is caused by an incompatibility between the certificates used by Virtualization Manager and by Orion NPM 10.1.

Resolution:

Download the fix from the following location, and install the SolarWinds.FixIt.Md5 application:
http://downloads.solarwinds.com/solarwinds/Release/PreRelease15/Beta/SolarWinds.FixIt.Md5.1.0.0.7-Beta1.zip 

During the installation of the attached fix you may see an issue that the CertUtility.exe cannot stop a certain service. In this case, an old entry may still exist in the registry.

To solve this issue, delete the old entry from the registry.

Warning: SolarWinds strongly recommends that you only make registry changes per our instructions. Follow the instructions exactly and make the required changes in all registry locations specified. Failure to follow these instructions can introduce errors into the application or, in some situations, cause operating system issues.

  1. Before editing the registry, create a snapshot if you work with a virtual machine, or create a restore point using System Restore. The restore point contains information about the registry, and you can use the restore point to undo changes to your system.
  2. Create a backup of the specific registry key:
    1. Locate the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds.Net\ConfigurationWizard\ServicesName
    2. Click the name of this registry key, select File > Export, and then select Desktop from the Save in list.
    3. Use the registry key name as the title, and then click Save.
  3. Under the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds.Net\ConfigurationWizard\ServicesName registry key, select the Service that could not be stopped by CertUtility.exe.
  4. Click Start > Run, type services.msc, and then click OK.
  5. In the Services list, verify that the service you located in the registry no longer exists.
  6. Right-click the service name in the registry editor, and then click Delete.
  7. Run the CertUtility.exe again according to the instructions contained in the package.

After applying these steps, CertUtility.exe should run without issues and should be able to stop the necessary services.

Last modified

Tags

Classifications

Public