Wednesday, March 21, 2012

Error: 18456, Severity: 14, State: 11 Valid login but server access failure

Recently, one of my clients began receiving this error. My team gave them sysadmin permissions, but this is terrible practice. I have read into disablying simple file sharing, but I don't even think I have the option to do it. I look in mycomputer > tools > view and don't see any option for this. Besides, the problem just started occuring recently, within the last week. The server is a cluster with veritas clustering and the edition is sql server 2000. Has anybody ever had a problem like this and have a good fix?

Thanks for any help in advance...

-Kyle

Disabling simple file sharing is usually more of something you do to address issues with XP operating system and authentication in workgroup scenarios. What user was the login failing for? Was it a regular domain user or a built in account that is failing? Does the login name show up in the login failure? How are the users granted access - individually, through groups or are they accessing this through an application and authentication is handled by the application?

-Sue

|||

Hi Sue,

I'm currently having the same issue.

We have 4 domain AD accounts who access an MS access link through citrix metaframe presentation server.

this links to the actual dbase on another server running SQL Server 2005.

3 of these accounts work fine.

one of them however comes up with the error which i'm reading from the log file viewer

Login failed for user 'Domain\Username'. (CLIENT: ip address)

Error: 18456, Severity:14, State: 11.

the error received when running the appliation is...

Connection Failed:

SQLState: '28000'

SQL Server Error: 18456

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'Domain\Username'.

I've checked and found that State: 11 means Valid login but server access failure.

this account is identical to the other 3 (AD and SQL).

any help will be greatly appreciated.

thanks,

luke

|||

Well...it's probably not exactly the same. Try dropping the problematic login (and user) from the database users and logins and then recreate it.

-Sue

No comments:

Post a Comment