ERROR_ACCOUNT_LOCKED_OUT=ERROR_ACCOUNT_LOCKED_OUT

Help Robot
,
1

We keep getting this but only ever on one VM.
All of the VMS are identical for software and setup within our Azure Environment nobody has been on the VM etc. Its very annoying, any ideas

Reason: ERROR_ACCOUNT_LOCKED_OUT=ERROR_ACCOUNT_LOCKED_OUT=0x00000775 : The referenced account is currently locked out and may not be logged on to…

2

The error message is pretty clear. Have you unlocked the robot’s login account? Also make sure the robot account has RDP permissions on that server. And make sure the password is correct in Orchestrator.

3

I know its pretty clear… but a) it keeps happening, but only to that VM, theres nothing to unlock there arn’t ay locks anywhere.
The Robot works 90% of the time then we get this periodically.
Passwords are all correct

4

I wonder if it’s a timeout issue and UiPath misinterprets the longer time it takes to log in with being the account locked.

5

There are a few possible reasons why you are getting the error message “ERROR_ACCOUNT_LOCKED_OUT=ERROR_ACCOUNT_LOCKED_OUT=0x00000775 : The referenced account is currently locked out and may not be logged on to” on one VM but not on others, even though the VMs are identical in software and setup.

  • The account may have been locked out due to too many failed login attempts. This could happen if someone is trying to brute-force the password for the account.
  • The account may have been locked out by a malicious actor. For example, an attacker could use a phishing attack to trick someone into revealing their login credentials.
  • There may be a problem with the VM itself. For example, the VM may be infected with malware or there may be a problem with the operating system.

To troubleshoot this issue, you can try the following:

  1. Unlock the account. You can do this using the Azure portal, PowerShell, or the Active Directory Users and Computers console.
  2. Check the event logs for the VM. This may give you clues about why the account was locked out.
  3. Scan the VM for malware.
  4. Check the VM’s operating system for updates.

If you are still having problems, you may need to contact Microsoft support for assistance.