Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Could not load type error in the VIM business layer log

Could not load type error in the VIM business layer log

Updated December 15, 2017

Overview

This article will provide solution for the issue where the Orion receives Events alerts for 'virtualization business layer failed to start. Please restart the module engine service'.

 

The issue causes Orion VIM to not be able to collect data on monitored vCenter nodes affecting the data collection for the Host and VM nodes under the vCenter nodes.

 

Below are the errors:

 

VIM business layer logs
=======================
2017-12-08 12:44:26,766 [Main] ERROR SolarWinds.Orion.Common.SWEventLogging - Unhandled Exception caught in Virtualization Service Engine startup. Could not load type 'SolarWinds.CloudMonitoring.Shared.CloudAccounts.CloudAccountDal' from assembly 'SolarWinds.CloudMonitoring.Shared, Version=1.0.1.4, Culture=neutral, PublicKeyToken=null'.

2017-12-08 12:44:26,766 [Main] FATAL SolarWinds.VIM.BusinessLayer.VirtualizationBusinessLayerPlugin - Unhandled Exception caught in plugin startup.
System.TypeLoadException: Could not load type 'SolarWinds.CloudMonitoring.Shared.CloudAccounts.CloudAccountDal' from assembly 'SolarWinds.CloudMonitoring.Shared, Version=1.0.1.4, Culture=neutral, PublicKeyToken=null'.
at SolarWinds.VIM.BusinessLayer.VirtualizationCloudMonitoringBusinessLayerServiceFactory.CreateCloudMonitoringBusinessLayerService()
at SolarWinds.VIM.BusinessLayer.VirtualizationBusinessLayerPlugin.Start()

Environment

  • Orion VIM/VMAN 8.1

Cause

VIM module service is unable to start due to the SolarWinds.CloudMonitoring.Shared.dll file that was not removed during the upgrade from Orion VIM 8.0 to version 8.1.

Resolution

Removing the SolarWinds.CloudMonitoring.Shared.dll file should fix the issue. Follow the steps below:

 

  1. Stop all Orion services.
  2. Delete the file SolarWinds.CloudMonitoring.Shared.dll on:
    C:\Program Files (x86)\SolarWinds\Orion\VIM\
  3. Start the Orion services.
  4. Verify that the event is gone on the Orion Events.
 

 

Last modified

Tags

Classifications

Public