Friday, February 24, 2012

Error trying to execute a sp on a remote server with an SQL agent

Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated by
SETUSER. [SQLSTATE 42000]
I get the above error when I try to execute a sp sitting on a remote server
with a SQL Server Agent job.
The sp executes fine if I run it from Query analyser.
Maybe the problem lies with how my linked server is set up, or why does it
try to connect to the remote server with NT security and using SQL
authentication?
Can I force it to connect with SQL Authentication ?
Rgds,
NicoNico,
Possibly 811031 PRB: SQL Server Agent Job Fails When the Job Uses a Linked
Server and
http://support.microsoft.com/?id=811031
John Gose
MCDBA
Microsoft SQL Server Support
This posting is provided "AS IS", with no warranties, and confers no rights
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
| Thread-Topic: Error trying to execute a sp on a remote server with an SQL
agent
| thread-index: AcSxAO/Fym/0adp3SrSXr6fzDw/fvQ==
| X-WBNR-Posting-Host: 168.210.90.181
| From: "examnotes" <Nico@.discussions.microsoft.com>
| Subject: Error trying to execute a sp on a remote server with an SQL agent
| Date: Wed, 13 Oct 2004 01:45:05 -0700
| Lines: 15
|
<Snip of Header Stuff>
|
| Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
| Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated
by
| SETUSER. [SQLSTATE 42000]
|
| I get the above error when I try to execute a sp sitting on a remote
server
| with a SQL Server Agent job.
| The sp executes fine if I run it from Query analyser.
|
| Maybe the problem lies with how my linked server is set up, or why does
it
| try to connect to the remote server with NT security and using SQL
| authentication?
| Can I force it to connect with SQL Authentication ?
|
| Rgds,
| Nico
|

No comments:

Post a Comment