Re: client logins
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2006 19:38:10 -0600
From the error, it looks like you need to use Windowsauthentication. Just because you can create a SQL login
doesn't mean the server accepts a SQL login. The SQL Server
can be configured to use Windows Authentication only.
Since you can login somehow (when you added the user), you
can check by executing:
select serverproperty('IsIntegratedSecurityOnly')
If it returns 1, your SQL Server allows Windows
authentication only and in that case you can't use SQL
logins.
-Sue
On Fri, 7 Apr 2006 14:43:02 -0700, rseedle
<rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Sue:
I looked up Windows Authentication and found the procedure to create a user
using a windows authentication. I tried using the SQL Server authentication
instead. It created the user but trying to use it in the Visual Studios
server explorer, add new connection still produces the error:
Login failed for user 'new_testID'. Reason: Not associated with a trusted
SQL Server connection.
Randy
"Sue Hoegemeier" wrote:
If Windows logins work and SQL logins do not then the server
may be set to Windows Authentication only. You also need to
make sure that you also add the login as a user to whatever
database the app is using and the database user needs the
appropriate permissions. But it could be a lot of different
things. Without any specific error message, it's all just a
guess.
-Sue
SQL Server MVP
On Tue, 4 Apr 2006 19:34:01 -0700, rseedle
<rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
How come when I make a SQL Server login that login can't be used to login
from my C# application (OLEDBConnection.Open()) or the properties menu
wizard.
Randy
.
- References:
- Re: client logins
- From: Sue Hoegemeier
- Re: client logins
- Prev by Date: Re: different environment fails to fill a dataset
- Next by Date: Re: different environment fails to fill a dataset
- Previous by thread: Re: client logins
- Next by thread: Re: client logins
- Index(es):
Relevant Pages
|
Loading
