Help me with solution for the below error,
“Could not start executor. The referenced account is currently locked out and may not be logged on to. (Exception from HRESULT: 0x80070775)”
Thanks,
Robert.
Hi @Robertraj,
Seems that you have something wrongly configured. Please give us more details if you are using robot/orchestrator, if it’s properly configured etc. I will make this post public as eventual solution can be helpful for others 
1 Like
We have configured orchestrator in Azure and we are using 2016 server with 10 terminals (10 Robots). The job is scheduled every 15 minutes 10 hours a day. At a point of time getting this error mesage "Could not start executor. The referenced account is currently locked out and may not be logged on to. (Exception from HRESULT: 0x80070775)" But at the same time other robot is running (with different terminal) . In the next 15th minute its running. say example we are getting the error 5 to 6 times a day (not repeatedly).
Hmmm it seems like from time to time after ending the job some of sessions are not logging out completely and are blocking machine to go with the next run. Try to observe “users” (robot) sessions after job. I think here might be a problem.