Earlier today I ran across an error message that I had not seen previously. The message said:
Login failed for user ‘[i’m not telling you our domain]\[or the service name]’. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Um…yeah…what?
I had just changed the service accounts for the instance. For whatever reason they got mixed up and I was trying to put things back in order. The real funny part to me is that when I started the service I know I saw the word ‘Started” in the console and left my RDP session because I thought I was done. Clearly I wasn’t, so I decided to put my MVP-ness to some use by immediately doing the following.
- Do a Google search for “Token-based server access validation failed with an infrastructure error.”
- Navigate to this link
- Read, and pay attention to the part about “logon failure” and “sysadmin”.
- Add the service account to the sysadmin fixed server role
- Restart services
- Miller Time
And now all is good. But since I had not seen that particular error message before I thought I should share it with both of you. You’re welcome.
