Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > Powershell scripts stop working after upgrading to .Net 4.0

Powershell scripts stop working after upgrading to .Net 4.0

Overview

Powershell scripts stop working after upgrading to .Net 4.0.

Environment

All SAM versions

Cause

This issue can be fixed by adding legacy .Net compatibility into the configuration file of the SAM/APM module/application that launches Powershell monitors.

 

Note: This is a known issue and will be addressed in a future release.

Resolution

If possible, upgrade to SAM 5.2 or higher. If this is not possible, follow the steps below by updating the highlighted content from the Original File Content example to the Fixed File Content example:

 

Apply the change inside the Job Engine worker’s configuration files :
“c:\Program Files (x86)\Common Files\SolarWinds\JobEngine.v2\SWJobEngineWorker2.exe.config” and
“c:\Program Files (x86)\Common Files\SolarWinds\JobEngine.v2\SWJobEngineWorker2x64.exe.config”

Original file content:

 

code2.png

 

Last modified

Tags

Classifications

Public