Reporting Services Service acting strangely

Question

Whenever I start the SQL Reporting Services Service, the service starts successfully, but immediately logs three failed login attempts in the security event log.  The audit failure reports this:
An account failed to log on.
Subject:
Security ID: [domain]\[authorized service account]
Account Name: [authorized service account]
Account Domain:  [domain]
Logon ID: 0x19a662b7
Logon Type: 2
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:  [owner of reporting services database; different from service account above]
Account Domain:  [domain]
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
Process Information:
Caller Process ID: 0x508
Caller Process Name: D:\MSRS10_50.ORCHESTRATE_PROD\Reporting Services\ReportServer\bin\ReportingServicesService.exe
Network Information:
Workstation Name: [SQL Server]
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi 
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
The SQL Server log reports this:
Date  1/24/2014 10:40:05 AM
Log  SQL Server (Current - 1/24/2014 10:00:00 AM)
Source  Logon
Message
Login failed for user '[domain]\[authorized service account]'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
I don't even know where to start on this.  Reporting services and replication were working fine before the vendor started poking around.  I don't know what (if anything) they changed.  The logs show that the ReportService database and the
ReportServicesTempDB had indices restored just before the error started showing up.
Help?

Answer 1

Hi goodros_nemesis,
If you’re getting a login failed for your Windows user which you’re sure you put in the sysadmins role. And based on the error message “Login failed for user '[domain]\[authorized service account]'. Reason: Token-based server access validation failed with
an infrastructure error. Check for previous errors. [CLIENT: <local machine>]”, it’s probably because UAC isn’t passing all your group memberships to SSMS when you run it, and therefore giving you access denied.
To fix this issue, please try right clicking and running as administrator and seeing if it goes away. Of course if we added our user explicitly we’re probably fine, but just to get a cluster up and running. We can add domain admins user to the DB, and of
course that’s a membership that UAC will mask.
If there are any misunderstanding, please elaborate the issue for further investigation.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support