RPA unable to connect to windows machine

Maros Gr_ninger
Tera Contributor

‎08-30-2023 05:06 AM

Hi All,

 

I have built unattended robot on MID server and it works well when I start process from RPA designer studio.

However when triggering bot process from instance, I get following error:

Failed to login onto the computer, please validate the credentials. Job was canceled.

 

Seems straight forward, that credentials are wrong. However I am using my credentials and I am able to log in with them. I have set up credential set, assigned robot and liked those together via process robot credentials record.

 

In windows I have configured unattended robot and connected it to the instance.

Does anyone have any idea what else it might be?

 

If anyone else is logged to the machine, I get different error:

Another user '************' was already logged on to this computer. Job was canceled.

This is easily fixed by signing off. But to me it looks like it is connecting to correct device because of that.

Anyway, any help or advice would be much appreciated.

 

Maros

  • 3,155 Views
8 REPLIES 8

Paul van Altenb
ServiceNow Employee
ServiceNow Employee

‎09-11-2023 08:29 AM

Hi,

I ran into the same issue. Have you found a solution?

Tha

sandeep16kumar7
Tera Contributor
In response to Paul van Altenb

‎08-06-2024 04:11 AM

Hi Paul,
This issue is existed when we giving  the wrong window user name is the credential set record.Please use the right Window user name after that you cannot faced this error.

sandeep16kumar7_0-1722942370716.png

Use below command to check your Window's username.

sandeep16kumar7_1-1722942672042.png

 

 

varadhi
ServiceNow Employee
ServiceNow Employee

‎09-22-2023 03:05 AM

Note: Before proceeding with these steps, ensure you have administrative access to the virtual machine (VM) and that you've backed up any critical data or configurations as needed.

 

  1. Uninstall and Install the Latest Login Agent:
  • Log in to the VM with administrative privileges.
  • Navigate to "Control Panel" > "Programs" > "Programs and Features."
  • Locate the old login agent in the list of installed programs, select it, and choose "Uninstall."
  • After the uninstallation is complete, download the latest login agent MSI from a trusted source or your instance.
  • Double-click the MSI file to run the installer.
  • Follow the installation wizard's instructions, which typically involve specifying installation options and confirming the installation.
  • Once the installation is complete, reboot the VM if required.

 

  1. Troubleshoot Bot Runtime:
  • Ensure the bot's runtime environment is properly configured to run when the VM is locked or signed out. This may involve modifying the bot's settings or using a task scheduler.
  • Test the bot's behavior by locking the VM or signing out and then triggering the bot to ensure it operates as expected.

 

  1. Uninstall and Install the Latest Unattended Bot:
  • Follow a similar process as in Step 1 to uninstall the old unattended bot from the VM.
  • Download the latest unattended bot MSI from your instance.
  • Run the MSI installer, follow the installation wizard's instructions, and reboot the VM if necessary.

 

  1. Test the Unattended Bot:
  • After installing the latest unattended bot, trigger it to perform its tasks.
  • Confirm that the unattended bot functions correctly even when the VM is signed out.

 

  1. Monitor and Verify:
  • Keep a close eye on the bot's behavior and performance to ensure it continues to work as expected.
  • Implement monitoring and logging to track bot activities and identify any potential issues.

 

  1. Documentation and Backup:
  • Document the changes you've made, including the versions of login agents and unattended bots installed.
  • Maintain backup copies of the installation files and any critical configurations for future reference or recovery.
0 Helpfuls

Ben_G
Tera Expert

‎10-17-2023 08:25 PM

Hi,

 

I ran into the same issue and found this post.

Login would work when the VM was locked with the login user but the robot would not be able to sign in.

 

After lots of googling, in the end changing the group policies below fixed the problem for me.

 

[Local Security Policy: Interactive Login: Do not require CTRL + ALT + DEL: Enabled]

[Local Security Policy: Interactive Login: Message title for users attempted to log on: Empty]

[Local Security Policy: Interactive Login: Message text for users attempted to log on: Empty]

[Local Group Policy Editor: Do not display the lock screen: Enabled]