VM getting locked out

Hi All,

We’re having a process running multiple unattended bots in a High Density machine in Cloud. When processing scheduled jobs, some times we’re facing VM lock out issue saying 'The referenced account is currently locked out and may not be logged on to.
(Exception from HRESULT: 0x80070775) RemoteException wrapping System.Runtime.InteropServices.COMException: The referenced account is currently locked out and may not be logged on to. (Exception from HRESULT: 0x80070775) at UiPath.Service.Core.Windows.Session.LogonUserHeadless

After 30 mins again the BOT is getting unlocked by itself and running normal.

Can anyone please help me out in this.Attaching error screenshot also for reference.

this occurs usually when this account has tried many times wrong password, so account gets locked and maybe is released after some time…

Hi @bcorrea, i thought of the same but it’s not entering any password anywhere. if entering wrong password is the case it should get all the time right. But it’s happening only when running multiple jobs one after the another sometimes only the error is coming up.

Is this for local or domain accounts? Have you reviewed your Windows Event Log to see if there is further context for the frequent lockout?

We are also facing same issue. It throws error messsage for 1 time and next time is works. did you get the solution?

Anyone get the solution?

Check if these approaches are helping you:

Approach 1:

Refer blog - The Referenced Account Is Currently Locked Out And May Not Be Logged On To .

Kindly follow the links suggested below and check if this helps :

  1. https://social.msdn.microsoft.com/Forums/en-US/02044e43-d39f-41e6-9b00-683368f6f03a/the-referenced-account-is-currently-locked-out-and-may-not-be-logged-on-to-exception-from-hresult?forum=sqlreportingservices
  2. How to Fix “The referenced account is currently locked out and may not be logged on to” Error on Windows 10?

Approach 2 :

A) General:

  • Remove your network cable and restart your PC;
  • Disconnect the mapped drives, reset the password and try again;
  • Check your time and date settings

B) Security policies:

  • Click Windowa key + R, type secpol.msc, and hit Enter.
  • When the Local Security Policy window opens, select Security Settings.
  • Open Account Policy and select Account Lockout Policy.
  • Double-click on the Account lockout threshold policy (on the right) to open Settings configuration window.
  • To disable account lockout, replace the existing value with 0 and click Apply to save the changes.
  • Then press OK and close the Local Security Policy window.
  • After that, you will be able to log on to your account without seeing “The referenced account is currently locked out and may not be logged on to” error.

c) Validating DNS settings:

  • Right-click on Start button and pick Network Connections
  • On the right pane, select Ethernet
  • Click on Change adapter options on the right
  • Right-click on Ethernet and select Properties
  • From the list, find Internet Protocol Version 4 (TCP/IPv4) and click on Properties
  • In the Properties window, tick Obtain DNS server addresses automatically and click OK

D) Set account password to never experice:

  • Press Windows key + R, enter lusrmgr.msc and hit Enter
  • Select Users in the right pane
  • Right click on the user and pick Properties
  • In the General tab, tick the Password never expires box and click OK

E) Clear Cached credentials from system.

  • Click on Start button and type Credential Manager into the search box
  • Select Windows Credentials
  • Click and arrow next to credentials you want to remove and select Remove

Approach 3:

If the issue still persists we would recommend you to please log in to the robot machine using the same account manually multiple times and validate if the account is getting locked. In case the account is getting locked on the machine then please do get in touch with the local IT help desk as this seems to be an environment related issue.

Once the user account is activated again please go ahead and configure the same password again in the robot settings Orchestrator.


Approach 4 :

Kindly validate the below reference links and let us know if this helps.

  1. User account is currently locked out - #4 by ovi