Re: SQL Server 2005 Windows Authentication - logon failure

From: "Janusz" <samsUSUNTO@xxxxxxxxxx>
Date: Fri, 22 Aug 2008 08:55:08 +0200

"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0EC69D65-A6D4-4DE0-9545-F30CA0393313@xxxxxxxxxxxxxxxx

Error: 18456, State 11 is "Login is valid, but server access failed."
1. In Management Studio, in Object Explorer, expand Security, expand

Logins,

right-click the users login, and then click Properties.
2. On the Status page, are Grand and Enabled selected?
--

Both are selected.

Regards,
Janusz

Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no

rights.

<dooseiai@xxxxxxxxx> wrote in message
news:f365be24-0f71-414f-97d4-f834c3f67c55@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi all,

I have a problem with SQL Server 2005. The application (written in
VB.NET) connects to SQL Server 2005 using Windows Authentication. When
a user's domain account had been locked out, the user - after it has
been made active again - cannot connect to the DB (with a message
"login failed for user (...)". The user's account is defined in the DB
it tries to connect to and it has necessary DB permissions. SQL
Server's log shows:

08/21/2008 09:11:39,Logon,Unknown,Login failed for user 'XXX\ABC'.
[CLIENT: XXX.XXX.XXX.XXX]
08/21/2008 09:11:39,Logon,Unknown,Error: 18456<c/> Severity: 14<c/>
State: 11.

Any ideas of what can be wrong?

Best regards,
Janusz

References:
- SQL Server 2005 Windows Authentication - logon failure
  - From: dooseiai
- Re: SQL Server 2005 Windows Authentication - logon failure
  - From: Rick Byham, \(MSFT\)

Prev by Date: Re: sp_revoke login is not working as expected.
Next by Date: RE: Setuser failed?
Previous by thread: Re: SQL Server 2005 Windows Authentication - logon failure
Next by thread: Re: how to find out if a domain user is in the sysadmin server role?
Index(es):
- Date
- Thread

Relevant Pages

Re: System Administrator Implied Permissions
... >> Hi Dan, ... >> Now, given this, why does SQL Server ... However, these logins were not ... Other sysadmin role members have the ...
(microsoft.public.sqlserver.security)
Re: SQL Server 2005 Login Problem
... There are two authentication method in SQL Server. ... 1- Windows Authentication ... Only creating Logins is not the complete solution of course, then you'll need to map those users to the appropriate databases and assign them roles and grant them permissons. ...
(microsoft.public.sqlserver.clients)
Re: Windows permissions to run Jet OLEDB 4.0
... in SQL Server or not when you have to go outside of the server to the ... Actually I was talking about Windows logins. ... There is no security whatsoever implemented on the mdb ...
(microsoft.public.data.oledb)
Re: Logins & Permissions
... At server level, we use "Logins" to connect to a SQL Server Instance and perform server level jobs. ... "Users" are used and these users are mapped to Logins. ... I am using SQL Server 2005 on a Windows NT Network ...
(microsoft.public.sqlserver.security)
No Application Logins Allowed - SOX
... I'm trying to work through an issue regarding our MS SQL Server logins. ... "Customer" application uses a login to SQL Server called "Customer" and the ... Grant our users Windows Authentication access to SQL Server. ...
(microsoft.public.sqlserver.security)