SQL Server Agent job fails when the job uses a linked server and the job owner is not a system administrator
This article has been archived. It is offered "as is" and will no longer be updated.
When you run a SQL Server Agent job that uses a linked server and the owner of the job is not a system administrator account, the job may fail and SQL Server displays the following error message:
Remote access not allowed for Windows NT user activated by SETUSER. [SQLSTATE 42000] (Error 7410). The step failed.
When you run a SQL Server Agent job that is not owned by a system administrator account, SQL Server Agent runs SETUSER to impersonate the owner of the job.
If the job uses linked servers, the job may fail because remote access is not allowed after the execution of SETUSER.
To work around this problem, use one of the following methods:
Make the system administrator the owner of the job.
Use mapped security context for the linked server and modify the job to run as OSQL.
To set the mapped security context for the linked server:
- Right-click the linked server, and then click Properties.
- Click the Security tab.
- Select either of the following options.
- Be made using the login's current security context
- Be made using this security context
To modify the job to run as OSQL:
- Right-click the job, and then click Properties.
- In the Steps tab, click the Step Name that you want to edit, and then click Edit.
- On the General tab of the Edit Job Step dialog box, click Operating System Command (CmdExec) in the Type list.
- In the Command text box, type osql –E –Q “Exec storeProc”.
- In the Edit Job Step dialog box, click OK.
- In the Properties dialog box, click OK.
This behavior is by design.
For more information, visit the following Microsoft Web site:
Article ID: 811031 - Last Review: 12/08/2015 01:44:50 - Revision: 4.5
Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 7.0 Standard Edition
- kbnosurvey kbarchive kberrmsg kbprb KB811031