another "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." post :)

  • Hi,

    I've set up a linked server between one of our 2005 boxes and our 2000 box. I've used the "be made using the login's current security context" option.

    I'm the uberadminster so I can connect no problems but one of the chaps in dev gets the dreaded:

    Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

    He connects using his domain account which is part of a group which has permissions on both servers (ie his domain account isn't on either server itself just the group). He can log on to both servers via remote access and see things but the second he uses the db link he gets the above error.

    I've tested the link works as a fixed sqlserver user on both sides - I assume the issue lies with the fact he's connecting though a group.

    Any ideas SQLServerCentral.comrades? Clearly I could just create him a login on both sides but that's not the way we do things as we'd have hundreds of user logins.

  • Have you tried switching to use "using this security context" and specify the domain and group?

    Tom

  • wouldn't that then restrict the use of the link to people in that group? at the moment we have a service account using it too which works fine.

  • Sarah Orange (8/22/2011)


    wouldn't that then restrict the use of the link to people in that group? at the moment we have a service account using it too which works fine.

    Yes, it would. So you would have to add a separate linkedserverlogin for that service account, specifying that it uses its own credentials. This would be a pain if you have a lot of such accounts.

    I seem to remember an option to specity the security for "all other accounts" (ie what to do with accounts for which you haven't specified what credentials to use at the remote server, but I can't find any documentation for it in BoL, and I don't have a 2005 installation that I can play with to see if it shows up in SSMS. If that option does exist it would make things simpler.

    Tom

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply