November 26, 2011 at 12:37 pm
I have performed a fresh install of SQL 2008 x64 on a fresh install of Server 2008 R2 x64 in an AD environment. Upon install completion, I cannot login to the SQL Instance via SSMS, with the following error: Login failed for user domain\user. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ].
Background: the server is correctly joined to the AD Domain, the install was performed with defaults, windows authentication only (per organizational rules), the SQL install completes with no errors, domain\user was added as SQL Amin during setup account provisioning, I am logged into to console as domain\user when this error occurs, windows firewall is OFF, UAC is ON (an will never be turned off IAW organizational policy).
To troubleshoot this error I have tried:
Run SSMS as administrator: fail;
Start SQL in single user mode, run SSMS: fail
Start SQL in single user mode, run SSMS as administrator: Success
Start SQL in single user mode, run SSMS as administrator, remove domain\user from sysadmin group, re-add, run SSMS: fail;
Any combination and permutation of log off and log on, reboot, and chant gregorian prayers: fail;
Reimage server with 2008 x64, slipstream SP2 into SQL 2008 install, all above troubleshooting steps are repeatable exactly, so I've narrowed this down to not being a SP issue;
(this is NOT 2008 SQL R2)
Any suggestion on how to grant management access to this fresh install of SQL 2008 via SSMS? Our organizational policy is no console access to servers, management will be done via management tools intalled on client workstations. domain\user is a group of 8 users whom will have SSMS installed on workstations. However, we can't even access SQL via SSMS from the console! We cannot deploy this in an environment where these 8 users will have to sneak into the server closet on the weekends and have console access to SQL and run SSMS as administrator...
November 28, 2011 at 3:29 am
We received a similar case few days back in SSC. Faulty Logins were the issue. Can you please verify the Logins you are using didn’t change their password recently? Also can you verify that SQL Server Service is UP? If not, please verify the Error Logs.
November 28, 2011 at 3:35 am
Have the tcp/ip and named pipes providers been enabled under SQL Server Configuration Manager on the server by the person who installed SQL?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply