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
>
