Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Error when adding Cloud AWS monitoring: Could not load file or assembly AWSSDK.Core

Error when adding Cloud AWS monitoring: Could not load file or assembly AWSSDK.Core

Updated Jan 23, 2018

Overview

When you are trying to add AWS monitoring from Orion Web Console or Manage Cloud Accounts, you receive the error below. Test of AWS credentials passes without any issue.

 

SolarWinds.JobEngine.WorkerProcess.JobExecutionException: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'AWSSDK.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=885c28607f98e604' or one of its dependencies. The system cannot find the file specified.
at SolarWinds.VIM.CloudMonitoring.Aws.AmazonEc2ClientFactory..ctor()
at SolarWinds.VIM.CloudMonitoring.Jobs.Aws.AwsGetVirtualMachinesOneTimeJob..ctor()

Environment

  • Orion Core
  • Cloud Monitoring / VIM

Cause

This is a known issue in Core Platform versions 2018.1 and earlier.

Resolution

Work around:

1. Create snapshot of machine with Orion

2. From the [OrionInstallationFolder]/CloudMonitoring (Default path C:\Program Files (x86)\SolarWinds\Orion\CloudMonitoringfolder) copy (not move) following files to [OrionInstallationFolder]/VIMCloudMonitoring

    AWSSDK.Core.dll
    AWSSDK.EC2.dll

3. Restart all services, verify if it solve the issue or no
4. If no, please copy all remaining  files from [OrionInstallationFolder]/CloudMonitoring to [OrionInstallationFolre]/VIMCloudMonitoring
5. Restart all services, verify if it solves the issue or no
6. If the issue is not resolved, please grab fresh diagnostics and send to support

 

Upgrade the Orion Platform to 2018.2 or later and if you are still getting same error then upload fresh logs to Solarwinds Support

 
Last modified

Tags

Classifications

Public