Re: Linked Server Confusion - I don't know where to start...
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Thu, 13 Apr 2006 21:30:02 -0600
If you can execute the stored procedure manually but it
fails when run as a job, it's often an issue in the area of
security context differences. The job is run under the
security context of the Agent service, manually it's running
under the context of your login. You may also want to check
the properties of the DSN. In the ODBC Data Source
Administrator, select the DSN and the click configure. Click
the client configuration button on the second screen. Make
sure the protocol is set to TCP/IP. In the Linked Server
security settings, I'd also try explicitly mapping the Agent
service account to the login you want to use.
-Sue
On 13 Apr 2006 08:23:39 -0700, "Datamover"
<datamovr@xxxxxxxxx> wrote:
One thing I forgot to mention, the job fails at exactly the point in
the stored procedure where it tries to insert a row into a linked
server table. This is the only line in the code that connects to the
linked server. The error I'm getting is certainly related to the
linked server.
.
- Follow-Ups:
- Re: Linked Server Confusion - I don't know where to start...
- From: Datamover
- Re: Linked Server Confusion - I don't know where to start...
- References:
- Linked Server Confusion - I don't know where to start...
- From: Datamover
- Re: Linked Server Confusion - I don't know where to start...
- From: Sue Hoegemeier
- Re: Linked Server Confusion - I don't know where to start...
- From: Datamover
- Re: Linked Server Confusion - I don't know where to start...
- From: Datamover
- Linked Server Confusion - I don't know where to start...
- Prev by Date: Re: Encryption in SQL Server 2005
- Next by Date: Re: Logon failed for user ". but only for membership tables in same database that other request work
- Previous by thread: Re: Linked Server Confusion - I don't know where to start...
- Next by thread: Re: Linked Server Confusion - I don't know where to start...
- Index(es):