Robot is unable to logon to RPA Assistant

This issue is encountered even when the robot is configured in Mastermind.

Perform these checks:

• Log on manually to the device with a different user account to observe the log on behavior.
  1. Open a ‘cmd’ terminal.
  2. Provide the ‘qwinsta’ command and click Enter to review the active RDP sessions on the device.
  3. Trigger a job in Mastermind.
  4. Provide the ‘qwinsta’ command a few times to confirm if the selected robot user appears on the list. If the user appears, see Robot is able to log on but nothing happens later.
• Ensure that interactive log on messages are disabled for the unattended RPA device. See, Disabling interactive log on messages section in the RPA Installation Guide.
• Verify that the Windows user being utilized as the RPA Robot has not changed the password or the password has not expired.
• Verify that the Windows user being utilized as the RPA Robot, is still a part of the RDP user group. This check must be confirmed when using the RPA Configuration Manager functionality in the Manage Users menu of the Mastermind application.
• Verify that Org or Device specific policies are not blocking the FreeRDP.exe process. Some AV providers flag this as a false positive.
• Verify that the robot and device are created in Mastermind with the proper domain value, if the robot is expected to log on as a domain user.

  For example, if the device is on Infor domain, the robot must be created with the domain set to Infor in the Creative Device menu of the Configuration Manager. The subsequent robots must also be created with the domain value set to Infor.

  Note: When mapping a robot to a device, the domain or the FQDN must be an exact match between both the device and the robot.