RE: login failed for user "null"
From: Chris Barnwell (Barnwell_at_discussions.microsoft.com)
Date: 08/27/05
- Next message: Kalen Delaney: "Re: Confused about dbo"
- Previous message: Rene: "Re: Confused about dbo"
- In reply to: dobrzak: "login failed for user "null""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 26 Aug 2005 16:53:01 -0700
Are the linked servers set up to "Be made using the login's current security
context"? If that's the case, then I'm guessing that you are having a
problem with delegation. Review the BOL topic "Security Account Delegation"
this will get you going in the right direction. You will need to have a
domain admin assist you with this if you do not have domain admin rights.
After running the setspn command, it may take a while for the change to take
effect. (at least it did in my environment)
"dobrzak" wrote:
> Hello,
> I have problem with linked servers (MS SQL Server 2k)- when I try to execute
> query(update, insert..) with linked servers, I have message Login failed for
> user 'null'. This is very strange problem, some computers in AD (2k3 std)
> don't have this error, when the other have this problem for few hours and
> some have this error all the time. Network Protocols is TCP/IP.
>
> Any idea ?
>
>
>
- Next message: Kalen Delaney: "Re: Confused about dbo"
- Previous message: Rene: "Re: Confused about dbo"
- In reply to: dobrzak: "login failed for user "null""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|