SETUSER in SQLMail is causing a problem I can't fix !!
From: Steve (Spt@Airnet.co.uk)
Date: 02/18/03
- Next message: Tom: "Re: logon failed"
- Previous message: Sue Hoegemeier: "Re: Deny administrator"
- Next in thread: Gert E.R. Drapers: "Re: SETUSER in SQLMail is causing a problem I can't fix !!"
- Reply: Gert E.R. Drapers: "Re: SETUSER in SQLMail is causing a problem I can't fix !!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Steve" <Spt@Airnet.co.uk> Date: Tue, 18 Feb 2003 05:58:14 -0800
SETUSER in SQLMail is causing a problem I can't fix !!
Since installing SQL 2000 SP3 (Ent.Ed), I am having a
problem with the user account for SQL Mail Queries not
being allowed to communicate with Remote/Linked Servers
with "OPENQUERY" over ODBC.
ERORR : ODBC error 7410 (42000) Remote access not allowed
for Windows NT user activated by SETUSER.
I've read Microsoft Knowledge Base Article - 811031 and
method 1 & 2 are already actioned.
However, the error still occurs when running a Query
outside of the Agent Job/Procedure Call so I now assume
it's SQLMail related.
We do not SQL Mail on our clusterd SQL systems.
We use a single SQL2000 SP3 Server and SQLMail, and
generate Notifications using data from several SQL2000
Clusters (also on SP3).
The data for SQL Mails are generated from Agent Jobs and
Stored Procedures, using "OPENQUERY"
or "Server.DB.dbo.StoredProc"
to communicate with the clustered databases.
Steve ...
- Next message: Tom: "Re: logon failed"
- Previous message: Sue Hoegemeier: "Re: Deny administrator"
- Next in thread: Gert E.R. Drapers: "Re: SETUSER in SQLMail is causing a problem I can't fix !!"
- Reply: Gert E.R. Drapers: "Re: SETUSER in SQLMail is causing a problem I can't fix !!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]