Powershell scripts stop working after upgrading to .Net 4.0
Issue: Powershell scripts stop working after upgrading to .Net 4.0
Note: This is a known issue and will be addressed in a future release.
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.
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:
No related articles were found.
No attachments were found.
No visitor comments posted. Post a comment
Post Comment for "Powershell scripts stop working after upgrading to .Net 4.0"
If this article does not provide the solution you need, please consider visiting our community forums on thwack or contacting SolarWinds Support. Please use the following form to provide comments that help us improve this KB article. Fields marked with an asterisk are required.