Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > 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