[quoted text, click to view]

Um, a connection string that doesn't specify a SQL username and password?
Could you show the connection string you're using, so we don't have to
guess?

I have a job that connects one SQL Server to another (both MSDE).
Sometimes (most of the times) a got an error that says:
"Login failed for user 'userID'. Reason: Not associated with a trusted SQL
connection."

I already have made all the things that i see in newsgroups to correct the
problem but it continues to persist.
I use SQL Authentication and i have already test changing the security in
the linked servers, but it continues to give me this error. I also change
authentication of SQL Server to Windows and then to Mixed mode and the
results are the same: doesn't work.
I have a third SQL Server (also MSDE) that connects without problems to my
central server.
All machines have Windows XP Pro installed.

What could be the cause of this?

thanks,
Gonçalo Boléo
Portugal

Previous post:

""Login failed for user 'userID'. Reason: Not associated with a trusted SQL
connection."
"I use SQL Authentication and i have already test changing the security in
the linked servers, but it continues to give me this error. I also change
authentication of SQL Server to Windows and then to Mixed mode and the
results are the same: doesn't work"

The error message indicates that the connection request from the job is
attempting to make a Windows NT Authenticated connection and failing.
Since you indicate that you're using SQL Authentication, then this is the
expected result. Windows NT Authentication uses the domain credentials of
the client. Changing the server to Mixed mode should resolve this only if
you restart the MSSQLServer service for the remote server.

Who owns the jobs? Are they owned by NT users or groups or by Standard SQL
logins?


Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

try starting the NTLM ss Provider service.
[quoted text, click to view]