Applications Systems

AppInsight for Exchange - WinRM unable to load assembly

Reference this article when WinRM unable to load assembly in AppInsight for Exchange.

First published date

10/15/2018 7:45 PM

Last published date

6/26/2020 4:50 AM

Overview

AppInsight for Exchange: WinRM unable to load assembly.

Product section

Server Application Monitor

Resolution

The following steps should be performed on the Exchange server to remove the reference to  the broken assembly:
 

  1.  Run the following PowerShell Command: 
    # Scripts are not supported under any SolarWinds support program or service.
    # Scripts are provided AS IS without warranty of any kind. SolarWinds further
    # disclaims all warranties including, without limitation, any implied warranties
    # of merchantability or of fitness for a particular purpose. The risk arising
    # out of the use or performance of the scripts and documentation stays with you.
    # In no event shall SolarWinds or anyone else involved in the creation,
    # production, or delivery of the scripts be liable for any damages whatsoever
    # (including, without limitation, damages for loss of business profits, business
    # interruption, loss of business information, or other pecuniary loss) arising
    # out of the use of or inability to use the scripts or documentation.
    
    get-childitem -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters

Working Server Output:

 

  • Microsoft.WSMan.Management\WSMan: localhost\Plugin\microsoft.powershell\InitializationParameters


ParamName                      ParamValue
---------                 ----------

PSVersion            3.0

 

Non-Working Server Output:

 

  • Microsoft.WSMan.Management\WSMan::localhost\Plugin\microsoft.powershell\InitializationParameters


ParamName                      ParamValue
---------                                 ----------
PSVersion                         3.0
assemblyname                   -
pssessionconfigurationtypename ShowSecurityDescr...

 

  1. The issue is with the "-" value so it must be removed.
  2. Run the following commands to remove the two extra InitializationParameters.
  • Remove-Item -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters\assemblyname
  • Remove-Item -Path wsman:\localhost\plugin\microsoft.powershell\InitializationParameters\pssessionconfigurationtypename
  1. Restart the server.