Re: Linked Server login problem with a Job
From: Andrew J. Kelly (ajkellynospam_at_attbi.com)
Date: 04/28/03
- Previous message: Steve Thompson: "Re: Auditing SQL Server"
- In reply to: Jen Skripac: "Linked Server login problem with a Job"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 28 Apr 2003 13:55:52 -0400
Have you tried dropping the linked server and recreating it?
-- Andrew J. Kelly SQL Server MVP "Jen Skripac" <jen526@aol.com> wrote in message news:vaqkgdk1g77q48@corp.supernews.com... > Any help with this would be appreciated. My client has two servers: Server A > runs SQL7 and Server B runs SQL2000. Both are Win2000 machines, and Server > B is defined as a Linked Server on Server A. > > I have a job on Server A that calls a stored procedure (also on Server A). > The stored proc then populate some data on Server B. > > This was working fine. Last week, the client started to upgrade the SQL7 db > to SQL2000, then aborted and rebuilt it back on SQL7 instead. Now, the job > fails with: "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'" > > The linked server SEEMS to be ok...if we log into Query Analyzer as "sa" and > run the procedures manually, it works fine. Other pertinent data: ServerA's > "sa" user is mapped to the remote "sa" login on Server B. Both have > authentication to "SQL Server and Windows" > > So, I'm guessing there's something wrong with the job definition, but I > can't figure what. The owner of the job is "sa" and the "Run as User" > setting for all steps is "(self)". I'm stumped as to why the "sa" user > would run fine via Query Analyzer, but not from a job? > > I'd be grateful for any suggestions. > > Jennifer Skripac > skripac@mainstreams.com > > > > > > >
- Previous message: Steve Thompson: "Re: Auditing SQL Server"
- In reply to: Jen Skripac: "Linked Server login problem with a Job"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
