Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC call
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.
This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx