DB_Newbie2007 (2/1/2013)

---

"Login failed for user 'NT AUTHORITY\SYSTEM'... "

DB_Newbie2007 (2/11/2013)

---

Nope. No proxies.

The job is actually run with a custom higher level account with full permissions in every database. Yes, it has full SA permissions... again, please no discussions on the use of an "SA" level account to run the job... focus on the particular issue at hand, thanks!

DB_Newbie2007 (2/11/2013)

---

Sorry for any confusion... I believe there are a few levels of "ownership" (http://www.sqlservercentral.com/articles/SQL+Jobs/68764/) per my understanding?

1) The account that is configured to run SQL Server Agent service.
2) The account that has "ownership" of the job (which is what I was referring to previously):
SELECT j.[name] AS 'JobName',
Enabled = CASE WHEN j.Enabled = 0 THEN 'No'
ELSE 'Yes'
END,
l.[name] AS 'OwnerName'
FROM MSDB.dbo.sysjobs j
INNER JOIN Master.dbo.syslogins l
ON j.owner_sid = l.sid
ORDER BY j.[name]
GO
3) The Step "run as" (i.e., proxy account).

The "job owner" (listed from the query above) is an account that is in the sysadmin fixed server role, so I believe the step should be executed under the account used by the SQL Server Agent service (NT AUTHORITY\SYSTEM in our case), as are all of the jobs on this server. We use a specific account for all of the "job owners".... we try to not do anything using the "sa" account (I could not tell you what the sa pwd is... it is locked away in a drawer).

The job step has the "run as" left blank (i.e., the "Proxy account").

Thanks!