Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

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
21:34, 30 Nov 2016

Tags

Classifications

Public