Home Dashboard Directory Help
Search

Login failed for user '(domain)\dbuser'. Reason: Token-based server access validation failed with an infrastructure error by DarekBe


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 640909
Opened: 2/2/2011 4:27:02 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

we have 3 servers dbsrv (sql server is running as network service) and srv1 and srv2.
One user (domain)\dbuser while trying to connect to dbsrv1, configuring odbc (create new odbc connection from admin tools) getting the error:
Login failed for user '(domain)\dbuser'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <srv1 IP address>]. This error i see in the dbsrv logs.

But, the same operation from srv2 does not generate the error (the same user, the same operation).

Now, Other user (domain)\dbuser1 can succesfull connect to dbsrv from srv1 and srv2 (the same operation: creating odbc connection).

any idea. it was working and one day it stops.

Details
Sign in to post a comment.
Posted by Microsoft on 4/4/2011 at 12:00 PM
Hi,

We haven't heard from you in a while so I'll close this feedback for now. If you are able to collect the information and are facing the same issue again, please let me know and I'll reopen this issue.

Thank you and regards,
Don Pinto
SQL Server Engine
Posted by Microsoft on 3/7/2011 at 11:36 AM
Hi,

In order to investigate this issue further, can you please provide us with the error logs. Alternatively, you should also try the 'SQL Server Authentication Troubleshooter' which is available at -
http://blogs.msdn.com/b/sqlsecurity/archive/2010/03/29/sql-server-authentication-troubleshooter.aspx

Thank you and regards,
Don Pinto
SQL Server Engine
Posted by DarekBe on 2/3/2011 at 11:41 PM
Hello,
tnx for reply.
I has to correct one think. dbuser connects to dbsrv\instance, not to the dbsrv (root instance) as i described. Rest is correct. So the post should sound like this:
we have 3 servers dbsrv whith instance dbsrv\instance (sql server is running as network service) and srv1 and srv2.
One user (domain)\dbuser while trying to connect to dbsrv1\instance, configuring odbc (create new odbc connection from admin tools) getting the error:
Login failed for user '(domain)\dbuser'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <srv1 IP address>]. This error i see in the dbsrv logs.

But, the same operation from srv2 does not generate the error (the same user, the same operation).

Now, Other user (domain)\dbuser1 can succesfull connect to dbsrv\instance from srv1 and srv2 (the same operation: creating odbc connection).

any idea. it was working and one day it stops.
-------------------------------------------------------------------

I used the "SQL server" driver, version: 6.01.7600.16385, company: Microsoft, File: sqlsrv32.dll, Date: 2009-07-14.

But one more think: dbuser can successfull connect by using ssms, and osql while connecting to dbsrv\instance from srv1.

And one one more think i found:
dbsrv has two instance. dbuser has grant access to dbsrv\instance1 (sql login, and sql user) but do not has access to dbsrv - root instance. When i added dbuser to the root instance. Than dbuser can connect to the dbsrv\instance, but can't read any database. If i restore some database from dbsrv\instance to dbsrv, than dbuser connecting to dbsrv\instance and can read date (but it has to bee in root instance). It looks like sql client trying to connect to the root instance not to dbsrv\instance. It sounds crazy i know, but it look like some ODBC problem or what ???
Posted by Microsoft on 2/3/2011 at 12:51 PM
Thanks for reporting this issue to us.
To help us investigate the root cause, please identify the name of the ODBC driver you selected through the ODBC administrator tools.

Regards,
Microsoft SQL Server
Sign in to post a workaround.