Login failed for user == Error: 18456, Severity: 14, State: 11

Question

Something has changed into my Windows XP server (the one that SQL Server is installed) and I cannot connect to the database.

The error is

Login failed for user == Error: 18456, Severity: 14, State: 11

State 11 = Login is Valid, but server access failed.

Also, by looking into "Event Viewer" I keep seeing the following error:

Type = Failure Audit

Source = MSSQLSERVER

Event = 18456

Description = Login failed for user '<Domain USer>'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

Best regards,

Tom

 

 

---

New to SQL Server

Answer 1

Has the account you are using been dropped and re-created recently, or migrated and the SID has changed? If so you may find that dropping the login and re-creating it helps.

 

Thanks

---

/Neil Moorthy - Senior SQL Server DBA/Developer (MCITP (2005/2008), MCAD, ITILv3, OCA 11g) Please click the Mark as Answer button if a post solves your problem

Answer 2

Actually, the Windows Team had to replace the Domain Controller!

I was told that no user has been dropped.

I used to connect to SQL Server (SQL Server 2008), with a domain user acccount, now I can NOT.

I have even tried the (local) Administrator account, I get the same error (from the sqlcmd prompt):
<< Error: 18456, Severity: 14, State: 11 >>

On top of that, I am missing the password for 'sa' !!!

What are my alternative(s) ?

Best regards,

Tom

 

 

---

New to SQL Server

Answer 3

The issue has been resolved!

I started SQL Server, in Single User Mode, and then I was able to logon as (local)\Administrator.

 

---

New to SQL Server

Answer 4

That is great, but I have 3 users that need to use it.

On one machine we have This problem:

SQL Server on server log reports failed login codes:

Error: 1846 Severity: 14 State: 11

But on others we do not.

The machine...

SQL Server 2008 R2 64x V10.50.2500.0 on Server 2008 R2

Running on VMWare

Answer 5

Rather than posting to a very old thread, it's better to start a new thread.

Are these Windows logins or SQL logins?

If they are Windows logins, try dropping them and readding them. Do the same for the database users. The logins may have been dropped and readded in the AD.

---

Erland Sommarskog, SQL Server MVP, [e-mail]