This can be caused by several things :
- Lack of SQL permissions (unless Orchestrator service account has sysadm permissions on SQL).
- Orchestrator service account does not have “Logon as a batch job” permissions
- Application Pool not using Orchestrator service account