Logging query errors: manager

Showing posts with label manager. Show all posts

Monday, March 26, 2012

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.
>

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

Friday, March 23, 2012

Login failed for user '(null)'

I have SQL Server 2000 Enterprise Manager installed on XP box. I want to
connect to SQL Server 2000, using trusted connection. I have required
permisiions, but I receive this error message:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
Has anyone any idea?
Thanks in advance.
Best Reagrds,
Bil
Hi Bil,
Here is a link to an article on troubleshooting connectivity:
http://support.microsoft.com/default...&Product=sql2k
In addition, I archived an email from another individual that received a
similar error (slightly different circumstances), I'm reposting it in case
it helps you -- let us know?
~~~~~~~
There are two ways to fix this problem: to remove TCP/IP protocol from SQL
server or to impersonate users.
Remove TCP/IP
1. Go to SQL Server properties, then to General tab - Network configuration.
Remove TCP/IP protocol there.
This worked for me. However, since TCP/IP is required for replication, I had
to add it back.
Impersonate SQL Server users.
Usually you can impersonate users by going to the Local security policy in
Administrative Tools, then to Impersonate a client after authentication.
However, if you deal with the Domain controller, most of the controls there
are disabled. So:
1. Go to the Active Directory, right-click on Domain Controllers and select
Properties
2. Go to the Group Policy tab and highlight Default Domain Controller
Policy, click Edit
3. Go to Windows Settings - Security Settings - Local Policies - User Rights
Assignment
4. Double-click Impersonate a client after authentication
Then Microsoft suggested to uncheck the box Define these policy settings,
then go to the Local security policy and add users there. It worked.
However, I think it would be better just add the users right there, without
going to the Local security policy.
Either way, this solved my problem.
~~~~~~~
Steve
"Bil" <biljanat@.nbrm.gov.mk> wrote in message
news:%23oR4wygpEHA.2304@.TK2MSFTNGP14.phx.gbl...
> I have SQL Server 2000 Enterprise Manager installed on XP box. I want to
> connect to SQL Server 2000, using trusted connection. I have required
> permisiions, but I receive this error message:
> Connection failed:
> SQLState: '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> Has anyone any idea?
> Thanks in advance.
> Best Reagrds,
> Bil
>
|||Steve, thank you very much. I will reply to group about the results.
Best Regards,
Bil
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:#tre8LipEHA.3728@.TK2MSFTNGP09.phx.gbl...
> Hi Bil,
> Here is a link to an article on troubleshooting connectivity:
>
http://support.microsoft.com/default...&Product=sql2k
> In addition, I archived an email from another individual that received a
> similar error (slightly different circumstances), I'm reposting it in case
> it helps you -- let us know?
> ~~~~~~~
> There are two ways to fix this problem: to remove TCP/IP protocol from SQL
> server or to impersonate users.
> Remove TCP/IP
> 1. Go to SQL Server properties, then to General tab - Network
configuration.
> Remove TCP/IP protocol there.
> This worked for me. However, since TCP/IP is required for replication, I
had
> to add it back.
> Impersonate SQL Server users.
> Usually you can impersonate users by going to the Local security policy in
> Administrative Tools, then to Impersonate a client after authentication.
> However, if you deal with the Domain controller, most of the controls
there
> are disabled. So:
> 1. Go to the Active Directory, right-click on Domain Controllers and
select
> Properties
> 2. Go to the Group Policy tab and highlight Default Domain Controller
> Policy, click Edit
> 3. Go to Windows Settings - Security Settings - Local Policies - User
Rights
> Assignment
> 4. Double-click Impersonate a client after authentication
> Then Microsoft suggested to uncheck the box Define these policy settings,
> then go to the Local security policy and add users there. It worked.
> However, I think it would be better just add the users right there,
without
> going to the Local security policy.
> Either way, this solved my problem.
> ~~~~~~~
> Steve
> "Bil" <biljanat@.nbrm.gov.mk> wrote in message
> news:%23oR4wygpEHA.2304@.TK2MSFTNGP14.phx.gbl...
>
|||I removed TCP/IP protocol on client machine and this resolved the problem.
Thank you again for your help.
Best Regards,
Bil
"Bil" <biljanat@.nbrm.gov.mk> wrote in message
news:OCh98PipEHA.324@.TK2MSFTNGP11.phx.gbl...
> Steve, thank you very much. I will reply to group about the results.
> Best Regards,
> Bil
>
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:#tre8LipEHA.3728@.TK2MSFTNGP09.phx.gbl...
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
case[vbcol=seagreen]
SQL[vbcol=seagreen]
> configuration.
> had
in[vbcol=seagreen]
> there
> select
> Rights
settings,[vbcol=seagreen]
> without
to
>
|||Excellent -- thanks for replying with the resolution.
Steve
"Bil" <biljanat@.nbrm.gov.mk> wrote in message
news:eK194YipEHA.2104@.TK2MSFTNGP10.phx.gbl...
> I removed TCP/IP protocol on client machine and this resolved the problem.
> Thank you again for your help.
> Best Regards,
> Bil
>
> "Bil" <biljanat@.nbrm.gov.mk> wrote in message
> news:OCh98PipEHA.324@.TK2MSFTNGP11.phx.gbl...
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
a[vbcol=seagreen]
> case
> SQL
I[vbcol=seagreen]
policy[vbcol=seagreen]
> in
authentication.[vbcol=seagreen]
> settings,
want[vbcol=seagreen]
> to
required[vbcol=seagreen]
user[vbcol=seagreen]
connection.
>
|||Hi,
I tried with TCP/IP and messed up something, had to install SQL server all
over again. Also i can not afford to do that, as it has to run on the client
machines. guys please have a look at the problem, probably you could help me
out.
I have a windows setup program (framework 1.1), this setup program calls
one util.exe with parameters. util.exe opens the connection (SQL Server
2000, windows authentication only) and does some db updations. when i run
thru setup exe fails throwing "Login failed for user ''(null)'. Reason: Not
associated with a trusted SQL Server connection" error. if i run the exe
separately thru command line argument, it executes properly.
I can give little more insight, while running thru the setup.exe, util.exe
runs under system account and if I run util.exe in stand alone mode it runs
under logged in user account, first case it always fails with the error as
mentioned.
How could I impersonate or what else could I do?
Thanks in advance
Prashant
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:Of3DXAjpEHA.3424@.TK2MSFTNGP12.phx.gbl...
[vbcol=seagreen]
> Excellent -- thanks for replying with the resolution.
> Steve
> "Bil" <biljanat@.nbrm.gov.mk> wrote in message
> news:eK194YipEHA.2104@.TK2MSFTNGP10.phx.gbl...
problem.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
received[vbcol=seagreen]
> a
in[vbcol=seagreen]
from[vbcol=seagreen]
replication,[vbcol=seagreen]
> I
> policy
> authentication.
controls[vbcol=seagreen]
Controller[vbcol=seagreen]
User
> want
> required
> user
> connection.
>
|||Could you elaborate on "I tried with TCP/IP and messed up something, had to
install SQL server"?
If you remove TCP/IP from the SQL Server library utility (following the
instructions in the attached email), you should not have had to re-install
SQL Server!
Have you tried the impersonation suggestion?
Steve
"Prashant" <barnwal_p@.hotmail.com> wrote in message
news:uEvP1o5qEHA.3172@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I tried with TCP/IP and messed up something, had to install SQL server all
> over again. Also i can not afford to do that, as it has to run on the
client
> machines. guys please have a look at the problem, probably you could help
me
> out.
> I have a windows setup program (framework 1.1), this setup program calls
> one util.exe with parameters. util.exe opens the connection (SQL Server
> 2000, windows authentication only) and does some db updations. when i run
> thru setup exe fails throwing "Login failed for user ''(null)'. Reason:
Not
> associated with a trusted SQL Server connection" error. if i run the exe
> separately thru command line argument, it executes properly.
> I can give little more insight, while running thru the setup.exe, util.exe
> runs under system account and if I run util.exe in stand alone mode it
runs
> under logged in user account, first case it always fails with the error as
> mentioned.
> How could I impersonate or what else could I do?
> Thanks in advance
> Prashant
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:Of3DXAjpEHA.3424@.TK2MSFTNGP12.phx.gbl...
> problem.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
> received
> in
> from
> replication,
> controls
and[vbcol=seagreen]
> Controller
> User
worked.[vbcol=seagreen]
there,
>
|||Hi Steve,
Thanks for giving ears, i posted multiple places to get the results, i will
continue with this group. I removed TCP/IP, protocol from server, and
restarted the services then none of SQL client were able to connect to the
server. I added back but in vain, it was a test bed, so i installed again.
I have gone thru articles and solutions listed here, nothing seems to
work-around for me.
my all computers are in lamboDomain, its small farm setup where IIS is on
one server and DB is on separate one. i have two small farm, on one farm
everthing works fine but second farm problem occurs.
If it is working for one farm do i still need to look into the
impersonation? i am asking this because then i'll have to take permission
from network authority to make changes in the active diorectory and i might
not be allowed.
please do the needful.
thanks,
Prashant
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:OJK7In7qEHA.376@.TK2MSFTNGP14.phx.gbl...
> Could you elaborate on "I tried with TCP/IP and messed up something, had
to[vbcol=seagreen]
> install SQL server"?
> If you remove TCP/IP from the SQL Server library utility (following the
> instructions in the attached email), you should not have had to re-install
> SQL Server!
> Have you tried the impersonation suggestion?
> Steve
> "Prashant" <barnwal_p@.hotmail.com> wrote in message
> news:uEvP1o5qEHA.3172@.TK2MSFTNGP10.phx.gbl...
all[vbcol=seagreen]
> client
help[vbcol=seagreen]
> me
calls[vbcol=seagreen]
run[vbcol=seagreen]
> Not
util.exe[vbcol=seagreen]
> runs
as[vbcol=seagreen]
results.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
it[vbcol=seagreen]
protocol[vbcol=seagreen]
> and
> worked.
> there,
I[vbcol=seagreen]
for
>
|||Hi Prashant,
Replies in-line
"Prashant" <barnwal_p@.hotmail.com> wrote in message
news:eJkYaDJrEHA.736@.tk2msftngp13.phx.gbl...
> Hi Steve,
> Thanks for giving ears, i posted multiple places to get the results, i
will
> continue with this group. I removed TCP/IP, protocol from server, and
> restarted the services then none of SQL client were able to connect to the
> server.
If I understand you correctly, you should NOT remove TCP/IP protocol from
the server, this is effectively like unplugging your server network cable!
This would also explain the clients being unable to connect...
What was suggested was:
" ... remove TCP/IP from the SQL Server library utility"
This is done by navigating to:
Start>Program Files>Microsoft SQL Server>Server Network Uitlity
Ensure (for this test) that only Named Pipes is enabled as THE primary SQL
Server protocol.

>I added back but in vain, it was a test bed, so i installed again.
> I have gone thru articles and solutions listed here, nothing seems to
> work-around for me.
> my all computers are in lamboDomain, its small farm setup where IIS is on
> one server and DB is on separate one. i have two small farm, on one farm
> everthing works fine but second farm problem occurs.
> If it is working for one farm do i still need to look into the
> impersonation?
Try the above suggestion, first, then we'll take it from there. Do check the
SQL Server Client Network Utility (same path as before) that Named Pipes is
enabled as THE primary SQL Server protocol.

>i am asking this because then i'll have to take permission
> from network authority to make changes in the active diorectory and i
might[vbcol=seagreen]
> not be allowed.
> please do the needful.
> thanks,
> Prashant
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:OJK7In7qEHA.376@.TK2MSFTNGP14.phx.gbl...
> to
re-install[vbcol=seagreen]
> all
> help
> calls
Server[vbcol=seagreen]
> run
Reason:[vbcol=seagreen]
exe[vbcol=seagreen]
> util.exe
error
> as
> results.
>
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
reposting[vbcol=seagreen]
> it
> protocol
security[vbcol=seagreen]
Controllers[vbcol=seagreen]
Policies -[vbcol=seagreen]
policy[vbcol=seagreen]
box.
> I
> for
>

Login failed for user '(null)'

Hello world,
I'm getting the following error when trying to register an instance of SQL
in Enterprise Manager (connecting using Windows authentication):
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
EM sits on a developer's PC running XP Professional SP2, and SQL Server 2000
Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
This particular PC was previously able to connecte to this manner prior to
migrating the SQL server from being a member server within an NT4 domain to
being a member server within a Windows 2003 Active Directory Domain.
Any thought's as to why Windows authentication has stopped working would be
most appreciated.Chris
Do you grant access to SQL Server,for login? What is a default database
did you assign to him?
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:0189E38E-31FC-4E43-A79E-FCABE2726A9A@.microsoft.com...
> Hello world,
> I'm getting the following error when trying to register an instance of SQL
> in Enterprise Manager (connecting using Windows authentication):
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> EM sits on a developer's PC running XP Professional SP2, and SQL Server
> 2000
> Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
> This particular PC was previously able to connecte to this manner prior to
> migrating the SQL server from being a member server within an NT4 domain
> to
> being a member server within a Windows 2003 Active Directory Domain.
> Any thought's as to why Windows authentication has stopped working would
> be
> most appreciated.|||Uri
Thanks for replying so quickly.
Yes for the purposes of testing the connection, I've assigned the developer
(an ordinary domain user) public access to Northwind.
I've also tried making them a member of the Sysadmin Server role to no effec
t.
The same user can connect to another SQL server using Windows Authentication
(SQL 2000 Workgroup Ed SP4 running on Windows 2003 SP1).
I've just tried the same user from a different PC and he can log in from
there too (that one runs Windows 2000 Professional SP4).
"Uri Dimant" wrote:

> Chris
> Do you grant access to SQL Server,for login? What is a default database
> did you assign to him?
>|||Chris
Any errors in event viewer, sql server log file?
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:5DD31C06-D0ED-4DC1-9768-A072FBBBBA1B@.microsoft.com...
> Uri
> Thanks for replying so quickly.
> Yes for the purposes of testing the connection, I've assigned the
> developer
> (an ordinary domain user) public access to Northwind.
> I've also tried making them a member of the Sysadmin Server role to no
> effect.
> The same user can connect to another SQL server using Windows
> Authentication
> (SQL 2000 Workgroup Ed SP4 running on Windows 2003 SP1).
> I've just tried the same user from a different PC and he can log in from
> there too (that one runs Windows 2000 Professional SP4).
> "Uri Dimant" wrote:
>
>|||Uri
Nothing that appears to by related to the problem on either the Server SQL
and Event logs or the client event logs.
Most of the events in the security logs appear to be Privilege Use types
related to other processes.
"Uri Dimant" wrote:

> Chris
> Any errors in event viewer, sql server log file?
>|||Can anyone offer any other suggestions?|||Further tests have revealed that only clients with Windows XP Professional
are affected. Prior OS versions seem to work fine.|||Several things...
1) Depending on how your active directory is setup, you may need to be in
the domain to authenticate to it if it's only supporting kerberos rather
than just ntlm
2) Domain policies can restrict stuff. If both computers aren't in the
domain than perhaps one is more restrictive than the other.
3) If using kerberos to authenticate, you may need to enable kerberos
delegation on the sql server.
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:0189E38E-31FC-4E43-A79E-FCABE2726A9A@.microsoft.com...
> Hello world,
> I'm getting the following error when trying to register an instance of SQL
> in Enterprise Manager (connecting using Windows authentication):
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> EM sits on a developer's PC running XP Professional SP2, and SQL Server
> 2000
> Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
> This particular PC was previously able to connecte to this manner prior to
> migrating the SQL server from being a member server within an NT4 domain
> to
> being a member server within a Windows 2003 Active Directory Domain.
> Any thought's as to why Windows authentication has stopped working would
> be
> most appreciated.

Login failed for user (null)

Hi,

I am using MS SQL 2000 Personal Edition on my Windows XP Professional machine. It is working fine with Enterprice manager and SQL Query analyser.

To use the db in my web application I configured a system dsn of "SQL Server" driver. I used "sa" user with my pass and tested the connection. It said it was ok. When I used in my web page it throws this exception

ODBC Error Code = 28000 (Invalid authorization specification)

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Any one could help me figure this prob.Can you post the connection string you are using? To the best of my knowledge, if you are using DSN connection, you still need to supply the user name and password.

Regards,

Hugh Scott

Originally posted by karthiknataraj
Hi,

I am using MS SQL 2000 Personal Edition on my Windows XP Professional machine. It is working fine with Enterprice manager and SQL Query analyser.

To use the db in my web application I configured a system dsn of "SQL Server" driver. I used "sa" user with my pass and tested the connection. It said it was ok. When I used in my web page it throws this exception

ODBC Error Code = 28000 (Invalid authorization specification)

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Any one could help me figure this prob.|||I use Cold fusion. So I created a system DSN and in my <cfquery> tag I simply give the dsn name. Another one site which is live uses sql server and I checked the code it the same.

<CFQUERY NAME="Q1" DATASOURCE="Test">
Select * from emp
</CFQUERY>|||I don't have any experience with Cold Fusion, and I try to stay away from DSN connections as much as possible. I am digging through the cobwebs of my memory to try to come up with an answer.

I would:
1. Re-verify that the password is saved in your DSN config
2. Try specifying the UID and password in the CFQUERY; your production web server may be using a Windows Trusted connection to your SQL Server.
3. See if Cold Fusion can make DSN-less connections to source databases.

HTH,

Hugh Scott

Originally posted by karthiknataraj
I use Cold fusion. So I created a system DSN and in my <cfquery> tag I simply give the dsn name. Another one site which is live uses sql server and I checked the code it the same.

<CFQUERY NAME="Q1" DATASOURCE="Test">
Select * from emp
</CFQUERY>|||I had the same problem. Microsft had me chage the AllowInProcess reg key to 0 for the provider type I was having issues with (in my case MADASQL). This will move these connections out of the MemToLeave area the SQL uses. However you will have to use SQL authentication after this.|||Even if you use a pedifined DSN for your connection, you still HAVE to supply the user="sa" and the pass="". I don't how you can do this with cold fusion, but I that's a guess:

"DATASOURCE=DSN2;USER=SA:PASSWORD="

Monday, March 19, 2012

Login failed - Catalog information cannot be retrieved

When I try to connect to a MS Access 2000 database in

enterprise Manager , i get

an error "Login failed -

Catalog information cannot be retrieved". I get this

error message in a dialog box about 5 or 6 times. The

database file location ends up in the file location box. I

can click "Test Connection" and the connection succeeds

with a series of dialog boxes with the message "Login

failed - Catalog information cannot be retrieved"

Any help is appreciated greatly.

--
Posted via http://dbforums.comjagdishkab wrote:

>When I try to connect to a MS Access 2000 database in
>enterprise Manager , i get
>an error "Login failed -
>Catalog information cannot be retrieved". I get this
>error message in a dialog box about 5 or 6 times. The
>database file location ends up in the file location box. I
>can click "Test Connection" and the connection succeeds
>with a series of dialog boxes with the message "Login
>failed - Catalog information cannot be retrieved"
>
>Any help is appreciated greatly.
>
>--
>Posted via http://dbforums.com
>
Why would you think you could connect to MS Access with Enterprise Manager?

You want help? I'd suggest something I rarelly say: RTFineM.

--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)|||jagdishkab wrote:

>When I try to connect to a MS Access 2000 database in
>enterprise Manager , i get
>an error "Login failed -
>Catalog information cannot be retrieved". I get this
>error message in a dialog box about 5 or 6 times. The
>database file location ends up in the file location box. I
>can click "Test Connection" and the connection succeeds
>with a series of dialog boxes with the message "Login
>failed - Catalog information cannot be retrieved"
>
>Any help is appreciated greatly.
>
>--
>Posted via http://dbforums.com
>
Sorry about my previous post ... I read "Enterprise Manager" and thought
I was in an Oracle group.

You'd think copyright law would keep people from naming products the
same. Oh well. Again sorry.

--
Daniel Morgan
http://www.outreach.washington.edu/...oad/oad_crs.asp
http://www.outreach.washington.edu/...aoa/aoa_crs.asp
damorgan@.x.washington.edu
(replace 'x' with a 'u' to reply)

Monday, March 26, 2012

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

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

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

Friday, March 23, 2012

Login failed for user '(null)'

Login failed for user '(null)'

Login failed for user (null)

Monday, March 19, 2012

Login failed - Catalog information cannot be retrieved

Logging query errors

Blog Archive

About Me