unable to execute commands using Powershell Script from PAM
search cancel

unable to execute commands using Powershell Script from PAM


Article ID: 217745


Updated On:


CA Process Automation Base


When trying to execute a PAM process that involves a Script Operator for a Powershell script the instance hangs until timeout.

The same code is working from PowerShell Explorer on the Server, but not from PAM Process.


Release : 4.3

Component : Process Automation


This was caused by the Powershell Execution policy not being set appropriately on the server. The default execution policy of PowerShell on Windows is Restricted, and needs to be changed (either during the installation of the Orchestrator/Agent running the script) or afterwards.


If the issue remains, implement the following KB article in the Orchestrator server and agents:

PAM server not triggering Powershell script within a workflow process