Here's a two-liner that aborts when I run it as a SQL Agent job in SSMS:
Here's the info from the job history:
A job step received an error at line 2 in a PowerShell script.
I've found that if the account used to run the job has admin-level privileges, as is well, but when I remove the account from the admin group, I get the abort.
Might anyone know off-hand the minimum privileges needed to execute sqlps jobs that use the SQLSERVER provider?
I've found that SQL Agents jobs need to be run with a high level of privilege for PowerShell steps to work. I think you'll probably need to stick with admin level rights
You must be logged in to reply to this topic.