SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Strange login connectivity issue


Strange login connectivity issue

Author
Message
Database admin(DBA)
Database admin(DBA)
SSCarpal Tunnel
SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)SSCarpal Tunnel (4.7K reputation)

Group: General Forum Members
Points: 4652 Visits: 2001

Hello All,

I’m facing some strange issue when troubleshooting the user connectivity issue.

User not able to connect to SQL Server but he can able to RDP to the machine ,however user id is already part of AD domain group with enough permission on the database instance.so there is no issue with AD level

But still user not able to connect to the Database and getting the below error message ,even user tried with runas administrator but no luck..

Login failed for user ‘Microsoft\DBA’ . Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

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

Please kindly let me know how to troubleshoot this issue further (Pls don’t say its UAC part)

Thanks in advance!!

Best Regards,



SQL server DBA
Chris Harshman
Chris Harshman
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: General Forum Members
Points: 36329 Visits: 6952
Database admin(DBA) - Friday, September 15, 2017 1:25 PM

Login failed for user ‘Microsoft\DBA’ . Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

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


SQL Server access doesn't really have any correlation to RDP access, other than that proves the user can reach the server over the network.
I've typically seen this specific error when the user trying to connect to SQL Server using Windows authentication doesn't have a login setup or an AD group they belong to setup as a login for the SQL Server instance.
Try running this command in the database the user is trying to access to see if it returns a mapped login name and a permission path:
exec xp_logininfo N'Microsoft\DBA','all'

Arsh
Arsh
SSCarpal Tunnel
SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)SSCarpal Tunnel (4.9K reputation)

Group: General Forum Members
Points: 4941 Visits: 998

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search