 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Indrahig Guest
|
Posted: Sat Apr 10, 2004 5:01 am Post subject: Login failed for user <user_Name>. User not associated with |
|
|
I try to connect using ADO to SQL server 2000 through my application an
I get the following message:
"Login failed for user <user_Name>. User not associated with trusted
connection"
I use Windows XP Profesional and local server database (SQL server 2000).
Any help will be appreciated..
thanks,
Indra Gunawan
--- posted by geoForum on http://delphi.newswhat.com
|
|
| Back to top |
|
 |
Jeremy Collins Guest
|
Posted: Sat Apr 10, 2004 8:22 am Post subject: Re: Login failed for user <user_Name>. User not associated w |
|
|
Indrahig wrote:
| Quote: | I try to connect using ADO to SQL server 2000 through my application an
I get the following message:
"Login failed for user <user_Name>. User not associated with trusted
connection"
I use Windows XP Profesional and local server database (SQL server 2000).
Any help will be appreciated..
|
If you have "Integrated Security=SSPI" as part of your
connection string, then the username and password must
be a valid /Windows/ login, and you must enable "trusted
connections" AKA Windows Authentication in your SQL Server
settings.
If you do not wish to use trusted connections, remove
this from the connection string and instead include a
valid SQL Server user name and password.
--
jc
Remove the -not from email
|
|
| Back to top |
|
 |
Euan Garden Guest
|
Posted: Mon Apr 12, 2004 6:17 am Post subject: Re: Login failed for user <user_Name>. User not associated w |
|
|
Close but not really correct, the below is a simplfiied version.
If you specify SSPI in a connection string SQL Server will assume this is a
Windows authentication based session, as such you should not pass any userid
or password info on the connection string as Windows will pass the
credentials for you.
The security mode is called Windows Authentication (NT auth in SQL 7) and it
is ALWAYS on for SQL Server and hence the default.
If you wish to use SQL Authenication, this means passing a userid and
password in the connection string and not specifying SSPI, this mode needs
to be switched on either in setup or in the properties of the server,
because Windows Mode is always on, this second option is referred to as
mixed authentication because it supports both.
To get back to the original posters problem, its likely that you are passing
a User Id and Password in the connection string but are working in Windows
Auth only, you have 2 choices, switch the server to mixed mode or don't pass
the credentials and it should use your windows credentials.
-Euan
"Jeremy Collins" <jd.collins (AT) ntlworld-not (DOT) com> wrote
| Quote: | Indrahig wrote:
I try to connect using ADO to SQL server 2000 through my application an
I get the following message:
"Login failed for user <user_Name>. User not associated with trusted
connection"
I use Windows XP Profesional and local server database (SQL server
2000).
Any help will be appreciated..
If you have "Integrated Security=SSPI" as part of your
connection string, then the username and password must
be a valid /Windows/ login, and you must enable "trusted
connections" AKA Windows Authentication in your SQL Server
settings.
If you do not wish to use trusted connections, remove
this from the connection string and instead include a
valid SQL Server user name and password.
--
jc
Remove the -not from email
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|