Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\loginname'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
There are several reasons because of which you could get this error but the primary reason is as follows.
Typically, when you are asked to provide access to a SQL Server instance, you would create a new login (windows or SQL) in the SQL Server instance.
But sometimes the person who is responsible for creating an account for you and give you sysadmin role, will add your windows domain login to the LOCAL ADMINISTRATIVE login group. This is assuming the fact that the local admin login is a sysadmin on SQL Server instance. So I have always wondered why we get this error.
But the easy fix is to explicitly create a new login with Windows Authentication in the SQL Server instance and assign the server role to that ID.
Login failed for user 'domain\loginname'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
There are several reasons because of which you could get this error but the primary reason is as follows.
Typically, when you are asked to provide access to a SQL Server instance, you would create a new login (windows or SQL) in the SQL Server instance.
But sometimes the person who is responsible for creating an account for you and give you sysadmin role, will add your windows domain login to the LOCAL ADMINISTRATIVE login group. This is assuming the fact that the local admin login is a sysadmin on SQL Server instance. So I have always wondered why we get this error.
But the easy fix is to explicitly create a new login with Windows Authentication in the SQL Server instance and assign the server role to that ID.
I am seeing the same error but don't want to be creating a login for every user in the group. Did you find an answer to this problem?
ReplyDeleteUnfortunately, I haven't found a solution to this But for some strange reason this does not happen with every user. So i don't have to do it for everyone.
ReplyDeleteIt seems to be a very old post but still wish to put my comment .
ReplyDeleteI have dropped the login and then re-created and it is working fine for me.
yeah for me also the error appeared for two hours and after that it started working fine.
ReplyDelete