In reply to Keith Johnson.

A combination of the execution policy and the mapped drive (network location) of the script might be a factor, as PowerShell might want some elevated levels of trust for this. If you can, you might try to remove SAS from the equation and try running the script from another process (like VBS or a batch file) and see what it takes to make it work. The Set_Execution-Policy Bypass would need to be run as an Admin and apply to the Machine level (I think) to affect future invocations like this.