Named User Access with Impersonation set to 'Full'

From time to time, we get customer reports where the named users trying to run protocols gets the below error-

Pilot Error: Unable to authenticate the username and password (username = *****, domain = ****, impersonation token = 1). Logon failure: the user has not been granted the requested logon type at this computer.

Please note that with impersonation set to on, either the Security Policy "Log on locally" or "Log on as a batch job" must be enabled for the named users who are running protocols. The issue is most likely to get resolved if you set this security policy on the server.