Re: Login failed for user '(null)'
From: Bil (biljanat_at_nbrm.gov.mk)
Date: 09/29/04
- Next message: folke: "Selecting from 3 tables."
- Previous message: Bil: "Re: Login failed for user '(null)'"
- In reply to: Bil: "Re: Login failed for user '(null)'"
- Next in thread: Steve Thompson: "Re: Login failed for user '(null)'"
- Reply: Steve Thompson: "Re: Login failed for user '(null)'"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Sep 2004 15:15:03 +0200
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...
> > Hi Bil,
> >
> > Here is a link to an article on troubleshooting connectivity:
> >
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;827422&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
> > >
> > >
> >
> >
>
>
- Next message: folke: "Selecting from 3 tables."
- Previous message: Bil: "Re: Login failed for user '(null)'"
- In reply to: Bil: "Re: Login failed for user '(null)'"
- Next in thread: Steve Thompson: "Re: Login failed for user '(null)'"
- Reply: Steve Thompson: "Re: Login failed for user '(null)'"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
