Unable to Login to SQL Server 2008 RC0 X64 installed on Windows 2008 X64 - by SUMIT SARKAR

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 353451 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 6/27/2008 12:06:37 AM
Access Restriction Public

Description

Unable to Login to SQL Server 2008 RC0 X64 installed on Windows 2008 X64

2008-06-26 23:26:41.32 Server      Authentication mode is MIXED.

Both the Ids are Admin  in this Box
 

2008-06-26 23:26:48.23 Logon       Login failed for user 'PEOPLESOFT\SUMISARK'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

2008-06-24 14:20:55.60 Logon       Login failed for user 'PEOPLESOFT\qaeuser1'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

SQLServer is running under Local System Account. 

Changed SQL server account from 'Local System' to Domain Account. 

Same Problem occurs.

Only Issue similar to this reported for Feb CTP

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2931470&SiteID=1

I do not see any Security Errors on the Security Log under eventviewer

Thanks Sumit 
Sign in to post a comment.
Posted by DarekBe on 2/2/2011 at 4:16 AM
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.

Posted by Microsoft on 7/29/2008 at 1:07 PM
Thanks for letting us know that things worked out well this way.

Best regards,
Torsten Grabs

Program Management
Microsoft SQL Server Engine
Posted by SUMIT SARKAR on 6/27/2008 at 3:14 AM
Issues is Resolved.

Logged in through Windows Authentication after bringing SQL Server in single user mode.

Started SQL server in Single User Mode using -m switch

Connected through Windows Authentication without errors.

sqlcmd -SQTNTDB03\SQL2008 -E
1>

Rebooted SQL Server.

Changed sa password through Management Studio

and now can connect using both Windows & SQL server authentication
Posted by SUMIT SARKAR on 6/27/2008 at 2:55 AM
Issues is Resolved.

Logged in through Windows Authentication after bringing SQL Server in single user mode.

Started SQL server in Single User Mode using -m switch

Connected through Windows Authentication without errors.

sqlcmd -SQTNTDB03\SQL2008 -E
1>

Rebooted SQL Server.

Changed sa password through Management Studio

and now can connect using both Windows & SQL server authentication.