Question

A SQL Server Agent job that runs a PowerShell step to export data to a network share completes successfully when you manually start it from SSMS while logged in as a domain administrator. However, when the job runs on its schedule, the step fails with an 'access is denied' error writing to the share. The job step is configured to run under the SQL Server Agent Service Account. What is the most likely cause and appropriate fix?

Accepted Answer

The SQL Server Agent service account lacks write permission to the network share; configure the step to run under a proxy account mapped to a credential with the required share access.

Answer

The job schedule is disabled; re-enable the schedule and set it to run under the current interactive user context.

Answer

The PowerShell subsystem is not installed; reinstall SQL Server Agent to add the PowerShell subsystem.

Answer

The job history log is full; purge the msdb job history so the step can write its output.