Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
From: Peter Afonin (pva_at_speakeasy.net)
Date: 05/04/04
- Next message: Hari: "Re: tableoption"
- Previous message: Ronald James: "alerting for severity levels and not through SQL Alerts"
- In reply to: Mike Y: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Next in thread: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Reply: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 20:15:59 -0700
Thank you everyone for your help.
I finally had to open ticket with Microsoft. The problem was just like with
ASP - I had to add some accounts to "Impersonate users after authentication"
setting in the Local Security policy. It was mentioned in some articles, but
in Windows server 2003 the controls in my Local Security policy were
disbled, so I couldn't add anything. It took Microsoft some time to figure
out how to enable it.
So it's OK now.
Thanks again,
Peter
"Mike Y" <anonymous@discussions.microsoft.com> wrote in message
news:7efa01c43182$f9fc5670$a001280a@phx.gbl...
> Hi Peter,
>
> I actually just fix the same problem with out enviroment.
> My questions are that:
> 1. Do you have novell client installed on your computer
> 2. Is your computer in any domains or just create new
> domain
> If so, bypass novell and just login windows domain or AD
> firstly to see any changes. This is what I did to fix the
> null login problem.
> If you do not have novell. make sure you have a domain
> login (Or just re create new login)and try again.
> Good luck
>
> Mike
>
>
> >-----Original Message-----
> >Was there a change in servername ? Run "select
> @@servername " within QA .
> >Does this coincide with the actual servername ? If not,
> look at
> >sp_dropserver and sp_addserver
> >I have seen that message when my system is too
> busy ...and cannot accept any
> >more connections. Look at you SQL error log and see if
> theres anything worth
> >a note there.
> >
> >"Russell Fields" <RussellFields@NoMailPlease.Com> wrote
> in message
> >news:O9MIXfUMEHA.556@TK2MSFTNGP10.phx.gbl...
> >> OK. The (null) probably suggests the comment in my
> other post. (Unless
> >> 'sa' is returning a similar message.)
> >>
> >> IF in the unlikely event that your registry is messed
> up:
> >> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;285097
> >>
> >> Russell Fields
> >> "Peter Afonin" <pva@speakeasy.net> wrote in message
> >> news:uNK2oUUMEHA.3216@TK2MSFTNGP12.phx.gbl...
> >> > Thank you, but it's configured this way.
> >> >
> >> > Peter
> >> >
> >> > "Russell Fields" <RussellFields@NoMailPlease.Com>
> wrote in message
> >> > news:O4mPpDUMEHA.624@TK2MSFTNGP11.phx.gbl...
> >> > > Peter,
> >> > >
> >> > > CAUSE
> >> > > This error occurs because the SQL Server is
> configured to use "Windows
> >> > only"
> >> > > authentication.
> >> > > RESOLUTION
> >> > > On the SQL Server Security tab, configure SQL
> Server to use "SQL
> >Server
> >> > and
> >> > > Windows" authentication.
> >> > >
> >> > > Russell Fields
> >> > > "Peter Afonin" <pva@speakeasy.net> wrote in message
> >> > > news:uv2RYZTMEHA.2500@TK2MSFTNGP12.phx.gbl...
> >> > > > Hello:
> >> > > >
> >> > > > I've just upgraded Windows 2000 server to
> Windows server 2003, and
> >> after
> >> > > > this I cannot get to the SQL server Enterprise
> manager, I'm getting
> >> > error
> >> > > > "Login failed for user '(null)'. Reason: Not
> associated with a
> >trusted
> >> > SQL
> >> > > > Server connection"
> >> > > >
> >> > > > I've found many articles about it, but they are
> all about problems
> >> with
> >> > > ASP
> >> > > > or ASP.Net. I don't have a problem with ASP.Net,
> my Intranet
> >> application
> >> > > is
> >> > > > running OK.
> >> > > >
> >> > > > I still can get in using SQL server connection
> if I change the
> >> > > registration
> >> > > > properties, but if I use Trusted connections I
> get this error. And I
> >> > need
> >> > > to
> >> > > > use trusted connections.
> >> > > >
> >> > > > I would appreciate any help very much.
> >> > > >
> >> > > > Thank you,
> >> > > >
> >> > > > --
> >> > > > Peter Afonin
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >
- Next message: Hari: "Re: tableoption"
- Previous message: Ronald James: "alerting for severity levels and not through SQL Alerts"
- In reply to: Mike Y: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Next in thread: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Reply: Steve Thompson: "Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|