Re: SQL Server 2005 Windows Authentication - logon failure
- From: "Rick Byham, \(MSFT\)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Aug 2008 08:48:39 -0700
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?
--
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
.
- Follow-Ups:
- References:
- SQL Server 2005 Windows Authentication - logon failure
- From: dooseiai
- SQL Server 2005 Windows Authentication - logon failure
- Prev by Date: SQL Server 2005 Windows Authentication - logon failure
- Next by Date: Re: how to find out if a domain user is in the sysadmin server role?
- Previous by thread: SQL Server 2005 Windows Authentication - logon failure
- Next by thread: Re: SQL Server 2005 Windows Authentication - logon failure
- Index(es):
Relevant Pages
|