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

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"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> 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.
If you enable auditing on both the server and SQL Server, do you see any
failed login attempts? If so, which account is being used?
Steve|||"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> 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.
Moments after I posted the last message, I found this link which may be of
value to you:
How to troubleshoot connectivity issues in SQL Server 2000
http://www.support.microsoft.com/?id=827422
Steve|||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
>|||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
> >
> >
>|||Thank you, Steve.
I'm working on it, buy now I even cannot get in with my administrative (sa)
account. I don't know what's wrong.
Peter
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > 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.
> Moments after I posted the last message, I found this link which may be of
> value to you:
> How to troubleshoot connectivity issues in SQL Server 2000
> http://www.support.microsoft.com/?id=827422
> Steve
>|||By chance, did you change the security mode and not restart MSSQLServer
service?
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Thank you, Steve.
> I'm working on it, buy now I even cannot get in with my administrative
(sa)
> account. I don't know what's wrong.
> Peter
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> >
> > > 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.
> >
> > Moments after I posted the last message, I found this link which may be
of
> > value to you:
> >
> > How to troubleshoot connectivity issues in SQL Server 2000
> > http://www.support.microsoft.com/?id=827422
> >
> > Steve
> >
> >
>|||Peter,
Do you get the same error when logging in as 'sa'? If so, that is telling
you that the server is not accepting standard SQL logins, no matter what the
settings seems to be.
Do you have a domain account with sysadmin rights that you can login with?
If so, try that one.
During the upgrade of your server, did you lose any local Windows accounts?
Domain accounts? Look at article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307002
Russell Fields
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> Thank you, Steve.
> I'm working on it, buy now I even cannot get in with my administrative
(sa)
> account. I don't know what's wrong.
> Peter
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> >
> > > 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.
> >
> > Moments after I posted the last message, I found this link which may be
of
> > value to you:
> >
> > How to troubleshoot connectivity issues in SQL Server 2000
> > http://www.support.microsoft.com/?id=827422
> >
> > Steve
> >
> >
>|||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
> > >
> > >
> >
> >
>|||I did restart it, thanks.
Peter
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:e1RnoaUMEHA.1556@.TK2MSFTNGP10.phx.gbl...
> By chance, did you change the security mode and not restart MSSQLServer
> service?
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Thank you, Steve.
> >
> > I'm working on it, buy now I even cannot get in with my administrative
> (sa)
> > account. I don't know what's wrong.
> >
> > Peter
> >
> > "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> > news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > >
> > > > 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.
> > >
> > > Moments after I posted the last message, I found this link which may
be
> of
> > > value to you:
> > >
> > > How to troubleshoot connectivity issues in SQL Server 2000
> > > http://www.support.microsoft.com/?id=827422
> > >
> > > Steve
> > >
> > >
> >
> >
>|||No, it's accepting standard logins, it's just not accepting sa. I didn't
loose any Windows accounts.
All articles I saw say that it has something to do with impersonation, but I
even cannot change these settings - all my controls in Local security policy
are greyed out.
And SQL server doesn't take any domain accounts.
Thanks,
Peter
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:%23pXmGcUMEHA.3944@.tk2msftngp13.phx.gbl...
> Peter,
> Do you get the same error when logging in as 'sa'? If so, that is telling
> you that the server is not accepting standard SQL logins, no matter what
the
> settings seems to be.
> Do you have a domain account with sysadmin rights that you can login with?
> If so, try that one.
> During the upgrade of your server, did you lose any local Windows
accounts?
> Domain accounts? Look at article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;307002
> Russell Fields
> "Peter Afonin" <pva@.speakeasy.net> wrote in message
> news:OVxnWVUMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > Thank you, Steve.
> >
> > I'm working on it, buy now I even cannot get in with my administrative
> (sa)
> > account. I don't know what's wrong.
> >
> > Peter
> >
> > "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> > news:uD1X1CUMEHA.3596@.tk2msftngp13.phx.gbl...
> > > "Peter Afonin" <pva@.speakeasy.net> wrote in message
> > > news:uv2RYZTMEHA.2500@.TK2MSFTNGP12.phx.gbl...
> > >
> > > > 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.
> > >
> > > Moments after I posted the last message, I found this link which may
be
> of
> > > value to you:
> > >
> > > How to troubleshoot connectivity issues in SQL Server 2000
> > > http://www.support.microsoft.com/?id=827422
> > >
> > > Steve
> > >
> > >
> >
> >
>|||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
> > > >
> > > >
> > >
> > >
> >
> >
>|||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
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>
>.
>|||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
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >|||"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"
null points to an anonymous user that tries to login. In a (default) Win2000
is anonymous login easily possible. In Win2003 not.
Another thing to look at, is your client configuration (see SQL menu). It
might be that you use the wrong protocol such as TCP/IP while it needs named
pipes.|||Thanks for posting the solution!
"Peter Afonin" <pva@.speakeasy.net> wrote in message
news:eFGjcYYMEHA.2628@.TK2MSFTNGP12.phx.gbl...
> 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
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> > >.
> > >
>|||Thank you.
You're correct, removing TCP/IP protocol solved the problem as well.
However, we needed TCP/IP for replication. Impersonation solved all
problems, and we could add TCP/IP back.
Peter
"Egbert Nierop (MVP for IIS)" <egbert_nierop@.nospam.invalid> wrote in
message news:ep7NeCaMEHA.340@.TK2MSFTNGP11.phx.gbl...
> "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"
> null points to an anonymous user that tries to login. In a (default)
Win2000
> is anonymous login easily possible. In Win2003 not.
> Another thing to look at, is your client configuration (see SQL menu). It
> might be that you use the wrong protocol such as TCP/IP while it needs
named
> pipes.
>