Re: SETUSER in SQLMail is causing a problem I can't fix !!

From: Gert E.R. Drapers (GertD@SQLDev.Net)
Date: 02/19/03 

From: "Gert E.R. Drapers" <GertD@SQLDev.Net>
Date: Tue, 18 Feb 2003 19:13:19 -0800

This is expected behavior, when an XP is impersonating the connection using
srv_impersonate_client, this is equivalent to a manual setuser call.
And as you found out calling setuser and performing an OpenQuery do not
together, because you can not set the security credentials of a Windows NT
user, without having a password.

GertD@SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.

"Steve" <Spt@Airnet.co.uk> wrote in message
news:052101c2d755$c815d060$a501280a@phx.gbl...
> 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 ...
>
>