recently i was at a customer site trying to run reports from the SCCM console and it was failing with login failed.
Looking at the reporting logs, i saw the following “ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedExecution: Logon attempt for user ‘xxxxxx’ failed., Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException: Log on failed. Ensure the user name and password are correct. –> System.ComponentModel. Win32Exception: Logon failure: the user has not been ranted the requested logon type at this computer.
And looking at the error, it seems obvious, i typed the wrong username/password. I’ve checked it and tested and everything should be working, however, I was not sure about the AD replication. Anyway, i waited many hours just to be sure and the issue was still there.
After this, i used rsop.msc to check what policies where being applied and noticed that the Logon Locally policy was set and looking at the membership rules, i noticed that the SQL Server Execution Account was not there as well as nor any of the groups that account was member of.
Adding the account to the correct group, everything started working, so, if you’re getting this, remember to add the account to the “Allow logon locally” as well as make sure the account are not part of the “Deny log on locally”.